flashing stock with latest odin failed writing system.img to System Partition - Samsung Galaxy S7 Questions and Answers

I am using the latest stable nightly build for me, the one released in 04-04 of the LineageOS.
The build is working fine, however, I need to go back to stock firmware.
Last time I tried to do it using newest Odin, I was on latest build (the one that has all those crashes) and right at the beginning of the flashing process, the writing of system.img to System partition fails and the device was bricked.
Bricked up to the point where a restore using Samsung Switch was the only apparent solution. So I went for it. I have to say it is a really annoying procedure, you will need your device serial number and a good internet connection. When the download was finished, the software instructed me to go into download mode. The installation started and seemed to be doing fine, but sadly the process has failed at 67%.
As a workaround, I flashed TWRP and then another more stable version of LineageOS. Before flashing the OS, i did a file system repair on the System partition, which had a strange small size.
I'm afraid that the same thing could happen again.
Could you please help me out?
Thanks.

Extract system.img from software and flash it alone

Or use samsung kies to flash back the orig firmware.

RiTCHiE007 said:
Or use samsung kies to flash back the orig firmware.
Click to expand...
Click to collapse
I did, and it has failed at 67%.

hemp_invader said:
I did, and it has failed at 67%.
Click to expand...
Click to collapse
Try flashing the PIT file with Repartition enabled in ODIN first
https://www.s a m m ob i l e.com/forum/showthread.php?t=30609

*Detection* said:
Try flashing the PIT file with Repartition enabled in ODIN first
https://www.s a m m ob i l e.com/forum/showthread.php?t=30609
Click to expand...
Click to collapse
Thanks mate, I will take a look at this.
I have been looking for a solution and ran into this alternative in other communities. The problem is, I don't have that much experience with Odin rather than flashing the usual files in order to install a ROM.
When the device became bricked, it wouldn't even boot to download mode. The only solution was recovering with Samsung Switch, which took a while to download the build by the way. Then the software allows you to boot into download mode. The automated install process seemed to be doing just fine, until it failed at 67%. So I booted into download mode and flashed latest TWRP, that allowed me to repair the system partition (which had a strange small size) and then flashing a more stable version of the LineageOS and here I am now.

hemp_invader said:
Thanks mate, I will take a look at this.
I have been looking for a solution and ran into this alternative in other communities. The problem is, I don't have that much experience with Odin rather than flashing the usual files in order to install a ROM.
When the device became bricked, it wouldn't even boot to download mode. The only solution was recovering with Samsung Switch, which took a while to download the build by the way. Then the software allows you to boot into download mode. The automated install process seemed to be doing just fine, until it failed at 67%. So I booted into download mode and flashed latest TWRP, that allowed me to repair the system partition (which had a strange small size) and then flashing a more stable version of the LineageOS and here I am now.
Click to expand...
Click to collapse
Well CSC contains the PIT file, so using CSC & Checking 'Repartition' in ODIN while flashing the full 4 sections of the ROM 'should' in theory do the same thing, so give both a try
PIT = Deletes and recreates the partitions on the internal storage before flashing the ROM, so if one of them is messed up size wise from Lineage or something, then the PIT should fix it
There could also be a hardware problem, but still a few options to try with firmware and flashing first

Related

Help greatly appreciated - S6 G920F Bootloop after odin flash

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.

Newest bootloader & modem

