Database Develop

[Q] Help! Can't Delete Files on Galaxy S

Hi everyone,
My galaxy S recently had the "System UID Inconsistent" problem. As solution, everyone says to wipe data, or reinstall the rom. I've did it a lot of times, and this still continues. I've now installed the clockwork recovery mod to try to wipe the data and fix permissions.
The strange thing is that I mount the USB Storage, delete ALL FILES ON THE PHONE, and go back to the recovery ALL FILES ARE BACK THERE. I don't have any clue on what is happening, why all files get back to the phone, and why i can't delete the files on it. Can someone help me?

Hi Mate,
Follow the link posted below and hopefully your problem will be fixed.
http://www.theandroidsoul.com/ezbase-ezrom-for-android-2-2-install-revert-back/
Cheers

Tryed it, FAILED
With the "Repartition" ticked, it give an error that can't do the repartition... Without it checked, it completes the proccess, but he doesn't finish to boot.
I think that the data partition is really ****ed up... when it finish to install the official rom when it comes to the recovery mode, it gave me some errors on dbdata (he can't write it) and some errors to wipe the data partition.
here are some errors that usually occurs.
Flash errors said:
E:failed to mount /dbdata (File Exists)
E:delete_data_files:Can't mount /dbdata
your storage not prepared yet, please use UI menu for format and reboot actions.
Media File copy Error
-- Deleting files...
E:failed to mount /dbdata (File Exists)
E:delete_data_files:Can't mount /dbdata
your storage not prepared yet, please use UI menu for format and reboot actions.
-- Updateing filesystem...
E:failed to mount /dbdata (File exists)
E:discard_filesystem_for_rfs:Can't mount /dbdata
-- Wiping cache
Formating /cache...
Cache wipe failed.
--Applying Multi-CSC...
(here all goes ok)
Click to expand...
Click to collapse

Nobody? No one knows why files can't be Deleted? It's really bricked?

an idea..
hi dark,
you have a re-partition problem which means probably you made lagfix and you just install a new firmware wout taking lagfix back
you should install a firmware which has an ability to repart your phone. Your best alternative is I9000XXJPU 2.2 Froyo Rom which has a future with it. download it. from samfirmware and install it.
and then upgrade as u want to girgerbread etc..
i hope this helps

Ok. I'll try soon... but, I've never made a lagfix on my phone

hello,
i have the same problem. Have you found a solution?
thanks

Try what everyone said befora... but still don't get any clue about the problem

Do you have the I9000 M << by any chance ? These are know for SD card failures, resulting in strange behaviour like you have mentioned..
Also what firmwares have you tried to flash with odin ?
something waaaaay back always works for me, Something like Eclair with all 3 files and 512PIT... No matter whats issues i have encountered, That firmware always makes my phone better
Good luck, Hope you get it sorted

Mine is T ... I have read about the M problems and tryed the same with T ... but nothing worked... I've flashed 2.1 2.2 and 2.3 official roms but doesn't worked... I still have the "Undeletable partition" issue... I think that it'll be a Time Capsule, frozen files in time to record later.

undeletable partition sdcard and "System UID Inconsistent"
Hi Dark FlameS,
have you found a solution to your problem, I also have the same?
The only ROM that don't give me at the beginning the "System UID Inconsistent" is probably the last one I installed 2.3.5 i9000XXXJVS before the partition /sdcard became undeletable.
With that ROM I can use at least the phone to make phone call and navigate, but I can't install or delete any program on /sdcard.
This is very frustrating!
Please someone help us thank you very much in advance!
This is the log of ODIN and it seems there are no error but the /sdcard (internal sd) are always there!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_XFJVA_Sbl.tar.md5 is valid.
<OSM> PHONE_XXJVT.tar.md5 is valid.
<OSM> CSC_OXFJV1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> param.lfs
<ID:0/004> NAND Write Start!!
<ID:0/004> zImage
<ID:0/004> boot.bin
<ID:0/004> Sbl.bin
<ID:0/004> factoryfs.rfs
<ID:0/004> dbdata.rfs
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response form LOKE
<ID:0/004> cache.rfs
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!

No, Haven't found any solution
I'm from Brazil, and this phone was bought over the internet and it's not from Brazil. I'm not sure if it is from New Zealand or Mexico...
I had seen some people telling that this occurs only with I9000T Early versions, and people who had this problem had changed their phone on the warranty... But, samsung Brazil says that they can't do nothing for me 'cause they don't have the software for my phone, just for the Brazillian version of the phone (I9000B)...
If your phone is not an I9000T, search a bit more for a solution, it may be just corrupted files. My case is that the filesystem won't write nothing more, so the phone can't delete the files there and neither write files.
I've seen that some Galaxy phones crash sometimes with files that has large names and lightbox photo app sometimes write files with these large names and the system file goes crazy, if you handle to delete these files, maybe your phone could work, if you're lucky.
Lightbox might have been the sparkle to this occurs to me, as it has occured in the day that I have instaled it. Or maybe it was changing the sd card that i had in there, that I've done in the same day...
I just could say to you know that I have no solution, the only solution will be buy a new phone. Hope that you're luckyer than me...

Thank you for the reply, mine it's a I9000 but I installed superuser.apk and for the same reason (undeletable file, apk, and partition) I can't delete it, so I don't think they will accept the warranty!

But you still could try the payed fix... they can't refuse... The problem with me is that samsung brazil only fix brazillian phones

Hung on Logo display... CWM Recovery Mode works

Hi,
I am new to this and seeking help from you all.
I have some problems and after the restart it stops at Galaxy S main screen. When in CWM Recovery Mode v3.0.0.5, I found that the volume is not mounted. When I try to mount the volume under Mounts and Storage > mount USB storage, I get:
E: unknown volume for path [/data]
E: unknown volume for path [/data]
E: Unable process volume! Skipping...
Checking /cache...
E: unknown volume for path [/cache]
E: unknown volume for path [/cache]
E: Unable process volume! Skipping...
Done!
E: unknown volume for path [/cache/recovery/command]
E: Can't mount /cache/recovery/command
E: unknown volume for path [/cache/recovery/log]
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: unknown volume for path [/cache/recovery/last_log]
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: unknown volume for path [/cache/recovery/command]
I cannot do anything. Please guide me as I am new to all this.
Regards,
A Failed I9000

you need to get the latest CWM here
you will have to run partition sdcard and, YOU will lose everything on it. So take out sdcard and copy all to pc.
See this post

Okay.. that's a bootloop..
No need to worry.. Just flash a stock gingerbread firmware like jw4 or jvu via Odin...
u Can get it from samfirmware.com for Ur country..
If my post helped, don't mind hitting THANKS 

drakester20 said:
Okay.. that's a bootloop..
No need to worry.. Just flash a stock gingerbread firmware like jw4 or jvu via Odin...
u Can get it from samfirmware.com for Ur country..
If my post helped, don't mind hitting THANKS 
Click to expand...
Click to collapse
Thank you... This is the result from Odin
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Please guide me next as I have no clue here. My phone only goes into the download mode and not to Recovery Mode anymore. Did I screw it up?
Please help.

Taysider said:
you need to get the latest CWM here
you will have to run partition sdcard and, YOU will lose everything on it. So take out sdcard and copy all to pc.
See this post
Click to expand...
Click to collapse
I have clicked on the link but it said it will get downloaded to your phone. nothing happened even after 30 mins.

U flashed the correct firmware, right?
If my post helped, don't mind hitting THANKS

Hey
Dies your fone boot properly?
Cheers
If my post helped, dont forget to hit the thanks button..

tchindalia said:
Hey
Dies your fone boot properly?
Cheers
If my post helped, dont forget to hit the thanks button..
Click to expand...
Click to collapse
I flashed it two times more but nothing happens... the previous ROM is flashed out and I can now see the phone in only Download mode...

1. Go to samfirmware.com.
2. Download stock firmware
3. Flash in odin with repartition checked. Pit file dont matter
4. Wipe data/factory reset from stock recovery
5. Flash Semaphore ICS kernel tar in pda through odin, no repartition.
6. Boot into recovery
7. Flash whatever you want
8. Sucess.
No format of sd needed.

AlwaysDroid said:
1. Go to samfirmware.com.
2. Download stock firmware
3. Flash in odin with repartition checked. Pit file dont matter
4. Wipe data/factory reset from stock recovery
5. Flash Semaphore ICS kernel tar in pda through odin, no repartition.
6. Boot into recovery
7. Flash whatever you want
8. Sucess.
No format of sd needed.
Click to expand...
Click to collapse
Thank you, AlwaysDroid. This worked.. You saved my phone...

Randomly Stuck on Boot logo? (Possible eMMC issue?)

Hi Guys,
I have a Galaxy S3 (i9305) Rooted on Stock 4.4, Knox disabled, w Xposed. Running Philz Recovery.
Anyways, I woke Saturday morning to my phone stuck on the Samsung Boot Logo.
I tried rebooting several times to no avail, so tried a recovery via Philz. (I can get into Odin Mode / Recovery no problems)
However when I try to do a restore, it fails. When I initially boot up Philz I get this;
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
And when I try to wipe caches / system etc I get an error message;
E: format_volume: make_ext4fs failed on /dev/block/mmcblk0p12
Tried flashing stock FW via Odin and that fails.
So not sure what I can do? From my research it looks like the eMMC (internal SD) has croaked, but how can I be
absolutely sure? Has anyone had a similar situation and been able to recover?
Thanks in Advance!

BrikHaus said:
Hi Guys,
I have a Galaxy S3 (i9305) Rooted on Stock 4.4, Knox disabled, w Xposed. Running Philz Recovery.
Anyways, I woke Saturday morning to my phone stuck on the Samsung Boot Logo.
I tried rebooting several times to no avail, so tried a recovery via Philz. (I can get into Odin Mode / Recovery no problems)
However when I try to do a restore, it fails. When I initially boot up Philz I get this;
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
And when I try to wipe caches / system etc I get an error message;
(will enter exact info when an home and can see phone)
Can't format /system/ doesn't exist?
Tried flashing stock FW via Odin and that fails.
So not sure what I can do? From my research it looks like the eMMC (internal SD) has croaked, but how can I be
absolutely sure? Has anyone had a similar situation and been able to recover?
Thanks in Advance!
Click to expand...
Click to collapse
Try TWRP.
Flash: http://d-h.st/users/psndna88/?fld_id=34039#files (all files). But attention, when you format 'data' partition, you lost all files from internal (you can skip format data, or if you not have important files, format)
After this, flash a new rom with Odin (or if you have custom rom, flash again)

il3gal said:
Try TWRP.
Flash: http://d-h.st/users/psndna88/?fld_id=34039#files (all files). But attention, when you format 'data' partition, you lost all files from internal (you can skip format data, or if you not have important files, format)
After this, flash a new rom with Odin (or if you have custom rom, flash again)
Click to expand...
Click to collapse
Thanks il3gal.
When I try to flash TWRP (Which I had before I installed Philz) I get the following from Odin;
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)​
Can you provide a bit more info about how I flash those 4 files? If I can?

