Related
i got xposed framework and i installed it and when i reboot it says like please install again or some error comes up. I have a htc one m8 att unlocked rooted also
shalko25 said:
i got xposed framework and i installed it and when i reboot it says like please install again or some error comes up. I have a htc one m8 att unlocked rooted also
Click to expand...
Click to collapse
I feel your pain. I had it working at one point but I restored a backup with TWRP and now I have the issue again. I am going to mess with it now and see if I can get it to stick. It will work because I also have a backup (TWRP) in which it does. But on that image, my wifi tether stops when the screen goes black/locks. I WILL figure it out though.
shalko25 said:
i got xposed framework and i installed it and when i reboot it says like please install again or some error comes up. I have a htc one m8 att unlocked rooted also
Click to expand...
Click to collapse
OK. I Got it going again.
Here are ALL the steps I tried in order:
1. Install latest apk
2. Open app and install framework
3. Select install zip manually via recovery
4. Install framework 2.3.1 zip
5. Reboot
6. Didn’t work.
7. Uninstall. This will make an Xposed disabler and give the path
8. Hit ok and it will boot to recovery
9. Click install and locate the Xposed-Disabler-Recvoery.zip. This will uninstall the framework.
10. Uninstall app
11. Reinstall app
12. Open app and install framework via the zip recovery method
13. In recovery, click install
14. Install version 2.1.4 framework
15. Reboot
16. Didn’t work
17. Install framework with recovery-use auto mode
18. WIN!!!!
It was way easier than I was making it. So in short.
1> Install the latest version (stable) 2.6.1 of the app/apk.
2> Open the app after it installs.
3> Click on Framework.
4>Installation Mode should be set to (flash zip
automatically).
5> Click Install/Update.
6> When prompted, click OK to reboot to
recovery.
7> Phone will boot to recovery, install the frame work and
reboot.
8> When the phone reboots, open the Xposed app and the framework
should be good to go.
Let me know.
Helllo friends ,
i installed a theme from play store and applied now i am getting error System ui stopped working help
where to do change to set default theme on boot. i have twrp recovery installed
Solution: check DutchMan_1990's reply
I think Only one way , Three wipe . Advance wipe the first three item.
Rahuljs said:
Helllo friends ,
i installed a theme from play store and applied now i am getting error System ui stopped working help
where to do change to set default theme on boot. i have twrp recovery installed
Click to expand...
Click to collapse
If you have TWRP recovery installed, then reboot to recovery mode. Then goto
1. Advanced
2. File manager
3. Follow the path
Code:
[B][COLOR="Red"]/data/system/[/COLOR][/B]
4. Delete the "theme" folder
5. Reboot your device.
If it's not working then again goto recovery and repeat the process 1 and 2.
Next follow the path
Code:
[B][COLOR="red"]/data/app/[/COLOR][/B]
4. Delete the corresponding theme folder. Check play store link of that theme to find the developer or package name for the specific theme pack.
5. Reboot your device.
I don't have CWM installed, but the process is pretty much same. It has Aroma File Manager inbuilt.
Oh，such a good methon!!
nirjharmistry said:
If you have TWRP recovery installed, then reboot to recovery mode. Then goto
1. Advanced
2. File manager
3. Follow the path
Code:
[B][COLOR="Red"]/data/system/[/COLOR][/B]
4. Delete the "theme" folder
5. Reboot your device.
If it's not working then again goto recovery and repeat the process 1 and 2.
Next follow the path
Code:
[B][COLOR="red"]/data/app/[/COLOR][/B]
4. Delete the corresponding theme folder. Check play store link of that theme to find the developer name for the specific theme pack.
5. Reboot your device.
I don't have CWM installed, but the process is pretty much same. It has Aroma File Manager inbuilt.
Click to expand...
Click to collapse
Thanks , I learn a lot.
nirjharmistry said:
If you have TWRP recovery installed, then reboot to recovery mode. Then goto
1. Advanced
2. File manager
3. Follow the path
Code:
[B][COLOR="Red"]/data/system/[/COLOR][/B]
4. Delete the "theme" folder
5. Reboot your device.
If it's not working then again goto recovery and repeat the process 1 and 2.
Next follow the path
Code:
[B][COLOR="red"]/data/app/[/COLOR][/B]
4. Delete the corresponding theme folder. Check play store link of that theme to find the developer or package name for the specific theme pack.
5. Reboot your device.
I don't have CWM installed, but the process is pretty much same. It has Aroma File Manager inbuilt.
Click to expand...
Click to collapse
Thanks bro your solution worked...
above solution did not solved for me.
Rom - Mokee Nightly
Android version - Marshmallow
Uninstall by safe booting
Rahuljs said:
Helllo friends ,
i installed a theme from play store and applied now i am getting error System ui stopped working help
where to do change to set default theme on boot. i have twrp recovery installed
Solution: check DutchMan_1990's reply
Click to expand...
Click to collapse
Uninstall the theme app in safe mode.
Open Beta 10 Out.
Direct link for Full Zip: https://otafsg1.h2os.com/patch/amaz....W.27_OTA_027_all_2003061929_bad6dc784e81.zip
Changelog: Screenshot
Mine says installation failed at 79% using incremental update from oxygen updater app ?
rootSU said:
Open Beta 10 Out.
Direct link for Full Zip: https://otafsg1.h2os.com/patch/amaz....W.27_OTA_027_all_2003061929_bad6dc784e81.zip
Changelog: Screenshot
Click to expand...
Click to collapse
Downloading now, I'm rooted with twrp and decrypted so should install with no problems through twrp, will report back, thanks for sharing my friend, cheers.
vtec303 said:
Downloading now, I'm rooted with twrp and decrypted so should install with no problems through twrp, will report back, thanks for sharing my friend, cheers.
Click to expand...
Click to collapse
Sounds good. Are you currently on OB9?
AndroidRooterKev said:
Sounds good. Are you currently on OB9?
Click to expand...
Click to collapse
No, 10.0.4, cheers.
hoseth0711 said:
Mine says installation failed at 79% using incremental update from oxygen updater app ?
Click to expand...
Click to collapse
Update: I had to download and install it through built in updater function as a full update. But I'm now on beta 10
Can someone tell me how to update without loosing root? Last time I did it (with magisk retention script) I ended up in bootloop and had to reset my whole device.
Baldesarra said:
Can someone tell me how to update without loosing root? Last time I did it (with magisk retention script) I ended up in bootloop and had to reset my whole device.
Click to expand...
Click to collapse
I just follow this steps and I safely update with keeping my root and twrp. (Thanks to @HippoMan)
To be clear and complete, these are the steps that I followed (there are a couple of minor clarifications here to what I wrote in my earlier message on this subject) ...
1. Download the ROM and copy it onto the top-level directory of your sdcard. I got OB10 via the Oxygen Updater app, and it also can be found elsewhere.
2. Uninstall all Magisk modules
3. Reboot
4. Go to Settings->System->System Updates and click on the little gear on the upper right. Then, select Local upgrade, select the ROM on your sdcard, and start the installation
5. After the installation is complete, *** DO NOT REBOOT ***
6. Run Magisk Manager, go to Downloads, and then search for, download, and install the TWRP A/B Retention Script.
7, After this module installation is complete, *** DO NOT REBOOT ***
8. Immediately go to the main page of the Magisk Manager, and in the "Magisk is up to date" section, select INSTALL->INSTALL->Install to inactive slot(After OTA)
9. After this completes, reboot.
10. Your device should come back up rooted and with OB10 shown in Settings->About phone->Build number
11. If you have been using Smurf, boot into recovery and flash it again. Then, reboot back to System (I'm not sure whether reflashing Smurf is actually necessary, but it doesn't do any harm).
12. Reinstall all your formerly installed Magisk modules. You'll notice that the A/B Retention Script is not showing as "installed", and this is correct. It is just used as a one-time setup before the Install to inactive slot step, described above.
Steps 1 through 11 took less than 30 minutes, with steps 1 and 4 taking the longest. I have a number of Magisk modules, so step 12 took maybe 10 minutes more, because I rebooted after each individual Magisk module was reinstalled, in order to make sure that its installation was successful.
Sent from my GM1913 using Tapatalk
sudanking said:
I just follow this steps and I safely update with keeping my root and twrp. (Thanks to @HippoMan)
To be clear and complete, these are the steps that I followed (there are a couple of minor clarifications here to what I wrote in my earlier message on this subject) ...
1. Download the ROM and copy it onto the top-level directory of your sdcard. I got OB10 via the Oxygen Updater app, and it also can be found elsewhere.
2. Uninstall all Magisk modules
3. Reboot
4. Go to Settings->System->System Updates and click on the little gear on the upper right. Then, select Local upgrade, select the ROM on your sdcard, and start the installation
5. After the installation is complete, *** DO NOT REBOOT ***
6. Run Magisk Manager, go to Downloads, and then search for, download, and install the TWRP A/B Retention Script.
7, After this module installation is complete, *** DO NOT REBOOT ***
8. Immediately go to the main page of the Magisk Manager, and in the "Magisk is up to date" section, select INSTALL->INSTALL->Install to inactive slot(After OTA)
9. After this completes, reboot.
10. Your device should come back up rooted and with OB10 shown in Settings->About phone->Build number
11. If you have been using Smurf, boot into recovery and flash it again. Then, reboot back to System (I'm not sure whether reflashing Smurf is actually necessary, but it doesn't do any harm).
12. Reinstall all your formerly installed Magisk modules. You'll notice that the A/B Retention Script is not showing as "installed", and this is correct. It is just used as a one-time setup before the Install to inactive slot step, described above.
Steps 1 through 11 took less than 30 minutes, with steps 1 and 4 taking the longest. I have a number of Magisk modules, so step 12 took maybe 10 minutes more, because I rebooted after each individual Magisk module was reinstalled, in order to make sure that its installation was successful.
Sent from my GM1913 using Tapatalk
Click to expand...
Click to collapse
Shouldn't be that difficult.
Download the full zip from OP
Remove all the current Magisk Modules just to be safe
Boot into TWRP
Flash the OTA zip
Flash TWRP 76 zip
Reboot into Recovery
Flash Magisk Canary Zip
Boot to system
That's what I always follow, and it has never failed me.
With each update icons, fonts and whole UI seems to be larger and larger. It looks awful.
1- uninstall Magisk modules.
2- install Oos stable/open beta with Settings > Local upgrade . DON'T reboot!!!
3- back to Magisk > Downloads. Install TWRP A/B Retention Script. DON'T reboot!!!
4- back in Magisk. Touch install. Choose (Install to inactive slot after' OTA)
5- reboot to system.
Now you have latest Oos ob10, twrp 3.3.1_79 & Magisk Canary root. I updated this way from ob5...
I was on Oos 10.0.4, twrp 3.3.1_76, Magisk Canary form 12.02.2020.
using the LIV DARK substartum theme on oneplus 7 pro after the update on oxygem beta 9 and beta 10 when i apply the theme to the call dialer the theme is applied to the contacts and when i open the call dialer it does not open the failure message. .
No thanks , I will stick with Open Beta 8 all day long
until they bringing Back the One-Handed Mode
Except Feb patch I don't see anything new but... It seems snappier! Good update!
Sent from my OnePlus7Pro using XDA Labs
Thank you for sharing this with us.
You now have two functions Tap once to wake ambientscreen, tap twice to wake the lockscreen. Love it.
i6rb said:
No thanks , I will stick with Open Beta 8 all day long
until they bringing Back the One-Handed Mode
Click to expand...
Click to collapse
Are you using the dialer beta version? I had to change to normal/stock dialer and it works fine. Same theme, Liv dark
Also make sure to uninstall all layers and then reboot. Then you should try to apply the layers
When you boot or reboot your phone you too have a bug that the display won't turn on and you need to press tge power button to make the screen turn on?
preference said:
Are you using the dialer beta version? I had to change to normal/stock dialer and it works fine. Same theme, Liv dark
Also make sure to uninstall all layers and then reboot. Then you should try to apply the layers
Click to expand...
Click to collapse
can you pass me the stock dialer please
Svid said:
When you boot or reboot your phone you too have a bug that the display won't turn on and you need to press tge power button to make the screen turn on?
Click to expand...
Click to collapse
I have had this issue for a while. Don't know what is the cause and didn't see reports on it. Also, I can tap on the screen while it is still black (after reboot) and PIN would be pressed!
[GUIDE/TUTORIAL/HOWTO] Google Nexus 7 2012 stock to Android 7.1
[GUIDE/TUTORIAL/HOWTO] Google Nexus 7 2012 3G/tilapia or wifi-only/grouper to Android 7.1 Nougat / LineageOS 14.1
This detailed step-by-step guide helps you transform your Google Nexus 7 (3G or wifi) with Android 5 to a powerful one with Android 7.1 Nougat.
Don't expect stable Android 8 or 9 on this tab, but 7.1 is already perfect ;-)
### I'll make a few notes using this style: PLEASE READ THEM.
Before going further, make sure you have the correct model.
Go to Settings > About tablet > Model number: Nexus 7
And on tablet's back cover: Nexus is written horizontally (vertically on 2013 model)
### See here if not clear: https://android.stackexchange.com/questions/58273/how-to-distinguish-nexus-7-2012-and-nexus-7-2013
And if you have a SIM card slot on the side, it is a 3G model (codename tilapia), if not, Wifi only alias grouper.
Make sure you have latest official updates.
Connect tab to Wifi network.
Go to Settings > About > Update. Download if update is available.
CHANGELOG
v3. Improve readability + update TWRP + gapps-config.txt (thx to @23deanor)
v2. Minor updates for tutorial + pack
v1. Initial release
1) DOWNLOAD
- djibe Nexus 7 2012 pack: https://bit.ly/djibe-nexus7-2012-packv2
(contains USB drivers r13 + fastboot & adb + TWRP recovery 3.5.2_9-0 + gapps-config.txt by @aaopt + working OpenGapps pico + Magisk root).
### Use Incognito web browser mode if needed to download pack.
Unzip pack on Windows desktop.
For 3G model/tilapia:
ROM LineageOS 14.1: https://forum.xda-developers.com/t/rom-7-1-2-tilapia-unofficial-lineageos-14-1-2021-01-11.3978723/
Download latest build: https://androidfilehost.com/?fid=17248734326145713539
For Wifi model/grouper:
ROM LineageOS 14.1: https://forum.xda-developers.com/t/rom-7-1-2-grouper-unofficial-lineageos-14-1-2021-01-11.4112431/
Download latest build: https://androidfilehost.com/?fid=17248734326145713542
Google Apps are included in my pack (open_gapps-arm-7.1-pico-20190209.zip)
Tablet must be fully charged to 100%.
2) INSTALL WINDOWS DRIVERS AND BACKUP
Go to the folder you unzipped earlier.
navigate to usb_driver_r13-windows > usb_driver.
Right click on android_winusb.inf and select Install. Confirm with OK.
Restart Windows.
Make sure Google/provider account is synchronized.
Backup photos, documents, contacts before going any further (ex: use the backupyourmobile app).
Connect tab to PC and retrieve data.
3) UNLOCK BOOTLOADER OF GOOGLE NEXUS 7 2012
In Android, go to Settings > About tablet.
Tap 7 times on "Build number", a notification confirms Developer menu is unlocked.
Go to Settings > Developer options and check USB debugging ON.
Open a Windows command prompt on the /djibe pack folder you unziped earlier:
select folder with left click, right click while holding SHIFT on keyboard > Open command windows here
Connect tab to PC.
Enter command
Code:
adb devices
Command starts adb and returns
Code:
015d3b668413fc0d unauthorized
ADB (Android Debug Bridge) has started but tab is waiting for authorization.
On tablet, authorize adb commands from Allow USB debugging dialog: tap on OK.
Then enter command
Code:
adb reboot bootloader
Tab restarts and prints a dark screen with message: LOCK STATE - LOCKED
Enter command
Code:
fastboot oem unlock
Using Volume+, select Yes - Unlock bootloader, confirm by pressing Power.
Use Volume keys to select Reboot and Power to confirm.
Tablet is unlocked.
Configure Android fast, reactivate Developer options and USB debugging.
Then restart tablet to bootloader using once again
Code:
adb reboot bootloader
4) FLASH TWRP 3.5 RECOVERY
Now enter this command
Code:
fastboot flash recovery twrp-3.5.2_9-0-tilapia.img
### Or for Wifi only model:
Code:
fastboot flash recovery twrp-3.5.2_9-0-grouper.img
Command returns Finished. Total time: 1.828s
Use Volume keys to select Recovery mode, confirm with Power.
Welcome to TWRP recovery.
Check Never show this screen during boot again and Swip to Allow Modifications.
Go to Backup > select System, Data, Boot partitions.
Swipe to Backup and wait during backup.
Back to home screen > Mount.
You can access folders from PC if Data partition is checke and bottom right button show Disable MTP.
From Windows Explorer, navigate to Nexus 7 > Internal Storage.
Copy TWRP folder and paste it somewhere safe on PC.
This is a perfect backup in case of crash.
5) SET FILESYSTEM TO F2FS
F2FS is the fastest filesystem for read and write partitions on flash memories. Compared to EXT4, gain is from 15 to 280%.
No need to format the /System partition because it is Read only and Ext4 is still faster.
Now go Wipe > Advanced Wipe.
Select Dalvik / ART Cache, System, Cache, Data, Internal Storage and Swipe to Wipe.
Tap on Back button (to Advanced Wipe Menu).
Select /cache partition > Repair or Change File System > Change File System > F2FS, Swipe.
Go Back and back to Advanced Wipe Menu.
Select /data partition > Repair or Change File System > Change File System > F2FS, Swipe.
Tap on Home button > Reboot > Recovery > Swipe to Reboot
6) FLASH ANDROID + OPENGAPPS + MAGISK
On restart, check Never show this screen during boot again and Swipe to Allow Modifications.
Back to Mount menu.
Connect tab to computer.
Copy ROM + GAPPS + gapps-config.txt + Magisk
### Do not unzip files. Copy and paste zip files to Internal Storage
### Copy gapps-config.txt or you will get an "insufficient space" crash during flash.
Then go back to Home menu > Install
Select lineage-*.zip, and Add More Zips,
then open_gapps-arm-7.1-pico-20190209.zip and Add More Zips,
then Magisk.zip and Swipe to force install.
Be patient.
### If it fails, install zips 1 by 1.
Android 7.1 is installed !
When done message prompts, tap on Wipe Cache/Dalvik and swype to confirm, wait.
Disconnect tab from PC.
Then Reboot System.
Let the tab start (at least 10 minutes).
7) ROOT WITH MAGISK
Configure Android as you like.
Magisk root starts with Android.
You can manage permissions and extra modules with Magisk Manager app.
Open Magisk app (v23+).
Go to Settings > go to App Rename app to Godmode to hide hide.
Below, switch MagiskHide ON.
Now go to Magisk Modules tab > install liboemcrypto disabler and MagiskHide Props Config.
Connect to your Google account, download from Play Store Netflix and Disney+.
### If you are already connected to Google account.
Clear cache (Settings > Apps > All apps > Google Play Store > Storage > Clear storage) and restart tab.
Relaunch Play Store, Netflix and Disney+ will be available in SD.
10) OTHER APPS
- You can use GPS Status & Toolbox for faster GPS fix.
- Developer options
Settings > About tablet.
Tap 7 times on build number.
Back to Settings > Developer options
Select USB Configuration > set MTP
Set Windows animation scale, Transition animation scale and Animator duration scale to .5x
- In Developer options, you may try Force GPU rendering.
Much faster on my tab, tell me if it does (or not for you)
That's it.
Enjoy ;-)
Thanks: ud4, AndDiSa, aaopt, TWRP team, LineageOS team, OpenGApps team
hi is there a video tutorial for this bit
Open a Windows command prompt on the /djibe pack folder you unziped earlier:
select folder with left click, right click while holding SHIFT on keyboard > Open command windows here
i've never used command prompt or adb,thanks
tonybhoy said:
hi is there a video tutorial for this bit
Open a Windows command prompt on the /djibe pack folder you unziped earlier:
select folder with left click, right click while holding SHIFT on keyboard > Open command windows here
i've never used command prompt or adb,thanks
Click to expand...
Click to collapse
Hi, you may try this: https://www.thewindowsclub.com/how-to-open-command-prompt-from-right-click-menu
djibe89 said:
Hi, you may try this: https://www.thewindowsclub.com/how-to-open-command-prompt-from-right-click-menu
Click to expand...
Click to collapse
hi,i can open cmd prompt i just don't know how to get it to find the folder i'm looking for,the flash one i think
this is all i get
tonybhoy said:
this is all i get
Click to expand...
Click to collapse
Hi,
it seems you didn't read well the WindowsClub tutorial.
3 choices:
From within the /flash folder, enter "cmd" in the address bar and hit ENTER. It will open the CMD in the /flash context.
Copy path of folder from Windows Explorer address bar and enter following command in CMD:
cd /d (CTRL + V TO PASTE THE PATH)
Move to the parent directory (/djibe). Select /flash folder, then hold SHIFT and right click Open command here.
Command will open on the /flash context.
djibe89 said:
Back to home screen > Mount.
You can access folders from PC if Data partition is checke and bottom right button show Disable MTP.
From Windows Explorer, navigate to Nexus 7 > Internal Storage.
Copy TWRP folder and paste it somewhere safe on PC.
This is a perfect backup in case of crash.
5) SET FILESYSTEM TO F2FS
F2FS is the fastest filesystem for read and write partitions on flash memories. Compared to EXT4, gain is from 15 to 280 %.
No need to format the /System partition because it is Read only and Ext4 is still faster.
Now go Wipe > Advanced Wipe.
Select Dalvik / ART Cache, System, Cache, Data, Internal Storage and Swipe to Wipe.
Tap on Back button (to Advanced Wipe Menu).
Select /cache partition > Repair or Change File System > Change File System > F2FS, Swipe.
Go Back and back to Advanced Wipe Menu.
Select /data partition > Repair or Change File System > Change File System > F2FS, Swipe.
Tap on Home button > Reboot > Recovery > Swipe to Reboot
6) FLASH ANDROID + OPENGAPPS + MAGISK
On restart, check Never show this screen during boot again and Swipe to Allow Modifications.
Back to Mount.
Copy ROM + GAPPS + gapps-config-tilapia.txt + Magisk + Magisk Manager.
Click to expand...
Click to collapse
Everything is going great until this point - the storage is not mounted (can't see them in Explorer). Any ideas?
23deanor said:
Everything is going great until this point - the storage is not mounted (can't see them in Explorer). Any ideas?
Click to expand...
Click to collapse
Hi,
try to reboot recovery,
go to Mount and play with bottom right button Enable/disable MTP.
If it doesnt work, go over Windows Start Menu icon > right click > Device management and make sure the Tab is well detected.
The bottom right button Enable/disable MTP didn't do much - the laptop made the noise like a USB device was being disconnected (not connected) and in the system tray, the option to eject Nexus 7 was present. I can't check Device Manager at the moment because the tablet is currently completely unresponsive. I think the battery may be flat because I left it all day and overnight before being able to come back to work on it.
I appreciate your help and would really like to get this 7.1 ROM working.
Nothing appears to be working, the tablet can be seen in adb-devices in recovery mode, but not in Device Manager or Windows Explorer.
The tablet now has no OS on it so as it currently stands is useless - do you have any ideas how to get this going again?
Hi,
install USB drivers from my pack on another PC.
Then connect tab.
And tell me what happened
djibe89 said:
Hi,
install USB drivers from my pack on another PC.
Then connect tab.
And tell me what happened
Click to expand...
Click to collapse
I renamed the folder to have no spaces in the name and used adb push to get the files on to the tablet. Next problem is there isn't enough storage to install the gapps package.
23deanor said:
I renamed the folder to have no spaces in the name and used adb push to get the files on to the tablet. Next problem is there isn't enough storage to install the gapps package.
Click to expand...
Click to collapse
Did you flash the repartition script first ?
djibe89 said:
Did you flash the repartition script first ?
Click to expand...
Click to collapse
No, I don't see that in your instructions.
23deanor said:
No, I don't see that in your instructions.
Click to expand...
Click to collapse
Well, sorry, I'm confused with Nexus 7 2013.
Wipe all partitions.
Copy ROM + GAPPS + the file gapps-config-tilapia.txt. Without this GApps are oversized
djibe89 said:
Well, sorry, I'm confused with Nexus 7 2013.
Wipe all partitions.
Copy ROM + GAPPS + the file gapps-config-tilapia.txt. Without this GApps are oversized
Click to expand...
Click to collapse
You have me confused too now.
Is there a need to repartition or not?
23deanor said:
You have me confused too now.
Is there a need to repartition or not?
Click to expand...
Click to collapse
Hi, you don't need to repartition for Android 7.1.
You need both Opengapps + gapps-config-tilapia.txt when falshing GApps.
djibe89 said:
Hi, you don't need to repartition for Android 7.1.
You need both Opengapps + gapps-config-tilapia.txt when falshing GApps.
Click to expand...
Click to collapse
Ok. But there isn't the space to install them despite wiping everything, so I will need to look elsewhere I think.
23deanor said:
Ok. But there isn't the space to install them despite wiping everything, so I will need to look elsewhere I think.
Click to expand...
Click to collapse
Is the txt config file along gapps when you flash ?
If not it won't work.
djibe89 said:
Is the txt config file along gapps when you flash ?
If not it won't work.
Click to expand...
Click to collapse
Yes I push them both across to /data and install from there using TWRP
Hi, here's my guide on how install Ancient OS 5.2 (A11) on Redmi 8
What doesn't work
- Bluetooth
- 4g network and VoLTE (Fix below)
- Brightness slider and auto-brightness (Fix below)
Fixes:
- For brightness: Open settings -> Go in "Phh Treble Settings" -> "Misc Features" -> Scroll until you are in backlight menu -> Select "Force alternative backlight scale" and "Enable auto-brightness overlay" -> then deselect both and reboot
- For 4g and VoLTE: Open settings -> Go in "Network and internet" -> "Mobile network" -> Tap on "Preferred network type" and select "LTE" and then reboot
Note 1: If you find a fix for bluetooth describe it in comments, I will update the guide
Note 2: If you fing other bugs tell me in comments, maybe I could help you (I'm not the developer of the rom)
IMPORTANT ADVICE:I am not responsible for any damage caused to your device by not following the steps or negligence at the time of this process, all the steps were carried out and tested on my personal device and are confirmed, my device is Redmi 8 4/64
Installation Steps - All the files you need are HERE
Note 3: I did the installation coming from Mui 12.0.1 stock (flashed in fastboot with Mi Flash) and there was no problem in the installation process or in the boot process
1- First make a backup of all the necessary information in case something goes wrong you can easily recover, Charge the battery at least 80%
All your data will be deleted during the process
2- Unlock the Bootloader if you have not already done it or do not know how to, follow this post: http://en.miui.com/unlock/
3- Before continue following steps estract on pc "system-arm64-AB-vndklite.img" from "AncientOS-R-Society-v5.2-ARM64_AB_vndklite-Iron-20210227-vanilla.zip" and activate USB debug in phone settings
4- Reboot in fastboot and connect the phone to the pc with cable
5- Install on pc minimal adb tool (zip at the bottom), flash the TWRP recovery typing " fastboot flash recovery ", now drag twrp file near the command, then vbmeta typing " fastboot --disable-verity --disable-verification flash vbmeta " and drag vbmeta file near the command. Finished the procedure type " fastboot reboot " and hold volume + on the phone until you see the recovery screen
6- Scroll on the slider at the bottom of the phone screen to access in the TWRP
7- Go to Wipe -> Format data -> type "yes"
8- Go to Reboot -> Recovery
9- Go to Wipe -> Avanced wipe -> wipe dalvik, data, cache and system
10- Go to Reboot -> Recovery
NOW YOU HAVE TO TRANSFER ALL OTHER FILES OR IN THE INTERNAL STORAGE OF THE PHONE OR IN SD/USB WITH OTG CABLE
11- Go to Install -> Select the storage where you have files -> Install img -> select "system-arm64-AB-vndklite.img" and flash it (Extracted from the zip)
12- Wait and then go to Reboot -> Recovery
13- Wait and then go to Reboot -> Recovery
14- Wipe -> Advanced wipe -> select "system" and click on "Repair or change file system" -> Resize system
15- Wait and then go to Reboot -> Recovery
16- Install -> Select the storage where you have files -> Flash "GSI-BUGS-FIXER_11_Q.zip"
17- Wait and then go to Reboot -> Recovery
18- Install -> Select the storage where you have files -> Flash "open_gapps-arm64-11.0-nano-20210130-TEST.zip"
19- Wait and then go to Reboot -> System
20-Configure phone and enjoy your new rom
Note 4: Rom is pre-rooted, you only need to install magisk apk, file below
Note 5: I reccomend you the best gcam I've found for Redmi 8, everything works except slow motion, link HERE
Thanks for the attenction
-Estatè
zas far as i know bluetooth works on vendor from lineageOS 16 from this forum, there are the same bugs on every rom with original vendor.
Why U use my fixes and manuals without request to me? Your manuals wrong and makes bootloop. Before stupid copy-paste read instructions.
All roms booted without any permissiver. Certification patch retarded and not supported Android 11.
GSI FIXER is rom and vendor-specified.
Number in name = Android in rom
Letter in name = Android in vendor
kulaklığımı algılamıyor
edit: Fixed
Vicuel said:
does not detect my headphone
Click to expand...
Click to collapse
Open termux and type....
su
Then give termux root access....
Then type.....
setprop persist.sys.overlay.devinputjack true
mwaseem851 said:
Open termux and type....
su
Then give termux root access....
Then type.....
setprop persist.sys.overlay.devinputjack true
Click to expand...
Click to collapse
This needs to be done after every reboot?
gattud said:
This needs to be done after every reboot?
Click to expand...
Click to collapse
Nono, only paste it in termux with root access and reboot, then you will solve the problem forever
mwaseem851 said:
Termux'u açın ve .... yazın.
su
Sonra termux root erişimi verin ....
Sonra yazın .....
setprop persist.sys.overlay.devinputjack doğru
Click to expand...
Click to collapse
thanks
Don't use any my GSI-BUGS-FIXERS from XDA. This fixes retarded and no more supported!
Don't say to me in Telegram chat about bugs if you use fixes and instructions from any users of XDA except me.
I used the gsi bugs fixer in Telegram
@Estatè Mosconi If you haven't already I suggest you take a look in your PM inbox.