Database Users

HELP : accidentally uninstalled TouchWiz

I accidentally uninstalled Touchwiz using Titanium Backup. Since I already use ADW.Launcher, I thought its not a big deal, until I did a hard reset.
Upon hard reset, my Galaxy S tries to install Touchwiz, which of course fails, and the darn phone just crashes and hangs. I managed to get it to boot up eventually after some trouble, but I'll prefer not to have to do this everytime I hard reset.
Can someone please please send me the TouchWiz apk and odex files so that I can put them back in the system directory ? I'm using stock Froyo 2.2 ( Build FROYO.DXJPA, Kernel 2.6.32.9 ). Please email them to [email protected], or tell me where I can download them.
I know this would cease to be a problem if I just flash a custom rom, and I would love to try that in future, but not now.
Thanks so much in advance.

Easy way would be to go to the Rom Kitchin build update zip with only the Touchwizz in it and flash it from SD card via CWM.
http://romkitchen.org/sgs/?s=generator
APK might be in Perkas file stash from this forum ..###
jje

JJEgan said:
Easy way would be to go to the Rom Kitchin build update zip with only the Touchwizz in it and flash it from SD card via CWM.
http://romkitchen.org/sgs/?s=generator
APK might be in Perkas file stash from this forum ..###
jje
Click to expand...
Click to collapse
Thanks, but I'm on 2.2, which means I have the 3e loader which does not allow me to setup update.zips which are unsigned. For this reason, i was also not able to get CWM installed. I know there's a way to downgrade the loader to 2e, but I'll rather not try that at this moment.

I agree with jje. The best and probably easiest way would be to flash 2e recovery. Chainfire has created a kernel for that purpose and as long as you can access download mode you should be fine.
Sent from my GT-I9000 using XDA Premium App

chriszzz said:
Thanks, but I'm on 2.2, which means I have the 3e loader which does not allow me to setup update.zips which are unsigned. For this reason, i was also not able to get CWM installed. I know there's a way to downgrade the loader to 2e, but I'll rather not try that at this moment.
Click to expand...
Click to collapse
Flash SpeedMOD kernel with Odin and you'll get CWM.

Hi JJEgan, anfearg, Intratech
Thanks for the advice so far. But would it be possible for me to just simply use a file manager to copy the TouchWiz apk and odex files to my system/app directory ? My phone is rooted, so I know it's possible as long as I can get those files. I'm just not sure if there's anything else that needs to be configured to get Android to use those files during setup. If this is workable, this would be the easiest route. Now I just need to get my hands on those files.
I know Odin can fix this, but I'll rather just stick to the current stock rom for now, and just add the missing 2 files.
Intratech said:
Flash SpeedMOD kernel with Odin and you'll get CWM.
Click to expand...
Click to collapse

I'm going to take a look at Odin and see if its not too risky to flash my i9000. I've flashed my old WinMo phones in the past, so flashing is not new to me. But I've yet to try it for Android. Maybe I'll give it a go.
chriszzz said:
Hi JJEgan, anfearg, Intratech
Thanks for the advice so far. But would it be possible for me to just simply use a file manager to copy the TouchWiz apk and odex files to my system/app directory ? My phone is rooted, so I know it's possible as long as I can get those files. I'm just not sure if there's anything else that needs to be configured to get Android to use those files during setup. If this is workable, this would be the easiest route. Now I just need to get my hands on those files.
I know Odin can fix this, but I'll rather just stick to the current stock rom for now, and just add the missing 2 files.
Click to expand...
Click to collapse

OK, so I spent a couple of hours googling and downloaded Odin, a couple of stock ROMs, PIT files and USB drivers. Fired up Odin, followed instructions, and I'm now back to 2.1 with the 2e loader. Sweet. Had a heart stopping moment when Odin said "FAILED" in red, so i just reflashed another ROM and it went through successfully.
Looks like I'm in the ROM flashing crowd now.
Quick question : some ROMs ( like the one I flashed successfully with Odin ) contains just a few tars - 1 each for CODE/PDA, CSC and MODEM/Phone.
Others ( like the one that Odin failed to flash ) just contains a bunch of directories with files that have bin, rfs, lfs extensions.
Why are there 2 different types of ROM packaging ? Is the first one ( with the tar files ) specific to Odin ? How do I flash the other type then ? With ClockWorkMod ?
chriszzz said:
I'm going to take a look at Odin and see if its not too risky to flash my i9000. I've flashed my old WinMo phones in the past, so flashing is not new to me. But I've yet to try it for Android. Maybe I'll give it a go.
Click to expand...
Click to collapse

