So.. hello.
Normally I don't come to forums to get help... but yeah. This is kinda bad.
I've got a little situation here.
I got my new Samsung Galaxy Note 4 (SM-N910F).
It was delivered with Stock 5.1.1.
First try:
I booted to the Downloader, fired up Odin, let it download the Autoroot.
Then I've got a bootloop.
Second try:
Booted into the Downloader, fired up Odin, let it install the 5.0.1 Stock ROM (Ending with 'BOB4')
It booted normally , then two things pop up constantly:
Something like "phone.xxxxxxxx.xxx Service crashed".
and "NFC crashed."
So I can't even unlock that phone.
Third try:
Booted into the Downloader, fired up Odin, let it install "N910FXXU1COI3_DevBase_alexndr".
Ended up in a Bootloop.
Then I tried to install the Bootloader aswell as the Modem and the Kernel, which are also in alexndr's Thread.
Ended up in the same Situation as the second try.
I don't no what to do anymore.
I'd really love to hear some help from you guys.
Greetings,
R3dRacoon
// Edit:
// It is a German Device from Telekom.
// If that helps or makes a little difference.
______________
UTC+1 (If I don't answer instantly)
And yeah, I've used search. And that for like the whole day.
Try Samsung care
R3dRacoon said:
So.. hello.
Normally I don't come to forums to get help... but yeah. This is kinda bad.
I've got a little situation here.
I got my new Samsung Galaxy Note 4 (SM-N910F).
It was delivered with Stock 5.1.1.
First try:
I booted to the Downloader, fired up Odin, let it download the Autoroot.
Then I've got a bootloop.
Second try:
Booted into the Downloader, fired up Odin, let it install the 5.0.1 Stock ROM (Ending with 'BOB4')
It booted normally , then two things pop up constantly:
Something like "phone.xxxxxxxx.xxx Service crashed".
and "NFC crashed."
So I can't even unlock that phone.
Third try:
Booted into the Downloader, fired up Odin, let it install "N910FXXU1COI3_DevBase_alexndr".
Ended up in a Bootloop.
Then I tried to install the Bootloader aswell as the Modem and the Kernel, which are also in alexndr's Thread.
Ended up in the same Situation as the second try.
I don't no what to do anymore.
I'd really love to hear some help from you guys.
Greetings,
R3dRacoon
______________
UTC+1 (If I don't answer instantly)
And yeah, I've used search. And that for like the whole day.
Click to expand...
Click to collapse
The third attempt was incorrect, that file is to be flashed from a custom recovery.
The second try might be because you did a dirty flash (Need to wipe data)
The first attempt boot-looped because in order to root in 5.1.1 you need a rootable kernel and the latest SuperSU (Not CF-Auto root)(Kernel is found in the Android Development thread)
Battlehero said:
The third attempt was incorrect, that file is to be flashed from a custom recovery.
The second try might be because you did a dirty flash (Need to wipe data)
The first attempt boot-looped because in order to root in 5.1.1 you need a rootable kernel and the latest SuperSU (Not CF-Auto root)(Kernel is found in the Android Development thread)
Click to expand...
Click to collapse
Thanks for the response.
What can I do to get a correct working System back? (Theoretically, I got time and bandwidth.)
Since flashing the Stock ROM did not quiet work.
medo sator said:
Try Samsung care
Click to expand...
Click to collapse
KNOX Flag is already 0x1. Means varranty is void, isn't it?
So I don't think they will help me.
R3dRacoon said:
KNOX Flag is already 0x1. Means varranty is void, isn't it?
So I don't think they will help me.
Click to expand...
Click to collapse
ok first flash twrp via odin then flash your 5.0.1 bootloader and modem then boot to recovery and wipe all systems and data then bootinto download mod and flash any custom 5.0.1 rom
medo sator said:
ok first flash twrp via odin then flash your 5.0.1 bootloader and modem then boot to recovery and wipe all systems and data then bootinto download mod and flash any custom 5.0.1 rom
Click to expand...
Click to collapse
I've already tried to flash TWRP via Odin, but I've never seen it.
Flashed recovery was for trltexx.
Getting to Recovery should be the same as getting to Download Mode, or?
Anyways. Will try it with tbltetmo and report back.
// Just installed the tbltetmo.
// Can't see how to get into the recovery.
// Am I missing something?
Update:
Just signed up at sammobile and downloaded the BOB6 (4.4 i think) for T-Mobile.
Flashed via Odin.
Seems like it does work again.
Currently its installing like 260 Apps.
Let's see.
// Edit: Nah. It got even worse.
// But I got a Recovery. So that's something.
IT ****ING WORKS NOW
Went into the recovery and cleared cache and data. (Kinda stupid I did not do it inb4)
Do a clean install in Odin. Since it came with stock android 5.1.1, then flash the 5.1.1 stock firmware in Odin. If you have a locked device of a specific carrier it will be even better to use the firmware made for that carrier only. And check the "Nand erase all" option in odin before hitting the start button to flash. That will erase all the data from ur phone and will do a clean install. Your phone must then boot normally. Also note that android 5.0 root file may not work for 5.1. Also check the model number before flashing.
Related
Hi, all
I have an S4, the I9505. I wanted to install a new KitKat-rom, the I9505_-_Official_Google_Edition_4.4.2_by_Jamal2367_Final-R1.2.
Then I wiped the device (I'm using CWM philz_touch_6.09.6-jfltexx.tar) but when installing the ROM, I get a weird '7'-error,
I forgot the real error.
Anyways: I thought: forget it and let's go back to stock.
So I rebooted in recovery, wiped/factory reset my s4 and rebooted. But it just comes back in Recovery?
What's wrong?
So then I thought: let's ODIN a factory-ROM, which I can download from SAMFIRMWARE.COM but since the file is
bigger than 1Gb I need to pay. Well, I don't care about the 5 euro's but I don't want to leave my creditcard stuff behind.
Any other options??
Thanks!
rommelrommel said:
Hi, all
I have an S4, the I9505. I wanted to install a new KitKat-rom, the I9505_-_Official_Google_Edition_4.4.2_by_Jamal2367_Final-R1.2.
Then I wiped the device (I'm using CWM philz_touch_6.09.6-jfltexx.tar) but when installing the ROM, I get a weird '7'-error,
I forgot the real error.
Anyways: I thought: forget it and let's go back to stock.
So I rebooted in recovery, wiped/factory reset my s4 and rebooted. But it just comes back in Recovery?
What's wrong?
So then I thought: let's ODIN a factory-ROM, which I can download from SAMFIRMWARE.COM but since the file is
bigger than 1Gb I need to pay. Well, I don't care about the 5 euro's but I don't want to leave my creditcard stuff behind.
Any other options??
Thanks!
Click to expand...
Click to collapse
Download and Flash Philz Recovery 6.09.2 via recovery then reboot recovery and then do a fullwipe and flash the Custom rom you want and you wont get that Error 7 anymore
Repulsa said:
Download and Flash Philz Recovery 6.09.2 via recovery then reboot recovery and then do a fullwipe and flash the Custom rom you want and you wont get that Error 7 anymore
Click to expand...
Click to collapse
Thanks, but ... your link wad dead. Did some searching, saw a newer version (6.13.1 from Feb 6).
Installed that without issues.
Booted in recovery, factory reset + davlik , installed the ZIP.
Same error: Status 7.
Or should I have used only the version you mentioned?
rommelrommel said:
Thanks, but ... your link wad dead. Did some searching, saw a newer version (6.13.1 from Feb 6).
Installed that without issues.
Booted in recovery, factory reset + davlik , installed the ZIP.
Same error: Status 7.
Or should I have used only the version you mentioned?
Click to expand...
Click to collapse
When i was clickin the file i gave you, it works tho but Yea feel free to download that version 6.09.2 and you should be fine flashing any custom rom.
Because of this error, yes, it won't boot to system. Been there. You should've made a backup. I just restored it and voila.
That error "status 7" seems to be the problem with Philz recovery, when I switched to TWRP I was able to flash any rom no problems.
Repulsa said:
When i was clickin the file i gave you, it works tho but Yea feel free to download that version 6.09.2 and you should be fine flashing any custom rom.
Click to expand...
Click to collapse
Hm, thanks again, I think there's much more going on.
I downloaded a 4.3 STOCK-rom, and in download-mode I was able to get a working phone again.
That is: apparently everything works BUT I cannot enable WIFI.
I saw another thread on that for a different phone.
But ... this is a phone from my employer ... I now have the KNOX Waranty VoId set to 0x1
I guess this is the reason for not being able to switch on WIFI ...
If I try to switch on wifi I get a security notice:
'your device's security has blocked an action that is not permitted. No further action is required'
If I pres on App-info, it comes out of KNOX ...
I guess this is also the reason for the Status-7 error ....
SOLVED!
When i was looking for the factory-ROM I ended at SamMobile. According to that page I 'landed' on, the latest factory-ROM for the I9505
was for 'Montenegro'.
I then downloaded the one specific for the Netherlands (where I live) and used ODON directly on top of the Montenegro-version,
no factory-reset.
After booting, WiFi was back aain, message about KNOX is gone. It's even rooted again, so it all works.
Yes, I still have the KNOX warranty Void 0x1 but I can access corporate e-mails so good to go.
Pfew ...
Hello,
many people out there say it's impossible to do a full unroot on the S4 Mini, but I'll prove them wrong:
If you have a custom recovery like clockworkmod installed, that's obvious for a rooted phone,
before flashing you'll have to flash an original Samsung stock recovery first.
Otherwise the after-reboot process doesn't work correctly and you'll still have status "custom".
So here is what I did step-by-step:
- I startet with a rooted Samsung stock rom (XXUAMG8)
- I let SuperSU unroot the device (one of it's options), then
- I went into system/accounts/backup&restore and did the full restore - reboot
- I installed an original Samsung stock recovery with Odin - reboot
- I flashed the original Samsung stock rom (XXUAMG8) with Odin.
Afterwards you can check in DL mode the status, it's all "Official".
Additional Notes:
On my phone, when I didn't flash the samsung recovery first, the system boot time increased to up to 5(!) minutes every time (not only the first one...)
And why would I want to unroot my phone?
The warranty is void anyway. The Knox flag remains 0x1.
Original Samsung Stock Recovery Request
Hello, friend!
Can you get me that "original Samsung stock recovery" you mentioned, please?
Recently, I flashed a CWM file on my GT-I9192 and it doesn't work properly.
I'm searching everywhere and I couldn't find anything that helped me out...
So you're my savior...:laugh
Please attach the file or show me the link... So you will help not just me, but too many people that just messed up their phones..:angel::good:
Best regards from Brazil.
If you do not want to flash a custom rom, you don't need cwm.
Instead, use saferoot
http://forum.xda-developers.com/showthread.php?t=2565758
...
work perfectly on my seranoltexx.
gogoland2002 said:
If you do not want to flash a custom rom, you don't need cwm.
Instead, use saferoot
...
Click to expand...
Click to collapse
This thread is about UNROOTING and not how to root...
cemimo said:
And why would I want to unroot my phone?
The warranty is void anyway. The Knox flag remains 0x1.
Click to expand...
Click to collapse
This how-to is about a phone with an older bootloader without knox.
So if you have a knox free bootloader, this description leads you back to full warranty conditions
help
Peter Semper said:
Hello,
many people out there say it's impossible to do a full unroot on the S4 Mini, but I'll prove them wrong:
If you have a custom recovery like clockworkmod installed, that's obvious for a rooted phone,
before flashing you'll have to flash an original Samsung stock recovery first.
Otherwise the after-reboot process doesn't work correctly and you'll still have status "custom".
So here is what I did step-by-step:
- I startet with a rooted Samsung stock rom (XXUAMG8)
- I let SuperSU unroot the device (one of it's options), then
- I went into system/accounts/backup&restore and did the full restore - reboot
- I installed an original Samsung stock recovery with Odin - reboot
- I flashed the original Samsung stock rom (XXUAMG8) with Odin.
Afterwards you can check in DL mode the status, it's all "Official".
Additional Notes:
On my phone, when I didn't flash the samsung recovery first, the system boot time increased to up to 5(!) minutes every time (not only the first one...)
Click to expand...
Click to collapse
I know this is an old thread and this is my first post.
I have tried doing these steps and my device still says custom I think I am using the wrong stock firmware I was on Vodafone UK firmware then rooted to Cwm 6.0.4.6 I am currently trying to unroot to receive ota update as kies doesn't work to update I did unroot with original firmware that was btu black edition I am guessing this shouldn't make a difference but if I am wrong then go ahead and laugh at me but I do need help with my phone
thanks
steve
mason01983 said:
I know this is an old thread and this is my first post.
I have tried doing these steps and my device still says custom I think I am using the wrong stock firmware I was on Vodafone UK firmware then rooted to Cwm 6.0.4.6 I am currently trying to unroot to receive ota update as kies doesn't work to update I did unroot with original firmware that was btu black edition I am guessing this shouldn't make a difference but if I am wrong then go ahead and laugh at me but I do need help with my phone
thanks
steve
Click to expand...
Click to collapse
flash twice the firmware in odin, sometimes baseband isn't flashed
Didn't work for me either.
Starting from CM11, wanted to flash latest stock ROM with KNOX boot loader removed - downloaded my local carrier-specific firmware from Samsung updates, then proceeded to use the tar and md5 -rt tools on a Mac, failed signature. So did it in Windows using 7zip and it managed to flash. Did it twice to ensure baseband was flashed.
Flashing the stock recovery then doing the same still gives me a custom version
Anyone has any ideas on how to return to stock? I'm on non-KNOX boot loader.
Sent from my SM-N9005 using XDA Premium 4 mobile app
I had cm 4.4.2 on my I9195 I have to re flash with odin to go back to clockwork mod then flash original firmware twice and it worked just waiting for the ota update now
problem
It did work flashing original firmware twice however I go into recovery mode and I have a dead android with a red triangle and the words no command
It works. I got "official" status and I can download software updates, but now I get dead android with red triangle when I go recovery mode with this message:
Code:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : NEE
Succesfully applied multi-CSC.
No command.
And when I select reboot it says "error," then reboots normally and everything works fine... But is there something wrong?
Tyhjäntoimittaja said:
It works. I got "official" status and I can download software updates, but now I get dead android with red triangle when I go recovery mode with this message:
Code:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : NEE
Succesfully applied multi-CSC.
No command.
And when I select reboot it says "error," then reboots normally and everything works fine... But is there something wrong?
Click to expand...
Click to collapse
Which recovery?
splitterzelle said:
Which recovery?
Click to expand...
Click to collapse
Samsung stock recovery which is attached in the first post.
Same prob.
Tyhjäntoimittaja said:
Samsung stock recovery which is attached in the first post.
Click to expand...
Click to collapse
Same here. I've got problems with that Android Stock recovery file. After flashing it, when I tried to go into recovery mode, the dead android logo appeared. However if I reflash CWM everything goes ok. Where can I find another stock android recovery file?, it seems that this one only works for some specific sort of models. Mine is: GT-i9195L. (the "L" doesn't really matter).
Thanks.
Good afternoon guys,
i have a big issue with my galaxy s5 SM-G900S (korean version). I bought it as a refurbished device. Knox was on 0x1 so something may have been modified.
It came with the stock (?!) android 4.4.2 from march14. I tried to update but it returned a registration error. Probably because knox is 0x1
In any case, I activated usb debugging and tried to root the phone using cfautoroot and the corresponding root file: CF-Auto-Root-klteskt-klteskt-smg900s.zip which I still assume to be the correct one.
I used odin for flashing. The device was properly connected (blue).
Everything seemed to go smooth until the phone restart when it said "recovery is not seandroid enforcing". I tried several times with both odin 3.07 and 3.09 but i cannot pass this step. I also tried the method to untick auto reboot, shut the phone down manually and boot into recovery mode but it failed.
This means I am now stuck in the bootloop. I can access download mode, but i cannot reach recovery mode. Also the phone is not recognized by the computer if i try to connect it to adb, kies etc. Odin seems to connect properly still.
Alright how should i proceed now?? My actual target is to flash a custom rom. I will need to go for a dirty flash now correct? Should I flash a stock rom with odin? If yes, which one?
Please support me a bit, I am very frustrated on this topic, especially cause I still dont realize my mistake......
Merry Christmas and greets from Bavaria, Germany.
cheeet
Flash the stock firmware to get out of boot loop. After flashing the stock firmware, everything should be working fine and booting again. Instead of using CF auto root, flash a custom recovery like TWRP and then use it to flash the SuperSU zip.
toxious651 said:
Flash the stock firmware to get out of boot loop. After flashing the stock firmware, everything should be working fine and booting again. Instead of using CF auto root, flash a custom recovery like TWRP and then use it to flash the SuperSU zip.
Click to expand...
Click to collapse
Alright, Im back to stock android 4.4.2 now. Works perfect, aside from registration. If I click on "update now" it shows: SKT-USIM required.
Can someone link a detailed guide for flashing cm13? I checked the web but i still dont entirely understand.
In any case I do not want to risk going into a tricky situation once more.....
Thanks in advance.
Greets, cheet
I've gotten no help at all with this. Very unlike this forum. My phone is a kltevew, which is straight talks version of a g900v. I need help, there are lots of great looking Roms that require you to have mm firmware I'd like to try!
Not sure why I'm getting g no responses on this. Surely someone must know something... The only response I got was not only not helpful but jerky and obnoxious. Doesn't anyone know how to upgrade the firmware on my phone? (And no, google has no answers for me on this.. I look everyday)
ddjr said:
Not sure why I'm getting g no responses on this. Surely someone must know something... The only response I got was not only not helpful but jerky and obnoxious. Doesn't anyone know how to upgrade the firmware on my phone? (And no, google has no answers for me on this.. I look everyday)
Click to expand...
Click to collapse
Download it with samfirm http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 (Model= SM-G900V Region= VZW) or from sammobile http://www.sammobile.com/firmwares/database/SM-G900V/ , do you know how to flash firmware with odin?
I do. Thanks so much for responding. Every time I try with Odin, a few different releases, it always gives me the error message fail. Can it be done with flashfire?
What stands in the log of odin when the flash completes?
Ill have to do it again to see... Be back in a bit!
I think it says FAIL! modem but I'll have to run it again... Brb
Last night I used flash fire to install firmware. That didn't get past the red Verizon logo, so I put twrp on it with Odin. Twrp showed it as dpd1, but it just wouldn't boot. So I wiped it once and flashed a ROM that requires mm firmware. Same thing, justbootloop. So I put stock back on it, then mokee 6.0.1. which works, I'm just not on mm firmware and all the great new roms are still unavailable to me.
ddjr said:
Last night I used flash fire to install firmware. That didn't get past the red Verizon logo, so I put twrp on it with Odin. Twrp showed it as dpd1, but it just wouldn't boot. So I wiped it once and flashed a ROM that requires mm firmware. Same thing, justbootloop. So I put stock back on it, then mokee 6.0.1. which works, I'm just not on mm firmware and all the great new roms are still unavailable to me.
Click to expand...
Click to collapse
Have you enabled the option to flash bootloader on flashfire setting?
What? No, I haven't... but do do right now. Thanks for the tip! Actually, where would I find it?
So would I do it in this order? Flash the dpd1 bootloader, then modem, them rom, then jrkruse patch? All in flash fire?
ddjr said:
So would I do it in this order? Flash the dpd1 bootloader, then modem, them rom, then jrkruse patch? All in flash fire?
Click to expand...
Click to collapse
It's in setting of flashfire...but only do it if odin doesn't work because do it from flashfire is more riskiy...
1)do a backup
2)check the bootloader flash option
3)install the firmware with all the wipe except internal storage(it mean that flashfire delete /data excluding /data/media/0 (sdcard) but include it in your backup copy because you never know )
4)wait till reboot skip setup wizard "spamming" the next button then install the rom with flashfire or twrp
On the flashfire site i found this:
Flash bootloaders
"This setting controls if FlashFire will attempt to flash bootloader partitions. By default, bootloader partitions are only read and never written. Even when enabled, flashing bootloader partitions may not succeed - many devices have protections in place against the bootloaders being overwritten.
Please note that flashing bootloaders is extremely dangerous. Any bug, error, or failure may result in an unrecoverable hard-brick. Do not use this feature unless you know exactly what you are doing.
Due to the danger of this feature, it is automatically turned off every time FlashFire starts. You have to manually re-enable it every time you want to use it.
If you must flash bootloaders, it is advised to use a bootloader-based flashing tool such as fastboot or ODIN to do it, as these are the safest methods. OTAs may also update bootloaders, and though slightly less safe than fastboot/ODIN, it is still much safer than having FlashFire flash bootloader partitions directly."
So i suggest to try to flash the firmware directly from odin first
No dice... still doesn't boot up past the red Verizon logo
ddjr said:
No dice... still doesn't boot up past the red Verizon logo
Click to expand...
Click to collapse
did you install the firmware in the "AP" box on odin? (after you factory reset your phone)
I did. At this point guess I'm lucky I haven't bricked my phone. Ive tried every possible combination, nothing works!
ddjr said:
I did. At this point guess I'm lucky I haven't bricked my phone. Ive tried every possible combination, nothing works!
Click to expand...
Click to collapse
Redownload the firmware extract it again,factory reset your phone,and try to install the firmware,maybe it's a bad download
Should I be flashing a kernel too? Will it even start/boot without the right kernel?
find out if you phone is refurbished. to install stock ROM you would need the main board and boot to be the same model.
if it's not, then you just need to install bootloader/modem without full ROM. look around in xda for bootloader/modem.
So I have a friend who decided to mess with his phone, of course without doing a backup, and now he's stuck in a situation that it can't boot even into recovery.
Currently all I see when booting to recovery:
Recovery Booting. . . . .
Set Warranty Bit : recovery
The phone is G900F
He has no idea what version was installed on it before.
I don't need the phone to boot, I need to recover the files on it.
Being a oneplus person myself, I'm not that familiar with samsung phones (my latest samsung was s2).
I've tried to install with odin (3.0.7 - if that matters) the following recoveries:
official twrp 2.8.7
twrp
cwm
All these recoveries showed "Recovery is not seandroid enforcing" message as well as the above when trying to boot into recoveries.
I've tried the official recovery as well:
https://forum.xda-developers.com/galaxy-s5/general/sm-g900f-stock-recovery-5-0-lollipop-t3228871
which removed the "seandroid" message, but that's all.
Not sure what I'm missing.
Any help would be appreciated!
Tahvok said:
So I have a friend who decided to mess with his phone, of course without doing a backup, and now he's stuck in a situation that it can't boot even into recovery.
Currently all I see when booting to recovery:
Recovery Booting. . . . .
Set Warranty Bit : recovery
The phone is G900F
He has no idea what version was installed on it before.
I don't need the phone to boot, I need to recover the files on it.
Being a oneplus person myself, I'm not that familiar with samsung phones (my latest samsung was s2).
I've tried to install with odin (3.0.7 - if that matters) the following recoveries:
official twrp 2.8.7
twrp
cwm
All these recoveries showed "Recovery is not seandroid enforcing" message as well as the above when trying to boot into recoveries.
I've tried the official recovery as well:
https://forum.xda-developers.com/galaxy-s5/general/sm-g900f-stock-recovery-5-0-lollipop-t3228871
which removed the "seandroid" message, but that's all.
Not sure what I'm missing.
Any help would be appreciated!
Click to expand...
Click to collapse
Hmm...
I see that your friend messed up his phone very well .....
Hopefully the eMMC memory is not corrupted becuase then only motherboard replacement would be necessary.
Summarising what you wrote:
1. you flashed "official recovery 2.8.7" -> where did you get it from? 2.8.7 is the very old version!
2. you flashed unofficial TWRP very old (2014) recovery (I checked your link)
3. you flashed unofficial CWM very old (2014) recovery (I checked your link)
4. finally you flashed stock, from old OS 5.0 Lollipop recovery provided from entrusted source - nobody reported that it works in the thread.
I listed this for you in order to underline one thing - READ, READ, READ, ASK, ASK, ASK .... before flashing anything to the phone and tell it to your friend.
Le's start with flashing from ODIN ver 3.12.7 (I am using it) this version of TWRP:
twrp-3.1.1-0-klte.img.tar for G900F which is the latest official recovery:
https://twrp.me/samsung/samsunggalaxys5qualcomm.html
Read how to flash it with odin method (when you open the link).
Edit: Are you sure the phone is SM-G900F? Please check model number on the label under battery (inside the phone).
Edit2: When you enter odin mode check phone model version as well - it is provided by installed bootloader.
Many40 said:
Hmm...
I see that your friend messed up his phone very well .....
Hopefully the eMMC memory is not corrupted becuase then only motherboard replacement would be necessary.
Summarising what you wrote:
1. you flashed "official recovery 2.8.7" -> where did you get it from? 2.8.7 is the very old version!
2. you flashed unofficial TWRP very old (2014) recovery (I checked your link)
3. you flashed unofficial CWM very old (2014) recovery (I checked your link)
4. finally you flashed stock, from old OS 5.0 Lollipop recovery provided from entrusted source - nobody reported that it works in the thread.
I listed this for you in order to underline one thing - READ, READ, READ, ASK, ASK, ASK .... before flashing anything to the phone and tell it to your friend.
Le's start with flashing from ODIN ver 3.12.7 (I am using it) this version of TWRP:
twrp-3.1.1-0-klte.img.tar for G900F which is the latest official recovery:
https://twrp.me/samsung/samsunggalaxys5qualcomm.html
Read how to flash it with odin method (when you open the link).
Edit: Are you sure the phone is SM-G900F? Please check model number on the label under battery (inside the phone).
Edit2: When you enter odin mode check phone model version as well - it is provided by installed bootloader.
Click to expand...
Click to collapse
First, thank you for trying to help me!
Please see attachments:
https://drive.google.com/folderview?id=1euC7-CoBeeUQxTGXQnPPgRE2-5VxFXLh
You can see that it is indeed g900f. I've also checked under the battery.
I've flashed the recovery you asked, however I could not find odin 3.12.7 only 3.12.10, so I've flashed with that (the odin thread on xda does not provide a link for 3.12.7 download).
You can see that it's still not booting with that recovery, it's just stuck at "booting recovery" screen.
I'm thinking perhaps it has a bad bootloader? How would you suggest to proceed?
Tahvok said:
First, thank you for trying to help me!
Please see attachments:
https://drive.google.com/folderview?id=1euC7-CoBeeUQxTGXQnPPgRE2-5VxFXLh
You can see that it is indeed g900f. I've also checked under the battery.
I've flashed the recovery you asked, however I could not find odin 3.12.7 only 3.12.10, so I've flashed with that (the odin thread on xda does not provide a link for 3.12.7 download).
You can see that it's still not booting with that recovery, it's just stuck at "booting recovery" screen.
I'm thinking perhaps it has a bad bootloader? How would you suggest to proceed?
Click to expand...
Click to collapse
Ok. Let's continue ... I hope (as I had very similar situation) that the phone is not hardbricked and eMMC memory is not corrupted -> I faced this on my phone and finally had to replace motherboard.
But let's be optimistic:
1. For data recovery - I don't have a silver bullet for this but I found this software: http://www.recover-android-iphone.com/recover-android/how-to-recover-data-bricked-samsung.html
It needs working odin mode so under condition that it supports s5 G900F it should be able to restore some data.
2. For unbricking - I recommend to flash via odin the latest official Samsung stock firmware dedicated to your friend's country/region:
https://www.sammobile.com/firmwares/galaxy-s5/SM-G900F/
You must be registered to download the software. Link for odin 3.12.7 is available on the bottom of the download page.
Just to underline - odin flash most probably (anybody please confirm that) will wipe your data so be aware of that.
Good luck.
Many40 said:
Ok. Let's continue ... I hope (as I had very similar situation) that the phone is not hardbricked and eMMC memory is not corrupted -> I faced this on my phone and finally had to replace motherboard.
But let's be optimistic:
1. For data recovery - I don't have a silver bullet for this but I found this software: http://www.recover-android-iphone.com/recover-android/how-to-recover-data-bricked-samsung.html
It needs working odin mode so under condition that it supports s5 G900F it should be able to restore some data.
2. For unbricking - I recommend to flash via odin the latest official Samsung stock firmware dedicated to your friend's country/region:
https://www.sammobile.com/firmwares/galaxy-s5/SM-G900F/
You must be registered to download the software. Link for odin 3.12.7 is available on the bottom of the download page.
Just to underline - odin flash most probably (anybody please confirm that) will wipe your data so be aware of that.
Good luck.
Click to expand...
Click to collapse
Why a full firmware is needed? Perhaps I can flash only the parts required to get into recovery? I count mount the phone from recovery, that's why it's my priority.
I would like to know also if odin will wipe everything if flashing a full firmware?
Tahvok said:
Why a full firmware is needed?
Click to expand...
Click to collapse
Because it is commonly recommended way to unbrick a phone.
Perhaps I can flash only the parts required to get into recovery?
Click to expand...
Click to collapse
Perhaps, yes. But:
1. I don't exactly know what restricts your recovery to run properly. Flashing separate recovery failed.
2. You, for example, could try flashing separately one of the latest bootloaders dedicated to G900F from BL section with odin but I doubt it would help.
I count mount the phone from recovery, that's why it's my priority.
I would like to know also if odin will wipe everything if flashing a full firmware?
Click to expand...
Click to collapse
As far as I know yes but I am not 100% sure because I didn't try that myself on s5.
I would appreciate if somebody else confirms that.
Many40 said:
2. You, for example, could try flashing separately one of the latest bootloaders dedicated to G900F from BL section with odin but I doubt it would help.
Click to expand...
Click to collapse
Can you suggest a bootloader for me? I would like to try that first.
Tahvok said:
Can you suggest a bootloader for me? I would like to try that first.
Click to expand...
Click to collapse
In my opinion, if odin mode works then bootloader should be OK. But as you wish -
tell me first what stock firmware will you later on trying to flash on your friends phone or in which country the phone will be operated.
Many40 said:
In my opinion, if odin mode works then bootloader should be OK. But as you wish -
tell me first what stock firmware will you later on trying to flash on your friends phone or in which country the phone will be operated.
Click to expand...
Click to collapse
Hong Kong
Tahvok said:
Hong Kong
Click to expand...
Click to collapse
Latest available Firmware version for Hong Kong is G900FZHS1CQD1 however I can't find a separate flashable bootloader for you.
Generaly, in my opinion you might try any of the latest bootloaders compatible with SM-G900F phone (here you can find a collection: https://forum.xda-developers.com/showpost.php?p=54094068&postcount=3, I am on G900FXXS1CQI4) but again:
1. I doubt it will help for entering recovery;
2. I still recommend to flash complete stock firmware to unbrick the phone.
However if you anyway decide to try with a bootloader, flash it with odin from BL section (untick auto reboot). Also turn off the phone before and after flashing and pull out battery for about 30 sec. It happens that bootloader doesn't flash properly at once even the odin says "PASS" so some people reported that they needed to repeat flashing a few times. I managed to flash bootloader at first time.
Unfortunateely the phone is not with me anymore, so I won't be able to continue testing. Thank you anyway for trying to help me! I really appreciate your help!