Related
Might be a weird one but I did followed the instructions to install CM9 Alpha 2 but when I go into moboot, there is no Android option there?
The options I get are- boot WebOS, boot clickworkmod,boot web OS mod, reboot, shut-down
Any help would be appreciated.
Thanks
Looks like cyanogenmod alpha 2 didn't get installed by the acmeinstaller.
Choose clockworkmod when you boot up, you will get a menu, use the volume keys and the home button to select "install zip from SD", you should see your files, you need to have the rom file on the touchpad, it will be called something like cyanogenmod9alpha2.zip, select it and install it, once its done choose reboot, your menu should now have a cyanogenmod option.
First of all, a big thankx to S10+ Thread members who've helped me to root and install twrp on the device. Without your help i couldn't have done it.
Secondly, i've installed the December security patch firmware. Now its been rooted with magisk and a twrp installed. So i was thinking to upgrade to January patch. But i am afraid, it would affect the rooted state or replace the twrp.
Is there any way to upgrade without losing current status and data on the device ?
No easy way. Pre patched firmware then flash pre patched twrp
but no TWRP
sunmughans said:
Is there any way to upgrade without losing current status and data on the device ?
Click to expand...
Click to collapse
Firmware updates and keeping your data, for phones Magisk rooted without TWRP.
https://forum.xda-developers.com/showpost.php?p=80076303&postcount=1436
Just download new firmware, copy the AP file of the new firmware to your phone.
Open Magisk Manager, ensure Magisk is up to date, if not, update it.
When Magisk is up to date, if you have any Magisk Modules running, go into Modules and disable them (no need to uninstall them). Then reboot and go back into Magisk Manager.
Hit the _top_ INSTALL, select INSTALL again then select 'Select and Patch a File'
Locate the new AP file from your new firmware and patch it. Then copy the *magisk_patched.tar* (find it in /sdcard/Download - do not forget to delete it here after everything is done; otherwise Magisk will choke on the next patch) back to your computer, preferably with adb pull to minimize corruption during transfer.
Power off phone and reboot to *Download mode* (switch off, Vol-Down + Bixby and plug USB cable).
Open Odin 3.13.1 or later on your computer, and deselect Reboot under Options tab.
Now use the new magisk_patched file in the AP slot, the BL and CP from your new firmware into their respective slots and importantly *HOME_CSC* into the CSC slot.
Press start and let Odin do it's stuff.
When flashed, do not wipe.
Press and hold Vol-down and Power, when screen goes off, quickly change to Vol-up, Bixby button and Power.
As soon as screen appears, let go of all buttons.
Within moments without any further user intervention your phone will reboot into your updated Magisk rooted mode, data intact.
Just re-enable your previously disabled Magisk modules.
This is the original work of:
Last edited by @robbo1947; 2019-08-30 at 04:28.
(only copied here because this useful stuff is buried in a long thread - follow the link on the second line)
last edited by me 2019-10-05
DHGE said:
Firmware updates and keeping your data, for phones Magisk rooted without TWRP.
https://forum.xda-developers.com/showpost.php?p=80076303&postcount=1436
Just download new firmware, copy the AP file of the new firmware to your phone.
Open Magisk Manager, ensure Magisk is up to date, if not, update it.
When Magisk is up to date, if you have any Magisk Modules running, go into Modules and disable them (no need to uninstall them). Then reboot and go back into Magisk Manager.
Hit the _top_ INSTALL, select INSTALL again then select 'Select and Patch a File'
Locate the new AP file from your new firmware and patch it. Then copy the *magisk_patched.tar* (find it in /sdcard/Download - do not forget to delete it here after everything is done; otherwise Magisk will choke on the next patch) back to your computer, preferably with adb pull to minimize corruption during transfer.
Power off phone and reboot to *Download mode* (switch off, Vol-Down + Bixby and plug USB cable).
Open Odin 3.13.1 or later on your computer, and deselect Reboot under Options tab.
Now use the new magisk_patched file in the AP slot, the BL and CP from your new firmware into their respective slots and importantly *HOME_CSC* into the CSC slot.
Press start and let Odin do it's stuff.
When flashed, do not wipe.
Press and hold Vol-down and Power, when screen goes off, quickly change to Vol-up, Bixby button and Power.
As soon as screen appears, let go of all buttons.
Within moments without any further user intervention your phone will reboot into your updated Magisk rooted mode, data intact.
Just re-enable your previously disabled Magisk modules.
Last edited by @robbo1947; 2019-08-30 at 04:28.
last edited by me2019-10-05
Click to expand...
Click to collapse
Thank you so much bro! You really saved a lot of time. I will follow your instructions.
sunmughans said:
Thank you so much bro! You really saved a lot of time. I will follow your instructions.
Click to expand...
Click to collapse
Don't forget to thank me, I wrote the original instructions !!.
https://forum.xda-developers.com/ga...s10-series-t3918699/post80076303#post80076303
Did not work for me(root&twrp), phone is required to reset, however with backup, data can be restored. So backup your data before update.
DHGE said:
When flashed, do not wipe
Click to expand...
Click to collapse
what do you mean by that?
@topjohnwu has left xda due to some reasons.
but before that, he also fixed the bootloop problem.
if you already in the version 19.3, guided by @redymedan, update to new v20.4 by the beta channel...
it works in ata6 build for me, but i can't risk my data again to test on android q.
update: i tried on android q bit it didn't work. welp, back to 9 i guess.
halcyon441 said:
@topjohnwu has left xda due to some reasons.
but before that, he also fixed the bootloop problem.
if you already in the version 19.3, guided by @redymedan, update to new v20.4 by the beta channel...
it works in ata6 build for me, but i can't risk my data again to test on android q.
Click to expand...
Click to collapse
I have tested Magisk v20.4 and facing same problem with magisk v20.3, I tried to fix it:
1. Boot system without magisk
2. Clear magisk data/cache ( don't run magisk after clear data/cache, just turn power off )
3. Boot system with magisk
redymedan said:
I have tested Magisk v20.4 and facing same problem with magisk v20.3, I tried to fix it:
1. Boot system without magisk
2. Clear magisk data/cache ( don't run magisk after clear data/cache, just turn power off )
3. Boot system with magisk
Click to expand...
Click to collapse
on android Q?
[update 2] hey folks, after a day testing and stuff, even mess up my sd card with more than 15gb data in it (rip my "homework n stuff"), i had decided that stay in android 9 would be better. Magisk v20.4 COULD works in android 10, but can't do initial setup thingy, so you can't install modules., try to delete MM data and it won't work, conflict with OneDrive maybe.
backup your data, unlock the bootloader and unlock OEM.
open your MM, choose beta channel and refresh, you'll see v20.4 (20400)
copy AP files ( ata6 recommend), to your phone.
select "patch a file", choose the AP files and let the MM do it jobs.
after MM done patching, connect your phone with PC.
open File Explorer, accept permission, copy magisk_patched.tar to your pc.
to Odin, UNTICK THE "AUTO REBOOT" and KEEP "F.RESET TIME"
choose bl file for bl
magisk_patched.tar for ap
cp for cp
and note this: if you choose csc file in csc, you will mess up. your phone will be shrink from 64gb to 16gb.
home_csc for csc.
click start and wait...
after 2 minutes or less, odin will say "PASS".
next step will be hard, buy some coffee for
concentrate in pressing buttons (lol)
press volume down and power for more 7s, when screen blank, use 50% of your mana and press both volume up and power.
when samsung text appear, hold till it pass the bootloader warning, after that, only keep the volume up.
after a few secs, you will see text "erasing" and the screen will eventually blank again.
continue the process, do as above, and keep the volume up button to enter recovery mode.
wipe all data&factory reset.
choose the "reboot system now", when the screen blank, immediately hold both power up and power until it passes the bootloader warning.
the first time it boot, it won't boot to os but instead it will reboot again, dont panic, just stay at natural.
wait...
do setup, PLEASE NOTE THAT DO NOT CONNECT WIFI IN SETUP OR ELSE YOU WILL GET IN BOOTLOOP.
after setup, you can connect to wifi.
go to MM to do initial setup, and done.
feel free to restore your data, install modules, block ads,...
halcyon441 said:
[update 2] hey folks, after a day testing and stuff, even mess up my sd card with more than 15gb data in it (rip my "homework n stuff"), i had decided that stay in android 9 would be better. Magisk v20.4 COULD works in android 10, but can't do initial setup thingy, so you can't install modules., try to delete MM data and it won't work, conflict with OneDrive maybe.
backup your data, unlock the bootloader and unlock OEM.
open your MM, choose beta channel and refresh, you'll see v20.4 (20400)
copy AP files ( ata6 recommend), to your phone.
select "patch a file", choose the AP files and let the MM do it jobs.
after MM done patching, connect your phone with PC.
open File Explorer, accept permission, copy magisk_patched.tar to your pc.
to Odin, UNTICK THE "AUTO REBOOT" and KEEP "F.RESET TIME"
choose bl file for bl
magisk_patched.tar for ap
cp for cp
and note this: if you choose csc file in csc, you will mess up. your phone will be shrink from 64gb to 16gb.
home_csc for csc.
click start and wait...
after 2 minutes or less, odin will say "PASS".
next step will be hard, buy some coffee for
concentrate in pressing buttons (lol)
press volume down and power for more 7s, when screen blank, use 50% of your mana and press both volume up and power.
when samsung text appear, hold till it pass the bootloader warning, after that, only keep the volume up.
after a few secs, you will see text "erasing" and the screen will eventually blank again.
continue the process, do as above, and keep the volume up button to enter recovery mode.
wipe all data&factory reset.
choose the "reboot system now", when the screen blank, immediately hold both power up and power until it passes the bootloader warning.
the first time it boot, it won't boot to os but instead it will reboot again, dont panic, just stay at natural.
wait...
do setup, PLEASE NOTE THAT DO NOT CONNECT WIFI IN SETUP OR ELSE YOU WILL GET IN BOOTLOOP.
after setup, you can connect to wifi.
go to MM to do initial setup, and done.
feel free to restore your data, install modules, block ads,...
Click to expand...
Click to collapse
has anyone been able to successfully root on Q? on which firmware? I have tried this endless times on 4BTB4 firmware but always getting bootloop before I can even complete initial android setup.
kamwash said:
has anyone been able to successfully root on Q? on which firmware? I have tried this endless times on 4BTB4 firmware but always getting bootloop before I can even complete initial android setup.
Click to expand...
Click to collapse
Ive succesfully root it
nikkali25 said:
Ive succesfully root it
Click to expand...
Click to collapse
what firmware version do you have?
nikkali25 said:
Ive succesfully root it
Click to expand...
Click to collapse
Btb4
First of all, the download link of all the files required for this "ROM" is taken from the "xda developers forum" posts.
I was constantly experimenting with GSI roms for Redmi 8. I was able to install the Pixel ROM on Redmi 8. I don't think you will have a problem if you follow the steps I shared with you one by one.
I do not take responsibility for the ROM. RESPONSIBILITY IS ENTIRELY YOURS.
Not working
-Face unlock
-Radio
-VoLTE
(You need to make a setting for the camera, notch, LTE Mobile Network and auto-brightness. I told you how to make the settings.)
NOTE: A computer is required to make this ROM setup. It must also be installed in ADB on your computer.
Note: You can install this ROM Google Camera as apk. Unfortunately, there are no features such as Portrait, night mode in the original camera application of the device. However, you can use it if you install it as an apk.
Please download that files:
Download - Pixel Experience ROM GSI file
Download --- Sky Hawk Recovery file
Download - Permissiver V5
Download -Certification Patch for Redmi 8
Download -Treble overlay for Redmi 8
Download --- Lastest Magisk-v20.4
Here -Get the TWRP Official for Redmi 8
Download - vbmeta.img
Note: Please charge your phone at least 60%
First, take the necessary backups as your phone will be completely reset.
1- Unlock your bootloader. For unlocking follow this: http://en.miui.com/unlock/
2- Copy all the files to your SD Card (PixelExperience_ARM64AB-10.0-20200118-2138-GSI.img, SHRP_v2.2.zip, Permissiver_v5.zip, Certification_Patch.zip, Magisk-v20.4.zip, treble-overlay-xiaomi-redmi8.apk)
3-Enable USB debugging. Connect the phone your computer Then copy the twrp.img and vbmeta.img files to the adb folder.
Note: If the name of your twrp file is not twrp.img, please set its name to twrp.img.
4- Go to your computer, open adb folder in cmd, write that:
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot flash vbmeta vbmeta.img
5- Now we will go to the restart phone command. At that moment, you should quickly hold down the volume up key and power button of your phone. Enter this command:
fastboot reboot
Then, hold down the power button with quick boost and turn on twrp.
6- Install Magisk-v20.4.zip in twrp.
Then restart the phone. After the phone reboots, check if Magisk is installed. Once you see it installed, reboot the phone in recovery mode.
7- Install SHRP_v2.2_olive.zip then reboot recovery.
8- Now find the wipe button and tap it. Then press the format data and confirm by typing yes.
9- Then tap wipe again and click on the wipe button at the bottom right.
10- Tap the wipe again and tap on advanced wipe. Select the Dalvik, data, cache, system partitions and reset them.
11- Now return to the main menu screen and tap flash. Select your SD card in the lower right section and tap the PixelExperience_ARM64AB-10.0-20200118-2138-GSI.img file. Then select it as system image and install it.
12- Return to the main menu and come to the flash section and install the file Permissiver_v5.zip.
13- Then go back to the flash section and install the Certification_Patch.zip file.
14- Return to the main menu, tap wipe and complete the wipe from the button on the bottom right.
15- Reboot the system. Your device will either boot in fastboot mode or be bootloop. (If you see it open normally and no problems occur, you can skip step 18.)
16- Go to fastboot mode.
17- Connect the phone to the computer and open the adb folder on cmd. Type:
fastboot flash recovery twrp.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
The phone will reboot and turn on. Please set up the phone and turn USB debugging back on.
18- After doing setup and enabling usb debugging, reboot to recovery mode and install magisk.zip. Then reboot the phone.
19- Install build prop editor(https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en&pli=1) and root browser(https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree&hl=en) from the Play Store.
20- Open root browser and allow root access then go to your SD card and find treble-overlay-xiaomi-redmi8.apk
21- Copy to treble-overlay-xiaomi-redmi8.apk on Root Directory/system/overlay/ folder.
22- Select treble-overlay-xiaomi-redmi8.apk file on overlay folder and tap the three dots in the top right and tap the properties.
23- Click on the Permissions at the top bar.
24- Select like this photo (link: https://lh3.googleusercontent.com/p...VrSOGT_V9Q2bzgy5IuE9nIfPslILJ1Vz=w429-h904-no ) and click apply then reboot system.
25- Open the build prop editor and allow root access. then tap the 3 dots in the upper right and tap new.
name= persist.camera.HAL3.enabled
value= 1
Set it to and save it. Restart the system.
26- Go to the dialer and dial *#*#4636#*#*. Tap Phone information and set "set preffered network type: LTE only." Then reboot system.
27- Finally, if you want to fix the appearance of the screen notch go to
developer settings >> display cutout and select corner cutout.
That was it. Please note that I am not a developer, so I cannot resolve any errors. I believe that if you apply them like me, you won't have a problem. I will be waiting for your comments. Have a nice day.
I´ll give it a try in my wife´s redmi 8, cus I had tried to flash a bunch of roms in that device and I had not success. Thanks
dngr.fun said:
I´ll give it a try in my wife´s redmi 8, cus I had tried to flash a bunch of roms in that device and I had not success. Thanks
Click to expand...
Click to collapse
You're welcome. If you encounter any problems, please let me know. If you follow what I wrote under normal conditions step by step, you won't have a problem.
Query before flashing
Hello Boss,
on checking the system by "Treble Check" app, it is showing that it is A-type System partition. And the ROM you suggested is AB type. Is there any thing i should worry about before flashing.
I am currently using Lineage OS (unofficial), and following functions doesn't work on it.
Finger print
VOLTE
Radio
face unlock
What about this ROM functionality.
hrwt20 said:
Hello Boss,
on checking the system by "Treble Check" app, it is showing that it is A-type System partition. And the ROM you suggested is AB type. Is there any thing i should worry about before flashing.
I am currently using Lineage OS (unofficial), and following functions doesn't work on it.
Finger print
VOLTE
Radio
face unlock
What about this ROM functionality.
Click to expand...
Click to collapse
At first I tried installing A-only on my device but it didn't work. It worked when I installed A / B. So please try A / B GSI. Because the device you have is probably A / B, not A-Only.
Finger print is working and face unlock is not have in Pixel Experience ROM.
VOLTE and Radio is not working bro.
I will list all the features that work by edit the post today or tommorrow bro
Certification_patch.zip
Whats the use for certification_patch.zip file?
Does it fixes the certification status in google play store?
Also, Can this file be used in any othe gsi too?
coolboyforeva said:
Whats the use for certification_patch.zip file?
Does it fixes the certification status in google play store?
Also, Can this file be used in any othe gsi too?
Click to expand...
Click to collapse
This file exists to integrate the model of the device into rom. I don't know much about google play and you can also install this and permissiver_v5 with other gsi roms. These only for Redmi 8.
hrwt20 said:
Hello Boss,
on checking the system by "Treble Check" app, it is showing that it is A-type System partition. And the ROM you suggested is AB type. Is there any thing i should worry about before flashing.
I am currently using Lineage OS (unofficial), and following functions doesn't work on it.
Finger print
VOLTE
Radio
face unlock
What about this ROM functionality.
Click to expand...
Click to collapse
Before system-as-root was used only on A/B devices but now all devices that ship with Android 9 must use system-as-root. Because of this reason you need to flash A/B roms on A-Only on these devices. As you can see from this page's device list, Redmi 8's image type is A/B so you need to flash an A/B image: https://github.com/phhusson/treble_experimentations/wiki
Does the sensor work? I tried other gsi and custom roms and sensors like accelerometer doesnt work..
Abdul Aziz Shakib said:
Does the sensor work? I tried other gsi and custom roms and sensors like accelerometer doesnt work..
Click to expand...
Click to collapse
All sensors working
i tried it and the sensors didn't work. i needed to flash stock rom and then pixel rom over the stock rom to get it work. seems logical, had no issue so far except the camcorder. when i record a video, lets say i recorded a video for 10 second. but when i play the video, it becomes 1hour video and the sound doesn't sync with the video. video stays frozen the whole time and plays normally at the last few seconds. i tried other gsi and had the same issue. is something wrong? any known solution? are you facing the same problem? if not, then which camera app you are using? thanks in advance because pixel experience is working now after following ur steps
Yes, there is a problem in this regard. Unfortunately, I could not solve this problem. I usually use Instagram cam for video. You can try bro
Abdul Aziz Shakib said:
i tried it and the sensors didn't work. i needed to flash stock rom and then pixel rom over the stock rom to get it work. seems logical, had no issue so far except the camcorder. when i record a video, lets say i recorded a video for 10 second. but when i play the video, it becomes 1hour video and the sound doesn't sync with the video. video stays frozen the whole time and plays normally at the last few seconds. i tried other gsi and had the same issue. is something wrong? any known solution? are you facing the same problem? if not, then which camera app you are using? thanks in advance because pixel experience is working now after following ur steps
Click to expand...
Click to collapse
I use havocOs gsi. It has same problem. Solution:
1. record a video.
2. do not close camera app.
3. open video from the camera app not from gallery.
4. play the video once.
if that plays then you can open that same video from any app.
try that, might work.
kouseralamin said:
I use havocOs gsi. It has same problem. Solution:
1. record a video.
2. do not close camera app.
3. open video from the camera app not from gallery.
4. play the video once.
if that plays then you can open that same video from any app.
try that, might work.
Click to expand...
Click to collapse
it works sometimes but not always.. Currently I am using Havoc OS and it doesn't have a gallery app. So I downloaded "Gallery Go" from playstore and when I try to open the video from the camera app, it opens with gallery go app.
to be noted, i have added some commands in build.prop..
media.camera.ts.monotonic=0
debug.stagefright.ccodec=0
persist.camera.HAL3.enabled=1
i don't know what these do but these commands were mentioned somewhere to enable camera2api..
am i missing something?
kouseralamin said:
I use havocOs gsi. It has same problem. Solution:
1. record a video.
2. do not close camera app.
3. open video from the camera app not from gallery.
4. play the video once.
if that plays then you can open that same video from any app.
try that, might work.
Click to expand...
Click to collapse
try this for video recording , go to phh treble settings, go to Misc, go to camera force timestamp, clock boottime
Redmi 4A abdal said:
try this for video recording , go to phh treble settings, go to Misc, go to camera force timestamp, clock boottime
Click to expand...
Click to collapse
Thanks, I tried it in the havocOs and it is fully ok now.
Hello, is Bluetooth audio working?
Is there an option for internet speed indicator on this rom?
IS TBH
sessionid0 said:
First of all, the download link of all the files required for this "ROM" is taken from the "xda developers forum" posts.
I was constantly experimenting with GSI roms for Redmi 8. I was able to install the Pixel ROM on Redmi 8. I don't think you will have a problem if you follow the steps I shared with you one by one.
I do not take responsibility for the ROM. RESPONSIBILITY IS ENTIRELY YOURS.
Not working
-Face unlock
-Radio
-VoLTE
(You need to make a setting for the camera, notch, LTE Mobile Network and auto-brightness. I told you how to make the settings.)
NOTE: A computer is required to make this ROM setup. It must also be installed in ADB on your computer.
Note: You can install this ROM Google Camera as apk. Unfortunately, there are no features such as Portrait, night mode in the original camera application of the device. However, you can use it if you install it as an apk.
Please download that files:
Download - Pixel Experience ROM GSI file
Download --- Sky Hawk Recovery file
Download - Permissiver V5
Download -Certification Patch for Redmi 8
Download -Treble overlay for Redmi 8
Download --- Lastest Magisk-v20.4
Here -Get the TWRP Official for Redmi 8
Download - vbmeta.img
Note: Please charge your phone at least 60%
First, take the necessary backups as your phone will be completely reset.
1- Unlock your bootloader. For unlocking follow this: http://en.miui.com/unlock/
2- Copy all the files to your SD Card (PixelExperience_ARM64AB-10.0-20200118-2138-GSI.img, SHRP_v2.2.zip, Permissiver_v5.zip, Certification_Patch.zip, Magisk-v20.4.zip, treble-overlay-xiaomi-redmi8.apk)
3-Enable USB debugging. Connect the phone your computer Then copy the twrp.img and vbmeta.img files to the adb folder.
Note: If the name of your twrp file is not twrp.img, please set its name to twrp.img.
4- Go to your computer, open adb folder in cmd, write that:
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot flash vbmeta vbmeta.img
5- Now we will go to the restart phone command. At that moment, you should quickly hold down the volume up key and power button of your phone. Enter this command:
fastboot reboot
Then, hold down the power button with quick boost and turn on twrp.
6- Install Magisk-v20.4.zip in twrp.
Then restart the phone. After the phone reboots, check if Magisk is installed. Once you see it installed, reboot the phone in recovery mode.
7- Install SHRP_v2.2_olive.zip then reboot recovery.
8- Now find the wipe button and tap it. Then press the format data and confirm by typing yes.
9- Then tap wipe again and click on the wipe button at the bottom right.
10- Tap the wipe again and tap on advanced wipe. Select the Dalvik, data, cache, system partitions and reset them.
11- Now return to the main menu screen and tap flash. Select your SD card in the lower right section and tap the PixelExperience_ARM64AB-10.0-20200118-2138-GSI.img file. Then select it as system image and install it.
12- Return to the main menu and come to the flash section and install the file Permissiver_v5.zip.
13- Then go back to the flash section and install the Certification_Patch.zip file.
14- Return to the main menu, tap wipe and complete the wipe from the button on the bottom right.
15- Reboot the system. Your device will either boot in fastboot mode or be bootloop. (If you see it open normally and no problems occur, you can skip step 18.)
16- Go to fastboot mode.
17- Connect the phone to the computer and open the adb folder on cmd. Type:
fastboot flash recovery twrp.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
The phone will reboot and turn on. Please set up the phone and turn USB debugging back on.
18- After doing setup and enabling usb debugging, reboot to recovery mode and install magisk.zip. Then reboot the phone.
19- Install build prop editor(https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en&pli=1) and root browser(https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree&hl=en) from the Play Store.
20- Open root browser and allow root access then go to your SD card and find treble-overlay-xiaomi-redmi8.apk
21- Copy to treble-overlay-xiaomi-redmi8.apk on Root Directory/system/overlay/ folder.
22- Select treble-overlay-xiaomi-redmi8.apk file on overlay folder and tap the three dots in the top right and tap the properties.
23- Click on the Permissions at the top bar.
24- Select like this photo (link: https://lh3.googleusercontent.com/p...VrSOGT_V9Q2bzgy5IuE9nIfPslILJ1Vz=w429-h904-no ) and click apply then reboot system.
25- Open the build prop editor and allow root access. then tap the 3 dots in the upper right and tap new.
name= persist.camera.HAL3.enabled
value= 1
Set it to and save it. Restart the system.
26- Go to the dialer and dial *#*#4636#*#*. Tap Phone information and set "set preffered network type: LTE only." Then reboot system.
27- Finally, if you want to fix the appearance of the screen notch go to
developer settings >> display cutout and select corner cutout.
That was it. Please note that I am not a developer, so I cannot resolve any errors. I believe that if you apply them like me, you won't have a problem. I will be waiting for your comments. Have a nice day.
Click to expand...
Click to collapse
Is there a way to flash it without SD card???my adb sideloader also doesnt open
I will try it tank you
Hello!
So recently I was able to install LineageOS 18.1 (GSI) + GApps on my Samsung Galaxy Tab A 8 (SM-T290) tablet and wanted to share how I did it. I noticed a lack of decent step-by-step guides to modding this tablet so I figure I'd share what I learned through scouring multiple threads and through multiple headaches. Fun fact: I also got this working with LineageOS 19 (GSI), however it ran pretty poorly and Android 12 is ugly as hell so why bother anyway? ALSO interestingly enough, you'll see I wrote [SM-T290N] in the title as well. That is the model of the Kid's Edition of this phone, which happens to be the one I had. So I can confirm this process works for the Kid's Edition of this tablet as well as the original.
Some Things To Note
Below I'll list the software/firmware I used in this process. You don't necessarily need to follow this exactly but I don't see any reason not to. The end result is a working install of LineageOS with GApps so if that's what you want I would just follow along step-by-step. ALSO I'm writing this from memory so if I make a mistake please let me know and I'll try and correct it.
Click to expand...
Click to collapse
What You'll Need
Your tablet
A USB Cable to connect your tablet to your PC
A 4GB+ MicroSD card
A Windows PC
Some patience
Instructions
Preparing Your MicroSD Card
1. Place the LineageOS 18.1 .img file from this thread (On SourceForge, there is a section below the files about the naming conventions and how they relate to the hardware of your device and configuration of your ROM. I used the lineage-18.1-20220315-UNOFFICIAL-arm64_bvS-vndklite.img.xz image for my device. If your device is slightly different, you can use Treble Info to determine what ROM you should use. Just make sure to use the VNDKLITE rom if your device supports it.
2. Place the multidisabler .zip folder on there as well. This will preserve encryption provided by TWRP after rebooting.
3. Finally, place the MindTheGapps .zip folder on your SD card (make sure to get the correct version. In my case this was the 11.00-arm64 version).
4. Insert your MicroSD card into your device.
Unlocking the Bootloader
So the first thing you're gonna want to do is unlock your OEM bootloader on your Samsung device.
1. Go to Settings->About Phone->Software Information and look for a field called "Build Number". Tap this Five Times until you see a notification saying developer settings were enabled.
2. Go to Settings->Developer Settings and look for the setting labeled OEM Unlock and turn it on.
If you don't see this setting try connecting to wifi, changing your date and time to around two months prior (I set mine to back to May 2021 since the firmware I was using was set in July 2021), then go back to your developer settings and switch them off and back on again. You should now see the OEM Unlock option.
Click to expand...
Click to collapse
3. From here, you can reboot your device into Recovery Mode by holding the Vol+ and Vol- buttons when the device begins to boot again.
4. You should see a blue screen with some options. Press the Vol+ button to enter Download Mode. This is where you'll use Odin to flash the firmware you need as well as TWRP.
Flashing Firmware
So when I attempted this process I used Magendanz's Unofficial TWRP 3.6.0 as it is the only version of TWRP I found for this device. I also used Odin v3.14.1_3B Patched from this XDA thread. Magendanz's TWRP requires you to have the T290XXU3CUG4 Firmware (I used the XAR region) in order to flash TWRP to your device (you can check wether or not you already have this firmware on your phone by looking the About Phone section again). It takes a while to download though make sure you have some time.
1. Download Odin and run the program. Unzip your firmware folder and use the relevant files when selecting the BL, AP, CP, CSC fields in Odin. I didn't use the HOME_CSC just leave it blank.
2. Connect your device via USB and Flash this firmware to your device.
3. Once your device restarts, go through the setup process and then repeat the Unlocking the Bootloader instructions above in order to make sure it is unlocked again.
4. Reboot your device the same way as stated above.
Flashing TWRP
Before starting, be aware that after you flash TWRP to your device, your device will restart and attempt to open the stock system again. You're going to want to hold the Power and Vol+ buttons simultaneously. You will likely get a warning screen saying that the bootloader is unlocked and may ask you to do a factory reset, this (I believe) is fine. The key here is that once you press the Power Button to continue (as instructed on the warning screen) you'll want to immediately press and hold the Power and Vol+ keys for around 6 Seconds before letting go again (you should be seeing the Samsung Galaxy Tab A logo screen). After letting go, wait around 3-4 seconds, if nothing changes, restart the device by holding all three buttons (Power, Vol+,Vol-) and attempt the process again. It's a pain in the ass but you'll get it eventually. Just make sure not to let the device boot into the system again as that can cause problems in TWRP and you'll likely have to start the process over (from flashing the firmware).
1. Once your tablet is once again in Download Mode, open Odin again and flash the TWRP (tar.md5 file) to the AP (recovery) partition. Do not use any of the other partitions.
2. If this is successful, your phone will begin to reboot. Quickly press and hold the combination of buttons Power and Vol+ until you see the warning dialog pop up. Once you do, release all buttons and be ready to quickly press and release the Power button continue, and then immediately after press and hold the Power and Vol+ buttons again for 6 seconds. After around 6 seconds, release all buttons. Wait around 3-4 seconds and, if the screen does not change to the TWRP logo, restart the device by pressing and holding all buttons simultaneously and try this step again.
3. If you have entered into TWRP, congrats!
Installing Custom ROM + Software in TWRP
1. The first thing you'll want to do is select the Wipe->Format Data. Type 'yes' and hit enter (or swipe I forget which).
2. Next, select Install, and then select your MicroSD card as your storage device. You should see your zip files (if not switch from the install image option).
3. Install the multidisabler, do not reboot
4. Go back into Install and select Install Image (might not be the exact naming) option. Select your MicroSD card as the storage device again and install the LineageOS 18.1 rom. Do not reboot.
5. Go back into Install and select your MindTheGapps zip file and install it.
Now, a lot of people run into a problem when trying to install Gapps which is your device complaining about no more available space in the system partition. If this is the case, go back to Wipe and select Advanced Wipe. Select your system partition and then select Change or Repair Partition. Once you're here you should see the size and available space of your partition. You'll want to hit Resize Partition and let it do it's thing. To confirm it worked, go back to Wipe->Advanced Wipe->Select System->Change or Repair Partition and your available space should be much larger now. Now just attempt to install MindTheGapps again.
Click to expand...
Click to collapse
Final Steps
Once you reboot you should be able to successfully reach the setup screen for Lineage. Go through the steps of setting up your device as usual and be sure that Gapps are installed. Go ahead and re-enable developer settings and enable USB-Debugging and Root Debugging. The reason for this is that, when I first installed Gapps, Google Play Protect would keep throwing warnings at me about my device not being Google Play Certified. This means I couldn't actually use any of the google play services. If you run into the same issue, here are the steps you can take to fix it:
1. First, go into Settings->Apps and find your Google Play Services app. Clear the cache and delete the app data, then reboot your device. If you try and sign into the Google Play store and you are able to without getting any play protect warnings, then you're good you can disregard the following steps.
2. If you are still receiving these warnings, you'll want to head over to this site and follow the instructions (I'm not gonna tell you how to use ADB here). Once you submit your framework ID, reboot your device. Everything should be working fine now.
And that's it! If I am forgetting any steps please let me know, again I am writing this from memory of the process so it may be missing some minor details. I hope this helps!!!
How's the stability, speed and the responsiveness on Lineage with a t290? I have mine rooted debloated and twrp installed but it is slow on stock OS
kkdamion said:
How's the stability, speed and the responsiveness on Lineage with a t290? I have mine rooted debloated and twrp installed but it is slow on stock OS
Click to expand...
Click to collapse
It runs surprisingly well! Much better than stock. There’s virtually no input lag and the battery life is also very solid on lineage.
Where i run into some lag is when trying to use apps that have embedded video in them. For whatever reason the T290 cannot handle video very well at all.
So yeah I would definitely recommend trying it, it’ll really breathe new life into that tablet
i cant get google play services to work and i cant fetch device_id to register the device
i get "no closing qoute" message
adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \
/system/bin/sh: no closing quote
EDIT: downloaded "android device id" APK from the internet and gathered the framework id information from the app
kkdamion said:
i cant get google play services to work and i cant fetch device_id to register the device
i get "no closing qoute" message
adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \
/system/bin/sh: no closing quote
EDIT: downloaded "android device id" APK from the internet and gathered the framework id information from the app
Click to expand...
Click to collapse
Glad it worked out for you! Let me know if you have any more questions and I'd be happy to help.
Hi! is this applicable also for SM-T295?
for those trying to figure out the Google Play Certified page with the adb command
Code:
adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \
"select * from main where name = \"android_id\";"'
do : adb shell
first then paste in :
sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \
"select * from main where name = \"android_id\";"
and it shouldn't give you the error
i must say. linageos on my sm-t290 is really nice
its fast and smooth way much better then stock fw
i would reccomend anyone with a t290/t295 to install this GSI
Im into a bootloop right now after a few fails with installing Lineage on my SM-T290..
Seems like i cant install any rom? not sure how to fix this issue, can anyone point me in the right direction?
Im able to get into TWRP and download mode. but cant install any rom?
thepalek1ng said:
Hello!
So recently I was able to install LineageOS 18.1 (GSI) + GApps on my Samsung Galaxy Tab A 8 (SM-T290) tablet and wanted to share how I did it. I noticed a lack of decent step-by-step guides to modding this tablet so I figure I'd share what I learned through scouring multiple threads and through multiple headaches. Fun fact: I also got this working with LineageOS 19 (GSI), however it ran pretty poorly and Android 12 is ugly as hell so why bother anyway? ALSO interestingly enough, you'll see I wrote [SM-T290N] in the title as well. That is the model of the Kid's Edition of this phone, which happens to be the one I had. So I can confirm this process works for the Kid's Edition of this tablet as well as the original.
What You'll Need
Your tablet
A USB Cable to connect your tablet to your PC
A 4GB+ MicroSD card
A Windows PC
Some patience
Instructions
Preparing Your MicroSD Card
1. Place the LineageOS 18.1 .img file from this thread (On SourceForge, there is a section below the files about the naming conventions and how they relate to the hardware of your device and configuration of your ROM. I used the lineage-18.1-20220315-UNOFFICIAL-arm64_bvS-vndklite.img.xz image for my device. If your device is slightly different, you can use Treble Info to determine what ROM you should use. Just make sure to use the VNDKLITE rom if your device supports it.
2. Place the multidisabler .zip folder on there as well. This will preserve encryption provided by TWRP after rebooting.
3. Finally, place the MindTheGapps .zip folder on your SD card (make sure to get the correct version. In my case this was the 11.00-arm64 version).
4. Insert your MicroSD card into your device.
Unlocking the Bootloader
So the first thing you're gonna want to do is unlock your OEM bootloader on your Samsung device.
1. Go to Settings->About Phone->Software Information and look for a field called "Build Number". Tap this Five Times until you see a notification saying developer settings were enabled.
2. Go to Settings->Developer Settings and look for the setting labeled OEM Unlock and turn it on.
3. From here, you can reboot your device into Recovery Mode by holding the Vol+ and Vol- buttons when the device begins to boot again.
4. You should see a blue screen with some options. Press the Vol+ button to enter Download Mode. This is where you'll use Odin to flash the firmware you need as well as TWRP.
Flashing Firmware
So when I attempted this process I used Magendanz's Unofficial TWRP 3.6.0 as it is the only version of TWRP I found for this device. I also used Odin v3.14.1_3B Patched from this XDA thread. Magendanz's TWRP requires you to have the T290XXU3CUG4 Firmware (I used the XAR region) in order to flash TWRP to your device (you can check wether or not you already have this firmware on your phone by looking the About Phone section again). It takes a while to download though make sure you have some time.
1. Download Odin and run the program. Unzip your firmware folder and use the relevant files when selecting the BL, AP, CP, CSC fields in Odin. I didn't use the HOME_CSC just leave it blank.
2. Connect your device via USB and Flash this firmware to your device.
3. Once your device restarts, go through the setup process and then repeat the Unlocking the Bootloader instructions above in order to make sure it is unlocked again.
4. Reboot your device the same way as stated above.
Flashing TWRP
Before starting, be aware that after you flash TWRP to your device, your device will restart and attempt to open the stock system again. You're going to want to hold the Power and Vol+ buttons simultaneously. You will likely get a warning screen saying that the bootloader is unlocked and may ask you to do a factory reset, this (I believe) is fine. The key here is that once you press the Power Button to continue (as instructed on the warning screen) you'll want to immediately press and hold the Power and Vol+ keys for around 6 Seconds before letting go again (you should be seeing the Samsung Galaxy Tab A logo screen). After letting go, wait around 3-4 seconds, if nothing changes, restart the device by holding all three buttons (Power, Vol+,Vol-) and attempt the process again. It's a pain in the ass but you'll get it eventually. Just make sure not to let the device boot into the system again as that can cause problems in TWRP and you'll likely have to start the process over (from flashing the firmware).
1. Once your tablet is once again in Download Mode, open Odin again and flash the TWRP (tar.md5 file) to the AP (recovery) partition. Do not use any of the other partitions.
2. If this is successful, your phone will begin to reboot. Quickly press and hold the combination of buttons Power and Vol+ until you see the warning dialog pop up. Once you do, release all buttons and be ready to quickly press and release the Power button continue, and then immediately after press and hold the Power and Vol+ buttons again for 6 seconds. After around 6 seconds, release all buttons. Wait around 3-4 seconds and, if the screen does not change to the TWRP logo, restart the device by pressing and holding all buttons simultaneously and try this step again.
3. If you have entered into TWRP, congrats!
Installing Custom ROM + Software in TWRP
1. The first thing you'll want to do is select the Wipe->Format Data. Type 'yes' and hit enter (or swipe I forget which).
2. Next, select Install, and then select your MicroSD card as your storage device. You should see your zip files (if not switch from the install image option).
3. Install the multidisabler, do not reboot
4. Go back into Install and select Install Image (might not be the exact naming) option. Select your MicroSD card as the storage device again and install the LineageOS 18.1 rom. Do not reboot.
5. Go back into Install and select your MindTheGapps zip file and install it.
Final Steps
Once you reboot you should be able to successfully reach the setup screen for Lineage. Go through the steps of setting up your device as usual and be sure that Gapps are installed. Go ahead and re-enable developer settings and enable USB-Debugging and Root Debugging. The reason for this is that, when I first installed Gapps, Google Play Protect would keep throwing warnings at me about my device not being Google Play Certified. This means I couldn't actually use any of the google play services. If you run into the same issue, here are the steps you can take to fix it:
1. First, go into Settings->Apps and find your Google Play Services app. Clear the cache and delete the app data, then reboot your device. If you try and sign into the Google Play store and you are able to without getting any play protect warnings, then you're good you can disregard the following steps.
2. If you are still receiving these warnings, you'll want to head over to this site and follow the instructions (I'm not gonna tell you how to use ADB here). Once you submit your framework ID, reboot your device. Everything should be working fine now.
And that's it! If I am forgetting any steps please let me know, again I am writing this from memory of the process so it may be missing some minor details. I hope this helps!!!
Click to expand...
Click to collapse
bro, I have a problem, my tablet is in a bootloop and I don't know what to do, try with other custom roms but it's the same, what do I have to do so that when I install a custom room it doesn't give me that error?
Flashing the Gapps package resulted in an error: Failure to mount '/system_root' (Invalid argument)
V0latyle said:
Flashing the Gapps package resulted in an error: Failure to mount '/system_root' (Invalid argument)
Click to expand...
Click to collapse
Sorry for the bother, new to Android modding scene.
I went into the recovery menu (oem unlock on) and tried to flash TWRP as written on this guide, but I get a secure check fail : aboot on my device and fail on Odin. What do I do here?
Edit: Aparently my device is SM-T295, basically the LTE version of the same device, which is why it isn't recognising it. My bad.
Do you have any video to teach better ???
HyruleanKnight said:
Sorry for the bother, new to Android modding scene.
I went into the recovery menu (oem unlock on) and tried to flash TWRP as written on this guide, but I get a secure check fail : aboot on my device and fail on Odin. What do I do here?
Edit: Aparently my device is SM-T295, basically the LTE version of the same device, which is why it isn't recognising it. My bad.
Click to expand...
Click to collapse
Shouldn't matter, TWRP is the same for both variants.
There's two ways to get around the secure check fail problem:
After updating via Odin, make sure you immediately interrupt the boot and force reboot into Download Mode. Then, flash TWRP.
Or, after updating, allow your device to boot to Android, skip through the setup wizard (make sure you connect to the internet), and enable Developer Options. Ensure OEM Unlocking is there and grayed out. If not, leave it for a bit until it is. This disables Vaultkeeper on the bootloader. Then, reboot to download mode and flash TWRP.
In both cases, after flashing TWRP, DO NOT let the device boot into Android. Force boot into recovery, then install the Multidisabler from here.
Now to my own problem...
I don't know what I did differently (or wrong) but I cannot get LineageOS to boot correctly on my T290. I was running 18.1 before. I recently updated to CVG3 and followed the same process as I did before - flashed TWRP, then installed the LineageOS GSI to /system.
18.1 continuously bootloops without even loading LineageOS.
19.1 gets to the LineageOS splash screen, and occasionally the setup screen, but continuously reboots also.
After flashing TWRP, I'm installing the multidisabler, then wiping /system, /data, /cache.
Any idea what I'm doing wrong?
@J.Michael any thoughts? You're more familiar with Samsung than I am
V0latyle said:
Shouldn't matter, TWRP is the same for both variants.
There's two ways to get around the secure check fail problem:
After updating via Odin, make sure you immediately interrupt the boot and force reboot into Download Mode. Then, flash TWRP.
Or, after updating, allow your device to boot to Android, skip through the setup wizard (make sure you connect to the internet), and enable Developer Options. Ensure OEM Unlocking is there and grayed out. If not, leave it for a bit until it is. This disables Vaultkeeper on the bootloader. Then, reboot to download mode and flash TWRP.
In both cases, after flashing TWRP, DO NOT let the device boot into Android. Force boot into recovery, then install the Multidisabler from here.
Now to my own problem...
I don't know what I did differently (or wrong) but I cannot get LineageOS to boot correctly on my T290. I was running 18.1 before. I recently updated to CVG3 and followed the same process as I did before - flashed TWRP, then installed the LineageOS GSI to /system.
18.1 continuously bootloops without even loading LineageOS.
19.1 gets to the LineageOS splash screen, and occasionally the setup screen, but continuously reboots also.
After flashing TWRP, I'm installing the multidisabler, then wiping /system, /data, /cache.
Any idea what I'm doing wrong?
@J.Michael any thoughts? You're more familiar with Samsung than I am
Click to expand...
Click to collapse
I think I have a solution.
I see that you are installing the multidisabler after you booted TWRP and by wiping the partitions, however, what you are supposed to do is this:
After you have booted into TWRP and have swiped to allow modifications, go to Wipe> Format Data and type yes. Don't reboot, and don't wipe any other partitions.
After that, go to install and then install the multidisabler, don't reboot.
Then install the latest LineageOS gsi to the system partition, and finally install gapps, then reboot.
Make sure you are choosing the arm64_bvS_vndklite variant, otherwise it will bootloop.
Hope this helps!
Just Mike said:
I think I have a solution.
I see that you are installing the multidisabler after you booted TWRP and by wiping the partitions, however, what you are supposed to do is this:
After you have booted into TWRP and have swiped to allow modifications, go to Wipe> Format Data and type yes. Don't reboot, and don't wipe any other partitions.
After that, go to install and then install the multidisabler, don't reboot.
Then install the latest LineageOS gsi to the system partition, and finally install gapps, then reboot.
Make sure you are choosing the arm64_bvS_vndklite variant, otherwise it will bootloop.
Hope this helps!
Click to expand...
Click to collapse
Okay, so install Multidisabler AFTER wiping data. I'll try that.
I'm using the bgS image so it's already got Google apps. I didn't have any success flashing any of the Gapps packages on the vanilla images.
Is Multidisabler still necessary on Android 11 on this device, or do we just need a patched vbmeta.img?
V0latyle said:
Okay, so install Multidisabler AFTER wiping data. I'll try that.
I'm using the bgS image so it's already got Google apps. I didn't have any success flashing any of the Gapps packages on the vanilla images.
Is Multidisabler still necessary on Android 11 on this device, or do we just need a patched vbmeta.img?
Click to expand...
Click to collapse
Yes, Multidisabler is necessary, otherwise it'll bootloop. I haven't tried anything with a patched vbmeta and frankly don't want to.
The bgS version will work just fine for Android 11.
Currently running Android 13 with LineageOS 20.0, the bvS version. Gotta say it works great. MindtheGapps 13 will work, I haven't encountered any "This device is not certified" issues.
Just Mike said:
Yes, Multidisabler is necessary, otherwise it'll bootloop. I haven't tried anything with a patched vbmeta and frankly don't want to.
The bgS version will work just fine for Android 11.
Currently running Android 13 with LineageOS 20.0, the bvS version. Gotta say it works great. MindtheGapps 13 will work, I haven't encountered any "This device is not certified" issues.
Click to expand...
Click to collapse
Do I need to wipe /system or /boot or anything before installing? I did exactly as you said - rebooted to recovery (was running Samsung stock), formatted data, installed multidisabler, then installed a LineageOS 19 image to /system. It begins to boot (LineageOS animation) then reboots.
Are you using Andy Yan's builds?
V0latyle said:
Do I need to wipe /system or /boot or anything before installing? I did exactly as you said - rebooted to recovery (was running Samsung stock), formatted data, installed multidisabler, then installed a LineageOS 19 image to /system. It begins to boot (LineageOS animation) then reboots.
Are you using Andy Yan's builds?
Click to expand...
Click to collapse
Nope, you don't have to wipe any other partitions, only format data
Yes, I'm using Andy Yan's builds. I'll link the thread here: https://forum.xda-developers.com/t/gsi-13-lineageos-20-trebledroid-based.4517345/
If I may ask, which type GSI from Andy Yan did you use?
Just Mike said:
Nope, you don't have to wipe any other partitions, only format data
Yes, I'm using Andy Yan's builds. I'll link the thread here: https://forum.xda-developers.com/t/gsi-13-lineageos-20-trebledroid-based.4517345/
If I may ask, which type GSI from Andy Yan did you use?
Click to expand...
Click to collapse
Trying to get back into TWRP, just a sec...
-arm64_bgS.img
Flashing the vndklite one now to see if it works
If I can get this working, I plan on using a bgN flavor so I can just install Magisk, since I don't use SuperSU
Edit: vndklite is bootlooping too