chriszzz said:
OK, so I spent a couple of hours googling and downloaded Odin, a couple of stock ROMs, PIT files and USB drivers. Fired up Odin, followed instructions, and I'm now back to 2.1 with the 2e loader. Sweet. Had a heart stopping moment when Odin said "FAILED" in red, so i just reflashed another ROM and it went through successfully.
Looks like I'm in the ROM flashing crowd now.
Quick question : some ROMs ( like the one I flashed successfully with Odin ) contains just a few tars - 1 each for CODE/PDA, CSC and MODEM/Phone.
Others ( like the one that Odin failed to flash ) just contains a bunch of directories with files that have bin, rfs, lfs extensions.
Why are there 2 different types of ROM packaging ? Does each ROM come in both forms ? Can they be converted from 1 form to the other ?
Click to expand...
Click to collapse
the .tar types are to be flashed via odin only whereas the ones with the directories are to be flashed via CWM(2e recovery).... mix them up and you'll be in trouble... ;-)

You only needed to flash the recovery 2e zip file through Odin from the forum .
jje

chriszzz said:
<snipped>.. Others ( like the one that Odin failed to flash ) just contains a bunch of directories with files that have bin, rfs, lfs extensions.
Why are there 2 different types of ROM packaging ? Is the first one ( with the tar files ) specific to Odin ? How do I flash the other type then ? With ClockWorkMod ?
Click to expand...
Click to collapse
The single .tar file with .rfs, .bin, etc. is a high-level package. It's sort of a firmware update and can only be flashed on top of an existing firmware. That is, you don't tick re-partition in odin. The ones that come with 3 separate files for CSC, PDA and MODEM are either medium or low-level packages. I think, the low-level ones come with bootloaders. These can be flashed with re-partition ticked.

Thanks guys.
Today I learned how to flash using ODIN (flashed a European 2.1 ROM onto my international i9000 originally with Asian ROM, and downgraded my 3e loader to 2e).
Then I learned to use ClockWorkMod, which I used to flash Darky's ROM 9.5 ( nice ROM, although booting up seems to take an usually long time. Not sure why ). Finally, I almost had a heart attack, twice, when my phone refused to boot after flashing. Nothing a 3 button combo to download mode couldn't fix though.
Fun fun fun. Thanks all.

Stuck in download mode

New i337 user here.
Had it rooted yesterday, using the ./pwn method.
I realize now - I was on AMF3.
Once rooted - I was trying to get TWRP installed via goomanager.
Now I'm stuck in download mode. When ever I try to flash via odin to MDL or MDB, I get a FAIL! (Auth) error.
Is there anyway to fix this? Is there an AMF3 tar out there that's flashable via Odin?
Or am I completely screwed?

Sorry to say, you're screwed. There is no mf3 Odin file. And you can't put a custom recovery on mf3. That's what bricked you. You could try jtag. Talk to mobiletechvideos.com.

Fail.
Other alternative is to wait for an Odin flashable file, I assume?

str8shot said:
Fail.
Other alternative is to wait for an Odin flashable file, I assume?
Click to expand...
Click to collapse
Yes, but it could be a real long wait. I'm not even sure jtag would work. From what I've seen on xda it seems the mf3 is really causing problems. If you go that route talk to mobiltech and explain what happened as see if they have a fix before you send your phone in. Warranty might also work.

has anyone tried kies emergency recovery yet with this issue? i'm curious.

xBeerdroiDx said:
has anyone tried kies emergency recovery yet with this issue? i'm curious.
Click to expand...
Click to collapse
I tried that, but Kies doesn't even register the phone as connected.
I'm really bumming.

Even if there was a stock MF3 boot/recovery flashable via odin, that would probably work. All the other partitions should be fine...

Huh
str8shot said:
Even if there was a stock MF3 boot/recovery flashable via odin, that would probably work. All the other partitions should be fine...
Click to expand...
Click to collapse
Man, I'm feeling your pain. I was thinking along the same lines. Some how you borked the recovery and if you could get that back on you might be ok. You might want to check with Aou or AdamOutler. They're wizzes at this type of stuff.
Edit, Just found this. http://forum.xda-developers.com/showthread.php?p=44431964

