How to get profile information from Kyocera Brio

Hi,

I just received my feature phone and activated it. I want to use my EVO 3D 4G that I purchased myself, But the problem is how do I get the profile settings from the Brio ? Nobody has mentioned about it. Can someone please provide me some help. BTW, I have spent quite some time on EVO side and I think I know how to get things done on that side. I will offer my help on that side and FYI, you do not need to pay for cdma-workshop, everything can be done for free.

Thanks for your help,

 

Moderator's Note: Please read this entire thread before making any decisions based on the information provided. Yes it's a long thread, but there is lots of healthy debate about what can, could and does work with this device as donor. 

6

Comments

173 comments
  • I have set everything except shared secret passwords which apparently is protected. Any help to get them would be much appreciated.

    0
    Comment actions Permalink
  • It looks like you might be the first to try and do this with the Brio. Good luck!

    0
    Comment actions Permalink
  • Please keep us updated on your progress with the Kyocera Brio, as the Sanyo Vero is permanently out of stock, and no one has provided information about the upcoming Samsung M370 that will replace it.  I have a Nexus S on the way and need to order a Ting donor phone, but I am waiting to see which one will provide the best option.  My contract ends in two days and I would like to migrate to Ting ASAP.

    0
    Comment actions Permalink
  • Looks like I am stuck, I cannot get it to working. My phone works flawlessly but absolutely no data service. DFS shows those AAA shared Secret and HA Shared secret values to be blank. I have made all values from the donor identical to the receiver -- but no lucks.

    I need someone more knowledgeable on this to help me out. I have turned all stones I could but no luck so far. I will wait and see if anyone else can come up with some ideas.

    BTW, anyone knows who assigns those secrets ? Is it Ting or Spring ? I was wondering who would have first hand access to them ? Is the password unique per device/ per phone model or per service provider. Can someone PM me their passwords [has working ting data service] so that I can give it a try ?

    I wish I knew little more on these stuffs.

    Thanks much.

     

    0
    Comment actions Permalink
  • Nirapada - did you unlock the Brio with the MSL code from Ting?

     

    I used the Sanyo Vero as a donor phone, voice and text work but I can't figure out data either, even though I have the AAA and HA passwords...

    0
    Comment actions Permalink
  • Joseph, I did unlock it. I have everything set to exactly the same setting -- except those passwords which Brio doesn't show nor allow to read. For your vero phone, I thought it works, did you follow all the instructions for your model ? what is your target phone ?

    0
    Comment actions Permalink
  • My target phone is an HTC Incredible, much like any other HTC Android. The instructions are vague at best - the Evo 3D instructions say the data profiles auto-provisioned themselves ( I doubt that's possible without a data connection in the first place!) and the Nexus S instructions aren't as detailed as I'd like. Maybe after work I'll try DFS to read the two profiles from the Vero and then flash them to my Incredible. I was previously using an old version of CDMA Workshop, but DFS seems way more detailed and totally free.

     

    I wish I could help figure out how to get those passwords from the Brio for you...but if DFS can't read them I don't know what will. Have you tried to read the data in QPST?

    0
    Comment actions Permalink
  • Nirapada,

    The username/password are definitely tied to the serial and phone number of the phone, so using someone else's won't work. Have you tried using QXDM to read out the passwords? sometimes that works better, though the interface is a little clunkier. Essentially you will need to have it connect to your phone port and type the following in the output command box

    SPC <donor msl>

    requestnvitemread ds_mip_ss_user_prof 0

    requestnvitemread ds_mip_ss_user_prof 1

    Joseph I would recommend trying to use QPST to program your incredible - the profile screen is much easier to use there and it works. For some reason I could not get DFS to write my passwords on the Nexus S correctly. Using the "auto-provision" feature on the evo 3d makes sense - it's a sprint phone and it's being provisioned by sprint, but since your phone is NOT a sprint phone, it will definitely need to be manually provisioned. Stick with it though, I'm sure we can get it going!

    0
    Comment actions Permalink
  • Scott, I have tried QXDM, all commands I have tried except these failed. apparently Brio has these items locked somehow so that nobody can read it. Unless someone knows of some diagnostic mode where these locks are not effective.

    BTW, you mention an "auto-provision" option in Evo 3d, how do I enable that ? I want to try that in case that helps, my phone is evo 3d.

     

    Thanks.

    0
    Comment actions Permalink
  • I'm interested in more detail about the auto-privisioning as well. I used my Vero ESN on my HTC Incredible, which is much like the Evo 3D (same diag codes, firmware, etc)... I have voice and texts but can't get the data profiles to connect!

    0
    Comment actions Permalink
  • There should be an "update profile" setting somewhere. Some evo users have said that worked to get data working. So if you have your MEID hacked and your phone number programmed, try that. You can probably find it somewhere like Menu > Settings > About Phone > System Updates

    0
    Comment actions Permalink
  • Nevermind Scott, I just saw you mentioned me in your reply above. I'll try QPST! I'm positive this phone will work, since I had it on Boost Mobile previously. I'll give it a go tonight, and I have a friend who is more experienced in flashing commercially who will be able to assist. I'll post my findings if we figure it out!

    0
    Comment actions Permalink
  • It's not really "auto" provisioning, sorry I should have said it that way. It's an over the air provisioning. I don't think it has a good chance of working, but it's possible.

    0
    Comment actions Permalink
  • Thanks for the info. I will definitely try it. I had issues with QPST finding my phone while DFS was a simple process, but I'll stick with it tonight and make it work :)

     

    I wonder if the autoprovisioning will work, now that I have my MEID already programmed in the phone, with voice/texts working...

    0
    Comment actions Permalink
  • Hi Joseph,

    any lucks or status on this ? just curious. I am out of luck on my Brio so far, kind of given up.

    0
    Comment actions Permalink
  • No, I couldn't find any information about the Brio. I still can't get QPST to see my phone either. I have to bring it to my flasher friend's store to see if he can figure it out.

    0
    Comment actions Permalink
  • Any news about the Brio? Did over the air provisioning work for you Scotti? 

    0
    Comment actions Permalink
  • I called one of those shady phone flashers advertising on Craigslist and asked if he could try flashing a Brio from Ting. He said he wouldn't be able to do data. I was hoping if this guy does it all the time on many phones, he'd be the one to be able to do it is possible.

    0
    Comment actions Permalink
  • Where did you get the USB drivers for the Kyocera Brio?  I tried a bunch, but none worked? Can anyone post a link to the exact USB Drivers needed to connect to Windows 7? (thanks in advance)

    0
    Comment actions Permalink
  • 0
    Comment actions Permalink
  • Thanks Nirapada! Those drivers allowed me to connect to the Phone using Windows 7.

    I used CDMA Workshop and was able to clone the ESN, but also was unable to get the data part working.

    I followed the same steps that I did for cloning a Sanyo Vero to the HTC Evo 3D, but I was unable to clone the 3g/data connection from the Kyocera Brio to another HTC Evo 3D that I bought.  To be specific, I exported the NAM1 and NAM2 settings from the Brio and wrote them into a HTC Evo 3D, but that didnt work.  One thing that I did notice was that when I connected the Kyocera Brio to my computer, there were 2 com ports (based on the info displayed form "DFS Tool"), but I was only able to connect to 1 of them.

    Anyways, thanks for the drivers, and if there's anything you guys can think of to grab the 3g/data settings over, please let me know and Id be glad to also try it out.

    0
    Comment actions Permalink
  • Hi Scott, I think  the problem is: Brio is not allowing any tool to read those keys [HA and AAA] -- which is causing "data" not to work. If you try to read them explicitly with any other tool, you will see --it says "Access denied". If you can somehow get the device in test mode or diagnostic mode, that might allow us to read those. I spent quite some time on it and then gave up, if you can make it work -- it would be wonderful. Best of luck.

    0
    Comment actions Permalink
  • BTW, cdma workshop's trial period has expired, is there a way to restart that ?

    Thanks,

     

    0
    Comment actions Permalink
  • What version were you using Nirapada? Have you tried DFS and QPST? I found them to be infinitely better than CDMA Workshop (but not as user-friendly).

    0
    Comment actions Permalink
  • Oh, and free.

    0
    Comment actions Permalink
  • version 3.8.5.

    I have tried DFS and QPST. BTW, only cdma workshop can get me the MSL for the target phone. None of the others do, which is mainly why I need to be able to run cdma workshop. Thanks.

    0
    Comment actions Permalink
  • I was able to get data to working to some degree on my Evo 4g using the Brio as a donor...

    So far I have been able to find the HA and AAA passwords only for profile 1. Profile 1 seems to get you data, but not 3g data which I assume is where profile 0 comes in. I used the QPST Memory Debug tool and dumped the Brio's memory onto my computer. I then used a hex editor to dig around in the resulting files. In the sdram_dump.lst file, I found the NAI for profile 1 (Do a text search for "mvno102" and you should find it). Just below it there were two 6-character text strings. One was "usxv8v" (yours will be different), the other was the word "secret"... I used QPST Service Programming to a write "secret" as my HA and and "usxv8v" as my AAA to profile 1 on my Evo and after a reboot I had 1x data.

    The AAA passwords for each profile are going to be different, so this is isn't the complete solution, but it's a step in the right direction. From my understanding, we're looking for a 16 character string for the profile 0 AAA.

    0
    Comment actions Permalink
  • Nice job!!! Please do keep us updated on your results! :)

    0
    Comment actions Permalink
  • Nice! "secret" should be the HA password for both profiles, if that helps you search your memory dump.

    0
    Comment actions Permalink
  • Aaron, where is the QPST memory debug tool ?

    Thanks.

    0
    Comment actions Permalink

Please sign in to leave a comment.