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
___________________________________________________________________
Used same method on forums for downgrade purpose. (Buzz downgrader)
But when i click on step 1.bat,it says-
cannot stat 'dmisc.img' : no such file or directory
cannot stat 'flash_image' :no such file or directory
cannot stat 'psneuter' : no such file or directory
unable to chmod /data/local/psneuter:no such file or directory
***getting temproot***
error opening /data/loca/dmisc.img:no such file or directory
***step 1 is done,continue with step two***
I have ADB installed correctly and have downgraded my device 1 time with success.,but now it gives me this.
I have HTC Wildfire(Non rooted)
S-ON
hboot-1.01.0002
android 2.2.1
Thanks,desperately need help!
___________________________________________________________________
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Please help anyone????!!!!!
Well I am getting a message similar to the one in the title. I just got this galaxy tab p5113 model a couple days ago and decided to go ahead and get root access as well as flash cwm recovery. Everything went well.....gained root access...bbooting into cwm recovery with no problems..
I went and rebooted the phone after all operationswere complete and I found the boot logo to be missing, and in it's place is green text that says "espresso10.jpg draw failed" .....
Now I have searched and not found a comprehensive answer or very many threads containing much useful information.
In an attempt to fix the problem I subsequently downloaded the stock p5113 firmware and flashed via Odin.....still showing the error message on boot.
This one has really stumped me!
What files could possibly have been corrupted and why wouldn't the flashing of the stock firmware fix and repair the problem.....I would assume that it would have replaced the missing files....
ssCISengineer said:
Well I am getting a message similar to the one in the title. I just got this galaxy tab p5113 model a couple days ago and decided to go ahead and get root access as well as flash cwm recovery. Everything went well.....gained root access...bbooting into cwm recovery with no problems..
I went and rebooted the phone after all operationswere complete and I found the boot logo to be missing, and in it's place is green text that says "espresso10.jpg draw failed" .....
Now I have searched and not found a comprehensive answer or very many threads containing much useful information.
In an attempt to fix the problem I subsequently downloaded the stock p5113 firmware and flashed via Odin.....still showing the error message on boot.
This one has really stumped me!
What files could possibly have been corrupted and why wouldn't the flashing of the stock firmware fix and repair the problem.....I would assume that it would have replaced the missing files....
Click to expand...
Click to collapse
First, did you factory reset then flash the file through Odin? Does the tablet boot up?
p3113owner said:
First, did you factory reset then flash the file through Odin? Does the tablet boot up?
Click to expand...
Click to collapse
Yes sir the tablet boots, and I did reset and flash in Odin.
please remember to thank me for e-peen points!
Sent from a Galaxy Nexus between here and there.
ssCISengineer said:
Yes sir the tablet boots, and I did reset and flash in Odin.
please remember to thank me for e-peen points!
Sent from a Galaxy Nexus between here and there.
Click to expand...
Click to collapse
My suggestion is to reset and flash in Odin again. Try downloading the stock ROM file again as the one you have may be corrupted.
I'm having the same issues as the OP. Sorry to resurrect an old thread but I've been searching everywhere and I can't find a fix for this. I've attempted everything stated above and still no fix. I've heard that flashing the stock param.lfs would fix this issue however I can't find the stock param.lfs anywhere. If anyone happens to have it, I'd appreciate it if they could share it out.
Code:
# ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name/ | grep PARAM
lrwxrwxrwx root root 2012-09-20 15:50 PARAM -> /dev/block/mmcblk0p4
# cat /dev/block/mmcblk0p4 > /sdcard/mmcblk0p4.raw
# strings /sdcard/mmcblk0p4.raw | grep espresso
logo_espresso7.jpg
logo_espresso7.jpg
logo_espresso10.jpg
logo_espresso10.jpg
logo_espresso10.jpg
ketut.kumajaya said:
Code:
# ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name/ | grep PARAM
lrwxrwxrwx root root 2012-09-20 15:50 PARAM -> /dev/block/mmcblk0p4
# cat /dev/block/mmcblk0p4 > /sdcard/mmcblk0p4.raw
# strings /sdcard/mmcblk0p4.raw | grep espresso
logo_espresso7.jpg
logo_espresso7.jpg
logo_espresso10.jpg
logo_espresso10.jpg
logo_espresso10.jpg
Click to expand...
Click to collapse
I'm sorry man, I'm not great at this. What should I do with this? Actually, what I should say is what should I do with the mmcblk0p4.raw file? Is this my param.lfs?
detninrod said:
I'm sorry man, I'm not great at this. What should I do with this? Actually, what I should say is what should I do with the mmcblk0p4.raw file? Is this my param.lfs?
Click to expand...
Click to collapse
1. The first command to know which the PARAM block device
2. The second to dump the param block device to a file
3. The third, I show you I found the logo file inside /dev/block/mmcblk0p4, my device P3100
The "#" prefix mean I run a command as root.
Open Terminal Emulator or over "adb shell", and then type "su" (without quote). Issue all my above command, write the result here. Compress your param dump file and upload it here. Probably a recovery override your param partition.
ketut.kumajaya said:
1. The first command to know which the PARAM block device
2. The second to dump the param block device to a file
3. The third, I show you I found the logo file inside /dev/block/mmcblk0p4, my device P3100
The "#" prefix mean I run a command as root.
Open Terminal Emulator or over "adb shell", and then type "su" (without quote). Issue all my above command, write the result here. Compress your param dump file and upload it here. Probably a recovery override your param partition.
Click to expand...
Click to collapse
Code:
[email protected]:/ # ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name/ | grep PARAM
lrwxrwxrwx root root 2012-09-20 12:12 PARAM -> /dev/block/mmcblk0p4
This is what I get after running the first command. I then dumped the param block device to file and then ran the check on it.
Code:
[email protected]:/ # strings /sdcard/mmcblk0p4.raw | grep espresso
# strings /sdcard/mmcblk0p4.raw | grep espresso
logo_espresso7.jpg
logo_espresso7.jpg
logo_espresso10.jpg
logo_espresso10.jpg
logo_espresso10.jpg
I'll attach the resulted file in just a moment. Thank you.
detninrod said:
Code:
[email protected]:/ # ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name/ | grep PARAM
lrwxrwxrwx root root 2012-09-20 12:12 PARAM -> /dev/block/mmcblk0p4
This is what I get after running the first command. I then dumped the param block device to file and then ran the check on it.
Code:
[email protected]:/ # strings /sdcard/mmcblk0p4.raw | grep espresso
# strings /sdcard/mmcblk0p4.raw | grep espresso
logo_espresso7.jpg
logo_espresso7.jpg
logo_espresso10.jpg
logo_espresso10.jpg
logo_espresso10.jpg
I'll attach the resulted file in just a moment. Thank you.
Click to expand...
Click to collapse
Here is the resulted file. Thanks again.
I also misread OP's original post stating they have a P-3113. Mine is a P-5113 however I have done the exact same steps as he did.
detninrod said:
Here is the resulted file. Thanks again.
Click to expand...
Click to collapse
Are you sure zipped the correct dump file? What I have got is empty mmcblk0p4.raw prefixed by your command!
ketut.kumajaya said:
Are you sure zipped the correct dump file? What I have got is empty mmcblk0p4.raw prefixed by your command!
Click to expand...
Click to collapse
I did something dumb and I'm not going to admit to it.. but I did end up fixing the problem. I found a .tar.md5 that can be flashed with Odin for the P-3110. I put it on my ExtSDcard and flashed my param partition using it and it fixed my issue. I got the .tar.md5 from here. I just flashed my param partition, I didn't use it to flash anything else. I really wouldn't recommend it to anyone that doesn't have a P3110, but I just ended up getting lucky. Thanks for your help ketut.kumajaya, I do appreciate your assistance with this.
detninrod said:
I did something dumb and I'm not going to admit to it.. but I did end up fixing the problem. I found a .tar.md5 that can be flashed with Odin for the P-3110. I put it on my ExtSDcard and flashed my param partition using it and it fixed my issue. I got the .tar.md5 from here. I just flashed my param partition, I didn't use it to flash anything else. I really wouldn't recommend it to anyone that doesn't have a P3110, but I just ended up getting lucky. Thanks for your help ketut.kumajaya, I do appreciate your assistance with this.
Click to expand...
Click to collapse
The file name param.lfs? Mind to share here? 637MB is too big for 8MB data
ketut.kumajaya said:
The file name param.lfs? Mind to share here? 637MB is too big for 8MB data
Click to expand...
Click to collapse
lol it's not actually mine but I'm sure it should be fine (I found a tutorial somewhere out on the interwebs). It isn't just the param.lfs, it's the FULL flash for the P-3113. I used Mobile Odin, chose the param partition, chose this image, and flashed it. It will only pull the param.lfs from the image if you only choose the param partition.
I would have used the P-5113 image to reflash my param partition, but it doesn't included it for some reason
Here's the actual param.lfs. I guess it would be a bit easier to manage then copying the full image over to an SD card.
detninrod said:
Here's the actual param.lfs. I guess it would be a bit easier to manage then copying the full image over to an SD card.
Click to expand...
Click to collapse
Just flashed this on my 3110, fixed the logo, nice one, cheers
GiggedyGoo said:
Just flashed this on my 3110, fixed the logo, nice one, cheers
Click to expand...
Click to collapse
Nice! Glad to hear it!
detninrod said:
I'm having the same issues as the OP. Sorry to resurrect an old thread but I've been searching everywhere and I can't find a fix for this. I've attempted everything stated above and still no fix. I've heard that flashing the stock param.lfs would fix this issue however I can't find the stock param.lfs anywhere. If anyone happens to have it, I'd appreciate it if they could share it out.
Click to expand...
Click to collapse
The param.lfs word guided me to the right direction: http://forum.xda-developers.com/showthread.php?t=1898377
Thank you !!!
detninrod said:
Here's the actual param.lfs. I guess it would be a bit easier to manage then copying the full image over to an SD card.
Click to expand...
Click to collapse
Just flashed my GT-P5100 and everything got fixed
Device have now right bootlogo and right charge logos without any jpg drawing errors, also my P5100 now also boots right in android instead first boot going to cwm.
I used mobile odin and used that param.lfs and now everything is normal :good:
THANK YOU !
hello everyone , i m done searching for 1 to 2 weeks for x-factor exploit which will works for Rogers Htc One Xl firmware 3.18 , where ever i search , i found it for AT&T firmware 2.2 , so plear help me because i need to get supercid 11111111 so that i can make my device s-off by the help of this forum http://forum.xda-developers.com/showthread.php?t=2155071
thanx in advance for ur time and help !!!
Thank the heavens! You've finally made your own thread instead of posting in old, unrelated ones!
From the PMs you sent, you are already rooted. So no need for an exploit.
EDIT: You need to use the hex edit method.
http://forum.xda-developers.com/showthread.php?t=1671396
If the hex edit method didn't work for you (as you mentioned in another post or PM), you probably made a mistake. You know you need to look for your carrier's CID, and not CWS_001 (which is AT&T's CID)?
You can use the hex edit method to get SuperCID:
http://forum.xda-developers.com/showthread.php?t=2212737
Sent from my Evita
screen display: [email protected]:/ # ........................
timmaaa said:
You can use the hex edit method to get SuperCID:
http://forum.xda-developers.com/showthread.php?t=2212737
Sent from my Evita
Click to expand...
Click to collapse
When i open cmd, and type first line:
adb shell
the screen display: [email protected]:/ # ........................
So what i need to type in this .........................????????????
screen display: [email protected]:/ # ........................
redpoint73 said:
Thank the heavens! You've finally made your own thread instead of posting in old, unrelated ones!
From the PMs you sent, you are already rooted. So no need for an exploit.
EDIT: You need to use the hex edit method.
http://forum.xda-developers.com/showthread.php?t=1671396
If the hex edit method didn't work for you (as you mentioned in another post or PM), you probably made a mistake. You know you need to look for your carrier's CID, and not CWS_001 (which is AT&T's CID)?
Click to expand...
Click to collapse
When i open cmd, and type first line:
adb shell
the screen display: [email protected]:/ # ........................
So what i need to type in this .........................????????????
sahi.saab.1 said:
When i open cmd, and type first line:
adb shell
the screen display: [email protected]:/ # ........................
So what i need to type in this .........................????????????
Click to expand...
Click to collapse
Not sure. I've never actually done the hex edit method myself, just pointed you towards it.
What happens whey you try to type the next commands in the instructions?
No matter what I type , it keeps asking :
the screen display: [email protected]:/ # ......................
I. Need to type something in that space but I don't 9 what to type !
Sent from my HTC One X using XDA Premium 4 mobile app
Have you tried giving the next command (su)?
Sent from my Evita
Yes , I do , I try to give next command but screen keep displaying: [email protected]:/ # ......................
Sent from my HTC One X using XDA Premium 4 mobile app
I haven't used this method so I'm not sure what kind of return you should receive after giving those commands.
Sent from my Evita
any1 who can help ?
any1 who try this method http://forum.xda-developers.com/showthread.php?t=2212737 and can help me with my problem ?
When i open cmd, and type first line:
adb shell
the screen display: [email protected]:/ # ........................
So what i need to type in this .........................????????????
Hi,it all started after i flashed TWRP in my HTC sensation xe(i had 4EXT recovery),then i wanted to flash a new rom but something happened and my htc freezed and then i pulled out the battery and inserted it,i turned it On but then it couldn't mount the system,cache,data.One of my friends managed to flash again the 4EXT recovery and told me that my partitions are corrupted.I tried some metjods with adb but nothing happened,
</tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37> but it says <no such file or directory>
and also tried this <parted /dev/block/mmcblk0 mkfs ext2> but it says <can't have overlapping partitions>
It appears like your Partition table is corrupted and needs to be rebuilt. Please try flashing the Stock Firmware.
This thread seems like a good Start. [Finally Here!] HTC Unbricking Project
You may also be interested in ☺ A great starting point for all new Sensation owners
Kindly post your issue in Sensation Q&A, Help & Troubleshooting so that experts specific to your phone may be able to help.