Database Users

[Q] [HELP] i9505 Recovery Booting Stuck

Hello guys,
I need your help again!
I recently changed my i9100g with this other device, GT-I9505 Italian version, no brand.
The history of this device was quite this: stock FW until 4.3 (just my suppose) --> CM11 --> try to flash 4.2.2 stock --> brick @[email protected]
Now I tried to put the original 4.4.2 firmware by flashing with Odin v3.09, because I don't want custom rom for the moment, just make it work.
The problem is that the phone stucks at Samsung logo, and when I tried to go in recovery mode, it stays on the same logo but there's a blue write in the top left corner "Recovery Booting".
Do you have any suggestion?
TY in advance

Drake9090 said:
Hello guys,
I need your help again!
I recently changed my i9100g with this other device, GT-I9505 Italian version, no brand.
The history of this device was quite this: stock FW until 4.3 (just my suppose) --> CM11 --> try to flash 4.2.2 stock --> brick @[email protected]
Now I tried to put the original 4.4.2 firmware by flashing with Odin v3.09, because I don't want custom rom for the moment, just make it work.
The problem is that the phone stucks at Samsung logo, and when I tried to go in recovery mode, it stays on the same logo but there's a blue write in the top left corner "Recovery Booting".
Do you have any suggestion?
TY in advance
Click to expand...
Click to collapse
Flash the stock rom again..and do NOT check autoreboot in odin.
The straight away boot into recovery, factory reset it..and you'll boot
"If someone helps, never forget to hit thanks ? "

DeepankarS said:
Flash the stock rom again..and do NOT check autoreboot in odin.
The straight away boot into recovery, factory reset it..and you'll boot
"If someone helps, never forget to hit thanks ? "
Click to expand...
Click to collapse
Thank you very much for your reply!
It doesn't work, maybe I'm just doing something wrong, what should I have to do after flash?

Drake9090 said:
Thank you very much for your reply!
It doesn't work, maybe I'm just doing something wrong, what should I have to do after flash?
Click to expand...
Click to collapse
-Open odin
-Uncheck autoreboot
-Add your firmware file to the AP/PDA section
-Start the process
When this will end, your ohone wont boot automatically (obviously)
After 2-3 minutes start it, if it turns on properly congo..
If it doesnt..just boot into recovery (volume up+home button+power button) and perform a data wipe.
If this does not helo at all, download the LATEST KITKAT 4.4.2 UNBRANDED again for your phone as it can be a bad download issue too.
"If someone helps, never forget to hit thanks ? "

DeepankarS said:
-Open odin
-Uncheck autoreboot
-Add your firmware file to the AP/PDA section
-Start the process
When this will end, your ohone wont boot automatically (obviously)
After 2-3 minutes start it, if it turns on properly congo..
If it doesnt..just boot into recovery (volume up+home button+power button) and perform a data wipe.
If this does not helo at all, download the LATEST KITKAT 4.4.2 UNBRANDED again for your phone as it can be a bad download issue too.
"If someone helps, never forget to hit thanks ? "
Click to expand...
Click to collapse
I would try another firmware less recent, just to see what happens...
But I have great news: Philz touch works, so now I have a working custom recovery!
the problem is that I can't just flash a custom ROM to repair
I think I need the pit file, but I can't find one on the internet @[email protected]

Drake9090 said:
I would try another firmware less recent, just to see what happens...
But I have great news: Philz touch works, so now I have a working custom recovery!
the problem is that I can't just flash a custom ROM to repair
I think I need the pit file, but I can't find one on the internet @[email protected]
Click to expand...
Click to collapse
Y do you need a pit? Pit files are not to be played with and can possibly brick if not flashed with utmost care.
Try a stock firmware first. Dont try any stock firmware till you have a working phone..
"If someone helps, never forget to hit thanks ? "

DeepankarS said:
Y do you need a pit? Pit files are not to be played with and can possibly brick if not flashed with utmost care.
Try a stock firmware first. Dont try any stock firmware till you have a working phone..
"If someone helps, never forget to hit thanks ? "
Click to expand...
Click to collapse
I'm flashing this firmware: I9505XXUGNG8_I9505ITVGNG1_ITV
I was thinking about pit because the philz says strange errors:
failed to mount /data to setup /data/media, or something like this... and also other problems related to /sdcard
Have you an idea on what to do?
I'm just following this guide: http://forum.xda-developers.com/showthread.php?t=2265477

