Database Users

[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.

Recovery Mode error and does not install TWRP

Hi!
I'm 3 days trying to solve a problem in my J5 and I can not get anything.
About a year ago I bought this device and did the ROOT process of it, I installed TWRP and SuperUser.
I needed to remove the SuperUser and unfollow the root procedure, so I went back to the official Stock Rom.
After about 2 weeks of this procedure the device was no longer starting the bot, tried to enter by the TWRP and simply did not enter as well.
I obtained at the time a bootloader (it was said to be official) and installed via odin.
The Apparatus has come back to life!
Now I'm trying to install TWRP and it just does not install!
When I try to enter recovery mode it displays the following messages in sequence "installing software update", "no command found" and after a minute it goes into a simple recovery.
I tried to change the TWRP odin several times, not the error, appears "pass" and reboots the device, when I try to access the recovery appears always the message above and back to simple recovery.
What could be happening?
Do you know any solution?
Model: SM-J500M
Android: 6.01
Kernel: 3.10.49-99447777 dpi @ SWDD3016 # 1
STOCK ROM: J500MUBU1BPH1_J500MZTO1BPH1_J500MUBU1BPH1_HOME.tar
Complementing:
I was able to solve some of the problem.
As a last attempt I decided to change the USB cables, I used 5 different cables until a good old one of the motorola worked and I was able to complete the process by odin.
Of these cables 4 are original, one being that of the apparatus itself.
Now another problem I noticed is not being able to root in the device.
I can install the TWRP after uploading the rom stock, however when installing the super user via TWRP the device will no longer start and it will be locked in the samsung logo.
I was thinking of installing some CFW, but the ones I find are for another version or have bugs that affect my use, for example the camera does not save photos, can only use a SIM card and not listen to the audio in the voice calls.

Hey, nunca flash un gestor de arranque solo que es muy arriesgado en caso de ladrillo blando que necesita para flash stock rom vía odin. Ahora a twrp dependiendo de la versión del software cerciórese de que hve el twrp derecho entonces al destellar vía odin cerciórese de que usted desmarque el rearranque automático pues ha estado causando errores y el twrp no instala bien cuando usted deja el autoreboot marcado acaba de desmarcarlo y de destellar otra vez .
Sent from my SM-J500F using Tapatalk

@ridestorm : You must post in English on this forum. If you don't know English, then try Google translate although it doesn't translate right many times.

#Henkate said:
@ridestorm : You must post in English on this forum. If you don't know English, then try Google translate although it doesn't translate right many times.
Click to expand...
Click to collapse
I'm sorry, I've been in my language to translate and the press.
Now I'm with Another with or root of the problem.
ridestorm said:
Complementing:
I was able to solve some of the problem.
As a last attempt I decided to change the USB cables, I used 5 different cables until a good old one of the motorola worked and I was able to complete the process by odin.
Of these cables 4 are original, one being that of the apparatus itself.
Now another problem I noticed is not being able to root in the device.
I can install the TWRP after uploading the rom stock, however when installing the super user via TWRP the device will no longer start and it will be locked in the samsung logo.
I was thinking of installing some CFW, but the ones I find are for another version or have bugs that affect my use, for example the camera does not save photos, can only use a SIM card and not listen to the audio in the voice calls.
Click to expand...
Click to collapse
Thank you!

Help me have some fun with demo unit

So I installed Windows 10 on a client's computer and collected the pay and also gave me a sm-g935x live demo unit. I accepted even after initial look that it was a failed attempt at root attempt. Current issues. I have never flashed a room on a phone before. I also never done a tarp install or used odin. The work involved is not too much different than my computer work though. Now for the phone issues that I know from power on.
Kernel is not seandroid enforcing
Try resetting I can not get in there. Trying to boot into safe mode I get
Custom Binary blocked by frp lock.
Going to Odin is this.
Odin Mode
Download Speed: Fast
Product Name: sm-g935x
Current Binary: Custom
System Status: Custom
FRP Lock: On
Secure Download: Enabled
Warranty Void: 1 (0x020c)
RP SWREV: B:1 K:0 S:0
I searched and I do not know if this is phone is exynos or the other on. I do know that flashing a wrong type can make over hard eggs and it does not have the guts to make it a real phone (I can easily solve that, parts are available all over the place and I can replace them if I decide to go that far, or do it to and have the fun with my J7 on learning how to flash phones (don't know why I never did it)
Other things I am considering on it immediately... get into the phone by fixing that binary and frp. It is something I should have learned years ago. Any links on it that preferably can be done via a usb stick? My kids borrowed my laptop till school year is over in a different state (likely not). Once I can get past that I want to learn as much as I can about installing custom roms, modifying protected system files on droids, making my own rom (nice guide here). Perhaps even completely wiping the rim and seeing if I can install windows, linux, sox, Kodi. With my kids gone I have time for that.
Or I can just get it a motherboard and transmitter as that is work I know how to do and do that stuff with this j700t1 which is driving me to total distraction and motivating me to learn that stuff.
Any links on how to get this ball rolling and PM' s on how to do it if it is not clear on how to do the steps be appeciated.
Thanks all in advance and hope this is in the right forum.

Dead Phone Within 2 Hours of Receiving

Well, my S8+ experience has not gone very well so far. After a lot of screwups in trying to actually get one, it finally arrived in the mail yesterday. Initially, everything was going great, powered it on and started setting things up before inserting the SIM, as well as installing an OTA update from Samsung. After this, things seemed to start going wrong. The phone restarted itself in the middle of me working on it and when it came back up, told me that a hard reset had been performed and wiped all the data. Started all over again setting it up, and eventually powering down to install the SIM, except this time, things were laggy and glitchy when it started back up and it just wasn't operating smoothly and continued getting worse and worse. It restarted itself a few more times and each time took longer and longer to actually get started until finally it restarted with an error message in red text reading "BOTA: fail to read bota partition, Status (Device Error)".
Tried to do a couple things at this point, soft and hard resets, but the phone was completely unresponsive to any input at all. I left it like this last night and when I woke up this morning, it had new error messages, overwritten on top of the BOTA error message:
RPMB fuse blown
RPMB Unexpect exception
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FNP LOCK: OFF
WARRANTY VOID: 0xFFFFFFFF 00x00
QUALCOMM SECUREBOOT: 0xFFFFFFFF
RP SWREV: B0 (0,0,0,0,0) K1 S1
SECURE DOWNLOAD: ENABLE
Still totally unresponsive to any input. I checked it again a while ago and it finally ran out of battery power so I as able to plug it in and do a factory reset before it goes back!

Reznor909 said:
Well, my S8+ experience has not gone very well so far. After a lot of screwups in trying to actually get one, it finally arrived in the mail yesterday. Initially, everything was going great, powered it on and started setting things up before inserting the SIM, as well as installing an OTA update from Samsung. After this, things seemed to start going wrong. The phone restarted itself in the middle of me working on it and when it came back up, told me that a hard reset had been performed and wiped all the data. Started all over again setting it up, and eventually powering down to install the SIM, except this time, things were laggy and glitchy when it started back up and it just wasn't operating smoothly and continued getting worse and worse. It restarted itself a few more times and each time took longer and longer to actually get started until finally it restarted with an error message in red text reading "BOTA: fail to read bota partition, Status (Device Error)".
Tried to do a couple things at this point, soft and hard resets, but the phone was completely unresponsive to any input at all. I left it like this last night and when I woke up this morning, it had new error messages, overwritten on top of the BOTA error message:
RPMB fuse blown
RPMB Unexpect exception
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FNP LOCK: OFF
WARRANTY VOID: 0xFFFFFFFF 00x00
QUALCOMM SECUREBOOT: 0xFFFFFFFF
RP SWREV: B0 (0,0,0,0,0) K1 S1
SECURE DOWNLOAD: ENABLE
Still totally unresponsive to any input. I checked it again a while ago and it finally ran out of battery power so I as able to plug it in and do a factory reset before it goes back!
Click to expand...
Click to collapse
Jesus sounds horrible and what a disappointment I'd return it sorry

I have learned the hard way that you should always insert your sim card BEFORE setting everything up.

The G Dept. said:
I have learned the hard way that you should always insert your sim card BEFORE setting everything up.
Click to expand...
Click to collapse
could that be his problem?

I don't think so. When I say that I've learned the hard way, it's because when you insert the sim card for the first time, it wipes the phone to lock it to the carrier.
It's normal behavior so it shouldn't give such errors, really..
Envoyé de mon SM-G955W en utilisant Tapatalk

It sounds like the hard drive completely crashed. It's A REALLY uncommon problem about today's tech, but return your phone and grab a new one.
Best of luck on it, though!

As someone else said, when you insert your SIM card, it matches the CSC and wipes your phone, it did that for me, first boot took ages, but it booted up fine and it's been running great ever since.
Yours somehow killed its own eMMC during the wipe process causing it to not boot.

any advice greatly appreciated

Hi there, I have a problem with my phone and I was ponited in the direction of this forum to see if anyone would be able to help out. Any assistance woud be very greatly appreciated
I am based in UK and I recently bought myself a Galaxy Note 4. 2nd Hand but as new condition. I tried to do an over the air software update to see if the phone would be able to get a more recent version of Android (it was running 5.0.1) and the phone wouldn't connect to the server. Also whe I tried to connect to Android Pay I got an error saying the device was rooted so I couldn't use the app on this phone. I therefore wanted to unroot the phone
I must stress my real technical knowledge of Android phones is basically at novice level but I tried to unroot the phone using SuperSU which I downloaded from the app store. I ran the unroot option and restarted the phone as prompted but this resulted in my phone being stuck in Bootloop. It wouldn't go past the Samsung load screen
I probably did the worst thing which was panic, went into recovery mode and attempted to factory reset to return the phone to out of box settings. I wiped the cache and did the factory reset but, of course, this hasn't resolved the problem. I then done a bit more reading and downloaded Odin and attempted to find the stock firmware for my phone (Model SM-910F), which i did, but unfortunately when I tried to flash this firmware back to my phone through Odin I get a failed error
So basically i'm on my knees trying to get some technical advice as to what else i can try or how to proceed. I did try taking it back to the Samsung Store and plead ignorance for help but the best I got there was that my main board would need replacing which would probably set me back another 200 nicker. For that money I may as well just buy a new phone. any help would be greatly appreciated as I'm currently left with a very expensive paperweight
Many thanks in advance guys
Lash

lashley82 said:
Hi there, I have a problem with my phone and I was ponited in the direction of this forum to see if anyone would be able to help out. Any assistance woud be very greatly appreciated
I am based in UK and I recently bought myself a Galaxy Note 4. 2nd Hand but as new condition. I tried to do an over the air software update to see if the phone would be able to get a more recent version of Android (it was running 5.0.1) and the phone wouldn't connect to the server. Also whe I tried to connect to Android Pay I got an error saying the device was rooted so I couldn't use the app on this phone. I therefore wanted to unroot the phone
I must stress my real technical knowledge of Android phones is basically at novice level but I tried to unroot the phone using SuperSU which I downloaded from the app store. I ran the unroot option and restarted the phone as prompted but this resulted in my phone being stuck in Bootloop. It wouldn't go past the Samsung load screen
I probably did the worst thing which was panic, went into recovery mode and attempted to factory reset to return the phone to out of box settings. I wiped the cache and did the factory reset but, of course, this hasn't resolved the problem. I then done a bit more reading and downloaded Odin and attempted to find the stock firmware for my phone (Model SM-910F), which i did, but unfortunately when I tried to flash this firmware back to my phone through Odin I get a failed error
So basically i'm on my knees trying to get some technical advice as to what else i can try or how to proceed. I did try taking it back to the Samsung Store and plead ignorance for help but the best I got there was that my main board would need replacing which would probably set me back another 200 nicker. For that money I may as well just buy a new phone. any help would be greatly appreciated as I'm currently left with a very expensive paperweight
Many thanks in advance guys
Lash
Click to expand...
Click to collapse
Go to odin download mode and tell me what exactly your model shows there? Maybe I can help.
Press 3 button combo while phone is turned off to go into download mode.(volume down+home+power)
Or even better if you can take picture and upload it while your phone in download mode.

Trex888 said:
Go to odin download mode and tell me what exactly your model shows there? Maybe I can help.
Press 3 button combo while phone is turned off to go into download mode.(volume down+home+power)
Or even better if you can take picture and upload it while your phone in download mode.
Click to expand...
Click to collapse
Hi and thank you for coming back to me, i get the following
ODIN MODE (HIGH SPEED)
Product Name: SM-910T - (this does confuse me slightly as the phone model actually says SM-910F)
Current Binary: Custom
System Status: Custom
Reactivation Lock: OFF
KNOX Warranty Void: 0x1 (3)
QUALCOMM Secureboot: ENABLE (CSB)
RP SWREV: S1, T1, R1, A2, P1
Secure Download: ENABLE
Hope this is of help

lashley82 said:
Hi and thank you for coming back to me, i get the following
ODIN MODE (HIGH SPEED)
Product Name: SM-910T - (this does confuse me slightly as the phone model actually says SM-910F)
Current Binary: Custom
System Status: Custom
Reactivation Lock: OFF
KNOX Warranty Void: 0x1 (3)
QUALCOMM Secureboot: ENABLE (CSB)
RP SWREV: S1, T1, R1, A2, P1
Secure Download: ENABLE
Hope this is of help
Click to expand...
Click to collapse
Hello there.
Sorry to say but you dont have N910f international model.its refurbished and faked by n910F software.as you can see your download mode shows n910t that's the orignal motherboard model.and also it shows binaries and status custom and not official as it should.also knox is 0×1 it means it was rooted before and warranty was void.
You have sm-N910T that's T-mobile usa model.
You can download latest N910T firmware from www.sammobiles.com/firmwares and flash through odin.
Dont try to flash n910f firmware otherwise it can be bricked and unusable.
Hope this will help.

Trex888 said:
Hello there.
Sorry to say but you dont have N910f international model.its refurbished and faked by n910F software.as you can see your download mode shows n910t that's the orignal motherboard model.and also it shows binaries and status custom and not official as it should.also knox is 0×1 it means it was rooted before and warranty was void.
You have sm-N910T that's T-mobile usa model.
You can download latest N910T firmware from and flash through odin.
Dont try to flash n910f firmware otherwise it can be bricked and unusable.
Hope this will help.
Click to expand...
Click to collapse
Thank you, I'm going to give this a go and see if it works
Many Thanks

lashley82 said:
Thank you, I'm going to give this a go and see if it works
Many Thanks
Click to expand...
Click to collapse
You're welcome.
Make sure after flash firmware go to recovery by pressing (volume up+ home+ power ) while phone is off and do (data factory reset & wipe cache)otherwise it will stuck on Samsung logo at first boot.
First boot will take approximately 15 minutes.