Database Info

Gear S2 Fimware Update

Hey guys,
here's the link to the first firmware update for the SM-R732:
fota-s3-dn.ospserver.net/firmware/DBT/SM-R732/f9cd6fdcda8e4a56b99ea23436c3224b.bin
MD5: C4A14900315D87CE9CBC86B12ECCEB3E
Size: 5,500,427 bytes
Stock firmware version: R732XXU2AOIL
This version: R732XXU2AOJ3
Content:
delta.boot
delta.csc
delta.module
delta.ramdisk2
delta.recovery
delta.rootfs
delta.ua
sboot.bin
update.cfg

Not sure how to access firmware. My S2 can't connect to Nexus 5 since Marshmallow update on Monday. Although, is this only for Samsung Galaxy phones, or all?

Changelog?
Sent from my SM-G925P using Tapatalk

SKFU said:
Hey guys,
here's the link to the first firmware update for the SM-R732:
fota-s3-dn.opserver.*et/firmware/DBT/SM-R732/f9cd6fdcda8e4a56b99ea23436c3224b.bin?px-hash=&px-wid=WP20151014-CC-62666281&px-wctime=2015-10-14%2013:44:40.0&px-unum=%20HTTP/1.1\r\n
Make sure to replace the timestamps etc to get a valid download.
MD5: C4A14900315D87CE9CBC86B12ECCEB3E
Size: 5,500,427 bytes
Stock firmware version: R732XXU2AOIL
This version: R732XXU2AOJ3
Content:
delta.boot
delta.csc
delta.module
delta.ramdisk2
delta.recovery
delta.rootfs
delta.ua
sboot.bin
update.cfg
Click to expand...
Click to collapse
This is not a working URL...

I've tried changing the time stamps but nothing seems to work. Can someone upload to another host? or shed light on what to do with the time stamps?

I don't see any info regarding an update anywhere on the web. You would think someone would write about it.

Hey,
I'll try to reverse the update process over the next days, it seems it requires more than just valid timestamp to receive the valid download.
This update is an OTA update and does not contain the full system image. Mounting the rootfs fails, I think it's more likely an incremental patch file or similar.
Nevertheless, you can easily sniff it yourself. Just make sure you use an on-device sniffer because Samsung uses a technique to bypass proxies.
Once set-up, start the Gear Manager on your phone and search for an update for your watch.
Furthermore I requested the open-source parts of the Gear S2 at Samsung. They made available the files for the last firmware here:
opensource.samsung.com - search for SM-R720
Best regards,
- S

Ok guys, the link is now working, it was just a typo, my fail
fota-s3-dn.ospserver.net/firmware/DBT/SM-R732/f9cd6fdcda8e4a56b99ea23436c3224b.bin
Anyway, still going to check how it finds the firmware files...

Once we have the downloaded file, how do we push it to the watch?
SKFU said:
Ok guys, the link is now working, it was just a typo, my fail
fota-s3-dn.ospserver.net/firmware/DBT/SM-R732/f9cd6fdcda8e4a56b99ea23436c3224b.bin
Anyway, still going to check how it finds the firmware files...
Click to expand...
Click to collapse

It's more likely for research. Normally you simply update via the Gear Manager. Nevertheless it should be possible to upload the file via Odin as well.
There is a new version of it called NetOdin especially for non USB devices like this.
ripv2 said:
Once we have the downloaded file, how do we push it to the watch?
Click to expand...
Click to collapse

SKFU said:
It's more likely for research. Normally you simply update via the Gear Manager. Nevertheless it should be possible to upload the file via Odin as well.
There is a new version of it called NetOdin especially for non USB devices like this.
Click to expand...
Click to collapse
Have you a link to NetOdin? I can't see it anywhere

Here you go: bbs.52samsung.com/thread-737324-1-1.html
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ash99 said:
Have you a link to NetOdin? I can't see it anywhere
Click to expand...
Click to collapse

is this firmware update worth side loading? I don't think people on "Non Supported" devices will be able to get the update normally, so this might be the only option.
SKFU said:
Here you go: bbs.52samsung.com/thread-737324-1-1.html
Click to expand...
Click to collapse

