Database Users

Locking up straight out of the box

Just got my new i9500, turned it on and with in minute it locked up then rebooted (no sim or mem card at this stage).
Did't think much of it at the time. Went ahead and rooted it & flashed Omega rom.
Unfortunately it continues to lock up & reboot every few minutes of use. Looks like it is faulty and will have to go back for warranty. My concern is the rom counter and warranty. Will flashing a stock firmware with odin put the counter back to zero?

Flashing stock with odin will not reset Samsung's rom counter. From my understanding, there are ways to reset the counter, but you have to be very careful because it has the potential to really mess up the phone. If you flash back to stock rom and stock recovery and relock the bootloader, you will be able to exchange it wherever you bought it without an issue (assuming you are still within the 14 day period most carriers give you). No one will look that deeply into the software of the phone until it gets back to Samsung. And even then, it is not guaranteed they will check that. I'm not saying it won't happen, but the odds of you having any issues are slim.

KTM690 said:
Just got my new i9500, turned it on and with in minute it locked up then rebooted (no sim or mem card at this stage).
Did't think much of it at the time. Went ahead and rooted it & flashed Omega rom.
Unfortunately it continues to lock up & reboot every few minutes of use. Looks like it is faulty and will have to go back for warranty. My concern is the rom counter and warranty. Will flashing a stock firmware with odin put the counter back to zero?
Click to expand...
Click to collapse
Flash a Stock Firmware using Odin below is the link u can find a firmware of ur cell
http://forum.xda-developers.com/showthread.php?t=2265477&highlight=stock+firmware
after flashing a firmware again reset the device from ur cell
and i9500 has hidden counter mostly so u cant see how many flashes u have got however there isnt any way to reset also for now may be we have to wait till chainfire gets one for i9500 .. Once u flash a stock firmware it will show official hopefully they will replace it
Make sure its saying official on download mode and also in abous us / status / device status all should be official of whatever samsung writes

I have flashed a genuine firmware but it still says "Custom" when I boot into download mode.
Any ideas how to get it back to official & reset counter?

[Q] Phone rebooting randomly - help needed

Hey everyone,
So, I'm pretty new to Android having had the past two iterations of the Nexus 7 and decided to take the leap from an iPhone (which I had jailbroken) to a Samsung Galaxy S4 GT-I9505 LTE, which I bought unlocked and outright.
I ran stock TouchWiz for a while and then wanted to play, so installed FoxHound 3.2. This worked fine for some time, but then I started getting random reboots which seemed to coincide with listening to music on the device. After a while the reboots suddenly became more regular and it got so I couldn't even open WhatsApp without it either restarting or going into a bootloop. Usually, if it went into a bootloop and I tried starting the phone straight away it would fail, but if I left it off for some time it would start up okay, only to reboot again later if I used it for anything. I also noticed the battery draining quickly.
I tried flashing the device with various other ROMs - PACMan, Google AOKP, etc. - but got the same issue. Many times, the system would crash just when I first started to setup the phone. I finally determined the reason it was crashing at the initial startup was that it was when WiFi was being enabled. So, I ended up following a fruitless several hours of attempting to fix the WiFi using files provided on this page: http://forum.xda-developers.com/showthread.php?t=2192025. I tried XXUDMH8, XXUEMJ7 and XXUEMK8 all to no avail - I installed both the firmware and the WiFi fix files using Odin and thought I had it cracked, only for my phone to eventually reboot again whilst WiFi was not even enabled - it did take a bit longer this time though, admittedly, but it still rebooted and went into a bootloop.
So, I finally followed this page: http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/ to completely return my device to stock TouchWiz, but still no joy.
I have tried factory resetting the device and wiping all cache from the stock recovery and from Philz CWM (which I had while using the custom ROMs), but this does nothing.
I tried connecting my device to Kies now that I have the stock TouchWiz ROM back on the device, but it is now rebooting even more frequently and I can't get in long enough to run the emergency firmware recovery. It used to stay up longer (sometimes indefinitely) when connected to the PC via the Samsung factory cable or to a power supply with the Samsung charger, but now it is even rebooting when plugged in.
I am extremely worried that my device that cost me nearly £600 a few months ago is bricked for good. I did (understandably) think that returning it to default would've resolved the issue, but even this has failed.
Is there ANYTHING else I can try that I have not already........?

