Related
Hello all, I just completed an app I'd like to share with you all.
It's called Search2Play, it lets you play and pause your music by pressing a button on your device. On most devices, it is the search key. Currently, the Nexus & MyTouch 3G both use the Search key, whereas the Droid uses the Camera key. If you have physical keys (i.e. Droid, MT3G, G1, etc) then it will work when the phone is locked, but if you have capacitive keys (Nexus, Moment, Eris, Incredible, etc) then the screen must be on (lockscreen works, and fully unlocked of course).
It is available on the market under the name "Search2Play (Root Required)". It's totally free.
It requires root permissions to install. It also requires that you have a version of BusyBox that supports the "cp" command. Only Droid users probably have to worry about the busybox version, as most other custom ROMs have that already. Droid users, I recommend CyanogenMod for Droid or Bugless Beast as I know both of them have the right version.
It does not run in the background or install a service, just makes some changes to a few files on the /system partition.
The UI is very simple, just two buttons and some text explaining the app. Once you hit install, it will ask for permission to use root, you must hit accept or the app won't serve its purpose
The other button, "Restore", lets you remove the mod and go back to stock settings, where the search button brings up search, etc.
Supported Devices:
Nexus
Spica
Hero (GSM & CDMA)
Galaxy S devices (all US variants and probably the i9000 as well. It's not tested)
MyTouch 3G
Droid 1 (I've been told DX & D2 work as well, though I'm not sure how :?)
Evo (must be NAND unlocked or S-OFF)
Desire (must be NAND unlocked or S-OFF)
Free Version on Market:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Or click this from your device: Search2Play Free
See the Market to view a screenshot. Please give me some feedback. Thanks! Hope you enjoy the app :
FOR DEVICE REQUESTS SEE POST #3
Changelog:
1.4.1 thru 2.1:
Add support for Evo, GSM Hero, CDMA Hero, & Samsung Spica (thanks to Aasheet Kumar for the files I needed for Spica support!)
1.4:
Fixed rare root checking bug on some Droid ROMs, and maybe some Nexus ROMs too
1.6+ only now, sorry, it's not like any device this works for isn't updated to at least 1.6
1.3:
Now checks if the SD card is present on launch instead of just crashing if it's not there
Cleaned things up more
Merged some code between the donate & free versions
Better checks to see if it can be installed
1.2.5:
FINALLY stopped it from causing buttons to stop working. Checks for compatibility, and throws an error if it detects it can't run.
1.2:
Droid support!!
More should fix a few FC issues some people have seen. Let me know if you have problems.
1.1.2:
Fixes the not restoring bug
1.1.1:
Failed attempt at fixing the not restoring bug.
1.1:
Support for low res devices.
Now works with MT3G! Since it has a hard search key, it will even work when the phone is locked
Deletes files from SD card once done installing.
Cleaned up more code.
1.0.1:
Sets system back to Read-Only once finished installing
Cleaned up some code, if you have FCs let me know.
1.0:
Base release
If you want to request support for your device here's what I need. Note that your device must be able to be rooted and the system partition must be able to get read/write access from userspace. I.E. any Desire or Evo or any other recent HTC device with a NAND lock will not work, unless it has been NAND unlocked with an S-OFF bootloader, like via Unrevoked.. If your device has all that, get this info and send me an email at [email protected]
Run the command "adb shell mount" and tell me the output. I don't need the whole thing, just the line referring to the system partition. I.E. "/dev/block/mtdblock3 on /system type yaffs2 (ro,relatime)" is the line on the Nexus, it should be similar to that.
Then, run "adb shell getprop" and tell me the 1-4 lines related to the keyboard, like hw.keyboards.*.devname and tell me those lines. I.E the Nexus returns "mahimahi-keypad". Yours should be similar.
Finally, run "adb shell ls /system/usr/keylayout/". It should return a list of files all ending in ".kl"
Remember the keypad name from step 2? Good
There should be a ".kl" file matching that name (like mahimahi-keypad.kl). Pull that file with "adb pull /system/usr/keylayout/keypadname.kl directory" with directory being the folder you want to pull the file to and keypad name being the name from step 2.
Zip that file, and then send it to me please.
That should be it, if you have any questions or problems with this list hit me up on GTalk or email me. [email protected] for both GTalk & email.
Dear geniusdog
I just tried out your app.
I installed it, run it, pressed the install button, allowed root access and rebooted mynexus one. But after that reboot, my sell doesn't react on anypressed buttons anymore. I can only use the touchscreen...
I also tried to restore in your app, but there appeared a window saying that the app is not responding anymore.
How can I manually restore it? Is there a command or some files, I can edit?
Thanks for your help
bayoffire said:
Dear geniusdog
I just tried out your app.
I installed it, run it, pressed the install button, allowed root access and rebooted mynexus one. But after that reboot, my sell doesn't react on anypressed buttons anymore. I can only use the touchscreen...
I also tried to restore in your app, but there appeared a window saying that the app is not responding anymore.
How can I manually restore it? Is there a command or some files, I can edit?
Thanks for your help
Click to expand...
Click to collapse
Sorry for the issue. I have uploaded a new version of both apps that should fix the problem. If you can download the app and install it again, otherwise, PM me & I will give you manual instructions to restore it.
Also, just some technical details, the problem was caused because I had set it to create the directory on the start of the application. After that I removed it once you clicked the button & the install was finished. Because of that, if you clicked restore after install, it would fail to find the directory and then proceed to FC. Sorry for the trouble
Droid Support!!!!
Help!!!!!
I have installed V1.0.4, but my touch keys(back, Menu, Home and Search) don't work.
Then I have tried to restore it, but it's failed.
How could I fix it? Thanks.
My Rom is 2.1-update1 rooted.
hahabear said:
Help!!!!!
I have installed V1.0.4, but my touch keys(back, Menu, Home and Search) don't work.
Then I have tried to restore it, but it's failed.
How could I fix it? Thanks.
My Rom is 2.1-update1 rooted.
Click to expand...
Click to collapse
Hmm I dont have this issue, how does it fail? Does it just freeze, or does it FC, or does it say it finishes then do nothing? Also, what ROM, CM? Enomther? Please let me know so I can work on this.
Also, to fix it, download the attached file, & run the following commands (you must have ADB set up):
adb remount
adb shell rm /system/usr/keylayout/mahimahi-keypad.kl
adb push *path to downloaded file* /system/usr/keylayout/mahimahi-keypad.kl
Or you can just reflash your ROM, either way you'll get the same thing.
My phone is Nexus one.
My rom is Official v2.1-updated1.
When I execute the command as your indication.
"adb shell rm /system/usr/keylayout/mahimahi-keypad.kl"
rm failed for /system/usr/keylayout/mahimahi-keypad.kl, No such file or directory
What's wrong? And thank you for your quick reply.
hahabear said:
My phone is Nexus one.
My rom is Official v2.1-updated1.
When I execute the command as your indication.
"adb shell rm /system/usr/keylayout/mahimahi-keypad.kl"
rm failed for /system/usr/keylayout/mahimahi-keypad.kl, No such file or directory
What's wrong? And thank you for your quick reply.
Click to expand...
Click to collapse
Ok excellent that answers the second part of my question its failing to copy the file back over after deleting the original on certain ROMs.
You can just skip that step and go on to the "adb push" step. Also, can you run the command "adb shell cp" and tell me the output?
bingo! Thanks for your help. It's resolved.
On the other hand, I could get the mod.kl from SD Card, push again, Search2play will work, is that right?
hahabear said:
bingo! Thanks for your help. It's resolved.
On the other hand, I could get the mod.kl from SD Card, push again, Search2play will work, is that right?
Click to expand...
Click to collapse
Yes, but can you tell me what it says if you run the command "adb shell cp"
That will tell me if the issue is with the version of BusyBox on some ROMs.
Geniusdog254 said:
Yes, but can you tell me what it says if you run the command "adb shell cp"
That will tell me if the issue is with the version of BusyBox on some ROMs.
Click to expand...
Click to collapse
C:\N1root>adb shell cp
cp: not found
My god!!! It means there is not cp command in my phone?
hahabear said:
C:\N1root>adb shell cp
cp: not found
My god!!! It means there is not cp command in my phone?
Click to expand...
Click to collapse
Yeah exactly lol. Not sure if that was sarcasm or what, but thats what is causing the FC's and the failures some people are getting. And theres not a damn thing I can do about it.
I would recommend installing the CyanogenMod ROM, since it is fast, adds extra features, and supports cp Then the app will work just fine
Anyway. Thanks for your help. You are so kind. I will try new ROM later. And I will support your work. cu.
hahabear said:
Anyway. Thanks for your help. You are so kind. I will try new ROM later. And I will support your work. cu.
Click to expand...
Click to collapse
Thanks you very much for your support. Glad I could help you, if you have any other problems please email me, email listed in the market
Donate version now just to support me, added support for all devices to free version.
Please donate!
1.3 version uploaded
See changelog.
Any updates on newer phones?
KaliKot said:
Any updates on newer phones?
Click to expand...
Click to collapse
I can make it work for any phone without a NAND lock. Any requests?
I need to do the Galaxy S series, but the only one I can test is the Epic and I'm not sure if the others have different mount tables or not. Desire still has NAND lock so I can't do it. Not sure about Droid2/X. Just email/Twitter/PM me or post here with a request. I'll get back to you.
Use my new RegawMOD Hero Rooter HERE
If you do not see the Superuser Permissions app in the app tray after running the exploit, on your phone, go to
Settings > About Phone > Software information
If it says 2.27.651.6 under "Build Number" (notice the bolded, underlined, italic 6), you need to run the RUU in the second post of this thread to revert to .5 first. Doing this WILL erase all of your data on your phone, so be sure to back up anything if you need to first.
It's been a long search for root, but it has finally been achieved!
The Hero 2.1 exploit is based on the EVO rooting method.
The EVO rooting could not have been possible without the combined efforts of:
Matt Mastracci
ozzeh
Joshua Wise
They are all AMAZING and should be thanked for all they have done.
Thank you to Amon_RA for the recovery.img (1.5.2) and Jus10o for packing up a boot.img for me last night when I needed it quick.
Over the past week, Matt and I worked hard applying this exploit to gain permanent root on the Hero.
I now have permanent root access on 2.1 down to a few simple steps that are detailed in this guide.
Also, I'd like to thank everyone that worked really hard on trying to find root here in the Hero community, and specifically all of those who contacted me and worked together with me trying to gain root:
abcdfv
imleon
thatguythatdid
navalynt
nfinitefx45
lifetrip718
rejectedkid
nebenezer (for being cool)
These guys worked incredibly hard with me and had extremely innovative ideas. They deserve a ton of credit for sticking with it as well trying to find . They were all in this for all the Hero users.
If I forgot your name, please let me know via pm so I can add you to the list.
As of right now, this guide is for windows only. Soon to come, OSX & Linux.
HOW TO ROOT SPRINT'S 2.27.651.5 RELEASE FOR THE CDMA HERO (Stock Android 2.1)
Make sure your phone is unplugged from your computer until I tell you to plug it in!
If you already have the Android SDK and HTC Sync set up on your computer, skip to Step 4 now
Step 1: Download the Android SDK here
Step 2: Extract the Android SDK zip. Move the contents of the extracted zip to C:\
Your Android tools folder path should now be C:\android-sdk-windows\tools
Step 3: Download HTC Sync 2.0.33 here
Run the installer, and reboot your computer when it is finished. Move on to step 4 once rebooted.
Step 4: Download the hero-root.zip. This zip contains everything you need to root your Hero.
(md5: c6e5058ed14f71c68fb099e10be142fb)
Step 5: Extract the 3 files inside hero-root.zip to the C:\android-sdk-windows\tools folder on your computer.
Step 6: Make sure USB Debugging is ON (checked) on your Hero. Go to Settings > Applications > Development > and make sure it is checked.
Step 7: Plug your phone into the computer via USB, Make sure that the connection type in the Notification Pull-Down Bar is "Charge Only", not "Disk Drive" or else this won't work.
If your computer asks you to restart after the new drivers were installed, do that now.
Step 8: Open a Command Prompt window by clicking the Start button and typing cmd into the search box and pressing enter.
It is also found under Start Menu > All Programs > Accessories > Command Prompt
Step 9: You will now enter the commands that I have put in code boxes followed by pressing ENTER, one code at a time.
You may also copy/paste these commands in to the Command Prompt, pressing ENTER after each, one at a time.
Comments will be outside of the code boxes (do NOT type these into the Command Prompt as they just are to help describe the root process)1:
Code:
cd C:\android-sdk-windows\tools
You should now see C:\android-sdk-windows\tools>
Now type2:
Code:
adb devices
If you've been following this guide you will see your phone's serial number. If you get "device not found" error, you either need to make sure you the drivers were properly installed or make sure you enable USB debugging on your phone. Continue on once you get the proper phone serial output.
You will now push the files needed to gain root to your sdcard in your phone with these following commands:3:
Code:
adb push unrevoked /sdcard
4:
Code:
adb push recovery.img /sdcard
5:
Code:
adb push boot-patched.zip /sdcard
Now we run the exploit. Be patient, this may take up to 40 seconds.6.
Code:
adb shell
(You should now see $)7.
Code:
sh /sdcard/unrevoked
You should now see output that says this:
Code:
$ sh /sdcard/unrevoked
sh /sdcard/unrevoked
Unpacking, please wait...
88 88 88b 88 88""Yb 888888 88 dP dP"Yb 88 dP 888888 8888b.
88 88 88Yb88 88__dP 88__ 88dP dP Yb 88odP 88__ 8I Yb
Y8 8P 88 Y88 88"Yb 88"" 8dP Yb dP 88"Yb 88"" 8I dY
`YbodP' 88 Y8 88 Yb 888888 YP YbodP 88 Yb 888888 8888Y
==================================================================
unrEVOked: root for HTC evo and hero (http://unrevoked.com)
#
-----------------
Now, on your phone, go to your app tray, and you will see that the Superuser Permissions app is in it.
Open the Superuser Permissions app. You will see a blank screen.
If you do not see the Superuser Permissions app in the app tray, go to
Settings > About Phone > Software information
If it says 2.27.651.6 under "Build Number" (notice the bolded, underlined, italic 6), you need to run the RUU in the second post of this thread to revert to .5 first and run this guide again. Doing this WILL erase all of your data on your phone, so be sure to back up anything if you need to first.
-----------------
In the Command Prompt on your computer, type:8.
Code:
su
A prompt will appear on your Hero asking you to give /system/bin/sh privileges. Click Allow.
Go back to your command prompt, and you should see
Code:
$ su
su
#
Now type:9.
Code:
flash_image recovery /sdcard/recovery.img
Flashing the recovery may take many seconds to complete. Wait until the # symbol returns to proceed.
You should now see
# flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
#
This means it was a successful flash.
Now type10.
Code:
reboot recovery
Your phone will now boot to the custom recovery image you just flashed.
If that doesn't work, (ie you get errors or it stays at the white/green HTC screen) try using this recovery image, put it on your sdcard, and try code #9 again.
In the Recovery Menu on your phone, choose the option:
Code:
Flash zip from sdcard
Then select
Code:
boot-patched.zip
and press the Home button to apply.
Once Recovery says "Install from sdcard complete", you need to make a nandroid backup!
In the main menu or the Recovery Screen, you will see an option that says
Code:
Backup/Restore
Choose that option, and then choose the option
Code:
Nand backup
This can take up to 5 minutes, so be patient while you see the
Code:
............
Once done, a nandroid backup of your phone will be created and saved to your sdcard in the folder directory:
Code:
/sdcard/nandroid/(your serial number)/
When it is complete, hit the back button to return to the Main menu, and hit "Reboot system now" from the menu to reboot normally!
DISABLE OTA UPDATES!!!!
To disable OTA updates that will patch this exploit, (after rooting and booted after creating a nandroid backup) run the following commands from Command Prompt.
Code:
cd C:\android-sdk-windows\tools
Code:
adb remount
Code:
adb shell
Code:
mv /system/etc/security/otacerts.zip /system/etc/security/otacerts.zip.bak
After doing this, the OTA updates WILL still download, BUT they will not pass signature checks to flash because of the code you just entered.
You now have full root access on 2.1!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The RUU that was updated on HTC and Sprint's Websites was in fact the patch to this exploit. I am posting a few VERIFIED copies of the 2.27.651.5 RUU's that are from the original release date, and have not been patched. Use these to revert back to .5 before rooting.
My Personal One I used for testing
nfinitefx45
More mirrors to come after verification from me.
HAHAHA
I knew if anyone could do it it would be Regaw
Way to go bro
regaw_leinad said:
Coming at 9pm PST
Click to expand...
Click to collapse
regaw_leinad said:
reserveddd
Click to expand...
Click to collapse
congrats dood.
regaw_leinad said:
Coming at 9pm PST
Click to expand...
Click to collapse
Nice thank you
Good job guys.
Coming at 9pm PST
Click to expand...
Click to collapse
Very good job....
-------------------------------------
Sent via the XDA Tapatalk App
great man, regaw!
awesome.....as a coder, this puts you right up there with Toast. obviously that's saying a lot. congrats!
You like to me?
Not cool bro.
Great job to all involved. Hope to keep some of ya around after the EVO.
regaw_leinad said:
Coming at 9pm PST
Click to expand...
Click to collapse
Thank you for your hard work.......
Congratulations. Damn we've got a talent pool here in the Sprint Hero section!
you are the man
Good job bro! I was wondering if it was even possible for a second there. Nice to see your back rooted too.
I'm impressed. Great job man , I was smart enough not to upgrade though (lol jk!). I should of tried to root 2.1, but I was way too busy; I guess I'll try when 2.2 comes around.
JsChiSurf said:
Congratulations. Damn we've got a talent pool here in the Sprint Hero section!
Click to expand...
Click to collapse
Yes we do! I'm just hoping not all of this talent is jumping ship to the Evo in the next 10 or so hours.
Congratulations to Daniel and all the others who helped him root the cursed official 2.1! Thanks for all your hard work.
I really hope htc will release the new 2.1 kernel source code soon after regaw release the root method, haha. Great job regaw!
Ausgezeichnet!!!
regaw_leinad said:
Coming at 9pm PST
Click to expand...
Click to collapse
Half an hour left!!!!
Imma finish watching the laker game..
I had faith in you Regaw.
i caught you asking question in the General section of Xda not the CDMA Hero Section
and i was like ohhh hes dedicated lmao.
***** IMPORTANT ROOT IS REQUIRED BEFORE PROCEEDING *****
TO ROOT YOUR INFUSE 4G GO THE FOLLOWING LINK AFTER ROOTING PROCEED BELOW
http://forum.xda-developers.com/showthread.php?t=803682
***** ALSO PLEASE READ CAREFULLY BEFORE ACTUALLY APPLYING STEPS *****
All right ladies and gentlemen, coders and non coders again I have personally found the unlock code NOT THE FREEZE CODE only the unlock code for your Samsung Infuse 4G by ATT hidden in the same files as previous Samsung phones.
This procedure is similar to finding the unlock code for the Vibrant 4G for those that have performed my steps in the past it should be a no brainer but if not please once again read everything carefully its not hard but just takes patience Of-course this all depends on your dedication and time but hopefully I have simplified it for you.
Steps:
1. Install "010 Hex editor" you can use trial does not have to be registered
2. Go to your Infuse 4G and open a terminal emulator (free on the Market) - (Root Required)
The following steps are credit to SS2006 on a different post
*** Dont forget the (su) command *** after the second line
_____
after opening a terminal emulator type the following
cd /dev/block <enter>
su <enter> <at this point your phone will ask for superuser access ALLOW it if you already haven't done so>
dd if=/dev/block/bml3 of=/sdcard/external_sd/bml3.bak <enter>
note: if you dont have an external SD CARD type the following
dd if=/dev/block/bml3 of=/sdcard/bml3.bak
Go find the file on your SD Card or Internal Storage depending on your situation and transfer it to your computer
3. Open 010 Hex Editor
4. In 010 Hex Editor go to the Menus above and select VIEW>LINEFEEDS>SELECT CUSTOM>SET YOUR BYTES TO "32" Nothing Less
5. Locate the bml3.bak file you created and transfered to your computer and open it using the editor
(CREDIT TO FR0Z3N FOR CLARIFYING THE FOLLOWING 2 STEPS)
6. Using your keyboard select CRTL+F to search for a hex string, when the search window pops up select "Hex byte" in the Type field and then search for the following string below:
"FFFFFFFFFF0100000000" ALL TOGETHER, Then Hit the FIND ALL button to the right, some of you will get many results and others up to 10 results on your screen below
7. If you look at your Hex editor there are 3 window panes on the selected line (See Image Below)
e.g 4CCC60h <-- Offset
01 01 01 01 < -- Hex Keys
yyyyyyyyy <- ASCII text where your code is
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
8. Go through each result from the above search and you will see on the 3rd window pane (as shown on pic above) after the hex keys there is an 8 DIGIT CODE (Write this code Down) this is your unlock code NCK for your phone
Sidenote: SCAN THROUGH EACH RESULT AND YOU WILL SEE THAT IN YOUR RESULTS SOME OF YOU MAY GET UP TO 3 DIFFERENT 8 DIGIT CODES WRITE THEM ALL DOWN NORMALLY THE 8 DIGIT CODE THAT APPEARS THE MOST WILL BE THE ONE THAT UNLOCKS YOUR PHONE THE OTHER CODES MAY BE YOUR FREEZE CODE BUT I HAVE NOT TESTED THIS YET THIS 8 DIG CODE SHOULD SHOW ON AT-LEAST ONE MORE RESULT CHECK ALL YOUR RESULTS FROM THE SEARCH ABOVE( SOME OF YOU WILL HAVE YOUR CODE SHOWN AT-LEAST 2 TIMES AND SOME OF YOU WILL HAVE THE CODE SHOW MORE THAN 4 TIMES) YOUR RESULTS MAY VARY EVEN UP TO 39 RESULTS AGAIN SCAN THROUGH ALL RESULTS
**** TO INPUT THE UNLOCK NETWORK CODE DO THE FOLLOWING ****
9. Turn off your phone
10. Insert a foreign SIM card not attached to your current provider (e.g if you have ATT use a TMOBILE SIM CARD) and turn on your phone
11. You will be prompted to enter a Network Unlock Control Key ( Use the code above that you wrote down and type it in your phone exactly)
12. After entering your NCK please hit Unlock or GO button and you should see a screen that says "network unlock successful" and your phone should go in the main screen after your phone has been unlocked.
THATS IT FOLKS HAVE FUN
PS> If you entered an incorrect code you must of entered the wrong code or wrote it down wrong please read carefully and verify the code matches the results from above in at-least more than one instance
SHOULD ANYONE NEED HELP PM ME AND I WILL BE GLAD TO HELP
personally my INFUSE 4G has been rooted from day 1 and wi-fi tethering enabled and now it has been Unlocked
10. Insert a foreign SIM card not attached to your current provider (e.g if you have
Where can I go to get this SIM card?
Regards,
Jim Jep
JimJep said:
Where can I go to get this SIM card?
Regards,
Jim Jep
Click to expand...
Click to collapse
You can go out and buy any SIM card not attached to your phone example buy a prepaid SIM like SIMPLE MOBILE / TMOBILE etc.. put in any sim card that is not your carriers basically it does not have to be an International SIM if that's what your thinking
Hope this helps
This one works and is much easier.
Also no root required (it does root the phone temporary but returns it to stock without you having to do anything).
Click me.
Papi4baby said:
This one works and is much easier.
Also no root required (it does root the phone temporary but returns it to stock without you having to do anything).
Click me.
Click to expand...
Click to collapse
If you read through the posts of the link you posted no all get the code some get NULL some get nothing in this instance you actually see the code you are risking in changing file on your phone and possibly bricking your phone. My method is a simple file where your code is hidden.
To each his own, various methods I tried that link before I did mine and did not work so I tried my own method and what would you know It worked
Thanks again though for showing the options
Note: Please post your results thanks
Thankz Sanfranx415, your unlock instruction worked perfect for me. One thing i have noticed, Terminal Emulator didnt like back space, so be accurate with those commands, other than that yours is perfect. Thankz again.
Hi there.
Thanks for such a great and helpful post.I have a couple questions...what is the freeze code and what is the difference between this code and the freeze.
Once again thank you.
sweet, this works on this model as well
going to be unlocking mine right now
The freeze code is the code you would use if you tried too many times to unlock your phone
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
fr0z3n said:
sweet, this works on this model as well
going to be unlocking mine right now
Click to expand...
Click to collapse
Go for it, as always I credit where credit is due thank you
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
NGOPHUSAI said:
Thankz Sanfranx415, your unlock instruction worked perfect for me. One thing i have noticed, Terminal Emulator didnt like back space, so be accurate with those commands, other than that yours is perfect. Thankz again.
Click to expand...
Click to collapse
Yes terminal emulator can be sensitive but i'm glad your unlock was sucessful
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
Re unlock code
Many thanks excellent hack I got there in the end without to many problems, just a quick comment it did return 4 codes 3 all the same 1 different however it was the single code that worked not the 3 the same! however for the faint of heart you do get 10 attempts again many thanks to all who contributed to this hack
Please see my reply in thread thanks man a great job and a great hack
Worked like a charm
Thanks for your tutorial. This worked like a charm.
I had three entries come up and they all had the same code. Verified on a T-mobile Sim.
First time the codedid not work the second time it went in. I must of fat fingered the first try
paul1994 said:
Thanks for your tutorial. This worked like a charm.
I had three entries come up and they all had the same code. Verified on a T-mobile Sim.
First time the codedid not work the second time it went in. I must of fat fingered the first try
Click to expand...
Click to collapse
Your welcome glad to help
Sent from my LG-P999 using XDA Premium App
I had only one code come up, and it worked perfectly.
I used my old T-Mobile SIM.
Thanks for the tutorial.
GREAT HACK!
Confirmation, it works thanks as much as useful this unlock
sanfranx415 said:
***** IMPORTANT ROOT IS REQUIRED BEFORE PROCEEDING *****
TO ROOT YOUR INFUSE 4G GO THE FOLLOWING LINK AFTER ROOTING PROCEED BELOW
http://forum.xda-developers.com/showthread.php?t=803682
***** ALSO PLEASE READ CAREFULLY BEFORE ACTUALLY APPLYING STEPS *****
All right ladies and gentlemen, coders and non coders again I have personally found the unlock code NOT THE FREEZE CODE only the unlock code for your Samsung Infuse 4G by ATT hidden in the same files as previous Samsung phones.
This procedure is similar to finding the unlock code for the Vibrant 4G for those that have performed my steps in the past it should be a no brainer but if not please once again read everything carefully its not hard but just takes patience Of-course this all depends on your dedication and time but hopefully I have simplified it for you.
Steps:
1. Install "010 Hex editor" you can use trial does not have to be registered
2. Go to your Infuse 4G and open a terminal emulator (free on the Market) - (Root Required)
The following steps are credit to SS2006 on a different post
*** Dont forget the (su) command *** after the second line
_____
after opening a terminal emulator type the following
cd /dev/block <enter>
su <enter> <at this point your phone will ask for superuser access ALLOW it if you already haven't done so>
dd if=/dev/block/bml3 of=/sdcard/external_sd/bml3.bak <enter>
note: if you dont have an external SD CARD type the following
dd if=/dev/block/bml3 of=/sdcard/bml3.bak
Go find the file on your SD Card or Internal Storage depending on your situation and transfer it to your computer
3. Open 010 Hex Editor
4. In 010 Hex Editor go to the Menus above and select VIEW>LINEFEEDS>SELECT CUSTOM>SET YOUR BYTES TO "32" Nothing Less
5. Locate the bml3.bak file you created and transfered to your computer and open it using the editor
(CREDIT TO FR0Z3N FOR CLARIFYING THE FOLLOWING 2 STEPS)
6. Using your keyboard select CRTL+F to search for a hex string, when the search window pops up select "Hex byte" in the Type field and then search for the following string below:
"FFFFFFFFFF0100000000" ALL TOGETHER, Then Hit the FIND ALL button to the right, some of you will get many results and others up to 10 results on your screen below
7. If you look at your Hex editor there are 3 window panes on the selected line (See Image Below)
e.g 4CCC60h <-- Offset
01 01 01 01 < -- Hex Keys
yyyyyyyyy <- ASCII text where your code is
8. Go through each result from the above search and you will see on the 3rd window pane (as shown on pic above) after the hex keys there is an 8 DIGIT CODE (Write this code Down) this is your unlock code NCK for your phone
Sidenote: SCAN THROUGH EACH RESULT AND YOU WILL SEE THAT IN YOUR RESULTS SOME OF YOU MAY GET UP TO 3 DIFFERENT 8 DIGIT CODES WRITE THEM ALL DOWN NORMALLY THE 8 DIGIT CODE THAT APPEARS THE MOST WILL BE THE ONE THAT UNLOCKS YOUR PHONE THE OTHER CODES MAY BE YOUR FREEZE CODE BUT I HAVE NOT TESTED THIS YET THIS 8 DIG CODE SHOULD SHOW ON AT-LEAST ONE MORE RESULT CHECK ALL YOUR RESULTS FROM THE SEARCH ABOVE( SOME OF YOU WILL HAVE YOUR CODE SHOWN AT-LEAST 2 TIMES AND SOME OF YOU WILL HAVE THE CODE SHOW MORE THAN 4 TIMES) YOUR RESULTS MAY VARY EVEN UP TO 39 RESULTS AGAIN SCAN THROUGH ALL RESULTS
**** TO INPUT THE UNLOCK NETWORK CODE DO THE FOLLOWING ****
9. Turn off your phone
10. Insert a foreign SIM card not attached to your current provider (e.g if you have ATT use a TMOBILE SIM CARD) and turn on your phone
11. You will be prompted to enter a Network Unlock Control Key ( Use the code above that you wrote down and type it in your phone exactly)
12. After entering your NCK please hit Unlock or GO button and you should see a screen that says "network unlock successful" and your phone should go in the main screen after your phone has been unlocked.
THATS IT FOLKS HAVE FUN
PS> If you entered an incorrect code you must of entered the wrong code or wrote it down wrong please read carefully and verify the code matches the results from above in at-least more than one instance
SHOULD ANYONE NEED HELP PM ME AND I WILL BE GLAD TO HELP
personally my INFUSE 4G has been rooted from day 1 and wi-fi tethering enabled and now it has been Unlocked
Click to expand...
Click to collapse
Thanks. OMG. I did not think that this would work or that I could get 010 Hex Editor to work for me, but, all of you, just take a breath, read carefully, and it works. I just unlocked my Infuse and T-Mobile and Airtel (India) sim cards are both working. I turned off and on my phone multiple times, and low and behold, it still works. Amazing. Thanks for all your work. I will definately donate.
Worked like charm here. I just went into tmobile and they gave me a sim. just finished with an unlock successful. The reason I want it unlocked was to have free tethering (coming from an unlocked streak) but after the unlock when I go to settings it still says must have a plan or whatever at&t crap it says? Can anyone confirm that once unlocked you can tether and hotspots for free under at&t?
Thanks
Sent from my A500 using XDA Premium App
I just wanted to share if you unlocked and are on stock and try to tether or use hotspot and get the verifying crap or you need a plan message you need to disable the system apk tethering manager is the name I believe. To do so you need to be rooted.
1.be rooted
2. Use root explorer to navigate to /system/app and search for tether manager I can't remember exactly but if you go to the T's its the only .apk with tether in the name.
3. Make sure you mount as r/w
4.long press on the target .apk and select rename
5. Rename to "tether whatever.bak" so just replace the extension .apk to .bak. Select ok and your done
Now you can tether and hotspot for free, enjoy
Note: if unlocked on running infused rom the tethering.apk has already been removed
Sent from my infused machine
I bought my first smart phone Samsung Gio S5660M and tried to unlock it. I tried different ways but weird things happened and I don’t know what causes the problem. I was wondering whether the unlock code would change if I did something to the phone. Now the phone is still locked and I really need and appreciate your help.
First I used the method in the link: http://forum.xda-developers.com/showthread.php?t=1204705 to root and unlock the phone but was not able to finish it. The steps that I have completed are as follows:
To root the phone:
1. Download this file http://www.mediafire.com/download.php?jzvnlbhidsd5f6l
2. Copy root_gb_gio.zip to the root of the SD card and put the card in the phone
3. Shutdown the phone.
4. Put the phone in recovery Mode (press: Home button + Power button toghether)
5. In recovery mode, choose Install Update from SD-card using Vol. up / down key and press Home key to confirm
6. Search for the root_gb_gio.zip file on the SD-card and Press home key again to run the update
7. Reboot
8. Verify in the app folder if SuperUser app is installed properly
9. Reboot
Network Unlock (using ADB Shell from PC).
1. Download and install Samsung Kies to the PC from here: http://www.samsungapps.com/about/onPc.as, also install Samsung USB Driver
2. Download and install ADB which comes with Android SDK from: http://developer.android.com/sdk/index.html
-Go to the "Available Packages" Option on the left Menu
-Click on the "Refresh" Button on the bottom Right and wait until it finish
-From Items select the "Andoid SDK platform-tools, revision 6" Item
-Click the "Install Selected" button on the botton right and wait until it finish then close the Android SDK
3. Add the correct path
-Right-click on Computer Icon (on your Desktop) and select "Properties" from the menu,
-On My PC Properties select the "Advanced Options" Tab
-Click "Advanced System Settings"
-Click "Environment Variables"
-Highlight the "Path" Variable and click the "Edit"
-At the end of the line (and path) add the path: ;C:\Program Files\Android\android-sdk\platform-tools
4. Connect the phone to the computer via the USB cable
-Click on the start button and open the "Run" option, on Run type cmd.exe and press enter. A command prompt window popped out.
-Type the next text to access the ADB Shell: cd C:\Program Files\Android\android-sdk\platform-tools
-Type: adb shell
-Now in adb shell (and executing commands on the phone itself)
-Type the next command: su
-The superuser application popped up on the PHONE SCREEN (yes take a look at the phone screen) asking to allow root privileges to the adb shell. Choose Allow root access for the ADB shell on the phone.
-Type: cd /
-Type : mount -o remount rw /
-Type: mkdir /efs
-Type: mount -o nosuid,ro,nodev -t vfat /dev/block/stl5 /efs
-Type: cat /efs/mits/perso.txt
got a bunch of characters on the screen and a 8 digit number, the unlock code, which is 28572603
-Type: unmount /efs (It should umount /efs, but I typed it wrong)
5. Disconnect the USB cable from the phone
6.Turn the phone off and insert the SIM card
7. Turn on the phone
In the last step it should ask for the unlock code to unlock the phone, however, it didn’t ask for the unlock code. Instead there was a message: “Phone is SIM Corporate Locked” and there is nowhere to input any code.
When I typed “*#7465625#, the result is as follows: Network Lock [OFF], Network Subset Lock [OFF], SP Lock [OFF], CP Lock [ON]. Note that the corporate lock is on. But I could access menu with the foreign SIM card in the phone. When I tried to dial “*#7465625*638*28572603” or “#0111*28572603” with or without foreign SIM card, the message is always something like network not available (cannot recall the exact words). When I went to a FIDO kiosk for help (SIM card is from FIDO), they told me to unroot the phone so that the phone could ask for the unlock code.
I googled corporate lock/SPCK code on the Internet and there is such message: “In 1% of cases to unlock samsung SPCK code is need”, I called Samsung for help with SPCK code. The technical support in Samsung asked me to factory reset the phone by typing “*2767*3855#”. After the reset, the status of the locks were still the same as before, so is the message “Phone is SIM Corporate Locked”. Then Samsung told me that they don’t have SPCK code. I noticed that SuperUser icon was still on the menu after the factory reset.
A further search showed the unlock method of mapping image partition from: http://forum.xda-developers.com/showthread.php?t=1244695 and http://forum.xda-developers.com/showpost.php?p=17148825&postcount=334 (same method). When I went to Shell and typed “su”, not sure whether because of the factory reset or not, superuser or admin denied, so I redid the rooting by following the previous steps, but it only took a few seconds to finish it. Then the steps I followed were:
1, first, go to the command line of pc.(win xp "start->run->cmd" )
and type "cd\", now in the root of the hard drive (also tried cd \Program Files\Android\android-sdk\platform-tools)
2, second, type "adb shell".
3, after that, type "su".
4, then, type "cat /dev/bml5>/sdcard/bml5.img"
5, type twice "exit" to disconnect with gio.
6, type "adb pull /sdcard/bml5.img"
But there is an error message “remote object /sdcar/bml5.img does not exist". I just repeated the steps a few minutes ago to get a few screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(using cd \Program Files\Android\android-sdk\platform-tools)
(using cd \)
(a different error: so I used mount command)
I think at this point (cannot recall after the following tries or at this time) that I inserted a foreign SIM card, the phone began to show message “Network Locked”, took out the foreign SIM card, typed “*#7465625#", weird enough, the result changed to: Network Lock [ON], Network Subset Lock [OFF], SP Lock [OFF], CP Lock [OFF]. Corporate lock is gone but the network lock came back. I don’t know the reason – is that because I did factory reset?
I put the foreign SIM card back to the phone, input the unlock code generated earlier “28572603”, but it was not successful. I decided to go back to the first method (ADB shell from PC) to generate the unlock code again to see whether the result code is the same. However, weird gain, this time no code at all. I reproduced the screenshot a moment ago for the result (I had to cut the screen into two half):
The third method I tried is to unlock the phone by using Android Terminal Emulator, the steps were:
- In Android Market, download and install Android Terminal Emulator
- Boot up the Android Terminal Emulator application
-Using the on-screen keyboard, type su, allowed the permission from the prompt
-Type: cd /
-Type : mount -o remount rw /
-Type: mkdir /efs
-Type: mount -o nosuid,ro,nodev -t vfat /dev/block/stl5 /efs
-Type: cat /efs/mits/perso.txt
The desire result should be a bunch of characters on the screen and a 8 digit number. However, I didn’t get the desire result – it seems that the result is the same as using the first method after factory reset, here is the screenshot (it seems that the shot is incomplete, but I had a hard time to get even such an incomplete shot – the shell would exit when I tried to screenshot):
My questions are: why the same method cannot generate the same code? Is it because I did something to the phone, like factory reset? The unlock code will change because of the situation or it will always keep the same? Why I cannot see the bml5.img? Is it possible I damaged it by chance? I am also worried that now even if I buy uncode code from GSMLiberty, it would not work any more because of what I did to the phone. Is it possible so? What is my option now? (I tried the code once, so I still have another two chances to input unlock code). Is what has happened weird or there is a reason for that?
Thank you very much.
I also pulled the perso.txt file onto my PC and reviewed it in XVI32. It does not look like any of the files others mentioned (a lot of 00 or FF followed by a number). Attached here is perso.txt. Is my perso.txt corrupted? If yes, how can I recover it? Thanks.
As far as I know, you're the first person that's reported seeing a CP lock on this phone... One possibility is that this happened instead of plain old bricking when you mistyped the umount command the first time around.
Is your IMEI still intact?
Did you reboot the phone since your third attempt?
Did you by any chance keep the first perso.txt you cat'ed on your first attempt?
The suggestion below is at best a shot in the dark and could very well worsen the situation. With that out of the way...
If your IMEI is still intact, you could try booting in CWM, mounting /efs as rewritable, and upload the attached perso.txt, unmount efs and reboot. The file is simply my own perso.txt, from an unlocked 5660M, with your unlock code put in place of mine in a Unix line-ending aware editor. (Another, albeit riskier possibility would be to mount rewritable in the main OS and cat the file into place, then unmount and reboot.)
Good luck,
Darkshado
Thank you, Darkshado, for answering my questions.
Yes the IMEI is still intact. What is weird is that now CP is off and network lock is on after I don't know which operation - I thought it should be due to the factory reset, but after factory reset, the status was still CP [ON] and network lock [OFF]. The I did reroot. The phone was rebooted many times after each attempt, and I only input unlock code once so I still have another two chances.
No I didn't make a copy of the original perso.txt as I almost knew nothing when I first tried.
About unmount mistake, is it so severe if there is a typo? My thought was that mounting and unmounting just control access to the file. When we mount a file, we get access to the file. If we forget to unmount it, it leave a hole for others to access. Is my understanding right? If yes, the typo in unmount command for the first method should not be a big deal as I rebooted the phone after an probably unsuccessful unmount.
As to the perso.txt, what I guess is that the file perso.txt contains all the unlock codes and when we input unlock code from the screen, the system will compare the input code with the code in perso.txt. If they are the same, unlock succeeds, which is similar to using password when we login anywhere. Am I right?
I actually think that uploading your perso.txt mught be a solution. But before doing that, I think it is better to compare your perso.txt with another perso.txt from another phone to see whether the difference is only the unlock code. If yes, the solution will succeed. However, if the perso.txt files from different phones are quite different -like the location of the unlock code and other data that is not 00 or FF, there is a good chance that it's very risky. Do you have another perso.txt available? Or anybody in the forum has a perso.txt available to compare?
My other question is how useful is this perso.txt. If I delete it totally by chance and ask people to unlock the phone from hardware, will the system still operate normally?
I'm going to try to factory reset the phone and reroot again - My PC is in repair and I'll try after I get my PC back - to see whether perso.txt could be restored. Do you have bml5.img in your phone? I don't know why I don't have it on my phone. But from the forum, it looks like that the bml5.img is very similar to perso.txt, only 00 becomes FF or vice verse.
Thanks again for your help.
SPnewb said:
Thank you, Darkshado, for answering my questions.
Yes the IMEI is still intact. What is weird is that now CP is off and network lock is on after I don't know which operation - I thought it should be due to the factory reset, but after factory reset, the status was still CP [ON] and network lock [OFF]. The I did reroot. The phone was rebooted many times after each attempt, and I only input unlock code once so I still have another two chances.
Click to expand...
Click to collapse
That is very strange. What, if any, SIMs did you have in the phone when attempting the unlock at the different stages? Was the Fido SIM in at any time before trying to get an unlock code prompt?
As far as I know, the factory reset operation, at least when triggered from recovery, only wipes the /data and /cache partitions. Is anything done to NV items? I don't have any data to tell.
About unmount mistake, is it so severe if there is a typo? My thought was that mounting and unmounting just control access to the file. When we mount a file, we get access to the file. If we forget to unmount it, it leave a hole for others to access. Is my understanding right? If yes, the typo in unmount command for the first method should not be a big deal as I rebooted the phone after an probably unsuccessful unmount.
As to the perso.txt, what I guess is that the file perso.txt contains all the unlock codes and when we input unlock code from the screen, the system will compare the input code with the code in perso.txt. If they are the same, unlock succeeds, which is similar to using password when we login anywhere. Am I right?
Click to expand...
Click to collapse
Your understanding about mounting and unmounting is correct, but I am not certain that perso.txt is actually used by the phone to check the unlock code. It may also be written there for some other reasons...
The problem with our phones is that corruption has occurred by merely reading the stl5 partition the wrong way.
I actually think that uploading your perso.txt mught be a solution. But before doing that, I think it is better to compare your perso.txt with another perso.txt from another phone to see whether the difference is only the unlock code. If yes, the solution will succeed. However, if the perso.txt files from different phones are quite different -like the location of the unlock code and other data that is not 00 or FF, there is a good chance that it's very risky. Do you have another perso.txt available? Or anybody in the forum has a perso.txt available to compare?
My other question is how useful is this perso.txt. If I delete it totally by chance and ask people to unlock the phone from hardware, will the system still operate normally?
Click to expand...
Click to collapse
The idea of comparing some perso.txt files is good, but so far all the perso.txt files I've seen uploaded came from the Euro/Asia 5660 Gio, so we'd need files from a 5660M. They did look almost identical to mine though, with essentially a Bell network identifier at the beginning that wasn't present at all in theirs. One person with a 5660 also posted a before/after set, and the file does change a little after the unlock.
I've been reluctant to try too many things on my EFS partition, like deleting perso.txt to see how the phone reacts, for fear of bricking it.
I'm going to try to factory reset the phone and reroot again - My PC is in repair and I'll try after I get my PC back - to see whether perso.txt could be restored. Do you have bml5.img in your phone? I don't know why I don't have it on my phone. But from the forum, it looks like that the bml5.img is very similar to perso.txt, only 00 becomes FF or vice verse.
Thanks again for your help.
Click to expand...
Click to collapse
There are two "levels" you can access the partitions on the phone. stl is a higher level access, with which you can get correct RFS partitions for instance, while bml is a lower, block-level access. perso.txt is simply a file contained in stl5, also known as the /efs partition. You can read its contents in a round-about way via bml, but you wouldn't want to flash an /efs, /system/ or /data partition through bml.
Unlike reading stl5, reading bml5 has not caused anyone bricking so far. bml5 is sufficient to get the unlock code as well.
Good luck,
Darkshado
Hi Darkshado,
Thank you very much for your help.
Darkshado said:
That is very strange. What, if any, SIMs did you have in the phone when attempting the unlock at the different stages? Was the Fido SIM in at any time before trying to get an unlock code prompt?
Click to expand...
Click to collapse
The phone was locked to Bell, and my SIM card is from FIDO. I also got a Rogers SIM card for testing. When I rooted and generated teh code, I didn't have any SIM card in the phone. When I inserted Fido card after teh first attempt, I got the message " Phone is SIM Coperated locked" [i.e. when CP lock is On and other locks OFF], but I could still use the other functions of the phone. When the CP lock is OFF and Network lock is ON, I could not use the phoen at all because teh screen asked to input unlock code. If no input orcode is wrong, I cannot use the phone at all. Without SIM card, I could still use other functions of the phone.
As far as I know, the factory reset operation, at least when triggered from recovery, only wipes the /data and /cache partitions. Is anything done to NV items? I don't have any data to tell.
Click to expand...
Click to collapse
What is NV items? Can you tell me how I can tell where to see NV items?
Your understanding about mounting and unmounting is correct, but I am not certain that perso.txt is actually used by the phone to check the unlock code. It may also be written there for some other reasons...
Click to expand...
Click to collapse
I was wondering whether the perso.txt is like config file?
The problem with our phones is that corruption has occurred by merely reading the stl5 partition the wrong way.
Click to expand...
Click to collapse
perso.txt is simply a file contained in stl5, also known as the /efs partition. You can read its contents in a round-about way via bml, but you wouldn't want to flash an /efs, /system/ or /data partition through bml.
Click to expand...
Click to collapse
I cannot think of where I read the partition wriong other than I might hav etyped the wrong unmount for the first time followed by a reboot. I actually thinking of falshing the phone, but for the moment I have not read anything about flash yet and have no idea where to find the proper version of files to falsh.
When I pull the perso.txt to PC, I seemed to use the following method (my PC is still in repair so I cannot verify ):
-Type: adb shell
-Now in adb shell
-Type: su
- allow root privileges to the adb shell.
-Type : mount -o remount rw /
-Type: mkdir /efs
-Type: mount -o nosuid,ro,nodev -t vfat /dev/block/stl5 /efs
-Type: exit twice to exit shell
-Type: adb pull /efs/mits/perso.txt
-Type: adb shell (to go back to shell)
-Type: umount
Is there any risk with this method?
About perso.txt,
One person with a 5660 also posted a before/after set, and the file does change a little after the unlock.
Click to expand...
Click to collapse
I will try to see whether I could get some perso.txt files from anotehr forum (redflagdeals). Can you tell me where I can find the before/after set?
Thank you again very much.
Cathy
Hello Cathy,
One big piece of advice I can give you is to try and have a basic understanding of whatever command it is you're typing in an ADB shell.
The "cat" command can take one or many standard inputs (we'll stick to files for now) and output them to a standard output; in our case, the screen or another file.
Its one way of copying a file, or simply seeing its contents depending on where you send it.
With multiple files in the input, you're concatenating them before they get output.
I would not try the method in your last post AT ALL. You already have your code, and I see no reason why your current perso.txt would be of any use. It is a configuration file, it has to do with the various locks, but I wouldn't be able to tell you more. The way yours has been "corrupted" (I'm employing the term loosely here) may be the reason you've seen that CP lock appear. It may also have altered your Network unlock code in unforeseen ways.
I don't remember anyone trying to directly adb pull perso.txt from the /efs partition off a live phone. Do this at your own risk.
The problems we've seen occur are in all likelyhood due to interference between the modem firmware and the higher-level Android OS. That's why even normally "harmless" read commands have caused problems.
The dd command, as well as leaving /efs mounted on normal mode phone shutdown are constants in multiple bricking cases on the Gio and other similar Samsung phones like the Galaxy Ace and Mini.
The lower-level bml5 partition has been deemed safe to read with the dd command so far, even from a live phone.
Completely disable the modem firmware, like in recovery mode, and you can access, and even edit, the /efs partition in a relatively safe manner.
Something interesting happened as I began writing this: I don't know how or when this happened, but I somehow had relocked my phone to Bell!
I decided to try the lock status code you posted above and saw "Network Lock: ON" Slipping another SIM (an unactivated Koodo one) in my Gio prompted for the unlock code, which I typed and got a network unlocked message.
I took another look at the perso.txt file I had modified for you and recognized a number near the beginning: 302610 that's the Bell MNC! I rebooted in recovery, mounted /efs and adb pulled perso.txt again (safe because I was in recovery mode). The file has the exact same length, and a few differences visible in Winmerge or a hex editor of your choosing.
I turns out I can relock and unlock my phone as I see fit! I haven't tried, but I wouldn't be surprised if I could even lock my phone to a network other than Bell.
You also asked about NV items: they're phone settings common to all Qualcomm cellular modem based cellphones. GSM and WCDMA antenna power and gain settings, factory test mode, IMEI, there are thousands.
In the case of the Gio, some are accessible off the EFS (stl5) partition in the /nvm/num/ directory. Others, like the IMEI unfortunately, are stored elsewhere in the phone, I don't know where. We can read all the settings by using two leaked Samsung programs, named QPST and QXDM respectively. We can edit some of them, but unless you know exactly what you're doing, this is an easy way to completely mess up a phone.
One last silly question: did you have a MicroSD memory card in the phone when you tried cat'ing bml5 to /sdcard on your second attempt?
Okay. I think there is a way to solve your unusual lock problems, try the following steps:
Get Odin here
Get the latest Odin-flashable Gio ClockworkMod-based recovery available on XDA.
Download the perso_Cathy.txt attached below.
Flash the CWM-based recovery to your phone.
Reboot in recovery mode and connect the phone to your computer.
In Windows Explorer, go to the directory you've saved perso_Cathy.txt, and shift+right-click on the directory. Open command line from here. (Otherwise, open a command line window and cd to that directory.)
adb shell (notice your shell is already # aka root)
mount -o nosuid,rw,nodev -t vfat /dev/block/stl5 /efs (notice we're mounting rewritable this time)
exit (this will take you back to the regular command line)
adb push perso_Cathy.txt /efs/mits/perso.txt (so we're pushing and renaming at the same time)
adb shell umount /efs (I doubt this is *really* necessary, but better safe than sorry. You can send single commands to the shell this way)
adb reboot
The phone should already be unlocked on reboot.
Good luck,
Darkshado
Hi Darkshado,
Thank you for your quick response.
Darkshado said:
One big piece of advice I can give you is to try and have a basic understanding of whatever command it is you're typing in an ADB shell.
Click to expand...
Click to collapse
That's good advice If I read the whole thread of unlocking first before I began unlocking, there might not have been problems. I began to unlock after reading a few postings. I used Linux long time ago, but obviously I could not recall anything now.
I would not try the method in your last post AT ALL. You already have your code, and I see no reason why your current perso.txt would be of any use. It is a configuration file, it has to do with the various locks, but I wouldn't be able to tell you more. The way yours has been "corrupted" (I'm employing the term loosely here) may be the reason you've seen that CP lock appear. It may also have altered your Network unlock code in unforeseen ways.
Click to expand...
Click to collapse
The code I had was got before the corrupted perso.txt. I had a strong feeling that the input unlock code will be compared with the code in perso.txt for unlocking, Otherwise if perso.txt is not useful any more, why when I input the initially generated unlock code, the unlocking is not successful. The CP lock is now OFF after the perso.txt is corrupted, though it is hard to judge whether CP is ON or not before perso.txt is corrupted because I got the unlock first then I saw CP was ON.
I don't remember anyone trying to directly adb pull perso.txt from the /efs partition off a live phone. Do this at your own risk.
Click to expand...
Click to collapse
Can you tell me what command you use to get perso.txt? From the info below it seems that you use the same or similar commands, but in the recovery mode instead of the normal mode, is it right?
I turns out I can relock and unlock my phone as I see fit! I haven't tried, but I wouldn't be surprised if I could even lock my phone to a network other than Bell.
Click to expand...
Click to collapse
By editing perso.txt only?
One last silly question: did you have a MicroSD memory card in the phone when you tried cat'ing bml5 to /sdcard on your second attempt?
Click to expand...
Click to collapse
Yes, since I inserted the MicroSD card into the phone for rooting, I never took it out. But I can hardly imagine this will cause any problem.
I think there is a way to solve your unusual lock problems, try the following steps:
Get Odin here
Get Ingmar Steen's latest Gio ClockworkMod-based recovery here
Download the perso_Cathy.txt attached below.
Flash the CWM-based recovery to your phone.
Reboot in recovery mode and connect the phone to your computer.
In Windows Explorer, go to the directory you've saved perso_Cathy.txt, and shift+right-click on the directory. Open command line from here. (Otherwise, open a command line window and cd to that directory.)
adb shell (notice your shell is already # aka root)
mount -o nosuid,rw,nodev -t vfat /dev/block/stl5 /efs (notice we're mounting rewritable this time)
exit (this will take you back to the regular command line)
adb push perso_Cathy.txt /efs/mits/perso.txt (so we're pushing and renaming at the same time)
adb shell umount /efs (I doubt this is *really* necessary, but better safe than sorry. You can send single commands to the shell this way)
adb reboot
Click to expand...
Click to collapse
After a second thought, I decided not to flash the memory since I have little knowledge about it and the tools you mentioned here. As you suggest, I should know enough before doing it. So now, I was wondering whether it will solve the problem by just push the file perso_Cathy.txt in your above message to /efs/mits/perso.txt in recovery mode. What do you think? Another quesion is that I wish to back up all the files in the operating system before any more action. Can you tell me how to back up?
My PC is back but now I cannot even install androit SDK on the computer, so I have to bring it back for repair. So the next few days I probably would not be able to try anything, but once I try, I'll let you know the rsult.
Thank you very much.
Cathy
SPnewb said:
I had a strong feeling that the input unlock code will be compared with the code in perso.txt for unlocking
Click to expand...
Click to collapse
It most definitely is compared. From what I can tell, perso.txt contains all the SIM-lock information, status and codes.
Can you tell me what command you use to get perso.txt? From the info below it seems that you use the same or similar commands, but in the recovery mode instead of the normal mode, is it right?
Click to expand...
Click to collapse
Exactly. Recovery mode is what makes the whole thing safe. You need a rooted recovery to do it though.
There are two ways to get the actual perso.txt file off the phone: adb pull (directly or by cat'ing the file to the sd card beforehand) or dd'ing the stl5 partition and extracting perso.txt from it.
By editing perso.txt only?
Click to expand...
Click to collapse
Yes.
After a second thought, I decided not to flash the memory since I have little knowledge about it and the tools you mentioned here. As you suggest, I should know enough before doing it. So now, I was wondering whether it will solve the problem by just push the file perso_Cathy.txt in your above message to /efs/mits/perso.txt in recovery mode. What do you think?
Click to expand...
Click to collapse
I'm pretty confident it will solve the problem, otherwise I would not have gone to the trouble of writing these instructions and uploading the file for you.
Another quesion is that I wish to back up all the files in the operating system before any more action. Can you tell me how to back up?
Click to expand...
Click to collapse
Look here.
My PC is back but now I cannot even install androit SDK on the computer, so I have to bring it back for repair. So the next few days I probably would not be able to try anything, but once I try, I'll let you know the rsult.
Click to expand...
Click to collapse
What does the ADK installer say? If its complaining about not finding the JDK when you've already installed it, just it Back, and then Next. It will detect at that time and proceed with the installation. It's a known bug. Also, stick to JDK version 6 for the time being. Version 7 is so recent there might be some incompatibilities...
Thank you very much.
Click to expand...
Click to collapse
You're welcome.
Goodbye,
Darkshado
The phone is bricked now. What I did is: hole the HOme key while pressing the power key, the phone asked me whether to "reboot the system now" or "update from /sdcard" or "wipe /data XXX factory reset" (sth like factory reset) or "wipe /cach", I chose "reboot the system now". after that , connect the phone to the system. What I did in PC is catured in teh following image:
After that, when rebooting the phone, the phone began to falsh "samsung" and it cannot be shut down any more.
It seems that using other people's perso.txt does not work. One reason may be that, as you said, "perso.txt contains all the SIM-lock information, status and codes", other than unlock code, it might also read each individual phone's information, since that hte perso.txt is not mine, the phone cannot find the proper information, which causes phone to do indefinite loop. If that is the case, instead of uploading a new perso.txt, editing my own (even the corrupted) perso.txt and changing the corresponding location into the unlock code might work, as the phoen could start up before. Another reason may be that by editing the perso.txt, the system might detect the action for example like using CRC, and if only perso.txt is edited, system detected inconsistency and will go into indefinite loop. If I were the developer and I am aware that perople crack the phone, I might using another file or check code to protect. In this case, "I turns out I can relock and unlock my phone as I see fit! I haven't tried, but I wouldn't be surprised if I could even lock my phone to a network other than Bell." might not work.
I guess that now even hardware unlock will not work, becaue when the phone start, it will read "perso.txt" and cannot find the right information. The only solution is push my original corrupted perso.txt back to the phone, but the question is how? Can you advise me what I should do now? SInce the phone does not start up at all, can I still flash the memory using Odin?
Thank you very much.
Cathy
Crap. I'm afraid that if your phone is now bootlooping with no access to recovery mode there is little to be done but to get it serviced or replaced.
No one has been able to flash EFS with Odin yet on our phones.
Also, your image attachment explaining what you attempted exactly is missing...
Look at the perso.txt files in a hex editor, there's no CRC or MD5 like thing anywhere in there. Of course it could be placed elsewhere, but it would be a first to have a booby-trapped phone OS...
I'll try locking my phone to another network within the next week for the heck of it.
Goodbye,
Darkshado
It's the format of the image. I changed to a different image format. You should be able to view the image in the first page now. Anyway, I posted it here again:
I'll try locking my phone to another network within the next week for the heck of it.
Click to expand...
Click to collapse
Let me know the result.
Thanks.
Cathy
SPnewb said:
Anyway, I posted it here again:
Click to expand...
Click to collapse
Please tell me: in what mode were you booted when you did the above?
Recovery?
Was the text blue or orange?
It's not normal that you had to use su. Otherwise your commands were correct starting with mount -o remount rw /
Darkshado said:
Please tell me: in what mode were you booted when you did the above?
Recovery?
Was the text blue or orange?
It's not normal that you had to use su. Otherwise your commands were correct starting with mount -o remount rw /
Click to expand...
Click to collapse
I thought that I booted in recovery mode since when I turned on the phone, I held Home key then press the power key, but when the phone start up there were only 4 or 5 choices in the recovery menu and except the one "reboot the system now", there were no other choices about reboot. I suspected that to choose "reboot the system now" will cause startup in normal mode. How do you start up the phone in recover mode?
I cannot recall teh color of the text, but I never see any orange text since I had the phone.
Thank you very much for your help. I'm going to get another Gio to unlock.
Found this on the Internet not my work, I now have a ROOTED fully working mobile running Ice Cream Sandwich, all credit goes to "TPSparky" for the development of the software.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
First of all, go to the settings - Developer options and check "USB debugging"
Your phone NEEDS to be recognized as an "ADB Device" in "Device Manager" on your pc, or else this won't work!
Download this file:
https://rapidshare.com/files/1767087805/4.0root.rar
Unpack the RAR.
Double click the TPSparkyRoot.bat
TAKE YOUR TIME!!! Your phone will re-boot several times, be patient!!! The procedure should look something like this:
Once it's successful, your phone should now have a "Superuser" app installed and it should be rooted
YOU ARE DOING THIS AT YOUR OWN RISK!!!!
Will that not stop the Dual Sim Function on hte mobile phone I presume we are on about the same product.
Is this the same product as yours.
http://www.freeyourmobile.com/produ...SIM-Phone-with-4.3inch-touch-screen-M306.html
Can you upload pics somewhere else? Imageshack links are dead.
freeyourmobile said:
Will that not stop the Dual Sim Function on hte mobile phone I presume we are on about the same product.
Is this the same product as yours.
http://www.freeyourmobile.com/produ...SIM-Phone-with-4.3inch-touch-screen-M306.html
Click to expand...
Click to collapse
IcedFlame said:
Can you upload pics somewhere else? Imageshack links are dead.
Click to expand...
Click to collapse
Hi freeyourmobile, Yes it looks the same as my BIRD V1277 mobile.
Hi IcedFlame, no problem, but can you tell me where I should re-upload the pictures to?
RESPECT...
freeyourmobile said:
Will that not stop the Dual Sim Function on hte mobile phone I presume we are on about the same product.
Is this the same product as yours.
http://www.freeyourmobile.com/produ...SIM-Phone-with-4.3inch-touch-screen-M306.html
Click to expand...
Click to collapse
Hi freeyourmobile, dual sims work just fine.
chunky2 said:
Hi IcedFlame, no problem, but can you tell me where I should re-upload the pictures to?
RESPECT...
Click to expand...
Click to collapse
imgur (.com)
tinypic (.com),
photobucket (.com)
postimage (.org)
Thanks :good:
Hi All, Re-uploaded images, this time from photobucket.
RESPECT....
Hello chunky2,
I've searched everywhere on the internet, but I did'nt find an answer.
Does this Phone have a built in compass?
weissgold said:
Hello chunky2,
I've searched everywhere on the internet, but I did'nt find an answer.
Does this Phone have a built in compass?
Click to expand...
Click to collapse
Hi, Not sure at the moment as I did a factory reset to clear out some old data and now its lock in recovery mode and I dont know how to get out of it.
Oh - I feel sorry for that.
Thanks Enelna from Hungary
V12 / v1277
I Think we should call this type of phone by its model which is V1277 and V12 respectively.
V12 looks perfectly the same as V1277 but it has MT6575 cpu which on the otherhand;
V1277 has MT6575 version 2 which they code named MT6577.
I think if we all agree with this we could identify/classify right away which phone was it whether its brand is either star, ulefone, bird or what not. Right?
By the way, Is anyone here got to try flashing a custom rom for this kind of phone like the MIUI? :fingers-crossed:
Rooting failed
I desperately need your help because i know that you are my life saver.
Model number: I9100
CPU: MTK6573
Android version: 4.0.9
Baseband version: I9100XXK13
Kernel version: 2.6.35.7-I9100
Build number: GT_I9100_01
Custom build version: 1341280728
After the first rebooting the output text is : cannot create /data/local.prop: permission denied.
I have tried it 3 times but with the same problems. Is your rooting program dedicated only for MTK 6577 because mine is MTK 6573. Do you have some clues on how to fix this. Thanks for your time in helping me out. :fingers-crossed:
possible solution
shaamt said:
I desperately need your help because i know that you are my life saver.
Model number: I9100
CPU: MTK6573
Android version: 4.0.9
Baseband version: I9100XXK13
Kernel version: 2.6.35.7-I9100
Build number: GT_I9100_01
Custom build version: 1341280728
After the first rebooting the output text is : cannot create /data/local.prop: permission denied.
I have tried it 3 times but with the same problems. Is your rooting program dedicated only for MTK 6577 because mine is MTK 6573. Do you have some clues on how to fix this. Thanks for your time in helping me out. :fingers-crossed:
Click to expand...
Click to collapse
I had a similar problem when trying to root my bird v1277 with Android 4.0.4
I ended up having to do the first steps of the script manually combining the phone's engineer menu and the adb shell.
The objective is to put the local.prop file, with ro.kernel.qemu=1 in it, in the /data directory so that the phone will run in emulater mode and give adb a root shell.
For this I created the local.prop file on my computer and pushed it to /data/local/tmp. Then I entered the engineer mode on my phone and searched around and found a place where you can type shell comands as the system user and copied the local.prop file to /data with busybox.
Hope this helps you
Instructions:
[email protected]$ adb push local.prop /data/local/tmp/local.prop
from PC: adb push busybox /data/local/tmp/busybox
from PC: adb shell chmod 0777 /data/local/tmp/busybox
Enter engineer mode by typing on the dialpad *#15963#* (this may vary from phone to phone so search around if this code doesn't work).
Goto CDS Information / Network Utility. Then run: /data/local/tmp/busybox cp /data/local/tmp/ocal.prop /data/local.prop
You can run: ls /data to confirm local.prop is there.
Reboot.
From here on you can either manually do the rest of the script or copy the rest of it to a new script and run it.
EDIT: amended to make it actually work (originally tred to use mv instead co pushing busybox and using cp.
EDIT2: amended adb chmod to adb shell chmod
Engineer Mode Help for MTK Device
For the last few days i've being trying to get the engineer mode code for my phone but failed until i hit "mtk engineer mode" through googling. There is an application called "Mobileuncle MTK Tools" that could excess the engineer mode of my mtk phone.
Mobileuncle MTK Tools is able to list down the menu in engineer mode but there are no CDS Information / Network Utility in the list. The menu listed are as follows:
Battery Log
TouchScreen
GPRS
Audio
Camera
WiFi
Bluetooth
NetworkInfo
AutoAnswer
YGPS
AGPS
EPO
VideoTelephony
Display
Memory
IO
Power
BaseBand
FM Receiver
SIMMeLock
SystemLog
De-Sense
CPU Freq Test
BandMode
I'm hoping that you may have some clues on the next step of solving this problems of mine. Thanks for your time in helping me and i appreciate it very much.
FrankVM said:
I had a similar problem when trying to root my bird v1277 with Android 4.0.4
I ended up having to do the first steps of the script manually combining the phone's engineer menu and the adb shell.
The objective is to put the local.prop file, with ro.kernel.qemu=1 in it, in the /data directory so that the phone will run in emulater mode and give adb a root shell.
For this I created the local.prop file on my computer and pushed it to /data/local/tmp. Then I entered the engineer mode on my phone and searched around and found a place where you can type shell comands as the system user and moved the local.prop file to /data
Hope this helps you
Instructions:
[email protected]$ adb push local.prop /data/local/tmp/local.prop
Enter engineer mode by typing on the dialpad *#15963#* (this may vary from phone to phone so search around if this code doesn't work).
Goto CDS Information / Network Utility. Then run: mv /data/local/tmp/local.prop /data/local.prop
You can run: ls /data to confirm local.prop is there.
Reboot.
From here on you can either manually do the rest of the script or copy the rest of it to a new script and run it.
Click to expand...
Click to collapse
Hello
I do have a V1277 as well, but I'm not that up to date on android manipulations. Thing is, that I went into the engineer mode, got to CDS info/network utility. Ran ls /data and saw the local.prop. (I'm not sure if I did it before the " Then run: mv /data/local/tmp/local.prop /data/local.prop" or not...sorry...I'm noob). And also I ran the
Anyways. Everything still gives me error messages telling me that access is denied. In fact the mv command as well.
I guess I may be missing the first line of your instructions. If you have time can you please explain it a bit more deeply? (I got the TPSparkyRoot thing, with adb.exe in it, tried running the command adb push from total commander and also adb terminal)
Thanks in advance
Hi everyone.
I recently bougth a micro d-hdmi to hdmi for my v1277 so that I could use it to connect to my lcd tv.
I connected it and it works. The only thing that bothers me is that it won't go on full screen on the tv. The picture is always on portrait and centered at the lcd which kind a disgusted me. I cannot find any options on the hdmi menu to turn it to fullscreen or have it default to landscape mode just to use the whole screen real state.
Does anybody knows howntp do it? Is there an app to solve this that is available on google play.
Help.
Sent from my V1277 using xda app-developers app
shaamt said:
For the last few days i've being trying to get the engineer mode code for my phone but failed until i hit "mtk engineer mode" through googling. There is an application called "Mobileuncle MTK Tools" that could excess the engineer mode of my mtk phone.
.
Click to expand...
Click to collapse
Try these ones *#*#3646633#*#* or *#3646633#
You can also check if SystemLog / NetLog has an operational shell command box
---------- Post added at 01:47 AM ---------- Previous post was at 01:27 AM ----------
Nekem8 said:
Hello
I do have a V1277 as well, but I'm not that up to date on android manipulations. Thing is, that I went into the engineer mode, got to CDS info/network utility. Ran ls /data and saw the local.prop. (I'm not sure if I did it before the " Then run: mv /data/local/tmp/local.prop /data/local.prop" or not...sorry...I'm noob). And also I ran the
Anyways. Everything still gives me error messages telling me that access is denied. In fact the mv command as well.
I guess I may be missing the first line of your instructions. If you have time can you please explain it a bit more deeply? (I got the TPSparkyRoot thing, with adb.exe in it, tried running the command adb push from total commander and also adb terminal)
Thanks in advance
Click to expand...
Click to collapse
ok run these commands and tell me what they say and I'll try and figure out what is going on:
id
ls -ld /data
cat /data/local.prop
All,
I have sucessfully rooted my v1277 using the same procedures on how to root lenovo p700.
[Guide] how to root lenovo p700http://forum.xda-developers.com/showthread.php?t=1774567
You can try it also and please READ, understand, follow and execute the procedures carefully then you will succeed.
Sent from my V1277 using xda app-developers app
Engineer Mode Help for MTK Device
FrankVM said:
Try these ones *#*#3646633#*#* or *#3646633#
You can also check if SystemLog / NetLog has an operational shell command box
---------- Post added at 01:47 AM ---------- Previous post was at 01:27 AM ----------
Click to expand...
Click to collapse
I think i've tried all the engineer code listed on forums/web but anyway i tried again the one given by you and the result are still the same.
SystemLog / NetLog has no operational shell command box. But anyway i've installed "Terminal Emulator" from google play.
From the shell command in the device are there any way for me to check any directory that allowed system user running in emulator mode and give adb a root shell.