Getting the MSL & Loading Sprint PRL

[UPdownLoAD]

OK, today's driver project:
http://www.alcatelonetouch.com/usa/products/smartphones/ot-909b.html

Click the download tab and install both of the downloads. Then connect your phone and see if it will add the right drivers for QPST (steps 7-9 way above)

 

[Dracable]

ill give it a go a bit later today and post results if no one beats me to it.

 

[sunsuke]

OK, today's driver project:
http://www.alcatelonetouch.com/usa/products/smartphones/ot-909b.html

Click the download tab and install both of the downloads. Then connect your phone and see if it will add the right drivers for QPST (steps 7-9 way above)

i am trying this right now

 

[Dracable]

r u sure the 2nd download isnt some kind of firmware updater? just wanna make sure cuz it didnt seem to clear either way. dont wanna hard brick.

 

[sunsuke]

r u sure the 2nd download isnt some kind of firmware updater? just wanna make sure cuz it didnt seem to clear either way. dont wanna hard brick.

ill see what it is then
from what i see it should only update the android system i think
but since it's at the latest 2.0 (2.3)
i don;t thinik it will update the phone

 

[UPdownLoAD]

The second link is an INSTALLER for an updater. I believe the drivers are included in it. Just download on your PC, install, DON'T RUN.

 

[sunsuke]

The second link is an INSTALLER for an updater. I believe the drivers are included in it. Just download on your PC, install, DON'T RUN.

Nothing, still cannot add a port on QSPT

 

[UPdownLoAD]

Nothing, still cannot add a port on QSPT

OK, I'm going to grab something to eat and will be back later with a few more things to try.

In the meantime, install this: Install Terminal Emulator

Run it, Enter at command prompt: getprop ril.MSL
This will generate a 6 digit code. Write it down and save it!
(Please note, the command is case sensitive)

 

[sunsuke]

OK, I'm going to grab something to eat and will be back later with a few more things to try.

In the meantime, install this: Install Terminal Emulator

Run it, Enter at command prompt: getprop ril.MSL
This will generate a 6 digit code. Write it down and save it!
(Please note, the command is case sensitive)

Did you forget anything in the command? and enjoy your food

 

[UPdownLoAD]

Did you forget anything in the command? and enjoy your food

Nope, EXACTLY getprop ril.MSL (and MSL MUST be CAPITALIZED)

If you tried that, try it again and then try this:
-Install Connectbot
-Open Connectbot
-change ssh to local
-type a nickname and hit enter/done
-type "getprop ril.MSL" without the quotes, this is case sensitive!
The number you see is your MSL.

 

[sunsuke]

Nope, EXACTLY getprop ril.MSL (and MSL MUST be CAPITALIZED)

If you tried that, try it again and then try this:
-Install Connectbot
-Open Connectbot
-change ssh to local
-type a nickname and hit enter/done
-type "getprop ril.MSL" without the quotes, this is case sensitive!
The number you see is your MSL.

Ill try this as soon as i fix my ROM ^^'

 

[UPdownLoAD]

Thanks. 3 things to (re)try for getting the MSL:

-I forgot to add that when you open Terminal Emulator, before you type getprop ril.MSL, you need to type su for superuser! If it shows nothing after typing getprop ril.MSL, type msl. It'll say invalid code. Retype getprop ril.MSL and it'll should now work.

-You may need to type su before typing getprop ril.MSL using Connectbot.

-Download and install aLogcat
Run aLogcat and set it to filter for "sec_code"
Go to your Phone and dial ##33284# or ##786# or ##3282#
When prompted for the MSL, type 000000.
Now, go to aLogcat. And it should have found a "sec_code:" line with your MSL code at the end of it. It's 6 digits.

 

[sunsuke]

Thanks. 3 things to (re)try for getting the MSL:

-I forgot to add that when you open Terminal Emulator, before you type getprop ril.MSL, you need to type su for superuser! If it shows nothing after typing getprop ril.MSL, type msl. It'll say invalid code. Retype getprop ril.MSL and it'll should now work.