Drake9090 said:
I'm flashing this firmware: I9505XXUGNG8_I9505ITVGNG1_ITV
I was thinking about pit because the philz says strange errors:
failed to mount /data to setup /data/media, or something like this... and also other problems related to /sdcard
Have you an idea on what to do?
I'm just following this guide: http://forum.xda-developers.com/showthread.php?t=2265477
Click to expand...
Click to collapse
The pit file is right there in @samersh72s thread
In the attachments.
Flash properly after reading the OP very carefully and DO NOT SKIP ANY STEP OR MODIFY any
Still IMHO a data wipe after reflashing can fix your bootloop.
"If someone helps, never forget to hit thanks ? "

DeepankarS said:
The pit file is right there in @samersh72s thread
In the attachments.
Flash properly after reading the OP very carefully and DO NOT SKIP ANY STEP OR MODIFY any
Still IMHO a data wipe after reflashing can fix your bootloop.
"If someone helps, never forget to hit thanks ? "
Click to expand...
Click to collapse
I thought the same way too, but didn't work...
The attachment doesn't work, but some posts later there is one working
I'll try and let you know the results!

Stll locked here...
Used yhe pit file, but nothing changed
in Philz Touch 6 with CWM 6.0.4.7 I have this error:
E: could not mount /data to setup /data/media path!
Have you ever faced it?

Drake9090 said:
Used yhe pit file, but nothing changed
in Philz Touch 6 with CWM 6.0.4.7 I have this error:
E: could not mount /data to setup /data/media path!
Have you ever faced it?
Click to expand...
Click to collapse
Ermm no...
@Lennyz1988 @MAX 404
Help?
Sent from my GT-I9500 using XDA Free mobile app

I was thinking about a possible cause: could it be that I'm using a wrong firmware?
this device is used, so I supposed that it was ITV the correct firmware, but not 100% sure...
I'm just sure that it is no-brand.

Drake9090 said:
I was thinking about a possible cause: could it be that I'm using a wrong firmware?
this device is used, so I supposed that it was ITV the correct firmware, but not 100% sure...
I'm just sure that it is no-brand.
Click to expand...
Click to collapse
Screenshots of "phone info samsung" app please.
"If someone helps, never forget to hit thanks ?"

When you flash the Odin firmware it's succesfull?

DeepankarS said:
Screenshots of "phone info samsung" app please.
"If someone helps, never forget to hit thanks ?"
Click to expand...
Click to collapse
The only info that I'm able to see are the ones in download mode...
If the phone don't boot any firmware, how can I use that app?

Lennyz1988 said:
When you flash the Odin firmware it's succesfull?
Click to expand...
Click to collapse
Yes, or better to say, Odin says PASS, but when I reboot (even with or without Auto-Reboot flag) the phone stucks on Samsung Logo saying Recovery Booting.

DeepankarS said:
The pit file is right there in @samersh72s thread
In the attachments.
Flash properly after reading the OP very carefully and DO NOT SKIP ANY STEP OR MODIFY any
Still IMHO a data wipe after reflashing can fix your bootloop.
"If someone helps, never forget to hit thanks ? "
Click to expand...
Click to collapse
Drake9090 said:
Yes, or better to say, Odin says PASS, but when I reboot (even with or without Auto-Reboot flag) the phone stucks on Samsung Logo saying Recovery Booting.
Click to expand...
Click to collapse
On top of all advice given here...
Can you boot at all? what is the status at the moment , rom recovery?
I would try to flash a recovery first ( twrp , philz) see if it works , do a factory reset ( backup first) and try flashing a stock rom,,see if it helps

