If your Mi Box won't reboot with July update... - Android Stick & Console AMLogic based Computers

Someone was nice enough to find the file:
https://www.reddit.com/r/AndroidTV/...july_update_androidtv_601_google_source_link/
• Download
• Rename to update.zip
• Save to USB Key
• Follow these steps:
https://beebom.com/how-update-mi-box-android-nougat/
*disregard that it is for Nougat and don't use the update.zip from that site. (unless you want Nougat - beta)
Worked for me.

vission1 said:
Someone was nice enough to find the file:
https://www.reddit.com/r/AndroidTV/...july_update_androidtv_601_google_source_link/
• Download
• Rename to update.zip
• Save to USB Key
• Follow these steps:
https://beebom.com/how-update-mi-box-android-nougat/
*disregard that it is for Nougat and don't use the update.zip from that site. (unless you want Nougat - beta)
Worked for me.
Click to expand...
Click to collapse
You're quick on the trigger. I just made that post on reddit less than 30 minutes ago.
Lucky I have a rooted box and could grab the d/l link before box rebooted!!

vission1 said:
Someone was nice enough to find the file:
• Download
• Rename to update.zip
• Save to USB Key
• Follow these steps:
*disregard that it is for Nougat and don't use the update.zip from that site. (unless you want Nougat - beta)
Worked for me.
Click to expand...
Click to collapse
The google link seems not to be working. Got any other links please

dayaki said:
The google link seems not to be working. Got any other links please
Click to expand...
Click to collapse
Works fine

Related

Any big-hearted developer ?