I agree, I did not notice any major changes after the update.
As said, this is for research purpose in my view. The update *should* only be applied via the official Samsung Gear app. This update file is for the Classic Bluetooth EU version btw.
Anyway, since the files seem to be patches and not a full OS, we might not go too far with this. Mounting does not work for me, so rooting can not be applied to it, yet
If someone finds the full firmware somehow (maybe call Samsung and pretend a brick?), let us know
ripv2 said:
is this firmware update worth side loading? I don't think people on "Non Supported" devices will be able to get the update normally, so this might be the only option.
Click to expand...
Click to collapse

Interesting, someone succsessfully testet this update? I am quite interessted in this Version because of my US Version of my S2 classic. Can I overwrite es US setting for the metric system and my anguage s-voice?
I can't really deal with that fahrenheit degree.

Does this update fix the notification issues? The issues I see is when the watch doesn't show the always on screen it will not vibrate when notifications come in.

I just got the update on my s2 sport and have not really noticed any differences. It said performance so maybe the battery life will be a little better than what it already is! I'll keep playing with it to see if there are any changes I'm missing.

Got the update last night and so far, no real changes. There is susposed to be an update in November to enable Samsung Pay. Can't see that this update has that.

I can confirm that I have repeatedly been able reconnect my S2 to my Nexus 5 on Marshmallow after I installed the S2 firmware update that was available in the USA in the Gear app under the About Gear settings. I went from firmware version R720XXU2AOIL to R720XXU2AOJ3. I found that even after installing the firmware, I had to do one Light Reset on the S2 before the S2 would reconnect.
So far so good. Have intentionally gone out of range 6 times and reconnected all 6 times. Will report back if situation changes.

There is a firmware update available for the watch from the gear manager. My update was 5.30MB in size and says it has bug fixes.

[ROM][925Z][5.0.2]Root/Busybox/Debloat/Deodex/Zip-Align Stock Softbank Rom (Japan)