MAX 404 said:
On top of all advice given here...
Can you boot at all? what is the status at the moment , rom recovery?
I would try to flash a recovery first ( twrp , philz) see if it works , do a factory reset ( backup first) and try flashing a stock rom,,see if it helps
Click to expand...
Click to collapse
The situation is still the same, so in order:
I cannot boot a complete system, I just stuck on samsung i9505 logo with blue "Recovery Booting" written in top-left on the screen;
At the moment I'm reflashing ossessively the stock rom, and philz touch; I can go in DL mode and not in the stock recovery, but when I flash philz touch I can enter by double clicking vol up when I see the blue, red and yellow writes.
I cannot do a factory reset, that is the real problem I suppose, 'cause when I enter in philz recovery, it says: "error mount /data etc etc..." as you can see in previous posts.
In DL mode this is the situation:
PN: GT-I9505
Current binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
csb-config-lsb: 0x30
write prot: enabled
eMMC Burst mode enabled

Drake9090 said:
The situation is still the same, so in order:
I cannot boot a complete system, I just stuck on samsung i9505 logo with blue "Recovery Booting" written in top-left on the screen;
At the moment I'm reflashing ossessively the stock rom, and philz touch; I can go in DL mode and not in the stock recovery, but when I flash philz touch I can enter by double clicking vol up when I see the blue, red and yellow writes.
I cannot do a factory reset, that is the real problem I suppose, 'cause when I enter in philz recovery, it says: "error mount /data etc etc..." as you can see in previous posts.
In DL mode this is the situation:
PN: GT-I9505
Current binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
csb-config-lsb: 0x30
write prot: enabled
eMMC Burst mode enabled
Click to expand...
Click to collapse
Lets go one step at the time.........forget about recovery for now
Flashing with Odin a stock rom ( use same rom you had before or newer) , what happen? did you followed the guide
http://forum.xda-developers.com/show....php?t=2265477 that @DeepankarS suggested ? did you flash the PIT file?

MAX 404 said:
Lets go one step at the time.........forget about recovery for now
Flashing with Odin a stock rom ( use same rom you had before or newer) , what happen? did you followed the guide
http://forum.xda-developers.com/show....php?t=2265477 that @DeepankarS suggested ? did you flash the PIT file?
Click to expand...
Click to collapse
Followed that guide many times, but the result is stuck in Samsung Logo.
Even tried flashing PIT file, but nothing changed.
maybe flash just a stock recovery after the firmware could solve the problem?

[SOLVED] How do I wipe data/cache in download mode?

Hello!
I've flashed a stock ROM on my Samsung Galaxy S5 (SM-G900F) using ODIN 3.07 and now the phone is bootlooping. I guess It's because I need to wipe data and cache partitions and here's the problem.
My home button is not working, so I can't boot in recovery mode. Adb does NOT recognize my device. I'm only able to access download mode using a JIG.
So, is there any way to wipe those partitions or to be able to access recovery using ODIN?
Thanks in advance for your help!

That is a challenging situation! I'd try flashing the stock ROM once more, just on top of the one you already did using Odin and see if it boots this time.
If it didn't, see if Samsung kies would recognize your phone on download mode and get kies to flash the proper stock rom because I know kies does a full wipe before flashing automatically every time.

Yea, you shouldn't need to wipe anything if you use the correct tar in Odin, it should do it automatically. I would try again as stated above. Are you sure you have the correct tar file?