New i337 user here.
Had it rooted yesterday, using the ./pwn method.
I realize now - I was on AMF3.
Once rooted - I was trying to get TWRP installed via goomanager.
Now I'm stuck in download mode. When ever I try to flash via odin to MDL or MDB, I get a FAIL! (Auth) error.
Is there anyway to fix this? Is there an AMF3 tar out there that's flashable via Odin?
Or am I completely screwed?
Click to expand...
Click to collapse
Call Samsung tell them your phone not working it is not turning on and send for repair [ PS free warranty for yr ] best they can do is tell you no after looking phone. Shipping is free as well.
I have bricked my s3 by flashing different Rom and they fixed it for me.
Also bricked my s4 AT&T same way as u did they fixed it for me lol
Most of time they be nice and fix it for you.

str8shot said:
Even if there was a stock MF3 boot/recovery flashable via odin, that would probably work. All the other partitions should be fine...
Click to expand...
Click to collapse
jd1639 said:
Man, I'm feeling your pain. I was thinking along the same lines. Some how you borked the recovery and if you could get that back on you might be ok. You might want to check with Aou or AdamOutler. They're wizzes at this type of stuff.
Click to expand...
Click to collapse
The closest we got was this:
http://forum.xda-developers.com/showthread.php?t=2374221 (see end of post #6 for tarball)
We managed to build an odin-flashable tarball with the MF3 recovery. If it worked, it would save your device.
Problem is, the only copies of recovery.img that we can get right now are refused by the phone because they are not signed. If we got a signed version, we'd be golden. Unfortunately we probably won't see this until Kies has MF3.

Aou said:
The closest we got was this:
http://forum.xda-developers.com/showthread.php?t=2374221 (see end of post #6 for tarball)
We managed to build an odin-flashable tarball with the MF3 recovery. If it worked, it would save your device.
Problem is, the only copies of recovery.img that we can get right now are refused by the phone because they are not signed. If we got a signed version, we'd be golden. Unfortunately we probably won't see this until Kies has MF3.
Click to expand...
Click to collapse
It's a miracle!
I read through your thread; and for giggle - instead of letting it fail to boot and fall back to dl mode, I manually entered dl mode, then hit vol down to cancel and reboot.
It booted normally and all appears well...guess I have to delete goo for now. I'm missing CM10.1, though.
Thanks! And PHWEW! Thought I was screwed!

str8shot said:
It's a miracle!
I read through your thread; and for giggle - instead of letting it fail to boot and fall back to dl mode, I manually entered dl mode, then hit vol down to cancel and reboot.
It booted normally and all appears well...guess I have to delete goo for now. I'm missing CM10.1, though.
Thanks! And PHWEW! Thought I was screwed!
Click to expand...
Click to collapse
Congrats! Yes, you'll be without custom ROMs until we find a new exploit similar to Loki, or fully unlocked bootloaders.
I'm assuming you don't have a recovery at all now, right? Might want to check that out while you have everyone's attention here.
If it's borked, you might be able to manually use "dd" to flash the stock MF3 recovery back onto your device... You would use something like:
Code:
su
dd if=/sdcard/mf3-recovery.bin of=/dev/block/mmcblk0p21
For the love of God, don't get that partition number wrong (p21) - check your spelling before pressing Enter. There is some risk in this method, so check out any available options you might have in goo manager to restore a backup or something first.

Aou said:
Congrats! Yes, you'll be without custom ROMs until we find a new exploit similar to Loki, or fully unlocked bootloaders.
I'm assuming you don't have a recovery at all now, right? Might want to check that out while you have everyone's attention here.
If it's borked, you might be able to manually use "dd" to flash the stock MF3 recovery back onto your device... You would use something like:
Code:
su
dd if=/sdcard/mf3-recovery.bin of=/dev/block/mmcblk0p21
For the love of God, don't get that partition number wrong (p21) - check your spelling before pressing Enter. There is some risk in this method, so check out any available options you might have in goo manager to restore a backup or something first.
Click to expand...
Click to collapse
Using the unsigned recovery from the other post?

str8shot said:
Using the unsigned recovery from the other post?
Click to expand...
Click to collapse
As a last resort, yes. It came from @joeybear23 who dumped it using my instructions in post #2 of that same thread, or you could extract it out of the tarball if you wish. The image itself can be downloaded in the first part of post #6. Might need to rename it or otherwise change the filename referenced in the "dd" command.
Again, this is only if your recovery is currently borked and unusable.

