[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE][SIZE=+2]Specific to[/SIZE]
{
"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"
}
Xiaomi Mi Max
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button , in lieu of simply posting "Thank you".
Please keep discussion focused, on questions pertaining to this Device
List of supporters@Vatsal
...
...To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.
If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you!
Supporters: If you want to be put on or off the list, just make a request here in the thread!
Before posting anything, I strongly advise you to read
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
FAQs for Device Thread link
Please look for a similar [HELP THREAD] when visiting another device forum.
If you would like to create a similar [Help Thread] please Click Here.
CyanogenMod 14.1http://forum.xda-developers.com/mi-max/development/hydrogen-cyanogenmod-14-t3503822
[GUIDE]ROOT/TWRP/MULTIROM/Cm13/RR on Locked Bootloader + Hardbrick Recoveryhttp://forum.xda-developers.com/mi-max/how-to/guide-install-global-miui8-root-t3435594
Telegram Invite Linkhttps://telegram.me/joinchat/B6at4UAb_dESnykJ_3PB6g
Thread stuck.
Thank you for this
I'm glad that this thread is up. It's quite timely as I had two quick questions.
After around 5 hours with the device, I was able to do the following:
Unlock the bootloader using the official unlocker.
Format System and Userdata Partitions using Fastboot
Flash TWRP using Fastboot
Mount MTP within TWRP
Copy latest Recovery Image (Stable Global) and SuperSU to Internal Storage
Flash latest Recovery Image (Stable Global) using TWRP
Flash SuperSU 2.78 using TWRP
Everything works as I want it to be right now. It was rather hard since the information was very limited and I haven't seen a detailed guide on how to do this.
If I have time, I'll try to do a short guide. I read a lot of posts in other forums that this was not possible without using a custom ROM which was not the case.
Nonetheless, two questions are coming to mind.
How can I update my ROM if a new version comes out without losing root?
Is Xposed available and if so, where do I download it and how do I flash it?
Thanks!
oreo27 said:
I'm glad that this thread is up. It's quite timely as I had two quick questions.
After around 5 hours with the device, I was able to do the following:
Unlock the bootloader using the official unlocker.
Format System and Userdata Partitions using Fastboot
Flash TWRP using Fastboot
Mount MTP within TWRP
Copy latest Recovery Image (Stable Global) and SuperSU to Internal Storage
Flash latest Recovery Image (Stable Global) using TWRP
Flash SuperSU 2.78 using TWRP
Everything works as I want it to be right now. It was rather hard since the information was very limited and I haven't seen a detailed guide on how to do this.
If I have time, I'll try to do a short guide. I read a lot of posts in other forums that this was not possible without using a custom ROM which was not the case.
Nonetheless, two questions are coming to mind.
How can I update my ROM if a new version comes out without losing root?
Is Xposed available and if so, where do I download it and how do I flash it?
Thanks!
Click to expand...
Click to collapse
1.You have done it already... Do the same steps from Copy..., Flash..., Flash...
2.Install this Xposed Installer and within you have option to install miui xposed framework
http://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
nijel8 said:
1.You have done it already... Do the same steps from Copy..., Flash..., Flash...
2.Install this Xposed Installer and within you have option to install miui xposed framework
http://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
Click to expand...
Click to collapse
Alright. So I don't have to format the filesystem the next time I install an update?
Thanks. Installing that now.
CM14.1
So I just ordered this set. Primary goal was ofcourse to watch anime, secondary goal being psp emulation.
I was quite surprised I cannot disable any of the core system apps unlike my karbonn titanium where disabling google stuff made the 2000mah battery last 3 days in 2g mode without wifi easily.
I think the only way to remove the gapps would be to flash a custom rom at this point, being the CM14.1 with nougat. So my question is, the guide mentions installing the gapps after nougat, I want to know if I can skip it? The main guide doesn't mention anything about skipping it, would like to know what would happen.
Hi guys, Just added a Telegram invite link to the 2nd post.
It will help in making the community grow. Also you can help the developers to test ROMs/Kernels.
nonoganosus said:
So I just ordered this set. Primary goal was ofcourse to watch anime, secondary goal being psp emulation.
I was quite surprised I cannot disable any of the core system apps unlike my karbonn titanium where disabling google stuff made the 2000mah battery last 3 days in 2g mode without wifi easily.
I think the only way to remove the gapps would be to flash a custom rom at this point, being the CM14.1 with nougat. So my question is, the guide mentions installing the gapps after nougat, I want to know if I can skip it? The main guide doesn't mention anything about skipping it, would like to know what would happen.
Click to expand...
Click to collapse
I think skipping it won't prevent the device from functioning correctly. However, you won't have access to Google's services including the Play Store if I'm not mistaken.
---------- Post added at 09:52 AM ---------- Previous post was at 09:37 AM ----------
nijel8 said:
1.You have done it already... Do the same steps from Copy..., Flash..., Flash...
2.Install this Xposed Installer and within you have option to install miui xposed framework
http://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
Click to expand...
Click to collapse
Xposed installer worked great mate! Thanks.
So all I have to do is to flash the new ROM using the update(ZIP) package. Then flash SuperSU again? I'll probably have to re-install Xposed/Busybox too right?
Also, if the update is available and I flash an update ZIP from within TWRP, won't it overwrite userdata? I'm not sure but I think that zip contains some of these: (I have zero idea what these are) :highfive:
Code:
Line 206: /data(/.*)? u:object_r:system_data_file:s0
Line 207: /data/.layout_version u:object_r:install_data_file:s0
Line 208: /data/unencrypted(/.*)? u:object_r:unencrypted_data_file:s0
Line 209: /data/backup(/.*)? u:object_r:backup_data_file:s0
Line 210: /data/secure/backup(/.*)? u:object_r:backup_data_file:s0
Line 211: /data/security(/.*)? u:object_r:security_file:s0
Line 212: /data/system/ndebugsocket u:object_r:system_ndebug_socket:s0
Line 213: /data/drm(/.*)? u:object_r:drm_data_file:s0
Line 214: /data/gps(/.*)? u:object_r:gps_data_file:s0
Line 215: /data/resource-cache(/.*)? u:object_r:resourcecache_data_file:s0
Line 216: /data/dalvik-cache(/.*)? u:object_r:dalvikcache_data_file:s0
Line 217: /data/dalvik-cache/profiles(/.*)? u:object_r:dalvikcache_profiles_data_file:s0
Line 218: /data/adb(/.*)? u:object_r:adb_data_file:s0
Line 219: /data/anr(/.*)? u:object_r:anr_data_file:s0
Line 220: /data/app(/.*)? u:object_r:apk_data_file:s0
Line 221: /data/app/[^/]+/oat(/.*)? u:object_r:dalvikcache_data_file:s0
Line 222: /data/app/vmdl[^/]+\.tmp(/.*)? u:object_r:apk_tmp_file:s0
Line 223: /data/app/vmdl[^/]+\.tmp/oat(/.*)? u:object_r:dalvikcache_data_file:s0
Line 224: /data/app-private(/.*)? u:object_r:apk_private_data_file:s0
Line 225: /data/app-private/vmdl.*\.tmp(/.*)? u:object_r:apk_private_tmp_file:s0
Line 226: /data/tombstones(/.*)? u:object_r:tombstone_data_file:s0
Line 227: /data/local/tmp(/.*)? u:object_r:shell_data_file:s0
Line 228: /data/media(/.*)? u:object_r:media_rw_data_file:s0
Line 229: /data/mediadrm(/.*)? u:object_r:media_data_file:s0
Line 230: /data/property(/.*)? u:object_r:property_data_file:s0
Line 233: /data/misc/adb(/.*)? u:object_r:adb_keys_file:s0
Line 234: /data/misc/audio(/.*)? u:object_r:audio_data_file:s0
Line 235: /data/misc/bluetooth(/.*)? u:object_r:bluetooth_data_file:s0
Line 236: /data/misc/bluedroid(/.*)? u:object_r:bluetooth_data_file:s0
Line 237: /data/misc/bluedroid/\.a2dp_ctrl u:object_r:bluetooth_socket:s0
Line 238: /data/misc/bluedroid/\.a2dp_data u:object_r:bluetooth_socket:s0
Line 239: /data/misc/camera(/.*)? u:object_r:camera_data_file:s0
Line 240: /data/misc/dhcp(/.*)? u:object_r:dhcp_data_file:s0
Line 241: /data/misc/gatekeeper(/.*)? u:object_r:gatekeeper_data_file:s0
Line 242: /data/misc/keychain(/.*)? u:object_r:keychain_data_file:s0
Line 243: /data/misc/keystore(/.*)? u:object_r:keystore_data_file:s0
Line 244: /data/misc/logd(/.*)? u:object_r:misc_logd_file:s0
Line 245: /data/misc/media(/.*)? u:object_r:media_data_file:s0
Line 246: /data/misc/net(/.*)? u:object_r:net_data_file:s0
Line 247: /data/misc/shared_relro(/.*)? u:object_r:shared_relro_file:s0
Line 248: /data/misc/sms(/.*)? u:object_r:radio_data_file:s0
Line 249: /data/misc/systemkeys(/.*)? u:object_r:systemkeys_data_file:s0
Line 250: /data/misc/user(/.*)? u:object_r:misc_user_data_file:s0
Line 251: /data/misc/vpn(/.*)? u:object_r:vpn_data_file:s0
Line 252: /data/misc/wifi(/.*)? u:object_r:wifi_data_file:s0
Line 253: /data/misc/wifi/sockets(/.*)? u:object_r:wpa_socket:s0
Line 254: /data/misc/wifi/sockets/wpa_ctrl.* u:object_r:system_wpa_socket:s0
Line 255: /data/misc/wifi/hostapd(/.*)? u:object_r:wpa_socket:s0
Line 256: /data/misc/zoneinfo(/.*)? u:object_r:zoneinfo_data_file:s0
Line 257: /data/misc/vold(/.*)? u:object_r:vold_data_file:s0
Line 258: /data/misc/perfprofd(/.*)? u:object_r:perfprofd_data_file:s0
Line 259: /data/system/heapdump(/.*)? u:object_r:heapdump_data_file:s0
Line 262: /data/system/users/[0-9]+/fpdata(/.*)? u:object_r:fingerprintd_data_file:s0
Line 265: /data/bootchart(/.*)? u:object_r:bootchart_data_file:s0
Line 284: /data/system/users/[0-9]+/wallpaper u:object_r:wallpaper_file:s0
Line 312: /data/app-asec(/.*)? u:object_r:asec_image_file:s0
Line 326: /data/fpc(/.*)? u:object_r:fpc_data_file:s0
Line 330: # /data/extend_size.userdata
Line 331: /data/extend_size.userdata u:object_r:cache_file:s0
Line 613: /data/connectivity(/.*)? u:object_r:cnd_data_file:s0
Line 614: /data/data_test(/.*)? u:object_r:data_test_data_file:s0
Line 614: /data/data_test(/.*)? u:object_r:data_test_data_file:s0
Line 615: /data/diag_log(/.*)? u:object_r:diag_data_file:s0
Line 616: /data/misc/sensors(/.*)? u:object_r:sensors_data_file:s0
Line 617: /data/rfs.* u:object_r:rfs_file:s0
Line 618: /data/hlos_rfs(/.*)? u:object_r:rfs_shared_hlos_file:s0
Line 619: /data/camera(/.*)? u:object_r:camera_socket:s0
Line 620: /data/misc/stargate(/.*)? u:object_r:qfp-daemon_data_file:s0
Line 621: /data/system/sensors(/.*)? u:object_r:sensors_data_file:s0
Line 622: /data/time(/.*)? u:object_r:time_data_file:s0
Line 623: /data/nfc(/.*)? u:object_r:nfc_data_file:s0
Line 624: /data/system/perfd(/.*)? u:object_r:mpctl_data_file:s0
Line 625: /data/misc/iop(/.*)? u:object_r:iop_data_file:s0
Line 626: /data/misc/iop/iop u:object_r:iop_socket:s0
Line 627: /data/misc/display(/.*)? u:object_r:display_misc_file:s0
Line 628: /data/misc/ipa(/.*)? u:object_r:ipacm_data_file:s0
Line 629: /data/dpm(/.*)? u:object_r:dpmd_data_file:s0
Line 630: /data/misc/qsee(/.*)? u:object_r:data_qsee_file:s0
Line 631: /data/misc/location(/.*)? u:object_r:location_data_file:s0
Line 632: /data/misc/location/mq/location-mq-s u:object_r:location_socket:s0
Line 633: /data/misc/location/mq/alarm_svc u:object_r:location_socket:s0
Line 634: /data/FTM_AP(/.*)? u:object_r:mmi_data_file:s0
Line 635: /data/misc/hbtp(/.*)? u:object_r:hbtp_log_file:s0
Line 636: /data/misc/qlogd(/.*)? u:object_r:qlogd_data_file:s0
Line 637: /data/usf(/.*)? u:object_r:usf_data_file:s0
Line 638: /data/misc/dts(/.*)? u:object_r:dts_data_file:s0
Line 639: /data/misc/seemp(/.*)? u:object_r:seemp_file:s0
Line 640: /data/misc/SelfHost(/.*)? u:object_r:RIDL_data_file:s0
Line 641: /data/misc/qti-logkit(/.*)? u:object_r:qti_logkit_priv_data_file:s0
Line 642: /data/misc/qti-logkit/shared-public(/.*)? u:object_r:qti_logkit_pub_data_file:s0
Line 643: /data/misc/qti-logkit/logdata(/.*)? u:object_r:qti_logkit_pub_data_file:s0
Line 644: /data/misc/radio(/.*)? u:object_r:radio_data_file:s0
Line 645: /data/misc/port_bridge(/.*)? u:object_r:port_bridge_data_file:s0
Line 646: /data/misc/fm(/.*)? u:object_r:fm_data_file:s0
Line 647: /data/misc/audio_pp(/.*)? u:object_r:audio_pp_data_file:s0
Line 648: /data/ramdump(/.*)? u:object_r:ssr_ramdump_data_file:s0
Line 649: /data/misc/SelfHost/socket(/.*)? u:object_r:RIDL_socket:s0
Line 650: /data/misc/qti-logkit/socket-privileged(/.*)? u:object_r:qti_logkit_priv_socket:s0
Line 651: /data/fpc/s(/.*)? u:object_r:fpc_stat_data_file:s0
Line 652: /data/misc/qti-logkit/socket-public(/.*)? u:object_r:qti_logkit_pub_socket:s0
Line 660: /persist/data(/.*)? u:object_r:persist_drm_file:s0
Line 661: /persist/data/tz(/.*)? u:object_r:persist_drm_file:s0
Line 662: /persist/data/sfs(/.*)? u:object_r:persist_drm_file:s0
Line 816: /data/display-tests/media(/.*)? u:object_r:display_test_media_file:s0
Line 837: /data/system/mcd(/.*)? u:object_r:mcd_data_file:s0
Line 842: /data/system/nativedebug(/.*)? u:object_r:miui_native_file:s0
Line 843: /data/system/nativedebug/core(/.*)? u:object_r:miui_coredump_file:s0
Line 848: /data/system/theme(/.*)? u:object_r:theme_data_file:s0
Line 849: /data/system/theme_magic(/.*)? u:object_r:theme_data_file:s0
Line 863: /data/user/1[0-9]+/.* u:object_r:app_data_file:s0
Line 864: /data/user/1[0-9]+/com.android.providers.downloads/cache u:object_r:download_file:s0
Line 871: /data/system/users/[0-9]+/.Spaces(/.*)? u:object_r:securespaces_file:s0
oreo27 said:
I think skipping it won't prevent the device from functioning correctly. However, you won't have access to Google's services including the Play Store if I'm not mistaken.
Click to expand...
Click to collapse
Think... not good enough Would help to know if someone is sure. I'm actually puzzled its not given in the FAQ like "Can I skip GAPPS zip install after nougat rom").
Also really wish I could post on that main CM14.1 thread. Would like to have some before after benchmarks.
Hi Guys,quick one from me.Can the 'dual apps' feature be used for many apps at same time?Like viber,line,whatsapp etc?
Has anyone had scratches on this device? I scratched the top part (metal, I think) of mine and I was wondering if it's possible to remove it like how one would remove light scratches on a car using a buffing tool?
my charger makes sound slight soundwhen charging. is it normal?
shaun95 said:
my charger makes sound slight soundwhen charging. is it normal?
Click to expand...
Click to collapse
Had this in another device. I've read somewhere that this is perfectly normal. It scared me the first time I heard it too.
oreo27 said:
Has anyone had scratches on this device? I scratched the top part (metal, I think) of mine and I was wondering if it's possible to remove it like how one would remove light scratches on a car using a buffing tool?
Click to expand...
Click to collapse
If you're talking about the very top of the phone then its definitely plastic. Both the top and bottom sections of the rear cover are plastic caps. Only the middle section is metal. If the scratch is at the top of the middle section you might be able to buff it out, but I guess you'd run the risk of making a larger mark. Good luck!
RAMBO29 said:
Hi Guys,quick one from me.Can the 'dual apps' feature be used for many apps at same time?Like viber,line,whatsapp etc?
Click to expand...
Click to collapse
I think so, although I haven't tried it myself. On my device it recommends WhatsApp, Facebook, and Facebook Messenger. Plus, it lists all my other installs below, so I think you should be able to clone just about anything
Enable Softkeys on Navbar
Hi Folks. Has anyone been able to enable the Navbar on this device. I've tried the following to no avail:
GravityBox
SoftKey Enabler APK
qemu.hw.mainkeys=0
Is that Mi Max has different some hardware variant too between old batch and new batch?, like redmi note 3 that has two different FP sensor (goodix and fpc1020), has different front and back camera, also has different display, this cause some of a loot custom rom still doesn't support one of that hardware variant.
I'm interested in buying the Xiaomi Mi Max. But before I do I got some questions:
1) Is it compatible with T-mobile USA on their 4G LTE?
2) Can you install Marshmallow on it?
3) Is the phone easily bendable making it not structurally sound?
4) I saw a review that said that the video recording was jumpy and not stable. If this is true, is there a fix to this?
5) What are any problems with it you dont like?
6) Which is better, this phone or the Doogee Y6 Max?
7) Do you recommend this phone?
nonoganosus said:
Think... not good enough Would help to know if someone is sure. I'm actually puzzled its not given in the FAQ like "Can I skip GAPPS zip install after nougat rom").
Also really wish I could post on that main CM14.1 thread. Would like to have some before after benchmarks.
Click to expand...
Click to collapse
Hi, first of all thx @Vatsal for this thread, on my understanding you perfectly can skip to flash GAPPs cause no included in any nougat rom for mi max, but some apps need Play Services to work correctly, other you can freeze them with greenify or doze or other.
If you update from same version rom don't erase any data, of course yes all you flashed by recovery (mods, supersu) and you must reflash again and before reboot recommend for best performance.
I'm on last version 8.1.4.0 and my method to update is after download zip delete file emmc_appsboot_mnc from romzip/update-firmware to avoid replace recovery or relock bootloader.
Related
Just learned about GIS. Still using a Galaxy S4 w/Lineage, but am a huge fan of eink everything and impulse pre-ordered this new black and white phone from new and unknown Chinese vendor. Alleged to ship in August.
Assumed I was just going to use it off line as an ebook reader (to replace my kobo mini), but GIS has given me hope that there is a chance for a (relatively) safe/unbloated life for this device beyond that.
I’m sure there will be some eink optimization in the official ROM, but am less concerned about that than I am mysterious Chinese software.
Would love to hear anyone’s thoughts. I am more than happy to contribute to the cost of a Getting a test device in capable hands if necessary.
As a privacy enthusiast would also appreciate thoughts on hardware security on random Chinese phone as well. This is the first time I’ve ever gone out on such a limb.
Kingrow K1 Specs
5.17-inch E Ink Carta display (1280 x 720 with 283 ppi).
Frontlight.
2.0GHz MediaTek Helio P23 (MT6763) octa-core processor.
16GB of storage space.
2GB of RAM.
MicroSD card slot with support up to 64GB.
3100 mAh battery.
8MP rear camera with LED flash and auto-focus.
Android 8.1 Oreo operating system.
Dual SIM.
USB-C port.
Dual speakers.
138 x 72 x 8.5mm.
Thanks in advance.
Just realized one particular hardware issue may be the front light (since screen is not backlit like an LCD) and the controls may not be identical to backlight controls. I hope it treats the screen brightness identically and that it won’t be an issue.
Bump. For this type of preocessor I’ve only seen one example of getting stock android running relatively easily, anybody have any insight on what I can expect in the attempt?
I waited with backing this project on Indiegogo, because of the lack of GMS. I hope that could be fixed through another rom. But I doubt there will be a big developer crowd for this device. Nevertheless its nice to see it here on XDA. Followed!
Hi, I just got my Kingrow K1 in the mail today. I've always wanted an e-ink smartphone for longer battery life + less distraction, so I'm pretty excited about this. Unfortunately, the preinstalled software looks rather clunky and, as you mention, it might include random Chinese bloat/spyware. I'm hoping somebody can root this thing and we can get a developer scene going for it.
Some of the work done for Barnes & Noble Nook devices might be relevant, as those are also e-ink devices running Android.
For future reference, here's a list of everything installed on the stock ROM. I'm still trying to sort out what it all is, I think all the MTK* stuff are alternatives to missing Google packages provided by MediaTek.
$ pm list packages -f
package:/system/priv-app/FMRadio/FMRadio.apk=com.android.fmradio
package:/system/app/Gba/Gba.apk=com.mediatek.gba
package:/system/priv-app/ImsService/ImsService.apk=com.mediatek.ims
package:/system/plugin/PrivacyProtectionLock/PrivacyProtectionLock.apk=com.mediatek.ppl
package:/system/priv-app/CtsShimPrivPrebuilt/CtsShimPrivPrebuilt.apk=com.android.cts.priv.ctsshim
package:/system/app/Uicc2Terminal/Uicc2Terminal.apk=org.simalliance.openmobileapi.uicc2terminal
package:/system/priv-app/MtkTelephonyProvider/MtkTelephonyProvider.apk=com.android.providers.telephony
package:/system/app/Camera/Camera.apk=com.mediatek.camera
package:/system/priv-app/MtkCalendarProvider/MtkCalendarProvider.apk=com.android.providers.calendar
package:/system/priv-app/MtkMediaProvider/MtkMediaProvider.apk=com.android.providers.media
package:/vendor/app/LPPeService/LPPeService.apk=com.mediatek.location.lppe.main
package:/system/priv-app/WallpaperCropper/WallpaperCropper.apk=com.android.wallpapercropper
package:/vendor/app/SchedulePowerOnOff/SchedulePowerOnOff.apk=com.mediatek.schpwronoff
package:/system/app/Protips/Protips.apk=com.android.protips
package:/system/app/SmartcardService/SmartcardService.apk=org.simalliance.openmobileapi.service
package:/system/priv-app/MtkDocumentsUI/MtkDocumentsUI.apk=com.android.documentsui
package:/vendor/overlay/framework-res__auto_generated_rro.apk=android.auto_generated_rro__
package:/system/priv-app/ExternalStorageProvider/ExternalStorageProvider.apk=com.android.externalstorage
package:/system/app/YGPS/YGPS.apk=com.mediatek.ygps
package:/system/priv-app/MtkSimProcessor/MtkSimProcessor.apk=com.mediatek.simprocessor
package:/system/app/HTMLViewer/HTMLViewer.apk=com.android.htmlviewer
package:/system/app/CompanionDeviceManager/CompanionDeviceManager.apk=com.android.companiondevicemanager
package:/system/app/QuickSearchBox/QuickSearchBox.apk=com.android.quicksearchbox
package:/system/priv-app/MtkMmsService/MtkMmsService.apk=com.android.mms.service
package:/system/priv-app/MtkDownloadProvider/MtkDownloadProvider.apk=com.android.providers.downloads
package:/system/app/EngineerMode/EngineerMode.apk=com.mediatek.engineermode
package:/system/priv-app/xxLauncher/xxLauncher.apk=com.android.xx.launcherink
package:/system/app/Omacp/Omacp.apk=com.mediatek.omacp
package:/system/app/MtkBrowser/MtkBrowser.apk=com.android.browser
package:/system/app/OP01SoundRecorder/OP01SoundRecorder.apk=com.android.soundrecorder
package:/system/priv-app/WfoService/WfoService.apk=com.mediatek.wfo.impl
package:/system/priv-app/DefaultContainerService/DefaultContainerService.apk=com.android.defcontainer
package:/system/app/RedStoneOta/RedStoneOta.apk=com.redstone.ota.ui
package:/system/app/MtkDownloadProviderUi/MtkDownloadProviderUi.apk=com.android.providers.downloads.ui
package:/system/app/PacProcessor/PacProcessor.apk=com.android.pacprocessor
package:/system/app/CertInstaller/CertInstaller.apk=com.android.certinstaller
package:/system/priv-app/MtkCarrierConfig/MtkCarrierConfig.apk=com.android.carrierconfig
package:/system/framework/framework-res.apk=android
package:/system/priv-app/MtkContacts/MtkContacts.apk=com.android.contacts
package:/vendor/app/EmCamera/EmCamera.apk=com.mediatek.emcamera
package:/system/app/EasterEgg/EasterEgg.apk=com.android.egg
package:/system/priv-app/MtkMms/MtkMms.apk=com.android.mms
package:/system/priv-app/MtpDocumentsProvider/MtpDocumentsProvider.apk=com.android.mtp
package:/system/app/NfcNci/NfcNci.apk=com.android.nfc
package:/system/priv-app/Stk1/Stk1.apk=com.android.stk
package:/system/priv-app/BackupRestoreConfirmation/BackupRestoreConfirmation.apk=com.android.backupconfirm
package:/system/plugin/PermissionControl/PermissionControl.apk=com.mediatek.security
package:/system/app/BtTool/BtTool.apk=com.mediatek.bluetooth.dtt
package:/system/priv-app/Provision/Provision.apk=com.android.provision
package:/system/priv-app/StatementService/StatementService.apk=com.android.statementservice
package:/system/app/MDMLSample/MDMLSample.apk=com.mediatek.mdmlsample
package:/system/app/MtkCalendar/MtkCalendar.apk=com.android.calendar
package:/system/app/DrmProvider/DrmProvider.apk=com.mediatek.providers.drm
package:/vendor/overlay/SysuiDarkTheme/SysuiDarkThemeOverlay.apk=com.android.systemui.theme.dark
package:/system/priv-app/MtkSettingsProvider/MtkSettingsProvider.apk=com.android.providers.settings
package:/system/priv-app/SharedStorageBackup/SharedStorageBackup.apk=com.android.sharedstoragebackup
package:/system/app/PrintSpooler/PrintSpooler.apk=com.android.printspooler
package:/system/app/Uicc1Terminal/Uicc1Terminal.apk=org.simalliance.openmobileapi.uicc1terminal
package:/system/app/BasicDreams/BasicDreams.apk=com.android.dreams.basic
package:/system/app/webview/webview.apk=com.android.webview
package:/system/priv-app/InputDevices/InputDevices.apk=com.android.inputdevices
package:/system/app/BuiltInPrintService/BuiltInPrintService.apk=com.android.bips
package:/system/framework/mediatek-res/mediatek-res.apk=com.mediatek
package:/vendor/app/AutoDialer/AutoDialer.apk=com.example
package:/system/priv-app/DuraSpeed/DuraSpeed.apk=com.mediatek.duraspeed
package:/system/priv-app/MusicFX/MusicFX.apk=com.android.musicfx
package:/system/app/ExtShared/ExtShared.apk=android.ext.shared
package:/system/priv-app/OneTimeInitializer/OneTimeInitializer.apk=com.android.onetimeinitializer
package:/vendor/app/NlpService/NlpService.apk=com.mediatek.nlpservice
package:/system/priv-app/MtkTelecom/MtkTelecom.apk=com.android.server.telecom
package:/system/app/KeyChain/KeyChain.apk=com.android.keychain
package:/system/app/PrintRecommendationService/PrintRecommendationService.apk=com.android.printservice.recommendation
package:/system/priv-app/MtkDialer/MtkDialer.apk=com.android.dialer
package:/system/app/MtkGallery2/MtkGallery2.apk=com.android.gallery3d
package:/system/app/GoogleTTS/GoogleTTS.apk=com.google.android.tts
package:/system/priv-app/ExtServices/ExtServices.apk=android.ext.services
package:/system/priv-app/CallLogBackup/CallLogBackup.apk=com.android.calllogbackup
package:/system/priv-app/MtkPackageInstaller/MtkPackageInstaller.apk=com.android.packageinstaller
package:/system/priv-app/ProxyHandler/ProxyHandler.apk=com.android.proxyhandler
package:/system/app/MtkLatinIME/MtkLatinIME.apk=com.android.inputmethod.latin
package:/system/priv-app/ManagedProvisioning/ManagedProvisioning.apk=com.android.managedprovisioning
package:/system/app/CalendarImporter/CalendarImporter.apk=com.mediatek.calendarimporter
package:/vendor/app/MTKThermalManager/MTKThermalManager.apk=com.mediatek.thermalmanager
package:/system/priv-app/CallRecorderService/CallRecorderService.apk=com.mediatek.callrecorder
package:/system/app/MtkWebView/MtkWebView.apk=com.mediatek.webview
package:/system/app/WAPPushManager/WAPPushManager.apk=com.android.smspush
package:/vendor/app/SimRecoveryTestTool/SimRecoveryTestTool.apk=com.mtk.telephony
package:/system/priv-app/Baidu_Location/Baidu_Location.apk=com.baidu.map.location
package:/system/priv-app/StorageManager/StorageManager.apk=com.android.storagemanager
package:/system/app/OpenWnn/OpenWnn.apk=jp.co.omronsoft.openwnn
package:/system/app/BookmarkProvider/BookmarkProvider.apk=com.android.bookmarkprovider
package:/system/priv-app/MtkSettings/MtkSettings.apk=com.android.settings
package:/system/app/MDMConfig/MDMConfig.apk=com.mediatek.mdmconfig
package:/system/app/ExactCalculator/ExactCalculator.apk=com.android.calculator2
package:/vendor/app/LocationEM2/LocationEM2.apk=com.mediatek.lbs.em2.ui
package:/system/app/CtsShimPrebuilt/CtsShimPrebuilt.apk=com.android.cts.ctsshim
package:/system/priv-app/VpnDialogs/VpnDialogs.apk=com.android.vpndialogs
package:/system/app/MtkEmail/MtkEmail.apk=com.android.email
package:/vendor/app/MusicBspPlus/MusicBspPlus.apk=com.android.music
package:/system/priv-app/MtkTeleService/MtkTeleService.apk=com.android.phone
package:/system/priv-app/Shell/Shell.apk=com.android.shell
package:/system/app/WallpaperBackup/WallpaperBackup.apk=com.android.wallpaperbackup
package:/system/priv-app/BlockedNumberProvider/BlockedNumberProvider.apk=com.android.providers.blockednumber
package:/system/app/UserDictionaryProvider/UserDictionaryProvider.apk=com.android.providers.userdictionary
package:/system/priv-app/MtkEmergencyInfo/MtkEmergencyInfo.apk=com.android.emergency
package:/system/priv-app/FusedLocation/FusedLocation.apk=com.android.location.fused
package:/system/app/FactoryTest/FactoryTest.apk=com.xthink.factorytest
package:/system/app/MtkDeskClock/MtkDeskClock.apk=com.android.deskclock
package:/system/priv-app/MtkSystemUI/MtkSystemUI.apk=com.android.systemui
package:/system/app/Exchange2/Exchange2.apk=com.android.exchange
package:/system/app/BluetoothMidiService/BluetoothMidiService.apk=com.android.bluetoothmidiservice
package:/system/app/MtkNlp/MtkNlp.apk=com.mediatek.location.mtknlp
package:/system/app/FileManager/FileManager.apk=com.mediatek.filemanager
package:/system/app/MTKLogger/MTKLogger.apk=com.mediatek.mtklogger
package:/system/app/SensorHub/SensorHub.apk=com.mediatek.sensorhub.ui
package:/system/app/MtkBluetooth/MtkBluetooth.apk=com.android.bluetooth
package:/system/app/MtkWallpaperPicker/MtkWallpaperPicker.apk=com.android.wallpaperpicker
package:/system/priv-app/MtkContactsProvider/MtkContactsProvider.apk=com.android.providers.contacts
package:/system/app/CaptivePortalLogin/CaptivePortalLogin.apk=com.android.captiveportallogin
package:/system/plugin/DataProtection/DataProtection.apk=com.mediatek.dataprotection
package:/vendor/app/WapiCertManager/WapiCertManager.apk=com.wapi.wapicertmanager
package:/system/app/kindlefc/kindlefc.apk=com.amazon.kindle
Click to expand...
Click to collapse
I've managed to get the device into fastboot mode. I'd like to flash a custom recovery like TWRP, but I don't know which one is compatible with this device. Any suggestions?
Bunyip123 said:
I've managed to get the device into fastboot mode. I'd like to flash a custom recovery like TWRP, but I don't know which one is compatible with this device. Any suggestions?
Click to expand...
Click to collapse
do you happen to have the stock firmware with the boot.IMG. i want to look at it and see if its similar to my device. i have a umidigi one max and it has the same chipset and it looks like alot of the same apps
th3d3ck3r said:
do you happen to have the stock firmware with the boot.IMG.
Click to expand...
Click to collapse
No, I don't have the stock firmware. If you can point me to some instructions, I'm happy to try to extract a copy of it and post it here.
Kingrow K1 doesn't let me log in to google services
Hi,
I'm not a developer, sorry for my lack of knowledgle, however I'm desparate to find a sollution, maybe you can help me here.
I've bought the Kingrow K1 only to find there's no way of signing in to google accounts, contacts, callendar etc. $%^&*()!~
I hope it's just a question of installing and configuring the missing pieces.
Can you please help me out?
Tom
Maybe flashing Gapps like on AOSP? ?
You could try flashing a gapps package like https://opengapps.org/ but I don't know if it will work without root.
Bunyip123 said:
You could try flashing a gapps package but I don't know if it will work without root.
Click to expand...
Click to collapse
Without TWRP
We even have no stock firmware. I see it's a first step to acquire it.
sandworm88 said:
Without TWRP
We even have no stock firmware. I see it's a first step to acquire it.
Click to expand...
Click to collapse
is it of any help the url that get called when a k1 fails to find a new OTA firmware?
It's using a server called
fota.redstone.net.cn
on the port 6100
and it's asking for service/request
_jet said:
is it of any help the url that get called when a k1 fails to find a new OTA firmware?
It's using a server called
fota.redstone.net.cn
on the port 6100
and it's asking for service/request
Click to expand...
Click to collapse
...i'm just asking, i don't know anything about how to retrieve (and keep) a firmware copy
Any updates on this? someone in Kingrow K1 eReader/Phone User Group on FB claims they got root:
{
"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"
}
Hello, I've worked on a MT6763 device before. You may be in luck because MTK devices have built-in flash mode you can access. This would mean you can dump partitions provided you locate their offsets (if you can get hands on a scatter file, that would help a lot). The flash mode also allows you to bypass any locked bootloader (though, you don't seem to face such issue, but nice to know it's possible) restrictions. You may also be able to dd the blocks and create a stock firmware dump for backup. A good chance TWRP can be ported without kernel sources by using a very similar device's port as a base and dropping your current recovery image's kernel and fstab values in it.
I do not own this device myself, but I am interested in any findings regarding this topic. Good luck.
EDIT:
_jet said:
...i'm just asking, i don't know anything about how to retrieve (and keep) a firmware copy
Click to expand...
Click to collapse
Can you tell me how your /dev/block structure looks like, (use ls). If you navigate deep enough, you will see "by-name" folder, you can then dd the "boot" partition as a boot.img file.
EDIT2:
Actually, I suggest just dd'ing your system partition to your PC. You can also flash GSIs using fastboot. By dd'ing your system partition, you essentially make a fallback in case the image fails.
Cernodile said:
Hello, I've worked on a MT6763 device before. You may be in luck because MTK devices have built-in flash mode you can access. This would mean you can dump partitions provided you locate their offsets (if you can get hands on a scatter file, that would help a lot). The flash mode also allows you to bypass any locked bootloader (though, you don't seem to face such issue, but nice to know it's possible) restrictions. You may also be able to dd the blocks and create a stock firmware dump for backup. A good chance TWRP can be ported without kernel sources by using a very similar device's port as a base and dropping your current recovery image's kernel and fstab values in it.
I do not own this device myself, but I am interested in any findings regarding this topic. Good luck.
EDIT:
Can you tell me how your /dev/block structure looks like, (use ls). If you navigate deep enough, you will see "by-name" folder, you can then dd the "boot" partition as a boot.img file.
EDIT2:
Actually, I suggest just dd'ing your system partition to your PC. You can also flash GSIs using fastboot. By dd'ing your system partition, you essentially make a fallback in case the image fails.
Click to expand...
Click to collapse
Thanks for you answer @Cernodile. I'm the guy Ti He who posted in the FB group.
I'm currently trying to port a TWRP to our device. First I did a full read with Miracle Box, so in case something goes wrong I can restore my device. I used a TWRP from Cubot King Kong 3 because it has the same SoC and GPU. I unpacked my stock recovery and the Cubot recovery and replaced files like recovery.img-kernel
recovery.img-kernel_offset
ramdisk/prop.default
ramdisk/init files
ramdisk/ueventd.rc
ramdisk/ect/recovery.fstab
I flashed the repacked recovery through fastboot and booted into TWRP. I assume that TWRP would have been booted, because I can do adb devices and see my phone in recovery. But the display only shows some black lines, so there must be something wrong. Do you have any idea where to look at? See attached the log from /cache/recovery/.
Regards - Timo
helnorsksvartmetall said:
Thanks for you answer @Cernodile
I'm currently trying to port a TWRP to our device. First I did a full read with Miracle Box, so in case something goes wrong I can restore my device. I used a TWRP from Cubot King Kong 3 because it has the same SoC and GPU. I unpacked my stock recovery and the Cubot recovery and replaced files like recovery.img-kernel
recovery.img-kernel_offset
ramdisk/prop.default
ramdisk/init files
ramdisk/ueventd.rc
ramdisk/ect/recovery.fstab
I flashed to repacked recovery through fastboot and booted into TWRP. I assume that TWRP would have been booted, because I can do adb devices and see my phone in recovery. But the display only shows some black lines, so there must be something wrong. Do you have any idea where to look at? See attached to log from /cache/recovery/.
Regards - Timo
Click to expand...
Click to collapse
That seems already quite promising! It seems like your device is trying to render some TWRP elements, perhaps you have wrong resolution set as suggested by "framebuffer: 3 (344 x 725)". What would assist me here greatly would be .prop files from stock and your TWRP port such as default.prop.
I also attached the Scatter file from my device on my last post.
See below the prop files from stock and port (Cubot King Row 3).
(I also tried with port TWRP from Umidigi One Max but with the same result)
helnorsksvartmetall said:
I also attached the Scatter file from my device on my last post.
See below the prop files from stock and port (Cubot King Row 3).
(I also tried with port TWRP from Umidigi One May but with the same result)
Click to expand...
Click to collapse
First inconsistencies I see:
This is in your stock, but not port.
Code:
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
dalvik.vm.isa.arm64.variant=cortex-a53
dalvik.vm.isa.arm64.features=default
dalvik.vm.isa.arm.variant=cortex-a53
Although, I don't think that is the cause. I'd keep looking for a device that has e ink patches for TWRP, you can use that as base, rebuild the similar device's TWRP and then do same port method.
Xperia Chinese Keyboard modified to work on any device
Supports pinyin, zhuyin, stroke order, handwriting and Cangjie, as well as English input
Version: 25.1.A.0.45 Patch #6 Updated 2022-11-18
{
"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"
}
Download
From Mega.nz (file too large to attach here):
Patch 6 for LOS 19.1 / Android 12
Patch 5 for LOS 18.1 / Android 11
Spoiler: Other versions – for reference only
Patch 4 - Test (for Lineage 18.1, test workaround)
Patch 3 (for LineageOS 18.1, occasional crashes)
Patch 2 (for LineageOS 17.1)
Patch 1 (for LineageOS 16.0)
Installation
Best installed with: adb install -g <filename>
Otherwise, have to manually grant the permission: Settings → Apps & notifications → See all apps → Xperia Chinese keyboard → Advanced → Display over other apps: Allowed (will crash if you won't)
Enable the input method in Settings → Languages & input and switch to it using the keyboard icon on the navigation bar, which appears when you start editing text
Some Details
Based on firmware H9493_Customized TW_52.1.A.3.137-R4C for Sony Xperia XZ3 (Akatsuki)
Includes libraries to make it work as a user (not system) app:
libbase.so, libc++.so, and libnativehelper.so from LineageOS 18.1
libsqlite.so from SQLite's official precompiled Android binaries
Changed values loaded into $LayoutParams;->type:I from 0x000007dc = 0x000007d9 (TYPE_KEYGUARD_DIALOG) | 0x00000002 (TYPE_APPLICATION) | 0x00000001 (TYPE_BASE_APPLICATION), only allowed for system apps, to 0x000007f6 (TYPE_APPLICATION_OVERLAY) and updated the manifest accordingly to request the permission android.permission.SYSTEM_ALERT_WINDOW (which must be granted manually)
Patch 3: Remove dependency on Sony Vibration Effect library (com.sonymobile.vibrationeffect.api_1) from the manifest
Patch 3: Replace all references to Sony Vibration Effect library: invoke-static {p1}, Lcom/sonymobile/vibrationeffect/VibrationEffect;->get(I)Landroid/os/VibrationEffect;which were causing the app to crash, with standard Android calls:
const/4 p0, -0x1 (DEFAULT_AMPLITUDE)
const-wide/16 v2, 0xc (Duration: 12 ms)
invoke-static {v2, v3, p0}, Landroid/os/VibrationEffect;->createOneShot(JI)Landroid/os/VibrationEffect;
— for keypresses
const v0, 0x2 (EFFECT_TICK)
invoke-static {v0}, Landroid/os/VibrationEffect;->createPredefined(I)Landroid/os/VibrationEffect;
— for other events
Patch 4 - Test: Remove the invocation of a virtual method invoke-virtual {p0}, Lcom/sonyericsson/textinput/chinese/uxp/view/hw/HWFullView;->getVisibility()I that causes a crash under some circumstances in InputMethodServiceGlue. However the side effect of this change is that other UI elements cannot be interacted with while the keyboard is open. How to fix this completely needs further investigation. Since the crash seems rare, I recommend sticking with Patch 3 for now.
Patch 5: A different workaround for the above mentioned issue. If iget-object p0, p0, Lcom/sonyericsson/textinput/chinese/glue/InputMethodServiceGlue;->mHwFullView:Lcom/sonyericsson/textinput/chinese/uxp/view/hw/HWFullView; returns 0 (i.e. effectively NULL but there's no explicit check for that in Smali), then skip the call and return from the method. Otherwise, proceed. After a week of testing, this seems to work well: no rare crashes, and the UI is accessible too with the keyboard open.
Tested to work on two different LineageOS 18.1 devices. Should work elsewhere too. If it doesn't, it's probably because of the three libraries (libbase.so, libc++.so, and libnativehelper.so): check adb logcat and replace them with the versions from your system.
Patch 6: Fix compatibility with LOS 19.1/Android 12 where a call to jniGetFDFromFileDescriptor() from libnativehelper.so fails by design due to API changes (see: Google Issue Tracker), and the version of the library included with the app can no longer be used due to name conflict with the system library with the same name. The workaround: rename the bundled libnativehelper.so (same as Patch 5/Android 11/LOS 18.1, so unchanged) to libforeignenemy.so and change references to it in libcootek_pte_oem.so, libcootek_pte_oem_western.so and libcurve_oem.so accordingly. Also update libbase.so and libc++.so to current versions from LOS 19.1 (Android 12).
Related
Xperia keyboard for most languages port by @greenys'
Xperia Chinese keyboard version 10.1.A.0.1 (Android 4.4+, 2012-2013) by @danist727
That's some amazing work there. I wish there was a more up to date version for general languages not just the good ol 8.0.A.110 version that I've been using for 3 years or more across my devices. Thanks a lot.
Thank you for your work! However, the link is down, it is giving 410 error from XDA. Can you reupload it? Thanks again.
sjdhmtthm said:
Thank you for your work! However, the link is down, it is giving 410 error from XDA. Can you reupload it? Thanks again.
Click to expand...
Click to collapse
Hi, the files are attached to the post, so they are hosted here on XDA. I checked the links and they seemed to start downloading correctly for me but now I edited the post and removed the inline links, so the files should show up as an attachment below the post instead.
Can you successfully download any other attachments at all (from other posts)? Maybe there are some restrictions in place for newly-created XDA accounts. Anyway, if they still don't download for you, let me know and I'll upload them elsewhere as well. (The advantage of having the files hosted here is that the links never expire.)
Aqq123 said:
Hi, the files are attached to the post, so they are hosted here on XDA. I checked the links and they seemed to start downloading correctly for me but now I edited the post and removed the inline links, so the files should show up as an attachment below the post instead.
Can you successfully download any other attachments at all (from other posts)? Maybe there are some restrictions in place for newly-created XDA accounts. Anyway, if they still don't download for you, let me know and I'll upload them elsewhere as well. (The advantage of having the files hosted here is that the links never expire.)
Click to expand...
Click to collapse
It works now, must be having some errors just now. Thanks again.
Edit: Part 2 seems to not be able to download and corrupted, second try gives me the same error again.
I asked my friend who is not logged in to download and he experienced the same error.
It would be great if you can upload it elsewhere, the two tries I where I successfully downloaded part 2 returns corrupted. Thank you.
Edit 2: Changing browsers on mobile worked. Surprised that both Firefox on mobile and desktop returned an error for me. Thank you, problem is solved.
Is this keyboard for chinese only or can I use english as well? its been a while and long since we get an updated Xperia Keyboard version, still using the 2/3 years old v8.1.A.0.12 dated November 12, 2017.
SM-03 said:
Is this keyboard for chinese only or can I use english as well?
Click to expand...
Click to collapse
It can be used for English input too. If you take a look at the first 3 screenshots, there is a button (labelled "CN") that toggles between English and Chinese in the bottom right corner of the keyboard.
It supports word completion in English too but there's no way to type accented characters (for other languages written in the Latin script).
how to dl and extract this? I downloaded two p[arts but still getting error while extracting, any other parts there or missing?
is there any update for android10?
after update to 55.1.A.0.748
chinese keyboard keep crashed
SM-03 said:
any other parts there or missing?
Click to expand...
Click to collapse
Just checked again, it unpacks fine. Nothing is missing. The complete instructions are already in the first post. Not sure what else would need explaining.
frank3302 said:
is there any update for android10?
Click to expand...
Click to collapse
I don't use Android 10. Feel free to contribute an update, and I will link to it in the first post.
Aqq123 said:
Just checked again, it unpacks fine. Nothing is missing. The complete instructions are already in the first post. Not sure what else would need explaining.
Click to expand...
Click to collapse
Yes, it's working (extracted) as per the instructions written into the OP, but the font size is too small that I didn't see /notice that instruction earlier, you should've mentioned that in bold & highlighted for better & clear visibility.
SM-03 said:
I didn't see /notice that instruction earlier, you should've mentioned that in bold & highlighted for better & clear visibility.
Click to expand...
Click to collapse
This board is called XDA Developers for a reason. As a participant you are expected to possess a modicum of rudimentary computer skills and, more importantly, willingness to learn to solve your own problems. In particular, this thread is in the Development section. This is not the place to demand an illustrated step-by-step tutorial how to unpack a ZIP file.
Besides, as duly proven, even the best instructions won't help an ignorant person who can't be bothered to read them such as yourself. And finally, neither me nor anyone else here owes you anything just because you can't get something to work, so the only thing I "should have" is not indulged this behavior earlier.
Good luck with your future endeavors as you will need it with this kind of an attitude. Now, feel free to move on.
Aqq123 said:
This board is called XDA Developers for a reason. As a participant you are expected to possess a modicum of rudimentary computer skills and, more importantly, willingness to learn to solve your own problems. In particular, this thread is in the Development section. This is not the place to demand an illustrated step-by-step tutorial how to unpack a ZIP file.
Besides, as duly proven, even the best instructions won't help an ignorant person who can't be bothered to read them such as yourself. And finally, neither me nor anyone else here owes you anything just because you can't get something to work, so the only thing I "should have" is not indulged this behavior earlier.
Good luck with your future endeavors as you will need it with this kind of an attitude. Now, feel free to move on.
Click to expand...
Click to collapse
wow, so many words for just saying the small font & you should've written it with bigger font size for better visibility? You're rare & amazing.
I am not able to merge the two zipped files into one. I followed the instruction to rename as .zip and .z01 for both files but the second part stated no content inside to extract. should I download rar software to unrar it in desktop file explorer? Can someone kind hearted enough keep the file in one and upload somewhere for me to download?
atisha said:
I am not able to merge the two zipped files into one. I followed the instruction to rename as .zip and .z01 for both files but the second part stated no content inside to extract. should I download rar software to unrar it in desktop file explorer? Can someone kind hearted enough keep the file in one and upload somewhere for me to download?
Click to expand...
Click to collapse
I just checked and it unpacks with WinRAR and 7-Zip for me. Anyway, since I made another version later, here they are both, externally hosted:
Patch 2 (try this first, should be compatible with LineageOS 17.1 at least)
Patch 1 (original version as linked above)
I also updated the original post accordingly.
Found a Bug
Hi Aqq123,
This is some impressive work, thank you for making this!
Just wanted to post a bug I found: the "pull down menu" for the Chinese typing doesn't work. E.g. I want to type the word 蚝煎, but after clicking on the arrow on the right, nothing appears! So I wasn't able to type things beyond the suggestions in the first row.
I'm using Sony Xperia 10 II, Android 10 (Build number 59.0.A.10.5), and I used Patch 2 of your download. Would really appreciate if you could solve the bug, because this keyboard is such a life saver for me. Thanks!
Screenshot: https:// drive. google. com/ file/ d/ 12eEBAzBalbq0ZKfQMh2SLI-045-Gb1Z1/ view?usp=sharing
(Included the spacing because the forum just wouldn't let me post it)
johnsyh said:
Just wanted to post a bug I found: the "pull down menu" for the Chinese typing doesn't work
Click to expand...
Click to collapse
You're right, thanks for spotting it. It used to work in the first version though, so it's probably down to some library incompatibility (and the first version itself won't work with the newer Android). I'll look into it when I have the time. A better approach though might be to ditch it altogether and look at adopting a newer APK version instead. Meanwhile, a lousy workaround is to just hand-write the character.
Since you're using Sony stock firmware, have you tried downloading the Hong Kong or Taiwan version for your device with XperiFirm, extracting the APK from there (for example with UnSIN), and installing it? It'd either work immediately or, if not, the exact library versions to make it work would also be there.
Aqq123 said:
Hi, the files are attached to the post, so they are hosted here on XDA. I checked the links and they seemed to start downloading correctly for me but now I edited the post and removed the inline links, so the files should show up as an attachment below the post instead.
Can you successfully download any other attachments at all (from other posts)? Maybe there are some restrictions in place for newly-created XDA accounts. Anyway, if they still don't download for you, let me know and I'll upload them elsewhere as well. (The advantage of having the files hosted here is that the links never expire.)
Click to expand...
Click to collapse
Thank you so much. I am able to download patch 2 and install directly. So so very grateful as this is the best T9 keyboard ever! (Could be better if it supports Malay too with black layout white font but one shouldnt be too greedy).
Aqq123 said:
You're right, thanks for spotting it. It used to work in the first version though, so it's probably down to some library incompatibility (and the first version itself won't work with the newer Android). I'll look into it when I have the time. A better approach though might be to ditch it altogether and look at adopting a newer APK version instead. Meanwhile, a lousy workaround is to just hand-write the character.
Since you're using Sony stock firmware, have you tried downloading the Hong Kong or Taiwan version for your device with XperiFirm, extracting the APK from there (for example with UnSIN), and installing it? It'd either work immediately or, if not, the exact library versions to make it work would also be there.
Click to expand...
Click to collapse
HI would you have general sony xperia keyboard (non Chinese, English) apk as well to share? with layout skin colour if possible.
On behalf of my wife, who has just upgraded from Xperia XZs to the new Xperia 1 III, and couldn't get over how bad gboard is over the Xperia 注音 input (she has a very unusual character in her name, which gboard doesn't recognize, it spoiled her fun of getting a new device when she couldn't even type her name in correctly during setup) - thank you! You have made me a hero around the house for finding this, and installing it on her phone. My old account on this forum got lost in time, gone with an e-mail domain that no longer exists, but I set up a new one just to thank you for your work!
Please read the following instructions carefully .
Download Link(only latest):
G980F Version 1.2.0 https://drive.google.com/file/d/1w-5cKNsord7KwvfOAD8hTvxhAS__6mmo/view?usp=sharing
G985F Version 1.1.0 https://drive.google.com/file/d/1kEOkf5Yfs3DGDYjSwph-mINwmOtZ2JUR/view
G981B Planed
G986B Planed
G988B Planed Should be next since I got tons of request.
This custom firmware is based on stock S20(+) G980(5)FXXU4BTH5 . Please make sure you are using G980F/G985F. The G980F is a unblocked 4G version S20, the G985F is a unblocked 4G version S20+.
Depending on the feedbacks and requirements, I might make for other variants in the future. But now, G980F/G985F are the only supported devices.
Disclaimer:
1.This firmware has been tested on G980F real device properly, however, you choose to use at your own risk.
2.Feedbacks are generally welcomed, but please use "search thread" function before ask how to fix xxx problem.
Features:
1.Patched boot.img with Magisk. thanks (https://github.com/topjohnwu/magisk_files/tree/canary)
2.Debloat system.img/product.img, full list below.
3.Deknox system.img/product.img, full list below.
4.Debloat prism.img, full list below.
5.Debloat userdata.img, full list below.
6.Build.prop tweaks in system.img.
7.Replace Samsung default apps(Contacts, Calender, Clock, Calculator, Messages, Dialer, Recorder) to Google apps in system.img.
8.Clear Bootlogo, thanks (https://forum.xda-developers.com/galaxy-s20/development/s20-5g-clean-bootlogo-unlocking-t4067177)
9.Mod optics.img to unlock the advanced features, thanks (https://forum.xda-developers.com/ga...agisk-module-decodedcscfeaturesfiles-t4082445)
10.Mod vbmeta.img to disable Android Verified Boot(proved in screenshot below), thanks (https://forum.xda-developers.com/galaxy-s20/how-to/howto-root-s20-series-upgrade-firmware-t4079353)
11.Disable first boot initial setup wizard, your first boot will enter the system straight away.
12.Debloat media/audio(alarms, notification, ringtones), replace with theme audio from Samsung/Google Pixel/Sony.
13.Youtube No Ad version included. Please disable auto update from Google Play, if you accidentally update youtube, you can always uninstall update from google play, thanks (https://forum.xda-developers.com/android/apps-games/app-youtube-vanced-edition-t3758757)
14.All apps up-to-date(28/9/2020) in this rom.
How to flash?
0. Back up all your data.
1. OEM unlock follow (https://forum.xda-developers.com/galaxy-s20/how-to/howto-root-s20-series-upgrade-firmware-t4079353)
2. Download the zip file flash with Odin.
3. Choose BL, AP and CP. Please note there is no CSC.tar in this zip, since CSC files are included in AP.
4. After flashing, make sure wipe data/factory reset in recovery. (Volume up + power button when boot up)
5. Enjoy!
Changelog:
1.2.0
1.Support G980F
2.Based on BTIB OneUI 2.5 Sep Patch, (1.Improved performance. - Camera 2.The security of your device has been improved.) (https://doc.samsungmobile.com/SM-G980F/DBT/doc.html)
3.Fix Samsung Health compatibility, you can install from Google Play or Samsung store.
4.Replace Samsung Dialer with Google Dialer, now we are Samsung app free except the Samsung Gallery app, since stock camera app can only open gallery.
5.Fix some bugs here and there.
1.1.0
1.Support G980F/G985F.
2.Based on BTH5 OneUI 2.5, all apps update-to-date.
3.Fix some bugs here and there.
4.Debloat list update.
1.0.0
1.Support G980F.
2.All basic features implemented.
FAQ/Known issues:
1.Accessibility -> Visibility enhancements can not be open. This is due to nasty Samsung requires Samsung keyboard's content provider to open this setting. Since Samsung keyboard is considered as bloatware, so you wouldn't be able to open this setting. But in reality, there is nothing need to be set in this setting unless you are colour-blind or having other vision disorder.
2.Please don't mod /system partition. Originally, if you using the official firmware, you can't even edit /system partition. Now you can with edited super.img and root access, but it will cause boot loop. I believe this is a mount issue with logical partition. To save your soft brick phone, the easily way is extract super.img from AP, compress super.img to super.tar, then simply flash super.tar as AP in odin and reboot, no need to wipe data/factory reset.
3.Riru Edxposed is fully compatible, since it is systemless.
4.If you found any app you want to use is in the debloat list, you can try to manually install but please do not ask me how to fix certain apps, such questions won't be answered again and again.
5.Generally speaking, if you found any app does not work but it is not in the debloat list, chances are you forgot wipe data/cache in recovery after flashing this rom.
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"
}
Here is a list of bloats been deleted in system.img/product.img.
#Knox
system\app\BBCAgent
system\app\KnoxAttestationAgent
system\app\MDMApp
system\app\SecurityLogAgent
system\app\UniversalMDMClient
system\priv-app\DiagMonAgent
system\priv-app\KLMSAgent
system\priv-app\KnoxCore
system\priv-app\knoxvpnproxyhandler
system\priv-app\knoxanalyticsagent
system\priv-app\KnoxDesktopLauncher
system\priv-app\KnoxKeyChain
system\container
system\etc\permissions\knoxsdk_mdm.xml
system\etc\permissions\knoxsdk_edm.xml
#Skip Setup & Restore
product\priv-app\SetupWizard
product\priv-app\GoogleOneTimeInitializer
product\priv-app\GoogleRestore
#AR
system\app\ARDrawing
system\app\ARZone
system\app\ARCore
system\app\VisionARApps1.1
system\priv-app\AREmoji
system\priv-app\AREmojiEditor
system\priv-app\AvatarEmojiSticker*
system\priv-app\AutoDoodle_Q
system\priv-app\LiveStickers
#Bixby
system\app\*Bixby*
system\app\VisionARApps
system\app\VisionIntelligence*
system\priv-app\Bixby*
system\priv-app\Routines
system\priv-app\*Bixby*
#Wearable
system\app\AntHalService
system\app\ANTPlusPlugins
system\app\ANTPlusTest
system\app\GearManagerStub
system\priv-app\ANTRadioService
#Dex
system\priv-app\DesktopModeUiService
system\priv-app\DeXonPC
system\priv-app\SystemUIDesktop
#Original Youtube
product\app\YouTube
#Samsung Mixed
system\app\ClockPackage
system\app\DailyBoard
system\app\GameOptimizingService
system\app\HoneyBoard
system\app\KidsHome_Installer
system\app\LinkSharing*
system\app\LiveDrawing
system\app\SamsungCalendar
system\app\SamsungDaily
system\app\SamsungPassAutofill*
system\app\SamsungTTS
system\app\SBrowserEdge
system\app\SecFactoryPhoneTest
system\app\SetupWizardLegalProvider
system\app\SmartSwitchAgent
system\app\SmartReminder
system\app\VideoEditorLite_Dream_N
system\app\VideoTrimmer
system\app\Weather_SEP*
system\priv-app\AuthFramework
system\priv-app\GameHome
system\priv-app\GameOptimizingService
system\priv-app\GameTools_Dream
system\priv-app\MateAgent
system\priv-app\PreloadInstaller
system\priv-app\SamsungContacts
system\priv-app\SamsungCloudClient*
system\priv-app\SamsungMessages*
system\priv-app\SamsungPass
system\priv-app\SamsungSocial
system\priv-app\SendHelpMessage
system\priv-app\SmartSwitchAssistant
system\priv-app\SecMyFiles*
system\priv-app\SOAgent
system\priv-app\SPPPushClient
system\priv-app\SVoiceIME
system\priv-app\OneDrive*
system\priv-app\Tips
#Other Mixed
product\app\DuoStub
product\priv-app\AndroidAutoStub
product\priv-app\Turbo
system\app\AutomationTest_FB
system\app\BasicDreams
system\app\BlockchainBasicKit
system\app\CarmodeStub
system\app\DictDiotekForSec
system\app\DRParser
system\app\DuoStub
system\app\EasterEgg
system\app\EasyOneHand3
system\app\ESEServiceAgent
system\app\Facebook_stub
system\app\FBAppManager_NS
system\app\FactoryAirCommandManager
system\app\FactoryCameraFB
system\app\FlipboardBriefing
system\app\HandwritingService
system\app\IceCone
system\app\Netflix_activationCommon
system\app\Netflix_stub
system\app\SafetyInformation
system\app\WebManual
system\app\WifiGuider
system\priv-app\AndroidAutoStub
system\priv-app\ContainerAgent*
system\priv-app\DigitalWellbeing
system\priv-app\EnhancedAttestationAgent
system\priv-app\FBInstaller_NS
system\priv-app\FBServices
system\priv-app\Fmm
system\priv-app\FotaAgent
system\priv-app\HealthService
system\priv-app\LedBackCoverAppHubble
system\priv-app\LedCoverService
system\priv-app\LinkToWindowsService
system\priv-app\ManagedProvisioning
system\priv-app\NSFusedLocation*
system\priv-app\PaymentFramework
system\priv-app\RubinVersion*
system\priv-app\SecureFolder
system\priv-app\Upday
system\priv-app\YourPhone*
system\preload\SmartSwitch
system\etc\recovery-resource.dat
system\recovery-from-boot.p
system\hidden\INTERNAL_SDCARD\Samsung
system\media\audio\ui\Media_preview_Over_the_horizon.ogg
system\tts
Here is a screenshot of bloats in prism.img
Here is a screenshot of bloats in userdata.img
Reserved.
thanks for share。
Sent from my HTC U11+ using XDA Labs
hi mate
can i use this on S20 ULTRA?
patuticci said:
hi mate
can i use this on S20 ULTRA?
Click to expand...
Click to collapse
no
hmy65 said:
@MikeChannon
Can you move this post to Samsung Galaxy S20 / S20+ / S20 Ultra Samsung Galaxy [EXYNOS] S20 / S20+ / S20 Ultra ROMs, Kernels, Recoveries, & Other Development?
I can't post at that area. But I think only I made the public available S20 custom rom right now.
Click to expand...
Click to collapse
hi man,
can you do the same for S20Ultra G988B?
or if you can share what you used to do maybe someone could do it for S20Ultra G988B.
thanks.
stefanz08 said:
hi man,
can you do the same for S20Ultra G988B?
or if you can share what you used to do maybe someone could do it for S20Ultra G988B.
thanks.
Click to expand...
Click to collapse
Hi, I only have S20 G980F. To release a custom firmware, I need to test it on real device to make sure it won't break your phone, because I can't expect everyone to have the ability to save their soft-bricked phone. I saw some people doing this to expect others to test for them, but that is not my current way of doing things, maybe it will change in the future. Thanks for understanding.
hmy65 said:
Hi, I only have S20 G980F. To release a custom firmware, I need to test it on real device to make sure it won't break your phone, because I can't expect everyone to have the ability to save their soft-bricked phone. I saw some people doing this to expect others to test for them, but that is not my current way of doing things, maybe it will change in the future. Thanks for understanding.
Click to expand...
Click to collapse
hi,
total understanding.
but if you can /want to send me a private message how it is doing and i will doing it for my onw. if you want.
and btw, the debloated ROM is rooter right? if you are using Magisk..
stefanz08 said:
hi,
total understanding.
but if you can /want to send me a private message how it is doing and i will doing it for my onw. if you want.
and btw, the debloated ROM is rooter right? if you are using Magisk..
Click to expand...
Click to collapse
It is rooted by patching boot.img with Magisk.
If you asking how to make this ROM, you need to use Linux. 1. extract tar 2. extract lz4 3. convert sparse img to ext img 4. mount and edit that img 5. convert ext img back to sparse img.
Can someone post system.img vendor.img unpacked from super.img
Thank you very much for your efforts, is there anyway to get my led cover working? I've tried downloading the APK with no luck
i understand it right, that i just have to unlock bootloader? So i only have to do stage 1,2 and then i can flash it?
And should i use my HOME_CSC (DBT)?
I just unlocked my boot loader, then booted system to check its unlocked in developer options, then flashed using Odin using only the files in the download,I didn't add my own home CSC,
bazz007 said:
Thank you very much for your efforts, is there anyway to get my led cover working? I've tried downloading the APK with no luck
Click to expand...
Click to collapse
Sorry, I didn't expect anyone use Samsung's offcial led cover. So I deleted that supported apk as a bloat. Next update I will include that apk.
Segelflugpilot said:
i understand it right, that i just have to unlock bootloader? So i only have to do stage 1,2 and then i can flash it?
And should i use my HOME_CSC (DBT)?
Click to expand...
Click to collapse
If you read the instruction carefully, you should notice I mentioned you don't need CSC.
No problem, thx
Yeah i have read that it is in the AP, but just want to be Sure, sorry. Thanks!
if editing system causes bootloop then u probably didnt disable avb.. u cant disable simply by editing vbmetq anymore.. theres more steps to it then that
elliwigy said:
if editing system causes bootloop then u probably didnt disable avb.. u cant disable simply by editing vbmetq anymore.. theres more steps to it then that
Click to expand...
Click to collapse
The way to disable avb is from ((https://forum.xda-developers.com/gal...mware-t4079353)), I mentioned that in the post.
However, I don't think bootloop is caused by avb.
I guess is caused by super.img. Cuz super.img uses logical partition, I use lpunpack/lpmake to unpack/repack that to system.img, product.img, odm.img, vendor.img.
I guess maybe some data lost during these processes causes the entire system.img uneditable, but it won't affect your normal daily use.
Cuz I tried only root with magisk with stock firmware, the entire system partition is read only. But with my repacked super.img, you can edit system partition, but it can cause bootloop.
There is no twrp for firmware packed with super.img, even they don't know how to mount logical partition properly, so I can only do my best lol
Please Help
Hi there, I'm having some issues flashing the three .tar files in Odin - Odin is getting stuck on <ID:0/005> up_param.bin
Please can you assist, thanks.
Andy1122 said:
Hi there, I'm having some issues flashing the three .tar files in Odin - Odin is getting stuck on <ID:0/005> up_param.bin
Please can you assist, thanks.
Click to expand...
Click to collapse
1.Are you using G980F the S20 4G version?
2.Check your devices is OEM unlocked.
3.From other members post, this ROM has no problem with odin at all.
*** Please follow the laws and regulations of the corresponding country or region ***
thanks for @HarryShan
I'm not living in Japan and use other country SIM card always shutter sound.
Pixel 6 Pro has a Model ID GF5KQ for Japan
G8VOU for US
they are same hardware
changing Model ID can control Gcam shutter sound
Model ID storage in /dev/block/by-name/devinfo for pixel 6 and 6 pro
run a adb shell to changing or using terminal
1.shell into phone
adb shell
Click to expand...
Click to collapse
2.change to root
$su
Click to expand...
Click to collapse
3.copy devinfo to img
#dd if=/dev/block/by-name/devinfo of=/sdcard/devinfo.img
Click to expand...
Click to collapse
4.changing Model ID with hex editer
{
"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"
}
5.save and flash back
# dd if=/sdcard/Mod_devinfo.img of=/dev/block/by-name/devinfo
Click to expand...
Click to collapse
6.reboot and enjoy it.
In theory, it should be possible to use “fastboot flash devinfo xxx.img”
But it should be necessary to repackage the img file before .
Please tell me if there is a systemless method , thanks
This Is Why In Japan A Phone’s Camera Shutter Sound Cannot Be Muted
You know that annoying “passht” camera shutter sound your phone makes whenever you take a picture? Well, in Japan, you can’t mute it, not even if you switch to mute mode! Here’s why.
Back in early 2000, when Kyocera VP-210 was launched, Japan became the first country to sell camera equipped phones. These phones also had the ability to send photos via email (pretty astonishing for 2000, isn’t it?). When users started to get used to them and learned how to attach pictures to an email, a big problem started to emerge: as any citizen of a civilized society would do, people started using their camera to take up-skirt photos of women, especially in crowded places like trains!
By 2001, this was already a matter of online discussion and, because no legal provision has been taken by the government, wireless carriers took it upon themselves. In order to prevent secret filming and ensure privacy, carriers made it a requirement that all phones sold in Japan must be customized for the market so that all built-in cameras cannot be muted.
Phone producers and Japanese wireless carriers have cooperated ever since so that all phones make a distinct sound whenever you use the camera.
This Is Why In Japan A Phone's Camera Shutter Sound Cannot Be Muted
Tap on the pic to find out.
theuijunkie.com
@iCassius
You can use my Magisk module.
Basically you only need to "setprop audio.camerasound.force false" and overlay to disable force sound.
GitHub - AndroPlus-org/magisk-module-pixel6: Google Pixel 6シリーズ以降向けのMagiskモジュールです。
Google Pixel 6シリーズ以降向けのMagiskモジュールです。. Contribute to AndroPlus-org/magisk-module-pixel6 development by creating an account on GitHub.
github.com
miravision said:
This Is Why In Japan A Phone’s Camera Shutter Sound Cannot Be Muted
You know that annoying “passht” camera shutter sound your phone makes whenever you take a picture? Well, in Japan, you can’t mute it, not even if you switch to mute mode! Here’s why.
Back in early 2000, when Kyocera VP-210 was launched, Japan became the first country to sell camera equipped phones. These phones also had the ability to send photos via email (pretty astonishing for 2000, isn’t it?). When users started to get used to them and learned how to attach pictures to an email, a big problem started to emerge: as any citizen of a civilized society would do, people started using their camera to take up-skirt photos of women, especially in crowded places like trains!
By 2001, this was already a matter of online discussion and, because no legal provision has been taken by the government, wireless carriers took it upon themselves. In order to prevent secret filming and ensure privacy, carriers made it a requirement that all phones sold in Japan must be customized for the market so that all built-in cameras cannot be muted.
Phone producers and Japanese wireless carriers have cooperated ever since so that all phones make a distinct sound whenever you use the camera.
This Is Why In Japan A Phone's Camera Shutter Sound Cannot Be Muted
Tap on the pic to find out.
theuijunkie.com
Click to expand...
Click to collapse
while I'm not Japanese, I do find these articles somewhat annoying as they sort of paint a negative image of Japanese people in general. yeah, of course there are perverts in Japan that do this, but as many as there are Japanese perverts, there are that many if not more in other countries as well.
Do you know if this can be done to enable the mmWave on GLU0G European model?
Other question: updating firmware will not overwrite that memory block, right?
gpvecchi said:
Do you know if this can be done to enable the mmWave on GLU0G European model?
Click to expand...
Click to collapse
Idont think so ,These 2 versions should be different hardware scales
this partition will not flash with update package
it only record your mac addr bt addr and etc
so be careful
Yeah. It's a first world problem. When I try to take a picture of my kids while they're asleep the shutter awakens them. There are several camera apps in the store (s) that don't make the shutter sound if you're interested.
I'm thankful for the sound tbh. People at times try to record my kids on the trains( Japanese with natural blonde hair) usually I just tell them to stop and they do.
My kids aren't a tourist attraction for your amusement...
AndroPlus said:
@iCassius
You can use my Magisk module.
Basically you only need to "setprop audio.camerasound.force false" and overlay to disable force sound.
GitHub - AndroPlus-org/magisk-module-pixel6: Google Pixel 6シリーズ以降向けのMagiskモジュールです。
Google Pixel 6シリーズ以降向けのMagiskモジュールです。. Contribute to AndroPlus-org/magisk-module-pixel6 development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
how exactly to do this, sorry but i am a newbie
iCassius said:
*** Please follow the laws and regulations of the corresponding country or region ***
thanks for @HarryShan
I'm not living in Japan and use other country SIM card always shutter sound.
Pixel 6 Pro has a Model ID GF5KQ for Japan
G8VOU for US
they are same hardware
changing Model ID can control Gcam shutter sound
Model ID storage in /dev/block/by-name/devinfo for pixel 6 and 6 pro
run a adb shell to changing or using terminal
1.shell into phone
2.change to root
3.copy devinfo to img
4.changing Model ID with hex editer
View attachment 5467843
5.save and flash back
6.reboot and enjoy it.
View attachment 5467819
In theory, it should be possible to use “fastboot flash devinfo xxx.img”
But it should be necessary to repackage the img file before .
Please tell me if there is a systemless method , thanks
Click to expand...
Click to collapse
was able to the above but still the Camera Sound option still not appear in the Camera settings
noyalas said:
was able to the above but still the Camera Sound option still not appear in the Camera settings
Click to expand...
Click to collapse
it is now working, thanks @iCassius
iCassius said:
*** Please follow the laws and regulations of the corresponding country or region ***
thanks for @HarryShan
I'm not living in Japan and use other country SIM card always shutter sound.
Pixel 6 Pro has a Model ID GF5KQ for Japan
G8VOU for US
they are same hardware
changing Model ID can control Gcam shutter sound
Model ID storage in /dev/block/by-name/devinfo for pixel 6 and 6 pro
run a adb shell to changing or using terminal
1.shell into phone
2.change to root
3.copy devinfo to img
4.changing Model ID with hex editer
View attachment 5467843
5.save and flash back
6.reboot and enjoy it.
View attachment 5467819
In theory, it should be possible to use “fastboot flash devinfo xxx.img”
But it should be necessary to repackage the img file before .
Please tell me if there is a systemless method , thanks
Click to expand...
Click to collapse
I tried this method on my 6 pro and it's stuck in a bootloop! can anyone help me?
I tried to reinstall the stock rom again but fastboot is as far as I can get. I can't boot into fastbootd to complete the flashing process.
I still have the original devinfo.img and I don't know how to restore it using fastboot. I tried fastboot flash devinfo devinfo.img but I get file size error.
please help
unbricked my phone.
you should have added "bs=8192 count=1" to your dd command.
now because of your half baked guideeven though I unbricked, wifi isn't working.
mohamed.sakhiri said:
unbricked my phone.
you should have added "bs=8192 count=1" to your dd command.
now because of your half baked guideeven though I unbricked, wifi isn't working.
Click to expand...
Click to collapse
Try the Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own). You may have to choose the option to Force Flash All Partitions, which will also wipe your phone.
roirraW edor ehT said:
Try the Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own). You may have to choose the option to Force Flash All Partitions, which will also wipe your phone.
Click to expand...
Click to collapse
nope that did not work, unfortunately.
mohamed.sakhiri said:
nope that did not work, unfortunately.
Click to expand...
Click to collapse
I would pursue the warranty possibility ASAP, if you can. Then, if they let you RMA it, use the flash tool once more, but this time check the box for both Wipe and for Re-lock the Bootloader.
I apologize for the bad news.
roirraW edor ehT said:
I would pursue the warranty possibility ASAP, if you can. Then, if they let you RMA it, use the flash tool once more, but this time check the box for both Wipe and for Re-lock the Bootloader.
I apologize for the bad news.
Click to expand...
Click to collapse
Unfortunately I can't send it back even if they agree, custom fees are insane here.
Do you own a pixel 6 pro? If so, can you please send me a backup of your devinfo partition?
mohamed.sakhiri said:
Unfortunately I can't send it back even if they agree, custom fees are insane here.
Do you own a pixel 6 pro? If so, can you please send me a backup of your devinfo partition?
Click to expand...
Click to collapse
Right, I saw your post in the other thread. Like I said, you should stick to a single thread - now you've got three threads going about the subject.
No, I don't own a Pixel 6 Pro, my wife and I traded ours in, which Google received today.
mohamed.sakhiri said:
I tried this method on my 6 pro and it's stuck in a bootloop! can anyone help me?
I tried to reinstall the stock rom again but fastboot is as far as I can get. I can't boot into fastbootd to complete the flashing process.
I still have the original devinfo.img and I don't know how to restore it using fastboot. I tried fastboot flash devinfo devinfo.img but I get file size error.
please help
Click to expand...
Click to collapse
This partition is record of hardware information
So I think you did something wrong while modifying this partition
You can post the information about the failure when you flash the system partition
To facilitate better analysis of the reasons
In addition, if you stay on the google logo interface all the time,
you can check whether the computer system device currently has an adb or fastboot connection to confirm where the device boot stays.
iCassius said:
This partition is record of hardware information
So I think you did something wrong while modifying this partition
You can post the information about the failure when you flash the system partition
To facilitate better analysis of the reasons
In addition, if you stay on the google logo interface all the time,
you can check whether the computer system device currently has an adb or fastboot connection to confirm where the device boot stays.
Click to expand...
Click to collapse
It is solved by now.
[SOLVED] Bricked my Pixel 6 Pro
Hello, Today I messed up, I tried to change my Pixel 6 Pro's model from US version to global, so I edit the devinfo.img and pushed it successfully using adb, the same steps shared in some articles on xda. Now it won't boot again, it's stuck on...
forum.xda-developers.com
This is the support thread of PixelFlasher
(PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features).
Note: This thread is meant for issues and problems faced in Google Pixel 6 Pro devices, generic issues that are device agnostic should be discussed in the main thread.
For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.
Troubleshooting:
If you need support or assistance, the best way to get is by generating a support file from within PixelFlasher.
You can hit that big Support button on the main screen, or select it from the Help menu.
The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.
Placeholder
Placeholder
this is an interesting project.
can you add a way to flash all partition/boot slots easily for new users? I think that can resolve a ton of issues. (the flash tool doesn't do this, just reinstalls some of the images like bootloader and raidio).
Alekos said:
this is an interesting project.
can you add a way to flash all partition/boot slots easily for new users? I think that can resolve a ton of issues. (the flash tool doesn't do this, just reinstalls some of the images like bootloader and raidio).
Click to expand...
Click to collapse
There's some discussion ongoing in the main thread of PixelFlasher about advanced options.
Feel free to chime in there, as this point is not specific to Pixel 6 Pro and would help all devices if it is discussed in the main thread.
📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.
DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...
forum.xda-developers.com
badabing2003 said:
There's some discussion ongoing in the main thread of PixelFlasher about advanced options.
Feel free to chime in there, as this point is not specific to Pixel 6 Pro and would help all devices if it is discussed in the main thread.
📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.
DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...
forum.xda-developers.com
Click to expand...
Click to collapse
Done, check the new release.
New Release:
March 24, 2022 v1.2.0.1-alpha release.
Added Advanced Configuration menu which unlocks advanced features such as:
- Flashing to both slots
- Disabling Verity
- Disabling Verification
- (More features to come)
The UI will now display the chosen Android Platform Tool's version.
Added an option to toggle verbose console output (help troubleshooting, more verbosity to come).
Stability fixes.
New Release: (See full details here on xda or here at github)
April 03, 2022 v2.0.0.0-pre release.
Major refactoring
Added Advanced (Expert) mode UI.
Basic mode keeps UI simple and hides expert features.
Support for setting active slot.
Reboot options (recovery, system, bootloader)
Moved custom ROM options to expert mode.
Added custom flashing to expert mode, can now flash to live (temporary root), or custom flash any image to any partition.
Moved flashing to both slots, disabling verity / verification to expert mode.
Many other improvements, validations and checks.
Updated documentation.
Update:
Version 2.0.1 which includes a hotfix for issue reported here.
Flawless one click update. Thanks. This going to be my default update tool.
Just used it to flash April update on my 6 Pro. Worked like a charm. Thanks.
Also used this to get to April from February and it was one of the simplest things I've ever had to do. Excellent work on this.
It keeps saying magisk is not on my phone, but it is, and it's not hidden.
According to the logs it thinks my phone is not rooted, but it is.
Edit: Followed the instructions and it updated perfectly though, just weird it thinks my phone is not rooted. Awesome app my friend, will be using this as long as it works!
Zach Alt said:
It keeps saying magisk is not on my phone, but it is, and it's not hidden.
According to the logs it thinks my phone is not rooted, but it is.
Edit: Followed the instructions and it updated perfectly though, just weird it thinks my phone is not rooted. Awesome app my friend, will be using this as long as it works!
Click to expand...
Click to collapse
Thanks for bringing this up, I'll add it to the guide,
Shell would need root permission for it to be able to do detect and use magisk.
{
"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"
}
badabing2003 said:
Thanks for bringing this up, I'll add it to the guide,
Shell would need root permission for it to be able to do detect and use magisk.
View attachment 5581317
Click to expand...
Click to collapse
Awesome, I'll enable it for next month's update. Again, thanks for this software, it's awesome.
I toggled root access for shell and now my phone shows as rooted in Pixel Flasher.
New Release:
April 06, 2022 v2.1.0 release
Setup dedicated profile directory.
Put logs in the profile directory and maintain log history.
Plumbing for Linux support (just the flashing part is left to do).
Plumbing for new workflow.
Bugfix to handle name conflict in ROM filename.
Various minor improvements.
Update documentation.
Forgot to mention this but I was running this last night and did a dry run before the real thing, it progressed but my cable was apparently faulty so it lost connection mid way (good thing I did dry run and thank you for having it). Anyway, when it lost connection it caused the app to lock up. I closed it in task manager but the files were stuck in use and I had to find and kill the processes still open to free them up before I could start again.
Suggestion: add a check for and close of any existing processes related to the pixel flasher program if it gets reopened to avoid things being stuck in use. I work in IT so I was fine poking around to kill those processes but not everyone will be.
If you can't, maybe just add the list of processes to the OP so people can kill them on their own.
wgrant said:
Forgot to mention this but I was running this last night and did a dry run before the real thing, it progressed but my cable was apparently faulty so it lost connection mid way (good thing I did dry run and thank you for having it). Anyway, when it lost connection it caused the app to lock up. I closed it in task manager but the files were stuck in use and I had to find and kill the processes still open to free them up before I could start again.
Suggestion: add a check for and close of any existing processes related to the pixel flasher program if it gets reopened to avoid things being stuck in use. I work in IT so I was fine poking around to kill those processes but not everyone will be.
If you can't, maybe just add the list of processes to the OP so people can kill them on their own.
Click to expand...
Click to collapse
The reason that happened is because PixelFlasher is running flash-all equivalent script, which has fastboot commands in it, most fastboot commands (aside from informational ones) are blocking, i.e. it waits for device.
Because your cable was faulty and your device was not appearing connected, it got blocked waiting for it.
It's a good idea to display a message and the PID of the spawned process, the user can kill it if they wish.
I really don't want to intervene with that spawned process as it is the one flashing your phone, any glitch in there and it could mess up the phone.
badabing2003 said:
The reason that happened is because PixelFlasher is running flash-all equivalent script, which has fastboot commands in it, most fastboot commands (aside from informational ones) are blocking, i.e. it waits for device.
Because your cable was faulty and your device was not appearing connected, it got blocked waiting for it.
It's a good idea to display a message and the PID of the spawned process, the user can kill it if they wish.
I really don't want to intervene with that spawned process as it is the one flashing your phone, any glitch in there and it could mess up the phone.
Click to expand...
Click to collapse
That's a good idea as well, better to not force a closure of the process and instead inform then give the user the information necessary to close it themselves. It was definitely the fastboot process that was holding the files. Once I killed that it was fine for me to proceed. Providing a pop up with the PID or even just the process name (unless the PID is always the same) and instructions in that pop up would certainly help someone get out of a jam without needing to reboot the computer.
I've done some stuff like this project with batch but this blows that completely out of the water. Excellent work, you should be proud of what you've given to the community.
can I also root my Pixel with that?