Related
FyrestoneROM T113The simplicity of TouchWiz system without superfluous
Code:
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
Introduction:
This Rom is the stock samsung without annoying apps and with some tweaks made to make your life easier.
I have a lot to do for make it better, but I hope you appreciate my work, if you don't thanks for giving me a chance.
Features:
Based on T113XXU0ARB1
Debolated - Samsung and Google apps (350 MB of useless apps)
Deodexed
Zipaligned
Faster animation scale
Knox Free
Removed boot sound
Rooted with SuperSu
Busybox
Sony System signature - Feel free to install sony apps from play store!
AOSP Keyboard
Removed Samsung Update
Allow apps access to external storage
Removed Loud volume warning
Cyanogen/LineageOS UI sounds
Tweaks:
Battery Tweaks
Better scrolling
Video acceleration and HW debugging
Better RAM management
Google DNS
Download Link:
DOWNLOADMD5: b7694314c6cfe88f013522b86319210d
Old version [4 Feb 2017]: DOWNLOAD
MD5: 283aa300c00ae227b4362945925db4b4
Old version [4 Jan 2017]: DOWNLOAD
MD5: 6f97e788b0b2571742b256e6fcaf1e86
How to install The Rom:
Update your bootloader and baseband to XXU0ARB1 before flash!
1. Flash TWRP 2.8.7.0.tar with Odin 3.12.10.
2. Flash TWRP 3.0.2-0.img inside the recovery (Select Install image and choose Recovery partition).
3. Reboot into TWRP 3.0.2-0.
4. Copy FyrestoneROM_T113_XXXXX.zip in your SD Card.
5. Wipe: System, Data, Cache and Dalvik.
6. Optional – Wipe Internal Storage.
7. Install FyrestoneROM_T113_XXXXX.
8. Reboot and wait about 10 minutes.
How to install The Firmware:
1. Download and extract a zip file containing your desired firmware.
2. Open Odin Tool.
3. Boot your device in the "Download Mode":
(Press Volume Down, Power and Home buttons at same time for 5-8 seconds until download mode is active.)
4. Connect your device to PC via the USB cable while in download mode.
5. Next, check the "Auto Reboot" and "F. Reset Time" options in Odin Tool.
6. Hit the AP/PDA button then browse and select a tar.md5 file from the extracted folder.
7. Finally press the start button to begin flashing the firmware update on your device.
Credits:
Google for Android OS
Samsung for FW and source
Sony for System signature
Cyanogenmod for File manager
@SuperR for the kitchen
@bravonova for Build.prop Tweaks
@Chainfire for SuperSu
@mrRobinson for AdAway
XDA:DevDB Information
FyrestoneROM, ROM for the Samsung Galaxy Tab 3
Contributors
Jimbus369
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: T113XXU0AQA1
Based On: STOCK Samsung
Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2017-02-04
Created 2017-01-04
Last Updated 2018-08-18
Reserved
Changelog:
27 July 2018:
Updated to XXU0ARB1
Fixed all previous issues
Removed Cyanogen File manager and Adawey
Now Thunderoar Kernel v5.0 is fully compatible
Updated Busybox and SuperSu
4 Feb 2017:
Updated to XXU0AQA1
Removed some Bloatware
Deodexed
Zipaligned
Faster animation scale
Allow apps access to external storage
Loud volume warning removed
Cyanogen/LineageOS UI sounds
Battery Tweaks
Increase Quality Of Media Streaming
Fixed Google DNS
Fixed Calendar Sync
Various build.prop changes
Various fix
4 Jan 2017:
Initial release
Known issues:
Calendar doesn't synchronize --> Calendar_sync_fix.zip
Tablet doesn't support vpn functionality --> VPN_FIX.zip
Print spooler does not works --> PrintSpooler_FIX.zip
Fantastic! Finally we've got a rom of our very own, for which you've got my immense thanks. I'm very much looking forward to trying it out.
Unfortunately when I flashed it there was a loooong wait on the Samsung logo, and then... Well, after an hour I booted back to recovery to start over.
I honestly don't think your rom was the problem though, because from some point last night everything I tried - custom rom flashing and nandroid backup restores - wound up the same way. Odin + stock + root got a usable system at least, and today's been too busy to try again. But when I do I'll post back about how it goes.
(Sadly, I can't go back in time to see what order I did things and look for a pattern if this happens again. In case it might be useful to anyone, I know for sure I'd gotten stock set up comfortably and made a complete backup before giving thunderoar's T113 kernel a whirl, and that went swimmingly. Even had mounts2sd properly recognizing external sd set up after a long struggle, though not actually enabled yet. Don't know what else i did between making that backup and trying to flash this, but it's likely I just screwed something up somehow.)
PushyPhoenix said:
Fantastic! Finally we've got a rom of our very own, for which you've got my immense thanks. I'm very much looking forward to trying it out.
Unfortunately when I flashed it there was a loooong wait on the Samsung logo, and then... Well, after an hour I booted back to recovery to start over.
I honestly don't think your rom was the problem though, because from some point last night everything I tried - custom rom flashing and nandroid backup restores - wound up the same way. Odin + stock + root got a usable system at least, and today's been too busy to try again. But when I do I'll post back about how it goes.
(Sadly, I can't go back in time to see what order I did things and look for a pattern if this happens again. In case it might be useful to anyone, I know for sure I'd gotten stock set up comfortably and made a complete backup before giving thunderoar's T113 kernel a whirl, and that went swimmingly. Even had mounts2sd properly recognizing external sd set up after a long struggle, though not actually enabled yet. Don't know what else i did between making that backup and trying to flash this, but it's likely I just screwed something up somehow.)
Click to expand...
Click to collapse
Upgrade your firmware to PH5 before flash and use TWRP 3.0.2-0.
Firmware: http://samsung-updates.com/device/?id=SM-T113
TWRP: https://dl.twrp.me/goyave/
Wipe all partition in TWRP:
System, Cache, Dalvik and if you can internal Storage.
Thunderoar Kernel isn't compatible with PH5 firmware for the moment.
Let me know how it goes
Thanks so much for responding even though I didn't specifically ask.
Pretty much all my knowledge comes from following instructions in these forums and piecing little bits of information together, so I've got a few questions - trying to understand the "why" behind these things in order to be more self-sufficient. Please feel free to point me towards resources where I can learn more!
Jimbus369 said:
Upgrade your firmware to PH5 before flash and use TWRP 3.0.2-0.
Click to expand...
Click to collapse
This is a surprise to me - I'd always thought that when flashing a new ROM, everything gets replaced. I never would have figured this part out on my own!
Firmware: http://samsung-updates.com/device/?id=SM-T113
Click to expand...
Click to collapse
There's no Canadian version - but should I presume that, since this is a Wi-Fi only device, the CSC isn't too important?
How much does this matter even when using a device with a network connection?
TWRP: https://dl.twrp.me/goyave/
Click to expand...
Click to collapse
(Ooops, forgot to do this right off the bat. My bad!)
Does recovery version generally make a big difference?
Wipe all partition in TWRP:
System, Cache, Dalvik and if you can internal Storage.
Click to expand...
Click to collapse
I've been wiping Data as well - is that not necessary?
Does wiping Internal Storage have a big effect? I suppose there's a fair bit of app-specific stuff in there that could cause issues?
Thunderoar Kernel isn't compatible with PH5 firmware for the moment.
Click to expand...
Click to collapse
Ah well, soon enough!
Let me know how it goes
Click to expand...
Click to collapse
Of course! You're investing time in putting this together, and helping out users; the very least I can do is let you know what's going on with that time you've invested!
Okay, about to check on the firmware installation!
PushyPhoenix said:
This is a surprise to me - I'd always thought that when flashing a new ROM, everything gets replaced. I never would have figured this part out on my own!
Click to expand...
Click to collapse
When you install a rom, especially a TW one, in most case you need a specific Bootloader to cause it to start and work smoothly.
Wikipedia:
A boot loader is a computer program that loads an operating system or some other system software for the computer after completion of the power-on self-tests; it is the loader for the operating system itself. Within the hard reboot process, it runs after completion of the self-tests, then loads and runs the software. A boot loader is loaded into main memory from persistent memory, such as a hard disk drive or, in some older computers, from a medium such as punched cards, punched tape, or magnetic tape. The boot loader then loads and executes the processes that finalize the boot. Like POST processes, the boot loader code comes from a "hard-wired" and persistent location; if that location is too limited for some reason, that primary boot loader calls a second-stage boot loader or a secondary program loader.
The bootloader runs your rom with specific instructions, if the rom does not support an older bootloader simply does not boot. My rom does not support the older bootloader. A zip flash in this case cannot upgrade a delicate part like the bootloader. You need to flash the newer one with Odin.
There's no Canadian version - but should I presume that, since this is a Wi-Fi only device, the CSC isn't too important?
How much does this matter even when using a device with a network connection?
Click to expand...
Click to collapse
The latest update for your country is PA5. Try with THIS.
Your country code is XAC.
The CSC (Sale Country Code) Is that part of the firmware that contains all the telephone operator customizations (e.g. WAP, MMS) for the intended country. As far as i know, It is not important for us.
(Ooops, forgot to do this right off the bat. My bad!)
Does recovery version generally make a big difference?
Click to expand...
Click to collapse
Yes, the Recovery can make the difference.
I've been wiping Data as well - is that not necessary?
Does wiping Internal Storage have a big effect? I suppose there's a fair bit of app-specific stuff in there that could cause issues?
Click to expand...
Click to collapse
I forgot to write data, my bad! But i wrote it in the instructions in the first topic. For personal experience i had different issues when I didn't formatted the Internal Storage. The Android folder, .thumbnails and others, can create issues.
Ah well, soon enough!
Click to expand...
Click to collapse
I hope that in the next update we could use this kernel. :fingers-crossed:
Of course! You're investing time in putting this together, and helping out users; the very least I can do is let you know what's going on with that time you've invested!
Okay, about to check on the firmware installation!
Click to expand...
Click to collapse
I want to give my best support at all users in difficulty, if you have a problem just ask. :good: :good:
Sorry for my english
Jimbus369 said:
Sorry for my english
Click to expand...
Click to collapse
You're doing just fine!
I'll reply more later, but wanted to report that it's installed and running very smoothly! Haven't played around much but will do at home later.
If you've got any tips for getting mounts2sd up and running I'd really appreciate it!
PushyPhoenix said:
You're doing just fine!
I'll reply more later, but wanted to report that it's installed and running very smoothly! Haven't played around much but will do at home later.
If you've got any tips for getting mounts2sd up and running I'd really appreciate it!
Click to expand...
Click to collapse
I'm happy to hear it. Anyway, I don't know how mounts2sd works. Have you already tried HERE?
Jimbus369 said:
I'm happy to hear it. Anyway, I don't know how mounts2sd works. Have you already tried HERE?
Click to expand...
Click to collapse
Yup, that's the app I'm using, but haven't been able to get my external partition mounted properly. I did manage it once, think it was with thunderoar's kernel though.
Sent from my SM-G900W8 using XDA Labs
Jimbus369 said:
I'm happy to hear it.
Click to expand...
Click to collapse
Life has gotten in the way of playing around with this, but thought I'd send you an update as I said I would...
Your rom is running really nicely on my tablet as I use it daily. It's smooth and small, with no unexpected reboots or fc's on installed apps. Didn't wipe internal SD but it hasn't given me any issues with existing data (probably because there wasn't much to start with).
One thing that has caused a problem is calendar sync. It looks like you've taken out the actual syncing service, so when I try to access my calendars through any app I'm asked to add a new Google account, even though everything's already set up in "Accounts" under Settings. I haven't tried running the "calendars.providers.apk" from my other phone, that should fix the problem - but I don't want to use the wrong version and break something!
Also, I've confirmed that the only time I got mounts2sd working, it was with thunderoar's kernel. So guess that's going to have to wait.
A few adjustments I made to the setup were to uninstall all "unnecessary" system apps (not needed to run the device), and re-install them from the store. This way I've got 676mb free on /system and still over 1.5GB free on internal storage.
I've also added a multi-reboot menu to make getting into recovery or download mode simpler, and this is loading more quickly on your rom than stock. I've also had to modify permissions.xml to allow apps to access external storage by default, and made another tweak to disable the "loud volume warning" (don't remember quite what it was offhand).
Would you consider adding these to a future version?
Again, thanks SO much for putting this together, answering questions, and doing your thing. It's greatly appreciated!
PushyPhoenix said:
Life has gotten in the way of playing around with this, but thought I'd send you an update as I said I would...
Your rom is running really nicely on my tablet as I use it daily. It's smooth and small, with no unexpected reboots or fc's on installed apps. Didn't wipe internal SD but it hasn't given me any issues with existing data (probably because there wasn't much to start with).
One thing that has caused a problem is calendar sync. It looks like you've taken out the actual syncing service, so when I try to access my calendars through any app I'm asked to add a new Google account, even though everything's already set up in "Accounts" under Settings. I haven't tried running the "calendars.providers.apk" from my other phone, that should fix the problem - but I don't want to use the wrong version and break something!
Also, I've confirmed that the only time I got mounts2sd working, it was with thunderoar's kernel. So guess that's going to have to wait.
A few adjustments I made to the setup were to uninstall all "unnecessary" system apps (not needed to run the device), and re-install them from the store. This way I've got 676mb free on /system and still over 1.5GB free on internal storage.
I've also added a multi-reboot menu to make getting into recovery or download mode simpler, and this is loading more quickly on your rom than stock. I've also had to modify permissions.xml to allow apps to access external storage by default, and made another tweak to disable the "loud volume warning" (don't remember quite what it was offhand).
Would you consider adding these to a future version?
Again, thanks SO much for putting this together, answering questions, and doing your thing. It's greatly appreciated!
Click to expand...
Click to collapse
The calendar sync issue should be fixed in the next update.
Anyway, If I have enough time, the next update should contain a lot of new features. Your suggestions are already planned :good:
Jimbus369 said:
When you install a rom, especially a TW one, in most case you need a specific Bootloader to cause it to start and work smoothly.
....
The bootloader runs your rom with specific instructions, if the rom does not support an older bootloader simply does not boot. My rom does not support the older bootloader. A zip flash in this case cannot upgrade a delicate part like the bootloader. You need to flash the newer one with Odin.
Click to expand...
Click to collapse
One more question about this: The way you've worded the second paragraph seems to imply only that older bootloaders don't work with newer roms, so are newer bootloaders backwards compatible? Say I've got the PH5 bootloader installed and I want to restore a backup of the previous firmware, do I have to flash that firmware first?
Sorry if it seems obvious, this is how we learn!
Sent from my SM-G900W8 using XDA Labs
PushyPhoenix said:
One more question about this: The way you've worded the second paragraph seems to imply only that older bootloaders don't work with newer roms, so are newer bootloaders backwards compatible? Say I've got the PH5 bootloader installed and I want to restore a backup of the previous firmware, do I have to flash that firmware first?
Sorry if it seems obvious, this is how we learn!
Sent from my SM-G900W8 using XDA Labs
Click to expand...
Click to collapse
Absolutely it isn't obvious, don't worry . The Bootloader, for my personal experience, are backwards compatible. I don't have a scientific knowledge about this, but for what I did with other device it can work. Just try :fingers-crossed:, don't forget a full backup.
Calendar_sync_fix.zip
Here is a fix for calendar sync.
@PushyPhoenix Thanks for reporting this issue
Jimbus369 said:
Calendar_sync_fix.zip
Here is a fix for calendar sync.
@PushyPhoenix Thanks for reporting this issue
Click to expand...
Click to collapse
This is a huge help, as one reason for getting this tablet was to use the calendar on a bigger screen.... Thanks so much!
---------- Post added at 10:58 PM ---------- Previous post was at 10:50 PM ----------
Jimbus369 said:
The Bootloader, for my personal experience, are backwards compatible. I don't have a scientific knowledge about this, but for what I did with other device it can work. Just try :fingers-crossed:
Click to expand...
Click to collapse
Fantastic - it worked on my S5 (had to restore a backup to retrieve some data).
don't forget a full backup.
Click to expand...
Click to collapse
Never! The most important thing, along with wiping.
When is coming to FyrestoneROM V2 ?
And thank you very much. So love...
Does this work on sm-t116ny ?
Because no development for sm-t116ny .
dhruvpatel_9880 said:
Does this work on sm-t116ny ?
Because no development for sm-t116ny .
Click to expand...
Click to collapse
I don't think it can work. If your device codename is Goyave you can try. Let me know if it works
Jimbus369 said:
I don't think it can work. If your device codename is Goyave you can try. Let me know if it works
Click to expand...
Click to collapse
First of all thanks for replying
My device codename is Goyave3g5m probably .
Can you please tell me which all models have same codename "Goyave"?
And cm 11 for sm-t116 works well on my sm-t116ny.
I will try and let you know does it boots .
---------- Post added at 01:55 PM ---------- Previous post was at 01:40 PM ----------
It is working on sm-t116ny
But wifi hotspot not working
Please help
dhruvpatel_9880 said:
First of all thanks for replying
My device codename is Goyave3g5m probably .
Can you please tell me which all models have same codename "Goyave"?
And cm 11 for sm-t116 works well on my sm-t116ny.
I will try and let you know does it boots .
---------- Post added at 01:55 PM ---------- Previous post was at 01:40 PM ----------
It is working on sm-t116ny
But wifi hotspot not working
Click to expand...
Click to collapse
T113/T113nu and T116/T116ny have a similar codename and hardware (The recovery have goyave codename, therefore any rom with goyave codename can be flashed). For the hotspot, maybe some missing libraries, a different driver or a different kernel makes hotspot broken. Try to restore your kernel from a previous backup.
Hi all,
Today I have updated my Note 9 from 8.1 to 9.0
Everything went smoothly, and the update was installed without any issues.
Seems to be that everything works fine, except one small little thing:
Contact information on the AOD.
It does exist, and it's visible on the lock screen.
Tried to remove it, re-add it, phone restart, cache removal, app cache+data removal, but without any luck....
I'm using the up-to-date version of the app, 4.1.37.
Basically, everything is stock and up to date.
Does anyone have the same problem?
[UPDATE] I have just talked to Samsung Support, and looks like it's a bug.
Her advice was to do the factory reset.
I need to do the backup first, and then I will let you know the outcome.
Could you share how you updated to Pie please? I'm getting mixed, confusing info. after browsing thru all the forum threads...
Thanks!
rodrigofd said:
Could you share how you updated to Pie please? I'm getting mixed, confusing info. after browsing thru all the forum threads...
Thanks!
Click to expand...
Click to collapse
Hi,
I have received an updated OTA.
Full stock, not rooted.
Settings - Software Update - Download and install updates.
Best regards.
rodrigofd said:
Could you share how you updated to Pie please? I'm getting mixed, confusing info. after browsing thru all the forum threads...
Thanks!
Click to expand...
Click to collapse
*#1234# <--- Type that into phone dialer and see if it's the same as the screen shot firmware Note 9 version info i have posted! if yes then follow below!
NOTE: THESE UPDATE.ZIP's ARE ONLY FOR DEVICES WITH MULTI-CSC OXM!!!
You can check this, to type in your dialer *#1234#, and check if OXM is in the CSC-build...
Managed to get the UPDATE.ZIP if your Note9 is currently on ARL3 (Oreo) to CSA2 (Pie)
ARL3 -> CSA2
If your device is still on ARK2, then update first to ARL3:
ARK2 -> ARL3
* If you have sd card place update.zip in it boot to recovery by holding power up + power +bixby button.
* Go to apply update from SD card.
* just choose install update, If no sd card choose adb in recovery.
* Download adb from here https://dl.google.com/android/reposi...st-windows.zip
Please NOTE this is not my guide!! All Thanks and all credits go to @jaylence for taking the effort to reset his device, and getting the "update.zip" for you!
Original Thread --> https://forum.xda-developers.com/showpost.php?p=78660727&postcount=384
N1NJATH3ORY said:
*#1234# <--- Type that into phone dialer and see if it's the same as the screen shot firmware Note 9 version info i have posted! if yes then follow below!
NOTE: THESE UPDATE.ZIP's ARE ONLY FOR DEVICES WITH MULTI-CSC OXM!!!
You can check this, to type in your dialer *#1234#, and check if OXM is in the CSC-build...
Managed to get the UPDATE.ZIP if your Note9 is currently on ARL3 (Oreo) to CSA2 (Pie)
ARL3 -> CSA2
If your device is still on ARK2, then update first to ARL3:
ARK2 -> ARL3
* If you have sd card place update.zip in it boot to recovery by holding power up + power +bixby button.
* Go to apply update from SD card.
* just choose install update, If no sd card choose adb in recovery.
* Download adb from here https://dl.google.com/android/reposi...st-windows.zip
Click to expand...
Click to collapse
Hi,
1.) Please credit the OP.
2.) Both of you are off-topic.
If you have already upgraded your Note 9, can you please check it out and answer my questions?
Thank you!
i also have a problem
dorianborovina said:
Hi,
1.) Please credit the OP.
2.) Both of you are off-topic.
If you have already upgraded your Note 9, can you please check it out and answer my questions?
Thank you!
Click to expand...
Click to collapse
Apologies i'll credit and edit above guide! Thanks
---------- Post added at 01:26 AM ---------- Previous post was at 01:09 AM ----------
dorianborovina said:
Hi all,
Today I have updated my Note 9 from 8.1 to 9.0
Everything went smoothly, and the update was installed without any issues.
Seems to be that everything works fine, except one small little thing:
Contact information on the AOD.
It does exist, and it's visible on the lock screen.
Tried to remove it, re-add it, phone restart, cache removal, app cache+data removal, but without any luck....
I'm using the up-to-date version of the app, 4.1.37.
Basically, everything is stock and up to date.
Does anyone have the same problem?
Click to expand...
Click to collapse
Yep i have the same issue, i typed out N1NJATH3ORY saved it, put NOTE-9 to sleep so AOD comes on. i can’t see N1NJATH3ORY i even tried different AOD face to see if that fixes it, but it don’t. I can’t see no contact info being displayed on AOD.. Your not the only one, I am on Android PIE 9.ONE UI NOTE-9 EXYNOS!
N1NJATH3ORY said:
Apologies i'll credit and edit above guide! Thanks
---------- Post added at 01:26 AM ---------- Previous post was at 01:09 AM ----------
Yep i have the same issue, i typed out N1NJATH3ORY saved it, put NOTE-9 to sleep so AOD comes on. i can’t see N1NJATH3ORY i even tried different AOD face to see if that fixes it, but it don’t. I can’t see no contact info being displayed on AOD.. Your not the only one, I am on Android PIE 9.ONE UI NOTE-9 EXYNOS!
Click to expand...
Click to collapse
Hi,
Thank you for your time and effort!
Looks like it's a Android 9 feature.
Just to make it sure, contact information text does appear on the lock screen?
Best regards,
Dorian Borovina
dorianborovina said:
Hi,
Thank you for your time and effort!
Looks like it's a Android 9 feature.
Just to make it sure, contact information text does appear on the lock screen?
Best regards,
Dorian Borovina
Click to expand...
Click to collapse
That's correct i can see contact info on lock screen! But no contact info on AOD!
N1NJATH3ORY said:
That's correct i can see contact info on lock screen! But no contact info on AOD!
Click to expand...
Click to collapse
Thank you for your confirmation.
I just wanted to know if it was a problem only on my side.
Best regards,
Dorian Borovina
same problem
No problem
biyolog4472 said:
No problem
Click to expand...
Click to collapse
Strange,
Please can you compare my signature data with your mobile phone software versions?
Thanks!
Exactly the same issue.
Exynos Version of Note 9 (Android Pie).
Micheal86 said:
Exactly the same issue.
Exynos Version of Note 9 (Android Pie).
Click to expand...
Click to collapse
Customer support told me to do the factory reset.
Not sure if I want to do it, and reconfigure the whole thing back again.
Has anyone tried to do and restore the complete phone backup with Samsung Switch?
dorianborovina said:
Customer support told me to do the factory reset.
Not sure if I want to do it, and reconfigure the whole thing back again.
Has anyone tried to do and restore the complete phone backup with Samsung Switch?
Click to expand...
Click to collapse
I`ve done factory reset after the update and then set up the device. And after installing all the apps wipe cache.
But still, have the same issue.
Micheal86 said:
I`ve done factory reset after the update and then set up the device. And after installing all the apps wipe cache.
But still, have the same issue.
Click to expand...
Click to collapse
Thank you for your reply, I appreciate it!
I was wondering if I should do the factory reset, because I've done everything except factory reset.
But, now you told me that you did it, and that the problem still persists, you have really saved me some time!
I'm going to contact the Samsung support one more time, and let them know what's going on.
Stay in touch!
Best regards,
Dorian Borovina
dorianborovina said:
Hi all,
Today I have updated my Note 9 from 8.1 to 9.0
Everything went smoothly, and the update was installed without any issues.
Seems to be that everything works fine, except one small little thing:
Contact information on the AOD.
It does exist, and it's visible on the lock screen.
Tried to remove it, re-add it, phone restart, cache removal, app cache+data removal, but without any luck....
I'm using the up-to-date version of the app, 4.1.37.
Basically, everything is stock and up to date.
Does anyone have the same problem?
[UPDATE] I have just talked to Samsung Support, and looks like it's a bug.
Her advice was to do the factory reset.
I need to do the backup first, and then I will let you know the outcome.
Click to expand...
Click to collapse
another reason i will not be updating! cant get the Senselessness of pushing out half - baked updates
dorianborovina said:
Thank you for your reply, I appreciate it!
I was wondering if I should do the factory reset, because I've done everything except factory reset.
But, now you told me that you did it, and that the problem still persists, you have really saved me some time!
I'm going to contact the Samsung support one more time, and let them know what's going on.
Stay in touch!
Best regards,
Dorian Borovina
Click to expand...
Click to collapse
You`re welcome mate.
BTW, how is your battery life in Android Pie?
Mine is not satisfactory. I used to get better battery backup in Android O. Though I know this new OS would take some time to be stable, and battery backup might be increased.
Sorry for the off-topic.
Micheal86 said:
You`re welcome mate.
BTW, how is your battery life in Android Pie?
Mine is not satisfactory. I used to get better battery backup in Android O. Though I know this new OS would take some time to be stable, and battery backup might be increased.
Sorry for the off-topic.
Click to expand...
Click to collapse
To be honest, I haven't noticed any difference.
I'm able to go through the day without recharging it, and that's the most important thing for me.
How often do you charge it?
XZ/KAGURA/F8331 OmniROM BUILDS
PIE 9.0
DOWNLOAD WEEKLY
REQUIREMENTS TO SUCCESSFULLY FLASH OMNIROM:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip (version 9) has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
INSTALLATION INSTRUCTIONS:
1. Reboot device to fastboot mode, and flash the ODM image with this command
Code:
fastboot flash oem <ODM image>
2. Reboot device to TWRP and flash the WEEKLY zip file
3. (If coming from an 8.1 ROM) Fix /dsp SELinux labels with the dsp-label-fixer.zip
4. (Optional) Flash a gapps package
5. Reboot device to system
CURRENT ISSUES ON OFFICIAL:
1. Device wakes up by itself every 5 seconds, reason unknown
2. Camera quality is suboptimal
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-9.0
BUG REPORTS
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
XDA:DevDB Information
[ROM][XZ][P][9.0][WEEKLY]OmniROM, ROM for the Sony Xperia XZ
Contributors
oshmoun, humberos, local__hero
Source Code: https://github.com/omnirom
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: latest stock ftf
Version Information
Status: Beta
Created 2019-03-17
Last Updated 2019-05-31
Thank you for the separate this from the other pie roms.
I will flash it after I arrive home.
Thank you all for the hard work!
Sent from my kagura using XDA Labs
I'm loving the fact Omnipie is official. I will be flashing this right now. Thank you so much.
Finally flashed! been using it for less than an hour, i can say that its definitely good for daily use. Camera seems better and hasnt crashed yet (like it use to), mic actually picks up audio properly, brightness slider is finally proportional to the brightness level, and its pie
however, the stereo speaker seems to muffle at high volumes (especially with the ringtones and less with youtube, but still a little prevelent), app opening times seem a little longer than 8.1, and 120HZ still doesnt work
im also curious why the linked odm isnt the latest one (im pretty sure the latest is 1st march not feb)
anyways, thanks dev! (may be editing this thread after more use for battery etc)
XxperexX said:
however, the stereo speaker seems to muffle at high volumes (especially with the ringtones and less with youtube, but still a little prevelent)
Click to expand...
Click to collapse
Could it be this kernel bug: https://github.com/sonyxperiadev/bug_tracker/issues/336 ? Looks like the sonyxperiadev team is working on it.
XxperexX said:
im also curious why the linked odm isnt the latest one (im pretty sure the latest is 1st march not feb)
Click to expand...
Click to collapse
The March 1 release says "Android 8.1", the linked one looks like the latest for Pie.
sinivalas23 said:
Could it be this kernel bug: https://github.com/sonyxperiadev/bug_tracker/issues/336 ? Looks like the sonyxperiadev team is working on it.
The March 1 release says "Android 8.1", the linked one looks like the latest for Pie.
Click to expand...
Click to collapse
Ah, your correct it does say 8.1 my bad
opps
I saw this version from delta updater (using 8.1 omni) and immediately downloaded flashed oem for pie and downloaded omni 9 but it stucked new omni animated logo. Waited like 10 minutes but nothing happened then rebooted phone but same thing happened. Should i wait more or something went wrong?
Im here with OmniROM freshly flashed trough Open Delta.
I have some problems. First boot never ends, BUT restart worked for me but I have another problem.
Now I need 10 min to unlock the phone when Im lucky.
I unlock with the code and then its instantly relock and it say I cant use fingerprint for first unlock, so I use code again and not work again and still can't use fingerprint.
I do this A LOT OF TIME before I can use my phone. Sometimes it helps sometimes not if I not unlock my phone but use corner dial icon first and then if its ask for code i use it and then I got SystemUI crash error again and again and again.
As I said I try to repeat this methods for like 10 min after every restart. I tried to delete some maybe not compatible apps with this new update but still nothing. Now I will remove some Magisk modules. I will write again.
KikiGames said:
Im here with OmniROM freshly flashed trough Open Delta.
I have some problems. First boot never ends, BUT restart worked for me but I have another problem.
Now I need 10 min to unlock the phone when Im lucky.
I unlock with the code and then its instantly relock and it say I cant use fingerprint for first unlock, so I use code again and not work again and still can't use fingerprint.
I do this A LOT OF TIME before I can use my phone. Sometimes it helps sometimes not if I not unlock my phone but use corner dial icon first and then if its ask for code i use it and then I got SystemUI crash error again and again and again.
As I said I try to repeat this methods for like 10 min after every restart. I tried to delete some maybe not compatible apps with this new update but still nothing. Now I will remove some Magisk modules. I will write again.
Click to expand...
Click to collapse
you need to do a full wipe before upgrading to p
Just as @oshmoun said; before flashing new ROMs, it's imperative to do full wipe (if you don't want to lose all your data, then do a full backup in TWRP), as flashing without full wiping can cause TONS of problems. Don't be lazy and follow the instructions properly.
oshmoun said:
you need to do a full wipe before upgrading to p
Click to expand...
Click to collapse
I used the same rom before but the last update. I updated through OpenDelta.
Hello !
It's cool to see our XZ is alive !
I have some problems with this rom after a full wipe and update to oem V6 :
- no sounds during calls, no mic, no earphone, no sounds on speaker
- Magisk 18.1 not working
- With official camera app, while using the flash, only the autofocus led is lit, the second and much powerful led is never triggered resulting on dark shots
For now that's all
Thx
Performance is somewhat distressed and the camera does not work for the sound is not working after restarting the device is improving
KikiGames said:
I used the same rom before but the last update. I updated through OpenDelta.
Click to expand...
Click to collapse
you cant do that. its pretty misleading having it available on that opendelta ota thingy. you have to follow the instructions in this thread
Flashed data, cache and dalvik, factory reset. And installed latest nightly with gapps and magisk 18.1.
Only reason I did it this way is because I was on a unofficial build on Omni. Everything is working as it should. Very snappy and no lag. Still have to see how the ROM handles after it's settled for a couple day, but right off the bat it's amazing. Thank you very much Dev, and happy to see you back on XDA.
XxperexX said:
you cant do that. its pretty misleading having it available on that opendelta ota thingy. you have to follow the instructions in this thread
Click to expand...
Click to collapse
Why this ROM showed up as an update then?
I just don't understand it.
Nevermind this is my main and only phone and I work 4 days straight before I can use my PC so I need to use this ROM buggy for me. :/
KikiGames said:
Why this ROM showed up as an update then?
I just don't understand it.
Nevermind this is my main and only phone and I work 4 days straight before I can use my PC so I need to use this ROM buggy for me. :/
Click to expand...
Click to collapse
You need a PC to flash this. Follow all steps in order and it'll work. Always remember, unless you have a messaging app that backups texts, you will lose them flashing a cfw. Always always backup anything you don't want to lose.
---------- Post added at 12:56 AM ---------- Previous post was at 12:28 AM ----------
I've had a reoccurring issue on the unofficial and official builds so far. I do not have the option to use my phone when calling unless speaker phone or a Bluetooth headset. I cannot put the phone to my head and use normally. Is there any kind of option to fix this nuisance. Any feedback is truly appreciated
Every 9.0 ROM I ever flash, I always seem to have the same problem. Whether its dirty flashing, or starting with flashtool, to CMD, and then to TWRP, the same problem seems to happen. After the ROM has settled, audio quality through calls becomes a huge problem. I'm not sure if I'm doing something wrong, but it has been a persistent bug, next chance I get for the next nightly ill send a logcat, kinda cant not since back on stock. I need good call quality for work lol. Either way, thank you for bringing OMNI to 9.0 official
anyone having problems with video playback? videos dont play on instagram, youtube or snapchat. using magisk 18.1 and latest omni 9 rom
edit: nvm, found out that the Google camera fix module for magisk was the problem
Thanks to "O grupo de discussões sobre tecnologia e outras coisas!...https://t.me/VegaData " for your solution.
Download GSI https://drive.google.com/file/d/1EnLAwEBaYLeepTSuQ2iUSoE8lm-csTPw/view?usp=sharing
(MIUI11-Aonly-9-VegaDataTests-exp-20191209-ErfanGSI.img.gz) ---extract before use
Information:
Android Version: 9
Brand: Xiaomi
Model: POCO F1
Codename: beryllium
Build Type: beryllium-user
Build Number: PKQ1.180729.001
Incremental: V11.0.5.0.PEJMIXM
Tags: release-keys
Security Patch: 2019-10-01
Fingerprint: Xiaomi/beryllium/beryllium:9/PKQ1.180729.001/V11.0.5.0.PEJMIXM:user/release-keys
Description: beryllium-user 9 PKQ1.180729.001 V11.0.5.0.PEJMIXM release-keys
Raw Image Size: 2.49 GiB
Clean Installation
Step:
1. flash latest Firmware https://mega.nz/#!QDplSYab!mrB5f8875VghQHfrrGvid4iJICMopkq3anZCipLWzqo
2. flash Vendor https://mega.nz/#!ECAG1aIS!OuGf9eVoiJpg0xreeLIarAWs5GkuCbu9AwR95MSlO-g
3. flash GSI as System Image
4. flash Permissiver v4.zip https://mega.nz/#!ETIwHQJC!Go5NfpgXFy5gPw8gFG8JbUCch7Eijw4rDp3NVTkhd-M
5. flash Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip https://mega.nz/#!gTohmQaR!ZL5jCeatYXUzUMx_moJseJ9o7b1RoLUf3o_PfOtn_aw
--Mount System & Vendor
6. flash Sound Fix (fixaudiogsi.zip) https://mega.nz/#!AD52wIhD!FM5GruKjw76gRnXqqLrh73CsSIZmldANlZrzyfVlcX0
7. flash DropVendorLightHAL.zip https://mega.nz/#!QKgVxaCI!lJuYDA2HjpP8msTbB7uXzW5jlvHImmHBtjjAdjt5R5g
8. flash DisableForceEncryption_Treble_v20.1.zip https://mega.nz/#!BHgRWYDS!jfuIRqTPTjS_lVy2tfpSbVRfqmxqqadeLFttgbKmhYQ
Reboot
-Verify your MI Account.
1.connect your WiFi 2. input you mi password. ...wait
- Magisk manager add MIUI_Auto_Brightness_Fix_v4_(pie).zip
https://mega.nz/#F!hT5UkSAQ!VCiS_BVC0Jlobpo6EMLsDg
-install GMS.apk and reboot
Coming soon --- Fingerprint Fix
Really great rom, everything works. Only missing feature is the face unlock. It's crazy smooth rom.
Hi, i plan to flash this one, is it better to use xiaomi flashtool or flashing them by hand?
ƁɐⱤᶒ said:
Hi, i plan to flash this one, is it better to use xiaomi flashtool or flashing them by hand?
Click to expand...
Click to collapse
By hand
zuhero said:
By hand
Click to expand...
Click to collapse
ok thanks
got it, but has problem with brightness,at most it remains low
Another noob question, is it better to be in china rom before going further with Miui 11 -Erfan GSIs or it is ok if i am on the EU Rom ?
and should i do a clean install before flashing anything?
pietroarnoldi said:
got it, but has problem with brightness,at most it remains low
Click to expand...
Click to collapse
I have no brightness problems
---------- Post added at 07:08 AM ---------- Previous post was at 07:06 AM ----------
ƁɐⱤᶒ said:
Another noob question, is it better to be in china rom before going further with Miui 11 -Erfan GSIs or it is ok if i am on the EU Rom ?
and should i do a clean install before flashing anything?
Click to expand...
Click to collapse
I don't think it matters cuz you're gonna flash the latest firmware.
Okay so after everything done, after reboot i 've been asked to unlock the device with the mi account, that succeed; except i have a message saying "An internal problem with your device has occurred. Please contact the manufacturer for more information."
On the latest Mega link i didn't find Magisk Manager.
And the external storage is working Yay!
ƁɐⱤᶒ said:
Okay so after everything done, after reboot i 've been asked to unlock the device with the mi account, that succeed; except i have a message saying "An internal problem with your device has occurred. Please contact the manufacturer for more information."
On the latest Mega link i didn't find Magisk Manager.
And the external storage is working Yay!
Click to expand...
Click to collapse
That message only appears one time after every boot, it doesn't matter, just ignore it. I'm using the latest magisk canary, working like a charm.
Understood, but i have another issue with Chrome that trying to update 299ko
i already checked authorizations under app settings
and made a video here
https://youtu.be/sp7jtkbLuKk
weird things is that i could install two apps without problems; any thought?
otherwise, this rom runs incredibly faster than the original one o_0'
Thanks for that!:good:
ƁɐⱤᶒ said:
Understood, but i have another issue with Chrome that trying to update 299ko
i already checked authorizations under app settings
and made a video here
https://drive.google.com/file/d/1BnNj6CH1tkQp1NQttDiBbTx6mORoRX9a/view?usp=sharing
weird things is that i could install two apps without problems; any thought?
otherwise, this rom runs incredibly faster than the original one o_0'
Thanks for that!:good:
Click to expand...
Click to collapse
Never had issues with chrome, try to reinstall app or clear data and cache from playstore and reboot.
Hi.
A video tutorial would be fine.
Thanks.
DANI36ZGZ said:
Hi.
A video tutorial would be fine.
Thanks.
Click to expand...
Click to collapse
i agree this installation is a bit more specific than what i already encounter, but following the steps on post is ok.
Many thanks for a great ROM and awesome work!!!
Please help about flash procedure:
3. flash GSI as System Image
Where is it please? And hot to flash it as system image?
Thanks!
Tom, thanks for everything you have done.
Only one question: when you fix fingerprint, will we have to flash whole system again or maybe only a part of it? Reading mode going to be fixed? (block blue light,useful to study)
thanks.
Edit:
@nirh216
Dude, in the bottom side, right side, there's a option to image file. click it, then choose the huge file (about 2gb) you donwloaded and flash it.
Edit2: Physical home button it's kinda useless to unlock right now, right? I cant see to use it even to unlock it, only as "home button". And i did not installed fix for auto brightness because mine is working, and i could not find how to install it by magisk, if anyone has atuto for it. thanks.
Edit3: 2 bugs I found. 1st Nav bar stop working after a while, needing to restart device to work. 2nd brightness from screen is definetly low, like half the bright from normal stock rom ----> I guess brightness is a problem from pocophone and about nav bar seems like tasker was fckng it up
Thanks.
Edit4: last edit lol. My twrp seems to be gone after doing every step and i cant find to install it again. you guys have twrp working?
tom.android said:
Thanks to "O grupo de discussões sobre tecnologia e outras coisas!...https://t.me/VegaData " for your solution.
Download GSI https://drive.google.com/file/d/1EnLAwEBaYLeepTSuQ2iUSoE8lm-csTPw/view?usp=sharing
(MIUI11-Aonly-9-VegaDataTests-exp-20191209-ErfanGSI.img.gz) ---extract before use
Information:
Android Version: 9
Brand: Xiaomi
Model: POCO F1
Codename: beryllium
Build Type: beryllium-user
Build Number: PKQ1.180729.001
Incremental: V11.0.5.0.PEJMIXM
Tags: release-keys
Security Patch: 2019-10-01
Fingerprint: Xiaomi/beryllium/beryllium:9/PKQ1.180729.001/V11.0.5.0.PEJMIXM:user/release-keys
Description: beryllium-user 9 PKQ1.180729.001 V11.0.5.0.PEJMIXM release-keys
Raw Image Size: 2.49 GiB
Clean Installation
Step:
1. flash latest Firmware https://mega.nz/#!QDplSYab!mrB5f8875VghQHfrrGvid4iJICMopkq3anZCipLWzqo
2. flash Vendor https://mega.nz/#!ECAG1aIS!OuGf9eVoiJpg0xreeLIarAWs5GkuCbu9AwR95MSlO-g
3. flash GSI as System Image
4. flash Permissiver v4.zip https://mega.nz/#!ETIwHQJC!Go5NfpgXFy5gPw8gFG8JbUCch7Eijw4rDp3NVTkhd-M
5. flash Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip https://mega.nz/#!gTohmQaR!ZL5jCeatYXUzUMx_moJseJ9o7b1RoLUf3o_PfOtn_aw
--Mount System & Vendor
6. flash Sound Fix (fixaudiogsi.zip) https://mega.nz/#!AD52wIhD!FM5GruKjw76gRnXqqLrh73CsSIZmldANlZrzyfVlcX0
7. flash DropVendorLightHAL.zip https://mega.nz/#!QKgVxaCI!lJuYDA2HjpP8msTbB7uXzW5jlvHImmHBtjjAdjt5R5g
8. flash DisableForceEncryption_Treble_v20.1.zip https://mega.nz/#!BHgRWYDS!jfuIRqTPTjS_lVy2tfpSbVRfqmxqqadeLFttgbKmhYQ
Reboot
-Verify your MI Account.
1.connect your WiFi 2. input you mi password. ...wait
- Magisk manager add MIUI_Auto_Brightness_Fix_v4_(pie).zip
https://mega.nz/#F!hT5UkSAQ!VCiS_BVC0Jlobpo6EMLsDg
-install GMS.apk and reboot
Coming soon --- Fingerprint Fix
Click to expand...
Click to collapse
Hello, I installed this version, in <Additional Settings>, <Region>, it shows "CHINA" and I can't change to my "Brazil" region. How do I change?
evanderfreitas said:
Hello, I installed this version, in <Additional Settings>, <Region>, it shows "CHINA" and I can't change to my "Brazil" region. How do I change?
Click to expand...
Click to collapse
I don't think u can. But it doesn't change much anyway. I dont think it has Portuguese
Works well but..
That's the only rom i found that is smooth, and have dark mode
also the only one with Miui11 that support sdcard slot
So thanks a lot!! :good::good:
The only problem is that everything on the screen is too big, even if i reduce it with display settings or other settings.
Is there anything we can do ? Like flashing a zip with magisk that'll change that?
nabilrezki said:
That's the only rom i found that is smooth, and have dark mode
also the only one with Miui11 that support sdcard slot
So thanks a lot!! :good::good:
The only problem is that everything on the screen is too big, even if i reduce it with display settings or other settings.
Is there anything we can do ? Like flashing a zip with magisk that'll change that?
Click to expand...
Click to collapse
Just change dpi of the screen to 600 dp through developer settings
---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------
nizdi said:
Tom, thanks for everything you have done.
Only one question: when you fix fingerprint, will we have to flash whole system again or maybe only a part of it? Reading mode going to be fixed? (block blue light,useful to study)
thanks.
Edit:
@nirh216
Dude, in the bottom side, right side, there's a option to image file. click it, then choose the huge file (about 2gb) you donwloaded and flash it.
Edit2: Physical home button it's kinda useless to unlock right now, right? I cant see to use it even to unlock it, only as "home button". And i did not installed fix for auto brightness because mine is working, and i could not find how to install it by magisk, if anyone has atuto for it. thanks.
Edit3: 2 bugs I found. 1st Nav bar stop working after a while, needing to restart device to work. 2nd brightness from screen is definetly low, like half the bright from normal stock rom ----> I guess brightness is a problem from pocophone and about nav bar seems like tasker was fckng it up
Thanks.
Edit4: last edit lol. My twrp seems to be gone after doing every step and i cant find to install it again. you guys have twrp working?
Click to expand...
Click to collapse
No problem with twrp
Hi, when i reverted back to android 11 from android 12 beta 1 my play store system update is stuck on January patch. How do i get to the latest security patch? i've checked for update but nothing happens.
Is this after the June update? Mine is currently on May 1st after the June update. If unlocked I would try dirty flashing a full image. If locked, sideload the latest OTA via recovery.
I'm having the same issue since the first android 12 preview,when downgrading to android 11, google play system update stuck at January,i tried many ways but no luck.
Same here with Pixel 4
gm007 said:
I'm having the same issue since the first android 12 preview,when downgrading to android 11, google play system update stuck at January,i tried many ways but no luck.
Click to expand...
Click to collapse
Did you try flashing the full image and allowing a data wipe (fresh install). I'm guessing you tried dirty flashing it already. @2WildFirE
v12xke said:
Did you try flashing the full image and allowing a data wipe (fresh install). I'm guessing you tried dirty flashing it already. @2WildFirE
Click to expand...
Click to collapse
I said everything
I had to ask also in Google pixel community https://support.google.com/pixelpho...gle-play-system-update-stuck-at-january?hl=en
Yes I tried all tips, Google Support doesn't know to help.
It's an downgrade issue when come from 12
2WildFirE said:
Yes I tried all tips, Google Support doesn't know to help.
It's an downgrade issue when come from 12
Click to expand...
Click to collapse
When you reflash your phone using a full image, it wipes and formats your partitions, returning it to out of the box condition. That is the sole purpose of unlocking the bootloader and flashing a full factory image. There is nothing residual after flashing this way, so it cannot be a downgrade issue. I also agree the Google Pixel community is totally useless and laughable.
I suspect it is a server problem, it seems as if the pixels are still marked as beta and are therefore not getting an update.
2WildFirE said:
I suspect it is a server problem, it seems as if the pixels are still marked as beta and are therefore not getting an update.
Click to expand...
Click to collapse
I suspect people don't want to lose their data by properly wiping & restoring their phone to its factory state.
U don't know how often I did a full factory image flash.
But nothing worked!
v12xke said:
When you reflash your phone using a full image, it wipes and formats your partitions, returning it to out of the box condition. That is the sole purpose of unlocking the bootloader and flashing a full factory image. There is nothing residual after flashing this way, so it cannot be a downgrade issue. I also agree the Google Pixel community is totally useless and laughable.
Click to expand...
Click to collapse
I met the same issue with 4a5g. I tried flashing 5 times but issue still come. Google play services system update will automatically display 1 jan 2021 when i log in google account ( the account i was enroll to using android 12beta via OTA, but i've cancelled android 12beta)
I think issue need to be resolve by google or we can use other google account.
After opt in Android 12 Beta again, Google Play System Updates working on Android 12.
Today received the update from April to May
2WildFirE said:
After opt in Android 12 Beta again, Google Play System Updates working on Android 12.
Today received the update from April to May
Click to expand...
Click to collapse
So that mean, we need to enroll pilot update 12beta again via OTA or flashing, right?
2WildFirE said:
After opt in Android 12 Beta again, Google Play System Updates working on Android 12.
Today received the update from April to May
Click to expand...
Click to collapse
Strange how it is behind. I thought new beta versions came out after the general release so they could roll the new security release into the beta. This would mean A12 beta would also be current. But I also haven't been running the betas for a couple years. Interesting.
2WildFirE said:
After opt in Android 12 Beta again, Google Play System Updates working on Android 12.
Today received the update from April to May
Click to expand...
Click to collapse
Please share your solution with android 11.
Sorry mate, no solution for Android 11 yet.
Only works so with Android 12 Beta
So thinking if Android 12 goes out live for all, our problem is solved.
The solution on Android 11 is to simply install the "Main components" APK from APK mirror
It's basically you're just updating manually.
Main components APKs - APKMirror
Main components APKs - APKMirror Free and safe Android APK downloads
www.apkmirror.com
2WildFirE said:
Sorry mate, no solution for Android 11 yet.
Only works so with Android 12 Beta
So thinking if Android 12 goes out live for all, our problem is solved.
Click to expand...
Click to collapse
There is a solution check my post.
Alexisnotfrommars said:
There is a solution check my post.
Click to expand...
Click to collapse
This isn't a solution. It only change the date not more or less!