Hi folks,
As this phone is pretty niche/doesn't have much of a community yet (and may never) I've decided to put a few of my thoughts together in one thread. XDA is my go to for new phones so having an empty device sub makes me sad. None of this may be useful or some of it may be, you tell me.
Purchase:
Bought December 2020. Total cost: €160
This is notable as the market price for these is €400+ SIM Free so this was a bit of a steal for the 765G
Network: Three Ireland, locked
Root?
See bootloader
Bootloader
Is locked down tighter than fort knox. There IS a developer option to allow unlocking but it seems to do nothing. This is common with Alcatel/TCL. Hopefully it's broken, I'm not holding my breath though.
Code:
C:\Users\Administrator>fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
Finished. Total time: 0.008s
Current software?
Code:
Build: QKQ1.200329.002 release-keys
Radio: PAN_GEN_PACK-1.303751.1.304885.8
4.19.81
Patch Level: Aug 2020
Branded splash?
Yes, cannot be removed without root
Quick note on physical build:
Normally I'd always say go on, go bigger. This time I'm finding it a little awkward reaching some stuff. I'm a tall man with reasonably large hands so could get away with anything slightly smaller and reach the whole display. Aspect plays a part here.
The Google button(thank Christ its not Bixby) on the left is super helpful and also super annoying. Find it really easy to accidentally press when holding it in my left hand which is my default.
The power button on the far side is equally easy to press fine. The problem is double press is camera but triple press is EMERGENCY. I do not want emergency. FFS TCL. Seems like no way to disable it.
The gradient on the back is nice but maaaan is it slippy.
Brightness:
Autobrightness is woeful. Like far too aggressive. Blinds you half the time then dimms down to unreadable. Not a fan. Turned it off.
Battery:
The usual chinese affair, kill everything running for more than 6 seconds. Get amazing battery life but prevent apps doing anything useful. Play the usual game of protecting half the apps on your phone and remember to do it with new apps. Problem solved, battery life more normal.
That said the 4500mAh paired with the 765G is pretty sweet.
De-Bloating:
Okay. So we can't root. Sh1t. But all is not lost. ADB gives us some control.
This isnt unique to TCL, sample guide here -> https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
Once you've got an active adb shell:
Code:
pm list packages
That gives us all the installed apps. I'll include that list in post #2
We can "remove" them with the below
Code:
pm uninstall -k --user 0 $package
eg
Code:
pm uninstall -k --user 0 com.ebay.carrier
Here's most or all of what I removed
Code:
com.ebay.carrier
com.amazon.appmanager
ie.three.threeplus
ie.three.my3
com.amazon.mShop.android.shopping
com.tct.smart.account
com.ebay.mobile
com.tct.smart.community
com.facebook.appmanager
com.facebook.system
com.facebook.katana
com.tct.smart.community
com.netflix.mediaclient
com.netflix.partner.activation
com.spectreit.three
com.amazon.avod.thirdpartyclient
com.tcl.usercare
com.facebook.services
com.netflix.partner.activation
com.spectreit.three
com.tcl.usercare
com.tct.smart.notes
I've removed a few at a time in case it causes the system to crash etc. So far so good but do so at your own risk.
Install Youtube Vanced works via normal sideload. IMO really worth doing.
DPI/Scaling:
Defaults to 360
Somewhere around 400-420 is better IMO
Network unlocking:
So far nobody has been able to offer network codes for 272-05 but other networks in the same country are apparently available. Hopefully soon.
More notes, tidbits & complaints as I get them
- Scratchling
Great write-up. One suggestion, maybe try with pm disable first to verify before doing the pm uninstall.
Scratchling said:
Hi folks,
As this phone is pretty niche/doesn't have much of a community yet (and may never) I've decided to put a few of my thoughts together in one thread. XDA is my go to for new phones so having an empty device sub makes me sad. None of this may be useful or some of it may be, you tell me.
Purchase:
Bought December 2020. Total cost: €160
This is notable as the market price for these is €400+ SIM Free so this was a bit of a steal for the 765G
Network: Three Ireland, locked
Root?
See bootloader
Bootloader
Is locked down tighter than fort knox. There IS a developer option to allow unlocking but it seems to do nothing. This is common with Alcatel/TCL. Hopefully it's broken, I'm not holding my breath though.
Code:
C:\Users\Administrator>fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
Finished. Total time: 0.008s
Current software?
Code:
Build: QKQ1.200329.002 release-keys
Radio: PAN_GEN_PACK-1.303751.1.304885.8
4.19.81
Patch Level: Aug 2020
Branded splash?
Yes, cannot be removed without root
Quick note on physical build:
Normally I'd always say go on, go bigger. This time I'm finding it a little awkward reaching some stuff. I'm a tall man with reasonably large hands so could get away with anything slightly smaller and reach the whole display. Aspect plays a part here.
The Google button(thank Christ its not Bixby) on the left is super helpful and also super annoying. Find it really easy to accidentally press when holding it in my left hand which is my default.
The power button on the far side is equally easy to press fine. The problem is double press is camera but triple press is EMERGENCY. I do not want emergency. FFS TCL. Seems like no way to disable it.
The gradient on the back is nice but maaaan is it slippy.
Brightness:
Autobrightness is woeful. Like far too aggressive. Blinds you half the time then dimms down to unreadable. Not a fan. Turned it off.
Battery:
The usual chinese affair, kill everything running for more than 6 seconds. Get amazing battery life but prevent apps doing anything useful. Play the usual game of protecting half the apps on your phone and remember to do it with new apps. Problem solved, battery life more normal.
That said the 4500mAh paired with the 765G is pretty sweet.
De-Bloating:
Okay. So we can't root. Sh1t. But all is not lost. ADB gives us some control.
This isnt unique to TCL, sample guide here -> https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
Once you've got an active adb shell:
Code:
pm list packages
That gives us all the installed apps. I'll include that list in post #2
We can "remove" them with the below
Code:
pm uninstall -k --user 0 $package
eg
Code:
pm uninstall -k --user 0 com.ebay.carrier
Here's most or all of what I removed
Code:
com.ebay.carrier
com.amazon.appmanager
ie.three.threeplus
ie.three.my3
com.amazon.mShop.android.shopping
com.tct.smart.account
com.ebay.mobile
com.tct.smart.community
com.facebook.appmanager
com.facebook.system
com.facebook.katana
com.tct.smart.community
com.netflix.mediaclient
com.netflix.partner.activation
com.spectreit.three
com.amazon.avod.thirdpartyclient
com.tcl.usercare
com.facebook.services
com.netflix.partner.activation
com.spectreit.three
com.tcl.usercare
com.tct.smart.notes
I've removed a few at a time in case it causes the system to crash etc. So far so good but do so at your own risk.
Install Youtube Vanced works via normal sideload. IMO really worth doing.
DPI/Scaling:
Defaults to 360
Somewhere around 400-420 is better IMO
Network unlocking:
So far nobody has been able to offer network codes for 272-05 but other networks in the same country are apparently available. Hopefully soon.
More notes, tidbits & complaints as I get them
- Scratchling
Click to expand...
Click to collapse
have you heard anything about this model getting updates as when i google its just gives the tcl 10 pro will get updated, nothing about the 10 5g...
any info apreciated as im still stuck on may 2020 security patch and no update available, mines unlocked but from 3 uk..
dat7476 said:
have you heard anything about this model getting updates as when i google its just gives the tcl 10 pro will get updated, nothing about the 10 5g...
any info apreciated as im still stuck on may 2020 security patch and no update available, mines unlocked but from 3 uk..
Click to expand...
Click to collapse
I have the TMobile variant and got the security update just yesterday. Hopefully they'll bring Android 11.
I wouldnt hold my breath for much development time put into this one tbh. If we got to Junes 2021 patch level I'd say we're doing well.
Scratchling said:
I wouldnt hold my breath for much development time put into this one tbh. If we got to Junes 2021 patch level I'd say we're doing well.
Click to expand...
Click to collapse
Lol I hear you. I was hoping there would be more development on xda, doesn't seem it's happening though.
great good info about this device,i hope it is available firehose or a method to unlock bootloader
I need ROOT lol firehose anything?
Randomly bought some new wired IEMs. Headphone preamp on this thing is garrrrrbage. Doesnt really matter, but worth noting.
Nice work on this post! There was one part I'm confused about. How did you manage to issue fastboot commands? When I tried adb reboot bootloader, the device would shutdown, flash briefly, and then boot normally.
Eric1084 said:
Nice work on this post! There was one part I'm confused about. How did you manage to issue fastboot commands? When I tried adb reboot bootloader, the device would shutdown, flash briefly, and then boot normally.
Click to expand...
Click to collapse
Either the key combo (power+up or pwr+down) or using ADB worked for me. I had set the "OEM Unlocking" flag in developer options but that probably isnt controlling fastboot IMHO.
Is your build vanilla or branded?
Scratchling said:
Either the key combo (power+up or pwr+down) or using ADB worked for me. I had set the "OEM Unlocking" flag in developer options but that probably isnt controlling fastboot IMHO.
Is your build vanilla or branded?
Click to expand...
Click to collapse
Yeah, I have the rebanded T-Mobile variant. That's probably the cause for the inaccessible fastboot.
pwr+up = recovery, up+down = download, pwr+down = reboot.
Eric1084 said:
Yeah, I have the rebanded T-Mobile variant. That's probably the cause for the inaccessible fastboot.
pwr+up = recovery, up+down = download, pwr+down = reboot.
Click to expand...
Click to collapse
You can enter fastboot from the recovery loader
https://imgur.com/F6GCXV8
Scratchling said:
https://imgur.com/F6GCXV8
Click to expand...
Click to collapse
I can confirm that the Tmobile branded version is locked down and the recovery is stripped down. There is no option to get to adb or fastboot from recovery.
Same here BUT i did find this tool that somehow gets it into "fastbootd" its weired never heard of that.. only "fastboot" but I'm not quite sure what to go from there I tried fast boot oem unlock and a few others and still nothing I'll give the link for the tool that I used it was for a oppo phone cuz I was originally trying anything and everything just to get into fast boot and was trying to find things that had the similar chipset. SOC "SDM765G" I ALSO WAS TRYING TO FIND A FIRE HOSE FOR EDL and I ran across this tool that somehow got me into that mode I will link it soon. Verizon model T790S I will upload a picture of the "fastbootd" also and my recovery is stripped down as well only have the options to format. to restart into bootloader and to power off nothing else .
{
"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"
}
Google is your friend. Secret Tools V1.4 just choose reboot fast boot then click on do job on the bottom right corner of the picture
And also with the phone on you can access adb sideload with "adb reboot sideload "
Metconnect2000 said:
I have the TMobile variant and got the security update just yesterday. Hopefully they'll bring Android 11.
Click to expand...
Click to collapse
Can you run the command to pull the logcat? It will have the download link to the full firmware file. Need to look inside to see if there is a possibility of extracting the boot.img and patching it with magisk.
Related
Hello user space,
A couple days ago I decided to take a chance by building AOSP for my G8342 Dual, the experimentation was quite... let's call it adventurous. It all started by firing up my VM, which I currently use to build, unofficially, LineageOS for my Nexus 5. I'd set a side enough space for the VM to cover the LOS build, not remembering the amount space used I was oblivious. I then jumped on Sony dev site, just to find out the XZ1 had been added to the list of unlockable devices, sweet! I backed up my current XZ1 data not sure whether the bootloader unlock would wipe all data, after sweeping the web for more information, it was confirmed that data would be wiped. I should have known because my N5 did wipe data, which I take is a security measure.
Back on the VM, per Sony's dev site, I made sure the necessary packages were installed which was all of them minus maybe one that wasn't. After all this VM builds for another device so it should be 98% complete. With haste, I 'repo sync'd that bad boi, and 'repo_update'd and on to the 'make -j4'. Little did I know, I had space issues. Remember that space issue up there?^^ It came to haunt me later, like 78% building complete later. :/. #$%^&(* I created a new VM with more space for both N5 builds and Xperia. The build was completed successfully, 3.xx-hrs later.
AOSP was manageable on the N5 with Google proprietary vendor files, etc. But this XZ1 is just blah.. even with the sony binary(4.4). By the way, without the sony binary(fastboot flash oem *.img) the thing will not boot. I flashed an unofficial gapps package from back in Dec. 2017, which I believe is the only functional(per xda) one for Oreo. Needless to say, the gapps package works.
Here are my issues with the AOSP XZ1: Android-8.1.0_r15
-SIM2 is defunct. I selected option 48 from lunch menu. Option 48 was aosp-g8342-userdebug.
-The camera, I know, DRM is sorta still there, with limits :/.
a.) Noise reduction is nowhere to be found even under good light. This camera has a good f-stop.
b.) HDR? It's there but is it actually performing its best work? No.
c.) Camera focus at close range, under a foot? Problematic or mostly nada on screen tap.
-A minor change: screenshot capture is now Volume down + power button. Aosp style!
Non-issues:
-Its plain vanilla, flat as a soda that's been seating out open all day.
-Because I built a userdebug version, root is automagically embedded.
https://source.android.com/setup/building#choose-a-target
Code:
You take on the responsibility of your device. Backup your data because the images will wipe everything.
=============How to flash=============
Get a copy of the latest binary here: software-binaries-for-aosp-oreo-android-8-1-kernel-4-4-yoshino
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash userdata userdata.img
fastboot flash oem SW_binaries_for_Xperia_AOSP_O_MR0_4.4_<release version>_<platform>.img
====================================
===============8.1.0_r20==========================
-Grab a copy of this aosp-g8342_dual-userdebug:
AOSP_Android-8.1.0_r20_G8342_Dual.zip
-Grab a copy of this aosp-g8341_single-userdebug:
AOSP_Android-8.1.0_r20_G8341_Single.zip
===============8.1.0_r20==========================
Here are a few screenshots:
{
"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"
}
perhaps it was a nice story to tell.... have a nice day xda.
Hello. Nice story. I have the single Sim version so I don t know if this will work, but have you had a chance to check the fingerprint sensor? Thanks
Can u build g8341 aosp?
emyjojo said:
Hello. Nice story. I have the single Sim version so I don t know if this will work, but have you had a chance to check the fingerprint sensor? Thanks
Click to expand...
Click to collapse
It will not work with single sim. Yes I have checked the fingerprint even registered two of them. I've attached some pictures for you to see.
dcrin3 said:
It will not work with single sim. Yes I have checked the fingerprint even registered two of them. I've attached some pictures for you to see.
Click to expand...
Click to collapse
That's great news, as it was not working in the previous builds. Would you have the time to build a version for the single SIM model? Would like do give it a shot.
Thank you.
AOSP_Android-8.1.0_r15_G8342_Single
emyjojo said:
That's great news, as it was not working in the previous builds. Would you have the time to build a version for the single SIM model? Would like do give it a shot.
Thank you.
Click to expand...
Click to collapse
You know I just realized that my Dual device is not listed on the Supported devices and functionality page.
The XZ Premium has a dual edition listed but not the XZ1, I wonder why.
Well that makes some sense now.
Code:
Please be aware that I've not tested this package as I do not have the device(You take on the responsibility). Backup your data because the images will wipe everything.
Here is the single version:AOSP_Android-8.1.0_r15_G8341_Single.zip
You let me know if its at least fingerprint and sim1 functional.
see ya.
dcrin3 said:
You know I just realized that my Dual device is not listed on the Supported devices and functionality page.
The XZ Premium has a dual edition listed but not the XZ1, I wonder why.
Well that makes some sense now.
Here is the single version:AOSP_Android-8.1.0_r15_G8342_Single.zip
You let me know if its at least fingerprint and sim1 functional.
see ya.
Click to expand...
Click to collapse
Hi fingerprint is working rom boots fine thank you
yoyoyed said:
Hi fingerprint is working rom boots fine thank you
Click to expand...
Click to collapse
What do you think of its vanilla-ness? its tooo plain no?
dcrin3 said:
What do you think of its vanilla-ness? its tooo plain no?
Click to expand...
Click to collapse
I like it for me perfect can you please support this and keep it updated in the future. Thanks
Hello, It works fine for me as well, but we still need to do the trick with Google Play, in order to get it to work. Will test drive this for a while. Thank you for your efforts.
I have a couple of questions.
1: Does the data activate immediately or does it take several minutes to become active upon booting?
2: Does "OK Google" work from any screen as it does on the stock ROM. (I attempted to run a previous build of AOSP on my 8341 and that feature wouldn't work properly and it drove me insane as i use it all the time.)
3: Is this package a flashable zip or do we have to install each file seperately via fastboot?
Thanks
N1ghtr08d said:
I have a couple of questions.
1: Does the data activate immediately or does it take several minutes to become active upon booting?
2: Does "OK Google" work from any screen as it does on the stock ROM. (I attempted to run a previous build of AOSP on my 8341 and that feature wouldn't work properly and it drove me insane as i use it all the time.)
3: Is this package a flashable zip or do we have to install each file seperately via fastboot?
Thanks
Click to expand...
Click to collapse
Hello,
The data activates immediately upon booting, i do not use google assistant so can't really help about the second point. It is not a flashable zip, you will need to flash each .img via fastboot.
A new thing that I've noticed, the fingerprint sensor is always on, it can unlock the device with the screen turned off.
Hope this helps.
N1ghtr08d said:
I have a couple of questions.
1: Does the data activate immediately or does it take several minutes to become active upon booting?
2: Does "OK Google" work from any screen as it does on the stock ROM. (I attempted to run a previous build of AOSP on my 8341 and that feature wouldn't work properly and it drove me insane as i use it all the time.)
3: Is this package a flashable zip or do we have to install each file seperately via fastboot?
Thanks
Click to expand...
Click to collapse
1 For me data working immidiately
2 ok google only on google app
3 package flash via fastboot
And instal gapps is no issue on this rom works fine
Thanks for the replies. The big issue for me is Google Assistant. If I can't use it from anywhere/with the screen off then it's a no go for me. I'm glad I asked this question before I flashed. Going back to stock is always time consuming.
---------- Post added at 12:08 PM ---------- Previous post was at 12:02 PM ----------
yoyoyed said:
1 For me data working immidiately
2 ok google only on google app
3 package flash via fastboot
And instal gapps is no issue on this rom works fine
Click to expand...
Click to collapse
Could you please try something for me? Delete your trained voice from the Google app then retrain it again but when saying the "ok Google" command, say each of the 3 commands from different distances from the microphone, for example the first really close to the phone, second about 1ft away, 3rd about 2ft away. After its retrained please answer back and let me know if there's any difference please.
I really rely on the Google Assistant so I'm hoping we can fix it somehow.
---------- Post added at 12:12 PM ---------- Previous post was at 12:08 PM ----------
I also found this via search...
I opened the Google App and went to Settings in main menu. Then "'OK Google' detection". Then I disabled all 3 OK Google settings ("Say 'OK Google' any time", "Trusted voice", and "While driving"). Then I re-enabled all 3 and it asked me to retrain by saying "OK Google" 3 times (which is weird because I never explicitly deleted the training data). Then "OK Google" seemed to work fine again after Oreo upgrade.
Could you try that if the first one didn't work?
It seems that it was a false positive with the fingerprint scanner, at least for me. After a Day of usage, it says no fingerprint hardware. It works briefly after a reboot, but it stops.
I figured out a partial fix for Google Assistant not working. The only caveat is that it won't work from a locked screen and unlock the phone, but it works from any screen while the screen is on.
This problem that u have can occur if the Google app is not installed as a system app .
So to fix this ,follow the next few steps -
1) Convert Google app into system app using apps like Titanium backup or anything of your preference. (I found that doing this caused a never ending process and it is fixed by simply going to Titanium Backup so permissions then force stop the app.)
2) Using any root Explorer navigate to Root > system > app and search for an app named similar to 'googlesearchbox' and cut the app from this folder.
3) Now Navigate to Root > system > priv-app and paste the app.
4) Reboot and now the problem will be gone
5) Finally go to the app permissions of the Google app then clear the cache and data then reboot.
The problem should be solved and you should be able to retrain the voice commands.
@yoyoyed
"I like it for me perfect can you please support this and keep it updated in the future. Thanks"
I will certainly entertain the idea. I need to start utilizing twrp backup now that the bootloader is unlocked.
It takes too much time to restore this beast to its working condition.
@emyjojo
"Hello, It works fine for me as well, but we still need to do the trick with Google Play, in order to get it to work. Will test drive this for a while. Thank you for your efforts."
I may have a dirty trick to pull that off. I need to spend more time in the android playground, experimenting. You're welcome @emyjojo
@N1ghtr08d
"2: Does "OK Google" work from any screen as it does on the stock ROM. (I attempted to run a previous build of AOSP on my 8341 and that feature wouldn't work properly and it drove me insane as i use it all the time.)"
That's a low possibility of it happening but along the same experimenting as above ^^^ it may come through. But I'm not promising.
"3: Is this package a flashable zip or do we have to install each file seperately via fastboot?"
That is possible with me spending more time in the playground.
@emyjojo
"It seems that it was a false positive with the fingerprint scanner, at least for me. After a Day of usage, it says no fingerprint hardware. It works briefly after a reboot, but it stops."
After testing out some of the ideas above I will opt to test the phone(AOSP) for a couple days. I want to see how the fingerprint handles on longer usage scenarios.
thank you all for testing it out.
see ya!
dcrin3 said:
@N1ghtr08d
"2: Does "OK Google" work from any screen as it does on the stock ROM. (I attempted to run a previous build of AOSP on my 8341 and that feature wouldn't work properly and it drove me insane as i use it all the time.)"
That's a low possibility of it happening but along the same experimenting as above ^^^ it may come through. But I'm not promising.
Click to expand...
Click to collapse
Bro, look at the post directly above yours. I solved the issue with Google assistant!
@dcrin3
I have a logcat of the fingerprint failure if it will help:
08:42:26.134 V/FingerprintService(952): request stop current client com.android.systemui
03-21 08:42:26.134 W/FingerprintService(952): stopAuthentication: already cancelled!
03-21 08:42:29.137 W/FingerprintService(952): Client com.android.systemui failed to respond to cancel, starting client com.android.systemui
03-21 08:42:29.138 V/FingerprintService(952): starting client AuthenticationClient(com.android.systemui), initiatedByClient = false)
03-21 08:42:29.164 W/FingerprintService(952): startAuthentication failed, result=1
03-21 08:42:29.780 E/KernelUidCpuTimeReader(952): Failed to read uid_cputime: /proc/uid_cputime/show_uid_stat (No such file or directory)
03-21 08:42:32.176 V/FingerprintService(952): stop client com.android.systemui
03-21 08:42:32.179 W/FingerprintService(952): client com.android.systemui is no longer authenticating
03-21 08:42:32.180 V/FingerprintService(952): startAuthentication(com.android.systemui)
03-21 08:42:32.182 V/FingerprintService(952): request stop current client com.android.systemui
03-21 08:42:32.182 W/FingerprintService(952): stopAuthentication: already cancelled!
03-21 08:42:35.185 W/FingerprintService(952): Client com.android.systemui failed to respond to cancel, starting client com.android.systemui
03-21 08:42:35.185 V/FingerprintService(952): starting client AuthenticationClient(com.android.systemui), initiatedByClient = false)
03-21 08:42:35.210 W/FingerprintService(952): startAuthentication failed, result=1
03-21 08:42:42.948 E/KernelUidCpuTimeReader(952): Failed to read uid_cputime: /proc/uid_cputime/show_uid_stat (No such file or directory)
03-21 08:42:48.287 E/KernelUidCpuTimeReader(952): Failed to read uid_cputime: /proc/uid_cputime/show_uid_stat (No such file or directory)
03-21 08:42:50.184 I/PowerManagerService(952): Waking up from sleep (uid=1000 reason=android.policyOWER)...
03-21 08:42:50.211 E/KernelUidCpuTimeReader(952): Failed to read uid_cputime: /proc/uid_cputime/show_uid_stat (No such file or directory)
03-21 08:42:50.218 V/FingerprintService(952): stop client com.android.systemui
03-21 08:42:50.218 I/DisplayPowerController(952): Blocking screen on until initial contents have been drawn.
03-21 08:42:50.220 W/FingerprintService(952): client com.android.systemui is no longer authenticating
03-21 08:42:50.221 V/FingerprintService(952): startAuthentication(com.android.systemui)
03-21 08:42:50.221 V/FingerprintService(952): request stop current client com.android.systemui
03-21 08:42:50.221 W/FingerprintService(952): stopAuthentication: already cancelled
Very good job, nice to see people caring about bringing stock android to the XZ1.
What about treble generic ROMs? Did u try?
Can't wait to have a official treble Ressurection Remix!
Hi guys,
I’m currently facing issue with this phone where I can’t figure out how to turn off the auto answer on this device, please help!
Specs:
Phone Model: Blu g8, running in sc9863a
Rom: stock rom version - blu_G0170_V9.0.04.09_Generic 12-10-2019
Android pie (9)
Kernel version: 4.4.147
Non rooted device with locked bootloader
Here is my 3 month life story on this: I recently bought (in oct) this device from best buy (blu g8) deceived under the brand name blu v9, and brought this back with me to India to use it with local carriers. I have currently Jio and Airtel sims in this as it supports dual sim. The first thing i realize is this device isn’t supported by Jio network as it doesn’t turns on volte by default by the carrier and doesn’t registers this device as a 4g lte supported device. This was my 2 month project to try to figure out to make it work. Eventually after a lot of trial and errors, I found out through shortcut manager lite, there is a setting in gcf (for spreadtrum devices) under the name “gcf volte” upon clicking it, it forces the volte to turn on and then the network started to work for me.
This is where the problem lies, I tinkered soo much with this device beyond engineering mode (as the above setting isn’t visible in the EM app) that for some reason it turned on the auto answer feature via the gcf setting under the name “GCF RF” where all it shows is auto answer is: success.
Possible solutions: after all of this, I realized there was no other way to turn this off as the EM app always shows auto answer as off, turning it on and then off also doesn’t helps as still the phone gets picked up automatically in just one short ring (no bluetooth, no android auto, no special apps to stop or turn it on). I was left with no choice but to factory reset it. I did that, still the same issue. Even after FR on a stock rom, no google updates or even with updated google apps, this problem hasn’t gone till date.
I have also tried to root this device, take backups, tried to restore to another blu stock rom, but was never able to get it to working with any current solutions I researched for. Possibly its the spreadtrum version which none of these android softwares like spd, miracle thunder etc. supports. It always shows me the device drivers as connected but when ai invoke the spd or MT flash tools, it fails to detect the phone when it tries to connect to download the rom. Yes, the phone has authorization for the pc I’m trying to connect with and its a direct usb cable connection as I’m able to access the phone drive and sd card through my window pc. As you can see, I’m not the kind of person who doesn’t do their research and begs online for spoon feeding but in this case I’m leveled to do so. Please help experts, I’m new to Android Dev world.
My Ask: if you’re aware on how to stop the auto answer with above not included as your suggestion, please share. I also didn’t find the stock rom or the supported usb drivers with this current spreadtrum device and the pc software to work with it. I’ll need help with those too, if flashing is your option.
Thanks!
I also tried the “adb shell setprop persist.sys.tel.autoanswer.ms 0” command to set the auto answer off but no luck again
no as conseguido la solucion para el root
MOD Edit:
you have not got the solution for the root
Yes that is correct. I haven't been able to root this phone or unlock the bootloader still. (yes this is still me trying to work this phone).
How ever the auto answer has been resolved. I rest the phone to factory settings and used the Shortcut lite app to go to secrets codes for GCF Activity and turned on LTE setting (ONLY). This helped me turn on VOLTE function on this phone for my local JIO Provider.
HELP WANTED!: Still looking for ways to unlock the boot loader. The below is what I get when trying to use Fastboot commands:
F:\Android\platform-tools>fastboot devices
1070308019001034 fastboot
F:\Android\platform-tools>fastboot oem unlock
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
F:\Android\platform-tools>fastboot flashing unlock
FAILED (remote: 'Not implemet.')
fastboot: error: Command failed
Click to expand...
Click to collapse
thydabiz said:
Yes that is correct. I haven't been able to root this phone or unlock the bootloader still. (yes this is still me trying to work this phone).
How ever the auto answer has been resolved. I rest the phone to factory settings and used the Shortcut lite app to go to secrets codes for GCF Activity and turned on LTE setting (ONLY). This helped me turn on VOLTE function on this phone for my local JIO Provider.
HELP WANTED!: Still looking for ways to unlock the boot loader. The below is what I get when trying to use Fastboot commands:
Click to expand...
Click to collapse
Hello friend. I recently got my phone into a similar situation with auto answer on, and it is really annoying. The auto answer function in Engineering Mode is disabled yet the problem persists. Apparently, I have tracked down the function that enabled the auto answer through the GCF ACTIVITY function, but it doesn't offer any way to disable it. Please help me with what you did to clears the problem in your case.
NOTE: my phone doesn't have the LTE capability so I can't turn it on like you said you did on yours.
Also, I have included two screenshots to give you an idea of the options that enable the problematic auto answer feature.
The first screenshot below outlines the initial gcf.gcfactivity,
The second screenshot shows the resulting menu from the first step above,
The third screenshot shows the aftermath of clicking the GCF RF option from the second screenshot above, which shows a dialog box outlining the features enabled by that final step with auto answer as one of them.
{
"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"
}
Bravo N Justin said:
Hello friend. I recently got my phone into a similar situation with auto answer on, and it is really annoying. The auto answer function in Engineering Mode is disabled yet the problem persists. Apparently, I have tracked down the function that enabled the auto answer through the GCF ACTIVITY function, but it doesn't offer any way to disable it. Please help me with what you did to clears the problem in your case.
NOTE: my phone doesn't have the LTE capability so I can't turn it on like you said you did on yours.
Also, I have included two screenshots to give you an idea of the options that enable the problematic auto answer feature.
The first screenshot below outlines the initial gcf.gcfactivity,
The second screenshot shows the resulting menu from the first step above,
The third screenshot shows the aftermath of clicking the GCF RF option from the second screenshot above, which shows a dialog box outlining the features enabled by that final step with auto answer as one of them.View attachment 5938515View attachment 5938517View attachment 5938519
Click to expand...
Click to collapse
Hi My Friend. Welcome to the painful world of A BLU Phone owner . From all of my lessons learned with this one, the best answer is reset your device and this would go away or if you have a latest version available to install, upgrade the phone. Also, in your 3rd screenshot, the last option enables the volte function and this is what I do always. Goodluck!
thydabiz said:
Hi My Friend. Welcome to the painful world of A BLU Phone owner . From all of my lessons learned with this one, the best answer is reset your device and this would go away or if you have a latest version available to install, upgrade the phone. Also, in your 3rd screenshot, the last option enables the volte function and this is what I do always. Goodluck!
Click to expand...
Click to collapse
Thank you for the prompt reply, buddy. I think I will just reset the damn thing; I hope that is gonna help.
Regards,
BRAVO
Hello!
Before I start, shout out to xda user dany_ev3 for inspiration and his guide which is featured here.
This guide is only meant for ticwatch e, s and pro 2020, and the C series excluding the C2 plus. 3 pro has been updated to include different software.
Before following these steps, please follow https://forum.xda-developers.com/wear-os/development/make-ticwatch-smoother-disabling-t3951734 and then come back here
Your ticwatch comes pre-installed with lots of bloat. This bloat CONSTANTLY runs in the background, making your watch slow and having virtually no battery life. First you will need to disable the ticsystem app. The thing that controls this bloat. See the Link above. (another shout-out to dany_ev3)
Go into your watches settings, scroll to system > about > and tap on build number 10 times. Or until it says 'You are now a developer!'.
Then, make sure you have adb on your PC, I wont cover it here, just google install adb and follow a guide.
One done navigate to C:\adb and then open a command prompt. Then type 'adb shell'
Your in the shell now.
Type:
pm list package | grep 'mobvoi'
and it should give you a list of package names.
Then, type:
pm uninstall -k --user 0 package-name
replacing package-name with the packages they gave you.
DO NOT UNINSTALL SYSTEM OR WATCHFACE. THIS WILL MAKE YOUR SYSTEM UNSTABLE. DON'T ASK ME HOW I KNOW.
After uninstalling, reboot your watch. Now your watch will be faster, smoother and have better battery life.
Again, shout out to dany_ev3 for his amazing guide.
so this didn't work as well for me as it did for you.. I uninstalled the privacy, account, fitness and health packages and rebooted. Now the system is unstable and won't stay on long enough to factory restart or do anything, nor will it boot into recovery. After one reboot it displays the message: "mobvoi/catshark/catshark
9/pwdd.190617.032/5929426
user/release-keys"
and "can't load android system."
What's going on and how do I fix it?
EDIT: Per this thread (https://forum.mobvoi.com/viewtopic.php?t=54561), when it brings up this screen, you can hit the lower button to completely factory reset. Not optimal, but it fixed this issue.
swajsofa said:
so this didn't work as well for me as it did for you.. I uninstalled the privacy, account, fitness and health packages and rebooted. Now the system is unstable and won't stay on long enough to factory restart or do anything, nor will it boot into recovery. After one reboot it displays the message: "mobvoi/catshark/catshark
9/pwdd.190617.032/5929426
user/release-keys"
and "can't load android system."
What's going on and how do I fix it?
EDIT: Per this thread (https://forum.mobvoi.com/viewtopic.php?t=54561), when it brings up this screen, you can hit the lower button to completely factory reset. Not optimal, but it fixed this issue.
Click to expand...
Click to collapse
That's weird. Nothing I would of done wouldn't result in the Android system crashing. Did you disable Mobvoi system? Also, what's your Android and Wearos version. I need to look into this.
BlockArchitech said:
That's weird. Nothing I would of done wouldn't result in the Android system crashing. Did you disable Mobvoi system? Also, what's your Android and Wearos version. I need to look into this.
Click to expand...
Click to collapse
sure; thanks. I had previously disabled the System package as described in the other post you linked to here and it worked fine. It was only after I uninstalled packages via the process you outlined here that the system became unstable. Wear OS 2.17, says the system version is H.
swajsofa said:
sure; thanks. I had previously disabled the System package as described in the other post you linked to here and it worked fine. It was only after I uninstalled packages via the process you outlined here that the system became unstable. Wear OS 2.17, says the system version is H.
Click to expand...
Click to collapse
Sorry for extremely late reply, what watch are you using? Some watches have a different system app that HAS to run in the background for the system to work.
@BlockArchitech
I own a Ticwatch Pro (Not 4G).
I disabled some mobvoi apps thanks to the guides on this forum and the watch now is extra reactive.
You suggest not to uninstall TicSystem and Watchfaces because the watch will become unstable.
Is this true even if the watch is ok with these 2 apps disabled?
I use Google Fit Watchface so I don't need all the others, as an example.
Thanks!
which package do you uninstal? this is my output
Code:
package:com.mobvoi.wear.privacy.aw
package:com.mobvoi.wear.fitness.aw
package:com.mobvoi.wear.account.aw
package:com.mobvoi.wear.appsservice
package:com.mobvoi.wear.health.aw
package:com.mobvoi.ticwatch.cmodel.c2.male
package:com.mobvoi.companion.aw
package:com.mobvoi.wear.watchface.aw
package:com.mobvoi.wear.system.aw
IL_DEMONICO said:
which package do you uninstal? this is my output
Code:
package:com.mobvoi.wear.privacy.aw
package:com.mobvoi.wear.fitness.aw
package:com.mobvoi.wear.account.aw
package:com.mobvoi.wear.appsservice
package:com.mobvoi.wear.health.aw
package:com.mobvoi.ticwatch.cmodel.c2.male
package:com.mobvoi.companion.aw
package:com.mobvoi.wear.watchface.aw
package:com.mobvoi.wear.system.aw
Click to expand...
Click to collapse
Every one of them except for:
package:com.mobvoi.wear.watchface.aw
package:com.mobvoi.wear.system.aw
I uninstalled everything except for the system, watchface and Lauchner.
Is there a second launcher installed? or will I get lost without a lauchner?
Is there an original Google Lauchner like on Android?
OK, i have a Problem, seems ticwatch 3 pro has Other Services that should not get uninstalled.
i did not uninstall watchface. When I wanted to change my watchface, a simple number clock appeared instead, I can no longer select a watchface
spoeckes said:
OK, i have a Problem, seems ticwatch 3 pro has Other Services that should not get uninstalled.
i did not uninstall watchface. When I wanted to change my watchface, a simple number clock appeared instead, I can no longer select a watchface
Click to expand...
Click to collapse
This guide is only meant for ticwatch e, s and pro 2020, 3 pro has been updated to include different software.
Sorry for the confusion
these uninstaled(deleted separately)pm made crash of the wearos system:
com.mobvoi.wear.health.aw
com.mobvoi.wear.watchface.aw
com.mobvoi.wear.appsservice
ticwathpro2020 with customrom from JANJAN
BlockArchitech said:
This guide is only meant for ticwatch e, s and pro 2020, 3 pro has been updated to include different software.
Sorry for the confusion
Click to expand...
Click to collapse
Does this include all the E (E2, E3) series? Or just the original E?
Ticwatch-Pro-4G-USA(Catshark)
witch of these is safe to go?
package:com.mobvoi.wear.privacy.aw
package:com.mobvoi.ticwatch.jupiter.home
package:com.mobvoi.wear.fitness.aw
package:com.mobvoi.wear.sos
package:com.mobvoi.wear.lpa.aw
package:com.mobvoi.wear.mcuservice.aw
package:com.mobvoi.wear.account.aw
package:com.mobvoi.wear.appsservice
package:com.mobvoi.wear.health.aw
package:com.mobvoi.companion.aw
package:com.mobvoi.wear.watchface.aw
package:com.mobvoi.ticwatch.cmodel.pro.modem.us.vzw
Click to expand...
Click to collapse
so far I've disabled
package:com.mobvoi.wear.fitness.aw
package:com.mobvoi.wear.lpa.aw
package:com.mobvoi.wear.account.aw
package:com.mobvoi.wear.health.aw
package:com.mobvoi.companion.aw
Click to expand...
Click to collapse
With no obvious effects
from what I've read on reddit com.mobvoi.wear.mcuservice.aw
provides the essential screen
looks like when I rooted mine com.mobvoi.wear.lpa.aw was already disabled along with com.google.android.wearable.reminders
How to re-install if I need?
htth211101 said:
How to re-install if I need?
Click to expand...
Click to collapse
Factory Reset
a suggestion: unless you really NEED the space on the watch do not UNINSTALL: just DISABLING the apps achieve the same result while also not requiring a whole factory reset to get them back should you disable the wrong one or decide you liked some of them after all.
Just says
C:\1>adb shell
catfish_ext:/ $ pm list package | grep 'mobvoi'
package:com.mobvoi.wear.privacy.aw
package:com.mobvoi.ticwatch.jupiter.home
package:com.mobvoi.wear.fitness.aw
package:com.mobvoi.wear.breath
package:com.mobvoi.wear.mcuservice.aw
package:com.mobvoi.wear.account.aw
package:com.mobvoi.wear.sleep.aw
package:com.mobvoi.wear.appsservice
package:com.mobvoi.wear.heartrate.aw
package:com.mobvoi.wear.health.aw
package:com.mobvoi.wear.recorder
package:com.mobvoi.ticwear.noisedetect
package:com.mobvoi.companion.aw
package:com.mobvoi.wear.watchface.aw
package:com.mobvoi.wear.system.aw
catfish_ext:/ $ pm uninstall -k --user 0 package:com.mobvoi.wear.privacy.aw
Failure [not installed for 0]
1|catfish_ext:/ $ pm uninstall -k --user 0 package:com.mobvoi.wear.fitness.aw
Failure [not installed for 0]
1|catfish_ext:/ $
So if i'm not user 0, what am i?
Thanks to another thread a noticed that i had to remove the package: string.
Worked great and i removed
com.mobvoi.wear.privacy.aw
com.mobvoi.wear.fitness.aw
com.mobvoi.wear.breath
com.mobvoi.wear.sleep.aw
com.mobvoi.wear.heartrate.aw
com.mobvoi.wear.health.aw
com.mobvoi.wear.recorder
and now i'm stuck at this
{
"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"
}
SGT John Doe - i had same. But you can do a factory reset from that screen
spoeckes said:
OK, i have a Problem, seems ticwatch 3 pro has Other Services that should not get uninstalled.
i did not uninstall watchface. When I wanted to change my watchface, a simple number clock appeared instead, I can no longer select a watchface
Click to expand...
Click to collapse
Same here. I am using Ticwatch S2.
Hello! I have an T-mobile version of LG v60. It is permanently unlocked and it has the V600TM20n update. I tried researching on internet about the LG V60 variant, and I couldn't find much information.
Can somebody tell me:
If it is possible to prevent the updates from applying during midnight?
If Android 11 version is still 'root-able'?
If not, is still possible to revert to an older version of Android without losing carrier unlocked status?
My main concern is that these updates will disable my ability to root the phone. Thanks.
Your carrier can disable OTA updates from their end.
Try this.
Or use a package disabler to do it or an adb edit.
Do Not update to 12, it's fubar.
9 or 10 are likely better and more functional.
blackhawk said:
Your carrier can disable OTA updates from their end.
Try this.
Or use a package disabler to do it or an adb edit.
Do Not update to 12, it's fubar.
9 or 10 are likely better and more functional.
Click to expand...
Click to collapse
I just updated my Velvet to 12.It's not terrible from what I have seen.A few changes here and there but nothing spectacular for me to brag about just yet..lol.
surgemanx said:
I just updated my Velvet to 12.It's not terrible from what I have seen.A few changes here and there but nothing spectacular for me to brag about just yet..lol.
Click to expand...
Click to collapse
CPU cycle sucking scoped storage is fully active in 11. Many have reported issues after upgrading to 12 across many unrelated devices. Issues with 3rd party apps including manufacturer system apps seem to be common. Even Pixels aren't exempt
If your phone is running well on Pie or 10 you have very little to gain and a lot to lose in terms of usability and functionality in exchange for questionable "improvements".
blackhawk said:
CPU cycle sucking scoped storage is fully active in 11. Many have reported issues after upgrading to 12 across many unrelated devices. Issues with 3rd party apps including manufacturer system apps seem to be common. Even Pixels aren't exempt
If your phone is running well on Pie or 10 you have very little to gain and a lot to lose in terms of usability and functionality in exchange for questionable "improvements".
Click to expand...
Click to collapse
How can I prevent update to Android 12?
Pioneer22 said:
How can I prevent update to Android 12?
Click to expand...
Click to collapse
You need to disable the update app. Not sure what it's called on LG's.
You can use adb edit or Package Disabler Pro for other devices. PM me if you want that website, it's [email protected]
This what it looks like on my Samsung:
{
"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"
}
I read that if you use adb to remove the FOTA system app (T-Mobile), it will prevent Android updating. If this is true, can I still receive security patches? Are security patches updated separately?
I don't think that works as the updates will be overided by google play services which youll need root so it automatically stops updates for you.
Android 12 was a performance benefit of both android 10 and android 11 of the V60. android 11 on the v60 was smooth but had Vulkan issues, and performance was not great as it suffered lag and slowdowns when gaming. On antutu V8.4.5 android 10 got 559,000 overall score, android 11 got 536,000 overall score, and android 12 got 574,000 overall score. So I would recomend A12 update.
KouaV1 said:
I don't think that works as the updates will be overided by google play services which youll need root so it automatically stops updates for you.
Click to expand...
Click to collapse
You disable the OTA update app by using a package disabler or adb edit. No root needed to end it's reign of tyranny.
blackhawk said:
You disable the OTA update app by using a package disabler or adb edit. No root needed to end it's reign of tyranny.
Click to expand...
Click to collapse
I think that works only on some models of the V60, I have the tmobile v60 and yes I have done adb and yet google play will overide it with the software updates have factory resetted and tried again about 5-10 times no work. which is why i turned to root
KouaV1 said:
I think that works only on some models of the V60, I have the tmobile v60 and yes I have done adb and yet google play will overide it with the software updates have factory resetted and tried again about 5-10 times no work. which is why i turned to root
Click to expand...
Click to collapse
The update app is a dependency of Google play Services probably. It likely has the permissions to turn on Google play Services too.
The update app acts like a rootkit
You need to find the update app(s) and permanently disable them. It may take some work but should be doable. Lol, LG can't be worse than Samsung in this regard.
It will have startup at boot permissions.
You can find it with this:
blackhawk said:
The update app is a dependency of Google play Services probably. It likely has the permissions to turn on Google play Services too.
The update app acts like a rootkit
You need to find the update app(s) and permanently disable them. It may take some work but should be doable. Lol, LG can't be worse than Samsung in this regard.
It will have startup at boot permissions.
You can find it with this:
Click to expand...
Click to collapse
Ah I see, Thank You
I recently got a LM-V600TM on Android 11 and am trying to do my damndest to prevent 12. I don't care about benchmark performance because I don't do mobile gaming. I just don't want to give up control over my phone when LG has a history of putting out half-assed Android updates. It also wasn't cool that 12 removed manual 8K video recording. While it doesn't appear that they broke anything like how Oreo crippled various mods on the V20, I'm not okay with updates that introduce issues and remove features.
Here are the following things I've done so far on my V60:
adb shell pm uninstall -k --user 0 com.lge.android.atservice
adb shell pm uninstall -k --user 0 com.lge.gdec.client
adb shell pm uninstall -k --user 0 com.lge.lgfota.permission
adb shell pm uninstall -k --user 0 com.lge.pickme
Source: https://forum.xda-developers.com/t/v60-bootloader-unlock-and-magisk-root.4358785/post-85909081
adb shell pm uninstall -k --user 0 com.lge.appbox.client
adb shell pm uninstall -k --user 0 com.lge.appbox.installer
adb shell pm uninstall -k --user 0 com.lge.updatecenter
Source: https://forum.xda-developers.com/t/...m-lg-v60-tmobile-or-att.4244333/post-84875105
Some additional info on what apps to disable and what behavior to look out for is here:
https://www.reddit.com/r/LGV60/comments/rqwwlo/_/hqd9kjk
All of the above should effectively disable OTA updates, but Google Play services will still find a way to annoy the hell out of you every two days. The following system lightbox dialog supposedly comes from Google Play services:
----------
Install update to keep device running smoothly
Your system is [X] days out of date.
[Link] Learn more
[Option] Install Now
[Option] Remind me later
----------
I was frustrated to discover it was possible to get almost all the way there without rooting only to find that removing the dialog is the part that requires root.
Source: https://forum.xda-developers.com/t/how-do-i-stop-update-notices.4171467/post-84529465
The only thing I really needed root for in recent years was system-wide ad blocking, and I have that taken care of now with Blokada 5 and an archive of the last version of Vanced, but it looks like I'll get sucked back into the rooting endeavor at least one more time just to get rid of this system update dialog.
Rooting phones felt kind of cool years ago when it was a novel thing to do and doing so actually opened up lots of customization options. Now it just feels like a chore.
To follow-up my own post:
Because there is currently no T-Mobile Android 12 KDZ (only US Cellular and unlocked Canada) for the V600TM and upgrading to 12 doesn't trip some kind of anti-rollback mechanism like firmware updates did on previous LG phones, I considered letting 12 install itself. The system lightbox nag dialog was too annoying for me.
After reviewing the changes in the LG Android 12 package, I had concluded that it wasn't crippling to the V60 other than dropping the manual 8K recording, which I'm not a fan of removing, but I also don't use. I figured that I have a T-Mobile Android 11 20n KDZ that I could always use for rooting later. However, once I decided to let the 12 update proceed, it kept erroring out and failing no matter what I did.
I tried one last time to root the phone on Android 11 20n and finally succeeded on Windows 10. Previously, QFIL failed on port comms on both of my Windows 7 machines. Anyway, I'm glad this nightmare is done. Just for how bad the initial rooting experience was on this phone, I'm not particularly pleased with it at the moment. Maybe it will slowly win me over if I never get that damn nag screen again after following the instructions in this link:
https://forum.xda-developers.com/t/how-do-i-stop-update-notices.4171467/post-84529465
I'm beginning to realize that I'm probably not going to keep this phone for very long compared to my two V20s. I've used the V20 for nearly 5 years now. I might get 2-3 out of this V60 before I go with a used Sony Xperia 1 IV or a future Xperia 5 if it ever gets good T-Mobile 5G band support. I want something without carrier bloat, has good community support (which this phone has virtually none), and is far more friendly to bootloader unlocking and rooting, but doesn't strip away the ports and external storage like just about every damn phone out there does now.
In case anyone would find it helpful, to revert the disabled app changes I made to my V60 in the previous post, I used the following command for all 7 of the apps I had uninstalled for user 0:
adb shell cmd package install-existing <package_name>
Source: https://android.stackexchange.com/q...l-an-accidentally-uninstalled-app-through-adb
I just received a NUU A5X/N5501LAT from Abbott. Interesting little device; I haven't seen a self-proclaimed "PDA" since the iPAQ days. It's running Android 9 on either a MT6739 or a MT8765, according to the FCC teardown photos.
Either way, it's severely locked down. The notification shade automatically wipes away, developer mode is blocked, most settings are restricted, and the launcher literally only allows four apps: Nuu App Store (which, coincidentally, only has two other apps in it), the AOSP Browser, the Abott Frestyle app that the device is meant to be used for, and Firefox.
It will take a MicroSD (and, entertainingly, has a micro-SIM slot despite not being a phone), and has a micro-USB port as well. I can't find a fastboot combination using its volume and power keys.
I'd love some thoughts on how to make this thing into a generic PDA without all the restrictions. I'm stuck without access to ADB at this point due to the developer settings being blocked, and I'm honestly at a bit of a loss as to where to go next. Thanks for your input!
Hi, I have the identical gadget; the NUU A5X, that is. Mine can't be made to change its boot sequence by holding down buttons, either, it seems. Mine is locked indentically I believe.
Mine responds to USB connection, but It does not seem useful.
I think It mighr be possible to connect to it via NFC or bluetooth, but I know far too little about those protocols, other than TCP/IP, if that runs on blueooth, then that might work. I might try make a grid of procedures to test all buttons
databoy2k said:
I just received a NUU A5X/N5501LAT from Abbott. Interesting little device; I haven't seen a self-proclaimed "PDA" since the iPAQ days. It's running Android 9 on either a MT6739 or a MT8765, according to the FCC teardown photos.
Either way, it's severely locked down. The notification shade automatically wipes away, developer mode is blocked, most settings are restricted, and the launcher literally only allows four apps: Nuu App Store (which, coincidentally, only has two other apps in it), the AOSP Browser, the Abott Frestyle app that the device is meant to be used for, and Firefox.
It will take a MicroSD (and, entertainingly, has a micro-SIM slot despite not being a phone), and has a micro-USB port as well. I can't find a fastboot combination using its volume and power keys.
I'd love some thoughts on how to make this thing into a generic PDA without all the restrictions. I'm stuck without access to ADB at this point due to the developer settings being blocked, and I'm honestly at a bit of a loss as to where to go next. Thanks for your input!
Click to expand...
Click to collapse
I think you could write and compile an executable to put the nuu service to sleep, or to withdraw its privileges, or to ovet-ride it. Unfortunately, I never got my development environment for Android set up.
I might be able to write a small utility in C,
even if it only makes a system() call. it might do the job. I have found that Firefox can download an arbitrary file. The executable would call an Intent, to do some job or other to "pull the plug".
I am looking to see what the possibilities are.
/Dave
I am interested as well in a solution
+1
I'm trying somethiing. It will take time. Don't hold your breath
I found out if you click idk how much times on the nu sogen in the Home Screen then you need to enter a password bud i don’t know the pasword
hi people, the same here, anyone have found something to make this brick useful ?
+1 to this
Acording to NUU Mobile Support, this phone can't booted into recovery mode, or be flashed.....
This phone is made to be used to track blood pressures in hospitals. I haven't tried to flash it yet, but I will
meme problématiques un genie ce cache parmis vous pour resoudre ce probleme???
Mod translation via GT: even problems a genius this hides among you to solve this problem???
Just been given one of these.
As already said holding the power and down or up buttons or all 3 has no effect.
and you cant click about phone 9 times to enable debugging mode for ADB access. which would be handy.
I can bluetooth files from one phone to it. but it doesnt know what to do with them. I put a sim card in, but there is no app to make phone calls.
The default browser does have permission to access system files, but I have no idea how to tell it to do so. Cant even get the camera to work. ah well maybe I should just use it to read my blood sugar levels. I guess I could buy a sensor to hammer into my arm hehh hehh
Same here, tried everything i could but no change.
If you download a file with their built-in browser that it can't open it will open up the file manager where I got some log files
Appearently serial over USB is enabled at some point during the boot process (?)
Use this tool: https://github.com/bkerler/mtkclient
And do: mtk meta FASTBOOT, then follow the instructions shown and finally do fastboot flashing unlock to perform an unlock
It will give you a message basically like:
if you do this, warranty will be void and a factory reset will be done. Press Volume up to continue.
Disclaimer: I haven't tested it to the end (shut it off instead of pressing volume up) since I want to do some more exploring with my currently installed toolset so I can find out more
tuxifan said:
Use this tool: https://github.com/bkerler/mtkclient
And do: mtk meta FASTBOOT, then follow the instructions shown and finally do fastboot flashing unlock to perform an unlock
It will give you a message basically like:
if you do this, warranty will be void and a factory reset will be done. Press Volume up to continue.
Disclaimer: I haven't tested it to the end (shut it off instead of pressing volume up) since I want to do some more exploring with my currently installed toolset so I can find out more
Click to expand...
Click to collapse
I tried it today, the result is weird, as MTKClient seems to react to the phone off, but not the ADB command that staying in the wait of any devices.
Also, the phone still can show battery status in that state? Normal?
It looks like it get in, then out of the FASTBOOT
Nuu Service is an extra launcher that opens and overlays when you start your smartphone. The default system launcher is Quickstep and you can change the launcher. However, the change is suppressed and immediately reversed. A reset is also blocked in the system. The standard browser is authorized to make changes to the system. There is definitely a weak point.
How can I execute key codes such as +#06#? I can't find the caller keypad.
You can also enter "secret codes" via a detour.
Open the standard browser, enter a bar/restaurant in google search, press call. The call keypad opens. I've already tested a few codes.
*#*#1111#*#* Hardwareversion
*#*#4636#*#* Display information Wifi, Phone-Info, Userstats
*#*#225#*#* Calendar Storage
Edit:
*#*#3646633#*#* Code for Engenering Mode - I get a message that developer mode is locked.
Just for fun I made a packet recording with the Fritzbox and looked at it with Wireshark. The device pings several servers in Germany, Finland and the USA.
The apps are actually online downloads. I did not expect.
I took a closer look at the ip's and found that "Sure Lock" runs on the device as a kiosk app. This can be configured as the customer wants. So Abbott/NUU.
If you type very quickly and often in succession on the home screen, a password input field will appear after a while.
If you had a password now...
Sure Lock's standard password (0000) obviously doesn't work
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi,
I found something interesting on this device. Indeed I can have access to notifications and in particular to NUU service, which when I keep pressing it appears a small i button, which allows access to the parameters of this application.
Obviously everything is blocked on it except in the advanced settings it's possible to deactivate the overlay to other apps and the possibility of modifying the system parameters.
After turning everything off and restarting the phone, I arrive not on the launcher but on the classic version of Android 9, which lasts a few seconds before glitching on the famous launcher.
I tried to exploit these few seconds at best but without success, I remain stuck on the lock screen.
Have you tried this generic bootloader-unlocking method?
GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) - GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
github.com