-You may need to type su before typing getprop ril.MSL using Connectbot.

-Download and install aLogcat
Run aLogcat and set it to filter for "sec_code"
Go to your Phone and dial ##33284# or ##786# or ##3282#
When prompted for the MSL, type 000000.
Now, go to aLogcat. And it should have found a "sec_code:" line with your MSL code at the end of it. It's 6 digits.

Good to know you put the smiley face i thought you be mad at me for some reason anyways back on to subject i got nothing i took screenshots to see if i am doing something wrong?
and i did also put alogcat filter at "sec_code:"

 

[UPdownLoAD]

Good to know you put the smiley face i thought you be mad at me for some reason anyways back on to subject i got nothing i took screenshots to see if i am doing something wrong?
and i did also put alogcat filter at "sec_code:"

Thanks, the pics show you did it correctly. Did you try again with Terminal Emulator as well?

If you did, I'm giving up on the MSL for the moment and am now going to focus on getting the phone into diagnostic mode. So that said, let's try a few things:

In Terminal Emulator, type:
su
echo 1 > /dev/qct_diag_enable
..and your phone should go into USB diag mode. when you are done just:
echo 0 > /dev/qct_diag_enable

Second Method:
su
echo 1 > /sys/devices/virtual/usb_composite/diag/enable
To disable diag mode:
echo 0 > /sys/devices/virtual/usb_composite/diag/enable

 

[sunsuke]

Thanks, the pics show you did it correctly. Did you try again with Terminal Emulator as well?

If you did, I'm giving up on the MSL for the moment and am now going to focus on getting the phone into diagnostic mode. So that said, let's try a few things:

In Terminal Emulator, type:
su
echo 1 > /dev/qct_diag_enable
..and your phone should go into USB diag mode. when you are done just:
echo 0 > /dev/qct_diag_enable

Second Method:
su
echo 1 > /sys/devices/virtual/usb_composite/diag/enable
To disable diag mode:
echo 0 > /sys/devices/virtual/usb_composite/diag/enable

The Termianl did nothing, sorry for late reply was figuring out how to get my touch keyboard working so i can use the ">" until i dozed off on my keyboard ^^'
but Nothing in the terminal anything else?

 

[UPdownLoAD]

The Termianl did nothing, sorry for late reply was figuring out how to get my touch keyboard working so i can use the ">" until i dozed off on my keyboard ^^'
but Nothing in the terminal anything else?

I think I got that.... anyway here's instructions I found on another phone to force it into diagnostic mode.

-Download and install Anycut
-Open Anycut and select "New Shortcut"
-Now click Activity
-Scroll down the list of activities until you see "Select COM Port Mode" and click it. Just hit ok to accept the default name
-You will see a "shortcut created" notification. Go back to your homescreen and look for the new shortcut
-Once you click the new shortcut you'll see three radio buttons. Simply change from Mass Storage to Diag and your debugging port will be on all the time.

When changed to diag, your phone will reconnect to the PC and drivers will install if necessary.

 

[sunsuke]

I think I got that.... anyway here's instructions I found on another phone to force it into diagnostic mode.

-Download and install Anycut
-Open Anycut and select "New Shortcut"
-Now click Activity
-Scroll down the list of activities until you see "Select COM Port Mode" and click it. Just hit ok to accept the default name
-You will see a "shortcut created" notification. Go back to your homescreen and look for the new shortcut
-Once you click the new shortcut you'll see three radio buttons. Simply change from Mass Storage to Diag and your debugging port will be on all the time.

When changed to diag, your phone will reconnect to the PC and drivers will install if necessary.

Their is no select com port mode ^^' sorry

 

[Dracable]

