Hello everyone,
I'm attempting to unlock a Samsung Galaxy 550 (AKA Samsung Galaxy I550M) on the Bell Mobility network.
I have located a thread here on XDA at the following URL - http://forum.xda-developers.com/showpost.php?p=12099386&postcount=6
The instructions below are posted within the thread and claimed to be a safe and current method for unlocking this particular model. (2011 tested and working)
Im looking to gain some clarification from veterans here on the boards who can enlighten on whether this quoted procedure will be a success when it comes to a Bell Mobility Galaxy 550. And exactly how to go about implementing this unlock successfully. Is it advisable? Is it safe? A foolproof method?
Im hoping to gain further insight into this procedure. Any details, suggestions, feedback, advice, or clarification is greatly appreciated in order to forgo the risk of bricking the device upon an unsuccessful attempt.
Thanks everyone.
"Since I can't give up on this one I digged a little further into my i5500 memory.
EDIT: SAFE METHOD Did it again on april 8 2011, it works! Stick to the commands.
Guess what? I f.ckin did it. Big hoora. I'am good I know Thank you!
Code:
- root your phone
- adb shell
- su
- cd /
- mount -o remount,rw / (or do it before adb with root explorer)
This works on other systems: mount -o remount,rw -t rootfs rootfs /
- mkdir /efs
- mount -o nosuid,ro,nodev -t vfat /dev/block/stl5 /efs
- cat /efs/mits/perso.txt
- umount /efs
- reboot
EDIT: stl5 is es-tee-el-five (like STL5)
EDIT: /efs on the Galaxy the /etc/fstab says: mount rfs /dev/block/stl5 /efs nosuid nodev check=no
You will see some numbers: In my case 20404 for Vodafone NL.
Then you will see your SP unlock code followed by some 000000000 codes and another
code. Write the first one (and second just in case) down.
Shut down the phone and put it a "locked" sim. Start your phone, input the pin, and when asked for a unlock code give it the first code. Your phone is now unlocked."
mods may feel free to delete thread as phone has been unlocked successfully
Related
hello, I have an Archos5 unit with the firmware version 1.7.99 android 1.6 on it. i have managed to root the device but I cant figure out how to remount /system read write on the device.
I checked my root ID and its 0.
i have tried mounting with this command : mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
I get an invalid argument if i try mounting from block.
its the same if i try mounting mtdblock5 where cat /proc/mtd5 shows system being located/
i also tried mounting mtd directly but it spits out an error saying block device required.
i would try through android ADB if i could get it working on linux. the windows archos version wont let me remount (vista).
ignoore this thread. i have succeded in doing what i wanted and now have debian apt working in my archos5. since its quite hard to do I will post a how to in another thread.
Hi;
I'm looking for a safe way to root my new A5, firmware 2.0.38, Android 1.6
I want to use Wifi Helper but it requires rooting. I've yet to find how to do this on this machine. Can you help me?
I was never successful using SuperOneClick for the Optimus V. hangs at wating for device.
THOUGH...
I believe I did finally get it rooted using adb and push psneuter, busybox, su and Superuser.apk...via Ubuntu 10.10 Maverick...
I rebooted the device twice...downloaded terminal from the market and sure enough I can su to a # prompt...I take this to confirm I have successfully rooted my Optimus V.
Now to the question....
I found several post most of which included this command in adb shell:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
However I was successful based on a post found here by (Endur):
http://forum.xda-developers.com/showthread.php?p=12076877
with the command
mount -o rw,remount /dev/block/stl9 /system
What is the difference? Have I done something horribly wrong?
And Thank you for all your work here...This is a lot of fun prying into the technologies of today and tomorrow.
Any answer or pointing me in the direction to research on my own would be much appreciated.
Jim
Hi, I cannot figure out what I need to write in terminal emulator to gain root access to install cwm. I was hoping someone could post the exact command needed, I would appreciate it alot. I have tried searching but the generic commands i found on a different site didnt work. Thanks!
Can you gain root from terminal emulator? First I have heard this. Why not just Odin one of the modded kernels?
Sent from my HTC Sensation Z710e using xda premium
andale927 said:
Hi, I cannot figure out what I need to write in terminal emulator to gain root access to install cwm. I was hoping someone could post the exact command needed, I would appreciate it alot. I have tried searching but the generic commands i found on a different site didnt work. Thanks!
Click to expand...
Click to collapse
If you're just looking for the command to mount /system as read/write, you'll have to figure out what "device" is used for the mount. From the terminal, type:
mount
That will show you a list of things that are currently mounted. You'll see something like (not exactly):
/dev/block/stl9 /system rfs rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime, uid=1000,gid=1015,fmask=0002,dm
ask=0002,allow_utime=0020,codepage=cp437,iocharset =iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
The part you're interested in is the part before "/system" and that is the block device used to mount your system partition. To mount it read/write, you type (based on this example's block device & based on the rfs vs. ext4 file system):
mount -o rw,remount -t rfs /dev/block/stl9 /system
The -o part tells mount "here come the options" which are read/write & remount. The -t tells it the filesystem type (rfs or ext4, depends on if you have voodoo enabled). The next argument tells it the block device, then what mount point to use.
As for root, what Exodian said. You'll either have to flash a root enabled kernel or use SuperOneClick v2.2.
Hi, this is a blatant crosspost from the android stackexchange site, questions/24081... I posted it there and figured I wouldn't get much help, so I thought I'd try here. Let me know if this is OT or in the wrong place or whatever.
I want to remount a read-only partition in read-write mode, but I want it to be writable for all users.
So far I've got this:
Code:
mount -o bind /someplace /someplace_else
mount -o remount rw /someplace_else
The first command creates a new mount point from a directory. The second one remounts the new mount point as rewritable. This all works.
Problem is, the new mount point has uid=1000,fmask=0222,dmask=0222, so the non-root user still can't write anything, and root can't give it permission.
How do I change the fmask and uid when remounting, or is there something else I can do to make the mount writable for the normal user?
Also, note that the command that worked for me is this:
Code:
mount -o remount rw /someplace_else
...with no comma between "remount" and "rw," as I've seen in almost everything my searches turned up. Does anyone know anything about this discrepancy in syntax?
I'm doing most of this in a terminal emulator on the phone, and in SL4A.
I have TF700T which I have successfully unlocked and run a newer android on it.
Now the daugther also wants her tablet updated. Now all the problems comes......
As many others I have been struggling with ASUS Support because it just reports some error and won't unlock the tablet. After a very long thread where ASUS claimed that they have done something (which obvoiusly didn't help), I just found this:
http://forum.xda-developers.com/showthread.php?t=2549709
It turns out that my daughter tablet hasn't any serial set as described. So I guess that is my last hope.....
The question is: The article tells to manually mount /dev/block/mmcblk0p5. CAn someone help me with some instructions her?
I first want to mount it on my tablet just to inspect how it should look like, and then afterwards on the daugthers tablet to correct the problem and hopefully be able to unlock.
My tablet is rooted, the daugthers tablet isn't (since it is running ASUS Stock ROM)
Can anybody help me with this?
Best Regards
Martin
Mr.Eskildsen said:
The question is: The article tells to manually mount /dev/block/mmcblk0p5. CAn someone help me with some instructions her?
I first want to mount it on my tablet just to inspect how it should look like, and then afterwards on the daugthers tablet to correct the problem and hopefully be able to unlock.
My tablet is rooted, the daugthers tablet isn't (since it is running ASUS Stock ROM)
Click to expand...
Click to collapse
Run this in a root shell (via adb shell from a PC or in a terminal emulator on the device):
Code:
cd /sdcard
mkdir PER
mount -o ro -t vfat /dev/block/mmcblk0p5 PER
Now you can inspect the contents in the PER subdirectory. You should have files named ISN, SSN and UUID (and subdirs for lightsensor and sensors), where SSN contains your serial number and UUID contains the same serial number as returned by "getprop ro.boot.serialno". I don't know what ISN is.
When you're done, run
Code:
umount /sdcard/PER
rmdir /sdcard/PER
to clean up.
Thanks a lot for the quick answer. Worked after i did root the daughters tablet
I actually found out what I suspected was the problem. That is on my tablet, all the mentioned files is there, but on the daugthers tablet, especially SSN and also the subdirs is missing.
I guess I need the SSN file to be there?
I try to mount it as read/write:
Code:
mount -o rw -t vfat /dev/block/mmcblk0p5 PER
But I just get an error telling me that device is already busy
Code:
mount: Device or resource busy
How can I correct this problem?
BTW. Impressed of the fast response
/Martin
Mr.Eskildsen said:
I guess I need the SSN file to be there?
Click to expand...
Click to collapse
I guess you're right.
Mr.Eskildsen said:
I try to mount it as read/write:
Code:
mount -o rw -t vfat /dev/block/mmcblk0p5 PER
Click to expand...
Click to collapse
If you mounted it ro before, you need to either reboot or unmount before trying to mount rw, or just change the mount option to "-o rw,remount".
Thanks for your fast reply - I am impressed!
Well now the tablet seems to have a serial, but still unlock fails. I hav had a very long struggle with asus and I really don't know what to do.
I can see from other posts that this problem seems to be quite usual. Any suggestions? Any magic tricks? Or should I just forget about it?