[Mi a1] [Discussion] [How-TOs] MONTHLY STOCK UPDATES, ROOT, TOOLS AND MORE | May 4 - Xiaomi Mi A1 Guides, News, & Discussion

{
"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"
}
A THREAD WHERE WE CAN DISCUSS THE MONTHLY OFFICIAL UPDATES FOR MI A1 AND OTHER USEFUL TOOLS AND MODS
TUTORIALS
============================​
How to unlock bootloader:
1. Configure fastboot for your machine. Tutorial here.
2. Reboot phone to fastboot. (Turn off, and keep pressed volume - and power buttons until you see the fastboot image.)
3. Type this at a command prompt: fastboot oem unlock. Your phone will be unlocked.
3a. Starting with May 2018 update, unlocking the bootloader will wipe the device. So, backup first.
==========================================​
Flashing stock fastboot rom:
1. Download the Mi Flash Tool from here.
2. Download the latest ROM package file for mi a1 from here.
3. Decompress the ROM so that you can see its files and folders. You may have to unzip it twice.
3. Enter phone in Fastboot mode. (check step 2 in the unlock bootloader process above)
4. Connect the phone with your computer.
5. Decompress the Mi Flash Tool downloaded in Step 1, and open XiaoMiFlash.exe
6. Press the select button to the left in the Mi Flash Tool and select the folder where you extracted the fastboot ROM.
7. Click the Refresh button, and MiFlash tool should automatically recognize the device. (check note below before flashing)
8. Click flash to flash the ROM file to the device.
9. Wait until the progress bar inside MiFlash turns fully green, which means the ROM has been successfully installed. The phone should automatically boot to the new version.
NOTE:
To the bottom right of the Miflash tool you have three option you can choose before flashing. This is what they mean:
Clean all: All data and user configuration will be cleaned. Device will remain 'Unlocked' after flashing.
Save user data: All data and user configuration will be saved.
Clean all and lock: All data and user configuration will be cleaned and device will be 'Locked' after flashing.​
=======================================​
How to root stock ROM:
1. Make sure your bootloader is unlocked as explained above
Method 1:
1. Download latest magisk.zip and put it on your sd card
2. Reboot into bootloader
3. Boot the latest twrp recovery with the command: fastboot boot twrpxxx.img
4. After booting into twrp flash magisk and reboot
Method 2:
1. Extract the boot.img file from the fastboot ROM you downloaded from here and copy the file to your phone
1a. If you updated your system Over The Air (OTA) and the official fastboot ROM is not out yet, you can extract the boot.img yourself. See the note in the end of this tutorial for this
2. Install magisk manager app from here
3. Run Magisk manager, and click install. Choose patch boot image. Choose the boot.img you copied to your phone in step 2. Let the app to patch the file. When done it will tell you where the patched file is located. Usually, in your internal sd card/Magisk
4. Copy the patched_boot.img file to your computer
5. Reboot phone in fastboot mode
6. Connect phone with computer, open a terminal window where the file is located, and run the following command
Code:
fastboot flash boot patched_boot.img
7. Reboot phone after the flashing procedure is done. You can use this command
Code:
fastboot reboot
8. Open Magisk app and now install latest Magisk through the app
9. Done
Note:
To extract the latest boot.img from your freshly updated phone yourself do the following
1. Reboot phone to fastboot and connect with your computer
2. Boot TWRP from here or use your preferred TWRP version
3. In recovery choose Backup and select Boot only. You may want to select the external sd card for the backup location
4. Wait for it to finish and reboot to system
5. Go to the TWRP folder and browse the backup folder
6. Find the file boot.emmc.win. This is your boot.img file. Rename it to boot.img and now continue with the step 3 above​
=================================================​
If your phone fails to apply OTA update because of rooting, flashing twrp and other mods to the system:
1. Uninstall Magisk from magisk manager
2. Reboot to Fastboot
2. Flash latest fastboot ROM with Mi Flash tool with the option "Save user Data"
3. Once phone restarts, your files will be preserved and now you can apply OTA
4. Root again with the above tutorial.
=================================================​
Enable camera2 API, EIS and install gcam mod:
1. Root your phone with Magisk and install Magisk manager (see above for tutorial).
2. Add this Magisk module that I made and reboot. DOWNLOAD
3. For stock rom you need to add another module in Magisk to resolve the delay in opening the gcam app. Download it from here. Credits to @flex1911
3. Finally, download gcam mod from here. Latest Arnova version is reccomended.
4. Install as a normal app, tweak the settings to your need and enjoy.
NOTE: Discussion about Arnova gcam here.
=================================================​
Reviews:
Unbox Therapy - The $200 Smartphone You NEED To Know About
GSM Arena - Xiaomi Mi A1 Review
Android Authority - Xiaomi Mi A1 review: the perfect budget phone?
Android Police - Xiaomi Mi A1 second take: For $215, it offers the best value of any Android smartphone right now
Trusted Reviews - Xiaomi Mi A1

May 26:
WARNING!!! THERE ARE REPORTS THAT UNLOCKING BOOTLOADER WITH LATEST MAY 2018 UPDATE WILL WIPE THE DEVICE.
TOO, USING MIFLASH TOOL WITH SAVING YOUR USERDATA WILL NONETHELESS WIPE DATA!
YOU HAVE BEEN WARNED!
Update:
May 4, 2019 (Android 9)
http://bigota.d.miui.com/V10.0.4.0....0.PDHMIXM_20190104.0000.00_9.0_2cee840c96.tgz
January 2019 update (Android Pie):
http://bigota.d.miui.com/V10.0.4.0....0.PDHMIXM_20190104.0000.00_9.0_2cee840c96.tgz
October 2018 update:
http://bigota.d.miui.com/V9.6.7.0.O...0.ODHMIFE_20181015.0000.00_8.0_47d6fd23c7.tgz
June 2018 security patch:
http://bigota.d.miui.com/V9.6.4.0.O...0.ODHMIFE_20180712.0000.00_8.0_735823083f.tgz
May 30, 2018 - May security update:
http://bigota.d.miui.com/V9.5.11.0....0.ODHMIFA_20180504.0000.00_8.0_1a04581058.tgz
April 24, 2018 -New stock firmware with April security patch. Version:
V.9.5.10.0.ODHMIFA
April 6, 2018 - New stock firmware released. Version:
V9.5.9.0.ODHMIFA
March 22, 2018 - New stock firmware released. Version:V9.5.4.0.ODHMIFA (Android O)
March 17, 2018 - Oreo kernel source pushed.
March 7, 2018 - Beta Stable OPR1.170623.026.9.5.4 (V9.5.4.0.ODHMIFA) has been pushed via OTA
March 2, 2018 - February security update OTA released.
Old info!
GET UPDATES FASTER:
To receive the update faster try updating your Google Play Services to beta from here.
Or, download latest Google play services from apkmirror.
More information about Google play services and the check for update button here.

devs should make this thread sticky, otherwise, noobs will open new threads anyway.
Sent from my E6653 using Tapatalk

People are reporting this:

varben said:
People are reporting this:
Click to expand...
Click to collapse
Where did you receive that from?
Sent from my Xiaomi Mi A1 using XDA Labs

joeyhuab said:
Where did you receive that from?
Click to expand...
Click to collapse
It's being reported in some forums like miui forums for example.

Something is off in build number. It looks like miui numbering scheme.

varben said:
People are reporting this:
Click to expand...
Click to collapse
That's so weird looking. Is it true?