Based off of the lastest Softbank firmware, 404SCSCU1BOH3_404SCSBM1BOH3_404SCSCU1BOH3. I used SuperR's Kitchen to root, add busybox, deodex, zip-align, and debloat in accordance with the list below. This is my first ROM ever, and I have a rather busy job, so please don't expect much support. But if you find a problem, post it here because I will want to know too!
So far, the only problem I have had is Touchwiz launcher force closing, but I use Nova anyway. I attempted to incorporate the Alliance Framework, but it just bootloops and I didn't know enough to try to fix it.
Rom Download v1.0
Stock Firmware in case you need it.
Installation:
Install Zerolte TWRP Custom Recovery available here. I use the twrp-2.8.6.0-zeroltezt.img.tar. 2.8.7.0 didn't work for me. Flash this with the AP block in ODIN with the phone in download mode.
Wipe System, Cache, Dalvik Cache, and I also recommend wiping Data. This will factory reset your phone. You will have to reenter account info, reinstall apps, etc.
Install the zip and reboot. The phone will hang at the Galaxy screen for a few minutes. Don't be alarmed unless something else happens.
Known Issues:
No contact editor installed.
Changelog:
01-Jan-2016: Moved 1.0 links to Android File Host
Debloat List:
system/app/AccessControl*
system/app/AdvSoundDetector2015*
system/app/AllShareCastPlayer*
system/app/AllshareFileShare*
system/app/AllshareFileShareClient*
system/app/AllshareFileShareServer*
system/app/AllshareMediaShare*
system/app/AntHalService*
system/app/ANTPlusPlugins*
system/app/ANTPlusTest*
system/app/ANTRadioService*
system/app/AssistantMenu2_ZERO*
system/app/BadgeProvider*
system/app/BasicDreams*
system/app/BBCAgent*
system/app/BeaconManager_20*
system/app/BluetoothTest*
system/app/Books*
system/app/Bridge*
system/app/CarmodeStub*
system/app/CatchFavorites_L*
system/app/Chrome*
system/app/ChromecastFrameworkService*
system/app/ChromeCustomizations*
system/app/ClockPackage_L*
system/app/ColorBlind_L*
system/app/DigitalClockEasy_L*
system/app/DigitalClock_L*
system/app/Drive*
system/app/DRParser*
system/app/DualClockDigital_L*
system/app/EasymodeContactsWidget*
system/app/EdmSimPinService*
system/app/EdmVpnServices*
system/app/ELMAgent*
system/app/EmergencyLauncher*
system/app/EmergencyModeService*
system/app/Facebook_stub*
system/app/FactoryCamera_FB*
system/app/FBAppManager*
system/app/FBInstagram_stub*
system/app/FBMessenger_stub*
system/app/FidoUafClient*
system/app/FlipboardBriefing*
system/app/GalaxyAppsWidget_Phone*
system/app/GearManagerStub*
system/app/Gmail2*
system/app/Hangouts*
system/app/imsservice*
system/app/ImsSettings*
system/app/ImsTelephonyService*
system/app/JpnDioDict4*
system/app/KeyguardWallpaperUpdator*
system/app/KnoxAttestationAgent*
system/app/KnoxSetupWizardClient*
system/app/K_Widget_WeatherNews2015*
system/app/Maps*
system/app/MirrorLink*
system/app/MobileFeliCaClient*
system/app/MobileFeliCaMenuApp*
system/app/MobileFeliCaSettingApp*
system/app/MobileFeliCaWebPluginBoot*
system/app/MobilePrintSvc_Samsung*
system/app/MobileTrackerEngineTwo*
system/app/MultiWindowTrayService2*
system/app/MYDManager_ver78*
system/app/NfcFeliCaSettings*
system/app/NfcFn*
system/app/OneDrive_Samsung*
system/app/OneNote_Compact_Samsung*
system/app/PageBuddyNotiSvc2*
system/app/PartnerBookmarksProvider*
system/app/Personalization*
system/app/PhotoTable*
system/app/PlayGames*
system/app/PlusOne*
system/app/Preconfig*
system/app/PreloadInstaller*
system/app/QuickConnect_20*
system/app/RCPComponents*
system/app/RemoteLock*
system/app/RemotePlayer*
system/app/ringtoneBR*
system/app/RootPA*
system/app/Sagiwall*
system/app/SamsungContentsAgent*
system/app/SamsungTTS*
system/app/SBrowser_3.0.38*
system/app/SCONE_Android_ProxyService_Lib*
system/app/SecCalculator2_L*
system/app/SecDict2Zero*
system/app/SecFactoryPhoneTest*
system/app/SecMemo2*
system/app/SecSetupWizard2015*
system/app/SecurityLogAgent*
system/app/smartsecurity_mcafee*
system/app/SnsImageCache*
system/app/SoftBank_AppPass_StubApp*
system/app/SPlannerWidget_Material*
system/app/SPlanner_Material*
system/app/SplitSoundService*
system/app/SPrintSpooler*
system/app/STalkback*
system/app/Stk*
system/app/TuiService*
system/app/UniversalMDMClient*
system/app/USBSettings*
system/app/VideoEditor_Zero*
system/app/Videos*
system/app/WeatherDaemon2015*
system/app/WfdBroker*
system/app/withTV*
system/app/WlanTest*
system/app/Wluc*
system/app/YahooLiveWeather*
system/app/YouTube*
system/priv-app/AutomationTest_FB*
system/priv-app/AutoPreconfig*
system/priv-app/BackupRestoreConfirmation*
system/priv-app/CocktailBarService*
system/priv-app/ContextProvider*
system/priv-app/DeviceKeystring*
system/priv-app/DeviceTest*
system/priv-app/DiagMonAgent*
system/priv-app/DirectShareManager*
system/priv-app/DisasterMessageBoard*
system/priv-app/DSMLawmo*
system/priv-app/EasyLauncher2_Zero*
system/priv-app/FBInstaller*
system/priv-app/FeliCaLock*
system/priv-app/FidoUafAsm*
system/priv-app/FingerprintService2*
system/priv-app/FmmDM*
system/priv-app/FmmDS*
system/priv-app/FsDtvApp*
system/priv-app/GalaxyApps_3xh_zero*
system/priv-app/GoogleFeedback*
system/priv-app/HancomOfficeViewer*
system/priv-app/HealthService*
system/priv-app/Hearingdro_V4*
system/priv-app/Hs20Settings*
system/priv-app/HwModuleTest*
system/priv-app/IchinaviClient*
system/priv-app/ImsLogger+*
system/priv-app/intelligenceservice*
system/priv-app/Kies*
system/priv-app/KLMSAgent*
system/priv-app/MyPlaces*
system/priv-app/ParentalControls*
system/priv-app/PCWClientS18*
system/priv-app/PeopleStripe*
system/priv-app/PhoneErrService*
system/priv-app/ProxyHandler*
system/priv-app/S-Voice_Android_phone*
system/priv-app/SamsungBilling*
system/priv-app/SamsungMagnifier2*
system/priv-app/sCloudBackupAppZero*
system/priv-app/sCloudDataRelay*
system/priv-app/sCloudDataSyncZero*
system/priv-app/sCloudSyncCalendar*
system/priv-app/sCloudSyncContacts*
system/priv-app/sCloudSyncSBrowser*
system/priv-app/sCloudSyncSNote3*
system/priv-app/SecContacts_L*
system/priv-app/SecEmailComposer*
system/priv-app/SecEmailProvider*
system/priv-app/SecEmailSync*
system/priv-app/SecEmailUI*
system/priv-app/SecEmailWidget*
system/priv-app/SecEmbeddedServerService*
system/priv-app/SecLiveWallpapersPicker*
system/priv-app/SecMyFiles2015*
system/priv-app/SendHelpMessage*
system/priv-app/serviceModeApp_FB*
system/priv-app/ServiceModeApp_RIL*
system/priv-app/SFinder_L*
system/priv-app/SHealth4*
system/priv-app/SmartRemoteStub_zero*
system/priv-app/SmartSwitchAgent*
system/priv-app/SMCore*
system/priv-app/SMusic*
system/priv-app/SNS_v2*
system/priv-app/SOAgent*
system/priv-app/softbankmail*
system/priv-app/SPDClient*
system/priv-app/SPPPushClient_Prod*
system/priv-app/SVF*
system/priv-app/SyncmlDM*
system/priv-app/Tag*
system/priv-app/VirtualTourViewer_WQHD_lightTheme*
system/priv-app/VoiceNote4Z_32*
system/priv-app/VoiceWakeUp*
system/priv-app/VRSetupWizardStub*
system/priv-app/WhatsAppDownloader*
system/priv-app/wssyncmlnps2*
Application Manager Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Special thanks to:
@SuperR for making the kitchen. This is the only tool I have used that worked with the Softbank version! Thank you!

