Database Users

[Q] How to install stock ROM on I9505

Hi,
Currently there is not much on the phone, at least nothing to start up. I had CM, but had to go back so I tried the guide posted on this forum. With little success. So now im not sure where I stand as the phone is in a state without a ROM. When I try to start up normally i get "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Anyone can help me with installing fresh stock Samsung ROM?
Thanks in advance!
Sincerely,
Tho_kva2

Which was your last stock rom bevor you installed cm?
And which stock rom did you try to flash after cm?
Did they had the same product key?
Was the flashing process successful or did odin say "fail"?
And how is your current knox status? 0x1?
Send from my Galaxy S4 using Tapatalk

Not sure, but my phone was up to date with the latest update from Samsung.
I first tried to use "Norway (telenor)" first as, and when that failed I tried "Norway 4.4.2" Both found in the second post of the Guide.
Product key?
Odin said Fail. I tried multiple times with different odin versions and with PIT file.
Is it the "Knox warranty void" is so 0x1

And the latest original firmware running on your phone was it a Norway (telenor) firmware?
With product key i meant the csc.
The old firmware and the one you want to flash now have to have the same csc, i guess.
You can also flash a custom recovery and try to wipe and then flash again.
Send from my Galaxy S4 using Tapatalk

I'm not sure what the original firmware was, but it was the stock firmware i got with the phone when i bought it + updates.
CSC is TEN (Norway)
I do not know how to do a custom recovery, im a total noob on this subject of flashing and modding phones. Got any kind of guide or directrions to point me in? Sorry for not knowing squat, but hope you or someone else here can help me!

Hi,
okay, before you flash a recovery, you can try to flash another firmware but it have to be android 4.4.2 norway TEN
Did you also follow this note here?
"Odin troubleshooting:*If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer."
When odin will continue failing then try this.
http://www.usp-forum.de/downloads.php?do=file&id=1531
This is a 4 part open Europe firmware. Try to flash it...First time without pit,when odin failed try with pit...
If nothing helped, then you can install a custom recovery.
You once installed a recovery, before you flashed CM, remember?
But I will look for a guide and the right files.
Send from my Galaxy S4 using Tapatalk

It worked with the European version! Cheers mate Oh, it was without the pit.
Atleast android is installed hehe. but keyboard keeps crashing so cant type anything, and I cant turn on wifi; I get "Security notice, your device's security has blocked an action that is not permitted. No further action is required" -Knox Notification Manager.?
Oh and I got no SIM card to try at the phone atm. will get it later
So waht should be the next step?

Did you rooted this firmware already?
Try to fullwipe again. I thought this message only pops up, when the devise is rooted and Knox still not deleted... mysterious
Send from my Galaxy S4 using Tapatalk

I did not root it. I will try to wipe
Edit:
****ed up. Tried flashing the same again, and it failed lol.. so now im back to where I was before the phone "worked" again.
So I think I should get a recovery. Any thought?

Lol that's crazy. Also tried 4 part with pit?
And when you flash a Norway firmware again? Maybe it will work now, i don't know what's going on there
http://forum.xda-developers.com/showthread.php?t=2397108
This is CWM recovery for i9505, you have to flash the .tar file with odin in PDA or AP. It's your choice, whether you install the touch or non touch version.
Edit: anything new?
Send from my Galaxy S4 using Tapatalk

PIT File n910k note 4

Having major issues with my note 4.
I rooted the device with CF and had no problem, I think tried to install the CWM recovery and kept getting a FAIL in odin.
Tried different USB ports, different cables and 3 different computers.
I read to try unrooting then flashing recovery and then root again.
Once I unrooted the phone was stuck in a boot-loop and I still can't flash anything to the phone, not even CF-Root now, just bombs out with a fail.
I think I might need to re-partition the device, but need a PIT file for the note 4 please. All the phone displays now is a picture of a phone a yellow triangle and a computer, I have tried connecting kies but it says the phone is not supported, maybe because it is a korean model.
Thank you in advance

Ok starting to get massively confused now.
I have managed to flash the original firmware back to the phone, I can now do this everytime without fail via odin
But I cannot flash CF-Root or CWM recovery, everytime I get a fail error, even though i was able to flash CF-Root the other day.
Anyone got any ideas please, thank you in advance

