Of course, because Pixel 6 and Pixel 6 pro are different devices.
Pixel 6 is Product ID "oriole" and Pixel 6 pro Product ID "raven". For now the module v2.05 and less is for Pixel 6 only.
Send me to PM some info from your device to upgrade this for Pixel 6 pro too. No problem, I will add everything into the script for convertin
Sir, can you add a script for pixel 3a xl? plsOf course, because Pixel 6 and Pixel 6 pro are different devices.
Pixel 6 is Product ID "oriole" and Pixel 6 pro Product ID "raven". For now the module v2.05 and less is for Pixel 6 only.
Send me to PM some info from your device to upgrade this for Pixel 6 pro too. No problem, I will add everything into the script for converting.
Because you used incorrect commands, read carefully manual for using the script on 1-st page. Must be with Super User permission:Hi there, gave this a try on my Pixel 6 Pro. I got as far as MID_Changer.sh and then I get an "Unknown Model ID. Exit" error. Any thoughts on what could be causing that?
View attachment 5524731
Edit: I was able to make it work using the first method.
Thank you!
Yes, it should be possible as the change made is on the /dev partition and will remain even if you unroot. You can unroot by simply uninstalling Magisk and re-lock the bootloader if needed.Hey guys,
I am new to this.
After converting with root, would it be possible to retain the conversion by removing the root and also bootloader locking it?
Thank you.
This is my Pixel 5a cdt dump after modification. I just masked my personal information and just put IMEI, MAC ADDRESS, etc instead. However, I think the SKU offsets are different between Pixel 5 and 5a so the update_binary script screwed up my cdt file. Where I have put the arrows is where the changes were made by the script and also manuallly.I have a Japanese pixel 5a and tried to adapt the update-binary from MID_Changer_v1.02-TWRP.zip by adding MID_barbet with G1F8F, G4S1M SKU.
But I think I screwed up my cdt file by doing so as offset appear different from pixel 5. The script itself doesnt take any backup. At least, my device is not bricked but when checking the Regulatory Labels, I get nothing apart from the title.
Could someone share his cdt file in private with me so I can try to revert back to original? At least, I would like to know the sections 0x1a0 to 0x200, which should correspond to psn, bootmode, pcbcfg,sku in reverse order. That should not contain personal information such as IMEI, MAC address, etc. Thanks!
Well, I thought it would be easy just to add the barbet model and related SKU. My phone was not rooted at that time so I couldn't check the original cdt file and take a backup. It was a bad lesson for me, I guess. Anyway, I did check the /persist partition but couldn't find it. Is it part of the original file system? I have unrooted my phone for now and using modded gcam app.blood_talon,
I haven't to answer because you didn't ask me and I don't like when someone change my scripts without necessity especially when I explained above that any converting won't help for your devise due to HW.
So, I have no idea how much you changed my script but any my scripts always save the original partition image to /persist before converting. Look at there..
Hi Ziand, thanks for offering. Let me send my cdt.img in private.@blood_talon, if you are still with this trouble, you can send me to PM your current cdt.img and I will send you back corrected one.
I'm not familiar with law in every country but doing this could have risk. Research before acting.
The instructions requires basic Linux/Android knowledge. You could brick your phone if not knowing what you're doing. You can always wait for ziand's work for more safety.
I confirm this works on my phone. But I'm not responsible for anything happens on yours. Use at your own risk.
adb shell
su
dd if=/dev/block/by-name/devinfo of=/sdcard/devinfo.img
Keep this file as backup
adb push ./devinfo_modified.img /sdcard/
adb shell
su
dd if=/sdcard/devinfo_modified.img of=/dev/block/by-name/devinfo
Here is below a script to convert the device to another version.At the same time @ziand may also work on a magisk module or something when possible, doing the same thing but in a much safer way. Once his work is done please switch to his method.
This is known issue as even global Pixel do have forced shutter and screenshot sound when a Japanese carrier SIM is inserted, no matter where you use it. In this case MID changing method can't help you.Yes i am working in japan, i tried inserting softbank sim, sadly the camera sound is back again and the setting to turn off shutter sound is gone.I tried removing the sim and restarting the device ...the setting to turn off camera sound appeared again. very happy
For adding Mobile Suica to my P7P, and I just modified the SKU of it then flashed it back to stock firmware.I convert to GE2AE from GFE4J. Anyway why you want to change your SKU to Japan?