Amazing! Perfect. thankyouu.
Ive been using this rom for a day or two now.
it seems very very light weight and fast.
Im very satisfied, no errors that I can find yet.
Infinitely better than the default Samsung bloat Lollipop.

I seem to have deleted whatever app allows you to edit contacts. For now, install something like Contact Editor Free.

Can u link me a thread or key word that help u deodex your Rom?
I cant find anyway to deodex my rom cause it 64bit and deodex tool cant deodex both 64bit and 32bit at the same time even deodex seperate then combine those 2.
Tks

Has anyone rooted after the softbank update to 6.0.1 marshmellow yet?
Sent from my 404sc aka softbank galaxy s6 edge

I just found out it was released today. I haven't been able to upgrade yet, though.
For some reason nothing happens when I hit the upgrade now button (maybe because Im not in Japan right now)
Edit: I got into Marshmallow, but I haven't been able to flash a new recovery reliably. All i get when I try to go into recovery is an "Installing system update..." that fails and then boots into android.
Edit2: I found a firmware file. Going to start testing out 6.0.1 roms
EDIT 3: Try the zeroltezt cf-auto-root for a working root. Available: here

Anyone rooted there softbank s6 edge 925Z now that 7.0 Nougat is out?

[GUIDE] How to install Internal Android 10 Build for Nokia 9 PureView

If you want to repost this internal OTA to other websites (other than XDA itself), please ask me for permission, thanks.
Click to expand...
Click to collapse
Alright.
AOP-513D-0-00WW-B03 (V5.13D_B03) here is same to the official release. So if you have installed this build, just enjoy it.
You will get later updates like regular Nokia 9 Devices.
To those who are still running 5xxx builds older than 513D B03, please download packages here.
Click to expand...
Click to collapse
To users who have installed this internal build, please share your experience report here if you're willing to, thanks.
Now I think Android 10 for Nokia 9 is stable enough and will be released to public soon, so I think it's time to post it here.
If HMD will push Android 10 officially, you can install it under ADB sideload easily and link will be posted here.
Internal build version: AOP-513B-0-00WW-B01
It will be updated from: AOP-427F-0-00WW-B01, which is released October 2019 Security Update.
Let me tell you how to verify:
1. Dial *#*#227#*#* to check current Version. If older than AOP-427F-0-00WW-B01, update to 427F before proceed.
FYI, 427F is October 2019 Security Update.
Alternately, you can use command "fastboot oem getversions" under fastboot mode / Download mode to check current firmware version.
2. Install AOP-513A-0-00WW-B01-427F-0-00WW-B01-update.zip with adb sideload under recovery.
3. Reboot to normal OS and recovery again - it's not over yet.
4. Install AOP-513B-0-00WW-B01-513A-0-00WW-B01-update.zip with adb sideload under recovery.
5. Reboot your phone.
That's it.
If Android 10 official update pushed publicly, link will be updated here.
To root the phone, you may want to use Magisk 20 released October 12th, 2019 or newer. I've uploaded stock boot image here if you have unlocked bootloader. There's no "Flashing is not rooted for fused device" issue under 5xxx build.
You can check overall experiences here (prototype, though): https://www.youtube.com/watch?v=v6ScYgISGFg
Download link:
To prevent throttle error, I didn't upload them to Google Drive or other cloud storages. Sorry for inconvenience.
https://www.androidfilehost.com/?w=files&flid=300249