BrikHaus said:
Thanks il3gal.
When I try to flash TWRP (Which I had before I installed Philz) I get the following from Odin;
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)​
Can you provide a bit more info about how I flash those 4 files? If I can?
Click to expand...
Click to collapse
This 4 files is for format your partition in ext4. (if you try to modify partitions with f2fs or others)
Try 2/3 times with Odin and TWRP. If not work, download stock rom from http://www.sammobile.com/firmwares/database/GT-I9305/ and install with Odin
What Odin are you use to flash TWRP? Reinstall usb drivers or change usb port

il3gal said:
This 4 files is for format your partition in ext4. (if you try to modify partitions with f2fs or others)
Try 2/3 times with Odin and TWRP. If not work, download stock rom from http://www.sammobile.com/firmwares/database/GT-I9305/ and install with Odin
What Odin are you use to flash TWRP? Reinstall usb drivers or change usb port
Click to expand...
Click to collapse
Do you use Odin to flash those 4 files? If so what are they 'AP'?
I've tried to flash on 2 different computers using (5) different cables. Still no luck at all..
Using Odin 3.10.6
I think I'm screwed..

BrikHaus said:
Do you use Odin to flash those 4 files? If so what are they 'AP'?
I've tried to flash on 2 different computers using (5) different cables. Still no luck at all..
Using Odin 3.10.6
I think I'm screwed..
Click to expand...
Click to collapse
For .zip files you need flash with recovery (cwm/twrp/philz)...but if you try with Odin and is not work..i dont now if my method is work for you..