KalarAzar said:
Is there ANYTHING else I can try that I have not already........?
Click to expand...
Click to collapse
hello mate, what bootloader do you have?(Boot into download mode too see if it says Knox void warranty or not) and can you still boot into download mode? thanks

Repulsa said:
hello mate, what bootloader do you have?(Boot into download mode too see if it says Knox void warranty or not) and can you still boot into download mode? thanks
Click to expand...
Click to collapse
Hi and thanks for your reply,
I can boot into download mode - one of the only things I can do! - and it says 0x1 under KNOX WARRANTY VOID, so yes it is showing Knox void.
Just in case you need it, the full information shown on the screen in download mode is as follows:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
Thanks again..

KalarAzar said:
Thanks again..
Click to expand...
Click to collapse
I want you to flash the 4.3 stock rom firmware from samsung (Sign up)www.sammobile.com/firmwares/1/ make sure to choose the right one such as device, country . Then when your done flash the file via odin 3.09 and select AP ,Or follow the instruction from here, how to do a proper flash. http://forum.xda-developers.com/showthread.php?t=2252982 . have a nice day.

Repulsa said:
I want you to flash the 4.3 stock rom firmware from samsung (Sign up)www.sammobile.com/firmwares/1/ make sure to choose the right one such as device, country . Then when your done flash the file via odin 3.09 and select AP ,Or follow the instruction from here, how to do a proper flash. http://forum.xda-developers.com/showthread.php?t=2252982 . have a nice day.
Click to expand...
Click to collapse
Hey Repulsa,
Thanks again. Unfortunately, this is what I did. I signed up at samfirmware and downloaded the file: I9505XXUEMK8_I9505BTUEMK5_BTU.zip
The only thing I did different was that I used Odin 3.07 and flashed using the PDA option, but I'm presuming this is the same thing..? After the bootloop, I went into recovery and factory reset, but still the bootloop occurs.
I have since managed to get into my phone after leaving it off for a couple of hours again and looking through the settings it says I have "Samsung" as the secure boot status and "Official" as the device status. The build number is showing up as JSS15J.I9505XXUEMK8 on Android 4.3.
Should I try anything else that you can think of?
Thanks again for the reply.

KalarAzar said:
Hey Repulsa,
Thanks again. Unfortunately, this is what I did. I signed up at samfirmware and downloaded the file: I9505XXUEMK8_I9505BTUEMK5_BTU.zip
The only thing I did different was that I used Odin 3.07 and flashed using the PDA option, but I'm presuming this is the same thing..? After the bootloop, I went into recovery and factory reset, but still the bootloop occurs.
I have since managed to get into my phone after leaving it off for a couple of hours again and looking through the settings it says I have "Samsung" as the secure boot status and "Official" as the device status. The build number is showing up as JSS15J.I9505XXUEMK8 on Android 4.3.
Should I try anything else that you can think of?
Thanks again for the reply.
Click to expand...
Click to collapse
is the problem still persist? if it does Turn off your phone and Press and hold Power+Volume up and do another Wipe cache and Factory reset.

Repulsa said:
is the problem still persist? if it does Turn off your phone and Press and hold Power+Volume up and do another Wipe cache and Factory reset.
Click to expand...
Click to collapse
Yes, I'm afraid it does, and I have already done the wipe cache and factory reset, but no joy. I did it again anyway and on reboot it went back into the bootloop again, I'm afraid..

