• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Retrieving your MSL (ENABLE WIN 7 HIDDEN ADMIN)

Thanks alot WhisperPntr and BliND123!! I got my msl and am now rooted! The steps are pretty easy until you only get F's and 0's but thats when i used BliND's guide using the takeownership program and worked!! Cant wait for a recovery an rom :D
 
i tried calling virgin mobile and saying i need the msl code to develope a game and they said they couldent give it out i hav ealso tried the hex and the offset stops at 03 not 07 i need help
 
slutyman said:
i tried calling virgin mobile and saying i need the msl code to develope a game and they said they couldent give it out i hav ealso tried the hex and the offset stops at 03 not 07 i need help
Click to expand...
They are on to this tactic.

You need to tell them something they cannot refuse... Error 67.
 
OK, I am going to release some sad news... I no longer own the Optimus Elite, I passed over to the HTC One V for the ICE CREAM! :) Anyways, If you can not find your MSL because your file is corrupt of for any other reason Please send me a PM with the link to your ebi0_cs0.bin and I will see something. I think I might have a way to get around it.. maybe not :P IDK! if it works AGAIN, because I think it did work for slutyman then I will let you all know :P
 
This worked for me. I wanted to do it the hard way cause I have a lot of time on my hands. the trick for me was not letting the phone shut all the way down when it reboots after you enter the 6 0s twice. (entering download mode immediately by holding down volume buttons) I was getting corrupted files before that. I also had to check more than one offset in the bin file and found my msl in about 5 places.

00150f50(has capital U in front of it)
001511f0(again capital U in front of it)
063da370 - 063da80 (split between two lines)
07496a90
0fbfe5d0 - 0fbfe5e0 (split between two lines)




I am using Vista home premium 64bit.
 
It should be noted, if it hasn't been noted already, that in order to get a good .bin and your MSL, you must first have your phone activated. Add that to the prerequisites.
I just noticed this after trying to root my replacement prior to actually activating the service on it. Did not get a good .bin after multiple saves until I activated, now it's perfect.
 
Artine said:
It should be noted, if it hasn't been noted already, that in order to get a good .bin and your MSL, you must first have your phone activated. Add that to the prerequisites.
I just noticed this after trying to root my replacement prior to actually activating the service on it. Did not get a good .bin after multiple saves until I activated, now it's perfect.
Click to expand...

ok I'll try that, I just got my replacement to
 
jmfolcik said:
Everyone whose had problems, try that holding down the volume rocker from the moment you type in the wrong MSL's until it gets into the download mode. I just had my replacement phone arrive today cuz my other one rebooted randomly on me at work and I got good files using this method. So not sure if its just the new phone happens to work with pulling the memory off it or if it was this difference in procedure.
Click to expand...

Just wanted to say that this method worked for me, first try, after dozens of corrupted files. Maybe we should add it to the instructions?

Thanks to everyone for their excellent work.
 
Has anyone else noticed their google account passwords written in plain text in their dump bin files? Shouldn't they be encrypted or something?
 
Does it really matter that much? If you aren't constantly taking rom dumps and uploading them I don't think that's considered a problem really.
 
This is ram. If there is 1 single place that a password would need to be in plain-text, it would have to be in ram. Any time you decrypt, decypher, or decode something using a computer, the very first place the decrypted data appears is in ram.
 
This wouldn't do anything to fix a boot loop. What did you do to cause the boot loop?

Besides; This is irrelevant. You could install giantpunes kernel, boot the phone, and use a root explorer and idr where but there's a txt file containing your MSL somewhere.
 
WhisperPntr said:
Ya know what? I've been rather patient about this but I am going to speak my mind

@giant, Nice that the ownership suggestion was ignored and you did something that I've TOLD you ad nauseum to do. ##DATA#.

You should know that in windows xp, since you're still using that rather antiquated OS, that there are no issues with administrative rights. But instead drivers will and often are left behind in the development dust.

Call me a wee bit sensitive or what not, but I feel you've consistently taken a big crap on my efforts thus far, in PM and beyond. Dismissing what I tell you to do and adding other suggestions as though my methods are not good enough for you.

I'm glad you got it working and yes per your PM feel free to post your program as it is obvious you feel it is superior. Never mind the fact that the surrounding text data such as the drlmac and Data text are signs and patterns that leads you to the CORRECT MSL rather than some arbitrary 6 digit number that a program cannot root and find out.

I spent 14 hours on this nonstop for the past 4 days and have teamviewed more than my fair share I'm going to stop. If any of you think you're more technical, if you think you have a great idea to find out an MSL from a phone released less than 2 months ago, do it and don't bitch about it. Don't ask for my help then insinuate my methods are behind, roundabout and what not.

Also I'm going to be a bitch and say that if you don't follow and read my instructions then DISCOVER That you find the MSL thorugh OMG reading my instructions, I'm going to go BS. ##DATA# And enter in as many commands as you can I ALREADY suggested and you blew it OFF. So I trusted you and didn't make a second suggestion even though it could have helped MANY on here.

And that's what pisses me off. One person ruining it for many.

Yes this method is fickle, behind and what not, and ALL that you've so nicely implied. But you know what? It works if you follow it and know how to troubleshoot.

I have NO ego in regards to how I found it so very quickly, and I also trust every single person NOT to have an ego and to have tried their best and read through my methods diligently BEFORE asking for my help.

So YOU want to improve it? DO it and make it easy? BE MY GUEST. But don't ask for MY help, and if you want to do it RIGHT then you should troubleshoot EVERY single person with every single issue without making the other person wrong even though you know very likely they didn't FOLLOW a step.

From what your Private Messages showed I don't think you're capable of that, unless this extreme doubt is only directed at me.

But maybe I'm wrong.

So I'm going to take a break and giant can lead this MSL development since I get Private Messages insinuating I don't know shit.

Perhaps he's right. ANd in that case the torch goes to him.

Enjoy.
Click to expand...

i THANK YOU VERY MUCH FOR YOUR EFFORT IN THIS AND I HOPE IN THE FUTURE YOU KEEP COMING BACK!!!!
 
giantpune said:
holyshit! i got it :D

I took a hint from blind123's instructions. Since I'm using xp, I ignored all that stuff about taking ownership. Here's what I made sure to do differently this time:

1 - plug the phone into the PC and turn it on normally.
2 - dial the ##DATA#, click the first item in the list and select "edit". When it asks for the code, I gave it 000000 twice and it said it was going to reboot. I immediately pressed and held both volume buttons and waited for the phone to enter download mode
3 - I started up the memory dump program just as I had done 100 times already and made a dump and it actually worked this time.
Click to expand...

Thnks for your help! I got it to work with you and WhisperPntr's help
 
So I had gotten one of these a while back when Radio Shack was selling them for < $50 with a $10 off coupon.

Finally got it out of the package today and decided to test it out. Attempted to read the MSL/SPC w/ QPST Memory Debug App and file was full of FF's, deduced it was corrupted after reading other posts on this thread. Without the phone activated, I followed the trick to enter SPC wrong twice and hold Vol Down + Vol Up to boot back into download mode. That time, I got a file that was not corrupted, but it did not contain the SPC. Finally, I saw the post mentioning it needed to be activated. Did that, but did not submit any payment to VM yet. Once activated, tried the SPC trick as above, and did a second memory dump. Looking at the second dump, I found the MSL at location 074B8270. I looked for 50n
 
hi I think it worked but am not sure what happens after you enter your suspected msl does it go to a screen that says Diag disabled & give you the option to enable it? I hope so because I enabled it,if I got it right what next to root? Thanks
 
You must log in or register to reply here.
Back
Top Bottom