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
Related
Hi all,
I recently upgraded to JPM version of froyo, and wanted to change back the product code to the original. After restoring from the .bak files, I got back the original product codes. However, while copying to another location for backup, I deleted the contents of the /efs folder by mistake (atleast I think I did).
The /efs folder is empty, but the phone still works fine. Haven't rebooted the phone for fear of bricking it. Is there a way to recover deleted files? Or are those files just hidden from view?
Someone please help
Update:
Managed to get of copy of nv_data.bin from a folder used by sgstoolbox. Rebooted the phone and phone works fine. Checked the folder contents, has nv_data.bin, nv_data.bin.md5, .nv_state and a folder named .android. Is there anything else which should be there? How to restore?
Do you have a backup of your /efs folder?
Woah same happened to me just some Hours ago !
If you used SGS Toolbox to check, you are lucky because it automatically creates a backup.
-> I think SUFBS Explorer deleted the efs because i am sure i checked "copy" ... anyway !
If you have any backup file, you are lucky.
One question by the way:
I´ve also lost the "IMEI" Folder, but my IMEI is still correct. Is that because ne nv_bin is just enough for the system checks ?
EDIT: Go and check with SGS Toolbox, if it displays your code, it is still there + it creates a backup file on your sdcard (you should double-check that anyway)
I'd say that the best and easiest way of restoring your product code is by using this: http://forum.xda-developers.com/showthread.php?t=787163
messing around with /efs folder is not a good idea, especially if you don't have a back up.
Just remembered that I have a titanium batch backup of system + apps taken a while ago when I was on stock firmware. Any way to restore the /efs folder from that? The shock of losing the /efs folder was enough to jolt me out of a beer induced haze ;-)
The phone still works, which is good news. But anyway to restore from Titanium backup?
fullerms said:
Just remembered that I have a titanium batch backup of system + apps taken a while ago when I was on stock firmware. Any way to restore the /efs folder from that? The shock of losing the /efs folder was enough to jolt me out of a beer induced haze ;-)
The phone still works, which is good news. But anyway to restore from Titanium backup?
Click to expand...
Click to collapse
Titanium does not backup /efs.. If you don't have a backup, you're basically screwed! Sorry to be the bearer of bad news
Like I said, the phone works fine after I restored the nv_data.bin file. I listed the files which were rebuilt by the system. Is there anything else missing? Can someone post a screen shot of the contents of your efs folder?
Sent from my GT-I9000 using XDA App
fullerms said:
Like I said, the phone works fine after I restored the nv_data.bin file. I listed the files which were rebuilt by the system. Is there anything else missing? Can someone post a screen shot of the contents of your efs folder?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Oh, so you DID have a backup? Nice! Besides what you lited in the first post, there are the following things:
.imei (file)
imei (folder)
- .nvmac.info
- bt.txt
- mps_code.dat
Any idea what those files are for? Possible to check what they contain?
Sent from my GT-I9000 using XDA App
Like i said, my imei folder was deleted aswell...
No problems so far with that !
Use rootexplorer, dont use ASTRO. It's crap and does not show all files, including the whole /efs
My EFS folder is empty too...and I don't know why, I have only flashed a couple of time with odin and JM9....
But SGS Toolbox report my csc correctly as ITV....even if I used the HUI csc from my operator with odin....
Could it be a problem if the efs folder is empty? The phone is working well...the only problem is that it loses very often the wifi connection...but I don't think that it is csc related...
I created a custom Rom, a really great mash up for people that like certain things from eugenes R2 final and Nero using KA6 while also implementing a very nice stock look (stock gingerbread messaging, dialer, contacts)... calling it Frankenstein. I of course will give credit and am not taking any credit away from these real great devs... this is just a mash-up.
This is where I need my [Help] while doing this, testing on my vibrant etc. I have managed to mess up my market.... my phone started off by not being able to connect (data) at all, and only having basic phone ability (mms, callling out).. I have fixed that, but no matter if I odin back to stock, do the eugene froyo odin/reformat back to jfd.. the market will not update. No apps really whatsoever... I get more apps when going to a rom like Nero V5 vs. stock JFD.. so this tells me that I am getting the market the way it was when they were implemented into the roms? but even with nero v5 im still missing a great deal such as titanium backup, file managers... even little things like doodle jump....
anyone that can provide detail that leads to a fix i will happily donate $15 via paypal, no big deal.
files must be missing, would love help.
Edit: have tried clearing data, resigning in.. all the little things... and as i said i have flashed back to jfd... now im on jfd with apps such as firefox test.. and a bunch of apps that were most likley the first apps ever put on market.. this puzzles me.
Thanks, Brandon
the only featured app right now is auto focus snake.. which looks like a android test app...
http://www.google.com/support/forum/p/Android+Market/thread?tid=55c997eccabf0a6a&hl=en&start=40
seems to be an issue with SGS devices and the market? WTF
Attached is a copy of the vending.apk I've been using in my kangs, and haven't had a problem with it. It shows all apps, on my phone its updated by now, but if it isn't when you push it, it should update properly given a little bit and a reboot. I would say if this doesn't fix your issue, it may be something else in your build. Just push the file to the system/app folder in your build, reboot and test it. Or, copy and replace the vending.apk in your working files, recompile and flash your rom, and test it. Good Luck.
so, select section you want, select free or latest or whatever, and you will see them.... or just search for the app you want
IMEI issue
I had the same issue all test apps in market and really no access.
I had to restore my backup and relock the phone.
Now all is working.
It is because certain apps don't recognize the Vibrant's build number. (T959KA6 is an example of a build number)
Sent from my SGH-T959 using XDA App
No I flashed back to stock tried Nero 5. Nothing helped had to restore nvdata. Imei was something like 004 phone was unlocked and tested on ATT. Look when you go into the market and it popup saying phone kay not support the market. Tried multiple google accounts its linked to your google account and your imei for supported apps on your type of phone.
Sent from my SGH-T959 using XDA App
saintjmf said:
No I flashed back to stock tried Nero 5. Nothing helped had to restore nvdata. Imei was something like 004 phone was unlocked and tested on ATT. Look when you go into the market and it popup saying phone kay not support the market. Tried multiple google accounts its linked to your google account and your imei for supported apps on your type of phone.
Sent from my SGH-T959 using XDA App[/QUOTE
there we go, my imei starts with 004 too, and is not my original imei.. what is the easiest way to restore my files? if you could give step by step that would be great! thanks mate.
Click to expand...
Click to collapse
You have to have a backup copy of your original.
If you do delete the files that start with nv -- in the /efs directory.
You probably can see your original IMEI if you open the file that is hidden in the directory /efs it is .imei -- That held the correct number for my IMEI. not sure if someone knows how to use that if you dont have an original backup of nvdata.bin.
I took nvdata.bin and put it in the /efs directory.
removed all files that start with nv in /efs example nv2data.bak
rebooted phone it built md5 from nvdata.bin.
factory reset and all apps back.
I also coudlnt get my pro license of titanuim backup to register with google checkout until this was completed.
saintjmf said:
You have to have a backup copy of your original.
If you do delete the files that start with nv -- in the /efs directory.
You probably can see your original IMEI if you open the file that is hidden in the directory /efs it is .imei -- That held the correct number for my IMEI. not sure if someone knows how to use that if you dont have an original backup of nvdata.bin.
I took nvdata.bin and put it in the /efs directory.
removed all files that start with nv in /efs example nv2data.bak
rebooted phone it built md5 from nvdata.bin.
factory reset and all apps back.
I also coudlnt get my pro license of titanuim backup to register with google checkout until this was completed.
Click to expand...
Click to collapse
i do have a back up of my efs folder thank god. what program did you use to access your efs folder is what im saying? not sure if i have access to adb commands on this machine that i am using, any other way?
and remember i cant use market, so if someone can maybe provide a program to navigate my phone files from my pc, i can just put back in the nv data
I used root explorer
Sent from my SGH-T959 using XDA App
Can I flash this with clockwork mod? And does the voodoo kernel and sounds work with this?
I created another thread about this as I believe there maybe alot more users with this issue
Sent from my SGH-T959 using XDA App
whit this program you use to access your efs folder
http://www.mediafire.com/?c8x8wvpc9vhcd5x
shon yakobi said:
whit this program you use to access your efs folder
http://www.mediafire.com/?c8x8wvpc9vhcd5x
Click to expand...
Click to collapse
said this version is expired, need to update manually?
saintjmf said:
I used root explorer
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
do you know if there is a rom out there that has this preinstalled? remember i cant get apps because of that market.
The problem [might] be inside the build.prop.
Try changing:
Code:
ro.build.fingerprint=Samsung/SGH-T959/SGH-T959/SGH-T959:2.2/FROYO/UVKA6:user/release-keys
to
Code:
ro.build.fingerprint=Samsung/SGH-T959/SGH-T959/SGH-T959:2.1-update1/ECLAIR/UVJFD:user/release-keys
total commander
whit this program you use to access your efs folder its ok no problom
http://forum.xda-developers.com/attachment.php?attachmentid=494485&stc=1&d=1295487965
IMEI
You're IMEI can easily be found by just taking out your battery and looking under it at the sticker with all the numbers and bar codes. It may just show IME and have either dashes or periods (you can ignore the punctuation). That is your original IMEI (this is nothing more than your serial number, make sure you know what it is because if you ever have a hardware issue and want to still utilize your warranty then they check by this number, and of course unroot the phone first so it won't be considered out of warranty)
Hey folks. I'm having a hell of a time here - I noticed that after the (fresh) installation of cm7 and updating to the latest nightly, my imei changed to 004999010640000.
Now, I have two backups, and went ahead and copied nv_data.bin, from when I originally got the phone, to /efs and changed the permissions to 1001:1001. After a reboot, imei is still 004999010640000.
I went ahead and flashed back to JL2, at which point my iemi was showing correctly, so I flashed speedmod, flashed cm7-kernel, rebooted, installed the cm7 update, and now my iemi is back to 004999010640000.
It doesn't seem to have any negative effects, my phone works as it usually does, but it is driving me nuts why my iemi is buggered up under cm7, and why restoring the original doesn't fix it. Is this a cm7 issue?
TIA
CM7 copies the efs folder and reads it from somewhere else. That's why restoring it to original place didn't do anything. Don't know why it changed it.
Yeah I started poking around the initial flash zip and noticed that all efsbackup.sh does it copy the contents of /efs to /sdcard/backup/efs.
I figured that they were keeping /efs because of
Code:
/dev/block/mtdblock4 on /efs type yaffs2 (rw,relatime)
showing up when viewing mounts...
Still having the problem... im hoping someone here can offer up some suggestions.
Sent from my GT-I9000 using XDA App
EFS backup post somewhere on the forum its a topic thats been well covered.
Due to flashing wiping efs .
One post is .
http://forum.xda-developers.com/showthread.php?t=881162
jje
JJEgan said:
EFS backup post somewhere on the forum its a topic thats been well covered.
Due to flashing wiping efs .
One post is .
http://forum.xda-developers.com/showthread.php?t=881162
jje
Click to expand...
Click to collapse
Thanks for the link, but it doesn't relate to my problem. The edits to nv_data.bin in that thread relate to changing the product code back to a proper AT&T product code on the captivate. I have a BMC i9000m, and an original (and proper) nv_data.bin from my stock phone when purchased.
The issue is when I copy my proper nv_data.bin to /efs, set proper permissions and reboot, it reverts back to a buggered IEMI according to settings -> status in CM7. I'm looking to find how how exactly CM7 handles /efs, and if it is CM7 specifically that is overwriting my nv_data.bin or if something else is at work.
Ah, finally figured it out. After seeing what nv.log was saying and thanks to zacharias over on the cm forums for tipping me off that just restoring nv_data might not work without everything else in /efs. I transferred my efs backup from windows to my ubuntu vm, set the permissions and made a tarball. Transferred that to my device, extracted the tarball, rebooted and poof, it worked. As this was a complete /efs backup and not just nv_data.bin, I'm guessing there was another file that the phone needed, despite what some of the guides say.
I still wish I knew what caused the phone to reject the nv_data.bin (as per nv.log)... I did delete the nv_data.bin.md5 because I read elsewhere that the phone would simply rebuild a new hash on boot, but it obviously didn't work. I wonder if it had something to do with that.
Oh well, it works now... thanks everyone!
Hey, I got some problems. Posted in another forum, but it's very urgent so I post it here to. Just quoting what I previously posted.
Hey, flashed the JVS modem on top of the Chameleon Final. Didn't get any signal and the baseband version in settings stated "unknown". Tried another modem, JVO and flashed back to Chameleon modem, still not fixed. Also tried to wipe everything and install rom again... did not help either. Odin didn't report any errors whatsoever.
Desperate for some help her guys!
Click to expand...
Click to collapse
Got reply that my IMEI was screwed, and replied:
[quote author=bahafeld link=topic=1931.msg13081#msg13081 date=1316107492]
Okey, I have backup of my original EFS folder. Isn't it there the IMEI is saved? can I just copy it over again with Root Explorer?
Please help me out here. All the guides I've found have the EFS saved in a .tar format. However I just backed up the EFS folder with root explorer. Anyone know I can recover my EFS, tried just copying it back, but that did not work.
Its kinda urgent!
[/quote]
So I hope you guys at XDA can help me a bit faster.
Thx
bahafeld
if you have a .tar version of your EFS. Unzip it. Copy all the contents of it, And paste them to the /EFS on the phone. Making sure they overwrite the current contents.
Once that has done, Restart the phone without backing out of root explorer (or what ever app you are using to copy/paste these files).
If that fails, Repeat the above step but ONLY copy / paste the NV_data.bin & NV_data.bin.md5
And finally if that fails. Backup all your stuff using Titanium Backup (or similar) And re flash a stock Froyo ROM. Maybe older, its upto you.
That will Definitely restore the IMEI, Then re-root and go back to whatever ROM you wish.
Good luck.
Hello,
got the same Problem like alot others. Wrong flashing and the complete EFS was destroyed.
Now i go back to Stock, rebuild the Baseband and the Counter is 0. But still have IMEI NULL/NULL
I read now alot of posts in the Net and tryed a lot but nothing helped.
So my Question is, is there really a solution to build the IMEI back to the Original one if you completly lose the original
EFS Folder? Or do i need to get it to technican to get it back with a Box?
I tryed IMEI Changer App but this one doesnt work on my i8190.
If there is another way to fix this, would be grate to get a but of Help.
Thank you in advance.
So i try to change the IMEI with ALP. But ALP directly gets an Read Error while try to get the IMEI.
Is there a File i can put in and change it with ALP to get back my IMEI?
I had the same problem when i was on my SGY. Just reflash the rom through odin and fix permissions. ??
There is no bad choises, only bad results.
SGS III Mini
tenshi_xp's PAC Rom RC-3
KitKat 4.4.4.
Hi,
thank you for your Answer. But i already reflashed Stock Rom all things are back, i just miss the IMEI File or Area. Saw on the net there are IMEI Folder to flash with ODIN
so i can change it with ALP. But most of the Sites or Files or deleted, maybe false and Viruses, i dont know.
My Problem is that my complete EFS Folder was lost, no Backup nothing. With different Flashes and Stuff i got it back with Baseband, CSC and so on. Just my IMEI tells
me NULL/NULL and ALP cant get it, because this Part isnt available anymore
Can you tell me Stockrom or something i can try? Need something for an open German i8190.
Best Regards
guzzzi0 said:
Hi,
thank you for your Answer. But i already reflashed Stock Rom all things are back, i just miss the IMEI File or Area. Saw on the net there are IMEI Folder to flash with ODIN
so i can change it with ALP. But most of the Sites or Files or deleted, maybe false and Viruses, i dont know.
My Problem is that my complete EFS Folder was lost, no Backup nothing. With different Flashes and Stuff i got it back with Baseband, CSC and so on. Just my IMEI tells
me NULL/NULL and ALP cant get it, because this Part isnt available anymore
Can you tell me Stockrom or something i can try? Need something for an open German i8190.
Best Regards
Click to expand...
Click to collapse
Our IMEI number isn't saved in /efs partition/folder. It's saved in mmcblk0p9 partition which take up to 1MB. The efs partition (/efs>imei folder) only contains the IMEI key code to access the IMEI number in mmcblk0p9 path. If your IMEI key code got wiped and you didn't make a backup of your efs partition, then you will (unfortunately) never see your IMEI again
BTW : Does WiFi, Bluetooth etc. works or not?
EDIT : I found a interesting therad for you http://forum.xda-developers.com/showthread.php?t=2755787. Maybe you can use this efs backup from this user and change the IMEI to your original one.
xXPR0T0TYPEXx said:
Our IMEI number isn't saved in /efs partition/folder. It's saved in mmcblk0p9 partition which take up to 1MB. The efs partition (/efs>imei folder) only contains the IMEI key code to access the IMEI number in mmcblk0p9 path. If your IMEI key code got wiped and you didn't make a backup of your efs partition, then you will (unfortunately) never see your IMEI again
BTW : Does WiFi, Bluetooth etc. works or not?
Click to expand...
Click to collapse
Yes all other Services are working WiFi and BT. Just the IMEI Numbers are gone.
But if its possible to recreate the Folder and File i think its possible to change the IMEI Number with APS to the old one from the Mobilphone.
But i can get them back if i recover with a OctupsBox or how this boxes are calling?!
guzzzi0 said:
Yes all other Services are working WiFi and BT. Just the IMEI Numbers are gone.
But if its possible to recreate the Folder and File i think its possible to change the IMEI Number with APS to the old one from the Mobilphone.
But i can get them back if i recover with a OctupsBox or how this boxes are calling?!
Click to expand...
Click to collapse
Check my edited post mate
xXPR0T0TYPEXx said:
Check my edited post mate
Click to expand...
Click to collapse
Thank you. Will try this when im back at Home. I will give Feedback if it was possible.
When try to install this with CWM i get an Installation aborted
Isnt there a complete Stock Rom with Partition file and everything needed?
guzzzi0 said:
When try to install this with CWM i get an Installation aborted
Isnt there a complete Stock Rom with Partition file and everything needed?
Click to expand...
Click to collapse
There is an alternative method. You can flash this efs.img (which you find in the zip file) with terminal emulator which needs ROOT access.
1. root your device and download terminal emulator from Google play store.
2. Copy the efs.img to your internal storage and open terminal emulator.
3. After open terminal emulator type su to give root access, (your supperuser app asks for root access, confirm with yes)
4. Type/Copy this code : dd if=/storage/sdcard0/efs.img of=/dev/block/mmcblk0p11 in terminal emulator and press "enter"
5. Now your efs partition got overwritten with the efs.img
BEFORE!! you start this method, backup your "current" efs folder by type in terminal emulator : dd if=/dev/block/mmcblk0p11 of=/extSdCard/EFS.img
Please do this at your own risk!
xXPR0T0TYPEXx said:
There is an alternative method. You can flash this efs.img (which you find in the zip file) with terminal emulator which needs ROOT access.
1. root your device and download terminal emulator from Google play store.
2. Copy the efs.img to your internal storage and open terminal emulator.
3. After open terminal emulator type su to give root access, (your supperuser app asks for root access, confirm with yes)
4. Type/Copy this code : dd if=/storage/sdcard0/efs.img of=/dev/block/mmcblk0p11 in terminal emulator and press "enter"
5. Now your efs partition got overwritten with the efs.img
BEFORE!! you start this method, backup your "current" efs folder by type in terminal emulator : dd if=/dev/block/mmcblk0p11 of=/extSdCard/EFS.img
Please do this at your own risk!
Click to expand...
Click to collapse
Hello,
the Problem is this .ZIP File isnt available anymore on MEGA Hoster
guzzzi0 said:
Hello,
the Problem is this .ZIP File isnt available anymore on MEGA Hoster
Click to expand...
Click to collapse
Wait mate. I will upload this efs.img...
guzzzi0 said:
Hello,
the Problem is this .ZIP File isnt available anymore on MEGA Hoster
Click to expand...
Click to collapse
Here the ZIP file. It's not flashable, just unzip it and flash it with terminal emulator
Im sorry but this didnt helped. I think i really need all Parts back to re-partition + Bootloader and all other stuff to get it back.
But i think to send it to a shop to get it back into life.
Many thanks for your Help and merry Christmas and happy new Year
Best Regards
guzzzi0 said:
Im sorry but this didnt helped. I think i really need all Parts back to re-partition + Bootloader and all other stuff to get it back.
But i think to send it to a shop to get it back into life.
Many thanks for your Help and merry Christmas and happy new Year
Best Regards
Click to expand...
Click to collapse
Yes it's better to send it back to Samsung center
Merry Christmas and happy new year too