KalarAzar said:
Hey everyone,
So, I'm pretty new to Android having had the past two iterations of the Nexus 7 and decided to take the leap from an iPhone (which I had jailbroken) to a Samsung Galaxy S4 GT-I9505 LTE, which I bought unlocked and outright.
I ran stock TouchWiz for a while and then wanted to play, so installed FoxHound 3.2. This worked fine for some time, but then I started getting random reboots which seemed to coincide with listening to music on the device. After a while the reboots suddenly became more regular and it got so I couldn't even open WhatsApp without it either restarting or going into a bootloop. Usually, if it went into a bootloop and I tried starting the phone straight away it would fail, but if I left it off for some time it would start up okay, only to reboot again later if I used it for anything. I also noticed the battery draining quickly.
I tried flashing the device with various other ROMs - PACMan, Google AOKP, etc. - but got the same issue. Many times, the system would crash just when I first started to setup the phone. I finally determined the reason it was crashing at the initial startup was that it was when WiFi was being enabled. So, I ended up following a fruitless several hours of attempting to fix the WiFi using files provided on this page: http://forum.xda-developers.com/showthread.php?t=2192025. I tried XXUDMH8, XXUEMJ7 and XXUEMK8 all to no avail - I installed both the firmware and the WiFi fix files using Odin and thought I had it cracked, only for my phone to eventually reboot again whilst WiFi was not even enabled - it did take a bit longer this time though, admittedly, but it still rebooted and went into a bootloop.
So, I finally followed this page: http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/ to completely return my device to stock TouchWiz, but still no joy.
I have tried factory resetting the device and wiping all cache from the stock recovery and from Philz CWM (which I had while using the custom ROMs), but this does nothing.
I tried connecting my device to Kies now that I have the stock TouchWiz ROM back on the device, but it is now rebooting even more frequently and I can't get in long enough to run the emergency firmware recovery. It used to stay up longer (sometimes indefinitely) when connected to the PC via the Samsung factory cable or to a power supply with the Samsung charger, but now it is even rebooting when plugged in.
I am extremely worried that my device that cost me nearly £600 a few months ago is bricked for good. I did (understandably) think that returning it to default would've resolved the issue, but even this has failed.
Is there ANYTHING else I can try that I have not already........?
Click to expand...
Click to collapse
it can be a bad battery aswell if your battery serial starts with BD exchange it asap you may also experience any issues mentioned in this thread http://forum.xda-developers.com/showthread.php?t=2570608

Acer4605 said:
it can be a bad battery aswell if your battery serial starts with BD exchange it asap you may also experience any issues mentioned in this thread http://forum.xda-developers.com/showthread.php?t=2570608
Click to expand...
Click to collapse
Ah FFS. My battery serial does start with BD and I was wondering if it was a battery issue, but didn't want to replace it if the fault was wider spread. I guess I may have to try this then..
I'm just flashing to MJ7 right now, but if it reboots again I will see about a new battery from where I bought it on Monday

And, as I forgot to say in the last post: thanks for your reply. If this fixes it, much kudos, my friend..

Yep. The flashing of MJ7 did not work. Maybe my battery is a dud as it went straight back into a bootloop at the Samsung logo.
Carphone Warehouse visit on Monday methinks..

KalarAzar said:
Yep. The flashing of MJ7 did not work. Maybe my battery is a dud as it went straight back into a bootloop at the Samsung logo.
Carphone Warehouse visit on Monday methinks..
Click to expand...
Click to collapse
you can get passed the samsung logo if you boot while your charger is connected to the phone, the battery might swell as well or is already bigger then it originally was

My phone has been randomly shutting down over the past couple of days and the only way I can get it to boot is to connect a charger/cable to pc. I've tried different ROMs and returning to stock. No joy.
I guess my battery could well be the problem
---------- Post added at 11:33 AM ---------- Previous post was at 11:28 AM ----------
My phone has randomly started shutting down over the past couple of days and the only way I can get it to boot is to connect charger/cable to pc. When it dies, it also loses all of my wifi passwords. It's a bit of a head scratcher. Any help appreciated

Definately the battery, dude
I was experiencing the same problems, and I observed that the battery swollen. So I replaced it and now the phone is functioning properly. Do not wait for the battery to modify its volume because you are risking to put pressure on the display and crack it. Beware.

Was, indeed, the battery
Hey everyone,
Just to let you know that I went back to Phones4u with the receipt from September (when I bought the new phone) and they filled out a form to request a new battery from Samsung and replaced mine their and then in the shop with a new battery from another Samsung Galaxy S4.
My old battery did, indeed, have a serial number that started with BD and the new one starts with AA so hopefully I am now sorted.
Massive thanks to everyone who replied and hopefully this thread will save someone else the time and lost data that flashing ROMs can incur.
Cheers,
A very happy Steve :laugh:

[Q] Soft brick? Hard brick? Sort of firm'ish brick really

