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!
Related
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.
Hello all...I have to first say that I HAVE been reading A LOT before I posted this question but I am somewhat confused. I have an SM-N900V with the following details :
- Rooted with Arabic Tool
- Android 5.0
- Build OF1
- Bootloader unlocked based on instructions at http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
I also have a SM-N900T for which I have been using CWM based recovery for many years and I am very happy with it. But I am not forced to change to the N900V and I have it rooted already but I am having a hard time finding the right recovery for it. I tried a philz CWM based recovery and it ended u getting the unit into a recovery bootloop so I have to flash the stock firmware from scratch and start again.
Can someone save me a few hours, and potentially more reflashes, and tell me which is the right recvery for this unit and how to install it? I am partial to CWM but I have read that it does not work. As long as I can take backups and restore them I am happy with TWRP. I have also read that SafeStrap is the only option. So again, I just need a straight answer so I can get this done.
Your feedback will be much appreciated!
thanks!
Did you mean "now forced" instead of "not forced" in the 2nd paragraph? The use later on of antecedent references such as "it" and "this phone" make it slightly confusing which phone you are talking about.
calderonr said:
I tried a philz CWM based recovery and it ended u getting the unit into a recovery bootloop so I have to flash the stock firmware from scratch and start again.
Click to expand...
Click to collapse
If you have unlocked the SM-N900V's bootloader, then a bootloop can be remedied by flashing with Odin only the partitions you need fixed, not the entire firmware set. This relieves you from having to re-customize a stock ROM and/or re-root. Moreover and more importantly having an unlocked bootloader means that your phone will no longer require blobs to be Sammy-signed: you can flash custom recoveries with Odin if you please. (You just need to learn how to create the *.tar.md5 files for Odin and you are in business - search for "Odin ustar md5")
So had you know that, you could have just prepared Odin flash tarballs for different recoveries and tried them out according to whim (It is also possible to flash a recovery from the rooted ROM as well, but you need to know how to escape from a perpetual failed recovery boot loop, I.e. : battery pull -> restart with VolDown+Home+Power -> Cancel)
I haven't ever put CWM on my SM-N900V, but can tell you that either the " hlte" or "hltevzw" variants of twrp should work just fine; as you are on OF1 firmware, the -4.4 versions should be used, e.g. twrp-3.0.2-0-hlte-4.4.img or twrp-3.0.2-0-hltevzw-4.4.img
PS Safestrap was the method of choice prior to bootloader unlock methods, and I believe does not work with OB6 or OF1 (possibly also NK1?).
.
calderonr said:
Hello all...I have to first say that I HAVE been reading A LOT before I posted this question but I am somewhat confused. I have an SM-N900V with the following details :
- Rooted with Arabic Tool
- Android 5.0
- Build OF1
- Bootloader unlocked based on instructions at http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
I also have a SM-N900T for which I have been using CWM based recovery for many years and I am very happy with it. But I am not forced to change to the N900V and I have it rooted already but I am having a hard time finding the right recovery for it. I tried a philz CWM based recovery and it ended u getting the unit into a recovery bootloop so I have to flash the stock firmware from scratch and start again.
Can someone save me a few hours, and potentially more reflashes, and tell me which is the right recvery for this unit and how to install it? I am partial to CWM but I have read that it does not work. As long as I can take backups and restore them I am happy with TWRP. I have also read that SafeStrap is the only option. So again, I just need a straight answer so I can get this done.
Your feedback will be much appreciated!
thanks!
Click to expand...
Click to collapse
As long as you are rooted and have the bootloader unlocked... Use Flashify to load TWRP which is an excellent recovery and does what you wish.
See this message:
http://forum.xda-developers.com/showthread.php?p=66380697
Sent from my SM-N900V using Tapatalk
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.
I just upgraded to the latest G935FXXU1BPH6 using Odin (v3.12.3). With past firmware releases, I was able to load TWRP twrp-3.0.2-2-hero2lte.img.tar using Odin and then proceed to root the phone.
However, with BPH6, TWRP refuses to boot. I try the volume-up+home+power sequence but TWRP recovery never starts. The phone just sits there on the boot screen.
I'm able to recover by re-flashing the BPH6 firmware but this leaves me thinking that the bootloader has changed in BPH6 and twrp 3.0.2-2 is no longer compatible.
1) Anyone else having this issue?
2) Any solutions or workarounds?
3) Do people think it would be safe to dowgrade the bootloader or entire firmware? I'm willing to try it but I'm a little concerned about bricking the phone.
kociubin said:
I just upgraded to the latest G935FXXU1BPH6 using Odin (v3.12.3). With past firmware releases, I was able to load TWRP twrp-3.0.2-2-hero2lte.img.tar using Odin and then proceed to root the phone.
However, with BPH6, TWRP refuses to boot. I try the volume-up+home+power sequence but TWRP recovery never starts. The phone just sits there on the boot screen.
I'm able to recover by re-flashing the BPH6 firmware but this leaves me thinking that the bootloader has changed in BPH6 and twrp 3.0.2-2 is no longer compatible.
1) Anyone else having this issue?
2) Any solutions or workarounds?
3) Do people think it would be safe to dowgrade the bootloader or entire firmware? I'm willing to try it but I'm a little concerned about bricking the phone.
Click to expand...
Click to collapse
In Odin flash an older firmware then reroot and wait for a root update from Chainfire and the TWRP team
I know a couple people that have done that.
"And on that bombshell!"
Sent from my Echoe powered AEL Driven G935F
When I first upgraded to the new firmware, I found the same thing that you did - I wanted to be able to flash custom roms and didn't know when or if TWRP and ROOT was going to be possible with this new firmware - so I used odin and reflashed July's Firmware and I was able to do so without any Issues - so then I decided to try to upgrade the AP/CSC/CP files from the latest update and replaced the bootloader with the bootloader from july's update and it worked.
Good luck - frankly I am Concerned. It appears that the latest bootloader from Samsung is LOCKED - I only hope someone is able to get root and twrp working - and I hope this is not an indication of future issues for rooting samsung phones....
mocsab said:
Good luck - frankly I am Concerned. It appears that the latest bootloader from Samsung is LOCKED - I only hope someone is able to get root and twrp working - and I hope this is not indication of future issues for rooting samsung phones....
Click to expand...
Click to collapse
No it isn't. Korean models had already been incompatible with official TWRP since firmware APG7 and I confirmed it working again when I replaced the kernel inside TWRP with one built from the latest source released by Samsung. So, someone needs to build a new TWRP recovery with BPH6 kernel source and everything will become fine again.
I didnt know that but it is very good news as far as I am concerned.
I have alwasy been fearful that Samsung was going to eventually lock down their international phones like they did to the US Variants - and when this originally happened to me, I started thinking that maybe my worst fears had come true. Thanks for the information....
I have the same question,but i soved it,i Flash the old BL and TWRP can working
BL version :BL_G935FXXU1APGH_CL8252943_QB10274482_REV00_user
Xlim said:
I have the same question,but i soved it,i Flash the old BL and TWRP can working
BL version :BL_G935FXXU1APGH_CL8252943_QB10274482_REV00_user
Click to expand...
Click to collapse
pls send related boot loader download link
same iussue .. some news??
by the way to use root now i put the old firmwere
FARSHOOD said:
pls send related boot loader download link
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24671318762848807
When flashing bootloader in Odin there is an options tab, there are checkboxes - Auto Reboot which is checked - Re-Partiion which is unchecked - and - F.Reset Time which is checked, I flashed new bootlaoder and modem and now my phone will not restart no matter the key combination I press. So Are those checkboxes suppose to be checked off or unchecked
Its making me scared i downloaded a recovery and flashed its via odin but always stock at boot logo with a red writing saying recovery is not seandriod enforcing
will it not progress past that? also, which S5 do you have? the model # will be SM-G900? but the ? will be a letter
model # of phone, what rom/firmware were u running .
which twrp version did u flash, provide a link to it.
dont be scared, most soft bricks are easily fixed, the red warning is normal, worst case scenario is flashing stock via odin
vincom said:
model # of phone, what rom/firmware were u running .
which twrp version did u flash, provide a link to it.
dont be scared, most soft bricks are easily fixed, the red warning is normal, worst case scenario is flashing stock via odin
Click to expand...
Click to collapse
this is correct. sammobile.com/firmwares is the best place ot get said firmwares, but its a SLLLLLOOOOWWWWWW download for non premium members. But its the offical place to get em. D/L your firmware, flash it in Odin and youll likely be back to new. Then you can go from there for root and TWRP
im using a samsung smg 900h and i tried flashing a twrp recovery and it wount always boot the recouvery but alwaysbstocks at samsung logo i did it several times and it finally boot into the recouvry once but still shows 0mb no storage .. after i removed the battery and inserted it back from there again it stoped loading the recovery can u help me please
pro_rikee said:
im using a samsung smg 900h and i tried flashing a twrp recovery and it wount always boot the recouvery but alwaysbstocks at samsung logo i did it several times and it finally boot into the recouvry once but still shows 0mb no storage .. after i removed the battery and inserted it back from there again it stoped loading the recovery can u help me please
Click to expand...
Click to collapse
go to sammobile.com/firmwares and download the firmware for your phone. its a slow download, but its THE BEST place to get the tar.md5 file. Flash it in Odin, and start over. That should get you up and running. The 0 mb thing is usually because a PIT file got flashed incorrectly.
pro_rikee said:
im using a samsung smg 900h and i tried flashing a twrp recovery and it wount always boot the recouvery but alwaysbstocks at samsung logo i did it several times and it finally boot into the recouvry once but still shows 0mb no storage .. after i removed the battery and inserted it back from there again it stoped loading the recovery can u help me please
Click to expand...
Click to collapse
be sure to flash correct fw for 900h
same as w/twrp, which one/method did u try
vincom said:
be sure to flash correct fw for 900h
same as w/twrp, which one/method did u try
Click to expand...
Click to collapse
this is correct, sammobile.com/firmwares is the most legit place to get the tar.md5 files, but the d/l is super slow if youre a free member. The wait is worth it tho as theyre straight from samsung. TWRP 3.0.2 is the best one ATM also. There are 3.0.2-1 and 3.0.2-2 as well, but dont use those as they are buggy as [email protected]
youdoofus said:
this is correct, sammobile.com/firmwares is the most legit place to get the tar.md5 files, but the d/l is super slow if youre a free member. The wait is worth it tho as theyre straight from samsung. TWRP 3.0.2 is the best one ATM also. There are 3.0.2-1 and 3.0.2-2 as well, but dont use those as they are buggy as [email protected]
Click to expand...
Click to collapse
3.0.2-2 is buggy in what way. its the only one afaik can lets me access my sdcards while in recovery via windows explorer
vincom said:
3.0.2-2 is buggy in what way. its the only one afaik can lets me access my sdcards while in recovery via windows explorer
Click to expand...
Click to collapse
3.0.2-1 and 3.0.2-2 have well documented instances of issues restoring NANDs from internal and external that those versions made themselves. Ive never seen a report of 3.0.2 having nand restore issues. Used to see it all the time on 3.0.2-1 and 3.0.2-2 when they first came out a while back. For those of us who flash tons of ROMS, a good nand is necessary and it has to be reliable because having to Odin flash due to a corrupted nand is annoying.
I was agreeing with you earlier btw. just trying to give additional info