Hi
I recently tried to fix my wifes Galaxy S5 SM-G900F (Nordic), but nothing seems to work.
Problems started after she made an update to 6.0.1. The phone started to reboot randomly.
Later it went into a reboot loop and would not start. I had trouble getting to the factory reset menu, but once it worked and I made a factory reset / wipe.
Same problem, the phone stayed in the recovery boot loop.
I brought it to Samsung service, and they said that they could not install any rom on it.. So I tried myself.
I flashed the factory rom (6.0.1) with odin3 SUCCESFULLY, but nothing would change.. Still same recovery boot loop.
I did the same again with an older version (5.0).. Same problem.
I cant even reach the factory reset menu any more.
Is there something left to try?
-George-
Jormakka said:
Hi
I recently tried to fix my wifes Galaxy S5 SM-G900F (Nordic), but nothing seems to work.
Problems started after she made an update to 6.0.1. The phone started to reboot randomly.
Later it went into a reboot loop and would not start. I had trouble getting to the factory reset menu, but once it worked and I made a factory reset / wipe.
Same problem, the phone stayed in the recovery boot loop.
I brought it to Samsung service, and they said that they could not install any rom on it.. So I tried myself.
I flashed the factory rom (6.0.1) with odin3 SUCCESFULLY, but nothing would change.. Still same recovery boot loop.
I did the same again with an older version (5.0).. Same problem.
I cant even reach the factory reset menu any more.
Is there something left to try?
-George-
Click to expand...
Click to collapse
I do not know if I understood correctly.
When you install the original ROM it got stuck at the boot of Samsung, right?
Have you been in recovery mode yet? If you can not try installing Twrp, that's what got me wrong, I had a similar case. Install with Odin.
And put a ROM for example: LineageOS.
Hi
Thanks for the info. I managed to install TWRP successfully, but I still cant reach the factory reset menu. It keeps on doing the boot loop with samsung logo.
Now after couple of unsuccessful reboot attempts the phone went into download mode by itself.
Could not do normal boot.
ddi: mmc_read failed
PRODUCT NAME: SM-G900F
CURRENT BINARY: Samsung official
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x1 (0)
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWERV: S1, T1, R1, A1, P1
SECURE DOWNLOAD : ENABLE
UDC START
I restarted into download mode and tried to install the stock rom with the pit file.
It would fail with and without re-partition:
Here without re-partition
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1205)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> rpm.mbn
<ID:0/007> sbl1.mbn
<ID:0/007> tz.mbn
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> modem.bin
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Size)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Next I deleted the hidden.img.ext4 and I got a PASS! (without the pit file and re-partition)
After a restart attempt i still have the recovery booting.... looping
Next I flashed the pit file and it would start to samsung galaxy s5 logo (without the recovery boot.... text on top) and do a restart loop.
I even did the recovery with kies, and it went through, but still I only get to recovery boot loop.
As a last resort i did also a NAND flash with odin. Still recovery boot loop
I think this phone is bricked for good..
Jormakka said:
Hi
Thanks for the info. I managed to install TWRP successfully, but I still cant reach the factory reset menu. It keeps on doing the boot loop with samsung logo.
Now after couple of unsuccessful reboot attempts the phone went into download mode by itself.
Could not do normal boot.
ddi: mmc_read failed
PRODUCT NAME: SM-G900F
CURRENT BINARY: Samsung official
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x1 (0)
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWERV: S1, T1, R1, A1, P1
SECURE DOWNLOAD : ENABLE
UDC START
I restarted into download mode and tried to install the stock rom with the pit file.
It would fail with and without re-partition:
Here without re-partition
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1205)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> rpm.mbn
<ID:0/007> sbl1.mbn
<ID:0/007> tz.mbn
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> modem.bin
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Size)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Next I deleted the hidden.img.ext4 and I got a PASS! (without the pit file and re-partition)
After a restart attempt i still have the recovery booting.... looping
Next I flashed the pit file and it would start to samsung galaxy s5 logo (without the recovery boot.... text on top) and do a restart loop.
I even did the recovery with kies, and it went through, but still I only get to recovery boot loop.
As a last resort i did also a NAND flash with odin. Still recovery boot loop
I think this phone is bricked for good..
Click to expand...
Click to collapse
Sequence? pressing and holding Volume Up, Home and Power? or this: ''well, you can try to pull the battery and hold the vol and home button while putting the battery back in. the power button isnt really needed to get it into recovery or download other than making it start the sequence''
Mate. When the Samsung service was not able to flash a ROM, you will not either. Had the same like you. After just 2 months of having this phone it started bootlooping. Tried everything. also the pit files. Flashing was no problem but the issue persisted. FLashed the stock ROM and brought it to the shop. They send it to samsung service and after a week I got a new device as the flash memory on the one that was bootlooping got defective somehow.
So well it´s not bricked as it still trying to boot but with a defective flash storage the results are almost the same as the needed data is corrupt due to defective memory cells.
Sorry guys mmc_read failure is due to bad memmory. It's a hardware issue. It's common in the note 4 series.
Related
Hello,
-sorry for my english I dont speak well but...
phone: I9505
I was testing cyanogemod 10.1.3 for a while but then I decided get back to stock rom, did full wipe and put this ROM I9505XXUBMF8 into Odin and start flashing but he said this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
-then I couldnt go to system, recovery just to download mode so I flashed TWRP.
(I tried another stock rom, odin, PC but always same problem.)
-then i tried get back CM 10.1.3 via TWRP and it flashed and work without problem.
-then I tried flash omega rom via TWRP and it flashed without problem but booting is very slow and during the logo Samsung it takes about 10mins to boot into system and device is very hot.
-Everything about Kies and antivirus is off.
-Using just original USB cable.
-what says download mode:
ODIN MODE
PRODUCT NAME: gt-i9505
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X1
CSB-CONFIG-LSB: 0X30
WRITE PROTECTION: ENABLED
START [224, 1440]
SW REV, CHECK FAIL : FUSED : 2 , BINARY : 1
Any ideas how to resolve this?
Thank you
you have a secured bootloader, you can not flash old firmwares, flash MH8
use search button, there is a lot of threads talking about this issue
samersh72 said:
you have a secured bootloader, you can not flash old firmwares, flash MH8
use search button, there is a lot of threads talking about this issue
Click to expand...
Click to collapse
Thank you so much, I was looking for something all day but i didnt sure what Im really looking for
I have a Sprint Galaxy S4 (SPH-L720), non-spark edition.
It is currently running the Euroskank CM12 Feb 22 nightly.
Everything is working well, except I no longer have any voice/text service. Data (4G LTE), however, works.
Sprint has told me to update my profile/PRL, however, I don't think those options exist in CM12? So I've decided to go back to stock.
I downloaded the L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5 file and am using Odin v3.09
It gets very far (>90%) in the install process before it fails:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Do I need a PIT file? Do I extract that from the L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar file?
The Odin screen now shows:
ODIN MODE
PRODUCT NAME: SPH-L720
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
Click to expand...
Click to collapse
I also just finished downloading the L720VPUFNG2_L720SPTFNG2_SPR file, it similarly, also errors out.
When I reboot the phone, it says it's in Emergency Recovery Mode and to connect it to Kies, but Kies doesn't recognize the phone.
Any help is greatly appreciated!
I (half) figured it out.
Tried using a different computer (both Windows 7 machines) to flash back to stock (L720VPUFNAE_L720SPTFNAE_SPR using Odin 3 v3.09) and it went through!
Hit a boot loop, so I factory reset, updated the profile/PRL/activated the device, and everything worked for about 10 minutes.
Then Sprint told me of an OTA update, I installed it, and now I have no service (voice, text or data). There are service bars shown in the system tray, but attempting to even dial out gives me a "Mobile network not available" error.
With no service, I'm unable to update profile/PRL/activate. Unsure how to proceed from here other than maybe trying to flash a different ROM completely then going from there to stock?
I called Sprint and all the lady tried to do was sell me an insurance plan so that I could take it into the store and their technicians could look at it.
@MrCodedude, Try flashing KT's TW kernel or Negamann's r50
JhoonB51 said:
@MrCodedude, Try flashing KT's TW kernel or Negamann's r50
Click to expand...
Click to collapse
It was recommended elsewhere to put the phone in airplane mode, reset, then take it out of airplane mode. That didn't work, but reseating the SIM card did.
I haven't used this Galaxy S4 in awhile, I wonder if there's a problem with the SIM (or maybe the enclosure). I'll probably hold off on flashing a non-stock kernel to see if it still acts up.
I'll also be sad if this is the reason why voice/text didn't work in CM12.
This morning I updated my Note 3 (SM-900W8 on the Canadian Rogers network) to 5.0.
I had rooted this device before then, and had used Titanium Backup to backup all my apps/data. When the initial OTA update failed, someone pointed out that it was because the phone was rooted. So, figuring I had this backup in hand, I factory-reset my phone and went through the update - though I used the Samsung KIES app as it was quicker to download the firmware update than over my phone's WiFi.
Once the phone was on 5.0, I went to restore the backup... and found that Titanium Backup only works when the phone is rooted. Oops.
So, I figure that I need to root my phone again. I find instructions on how to root a note 3 and start to work through it. I go to the link for "Download appropriate CWM or TWRP recovery for your Note 3" and find the one that says "KitKat/Lollipop Android 4.4.2 CWM Recovery" and pick the one "SM-N900W8 Canadian Note 3 – CWM Recovery", because 5.0 is 'Lollipop' and my phone is the SM-N900W8. I attempt to use this with Odin, and Odin reports 'FAIL!' and the phone is stuck on "Downloading - Do not turn off target !!'. I give this a while just in case things take a while to happen... and nothing does, so I figure it did fail. I have no alternative but to turn off the phone now.
And restarting it, the phone comes up in "ODIN MODE" with the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
The messages at the top of my phone on this screen are:
Code:
ODIN MODE
PRODUCT NAME: SM-900W8
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P2
SECURE DOWNLOAD : ENABLE
UDC START
I connect the phone up again, select the Recovery tool in Kies... and the phone is not detected. No matter what I try.
So then I try and download the official firmware N900W8_RWC_N900W8VLU2DOC4_N900W8OYADOC4 from Samsung Updates and try to use Odin to recovery it that way.
Again, the update fails... time and time again.
The Odin messages output is:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900W8VLU2DOC4_N900W8OYADOC4_N900W8VLU2DOC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I now have a bricked phone, and no idea how to fix it.
What can I do?
frysco said:
What can I do?
Click to expand...
Click to collapse
1. Reflash STOCK firmware 5.0 for your device: HERE. Factory reset your device when finish of boot.
2. Use TWRP (You can flash this ONE via ODIN) and root your device then.
3. Don't restore your data of android 4.4.2.
I've managed to fix things.
From other searching around, it seems that trying to use Odin via VMWare Fusion on a Mac is a 'known issue' where it gets stuck at this point.
Installed a trial version of Parallels and a basic Win XP install, re-flashed and it WORKED!
Code:
Hi, I have a serious problem with my Note 4 (SM-N910F).
Since the phone where lagging a lot from a few days, yesterday I choose to do a restore to factory condition, but after that it begun to bootloot.
So I flashed the latest 5.11 firmware available (this from Sammobile for Italy.
As soon as I did, I thought that all my problems were gone, but no. After the firmware, I wanted to get root, so after a quick search on Internet, I choose to get this kernel.
But after the flash of the kernel, I begun to have A LOT of problem. So I decided to flash again only the firmware.
Today I tried again to flash the TWRP recovery to flash the kernel .zip to get the root, but as soon as I did it, the phone didn't go beyong the Samsung logo.
I tried to take these steps: firmware-recovery-root, but after a while, ODIN gave me the error of "PIT binary missing" (or similar).
So, I downloaded a .PIT file for the 5.1.1 (I don't remember where) and I reflashed the firmware with the .PIT file and I didn't got any errors.
After I checked that there were no problems, I tried again to install that kernel.
And I tried again, and again, with different 5.1.1 firmwares.
A thing that I think it's important, it's that I noticed that sometimes while powering on the phone, it went automatically to Download Mode, with a message saying that it couldn't boot in "normal mode" and "MMC read error".
Also I noticed that everytime a powered off, or I rebooted the phone, I had to take off the battery in order to turn on again the phone. It seems like the phone never really turns off.
Now, the phone doesn't boot, the recovery isn't working, and the only thing I have is the download mode.
I tried on 2 pcs, with 2 usb cables, with 2 ODIN versions (3.09 and 3.10.6) to flash a couple of 5.1.1 firmware with and without the .PIT file.
Every time I start the flash on ODIN, while flashing the SYSTEM.img, the flashing stops and on the phone I get this message "ODIN: flash write failure".
I don't really know what to do, unless took it to a warranty center. I think that this problem could be caused by a faulty EMMC, or a brick caused by me.
PS: this is the log from ODIN
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910FXXU1COH4_N910FITV1COH1_N910FXXU1COH4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005>[COLOR="Red"] FAIL! (Write)[/COLOR]
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
UPDATE:
I successfully installed the TWRP recovery (twrp-2.8.6.0-trltexx.img.tar) with ODIN, so I wiped all the partitions but one: SYSTEM. The error is "E:Unable to mount '/system'.
At this point I think I messed up with the partitions.
UPDATE2:
I installed the CWM PhilZ, and with that I formatted the /system partition.
So I tried to re-flash the firmware with no success, but I tried again with the .PIT file and it succeeded!
Do you think I should retry to root it?
UPDATE 3:
So, after the first setup (google account, samsung account, time, etc.) I turned the phone off to insert my SIM card.
But as soon as the smartphone turned off, it powered on itself again in Download mode, showing me this error:
Could not do normal boot.
ddi : mmc_read failed
I think that maybe, there's a problem with the eMMC
Hi there
Do you want to flash the firmware?
i have s6 edge and when i choose file(in odin) for (PA) it falis so i tried for (CSC) and it worked.
Exactly the same thing happened to me. I have not been able to fin any solution to this topic. Every new you report will be very appreciated. If I find any solution y will post it here.
landerhazard said:
Exactly the same thing happened to me. I have not been able to fin any solution to this topic. Every new you report will be very appreciated. If I find any solution y will post it here.
Click to expand...
Click to collapse
i had a simialar problem with odin but my problem was that the adb wasnt successful i had to do it twice before it said successful then when i ran odin it worked not sure if this will help but i was stuck for days with the odin fail it was frustrating but good luck hope you find a solution
Hi there,
a friend gave me his daughters phone for repair. I replaced the screen and the USB socket, home button pcb. Apart from that I did not touch the phone. It booted nicely and worked well. It was all stock.
A week later he came back and the phone would not boot anymore. In the upper left corner was the "secure boot" and "waranty bit set" notice. I assume that somebody else tampered with the phone and unsuccessfully tried to root it. His daugter denies.
I wanted to bring the phone bach to stock. Downloaded
Code:
G900FXXU1CRA2_G900FDBT1CRB1_G900FXXU1CQK3_HOME.tar.md5
from sammobile and flashed it to the phone.
Latest German firmeware DBT (unbranded)
Flashed it using ODIN V3.13.3
ODIN showed success.
However. The phone got stuck in Bootup on the Samsung splash screen. I left it there for more than 20 min just to make sure it realy was stuck and removed the battery.
I tried to reflash and ran into diferent errors. The latest is:
Code:
ODIN OUTPUT
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> modem.bin
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone:
ODIN MODE
PRODUCT NAME: SM-G900F
CURRENT BINARY: Samsung Official
SYSTEMSTATUS: Official
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0X1 (1)
QUALCOM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T1, R1, A1, P1
SECURE DOWNLOAD : ENABLE
UDC START
Set Waranty Bit : System
SECURE CHECK FAIL : modem
Has anyone got and idea how to rescue the phone?
Kindest regards,
Gazorbeam
I've tried to flash an older firmeware version.
Code:
G900FXXS1CQD4_G900FDBT1CQA1_G900FXXU1CQA3_HOME.tar.md5
flashing with ODIN was successfull, but the phone does not boot.
RECOVERY BOOTING (blue text in upper left corner)
Hangs on splash:
Samsung Galaxy S5 / powered by andriod
Any ideas?
Regards, Gazorbeam
je lance odin apres avoir mit le firmware mais il affiche secure check fail pit
That´s what happen on my SM-G9900F a few weeks ago, what I did was using the TWRP and wipe all including the system and reinstalled again via ODIN the stock ROM.