I want to flash the latest bootloader and modem to my G920F. But the problem is, that I have no idea for what is this etc. Could someone explain, could I install the bootloader and a modem with a different designation than my rom? For example, I have now COI9, can i flash another modem than with the designation COI9? I someone could, please link to the latest version, thank you!
You dont need to do it... Always stick with the modem and bootloader same as the system... Mixmatching those files can couse battery drain ( radio interference , deep sleep problems ) ... For the time ive used the s6 COI9 was the best modem i ever tested.. So stay with OI9
lummujaj said:
You dont need to do it... Always stick with the modem and bootloader same as the system... Mixmatching those files can couse battery drain ( radio interference , deep sleep problems ) ... For the time ive used the s6 COI9 was the best modem i ever tested.. So stay with OI9
Click to expand...
Click to collapse
when my rom is on DOK9, will be better, when i flash modem/bootloader from DOK9?
botanicfts said:
when my rom is on DOK9, will be better, when i flash modem/bootloader from DOK9?
Click to expand...
Click to collapse
yes and no ... as i said mixing ap,bl,cp can cause weird stuff ... for my opinion is IO9 BTU ... best battery life and less bloatware ... and i think will be the 1st to get MM official ...
lummujaj said:
yes and no ... as i said mixing ap,bl,cp can cause weird stuff ... for my opinion is IO9 BTU ... best battery life and less bloatware ... and i think will be the 1st to get MM official ...
Click to expand...
Click to collapse
can you give me link for the OI9 bootloader, modem etc? thanks!
botanicfts said:
can you give me link for the OI9 bootloader, modem etc? thanks!
Click to expand...
Click to collapse
https://drive.google.com/uc?id=0B40ItdHKfkyQSmNOWjFIa1JRWms&export=download
download and extract
lummujaj said:
https://drive.google.com/uc?id=0B40ItdHKfkyQSmNOWjFIa1JRWms&export=download
download and extract
Click to expand...
Click to collapse
what should i flash from these 4 files? im newbie xD
botanicfts said:
what should i flash from these 4 files? im newbie xD
Click to expand...
Click to collapse
bl - botloader
ap - system
cp - modem
csc - csc
i prefer you to flash them all + pit file ,,, BTU is the most stock debloated and most stable rom ...
anyway i dont have anymore my galaxy s6 ive swaped with an oneplus 2
lummujaj said:
bl - botloader
ap - system
cp - modem
csc - csc
i prefer you to flash them all + pit file ,,, BTU is the most stock debloated and most stable rom ...
anyway i dont have anymore my galaxy s6 ive swaped with an oneplus 2
Click to expand...
Click to collapse
so, I searched at the forum and probably i'll test the marshmallow, then I'll try a few combinations with roms, kernels etc. because my battery life on my s6 dont satisfied me
If you try MM make sure your device will "deep sleep"
lummujaj said:
bl - botloader
ap - system
cp - modem
csc - csc
i prefer you to flash them all + pit file ,,, BTU is the most stock debloated and most stable rom ...
anyway i dont have anymore my galaxy s6 ive swaped with an oneplus 2
Click to expand...
Click to collapse
Hi,
I have this galaxy s6 that only boots in download mode.. I literally flashed every stockrom and recovery etc. Have you got any other solution I could try? I tried pit file but it gives me an error... maybe it's not the right pit file. PLS ow pretty PLS, give me a link to a good debloated odin flashable stock rom and a good pit file. I'm pretty desperate about this phone. it does boot in download so I guess this phone is still fixable. I also tried Nand Erase All option, it passes but still no normal boot nor recovery. so can you tell me where to find a good rom and pit file?
Thanks in advance
liobeir said:
Hi,
I have this galaxy s6 that only boots in download mode.. I literally flashed every stockrom and recovery etc. Have you got any other solution I could try? I tried pit file but it gives me an error... maybe it's not the right pit file. PLS ow pretty PLS, give me a link to a good debloated odin flashable stock rom and a good pit file. I'm pretty desperate about this phone. it does boot in download so I guess this phone is still fixable. I also tried Nand Erase All option, it passes but still no normal boot nor recovery. so can you tell me where to find a good rom and pit file?
Thanks in advance
Click to expand...
Click to collapse
Im afraid i cannot help.. this post is more than 3 years old ... I can suggest you flash twrp and a costom rom of your choice
Did the same thing last week
liobeir said:
Hi,
I have this galaxy s6 that only boots in download mode.. I literally flashed every stockrom and recovery etc. Have you got any other solution I could try? I tried pit file but it gives me an error... maybe it's not the right pit file. PLS ow pretty PLS, give me a link to a good debloated odin flashable stock rom and a good pit file. I'm pretty desperate about this phone. it does boot in download so I guess this phone is still fixable. I also tried Nand Erase All option, it passes but still no normal boot nor recovery. so can you tell me where to find a good rom and pit file?
Thanks in advance
Click to expand...
Click to collapse
I've been there with my S6 Edge...only a week ago while I was installing LineageOS. I was feeling pretty hopeless for awhile but installing a custom ROM got my phone to the point where it was usable again. I'm still burning through firmware variations from sammobile in search of a better modem but at least I got it working again. Odin is your friend.
AKdballs said:
I've been there with my S6 Edge...only a week ago while I was installing LineageOS. I was feeling pretty hopeless for awhile but installing a custom ROM got my phone to the point where it was usable again. I'm still burning through firmware variations from sammobile in search of a better modem but at least I got it working again. Odin is your friend.
Click to expand...
Click to collapse
Can I make any rom zip flashable in odin? Because I can't get in recovery... And I don't know if I'm rooted.. Because I did flash cf root but yeah... I don't know if I'm rooted now.
Flash TWRP
liobeir said:
Can I make any rom zip flashable in odin? Because I can't get in recovery... And I don't know if I'm rooted.. Because I did flash cf root but yeah... I don't know if I'm rooted now.
Click to expand...
Click to collapse
Why can't you get into recovery? If you can get your phone into download mode, then you can use Odin to install TWRP which will give you access to recovery. You said you had the S6 right, not Edge? You can get TWRP for that version here https://twrp.me/samsung/samsunggalaxys6.html and then install it with Odin. After that, boot into recovery, and then plug your phone into a computer and transfer your ROM onto the phone and install it. If you aren't able to get that part of it done, then the stock firmware for your S6 may be available for download from https://www.sammobile.com/ and those can be flashed using Odin. If one of those doesn't work, try a different one until you find one that works. Good luck; don't lose hope. I have found my S6 Edge resilient and hard to permanently brick.
AKdballs said:
Why can't you get into recovery? If you can get your phone into download mode, then you can use Odin to install TWRP which will give you access to recovery. You said you had the S6 right, not Edge? You can get TWRP for that version here https://twrp.me/samsung/samsunggalaxys6.html and then install it with Odin. After that, boot into recovery, and then plug your phone into a computer and transfer your ROM onto the phone and install it. If you aren't able to get that part of it done, then the stock firmware for your S6 may be available for download from https://www.sammobile.com/ and those can be flashed using Odin. If one of those doesn't work, try a different one until you find one that works. Good luck; don't lose hope. I have found my S6 Edge resilient and hard to permanently brick.
Click to expand...
Click to collapse
Ow believe me I have tried this. I tried stock recovery, twrp (different versions), cf root so ik hoped it would flash CWM, different stock roms... Nothing wakes up this phone.
I'm going to try some stuff now. I'll keep you posted!
---------- Post added at 06:51 PM ---------- Previous post was at 06:20 PM ----------
AKdballs said:
I've been there with my S6 Edge...only a week ago while I was installing LineageOS. I was feeling pretty hopeless for awhile but installing a custom ROM got my phone to the point where it was usable again. I'm still burning through firmware variations from sammobile in search of a better modem but at least I got it working again. Odin is your friend.
Click to expand...
Click to collapse
How did you flash that rom when you couldn't get in recovery?
liobeir said:
Ow believe me I have tried this. I tried stock recovery, twrp (different versions), cf root so ik hoped it would flash CWM, different stock roms... Nothing wakes up this phone.
I'm going to try some stuff now. I'll keep you posted!
Click to expand...
Click to collapse
I thought I was done for last week when I flashed a package from Sammobile that my phone didn't like and it resulted in Error message from Odin. After that, download mode showed up as wrecked and said to use Smartswitch to enter emergency recovery mode. I tried a few versions of Smartswitch but they all kept saying my device was unsupported. I went to sleep feeling pretty lousy.
The next day I started fresh and had a few more packages from Sammobile to try. Even with the message about "emergency recovery mode", I was able to install a new Sammobile package using Odin. That replaced modem, system, bootloader, everything the phone needed. Except the phone was stuck in a bootloop and kept restarting every time it go to the "installing android" part of the boot process. At that point I shut the phone down and installed the latest TWRP recovery, booted into recovery, and transferred my ROMs + GApps onto it and then installed them following the ROM's installation instructions. It was pretty hairy for awhile but my persistence paid off and now it works again. Hopefully you get yours working.
What do you mean "nothing wakes up this phone" does it hang at a particular part?
How did you flash that rom when you couldn't get in recovery?
Click to expand...
Click to collapse
I don't think you can. You need to install TWRP recovery in download mode before you can flash ROMs. Is that what you're having problems with?
​
AKdballs said:
I thought I was done for last week when I flashed a package from Sammobile that my phone didn't like and it resulted in Error message from Odin. After that, download mode showed up as wrecked and said to use Smartswitch to enter emergency recovery mode. I tried a few versions of Smartswitch but they all kept saying my device was unsupported. I went to sleep feeling pretty lousy.
The next day I started fresh and had a few more packages from Sammobile to try. Even with the message about "emergency recovery mode", I was able to install a new Sammobile package using Odin. That replaced modem, system, bootloader, everything the phone needed. Except the phone was stuck in a bootloop and kept restarting every time it go to the "installing android" part of the boot process. At that point I shut the phone down and installed the latest TWRP recovery, booted into recovery, and transferred my ROMs + GApps onto it and then installed them following the ROM's installation instructions. It was pretty hairy for awhile but my persistence paid off and now it works again. Hopefully you get yours working.
What do you mean "nothing wakes up this phone" does it hang at a particular part?
I don't think you can. You need to install TWRP recovery in download mode before you can flash ROMs. Is that what you're having problems with?
Click to expand...
Click to collapse
Thanks for sticking up with me. We'll, the phone only boots in download mode. I flashed literally everything... From custom recoveries to stock roms, also had the smarts witch notification but smarts switch nor Kies doesn't fix the problem. I tried flashing recoveries, different versions, nothing. What I mean with waking up the phone... Well even after a successful Odin stock firmware flash, the phone doesn't boot by itself. Tried with the auto reboot ticked off but... Yeah... The phone only boots in download mode. But in download mode I see that it says CUSTOM BINARY,.... so... It flashes but... It's not booting. Not even getting a starting up screen that freezes... Nothing...all black... Only download mode. I just now tried converting a custom Rom zip to a tar file... Flashed it... Failed... Blablabla... This s6 is giving me a hard time! now, it' s a phone from a college that actually threw the phone in the garbage... But I retrieved it and I wanted to fix this s6. It's a good phone... It goes in download mode so.... That thought keeps me hopeful!
Again thanks for the support...
liobeir said:
​
Thanks for sticking up with me. We'll, the phone only boots in download mode. I flashed literally everything... From custom recoveries to stock roms, also had the smarts witch notification but smarts switch nor Kies doesn't fix the problem. I tried flashing recoveries, different versions, nothing. What I mean with waking up the phone... Well even after a successful Odin stock firmware flash, the phone doesn't boot by itself. Tried with the auto reboot ticked off but... Yeah... The phone only boots in download mode. But in download mode I see that it says CUSTOM BINARY,.... so... It flashes but... It's not booting. Not even getting a starting up screen that freezes... Nothing...all black... Only download mode. I just now tried converting a custom Rom zip to a tar file... Flashed it... Failed... Blablabla... This s6 is giving me a hard time! now, it' s a phone from a college that actually threw the phone in the garbage... But I retrieved it and I wanted to fix this s6. It's a good phone... It goes in download mode so.... That thought keeps me hopeful!
Again thanks for the support...
Click to expand...
Click to collapse
okay so, tried a couple more firmwares...they all pass in odin but not booting my phone. also not in recovery. tried flashing twrp and stuff but can't get it to boot! It doesn't hang on a screen. it just doesn't boot. only on download mode I get it to boot. Could this be a hardware problem?? I think not because it boots in download mode. Maybe try to flash bootloaders? Are there other recoveries? CWM, Philz touch?