Is there any developer, who could make just 3 flash-able zips for
X10_3.0.1.G.0.75_CUST-IN GENERIC_1237-0692 i.e. stock firmware.
1. Screenshot.
2. Skip track via volume buttons.
3. Reboot
Please, please, please. OK, for screenshot i can download from playstore but
can't for "skipping tracks"
Waiting for my grant
Btw, I did flash commonly available flash-able screen shot zip but it froze/hang/boot-looped my stock rom.
pathaniya said:
Is there any developer, who could make just 3 flash-able zips for
X10_3.0.1.G.0.75_CUST-IN GENERIC_1237-0692 i.e. stock firmware.
1. Screenshot.
2. Skip track via volume buttons.
3. Reboot
Please, please, please. OK, for screenshot i can download from playstore but
can't for "skipping tracks"
Waiting for my grant
Btw, I did flash commonly available flash-able screen shot zip but it froze/hang/boot-looped my stock rom.
Click to expand...
Click to collapse
look at my thread all that and many more btw in one zip xrecovery doomkernel needed http://forum.xda-developers.com/showthread.php?t=2108109 look here
This is how i searched,
Thread Tools>Show Printable version then 'Show 50 post(s) from this thread on one page', then pressed Ctrl+F and searched with '.com', asumming that there would a link for the zip file, which holds the key to my happiness (refer to OP) but couldn't find any link or zip file. Yes saw lot of custom rom link, but i don't want a ROM.
All I want is three features integrated into the the Stock ROM.
Btw, your Miui Rom 2.3.3 look enticing might try it, but could you direct into the right direction?
Thanks And regards
sorry double post
pathaniya said:
Is there any developer, who could make just 3 flash-able zips for
X10_3.0.1.G.0.75_CUST-IN GENERIC_1237-0692 i.e. stock firmware.
1. Screenshot.
2. Skip track via volume buttons.
3. Reboot
Please, please, please. OK, for screenshot i can download from playstore but
can't for "skipping tracks"
Waiting for my grant
Btw, I did flash commonly available flash-able screen shot zip but it froze/hang/boot-looped my stock rom.
Click to expand...
Click to collapse
Hello,
For the screenshot option I made a tuto in "dev" thread so it's possible to add it.
For the reboot option there are some great tuto on xda (I used them to make screenshot option )
For skipping tracks, I dont't know much about it but I think it can be found
pathaniya said:
Is there any developer, who could make just 3 flash-able zips for
X10_3.0.1.G.0.75_CUST-IN GENERIC_1237-0692 i.e. stock firmware.
1. Screenshot.
2. Skip track via volume buttons.
3. Reboot
Please, please, please. OK, for screenshot i can download from playstore but
can't for "skipping tracks"
Waiting for my grant
Btw, I did flash commonly available flash-able screen shot zip but it froze/hang/boot-looped my stock rom.
Click to expand...
Click to collapse
Hello bro,
try to download the whole rom (zip) from THIS POST.
For above item(s) :
For screenshot option , you need below file from inside zip :
- Framework-res.apk (from : system/framework)
- Andorid.policy.jar (from : system/framework)
- Screenshot.apk (from : system/app)
- screenshot (from : system/bin)
For Volume key rocker and Reboot Option : You need below file from inside zip :
- Framework-res.apk (from : system/framework)
- framework.jar (from : system/framework)
- Andorid.policy.jar (from : system/framework)
See permission set for these files above in update-script file (inside zip's sign).
FYI
Regards
EDIT :
I had removed Sony's sign on above rom to port NXT Lockscreen, so you have to resign it again.
Go here for better one :
http://forum.xda-developers.com/showthread.php?t=2231545

[GUIDE] How to use microG with our mi5 (Custom Nougat ROM)

Installation guide of microG services in three ways:​-On ROMs with signature spoofing option.
-On Deodexed ROMs without signature spoofing option.
-On Odexed ROMs without signature spoofing option.​
I'm using win10 all the time here, and this guide is for Nougat ROMs only.
Hi everybody! Two months ago I discovered the awesome world of microG, a life without original google play services, without any of my data on google and with better battery life (we all know how google services drains battery). For more general information, refere please to these threads and forums:
https://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616
https://microg.org/
https://shadow53.com/no-gapps/
Today I present you my guide (none of this work is done by me, I'm just showing the way I install these services) to install microG features.
The first thing we need is a ROM without gapps included. Then is needed to know if it supports signature spoofing out-of-the-box, you can see if the ROM is present on this list: https://forum.xda-developers.com/android/general/index-list-custom-roms-offering-t3557047 or ask developer in his own thread. If it supports it, you can directly go to the instructions num 1) . If else, you need to know if the ROM is odexed or deodexed, for this, you can ask on the dev thread or unpack the rom yourself.
How to unpack the ROM:
You can unpack it with 7-zip and then decompress it with this tool: https://forum.xda-developers.com/android/software-hacking/tool-tool-unpack-repack-dat-img-v2-0-t3284806. You must place the system.transfer.list and the system.new.dat you'll find in the decompressed folder in the Input_dat folder of the tool given, then open the tool with usage permission and mark option 1, then wait until process is finished and you'll have the output in the System_unpack folder.
Then you only need to go to the /system_/framework/ folder and see if there's any arm, arm64, folder with .oat files inside. If there isn't, congratulations, your rom is deodexed and you can follow path 2). If there is any of these folders mentioned with .oat files, your rom is odexed, and you'll need to follow path 3).
Note: on all this process we will be using the @Shadow53 files placed on https://shadow53.com/no-gapps/downloads/, I personally use the "microG with playstore" and the "calendar and contacts" flashable zips (I've modified the calendar and contacts zip because of some issues with sync that i don't know if were solved, I let the modified flashable zip later in this post) please, before asking or complaining, read his page fully, his work is awesome.
1) ROMs with signature spoofing option:
This is the easy way. We only need to install the clean ROM and then flash the microG and the sync packages we've donwnloaded before. Once booted, we only need to active signature spoofing option and check microG Self-Check and we are ready to go. In order to install backends for network location, please, refer to proper threads.
2) Deodexed ROMs without signature spoofing option.
Here we will follow the steps as if we had a signature spoofing option (as the previous paragraph) but obiously we won't active nothing when booted and we will use this tool: https://forum.xda-developers.com/android/development/tingle-fork-needle-t3438764 (please, read carefully before asking) if your ROM is deodexed and you follow the steps carefully, you'll have patched the ROM in a few minutes. Then you just need to reboot and check with microG Self-Check.
3) On Odexed ROMs without signature spoofing option.
This is my "original" way, as nobody explained fully how to do it. Here, you need to deodex the framework folder and then flash the rom with the tingle patch already applied. Let's begin.
First, you need to get the /system_/framework and the build.prop you unpacked when checking if the rom was or not odexed. Then you need to deodex it by using this tool https://forum.xda-developers.com/android/software-hacking/tooll-03-12-fulmics-deodexer-1-0-t3512081 (I have to say sometimes it only works for me the 1.1 version) it's easy, you'll need to download the tool and the backsmali, smali 2.2 or later (already compiled in .jar, I let them later in this thread) and run it.
Once you have the framework deodexed (erase the arm, arm65 and oat folder if there is any left) you just need to get the framework.jar and patch it with tingle (option 2 in the script, the patched file will be in the output folder), then replace the patched framework in the deodexed framework folder.
Now you just need to pack it in a flashable zip that must erase the current framework folder of your ROM and then place the one you deodexed, for this, I let you all a flashable zip I made modifying the one the ZIPme app made. Yo must unpack it and replace the framework folder in "system" with the deodexed one with the patched file and repack it.
Then you just need to flash the clean ROM and afte that the framework-replacer.zip and all microG flashable zips you need, once booted you can directly check microG and you'll se it is already patched.
Suggestions are welcome on this guide!
Many thanks to all devs and people made all this possible:
Marvin for microG.
Shadow53 for his guide and flashable zips.
ale5000 for tingle.
xpirt for fulmics deodexer.
Kritsada Chaitan for his unpacking tool.
Primokorn for his signature spoofing support list.
JRummy Apps for ZIPme.
kevinkvothe (I gess)
Anyone else feeling he/she should be on this list, please, tell me.​
Downloads.
https://mega.nz/#F!id1jlZoS!6Su8IJeGQnYO_3olQmQMTg
Reserved
Pole
Thanks for the concise, resource-rich guide. I've been trying to patch an odexed ROM for the past few weeks, and never thought to try and flash it with the patched framework.jar. Cheers! I'm going to give this a try first thing tomorrow!
Thx for this guide, worked for me...
Best regards
@kevinkvothe
Hi,
have you tried my Google Sync Add-on?
It would be nice to know if it is working for everyone.
That was one hell of a long ride but I got the signature spoofing working.. Thanks a lot.
I got the Error [RH-01] with play store but after rebooting it was fixed somehow.
ikzouhetnietweten said:
That was one hell of a long ride but I got the signature spoofing working.. Thanks a lot.
But my Play Store aint working! it says Error [RH-01] , I tried everything from deleting cache, data, enabled google device registration in micro settings, enabled google cloud messaging.. etc etc Everything is checked in Self checked.
Click to expand...
Click to collapse
Enable "Google device registration" in micro settings, then clear data of Play Store, termintate it and remove it from recent apps.
Then run it again.
ale5000 said:
@kevinkvothe
Hi,
have you tried my Google Sync Add-on?
It would be nice to know if it is working for everyone.
Click to expand...
Click to collapse
I tested it once, when I started to learn about microG and it didn't work, but I'm not sure all was working and if I had signature spoofing support so... I'll test it when possible.
Hi all,
I'm using RR + Magisk + NanoMod which can achieve this faster. However, I was dumbfounded when I couldnt get sync properly to work, however flashing the google sync adapter work. I urge anyone who want to use microG to use nanomod version, as it is simpler. you only have to flash via twrp and let it sit.
ale5000 said:
@kevinkvothe
Hi,
have you tried my Google Sync Add-on?
It would be nice to know if it is working for everyone.
Click to expand...
Click to collapse
thank you
xiiihyou13 said:
Hi all,
I'm using RR + Magisk + NanoMod which can achieve this faster. However, I was dumbfounded when I couldnt get sync properly to work, however flashing the google sync adapter work. I urge anyone who want to use microG to use nanomod version, as it is simpler. you only have to flash via twrp and let it sit.
thank you
Click to expand...
Click to collapse
It depends what you mean, both are flashable zip so as simplicity should be the same.
kevinkvothe said:
I tested it once, when I started to learn about microG and it didn't work, but I'm not sure all was working and if I had signature spoofing support so... I'll test it when possible.
Click to expand...
Click to collapse
In the latest version I have fixed permission problems, so it will most likely work out of the box.
xiiihyou13 said:
Hi all,
I'm using RR + Magisk + NanoMod which can achieve this faster. However, I was dumbfounded when I couldnt get sync properly to work, however flashing the google sync adapter work. I urge anyone who want to use microG to use nanomod version, as it is simpler. you only have to flash via twrp and let it sit
thank you
Click to expand...
Click to collapse
But unfortunately Nanomod Patcher does not work on odexed and deodexd ROMs, I don't know yet if mine is odexed or deodexed but will have to check It's the unofficial LinageOS 14.1 for lt03lte - the official nightly does unfortunately not detect my external SD Card!
Juat FIY, now that nougat supports xposed, this is much easier when using Fakegapps module [emoji106]
Lähetetty minun MI 5 laitteesta Tapatalkilla
Seems like noone mentioned this but microG have own fork of LineageOS with already build in microG services.
https://lineage.microg.org/

