Related
I do Cell testing and one of the my phones updated to 4.3 now I cant find the right menu. *#7482# (qualcomm usb settings menu) i need to change the RMNET + DM + MODEM
Please help need it to work tomorrow
davidtanis said:
I do Cell testing and one of the my phones updated to 4.3 now I cant find the right menu. *#7482# (qualcomm usb settings menu) i need to change the RMNET + DM + MODEM
Please help need it to work tomorrow
Click to expand...
Click to collapse
I found it *#0808#
davidtanis said:
I found it *#0808#
Click to expand...
Click to collapse
THANKS, been searching for days now for this option
Thanks
I have been searching for days also many thanks
Do you know how to get to USB Settings on a Verizon I535 upgraded to 4.3? The listed methods do not work. I have been searching for hours!! I do cell testing and require the phone to be RMNET as well.
yockfu said:
Do you know how to get to USB Settings on a Verizon I535 upgraded to 4.3? The listed methods do not work. I have been searching for hours!! I do cell testing and require the phone to be RMNET as well.
Click to expand...
Click to collapse
Please look at this link. From the link I provided you, it appears it is ##366633# - Next time, please don't hijack threads.
I was having a heck of a time trying to downgrade to 4.0.4 to unlock my phone, then found out it's because Bell updated the bootloader to make it harder to unlock/downgrade.
Realizing this I flashed a new recovery (to root) and attempted to use SamMobile SRS unlock. I'm running into issues, and wanted to ask for help.
I am using these instructions, but I can't select I747-NS1 since it's not even an option.
Hopefully someone has advice. Here are the errors I get from SRS
9:22:19 PM - OMAP Testmode: Done
9:22:19 PM - Reading Phonedata...
9:22:20 PM - Imei: 3xxxxxxxxx5006
9:22:20 PM - Chipset: M8960A-AAAANAZM-1.0.443100
9:22:20 PM - Analysing phone..
- ERROR: Access Denied (13)
Your phone have new security, please select model I747M-ns1 in the software and try again..
-- Operation done in 4 seconds --
Is it b the Knox software that is causing the problem? Did you try using Knox removal utility?
audit13 said:
Is it b the Knox software that is causing the problem? Did you try using Knox removal utility?
Click to expand...
Click to collapse
I'm using the SRS (Samsung Remote Server) 123Unlock GSM services. I took a screen of the software and the error. At this point I'm not sure if I am missing something or if these guys are providing wrong info.
Never used that service before although I have used online locking services before.
oh, if you can let me know the service, I will try them instead.
I'm not satisfied with 123unlocker. Their instructions were incorrect, their support not great, and considering I'm paying money to unlock -- I don't expect to be figuring out things on my own like this.
I used fastgsm.com.
You need to be running stock ROM too.
Cool, thank you for the referral.
I will flash back to stock ROM, unlock and then flash back to custom. ;p I'll update the post on my progress in case anyone else runs into this problem.
Hmm, FastGSM doesn't work either. I have stock 4.3 with the latest bootloader I747MVLUEMK5. Were you able to unlock and if so do you have any tips?
1. Make sure your phone battery is 100% charged.
2. Turn on your phone without SIM card.
3. Go to the Phone Keypad and dial *#7284#.
4. Set UART to PDA.
5. Select "Qualcomm USB Settings". (I have to use *#0808# instead)
6. Select "DM+MODEM+ADB" and press "OK".
7. Exit ServiceMode menu.
8. Now restart your phone and wait until it fully starts up.
9. Plug your phone to the computer via USB and wait until all drivers are installed.
10. Unplug the USB cable, wait 10 seconds and plug it back to your phone.
11. Click "Next" button.
Reading firmwareware version...
READING FIRMWAREWARE VERSION : [FAIL]
READING FIRMWAREWARE VERSION : [FAIL]
READING FIRMWAREWARE VERSION : [FAIL]
Reading firmwareware version...
READING FIRMWAREWARE VERSION : [FAIL]
READING FIRMWAREWARE VERSION : [FAIL]
READING FIRMWAREWARE VERSION : [FAIL]
READING FIRMWAREWARE VERSION : [FAIL]
READING FIRMWAREWARE VERSION : [FAIL]
READING FIRMWAREWARE VERSION : [FAIL]
READING FIRMWAREWARE VERSION : [FAIL]
Your recovery is also the stock recovery?
I've used that service to unlock a Bell s2 HD LTE, a Bell Samsung Discovery, and a Samsung Wave. Sorry, I have never used the service to unlock an s3.
As it turns out, I had to use GSMLiberty, and paid for an unlock code. It worked the first try and cost $31 CAD. Sucks, but not worth wasting my time with the other unlockers that use SRS which don't even appear to work with the latest bootloader. >.<
I'll try uploading a video to get a free unlock/refund.
Edit--
I Uploaded a video of the unlock, and posted it for them and got a free unlock! (saved the $30.99 CAD) Definitely the way to go at this point until the new bootloader can be downgraded!!
Thank you again for all the assistance, and I hope someone finds these threads useful.
This is the video of me unlocking:
vimeo.com/96549806
Thank you again for the assistance. I factory unlocked and received a free unlock for uploading a vid of the unlock and helpful info.
Currently the phone is running Android 4.3. The phone is currently locked to Fido.
Baseband version: I747MVKUEMK5
Is it possible to unlock this phone? If not, is there unlock codes like for Blackberry on ebay that are 99cents?
Only if you have an unlock code. You can usually get one from the carrier or buy one online. Yes, you can find them on ebay.
Thanks for the help! Ill look on ebay seems like its about 13-15$ to unlock the phone.
DHeffernan said:
Thanks for the help! Ill look on ebay seems like its about 13-15$ to unlock the phone.
Click to expand...
Click to collapse
That may seem expensive but not compared to the Bell version of the i747m.
Really? Wasn't that long ago I heard about people doing this for less than $5. Ill see if I cant find it later. Think it was in the T-Mobile General sections unlock thread if you want to search through it yourself.
audit13 said:
That may seem expensive but not compared to the Bell version of the i747m.
Click to expand...
Click to collapse
Well this is a FIDO one. You got a better and cheaper source?
DocHoliday77 said:
Really? Wasn't that long ago I heard about people doing this for less than $5. Ill see if I cant find it later. Think it was in the T-Mobile General sections unlock thread if you want to search through it yourself.
Click to expand...
Click to collapse
Well there was a free way until android 4.3 came which blocked that. The current one I tried tonight ($13) just emailed me back and said he couldn't find a code for my IMEI.. Wtf.
Can either of you help me with a better source?
Sorry, I don't have a cheaper source. I was able to unlock my phones using the free method. I was lucky enough to find three i747m phones from Bell that were all running 4.1.2.
No worries. I think I might have found another few sources that are around 13-15$.
When I was searching around for the GPS fix(GPS tends to break when you switch from TouchWiz to AOSP or vice versa a bunch of times, and for me as a crack flasher this would be a bummer) I found out about the same service menu you guys use to unlock the phones. I was unable to even reach the menu, but surprisingly enough it worked perfectly with one ROM I flashed. The last step(which is used to initialize the NV data or something similar) doesn't exist in the menu, but there is an option to rebuild the NV data, which might be a perfect substitute. So it might be theoretically possible to unlock the S3, even on 4.3! Can someone please try the steps below and report back? (you will be flashing another ROM, so be prepared to do a full wipe)
1-) Download StockMOD ROM located in the Android development section, not sure if you should use 4.4 or 4.3, please try both and report.
2-) Flash the zip file using the custom recovery of your choice. Make sure to do a full wipe.
3-) Open the dialer of your phone and enter the code *#197328640#, it will open the Service Mode Menu.
4-) In the Service Mode Menu, select [1] UMTS. If you select the wrong option by mistake, press the menu button of your device and select back.
5-) In the menu under UMTS, select the [1] DEBUG SCREEN.
6-) In the Debug Screen, select [8] PHONE CONTROL.
7-) In the Network Lock Screen, select [3] PERSO SHA256 OFF and wait for 30 seconds. Then press the Menu button and select back.
Now, if you're lucky, there might be an option called [4] NW Lock NV Data INITIALLIZ, I personally couldn't find it, and this method itself is untested(can't test it myself, my only phone is hardbricked from the KitKat update and I already unlocked it on 4.1.1). If you're lucky, press that option, wait for a couple of minutes, reboot the phone and you're done! If you're not, look for the NV Rebuild option somewhere in the menus, I can't give direct instructions because I don't own a phone at the moment. If you find it, wait a minute and reboot. If it's unlocked, please report back.
CBKarabudak said:
When I was searching around for the GPS fix(GPS tends to break when you switch from TouchWiz to AOSP or vice versa a bunch of times, and for me as a crack flasher this would be a bummer) I found out about the same service menu you guys use to unlock the phones. I was unable to even reach the menu, but surprisingly enough it worked perfectly with one ROM I flashed. The last step(which is used to initialize the NV data or something similar) doesn't exist in the menu, but there is an option to rebuild the NV data, which might be a perfect substitute. So it might be theoretically possible to unlock the S3, even on 4.3! Can someone please try the steps below and report back? (you will be flashing another ROM, so be prepared to do a full wipe)
1-) Download StockMOD ROM located in the Android development section, not sure if you should use 4.4 or 4.3, please try both and report.
2-) Flash the zip file using the custom recovery of your choice. Make sure to do a full wipe.
3-) Open the dialer of your phone and enter the code *#197328640#, it will open the Service Mode Menu.
4-) In the Service Mode Menu, select [1] UMTS. If you select the wrong option by mistake, press the menu button of your device and select back.
5-) In the menu under UMTS, select the [1] DEBUG SCREEN.
6-) In the Debug Screen, select [8] PHONE CONTROL.
7-) In the Network Lock Screen, select [3] PERSO SHA256 OFF and wait for 30 seconds. Then press the Menu button and select back.
Now, if you're lucky, there might be an option called [4] NW Lock NV Data INITIALLIZ, I personally couldn't find it, and this method itself is untested(can't test it myself, my only phone is hardbricked from the KitKat update and I already unlocked it on 4.1.1). If you're lucky, press that option, wait for a couple of minutes, reboot the phone and you're done! If you're not, look for the NV Rebuild option somewhere in the menus, I can't give direct instructions because I don't own a phone at the moment. If you find it, wait a minute and reboot. If it's unlocked, please report back.
Click to expand...
Click to collapse
I read through some of the other threads and the 4.1.1 modem is required to get the unlock option but the 4.1.1 modem will not work on a 4.3 bootloader. Users have even loaded a completely stock 4.1.1 ROM onto a 4.3 bootloader without any luck.
audit13 said:
I read through some of the other threads and the 4.1.1 modem is required to get the unlock option but the 4.1.1 modem will not work on a 4.3 bootloader. Users have even loaded a completely stock 4.1.1 ROM onto a 4.3 bootloader without any luck.
Click to expand...
Click to collapse
The ROM I mentioned about is a 4.3 ROM(there's even a 4.4 version if I remember correctly) but for some odd reason the service menu opens perfectly on it, so if you haven't unlocked yet, can you please try the instructions I posted and report back?
CBKarabudak said:
The ROM I mentioned about is a 4.3 ROM(there's even a 4.4 version if I remember correctly) but for some odd reason the service menu opens perfectly on it, so if you haven't unlocked yet, can you please try the instructions I posted and report back?
Click to expand...
Click to collapse
I can't try it since all of my phones have already been unlocked. The stock mod ROM needs the i747 bootloader and my phones are three i747m.
audit13 said:
I can't try it since all of my phones have already been unlocked. The stock mod ROM needs the i747 bootloader and my phones are three i747m.
Click to expand...
Click to collapse
I have an i747M and I installed it perfectly, i747 and i747M ROM's are perfectly interchangeable, just make sure you do NOT install any sorts of bootloaders/modems/anything, that will brick your phone. As long as you only flash the zip file, you shouldn't have any problems, at least I didn't.
Well I just ordered the unlock code $8.99. We will see if it works.
audit13 said:
I read through some of the other threads and the 4.1.1 modem is required to get the unlock option but the 4.1.1 modem will not work on a 4.3 bootloader. Users have even loaded a completely stock 4.1.1 ROM onto a 4.3 bootloader without any luck.
Click to expand...
Click to collapse
Should also mention that downgrading from the 4.3 bootloaders will brick their device.
CBKarabudak said:
I have an i747M and I installed it perfectly, i747 and i747M ROM's are perfectly interchangeable, just make sure you do NOT install any sorts of bootloaders/modems/anything, that will brick your phone. As long as you only flash the zip file, you shouldn't have any problems, at least I didn't.
Click to expand...
Click to collapse
The reason I mentioned the fact that I have an i747m is that I could not load the stock mod ROM because I do not have an i747 bootloader and I would never attempt to load an i747 bootloader onto an i747m.
BWolf56 said:
Should also mention that downgrading from the 4.3 bootloaders will brick their device.
Click to expand...
Click to collapse
That's what I read when I further googled some stuff.. lots of people reporting bricking phones if they downgrade.. and it's just not worth it to me considering the unlock code was $9...
I'll report back if this unlock code comes through, the last place I purchased it from $13 they emailed me back and said they couldn't find a code for it and refunded me the money. So crossing my fingers on this place.
StockMod should run just fine on the I747M. You may need to update your firmware for it to flash, but it would work just fine on that model.
So the second place got back to me.. also informing me that they can't get a unlock code for the phone. WTF is the deal with this?
Are Samsung's difficult to unlock or what?
DHeffernan said:
So the second place got back to me.. also informing me that they can't get a unlock code for the phone. WTF is the deal with this?
Are Samsung's difficult to unlock or what?
Click to expand...
Click to collapse
It's not so much about Samsung's phone but being a Canadian variant. Canadian carriers are a pita when it comes to unlocking.
Hi!
So I bought a HTC 10 from Amazon back in May and, even though the product description said it was the US version which had LTE bands for US carriers (specifically 4-AWS), they sent me a M10h, which is the international/asian version that doesn't support band 4. I can't return the phone though, since I'm from Argentina and with the insane customs ruling here, sending the phone to the US and back would cost me almost as much as just buying selling mine (at a highly reduced pricepoint since it doesn't support LTE in my country) and buying a new one.
After a lot of reading here in XDA, paying 25$ to be S-Off, flashing radios, changing roms and kernels, and a bunch of other stuff, I've come to the conclusion that my only alternative left is to change the 06828 NV value (which determinates what LTE bands are activated) with QXDM/DFS tools/whatever program. I've managed to put the phone in diag mode (for those who don't know how, I'll leave a little tutorial in the end of the thread), but when I write the value and then read it again it's back to its original state. I guess this is some kind of protection Qualcomm/HTC/whoever put in place to avoid users messing around with this stuff.
I read in the HTC One M9 forums that users with CDMA phones could change the 06828 value, while I, using a GSM phone, have been able to change 06829. I tried using a Verizon radio, which turns on and off the diag mode for some reason, and a Sprint radio, which gives me a "diag error response" in QXDM when I try to read/write any NV value.
Maybe a custom kernel can help avoid the write protection for NV values? I don't know a lot about that kind of stuff, so it's the only thing that I believe could change my situation
Phone info:
White HTC 10 M10h model
LeeDroid 10 v2.4.1-stable rom with CleanSlate kernel
S-Off and root
Baseband version [email protected]_51.01_F
---------------------------------------------------------------------------
For those who can't make it to Diag Mode:
1) Install the HTC Diag Drivers in your PC
2) Install a terminal emulator in your phone (in my case I used SManager)
3) Connect the phone to the computer with the USB cable
4) In the terminal emulator use:
Code:
su
and then
Code:
setprop sys.usb.config diag
5) Now touch on the "Use USB for" notification.
6) If everything worked, the phone should block you from choosing any option in the list besides Charging and USB tethering
7) Choose USB tethering
8) Your phone should appear in the Windows Device Manager as HTC Diagnostic Interface, which means the phone is in Diag Mode
9) To return to the default USB mode, repeat step 4, but replacing setprop sys.usb.config diag for
Code:
setprop sys.usb.config mtp
--------------------------------------------------------------------------
Does anyone know any way to make my phone work? Any kernel made from scratch I can try? I'm really desperate.
Thank you all for reading!
wouldnt flashing the us unlocked ruu work out since your all s-off and unlocked?
afuller42 said:
wouldnt flashing the us unlocked ruu work out since your all s-off and unlocked?
Click to expand...
Click to collapse
Unfortunately, it doesn't. As I can check both trying to use the phone or reading the NV values with DFS tool, the LTE bands remain the same no matter what RUU, radio or whatever I try.
Up!
Nachorl250 said:
Up!
Click to expand...
Click to collapse
Could you post a guide as to how can it be done?
INDIAN-MAfIA said:
Could you post a guide as to how can it be done?
Click to expand...
Click to collapse
I'm sorry, I don't get what you're asking me. A guide to do what?
Nachorl250 said:
I'm sorry, I don't get what you're asking me. A guide to do what?
Click to expand...
Click to collapse
I thought you got your unlocked band 'up and running' not realising you just wanted to accelerate your thread to the top. My bad.
INDIAN-MAfIA said:
I thought you got your unlocked band 'up and running' not realising you just wanted to accelerate your thread to the top. My bad.
Click to expand...
Click to collapse
No problem!
Nachorl250 said:
Unfortunately, it doesn't. As I can check both trying to use the phone or reading the NV values with DFS tool, the LTE bands remain the same no matter what RUU, radio or whatever I try.
Click to expand...
Click to collapse
As I have stated in other posts, we need a kernel built from scratch rather than a "custom kernel".
No custom kernel for Sense is going to work for this purpose.
Cyanogenmod technically provides that built-from-scratch kernel that we need., but the trick there is enabling Diagnostic Mode.
You can either flash Resurrection or Beanstalk and try to find a way to activate it.
An idea that could work is messing arround with the init.qcom.usb.rc and init.usb.rc files.
Those files include the triggers for several usb modes (the setprop sys.usb.config line).
The problem for Cyanogenmod is that those files don't include triggers for Diag.
So one way could be to replace them or modifying them.
I'm no coder at all, but to modify those files we need to modify the ramdisk at the boot partition.
If we don't, every modification to these files won't be kept past reboot.
Even achieving it won't assure Diag Mode, but I'm running out of ideas.
This certainly trascends my scarce knowledge
And CM is not at a point suitable for daily driver, so any testing there would be going back and forth between CM and Sense.
So unless we find a way to enable Diagnostic Mode on CM we are stuck.
I ran into the same issue as you. I bought a white 32gb thinking it was all the same, didn't know that it was the m10h.
I had to s-off, and change the CID and MID number to SuperCID and US unlocked MID , then install the latest US RUU to get the US firmware/radios/etc.
Currently on T-mobile, and all I have in my area is Band 12 (which my phone picks up), and I saw it pick up another band, but can't recall what it was. I wanna say that it worked, but I can't verify that my phone is actually reading all of the US LTE bands.
I'm switching to cricket (att) sometime this week. Once I switch over, I can check to see which bands im getting around my home and work
activated my cricket SIM, and I'm currently connecting to band 17.
will drive around town and take notes on what bands i pick up
Sports same issue here, I can't get my phone to work on au network in Japan.
kainanmaki said:
As I have stated in other posts, we need a kernel built from scratch rather than a "custom kernel".
No custom kernel for Sense is going to work for this purpose.
Cyanogenmod technically provides that built-from-scratch kernel that we need., but the trick there is enabling Diagnostic Mode.
You can either flash Resurrection or Beanstalk and try to find a way to activate it.
An idea that could work is messing arround with the init.qcom.usb.rc and init.usb.rc files.
Those files include the triggers for several usb modes (the setprop sys.usb.config line).
The problem for Cyanogenmod is that those files don't include triggers for Diag.
So one way could be to replace them or modifying them.
I'm no coder at all, but to modify those files we need to modify the ramdisk at the boot partition.
If we don't, every modification to these files won't be kept past reboot.
Even achieving it won't assure Diag Mode, but I'm running out of ideas.
This certainly trascends my scarce knowledge
And CM is not at a point suitable for daily driver, so any testing there would be going back and forth between CM and Sense.
So unless we find a way to enable Diagnostic Mode on CM we are stuck.
Click to expand...
Click to collapse
Thank you for all the info! We should make a main thread on the subject so that we can better organize ourselves and everyone can help solve this problem.
Nachorl250 said:
Thank you for all the info! We should make a main thread on the subject so that we can better organize ourselves and everyone can help solve this problem.
Click to expand...
Click to collapse
I agree. But I think it could be better to wait for a full port of Cyanogenmod.
Guys over there are making big strides, and maybe they could help us achieving diag mode for CM.
Don't want to bug them with this issue until they are at peace with the full port (and they seem to be really close to the end).
It's sad, but I don't even know how to bake a rom modifying a couple of files.
Even in that case, my idea was to use part of the code of init.qcom.usb.rc and init.usb.rc from Sense.
And introduce it on the init.qcom.usb.rc and init.usb.rc files of CM.
Checking which folders are involved on the code, they are present too in CM.
Which makes me believe that modifying those files on CM could prove enough for DIAG to be activated with "setprop sys.usb.config diag". It's just a guess though.
I'm sure that maybe crpalmer and squid2 could help us with this later.
De alguna forma va a salir...
[FONT="]echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
[FONT="][FONT="][FONT="][FONT="][FONT="][FONT="][FONT="][FONT="][FONT="][FONT="]did you try this code? it work[FONT="]ed f[FONT="]or me on M8 on custom roms viper one, A[FONT="]RHD[FONT="], maximusHD and few others.
[FONT="]BTW i [FONT="]still cant get to write nv values on my phone either[FONT="]. The[FONT="]y[/FONT]revert to old values after reboot. Still trying to figure out a way. will be flashing [FONT="]custom [FONT="]kitkat bas[FONT="]ed rom with custom revovery to try my luck.
[FONT="]I even t[FONT="]r[FONT="]ied[FONT="] [/FONT][/FONT] to disable one supported band 20 just to be sure if [FONT="]is hardware limitation that is causing the nv val[FONT="]ues to revert. But i[FONT="] found out that the nv values[FONT="] are not being written al all. So it is definitely not [FONT="]band compatibility issue.
[FONT="]May you too could try the same and check if at all you are able to write to nv.[/FONT]
[/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT] [/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT]
---------- Post added at 05:51 PM ---------- Previous post was at 05:06 PM ----------
Nachorl250 said:
Unfortunately, it doesn't. As I can check both trying to use the phone or reading the NV values with DFS tool, the LTE bands remain the same no matter what RUU, radio or whatever I try.
Click to expand...
Click to collapse
Dont you have the option to select which radio band region to select as in Unlocked intl M8?
what does it show when you open phone info->select 3 dots->select radio band ? do you atleast have this option?
smartpal said:
[FONT="]echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
[FONT="][FONT="][FONT="][FONT="][FONT="][FONT="][FONT="][FONT="][FONT="][FONT="]did you try this code? it work[FONT="]ed f[FONT="]or me on M8 on custom roms viper one, A[FONT="]RHD[FONT="], maximusHD and few others.
[FONT="]BTW i [FONT="]still cant get to write nv values on my phone either[FONT="]. The[FONT="]y[/FONT]revert to old values after reboot. Still trying to figure out a way. will be flashing [FONT="]custom [FONT="]kitkat bas[FONT="]ed rom with custom revovery to try my luck.
[FONT="]I even t[FONT="]r[FONT="]ied[FONT="] [/FONT][/FONT] to disable one supported band 20 just to be sure if [FONT="]is hardware limitation that is causing the nv val[FONT="]ues to revert. But i[FONT="] found out that the nv values[FONT="] are not being written al all. So it is definitely not [FONT="]band compatibility issue.
[FONT="]May you too could try the same and check if at all you are able to write to nv.[/FONT]
[/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT] [/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT]
---------- Post added at 05:51 PM ---------- Previous post was at 05:06 PM ----------
Dont you have the option to select which radio band region to select as in Unlocked intl M8?
what does it show when you open phone info->select 3 dots->select radio band ? do you atleast have this option?
Click to expand...
Click to collapse
Instead of using "echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on", we use the setprop type of lines.
They work properly on stock HTC rom. You can enable ADB,MTP, RNDIS, Modem and so on, including the all important DIAG (Diagnostic).
And the reason it's not working on CM is that the presets that enable and disable this kind of command do not include DIAG in any of them.
So you can't use setprop to invoke DIAG, or at least to my knowledge. Would love to be proven wrong here.
Since the presets work in a script fashion, maybe using the line related to DIAG could trigger the mode, I just don't know how to use it.
For E.G, the setprop sys.usb.config=diag does the following on tht init.qcom.usb.rc file (located at root of FS).
Code:
on property:sys.usb.config=diag
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 05C6
write /sys/class/android_usb/android0/idProduct 900E
write /sys/class/android_usb/android0/f_diag/clients diag
write /sys/class/android_usb/android0/functions diag
write /sys/class/android_usb/android0/enable 1
setprop sys.usb.state ${sys.usb.config}.
Maybe someone does have a clue of how to use it on CyanogenMod. Which is closer to be a reality so maybe in some weeks we can ask the guys over the CM thread for some help.
kainanmaki said:
Instead of using "echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on", we use the setprop type of lines.
They work properly on stock HTC rom. You can enable ADB,MTP, RNDIS, Modem and so on, including the all important DIAG (Diagnostic).
And the reason it's not working on CM is that the presets that enable and disable this kind of command do not include DIAG in any of them.
So you can't use setprop to invoke DIAG, or at least to my knowledge. Would love to be proven wrong here.
Since the presets work in a script fashion, maybe using the line related to DIAG could trigger the mode, I just don't know how to use it.
Click to expand...
Click to collapse
setprop sys.usb.diag.config diagon
this code worked for me on M8 with CM11. It did enable the diag mode atleast for me. Just now tried it.
smartpal said:
[FONT="]echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
[FONT="][FONT="][FONT="][FONT="][FONT="][FONT="][FONT="][FONT="][FONT="][FONT="]did you try this code? it work[FONT="]ed f[FONT="]or me on M8 on custom roms viper one, A[FONT="]RHD[FONT="], maximusHD and few others.
[FONT="]BTW i [FONT="]still cant get to write nv values on my phone either[FONT="]. The[FONT="]y[/FONT]revert to old values after reboot. Still trying to figure out a way. will be flashing [FONT="]custom [FONT="]kitkat bas[FONT="]ed rom with custom revovery to try my luck.
[FONT="]I even t[FONT="]r[FONT="]ied[FONT="] [/FONT][/FONT] to disable one supported band 20 just to be sure if [FONT="]is hardware limitation that is causing the nv val[FONT="]ues to revert. But i[FONT="] found out that the nv values[FONT="] are not being written al all. So it is definitely not [FONT="]band compatibility issue.
[FONT="]May you too could try the same and check if at all you are able to write to nv.[/FONT]
[/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT] [/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT]
---------- Post added at 05:51 PM ---------- Previous post was at 05:06 PM ----------
Dont you have the option to select which radio band region to select as in Unlocked intl M8?
what does it show when you open phone info->select 3 dots->select radio band ? do you atleast have this option?
Click to expand...
Click to collapse
We don't have that option in the HTC 10
Nachorl250 said:
We don't have that option in the HTC 10
Click to expand...
Click to collapse
dont you have any option to go in testing mode just like *#*#4636#*#* for M8?
smartpal said:
dont you have any option to go in testing mode just like *#*#4636#*#* for M8?
Click to expand...
Click to collapse
Oh, I was looking for it in the settings menu. It doesn't change anything, though.
This Work From Version NCQ26.69-56 up to NCQ26.69-64-X .
Solution One :
Download shortcut master
Then on app search to find
SETTINGS
select com.motorola.programmenu.PgmApnSettings
Launch > New APN
Solution Two :
Download Terminal Emulator .
on the terminal :
1. su
2. am start com.motorola.programmenu/.PgmApnSettings
3. NEW APN
Solution Three :
need adb tools. adb drivers
From The Computer
Open Cmd Or PowerShell Or Bash If Is On Linux
1. Enable Usb Debugging >> Connect The Phone To The Pc
2. adb devices >> Authorize on the Phone
3. adb shell
4. su
5. am start com.motorola.programmenu/.PgmApnSettings
3. NEW APN
Thanks Everybody :> no More Frustration Or Downgrading Or Hardbriking Trying To. Happy 4G LTE Hotspot
Thank you @ozmage, for your informative guide. This will undoubtedly benefit users who want the most recent firmware build AND the ability to use a GSM service provider. Nice work.
MotoJunkie01 said:
Thank you @ozmage, for your informative guide. This will undoubtedly benefit users who want the most recent firmware build AND the ability to use a GSM service provider. Nice work.
Click to expand...
Click to collapse
No Thank You Man Is An Honor Coming From You , And Yes Im Glad To Help And Share This Discovery.
someone knows how to get the msl code ? not calling the Carrier
Hi, I have a problem
Hello, I update my Moto E4 Sprint and now it does not let me create a new APN, these options need root, but I can not find the post to root this phone, if you know some post to root this phone, please can tell me, excuse my English because I do not know much. Thank you very much.
Leodanis said:
Hello, I update my Moto E4 Sprint and now it does not let me create a new APN, these options need root, but I can not find the post to root this phone, if you know some post to root this phone, please can tell me, excuse my English because I do not know much. Thank you very much.
Click to expand...
Click to collapse
1. Boot loader unlock (through official Motorola boot loader unlock) https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
2. Flash twrp via (fastboot flash recovery recovery.img) https://forum.xda-developers.com/mo...velopment/twrp-twrp-moto-g4-qualcomm-t3655160
3. Flash Magisk On Twrp . https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Step 0 : Enable Developer Options , Enable Oem Unlocking , Enable Usb Debugging , Run Adb On The Computer With The Phone Connected And Authorize ADB , Reboot To Fastboot unlock bootloader etc
Done !!!
ozmage said:
1. Boot loader unlock (through official Motorola boot loader unlock) https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
2. Flash twrp via (fastboot flash recovery recovery.img) https://forum.xda-developers.com/mo...velopment/twrp-twrp-moto-g4-qualcomm-t3655160
3. Flash Magisk On Twrp . https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Step 0 : Enable Developer Options , Enable Oem Unlocking , Enable Usb Debugging , Run Adb On The Computer With The Phone Connected And Authorize ADB , Reboot To Fastboot unlock bootloader etc
Click to expand...
Click to collapse
Thank you very much, I just needed to root my phone and with that magisk worked, I can create apn, thanks. :good::good::good:
Leodanis said:
Thank you very much, I just needed to root my phone and with that magisk worked, I can create apn, thanks. :good::good::good:
Click to expand...
Click to collapse
Glad To Help :good:
A question
ozmage said:
Glad To Help :good:
Click to expand...
Click to collapse
I used this method because I installed several custom rom (aicp_perry_n-12.1-UNOFFICIAL-20180202, aoscp_perry-4.1.2-20180127-unofficial and RR-N-v5.8.5-20171206-perry-Unofficial), but in all case my phone does not catch signal, but with the official is ok, What can be ?.
Thanks for your time.
Leodanis said:
I used this method because I installed several custom rom (aicp_perry_n-12.1-UNOFFICIAL-20180202, aoscp_perry-4.1.2-20180127-unofficial and RR-N-v5.8.5-20171206-perry-Unofficial), but in all case my phone does not catch signal, but with the official is ok, What can be ?.
Thanks for your time.
Click to expand...
Click to collapse
Yes This Is A Problem That Comes With The Last Ota Several People Have This Problem Included Myself , But Soon This Will Be Solved By Squid2 The Maintainer Of Lineage-Os For Moto E4 Perry , The RIL Binaries From New Stock Needs To Be Cooked In LOS
And Other Roms.
Leodanis said:
I used this method because I installed several custom rom (aicp_perry_n-12.1-UNOFFICIAL-20180202, aoscp_perry-4.1.2-20180127-unofficial and RR-N-v5.8.5-20171206-perry-Unofficial), but in all case my phone does not catch signal, but with the official is ok, What can be ?.
Thanks for your time.
Click to expand...
Click to collapse
Has anyone found a fix yet
Bailey36375 said:
Has anyone found a fix yet
Click to expand...
Click to collapse
No. The latest OTA update remove the ability to use a custom ROM to use it on a different network
Not try to use different networks want to stay on boost but when if flash from stock to a custom rom there's no data or signal i was hoping that dome one had a working custom rom on boost that could do a back up and send it to me to flash.
Bailey36375 said:
Not try to use different networks want to stay on boost but when if flash from stock to a custom rom there's no data or signal i was hoping that dome one had a working custom rom on boost that could do a back up and send it to me to flash.
Click to expand...
Click to collapse
You might need blobs and APN fix zip for boost
I've got blobs and apn but still not working.
---------- Post added at 04:00 AM ---------- Previous post was at 03:57 AM ----------
I flashed blobs and apn together and separated before I booted but still nothing can you explain what I may be doing wrong
Does it mean that if I follow the instruction to root, twrp, Magisk and then bring up the APN menu, I can use the E4 with other GSM carriers? As long as I stay stock?
nookin said:
Does it mean that if I follow the instruction to root, twrp, Magisk and then bring up the APN menu, I can use the E4 with other GSM carriers? As long as I stay stock?
Click to expand...
Click to collapse
Having root does not bring up the APN settings menu. You have to actually find the file in the system and edit it manually.
madbat99 said:
Having root does not bring up the APN settings menu. You have to actually find the file in the system and edit it manually.
Click to expand...
Click to collapse
That's what this command does, right?
am start com.motorola.programmenu/.PgmApnSettings
Can someone confirm that I can turn an XT1766 with latest OTA into a phone that works with GSM and remain stock firmware?
In other words, does editing APN gives stock firmware the ability to use GSM?
nookin said:
That's what this command does, right?
am start com.motorola.programmenu/.PgmApnSettings
Can someone confirm that I can turn an XT1766 with latest OTA into a phone that works with GSM and remain stock firmware?
In other words, does editing APN gives stock firmware the ability to use GSM?
Click to expand...
Click to collapse
Yep. Also check this post out. https://forum.xda-developers.com/mo...estoring-moto-e4-xt1766-t3820749/post77194110
If you get your MSL code from your carrier you can also enter the menu with ##3282# to edit your APN also a few other things including band priority.
See this post
madbat99 said:
Yep. Also check this post out. https://forum.xda-developers.com/mo...estoring-moto-e4-xt1766-t3820749/post77194110
If you get your MSL code from your carrier you can also enter the menu with ##3282# to edit your APN also a few other things including band priority.
See this post
Click to expand...
Click to collapse
I can bring up the ##3282# menu. You mean the lock code for Edit APN? It is a 6 digits number. I wonder if there is a limit on number of attempts? 6-digits is not a terribly large combination.