Thank you so much!!
The problem is that I was trying to flash an older firmware to use Towelroot. I've flashed the same firmware and now it's working again!
Now, I really need to root because I need virtual keys (hardware ones don't work) and i have to edit build.prop file.
What's the easiest way to root on a Lollipop firmware? I don't care about Knox and warranty void.
Also, I already tried CF-Auto Root but when the phone rebooted It gave me this message: "RECOVERY IS NOT SEANDROID ENFORCING" and it didn't start anymore, that's why I needed to flash the stock firmware again.
EDIT: Nevermind. I flashed TWRP using Odin and then I flashed SuperSU in the recovery. I've booted in the recovery using "adb reboot recovery". Thanks again!

Glad you got it working!

Please Help Very Frustrated.

hello guys,
i bought a used galaxy s5 from someone running Poland Android lollipop 5.0 and it shows the model as SM-G900F When i try to root it with CF-Auto-Root-klte-kltedx-smg900f It gets stuck on the boot screen saying
"1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)"
i googled alot and flashed Phillz recovery which removed the error above but when i go to recovery its the stock recovery? .... I cant install twrp-2.8.7.0-klte.img.tar Either because after flashing it when i go to recovery its stock recovery again. Activation lock is off, SE for Android status is "enforing" does this mean this phone has a locked bootloader? Maybe this phone was on At&T, Sprint or Verizon and the last owner flashed 900f firmware on it to make it look carrier free but it maybe a carrier phoone? Please help me i am very very frustrated right now. i dont even know what recovery is seandroid enforcing means.....:crying::crying::crying:

dork997 said:
hello guys,
i bought a used galaxy s5 from someone running Poland Android lollipop 5.0 and it shows the model as SM-G900F When i try to root it with CF-Auto-Root-klte-kltedx-smg900f It gets stuck on the boot screen saying
"1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)"
i googled alot and flashed Phillz recovery which removed the error above but when i go to recovery its the stock recovery? .... I cant install twrp-2.8.7.0-klte.img.tar Either because after flashing it when i go to recovery its stock recovery again. Activation lock is off, SE for Android status is "enforing" does this mean this phone has a locked bootloader? Maybe this phone was on At&T, Sprint or Verizon and the last owner flashed 900f firmware on it to make it look carrier free but it maybe a carrier phoone? Please help me i am very very frustrated right now. i dont even know what recovery is seandroid enforcing means.....:crying::crying::crying:
Click to expand...
Click to collapse
Akalsemann said:
Ok guys, try this.
1. Download philz kernel that matches your modem number. I think philz_touch_6.26.6-klte.tar.md5 works good.
2. Put it in ODIN on PDA/AP
3. Uncheck "Auto Reboot" and make sure Re-Partition is NOT CHECKED (keep F. Reset time)
4. Flash
5. It will say RESET on Odin and nothing further when it is done so just wait 2-3 minutes when RESET appears to be entirely sure that the procedure is done.
6. Pull out phones battery.
7. Put it back in and now go into Recovery directly (Vol up+home+power)
8. ???
9. Profit
Hopefully this might work, i think i did the same
Click to expand...
Click to collapse
Try that

Akalsemann said:
Try that
Click to expand...
Click to collapse
Kindly note that i am able to boot fine now, but the recovery wont stick and whenever i try to root this seandroid error happens

Did u do the following steps correctly
it should work bro
Been there
done the same process
thanx again Akalsemann

vinura kithmal said:
Did u do the following steps correctly
it should work bro
Been there
done the same process
thanx again Akalsemann
Click to expand...
Click to collapse
yes i entered philz recovery > selected format to install new rom > now stuck on samsung logo maybe it removed rom files. Now downloading flash roms from sammobile. Dont know if it will let me root it or not. can u please explain what this error is and why is it caused?

dork997 said:
Kindly note that i am able to boot fine now, but the recovery wont stick and whenever i try to root this seandroid error happens
Click to expand...
Click to collapse
You need to just boot into download mode (voldown+home+power) then push volup to enter download mode
Use Odin to flash trwp 2.8.6.0 tar file in AP spot
Download a pre rooted rom of your choice for g900f
Place on sd card
Reboot to twrp by holding volup+home+power immediately during start of boot
Flash the rom you just downloaded
Now you'll be rooted
(That's what I did in order to get my phone rooted after installing the newest stock lollipop ota)
Sent from my SM-G900F using Tapatalk

dork997 said:
yes i entered philz recovery > selected format to install new rom > now stuck on samsung logo maybe it removed rom files. Now downloading flash roms from sammobile. Dont know if it will let me root it or not. can u please explain what this error is and why is it caused?
Click to expand...
Click to collapse
Common bro
u haven't rooted your device,
u have to flash the supersu zip to get the root access
http://download.chainfire.eu/supersu
first download this file and place it in your device storage,once u pull the battry off and put it back in go straightly to the recovery
select install zip and flash the supersu.zip
then reboot it,after the first boot then go to the recovery and
install your custom rom

Swimguy14 said:
You need to just boot into download mode (voldown+home+power) then push volup to enter download mode
Use Odin to flash trwp 2.8.6.0 tar file in AP spot
Download a pre rooted rom of your choice for g900f
Place on sd card
Reboot to twrp by holding volup+home+power immediately during start of boot
Flash the rom you just downloaded
Now you'll be rooted
(That's what I did in order to get my phone rooted after installing the newest stock lollipop ota)
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
vinura kithmal said:
Common bro
u haven't rooted your device,
u have to flash the supersu zip to get the root access
http://download.chainfire.eu/supersu
first download this file and place it in your device storage,once u pull the battry off and put it back in go straightly to the recovery
select install zip and flash the supersu.zip
then reboot it,after the first boot then go to the recovery and
install your custom rom
Click to expand...
Click to collapse
I followed instructions given earlier to install philz recovery, i opened it by booting into it immediately i selected format for new rom install. after that i am stuck on samsung logo i think the old rom is now deleted. Now i am downloading fresh 5.0.2 UK from sammobile i will download it and try to root it normally with flashing CF ROOT via odin. if it does not work then i will do what u guys said. I dont know if TWRP will work by the same method (booting immediately into recovery) but philz recovery did. And i will also try flashing a prerooted Rom. What i dont understand is that why is this happening in the first place? i had an alpha before i could enter into TWRP normally i rooted it with CF AUTO root normally...no errors or anything why is this happening on my S5? the last owner must have done something weird with it ...i am trying to figure out why is this happening in the first place. Appreciate ur feedback.

I also dont know why this is happening
and yeah
i had all the galaxy S series upto S5 and this the only device that is not rooting with CF-auto root
the latest updates from samsung may have done something i dnt knw
and eralier mentioned method worked 100% for me and i did root my device like that
And last owner may b or may not done anything with it because my device is a brand new and still i had that issue

[A700FD] Root Problem galaxy A7

OK guys,
well after i updated to new lolipop via kies i didn't like it so i downgraded again to kitkat 4.4.4. Now its been almost 2 weeks trying everything i know and can to root my phone again but so far i can not .
i used CF-Auto-Root-a7lte-a7ltexx-sma700fd with base "A700FDXXU1AOA2_HOME.tar" all via odin and still won't work everytime i try to root i get this stupid error "Recovery is not Seandroid Enforcing set | warrnty bit: recovery"
i tried everything wipe date-hard factory reset .... everything it just won't get done -_->
so i tried kingroot and now boom it worked BUT i want to install SuperSu and it won't install bianry i tried everything from supersu me to terminal console trick and still won't get done and i need SuperSu coz i like it more and it works better with Lucky Patcher plus i already got it premium XD
so what did i do wrong? why i can't root it and get this stupid error ?
P.S
1-in odin mode there is this blue text 'Secure download on "
2-could this all relate to knox some how ?

"Recovery is not Seandroid Enforcing set warranty bit: recovery" is not an error, its a warning and means nothing.
When downgrading to kitkat you need to wipe the data partition.
Flash the stock firmware, wipe the Data partiton, boot to android (10mins), reboot to download mode, flash cfautoroot.
If cfautoroot doesn't work flash TWRP then flash Supersu.

ashyx said:
"Recovery is not Seandroid Enforcing set warranty bit: recovery" is not an error, its a warning and means nothing.
When downgrading to kitkat you need to wipe the data partition.
Flash the stock firmware, wipe the Data partiton, boot to android (10mins), reboot to download mode, flash cfautoroot.
If cfautoroot doesn't work flash TWRP then flash Supersu.
Click to expand...
Click to collapse
u mean installing CF-Auto-Root-a7lte-a7ltexx-sma700fd via Odin again but after re-install the firmware and wipe data partition?
also why would i tried to flash TWRP before and it caused the phone to freez in samsung logo with same error ""Recovery is not Seandroid Enforcing set warranty bit: recovery""
?

OnMission said:
flash cfautoroot? u mean installin it via Odin ? and can i have link for it please ?
also why would i tried to flash TWRP before and it caused the phone to freez in samsung logo with same error ""Recovery is not Seandroid Enforcing set warranty bit: recovery""
?
Click to expand...
Click to collapse
You already have it: CF-Auto-Root-a7lte-a7ltexx-sma700fd
Are you sure you used the correct TWRP?

ashyx said:
You already have it: CF-Auto-Root-a7lte-a7ltexx-sma700fd
Are you sure you used the correct TWRP?
Click to expand...
Click to collapse
i don't know ? how can i till ? i clicked on vol up +home button+lock button and open recovery mode ( before trying TWRP)

OnMission said:
i don't know ? how can i till ? i clicked on vol up +home button+lock button and open recovery mode ( before trying TWRP)
Click to expand...
Click to collapse
Which TWRP did you flash -link?

ashyx said:
Which TWRP did you flash -link?
Click to expand...
Click to collapse
this one here
http://forum.xda-developers.com/android/development/recovery-galaxy-a7-t3085266

OnMission said:
this one here
http://forum.xda-developers.com/android/development/recovery-galaxy-a7-t3085266
Click to expand...
Click to collapse
I don't think that is for your device.
This one is t700fd: http://forum.xda-developers.com/showthread.php?t=3253126

ashyx said:
I don't think that is for your device.
This one is t700fd: http://forum.xda-developers.com/showthread.php?t=3253126
Click to expand...
Click to collapse
i tried it all again and it worked like charm i flashed using same link verion i posted above and it worked
after hard reset>flash frimware>using odin to root it worked i think the problem was in the frimware i used
thanks guys for helping out

how did u downgrade from 5.0.1 to 4.4.4. pls explain in detail

SM-G900F: can not boot ROM and Recovery

hey guys,
first of all: S5 was not rooted and I did never flash a custom rom on this phone
a few days ago my S5 hang up and then rebooted.. it then stucks at the bootloader ("Set Warranty Bit : kernel").. I tried entering the recovery, but it doesn't work..
I tried to flash the recent stock rom (6.0.1) using download mode and Odin 3.12 and managed somehow to get to the recovery (couldn't boot android).. I wiped data and cache but that doesn't help either..
I tried flashing
- 6.0.1 (stock)
- 5.0 (stock)
- CWM recovery
- Bootloader and Modem
after flashing the rom it stucks at "Set Warranty Bit : recovery", after flashing bootloader and modem at "Set Warranty Bit : kernel" again..
thanks for your help..

stefan9310 said:
hey guys,
first of all: S5 was not rooted and I did never flash a custom rom on this phone
a few days ago my S5 hang up and then rebooted.. it then stucks at the bootloader ("Set Warranty Bit : kernel").. I tried entering the recovery, but it doesn't work..
I tried to flash the recent stock rom (6.0.1) using download mode and Odin 3.12 and managed somehow to get to the recovery (couldn't boot android).. I wiped data and cache but that doesn't help either..
I tried flashing
- 6.0.1 (stock)
- 5.0 (stock)
- CWM recovery
- Bootloader and Modem
after flashing the rom it stucks at "Set Warranty Bit : recovery", after flashing bootloader and modem at "Set Warranty Bit : kernel" again..
thanks for your help..
Click to expand...
Click to collapse
Try to reinstall the firmware using samsung smart switch

KillersEnergy said:
Try to reinstall the firmware using samsung smart switch
Click to expand...
Click to collapse
that doesn't work for me still getting "Set Warranty Bit : recovery"..

stefan9310 said:
that doesn't work for me still getting "Set Warranty Bit : recovery"..
Click to expand...
Click to collapse
Download the firmware from fw.updato.com(IMHO is better than sammobile because you can download firmware without speed cap) then extract boot.img and recovery.img from the firmware archive (tar.md5) that you have downloaded and using 7zip make a .tar archive with those file and flash the tar with odin

KillersEnergy said:
Download the firmware from fw.updato.com(IMHO is better than sammobile because you can download firmware without speed cap) then extract boot.img and recovery.img from the firmware archive (tar.md5) that you have downloaded and using 7zip make a .tar archive with those file and flash the tar with odin
Click to expand...
Click to collapse
doesn't work too still getting the same messages.. S5 tries now to boot rom on startup ("...kernel") again and when I try to boot the recovery, I still get "...recovery"..

stefan9310 said:
doesn't work too still getting the same messages.. S5 tries now to boot rom on startup ("...kernel") again and when I try to boot the recovery, I still get "...recovery"..
Click to expand...
Click to collapse
Are you sure that you are downloading the right firmware? What model do you have?

KillersEnergy said:
Are you sure that you are downloading the right firmware? What model do you have?
Click to expand...
Click to collapse
yes, pretty sure.. SM-G900F, as it was written in the title.. I used this one from here..

stefan9310 said:
yes, pretty sure.. SM-G900F, as it was written in the title.. I used this one from here..
Click to expand...
Click to collapse
So smart switch and firmware restore didn't work...the last thing you could try is that method but IT WILL ERASE ALL YOUR DATA exept external-sdcard but pull it out of the phone to be sure,if you have one...
So the method is:
1)Download samfirm from here: http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
2)Config it like that: Region= DBT,Model=SM-G900F,check this option: auto,binary nature,check CRC32 and decrypt automatically
3)extract the firmware from the zip in a folder and you should have 4 tar.md5 archives: BL,AP,CP,CSC (with their infos)
4)Download the latest version of odin (3.12.3 as of now) from here http://forum.xda-developers.com/showthread.php?t=2711451,open it and control that Auto-Reboot and F. Reset Time are checked and be sure that Re-Partition is NOT checked put the archives in their right place and flash the phone
5)If the phone doesn't boot,pull the battery for 20 sec and reboot in recovery then wipe data and cache

