Hello, I have been trying to flash for 2 days now but still couldn't get it working.
Initially, my I9305 is running on stock without root. I wanted to root it and then install recovery and ROM.
And so I prepare the necessary files, and start to flash.
I used CF-Auto-Root to root my device first, then got Resurrection ROM and Gapps to flash.
Then I started to get some issue, as it always fail. Error message like no file context and so on. So I read online resources, and found out that I had a older version of TWRP installed which may cause the install.
I then tried to upgrade TWRP but it doesn't allow me to. No choice, I had to flash philz touch, and I did.
I then tried to flash Resurrection again, boot up, and it keep giving me bootloop. After which I downloaded nameless ROM, and CM11 but same issue.
Yesterday night, I downloaded the stock firmware to try. I flashed it, and it is successful based on ODIN, but it still won't boot up.
I just tried it again and it stuck on the Samsung logo screen.
Can anyone tell me what else to do? What I have to do?
This is the stock firmware that I have downloaded and flash - I9305XXUENH1_I9305EVRENH1_EVR.
Let me know what other information I have to provide.
Thanks!
Here's the Download mode information.
Custom binary count: 9 counts
Current binary: samsung offical
System status: custom
Knox void: 1
RP SWREV: A2
Update: 16/1
I just tried to go into my recovery mode and apparently, it has been changed back to stock recovery which I assume is because I have flashed the stock firmware.
I am trying it yet again after wiping in stock recovery, to flash the stock firmware again now.
P.S: I have posted it in http://forum.xda-developers.com/galaxy-s3/help-i9305/qa-samsung-galaxy-s3-lte-roms-kernels-t2999494 but no reply. So trying my luck here.
Ok, this is funny. I waited for 2-3 days before posting here for help. And it doesn't work for all those days.
Now that I just posted, it finally worked. I am getting into the setup screen.
Anyway, for those people who may have the same issue as me in the future, try to wipe everything after flash to stock firmware. then flash stock firmware again.
After flash
It's a good call,as per your last post,to wipe data and factory reset after a flash and even a second install.Need to give time for changes to occur.Don' go too fast.HTH.
Hello!, my device is GT-i9305 and i seem to have a problem of some sort. (I have had three devices before this and installed lots of custom roms, but never have i encountered something like this)
Whenever i try to install a custom rom (omnirom/pacrom/cyanegenmod) i get stuck in the splash/boot screen animation, but when i flash back to stock rom (4.4.4) using odin it loads up and everything works like its supposed to.
I have tried using TWRP and CWM-recovery. (With CWM i can get omnirom to boot, but i wont be able to dial or use mobile-data etc. (Seems like my efs files or something are missing) and i also get some error message about androidcore or somethinglikethat.
Most common fixes for this in the forums are to wipe dalvic and cache after installing. Which i have done + some other odd "fixes" i found.
I am really baffled. Whats wrong?
Did you flash TWRP 2.8.7.0? That recovery is buggy and does not work. You have to stay on 2.8.5.0 for the moment. There are people already trying to fix the faulty recovery. CWM won't get any updates anymore. It does still work but you might come across some ROMs which won't work with CWM.
To start all over again with no issues: flash 4.4.4 Stock, install TWRP 2.8.5.0 and you're good to go
Thankyouthankyouthankyou
That totaly fixed it! Thank you sooooo much, no more sleepless nights because of this.
Hello XDA Developers!
I'm trying to install a custom rom om my i9305 bought in Denmark.
So far I have gotten the TWRP and Cyanogenmod recoveries to work, and through those I have successfully installed the two last versions of CM11 nightlies for the i9305 and the two last versions of AOSB 4.4.4 for the i9305. Yet I can't get any of them to boot past their respective logos (the phone moves nicely past the Samsung Galaxy S3 logo).
I have tried full system++ wipes, multiple Dalvik cache and cache wipes and Factory resets etc, but whatever I do my phone never gets past the CM / AOSB logo. I have waited for 20 minutes once for CM11 and once for AOSB, and 5+ minutes multiple times on both. Nothing changes.
Is there anyone out there with a 9305 that successfully installs custom ROM's that can help? Any help is greatly appreciated as I'm currently without a working phone
PS: Sorry if this is already an answered question. I googled extensively and looked at all the suggested threads before clicking "Submit" and couldn't find an answer.
Technical info:
Heimdall (latest unofficial from developer to get it working with OS X El Capitan)
Android Studio 1.4 with Platform Tools installed today
TWRP 2.8.7.0
Two latest nightlies from the official Cyanogenmod page attempted (I'm not yet allowed to post links), through TWRP as well as the recovery
Two latest versions from the AOSB website (still not allowed to post links, sorry)
MaHo_66 to the rescue
I was able to bring my phone back using the 9305N ROM posted on /galaxy-s3/development-i9305/rom-samsung-stock-4-4-4-rom-collection-t3124027
Still curious why it didn't work with the others, but at least now I have a phone again.
your issue is TWRP 2.8.7.0
several users, including me, had issues with the updated version as it's messes up with partitions etc. You experienced what we were having issues with. After installing the new recovery the installed ROM won't boot up anymore. The only way to fix this was to install stock ROM or a custom ROM based on stock.
I recommend to stay on TWRP 2.8.5.0 till the new version is fixed. Some users are working on a fixed updated TWRP recovery.
if you have made a nandroid backup of any previous rom that boots then try that, if that also fails to load then you need to install stock firmware again and start from the beginning again, stock firmwares can be found on samfirmware,
i have been flashing phones for several years, yet the other day i faced the exact same issue, not sure what caused it, it was also for the same device, stock firmware fixed all issues.
good luck
maultasche said:
your issue is TWRP 2.8.7.0
several users, including me, had issues with the updated version as it's messes up with partitions etc. You experienced what we were having issues with. After installing the new recovery the installed ROM won't boot up anymore. The only way to fix this was to install stock ROM or a custom ROM based on stock.
I recommend to stay on TWRP 2.8.5.0 till the new version is fixed. Some users are working on a fixed updated TWRP recovery.
Click to expand...
Click to collapse
Thanks for the reply! I also tried with the CyanogenMod Recovery, which ended the same way.
But installing a custom ROM based on stock worked, and is both way faster and pulls way less battery than the original ROM. So it all worked out in the end (until I can't resist the temptation and try to do it all again).
kamikaze702k said:
if you have made a nandroid backup of any previous rom that boots then try that, if that also fails to load then you need to install stock firmware again and start from the beginning again, stock firmwares can be found on samfirmware,
i have been flashing phones for several years, yet the other day i faced the exact same issue, not sure what caused it, it was also for the same device, stock firmware fixed all issues.
good luck
Click to expand...
Click to collapse
Custom ROM based on stock worked, thanks!
Were you able to install any custom ROMs after fixing your issue, or are you also "stuck" on a stock based ROM?
elysium7 said:
Custom ROM based on stock worked, thanks!
Were you able to install any custom ROMs after fixing your issue, or are you also "stuck" on a stock based ROM?
Click to expand...
Click to collapse
I flashed carbon rom 4.4.4, twrp recovery is user friendly but on this particular device the recovery was cwm, I don't like stock based roms
kamikaze702k said:
I flashed carbon rom 4.4.4, twrp recovery is user friendly but on this particular device the recovery was cwm, I don't like stock based roms
Click to expand...
Click to collapse
Nice, thanks! I'll try cwm next time then
Hello guardians of the Android Phones. I ran into a major issue while updating from 5.1.1 custom ROM to 6.0.1 that I found on this thread : http://forum.xda-developers.com/tmo...20t-android-6-0-1-marshmallow-update-t3356838
Steps I took:
1) Upgraded TWRP to 3.0.2.0 (3.0.2.1 doesn't work properly on my device. it flashes the TWRP 3 logo and then goes black) ... So I ended up re-installing TWRP 2.8.7.2 and then flashed TWRP 3.0.2.0
2) Copied the ROMS of choice to the SDCARD
3) Using Odin 3.10.7 I flashed using Twisted Sixx Custom ROM (which didn't work correctly due to the bootloader not being Marshmallow 6.0.1 compatible) from my understanding of what i've read through these threads.
4) Flashed the AP using G920TUVU3EPD1_G920TTMB3EPD1_G920TUVU3EPD1_HOME.tar.md5
Now i'm 100% locked out from downgrading Stock or Custom ROMS. TWRP can no longer be installed.
Having a feeling I used a Bear Trap ROM.
What do I do? Feeling like throwing this out the window. *sigh*.
Thanks ahead of time... anything to point me in the right direction would be greatly appreciated.
I am not a dev... but I tried smartswitch, perhaps it can help you. Hopefully you didn't do factory reset.
Try that and then if it doesn't work, again, wait for the experts.
What is SmartSwitch? Do you have a URL or THREAD with information and download links?
Thanks for the tip.
britchel said:
I am not a dev... but I tried smartswitch, perhaps it can help you. Hopefully you didn't do factory reset.
Try that and then if it doesn't work, again, wait for the experts.
Click to expand...
Click to collapse
I did an Odin flash of EPF1 and didn't lose the ability to flash recovery. I have not yet tried downgrading. I would take a deep breath, drink a beer or two, and go back through things step by step. At this point I would suggest using Odin to flash a complete image, perhaps of a different version, and go from there.
ninjadroids said:
What is SmartSwitch? Do you have a URL or THREAD with information and download links?
Thanks for the tip.
Click to expand...
Click to collapse
http://www.samsung.com/us/smart-switch/assets/downloads/Smart_Switch-PC_setup.exe
Hey can u reboot to recovery and to download mode?
You need to be in download mode to use smart-switch
Here's another tread alike to yours....
http://forum.xda-developers.com/tmo...rick-wont-boot-successful-odin-flash-t3435751
Smiles on the beer or two!
Are you using the G920T also? Which image did you Odin flash with? Do you have the direct link? I do like your idea of flashing with a different 6.x image variant as opposed to downgrading.
socal87 said:
I did an Odin flash of EPF1 and didn't lose the ability to flash recovery. I have not yet tried downgrading. I would take a deep breath, drink a beer or two, and go back through things step by step. At this point I would suggest using Odin to flash a complete image, perhaps of a different version, and go from there.
Click to expand...
Click to collapse
Yes I can reboot into recovery and to download mode. Thank you for the link.
britchel said:
http://www.samsung.com/us/smart-switch/assets/downloads/Smart_Switch-PC_setup.exe
Hey can u reboot to recovery and to download mode?
You need to be in download mode to use smart-switch
Here's another tread alike to yours....
http://forum.xda-developers.com/tmo...rick-wont-boot-successful-odin-flash-t3435751
Click to expand...
Click to collapse
ninjadroids said:
Smiles on the beer or two!
Are you using the G920T also? Which image did you Odin flash with? Do you have the direct link? I do like your idea of flashing with a different 6.x image variant as opposed to downgrading.
Click to expand...
Click to collapse
I don't unfortunately - Google is your friend. Some firmwares that come to mind are DOJ7, DOJC, and COF6.
But first: Is your bootloader locked? If you have not yet unlocked it, that may be a problem. I unlocked mine as soon as I got my phone (and yes I'm on a G920T). A locked bootloader may prevent downgrading although it should not prevent a rescue Odin of the same or newer firmware.
Yes it's locked.
Is there a way to unlock it while maintaining my current image?
All those firmware are 5.x
I'm stuck on unlocked Marshmallow 6.0.1
And according to Smart Switch. I'm one version down from latest with it prompting to upgrade.
I'm going to hold off on that for the moment...
If you flashed edp1, you are far from latest.
Lemme know if i am wrong at anything
If you can access download and recovery, that means the phone is in a bootloop when booting up..
Since you flashed the edp1 firmware, your bootloader must have been updated so now you can only use mm roms.
As for recovery, is it stock or twrp?
Also when in download modex whats your system status - stock or custom?
Well if EDP1 is far from latest, then that is great news. I can boot into my firmware. It's for sure stock as far as I can tell.
Download mode output:
RED: ODIN MODE
PRODUCT NAME: SM-G920T
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
FAP LOCK: OFF
BLUE: Secure Download: Enabled
Knox Warranty Void: 1 (I tripped it when rooting it in 5.x)
AP SWREV: B:3 K:2 S:2
It won't let me get into TWRP after flashing it... when I try it says the following:
RED: "RECOVERY IS NOT SEANDROID ENFORCING"
It doesn't matter which version of TWRP I attempt to flash with.
Thanks!
danveer said:
If you flashed edp1, you are far from latest.
Lemme know if i am wrong at anything
If you can access download and recovery, that means the phone is in a bootloop when booting up..
Since you flashed the edp1 firmware, your bootloader must have been updated so now you can only use mm roms.
As for recovery, is it stock or twrp?
Also when in download modex whats your system status - stock or custom?
Click to expand...
Click to collapse
Did you flashed root or anything after you tried to flash recovery via odin?
Also when you flashed edp1, phone still didnt boot?
Edp1 is about the march or april update i think
The next main update is epf1 because it restricts going back futher
Then there came a update 5 days ago.. just a security update... havent flashed that coz i am rooted..
Anyways lets concentrate on edp1
Since its a mm rom, going back to 5.1 roms means a bootloop, so ill suggest not doing that
Also after flashing the mm rom, if you flash anything over it, you wont be able to boot a system because a new dm verity check mm has introduced.. to bypass it, you either need to flash a mm root file or a kernel that can disable the check.
I was stuck at the same thing since i Flashed recovery and that failed the checks so was getting bootloops..
I was able to go in recovery and download mode but not boot up..
Since you have a custom status, it can be a reason for bootloops
http://forum.xda-developers.com/gal...y-official-twrp-galaxy-s6-edge-t3354508/page8
The phone boots. I just cannot get root. I guess I don't understand the terminology regarding "bootloops" or "MM" ... I attempted a APK root... which failed. And still using my previous kernel unless flashing the custom ROM overwrote that.
So I can login to the phone and connect it to USB and sideload APK files, no problem. I just cannot TWRP flash properly and enter it using the UP recovery mode. And when I tried flashing other ROMS in Download recovery mode either ODIN crashes or it gives me a NAND WRITE error.
Which root and / or kernel files would you suggest to me to flash in ODIN to break this protection that's preventing a full root on this image? Or would it be preferable in my situation to find a different ROM and resolving the ODIN crash problem to achieve a full 6.x marshmallow root?
Thanks again! Greatly appreciated Sir.
danveer said:
Did you flashed root or anything after you tried to flash recovery via odin?
Also when you flashed edp1, phone still didnt boot?
Edp1 is about the march or april update i think
The next main update is epf1 because it restricts going back futher
Then there came a update 5 days ago.. just a security update... havent flashed that coz i am rooted..
Anyways lets concentrate on edp1
Since its a mm rom, going back to 5.1 roms means a bootloop, so ill suggest not doing that
Also after flashing the mm rom, if you flash anything over it, you wont be able to boot a system because a new dm verity check mm has introduced.. to bypass it, you either need to flash a mm root file or a kernel that can disable the check.
I was stuck at the same thing since i Flashed recovery and that failed the checks so was getting bootloops..
I was able to go in recovery and download mode but not boot up..
Since you have a custom status, it can be a reason for bootloops
http://forum.xda-developers.com/gal...y-official-twrp-galaxy-s6-edge-t3354508/page8
Click to expand...
Click to collapse
ninjadroids said:
The phone boots. I just cannot get root. I guess I don't understand the terminology regarding "bootloops" or "MM" ... I attempted a APK root... which failed. And still using my previous kernel unless flashing the custom ROM overwrote that.
So I can login to the phone and connect it to USB and sideload APK files, no problem. I just cannot TWRP flash properly and enter it using the UP recovery mode. And when I tried flashing other ROMS in Download recovery mode either ODIN crashes or it gives me a NAND WRITE error.
Which root and / or kernel files would you suggest to me to flash in ODIN to break this protection that's preventing a full root on this image? Or would it be preferable in my situation to find a different ROM and resolving the ODIN crash problem to achieve a full 6.x marshmallow root?
Thanks again! Greatly appreciated Sir.
Click to expand...
Click to collapse
Which odin are you using?
Try 3.10.7 because using older odin on mm gives that nand write error...
That could explain a lot of things
I'm using 3.10.7 latest.
danveer said:
Which odin are you using?
Try 3.10.7 because using older odin on mm gives that nand write error...
That could explain a lot of things
Click to expand...
Click to collapse
http://forum.xda-developers.com/che...rite-start-fail-odin-soluction-t2851096/page5
Try this thread..
It has solutions when nand write fails...
Also trying a different verion pf odin might work like 3.10.6 or another maybe
ninjadroids said:
Yes it's locked.
Is there a way to unlock it while maintaining my current image?
All those firmware are 5.x
I'm stuck on unlocked Marshmallow 6.0.1
And according to Smart Switch. I'm one version down from latest with it prompting to upgrade.
I'm going to hold off on that for the moment...
Click to expand...
Click to collapse
EPD1 and EPF1 are 6.0.1 Marshmallow.
@ninjadroids:
Take this as you will but reading back through this thread gives me the impression that you lack the necessary know-how to customize your phone. I highly suggest you leave it stock for the time being until you know EXACTLY what you are doing.
My reasons for saying this:
-In your first post you state that "using Odin 3.10.7 I flashed using Twisted Sixx Custom ROM". To my knowledge there are NO custom ROMs designed to be flashed via Odin. They are in .zip files, to be installed via recovery ONLY.
-This is actually my mistake - the G920T bootloader does not have a lock function; flashing a custom recovery will simply trip the e-fuse and render it Knox 0x1 warranty void.
-You are not familiar with what Odin images are for the G920T, or what version they are. You should NEVER flash ANYTHING via Odin unless you are absolutely sure it is intended for your specific device.
-In the 9th post you state your bootloader is unlocked (again I apologize for the confusion) but in the 3rd line you say you're on unlocked Marshmallow. I'm going to assume you have limited knowledge of what the bootloader, the recovery, download mode, and system are.
-You mention seeing the red "RECOVERY IS NOT SE ANDROID ENFORCING". This is an error message generated by the bootloader saying the recovery is custom and did not pass the security check...but it is also completely normal. I get it every single time I go into TWRP...which works just fine.
-You do not understand what "MM" means when all of us including you are talking about Marshmallow.
-You do not understand what a "bootloop" is. For the sake of education, a bootloop is exactly what it sounds like - your device gets stuck in a loop while booting. This is generally mentioned when it is persistent - the device does not complete the boot process, coming to a stable useable Android interface. This is indicative of several possible problems; most likely you did something incorrectly, causing the boot process to halt, in which case the phone restarts itself to attempt to boot again, hence the loop.
-You do seem to understand sideloading via ADB and I'll give you credit for that. But when using the button combo (Vol Up+Home+Pwr) to boot into recovery, you WILL boot into recovery...whether that is stock recovery or TWRP. Some reboots may prevent this; if in doubt, hold Vol Down+Home+PWR until the screen shuts off; immediately go to Vol UP while still holding Home and Power.
-In the 13th post you ask about flashing kernels via Odin. Firstly: custom ROM .zips contain the kernel intended to work with that ROM. There is no need to flash anything separately. I am a little fuzzy on how root is accomplished on stock Marshmallow; it used to be we could flash SuperSu via recovery, but now there is talk about systemless...Anyway, I will reiterate what I was saying about Odin: DO NOT USE IT unless you know EXACTLY what you are doing. You have the potential to turn your phone into an expensive paperweight.
I am not trying to put you on blast or criticize you; I'm trying to help you avoid bricking your phone. There are a lot of things that could go wrong; you shouldn't be messing with something you don't understand, especially if you don't know how to fix it if something goes wrong.
For now even i am confused as to what is causing error.
Its probably that his storage is not curropt causing namd write fail..
I would recommend doing a backup. since you can turn on a phone, connect it to pc and move the important files and contacts to it.
Then download stock rom via sam mobile and do a clean install..
Ill prefer pf1 because, if memory serves right, edp1 had that notorious auto brightness bug.. If odin is not helping then try smart switch.
Boot up system, see if everything is working..it should be fresh as new.
After that follow the instructions as to flash twrp from the link i gave in one of my previous posts.. twrp should now flash...( i dont see any reason it shouldnt )
Flash root via recovery, or a custom rom you wanna flash but make sure its a 6.0.1 one ( xtre sto lite or alexis recommended )
That should root your phone too...
P.s. mm -> short for MarshMallow
Bootloop, when all you see is samsung logo which comes during boot... it wont go past that.. you never reach your lock screen or are able to unlock your phone... as mentioned in detail by -> socal
Flashing any rom overwrites kernel so if you flashed edp1, you are now on stock kernel...
P.p.s when you said sideload apk.. was it via adb shell or simply installing apk from internal memory of phone?
You answered a lot of my questions in that last post. Thank you kindly.
socal87 said:
EPD1 and EPF1 are 6.0.1 Marshmallow.
@ninjadroids:
Take this as you will but reading back through this thread gives me the impression that you lack the necessary know-how to customize your phone. I highly suggest you leave it stock for the time being until you know EXACTLY what you are doing.
My reasons for saying this:
-In your first post you state that "using Odin 3.10.7 I flashed using Twisted Sixx Custom ROM". To my knowledge there are NO custom ROMs designed to be flashed via Odin. They are in .zip files, to be installed via recovery ONLY.
-This is actually my mistake - the G920T bootloader does not have a lock function; flashing a custom recovery will simply trip the e-fuse and render it Knox 0x1 warranty void.
-You are not familiar with what Odin images are for the G920T, or what version they are. You should NEVER flash ANYTHING via Odin unless you are absolutely sure it is intended for your specific device.
-In the 9th post you state your bootloader is unlocked (again I apologize for the confusion) but in the 3rd line you say you're on unlocked Marshmallow. I'm going to assume you have limited knowledge of what the bootloader, the recovery, download mode, and system are.
-You mention seeing the red "RECOVERY IS NOT SE ANDROID ENFORCING". This is an error message generated by the bootloader saying the recovery is custom and did not pass the security check...but it is also completely normal. I get it every single time I go into TWRP...which works just fine.
-You do not understand what "MM" means when all of us including you are talking about Marshmallow.
-You do not understand what a "bootloop" is. For the sake of education, a bootloop is exactly what it sounds like - your device gets stuck in a loop while booting. This is generally mentioned when it is persistent - the device does not complete the boot process, coming to a stable useable Android interface. This is indicative of several possible problems; most likely you did something incorrectly, causing the boot process to halt, in which case the phone restarts itself to attempt to boot again, hence the loop.
-You do seem to understand sideloading via ADB and I'll give you credit for that. But when using the button combo (Vol Up+Home+Pwr) to boot into recovery, you WILL boot into recovery...whether that is stock recovery or TWRP. Some reboots may prevent this; if in doubt, hold Vol Down+Home+PWR until the screen shuts off; immediately go to Vol UP while still holding Home and Power.
-In the 13th post you ask about flashing kernels via Odin. Firstly: custom ROM .zips contain the kernel intended to work with that ROM. There is no need to flash anything separately. I am a little fuzzy on how root is accomplished on stock Marshmallow; it used to be we could flash SuperSu via recovery, but now there is talk about systemless...Anyway, I will reiterate what I was saying about Odin: DO NOT USE IT unless you know EXACTLY what you are doing. You have the potential to turn your phone into an expensive paperweight.
I am not trying to put you on blast or criticize you; I'm trying to help you avoid bricking your phone. There are a lot of things that could go wrong; you shouldn't be messing with something you don't understand, especially if you don't know how to fix it if something goes wrong.
Click to expand...
Click to collapse
Wonderful. Thanks man. I will be attempting a Stock ROM Odin flash and go from there. I will update my progress. Thank you all very much for the answered questions and pointing me in the right direction. Hopefully this thread will prove useful for anyone who is attempting to deal with a G920-T and attaining root the proper way for Marshmallow 6.x
danveer said:
For now even i am confused as to what is causing error.
Its probably that his storage is not curropt causing namd write fail..
I would recommend doing a backup since you can turn on a phone
Then downloading stock rom via sam mobile and do a clean install...if odin is not helping doing that then try smart switch.
Boot up system, see if everything is working..
After that follow the instructions as to flash twrp from the link i gave in one of my previous posts.. twrp should now flash...( i dont see any reason it shouldnt )
Flash root via recovery, or a custom rom you wanna flash vut make sure its a 6.0.1 one ( xtre sto lite or alexis recommended )
That should root your phone too...
Click to expand...
Click to collapse
Hi guys I've rooted my device 3 different ways(cf-autoroot, Skipsoft Toolkit, Root_SuperSU.1.02-Busybox.1.21.0.zip) tried 3 or 4 different roms and I've tried every custom recovery(philz, twrp, CWM) but can't get past the boot animation no matter which rom I use, does anyone have a fool proof way of rooting and installing a custom rom without being stuck at the boot animation? does knox affect this sort of thing? I honestly can't work out why I can't get this to work
Any help is really very much appreciated
Hey I got it sorted I had to reinstall the original rom and then flash cf-root with odin version 3.09
https://forum.xda-developers.com/galaxy-s3/help-i9305/installing-rom-failure-t2785670