Soft bricked S6- Run out of options

My S6 only goes into odin/download mode, I have tried multiple times trying to flash the stock rom using different versions of odin and different versions of the stock rom just to be sure. I never rooted the phone but I read that you dont need to be rooted or in debugging mode to use odin. Everytime I have used odin it stops after nand write start. I have tried to root if using cf auto root but that failed as well. I have tried renaming the tar.md5 into just tar and extracting the files (never once found hidden.img though), recompiled them to make new tar files and tried booting them individually but still no luck. I really have no idea what I am doing wrong or why this phone will not flash the stock firmware. Even smart switch wont work, so I cant go into recovery mode to manually wipe the phone. The model number is the G920W8.
Any help or new ideas would be appreciated.
restore stock and take it back to the store. i had the same problem too. new one coming soon.
smiley45 said:
restore stock and take it back to the store
Click to expand...
Click to collapse
That's all I've been trying to do. Just restore the stock firmware. My problem is that it won't restore to stock. Neither through Odin or smart switch.
Also my battery does not charge, that was the original problem.
murph123 said:
That's all I've been trying to do. Just restore the stock firmware. My problem is that it won't restore to stock. Neither through Odin or smart switch.
Click to expand...
Click to collapse
did you get this to restore?
smiley45 said:
did you get this to restore?
Click to expand...
Click to collapse
No still no luck. Any suggestions?
murph123 said:
No still no luck. Any suggestions?
Click to expand...
Click to collapse
try to flash android 5.1.1. for your phone model if you can get into twrp. do a full phone wipe. and a factory restore. then flash android 5.1.1 thru odin. you should be good to go. if you are still having boot loops let the phone die completely and wait for 10 min to 15 min. you may need to do this few times but i did this and it works for me let my know what happens. ( you might need to stay in download mode until the phone dies)
some times the answer is more simple as expected, try another usb port, or maybe another computer ...
http://forum.xda-developers.com/galaxy-s6/help/how-to-unbrick-samsung-galaxy-s6-100-t3378857 read my post mate it helped me
murph123 said:
My S6 only goes into odin/download mode, I have tried multiple times trying to flash the stock rom using different versions of odin and different versions of the stock rom just to be sure. I never rooted the phone but I read that you dont need to be rooted or in debugging mode to use odin. Everytime I have used odin it stops after nand write start. I have tried to root if using cf auto root but that failed as well. I have tried renaming the tar.md5 into just tar and extracting the files (never once found hidden.img though), recompiled them to make new tar files and tried booting them individually but still no luck. I really have no idea what I am doing wrong or why this phone will not flash the stock firmware. Even smart switch wont work, so I cant go into recovery mode to manually wipe the phone. The model number is the G920W8.
Any help or new ideas would be appreciated.
Click to expand...
Click to collapse
Try to flash a costum rom with twrp