KillersEnergy said:
So smart switch and firmware restore didn't work...the last thing you could try is that method but IT WILL ERASE ALL YOUR DATA exept external-sdcard but pull it out of the phone to be sure,if you have one...
So the method is:
1)Download samfirm from here: http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
2)Config it like that: Region= DBT,Model=SM-G900F,check this option: auto,binary nature,check CRC32 and decrypt automatically
3)extract the firmware from the zip in a folder and you should have 4 tar.md5 archives: BL,AP,CP,CSC (with their infos)
4)Download the latest version of odin (3.12.3 as of now) from here http://forum.xda-developers.com/showthread.php?t=2711451,open it and control that Auto-Reboot and F. Reset Time are checked and be sure that Re-Partition is NOT checked put the archives in their right place and flash the phone
5)If the phone doesn't boot,pull the battery for 20 sec and reboot in recovery then wipe data and cache
Click to expand...
Click to collapse
doesn't work again phone tries to boot to recovery instantly with the same error message ("Set Warranty Bit : recovery").. so I didn't manage to wipe data and cache (again)..

stefan9310 said:
doesn't work again phone tries to boot to recovery instantly with the same error message ("Set Warranty Bit : recovery").. so I didn't manage to wipe data and cache (again)..
Click to expand...
Click to collapse
Does it boot in stock recovery?
Go to download mode and check for:
Current Binary
System Status
Knox Warranty Void