I've made a bit of a mess and I need help please. My s4 is softbricked, but as softbricks go, it's rather hard.
I have an early S4 i9505 bought from Carphone Warehouse (UK, unlocked, pre knox). I rooted it, installed TBackup, greenify and got it how I wanted it. Then I downloaded a stock firmware from Sammobile and tested to see if I could get it back to 'warranty' condition, which was a success.
Confident that I could obtain warranty if I needed it, I re-rooted it, installed TB and greenify, and it ran sweetly for months from that point onwards.
I read about the arrival of updates (and knox) and concluded I didn't need them. It was working, leave it alone.
Then out of the blue, my nice stable machine broke. I didn't change anything I was aware of to cause it.
No normal boot.
No recovery.
Download only.
Using Odin, I tried allsorts, eventually getting the same Sammobile firmware to run.
2 days later, it broke again, same as before, but worse!?
Then I tried all sorts of stuff downloading no end of things trying to get it to boot or even go into recovery. The most promising approach was to reload the firmware along with a .pit file, but still no joy. I've lost track of the other things I tried, but I've been doing it for a week, so a lot has been done. In desperation, I even tried downloading the latest firmware, so I now have signs of knox of the odin page.
I now have the following symptoms:
Booting into recovery brings up the blue 'booting recovery' message then just blackness.
Normal boot is exactly the same as above.
Unpowered conection to my laptop gives a 5 second boot loop featuring the buzz only.
I can reliably boot into download and download stuff with Odin and change the little Odin page status messages. After (foolishly) trying the latest firmware, these messages say
ODIN MODE
PRODUCT NAME GT-I9505
CURRENT BINARY Samsung Official
SYSTEM STATUS Official
KNOX KERNEL LOCK 0x0
KNOX WARRANTY VOID 0x0
CSB-CONFIG-LSB 0x30
WRITE PROTECTION: enable
eMMC BURST MODE enabled
Please can anyone give me some advice on what else I could try?
Thanks
Steve

