Related
When I go to system settings -> security -> encrypt phone, with phone fully charged and plugged in and a suitable PIN set, the phone reboots back to lock screen but does not appear to do anything to actually encrypt the phone. After reboot, the option remains looking identical in the settings menu. No error messages or the like.
The lock screen works fine (PIN required), the PIN is suitably long, everything is updated, etc.
I'm not sure what the issue is. I rooted & changed ROM immediately on getting the phone (it's new), so I don't know whether it would've worked w/ stock bootloader / rom / etc.
I'm running:
Nexus 4 (android 4.2.2)
ParanoidAndroid 3.65 (pa_mako-3.65-20130712 + pa_gapps-full-4.2-20130710)
TWRP bootloader (openrecovery-twrp-2.6.0.0-mako)
Any ideas on what's going wrong?
Thanks!
My just be bug in the rom you chose, go get an official Cyanogenmod or AOKP rom. Also, did you cache wipe/factory wipe phone after root and rom installation, this could also be a cause, just boot into recovery and do so
DISCONTINUED DUE TO LOWER PERFORAMNCE THAN LEGACY!!!
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
CyanogenMod 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. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What are Nightly builds? Auto compiled builds of the latest CyanogenMod source from github. This version change each night and aren't officialy supported. If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
All bug reports that don't meet this conditions will be ignored:
You have the kernel provided in the zip file
You made a clean flash and didn't restore anything
You made a detailed review of the problem
You provide a logcat in a .txt file (Search internet)
You provide dmesg or last_kmsg if it is a kernel panic (Search internet)
EVERY AND ALL REPORTS OF BUGS WITHOUT LOGS WILL BE IGNORED. DO NOT POST WITHOUT LOGS BECAUSE NOTHING WILL BE SOLVED. THANKS. I CAN'T DO WITCHCRAFT.
What's working :
Booting
RIL and Mobile Data (Should work for Dual-Sim also) !!! SOMEONE CONFIRM
Storages (Internal and External)
Notification Led
Flashlight
Sound
Wi-Fi
Bluetooth
GPS
Tethering (BT, Wi-Fi, USB)
Sensors
Camera
Browser
Autoselecting your phone based on your MODEM partition
BATTERYLIFE SHOULD BE CRAAAAZYYYY
What's not working :
Video playback
Fm Radio
NFC (I never used it and it is a pain to separate from other versions other than P710)
Other things might be broken please report with logs
Instructions :
Reboot to recovery
Make a full wipe (/system, /data, /cache, /dalvik-cache)
Flash the CM11 zip
Flash Gapps (if you want)
Make factory reset
Reboot to system
Downloads :
ROM:
Older versions:
cm-11-20160222-UNOFFICIAL-vee7-RC1.zip
md5: abe9b3aaa42a3e8dd6f9bdd96bdb02c3
cm-11-20160222-UNOFFICIAL-vee7-RC2.zip
md5: 5dafd54589f603b43780bee5a5d134da
GAPPS:
pa_gapps-modular-nano-4.4.4-20150308-signed.zip
If you really appreciate my work on the L7 II series please consider getting me a coffee right now
Credits :
@Caio99BR
chil360
Y300 Team
TeamHackLg
CyanogenMod
Xda for this nice home
Donators (BIG THANKS!!!) :
XDA:DevDB Information
CM11 vee7 CAF, ROM for the LG Optimus L7 II
Contributors
neutrondev
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CM
Version Information
Status: Stable
Created 2016-02-22
Last Updated 2016-02-22
Reserved
Changelog :
22.02.2016 ---> Initial Release RC1
You have the bugs and what is working in the first post
24.02.2016 ---> RC2
overclocked cpu
added governors
added hardware monitoring for battery
probably fixed dual sim
Reserved
Wow! This so fast. hahaha!
I have P716 and I will flash then as soon as I download it.
'll test and post the feedback. If you need some test of roms for dual sim devices you can ask me.
Anyway thank's for your efforts for our device.
In P716 boot is run( although the boot in this is slightly slower than the other ROMs, but ok), so start the device,
sim card's are detecded, but when i try enable then, an error occurs and activation failed, and return to mesage "new sim card detected....", then I was not able to activate neither one sim card.
So, return to the welcome page and after choose the language, a bar run, and aking "just a sec...", after few minutes, setup wizard crashes "Unfortunately, Setup Wizard has stoped". Device does not start.
I was trying reboot for sometimes, but every time the same occurs.
I read and follow all instructions and flash this rom two times.
As the device does not start, I was unable to get Catlog. Sorry.
Edit:
Now I tried to flash without GAPPS and it worked.
But, Setup Wizard not loaded. it probably crash. Before the first boot go directly to the Home screen. All configuration, wifi, data, time, language, ... was done manually.
Too, simcard's faliled to activated. included by terminal. I will provide the logcat soon. I'm sleepy now. hehe
After, I reboot to recovery and flash GAPPS now it worked. When rebooted playstore app not works in first time, after new rebooted, playstore app works but was slowly for now all ok.
The rest all ok for now. too videoplayback is ok.
What is CAF? How is it different from normal and your previous cm11 build.
XDA-00 said:
What is CAF? How is it different from normal and your previous cm11 build.
Click to expand...
Click to collapse
First search result in google: https://www.reddit.com/r/Android/comments/1rt9md/eli5_what_is_caf_why_is_cm_going_caf_affects_the/
shhnedo said:
First search result in google: https://www.reddit.com/r/Android/comments/1rt9md/eli5_what_is_caf_why_is_cm_going_caf_affects_the/
Click to expand...
Click to collapse
So Qualcomm devices(like my p715) will have increased performance/battery life with custom roms having CAF. Right?
XDA-00 said:
So Qualcomm devices(like my p715) will have increased performance/battery life with custom roms having CAF. Right?
Click to expand...
Click to collapse
Something along those lines, yes.
Sorry i don't understand one thing, to flash this rom, and Also your cm12-13, i have to use twrp3 or can I use my old cwm, the old no-touch version? Sorry for my bad english
MustangBR said:
In P716 boot is run( although the boot in this is slightly slower than the other ROMs, but ok), so start the device,
sim card's are detecded, but when i try enable then, an error occurs and activation failed, and return to mesage "new sim card detected....", then I was not able to activate neither one sim card.
So, return to the welcome page and after choose the language, a bar run, and aking "just a sec...", after few minutes, setup wizard crashes "Unfortunately, Setup Wizard has stoped". Device does not start.
I was trying reboot for sometimes, but every time the same occurs.
I read and follow all instructions and flash this rom two times.
As the device does not start, I was unable to get Catlog. Sorry.
Edit:
Now I tried to flash without GAPPS and it worked.
But, Setup Wizard not loaded. it probably crash. Before the first boot go directly to the Home screen. All configuration, wifi, data, time, language, ... was done manually.
Too, simcard's faliled to activated. included by terminal. I will provide the logcat soon. I'm sleepy now. hehe
After, I reboot to recovery and flash GAPPS now it worked. When rebooted playstore app not works in first time, after new rebooted, playstore app works but was slowly for now all ok.
The rest all ok for now. too videoplayback is ok.
Click to expand...
Click to collapse
I need dmesg and logcat and logcat -b radio. we will fix it
@MustangBR
Flash this in recovery then tell me if it works.
https://www.androidfilehost.com/?fid=24421527759886035
shhnedo said:
Something along those lines, yes.
Click to expand...
Click to collapse
Great!
Its strange for me TWRP 3x recovery writes during installation about "unable to mount system on block 14 and data on block 20 device is busy".Nothing wrong,just strange.
First bug just on first start,setup wizard "unfortunatelly stopped" after lang selection,with or without SIM and all.Maybe reason is i am flashing not provided gApps pack but just micro[dont need lots of junk in /system]. Logcat named xD is in attached RAR.May be You will see what went wrong,sir.
Flashed without gApps,first start is working well=) .BTW if i install that micro gApps after first start,evth is fine.
Then,about camera.While focusing camera app crushes,the same was on Weritos CM with his videorecording fix.Logcat named camera attached[not filtered by error type and thats why too large,sorry].
Gonna test and look now,what else can I see.
Okay,turned developer settings ON,setted all animations to 0.5x,seems all works well on my 713.
And a question,will ART work better than Dalvik?
neutrondev said:
I need dmesg and logcat and logcat -b radio. we will fix it
@MustangBR
Flash this in recovery then tell me if it works.
https://www.androidfilehost.com/?fid=24421527759886035
Click to expand...
Click to collapse
Log are attached.
I was not able to download RIL_DS.zip, tried several mirror, but will not download.
I'll try to download more times, so get flash it I reply here.
Edit:
I was able to download now and flash it.
Remain the same any sim can not be activated. New log's below
MustangBR said:
Log are attached.
I was not able to download RIL_DS.zip, tried several mirror, but will not download.
I'll try to download more times, so get flash it I reply here.
Edit:
I was able to download now and flash it.
Remain the same any sim can not be activated. New log's below
Click to expand...
Click to collapse
I will look into it. It seems there are some issues .
@MustangBR add this line to build.prop and restart
ro.telephony.ril_class=LGEQualcommUiccRIL
Okay,played a bit with ROM.
First,smth is with lockscreen when music is played.Pictures sometime stuck,and even with player off it sometimes freezes a bit while unlocking.
Second,few times stuck on main screen with music played,one time phone even rebooted itself,other times i pulled battery.
Then,as in another CM builds,maximum volume is ABNORMAL high.
Also,sometimes battery indicates strange.I was goin home with 9%,then raised to 14% and now 20%.
Will try to catch error about freezes in music/locker soon,probably tomorrow will send an logcat.
ART works good=)
And my opinion:This will be the best ROM for vee7.Holds battery great,and works great[i changed launcher to Nova for myself to have biggest grid in menu]
And can i ask to add Smartass Governor to kernel?
DS_katauri said:
Okay,played a bit with ROM.
First,smth is with lockscreen when music is played.Pictures sometime stuck,and even with player off it sometimes freezes a bit while unlocking.
Second,few times stuck on main screen with music played,one time phone even rebooted itself,other times i pulled battery.
Then,as in another CM builds,maximum volume is ABNORMAL high.
Also,sometimes battery indicates strange.I was goin home with 9%,then raised to 14% and now 20%.
Will try to catch error about freezes in music/locker soon,probably tomorrow will send an logcat.
ART works good=)
And my opinion:This will be the best ROM for vee7.Holds battery great,and works great[i changed launcher to Nova for myself to have biggest grid in menu]
Click to expand...
Click to collapse
Will add governors and Hardware monitor of battery sure.
neutrondev said:
I will look into it. It seems there are some issues .
@MustangBR add this line to build.prop and restart
ro.telephony.ril_class=LGEQualcommUiccRIL
Click to expand...
Click to collapse
No way.
Now when to open dialer app this is crashes. The same occurs when trying to configure and activate simcard in configurations he crashes.
Also now show only one sim card symbol on the top bar of the screen, before this command appeared two.
I confirm all @DS_katauri has written. I noted the same things. + sometimes after pressing the power button to block screen and press it again to unblock screem takes several seconds with black screen until to show the screen.
GPS(included navigation mode), camera, wifi, sensors, usb, sound,video, browsers are fine, batterylife is unbelievable, very good.
Not a ROM bug,i forget to use some autostarts manager and disable sync=)
Seems ROM is stable,no reboots for night.Just damn gApps.
@MustangBR
Try the new version. Clean flash. Tell me if Dual Sim works.
@DS_katauri
Overclocked CPU and governors are there.
Also battery is monitored with kernel interface now.
THIS IS NOT A RELEASE THREAD!
IT'S ONE AND ONLY PURPOSE IS TO ARCHIVE FILES FROM A DISCONTINUED PROJECT!
The original thread can be found here: https://forum.xda-developers.com/zenwatch-2/development/wear-2-development-sparrow-t3581617
All files and their description + how to flash this ROM are available here: https://paper.dropbox.com/doc/ZenWatch-2-sparrow-WI501Q-WebWear-Backup-W90rNXRqV2TftstVtri1C
A shared folder for all files is available here: https://www.dropbox.com/sh/7cxdx0ho2m3frvy/AABgfinUMsPvRPoo8gaXRP1ea?dl=0 - OneDrive Backup
Here's the last version of the first post from the original thread:
DaanNL said:
First a little disclaimer
test
DISCLAIMER:
I am not responsible for anything that may happen to your watch as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
"This is a user friendly thread. All feature requests will be heard and considered. I am not against anything that doesn't stray too far away from the original idea of the ROM! Helping one another is also encouraged! Please be respectful and you will always be treated the same way, we are all here for a good experience."
The rom is named WebWear after my nickname (WebWire).
Known problems:
Touchscreen freezes some times.... maybe after certain actions or a certain amount of time?
No way to launch assistant, you can activate ok google in settings to launch assistant... but it cant be launched with a button
Install the latest version of Zenwatch Manager
Zenwatch Manager beta signup
Releases:
20-04-2017
Version 0.5 Beta!
Changes to setup procedure
Fixed issue where clock will crash after installation
Download here
18-04-2017:
Version 0.4
Changes:
In this build wifi/bluetooth firmware has been updated.
Touchscreen issues are fixed.
Single press button on home screen for menu
Longpress for Google Assistant
Odexed framework for faster startup
Ambient display is working
Battery optimizations
Tilt to wake fixed
Fixed bluetooth dialing (no speaker and mic yet but you can select a contact from the phone application and your phone will call).
Updated Google App to beta version 7.x
Setup modifications... setup works better than before.
Watchface selection on watch is fixed
Battery optimizations!
Please report your experience so we can help eachother!
Known problems:
Bluetooth calling not working...
https://www.androidfilehost.com/?fid=457095661767155028
15-04-2017:
Version 0.3
Changes:
Ambient mode
Always on display mode
Multicore CPU config (ondemand)
Nice and steady!
For new users a factory reset is needed, users comming from 0.2 only need to flash boot and system image
https://www.androidfilehost.com/?fid=457095661767153891
13-04-2017:
Version 0.2
Changes:
Stability improvements, zenwatch manager integration....
Watchfaces work ok with complications... wifi improvements....
7.1.2_r5-WebWear-2.0.1_02
https://www.androidfilehost.com/?fid=745425885120724018
Use this boot image with image above image! otherwise it won't boot[/URL]
13-04-2017:
Version 0.1
7.1.2_r5-WebWear-2.0.1_01
https://www.androidfilehost.com/?fid=745425885120723803
The first release is WebWear 7.1.2_r5-WebWear-2.0.1_01 Alpha!
And here the installation instructions:
Before setup:
The boot will take about 10-40 minutes.. it will compile the java code with dex2oat because of limited space on the watch.
After the compilation it will begin the setup, because of screen timeout screen can turn black.... if you don't see the bootlogo touch the screen to show the setup.
In setup:
The setup/update task takes a long time, in the background google service get installed and updated.
When setting up a google account (copy accounts) you have to do this step multiple times until it finishes successfully, most times it takes me 3 times.... Google will update the services in the background... and finally the account copy function will work... don't skip this step because the initial watch setup is done in this step...
If something goes wrong during setup, first try a reboot and otherwise factory reset and repeat the steps.
After setup:
Screen can turn black again, touch to wake...
Give the watch a little time to boot... for apps menu touch the screen to wake and if it's awakw click the crown button.
Installing is simple!
Download the zip and extract.
Factory reset your watch
If you have adb (enabled developer options or recovery mode), you can reboot into bootloader with "adb reboot bootloader"
Reboot into bootloader, and fastboot flash the images
"fastboot flash boot boot.img"
"fastboot flash system system.img"
Optionally factory reset can be done when in bootloader
"fastboot erase userdata"
"fastboot erase cache"
"fastboot -w" (Erases userdata and cache (and format if supported by partition type)).
and "fastboot reboot" to reboot
I've added a log sender which sends debug logs for development purposes, this could contain your mail address... it also contains serial number of your watch but nothing to worry about.
Logs will be sent every hour and are from the last hour... it will cost around 20mb of data a day but it helps me a lot in developing this rom.
Click to expand...
Click to collapse
Hi!
I'm running stock Android Pie and I installed Swift Installer overlays to get a dark theme. Yesterday I tapped on the system update just before remembering to disable overlays before doing so... and no way to cancel the update before it actually installed it
Now my phone won't start properly: I get the Samsung logo, then I enter my pattern do decrypt the phone, then it loads and when finished loading it restarts immediately. The second time, instead or restarting immediately it will display the wallpaper for a few seconds, then black screen for a few seconds, and then the Samsung logo disappearing as it shuts the system down. And then it boots me into a special recovery mode with 4 options:
Try again
Erase App data
Power off
View Rescue log
Viewing the rescue log shows me it really is a system UI issue that's very likely because of the Swift Installer overlay: Attempt to invoke virtual method 'int com.android.systemui.statusbar.notification.FakeShadowViw.getVisibility()' on a null object reference
Trying again does the same as before, "Erase App data" doesn't help either, and "Power off" actually reboots to the regular recovery mode, with different options:
Reboot system now (same result)
Apply update from ADB
Apply update from SD card
wipe data/factory reset
wipe cache partition
Mount /system
view recovery logs
run graphics test
run locale test
Power off
Lacking storage booting
From the document from the Play Store page of Swift Installer, you can download a rescue script (rescue_Pie.zip). I tried sideloading that file using adb (option 2), and from an SD card (option 3)
and both yield the same result:
Code:
E:footer is wrong
Update package verification took 0.2s (result 1).
E:signature verification failed
E:error:21
Installation aborted
I tried wiping the cache partition and that didn't help, I tried booting with Safe Mode and that didn't help, the only obvious option left that I can see is to do a factory reset, but there are photos from my last trip I would hate to lose and since my phone is encrypted, doing a factory reset would lose the encryption key and I wouldn't be able to recover them.
Would there be any way to
Get the rescue script to run properly, or
Get access to a shell to run the bash commands from the script myself (it's really simple), or
Erase everything BUT my user data, or
Get my photos out of my phone from recovery mode, or
Stop the phone from rebooting long enough for me to try and get my photos out to my computer
It seems really dumb that there is no way to restart with all non-stock apps disabled or to reset the system without losing photos and such...
Thanks for your time and any help!
Try flashing the latest CSAB build with CSC_Home using ODIN. That should essentially replace Android and retain your data. Hopefully that will override the overlay with stock OneUI. If you can't, you can at least flash back to BRK2, CSC_Home, disable overlays, then push forward to CSAB through OTA.?
---------- Post added at 01:44 AM ---------- Previous post was at 01:40 AM ----------
The latter would probably be your best bet in keeping your files.
Thanks for the quick reply!
I downloaded Odin, your answers are a bit cryptic to me, I started downloading the latest firmware (which has the same version id as shown in recovery mode before you edited your message.
I assume BRK2 is the previous version, and would match the overlays I installed so I can boot properly. ls there a guide to stock version names
loomie209 said:
Thanks for the quick reply!
I downloaded Odin, your answers are a bit cryptic to me, I started downloading the latest firmware (which has the same version id as shown in recovery mode before you edited your message.
I assume BRK2 is the previous version, and would match the overlays I installed so I can boot properly. ls there a guide to stock version names
Click to expand...
Click to collapse
I'm assuming you're currently running CSAB on a G965U. You'll need the BRK2 firmware package (doesn't matter what carrier). Flash that using ODIN and for CSC you will use CSC_Home to retain your data. That would essentially put you back to preupdate. You'd then disable the overlay and allow it to update to CSAB on its own, however I think Samsung blocked overlays in Pie all together so you may not be able to use them again.
---------- Post added at 02:29 AM ---------- Previous post was at 02:21 AM ----------
There is no "guide" per say... If you're on a carrier branded US G965U device, you'll want to downgrade from pie (CSAB) to BRK2 (Oreo) and flash the CSC_Home file (NOT CSC_OMC that will wipe).
If you're on the Exynos or international unlocked, I can't help you because those firmware builds are out of my scope.
Thanks a lot for your help!
I flashed G965FXXU2BRK2 on my phone using Odin, and it got stuck in a loop of loading and "Optimizing app X of 72" Over and over again without rebooting. I tried to wipe the cache data and reboot but still the same.
So I flashed G96FXXU2CSA2 (which was the version I had already apparently) and now I seem to be back to my starting point: same behaviour, same error in the log...
My phone is a G965F.
I am having this exact same issue all my Galaxy note 10 plus using synergy and substratum lite. I have been steaming my phone using these same methods since the note 10 plus was released and all of a sudden today I start getting issues to wear my phone automatically boots into a boot loop. I have reset my phone twice now and then I theme it and it works fine but then I went to switch themes and all of a sudden phone shut off in into bootloop. Did you ever get any explanation?
{
"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"
}
Here's my first effort at porting the Nexus Stock custom ROM to the 2019 Galaxy Tab A 8.0 [SM-T290] on Android 10. It's very much a work in progress, but it should hopefully help blaze the trail for even better work.
Notes:
The current process may require you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
The system is based on eremitein's CAOS GSI project with the latest Stock variant from OpenGApps.
Boot animation and default wallpaper is from my Nexus series of custom ROMs for Android TV, and I'm using the Pixel boot animation with black background.
This should be installed using my latest TWRP build for the SM-T290.
The properties now correctly identify the device as a tablet, and so the Google Dialer and Messenger are no longer installed. I've also disabled the Emergency button, but SetupWizard still insists on reminding you to insert a SIM (sigh!).
This is unofficial and unsupported, so the usual caveats apply. Since we don't mess with the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for file-based encryption
MTP support (pending FFS MTP fix)
Downloads:
Nexus_Stock_CR_T290XXU3CUK4-20220327.tar.md5 (Odin tarball)
Nexus_Stock_CR_T290XXU3CUK4-20220327.zip (TWRP update)
Build Archives:
Android File Host
Change Log:
20220327:
Updated to Android 11 OEM stock T290XXU3CUK4 kernel (November 2021 Update).
System partition based on CAOS 11.0 v316 (March 2022 Security Update)
Updated TWRP recovery to v3.6.1_11-0 (20220327).
Stripped product partition to get .zip update under the 2GB limit.
20220220:
Boots normally for offline (cold) charging
System partition based on CAOS 11.0 v315 (January 2022 Security Update)
Updated TWRP recovery to v3.6.0_11-1 (20220220).
Updated Google apps from latest OpenGapps Stock variant (20220215) w/ rollback for WebView
20211121:
Updated to Android 11 OEM stock T290XXU3CUG4 kernel (July 2021 Update).
Switched underlying GSI from LineageOS 17.1 to CAOS 11.
Updated TWRP recovery to v3.5.2_9-1 (20211017).
Updated Google apps from latest OpenGapps Stock variant (20211120) w/ rollback for WebView
IMPORANT NOTE: Dirty flash is not possible because we're transitioning to Android 11 kernel. Use Oden and do a factory reset from TWRP.
20210516:
Switched GSI from custom AOSP build to the latest LineageOS 17.1 (20210512).
Restored enforced OEM file-based encryption to work around issue with screen lock.
Sized boot animation correctly for 720p screen.
Worked around issue with OpenGApp's Google Recorder installation.
Updated to OEM stock T290XXU3BUC1 kernel (March 2021 Update).
Updated TWRP recovery to v3.5.2_9-0.
Updated Google apps from latest OpenGapps Stock variant (20210515)
20210104:
Updated to OEM stock T290XXS3BTL6 kernel (December 2020 Update).
Updated TWRP recovery to v3.5.0_9-0.
Updated Google apps from latest OpenGapps Stock variant (20201223)
20201223:
Initial build based on OEM stock T290XXU3BTI2 kernel (September 2020 Update) and AOSP 10.0 v222.
Latest Google apps from Stock variant of OpenGApps (20201205)
Instructions:
From OEM stock firmware:
Unlock bootloader
Ensure matching OEM build (e.g. T290XXU3CUG4) is installed
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install custom ROM tarball (.tar.md5 file) to AP with Odin
When TWRP launches, factory reset with Wipe->Format Data. (Not necessary for incremental upgrades.)
Reboot to system
From existing TWRP install (for incremental updates):
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install, select your update (.zip file), and then swipe to install
Reboot to system
Source:
android_device_samsung_gtowifi
Phh-Treble
Donations:
Your support is always appreciated! Just click here.
I'm leveraging a ton of work done by @phhusson for Treble GSIs, so please show him some love here!
Note: If you install Google Recorder from the Google Play Store, it works just fine. The issue is with the pre-installed APK from OpenGApps.
Hello! Finally first custom rom for our tablet =)
Using this for couple hours, it seems, almost everything works pretty fine. When i installed, the first issue was Google Assistant, cant skip this while first setup. Then i installed Magisk and see that SafetyNet check failed (but basic is true). SafetyNet on stock firmware failed too, but MagiskHide always help. In your ROM, if i turn on MagiskHide, i got cyclyng reboot, over and over again until i turn "hide" off.
Its really sad that MTP is not working.
About the rom: Everything good, no trash apps, works faster than stock, battery drain good... and... i dont know what i can say else =)
Thank you so much for this work!
Also i have a one question. Can you make a custom Kernel with GPU Overclock? Tablet not so bad and run some games pretty well, with overclock they can be runs much better. GPU is a bottleneck in this tablet i think.
Sorry for bad English, if it is =)
eclipse00074 said:
SafetyNet check failed (but basic is true). SafetyNet on stock firmware failed too, but MagiskHide always help. In your ROM, if i turn on MagiskHide, i got cyclyng reboot, over and over again until i turn "hide" off.
Click to expand...
Click to collapse
SafetyNet fails by design on any device with an unlocked bootloader and custom ROM. Magisk has its tricks to try to fool SafetyNet, but it's a bit of Whack-a-Mole game.
eclipse00074 said:
Can you make a custom Kernel with GPU Overclock? Tablet not so bad and run some games pretty well, with overclock they can be runs much better.
Click to expand...
Click to collapse
Unfortunately, the Android 10 kernel source that was posted last week is not working. It compiles fine, but builds to a significantly different size and crashes to the bootloader when packaged in either boot or recovery images. Until that's addressed, I can't provide an MTP fix or any overclocking.
Note: I just posted a v3.4.0-1 update to my TWRP for SM-T290 thread that includes a new custom T290UES3ATC1 kernel fixing MTP support. If you install it over the TWRP build included in this build, it will allow file transfers on this custom ROM by rebooting to recovery.
Since this is an Android 10 custom ROM, I can't use it in the boot image, but it's a workaround until we get working T290XXU3BTI2 kernel source.
Hi, there. I've managed to get the image installed, used the compatible version, etc. After rebooting, I got to TWRP, did the wipe, etc. Upon reboot, I get through to the setup process, skip the SIM setup stuff (no cell stuff in this T290) and then when trying to add a wifi connection, it never completes the "Connect to WiFi" step. If I skip, I can get through manual set up of the basics, manual time config, a few other prompts. All that seems okay. But even when I get to the main menu menu, it seems like everything is working (pulls up, etc) but I'm still not connected. The WiFi radio appears to be turned completely off. Each time I try to turn it back on, it flashes on for a split second, then immediately turns off again.
Any ideas I can try to get this enabled?
Edit: Bluetooth is working, was able to connect to another device. The device had previously been using WiFi with the stock image with no problems.
qntmcat said:
Hi, there. I've managed to get the image installed, used the compatible version, etc. After rebooting, I got to TWRP, did the wipe, etc. Upon reboot, I get through to the setup process, skip the SIM setup stuff (no cell stuff in this T290) and then when trying to add a wifi connection, it never completes the "Connect to WiFi" step. If I skip, I can get through manual set up of the basics, manual time config, a few other prompts. All that seems okay. But even when I get to the main menu menu, it seems like everything is working (pulls up, etc) but I'm still not connected. The WiFi radio appears to be turned completely off. Each time I try to turn it back on, it flashes on for a split second, then immediately turns off again.
Any ideas I can try to get this enabled?
Click to expand...
Click to collapse
Okay, all weekend I've been trying to figure out why wireless isn't working on my custom kernel, but it appears the OEM kernel isn't working as well...and I didn't even realize it. This is actually a hugely valuable data point that will drive my troubleshooting in an entirely different direction.
I'm embarrassed that I missed this in my initial smoke testing, but at least I know that my MTP fix is solid. More info to follow...
Awesome, I passively helped with a thing! =)
qntmcat said:
Awesome, I passively helped with a thing! =)
Click to expand...
Click to collapse
I can still only reproduce the wireless networking issue with kernel's built from Samsung's posted kernel source. The released T290XXU3BTI2 boot image works fine (and my original tarball shouldn't have replaced it). Did you upgrade to the OEM release of T290XXU3BTI2 prior to installing my custom ROM? If not, you may be running with an Android 9.0 kernel and Android 10.0 vendor partition.
Hm. I believe I did, but I went through a few iterations before I got everything to work right. (Not super familiar with Odin.) I restored everything by using that OEM image, pushed through Odin. Restarted the system and caught it back into download mode and replaced AP with your image ( Nexus_Stock_AQ_T290XXU3BTI2-20201206.tar.md5). Restarted, caught TWRP, and used it to wipe the data and cache. Restarted. Long cycle, followed by the "Let's get started" screen.
I can try this again tomorrow, starting from scratch in case I messed something up.
I've gotten it maybe working after a few iterations. I'm not expert at this, so this is pure cargo-cult work of just trying to follow the various instruction sets out there, but I've tried several iterations and documented a few FAIL messages. Try not to laugh too hard at my flailing.
What I did:
1. Restored to OEM (ODIN 3.14.4, used theBL/AP/CP/CSC from XAR-T290XXU3BTI2-20201021133521.zip)
--Restore completed normally
2. Confirmed functional. Performed "Let's Go" setup. WiFi was working and detected my AP during setup. Did device registration etc.
--Tablet working normally
3. Stopped tablet, put back into download mode,used Odin3 again , AP = Nexus_Stock_AQ_T290XXU3BTI2-20201206.tar.md5 (no BL / CP / CSC selected)
--Fail at system.img.ext4
--Error on the tablet: SW REV CHECK FAIL : [system]Fused 3 > Binary 0
4. Restarted, and redid step 1 to restore back to stock.
--Did not confirm status, in case first boot did something to cause the issue
5. Restarted, and repeated step 3
--Same failure point / message
6. Restarted, redid step 1 again to restore
7. Restarted immediately and restored again, this time using stock BL / CP / CSC along with custom AP above.
--Same failure point / message
This next works, but there is an error, an
8. Reread information above, decided to apply the TWRP MTP correction you list above. I know this is stupid, because of version differences, but I thought it might be worth a try because I think this may have been what I did to get it partly working before. (Is there another TWRP MTP corrected image I would use here??)
9. Repeated step 1 to get fully stock
10. Restarted, Pushed the TWRP image from your post reference above in AP, along with the BL/CP/CSC files from BTI2 (because dumb? This seems like it shouldn't work because of the version difference.)
11. Pushed without issue. Made it to the TWRP menu. Did a wipe. Restarted.
12. Used Odin to push stock BL/CP/CSC files along with your custom AP again.
13. It worked (kinda.) I did not get the rev check fail I got before, but I did get an error when the vbmeta.img came up which read: SECURE CHECK FAIL : VBMETA -- But Odin kept pushing and gave me a PASS! at the end.
14. Restarted. Again, caught TWRP on the restart and told it to wipe again (just to be safe, but this could also have just been stupid)
15. Restarted.
16. Okay, this time I got to the "Start" button, and it actually made it to the wifi screen *and detected my AP!
17. Set up google account -- Initial login worked, but 2-step verification did not (brings up the correct prompts, but both the bluetooth and usb titankey get to a certain point and then halt. In the case of the bluetooth, it gets to the point where it says you need to enter the 6-digit code from the back of the key, but pressing NEXT button does nothing. In the case of the usb titankey, it prompts for the "tap the gold disc", I get lights on the titankey, but it never recognizes the tap.)
18. Used the "tap on a phone" method instead,, which worked.
19. Noticed an odd message after the "checking your account" message, couldn't catch all of it, but it said something about screen lock already being on. Probably benign.
20. Changed font sizes and swapped wallpapers just to check them out. Works as expected.
21. Tested Play Store. Loads. Was able to update apps (some are still updating) and install a few things I wanted. No issues.
22. Wanted to validate that the bluetooth titan key worked, so I went and paired it. Works fine from this level, got the "enter the code" prompt from paring,.
23. All apps I've tried so far have worked. Will explore some underpinnings to see if I find any other goofiness.
So, WiFi works now? Didn't work last times I did it a few days ago? Not sure what I did different, but pushing TWRP (even if it's the wrong version) seems to have done the trick.
(Now I just have to try to parse out whether I need to do the multidisabler / root / other stuff.)
I did find something not working, which is the screen lock. I am unable to get it to set to anything other than SWIPE. It *tries* to set it when I go to pin/password/pattern, it loads the change function for that thing, but when I complete the change, I get the same error I got during setup:
Screen lock was already changed. Try again with the new screen lock.
Additional: While bluetooth seems to be working for device connections and so on, I don't appear to be able to get sound output to actually go there, even when the paired device is listed as the correct one for sound output. Probably more of my just being wrong and uninformed.
qntmcat said:
Hm. I believe I did, but I went through a few iterations before I got everything to work right. (Not super familiar with Odin.) I restored everything by using that OEM image, pushed through Odin. Restarted the system and caught it back into download mode and replaced AP with your image ( Nexus_Stock_AQ_T290XXU3BTI2-20201206.tar.md5). Restarted, caught TWRP, and used it to wipe the data and cache. Restarted. Long cycle, followed by the "Let's get started" screen.
I can try this again tomorrow, starting from scratch in case I messed something up.
Click to expand...
Click to collapse
After going from stock to custom ROM you must FORMAT , not just wipe, the data partition. Wiping does NOT get rid of the encryption.
lewmur said:
After going from stock to custom ROM you must FORMAT , not just wipe, the data partition. Wiping does NOT get rid of the encryption.
Click to expand...
Click to collapse
Interesting. I will have to go through this process again, perhaps.
Will it work on the SM-T295 model?
Edit: And also can you provide me with a screenshot of the ROM? Thanks
I also have the Bluetooth connects but no audio issue. It instead plays through the speaker. Also the same issue if you plug headphones in via the headphone jack, but at least in that case you can hear through the headphones. Love the nexus theme, can't stand the samsung UI.
So can this ROM be used on SM-T295?
Also having the "no audio through Bluetooth" issue. other than that, build is awesome!
I am having trouble flashing this on my tablet; I have OEM unlock enabled and have unlocked the bootloader. It went through a reset after this and I confirmed that my version is T290XXU3BTI2. I flashed via Odin and had a failure like qnmtcat (SW REV CHECK FAIL : [system]Fused 3 > Binary 0), so I flashed back to T290XXU3BTI2 and then tried again. Now, I am stuck at the pre-boot software update error screen and can't get into anything or restore via Smart Switch as directed on the screen; I have tried various button combinations at various times (holding Vol + & Vol - stops boot at unlocked bootloader warning; pressing Vol + & Vol - opens Options menu, but all options return to error screen; from power off Vol + & Vol - & inserting cable returns to error screen). I haven't used Odin or custom ROMs in a few years, but I'm not unfamiliar with the process from that time. Thanks for any assistance! I would REALLY like to get a ROM like this going because the tablet is painfully slow for me on stock.
UPDATE: I was able to flash back to the OEM ROM and it is running fine now, but still would appreciate any help in figuring out what I am doing wrong and why it isn't working for me. TIA
UPDATE #2: I got it to work doing mostly the same steps as qnmtcat: from stock, flashing the TWRP 3.4.0-1 linked above and then the ROM; I did still get an error with vbmeta, but I haven't noticed the effect of that yet. I also previously had issues getting into TWRP using the button combination in the OP and it seems like holding just the Vol + beginning immediately after pressing Power to bypass the unlocked bootloader warning screen works better for me.
WeededSquash said:
UPDATE #2: I got it to work doing mostly the same steps as qnmtcat: from stock, flashing the TWRP 3.4.0-1 linked above and then the ROM; I did still get an error with vbmeta, but I haven't noticed the effect of that yet. I also previously had issues getting into TWRP using the button combination in the OP and it seems like holding just the Vol + beginning immediately after pressing Power to bypass the unlocked bootloader warning screen works better for me.
Click to expand...
Click to collapse
looks like the exaxt same process I had to take (first twrp 3.4.0-1, then rom), same difficulties with accessing twrp recovery, volume up button seems to do the trick better.
do you have sound routing through bluetooth, or also no sound going to bluetooth device, although connected?
shmigao said:
looks like the exaxt same process I had to take (first twrp 3.4.0-1, then rom), same difficulties with accessing twrp recovery, volume up button seems to do the trick better.
do you have sound routing through bluetooth, or also no sound going to bluetooth device, although connected?
Click to expand...
Click to collapse
I had the same issue UNTIL I played with some of the settings in the "Phh Treble Settings"! Try enabling "Force-disable A2DP offload" in "Misc features" and then restarting; that seemed to work for me.