KillersEnergy said:
Does it boot in stock recovery?
Go to download mode and check for:
Current Binary
System Status
Knox Warranty Void
Click to expand...
Click to collapse
No, stock recovery was flashed nearly the whole time.. CWM recovery only 5min to check whether it would help..
Current Binary: Custom
System Status: Custom
Knox Warranty Void: 0x1 (2)

stefan9310 said:
No, stock recovery was flashed nearly the whole time.. CWM recovery only 5min to check whether it would help..
Current Binary: Custom
System Status: Custom
Knox Warranty Void: 0x1 (2)
Click to expand...
Click to collapse
Are you really sure that you have a G900F lol,the possibility are 2
1)the bootloader keys are corrupted so every recovery get recognized as custom(that's quite impossible)
2)you have a different phone number
I think that's the 2 because a stock recovery signed by samsung can't get recognized as custom and after a complete firmware reinstallaton custom binary status should be "Samsung Official"...
Try to pull the battery and read the info at "Model"

KillersEnergy said:
Are you really sure that you have a G900F lol,the possibility are 2
1)the bootloader keys are corrupted so every recovery get recognized as custom(that's quite impossible)
2)you have a different phone number
I think that's the 2 because a stock recovery signed by samsung can't get recognized as custom and after a complete firmware reinstallaton custom binary status should be "Samsung Official"...
Try to pull the battery and read the info at "Model"
Click to expand...
Click to collapse
yeah I know.. I'm also a "bit" confused..
that's where I get the Model from.. SM-G900F.. 100% sure..

