Related
Thanks to the good folks here i've just upgraded my Galaxy S to the leaked JPM firmware. So far so good - much faster than JPK I was on.
However - I'm having problems with the Appbrain Fast Web Installer and seem to have found out that it's due to the android device ID being the same because we're all using the same ROM (or something) (http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=798644)
So.... How can I find out what my Device ID was/should be and how can I then change it to be "correct".
Any help much appreciated. Seems it might be a common issue....
Have you tried checking whether your IMEI changed after flashing? Type *#06# and if your IMEI starts with 0049... (I think...) then you need to do what almost everyone has been doing since JPC ... follow the instructions from here or some other threads from around here.
If your IMEI is fine, then I have no idea...
nonreviad said:
Have you tried checking whether your IMEI changed after flashing? Type *#06# and if your IMEI starts with 0049... (I think...) then you need to do what almost everyone has been doing since JPC ... follow the instructions from here or some other threads from around here.
If your IMEI is fine, then I have no idea...
Click to expand...
Click to collapse
Thanks for info - checked my IMEI and it seems to be fine - i.e. the one i registered with my insurance with (starts 3547)
I've read the thread you linked to trying to figure out what's what but I can't see anywhere how to find out what my product code is/was/should be or how I can change it. I've seen stuff about backing stuff up (nv_data?) but I'm not aware of having changed these.
All I've done to my phone - flashed JMX and now JPM and applied SuperOneClickv1.4-ShortFuse root. Will that have changed my product code?
I'm a bit lost with this one.
Use sgs toolbox to see the crc code.
Sometimes you got the right code in the backup file.
Just do a backup of all file on a safe place. The remove the 2 original file. Restart.
You need to be rooted for this.
Sent from my GT-I9000 using XDA App
DamianGto said:
Use sgs toolbox to see the crc code.
Sometimes you got the right code in the backup file.
Just do a backup of all file on a safe place. The remove the 2 original file. Restart.
You need to be rooted for this.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
A bit of info that might help(?):
I loaded up SGS toolbox and pressed ""check product code" it says:
---------------------
Got root access
Copied nv_data files...
nv_data.bin could not be read!
No backup .nv_data.bak found!
-----------------------------------------
I'm guessing that's bad news?!
Under Firmware Info it says:
------------------------------
PDA: I9000XXJPM
PHONE: I9000XXJPM
CSC: I9000OXAJPM
Build Info: 2010. 10
--------------------------------------
When I tap CSC selection it says: "USSD code running" and then "UNKNOWN APPLICATION"
When you say to backup 2 original files - i'm guessing it looks like I don't have those. Is there another way I can check or is it definite from the above. If I don't have the original files am I stuck? Can I get them from anywhere else? Are they default to a phone by region or carrier (my phone is from O2 in the UK and is the 8gb version)
If you say delete the original files (which aren't there it seems) - am I right in thinking this will them make the phone auto-generate new ones? (I really have no idea what these files are for or what they do).
What's the next thing to try? Can I get hold of the missing files from somewhere? Do I even need them? And how do I restore the Product ID (if it's changed!)?
Thanks
Have you checked the path manually for them?
If they are not there you are in deep water.
Its you personal data for the phone and you can't use others file.
Search this forum for help about this.
I can only give you a advice what i would do if i had that problem.
I would flash a original firmware that is lower than its on kies.
Then i would upgrade thought kies.
Then i would check if the crc code is there and right.
If it still wrong then i guess i would make the phone look like it was out of the box and return it.
If the code is right i would make a backup(full) and on this files( to my external sdcard).
Then i would upgrade to jpm/jp6.
Sent from my GT-I9000 using XDA App
DamianGto said:
Have you checked the path manually for them?
If they are not there you are in deep water.
Its you personal data for the phone and you can't use others file.
Search this forum for help about this.
I can only give you a advice what i would do if i had that problem.
I would flash a original firmware that is lower than its on kies.
Then i would upgrade thought kies.
Then i would check if the crc code is there and right.
If it still wrong then i guess i would make the phone look like it was out of the box and return it.
If the code is right i would make a backup(full) and on this files( to my external sdcard).
Then i would upgrade to jpm/jp6.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Hi - thanks for reply
I've checked the /efs folder with Root Explorer and it seems i've got:
.android - folder
.nv2.bak
.nv2.bak.md5
.nv_data.bak
.nv_data.bak.md5
.nv_state
/imei - folder
nv_data.bin
nv_data.bin.md5
Now i'm guessing this is good? is it all in the right folder?
Just to clarify - I've never messed with this folder - I've only ever flashed with Kies and cleared the cache and restored factory settings with recovery. I've also formatted internal and external memory card.
So are these files my original files? How can I tell? Are these included with the Rom's I've flashed? (JPK and now JPM)
I've copied the entire efs folder to a safe place - is there anything else I should backup also incase I can't restore it?
SGS toolbox still says:
---------------------
Got root access
Copied nv_data files...
nv_data.bin could not be read!
No backup .nv_data.bak found!
-----------------------------------------
Why can't SGS toolbox read the files?
Many Thanks
Maybe I am not following this thread correctly, but your last post deals with IMEI and unlock data. Your first post said you needed to change your deviceID. You even link to the Captivate thread that discusses the problem AND in that captivate thread is a link to change Device ID - http://forum.xda-developers.com/showpost.php?p=8604909&postcount=3550
review that post as it tells you where your device ID is located (it is not in the nv_data.bin file). Also, in the captivate thread, one person said he just made one up and that worked for him.
If you mess up with nv_data.bin you will mess up your IMEI and any unlock the phone has - so I caution you be careful.
I made a thread with the solution
http://forum.xda-developers.com/showthread.php?t=815503
This should work.
alsheron said:
Hi - thanks for reply
I've checked the /efs folder with Root Explorer and it seems i've got:
.android - folder
.nv2.bak
.nv2.bak.md5
.nv_data.bak
.nv_data.bak.md5
.nv_state
/imei - folder
nv_data.bin
nv_data.bin.md5
Now i'm guessing this is good? is it all in the right folder?
Just to clarify - I've never messed with this folder - I've only ever flashed with Kies and cleared the cache and restored factory settings with recovery. I've also formatted internal and external memory card.
So are these files my original files? How can I tell? Are these included with the Rom's I've flashed? (JPK and now JPM)
I've copied the entire efs folder to a safe place - is there anything else I should backup also incase I can't restore it?
SGS toolbox still says:
---------------------
Got root access
Copied nv_data files...
nv_data.bin could not be read!
No backup .nv_data.bak found!
-----------------------------------------
Why can't SGS toolbox read the files?
Many Thanks
Click to expand...
Click to collapse
I had the same problem.
I installed Busybox from the App Market and it solved the problem.
abumuqaatil said:
I had the same problem.
I installed Busybox from the App Market and it solved the problem.
Click to expand...
Click to collapse
thanks...had same problem and that solved it
Ok I have this problem. Some how the imei number programmed in the phone got erased. I think thats why my sim never register to any network or let me change any settings. But whenever I flash the kdz my imei is right in the logs but when i use *#06# it dont display my imei its blank just in the setting. I cant make calls or select a band when I use *#*#4636#*#* So now im looking for a way to program my imei to my phone. I know how to do this with cdma phones but not GSM. So anyone know of any info It will be greatly appreciated. I think this happen because of the previous owner flashed the NV
Anyone who is experienced in fixing this around? I've got the same issue as well.
I think I found a solution. I found an post about someone who had a similar problem here (http://forum.xda-developers.com/showthread.php?t=1089039) I searched my phone for an /efs folder but haven't found anything. So either this is my problem or I don't know where to look. Do anyone have a efs backup?
calcappone said:
I think I found a solution. I found an post about someone who had a similar problem here (http://forum.xda-developers.com/showthread.php?t=1089039) I searched my phone for an /efs folder but haven't found anything. So either this is my problem or I don't know where to look. Do anyone have a efs backup?
Click to expand...
Click to collapse
Yeah. That's for a Samsung Phone. I know this because I used to develop for one.
I have searched extensively for an /efs partition and have failed so far.
Sent from my Samsung Galaxy S II
Yeah I know but I was thinking that the basic file system for all androids are alike. Lestat you said you searched the phone for an \efs partition and couldn't find it? I may be wrong. Is there any way to get to the nv items on the phone? That way I could try to program my imei. I wish i could just use qxdm. Is there any software likethat for gsm phones?
Hmm. I currently don't know. I can try looking.
No IMEI
Hi, have you checked your APNs? I had the exact same problem before, my problem was solved by putting back the 3 default APNs that came on the phone and adding my carriers APN at last.
Whenever I try to change the APN it says "reorganizing internal process" then kicks me out. the same thing happens when i try to dial a number. I tried flashing kdz v10e, v10k, v20a, v20c, v21a. I tried flashing .bin for v10e and v10k. I tried flashing BB for froyo and gingerbread. I tried APN manager to make an apn to no avail. I tried using getRIL to make sure my radio was correct and it wouldn't detect my phone. Says it's unsupported but right below that it has P925 on the list of supported phones. So now I back to stock trying to get into the efs to program the right IMEI. One thing though when I flashed v21a it would let me into the apn settings. One I input the settings and try to save them then it say "Reorganizing Internal Process" and kicks me out. I would then reboot and try to go back to the apn but it's not saved. On another note v21a will not let me into the apn settings at all unless I *#*#4636#*#* and gointo phone info an change MPDP to disabled
i got the same issue... no IMEI, any new idea?
i have attempted to search for a solution to your problem and found a guide that might be able to help you? i dont understand it much but maybe it will help?
http://wireshock.com/guide-on-restoring-imei-number-after-losing-the-original-part7backup-file-using-gfree-on-mytouch-4g/
IMEI
If any have acces to fully working phone and it is rooted, know how to use ADB and have 2.3.5 android please do this (bold lines):
adb shell
$ su
su
# dd if=/dev/block/platform/mmci-omap-hs.1/by-name/nv1 of=/sdcard/nv1.img
dd if=/dev/block/platform/mmci-omap-hs.1/by-name/nv1 of=/sdcard/nv1.img
256+0 records in
256+0 records out
131072 bytes transferred in 0.024 secs (5461333 bytes/sec)
# dd if=/dev/block/platform/mmci-omap-hs.1/by-name/nv2 of=/sdcard/nv2.img
dd if=/dev/block/platform/mmci-omap-hs.1/by-name/nv2 of=/sdcard/nv2.img
256+0 records in
256+0 records out
131072 bytes transferred in 0.024 secs (5461333 bytes/sec)
It will give you 2 files on sdcard (nv2.img and nv1.img) and please send me files to compare with my broken files. Maybe I can find solution to fix this IMEI sh*t.
On mine nv2 partition IMEI is strored in 3 places and nv1 partition seems empty.
I will send you email in PM to send me files. Dont post files in public, becouse IMEI is stored i them.
Dont use tutorial in previus post becouse it will brick your phone. On partition 7 in our phone is system not EFS, NV or whatever is called. NV1 is partition 2 and NV2 is partition 3 on our phones.
You can open and edit nv1.img and nv2.img in hex editor.
Sorry for bad english!
iodak said:
If any have acces to fully working phone and it is rooted, know how to use ADB and have 2.3.5 android please do this (bold lines):
adb shell
$ su
su
# dd if=/dev/block/platform/mmci-omap-hs.1/by-name/nv1 of=/sdcard/nv1.img
dd if=/dev/block/platform/mmci-omap-hs.1/by-name/nv1 of=/sdcard/nv1.img
256+0 records in
256+0 records out
131072 bytes transferred in 0.024 secs (5461333 bytes/sec)
# dd if=/dev/block/platform/mmci-omap-hs.1/by-name/nv2 of=/sdcard/nv2.img
dd if=/dev/block/platform/mmci-omap-hs.1/by-name/nv2 of=/sdcard/nv2.img
256+0 records in
256+0 records out
131072 bytes transferred in 0.024 secs (5461333 bytes/sec)
It will give you 2 files on sdcard (nv2.img and nv1.img) and please send me files to compare with my broken files. Maybe I can find solution to fix this IMEI sh*t.
On mine nv2 partition IMEI is strored in 3 places and nv1 partition seems empty.
I will send you email in PM to send me files. Dont post files in public, becouse IMEI is stored i them.
Dont use tutorial in previus post becouse it will brick your phone. On partition 7 in our phone is system not EFS, NV or whatever is called. NV1 is partition 2 and NV2 is partition 3 on our phones.
You can open and edit nv1.img and nv2.img in hex editor.
Sorry for bad english!
Click to expand...
Click to collapse
i tried that procedure with a working imei thrill from a friend and mine, and restored the "good" imei back to mine with no luck
update: i tried returning to stock froyo and to my surprise it had the imei the first time it booted, after a couple minutes. Then when I put my sim on and turned it onagain the imei was gone
I just flashed the P920´s v10k via Lg Software updater, made the wipes (all of them in the 3e recovery) and the imei is back there.. don´t know if it´s temporary or permanent, but i´m able to make calls, and have rebooted twice, i lost the 3G 850mhz but hey got a useful phone for now!
You can get the v10k HERE
New update... after third reboot lost the IMEI again... but hey that´s a start
Another update: flashed v20p using the .kdz and now i´m on official ginger with IMEI... let´s see how long it sticks...
[[ Cold ]] said:
update: i tried returning to stock froyo and to my surprise it had the imei the first time it booted, after a couple minutes. Then when I put my sim on and turned it onagain the imei was gone
I just flashed the P920´s v10k via Lg Software updater, made the wipes (all of them in the 3e recovery) and the imei is back there.. don´t know if it´s temporary or permanent, but i´m able to make calls, and have rebooted twice, i lost the 3G 850mhz but hey got a useful phone for now!
You can get the v10k HERE
New update... after third reboot lost the IMEI again... but hey that´s a start
Another update: flashed v20p using the .kdz and now i´m on official ginger with IMEI... let´s see how long it sticks...
Click to expand...
Click to collapse
What software do you use to flash .kdz files? Do you use .dll files ?
Okay, so I have looked into the other posts about people not having anything in their /efs folder. So I bought an i957r from Rogers. Rooted it and have su and busybox installed. Astro shows that my /efs folder is empty. My IMEI is perfectly fine, all of my data services work, and I am sure root is installed. When I run the adb shell to pull my nv_data.bin, it tells me the file doesn't exist, and when I pull it from the sdcard, it is an empty file. Any ideas as to why that folder would be empty?
Also on a side note, if I was to factory reset it, with root installed, would it damage my device? The only reason I want to reset it is to get the /efs folder. Any help that can be given would be greatly appreciated. Thanks so much!!
Astro is lying to you. Astro also shows /efs to be empty on my ATT device, but if i get a root shell, it is NOT empty.
This is due to the default permissions on the /efs folder:
Code:
# ls -l | grep -i efs
drwxrwx--x system radio 2012-06-15 10:04 efs
Note the lack of read permissions for other users (not user system or member of group radio). If you change the permissions on the folder, say via:
Code:
# chmod 775 /efs
# ls -l | grep -i efs
drwxrwxr-x system radio 2012-06-15 10:04 efs
Astro would then should you the files in that folder. But that's probably not the best way to handle it... Just deal with the efs files from a root shell, not a user-level file browser like Astro.
Interestingly enough, my Tab 8.9, which has been through a hackathon and a half, doesn't have nv_data.bin file.. anywhere. I do have a /efs/redata.bin file, though.
I wonder if the lack of nv_data.bin is related to why my tab started displaying "Search Network Manually" when I turn LTE on, and sometimes randomly whines about an invalid SIM even though it then immediately connects and works like normal... I've been trying to root cause that change for a while, although it seems to have no negative effects. Probably leaving some whacky log entries on the carrier side of things, though... FWTW.
Do you all actually have an nv_data.bin in /efs?
Also, before someone else flames you... this thread does not belong in this forum... Use the main forum for non-development issues
Well thank you for not making me feel completely stupid, I wasn't really sure where to put it. Can you tell me how to move it? So I'm not "that guy"?
But as far as what I have, in the /efs folder, I have redata.bin, but no nv_data.bin and a couple of other files and folders.
I downloaded Root Explorer and it was able to show me what was in that folder. I also searched using that for nv_data... didn't find anything
But while I am already in the wrong forum, can you tell me if doing a factory reset will hurt my device? Also, if I don't have an nv_data.bin file, I can't unlock it, can I? Just hoping you could help. Thanks so much!
I could be wrong, but I believe only mods can move threads. Never tried, and don't see anything obvious.. Ah well, no big deal.
I wonder if these devices use something different than nv_data.bin? I mean, we both seem to get working LTE service without it, right? Other various posts found via gooogle show several folks that claim their corruption and/or lack of nv_data.bin results in no service.
I highly doubt a factory reset will do any damage, "factory reset" basically means wiping data and cache, which is quite safe. Factory reset doesn't touch /system, /boot, etc. The assumption is that the user never had access to modify /system, so wiping the cache and user data partitions results in a "factory fresh" condition.
No so much after you've haxxored up all sorts of stuff.
If you are looking to get back to as close to stock as possible, you are probably best off starting with the factory ODIN tarball, which I believe is still available on sammobile. It contains the boot, system, recovery, cache and two modem partitions (although it doesn't appear to contain an EFS image).
It would be interesting to see if a virgin device actually has this file. My suspicious is we are both missing this file because it never existed on the i957 in the first place. I believe another vector would be used to unlock the device, instead of the nv_data hack.
Futhermore, I believe the nv in nv_data means nvidia, who makes the Tegra chipset and associated radio modems which are used in devices based on Tegra. The i957 is based on the MSM8660 SOC, a Qualcomm part, which is an entirely different beast than the Tegra solution. Pretty much everything I can find online about hacking up nv_data.bin covers devices that are NOT based on Qualcomm SOCs, which in recent times is most devices not destined for LTE on AT&T or other similar carriers (Rogers/Bell/Telus).
The captivate had the nv data file and it was on a hummingbird chip which was the precursor to exynos
Sent from my SAMSUNG-SGH-I727 using xda premium
I have a rooted GT-I8190 with Android version 4.1.2 and Baseband version I8190DXAMA2. If this also helps, I live in Indonesia and purchased my phone from Indonesia too.
I'm facing some problems with files...
1) I can't seem to modify any files inside my phone. I can't clear app data/cache, I can't delete files from My Files app, app data won't update, and photos taken from camera won't save. I can modify files with Root Browser and from TWRP Recovery though.
I think this is related to...
2) Me being not able to open Gallery. Every time I opened it, it says "Not enough space. Delete unnecessary files..." which is weird because I have 1.74 GB space remaining in my internal SD and 777 MB remaining in my external SD.
Steps I've tried:
- Rebooting
- Factory Reset
- Unroot and reroot
But my problems still persist.
I've spent hours searching in XDA and in Google, but none of them worked.
I've found somewhere that it relates to my phone's corrupt firmware though (I flashed a firmware when I softbricked my phone). Is it true? If it's true, where and how can I find the correct firmware for my phone?
Any suggestions and answers are appreciated. Thanks!
bump
donjar said:
I have a rooted GT-I8190 with Android version 4.1.2.
Steps I've tried:
- Rebooting
- Factory Reset
- Unroot and reroot
But my problems still persist.
I've spent hours searching in XDA and in Google, but none of them worked.
I've found somewhere that it relates to my phone's corrupt firmware though (I flashed a firmware when I softbricked my phone). Is it true? If it's true, where and how can I find the correct firmware for my phone?
Any suggestions and answers are appreciated. Thanks!
Click to expand...
Click to collapse
Try to update Google Play Store
Try to install "Root External 2 Internal" By CODLAB from the Play Store.
Try to change the primary install location using the adb commands
Windows:
adb devices
adb shell pm set-install-location 2
adb shell pm get-install-location
hope this helps
urs
xero
I am puzzled and confused about the /efs folder.
I have a P1000 which was running a January nightly build of CM10; this worked, including the telephone function, sort of...
I then upgraded to Android 4.2.2, CM10.1 from 21030728 - which works much better BUT it lost all the telephone capabilities (it shows Baseband version unknown). After much digging I think understood correctly that I must have ruined my /efs folder.
I do have previous /efs folder copies (not made with any particular tool) on my external SD card but even using something like Root Browser or Root File Manager to copy an old version (in which the telephone worked) to write over the existing /efs folder I do not regain access to the phone function.
My questions are these, if anyone can explain to me what is happening for I would like to understand:
1. I tried to delete the existing /efs folder (using Root Browser and Root File Manager) but it does not delete: why?
2. I am clearly doing something wrong when trying to copy an old version in order to write over the existing one (which does not work): what and why and how do I get around this to make it work?
3. How does Android protect the /efs folder and is there a way to get round this?
i have read far and wide but so much seems to be contradictory or inconsistent. Or is there a place where all is explained (and if so where?).
Thank you in advance.
Hello,
I had the same problem. I have restocked my Galaxy Tab but it did not work. I have tried to flash the modem with odin and it works! After reboot my Galaxy Tab i have Signal and the imei is restored. I have root my Galaxy Tab again and flash CM10.1 and it works prefect. I have now CM10.1 on my tab and i can use phone functions and the imei is restored. Have you tried to restock it and flash the modem with odin?
Good Luck!
Besides restocking or flashing a modem, you can try and restore your EFS backup with EFS Professional... Try to give it a shot.