download odin 3.09.....i tried odin 3.10 and it did not recognized my phone and download the usb drivers from the recovery thread on the developing section.
http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249

Thanks il3gal, tried to flash those zips and get an error message;
E: Failed to setup expected mounts for install; Aborting

hexisg said:
download odin 3.09.....i tried odin 3.10 and it did not recognized my phone and download the usb drivers from the recovery thread on the developing section.
http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
Click to expand...
Click to collapse
Thanks hexisg. Tried 3.09 and same issue. No Luck.

Recover Samsung Galaxy S2 - T817 5.1.1.

Greetings! I've managed to brick my Samsung S2 T817 (5.1.1). I'm stuck in one of two bootloops.
1) Your device didn't update successfully use the Verizon Software Repair Assistant...
2) ODIN Mode
Download Speed: FAST
Product Name: SM-T817V
Current Binary: Samsung Official
Downloading....
Short story, I (foolishly) tried to root using ODIN an a T810.tar and I bricked the device. Can someone send me a URL for the Verizon Assistant Recovery software OR provide steps direction on how to un-brick my device? Any help you can provide would be awesome!

Just flash the stock Firmware with Odin.
http://easy-firmware.com/index.php?a=browse&b=category&id=6552

Thanks for the help Ashyx but when I download/extract the MD5 file I cannot flash the package.
I was sure to run Odin as Admin. My tablet displays the following:
SW REV. CHECK FAIL. DEVICE: 2. BINARY: 1
Odin Odin presents the following error:
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> param.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any idea what I'm missing? Thanks for the help!