stefan9310 said:
yeah I know.. I'm also a "bit" confused..
that's where I get the Model from.. SM-G900F.. 100% sure..
Click to expand...
Click to collapse
Do your phone boot now?
If it doesn't then probably the eMMc is broken...

KillersEnergy said:
Does your phone boot now?
Click to expand...
Click to collapse
nope.. tries to boot recovery instantly on startup but fails.. looks like this.. stuck at this message

stefan9310 said:
nope.. tries to boot recovery instantly on startup but fails.. looks like this.. stuck at this message
Click to expand...
Click to collapse
It happen when you flash wrong boot.img(kernel) or/and system.img or a complete different firmware...try to download a casual custom kernel (for G900F) and flash it
---------- Post added at 05:11 PM ---------- Previous post was at 05:02 PM ----------
stefan9310 said:
yeah I know.. I'm also a "bit" confused..
that's where I get the Model from.. SM-G900F.. 100% sure..
Click to expand...
Click to collapse
The last things i could think will solve the problem is try to downgrade to lollipop or kitkat or try another marshmallow firmware...if that doesn't work your phone is broken and you have to take it to a samsung service center and hope they doe sn't refuse your warranty due to knox 0x1...if they notice that you could try to say that the recovery error tripped knox even if it's stock
P.s.: Is your phone refurbished?

