I had used ccswe to disable software updates and keep my US t-mobile note 10+ on android 10, but my niece was messing with my phone and I have no idea what she did except that she triggered the update (handed the phone back to me with the blue update running screen already at 46%).
Is there any way to downgrade? I'm familiar with Odin and flashing firmware, or was a couple years ago anyway. But I've been searching the forums here (is it just me or did the search get less useful?) and can't find a link to download the firmware to downgrade.
Um no since usually the kernel changes in Samsung phones from a10 to a11
If you try to flash an older kernel your phone will brick.
You must see if the kernel has been changed. If not then it is possible. If it is, I'm not sure if you can downgrade.
Related
There has been a firmware upgrade waiting to be installed since 12/12 on my international version 7100. Coincidentally, or not, that's when I entered the phone's country of origin again, so the upgrade may have been available for much longer.
Has anyone successfully installed it without breaking anything, and could tell me what version of Android it is? I am currently on 4.4.2, guess it's too much to hope for 5, so it's likely just 4.4.4?
Usually, I don't think twice about firware upgrades, and just dl and install, but my Note II is paired with a Gear S, and I am a bit worried the upgrade may break connectivity or functionality.
Some time ago I loaded a firmware onto my VZW S8+ (G955U) which I thought was a legitimate firmware. However, I've never been able to update the phone since. The firmware that I loaded was CRE1 and since loading that, no OTA updates have occurred and even trying to use the VZW update tool, I get an error saying no update for that firmware or something to that effect.
I assume that I would need to flash back to a base version 8 firmware and then see how things go from there but I haven't been able to locate a base v8 firmware - assuming that is the direction I need to go.
Can anyone advise? The phone is not rooted. I did see one other similar thread with CRE1 firmware from 2018 - I can try downloading the closest firmware to CRE9 that I can find, which is CRK9, and see if I can get it to load.
Other suggestions/ideas are welcome!
[UPDATE]
So I essentially followed another post here and using Odin 3.13.1 I loaded CRK1, the oldest I could find that was near CRE1, and the phone came back up and pretty much immediately notified of an OTA update. About 12 or so OTA updates later and I'm at the current OTA release.
I'm having the same issue. I bought a VZW S8+ (G955U) from eBay Seller mistyelectronics that was supposed to be new in box. It has never updated since I received it almost a year ago. It stuck on Software Version G955USQS5DSE5. Any insight or advice to go the same route? I used Odin years ago. Where would I look for the files to load to the phone?
I appreciate any help you can give.
My phone is Chinese variant running miui 11 Android 9 and i installed the anti brick from the mega thread. Now i have an Android 10 update and i downloaded the update for 3 times but Everytime it says update.zip is corrupted during update process. I also tried with choose update package to update manually but same results. How can i overcome this problem?
This thread?
Not sure, since it's pretty long ago that i used to flash custom recovery's and roms, but if you have TWRP as your recovery i don think you're able to flash official firmware. Also read something in that thread about Android 10 and Anti Brick not going along very well. My best guess is; get rid of TWRP and Anti Brick by flashing the correct official firmware for your device via Fastboot.
Try and find a very very VERY clear howto. Lots of reading and caution = not bricking your device.
Hi guys, I just bought a brand new note 10+ N975W (canada version). I'm on stock firmware. It keep asking me to update. Shall I update? which version is best to keep the battery last as long as possible?
Also, can i downgrade to previous versions or stock if i dont like the upgraded firmware?
Yes update. It's probably just security updates at this point, so there would be no reason to go back. The Note 10 firmware is fairly mature by now.
chances are if you bought it recently it is already an updated firmware unless the store is running really old stock, as they tend to produce the devices with the latest firmware at the time of manufacture. basically you would need to find a phone that was manufactured before any updates to get the original stock firmware.
chances are any phone produced this year likely has Android 10 pre installed instead of Android 9 and a much more recent security patch, so in that case you may as well update the phone as it is already updated to an extent.
as for downgrading to an actual launch firmware it's not possible as every so often they make a change that can't be reversed so it stops you going to an older firmware (I know it happend with both Android 10 and the One UI update, there are likely more points)
but in terms of battery use, everyone's numbers will differ no matter the firmware as a lot of it comes down to settings, what its used for and the environment it is ran in.
Belimawr said:
chances are if you bought it recently it is already an updated firmware unless the store is running really old stock, as they tend to produce the devices with the latest firmware at the time of manufacture. basically you would need to find a phone that was manufactured before any updates to get the original stock firmware.
chances are any phone produced this year likely has Android 10 pre installed instead of Android 9 and a much more recent security patch, so in that case you may as well update the phone as it is already updated to an extent.
as for downgrading to an actual launch firmware it's not possible as every so often they make a change that can't be reversed so it stops you going to an older firmware (I know it happend with both Android 10 and the One UI update, there are likely more points)
but in terms of battery use, everyone's numbers will differ no matter the firmware as a lot of it comes down to settings, what its used for and the environment it is ran in.
Click to expand...
Click to collapse
my phone is still running on android 9.0.
aznboix said:
my phone is still running on android 9.0.
Click to expand...
Click to collapse
Since the phone is new. Before getting to far into configuration, run the update, then do a factory reset. It'll do a fresh install of Android 10 and any security updates.
That will give you a nice clean install you can then setup.
Sent from my SM-N976V using Tapatalk
You should always update. They are mostly Security Updates, these are for security reasons (Hence the name ). Yeah there are some system modifications and enhancements too but the main reason is to ensure the device is as secure as possible
Is there a custom firmware that works perfectly?
can i root my device?
can i flash to another firmware? Asia firmware for exemple
what are the apps that i can't miss on note 10+?
which firmware that has vietnamese language?
thanks
Hi,
First off I'm pretty new to the Forum so I'm just starting to understand some of the existing threads posted here.
My TMO OnePlus 9 Pro was updated to Android 12 back in March and since that time I've been having several issues the primary of which is that Microsoft Intune is no longer able to validate the configuration of my device. This has locked me out of company apps on my phone for the past several months and it's a real pain.
I looked into the issue and from what I can see it seems to be a bug in oxygen OS 12 relating to Android work profile. I have heard that this bug was fixed in later versions of oxygen OS but unfortunately T-Mobile have not made any new version available since March.
I tried converting my device to T-Mobile EU using the MSM tool and, while I was initially successful I wasn't able to get the T-Mobile modem to work on Android 12. I sent reverted back to T-Mobile US using that MSM.
The way I see it I have two options.
1. Wait and/or work with T-Mobile support to get a newer Oxygen OS build pushed to my device.
2. Figure out a way to fix the modem issues I was facing after upgrading to A12 following the EU MSM conversion.
Is there a fix available for the T-Mobile modem in Android 12? Sorry if it's been answered already but I couldn't find details anywhere despite searching. I'm looking for a no-root solution since that defeats the purpose of doing this to get Intune working.
SmartMart92 said:
Hi,
First off I'm pretty new to the Forum so I'm just starting to understand some of the existing threads posted here.
My TMO OnePlus 9 Pro was updated to Android 12 back in March and since that time I've been having several issues the primary of which is that Microsoft Intune is no longer able to validate the configuration of my device. This has locked me out of company apps on my phone for the past several months and it's a real pain.
I looked into the issue and from what I can see it seems to be a bug in oxygen OS 12 relating to Android work profile. I have heard that this bug was fixed in later versions of oxygen OS but unfortunately T-Mobile have not made any new version available since March.
I tried converting my device to T-Mobile EU using the MSM tool and, while I was initially successful I wasn't able to get the T-Mobile modem to work on Android 12. I sent reverted back to T-Mobile US using that MSM.
The way I see it I have two options.
1. Wait and/or work with T-Mobile support to get a newer Oxygen OS build pushed to my device.
2. Figure out a way to fix the modem issues I was facing after upgrading to A12 following the EU MSM conversion.
Is there a fix available for the T-Mobile modem in Android 12? Sorry if it's been answered already but I couldn't find details anywhere despite searching. I'm looking for a no-root solution since that defeats the purpose of doing this to get Intune working.
Click to expand...
Click to collapse
My TMo OP9P LE2127 had updated to OOS12 before I had a chance to root it. I hadn't read enough about it to worry about trying to block the update. Well, I hated OOS12 and I eventually downgraded back to Stock OOS11 and then converted it EU with the MSM tool. Currently running a rooted OOS11.2.10.10 on both slots.
Not once did I have to touch the modem and my 5G works just fine. Everything worked out of the box (aka conversion MSM). My phone is even still SIM locked. I believe others have experienced the same thing with a LE2127 that updated to the stock TMo OOS12 firmware. The modem seems to stick after that upgrade, even after downgrading it back to OOS11.
I've blocked my phone from manually checking for updates and I'm perfectly happy with my phone for the time being. That said, I have not tried updating my phone to any EU versions of OOS12 (C.48 being the latest, I think?).
So, that's my experience, but your mileage may vary.
SmartMart92 said:
Hi,
First off I'm pretty new to the Forum so I'm just starting to understand some of the existing threads posted here.
My TMO OnePlus 9 Pro was updated to Android 12 back in March and since that time I've been having several issues the primary of which is that Microsoft Intune is no longer able to validate the configuration of my device. This has locked me out of company apps on my phone for the past several months and it's a real pain.
I looked into the issue and from what I can see it seems to be a bug in oxygen OS 12 relating to Android work profile. I have heard that this bug was fixed in later versions of oxygen OS but unfortunately T-Mobile have not made any new version available since March.
I tried converting my device to T-Mobile EU using the MSM tool and, while I was initially successful I wasn't able to get the T-Mobile modem to work on Android 12. I sent reverted back to T-Mobile US using that MSM.
The way I see it I have two options.
1. Wait and/or work with T-Mobile support to get a newer Oxygen OS build pushed to my device.
2. Figure out a way to fix the modem issues I was facing after upgrading to A12 following the EU MSM conversion.
Is there a fix available for the T-Mobile modem in Android 12? Sorry if it's been answered already but I couldn't find details anywhere despite searching. I'm looking for a no-root solution since that defeats the purpose of doing this to get Intune working.
Click to expand...
Click to collapse
In order to get the modem working in A12, you have to have root and flash a Magisk module that fixes your build.prop. Unfortunately, your need to be unrooted prevents that from happening.
If you're OK with rooting temporarily, you could modify your build.prop to have "ro.vendor.oplus.radio.multisim.config=ssss" after flashing EU, then unroot afterwards by flashing stock boot.img.
razercortex said:
In order to get the modem working in A12, you have to have root and flash a Magisk module that fixes your build.prop. Unfortunately, your need to be unrooted prevents that from happening.
If you're OK with rooting temporarily, you could modify your build.prop to have "ro.vendor.oplus.radio.multisim.config=ssss" after flashing EU, then unroot afterwards by flashing stock boot.img.
Click to expand...
Click to collapse
Yeah, that could work. Does build.prop need to be updated after each OTA update?
SmartMart92 said:
Yeah, that could work. Does build.prop need to be updated after each OTA update?
Click to expand...
Click to collapse
Shouldn't need to be updated.
Also, you could try unlocking bootloader, rooting, modifying build.prop, unrooting, then relocking bootloader if you're ok with testing. It may/may not work. If it works, then you don't need to modify ever again, at least until a future update touches that file.
If I have no sims detected am I able to flash something to regain sim detection and data?