alright I have only tested this on the MI3 firmware, but I have tested it on rooted and stock and both worked. I have sucessfully gotten the MSL without sprint and I also changed it to 000000. Ok so here are the instructions....
MAKE SURE YOU FOLLOW STEPS VERY CAREFULLY, BECAUSE THEY WORK IF YOU DO EXACTLY AS I DO, I HAVE TESTED ON 3 DIFFERENT NOTE 3 NOW AND IT WORKED ON ALL 3 OF THEM.
Ok so first make sure usb debugging is on and unknown sources and that your using the newest adb out and that you have adb access.
next make sure you are on mtp+adb, I havent been able to get it working if diag is enabled so dont enable it.
ok now open the file GETMSL.bat, and its going to run a logcat in the background thats fineas long as its running thats all you need.
VERY IMPORTANT, if you dont do this exactly it wont work ok.
DIAL ##3424# not ##3282# only ##3424# will work, and then click edit or enter msl and then MAKE SURE you put 123456 as the password. Nothing else works that I have tried so it has to be 123456 and then click ok.
Its going to give you a bad spc error, thats fine press back till your at the home screen and sit and wait for 5 seconds. After that unplug your cable from the phone and read the command prompt for your msl. THIS WORKS but you have to follow exactly.
Thanks for everyone who let me get there msl over team viewer and get this fine tuned. If you have questions or need help just let me know Ill be glad to assist you in any way I can.
E:\Download\Mobile\N900P\GETMSL>findstr "I/MSL_Checker( 1166):" logcat.txt
I/MSL_Checker( 1185): onCreate
I/MSL_Checker( 1185): onCreate2
I/MSL_Checker( 1185): hdata_edit
I/MSL_Checker( 1185): Chameleon diag valuenull
I/MSL_Checker( 1185): Chameleon Check value2false
I/MSL_Checker( 1185): connect To Secphone service
I/MSL_Checker( 1185): onCreate1
I/MSL_Checker( 1185): hdata_edit
I/MSL_Checker( 1185): hdata_edit
I/MSL_Checker( 1185): Enter checkMSLCode
I/MSL_Checker( 1185): success to write
I/MSL_Checker( 1185): End checkMSLData
I/MSL_Checker( 1185): error=0
I/MSL_Checker( 1185): size of result : 14
heixiuyo said:
E:\Download\Mobile\N900P\GETMSL>findstr "I/MSL_Checker( 1166):" logcat.txt
I/MSL_Checker( 1185): onCreate
I/MSL_Checker( 1185): onCreate2
I/MSL_Checker( 1185): hdata_edit
I/MSL_Checker( 1185): Chameleon diag valuenull
I/MSL_Checker( 1185): Chameleon Check value2false
I/MSL_Checker( 1185): connect To Secphone service
I/MSL_Checker( 1185): onCreate1
I/MSL_Checker( 1185): hdata_edit
I/MSL_Checker( 1185): hdata_edit
I/MSL_Checker( 1185): Enter checkMSLCode
I/MSL_Checker( 1185): success to write
I/MSL_Checker( 1185): End checkMSLData
I/MSL_Checker( 1185): error=0
I/MSL_Checker( 1185): size of result : 14
Click to expand...
Click to collapse
what build are u on? Is your kernel stock??
robhuffster said:
what build are u on? Is your kernel stock??
Click to expand...
Click to collapse
JSS15J.N900PVPUBMI3
dial # # 3424 # does not require input MSL,I use dial # # 3282 #, get this result
Will this work on mj5
for most people on MI3 ##3424# does require msl, and im not sure if it works on other builds, give it a try and let me know, I have only had mine to do this too and there might be other steps that are required to do this let me know if it doesnt work and ill post other steps
Ran on my phone and couldn't find the msl line. Msl checker is on there though.
hkleiner said:
Ran on my phone and couldn't find the msl line. Msl checker is on there though.
Click to expand...
Click to collapse
alright well i hope you have root cause you will need it now if you pull your /data/system/packages.xml and send it to me (just use adb pull /data/system/packages.xml if it gives you a permission error then do adb remount first, of that doesnt work then download this apk here and browse to the location and copy it to your sd card and then send it and Ill edit the files necassary to get your msl to show up.
I am rooted yes. Could also just let me know what lines to change.
---------- Post added at 10:26 PM ---------- Previous post was at 10:21 PM ----------
Link for xml
https://db.tt/mLAMZsNf
the first post has been updated and is working
Has not worked yet, even with the hidden menu enabled.
hkleiner said:
Has not worked yet, even with the hidden menu enabled.
Click to expand...
Click to collapse
its probably because your not on MI3? heres my file if anyone wants to use it and then run the script ill show you what it does!!
look at my pictures after i change those settings
it shows my msl
Anyone confirm this works? I am downloading mi3 but I have a feeling that won't change anything.
---------- Post added at 06:12 AM ---------- Previous post was at 06:09 AM ----------
I never saw the phonutil_vmu line. I enabled the hidden menu. What am I missing.
hkleiner said:
Anyone confirm this works? I am downloading mi3 but I have a feeling that won't change anything.
---------- Post added at 06:12 AM ---------- Previous post was at 06:09 AM ----------
I never saw the phonutil_vmu line. I enabled the hidden menu. What am I missing.
Click to expand...
Click to collapse
hey you have to do ##3424# ok dont do ##3282# becuase it doesnt work and it does work using ##3424#
robhuffster said:
hey you have to do ##3424# ok dont do ##3282# becuase it doesnt work and it does work using ##3424#
Click to expand...
Click to collapse
I got the MSL code. Thanks a lot
Root Not Required
Here is some steps which i used.
1. enable USB debug
2. connect phone with the pc , it will ask you for permission. click on check box & Ok.
3. run the cmd "adb devices" it will show you (see screenshot)
List of devices attached
0f3ab02x device
if not(offline) pl update your adb tool. search on Google "latest adb for 4.3 or 4.2.2 android".
4. Copy GETMSL.bat into adb folder & run
5. Dial ##3424# enter 123456
6. cmd will not show you any output.
7. goto adb folder & open logcat.txt file (dnt close cmd)
8. search "I/MSL_Checker" press enter 4-5 times & you'll get the MSL code.(see screenshot)
Special Thanks to "robhuffster"
adb tools link for note 3
what is the link to adb tools for the note 3
javed91214 said:
Root Not Required
Here is some steps which i used.
1. enable USB debug
2. connect phone with the pc , it will ask you for permission. click on check box & Ok.
3. run the cmd "adb devices" it will show you (see screenshot)
List of devices attached
0f3ab02x device
if not(offline) pl update your adb tool. search on Google "latest adb for 4.3 or 4.2.2 android".
4. Copy GETMSL.bat into adb folder & run
5. Dial ##3424# enter 123456
6. cmd will not show you any output.
7. goto adb folder & open logcat.txt file (dnt close cmd)
8. search "I/MSL_Checker" press enter 4-5 times & you'll get the MSL code.(see screenshot)
Special Thanks to "robhuffster"[/QUO
Click to expand...
Click to collapse
ghettowar04 said:
what is the link to adb tools for the note 3
javed91214 said:
Root Not Required
Here is some steps which i used.
1. enable USB debug
2. connect phone with the pc , it will ask you for permission. click on check box & Ok.
3. run the cmd "adb devices" it will show you (see screenshot)
List of devices attached
0f3ab02x device
if not(offline) pl update your adb tool. search on Google "latest adb for 4.3 or 4.2.2 android".
4. Copy GETMSL.bat into adb folder & run
5. Dial ##3424# enter 123456
6. cmd will not show you any output.
7. goto adb folder & open logcat.txt file (dnt close cmd)
8. search "I/MSL_Checker" press enter 4-5 times & you'll get the MSL code.(see screenshot)
Special Thanks to "robhuffster"[/QUO
Click to expand...
Click to collapse
Click to expand...
Click to collapse
robhuffster said:
hey you have to do ##3424# ok dont do ##3282# becuase it doesnt work and it does work using ##3424#
Click to expand...
Click to collapse
How can # # 3424 # ok?##3424# does require msl。
heixiuyo said:
How can # # 3424 # ok?##3424# does require msl。
Click to expand...
Click to collapse
##3424# does not require msl for me on jellybomb.
I want to use QPST to unlock bands
But I have to enable Diag Mode first
I'v tried [setprop sys.usb.config diag,adb] [setprop persist.usb.eng 1] [echo 1 > /sys/class/android_usb/android0/enable]
but doesn't work...
windswoods said:
I want to use QPST to unlock bands
But I have to enable Diag Mode first
I'v tried [setprop sys.usb.config diag,adb] [setprop persist.usb.eng 1] [echo 1 > /sys/class/android_usb/android0/enable]
but doesn't work...
Click to expand...
Click to collapse
As far as I can tell you need a different pinout usb cable or something. Even in engineering mode and enabling diag mode does not work
I have tried everything I know and have come to the idea that the phones usb port has a different pinout for qcom usb and it is infact enabling. we can test this by flashing cm12 and trying to enable qcom usb. But I am not willing to go that far
tjsooley said:
As far as I can tell you need a different pinout usb cable or something. Even in engineering mode and enabling diag mode does not work
I have tried everything I know and have come to the idea that the phones usb port has a different pinout for qcom usb and it is infact enabling. we can test this by flashing cm12 and trying to enable qcom usb. But I am not willing to go that far
Click to expand...
Click to collapse
It sounds hard to do ..
I found this on the web:
on property:sys.usb.config=diag,adb
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 05C6
write /sys/class/android_usb/android0/idProduct 9025
write /sys/class/android_usb/android0/f_diag/clients diag
write /sys/class/android_usb/android0/f_serial/transports smd,tty
write /sys/class/android_usb/android0/f_rmnet/transports smd,bam
write /sys/class/android_usb/android0/functions diag,adb,serial,rmnet,mass_storage
write /sys/class/android_usb/android0/enable 1
start adbd
setprop sys.usb.state $sys.usb.config
on property:sys.usb.config=diag,mdm,adb
stop adbd
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 05C6
write /sys/class/android_usb/android0/idProduct 9031
write /sys/class/android_usb/android0/f_diag/clients diag,diag_mdm
write /sys/class/android_usb/android0/f_serial/transports hsic,tty
write /sys/class/android_usb/android0/f_serial/transport_names serial_hsic
write /sys/class/android_usb/android0/f_rmnet/transports hsic,hsic
write /sys/class/android_usb/android0/f_rmnet/transport_names rmnet_hsic
write /sys/class/android_usb/android0/functions diag,adb,serial,rmnet,mass_storage
write /sys/class/android_usb/android0/enable 1
start adbd
setprop sys.usb.state ${sys.usb.config}
# Fusion 3 composition with diag_mdm and adb
on property:sys.usb.config=diag,diag_mdm,serial_hsic,serial_tty,rmnet_hsic,mass_storage,adb
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 05C6
write /sys/class/android_usb/android0/idProduct 9031
write /sys/class/android_usb/android0/f_diag/clients diag,diag_mdm
write /sys/class/android_usb/android0/f_serial/transports hsic,tty
write /sys/class/android_usb/android0/f_serial/transport_names serial_hsic
write /sys/class/android_usb/android0/f_rmnet/transports hsic,hsic
write /sys/class/android_usb/android0/f_rmnet/transport_names rmnet_hsic
write /sys/class/android_usb/android0/functions diag,adb,serial,rmnet,mass_storage
write /sys/class/android_usb/android0/enable 1
start adbd
setprop sys.usb.state ${sys.usb.config}
Powered by Gitiles
I try to use 'android terminal emulator' ,and then connect to PC
It appear a unknow device but I can't find driver for it..
windswoods said:
It sounds hard to do ..
I found this on the web:
on property:sys.usb.config=diag,adb
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 05C6
write /sys/class/android_usb/android0/idProduct 9025
write /sys/class/android_usb/android0/f_diag/clients diag
write /sys/class/android_usb/android0/f_serial/transports smd,tty
write /sys/class/android_usb/android0/f_rmnet/transports smd,bam
write /sys/class/android_usb/android0/functions diag,adb,serial,rmnet,mass_storage
write /sys/class/android_usb/android0/enable 1
start adbd
setprop sys.usb.state $sys.usb.config
on property:sys.usb.config=diag,mdm,adb
stop adbd
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 05C6
write /sys/class/android_usb/android0/idProduct 9031
write /sys/class/android_usb/android0/f_diag/clients diag,diag_mdm
write /sys/class/android_usb/android0/f_serial/transports hsic,tty
write /sys/class/android_usb/android0/f_serial/transport_names serial_hsic
write /sys/class/android_usb/android0/f_rmnet/transports hsic,hsic
write /sys/class/android_usb/android0/f_rmnet/transport_names rmnet_hsic
write /sys/class/android_usb/android0/functions diag,adb,serial,rmnet,mass_storage
write /sys/class/android_usb/android0/enable 1
start adbd
setprop sys.usb.state ${sys.usb.config}
# Fusion 3 composition with diag_mdm and adb
on property:sys.usb.config=diag,diag_mdm,serial_hsic,serial_tty,rmnet_hsic,mass_storage,adb
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 05C6
write /sys/class/android_usb/android0/idProduct 9031
write /sys/class/android_usb/android0/f_diag/clients diag,diag_mdm
write /sys/class/android_usb/android0/f_serial/transports hsic,tty
write /sys/class/android_usb/android0/f_serial/transport_names serial_hsic
write /sys/class/android_usb/android0/f_rmnet/transports hsic,hsic
write /sys/class/android_usb/android0/f_rmnet/transport_names rmnet_hsic
write /sys/class/android_usb/android0/functions diag,adb,serial,rmnet,mass_storage
write /sys/class/android_usb/android0/enable 1
start adbd
setprop sys.usb.state ${sys.usb.config}
Powered by Gitiles
I try to use 'android terminal emulator' ,and then connect to PC
It appear a unknow device but I can't find driver for it..
Click to expand...
Click to collapse
Can you post the script file your using?
tjsooley said:
Can you post the script file your using?
Click to expand...
Click to collapse
I don't know how to use script file
I type it on 'android terminal emulator'
adb shell
su
stop adbd
echo 0 > /sys/class/android_usb/android0/enable
echo 1004 > /sys/class/android_usb/android0/idVendor
echo 631B > /sys/class/android_usb/android0/idProduct
echo 239 > /sys/class/android_usb/android0/bDeviceClass
echo 2 > /sys/class/android_usb/android0/bDeviceSubClass
echo 1 > /sys/class/android_usb/android0/bDeviceProtocol
echo tty > /sys/class/android_usb/android0/f_acm/acm_transports
echo diag,diag_mdm > /sys/class/android_usb/android0/f_diag/clients
echo acm,diag,mtp,adb > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable 1
start adbd
setprop sys.usb.state diag,adb
Here is a script file from that code. it does change the driver type. I tried the modified htc diag drivers forcing them and it does not work so if this did put the phone is qcom mode we need to find the drivers. to run the script you need to copy it to the /data and using root explorer click on it and select execute you will need to adjust the permissions to allow exec first
tjsooley said:
Here is a script file from that code. it does change the driver type. I tried the modified htc diag drivers forcing them and it does not work so if this did put the phone is qcom mode we need to find the drivers. to run the script you need to copy it to the /data and using root explorer click on it and select execute you will need to adjust the permissions to allow exec first
Click to expand...
Click to collapse
I successfully installed the driver,but QPST still not connected to the phone..
windswoods said:
I successfully installed the driver,but QPST still not connected to the phone..
Click to expand...
Click to collapse
I am in the same spot
tjsooley said:
As far as I can tell you need a different pinout usb cable or something. Even in engineering mode and enabling diag mode does not work
I have tried everything I know and have come to the idea that the phones[QRCODE][/QRCODE] usb port has a different pinout for qcom usb and it is infact enabling. we can test this by flashing cm12 and trying to enable qcom usb. But I am not willing to go that far
Click to expand...
Click to collapse
I have tried to flash cm12(cm-12.1-20150417-NIGHTLY-t00n.zip),then use different script file. But when I do when the phone is not even connected to the computer, really strange.
Finally, I went back to the Android 4.4...
9002 is no diag port for QPST, forcing HTC modified drivers wont work here. It should be Asus's own Qualcomm Port ( if there is any ).
https://play.google.com/store/apps/details?id=com.afp_group.software&hl , install this apk to Asus phone and try to find any secret code ( dial pad combination ). I have found a couple of secret codes that opens diag port for QPST and installed them with Qualcomm's own drivers, Vivo Xplay 3s for example, in early days. Please do a backup, some of secret codes do hard reset to phone. Hope this helps.
PS: Try on stock rom please.
---------- Post added at 10:35 PM ---------- Previous post was at 10:28 PM ----------
windswoods said:
I have tried to flash cm12(cm-12.1-20150417-NIGHTLY-t00n.zip),then use different script file. But when I do when the phone is not even connected to the computer, really strange.
Finally, I went back to the Android 4.4...
Click to expand...
Click to collapse
Trying to install cm11 and the command "setprop sys.usb.config diag,adb, or setprop persist.usb.eng 1" might help too. No diag ports in Android 5 with those scripts ( commands ) as far as i know ( experianced it on Oneplus, works on Kitkat, nothing on Lolipop).
os_man said:
9002 is no diag port for QPST, forcing HTC modified drivers wont work here. It should be Asus's own Qualcomm Port ( if there is any ).
https://play.google.com/store/apps/details?id=com.afp_group.software&hl , install this apk to Asus phone and try to find any secret code ( dial pad combination ). I have found a couple of secret codes that opens diag port for QPST and installed them with Qualcomm's own drivers, Vivo Xplay 3s for example, in early days. Please do a backup, some of secret codes do hard reset to phone. Hope this helps.
PS: Try on stock rom please.
---------- Post added at 10:35 PM ---------- Previous post was at 10:28 PM ----------
Trying to install cm11 and the command "setprop sys.usb.config diag,adb, or setprop persist.usb.eng 1" might help too. No diag ports in Android 5 with those scripts ( commands ) as far as i know ( experianced it on Oneplus, works on Kitkat, nothing on Lolipop).
Click to expand...
Click to collapse
Done that their is none. I know asus uses the calculator to enable the factory test mode its possible their is a calc code to enable the diag port
I got it!
I got it!
I got a special Nandroid can turn on diag mode
Use Recovery to restore it.
And it contain some tools can turn diag mode
https://drive.google.com/file/d/0BwZ5B9Qa5muabG9vVTRfc2sxMG8/view?usp=sharing
windswoods said:
I got it!
I got a special Nandroid can turn on diag mode
Use Recovery to restore it.
And it contain some tools can turn diag mode
https://drive.google.com/file/d/0BwZ5B9Qa5muabG9vVTRfc2sxMG8/view?usp=sharing
Click to expand...
Click to collapse
Awesome! WHat about QPST? What kind of driver do we need? Can i use this to my Padfone S?
paleszgergo said:
Awesome! WHat about QPST? What kind of driver do we need? Can i use this to my Padfone S?
Click to expand...
Click to collapse
QPST works perfect,I successfully unlocked bands thant I can use 3G in my country.
I think padfone s is the same, but I didn't have padfone s , you can try.
windswoods said:
I got it!
I got a special Nandroid can turn on diag mode
Use Recovery to restore it.
And it contain some tools can turn diag mode
https://drive.google.com/file/d/0BwZ5B9Qa5muabG9vVTRfc2sxMG8/view?usp=sharing
Click to expand...
Click to collapse
What recovery do you use? CWM or TWRP or stock?
Could you post what you did in this rom to get qpat workong? I want to get ot working on padfrone s firmware
Sent from my ASUS_T00N using Tapatalk
tjsooley said:
Could you post what you did in this rom to get qpat workong? I want to get ot working on padfrone s firmware
Sent from my ASUS_T00N using Tapatalk
Click to expand...
Click to collapse
:good: yeah, the backup didnt work on padfone s
My step:
root
flash recovery (cwm6)
unlock bootloader
install padfone s rom
use recovery(cwm6) restore from sperial Nandroid backup
my deviceadfone x
windswoods said:
My step:
root
flash recovery (cwm6)
unlock bootloader
install padfone s rom
use recovery(cwm6) restore from sperial Nandroid backup
my deviceadfone x
Click to expand...
Click to collapse
Won't boot up. got CWM, unlocked BL, restored and then nothing happens
paleszgergo said:
Won't boot up. got CWM, unlocked BL, restored and then nothing happens
Click to expand...
Click to collapse
I do beleave his restore is padfone x firmware not s so you should need to boot cwm6 format everything then restore
In the last MIUI update Xiaomi has disabled the option of disabling the notification for MI Apps which I don't want to use and don't want to see notifications from it. So, I searched the internet and found the trick.
Prerequisites:
1. PC with android SDK or Minimal ADB and Fastboot
Step 1 : Enable developer options on your phone
Step 2 : Enable USB debugging and USB debugging (Security settings) and connect it to your PC
Step 3 : Run Command Prompt as Administrator
Step 4 : Navigate to your ADB folder
Step 5 : Type
Code:
adb devices
Step 6 : then
Code:
adb shell
Step 7 : then
Code:
pm uninstall -k --user 0 com.xiaomi.mipicks
or any other package name you want to get rid of
Thats it. :good:
Enjoy
Dude, big thanks for this tutorial. It was pushing notifications 5 times a day.
I won't be updating this MIUI pos henceforth
Failure [Not installed for 0] error
After performing above steps to unistall Mi Apps ..I am getting error
failure [not installed for 0]
But I was able to uninstall Mi Browser and other google bloatwares.
Also tried disabling MIUI Optimization,
Suggest If there is a option.
I am having Redmi Note 4 with MIUI 9.5
EDIT :
I was entering wrong package name.Be carefull its com.xiaomi.mipicks....that 'a' sucks
Got rid of the error.
skysar said:
In the last MIUI update Xiaomi has disabled the option of disabling the notification for MI Apps which I don't want to use and don't want to see notifications from it. So, I searched the internet and found the trick.
Prerequisites:
1. PC with android SDK or Minimal ADB and Fastboot
Step 1 : Enable developer options on your phone
Step 2 : Enable USB debugging and USB debugging (Security settings) and connect it to your PC
Step 3 : Run Command Prompt as Administrator
Step 4 : Navigate to your ADB folder
Step 5 : Type
Code:
adb devices
Step 6 : then
Code:
adb shell
Step 7 : then
Code:
pm uninstall -k --user 0 com.xiaomi.mipicks
or any other package name you want to get rid of
Thats it. :good:
Enjoy
Click to expand...
Click to collapse
Call it a good disable because apps will be on phone. You can't get rid of them unless you root. Misleading headline.
Sag555 said:
After performing above steps to unistall Mi Apps ..I am getting error
failure [not installed for 0]
But I was able to uninstall Mi Browser and other google bloatwares.
Also tried disabling MIUI Optimization,
Suggest If there is a option.
I am having Redmi Note 4 with MIUI 9.5
EDIT :
I was entering wrong package name.Be carefull its com.xiaomi.mipicks....that 'a' sucks
Got rid of the error.
Click to expand...
Click to collapse
Thanks
First thing to do is to unlock bootloader and then root your device. Then go to terminal on pc and enable usb debugging. type:
adb shell
su
then copy and paste all this into the terminal window : https://del.dog/asovalisad.pl then type enter.
if you go to aida 64 it will tell you that all your sensors are working again. DO NOT REBOOT, FIX DOESN'T STICK AFTER REBOOT Tested on Pixel 3 (blueline) but it should work on every pixel. full credit to @ab123321 and @_LLJY
Add "sync"
Hey if you're touching the persist partition, you'll want to add a "sync" command to flush content out to the disk / UFS.
zaacc said:
First thing to do is to unlock bootloader and then root your device. Then go to terminal on pc and enable usb debugging. type:
adb shell
su
then copy and paste all this into the terminal window : https://del.dog/asovalisad.pl then type enter.
if you go to aida 64 it will tell you that all your sensors are working again. DO NOT REBOOT, FIX DOESN'T STICK AFTER REBOOT Tested on Pixel 3 (blueline) but it should work on every pixel. full credit to @ab123321 and @_LLJY
Click to expand...
Click to collapse
Thank you for sharing the script.
A suggestion to try out: put this script in init so it is initialised at each reboot.
Let us know if it works!