Download connect bot
click the ssh dropdown and pick local, put a nickname
in terminal type "su" without quotes
after your $ turns to # type getprop ril.MSL
the readout is your msl, comes in handy for when you're doing late night dev and can't get ahold of sprint, or just don't feel like lying lol.
EDIT: to use su you need root access, I'm not sure if this works without superuser permissions, this was the first command I've tried
okay, just tried, and you DO NOT need to use su, you can just type getprop ril.MSL and you will get the same readout
jlear3 said:
EDIT: to use su you need root access, I'm not sure if this works without superuser permissions, this was the first command I've tried
okay, just tried, and you DO NOT need to use su, you can just type getprop ril.MSL and you will get the same readout
Click to expand...
Click to collapse
It works without superuser no problem.
Good find!
Sent from my SPH-D710 using XDA App
jlear3 said:
Download connect bot
click the ssh dropdown and pick local, put a nickname
in terminal type "su" without quotes
after your $ turns to # type getprop ril.MSL
the readout is your msl, comes in handy for when you're doing late night dev and can't get ahold of sprint, or just don't feel like lying lol.
EDIT: to use su you need root access, I'm not sure if this works without superuser permissions, this was the first command I've tried
okay, just tried, and you DO NOT need to use su, you can just type getprop ril.MSL and you will get the same readout
Click to expand...
Click to collapse
I'm not sure why but every time I type ril, it changes it to rIl, which obviously will not work since it's case sensitive. I have tried Terminal Emulator and get the same result. I am not rooted, completely stock. I used connect bot on my OG Epic 4G and didn't have this issue.
Any idea how to get past this?
this has been around for ages
Use samsung keboard thats a swype thing.
PsycloneTW said:
I'm not sure why but every time I type ril, it changes it to rIl, which obviously will not work since it's case sensitive. I have tried Terminal Emulator and get the same result. I am not rooted, completely stock. I used connect bot on my OG Epic 4G and didn't have this issue.
Any idea how to get past this?
Click to expand...
Click to collapse
Sent from my SPH-D710 using XDA App
Yes don't use swype change to samsung keyboard
Sent from my SPH-D710 using xda premium
nice find thx
imtjnotu said:
this has been around for ages
Click to expand...
Click to collapse
I'm aware but I also am aware not everyone knows it and I figures id help...
Sent from my SPH-D710 using XDA App
You guys are awesome . The Samsung keyboard fixed it for me .
I"m not sure if I'm looking in the wrong place but I see where I'm typing in the emulator, I type getprop ril.msl and press enter
it just goes to the next line
EDIT - My bad, I didn't have the MSL in caps.
Anyone have a link that explains what other information is available with getprop ril.MSL?
You can get it without root just send this password to the phone with cdma workshop (free version) 01F2030F5F678FF9
Sent from my Galaxy S2 using Tapatalk
vdub804 said:
You can get it without root just send this password to the phone with cdma workshop (free version) 01F2030F5F678FF9
Sent from my Galaxy S2 using Tapatalk
Click to expand...
Click to collapse
You can get it via terminal emulator without root using getprop til.MSL
Sent from my SPH-D710 using Tapatalk
Great! This worked like a charm. Does the Starburst rom not have the default samsung dailpad?
Im not rooted and i cant terminal to switch from $ to #
Sent from my Samsung Galaxy S2 Epic Touch 4g
Switching from $ to # denotes switching to root user id, so that is expected given you aren't rooted.
However, you don't need to be rooted to run "getprop ril.MSL"
sfhub said:
Switching from $ to # denotes switching to root user id, so that is expected given you aren't rooted.
However, you don't need to be rooted to run "getprop ril.MSL"
Click to expand...
Click to collapse
Thats where im having the issue i get no result when i run getprop ril.MSL is there more to the command from the $ prompt
Sent from my Samsung Galaxy S2 Epic Touch 4g
Like a charm!
Sent from my SPH-D710 using xda premium
Optimal Carnage said:
Thats where im having the issue i get no result when i run getprop ril.MSL is there more to the command from the $ prompt
Click to expand...
Click to collapse
Not sure what is going wrong. It works on stock unrooted. Are you sure you are typing MSL in caps and ril in lower case? You have it right in your post, but sometimes people type different things not realizing it is case sensitive.
Related
my computer wont detect my myTouch Slide when im trying to root it. It wont show the "device is offline" after i put it in recovery mode after i typed in loop. Does anyone know why thats happening
Type in loop? Not sure why do that, but to mount your phone with adb for rooting you should stay off with the command 'adb devices'
Sent from my T-Mobile myTouch 3G Slide using XDA App
guitarist5122 said:
Type in loop? Not sure why do that, but to mount your phone with adb for rooting you should stay off with the command 'adb devices'
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
I think he's talking about running the loop.bat file. It loops the 'adb devices' command. You might remember it from the original root method written by Eugene.
For the question: Did you 'cd' to the sdk tools directory? If you want to know about that look in the "slide rom bible" (search xda for it) and find the original slide rooting method written by Eugene. Read it, watch the vids, and you'll learn all this stuff. You can't use his method now since your slide has the tmobile update.
yeah i was doing it watching the video too and yeah i cded by doing CD C:\android-sdk-windows\tools and like i did loop then went into the fastboot thing and did recovery and instead of saying offline devices it just saud "List of Devices Attatched" and under it its supposed to say offline device cuz i saw it from the video but its just a blank spot
The loop method NO LONGER WORKS AFTER THE LATEST SOFTWARE UPDATE. If you got your slide after August 13, you have the new software update. The ONLY working method with the software update is nbetcher's.
Sent from my T-Mobile myTouch 3G Slide using XDA App
And where do I get the instructions for the nbetchers thing?
Personguy96 said:
And where do I get the instructions for the nbetchers thing?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=754020
Personguy96 said:
And where do I get the instructions for the nbetchers thing?
Click to expand...
Click to collapse
By using the search bar.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Looks like the boot.img on the WiFi only model is slightly different. Flashed the rooted boot.img file and now I'm stuck at the Dual Core technology screen. Anyone have this available. All help greatly appreciated!
UPDATE
See thread -> http://forum.xda-developers.com/showthread.php?p=12432218
Can someone post the stock xoom wifi dump of the boot.img, recovery.img, system.img, and userdata.img in case something happens?
Apparently it looks like its slightly different than the wifi+3g version. Also is the overclocked kernel file working posted by coolbho3000?
i need the answer too... i m comfused.
Alright I have a stock Xoom tablet now Just gotta figure out how to pull the boot.img file off. Any ideas and I'll do it ASAP.
No clue mate. From my knowledge you have to be rooted, or have the SDK on your pc. I think. Neither which are available as of now
So is the wifi only version able to be rooted as of now?
currently, yes. We need a new root method. Well I would not say a new "method" but their need to be some modifications done to the original rootboot img file. Shouldnt be hard for devs
found the answer here:
http://forum.xda-developers.com/show...&postcount=134
coolbho3000 said:
If you want to rip your current one, run
# cat /dev/block/platform/sdhci-tegra.3/by-name/boot > /sdcard/boot.img
onicrom said:
found the answer here:
http://forum.xda-developers.com/show...&postcount=134
coolbho3000 said:
If you want to rip your current one, run
# cat /dev/block/platform/sdhci-tegra.3/by-name/boot > /sdcard/boot.img
Click to expand...
Click to collapse
Issue 1: Don't currently have root
Issue 2: No SD card access
But I did try it and got an access denied.
onicrom said:
found the answer here:
http://forum.xda-developers.com/show...&postcount=134
coolbho3000 said:
If you want to rip your current one, run
# cat /dev/block/platform/sdhci-tegra.3/by-name/boot > /sdcard/boot.img
Click to expand...
Click to collapse
Think for the Xoom it would be from a windows command prompt:
adb shell cat /dev/block/platform/sdhci-tegra.3/by-name/boot > c:\boot.img
I could be wrong but try it and see.
Sent from my Nexus One using XDA Premium App
B Dizzle said:
Think for the Xoom it would be from a windows command prompt:
adb shell cat /dev/block/platform/sdhci-tegra.3/by-name/boot > c:\boot.img
I could be wrong but try it and see.
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
It's actually a Permission issue.
/dev/block/platform/sdhci-tegra.3/by-name/boot: Permission denied
So someone with root needs to run it. Anyone wanna help out? Im not getting mine till tomorrow but by then I suppose you would have yours exchanged
Sent from my Nexus One using XDA Premium App
B Dizzle said:
So someone with root needs to run it.
Click to expand...
Click to collapse
That's actually the catch-22... can't get root because we don't have the right boot.img file. I think it's going to boil down to Motorola releasing a stock one.
If anyone is up for IRC chat - hop onto Freenode and room #Xoom
I can try if someone tells me what needs to be done. I tried copying it over to another folder in root explorer but no luck.
Update: Ran through the fastboot oem unlock in hopes that it would resolve the Permission Denied. It did not.
http://forum.xda-developers.com/showpost.php?p=11863700&postcount=154
destroyerbmx said:
http://forum.xda-developers.com/showpost.php?p=11863700&postcount=154
Click to expand...
Click to collapse
You'll end up with a (soft)brick
No luck
I also booted into fast boot, tried and still got no permission sometimes and no such directory some times... If some one will walk me through getting the img file I will gladly do so
how can I remove the softbrick, I saw this AFTER I tried to root and now I cannot even turn it off, just sitting on the Motorola Dual Core Technology screen.
ok I also now need to the stock boot.img from a wifi xoom. Can anyone help? I can flash it if someone can provide it please, if not I guess I will go exchange my xoom in the morning.
has anyone started to root this device?
i need to gain access to the root folder
It's really annoying, with the bootloader unlocked it's like if Jessica Biel is nude on your bed and saying come here honey,let me have a good time(root me)...but you don't because you don't have the durex
Lol what a way to put it
Sent from my LT15i using Tapatalk
vegetaleb said:
It's really annoying, with the bootloader unlocked it's like if Jessica Biel is nude on your bed and saying come here honey,let me have a good time(root me)...but you don't because you don't have the durex
Click to expand...
Click to collapse
+1
hahah this made my day
I will try tomorrow. Will have to get testers as I can only test on DHD.
vegetaleb said:
It's really annoying, with the bootloader unlocked it's like if Jessica Biel is nude on your bed and saying come here honey,let me have a good time(root me)...but you don't because you don't have the durex
Click to expand...
Click to collapse
Good 1 :-D
lollylost100 said:
I will try tomorrow. Will have to get testers as I can only test on DHD.
Click to expand...
Click to collapse
I would like to help testing. just pm me when you need a tester
vegetaleb said:
It's really annoying, with the bootloader unlocked it's like if Jessica Biel is nude on your bed and saying come here honey,let me have a good time(root me)...but you don't because you don't have the durex
Click to expand...
Click to collapse
Whaha really Genius!
But rooting can't be far away now..... Because I don't think the Durex is sold out in the super market. I actually think they have a special offer...
It's precisely because of the lack of root access that I've held of unlocking my bootloader; I don't see any point of having to erase all my data and setting up my device when there's no pay-off in the form of root and custom ROMs
Yeah well you never know if SE change their minds and cancel the unlocking website
Better get your gift before Santa takes it back
I will try to convince Marc from MIUI to think about the Arc...
I don't think SE will change it's mind, but the longer you wait, the more adjustments you make on your device (well at least I do..). So that's why I unlocked the bootloader as soon as I had my Arc. Even though I had allready played with it. But what the h*ll, now I had to play a bit longer with it. I don't see the problem
They wont change their mind but the downside of unlocking is that you cannot update using SEUS
Hopefully SE will change that if you use stock firmware but have the bootloader unlocked
Sent from my LT15i using XDA App
Blomkungen said:
They wont change their mind but the downside of unlocking is that you cannot update using SEUS
Hopefully SE will change that if you use stock firmware but have the bootloader unlocked
Sent from my LT15i using XDA App
Click to expand...
Click to collapse
I don't see where that's a problem : if you unlock your bootloader, it's because you want to flash custom roms, isn't it ?
Who care about stock update when we get better functionnalities and often faster updates with all the leaks with custom roms ?
I need somebody to carry out the following steps on their bootloader unlocked device
1. Enable USB Debugging
2. Run adb and enter the following commands (line-by-line)
Code:
adb shell
su
What is the response?
lollylost100 said:
I need somebody to carry out the following steps on their bootloader unlocked device
1. Enable USB Debugging
2. Run adb and enter the following commands (line-by-line)
Code:
adb shell
su
What is the response?
Click to expand...
Click to collapse
permission denied
lollylost100 said:
I need somebody to carry out the following steps on their bootloader unlocked device
1. Enable USB Debugging
2. Run adb and enter the following commands (line-by-line)
Code:
adb shell
su
What is the response?
Click to expand...
Click to collapse
su: permission denied
lollylost100 said:
I need somebody to carry out the following steps on their bootloader unlocked device
1. Enable USB Debugging
2. Run adb and enter the following commands (line-by-line)
Code:
adb shell
su
What is the response?
Click to expand...
Click to collapse
I try to test when I reach home. Don't I need to push the su to the phone first?
Sent from my Xperia Arc
I don't have my PC with working ADB drivers here, try this:
adb remount
adb shell
su
Sometimes it need the adb remount to access system files
vegetaleb said:
I don't have my PC with working ADB drivers here, try this:
adb remount
adb shell
su
Sometimes it need the adb remount to access system files
Click to expand...
Click to collapse
remount failed: operation not permitted
We definitely need a custom Boot image flashed then!
If only I took Linux courses...
I sent my tablet off to get repaired after it was bricked. My new version is different when it boots than it used to be. the new build version number on my tablet is " Acer_AV041_A100_1.015.00_PA_CUS1 " and it is on kernel 2.6.39.4+. is this what others have? When i boot it now comes up with 2 acer logos one in the upper right and left. than changes to the normal center acer then android .
max69power said:
I sent my tablet off to get repaired after it was bricked. My new version is different when it boots than it used to be. the new build version number on my tablet is " Acer_AV041_A100_1.015.00_PA_CUS1 " and it is on kernel 2.6.39.4+. is this what others have? When i boot it now comes up with 2 acer logos one in the upper right and left. than changes to the normal center acer then android .
Click to expand...
Click to collapse
This is exactly what I've been waiting to see. If you can get adb up can you paste the output of adb shell cat /proc/cmdline ? The boot loader change may hint at Acer doing some work on the cause of the brick.
Tapatalked from my Galaxy S II.
pio_masaki said:
This is exactly what I've been waiting to see. If you can get adb up can you paste the output of adb shell cat /proc/cmdline ? The boot loader change may hint at Acer doing some work on the cause of the brick.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
I will get it up in about 45 min when I can get back to my PC.
do i need it rooted ? I got permission denied
max69power said:
do i need it rooted ? I got permission denied
Click to expand...
Click to collapse
Probably do accessing that file to output. You could try adb root then try again but it'll probably deny that too. If you don't want to root that's cool I'll wait to see if I can pay for mine to get fixed then do it when I get it back.
Tapatalked from my Galaxy S II.
i rooted and unlocked it is still says access is denied. i am willing to try something else.
pio_masaki said:
Probably do accessing that file to output. You could try adb root then try again but it'll probably deny that too. If you don't want to root that's cool I'll wait to see if I can pay for mine to get fixed then do it when I get it back.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
if there is a way just to copy the os and boot loader i will put it up
max69power said:
i rooted and unlocked it is still says access is denied. i am willing to try something else.
Click to expand...
Click to collapse
try:
Code:
adb kill-server; adb root; adb wait-for-device; adb shell cat /proc/cmdline
If you are rooted and adb starts as root you shouldn't get permission denied. If you still do get permission denied give output of :
Code:
adb shell ls -l /proc
This will be quiet large, but we really only need to know the specific line like this:
-r--r----- root radio 0 2012-08-12 02:44 cmdline
And make sure that you aren't getting any messages like "Root isn't available in Production builds"
Thanks.
i got unknown option '-1' aborting. I will have to pick this up tomorrow afternoon.
Copy your SDK platform tools to the desktop and try again. From there.
Check android debugging
Sent from my A500 using xda app-developers app
Oh its L not 1, lowercase.
If he isn't rooted he doesn't have busy box. Just saying.
Tapatalked from my Galaxy S II.
i am charging it i will start trying in a few min. I am rooted and unlocked.
I have seen the .015 pa cus, its nothing unusual. It was one of the first ics ota's.
Romman0 said:
I have seen the .015 pa cus, its nothing unusual. It was one of the first ics ota's.
Click to expand...
Click to collapse
have you seen it start out with 2 acer logos when you are not rooted or unlocked? That was the first thing i noticed that was different.
I did the comand i got a ton of lines saying root and the one line you asked about is the same except for a different time.
Romman0 said:
I have seen the .015 pa cus, its nothing unusual. It was one of the first ics ota's.
Click to expand...
Click to collapse
Its the boot loader change that I'm interested in, not really the system image.
Tapatalked from my Galaxy S II.
linuxsociety said:
try:
Code:
adb kill-server; adb root; adb wait-for-device; adb shell cat /proc/cmdline
If you are rooted and adb starts as root you shouldn't get permission denied. If you still do get permission denied give output of :
Code:
adb shell ls -l /proc
This will be quiet large, but we really only need to know the specific line like this:
-r--r----- root radio 0 2012-08-12 02:44 cmdline
And make sure that you aren't getting any messages like "Root isn't available in Production builds"
Thanks.
Click to expand...
Click to collapse
ok i have done these and tried the first line again also but the first line is still denied. I will keep an eye on this thread if you want me to try anything else.
max69power said:
have you seen it start out with 2 acer logos when you are not rooted or unlocked? That was the first thing i noticed that was different.
Click to expand...
Click to collapse
I have not seen the dual logos. It is very interesting.
But didn't you just overwrite the new bootloader you had by installing the unlocked a200 bootloader?
i rooted and unlocked it is still says access is denied. i am willing to try something else
Click to expand...
Click to collapse
true i guess i did
I'm trying to find my msl number for my phone.. I have tried connectbot and terminal e and cant see to get it to find anything.. When I type in the getprop ril.MSL and hit enter it just goes to another command line.. So I typed in getprop and scrolled down to the ril. section and ther is no ril.mls listed.. So how do I get the msl for my Sprint version of the Galaxy s3
Thanks for this development. Downloading now.
Sent from my SPH-L710 using xda premium
Read forum rules before posting
Questions go in Q&A
Thread moved
FNM
Sent from my SPH-L710 using xda premium
doubledragon5 said:
I'm trying to find my msl number for my phone.. I have tried connectbot and terminal e and cant see to get it to find anything.. When I type in the getprop ril.MSL and hit enter it just goes to another command line.. So I typed in getprop and scrolled down to the ril. section and ther is no ril.mls listed.. So how do I get the msl for my Sprint version of the Galaxy s3
Click to expand...
Click to collapse
Message me. I may be able to help.
doubledragon5 said:
I'm trying to find my msl number for my phone.. I have tried connectbot and terminal e and cant see to get it to find anything.. When I type in the getprop ril.MSL and hit enter it just goes to another command line.. So I typed in getprop and scrolled down to the ril. section and ther is no ril.mls listed.. So how do I get the msl for my Sprint version of the Galaxy s3
Click to expand...
Click to collapse
Goto dialer ##3282# enter any 6 numbers then open terminal and do the getprop.
When I tried to get mine, none of that worked. I ended up just calling Tech support, and telling them I was having trouble with my phone signal. The helped me with how to update my prl. I told them, I had done it before and If it didnt work this time, I did not want to have to call back and wait for hours on tech support. I had heard there is a code I can use to reset my phone and make it like it was before I started, Could the save me the call back and hours on the phone, but just giving me the number now?
They helped me out with the MSL code. For some reason no other way worked.
Dan
scoobysnack said:
Goto dialer ##3282# enter any 6 numbers then open terminal and do the getprop.
Click to expand...
Click to collapse
did all that last night with no luck using connectbot or terminal E
doubledragon5 said:
did all that last night with no luck using connectbot or terminal E
Click to expand...
Click to collapse
Sorry my bad that only works on a TW ROM. You could always flash a new ROM and grab your MSL.
Called sprint ,told them I bought it, paid full price and wanted my msl code. They gave it to me no problem
What worked for me GS3 and GN2 Sprint
I started fresh using a reboot on both devices. I went to dialer and hit ##3282#. I then went to edit mode and entered an incorrect MSL code as instructed above. I used 123456 for both devices. Enter the incorrect code only once, as I accidentally did it twice on my Note 2 and it caused it to reboot. I then opened Terminal Emulator and typed the above getprop ril.MSL and it displayed my MSL for both devices. I wasn't having any luck with GetMyMSL or ConnectBot. Terminal Emulator didn't work for me at first on my GS3 until i did the above steps. Hope this helps someone.
Mike
PS -- I'm stock rooted JellyBean for both devices
getting msl code
kuroyoma said:
Message me. I may be able to help.
Click to expand...
Click to collapse
I also am having that same exact issue with my sprint Samsung s4. can you help? : ) thanks in advance
Look up msl utility
Sent from my SPH-L710 using XDA Premium 4 mobile app
The one that looks like a lock
Sent from my SPH-L710 using XDA Premium 4 mobile app
luvsm said:
I also am having that same exact issue with my sprint Samsung s4. can you help? : ) thanks in advance
Click to expand...
Click to collapse
Sent you a PM.