Pixel2 and QXDM - Google Pixel 2 Questions & Answers

Hi,
I have seen branch with discuss about Pixel XL + activating diag port but I couldnt find it for Pixel 2 (OPM1.171019.013).
I'm suck a bit after trying to do next steps:
1. I have rooted device, OREO
2. I replaced default init.walleye.diag.rc file but again it was produced for XL and I couldnt find things on the folder:
/sys/class/android_usb/android0/ as f_diag and so on.
3. I'm not sure which paths I have to use and what exactly needed to be changed
4. if it requires to rebuild vendor.img for /vendor/ to keep changes what the best way to do that? I was able to find
https://forum.xda-developers.com/pixel-2-xl/how-to/tools-tools-building-pixel-2-xl-kernel-t3693955
but again it is about pixel XL mostly and not sure applicable for pixel2.
Did anybody unlock diag on Pixel2? What the steps?
Thanks!

I would like to connect to the question above.
Do anyone have any idea how to make Pixel2 working with QXDM? (having diagnostic ports enabled)
/.witek

Related

How to fix USA BAND / AUTO problem for Pixel

Hi guys,
Looks like Pixel has the same problem than Nexus 5, Nexus 5X, Nexus 6P and Nexus 6. If you select a band from the *#*#3646*#*# menu, you will loose signal and you won't be able of going back to your original config (not even reflashing radio, system images and so on).
@bitdomo tried to build a aosp rom with for the pixel but he hasn't been able (he is getting memory problems).
The fix seems to be easy (all credits to @bitdomo) you have to modify this file https://android.googlesource.com/pl...1.1_r4/src/com/android/settings/BandMode.java to run this code part http://pastebin.com/MpH8ccPq
Maybe if someone can build aosp with that modification it will be helpfull for people with this problem. Or maybe a rom is not needed just a .zip file?
I really don't understand how google hasn't fixed that, you can enter that menu with your bootloader locked and without root.. Heck even without developer options enabled!
Was there a "hot flashable" fix for the Nexus devices?
This was fixed by @bitdomo
http://forum.xda-developers.com/showthread.php?t=3516505
Sent from my Pixel using Tapatalk
What config is lost?
Sent from my Pixel using Tapatalk

[HELP] Leagoo T5: why is not available any ROM ?

