[Q] Rogers AIO mount/st110 - Captivate Q&A, Help & Troubleshooting

Hi Guys
Trying to go from Cyanogenmod 7 nightly back to stock
Been spending hours on this. Read through the AIO captivate thread and noted a few others with:
E: cant mount /dev/block/st110
(invalid argument)
E:Copy_dbdata_media:Can't mount DBDATA:
copy default media content failed.
Stuck in this loop, wont go past this point with newish Rogers Captivate
Initially it was the ODIN version causing it for Rogers users but supposedly v1.0 should be OK and that's whats packed with the Rogers Version
But i can't get passed the mounting issue, things i've tried:
1. Just loading pre packaged PIT file with repartition ticked - Hangs
2. Loading pre packaged PIT and PDA with repartiton ticked - Can't mount
3. Loading pre packaged PIT and PDA part ticked / reboot / reset button / load just PDA part unticked - Can't mount
I've seen others load different PIT and JM files but they mostly seem to be for the AT&T version.
Anyone know which files i can try individually for rogers to get past this mounting issue?
cheers

there is a guide here on how to go back from cm7 on fascinate, maybe that would work for your solution.

Had a quick look in the Fascinate forum, didn't see anything going back from CM7 i was also under the impression to OS structure was different for the fascinate?
In the mean time i managed to load just the PIT file with repartition ticked, but still a no go.
I've tried wiping user data, cache's, factory reset all from the 3 button recovery and Nada
everything keeps coming back to:
E:Can't mount /dev/block/stl10
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
copy default media content failed.
Luckily i can still get into recovery and download, but only with the buttons.
EDIT: Sorry put question in wrong section and currentyl following this thread to see if it fixes it http://forum.xda-developers.com/showthread.php?t=979133

You hear that ??? Thats my sign of relief
In all my reading around somehow i missed this thread http://forum.xda-developers.com/showthread.php?t=979133
Fixed it by flashing AT&T first and then the Rogers afterwards, worked like a charm.
Big thanks to the guys who provided the files, i couldn't thank you in the thread cos i don't have 10 post yet

Related

[Q] URGENT can't mount \dev\block\stl11 please help!

