Database Info

[Q] GT-N8010 stuck in logo and won't enter recovery

Hi folks,
I've seen other threads where people report similar but perhaps not quite the same issue I am having with my GT-N8010. For context, I installed 4.4.2 a while ago (February?). This was one of the Omni nightlies, omni-4.4.2-20140210. In preparation for this I had installed twrp-2.6.3.1-n8000. All was well and I much enjoyed kitkat until a few weeks came back from a trip and noticed the device had run out of juice. Connected it to the charger and then...
Symptoms:
* Seems to be stuck displaying the Samsung logo
* Download mode works
* When trying to enter recovery (Power+VOL_UP) it briefly shows the Team Win screen logo and then just reboots
Things I've tried:
* Reinstall twrp, using Odin and download mode; Odin succeeds, the device reboots, same symptoms as before
* Install some other recovery (HighOnAndroidv1CWMRecoveryGTN8000), same result; it is as though NOTHING gets flashed???
* Install stock (4.0.4 or 4.1.2, I don't remember) Samsung ROM; Odin succeeds (it takes a few minutes), device reboots but HECK I'm going insane NOTHING has changed, symptoms as before
Please please can one of you ninja dudes help me out as this is such a precious tablet and hopefully not just a brick now .
Among the things I haven't tried, but heard can do wonders, is to re-partition. So if you happen to have a PIT file from your N8010 then would you mind sharing it through a PM please.
Also am currently downloading the "official" 4.4.2 release for the N8000. I've heard this is NOT for the N8010 but as a last resort, I might flash it??
Many thanks in advance for all the help!
Matt

matt_9010 said:
Hi folks,
I've seen other threads where people report similar but perhaps not quite the same issue I am having with my GT-N8010. For context, I installed 4.4.2 a while ago (February?). This was one of the Omni nightlies, omni-4.4.2-20140210. In preparation for this I had installed twrp-2.6.3.1-n8000. All was well and I much enjoyed kitkat until a few weeks came back from a trip and noticed the device had run out of juice. Connected it to the charger and then...
Symptoms:
* Seems to be stuck displaying the Samsung logo
* Download mode works
* When trying to enter recovery (Power+VOL_UP) it briefly shows the Team Win screen logo and then just reboots
Things I've tried:
* Reinstall twrp, using Odin and download mode; Odin succeeds, the device reboots, same symptoms as before
* Install some other recovery (HighOnAndroidv1CWMRecoveryGTN8000), same result; it is as though NOTHING gets flashed???
* Install stock (4.0.4 or 4.1.2, I don't remember) Samsung ROM; Odin succeeds (it takes a few minutes), device reboots but HECK I'm going insane NOTHING has changed, symptoms as before
Please please can one of you ninja dudes help me out as this is such a precious tablet and hopefully not just a brick now .
Among the things I haven't tried, but heard can do wonders, is to re-partition. So if you happen to have a PIT file from your N8010 then would you mind sharing it through a PM please.
Also am currently downloading the "official" 4.4.2 release for the N8000. I've heard this is NOT for the N8010 but as a last resort, I might flash it??
Many thanks in advance for all the help!
Matt
Click to expand...
Click to collapse
There is a n8010 release of 4.4.2 for your Device. but Do NOT Flash the n8000 rom on it..
I think you should odin the 8010 rom from Sam mobile and you will be ok . If not browse the forum and find a pit file for that device.. also some have reported Issues flashing with latest odin. try i think verson 2.9 ?

erica_renee said:
There is a n8010 release of 4.4.2 for your Device. but Do NOT Flash the n8000 rom on it..
I think you should odin the 8010 rom from Sam mobile and you will be ok . If not browse the forum and find a pit file for that device.. also some have reported Issues flashing with latest odin. try i think verson 2.9 ?
Click to expand...
Click to collapse
Thanks, have just flashed the 8010 4.4.2 stock fw. Symptoms remain. I'd be very grateful for a PIT file as I've waded through the other threads and not too sure about the links to PIT files there. PM, anyone, please please .

I've got the N8010 PIT file from here:
http://forum.xda-developers.com/showthread.php?t=2363703
Sadly, this didn't change a thing. I'm still stuck at the Samsung logo, and still cannot enter recovery mode which still briefly shows the TeamWin logo and then reboots.
This N8010 is just over a year old. Bought in Germany, I wonder whether Samsung would repair under warranty. I guess they won't as it's been fiddled with. I've heard about JTAG repairs but something tells me this isn't going to help as I have a feeling that I just can't flash the darn thing. Eeek, faulty flash memory??

matt_9010 said:
I've got the N8010 PIT file from here:
http://forum.xda-developers.com/showthread.php?t=2363703
Sadly, this didn't change a thing. I'm still stuck at the Samsung logo, and still cannot enter recovery mode which still briefly shows the TeamWin logo and then reboots.
This N8010 is just over a year old. Bought in Germany, I wonder whether Samsung would repair under warranty. I guess they won't as it's been fiddled with. I've heard about JTAG repairs but something tells me this isn't going to help as I have a feeling that I just can't flash the darn thing. Eeek, faulty flash memory??
Click to expand...
Click to collapse
search for this file in the forum: Note10_PIT.zip (dunno0 where was it)
the if u can enter to download mode try to flash one of the latest 4.1.2 stock roms with odin 3.07....
if u succeed write here....:laugh:

karaern said:
search for this file in the forum: Note10_PIT.zip (dunno0 where was it)
the if u can enter to download mode try to flash one of the latest 4.1.2 stock roms with odin 3.07....
if u succeed write here....:laugh:
Click to expand...
Click to collapse
Sadly not. Others have reported that having gone with one of the Omni 4.4.2 builds they cannot get the official 4.4.2 release from Samsung installed, at least not with desktop Odin. They do succeed with mobile Odin but yeah, that's not an option here as I don't get past the Samsung logo and no recovery. This is really frustrating.....

matt_9010 said:
Sadly not. Others have reported that having gone with one of the Omni 4.4.2 builds they cannot get the official 4.4.2 release from Samsung installed, at least not with desktop Odin. They do succeed with mobile Odin but yeah, that's not an option here as I don't get past the Samsung logo and no recovery. This is really frustrating.....
Click to expand...
Click to collapse
Try to reinstall the latest rom u had before installing kk! Exact same version with same recovery.

matt_9010 said:
Hi folks,
I've seen other threads where people report similar but perhaps not quite the same issue I am having with my GT-N8010. For context, I installed 4.4.2 a while ago (February?). This was one of the Omni nightlies, omni-4.4.2-20140210. In preparation for this I had installed twrp-2.6.3.1-n8000. All was well and I much enjoyed kitkat until a few weeks came back from a trip and noticed the device had run out of juice. Connected it to the charger and then...
Symptoms:
* Seems to be stuck displaying the Samsung logo
* Download mode works
* When trying to enter recovery (Power+VOL_UP) it briefly shows the Team Win screen logo and then just reboots
Things I've tried:
* Reinstall twrp, using Odin and download mode; Odin succeeds, the device reboots, same symptoms as before
* Install some other recovery (HighOnAndroidv1CWMRecoveryGTN8000), same result; it is as though NOTHING gets flashed???
* Install stock (4.0.4 or 4.1.2, I don't remember) Samsung ROM; Odin succeeds (it takes a few minutes), device reboots but HECK I'm going insane NOTHING has changed, symptoms as before
Please please can one of you ninja dudes help me out as this is such a precious tablet and hopefully not just a brick now .
Among the things I haven't tried, but heard can do wonders, is to re-partition. So if you happen to have a PIT file from your N8010 then would you mind sharing it through a PM please.
Also am currently downloading the "official" 4.4.2 release for the N8000. I've heard this is NOT for the N8010 but as a last resort, I might flash it??
Many thanks in advance for all the help!
Matt
Click to expand...
Click to collapse
Did you ever find a solution ?

chappatti said:
Did you ever find a solution ?
Click to expand...
Click to collapse
Err well I ended up bringing the tablet to a Samsung service store where it was repaired under warranty, free of charge. Dunno what they did to it but it works and has the latest 4.4.2 firmware on it. Glad I have it back.

I have exactly same problem with N8005!... Can't reinstall twrp or any other recovery with Odin. ( "failed")... Can't enter twrp... Can't boot... I guess my tablet decided to suicide.

[Q] What type of brick is my Galaxy note 10.1 gt n8010 stuck?

Two days ago my Galaxy Note 10.1 gt-n8010 got stuck at the initial screen (Samsung Galaxy Note 10.1)
It was working normally, and it was last successfully upgraded to a custom rom and CWM 6.0.3.6 a month ago.
The custom rom was (to my best knowledge Android Revolution HD 11.2 - 4.1.2)
Booting into recovery and download modes works.
CWM recovery works partially. Erasing Cache en resetting to factory works, and sometimes results in getting to the second splash screen of the boot process where it again gets stuck (Samsung animation keeps glowing), but more it keeps getting stuck at he first boot screen.
Erasing Dalvic cache leads to immediate reboot.
CWM log files cant be opened / external sd card can't be reached/mounted.
So CWM is only working for a small part.
I've attached images of the CWM screens including a log-screen that shows that files and folders cannot be found.
Using ODIN, to flash a new CWM or custom/original ROM result in a FAIL message.
Tried different ODIN version, two original Samsung data cables and two computers. Alle the same result. FAIL.
I'm hesitant to continue now without some help. I might do more harm and destroy all chances there are to recover this tablet.
I've flashed all my phones and tablets before. I'm not an expert, but never had a mishap, because I triple read the instructions. The situation that arises now is not a result of a failed upgrade/flash, but suddenly appeared one morning.

On the last days i thought i had also broken my tablet and i had more or less the same problem. If i were you i would directly download an official 4.4.2 and flash it via odin. Then if you everything works i would try whatever you want to flash

Try changing recovery. Give TWRP a try. Had it happen with a phone and switching recoveries solved it.
Sent from my SM-N900T using XDA Free mobile app

Well I had the same problem due to toooo many consecutive reboots
I was on gnabo then wid twrp
then I reflashed 4.4.2 update via odin and everything was a breeze after that
and one more thing
be sure to change the recovery cause the same one might not work again
well at least it didn't do worth me
I use philz now

Can't flash anything
Tried everything I could find but nothing works. I'm using windows 7 and cannot flash anything using Odin.
Download mode and CWM recovery still boot.
Are there other ways to communicate and reprogram the galaxy note 10.1?

Deadbeef said:
Tried everything I could find but nothing works. I'm using windows 7 and cannot flash anything using Odin.
Download mode and CWM recovery still boot.
Are there other ways to communicate and reprogram the galaxy note 10.1?
Click to expand...
Click to collapse
are you sure you do not have a bad cable

I've used two different original Samsung cables. Same result.

Brick?
Change a Odin version like odin 3.07 http://forum.xda-developers.com/showthread.php?t=1837605?
your odin shows your device is Samsung I9505 Galaxy S4

Where does Odin show the device is a i9505? It's a n8010.

reCAPTCHA
I am having similar issues (Galaxy Note 10.1 N8010 Gnabo ROM) - stuck on the samsung logo (never managed to get past it though) boots into recovery but can't mount sd card OR internal storage. Can't flash anything using Odin, always gets a Complete(Write) operation failed. Any suggestions ?

Looks like we're both in the same sinking boat.

Sorry for late reply
Deadbeef said:
Where does Odin show the device is a i9505? It's a n8010.
Click to expand...
Click to collapse
Sorry for late reply
Your Odin Screen Shot Say i9505 as your device

Deadbeef said:
Looks like we're both in the same sinking boat.
Click to expand...
Click to collapse
I join u guys as well....
also was on gnabo rom and suddenly stuck on Samsung screen... however what's different from you is that I have a N8000 and Odin flashing shows "PASS". But whatever I flash doesn't boot... I think I need to open a thread about it.

georgesmh said:
I join u guys as well....
also was on gnabo rom and suddenly stuck on Samsung screen... however what's different from you is that I have a N8000 and Odin flashing shows "PASS". But whatever I flash doesn't boot... I think I need to open a thread about it.
Click to expand...
Click to collapse
Same here with Ganbo v7 since ysterday....
Just get stuck on Samsung logo and nothing works, even reverting to older backup image

Agyar said:
Same here with Ganbo v7 since ysterday....
Just get stuck on Samsung logo and nothing works, even reverting to older backup image
Click to expand...
Click to collapse
guys did any of you solve the problem??

georgesmh said:
guys did any of you solve the problem??
Click to expand...
Click to collapse
Nothing yet.... I've tried one old backup of v5 I've had and that won't boot now as well...
Really strange. I'm hoping to get it working somehow over the weekend latest, since I'll be on business trip next week and would like to have operating device on airplanes.

Agyar said:
Nothing yet.... I've tried one old backup of v5 I've had and that won't boot now as well...
Really strange. I'm hoping to get it working somehow over the weekend latest, since I'll be on business trip next week and would like to have operating device on airplanes.
Click to expand...
Click to collapse
maybe it's a problem from Gnabo ROM itself??? What's really sad is nobody on the threads knows how to help us
Uni starts next week!

georgesmh said:
maybe it's a problem from Gnabo ROM itself??? What's really sad is nobody on the threads knows how to help us
Uni starts next week!
Click to expand...
Click to collapse
I've seen few other occurrences of this on different roms on various forums, so probably not Gnabo issue. also, nobody nowhere had a fix for it

I had similar problem last November with a stock 4.4.2 ROM. Fortunately it was still in warranty (2 years in the UK) and Samsung took it in and replaced both battery and main board. They did not explain what was wrong, only that they were seeing quite a few with this issue. Could it be flash failure?

dmarchant said:
I had similar problem last November with a stock 4.4.2 ROM. Fortunately it was still in warranty (2 years in the UK) and Samsung took it in and replaced both battery and main board. They did not explain what was wrong, only that they were seeing quite a few with this issue. Could it be flash failure?
Click to expand...
Click to collapse
I don't think it was flash failure, at least not in my case, since device worked without any issue for quite a while after last flashing... what was different now is that my battery was drained out for the first time i quite a while...

Touchscreen x axis reversed

I accidentaly flashed the edge version of twrp to my regular s6, 920r4. Now my touchscreen is reversed along the xaxis. When I dial *#2663#, nothing happens, only a dialtone goes on. Any suggestions?

Reflash regular S6 5.1.1 stock ROM via odin.

I did that, still no fix. Then I did a full reset, no fix.

Bring your S6 back to Samsung for repair.

roydok said:
Bring your S6 back to Samsung for repair.
Click to expand...
Click to collapse
Obviously my knox is tripped after flashing TWRP, would samsung be able to fix this anyway?

I hope so...

In other related threads, members were able to use the "secret codes" to update the TSP firmware. Could I perhaps install say the firmware for the 920F, then access the secret codes on that firmware, and in that process update the TSP firmware?

Flash this S6 regular S920R4 5.1.1 stock ROM instead of G920F:
http://www.sammobile.com/firmwares/download/48614/G920R4TYU2BOF7_G920R4USC2BOF7_USC/

Posting this for future reference for anyone that comes across this issue. The instructions below resolved my reversed issue.
@ScottBroker - If that happens again, you will not need to exchange your device. In the dialer, input *#2663# and select the "TSP FW update (General)". In order to do this, you would have to actually press "TSP FW update (Internal Storage)" since your horizontal touch is reversed.

This did not do anything for me. Could i just use the right one instead and all should go well? or there be another solution?
lagvoid said:
Posting this for future reference for anyone that comes across this issue. The instructions below resolved my reversed issue.
@ScottBroker - If that happens again, you will not need to exchange your device. In the dialer, input *#2663# and select the "TSP FW update (General)". In order to do this, you would have to actually press "TSP FW update (Internal Storage)" since your horizontal touch is reversed.
Click to expand...
Click to collapse

I finally got this issue fixed after almost half a year. I updated the firmware to a newer version, using the software update on the phone. My issue is finally fixed. I think that perhaps the several months new software update was different enough to require a complete changing of the recovery software.
Or at least something like that!
No longer will I be using my old s4, running liquidsmooth, that restarts 3-4 times a day. With a shattered screen at that!

Resurrecting the Thread
lagvoid said:
Posting this for future reference for anyone that comes across this issue. The instructions below resolved my reversed issue.
@ScottBroker - If that happens again, you will not need to exchange your device. In the dialer, input *#2663# and select the "TSP FW update (General)". In order to do this, you would have to actually press "TSP FW update (Internal Storage)" since your horizontal touch is reversed.
Click to expand...
Click to collapse
A year after OP, I've ran into the same issue as the OP.
I accidentally flashed an edge kernal (I think, might've just been an incorrect baseband) on my flat S6 (920t). Tried things from flashing correct kernals to wiping to Odin restoring stock firmware. Nothing worked, then I found this and my problem was resolved in 2.4 seconds. I laughed at myself for this one :silly:
(Note: I had a TWRP backup, but didn't try restoring because it was from a previous firmware and I'm not sure it would've worked, which is why I searched for other solutions...and found this one!)

Hi I have got same problem. but afters tiping *#2663# nothing hapend. What can I do?
Ishmael89 said:
A year after OP, I've ran into the same issue as the OP.
I accidentally flashed an edge kernal (I think, might've just been an incorrect baseband) on my flat S6 (920t). Tried things from flashing correct kernals to wiping to Odin restoring stock firmware. Nothing worked, then I found this and my problem was resolved in 2.4 seconds. I laughed at myself for this one :silly:
(Note: I had a TWRP backup, but didn't try restoring because it was from a previous firmware and I'm not sure it would've worked, which is why I searched for other solutions...and found this one!)
Click to expand...
Click to collapse

wolkowicz said:
Hi I have got same problem. but afters tiping *#2663# nothing hapend. What can I do?
Click to expand...
Click to collapse
Which model do you have? The dialer menus might be specific to the model/carrier, I'm not certain about that though.

After rebooting my phone couple of times it works. Thanks!!!
Ishmael89 said:
A year after OP, I've ran into the same issue as the OP.
I accidentally flashed an edge kernal (I think, might've just been an incorrect baseband) on my flat S6 (920t). Tried things from flashing correct kernals to wiping to Odin restoring stock firmware. Nothing worked, then I found this and my problem was resolved in 2.4 seconds. I laughed at myself for this one :silly:
(Note: I had a TWRP backup, but didn't try restoring because it was from a previous firmware and I'm not sure it would've worked, which is why I searched for other solutions...and found this one!)
Click to expand...
Click to collapse
Ishmael89 said:
Which model do you have? The dialer menus might be specific to the model/carrier, I'm not certain about that though.
Click to expand...
Click to collapse

wolkowicz said:
After rebooting my phone couple of times it works. Thanks!!!
Click to expand...
Click to collapse
No problem, glad it worked out and you can use your phone regularly now!

As I have found multiple threads for the same issue, I figured I would post the info in a few of them so if anyone else come looking for the issue and fix - they can get right to the howto instead of digging through multiple threads like I did. More info about the issue was found on the following link/s - https://1024kb.co.nz/galaxy-s6-reversed-touchscreen/ & https://forum.xda-developers.com/showpost.php?p=62289392&postcount=9
You DO not have to flash any stock roms or other versions of twrp to fix this, as it will NOT fix the issue, as near as I can tell something corrupted or changed the setting somewhere on the hidden section of the phone's firmware. All you need to do is access a hidden engineers menu, click on a button and your done.
The hidden adjustment setting is accessible through keypad *#2336# (reverse-entered as #*2114*) (you have to do this as the touchscreen is still reversed so you are unable to enter *#2336# normally). Once the task completed I then was able to press the back key and have it function as normal which confirmed the fix.

Odin fails at cm.bin while flashing Galaxy J710FN

I was trying to flash Glaxy J710FN with stock ROM using Odin. But it fails at cm.bin and shows 'Complete write operation failed'. Please do help me with this.

I am facing the same issue, I've googled the problem and Its something to do with the wrong baseband version which cannot be downgraded.
I am on supernova ROM and want to switch to complete stock, unroot for warranty.
DId you find any solution?

jumbobombo said:
I am facing the same issue, I've googled the problem and Its something to do with the wrong baseband version which cannot be downgraded.
I am on supernova ROM and want to switch to complete stock, unroot for warranty.
DId you find any solution?
Click to expand...
Click to collapse
It has something to do with the USB cable, USB port and the installed driver versions. Update your driver to the latest version. Try using a different USB port, never use a USB hub. And that's it.

Jezwn said:
It has something to do with the USB cable, USB port and the installed driver versions. Update your driver to the latest version. Try using a different USB port, never use a USB hub. And that's it.
Click to expand...
Click to collapse
Also check whether you're trying to downgrade to a former version of Android which can't be done using Odin. Try getting the latest version of your stock ROM which you can Google yourself.

Thanks for your reply
I tried with different USB port but receiving same error.
Supernova custom ROM is on Android 6 and the firmware that I downloaded are also Android 6
I am completely clueless on how to solve this issue. I've been sitting and researching about this since 2 days now with no luck

jumbobombo said:
Thanks for your reply
I tried with different USB port but receiving same error.
Supernova custom ROM is on Android 6 and the firmware that I downloaded are also Android 6
I am completely clueless on how to solve this issue. I've been sitting and researching about this since 2 days now with no luck
Click to expand...
Click to collapse
You do have a J710FN right. Even though the downloaded one is Android 6 it has got variants as Samsung provides updations frequently. J710FXXU2APK6 is my current basaeband version. If I try to flash an update below this version it shows the same error. So do check your current version and try flashing an update above that.

Jezwn said:
You do have a J710FN right. Even though the downloaded one is Android 6 it has got variants as Samsung provides updations frequently. J710FXXU2APK6 is my current basaeband version. If I try to flash an update below this version it shows the same error. So do check your current version and try flashing an update above that.
Click to expand...
Click to collapse
Hey,
I tried a firmware of SM-J710F instead of SM-J710FN and odin worked.
I got official full stock ROM.
But issue is the boot screen when you first switch on the phone. It is still of the previous custom ROM Supernova. So it appears as "Samsung S8" Because of the custom ROM
Even though I flashed complete firmware through Odin the S8 did not return to stock
I am on complete stock with no root now
How to change the first boot image back to J7?
Thanks in advance

jumbobombo said:
Hey,
I tried a firmware of SM-J710F instead of SM-J710FN and odin worked.
I got official full stock ROM.
But issue is the boot screen when you first switch on the phone. It is still of the previous custom ROM Supernova. So it appears as "Samsung S8" Because of the custom ROM
Even though I flashed complete firmware through Odin the S8 did not return to stock
I am on complete stock with no root now
How to change the first boot image back to J7?
Thanks in advance
Click to expand...
Click to collapse
Are you sure you're on J710FN? The problem with the boot image would be that the ROM you're saying stock is a custom one with the S8 boot image. Try wiping all your data including David cache and flash the ROM again. If it's still the same root your phone and change the boot image.

Downgrade from Nougat 7 to Oreo 8 G955FD

First thing i searched everywhere and find out am the only one with this problem....
The problem start after Oreo update first with random restarts and finally freezing screen.
i am now on Oreo update U4 september and the phone is very unstable with rabdom restarts and freezing on a black screen THAT EVEN DONT RESPOND TO FORCE RESTART !!!
So i need to wate till the phone loss all is battery then charging it, power it on to be able to flash official rom again and agian everytime this happen.
the phone can hold sometimes for 400-600 hours after flashing the offical rom and the the problem occure again
i start to believe theres something wrong with Oreo on this phone..So the last thing to do to make sure there is nothing wrong with Hardware i need to Downgrade to Nougat 7 but when i do that using Oden (flashing AP and BL) it show me error ..So i hope someone can help me with another method to downgrade to Nougate or even figure out whats the main problem that cause all this...
sorry for my bad english hope you can help

heider.raheem said:
First thing i searched everywhere and find out am the only one with this problem....
The problem start after Oreo update first with random restarts and finally freezing screen.
i am now on Oreo update U4 september and the phone is very unstable with rabdom restarts and freezing on a black screen THAT EVEN DONT RESPOND TO FORCE RESTART !!!
So i need to wate till the phone loss all is battery then charging it, power it on to be able to flash official rom again and agian everytime this happen.
the phone can hold sometimes for 400-600 hours after flashing the offical rom and the the problem occure again
i start to believe theres something wrong with Oreo on this phone..So the last thing to do to make sure there is nothing wrong with Hardware i need to Downgrade to Nougat 7 but when i do that using Oden (flashing AP and BL) it show me error ..So i hope someone can help me with another method to downgrade to Nougate or even figure out whats the main problem that cause all this...
sorry for my bad english hope you can help
Click to expand...
Click to collapse
Since your on bootloader version 4 (u4) you won't be able to downgrade to nougat which is why you are getting errors in Odin. When flashing firmware do you use CSC or home CSC.
Not sure if it's hardware related or not but if you are getting up to 400 - 600 hrs out of it I would say it:s software related. There are some apps on playstore for hardware test to try if you like. One issue I have had is the processor running to hot and causes me some issues to the point you can't do anything until it cools down.

spawnlives said:
Since your on bootloader version 4 (u4) you won't be able to downgrade to nougat which is why you are getting errors in Odin. When flashing firmware do you use CSC or home CSC.
Not sure if it's hardware related or not but if you are getting up to 400 - 600 hrs out of it I would say it:s software related. There are some apps on playstore for hardware test to try if you like. One issue I have had is the processor running to hot and causes me some issues to the point you can't do anything until it cools down.
Click to expand...
Click to collapse
i use Home CSC ... and i am sure its not the heat that cause the freezing its happen even when device cool.... This weird behavior doesnt have a constant form... most of the time the freezing happen during the first few minuts during setup device ...FORGET TO MENTION ....in TWRP recovery the device is feeling very well and run smooth without any issue at all... is there something to do now in your openion can solve this?
and if not... what samsung can do for the device to bring it life again?... thanks for your replays

heider.raheem said:
i use Home CSC ... and i am sure its not the heat that cause the freezing its happen even when device cool.... This weird behavior doesnt have a constant form... most of the time the freezing happen during the first few minuts during setup device ...FORGET TO MENTION ....in TWRP recovery the device is feeling very well and run smooth without any issue at all... is there something to do now in your openion can solve this?
and if not... what samsung can do for the device to bring it life again?... thanks for your replays
Click to expand...
Click to collapse
I would think if it is hardware related than the issues would also happen in recovery and/or download mode. I have heard of other people having issues when flashing firmware with home CSC.
Some things I would personally try are:
1. You could try smart switch and check for latest firmware or recovery option.
2. Run in safe mode see if that makes a difference
3. In recovery wipe cache/dalvik and reboot
4. In recovery factory reset
5. Flash firmware again with CSC not home CSC.
Problems with options 1,4,5 is you will need to backup your apps and data etc. Option 5 you will have to reinstall twrp.
These options aren't in any order so I would start with 3 first see how it goes then 2 see how it goes then ,1,4 and 5 and see how it goes for each step.
Let me know how it goes

spawnlives said:
I would think if it is hardware related than the issues would also happen in recovery and/or download mode. I have heard of other people having issues when flashing firmware with home CSC.
Some things I would personally try are:
1. You could try smart switch and check for latest firmware or recovery option.
2. Run in safe mode see if that makes a difference
3. In recovery wipe cache/dalvik and reboot
4. In recovery factory reset
5. Flash firmware again with CSC not home CSC.
Problems with options 1,4,5 is you will need to backup your apps and data etc. Option 5 you will have to reinstall twrp.
These options aren't in any order so I would start with 3 first see how it goes then 2 see how it goes then ,1,4 and 5 and see how it goes for each step.
Let me know how it goes
Click to expand...
Click to collapse
Actually steps 1,3,4,5 all have been tried before without making difference but i never tried to run in safe mode (step 2)... i should tried it.... but now i cant cause one of the freezing form and the most occuring one is when blue screen with android logo at the center that appear befor the samsung logo (trying to erasing data befor the first boot after flashing a new rom)...so i have to download a nother oreo firmware from sammobile to make it run ...sorry if i make it complicated for you but this is how my device acting very weird....
Do you think its somthing wrong with Oreo in this s8+ that can be solved when downgraded to Nougat or Upgaraded to Pie maybe?

heider.raheem said:
Actually steps 1,3,4,5 all have been tried before without making difference but i never tried to run in safe mode (step 2)... i should tried it.... but now i cant cause one of the freezing form and the most occuring one is when blue screen with android logo at the center that appear befor the samsung logo (trying to erasing data befor the first boot after flashing a new rom)...so i have to download a nother oreo firmware from sammobile to make it run ...sorry if i make it complicated for you but this is how my device acting very weird....
Do you think its somthing wrong with Oreo in this s8+ that can be solved when downgraded to Nougat or Upgaraded to Pie maybe?
Click to expand...
Click to collapse
Just curious what firmware version are you using.

spawnlives said:
Just curious what firmware version are you using.
Click to expand...
Click to collapse
i use now Oreo G955FXXU4CRI5

heider.raheem said:
i use now Oreo G955FXXU4CRI5
Click to expand...
Click to collapse
Is it working ok or still same problem

spawnlives said:
Is it working ok or still same problem
Click to expand...
Click to collapse
its froze right now it cant even get to samsung logo...and even if i flash the ROM again and get it work it will freez after maximum 600 hours (thats happened 3 times)