Related
Hello folks. Today I did a cache, system, data wipe in TWRP on my G920F. After that I tried to restore a nandroid backup, but it failed and when I tried to restart it said there was no OS installed. So the phone wouldn't boot. I figured I did something wrong so I downloaded a 5.1.1 stock rom (UK) and flashed it with odin. But after the flash the phone would just bootloop. How can I revive the phone? Tried flashing the firmware again using another version of odin and also, I did a factory reset from the stock recovery, but no dice. Any ideas? Thanks in advance
Hey there,
check this thread here, should help (use TWRP to flash a ROM instead of Odin, links in thread).
Good luck!
Managed to make it work flashing another official rom, then factory reset. Lost all my files though...
Can be closed. Thanks!
Sent from my SM-G925F using Tapatalk
kendall1004 said:
Hey there,
check this thread here, should help (use TWRP to flash a ROM instead of Odin, links in thread).
Good luck!
Click to expand...
Click to collapse
How can i make TWRP flash a rom when Galaxy S6 doesn't have SD card to put the rom in the phone?
Immoblize said:
How can i make TWRP flash a rom when Galaxy S6 doesn't have SD card to put the rom in the phone?
Click to expand...
Click to collapse
Connect the phone to your PC and copy the ROM file to its root folder (just open "phone" and drop it there).
Using TWRP's "install" menu, you can browse your files and point it to this one; usually you're already in the right directory.
kendall1004 said:
Connect the phone to your PC and copy the ROM file to its root folder (just open "phone" and drop it there).
Using TWRP's "install" menu, you can browse your files and point it to this one; usually you're already in the right directory.
Click to expand...
Click to collapse
I wish that was so easy. I am on bootloop on my second day and i can fix it. I am getting crazy here. Nothing work - Kies, Smart Switch or Odin.
Immoblize said:
I wish that was so easy. I am on bootloop on my second day and i can fix it. I am getting crazy here. Nothing work - Kies, Smart Switch or Odin.
Click to expand...
Click to collapse
None of these three will help, i'm afraid.
The bootloop issue is a result of system write protection with 5.1.1 version, the phone tries to override a flashed recovery-
if it succeeds in automatically rebooting after you flashed, you're stuck on bootloop.
You have to flash a new kernel and root user via Odin, then flash TWRP and use it to install a new ROM.
A short description in this thread here, have a look.
As long as you can get into download mode, don't worry, nothings bricked :good:
kendall1004 said:
None of these three will help, i'm afraid.
The bootloop issue is a result of system write protection with 5.1.1 version, the phone tries to override a flashed recovery-
if it succeeds in automatically rebooting after you flashed, you're stuck on bootloop.
You have to flash a new kernel and root user via Odin, then flash TWRP and use it to install a new ROM.
A short description in this thread here, have a look.
As long as you can get into download mode, don't worry, nothings bricked :good:
Click to expand...
Click to collapse
THANKS A LOT for the info. I have today worked for about 8-9 hours to fix it. I will try read tomorrow on the site you put there and also read about how to put files to TWRP - since i don't have a SD card on my S6.
Immoblize said:
THANKS A LOT for the info. I have today worked for about 8-9 hours to fix it. I will try read tomorrow on the site you put there and also read about how to put files to TWRP - since i don't have a SD card on my S6.
Click to expand...
Click to collapse
Sleep over it, tomorrow is another day
Also, browse my recent postings here; most of them revolving around your issue, this will surely help.
kendall1004 said:
None of these three will help, i'm afraid.
The bootloop issue is a result of system write protection with 5.1.1 version, the phone tries to override a flashed recovery-
if it succeeds in automatically rebooting after you flashed, you're stuck on bootloop.
You have to flash a new kernel and root user via Odin, then flash TWRP and use it to install a new ROM.
A short description in this thread here, have a look.
As long as you can get into download mode, don't worry, nothings bricked :good:
Click to expand...
Click to collapse
Okay, i have done almost all of what you said.
But what im thinking about is the thread your refering to is to a S6 Edge and not for SM-G920F model.
But so far so good.
What kernel to you want me to flash? How can i root via Odin when i don't have USB-debugging on - But i can according to the thread, install SuperSU via TWRP.
I didn't know what kernel i had on, but i managed to install TWRP, install SuperSU via TWRP, pushing my stock rom to TWRP. But when installing the stock rom, it says "no md5 file found" or something like that. What am i doing wrong?
Immoblize said:
Okay, i have done almost all of what you said.
But what im thinking about is the thread your refering to is to a S6 Edge and not for SM-G920F model.
But so far so good.
What kernel to you want me to flash? How can i root via Odin when i don't have USB-debugging on - But i can according to the thread, install SuperSU via TWRP.
I didn't know what kernel i had on, but i managed to install TWRP, install SuperSU via TWRP, pushing my stock rom to TWRP. But when installing the stock rom, it says "no md5 file found" or something like that. What am i doing wrong?
Click to expand...
Click to collapse
Should work on both Edge and normal.
I have the G920F and did it this way, i also had problems, by the way:
http://forum.xda-developers.com/showpost.php?p=62550973&postcount=29
I recommend chosing an XtreStoLite ROM, the odexed version is an "improved stock" one, comes with a modified UniKernel and runs much smoother than stock.
Anyway, in TWRP, there is an option to skip md5 checking for backup files and for skipping the zipfile-check; not sure if you can also disable md5sum-checks.
Maybe you should try downloading the ROM from here or sammobile.de, verify the md5-sum yourself to make sure it is fine, and flash that one.
If TWRP doesn't think the ROM file is ok, it probably isn't ...
here's the odexed version of XtreStoLite:
http://forum.xda-developers.com/galaxy-s6/development/rom-xtrestolite-pure-edition-1-0-beta-1-t3082467
kendall1004 said:
Should work on both Edge and normal.
I have the G920F and did it this way, i also had problems, by the way:
http://forum.xda-developers.com/showpost.php?p=62550973&postcount=29
I recommend chosing an XtreStoLite ROM, the odexed version is an "improved stock" one, comes with a modified UniKernel and runs much smoother than stock.
Anyway, in TWRP, there is an option to skip md5 checking for backup files and for skipping the zipfile-check; not sure if you can also disable md5sum-checks.
Maybe you should try downloading the ROM from here or sammobile.de, verify the md5-sum yourself to make sure it is fine, and flash that one.
If TWRP doesn't think the ROM file is ok, it probably isn't ...
here's the odexed version of XtreStoLite:
http://forum.xda-developers.com/galaxy-s6/development/rom-xtrestolite-pure-edition-1-0-beta-1-t3082467
Click to expand...
Click to collapse
Okay, i have flashed TWRP, installed the kernel and Super SU (http://forum.xda-developers.com/gal...p-recovery-2-8-7-1-g925f-android-5-1-t3144866). But i can't flash the modem and bootloader for the XtreStoLite because it gives me Nand write error. I tried then to install XtreStoLite from TWRP which installed correctly but still doesn't fix the bootloop. I can read that i WILL get the bootloop if not using the correct modem and bootloader, but for some reason i am not able to flash them. Any help here? Or am i doing everything wrong here?
Immoblize said:
Okay, i have flashed TWRP, installed the kernel and Super SU (http://forum.xda-developers.com/gal...p-recovery-2-8-7-1-g925f-android-5-1-t3144866). But i can't flash the modem and bootloader for the XtreStoLite because it gives me Nand write error. I tried then to install XtreStoLite from TWRP which installed correctly but still doesn't fix the bootloop. I can read that i WILL get the bootloop if not using the correct modem and bootloader, but for some reason i am not able to flash them. Any help here? Or am i doing everything wrong here?
Click to expand...
Click to collapse
Alright, you have root access and TWRP is running.
All you have to do is install the ROM file (unextracted, as a .zip) from your phone`s root folder; if your model is a G920F, the bootloader should be 5.1.1 and work, no need to change.
When exactly does Odin give you the error message, right after you click start or after a few secs of flashing?
I suspect the issue to be related to first reboot after flashing the recovery,.
When finished flashing TWRP, did you successfully boot into recovery menu be pressing vol up+home+power?
If you saw the bootloop screen then, you`ll have to do it again, i'm afraid:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. (...) Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
I know, it`s annoying; but give it another try:
use Odin 3.1.0.7 (run with admin rights), do a full wipe and install TWRP 2.8.7.
When doing so and Odin gives you the "finished/successfully flashed" message, immediately press & hold the key combo to get into recovery; don`t wait for the scrteen to change or unplug the phone, you need to be damn quick here.
If you have done it right, you are in TWRPs recovery menu.
From there, install the XtreStoLite ROM after doing a factory reset; reboot and you should be fine.
Aaaarrgh we will get this thing running, goddammit
kendall1004 said:
Alright, you have root access and TWRP is running.
All you have to do is install the ROM file (unextracted, as a .zip) from your phone`s root folder; if your model is a G920F, the bootloader should be 5.1.1 and work, no need to change.
When exactly does Odin give you the error message, right after you click start or after a few secs of flashing?
I suspect the issue to be related to first reboot after flashing the recovery,.
When finished flashing TWRP, did you successfully boot into recovery menu be pressing vol up+home+power?
If you saw the bootloop screen then, you`ll have to do it again, i'm afraid:
I know, it`s annoying; but give it another try:
use Odin 3.1.0.7 (run with admin rights), do a full wipe and install TWRP 2.8.7.
When doing so and Odin gives you the "finished/successfully flashed" message, immediately press & hold the key combo to get into recovery; don`t wait for the scrteen to change or unplug the phone, you need to be damn quick here.
If you have done it right, you are in TWRPs recovery menu.
From there, install the XtreStoLite ROM after doing a factory reset; reboot and you should be fine.
Aaaarrgh we will get this thing running, goddammit
Click to expand...
Click to collapse
What i did was install stock android via Odin.
Flashed TWRP
Flashed Alex V kernel first, then SUPER SU.
Flashed XtreStoLite and it still gives me bootloop.
What i can't manage to do is after flashing TWRP, then i am not fast enough to press Shutdown button, home button, and volume up button before the Samsung logo appears. I think that is the problem.
:silly:
Immoblize said:
What i did was install stock android via Odin.
Flashed TWRP
Flashed Alex V kernel first, then SUPER SU.
Flashed XtreStoLite and it still gives me bootloop.
What i can't manage to do is after flashing TWRP, then i am not fast enough to press Shutdown button, home button, and volume up button before the Samsung logo appears. I think that is the problem.
Click to expand...
Click to collapse
That IS the problem, i think :fingers-crossed:
Solved the same problem at reddit, take a look: reddit thread
Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it.
So now, take a deep breath, lean back and try again.
As soon as you have clicked to start the flashing procedure, press the 3 butons firmly, simultaneously and quick as lightning-
hold them down till it boots into TWRP.
Come on, even i have managed it after a few tries
kendall1004 said:
:silly:
That IS the problem, i think :fingers-crossed:
Solved the same problem at reddit, take a look: reddit thread
Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it.
So now, take a deep breath, lean back and try again.
As soon as you have clicked to start the flashing procedure, press the 3 butons firmly, simultaneously and quick as lightning-
hold them down till it boots into TWRP.
Come on, even i have managed it after a few tries
Click to expand...
Click to collapse
HMMM. I see.
It's not possible for me to boot into TWRP without the Samsung logo appears. I press the start, the same time i press the start, i press Power, Home and Volume Up button but still the logo appears. It takes 4 sec and it have flashed the TWRP. It's not possible...
Immoblize said:
HMMM. I see.
It's not possible for me to boot into TWRP without the Samsung logo appears. I press the start, the same time i press the start, i press Power, Home and Volume Up button but still the logo appears. It takes 4 sec and it have flashed the TWRP. It's not possible...
Click to expand...
Click to collapse
So, for some reason you can't enter recovery mode.
This could be
a) TWRP is not installed correctly (did you use the .img ot the .tar-file? Odin needs the .tar-format: link )
or
b) the kernel you flashed doesn't work with this-
here is the one i have used to root my S6.
I would try to reflash above Unikernel first, if you used the .img-file of TWRP rather than the .tar to flash TWRP,
do it again with the .tar file instead.
If this fails, the last thing would be to flash a unmodified stock ROM to restore the original setup including the bootloader...
i will look into this now a little bit deeper, there has to be a workaround.
Best of luck for now, we stay in touch
EDIT: the developer of XtreStoLite recommends another way with Chainfire's root:
Flash CF-Root for your model with Odin - Make sure you have an custom recovery installed (I advise you to use TWRP) (2.8.7.1 or newer REQUIRED for v.2.1 > of this ROM!!)
Click to expand...
Click to collapse
If the bootloader is your problem, you can update to the newest versions of bootloader and modem for your model following these instructions:
edgarf28`s instructions
I will do this right now, for a new version of XtreStoLite was just released today and i will upgrade.
Keep me informed
kendall1004 said:
So, for some reason you can't enter recovery mode.
This could be
a) TWRP is not installed correctly (did you use the .img ot the .tar-file? Odin needs the .tar-format: link )
or
b) the kernel you flashed doesn't work with this-
here is the one i have used to root my S6.
I would try to reflash above Unikernel first, if you used the .img-file of TWRP rather than the .tar to flash TWRP,
do it again with the .tar file instead.
If this fails, the last thing would be to flash a unmodified stock ROM to restore the original setup including the bootloader...
i will look into this now a little bit deeper, there has to be a workaround.
Best of luck for now, we stay in touch
EDIT: the developer of XtreStoLite recommends another way with Chainfire's root:
If the bootloader is your problem, you can update to the newest versions of bootloader and modem for your model following these instructions:
edgarf28`s instructions
I will do this right now, for a new version of XtreStoLite was just released today and i will upgrade.
Keep me informed
Click to expand...
Click to collapse
I can enter the recovery mode (TWRP) but not before the Samsung logo appears when i install TWRP. I have tried many times and i still can't enter TWRP before the samsung logo appears for 1-2 secs.
I am not able to flash Edgar28s bootloader and modem because it always gives me nand write error fail. I think it's because i'm not rooted with CFautoroot - and to get rooted with that way, i have to have USB debuggin on which i don't have.
What i think is, that i was very close but i still can't manage to enter TWRP (after installing) without the samsung logo appears for 1-2 secs. Because what you said before "Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it."
So what do you think now?
And btw thanks for all the help so far. I'm trying my best and following your steps but i always think i'm very close. I'm also so close to destroy my phone but i've read so many places that "it's only a softbrick, that can be fixed very easy".
Immoblize said:
I can enter the recovery mode (TWRP) but not before the Samsung logo appears when i install TWRP. I have tried many times and i still can't enter TWRP before the samsung logo appears for 1-2 secs.
I am not able to flash Edgar28s bootloader and modem because it always gives me nand write error fail. I think it's because i'm not rooted with CFautoroot - and to get rooted with that way, i have to have USB debuggin on which i don't have.
What i think is, that i was very close but i still can't manage to enter TWRP (after installing) without the samsung logo appears for 1-2 secs. Because what you said before "Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it."
So what do you think now?
And btw thanks for all the help so far. I'm trying my best and following your steps but i always think i'm very close. I'm also so close to destroy my phone but i've read so many places that "it's only a softbrick, that can be fixed very easy".
Click to expand...
Click to collapse
OK, so you can enter the TWRP menu and install a ROM, right?
Any stock ROM from sammobile.com includes firmware, kernel and bootloader, so flashing the right one of these should reset all this.
Give it a try, for i think TWRP is actually working- otherwise you wouldn't get to the screen.
If the phone runs again with stock firmware, you can then flash a custom ROM.
And yeah, we're close, this can be only a minor flaw...it's near impossible to brick your android phone, so they say.
Don't worry mate, and be assured you're not the only one:
i just got stuck on bootloop also for a few minutes after upgrading to the newest version of XtreStoLite, which came out today.
Using TWRP, i could just flash back the previous version and all's good again.
Cya tomorrow...
EDIT:
I read through your previous comments again; the "md5sum"- issue seems to be a problem with the ROM file itself (corrupted or wrong version).
I'd bet that flashing the correct stock firmware for your carrier and model will solve the problem.
So enter the exact model number (like G920FXXU3COI9 or such) you have, get the right ROM and flash it with Odin 3.10.7
I couldn't find a denmark carrier on sammobile, eventually you have to look here at XDA, there's a list of stock imges as well.
Read lots of threads around this issue, almost all solved the problem flashing a stock ROM again.
Fingers crossed :fingers-crossed:
OK, so you can enter the TWRP menu and install a ROM, right?
Any stock ROM from sammobile.com includes firmware, kernel and bootloader, so flashing the right one of these should reset all this.
Give it a try, for i think TWRP is actually working- otherwise you wouldn't get to the screen.
If the phone runs again with stock firmware, you can then flash a custom ROM.
And yeah, we're close, this can be only a minor flaw...it's near impossible to brick your android phone, so they say.
Don't worry mate, and be assured you're not the only one:
i just got stuck on bootloop also for a few minutes after upgrading to the newest version of XtreStoLite, which came out today.
Using TWRP, i could just flash back the previous version and all's good again.
Cya tomorrow...
EDIT:
I read through your previous comments again; the "md5sum"- issue seems to be a problem with the ROM file itself (corrupted or wrong version).
I'd bet that flashing the correct stock firmware for your carrier and model will solve the problem.
So enter the exact model number (like G920FXXU3COI9 or such) you have, get the right ROM and flash it with Odin 3.10.7
I couldn't find a denmark carrier on sammobile, eventually you have to look here at XDA, there's a list of stock imges as well.
Read lots of threads around this issue, almost all solved the problem flashing a stock ROM again.
Fingers crossed
Click to expand...
Click to collapse
Yeah, i've never had problems entering TWRP menu. I can flash stock firmware via Odin but i can never do it via TWRP because it's says no md5 file found error - tho i can flash XtreStoLite (i think it's because it says aroma installer).
I've read many places about the md5 file error, but for some reason, i can't figure out how to fix it.
No, there is no Denmark model, but we have NEE (Nordic). The only stock firmware i can install is XEF (i don't remember where i got that from actually).
I will try agian and flash stock android via TWRP AND read about the md5 file error now/later. Tomorrow i will call the store i got the phone from and tell them i have a hardware issue or something like that. The guy owns a store for sellings covers, cases and stuff like that. He got the phone from Samsung free and sold it brand new in the package with 1 year warranty, so i will contact him tomorrow if i can't figure out how to flash stock android via TWRP or if it gives me error about the md5 file.
Talk to you tomorrow.
Update: I can not flash NEE model via Odin. Only XEF model - i also found out it was French firmware.
Hello,
I have a Galaxy S6 Edge SM-G925W8 on firmware 5.1.1. I recently updated my firmware using Smart Switch which brought me to 5.1.1 and wiped out my root access. I attempted to re-root the phone using the same TWRP Recovery I used to root it previously, which flashed successfully according to Odin. I was however unable to enter TWRP Recovery, getting the error "recovery is not seandroid enforcing" while at the booting screen. I figured maybe the TWRP Recovery I flashed was outdated and no longer worked for firmware 5.1.1 so I am now attempting to flash the Stock Recovery.img to wipe out my now broken Recovery. The problem is when I flash the stock recovery, Odin claimed the flash failed, giving no reason as to why. I'm not sure what I should do now - return to stock recovery (which fails when I attempt) or is there perhaps a way to restore TWRP Recovery and access root privileges once again.
Thank you for your help!
"recovery is not seandroid enforcing" is not a error, it's just a warning. If it stuck at this screen, that means the TWRP you're using is not compaitable with installed bootloader.
What's your PDA number?
forumber2 said:
"recovery is not seandroid enforcing" is not a error, it's just a warning. If it stuck at this screen, that means the TWRP you're using is not compaitable with installed bootloader.
What's your PDA number?
Click to expand...
Click to collapse
I'm sorry I'm not sure what that number is. I have searched through my phone's "About Phone" and "Developer Options" but did not find anything called a PDA number. If you mean the file I used to flash the TWRP Recovery, its name is "twrp-2.8.6.0v2-zeroltetmo.tar". If that's not what you need, could you please tell me how to find it?
Thank you!
vgplayer54 said:
I'm sorry I'm not sure what that number is. I have searched through my phone's "About Phone" and "Developer Options" but did not find anything called a PDA number. If you mean the file I used to flash the TWRP Recovery, its name is "twrp-2.8.6.0v2-zeroltetmo.tar". If that's not what you need, could you please tell me how to find it?
Thank you!
Click to expand...
Click to collapse
Type *#1234# on dialer. It'll show you software version (AP), modem -baseband- version (CP) and CSC version. I'm asking for AP version.
The TWRP version that you're trying to use is pretty old. The latest official TWRP is working on latest Android 5.1.1 bootlader. Try this; (for T-Mobile variant)
https://dl.twrp.me/zeroltetmo/twrp-3.0.2-0-zeroltetmo.img.tar
Thank you for getting back to me, will that T-Mobile version work on my Canadian Sm-G925W8? It's with Rogers, not sure if that makes a difference.
vgplayer54 said:
Thank you for getting back to me, will that T-Mobile version work on my Canadian Sm-G925W8? It's with Rogers, not sure if that makes a difference.
Click to expand...
Click to collapse
Okay, thank you for getting my AP number . The AP is G925W8VLU3B0J7.
forumber2 said:
Type *#1234# on dialer. It'll show you software version (AP), modem -baseband- version (CP) and CSC version. I'm asking for AP version.
The TWRP version that you're trying to use is pretty old. The latest official TWRP is working on latest Android 5.1.1 bootlader. Try this; (for T-Mobile variant)
https://dl.twrp.me/zeroltetmo/twrp-3.0.2-0-zeroltetmo.img.tar
Click to expand...
Click to collapse
Thank you for the link, I just finished flashing that TWRP Recovery and it appears to have worked. The problem now is I booted into the Recovery, installed SuperSU2.49 to add the SuperUser permissions and now I'm stuck on an infinite boot loop. The phone doesn't make it past the boot screen. Is there a way to reverse or fix this? I am still able to boot into the TWRP Recovery however, anything I can do here to fix the problem?
vgplayer54 said:
Thank you for the link, I just finished flashing that TWRP Recovery and it appears to have worked. The problem now is I booted into the Recovery, installed SuperSU2.49 to add the SuperUser permissions and now I'm stuck on an infinite boot loop. The phone doesn't make it past the boot screen. Is there a way to reverse or fix this? I am still able to boot into the TWRP Recovery however, anything I can do here to fix the problem?
Click to expand...
Click to collapse
try cleaning the cache and daavik cache. To remove any stray bits of code left over.
vgplayer54 said:
Thank you for the link, I just finished flashing that TWRP Recovery and it appears to have worked. The problem now is I booted into the Recovery, installed SuperSU2.49 to add the SuperUser permissions and now I'm stuck on an infinite boot loop. The phone doesn't make it past the boot screen. Is there a way to reverse or fix this? I am still able to boot into the TWRP Recovery however, anything I can do here to fix the problem?
Click to expand...
Click to collapse
You flashed a whole old version of SuperSU. You need to flash latest beta;
http://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
But, you have to do it after reflash the stock firmware, because you modified the /system, which you shouldn't.
Or, just wipe everything and flash a custom ROM (I prefer this ROM )
forumber2 said:
You flashed a whole old version of SuperSU. You need to flash latest beta;
http://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
But, you have to do it after reflash the stock firmware, because you modified the /system, which you shouldn't.
Or, just wipe everything and flash a custom ROM (I prefer this ROM )
Click to expand...
Click to collapse
Thank you so much for the advice. I ended up downloading the stock firmware 5.1.1 for my phone model (AP number matched and everything) although what I didn't expect was for it to delete all my data and storage. I had no backup...as I didn't expect the root to go bad. But since it happened anyway, could you tell me a bit about these custom ROMS? The reason I never wanted to use one was due to not wanting to lose my data. But it happened anyway...so I might as well see what it's all about. I checked out the link to the one you said you prefer, is it overly beneficial to use a custom ROM? Does it already come Rooted or do I still have to do that myself?
Please let me know!
I'm going crazy. I wanted to upgrade my Samsung Galaxy S5 SM-G900F finally from 4.4.2 to 6.01. I rooted it years ago and never cared to upgrade through OTA, since it never worked. So I found out about the FlashFire app recently, and used it to flash a 6.0.1 firmware stock zip file I downloaded. Followed all instructions, left all deselected partitions as is, only flashed boot, recovery, system, cache and preload. FlashFire started working on it, reboots into loading logo screen for a while, I start getting concerned but then it loads up a screen showing "Optimizing files" of like 250. Once that got done, it rebooted. Here is where I'm stuck since then.
My phone has been soft bricked, it's stuck on an endless Samsung logo screen, that gently flashed back and forth, and there's a blue notification light on during this. So I googled what I can do, and I tried using Volume Up + Power Button + Home button, since that would get me into recovery mode. That works, but instead of the Samsung recovery mode I get the Clockwork mod recovery screen. I had completely forgotten that I even had that. But, the same options are there too, so I wipe cache, wipe user data, wipe dalvik and factory reset. Once I did that, I selected reboot.
And the same thing happens. Endless Samsung logo screen. Stuck on it for hours. Now I honestly don't know what to do. I've done the recovery mode options 3 times, nothing changes.
Someone please help me out, I can't figure out what went wrong and how I can fix it. I can't afford a new phone...Ideally, I would like to be able to completely reset the phone entirely to factory settings. Is this possible? I appreciate any advice I can get.
Download odin and flash the whole firmware tar.md5.
4.4.2 to 6.0.1 is a big step so you'll probably need all partitions in that file.
Skickat från min SM-A310F via Tapatalk
tys0n said:
Download odin and flash the whole firmware tar.md5.
4.4.2 to 6.0.1 is a big step so you'll probably need all partitions in that file.
Skickat från min SM-A310F via Tapatalk
Click to expand...
Click to collapse
Thanks for replying. Which firmware? I don't understand what you mean by all partitions. Will this Odin method really fix my bootlooped phone?
tempest22 said:
Thanks for replying. Which firmware? I don't understand what you mean by all partitions. Will this Odin method really fix my bootlooped phone?
Click to expand...
Click to collapse
For some reason the recovery flash diden't work, and custom recoveries can't extract the csc-zip that its inside cache.img.
It could be that bootloader, modem and other partitions needs to be updated as well.
Yes. I think you'll need to flash the whole firmware with odin.
tys0n said:
For some reason the recovery flash diden't work, and custom recoveries can't extract the csc-zip that its inside cache.img.
It could be that bootloader, modem and other partitions needs to be updated as well.
Yes. I think you'll need to flash the whole firmware with odin.
Click to expand...
Click to collapse
When I googled how to properly use FlashFire when I first used it (which then lead to this soft brick) I read that you shouldn't flash the modem and other priority partitions that were unselected. So now I should do it?
Where is the best place to get firmware? And which firmware do I even get? 6.0.1? Or my old 4.4.2 to get it back to it's original state?
Help pls
tempest22 said:
When I googled how to properly use FlashFire when I first used it (which then lead to this soft brick) I read that you shouldn't flash the modem and other priority partitions that were unselected. So now I should do it?
Where is the best place to get firmware? And which firmware do I even get? 6.0.1? Or my old 4.4.2 to get it back to it's original state?
Click to expand...
Click to collapse
Either 4.4.2, 5.0 or 6.0.1 would do since you only flashed four partitions.
Use http://updato.com/firmware-archive-select-model?r=&v=&q=SM-G900F&exact=1&rpp=15
You can sort it by version, date, region etc.
tys0n said:
Either 4.4.2, 5.0 or 6.0.1 would do since you only flashed four partitions.
Use http://updato.com/firmware-archive-select-model?r=&v=&q=SM-G900F&exact=1&rpp=15
You can sort it by version, date, region etc.
Click to expand...
Click to collapse
Ok. So you're saying I download let's say the 6.0.1 from there, then I download Odin, connect my phone in download made and flash ALL partitions from that firmware? This will get my phone out of this crazy bootloop Samsung logo soft brick it's been in for 3 days?
tempest22 said:
Ok. So you're saying I download let's say the 6.0.1 from there, then I download Odin, connect my phone in download made and flash ALL partitions from that firmware? This will get my phone out of this crazy bootloop Samsung logo soft brick it's been in for 3 days?
Click to expand...
Click to collapse
You make it sound like odin is some shady, untrusted software while it's in fact the very same software that samsung service centers use, flashing the very same firmware packages. I'd say it's far more reliable than any app you can flash with.
They're only good for smaller partitions like boot, recovery but not for upgrading android versions.
I can't guarantie anything, but yeah, going from 4.4.2 to 6.0.1 I'd say you'll probably need updated bootloader, modem etc to make it work. Flashing whole .tar.md5 package will fix that.
Unless you have some better idea...
And don't be mad at me if it turns out it's not working.
You're the one who messed it up in the first place. I'm just trying to help.
tys0n said:
You make it sound like odin is some shady, untrusted software while it's in fact the very same software that samsung service centers use, flashing the very same firmware packages. I'd say it's far more reliable than any app you can flash with.
They're only good for smaller partitions like boot, recovery but not for upgrading android versions.
I can't guarantie anything, but yeah, going from 4.4.2 to 6.0.1 I'd say you'll probably need updated bootloader, modem etc to make it work. Flashing whole .tar.md5 package will fix that.
Unless you have some better idea...
And don't be mad at me if it turns out it's not working.
You're the one who messed it up in the first place. I'm just trying to help.
Click to expand...
Click to collapse
Ok, how exactly do I flash whole .tar.md5 package? I've been looking at how to use Odin and I don't really see how to do that.
tys0n said:
You make it sound like odin is some shady, untrusted software while it's in fact the very same software that samsung service centers use, flashing the very same firmware packages. I'd say it's far more reliable than any app you can flash with.
They're only good for smaller partitions like boot, recovery but not for upgrading android versions.
I can't guarantie anything, but yeah, going from 4.4.2 to 6.0.1 I'd say you'll probably need updated bootloader, modem etc to make it work. Flashing whole .tar.md5 package will fix that.
Unless you have some better idea...
And don't be mad at me if it turns out it's not working.
You're the one who messed it up in the first place. I'm just trying to help.
Click to expand...
Click to collapse
Odin worked. Thanks!
Hello i have a Galaxy S7 SM-G930W8 thats frp locked and i have been looking to unlock it for the past 4 days but could not find any solution on how to please help,thanks
Kemako121 said:
Hello i have a Galaxy S7 SM-G930W8 thats frp locked and i have been looking to unlock it for the past 4 days but could not find any solution on how to please help,thanks
Click to expand...
Click to collapse
Flash stock then log in with your Google credentials
*Detection* said:
Flash stock then log in with your Google credentials
Click to expand...
Click to collapse
well could you please link me the stock of my phone because i cannot find it myself.... i was looking for a while and tried some but now my phone is just stuck on the boot screen..
Stock sm-g930w8 firmware is here: https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/
This post may be helpful: https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
audit13 said:
Stock sm-g930w8 firmware is here: https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/
This post may be helpful: https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
Click to expand...
Click to collapse
thank you a lot but i have another question after i ran a boot.tar from firmware.obi my phone is stuck on the boot logo what can i do to move on and is it safe if i boot the files u sent me with the current state of my phone? also the download will be ages since the speed for non premium is 15kb/sec
To return the phone to a stock condition, you flash the ROM using Odin which will overwrite everything with the possible exception of the data partition.
If the phone is stuck at the boot logo, have you tried a factory reset from stock recovery?
You can try this link: http://samsung-updates.com/device/?id=SM-G930W8 or https://updato.com/firmware-archive-select-model?exact=1&q=SM-G930W8
I don't know about download speeds for the above-two links as I have never used them before but other XDA members have.
audit13 said:
To return the phone to a stock condition, you flash the ROM using Odin which will overwrite everything with the possible exception of the data partition.
If the phone is stuck at the boot logo, have you tried a factory reset from stock recovery?
You can try this link: http://samsung-updates.com/device/?id=SM-G930W8 or https://updato.com/firmware-archive-select-model?exact=1&q=SM-G930W8
I don't know about download speeds for the above-two links as I have never used them before but other XDA members have.
Click to expand...
Click to collapse
i have tried going into the boot menu for factory reset but no luck the phone just resets,im starting the odin method right now with the thing you provided, also do i fill all the blanks (like the csc,ap and cp?) in odin?
After downloading the file from sammobile.com, unzip the file once (I use 7zip) to yield the necessary files. Each file will be preceded by the blank or slot location.
Difference between CSC and Home CSC: https://forum.xda-developers.com/s7-edge/help/csc-home-csc-simple-t3464835 or https://forum.xda-developers.com/galaxy-s7/help/question-using-ap-bl-csc-instead-home-t3562545
audit13 said:
After downloading the file from sammobile.com, unzip the file once (I use 7zip) to yield the necessary files. Each file will be preceded by the blank or slot location.
Difference between CSC and Home CSC: https://forum.xda-developers.com/s7-edge/help/csc-home-csc-simple-t3464835 or https://forum.xda-developers.com/galaxy-s7/help/question-using-ap-bl-csc-instead-home-t3562545
Click to expand...
Click to collapse
help when i put in all the things it says: SW REV. CHECK FAIL DEVICE:2 BINARY:1
Odin recognizes the phone? Are you seeing the message in download mode?
audit13 said:
Odin recognizes the phone? Are you seeing the message in download mode?
Click to expand...
Click to collapse
so i managed to get this phone back to its original state when it was frp locked by downloading software from sammobile but it still remembers the google account... i will try to download a older version of android and run that to hopefully get the phone to 6.0.1 or whatever the original version was and try some older ways to frp unlock my phone because the older version will have less security patches. hopefully this works! thanks for the help so far .:good:
I'm not sure that you can downgrade once the phone has been updated.
Good luck.
same here, stuck without solutions. tried pretty much everything found on the internet carefully and taking the time to do it.. but still...
i still need help can someone find a way to unlock my phone?
One way to remove frp lock is to flash a custom recovery (like TWRP) for your phone and then use the wipe -> format data (and type 'yes' when asked, without the quotes). Restart the phone and let the system boot. After it boots you can procede to flash the stock rom
* P.S. 1: flashing a custom recovery will trigger KNOX so say bye bye to S Health if you are not planning to root the phone (so as to be able to edit the build prop and enable SHealth again) after flashing the stock rom again. Do not attemp to flash the stock recovery image on its own or your phone will be soft bricked and the dm-verity error will give you nightmares (happened twice to me, took me 6 hours to recover my phone). To get back the stock recovery you need to flash the stock rom again.
* P.S. 2: If your phone has the bootloader locked you will not be able to flash a custom recovery. In that case you can try to downgrade to 6.0 but there are not guarantees that it will work ok.
Sent from my SM-G930F using Tapatalk
coto39 said:
One way to remove frp lock is to flash a custom recovery (like TWRP) for your phone and then use the wipe -> format data (and type 'yes' when asked, without the quotes). Restart the phone and let the system boot. After it boots you can procede to flash the stock rom
* P.S. 1: flashing a custom recovery will trigger KNOX so say bye bye to S Health if you are not planning to root the phone (so as to be able to edit the build prop and enable SHealth again) after flashing the stock rom again. Do not attemp to flash the stock recovery image on its own or your phone will be soft bricked and the dm-verity error will give you nightmares (happened twice to me, took me 6 hours to recover my phone). To get back the stock recovery you need to flash the stock rom again.
* P.S. 2: If your phone has the bootloader locked you will not be able to flash a custom recovery. In that case you can try to downgrade to 6.0 but there are not guarantees that it will work ok.
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
hi could you please link the stuff i need to download in order to to this my phone is SM-G930W8
Hi,
Using latest Odin I am trying to return to my phone to stock but cannot
I have tried 4 different firmware’s already (over 20 times) and each one will PASS the flash process, phone rests, installing system update (stops at around 30%) and during the blue screen the update stops, resets, receive Erasing message for a bit and then NO COMMAND and phone will simply not boot. (with some flashes the stock recovery is not even available, working or present)
... only way to boot the phone is to install TWRP... installing the NO VERITY file seems to help in booting…
I have noticed when i plug the phone is it comes up as another device name (from a previous ROM) so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
Back in DOWLOAD MODE under system status = CUSTOM (after flashing stock firmware)
My guess is that the new firmware I flash simply wont stick, or is half installed, or could be something to do with encryptions,
Some of the logs I see include:
Failed to open recovery
Reboot recovery cause UNKNOWN
E: Failed setting up dirty target
Fail to mount /system as rw
i have no idea what else to try
GODSPD said:
Hi,
Using latest Odin I am trying to return to my phone to stock but cannot
I have tried 4 different firmware’s already (over 20 times) and each one will PASS the flash process, phone rests, installing system update (stops at around 30%) and during the blue screen the update stops, resets, receive Erasing message for a bit and then NO COMMAND and phone will simply not boot. (with some flashes the stock recovery is not even available, working or present)
... only way to boot the phone is to install TWRP... installing the NO VERITY file seems to help in booting…
I have noticed when i plug the phone is it comes up as another device name (from a previous ROM) so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
Back in DOWLOAD MODE under system status = CUSTOM (after flashing stock firmware)
My guess is that the new firmware I flash simply wont stick, or is half installed, or could be something to do with encryptions,
Some of the logs I see include:
Failed to open recovery
Reboot recovery cause UNKNOWN
E: Failed setting up dirty target
Fail to mount /system as rw
i have no idea what else to try
Click to expand...
Click to collapse
You flashed the wrong firmware and corrupted your device.
You should flash the newest available firmware for your specific model number. You might have to flash the PIT file for your model number along with the firmware with the "re-partition" option checked in Odin when you flash it.
Sent from my LGL84VL using Tapatalk
Droidriven said:
You flashed the wrong firmware and corrupted your device.
You should flash the newest available firmware for your specific model number. You might have to flash the PIT file for your model number along with the firmware with the "re-partition" option checked in Odin when you flash it.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I need to keep v3 bootloader, i am very sure that latest firmware will work but i am trying to avoid it, and i never flashed the wrong firmware, i have tried aroud 6 different v3 and none will stick, can you suggest where i can find the PIT files and possible guide? without the pit file the repartition option fails each time...
GODSPD said:
I need to keep v3 bootloader, i am very sure that latest firmware will work but i am trying to avoid it, and i never flashed the wrong firmware, i have tried aroud 6 different v3 and none will stick, can you suggest where i can find the PIT files and possible guide? without the pit file the repartition option fails each time...
Click to expand...
Click to collapse
If you didn't flash the firmware then how did it show up as a different device "from a previous ROM", as you said?
They might have been V3 firmware, but was it for the same model number of V3 as yours? Are the model numbers different? Is V3 the model number? Or is it the device branded name?
Sent from my LGL84VL using Tapatalk
Droidriven said:
If you didn't flash the firmware then how did it show up as a different device "from a previous ROM", as you said?
Thanks for the feedback.
They might have been V3 firmware, but was it for the same model number of V3 as yours? Are the model numbers different? Is V3 the model number? Or is it the device branded name?
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks for the feedback, several months ago i flashed G935FXXS3ERHD_G935FXEO3ERG2_XEO on the S7 Edge International, so firmware is correct, i flashed a custom ROM - Glamour ROM a S9+ Ported ROM for the S7E, everything worked fine until i tried to revert back to stock, every other V3 firmware apart from the one mentioned above wont flash correctly, either fails or boot loops, has no stock recovery, and system status is still showing CUSTOM, when i plug the device in it will come up as Galaxy S9+ ... for some reason i cannot do a proper flash on it,
I am almost certain i can do a proper flash with the latest firmware but i am trying to avoid that...
GODSPD said:
Thanks for the feedback, several months ago i flashed G935FXXS3ERHD_G935FXEO3ERG2_XEO on the S7 Edge International, so firmware is correct, i flashed a custom ROM - Glamour ROM a S9+ Ported ROM for the S7E, everything worked fine until i tried to revert back to stock, every other V3 firmware apart from the one mentioned above wont flash correctly, either fails or boot loops, has no stock recovery, and system status is still showing CUSTOM, when i plug the device in it will come up as Galaxy S9+ ... for some reason i cannot do a proper flash on it,
I am almost certain i can do a proper flash with the latest firmware but i am trying to avoid that...
Click to expand...
Click to collapse
Have you tried factory resetting the device then try flashing via Odin? Sometimes there is conflicting data that prevents from flashing the firmware.
You might not have a choice of which firmware to flash to repair your device.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Have you tried factory resetting the device then try flashing via Odin? Sometimes there is conflicting data that prevents from flashing the firmware.
You might not have a choice of which firmware to flash to repair your device.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
more than you can imagine, every possible wipe and combination has been done with no luck at all
GODSPD said:
more than you can imagine, every possible wipe and combination has been done with no luck at all
Click to expand...
Click to collapse
Well then, suck it up and flash the newest firmware, you are out of options.
Your device probably doesn't allow downgrading, in this case, you can only flash exactly what was on the device before you caused the issue or a newer firmware, you can't go backwards to an older firmware.
If you're trying to flash an older firmware in an effort to get past a locked bootloader, you are probably wasting your time, that doesn't work out most of the time.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Well then, suck it up and flash the newest firmware, you are out of options.
Your device probably doesn't allow downgrading, in this case, you can only flash exactly what was on the device before you caused the issue or a newer firmware, you can't go backwards to an older firmware.
If you're trying to flash an older firmware in an effort to get past a locked bootloader, you are probably wasting your time, that doesn't work out most of the time.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
That definitely makes sense that i cannot downgrade but i am flashing either the same firmware or slightly newer staying on the same bootloader version.