I have the leaked ver of Oreo installed, but I have an app that's incompatible with the new OS, so I've been trying to downgrade for several weeks now, with no success.
I've seen answers online that completely contradict each other- use Smart Switch backup (tried that, didn't roll back the OS), tried several versions of Odin and firmware, always get 'FAILED AUTH'.
Also seen some posts that say you can't downgrade, others that say yes you can.
Is it possible? How can I find out which bootloader I have?
I heard with Oreo they did the same as Apple do. They stop downgrading the OS, but I'm not sure about it.
I hope other members can help you.
I'm having the same issue, I have a Verizon tmb tmb vzw software version, I flashed the carrier switch CDC thing xxa I entered the codes what ever, but i don't k ow i kind of got stuck and flashed bra8 and it came up with tmobile after flashing that was my intention, and then I flashed oreo, I'm trying to roll back to update to the latest crb8 oreo but anything I try in Odin fails at initialization... or It just wont work, and the phone doesnt have a progress bar as I press start, it's like stuck, I'm losing my mind here, I even tried flashing tmobile and Verizon firmware on odin, I tried kies and switch to restore yo nougat bra8 with no go, even tried flashing the carrier switch thing, NOTHING IS WORKING different USB ports rebooting PC, reinstalled drivers, took aim out when odin, nothing.
Some one help us
Fixed
And just like that, as soon as I post this, I get it to work. After spending all night trying different versions of Prince Odin and different firmwares, I just switched to normal Odin and it worked immediately, so back to 7.1.1
can you please tell how and what you used to down grade note 8 back to 7.1.1....thanks
PAULG1919 said:
can you please tell how and what you used to down grade note 8 back to 7.1.1....thanks
Click to expand...
Click to collapse
Have you tried Odin and the firmware for your device?
as long as the version you want to downgrade to is same version bootloader would it not be fine?
ie.. v3 to v3 is fine but not v3 to v2
I haven't been rooting or flashing with the Note 8 yet but that's the understanding I have from other threads
briwil said:
And just like that, as soon as I post this, I get it to work. After spending all night trying different versions of Prince Odin and different firmwares, I just switched to normal Odin and it worked immediately, so back to 7.1.1
Click to expand...
Click to collapse
can you please share your files and steps?:good:
pls share your steps for downgrading
briwil said:
And just like that, as soon as I post this, I get it to work. After spending all night trying different versions of Prince Odin and different firmwares, I just switched to normal Odin and it worked immediately, so back to 7.1.1
Click to expand...
Click to collapse
i already tried few procedures with no luck. what do you mean in prince ODIN and normal ODIN ? i am using the latest 3.13.1, shd we use something else ?
btw, i have oreo ...U2 and the SAM nougat rom is ...U1, i cant find any nougat with U2.
appreciate any help here...
tks
I think they changed something in oreo , where you cant downgrade now. Odin. Maybe latest update annoying i know.....no work around yet
The thing is like this: you can always flash roms with EQUAL O HIGHER bootloader version, just that, and NEVER to a lower bootloader version, and this is not new
briwil said:
I have the leaked ver of Oreo installed, but I have an app that's incompatible with the new OS, so I've been trying to downgrade for several weeks now, with no success.
I've seen answers online that completely contradict each other- use Smart Switch backup (tried that, didn't roll back the OS), tried several versions of Odin and firmware, always get 'FAILED AUTH'.
Also seen some posts that say you can't downgrade, others that say yes you can.
Is it possible? How can I find out which bootloader I have?
Click to expand...
Click to collapse
Don't you want to try flashing only AP and CSC_OXM (not HOME)? I read on 4pda that it's possible, but you can have some errors while using your device.
Flash the oldest oreo with bootloader you have, then flash the latest nougat without BL and CP. Only AP and CSC OXM. Backup your data before doing it.
Related
Hey guys so recently I had rooted my i537 S4 active and have been researching and modifying here and there until i decided to get a custom ROM. I found WickedROM via this post http://forum.xda-developers.com/show....php?t=2491762 and considering it had worked on this person's i537 I decided to flash the ROM. After flashing I had become stuck in a bootloop and I can't get to anything besides DOWNLOAD MODE. Due to this problem I decided to run a stock firmware via Odin with this one_click http://rootzwiki.com/topic/44121-sgh...axy-s4-active/ ... this filled up until the bar was about 90% and then all of a sudden fails at <ID:0/003> system.img.ext4. I've tried other firmwares with no luck and have resorted to posting about this problem. please help and guide me in the right direction, my phone's been bricked for 3 days now. Trying to boot into recovery gives me the "there's been a problem with your firmware update, please run in Kies recovery" and Kies doesn't recognize my phone.
nickeon1 said:
After flashing I had become stuck in a bootloop and I can't get to anything besides DOWNLOAD MODE.
Click to expand...
Click to collapse
You forgot to flash the masterpatch which makes roms designed for the AT&T S4 (not active) work for our phone. If I understand correctly it needs to be flashed immediately after the rom is installed (i.e. still in SafeStrap, before you attempt to boot up).
nickeon1 said:
Due to this problem I decided to run a stock firmware via Odin with this one_click http://rootzwiki.com/topic/44121-sgh...axy-s4-active/ ... this filled up until the bar was about 90% and then all of a sudden fails at <ID:0/003> system.img.ext4 and Kies doesn't recognize my phone.
Click to expand...
Click to collapse
That link is for MF1, an outdated firmware. Here is a collection of stock i537 firmwares. I can personally confirm the NH3 file is usable since I used it to upgrade to the most recent firmware without losing root.
This thread will provide you instructions on how to use Odin to flash any stock firmware. I can only add I recommend using Odin v3.07, as I've used it with the most success and fewest issues. Also use NH3 firmware or at the very least NE3, because anything else is outdated, assuming you were on stock KitKat originally, and you will encounter similar issues if trying to downgrade to jellybean.
Also flashing with Odin deletes all your saved files/user info etc. on your phone. From the sound of it, fixing your phone is going to involve inevitably wiping it one way or the other, so I hope you have a backup saved somewhere other than your phone's internal memory.
nickeon1 said:
Hey guys so recently I had rooted my i537 S4 active and have been researching and modifying here and there until i decided to get a custom ROM. I found WickedROM via this post http://forum.xda-developers.com/show....php?t=2491762 and considering it had worked on this person's i537 I decided to flash the ROM. After flashing I had become stuck in a bootloop and I can't get to anything besides DOWNLOAD MODE. Due to this problem I decided to run a stock firmware via Odin with this one_click http://rootzwiki.com/topic/44121-sgh...axy-s4-active/ ... this filled up until the bar was about 90% and then all of a sudden fails at <ID:0/003> system.img.ext4. I've tried other firmwares with no luck and have resorted to posting about this problem. please help and guide me in the right direction, my phone's been bricked for 3 days now. Trying to boot into recovery gives me the "there's been a problem with your firmware update, please run in Kies recovery" and Kies doesn't recognize my phone.
Click to expand...
Click to collapse
When you flash back to stock, you can only flash a version that is equal to or greater than the version you were already on. So if you were originally on 4.4.2 you can only flash a 4.4.2 stock ROM, any other ROM will fail to flash.
thisisapoorusernamechoice said:
You forgot to flash the masterpatch which makes roms designed for the AT&T S4 (not active) work for our phone. If I understand correctly it needs to be flashed immediately after the rom is installed (i.e. still in SafeStrap, before you attempt to boot up).
That link is for MF1, an outdated firmware. Here is a collection of stock i537 firmwares. I can personally confirm the NH3 file is usable since I used it to upgrade to the most recent firmware without losing root.
This thread will provide you instructions on how to use Odin to flash any stock firmware. I can only add I recommend using Odin v3.07, as I've used it with the most success and fewest issues. Also use NH3 firmware or at the very least NE3, because anything else is outdated, assuming you were on stock KitKat originally, and you will encounter similar issues if trying to downgrade to jellybean.
Also flashing with Odin deletes all your saved files/user info etc. on your phone. From the sound of it, fixing your phone is going to involve inevitably wiping it one way or the other, so I hope you have a backup saved somewhere other than your phone's internal memory.
Click to expand...
Click to collapse
Thanks very much for this! I flashed an NE3 firmware and was able to get my phone in working condition. So if I wanted to flash a rom on my phone I would have to masterpatch AFTER the rom flash via Safestrap?
nickeon1 said:
Thanks very much for this! I flashed an NE3 firmware and was able to get my phone in working condition. So if I wanted to flash a rom on my phone I would have to masterpatch AFTER the rom flash via Safestrap?
Click to expand...
Click to collapse
Yes, but make sure the phone doesn't reboot in between flashing the ROM and flashing the Masterpatch.
i9305 Imei shows null/null after flashing I9305XXUFNL1_DBTFNL1 which was a stock rom
Also no signal as you would guess
Now I cant even downgrade to any roms apart from 4.4.4.
Phoen is rooted and tried 4.1.1. I9305XXALI5_I9305EVRALI5_I9305BVALI5 through Odin and Mobile ODIN
On Mobile odin phone looks like its working then stays on the SAMSUNG Logo for ages and nothing, just stays there
I have a Back up of an efs which I done through Rom Manager but not sure if its corrupted or how to restore it
If someone coud give me a walkthrough :highfive:
EwOkie said:
i9305 Imei shows null/null after flashing I9305XXUFNL1_DBTFNL1 which was a stock rom
Also no signal as you would guess
Now I cant even downgrade to any roms apart from 4.4.4.
Phoen is rooted and tried 4.1.1. I9305XXALI5_I9305EVRALI5_I9305BVALI5 through Odin and Mobile ODIN
On Mobile odin phone looks like its working then stays on the SAMSUNG Logo for ages and nothing, just stays there
I have a Back up of an efs which I done through Rom Manager but not sure if its corrupted or how to restore it
If someone coud give me a walkthrough :highfive:
Click to expand...
Click to collapse
Hi,
About IMEI null/null with 4.4.4 firmware, you should search in this Q/A forum, there a lot of threads asking for this issue. Maybe you should get an answer yourself
However, you should try again to do a clean flash of latest official 4.4.4 firmware with ODIN v3.09 by following this GUIDE HERE from @MaHo_66.
AFAIK, it's impossible to downgrade from 4.4.4 because of KNOX bootloader. It has been said many times in this Q/A forum. Maybe it exists somewhere a tricky trick to do it but I'm not aware of this.
FLooDW said:
Hi,
About IMEI null/null with 4.4.4 firmware, you should search in this Q/A forum, there a lot of threads asking for this issue. Maybe you should get an answer yourself
However, you should try again to do a clean flash of latest official 4.4.4 firmware with ODIN v3.09 by following this GUIDE HERE from @MaHo_66.
AFAIK, it's impossible to downgrade from 4.4.4 because of KNOX bootloader. It has been said many times in this Q/A forum. Maybe it exists somewhere a tricky trick to do it but I'm not aware of this.
Click to expand...
Click to collapse
In Addition to @FLooDW 's answer:
Try to use Philz 6.48.4 or 6.59.0 as your recovery rather then TWRP or the old CWM (6.0.4.7), especially DON'T use the latest TWRP from their official website, its a broken build and its known to mess up the partitions! That could be your problem if you have done that before...
Any recovery you want to use, download from my RECOVERY/GUIDE thread that FLooDW linked to you, use those they work fine.
PS. before flashing official firmware with ODIN, make sure you have a custom recovery installed, then boot into recovery, wipe system/data/cache/dalvik-cache/internalSD/boot/modem etc. this is to ensure when you have flashed the firmware, there is nothing left from the previous firmware that was installed.
Note: when explaining your issue, try to do that by providing as much as possible info about your actions before and after the problem occured, that way anyone who wants to help can help you the best way possible.
MaHo_66 said:
In Addition to @FLooDW 's answer:
Try to use Philz 6.48.4 or 6.59.0 as your recovery rather then TWRP or the old CWM (6.0.4.7), especially DON'T use the latest TWRP from their official website, its a broken build and its known to mess up the partitions! That could be your problem if you have done that before...
Any recovery you want to use, download from my RECOVERY/GUIDE thread that FLooDW linked to you, use those they work fine.
PS. before flashing official firmware with ODIN, make sure you have a custom recovery installed, then boot into recovery, wipe system/data/cache/dalvik-cache/internalSD/boot/modem etc. this is to ensure when you have flashed the firmware, there is nothing left from the previous firmware that was installed.
Note: when explaining your issue, try to do that by providing as much as possible info about your actions before and after the problem occured, that way anyone who wants to help can help you the best way possible.
Click to expand...
Click to collapse
Really helpful addition !
Trying what you guys have mentioned just now, let you know as soon as :good:
What 4.4.4. om do you suggest?
Also the efs I backed up (not sure if its working or not as it was with Rom Manager)
How do I restore, can it be done with root explorer?
Tried the [ROM][i9305][18.10.15]>>>4.4.4<<<[KK][STOCK][TW][STABLE][+AROMA] S5 Elite Lite v4.0
which I posted a few days ago, left a post with no reply and thats when I started getting the null/null
PSN_AGNi_pureSTOCK-v5.9.5-4.4.x_I9305_AROMA
Currently trying this rom.. watching the installation set up and says so far that set_perm: some changes failed
used philz_touch_6.59.0-i9305
Rebooting and stays on Samsung Galaxy boot screen ??
EwOkie said:
PSN_AGNi_pureSTOCK-v5.9.5-4.4.x_I9305_AROMA
Currently trying this rom.. watching the installation set up and says so far that set_perm: some changes failed
used philz_touch_6.59.0-i9305
Rebooting and stays on Samsung Galaxy boot screen ??
Click to expand...
Click to collapse
AGNi is not a ROM, this is a kernel. Did you flash AGNi kernel over official Samsung firmware ?
As MaHo_66 said, you have to explain more what you have done and what you need if you want us to help you.
Steps :
reflashed a Stock Rom then Rooted it then added Philz Recovery
Then Tried this rom : I9305XXUFNL1_O2UFOB1_4.4.4_KK.zip
Currently trying various modems to see what this gives me
Failing this will need to try QPTS or EFS Professional again.
* I know how to flash and root roms if you look at my signature along with kernels I am basically telling you what I have tried to get
this null/null away as I think its a baseband/modem issue somewhere as I have read various posts and some people agree.
Cant even do the *#197328640# or *#*#197328640#*#* to get into certain modes
Thinking it maybe the sim card slot now .......... I am losing my mind now!
EwOkie said:
Steps :
reflashed a Stock Rom then Rooted it then added Philz Recovery
Then Tried this rom : I9305XXUFNL1_O2UFOB1_4.4.4_KK.zip
Currently trying various modems to see what this gives me
Failing this will need to try QPTS or EFS Professional again.
* I know how to flash and root roms if you look at my signature along with kernels I am basically telling you what I have tried to get
this null/null away as I think its a baseband/modem issue somewhere as I have read various posts and some people agree.
Cant even do the *#197328640# or *#*#197328640#*#* to get into certain modes
Thinking it maybe the sim card slot now .......... I am losing my mind now!
Click to expand...
Click to collapse
There are few other possible solutions you could try:
- try this, it shows you how to get in service mode and the restoring of the golden efs backup, that should be present if its good.
If above doesnt work, then try the one below.
- have you tried to flash the param_bin file? if not try that with ODIN, it might work.. file attached.
Let us know how it goes.
H yes tied that file and didnt work
will the imei work from another phone or efs?
isnt that link just gps?
I have gone back and forth between 5.1.1, 5.0.1, and 4.4.4 roms by using odin to flash the COG2, COD6, or ANK4 firmware first, then using odin to flash autoroot and TWRP. Then use TWRP to flash the desired rom. I have no problem going from lollipop to kitkat and back. I have used the COG2 firmware for all the 5.1.1 roms, like Texxodus, Resurrection, Slim, CM12, etc. I have used COD6 for 5.0.1 like Alliance, I have used ANK4 for Firekat. I have never had a problem reverting between any of them.
Why is DOK2 different? Does it trip some kind of hardware switch, like knox? If I was on it and used odin to flash, say, the kitkat firmware, what happens? Does odin no longer work when you're on DOK? Does it crash? Does the flash appear to work but it stays on DOK? Does it flash the firmware but bootloop? Does it brick the phone? I always thought that odin flashed firmware to the lowest level so that as long as you could connect the phone to a PC and had a good firmware load, you could restore it.
I am sorry to belabor this, but nothing I have read has explained this. All you get is that once you are on DOK2, you can't go back, but no one seems to know why and no one appears to have tried using Odin to flash a previous firmware and can answer the questions in the previous paragraph.
phoneturf said:
I have gone back and forth between 5.1.1, 5.0.1, and 4.4.4 roms by using odin to flash the COG2, COD6, or ANK4 firmware first, then using odin to flash autoroot and TWRP. Then use TWRP to flash the desired rom. I have no problem going from lollipop to kitkat and back. I have used the COG2 firmware for all the 5.1.1 roms, like Texxodus, Resurrection, Slim, CM12, etc. I have used COD6 for 5.0.1 like Alliance, I have used ANK4 for Firekat. I have never had a problem reverting between any of them.
Why is DOK2 different? Does it trip some kind of hardware switch, like knox? If I was on it and used odin to flash, say, the kitkat firmware, what happens? Does odin no longer work when you're on DOK? Does it crash? Does the flash appear to work but it stays on DOK? Does it flash the firmware but bootloop? Does it brick the phone? I always thought that odin flashed firmware to the lowest level so that as long as you could connect the phone to a PC and had a good firmware load, you could restore it.
I am sorry to belabor this, but nothing I have read has explained this. All you get is that once you are on DOK2, you can't go back, but no one seems to know why and no one appears to have tried using Odin to flash a previous firmware and can answer the questions in the previous paragraph.
Click to expand...
Click to collapse
Try it and report back. The bootloader can never be downgraded once it has been updated but I have heard of people odining back to kitkat from 5.1.1 and them getting it to work. Not sure how it was done but they did it.
DeeXii said:
Try it and report back. The bootloader can never be downgraded once it has been updated but I have heard of people odining back to kitkat from 5.1.1 and them getting it to work. Not sure how it was done but they did it.
Click to expand...
Click to collapse
You say the bootloader can never be downgraded once it has been updated. Okay, that's what everyone says. But is it true? No one seems to know. And if it is true, why? I find this very odd that no one knows.
My current favorite rom is Alliance since for me it has the best battery life and the least lag of the roms I have tried, so I don't want to take a chance that I can no longer run it if I flash DOK2 and don't like it.
phoneturf said:
You say the bootloader can never be downgraded once it has been updated. Okay, that's what everyone says. But is it true? No one seems to know. And if it is true, why? I find this very odd that no one knows.
My current favorite rom is Alliance since for me it has the best battery life and the least lag of the roms I have tried, so I don't want to take a chance that I can no longer run it if I flash DOK2 and don't like it.
Click to expand...
Click to collapse
go here for your answers
http://forum.xda-developers.com/not...-solution-to-emmcread-write-problems-t3281179
My understanding is that it's part of a new "security policy", I believe implemented by Tmo. My source of this info isn't related directly to my Note 4, but last month I Jumped my tablet to a new Samsung Galaxy Tab S2 that came loaded with 5.1.1. The day after picking it up I got a notification for a firmware update, still 5.1.1 (small size), screenshot of the "release notes" attached below. I didn't take the update and froze updates in TiBu. There's not a whole lot of development for that device yet and I think that I would have lost root if I had taken it.
I'm all for "security", but disabling users' ability to downgrade firmware hardly seems like much of a contribution to that end. IMO this is a disappointing development, and has much greater potential to affect "power users" vs. "regular users" as I doubt that a regular user downgrading the firmware on their device to their determent is something that even happens... ever.
jazzmachine said:
My understanding is that it's part of a new "security policy", I believe implemented by Tmo. My source of this info isn't related directly to my Note 4, but last month I Jumped my tablet to a new Samsung Galaxy Tab S2 that came loaded with 5.1.1. The day after picking it up I got a notification for a firmware update, still 5.1.1 (small size), screenshot of the "release notes" attached below. I didn't take the update and froze updates in TiBu. There's not a whole lot of development for that device yet and I think that I would have lost root if I had taken it.
I'm all for "security", but disabling users' ability to downgrade firmware hardly seems like much of a contribution to that end. IMO this is a disappointing development, and has much greater potential to affect "power users" vs. "regular users" as I doubt that a regular user downgrading the firmware on their device to their determent is something that even happens... ever.
Click to expand...
Click to collapse
Canadian note 4 dont seem to have the security lock on them since i rolled back to 5.0.1 bootloader but yes it wont let u roll back to any other 5.1.1 bootloader
U can try to download canadian BOE2 firmware and flash that since tmobile nd canada r pretty mch the same
This can be very dangerous so be cautious
phoneturf said:
I have gone back and forth between 5.1.1, 5.0.1, and 4.4.4 roms by using odin to flash the COG2, COD6, or ANK4 firmware first, then using odin to flash autoroot and TWRP. Then use TWRP to flash the desired rom. I have no problem going from lollipop to kitkat and back. I have used the COG2 firmware for all the 5.1.1 roms, like Texxodus, Resurrection, Slim, CM12, etc. I have used COD6 for 5.0.1 like Alliance, I have used ANK4 for Firekat. I have never had a problem reverting between any of them.
Why is DOK2 different? Does it trip some kind of hardware switch, like knox? If I was on it and used odin to flash, say, the kitkat firmware, what happens? Does odin no longer work when you're on DOK? Does it crash? Does the flash appear to work but it stays on DOK? Does it flash the firmware but bootloop? Does it brick the phone? I always thought that odin flashed firmware to the lowest level so that as long as you could connect the phone to a PC and had a good firmware load, you could restore it.
I am sorry to belabor this, but nothing I have read has explained this. All you get is that once you are on DOK2, you can't go back, but no one seems to know why and no one appears to have tried using Odin to flash a previous firmware and can answer the questions in the previous paragraph.
Click to expand...
Click to collapse
I have been try a lot of time for use odin to flash cog2 or cod6 from dok2. And it allway fail in odin. And you will receive a notice in the download mode screen like that o"Odin fai, binary =2>1". So you can't flash succesfull in odin.
And evething can't change. I have read 5.1.1 plicy and it also said that we can't downgrade from t mobile phone.lol
Perhaps development can recompile bootloader without tmo security and use Canadian firm to patch.
I just upgrade from COG2 to DOK2. Is there any difference? Which is better?
I have the N910T.
Dok2 has been reported to have improved performance and battery life than cog2 but cannot be downgraded.
Bruce lee roy said:
Dok2 has been reported to have improved performance and battery life than cog2 but cannot be downgraded.
Click to expand...
Click to collapse
I see. My cook ROM say use DOK2. I didnt know about the downgrade. I guess its ok and thanks for the info.
Galaxy Note 5 SM-N920G I need some help here. After a long time using custom roms, recently I've tried to flash a stock rom to my device (it was an Indian nougat rom from sammobile) and I got an error on Odin when flashing system. After that I lost my recovery (TWRP) an my Note 5 went only in download mode. Then a I flashed TWRP again and installed a custom rom again. Now I'm trying to flash any stock rom and I am getting random errors like "device 1 binary 0". I've tried many different roms and 0 luck. Someone could help me here? I never have this problem before and I just don't know more what to do.
diegowebber said:
Galaxy Note 5 SM-N920G I need some help here. After a long time using custom roms, recently I've tried to flash a stock rom to my device (it was an Indian nougat rom from sammobile) and I got an error on Odin when flashing system. After that I lost my recovery (TWRP) an my Note 5 went only in download mode. Then a I flashed TWRP again and installed a custom rom again. Now I'm trying to flash any stock rom and I am getting random errors like "device 1 binary 0". I've tried many different roms and 0 luck. Someone could help me here? I never have this problem before and I just don't know more what to do.
Click to expand...
Click to collapse
Peace..
I'm having the same exact problem--I found firmware that only flashed to radio--then abruptly stopped--wiping my system, so i'm stuck in download mode, phone will not power off. Instead of flashing Nougat ROM, i opted to flash "stock" MM firmware (6.01) and let phone update to Nougat on its on---then re-root it. As of now I have a paper-weight and it appears there's no support for 920G
Have you all tried Smart Switch?
CodeNameRedNeck said:
Have you all tried Smart Switch?
Click to expand...
Click to collapse
Yes... Smart Switch gave me an error in 2 ways of restoration.
ZEDEK said:
Peace..
I'm having the same exact problem--I found firmware that only flashed to radio--then abruptly stopped--wiping my system, so i'm stuck in download mode, phone will not power off. Instead of flashing Nougat ROM, i opted to flash "stock" MM firmware (6.01) and let phone update to Nougat on its on---then re-root it. As of now I have a paper-weight and it appears there's no support for 920G
Click to expand...
Click to collapse
Paper-weight? That's bad... Can't you flash a custom recovery on Odin and install a custom rom? I still can do that.
diegowebber said:
Galaxy Note 5 SM-N920G I need some help here. After a long time using custom roms, recently I've tried to flash a stock rom to my device (it was an Indian nougat rom from sammobile) and I got an error on Odin when flashing system. After that I lost my recovery (TWRP) an my Note 5 went only in download mode. Then a I flashed TWRP again and installed a custom rom again. Now I'm trying to flash any stock rom and I am getting random errors like "device 1 binary 0". I've tried many different roms and 0 luck. Someone could help me here? I never have this problem before and I just don't know more what to do.
Click to expand...
Click to collapse
It's because you flashed Nougat and that's Android 7.0 and it now thinks you're trying to "downgrade", which is pretty much blocked by trying to use "stock" roms.. The only thing you could probably do is find the stock rom you're interested in flashing but make sure it can be flashed via TWRP.. I don't think you can use Odin now to flash backwards "downgrade" to another stock rom after flashing Nougat 7.0..
MrMike2182 said:
It's because you flashed Nougat and that's Android 7.0 and it now thinks you're trying to "downgrade", which is pretty much blocked by trying to use "stock" roms.. The only thing you could probably do is find the stock rom you're interested in flashing but make sure it can be flashed via TWRP.. I don't think you can use Odin now to flash backwards "downgrade" to another stock rom after flashing Nougat 7.0..
Click to expand...
Click to collapse
Interesting... So maybe I can wait for a nougat ZTO ROM an then try to flash? Anyway, thanks for the help
MrMike2182 said:
It's because you flashed Nougat and that's Android 7.0 and ..
Click to expand...
Click to collapse
Good catch, I hadn't even thought of that.
CodeNameRedNeck said:
Good catch, I hadn't even thought of that.
Click to expand...
Click to collapse
Well I figured out you can downgrade from Nougat to Marshmallow but that's only to a specific firmware version. Depending upon what bootloader has been flashed (meaning if you flashed Nougat bootloader you can only go back to Marshmallow with the same bootloader level).. But this is only working (surprisingly) on the locked bootloaders of Verizon and AT&T.. The other S6 Edge Plus I have with an unlocked bootloader and tripped knox that I recently acquired will not accept nothing stock which is unusual, but I'm still working on that one.
So I had a botched situation caused by me when flashing a custom Rom (Rom/instructions is great, I went off the reservation myself) and had a soft brick.
I had decided at that point to just revert back to stock and not play around until things stabilize with Eng more. However, I couldn't.
The last stock referenced topic is with an outdated firmware and being 950U1 rather than just U. Downloading updated firmwares (or even attempting that one blindly) resulted in "Device dismatch".
I was then basically forced to (and successfully) go to SamPWN but that wasn't my initial intention.
Does anyone have an updated guide on how we can go back to stock without EngBoot, and specifically also states which CSC file is needed?
uaktags said:
So I had a botched situation caused by me when flashing a custom Rom (Rom/instructions is great, I went off the reservation myself) and had a soft brick.
I had decided at that point to just revert back to stock and not play around until things stabilize with Eng more. However, I couldn't.
The last stock referenced topic is with an outdated firmware and being 950U1 rather than just U. Downloading updated firmwares (or even attempting that one blindly) resulted in "Device dismatch".
I was then basically forced to (and successfully) go to SamPWN but that wasn't my initial intention.
Does anyone have an updated guide on how we can go back to stock without EngBoot, and specifically also states which CSC file is needed?
Click to expand...
Click to collapse
I may not have the answer, but check these guys and ask questions there, you should get an answer.
https://forum.xda-developers.com/tm.../guide-how-to-convert-to-100-stock-t-t3615957
And this link if from an unlocked S8 forum, but it has some info that you can find useful.
https://forum.xda-developers.com/galaxy-s8/how-to/snap-guide-flashing-standard-fw-carrier-t3625817
Charkatak said:
I may not have the answer, but check these guys and ask questions there, you should get an answer.
https://forum.xda-developers.com/tm.../guide-how-to-convert-to-100-stock-t-t3615957
And this link if from an unlocked S8 forum, but it has some info that you can find useful.
https://forum.xda-developers.com/galaxy-s8/how-to/snap-guide-flashing-standard-fw-carrier-t3625817
Click to expand...
Click to collapse
Download latest firmware for your phone, download Odin. Then flash them.
mweinbach said:
Download latest firmware for your phone, download Odin. Then flash them.
Click to expand...
Click to collapse
As I stated, I've attempted this and it failed. Plus it doesn't explain which file for the CSC had it worked anyhow. Downloading the latest results in the model dismatch. So can't JUST download and flash. But thanks for atleadt trying.
@charkata thanks for the links, I'll check them out and see how that goes.
uaktags said:
As I stated, I've attempted this and it failed. Plus it doesn't explain which file for the CSC had it worked anyhow. Downloading the latest results in the model dismatch. So can't JUST download and flash. But thanks for atleadt trying.
@charkata thanks for the links, I'll check them out and see how that goes.
Click to expand...
Click to collapse
Not the home version. And try using modified Odin.
mweinbach said:
Not the home version. And try using modified Odin.
Click to expand...
Click to collapse
I'll give it a go, going to try to do it in an hour or so and see if it'll work with the PrinceC version.
Is there any chance (in your or anyone elses opinion) that the mismatch could be the result of the custom rom being based on U1 rather than just U?
uaktags said:
I'll give it a go, going to try to do it in an hour or so and see if it'll work with the PrinceC version.
Is there any chance (in your or anyone elses opinion) that the mismatch could be the result of the custom rom being based on U1 rather than just U?
Click to expand...
Click to collapse
No, it can't modify hardware based model number.
uaktags said:
So I had a botched situation caused by me when flashing a custom Rom (Rom/instructions is great, I went off the reservation myself) and had a soft brick.
I had decided at that point to just revert back to stock and not play around until things stabilize with Eng more. However, I couldn't.
The last stock referenced topic is with an outdated firmware and being 950U1 rather than just U. Downloading updated firmwares (or even attempting that one blindly) resulted in "Device dismatch".
I was then basically forced to (and successfully) go to SamPWN but that wasn't my initial intention.
Does anyone have an updated guide on how we can go back to stock without EngBoot, and specifically also states which CSC file is needed?
Click to expand...
Click to collapse
You should be able to just completely reflash the stock TMB firmware with the modded Odin without an issue...am I understanding correctly that this did not work? Download the Prince Comsey modded Odin. It has a .ini file that you need to open w/ a text editor like notepad++, and edit UMS=0 to UMS=1 -this allows you to also flash the userdata file included in the TMB firmware, along w/ the normal BL, AP, CP & CSC.
Make sure you downloaded the correct firmware for the S8 (G950U), not S8+ (G955U).
https://updato.com/firmware-archive-select-model?record=F9F75B5C6CF011E7963AFA163EE8F90B
Did this work? Can anyone confirm? If not, I'm going to try it this weekend and hopefully I'll remember to reply here with results.