Being a huge fan of the Pixel series and living in China is not easy. Just upgraded my XL to 3 XL and naturally I had to enable the LTE to work in China. Regardless what you may see on the Chinese forums (gfan), all the files you need are already present on the phone.
Files you need:
1) The ADB bridge for Windows
2) The most recent factory image
3) Magisk Manager
4) Chinese-Carrier-Pixel-3-xl-LTE-VoLTE-Enabler (Magisk Manager module) - Github direct: https://github.com/wangdaning/Chinese-Carrier-Pixel-3-xl-LTE-VoLTE-Enabler (big thank you to wangdaning for allowing me to publish it.) Also attached as a zip file to this post.
If you don't understand what these files are for or where to find them, perhaps you should ask a friend to help you. Flashing anything wrong could result in an expensive brick. Always backup your data, never blindly trust a post, and do your research. This post is in good faith and I am not liable for your actions.
Now, I don't have any of the variants of 3 (Pixel 3, 3a, 3a XL) but I would assume it would work in a similar fashion; however, see above and do your research. Check file structures, read some posts, backup data, etc. If someone does try it, please report both success and failure to build the knowledge.
1) We need to ensure our phone has an unlocked bootloader. If your bootloader is locked, you WILL lose all your data. Ensure you backup everything you want to keep. There is no getting around this step. We need to be a developer first. Go to Setting->About Phone->Build number (tap it until it says you are a developer). Then go to System-> Developer options -> OEM unlocking: turn it on. Next we need to reboot to the bootloader by resetting the phone and hold the down volume key as it reboots. In the bootloader, first use the volume keys to find and select the unlock the bootloader command with the power key. Then, we need to send the following command:
Code:
fastboot flashing unlock
You will receive a wipe and security warning. Accept and reboot the phone. It will wipe and reset your phone to factory.
2) I started from a stock image (May update; QQ2A.200501.001.B2). I suggest you start from there.
3) While we have the May update in front of us, we need to extract the boot.img so it can be patched to root the phone. TWRP doesn't support us at the time of writing on Android 10. (Hope that new baby is healthy!) The boot image can be found in the zip image-crosshatch-*release code*.zip/boot.img. Transfer this boot.img to the phone to be modded to enable root.
4) Next the phone needs to be rooted. You need to download the most recent version of Magisk Manager. Once installed, open up Magisk Manager. It will report no Magisk and that's ok, we are installing it now.
5) Tap install on Magisk and it will ask if you want to install, so install. Then you need to select the method. We will choose "Select and patch a file." Tell it where you saved your boot.img and it will patch it to allow us to root the phone. The output file we need is called magisk_patched.img is on the phone. Move it back to your directory with your ADB bridge.
6) Next we need to flash this patched boot file to our phone to complete the rooting process. Reboot to the bootloader and send the two commands:
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Reboot the phone and congrats, you are rooted with an unlocked bootloader.
7) To prepare for the install of the mock files that will point to the files on the phone, we need to delete a few checking files. Using your file explorer of choice that can gain root access delete the following:
/data/vendor/modem_fdr/fdr_check
everything in /data/vendor/radio/ (make the target folder empty)
8) Download the LTE_enabler from Github or the zip file here. Open Magisk Manager and open the menu -> Modules -> "Yellow Plus" to add. Point it to the zip file.
9) Reboot and enjoy using your phone as intended.
I tried to be as detailed as I could but not be over verbose either. If any step is unclear, there are more detailed guides on this forum concerning bootloader unlocking and Magisk rooting on Android 10. As a bonus tip, does the "x" showing no data bother you and stop some services from working? If so, this can be fixed by re-pointing your captive portal to something inside the firewall. This can be accomplished with one line of code:
Code:
adb shell "settings put global captive_portal_https_url https://developers.google.cn/generate_204"
Enjoy and if you have questions about Pixel and China, feel free to post them. Support right to repair!
I downloaded the zip file but it tells me it's not a module.
jifengSherry said:
I downloaded the zip file but it tells me it's not a module.
Click to expand...
Click to collapse
Could use more details, otherwise it is hard to help. It definitely is a module and installs fine. Something else is going on.
is this for china only? I have a Canadian 3 XL and moved to Bucharest, need to enable VOLTE on Orange Romania. I'm also on Android 11
It should work, but you would have to slightly modify the files. Instead of pointing to the Chinese carrier modem file you would want to point to the orange Romania file. I looked and there is an mbn file for orange Romania, it is just not included in the mbn_sw.txt. Then again, have you made sure Orange has activated VOLTE for your device?
wangdaning said:
It should work, but you would have to slightly modify the files. Instead of pointing to the Chinese carrier modem file you would want to point to the orange Romania file. I looked and there is an mbn file for orange Romania, it is just not included in the mbn_sw.txt. Then again, have you made sure Orange has activated VOLTE for your device?
Click to expand...
Click to collapse
I contacted Orange and they say VOLTE should be working, that the issue is my device not being compatible with their network. I also bought a Samsung watch 3 with LTE and can't activate LTE through my phone, i assume it's due to the same issue.
I'll follow your guide and report back.
Should be no issue if i am using Android 11 instead of 10 right?
Should be fine, you just need to make sure that you modify the mbn_sw.txt file to include the location of the Orange Romania mbn file. You might just try this first:
7) To prepare for the install of the mock files that will point to the files on the phone, we need to delete a few checking files. Using your file explorer of choice that can gain root access delete the following:
/data/vendor/modem_fdr/fdr_check
everything in /data/vendor/radio/ (make the target folder empty)
Click to expand...
Click to collapse
If that does not work then you need to modify the module to include the romania mbn.
wangdaning said:
Should be fine, you just need to make sure that you modify the mbn_sw.txt file to include the location of the Orange Romania mbn file. You might just try this first:
If that does not work then you need to modify the module to include the romania mbn.
Click to expand...
Click to collapse
Dude i love you! worked perfectly. I followed the guide to root Pixel 3 on Android 11 and then your steps, didn't modify anything and now i have VOLTE enabled!
thank you so much!
angeluszero said:
Dude i love you! worked perfectly. I followed the guide to root Pixel 3 on Android 11 and then your steps, didn't modify anything and now i have VOLTE enabled!
thank you so much!
Click to expand...
Click to collapse
ok i spoke too fast, while VOLTE is enabled now in the settings, when i make a call, it switches to H+ which means its not using VOLTE. any idea? I modified the .txt file to include the location of the romania .mbn file, i modified the file directly on the phone though, after installing the module with magisk manager
Not sure, to many variables at play. I mean it could be that orange Romania only has VoLTE in certain areas/cases. Try using *#*#4636#*#* and phone information, see what it says.
wangdaning said:
Not sure, to many variables at play. I mean it could be that orange Romania only has VoLTE in certain areas/cases. Try using *#*#4636#*#* and phone information, see what it says.
Click to expand...
Click to collapse
I did that, both VOLTE and Wifi calling say provisioned. I guess it might be something on Orange's end.
I saw a reddit post for a Pixel 3 having the same issue and the carrier ended up doing something on their side.
Confirmed working on Pixel 3 w/ Android 11!
Can this patch work on Pixel 4 as well? Thank you
duffercn said:
Can this patch work on Pixel 4 as well? Thank you
Click to expand...
Click to collapse
You would have to find the location of the files on the Pixel 4 as I am not sure where they are. Then modify the module to point to the correct location.
Related
I am not a developer but a HW guy.
This applies only to i9505 international version with Qualcomm processor as tested.
Please note that whoever tries the following, upon failure and/or ending up with bricked phone(s), incurring any loss, implied or direct, resulting from the application of what is described in this post, including but not limited to time, warranty, update from Samsung including security updates, resources, financial or otherwise,etc., does not point a finger in my direction but, does so at his/her own risk.
(Hope I scared a few).
The unit that I used originally had XXUHPK2 - XST firmware.
Whatever given below are personally experienced after quite a bit of searching, testing and few near misses including SIM not being detected or infinite loops when searching for network to register due to my own experimentation with Modem and NON-HLOS files.
But I never once lost my IMEI as the method is fairly straightforward. Always God "ODIN" is there to the rescue.
This applies to those who do not want an "always on" Jio4GVoice app and prefer to stay with stock recovery. Of course custom recovery can always be installed.
I have used PI1_VOLTE_JIO FW available on this forum but had faced few issues related to calling out at times, more so when I travel long distance. If I stay put at certain places it always worked.
Now to the works:
1. Using ODIN install I9505XXUPOL1_I9505PHNPOL1_PHN FW. - Search to download FW.
Nordic version of FW with PI1 modem "may" be used but I found network search for registering yields less number of networks. I have not tried using the Nordic FW.
2. Root the device using CF-Auto-Root.
3. Search for "Volte fix.zip" and download. Easiest way to get links to download is YouTube. In the zip file I used all files have 07-11-2016 as creation date. I found VoLTEFiles zip too with the same dates but did not try it so far.
4. Watch the YouTube, say, at "watch?v=MlkaziK6AkY" or any other relevant VoLTE zip file installation video to get the gist of the method before attempting.
5. The zip contains an Apks folder and a Files folder. Extract APK, csc folder, CSCVersion.txt and SW_Confgiuration.xml to a known folder preferably in ext-sd if available.
6. Install root explorer. It is under extracted Apks folder. Allow for installation of app from unknown sources.
7. Open Root Explorer browse to /system directory. Rename existing csc folder, CscVersion.txt and SW_Configuration.xml with some leading characters as fall back. The csc folder and the files can optionally be deleted as well.
Root Explorer will require the patition to be mounted as RW saying it is Read Only. Say OK to proceed.
8. Copy and paste the above folder and files obtained from zip to /system.
9. Change permissions via Root Explorer as below:
Touch the folder or file under Root Explorer. Once selected touch 3 dots on top right and select permissions. Given numbers can be directly entered using Octal button.
csc folder - 755 octal
CscVersion.txt - 644 octal
SW_Configuration.xml - 644 octal
10. Exit Root Explorer and Reboot. And wait patiently for a while until the two way sign appears on status bar. It really takes a while.
Call Settings - "Outgoing voice call settings" automatically shows "Use VoLTE when available".
Factory reset does not restore VoLTE icon on status bar and calling is not possible as well. Wait for a while for the phone to complete all processes after setting up. Reboot to get VoLTE back.
It seems to take a while and the Sammy phone will show a report being sent when connected to WiFi... to inform you later when you select "Software Update" that the phone has modified in an un-authorized way, etc.
Calling and messaging works even with WiFi ON.
I have not provided any link as the credit should go where it belongs.
See screenshots in the attached thumbnails.
ODIN Version used 3.12.7
CF-Auto-Root available on this forum.
And most importantly thanks to the developer who created the VoLTE fix files. And a special thanks to @dhiru1602 with his PI1-VOLTE-JIO ROM as it was instrumental in making me search and test.
Does this work on other S4 not for JIO and on other networks?
treysis said:
Does this work on other S4 not for JIO and on other networks?
Click to expand...
Click to collapse
Sorry for the belated reply. I was using it on Jio only as no other nw providers were offering VoLTE at that time. Now the unit is with someone else in another country. I learnt VoLTE is available in that country and will request to get it checked. Will revert with results.
hey, no problem and thanks for the help! Have you heard back from your friend yet?
treysis said:
hey, no problem and thanks for the help! Have you heard back from your friend yet?
Click to expand...
Click to collapse
Yes and a No - On one network it does not show the icon. He is not sure if the ISP actually implemented VoLTE though announced last year. On the other he has not tested as yet. Says needs to get the 4G SIM. Will wait for some more time and revert again.
Ok. I know for sure that my network and my SIM support VoLTE, cause I am using it on another Samsung handset and it's working fine. But on the S4 no luck yet.
Btw. I just put a Malaysian SIM and this enabled VoWiFi in the settings. But couldn't try it as the card is not fully active anymore.
Is there any new instruction how to force VoLTE and VoWifi to work on PIXEL3?
Features works great on S9, SIM card is provisioned. The IMS options are blacked out on PIXEL.
Does any Custom ROM forces the feature to work even if carrier says that they don't officialy support it?
If it is just that your provider does not allow this service on Pixel you could try MagiskHide Props Config module to change device fingerprint to match a phone that is supported by your carrier. Not sure if it will word, but worth a shot.
wangdaning said:
If it is just that your provider does not allow this service on Pixel you could try MagiskHide Props Config module to change device fingerprint to match a phone that is supported by your carrier. Not sure if it will word, but worth a shot.
Click to expand...
Click to collapse
Carrier says that the issue is not on their side, they claim that they have enabled services. I checked on S10 with the same SIM card, both VoLTE and VoWifi works without issues.
The other thing is that I don't want to dive deep into changing factory images to force the features. I would need to unlock bootloader and root phone.
Until now Google does everything just to avoid questions and providing support for modem issues for other carriers than US.
mxtuu222 said:
Carrier says that the issue is not on their side, they claim that they have enabled services. I checked on S10 with the same SIM card, both VoLTE and VoWifi works without issues.
The other thing is that I don't want to dive deep into changing factory images to force the features. I would need to unlock bootloader and root phone.
Until now Google does everything just to avoid questions and providing support for modem issues for other carriers than US.
Click to expand...
Click to collapse
It might have something to do with the modem files in the vendor partition, we have that issue here in China. Only way to fix that is to be rooted and systemlessly make the phone read the files correctly. Custom roms cannot change the vendor.img.
wangdaning said:
It might have something to do with the modem files in the vendor partition, we have that issue here in China. Only way to fix that is to be rooted and systemlessly make the phone read the files correctly. Custom roms cannot change the vendor.img.
Click to expand...
Click to collapse
;/ so probably there is no easy workaround. Rooting and modem modification makes it too complex. Especially that on Android Q there is a problem with USB debugging mode for Qualcomm in fastboot
PIXEL2: [GUIDE]Enable VoLTE for unsupported carriers
mxtuu222 said:
;/ so probably there is no easy workaround. Rooting and modem modification makes it too complex. Especially that on Android Q there is a problem with USB debugging mode for Qualcomm in fastboot
PIXEL2: [GUIDE]Enable VoLTE for unsupported carriers
Click to expand...
Click to collapse
Rooting is not really dangerous, and the modem modification makes no real changes. It is systemless changes, which means no files are actually modified. What carrier do you use, odd that a US carrier would not be supported natively by google.
wangdaning said:
Rooting is not really dangerous, and the modem modification makes no real changes. It is systemless changes, which means no files are actually modified. What carrier do you use, odd that a US carrier would not be supported natively by google.
Click to expand...
Click to collapse
I need to have an option for carrier PLAY in POLAND.
I'm curious if just a root and enabling VoEnabler packet from MAGISK will be enough.
Some of the guys from PIXEL 2 were suggesting to use modem configs with VoLTE, VoWifi from the same chipsets Qualcomm 845 and putting it to PIXEL 3.
mxtuu222 said:
I need to have an option for carrier PLAY in POLAND.
I'm curious if just a root and enabling VoEnabler packet from MAGISK will be enough.
Some of the guys from PIXEL 2 were suggesting to use modem configs with VoLTE, VoWifi from the same chipsets Qualcomm 845 and putting it to PIXEL 3.
Click to expand...
Click to collapse
That is problematic, as looking at the modem files (on my device), their is nothing under the folders for PLAY network. That would mean you could get the modem file from another similar device that has it, but the magisk setup would need to change two files instead of one. You would have to mock load a mbn file for your provider. You would need to change /mcfg_sw/generic/"modem file you want to try" and /mcfg_sw/mbn_sw.txt to include the directory of the file you want to include.
In reality, those mbn files you get might never work. This is google borking their work. For us in China, the modem files are their, they just refuse to reference them. For you the files are not even there it seems.
Try this. You will need magisk root to do it. You will also need to edit the zip file with the mbn file you can get a hold of. It will go in this file "For Help Pixel 3 LTE-VoLTE Enabler.zip\system\vendor\rfs\msm\mpss\readonly\vendor\mbn\mcfg_sw\generic\EU\Play" directory. It will simlpy load the modem file you need/want/got from a similar device at boot(just name it mcfg_sw.mbn and put it in there replacing the "put mcfg_sw.mbn here.txt"). You also need to delete the files in the description of the module (these are auto generated files) before this will take place. Good luck.
If you are doubtful, have a good look at what I am asking it to do.
wangdaning said:
Try this. You will need magisk root to do it. You will also need to edit the zip file with the mbn file you can get a hold of. It will go in this file "For Help Pixel 3 LTE-VoLTE Enabler.zip\system\vendor\rfs\msm\mpss\readonly\vendor\mbn\mcfg_sw\generic\EU\Play" directory. It will simlpy load the modem file you need/want/got from a similar device at boot(just name it mcfg_sw.mbn and put it in there replacing the "put mcfg_sw.mbn here.txt"). You also need to delete the files in the description of the module (these are auto generated files) before this will take place. Good luck.
If you are doubtful, have a good look at what I am asking it to do.
Click to expand...
Click to collapse
Great, thank you for all the tips. I will try to find some mbn files from NOKIA modems.
Do you know if it's possible to unlock the bootloader, root, make possible changes, unroot, lock bootloader?
Is the modem file will be permanently on vendor partition even if I install newest OTA?
mxtuu222 said:
Great, thank you for all the tips. I will try to find some mbn files from NOKIA modems.
Do you know if it's possible to unlock the bootloader, root, make possible changes, unroot, lock bootloader?
Is the modem file will be permanently on vendor partition even if I install newest OTA?
Click to expand...
Click to collapse
I am pretty sure you will need to keep root, as magisk is mocking the modem file you need. It somehow could cause the phone to connect and after the phone stays connected, but I do not see how that could work.
I'm fairly reluctant to root the phone. I have had an excellent resource on here pretty much warn me against that.
I really want to put a different font on the phone. That's really the only reason I interest in rooting. I'm not wanting it just to be more decorative...I find the bold font hard to read in whatever app may be presenting bold text.
So anyway, l'd hate to do the root (which I understand is not really a full root), and then find it doesn't allow me to install the new fonts anyway.
ewingr said:
I'm fairly reluctant to root the phone. I have had an excellent resource on here pretty much warn me against that.
I really want to put a different font on the phone. That's really the only reason I interest in rooting. I'm not wanting it just to be more decorative...I find the bold font hard to read in whatever app may be presenting bold text.
So anyway, l'd hate to do the root (which I understand is not really a full root), and then find it doesn't allow me to install the new fonts anyway.
Click to expand...
Click to collapse
Rooting is 'full', just that technology (Android 9/10) is changing.
For AdAway app you must enable Systemless hosts (option/module in Magisk Manager), for modules Magisc automatically handles symlinking to the read-only System
So, even from root explorer (sugested MiXPlorer), you see as if AdAway wrote directly to the file system/etc/hosts, or that BusyBox tools are applied directly to system/xbin
Since EMUI 8, Huawei replaced Boot with Ramdisk, and since EMUI 9.1 Ramdisk is also read-only, hence Magisk must patch to Recovery instead
Because of that, you cannot have TWRP if you go for root (don't consider an alternative solution to flash TWRP over erecovery). But formally speaking, TWRP is not part of root (on the old systems, you could have TWRP without root, vice versa, or both). Even with TWRP, TWRP could not change read-only System, and it cannot see dynamical linking active only when system is running (Magisk running). Plus, because of new encryption since EMUI 8, TWRP cannot handle Internal storage (don't consider alternative solution to completely wipe Internal storage and format it without encryption)
All together, from system, systemless works fully seemlessly (as 'full' root). Just you don't use TWRP
To root:
- Install Huawei UpdateExtractor (PC), download update.zip for your 9.1.0.252 c432 from FirmwareFinder, unzip and extract Recovery_Ramdisk.img
- Copy Recovery_Ramdisk.img to the phone, install Magisk Manager, choose Install and then Patch a file, check all three options Preserve AVB, Preserve encryption, Recovery file
- Copy patched_boot.img (rename to patched_recovery.img or so) to PC and flash from Fastboot to Recovery (similar like flashing TWRP) - of course, Bootloader must be unlocked (you have code) and OEM/FRP must be unlocked
- You must boot to system through recovery (because Magisk was patched to recovery), if Magisk Manager shows rooted, you are done
To unroot:
- In case of bootloop or anything: just flash stock Recovery_Ramdisk.img back to Recovery, and you are back to stock
- Regular unrooting: take Uninstall from Magisk (and later, optionally, flash stock recovery_ramdisk.img)
- In case of OTA: unroot (regularly, as above), accept OTA, root again
Btw, you could update your sig now (no more EMUI 5)
Thanks for all the info.
One thing I did not understand from that: will rooting then allow me to add different fonts?
Thanks for the reminder on the sig. I've been thinking of it but procrastinating...which means I would ultimately forget.
ewingr said:
Thanks for all the info.
One thing I did not understand from that: will rooting then allow me to add different fonts?
Thanks for the reminder on the sig. I've been thinking of it but procrastinating...which means I would ultimately forget.
Click to expand...
Click to collapse
Font size can be changed in Settings /Display
I never changed system fonts but there are Magisk modules to do so, search by Google, eg:
https://forum.xda-developers.com/apps/magisk/avfonts-march-6-t3760827
https://forum.xda-developers.com/apps/magisk/module-midnightcore-one-midnight-modules-t3762758
Maybe I just am having a mental block...I can't find the firmware in FF. I searched on each of these as criteria:
MHA-L129C432
MHA-L129C432E7R1P8
9.1.0.252
9.1.0.252 c432
MHAJ-L129C432 9.1.0.252
None of those searches found a FW for L129 for the 9.1.0.252 version. I did see a lot for MHA-LGRP2.
I used FF on the phone. I downloaded FF for the PC, and can't figure out how to use it. I put a model in on the Main Page, nothing happens. I see no way to put a model in on the Search Firmwares page.
Of course, I was updated to 9.1 via OTA, so all the work I did getting to 9.1 did not involve downloading the firmware to my PC, so I don't have it from all that work.
ewingr said:
Maybe I just am having a mental block...I can't find the firmware in FF. I searched on each of these as criteria:
MHA-L129C432
MHA-L129C432E7R1P8
9.1.0.252
9.1.0.252 c432
MHAJ-L129C432 9.1.0.252
None of those searches found a FW for L129 for the 9.1.0.252 version. I did see a lot for MHA-LGRP2.
I used FF on the phone. I downloaded FF for the PC, and can't figure out how to use it. I put a model in on the Main Page, nothing happens. I see no way to put a model in on the Search Firmwares page.
Of course, I was updated to 9.1 via OTA, so all the work I did getting to 9.1 did not involve downloading the firmware to my PC, so I don't have it from all that work.
Click to expand...
Click to collapse
Look for MHA-LGRP2-OVS - see screenshots.
You can also find through Web:
https://pro-teammt.ru/firmware-database/?firmware_model=MHA-LGRP2-OVS
Btw, there are several b252 packages there, all the same size (and probably all ok) but I was told that package number #279403
is the one that is distributed by OTA
Thanks.
I saw the MHA-LGRP2-OVS ones, but I thought I needed to find one with identical name to the one I'm on.
This stuff doesn't make much sense...at least not logical. Only experience and/or help makes it possible to get it done.
Appreciate y our help.
Well, I don't know what's going on. I downloaded the FW from the link you provided, as well as from FF on the phone.
The one from the phone, once I transferred it to the PC, wouldn't extract anything from the zip.
The one from the link extracted, but when I loaded the Update.app into Update EXtractor, I got this error:
So, I then downloaded a different version from the web site (282444), and got this in Update Extracter:
Maybe it's warning me to not root:silly:
I am going through the thread about the extracter tool now to see if I find anything helpful. First blush looks like I'd need to make a profile file that is outside the limits of my knowledge. We'll see.
I found a post saying:
Try with crc check off (in settings) for extracting
Click to expand...
Click to collapse
So I turned off the settings outlined in red:
I ended up with these two files and sizes:
Do those sizes look right?
ewingr said:
I found a post saying:
So I turned off the settings outlined in red:
I ended up with these two files and sizes:
Do those sizes look right?
Click to expand...
Click to collapse
Yeah, I also switched checksum off and it showed things as usual.
Extracted Recovery-Ramdisk (32 MB is usual size, you need only that IMG file):
https://mega.nz/#!g4lwiCIC!ikK7xJk2j1G9aSsIj1y0sQsV_s6pWTcrxCJtn56YCik
Btw, now having also service repair package for MHA-L29 9.1.0.252 c432E7R1P8 (like you used MHA-L29c432b386), i.e., suitable for DLOAD installation (if anything goes wrong):
https://www.androidfilehost.com/?fid=4349826312261725171
zgfg said:
Yeah, I also switched checksum off and it showed things as usual.
Extracted Recovery-Ramdisk (32 MB is usual size, you need only that IMG file):
https://mega.nz/#!g4lwiCIC!ikK7xJk2j1G9aSsIj1y0sQsV_s6pWTcrxCJtn56YCik
Btw, now having also service repair package for MHA-L29 9.1.0.252 c432E7R1P8 (like you used MHA-L29c432b386), i.e., suitable for DLOAD installation (if anything goes wrong):
https://www.androidfilehost.com/?fid=4349826312261725171
Click to expand...
Click to collapse
Sounds good
So, I figured I need to start by re-unlocking my phone. But at the site for DC Unlocker, the following message seems to indicate I can't unlock:
WARNING:
If your phone runs Android 8 or later with latest security patch - then this service won't work!
Click to expand...
Click to collapse
I'm on Android 9 with security patch 3.
ewingr said:
Sounds good
So, I figured I need to start by re-unlocking my phone. But at the site for DC Unlocker, the following message seems to indicate I can't unlock:
I'm on Android 9 with security patch 3.
Click to expand...
Click to collapse
OMG - I think Im writing you THIRD or FOURTH time that the same unlock code you obtained will still work!!!
Because the code is bound to the serial number of your phone and will work for unlocking/relocking for the lifetime of your phone
Huawei is just making harder and harder to obtain the code (in the old days Huawei was giving the codes immediately and for free through their own page, now with the new EMUI versions it is needed to physically open the phone and use Testpoints and code providers charge you 30 Euros or more) but once you have a code (no matter when and how you obtained) , you can use the code the same way as always (fastboot oem unlock/relock ...)
zgfg said:
OMG - I think Im writing you THIRD or FOURTH time that the same unlock code you obtained will still work!!!
Because the code is bound to the serial number of your phone and will work for unlocking/relocking for the lifetime of your phone
Huawei is just making harder and harder to obtain the code (in the old days Huawei was giving the codes immediately and for free through their own page, now with the new EMUI versions it is needed to physically open the phone and use Testpoints and code providers charge you 30 Euros or more) but once you have a code (no matter when and how you obtained) , you can use the code the same way as always (fastboot oem unlock/relock ...)
Click to expand...
Click to collapse
OMG, yes, you have. BUT the site that provided the method to do it says it won't, per the quote I put in my post. I'm inclined to believe you, you have been a very good source and patient. But, I was wondering why would they say it won't work? That is their exact words, about their tool.
That being said, I guess as that I had the code before upgrading to 9, then just following the fastboot commands with that code will work, and in fact doesn't even use their tool. . So, I'll continue with that then. The information out here can sure be confusing.
Thanks...
[EDIT]
I figured that likely it would be the ramdisk.img file, and through Google search I found a thread that verified that. So, I'm continuing on.
Thanks...
Here's an interesting thing.
After patching the file, and seeing the instructions here, I find that the file they referenced in Downloads is a different size from the one I selected to patch, which was the RECOVERY_RAMDIS.img.
Do you think that indicates a problem? I presume I should use the one I selected, which was your instructions, but wonder if maybe something went wrong with the patch.
Again, just being cautious.
Thanks for your help.
56_kruiser said:
Here's an interesting thing.
After patching the file, and seeing the instructions here, I find that the file they referenced in Downloads is a different size from the one I selected to patch, which was the RECOVERY_RAMDIS.img.
Do you think that indicates a problem? I presume I should use the one I selected, which was your instructions, but wonder if maybe something went wrong with the patch.
Again, just being cautious.
Thanks for your help.
Click to expand...
Click to collapse
So, are you the same as previously, @ewingr?
If so, have you successfully unlocked Bootloader with that old code
OpenKirin instruct to patch Ramdisk and that was correct for EMUI 8.
(If) yu are on EMUI 9.1, hence you need to patch and flash Recovery Ramdisk
When patching from Magisk Manager (MM), you have to check all three options: Preserve AVB 2.0 DM-Verity, Preserve Force Encryption and Recovery Mode.
Does MM report any error while flashing or success/ok?
You can rename patched_boot.img to like patched_recovery.img, doesn't matter, but you must flash it to Recovery (like flashing TWRP to Recovery).
Right after flashing, boot by key combo to that patched Recovery (like booting to TWRP by key combo, after flashing TWRP).
Of course, you will not flash/use TWRP here
I don't imagine you'll find this hard to believe, but I got an error on the flash attempt
I renamed the patched file to: Patched_RECOVERY_RAMDIS.img
I entered this command:
fastboot flash ramdisk Patched_RECOVERY_RAMDIS.img
Click to expand...
Click to collapse
I got this response:
target reported max download size of 471859200 bytes
sending 'ramdisk' (32768 KB)...
OKAY [ 0.721s]
writing 'ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.757s
Click to expand...
Click to collapse
56_kruiser said:
I don't imagine you'll find this hard to believe, but I got an error on the flash attempt
I renamed the patched file to: Patched_RECOVERY_RAMDIS.img
I entered this command:
I got this response:
Click to expand...
Click to collapse
Again, if you are on EMUI 9.1, forget Open Kirin instructions (for EMUI 8).
You must patch Recovery Ramdisk and flash to Recovery Ramdisk, so:
fastboot flash recovery_ramdisk Patched_RECOVERY_RAMDIS.img
I did in fact not use anything from the OpenKirin. But I apparently used wrong syntax for the command. But you providing that will help.
.......
It didn't work at first pass. I think this is why.
You will recall that in the discussion I had about the OpenKirin instructions that I mentioned they referenced a patched file in Downloads. Well, stepping through it again, and reading the small print, it says "Patched file is in downloads". So, it did not update the file I had put there, it used that to create a new patched file that was saved in downloads.
So, I will not go ahead and download that one and continue with the instructions. I bet it works this time.
---------- Post added at 10:04 PM ---------- Previous post was at 09:41 PM ----------
I think I have success. But of course, a couple interesting things:
So, you indicated I need to "boot through recovery". So I expected to hold power, and vol-up to boot into recover. But it booted to the phone.
I got a request to grant Superuser to Tasker, which I did.
I loaded Magisk, and it says it is installed, but doesn't have any indication if it is rooted. I presume it is, given the request for Superuser for Tasker.
Just now had it pop up with a notice that there is an important system update patch. I don't know if I can stop it, or if I should care about it. I did say "later" so for now, it is not installing.
One other question: Is the method to have root accomplished in the future by booting with Power+Vol-UP? If not done that way, it boots non-rooted? (I ask because it did get booted up w/o holding pwer+vol-up, and it did not show Magisk installed. After that was when I booted with the key sequence.
56_kruiser said:
I did in fact not use anything from the OpenKirin. But I apparently used wrong syntax for the command. But you providing that will help.
.......
It didn't work at first pass. I think this is why.
You will recall that in the discussion I had about the OpenKirin instructions that I mentioned they referenced a patched file in Downloads. Well, stepping through it again, and reading the small print, it says "Patched file is in downloads". So, it did not update the file I had put there, it used that to create a new patched file that was saved in downloads.
So, I will not go ahead and download that one and continue with the instructions. I bet it works this time.
---------- Post added at 10:04 PM ---------- Previous post was at 09:41 PM ----------
I think I have success. But of course, a couple interesting things:
So, you indicated I need to "boot through recovery". So I expected to hold power, and vol-up to boot into recover. But it booted to the phone.
I got a request to grant Superuser to Tasker, which I did.
I loaded Magisk, and it says it is installed, but doesn't have any indication if it is rooted. I presume it is, given the request for Superuser for Tasker.
Just now had it pop up with a notice that there is an important system update patch. I don't know if I can stop it, or if I should care about it. I did say "later" so for now, it is not installing.
One other question: Is the method to have root accomplished in the future by booting with Power+Vol-UP? If not done that way, it boots non-rooted? (I ask because it did get booted up w/o holding pwer+vol-up, and it did not show Magisk installed. After that was when I booted with the key sequence.
Click to expand...
Click to collapse
Magisk by default means you have root. You can install and disable modules in Magisk Manager, but you cannot disable root - for that you must Unistall Magisk (an option in Magisk Manager).
In MM you have a tab/menu showing all apps that were granted root - you can suspend or even revoke to some
Check in Settings/About, does it show you have b252 or b252 Patch03. I think that it thinks you are on b252 without Patch03, and it wants to install that patch.
But I don't know would you loose Magisk if you accept (or even get bootloop), so better disable authomatic OTA updates for now.
Believe me, similar 'Important' patches were receiving users (starting at the same time) with various Huawei phones running EMUI 9.1, discussing on XDA what it was, but there was never an answer, nobody detected any change for something better or worse.
So you don't loose anything if About showing b252 without Patch03
To boot to Magisk you must boot with Vol+ pressed - with USB discinnected.
If connected by USB to charger or PC, booting with Vol+ pressed will boot to eRecovery.
Normal booting (without Vol+ pressed) boots to the system (Android), but with Magisk disabled (MM will say that Magisk is not installed), so no root.
Reboot again with Vol+ and you are again rooted
If it ever comes an OTA for higher than b252, you will have to Uninstall Magisk from Magisk Manager and then accept OTA (and root by yhe same procedure one more time, with recovery_ramdisk.img from the new firmware).
Anomoly with root...
Root is working, albeit with anomalies.
If I boot w/o going through the recovery/Magisk, the phone boots up w/o root, and all works fine. When I go through recovery/Magisk, it comes up rooted, but with the following untenable anomalies: Dialer/Phone does not load; Contacts are not available; As result calls I receive do not show who is calling, and I cannot make calls out.
Given that changing fonts do not give me the fix I was chasing (see this thread), I may, unroot. But given that I can boot up w/o root and it works fine, I'll hold off un-rooting for a bit.
** USE THIS AT YOUR OWN RISK.
** READ THROUGH THE STEPS BEFORE ATTEMPTING. IF AT ANY POINT WHILE READING THESE STEPS YOU GET CONFUSED, YOU PROBABLY SHOULDN'T ATTEMPT THIS.
** BACKUP YOUR FILES AND APP DATA AS THIS WILL WIPE YOUR PHONE.
** BACKUP YOUR WORKING MODEMST1/2 AND PERSIST PARTITION IMAGES WITH BEFORE CONTINUING. THESE PARTITIONS ARE DEVICE UNIQUE, SO IF SOMETHING HAPPENS TO THESE PARTITIONS DURING THE CONVERSION, AND YOU DON'T HAVE A BACKUP, NOT EVEN MSM DOWNLOAD TOOL CAN SAVE YOU. YOU'LL HAVE TO SEND YOUR DEVICE BACK TO ONEPLUS FOR REPAIR. If YOUR PHONE IS ALREADY ROOTED, I RECOMMEND USING PARTITIONS BACKUP AND RESTORE TO DO THIS. JUST REMEMBER TO COPY YOUR BACKUPS OFF YOUR PHONE BEFORE YOU GET STARTED.
** BE SURE TO HAVE MSM DOWNLOAD TOOL AT THE READY FOR IF SOMETHING DOES HAPPEN. FOR THE T-MOBILE ONEPLUS 9, YOU CAN GET IT HERE: https://forum.xda-developers.com/t/oneplus-9-11-2-22-2-t-mobile-msm-download-tool.4276119/
THIS METHOD REQUIRES AN UNLOCKED SIM AND BOOTLOADER
If you don't wish to unlock either, craznazn has released a MSM conversion package you can use to acomplish the same thing without requiring ether to be unlocked. Just download the package from their post, and follow the steps on their 8T MSM Conversion guide, as the steps should mostly be identical.
* I've successfully done this ONCE on my own personal T-Mobile OnePlus 9
* The script used here is just the same one made by craznazn to convert the T-Mobile OnePlus 9 Pro to EU firmware. I just swapped EU OnePlus 9 Pro images for the Global OnePlus 9 images and wrote a bash script for non-Windows users to use. You can just download my conversion package and follow their steps if you want. Just for convenience I'll also be writing the steps on how to use it here as well.
* You can drag and drop my bash script into craznazn's conversion package to use their package on non-Windows systems. You can download the bash script by itself here: https://gist.github.com/Lomeli12/73825a287d3cf60414e244aece9b6bdf
* This package will install Global Firmware 11.2.2.2. You'll need to use Oxygen Updater to update it to the current version (or at least until System Update can do it for you).
* Use the latest platform tools, either from https://developer.android.com/studio/releases/platform-tools or through your package manager of choice (apt, brew, scoop, etc). DO NOT USE MINIMAL ADB, it has not been updated for years.
* If you're having issues with either adb or fastboot detecting your device, consider installing the Universal ADB Driver.
* Have any issues? Describe the steps you take, copy the script's output log, and take screenshots. Include the output of fastboot --version in your post.
Now with all that out of the way...
Steps to convert your T-Mobile OnePlus 9 to the Global (or other) firmware
Unlock your bootloader and SIM. See https://forum.xda-developers.com/t/how-to-unlock-the-t-mobile-bootloader.4256319/
Download and unzip the conversion package:
Global 11.2.2.2
MD5: 14e0c5e41df26bacbc11fe7e69a63c0e
SHA256: 10801f12c50e2d9a7e8085d113ac4a90ab312018beb84a10fa4c1a0f84fc95eb
Google Drive: https://drive.google.com/file/d/1h7Hpbde40wLYynUIo83TTIoERhA_04nS/view
AndroidFileHost: https://www.androidfilehost.com/?fid=2188818919693806454
Spoiler: If you want to use a newer or different region firmware, delete all the *.img files from my conversion package and do the following:
Download and unzip the firmware you want from the OxygenOS Repo thread. You'll specifically want to extract the payload.bin file.
Install Python 3 and Python Protobuf. Figure out how to do this on your own system.
Download cyxx's extract android ota payload script from GitHub: https://github.com/cyxx/extract_android_ota_payload/
Place the payload.bin you extracted earlier into the same directory as the extract_android_ota_payload.py script.
Run the extraction script and wait. This step usually takes a while to complete
Bash:
python3 extract_android_ota_payload.py payload.bin tmp/
Open up the tmp folder the script created and copy all the image files from there over to where flash_all scripts are located.
Boot to bootloader
From adb:
Bash:
adb reboot bootloader
From fastboot/bootloader:
Bash:
fastboot reboot bootloader
Execute either flash_all.bat or flash_all.sh from the unzipped conversion package.
Reboot into recovery and wipe everything
Once fully booted and setup, use Oxygen Updaterto update your phone to the latest version the app provides. Oxygen Updater will provide steps on how to use the full OTA zip.
After you've updated using Oxygen Updater, go into Settings -> System -> System Updates and check for new updates, as Oxygen Updater usually takes a few days to have the absolute latest OTA available. If there is another update available, go ahead and let the System Updater do its thing.
Do a regular system reboot, NOT into recovery, bootloader, or fastbootd.
NOTE: The following steps (8-10) may or may not be optional, we haven't 100% figured it out yet
Repeat step 3 to get back into the bootloader.
Flash the T-Mobile modem included in the conversion package
Bash:
fastboot flash modem NON-HLOS.bin
After each full OTA you take in the future, repeat steps 8 and 9 again.
Fixing SafetyNet by installing Magisk
When I first did this on my own phone, my phone would fail SafetyNet, specifically with a CTS Profile Mismatch. Once I installed Magisk and enabled MagiskHide, however, SafetyNet was passed once more. No MagiskHidePropConfig or UniversalSafetyNetFix required. Here are the steps I did.
Make sure you've updated your phone to the absolute latest version of OxygenOS you can. See step 6 of the conversion steps on how to do so.
Copy the boot.img from the conversion package onto your phone.
Install Magisk Manager onto your phone.
Open Magisk Manager and patch boot.img
Tap Install
Select Select and Patch a file and tap Let's Go
Choose the boot.img file we copied over and hit okay
Once the patch is finished, copy the patched boot.img back onto your PC. Magisk Manager usually puts it in your phone's downloads folder as magisk_patched-<current magisk version>_<random string of characters>.img. The logs in Magisk Manager will tell you exactly what it named the patch image as.
Boot to your bootloader. See step 3 of the conversion steps for this.
Boot your phone using the patched boot.img
Bash:
fastboot boot magisk_patched-<current magisk version>_<random string of characters>.img
Once your phone has booted up, open Magisk Manager once more
Go into Magisk Manager settings and enable MagiskHide.
Back out of the settings and install Magisk via Direct Install
Reboot your phone normally. You should now have Magisk and pass SafetyNet.
Issues so far:
Using EdXposed Hide on the Google Play Store or Google Play Services can cause a soft brick requiring resetting your device via recovery. No issues with LSPosed so far.
Google Phone dialer doesn't display option for Visual Voice Mail. The T-Mobile Visual Voicemail app can be used though.
What appears to work:
Everything else
Edit 1 (5/17/2021):
Fixed some wording that I felt was awkward after the fact.
Made a note that flashing the T-Mobile modem may be optional, still up in the air on that.
Included download mirror for AndroidFileHost.
Listed EdXposed softbrick reported by @Josh McGrath.
Edit 2 (5/19/2021):
Added note about VVM missing from Google Dialer, but T-Mobile VVM app being a good alternative.
Adjusted phrasing in modem flashing steps
Edit 3 (6/7/2021):
Added link to craznazn's MSM conversion tool, which is a good alternative for those who don't want to unlock their bootloader.
Excellent. I've been waiting for this. For partition backup, using the MSM readback functionality (password is usually oneplus) is also an option.
If the OP9 is anything like the OP8T, a direct Euro conversion would be better for quicker updates.
Getting to Euro from Global in a GUI-based approach is also possible. Just set the device ID to OnePlus 9 (EU) in Oxygen Updater and follow the rest of the main guide. You might need to enable advanced settings and ignore device mismatch warnings though. Assuming you are already rooted at this point, you can keep root after the local upgrade, but before rebooting, by flashing Magisk to the inactive slot. Modem still needs to be reflashed.
Modem in general is going to be a pain. Somebody will need to extract it from each T-Mobile OTA if you want fixes and new carrier aggregation combos.
Note: I have not tested this and this is not advice. Follow at your own risk.
He said the TMobile modem files were in the download. Are those 2 files not the correct ones or something?
Or are you just talking about updating the modem every time Tmo sends out an update. (which is usually every 3 months )
Talking about modems in OTAs.
That will be a pain to get any updated modem images, but 1) we just need one person who's willing to stay on the T-Mobile firmware and dump it. Just need to find this willing person and 2) like @Josh McGrath said, expecting T-Mobile OTAs to come frequently, especially those with substantially changes to the modem.img, might be giving T-Mobile too much credit.
Just wanted to say thank you to @Lomeli12 for this tutorial! Also..
After following this guide, and updated through oxygen updater to 11.2.4.4 then 11.2.5.5 from factory OTA . I have full 5g internet and phone signal, without ever flashing modem non-HLOS.bin.... has anyone else had this luck? or am I the only one???
Jg1234 said:
Just wanted to say thank you to @Lomeli12 for this tutorial! Also..
After following this guide, and updated through oxygen updater to 11.2.4.4 then 11.2.5.5 from factory OTA . I have full 5g internet and phone signal, without ever flashing modem non-HLOS.bin.... has anyone else had this luck? or am I the only one???
Click to expand...
Click to collapse
I also noticed this on my phone. I still flashed the T-Mobile modem.img just for network compatibility, but it is possible we don't even need the T-Mobile modem.img to begin with.
Lomeli12 said:
I also noticed this on my phone. I still flashed the T-Mobile modem.img just for network compatibility, but it is possible we don't even need the T-Mobile modem.img to begin with.
Click to expand...
Click to collapse
I know they have trouble with the pro version, so far I haven't had any issues. I will report back after the weekend and test it more while I travel, but don't think that will make a difference. Maybe others can test too!
I was about to do this but I've been using Minimal ADB of course but I downloaded platform tools from the link, unzipped it and ADB.exe won't work. It immediately closed.
Anyone had this issue?
And I didn't read that sentence correctly. Any specifics on what adb error ya got
No prob on the misreading my post bro.
There are no errors, it just simply will not stay open. It opens and immediately closed down. I've downloaded it twice already. Any idea? Win 10
Again, sorry. Completely misread the sentence. Without getting logs or anything more specific than "adb.exe isn't working", we can't really help you.
Not a problem. And yes I totally understand that. I was hoping it was a known easy fix that someone knew but I guess not. But thanks for your help anyhow and will ask again if I can't get it working and get the logs.
Just to test things out and see if adb is working, verify that you don't have minimal adb installed anymore and run
Bash:
adb devices > log.txt
and copy whatever got piped into log.txt.
Minimal ADB is too old. Follow directions.
You may need to set PATH for ADB or put everything in the same folder.
LLStarks, I said I was not using min adb. However, I was able to fix my issue by doing the exact rookie error you stated. :Facepalm.
But I got it all converted over now as of last night and everything is working great so thank you for this guide, Lomeli12.
The new edxposed has an Xposed hide option and I will say to NOT try to hide the play store or play services with this cause it soft bricked me and had to do a master reset via recovery. Just a fyi for anyone trying to hide for safety net. (I did use it for Snapchat and it works)
Josh McGrath said:
LLStarks, I said I was not using min adb. However, I was able to fix my issue by doing the exact rookie error you stated. :Facepalm.
But I got it all converted over now as of last night and everything is working great so thank you for this guide, Lomeli12.
The new edxposed has an Xposed hide option and I will say to NOT try to hide the play store or play services with this cause it soft bricked me and had to do a master reset via recovery. Just a fyi for anyone trying to hide for safety net. (I did use it for Snapchat and it works)
Click to expand...
Click to collapse
Good that you've resolved your issue. I've only tried with LSPosed without issue or triggering SafetyNet, but I'll make a note of it for EdXposed.
After replacing the flash, does the VVM voicemail in the dialer work?
After replacing the flash, does the VVM voicemail in the dialer work?
iSkyJIE said:
After replacing the flash, does the VVM voicemail in the dialer work?
Click to expand...
Click to collapse
Can confirm Visual Voicemail does work, so does the Dialer.. Although, i don't recognize the dialer as the oneplus stock one... someone else may be of better use for an answer for that, as I have never used the stock dialer. Although, one slight issue with the conversion.. And it doesn't seem as if anyone else is having this problem.. After I updated to 11.2.4.4 via oxygen updater, I can't get OTA to work.. It starts for two seconds and says Update Failed.. I'm not sure what I could have done wrong, I followed the steps 100% and the only thing I could think of that could have caused it is that when I rooted before this process (while still on the T-Mobile ROM), I accidentally flashed the boot.img from the EU version instead of boot it. I tried to flash the boot img that was in the ZIP package from the download above, and still didn't fix it. Hoping I or someone could figure this one out.
Hello, This is a work in progress guide to help you with rooting your phone for whatever reason (i root it to use the Automate app as i am lazy)
I hope this is not a total mess, i will edit this if you have too much trouble reading
DISCLAIMER /!\
• Please consider that you follow this guide at your own risks, i am a random person in the internet, if you do not trust any part of this guide, dont follow it!
• I am adressing this guide to experimented users, i have probably missed a lot of steps and i will try to correct myself, (or not, it takes time sry)
• i am from Europe; not a native english speaker + a noob in the field. feel free to criticize, but be elaborate to help others
I did this on the GALAXY A53 5G phone with :
• Build ver. SP1A.210812.016.A536BXXU1AVCC
• One UI 4.1
• Android Version 12
The following is needed in order to speedrun this :
+MAGISK25.1
+LZ4
+ODIN3.14
+YOUR BOOT.IMG (FROM THE AP_ FILE OF THE FIRMWARE)
1) On your phone go to Settings -> About phone
2) Then -> Software info
3) Check at (the 6th line) ; BUILD Versionfor me it was:
SP1A.210812.016.A536BXXU1AVCC
4) You will have to download yours at sammobile or any other website you trust more : (needs an account but then is free to download)
Download Samsung Galaxy A53 5G SM-A536B firmware
Download the latest Samsung firmware for Galaxy A53 5G with model code SM-A536B. Check out our free download or super fast premium options.
www.sammobile.com
Then when you have you files , the one that matters is the one starting with AP_
5) extract the boot.img.lz4
6) download one of the versions of LZ4 from : https://github.com/lz4/lz4/releases
7) extract all files into a folder
8) drag and drop the extracted file from part 5) INTO the .exe file from part 7)
YOU HAVE YOUR BOOT.IMG
9) Now drag and drop this Boot.img INTO your phone
The version 25.1 of Magisk (or above is needed ? as i used that version of magisk to root my phone i guess)
10) Install it on your A53 you can download it from :
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
11) inside the app, click on INSTALL (written in blue on top right)
12) select the only option
13) go to the boot.img (that you dropped into your phone at part 9)
14) wait
15) when it is done, plug your phone again if you unplugged it and drop the new file generated by MAGISK into your computer and rename it boot.img.tar
Unlock the bootloader of your phone by either ;
• Watch a tutorial it helped me understand why i kept having an error while doing the next steps (i "unlocked" OEM only within dev options, that wasn't enough)
and skip to 22)
• Or follow these steps
on your A53 go developper mode by clicking 7-10 times on the VERSION in settings -> about phone -> Software
turn on the switch for OEM unlocking (wifi must be connected if the button doesnt appear)
and i am not sure if we need to but , turn on the switch for USB DEBUGGING as well (for adb)
16) stay pressed on both VOL UP + VOL DOWN
17) plug your phone to computer
18) wait
19) long press VOL UP
20) wait
21) press VOL UP
ez
So now get ODIN 3.14 on ur computer
I got the official website but cant remember where from, i will look into it, maybe you can find it on google but be carefull of malicious ones i swear !
(if you are kind enough you will share it below ♥)
22)after launching ODIN
23)The on the AP button put your boot.img.tar file that you got from part 15)
24) on your A53 go developper mode by clicking 7-10 times on the VERSION in settings -> about phone -> Software
25) check that you wave wifi connected
26) go to dev options and check if OEM unlock is grey'd out
30) turn OFF your A53 phone
wait for it to BZZZZZZZZ (viber)
31)STAY PRESSED onto the 2 buttons VOL UP + POWER
on recovery choose the 2nd option with your volume keys, "reboot to bootloader"
then if odin recognise the phone press start
This looks like a great guide. Too bad OEM Unlocking doesn't appear on US carrier phones, or else I'd totally do this :/
sorry if i sound stupid but how do i get the boot.img.lz4 file?
This does NOT work on VD7 or most likely later with Magisk 25.1/25.2 (the BL is unlocked on this SM-A536B as I get the warning on reboot and the OEM unlocked is on and greyed out in developer options).
I used the patch the entire AP file method in Magisk and flashing the patched AP file (you can google T505N XDA root Samsung; I will find the forum link later and remember to post it here (this method works on VD7 and probably higher)
I am now rooted with TWRP, thanks to this site, https://www.droidwin.com/install-twrp-recovery-and-root-samsung-galaxy-a53-5g/
Still cannot delete system/app, system/priv-app (not even in twrp) but am able to access data/app (and remove .digest and .dm files)
crazyut said:
I used the patch the entire AP file method in Magisk and flashing the patched AP file (you can google T505N XDA root Samsung; I will find the forum link later and remember to post it here (this method works on VD7 and probably higher)
Click to expand...
Click to collapse
Confirmed, works with VG1 and latest VGA. I used patched AP along with BL, CP and (Home) CSC. Please note that you have to do a factory reset after this, so remember to backup your data properly.
Hlo I rooted my a53 5g thanks to you but cannot remount system partition as read write
I get this output after running
Code:
mount -o remount,rw / <
'/dev/block/dm-0' is read-only
Please help me with it
And also cannot disable dm-verity flashed disable-dm-verity.zip but after formatting data device stuck in bootloop...
Hello. I am new to programming. I have a rudimentary knowledge of android, i.e. whatever I figured out while jailbreaking JP5 and JP6 Securus tablets, and I await academic coursework for formal education in computer hardware and software engineering.
Clarity and redundancy is greatly APPRECIATED regarding any replies to my post.
The question(s) are, what benefits would I obtain from rooting my A53, what about the Cons? I Can I improve the performance of my phone, processing data, etc.
Afterwards in the future, can I still flash the Android 13 firmware? Does Samsung find out?
I know I have to read up, I am being lazy.
THANK YOU.
JoseAndDiezel104 said:
Hello. I am new to programming. I have a rudimentary knowledge of android, i.e. whatever I figured out while jailbreaking JP5 and JP6 Securus tablets, and I await academic coursework for formal education in computer hardware and software engineering.
Clarity and redundancy is greatly APPRECIATED regarding any replies to my post.
The question(s) are, what benefits would I obtain from rooting my A53, what about the Cons? I Can I improve the performance of my phone, processing data, etc.
Afterwards in the future, can I still flash the Android 13 firmware? Does Samsung find out?
I know I have to read up, I am being lazy.
THANK YOU.
Click to expand...
Click to collapse
While I don't have a Galaxy A53, I can speak from experience that almost all Samsung phones suffer from the same pros and cons to rooting
Let's start with the pros:
Using a system-wide adblocker like Adaway is much more battery friendly and more effective using it on root mode than any non-root alternative. This one is the main reason a lot of people root and I think it merits it, it's a really amazing ad blocker.
You'd be able to activate some features that Samsung likes to disable on A-series, like full edge lighting and the camera privacy toggle (I don't know if it's disabled on A53 by default but I'm leaning towards yes)
You get to experiment with GSI and maybe some custom ROMs in the future
You can install some neat Magisk modules like the Pixelify module for example, that tricks Google Photos and lets you have unlimited space like the Pixels have.
With root, you have almost unlimited possibilities of modding your phone, it's just a matter of knowing what you want to modify and finding the right mods to it.
Now, the cons:
Samsung phones have an e-fuse. Flashing custom firmware automatically trips this fuse and it is impossible to recover from unless you change the motherboard. When this fuse is blown, you will never be able to use Samsung's security features like Samsung Pass, Pay, Secure Folder, Secure Wifi, etc...
Even if you flash your stock firmware and even if you re-lock your bootloader, the fuse will still be blown.
There are some regions which even deny any warranty claims if they find out that this fuse is blown, but some places in Europe still accept the phone in this condition.
Another con is that sometimes some apps refuse to work if they detect you are rooted like Google Pay and I believe Netflix and others too (like banking apps). Some are easy to fool/bypass root detection and some are more complicated. It all depends on the app.
And to answer your final question. Fortunately for you, you still should be able to flash the latest stock firmware and if you re-lock your bootloader, you should still be able to receive updates via OTA, just keep in mind of the services that will never work again I mentioned above
Hello. I am following up with my previous post.
I found the exact zip and Odin file at Sammobile. Would this be a good start? My understanding is that the bootloader option is not available yet
...
I am learning as I go and before I move forward (big IF) I want as many redundancies as I can.
JoseAndDiezel104 said:
Hello. I am following up with my previous post.
I found the exact zip and Odin file at Sammobile. Would this be a good start? My understanding is that the bootloader option is not available yet
...
I am learning as I go and before I move forward (big IF) I want as many redundancies as I can.
Click to expand...
Click to collapse
I din't have unlocking bootloader option. But I did:-
1)factory reset phone
2)insert sim
3)restart phone
4)enable developer mode
5)And you will get a message "Welcome to Samsung your device is registered"
6)that's it OEM unlocking option will be avilable
7)power off phone
8)holding vol +&- keys connect usb to pc
9) leave both keys after you see waring messages
10)press and hold volume + key , bootloader will be unlocked and phone will be factory resetted.
aryanrh said:
I din't have unlocking bootloader option. But I did:-
1)factory reset phone
2)insert sim
3)restart phone
4)enable developer mode
5)And you will get a message "Welcome to Samsung your device is registered"
6)that's it OEM unlocking option will be avilable
7)power off phone
8)holding vol +&- keys connect usb to pc
9) leave both keys after you see waring messages
10)press and hold volume + key , bootloader will be unlocked and phone will be factory resetted.
Click to expand...
Click to collapse
Would this work for US phones?
nsfxpython said:
Would this work for US phones?
Click to expand...
Click to collapse
Unless you find a a hack, any U/U1 (USA/United States/The States/States/American/America) and W series (Canada) phones have not been bootloader unlock or root for the last 5+ years or more. If you want root options, get a B (EU/UK) or E series phone.
crazyut said:
Unless you find a a hack, any U/U1 (USA/United States/The States/States/American/America) and W series (Canada) phones have not been bootloader unlock or root for the last 5+ years or more. If you want root options, get a B (EU/UK) or E series phone.
Click to expand...
Click to collapse
Is there any way to recover deleted pictures in the Samsung A53 5G (USA version) if it is impossible to root this version of the phone?
I accidentially manually deleted some photos in my phone today with my computer (so it doesn't appear in the photo's trash bin), and every single recovery program I encountered says I need to root my phone in order to use a deep scan to look for the deleted files.
I have litte hope that there is anything to recover. Despite the fact that us versions can't be unlocked what would be necessary for rooting, flash storage management (also garbage collection, trim etc.) tends to shift data all the time to other/new cells making it unlikely for you to recover lost data on an active device. Better backup from time to time, always your best bet.
Hello! Im having an issue, maybe im doing somthing wrong. I'm at 13) After giving the img.boot.lz4 i wait and wait and the memory of the phone fills completly (Around 120+Gb) and the patched img do not comes out, any thougths?
This is a deprecated method. You have to patch the whole AP file with magisk and flash it along with BP, CP and (Home) CSC after you've unlocked the bootloader.
Andoreid said:
This is a deprecated method. You have to patch the whole AP file with magisk and flash it along with BP, CP and (Home) CSC after you've unlocked the bootloader.
Click to expand...
Click to collapse
That's right, but for folks with no experience rooting new Samsung devices, please:
- DO read OP's "Unlock bootloader" section. Visitors to this page who skip to the end and have never rooted non-Samsung or older devices might think "adb reboot fastboot" followed by "fastboot flashing unlock" or "fastboot oem unlock" will do the trick. It won't. To clarify: fastboot will NOT recognize this phone, which is normal because it doesn't have a standard fastboot mode, and simply enabling "Allow OEM unlock" in developer settings is necessary but not enough.
Do follow OP's steps for unlocking.
- For rooting, I followed the instructions here https://samsungusbdriver.me/root-samsung-galaxy-a53-5g/ (second method).
But the instructions on that page for getting the actual model number and CSC for Frija are unclear. Finding that information was not straightforward. Depending on the method I used, the model number would be SEPF_SM-A536B_12_0001, SM-A536B/DS, A536B... and you need to know CSC stands for "country-specific code" and it's a 3-character code. I eventually figured out my model was SM-A536B and CSC was EUX. But it took quite a bit of research.
-If you're not familiar with Magisk's DenyList, google it. You might have to use it some apps, particularly banking apps. I think you need it for Netflix, too. Speaking of Netflix, the version that comes preinstalled won't work after rooting. The way I got it to work was uninstalling that version and sideloading the Netflix APK from Apkpure. And adding it to Magisk's DenyList.
Hello,
I have a rooted (Magisk) A53 with TWRP. For a week, I get a notification asking me to update to security patch level of May 1st, 2023. I thought that with unlocked bootloaders, OTA wasn't possible, but whatever. My question is if it's possible to perform the update without losing TWRP and Magisk, and also if it's possible to keep all user data and installed apps. I have little time to spare after work and really don't want to go again through the process of resetting my phone.
Thanks.