Related
I'm on Valhalla-Final with it's stock Kernel. I had a Bad flash which resulted in my IMEI becoming 0000000000000.
My phone is working fine right now (I can't download Swype Beta. I get can't install Android Emulator Notific) on Valhalla-Final AND I have my (Pre flash) efs folder backed up on my external sdcard and my laptop.
My back up is different than my current efs folder. It has my IMEI #, ect, in it. It is Good.
I have researched and read this thread:
http://forum.xda-developers.com/showthread.php?p=12807550
But a fix for me isn't in it.
What do I do??.. I could delete my Null efs folder and paste my back up then reboot??..
I DON"T WANT TO MESS THIS UP. To me the only thing worse than this problem is a Hard Brick.
Any Advise will be Appreciated.
I ALWAYS Give Thanks!
First take out the battery for 10mins and see if the IMEI is restored after you power it back on.
Sent from my SGH-T959V using XDA App
I've tried that twice already and I'm doing it again right now at your suggestion..
right before the battery pull I copy, pasted and rebooted my backed up efs folder to the efs folder WITHOUT deleting my current and 000000000 efs folder. That did not work.
FIXED!!!
I deleted my 00000000000 IMEI efs folder and copy and pasted my pre-flash efs back up using Root Explorer (Paid version) Then Powered down and Powered up.
My IMEI AND Wi-Fi MAC address are both restored!!..
I guess I knew what to do but wanted confirmation.. I don't have a contract and paid $500 for my phone so Mod with Caution..
If I have Your/THE answer for you I will ALWAYS give it even if I think you should know it or find it on your own.. Probably because I can only help on a few things so I'm proud to and not burnt out helping Members LOL...
Thank God I came here when there was no CWM or ROMS and it was so Dead People were EAGER to Help me. Because I knew NOTHING.. This is my first time Rooting and hacking Andriod. My first Forum..
I Love this Phone, It's Devs, Themers, Modders and Members!!
THANK YOU ALL!
Now that my IMEI is restored I just downloaded and installed Swype Beta...
If you get a " Can't Install Android Emulator" Notification check that your IMEI is not 00000000000..
Menu> Settings> About Phone> Status> IMEI.. check Wi-Fi MAC address TO
LESSON LEARNT (for everyone): Please make sure to do a complete EFS backup before you do anything or you will end up like me!!!
So yeah I flashed Deodex_LF2_Cwm.zip yesterday, trying to deodex my DDFL2.
And following that I experienced total loss of mobile signal, baseband, IMEI, IMEI SV, and phone (*#1234#).
And I haven't been seeing this kinda thing to come, I did not back up EFS. (Yeah brilliant me)
So I tried a few of these:
[GUIDE] Recover your IMEI in 9 steps
Repair IMEI using EFS Pro
Reflashing from latona.pit then XXKPE; for a few times
Flashing stock ROM for Malaysia region (Froyo and GB)
Flashing various Modem.tar (DDLE1, DXKP7, etc) via Odin3 at different ROM levels (XXKPE, DDLF2, even CM10A4)
Restoring Nandroid backup from other SL user (Thanks Rich'Dawg')
But nothing worked so far yet.
Now that I checked the /efs folder is empty and there is only a folder named lost+found.
Some websites said about fixing IMEI for small fees but in cases of blank IMEI (*#06#), chances are only 30%.
And my last resort would be getting it replaced in Samsung service centre or any repair shop, which I suspect that the motherboard would be more expensive than some simple new Android phones.
Leaving this forum for the moment as to collect more money to get a new phone . . . :crying:
Lastly, thanks for all the input. Greatly appreciated.
Do you able to call anyone. ? if yes then no need to change anything. if no then you should search for imei solution on xda. there is some tutorial for fake imei.
nicsptl said:
Do you able to call anyone. ? if yes then no need to change anything. if no then you should search for imei solution on xda. there is some tutorial for fake imei.
Click to expand...
Click to collapse
Nope. I totally lost signal and mobile network.
cheeyeen said:
Nope. I totally lost signal and mobile network.
Click to expand...
Click to collapse
do you flash b4 CM10? if yes, search your sd card and External sd card for the installation backup of efs folder
chongns said:
do you flash b4 CM10? if yes, search your sd card and External sd card for the installation backup of efs folder
Click to expand...
Click to collapse
Yes I did but nope I couldn't find. sucks.
It is in a folder name backup
Sent from my GT-I9003 using Tapatalk 2
chongns said:
It is in a folder name backup
Sent from my GT-I9003 using Tapatalk 2
Click to expand...
Click to collapse
Sad enough this folder does not exist in my phone....
Have you had any idea if Samsung would fix this in Malaysia..? Or how much would that be.
I spent like 10 hours trying to look for a solution but >"<
cheeyeen said:
Sad enough this folder does not exist in my phone....
Have you had any idea if Samsung would fix this in Malaysia..? Or how much would that be.
I spent like 10 hours trying to look for a solution but >"<
Click to expand...
Click to collapse
no idea of how much it should be.
but a idea to help you,
1st idea:
go in recovery and fix permission.
2nd idea:
you said you flash Deodex LF2 in CWM, it should not touch efs folder. so, very high change of your nv_data.bin file backup still good.
OK. use any file browser look in the efs folder, see if the below file still exiting, (they are hidden file)
check on the file date. is the date older than the date you flash the zip, if yes, this is the one original from your phone.
the file name start with a dot
.nv_data.bak - ( this is your imei backup file) copy and rename the .nv_data.bak to nv_data.bin and set permission and change owner.
.nv_data.bak.md5 - (delete this file first)
chongns said:
no idea of how much it should be.
but a idea to help you,
1st idea:
go in recovery and fix permission.
2nd idea:
you said you flash Deodex LF2 in CWM, it should not touch efs folder. so, very high change of your nv_data.bin file backup still good.
OK. use any file browser look in the efs folder, see if the below file still exiting, (they are hidden file)
check on the file date. is the date older than the date you flash the zip, if yes, this is the one original from your phone.
the file name start with a dot
.nv_data.bak - ( this is your imei backup file) copy and rename the .nv_data.bak to nv_data.bin and set permission and change owner.
.nv_data.bak.md5 - (delete this file first)
Click to expand...
Click to collapse
Fixed permission.
I found one .nv_data.bak dated year 1994 , which I think came in when I was trying to flash some efs fixes i found in XDA.
Without much hope I tried what you said, but still nothing happened. IMEI blank, baseband unknown.
Is it possible to have the mobile phone repair shop with RIFF or Jtag or some box thingy to have this done?
i think you must change the motherboard
cheeyeen said:
[Request] Is it possible if anyone could send me a Nandroid backup of a working rom, so I could restore it via CWM? (It is a way I found in the XDA forum).
...
So yeah I flashed Deodex_LF2_Cwm.zip yesterday, trying to deodex my DDFL2.
And following that I experienced total loss of mobile signal, baseband, IMEI, IMEI SV, and phone (*#1234#).
And I haven't been seeing this kinda thing to come, I did not back up EFS. (Yeah brilliant me)
So I tried a few of these:
[GUIDE] Recover your IMEI in 9 steps
EFS Pro
Reflashing from latona.pit then XXKPE; for a few times
Flashing various Modem.tar (DDLE1, DXKP7, etc) via Odin3 at different ROM levels (XXKPE, DDLF2, even CM10A4)
But nothing worked so far yet.
Now that I checked the /efs folder is empty and there is only a folder named lost+found.
And my last resort would be getting it replaced in Samsung service centre??
I don't know how much would it cost in Malaysia to change the motherboard but I'm sure it will be stupidly high...
Or.. does that mean my time in i9003 forum is up..? :crying:
Please help me because I don't want to buy a new phone yet! :crying:
Click to expand...
Click to collapse
Mate, do you like JellyBam V.1.3.0? Because that's the only Nandroid backup i have in my phone. I was thinking to upload it to my Box account for Emergency Backup if i don't have my computer. If you like, i can upload it for you, but the size of the backup would be nuts, it's 850 MB. It's up to you.
Rich'Dawg' said:
Mate, do you like JellyBam V.1.3.0? Because that's the only Nandroid backup i have in my phone. I was thinking to upload it to my Box account for Emergency Backup if i don't have my computer. If you like, i can upload it for you, but the size of the backup would be nuts, it's 850 MB. It's up to you.
Click to expand...
Click to collapse
I would try anything as long as it works! Please do!
Best of Luck
a friend of mine ran through the same same problem and i think he did some sort of repair from a shop but later we came to know that the backup can do the task not sure whether that work or not but u can give it a try,, BEST of Luck with that..... Hopit Fix the Issue
Good luck sir! As far as I know, if you would choose to replace the motherboard from repair center, it would cost you more or less 80% of the original price of the phone. So it would seem that you have to buy a new one. I hope that a nandroid backup (as stated above) would solve the problem. God bless you! Think positive
i have the same problem and tried those solution the TS tested and still no luck, i wan't to try those nandroid backup but can't find any.
Rich'Dawg' said:
Mate, do you like JellyBam V.1.3.0? Because that's the only Nandroid backup i have in my phone. I was thinking to upload it to my Box account for Emergency Backup if i don't have my computer. If you like, i can upload it for you, but the size of the backup would be nuts, it's 850 MB. It's up to you.
Click to expand...
Click to collapse
Bro,pls upload... let me try it... if imei is changed to 043xxxxxxx then we can fix with z3x box
Xperia.IN said:
Bro,pls upload... let me try it... if imei is changed to 043xxxxxxx then we can fix with z3x box
Click to expand...
Click to collapse
can you share it with me if you have nandroid backup, i will try to fix it with z3x and asansam
never thought deodexing gonna brick the phone.. ive deodex once without any problem.. without any doing backup before that.. lucky me.. huhu
try other people's nandroid and see.. i dont think it needs a specific emei or what so ever.. as long as its a backup.. goodluck..
the problem is we can't find someone to lend us their nandroid backup.
I did it!
Bro, try use Efs Pro, http://forum.xda-developers.com/showthread.php?t=1308546
Try the new version, you can choise Qualcom version, write you IMEI number, go back to initial and do NV Restore.
My SG Fit go back to life (after maybe 4 months with 0000000000000 Imei). :good:
I´m very happy
Hope it work for you! Good luck!
so i managed to soft brick an hdc note 3 clone , to my surprise the boot menu that came with it was upside down (you read that right) and while the option to factory reset it was there, no button gave the OK confirmation needed .
so next option was finding a suitable rom and doing the flash which came after hours of researching where needrom.com had few to test with and found drivers somewhere but would want to leave that as a final resort since this could brick it for good
now there was another option i came across yet need the assistance of an adb geek to help me with.
i originally bricked the device by copying build.prop to build.prop.bak in system folder then edited build.prop which lead it to soft brick, now the question, is there a way to use adb to access the device and delete old build.prop, then rename .bak one to build.prop?
please bare my noobness
night-mayor said:
so i managed to soft brick an hdc note 3 clone , to my surprise the boot menu that came with it was upside down (you read that right) and while the option to factory reset it was there, no button gave the OK confirmation needed .
so next option was finding a suitable rom and doing the flash which came after hours of researching where needrom.com had few to test with and found drivers somewhere but would want to leave that as a final resort since this could brick it for good
now there was another option i came across yet need the assistance of an adb geek to help me with.
i originally bricked the device by copying build.prop to build.prop.bak in system folder then edited build.prop which lead it to soft brick, now the question, is there a way to use adb to access the device and delete old build.prop, then rename .bak one to build.prop?
please bare my noobness
Click to expand...
Click to collapse
This forum is not about clones - there are other places on xda where there are threads specific to certain clones and you can ask there.
Actually, regardless of clone or not, this is a standard ADB question.
However, it's in the wrong forum, so I'll move it to the Android General. Some folks there should be able to help you.
MD
Moved....
OK,
First of all it seems you are my last hope. Yes i know there are similar posts, yes i know that i m making another one (i m sorry for that), yes i belive that i have exhausted options from those posts.
i used sp flash tool with format all + download option (yes i did not had idea that it would cause that much trouble). I have much snail 78P01 phone. As everyone is expecting , no imei, no baseband.
Phone is rooted (of course), things that i tried and they did not worked (becouse file pttycmd1 will be deleted everytime after reboot - maybe someone can explain):
1. mtkdroid tools (dont see band, imei is null) after i try change imei, there in log i can see that pttycmd1 could not be found (which is true, if i use root rexplorer its not anywhere near where it should be).
2. echo 'AT+....1,7,"IMEI..." > /dev/ptt... - yes its there (and mtk droid tool can confirm that , becouse its not giving you error, but thats all...)
3. *#*#3646633#*#* , .... AT+.... i will get error with sending command (yes i tried it as someone suggested with space, )
4. creating your own imei file MP0B_001 and placing it to /data/nvram/md/NVRAM/NVD_IMEI/ (btw my md folder is blank , there is nothing there)
5. downloading and flashing nvram (hope so that is nvram) "All Mtk BPLGU Modem files for Imei change.rar"
6. maybe something that i have forgot
btw:cpu mt 6592
I should be sleeping for like 4 hours now, but i m not, working (googling) on this like 10 hours straight. Any advice would be most welcomed.
Hi,
Thanks for using XDA assist.
I couldn't find any useful information on XDA regarding to your problem. If you haven't already, please create a XDA account and post in the following forum:
Android Q&A, Help & Troubleshooting
Good Luck! - gsstudios
Hi,
I have a note 3 neo, 7505 and i updated the firmware. It was all working good for a week then i was listening to soundcloud to sleep and the phone restarted, since then the phone doesn't have an imei and says to insert sim card, and of course unknown modem..
Anyway, i created a backup of the efs using twrp, i have tried gazillion ways to restore the backup and gazillion manual ways too. Going to stock recovery... trying to copy manually the nvdata and all but it doesnt resolve. The files are placed there, i can see it in the shell but the thing just wont work!
i don't know how to proceed to this, i don't know if its a hardware fault, had it been that, shouldnt have i gotten the efs corrupted or some issue? could it be that the hardware itself is damaged all of a sudden? i dont think so, i pretty much think its the efs and yet i cant restore it?
should i attach my efs folder if someone can look through hex editor or logs to suggest a possible solution?
Thanks a lot and also i have search through and proceeded with many solutions and after that created a thread. hope someone can help.
P.S. I just noticed the serial number can be seen in phone status, so apparently its reading NVdata? or is it getting it from elsewhere? how to test if its a hardware fault?
penandweb said:
Hi,
I have a note 3 neo, 7505 and i updated the firmware. It was all working good for a week then i was listening to soundcloud to sleep and the phone restarted, since then the phone doesn't have an imei and says to insert sim card, and of course unknown modem..
Anyway, i created a backup of the efs using twrp, i have tried gazillion ways to restore the backup and gazillion manual ways too. Going to stock recovery... trying to copy manually the nvdata and all but it doesnt resolve. The files are placed there, i can see it in the shell but the thing just wont work!
i don't know how to proceed to this, i don't know if its a hardware fault, had it been that, shouldnt have i gotten the efs corrupted or some issue? could it be that the hardware itself is damaged all of a sudden? i dont think so, i pretty much think its the efs and yet i cant restore it?
should i attach my efs folder if someone can look through hex editor or logs to suggest a possible solution?
Thanks a lot and also i have search through and proceeded with many solutions and after that created a thread. hope someone can help.
P.S. I just noticed the serial number can be seen in phone status, so apparently its reading NVdata? or is it getting it from elsewhere? how to test if its a hardware fault?
Click to expand...
Click to collapse
The point is that TWRP creates faulty EFS backups on many devices which can't be restored properly.
There are different backup solutions (e.g. EFS Pro) confirmed working which may help you prevent future issues. I prefer the manual backup using adb shell or terminal emulator:
dd if=/dev/block/mmcblk0pXX of=/storage/SdCard/efs.img bs=4096
(XX needs to be replaced with the model specific partition number as they use different partition tables)
Restore:
dd if=/storage/SdCard/efs.img of=/dev/block/mmcblk0pXX bs=4096
thanks LS.xd, but i guess i have a pretty solid backup as i did create backup various ways, some were corrupt, but one that i working with has nvdata and every other file along with imei pretty intact....
i can open it up with winrar, and open the nvdata with hexeditor, i was wondering if i could confirm some way that the back up is actually 100% solid?
wondering if the partition's aren't aligned. I don't know for sure if EFS folder in the root directory is the same as being pointed by /mmcblkp03/platform/by-name/EFS ?
i mean they should be the same thing, its just a redirection right?
what should i be doing now? the baseband is unknown and the imei wont just work, waste the phone? or it could be done via some boxes or some other process?
there must be a starting point? isn't there some way i could use a generic imei and just any modem? then i could replace nvdata may be? right now, i'm installing various versions of stock firmware and repeatedly placing old efs data in various ways and i kind of turning hopeless. first i lost a nexus then i bought a g4 last month, gave me a bootloop just a week after, gone dead. then i bought the n3n and now this..... i mean 3 phones in a row..... i really hope this could work..
penandweb said:
there must be a starting point? isn't there some way i could use a generic imei and just any modem? then i could replace nvdata may be? right now, i'm installing various versions of stock firmware and repeatedly placing old efs data in various ways and i kind of turning hopeless. first i lost a nexus then i bought a g4 last month, gave me a bootloop just a week after, gone dead. then i bought the n3n and now this..... i mean 3 phones in a row..... i really hope this could work..
Click to expand...
Click to collapse
So you got some non TWRP made EFS backup, too? You can list your partitions using shell:
[email protected]:/ # cat /proc/emmc
You can use the dd command once you know the layout. Backups not generated manually may only be restored with the specific app/version and are probably not compatible using other restore methods. For my OnePlus 3 EFS backup can generated fine using TWRP but restoring it screws up the partition. Manually created image works fine. As I don't have a Note 3 Neo I don't know how it behaves for your device.
any idea how would i go on about inspecting the nvdata.bin? i'm in hex editor trying to see something resembling imei but its just so much garbage except a few lines.
i can't be sure whether its corrupt or not...
in efs -> imei -> a file called mps_code.dat i open it up in hex editor, and it has only 3 characters.....
is it possible i could initially use a generic imei and modem and later on populate it with actual somehow or just keep using generic one for now until i find a better solution, using hex editor or something...?
there are some tutorials on qualcom.. none for exynos but it should happen the same way, somewhere in nvdata, you place the imei ... and it would be generic method for most exynos devices...
i wish someone could guide me to that...
also can it be restored via "boxes"?
penandweb said:
any idea how would i go on about inspecting the nvdata.bin? i'm in hex editor trying to see something resembling imei but its just so much garbage except a few lines.
i can't be sure whether its corrupt or not...
in efs -> imei -> a file called mps_code.dat i open it up in hex editor, and it has only 3 characters.....
is it possible i could initially use a generic imei and modem and later on populate it with actual somehow or just keep using generic one for now until i find a better solution, using hex editor or something...?
there are some tutorials on qualcom.. none for exynos but it should happen the same way, somewhere in nvdata, you place the imei ... and it would be generic method for most exynos devices...
i wish someone could guide me to that...
also can it be restored via "boxes"?
Click to expand...
Click to collapse
After 3 years I had to retire my HTC One S. I flashed roms and firmwares up to 3-4 times a week without having any issues. One sunny day some update bricked then nvdata. I spent a bunch of hours trying to restore it in different ways, extracted data from stock firmware as well as using dumps from other user's phones, as some users reported this error fixed doing so. Even when the files was identical it just did not work for me. Changing the mainboard was the only possible solution so I decided to get a new device.
All I want to say is try to restore a valid backup in a way confirmed working. If you don't have a usable backup ask in your device's forum for somebody may upload it. Or spend 100 hours messing around with hex editors until you reach then point where you realize its cheaper to switch the device as wasting a year's holidays browsing the internet for some solution.