DO NOT USE THIS TOOL! Go here: http://forum.xda-developers.com/showpost.php?p=17148825&postcount=334
FIX:
Hi guys,
Sorry for your screenloop but one member has find/create a fix.
1. Make sure the phone is rooted
2. Connect the phone to your PC.
3. using adb shell type
su -
dd if=/sdcard/stl5.rfs of=/dev/block/stl5
4. Reset your phone
Second Fix
1. turn of device
2. press power button + home button
3. run Factory Reset
4. insert again your unlock code
Iam now searching with a team for a third fix.
We have an HEX-editor and 3 Android Developer and me as Android developer.
I hope that we can release soon a fix but you need to know that we dont have a bricked phone!
not working on my xperia neo
orly1001 said:
not working on my xperia neo
Click to expand...
Click to collapse
Sorry, sorry forgot to say that this is only for Galaxy Phones!
Hi,
I have a Samsung Galaxy Gio, and the app seems to run and do 'something'. Far from the 60 seconds of blank screen, maybe 2 seconds if even that.
The app does generate 4 lines of codes, as in the screenshot. Items that are unlocked on the phone are filled with zero's. So it appears that each code corresponds to one of the locks (simlock and 'SP'? lock).
After entering the code (with a valid sim) #7465625*638*# the dial field is empty again, this the point when to enter the 8 digit code?
Also, (and I will search some more on this subject later) is it possible that the SP code is the unfreeze code? I wonder about this because I accidentally eentered a wrong code with different network sim in it. I stupidly thought it was asking for the pin-code :S
Generally speaking, how often may you enter a unlock code, can you see the 'freeze' counter somewhere? Does it have some sort of cooldown?
I am searching for the freeze answers here now, so I may edit the post when I have found it
P.S. Is there more info about this app somewhere? I'm curious about how it finds the info to unlock the phone, as this series of phones doesn't have the 'efs' folder as the S series seem to have.
UPDATE!
Before running the program, the phone was pretty much 'factory resetted'. I ran the app, wrote down the code, but didn't use it for anything. I'm not sure when I checked the simlock status, but I had 1010 (binary) and I guess it must have been before running the app. I then did a nother factory reset, and ran the app again; just to see if it would generate the same codes. It did.
Since I wanted to search about for the unfreeze code, I checked the status of the lock again ... both where now gone!!
So not only does this app most likly generate the proper codes, it also appears to remove both locks!
I guess the app could have installed some backdoor or something but on a rooted phone, it works!
ol1ver said:
Hi,
I have a Samsung Galaxy Gio, and the app seems to run and do 'something'. Far from the 60 seconds of blank screen, maybe 2 seconds if even that.
The app does generate 4 lines of codes, as in the screenshot. Items that are unlocked on the phone are filled with zero's. So it appears that each code corresponds to one of the locks (simlock and 'SP'? lock).
After entering the code (with a valid sim) #7465625*638*# the dial field is empty again, this the point when to enter the 8 digit code?
Also, (and I will search some more on this subject later) is it possible that the SP code is the unfreeze code? I wonder about this because I accidentally eentered a wrong code with different network sim in it. I stupidly thought it was asking for the pin-code :S
Generally speaking, how often may you enter a unlock code, can you see the 'freeze' counter somewhere? Does it have some sort of cooldown?
I am searching for the freeze answers here now, so I may edit the post when I have found it
P.S. Is there more info about this app somewhere? I'm curious about how it finds the info to unlock the phone, as this series of phones doesn't have the 'efs' folder as the S series seem to have.
UPDATE!
Before running the program, the phone was pretty much 'factory resetted'. I ran the app, wrote down the code, but didn't use it for anything. I'm not sure when I checked the simlock status, but I had 1010 (binary) and I guess it must have been before running the app. I then did a nother factory reset, and ran the app again; just to see if it would generate the same codes. It did.
Since I wanted to search about for the unfreeze code, I checked the status of the lock again ... both where now gone!!
So not only does this app most likly generate the proper codes, it also appears to remove both locks!
I guess the app could have installed some backdoor or something but on a rooted phone, it works!
Click to expand...
Click to collapse
The App install nothing but it needs root because he need reading files in the android system files.
Fine to hear that this app works for you!
btw this guy makes also a free version for Galaxy S unlock
strunkie said:
The App install nothing but it needs root because he need reading files in the android system files.
Fine to hear that this app works for you!
btw this guy makes also a free version for Galaxy S unlock
Click to expand...
Click to collapse
Yeah, the problem is though, the app unlocked the phone and displayed the codes. I did not enter them. I did enter the code you listed above to get to the 'enter code now' screen so to say, but i never entered anything.
I guess it's all about trust I wonder though where he obtained the information on the phone, since the gio doesn't have nv_data or /efs. I'm still very happy though
Thank you for program
WARNING!
This app may actually brick/reset certain things. I found that my imei now actually reads 00000000 as wel as having all my mac adreses reset.
Actually, it seems my efs has been reset.
http://forum.xda-developers.com/showthread.php?t=828534
read more about this app.
ol1ver said:
WARNING!
This app may actually brick/reset certain things. I found that my imei now actually reads 00000000 as wel as having all my mac adreses reset.
Actually, it seems my efs has been reset.
http://forum.xda-developers.com/showthread.php?t=828534
read more about this app.
Click to expand...
Click to collapse
My IMEI isnt resetted and my mac isnt too.
You say in an earlier post that your phone was freezed? Because too much wrong unlock codes?this app dont write things he read only IMEI and generate code.
I hope that you can reset your IMEI ;-)
My phone was not frozen, I was affraid I might freeze it, so I didn't enter the key yet.
Basically I only ran it.
What happens on Gio's anyway is, that the App does a dd if=/dev/block/stl5 of=/sdcard/Galaxy_Ace_Unlock/stl5.rfs
READING, as the app is doing, from the 'efs' partition causes something to go wrong and it borkes the efs partition! That is why my phone was unlocked, as the lock is stored in the efs partition!!
ol1ver said:
My phone was not frozen, I was affraid I might freeze it, so I didn't enter the key yet.
Basically I only ran it.
What happens on Gio's anyway is, that the App does a dd if=/dev/block/stl5 of=/sdcard/Galaxy_Ace_Unlock/stl5.rfs
READING, as the app is doing, from the 'efs' partition causes something to go wrong and it borkes the efs partition! That is why my phone was unlocked, as the lock is stored in the efs partition!!
Click to expand...
Click to collapse
Specialy for you i reflash my phone back to GingerBread and i formatted my SD card.
After the flash i check my lockstatus and all things stays on OFF.
This tool need only files to read your IMEI and generate an unlock Code.
I think its safe and its works for me.
When you're afraid for freezing your phone i will advertise you to try an unlock service.
Thats not free but you got a guaranteed unlock tool.
Good luck
Thanks for this guide on how to unlock the Samsung GIO. I have already tried several methods to unlock using the apps provided on this forum to unlock Samsung Galaxy phones. However on my GIO the efs folder doesn't excist and therefore the methods I found didn't work. When I get home from work I'll try the unlock method as described above. If it works I'd be very happy . You'll hear from me.
Grat news... I tried the above things. I downloaded Galaxy_Ace_Unlock as apk, copied it onto my SDcard and installed it on my GIO using an app installer. I got 4 codes, from which 2 of them looked like working codes. I haven't tried the codes and rebooted my phone. I just wanted to make sure my phone wasn't broken after using the app and guess what, it did break my phone. Whenever I try to boot my phone it stucks @ flashing loadscreen. I can't get past the flashes, even when I attach my usb cable that's connected to my computer it won't get passen anything.
Help me out here, is there ANY way to reset my phone back to original factory settings?
I have no phone filesystem backup or whatever, I just ran the app as specified above and did NOT enter any code.
What can I do?
My phone also boot-loops!
I successfully rooted the phone and ran this application, it successfully read one code. I didn't do anything else then, didn't enter any code but instead I restarted the phone to change sim-card. But then the phone just boot-loops.
This is pretty much a direct KANG of my work with no thanks or anything.
Here is how its done for those who care.
this.os.writeBytes("dd if=/dev/block/stl5 of=/sdcard/Galaxy_Ace_Unlock/stl5.rfs\n");
this.os.flush();
this.os.writeBytes("cd /sdcard/Galaxy_Ace_Unlock/\n");
this.os.flush();
this.os.writeBytes("dd if=stl5.rfs of=code1.txt bs=1 skip=860170 count=8\n");
this.os.flush();
this.os.writeBytes("dd if=stl5.rfs of=code2.txt bs=1 skip=860202 count=8\n");
this.os.flush();
this.os.writeBytes("dd if=stl5.rfs of=code3.txt bs=1 skip=860234 count=8\n");
this.os.flush();
this.os.writeBytes("dd if=stl5.rfs of=code4.txt bs=1 skip=860266 count=8\n");
this.os.flush();
this.os.writeBytes("exit\n");
Click to expand...
Click to collapse
Hehe, so you think it's weird that I come here to ask how to solve the bootloop after using the APP? Sorry but is it also possible to restore back to Factory settings or anything or to restore a phone that is totally unusable after this? I can only load download mode and emergency mode now. I have searched this forum but can't find any help on how to restore back. I'd be up to restore back and then retry your method and thanks you greatly after removing my lock then . Don't understand me wrong, I'm only hoping you can also help me out after my phone is bricked atm. No hard feelings, it's my own fault after all for using someone else's code. I'm a programmer after all and I know how things can depend on device specific things .
Anyway thanks in advance, I'd like to hear from u soon!
This is what I did find on the forum:
using dd command on stl5 is bricking the phone: UNSAFE METHOD
Ok. For good comparison I attached both perso.txt: before and after unlock.
Perhaps that helps. My network was locked to 20404 and the unlock code is 61493638
and there is another code in the file: 92427358 but I don't know what that one does.
Perhaps it is better practise to follow this road for getting the codes:
- adb shell
- su
- dd if=/dev/block/stl5 of=/sdcard/stl5.rfs bs=4096
Then use winimage or similar to examine /sdcard/stl5.rfs as FAT16 image file.
Cheers
Click to expand...
Click to collapse
So reading this, could you find a method to unbrick ?
Thanks!
delete bull**** inside
rhcp0112345 said:
This is pretty much a direct KANG of my work with no thanks or anything.
Here is how its done for those who care.
Click to expand...
Click to collapse
I hope it is not a direct rip from your idea as it bricks phones
the thread linked earlier confirms it. dd-ing the unmount efs partition on a 'normally' running phone causes it to corrupt the efs partition.
Personally, I still have not rebooted my phone, until I have found a solution so that it is not stuck in a reboot loop. Be it as it may, I will remove my root and put it back to default settings and return it hopefully under warranty to reset the IMEI. The phone is just over a week old :S
So are there any ideas on how to restore a corrupted efs by using the DD method as described before? My phone is just 4 days old and already teared apart now . I'm looking on all fora I can find but nowhere there is an explanation to be found on how to reset all of this.
yvanruth said:
So are there any ideas on how to restore a corrupted efs by using the DD method as described before? My phone is just 4 days old and already teared apart now . I'm looking on all fora I can find but nowhere there is an explanation to be found on how to reset all of this.
Click to expand...
Click to collapse
IF you have backed up the efs partition, you can use odin. But since its nearly impossible to backup (may be in emergency boot mode, you actually can read) you actually brick your phone from performing said backup. I don't think the repair tool has been leaked yet (e.g. an efs generator of sorts) so it's pretty much impossible to do this at home. The only way to fix it is to have a certified repair technician fix it, as he has the tools (hopefully) to do this.
Lastly, this tool should be deleted from the firstpost. Helroz has already removed it from his site, since it does corrupt phones.
Related
Hi! all, i'm here for the first time, so i try to find some post for my problem but couldn't....
here's the thing, sometimes, after a call my screen stays black and do not react on any keys that i press... only led light under home key turn on.... i'm using .266 firmware and this happens two or three times on 10 calls.... when i update on .42 firmware, it happens all the time... only solution is to take out the battery and start it again...but i make like 50 calls a day so u can imagine what problem this present for me.....
can anyone help me, what to do? i try to test my proximity sensor on service menu, and it sometimes works ok, sometimes don't.... so what can i do to make this problem right?
Thx!
A friend of mine has the same problem with the Arc (not S).
Different FW tested...
Yep, ppl having this problem. I try to find solution everywhere on the internet but no luck foe that. That's why i'm writing here, hope someone can help.
If you have Root try this steps:
Open Root Explorer and open your Build.prop and add the following lines at the end of it.
Code:
ro.lge.proximity.delay=25
mot.proximity.delay=25
or use adb
Code:
adb remount
adb shell sed -i '$a\ro.lge.proximity.delay=25' /system/build.prop
adb shell sed -i '$a\mot.proximity.delay=25' /system/build.prop
Im new to this... So let me review all of this that u write here... Root? Do u mean open build.prop over astro and simply add this two lines of code under everything else??? If yes, what then sould i get from it?
And second, i dont know how to use adb so if the first step is the same like second one do i jave to do it?
Thx!
PhiberOptic1984 said:
Im new to this... So let me review all of this that u write here... Root? Do u mean open build.prop over astro and simply add this two lines of code under everything else??? If yes, what then sould i get from it?
And second, i dont know how to use adb so if the first step is the same like second one do i jave to do it?
Thx!
Click to expand...
Click to collapse
Start with this article http://forum.xda-developers.com/showthread.php?t=1133650 it explains you everything you need to know about Rooting, Booloader unlocked etc.
Root using DooMLoRD’s Easy Rooting Toolkit
It will not work with Astro because Build.prop is under system which you need Root access to open and edit the file. You need Root Explorer
Regarding ADB
[Guide] Setting up ADB [Windows]
[HOW-TO]Set up Android SDK/ADB/Fastboot on Ubuntu Linux
You only have to do this one or the other.
Let me know if you have any questions
Well my arc s is not rooted, it was but then i install a clean generic firmware from wotan. But never the less, i can access build.prop from astro... Ok thx for now, i'll try this tommorow and let u know whats going on.
Sent from my LT18i using XDA App
hi again.... well i try this but now when i test my proximity sensor it sais that it's ON always.... i'lll test with calls and report back.
Yup i started experiencing this on my arc since the past few days , but i have had .42 for more than a month now, i have no idea whats causing this issue though.
well try this as i did... i entered this two lines of code in my build.prop file and for now, after every call my screen comes back as it should..... so for now this think works... but let me test it for couple days more so that i can tell my final verdict.
but i have one question. what i did with this two lines, what i have changed?
Thx!
So did u try this bud? This morning, i hade the same problem with black screen again after one call, will see what will happend in future.
Sent from my LT18i using XDA App
i reflashed my phone with a data wipe, .58 firmware and also formatted my sd card. I have not faced a reboot since yesterday.
yer i was having the issue as well and added the two lines in build.prop, seems to be working so far but like the post above will test over a few days.
cheers
Brezzz
Did u putt command lines thrue astro like i said and did u root your phone? Because i just mod my build.prop file thrue astro and dave the changes but when i open build.prop again, i cant find two command lines, like u didn't even put them there
Sent from my LT18i using XDA App
It's probably a stupid question I'm gonna ask now since it seems to be possible to solve this when "adding a few lines of code in build.prop". But I'll ask anyway.
Do you have a protective case/film on the phone/display? If you do and this covers the sensor it might be the cause of this problem. Try to remove it and see if there's any difference.
Before you decide to root the phone I suggest you try to repair the software with the official flash tool (PC Companion) and if that does not help you send the phone to a repair centre for examination.
When you root a phone you loose the warranty so that's why I want you to try these things before doing that.
IF you decide to root, XDA developers is the place to be I think. A lot of experts around here.
Markus-SEAnswers said:
Do you have a protective case/film on the phone/display? If you do and this covers the sensor it might be the cause of this problem. Try to remove it and see if there's any difference.
Click to expand...
Click to collapse
Was my thought too.
I've had similar problems with exactly that.
Markus-SEAnswers said:
It's probably a stupid question I'm gonna ask now since it seems to be possible to solve this when "adding a few lines of code in build.prop". But I'll ask anyway.
Do you have a protective case/film on the phone/display? If you do and this covers the sensor it might be the cause of this problem. Try to remove it and see if there's any difference.
Before you decide to root the phone I suggest you try to repair the software with the official flash tool (PC Companion) and if that does not help you send the phone to a repair centre for examination.
When you root a phone you loose the warranty so that's why I want you to try these things before doing that.
IF you decide to root, XDA developers is the place to be I think. A lot of experts around here.
Click to expand...
Click to collapse
Ok, Lets say this again:
ROOT DOES NOT VOID YOUR WARRANTY!
unlocking your bootloader does.
if you have root, and reinstall original software, they are still going to give you your warranty because they can't see that you have rooted in the past.
ok so to close this topic... after everything, i sent my phone to SE, they tested it and contacted me saying that the proximity sensor error that i have is a factory defect and that they are sending me a brand new phone... so after all i think that anyone having this problem should simply return their phone and get a new one.
crazymister said:
Ok, Lets say this again:
ROOT DOES NOT VOID YOUR WARRANTY!
unlocking your bootloader does.
if you have root, and reinstall original software, they are still going to give you your warranty because they can't see that you have rooted in the past.
Click to expand...
Click to collapse
Also hardware factory defects are still covered by warranty when you unlock your bootloader.
iR¡[email protected]!* via Tapatalk
if you have a sticker on ur screen remove it .propably its covering the sensor.
***WARNING TO ALL***FLASHING ANY FIRMWARE CAN POTENTIALLY BRICK YOUR DEVICE
With that said, PLEASE use some precautionary measures to keep your device alive!
There are many threads out there about making a backup copy of the "/efs" folder. that folder contains all of your IMEI information that is NOT replaceable! There are several cases all over the web, about people who have lost that information causing them not to have service, leaving them with "generic" IMEI's and some with all "0's"
I am posting this to help prevent thoes who are unaware of the consequences that happen when the EFS information is lost!
Here I will post a few guides and informational threads here in XDA to help with this.
EFS Tool for Windows
Guide for the Galaxy S II
A Story From the Vibrant
From the Galaxy Note
I would also emphasize on making a nandroid backup of your complete system in recovery before starting to venture off onto any custom rom!
Here the folks at XDA have built a great community with a outstanding reputation to help one another advancing to the next level, also unlocking the extreme potential of our devices.
Be sure to "hit" the thanks button and when possible post a personal "Thanks" to the great devs and contributers we have here in XDA!
Feel free to add to this thread, any useful tips and such...
Thanks and God bless.
I have not yet confirmed this, but here are three links to what may be a way for those who have lost their EFS to repair it!
there are other guides on how to recreate the efs folder but these tools may enable us to insert the correct information!
http://forum.gsmhosting.com/vbb/f611/android-language-editor-android-language-project-1543222/
http://forum.xda-developers.com/showthread.php?t=1570342
Thanks to Pierreone, he has provided this link providing a individual from Poland that can repair your IMEI through TeamViewer for a small donation. This may be out only hope!!
http://forum.samdroid.net/f70/repair-imei-s2-5729/
Please if anyone tries these methods, report here to confirm success or failed!
Thanks.
I just copy and paste in my pc the EFS folder, thats enough? and how you can identify if there is a problem in the EFS?
lorddavid said:
I just copy and paste in my pc the EFS folder, thats enough? and how you can identify if there is a problem in the EFS?
Click to expand...
Click to collapse
That should be enough, but I would make backups in at least to other ways just to be safe, it's better to be safe than sorry. a single file can get corrupt without your knowledge! find a on-line file host like Google drive and that way if your pc was ever to go down it will always be there. Just don't loose your password!!!
to know that there is a problem, check the about phone section in status, the device will show your phone info, look for the IMEI! if it reads all 0's or a generic number starting with "04" and ending like "40000" you have problems! that is a unique serial number that identifies your individual phone!
I'm also not sure that if you were to use it to call an emergency hot line like "911" they would be able to locate you in time! that may not be true tho!
dbrannon79 said:
That should be enough, but I would make backups in at least to other ways just to be safe, it's better to be safe than sorry. a single file can get corrupt without your knowledge! find a on-line file host like Google drive and that way if your pc was ever to go down it will always be there. Just don't loose your password!!!
to know that there is a problem, check the about phone section in status, the device will show your phone info, look for the IMEI! if it reads all 0's or a generic number starting with "04" and ending like "40000" you have problems! that is a unique serial number that identifies your individual phone!
I'm also not sure that if you were to use it to call an emergency hot line like "911" they would be able to locate you in time! that may not be true tho!
Click to expand...
Click to collapse
mines is ok, has al ot of different numbers. Just a question, what ab out the serial number? mines has only 00000000000
lorddavid said:
mines is ok, has al ot of different numbers. Just a question, what ab out the serial number? mines has only 00000000000
Click to expand...
Click to collapse
the serial number so far is not a problem! it's the IMEI that you need to worry about! some refurbished phones and others that have flashed a custom rom will display an all "0's" serial no.
this is simply a helpful warning to make a backup before doing any modding! and finding ways for others to repair what is lost! if your phone is ok, just make a backup and your good!
One day we will figure out how to completely restore a lost efs and edit what is needed to get back to the norm!
Thanks to Pierreone, I added a link to a thread that looks promising and has success reports!!
Whew, I got lucky. I don't have an EFS backup and have flashed several custom ROMs, but I referenced About Phone against the label under the battery and my IMEI is still intact!
Could someone post what the Generic IMEI is so people can know whether their device is intact?
This is a a bigger problem than it sounds, because in some countries, changing the IMEI may be crime and land you jail time! If the IMEI under About Phone doesn't match the under-battery label, you could be in deep ****.
roothorick said:
Could someone post what the Generic IMEI is so people can know whether their device is intact?
Click to expand...
Click to collapse
It is 004999010640000.
Have it, because the unlock made my network disconnect every 10 seconds.
About the efs folder ?
First of all Thank You for the heads up... I'm finding out a lot about backing up the efs folder but not a lot of detail about what exactly is contained in it other than imei and serial... probably because it shouldn't be fooled with but I like to know how things work in detail... is there any detailed post or site where I can get a complete explanation about it ? Complete file list/tree? What else does it control ? Can it be edited ?
EFS Tool for Windows
Click to expand...
Click to collapse
This utility works fine. Just wanted to mention 2 things that you need to set before running this successfully:
Settings -> developer options -> android debugging enabled
Settings ->Developer options-> Root access -> set to 'apps and adb'
I followed the guide from the Galaxy S2 forum, and after the first command:
busybox cp -a /efs /sdcard/efs/
Every line says "can't preserve ownership of..." and "operation not permitted"
Am I doing this right?
I did get an efs folder on my internal storage which is about 5mb in size after that command anyway
The rest of the guide, all of the other commands went through ok.
Holy crap, I wish I had listened to this warning! After flashing a great new rom and getting it 98% set up the way I like it I was deleting some junk apps the marketplace had auto installed, one of them (for wi-fi hotspots I think) was to blame and must have toasted my IMEI.
I thought, oh I'll just restore my CWM backup from an older setup - md5 error can't restore. DOH! After spending most of two days hunting for solutions (none of them linked in this thread worked, except I did get to where I could place calls with a generic IMEI but no data or text). I finally was able to recalculate the md5 manually and restore my old backup, which then got stuck at boot logo, then I flashed a new ROM and the IMEI still isn't back! After much reading I have come to understand NANDROID BACKUPS DO NOT TOUCH THE EFS. That is one thing that that I didn't understand, and the reason I thought I was safe. Please update the OP to state that so more people like me will listen to your advice.
Backup your EFS! Thanks for the warning
Sent from my SGH-I927 using xda app-developers app
Victory!!!! :victory:
I was so close to just paying at http://sam.123unlock.nl/ and using their service to re-write my IMEI (because they show an unlock video using our phone and their software), but I kept digging in XDA and trying everything I could find. I tried the SIII IMEI editor, NV reader-writer, manually restoring the .nv_data.bin, mobiletech videos backup script...blah blah blah. I tried restoring CWM backups, flashing back to stock everything, using kies, I was trying everything! During all this I at times had no IMEI, all 000s, and a generic #, each of which provided different levels of services. I considered keeping the generic IMEI which AT&T didn't seem to mind but then I finally stumbled on a solution.
In reading the http://forum.xda-developers.com/showthread.php?t=859914 post which is linked to in the "A Story From the Vibrant" in the OP I tried the abd EFS tar command and executed it on another Captivate Glide I have that had some water damage but is mostly still functional thinking I could overwrite the entire good EFS of that phone to my good phone with the hosed IMEI. I used AROMA http://forum.xda-developers.com/showthread.php?t=1646108 and deleted the EFS from CWM (I felt like adb and terminal weren't effective since the OS was still awake) and then restored from my working EFS tar, then wrote on top of that the first backup of the hosed EFS I had from before I started messing with it (thinking I'd try that before trying just the other phone's E)FS.
When I rebooted I had the correct serial and IMEI back for the phone! It is now working 100%
I flash alot from to rom, if i use the aroma file manager n save the entire efs folder on my external drive ,if i were to ever run into problems can i go bak to aroma file manager n just restore the efs folder and make everythinfunction again ?
Some guys say yes, others say use the tar command to preserve file permissions. I backed it up both ways. When I used aroma I deleted the files and replaced them rather than over-writing the corrupted ones and it worked fine for me.
Sent from my SGH-I927 using xda app-developers app
So I just got my captivate glide bought it used and I followed thegreatones instructions to get CM 10.1 using the factory image to get it to 4.X then flashing the rom.. and after i flashed CM 10.1 my imei was gone. SIGH. I don't have a backup, which of the paid services works the best? who has tried them?
I managed to make EFS Pro work but the glide is not listed and I don't see any partition to backup. Am I missing something?
Timelord83 said:
So I just got my captivate glide bought it used and I followed thegreatones instructions to get CM 10.1 using the factory image to get it to 4.X then flashing the rom.. and after i flashed CM 10.1 my imei was gone. SIGH. I don't have a backup, which of the paid services works the best? who has tried them?
Click to expand...
Click to collapse
I haven't tried any but I would first give AT&T a call. They can probably assist you. And I believe there's a 14 day return date, I believe AT&T only checks the physical aspects of the phone.
jzamoras said:
I managed to make EFS Pro work but the glide is not listed and I don't see any partition to backup. Am I missing something?
Click to expand...
Click to collapse
It worked for others. Check to make sure you have all Glide drivers installed and reread the OP please Thanks!
Finally I used an older EFS Tool and it worked!
---
Is the baseband showing as Unknown instead of I927UCsomething? That we may be able to fix. Otherwise you're kinda screwed :/
The fact the codes don't work suggests that we don't have a Qualcomm radio. Since it's usually inside the SoC that doesn't surprise me.
This may work: http://gsmforum7.blogspot.com/2012/04/samsung-android-repair-efs-imei-repair.html
idulkoan said:
i have recently bought the samsung captivate glide off of ebay. I live in the UK so i am not on att. I updated my glide to ics, installed cwm recovery, and rooted it. The phone is unlocked so it worked great. I was using a giffgaff sim (o2 network), and everythign worked great, except mms. I found an app that fixes mms, but when I ranit it deleted all my apns and froze the phone. I rebooted the phone and now there is no imei. I do not have an efs backup. After i found that my service is gone and that my imei is gone, i backed up the damaged efs and started reading up and editing it. I finally got my imei changed, but its still incorrect and my service was still not working. I restored my corrupted efs folder back and now it still has no imei. How can i repair my imei? i looked all over the internet, and was going to try qpst but i cant get this phone in diag mode for the com port. What should i do?
ps this exact thing happened to me last year when i lived in america on metro pcs, but to fix it I went into the metro pcs store and they flashed my imei back.
Click to expand...
Click to collapse
Read this http://forum.xda-developers.com/showthread.php?t=2019540 and see the post no. 2. It has link to a site run by an individual, see if that helps http://www.cvxcvx.pl/?lang=en as it has i927 in his list.
doesnt work..
---
Have you tried installing a GB ROM, especially stock?
idulkoan said:
i dont have any .bak files in the efs.. :/
The imei editor (generator) only lets me put in 14 characters, but my imei is 15 characters long..
the "Android Language Editor with Android Language Project" requires the purchased version in order to use the imei settings
Click to expand...
Click to collapse
You should have looked on the other link i gave in my post above. anyway check this out http://www.cvxcvx.pl/podstrona-0/check-when-repair-no-problem?lang=en.
For 10 euros, the guy promises to fix it 99% of the cases where the imei no is either shown as all zero's or ending with '640000' . Other cases are also mentioned.
---
efs question
---
idulkoan said:
if i backup my efs on a spare android phone that works but I do not use, and restore it to my glide, wil that work?
[like will my imei be changed to the other phones so that my service will work? and for people that think my phone is stolen, it isnt and my original imei is not blocked especially because im using this phone in a different country (england instead of att in america)]
i dont mind a different imei, as long as i kan get the service back on this phone. I am going to 2 repair shops today to see if they can restore my imei to my original one.
Click to expand...
Click to collapse
The other phone should be samsung glide i927 and not just any other phone. But then i think you'll have 2 phones with same imei no.s which is illegal in many countries and is termed as cloning. And i'm not sure but XDA probably discourages these kind of discussions.
Let us know what was the outcome of going to the repair shops and best of luck. :good:
FIXED
---
idulkoan said:
i dont have any .bak files in the efs.. :/
Click to expand...
Click to collapse
Did you check with ls -a in adb? dotfiles don't show up in most file managers.
fixed.. sort of
---
roothorick said:
Did you check with ls -a in adb? dotfiles don't show up in most file managers.
Click to expand...
Click to collapse
---
idulkoan said:
ok so this problem is still here but randomly. If i reboot the phone, sometimes the imei doesnt show up and i have to turn off turn back on, and then if the imei isnt there i have to take out the battery and wait a minute then turn it back on and then its fixed. SO the problem is here still [randomly happens, usually when not shutting down properly (like holding power button till the screen jsut shuts off) or when rebooting the phone a couple times with the build in reboot option] but the solution is to reboot onces or twice to bring it back to fix it.
Click to expand...
Click to collapse
I had the same problem in India and it keeps increasing till you cant use the phone. I discussed it with some repair shops and they were quite clear that its a software issue and needs "box" to fix it along with Samsung software. Even the samsung service center recommended getting it flashed properly and it will start working. Unfortunately, cant locate a local repair shop here which can flash this.
Suggest u get it properly fixed now, if possible from an official Samsung service center.
oh ok
---
idulkoan said:
oh ok thanks for the info so basically this will keep happening until it stops working? cause it does still happen, but I kn fix it by taking out the battery and putting the battery back in..
Click to expand...
Click to collapse
Atleast thats what happened to my phone. Taking out battery would get the phone working, but the problem would surface after some time.
I flashed a lot of roms and the best rom I used was Osimod GB (with regards to this problem only) as it used to work for 2-3 days before giving the problem. Also, typically, it would happen a bit after you make or get a call. You can observe for sometime and see if its the same problem and if it is growing.
idulkoan said:
whats the full adb command? ahha
Click to expand...
Click to collapse
"adb shell ls -a /efs" should show everything. May need to be root, I'll have to check.
---
mrigancb said:
I had the same problem in India and it keeps increasing till you cant use the phone. I discussed it with some repair shops and they were quite clear that its a software issue and needs "box" to fix it along with Samsung software. Even the samsung service center recommended getting it flashed properly and it will start working. Unfortunately, cant locate a local repair shop here which can flash this.
Suggest u get it properly fixed now, if possible from an official Samsung service center.
Click to expand...
Click to collapse
I have similar problem with my galaxy s2 and posted in the forum
http://forum.xda-developers.com/showthread.php?t=2061816
Did you get your phone fixed ? if so can you let me know the steps .
thanks
---
I'm sorry if this thread is out there but I looked and I may be an idiot or I'm the first with this problem, I guess we'll find out.
I have a Galaxy S3 on Rogers network.
This all began when trying to unlock my phone. I was not having any luck so one of the steps was using the command *2767*3855# to reset my phone. This did not help with being able to unlock my phone.
I have tried every unlocking method under the sun and none of the # or * commands work, not even *2767*3855# anymore. Which is weird because I have used that command to restore the phone once.
I thought me rooting my phone may have been the issue so I restored the factory firmware and still nothing. I have wiped my device using the option in the phones settings menu and also by holding Volume up + Menu + Power button. Still none of the other commands work when dialed into my device.
The only command I get to work is *#06# for the IMEI number.
Can anyone help me figure out why these commands aren't working as I would really like this phone unlocked. The one that boggles me is *2767*3855# not working although I am aware this function will not unlock my phone there is no reason it should not be wiping the device when punched into the device.
Please help,
Thanks!
I too have this problem!
bertuzzmo said:
I'm sorry if this thread is out there but I looked and I may be an idiot or I'm the first with this problem, I guess we'll find out.
I have a Galaxy S3 on Rogers network.
This all began when trying to unlock my phone. I was not having any luck so one of the steps was using the command *2767*3855# to reset my phone. This did not help with being able to unlock my phone.
I have tried every unlocking method under the sun and none of the # or * commands work, not even *2767*3855# anymore. Which is weird because I have used that command to restore the phone once.
I thought me rooting my phone may have been the issue so I restored the factory firmware and still nothing. I have wiped my device using the option in the phones settings menu and also by holding Volume up + Menu + Power button. Still none of the other commands work when dialed into my device.
The only command I get to work is *#06# for the IMEI number.
Can anyone help me figure out why these commands aren't working as I would really like this phone unlocked. The one that boggles me is *2767*3855# not working although I am aware this function will not unlock my phone there is no reason it should not be wiping the device when punched into the device.
Please help,
Thanks!
Click to expand...
Click to collapse
I rooted my phone via odin and recently unrooted via odin. Im on a recove. I tried doing this command to resolve an internal memory problem I've been having. Im running Att GN2 with 4.2.1. Ive tried a factory reset and a cache data wipe and still nothing. If anyone has another way to format the internal memory of the phone (because i want all my gigs back(apparently, i only have 11 or so it says)).
bertuzzmo said:
I'm sorry if this thread is out there but I looked and I may be an idiot or I'm the first with this problem, I guess we'll find out.
I have a Galaxy S3 on Rogers network.
This all began when trying to unlock my phone. I was not having any luck so one of the steps was using the command *2767*3855# to reset my phone. This did not help with being able to unlock my phone.
I have tried every unlocking method under the sun and none of the # or * commands work, not even *2767*3855# anymore. Which is weird because I have used that command to restore the phone once.
I thought me rooting my phone may have been the issue so I restored the factory firmware and still nothing. I have wiped my device using the option in the phones settings menu and also by holding Volume up + Menu + Power button. Still none of the other commands work when dialed into my device.
The only command I get to work is *#06# for the IMEI number.
Can anyone help me figure out why these commands aren't working as I would really like this phone unlocked. The one that boggles me is *2767*3855# not working although I am aware this function will not unlock my phone there is no reason it should not be wiping the device when punched into the device.
Please help,
Thanks!
Click to expand...
Click to collapse
Unlocking your phone will require the unlock code (which you can get from App in the market or from your carrier *paid*). From there, you insert another SIM than your carrier's and it will prompt ask for the unlocking code. Enter it and enjoy.
Juan-Solo said:
I rooted my phone via odin and recently unrooted via odin. Im on a recove. I tried doing this command to resolve an internal memory problem I've been having. Im running Att GN2 with 4.2.1. Ive tried a factory reset and a cache data wipe and still nothing. If anyone has another way to format the internal memory of the phone (because i want all my gigs back(apparently, i only have 11 or so it says)).
Click to expand...
Click to collapse
11.95GB is what you are supposed to have.
Sent from my SAMSUNG-SGH-I747 using xda premium
BWolf56 said:
Unlocking your phone will require the unlock code (which you can get from App in the market or from your carrier *paid*). From there, you insert another SIM than your carrier's and it will prompt ask for the unlocking code. Enter it and enjoy.
Click to expand...
Click to collapse
Thanks for the reply.
I have the unlock code and I've tried that method of unlocking my phone, which did not work, therefore I am trying other methods which the commands do not work or prompt anything. This is why I wondering if anyone has any experience with these prompts not working.
Thanks!
Bump
~12GB is what you should get (even though the phone itself says 16GB)
most phone provider companies never actually list the actual size that you'll get (so far i only see Google does it)
bertuzzmo said:
Thanks for the reply.
I have the unlock code and I've tried that method of unlocking my phone, which did not work, therefore I am trying other methods which the commands do not work or prompt anything. This is why I wondering if anyone has any experience with these prompts not working.
Thanks!
Click to expand...
Click to collapse
What happens when you insert another sim card? Does it ask you for the code?
Also, you gotta change your APN to the new carrier's.
BWolf56 said:
What happens when you insert another sim card? Does it ask you for the code?
Also, you gotta change your APN to the new carrier's.
Click to expand...
Click to collapse
Ya try this. From what I remember the only way to unlock the US variant is to insert a different carrier sim...
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Im looking for advice as my brothers LG G4 is no longer working. My brother passed away in May of this year and no one is aware of the draw pattern to unlock the phone. I attempted to use an online tool called Dr.Fone to take the passcode off, however this didnt work. The firmware update screen froze and nothing would move so i removed the battery to restart it. On restarting it, the screen began to change colour and the touchscreen wouldnt work, although it takes you to the draw pattern screen. Im at a loss with what to do, as I cant loose the data on the phone and a hard reset isnt an option. If theres an suggestions id be grateful.
You cant do anything then. Android isnt as stupid as it used to be
Scobie93 said:
Im looking for advice as my brothers LG G4 is no longer working. My brother passed away in May of this year and no one is aware of the draw pattern to unlock the phone. I attempted to use an online tool called Dr.Fone to take the passcode off, however this didnt work. The firmware update screen froze and nothing would move so i removed the battery to restart it. On restarting it, the screen began to change colour and the touchscreen wouldnt work, although it takes you to the draw pattern screen. Im at a loss with what to do, as I cant loose the data on the phone and a hard reset isnt an option. If theres an suggestions id be grateful.
Click to expand...
Click to collapse
Backing up your data can be done with DLM backup (check my sig)!
Removing the screen lock is possible in TWRP if you have it.. If not its maybe possible in download mode but this requires Linux or best FWUL (check my sig) as here all tools needed already included!
Depending on what you have i can share details but first i need to know :
Do you have TWRP and so your device is unlocked?
Do you have Linux AND do you have the knowledge to use it? If you can't answer BOTH with "yes" download FWUL first.
sfX
Il be honest that i have absolutely no idea what they are. Im not technically savvy when it comes to phones and things of the sort.
As far as i can explain, the touchscreen wont work and anytime you press the home button the screen lights up, but you cant actually use it. Im not sure if the term bricked applies as it sounds potentially along those lines?
Id probably need a step by step to sort it without getting to the point of being unable to salvage it.
steadfasterX said:
Backing up your data can be done with DLM backup (check my sig)!
Removing the screen lock is possible in TWRP if you have it.. If not its maybe possible in download mode but this requires Linux or best FWUL (check my sig) as here all tools needed already included!
Depending on what you have i can share details but first i need to know :
Do you have TWRP and so your device is unlocked?
Do you have Linux AND do you have the knowledge to use it? If you can't answer BOTH with "yes" download FWUL first.
sfX
Click to expand...
Click to collapse
With your DLM back up, i could transfer all the data onto a USB, wipe the phone then reapply it all? Would that be a possibilty?
Scobie93 said:
With your DLM back up, i could transfer all the data onto a USB, wipe the phone then reapply it all? Would that be a possibilty?
Click to expand...
Click to collapse
In theory yes. It depends on the firmware and device model if it works or not.. Some firmwares are more locked down then others but for 8 of 10 it works.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
In theory yes. It depends on the firmware and device model if it works or not.. Some firmwares are more locked down then others but for 8 of 10 it works.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
The model of the phone is a LG-H815, however im unsure of the firmware.
Scobie93 said:
The model of the phone is a LG-H815, however im unsure of the firmware.
Click to expand...
Click to collapse
Your chances are good then. What I meant was you have to try as there are no guarantees...
Sent from my LG-H815 using XDA Labs