ALL IN ONE ZIP[HwIntelligent, CallRecord, HwParent, Autorun, HwMusicCutter, HpPlugin]

This is the all in one zip file with some extra functionality for honor 6x.
The file will give you some useful utilities like hw intelligent , call record , autorun, hp plugin, music with cutter, parent control.
REQUIREMENT:
1. ROOT , TWRP RECOVERY.
2. ANY ROOT EXPLORER.
STEPS:
1. OPEN ANY ROOT EXPLORER AND NAVIGATE TO SYSTEM/PRIV-APP/GOOGLE PACKAGE INSTALLER
2. DELETE THE FOLDER GOOGLE PACKAGE INSTALLER.
3. REBOOT TO RECOVERY , FLASH THE DOWNLOADED ZIP .
THATS IT , YOU HAVE DONE IT.
Download links below :
http://gestyy.com/wrLHXH
screenshots
http://gestyy.com/wrLGLz
Thanks
XDA:DevDB Information
EXTRA UTILITIES FOR HONOR 6X, Tool/Utility for the Honor 6X
Contributors
Khan ubaid
Version Information
Status: Testing
Created 2017-11-05
Last Updated 2017-11-05
It doesn't work on 6X BLN21, bootloop on start after flashed the zip !
MiPiMok said:
It doesn't work on 6X BLN21, bootloop on start after flashed the zip !
Click to expand...
Click to collapse
You can go for manual setup ,
1. Extract the zip file, you will get HwCallrecord, HwParent, HwIntelligent under system/app
and PackageInnstaller, HwMediacenter, HpPlugin under system/priv-app.
2. Copy these files in corresponding directory by using any root explorer under root/system/app and root/ystem/priv-app.
3. If you want package installer with autorun and backgroung run facility, you have to delete the GooglePackageInstaller under /root/system/priv-app/GooglePackageInstaller.
4.Give permission to the apk files as well as folders, How? go through screenshots.
5. Reboot, Enjoy
Any queries, you can ask....
Remember to give permission to every folders and files you place or replace...
MiPiMok said:
It doesn't work on 6X BLN21, bootloop on start after flashed the zip !
Click to expand...
Click to collapse
Permission to odex file also...
http://q.gs/Dx2KW
Done ! And it works, thanks.
Welcome buddy...
Hi, I've got problem with HwParent and HwIntelligent, how install them if they are not installed in the original ROM...because I can't install them normally...package corrupt it says me....
you cannot install them normally, they have to be placed in the system partition and changing the permission as i have already given the screenshots...
Thank you
Hey,
thank you for explaining the manual way - that helped me a lot and also fixed a second problem i have had.
The problem was, that after the update my FM Radio was gone.
I found the app here but i cant push files by ADB as root. So i just installed doing the same way:
i copied the apk to an own folder to /system/app/ , set permissions, rebbooted and it worked perfect.
all your apps are working too.
Except the parental controll - i didnt install it because nothing planned yet... ^^
starkeeper2018 said:
Hey,
thank you for explaining the manual way - that helped me a lot and also fixed a second problem i have had.
The problem was, that after the update my FM Radio was gone.
I found the app here but i cant push files by ADB as root. So i just installed doing the same way:
i copied the apk to an own folder to /system/app/ , set permissions, rebbooted and it worked perfect.
all your apps are working too.
Except the parental controll - i didnt install it because nothing planned yet... ^^
Click to expand...
Click to collapse
Thats good.... keep it up,,
and about parent control should work too, after installing by the given procedure is done,,, you will find it under setting/additional setting /student mode
Khan ubaid said:
you cannot install them normally, they have to be placed in the system partition and changing the permission as i have already given the screenshots...
Click to expand...
Click to collapse
OK sorry, it was badly asked... I did it as you explained and I succeed to install them but I can't find where to activate them... Now, I find the parent control in the advanced settings with the "student app" with the last post and it works but where I can find or activate the "intelligent" smart assistance app ? And about the package installer, I pasted it in the priv-app file but what happens now ?
MiPiMok said:
OK sorry, it was badly asked... I did it as you explained and I succeed to install them but I can't find where to activate them... Now, I find the parent control in the advanced settings with the "student app" with the last post and it works but where I can find or activate the "intelligent" smart assistance app ? And about the package installer, I pasted it in the priv-app file but what happens now ?
Click to expand...
Click to collapse
After you paste the package installer and gave permission , you have to delete( or cut to make a copy of ) google package installer,,, it will be activated when you remove google package installer folder in the same directory
link dead
Link dead need mirror for the same
.
does anybody have the apps from the link?
can someone reupload it?