Try flashing just the recovery. Convert it to a tar archive first.

Still Bricked
ashyx said:
Try flashing just the recovery. Convert it to a tar archive first.
Click to expand...
Click to collapse
Thanks for the tip but no luck. I used 7-zip to create a tar file. I can load this to Odin3 but as soon as I select Start the program crashes. Uggh. Is it possible to get the Verizon Software Repair tool?
Thanks!

NewYork2Cali said:
Thanks for the tip but no luck. I used 7-zip to create a tar file. I can load this to Odin3 but as soon as I select Start the program crashes. Uggh. Is it possible to get the Verizon Software Repair tool?
Thanks!
Click to expand...
Click to collapse
It shouldn't crash, how did you create it and which version of 7zip?

I used 7 zip 64 bit for Win 10.
I successfully created the tar file from the (MD5 file) located in the T817VVRU1AOG9_T817VVZW1AOG9_5.1.1_USA_Verizon_ALL.zip file. Odin3 crashes as soon as I select Start. Thanks!

NewYork2Cali said:
I used 7 zip 64 bit for Win 10.
I successfully created the tar file from the (MD5 file) located in the T817VVRU1AOG9_T817VVZW1AOG9_5.1.1_USA_Verizon_ALL.zip file. Odin3 crashes as soon as I select Start. Thanks!
Click to expand...
Click to collapse
You need to pull the recovery.img out of the md5 and tar that up not the md5 itself.

