Related
guys, can anyone knows how to revert to android 4.4.2 android 5.0.1 with? updated firmware bass headphones disappeared, this problem occurs not only at me. who are important sound in the headphones do not advise upgraded. ASUS disappointed by this update.
ME572C Lollipop 5.0.1? Where? Please share it with us. You can downgrade with MOFD_SDUPDATE.zip and recovery.
BerndHhn said:
ME572C Lollipop 5.0.1? Where? Please share it with us. You can downgrade with MOFD_SDUPDATE.zip and recovery.
Click to expand...
Click to collapse
I tried to downgrade the firmware. but in the new android 5.0.1 bootloader and recovery, and this does not take recovery firmware based on Android 4.4.2. And here is the update on the official website for ME572C, but only TW version, WW firmware not yet available. http://www.asus.com/ru/supportonly/ASUS MeMO Pad (ME572C)/HelpDesk_Download/
Yeah
I installed this night.
Sound is fine.
Tested on Audio Out and Bluetooth, but unfortunately no root possibility yet.
It broke my auto screen rotation. Although this isn't Asus fault it's a bug in lollipop. Also been reported on nexus and moto.
However I don't like the new look and don't like the new notification system or the way quick settings now require two swipes. Quick should mean quick.
Also noticed more lag in starting apps.
Want to revert back to 4.4.2 too
Frisian said:
It broke my auto screen rotation. Although this isn't Asus fault it's a bug in lollipop. Also been reported on nexus and moto.
However I don't like the new look and don't like the new notification system or the way quick settings now require two swipes. Quick should mean quick.
Also noticed more lag in starting apps.
Want to revert back to 4.4.2 too
Click to expand...
Click to collapse
downgrade do not advise to do, I wanted to do this service firmware (which use service centers to flash, free access to this firmware is not), but killed the tablet, it will not turn on and hung on the splash screen Intel Inside. I repeat: who is not updated to 5.0.1 do not advise to do it, a lot of bugs in the new firmware.
Armada17 said:
downgrade do not advise to do, I wanted to do this service firmware (which use service centers to flash, free access to this firmware is not), but killed the tablet, it will not turn on and hung on the splash screen Intel Inside. I repeat: who is not updated to 5.0.1 do not advise to do it, a lot of bugs in the new firmware.
Click to expand...
Click to collapse
Thats awful for you. Can't you get into any recovery anymore? Perhaps flash the 5.0.1. again?
I'm not going to try to downgrade but I wish I hadn't installed lollipop. I really like this tablet and everything worked perfectly. Now I have to rotate the screen manually. I cheked the sensors with a diagnostic tool and they are working fine. It's the software. It isn't known what triggers the bug so it could happen at any time or never. Nice work google.
Hopefully we'll have root and custom mods in the near future.
Armada17 said:
downgrade do not advise to do, I wanted to do this service firmware (which use service centers to flash, free access to this firmware is not), but killed the tablet, it will not turn on and hung on the splash screen Intel Inside. I repeat: who is not updated to 5.0.1 do not advise to do it, a lot of bugs in the new firmware.
Click to expand...
Click to collapse
If you can boot back into the download screen, you can probably reflash the newest firmware.
pWEN said:
If you can boot back into the download screen, you can probably reflash the newest firmware.
Click to expand...
Click to collapse
does not work, bootloader killed, dependent on Intel Inside logo.
Hi, i try at the moment downgrade from the me581cl. It looks good. You can look at my thread Root with downgrade for the intel developer tool.
The highest importent file is the ifwi.bin.
You can it flash with fastboot flash dnx .....
Has anyone found a way to do this? I foolishly manually upgraded my ME572CL (JP SKU) with the WW 5.0.1 firmware. Seemed OK at first but now noticing a lot of bugs which are making it quite unpleasant to use. Lollipop firmware didn't seem to add anything much to the experience anyway, so I would really like to downgrade back to 4.4.2 but MOFD_SDUPDATE fails.
kanagawaben said:
Has anyone found a way to do this? I foolishly manually upgraded my ME572CL (JP SKU) to the WW 5.0.1 firmware. Seemed OK at first but now noticing a lot of bugs which are making it quite unpleasant to use. Lollipop firmware didn't seem to add anything much to the experience anyway, so I would really like to downgrade back to 4.4.2 but MOFD_SDUPDATE fails.
Click to expand...
Click to collapse
I got ME572C(JP sku) and tried almost same things. Android 5.0.1(WW) seems stable on my environment but root is required for my usage. Downgrading with MOFD_SDUPDATE method also failed and now watching TWRP/CWM forums in order to get revised intel atom platform supports for 5.01....
gmaxjp said:
I got ME572C(JP sku) and tried almost same things. Android 5.0.1(WW) seems stable on my environment but root is required for my usage. Downgrading with MOFD_SDUPDATE method also failed and now watching TWRP/CWM forums in order to get revised intel atom platform supports for 5.01....
Click to expand...
Click to collapse
I did a factory reset and the WW 5.0.1 seems stable again now. Would still like to return to a rooted 4.4.2 if possible though.
Any progress on downgrading or rooting ME572C on lollipop? I do have droidboot.img available took out from 4.4 if that might help.
Myuboku said:
Any progress on downgrading or rooting ME572C on lollipop? I do have droidboot.img available took out from 4.4 if that might help.
Click to expand...
Click to collapse
Thanks for interest that. But it seems that we have no ways to revert 5.0x upgrade to 4.4x with method such as reflash partition or something like that because of fastboot oem stuffs to unlock bootloader are completely changed.
The only thing I succeed was reflashing the same version of OTA image WW_V12.14.1.12 downloaded from ASUS site (stupidly I cleared partitions before I confirmed if oem unlock is still valid or not....so I tried this to unblrick my one..). I tried flash partitions with images extracted from older ROM and fastboot server said "Not able to downgrade to KK" or something like that.
Perhaps fastboot server checks version of current vs to be flashed and reject if the version of the software is OLDER THAN CURRENT. This perhaps shows we can inject some hacks into current image, but I have still no progress regarding this idea because I was newbie to IA architecture hacking....I'm guessing that reversing fastboot.img contents shows the way to next milestone....
gmaxjp said:
Thanks for interest that. But it seems that we have no ways to revert 5.0x upgrade to 4.4x with method such as reflash partition or something like that because of fastboot oem stuffs to unlock bootloader are completely changed.
The only thing I succeed was reflashing the same version of OTA image WW_V12.14.1.12 downloaded from ASUS site (stupidly I cleared partitions before I confirmed if oem unlock is still valid or not....so I tried this to unblrick my one..). I tried flash partitions with images extracted from older ROM and fastboot server said "Not able to downgrade to KK" or something like that.
Perhaps fastboot server checks version of current vs to be flashed and reject if the version of the software is OLDER THAN CURRENT. This perhaps shows we can inject some hacks into current image, but I have still no progress regarding this idea because I was newbie to IA architecture hacking....I'm guessing that reversing fastboot.img contents shows the way to next milestone....
Click to expand...
Click to collapse
On one russian forum there is already a person who was able to downgrade to 4.4. Although, he flashed something from "CL" version, instead of "C" so the tablet was unusable, thats why he brought it to Asus service, they did a normal downgrade for him, but it took almost a month.
Myuboku said:
On one russian forum there is already a person who was able to downgrade to 4.4. Although, he flashed something from "CL" version, instead of "C" so the tablet was unusable, thats why he brought it to Asus service, they did a normal downgrade for him, but it took almost a month.
Click to expand...
Click to collapse
Beside the changed bootloader & recovery i believe it is not possible because of the changed partition assignment on LP5.0.1. KK isnt compatible with that anymore i guess and as far as i can see the partition assignment is not renewed and rewritten within any of the prelollipop firmwares again.
tycoo said:
Beside the changed bootloader & recovery i believe it is not possible because of the changed partition assignment on LP5.0.1. KK isnt compatible with that anymore i guess and as far as i can see the partition assignment is not renewed and rewritten within any of the prelollipop firmwares again.
Click to expand...
Click to collapse
Thus, Asus service has .raw service firmware, and they can downgrade to kitkat
Myuboku said:
Thus, Asus service has .raw service firmware, and they can downgrade to kitkat
Click to expand...
Click to collapse
Ya, that might be true.
tycoo said:
Ya, that might be true.
Click to expand...
Click to collapse
Also as i know, there is a person who has service firmwares. As he explained, when flashing service lollipop firmware, it somehow unlocks bootloader(i can be mistaken at this part), and makes it possible to install any android firmware.
Hi,
about 2 years ago I rooted my S2 Galaxy Tab (T719) and now I would like to upgrade from Android 6.0.1 to Android version to 7 or 8. I have googled for instructions on how to upgrade a rooted S2 Tab but did not find anything useful (most info is on OTA upgrades which no longer works on rooted devices). Could someone please post step-by-step instructions (please bear in mind that I only ever deal with this kind of thing once every 2-3 years so I do not have much experience). I have TWRP v 3.0.2 installed (do I need to update this as well?) and the tablet is not encrypted (so hopefully I won't have to wipe the system partition and re-install all the app?!?). Thanks.
I also noticed that there is now a huge variety of ROMs out there. How can one know which ones are trustworthy? The main reason I rooted the tablet was to be able to increase privacy (control app permissions with XPrivacy). So I do not want to install some custom ROM that maybe contains spyware or other compromising features. Any advice on this would be greatly appreciated. Given my motivation (privacy) for rooting, would it maybe be better to go back to Stock ROMs (i.e. non rooted) and simply control web access via netguard (by preventing net access for some apps, they may still spy on my contacts, location, or email but cannot phone home to transmit the information)? At least I would still get OTA updates because being excluded from the OTA channel also poses a security risk in itself I suppose. Ok so any advice would be appreciated.
Thank you in advance!
There is no official Android 8 for our device. If you want 8 or 9 you have to install a custom ROM like LuK1337's LineageOS port. It is as safe as LineageOS is by itself on any device. Only problem you might have then is that calling is not possible anymore for now, but LTE works. If you want to use LOS, you HAVE to format data because it's not compatible at all. If you wanna stay on official Android you might keep it. Installing is done by flashing the official firmware with the correct country code over Odin. This will remove TWRP at first so you have to reflash it by Odin afterwards. For firmware download I always use: https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 and Odin is found by google. If you wanna got the way to LOS you have to do all the steps I mentioned before too anyways to have a recent Modem firmware and bootloader. In that case you just have to flash LOS and OpenGAPPS by TWRP and delete /data aka Factory reset.
Regardless what you do, after ODIN is done, you HAVE TO boot into TWRP immediately to keep it from being removed by official firmware. While you are in there anyways you can install magisk to keep it from encrypting /data
Many thanks emuandco. So I guess I will stick with the Android 7 as I do not want to reformat the tablet and reinstall all the apps. I have started to download the Android 7 stock ROM, but it is taking quite long so in the meantime just to confirm, the steps to follow are:
1- use odin to flash the stock ROM (no steps required prior to this? I simply overwrite the existing ROM? I suppose that I will loose root then and need to re-root the device using the standard procedure as explained here: http://www.samsungsfour.com/tutoria...nougat-7-0-using-cf-auto-root-all-models.html ?)
2- use odin to flash TWRP (I will need the newest version I guess and cannot use the same as for Android 6?)
3- boot into recovery mode to ensure that TWRP does not get overwritten
4- done
Is this correct? Do I then need to reinstall Xposed, SuperSU and Xprivacy or will they be preserved?
Thanks again!
P.S.: BTW, I also found these instructions: https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627 which are slightly different from http://www.samsungsfour.com/tutoria...nougat-7-0-using-cf-auto-root-all-models.html and require a wipe of the data partition. Does this mean that for an update to Android 7 I definitely do need to wipe the data partition? If this is the case then this would be a major disadvantage of rooting in the first place and maybe I simply flash the stock ROM and do not root at all but go the "netguard" route as mentioned in my original message?
I never used the official Firmware that much. Fist thing I did was going on LuK1337's nerves to get a port of LOS for it up and running So no clue if Samsung manages to keep /data but I guess so. Yeah, looks fine what you list there. You COMPLETELY overwrite ANY modification in kernel or /system, so reflash your mods and root (Magisk). I always recommend to uase the MOST recent TWRP. (https://dl.twrp.me/gts28velte/ should be it in your case).
Ah and looking at your manuals... Check OEM unlock just to be rather safe than sorry if things go mad.
emuandco said:
I never used the official Firmware that much. Fist thing I did was going on LuK1337's nerves to get a port of LOS for it up and running So no clue if Samsung manages to keep /data but I guess so. Yeah, looks fine what you list there. You COMPLETELY overwrite ANY modification in kernel or /system, so reflash your mods and root (Magisk). I always recommend to uase the MOST recent TWRP. (https://dl.twrp.me/gts28velte/ should be it in your case).
Ah and looking at your manuals... Check OEM unlock just to be rather safe than sorry if things go mad.
Click to expand...
Click to collapse
Deleted
Hi everyone,
I had updated my Galaxy Note 9 with March 2020 update and I am one among many poor souls who are suffering from display discoloration, horizontal lines during low brightness and over heating.
- I have tried all possible methods as suggested by Samsung team in their US community page, tried factory reset multiple times, nothing worked. Took screenshots of the screen and shared it to other to check if the problem is with display, but the screenshots were just fine, no colour distortion or verticle lines. So i am of the opinion that, its basically software glitch in March update.
So, I have some following specific queries. I tried looking for these queries in the forum but did not find any, so, have collated all my queries below:
- My current Bootloader version is 5. Is there any process by which i can downgrade my Bootloader from 5 to 4? I would like to go back to January update.
- If I root my phone and install custom rom (latest version of Linage OS. You guys can suggest a good OS, if you have tried one), will the display problem be solved?
- After installing custom rom as mentioned above, can I go back and install stock firmware with Bootloader version 4?
As you can see, I am just trying to find a solution to come out of display problem. Any other suggestions or any tried and tested solutions are welcome.
Thanks everyone in advance
#note9displayproblems, #note9marchupdate
Nagharjun said:
Hi everyone,
I had updated my Galaxy Note 9 with March 2020 update and I am one among many poor souls who are suffering from display discoloration, horizontal lines during low brightness and over heating.
- I have tried all possible methods as suggested by Samsung team in their US community page, tried factory reset multiple times, nothing worked. Took screenshots of the screen and shared it to other to check if the problem is with display, but the screenshots were just fine, no colour distortion or verticle lines. So i am of the opinion that, its basically software glitch in March update.
So, I have some following specific queries. I tried looking for these queries in the forum but did not find any, so, have collated all my queries below:
- My current Bootloader version is 5. Is there any process by which i can downgrade my Bootloader from 5 to 4? I would like to go back to January update.
- If I root my phone and install custom rom (latest version of Linage OS. You guys can suggest a good OS, if you have tried one), will the display problem be solved?
- After installing custom rom as mentioned above, can I go back and install stock firmware with Bootloader version 4?
As you can see, I am just trying to find a solution to come out of display problem. Any other suggestions or any tried and tested solutions are welcome.
Thanks everyone in advance
#note9displayproblems, #note9marchupdate
Click to expand...
Click to collapse
From what i've read, 5 to 4 is impossible.
Rosli59564 said:
From what i've read, 5 to 4 is impossible.
Click to expand...
Click to collapse
There should be some or the other way around for this. May be some developer should help us out here.
Nagharjun said:
Hi everyone,
I had updated my Galaxy Note 9 with March 2020 update and I am one among many poor souls who are suffering from display discoloration, horizontal lines during low brightness and over heating.
- I have tried all possible methods as suggested by Samsung team in their US community page, tried factory reset multiple times, nothing worked. Took screenshots of the screen and shared it to other to check if the problem is with display, but the screenshots were just fine, no colour distortion or verticle lines. So i am of the opinion that, its basically software glitch in March update.
So, I have some following specific queries. I tried looking for these queries in the forum but did not find any, so, have collated all my queries below:
- My current Bootloader version is 5. Is there any process by which i can downgrade my Bootloader from 5 to 4? I would like to go back to January update.
- If I root my phone and install custom rom (latest version of Linage OS. You guys can suggest a good OS, if you have tried one), will the display problem be solved?
- After installing custom rom as mentioned above, can I go back and install stock firmware with Bootloader version 4?
As you can see, I am just trying to find a solution to come out of display problem. Any other suggestions or any tried and tested solutions are welcome.
Thanks everyone in advance
#note9displayproblems, #note9marchupdate
Click to expand...
Click to collapse
I am facing same issue ...display distortion from 20% to 80% ..after that display looks fine.
I tried to downgrade to pie ..still no success...it has same issue...
I also believe that its software issue or some connection issue
Sue samsung for trying to force user to change screen. Samsung's screen is so expensive. Apple was fined for throttling the iphones.
I have same issue on my N9600... :'(
What is causing the distortion? Sofware bug? Can shot a picture showing the issue?
Jlozde said:
What is causing the distortion? Sofware bug? Can shot a picture showing the issue?
Click to expand...
Click to collapse
Ita all over the internet. Just Google Samsung galaxy note 9 display discoloration.
I don't know if this will solve your problem but you would be able to flash a Android 9 ROM on a Android 10 bootloader. If you're like me you hate Android 10. What you do is you flash Android 9 bootloader made for twrp flash the Android 9 rom of your choice. Than flash the Android 10 bootloader that you want via Odin, than fastly reflash twrp for Android 10
For me it works but I kind of jerry-rigged it to work. I regret every day updating to Android 10 but since I'm able to still run Android 9 on an Android 10 bootloader, I'm okay with that.
Hope this kind of help you.
Nagharjun said:
Hi everyone,
I had updated my Galaxy Note 9 with March 2020 update and I am one among many poor souls who are suffering from display discoloration, horizontal lines during low brightness and over heating.
- I have tried all possible methods as suggested by Samsung team in their US community page, tried factory reset multiple times, nothing worked. Took screenshots of the screen and shared it to other to check if the problem is with display, but the screenshots were just fine, no colour distortion or verticle lines. So i am of the opinion that, its basically software glitch in March update.
So, I have some following specific queries. I tried looking for these queries in the forum but did not find any, so, have collated all my queries below:
- My current Bootloader version is 5. Is there any process by which i can downgrade my Bootloader from 5 to 4? I would like to go back to January update.
- If I root my phone and install custom rom (latest version of Linage OS. You guys can suggest a good OS, if you have tried one), will the display problem be solved?
- After installing custom rom as mentioned above, can I go back and install stock firmware with Bootloader version 4?
As you can see, I am just trying to find a solution to come out of display problem. Any other suggestions or any tried and tested solutions are welcome.
Thanks everyone in advance
#note9displayproblems, #note9marchupdate
Click to expand...
Click to collapse
Hi Bro, the same problem here. We have created a group to discuss about the issue. Plz join there and will discuss about this.
https://t.me/samsungDisplayProblem
We have a temporary fix for this but also trying for permanent fix which can solve our issue.
---------- Post added at 01:42 PM ---------- Previous post was at 01:39 PM ----------
sagarabhiwant said:
I am facing same issue ...display distortion from 20% to 80% ..after that display looks fine.
I tried to downgrade to pie ..still no success...it has same issue...
I also believe that its software issue or some connection issue
Click to expand...
Click to collapse
Hi Bro, we are also facing the same issue so we have created a Telegram group to discuss about this and gathering all with this problem. Plz join there.
https://t.me/samsungDisplayProblem
We have two to three temporary fixes but we also trying for permanent fix.
this.guy.lol said:
I don't know if this will solve your problem but you would be able to flash a Android 9 ROM on a Android 10 bootloader. If you're like me you hate Android 10. What you do is you flash Android 9 bootloader made for twrp flash the Android 9 rom of your choice. Than flash the Android 10 bootloader that you want via Odin, than fastly reflash twrp for Android 10
For me it works but I kind of jerry-rigged it to work. I regret every day updating to Android 10 but since I'm able to still run Android 9 on an Android 10 bootloader, I'm okay with that.
Hope this kind of help you.
Click to expand...
Click to collapse
hi i have the same problem and i want downgrade to andoid 9 from 10
can you explain how to do it
thanks
majedabbas said:
hi i have the same problem and i want downgrade to andoid 9 from 10
can you explain how to do it
thanks
Click to expand...
Click to collapse
only way is to trip knox by rooting and then flashing an android 9 rom. as you know once it has been tripped you will instantly lose access to samsung pay, secure folders etc. however on the plus side you have the choice of root or non root.
Hi guys,
Me and my mum are experiencing a similar situation.... I'm trying to downgrade my galaxy Note8 boot-loader, everything was working till I press the button to upgrade. Now I cant use any memory card all i see is 'the Sandisk card is not supported' and for my mum's Note 9 when she activates the biometric sensor the phone restarts each 15 - 30 mins. I always bought Samsung but now I'm considering to don't do it anymore...
How do you install android pie over android 10 BL
this.guy.lol said:
I don't know if this will solve your problem but you would be able to flash a Android 9 ROM on a Android 10 bootloader. If you're like me you hate Android 10. What you do is you flash Android 9 bootloader made for twrp flash the Android 9 rom of your choice. Than flash the Android 10 bootloader that you want via Odin, than fastly reflash twrp for Android 10
For me it works but I kind of jerry-rigged it to work. I regret every day updating to Android 10 but since I'm able to still run Android 9 on an Android 10 bootloader, I'm okay with that.
Hope this kind of help you.
Click to expand...
Click to collapse
can you please tell how to install android pie over android 10 BL?
only way is to trip knox root and then flash/ if you dont want to trip knox its not possible
A|ex said:
only way is to trip knox root and then flash/ if you dont want to trip knox its not possible
Click to expand...
Click to collapse
Hi, ok so assuming we don't care about tripping knox, rooting and flash.. still, how would this be done?
I'm on a SM-N9600 atm, with latest Android 10, rooted and TWRP installed. Where do I find a custom Android 9 Rom (compatible with my model) that I can flash via TWRP?
Thanks in advance
Stefo2332 said:
Hi, ok so assuming we don't care about tripping knox, rooting and flash.. still, how would this be done?
I'm on a SM-N9600 atm, with latest Android 10, rooted and TWRP installed. Where do I find a custom Android 9 Rom (compatible with my model) that I can flash via TWRP?
Thanks in advance
Click to expand...
Click to collapse
All you do is just flash the android 9 rom. Downgrading the bootloader makes no difference if you have already unlocked it. The whole point of it is for people who are on later bootloaders and still have knox and want to go to android 9 which is not possible without the trip.
A|ex said:
All you do is just flash the android 9 rom. Downgrading the bootloader makes no difference if you have already unlocked it. The whole point of it is for people who are on later bootloaders and still have knox and want to go to android 9 which is not possible without the trip.
Click to expand...
Click to collapse
Hi @A|ex , thanks for your answer. I still don't know where I can find a custom Android 9 rom, compatible with Note 9 snapdragon (SM-N9600) that I could flash via TWRP... (Assuming it's impossible to flash stock Android 9 via Odin even if my phone is currently already rooted on latest Android 10 (bootloader == 5).
Here on XDA there are some ROMs for the Exynos model but nothing except the 'WETA' rom for Snapdragon model, which is not a full rom anyway from what I understand.
If you could shed some light on this it would be much appreciated: where can I find a custom Android 9 rom, flashable via TWRP, compatible with a rooted SM-N9600 (currently on latest Android 10, with a BL==5, unlocked)?
Thanks again for any help!!
Hi All,
I urgently need some help to downgrade Samsung Galaxy Note 9 phone Model No: SM-N960F/DS from currently running OS Android 10 to Android (Oreo) 8.1 or 8.0.
Following are the current versions running:
Software version: SAOMC_SM-N960F_OXM_XSA_QQ_0016
Knox Version: Knox 3.4.1, Knox API Level: 30, TIMA: 4.10.
I have downloaded the XSA version of Android 8.1 from Sammobile, followed all the instructions by running Odin3 V3.14.4, gone into the Download mode of the phone. The phone connects to Odin as I can see on Odin status of Blue Colour Com connection established, Odin then displays "Recovery", unfortunately the phone gets stuck at this status showing "Recovery". I have let the phone run for hours or even a full day but the status never changes from "Recovery"
Could anyone please assist me to complete the downgrade. Am I missing any step here?
Thanking you in advance
I don't think downgrade to oreo is possible. Pie is possible if baseband version's 5th character from the back is 4.
Rosli59564 said:
I don't think downgrade to oreo is possible. Pie is possible if baseband version's 5th character from the back is 4.
Click to expand...
Click to collapse
Thank you for the prompt reply. I just check the digit, its 6 not 4. What are my options here?
None. Your options are only firmwares with the number 6, which date to April/May, last OneUI 2.0 firmwares.
I did read that one can flash custom roms that are older, if one leaves Bootloader untouched to v6, but that is something i wouldn't encourage to do.
PlutoDelic said:
None. Your options are only firmwares with the number 6, which date to April/May, last OneUI 2.0 firmwares.
I did read that one can flash custom roms that are older, if one leaves Bootloader untouched to v6, but that is something i wouldn't encourage to do.
Click to expand...
Click to collapse
Thank you PlutoD, I am happy to read about it as well, if you want to post the link or let me know where to find the info.
CrazynWild said:
Thank you PlutoD, I am happy to read about it as well, if you want to post the link or let me know where to find the info.
Click to expand...
Click to collapse
I have no links except the Development board here, my input came as something that i've seen discussed somewhere in there.
As you can see, there are some Oreo Custom ROMs, i'm not sure if they are actively maintained (if one can say anything active about that), but if you are determined to do what you want, i would start by choosing the ROM first, put a question there or the last resort, contact the developer.
I'll be very blunt with you, i see no reason for people to revert to older roms, but i dont want to get in to that argument, but having a v6 Bootloader (and maybe Modem too) with a v1/v2 system firmware is something that could give you unpredictable issues nobody could help you with.
Could boot a pie custom rom with android10 bootloader. Not sure about oreo though
I didnt spot the message about losing GearVR and now having upgraded my GearVR is not functional. It says I cannot go back but... this is XDA so, can i ??
Also not sure if I can re-install the Oculus GearVR app (can't see it on PlayStore) so does anyone know which APKs I need to install as well?
on my s10+ i get se same Issue. According official samsung information, it seems that gear VR do not run on android 12. I did not find any solution for now.
Methanoid said:
I didnt spot the message about losing GearVR and now having upgraded my GearVR is not functional. It says I cannot go back but... this is XDA so, can i ??
Also not sure if I can re-install the Oculus GearVR app (can't see it on PlayStore) so does anyone know which APKs I need to install as well?
Click to expand...
Click to collapse
Sorry don't know anything about gearVR, but no, if the bootloader version has increased, which I believe it does when going to A12, then you can't downgrade.
I'm pretty sure there is no xda 'work'a'round' for that, haven't seen one and everything I've read indicates not possible. Do some searching I guess to be positive, but one prereq to bootloader unlock is being on a specific BL version, and even their directions indicate if you're above that version, nothing you can do.
cheers
Thanks for replying... I guess I am boned
I successfuly reverted to Android 11 G975XXSEFUJ2 from Android 12 since I saw issue about GearVR...IF you are on first release of A12 you can downgrade.
Flash all A11 stock firmware package and choose CSC instead Home_csc !
tin2404 said:
I successfuly reverted to Android 11 G975XXSEFUJ2 from Android 12 since I saw issue about GearVR...IF you are on first release of A12 you can downgrade.
Flash all A11 stock firmware package and choose CSC instead Home_csc !
Click to expand...
Click to collapse
You have the S10+, from what I see, the most recent BL version is 6 on both a11 and the new a12, so that fits the requirements.
It looks like for at least some of the S10 firmware upgrades, the BL version changes, thus u cannot go back if that's the case. Not all A12 updates are out for the S10, so we don't know yet if the BL version will change for them.
Yes.I think they left compatible downgradable bootloader for those users who didn't saw info about GearVR support as a last chance to revert.
I presume,as we learned from previous updates, in future releases of A12 downgrade will not be possible because of their privacy paranoia.
AsItLies said:
You have the S10+, from what I see, the most recent BL version is 6 on both a11 and the new a12, so that fits the requirements.
It looks like for at least some of the S10 firmware upgrades, the BL version changes, thus u cannot go back if that's the case. Not all A12 updates are out for the S10, so we don't know yet if the BL version will change for them.
Click to expand...
Click to collapse
I have the S10 and from what I can tell the BL version is also 6 on my A12 update.
Does this mean I can just use odin to load a "compatible downgradable bootloader" and I will be able to downgrade back to 11? Does my phone have to be unlocked to do this?
Assuming I back up all my data, will I be able to go back to 11 without compromising my xfinity number, security, ect.? I am simply looking for the best way to just revert back to 11 and reload everything I was using before.
Johnm77 said:
I have the S10 and from what I can tell the BL version is also 6 on my A12 update.
Does this mean I can just use odin to load a "compatible downgradable bootloader" and I will be able to downgrade back to 11? Does my phone have to be unlocked to do this?
Assuming I back up all my data, will I be able to go back to 11 without compromising my xfinity number, security, ect.? I am simply looking for the best way to just revert back to 11 and reload everything I was using before.
Click to expand...
Click to collapse
Well as far as I know you can, but that's from what I've read, not from doing the exact scenario you speak of. Sometimes we just have to try it to know for sure. I have read for sure the if the BL isn't the same version, you can't go back. And no, the phone does not have to be unlocked.
good luck
AsItLies said:
Well as far as I know you can, but that's from what I've read, not from doing the exact scenario you speak of. Sometimes we just have to try it to know for sure. I have read for sure the if the BL isn't the same version, you can't go back. And no, the phone does not have to be unlocked.
good luck
Click to expand...
Click to collapse
Thank you for your help!
I figured the most recent update of A11 from
Galaxy Firmware - Samsung Galaxy S10 SM-G973U (CHA) | G973USQU6GUJ3
This Firmware flash for Samsung Galaxy S10 with the Phone Model Number SM-G973U for region 🇺🇸 United States with CSC code CHA and R(Android 11) OS.
galaxyfirmware.com
is what I would need.
The Baseband I have from A12 currently is G973USQU6HULD, so from what was said here the BL ver. 6 means I should be able to do it.
Model #, Country, region/carrier from the above link all match my specs. So if I'm to understand correctly all I should have to do is backup and then use the firmware with odin to flash to my device using tin2404's procedure from above? (Flash all A11 stock firmware package and choose CSC instead of Home_csc !)
tin2404 said:
I successfuly reverted to Android 11 G975XXSEFUJ2 from Android 12 since I saw issue about GearVR...IF you are on first release of A12 you can downgrade.
Flash all A11 stock firmware package and choose CSC instead Home_csc !
Click to expand...
Click to collapse
Doesn't choosing CSC clear all the app data and basically factory reset it? Wouldn't I want to use Home_CSC, or does it not then work properly?
Johnm77 said:
Doesn't choosing CSC clear all the app data and basically factory reset it? Wouldn't I want to use Home_CSC, or does it not then work properly?
Click to expand...
Click to collapse
Update:
Successfully used odin to revert to os11, had to factory reset after odin completed, then I just reloaded my backup.
After more research I decided to block all future updates using ADB and this method:
No more headaches with my software!
Actually, it is neccessery to choose clear CSC to erase leftovers..Choosing Home_CSC brings various of errors possible.
Workaround is doing TWRP backup on SD Card then after clear flashing restoring ONLY data partition.