Hello
I've a Leagoo T5 wich use his own Nougat modifiied. TERRIFIC !!!
I'm looking for another ROM wich supporting all feature (also double rear camera and fingerprint reader) because it's impossible to use it.
T.I.A.
Paolo
You can use "MTK Extractor" to extract system.img and other files, you can then modify them, and flash them using "SP Flash".
I recently uploaded a clean stock ROM (LEAGOO_T5_OS2.1_E_20180116) to Mediafire and Needrom.
I've also uploaded a carepack if you are interested in the new ROM, or even for a custom.
The command for fast boot is: fastboot oem unlock
Ferather said:
You can use "MTK Extractor" to extract system.img and other files, you can then modify them, and flash them using "SP Flash".
I recently uploaded a clean stock ROM (LEAGOO_T5_OS2.1_E_20180116) to Mediafire and Needrom.
I've also uploaded a carepack if you are interested in the new ROM, or even for a custom.
The command for fast boot is: fastboot oem unlock
Click to expand...
Click to collapse
Do you mind sharing please? I'd love to get a working custom rom on this device.
I still can't add links yet, so you will have to Google search: "MTK Extractor". Download it, and then download the latest official ROM, which I have uploaded to Needrom and Mediafire, Google search: "OS2.1_E_20180116".
Extract the "system.img" file from the stock ROM using MTK Extractor, you can then go ahead and make your customization's. System apks are signed and locked, however they can be replaced.
When you have finished, you can use MTK Extractor to create a new system.img file with all of your modifications (including root, if you add it). The size for system.img is 4096mb.
The MTK Extractor tool uses a slider bar and text input for the partition size, the slider is limited, however enter 4096 into the text box (don't delete the text, it bugs).
Enter fastboot (Power + Volume up), third option, then using ADB with command prompt, type the command: "fastboot oem unlock", and then accept.
Now you have unlocked the phone, you can run your custom ROM. In a factory locked state, ROM's will install, but not run.
I forgot to mention my Needrom pack contains MTK Extractor. If you can make roms, there are 3 stock bugs that I would ask you to fix.
1: If the navigation bar is hidden, there is a window transition blip (bottom of the screen) if you swipe to recent apps.
2: If you select the first (bottom left) icon from the lock screen (voice, usually), you get a grey background.
3: Bluetooth scanning sometimes bugs (MAC instead of name), once paired there are no issues.*
* This may be due to my headset, but I remember my TV also displaying a MAC once.
Also, can you align or remove the 4G icon that shows even with data turned off.
Ok... So far this thread seems to be the only one on xda-dev about leagoo T5, which i just buy.
By the way thanks Ferather for pushing the rom on need rom.
Here the link :
https://www.needrom.com/category/leagoo/t5-leagoo/
Need help
Hi, could you please share the Mediafire link?
Since the last rom update (LEAGOO_T5_OS2.1_E_20180822 aka OS2.1_E_20181025) I post on needrom a moded rooted boot with magisk.
i have this leagoo t5 running this newest e_20181025 but im getting a problem with my front facing camera only displaying like an upsidedown image of the rear camera. please advise on what i can do to fix this
Maybe inconsistence between differents partitions (like boot and system)
If you know what you are doing I will advise reflashing all principal partitions.
But i don't think the phone came like this when new, so someone must have messed something.
https://www.mediafire.com/#3c2rnntnz3kw0
LEAGOO_T5_OS2.1_E_20181025.zip -- Original Leagoo T5 ROM
LEAGOO_T5_OS2.1_C_20181025.zip -- Custom Leagoo T5 ROM
No issues, other than the one I have mentioned, which is just an app default.
Enjoy!
hey cool rom bro.
Thank for sharing.
No problem, I thought I would start the ball rolling for customization of the rom, since adding ringtones does not work with the stock rom (media storage app issue I think).
You can permanently edit the rom yourself, which I found very easy. If you want to add apps, simply install them from sdcard or store, then navigate to "/data/app", you will find your installed app or update, with odex files and libs, if any.
I created a temp folder on "/data" called "Working" and copied everything into it, and then setup the correct permissions, and renames, and transferred to either "/system/app" or "/system/priv-app", depending on the app.
A better way to do it, is to use "Lubuntu" from live USB or DVD, and then mount the image and edit it as root: "sudo *file explorer*", in this case "sudo pcmanfm-qt", then create a folder in "/mnt" called "ROM".
Next copy "system.img" to "/tmp", and mount it "sudo mount /tmp/system.img /mnt/ROM", now you can do whatever you like, but make sure to "chown" and "chmod" all your modifications.
Make sure you delete anything you will replace when you transfer, else you might get old unused files (folder merged and non-replaced items remain).
----
If you make edits on the phone using an app, and want to make your own "system.img", use the readback option in "SP Flash Tool".
physical_start_addr: 0xe000000
partition_size: 0x100000000
----
Note: Most non-stock apps *do not* support the triple (3x) camera setup, and will either use the wrong camera or crash.
Yeah I encounter problems too to add custom ringtone and wallpaper but i manage to get over it by changing some files permissions
By the way I am "456456" on needrom, the boot img with magisk is from me
I know the time needed to make a custom rom and I'm glad to see that I'm not the only one trying to mess with this not-bad-at-all cheap phone
There is a possibility of an Oreo port, there is a Leagoo T8s with the the same chip that runs Oreo 8.1.0. I have checked over the rom and it looks possible (based on my basic knowledge).
Cygwin + Cmder, for Android. I made the pack myself, and thought it might help others using Windows who want various Linux tools.
I added Cmder for better console support and easy admin: ---- http://www.mediafire.com/folder/lzsf7xd2wwsm4/Commander
Quick update, will now self configure "/home", added ADB and Fastboot.
Ferather said:
There is a possibility of an Oreo port, there is a Leagoo T8s with the the same chip that runs Oreo 8.1.0. I have checked over the rom and it looks possible (based on my basic knowledge).
Click to expand...
Click to collapse
Hi, Running your ROM with no other mods, it's certainly better than original. Just curiousis there anyone working on an Oreo based ROM ?. ... J
Thanks, I did not manage to get the Oreo from the T8 to function, due to hardware changes.
Ferather said:
Thanks, I did not manage to get the Oreo from the T8 to function, due to hardware changes.
Click to expand...
Click to collapse
Ah !, C'est la vie, would have been interesting. Apologies for late reply was away from home and didn't have much spare time. ... Jack
please tell me how you can fix the inverted touchscreen Leegoo T5

OnePlus 6 drivers to build custom Android ROM?

I'm trying to build Android on my machine, and everything is going well, but there is one thing I am missing, and that is the binary drivers for the OnePlus 6. The Android build guide only has the drivers for the Nexus and Pixel phones, and after doing some major Googling, I can't find them anywhere.
Since people are already releasing custom ROMs for the OnePlus 6, I assume they are out there, but I haven't been able to find a download location for them at all.
To be clear; I'm looking for the drivers that are on the phone itself, not the USB drivers you install on your PC.
i noticed when I pulled my OP6 first time, a CD gets mounted with drivers, did you see it?
jabbermacy said:
i noticed when I pulled my OP6 first time, a CD gets mounted with drivers, did you see it?
Click to expand...
Click to collapse
I'm pretty sure that is just the drivers to connect it to the PC and keep it synced with the PC. What I am talking about is the drivers for the hardware inside the phone such as the GPS chip, GPU etc.
jabbermacy said:
i noticed when I pulled my OP6 first time, a CD gets mounted with drivers, did you see it?
Click to expand...
Click to collapse
is this a joke? :laugh:
TheMuppets Repo used to be my go-to proprietary vendor repository for huge number of OEM and devices. I see that Oneplus6 isnt there yet. May be wait until they add or may be someone else might help you out to get it at the earliest
vijai2011 said:
TheMuppets Repo used to be my go-to proprietary vendor repository for huge number of OEM and devices. I see that Oneplus6 isnt there yet. May be wait until they add or may be someone else might help you out to get it at the earliest
Click to expand...
Click to collapse
Thanks for the link. I've starred the repository. I guess I'll have to wait then or investigate some of the custom ROMs to see if I can extract them by hand. That might be a little difficult for me though as I'm entirely new to Android operating system development.
Are you talking about device tree? It's not available yet, but OP promised to release it.
Also, the current roms available use oxygen OS as the base ie. Modified Oxygen OS or take advantage of treble as device tree is not needed for that.
Shouldn't there be a pull-files.sh script that pulls all the files?
That's what I did on my 3T
Actually I don't even think the source code for ROMs is available yet, I saw this article: https://www.xda-developers.com/qualcomm-snapdragon-845-kernel-source-code/

Deep TEST fot OPPO RENO ACE(unlock bootloader)

OPPO's official website provides users with an official way to unlock bootloader.
coloros link:
https://bbs.coloros.net/graphic?id=1498611
you need to install the deeptest.apk to submit unlock request.
The application must meet all the following conditions:
1. The time to market must be more than 3 months;
2. No application record within 60 days;
3. The last consecutive login time of the OPPO account on this machine exceeds 60 days;
4. The number of in-depth test users has not reached the quota limit;
5. Non-government enterprises and operators customize mobile phones;
6. Support mobile phones listed in mainland China.
Unfortunately, there are currently no available quota.But if you want , you have to register an oppo account,and login time should more than 60 days.
So does this mean we can install custom rooms?
So... Hey guys,
I just wanted to let everyone know that I was actually able to flash the GSI from the link below on my OPPO Reno Ace:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development/aosp-10-0-quack-phh-treble-t3992559
I am super new to all this, but I decided to take the risk anyways because I really wanted to get away from ColorOS. Luckily it worked out to the point that the phone seems functional so far (just flashed it as of writing this).
Disclaimer: Do this at your own risk! I am not responsible for what happens to your phone for following what I did. Please think twice before trying! Also remember to back-up your phone first!
Before I continue on how I got it to work, I got the Reno Ace Gundam edition. Not sure if that makes a difference but I thought this should be mentioned. Also since I couldn't find a version of TWRP for the Reno Ace; I followed the instructions on how to flash without it.
Here are all the main links I used:
Walkthrough for Deep Test app: https://forum.xda-developers.com/find-X/how-to/guide-how-to-apply-deep-testing-pafm00-t3888013
GSI: https://forum.xda-developers.com/project-treble/trebleenabled-device-development/aosp-10-0-quack-phh-treble-t3992559
Flashing Instructions and "vbmeta.img": https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
Extra Links in case of weird trouble. Hopefully you won't need it:
Google Usb Driver: https://developer.android.com/studio/run/oem-usb#InstallingDriver
How to manually install Google USB Driver: https://visualgdb.com/KB/usbdebug-manual/
Useful Key Word: Kedacom USB Device
*** Backup your phone before going forward.
Getting the Deep Testing app:
Now first, you do need to sign-up for an OPPO account. The link from the OP will take you to their site and you can sign-up from there.
- You will be required to login to your OPPO account in order to use the app.
- The file you download is named "Reno Ace深度测试.apk".
- Add ".apk" to the end of the filename if it's not already there. DO NOT rename the file.
- Once logged into your OPPO account on your phone, you stay logged in so you don't need to worry about actively logging in everyday.
- Next, follow the instructions on how to use the app from the Deep Test thread.
- Keep trying until your submission gets accepted, then the hardest part begins: you...wait...
- Once approved, it took ~2 days for me to be able unlock.
Make sure you have ADB ready on your computer:
- There are plenty of guides on it, so I'll just leave a link here; honestly I forgot the specifics already: https://www.xda-developers.com/install-adb-windows-macos-linux/
Steps:
- Prepare your GSI: You can look for other GSI(s), but from my research it seems safest to get it from here first; before trying others: GSI thread
- This link explains what GSI are and how to choose which one to get.
- *Make sure to extract the ".img" file from the ".img.xz" zip file.*
- Download "vbmeta.img" from "Troubleshooting Tips" of the "Flash GSI without TWRP" section of the How to Flash GSI Guide.
-After you've extracted the ADB folder, keep the files (.img files) you intend to flash within the "platform-tools" folder.
*Noob tip lol: Clicking on the folder address and typing "cmd" is the quick way to open command prompt within the directory.*
- *** There are some unique steps for the Reno Ace, if not all OPPO phones, due to the Deep Testing app. ***
- After you get your approval, note that if you press the "Start Deep Testing" text you will be immediately put into fastboot mode. SO DO NOT PRESS IT NOW.
- Make sure you have OEM Unlock and USB Debugging enabled within Developer Options. Then connect your phone to your PC and set it to transfer files.
- On computer, open command prompt within the "platform- tools" folder. Enter the command "adb devices", when you see your device ID and "device" next to it, this means the phone has been connected. (If a prompt on your phone pop-ups, tap the "Always allow this computer to USB Debug" and "Allow". This is just what I did, not sure if it's necessary).
- Now go into the Deep Testing app on your phone, tap on "Queue status" and then "Start Deep Testing".
- You should see the images from this Oppo Find X tutorial, on your phone. Landing on the screen with the big green "Start" on top.
- Once you're here, enter "fastboot flashing unlock" into ADB and you'll move on to the next screen where you select "Unlock the Bootloader".
- After confirming, your phone will factory reset itself, and reboot into ColorOS again.
- Check to make sure your phone is connected to adb.
- From here on you follow "Flash GSI without TWRP" part of the How to Flash GSI Guide starting at step 2. If you have your ".img" files in the "platform-tools" folder then you can skip step 3.
- Before step 5 you need to flash the vbmeta: fastboot flash vbmeta name_of_vbmeta.img
Then flash the GSI ".img" file with fastboot -w flash system name_of_system.img.
(The comments there mentions that the "-u" is incorrect and should be "-w", which worked for me.)
* Important: without flashing "vbmeta.img" you'll be stuck in a boot loop because the phone prevents you from booting into the GSI. If this does happen, hold down Volume Down and Power until the phone vibrates to boot back into "fastboot mode". Enter "fastboot device" in ADB to confirm the phone is connected, and start over from step 4 in the How to Flash GSI Guide. *
- Once you finish step 6 your phone should boot into the GSI.
Hopefully this proves useful. I'm no expert, I simply found my way around things.
I honestly have no idea where to go from here, Magisk? LineageOS? If anyone can give me some pointers, that would be very much appreciated.
Things that are not working for me:
- Can't setup In-screen Fingerprint sensor
I got a twrp that works just finished rooting with help of the vbmeta above
Darktron13 said:
I got a twrp that works just finished rooting with help of the vbmeta above
Click to expand...
Click to collapse
Would you mind giving a link to the twrp you found? I was searching around for one as well, but I couldn't find anything I felt comfortable with.
Also did you also flash a gsi? If you did, I was wondering if your headphone jack is working. Mine doesn't work anymore; the phone seems to recognize it, but no headphone icon shows up and sound plays through the speakers only.
falsewind said:
Would you mind giving a link to the twrp you found? I was searching around for one as well, but I couldn't find anything I felt comfortable with.
Also did you also flash a gsi? If you did, I was wondering if your headphone jack is working. Mine doesn't work anymore; the phone seems to recognize it, but no headphone icon shows up and sound plays through the speakers only.
Click to expand...
Click to collapse
Haven't install any gsi just have ColorOS 7.1 C.27 I cant remember where I got that twrp from all I know is a Chinese twrp think I found it on some baidu drive I was just waiting on approval from the in depth testing app.
Darktron13 said:
Haven't install any gsi just have ColorOS 7.1 C.27 I cant remember where I got that twrp from all I know is a Chinese twrp think I found it on some baidu drive I was just waiting on approval from the in depth testing app.
Click to expand...
Click to collapse
Thanks for the quick reply. I think I know where that's from. I believe that it's from here:
http://www.romleyuan.com/lec/read?id=348
Let me know if it looks familiar. Great to know that it works!
falsewind said:
Thanks for the quick reply. I think I know where that's from. I believe that it's from here:
http://www.romleyuan.com/lec/read?id=348
Let me know if it looks familiar. Great to know that it works!
Click to expand...
Click to collapse
Yes looks familiar it should be that one the twrp itself has Chinese and English languages.
Formatting and wipe is working otg also haven't really tested alot also you can flash ozip stock rom with it if you plan on rooting the boot gets corrupted but with the vbmeta bypasses it.
if you plan on installing V4A don't do the magisk module will bootloop have to look for the rootless V4A. (also need AML and the sound is great)
also don't change to f2fs i did it and the phone make weird noises went back to ext4.
Darktron13 said:
Yes looks familiar it should be that one the twrp itself has Chinese and English languages.
Formatting and wipe is working otg also haven't really tested alot also you can flash ozip stock rom with it if you plan on rooting the boot gets corrupted but with the vbmeta bypasses it.
if you plan on installing V4A don't do the magisk module will bootloop have to look for the rootless V4A. (also need AML and the sound is great)
also don't change to f2fs i did it and the phone make weird noises went back to ext4.
Click to expand...
Click to collapse
Awesome! Thanks for the info, it will come in handy later on. Still just learning and getting familiar with all this.
A follow up after a couple of days of using phhusson's gsi.
Overall the phone is functioning very well. Generally smoother than on ColorOS.
Things to note:
- Battery life is good, same if not better than on ColorOS.
- Fast charge works. Full charge in around under 30 mins.
- Wi-fi works and Data works.
- Phone and Text work.
- Camera works.
- Headphone jack won't work until you go into the treble-settings (Phh Treble Settings) -> Qualcomm features -> and turn on "Use alternate audio policy"; then restart your phone. Then it will work again, although no headphone icons will appear. I don't use Headsets, so I couldn't test if that works as well.
- The phone will be rooted by default, so certain apps can't be downloaded, or used. (Root can be removed, but it doesn't seem like a good idea.) There are ways around this, but I didn't dive very deep into it.
Problems to note:
- In-screen fingerprint sensor can't be used.
- No auto-adjusting brightness.
- Brightness is a lot brighter than in ColorOS. Even lowest brightness is bright.
- Auto-Rotate is very sensitive and won't stay landscape when phone is flat on a table.
- Certain apps may not be full screen if you use the new gesture navigation. (Shadowverse)
- I didn't test Bluetooth or NFC. I don't use them much, or at all, so I'll follow up on that when the time comes and no one else has mentioned anything on them yet.
That should be all for now. Honestly very happy with the move. Hope this helps.
**Just an extra reminder that this is my experience with this specific gsi. **
Is this still available? I can't download the APK from Oppo, I logged onto my 'heytap' account but the download link just brings me to my account information.
twgib said:
Is this still available? I can't download the APK from Oppo, I logged onto my 'heytap' account but the download link just brings me to my account information.
Click to expand...
Click to collapse
I've reply back on the other post about Oppo Reno which model you have Ive posted both apks
Darktron13 said:
I've reply back on the other post about Oppo Reno which model you have Ive posted both apks
Click to expand...
Click to collapse
Thank you so much! You're too kind!
Nice to see some progress on this phone it has so much power and potential!
Help
Darktron13 said:
Haven't install any gsi just have ColorOS 7.1 C.27 I cant remember where I got that twrp from all I know is a Chinese twrp think I found it on some baidu drive I was just waiting on approval from the in depth testing app.
Click to expand...
Click to collapse
Please can you share the twrp, I have the device but it is really hard for me to download it from baidu, if you were already kind to share it, you would help me a lot to test the phone, thanks in advance. Sorry for my English, it's not very good.
is there any info about what stock rom you're using? i was trying to install Phh's AOSP gsi thourh fastboot, the system-quack-arm64-aonly-vanilla.img , and only to get stucked at the OPPO logo, i'm using C26 curently
刘欲杰lol said:
is there any info about what stock rom you're using? i was trying to install Phh's AOSP gsi thourh fastboot, the system-quack-arm64-aonly-vanilla.img , and only to get stucked at the OPPO logo, i'm using C26 curently
Click to expand...
Click to collapse
ok, i figured it out. Ace is a System-as-root device,so i need to use a/b img files
I wanna root my phone
OPPO Reno Ace Twrp.7z
1 file sent via WeTransfer, the simplest way to send your files around the world
we.tl
[这是color7 可以用的twrp 如果你们可以进去下载的话
xdsfh said:
OPPO's official website provides users with an official way to unlock bootloader.
coloros link:
ColorOS 12_话题_OPPO手机官方社区
ColorOS 12延续“无边界”设计理念,为你带来更懂你的智慧操作系统!
bbs.coloros.net
you need to install the deeptest.apk to submit unlock request.
The application must meet all the following conditions:
1. The time to market must be more than 3 months;
2. No application record within 60 days;
3. The last consecutive login time of the OPPO account on this machine exceeds 60 days;
4. The number of in-depth test users has not reached the quota limit;
5. Non-government enterprises and operators customize mobile phones;
6. Support mobile phones listed in mainland China.
Unfortunately, there are currently no available quota.But if you want , you have to register an oppo account,and login time should more than 60 days.
Click to expand...
Click to collapse
URL not found

Question Cross-Flashing Mi 11 Ultra (Snapdragon 888) - Lahaina Modem Image to ROG for more carriers compatibility ??

Hey Guys,
So along with my struggle of loading MBN files, I eventually used a Xiaomi Mi 11 Ultra (Global Edition) for a few days. This is another device that runs on the Same Snapdragon 888 SOC, and has the exact same Modem (Codename Lahaina). On the Mi 11 Ultra, Both my carriers have 5G / VoLTE working perfectly fine and had no issues whatsoever.
I opened up both the modem.img files (Can be viewed with 7Zip) and even the file structure is identical including the codenames, with the difference Xiaomi modem having more MBN files for many more carriers (I posted the MBN file extracted over here), (including the two MBN files my carriers use). On the other hand ASUS Modem.img has a very limited number of MBN files, which looks like they haven't updated it since the summer of 1969.
This is the Xiaomi Mi 11 Ultra Modem.img
File on MEGA
mega.nz
This is the ZS673KS (ROG 5) Modem.img
File on MEGA
mega.nz
Since there is no way to upload MBN files to the ROG 5 - Does anyone know whether we can fastboot flash the Modem image ?
Edl try
Akkaya34 said:
Edl try
Click to expand...
Click to collapse
Modem can be flashed over Fastboot.
Not required EDL.
But need to verify whether this has any risks. Only the chip (SOC) brand is same, but internally there might be other differences, and the image sizes are not the same either. So worried of hard brick.
BLOB images have the same code but very different interface to the kernel in most cases, so it's not likely anything will work
yurishouse said:
BLOB images have the same code but very different interface to the kernel in most cases, so it's not likely anything will work
Click to expand...
Click to collapse
Thanks a lot of the headsup !
Would the idea work better with rog 5 u.s modem blob?
Heero0101 said:
Would the idea work better with rog 5 u.s modem blob?
Click to expand...
Click to collapse
US version might have hardware differences .. So im not really sure.
Confirmed not working, restored partitions previously backed up for next surgical op.
katalinscrob said:
Confirmed not working, restored partitions previously backed up for next surgical op.
Click to expand...
Click to collapse
Thanks a lot for trying! Much appreciated!!
No pb! The main issue now that I have volte working along real 5G on both sim slots, is vowifi... PDC was the ideal method, but if sysprop vendor.usb.diag 1 command triggers correct diag mode, then for sure is another issue here, A11 related I guess...
katalinscrob said:
No pb! The main issue now that I have volte working along real 5G on both sim slots, is vowifi... PDC was the ideal method, but if sysprop vendor.usb.diag 1 command triggers correct diag mode, then for sure is another issue here, A11 related I guess...
Click to expand...
Click to collapse
How did you get VoLTE working?
Did you have the MBN inside already?
PDC is sadly blocked in A11 OS mode. However OnePlus Users They have a FTM mode - Which allows Efs tools / PDC to communicate. Hopefully something should come around for Asus.
You need root first of all.
There are 2 ways for permanent volte/vowifi toggle menus:
1. *#*#4636#*#*, set preffered network type NR/LTE, then back to original.
2. Magisk module Pixel5_VoWIFI.VoLTE_magisk_module_V1-MINI.zip (search github)
After this, via EfsTools method just copy to NV your carrier mbn from attached folder, reboot. Tried all of them until found compatible one from my carrier but no VoWIFI sadly.
katalinscrob said:
After this, via EfsTools method just copy to NV your carrier mbn from attached folder, reboot. Tried all of them until found compatible one from my carrier but no VoWIFI sadly.
Click to expand...
Click to collapse
Which thread did you follow?
I had a problem with my device not connecting via WIFI.
Full support 5G+VoLTE+VoWIFI:
1. Flash last A11 firmware WW-18.0840.2201.229 and root it.
2. Through QPST and AsusVOLTE apk, connect via wifi /same IP option ( I used IPV4+IPV6).
3. Download and unrar attached EfsTools, which contains the mcfg.mbn** and load it to NV.
4. Flash A12 firmware WW-31.0810.1226.57.
5. Root again, install voenabler*** module in magisk, restart.
**A11 banner mbn in .rar is for GermanyVodafone.
*** voenabler or any other method you agree with for enabling 4G/VOWIFI menus in settings.
In A12 banner is HW_DEFAULT instead any previous A11 carrier specific mbn, which means that ASUS finally resolved this problem for good.
Later edit: will try to extract and upload modem.img already modded for easy fix this entire stupid issue which Asus could have been more responsive to buyer's needs ...
Enjoy!
Since after .77 update lost again volte and vowifi, so disapointed... Respawned .mbn and voila, back in time with only volte capability, no vowifi.
Because I don't want to get through previous posted procedure, as I would be stuck in .57 basically, I found an alternative solution that could offer updates advantages and minimum-hassle procedure for regaining volte/vowifi, which basically is copying working mbn unpacked files to efs partition via efsExplorer in QPST. I tried mbn from an identical X60 qualcomm/lahaina chipset (found on xiaomi12t) and volte/vowifi working again, but no 5G this time. Anyway, is a matter of pacience and time for testing.
Another solution would be modifying modem.img extracted from Asus payload.bin but I didn't found an easy way to unpack/repack, only managed to open it through 7zip and get some resources. If you can find a solution to this, I think this would be the most elegant way for us to have all modem's capabilities activated, by simply restore modified-modem.img after every update.
And yes, tried AIK, various .img unpackers etc...

Categories

Resources