Can you please go into this thread for the S22U and see if this same method works to pop-up a Service Menu on your phones?
How to Enable All Bands Through Service Menu on ALL International Snapdragon Samsung S20/S21/S22/Fold2/Fold3/Fold4+ series (including 4G LTE, 5G NR)
Background Previous methods have only worked on US and Canada phones due to the dialer code only working on US/Canada phones on U and U1 firmware, and also the presence of IOTHiddenMenu on those devices' firmware. However, thanks to @K0mraid3's...
forum.xda-developers.com
Essentially go into a System Shell and launch the following command and see if a Service Menu pops up:
Code:
am broadcast -a com.samsung.android.action.SECRET_CODE -d android_secret_code://27663368378 -n com.sec.android.RilServiceModeApp/.SecKeyStringBroadcastReceiver
Previously this method was used for international Samsung's with Snapdragon processors to enable ALL missing bands for use in other countries, but it did NOT work on Exynos. Now that Snapdragon has been standardized across all regions this method may work on EU phones as well. If so it may give a wider reach to US users to contribute to cross-platform development; no more separating S23 forums by hardware type.
Report back if it works - You will be the first S23 pioneers to make this fascinating discovery!
Is this need rooted device or it was working without?
You may not have to be rooted, just have a system level shell to run the command which launches the Service Menu. See if @K0mraid3's System Shell Exploit works if you're not rooted:
***LOCKED UNTIL FURTHER NOTICE*** System Shell Exploit - ALL Samsung Mobile Devices NO BL UNLOCK REQUIRED.
***MODERATOR ANNOUNCEMENT: THREAD CLOSED*** @K0mraid3 you are hereby required to provide proper credit in your OP as follows: Link the assigned CVE for this exploit as it mentions the author's blog and GitHub, OR Link the original research repo...
forum.xda-developers.com
bdvince said:
You may not have to be rooted, just have a system level shell to run the command which launches the Service Menu. See if @K0mraid3's System Shell Exploit works if you're not rooted:
***LOCKED UNTIL FURTHER NOTICE*** System Shell Exploit - ALL Samsung Mobile Devices NO BL UNLOCK REQUIRED.
***MODERATOR ANNOUNCEMENT: THREAD CLOSED*** @K0mraid3 you are hereby required to provide proper credit in your OP as follows: Link the assigned CVE for this exploit as it mentions the author's blog and GitHub, OR Link the original research repo...
forum.xda-developers.com
Click to expand...
Click to collapse
This exploit doesn't work on the s23 Ultras sold in the US.
zeroktal said:
This exploit doesn't work on the s23 Ultras sold in the US.
Click to expand...
Click to collapse
It's also not working on my S918B.
The exact package required to exploit it has an anti roll-back protection on it.
Could be a OneUI 5.1 problem or a S23 series problem.
dDesuKb said:
It's also not working on my S918B.
The exact package required to exploit it has an anti roll-back protection on it.
Could be a OneUI 5.1 problem or a S23 series problem.
Click to expand...
Click to collapse
That's unfortunate the System Shell exploit isn't working on SM918B. I'm assuming you're not rooted to see if the Service Mode command launches directly from su?
bdvince said:
That's unfortunate the System Shell exploit isn't working on SM918B. I'm assuming you're not rooted to see if the Service Mode command launches directly from su?
Click to expand...
Click to collapse
Yep. Not rooted. The exact apk required is behind anti roll back so it just immediately fails and it does nothing except tries 5 times and fails 5 times.
bdvince said:
That's unfortunate the System Shell exploit isn't working on SM918B. I'm assuming you're not rooted to see if the Service Mode command launches directly from su?
Click to expand...
Click to collapse
I hope someone who's rooted can try this
bdvince said:
That's unfortunate the System Shell exploit isn't working on SM918B. I'm assuming you're not rooted to see if the Service Mode command launches directly from su?
Click to expand...
Click to collapse
Are you going to root and try this?
anyone with root able to test this?
Rooted S918B - command via SU and terminal works. Service menu pops up and is accessible, method 2 worked great (I didn't bother trying method 1)
Holy crap that is a lot of bands.
I tried on my rooted s918b, and it worked! However, it looks like the b version has less bands than u version. And there is no mmWave available.
Come faccio a testare? Quale applicazione devo avere sul mio telefono?
How do I test? What application should I have on my phone?
After buying an SM-S918B I can cofirm that you CAN enable the missing bands. 5G on T-mobile didn't work with the SM-S918B, but once I did this and enabled all bands it is now.
I had to root the phone and su to SYSTEM to run the am command.
can you explain step by step how you did it please?
ULTRA90 said:
can you explain step by step how you did it please?
Click to expand...
Click to collapse
1. Unlock bootloader
2. Root your phone
3. Su to system
4. run am broadcast -a com.samsung.android.action.SECRET_CODE -d android_secret_code://27663368378 -n com.sec.android.RilServiceModeApp/.SecKeyStringBroadcastReceiver
5. follow https://forum.xda-developers.com/t/...-fold4-series-including-4g-lte-5g-nr.4546229/ - *I* used
D. METHOD 2: Unlock all bands via Protocol Simulation menu.
If METHOD 1 above didn't work or not all bands were unlocked, you can try to unlock all bands by simulating a change in your CSC to GCF (Global Certification Forum). This won't actually change your CSC to GCF, but will change the options in the service menu as if you were on GCF CSC, which should give you access to all SA and NSA bands. Credits to @wr3cckl3ss1 for figuring out this method.
To do this method, first enter the service mode main menu using either of the following ways.
Open dialer and enter *#27663368378# to get directly into the service mode main menu.
Open dialer and enter *#73# to get into RF Test mode. Press Band Selection. Press three dots on top right -> Back. Repeat three dots -> back three more times until you get to the service mode main menu.
Using the service menu, change the following options
Go to: Service Mode Main Menu -> PROTOCOL STATE -> PROTOCOL SIMULATION -> IMEI PRE CFG SIMULATION.
In this menu, click [1] AP, then click GCF (last option). Then click [2] NET1 and change it to GCF as well. Do the same for [3] NET2. All GCF.
Press [4] Write. Then restart phone.
Check if all SA bands were unlocked. If not, repeat the band unlocking instructions from METHOD 1 above and then restart the phone and check again.
6. reboot
7. enjoy
zeroktal said:
After buying an SM-S918B I can cofirm that you CAN enable the missing bands. 5G on T-mobile didn't work with the SM-S918B, but once I did this and enabled all bands it is now.
I had to root the phone and su to SYSTEM to run the am command.
Click to expand...
Click to collapse
Besides mmWave, the screenshot @Boxy52 posted shows that the phone is missing the 5G n71 band and 4G 71 band. Are you saying you're able to enable these missing bands on the S918B through the Service Menu? Can you post a screenshot?
No, I was able to get all bands that were disabled on the rom enabled. 71 is not on this rom.
zeroktal said:
1. Unlock bootloader
2. Root your phone
3. Su to system
4. run am broadcast -a com.samsung.android.action.SECRET_CODE -d android_secret_code://27663368378 -n com.sec.android.RilServiceModeApp/.SecKeyStringBroadcastReceiver
5. follow https://forum.xda-developers.com/t/...-fold4-series-including-4g-lte-5g-nr.4546229/ - *I* used
D. METHOD 2: Unlock all bands via Protocol Simulation menu.
If METHOD 1 above didn't work or not all bands were unlocked, you can try to unlock all bands by simulating a change in your CSC to GCF (Global Certification Forum). This won't actually change your CSC to GCF, but will change the options in the service menu as if you were on GCF CSC, which should give you access to all SA and NSA bands. Credits to @wr3cckl3ss1 for figuring out this method.
To do this method, first enter the service mode main menu using either of the following ways.
Open dialer and enter *#27663368378# to get directly into the service mode main menu.
Open dialer and enter *#73# to get into RF Test mode. Press Band Selection. Press three dots on top right -> Back. Repeat three dots -> back three more times until you get to the service mode main menu.
Using the service menu, change the following options
Go to: Service Mode Main Menu -> PROTOCOL STATE -> PROTOCOL SIMULATION -> IMEI PRE CFG SIMULATION.
In this menu, click [1] AP, then click GCF (last option). Then click [2] NET1 and change it to GCF as well. Do the same for [3] NET2. All GCF.
Press [4] Write. Then restart phone.
Check if all SA bands were unlocked. If not, repeat the band unlocking instructions from METHOD 1 above and then restart the phone and check again.
6. reboot
7. enjoy
Click to expand...
Click to collapse
Please, did the Method 2 work without root?
Related
Recently i found a way to sim unlock Samsunga Galaxy A3(Sm-A300FU),there is no need to root,this worked for me on firmware A300FUXXU1ANL5 So this are the steps:
Dial *#0011#
When Menu comes long press options button and hit BACK
Long press again options button and press KEY INPUT then enter "Q"
Then again long press option button press KEY INPUT then enter "0000"(zero)
Now you should wait about 10-15 seconds and a new menu will come out
From that menu select option 2 UE SETTING & INFO
Next menu select option 1 SETTING
Next menu select 2 SYSTEM
Next menu select 4 NV BACKUP TEST
Next menu select 2 MAKE BACKUP
After that long press option button and hit BACK
Here select option 3 EFS CLEAR & RESTORE
Long press option button and hit BACK
Again long press option button and hit BACK
Here select option 3 NV REBUILD
Here select option 3 ALL
Reboot and Done!
I hope it works for you,i allready test it on 5 SAMSUNG A3 Locked to Vodafone Spain
not working for me
i have sm-a300 fu
a300fuxxu1anl4
Why bother if you can flash an unbranded stock rom via odin...
I have an A300H. can i flash A300HU firmware on it? cos this method is not working for my set.
dineshdias said:
I have an A300H. can i flash A300HU firmware on it? cos this method is not working for my set.
Click to expand...
Click to collapse
Not working for me either. I am on A300FU ANL5 locked to EE UK..
I believe this is a hoax and should be looked into and removed if it is because that post is spammed across google and no other references have been made, where did this guy supposedly find this method or how did he discover it?
finch69 said:
I believe this is a hoax and should be looked into and removed if it is because that post is spammed across google and no other references have been made, where did this guy supposedly find this method or how did he discover it?
Click to expand...
Click to collapse
I agree with the previous comment, please moderators remove these types of post since they are not valid/true and lack of detailed explanations, pictures, videos that proves it
Marecki_ said:
Why bother if you can flash an unbranded stock rom via odin...
Click to expand...
Click to collapse
I have A3 (SM-A300FU) locked to EE network, can I flash BTU firmware and have my phone be unlocked this way safely?
dineshdias said:
I have an A300H. can i flash A300HU firmware on it? cos this method is not working for my set.
Click to expand...
Click to collapse
If you have A300H you should only flash things made for A300H because you can brick your phone
I would like to know the same. Will i be able to flash unbranded software on my o2 branded locked a3?
This will only work at old versions, if you have newer release this bug is fixed. but you can always unlock it by
using the SRS solution from unlocksamsungonline.nl this will support A3 / A5 / A7 / A9 Series for direct unlock without root, and Imei repair, MSL reset en CERT write with root .
Code:
18:04:59 - Starting ADB Server
18:04:59 - ADB Device: SM-A300FU
18:05:00 - SW Version: A300FUXXU1BOI2 (Android: 5.0.2)
18:05:00 - Platform: MSM8916 - Chip: MSM8916
18:05:00 - Phone SNR: RF8G90XSAYT
18:05:00 - USB Mode: DIAG ACM ADB
18:05:00 - Trying to connect to diagnostic port COM5
18:05:00 - Reading Diagnostic Data...
18:05:01 - Imei: 35397407257874
18:05:01 - SW: MPSS.DPM.2.0.c5-00075-M8936FAAAANUZ
18:05:01 - Analyzing Phone Security..
18:05:01 - New Security Detected Bypassing.. Done
18:05:01 - Unlocking Block 1.. Please Wait.. [OK]
18:05:02 - Unlocking Block 2.. Please Wait.. [OK]
18:05:02 - Unlock: Done (Code: 00000000 or 01234567)
18:05:02 - Operation Done...
Marecki_ said:
Why bother if you can flash an unbranded stock rom via odin...
Click to expand...
Click to collapse
Flashing unbranded ROM on a network locked phone will cause a lot of issues.
I have rooted my device and also gave root access to shortcut master and phone info app but still it doesn't launch the menu and gives some error. Any solution?
I have the same problem, you can achieve band locking through shortcut master under app explorer, check out hidden network settings. Interestingly it has a reference for standalone 5G!
Might need to flash with a combination file to achieve full service mode. I have an S8+ running with an engineering Rom and it has 2 system apps which can achieve full service mode, the apps are called Samsung keystring and iot hidden menu. With samsung Keystring you can enter any secret code. And with iot hidden menu you just select debug menu. Was messing around with lucky patches seeing if I could modify them to work on the S9+ but no luck yet.
Hopefully someone will find a way soon. I had the same problem on another S8+ after it upgraded to Oreo, so I think it's linked to that, but don't think there is an option to have android 7 for the S9!
This looks like it's worth a try.
https://forum.xda-developers.com/note-4-sprint/general/how-to-access-hidden-menu-adb-rooted-t3403289
Aidoooo said:
I have the same problem, you can achieve band locking through shortcut master under app explorer, check out hidden network settings. Interestingly it has a reference for standalone 5G!
Might need to flash with a combination file to achieve full service mode. I have an S8+ running with an engineering Rom and it has 2 system apps which can achieve full service mode, the apps are called Samsung keystring and iot hidden menu. With samsung Keystring you can enter any secret code. And with iot hidden menu you just select debug menu. Was messing around with lucky patches seeing if I could modify them to work on the S9+ but no luck yet.
Hopefully someone will find a way soon. I had the same problem on another S8+ after it upgraded to Oreo, so I think it's linked to that, but don't think there is an option to have android 7 for the S9!
This looks like it's worth a try.
https://forum.xda-developers.com/note-4-sprint/general/how-to-access-hidden-menu-adb-rooted-t3403289
Click to expand...
Click to collapse
But bro you can change so many settings in full service mode like selecting CA combination,activating 4x4 mimo,256 qam etc. I know about hidden service menu but for me it doesn't properly lock bands for some reason so i rooted just for accessing full service mode but i get this error. That telephony command doesn't open the menu but still the broadcast value i get is 0. I want the menu so bad because i only use 4g and i can improve speeds by changing some settings but **** samsung has locked us out. Maybe if ur phone is rooted and you have that 2 apps u mentioned try placing that apps in sys/priv-app folder and try opening it or may be find another way.
I will give that a try, i want to get the full service mode working also for sure, I am hoping for an option of setting the LTE category higher 16 or 20. I was reading it could also be due to the version of supersu used as the same thing happens with the phone info app. And those app developers don't think it's there app.
Aidoooo said:
I will give that a try, i want to get the full service mode working also for sure, I am hoping for an option of setting the LTE category higher 16 or 20. I was reading it could also be due to the version of supersu used as the same thing happens with the phone info app. And those app developers don't think it's there app.
Click to expand...
Click to collapse
But i am using magisk and also tried it with latest supersu but it didn't work. Like is there anyone who can solve this problem
Aidoooo said:
I will give that a try, i want to get the full service mode working also for sure, I am hoping for an option of setting the LTE category higher 16 or 20. I was reading it could also be due to the version of supersu used as the same thing happens with the phone info app. And those app developers don't think it's there app.
Click to expand...
Click to collapse
Did u find any way?
Hi all,
I'm having exactly this problem now. My purpose is to use the advanced service mode to lock LTE bands and to activate the 256 QAM and MIMO 4x4 functions. I have my G965F rooted and I'm having the same problems described before executing "Phone info" and dialing directly the "2683662" code. I updated the firmware to "G965FXXS2BRI1" with the same result.
I was wondering if flashing COMBINATION ROM could help... but I'm a newbie with this things...
does anyone have any idea about how to solve it, please? At leaste, any idea to use the band lock functions?
Thank you!
Hey, did anyone find a solution for this?
Interceptor777 said:
Hey, did anyone find a solution for this?
Click to expand...
Click to collapse
Seems most of here who wants to achieve the SERVICEMODE are on all OREO FW....No problem getting it to work on Nougat/MM..But after OREO came out, now **** comes on Servicemode...
Finally got it working !!!! damn Sammy disabled the SM on Oreo FWs.
castrojeremy11 said:
Finally got it working !!!! damn Sammy disabled the SM on Oreo FWs.
Click to expand...
Click to collapse
How'd you get it working?
Sleepsy said:
How'd you get it working?
Click to expand...
Click to collapse
Just Downgrade to Nougat - the only option
Downgrade then root it then as use Shortcut app..
Nougat?
castrojeremy11 said:
Just Downgrade to Nougat - the only option
Downgrade then root it then as use Shortcut app..
Click to expand...
Click to collapse
Hi mate, I can't find nougat firmwares for S9/S9+, all I can find are oreo and above, where did you find it?
castrojeremy11 said:
Just Downgrade to Nougat - the only option
Downgrade then root it then as use Shortcut app..
Click to expand...
Click to collapse
I don't know if this will help, as I have an S8. It works on Pie, and I think I may have used it while on Oreo.
I was able to able to get Safestrap (via EDL exploit: Thanks jrkruse!), and edit efs/carrier/hiddenmenu (from NO to YES)
In the dialer, the only code that ended up working for me (after much searching), was *#27663368378#
All the shorter codes failed. But, type it enough, and you'll memorize it like I did.
Alternatively (to memorizing), just for kicks I just converted it to words. An applicable one is "as-modem-test"
224 More acronyms: https://phonespell.org/combo.cgi?n=27663368378
Included link, since we're exposed to tons of these codes.
hello
It's strange that the advanced Menu Mode is disabled ... How the samsung staff will do to repair or test phones ?
Sleepsy said:
I don't know if this will help, as I have an S8. It works on Pie, and I think I may have used it while on Oreo.
I was able to able to get Safestrap (via EDL exploit: Thanks jrkruse!), and edit efs/carrier/hiddenmenu (from NO to YES)
In the dialer, the only code that ended up working for me (after much searching), was *#27663368378#
All the shorter codes failed. But, type it enough, and you'll memorize it like I did.
Alternatively (to memorizing), just for kicks I just converted it to words. An applicable one is "as-modem-test"
224 More acronyms: https://phonespell.org/combo.cgi?n=27663368378
Included link, since we're exposed to tons of these codes.
Click to expand...
Click to collapse
the as-modem-test thing is clever. mnemonics can and do frequently prove themselves to be handy!
If you are rooted then use "Network signal guru" it can lock band and also might help you.... As i had used to force lte band 03 as my phone takes band 40 which has low speed.
Sleepsy said:
I don't know if this will help, as I have an S8. It works on Pie, and I think I may have used it while on Oreo.
I was able to able to get Safestrap (via EDL exploit: Thanks jrkruse!), and edit efs/carrier/hiddenmenu (from NO to YES)
In the dialer, the only code that ended up working for me (after much searching), was *#27663368378#
All the shorter codes failed. But, type it enough, and you'll memorize it like I did.
Alternatively (to memorizing), just for kicks I just converted it to words. An applicable one is "as-modem-test"
224 More acronyms: https://phonespell.org/combo.cgi?n=27663368378
Included link, since we're exposed to tons of these codes.
Click to expand...
Click to collapse
you should also make sure keystrings r enabled by changing /efs/FactoryApp/keystr from no to yes
also keep in mind keystrings r also carrier dependent.. some have kore than others and some have different ones.. its based on csc.. if u look through them u will find each carrier has a keystrings.dat file
Finally got tired of the Pixel 2 XL after the third one. Now I have this super rugged handset that I can actually hold on to! Great loud audio too!
The Sonim XP8 comes with a seemingly near stock Android 7.1.1 ROM. OEM unlocking is available in the developer options. I have it enabled. Does anyone know how to use the ADB/Fastboot tools to unlock it? The standard commands do not work. My unit is personal and not under any "enterprise" restrictions. Thanks for any help fellow hackers ... some TWRP would be awesome.
ctradio said:
Does anyone know how to use the ADB/Fastboot tools to unlock it? The standard commands do not work. My unit is personal and not under any "enterprise" restrictions. Thanks for any help fellow hackers ... some TWRP would be awesome.
Click to expand...
Click to collapse
(Im)patiently waiting for this too. I don't care if it is single touch or long drawn out process involving a cauldron, hermetic circle, and a full moon. Root is sorely needed...
Phuhque said:
(Im)patiently waiting for this too. I don't care if it is single touch or long drawn out process involving a cauldron, hermetic circle, and a full moon. Root is sorely needed...
Click to expand...
Click to collapse
Good luck! Still nothing. It looks like we might be able to sign up as a developer on their page .... fwiw. I find the interface on that device to be awful and am in the early stages of fighting AT&T for my money back. That device and another one with the same stupid issues and an admitted software problem that I'd have to wait for the carrier to decide to release. Awesone idea for a device, absolutely rushed to market with god awful software that was new in '16 or so.
ctradio said:
I find the interface on that device to be awful and am in the early stages of fighting AT&T for my money back. .
Click to expand...
Click to collapse
I am on T-Mobile and found the factory unlocked version with no bloatware (obtainable directly from the) to be rather refreshing, even if it did set me back an extra $100. I suggest do getting the refund, then turning around and getting the "clean" version. It may be more expensive, but considering how much it costs for monthly insurance, the overall price becomes somewhat more competitive with the 3 year "comprehensive" warranty...
Phuhque said:
I am on T-Mobile and found the factory unlocked version with no bloatware (obtainable directly from the) to be rather refreshing, even if it did set me back an extra $100. I suggest do getting the refund, then turning around and getting the "clean" version. It may be more expensive, but considering how much it costs for monthly insurance, the overall price becomes somewhat more competitive with the 3 year "comprehensive" warranty...
Click to expand...
Click to collapse
I was told there was no carrier unlocked variant of this thing. Didyou get it from Sonim? Also, any problems at all with it? I had two with touch issues along the right side of the screen (it perceives a light constant touch in various areas and it gets worse the longer the screen is on). The units would eventually start selecting things on its own and even deleting contacts. Also, the speaker phone is useless and the UI is horribly laggy at times (my mind operates fast and it screws with me). I presented them with a "laundry list" of the issues.
ctradio said:
I was told there was no carrier unlocked variant of this thing. Didyou get it from Sonim? Also, any problems at all with it? I had two with touch issues along the right side of the screen (it perceives a light constant touch in various areas and it gets worse the longer the screen is on). The units would eventually start selecting things on its own and even deleting contacts. Also, the speaker phone is useless and the UI is horribly laggy at times (my mind operates fast and it screws with me). I presented them with a "laundry list" of the issues.
Click to expand...
Click to collapse
Someone flat out lied to you. Go here: https://store.sonimtech.com/products/sonim-xp8-blk-nam
Well, maybe not lied at the time you were told... I waited several months for them to post it on their store page. In response to your concerns....
No issues with it going all AI on me. Speaker PHONE portion leaves a bit to be desired, but for audio books, this thing is damned awesome and really loud. Not sure how to reference the lag. My previous phone was a Note 4 with issues.
My own complaints. The lock screen is a pain. The default music program is broken in my opinion. I am suffering through with Musicolet for my books.
What sold me on this is that is is one of the last phones made today that has a removable battery (really my only requirement in a new phone), has both gps an glonass, and in a pinch I can use is an a hurled object to an opponents head. Someone complained about the camera, but it seems fine to me. Wouldn't matter much as I am partially colorblind and won't see any difference.
I have only had mine for a week, and am still tweaking the settings to how I want them. Honestly, I like it.
I would really love to see some support for this phone. Especially since the monsters at Telus have disabled the 2nd sim slot for no good reason. I have tried everything but without Root I am out of luck getting the dual sim feature to function. Is there anything I can provide to assist someone more knowledgeable in getting a root solution for this phone? Please let me know.
mertin said:
I would really love to see some support for this phone. Especially since the monsters at Telus have disabled the 2nd sim slot for no good reason. I have tried everything but without Root I am out of luck getting the dual sim feature to function. Is there anything I can provide to assist someone more knowledgeable in getting a root solution for this phone? Please let me know.
Click to expand...
Click to collapse
Hello,
I just bought this phone. I use 2 sim cards at the same time but it does not work properly: I can receive and make calls, but I can not send or review sms / mms on 1 operator. I use the xp8800 in France, it is a Att model unlocked. to have the 2 sim cards at the same time I rebooted several times, cut the data, without really understanding how I did . is there a way to restart the network part of Android ?
Thanks
Pascal S
I take it we are still coming up snake-eyes when it comes to someone being able to root the XP8. I am rather surprised with the fact it is on 7.1.1. Is this still an unbeatable task to overcome?
The thread is closed, this is the tested version of the firmware
Unlock fastboot
Step 1, open the developer mode
Go to “Settings” → “About Phone” and click “Version Number” 7 times to open Developer mode.
Step 2, open oemlock
Go to “Settings” → “Other Settings” → “Developer Mode” and open the OEM to unlock;
3 START mode
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
flashing lock_critical Prevents flashing bootloader-related
partitions.
flashing unlock_critical Enables flashing bootloader-related
partitions.
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
erase <partition> Erase a flash partition.
Firmware update soon.. ??
In May, I sent of another email to Sonim Tech support asking about firmware. I did get a response back. Granted it was rather vague, but it was an answer. Further granted, is is now mid June and no updates in sight including one that allows the viewing of PDF's. grrrr.
The support guy did mention that AT&T is going to be one of the first providers to get the update. That sucks for me because I got my unit direct. He also said the month of May was a non-official time frame.
So still waiting and no success story yet posted of anyone unlocking this little beastie.
https://www.att.com/devicehowto/tutorial.html#!/stepbystep/id/stepbystep_KM1259507?make=Sonim&model=XP8XP8800
No idea how to update manually, though...
Phuhque said:
In May, I sent of another email to Sonim Tech support asking about firmware. I did get a response back. Granted it was rather vague, but it was an answer. Further granted, is is now mid June and no updates in sight including one that allows the viewing of PDF's. grrrr.
The support guy did mention that AT&T is going to be one of the first providers to get the update. That sucks for me because I got my unit direct. He also said the month of May was a non-official time frame.
So still waiting and no success story yet posted of anyone unlocking this little beastie.
Click to expand...
Click to collapse
No idea how to update manually, though...[/QUOTE]
Thanks for the news , but no working to ATT from France , until in OTA .
Wait and see if dual sim working clean ....
Has anyone seen this video? There's a part in the video where as the guy turns it on, and there is a prompt to re-lock the bootloader(which, of course, implies that the bootloader is unlocked); I don't know how this really helps, but it might give someone more experienced than I something to grab at. I should mention that it is mentioned as a pre-production model of the Sonim XP8, so it probably won't apply to models that most people have, but it's something to look at.
Sonim XP8
I know that Verizon is now selling the Sonim XP8. Does anybody happen to know if it is possible to use both SIM card slots with this device after it is unlocked?
Being able to use BOTH AT&T AND Verizon would be a huge benefit to me.
is there any root yet ive tried about every root apps i cant even find working drivers for this phone
Thecctech said:
is there any root yet ive tried about every root apps i cant even find working drivers for this phone
Click to expand...
Click to collapse
Drivers are not an issue.. It's using Qualcomm reference designs from the S660 dev kit where most generic Qualcomm drivers should work with minimal modification.
This is a good thing! Most of the root apps are using a collection of known exploits where only vulnerable devices would fall victim. You would have to use an exploit that's more recent then the security patch level installed but you also have to remember - if you can do it that easily then an attacker can do it just as easily too! I personally believe that the association between root and device/firmware level vulnerabilities is the reason why most see root in a negative context today.
As far as I'm concerned - we only have 2 "correct" ways to achieve root.
1. Obtain (or compile) either a Debug or Engineering firmware variant from AT&T that includes the native su packages for adb root. This is usually not an option for us individuals.
2. Unlock the bootloader and use a patched boot image.. Works great! To unlock the bootloader takes a bit of work though and flashing still requires EDL so with that I have not been able to make a public instruction set yet.
Could be in the next few days.. Could be in the next few months.. I'm honestly not sure. Mostly just a matter of collecting images, testing, and finding time.
Enjoy!
XP8 Android Root Theory - DEBUG or Magisk over EDL
EDL is a must since Fastboot cannot be unlocked initially from standard "user" builds.
One option is flash a userdebug image (below) allowing for adb root, fastboot unlocking, and other useful features.
or
Without unlocking the bootloader - Similar flashing methods remain valid when standard magisk powered root is desired. This method allows preservation of all current system data aside from boot.img. All is covered since Magisk works with AVB and we have EDL as a flashing alternative. Please see Android Boot Flow > LOCKED Devices with Custom Root of Trust for more information.
Recommend method ..
It's up to you.. If you want OTA updates and your planning to use root apps then go with Magisk. As of today we have current debug images available and I personally prefer isolated adb root access only however future availability of updated Debug images cannot be guaranteed.
Disclaimer
-Devices with locked bootloaders will display a custom OS warning at boot
-Tested on AT&T branded devices only - please provide system dump for validation on other builds
-I have not identified any JTAG procedures and I can not help if you hard brick your device!
-This guide only touches boot_a and should be relatively safe since boot_b remains unmodified. I'm pretty sure this is enough to restore the original boot.img to boot_a under a failure scenario.. But I'm not really qualified enough to say definitively either.
-Take great caution - this is raw emmc access and critical system data! You are proceeding at your own risk!
Magisk Root
Step 1 - Pull Boot.img
We need to pull the boot.img in order to feed it to magisk later for patching. It's also good to keep on hand for if/when you need to restore for any reason.
1. Create an XML file with the data below
Code:
<?xml version="1.0"?>
<data>
<program start_sector="262144" sparse="false" readbackverify="false" physical_partition_number="0" partofsingleimage="false" num_partition_sectors="131072" label="boot_a" filename="boot.img" file_sector_offset="0" SECTOR_SIZE_IN_BYTES="512"/>
</data>
2. Boot to EDL mode and load firehose programmer
Code:
QSaharaServer.exe -p \\.\COM<#> -s 13:prog_emmc_ufs_firehose_Sdm660_ddr.elf
3. Backup boot.img using the following command
Code:
fh_loader.exe --convertprogram2read --port=\\.\COM<#> --sendxml=<xmlfile.xml> --lun=0 --memoryname=emmc --noprompt --reset
Or visit the XP8 carrier firmware thread for full system backup steps.
https://forum.xda-developers.com/showpost.php?p=80465045&postcount=6
Step 2 - Magisk Patch
1. ADB push boot.img /storage/self/primary/Download/
2. Install Magisk Manager and apply patch to boot.img
2a. Download from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
2b. Extract and run adb install magisk.apk
2c. Open Magisk app and apply patch to boot.img
3. ADB pull /storage/self/primary/Download/magisk_patched.img
Step 3 - Restore
1. Change the filename attribute in the XML to reflect newly created magisk_patched.img as shown below
Code:
<?xml version="1.0"?>
<data>
<program start_sector="262144" sparse="false" readbackverify="false" physical_partition_number="0" partofsingleimage="false" num_partition_sectors="131072" label="boot_a" filename="magisk_patched.img" file_sector_offset="0" SECTOR_SIZE_IN_BYTES="512"/>
</data>
2. Boot back into EDL mode and load firehose programmer
Code:
QSaharaServer.exe -p \\.\COM<#> -s 13:prog_emmc_ufs_firehose_Sdm660_ddr.elf
3. Apply magisk_patched.img using the following command
Code:
fh_loader.exe --port=\\.\COM<#> --sendxml=<xmlfile.xml> --lun=0 --memoryname=emmc --noprompt --reset
USERDEBUG Flash
Step 1 - Backup
1. Boot to EDL mode and load firehose programmer
2. Generate rawprogram0.xml - Run GPTConsole <COM Number>
Example: GPTConsole 19
3. Initiate backup
Code:
fh_loader.exe --port=\\.\COM<#> --convertprogram2read --sendxml=rawprogram0.xml --lun=0 --memoryname=emmc --noprompt --reset
4. Wipe all partitions
Code:
fh_loader.exe --port=\\.\COM<#> --convertprogram2read --sendxml=erase.xml --lun=0 --memoryname=emmc --noprompt --reset
5. Restore new image
Code:
fh_loader.exe --port=\\.\COM<#> --sendxml=rawprogram0.xml --lun=0 --memoryname=emmc --noprompt --reset --search_path=<extracted image file directory>
// rawprogram0_unsparse.xml for some images
Images and OTA Files
Full 8.1 System Image
XP8A_ATT_user_8A.0.5-11-8.1.0-10.54.00
XP8A_ATT-user-8A.0.5-10-8.1.0-10.49.00
USERDEBUG Images
XP8A_ATT_userdebug_8A.0.5-11-8.1.0-10.54.00
XP8A_ACG-userdebug-8A.0.0-00-7.1.1-32.00.12
XP8A_USC-userdebug-8A.0.0-00-7.1.1-34.00.10
(ATT 7.1 pending upload. Please check back or use other links available further in thread.)
OTA Updates
XP8_ATT_user_N10.01.75-O10.49.00
XP8_ATT_user_O10.49.00-O10.54.00
XP8_TEL_user_N12.00.24-O12.23.00
Flash Tools - programmer (elf) file provided by eleotk!
XP8 Drivers
Firmware Carrier Codes
Code:
None = 0,
ATT = 10
Bell = 11
Telus = 12
Sasktel = 13
Harris = 14
Verizon = 15
Ecom = 16
NAM = 17
Rogers = 18
T_Mobile = 19
EU_Generic = 20
MSI = 21
CISCO = 22
NAM_Public_Safety = 23
Vodafone_Global = 24
Orange = 25
Southern_Linc = 26
OPTIO = 27
India = 28
SPRINT = 29
JVCK = 30
AUS = 31
ACG = 32
CSPIRE = 33
USC = 34
SB = 35
Multi = 99
Automatic OTA without AT&T service:
Purchase a blank AT&T SIM card ($5)
Start online prepaid activation - complete pages 1 & 2
**SIM Card is now partially active without funding - do not complete page 3 (payment)***
*#*#368378#*#* > Clear UI > Check for updates in settings
XP5s
Sprint Image: XP5SA.0.2-03-7.1.2-29.03.00
Works the same. Tested with unmodified Sprint firmware. Like most other apps, the Magisk manager app is unusable since the XP5s has no touch screen - I had to patch the boot image on another device. You can plug in a USB mouse however the cursor does not seem to invoke in-app tap's.
Need to use the appropriate Firehose loader (prog_emmc_firehose_8920.mbn) and replace the boot image location according to the XP5s GPT (start_sector="790528").
Great, thanks alot for instructions, @smokeyou!
In order to be able to boot into patched boot image, does it require to have unlocked bootloader? Assuming I can upgrade my phone to build 8A.0.5-10-8.1.0-10.49.00, but have my bootloader locked, can I still use your instructions? Can you clarify it?
-albertr
albert.r said:
Great, thanks alot for instructions, @smokeyou!
In order to be able to boot into patched boot image, does it require to have unlocked bootloader? Assuming I can upgrade my phone to build 8A.0.5-10-8.1.0-10.49.00, but have my bootloader locked, can I still use your instructions? Can you clarify it?
-albertr
Click to expand...
Click to collapse
Untested but should not be a problem. Bootloader unlocking only allows Fastboot flashing where this method uses EDL only.
Basically the same outcome though just without the option to use TWRP or custom recovery (easily).
Hi! My name is Bautista.
This is my first post well explained, I already asked this question before but I did not express myself well (I hope to do it correctly in this attempt)
My problem happens with my Samsung Galaxy A01 SM-A015M, Running on OneUI 2.0/Android 10 with 2gb of ram, a Snapdragon 439, the stock rom/firmware and 32GB of storage, from Argentina.
Things I tried so far, and didn't work for me:
Unlocking the bootloader by following the Gearallnews and Cyanogenmods guides to the letter.
When trying to unlock the bootloader with the guides on the aforementioned pages, when starting the device a sign should appear saying that the bootloader is unlocked, which did not appear.
The device started correctly in the process to configure the device the first time it is turned on, connect the wifi as the guides said. Followed by that I went to the developer options and the option "Oem unlock" was still activated and in blue (which should not happen, it should appear grayed) I heard that some Samsung devices with snapdragon processors had a bootloader that cannot be unlocked
Unlocking the bootloader using ADB AND Fastboot. (ADB detects my device fine, but fastboot doesn't detect it at all)
Using Fastboot from Windows 7, Windows 10, and Kali Linux.
Installing TWRP.
Use rooting apps. (the ones that appear on the XDA rooting page)
What I am going to with this thread, is:
Can my device's bootloader be unlocked? And if so, how?
If the bootloader cannot be unlocked, how can I root or install TWRP?
Please, if you don't understand something or need more information, let me know by replying to this thread or sending me a private message.
Look inside here.
jwoegerbauer said:
Look inside here.
Click to expand...
Click to collapse
it's the same as Gearallnews and Cyanogenmods guides, i already did that, it dont work
Like the original poster I also have a Samsung Galaxy A01 SM-A015M/DS, OneUI 2.0/Android 10, 2GB ram, 32GB storage, Snapdragon 439, stock firmware (TPA) Panama. I have gone through all the aforementioned procedure and the bootloader does not unlock. There is no bootloader unlock warning on reboot and the OEM Unlock in developer option does not grey out. Does the Snapdragon processor not allow bootloader unlock or is anyone aware of a solution. Thanks for any assistance.
@mullerh
If in Settings -> Developer Option the option "OEM unlock" is present then unlocking the bootloader obviously isn't denied by OEM/Carrier.
But you can check it at your own:
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
jwoegerbauer said:
@mullerh
If in Settings -> Developer Option the option "OEM unlock" is present then unlocking the bootloader obviously isn't denied by OEM/Carrier.
But you can check it at your own:
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
Click to expand...
Click to collapse
Thanks for your response and assistance. The command:
adb shell "getprop ro.oem_unlock_supported" returns a 1
I googled it but found no clarification but I assume that means it is supported.
Therfore there is something else that is blocking the bootloader from unlocking from the unlock mode screen and just prior to reset.
There is also no unlock bootloader warning during the reset.
The more I have Googled this problem the more it seems to indicate that many newer Samsung phones released in North/Latin America with Qualicom Snapdragon 439 processors, have the the bootloaders locked down with a new "security" feature called SecureBoot. Would be interested in getting the experience of others. Thanks
mullerh said:
Thanks for your response and assistance. The command:
adb shell "getprop ro.oem_unlock_supported" returns a 1
I googled it but found no clarification but I assume that means it is supported.
Therfore there is something else that is blocking the bootloader from unlocking from the unlock mode screen and just prior to reset.
There is also no unlock bootloader warning during the reset.
The more I have Googled this problem the more it seems to indicate that many newer Samsung phones released in North/Latin America with Qualicom Snapdragon 439 processors, have the the bootloaders locked down with a new "security" feature called SecureBoot. Would be interested in getting the experience of others. Thanks
Click to expand...
Click to collapse
Hi! Did you manage to find a way to unlock the bootloader?
I have not been able to unlock the bootloader on this SM-A015M/DS (Latin American) model with Snapdragon processor. I have done a lot of searching but found little info except articles stating Samsung had gone through some extra effort to secure their latest phones. That also means I can not root it. I was hoping to get some feedback from other who may have had a better experience,
have you tried using the twrp app to install twrp?
i had an old galaxy grand prime which was impossible to unlock, but the app worked without issues
the only thing i had to pay attention is to turn it off right before ir reboots after installing and then loading into recovery
letting the mobile startup without doing this overrieded the command to install twrp
Thanks for your response. It is my understanding (I could be wrong) that before TWRP can be installed the Bootloader needs to be unlocked. The older Samsung usually allowed the Bootloader to be unlocked even if there was difficulty in rooting them. It appears that some of the newer Samsung's with the Snapdragon processors have added an additional security feature called SecureBoot which blocks the Bootloader from being unlocked.
Does anyone have a definitive answer for how to turn the bootloader on? I recently purchased a SM-A015M/DS and didn't have issues with the OEM bootloader option appearing in the options. But when I enter fastboot mode it says my device status is locked. I can't work out if that means it's locked or not.
For what it's worth, when I flashed the firmware onto the phone in the first place, I had to enable the developer option manually- I did this by booting into download mode and then a long press on the volume up button when prompted by the menu. I don't see why this wouldn't work for other devices. There are youtube videos that explain in greater detail if you haven't tried this yet.
Newiser7 said:
Does anyone have a definitive answer for how to turn the bootloader on? I recently purchased a SM-A015M/DS and didn't have issues with the OEM bootloader option appearing in the options. But when I enter fastboot mode it says my device status is locked. I can't work out if that means it's locked or not.
Click to expand...
Click to collapse
Enabling OEM unlock option in Developer options does NOT UNLOCK the bootloader. Once you enable the OEM unlock on your device, the unlock ability flag is set to 1, which will allow users to use the fastboot flashing unlock command, the command what starts the "unlocking the bootloader" procedure.
FYI:
After the command is executed, you will see an option for bootloader unlock on your device’s screen.
Use the volume buttons to move up and down and select the option to unlock the bootloader.
A prompt will pop up, asking for confirmation. Use the power button to confirm your selection as yes, and you are done.
The phone will now reboot to fastboot mode. Enter the command “fastboot reboot,” and it will boot into PC.
jwoegerbauer said:
Enabling OEM unlock option in Developer options does NOT UNLOCK the bootloader. Once you enable the OEM unlock on your device, the unlock ability flag is set to 1, which will allow users to use the fastboot flashing unlock command, the command what starts the "unlocking the bootloader" procedure.
FYI:
After the command is executed, you will see an option for bootloader unlock on your device’s screen.
Use the volume buttons to move up and down and select the option to unlock the bootloader.
A prompt will pop up, asking for confirmation. Use the power button to confirm your selection as yes, and you are done.
The phone will now reboot to fastboot mode. Enter the command “fastboot reboot,” and it will boot into PC.
Click to expand...
Click to collapse
FYI:
Samsung devices do not support fastboot command, you use Odin or Heimdall to flash what you need.
The answer you provide is misleading
mullerh said:
FYI:
Samsung devices do not support fastboot command, you use Odin or Heimdall to flash what you need.
The answer you provide is misleading
Click to expand...
Click to collapse
You are right: I was mistaken.
Thank you for clarifying that the bootloader is still locked. But how can I unlock it? Odin will let me flash the files, but I keep getting AUTH errors when I try to flash magisk patched files to root the phone. I'm assuming this is because the bootloader preventing the files from transferring. Is there a way to unlock it using ADB without fastboot, or a way using Odin? It seems crazy that unlocking the bootloader is enabled but I am still unable to actually unlock it.
I have also tried the CROM Service app (couldn't get it to install on my phone, error 3003 with ADB install), as well as the bootloader unlock method where I boot into download mode, hold the volume up key, and unlock the bootloader that way. I have done the latter at least 5 times and the bootloader is still locked. Ridiculous.
This prop apparently only confirms that the phone supports being unlocked, not that it is actually unlocked.
adb shell "getprop ro.oem_unlock_supported"
Check a few others, also see the official docs.
sys.oem_unlock_allowed
androidboot.flash.locked (the docs say this, but I think Samsung uses something different)
ro.boot.flash.locked
ro.boot.other.locked
Maybe also check these:
ro.boot.verifiedbootstate
ro.boot.veritymode
The docs indicate that the verifiedbootstate should be orange if the bootloader is unlocked. I don't know much about it, though.
You can always use grep to search for any interesting values, like "lock" or "boot" or "flash":
adb shell getprop | grep lock
adb shell getprop | grep boot
adb shell getprop | grep flash
Maybe report any interesting values you have with and without OEM Unlock checked. Maybe someone smarter than us will find it useful.
I would really like to see an A01 root happen, it's such an affordable and accessible device for all sorts of things. Great as a backup device or for a project. You think someone would've released some goods for it by now. It's been out all year.
And for the 16GB model, it's absolutely terrible because Samsung eats up so much space, then has the nerve to remove the Adoptable Storage feature. So even if you get a fast SD card, you can't install apps on it. Other than that, it's a perfectly serviceable phone. I would think with root we could get Adoptable Storage working.
To summarize what has been previously stated the Samsung Galaxy A01, version SM-A015M/DS is the Latin American version of this cellphone. This cellphone has a Snapdragon processor. This version is very similar to the versions (also Snapdragon processors) used by some US Carriers. Many current versions of Samsung cellphones have an additional security feature called "SecureBoot" which blocks bootloader unlocking. Some say this features was added at the request of US Carriers
The Asian version of the A01 has a Exynos processor. It is my understanding that with these it is very easy to unlock the bootloader and root the phone using the usual conventional methods. The Asian variant unfortunately does not cover some of the wireless bands used in the US/Canada/Latin America.
I have a Samsung Galaxy A01 SM-A015M/DS, OneUI 2.0/Android 10, 2GB ram, 32GB storage, Snapdragon 439, stock firmware (TPA) for Panama.
My research indicates that there is not yet an available bootloader unlocking and easy root method for this (A01) phone. For some other current Samsung models there does appear to be a method of flashing certain custom ROMs without a bootloader unlock but they appear to come with problems which include loss of some cellphone functions and a reduction in the charged battery life. So it seems hardly worth it.
It also appears that it is current well known that all current Samsung phones with Snapdragon processors have not allowed bootloader unlocking and rooting due to the enhanced security feature.
At this time we can only complain and/or not buy any additional Samsung phones
Perhaps with time skillful developers will come up with a method to solve this problem with this inexpensive A01.
Please provide any new or updated info if you have it.
Any solution for rooting Galaxy A01 ?
I use A015f region SER (Russia) In Russia, too, the device is locked (bootloader) of course, give any solution
One thing I know is that a fellow SM-M015f, which is almost identical, which is with the same Snapdragon 439, except for the battery capacity and screen size and gigabytes of internal memory, successfully unlocks and gets Magisk root.
this phone actually has a fastboot mode, from recover mode select reboot to bootloader, it will boot to fastboot mode,but ive still been unsucessful in getting fastboot mode to work, devices manager reports device error,
I can start the unlock proccess.
But after it is done and the data is wipped,
It keeps locked.
Sad
So first you have to root. I used twrp and magisk. There are guides on how to do that you can find by searching around.
Then once you do that, follow these directions,
What I did was manually entered all of these setprop commands below, on the terminal emulator app that I downloaded from the play store. First I typed in su in the app and pressed enter. Don't know if that matters but it said it granted superuser rights to the terminal emulator app, which I suppose could be important. I'm rooted with magisk and twrp don't know if that matters either.
setprop persist.vendor.dbg.ims_volte_enable 1
setprop persist.vendor.dbg.volte_avail_ovr 1
setprop persist.vendor.dbg.vt_avail_ovr 1
setprop persist.vendor.dbg.wfc_avail_ovr 1
Then I guess I reset the phone a couple times maybe turned the data on and off and then today it was all working and said volte at the top of the phone. Also vowifi is an option you can turn on as well in network settings. Now in the network settings you can also turn volte ("4G calling") on and off now.
Been testing it on calls and it works perfectly. No more dropped calls from 3G or H+ only call service.
dial *#*#4636#*#* in the phone dialer and click phone information to be taken to secret phone information settings and if it shows LTE under Both data network type and VOICE NETWORK TYPE, then that's another indicator that I got volte working.
You can also type getprop in the terminal emulator and if it says 1 on all the volte and vowifi options that means you enabled these network features as well
This is the easiest method I've found so let me know if it works for you. Now the zenfone 7 works in the USA! At least for tmobile I'd be interested for someone with ATT to try out the method and report back if it works or other people with other phone services.
Shout out to @Seosam and the other guys who actually know what they are doing who helped me figure out this simple method!
The pictures attached show that volte is enabled on my device and what yours should look like at least on tmobile for this phone.
juanappleseed said:
So first you have to root. I used twrp and magisk. There are guides on how to do that you can find by searching around.
Then once you do that, follow these directions,
What I did was manually entered all of these setprop commands below, on the terminal emulator app that I downloaded from the play store. First I typed in su in the app and pressed enter. Don't know if that matters but it said it granted superuser rights to the terminal emulator app, which I suppose could be important. I'm rooted with magisk and twrp don't know if that matters either.
setprop persist.vendor.dbg.ims_volte_enable 1
setprop persist.vendor.dbg.volte_avail_ovr 1
setprop persist.vendor.dbg.vt_avail_ovr 1
setprop persist.vendor.dbg.wfc_avail_ovr 1
Then I guess I reset the phone a couple times maybe turned the data on and off and then today it was all working and said volte at the top of the phone. Also vowifi is an option you can turn on as well in network settings. Now in the network settings you can also turn volte ("4G calling") on and off now.
Been testing it on calls and it works perfectly. No more dropped calls from 3G or H+ only call service.
dial *#*#4636#*#* in the phone dialer and click phone information to be taken to secret phone information settings and if it shows LTE under Both data network type and VOICE NETWORK TYPE, then that's another indicator that I got volte working.
You can also type getprop in the terminal emulator and if it says 1 on all the volte and vowifi options that means you enabled these network features as well
This is the easiest method I've found so let me know if it works for you. Now the zenfone 7 works in the USA! At least for tmobile I'd be interested for someone with ATT to try out the method and report back if it works or other people with other phone services.
Shout out to @Seosam and the other guys who actually know what they are doing who helped me figure out this simple method!
The pictures attached show that volte is enabled on my device and what yours should look like at least on tmobile for this phone.
Click to expand...
Click to collapse
In my mind these setprops are usable without root!
You only need debug mode and can use ist with adb shell
Seosam said:
In my mind these setprops are usable without root!
You only need debug mode and can use ist with adb shell
Click to expand...
Click to collapse
Hmm I might try since I'm not rooted then!
Seosam said:
In my mind these setprops are usable without root!
You only need debug mode and can use ist with adb shell
Click to expand...
Click to collapse
What is ist? And can you access idb shell without a computer? Like only on the phone itself?
CVonV said:
Hmm I might try since I'm not rooted then!
Click to expand...
Click to collapse
Please try! I have a non tech savvy friend who wants this phone and if there is a non root easy way to enter these set prop commands without getting rid of OTA updates then I'd definitely like to know!
Seosam said:
In my mind these setprops are usable without root!
You only need debug mode and can use ist with adb shell
Click to expand...
Click to collapse
it is not possible
It is true. not possible ...
Seosam said:
In my mind these setprops are usable without root!
You only need debug mode and can use ist with adb shell
Click to expand...
Click to collapse
Ok now that you've confirmed unable to do these commands without root can you confirm if after activating VoLTE can we unroot and unlock bootloader? The reason I ask is because I heard unlocked bootloader removes widevine l1. Thanks for any advice.
maxsterling said:
Ok now that you've confirmed unable to do these commands without root can you confirm if after activating VoLTE can we unroot and unlock bootloader? The reason I ask is because I heard unlocked bootloader removes widevine l1. Thanks for any advice.
Click to expand...
Click to collapse
Yes, you can unroot. But to lock bootloader again, you need to reset your phone.
So, unroot yes, lock bootloader no.
Seosam said:
Yes, you can unroot. But to lock bootloader again, you need to reset your phone.
So, unroot yes, lock bootloader no.
Click to expand...
Click to collapse
But if we are willing to reset phone to lock bootloader then this is ok too? When we lock bootloader will the VoLTE changes made remain? Thanks again. Cheers
maxsterling said:
But if we are willing to reset phone to lock bootloader then this is ok too? When we lock bootloader will the VoLTE changes made remain? Thanks again. Cheers
Click to expand...
Click to collapse
I'm not sure. But I think it will reset the modem too. So you will lost Volte.