I fixed mine using a dif file.
I found a file called MF3_BTL_FIX.tar.md5. Flashed it in odin and it fixed my bootloader issues. Everything back to normal. Found it used for a dif issue elsewhere on XDA. I thought I was screwed for the foreseeable future.

str8shot said:
It's a miracle!
I read through your thread; and for giggle - instead of letting it fail to boot and fall back to dl mode, I manually entered dl mode, then hit vol down to cancel and reboot.
It booted normally and all appears well...guess I have to delete goo for now. I'm missing CM10.1, though.
Thanks! And PHWEW! Thought I was screwed!
Click to expand...
Click to collapse
Just wanted to give this a second thumbs up. Seems soooo stupid but it works, lol. Thanks!

lol
after hours of trying every thing else thanx. it worked

Looking for stock recovery for i9515

Hello,
I am looking for the stock recovery for the i9515.
Or can I just use the i9505 stock recovery for it?
Thanks in advance!

nonoway2 said:
Hello,
I am looking for the stock recovery for the i9515.
Or can I just use the i9505 stock recovery for it?
Thanks in advance!
Click to expand...
Click to collapse
I would only ever use the suggested recovery options, NEVER use a different model in your phone.
http://www.sammobile.com/firmwares/
Click that link, type in the "Find device" search box and input GT-i9515 and you actually get a lot of stock roms. Because it's from Samsung it is all official. You will need to find Odin 3.09 and a helpful guide to aid in the procedure, all current information will be lost on your device and will bring it back to stock (except perhaps the flash counter, which can be reset with Triangle Away)
As always, do as much research as you can before going ahead with any potentially dangerous changes!
Good luck

irscotty said:
I would only ever use the suggested recovery options, NEVER use a different model in your phone.
Click that link, type in the "Find device" search box and input GT-i9515 and you actually get a lot of stock roms. Because it's from Samsung it is all official. You will need to find Odin 3.09 and a helpful guide to aid in the procedure, all current information will be lost on your device and will bring it back to stock (except perhaps the flash counter, which can be reset with Triangle Away)
As always, do as much research as you can before going ahead with any potentially dangerous changes!
Good luck
Click to expand...
Click to collapse
I actually did use a CWM recovery option that wasn't specifically for the i9515 but for the 9500 or the 9505. I do not remember which one of both of these I did use though and I do not want to take that risk again.
So this will also reset my ROM and wipe all data? That is not what I am looking for unfortunately. I am looking for solely the stock recovery menu. Everything else should stay as it is. Isn't that possible?

nonoway2 said:
I actually did use a CWM recovery option that wasn't specifically for the i9515 but for the 9500 or the 9505. I do not remember which one of both of these I did use though and I do not want to take that risk again.
So this will also reset my ROM and wipe all data? That is not what I am looking for unfortunately. I am looking for solely the stock recovery menu. Everything else should stay as it is. Isn't that possible?
Click to expand...
Click to collapse
As far as I'm aware the only solution to remove the Custom Recoveries is to flash stock firmware via Odin, I could be wrong but I've never heard of it.
Sorry I can't help further, best of luck with your predicament.

bump

nonoway2 said:
I actually did use a CWM recovery option that wasn't specifically for the i9515 but for the 9500 or the 9505. I do not remember which one of both of these I did use though and I do not want to take that risk again.
So this will also reset my ROM and wipe all data? That is not what I am looking for unfortunately. I am looking for solely the stock recovery menu. Everything else should stay as it is. Isn't that possible?
Click to expand...
Click to collapse
No it will not wipe your device. Just pick the stock rom that is for your device.

nonoway2 said:
bump
Click to expand...
Click to collapse
+1 with lennyz1988
Just flash the stock rom
"If someone helps, never forget to hit thanks ? "

I can't flash the stock rom because I want to keep a modified rom and yet still have the stock recovery.
If you care why: Cerberus anti-theft rom.
So I need a way to keep everything but the recovery. That one has to go back to stock so no thiefs suspect custom roms when doing a hard reset and seeing CWM Recovery.

Bump

Bump,
no one got an idea?

Well then just download the official firmware and extract recovery.img. Then flash it using terminal or heimdall.

Lennyz1988 said:
Well then just download the official firmware and extract recovery.img. Then flash it using terminal or heimdall.
Click to expand...
Click to collapse
Oh I did not know files inside the firmware files were seperated.
Why Terminal or Heimdall and not Odin?
Edit: Can't find a file for recovery in firmware from here: www.sammobile.com/firmwares/