Help! Galaxy amp prime (SM-J320AZ) stuck in bootloop

So my galaxy amp prime(Cricket, SM-J320AZ) is stuck in a bootloop, and I have tried to research why, yet every reason seams plausible. So ill start at the beginning...
I used odin with a boot.tar in the ap slot so that kingroot could root my phone. it was successful at rooting my device but refused to switch with supersu me( I now know I needed kingroot 4.5) anyways kingroot deployed as a system app which in turn compromised my safetynet status. I couldn't use a number of apps and services, so I decided to flash the stock rom for my device (found here on xda) it was a little over 1gb and I followed directions. yet when odin successfully flashed it, the device rebooted and now is stuck in a bootloop. it loads the Samsung logo twice then reverts to the android recovery. I tried to wipe cache partition and reboot to no avail. I then tried to wide data/factory reset and reboot, but its still stuck in bootloop.
I originally made a backup with Samsung smart switch, but now it says the device is unsupported.
Is there anything I can do? ive read soft bricks and bootloops can be fixed, but I'm not finding much on my device. any help is greatly appreciated,
sorry if this is in the wrong area, I'm still new to xda
Rororoolz said:
So my galaxy amp prime(Cricket, SM-J320AZ) is stuck in a bootloop, and I have tried to research why, yet every reason seams plausible. So ill start at the beginning...
I used odin with a boot.tar in the ap slot so that kingroot could root my phone. it was successful at rooting my device but refused to switch with supersu me( I now know I needed kingroot 4.5) anyways kingroot deployed as a system app which in turn compromised my safetynet status. I couldn't use a number of apps and services, so I decided to flash the stock rom for my device (found here on xda) it was a little over 1gb and I followed directions. yet when odin successfully flashed it, the device rebooted and now is stuck in a bootloop. it loads the Samsung logo twice then reverts to the android recovery. I tried to wipe cache partition and reboot to no avail. I then tried to wide data/factory reset and reboot, but its still stuck in bootloop.
I originally made a backup with Samsung smart switch, but now it says the device is unsupported.
Is there anything I can do? ive read soft bricks and bootloops can be fixed, but I'm not finding much on my device. any help is greatly appreciated,
sorry if this is in the wrong area, I'm still new to xda
Click to expand...
Click to collapse
Point to the firmware you downloaded and also which version of odin you used.
ashyx said:
Point to the firmware you downloaded and also which version of odin you used.
Click to expand...
Click to collapse
I extracted this
AP_J320AUCS2AQA1_CL7663112_QB12351033_REV00_user_low_ship.tar
i believe is the firmware, and I'm using odin 3.11.1
I also asked in page 17 of the original thread
I'm just running out of options here lol
you actually posted right above me in that thread!
Rororoolz said:
I extracted this
AP_J320AUCS2AQA1_CL7663112_QB12351033_REV00_user_low_ship.tar
i believe is the firmware, and I'm using odin 3.11.1
I also asked in page 17 of the original thread
I'm just running out of options here lol
Click to expand...
Click to collapse
I suggest you flash the entire firmware not just AP.
ashyx said:
I suggest you flash the entire firmware not just AP.
Click to expand...
Click to collapse
Do u happen to know where i can find the rest?
Would i have to re partition it? Because im trying to research and learn, but i was under the impression that AP was the only spot to put firmware
I believe your proper firmware would be J320AZTUU1APC4
http://www.mediafire.com/file/skiapd1xqj3s7se/J320AZTUU1APC4_J320AZAIO1APC4_5.1.1_USA_4Files.zip
seaf0ur said:
I believe your proper firmware would be J320AZTUU1APC4
http://www.mediafire.com/file/skiapd1xqj3s7se/J320AZTUU1APC4_J320AZAIO1APC4_5.1.1_USA_4Files.zip
Click to expand...
Click to collapse
The files say md5 error, binary failed
I think im missing something here
You tried to flash only AP but for J320A, here you have full firmware for J320AZ: https://drive.google.com/file/d/0B5vkBxwCY_cCSkh0UHNZMmxmcVk/view
johnny.goldy said:
You tried to flash only AP but for J320A, here you have full firmware for J320AZ: https://drive.google.com/file/d/0B5vkBxwCY_cCSkh0UHNZMmxmcVk/view
Click to expand...
Click to collapse
Most these files worked, i checked auto reboot, re partition, and r reset. I set the pit file and all 4 others in correct spot. Yet it failed a few times. I unchecked the bl file and it succeeded. When i reboot it shows logo twice then shows android saying installing sys update.... then error... then goes back to recovery.
Essentially i flashed everything except the bl file. And when i try to flash it by itself it says
Initialization
Erase...
Set PIT file
DO NOT TURN OFF TARGET
get pit for mapping
Firmware update starting
Single download
Sboot.bin
NAND write start!
Fail!
Complete(write) operation fail
............
Im guessing the problem is with my BL file
When i go to boot phone it shows an android and says installing system update then says error very quickly and goes to recovery.
I feel like thats progress but why would only BL file be failing? The green bar in odin goes halfway then fails (with only bl file checked)
Rororoolz said:
Most these files worked, i checked auto reboot, re partition, and r reset. I set the pit file and all 4 others in correct spot. Yet it failed a few times. I unchecked the bl file and it succeeded. When i reboot it shows logo twice then shows android saying installing sys update.... then error... then goes back to recovery.
Essentially i flashed everything except the bl file. And when i try to flash it by itself it says
Initialization
Erase...
Set PIT file
DO NOT TURN OFF TARGET
get pit for mapping
Firmware update starting
Single download
Sboot.bin
NAND write start!
Fail!
Complete(write) operation fail
............
Im guessing the problem is with my BL file
When i go to boot phone it shows an android and says installing system update then says error very quickly and goes to recovery.
I feel like thats progress but why would only BL file be failing? The green bar in odin goes halfway then fails (with only bl file checked)
Click to expand...
Click to collapse
It WILL fail at the bootloader as it's not intended for your device. Just flash the correct firmware as advised.
ashyx said:
It WILL fail at the bootloader as it's not intended for your device. Just flash the correct firmware as advised.
Click to expand...
Click to collapse
Thats what i mean, i extracted all 5 files as advised(a few comments ago) it had
BL
AP
CP
CSC
PIT
I placed them in corresponding odin slot (even pit, with re partition) yet it fails at the BL slot)
I flash it all except bl its still in bootloop
Also Says dm-verity verification failed
Mind you, that i am flashing the right firmware now. I realize my original mistake by flashing the 320a. But these are the stock 320AZ files i am now speaking of...
Rororoolz said:
Thats what i mean, i extracted all 5 files as advised(a few comments ago) it had
BL
AP
CP
CSC
PIT
I placed them in corresponding odin slot (even pit, with re partition) yet it fails at the BL slot)
I flash it all except bl its still in bootloop
Also Says dm-verity verification failed
Mind you, that i am flashing the right firmware now. I realize my original mistake by flashing the 320a. But these are the stock 320AZ files i am now speaking of...
Click to expand...
Click to collapse
This probably means you had a newer firmware revision on your device.
ashyx said:
This probably means you had a newer firmware revision on your device.
Click to expand...
Click to collapse
So do i have any options left? Or should i just chuck it into the cornfield
Rororoolz said:
So do i have any options left? Or should i just chuck it into the cornfield
Click to expand...
Click to collapse
Of course you probably just need the revision 3 firmware. It's posted at the link below.
https://forum.xda-developers.com/galaxy-j3-2016/development/odin-j320a-j320az-links-t3631914
J320AZTUS3AQG1
Try this one: https://www.androidfilehost.com/?fid=817550096634792721
johnny.goldy said:
Try this one: https://www.androidfilehost.com/?fid=817550096634792721
Click to expand...
Click to collapse
IT WORKED! Omg IT wOrked!
ashyx said:
Of course you probably just need the revision 3 firmware. It's posted at the link below.
https://forum.xda-developers.com/galaxy-j3-2016/development/odin-j320a-j320az-links-t3631914
J320AZTUS3AQG1
Click to expand...
Click to collapse
It wasnt the firmware you said, but thank you so much for the help!
Rororoolz said:
It wasnt the firmware you said, but thank you so much for the help!
Click to expand...
Click to collapse
Doesn't matter it was still revision 3 firmware.
The one linked is the latest revision 3 firmware.

Need help with Odin, cannot return to stock :(

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.

Categories

Resources