Right I have sussed it, reactivation lock was enabled, disabled this and all working fine
Sent from my SM-G900F using Tapatalk

lysaer said:
Having major issues with my note 4.
I rooted the device with CF and had no problem, I think tried to install the CWM recovery and kept getting a FAIL in odin.
Tried different USB ports, different cables and 3 different computers.
I read to try unrooting then flashing recovery and then root again.
Once I unrooted the phone was stuck in a boot-loop and I still can't flash anything to the phone, not even CF-Root now, just bombs out with a fail.
I think I might need to re-partition the device, but need a PIT file for the note 4 please. All the phone displays now is a picture of a phone a yellow triangle and a computer, I have tried connecting kies but it says the phone is not supported, maybe because it is a korean model.
Thank you in advance
Click to expand...
Click to collapse
How do you manage to fix the bootloop without a pit file?

I got the original firmware from sammobile and flashed that
Sent from my SM-G925F using Tapatalk

lysaer said:
I got the original firmware from sammobile and flashed that
Sent from my SM-G925F using Tapatalk
Click to expand...
Click to collapse
Have you encounter "NAND write start" "FAIL"?

fannyman said:
Have you encounter "NAND write start" "FAIL"?
Click to expand...
Click to collapse
I did, but I cannot remember what I was trying to do at the time.
Are you flashing the original firmware from Samsung?
Sent from my SM-G925F using Tapatalk

Hello everyone. Can anyone help me to solution problem. I have Note 4 SM-N910K after unsuccessful attempts firmware via Smart Switch. I got error and no successful firmware. And want to back., but get fail via odin. I think i need pit file. If someone have just put link please. Thank's for advance.

Need help on unfamiliar error screen. Image provided.

Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
UPDATE <21_03_2015><16_54_09_524>____________________________________________________________
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Before flashing
first_flash_no_pit
first_boot_after_first_flash
Second_flash_no_pit
3rd_flash_with_pit

I think that this error appears when a ROM isn't flashed properly to the device. So a possible solution might be a factory reset in recovery and a clean ROM flash with Odin. You just need to download a ROM for your device model - SM-N9005 from sammobile or samsung-updates.

3XTR3M1ST said:
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
Click to expand...
Click to collapse
Download an official firmware from sammobile and use odin to flash. It's all on their site
Sent from my SM-N9005 using XDA Free mobile app

Is Odin a entirely different piece of software to kies?
Also would you this to be soft brick and reason to demand for compensation from the seller?

intervall said:
I think that this error appears when a ROM isn't flashed properly to the device. So a possible solution might be a factory reset in recovery and a clean ROM flash with Odin. You just need to download a ROM for your device model - SM-N9005 from sammobile or samsung-updates.
Click to expand...
Click to collapse
Yes this appears when a rom isn't flashed properly, Or the user has manually soft bricked the device.
st3chn0 said:
Download an official firmware from sammobile and use odin to flash. It's all on their site
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
I wouldn't take this advice as you bought a phone that is soft bricked with knox tripped (0x1)
try and return it before you attempt to fix it.
3XTR3M1ST said:
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
Click to expand...
Click to collapse
3XTR3M1ST said:
Is Odin a entirely different piece of software to kies?
Also would you this to be soft brick and reason to demand for compensation from the seller?
Click to expand...
Click to collapse
It looks like your knox is 0x1 and the system status is 'custom' but i can't really tell as the quality of the pictures isn't good enough.
This means that the phone has been used before and rooted, then a wrong flash or simply just deleting a few system files so it doesn't boot to get that screen to show up instead.
If there is nothing wrong with the hardware, Odin should fix this easily.. but i wouldn't trust it as your imei could of been changed.. many things could of been tampered with.
Also you mention that kies doesn't detect the phone properly, only sometimes. This could be your pc but it is likely a hardware problem with the phone judging by how you recieved it with knox tripped (0x1).
As it has been sold in this condition i can only assume that it has been tampered with. Why else would the seller sell a soft bricked device ?
Was it advertised as new or used?
Return it and get your money back as soon as possible is all i can suggest, good luck.

