Related
Standard disclaimer:
This tutorial is for people who have bricked their phone due to messing about with important files/partitions on their Nitro HD and found that it won't boot up afterward. Prior to attempting this, see if you can access your phone while booting with adb in order to fix your problem. The method used in this tutorial should only be used as a last resort. Don't hold me responsible if this method somehow makes your problem worse (although, really, how much worse can it get than a phone that won't boot?).
Now that's out of the way, let's move on...
Things you'll need:
1) ADB: You can get this in the Android Developer SDK <-Once installed, install platform-tools and add the directory containing ADB to your PATH. Alternately, you can just grab the ADB folder from your SuperOneClick folder, copy it to C:/, and then add that directory to your PATH. Hell, you could even run all the commands from wherever you have the ADB folder, just make sure you have it.
2) LG P930 drivers: http://s3.amazonaws.com/lgforum.com/resources/assets/680/original/LGP930.zip
3) LG Mobile Software Update Tool: http://csmg.lgmobile.com:9002/client/app/B2CAppSetup.exe
4) UpTestEX_mod2_marwin/KDZ_FW_UPD_EN: http://www.filesonic.com/file/2255759914/KDZ_FW_UPD_EN.zip
5) LG SU-640 firmware V10F_00.kdz: http://www.megaupload.com/?d=31XABWWJ
6) A method of rooting your phone. My preferred method is the latest SuperOneClick due to its simplicity. I won't really cover how to root your phone in this tutorial as it's covered elsewhere.
The following should only need to be downloaded if you were stupid like me and bricked your device before you made backups of the necessary partitions (This will be explained elsewhere, but needless to say it's as simple as switching the "if=" argument and "of=" argument in the dd commands toward the bottom):
7) boot.img: http://fileape.com/dl/OCowIxMnbDUMiPW6
8) recovery.img: http://fileape.com/dl/jFMlB8I3kkSMOYWN
9) firmware.img: http://fileape.com/dl/4gHHDDUhODLiJGHM
10) baseband.img: http://fileape.com/dl/TMsvdaKOa7VG4mVT
11) system.img: http://depositfiles.com/files/f0ke241ew
Alright, now that you have everything you need, let's move on to fixing your phone. I'm going to assume you are competent enough to install ADB (Android SDK or folder included to with SuperOneClick) to your system PATH. Go ahead and install the LG Mobile Software Tool and then install the drivers for LG P930 if you haven't already. Extract the KDZ_FW_EN.zip file. Note, in my case, I didn't have to do anything with the mfc42.dll or run WindowsEnabler as mentioned in similar tutorials elsewhere, but your mileage may vary.
Flashing the SU-640 rom:
1) Put your phone in download mode: power off the phone if it's not already, unplug the usb charging cable, and simultaneously hold the volume up button and plug the usb charging cable back in.
2) Open up UpTestEX_mod2_marwin. (If you know what you're doing, I've been told you can use KDZ_FW_UPD_EN as well, but since I didn't use it, I'm not going to discuss it)
3) Hit the folder icon next to the "Select kdz file" line and browse to the SU-640 v10f_00.kdz
4) Select "CSE web upgrade test", a new window with some options including an "Upgrade Start" button should appear.
5) Take a deep breath...there's no going back Press "Upgrade Start".
6) At this point in time another dialog box will appear asking what country and language the LG Mobile Upgrade tool should use. Since this guide is written in English, I assume you'll want to change it from Republic of Korea to All other countries and Korean to English. This affects the language that output messages are displayed in in the LG Update tool only, it doesn't affect anything with the rom (that'll be all Korean on initial startup lol).
7) The update tool will proceed to flash your phone, but it should never complete "normally" (mine never made it past 4% according to the tool and other users have reported similar behavior). However, your phone should reboot once or a couple of times and then just be sitting idle waiting for you to go through the setup wizard. At this point, just kill the LG update tool process in task manager, don't wait for it to complete because it won't.
Rooting your phone:
1) Now, on your phone you should see the standard Android startup wizard...in Korean. Hit the left button confirming you want to go through it, and on the next screen should be an option to switch the language to English. Ah, much better.
2) Go through the rest of the setup wizard if you want, but it's not necessary and you won't be able to set up accounts anyway unless you somehow have wifi.
3) Put the phone in USB debug mode and allow 3rd party sources. Don't freak out if the phone spontaneously reboots when you do this. It rebooted on me every single time I put it into debug mode for the first time (I flashed it several times lol).
4) Once it's rebooted itself, you should be able to connect in debug mode and connect via PC mode. Go ahead and root it using your preferred method. We're almost there!
Restoring Nitro HD partition images:
1) Open up a command prompt and navigate to the folder you saved your recovery images to (hopefully you put them in the same folder, it'll make your job easier)
2) Push all the image files to the phone's sdcard using the command:
Code:
adb push filename.img /sdcard
Alternately, you can just mount up your phone in My Computer and copy and paste the files over.
3) Now the real fun begins! Use the following commands:
Code:
adb shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
dd if=/sdcard/firmware.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p14
4) You won't be able to issue a reboot command, so just hold power down on your phone til it's off and hold the volume down button so that it comes back up in factory data reset mode. You will want to pull your sdcard at this time if you don't want your data erased.
5) Hit power twice and your phone should go through its reset process and (hopefully!) come back up in a working (and rooted) AT&T "stock" rom
If you have any issues, it's possible I've forgotten some steps, so I'll address them in this thread. At this point, I'd like to thank specific people who helped me immensely getting a working phone again: bytecode64, gordec, schwin97, belth219, sukudos, and ziiljuks. (If I've missed you, I'm sorry, I'm thankful to this entire forum!)
Original post:
So I was messing with fonts (actually trying to get the "look of disapproval" from Reddit to display) and substituted DroidSansFallback with a kannada font using Font Installer *Root*. Well, long story short, it was causing issues with other non-english characters so I tried to restore *all* my fonts using the "stock" option that comes with Font Installer.
When I rebooted, my phone only got to the LG Screen and that's as far as it has gotten since. I can't do anything with it, but I can get to Factory Data Reset mode and Download mode. I tried plugging the phone into my computer, but it doesn't appear to get far enough to mount the disk. Odin recognizes it's attached when I put it in download mode, but obviously Odin doesn't work with our phones.
Does anyone know if there will ever be hope for my phone or should I pursue getting a replacement? I'm actually completely shocked that simply replacing fonts has bricked my phone to the point where it doesn't even boot. This has seriously made me reconsider tinkering with Android at all until recovery methods are possible. I'm more than willing to be a guinea pig at this point until I try to send it in for a replacement (within the next few days probably).
Click to expand...
Click to collapse
do a factory data reset ? my phone gets stuck on LG logo too when i try to move all my apps to SD using titanium backup . factory data reset option resolves it however . see if that works ?
Unfortunately factory reset won't help in this case, the app messed up something in the system.
But as long as it gets to the point when you can use adb (it comes with SuperOneClick if you don't have it installed), then yes, there still a chance
To make it easier, can you contact the app's author and ask what exactly that app changes in the system, which files, so if necessary we can provide you with these files.
[email protected],
I have adb from SuperOneClick, how would I know if I can use adb?
Edit, I guess what I'm asking is do you have a quick guide to connecting a phone using adb and pushing files that you can hit me with a link to?
open CMD window and type:
adb devices
It should show you your phone.
adb devices
If that comes back with a device listed you can still save your system. Good luck...
Okay, I'm at work now, but I'll check when I get home. I do believe I tried that command and it didn't show any connected devices, but I can't remember if I only tried that while I had it in Download mode or also while I was trying to boot it. I'm keeping my fingers crossed lol.
You should searching for the file named KDZ_FW_UPD_EN,and install LGMobile Support Tool which can be downloaded on the LG Official website.And then you should download the *.kdz file that matches your phone.
Finally launch the KDZ_FW_UPD_EN flash your phone with the kdz file.
I use the tool bring my bricked device back.
Good luck.
belth219,
Problem is I can't find a .kdz for my P930. This seems like it'd be really easy to do otherwise.
Alright, I've created a tutorial in the first post describing how I unbricked my phone. I don't think it's quite back to "stock", but I don't think anybody who bricks their phone will care about that.
You have done the great job.Thanks for the baseband.img.It made my SU640 closer to PERFECT!EDGE enabled!!
Sent from my LG-SU640 using XDA App
I can't claim credit (or blame lol) for creating any of the images in this tutorial. Gordec is responsible for 3/5 including the baseband and I am so glad he responded quickly with each image correctly copied!
Sent from my LG-P930 using xda premium
my 4g lte isn't working.
My 4G wasn't working until I did a factory data reset (a second one, actually). Is it just your LTE that's not working or 4G in general?
Sent from my LG-P930 using xda premium
Will this give a version that has wifi and regular calling available right off the bat? I messed up my nitro to the point that i can only sometimes make phone calls and my market / browser won't function at all. Force close immediately.
Think I should try this as an option?
AT&T LG Nitro HD P930 is my make
Also, I use it on TMobiles prepaid network. I only get edge. I checked the bands, I think im right but wanted reassurance that edge is all i can get. Thx
To the best of my knowledge, prepaid service providers only allow maximum 4G, but vary by provider. No prepaid that i know of allows access to the LTE network, only on a post-paid plan.
If you have a AT&T unit unlocked for use on another carrier, then there's not much you can do in this case. sorry.
basically my att data itself.
att goofed up on my data plan. The thing is great thanks a lot!
csmg.lgmobile.com:9002/swdata/WEBSW/LGSU640/ASKTBK/V10i_00/V10i_00.kdz
I couldn't get the version with the f's in the original post to work. Will this one do? It's 460 mb.
nope because you cant root the ...i version thus making it worthless.
Sandpapers,
I'm uploading the V10f_00.kdz to megaupload right now. I'll update my tutorial as soon as it's done. Sorry I didn't do this sooner.
Sent from my LG-P930 using xda premium
Hello, I have a Glide manufactured in Nov 2011. I tried to unlocked by many companies, but all failed to get the unlock code, saying that it is unavailable. I see that it is no software unlock tool (as for the Galaxy S). I have it rooted but locked...
Any idea when the code can become available or another solution to have it unlocked?
Thanks
Sorry, forgot to mention: it is locked on Rogers, Canada
After ~90 days after the purchase, if you call AT&T and say that you're 'going overseas' they'll give you an unlock code.
I have successfully unlocked mine using a code from this site - www.cellunlocker.net.
I hope it fine to post the name in this forum.
nickexel said:
I have successfully unlocked mine using a code from this site - www.cellunlocker.net.
I hope it fine to post the name in this forum.
Click to expand...
Click to collapse
I already tried it. Also tried RogersCodes.ca, Theunlock.ca, OttawaPC.ca, MobileInCanada.com, cellunlock.net...
Think that I will have to pay 40$ to Samsung directly. I understood from OttawaPC.ca that it is a chance they can get it from them.
Unlocking!!
I have imported a phone for use in India. Bought it on eBay. Recieved the phone last week.
Still exploring for ways to unlock the phone freely.
Any Developers can help us out ??
Ready for any experiment.
Thanks!!
VinayS said:
I have imported a phone for use in India. Bought it on eBay. Recieved the phone last week.
Still exploring for ways to unlock the phone freely.
Any Developers can help us out ??
Ready for any experiment.
Thanks!!
Click to expand...
Click to collapse
Hi, is this phone available in india sorry to ask here but really i need the phone!!!!Also what is the price u purchased for? And how is the phone for use in india?? pls reply... Thanks a lot Vinay....
shoz_on4u said:
Hi, is this phone available in india sorry to ask here but really i need the phone!!!!Also what is the price u purchased for? And how is the phone for use in india?? pls reply... Thanks a lot Vinay....
Click to expand...
Click to collapse
No the phone will not be released outside US & Canada. I bought it on eBay (.com - US) and got it to India through Borederlinx (Postal Forwarding). Approx 27k including shipping and duty charges.
Phone is very good especially for QWERTY lovers..
Just curious, but does this work? https://market.android.com/details?id=com.helroz.galaxysunlock&hl=en
Or could it be modded to work?
Edit...maybe this would work. http://forum.xda-developers.com/showthread.php?t=761045
bobbylx said:
Just curious, but does this work? https://market.android.com/details?id=com.helroz.galaxysunlock&hl=en
Or could it be modded to work?
Edit...maybe this would work. http://forum.xda-developers.com/showthread.php?t=761045
Click to expand...
Click to collapse
First tried - it doesn't work. I used it on another Galaxy S i9000 without problem, but it doesn't work on Glide (i927R)
Second: tried, doesn't work as it stated in the first page, the file nv_data.bin is re-created at each boot. I have to take a look deeper for hidden files (starting with .). I will do a try probably later
After many tests, deleted files (starting with dot or not) at each re-boot it will recreate the files.
In the file nv.log I see something like "restoring from secondary backup"... Where it stores that secondary backup it I have no idea...
catalinu said:
Sorry, forgot to mention: it is locked on Rogers, Canada
Click to expand...
Click to collapse
Found one for 13 USD in eBay
http://www.ebay.com/itm/unlock-code-ROGERS-Samsung-Galaxy-S2-LTE-Galaxy-S-Glide-/120833869898
Vendor is "unlockgsm4u"
VinayS said:
Found one for 13 USD in eBay
http://www.ebay.com/itm/unlock-code-ROGERS-Samsung-Galaxy-S2-LTE-Galaxy-S-Glide-/120833869898
Vendor is "unlockgsm4u"
Click to expand...
Click to collapse
Yes, thanks, I tried, but it was unable to get it. Waiting to refunf from him...
Meantime I did an unlock (deleting file systems), but I got my original IMEI replaced by a generic one. But at least my phone works now (with that generic IMEI), so I have something until a code will be available...
Hey guys, I just won one of these phones but I am on t-mobile. Will this phone function correctly on their network, in terms of data functionality?
Sent from my HTC Vision using xda premium
eioous said:
Hey guys, I just won one of these phones but I am on t-mobile. Will this phone function correctly on their network, in terms of data functionality?
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
2g only most likely
Sent from my SAMSUNG-SGH-I927R using Tapatalk
catalinu said:
Yes, thanks, I tried, but it was unable to get it. Waiting to refunf from him...
Meantime I did an unlock (deleting file systems), but I got my original IMEI replaced by a generic one. But at least my phone works now (with that generic IMEI), so I have something until a code will be available...
Click to expand...
Click to collapse
Can you please guide me how to do it ?? (brief Description)
Can you go back to the original later ??
Thanks!!
VinayS said:
Can you please guide me how to do it ?? (brief Description)
Can you go back to the original later ??
Thanks!!
Click to expand...
Click to collapse
I suppose that yours is rooted. If not, you will have to root it first. See here: http://forum.xda-developers.com/showthread.php?t=1378082.
After root, use a file explorer.
I use the ES File Explorer downloaded from the market:
- Launch it
- Goto "Settings> File Settings". Be sure that Show hidden files is checked
- Also be sure is checked "Settings > Root Explorer"
- In "Settings > Home directory" write "/" (without the quotes)
explore the "efs" folder in the root
- move the following files in a backup folder somewhere to your internal SD card (you will need them if you want to restore later to original phone setup) : .nv_core.bak, .nv_core.bak.md5, .nv_data.bak, .nv_data.bak.md5, nv_data.bin, nv_data.bin.md5. Moving them they will be deleted from the efs folder (that's ok).
Reboot.
Now you will have it unlocked but with the generic IMEI.
It worked for me, hope it will work for you. Do it on your own risk. Don't blame me...
Later, if you want to return to the original (locked): copy all mentioned files from the backup folder to the "efs" folder and reboot.
followed above steps.
After the reboot -- there is no default screen asking for Unlock Code.
Instead my phone reboots just to homescreen.
When the sim attempts to Register to Network i get an error message.
"Phone not allowed MM#6" which i believe is because of the Generic IMEI.
When i attempt an call, i get the error message "Not Registered on Network"
Generic IMEI is 004999010640000/02
PS: Files /efs/nv_data.bin & nv.data.bin.md5 is getting created after every boot
---------- Post added at 11:01 PM ---------- Previous post was at 10:51 PM ----------
replaced the backed up files to its original folder.
Phone back to normal.
i,e -- Locked and asking for Network unlock key
Maybe you can Unlock by finding the unlock code in the bml3.bak file. Here are some steps forgot where i got from. HAVE TO BE rooted and used adb. Download a hex editior. I used 010 Editor. simple
(Place phone in debugging mode)
CMD program on computer
(mount to your folder where adb files located vie 'Cd ........'
(next are commands and just put them all in but make sure you read it through first!!)
adb shell
su
Cd
cd /dev/block
(then press enter)
---------------------------
TYPE THE FOLLOWING:
su
(then press enter, now your phone might ask for superuser permission, ALLOW it or say YES. You may not have to do this step, if it asked you before)
----------------------------
Now you will do one of the following below. Pay attention.
----------------------------
IF YOU HAVE AN EXTERNAL SD CARD TYPE THE FOLLOWING:
dd if=/dev/block/bml3 of=/sdcard/external_sd/bml3.bak
(then press enter)
IF YOU DON'T HAVE AN EXTERNAL SD CARD TYPE THE FOLLOWING:
dd if=/dev/block/bml3 of=/sdcard/bml3.bak
(then press enter)
Step 5) Now, find the file on your External SD card or Internal Storage depending on your situation and transfer it to your computer. If you don't know how to find the file. Plug your phone up and enable Mass Storage or Connect USB Storage. I won't baby you on how to find it. It should be somewhere on your phone or external SD card if you did step 4 correctly. Transfer that bml3.bak file to your computer. I recommend the desktop so will always know where it's at. You can delete it later if you want. So transfer it to somewhere on your computer.
Step 6) On your computer, open up 010 Hex Editor
Step 7) IMPORTANT: In 010 Hex Editor go to the Menus at the top and select VIEW then LINEFEEDS then SELECT CUSTOM, now SET YOUR BYTES TO "32" Nothing Less. If you don't do this, you won't find your unlock code. Do it.
Step 8) While you're in 010 Hex Editor, click Open and locate the bml3.bak file you created and open it. There will be a bunch of letters, numbers or whatever, ignore them for now.
(CREDIT TO FR0Z3N FOR CLARIFYING THE FOLLOWING 2 STEPS)
Step 9) Now press CTRL+F on your keyboard to search for a hex string. Now a box that says Find should pop up and when the search window pops up select "Hex bytes (h)" in the Type field by pushing the down arrow and then search for the following string below:
"FFFFFFFFFF0100000000" ALL TOGETHER WITH NO SPACES, 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 (not mine, someone else's computer)
tried above method
and also the original method mentioned at
http://forum.xda-developers.com/showthread.php?t=1176886
However no result.
I am not able to locate bml3 file.
Also when i explore through ES File Explorer there is no such file in the directory
I second what Vinay said. Using root browser I found that the dev/block directory on my phone contains files that are 2012 loop0 through2012 loop7, 2012 mmcblk1 and 2012 mmcblkOp1 through 11. It also has the subfolders platform and vold. Also all the files in the folder are listed as 0.00 bytes. Any suggestions on the usefulness of any of these files or other places to look for the bml3 file? I don't think the search function in root browser is comprehensive.
Hi Folks
I'm sick of all the bloat-ware on my Sony Arc (Purchased last Aug). I've recently had the phone unlocked and for the life of me, I can't root the damn thing. I've spent the last few days, trawling through all the helpful posts on this site (very informative and top notch stuff), but no matter what I try, the links on the posts are either no longer valid, the exploits have now been patched or my firmware is not listed.
Please, please, please, can someone give me a "Dummie's Guide" on how to root my phone.
My Arc is running Version : 2.3.4, Build Number : 4.0.2.A.0.62
Incidentally, just in case anyone is wondering, if I switch the phone off, hold down the menu key and connect to the USB, my phone displays the little blue led.
The closest I've came to successfully rooting (from my numerous attempts on here) was a simple click systems screen by DoomLord. My phone seemed to take to the program and then rebooted fine, but it still wasn't rooted. I've enabled USB Debugging and enabled unknown sources, etc.
This is driving me crazy. Can anyone help, please?
Dacvolvo said:
Hi Folks
I'm sick of all the bloat-ware on my Sony Arc (Purchased last Aug). I've recently had the phone unlocked and for the life of me, I can't root the damn thing. I've spent the last few days, trawling through all the helpful posts on this site (very informative and top notch stuff), but no matter what I try, the links on the posts are either no longer valid, the exploits have now been patched or my firmware is not listed.
Please, please, please, can someone give me a "Dummie's Guide" on how to root my phone.
My Arc is running Version : 2.3.4, Build Number : 4.0.2.A.0.62
Incidentally, just in case anyone is wondering, if I switch the phone off, hold down the menu key and connect to the USB, my phone displays the little blue led.
The closest I've came to successfully rooting (from my numerous attempts on here) was a simple click systems screen by DoomLord. My phone seemed to take to the program and then rebooted fine, but it still wasn't rooted. I've enabled USB Debugging and enabled unknown sources, etc.
This is driving me crazy. Can anyone help, please?
Click to expand...
Click to collapse
Flash this kernel
http://icxperia.com/doomlord/arc/ask/ARC-Advanced-Stock-v01-boot.img
and have fun..
HOW TO FLASH
1) Open the fastboot folder (generally android-sdk\platform-tools\) and copy the downloaded file there (and better if you rename it to boot.img)
2) Press SHIFT key and right click on any blank part of the explorer window
3) Click on "Open Command Window Here"
4) On the command window type
Code:
fastboot.exe flash boot <kernel name>.img
Have fun..
Hit Thanks if I helped you
Hi now.i.feel
Problems with that too - when I click on your above link, it downloads as a Zip File to my lap-top's desktop and I then try to unzip it, but all I get is a window popping up which says this file cannot be unzipped or opened as it is not a valid Zip File???
I've tried to simply replace it in the "Fast Boot" folder on my desk top (replacing DoomLord's Zip File in there entitled LT15i_4.0.1.A.0.283_Generic_Global_system.img), but now the Command Window won't open???
What am I doing wrong?
Try to use flashtool.
You can find a download link of flashtool on this thread http://forum.xda-developers.com/showthread.php?t=1000012
After this, is just a matter of conect your fone to PC and push Root button.
.62 can't be rooted, you would either have to downgrade like it looks you have or flash a custom kernel like above.
Chances are that zip is actually made from flashtool, download it put the zip in its folder and change the extension to .ftf.
Edit: sorry blonde moment, download any kernel that has cwm, use fastboot boot boot.IMG then use doomlords zergrush script, that will install su and busybox for you.
Sent from my LT18i using XDA
PS. .62 FW CAN BE ROOTED WITH UNLOCKED BOOTLOADER
downgrading, flashing kernel , flashing prerooted roms is a long process and unecessary. You loose your data too.
fastest way (no data loss)
1. Unlock bootloader
2. Download root that supports install via recovery. put it in SD
3. Install CWM
4. Boot into recovery
5. Choose apply update from SD
6. Choose the zip and install it
7. Start up the phone and update the Superuser and SU binary
Prerequisites:
- the phone should be connected to the computer via the USB cable provided in the commercial package;
- the Settings / Applications / Development / USB Debugging option should be enabled;
- the USB drivers for the S5690 phone should already be installed on the host computer.
Instructions:
0. download the S5690_unlock.zip file attached to this post;
1. unzip the S5690_unlock.zip archive in any place on your local hard drive;
2a. if you wish to UNLOCK the phone, execute the s5690_unlock.bat script as Administrator (right-click on the script file and select Run as Administrator);
2b. if you wish to RELOCK your phone, execute the s5690_relock.bat script as Administrator (right-click on the script file and select Run as Administrator);
3. follow the on-screen instructions and NEVER restart the phone by yourself.
WARNINGS:
- at the beginning the script waits for the sdcard to be mounted in your phone. If you have no sdcard at all, the script will wait forever! In this case you should disconnect the usb cable, turn off the phone, insert an already formatted microsd card, turn on the phone and finally reconnect the usb cable. The script will resume by itself when the card is detected;
- do not reboot the phone by yourself at any step! (neither in Recovery nor in standby); the script will do that automatically everytime it needs it;
- the ROOT.zip and UNROOT.zip files which are attached to the S5690_unlock.zip archive can be used ONLY on S5690/S5690L/S5690M phones. They won't work on other phone models;
- do not try to Relock a neverlocked phone, simply because the effects could be unpredictable (since there is no PLMN ID stored in the /dev/bml25 memory that would normally tell the phone on what network is it locked to);
- the scripts should also work on the S5690L and S5690M phone models. Please post some feedback here if you unlock/relock one of these models.
After the complete execution of the unlock/relock script, the tmp subdirectory will contain two files:
- bml25_before.bin -> backup of the original /dev/bml25 dump;
- bml25_unlocked.bin OR bml25_locked.bin -> dump of /dev/bml25 block device AFTER the unlock/relock operation.
What the script does:
1. installs root on the phone;
2. dumps the /dev/bml25 block device to a binary file;
3. changes the first two bytes of that file from 01 to 00 (for unlock) or viceversa (for relock);
4. writes back the binary file to the /dev/bml25 block device;
5. removes the root from the phone;
6. removes ROOT.zip and UNROOT.zip files from your sdcard.
If your phone is already rooted then skip the ROOT.zip installation step (from the Recovery menu) and just press any key in the script window to go to the next step.
After the execution of the script, the phone will be UNROOTED! If you want to keep the root, then you should either break the script (CTRL+C) when it reaches the INSTRUCTIONS FOR ROOT REMOVAL step or you should press any key in the script window without actually installing the UNROOT.zip from the Recovery menu.
There is no problem if you run the unlock script on an already unlocked phone or if you run the relock script on an already locked phone. In either of those cases, the phone will have the same status in the end as before running the script (either unlocked or locked). If you compare the bml25_before.bin and bml25_[un]locked.bin files you should have no differences.
I've already tested both unlock and relock scripts on several S5690 Xcovers and everything works OK.
UPDATES:
20130208 -> added support for the S5690R variant (Rogers Canada) - thanks to theshowman
Thanks a lot for the scripts! Excellent job. One question though: if my phone is already rooted (with your update.zip ) what should I (if possible) remove from the unlock script in order to perform strictly the steps for unlocking? Thank you in advance.
You don't have to remove anything. When the script displays the instructions for Root, just press any key in the script window (without actually following the instructions, i.e. without installing the ROOT.zip archive in the recovery menu) so the script goes directly to the next step (the unlocking step).
Also if you want to keep the Root in the end, do exactly the same at the Unrooting step.
The script does not verify if you really root / unroot the phone when it asks you to do so.
Regards
Thanks for your work.
Respect!
I tried the script but unfortunatelly it didn't work on my phone. In attach there is one print screen of the operation. My Xcover is locked on Orange RO. What could be the problem?
Copy the text from the cmd.exe screen and post it here or upload a full size print screen. The image resolution is too small and I can't understand what's the problem.
It seems that the "su -c" commands are executed directly under the cmd.exe and NOT within the adb shell prompt as they should be.
Post the WHOLE output of the script (from the beginning to the end). Do more consecutive print screens if necessary.
I tried again and you are absolutely right. The script is executed in cmd.exe, not in adb as it should. I didn't pay attention earlier. What can I do to force it to start in adb? The screenshot has been taken and saved at 1280x800 but it has been resized automatically at upload.
Upload the image(s) on imageshack and post only the links here. I need the whole output of the script.
http://imageshack.us/photo/my-images/846/unlocking.png/
First link. If neccessary, I will make/upload the missing screens from cmd.exe (the missing parts are the root and unroot ones, that I skiped by pressing a key without following instructions as my phone is rooted).
never mind
@PaulTT: I think I've found the problem. The double quotes were not interpreted correctly (probably due to different regional settings).
Please download again the zip archive from the first post (I've replaced it with a newer version) and try again.
Regards
Now it worked flawlessly! I have the 2 .bin files in temp file and the phone is working with any non Orange SIM. Thanks a lot for your help!
It is working, but i had to write every command in cmd, after i got su acces, thank you tlc76
Thanks !
it worked flawless ! many thanks
Worked like a charm. Thanx!.
Offtopic: no CFW so far for this phone? I'd like to try an 4.0.x ROM.
thanks for the post, do you think it will work with any career in american countries?
Problem
Hey tlc76,
first of all, i'd like to say thank you for the script, but unfortunately it doesn't work.
So i did everything in the description. (Turning on USB-Debugging, Inserting SD-Card, Installing the Drivers from Samsung)
But everytime i open the unlock.bat file, the screen turns white and the script doesn't do anything. The PC says, that adb doesn't work sometimes.
With the standard software from samsung or the adb in eclipse it functions quite well.
I would be thankful for some advice.
Thanks,
greendot_189
nice tool! my phone is more happy now
So, i eradicated the problem from yesterday, by running the script with a different version of adb, which was already on my harddisk.
There are good and bad news.
The good ones first:
It doesn't freeze and turn white anymore.
The bad ones:
The script waits endlessly searching for a SdCard. (It is inserted, and the phone works with it)
greez,
greendot
Edit:
It works now. Thank you very much!
Problem:
It didn't find the device. I installed Android SDK (with the USB Drivers) + JDK7 on another computer. Then everything worked fine.
Thanks!
If the script waits endlessly for the SdCard and the dots on the screen ARE NOT expanding, then you can try the following (in this particular order):
- stop the script (CTRL+C and Y) and restart it;
- unplug and replug the USB cable (with the script still running);
- reboot the host computer.
It seems that sometimes the
Code:
adb -d shell "mount"
command freezes and the script cannot advance. Normally every two seconds a new dot should be displayed:
Waiting for the SdCard to be mounted.................
so if you see only 4 dots which are NOT expanding
Waiting for the SdCard to be mounted....
then the script is waiting endlessly for the output of the mount command and is not actually running, so you can do one of the 3 actions described above.
The problem is most probably caused by the adb interface.
Hello, this is really weird. In fact, when I insert the SIM to my Note 2 N7100 and turn it on, it allows me to make emergency call, but I cannot use it to make any others and it doesn't show the carrier name (it shows Emergency call only). And when I try to use it to make normal phone calls, it says that I am not registered to a mobile network. I try to factory reset my phone, but the problem remains. I then try to remove the SIM card, and it says that I need to insert a SIM card (that means that it is not a hardware problem since it recognizes the card). I then try to go to the mobile network setting to try to connect to the network manually, it connects me but it shows me a warning which says that the mobile network service is not available (and the Emergency call only label remains). However, I am sure that this is not the problem of the card neither since when I insert the card to my Moto MB860, I can make calls as usual. So, what is the problem ??? It seems to me that the problem happens spontaneously since it works perfectly until yesterday. And all other wireless function works fine including wifi , Bluetooth and GPS and the only thing goes wrong is 3g and 2g.
Additional information:
ROM: Omega v.16
Carrier: Fido Canada (as you can see)
Thanks.
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Noob 1st post......have had similar problems with koodo CDN
Not gonna give such an in depth suggestion as above.....he's something simple to try.
I live in a dead zone and often my phone ( galaxyAce) will switch to no service. Even after refreshing and selecting network under settings, it says it's connected, but isn't. A simple apk that always fixes the problem for me is Network Signal Booster @ theplaystore
jabrif said:
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Click to expand...
Click to collapse
I tried a simple way which is format everything and flash another ROM but the problem remains.
TRS_80 said:
Noob 1st post......have had similar problems with koodo CDN
Not gonna give such an in depth suggestion as above.....he's something simple to try.
I live in a dead zone and often my phone ( galaxyAce) will switch to no service. Even after refreshing and selecting network under settings, it says it's connected, but isn't. A simple apk that always fixes the problem for me is Network Signal Booster @ theplaystore
Click to expand...
Click to collapse
I don't know that we are in the same situation since at home I often got a good signal and this happened to me only since yesterday.
jabrif said:
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Click to expand...
Click to collapse
Some updates;
- IMEI is checked.
- I do not have any efs backup
- nv_data.bin has been deleted and recreated
- trying to register for the firmware
- My phone is always rooted.
Dan Law 001 said:
Some updates;
- IMEI is checked.
- I do not have any efs backup
- nv_data.bin has been deleted and recreated
- trying to register for the firmware
- My phone is always rooted.
Click to expand...
Click to collapse
Results..??
Sent from my GT-I9001 using xda premium
jabrif said:
Results..??
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
I need to get the firmware first... since I already passed the download quota for today... need to wait until tomorrow...
Mmm... I heard that you mentioned clearing the EFS in your given procedure, but I do not think that I modified that folder... However, about few days ago, since I want to gain better control on the volume on my headphone remotes, I did modify the file called Generic.kl in system/usr/keylayout, but I restore it after since it didn't work. However, I don't think that this modification will trigger something in the efs folder since it has different directory. By the way, I did some research online and they say that the efs contains information about the carrier on the phone, so will there's a greater chance that the problem is caused by the possible modification on the efs than any other factor and will there also something else that possibly trigger the similar effects?
Sent from my GT-N7100 using xda premium
Still nothing