Related
Instructions are below. Just a warning that you'll be modifying system files and so things could go wrong. Be careful, take your time, and back up the files you are replacing along with a nandroid backup. I assume no responsibility if your phone breaks though. This process was developed by someone else and I am posting this on their behalf. I will help where I can, but google will be your best friend
Instructions for Nexus 5 running 5.1 ASOP and Nexus 5 running 5.1.1 Cyanogenmod 12.1
1. You need to be rooted with a custom recovery. I won't go into detail on how to do that since there are plenty of threads on xda-developers about it.
2. Download the correct .zip for you system and install them after booting into recovery
Instructions for Nexus 5 running 5.0.1 ASOP and Nexus 5 running 5.0.2 Cyanogenmod 12
1. You need to be rooted with a custom recovery. I won't go into detail on how to do that since there are plenty of threads on xda-developers about it.
2. Copy the correct 2 files to your phone. One set is for a Nexus 5 running 5.0.1 ASOP and the other is for Nexus 5 running 5.0.2 Cyanogenmod 12 . I plugged my phone into my windows computer and just placed them in the root of the "drive". From the phone's point of view this is /sdcard.
3. You now need to change the permissions of the 2 files. You have to put them in the /system/ folder before you can change permissions. /mnt/sdcard doesn't allow you to change permissions. So copy them to /system/ and change their permissions to 0644 (rw-r--r--). I use root browser for this.
4. Use root browser and move libbluetooth_jni.so to /system/lib/ and move bluetooth.default.so to /system/lib/hw. I would copy the original files to somewhere else first as a backup in case something goes wrong. Double check the permissions on the new files after you move them to their respective locations.
5. Reboot.
6. Installed Kevo and it stopped telling my my phone wasn't supported at this point and everything worked fine.
Please join the KEVO ALPHA Google Group to get the most recent version of the app. I have provided a link to the 1.0.15, but it may be out of date.
KevoForAndroid-1.0.15p.apk
KevoForAndroid-1.0.15p.apk 7.91MB
PLEASE CHECK THE FILES BEFORE YOU COPY THE OVER YOUR FILES, ELSE YOU WILL BREAK YOU BLUETOOTH
-As along as you keep a copy of your original files you can always paste them over the broken ones
ANDROID Stock 5.0.1 ASOP ONLY Files from Download Tab
bluetooth.default.so 2015-02-26 12:36 1.26MB is for 5.0.1 ONLY
libbluetooth_jni.so 2015-02-26 12:36 87.63KB is for 5.0.1 ONLY
ANDROID Stock 5.1 ASOP ONLY File from Download Tab
patched-bluetooth.zip
ANDROID 5.0.2 Cyanogenmod 12 Nightly ONLY Files from Download Tab
bluetooth.default.so 2015-02-26 12:33 1.31MB is CM12 5.0.2 ONLY
libbluetooth_jni.so 2015-02-26 12:33 112.45KB is CM12 5.0.2 ONLY
ANDROID 5.1.1 Cyanogenmod 12.1 ONLY(WILL NOT WORK ON CM12.1 running 5.1.0) File from Download Tab
cm12.1-patched-bluetooth.zip
PROCESS IF YOU DONT HAVE EITHER ONE OF THESE OS:
If neither one of these sets of files work for you. You can make your own. This process will take the whole day and a lot of goggling if you have never used Linux, Source Code, or compiled anything. Remember to always have have all files up to date, use Python 2.7 not Python 3+, have >100 gig of hard drive space, and google the errors when you see them in the terminal window.(you will see a lot if this is your first time). If you are familiar with all this then it will likely take about 2 hours and that is just for downloading the source code and compiling.
1. You need to be rooted with a custom recovery. I won't go into detail on how to do that since there are plenty of threads on xda-developers about it.
2. Get the android source code. Follow the instructions from Google or from your ROM on how to do this. Note that you'll need either a Linux system or an OSX system. (I used an Ubuntu and installed it on a extrahardive, but you can use a virtual machine as well) Also note that getting the source takes quite a while. It took around an hour for me and I have 100Mb down.
3. Edit a file from the hammerhead source. If you followed the instructions on getting the source, you'll find the file at device/lge/hammerhead/bluetooth/. The file is called bdroid_buildcfg.h. Open the file and add "#define BLE_VND_INCLUDED TRUE" (without the quotes) above the line "#define BTM_BLE_ADV......". Save the file.
4. Compile, again following the instructions from Google or from your ROM. Obviously this time will vary depending on the speed of your computer. it can take anywhere from 30 min to 2 hours.
5. Once the compile is done, we need to grab 2 files. out/target/product/hammerhead/system/lib/libbluetooth_jni.so and out/target/product/hammerhead/system/lib/hw/bluetooth.default.so. Save the files in a location you can access easily for copy to your phone.
6. Copy the 2 files to your phone. I plugged my phone into my windows computer and just placed them in the root of the "drive". From the phone's point of view this is /sdcard.
7. You now need to change the permissions of the 2 files. You have to put them in the /system/ folder before you can change permissions. /mnt/sdcard doesn't allow you to change permissions. So copy them to /system/ and change their permissions to 0644 (rw-r--r--). I use root browser for this.
8. se root browser and move libbluetooth_jni.so to /system/lib/ and move bluetooth.default.so to /system/lib/hw. I would copy the original files to somewhere else first as a backup in case something goes wrong. Double check the permissions on the new files after you move them to their respective locations.
9. Reboot. Kevo stopped telling my my phone wasn't supported at this point and everything worked fine.
XDA:DevDB Information
Kevo Working on Nexus 5, App for all devices (see above for details)
Contributors
BSME_SWeedon, scorchsta
Version Information
Status: Beta
Current Beta Version: 1.0.15
Beta Release Date: 2015-02-17
Created 2015-02-26
Last Updated 2015-05-21
Any chance you could rebuild for Android 5.1 for the Nexus 5?
ludwigmace said:
Any chance you could rebuild for Android 5.1 for the Nexus 5?
Click to expand...
Click to collapse
You will find the patched files for 5.1 here: https://groups.google.com/forum/m/#!topic/kevo-alpha/-bOQs8V6KU0
Can this be done for other devices? Like the Note series or others?
johnathankong said:
Can this be done for other devices? Like the Note series or others?
Click to expand...
Click to collapse
Yes if you go to https://groups.google.com/forum/m/#!topic/kevo-alpha/-bOQs8V6KU0 you will see the forums for different device support. I saw Note 4 has support.
Step 8 isn't entirely necessary
Just a heads up if you want to simplify your first post, that part of step "8" is not necessary:
8. Reboot into recovery. Using your recovery's file browser (TWRP has one, not sure about others), move libbluetooth_jni.so to /system/lib/ and move bluetooth.default.so to /system/lib/hw. I would copy the original files to somewhere else first as a backup in case something goes wrong. Double check the permissions on the new files after you move them to their respective locations.
Click to expand...
Click to collapse
In fact, as you already are using Root Browser to change the permissions, you can also use Root Browser to move the 2 files. Worked just fine for me and removes the need for TWRP or another reboot.
CJSnet said:
Just a heads up if you want to simplify your first post, that part of step "8" is not necessary:
In fact, as you already are using Root Browser to change the permissions, you can also use Root Browser to move the 2 files. Worked just fine for me and removes the need for TWRP or another reboot.
Click to expand...
Click to collapse
Thanks I have updated the steps. There is also a zip file to install now, which is a lot easier.
@BSME_SWeedon any chance you can update 6.0 marshmallow files?
@Scorchsta was the one who generated the files, but he has not had a working nexus 5 in a while and I am about to jump ship the the Nexus 5x. I might try to push ASH6.0 to my nexus 5 this weekend and see if I can generate the files. I will post them if I am successful
thank you so much. looking forward to it.
BSME_SWeedon said:
@Scorchsta was the one who generated the files, but he has not had a working nexus 5 in a while and I am about to jump ship the the Nexus 5x. I might try to push ASH6.0 to my nexus 5 this weekend and see if I can generate the files. I will post them if I am successful
Click to expand...
Click to collapse
Thank you thank be very much appreciate
Anyone seen updated libs for the n5 with marshmallow yet? For me its either wait to see if kevo works on new nexus or keep snoozing my marshmallow update on my n5
The latest alpha works with an unmodified library, albeit the unlock is sent through the phone not the deadbolt.
https://groups.google.com/forum/m/#!topic/kevo-alpha/8CoLWU4-29Y
Here's a flashable zip for 6.0.1 (MMB29K). BSME_SWeedon's instructions were great and, now that I know how to do it, I'll try to stay on top of future updates.
BSME_SWeedon, could you update the title to include 6.0.1?
Can you post some screenshots?
Got this merged in CM 13 Nightlies
http://review.cyanogenmod.org/#/c/137324/
Should be effective on the Mar 22 Nightly
I've upgraded to lollipop 5.1.1
But the proplem was to root it
ALL I HAVE FOUND WAS
downgrade and build prerooted zip zip.. etc
But now you don't have to do that
So let's startBy rooting your device you will void warranty
1. do backup for your phone
IAM NOT RESPONSIBLE FOR ANY LOSS OR DAMAGE
2.download the the files we need... Links down
3.go to Setting>security>unknown sources .... And tick it
4. Setup king root and start it
You will notified that there is code in app trying to bypassing android security
Install it any way
5. When finish go to download folder and extract the second attachment to /sdcard/
6.download terminal emulator from here
https://play.google.com/store/apps/details?id=jackpal.androidterm
7. When install open it then get root permission
Code:
su
Then
Code:
sh /sdcard/mrw/root.sh
And you will have root with supersu
If you want to keep kingroot
Skip from step 5
Hit thank if that help you
Download
Kingroot
https://drive.google.com/file/d/0B3yReeEdHxbWZkRqWWsxdDZxWGc/view?usp=docslist_api
Repace kingroot with supersu
https://drive.google.com/file/d/0B3yReeEdHxbWbl9nYlNTc2FyeVk/view?usp=docslist_api
Sorry about thread name
My keyboard is going crazy ?
Screenshot
https://drive.google.com/file/d/0B3yReeEdHxbWNk40MzJYYXVtUnc/view
Last time I tried it only works on 5.0.2 unless kingroot updated and now you can do 5.1.1 too
Confirmed
Tested and worked for Xperia z1 lollipop 5.1.1 fw. 368
Worked for me.
First link was deleted by google. I tried with the kingroot apk from their site, but it didn't work with that.
EDIT: strange, it did work over Mobile data but not over WiFi. I am now considering you my personal God.
abdo.war said:
I've upgraded to lollipop 5.1.1
But the proplem was to root it
ALL I HAVE FOUND WAS
downgrade and build prerooted zip zip.. etc
But now you don't have to do that
Download
Kingroot
https://drive.google.com/file/d/0B3yReeEdHxbWZkRqWWsxdDZxWGc/view?usp=docslist_api
Repace kingroot with supersu
https://drive.google.com/file/d/0B3yReeEdHxbWbl9nYlNTc2FyeVk/view?usp=docslist_api
Sorry about thread name
My keyboard is going crazy ��
Click to expand...
Click to collapse
already root with pre-root zip but i wanna try this method, can you mirror kingroot file? because i cant access that file , thanks in advanced.
When I try to put in sh /sdcard/mrw/root.sh it says that the directory doesn't exist. I know it does though. Should I rename my sd card to sdcard? or is there something I'm missing?
Fishcracker29 said:
When I try to put in sh /sdcard/mrw/root.sh it says that the directory doesn't exist. I know it does though. Should I rename my sd card to sdcard? or is there something I'm missing?
Click to expand...
Click to collapse
Are you using the internal memory, or the external one? If you are using the external, and extracted the zip file there, you need to enter the path on sdcard1. So it's: sh /sdcard1/mrw/root.sh
iedafarha said:
already root with pre-root zip but i wanna try this method, can you mirror kingroot file? because i cant access that file , thanks in advanced.
Click to expand...
Click to collapse
You can Download KingRoot from their official site at http://www.kingroot.net/
oh dang what ?! kingroot works now ? since when ? why didnt this come up earlier?
migidid said:
oh dang what ?! kingroot works now ? since when ? why didnt this come up earlier?
Click to expand...
Click to collapse
doesn't kingroot add all that Chinese spyware crap?
Squatrack Curler said:
doesn't kingroot add all that Chinese spyware crap?
Click to expand...
Click to collapse
yes but if you have any knowledge about rooting, its easy to get rid of and replace it with SuperSU
Doctor0710 said:
Are you using the internal memory, or the external one? If you are using the external, and extracted the zip file there, you need to enter the path on sdcard1. So it's: sh /sdcard1/mrw/root.sh
Ah ok. I read SD card as SD card. Didn't realize he meant internal. I ran it, and it kept coming up with errors that kingroot stopped working. Is that what it is supposed to do? Also now that i have SU on it ( I assume) what next? do I need a specific rom for these? IE I have a telus phone so should I look for a international rom or can I flash any? LOL I am fairly new at Root, and only flashed an HTC M8 but not really sure how to go about the z1. Also is it safe to uninstall kingroot? Sorry and thanks.
Click to expand...
Click to collapse
just tested an it works !! thank you Z1 .368
A thread already exists for this here. Please use it to keep things together and avoid duplicate threads.
Thread closed
ADD FACE UNLOCK TO ANY ANDROID
NOTE:- I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE
So finally i have discovered a way to add face unlock to any android by using the Google Smart Lock feature...
This feature is available in most of the android devices:good:...
There are two methods of doing THIS 1. Using ROOT2. Without root(using adb)
LETS START
1. USING ROOT
-download gapps compatible with your android(gapps must be nano or above)
-install ''RAR'' to your phone
-extract gapps.zip to your phone[make a separate folder(optional)]
-open the extracted files and open GApps folder
-here you will find 4 files (1.facedetect-lib-arm.tar.lz, 2.faceunlock-all.tar.lz, 3.faceunlock-common.tar.lz, 4.faceunlock-lib-arm.tar.lz)
-open facedetect-lib-armcommonlib and copy libfilterpack_facedetect.so to systemlib and set the permissions
-similarlly copy all the files and if required create new folder with the permissions and paste the files from all the 4 files
-EX:- copy Face Lock folder to system/app and set permissions
-reboot your device
-open settings>security>smart lock... here you will find Trusted Face option
-ADD YOUR FACE ND ENJOY....!!!
NOTE:- Permissions details will be in second post...
2. Without root(using adb)
I will be updating the fourm later with full adb method details...
BUT, if you want to give it a try... then learn some adb commands for pushing files to system folder and setting up the commands...
Your would have to one by push the files and the folders and set the specific permissions...
***In the screenshot section, the first screenshot is of setting permissions for file and the second one is for setting permissions for folder***
NOTE:- I used es file explorer for doing this modification.
NOTE:- I tried this on a700fd on stock touchwiz android 6 rom... and it worked perfectly:laugh:
***If this helped you, please Press THANKS***
***For any query, REPLY***
XDA:DevDB Information
FACE UNLOCK, Tool/Utility for all devices (see above for details)
Contributors
smart123123
Version Information
Status: Testing
Created 2018-10-23
Last Updated 2018-10-23
Reserved
Hi, i need install trusted face using adb method in my j701m with android 8.1.0.. you can help me? Thanks
D2U2 said:
Hi, i need install trusted face using adb method in my j701m with android 8.1.0.. you can help me? Thanks
Click to expand...
Click to collapse
Yes but i would recommend you to use the root method bcz in adb method you have to side load everything and then give specific permissions...
adb method
smart123123 said:
Yes but i would recommend you to use the root method bcz in adb method you have to side load everything and then give specific permissions...
Click to expand...
Click to collapse
please i need adb method too can anyone help?
I have tried root method and is not working for me. I'm on Havoc OS Android AOSP 9.0 on a Xiaomi Mi Max 2 device.
Your guide isn't clear at all but I think that I made all the steps. When I reboot the phone, folder with files added in system/app are missing and of course the face unlock option at Smart Lock menu is not present. Seems that Android erase the files by itself, don't know why.
Thanks anyway.
Inotalas said:
I have tried root method and is not working for me. I'm on Havoc OS Android AOSP 9.0 on a Xiaomi Mi Max 2 device.
Your guide isn't clear at all but I think that I made all the steps. When I reboot the phone, folder with files added in system/app are missing and of course the face unlock option at Smart Lock menu is not present. Seems that Android erase the files by itself, don't know why.
Thanks anyway.
Click to expand...
Click to collapse
Have u rooted ur phn with magisk??
smart123123 said:
Have u rooted ur phn with magisk??
Click to expand...
Click to collapse
hey
It sounded risky when I read it but, I gave it a try using the root method. It works for me.
Thanks for these fantastic tricks.
OFRA562 said:
hey
Click to expand...
Click to collapse
Yes... Post any type is difficulty you aaya facing... I'll surely reply...
How can we get assistance spotlight for dark environment......
Will this work in android 10
there are no such files in the gapps for android 10
This should be at least be half a fix for android 10 faceunlock
MaximusPrime said:
there are no such files in the gapps for android 10
Click to expand...
Click to collapse
maybe this is a newb response but if the files aren't in android 10 it shouldn't matter since this mod is putting the files there. So the files will be there. Maybe the dev that started this thread or someone with more experience can chime in here because thats exactly why im here. They removed the faceunlock framework from opengapps and i figure if they can remove it then it can be added back. I kinda feel like something will still be missing if you do this mod alone on android 10 though. I would like to know what exactly they removed from opengapps and then compare that with the files in this mod and maybe the 2 combined should get it working. Thats the line of thinking that im on. Sometimes it's that simple. I mean look at how many features can be turned on with flags and simple build.prop edits. I'm just not sure exactly how the face detect and faceunlock was removed and i need that little piece of information to grasp the scope of the problem a little better. Anybody Tried this on lineage 17 or any other android 10/q rom yet?:silly:
---------- Post added at 09:31 PM ---------- Previous post was at 09:27 PM ----------
esparkinfo said:
It sounded risky when I read it but, I gave it a try using the root method. It works for me.
Thanks for these fantastic tricks.
Click to expand...
Click to collapse
What Rom/Device/and android version did you use??? Give us a little more info so more of us can try with less risk and a little more confidence.
Thanks
can i install it on Android 6.0？
Anything for Android 10?
Is it working in CUSTOM ROM AOSP 7.2
ON ONE PLUS 2?
CAN YOU PLEASE DESCRIBE WHAT TO EXACTLY DO?
Did you get anything?????
D2U2 said:
Hi, i need install trusted face using adb method in my j701m with android 8.1.0.. you can help me? Thanks
Click to expand...
Click to collapse
I don't want to root my device but I need face unlock in my Mi A2 device.
pixel experience （android Q） has this face lock feature, so I guess maybe we could extract from it
Welp, OpenGapps does not include the face unlock anymore so RIP :/
*This would not be possible without j4nn & his amazing temp root https://forum.xda-developers.com/xperia-xz1-compact/development/devonly-exploits-temp-root-to-backup-t3795510 please thank & donate 2 him!*
This is not really a "how 2 guide" because I am not good at explaining things like this. But I will try & explain how I did it. Because I have seen a lot of other people also searching for working Volte without unlocking their bootloader.
First I used j4nn's temp root guide & flashed old firmware & ran his magic program. Then I backed up my DRM keys (incase I want to unlock my bootloader someday). Then I stopped. And instead of unlocking my bootloader & while still in temp root.. I thought, maybe I can write to the OEM folder? So I typed
'mount -o rw,remount /oem' and that worked!
So.. I used another command window without closing the first one and pushed a new OEM folder to /data/local/temp
(I got the new OEM folder from US XZ1c firmware. you can also get that folder by searching for TMo-VoLTE-fix-v3.zip & unziping it)
Then, I went back to the original temp root command window & used the 'cp' command to copy that new OEM file from data/local/temp over to my /OEM folder. I re-set the owner & file permissions rebooted.
After testing it, I was able 2 flash the latest (non US for working fp) Oreo by flashing like normal with Newflasher except I deleted the OEM.sin file, so it wouldn't write over my new one! Finally I disabled auto update.
Now my XZp is still bootloader locked, running 47.1.A.16.20 with Fingerprint, Volte & wifi calling all working on tmobile in the US.
I can actually receive calls at home now!! Before this, most of my calls went 2 vm, after a long pause.
I did also try it with pie & it didn't work for me. But, ymmv. I am sure it's possible tho. I was not impressed with pie anyways & I really hate that new volume popup window that covered my home & back keys in landscape mode.
One other note is because I have the dual sim XZp I changed my modem name in the modem.conf file from "tmobile_us_ims" to "dsds_tmobile_us_ims". I am not sure this is actually necessary tho because I have since looked in other ds Volte firmwares like Taiwan. And they don't use "dsds" in their modem.conf file
Robin Banks said:
*This would not be possible without j4nn & his amazing temp root https://forum.xda-developers.com/xperia-xz1-compact/development/devonly-exploits-temp-root-to-backup-t3795510 please thank & donate 2 him!*
This is not really a "how 2 guide" because I am not good at explaining things like this. But I will try & explain how I did it. Because I have seen a lot of other people also searching for working Volte without unlocking their bootloader.
First I used j4nn's temp root guide & flashed old firmware & ran his magic program. Then I backed up my DRM keys (incase I want to unlock my bootloader someday). Then I stopped. And instead of unlocking my bootloader & while still in temp root.. I thought, maybe I can write to the OEM folder? So I typed
'mount -o rw,remount /oem' and that worked!
So.. I used another command window without closing the first one and pushed a new OEM folder to /data/local/temp
(I got the new OEM folder from US XZ1c firmware. you can also get that folder by searching for TMo-VoLTE-fix-v3.zip & unziping it)
Then, I went back to the original temp root command window & used the 'cp' command to copy that new OEM file from data/local/temp over to my /OEM folder. I re-set the owner & file permissions rebooted.
After testing it, I was able 2 flash the latest (non US for working fp) Oreo by flashing like normal with Newflasher except I deleted the OEM.sin file, so it wouldn't write over my new one! Finally I disabled auto update.
Now my XZp is still bootloader locked, running 47.1.A.16.20 with Fingerprint, Volte & wifi calling all working on tmobile in the US.
I can actually receive calls at home now!! Before this, most of my calls went 2 vm, after a long pause.
I did also try it with pie & it didn't work for me. But, ymmv. I am sure it's possible tho. I was not impressed with pie anyways & I really hate that new volume popup window that covered my home & back keys in landscape mode.
One other note is because I have the dual sim XZp I changed my modem name in the modem.conf file from "tmobile_us_ims" to "dsds_tmobile_us_ims". I am not sure this is actually necessary tho because I have since looked in other ds Volte firmwares like Taiwan. And they don't use "dsds" in their modem.conf file
Click to expand...
Click to collapse
Do we lose drm key? Can I access the / system or use root explorer?
tronganhha29 said:
Do we lose drm key? Can I access the / system or use root explorer?
Click to expand...
Click to collapse
You won't lose any drm keys if you don't unlock the bootloader. I posted screen shots above that show all security keys intact, with locked bootloader. And if you look at the top, the wifi calling icon is there! The "rooting" part I used was only temporary & I only tried 2 modify files in the /OEM folder because that's all I needed for Volte & WiFi calling on tmobile. I had 2 downgrade firmware & run a temp root exploit from j4nn.
His exploit is explained here https://forum.xda-developers.com/xperia-xz1-compact/development/devonly-exploits-temp-root-to-backup-t3795510 BUT, instead of unlocking the bootloader I just copied US Xz1c /OEM files into my /OEM folder then set file permissions. That would be awesome if someone could make a script 2 automate this process for everyone!
Remember after your done, your gonna want 2 update to a newer more secure firmware. I didn't have luck with Pie, but it's got some minor bugs anyways (I am running Oreo 47.1.A.16.20 now & I love it). The trick is you MUST DELETE the OEM.sin folder from the new firmware folder before you flash it. Otherwise it will write over your progress.
Robin Banks said:
You won't lose any drm keys if you don't unlock the bootloader. I posted screen shots above that show all security keys intact, with locked bootloader. And if you look at the top, the wifi calling icon is there! The "rooting" part I used was only temporary & I only tried 2 modify files in the /OEM folder because that's all I needed for Volte & WiFi calling on tmobile. I had 2 downgrade firmware & run a temp root exploit from j4nn.
His exploit is explained here https://forum.xda-developers.com/xperia-xz1-compact/development/devonly-exploits-temp-root-to-backup-t3795510 BUT, instead of unlocking the bootloader I just copied US Xz1c /OEM files into my /OEM folder then set file permissions. That would be awesome if someone could make a script 2 automate this process for everyone!
Remember after your done, your gonna want 2 update to a newer more secure firmware. I didn't have luck with Pie, but it's got some minor bugs anyways (I am running Oreo 47.1.A.16.20 now & I love it). The trick is you MUST DELETE the OEM.sin folder from the new firmware folder before you flash it. Otherwise it will write over your progress.
Click to expand...
Click to collapse
Can you help me on activating VoLTE? I read in the above tutorial just talking about backup and restore TA partition. Sorry for my English not good. Thank you!
tronganhha29 said:
Can you help me on activating VoLTE? I read in the above tutorial just talking about backup and restore TA partition. Sorry for my English not good. Thank you!
Click to expand...
Click to collapse
Are you in the US, & want Volte on Tmobile?
Robin Banks said:
Are you in the US, & want Volte on Tmobile?
Click to expand...
Click to collapse
No, I'm in Vietnam, i'm using G8141 with custom CH firmware
tronganhha29 said:
No, I'm in Vietnam, i'm using G8141 with custom CH firmware
Click to expand...
Click to collapse
I am sorry, I am not familiar with any phone providers in Vietnam. I don't think there is an easy fix because I haven't seen Vietnamese Volte modem files in any XZp firmware. I could be wrong tho, so maybe someone will correct me & also help you out.
The only reason this works for tmobile is because Sony included built in support files for some providers, like tmobile in the US. But, it's only their XZ1c phone that will actually load the correct modem file & trigger Volte & WiFi calling features out of the box. Only a couple files need to be changed on the XZp.
Problem was, it always required a bootloader unlock to change those files.
This is not a problem anymore... Because it can now be done with temproot thanks to j4nn!
Robin Banks said:
I am sorry, I am not familiar with any phone providers in Vietnam. I don't think there is an easy fix because I haven't seen Vietnamese Volte modem files in any XZp firmware. I could be wrong tho, so maybe someone will correct me & also help you out.
The only reason this works for tmobile is because Sony included built in support files for some providers, like tmobile in the US. But, it's only their XZ1c phone that will actually load the correct modem file & trigger Volte & WiFi calling features out of the box. Only a couple files need to be changed on the XZp.
Problem was, it always required a bootloader unlock to change those files.
This is not a problem anymore... Because it can now be done with temproot thanks to j4nn!
Click to expand...
Click to collapse
I worry about losing drm key. I was on the xzc and I had a camera error.
Thank you !
tronganhha29 said:
I worry about losing drm key. I was on the xzc and I had a camera error.
Thank you !
Click to expand...
Click to collapse
The only way you can lose your DRM keys... Is unlocking your bootloader. I did not want to do that. But, I wanted Volte & WiFi calling. This thread is about how I got those features WITHOUT unlocking my bootloader. And yes, of course I still have my DRM keys.
You said, that you had a camera error on an XZ1c? Assuming, you unlocked the bootloader. Did you get Volte working in Vietnam after you unlocked it? If not, then none of this will help you with your XZp. because they are very similar & they use the same provider modem files.
From what I understand, the Pie update fixes the green picture camera error. Have you tried updating your XZ1c to Pie? That should atleast make your camera work again.
Good idea, i'm using others country rom because my country update speed suck ... (Due to the carrier) , so i lose feature like WIFI calling and VoLTE. Gonna try this.
vyis said:
Good idea, i'm using others country rom because my country update speed suck ... (Due to the carrier) , so i lose feature like WIFI calling and VoLTE. Gonna try this.
Click to expand...
Click to collapse
This is what people in the US with the XZ1c have been doing because they want to enable their Fingerprint sensor AND have the US Volte settings.
So if your provider already supports Volte.. Flash that firmware first so your volte works. Then before you flash the country you want to use. Just delete the new OEM.sin file out of the folder. That will make a perfect mix of the two.
It will only keep your volte provider settings from old firmware. You don't even need temp root.
But I doubt Volte setting would survive an OTA update. It also will work with two different build versions. I don't know if this is possible with oreo/pie mix tho.
Robin Banks said:
*This would not be possible without j4nn & his amazing temp root https://forum.xda-developers.com/xperia-xz1-compact/development/devonly-exploits-temp-root-to-backup-t3795510 please thank & donate 2 him!*
This is not really a "how 2 guide" because I am not good at explaining things like this. But I will try & explain how I did it. Because I have seen a lot of other people also searching for working Volte without unlocking their bootloader.
First I used j4nn's temp root guide & flashed old firmware & ran his magic program. Then I backed up my DRM keys (incase I want to unlock my bootloader someday). Then I stopped. And instead of unlocking my bootloader & while still in temp root.. I thought, maybe I can write to the OEM folder? So I typed
'mount -o rw,remount /oem' and that worked!
So.. I used another command window without closing the first one and pushed a new OEM folder to /data/local/temp
(I got the new OEM folder from US XZ1c firmware. you can also get that folder by searching for TMo-VoLTE-fix-v3.zip & unziping it)
Then, I went back to the original temp root command window & used the 'cp' command to copy that new OEM file from data/local/temp over to my /OEM folder. I re-set the owner & file permissions rebooted.
After testing it, I was able 2 flash the latest (non US for working fp) Oreo by flashing like normal with Newflasher except I deleted the OEM.sin file, so it wouldn't write over my new one! Finally I disabled auto update.
Now my XZp is still bootloader locked, running 47.1.A.16.20 with Fingerprint, Volte & wifi calling all working on tmobile in the US.
I can actually receive calls at home now!! Before this, most of my calls went 2 vm, after a long pause.
I did also try it with pie & it didn't work for me. But, ymmv. I am sure it's possible tho. I was not impressed with pie anyways & I really hate that new volume popup window that covered my home & back keys in landscape mode.
One other note is because I have the dual sim XZp I changed my modem name in the modem.conf file from "tmobile_us_ims" to "dsds_tmobile_us_ims". I am not sure this is actually necessary tho because I have since looked in other ds Volte firmwares like Taiwan. And they don't use "dsds" in their modem.conf file
Click to expand...
Click to collapse
You are awesome! Can you please write specific commands you used to
1) push a new OEM folder to /data/local/temp
2) 'cp' command to copy that new OEM file from data/local/temp over to my /OEM folder.
3) I re-set the owner & file permissions rebooted.
Thanks!
VBBoston said:
You are awesome! Can you please write specific commands you used to
1) push a new OEM folder to /data/local/temp
2) 'cp' command to copy that new OEM file from data/local/temp over to my /OEM folder.
3) I re-set the owner & file permissions rebooted.
Thanks!
Click to expand...
Click to collapse
I will try. But, like I said. I am not that great at step by step instructions. It would be awesome if someone made a better guide or a script 2 run after temp root.
So, AFTER you already have temp root. Open another command window (keep your temp root window open!) assuming you have the new OEM folder in your command line root dir.
Adb push OEM /data/local/tmp
Then using the temp root window from earlier exploit.
mount -o rw,remount /oem
chown root.root /data/local/tmp/OEM
cd /data/local/tmp/OEM
cp - R * /oem
chmod 755 /oem/modem-config
chmod 755 /oem/modem-config/408
chmod 644 /oem/modem-config/408/modem.conf
chmod 755 /oem/overlay-408
chmod 644 /oem/overlay-408/android-res-310-408.apk
chmod 644 /oem/overlay-408/com.android.carrierconfig-res-310-408.apk
chmod 644 /oem/overlay-408/com.android.phone-res-310-408.apk
chmod 644 /oem/overlay-408/com.android.settings-res-310-408.apk
chmod 644 /oem/overlay-408/com.android.systemui-res-310-408.apk
chmod 755 /oem/system-properties/408
chmod 644 /oem/system-properties/408/config.prop
Done. Reboot. You might half to take out your Sim card & reinsert it. Or factory reset. To get volte setting to take. You will know because it will say something like restarting to update carrier configuration.
Then of course you can update, but be shure to delete the OEM.sin file before flashing newer firmware! I tried this with pie once & it did not work for me. But ymmv. Right now I like oreo better anyways
I have included the zip file I found here on XDA & used it. It's meant for bootloader unlocked so just Unzip it & only use the OEM file.
Please let me know how it goes or if I forgot something!
Robin Banks said:
I will try. But, like I said. I am not that great at step by step instructions. It would be awesome if someone made a better guide or a script 2 run after temp root.
So, AFTER you already have temp root. Open another command window (keep your temp root window open!) assuming you have the new OEM folder in your command line root dir.
Adb push OEM /data/local/tmp
Then using the temp root window from earlier exploit.
mount -o rw,remount /oem
chown root.root /data/local/tmp/OEM
cd /data/local/tmp/OEM
cp - R * /oem
chmod 755 /oem/modem-config
chmod 755 /oem/modem-config/408
chmod 644 /oem/modem-config/408/modem.conf
chmod 755 /oem/overlay-408
chmod 644 /oem/overlay-408/android-res-310-408.apk
chmod 644 /oem/overlay-408/com.android.carrierconfig-res-310-408.apk
chmod 644 /oem/overlay-408/com.android.phone-res-310-408.apk
chmod 644 /oem/overlay-408/com.android.settings-res-310-408.apk
chmod 644 /oem/overlay-408/com.android.systemui-res-310-408.apk
chmod 755 /oem/system-properties/408
chmod 644 /oem/system-properties/408/config.prop
Done. Reboot. You might half to take out your Sim card & reinsert it. Or factory reset. To get volte setting to take. You will know because it will say something like restarting to update carrier configuration.
Then of course you can update, but be shure to delete the OEM.sin file before flashing newer firmware! I tried this with pie once & it did not work for me. But ymmv. Right now I like oreo better anyways
I have included the zip file I found here on XDA & used it. It's meant for bootloader unlocked so just Unzip it & only use the OEM file.
Please let me know how it goes or if I forgot something!
Click to expand...
Click to collapse
Thank you!!! just needed to edit command cp - R * /oem to cp -R * /oem
Robin Banks said:
[...] because I have the dual sim XZp I changed my modem name in the modem.conf file from "tmobile_us_ims" to "dsds_tmobile_us_ims".
Click to expand...
Click to collapse
Since my G8342 does not load the correct 'Current Modem Configuration' (see screenshot from G8341) I can force this by editing the 'modem.conf', right?
SGH-i200 said:
Since my G8342 does not load the correct 'Current Modem Configuration' (see screenshot from G8341) I can force this by editing the 'modem.conf', right?
Click to expand...
Click to collapse
I am just gonna guess that your running a single Sim firmware & you want 2 load a dual sim modem? I am pretty shure that won't work. You can use a single Sim firmware & modem file on a dual sim phone. But the other sim slot won't function. But it looks like you already know that. I am using a dual sim firmware (and phone g8142). But there is no official Volte tmobile firmware for the XZp. Even tho the correct tmobile modem is baked into all the XZp firmwares. It needs the OEM.sin to provision volte & WiFi. It sets "IMS" true or something like that. So I used an oem.sin config file from a single Sim Xz1c. But the rest of my firmware is still XZp dual sim. I originally changed the part where it loads the correct modem & added "dsds" to the beginning because that's what the tmobile modem in my firmware is named. That worked. But it turns out, I didnt even half 2 do that. It still loads my "dsds_tmobile_us_ims" modem. Even tho I just have "tmobile_us_ims" in my modem.conf file. If you were gonna try and load a diffent modem it would be under /oem/modem-config/310/modem.conf because 310 is the customization that your running (in your thumbnail). So, yes you can force it 2 load whatever modem you want.. But only try the modems that are included with your current firmware. I wouldnt copy an actual dual sim modem into your single sim firmware. It *might* work. More then likely would brick it. Lemme know if you have any other questions & I will help ya if I can
Robin Banks said:
I am using a dual sim firmware (and phone g8142). But there is no official Volte tmobile firmware for the XZp. Even tho the correct tmobile modem is baked into all the XZp firmwares. It needs the OEM.sin to provision volte & WiFi. It sets "IMS" true or something like that. So I used an oem.sin config file from a single Sim Xz1c. But the rest of my firmware is still XZp dual sim.
Click to expand...
Click to collapse
This is the way I did it, too!
Robin Banks said:
[...]still loads my "dsds_tmobile_us_ims" modem. Even tho I just have "tmobile_us_ims" in my modem.conf file.
Click to expand...
Click to collapse
Flashing the OEM.sin is not enough in my case (G8342) because the modem file is missing!?
Robin Banks said:
But only try the modems that are included with your current firmware.
Click to expand...
Click to collapse
Is it possible to "look" into a SIN file without flashing it, to see which modem files are included, without flashing the firmware?
SGH-i200 said:
This is the way I did it, too!
Flashing the OEM.sin is not enough in my case (G8342) because the modem file is missing!?
Is it possible to "look" into a SIN file without flashing it, to see which modem files are included, without flashing the firmware?
Click to expand...
Click to collapse
The actual modem files are in modem.sin and you could unpack them and take a look. But, if your using a single sim xz1 OEM.sin that supports your carriers volte settings.. I think you should be able 2 just flash the whole firmware. I have flashed a single Sim firmware on my XZp and back to dual sim. You will loose your second sim functionality. But you can always flash a dual sim firmware back & it will be good has new. Do you really use 2 sim cards? Check out the 7th post in this thread (user rafi.mv6) about Xz1 single Sim flashing. https://forum.xda-developers.com/xz-premium/how-to/xzp-volte-firmware-t3631276
I used j4nn bindershell version of the temp root and Your guide to activate VoLTE and VoWiFi for Vodafone CZ not for the temp root supported Oreo, but for the actually last available Pie firmware 47.2.A.10.107 Customized CE1 (1308-5321) for XZ Premium single SIM G8141
I am about to write down the detailed guide soon. It is based on info from j4nn post #9 in his bindershell version temp root thread.
XZ Premium Vodafone CZ Volte & WiFi calling in Pie WITHOUT bootloader unlock
THE STORY BEHIND
As I have very poor telephone signal inside the building of our veteran garage due to combination of a garage-to-BTS distance and very thick walls of an old building and many calls to me ended up with "The number cannot be reached, try again later" and me receiving the SMS with info about missed call, I wanted to use last issued Android for my Xperia XZ Premium single SIM G8141 and to have available VoLTE and VoWiFi for my provider Vodafone CZ. Then I started to investigate, which version of the phone and which customization I have exactly. I found, that despite being located in Central Europe, my phone customization was to my surpise of South Africa (1308-5324 Customized ZA 47.2.A.10.107). To achieve activation of the VoLTE and VoWiFi I thought, it could be enough to flash the Central Europe customization (1308-5321 Customized CE1 47.2.A.10.107), as special Vodafone CZ customization was not showed by XperiCheck, and it will all work seamlessly then. I could not be wrong more. After quite weak search for the info, I downloaded and flashed that Pie CE1 customization, with skipping userdata, all TA files and persist.sin to keep all data and settings not erased, there was no VoLTE nor VoWiFi available anyway. Then I started to investigate the possibilities more intensively. What I found, there was no direct option to have VoLTE and VoWiFi activated somehow on Pie, as the temp root and modification guides was available just for Oreo. But there were some hints within those threads, that pointed me to the possibility to achieve to have that function on Pie as well. Despite there were infos, that the intended sequences did not worked for some members trying it for Pie, it was not detailed enough to be clear, how they proceed. So I started to think about that all the time and based on number of Xperia XZ1c/XZ1/XZp threads, I considered many ways how to achieve my goal. Finally, the resulted steps were none of my ideas, I just collected all the wisdome from those threads and I just put them into the right sequence, that worked for me. If being on temp root supported Oreo firmware when started, it could be a path without loosing any user data, but as I was on last Pie, I had to backup every possible data and settings and to proceed the downgrade from Pie to Oreo with factory reset. There is no known way to me to downgrade with user data being kept, as despite I was warned, I tried it and I got the "promised" bootloop of course.
THE BASIC INFO
- SONY Xperia XZ1 (G8341), SONY Xperia XZ1 Compact (G8441) and SONY Xperia XZ Premium (G8141) are very similar phones with almost identical hardware. Therefore their firmwares do not differ much, at least in the text config files content manner. Hinted by XDA users, there can be the config files adapted from one of those devices to another easily. Many of them tested that for the Oreo and it worked fine for them.
- There exists Vodafone CZ customized Pie firmware for both XZ Premium friendly phones and they differ to their CE1 customized Pie firmware version just in the config settings part of oem.sin file and all modem definitions present inside in the system.sin are the same, so to change active modem, there is just config files modification needed that can be achieved through the temp root
- Using UnSin and ext4 image mounting SW investigate the files content, location and presence and try to figure out, which files could work for Your phone
- when flashing firmware, all excluded *.sin files/partitions will be not overwritten by new data and kept in the phone in current status and content. This is used in described steps to transfer changes from firmware supported by temp root to target firmware.
THE DESCRIPTION
The VoLTE and VoWiFi config files are in the /oem folder's subfolders. The content of the /oem folder can be kept when upgrading from lower to higher version of the Android by excluding the oem*.sin file when flashing. I disliked the idea to have oem settings from Oreo in the Pie and I tried to modify Pie's /oem folder within the Oreo firmware. Based on the info from this forum and by comparing all the firmwares content, I prepared (copied from CZ customized Pie firmware version of friendly phone G8341 XZ1) few files, that I identified to be important to change the modem file choosing by the system in XZ Premium Pie. So I prepared my own custom Oreo temp root supported CE1 customized firmware, excluded the XZp Oreo oem.sin and included the XZp Pie oem*.sin. I prepared the files to be changed in XZp Pie's /oem folder and the XZp Pie firmware with oem.sin excluded as well. I flashed first the hybrid XZp Oreo-with-Pie-oem-folder firmware to my phone successfully, started the XZp with Android Oreo. I cancelled all automatic updates, activated developer menu item and set the USB debugging ON. With using ADB I ran temp root, injected modified files into the /oem folder and set their rights. Rebooted and with temp root again I checked the injected files presence in /oem folder. Then I flashed CE1 customized XZp Pie firmware with its oem.sin excluded and rebooted XZp to Pie. I cancelled all automatic updates again and checked the modem and VoLTE settings. There was VoLTE option switch inside the service menus in blue color and actitaved with the VoWiFi option greyed out but set to ON. There the Enable VoLTE menu item appeared in the Network settings and it could be switched ON. In the Call settings, the Wi-Fi calling menu item appeared there in Advanced settings and could be activated. The service itself appeared and started to function after activating the service inside the provider Self service web portal.
THE PRINCIPLE
- I wanted VoLTE and VoWiFi for Vodafone CZ on SONY Xperia XZ Premium single SIM G8141
- To let it work, I had to modify Pie's /oem folder
- it is posible to modify it only when rooted or temp rooted
- I do not want to root it
- the only temp root is for Oreo
- I prepared and flashed hybrid firmware, Pie /oem with the Oreo main system - this trick was my only invention to this and it fortunately worked !
- I modified Pie /oem folder inside Oreo firmware temp root to support Pie's VoLTE and VoWiFi for Vodafone CZ
- I flashed latest Pie excluding the oem.sin to keep modified /oem settings then
- I switched the device settings ON and I activated the provider support for Vodafone CZ VoLTE and VoWiFi in Self Service portal
- Now I can enjoy Vodafone CZ VoLTE and VoWiFi on SONY Xperia XZ Premium single SIM G8141
WHAT TO DOWNLOAD
- To investigate Your phone version settings (not needed to follow my steps)
Download UnSin (UnSIN 1.13 (Win x64).zip)
Download SW for mounting and explore ext4 partition (ext2explore-2.2.71.rar)
Download the firmware for the other phones to look for setting files. In my case, it was G8341 Vodafone CZ customized Pie firmware (XZ1 G8341_Vodafone CZ_47.2.A.11.228-R2C)
- To activate VoLTE and VoWiFi for Vodafone CZ on SOMY Xperia XZ Premium single SIM G8141 (enough to follow my steps)
Download ADB (platform-tools_r33.0.2-windows.zip)
Download newflasher (newflasher_v52.zip)
Download the j4nn temp root alternative solution for G8141 (bindershell)
Download the G8141 j4nn temp root supported Oreo firmware in the same customization, as the later Pie to minimize issues (XZ Premium G8141_47.1.A.16.20 Customization CE1)
Download the G8141 CE1 customized Pie firmware (1308-5321 Customized CE1 47.2.A.10.107)
Download the G8141 Vodafone CZ customized Pie /oem fodler files (attached here as G8141_Vodafone_CZ_Modded_Pie_OEM_folder.ZIP)
THE PREPARATION
- if You want to proceed for phone different to G8141 and Vodafone CZ, check with xpericheck all three phone versions firmwares, whether there is any that contains customized version for Your provider, if there is one for Your phone, just flash that customization and You go
- if there is customized version of the firmware for Your provider for any of the other two phones, investigate the content of those firmwares oem*.sin and system*.sin files and try to match the proper files to copy/modify for Your phone (use UnSin and ext4 explorer for this task), the content of modem.conf file in oem.sin file, modem-config folder holds the short name of the modem *.mbn file in system.sin file, etc/customization/modem folder. For example, if modem.conf file contains "vodafone_czech_volte_vowifi" text, it defines using the "amss_fsg_maple_vodafone_czech_volte_vowifi_tar.mbn" modem files, that allows function of VoLTE and VoWiFi for Vodafone CZ. If Your firmware in system.sin contains modem file with the same name, You can modify /oem part of the firmware to select this modem and activate VoLTE and VoWiFi for Your phone/provider combination as well. I was inspired by Robin Banks files copied and I identified and copied several relevant files from G8341 Vodafone CZ firmware's /overlay folder as well. Try to add similar files for Your phone version as well.
- Prepare the XZ Premium single SIM G8141 temp root supported Oreo firmware into folder "01 not full Oreo downgrade with Pie OEM"
- exclude the Oreo oem.sin to allow using Pie oem.sin
- exclude the following Oreo firmware files as well: see content of the folder "01b not used Oreo files" (for the list see attachement file G8141_Vodafone_CZ_mod_FoldersContent.TXT)
- do not exclude userdata.sin when downgrading or else You get the bootloop (tested by myself )
- copy inside the folder the Pie's oem*.sin (oem_X-FLASH-CUST-42E5.sin)
- copy inside the folder the newflasher.exe file (to ease the process)
- extract ADB files into its folder, c:\platform-tools\ in my case
- copy content of the "02 adb push files" folder into c:\platform-tools\, extract it from the attached G8141_Vodafone_CZ_Modded_Pie_OEM_folder.ZIP
- copy bindershell file from j4nn for Oreo temp root into c:\platform-tools\
- Prepare the XZ Premium single SIM G8141 last Pie firmware into folder "03 Pie flash without OEM"
- exclude the Pie oem.sin
- exclude the following Pie firmware files as well: see content of the folder "03b_not_used_Pie_files" (for the list see attachement file G8141_Vodafone_CZ_mod_FoldersContent.TXT)
- copy inside the folder the newflasher.exe file too
- check both firmware folders to have their boot_delivery.xml file in boot folder and partition_delivery.xml file in partition folder for the flash to end correctly
- check the G8141_Vodafone_CZ_mod_FoldersContent.TXT and compare the folders' content to match
THE STEPS (Windows PC)
#01 - have Your phone charged, all data and settings backed up (including trim areas) and all phone drivers installed, this is a good way to start
#02 - go to "01 not full Oreo downgrade with Pie OEM" folder and run newflasher.exe inside, it will open a command line window, stay in this window
#03 - switch off the phone, hold volume down key and connect it to PC, wait for green LED ilumination and release volume down button
#04 - type 'n' + ENTER to skip install of GordonGate flash driver (You have them already installed, see step #01)
#05 - type 'p' + ENTER for poweroff after flash
#06 - type 'n' + ENTER to skip of dump trim area backup and the Oreo with Pie oem.sin flash will start, wait several minutes for process to finish
#07 - when flash finished, disconnect phone, close command line window
#08 - switch ON the phone and start Oreo system fully, disable any automatic updates ASAP, to stay on temp root supported firmware version of the Oreo
#09 - become a Developer and in Developer menu switch USB debugging ON
#10 - connect the phone to PC and allow connection
#11 - go to c:\platform-tools\ in Explorer and using SHIFT+right click open e.g. first PowerShell window from this folder
#12 - in PowerShell window type 'adb push bindershell /data/local/tmp' and press ENTER to copy bindershell file to the phone
#13 - if You do not have ADB fully installed and You just have drivers copied into the c:\platform-tools\ folder, type the command like this './adb push bindershell /data/local/tmp', add the './' before ADB commands in future, if this error repeats
#14 - in PowerShell window type 'adb shell' (or add ./ in the front of the command again) and press ENTER to run shell in the phone, the command prompt will change from PC:/platform-tools> to the name of Your phone, e.g. G8141:/ $
#15 - get a simple temp root shell according j4nn HOWTO
G8141:/ $ cd /data/local/tmp
G8141:/data/local/tmp $ chmod 755 ./bindershell
G8141:/data/local/tmp $ ./bindershell
#16 - You will know to have a temp root, when the prompt character changes from $ to # (like G8441:/data/local/tmp #), keep this first PowerShell window open
#17 - open a second PowerShell window from the same folder as the first one (c:\platform-tools\) using SHIFT+right click
#18 - in the second PowerShell window type 'adb push OEM /data/local/tmp' and ENTER to copy your modified files from c:\platform-tools\OEM folder on the PC to /data/local/tmp/OEM folder in the phone (in case of error add the './' before the command), after finishing, You can close this second PowerShell window
#19 - activate the first PowerShell window with the temp root still active and type following commands (these are the Robin Banks commands he wrote in the post #13 modified for my XZ Premium single SIM Vodafone CZ version)
mount -o rw,remount /oem
chown root.root /data/local/tmp/OEM
cd /data/local/tmp/OEM
cp -R * /oem
chmod 755 /oem/modem-config
chmod 644 /oem/modem-config/modem.conf
chmod 755 /oem/overlay
chmod 644 /oem/overlay/android-res-305.apk
chmod 644 /oem/overlay/com.android.carrierconfig-res-305.apk
chmod 644 /oem/overlay/com.android.settings-res-305.apk
chmod 644 /oem/overlay/com.android.systemui-res-305.apk
chmod 755 /oem/system-properties/
chmod 644 /oem/system-properties/config.prop
#20 - for You own setup, remember to set rights 755 for any folder name and rights 644 for any file name copied from /data/local/tmp/OEM to /oem folder inside the phone
#21 - Done. Reboot the phone into the Oreo with now modified Pie /oem folder. Close PowerShell window.
#22 - You can repeat temp root now to check, If Your files are really present inside the phone /oem folder and You proceeded well.
#23 - do not panic, if You check the Service info/Software info menu item now by dialing *#*#7378423#*#* and there is still recent modem *.mbn file selected, do not care about it as it is prepared for Pie and You are still on Oreo firmware now
#24 - go to "03_Pie_flash_without_OEM" folder and run newflasher.exe inside, it will open a command line window, stay in this window
#25 - switch off the phone, hold volume down key and connect it to PC, wait for green LED ilumination and release volume down button
#26 - type 'n' + ENTER to skip install of GordonGate flash driver
#27 - type 'p' + ENTER for poweroff after flash
#28 - type 'n' + ENTER to skip of dump trim area backup and Pie without oem.sin flash will start, wait several minutes for process to finish
#29 - when flash finished, disconnect phone, close command line window, now there is complete Pie system with VoLTE and VoWiFi modified /oem folder installed on Your device and all should work from now on
#30 - switch ON the phone and start Pie system, disable any automatic updates ASAP to keep Your modification in tact and not overwritten by future possible updates, if You want, regularly check for the firmware updates manualy and if there is a newer firmware You want to run, be prepared to proceed the whole this procedure again with newer firmware and test if it works for it as well
THE CREDITS
- j4nn for the XZp temp root alternative
- Robin Banks for the original How To
- chris_j26 for information in his [GUIDE] Enable VoLTE for your non operator handset thread (this needs Unlocked BL)
- pbarrette for the info to flash the cust-reset.ta file to clear the device current carrier customization information
- and credits for the SW creators (UnSin 1.13 - IgorEisberg, newflasher v52 - munjeni, Ext2Explore - rcrajesh & regmi_manish)
- and all the others forgotten...
THE DOWNLOAD
Here You can find
files list with the folders structure for all steps described above and compressed modified OEM folder to push to G8141 XZp single SIM Vodafone CZ
- all files used by me listed with their folder structure in TXT file
- a zip file with XZ Premium single SIM OEM folder modified for Vodafone CZ VoLTE & VoWiFi
- pictures
01 original ZA customization info
02 target CE1 customization info before MOD
03 final CE1 modded to CZ customization info after MOD
04 *#*#4636#*#* telephone info after MOD
05 WiFi calling menu item after MOD
Hi fellows
I'm a kind of newbie in the Android world, but I created a set of shell scripts to work with Topway TS10 Firmware:
---------------------------------------------------------------------------------------------------------------
TS10-Firmware-WorkbenchScripts intended to mount the Topway TS10 Firmware, make modifications and reassemble the firmware They can retrieve the firmware from specified location and after modification, they can put the firmware into another specified location
Files:
1-) config.ini = A file to setup parameters, paths for the original firmware and patched firmware, temp directory to work with firmware files and mount point to edit the firmware
2-) import_original.sh = Retrieves the files .0 .1 .2 and .3 from the location specified in config.ini
3-) import_patched.sh = Retrieves the same files that 'import_original.sh' but from the patched location specified in the config.ini (normally a firmware that you've already patched before)
4-) unpack.sh = Unpack the imported firmware and create the mount moint (as specified in the config.ini file) to work with the firmware
5-) repack.sh = Unmount the modified firmware from the mount point, delete the mount point, split the firmware in files .0 .1 .2 and .3 and move it to the patched directory as specified in config.ini
6-) inject_tweaks.sh = Modify locale, dataroaming and remove (if necessary) the values in ro.fota.device to avoid message "UI unauthorized, please contact the supplier"
7-) inject_mods.sh = This will copy all the contents of the '_mods' folder inside firmware. I.E. I put a 'gps_debug.cfg' inside 'system/etc/' and it will be injected into firmware overwritting the existent
inject_su.sh = This will inject su binary into firmware as a daemon, this is dangerous as the firmware is permanently rooted and the apps don't ask for permissions (they already have the root access) USE AT YOUR OWN RISK
9-) clean_local.sh = This script will unmount the firmware and delete it, it will also delete temporary files. as its name says, it cleans the dir !
External (included) tools:
tools/twt (Topwaytool) forked from https://github.com/mkotyk/topwaytool
_mods folder containing a sample file 'gps_debug.cfg'
N'joy it !
---------------------------------------------------------------------------------------------------------------
News
This will allow you to have root privileges in original firmware, but read VERY CAREFULLY as this method int NOT SAFE at all
At least for me it do the trick as I expected
I'll have my Topway TS10 THEME1 HU in a week and, if I am brave enough, I'll give it a go.
mariodantas said:
News here
https://github.com/mariodantas/TS10-Firmware-Workbench
This will allow you to have root privileges in original firmware, but read VERY CAREFULLY as this method int NOT SAFE at all
At least for me it do the trick as I expected
Click to expand...
Click to collapse
Is this way to root ownice k7 radio that i wish?? TT wow.....
This will ROOT, but everything inside will have ROOT privileges, UNSAFE, but as I said, for me, it did the trick and I'm happy with this !
mariodantas said:
This will ROOT, but everything inside will have ROOT privileges, UNSAFE, but as I said, for me, it did the trick and I'm happy with this !
Click to expand...
Click to collapse
Hello mariodantas.
I'm trying to utilize the project you made to mount firmware and inject su.
I'm a little new to some of this, so any guidance would be grateful.
Question:
How do i know what the mount point should be while using unpack.sh in config.ini?
! Creating _mountpoint folder...
Step 4 of 4 - Mounting ready raw firmware into '_mountpoint/' folder
mount: exec /Library/Filesystems/auto.fs/Contents/Resources/mount_auto for /Users/me/Desktop/TS10-Firmware-Workbench-main/_mountpoint: No such file or directory
mount: /Users/me/Desktop/TS10-Firmware-Workbench-main/_mountpoint failed with 72
READY !!!, you can go into '_mountpoint/' folder.
But _mountpoint folder is empty.
Andason74 said:
Hello mariodantas.
I'm trying to utilize the project you made to mount firmware and inject su.
I'm a little new to some of this, so any guidance would be grateful.
Question:
How do i know what the mount point should be while using unpack.sh in config.ini?
! Creating _mountpoint folder...
Step 4 of 4 - Mounting ready raw firmware into '_mountpoint/' folder
mount: exec /Library/Filesystems/auto.fs/Contents/Resources/mount_auto for /Users/me/Desktop/TS10-Firmware-Workbench-main/_mountpoint: No such file or directory
mount: /Users/me/Desktop/TS10-Firmware-Workbench-main/_mountpoint failed with 72
READY !!!, you can go into '_mountpoint/' folder.
But _mountpoint folder is empty.
Click to expand...
Click to collapse
What is your platform ? OSX ?
mariodantas said:
What is your platform ? OSX ?
Click to expand...
Click to collapse
Yes, OSX. I was checking more last night and maybe the issue is how mac handles the "auto" for file type.
Yes it sould be the mount command for OSX, but i can't help with OSX sorry, maybe you can clone the repo and after find the solution issue a pull request ?
after rooting the firmware doesn't seem to pass the checksum, everything is not working please help me ts10 1.2 ols10. ownice
Hello, have to check what's wrong with my code against 1.2 ols10 firmware, will check tonight and come back ASAP !
Cannot open file patch /init.rc.patch do not such how to fix please
Ok will check tonight !
@binharmani please add this to your config.ini
#Super User Folder
SUPERUSERFOLDER="_ superuser"
Click to expand...
Click to collapse
thank bro tool is ok . amazing good job
Thanks fellow
you can modify the "build.prop" manually after using "unpack.sh" by entering into "_mountpoint", modifying what you need and then repack the file and reflash in your headunit
How to set 775 file build.prop on linux
binharmani said:
How to set 775 file build.prop on linux
Click to expand...
Click to collapse
chmod 0775 build.prop
you should use a command line instead of the interface !
Mario good morning, if possible for you check the metode for change image car on display of ownice K7 ? Image in centrale display is very bad ifnpossible change png image with other car .......?
hello!
i've managed to use your tool, but there is a mention:
i've used it in a ubuntu vm (latest) and the mountpoint directory is empty if i don't run everything as root
repacked ok after this
my question is if i have to add the other files originally found in my original firmware folder with the newly repacked firmware files.
original firmware content (TS10.1.2_20210505.171701_TW1-V2):
a53f244a-9cbf-11ea-bb71-8bb1f7c98e0b.*
a71a8002-9cbf-11ea-b64e-578022b8a84a
ab2e7e2e-9cbf-11ea-bb71-fbb02866c44e
repacked firmware content:
a53f244a-9cbf-11ea-bb71-8bb1f7c98e0b.*