I believe I did that. I extracted the zip and pulled out this file
ALL_VZW_T817VVRU1AOG9_T817VVZW1AOG9_CL5500403_QB5862896_REV02_user_low_ship.tar.md5
I used 7 zip to create this file
ALL_VZW_T817VVRU1AOG9_T817VVZW1AOG9_CL5500403_QB5862896_REV02_user_low_ship.tar
I loaded the tar file to Odin and it crashed. Am I missing a step? Thanks!

NewYork2Cali said:
I believe I did that. I extracted the zip and pulled out this file
ALL_VZW_T817VVRU1AOG9_T817VVZW1AOG9_CL5500403_QB5862896_REV02_user_low_ship.tar.md5
I used 7 zip to create this file
ALL_VZW_T817VVRU1AOG9_T817VVZW1AOG9_CL5500403_QB5862896_REV02_user_low_ship.tar
I loaded the tar file to Odin and it crashed. Am I missing a step? Thanks!
Click to expand...
Click to collapse
You're not paying attention.
You need the file called RECOVERY.IMG that is inside the tar.md5.
Right click the md5, select open archive in 7zip.
Pull the recovery.img out then using 7-zip right click it, select create archive. Select TAR and STORE as the only options. Flash with Odin.

Will flashing this have any negative affects on Knox or void my warranty? Id like to try and reset my tablet back to a new setup beyond what a factory reset does.

Stock 4.4.4 suddenly stuck on boot logo and ODIN always fails

Hi ya!
I am a long time lurker and am always amazed that the collective knowledge here.
I've never spent much time with the inner workings of mobile phones, but am otherwise quite good with tech and very very persevering
My problem is a S3 LTE GT-I9305.
HISTORY (just FYI, as the phone is currently soft bricked):
It was working fine for ages. Delivered with stock 4.1.2 and last had stock 4.4.4 (I9305XXUFNL1_DBTFNL1) running (via OTA - Triangle Away worked well to hide the root). It was rooted (@ 4.1.2) using CF Autoroot and SuperSU worked fine. I am not sure if I ever installed Custom Recovery (if, then it was CWM).
Then about two months ago I started getting persistent error Messages about Media, Media Storage, Download Manager, Hangouts, etc having stopped.
After a lot of reading and troubleshooting I finally backed up my stuff and did a factory wipe. Everthing worked fine after that.
I never restored everything, so the phone and firmware was lightly loaded only, when ...
YESTERDAY:
Having not looked at the phone for a day or so, I surprisingly heard the Samsung shut down tone and went to have a look. What I saw (some 20-30 seconds later) was the white on black boot logo and it never went past that. Thinking that it might have been crunching on an OTA update or similar, I hooked it up to my charger and watched it for 3 hours (I swear, 3 hours). I then pulled the battery and it now (continues) to get stuck on the white on black boot logo.
NOW:
(1) Booting gets stuck at the white on black logo.
(2) I can start it in recovery but it is the Samsung stock recovery only. Please refer below for the error messages I get. I can't clear the cache and even the factory wipe does not work.
(3) I can start it in download mode but ODIN 1.85, 3.04 and 3.10.7 give me persistent FAIL results when trying to flash TWRP 3.0.2-1, 3.3.1-0 or CF-Auto-Root-m3-m3zh-gti9305.tar.md5. I have tried 2 otherwise good cables and all 3 USB2 ports available on my Win7 laptop.
(4) Kies 3 says 'not supported device'
I am at a loss right now. The water is way too deep for my knowledge level.
I have read more than 50 websites and forum posts (includung pretty similar ones, before deciding to write myself).
If someone could point me in the right direction ... eternal gratitude will be yours
What I have downloaded but not used yet (since ODIN is not able to write at the moment) is the I9305XXUFNL1 factory ROM containing:
AP_I9305XXUFNL1.tar.md5
BL_I9305XXUFNL1.tar.md5
CP_I9305XXUFNL1.tar.md5
CSC_I9305XXUFNL1.tar.md5
M3_EUR_OPEN.pit
Since I can't make any screenshots or provide log files ... here is more (and hopefully all) Information needed.
Top right of the screen in download mode:
ODIN MODE
PRODUCT NAME: GT-I9305
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SSTEM STATUS: Custom
Secure Download: Enabled
KNOX WARRANTY VOID: 1
AP SWREV: A3
ODIN 1.85 after attempting to flash TWRP 3.3.1-0 (using PDA button and only 'F. Reset Time' checked):
Setup Connection..
Initialization..
Get PIT for mapping..
Firmware update start..
recovery.img
NAND Write Start!!
Complete(Write) Operation failed.
All threads completed. (succeed 0 / failed 1)
Recovery mode upon start:
E:failed to mount /efs (No such file or directory)
E:failed to mount /system (No such file or directory)
# MANUAL MODE #
-- Applying Multi-CSC...
E:failed to mount /system (No such file or directory)
can't mount '/system' (No such file or directory)
E:failed to mount /cache (No such file or directory)
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/last_recovery
E:failed to mount /system (No such file or directory)
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/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_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (No such file or directory)
Recovery mode upon selection of 'wipe cache partition' or 'wipe data/factory reset':
Much of the above 'can't open+mount' error messages, but with additional mention of:
/cache/recovery/last_log
(Block device required)

