First, an editorial comment:
For the money this is a great device. Compare it to the Flagship Tab S7 ($650 Fall 2021 - 128GB) versus the Tab A7 at $180 (32GB with a few $ more for a MicroSD). It is quick, plenty of storage with the MicroSD, and about the right size.
But my Rooted Tab A7 (via Magisk) kept bugging me about updating. It even started restarting in an effort to update itself.
I spent way too long yesterday reading instructions for updating to Android 11. It seems that everyone wanted to make it harder than it needed to be.
It isn't that difficult:
No loss of Data, apps, etc.
The details below have numerous steps, mostly for the unfamiliar. But there really are just three steps
Download the update
Use your existing Magisk installation to create a magisk-patched AP_T500
Flash it using Odin
DEVICE
Galaxy Tab A7 SM-T500, previously rooted with Magisk
Download Oden, the latest version. I used Odin3 v3.13.1_3B_PatcheD. https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
Download the Android 11 update. There are several ways to do this (Google it.) I found that the old standby, SamMobile lacked the latest update. I used https://samfrew.com/download/Galaxy__Tab__A7__-Wi-Fi-__/wte0/XAR/T500XXU3BUF3/T500OXM3BUF3/
Inside the ZIP file you'll find AP_T500XXU3BUF3_CL21871393_QB40910992_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS11.tar.md5
Move that to the Tablet. I put it in the root of the MicroSD card.
Open Magisk. Top Right, tap Install. Radial Button (put little black dot in circle) "Select and Patch a File"
{
"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"
}
Tab LET'S GO
Magisk puts the patched file in your Download Folder of your internal memory (the internal directory called "sdcard"
Move patched file magisk_patched-XXXXX_XXXX.tar to your computer (for convivence, the same folder as your unzipped SM-T500_1_20210617XXXXXX
Open Magisk and Turn off all your Magisk modules. (If your modules are all compatible with the version you're going to this is ok but mine were not which sent my tablet into a bootloop after the update)
Now unzip Oden, from step #1, into that same SM-T500_1_20210617XXXXXX folder (for convivence.)
Turn your Tablet OFF
Launch Odin
Boot to Download Mode - hold BOTH the VolumeUP and VolumeDOWN buttons down ans simultaniously plug in your Samsung USB-C , THAT IS ALREADY CONNECTED to the PC
Put the BL_T500XXU3BUF3_XXXXX???.md5 in the Odin BL, the HOME_CSC_OMC_OXM_T500OXM3BUF3_XXXXX???.md5 in the CSC and the magisk_patched-XXXXX_XXXX.tar in the AP
Tap the Tab Start
That should do it.
16. Open Magisk and uninstall the module and reinstall compatible modules
If you forget to turn off the Magisk modules and end up in a bootloop, hold the volume up button. The the tablet should go into Safe Mode which will cause magisk to disable all the modules. Manually reboot from Safe Mode
CREDITS
https://www.thecustomdroid.com/install-ota-update-rooted-android-device-guide/
https://forum.xda-developers.com/t/...-t860-without-wiping-data-using-odin.4250457/
I would have stayed with Q. Even Q is too restrictive with trusted apps, R went Apple wild.
There are reasons I don't want an Apple, Android is moving in the same lame direction trying to make a "safer" OS. Predictable and unacceptable.
Security was never an big issue for me when using Android... you just need to take out the trash.
My conclusion, you lose more than you gain with Android 11 and above.
Go ahead Gookill, prove me wrong...
if you can big sister☠
if i get this right, by flashing the new ota updatet firmware version with home_csc i will not get a fatory reset ?
Gianni_10 said:
if i get this right, by flashing the new ota updatet firmware version with home_csc i will not get a fatory reset ?
Click to expand...
Click to collapse
yes
Mister Monday said:
yes
Click to expand...
Click to collapse
but both firmware needed to be either non rooted or rooted right?
Gianni_10 said:
but both firmware needed to be either non rooted or rooted right?
Click to expand...
Click to collapse
No.
Related
I flashed cyanogenmod onto my Fire tablet 7 gen 5 and it all worked fine. However I decided to remove the trebuchet launcher to save space and it caused random crashes so I tried to use flashfire to reflash cyanogenmod and my device will get stuck on the boot screen(I left it on for a solid 15-20 minutes). The method I used to flash doesn't use TWRP and I couldn't get supertool to install TWRP(it would fail everytime) so I linked the picture of the recovery my device is using. Is my device bricked or is there any way to fix my device?
{
"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"
}
This is the picture if the link doesn't work
drive.google.com/open?id=0BydfdK3oLqJRTWhIUlcybElQdTQ
This is the method I used to flash cyanogenmod
reflectivecode.com/2016/03/installing-cyanogenmod-12-1-on-the-amazon-fire-2015/
berttheturt said:
I flashed cyanogenmod onto my Fire tablet 7 gen 5 and it all worked fine. However I decided to remove the trebuchet launcher to save space and it caused random crashes so I tried to use flashfire to reflash cyanogenmod and my device will get stuck on the boot screen(I left it on for a solid 15-20 minutes). The method I used to flash doesn't use TWRP and I couldn't get supertool to install TWRP(it would fail everytime) so I linked the picture of the recovery my device is using. Is my device bricked or is there any way to fix my device?
Click to expand...
Click to collapse
berttheturt said:
This is the picture if the link doesn't work
drive.google.com/open?id=0BydfdK3oLqJRTWhIUlcybElQdTQ
This is the method I used to flash cyanogenmod
reflectivecode.com/2016/03/installing-cyanogenmod-12-1-on-the-amazon-fire-2015/
Click to expand...
Click to collapse
Obsolete guidance. And no - you can't install TWRP on this device.
Reinstall FireOS 5.3.1 following guidance in this thread/video. Then return to this forum for instructions on how to root 5.3.1 and properly prepare device for the installation of a custom ROM. Once you have CM 12.1 working again think twice about removing trebuchet (or any other system component) even if you prefer a different launcher. Those pesky system apps serve a purpose including fallbacks should something go wrong with user installed alternatives. If desired you can move just about any app (including most system apps) to a suitable SD card using Link2SD or similar tool that leverages symbolic links. The native Apps2SD functionally is a crap-shoot at best for reasons that are beyond the scope of this post.
As an aside, if you want GAaps don't go for anything larger than mini (nano recommended) due to limited free space in the system partition - regardless of ROM.
Thanks so much, that worked perfectly
Davey126 said:
Obsolete guidance. And no - you can't install TWRP on this device.
Reinstall FireOS 5.3.1 following guidance in this thread/video. Then return to this forum for instructions on how to root 5.3.1 and properly prepare device for the installation of a custom ROM. Once you have CM 12.1 working again think twice about removing trebuchet (or any other system component) even if you prefer a different launcher. Those pesky system apps serve a purpose including fallbacks should something go wrong with user installed alternatives. If desired you can move just about any app (including most system apps) to a suitable SD card using Link2SD or similar tool that leverages symbolic links. The native Apps2SD functionally is a crap-shoot at best for reasons that are beyond the scope of this post.
As an aside, if you want GAaps don't go for anything larger than mini (nano recommended) due to limited free space in the system partition - regardless of ROM.
Click to expand...
Click to collapse
Hi, this is my first time rooting and android phone, so please excuse me if this sounds like a dumb request. I've been going about this for almost 2 days and ran out of options. First off, here is what I'm using:
- Redmi S2
- Android 9
- Root: Yes, Magisk 20.4
- MIUI 11.0.2 stock (flashed after I wiped system data by accident before my first backup)
So, my issue is the following: whenever I try to install an app through google play or attempt to download a Magisk module, the system fails to do so. In particular, Google Play shows a "Storage is full, please remove any of these apps:" message, however, I have about 20GB left from my storage. I googled this plenty, and came up with this solution: https://forum.xda-developers.com/general/general/how-to-fix-insufficient-storage-t2855191, which says that I have to give access to the system user to the app-lib folder in order for things to install. However, when I check the permissions on this folder (and its subfolders) I can see that the permissions for them are already granted to the system, as can be seen here:
{
"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"
}
Besides that, I have cleared caches, wiped data storage and system, and reinstalled Magisk many many times since, but none of these have helped with this issue. Something to note here is that if I uninstall Magisk, I can download apps again. It is only when Magisk is installed that the system is unable to access the storage.
Please if someone has any idea on how to fix this I'd be the most thankful!
Possible solution
Jandresgomez said:
Hi, this is my first time rooting and android phone, so please excuse me if this sounds like a dumb request. I've been going about this for almost 2 days and ran out of options. First off, here is what I'm using:
- Redmi S2
- Android 9
- Root: Yes, Magisk 20.4
- MIUI 11.0.2 stock (flashed after I wiped system data by accident before my first backup)
So, my issue is the following: whenever I try to install an app through google play or attempt to download a Magisk module, the system fails to do so. In particular, Google Play shows a "Storage is full, please remove any of these apps:" message, however, I have about 20GB left from my storage. I googled this plenty, and came up with this solution: https://forum.xda-developers.com/general/general/how-to-fix-insufficient-storage-t2855191, which says that I have to give access to the system user to the app-lib folder in order for things to install. However, when I check the permissions on this folder (and its subfolders) I can see that the permissions for them are already granted to the system, as can be seen here:
Besides that, I have cleared caches, wiped data storage and system, and reinstalled Magisk many many times since, but none of these have helped with this issue. Something to note here is that if I uninstall Magisk, I can download apps again. It is only when Magisk is installed that the system is unable to access the storage.
Please if someone has any idea on how to fix this I'd be the most thankful!
Click to expand...
Click to collapse
I had the same problem 2 years ago. What I did was buy another phone (an iPhone). It didn't fix the problem, but a friend of mine was very happy. Strongly recommended.
XiaomiFixer69 said:
I had the same problem 2 years ago. What I did was buy another phone (an iPhone). It didn't fix the problem, but a friend of mine was very happy. Strongly recommended.
Click to expand...
Click to collapse
Stupid solution [emoji1787]
Enviado do meu ASUS_I001DC através do Tapatalk
{
"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"
}
- = Installing Project Treble ROM = -
ARM64-A/B
Preliminary requirements:
The bootloader should be unlocked on the phone, adb+fastboot drivers should be installed on PC.
Recommendations:
1. Install Project Treble firmware with already integrated GAPPs, because there is no fully-functional TWRP for this phone yet.
2. Or after installing firmware without GAPPs use this MAGISK GAPPs installer.
From personal experience. Of all the Project Treble ROM I've tried, on the interface, settings, functionality, I liked the Octavi-OS
Instruction from installing:
1. Archive Project_Treble_Install unzip to the folder with the same name at your convenience place.
2. Download your choice of Project Treble system image archive for the ARM64-AB architecture. Unzip it into the Project_Treble_Install folder and rename it to system.img.
3. Boot the phone into bootloader mode and connect it to the PC.
4. If this is your first time installing a Project Treble system image, you need to do the following:
a) Run the executive file 0_slot_pre-check.bat to determine the active slot where the device system is located.
- 1_flash_treble_slot-a - use this executable file if the slot was detected as current-slot: a (if the system was not updated via OTA or was installed using MotoFlashPro or other similar software)
- 2_flash_treble_slot-b.bat - use this executable file if the slot was detected as current-slot: b (if the system was updated via OTA);
5. 3_flash_treble_new.bat - use this executable file if you previously installed Project Treble image and want to flash some other one.
6. The device will be rebooted to fastbootd mode during installation.
7. When the installation is finished the device will automatically boot into the system. Make all necessary settings.
8. Warning! After the initial setup, perform the necessary steps with MAGISK as described HERE
Project Treble firmware topic: XDA
Say, with real GAPPS (not microG), did you get this "Uncertified Device" error (that prevents you from logging in to GMS)?
I recall seeing that error on another device after flashing GApps on top of phh-AOSP v304, and I think the issue started to happen at that point on since I never encountered the message before. Maybe because I was not using Magisk at that time... so not sure if Magisk (pre MagiskHide drop) might be taking care of it...
I tried the guide to register my device before, but it didn't really work at that time, either because it doesn't always work, or just it does not immediately take effect, so I gave up and used NanoDroid instead (which uses microG and never had that issue, and it has working IAP).
On the ROM with integrated GAPPs all is well - device is certified.
Just checked your script. I noticed the following:
1. Looks like you provided your own vendor.img. As I'm using Edge S Pro I'm not sure if this vendor.img is applicable. Also, does VoLTE work for you? My device with the stock (unmodified) Edge S Pro vendor can't get VoLTE working correctly at the moment (you can force it active but calls will hang).
2. According to the scripts, looks like you simply cleared the previous dynamic partitions and installed your vendor as well as the user provided GSI to slot A and set it to active (with different sets of commands depending on the user's currently active slot). While there's no problem in this, I'm curious about whether there is any underlying difference between the two "slots" in the context of dynamic partitions.
LSS4181 said:
1. Looks like you provided your own vendor.img. As I'm using Edge S Pro I'm not sure if this vendor.img is applicable.
Click to expand...
Click to collapse
Yes. Everything works great!
LSS4181 said:
2. According to the scripts, looks like you simply cleared the previous dynamic partitions and installed your vendor as well as the user provided GSI to slot A and set it to active (with different sets of commands depending on the user's currently active slot). While there's no problem in this, I'm curious about whether there is any underlying difference between the two "slots" in the context of dynamic partitions.
Click to expand...
Click to collapse
I don't like it when the system wastes a lot of extra disk space on the device. If you check the dynamic partition sizes of both slots in fastbootd mode, you will understand. In essence there is no difference, but why should this unnecessary garbage eat up the disk space of a device which has no SD Card support?
LSS4181 said:
Also, does VoLTE work for you?
Click to expand...
Click to collapse
I don't use this function.
Hi I have a question, How can I port the default camera ?
hello greetings, I have a big problem I followed this guide to install rom gsi and my moto edge 20 pro is dead, the device manager recognizes it in edl mode and tried with the blank flash of version 19.50 and it gives me an error, help please
Hello friends!
I bought the Red Magic 3S. It has firmware from the Chinese version V5.17 and Android 11. I don't have Google play or Google Services. It also did not receive notification in most apps. I would like to know where to start, sorry for the bad english
As per "courtesy" a Senior Moderator translated your post, I encourage you to use a translator to use the English language in your later posts
Im in the same situation, installed the chinese version through system update. Updated chinese version to Android 11 V5.17. Installed TWRP with adb with bootloader and then also installed magisk through TWRP Recovery adb sideload but cannot install gapps pico it says error 70, when I googled that it means that theres not enough system storage to install gapps. I've deleted some of the original bloatware with magisk debloater and still has no space. I'm beginning to think that it is due to system being encrypted and twrp thinks theres no space to installed. Have tried removing screen lock still didn't work. Under settings security we can find were phone says encrypted I just have to figure out how yo decrypt. Maybe something nubia did to prevent us from rooting?
Try installing Google packages through the app called "HiGoPlay". You will find this app in the app center store
{
"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"
}
juan_carlos__007 said:
Im in the same situation, installed the chinese version through system update. Updated chinese version to Android 11 V5.17. Installed TWRP with adb with bootloader and then also installed magisk through TWRP Recovery adb sideload but cannot install gapps pico it says error 70, when I googled that it means that theres not enough system storage to install gapps. I've deleted some of the original bloatware with magisk debloater and still has no space. I'm beginning to think that it is due to system being encrypted and twrp thinks theres no space to installed. Have tried removing screen lock still didn't work. Under settings security we can find were phone says encrypted I just have to figure out how yo decrypt. Maybe something nubia did to prevent us from rooting?
Click to expand...
Click to collapse
In my case, I still haven't done any procedure, like unlocking the bootload, twrp, root, etc. But with you it can work!
if u still need help dm me
To install Оpen GApps pico on 11 android v5.17, you need to delete the folder nubia_Browser, it is in the folder app, this browser still needs to be removed so that it does not redirect to the Chinese store, you will have 100 mb of free space and twrp will not give an error that there is not enough free space.
https://sourceforge.net/projects/opengapps/files/arm64/20220503/open_gapps-arm64-11.0-pico-20220503.zip/download
Before installing google services, you need to remove all types of locks on your phone and put one pin code lock, then when you load it into the system, Google will ask for a pin code, then fingerprints: write your own pin code, fingerprints must be skipped!
Installing gapps pico:
1. You must be root!
2. reboot into twrp-3.3.1-4-NX629J-mauronofrio
3. click: settings
4. click: reset settings
5. go: extra
6. push: explorer
7. choose: system_root
8. choose: system
9. choose: app
10. find: nubia_Browser and other programs I threw off screenshots
11. in the lower right corner, click on the folder with a checkmark
12. click on: delete button
13. flash open gapps pico from phone memory or flash drive
14. reboot into the system.
15. optional: download Browser V7.3.5.2022091518a.zip, unzip and install browser apk.
SDCARD TRANSCRIPT:
The phone must be rooted with twrp-3.3.1-4-NX629J-mauronofrio installed!
1. In TWRP clear: Dalvik/ART Cache, Cache, Data, Device Memory
2. Reboot your phone in twrp
3. With flash drive install magisk Magisk-25.2(25200).zip
4. Reboot into the system.
5. Install Magisk 25.2.apk
{
"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"
}
Disclaimer
I am NOT responsible for bricked devices, dead SD cards or any
damage to you device. You are doing this at YOUR OWN RISKS. It's
reccomended to do a full SYSTEM BACKUP in case something went wrong.
Features
Tweaked with Build.prop for better experience
Deodexed for easy system apps modifications
DeKnoxed to remove annoying settings
Decrypted for keeping data when performing system changes trough TWRP of CWM recovery
Pre Rooted with Magisk to get superuser access and for some interesting advantages
Many others features coming from stock Oreo ROM
Busybox added to xbin
How to install
First of all, make sure you have downloaded the ROM flashable zip (Download link in bottom of this post)
Put the zip file in your phone storage or SD card if not already in
Reboot in custom recovery such as TWRP or CWM with hardware buttons (if not installed, this is a Tutorial)
Go to WIPE section and select advanced wipe
wipe Data, System, Preload, Cache-Dalvik, Cache and Internal Storage (I highly recommend to do a full backup of your ROM BEFORE WIPING)
Now, go back to home and to INSTALL section
Select storage where the ROM zip is stored and choose it
Start the operation with -zip signature check- unchecked or it will fail
If everything goes well, reboot to system and after booted, complete the setup wizard
That's it
Devices supported
Samsung Galaxy A5 2017 (SM-A520W) the one which i have tested (works fine)
Maybe F, K, L and S variants (Tell me if it works please)
Not for DS (dual sim) versions and Snapdragon
Requirements
A computer (for custom recovery flash)
Latest Oreo bootloader unlocked (developpers options from settings)
SD card (at least 4Gb)
Internet connection
A minimum of knowledge in Samsung phones
TWRP/CWM/OrangeFox recovery installed
Downloads
flashable rom zip file---------- N'CreamOS_8.0_v2_a5y17lte
Thanks to
AndroDef------ For his helpfull Classy Kitchen XDA Link
Topjohnwu------ For his irreplacable Magisk Root Magisk Github
sfirmware.com------ For the stock TAR.MD5 file SM-A520W(XAC)
If you see some bugs, please inform me
its just like samsung experience, i relly like it )
It is working fine on my Galaxy A520F Exynos Model, so you can check that out from the compat. checklist. For some reason the os thinks this is a A520W, but this is a F Model. I had a problem where TWRP said that flashing failed with error 7, but then I restarted it and I flashed it and it worked. Also you actually don't need a SD Card for the flasheble zip, you can actually just turn MTP on and Mount the DATA partition and copy the zip from your computer to your phone. This ROM is pretty good!
Oops, wrong post.