Related
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!
so samsung has reps at most best buys that will help you free of charge ( i had to go there when i first started rooting because i softbricked my phone and had no idea what to do and needed it the next day so if you dont feel like waiting or need something done that second or just dont wanna post on here you can always head up there and just tellem your question and theyll try and help you with what you need
Veid71 said:
so samsung has reps at most best buys that will help you free of charge ( i had to go there when i first started rooting because i softbricked my phone and had no idea what to do and needed it the next day so if you dont feel like waiting or need something done that second or just dont wanna post on here you can always head up there and just tellem your question and theyll try and help you with what you need
Click to expand...
Click to collapse
Thank you for your post. I soft bricked my S5 (bootloop) and will keep this in mind. For now I am at home and want to see if I can figure it myself. I need help to push a working ROM to my device SD card. I found a toolkit on root page http://forum.xda-developers.com/showpost.php?p=64744448&postcount=2
***Is there a tutorial that can help me know how to use the toolkit?
cyberfem said:
Thank you for your post. I soft bricked my S5 (bootloop) and will keep this in mind. For now I am at home and want to see if I can figure it myself. I need help to push a working ROM to my device SD card. I found a toolkit on root page http://forum.xda-developers.com/showpost.php?p=64744448&postcount=2
***Is there a tutorial that can help me know how to use the toolkit?
Click to expand...
Click to collapse
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
check that out if you werent previously rooted if you were previously rooted then try this
Use Odin to flash the lollipop kernel you were using. Then go into the stock recovery (hold Home + Vol UP and Power) and clear the cache and reboot. If that doesn't work, go back into the stock recovery, clear cache and select factory reset, then reboot. That should allow MOAR (whatever rom you want i stole this post from one of my other topics about when i softbricked mine) to boot, then you can reinstall SafeStrap Lollipop.
If you're getting any kind of logo screen showing up on boot, you are only "soft" bricked (not "hard" or permanently bricked) and you can fix it easily.
If you're only getting a logo, try what Veid71 said in the post above mine. If that doesn't work, then worst case you just need to flash a factory restore image with Odin and start over.
A word of caution, though: if your firmware version was updated to BOE1, BOG5, BOK3, do NOT flash an earlier factory image or you will brick because after BOD the bootloader was locked and you can't downgrade it.
painiac said:
If you're getting any kind of logo screen showing up on boot, you are only "soft" bricked (not "hard" or permanently bricked) and you can fix it easily.
If you're only getting a logo, try what Veid71 said in the post above mine. If that doesn't work, then worst case you just need to flash a factory restore image with Odin and start over.
A word of caution, though: if your firmware version was updated to BOE1, BOG5, BOK3, do NOT flash an earlier factory image or you will brick because after BOD the bootloader was locked and you can't downgrade it.
Click to expand...
Click to collapse
I get the logo screen like it is turning on then it goes to recovery mode options. I can get to Download mode and Odin has a blue port connection but my Win8 and Win7 PCs do not see the device at all, so I cant' flash in Odin. Background - I attempted to root using jrkruse method and got stuck and never rooted. Anyone know a way around this maybe using the external SD card?
cyberfem said:
I get the logo screen like it is turning on then it goes to recovery mode options. I can get to Download mode and Odin has a blue port connection but my Win8 and Win7 PCs do not see the device at all, so I cant' flash in Odin. Background - I attempted to root using jrkruse method and got stuck and never rooted. Anyone know a way around this maybe using the external SD card?
Click to expand...
Click to collapse
When it boots into the recovery mode options, try clearing cache and then reboot. If that doesn't work, do it again, clearing cache and also factory reset. That may allow your phone to boot back up normally.
The SDcard Unbrick method is only needed if your phone cannot boot into Download mode. In this case, it wouldn't help you because your phone is functioning in that regard.
When you have the phone in Download mode, your computer won't show it as a device in "My Computer" because it's not connected as a media device., but software that knows how to look for it can see it. If Odin is lighting up blue in the first ID:COM box, it IS seeing the phone and you will be able to flash to it.
If you're to a point where you need to flash a factory restore image, click the "AP" button in Odin to select it. The image needs to be one that ends with a file extension "tar.md5", or Odin can't see it. If what you've downloaded is a zip archive, the image is inside that and you need to extract it first. Use the image in "step 2" of the root thread
I figured out what went wrong from your response thanks! I had saved the .tar.md5 on the external SD card rather than pc. Now attempting to re-root, .bat sees device but doesn't root.
cyberfem said:
I figured out what went wrong from your response thanks! I had saved the .tar.md5 on the external SD card rather than pc. Now attempting to re-root, .bat sees device but doesn't root.
Click to expand...
Click to collapse
yeah its really annoying youll have to unplug and plug it back in and x out of the thing like 20 times before it acutually does it
The Core Prime will not boot into recovery, or safe mode, or to the home screen. The only way to sometimes get it into download mode is leave it plugged into the wall charger for a couple minutes, then it will SOMETIMES go into download mode to charge. Holding down every combination of keys does not work, please don't suggest holding down keys.
All I ever see is a mmc confirmation fail movinand checksum confirmation fail error no matter what I try. I never see the Samsung intro, boot intro, or tracfone intro anymore, just a black screen that leads to that error message in red letters.
Regardless of which computer or cable I use, Windows never sees the phone. Doesn't try to install the drivers, doesn't make a sound that something was plugged in, nothing shows up in device manager, nothing (even in download mode)
I called 800 Samsung (4 times asking the same thing to different people to make sure I didn't just get helped by a noob over the phone). I went and talked to the Samsung guys inside worst buy (didn't do anything except informing me there is a Samsung store in LA). I called the Samsung store in LA and talked to a technician and the technician supervisor (I could drive there if their answer wasn't factory reset)
But EVERYONE from Samsung is saying all that can be done is factory reset.
I do not need a factory reset. I need my data.
I have posted numerous threads, and even though there was good advice given, none of it worked.
All I did before this error was try to update Google maps. The phone has never been backed up/rooted/nothing its stock.
At this point, I'm willing to negotiate paying someone to get my data back.
Someone please help.
Sorry To Hear that this is really a big problem but every thing has a solution ..
As you say the windows doesn't read the device and so as Odin try http://tinyurl.com/Heimdall-oa on Linux (don't use virtual machine )
OK if Heimdall read the device flash stock firmware (same version) if the device open congratulations
else flash custom recovery (you can find one in cyanogen discussion) and launch aroma file manager pull out your data so you're safe to reset ?? hope to be helped you .
The x man said:
Sorry To Hear that this is really a big problem but every thing has a solution ..
As you say the windows doesn't read the device and so as Odin try http://tinyurl.com/Heimdall-oa on Linux (don't use virtual machine )
OK if Heimdall read the device flash stock firmware (same version) if the device open congratulations
else flash custom recovery (you can find one in cyanogen discussion) and launch aroma file manager pull out your data so you're safe to reset ���� hope to be helped you .
Click to expand...
Click to collapse
Thank you for trying to help me. I do not yet have a Linux box set up. Can you recommend a distro, version, or live cd of Linux to use?
You can use Ubuntu 14.04
The x man said:
You can use Ubuntu 14.04
Click to expand...
Click to collapse
I will post my results here as soon as I try
If your phone is still stuck, flash TWRP (google it if you don't know it) for s820l. After TWRP is installed backup your data to your Internal or External Storage. Once the backup is complete factory reset (I highly suggest bakcking up to an SD card) if it still only boots to this screen try flashing the Stock ROM.
If your phone is messed up after the factory reset, i suggest SD card for files and everything if your computer has an SD adapter and reader you won't need to turn the device on. Hopefully this fixes it for you.
P.S. By no means do I know exactly what I'm doing, I flashed the wrong TWRP for mine and only got a download screen. This is the method i used to fix it. Also i am not allowed to post links or I would. so google sm-s820l custom recovery and to get a Stock ROM. Above the page for it should be a bunch of tabs that look like this " Android Area 51 > Forum > Straight Talk/Net10 > Samsung Phones > Samsung Galaxy Core Prime > Recovery Releases" Click on Samsung GCP and then your all set. Hope this helps.
AJOKER21 said:
If your phone is still stuck, flash TWRP (google it if you don't know it) for s820l. After TWRP is installed backup your data to your Internal or External Storage. Once the backup is complete factory reset (I highly suggest bakcking up to an SD card) if it still only boots to this screen try flashing the Stock ROM.
If your phone is messed up after the factory reset, i suggest SD card for files and everything if your computer has an SD adapter and reader you won't need to turn the device on. Hopefully this fixes it for you.
P.S. By no means do I know exactly what I'm doing, I flashed the wrong TWRP for mine and only got a download screen. This is the method i used to fix it. Also i am not allowed to post links or I would. so google sm-s820l custom recovery and to get a Stock ROM. Above the page for it should be a bunch of tabs that look like this " Android Area 51 > Forum > Straight Talk/Net10 > Samsung Phones > Samsung Galaxy Core Prime > Recovery Releases" Click on Samsung GCP and then your all set. Hope this helps.
Click to expand...
Click to collapse
Core prime model is also G-360* (main number) not just SM-820L .
The x man said:
Core prime model is also G-360* (main number) not just SM-820L .
Click to expand...
Click to collapse
True so if it's not the SM-S820L just input your model number instead of the one I posted that was my bad I assumed TracFone. Also don't think just because the phone is the same they will all work if you do use the wrong TWRP or ROM because the model is different it will brick your device. Again it was my mistake but overall I hope this helps.
AJOKER21 said:
True so if it's not the SM-S820L just input your model number instead of the one I posted that was my bad I assumed TracFone. Also don't think just because the phone is the same they will all work if you do use the wrong TWRP or ROM because the model is different it will brick your device. Again it was my mistake but overall I hope this helps.
Click to expand...
Click to collapse
Never mind i just wanted to share info. + mine reply was before twrp or cwm being ported to core prime ,and at this time no custom roms for 360* Models
Is TWRP ported to other versions of this phone? It seems like it is atleast the VE one has it and my TracFone version does I'm sure most of the others ones do and you also do not need a Custom ROM just a stock one which is probably floating around out there somewhere. For the OPs phone which if the model was posted this would be a billion times easier. So Mr. OP please post your model for us to help if your issue is still happening.
G360 Rom
AJOKER21 said:
True so if it's not the SM-S820L just input your model number instead of the one I posted that was my bad I assumed TracFone. Also don't think just because the phone is the same they will all work if you do use the wrong TWRP or ROM because the model is different it will brick your device. Again it was my mistake but overall I hope this helps.
Click to expand...
Click to collapse
I have a SM-S820L that i flashed with a 360 and now its bricked
Hii @android_n this is also happen with me on My core 2 G355H I also try to flash Offical frimware but it only boot for few second and shut down
I replace battery with new one and it booted
Problem is in battery it only boot when charger is connect or you can charge your phone battery by booster charger hit thanks if I help
I tried that what i need is a new OS. It keeps telling me No OS is installed but Havent been able to get it installed
noxqes said:
I tried that what i need is a new OS. It keeps telling me No OS is installed but Havent been able to get it installed
Click to expand...
Click to collapse
Check out this thread here http://forum.xda-developers.com/gal...stock-rom-deodex-busybox-root-t3378999/page1. Hope this helps
Sent from my SM-G360T1 using XDA Labs
Well the title says it all. Made a similar post in that wrong area I believe. That's probably why I didn't get a response.
Anyway, I had 6.0 but had downgraded to 5.0 and my build is SM-G870AUCUBF03. I tried to apply a stock kernel, G870A_NE4_Stock_Kernel.tar.md5, more specifically and it appears to be soft-bricked.
It shows the Samsung splash then after awhile going into recovery mode. I can still access Download mode as well. I tried hard-resetting, wiping data/factory settings. Any help would be very much appreciated. Thanks for taking the time to read this.
You could try the restore firmware function in Kies. It will be the easiest way to get back a working phone
I'm trying that right now, but it is saying that the connected device is not supported.
Can't find 5.0 stock firmware or anything really that leads me to believe that I can recover this phone. I can't believe this.
bfletxh said:
Can't find 5.0 stock firmware or anything really that leads me to believe that I can recover this phone. I can't believe this.
Click to expand...
Click to collapse
Read here.
https://www.sammobile.com/forum/showthread.php?t=30248
First Google search.
https://www.sammobile.com/firmwares/galaxy-s5-active/SM-G870A/
I'd suggest staying away from KIES and using Odin instead. In fact if you use Odin, and you have KIES installed on the same PC, disable it first. When all else fails, Odin is your friend. Just read up on the steps for using Odin if you're unfamiliar with it. And make sure you have the right firmware.
Sent from my Samsung SM-G900I using XDA Labs
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.