Related
i installed safestrap and tried updating to oudhs recovery through recovery.
it says it installs but when i reboot its still safestrap.
also tried installing twrp thorugh android emulator still have safestrap.
any suggestions?
You can't flash a recovery. You're going to have to return to stock
Edit how can someone with so many posts know so little about their device. If you're on ss you have to use the recovery that comes with it. Read the stickies
but before i flashed ss, i was already using oudhs.
the reason why i flashed ss i have no idea
bstylz911 said:
but before i flashed ss, i was already using oudhs.
the reason why i flashed ss i have no idea
Click to expand...
Click to collapse
So if you are on MDB or MDL (You must have been if you have the AT&T S4 and custom recovery) just Odin back to stock firmware and re-install whichever custom recovery you want (as long as it is for this phone and LOKId). Make sure you get the custom recovery on the phone before it tries to update to a firmware that you can't do anything (other then Safestrap) with. Search and read to find the information you need if you don't understand what I am telling you. And don't do anything to your phone until you do. Good luck.
Hi All,
I'm not sure if this is the right place to post this as I'm relatively new to posting on XDA. My girlfriend has a Galaxy S4 (I337) that I quickly and easily installed Cyanogenmod on. It's awesome and significantly better than TouchWiz. So, I bought an S4 off Ebay assuming it would be similar enough. It turns out this new S4 is an I9500 and before shipping it was updated to 4.3, which appears to lock the bootloader and prevent downgrading. I've tried Odin, Heimdall, ADB, Philz, Chainfire, Cofface, stock ROMs, etc with no luck. Today I did manage to root the phone and confirm root with TowelRoot. I'm wondering/hoping someone might have some resources to get CM on this thing. While I'd prefer not to brick it I am willing to take risks as I have a Razr (soft-bricked and unbricked) running CM and am relatively comfortable with computers/Linux.
I've been Googling and trying things for a month now and can't even find that much information on the locked bootloader. Any help would be greatly appreciated, thanks.
--
SL
The I9500 doesn't have a locked bootloader. You just can't downgrade from 4.3 to 4.2.2 with official roms. Same applies when you are running 4.4, then you also can't downgrade officially.
Just flash a custom recovery true Odin and flash away.
Why would you even want to downgrade? Are you sure you are picking the right files? You cant flash the files for the I337 on the I9500. So just go to the section for the I9500 roms and flash away.
Hi Lennyz1988,
Thanks for the quick reply. I don't specifically want to downgrade but that's the last option I've tried. Ultimately the goal is to put Cyanogenmod on the phone. When I attempt to upload any file via Odin I get "secure magiccode check fail : boot" (or fail : recovery) depending on what I'm flashing. All the reading I've done says that when these phones are updated to 4.3 a fix has been applied that stops Odin from working. Thus, I my last resort is/was to try and downgrade. As I said, I've been Googling for the last month and while few people have posted about this I have not found any solutions.
Hoping someone might have a solution or anything new to try that I haven't tried already, thanks again,
--
SL
Download the latest TWRP recovery:
http://techerrata.com/browse/twrp2/i9500
Fire it up in Odin under PDA. You need the .tar (DON'T EXTRACT IT).
If it fails:
- Different usb port
- Different cable
- Different pc
- Reinstall drivers
- Make sure Kies is not running the background.
Or you can use heimdall to flash it. Use the command line though:
heimdall flash --recovery nameoftherecovery.img (you need the .img instead of the .tar)
No luck there, Odin still fails with the same message. I have tried Heimdall on 2 different computers (4 different usb cables) and always get the libusb 12 error.
Since I have root access I figured I might be able to wipe the recovery partition from a terminal emulator. I copied recovery.img from the I9500 CWM to the internal sd card. I then went to /dev/block/msm_sdcc.1/by-name to figure out what partition is recovery, turns out its 21. I then did “dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21”. I then booted into recovery and it just hung up. I had previously found a stock recovery partition so I flashed that via Odin (the only file I have found that works flashing via Odin). I could then boot back into the normal recovery. I then tried flashing both recovery and cache with the CF Auto files (cache is partition 18). Same result, it just hangs when trying to boot into recovery. At one point I did manage to flash a recovery that then came up with a warning about “software installed that is not supported by AT&T” and I couldn’t get past that so had to flash the stock recovery again.
On a side note, I accidentally wiped the EFS partition in this process (if found a tutorial that shows the S3 had recovery in partition 10, which is EFS on the S4). As a result 1.) the menu didn’t pop up when I hit the power button and 2.) wifi didn’t work. So, I made an .img of the EFS partition on my GT-I337 and moved it to the I9500 and that worked restoring both. In case anyone makes the same mistake.
I have now also used CWM ROM Manager and GooManger and tried installing recovery that way with no luck.
Just check if the internal memory partitioning is correct ( number, size and format) (use fdisk or parsed).
ODIN will install according to the PIT file and if drivers and cables are OK it is no other explanation than that.
PS: do not trust heimdall data because it just read the PIT file and do not give the true info from the memory part.!
Uhm on the TWRP website they say that the I9500 has it on partition 10.....
This would be the proper partition based on their website:
mmcblk0p10
Are you absolutely sure you have an i9500? Because my guess is that you don't.....
Boot into download mode. What does it say your model is?
Because on the AT&T it's partition 21.... So my guess is that you are messing up....
Thanks everyone for the input/feedback,
Something I think I had forgotten to mention previously, when the initial root/recovery attempts didn't work I downloaded an app to verify it is a genuine Samsung as I have heard of very good knock-offs. It is genuine according to the app.
Good point/catch regarding the location of the recovery partition. Under About Phone it shows as an I9500 and always has. When in download mode it currently shows as I337 but I wasn't sure if that was simply a result of all my attempts so I figured best to go with the one I am certain has been the same since I bought the phone. I had been hesitant to try wiping the recovery with for the I337 as that is how I soft-bricked my RazrHD (ultimately un-bricked it).
Tonight I will try the I337 files and see if Odin is successful. Thanks again.
Damn! Turns out my phone is an I337. The hardward (under the battery) says I9500 and when I plug it into a computer it shows up as I9500. On the weekend I thought I read that there is now the ability to flash recovery and install CyanogenMod on I337 if its updated to 4.4.2. So, I donwloaded the firmware and flashed with Odin. It flashed successfully but now I realize I am mistaken and 1.) cannot flash recovery, and 2.) cannot downgrade. For the time being I have installed Nova Launcher and removed as much of TouchWiz as possible. It's not perfect but at least usable. I'd like to start researching what it would take to flash recovery on this phone but I suspect I'm too busy at this moment.
Thanks everyone for the help,
Ive been going so crazy trying for about 15 hours total now trying to root and get a custom recovery on my phone, for some reason, nothing will work. I do have alot of experience with rooting and ive done just about everything, attempting to get this phone to flash a custom recovery.
ATT SGH i337
4.4.4
KTU84P.I337UCUFNJ4
I am currently rooted, but i cannot get a custom recovery. I have just tried this method,
http://forum.xda-developers.com/showthread.php?t=2297033
with that tool, however after running it, it successfully flashes the recovery, then boots me into the Odin Mode Download screen with the picture of an android. Same thing with trying any other method of flashing a recovery. Can someone please tell me how to get past this, im so exhausted trying to fix this. I tried factory reseting my phone from the phones settings and even that brought me back to the download screen with a picture of an android. I cant get into any recovery at all! Stock or custom it sends me back to that screen.
How can i flash a custom recovery and get this working? Thank you guys in advance
You're on nj4. Safestrap is the only recovery you're going to be able to use. Read the stickies in the general forum
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You're on nj4. Safestrap is the only recovery you're going to be able to use. Read the stickies in the general forum
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
i installed the proper NJ4 safestrap apk and pressed install recovery, however it still says it is not installed "reboot to recovery" is greyed out. Upon booting into recovery, i am still stuck in Odin mode. Anyway for me to stop odin mode from continuing to come up instead of recovery?.
I would guess the system is looking for stock recovery, and it isn't there any more due to your flashing the CWM OUDHS recovery and/or TWRP. You probably need to put the stock recovery back.
I know and I've been trying to find out a way to do that. Could you help me if that's what I need to do? Once I reinstall stock recovery will safestrap work?
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
I would suggest that you flash nb1 then nb4, root and install safestrap. At this point, a clean install is your best bet. Refer to this thread in the general forum.
U can get stock recovery back by either flashing the whole stock firmware via odin or extracting the recovery image from the firmware and flashing it by its self via odin I don't know anything about safestrap as I'm on Canadian version some one else can hopfully help u out with tht
I read what you posted and I don't entirely understand. Could you point to me to a download a maybe dumb it down a bit?
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
How would I do that..
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
xstokerx said:
U can get stock recovery back by either flashing the whole stock firmware via odin or extracting the recovery image from the firmware and flashing it by its self via odin I don't know anything about safestrap as I'm on Canadian version some one else can hopfully help u out with tht
Click to expand...
Click to collapse
Exxoriscism said:
I read what you posted and I don't entirely understand. Could you point to me to a download a maybe dumb it down a bit?
Click to expand...
Click to collapse
Exxoriscism said:
How would I do that..
Click to expand...
Click to collapse
You are on NJ4 (I337UCUFNJ4). There is no flashable "whole stock firmware" for that version. There is a flashable whole stock firmware for the NJ1 version (I337UCUFNB1). Also, there is no easy way to "extract the recovery image out of the firmware and flash it by its self via odin." The reason for this is that you need a .tar archive to flash in odin, so if you extract just the recovery, you then need a Linux box, or a Linux virtual machine running on your windows pc to make the tar file from it.
This is why I suggested that you flash the NB1 full stock firmware, and then flash the upgrade to NJ4 from stock recovery, as outlined in the guide I linked.
As you asked for a little more detailed help, I'll try to walk you through following the Odin to Stock, Updating, Rooting, and Safestrap Guide.
First, read through post #1 and the FAQ in post #3. Next, you need to decide what version you want to end up with. Let's assume that you want to end with NJ4 -- KitKat 4.4.4. (If you want to end with OC3 -- Lollipop 5.0.1, then the instructions are a little different.)
In post #2, under the section titled NJ4 -- KitKat 4.4.4 expand Step 1 - Odin to stock. The files you need to download are at the top of this section. Follow the steps; they are pretty self explanatory. Part 1 installs full stock NB1, and Part 2 installs the upgrade to NJ4.
You are now on fully stock NJ4. If you want to root and install Safestrap, expand Step 2 -- Root and Install Safestrap. The files you need to download are at the top of this section. Again, the steps are pretty self explanatory.
That's it. If you want to now install custom firmware, you are ready, or you can just stay on stock if you prefer.
creepyncrawly said:
You are on NJ4 (I337UCUFNJ4). There is no flashable "whole stock firmware" for that version. There is a flashable whole stock firmware for the NJ1 version (I337UCUFNB1). Also, there is no easy way to "extract the recovery image out of the firmware and flash it by its self via odin." The reason for this is that you need a .tar archive to flash in odin, so if you extract just the recovery, you then need a Linux box, or a Linux virtual machine running on your windows pc to make the tar file from it.
This is why I suggested that you flash the NB1 full stock firmware, and then flash the upgrade to NJ4 from stock recovery, as outlined in the guide I linked.
As you asked for a little more detailed help, I'll try to walk you through following the Odin to Stock, Updating, Rooting, and Safestrap Guide.
First, read through post #1 and the FAQ in post #3. Next, you need to decide what version you want to end up with. Let's assume that you want to end with NJ4 -- KitKat 4.4.4. (If you want to end with OC3 -- Lollipop 5.0.1, then the instructions are a little different.)
In post #2, under the section titled NJ4 -- KitKat 4.4.4 expand Step 1 - Odin to stock. The files you need to download are at the top of this section. Follow the steps; they are pretty self explanatory. Part 1 installs full stock NB1, and Part 2 installs the upgrade to NJ4.
You are now on fully stock NJ4. If you want to root and install Safestrap, expand Step 2 -- Root and Install Safestrap. The files you need to download are at the top of this section. Again, the steps are pretty self explanatory.
That's it. If you want to now install custom firmware, you are ready, or you can just stay on stock if you prefer.
Click to expand...
Click to collapse
Yes and i did everything under the NJ4 Kitkat 4.4.4 section. I am rooted and everything worked except for safestrap. I open it and press install recovery and everytime it finishes it says "state:Not Installed". And reboot to recovery is greyed out. Upon manually rebooting into recovery mode, i am in normal stock recovery.
I cant use the selinux mode changer it says. To root i didnt use towelroot because installing the NC1 kernel disables my wifi connection, and since the phone has no service, i had to use KingO Root. I have confirmed root access using root checker. But Safestrap wont work.
What do i do? Is safestrap not working because i didnt root with towelroot? I assumed it didnt quite matter how i rooted. If it is because of towelroot, then how do i get towel root to work while on the NC1 kernel with no wifi and no cell service?
Update: I found a selinux Mode changer apk on xda and installed it. I tried it and safestrap still would not work and said "not installed". I also reflashed the NC1 Kernel and the same thing happened. I booted into recovery for confirmation.
I guess its maybe because i didnt root with towelroot? But it is impossible without phone service because flashing NC1 disables the wifi. Please reply as soon as you can
I can't help with your current issue with safestrap because I don't own this phone. I have worked on my son's S4, and a couple of others that have come through my hands. I have performed the exact process you just used with no issues.
I would suggest you post your issues in the guide thread where someone who has more experience with safestrap can help.
creepyncrawly said:
I can't help with your current issue with safestrap because I don't own this phone. I have worked on my son's S4, and a couple of others that have come through my hands. I have performed the exact process you just used with no issues.
I would suggest you post your issues in the guide thread where someone who has more experience with safestrap can help.
Click to expand...
Click to collapse
Can i move this thread?
Exxoriscism said:
Can i move this thread?
Click to expand...
Click to collapse
You can't move this thread into that one. But you can state your issue in that thread and then provide a link to this one for more info.
Sent from my Nexus 9 using XDA Free mobile app
My phone is a Samsung Note 3 SM-9005, currently it's stuck in an infinite bootloop even after removing the battery for an hour.
I get this message:
RECOVERY BOOTING ...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
... along with the Samsung SM-N9005 logo, a couple of beeps/buzzes and then it repeats ad infinitum.
Here's what I did over the last day to get to this sorry state of affairs:
1. Upgraded from Android 4.3 (the original operating system) to 5.0 using the Samsung N9005XXUGBOA5 ROM with Odin 3.12. This worked fine but the phone lost root.
2. I rooted the phone again using Odin and Chainfire Auto-Root. All good so far.
3. I installed TWRP (the official TWRP App 1.5, going by my records)
4. I flashed the latest custom recovery which would have been 3.0.x and this seemed to be fine. So far no problems.
5. I then got ideas above my lowly station, apparently. I wanted to flash one of the newer ROMs: [Rom][N7 Port][12.12.2016] [Multi-DPI] Phronesis Rom N7 v4.1 Feature Rich & Smooth
https://forum.xda-developers.com/ga...m-phronesis-mm-rom-v1-0-feature-rich-t3463244
6. In the instructions, it said to use TWRP recovery version 2.8.7. I found that and flashed it. (Yes, it was for the Samsung SM N9005).
7. I rebooted into recovery mode to make a backup with that 2.8.7 version.
8. Now I'm stuck in boot loop hell with ...
RECOVERY BOOTING ...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
... with the Samsung SM-N9005 logo, a couple of beeps/buzzes and so on (as stated above).
I've tried leaving the battery out for an extended period and this hasn't worked. The phone never gets to the stage where I can talk to it with Odin or get any kind of menu. Is the phone truly bricked now?
If so, was it a critical error to go from the 3.0.x TWRP recovery back to 2.8.7 for the purposes of this custom ROM upgrade?
If not, what can be done to regain control of the phone?
This is obviously an older phone as I've had it for about 3 years now, but I'd love to get it working again if possible. I really loved it and was planning to use it for a couple more years (hence the upgrade path I've explained above).
Can you boot into download mode? I suspect you flash the 4.3 version of twrp, you need a 4.4 version. This one https://dl.twrp.me/hlte/twrp-2.8.7.0-hlte-4.4.img.tar.html
Boot into download mode and flash it with odin.
I suggest flashing the latest stock ROM, flash the latest tar version of twrp with Odin, root with supersu.zip in twrp.
Stonedead, you were right on the money. I did what you suggested (Download mode) and that different TWRP file, and it worked.
Thanks so much.
Thanks audit13 also, although I didn't need to go that far to undo my mistake.
I got the same problem with my note 3. Thank you for the solution. Now how do I exactly get TWRP working on my phone. It is already rooted.
See TWRP thread.
Basics flash twrp tar through odin
Root is not needed to install the tar version of TWRP with Odin.
Thanks. Managed to get twrp working now. Also installed the note 8 Rom
Hi ok im having the same problem kinda follow the installation as posted,so i have note 3 sm-n9005 stock rom,root and replaced twrp 4.3 for 4.4 to install phronesis n7 v7 for note 3 followed all instructed then rebooted went to samsung boot then booted to twrp recovery ive been on it all day thinking what da hell ive done wrong?can someone instruct me of what i did or didnt do or have i completely mess stuff up?cheers anyone.
instructions .
Boot into recovery (say TWRP 2.8.7.0)
JJEgan said:
instructions .
Boot into recovery (say TWRP 2.8.7.0)
Click to expand...
Click to collapse
Sorry jjegan not following?it already reboots into twrp recovery after the galaxy note 3 logo appears for 20 seconds?I have read and followed threads that have same or similar problems but no avail im am totally lost and from reading this rom it sounds great if I can get there that is,so please simple instructions would be very helpful as I'm still learning very sorry for being dumb.
This rom
phronesis n7 v7 for note 3
all Aroma roms require TWRP 2.8.7 and not newer versions .As posted multiple times in the thread .
Search results for query: TWRP
forum.xda-developers.com
JJEgan said:
This rom
phronesis n7 v7 for note 3
all Aroma roms require TWRP 2.8.7 and not newer versions .As posted multiple times in the thread .
Search results for query: TWRP
forum.xda-developers.com
Click to expand...
Click to collapse
Hi JJEgan,thank you for the reply back much appreciated for your time so far,so do you mean twrp-2.8.7.0-hlte-eu.tar file?and not twrp 2.8.7.0-hlte-4.4 img.tar file?that's the one I am using to flash the rom with and having problems with.
Hi there again ok im so confused not sure which one,there are so many of the 2.8.7.0 versions with 4.3 or 4.4-img.tar im not sure if im downloading 4.4 or 4.3 as im still a noob and love tech,I have read threads upon this rom problems still can't get the grasp of the simple twrp version I have lte au version android 5,and when I read 2.8.7.0 im think is it 4.4 4.3 or just 2.8.7.0 tar file?I'm following the installation up into the problem of not booting up in stays In galaxy note 3 boot and I have removed the battery 5mi z replaced then recovery and factory reset then it does the same again and I have tried 3 times waited longer each time im thinking maybe go back to stock I don't think my phone is agreeing with me,jjEgan thanks for the info amd time im sorry if annoy you with a simple installation to you,still I have read and grasp the concept of twrp installer version yeah??
Only use 2.8.70 as said later versions wont flash that rom.
2.8.7.0 TAR flashed through Odin .
JJEgan said:
Only use 2.8.70 as said later versions wont flash that rom.
2.8.7.0 TAR flashed through Odin .
Click to expand...
Click to collapse
Thanks for the reply JJEgan,no I have finally fix the problem solution start over fresh instalments installed stock,flash twrp 4.4, flashd supersu threw twrp,wiped 3x install,instead of rebooting threw Aroma rebooted system threw twrp it loaded first go,thanks for the threads I took bits n pieces frm each threaded problems,cheers JJEgan love the version rom,one more thing what kernel would be better or what would your choice be cheers
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!