Just installed on my Nokia 9 TA-1087, works perfectly. No bugs found so far. So far so good. Animations really smooth, camera launch is significantly faster than Android 9. The dark mode is not fully dark but that was expected. Overall excellent experience. Definitely worth the update.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Any tutorial for hpw to do that? And if something goes wrong how to flash stock pie again? Thnx

Ok done. Flashed... All working very well without bugs.
Battery life seems better on 10. There is no night mode on camera i hope add it to next updates...

can we use it in TA-1087?

Mod edit - Translated by Google Translate:
427F full package download address please provide trouble, thanks
*********************
427F全量包下载地址麻烦提供下，感谢啦

and the most serious.. do. we need to unlock bootloader?
Sent from my Nokia 9 using Tapatalk

ktlk21 said:
and the most serious.. do. we need to unlock bootloader?
Sent from my Nokia 9 using Tapatalk
Click to expand...
Click to collapse
No need to unlock bootloader or root

and when we want to go back to stable channel? what happens?
Sent from my Nokia 9 using Tapatalk

Google pay works but can't add new cards as it says it's been rooted or altered in some way. I know it's not rooted but will we not get the proper update now as a result of doing this?

I installed the internal build 10 update on my TA-1082 (US) last night (about 20 hours ago) and it's been working/behaving extremely stable.
Feels noticeably faster than 9.
Thanks to OP for making it available:good:

Hi there! Is the device certified or not after installing this software version? I'm thinking, if not, maybe the mobile banking apps won't work on it

I installed it a while ago and it seems pretty stable and fast, the face recognition doesn't work as well tho. Also its a shame when you switch the dark theme on it doesn't make the boot dark as well, like the pixels. Everything else is working great! Thanks for sharing the build :good:
PS: I didn't have to root or anything, I just downloaded the two builds and updated using the stock recovery via adb sideload, it works on a non rooted fully stock phone, which is awesome

Any idea if there is possibility to revert back to stock ROM? I found only nb0 firmwares that seems is not able to flash to Nokia 9 with Nokia flash took.
Thanks.

Thank you! I am on it now...
---------- Post added at 05:31 PM ---------- Previous post was at 05:27 PM ----------
How can I flash it into the recovery? If I boot on the recovery via adb I have "No Command" menu... what should I flash before?
Thanks!!!

sev7en said:
How can I flash it into the recovery? If I boot on the recovery via adb I have "No Command" menu...
Thanks!!!
Click to expand...
Click to collapse
Check out steps in this article-
https://www.techmesto.com/recovery-and-download-mode-in-nokia/

graphreak said:
Check out steps in this article-
https://www.techmesto.com/recovery-and-download-mode-in-nokia/
Click to expand...
Click to collapse
Thank you, I guess my model is not compatible as when I sideload I get that error:
"Package is for product AOP_sprout but expeced fih_sdm845"
I have the single sim edition available from UAE.
There is any OTA for that?
Cheers,

sev7en said:
Thank you, I guess my model is not compatible as when I sideload I get that error:
"Package is for product AOP_sprout but expeced fih_sdm845"
I have the single sim edition available from UAE.
There is any OTA for that?
Cheers,
Click to expand...
Click to collapse
Not aware of any OTA available for UAE model.
It is the Nokia 9 Pureview? What's the Model Number?
Mine is a single SIM too but, for US/North America with Model number TA-1082.