nonoway2 said:
Oh I did not know files inside the firmware files were seperated.
Why Terminal or Heimdall and not Odin?
Edit: Can't find a file for recovery in firmware from here: www.sammobile.com/firmwares/
Click to expand...
Click to collapse
You'll have to get the whole damn firmware.
"If someone helps, never forget to hit thanks ? "

DeepankarS said:
You'll have to get the whole damn firmware.
"If someone helps, never forget to hit thanks ? "
Click to expand...
Click to collapse
I gotta be really stupid or I am overseeing something.
I got the whole 1,6gb firmware.
It has this file in it: "I9515XXU1ANI2_I9515VFG1ANI1_I9515XXU1ANI2_HOME.tar.md5" I tried changing the .md5 to .zip but it only showed me a few files inside it then that did not include a recovery file. Emulating the .md5 file with daemon tools didn't work either.
I don't know how to find the recovery file in it.

Bump

nonoway2 said:
I gotta be really stupid or I am overseeing something.
I got the whole 1,6gb firmware.
It has this file in it: "I9515XXU1ANI2_I9515VFG1ANI1_I9515XXU1ANI2_HOME.tar.md5" I tried changing the .md5 to .zip but it only showed me a few files inside it then that did not include a recovery file. Emulating the .md5 file with daemon tools didn't work either.
I don't know how to find the recovery file in it.
Click to expand...
Click to collapse
Hi
Rename your .md5 firmware in .tar, then open it with winrar, and extract the kernel called "boot.img".
Then flash it with "mobile odin" in your phone.

Hey,
thanks for your help, but there is also a recovery.img. I guess I will flash that one and not the boot.img one if I want to have the stock Recovery, shouldn't I?

nonoway2 said:
Hey,
thanks for your help, but there is also a recovery.img. I guess I will flash that one and not the boot.img one if I want to have the stock Recovery, shouldn't I?
Click to expand...
Click to collapse
correct.

Alright then, wish me luck, I will try it this evening.
Edit: already did it quickly. Worked perfect! Now I have the stock Recovery back and just the Cerberus ROM installed. Perfect. May these thieves come if they dare... They won't realize at all that there is something integrated in this ROM.
I used RashR by the way.

nonoway2 said:
Alright then, wish me luck, I will try it this evening.
Edit: already did it quickly. Worked perfect! Now I have the stock Recovery back and just the Cerberus ROM installed. Perfect. May these thieves come if they dare... They won't realize at all that there is something integrated in this ROM.
I used RashR by the way.
Click to expand...
Click to collapse
Also just for knowledge..boot.img has the kernel
"If someone helps, never forget to hit thanks ? "

Some Help!

I odined the eng boot.img without thinking about backing up first and now stuck on tmobile screen during boot up. Is it possible to flash a stock boot to get back in or reflash whole software without it wiping all of my data?

xRogueShadow said:
I odined the eng boot.img without thinking about backing up first and now stuck on tmobile screen during boot up. Is it possible to flash a stock boot to get back in or reflash whole software without it wiping all of my data?
Click to expand...
Click to collapse
Try going into the stock recovery and wiping your data. It should boot but it will also wipe your phone. It sounds like you need to use Odin to flash the stock firmware. It will also wipe your data if you do that.
Sent from my SM-G930P using XDA-Developers mobile app

xRogueShadow said:
I odined the eng boot.img without thinking about backing up first and now stuck on tmobile screen during boot up. Is it possible to flash a stock boot to get back in or reflash whole software without it wiping all of my data?
Click to expand...
Click to collapse
Ehhhh... you might be able to. What firmware were you using before?

Binary100100 said:
Ehhhh... you might be able to. What firmware were you using before?
Click to expand...
Click to collapse
Original software. APB6 I think its called. Also if I do end up having to wiping(which I hope I wont need to) should I update to latest firmware?

Download your original firmware from Sammobile.
Then you can try to extract the AP file. Then extract the boot.img file from that.
Then you can try this script to convert the boot.img to an md5 file: http://forum.xda-developers.com/showthread.php?t=2446269
THEN try to flash it via odin.
Here's the boot.img from the PD8 file converted to a tar.md5 file. Might work. Guess you don't have anything to lose.
(Unzip it first obviously)