1. If its possible for him to return to the seller then yes but he can't to samsung. Due to knox being tripped. If he does its just basically a 50/50 chance
2. This nothing to do with soft brick. Such thing as a soft brick doesn't really exist.
3. Using odin to flash any official firmware. Is not bad advice.
Sent from my SM-N9005 using XDA Free mobile app

celderic said:
Yes this appears when a rom isn't flashed properly, Or the user has manually soft bricked the device.
I wouldn't take this advice as you bought a phone that is soft bricked with knox tripped (0x1)
try and return it before you attempt to fix it.
It looks like your knox is 0x1 and the system status is 'custom' but i can't really tell as the quality of the pictures isn't good enough.
This means that the phone has been used before and rooted, then a wrong flash or simply just deleting a few system files so it doesn't boot to get that screen to show up instead.
If there is nothing wrong with the hardware, Odin should fix this easily.. but i wouldn't trust it as your imei could of been changed.. many things could of been tampered with.
Also you mention that kies doesn't detect the phone properly, only sometimes. This could be your pc but it is likely a hardware problem with the phone judging by how you recieved it with knox tripped (0x1).
As it has been sold in this condition i can only assume that it has been tampered with. Why else would the seller sell a soft bricked device ?
Was it advertised as new or used?
Return it and get your money back as soon as possible is all i can suggest, good luck.
Click to expand...
Click to collapse
The seller is not responding to my questions, so I think the next best bet to attempt and fix it myself. Am I right to think that flashing an official firmware is the best option? What could go wrong if the imei have been changed?
Also, you just got me curious about the knox thing. Where do you suggest I look at for a comprehensive elaboration of the error codes?
http://postimg.org/image/rorg1p21n/

Flashing firmwate from sammobile will not trigger knox so as suggested earlier download and flash a firmware for your phone

st3chn0 said:
2. This nothing to do with soft brick. Such thing as a soft brick doesn't really exist.
Click to expand...
Click to collapse
This is a softbrick, if the hardware is fine then you should be able to fix it in 10mins by flashing a stock rom, but as the seller has sold it in this state then i assume it is softbricked for a reason so you can't test the device for example.
cryostasis25 said:
Flashing firmwate from sammobile will not trigger knox so as suggested earlier download and flash a firmware for your phone
Click to expand...
Click to collapse
But his knox is already tripped.. he bought a phone with knox 0x1 that's why i suggested returning it.
3XTR3M1ST said:
The seller is not responding to my questions, so I think the next best bet to attempt and fix it myself. Am I right to think that flashing an official firmware is the best option? What could go wrong if the imei have been changed?
Also, you just got me curious about the knox thing. Where do you suggest I look at for a comprehensive elaboration of the error codes?
http://postimg.org/image/rorg1p21n/
Click to expand...
Click to collapse
If the seller is not responding, then it points to them tampering with the device before selling it. Where did you buy it from, i would ring your bank as soon as possible.
Download the latest n9005 rom from sammobile and flash it through odin if you want to try and fix it, shouldn't really matter what csc as your knox is already tripped anyway so you can't recieve OTA updates or warranty from samsung anymore, mine is a BTU device but i have used many XEO roms.
If the phone isn't connecting to the computer properly like you say, then it's probably best to leave it. As this could result in the connection failing when it is flashing the bootloader or something. But if it works fine, then there should be no problems.
Here is something you could try, start up odin (i use v3.09), close all processes relating to kies, boot the device into download mode, that screen you provided pictures of. Plug the phone in and wait a few minutes to check the connection is stable, move the cable around to make sure the socket and cable are okay. You will see it come up on the top left in odin after windows has installed the drivers.
If this all works fine then flashing a stock rom should fix the device if the hardware is okay.

Just a quick question. From what site did you buy the phone and how did you pay for the phone?
Sent from my SM-N9005 using XDA Free mobile app

Where is a reliable source to download the official firmwares? I cant find it on the samsung site.
Tried http://www.samsungupdate.com/how-to/download-firmware but the file sizes are different on either filehost mirrors and it seems shady.

www.sammobile.com/firmwares/

I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Before flashing
first_flash_no_pit
first_boot_after_first_flash
Second_flash_no_pit
3rd_flash_with_pit