Hi Guys,
Just tried to flash from JG4 to JM8,
I followed the instructions as per http://forum.xda-developers.com/showthread.php?t=809423
Before i started i removed voodoo lagfix with the disable-lagfix method, then i did a factory reset.
I was up to step 2, that worked fine in Odin, then when i went to restart i got this error : can't mount \dev\block\stl11
any ideas what went wrong?
Thanks
Emm, what instructions have you followed? The link you gave is for kies and 2.2, not 2.1 and odin.
My guess - something to do with pit files and repartitioning. JG I think needs 513, while JM need 512, so repartition and try flashing one more time.
This does not belong in the development section ! The link you give is for update to froyo using kies .. You have flashed JM8 that is not froyo ! So make your question more clear and post it in q&a .. Anyway the error you get has to do with repartioning .. Flash JM8 again with odin check repartition and use .512 pit
sorry http://forum.xda-developers.com/showthread.php?t=807886
that is the correct link.
I used pit 512...
Edit: re-partition was checked and i definatly used pit 512... do you think voodoo had something to do with it?
reflashed again and and this is full error i receive in recovery;
E:Can't mount /dev/block/stl11
(Invalid argument)
update media, please wait....
update media, finished
# MANUAL MODE #
-- Applying Muti-CSC...
Installing Muti-CSC
mps_dat value: OPS
copy_multi_carrier from: OPS
multicsc : can not acces to /system/csc/OPS/system/
copy_common_data E:Can't mount /dev/block/stl11
(Invalid argument)
E:Can't mount /dev/block/stl11
(Invalid argument)
Do not leave csc blank in first step (flash to jm8). No idea why someone wrote it.
Hi,
i had the same problem flashing from JM5 to JM8.
When i clicked on reboot the system started without problem.
Then I flshed to JPM --> no problems either.
jahash said:
I was up to step 2, that worked fine in Odin, then when i went to restart i got this error : can't mount \dev\block\stl11
any ideas what went wrong?
Thanks
Click to expand...
Click to collapse
What happened is you probably flashed using Re-Partition but your PDA and/or CSC was missing the cache.rfs file.
If you tick Re-Partition, you MUST flash the complete set of firmware files (those that include cache.rfs and dbdata.rfs) otherwise you'll get errors like that.
To fix it you have to flash again with Re-Partition and make sure this time your PDA or CSC file has the cache.rfs and dbdata.rfs file inside. You'll lose all your app data, so backup first.
Next time when u flash, don't Re-Partition unless you know you need to. For example, the official JPM/JP6 Froyo update files do not come with a dbdata.rfs, so if you (wrongly) click Re-Partition when u flash them, you're gonna get a similar error but with the /dbdata partition instead.
Had the same problem when I forgot to do disable OCLF on one of my reflash.
I repartitioned, then flashed to JM8 with odin without repartioning (all pit 512) and worked like a charmed.
The only time i get this error is when i flash a FW and it requires a diff pit file.
I am getting a similar error when attempting to "format internal sd-card" in recovery mode.
I get the following error:
update media, please wait
E:Can't mount /dev/block/stl10
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
your storage not prepared yet, please use UI menu for format and reboot actions.
Similarly, I didn't remove OCLF before I attempted to flash XXJPM using Odin, so maybe it has something to do with that?
Does a full flash overwrite any changes made by OCLF? If not, how can this be remedied?
I also flashed using Step 3 from the same link as was provided by jahash. I think it may have something to do with the lagfix not being removed.
Should have read further before posting I guess, but I think my question is answered in post #7 of the HOWTO link.
My next question is, can anyone point me to a dbdata.rfs file that would resolve this problem?
redcell said:
I am getting a similar error when attempting to "format internal sd-card" in recovery mode.
I get the following error:
update media, please wait
E:Can't mount /dev/block/stl10
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
your storage not prepared yet, please use UI menu for format and reboot actions.
Similarly, I didn't remove OCLF before I attempted to flash XXJPM using Odin, so maybe it has something to do with that?
Does a full flash overwrite any changes made by OCLF? If not, how can this be remedied?
Click to expand...
Click to collapse
This happened because when u flashed JPM you ticked re-partition (which you shouldn't have). Its not caused by OCLF.
To fix it you have to flash again with re-partition using another firmware package which has the dbdata.rfs file (JM8 for example, JPM is missing it). Then after that if u want JPM flash it but DONT tick re-partition.
Thanks hardcore, that's exactly the info I was looking for. I will re-flash wish JM8 and then with JPM with partition unchecked.
Thanks, I'll report back with results.
As you said, I made a mistake. Went through steps 1, 2 and 3 and everything is fine now! Cheers!
i do have the exact same problem but flashing JM8 doesn't solve it.
in odin 1.3 with re-partition enabled I used s1_odin_20100512.pit, CODE_I9000XWJM8.tar.md5 as PDA and MODEM_I9000XXJM4.tar.md5 as phone
on startup I still get "E:Can't mount /dev/block/stl11 (Invalid argument)"
any ideas please?
XIAfbk like one of the rep said earlier, you must also flash with csc as well. So pick your original csc when you flash JM8. I had the the same problem and it was fixed when i flash the second time with my original csc as well.
drbunny said:
XIAfbk like one of the rep said earlier, you must also flash with csc as well. So pick your original csc when you flash JM8. I had the the same problem and it was fixed when i flash the second time with my original csc as well.
Click to expand...
Click to collapse
Where do you get an original csc file? I'm having exactly the same problem..
My phone is orange uk.. did not back up efs folder before flashing to froyo via kies reg hack.. Didn't know i had to..
Changed phone to xeu csc on froyo but now am reflashing whole process jm8-jpm-jpo.. to try to fix some modem issues..
Thanks
hardcore's post helped me a lot the procedure he posted works well ..... thanks hardcore
I just got out of this issue after struggling for 1 whole day. I tried each and every solution/suggestion/recommendation available on the web but NOTHING seemed to work. If you are in the same boat, here is some good news for you.
You don't need to mess around with CWM or Voodoo or whatever, simply use ODIN to flash the latest stock JPU (2.2.1) from the link below. This one does a complete rewrite of every partition on your device, including /cache, which is the issue here.
http://hotfile.com/dl/88094739/f5545cc/I9000XXJPU.exe.html
Once it is done, all your partitions will be properly mounted and formatted as per defaults. Then you may choose any rom you may like.
Just make sure you use the PIT, PDA, MODEM, and CSC files come with this firmware. Don't forget to click repartition.
Good luck!!!

Galaxy S - Doesnt boot any firmware except JM8

Hello,
I apologize if im violating any rules here, but the problem is making me so sick that i dont know what else to do ..
i recently got a i9000, locked to THREE.. had it unlocked, tried to update it via KIES but bricked on the Samsung S (static splash screen).. i tried a couple of firmwares, 2.2's and 2.2.1 (XXJPU) included.. all would just sit at the splash screen doing nothing.. even left it like that for an hour, but still nothing ..
im not sure what to do here. . whenever im stuck, i flash JM8 and while booting it gives me the following:
E: Cant't mount /dev/block/stl11
(invalid argument)
multicsc : cannot access to /system/csc/H3G/system/
copy_common_data E: Cant mount /dev/block/stl11
(Invalid Argument)
E: Can't mount /dev/block/stl11
(Invalid argument)
this only occurs once, once i select reboot system now it reboots fine and after that all other reboots go fine..
another thing that happens is that whenever i flash another firmware via ODIN, i cannot get the 3 -button recovery to work only the download.. while the 3 button recovery works on JM8
please help me.. this fone is driving me crazy
Have you tried re-partitioning in Odin before flashing?
Check re-partition, select correct pit-file, plug, flash, unplug, remove batt for 30 secs, uncheck re-partition, NO pit, select pda, modem, csc, plug, flash -> should work.
i actually tried a different trick to get rid of the errors ..
i used the modem and pda files from JM8 and the CSC file from JPU .. with repartition ticked i used the 512.pit to flash the phone via Odin.. all the errors went away .. well almost .. the phone started throwing a new error .. couldnt mount /dev/blocl/memblk10 or something ..
well .. thats something for the past now.. i got my cell changed .. things seem fine now .. thnx
For anyone checking this thread later for a solution...
I had the E: Cant't mount /dev/block/stl11 error myself and was able to recover via some combination of repartition and supplying a pit file. However, I was simply using a stock firmware for my phone (JH2 with 512 PIT). No fancy pda/modem/csc mixing needed for me

Can anyone Help Me Get Back to Rogers 2.1

I have a Samsung Captivate that was running 2.2 flashed by Keis.
I could not see all of my internal sd space so I wanted to flash a custom rom.
I have used Titanium Backup to back up my phone.
I then Tried to use AIO Captivate Toolbox 2.5 to flash back to stock.
Now every time that I try to boot my phone it goes into system recovery <2e>
at the bottom it says
update media, please wait ...
e:Can't mount /dev/block/st101
(invalid argument)
e:copy_DBdata_media:Can't mount DBDATA:
copy defaul tmedia content failed.
Please Help
Just to add to the last post I can still get into download.
download the file in my sig. Flash it with odin 1.3
http://dl.dropbox.com/u/20958367/Odin3 v1.3.exe
I can walk you through it if you like.
I got 1.3 from the link that you gave me, but neither link in your signature works.
Could you post them again?
windburn said:
I got 1.3 from the link that you gave me, but neither link in your signature works.
Could you post them again?
Click to expand...
Click to collapse
theres the new URL for 2.1
http://dl.dropbox.com/u/20958367/I896UXJI2-homebinary.tar
Thank you so much.
I am downloading it now.
Just a few questions.
When I do odin what do I select pit, PDA or what?
Also do I have to change any of the options like re-partition?
Don't change any options at all. Open odin and leave it as is.
The file goes into the PDA section, no pit file is required.
odin did it's thing said pass 1:51.
Then it re-booted into android system recovery <2e>
What would you like me to do?
Exit recovery, and attempt to boot the phone.
I thought we had it but no luck.
it is still going into recovery
with this error
update media, please wait ...
e:Can't mount /dev/block/st101
(invalid argument)
e:copy_DBdata_media:Can't mount DBDATA:
copy defaul tmedia content failed.
try flashing the 2.2 one it has a different recovery 3e.
I am downloading now.
I will let you know what happens
Once it reboots it should go into recovery and install a bunch of files and then boot back up by itself.
It re-booted into recovery but got the same error.
It did not install any files or reboot again.
windburn said:
It re-booted into recovery but got the same error.
It did not install any files or reboot again.
Click to expand...
Click to collapse
Its by me at this point. That method has always worked for me.
Sorry I couldn't get you any further than you were.
I was reading this does it make sense to you
http://forum.xda-developers.com/showthread.php?t=788850
It looks Like I screwed up the partition table does anyone have a pit file for 2.2 Rogers?
windburn said:
It looks Like I screwed up the partition table does anyone have a pit file for 2.2 Rogers?
Click to expand...
Click to collapse
Reading that, its sounds exactly like what happened.
I don't know of any pit file for Rogers.
Thanks for your help nickm50
I will keep looking and see if I can find any way to fix this.
Maybe someone who has fixed the problem before will let us know how they did it.

E:failed to mount /sdcard (File exists) Problem

Hello every one,
I tried to flash my Bell Samsung Galaxy GT I 9000M with gingerbread but things got messy and now I am stuck in bootloops...
I have already tried to flash back to the stock Eclair room but it's still not working.
I can still access download mode and recovery.
Here is the error message I get when I go into recovery:
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet, please UI menu for format and reboot actions
Media files copy failed.
I think I need the seperate PIT, PDA and PHONE files to flash via Odin ticking repartion, and then upgrade to last version avaible via kies to fix this. But I don't where to get this files for Bell Canada I9000M.
I don't know how to fix this. Can someone help me ?
Here was my phone stock configuration before all that happens:
Baseband version
I9000UGJL2
Firmware
2.2
Kernel
2.6.32.9
[email protected] #3
Build number
FROYO.UGJL2
galaxy s vibrant bell
gt-i9000m
Note: I hope I posted at the right place, if not the mods can feel free to move it
google searched and found this in an old thread:
http://forum.xda-developers.com/archive/index.php/t-768441.html
http://www.multiupload.com/N62CDNXXXK I haven't downloaded the file so I'm not sure if it is 3 parts.
The other thing I'm thinking of (and I hope is not true), is the time when all Bell I9000M phones were dying after the official upgrade to froyo 2.2
http://forum.xda-developers.com/showthread.php?t=886158
Best of luck to you, sorry I can't be of more help as I'm not that experienced with this.
Thanks man.
I found a way to fix it. I installed back the stock I9000UGJL2 froyo via ODIN using 512 PIT file and repartition, then I got this new error message
E: can't mount /dev/block/stl10 (invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
your storage not prepared yet, please use UI menu for format and reboot actions
copy default media content failed
After that I followed this tuto http://forum.xda-developers.com/showthread.php?t=984140 to solve it.
Now I'm back on trail and I have to find a safer way to instal Gingerbread JVH.
I will try the method that you described me here http://forum.xda-developers.com/showthread.php?t=1075144&page=2 but I would be happy to have some more details and the exact files I have to use...
I'm afraid to get in troubles again.
Thanks again for your help JJustin.
I found a way to solve my problem (i described it in the other thread I started http://forum.xda-developers.com/showthread.php?p=14620127#post14620127).
Now eventhough I am not so confident, I will try to install gingerbread again using other methods.
I am open to any ideas. I will let you guys know if I get it right.
Thank you all.
If u want gingerbread follow darkys guide exactly and u will run gingerbread
Sent from my GT-I9000m using XDA Premium App
nguetto said:
I found a way to solve my problem (i described it in the other thread I started http://forum.xda-developers.com/showthread.php?p=14620127#post14620127).
Now eventhough I am not so confident, I will try to install gingerbread again using other methods.
I am open to any ideas. I will let you guys know if I get it right.
Thank you all.
Click to expand...
Click to collapse
wat was it?
OH S***T!!!!! Thank you very much worked like a charm!!!
Plss help me i9000
I heve this error in my galaxy s i9000 .

[Q] Stuck on Samsung logo, recovery says can't mount /dev/block/mmcblk0p1

Hi.
I'm trying to fix my boss' tab, SPH-P100 (Sprint).
I have tried all kinds of things and nearly bricked it (got the phone ! computer symbol, but it still accepted uploads, so I was OK).
Here's the issues:
- Continuous loop of Samsung logo on boot
- From Recovery screen, I performed a factory reset, but it didn't help - same logo loop
- In the Recovery screen, I get errors similar to the ones quoted above:
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
I read all kinds of posts about simply flashing the stock ROM, and I found the ROM that was mentioned multiple times in these forums to be the right one for this tab (it did change the first boot animation, though...). The ROM I used is tab_sprint_noModem_20101226.tar inside Tab_Stock_-_No_Modem.rar.
I tried:
-ODIN with the stock ROM posted in this thread. It works, but it doesn't fix anything. I tried with and without the PIT file (one thread specifically warned NOT to use the PIT file, but in the end I tried it anyway - I think I did NOT hit Repartition, so it probably didn't do anything...).
-Heimdall doesn't seem to work at all for me. I found version 1.3.1, and the instructions in post 21 of the thread linked above don't seem to apply to this version. I finally figured out that I need to be in the FLASH tab, but I can't add files without the PIT file, it won't let me add the zImage file for recovery (or at least complains that there's no .bin file ending), and when I checked "Repartition", I got the error:
ERROR: Partition corresponding to -21 argument could not be located
Ending session...
Yes, I installed the drivers that came with Heimdall.
-Following other posts with very similar errors, I formatted the SD card in Windows using FAT32 - no change.
-I looked into another thread talking about parted, but I don't have root on that device, and I'm not sure what my boss would think about me rooting his pad... I also don't know enough to figure out which rooted ROMs would go with it - I'm scared enough with the "official stock rom" I'm using
I'm fairly tech savvy, know a little about Linux and have used adb to root my own phone, but otherwise a lot of the things I read here only make enough sense to me to follow the instructions and not get lost.
Maybe there's a different version of Heimdall that I should be using, or maybe I did something else wrong, but I'm sure I followed the instructions here.
Any help would be greatly appreciated!
Thanks in advance!
(PS, I originally posted this at the end of the thread I mentioned here but did not get an answer - I'm sorry, I had not read the post about not asking questions in that forum, even if it was attached to another post where similar questions were asked and answered, so I'm moving this post here instead.)
Update:
Found a different Rom in this thread - same situation:
I can flash it, but nothing changes, and I still get the error message I showed. The main change is that this ROM is the first I have found that has the same Sprint boot animation that the tab originally had.
The new information is that once it resets after flashing, it briefly shows a few messages - one said that if failed to wipe the cache, and I think the others showed the same error about /dev/block/mmcblk0p1 but I can't be sure (tried to get video of it, but I was too slow, and it's blurred - I'll try again later to get the exact error messages).
Update 2:
Found yet another ROM in this thread and tried it, and this one doesn't seem to work at all with this tab (tried with and without pit/re-partitioning) - the boot fails and immediately boots into Recovery by itself and shows the following:
-- bootmode=7 from cmdline
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/command
-- Wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting/cache...
E:format_volume: rfs format failed on /dev/block/mmcblk0p1
Data wipe failed.
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (No such file or directory)
Click to expand...
Click to collapse
Will try to flash the other ROM again to try and get a precise look at its error message...
UPDATE 3:
Flashed the first ROM again - no error message, just the same Samsung logo cycle that freezes briefly and then starts over.
Flashed the second ROM again (the one that has the correct Spring animation), and this time I got the error messages on video.
-- Wiping DATA:...
Formatting DATA:...
DATA: wipe failed.
-- Wiping CACHE:...
Formatting CACHE:...
CACHE: wipe failed.
--Wiping DBDATA:...
Formatting DBDATA:...
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
Rebooting...
Click to expand...
Click to collapse
Still hoping for ideas, but I think I'm at the end of what I can try...
Is it likely or possible that the internal memory got damaged?
I don't know exactly what my boss did to the tab, but he mentioned something about "the cold" meaning Minnesota winter cold - we had about 12 degrees last week, so maybe that's the cause...
Have you found and tried the EA24 stock flash tool?
Sent from my SPH-P100 using xda premium and ICS
Thanks for the reply!
If that's this file:
Sprint Galaxy Tab EA24 Flasher.zip
Then I have tried the ROM in it with Odin, but not the actual tool that came with it.
I'll see if I can get my boss to give me another shot with it (unless he's already returned it - I've had it for a few days already...).
Thanks!
has anyone found a solution to this? I am having the exact same issue...
Not sure why or how it happened everything was fine one day and next day wont go past logo and keeps rebooting.
Same problem here
My P100 started this problem last night, which was the first time it's been turned in in several days. It's fully stock, never had any rooting or flashing performed on it.
Booting into recovery mode shows failed mounts on everything it tries to do, and all the options for recovery also fail - except for "reboot system now", which does reboot it, but then it just sits on the pulsing Samsung logo endlessly. And I do mean endlessly, I let it go four hours last night, after which the battery ran out. Plugged it in after that, and it's right back to the same thing.
Every other thread I've found with this problem listed it as an after-effect of having attempted to flash a new ROM, but that is not the case with mine...
Hoping someone has the answer...
Thanks!
-mike
Same exact symptoms, and when I tried CM9 or other ICS ROMs this errors lead into the dreaded "Encryption Unsuccessful" bug.
At this point I'm just trying to get the device to boot consistently.
ChrisCTX said:
Same exact symptoms, and when I tried CM9 or other ICS ROMs this errors lead into the dreaded "Encryption Unsuccessful" bug.
At this point I'm just trying to get the device to boot consistently.
Click to expand...
Click to collapse
Did you try to do full restock (include bootloader and repartition)?
or you can try CM9 again with a fixed kernel by cdesai or jt. look at this conversation:
http://forum.xda-developers.com/showpost.php?p=28584567&postcount=2320
yappoe said:
Did you try to do full restock (include bootloader and repartition)?
or you can try CM9 again with a fixed kernel by cdesai or jt. look at this conversation:
http://forum.xda-developers.com/showpost.php?p=28584567&postcount=2320
Click to expand...
Click to collapse
I'm on it ASAP, thanks a ton for that
Edit: If possible mind giving a link to that specific kernel (or flashable .zip with it)?
Do you have this on your screen:
http://forum.xda-developers.com/attachment.php?attachmentid=1193979&d=1342124106
If so, we're in the same boat
Btw, I used a full repartition and boot following this thread:
http://forum.xda-developers.com/showpost.php?p=17817287&postcount=2
and same error occurs.
Bump in hopes of solving this issue.
My tab is basically bricked. I have this same issue after putting CM9 on it. Those errors consistently pop up. and thats it.
I guess its a paper weight now.
you may try flashing pit file and stock rom with micro SD inserted during flashing. that's what I did to my Samsung GT-I9003 when it failed to read the internal SD. At first, the camera may not work. Just root the device after flashing pit/ROM and do SD Swap Mod (external SD as internal SD).
Not sure if it's gonna work with Galaxy Tab. Give it a try. Hope this helps.
Hey guys, it appears JimRich is working on a solution for the CDMA (verizon and sprint) versions of thsi device, keep checking and be sure to let him know there are other people with this problem. http://forum.xda-developers.com/showthread.php?t=1789728

Categories

Resources