graphreak said:
Not aware of any OTA available for UAE model.
It is the Nokia 9 Pureview? What's the Model Number?
Mine is a single SIM too but, for US/North America with Model number TA-1082.
Click to expand...
Click to collapse
Hello,
my model is TA-1082, single sim. I purchased it in Dubai... but when I flash for the OTA upgrade, it shows the message as above. Why?
EDIT: My build number is: 00WW_4_27D_SP02

Feedback of issues I have gotten so far:
- Phone freezes when playing videos.
- Network connectivity drops to nothing randomly.
- Google Pay doesn't work without internet.
Feedback on improvements:
- Phone faster and more responsive.
- Better battery life after a week.
Is anyone having these issues or is it just me, and also how do we return to stock rom in case something goes bad? I haven't unlocked the bootloader or rooted the phone so I'm unaware on how to do this just in case.

Realme Q UI 1.0 update

Hello
I got android 10 ui 1.0 update
Do you advice me to download it or not?
is it better than color os 6?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

hsm90 said:
Hello
I got android 10 ui 1.0 update
Do you advice me to download it or not?
is it better than color os 6?
Click to expand...
Click to collapse
If you search here and on the net, in general, lots of people are very disappointed with the realme ui 1.0 upgrade.
Like many others, I've upgraded and the battery life has dropped around 20%, at least.
Not sure if RMX1971_11_C.02 or RMX1971_11_C.03, that some people are eligible to download, solves the issue.

hsm90 said:
Hello
I got android 10 ui 1.0 update
Do you advice me to download it or not?
is it better than color os 6?
Click to expand...
Click to collapse
better not to upgrade it,just stay at color os 6 coz so many bug on eary realme UI

Thank you guys

How to disable this update ever?

hsm90 said:
Hello
I got android 10 ui 1.0 update
Do you advice me to download it or not?
is it better than color os 6?
Click to expand...
Click to collapse
Nooo!!! Please do not update it!! It'll ruin your mobile!! So many bugs and the worst part is you will not be able to downgrade it!!

What bugs are we talking about, I've had UI 1.0 for a week and haven't had any issues, other then not being able to use my own messaging app, but that was the same with ColorOS 6. UI will actually let me run Nova Prime where ColorOS 6 wouldn't let me allow to set to default. Running Q CN model.

I'm not having any issues at all. Its better than color os for sure. And the battery backup has also increased.

imtiaz007 said:
I'm not having any issues at all. Its better than color os for sure. And the battery backup has also increased.
Click to expand...
Click to collapse
No issues at al except it removed themes app for good.

Hi everyone,
I am currently using the Global ColorOS port for the Realme Q.
If you are on Realme UI (Chinese ROM) for this phone, can you confirm how does the GAPPS work?
I want to upgrade to RealmeUI, but I don't want to fight with the chinese apps, prefer jsut to get the old gapps

just one question guys. i am still on colors os an didnt get the update yet (germany/europe). when I flash the ui 1.0 over it manually, with realme recovery and the official file from the website.
is this then a dirty flash which keeps data and apps?

jupppo said:
just one question guys. i am still on colors os an didnt get the update yet (germany/europe). when I flash the ui 1.0 over it manually, with realme recovery and the official file from the website.
is this then a dirty flash which keeps data and apps?
Click to expand...
Click to collapse
Yes off course, your data and app save. you can flashing firmware other region to your device without worry lose data and app.

I'm trying to install the Q update downloaded from the Realme website (https://www.realme.com/eu/support/software-update), but it keeps failing, both from the file manager and recovery. How do I even install this update, or should I skip it because it's bad.

I have problem with update to android 10, I was downloaded this file RMX1971EX_11_OTA_1040_all_XObW6afyijrq.ozip (var. C.04 but same with C.01) from realme website and if I try to install from the file manager it does not start updating only opens form with decompress option (instead of start updating).
If I try to install from recovery it runs abous 1-2 sec and after that writes Innstalation failed. Is it something what I'm doing wrong?

So I found solution, when I bought 5 pro a had version colorOS A.09. No OTA update available. Manual update to realmeUI wasn't working (file manager, recovery). I must download last version of colorOS A.17 and installed that (file manager worked) and after that I can update to realmeUI C.04 (file manager). So I hope that this info can help someone who struggled with update like I did.