[Treble][RIL] Qualcomm device and in-call audio not working? Check this out

Hello,
After a few weeks of having Project Treble GISs running in my Razer Phone, I had one big issue to solve, and that was the in-call audio. I stumbled upon a few people in #phh-treble Telegram group that suggested me to use ZUK (MSM8996) patches to get it to work, but unfortunately they weren't fully working... because of a missing apk from my device's stock image (which I didn't know until 2 or 3 days ago). Starting from there, I worked on it quite a lot of time until almost giving up, to then finally getting it to work just now.
Steps I followed:
1. Pull from your device's stock image the following files (they may not be in /system and instead be located in /vendor, depends on your OEM's Treble implementation)
- app/QtiSystemService
- app/QtiTelephonyService
- framework/qcrilhook.jar
- framework/QtiTelephonyServicelibrary.jar
- etc/permissions/privapp-permissions-qti.xml
- etc/permissions/qcrilhook.xml
- etc/permissions/qti_permissions.xml
- etc/permissions/telephonyservice.xml
- priv-app/qcrilmsgtunnel
2. Fortunately, those APKs will contain a .dex inside of them, but in case they didn't, you'd need to first deodex your rom based on the vdex files located in /system/framework/oat. However, the jars will definitely and for sure won't have the inner .dex classes. You'll need to use a tool such as vdexExtractor to get the final .dex files for qcrilhook.jar and QtiTelephonyServicelibrary.jar. Then, open the metioned .jar's as zip files, embed the .dex inside and done.
3. The tricky part comes now: With a tool such as APKTool, decompile the qcrilmsgtunnel.apk file you've extracted from your Stock ROM image. I'm not going to go throught the steps to perform that. Now, open up the AndroidManifest.xml and find the line:
Code:
<uses-library android:name="[email protected]" />
and replace it with
Code:
<uses-library android:name="[email protected]" android:required="false" />
Recompile the apk and, without signing it yet, put it in a safe place.
4. Open up the other APKs and remove the META-INF folders from inside of them (the signatures). Now, download a copy of SignAPK and sign every apk (including the ones we've removed the signature from, plus the modded version of qcrilmsgtunnel.apk with the platform keys (platform.*) from Android AOSP.
You can do so by using the following command:
Code:
java -jar /path/to/signapk.jar /path/to/platform.x509.pem /path/to/platform.pk8 NameOfTheApk.apk NameOfTheApk_signed.apk
5. Open up the files qcrilhook.xml and telephonyservice.xml and ensure that the file="" path points to /vendor. i.e:
Code:
file="/vendor/framework/qcrilhook.jar"
6. Move the files to your device according to this table:
- app/QtiSystemService -> /system_root/system/app/QtiSystemService (replace)
- app/QtiTelephonyService -> /system_root/system/app/QtiTelephonyService (replace)
- framework/qcrilhook.jar -> /vendor/framework/qcrilhook.jar (delete the original file wherever you found it)
- framework/QtiTelephonyServicelibrary.jar -> /vendor/framework/QtiTelephonyServicelibrary.jar (delete the original file wherever you found it)
- etc/permissions/privapp-permissions-qti.xml -> /system_root/system/etc/permissions/privapp-permissions-qti.xml (delete the original file wherever you found it)
- etc/permissions/qcrilhook.xml -> /system_root/system/etc/permissions/qcrilhook.xml (delete the original file wherever you found it)
- etc/permissions/qti_permissions.xml -> /system_root/system/etc/permissions/qti_permissions.xml (delete the original file wherever you found it)
- etc/permissions/telephonyservice.xml -> /system_root/system/etc/permissions/telephonyservice.xml (delete the original file wherever you found it)
- priv-app/qcrilmsgtunnel -> /system_root/system/priv-app/qcrilmsgtunnel (replace)
Reboot and profit.
Nice job now maybe the devs can add it to their rom.a little lengthy and out of my league to try
Of course this is not a final solution @gillim74.
But if the mentioned Qcomm apks or jar libs aren't present in the device's vendor partition (which I bet they aren't), the steps of decompiling them, and placing them into vendor is still needed, even for GSI's that include the patch.
What ZUK patch? I got a ZUK Z2 with treble rom and calling is not working.
Where can i get the patches?
andreas951207 said:
What ZUK patch? I got a ZUK Z2 with treble rom and calling is not working.
Where can i get the patches?
Click to expand...
Click to collapse
https://github.com/zuk-devs/android_vendor_zuk/commit/9ab51560c8d5632a08bdb949bd433909b8db5752
great explanation
linuxct said:
Hello,
After a few weeks of having Project Treble GISs running in my Razer Phone, I had one big issue to solve, and that was the in-call audio. I stumbled upon a few people in #phh-treble Telegram group that suggested me to use ZUK (MSM8996) patches to get it to work, but unfortunately they weren't fully working... because of a missing apk from my device's stock image (which I didn't know until 2 or 3 days ago). Starting from there, I worked on it quite a lot of time until almost giving up, to then finally getting it to work just now.
Steps I followed:
1. Pull from your device's stock image the following files (they may not be in /system and instead be located in /vendor, depends on your OEM's Treble implementation)
- app/QtiSystemService
- app/QtiTelephonyService
- framework/qcrilhook.jar
- framework/QtiTelephonyServicelibrary.jar
- etc/permissions/privapp-permissions-qti.xml
- etc/permissions/qcrilhook.xml
- etc/permissions/qti_permissions.xml
- etc/permissions/telephonyservice.xml
- priv-app/qcrilmsgtunnel
2. Fortunately, those APKs will contain a .dex inside of them, but in case they didn't, you'd need to first deodex your rom based on the vdex files located in /system/framework/oat. However, the jars will definitely and for sure won't have the inner .dex classes. You'll need to use a tool such as vdexExtractor to get the final .dex files for qcrilhook.jar and QtiTelephonyServicelibrary.jar. Then, open the metioned .jar's as zip files, embed the .dex inside and done.
3. The tricky part comes now: With a tool such as APKTool, decompile the qcrilmsgtunnel.apk file you've extracted from your Stock ROM image. I'm not going to go throught the steps to perform that. Now, open up the AndroidManifest.xml and find the line:
Code:
<uses-library android:name="[email protected]" />
and replace it with
Code:
<uses-library android:name="[email protected]" android:required="false" />
Recompile the apk and, without signing it yet, put it in a safe place.
4. Open up the other APKs and remove the META-INF folders from inside of them (the signatures). Now, download a copy of SignAPK and sign every apk (including the ones we've removed the signature from, plus the modded version of qcrilmsgtunnel.apk with the platform keys (platform.*) from Android AOSP.
You can do so by using the following command:
Code:
java -jar /path/to/signapk.jar /path/to/platform.x509.pem /path/to/platform.pk8 NameOfTheApk.apk NameOfTheApk_signed.apk
5. Open up the files qcrilhook.xml and telephonyservice.xml and ensure that the file="" path points to /vendor. i.e:
Code:
file="/vendor/framework/qcrilhook.jar"
6. Move the files to your device according to this table:
- app/QtiSystemService -> /system_root/system/app/QtiSystemService (replace)
- app/QtiTelephonyService -> /system_root/system/app/QtiTelephonyService (replace)
- framework/qcrilhook.jar -> /vendor/framework/qcrilhook.jar (delete the original file wherever you found it)
- framework/QtiTelephonyServicelibrary.jar -> /vendor/framework/QtiTelephonyServicelibrary.jar (delete the original file wherever you found it)
- etc/permissions/privapp-permissions-qti.xml -> /system_root/system/etc/permissions/privapp-permissions-qti.xml (delete the original file wherever you found it)
- etc/permissions/qcrilhook.xml -> /system_root/system/etc/permissions/qcrilhook.xml (delete the original file wherever you found it)
- etc/permissions/qti_permissions.xml -> /system_root/system/etc/permissions/qti_permissions.xml (delete the original file wherever you found it)
- etc/permissions/telephonyservice.xml -> /system_root/system/etc/permissions/telephonyservice.xml (delete the original file wherever you found it)
- priv-app/qcrilmsgtunnel -> /system_root/system/priv-app/qcrilmsgtunnel (replace)
Reboot and profit.
Click to expand...
Click to collapse
Hi
It seems to be a great work.
For me in resurrection remix 8.1 in call audio is working, but music sound over Bluetooth isn't working. Do you've got any ideas?
Please could you share your modified files for in call fix?
Thanks in advance
Thread dead?
No more updates?
Laptapper said:
No more updates?
Click to expand...
Click to collapse
This has already been implemented into phh's gsi repo. I have no clue what you expect from this thread anymore.
linuxct said:
This has already been implemented into phh's gsi repo. I have no clue what you expect from this thread anymore.
Click to expand...
Click to collapse
Thanks, but even as before there are problems with Bluetooth in call and/or audio as before on a couple of devices....
Does somebody know if this fix has been included in some ROM? I don't know which ROM to try as GSI on my Razer Phone
guillermohs9 said:
Does somebody know if this fix has been included in some ROM? I don't know which ROM to try as GSI on my Razer Phone
Click to expand...
Click to collapse
I said it literally 2 posts ago.
linuxct said:
This has already been implemented into phh's gsi repo. I have no clue what you expect from this thread anymore.
Click to expand...
Click to collapse
IT IS implemented in all new, recently built GSIs. Just try any.
linuxct said:
I said it literally 2 posts ago.
IT IS implemented in all new, recently built GSIs. Just try any.
Click to expand...
Click to collapse
damn, my bluetooth calling still doesn't work on any GSI i try.
knives of ice said:
damn, my bluetooth calling still doesn't work on any GSI i try.
Click to expand...
Click to collapse
Yeah bluetooth calling on Qualcomm devices is still a no-go.
There is a bounty for it: https://github.com/phhusson/treble_experimentations/issues/374
phhusson said:
Yeah bluetooth calling on Qualcomm devices is still a no-go.
There is a bounty for it: https://github.com/phhusson/treble_experimentations/issues/374
Click to expand...
Click to collapse
ok, I'm glad I'm not alone. AndroPlus posted in your bounty thread on github as well and he maintains the GSI based build for my device the mi mix 3. for most people bluetooth calling does work with his fix, but for me it does not. i will contribute to the bounty as well.
nice work bro but can you make a video to explain the way?
I have this problem in the Qualcomm j4 core msm8917
So I have a Qualcomm device(SD845 in an AGM X3), in-call audio and bluetooth calling work great but main audio does not work at all. I can force sound to route through the in-call speaker, but not really viable.
Any chance following this guide would help? Are there other files I should include since my issue is not in-app calling.
My device will not boot past v123, so if this has been resolved in newer releases unfortunately I can't install.
I tried building an overlay. I followed the method in the guide from phh as well as from a post on XDA. First few attempts broke boot but when I finally got an overlay build to boot it did not resolve problem.
So, would trying this route be worth a shot?
9.0 otherwise runs flawlessly on this device. Sound and MTP are the only things broken. Fingerprint reader is detected as volume down, but I don't use it anyway. It's very stable.

OP7T Pro MClaren Stock Android 10 T-Mobile (5g)

Only for OP7T PRO MCLAREN EDITION (5G) T-MOBILE​Someone is experiencing issues in android 11 in op7t pro MClaren Edition 5g (T-mobile). If your phone is bricked or you want to downgrade to stock android 10 - please follow the procedure below.....
1. Download the zip from here - op7t pro mclaren 5g - android 10
2. Unzip it.
3. Install qualcom driver from L2 drivers folder (If needed)
4. Run as administrator - MSMdownload Tool v.4 - from hotdogg_13_A.01_210311_repack folder.
5. Log in as other.
6. Power off your device . Hold volume up and down together and connect usb through original usb cable || You will be connected in EDL mode.
7. If com port is connected than start the flash from above left corner.
Tips : If com port is not connected try to power off your device and try again to enter into EDL mode (Do that until com is connected) .
TRY THIS TO DISABLE UPDATE:
adb shell pm disable-user --user 0 com.oneplus.opbackup
This information has been posted in another, much more detailed thread for over a year...
And I wouldn't trust that file either
Suspicious, no?
I have provided the official stock and final android 10 rom. Thank you.
and how do you then disable the updates? from being pushed to you
botN3t said:
and how do you then disable the updates? from being pushed to you
Click to expand...
Click to collapse
Turn on developer options tapping build number constantly and than turn off automatic update there. That's it, enjoy.
Nabil Prodhan said:
Turn on developer options tapping build number constantly and than turn off automatic update there. That's it, enjoy.
Click to expand...
Click to collapse
That doesn't work anymore; that's why everyone is complaining that they are being force updated to OOS11.
I know there's a better way, such as finding the right app and disabling it, but you can block the host it gets the updates from using an adblocker like AdAway. Updates come from
https://android.googleapis.com/packages/ota-api/
so if you block that (add it to your hosts file), you should be good.
starcms said:
That doesn't work anymore; that's why everyone is complaining that they are being force updated to OOS11.
I know there's a better way, such as finding the right app and disabling it, but you can block the host it gets the updates from using an adblocker like AdAway. Updates come from
https://android.googleapis.com/packages/ota-api/
so if you block that (add it to your hosts file), you should be good.
Click to expand...
Click to collapse
I try to add to host but it still download update any another way or web i can use ?
meovoz said:
I try to add to host but it still download update any another way or web i can use ?
Click to expand...
Click to collapse
That's the only simple way I could think of making it impossible to download the update so it would then just fail to update. You sure you have the option on in Magisk settings in addition to whatever app you are using?
Edit: The "correct" way of stopping it would be to find the service which controls updates and kill it. But since I've not an issue with OOS11 (it actually fixed my broken SA 5G and HD call functionality that I lost due to using the NSG app. MSM restore and persist restore couldn't fix it. Never ever install that app on this phone) I never looked into it.
starcms said:
That's the only simple way I could think of making it impossible to download the update so it would then just fail to update. You sure you have the option on in Magisk settings in addition to whatever app you are using?
Click to expand...
Click to collapse
Well if i add https://android.googleapis.com/packages/ota-api/ it still can download but if i add https://android.googleapis.com/ it will not but it also can't signin google acc anymore
meovoz said:
Well if i add https://android.googleapis.com/packages/ota-api/ it still can download but if i add https://android.googleapis.com/ it will not but it also can't signin google acc anymore
Click to expand...
Click to collapse
Omg, are you serious? That's obnoxious. But you should be able to block only the full url successfully. What AdBlock app are u using?
And see my edit in post above
starcms said:
That's the only simple way I could think of making it impossible to download the update so it would then just fail to update. You sure you have the option on in Magisk settings in addition to whatever app you are using?
Edit: The "correct" way of stopping it would be to find the service which controls updates and kill it. But since I've not an issue with OOS11 (it actually fixed my broken SA 5G and HD call functionality that I lost due to using the NSG app. MSM restore and persist restore couldn't fix it. Never ever install that app on this phone) I never looked into it.
Click to expand...
Click to collapse
Is there anyway to view what correct host it connect to
starcms said:
Omg, are you serious? That's obnoxious. But you should be able to block only the full url successfully. What AdBlock app are u using?
And see my edit in post above
Click to expand...
Click to collapse
I use adaway to block it
meovoz said:
I use adaway to block it
Click to expand...
Click to collapse
Yep, that's what I use and was gonna suggest...
Hmm, hehe, try this...
It downloads the OTA package to
/data/ota_package/payload_metadata.bin
If there's a file there, delete it, then create a blank file named payload_metadata.bin and remove all permissions from the file (--- --- --- or 0000) so the system can't overwrite it.
starcms said:
Yep, that's what I use and was gonna suggest...
Hmm, hehe, try this...
It downloads the OTA package to
/data/ota_package/payload_metadata.bin
If there's a file there, delete it, then create a blank file named payload_metadata.bin and remove all permissions from the file (--- --- --- or 0000) so the system can't overwrite it.
Click to expand...
Click to collapse
It only have metadata and payload_properties.txt
meovoz said:
It only have metadata and payload_properties.txt
Click to expand...
Click to collapse
Create a file named payload_metadata.bin and remove all permissions.
But here's a better plan:
Use Magisk to "over-write" systemlessly /system/etc/security/otacerts.zip with a blank file named otacerts.zip
Then the system can't verify the updates and they will fail
starcms said:
Create a file named payload_metadata.bin and remove all permissions.
But here's a better plan:
Use Magisk to "over-write" systemlessly /system/etc/security/otacerts.zip with a blank file named otacerts.zip
Then the system can't verify the updates and they will fail
Click to expand...
Click to collapse
Well i never create a magik module
starcms said:
Create a file named payload_metadata.bin and remove all permissions.
But here's a better plan:
Use Magisk to "over-write" systemlessly /system/etc/security/otacerts.zip with a blank file named otacerts.zip
Then the system can't verify the updates and they will fail
Click to expand...
Click to collapse
Is there anyway to view where it download from i still like the way block with host file
meovoz said:
Is there anyway to view where it download from i still like the way block with host file
Click to expand...
Click to collapse
It downloads a long, "random" named file from https://android.googleapis.com/packages/ota-api/ I told you this already
starcms said:
Create a file named payload_metadata.bin and remove all permissions.
But here's a better plan:
Use Magisk to "over-write" systemlessly /system/etc/security/otacerts.zip with a blank file named otacerts.zip
Then the system can't verify the updates and they will fail
Click to expand...
Click to collapse
I did it let see it can last long
meovoz said:
I did it let see it can last long
Click to expand...
Click to collapse
Let us know!

Categories

Resources