Yes. Its latest beta.

Get ready for where-is-march-security-update threads!!!

Mi A1
MIUI Developer ROM and Stable ROM are developed by MIUI Official Team. MIUI Developer ROM focuses on new features and updates weekly; MIUI Stable ROM prioritizes stablity and updates about every 2 months.

Here comes February update. Better late than never!
On to the March update saga!
Will post official link as soon as made public.

I don't have it yet

bgalka said:
I don't have it yet
Click to expand...
Click to collapse
Try restarting and checking again. If nothing yet, just wait.
Don't do any silly thing like clearing caches and alike. Be patient, you waited a month for this... a couple of days more won't hurt you.
Or, if you are impatient, and feel like starting your phone from scratch, flash January security patch with mi flash tool and check again!

Just updated to february patch, i noticed 1 bug that was in january update too but not in december update. LINE messenger notification doesnt have quick reply bar

I'm still stuck with the January Security Patch. Post here when I get the March one.
Cheers!
Update:
I got the update! WooHoo

How can I force the update? I don't want to mess with Google framework because last time I lost push notifications. I hear a sequence of character you need to tip in the dialer to force searching for the update
Sent from my Xiaomi Mi A1 using XDA Labs

varben said:
Here comes February update. Better late than never!
On to the March update saga!
Will post official link as soon as made public.
Click to expand...
Click to collapse
Lucky you, haven't got it yet.

valkyrjur said:
How can I force the update? I don't want to mess with Google framework because last time I lost push notifications. I hear a sequence of character you need to tip in the dialer to force searching for the update
Sent from my Xiaomi Mi A1 using XDA Labs
Click to expand...
Click to collapse
Try my guide I just set up! https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-february-update-via-play-t3757866

piplu.ewu said:
Lucky you, haven't got it yet.
Click to expand...
Click to collapse
Luck has nothing to do with it.

Related

[Discussion & Feedback] OxygenOS 10.3.7 OTA for the OnePlus 6

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey everyone,
We are starting to push the incremental rollout of OxygenOS 10.3.7 for OnePlus 6.
Changelog
Code:
[B]System:[/B]
• Newly added "Hide silent notifications in status bar" feature to filter unimportant notifications, making the app notification management easier( Route: Settings>Apps & Notifications> Notifications> Advanced> Hide silent notifications in status bar )
• Fixed the small probability issue that Screenshot may fail
• Updated Android Security Patch to 2020.11
• Improved system stability and fixed general bugs
[B]Game Space:[/B]
• Newly added gaming tools box for convenient switches of Fnatic mode. You can now choose three ways of notifications: text-only, heads up and block, just for your immersive gaming experience
• Newly added quick reply feature in a small window for WhatsApp and INS (Enable it by swiping down from upper right/left corners of the screen in gaming mode)
• Newly added mis-touch prevention feature. Enable it, swipe down from the top of the screen, click and the notification bar will pop out
Explore what's new on Android 10 here.
This OTA will have a staged rollout. The OTA will be received by a limited number of users today and will have a broader rollout in a few days after making sure there are no critical bugs. Using VPN to download this build might not work as the rollout Is not based on regions and is randomly pushed out to a limited number of devices.
For those who were on previous versions for OnePlus 6 and OnePlus 6T, we appreciate your active feedback and for reaching out to us. With your help, we have been able to better optimize and improve several key areas. Thank you for your patience and as always, we look forward to getting your continued feedback via the Community app.
If you don't have the Community app installed on your device, feel free to download it HERE. You can check here for more information on the integrated Feedback tool. Make sure to let us know how you feel about the build here in the thread too, we look forward to reading your feedback.
Downloads​
Full Update
OxygenOS 10.3.7: Official Link | Android File Host
MD5 Hash: 74e8f5a4439516aac04ce8c94fb9427a
Stock Boot Image
10.3.7 boot.img: Unofficial Link
MD5 Hash: b0c15983c4872b3ae622dc93693c4484
Magisk Patched Boot Image
10.3.7 boot.img: Unofficial Link
MD5 Hash: 4774a4a9eed732a837605ea9f5af4391
Previous Updates along with boot images:
Link: Unofficial Link
Custom Recoveries
Official/Unofficial TWRP by mauronofrio: Official Link
blu_spark TWRP by eng.stk: Official Link
Black Out TWRP by acuicultor/Morphine1: Official Link
Root
Magisk: Official Link
Warning: Do not flash partial update OTAs (under 1 GB) on a modified/rooted device! If you want to use partial OTAs, you must first flash the full OxygenOS zip that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing one of the above full zips in recovery.
Installation Instructions​
Download the necessary files from the section above and follow the steps below:
Note: Dirty flashing is fine if you are running an old OxygenOS version or a ROM based on OxygenOS. If you are, however, coming from a Custom ROM, you must clean flash.
Caution: Please remove your existing screen lock/pin/pattern/password and set it to swipe before starting the update process.
For Non-Rooted Users with a Locked Bootloader and Stock Recovery
Download the full ROM zip from the downloads section above and place it in the root of your internal memory
Reboot to Stock Recovery > Shutdown device > Press Volume Down + Power buttons together
Select Language > Install menu > Install from internal > Select the full zip > Flash
Reboot to System
Note: First boot may take some time, so please be patient and wait for it to boot.
[Dirty Flash] For Users with an Unlocked Bootloader and TWRP Recovery coming from Stable OxygenOS, OxygenOS Open Beta
Download the full ROM zip and TWRP recovery from the downloads section above
Transfer the full ROM zip and TWRP recovery to the root of your device's internal storage
Reboot to TWRP recovery and take a nandroid backup of your existing ROM
From the TWRP menu, Install > Select full ROM zip > Swipe to flash
From the TWRP menu, Install > Select TWRP recovery zip > Swipe to flash
Reboot to TWRP recovery
Flash the latest stable Magisk in case you want to root
Reboot to System
Note: First boot may take some time, so please be patient and wait for it to boot.
Warning: Dirty flashing (update) can be risky! Remember that if you face issues after dirty flashing, you will have to clean flash.
[Clean Flash] For Users with an Unlocked Bootloader and TWRP Recovery
Download the full ROM zip and TWRP recovery from the downloads section above
Transfer the full ROM zip and TWRP recovery to the root of your device's internal storage
Reboot to TWRP recovery and take a nandroid backup of your existing ROM
From the TWRP menu, Install > Select full ROM zip > Swipe to flash
From the TWRP menu, Install > Select TWRP recovery zip > Swipe to flash
Reboot to TWRP recovery
From the TWRP menu, Wipe > Swipe to wipe
Flash the latest stable Magisk in case you want to root
Reboot to System
Note: First boot may take some time, so please be patient and wait for it to boot.
Never Settle.
XDA:DevDB Information
[Discussion & Feedback] OxygenOS 10.3.7 OTA for the OnePlus 6, ROM for the OnePlus 6
Contributors
Funk Wizard, Akhil701
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Current Stable Version: 10.3.7
Stable Release Date: 2020-11-29
Created 2019-02-11
Last Updated 2020-11-28
Downloads moved to post 1
Thread Maintainer: @jslawler & @Akhil701
Flashing instructions moved to post 1
Thread Maintainer: @jslawler & @Akhil701
Can we get more details on the 5.1.5? What bugs were fixed? What improvements were made?
GizmoFreak said:
Can we get more details on the 5.1.5? What bugs were fixed? What improvements were made?
Click to expand...
Click to collapse
There are no details on the list of bugs fixed or the details on stability at this time.
If i get any details on it from the rom team i shall get back to you.
I believe the team is still working on a bigger update and is focused on getting some more software additions to the OnePlus 6.
Hopefully the future updates will get you better features and optimisation for a smoother experience.
Downloading it now. It seems to be getting the full ROM, probably because I have unlocked the bootloader.
I cannot wait to get my device!! Ordered at launch Direct from OnePlus via priority ship so hopefully Friday arrival!!
Ghashul said:
Downloading it now. It seems to be getting the full ROM, probably because I have unlocked the bootloader.
Click to expand...
Click to collapse
Yes the system would prompt a full zip download for unlocked bootloaders / rooted devices. Download via system updates or from the direct link in the download section :good:
i got the Notch options with this Update, but this update removed the Always On Display function. I hope it will come back
louisitou said:
i got the Notch options with this Update, but this update removed the Always On Display function. I hope it will come back
Click to expand...
Click to collapse
Always on display? I didn't see that I my settings ?
louisitou said:
i got the Notch options with this Update, but this update removed the Always On Display function. I hope it will come back
Click to expand...
Click to collapse
You talking about screensaver?
stian230 said:
Always on display? I didn't see that I my settings ?
Click to expand...
Click to collapse
It was available in OOS 5.1.0 that came pre-installed from factory. It's been removed in later OOS versions.
eroigaps said:
You talking about screensaver?
Click to expand...
Click to collapse
nope, Always on Display is showing you the Battery %, the Notifications and the Clock on your locked screen. Exactly the same feature like Samsung Galaxys and LG Phones have, and it was looking exactly the same too. But well they removed it now..
louisitou said:
nope, Always on Display is showing you the Battery %, the Notifications and the Clock on your locked screen. Exactly the same feature like Samsung Galaxys and LG Phones have, and it was looking exactly the same too. But well they removed it now..
Click to expand...
Click to collapse
oneplus isnt know for removing settings in stable release... maybe its been moved elsewhere.
It has been removed in the latest update. It's discussed all over the internet.
We hope to see AOD back in the next updates or beta.
If you wish to unroot/go back to stock recovery: Please take a look here
Ok guys we have not forgotten you and the update should be available soon. It brings some welcome additions and hopefully the global rollout will start soon :fingers-crossed:
Stay tuned :highfive:
Looking forward to it!!
SirTAVARES said:
where can i make some suggestions to oxygenOS ?
or is it wasted time?
Click to expand...
Click to collapse
Feedback is always welcome and request for features can be done on https://forums.oneplus.com/feedback/
Thank you for your continued support :good:
I just bloody flashed the test 5.1.6 build. I regretted it so much. Everything is working the same or probably faster except for the failed safety net test.
How to I revert back to 5.1.5? I tried to local update official 5.1.5 zip file but it won't let me - downgrading is not allowed apparently.
Or is it better for me to wait for full official 5.1.6 OOS zip and local update it? Will it work?

