Related
Hey guys, so im trying to downgrade my firmware because I wanna root my phone withoud losing my DRM keys and stuff, but im kind of stuck at the step where I need to downgrade. I'm trying to downgrade using firmwares I found on this post (http://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706), but all the older firmwares that I need are causing bootloops. I've tried around 4 and they all caused bootloops, yet the 1 lollipop firmwares I tried worked just fine. What do I do? Anyone know of any firmwares that don't cause it? or am I doing something wrong?
Yair1991 said:
Hey guys, so im trying to downgrade my firmware because I wanna root my phone withoud losing my DRM keys and stuff, but im kind of stuck at the step where I need to downgrade. I'm trying to downgrade using firmwares I found on this post (http://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706), but all the older firmwares that I need are causing bootloops. I've tried around 4 and they all caused bootloops, yet the 1 lollipop firmwares I tried worked just fine. What do I do? Anyone know of any firmwares that don't cause it? or am I doing something wrong?
Click to expand...
Click to collapse
They will cause bootloops unless you wipe data. Tick wipe data,cache,appslog in flashtool. When you downgrade from one android version to another, there is a 99% chance of a bootloop. However, you can usually upgrade without problems.
Hi. I've searched the forums for 2 days now, and can't find any solutions to my issue.
I have had stock rooted OC4 (Lollipop 5.0) from the FlashFire method for months now. Tried "unrooting" with SuperSU, rebooted, and now I am soft bricked. Looks like I am still rooted though.
When I try flashing a stock rom with odin I get the message "fused 4 > binary 3". I think this means the rom I'm trying to flash (G900AUCU3BOC4-OneClick) is below the version I currently have. I currently DO have OC4 though, so I don't understand. Is there a newer stock rom version around? Has somebody made a OneClick or other Odin flashable rom for AT&T S5 versions later than 5.0? Can somebody make one?
Or if anyone has another solution to help restore my phone to stock that would be great!
I seem to have the same issue as you, if you or anyone figure out something please share!
I have the exact same issue. I have tried everything from flashing using Odin, to sideloading the stock firmware, but nothing works!!!!
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.
I had problems of phone rebooting automatically and showing emc-read error and cannot boot normally and had to remove battery to start my canadian note 4 W8
the way i fixed this **** is by reverting back to 5.0.1 bootloader
the newest bootloader is the cause of all problems for us
you cannot roll back to the old bootloader just by flashing an old bootloader
but luckily i have found a trick to revert back to a older bootloader to replace **** COK3 (Newest for canadian ) bootloader
So to actually roll back to old boot loader you need a full firmware which has capability to format internal storage when it is flashed
i had a 5.1.1 firmware tar but it did not have the capability of formatting internal storage when it is flashed
But i lucky found a older 5.0.1 tar in my harddisk that has the capability which enabled me to go back to old baseband and bootloader and formatted internal storage and now everything fine
Phone flying as before without any reboots emc read error or lags (i think the reason why this tar worked and back flashed the boot loader is because it formatted the internal storage while the tar was being executed)
just to be extra cautious,once you have old boot loader flash recovery and wipe system,cache,dalvik and internal storage
*IMP GO TO WIPE>FORMAT DATA AND TYPE YES
*MAKE SURE TO RE-FLASH JUST 5.1.1 BASEBAND FOR NOTE 5 PORTS AND CM12.1/13 TO HAVE NETWORK
Attaching the error i had and pic of my current setup
FOR PEOPLE WHO STILL CANNOT DOWNGRADE BOOT LOADER YOU CAN TRY PARTITIONING YOU INTERNAL MEMORY TO FIX READ WRITE ERRORS
LINK OF THE FIRMWARE I USED
http://forum.xda-developers.com/note-4/general/ref-stock-firmware-kernel-modem-recovery-t2920452
LINK TO PIT FILES FOR REPARTITIONING
http://forum.xda-developers.com/note-4/orig-development/note-4-pit-files-repartiton-f-g-c-t-w8-t3282641/post64569392#post64569392
Canadians having same issue can now flash this firmware to go back to 5.0.1 bootloader
*i think this would work for Tmobile users too but i am not sure about the risks of cross flashing
i checked my 5.0.1 and 5.1.1 tars and they both have same files so i cant tel which tar you should download for internal storage to be formatted
my most educated guess would be try and download early 5.0.1 builds as samsung must have implemented formatting internal storage when from kitkat to lollipop uograde
And odin 3.10.7
Help Me
Hi,
Can you please help me lookup stock firmware for SM-N910T(T Mobile Note 4) which I can use to rollback my bootloader.
Thank You
Please help me...
I'm using note 4 n910t and have the same problem of your phone before...very lag and auto turn off the phone,can't boot up or error "mmc read fail".
Can't use your firwame for n910t?!. I know that n910t and n910w8 can using same firwame
---------- Post added at 03:53 PM ---------- Previous post was at 03:47 PM ----------
Can you upload you 5.0.1 bootloader and the manual to fix this error?!
I think a lot of people have this issue when update to newest firwame from samsung, and they are watting for a way to fix their phone
Thanks a lots! ^^
I keep getting "auth" fails. I can only flash the 5.1.1 software
Please get back to us asap, it's driving me crazy with my phone consistently rebooting and freezing
McMichael96 said:
I keep getting "auth" fails. I can only flash the 5.1.1 software
Please get back to us asap, it's driving me crazy with my phone consistently rebooting and freezing
Click to expand...
Click to collapse
Flash custom rom first
Maybe a cm 12 build and try again
thiennvbk said:
Please help me...
I'm using note 4 n910t and have the same problem of your phone before...very lag and auto turn off the phone,can't boot up or error "mmc read fail".
Can't use your firwame for n910t?!. I know that n910t and n910w8 can using same firwame
---------- Post added at 03:53 PM ---------- Previous post was at 03:47 PM ----------
Can you upload you 5.0.1 bootloader and the manual to fix this error?!
I think a lot of people have this issue when update to newest firwame from samsung, and they are watting for a way to fix their phone
Thanks a lots! ^^
Click to expand...
Click to collapse
As i said before
just flashing the bootloader doesnt work
U need the full firmware with internal storage wiping capability to return to older bootloader
I will do one thing to help everyone out
Either i will track down the link to download the 5.0.1 firmware i used
Or
I will upload the full 1.7 gb tar firmware
Till then find a older 5.0.1 firmware for your model and try it
Ashwin Prabhunerurkar said:
Flash custom rom first
Maybe a cm 12 build and try again
Click to expand...
Click to collapse
I tried that. Still didn't work. And I have a pretty old copy of 5.0.1. I think it has to do with how T-Mobile/Samsung pushed security policy's to this device. I read up where the last ones actually prevent downgrades.
McMichael96 said:
I tried that. Still didn't work. And I have a pretty old copy of 5.0.1. I think it has to do with how T-Mobile/Samsung pushed security policy's to this device. I read up where the last ones actually prevent downgrades.
Click to expand...
Click to collapse
I checked on samfirmware
And the BOE2 firmware 5.0.1 i have is the last version of 5.0.1 just before 5.1.1 started rolling out
So download the last version of 5.0.1 just before 5.1.1 released
Ashwin Prabhunerurkar said:
I checked on samfirmware
And the BOE2 firmware 5.0.1 i have is the last version of 5.0.1 just before 5.1.1 started rolling out
So download the last version of 5.0.1 just before 5.1.1 released
Click to expand...
Click to collapse
Will the Canadian firmware even work in odin for the t-mobile variant?
McMichael96 said:
Will the Canadian firmware even work in odin for the t-mobile variant?
Click to expand...
Click to collapse
Tmobile roms work out of the box for canadian note 4
But bootloader is on a whole another level
U can easily flash another baseband if phones gets busted but i dont know about bootloader
If you are in warrenty you should give it a try
McMichael96 said:
Will the Canadian firmware even work in odin for the t-mobile variant?
Click to expand...
Click to collapse
It might but u shld download the BEO2 equivalent for tmobile
I don't know if I have this problem or not. A few days ago I installed "[N910TUVU2DOK2] Debloated-Deodexed Stock ROM[Dec-18-2015]" along with TWRP recovery. It has seemed to be OK, but I did have a couple of unexpected random reboots. Today while using the phone, it just froze. It did not reboot. After battery pull, I tried to get into recovery, but nothing but short vibrations every 10 seconds or so.
I have not seen any messages about emmc_. The screen remained black entirely. I was unable to get into download mode or recovery mode. When I plugged in with USB, I was able to get it to recognized on USB and in Odin, but had not idea what mode it was in since the screen was black.
After letting it sit a while, I tried again, and was able to boot into recovery. From there, I was able to reboot into Andriod, and everything seems to be normal again.
Is this the same issue? Should I revert the bootloader? If so, what is the correct bootloader for the TMO Note4 N910TUVU2DOK2 ? I have stock ROM for 5.0.1 (N910TUVU1COD6_N910TTMB1COD6_N910TUVU1COD6_HOME.tar.md5) which contains the file boot.img. But in the first post it says it is not possible to simply flash boot.img with Odin?
The required procedure is this?
1) Flash the 5.01 stock firmware N910TUVU1COD6_N910TTMB1COD6_N910TUVU1COD6_HOME.tar.md5 (including the desired bootloader)
2) Boot into stock firmware
3) Select Factory Reset (to execute the data wipe capability in 5.0.1)
4) Shut down and boot into download mode.
5) Flash TWRP
6) Flash 5.1.1 N910TUVU2DOK2 (previously modified to remove boot.img from the tar.md5 file?)
( would this step 6 cause the full functionality of 5.1.1 to be available, but with the non-broken bootloader?)
Ashwin Prabhunerurkar said:
As i said before
just flashing the bootloader doesnt work
U need the full firmware with internal storage wiping capability to return to older bootloader
I will do one thing to help everyone out
Either i will track down the link to download the 5.0.1 firmware i used
Or
I will upload the full 1.7 gb tar firmware
Till then find a older 5.0.1 firmware for your model and try it
Click to expand...
Click to collapse
That mean I can download last 5.0.1 firwame and use odin to flash??.
I have try one and odin fail because binary. It isn't allow to come back 5.0.1 firwame.
Can you share the link of 5.0.1 firwame that you had been flash over odin?!
Thanks
thiennvbk said:
That mean I can download last 5.0.1 firwame and use odin to flash??.
I have try one and odin fail because binary. It isn't allow to come back 5.0.1 firwame.
Can you share the link of 5.0.1 firwame that you had been flash over odin?!
Thanks
Click to expand...
Click to collapse
Hmm, it's not quite that simple. Just installing 5.0.1 would leave you downgraded to 5.0.1.
There are reasons to move to 5.1.1 (if it works right), so we're trying to determine how to get the BL from 5.0.1 and everything else from 5.1.1.
timg11 said:
Hmm, it's not quite that simple. Just installing 5.0.1 would leave you downgraded to 5.0.1.
There are reasons to move to 5.1.1 (if it works right), so we're trying to determine how to get the BL from 5.0.1 and everything else from 5.1.1.
Click to expand...
Click to collapse
you can flash the 5.0.1 firmware now and then flash a 5.1.1 custom rom
so the bootloader version doesnt matter as long as its lollipop
but for baseband you need 5.1.1 baseband for 5.1.1 roms to have network
thiennvbk said:
That mean I can download last 5.0.1 firwame and use odin to flash??.
I have try one and odin fail because binary. It isn't allow to come back 5.0.1 firwame.
Can you share the link of 5.0.1 firwame that you had been flash over odin?!
Thanks
Click to expand...
Click to collapse
i have a canadian W8 variaant and i am not sure about the risks of cross flashing
Luckly i found the link of the firmware i used
here it is
http://forum.xda-developers.com/note-4/general/ref-stock-firmware-kernel-modem-recovery-t2920452
Download the link in first post
Ashwin Prabhunerurkar said:
you can flash the 5.0.1 firmware now and then flash a 5.1.1 custom rom
so the bootloader version doesnt matter as long as its lollipop
but for baseband you need 5.1.1 baseband for 5.1.1 roms to have network
Click to expand...
Click to collapse
OK, when I flash the 5.1.1 custom ROM, wouldn't that put the bad boodloader back int?
If I want to end up on 5.1.1 N910TUVU2DOK2, Is this procedure correct?
1) Flash the 5.01 stock firmware N910TUVU1COD6_N910TTMB1COD6_N910TUVU1COD6_HOME.tar .md5 (including the desired bootloader)
2) Boot into stock firmware
3) Select Factory Reset (to execute the data wipe capability in 5.0.1)
4) Shut down and boot into download mode.
5) Flash TWRP
6) Flash 5.1.1 N910TUVU2DOK2 (previously modified to remove boot.img from the tar.md5 file?)
( would this step 6 cause the full functionality of 5.1.1 to be available, but with the non-broken bootloader?)
Questions:
1) Why is the bootloader causing problems with random reboots? During the boot process it corrupts memory?
2) is the problem in internal memory or EXT-SD or both?
3) does the 5.1.1 bootloader continue to corrupt the memory? I.E. if the memory corruption was repaired by other means, would it soon be corrupted again by the bootloader?
4) The T-Mobile 5.1.1 stock ROM has been out since August. This seems like a huge bug. Nobody has seen this issue until now? Or is it specific to rooted devices or the Beastmode kernel?
timg11 said:
OK, when I flash the 5.1.1 custom ROM, wouldn't that put the bad boodloader back int?
If I want to end up on 5.1.1 N910TUVU2DOK2, Is this procedure correct?
1) Flash the 5.01 stock firmware N910TUVU1COD6_N910TTMB1COD6_N910TUVU1COD6_HOME.tar .md5 (including the desired bootloader)
2) Boot into stock firmware
3) Select Factory Reset (to execute the data wipe capability in 5.0.1)
4) Shut down and boot into download mode.
5) Flash TWRP
6) Flash 5.1.1 N910TUVU2DOK2 (previously modified to remove boot.img from the tar.md5 file?)
( would this step 6 cause the full functionality of 5.1.1 to be available, but with the non-broken bootloader?)
Questions:
1) Why is the bootloader causing problems with random reboots? During the boot process it corrupts memory?
2) is the problem in internal memory or EXT-SD or both?
3) does the 5.1.1 bootloader continue to corrupt the memory? I.E. if the memory corruption was repaired by other means, would it soon be corrupted again by the bootloader?
4) The T-Mobile 5.1.1 stock ROM has been out since August. This seems like a huge bug. Nobody has seen this issue until now? Or is it specific to rooted devices or the Beastmode kernel?
Click to expand...
Click to collapse
boot loader is the problem
i was using an older version of 5.1.1 bootloader for months and everything was fine but as soon as i upgraded to latest, i started having problems
internal and ext are both fine but just to be safe and start fresh i recommend formatting internal storage
boot loader was not executing internal memory properly hence all the errors,older bootloaders are perfect and you wont face any problems
i haven't faced a single problem in 2 days
there are many versions of 5.1.1 stock roms with different names but i think the latest once is the culprit, so stay away from 5.1.1 recent builds and only flash 5.1.1 base band but try to keep 5.0.1 boot loader.
your procedure seems about right but my tar automatically executed internal memory format and not just factory reset
those are two different things
factory reset formats /data
internal memory formats /system /data /cache etc
so if you tar doesnt support inernal mem format
my suggestion would be to install twrp after 5.0.1 flash and go to wipe>advanced and wipe internal storage
dont flash 5.1.1 again unless you are sure its bootloader is working properly
you just need 5.1.1 baseband to have a well functioning phone
I believe you when you say it works for your variant, but man I don't think it's going to work for our t-mobile variant. Even though they're really similar, I don't believe the Canadian variant got the security policy update that prevents downgrading like we did.
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.