Related
Hi guys,
I hope all of you are fine, now after more than one year of usage of OPPO R7Plusf which was really amazing, it seems like OPPO has no plans to upgrade our phones, when I purchased my device a ColorOS version 2.0 was installed already and recently, it was upgraded to ColorOS version 2.1.0i (based on 5.1.1 Android Lollipop). Nowadays, all of us heard about the Nougat upgrade when we still dreaming with Marshmallow!!
So please, any suggestions for a custom ROM (tested) to upgrade my OPPO phone to Nougat version with no usual known errors or bugs. I will be grateful.
Notice: I contacted both customer support (the local one and the international) and I received the usual formal disappointed answer: "we will inform you when the update is available", which I think it will not be.
So thanks
Anybody here!?
Depends what you like
I currently use Resurrection remix on mine however there are some issues with apps force closing is my main one. Lineage OS also had issues for me with bluetooth causing the phone the reboot over and over. CM 13 was the best but I can't find any download links for it any more (rip CM) I think they both have updates coming outside but I recommend trying some out and then making a decision. Also if your phone is on one of the latest oppo updates (one of the 2016 updates) you'll have to downgrade to a 2015 software as they locked the bootloader so you won't be able to root! It's easy to do just find an old firmware from the internet (I would post links but I can't, also has to be a 2015 one) turn off the phone and turn it back on whilst holding down the volume down button and then go install and install the old firmware and then follow any guides on the internet for installing custom ROMs
Hope this helped
Meroslave said:
Anybody here!?
Click to expand...
Click to collapse
Lol, yeah. There is not much traffic here, but the R7Plusf is still awesome and up to date. Mainly due to good people at LineageOS keeping the device fresh.
I don't have serious issues with AICP on Nougat. No reboots. It is build "on top of" LineageOS, but have more features plus a working theming system. Latest build uploaded today.
Try RR, AICP and LineageOS and see what you like. Wait with Lineage untill the next release (current is Feb 14), if you want to avoid reboots.
ccrocks426 said:
I currently use Resurrection remix on mine however there are some issues with apps force closing is my main one. Lineage OS also had issues for me with bluetooth causing the phone the reboot over and over. CM 13 was the best but I can't find any download links for it any more (rip CM) I think they both have updates coming outside but I recommend trying some out and then making a decision. Also if your phone is on one of the latest oppo updates (one of the 2016 updates) you'll have to downgrade to a 2015 software as they locked the bootloader so you won't be able to root! It's easy to do just find an old firmware from the internet (I would post links but I can't, also has to be a 2015 one) turn off the phone and turn it back on whilst holding down the volume down button and then go install and install the old firmware and then follow any guides on the internet for installing custom ROMs
Hope this helped
Click to expand...
Click to collapse
So, you recommend the CM13 in case it's available?
And what's the cons and pros?
teemo said:
Lol, yeah. There is not much traffic here, but the R7Plusf is still awesome and up to date. Mainly due to good people at LineageOS keeping the device fresh.
I don't have serious issues with AICP on Nougat. No reboots. It is build "on top of" LineageOS, but have more features plus a working theming system. Latest build uploaded today.
Try RR, AICP and LineageOS and see what you like. Wait with Lineage untill the next release (current is Feb 14), if you want to avoid reboots.
Click to expand...
Click to collapse
Sure I will try one of your recommendations, but all I was afraid of was the disappointed bugs after updat such as battery drain, camera errors, wifi issues ... etc. Of course my ColorOS became boring to me, but still stable with no errors
Any pros or cons for those above I will be great full
Meroslave said:
Sure I will try one of your recommendations, but all I was afraid of was the disappointed bugs after updat such as battery drain, camera errors, wifi issues ... etc. Of course my ColorOS became boring to me, but still stable with no errors
Any pros or cons for those above I will be great full
Click to expand...
Click to collapse
Battery drain on MM has improved compared to Lollipop and N has improved over MM. With 4 email accounts running (on Aqua Mail) and Location on "High accuracy", Viber messenger and other stuff running, I had not much drain on AICP 11 (MM). Drain during night with Location on "Device" was 0.5% per hour. On MM and especially N, you have many ways in settings you can fine tune battery drain. Many apps are automatically shut down when not in use. You can decide which to limit and which to keep running when phone is off. Without extra apps (as ColorOS has), you can limit what apps are allowed to do and see. All built into the system.
A final word on drain: With Googles and others services running all the time, tracking everything you do, some drain is expected. Luckily this can be turned off by you
The number one reason to upgrade in these hacker friendly times: N is updated with much improved security. Updated every month with the latest security patches.
For me, AICP 11 is error free. The latest MM builds are complete in features and practically error free. Features are still being merged one at the time on N, but is useable as is now with only some minor issues.
I have not tried RR. My guess is that it has more features than AICP, but also more issues.
Lineage is the mother of all, I expect it to be stable with a good set of features.
All the N builds have more or less issues with speaker-phone. It may or may not bother you (or the person in the other end). MM was not affected as much as N, for some unknown reason.
I use Resurrection Rom and very happy with this rom!
i am beginer
i have oppo r7 plus f. tried the auto root tool but ended up hard bricking my phone. i am a beginer and i do not have much knowledge .
want to install lineage os on my oppo r7 plus f please tell me some easy ways.
Meroslave said:
Hi guys,
I hope all of you are fine, now after more than one year of usage of OPPO R7Plusf which was really amazing, it seems like OPPO has no plans to upgrade our phones, when I purchased my device a ColorOS version 2.0 was installed already and recently, it was upgraded to ColorOS version 2.1.0i (based on 5.1.1 Android Lollipop). Nowadays, all of us heard about the Nougat upgrade when we still dreaming with Marshmallow!!
So please, any suggestions for a custom ROM (tested) to upgrade my OPPO phone to Nougat version with no usual known errors or bugs. I will be grateful.
Notice: I contacted both customer support (the local one and the international) and I received the usual formal disappointed answer: "we will inform you when the update is available", which I think it will not be.
So thanks
Click to expand...
Click to collapse
supriyo_rana said:
i have oppo r7 plus f. tried the auto root tool but ended up hard bricking my phone. i am a beginer and i do not have much knowledge .
want to install lineage os on my oppo r7 plus f please tell me some easy ways.
Click to expand...
Click to collapse
Rana, first I'm sure you have been a good phone user and your Oppo R7 plus is upto date, unfortunately this is a problem. So first thing you need to do (Assuming you have unbricked your phone) is find a older version of the genuine R7+ firmware. Preferably some time between 2015- mid2016. The reason for this is OPPO locked the bootloader on later versions, these earlier versions are what the autoroot tool was designed to work on. Once you have this firmware, flash through recovery (provided you still have genuine OPPO recovery), if not you also need to flash this. Once you have the older firmware on your phone you should be able to proceed as usual steps to install lineage on your phone using typical walkthroughs.
what to do next?
DooganAU said:
Rana, first I'm sure you have been a good phone user and your Oppo R7 plus is upto date, unfortunately this is a problem. So first thing you need to do (Assuming you have unbricked your phone) is find a older version of the genuine R7+ firmware. Preferably some time between 2015- mid2016. The reason for this is OPPO locked the bootloader on later versions, these earlier versions are what the autoroot tool was designed to work on. Once you have this firmware, flash through recovery (provided you still have genuine OPPO recovery), if not you also need to flash this. Once you have the older firmware on your phone you should be able to proceed as usual steps to install lineage on your phone using typical walkthroughs.
Click to expand...
Click to collapse
thanks for your reply
yeah i went to the ofiicial service centre for the unbricking , noy it is working fine with letest firmware . now according to you i should downgrade the firmware . but how to do it ? should i do it via oppo stock recovery? or via the local update option of system updater in the menu?
supriyo_rana said:
thanks for your reply
yeah i went to the ofiicial service centre for the unbricking , noy it is working fine with letest firmware . now according to you i should downgrade the firmware . but how to do it ? should i do it via oppo stock recovery? or via the local update option of system updater in the menu?
Click to expand...
Click to collapse
i have the same concern also. Can someone please provide a step by step instruction on how to downgrade the firmware to the old version?
supriyo_rana said:
thanks for your reply
yeah i went to the ofiicial service centre for the unbricking , noy it is working fine with letest firmware . now according to you i should downgrade the firmware . but how to do it ? should i do it via oppo stock recovery? or via the local update option of system updater in the menu?
Click to expand...
Click to collapse
bu11et said:
i have the same concern also. Can someone please provide a step by step instruction on how to downgrade the firmware to the old version?
Click to expand...
Click to collapse
Try here: https://forum.xda-developers.com/showpost.php?p=73786100&postcount=139
unlock bootloader still stuck..
Hi Guys..
First i don't know if i am posting this in right thread or not... but I need help... after lots of search i couldn't find anything to unlock my oppo R7 plus running r7plusEx_11_160922 on color os 2.1.o1 android 5.1.1.. As per my study the first thing I need to do it unlock bootloader, then do TWRP, then install any custom rom. (Please correct me if m wrong). Now please tell me how can i unlock my bootloader when I dont have access to fastboot by pressing power and Volume + key. Is there some other way. I have also tried the adb version 1.4.3 to get to the fastboot mode but it restarts my mobile to lock screen.
x_master1987 said:
Hi Guys..
First i don't know if i am posting this in right thread or not... but I need help... after lots of search i couldn't find anything to unlock my oppo R7 plus running r7plusEx_11_160922 on color os 2.1.o1 android 5.1.1.. As per my study the first thing I need to do it unlock bootloader, then do TWRP, then install any custom rom. (Please correct me if m wrong). Now please tell me how can i unlock my bootloader when I dont have access to fastboot by pressing power and Volume + key. Is there some other way. I have also tried the adb version 1.4.3 to get to the fastboot mode but it restarts my mobile to lock screen.
Click to expand...
Click to collapse
Download this rom https://www.dropbox.com/s/xmh77xyinz2iero/R7plusfEX_11_OTA_012_all_201512251816.zip?dl=0. Place it in your internal drive and flash it. It will install the ColorOS with an unlockable bootloader.
Even I'm facing the same issue. There are no such methods available on internet. I have ended bricking phone several times. Because since the last update oppo had limited tho access to bootloader. And the phone OPPO r7 plus f is quite old now so there's no people dealing with the issue. The only methods remain is to downgrade the firmware and repay the process again. Better look for some firmware version around mid 2015-2016early. I read somewhere that has access to bootloader. I haven't tried it personally but I hope the methods will work. Please let me know whatever the result is..
need your help badly
ccrocks426 said:
I currently use Resurrection remix on mine however there are some issues with apps force closing is my main one. Lineage OS also had issues for me with bluetooth causing the phone the reboot over and over. CM 13 was the best but I can't find any download links for it any more (rip CM) I think they both have updates coming outside but I recommend trying some out and then making a decision. Also if your phone is on one of the latest oppo updates (one of the 2016 updates) you'll have to downgrade to a 2015 software as they locked the bootloader so you won't be able to root! It's easy to do just find an old firmware from the internet (I would post links but I can't, also has to be a 2015 one) turn off the phone and turn it back on whilst holding down the volume down button and then go install and install the old firmware and then follow any guides on the internet for installing custom ROMs
Hope this helped
Click to expand...
Click to collapse
please pm me your email . i have an oppo r7 plus f (the international version ) and i do not have much knowledge about the rooting and installing custom recovery. and since oppo has closed the bootloader now please tell me which rom to download for downgrading( if possible please provide the link) and then how to flash the custom roms and which rom is best for oppo r7 plus? which one are you using?
DooganAU said:
Rana, first I'm sure you have been a good phone user and your Oppo R7 plus is upto date, unfortunately this is a problem. So first thing you need to do (Assuming you have unbricked your phone) is find a older version of the genuine R7+ firmware. Preferably some time between 2015- mid2016. The reason for this is OPPO locked the bootloader on later versions, these earlier versions are what the autoroot tool was designed to work on. Once you have this firmware, flash through recovery (provided you still have genuine OPPO recovery), if not you also need to flash this. Once you have the older firmware on your phone you should be able to proceed as usual steps to install lineage on your phone using typical walkthroughs.
Click to expand...
Click to collapse
Where can i find the 2015 firmware for oppo r7 plus f
Just check the link in my post above.
kishd said:
Just check the link in my post above.
Click to expand...
Click to collapse
Don't know why but the link is not working
What i have: a brand new carrier unlocked samsung galaxy s7 sm-g930w8 - came with 7.0
What Id love to do: downgrade to 6.0.1 official touchwiz rom but rooted
What im reading: that the security patch is from february of 2018, which means the bootloader is too new, which means downgrading using odin wont work ( https://www.sammobile.com/forum/threads/36282-Does-Region-Matter )
... so what can i do? i bought this phone with the sole intention of downgrading, as ive seen that it is possible for that phone model (s7) in general
i hate the look of the newer OS. They took the touchwiz out of touchwiz which i loved, although mine is a rare opinion. I want the operation and exact feel of 6.0. the menus are simpler, the notifications area isnt completely stripped of features differing from total stock android. i hate having to pull down twice to see everything. I just really want that older look and feel, but all around, not just a theme.
is there anything i can do to either downgrade or fool the bootloader into letting me carry this out? is this a true limitation, or si that info i found false/old? and if I can downgrade, which build version should I use?
ive been looking here for versions
https://samsung-firmware.org/model/SM-G930W8/ but im not sure which region to go with, or if i can technically use any region
sammobile doesnt list that version anymore at all ( https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/ )
https://mobiletech360.co/samsung-galaxy-s7-sm-g930w8-stock-firmware-rom-android-6-0-1-marshmallow/ there are a number of options here but unsure of the different numbers/builds. or if since its carrier unlocked, i could pick any?
I know most will think im silly for wanting to downgrade or caring that much about appearance, but silliness aside... is this even possible??
a while ago, i purchased an s5 mini, and downgraded that with no issues at all.... but its honestly been so long and i cant for the life of me remember the steps i took or if i needed to care about region codes or other numbers. but it did sucessfully work.... it was really built unwell/cheap, but it did work.... its also slower than my captivate glide which is still my current phone, until/if i can get this s7 working the way i desire.
any help and guidance is appreciated. If it is needed, ill be using it with a Koodo mobile sim.
well it is too new if its from DRAG or so onwards (those with U2/S2 in the file name) so no dice, you're stuck with 7.0 unless you want to upgrade to oreo. (and 7.0 firmwares prior to DRAG cant be downgraded to either, not that theres much point doing that)
btw this is the wrong forum to post this in
teddytsen said:
well it is too new if its from DRAG or so onwards (those with U2/S2 in the file name) so no dice, you're stuck with 7.0 unless you want to upgrade to oreo. (and 7.0 firmwares prior to DRAG cant be downgraded to either, not that theres much point doing that)
btw this is the wrong forum to post this in
Click to expand...
Click to collapse
But this is the forum about s7? I'm wanting to modify an s7?
Which part of the file name are you referring to? Which file?
I would have thought all s7's are made at the same time, and so released with the same overall software, but it all seems so complex now. I've seen s7's running 6.0.1 stock so in my mind it seems they should all be able to...
Not sure what you're referring to with drag either? Does that stand for something?
I'm really hoping this can work somehow, its the last flagship before the edge models which was why I got it, and I love Samsung software up until 7 and 8.
My mom has an s7 as well, not rooted or anything that's too complex for her, but she did the upgrade to 8 and it's still got all the same gross appearance factors that I don't like about version 7. I got excited when her phone wanted to upgrade, maybe they had fixed some of the grossness. But, nope. Wish they had included an option even for stock based or touchwiz based appearance and menus.
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
But this is the forum about s7? I'm wanting to modify an s7?
Which part of the file name are you referring to? Which file?
I would have thought all s7's are made at the same time, and so released with the same overall software, but it all seems so complex now. I've seen s7's running 6.0.1 stock so in my mind it seems they should all be able to...
Not sure what you're referring to with drag either? Does that stand for something?
I'm really hoping this can work somehow, its the last flagship before the edge models which was why I got it, and I love Samsung software up until 7 and 8.
My mom has an s7 as well, not rooted or anything that's too complex for her, but she did the upgrade to 8 and it's still got all the same gross appearance factors that I don't like about version 7. I got excited when her phone wanted to upgrade, maybe they had fixed some of the grossness. But, nope. Wish they had included an option even for stock based or touchwiz based appearance and menus.
Click to expand...
Click to collapse
go into about phone and tell me the last 6 characters of your build number
(i was referring to the PDA file in a stock firmware zip)
(Also i meant this should be in Q&A section)
Hello,
I can understand you and also understand what you want but Samsung installed a downgrade lock in their bootloader in early 2018,
if you installed this version you can't go back to an older version, I think that was in February.
You can go back from a 6.2018 version to a 4.2018 version for example but not to a 1.2018 version!
If you have a version of for example 12.2017, you can also go back to a version of 2016, so you can also go back to Android 6.01,
if not you only have the last versions of Android 7 or update to Oreo.
I hope I could help.
teddytsen said:
go into about phone and tell me the last 6 characters of your build number
(i was referring to the PDA file in a stock firmware zip)
(Also i meant this should be in Q&A section)
Click to expand...
Click to collapse
the last of the build number and the last of the baseband version are the same. But i did take a screenshot of it when i was thinking rooting and changing would be no big thing. figured that would be easier. i purposely havent even hooked it up to wifi yet or anything, said no to anything non essential when i was setting it up... on the chance it was starting up in version 6, and i didnt want it upgrading on its own.
also why would they block downgrading? It seems if anything blocking upgrading would be the way to go, to stop people from updating their devices before official software is ready, not just samsung but any manufacturer. in my head it seems silly to even need to root anymore... someone always figures it out, and cell phone manufacturers must know it. it would be nice if it were included, sort of like developer options, where its hidden, but if you know what to look for its there, and if youre not that advanced youll never find it.
if the bootloader is in fact locked and that is the main prevention, has anyone ever successfully unlocked it before?
ETA: Ive done a bit more looking around and there is alot around about frp and making you sign in to a google account in order to reset.... i have *not* needed and havent signed into a google account on that device at all... does that mean a downgrade is still possible though odin? Or, are these 2 things in fact unrelated...
eta #2: Did a bit more searching around, and it seems to be that in order to root your device, in the process it must unlock the bootloader? If that is still the case, would i be able to then flash the marshmallow stock ROM? Thats what i was looking to do all along, sorry maybe i should have been more clear about my planned method initially. Its a bit more nerve wracking as it seems rooting itself has gotten a little more difficult with that dm verity thing... but I definitely want root no matter which version im running. Ive had root on all my devices and theres no way im going back to a locked down OS (cant remove microsoft stuff for example), i need to be able to declutter beyond what factory allows lol.
Pawprints1986 said:
the last of the build number and the last of the baseband version are the same. But i did take a screenshot of it when i was thinking rooting and changing would be no big thing. figured that would be easier. i purposely havent even hooked it up to wifi yet or anything, said no to anything non essential when i was setting it up... on the chance it was starting up in version 6, and i didnt want it upgrading on its own.
also why would they block downgrading? It seems if anything blocking upgrading would be the way to go, to stop people from updating their devices before official software is ready, not just samsung but any manufacturer. in my head it seems silly to even need to root anymore... someone always figures it out, and cell phone manufacturers must know it. it would be nice if it were included, sort of like developer options, where its hidden, but if you know what to look for its there, and if youre not that advanced youll never find it.
if the bootloader is in fact locked and that is the main prevention, has anyone ever successfully unlocked it before?
ETA: Ive done a bit more looking around and there is alot around about frp and making you sign in to a google account in order to reset.... i have *not* needed and havent signed into a google account on that device at all... does that mean a downgrade is still possible though odin? Or, are these 2 things in fact unrelated...
eta #2: Did a bit more searching around, and it seems to be that in order to root your device, in the process it must unlock the bootloader? If that is still the case, would i be able to then flash the marshmallow stock ROM? Thats what i was looking to do all along, sorry maybe i should have been more clear about my planned method initially. Its a bit more nerve wracking as it seems rooting itself has gotten a little more difficult with that dm verity thing... but I definitely want root no matter which version im running. Ive had root on all my devices and theres no way im going back to a locked down OS (cant remove microsoft stuff for example), i need to be able to declutter beyond what factory allows lol.
Click to expand...
Click to collapse
TL;DR
your bootloader is currently on version 3, and you cant downgrade to marshmallow
see that "U3BRB2"? that "U3" means your bootloader is on version 3. i assume the marshmallow firmwares use bootloaders pre-version 3 so you cant downgrade to firmwares using bootloaders with version 1 or 2. (this is how it works for F/FD models and im pretty sure samsung made it like that too for the W8 models)
eta 1) unrelated
eta 2) F/FD/W8/S/K/L variants (basically all the exynos models) have unlocked bootloaders. only SD variants have locked bootloaders so it's just your misconception
So, it's literally impossible? Has nobody ever figured out a way to downgrade or mod the bootloader itself? It seems to me the rom makers wouldn't stand for this at all and would figure out a way around it...
I can see an old bootloader can't run new software, but it seems much easier for newer bootloader to run older software, isn't it? You can buy a windows 7 pc and install Windows xp on it much easier than you could buy a windows XP PC and install Windows 7 on it... It's just boggling my mind a little
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
So, it's literally impossible? Has nobody ever figured out a way to downgrade or mod the bootloader itself? It seems to me the rom makers wouldn't stand for this at all and would figure out a way around it...
I can see an old bootloader can't run new software, but it seems much easier for newer bootloader to run older software, isn't it? You can buy a windows 7 pc and install Windows xp on it much easier than you could buy a windows XP PC and install Windows 7 on it... It's just boggling my mind a little
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Off course you can downgrade to Marshmallow. To unlock the bootloader, enable OEM unlocking in devlopper options. After flash TWRP 3.1.0 for Herolte and wipe everything from the recovery. Install any 6.0 roms on XDA for G930F then flash Magisk 17.1 to root and you're done. You can't FRP if OEM unlocking in devlopper is enabled.
AoEKiller said:
Off course you can downgrade to Marshmallow. To unlock the bootloader, enable OEM unlocking in devlopper options. After flash TWRP 3.1.0 for Herolte and wipe everything from the recovery. Install any 6.0 roms on XDA for G930F then flash Magisk 17.1 to root and you're done. You can't FRP if OEM unlocking in devlopper is enabled.
Click to expand...
Click to collapse
You'll trip knox (which breaks features like secure folder, private mode, shealth and Sbrowser private mode) and lose the comfort of OTA updates if you do this tho. Not to mention that you can encounter signal reception problems because your flashed ROM is on marshmallow and your bl/cp is on Oreo or nougat. So I wouldn't advise this method as it may break so many things.
I have an SM-A530F and had no issues flashing roms and TWRP. I eventually tried Saboor OneUI from and my phone got completely encrypted and would only allow official binaries to be flashed. I flashed Binary 7 (Pie) to my device and tried to flash TWRP but had come across the error and after researching realised I'd have to wait 7 days with the phone continuously booted up. I have waited 7 days with nothing changed. I'm now on my 25th day and still have a prenormal KG state. But in developer options my OEM states that it is already unlocked and I can switch the toggle. I cannot flash TWRP or magisk though.
The same thing happens to me and I used the chimera program and nothing works. 12 euros in the trash.
they have returned my money
almeria53 said:
The same thing happens to me and I used the chimera program and nothing works. 12 euros in the trash
Click to expand...
Click to collapse
I've tried multiple binaries and nothing. Bootloader says its unlocked and even with adb commands I get an unlocked status but the RMM/KG remains prenormal. I'm wondering if anyone can repack TWRP for jackpotlte so the device and Odin THINKS it's an official recovery binary?
Zefpoes23 said:
I've tried multiple binaries and nothing. Bootloader says its unlocked and even with adb commands I get an unlocked status but the RMM/KG remains prenormal. I'm wondering if anyone can repack TWRP for jackpotlte so the device and Odin THINKS it's an official recovery binary?
Click to expand...
Click to collapse
i see you started another thread about this, so take my previous reply in that thread with a grain of salt. I still dont think its the TWRP file thats the culprit. Try reflashing stock firmware and do the 168 hour method again.
almeria53 said:
The same thing happens to me and I used the chimera program and nothing works. 12 euros in the trash.
they have returned my money
Click to expand...
Click to collapse
youdoofus said:
i see you started another thread about this, so take my previous reply in that thread with a grain of salt. I still dont think its the TWRP file thats the culprit. Try reflashing stock firmware and do the 168 hour method again.
Click to expand...
Click to collapse
I know TWRP isn't the culprit. But because of my predicament having waited well over 168 hours without a reboot (oem unlock toggle is available but still shows KG/RMM prenormal) I'm wondering if anyone can change TWRP to make the device think its an official recovery. That way I could flash it with a prenormal state as I can flash stock recovery no problem. If the device thought TWRP was official then that way I could still root and flash zip roms with a locked KG. I hope I'm making sense?
Zefpoes23 said:
I know TWRP isn't the culprit. But because of my predicament having waited well over 168 hours without a reboot (oem unlock toggle is available but still shows KG/RMM prenormal) I'm wondering if anyone can change TWRP to make the device think its an official recovery. That way I could flash it with a prenormal state as I can flash stock recovery no problem. If the device thought TWRP was official then that way I could still root and flash zip roms with a locked KG. I hope I'm making sense?
Click to expand...
Click to collapse
youre not going to get the phone to think that TWRP is official. If that was possible, we would all have root and without so much as unlocking the bootloader for that matter
manifesto- posted on another thread-sorry for the dupe
A bit of history gives a bit more depth/ Just when you thought it was okay to go back in the water. I'm Canadian you can probably tell by my accent. My journey with phones has always been Samsung simply due to availability s6 s7 s8 s8+ most recently the a530w.
In order for you to understand my joy finding the A8 and my horror is that the S8 series. in North America S8 uses a Qualcomm Snapdragon chip. g950u is SD g950f is the rest of the world (exnyos) This is probably due to some kind of World Trade Organization antitrust treaty {although qualcom makes great chips} or whatnot I don't care.
i do care about is their bootloader lock policy (g950u and up) so it is impossible to unlock an encrypted Snapdragon bootloader. When I ran into the a530w exnyos, I was like a three-year-old at Christmas now you have to understand I'm not a coder I'm more of a mason I'm familiar with bricks. I'm sure we've all watch the AP file upload and Odin like we watch paint dry. So when I first got the a530w pi version April patch I was able to TWRP install I believe at the time was Pixel project or something else added magisk, xposed you get the idea.
Eventually a file got corrupt (much like @Zefpoes23) and I had to common sense restock it. I think my mistake what is going with the most current pie version (hadn't read this thread yet from @corsicanu) which is binary 7 knowing what I know now I would have probably had the ability to go a binary 4 or so. I haven't done the 7 day challenge simply not to waste my sanity. my bootloader unlock never vanished, it like it's a light switch with no bulb. I've tried to backdated front dated. I refuse to wait 7 days to find out that I'm still at the same place. . The problem is all the fixes are zip files which you need TWRP to flash. I agree, it's not @BlackMesa123 version. it's the prenormal. No I'm certainly not a developer and some of them are mobile gods. My questions maybe Elementary logical. Is it possible to replace a recovery image in a stock AP and Odin flash it? Repack. Also is there any way to combo a stockfirm in order to downgrade from the B7. Alter it somehow so it's thinks it's a 7 but it's actually a 4 of some sort. think we're all about to become in the same boat. we could start a movement lie "#meprenormal2" In Time will tell. As or now "prenormal" is the new "normal" All I can to the devs: help me odin 3 canmodme. your my only hope
i have no idea what youre on about for half of this post, so ill chime in with what i could decipher and know the answer to
jthibault27 said:
Is it possible to replace a recovery image in a stock AP and Odin flash it? Repack. Also is there any way to combo a stockfirm in order to downgrade from the B7. Alter it somehow so it's thinks it's a 7 but it's actually a 4 of some sort.
Click to expand...
Click to collapse
nope, sorry man. you cant go backwards in bootloader revisions. if you have B7, youre stuck with revision 7
jthibault27 said:
I refuse to wait 7 days to find out that I'm still at the same place.
Click to expand...
Click to collapse
you wont have much say in this refusal as the 168 hour thing is quite normal. Every A8 owner ive seen come into these forums has had to do the 168 hour thing.
Youdoofus said:
i have no idea what youre on about for half of this post, so ill chime in with what i could decipher and know the answer to
nope, sorry man. you cant go backwards in bootloader revisions. if you have B7, youre stuck with revision 7
you wont have much say in this refusal as the 168 hour thing is quite normal. Every A8 owner ive seen come into these forums has had to do the 168 hour thing.
Click to expand...
Click to collapse
If I'm violating XDA rules please let me know. You are obviously higher up on the rank that I am. Since my post on November 10th my findings on other threads have led me to believe that this is not just an A8 problem but an entire Samsung Fleet. A summer security patch upgraded knox guard to disable any attempts to flash TWRP. If you are lucky enough to get through that stay on it. My bootloader is like a light switch I can on and off it at anytime. 168 hours is a solution for an old problem that I don't have. I'm in permanent prenormal state with the sole ability to only flash official stock firmware and in one direction v7 or higher.. Which is what Samsung wants. i'm on V7, security patch July 1st 2019. I cannot flash anything else through Odin 13.3.1. I'm simply voicing the fact 168 hours fix is to have the ability to unlock the bootloader. I have the bootloader unlocked. My kg is tripped and I believe my fix will come in Time through a modified Odin or combo firmware emerges. i will also recluse myself from posting on this thread and open my own
---------- Post added at 19:35 ---------- Previous post was at 19:20 ----------
Youdoofus said:
i have no idea what youre on about for half of this post, so ill chime in with what i could decipher and know the answer to
nope, sorry man. you cant go backwards in bootloader revisions. if you have B7, youre stuck with revision 7
you wont have much say in this refusal as the 168 hour thing is quite normal. Every A8 owner ive seen come into these forums has had to do the 168 hour thing.
Click to expand...
Click to collapse
And to clarify what I meant as to replace the recovery file in the AP stock firmware specifically unpacking the lz4 format using 7-Zip 19 ZS v144, replacing the recovery image with the TWRP Recovery image and repacking it (the AP) and flashing it hoping the phone with think it's official. I've consulted a developer who tried it several times without any luck since he shares the same problem on a50.
jthibault27 said:
If I'm violating XDA rules please let me know. You are obviously higher up on the rank that I am. Since my post on November 10th my findings on other threads have led me to believe that this is not just an A8 problem but an entire Samsung Fleet. A summer security patch upgraded knox guard to disable any attempts to flash TWRP. If you are lucky enough to get through that stay on it. My bootloader is like a light switch I can on and off it at anytime. 168 hours is a solution for an old problem that I don't have. I'm in permanent prenormal state with the sole ability to only flash official stock firmware and in one direction v7 or higher.. Which is what Samsung wants. i'm on V7, security patch July 1st 2019. I cannot flash anything else through Odin 13.3.1. I'm simply voicing the fact 168 hours fix is to have the ability to unlock the bootloader. I have the bootloader unlocked. My kg is tripped and I believe my fix will come in Time through a modified Odin or combo firmware emerges. i will also recluse myself from posting on this thread and open my own
---------- Post added at 19:35 ---------- Previous post was at 19:20 ----------
And to clarify what I meant as to replace the recovery file in the AP stock firmware specifically unpacking the lz4 format using 7-Zip 19 ZS v144, replacing the recovery image with the TWRP Recovery image and repacking it (the AP) and flashing it hoping the phone with think it's official. I've consulted a developer who tried it several times without any luck since he shares the same problem on a50.
Click to expand...
Click to collapse
naw man, youre good. i had an A8 for about a year and now the older kiddo has it and it seems to be working well as i havent heard any complaints as of yet.
I, by no means, am an expert on this device and i admittedly have not kept current on the 168 hour fix no longer being relevant.
There is a fellow who had this forum on point about a year ago, cant recall his alias. Ill tag him if i can find him. Hopefully he has kept current on this device more than I.
@mchlbenner if you have a moment, could you lend a hand?
Youdoofus said:
naw man, youre good. i had an A8 for about a year and now the older kiddo has it and it seems to be working well as i havent heard any complaints as of yet.
I, by no means, am an expert on this device and i admittedly have not kept current on the 168 hour fix no longer being relevant.
There is a fellow who had this forum on point about a year ago, cant recall his alias. Ill tag him if i can find him. Hopefully he has kept current on this device more than I.
Click to expand...
Click to collapse
I started in this thread because I had a8 after researching through a bunch of different search engines I found this link
https://forum.xda-developers.com/galaxy-note-9/help/rmm-prenormal-oem-unlock-android-9-0-t3952959
it ended to be a note link. The moderator is convinced that it's all in our heads but people have been flocking to this thread because the title is so specific that it brings in people from different Samsung devices. It's like Field of Dreams, if you can't mod it they will come. Anyway, there are interesting comments. I apologize if my redirect or hyperlink is off. I'm no expert in this web forum platforms.
jthibault27 said:
I started in this thread because I had a8 after researching through a bunch of different search engines I found this link
https://forum.xda-developers.com/galaxy-note-9/help/rmm-prenormal-oem-unlock-android-9-0-t3952959
it ended to be a note link. The moderator is convinced that it's all in our heads but people have been flocking to this thread because the title is so specific that it brings in people from different Samsung devices. It's like Field of Dreams, if you can't mod it they will come. Anyway, there are interesting comments. I apologize if my redirect or hyperlink is off. I'm no expert in this web forum platforms.
Click to expand...
Click to collapse
This issue is true I have seen this on other a8 plus.
It part of Samsung security and no mod can fix this.
mchlbenner said:
This issue is true I have seen this on other a8 plus.
It part of Samsung security and no mod can fix this.
Click to expand...
Click to collapse
there you are!! so, the A8 is now not rootable?
Youdoofus said:
there you are!! so, the A8 is now not rootable?
Click to expand...
Click to collapse
It's very rootable provided that you don't do what 99% of the world do before selling it on Kijiji (Canadian version of Craig's list) is upgrade the latest OTA to impress the buyer. if you have an Oreo built Axxx or Sxxx (basically an Exynos chip) you are golden. not going to get into the whole North American snapdragon-Qualcomm thing. If you have a (guessing) Pre-June 2019 security patch however 9.0 I believe you can flash TWRP (all things being equal) you have a chance. however, if you have (I'm guessing most recent models) 9.0 security patch July 1 2019+ stock (previously tripped KG on a custom ROM-which say got corrupt), you are in the non-mod world. you are stuck with 9.0 official Samsung. you can't flash oreo (until someone develops a matching binary). since through my sammobile travels, I've yet to encounter a baseband/BL Oreo higher than 4. my phone (a8 9.0) is B7
jthibault27 said:
It's very rootable provided that you don't do what 99% of the world do before selling it on Kijiji (Canadian version of Craig's list) is upgrade the latest OTA to impress the buyer. if you have an Oreo built Axxx or Sxxx (basically an Exynos chip) you are golden. not going to get into the whole North American snapdragon-Qualcomm thing. If you have a (guessing) Pre-June 2019 security patch however 9.0 I believe you can flash TWRP (all things being equal) you have a chance. however, if you have (I'm guessing most recent models) 9.0 security patch July 1 2019+ stock (previously tripped KG on a custom ROM-which say got corrupt), you are in the non-mod world. you are stuck with 9.0 official Samsung. you can't flash oreo (until someone develops a matching binary). since through my sammobile travels, I've yet to encounter a baseband/BL Oreo higher than 4. my phone (a8 9.0) is B7
Click to expand...
Click to collapse
Well I'm on gsi ROMs this will never see a Samsung rom ever again.
Also slot of don't follow rooting directions I have been lock out once on Oreo never had a problem with Android 9.
mchlbenner said:
Well I'm on gsi ROMs this will never see a Samsung rom ever again.
Also slot of don't follow rooting directions I have been lock out once on Oreo never had a problem with Android 9.
Click to expand...
Click to collapse
so, between what you and the other fella are saying, the newest factory OTA prevents folks from rooting this thing now, correct? That would be a shame, locking down even the F devices? Come on Samsung!!
Youdoofus said:
so, between what you and the other fella are saying, the newest factory OTA prevents folks from rooting this thing now, correct? That would be a shame, locking down even the F devices? Come on Samsung!!
Click to expand...
Click to collapse
note: This doesn't necessarily apply to everyone since my situation was that I had a custom ROM corrupt and I restock firmware to V7 on the A8. My original custom install using TWRP had triggered kg Knox. I should have not flashed the latest stock version of 9.0. This was simply just a bridge to a new custom firmware anyway. I did not realize that I was installing a security patch that Samsung would deploy. So the question is if you go and buy the latest a, n, s 9.0 (F) can you still TWRP? Or does it say pre normal as soon as you attempt to TWRP. Rooting is not even in the realm of possibilities if you can't install TWRP. Magisk now has a feature where it modifies the AP system file which you can Odin. I thought it would pass as official. Of course, it didn't. Those dam Samsung MIT grad security engineers probably think they're better than us. LOL. All I can tell you is the toggle for the unlock Bootloader is as effective as the close door button on an elevator, you're not sure if it's connected to anything. This has been an Android War since Jelly Bean.
jthibault27 said:
note: This doesn't necessarily apply to everyone since my situation was that I had a custom ROM corrupt and I restock firmware to V7 on the A8. My original custom install using TWRP had triggered kg Knox. I should have not flashed the latest stock version of 9.0. This was simply just a bridge to a new custom firmware anyway. I did not realize that I was installing a security patch that Samsung would deploy. So the question is if you go and buy the latest a, n, s 9.0 (F) can you still TWRP? Or does it say pre normal as soon as you attempt to TWRP. Rooting is not even in the realm of possibilities if you can't install TWRP. Magisk now has a feature where it modifies the AP system file which you can Odin. I thought it would pass as official. Of course, it didn't. Those dam Samsung MIT grad security engineers probably think they're better than us. LOL. All I can tell you is the toggle for the unlock Bootloader is as effective as the close door button on an elevator, you're not sure if it's connected to anything. This has been an Android War since Jelly Bean.
Click to expand...
Click to collapse
yes, from what ive gathered from mchelbenner, the party is over. I trust his input as he is very well versed in the A8. More than I as he has had this forum on lockdown even before i got my A8 to begin with. If he said its no longer possible, thats what i will go with also
Youdoofus said:
yes, from what I've gathered from mchelbenner, the party is over. I trust his input as he is very well versed in the A8. More than I as he has had this forum on lockdown even before I got my A8 to begin with. If he said its no longer possible, thats what i will go with also
Click to expand...
Click to collapse
If you ever come across a forum specific to this issue ({completely extrapolating the date by guess} July 1, 2019 9.0) but not necessarily specific to the A8, please share. as it stands now, my findings indicate isolated conversations in different forums on various models, sharing the same problem. We must unite! lol. truth be told, it's challenging searching for such a specific problem relating to a patch on many models.
Hi I have a samsung SM-970u ( s10e snapdragon TMO) is there a way to make a downgrade form android 11 to android 10 ?
I...wondered the exact same thing....
but even with an unlocked bootloader it doesn't seem possible if your bootloader version is too high...it was possible when Android 11 first came out but versions may have changed now. I tried flashing with odin myself but I'm getting sw rev check fail... even with an unlocked bootoader.
I'd love to be wrong cause I want stock android 10 but i can't find info otherwise.
Deathlan said:
Hi I have a samsung SM-970u ( s10e snapdragon TMO) is there a way to make a downgrade form android 11 to android 10 ?
Click to expand...
Click to collapse
What's your current Build/Baseband?
I was wondering if I can downgrade from 12 to 9.
But as I'm reading a lot of posts, I'm guessing it will be next to impossible?
Build: SPA1.210812.016.G970FXXUEGVA4
Baseband: G970FXXUEGVA2
Cilvaring said:
I was wondering if I can downgrade from 12 to 9.
But as I'm reading a lot of posts, I'm guessing it will be next to impossible?
Build: SPA1.210812.016.G970FXXUEGVA4
Baseband: G970FXXUEGVA2
Click to expand...
Click to collapse
You can never officially downgrade more than one version.
The only possibility would be to unlock the phone's bootloader and flash a custom ROM based on Android 9. But I do not even know if it is theoretically possible to run an Android 9 ROM on an Android 12 bootloader
iBowToAndroid said:
You can never officially downgrade more than one version.
The only possibility would be to unlock the phone's bootloader and flash a custom ROM based on Android 9. But I do not even know if it is theoretically possible to run an Android 9 ROM on an Android 12 bootloader
Click to expand...
Click to collapse
From what I've learned the phone has a version of the bootloader.
In my case that's version 14 (resp. E because it's hexadecimal)
I found that f.e. Android 11 was released in versions that had different bootloader versions (9, A, B, C, D & E).
So I was only able to install the Android 11 that came with bootloader version E.
And as it stands now, it seems like it's impossible to downgrade the bootloader which in the end makes it a huge pile of s**t on Samsung's or even Google's end.
It's kinda the Apple way of doing things and not letting you do what you wish...
Cilvaring said:
It's kinda the Apple way of doing things and not letting you do what you wish...
Click to expand...
Click to collapse
Kind of. Except:
1. Apple doesn't let you downgrade firmware at all
2. Apple doesn't offer unlockable bootloaders and therefore there's no possibility of a custom ROM
Cilvaring said:
From what I've learned the phone has a version of the bootloader.
In my case that's version 14 (resp. E because it's hexadecimal)
I found that f.e. Android 11 was released in versions that had different bootloader versions (9, A, B, C, D & E).
So I was only able to install the Android 11 that came with bootloader version E.
And as it stands now, it seems like it's impossible to downgrade the bootloader which in the end makes it a huge pile of s**t on Samsung's or even Google's end.
It's kinda the Apple way of doing things and not letting you do what you wish...
Click to expand...
Click to collapse
It's a cruel lesson. Android becomes more Apple than Android with each upgrade.
Literally the first thing I do on a new Samsung is package block OTA updates.
I have two N10+'s, one running on 9, the other 10.
They will stay on that firmware.
iBowToAndroid said:
Kind of. Except:
1. Apple doesn't let you downgrade firmware at all
2. Apple doesn't offer unlockable bootloaders and therefore there's no possibility of a custom ROM
Click to expand...
Click to collapse
Well yes, but the fact that google's core apps are not open source and more and more APIs or libraries are only available on phones that have certain pre-installed google apps takes a big piece of liberty out of android.
My bet also is, it won't get better since google just won't stop generating money in new ways day after day.
But: Android still is a whole lot better than the half-eaten piece of fruit. No doubt.
blackhawk said:
It's a cruel lesson. Android becomes more Apple than Android with each upgrade.
Literally the first thing I do on a new Samsung is package block OTA updates.
I have two N10+'s, one running on 9, the other 10.
They will stay on that firmware.
Click to expand...
Click to collapse
I hear you.
Was running a S7 with Oreo before I switched to the S10e now and it will stay on Oreo until it dies as a backup phone.
Sadly the seller of the S10e already had updated it to 12, so I'm stuck with at least 11 due to the bootloader.
Cilvaring said:
I hear you.
Was running a S7 with Oreo before I switched to the S10e now and it will stay on Oreo until it dies as a backup phone.
Sadly the seller of the S10e already had updated it to 12, so I'm stuck with at least 11 due to the bootloader.
Click to expand...
Click to collapse
Android 11 was one reason I bought a new N10+ about 5 months ago versus a N20U. I thought new N10+ be running on 9 but it ended up loaded with 10 due to the manufacturing date. It turned out ok.
I learned the hard way with Samsung and upgrades 6 years ago... and was about as happy as you.
Unfortunately many of the resellers will load whatever is the latest OS version when they test out a phone.
It's more than just a little aggravating. Forget the Google bs hype... I still remember the horror of MS Vista
Hopefully you'll find workarounds to iron out the rough edges or if it really gets on your last nerve return or resell it. Life's too short to live with a phone you hate.
Hey guys all good?
I got my hands on an A53 already on Android 13 (U.I 5.1), then I unlocked the bootloader, rooted, magisk working but then I decided to downgrade from 13 to 12 because of a few things
I tried via Odin (13.14.4 and 13.12.7) and both didn't work the first odin it fails the flashing and the second pass but it didn't flash the whole thing just reset the phone
any idea? or I'm now stuck with Android 13?
Cheers
From what I can find, Odin supposedly won't allow a downgrade if the boot loader version is lower.
That's just what people seem to say about Samsung devices and downgrading. I've never tried it and never will. Would immediately use multiple OS versions however if Android actually supported dual booting. Its fantastically messed up that it doesn't.
Not sure if TWRP will. Didn't look that one up. You didn't bring that one up but it might be a way to do it.
sandsofmyst said:
From what I can find, Odin supposedly won't allow a downgrade if the boot loader version is lower.
That's just what people seem to say about Samsung devices and downgrading. I've never tried it and never will. Would immediately use multiple OS versions however if Android actually supported dual booting. Its fantastically messed up that it doesn't.
Not sure if TWRP will. Didn't look that one up. You didn't bring that one up but it might be a way to do it.
Click to expand...
Click to collapse
Thanks for the reply. I was thinking something about that too. Not that the bootloader is lower but that it was modified (root) i guess
Unfortunately TWRP is not compatible yet with Android 13 UI 5.1 at least accordingly to this topic
So i guess I'm stuck for now
biustech said:
Thanks for the reply. I was thinking something about that too. Not that the bootloader is lower but that it was modified (root) i guess
Unfortunately TWRP is not compatible yet with Android 13 UI 5.1 at least accordingly to this topic
So i guess I'm stuck for now
Click to expand...
Click to collapse
You could flash a GSI image, but I guess that wouldn't be OneUI anymore
Hello you all hope you're having a good day, so no way to downgrade a53 5g from Android 13 to android 12 ??? I found some firmwares for Android 12 but the binary number is 4 and Android 13 is actually on binary number 5 , no way to do the downgrade with Odin?
I read somewhere that is not possible to flash a firmware with different binary number is it true ?? I would like to comeback to android 12 it's better