{
"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,
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a Official Build of madOS ( based on AOSP Oreo ) for Wiko Fever (2gb ram and 3gb ram) with MTK 6753 SoC and its clones:
Micromax Canvas 5 E481
Blu Life One X
Myphone 36
Qmobilez10
madOS is based on pure A.O.S.P. with many additional customizations and MediaTek support.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Working:
RIL (Calls /SMS, Data connection, etc)
Wifi
Bluetooth
FM Radio
All Sensors
Lights;
Both storages & MTP
HW de/encoding
Camera (photos and video)
GPS & aGPS
Audio
madOS Extras (the features ya'all used too), plus, some new features we added on Oreo)
Not working:
XDA:DevDB Information
madOS_O_FEVER, ROM for all devices (see above for details)
Contributors
DerTeufel1980, fire855, superdragonpt
Source Code: https://github.com/MediatekAndroidDevelopers
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: unlocked bootloader, twrp
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2018-03-19
Created 2018-03-13
Last Updated 2018-03-22
First time Install Instructions
0) Preparation
0.1) Backup your important data to PC
0.2) Ensure you are running Wiko Fever Android 6 already (also/especially when your device is not wiko fever, but a clone). If you are not, please update to it, before continuing here (replace the preloader from the wiko rom with your stock one, then use 'firmware upgrade' mode in sp flashtool. NEVER use 'format all + download')
Extra steps, if you are on blu life one x:
https://forum.xda-developers.com/showpost.php?p=76003104&postcount=81
0.3) Download “twrp_wiko_fever_oreo.img“: [url]http://www.mediafire.com/file/e96x8ltlyka392e/twrp_wiko_fever_oreo.img[/URL]
0.4) Download “madOS_8.1.0_fever_2018xxyy.zip“ [url]https://www.facebook.com/MediatekAndroidDevelopers/[/URL]
0.5) Optional, Download “Google Apps (aka Gapps)“: [url]http://opengapps.org/[/URL]. Choose: “ARM64“, “Android 8.1“, “nano“ or “pico“ package
1) Unlock bootloader (if not done already):
1.1) Boot for first time your device. I recommend to NOT register/login/add Wifi/add accounts/etc., because the unlock process DELETES all your data in the device. So to go more fast, skip all, and go directly to SETTINGS. In section ABOUT DEVICE, enable the developer options with eight time picks over “Build number”. Then in SETTINGS/DEVELOPER OPTIONS, enable the option “OEM unlocking” and “USB debugging” (if not enabled already), and choose to alollow usb debugging in the popping up window.
1.2) Boot the device in the BOOTLOADER mode (using ADB: "adb reboot-bootloader"). Execute in your computer the command “fastboot oem unlock”, say YES with “vol+” and “power” buttons. Then select reboot. This ERASES completely your device (factory restore), but the bootloader will be UNLOCKED! Two reboots needed.
2) Flash the recovery and boot to it. (choose option a) if you don't have another TWRP already installed, else choose b))
2.1a) Boot in the BOOTLOADER mode (using ADB: "adb reboot-bootloader").
Then execute command “fastboot flash boot twrp_wiko_fever_oreo.img”;
and then “fastboot reboot” (this is a trick to directly bring you to the newly flashed recovery. You can't boot up your current/stock rom at this point anymore).
2.1b) Boot to your current TWRP. Choose install --> image, and select “twrp_wiko_fever_oreo.img“. Then choose “recovery“ as the target. After few seconds, and succesful installation, hit “back“ several times, then go to “reboot --> recovery“
3) Install
3.0) Optional, but recommended: Go to "Wipe --> Advanced Wipe", click "Cache" and then "Repair or Change File system". Then select "Change File system" and choose "F2FS". Swipe to confirm.
Hit "back" three times (you can again choose a partition to change now). Choose "Data" and do as above.
Hit "back" several times, to get back to the main menu. Choose "Reboot --> Recovery".
3.1) While already in recovery (TWRP), connect your phone to pc, and copy “madOS_8.1.0_fever_2018xxyy.zip“ and the Google Apps to your phone.
3.2) Go to "Wipe", and directly slide the slider to the right.
3.3) Get back to main menu with the "back" button
3.4) Go to "Install" and hit “madOS_8.1.0_fever_2018xxyy.zip“, then uncheck all boxes and hit "Add more zips", now choose the Google Apps.
Confirm installation by swiping the slider to the right.
3.5) Reboot System
Click to expand...
Click to collapse
Follow up Install Instructions
Download rom and gapps
boot to recovery
flash rom and gapps
optional: flash superSu/Magisk
reboot system
General F.A.Q.
Q: What the hell is madOS ?
A: madOS, (M.A.D. Team OS), is a ROM based on pure A.O.S.P. with extended capabilities and customizations made by or merge/adapted by M.A.D. Team.
Q: Which recovery should I use for this ROM?
A: Latest M.A.D. TWRP 3.2.1-0 recovery for OREO 8.1.0
Q: How do i flash new recovery ?
A:
1: You can flash it with a scatter file
2: You can simply flash it from the existing twrp recovery: Install> Install image> Select Oreo TWRP> Select "Recovery" as partition to flash.
Reboot to recovery to use new one
Q: Do i need to make full wipes?
A: YES, dont come crying at me, if you didn't .... ;p
Q: What is "full wipes" ?
A: To Wipe : Cache; System; DATA ...
Q: What should i use f2fs or ext4?
A: Both are supported, choose the one you desire
Q: Does this rom have any Theme support
A: Yup, We have working Theme Engine (madOS extras)
Update: On Oreo 8.1.0:
- We have extended Theme support even further ( madLauncher, messaging, etc)
- As well as many fixes
Q: Some translations are missing for my language, can I help?
A: Sure you can, please check our translations repo available here , you can either do a pull request, or if you don't know how to work with git, sent us the XML. Strings for your language ( Check Readme on repo).
Q: I want to report a bug(s) do you have an issue tracker?
A: Yeah... madOS issue tracker
Q: What's working ?
A: Check first Post for current status
Q: App "x" doesn't work, why?
A: Probably not compatible with OREO yet, feedback is welcome
Q: Is the rom rooted?
A: NO, But you can easily root with :
1: Magisk ( v14 onwards.)
2: Super SU ( v2.82 onwards)
IF there are problems in rooting, you need to report it to the root-threads...There's nothing we can do
Q: Should i root together with rom ?
A: Not advised.. mainly the Magisk that gives some weird issues...
Flash ROM and GAPPS (if you use gapps), after first boot get back to recovery and flash your desire rooting method
Q: Does xposed work?
A: Is there Xposed for O? ... then no ;p
Q: How is battery life with Oreo?
A: Pretty awesome
Q: Does this build support Vulcan?
A: No....duh! v
Q: Does doze work in this build?
A: Yup
Q: when will (feature/issue here) be fixed?
A: NO ETA , please
Porting F.A.Q.
No porting support, no port questions allowed on this thread, and porting PMs will be auto-deleted, porting replies will be reported as well
G.APPS F.A.Q.
Q:What GAPPS package should I use?
A: openGapps arm64 nano/pico
Q: How to properly install GAPPS?
A:Flash Rom + Flash Gapps at once
CREDITS and Thanks
madOS Team
Our translators, credits list here
A.O.S.P.
Pure Nexus
AOSPA
DU (Dirty Unicorns)
Omni
HELP supporting madOS
We do this on our free time, however we do have costs on maintaining this :/
Any donation is highly appreciated
You can donate by using
this link
If the above doesn't work in your country, then you can directly donate by using this e-mail adress: [email protected]
About madOS Proprietary Apps
You are NOT allowed by any means, to use our madOS apps on any other build, your rom
This is exclusively for OFFICIAL madOS ROM releases
@To Moderators: Feel free to clean the thread, whenever users start spamming, severe OT, or questioning about porting...
Changelog 19th March 2018:
fixed offline charging
fixed proximity and light sensor
fixed applying smartwake settings after reboot
Facebook release post: https://www.facebook.com/notes/mad/rom-810-official-mados-wiko-fever-mt6753/1640799096003857/
for whatever reason, devDB is not working (very well) at the moment...causing this thread to be shown up, hours after i created it....now it's finally here and updated...and can be used
Thank u so much sir...we owe you?
superdragonpt said:
Android Oreo released
https://forum.xda-developers.com/android/development/rom-official-mados-wiko-fever-clones-t3762804
Click to expand...
Click to collapse
superdragonpt said:
The ROM was made using an Wiko device in the bring up
I know very well this TINNO devices, that are rebranded to many OEMs
In case of baseband (ie: BLU,Qmobile, MMX, you should use your stock baseband modem and place it under vendor/etc)
Cheers
PS: can you, that have other clones ( non-wiko) send us your working baseband?
(This way, we could perhaps just made an flashable zip for baseband or so)
Click to expand...
Click to collapse
Here is firmware folder(baseband) from Life One X with MM update.
Opened an issue about some sensors
https://bitbucket.org/maadteam/mado.../103/some-sensors-light-proximity-not-working
mrmazak said:
Here is firmware folder(baseband) from Life One X with MM update.
Click to expand...
Click to collapse
FERRARI81 said:
Opened an issue about some sensors
https://bitbucket.org/maadteam/mado.../103/some-sensors-light-proximity-not-working
Click to expand...
Click to collapse
Great
This .zip is pushing to system/etc, so this .zip won't work here on Oreo, where everything is moved to vendor/etc
For the time being for the blu, you can either updated the updater-script to push to "vendor" instead of "system" or root it, and move your baseband manually to vendor/etc
About the alsps ( brightness ) what's the sensor used in blu?
We need to enabled it I suppose
Cheers
superdragonpt said:
Great
This .zip is pushing to system/etc, so this .zip won't work here on Oreo, where everything is moved to vendor/etc
For the time being for the blu, you can either updated the updater-script to push to "vendor" instead of "system" or root it, and move your baseband manually to vendor/etc
About the alsps ( brightness ) what's the sensor used in blu?
We need to enabled it I suppose
Cheers
Click to expand...
Click to collapse
So the sensor.lib from Blu?
I will pull it and share.
superdragonpt said:
About the alsps ( brightness ) what's the sensor used in blu?
We need to enabled it I suppose
Cheers
Click to expand...
Click to collapse
Ehm...I have not blue, I have original Wiko Fever
And...I'm noob ...in wich way I could check what's the sensor?
FERRARI81 said:
Ehm...I have not blue, I have original Wiko Fever
And...I'm noob ...in wich way I could check what's the sensor?
Click to expand...
Click to collapse
just because adaptive brightness is not working , does not mean it is the sensor.
If sensor was not working , there is another test (check) you can do.
make a call, then put phone to head and see if screen goes off.
I had before when light sensor was not set correctly, when making a call the screen went black as soon as start a call, then could not get screen back on till 30 seconds after other end hung up the call.
I am away from my LOX now and for few days , so cant give direct test of light sensor.
attached just in case is usefull here are sensor libs from BLU-LOX. They are in /system/lib/hw and /system/lib64/hw.
I believe on oreo they go into /vendor/
Can we flash it over stock Lollipop ROM of Micromax Canvas 5 ??
I have a question that Can I flash it over the stock Lollipop ROM ?? existing kernel is 3.10.65.
Thanks
mrmazak said:
just because adaptive brightness is not working , does not mean it is the sensor.
If sensor was not working , there is another test (check) you can do.
make a call, then put phone to head and see if screen goes off.
I had before when light sensor was not set correctly, when making a call the screen went black as soon as start a call, then could not get screen back on till 30 seconds after other end hung up the call.
Click to expand...
Click to collapse
It doesn't work in call too : the screen is always on.
QUIZILLA said:
I have a question that Can I flash it over the stock Lollipop ROM ?? existing kernel is 3.10.65.
Thanks
Click to expand...
Click to collapse
Please remove the quote of the whole FAQ. This is totally useless to ask your question...
You need to flash wiko mm rom first
FERRARI81 said:
It doesn't work in call too : the screen is always on.
Click to expand...
Click to collapse
I'll check it today
Hello, I write from Padova, Italy,
I have the WIKO FEVER 3GB,I have the problem that after upgrading to MM (Android 6.0), device not connects to PC and no charge. The device is recognized ONLY if it turns off.
Can I do this update procedure with this problem?
I can not connect to the PC because device is not recognized. Can you help me? Can I root through an app installed by the playstore without using pc? Thank you so much for the answers.
Riccardo
ianto:
Rikadoo said:
Hello, I write from Padova, Italy,
I have the WIKO FEVER 3GB,I have the problem that after upgrading to MM (Android 6.0), device not connects to PC and no charge. The device is recognized ONLY if it turns off.
Can I do this update procedure with this problem?
I can not connect to the PC because device is not recognized. Can you help me? Can I root through an app installed by the playstore without using pc? Thank you so much for the answers.
Riccardo
ianto:
Click to expand...
Click to collapse
Why root? To update to oreo, you don't need root... But you still need to copy the new rom to your phone, as well as unlock the bootloader and install the twrp recovery. This needs to be done in fastboot mode by pc. I'd suggest to just try it
Unfortunately I am not very experienced, but I am very interested in solving my problem. I want to install this ROM, but without having to connect the device to the PC.
If I copy the ROM on the SD card. Can I then install?
I am in process of installing new oreo twrp and MADOS.
During install of TWRP, I loose adb authorization. (adb session is "unathorized")
in "prop.default" it has
Code:
ro.secure=1
security.perf_harden=1
ro.adb.secure=1
ro.allow.mock.location=0
ro.debuggable=0
is this intentional?
additional question,
Adb authorize connection window comes up multiple times even after putting check mark on remember this choice.
I think the adb auth problem is my pc, my other phone just started to do this too.
edit:
I have tried couple times to use blu firmware inside vendor folder. But not able to get baseband to be known.
tried just adding blu files ontop of original rom files.
tried removing rom files and adding blu files
tried removing whole folder then adding blu folder
each time I get unknown baseband.
I checked permission and ownership each way I tried and I set it to rw:r:r and root:shell just like original rom version, but not working for me.
One and more questions,....
1. Our bootloader is blocked or already unlocked?
2. If is locked, to unlock the bootloader of our device wiko fever which app I have to install?
3 if isn't locked, how I install a custom recovery like twrp manager?
4 how I boot the custom recovery twrp manager? Maybe if I switch off the device and reboot it, starts automatically the custom recovery?
5 at the end, from twrp can I flash the ROM Oreo?
AHH , last question, can I flash this ROM from my phone with Android MM?
mrmazak said:
I am in process of installing new oreo twrp and MADOS.
During install of TWRP, I loose adb authorization. (adb session is "unathorized")
in "prop.default" it has
is this intentional?
additional question,
Adb authorize connection window comes up multiple times even after putting check mark on remember this choice.
I think the adb auth problem is my pc, my other phone just started to do this too.
edit:
I have tried couple times to use blu firmware inside vendor folder. But not able to get baseband to be known.
tried just adding blu files ontop of original rom files.
tried removing rom files and adding blu files
tried removing whole folder then adding blu folder
each time I get unknown baseband.
I checked permission and ownership each way I tried and I set it to rw:r:r and root:shell just like original rom version, but not working for me.
Click to expand...
Click to collapse
Someone already uploaded vendor files for his model... Was it you? If not, please upload it for us
Requirements:
1. Unlocked Bootloader
2. You need ramdisk of current version.
a) Install this program from this link (you need the program installed in order to download the files)
Releases · ProfessorJTJ/HISuite-Proxy
Modifying HiSuite and manipulating it's connection data to install Roms before they officially get released. - ProfessorJTJ/HISuite-Proxy
github.com
b) Download Stock Firmware from here https://professorjtj.github.io.
c) Look for the brand and model and download the update.zip
3. Extract the zip. you will get an update.app
4. In Huawei Extractor, enter settings and uncheck "Verify header checksum" and "verify file checksum". then select update.app from its location. in the list find "RAMDISK.img"
5. a) Download Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip from here.
b) Download TWRP-323.img from here
TWRP-3.2.3.img
Shared with Dropbox
www.dropbox.com
6. any GSI from https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list that is ARM64 and A-only and Vanilla.
7. Download OpenGapps from here https://opengapps.org
Instructions:
1. Install Minimal Adb and Fastboot from here https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
2.. copy Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip and Open gapps on SD card
3. Boot into Fastboot Mode.
Fastboot:
4.. Flash TWRP -> fastboot flash recovery_ramdisk TWRP-3.2.3.img
5.. fastboot reboot recovery (the first time booting should show up the twrp menu)
press Power button + volume up. in my case, i had to enter erecovery, click on factory reset, then it boots to twrp.
TWRP:
6. Wipe -> Advanced Wipe -> select data + cache + dalvik-cache + internal -> Swipe to wipe -> back to start menu
7. Install -> Select Storage -> select Mircro SD card -> OK -> select Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip -> Swipe to confirm Flash
8. Reboot -> Bootloader (not System!!!)
Fastboot:
9. fastboot flash ramdisk RAMDISK.img
10. fastboot erase system
11. fastboot flash system <name.img>
12. fastboot reboot
13. Boot into the rom
14. Do step 5 all over again.
15. flash opengapps.
16. reboot.
Sound works, google works.
Bugs:
1. flashing magisk seems to make the rom non-bootable. will search for more
2. the lockscreen, at least on havoc os vs 3.8, is stuck in portrait mode.
3. flashing a rom with gapps will result in a bootloop.
4. also, seems you keep both recoveries. i have erecovery and twrp simultaneously. who knows, maybe is actually a feature XD
Note 1 :
To use fast charging enable it in Settings -> Phh Treble Setting -> Huawei features -> Huawei fast charge -> Mid-fast
To fix display blur enable it in Settings -> Phh Treble Setting -> Huawei features -> Enable blurry UI workaround
Note 2:
If you want to change roms after you just flash it, you dont need to run every step all over again. just erase system, flash ramdisk and flash rom.
Note 3:
change the screen resolution by going into settings>>display>> Smallest width. mine is set at 730.
EDIT: added new links, refreshed the guide
now credits where is due :
sadiqkarur
Received some questions about what to install and what did I meant about vanilla. Gonna repost my post here, in order to clarify it.
What does agN mean? What does avN mean? What does aoN mean? What does afN mean?
Some information you should know about knowing what type of gsi it is
<ARCH>_xyZ
<ARCH> can either be arm, a64 (arm32_binder64) or arm64
x can either be a or b
y can either be v, o, g or f
Z can be N or S
b = a/b
a = a-only
g = gapps
o = gapps-go
v = vanilla (no gapps included)
f = floss (free & open source apps instead gapps)
N = no superuser
S = superuser included
Z = dynamic superuser (you can toggle root on/off without rebooting)
so in most common example "arm64_avN" is ARM64 A-only vanilla with no superuser
Here is my Ramdisk, from latest version of Bah2-w19
File on MEGA
mega.nz
as requested
here is the backup everything without data
File on MEGA
mega.nz
and here is just the vendor partition
File on MEGA
mega.nz
Hi,
I've been trying to install either Pixel Experience Plus (Android 10) or AOSP (Android 11), but both fail with the same error. Do you know how I could fix it?
Spoiler
Code:
target reported max download size of 471859200 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 387334212 is not a multiple of the block size 4096
sending sparse 'system' 1/2 (460796 KB)...
error: write_sparse_skip_chunk: don't care size 387334212 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 387334212 is not a multiple of the block size 4096
OKAY [ 13.188s]
writing 'system' 1/2...
FAILED (remote: sparse flash write failure)
finished. total time: 18.092s
EDIT: Turns out, my dumbass thought I had to flash the .img.xz file, but I was supposed to use the file in it.
Anyway, thanks for the guide!
Hi Fytdyh,
first of all, many thanks for sharing! I was able to run thought it pretty smoothly - until the gapps.
I'm neither able to login to the Play Store, nor I'm able to add any accounts in the settings. The behavior is always the same - I can hit the buttons as much as I want, but no reaction clicking "Login" or "+ Add...." .
Some more infos:
- Tried both, Lineage 18.1 and AOSP 11 avS packages (from GSI link above).
- Flashed NikGapps Basic / Android R right after flashing the ROM, as well as after the first bootup into the ROM.
- I needed to repartition the eMMC to install GApps packages larger than Core - thus increased System partition size from 2.4G to 3.5G
- WebView and Google Services are installed (and seem to be running)
- Since flashing the GSI first time, I cannot find my M5 Lite via ADB anymore. Fastboot works.
- Some system apps seem unstable - i.e. when starting the Terminal from dev-options, the whole settings panel crashes.
- In general, my device preferences look pretty crippled - no model name, Android version etc. anymore (GSI effect?!).
However, I would like to review / provide more logs - is there any way to (a) fix ADB or (b) pull them via TWRP? I recognized that at least logcat does not output anything executed in TWRP.
Any help is appreciated - that the eRecovery to stock ROM failed last time makes me a bit nervous :\
Cheers,
André
el-pollo-diablo said:
Hi Fytdyh,
first of all, many thanks for sharing! I was able to run thought it pretty smoothly - until the gapps.
I'm neither able to login to the Play Store, nor I'm able to add any accounts in the settings. The behavior is always the same - I can hit the buttons as much as I want, but no reaction clicking "Login" or "+ Add...." .
Some more infos:
- Tried both, Lineage 18.1 and AOSP 11 avS packages (from GSI link above).
- Flashed NikGapps Basic / Android R right after flashing the ROM, as well as after the first bootup into the ROM.
- I needed to repartition the eMMC to install GApps packages larger than Core - thus increased System partition size from 2.4G to 3.5G
- WebView and Google Services are installed (and seem to be running)
- Since flashing the GSI first time, I cannot find my M5 Lite via ADB anymore. Fastboot works.
- Some system apps seem unstable - i.e. when starting the Terminal from dev-options, the whole settings panel crashes.
- In general, my device preferences look pretty crippled - no model name, Android version etc. anymore (GSI effect?!).
However, I would like to review / provide more logs - is there any way to (a) fix ADB or (b) pull them via TWRP? I recognized that at least logcat does not output anything executed in TWRP.
Any help is appreciated - that the eRecovery to stock ROM failed last time makes me a bit nervous :\
Cheers,
André
Click to expand...
Click to collapse
Hey there,
Haven't tested android 11 that much, will give it a go in a few days and will report back.
How did you managed to resize the system partition? What guide did you used?
Hey,
I mainly followed the approach of this guy in the answer here: https://android.stackexchange.com/q...-system-partition-and-decrease-data-partition
Main job using gdisk (recreating all partitions from system upwarts) and parted to rename them. Take care to write the original print output from both in some file first (or just take a photo ), that you have infront of you when creating IDs, blocksizes and names of new partitions correctly. After that i'm flashing my backups to the new partitions (includes product and vendor).
However, the "Core" pack from NikGapps seems to have just enough space on the original partition to work without resizing.
FYI - Just flashed Havoc 3.12 / Android 10 with NikGapps. Everything works fine so far, no issues with Gapps login... very strange.
el-pollo-diablo said:
FYI - Just flashed Havoc 3.12 / Android 10 with NikGapps. Everything works fine so far, no issues with Gapps login... very strange.
Click to expand...
Click to collapse
What about chrome based browsers? Still hang?
Nope, everything smooth until now.
el-pollo-diablo said:
Nope, everything smooth until now.
Click to expand...
Click to collapse
Good to hear. You could even try android 11. The version from CAOS is quite nice.
I'll give it a try! However, just gave up with A11 for now after my experience with AOSP and LineageOS. Probably i'll enjoy for some time a working M5 before starting again
Hi guys!
So i got hands on Mediapad M5 10.1 lite (bah2-w19). And I'm trying since 2 days to install a custom rom.
I unlocked it and flashed TWRP and its working fine. SO from there on I can just install any GSI, but unfortanetly they are not working at all or are not the on I'm looking for.
I would really like to flash Havoc 3.12 or Bliss Rom(Android 10), cause I like the clean look.
I tried it with these versions:
bless-v224-201015-arm64-avN.img.xz
Havoc-OS-v3.12-20201230-Official-GApps-arm64-aonly.img.xz
Thing is I can flash them both, but after the booting into the rom I always get this Error:
Spoiler: Error Message
{
"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 same for Havoc 3.12, but there its the shady launcher.
Have you some ideas how to fix this maybe? Would appreciate it.
If you need more information just say it.
Thanks a lot,
Schprick
EDIT:
I finally found a functioning ROM for my Tablet. I used the AOSP 10 v 221 (aonly, arm64, vanilla) and the nano package of OpenGapps, so I could avoid the repartition.
Works fine more or less.
Bugs I found till now:
- Chrome crashes sometimes
- official NEtflix app isnt available for my device
I've just installed succesfully Andy Yan's GSI Lineage 17.1 following Fytdyh's instructions. I can state I didn't detect any serious bug. It works fine. The only problem I noticed is in the lockscreen pin that doesn't work at all. When you put a security pin in the lockscreen and you try to unlock it you always receive a message of error. Is there a fix for it?
How did you manage to download the stock firmware for ramdisk file extraction?
Attempt to download anything from: http://update.dbankcdn.com/ results in "An error occurred".
Or maybe you've used a different source...
And just to confirm the procedure - I should download latest "FullOTA-MF" file?
My model is BAH2-L09.
kissiel7 said:
How did you manage to download the stock firmware for ramdisk file extraction?
Attempt to download anything from: http://update.dbankcdn.com/ results in "An error occurred".
Or maybe you've used a different source...
And just to confirm the procedure - I should download latest "FullOTA-MF" file?
My model is BAH2-L09.
Click to expand...
Click to collapse
It seems that the firmware site isn't working at the moment
Freshly installed lineage-17.1-20210212-UNOFFICIAL-treble_arm64_avS.img.xz following your procedure.
Let's see how it runs.
Many thanks Fytdyh for sharing your experience, bug feedback and notes. It helps.
kissiel7 said:
How did you manage to download the stock firmware for ramdisk file extraction?
Attempt to download anything from: http://update.dbankcdn.com/ results in "An error occurred".
Or maybe you've used a different source...
And just to confirm the procedure - I should download latest "FullOTA-MF" file?
My model is BAH2-L09.
Click to expand...
Click to collapse
Waiting for this website re opening, i don't think latest ota ramdisk file is needed, as there is a recent ramdisk here (and full back up in next message) :
Fytdyh said:
Here is my Ramdisk, from latest version of Bah2-w19
File on MEGA
mega.nz
Click to expand...
Click to collapse
Oups sound doesn't work ... (only notification works, no video sound)
Display blur is fixed but doesn't stay fix
Display settings locked
...
I will re flash later to check (this m5 is reteu rom based)
may someone help ?
⚠ This project is no longer maintained. See below. ⚠
You are encouraged to migrate to the official nightly builds (huge thanks to @anishpratheepan and to the LOS team for bringing that up). If you update from an unofficial build, it is highly recommended that you opt-in for build signature check after the flash:
Open Settings
Privacy => Trust
Check "Build signature" at the very bottom
Note that you should be able to update from unofficial to official builds seamlessly, without wiping anything.
-----
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, 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. Linked below is a package that has come from another Android project that restore the Google parts. 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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
Unlock your bootloader
Backup everything, especially the "persist" partition
Make sure you're on a recent version of OxygenOS.
Download the latest build
Run the following commands:
Code:
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot fastboot
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot reboot recovery
Wipe all data from recovery.
(Optional) If you need GApps, NikGApps Core are known to work ("Apply update" => "Update from ADB", and then run adb sideload <NikGapps-xxx-arm64-11-yyy.zip>). Note that other variants than Core can crash.
Reboot.
Downloads:
https://drive.google.com/drive/folders/1V17qsn_wMpwPgJHMhCjfYYmZEPGzPvP2
Known issues:
Displays "Charging slowly" when it's actually not
Build signed with public keys for now
Reporting Bugs:
Make sure the bug you want to report isn't already known
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][UNOFFICIAL][instantnoodle][11] LineageOS 18.1, ROM for the OnePlus 8
Contributors
KennyG9, LuK1337
Source Code:
Since February 2021 (based on the official LineageOS device tree):
Device tree: https://github.com/LineageOS/android_device_oneplus_instantnoodle
Kernel: https://github.com/LineageOS/android_kernel_oneplus_sm8250
Proprietary blobs: https://github.com/TheMuppets/proprietary_vendor_oneplus
Before February 2021 (based on LuK1337's work on instantnoodlep with minor adjustments to the device tree):
Device tree: https://gitlab.com/nlr/android_device_oneplus_instantnoodle
Kernel: https://github.com/luk1337/android_kernel_oneplus_sm8250
Proprietary blobs: https://github.com/luk1337/proprietary_vendor_oneplus
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2021-01-07
Last Updated 2021-02-10
Very cool. Stoked. Can you add link for gapps as I know lineage needs to work properly.
mattie_49 said:
Very cool. Stoked. Can you add link for gapps as I know lineage needs to work properly.
Click to expand...
Click to collapse
I don't have GApps myself and I don't want to flash them on my personal device. I'm fine with adding a link in the original post provided that one or two person can confirm it works and provide instructions. I think NikGApps are the best candidate.
KennyG9 said:
I don't have GApps myself and I don't want to flash them on my personal device. I'm fine with adding a link in the original post provided that one or two person can confirm it works and provide instructions. I think NiksGApps are the best candidate.
Click to expand...
Click to collapse
Fair enough. Thank you for bringing this to the op8 community.
I made an attempt to bundle OpenGApps into the build: https://drive.google.com/file/d/1edechrEwpX5L5SjE6OlsAjRckT-UF69t/view (using https://github.com/opengapps/aosp_build). It bootlooped on my device but I suspect that's because it requires a factory reset which I didn't want to do. Flashing instructions are identical, just make sure you have flashed OOS 11 at some point. If that happens to work for some of you, I'll try to publish both flavors with every release.
KennyG9 said:
I made an attempt to bundle OpenGApps into the build: https://drive.google.com/file/d/1edechrEwpX5L5SjE6OlsAjRckT-UF69t/view (using https://github.com/opengapps/aosp_build). It bootlooped on my device but I suspect that's because it requires a factory reset which I didn't want to do. Flashing instructions are identical, just make sure you have flashed OOS 11 at some point. If that happens to work for some of you, I'll try to publish both flavors with every release.
Click to expand...
Click to collapse
"Flash OOS 11 at some point"
What about upgrading from 17.1 ?
Also - Why no OOS 10 - 18.1?
mobile_sensei said:
"Flash OOS 11 at some point"
What about upgrading from 17.1 ?
Also - Why no OOS 10 - 18.1?
Click to expand...
Click to collapse
LOS builds only contain a few subset of all the partitions that exist on the OP8 (system, boot, product, dtbo, and some others). The OP8 also contains a lot of other proprietary partitions (ABL, AOP, bluetooth, modem, etc…) that only the manufacturer is able to provide updates for. As far as I understand, those blobs must also be updated to be able to run Android 11 without issues. If you don't update them, it'll likely bootloop or refuse to boot and it's not recommended anyways.
I'm not sure upgrading from 17.1 to 18.1 without wiping is even possible, but if you want to give it a shot, I think your best bet is to extract all the proprietary images from a recent OOS build, then flash them and flash LOS 18.1 over that. You may avoid the annoying MSM step, but my bet is that you'll have to wipe anyways if you want to boot, so I strongly advise that your backup all your data and apps before. In deeper details, you need to :
- get a recent and official OOS 11 build from here : https://www.oneplus.com/support/softwareupgrade/details?code=PM1586920535300
- extract the payload.bin from the image using a tool like this one : https://github.com/LineageOS/scripts/blob/master/update-payload-extractor/extract.py
- reboot to bootloader (adb reboot bootloader)
- flash the stock recovery you just extracted (fastboot flash recovery recovery.img)
- reboot into stock fastboot (fastboot reboot fastboot)
- flash all the blobs you just extracted (fastboot flash abl abl.img && fastboot flash aop aop.img && fastboot flash bluetooth bluetooth.img && ………)
- follow LOS 18.1 flashing instructions from the first post
mobile_sensei said:
"Flash OOS 11 at some point"
What about upgrading from 17.1 ?
Also - Why no OOS 10 - 18.1?
Click to expand...
Click to collapse
Yes I agree here.
I and need step by step exact instructions how to flash any rom here.
I am not even gonna try to flash this rom because I know my device is gonna end up at the Qualcomm dump mode.
I can't get anything booted if I flash anything coming from OOS11, don't ask because I have no idea why.
The only way to get my device booting stock rom at this point is to flash stock rom in EDL mode with the msm tool
[OP8][OOS 21AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
My device is OnePlus 8 5G - 12GB/256GB Interstellar Glow- Firmware : Firmware: OxygenOS - GE / EN / FR / ES
IN2010
Inspected 2020.06.18
As TWRP isn't working completely is there way to do the equivalent full system backup with all partitions without TWRP perhaps via fastboot? Because I know I'm not gonna be able to flash a rom its gonna be the same story over and over again setting up the same stock rom over again ..it gets old.
Because custom software for OnePlus 8 is not at the stage of flash and forget I think a unified toolkit in a zip is needed.
It can be separate or bundled with each rom release and regularly updated that I can extract and cd into, and run the fastboot commands from to help making flashing roms and debug as accurate as we possibly can starting with all of us using the same exact toolkit to begin with.
Driver used
Developer framework ie fastboot, adb executable
Payload dumper
Readme File
Bat/sh file for automation
perhaps payload/img files
bundled with rom Gapps with dev, flavor and release because this seem to be subject to not booting
This would make sure everyone is 100% following the same exact instructions making debugging much easier, in this case it seem like gapps one piece of the puzzle possibly preventing rom from booting, in my case I'm can't even make it to square one getting stuck at Qualcomm dump mode..
Spoiler
KennyG9 said:
LOS builds only contain a few subset of all the partitions that exist on the OP8 (system, boot, product, dtbo, and some others). The OP8 also contains a lot of other proprietary partitions (ABL, AOP, bluetooth, modem, etc…) that only the manufacturer is able to provide updates for. As far as I understand, those blobs must also be updated to be able to run Android 11 without issues. If you don't update them, it'll likely bootloop or refuse to boot and it's not recommended anyways. I'm not sure upgrading from 17.1 to 18.1 without wiping is even possible, but if you want to give it a shot, I think your best bet is to extract all the proprietary images from a recent OOS build, then flash them and flash LOS 18.1 over that. You may avoid the annoying MSM step, but my bet is that you'll have to wipe anyways if you want to boot, so I strongly advise that your backup all your data and apps before. In deeper details, you need to : - get a recent and official OOS 11 build from here : https://www.oneplus.com/support/softwareupgrade/details?code=PM1586920535300 - extract the payload.bin from the image using a tool like this one : https://github.com/LineageOS/scripts/blob/master/update-payload-extractor/extract.py - reboot to bootloader (adb reboot bootloader) - flash the stock recovery you just extracted (fastboot flash recovery recovery.img) - reboot into stock fastboot (fastboot reboot fastboot) - flash all the blobs you just extracted (fastboot flash abl abl.img && fastboot flash aop aop.img && fastboot flash bluetooth bluetooth.img && ………) - follow LOS 18.1 flashing instructions from the first post
Click to expand...
Click to collapse
Good information, I didn't finish my reply during breakfast and noticed you wrote one more.
The only thing I am not comfortable with is that there are links to tools that I have to download from the internet.
Its one factor subject to being sourced from random google searches.
Like the fastboot binary from xda although old doesn't work on op8, I found out the hard way and I am now downloading this directly from Android developer page.
But a lot of headache could be eliminated trying to figure out where and which binaries should be used, what work and what does not.
Is fastboot/adb bundle too old or driver not installed?
Did all of us follow the exact same installation steps in detail the rom developer did?
I hope you understand.
This device has been the most problematic I've ever dealt with
SUPERUSER said:
Yes I agree here.
I and need step by step exact instructions how to flash any rom here.
I am not even gonna try to flash this rom because I know my device is gonna end up at the Qualcomm dump mode.
I can't get anything booted if I flash anything coming from OOS11, don't ask because I have no idea why.
The only way to get my device booting stock rom at this point is to flash stock rom in EDL mode with the msm tool
[OP8][OOS 21AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
My device is OnePlus 8 5G - 12GB/256GB Interstellar Glow- Firmware : Firmware: OxygenOS - GE / EN / FR / ES
IN2010
Inspected 2020.06.18
As TWRP isn't working completely is there way to do the equivalent full system backup with all partitions without TWRP perhaps via fastboot? Because I know I'm not gonna be able to flash a rom its gonna be the same story over and over again setting up the same stock rom over again ..it gets old.
Because custom software for OnePlus 8 is not at the stage of flash and forget I think a unified toolkit in a zip is needed.
It can be separate or bundled with each rom release and regularly updated that I can extract and cd into, and run the fastboot commands from to help making flashing roms and debug as accurate as we possibly can starting with all of us using the same exact toolkit to begin with.
Driver used
Developer framework ie fastboot, adb executable
Payload dumper
Readme File
Bat/sh file for automation
perhaps payload/img files
bundled with rom Gapps with dev, flavor and release because this seem to be subject to not booting
This would make sure everyone is 100% following the same exact instructions making debugging much easier, in this case it seem like gapps one piece of the puzzle possibly preventing rom from booting, in my case I'm can't even make it to square one getting stuck at Qualcomm dump mode..
Good information, I didn't finish my reply during breakfast and noticed you wrote one more.
The only thing I am not comfortable with is that there are links to tools that I have to download from the internet.
Its one factor subject to being sourced from random google searches.
Like the fastboot binary from xda although old doesn't work on op8, I found out the hard way and I am now downloading this directly from Android developer page.
But a lot of headache could be eliminated trying to figure out where and which binaries should be used, what work and what does not.
Is fastboot/adb bundle too old or driver not installed?
Did all of us follow the exact same installation steps in detail the rom developer did?
I hope you understand.
This device has been the most problematic I've ever dealt with
Click to expand...
Click to collapse
I don't have a definitive answer to everything, but here are some remarks:
- Not sure what exactly your problems were and I'm unaware of any way to backup partitions using fastboot unfortunately. As far as I know, it was not possible to restore nandroid backups using mauronofrio's TWRP on Android 10 either. I think the best you can achieve for now is software and data backup (using "adb pull" and "OAndBackup+" or something else). I can also attest that I had way more weird partitioning issues when using TWRP than LOS' fastboot. Since I stopped using TWRP, I never had to use MSM again.
- What you may attempt to reduce the risk of bricking your device is to take advantage of the A/B partitioning. You can flash everything on the unused slot and switch back to the working slot if anything goes wrong. This can be done by running "fastboot getvar current-slot" to get the current slot, then "fastboot --set-active=a" to switch to slot a (or "fastboot --set-active=b" to switch to slot b, depending on which slot was active).
- I second your reluctance on using tools coming from untrusted sources. Please, don't get fastboot/adb from XDA, use the official Android builds. I can't help you regarding the drivers as I use Linux which ships with drivers, but if you use Windows try to get those drivers from either Microsoft, OnePlus or Qualcomm directly. My instructions to avoid flashing Android 11 with MSM makes you use an official image from OnePlus (which you have to trust anyways) + an open-source tool that's made by LOS developers (which you have to trust anyways). At this point, I think the weakest point of trust if you don't want to build LOS yourself is me.
- Regardless of what you attempt, always make sure you have backups of your valuable data, apps and persist partition. Especially given how capricious this device is .
working great so far. any way to re-enable the 90Hz refresh rate?
edit: found it in display options!
LuK1337 said:
OP8 is no longer supported so RIP.
Click to expand...
Click to collapse
New flash method for both 8p and 8t does not allow to use it on instantnoodle, migrated yesterday from there to this build and it's working perfect with NikGapps-core and Magisk, great job @KennyG9
any way to get the OP camera app working? tried several versions available on APKMirror, but all seem to crash. maybe there are some dependencies?
Does OnePlus 8 tmobile version work with dual sim on this rom?
veridiam said:
any way to get the OP camera app working? tried several versions available on APKMirror, but all seem to crash. maybe there are some dependencies?
Click to expand...
Click to collapse
There's a lot of proprietary software/firmware (apart from the camera apk itself) that its not included in LOS. There have been some ports in the past (e.g. OnePlus6 OOS Camera port or oxy-ify) but all of them seem dead, maybe because google camera port working out of the box.
Creating a magisk module should be doable, but you need to start the app, let it crash and add the missing dep N times until you have all of them
@LuK1337 , please accept pull request: https://github.com/luk1337/android_kernel_oneplus_sm8250/pull/1
Running great. I would mention that only nikgapps core works. The rest for me ended in a crash whilst setting up.
passion8059 said:
Running great. I would mention that only nikgapps core works. The rest for me ended in a crash whilst setting up.
Click to expand...
Click to collapse
Thanks, just updated first post to mention that.
KennyG9 said:
Thanks, just updated first post to mention that.
Click to expand...
Click to collapse
Would you be able to look into face unlock? Handy feature for me especially at work.
passion8059 said:
Would you be able to look into face unlock? Handy feature for me especially at work.
Click to expand...
Click to collapse
Face unlock is an OxygenOS feature and I don't think AOSP or LineageOS supports something like that officially as it's quite terrible security-wise. GApps also dropped support for face unlock in Android 10 because of security concerns. So unless I'm missing something it probably won't happen anytime soon unless through some third-party module, sorry. It's not just about porting some blobs, it's a whole new OS feature.
Is WiFi calling and LTE calling working?
Hi all,
i was kinda bored and sick of no Custom ROM development for our beloved S6 so i thought i'd try using a GSI and i've got it booting so i thought i would share the instructions!
As usual all care no responsibility! Nothing here is without risk.
Android 13
5 March 2023 Security Patch Level
1. Unlock your bootloader. (Very easy to do - https://www.hardreset.info/devices/...-s6/faq/bootloader-unlock/samsung-bootloader/)
2. Download the official vbmeta image provided by TWRP > https://dl.twrp.me/gts4lv/vbmeta.tar.html
3. Download TWRP https://twrp.me/samsung/samsunggalaxytabs6qcomwifi.html
4. Open Odin
5. Put VBMETA.TAR in the CP Slot & TWRP in AP slot and flash. On reboot hold down the Pwr/Up button so it boots straight into TWRP or sometimes it can be overwritten.
3. Format Data, reboot back into TWRP and Full Factory Reset . (Take a backup if you need one).
4. Transfer the LoS image file to the tablet via TWRP then Flash the LoS image through TWRP (System Partition) lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img (or whichever ARM64 flavour you like) from here: https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/
(might need to use the adb push command to copy the file across) adb push filename.extension /sdcard
5. Flash magisk if you like.
6. Reboot to system and enjoy!
i used the one above which includes GAPPS though there are ones that don't if you prefer
I only just finished installing though - quick summary:
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:
Only bottom speakers work
SafetyNet
Workarounds:
To pass SafetyNet (BASIC):
Flash Magisk in TWRP
Use Magiskhide
Turn on Zygist
Install Displax modified SafetyNet-Fix from link below;
hxxps://github.com/Displax/safetynet-fix/releases/tag/v2.4.0-MOD_1.2
Configure your Denylist in Magisk for Google Play Store and Services apps. (And anything else you need to not detect root).
To Fix Brightness:
Go to Settings - Phh - Misc Features - Tick the box for "Use Linear Brightness Slider"
To Help with Fingerprint:
Turn off taskbar in Settings to help alignment with Fingerprint scanner
Hope we can get some community effort behind this so we can bring this tablet back into support since Samsung gave up on it..
Credit to @AndyYan for the builds!
[GSI][13] LineageOS 20 TrebleDroid-based
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...
forum.xda-developers.com
RESERVED
In my case only bottom speakers work!
Sage said:
Hi all,
i was kinda bored and sick of no Custom ROM development for our beloved S6 so i thought i'd try using a GSI and i've got it booting so i thought i would share the instructions!
5.Install LoS image through TWRP (System Partition) lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img (or whichever ARM64 flavour you like) from here: https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/
Click to expand...
Click to collapse
Thanks so much for this!
I have built LOS for a couple unsupported devices in the past and would love to dedicate as much time and resources as needed to this project.
Could you share which build trees were used from Github and the extracted blobs?
I would like to replicate this build and put in a request with LOS developer stinX for an official one.
tablet_seeker said:
Thanks so much for this!
I have built LOS for a couple unsupported devices in the past and would love to dedicate as much time and resources as needed to this project.
Could you share which build trees were used from Github and the extracted blobs?
I would like to replicate this build and put in a request with LOS developer stinX for an official one.
Click to expand...
Click to collapse
I am not sure mate about the GIT and Blobs. These are GSI so "generic" so they may not have them. From my understanding they work with the existing Vendor image and take advantage of Treble to ensure everything works.
The source of the files is here:
[GSI][13] LineageOS 20 TrebleDroid-based
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...
forum.xda-developers.com
m0byn said:
In my case only bottom speakers work!
Click to expand...
Click to collapse
There are quite a lot of tweaks available in the PHH settings. I suggest you play around in there and you may get both sets of speakers working. I will do the same
I have added it to "Not Working" section.
Sage said:
There are quite a lot of tweaks available in the PHH settings. I suggest you play around in there and you may get both sets of speakers working. I will do the same
I have added it to "Not Working" section.
Click to expand...
Click to collapse
I should add i think this is MUCH faster than stock and battery life is looking great too!
I am happy there are some other people who are using this GSI on a Tab S6. I installed it some time ago and am very satisfied!
Some things I found:
Fingerprint XY coordinates are somehow off. Specifically, the symbol showing on screen and the actual reader are not on the same place. I think it is related to the app bar somehow, since it seems to be off by that. I think this could be fixed by an overlay.
Auto-brightntess is not available as well. Either use an app for that, or don´t use it. This can also be fixed by an overlay as far as I know.
Maybe it is also possible to get the top speakers working by making an overlay? I am not sure regarding this, however.
Obviously, DolbyAtmos is not included. However, I think there exists a Magisk Module. Maybe it would also be possible to integrate this into an overlay? This would be amazing
I am very new to the custom ROM/GSI scene. So, my experience with overlays and so on is basically none. However, I would try to contribute as good as I can if someone feels ready to create an overlay and then getting it implemented into the GSI.
Anyone interested in cooperating?
Sage said:
There are quite a lot of tweaks available in the PHH settings. I suggest you play around in there and you may get both sets of speakers working. I will do the same
I have added it to "Not Working" section.
Click to expand...
Click to collapse
I will try to do that as well...lets see.
I would explicitly add to the working section that the spen works and also pressure sensitivity of the spen works! At least in the Saber Handwritten Notes app which I use. This is amazing.
Sage said:
1. Unlock your bootloader. (Very easy to do - https://www.hardreset.info/devices/...-s6/faq/bootloader-unlock/samsung-bootloader/)
2. Install TWRP via Odin https://twrp.me/samsung/samsunggalaxytabs6qcomwifi.html
3. Full wipe thru TWRP. Including format data. (Take a backup if you need one).
4. Reboot back to TWRP.
5.Install LoS image through TWRP (System Partition) lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img (or whichever ARM64 flavour you like) from here: https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/
6. Boot and enjoy!
Click to expand...
Click to collapse
Didn`t you patch the vbmeta.img, or did you flash the multidisabler zip?
Somehow, one has to disable verified boot such that you can even boot LineageOS...as far as I know!
m0byn said:
Didn`t you patch the vbmeta.img, or did you flash the multidisabler zip?
Somehow, one has to disable verified boot such that you can even boot LineageOS...as far as I know!
Click to expand...
Click to collapse
All I did was what I posted above! I'm surprised how easy it was tbh!
Sage said:
All I did was what I posted above! I'm surprised how easy it was tbh!
Click to expand...
Click to collapse
Did you start from stock rom? Maybe you already flashed a vbmeta.img or multidisabler.zip some time ago which is still in effect?
I really doubt that it is possible to boot a different os if verified boot of Android is not adjusted...
m0byn said:
Did you start from stock rom? Maybe you already flashed a vbmeta.img or multidisabler.zip some time ago which is still in effect?
I really doubt that it is possible to boot a different os if verified boot of Android is not adjusted...
Click to expand...
Click to collapse
Nope. Started from stock. Literally unlocked bootloader right before moving to GSI. Just like the steps above.
I did install Magisk which may help disable verified boot though
Sage said:
Nope. Started from stock. Literally unlocked bootloader right before moving to GSI. Just like the steps above.
I did install Magisk which may help disable verified boot though
Click to expand...
Click to collapse
Ah, that might make the difference! So I think it is worth to mention to either install Magisk, or to patch the vbmeta.img in order to boot. If coming from stock with the stock vbmeta.img, then Android Verified Boot will not allow booting into a different ROM.
m0byn said:
Did you start from stock rom? Maybe you already flashed a vbmeta.img or multidisabler.zip some time ago which is still in effect?
I really doubt that it is possible to boot a different os if verified boot of Android is not adjusted...
Click to expand...
Click to collapse
OP is wrong.
Be careful flashing the latest TWRP for SMT-860 Wifi with Odin.
This happened to me today after doing it. "Error verifying vmbeta image: Invalid vmbeta header"
{
"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 device gets stuck like this and won't boot anymore, but you can get it back to normal by flashing the recovery.img from your firmware files (It's in AP)
You cannot install TWRP on the Galaxy Tab S6 without fixing the vmbeta.img issue.
I tried with the latest Samsung firmware downloaded via SamFirm and an older one.
@m0byn: Do you know what needs to be done with the vmbeta.img on this device, to allow for TWRP to be flashed?
I have found many different prescribed solutions such as patching boot.img with Magisk or just the vmbeta.img , but nothing seems to work.
Tablet, search my post here https://forum.xda-developers.com/t/t865-rooting-with-android-12-bootloop-and-error.4452641/ and try
Hey man, thank you for the suggestion. That post seems to be about Magisk and rooting.
The problem here is the vmbeta.img.
According to older posts from 2021 this can be resolved by flashing vbmeta_disabled.tar , but the latest 2022 version of TWRP should no longer require this. It's weird.
I am sorry. I thought something went wrong when you patched the firmware with Magisk
Probably flashing Magisk automatically patches the vbmeta.img. Not sure though.
Follow the steps below. This is how I did it. It worked.
I am assuming a stock recovery in this process. If you already installed TWRP just try if it works as well. not sure if this is impacting the process.
Unpack firmware using 7Zip tool
Unpack AP.tar.md5 using 7Zip tool
Unpack vbmeta.img.lz4 using 7Zip-ZS tool
Open file in FrhedPortable (HEX editor) to patch it
Go to offset (block) 123 and write 03 and save
Compress vbmeta.img to vbmeta.img.tar using 7Zip tool
Connect device via USB to computer
Hold volume up & volume down buttons
Press volume up button to proceed to download mode
Open Odin -> verify whether device number is added
Untoggle "auto-reboot" in options
Select AP section
Choose patched vbmeta.img.tar file
Click start to flash
When flashing process is done: hold power & volume down button to exit and power off device
IMPORTANT: as soon as device shuts off immediately release volume down button and press volume up button to enter recovery mode
Click factory reset
Click reboot to bootloader
Thanks @m0byn I managed to figure it out with your help.
For anyone else facing the same problem, here is what you need to do:
Download the official vbmeta image provided by TWRP > https://dl.twrp.me/gts4lv/vbmeta.tar.html
Proceed to flash with Odin.
Put the TWRP recovery image in AP and vbmeta.tar in the CP slot.
After this you can boot into the TWRP recovery normally, but for some reason any changed settings in TWRP are not saved. So everytime I reboot into TWRP recovery all previously selected TWRP settings are lost. I wonder if that's normal, but everything else seems to work.
Next step will be flashing the Lineage GSI, i'll keep you guys posted.
{
"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.