cjsegninir said:
Hi everyone,
I am currently using the Global ColorOS port for the Realme Q.
If you are on Realme UI (Chinese ROM) for this phone, can you confirm how does the GAPPS work?
I want to upgrade to RealmeUI, but I don't want to fight with the chinese apps, prefer jsut to get the old gapps
Click to expand...
Click to collapse
Hi, maybe it is late but anyway I am telling you: I used Global Port in Realme Q, it already has gapps, and when I dirty-installed RUI official, the system preserves gapps so you don't have to install them and they work fine, at least this is my case so if you try and it doesn't work, please, don't kill the messenger.
Good luck

Looking for help in reverting back to android 11

Hello everyone, I currently have a Samsung note 10 plus and just updated to Android 12 and it has completely ruined my home button and my recent button and my home screen. Is there a way to revert back to android 11? Or am SOL. I'm still trying to find a way to fix the current issue but haven't found anything as of yet. Thanks in advance

Use this if you can, works in Android 9 and 10.
Check Samsung settings too as Samsung tends to retain nav buttons in spite of Google's insanity.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thanks I'll try this when I get home. If this does not work is flashing the stock rom possible? I'm using an att samsung galaxy note 10 plus

imjustanoob said:
Thanks I'll try this when I get home. If this does not work is flashing the stock rom possible? I'm using an att samsung galaxy note 10 plus
Click to expand...
Click to collapse
Depends on the bootloader version. I think some here have rolled back but not sure if you can.
First thing I do is disable OTA updates. My N10+'s are running on 9 and 10.

Ahhh, well no luck for me on the good lock option. So how can I find my bootloader version? It's either a flash or I'll have to get a replacement phone

Understanding Firmware naming:
N986USQU1ATGM
N=Note
986U or F etc, the model of device
SQ, FX etc = CPU and model specific
U,S,E = Update, Security, Engineering, respectively
1,2,3,4,5 etc = bootloader revision (This is important! You cannot go to a previous revision)
A,B,C,D = Android version
T, U = Year (T=2020, U=2021 etc)
A,B,C etc = month (January A - December L)
1 - 9 and then A - Z =build compilation. This basically means how many builds there are in a month. They start at 1 and go to Z
So N986USQU1ATGM would be
N968-U-SQ-U-1-A-T-G-M
N968U (Note 20 Ultra Carrier version), SQ (Snapdragon), U (Update), 1 (Bootloader version), A (Build 10), T (2020), G (July), M (22nd build)
Significant digit, in this case it's a 2. This
my Android 9 variant:

Ahhh, well no luck for me on the good lock option. So how can I find my bootloader version? It's either a flash or I'll have to get a replacement phone sad
blackhawk said:
Understanding Firmware naming:
N986USQU1ATGM
N=Note
986U or F etc, the model of device
SQ, FX etc = CPU and model specific
U,S,E = Update, Security, Engineering, respectively
1,2,3,4,5 etc = bootloader revision (This is important! You cannot go to a previous revision)
A,B,C,D = Android version
T, U = Year (T=2020, U=2021 etc)
A,B,C etc = month (January A - December L)
1 - 9 and then A - Z =build compilation. This basically means how many builds there are in a month. They start at 1 and go to Z
So N986USQU1ATGM would be
N968-U-SQ-U-1-A-T-G-M
N968U (Note 20 Ultra Carrier version), SQ (Snapdragon), U (Update), 1 (Bootloader version), A (Build 10), T (2020), G (July), M (22nd build)
Significant digit, in this case it's a 2. This
my Android 9 variant:
View attachment 5510351
Click to expand...
Click to collapse
OK cool, mines happens to be a 7.

Ahh I read a little more in depth into your reply. Thanks for the detailed explanation

imjustanoob said:
Ahh I read a little more in depth into your reply. Thanks for the detailed explanation
Click to expand...
Click to collapse
You're welcome.
It's a lot easier just to lock down updates. My Android 10 variant might run slightly better but the differences between them is slight. Security has never been an issue on either one.
Try a factory reset if you haven't. You should do one with a major upgrade. May be some of the problem.

blackhawk said:
You're welcome.
It's a lot easier just to lock down updates. My Android 10 variant might run slightly better but the differences between them is slight. Security has never been an issue on either one.
Try a factory reset if you haven't. You should do one with a major upgrade. May be some of the problem.
Click to expand...
Click to collapse
I'll give that a try when I get home. Thanks so much