Binary100100 said:
Download your original firmware from Sammobile.
Then you can try to extract the AP file. Then extract the boot.img file from that.
Then you can try this script to convert the boot.img to an md5 file: http://forum.xda-developers.com/showthread.php?t=2446269
THEN try to flash it via odin.
Here's the boot.img from the PD8 file converted to a tar.md5 file. Might work. Guess you don't have anything to lose.
(Unzip it first obviously)
Click to expand...
Click to collapse
Actually tried that earlier and it failed. Tried yours just to see but also said failed.

xRogueShadow said:
Actually tried that earlier and it failed. Tried yours just to see but also said failed.
Click to expand...
Click to collapse
Expected as much. To to update your firmware. Seriously. Why not? PD8 is rootable and you won't be able to update after you root.

Binary100100 said:
Expected as much. To to update your firmware. Seriously. Why not? PD8 is rootable and you won't be able to update after you root.
Click to expand...
Click to collapse
Sounds like a plan. Thank you for the help

Paying to get this fixed

My s7 edge got stuck at boot screen so i reflashed stock rom and rerooted then restored the backup i had, it said fail because of low memory while restoring the system and now when i try to reflash the stock rom on odin it says model dismatch fail.
If someone could help me fix this I'm willing to pay something decent, but not a whole lot lol

Re-download the stock rom and flash it

Meboyzram said:
Re-download the stock rom and flash it
Click to expand...
Click to collapse
i did that lol thats when it says "model dismatch fail"

Do you have custom recovery?

Do you have a custom recovery?
Do you have the right and the newest Odin Version?
Did you try it with another transfercable or USB-Port?
Do you have the newest samsung drivers?
Did you have any Odin problems like this before?
My suggestion:
Just do a full wipe on your phone. Downlad the newest Odin Version. Get your device into download mode (maybe try different transfercables or USB Ports and the newest samsung drivers) and see if it works now.
If yes, flash the right Bootloader and Modem for your device and then flash the rom you wanted to flash.
If this didnt work, (and you have a custom recovery) try to reinstall the rom without any backups via the recovery at first and check afterwards, if the device is now recognized by Odin.
Good luck

JustAnotherAndroid said:
My s7 edge got stuck at boot screen so i reflashed stock rom and rerooted then restored the backup i had, it said fail because of low memory while restoring the system and now when i try to reflash the stock rom on odin it says model dismatch fail.
If someone could help me fix this I'm willing to pay something decent, but not a whole lot lol
Click to expand...
Click to collapse
I guess you still have twrp installed.
1. Step: go to TWRP and wipe everything except your SD-Card
2. Step: enter download mode on your device and then plug your usb in (maybe try a different usb-port or even another computer, or another usb cable)
3. Step:Flash the newest bootloader & modem in one step.
4. Step: Enter TWRP again and flash the firmware.zip via the installation process

I dont have TWRP, but i got it fixed, somehow my roomate got it, thanks anyways guys

So all he got was my phone to turn on, im still having this model dismatch fail issue..

Maybe You're trying to flash wrong firmware? What model did You buy?(check box) and what firmware did You download?
If nothing works then download 7zip. And remove all files from that tar.md5 file and leave system.img only. And then try reflashing it.
This way no matter what device You connect it should force flash this image file. Although it might be dangerous (a tiny little bit) so first make sure that You have proper firmware for Your model.

ProtoDeVNan0 said:
Maybe You're trying to flash wrong firmware? What model did You buy?(check box) and what firmware did You download?
If nothing works then download 7zip. And remove all files from that tar.md5 file and leave system.img only. And then try reflashing it.
This way no matter what device You connect it should force flash this image file. Although it might be dangerous (a tiny little bit) so first make sure that You have proper firmware for Your model.
Click to expand...
Click to collapse
Yes, I've used these files multiple times before i did what i did, ill give that a try, if it works, i owe you.

If system.img by itself will flash successfully and Your phone won't boot then add slowly more files to that tar file (boot.img, recovery.img etc)
You could also try looking for a pit file for Your phone and then flash it with it. Pit file usually fixes most problems even broken partitions.
And make sure that You put that tar file in AP/PDA.
If nothing above works then send me screenshots of ODIN and the file that You're trying to flash. Maybe I'll notice something. But I hope You'll fix it

JustAnotherAndroid said:
Yes, I've used these files multiple times before i did what i did, ill give that a try, if it works, i owe you.
Click to expand...
Click to collapse
So I tried, and i get some invalid file error
These are the files that are in the AP one
https://gyazo.com/a72785631ad62d412a8c40eb464d3126

I found out my problem, i was still uing the modified version of odin that i used to root my phone