Development [ROM][Android 11][OP9] crDroid v7 [21 DEC 2021]

{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
I built this from source because I love crDroid and our main camera doesn't work at all (and other various small nuisances) on the OnePlus 9 Pro crDroid rom. Proceed with caution, this is my first rom. However, things seem stable enough to call it weekly.
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
Download LOS recovery
Download Tiny ADB & Fastboot
Download arm64 gapps (tested with NikGapps Canary Core Gapps)
First time installation (clean flash):
It is recommended to come clean from latest OOS installation
Backup your data to PC, OTG flash drive
Reboot to bootloader (fastboot)
Run fastboot devices to confirm there is connection to the phone
Install LOS recovery with following command fastboot flash boot lineage-18.1-20211212-recovery-lemonade.img
Reboot to recovery with following command fastboot reboot recovery
Navigate with volume keys to Factory Reset -> Format data/factory reset and confirm format of data
Go back to main menu and choose Apply update and Apply from ADB
Now adb sideload latest crDroid package with adb sideload crDroid.zip
When asked to confirm flash, do confirm it
Now adb sideload latest gapps package with adb sideload gapps.zip
(if Gapps fails saying it could not mount system, boot to rom, then back to recovery and try sideloading Gapps again)
Sideload push will go up to 47% and fail - no worry is normal
Reboot to system
Update installation:
Through recovery:
Download latest crDroid zip and reboot to recovery
Choose Apply update and Apply from ADB
Now adb sideload latest crDroid package with adb sideload crDroid.zip
Sideload push will go up to 47% and fail - no worry is normal
Reboot to system
Built-in OTA (slower):
Might not work until we are official again.
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sm8350
Download:
ROM https://crdroid.net/lemonade
Changelog:
Changelogs from OP9Pro crDroid since last build should mostly apply:
Initial crDroid 7.13 code base
Updated to December 2021 security patches
Updated to clang 14.0.0
Updated SQLite
Updated libjpeg-turbo
TWRP is included
Some other small changes
Misc fixes and overall improvements
Updated translations
Known issues:
Flashing via USB C Thunderbolt 4 ports may brick your device to edl only mode requiring multiple msm restores to fix.
USB-OTG not working for me at least.
Looking for additional feedback to see.
Visit official website @ crDroid.net
crDroid Lemonade/Lemonadep Telegram
crDroid Community Telegram
Donate to help the crDroid team pay server costs
Donate to buy the maintainer a beer
Reserved
What is the way to go back to normal root 1.2.7.7 if I dont decide to revert back?
Do I still do ADB Sideload even with TWRP?
Don't use twrp for now, use lineageos recovery. When oneplus9 pro crdroid can flash from twrp I will make that ability available here.
If you have a backup made from twrp, I don't see why restoring from it wouldn't work.
Alright sounds good brother.
Glad to see this here for the 9 stoked. I ran on my Verizon variant op8 unlocked for a long time. Very nice.
audalics said:
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
I built this from source because I love crDroid and our main camera doesn't work at all (and other various small nuisances) on the OnePlus 9 Pro crDroid rom. Proceed with caution, this is my first rom.
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
Until TWRP is ready, this version of crDroid comes with prebaked core Gapps
Download LOS recovery
Download Tiny ADB & Fastboot
First time installation (clean flash):
It is recommended to come clean from latest OOS installation
Backup your data to PC, OTG flash drive
Reboot to bootloader (fastboot)
Run fastboot devices to confirm there is connection to the phone
Install LOS recovery with following command fastboot flash boot lineage-18.1-20210615-recovery-lemonadep.img
Power off and reboot to recovery by pressing VOL down + Power from shutdown state
Navigate with volume keys to Factory Reset -> Format data/factory reset and confirm format of data
Go back to main menu and choose Apply update and Apply from ADB
Now adb sideload latest crDroid package with adb sideload crDroid.zip
When asked to confirm flash, do confirm it
Sideload push will go up to 47% and fail - no worry is normal
Reboot to system
Update installation:
Through recovery:
Download latest crDroid zip and reboot to recovery
Choose Apply update and Apply from ADB
Now adb sideload latest crDroid package with adb sideload crDroid.zip
Sideload push will go up to 47% and fail - no worry is normal
Reboot to system
Built-in OTA (slower):
When ready
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sm8350
Download:
ROM https://www.dropbox.com/s/xkd5augxh37cfdk/crDroidAndroid-11.0-20210625-lemonade-v7.7.zip
Changelog:
Main camera sorta works
Camera cutout size and position corrected
Fingerprint hardware fixed
Fingerprint ui element fixed
Other various fixes for op9 vs op9pro
Known issues:
Camera app crashes when switching modes or to selfie camera.
Video recording not working.
Looking for additional feedback to see.
Visit official website @ crDroid.net
crDroid Lemonade Telegram
crDroid Community Telegram
Donate to help our team pay server costs
Click to expand...
Click to collapse
Hi why i have ' E:error 21
package is for product oneplus9 but expected oneplus9pro
Even when i have oneplus 9?
papad13 said:
Hi why i have ' E:error 21
package is for product oneplus9 but expected oneplus9pro
Even when i have oneplus 9?
Click to expand...
Click to collapse
You sure you sideloading correctly?
mattie_49 said:
You sure you sideloading correctly?
Click to expand...
Click to collapse
Yes but i flashed the oneplus 9 pro version of 'crdroid' in the begining .
And noew i see in the product name lahaina. I thing this is the oneplus 9 pro name ?
papad13 said:
Yes but i flashed the oneplus 9 pro version of 'crdroid' in the begining .
And noew i see in the product name lahaina. I thing this is the oneplus 9 pro name ?
Click to expand...
Click to collapse
Op9p is pro
papad13 said:
Hi why i have ' E:error 21
package is for product oneplus9 but expected oneplus9pro
Even when i have oneplus 9?
Click to expand...
Click to collapse
I have updated op to include instructions for resetting the device name if you've previously flashed a op9pro rom
I also have the same error. I tried it a hundred times.
illusiveairforce said:
I also have the same error. I tried it a hundred times.
Click to expand...
Click to collapse
Have you flashed the boot.img I added to the op? I also received this error in testing since I had flashed the OP9Pro crDroid build.
illusiveairforce said:
I also have the same error. I tried it a hundred times.
Click to expand...
Click to collapse
Your coming from aospa and it's built for op9 pro. So if you didn't msm between there is your issue.
mattie_49 said:
Your coming from aospa and it's built for op9 pro. So if you didn't msm between there is your issue.
Click to expand...
Click to collapse
I did msm already but no fix for the name
audalics said:
Have you flashed the boot.img I added to the op? I also received this error in testing since I had flashed the OP9Pro crDroid build.
Click to expand...
Click to collapse
Yep you are the man, Thanks. That worked
Yeah I guess I didnt msm. Now I kind of got all screwed up. I had to reset and wipe a bunch of times. fastboot the 1.2.7.7DA and then installed Magisk. Now my phone bootloops FOREVER but then finally gets to the homescreen. im talking like 15-20mins. It actually does the boot screen twice. I am lost. Can someone help me get back to square one?
Should I update local storage and do 1.2.7.7 all over again or what
illusiveairforce said:
Yeah I guess I didnt msm. Now I kind of got all screwed up. I had to reset and wipe a bunch of times. fastboot the 1.2.7.7DA and then installed Magisk. Now my phone bootloops FOREVER but then finally gets to the homescreen. im talking like 15-20mins. It actually does the boot screen twice. I am lost. Can someone help me get back to square one?
Should I update local storage and do 1.2.7.7 all over again or what
Click to expand...
Click to collapse
Msm now if one is available for your variant. Or use fastboot stock rom in the threads.
ok please help me out.
So I do adb devices and my device shows up.
i do adb reboot bootloader, works and goes to Fastboot, but then nothing i type works. I do fastboot boot patched_boot_11.2.7.7.LE25DA.img and it just waiting for device.
Now heres another. When I turn my game on, Pubg mobile. It says please enable permissions and I do it. But it still says media only. wont let me do files. i dont get it. Is it cause I accidently mounted system or something.
Please help
illusiveairforce said:
ok please help me out.
So I do adb devices and my device shows up.
i do adb reboot bootloader, works and goes to Fastboot, but then nothing i type works. I do fastboot boot patched_boot_11.2.7.7.LE25DA.img and it just waiting for device.
Now heres another. When I turn my game on, Pubg mobile. It says please enable permissions and I do it. But it still says media only. wont let me do files. i dont get it. Is it cause I accidently mounted system or something.
Please help
Click to expand...
Click to collapse
Make sure your instructions call for fastboot boot <img> instead of fastboot flash boot <img>, mixing up the two would cause issues.
As for the Pubg issue with permissions, I am unsure of what you mean.

[UPDATE / KEEP ROOT GUIDE] JULY 2021 (RQ3A.210705.001) - "CORAL" Magisk-Patched & Stock Boot / DTBO Images

IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!
==========> USEFUL LINKS ==========>
==> DOWNLOAD LATEST SDK PLATFORM TOOLS HERE: https://developer.android.com/studio/releases/platform-tools
==> Official Factory Image / OTA - Downloads / Flashing Guide Here (recommend reading): https://developers.google.com/android/images
==> topjohnwu's Official Magisk GitHub Repo - "Useful Links" Section includes installation instructions, FAQ's, documentations, and more: https://github.com/topjohnwu/Magisk#useful-links
==> @Didgeridoohan's excellent Magisk Troubleshooting / FAQ / Installation Guide (also linked from topjohnwu's GitHub!): https://www.didgeridoohan.com/magisk/HomePage
==> Universal SafetyNet Fix Magisk Module by kdrag0n - Use this module by kdrag0n (make sure to donate / give thanks to him for his amazing work!): https://github.com/kdrag0n/safetynet-fix/releases
==> SafetyNet w/ Xposed - I recommend LSposed over EdXposed (better hooking mechanism, less likely to trigger SafetyNet violation, overall more efficient with handling resources anyway).
<========== USEFUL LINKS <==========
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: twitter dot com /topjohnwu/status/1272136975022084097?s=19 (until I figure out how to stop new XDA from forcing the URL to embed a giant twitter posting in the middle of the post...)
ALL FILES BELOW ARE FOR "RQ3A.210705.001, Jul 2021"!
Magisk v23.0 Patched Boot Image: https://www.androidfilehost.com/?fid=14943124697586362377
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=14943124697586362378
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=14943124697586362379
----------------------------------------------
-------------UPDATE PROCESS BELOW-------------
----------------------------------------------​
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "11.0.0 (RQ3A.210605.005, June 2021". But the general idea is the same for other builds, you just need the correct files for your device.
coral-rq3a.210605.005-factory-dtbo.img: https://www.androidfilehost.com/?fid=14943124697586345553
coral-rq3a.210605.005-factory-boot.img: https://www.androidfilehost.com/?fid=14943124697586345555
July 2021 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-rq3a.210705.001-e4a33ac1.zip
DO NOT BOOT BACK INTO O/S UNTIL ALL STEPS ARE COMPLETED - THIS ENSURES EVERYTHING BOOTS BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
*. make sure installed Magisk (Manager) app version is equal to or greater than the Magisk pre-patched version boot image provided
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot coral-rq3a.210605.005-factory-boot.img
3. fastboot flash dtbo coral-rq3a.210605.005-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload coral-ota-rq3a.210705.001-e4a33ac1.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot coral-rq3a.210705.001-magisk_patched-23000.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it)
This is a 100% seamless update that requires no additional / re-setup of any of my Magisk or EdX/LSposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
-------------------------------------------------
-------------------TROUBLESHOOTING-------------------
-------------------------------------------------​
Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16
Since Magisk v21.x, Core Only mode has been replaced by using Android's built-in Safe Mode. Booting into Safe Mode should essentially boot you back into your system but with all modules disabled (as well as Magisk Hide). Keep in mind that even after you reboot, modules will remain disabled, unless you re-enable them first. Also remember to re-enable Magisk Hide if you had it enabled before.
Please see @Didgeridoohan's guide for more details: https://www.didgeridoohan.com/magisk/MagiskModuleIssues#hn_Core_Only_Mode
It's also worth mentioning, his guide is extremely well-made and contains a lot of useful information that could benefit all Magisk users and modders. I highly recommend looking through it anyway!
Hey man,
Great guide as always!
If I am still on February's update, can I go straight to this update?
Edit: got it figured out, thanks.
thanks
Thanks for the guide.
I just followed your steps again and everything almost worked out - however, for a reason unknown to me, the first sideloading of the OTA file failed (94% "failed to read command"). I had the most recent platform tools downloaded. I just re-did the command to sideload the OTA and then it magically worked without a problem. The heck do I know why.
{
"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"
}
--
The new August patch is out. Anyone tried that out yet?
Morgrain said:
Thanks for the guide.
The new August patch is out. Anyone tried that out yet?
Click to expand...
Click to collapse
I did. Just using the files from the August patch works fine!
Don't forget to updates platform tools as well (newest version is r31.0.3).
I'm sure @i5lee8bit will update his guide soon!
Ghisy said:
I did. Just using the files from the August patch works fine!
Don't forget to updates platform tools as well (newest version is r31.0.3).
I'm sure @i5lee8bit will update his guide soon!
Click to expand...
Click to collapse
lol, you must have typed this literally while I was making / uploading the files and writing the guide, haha
[UPDATE / KEEP ROOT GUIDE] AUGUST 2021 (RQ3A.210805.001.A1) - "CORAL" Magisk-Patched & Stock Boot / DTBO Images
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!! ==========> USEFUL LINKS ==========> ==> DOWNLOAD LATEST SDK PLATFORM TOOLS HERE: https://developer.android.com/studio/releases/platform-tools ==>...
forum.xda-developers.com
i5lee8bit said:
lol, you must have typed this literally while I was making / uploading the files and writing the guide, haha
[UPDATE / KEEP ROOT GUIDE] AUGUST 2021 (RQ3A.210805.001.A1) - "CORAL" Magisk-Patched & Stock Boot / DTBO Images
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!! ==========> USEFUL LINKS ==========> ==> DOWNLOAD LATEST SDK PLATFORM TOOLS HERE: https://developer.android.com/studio/releases/platform-tools ==>...
forum.xda-developers.com
Click to expand...
Click to collapse
Haha, probably!
Next will be Android 12 but I'll be holding out for this one. I need root and mods (EdXposed/Gravity Box).
Ghisy said:
Haha, probably!
Next will be Android 12 but I'll be holding out for this one. I need root and mods (EdXposed/Gravity Box).
Click to expand...
Click to collapse
Isn't Android 12 already root-able?
Morgrain said:
Isn't Android 12 already root-able?
Click to expand...
Click to collapse
Yes it is. Can't speak for EdXposed or Gravity Box as I don't use them, but Magisk works fine on Android 12.
Morgrain said:
Isn't Android 12 already root-able?
Click to expand...
Click to collapse
Oh it is but I don't think EdXposed or LSposed have been ported yet?
GravityBox needs to be updated for each new Android version though.

