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.
So here they are -
1. First, Is there a way to create a fastboot rom by extracting files from the device? Or you just have to download it?
The reason - As I've always found that stock roms in any phone are the most stable, and it'd be nice if we could create a fastboot rom out of it. Not to forget that we can also save a lot of bandwidth.
2. I recently tried to unlock my device and I was met with an error "wait 72 hours, use your device actively". So what rules I have to follow?
Moreover whenever I try to close my mobile connection whether through notification tab or inside settings, my device restarts.
Are these related? Though if I'm quick enough that I close internet before sim could load and show the H/LTE sign, then it doesn't restarts. But if I turn it later on and decide to shut it off, then it's bound to restart.
Was just tapping on usb tethering and it restarted, don't know if my connection went off as it rebooted very quickly, but it restarted again.
Update : Tried to switch from mobile data to wifi, still restarted. Sometimes if the sim is a little slow to connect to internet and I turn it off, then it doesn't restart either. The data got turned on later and got shut off automatically as in actuality it was off, but the phone didn't restarted then.
3. I'm having some problems with face recognition. First I registered in a dark environment, unlocked it 2/3 times right away. But when I tried later, it didn't worked several times either in dark or well lit environment. Then I installed it in a well lit environment, same thing worked 2/3 times right away, but as soon as I changed the location to dark or back to well lit, it didn't worked again. Just tried it RN, it worked several times except a few times, so what 's going on here? I'm confused.
Update : I think it's a distance issue.
4. This is a general question regarding miui. Where is the data saver (restrict background data) feature in miui? I've tried several times to find it in different mi phones. But was never able to find it. It's been here from kitkat or maybe even older, correct me if I'm wrong. So why not provide it in miui, such a feature rich rom? Is it hidden somewhere?
5. The stock rom my phone has is based on Android 8.1 (8.1.0 OPM1.171019.011) to be exact, for rom version refer to reply. I've tried different versions of gcam, but none of 'em has worked for me. Normal camera app works fine, nothing I've encountered yet.
These are the versions I've tried -
* F1v9.5_6.2.030.apk (Couldn't install as 6.2 is only supported by android pie)
* MGC_6.1.021_XCAMBase_F1_v5a.apk (Installed and worked, details below)
* MGC_6.1.021_Potter_v7.1_san1ty.apk (Installed, didn't open)
* MGC_6.1.021_Potter_v7_san1ty.apk (Installed, didn't open)
On photo, the camera lags like I'm playing a game at 2-3 fps, same for other photo related options. Except for panaroma, photo sphere, lens blur, these I didin't had problem with. Except panaroma pic never showed up in camera app or gallery. In video it doesn't lag, so recording normal video was fine. But when I recorded a slo mo video, it lagged after the recording, inside & out the camera app. Inside gcam the audio was fine but outside it was muffled. By outside I mean gallery app & vlc player.
I may try other versions but each app is so big.
Gurkirat_Singh said:
So here they are -
1. First, Is there a way to create a fastboot rom by extracting files from the device? Or you just have to download it?
The reason - As I've always found that stock roms in any phone are the most stable, and it'd be nice if we could create a fastboot rom out of it. Not to forget that we can also save a lot of bandwidth.
2. I recently tried to unlock my device and I was met with an error "wait 72 hours, use your device actively". So what rules I have to follow?
Moreover whenever I try to close my mobile connection whether through notification tab or inside settings, my device restarts.
Are these related? Though if I'm quick enough that I close internet before sim could load and show the H/LTE sign, then it doesn't restarts. But if I turn it later on and decide to shut it off, then it's bound to restart.
Was just tapping on usb tethering and it restarted, don't know if my connection went off as it rebooted very quickly, but it restarted again.
Update : Tried to switch from mobile data to wifi, still restarted. Sometimes if the sim is a little slow to connect to internet and I turn it off, then it doesn't restart either. The data got turned on later and got shut off automatically as in actuality it was off, but the phone didn't restarted then.
3. I'm having some problems with face recognition. First I registered in a dark environment, unlocked it 2/3 times right away. But when I tried later, it didn't worked several times either in dark or well lit environment. Then I installed it in a well lit environment, same thing worked 2/3 times right away, but as soon as I changed the location to dark or back to well lit, it didn't worked again. Just tried it RN, it worked several times except a few times, so what 's going on here? I'm confused.
Update : I think it's a distance issue.
4. This is a general question regarding miui. Where is the data saver (restrict background data) feature in miui? I've tried several times to find it in different mi phones. But was never able to find it. It's been here from kitkat or maybe even older, correct me if I'm wrong. So why not provide it in miui, such a feature rich rom? Is it hidden somewhere?
Click to expand...
Click to collapse
sir, you never mention which version you are on ? since Boot is locked so definately MIUI but which one? global/beta/Eu/ Stable/chine etc?
anways..
Answer for 1, - No you have to redownload it, the Fastboot Rom consist of few extra files like persist and recovery and if they are update you must use the latest one. however via twrp you can take system/data/ and other partitions backup if you want...
for 2. after 72hours, goto dev option and try enabling oemunlock, it will give you warning but do it, come out of dev option and go in and do it again, repeat until the UNLOCK setting stays on UNLOCK, (don't know why it is, but this is how it is,,,, ) , later verify your miui account and sim, keep signed in. download unlocker and sign- in and try unlocking the device (make sure all qualcom drivers are installed)
for 2 again, This is very strange, ONE OF ITS KIND error I AM hearing , I honestly thought this bug is ONLY custom rom related! , you see Poco f1, Beryllium uses MODIFIED VENDOR IMAGE ( can be found at) https://mirror.akhilnarang.me/MIUI/beryllium/.
now these modified vendor images by MIUI dumps logs on data/data/netstat (specially if you are USB TETHERING on 3g, ... you will start suddent System UI reboots and some com.android.xyz processes crashing errors and if you toggle Airplone mode 3g/4g or usb tethering from quick setting , device either hung or system ui restarts or device reboots.
now this error is always in all custom roms due to vendor image
solution? DELETE all files from data/data/netstat and reboot (rooted device on custom rom)
for locked device (unrooted) you may have to flash updated version of miui to fix this bug!
Once you unlock device take latest vendor image ( i am using 9.6.27.9-0 , it has better battery life) and flash custom rom...
for 2 again,,,, some users are complaing that miui10.3.6 alters fastboot commands! and twrp no longer works! , make sure you don't flash miui10.3.6,
for no3,, i don't use facial unlock feature, i will study more and will get back to u if relevent.
for 4
Open MIUI Security App.
Tap on Data Usage Tool.
Tap on Restrict Data Usage.
Now find out those data hunger apps and restrict them by tapping on the green tick.
@YasuHamed First of all big thanks for such a descriptive answer.
1. Now, I'm on stock miui rom i.e. MIUI global stable 9.6.14.0(OEJMIFD).
So If i haven't updated my rom in any way what so ever. can I create a fastboot rom out of it? If I can then also, will that fastboot rom have all the system settings I have on my phone right now? Or will they be default?
2. While not exactly as you said but something similar happened. I do remember enabling the option of oem unlock, but it was turned off. It didn't gave any warnings, so I enabled it multiple times maybe 4, then on the 4th time it showed me a warning and after that it was enabled permanently, even after several boots and reboots.
IDK which "unlock setting" do you mean, which has to say unlock? Is it something different than I mentioned here or are you talking about Mi unlock status, cause I already tapped the 'add account and device' option in it.
Yes really strange indeed. I'm just worried that my hardware isn't damaged? Cause I just got the phone 2 days ago and if it's only a software thing then it's fine. As I'm sure installing/flashing rom would fix it! But I can't RN as you know the time period. Why am I worried? I took my phone to a mobile shop to put lamination on it asap as to avoid any scratches. As you may know that they use heat gun, to do it properly around the curves, I'm just getting a little worried that it damaged my phone's hardware, please give me hope.
Some other strange things happened as well. After some reboots, when I went into file manager app, it would open showing previews etc. but as soon as I click on storage/folders, it says "disconnected" and later I get a message "couldn't add error 10000" like after 10-15 seconds, as I vaguely remember. But after some reboots it would work just fine so IDK what's going on.
3. I also think it's about the experience. More I used it, I think infrared illuminator doesn't throw rays too far, so you have to keep your face a little close.
4. Thanks I found it. But I don't think it is very effective, feature wise. And I also think it isn't working that well RN as it keeps showing the data usage as 0, maybe cause of the bugs? Also the features like restricting data etc for individual apps is good but if you have to restrict background data for each &very app, you have to do that individually. Though if i restrict data, can an app still use background data? As they are different menus. Also it doesn't show usb tethering or hotspot data or anything like that in the list.
Check my 5. question.
Gurkirat_Singh said:
@YasuHamed First of all big thanks for such a descriptive answer.
1. Now, I'm on stock miui rom i.e. MIUI global stable 9.6.14.0(OEJMIFD).
So If i haven't updated my rom in any way what so ever. can I create a fastboot rom out of it? If I can then also, will that fastboot rom have all the system settings I have on my phone right now? Or will they be default?
2. While not exactly as you said but something similar happened. I do remember enabling the option of oem unlock, but it was turned off. It didn't gave any warnings, so I enabled it multiple times maybe 4, then on the 4th time it showed me a warning and after that it was enabled permanently, even after several boots and reboots.
IDK which "unlock setting" do you mean, which has to say unlock? Is it something different than I mentioned here or are you talking about Mi unlock status, cause I already tapped the 'add account and device' option in it.
Yes really strange indeed. I'm just worried that my hardware isn't damaged? Cause I just got the phone 2 days ago and if it's only a software thing then it's fine. As I'm sure installing/flashing rom would fix it! But I can't RN as you know the time period. Why am I worried? I took my phone to a mobile shop to put lamination on it asap as to avoid any scratches. As you may know that they use heat gun, to do it properly around the curves, I'm just getting a little worried that it damaged my phone's hardware, please give me hope.
Some other strange things happened as well. After some reboots, when I went into file manager app, it would open showing previews etc. but as soon as I click on storage/folders, it says "disconnected" and later I get a message "couldn't add error 10000" like after 10-15 seconds, as I vaguely remember. But after some reboots it would work just fine so IDK what's going on.
3. I also think it's about the experience. More I used it, I think infrared illuminator doesn't throw rays too far, so you have to keep your face a little close.
4. Thanks I found it. But I don't think it is very effective, feature wise. And I also think it isn't working that well RN as it keeps showing the data usage as 0, maybe cause of the bugs? Also the features like restricting data etc for individual apps is good but if you have to restrict background data for each &very app, you have to do that individually. Though if i restrict data, can an app still use background data? As they are different menus. Also it doesn't show usb tethering or hotspot data or anything like that in the list.
Check my 5. question.
Click to expand...
Click to collapse
sir Gurkirat_Singh
1. sir you are on Miui9.6 which is based on oreo.I have personally updated till 10.0.03 and have all the fastboot command working fine.
you may download miui9.6.22 (a bit updated version from what you are currently on) from
http://en.miui.com/thread-3995650-1-1.html ( both Recovery (1.6gb) & Fb rom (2.5gb) as backup.
2. under Developer options , poco f1 has this trick that OEM UNLOCK doesnt stick on UNLOCK and keeps coming to default once after you exit Developer option. on my 5th attempt it finally stick to UNLOCK and i was able to unlock the device from unlocker Tool.
3. I havent removed my poco sticker from back (yet), put 9h class, bought extra skin my self and book cover too so yes I second that. I always protect my devices like part of me , even the retired ones are sleeping in boxes with proper covers and unused accories!,
now, update your rom and try again to toggle 3g/4g usb tethering. 99% chances are its software issue! and i have faced this issue many times and its my 5th month with device so i havent noticed any hardware damage or performance / speed problems yet... so don't worry. YES few kernels affect network connectivity, however I am on Optimus Drunk kernel on Havoc 2.8 and its working like a charm!
-about file manager issue, can you try the same with FX File Explorer? and report back plz
4.if you restrict globally then miui will only allow system apps to use data in background as and when needed. MIUI won't allow facebook/whatsapp and other VOIP callers to work in the background. Once in restricted mode on miui9 on RN5pro, I used to miss call on whatsapp unless i wake the device up and notifications starts appearing that i have many whatsapp miss calls!, this feature went even worse on rn5pro when i was on dual sim, miui use to prefer carier sim over data sim always! so yes miui has strict data usage control.
5. i am unable to find 5th question plz help
few screen shots of my poco f1 on HAVOC2.8 / OD kernel build20190820 / magisk19.3 / gapps nano
@YasuHamed
1. I didn't got the answer to my question, please read my question again.
2. I'm gonna assume you mean 'oem unlock' got enabled and I'd be able to unlock after 72 hours are over.
2. a. I hope so as well, thanks again.
Although sometimes it would run fine and even after turning off mobile data, wifi, usb tethering etc. it won't restart. I thought the oem unlock setting helped but when I tried not an hour ago, it restarted. Same thing with file manager, it's working fine now, I'm sure 3rd party file managers would work fine as well. Only a few times, it showed that 'disconnected' error.
4. I guess I'd just have to hit and trial myself.
5. Check my OP (original post).
Gurkirat_Singh said:
@YasuHamed
1. I didn't got the answer to my question, please read my question again.
2. I'm gonna assume you mean 'oem unlock' got enabled and I'd be able to unlock after 72 hours are over.
2. a. I hope so as well, thanks again.
Although sometimes it would run fine and even after turning off mobile data, wifi, usb tethering etc. it won't restart. I thought the oem unlock setting helped but when I tried not an hour ago, it restarted. Same thing with file manager, it's working fine now, I'm sure 3rd party file managers would work fine as well. Only a few times, it showed that 'disconnected' error.
4. I guess I'd just have to hit and trial myself.
5. Check my OP (original post).
Click to expand...
Click to collapse
sir
1. I never read any such method so far where you can reverse engineer the extracted files in partitions and pack them back as fastboot rom. and to think of it thats almost impossible because stockroms usually comes with digitally signed by vendors ensuring no foul play.
2. once your 72hrs over, just unlock the oem unlock switch from Dev option, verify sim of on your mi account, download the unlock tool, login using same mi account, hit unlock, after success, the device will BOOT on POCO logo and "UNLOCKED" will start appearing (always) and all data partition, internal storage will be wiped! so make sure you take backup!
2a. with me on custom rom it wasn't a sure thing but it used to happend randomly when least expected.
5. on oreo , GCAM version came in sep2016 worked for me and later ones are for pie and kept crashing (please check old version on apkmirror)
@YasuHamed Thanks for all the help.
5. I did found a version that is working fine for now. But the features I was interested in was super res zoom, night mode, slo mo etc. Super rez wasn't that impressive(seemed similar to stock zoom), night mode either, slo mo still doesn't work properly and phone heats up, even when I'm not using too old of a version of gcam. Even the stock cam app took some good shots with zooming.
And if those features will work better with pie version then IDK what to say cause that new version would come with better stock cam having slo mo, night mode and all that shiz if not everything. So I'm kinda thinking is this gcam port really relevant? It drastically changed image quality with my RN3 but I don't see that now.
Edit: Also I wanted to say that my phone was working fine now i.e. no reboots after closing mobile data or wifi or switching. But you know what they say don't celebrate too soon. As soon as I used usb tethering the problem arised again, I wasn't able to it for 2 days as my PC wasn't booting. Same reason why I wasn't able to reply to you earlier.
Not only this, this whole bugged situation has started to irritate me a lot. Just today I was trying to run flash on my android. And even on the supported browser, it just wouldn't show up. I really hope after I unlock this device, all of these bugs would go away after the data gets deleted, or I'm gonna be more disappointed.
@YasuHamed This has really started to piss me off now. It has started again.
While IDK if the camera or flash not working properly are related to this whole bugged system or not. But I guess usb tethering is the trigger to this whole thing. Everything was working fine, it started to record the mobile data usage, didn't turned off when turned off the mobile data and even worked when I used usb tethering, but suddenly it reboots and the whole **** show all over again. I'm really pissed now. Oh btw it started showing 0 data used AGAIN.
Gurkirat_Singh said:
@YasuHamed This has really started to piss me off now. It has started again.
While IDK if the camera or flash not working properly are related to this whole bugged system or not. But I guess usb tethering is the trigger to this whole thing. Everything was working fine, it started to record the mobile data usage, didn't turned off when turned off the mobile data and even worked when I used usb tethering, but suddenly it reboots and the whole **** show all over again. I'm really pissed now. Oh btw it started showing 0 data used AGAIN.
Click to expand...
Click to collapse
please consider upgrading to MIUI10.3.x , download the complete recovery rom and name it as update.zip and put it in download folder and open updater and call the rom from there , and flash it, I suggest CLEAN FLASHING so all the data will be deleted!
plz take backup!
@YasuHamed can you please find me fastboot rom for miui 9.6.14(OEJMIFD), I tried but I couldn't find it. I'd do the full clean flash through edl mode. That would resolve any bugs related software, right?
Come to think of it, why did this all started happening at the first place? As I remember, it all started after a failed attempt to unlock, I mean not fail fail, I just had to wait before I could do so. Do you see any patterns?
Also if you know anything in this regard, did the stock rom (9.6.14) had such problems back in the day?
Gurkirat_Singh said:
@YasuHamed can you please find me fastboot rom for miui 9.6.14(OEJMIFD), I tried but I couldn't find it. I'd do the full clean flash through edl mode. That would resolve any bugs related software, right?
Come to think of it, why did this all started happening at the first place? As I remember, it all started after a failed attempt to unlock, I mean not fail fail, I just had to wait before I could do so. Do you see any patterns?
Also if you know anything in this regard, did the stock rom (9.6.14) had such problems back in the day?
Click to expand...
Click to collapse
frankly i never used my poco on miui either on 9 nor on 10 ,
the day I got, I placed unlock request and after 3-4 days, I unlocked my device and put it on HAVOC and since then my experience is based on custom roms but i did flash miui 10 in between just to have a taste of it! and came back to havoc in a day or two, hence i never deeply tested these feature.
however I do know that modified vendore have created usb tethering problems throughout devices
https://mirom.ezbox.idv.tw/en/phone/beryllium/roms-global-stable/
@YasuHamed I don't think mine contains modified rom. As I went ahead and checked all the possibilities like using cn as in china in the codename of a global rom, updates are also working. I even went ahead to check the authenticity of my device. It checks out with some other things on the box as well. So I'm 100% sure, that this has got nothing related to that.
Some other things which I tried in the meantime. I wanted to test if I can run tegra games on this device. So I installed gltools and build prop. Gltools to make the app believe that my device has the gpu it's looking for. Build prop to make app believe I have the device on which this is supposed to run. But I ended up with the same results. So IDK what I did wrong there? In this regard I wanna ask that, is it possible for root checker to show your device is rooted when in fact its not properly rooted.
Why am I asking this? Cause while going through rooting procedure I skipped a few steps like not flashing 'disable force encryption treble' which I did notice after unlocking, during first boot, the device did do some encryption. I skipped that step cause of something mentioned on this link https://twrp.me/xiaomi/xiaomipocophonef1.html regarding dm verity, but as I just checked the same is mentioned regarding rn3 so IDK what to make of this now, but what I did is not 'swipe to allow modifications' and click on 'read only' in twrp recovery and it did rebooted to recovery properly. As mentioned in the link that some system could force to flash stock recovery. Other than that, not factory resetting, data wiping after root, but does it really matter that much?
I can hear you say that dude you're playing with your device too much, of course it's gonna have these problems. To that, I say I didn't do anything like this, prior to unlocking but the problems were still there if not all of them. So what is the root cause of this then? Do I really need to take it service centre to get it checked out or just flashing the rom through edl mode would fix this?
Not just that after I made those changes in build prop(not including gltools) something very weird/interesting happened. If I would restart my device the boot logo shown is poco but the boot splash is mi logo. And when it rebooted after closing the internet, it would only show the mi logo but then I remember that it must've been soft(hot) reboot as it only shows boot splash.
Not only this, after rebooting the style of the rom changed as well. The icon on the home rearranged themselves a bit. So instead of seeing 5 icons in a row, it was all 4 icons on home as well as on app drawer. As you may know Kika keyboard is defaulty present in this rom but after the build prop modifications, whenever I lock my device and wake it up it started showing ads sometimes, maybe the same ad everytime IDK.
Another thing as you know there is an option of reboot to recovery under about phone updates. When I did that that it showed the 'android' logo. I tried it again but it kept showing the loading sign only.
Also how did you find these files? Thanks again m8. You know just for reference if I'd have to find them myself. Also what are those that say (rolled back).
Gurkirat_Singh said:
@YasuHamed I don't think mine contains modified rom. As I went ahead and checked all the possibilities like using cn as in china in the codename of a global rom, updates are also working. I even went ahead to check the authenticity of my device. It checks out with some other things on the box as well. So I'm 100% sure, that this has got nothing related to that.
Some other things which I tried in the meantime. I wanted to test if I can run tegra games on this device. So I installed gltools and build prop. Gltools to make the app believe that my device has the gpu it's looking for. Build prop to make app believe I have the device on which this is supposed to run. But I ended up with the same results. So IDK what I did wrong there? In this regard I wanna ask that, is it possible for root checker to show your device is rooted when in fact its not properly rooted.
Why am I asking this? Cause while going through rooting procedure I skipped a few steps like not flashing 'disable force encryption treble' which I did notice after unlocking, during first boot, the device did do some encryption. I skipped that step cause of something mentioned on this link https://twrp.me/xiaomi/xiaomipocophonef1.html regarding dm verity, but as I just checked the same is mentioned regarding rn3 so IDK what to make of this now, but what I did is not 'swipe to allow modifications' and click on 'read only' in twrp recovery and it did rebooted to recovery properly. As mentioned in the link that some system could force to flash stock recovery. Other than that, not factory resetting, data wiping after root, but does it really matter that much?
I can hear you say that dude you're playing with your device too much, of course it's gonna have these problems. To that, I say I didn't do anything like this, prior to unlocking but the problems were still there if not all of them. So what is the root cause of this then? Do I really need to take it service centre to get it checked out or just flashing the rom through edl mode would fix this?
Not just that after I made those changes in build prop(not including gltools) something very weird/interesting happened. If I would restart my device the boot logo shown is poco but the boot splash is mi logo. And when it rebooted after closing the internet, it would only show the mi logo but then I remember that it must've been soft(hot) reboot as it only shows boot splash.
Not only this, after rebooting the style of the rom changed as well. The icon on the home rearranged themselves a bit. So instead of seeing 5 icons in a row, it was all 4 icons on home as well as on app drawer. As you may know Kika keyboard is defaulty present in this rom but after the build prop modifications, whenever I lock my device and wake it up it started showing ads sometimes, maybe the same ad everytime IDK.
Another thing as you know there is an option of reboot to recovery under about phone updates. When I did that that it showed the 'android' logo. I tried it again but it kept showing the loading sign only.
Also how did you find these files? Thanks again m8. You know just for reference if I'd have to find them myself. Also what are those that say (rolled back).
Click to expand...
Click to collapse
-sir, most of your observations are pertaining to V9.6.14.0.OEJMIFD, where I am not on MIUI hence I will wait for other members to step in and share their views about them.
- you can always use "Disable-Force-Encryption-Treble" from https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389, when flashing rom (clean flash, FORMAT DATA) to disable encryption on kernel level.
- since Twrp official doesnt support OTA so if you call recovery from updater, it wont work! you may have to use Orange Fox (oct/nov2018) version which had OTA support or better flash full rom after downloading desired version from https://mirom.ezbox.idv.tw/en/phone/beryllium/roms-global-stable/
- what are you looking is from different world of android devices, such as TEMP ROOT, IVORY ROOT (sony xperia on android 5.1) days only! when nothing used to be changed but just to gain access of certain partition temporarily, temp root techniques used to apply to extract DRM KEYS. ITs not the case here hence you will have to root your device properly!
- about gpu, i never tried but you can used app such as FK kernel manage or Kernel Auditor to play with your GPU accordingly
- twrp usually ask keep system readonly whenever flashed new room its standard warning to avoid any bootloops since Twrp doesn't know you will be flashing kernel and/or disabling dm varity soon. so it warns you.
- don't worry POCO is FREE from ARB4 $hit so when page said ROLLED BACK, it means those version were recalled back for some buggs and an update released soon after!
@YasuHamed So IDK whether I was clear or not, cause I couldn't understand most of the answers you gave me, maybe they got mixed up, IDK. Anyways I'll try to keep it simple and answer in best way possible and keep it organised so there's confusion.
1. Thing I forgot to mention, after flashing 'disable force encryption treble' file, my root stopped working, I thought it was part of the whole bugged system. In actuality, when I checked the steps while it was flashing, it installed Magisk 16.7, I think. That's why root stopped working. After flashing latest Magisk, it worked fine. So, After flashing "disable" file, Can I flash Magisk over it to get the latest Magisk version? Will it affect the disabled function in any way? Currently I have 3 files, which one do you suggest -
Disable-Force-Encryption-Treble.zip
DisableForceEncryption_Treble_v18.0.zip
Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Third one is form the link you provided.
2. DK if TWRP supports OTA, but I was able to boot to TWRP after tapping on reboot to recovery, just saying. By full rom do you mean the stock roms?
3. Did you meant if it checks out in root checker, then it's properly rooted already!?
4. This FK Kernel Manager or Kernel Auditor, you talk about, does it works the same way as Build Prop or GLTools? Cause I'm not an expert in using these tools. I just followed the steps mentioned in this video https://youtu.be/Y1wPIHhM1Yw similarly for the other games I was trying to run by gathering build prop info related to shield tv/tablet/portable but it didn't worked in my favor.
5. So if you chose the option of 'swipe to allow modifications' options instead of 'read only', and your phone boots without any bootloops or anything, as I've done a lot of time on my RN3 without even thinking about it, does that mean that everything's fine? Even when you haven't disabled dm-verity and still are on stock kernel(the one contained in stock roms i think). Does stock kernel changes to custom when you flash a custom rom? Does TWRP makes any changes to stock one if your system boots without any above mentioned problems having stock rom? Any details regarding differences in these two options?
6. When you say an update released soon after? Do you mean same versions were released with bugs fixed or a new/next version was released? In other words, is it ok to try these versions with such bad bugs that they were called back? Were those system breaking bugs fixed in the same version? Also again, I'd really appreciate if you could tell me how'd you find these roms?
7. I'm almost certain that usb tethering is the trigger to these reboots when turning off internet. Cause if I power off the device and turn it on later, then turn on-ff data, it doesn't reboot but sometimes it does. But as soon as I turn usb tethering on, it would reboot and the whole debacle starts again. And the ads kika shows are different along side something related to ram cleaner everytime. So I think it does uses internet. IK you don't use miui, just putting the info out there, if someone thinks of stepping in later.
please view my replies sir
Gurkirat_Singh said:
@YasuHamed So IDK whether I was clear or not, cause I couldn't understand most of the answers you gave me, maybe they got mixed up, IDK. Anyways I'll try to keep it simple and answer in best way possible and keep it organised so there's confusion.
1. Thing I forgot to mention, after flashing 'disable force encryption treble' file, my root stopped working, I thought it was part of the whole bugged system. In actuality, when I checked the steps while it was flashing, it installed Magisk 16.7, I think. That's why root stopped working. After flashing latest Magisk, it worked fine. So, After flashing "disable" file, Can I flash Magisk over it to get the latest Magisk version? Will it affect the disabled function in any way? Currently I have 3 files, which one do you suggest -
Disable-Force-Encryption-Treble.zip
DisableForceEncryption_Treble_v18.0.zip
Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Third one is form the link you provided.
I flashed "DisableForceEncryption_Treble_v18.0.zip" and it worked/works, but I always flash before magisk., the current version is Magisk19.3 hence I recomend you to use the updated version, 16.7 is obsolete long back. However if 19.3 may give you bootloops then the max you can go back is Magisk18.0 (since after 18.1, Magisk started using different Script language unknown to some recoveries. However if BOTH (your recovery and Magisk are latest, it should work just fine
2. DK if TWRP supports OTA, but I was able to boot to TWRP after tapping on reboot to recovery, just saying. By full rom do you mean the stock roms?
once on RN5p I tried updating OTA via twrp, it never booted to update hence I recomend you to download full recovery rom 1.8gb, of the build you want and flash it via twrp
3. Did you meant if it checks out in root checker, then it's properly rooted already!?
plz try any root checker and see
4. This FK Kernel Manager or Kernel Auditor, you talk about, does it works the same way as Build Prop or GLTools? Cause I'm not an expert in using these tools. I just followed the steps mentioned in this video https://youtu.be/Y1wPIHhM1Yw similarly for the other games I was trying to run by gathering build prop info related to shield tv/tablet/portable but it didn't worked in my favor.
fk kernel manager or kernel Auditor does support editing build prop, apart from many tweaks for GPU and Cores. the video shows a simple edit in order to think your device is some other version of Galaxy to trick samsung app ; however The boy didn't explain why he just didn't install the already downloaded apk file from fortnite website ?
5. So if you chose the option of 'swipe to allow modifications' options instead of 'read only', and your phone boots without any bootloops or anything, as I've done a lot of time on my RN3 without even thinking about it, does that mean that everything's fine? Even when you haven't disabled dm-verity and still are on stock kernel(the one contained in stock roms i think). Does stock kernel changes to custom when you flash a custom rom? Does TWRP makes any changes to stock one if your system boots without any above mentioned problems having stock rom? Any details regarding differences in these two options?
if you are flashing MIUI From twrp, and DON"T wana ROOT then yes you should never allow system modification because then device will never boot in to system due to DM-Verity. However if you are rooting yoru device, try reading Magisk Lines, It always patch fstab and disable Dm-verity, once its disabled /system parition permision wont be verified on boot. So when you boot in to twrp and you know you are going to flash Magisk, you can ALLOW SYSTEM MODIFICATION swip
on Custom Roms it doesn't matter, because twrp never ask such question. "allow system modification" is only limited to StockRoms
6. When you say an update released soon after? Do you mean same versions were released with bugs fixed or a new/next version was released? In other words, is it ok to try these versions with such bad bugs that they were called back? Were those system breaking bugs fixed in the same version? Also again, I'd really appreciate if you could tell me how'd you find these roms?
the next version above ROLLED BACK one is the bug fixed. (now i don't know what exactly were they) . Also MIUI forums for devices always announce updates! you can google
7. I'm almost certain that usb tethering is the trigger to these reboots when turning off internet. Cause if I power off the device and turn it on later, then turn on-ff data, it doesn't reboot but sometimes it does. But as soon as I turn usb tethering on, it would reboot and the whole debacle starts again. And the ads kika shows are different along side something related to ram cleaner everytime. So I think it does uses internet. IK you don't use miui, just putting the info out there, if someone thinks of stepping in later.
well probably this is the bug of this version 9.6.14 hence you should upgrade atleast to 9.6.20 in order to compare
Click to expand...
Click to collapse
@YasuHamed Again a little bit confused by some answers, but I'll try to keep it simple.
1. Do you mean you flash "d-f-e-t" file before magisk? That's what I was asking, does magisk interfere with the steps, this file does, in anyway? And why didn't u used the 'third file', the one from the link you mentioned, isn't that the better one in some ways?
2. I never said I tried to install an OTA through TWRP. I just said I was able to boot to TWRP through 'reboot to recovery' option under system updates tab.
3. I checked it with one 'root checker' app, do I need to check with others? Can you name some?
4. He didn't used the same apk, cause he wanted to show & tried to explain, what kind of changes we were doing to the system, rather than just blindly following the instructions, like what normally happens in these scenarios. I thought that was given, anyways, I've tried same things before in past. When I had the apk, data/obb files of an app/game, I'd simply just try to install them on miui and they'd just crash, but doing the same thing on a custom rom and it works, no special steps. Similarly did all this work, and ended with crashes, maybe I'll do the same thing on a custom rom and it'll work. On that note, do you know where I can download stable builds of lineage OS, or do I just have to research which one is a a stable version, Or is it okay to download any latest nightly builds, the only thing they post on their official website?
5. If one taps on 'read only' option the first time, and when it boots to twrp again and doesn't asks for it. Can one find that option somewhere else in twrp? I did that and still I'm booting normally, how's that possible then, if you say system won't boot!? And what does that option 'allow system modifications' do exactly? How unlocking & rooting are different, security wise? Cause vendors like Xiaomi allow unlocking officially, which means it doesn't void your warranty, though I don't know what would happen if you walk in with an unlocked device in their service centre, cause I've never done it, But they still warn you about data stealing during unlock process etc. Although if you root your device then it's out of warranty, but it's a much simpler process than unlocking. So what's the difference, is the threat real? Or is it just marketing to keep you locked in the stock experience?
6. Again you didn't tell me how'd you find those roms!?
7. It's just really random, sometimes it doesn't restart even when internet is turned off, sometimes with usb tethering on or sometimes not even connected to the pc. Kika still shows them ads, also after an app is installed/uninstalled etc. Other than those appearance changes, I wasn't also able to dial down the brightness to the very low. Whenever i did it, it restarted, camera stopped working etc. I revert the changes I did in build.prop to make it poco again, it rebooted and the boot splash was fixed, but as soon as the ui showed up, the poco launcher kept crashing. It was good that I had my apps opened in background and miui remembers them even after reboot, otherwise there would've been no way to access build.prop, so I revert it back to any shield tv/portable/tablet settings and it started working normally. Finally I've decided, I'm gonna edl flash the stock rom and report back if these bugs happen again(I hope it's only software), I downloaded 2 roms over this period of time i.e. 9.6.14 & 10.3.7.0, will try and get back to you.
Sorry for the late reply, got a little busy.
sir ..........................
Gurkirat_Singh said:
@YasuHamed Again a little bit confused by some answers, but I'll try to keep it simple.
1. Do you mean you flash "d-f-e-t" file before magisk? That's what I was asking, does magisk interfere with the steps, this file does, in anyway? And why didn't u used the 'third file', the one from the link you mentioned, isn't that the better one in some ways?
1- Yes I flashed DFET before Magisk19.3 - and why i didn't use the third file, i remember in post one user confirmed this particular one working for him (atleast) so i downloaded that one.
2. I never said I tried to install an OTA through TWRP. I just said I was able to boot to TWRP through 'reboot to recovery' option under system updates tab.
2- ideally this is the case with recoveries which doesn't support OTA, OrangeFox based on OLD version of TWRP does support OTA , I NEVER TRIED but worth reading the post. you should find it in the Poco Development section
3. I checked it with one 'root checker' app, do I need to check with others? Can you name some?
3- I use THIS ONE
4. He didn't used the same apk, cause he wanted to show & tried to explain, what kind of changes we were doing to the system, rather than just blindly following the instructions, like what normally happens in these scenarios. I thought that was given, anyways, I've tried same things before in past. When I had the apk, data/obb files of an app/game, I'd simply just try to install them on miui and they'd just crash, but doing the same thing on a custom rom and it works, no special steps. Similarly did all this work, and ended with crashes, maybe I'll do the same thing on a custom rom and it'll work. On that note, do you know where I can download stable builds of lineage OS, or do I just have to research which one is a a stable version, Or is it okay to download any latest nightly builds, the only thing they post on their official website?
4- To get general IDEA about altering Build.Prop, The video is Good! however you can not assume Samsung Modded Android over MIUI's one! also It seems the boy in the video has Android7 where Miui Poco is atleast on 8.1, there is huge difference!
The only way to find out whether any type of build.prop (EVEN ON CUSTOM ROMS) will WORK or NOT on POCO; is to Try and find out yourself.
5. If one taps on 'read only' option the first time, and when it boots to twrp again and doesn't asks for it. Can one find that option somewhere else in twrp? I did that and still I'm booting normally, how's that possible then, if you say system won't boot!? And what does that option 'allow system modifications' do exactly? How unlocking & rooting are different, security wise? Cause vendors like Xiaomi allow unlocking officially, which means it doesn't void your warranty, though I don't know what would happen if you walk in with an unlocked device in their service centre, cause I've never done it, But they still warn you about data stealing during unlock process etc. Although if you root your device then it's out of warranty, but it's a much simpler process than unlocking. So what's the difference, is the threat real? Or is it just marketing to keep you locked in the stock experience?
5- Once twrp changes the /System as writable, cannot be undone from Twrp itself - since you have magisk16.7 as you mention earlier the dm-varity is turned off and you are booting normally.
-unlocking means, your device can accept fastboot commands to Alter various Partitions developed by Third Party! /recovery /system /vendor /oem etc
-Rooting is Gaining /system access in Android OS to perform Forbiddon and/or Unsafe Commands / Apps etc
- now your question about security , i will simply say! its HIGHLY UNSECURE to unlock your device & Root it!, there is debate about SeLinux Permissions to be Permissive or Enforcing , SELinux in enforcing mode is considered to be little better and secure but Permissive mode means any command can be run even by hacker to gain your /system access ! REFERENCE
- unlocked bootloader is also very unsafe! anyone can just flash any compatable recovery and atleast WIPE your data!
HENCE this is what i say to all my fellow friends and mates in general! if you are CONCERN security privacy , NEVER ROOT your device! or keep two devices, one being as family device! for fotos, emails contacts etc! and play with the other!
- about warranty! every region has different rules! my country's Xiaomi centre doesn't cover any brick devices because here they are alreadly selling many Redmi fones on UNLOCKED mode! directly from china!
6. Again you didn't tell me how'd you find those roms!?
https://c.mi.com/oc/miuidownload/index select poco and see officially available rom
7. It's just really random, sometimes it doesn't restart even when internet is turned off, sometimes with usb tethering on or sometimes not even connected to the pc. Kika still shows them ads, also after an app is installed/uninstalled etc. Other than those appearance changes, I wasn't also able to dial down the brightness to the very low. Whenever i did it, it restarted, camera stopped working etc. I revert the changes I did in build.prop to make it poco again, it rebooted and the boot splash was fixed, but as soon as the ui showed up, the poco launcher kept crashing. It was good that I had my apps opened in background and miui remembers them even after reboot, otherwise there would've been no way to access build.prop, so I revert it back to any shield tv/portable/tablet settings and it started working normally. Finally I've decided, I'm gonna edl flash the stock rom and report back if these bugs happen again(I hope it's only software), I downloaded 2 roms over this period of time i.e. 9.6.14 & 10.3.7.0, will try and get back to you.
EDL ? you mean fastboot rom flashing via miflasher!, thats not edl! to trigger EDL you must have
1. authorized Xiaomi Account
2. back panel of poco to be opened and short test point to put device in EDL
Sorry for the late reply, got a little busy.
Click to expand...
Click to collapse
@YasuHamed
1. I tested the third file. It worked without any problems even after flashing magisk. Cause it doesn't mess or flash any magisk files, it also detects what sort of root the phone have.
3. -> 2. I used the same app to check so.
3. You mention some good points there. That's the same reason, things worked out in custom roms and not miui in my earlier experiences. As miui is heavily loaded compared to any custom rom or samsung experinece. I'll try it on other OSs and report back. On the same note, from what I've read that lineage team doesn't release stable builds or at least not anymore. I'm currently downloading pixel experience. Should I go with this one or lineage os? Is it like any other custom OS or heavily loaded like miui? Also what is the difference between PE normal vs plus vs caf? Also I'm gonna try multi rom, as it would be much better for testing.
4. (new) As you said you use havoc os or havoc kernel I think. Which other custom roms have you tried? Is havoc your favourite one? What sort of uses you make with these custom OSs, just normal daily use or something else? Or anything else you wanna share in this manner about your experience, recommendations or anything else.
5. I think I understand a bit, if I use the option 'swipe to allow system modifications' and do not root my device i.e. not flashing magisk which in turn won't disable dm-verity and then if I try to boot to system, it'll go in booloop?
IF I'm right, then what is "read only & root" vs "allow system modifications & root"? Also I have the latest magisk version. What I was trying to say, "When I flashed the 'first' file out of the three 'dfet' files, it flashed magisk 16.7 as well causing latest magisk manager to not work", which I figured out and fixed immediately.
Also when the first time I flashed twrp, only then I got these options. But later on when I flashed the fresh rom through fastboot and then the recovery I simply got booted to the main menu without getting to choose any of these options. During that, I formatted all the stuff like system, internal storage etc. which i wasn't supposed to format, cause of which I had to flash again, but I forgot to select the 'clean all' option instead of 'clean all and lock' option. So i had to unlock again and flash twrp again. But even after all that twrp remebered all the changes I made to it like time, vibration, brightness settings and again it didn't showed any of those two options. More on this in the last response.........
6. And again you gave me the link to miui's official website. I was asking how'd you find all those older roms at one place.
7. So I finally flashed miui rom today, having high hopes, which were proven to be right first then crushed down later. After I flashed the rom, I tested the heck out of it like turning data on/off, usb tethering on/off, no problem occured, didn't found any bugs except one in data usage, it was showing like 100-600gigs(I don't remember exactly) of usage, then it started showing 1300-1400gigs, but after seeing that my confidence dipped down a little.
But still I moved on and flashed twrp on it to get it rooted. After rooting everything was fine even the data usage bug also went away, then I installed gltools and I had my phone connected to pc in usb tethering, suddenly I hear a sound(it restarted<insert gta sa cj meme>) and it starts all over again. I flashed 9.6.14 ver of rom btw.
As you already know from my response above that I was only able to flash through fastboot mode and I wasn't able to get into edl mode as I read just a few hours ago that it's locked away. So my question is, is there a chance that this all could be solved if the rom is flashed through edl. As that's much more of a clean install rather than fastboot, as I mentioned twrp remembered the settings and all that shiz. Or should I just try another ver of miui I have or the custom rom I've downloaded?
Also to get into edl mode, does both of these requirements needed to be met? Or any 1 should work? :-
Authorised account - So who can get this? Is there any bypass or workaround for it?
Test Point - I don't wanna open my phone, as you know it's new & all, tho it's not a problem if there's no other way. It's just that I have some bad memories regarding test point of my beloved RN3(now dead) so I just wanted to stay away from hardware as long as possible. Is there any bypass or a workaround for it?
................................................................................................................................................................................
Gurkirat_Singh said:
@YasuHamed
1. I tested the third file. It worked without any problems even after flashing magisk. Cause it doesn't mess or flash any magisk files, it also detects what sort of root the phone have.
we i am glad , we have a winner here
3. -> 2. I used the same app to check so.
3. You mention some good points there. That's the same reason, things worked out in custom roms and not miui in my earlier experiences. As miui is heavily loaded compared to any custom rom or samsung experinece. I'll try it on other OSs and report back. On the same note, from what I've read that lineage team doesn't release stable builds or at least not anymore. I'm currently downloading pixel experience. Should I go with this one or lineage os? Is it like any other custom OS or heavily loaded like miui? Also what is the difference between PE normal vs plus vs caf? Also I'm gonna try multi rom, as it would be much better for testing.
Temporarily , LOS is suspended but even unofficial roms till mid August are very stable ! you should try! , hoever Pixel is very popular too, on deeper level what diferences you may find thats only user can discover over time. there is no direct answer to this question! LOS is driven from CynogenMod which was on AOSP wehre Pixel is CAF based, so the difference comes on Kernel Level this means CAF rom may have different Hardware performance / behaviour when compare to AOSP based roms (and vice versa). I am not sure about multirom as a daily driver, yes I would like to try for fun but wont keep it.
4. (new) As you said you use havoc os or havoc kernel I think. Which other custom roms have you tried? Is havoc your favourite one? What sort of uses you make with these custom OSs, just normal daily use or something else? Or anything else you wanna share in this manner about your experience, recommendations or anything else.
on Poco i have tried Nitrogen, Omni, MoKee, BootLeggers, CrDroid, LOS and Havoc..
BootLeggers is pretty stable rom! however CrDroid is outstanding because the developer @gwolfu is more active and releases many updates (sometimes 3-4 in a month). Crdroid has serious level of customization (dirtyUnicorn) and you can change the look of your rom in every possible way you imagine!
so the question is WHY am I on Havoc, well the simple answer is both Crdoid and Havoc Offers serious level of DU customization & variations found on deeper level. some items which crdroid doesn't offer i found in Havoc so I stick to it, moreoever I feel the font and resolution by default in havoc is next to pixel where in Crdoid you manualy have to fix (dpi and font)
now I am on havoc2.8 but I am using Optimus Drunk Kernel (which is also used by CRDROID) - the developer of havoc2.8 offers SHADOW kernel which as I said I feel is not very battery effcient (atleast for me, others can disagree)
5. I think I understand a bit, if I use the option 'swipe to allow system modifications' and do not root my device i.e. not flashing magisk which in turn won't disable dm-verity and then if I try to boot to system, it'll go in booloop?
IF I'm right, then what is "read only & root" vs "allow system modifications & root"? Also I have the latest magisk version. What I was trying to say, "When I flashed the 'first' file out of the three 'dfet' files, it flashed magisk 16.7 as well causing latest magisk manager to not work", which I figured out and fixed immediately.
-keeping system Read only OR swipe to allow /system as writable is on Recovery Level ,
- when you keep system on READY ONLY on recovery Level and later flash magisk, the module magisk modify the /system permission which twrp doesn't know!
-if you "allow system modification on twrp level the /system is now set on writable permission by twrp, and magisk is a module which is always set to alter /system partition permission irespective of Global policy on recovery level
Also when the first time I flashed twrp, only then I got these options. But later on when I flashed the fresh rom through fastboot and then the recovery I simply got booted to the main menu without getting to choose any of these options. During that, I formatted all the stuff like system, internal storage etc. which i wasn't supposed to format, cause of which I had to flash again, but I forgot to select the 'clean all' option instead of 'clean all and lock' option. So i had to unlock again and flash twrp again. But even after all that twrp remebered all the changes I made to it like time, vibration, brightness settings and again it didn't showed any of those two options. More on this in the last response.........
now this let me think a little bit, the only possible explaination (in theory) I found is
- when you flash all or clean flash all, its not necessary that /recovery partition is first erased by miflasher! and recovery.img file has many folders including setting folder! so miflasher and later by you simply there was swaping of recoveries, the Tree was always there! when you reflashed twrp! try to do this way
Code:
fastboot erase recovery
fastboot flash twrp.img
this should erase any previous left over data and settings
try and let me know!
6. And again you gave me the link to miui's official website. I was asking how'd you find all those older roms at one place.
i simply google / web search rom number with device name with code name like Miui9.6.20 fastboot download poco f1 beryllium and google suggest few popular results which usually works for me!
7. So I finally flashed miui rom today, having high hopes, which were proven to be right first then crushed down later. After I flashed the rom, I tested the heck out of it like turning data on/off, usb tethering on/off, no problem occured, didn't found any bugs except one in data usage, it was showing like 100-600gigs(I don't remember exactly) of usage, then it started showing 1300-1400gigs, but after seeing that my confidence dipped down a little.
But still I moved on and flashed twrp on it to get it rooted. After rooting everything was fine even the data usage bug also went away, then I installed gltools and I had my phone connected to pc in usb tethering, suddenly I hear a sound(it restarted<insert gta sa cj meme>) and it starts all over again. I flashed 9.6.14 ver of rom btw.
I would say 9.6.14 had bug so reflashing didnt help! as I said before, consider upgrading atleast to 9.6.20
As you already know from my response above that I was only able to flash through fastboot mode and I wasn't able to get into edl mode as I read just a few hours ago that it's locked away. So my question is, is there a chance that this all could be solved if the rom is flashed through edl. As that's much more of a clean install rather than fastboot, as I mentioned twrp remembered the settings and all that shiz. Or should I just try another ver of miui I have or the custom rom I've downloaded?
Also to get into edl mode, does both of these requirements needed to be met? Or any 1 should work? :-
Authorised account - So who can get this? Is there any bypass or workaround for it?
Test Point - I don't wanna open my phone, as you know it's new & all, tho it's not a problem if there's no other way. It's just that I have some bad memories regarding test point of my beloved RN3(now dead) so I just wanted to stay away from hardware as long as possible. Is there any bypass or a workaround for it?
till MiMax
-holding THREE buttons for 30 seconds used to trigger edl mode
-miflasher simply identify EDL mode and used to flash the beryllium fastboot rom
the question is why they stopped?
well fastboot rom when extracted, hackers can simply alter and repack the img files! YOU CAN EVEN place twrp as "recovery.img" in extracted folder miui will flash twrp thinking its vendor recovery! and the device in EDL mode will accept it..
this was serious security risk! so they capped EDL mode in both ends
- miuiflasher needs AUTHORISED ACCOUNT
- DEVICE won't enter in edl mode unless you remove back cover and under batter wire you short two motherboard points with thin wire or tweaser! (and immediately connect usb calbe to system)
now what can you do?
1. use older version of Miflasher which doesnt verify rom
2. user altered rom of specific build or time to WAKE UP your BRICKED device!
I have never done it so you need to investigate and use your poco as gunie pig to test these methods after REMOVING Back Panel (HIGHLY NOT RECOMENDED
or take device to authorised Mi Dealer and let them EDL for you!
Click to expand...
Click to collapse
{
"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.