KillersEnergy said:
It happen when you flash wrong boot.img(kernel) or/and system.img or a complete different firmware...try to download a casual custom kernel (for G900F) and flash it
---------- Post added at 05:11 PM ---------- Previous post was at 05:02 PM ----------
The last things i could think will solve the problem is try to downgrade to lollipop or kitkat or try another marshmallow firmware...if that doesn't work your phone is broken and you have to take it to a samsung service center and hope they doe sn't refuse your warranty due to knox 0x1...if they notice that you could try to say that the recovery error tripped knox even if it's stock
P.s.: Is your phone refurbished?
Click to expand...
Click to collapse
I just flashed this kernel but same result..
I tried to downgrade yesterday but it also doesn't fix the problem.. well warranty is over since august..
nope.. was a new one

stefan9310 said:
I just flashed this kernel but same result..
I tried to downgrade yesterday but it also doesn't fix the problem.. well warranty is over since august..
nope.. was a new one
Click to expand...
Click to collapse
1)flash twrp boot it and place a boot.img on sdcard then go to advanced->terminal and exec:
dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
If it doesn't work
2)go to the folder where you have extracted samfirm firmware open the csc archive with 7zip and extract the .pit file in the same folder,then open odin place all the 4 file in the right place go to pit and place there the pit file you have extracted and this time CHECK the repartition flag if is not checked check it by yourself or the pit will not have any effect

KillersEnergy said:
1)flash twrp boot it and place a boot.img on sdcard then go to advanced->terminal and exec:
dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
If it doesn't work
2)go to the folder where you have extracted samfirm firmware open the csc archive with 7zip and extract the .pit file in the same folder,then open odin place all the 4 file in the right place go to pit and place there the pit file you have extracted and this time CHECK the repartition flag if is not checked check it by yourself or the pit will not have any effect
Click to expand...
Click to collapse
1) can not boot to recovery again..
2) failed to boot to recovery after reboot.. removed battery and started again.. show up "Installing system update" and after that "Erasing" but still failed to boot (rom / recovery).. Still the same information in download mode (Custom, Custom, 0x1 (2))

stefan9310 said:
1) can not boot to recovery again..
2) failed to boot to recovery after reboot.. removed battery and started again.. show up "Installing system update" and after that "Erasing" but still failed to boot (rom / recovery).. Still the same information in download mode (Custom, Custom, 0x1 (2))
Click to expand...
Click to collapse
I'm sorry but if even the repartition doesn't work your phone is probably dead ,i think something in the motherboard(that would mean it's a hardware failure and not software problem and i think is unsolvable even with a jtag) like an eMMc partially broken and/or some printed circuit "burned" and/or other hardware part necessary to boot the recovery,kernel stopped working and that would explain:
1)why only download mode work(download mode is in sbl(secondary bootloader) partition that it's a part of the bootloader )
2)the bootloader behaviour("Set Warranty bit" even on stock partition)
3)and why none of the solutions worked
You could try to change the battery but i don't know if it will work...at least we tried