[ROM][UNOFFICIAL] LineageOS 20.0 [Android 13.0][JUDYLN] [Updated 15-10-2022]

{
"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"
}
A special thanks to @EmanuelCN for work hardly on Device Tree, Kernel and Recovery, without it this Rom wouldn't be possible.
ABOUT LINEAGE:
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS GitHub repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.
• Android OS version: 13.0 / 12.1(A12L)
• Android Release: android-13.0.0_r8 / android-12.1.0_r22
• Build Release date: 2022-10-15
• Security patch: October 5, 2022
• Build author/Device Maintainer: @DanCS1995
• Kernel version/Author: Linux 4.9.235-N0kernel+ by @EmanuelCN
• Device: LG G7 ThinQ
• Device codename: Judyln
DOWNLOAD:
LineageOS 20.0 (Android 13.0) October 5
LineageOS 19.1 (Android 12.1) October 5
OrangeFox
fastboot-tools.zip
fastboot-driver.zip
fix-fastboot.zip (You'll may need this)
ABOUT GAPPS:
Does this Rom come with GAPPS?
No, it doesn't. It means you'll not have "Google Play Store" app or any other Google related service or application in it.
If i wanna use it, wich one should i use?
Make sure to flash the right one that matches to your current Android version, AVOID Stock packages, and the ones that contains "Pixel Launcher" in it, it seams conflicts with Lineage Stock Launcher, and it will give you black screen.
For Lineage 19.1 ONLY!!!
For sure the better one seams to be the one that Lineage recomends you, that you can find it right here in Google Apps | LineageOS Wiki
CHANGELOG 15-10-2022:
• October 5, 2022 Security Patch.
• Whatsapp audio call issues now gone.
• No more "Internal Error" message.
BUGS:
• VoLTE (Will never work on custom roms on LG phones)
• 10 bit video recording (Watching content in 10 bit works, you just cant record video in 10 bit format).
• You tell me!
QUICK FASTBOOT-DRIVER GUIDE INSTALLATION:
How to install:
1. Extract the fastboot-driver.zip.
2. Open device manager
3. Click right on " Android " it should have a yellow warning icon, press on update driver
4. Select browse my computer then press on let me pick from a list of available drivers
5. Press on Have disk and then go to where you have extracted the zip file and select android_winusb.inf
6. Done.
IF YOU FACE SOME FASTBOOT ISSUES DOWNLOAD FIX-FASTBOOT ZIP :
Instructions: Copy it in main directory (usually in C: drive) and run it as administrator, problem solved.
ORANGEFOX GUIDE:
If you have acces to fastboot, download fastboot-driver.zip and fastboot-tools.zip for the tools necessary to boot ofox.
Open the CMD and use the following command to boot ofox:
Code:
fastboot boot ofox-metadata.img
If you don't have access to fastboot, enter in 9008 mode, open qfil and load ofox image on boot_a and boot_b then force reboot (hold volume - and power button for 10s), after it reboots it will get you automatly in ofox.
DISCLAIMER FLASHING OFOX IN QFIL WILL LEAD IN YOUR ROM NOT BOOTING AS LG G7 IS AN A/B DEVICE WHICH MEANS IT DOESN'T HAVE A RECOVERY PARTITION, BOOT IMAGE IS MANDATORY FOR YOUR PHONE TO BOOT, FLASHING OFOX USING QFIL ITS ONLY FOR YOU TO BE ABLE TO FLASH A CUSTOM ROM AS IT OVERWRITES THE BOOT IMAGE WITH THE CERTAIN ROM'S ONE.
INSTALLATION
NOTE: It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
"ROM Firmware Required: Must be on 30F EM, 30D EMW/EAW/AWM, 30D EMW for N model"
CLEAN FLASH : (If on A11/A12/A12L based rom other than Lineage 19.1)
1. Boot in OFOX metadata;
2. Format Data (Press on the recycle bin icon —-> format data ——> type yes);
3. FROM HERE YOU CAN CHOOSE BETWEEN 2 METHODS TO FLASH:
3.1. USING ADB SIDELOAD:​ 3.1.1. Press on "back" and flash the rom using adb sideload (Go to 3 lines in the bottom right corner, choose "ADB Sideload", Then "Swipe-->", open the cmd from adb tools folder in computer, then type "adb sideload", hit "Enter", then < drag and drop the zip over the cmd>);​ 3.1.2. Flash ofox zip the same way through adb sideload, it will automatically reboot to ofox after flashing is done;​ 3.1.3. Flash gapps; (Only if the rom does not contain gapps);​ 3.1.4. Flash magisk (Optional);​
3.2. OR IF YOU HAVE A MICROSD CARD, YOU CAN FOLLOW THIS:​ 3.2.1. Move the rom and ofox, and gapps(if you will use) zip file into your microsdcard;​ 3.2.2. Press on "/sdcard" area and choose "Micro SDCard", navigate straight into your rom zip file, then press on it, then "swipe ---->", it will start flashing it;​ 3.2.3. After flash the rom, locate your ofox zip file and flash it as you did with the rom;​ 3.2.4. Flash gapps; (If you want);​ 3.2.5. Flash Magisk (Optional);​
4. Change filesystem to f2fs (Go to 3 lines in bottom right corner ----> manage partitions ----> select data -----> change fs ------> f2fs);
5. Reboot.
DIRTY FLASH/UPGRADE ROM : (If you are already on Lineage 19.1)
• Boot in OFOX metadata;
• Flash the rom zip;
• Flash ofox zip, it will automatically reboot the phone to ofox after the flashing is done;
• Flash gapps (ONLY IF THE ROM IS WITH GAPPS ALREADY, MAKE SURE TO FLASH THE SAME ONE);
• Flash magisk (Optional);
Sources and Documentation
• ROM Source Code
• Kernel Source
Created 2022-05-24
Last Updated 2022-10-15
Screenshots:
Can the call be made? (Sim)
buymoney said:
Can the call be made? (Sim)
Click to expand...
Click to collapse
yes
fzdfdzff
Will 30E AWM work or do I need to reflash to 30D?
debianmain1 said:
Will 30E AWM work or do I need to reflash to 30D?
Click to expand...
Click to collapse
You can try with 30E AWM
deleted
Would it pass safetynet with microg, zygisk etc? I've heard ungoogled experience improved a lot recently
So I Accidently flash ofox to boot a/b with qfil and now my phone won't boot. Now the screen just show
"Your device has failed a routine safety check and will not boot." Is there a way to fix my phone so I can boot it back?
XScorpionX72YT said:
So I Accidently flash ofox to boot a/b with qfil and now my phone won't boot. Now the screen just show
"Your device has failed a routine safety check and will not boot." Is there a way to fix my phone so I can boot it back?
Click to expand...
Click to collapse
I also can boot to firmware update mode only and cant boot to edl...
09mysh said:
Would it pass safetynet with microg, zygisk etc? I've heard ungoogled experience improved a lot recently
Click to expand...
Click to collapse
I'm not familiar with microg, sorry
XScorpionX72YT said:
So I Accidently flash ofox to boot a/b with qfil and now my phone won't boot. Now the screen just show
"Your device has failed a routine safety check and will not boot." Is there a way to fix my phone so I can boot it back?
Click to expand...
Click to collapse
You need to get the boot_a.img and dtbo_a.img from the kdz stock rom a10 file and you can try flashing it in both boot_a and boot_b, dtbo_a and dtbo_b in qfil, this might fix it. ANd edl is still there, you need to try a fill more, and you will do it
XScorpionX72YT said:
So I Accidently flash ofox to boot a/b with qfil and now my phone won't boot. Now the screen just show
"Your device has failed a routine safety check and will not boot." Is there a way to fix my phone so I can boot it back?
Click to expand...
Click to collapse
I have also faced that issue. in my case, only edl mode was working. I followed the following steps & it worked for me. You should give it a try.
[Guide - HOW TO] Recover LG G7 (or other newer LG phones) from EDL or 9008 mode.
****** Unbrick all LG G7 models ****** ********** This guide has updated into two methods ********** (i). Recover from any boot problem to system or download mode.(which is defined below) This...
forum.xda-developers.com
XScorpionX72YT said:
I also can boot to firmware update mode only and cant boot to edl...
Click to expand...
Click to collapse
go over to the following link :
[Guide - HOW TO] Recover LG G7 (or other newer LG phones) from EDL or 9008 mode.
****** Unbrick all LG G7 models ****** ********** This guide has updated into two methods ********** (i). Recover from any boot problem to system or download mode.(which is defined below) This...
forum.xda-developers.com
Is there any way to enable VoLte on custom ROMs on LG G7?
sandip999 said:
Is there any way to enable VoLte on custom ROMs on LG G7?
Click to expand...
Click to collapse
sadly not, even if you just do a crosflash with another stock rom that isnt from your region, you cant use VoLTE, LG's fault
Hi,
I want to put this Lineage 19 rom on my G7. Can you help me please? My G7 is LM-G710EM, bootloader is unlocked. Its running LG's android 10 up to 01/11/2020 (that appears to be my final update possible - though I thought there was one in 2021?? - no available updates showing there now anyway)
1. (very noob question) when we say 'stock' do we mean just 'what came with the phone, and its subsequent updates?' As in, we didn't install any roms or recovery at this point. Is that right? Thats what i have right now. UK phone.
2. My firmware is V30h-EUR-XX, in this thread it says I need: "ROM Firmware Required: Must be on 30F EM, 30D EMW/EAW/AWM, 30D EMW for N model" - So do I need to find and install the 30F EM firmware? Where can I find the files and instructions please? Is it here: https://lg-firmwares.com/lg-lmg710em-firmwares/ ? ...Or is my V30h ok without this as its newer firmware?
**KEY QUESTION**
3. Could someone please outline for me the 'roadmap' for getting my G7 from: LG A10 -- to ---> L19
(Please correct / advise below)
1. use ofox to replace firmware 30H with 30F
2. use ofox to install L19 over existing LG A10
Is that right? ...or are there steps missing? e.g. I need to install x, then do y, ... and then install L19, or something like that?
Very grateful for any help you can give!
I am a noob but I had some success already putting cyanogen / lineage roms on old devices:
amazon kindle fire, my old HTC oneX, Samsung Galaxy Trend, LG G4 ...all still working fine ;-) ...thanks to XDA.
(I might not be able to reply straight away - work hours - but I'll try to get back asap)
Many Thanks,
tommy_brock said:
Hi,
I want to put this Lineage 19 rom on my G7. Can you help me please? My G7 is LM-G710EM, bootloader is unlocked. Its running LG's android 10 up to 01/11/2020 (that appears to be my final update possible - though I thought there was one in 2021?? - no available updates showing there now anyway)
1. (very noob question) when we say 'stock' do we mean just 'what came with the phone, and its subsequent updates?' As in, we didn't install any roms or recovery at this point. Is that right? Thats what i have right now. UK phone.
2. My firmware is V30h-EUR-XX, in this thread it says I need: "ROM Firmware Required: Must be on 30F EM, 30D EMW/EAW/AWM, 30D EMW for N model" - So do I need to find and install the 30F EM firmware? Where can I find the files and instructions please? Is it here: https://lg-firmwares.com/lg-lmg710em-firmwares/ ? ...Or is my V30h ok without this as its newer firmware?
**KEY QUESTION**
3. Could someone please outline for me the 'roadmap' for getting my G7 from: LG A10 -- to ---> L19
(Please correct / advise below)
1. use ofox to replace firmware 30H with 30F
2. use ofox to install L19 over existing LG A10
Is that right? ...or are there steps missing? e.g. I need to install x, then do y, ... and then install L19, or something like that?
Very grateful for any help you can give!
I am a noob but I had some success already putting cyanogen / lineage roms on old devices:
amazon kindle fire, my old HTC oneX, Samsung Galaxy Trend, LG G4 ...all still working fine ;-) ...thanks to XDA.
(I might not be able to reply straight away - work hours - but I'll try to get back asap)
Many Thanks,
Click to expand...
Click to collapse
Hey, you are fine with your 30H firmware, you should have no problems with it.
Anyway, to change firmware you don't use ofox, you use LGUP
the guide you can find on this thread
Cross-Flash Oreo or Pie firmwares for all LG G7, G7+ dual sim Thinq except t-mobile​
Once in ofox you can do from "CLEAN FLASH" steps of this guide
DanCS1995 said:
Hey, you are fine with your 30H firmware, you should have no problems with it.
Anyway, to change firmware you don't use ofox, you use LGUP
the guide you can find on this thread
Cross-Flash Oreo or Pie firmwares for all LG G7, G7+ dual sim Thinq except t-mobile​
Once in ofox you can do from "CLEAN FLASH" steps of this guide
Click to expand...
Click to collapse
Hi,
Thanks so much for your reply.
I will not try to flash firmware as you think mine will be OK, but I will check out the linked information you gave for my own understanding.
I will use ofox and follow the 'clean flash' guide from here, as you advise.
That's great! Now I have a plan for action
I will try this over the next couple of days.
Many thanks,
Success!!
Thanks for your help, I have L19 running on my G7 now. the install was painless! all seems good and working. I'm just trying it out, but so far, smooth. It is really nice to have something so up to date running on the phone. also so clean and simple, without all the crud the original system had. a huge improvement.
I have some questions,
- After reboot, trebuchet gives me an Android System message: 'There's an internal problem with your device. Contact your manufacturer for details'
...after I dismiss it, I don't see it again. Have you seen this message? It is too cryptic for me to troubleshoot, but it doesnt seem to be causing a problem (as yet....?)
- Android System Trust Security throws up 2 alerts: This build was signed with public keys ; SELinux is not enforcing, your security has been weakened
...I'm guessing these are ok?
- In the Lineage camera app, the wide camera does not function (only main and front present).
I already put Open Camera app on there, which recognises all three cameras, and gave me great results before this on the G7, so I use Open Camera anyway.
- Can anyone recommend a GCam build for this rom? even better if its older and I don't have to root and do the 'buffer fix' stuff.
If anyone could advise, That would be great thank you!
Cheers,

[AOSP ROM] [OFFICIAL] | Android 14 | GSI Install Instructions for Galaxy Tab S6 (SM-T860, SM-T865)

{
"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"
}
Hi everybody, I have been looking for a way to get an official version of Vanilla Android 14 on the Tab S6 for and wanted to make sure the community finally had access to a fully working and sufficiently detailed guide.
This ROM improves battery life by 200%, it's absolutely insane.
Every source, link or file referenced in this guide is 100% official and safe.
Cheers!
Download Firmware + Extract:​
Install SamFirm and download the latest firmware for the Tab S6.
(You will also need to install Visual Studio C++ 8 & 9 for this software to function properly)
SamFirm Tool
Download the latest version of SamFirm Tool, which helps you download the Samsung Stock Firmware (ROM) for free.
samfirmtool.com
Install 7Zip and extract the firmware zip.
Then open the CSC file with 7zip and extract the PIT.
Unlock Bootloader
Enable Developer Options and turn on OEM Unlocking
Disconnect USB/power cables and turn your device OFF
Hold both Volume buttons (do not press Power) and plug in the USB cord connected to your PC
The download/unlock screen should come up immediately. Select the option for device unlock mode.
Download TWRP:
Download the official TWRP and vbmeta image
TWRP > https://twrp.me/samsung/samsunggalaxytabs6qcomwifi.html
vbmeta > https://dl.twrp.me/gts4lv/vbmeta.tar.html
Download Official AOSP / Android 14 Image:
The official Android 14 (or 13/12/11) GSI is available on Google's developer page and needs to be extracted via 7zip. (This will also contain a vbmeta.img but disregard it)
(GMS = Gapps | No GMS = Vanilla | FLOSS = Open Source Apps Only)
(Make sure to get a arm64 version) https://developer.android.com/about/versions/14/gsi-release-notes.html
If you prefer the consumer grade "prettier" version of AOSP, you can also download one of the arm64 images provided by phhusson on Github, who exclusively uses official sources code, as well.
https://github.com/phhusson/treble_experimentations/releases
You can also download one of the official daily builds directly from the ACI Project's master-branch (Android Continuous Integration) which represents the literal bleeding edge of AOSP straight from Android : https://ci.android.com/builds/branches/aosp-master/grid?
Flashing Firmware with Odin
Download Odin Flash Tool from a safe source.
Odin - Download
Odin: Samsung-Geräte rooten und flashen - Kostenloser Download für ✓ Windows
www.netzwelt.de
Put the Tab S6 in Download Mode by pressing both Volume Up + Volume Down, while simultaneously connecting the USB cable. (The tablet needs to be off)
Open Odin and add the Firmware Files to the appropriate slots
BL > BL , AP > AP, CSC > CSC
Then click on PIT and add the previously extracted PIT file
Lastly click options and select Nand Erase, Re-Partition, while unselecting Auto Reboot
Flashing TWRP & vbmeta with Odin
After successfully flashing hold down Power Button + Volume Down for 7 seconds but be ready to immediately hold down Volume up + Volume Down to re-enter Download Mode.
(USB Cable needs to be connected at all times)
(If you missed your chance and it's booting, hold down Power Button + Volume down to reset and try again)
Once back in Download Mode click Reset in Odin
Deselect Auto Reboot in the Options again
Then add the TWRP image in AP and vbmeta.tar in the CP slot.
Wiping Cache & Partitions
After flashing hold down Power Button + Volume for 7 seconds and immediately hold down Power Button + Volume Up the entire time until you see TWRP.
Once inside TWRP wipe Dalvik Cache and Cache in the Advanced Wipe menu. Subsequently re-enter the wipe menu, select Format Data and type yes.
After this (USB cable still connected) make sure the Internal Storage is mounted and transfer the system.img (extracted from the AOSP GSI zip) to the tablet
Finishing Up
In TWRP click Install, select the system.img and choose system image.
Flash it, Reboot to System and your DONE!
Current build - Android 14:
Date: April 12, 2023
Build: UPB1.230309.014
Build type: experimental
Security patch level: April 2023
Google Play Services: 23.09.12
Working:
Fingerprint
Hardware Buttons
SDCard
Wifi
Bluetooth
Gapps and Google Setup
Tablet is very fast!
Charging
USB File Transfer
Audio
Video out for USB-C
Auto-rotate
GPS
Official Samsung Keyboard Physically attached working fine too!
Themes
Colours
Mic
SPen
Not Working:
Top Speakers
This issue has already been fixed in the Beta Version which will soon be moved to stable.
Current build - Android 13 (Beta):
(at the time of writing this)
Date: March 29, 2023
Build: T3B2.230316.003
Build type: experimental
Security patch level: March 2023
Google Play Services: 23.02.14
Generic System Image releases | Platform | Android Developers
developer.android.com
Many, many thanks for this.. If i understand correctly, we can choose the android 13 file which includes gaps, so to have Google services?
Also there must be an error. The pit file is in CSC file and not in AP file.
Il try it, I'll post the results when i do it.
Thanks again!
I just installed it. Working fine. It does have gaps and playstore and it is vanila android, doesn't have samsung ui.
I suppose i can install in twrp magisk to root it.
After i flashed twrp and restarted, it didn't boot in twrp, but all screen had an error message with yellow txt, something about microsd (which i didn't had). I restarted again to boot in twrp, and this time it did boot in twrp, so i did flash image.
Thanks again!
Anyone knows how to root it?
After flashing system image from android 13, twrp is deleted as i understand. Trying to boot in recovery, it boots to normal recovery, not twrp.
I flashed in odin again only twrp and vbmeta
(TWRP image in AP and vbmeta.tar in the CP slot.). Only those files i used, I'm not sure if this is correct. Anyway, i booted in twrp this time. I couldn't find download folder where i had magisk.zip to flash, trying to root, so i finally just restarted the tablet. It booted ok, but when i tryed again to boot in twrp, it booted in normal recovery again, not twrp.
---If anyone can show me the contact steps to install twrp and root..
--- Aslo in this 13 rom, there isn't fingerprint scanner. Is there any way (xposed, something) to install it?
Thanks!
Although rom is fantastic, with excellent battery life, Ulunfortunately i found a bug which is important for me. Only the 2 right speakers work. The other 2 dont. If some time in the future there is a fix to this, it would be much appreciated. Until then, i have to go to android 12 original..
sosimple said:
Although rom is fantastic, with excellent battery life, Ulunfortunately i found a bug which is important for me. Only the 2 right speakers work. The other 2 dont. If some time in the future there is a fix to this, it would be much appreciated.
Click to expand...
Click to collapse
The speaker issue has already been fixed in the Daily Beta Version of Android 13 offered on the Google Developer's page. Just flash one of those.
Versions des images système génériques | Plate-forme | Android Developers
developer.android.com
tablet_seeker said:
The speaker issue has already been fixed in the Daily Beta Version of Android 13 offered on the Google Developer's page. Just flash one of those.
Versions des images système génériques | Plate-forme | Android Developers
developer.android.com
Click to expand...
Click to collapse
Ok thanks. I'll try the beta.
sosimple said:
Ok thanks. I'll try the beta.
Click to expand...
Click to collapse
Additionally, you can also try the arm64 image from ACI's master-branch. This is literally straight from Android and built/updated hourly.
https://ci.android.com/builds/branches/aosp-master/grid?
I just flashed the one that was released this morning and all four speakers work.
tablet_seeker said:
Additionally, you can also try the arm64 image from ACI's master-branch. This is literally straight from Android and built/updated hourly.
https://ci.android.com/builds/branches/aosp-master/grid?
I just flashed the one that was released this morning and all four speakers work.
Click to expand...
Click to collapse
Which version/build did you use? Also, for updates, does the system>update function within the room work or does the full zip file need to be flashed each time?
weinbers said:
Which version/build did you use? Also, for updates, does the system>update function within the room work or does the full zip file need to be flashed each time?
Click to expand...
Click to collapse
The first column named "aosp_arm64"
Branch Grid
ci.android.com
That will lead you to this page: https://ci.android.com/builds/submitted/9909221/aosp_arm64-userdebug/latest where you'll choose "aosp_arm64-img-9909221.zip"
As for your question about updates, it depends on whether your device supports seamless system updates. The SM-T860 and SM-T865 do not support it.
AOSP GSI with Android 14 has just been released! You can flash it right now with this guide.
Android 14 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 14 preview builds.
developer.android.com
tablet_seeker said:
The first column named "aosp_arm64"
Branch Grid
ci.android.com
That will lead you to this page: https://ci.android.com/builds/submitted/9909221/aosp_arm64-userdebug/latest where you'll choose "aosp_arm64-img-9909221.zip"
As for your question about updates, it depends on whether your device supports seamless system updates. The SM-T860 and SM-T865 do not support it.
Click to expand...
Click to collapse
This one have gapps included ?
Stable ?
Thanks for your work
Amr.Bendari said:
This one have gapps included ?
Stable ?
Thanks for your work
Click to expand...
Click to collapse
GMS = Google apps included
The regular arm64 image is Vanilla Android without Gapps.
You can also grab daily gsi builds from ci.android.com
Android 14 is brand new, so it's not perfectly stable but definitely usable.
In the title you have Android 14.. though then in Post #1 you have Android 13?
I did try 14 though they brightness did not work properly? and the it kept freezing? You said "Android 14 is brand new, so it's not perfectly stable but definitely usable." which version did you use? Cause the one i tried definately wasn't
Hello ,
Thank you for sharing the info
I have checked Rom and answered my own questions .
Widevine is L3 (so only 480p on Netflix)
Performance in Hearthstone is way better .
Unfortunately for me only bottom speakers works , i have checked both 14 and 13 beta
When using spen or Samsung keyboard pointer is set to vertical orientation when tablet is in Horizontal position ,
So they are unusable .
Cannot relock boatloader since it is erroring out on the VBmeta
Hello!
Has anyone rooted now?
How about updates?
Can I just play it like that? I'm currently on Android 13...
Is there any way to use Samsung Apps like SNotes?
Thats the only thing I would need from OneUI
niklas389 said:
Is there any way to use Samsung Apps like SNotes?
Thats the only thing I would need from OneUI
Click to expand...
Click to collapse
maybe with some magisk modules.. or if your lucky just by flashing the apk
Sage said:
In the title you have Android 14.. though then in Post #1 you have Android 13?
I did try 14 though they brightness did not work properly? and the it kept freezing? You said "Android 14 is brand new, so it's not perfectly stable but definitely usable." which version did you use? Cause the one i tried definately wasn't
Click to expand...
Click to collapse
Thanks, fixed.
The Preview version on Google's main GSI site is unstable. You need to get the latest build on ci.android.com
They are literally building and releasing new artifatcs every 30 minutes.
Also, do you know where to get a Disabler for force encryption on Android 13 for the tab s6? Can't find anything.
Scodera said:
Hello!
Has anyone rooted now?
How about updates?
Can I just play it like that? I'm currently on Android 13...
Click to expand...
Click to collapse
Sure. Just download the Magisk APK from Github.
Install the Magisk APK, then extract the boot.img from your firmware files. Transfer the boot.img to your tablet, patch it with Magisk and then flash this patched img in TWRP choosing the boot option. There are tons of guides for this online.
No updates bc the tab S6 does not support seamless updates. You have to flash new versions. But its super fast because you just flash system and ur good.
niklas389 said:
Is there any way to use Samsung Apps like SNotes?
Thats the only thing I would need from OneUI
Click to expand...
Click to collapse
Yes. I don't trust APKMirror so what I do is install the stock ROM from the latest samfirm firmware. Root it. Install File Commander, or any other root file manager.
Then navigate to /data/app and grab the Samsung Notes APK. All other apps are stored in this directory BTW. Then just install the APK once you flashed AOSP GSI
niklas389 said:
Is there any way to use Samsung Apps like SNotes?
Thats the only thing I would need from OneUI
Click to expand...
Click to collapse
If you still want to keep using Samsung apps under a different OS like this one (AOSP, A14) install the Magisk module " Xmlpak a road to vendor apps".
After reboot, the Samsung apps you want to use again should show up in the app store for you to install. If not you can use APKMirror to download the APKs. Contrary to what a user posted above, this site is more than safe and verified.

Categories

Resources