Wrinklespots said:
ODIN MODE
PRODUCT NAME GT-I9505
CURRENT BINARY Samsung Official
SYSTEM STATUS Official
KNOX KERNEL LOCK 0x0
KNOX WARRANTY VOID 0x0
CSB-CONFIG-LSB 0x30
WRITE PROTECTION: enable
eMMC BURST MODE enabled
Please can anyone give me some advice on what else I could try?
Thanks
Steve
Click to expand...
Click to collapse
If anything else is not working (especially, if you're unable to go to recovery) I'd call sammy service center. Your download mode says that you did not rooted your phone, and knox is untouched either.

spamtrash said:
If anything else is not working (especially, if you're unable to go to recovery) I'd call sammy service center. Your download mode says that you did not rooted your phone, and knox is untouched either.
Click to expand...
Click to collapse
Thanks for looking spamtrash.
I was wondering if I could get away with that. It does look good from the Odin display, but the flash counter must have a pretty high number in it by now! Won't that show up somewhere?
Do you think it does actually have a fault on it, rather than just some software that's messed up and needs tweaking?
Thanks
Steve

Wrinklespots said:
Thanks for looking spamtrash.
I was wondering if I could get away with that. It does look good from the Odin display, but the flash counter must have a pretty high number in it by now! Won't that show up somewhere?
Do you think it does actually have a fault on it, rather than just some software that's messed up and needs tweaking?
Thanks
Steve
Click to expand...
Click to collapse
1. Are you able to go to recovery mode?
2. Assuming that your previous communicates were taken from the screen in download mode - you're clean.
If answer for 1 is: NO, and assuming 2: do not bother the flash counter. Flash counter does not means you messed with custom ROMs, it just means amount of the ROM update tries. As they are unable to prove that the counter was not increased by failed KIES updates, you're safe.
To go deeper, service will have to flash and wipe your phone.
One thing: remove your sd card prior to giving/sending it out.

Try a different usb cable.I was in same boat as you (after stupidly thinking mobile odin pro liked modems).
Luckily I had an unused cable off my tab 3.

[Q] Restore for warranty without cable

Hi to all.
I have some issues with my S4 and want to have it treated on warranty, but the major issue is the USB connector NOT working.
It is charging somehow, but disconnecting and connecting all the time.
Another issues I have are the switching between Edge and HSPDA+, which is mostly not working, I have to switch it manually to H+ or GSM.
Also my screen is blinking, so I will send it back and never want to se that again.
But the problem is, that the original rom I had was Polish (it is unofficial distribution in my country) and I flashed it a few times, rooted, tried several ROMs but reverted back to original. Now there is German Rom installed - the official one, no Root or recowery, but I think the internal counter (Knox or how is called) is set up.
Is there any way to put it to the original shape with only access through SD card? Or do you think, will the service look for that counter?
Thanks for your replies.

Jonage said:
Hi to all.
I have some issues with my S4 and want to have it treated on warranty, but the major issue is the USB connector NOT working.
It is charging somehow, but disconnecting and connecting all the time.
Another issues I have are the switching between Edge and HSPDA+, which is mostly not working, I have to switch it manually to H+ or GSM.
Also my screen is blinking, so I will send it back and never want to se that again.
But the problem is, that the original rom I had was Polish (it is unofficial distribution in my country) and I flashed it a few times, rooted, tried several ROMs but reverted back to original. Now there is German Rom installed - the official one, no Root or recowery, but I think the internal counter (Knox or how is called) is set up.
Is there any way to put it to the original shape with only access through SD card? Or do you think, will the service look for that counter?
Thanks for your replies.
Click to expand...
Click to collapse
The problem is, this counter is just for the services and seller... if Knox is 0x1 they wont repair it without costs. But you can try it anyway

How to check the knox?

Jonage said:
How to check the knox?
Click to expand...
Click to collapse
Shut down your phone. Press Power + Volume Down until the screen turns on. Than there is a Warning, ignore it and go ahead. There will be the Knox and everything

Thanks, I forgotten about that.
Yes, there is Know Warranty void: 0x1
Current banary: Samsung Official, System status: Official

Jonage said:
Thanks, I forgotten about that.
Yes, there is Know Warranty void: 0x1
Current banary: Samsung Official, System status: Official
Click to expand...
Click to collapse
If I help you, I would appreciate if you click thanks
So maybe your seller wont repair your phone...I would make a full wipe in your case and see if the problems still exist.

Another thought, maybe the download mode connection to computer is working.

Jonage said:
Another thought, maybe the download mode connection to computer is working.
Click to expand...
Click to collapse
Try it, if yes, go to recovery and wipe all your user data, clicking clean to install a new rom (In philz touch recovery) and than flash the latest software from sammobile, searching your provider
than flash it in Odin3.09, select AP and than choose the downloaded rom (it must be a tar.md5 file.)

Yeah, but now I read there is no way to set the knox trigger back, anyway....

Jonage said:
Yeah, but now I read there is no way to set the knox trigger back, anyway....
Click to expand...
Click to collapse
No, there is no way. Most of people say it's en eFuse chip and when you flash any custom thing, this chip will be destroyed and it will be destroyed for ever.

[devs help needed] g900f stuck in an unbreakable bootloop enigma

Hi to all,
sorry to use the bold character but it's REALLY an unbreakable enigma. It regards My fiancee Galaxy s5 g900f no brand ITV and that one of another user.
The thread in wich we found to be in the same situation is T H I S.
The phone was never touched, modified or altered in anyway as my fiancee doesn't even know what "root" or "rom" means. It was bought in november 2014, used with whatsapp, facebook and two games.
It was updated using wifi OTA to lollipop BOA3 ITV. Update was successful, she didn't wipe data as there were only 4-5 apps on it and the phone was working normally. It stayed this way for more than one month, no problems at all.
It was never touched in anyway, never diverted from the original. A very noob utilization to clarify.
At mid April one day when the phone was on the table in standby , we saw it rebooting. Then worked normally.
The day after it, two more reboots while doing anything , on the third one it appeared "SET WARRANTY BIT KERNEL" and BEGAN TO BOOTLOOP.
The bootloop starts right after "Samsung Galaxy s5 powered by android " and never ends.
Sometimes it gets stuck at "set warranty bit kernel".
THE PHONE ENTERS DOWNLOAD MODE always when pressing vol down,home,power.
IT DOESN'T ALWAYS ENTERS RECOVERY MODE. Sometimes gets stucked in "booting recovery. Recovery is not selinux enforcing. Set warranty bit recovery"
Me and one other guy on androidforums have tried everything:
-1. wipe cache, data and dalvick from stock recovery (it was difficult to enter it but done multiple times)
-2. flashing with ODIN stock images (OFFICIAL ITV FOR ME) . Kitkat and Lollipop officials. ALWAYS GREEN LIGHT PASS!
2.1 Updating bootloaders when going from kitkat to lollipop and viceversa.
2.2 Checking repartitioning using the right ITV PIT files.
2.3 wiping before and after that.
-3 flashing from KIES in FW UPGRADE MODE and emergency mode.
-4 flashed custom recovery. It gets stuck multiple times but the other guy managed to boot into Philz, formatting every partition,
-5 installing CYANOGENMOD 12 but it loads the cyanogen bootanimation for 1 sec, then bootloop.
With lollipop it gets stuck on the samsung bootloader logo.
With kitkat it gets to samsung bootanimation (led and audio working) but never ends.
ONE TIME IT MANAGED TO ARRIVE TO "upgrading android applications 1 of 1" for 2 seconds then bootloops (and it was data clean! so what app is it upgrading?!?)
the status in Odin mode is
ODIN MODE
PRODUCT NAME: SM-G900F
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0*1 (1)
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
SECURE DOWNLOAD : ENABLE
UDC START
But it was never modified with anything! and it stays this way after an original rom flash! (shouldn't be at least reporting "official" ?)
SAMSUNG SERVICE IN ITALY REFUSED TO REPAIR IT SAYING THAT WARRANTY IS VOID DUE TO CUSTOM MODS.
Don't know what to do. I've tried almost everything.
WE BEG FOR YOU HELP , PLEASE.
P.S. sorry if I have mistaken the thread section or the title

oile said:
Hi to all,
sorry to use the bold character but it's REALLY an unbreakable enigma. It regards My fiancee Galaxy s5 g900f no brand ITV and that one of another user.
The thread in wich we found to be in the same situation is T H I S.
The phone was never touched, modified or altered in anyway as my fiancee doesn't even know what "root" or "rom" means. It was bought in november 2014, used with whatsapp, facebook and two games.
It was updated using wifi OTA to lollipop BOA3 ITV. Update was successful, she didn't wipe data as there were only 4-5 apps on it and the phone was working normally. It stayed this way for more than one month, no problems at all.
It was never touched in anyway, never diverted from the original. A very noob utilization to clarify.
At mid April one day when the phone was on the table in standby , we saw it rebooting. Then worked normally.
The day after it, two more reboots while doing anything , on the third one it appeared "SET WARRANTY BIT KERNEL" and BEGAN TO BOOTLOOP.
The bootloop starts right after "Samsung Galaxy s5 powered by android " and never ends.
Sometimes it gets stuck at "set warranty bit kernel".
THE PHONE ENTERS DOWNLOAD MODE always when pressing vol down,home,power.
IT DOESN'T ALWAYS ENTERS RECOVERY MODE. Sometimes gets stucked in "booting recovery. Recovery is not selinux enforcing. Set warranty bit recovery"
Me and one other guy on androidforums have tried everything:
-1. wipe cache, data and dalvick from stock recovery (it was difficult to enter it but done multiple times)
-2. flashing with ODIN stock images (OFFICIAL ITV FOR ME) . Kitkat and Lollipop officials. ALWAYS GREEN LIGHT PASS!
2.1 Updating bootloaders when going from kitkat to lollipop and viceversa.
2.2 Checking repartitioning using the right ITV PIT files.
2.3 wiping before and after that.
-3 flashing from KIES in FW UPGRADE MODE and emergency mode.
-4 flashed custom recovery. It gets stuck multiple times but the other guy managed to boot into Philz, formatting every partition,
-5 installing CYANOGENMOD 12 but it loads the cyanogen bootanimation for 1 sec, then bootloop.
With lollipop it gets stuck on the samsung bootloader logo.
With kitkat it gets to samsung bootanimation (led and audio working) but never ends.
ONE TIME IT MANAGED TO ARRIVE TO "upgrading android applications 1 of 1" for 2 seconds then bootloops (and it was data clean! so what app is it upgrading?!?)
the status in Odin mode is
ODIN MODE
PRODUCT NAME: SM-G900F
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0*1 (1)
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
SECURE DOWNLOAD : ENABLE
UDC START
But it was never modified with anything! and it stays this way after an original rom flash! (shouldn't be at least reporting "official" ?)
SAMSUNG SERVICE IN ITALY REFUSED TO REPAIR IT SAYING THAT WARRANTY IS VOID DUE TO CUSTOM MODS.
Don't know what to do. I've tried almost everything.
WE BEG FOR YOU HELP , PLEASE.
P.S. sorry if I have mistaken the thread section or the title
Click to expand...
Click to collapse
facing exactly the same problem , any Devs kind enuff to enlighten us on this ?

No one could help?

Looks like a broken NAND(The 16GB storasge of the device) chip to me... It should be replaced with a new one to fix the problem. Repartitioning it won't fix it at all and 1 thing you've done wrong is flashing it with custom ROMs after it broke. You should have claimed warranty first before you tried the custom ROMs solution.
Now the only solution to this is approach samsung again and ask how much would it cost you replacing your S5's NAND. Nothing can be done here software wise. The explanation you made points only to this problem.
Being stuck in "Samsung Galaxy s5 powered by android" only means that the kernel won't even load at all and you flashing the kernel with stock & CM version and still encountering this issue only means it's a NAND problem.

I claimed the warranty repair before trying custom rom. I haven't had the possibility to try custom roms at all because the phone is not mine. But xtaeyeon who has the same problem did and cyanogenmod didn't boot.
Now, being you so kind giving your advice, is there any possibility to restore broken sectors on the nand? Or is there a way to have the nand chip only replaced? Do you know any repair center that can do that without buying a new motherboard?
It is so strange that it came out of nowhere exactly the same problem for me, xtaeyeon and another guy on a Spanish forum who changed the board to have it repaired.

As we are on different countries I couldn't tell if there's such a way for you to do that. Here in our country local phone technicians buy broken phones and salvage their parts to repair phones such as this. Hence if you were here I could say yes there's a way to fix it without having to replace the board.
Next is you said that you didn't flash custom ROMs on that device then why not claim for a warranty repair then? Is it out of warranty already? If it's still under warranty then I suggest you return it for replacement to them. You have every right to have it fixed for free and if they say that warranty is void because you modified the software then insist that you didn't and have a real technician from samsung decide.
As for restoring broken sectors... I don't think this is the problem at all. Cause if it is the filesystem configured on the NAND should have isolated the bad sectors automatically and allocate the files to good sectors indeed. I believe that the NAND chip here is totally broken like when you transfer files in there the file you transferred gets corrupted.
oile said:
I claimed the warranty repair before trying custom rom. I haven't had the possibility to try custom roms at all because the phone is not mine. But xtaeyeon who has the same problem did and cyanogenmod didn't boot.
Now, being you so kind giving your advice, is there any possibility to restore broken sectors on the nand? Or is there a way to have the nand chip only replaced? Do you know any repair center that can do that without buying a new motherboard?
It is so strange that it came out of nowhere exactly the same problem for me, xtaeyeon and another guy on a Spanish forum who changed the board to have it repaired.
Click to expand...
Click to collapse

Samsung said it is out of warranty because of Knox 0x1 and "custom" condition of binary and system. But it was never Flashed with anything different than the lollipop ota.
I don't know what to do. If it really is the new motherboard, my fiancé cannot afford it cause the Galaxy s5 was a gift. :/

oile said:
Samsung said it is out of warranty because of Knox 0x1 and "custom" condition of binary and system. But it was never Flashed with anything different than the lollipop ota.
I don't know what to do. If it really is the new motherboard, my fiancé cannot afford it cause the Galaxy s5 was a gift. :/
Click to expand...
Click to collapse
If you live in the EU the knox thing is irrelevant, they're required to service you anyway by law.
You have a right to flash the OS of your choice in EU. Sometimes they try to get rid of customers, basically they have an unofficial policy of avoiding giving you free service when possible. You just need to literally tell them you won't take no for an answer (this makes miracles happen) and that you won't leave until you get the service they owe you.
But if you live outside of EU, well, then I don't know.