@chinaman88 Never used stock on the i9305 but we still have two i9305's in not really daily but current use.
First, for all of our Samsung devices I use Odin v3.13.1; maybe you should also search the web (or XDA) for that version. You will experience some differences to your versions e.g. no PDA button. And you're correct, "Auto Reboot" must not be ticked because you need to immediately boot into TWRP after it has been flashed, otherwise TWRP won't stick.
Regarding TWRP: My own experiences is that no TWRP version above 3.0.2-1 works on the i9305. I always got flash errors with them. But 3.0.2-1 runs without any problems. My recommendation is to only use v3.0.2-1 and to flash that via Odin v3.13.1
If you succeeded with flashing of TWRP, then I'm happy to recommend the custom ROM that is still in use here.

@Oswald
I obtained Odin3 v3.13.1 and tried flashing both:
CWM_touch_6.0.4.7_i9305.tar
twrp-3.0.2-1-i9305.img.tar
Sadly the end result is the same ...
<ID:0/010> Odin engine v(ID:3.1301)..
<ID:0/010> File analysis..
<ID:0/010> Total Binary size: 6 M
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> NAND Write Start!!
<ID:0/010> SingleDownload.
<ID:0/010> recovery.img
<ID:0/010> FAIL!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
If I (with the help of the community) can't get my old I9305 running again (the SDS Sudden Death Syndrome has crossed my mind), then I will likely buy a used I9305 from someone and use that instead. But right now (unless it is really SDS in my case) I will still fight for my old phone ... thinking there has to be some way to get it working again. What is really strange to me is that I did nothing MYSELF to soft brick it - it happened all alone.
Thanks so far and I surely will take your offer to give me some advice on Custom ROMs (as more and more apps no longer support KitKat)!
I was thinking about Lineage 14.1 before all this happened. Is there anything better than that and, for Lineage 14.1, do you happen to remember which build was fully stable / most stable?

@chinaman88 First, happy new year to you. And I apologise for the delayed reponse but in your mention there was an error i.e. I didn't receive a notification.
As you have/had Kies installed you should have the driver for the i9305 installed on your PC but you may want to confirm. Additionally, I'm convinced you're aware that ODIN doesn't work if Kies is running in the background. I suggest to completely uninstall Kies prior to the launch of Odin (but do not uninstall the driver).
Are you able to flash the stock ROM via Odin?
And this is still my favourite ROM for the i9305, actually still runing daily: https://forum.xda-developers.com/ga...m-resurrection-remix-4-4-2-kitkat-v5-t2704828
This respective Q&A thread: https://forum.xda-developers.com/ga...resurrection-remix-4-4-2-kitkat-v5-1-t2950817
Search for my posts on both, and you'll find my current configuration including the custom kernel (a Boeffla mod).