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.
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.
I'm running an N910T with Rapture 8.2. As this ROM apparently isn't under development or support any longer, I'd like to move to another ROM that is. I'd also like to update my baseband to N910TUVU2DOK2. To update the baseband, do I need to ODIN back to stock and upgrade from there, or can I simply ODIN the baseband and move forward? I believe that I'm currently on COG1, but can't tell because I'm running a backup just now.
dmathis said:
I'm running an N910T with Rapture 8.2. As this ROM apparently isn't under development or support any longer, I'd like to move to another ROM that is. I'd also like to update my baseband to N910TUVU2DOK2. To update the baseband, do I need to ODIN back to stock and upgrade from there, or can I simply ODIN the baseband and move forward? I believe that I'm currently on COG1, but can't tell because I'm running a backup just now.
Click to expand...
Click to collapse
You always need to Odin to the full firmware that matches the ROM you want to use. Please keep in mind that once you go to 5.1.1, you'll be stuck on lollipop bootloader.
Sent from my SM-N910T using Tapatalk
Thanks! Should I ODIN to stock, or straight to the new ROM? I rooted and flashed my old note 2 gobs of times, but the note 4 I'm not that sure about.
dmathis said:
Thanks! Should I ODIN to stock, or straight to the new ROM? I rooted and flashed my old note 2 gobs of times, but the note 4 I'm not that sure about.
Click to expand...
Click to collapse
You use Odin to put stock firmware on and to root and add TWRP. You use TWRP to flash ROM's.
Sent from my SM-N910T using Tapatalk
Thanks! That's just what I needed.
You're very welcome
Sent from my SM-N910T using Tapatalk
Pick_A_Name said:
You always need to Odin to the full firmware that matches the ROM you want to use. Please keep in mind that once you go to 5.1.1, you'll be stuck on lollipop bootloader.
Click to expand...
Click to collapse
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'm on the tmo Galaxy N4 (SM-910T) and I want to try a N7 port, but I flashed one and it's in a boot loop. I have reason to believe that it will not work on will I am still on DOK2 so, I wanted to know if there's any way to update my phone through ODIN to 6.0.1 because I've tried going back to stock but it won't let me update for some reason.... So I'm trying to figure out if there is some kind of file I could flash to update it, or perhaps a rom I could use that would let me update since my stock won't let me... Thanks in advance.
(PS. I seen a thread on someone wanting to downgrade from EPG2 to DOK2. They say you can't go back, and I only have one phone still on 5.1.1, which is my N4. Is EPG2 worth it? Should I stay on DOK2 or should I really persue updating?)
The epg2 tar should be available from Samsung or here on the forums. I believe I downloaded it from a post here somewhere because I couldn't get my phone to install the update through ota due to bad home Internet and using an mvno so there's no free update data. I like the stock MM although the settings screen and colors are all awful. It's not been bad on battery for me or had any real issues. Using stock with magisk only.
gunz.jones said:
The epg2 tar should be available from Samsung or here on the forums. I believe I downloaded it from a post here somewhere because I couldn't get my phone to install the update through ota due to bad home Internet and using an mvno so there's no free update data. I like the stock MM although the settings screen and colors are all awful. It's not been bad on battery for me or had any real issues. Using stock with magisk only.
Click to expand...
Click to collapse
Alright i'll go search thank you
H3dgehog said:
Alright i'll go search thank you
Click to expand...
Click to collapse
http://forum.xda-developers.com/not...-maximum-ovrdrive-6-0-1-mm-beta-4-13-t3358326 it's in the first post of this thread. Near the bottom in the downloads section.
Hi Everyone,
I am kind of lost in the upgrade process.
6 months ago, my Samsung Note 3 (USA AT&T) phone was working perfectly fine, but just with OLD firmware. ,then due to urge on upgrading, i searched so many sites and found a link somewhere on droidviews.com (as my firmware was NJ1 or something, website said i need to upgrade to NC2, and then to OC1), this process messed up my phone call receiving & making capabilities.
Most of the time callers see me unreachable and I am unable to call them as i get "emergency calls only"....I still don't have a way out from this issue. Some places I read i need to install right CSC / modem etc, I even tried this thread by reflashing using ODIN & N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar. Even after this, i still have calls related issues same as above.
Can someone guide me to right direct (or) did i totally messed up with this? BTW, i am now in INDIA, using Airtel services...
I believe nj1 firmware is newer than nc2.
The Odin files came from here: https://forum.xda-developers.com/note-3-att/general/100-stock-lollipop-5-0-n900aucueoc1-t3069609 ?
audit13 said:
I believe nj1 firmware is newer than nc2.
The Odin files came from here: https://forum.xda-developers.com/note-3-att/general/100-stock-lollipop-5-0-n900aucueoc1-t3069609 ?
Click to expand...
Click to collapse
Thanks. I tried flashing to OC1, still same problem. my calls are mostly not working. Is there a way i can go back to original 4.3 stock rom that came with Note3 AT&T? or is there a way i can get current AT&T rom (latest) to try with?
Good part is, i can go between 4.4.3 and 5.0 as i have original stock roms downloaded. But bad part is, my calls still failing...
appreciate any clue/help.
Where did you get the stock ROM? AT&T never released full firmware for the 900a.
There is no way to go back fully to 4.3 since the phone bootloader can be downgraded to 4.3.
audit13 said:
Where did you get the stock ROM? AT&T never released full firmware for the 900a.
There is no way to go back fully to 4.3 since the phone bootloader can be downgraded to 4.3.
Click to expand...
Click to collapse
Hi, i downloaded NC2 & OC1 stock firmwares from XDA only. they are loading up fine (using ODIN). But my calling problem remains same.
So, Yesterday, i tried rooting the phone and installed AllianceROM. then i went into series of issues like "unfortunately NFC has stopped", "unfortunately settings has stopped" etc... then followed the instruction to wipe/factory reset, 3 to 4 times and disabled NFC services etc. As of now, phone works fine, but still need to check the calling function for a week...
thanks for your time.
audit13 said:
Where did you get the stock ROM? AT&T never released full firmware for the 900a.
There is no way to go back fully to 4.3 since the phone bootloader can be downgraded to 4.3.
Click to expand...
Click to collapse
Are we SOL with 900a? I was in the wrong forum earlier and was ready to use update to 7...until I realized it wasn't for me.
Dying on Lollipop (where I landed after the 7 fallout)
I re-read my post and noticed that I made an error: the bootloader on an n900a CANNOT be downgraded.
You cannot flash any ROM to the phone using TWRP, you must use flashfire. Only ROMs based on the stock Samsung ROM can be flashed to the n900a.
audit13 said:
I re-read my post and noticed that I made an error: the bootloader on an n900a CANNOT be downgraded.
You cannot flash any ROM to the phone using TWRP, you must use flashfire. Only ROMs based on the stock Samsung ROM can be flashed to the n900a.
Click to expand...
Click to collapse
We can flash roms using safestrap and flashfire
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.