Database Users

[Q] Samsung galaxy GT-I9500 that no one can repair!

Hi guys
I really hope someone can help me here as i am reaching dead ends on every door i knock:
I bought a new samsung galaxy S4 GT-I9500 in September 2013 from an ebay seller using paypal, and it was working for 2 weeks no problems at all.
I suddenly charged it once and then after pressing the switch on button, it got stuck at the SAMSUNG boot logo.
I didn't panic because i am sure there is always a way or a flashing technique that fixes these issues (like apple or other devices)
I asked around and some wonderful people in this forum guided me into the use of Odin, i tried many stock firmware but in vain. I did this in different ways too (got some guidance from one of the moderators here and we both got convinced that the flashing was successful but the phone still doesn't boot)
So after everything we tried, i thought i should return it to samsung (London , stratford smart centre). I was shocked to discover that they don't accept to look at it because they said it originated from South africa. Therefore even the existing warranty won't be valid.
I thought i will try contacting the samsung customer services in UK and the response was the same (email and phone)
I then went to look for a good repair company and i end up visiting The geek squad (part of carphone warehouse), they took the phone for a week then they said we cannot repair without giving me a precise reason. I am guessing they didn't try anything since they discovered it originates from South africa.
I called one or two other repair companies but the same answer too.
Finally, i emailed South africa Samsung and the answer was even more shocking. They said it doesn't have an international warranty as the device was not purchased thru the correct channels within the South african market!
My question is, can a device like this be unrepairable? does anyone know any repair shop in the area of London or in England that can deal with samsung galaxy S4 not booting bearing in mind it's a GT-I9500 and not GT-I9505?
I was thinking to send it to South africa but not after the email i received from them
many thanks in advance
Karim

krihoum said:
Hi guys
I really hope someone can help me here as i am reaching dead ends on every door i knock:
I bought a new samsung galaxy S4 GT-I9500 in September 2013 from an ebay seller using paypal, and it was working for 2 weeks no problems at all.
I suddenly charged it once and then after pressing the switch on button, it got stuck at the SAMSUNG boot logo.
I didn't panic because i am sure there is always a way or a flashing technique that fixes these issues (like apple or other devices)
I asked around and some wonderful people in this forum guided me into the use of Odin, i tried many stock firmware but in vain. I did this in different ways too (got some guidance from one of the moderators here and we both got convinced that the flashing was successful but the phone still doesn't boot)
So after everything we tried, i thought i should return it to samsung (London , stratford smart centre). I was shocked to discover that they don't accept to look at it because they said it originated from South africa. Therefore even the existing warranty won't be valid.
I thought i will try contacting the samsung customer services in UK and the response was the same (email and phone)
I then went to look for a good repair company and i end up visiting The geek squad (part of carphone warehouse), they took the phone for a week then they said we cannot repair without giving me a precise reason. I am guessing they didn't try anything since they discovered it originates from South africa.
I called one or two other repair companies but the same answer too.
Finally, i emailed South africa Samsung and the answer was even more shocking. They said it doesn't have an international warranty as the device was not purchased thru the correct channels within the South african market!
My question is, can a device like this be unrepairable? does anyone know any repair shop in the area of London or in England that can deal with samsung galaxy S4 not booting bearing in mind it's a GT-I9500 and not GT-I9505?
I was thinking to send it to South africa but not after the email i received from them
many thanks in advance
Karim
Click to expand...
Click to collapse
anyone can recommend a good "hardware" repair shop in England?
thanks

krihoum said:
anyone can recommend a good "hardware" repair shop in England?
thanks
Click to expand...
Click to collapse
You might wanna describe your flashing process, otherwise there won't be anybody who can help you. I doubt that this is a hardware related issue...

RobHands said:
You might wanna describe your flashing process, otherwise there won't be anybody who can help you. I doubt that this is a hardware related issue...
Click to expand...
Click to collapse
ok i will try to do my best to describe what i have done because i did many flashing:
The first ones i tried were suggested by a moderator here:
-install philz recovry, do the wipe, reboot
-install philz recovery, format system, flash your stock firmware (untick "auto-reboot", when it say "pass", remove battery, insert it, wipe data and cache in recovery, reboot.
- flash pit file alone.
- flash pit file with the stock firmware.
(stock firmware i used was from germany because at that time i didn't know the phone originated from South africa:
Germany MBC (May 2013)
PDA: I9500XXUAMDK
CSC: I9500MBCAMD6
Version 4.2.2)
Then i tried a different stock firmware from russia but still didn't work
Later i tried the south africa firmware but still didnt work
Finally i tried the flashing using sboot.tar in odin as pda (the file attached in my thread http://forum.xda-developers.com/show....php?t=2265477)
and that didn't work as well
My flashing technique was based on this forum here and i used it with on a computer with windows XP loaded with KIES software (samsung drivers available), using ODIN 3.07. I leave the checkboxes untouched, i.e. AUTOREBOOT & F. RESET TIME checked only. The ID:COM box on ODIN turning blue once the phone is connected.
I click on PDA to select the file or stock rom i flash with, then when the file path is shown and the software is ready i hit START and after few minutes, the flashing completes, making the phone reboot and i see the GREEN label on ODIN stating PASS. Never had any error message
However, the phone doesn't pass the boot logo
I am always willing to do more tests and try any suggestion you can think of
many thanks
Karim

krihoum said:
ok i will try to do my best to describe what i have done because i did many flashing:
The first ones i tried were suggested by a moderator here:
-install philz recovry, do the wipe, reboot
-install philz recovery, format system, flash your stock firmware (untick "auto-reboot", when it say "pass", remove battery, insert it, wipe data and cache in recovery, reboot.
- flash pit file alone.
- flash pit file with the stock firmware.
(stock firmware i used was from germany because at that time i didn't know the phone originated from South africa:
Germany MBC (May 2013)
PDA: I9500XXUAMDK
CSC: I9500MBCAMD6
Version 4.2.2)
Then i tried a different stock firmware from russia but still didn't work
Later i tried the south africa firmware but still didnt work
Finally i tried the flashing using sboot.tar in odin as pda (the file attached in my thread http://forum.xda-developers.com/show....php?t=2265477)
and that didn't work as well
My flashing technique was based on this forum here and i used it with on a computer with windows XP loaded with KIES software (samsung drivers available), using ODIN 3.07. I leave the checkboxes untouched, i.e. AUTOREBOOT & F. RESET TIME checked only. The ID:COM box on ODIN turning blue once the phone is connected.
I click on PDA to select the file or stock rom i flash with, then when the file path is shown and the software is ready i hit START and after few minutes, the flashing completes, making the phone reboot and i see the GREEN label on ODIN stating PASS. Never had any error message
However, the phone doesn't pass the boot logo
I am always willing to do more tests and try any suggestion you can think of
many thanks
Karim
Click to expand...
Click to collapse
I would suggest you try other recovery for i9500 like TWRP or CWM and then try flashing.
Have you tried flash custom ROM based on touchwiz?
When flashing PIT-file did you check "re-partition"?

RobHands said:
I would suggest you try other recovery for i9500 like TWRP or CWM and then try flashing.
Have you tried flash custom ROM based on touchwiz?
When flashing PIT-file did you check "re-partition"?
Click to expand...
Click to collapse
i dont think i have tried those but i am willing to try anything
can i find those you mentioned in this forum? do i need to pay attention to the the version type suitable for my 9500?
many thanks

krihoum said:
i dont think i have tried those but i am willing to try anything
can i find those you mentioned in this forum? do i need to pay attention to the the version type suitable for my 9500?
many thanks
Click to expand...
Click to collapse
First you should try flashing pit file again with "re-partition" checked and the stock firmware from south africa
If that don't work, try flashing wanam's rom for GT-i9500 (http://forum.xda-developers.com/showthread.php?t=2268569), with cwm (http://downloadandroidrom.com/file/GalaxyS4/GT-i9500/recovery/cofface_I9500_cwm_recovery_en_new.tar). He also has a possible solution if device gets stuck in bootloop, you might try that

RobHands said:
First you should try flashing pit file again with "re-partition" checked and the stock firmware from south africa
If that don't work, try flashing wanam's rom for GT-i9500 (http://forum.xda-developers.com/showthread.php?t=2268569), with cwm (http://downloadandroidrom.com/file/GalaxyS4/GT-i9500/recovery/cofface_I9500_cwm_recovery_en_new.tar). He also has a possible solution if device gets stuck in bootloop, you might try that
Click to expand...
Click to collapse
i will try these 2 solutions tomorrow from my work place because at home my laptop with windows 7 doesn't recognise the samsung driver for some reason
Just one question: the second solution is based on the memory card , because i don't have any way to access the files on the phone, is that correct?

krihoum said:
i will try these 2 solutions tomorrow from my work place because at home my laptop with windows 7 doesn't recognise the samsung driver for some reason
Just one question: the second solution is based on the memory card , because i don't have any way to access the files on the phone, is that correct?
Click to expand...
Click to collapse
If you install cwm recovery you can mount the phone storage so you can access it from your pc.

RobHands said:
If you install cwm recovery you can mount the phone storage so you can access it from your pc.
Click to expand...
Click to collapse
Excellent
i will try both methods and i let you know, i really appreciate
One thing i noticed is that no 32GB pit is available for the i9500, can I assume we just need to use the 16gb then?

krihoum said:
Excellent
i will try both methods and i let you know, i really appreciate
One thing i noticed is that no 32GB pit is available for the i9500, can I assume we just need to use the 16gb then?
Click to expand...
Click to collapse
I did the pit + latest south african rom with re-partition checked and it didn't do anything
(I found only pit for 16gb )
I am doing the second suggestion, i installed the latest CWM 6.0.4.5 and started by wipe data/factory reset
I went to mounts and storage but i guess i cannot mount the phone itself but rather the memory card
I wait until i go home and i use the card loaded with the rom
I hope i am doing this right
many thanks

krihoum said:
I did the pit + latest south african rom with re-partition checked and it didn't do anything
(I found only pit for 16gb )
I am doing the second suggestion, i installed the latest CWM 6.0.4.5 and started by wipe data/factory reset
I went to mounts and storage but i guess i cannot mount the phone itself but rather the memory card
I wait until i go home and i use the card loaded with the rom
I hope i am doing this right
many thanks
Click to expand...
Click to collapse
i have managed to install the wanamlite rom using a memory card loaded with the zip file but although it was successfully installed thru CWM, when i rebooted it has the same symptoms. i.e. samsung galaxy s4 9500 logo then followed by white samsung logo (with interrupted music), then stuck there. i also did re-partition using adonis.pit + stock firmware, then flashed CWM, the wanamlite rom, but in vain.
Am i doing something wrong? or maybe the phone is very much bricked?
any help or suggestion is very much appreciated
thanks

Tried with Kies? There's a procedure that revive your phone.. Once i almost got bricked and I can't do nothing except attaching device to usb port and press a button in Kies.. I don't remember the name... It was like a flash on the fly
Inviato dal mio GT-I9505G con Tapatalk 2

PacStealer said:
Tried with Kies? There's a procedure that revive your phone.. Once i almost got bricked and I can't do nothing except attaching device to usb port and press a button in Kies.. I don't remember the name... It was like a flash on the fly
Inviato dal mio GT-I9505G con Tapatalk 2
Click to expand...
Click to collapse
I will check this later but doubt it KIES has a solution for this problem
i am getting desperate to be honest, not sure where to go and what to do, especially it's a new phone used between sep 17 and october 1

krihoum said:
Excellent
i will try both methods and i let you know, i really appreciate
One thing i noticed is that no 32GB pit is available for the i9500, can I assume we just need to use the 16gb then?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2269941 (try to use the adonis pit-file from this thread)

RobHands said:
http://forum.xda-developers.com/showthread.php?t=2269941 (try to use the adonis pit-file from this thread)
Click to expand...
Click to collapse
Ok
i will try this again tonight and i will let you know
i will try any other rom if you think they are custom and might work differently

krihoum said:
I will check this later but doubt it KIES has a solution for this problem
i am getting desperate to be honest, not sure where to go and what to do, especially it's a new phone used between sep 17 and october 1
Click to expand...
Click to collapse
go to instruments, and then emergency firmware restore

PacStealer said:
go to instruments, and then emergency firmware restore
Click to expand...
Click to collapse
can't see my phone in KIES for some reason
could be because it's stuck in boot and not being recognised? It keeps saying connecting......
wonder how ODIN is seeing my phone then

krihoum said:
can't see my phone in KIES for some reason
could be because it's stuck in boot and not being recognised? It keeps saying connecting......
wonder how ODIN is seeing my phone then
Click to expand...
Click to collapse
same to me, you have to try sometimes.. try reboot or get the battery out, try to detach the cable or something, at the end it will work:good:

PacStealer said:
same to me, you have to try sometimes.. try reboot or get the battery out, try to detach the cable or something, at the end it will work:good:
Click to expand...
Click to collapse
thanks but i am starting to giving up, it looks more a hardware failure than software

SM-N9005 Kitkat 4.4.3 failed

After updating my phone to the new firmware N9005XXUENA6_N9005OXXENA5_XEO.zip my phone failed to flash using Odin. I have tried so many version of Odin and still no luck, i have basically downloaded every rom that i can find from samsung-updates.com and still no luck. Let me know if you guys have a for fix for this because as of right now i can boot into Odin Mode but when i try to flash it via Odin 3.09 on any Rom it will fail. And yes i have tried every Samsung Kies version to try initialize this phone but it just does not work. i have attached the image of my S/N and Model this is one of the HK version and yes i tried the HK TGY rom and still no luck.

con2vp1 said:
After updating my phone to the new firmware N9005XXUENA6_N9005OXXENA5_XEO.zip my phone failed to flash using Odin. I have tried so many version of Odin and still no luck, i have basically downloaded every rom that i can find from samsung-updates.com and still no luck. Let me know if you guys have a for fix for this because as of right now i can boot into Odin Mode but when i try to flash it via Odin 3.09 on any Rom it will fail. And yes i have tried every Samsung Kies version to try initialize this phone but it just does not work. i have attached the image of my S/N and Model this is one of the HK version and yes i tried the HK TGY rom and still no luck.
Click to expand...
Click to collapse
Well if you can still get into download mode you are still safe.
Does it fail mid flash or can´t even recognize your phone?

Reboot your pc and try again.

It will fail on the ABOOT, and i have tried to reboot my pc and still no luck i have attached my model of the phone

con2vp1 said:
It will fail on the ABOOT, and i have tried to reboot my pc and still no luck i have attached my model of the phone
Click to expand...
Click to collapse
Try this guide. It seems to be the same phone as yours.

If you are trying to go back to 4.3 from 4.4.2 then it won't be possible. You will now have to stay in KitKat only and wait for more ROM for KitKat.
Sent from my SM-N900 using Tapatalk

Did you try flashing with update bootloader ticked? If you tried that already then I think you are going to have to wait for the hk version of kit Kat for your phone to work again.
Or try this..... http://forum.xda-developers.com/showthread.php?t=null
Sent from my SM-N9005 using Tapatalk

odin 3.09 tick Phone boot loader update.

hey_joe said:
Try this guide. It seems to be the same phone as yours.
Click to expand...
Click to collapse
which one should i download the .zip or the .rar and they two different file size

con2vp1 said:
which one should i download the .zip or the .rar and they two different file size
Click to expand...
Click to collapse
Both are same.
Rar is just better compressed. I went with it.

Just an idea make sure reactivation lock is not ticked in settings
Sent from my SM-N9005 using xda app-developers app

rcp27 said:
Just an idea make sure reactivation lock is not ticked in settings
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Its not ticked, i might just have to wait to an HK firmware to update this because any other i have tried is not working and it says PIT FAIL when i try this solution http://forum.xda-developers.com/showthread.php?t=2613374. even though i followed the instructions step by step.
Is there another way to flash my device other than Odin? and yes ADB does not work

con2vp1 said:
Its not ticked, i might just have to wait to an HK firmware to update this because any other i have tried is not working and it says PIT FAIL when i try this solution http://forum.xda-developers.com/showthread.php?t=2613374. even though i followed the instructions step by step.
Is there another way to flash my device other than Odin? and yes ADB does not work
Click to expand...
Click to collapse
Can you screenshot your odin configuration that you flashed and post it here?

FeralFire said:
Can you screenshot your odin configuration that you flashed and post it here?
Click to expand...
Click to collapse
This is the Odin config and after the CSC was only applied the phone says PIT FAIL

con2vp1 said:
This is the Odin config and after the CSC was only applied the phone says PIT FAIL
Click to expand...
Click to collapse
Hmm.
Weird.
Do you know how to use heimdall?
Use it to have a look at your pit file and compare it to the one in the CSC zip. See what all is different.
Or just post your pit here.
EDIT: Just noticed that you have a 16GB version. I don't know how to help you there, man. You need a completely different pit file. One that is designed for 16GB. But since that model was only launched in Hong Kong, I don't think you will find one from outside, unless somebody can make one specifically for you. I have been trying to learn to do that, but as of yet, I can't.
Without a proper pit file, your only options are either wait for the Hong Kong Kitkat version or try installing the Sweet ROM.

con2vp1 said:
After updating my phone to the new firmware N9005XXUENA6_N9005OXXENA5_XEO.zip my phone failed to flash using Odin. I have tried so many version of Odin and still no luck, i have basically downloaded every rom that i can find from samsung-updates.com and still no luck. Let me know if you guys have a for fix for this because as of right now i can boot into Odin Mode but when i try to flash it via Odin 3.09 on any Rom it will fail. And yes i have tried every Samsung Kies version to try initialize this phone but it just does not work. i have attached the image of my S/N and Model this is one of the HK version and yes i tried the HK TGY rom and still no luck.
Click to expand...
Click to collapse
're using Odin with Note 3 connected to a USB 3.0? if yes, try connecting it to a USB 2.0. already happened to me a few times, and the solution was this. sorry for the bad english.

FeralFire said:
Hmm.
Weird.
Do you know how to use heimdall?
Use it to have a look at your pit file and compare it to the one in the CSC zip. See what all is different.
Or just post your pit here.
Click to expand...
Click to collapse
Well thats an issue because im not sure if this my right PIT FILE for this phone. Because usually it will go smoothly for these manual updates using Odin and this is my first encountering this error. And my fault i didnt backup my ROM which i should have done first before getting excited with this KitKat for my Note 3. That CSC file i got that from this site http://forum.xda-developers.com/showthread.php?t=2613374 and just followed instructions on how to do it, but it will just give me that error when i try to apply that method. But here's the PIT file that i got from that download.
I think its on a wrong region because i got that leaked update here http://www.sammobile.com/2014/01/13...kitkat-rolling-out-to-galaxy-note-3-sm-n9005/ and it looks like from Poland? does that matter? because my Note 3 is and HK version?
I have done so many phones rooted them and install custom roms this is the first time it failed on me. And funny thing is its my own cell phone lol

con2vp1 said:
Well thats an issue because im not sure if this my right PIT FILE for this phone. Because usually it will go smoothly for these manual updates using Odin and this is my first encountering this error. And my fault i didnt backup my ROM which i should have done first before getting excited with this KitKat for my Note 3. That CSC file i got that from this site http://forum.xda-developers.com/showthread.php?t=2613374 and just followed instructions on how to do it, but it will just give me that error when i try to apply that method. But here's the PIT file that i got from that download.
I think its on a wrong region because i got that leaked update here http://www.sammobile.com/2014/01/13...kitkat-rolling-out-to-galaxy-note-3-sm-n9005/ and it looks like from Poland? does that matter? because my Note 3 is and HK version?
I have done so many phones rooted them and install custom roms this is the first time it failed on me. And funny thing is its my own cell phone lol
Click to expand...
Click to collapse
You gave me the pit file from the zip. I was asking for the one from your phone.
But anyway I found one for the 16GB version somehwere. I am taking a look at it. Will try editing it to fit your needs. Give me a little while.
And yes, it matters, because the pit file determines the sizes of the various partitions. Since yours is a 16GB version, the pit from a 32GB won't work.

View attachment Modded_16GB.tar
Try flashing this tar file. Put it in the CSC part of the Odin.
Though I can't guarantee anything. First time, I am doing anything like this.

FeralFire said:
View attachment 2520563
Try flashing this tar file. Put it in the CSC part of the Odin.
Though I can't guarantee anything. First time, I am doing anything like this.
Click to expand...
Click to collapse
Thanks
Odin just crashed on me while it was on SET PARTITION

[Q] Note 3 Lollypop Flashing Help

Hello all,
I had a galaxy note 3 (SM-N9005, 16GB Hong Kong Version) with last updated to KitKat(OTA). For the first time, i decided to take the risk of flashing the ROM manually and downloaded the Poland Lollypop Rom N9005XXUGBOA5_N9005XEOGBOA4_N9005XXUGBOA1_HOME.tar.md5 and flashed the phone using Odin with only Reset and Reboot flags checked. It failed at ext Image error.
After some reading i find out that HongKong have different partition structure and hence require to flash with a pit, i downloaded a pit file
(SM-N9005_HLTE_HKTW_OPEN_16G) from forums here and tried to re flash it with Reset, Reboot and Repartition flags and this time it stucks at error
PIT Fail : Total Sectors (38777344). I can now only boot up in download mode.
Can anyone let me know is there any chance, whether i can bring my phone back to life.

spandita said:
Hello all,
I had a galaxy note 3 (SM-N9005, 16GB Hong Kong Version) with last updated to KitKat(OTA). For the first time, i decided to take the risk of flashing the ROM manually and downloaded the Poland Lollypop Rom N9005XXUGBOA5_N9005XEOGBOA4_N9005XXUGBOA1_HOME.tar.md5 and flashed the phone using Odin with only Reset and Reboot flags checked. It failed at ext Image error.
After some reading i find out that HongKong have different partition structure and hence require to flash with a pit, i downloaded a pit file
(SM-N9005_HLTE_HKTW_OPEN_16G) from forums here and tried to re flash it with Reset, Reboot and Repartition flags and this time it stucks at error
PIT Fail : Total Sectors (38777344). I can now only boot up in download mode.
Can anyone let me know is there any chance, whether i can bring my phone back to life.
Click to expand...
Click to collapse
It sounds like you tried to reflash the HK PIT file - what you actually need is a PIT to suit the firmware you want to flash. If you use the HK pit you need to flash a HK ROM.
Also, make sure you actually pull the battery to get into Download mode. i.e. take out battery, wait 10 secs, then put it in and hold down the keys for DL mode. Restarts don't seem to work properly when flashing BL's and Modems so the physical method is needed.
Start by getting the latest HK version and see if Odin will flash it. THEN look at getting a EU pit file to go with BOA5.

Journyman16 said:
It sounds like you tried to reflash the HK PIT file - what you actually need is a PIT to suit the firmware you want to flash. If you use the HK pit you need to flash a HK ROM.
Also, make sure you actually pull the battery to get into Download mode. i.e. take out battery, wait 10 secs, then put it in and hold down the keys for DL mode. Restarts don't seem to work properly when flashing BL's and Modems so the physical method is needed.
Start by getting the latest HK version and see if Odin will flash it. THEN look at getting a EU pit file to go with BOA5.
Click to expand...
Click to collapse
Thanks for reply!!
Yes, it makes sense. So, i am going to download the Hongkong firmware. Will try it and let you know if i got any luck in bringing it up

spandita said:
Thanks for reply!!
Yes, it makes sense. So, i am going to download the Hongkong firmware. Will try it and let you know if i got any luck in bringing it up
Click to expand...
Click to collapse
I had a HK S3 and had similar problems. Not sure why Samsung makes them so different. I was new to Androids and thought I had trashed my new phone.
But it's a good way to learn - first you find out what has gone wrong and then how to fix it and before you know it, you are on your way to being flash-addicted.

Thank you
@Journyman16 Thank you very much :victory:, i got my phone up again with the hong kong firmware .... I was also looking for pit file for lollipop polland firmware, but didnt find anyone specific to 16gb note...
Can you direct me to some good resource from where i can go through tit bits of flashing? Particularly regarding this numbering system of Android basebands
As you mentioned, i like the whole incident(Learned something new) .... and dont want to gie up on getting lollipop :highfive:

spandita said:
@Journyman16 Thank you very much :victory:, i got my phone up again with the hong kong firmware .... I was also looking for pit file for lollipop polland firmware, but didnt find anyone specific to 16gb note...
Can you direct me to some good resource from where i can go through tit bits of flashing? Particularly regarding this numbering system of Android basebands
As you mentioned, i like the whole incident(Learned something new) .... and dont want to gie up on getting lollipop :highfive:
Click to expand...
Click to collapse
Been a while since I looked at such things but search in Q&A as well as Android Development for things like 'root guide' or perhaps click on the Advanced Search button and look for 'guide' in post headings.
Also as you browse the subjects that interest you there are often links out to tutorials etc. - another reason for always reading a thread before posting.
Good luck on the journey...

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!

What firmware files do I need to complete reflash my Note 4 SM-N910F?

I got a bricked Samsung Galaxy Note 4 (910F) vodafone branded.
it's totally broken I can't start it, can't go into recovery (the hardware buttons are OK).
I can only go into download mode.
tried flashing everything with odin back to stock. followed many different instructions and now I'm lost.
can someone tell me what exact files I need?
I think I have the right firmware downloaded BUT what about the bootloader? on sammobile under germany-vodafone there are so many different versions which one shall I choose?
AND: Do I need CSC? if so which one and where to find? Couldn't find it on sammobile.
And am I right with putting the bootloader under BL, the firmware under AP, the CP (whatever this is) under CP, the csc under csc?
repartition unchecked as I read somewhere.
I still don't understand what this "pit" file is for and I'm not sure if I have the right one.. never had a phone with sooo many different firmware files..
I'm used to flash via fastboot "recovery.img, boot.img, system.img" odin is a new thing for me
HELP PLEASEEE :'(
the reactivation lock is on.

nekrosmsk said:
I got a bricked Samsung Galaxy Note 4 (910F) vodafone branded.
it's totally broken I can't start it, can't go into recovery (the hardware buttons are OK).
I can only go into download mode.
tried flashing everything with odin back to stock. followed many different instructions and now I'm lost.
can someone tell me what exact files I need?
I think I have the right firmware downloaded BUT what about the bootloader? on sammobile under germany-vodafone there are so many different versions which one shall I choose?
AND: Do I need CSC? if so which one and where to find? Couldn't find it on sammobile.
And am I right with putting the bootloader under BL, the firmware under AP, the CP (whatever this is) under CP, the csc under csc?
repartition unchecked as I read somewhere.
I still don't understand what this "pit" file is for and I'm not sure if I have the right one.. never had a phone with sooo many different firmware files..
I'm used to flash via fastboot "recovery.img, boot.img, system.img" odin is a new thing for me
HELP PLEASEEE :'(
the reactivation lock is on.
Click to expand...
Click to collapse
The note 4 firmware is usually only 1 file that contains all you need. It contains the bootloader and CSC that you pick during download. Just pick the CSC for your country.
This is unless you get a 4 file repair firmware, which contains separate bootloader, system, and CSC files.
The pit file is only needed to repartition your device.
But with all off that aside, you state that your activation lock is activated. These means the phone was password protected.
If you tell me your country, I can at least point you to the correct firmware. So at least you'll know you got the correct one.
But as far as the activation lock, I can't help with that. "Google"
Edit. I now see you mentioned Germany Voda.
So here's the most current firmware for your device.
https://fws03.updato.com/GALAXYNOTE4/SM-N910F/TCL/SM-N910F_1_20171228192640_l5rw6mqv67.zip
Download and unzip.
Then if it's just 1 file that's .md5 then you put it in AP slot.
If it's 4 files put them in appropriate slots.

aaron74 said:
The note 4 firmware is usually only 1 file that contains all you need. It contains the bootloader and CSC that you pick during download. Just pick the CSC for your country.
This is unless you get a 4 file repair firmware, which contains separate bootloader, system, and CSC files.
The pit file is only needed to repartition your device.
But with all off that aside, you state that your activation lock is activated. These means the phone was password protected.
If you tell me your country, I can at least point you to the correct firmware. So at least you'll know you got the correct one.
But as far as the activation lock, I can't help with that. "Google"
Edit. I now see you mentioned Germany Voda.
So here's the most current firmware for your device.
https://fws03.updato.com/GALAXYNOTE4/SM-N910F/TCL/SM-N910F_1_20171228192640_l5rw6mqv67.zip
Download and unzip.
Then if it's just 1 file that's .md5 then you put it in AP slot.
If it's 4 files put them in appropriate slots.
Click to expand...
Click to collapse
This reactivation lock doesn't matter I found a solution how to bypass it when the phone is set up running android.
my question is, is it possible to flash firmware to the note4 at all with reactivation lock on? Or is that just an android thingy?
And yes please that would be nice if you show me the right firmware.
My model:
N910F GSMH
I believe it is vodafone branded because when it once worked it showed a vodafone logo while starting up.
my country is Germany.
I hope thats enough info :/

nekrosmsk said:
This reactivation lock doesn't matter I found a solution how to bypass it when the phone is set up running android.
my question is, is it possible to flash firmware to the note4 at all with reactivation lock on? Or is that just an android thingy?
And yes please that would be nice if you show me the right firmware.
My model:
N910F GSMH
I believe it is vodafone branded because when it once worked it showed a vodafone logo while starting up.
my country is Germany.
I hope thats enough info :/
Click to expand...
Click to collapse
I believe it should still flash with lock. If it isn't flashing something is wrong.
If you can't get Odin to flash that firmware try this and see what happens.
Download TWRP and flash it. Can you boot into recovery then? If so download a custom rom and flash it and see what happens.
TWRP: https://eu.dl.twrp.me/trlte/twrp-3.2.1-0-trlte.img.tar
Do you have Samsung drivers installed on PC? http://developer.samsung.com/common/download/check.do?actId=698
Do you have a good Odin? https://dl.sammobile.com/Odin3-v3.13.1.zip

aaron74 said:
I believe it should still flash with lock. If it isn't flashing something is wrong.
If you can't get Odin to flash that firmware try this and see what happens.
Download TWRP and flash it. Can you boot into recovery then? If so download a custom rom and flash it and see what happens.
TWRP: https://eu.dl.twrp.me/trlte/twrp-3.2.1-0-trlte.img.tar
Do you have Samsung drivers installed on PC? http://developer.samsung.com/common/download/check.do?actId=698
Do you have a good Odin? https://dl.sammobile.com/Odin3-v3.13.1.zip
Click to expand...
Click to collapse
I have the right latest samsung drivers installed yes.
I have the Odin version you just sent a link of. ( I also tried different older versions but no success).
I can't boot into recovery doesn't work. the hardware buttons are 100% working as I have to press vol+ to confirm to go into download mode.
I tried flashing TWRP and CWM both didn't work "custom recovery blocked by A/L error".
I can successfully flash firmware with Odin. It says "PASS" and then the phone reboots and is stuck on Samsung Logo. and sometimes it just shows blue text "recovery booting" but is stuck. nothing happens.

nekrosmsk said:
This reactivation lock doesn't matter I found a solution how to bypass it when the phone is set up running android.
my question is, is it possible to flash firmware to the note4 at all with reactivation lock on? Or is that just an android thingy?
And yes please that would be nice if you show me the right firmware.
My model:
N910F GSMH
I believe it is vodafone branded because when it once worked it showed a vodafone logo while starting up.
my country is Germany.
I hope thats enough info :/
Click to expand...
Click to collapse
Hey sorry the link you've sent doesn't work :/

aaron74 said:
The note 4 firmware is usually only 1 file that contains all you need. It contains the bootloader and CSC that you pick during download. Just pick the CSC for your country.
This is unless you get a 4 file repair firmware, which contains separate bootloader, system, and CSC files.
The pit file is only needed to repartition your device.
But with all off that aside, you state that your activation lock is activated. These means the phone was password protected.
If you tell me your country, I can at least point you to the correct firmware. So at least you'll know you got the correct one.
But as far as the activation lock, I can't help with that. "Google"
Edit. I now see you mentioned Germany Voda.
So here's the most current firmware for your device.
https://fws03.updato.com/GALAXYNOTE4/SM-N910F/TCL/SM-N910F_1_20171228192640_l5rw6mqv67.zip
Download and unzip.
Then if it's just 1 file that's .md5 then you put it in AP slot.
If it's 4 files put them in appropriate slots.
Click to expand...
Click to collapse
hey thanks in advance, but this link doesnt work it says "hotlinking is not cool". anyways I searched the firmware for my model number on this site and applied the "germany vodafone" filter. but there are still soo many different entries which one shall I choose? The latest date?

nekrosmsk said:
hey thanks in advance, but this link doesnt work it says "hotlinking is not cool". anyways I searched the firmware for my model number on this site and applied the "germany vodafone" filter. but there are still soo many different entries which one shall I choose? The latest date?
Click to expand...
Click to collapse
Here's webpage
https://updato.com/firmware-archive-select-model?record=58770125168D11E89F15FA163EE8F90B
After you flash, how long are you waiting for it to boot?
Sometimes it takes awhile.

aaron74 said:
Here's webpage
https://updato.com/firmware-archive-select-model?record=58770125168D11E89F15FA163EE8F90B
After you flash, how long are you waiting for it to boot?
Sometimes it takes awhile.
Click to expand...
Click to collapse
Thanks for the link I'm downloading.
After flashing odin says PASS and my note 4 reboots. then there are 2 cases which in my view appear randomly. Either it shows the samsung logo and is stuck.
OR it shows the samsung logo and a blue little text in the upper left corner saying "recovery booting" and is stuck. I waited like 5 minutes. shall I wait longer? :/ hm..I'll try
OH and sometimes the screen just goes black idk if it really turns off after getting stuck on samsung logo.

Pull the battery, leave it out for 10+ minutes
Put battery back in
Boot to download mode (Power + Vol Down + Home)
Then try (re)flashing stock ROM via odin, i would try the earliest you can find to have the best chance, you can always flash a later one if you get it running
Better range of ROMS from sammobile, i never use updato for that reason: https://www.sammobile.com/firmwares/galaxy-note4/SM-N910F/VD2/
If none of that works, then its likely you have a hardware fault ...emmc or other

stylemessiah said:
Pull the battery, leave it out for 10+ minutes
Put battery back in
Boot to download mode (Power + Vol Down + Home)
Then try (re)flashing stock ROM via odin, i would try the earliest you can find to have the best chance, you can always flash a later one if you get it running
Better range of ROMS from sammobile, i never use updato for that reason: https://www.sammobile.com/firmwares/galaxy-note4/SM-N910F/VD2/
If none of that works, then its likely you have a hardware fault ...emmc or other
Click to expand...
Click to collapse
So I tried flashing. after flashing OH WONDER it said recovery booting and then it showed this green android logo thing with a rotating icon in it "you know what I mean" but then it stopped and just turned off.. I could freak out really.. I tried flashing again. same issue. I could then press the recovery mode key combo to get into this rotating android logo screen but everytime it just freezes and turns off. yes the battery is fully charged before I started flashing this firmware now. I flashed the one u said the earliest. So Now I tried the one the other guy here showed me. didn't work either. it just gets stuck at samsung logo. I found a repair firmware for my model containing (pit, bl, ap, cp, csc and odin) I flashed all but odin fails "write error". I then tried odin v3.0.7 but then it got stuck while flashing the system image. I waited like 1 hour. nothing. tried it again. nothing it freezes on the same position. I then tried the same on the latest versions of odin v3.12.3, 3.12.7 and on 3.13.1 but it also freezes on system.img.ext4 image flashing..

nekrosmsk said:
So I tried flashing. after flashing OH WONDER it said recovery booting and then it showed this green android logo thing with a rotating icon in it "you know what I mean" but then it stopped and just turned off.. I could freak out really.. I tried flashing again. same issue. I could then press the recovery mode key combo to get into this rotating android logo screen but everytime it just freezes and turns off. yes the battery is fully charged before I started flashing this firmware now. I flashed the one u said the earliest. So Now I tried the one the other guy here showed me. didn't work either. it just gets stuck at samsung logo. I found a repair firmware for my model containing (pit, bl, ap, cp, csc and odin) I flashed all but odin fails "write error". I then tried odin v3.0.7 but then it got stuck while flashing the system image. I waited like 1 hour. nothing. tried it again. nothing it freezes on the same position. I then tried the same on the latest versions of odin v3.12.3, 3.12.7 and on 3.13.1 but it also freezes on system.img.ext4 image flashing..
Click to expand...
Click to collapse
Try the Samsung Smart Switch for PC - like this : https://www.youtube.com/watch?v=9QhJngOuLQ4&t=337s
Good luck, maybe it will work - for me it did work for the 910C.

w41ru5 said:
Try the Samsung Smart Switch for PC - like this : https://www.youtube.com/watch?v=9QhJngOuLQ4&t=337s
Good luck, maybe it will work - for me it did work for the 910C.
Click to expand...
Click to collapse
doesnt work. I tried several versions of smartswitch AND samsung kies. nothing works it always says my model is not supported. I reinstalled drivers. tried on another pc. tried another usb port. yes I'm using the original stock usb cable. model not supported. But I've also read that in other threads that the 910F model seems to be unknown by kies or smartswitch. I'm rly starting to hate samsung now. I have never ever had so many problems with flashing and so on.

nekrosmsk said:
So I tried flashing. after flashing OH WONDER it said recovery booting and then it showed this green android logo thing with a rotating icon in it "you know what I mean" but then it stopped and just turned off.. I could freak out really.. I tried flashing again. same issue. I could then press the recovery mode key combo to get into this rotating android logo screen but everytime it just freezes and turns off. yes the battery is fully charged before I started flashing this firmware now. I flashed the one u said the earliest. So Now I tried the one the other guy here showed me. didn't work either. it just gets stuck at samsung logo. I found a repair firmware for my model containing (pit, bl, ap, cp, csc and odin) I flashed all but odin fails "write error". I then tried odin v3.0.7 but then it got stuck while flashing the system image. I waited like 1 hour. nothing. tried it again. nothing it freezes on the same position. I then tried the same on the latest versions of odin v3.12.3, 3.12.7 and on 3.13.1 but it also freezes on system.img.ext4 image flashing..
Click to expand...
Click to collapse
afaik the "repair" fimeware is no better than flashing a stock ROM in one file...
its startng to sound like a hardware error, if it cant even write to the dvice theres really not many (probably any) options left.
ive purposely bricked a phone and recovered it (not recommended of course), ive never had or never saw as much effort youve put in to try and recover a phone...

stylemessiah said:
afaik the "repair" fimeware is no better than flashing a stock ROM in one file...
its startng to sound like a hardware error, if it cant even write to the dvice theres really not many (probably any) options left.
ive purposely bricked a phone and recovered it (not recommended of course), ive never had or never saw as much effort youve put in to try and recover a phone...
Click to expand...
Click to collapse
me neither.. can't believe this.. how can a phone be physically damaged by flashing? paid 70 bugs for a note 4 with a software issue.. as I often do. recovered dead phones from sony, xiaomi, wiko, asus, lg, huawei etc... adb, fastboot and u good to go. odin is killin me.. gonna sell it as bricked.

Cleared caches?

R0B3RTF1SH3R said:
Cleared caches?
Click to expand...
Click to collapse
HOW? If I can't boot into recovery mode?