3XTR3M1ST said:
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Click to expand...
Click to collapse
1. Try flashing the new bootloader and modem first: http://forum.xda-developers.com/galaxy-note-3/general/odin-flashable-lollipop-bootloader-t3058101
2. If flashing modem and bootloader succeeded, try flashing the whole firmware again.
From what I learned from this http://forum.xda-developers.com/showthread.php?p=47287747#post47287747 thread, "invalid ext4 image" errors occur when bootloader is wrong.
Actually, do you have any info with what firmware was this phone last? I think I might have encountered another thread (don't remember it, though) which says that these exact problems occur when trying to upgrade from Jelly Bean 4.3 to Lollipop directly.

sirobelec said:
1. Try flashing the new bootloader and modem first: http://forum.xda-developers.com/galaxy-note-3/general/odin-flashable-lollipop-bootloader-t3058101
2. If flashing modem and bootloader succeeded, try flashing the whole firmware again.
From what I learned from this http://forum.xda-developers.com/showthread.php?p=47287747#post47287747 thread, "invalid ext4 image" errors occur when bootloader is wrong.
Actually, do you have any info with what firmware was this phone last? I think I might have encountered another thread (don't remember it, though) which says that these exact problems occur when trying to upgrade from Jelly Bean 4.3 to Lollipop directly.
Click to expand...
Click to collapse
Thanks for the suggestion. I'll give it a try after a little more research.
I have no idea what the phone was before, or what the seller did to it since he's just not responding anymore.

So I tried flashing the new bootloader as suggested, it seem to have worked to some extent, but then I screw it up again by pulling out the cable before seeing "PASS!". What now?
http://forum.xda-developers.com/showpost.php?p=59616074&postcount=16 said:
iketil said:
Hi the file size should be 58 041 KB
From what I can see from you ODIN log, ODIN has "done its thing"
If you did not uncheck the auto reboot tab, the phone should now be rebooting.
And bootloader and Modem should be updated when its booted up.
Are you still stuck at the "Samsung GALAXY Note3 SM-9005" screen ?
Click to expand...
Click to collapse
I'm still stuck on the "Samsung GALAXY Note3 SM-9005" screen. However I do think that the "hlte_lollipop_bootloader_modem.tar.md5" has "done its thing". I was previously unable to get to the recovery, but I was able to get to this <3e>recovery after flashing.
Also managed to see some logs of "i'm not sure what it is" before the phone went blank. I presume its due to battery going flat.
Later, I tried putting TWRP on it. Starting with "twrp-2.8.3.0-hlte-4.3.img.tar". But being a novice odin user I mistakenly unpluged the phone when odin is showing "RESET!". Then I tried going into recovery using VOLUP+HOME+POWER, and got this screen instead. I'm not sure if removing the phone before "PASS!" in odin could have caused this? Subsequently I tried flashing "twrp-2.7.0.3-hlte-4.3.img.tar" and
"twrp-2.7.2.0-hlte-4.3.img.tar", which resulted in the same error screen about SEANDROID.
I also noticed it increased my KNOX counter?
This is before and after.
Next I tried flashing ""hlte_lollipop_bootloader_modem.tar.md5" again hoping it would fix it. It didnt work. Silly me, this flash does not have a recovery image in it does it?
Anyway, now I dont have a working recover and is still stuck on the "Samsung GALAXY Note3 SM-9005". Thankfully odin mode still work. What should I do next? Please see this thread below for a little background to my problem. Thank you.
http://forum.xda-developers.com/galaxy-note-3/general/help-unfamiliar-error-screen-image-t3059227
Click to expand...
Click to collapse

HORRY SHET!!
I think my phone is asian! I just flashed the latest taiwan firmware released (N9005ZSUGOC3_N9005OZSGOC3_BRI) after flashing the new bootloader and everything works now!
I'm not sure what actually made it work since this is the first taiwan firmware I tried (its all XEO and BOB previously), but big thanks to everyone who helped!

Soft Bricked phone and now ODIN flash failing help!

So I upgraded from 4.4.2 kitkat to 5.0 lollipop. However, I soft bricked my phone by installing the wrong xposed SDK. Now I'm trying to flash 4.4.2 kitkat back onto my bricked phone and then update back to lollipop. Problem is ODIN is not wanting to flash the g900a stock rom back. It gives me an error saying 'SW REV CHECK FAIL : [ABOOT]FUSED 2 > BINARY 1' does anyone know how to fix this as I'd like to fix my phone soon!

900A? That's the AT&T model isn't it? That being the case, the locked bootloader on your device is only ever going to let you flash 5.0 if you had 5.0 on your device before you bricked....
http://i.imgur.com/rVnFwJM.jpg

help
keithross39 said:
900A? That's the AT&T model isn't it? That being the case, the locked bootloader on your device is only ever going to let you flash 5.0 if you had 5.0 on your device before you bricked....
Click to expand...
Click to collapse
That's good an all but where can I find a 5.0 in a tar format! My phone is literally bricked so I can't access it to flash the .zip files to it. I can't find a .tar of lollipop 5.0 anywhere no matter where I look all the links for ones have been taken down! You wouldn't happen to have one would you?

Not sure fella.....checked every hosting/firmware website I can think of, and all I'm seeing are KitKat firmwares.....
Have you tried Kies to see if it'll perform an 'emergency recovery/restore'?
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
Not sure fella.....checked every hosting/firmware website I can think of, and all I'm seeing are KitKat firmwares.....
Have you tried Kies to see if it'll perform an 'emergency recovery/restore'?
Click to expand...
Click to collapse
Kies won't recognize my device! It just says it's not supported! ;-; this is really unfortunate I've been looking everywhere with what little time I have (I work and I'm in college and it's around finals season for the semester so that doesn't help with time to fix this). I've been scouring everywhere but can't find anything. This is really unfortunate and I don't have the money to afford to have my phone fixed ;-; I'm really hoping I can find a solution soon! Everytime I try to install a kitkat 4.4.2 rom it just says FUSED 2 > BINARY 1 or something along those lines. From what I've heard that means I can't downgrade. Like I said what happened was I installed the wrong xposed sdk and it soft bricked. Every lollipop 5.0 rom I've found is in zip format. Now this wouldn't be a problem if I had a custom recovery that could flash zips and the means to put the zip on the phone. The problem is I don't (yes I've tried using ADB it refuses to put the zip on the phone it only lets me put .tar.md5's on there with the sideload and everything else just returns an error). If you find a solution or anyone else does please let me know! I'm In very dire need of help!! Also, my phone it makes it to the samsung galaxy s5 powered by android screen and then after that I just hear the AT&T noise but the screen doesn't change it just hangs there. I've also tried a full cache wipe and system restore in the recovery menu!

First of all.....The obvious....lol
These zips you mention, have you extracted them to see what's inside them.....
I know that sammobile and Samsung-updates provide their firmware .tars inside zips.....
Secondly, until someone makes an AT&T Lollipop firmware available, it looks like you're going to have to play the waiting game......at this point, I believe that with the correct firmware package, you WILL be able to recover your device....that may not be true further down the line if you continue to try 'potential' fixes.....
My advice is to leave it 'as-is' (unsatisfactory...I know) and wait for the firmware to become available......
Do you have an older device you can use in the mean time?
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
First of all.....The obvious....lol
These zips you mention, have you extracted them to see what's inside them.....
I know that sammobile and Samsung-updates provide their firmware .tars inside zips.....
Secondly, until someone makes an AT&T Lollipop firmware available, it looks like you're going to have to play the waiting game......at this point, I believe that with the correct firmware package, you WILL be able to recover your device....that may not be true further down the line if you continue to try 'potential' fixes.....
My advice is to leave it 'as-is' (unsatisfactory...I know) and wait for the firmware to become available......
Do you have an older device you can use in the mean time?
Click to expand...
Click to collapse
Yes I unzipped the zip. It was just files inside. I might just take it by an AT&T I'm pretty sure with all I've done to it the warranty is void but it's a worth a shot maybe they will take it in. I don't have an older device right now and I need to have some my phone soon as I have important usage of it with work. It seems I guess I don't have a choice left ;-; thank you though for all your help I'm very thankful for it

Galaxy S8 bricked - Stuck in boot loop after flashing twrp

Hey there everyone,
I wanted to root my s8 (sm-950f) and when I flashed twrp my phone initially got stuck in Samsung logo. After managing to shut it down I tried to go to recovery mode to wipe everything and perform a factory reset but I can not do it. All that happens is I get to s8 screen and it reads in red on top left of the screen "Only official released binaries are allowed to be flashed" and it keeps resetting itself. I can access download mode but that's it, I can't do anything else. Currently downloading a stock firmware to try and flash it but with the free downloads it's taking its time. Any help appreciated, I really want to unbrick my phone
note: It shows FRP and OEM lock to be off in download mode, i dont even know if i'll even be able to flash a new fw. Do I just have a very expensive brick in my hands now?

nekropok said:
Hey there everyone,
I wanted to root my s8 (sm-950f) and when I flashed twrp my phone initially got stuck in Samsung logo. After managing to shut it down I tried to go to recovery mode to wipe everything and perform a factory reset but I can not do it. All that happens is I get to s8 screen and it reads in red on top left of the screen "Only official released binaries are allowed to be flashed" and it keeps resetting itself. I can access download mode but that's it, I can't do anything else. Currently downloading a stock firmware to try and flash it but with the free downloads it's taking its time. Any help appreciated, I really want to unbrick my phone
Click to expand...
Click to collapse
This must be a international S8... Did you activate oem unlock in developer settings before flashing twrp
([emoji3590]09-09-18[emoji3590])

I'm not sure if it's international, it's most likely a Turkish version.
And yeah to your question

nekropok said:
I'm not sure if it's international, it's most likely a Turkish version.
And yeah to your question
Click to expand...
Click to collapse
But you know for a fact that there's a twrp version for your device.... Not good to do these expensive phones like that without officially having all the facts
([emoji3590]09-09-18[emoji3590])

Well it's too late for that now, I need actual solutions. I also tried smart switch - it doesn't recognize the phone

nekropok said:
Well it's too late for that now, I need actual solutions. I also tried smart switch - it doesn't recognize the phone
Click to expand...
Click to collapse
On the xda thread for your device there aren't no stock roms uploaded to Android host for fast download so you can flash in Odin and start the process of twrp again or just leave it alone you have a S8 it's good money
([emoji3590]09-09-18[emoji3590])

WHEW. Flashing a stock firmware seems to have fixed the issue. Mods can lock the thread.

nekropok said:
WHEW. Flashing a stock firmware seems to have fixed the issue. Mods can lock the thread.
Click to expand...
Click to collapse
You going to give up on twrp
([emoji3590]09-09-18[emoji3590])

I do want to root, but I don't want to approach it without knowing all my facts, do you have any suggestions for guides for Android 9.0?

nekropok said:
I do want to root, but I don't want to approach it without knowing all my facts, do you have any suggestions for guides for Android 9.0?
Click to expand...
Click to collapse
Just look in your device forum everything Is there however your device is a international cause it ends in with the F so twrp does work for your device..... You just need to find the specific one for your model once you have twrp you can install a android 9 custom rom
([emoji3590]09-09-18[emoji3590])

I had same issue as you and was pointed towards this thread may be of some use to you?
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535

Problem on my S8
PoochyX said:
This must be a international S8... Did you activate oem unlock in developer settings before flashing twrp
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
Sorry but I have a serious problem. I have activated oem and debug usb on developer option, but I can't install TWRP. I have tried with odin, prince cosmy odin, odin patched but FAIL everywhere, please help me, I just want twrp and i want to install a custom rom. thanks in advance everyone. If is a problem answer me here, you can send me a pvt message. I tried it from 3 days with the same FAILS :_(

I had this problem too a year ago but wasn't able to reflash the official firmware, but when I went to Samsung they fixed it for free even though Knox was already tripped

FabiusMod said:
Sorry but I have a serious problem. I have activated oem and debug usb on developer option, but I can't install TWRP. I have tried with odin, prince cosmy odin, odin patched but FAIL everywhere, please help me, I just want twrp and i want to install a custom rom. thanks in advance everyone. If is a problem answer me here, you can send me a pvt message. I tried it from 3 days with the same FAILS :_(
Click to expand...
Click to collapse
are you able to flash the stock firmware on it and get it to boot without TWRP installed?

I am with a stock rom now, The device works fine.