because we dont have the serial driver for it. are there any devs out there known for building drivers? i imagine that if u are going to find anyone who could build a custom serial driver, its gonna b created and used under linux. i would probably hop over to xda real quick (dont stay gone too long tho! ;-) ) and post a thread in a related linux and/or android development forum. i dont know anything about building drivers personally, so i dont know how realistic this really is, i just know that some linux users build their own drivers to get the most out of their hardware, since most manufacturers do not release linux specific drivers for their products. id say its worth a try! couldnt hurt to ask!

 

[UPdownLoAD]

because we dont have the serial driver for it. are there any devs out there known for building drivers? i imagine that if u are going to find anyone who could build a custom serial driver, its gonna b created and used under linux. i would probably hop over to xda real quick (dont stay gone too long tho! ;-) ) and post a thread in a related linux and/or android development forum. i dont know anything about building drivers personally, so i dont know how realistic this really is, i just know that some linux users build their own drivers to get the most out of their hardware, since most manufacturers do not release linux specific drivers for their products. id say its worth a try! couldnt hurt to ask!

I believe there are drivers (see post #51) but the phone cannot easily be put into Diagnostic mode. There should be a ##code to put in to switch it to diag mode or a script to run in terminal to switch it, but based on sunsuke's findings, nothing is working so far.

 

[sunsuke]

I believe there are drivers (see post #51) but the phone cannot easily be put into Diagnostic mode. There should be a ##code to put in to switch it to diag mode or a script to run in terminal to switch it, but based on sunsuke's findings, nothing is working so far.

hopefully something works ^^'

 

[UPdownLoAD]

I spent sometime last night with my friend's Venture, and tried everything that I had suggested with little luck.

However, I think I am making progress. I know that this command should/does work or is another variation of this command:

su
echo 1 > /sys/devices/virtual/usb_composite/diag/enable
To disable diag mode:
echo 0 > /sys/devices/virtual/usb_composite/diag/enable

In the /sys/devices/virtual/usb_composite/ directory, there are several folders, all of which contain an "enable" script:
adb
diag
modem
nmea
rmnet
rndis

I think that using the above command and changing diag out for one of the other folders may be the key. I haven't tried it yet though.

I do also recommend installing BOTH of the downloads discussed at the top of this page. Both programs install their own set of drivers which may prove useful when switching modes.

 

[sunsuke]

I spent sometime last night with my friend's Venture, and tried everything that I had suggested with little luck.

However, I think I am making progress. I know that this command should/does work or is another variation of this command:

su
echo 1 > /sys/devices/virtual/usb_composite/diag/enable
To disable diag mode:
echo 0 > /sys/devices/virtual/usb_composite/diag/enable

In the /sys/devices/virtual/usb_composite/ directory, there are several folders, all of which contain an "enable" script:
adb
diag
modem
nmea
rmnet
rndis

I think that using the above command and changing diag out for one of the other folders may be the key. I haven't tried it yet though.

I do also recommend installing BOTH of the downloads discussed at the top of this page. Both programs install their own set of drivers which may prove useful when switching modes.

Alrighty I am just wondering
I just recently swtiched OS from Windows to Ubuntu
will the drivers work under a virtualbox?
if not I will just get out my dinosuar laptop with XP on it SP3

 

[UPdownLoAD]

Alrighty I am just wondering
I just recently swtiched OS from Windows to Ubuntu
will the drivers work under a virtualbox?
if not I will just get out my dinosuar laptop with XP on it SP3

The short answer is maybe.

It hasn't been figured out how to get the phone in the correct mode to connect it to the PC yet. After that happens, the driver issue will come into play.

 

[sunsuke]

The short answer is maybe.

It hasn't been figured out how to get the phone in the correct mode to connect it to the PC yet. After that happens, the driver issue will come into play.

ok I will try this on my XP laptop so I can get the correct results

 

[sunsuke]

after doing the commands I thought I got nothing
but when I am trying to usb connect to move my screen shot that I took to show you I did it right
I can not usb connect to open my files
Is that normal?
I still have my terminal running ^^;
i remember I always had the terminal running and usb connecting to transfer files but now I can't.
is that a good sign or bad sign?