To start with, my friend bought an S2 from somebody, and it was running stock Android 2.3.4 Gingerbread, if i remember correctly something that ended with KI4. He had one problem: he could not log into his gmail account regardless of what he did so he decided to ask me to update his device. And this is where the fun started:
I tried to update using the OTA feature, but as he couldn't add his google account it didn't work.
Next i tried updating through KIES, but strangly it said that there was no update available.
We decided to root the phone and try installing a custom ROM.
We rooted it with the CF-Kernel and then installed Neat ROM Lite, but the ROM is not important.
After successfully installing it an starting the phone, we were stunned by the image below. The strangest part is that the image is above the wallpaper but under the widgets and when scrolling through home screens in remains there just like the four short cuts below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also, the home button did not work. From here on i have asked for help from the ROM developer and did the next things
Flashed the official LPX firmware with ODIN. It is worth mentioning that he is able to add his account on any 4.0.x ROm, but other problems appear. In the stock official LPX the home button worked but the strange image was still there.
After this we flashed the Siyah kernel via Odin, did the usual cleaning up like restore to factory settings, clearing every cache, formatting system after which i installed the custom ROM again but with the same results: home button not working and the image was still there.
My questions are:
1.How do i get rid of that bloody image on the stock ROM, since that seemed to be the best one.
2.How do i make the home button work again in the Neat ROM 3.3.
It is also important to mention that i have not yet tried other custom ROMs since i will only get my friends phone tomorrow. I have a feeling that i will have the same problems with other ROMs regardless of their official/custom status. I also remember that somebody had this problem before but i am unable to find that particular post, so if the person who found the solution reads this post please help me too
Thanks in advance.
Try resetting settings to default.
przemcio510 said:
Try resetting settings to default.
Click to expand...
Click to collapse
Thanks, but i forgot to mention i already did that
Then you can give CM10 a try, it's stable enough.
same problem
radu_wizu said:
To start with, my friend bought an S2 from somebody, and it was running stock Android 2.3.4 Gingerbread, if i remember correctly something that ended with KI4. He had one problem: he could not log into his gmail account regardless of what he did so he decided to ask me to update his device. And this is where the fun started:
I tried to update using the OTA feature, but as he couldn't add his google account it didn't work.
Next i tried updating through KIES, but strangly it said that there was no update available.
We decided to root the phone and try installing a custom ROM.
We rooted it with the CF-Kernel and then installed Neat ROM Lite, but the ROM is not important.
After successfully installing it an starting the phone, we were stunned by the image below. The strangest part is that the image is above the wallpaper but under the widgets and when scrolling through home screens in remains there just like the four short cuts below.
Also, the home button did not work. From here on i have asked for help from the ROM developer and did the next things
Flashed the official LPX firmware with ODIN. It is worth mentioning that he is able to add his account on any 4.0.x ROm, but other problems appear. In the stock official LPX the home button worked but the strange image was still there.
After this we flashed the Siyah kernel via Odin, did the usual cleaning up like restore to factory settings, clearing every cache, formatting system after which i installed the custom ROM again but with the same results: home button not working and the image was still there.
My questions are:
1.How do i get rid of that bloody image on the stock ROM, since that seemed to be the best one.
2.How do i make the home button work again in the Neat ROM 3.3.
It is also important to mention that i have not yet tried other custom ROMs since i will only get my friends phone tomorrow. I have a feeling that i will have the same problems with other ROMs regardless of their official/custom status. I also remember that somebody had this problem before but i am unable to find that particular post, so if the person who found the solution reads this post please help me too
Thanks in advance.
Click to expand...
Click to collapse
Have you found a solution? Please share with me.
It is due to mising of keystr file under imei folder...root your device->install root explore->locate folder efs/imei->check there is a keystr file if not create a new file by pressing menu button and create new file->name it keystr and edit the file ON->reset your device...
Sent from my GT-I9100 using xda app-developers app
eswar6280 said:
It is due to mising of keystr file under imei folder...root your device->install root explore->locate folder efs/imei->check there is a keystr file if not create a new file by pressing menu button and create new file->name it keystr and edit the file ON->reset your device...
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I gonna try your solution. I'll let you know. Thanks.
---------- Post added at 11:41 PM ---------- Previous post was at 11:17 PM ----------
eswar6280 said:
It is due to mising of keystr file under imei folder...root your device->install root explore->locate folder efs/imei->check there is a keystr file if not create a new file by pressing menu button and create new file->name it keystr and edit the file ON->reset your device...
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
what extension should the file have? what do you mean "edit the file on"?
mess18 said:
I gonna try your solution. I'll let you know. Thanks.
---------- Post added at 11:41 PM ---------- Previous post was at 11:17 PM ----------
what extension should the file have? what do you mean "edit the file on"?
Click to expand...
Click to collapse
No extension.
and by "edit the file on", he meant edit the file to contain the word ON. That's it. And make sure the file has 644 permissions. (rw-r--r--)
it will work
ctomgee said:
No extension.
and by "edit the file on", he meant edit the file to contain the word ON. That's it. And make sure the file has 644 permissions. (rw-r--r--)
Click to expand...
Click to collapse
Sure,it will work by creating a file with root explorer,rename the file to keystr and writing ON in the file with a text editor
Related
Heya!
Some know my little kTool already, some love it, some hate it.
Well, let's try to get some more love for it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
>> Now with support for the Galaxy-Nexus and the Galaxy-S3! <<
So, what does this do?
Dump current kernel (and recovery on devices having a seperate one)
Flash kernel from /sdcard/zImage
Flash recovery from /sdcard/recovery.bin
Backup EFS
(as raw .IMG dump and as .TAR archive)
Check/Verify EFS backup (i.e. compare to "live" EFS)
Restore EFS from either .IMG or .TAR
Open stock update .TARs and flash from from it:
- Modem Firmware
- PARAM.LFS
- Kernel
Reboot device
- normally
- to recovery
- to download mode
*) When you check the EFS backup right after you made it, it should show a 100% match to the current phone's EFS.
However, after a reboot, the EFS *does* start to differ a bit - that seems to be normal, during my tests the EFS differed for 80bytes more after each reboot, my original EFS dump even differed by ~150k already
kTool companion tool market link [ Show ]
Hope you like it.
If anyone has more suggestions on what would need to be checked/verified during the check operation, do tell
After doing backup I did efs backup check....
And in that it says nv_data.bin not found..
Whts the reason?
Sent from my GT-I9100 using XDA App
koolshubh said:
After doing backup I did efs backup check....
And in that it says nv_data.bin not found..
Whts the reason?
Click to expand...
Click to collapse
For the .img and the .tar or only for one of them?
What does it say for "mount returned:"?
"nv_data.bin not found" means a bad/corrupted backup.
// EDIT
Just saw the screenshot.
Something went wrong making the raw .img dump (weird....).
But the .tar backup is OK (100% match to the phone's one).
Hmm.... gotta investigate the .img issue some more.
Check this;
Sent from my GT-I9100 using XDA App
OK, that helps a lot already.
The efs.img dump might be all fine and OK, it's actually a problem getting it mounted to "look into it".
Dug around some more and also found this:
Code:
2: system error (out of memory, cannot fork, no more loop devices)
"2" was the returncode you got during the check, fits with the verbose error message you get when trying the mount from a shell.
Cool, at least I know where to look, not exately sure why this happens, but we'll find out.
Maybe a busybox thing, maybe I'll bundle one with the app....
thanks for updating~~~
I have used the old one from here
f.lui.li/get_99_f13d.html
Updated to v1.21
Everything is working from my end. Thanks for the tool!
Sent from my GT-I9100 using XDA App
HellcatDroid said:
Updated to v1.21
Click to expand...
Click to collapse
it just works!
thx!
Thanks and cheers.
Thanks, HellCat. Great little kTool you've made --- love the kernel dump feature, so more love for your app! ; )
Tiny update to v1.22.
"Restore EFS" now lets you chose if you want to restore the raw .IMG dump or from the .tar archive.
Hi. thanks for your work. I kept getting the error shown in the attached pic when on xxki4 so I flashed back to official wxki4 but get the same error.. can u help?
rasinell said:
Hi. thanks for your work. I kept getting the error shown in the attached pic when on xxki4 so I flashed back to official wxki4 but get the same error.. can u help?
Click to expand...
Click to collapse
Are you rooted?
// EDIT
Hmm, and what version of the app are you using?
Tried making the EFS backup again?
I take it the phone does work fine (correct IMEI and all)?
Stock Samsung ROM or a custom ROM?
HellcatDroid said:
Are you rooted?
// EDIT
Hmm, and what version of the app are you using?
Tried making the EFS backup again?
I take it the phone does work fine (correct IMEI and all)?
Stock Samsung ROM or a custom ROM?
Click to expand...
Click to collapse
Hi. Thanks for the response. Yeah I'm rooted running official stock Rom and kernel. Everything seems fine with phone n imei ect. Tried twice on unofficial stock Rom n kernel and twice on this Rom but get the same every time :-\ I'm using v1.22
Sent from my GT-I9100 using xda premium
-scrap initial post-
// EDIT
HAHAA! I think I found something!
Thought some more about this, behaviour/differences of stock kernels and double checked a few things in my code.
I think (i.e. hope) I found the reason for this - and if my theory is correct I will be able to reproduce the app's misbehaviour you are getting and can then fix it.
I'll make a new build tonight.
HellcatDroid said:
What's the version of kTool you are using?
You tried doing the backup as well again, not only the check?
I'll flash a stock kernel and try to reproduce this later tonight.
Click to expand...
Click to collapse
I'm using v1.22. Yeah tried that. I was wondering if it was the kernel that was problem, not had chance to try with another yet. Thanks
Sent from my GT-I9100 using xda premium
HellcatDroid said:
What's the version of kTool you are using?
You tried doing the backup as well again, not only the check?
I'll flash a stock kernel and try to reproduce this later tonight.
// EDIT
HAHAA! I think I found something!
Thought some more about this, behaviour/differences of stock kernels and double checked a few things in my code.
I think (i.e. hope) I found the reason for this - and if my theory is correct I will be able to reproduce the app's misbehaviour you are getting and can then fix it.
I'll make a new build tonight.
Click to expand...
Click to collapse
Cool. Thank you
Sent from my GT-I9100 using xda premium
rasinell said:
I'm using v1.22. Yeah tried that. I was wondering if it was the kernel that was problem
Click to expand...
Click to collapse
Well, in a way.
IIRC the shell command "cp" (to copy files) is not available on stock Samsung kernels, and the app just calls "cp" instead of (like for most of the other shell commands used by the app) using "busybox cp" to call/use the busybox applet of the command.
As said, I'll try, check and hopefully fix this later tonight and if all goes well will have an update ready by tomorrow
Published v1.23 with the above issue fixed
The update should show up on the market soon.
left on old v1.22, right on new v1.23:
.
I'm with friends forum 4pda made the "Big picture for incoming and outgoing calls".
Thank you for the work sk0t and den339.
[I
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Set the CWM recovery stage.
Using CWM recovery
- Put the zip in your sdcard.
- Go in CWM recovery
- Install zip from sdcard
- Choose zip from sdcard
- Find it and press the home button
- When it finishes press reboot system now
Note: This works on deodexed roms. If your rom is odexed remove /system/app
Contacts.odex;DialerTabActivity.odex;Phone.odex file with root explorer.
Using Root Explorer
Extract the Contacts.apk;DialerTabActivity.apk;Phone.apk from the zip (system/app/)
Put it in your sdcard
Navigate to it with root explorer, and copy it to /system/app/
Reboot your phone
After installation :
Note: after installation of the Mod,all the photos in contacts reinstall!!!
Note: if you synchronize Google compresses the photo to 96х96.
Tip: save contacts on a memory card. Or , if you want to sync with google, then on the memory card, create a double contacts, enough of the same name, here's to the contact link the photo, and associate it with гугловским. In goulet, naturally remove photos.
Solved the problem with a small photo. 29/12/2011
Download -- http://www.multiupload.com/UNUZ6SIZQ3 --
-------------------------------------------------------------------
Add to big photo on incoming and outgoing calls
Removed the growing call
Download --http://www.multiupload.com/ER049CLAWO--
Before installing, make a backup copy:Contacts.apk;DialerTabActivity.apk;Phone.apk.
Happy New Year!!!
Thank you guys! Great job!
Only one question, it's possible to do same work on phone/dialertab/contacts of Miui theme by ghost?
thanks..bro..amazing job
Is it universal? I mean can the same apks be used on Froyo, CM7 etc ?
Great job bdw looks amazing
Thanks Man, you made my work easier and thanks for all the help you gave throughout.
Sent from my GT-I5800 using xda premium
And what if I want to revert it back to original, how can I do that?
JanerNevis said:
And what if I want to revert it back to original, how can I do that?
Click to expand...
Click to collapse
Just make a backup of the three files before flashing .. if you want to revert, replace the modded files by the backed up ones using Root Explorer
Rapier07 said:
Just make a backup of the three files before flashing .. if you want to revert, replace the modded files by the backed up ones using Root Explorer
Click to expand...
Click to collapse
Tnx. I saw only CWM installation and somehow I skipped RE installation in 1st post. If I saw that I'll knew that I just need backups.
JanerNevis said:
Tnx. I saw only CWM installation and somehow I skipped RE installation in 1st post. If I saw that I'll knew that I just need backups.
Click to expand...
Click to collapse
The original Contacts;DialerTabActivity;Phone :http://www.multiupload.com/2XCGE4XKZ9
Set the CWM recovery stage
Besson said:
The original Contacts;DialerTabActivity;Phone :http://www.multiupload.com/2XCGE4XKZ9
Set the CWM recovery stage
Click to expand...
Click to collapse
Could you make one for CM7 as well?
Can anyone who tried confirm, does it erase contacts, are there any thing i should know before flashing that. I not quite understand what he wrote on 1st post due to his bad english(not disrespect). Tnx.
------------------------------------------------
Sent from Kyorarom Ascendency;
Don't be shy, press thanks to anyone who helped you in any way.. People appreciate that.
Nice job bro... Really nice...
alen1901 said:
Can anyone who tried confirm, does it erase contacts, are there any thing i should know before flashing that. I not quite understand what he wrote on 1st post due to his bad english(not disrespect). Tnx.
------------------------------------------------
Sent from Kyorarom Ascendency;
Don't be shy, press thanks to anyone who helped you in any way.. People appreciate that.
Click to expand...
Click to collapse
English is not his first language. He probably translated it (?). So ignore it, He did a job, that's all we want, right?
No, it won't erase your contacts. Just be sure you don't upload picture in Google Synced contact because Google resizes the pic to 96x96 instead just edit the contact you saved on your phone which is not synced with Google. So don't sync your contacts with Google.
And you will need to reselect the contact picture to get benefit of bigger crop size.
---------- Post added at 05:12 PM ---------- Previous post was at 05:03 PM ----------
Hey, Bessen I wonder if we can work for porting call recording feature in our G3. I will look for files and inform you!
friend863 said:
English is not his first language. He probably translated it (?). So ignore it, He did a job, that's all we want, right?
No, it won't erase your contacts. Just be sure you don't upload picture in Google Synced contact because Google resizes the pic to 96x96 instead just edit the contact you saved on your phone which is not synced with Google. So don't sync your contacts with Google.
And you will need to reselect the contact picture to get benefit of bigger crop size.
---------- Post added at 05:12 PM ---------- Previous post was at 05:03 PM ----------
Hey, Bessen I wonder if we can work for porting call recording feature in our G3. I will look for files and inform you!
Click to expand...
Click to collapse
I'm working on these issues ...
Yes, I speak Russian and the translation gives me Google.sorry
Great work guys
Could I get permission to use the mod in my Miui theme?
Just installed the .zip. Working and looks great. Thanks.
Ghost In The Ruins said:
Great work guys
Could I get permission to use the mod in my Miui theme?
Click to expand...
Click to collapse
Yes, of course.
Could you make non increasing ringtone version in a separate zip?
Tapnięte z G3
It works nicely. Good job. Only pictures in contacts and mms are kinda like bars, but that is how it needs to be. Im really pleased. )
------------------------------------------------
Sent from Kyorarom Ascendency;
Don't be shy, press thanks to anyone who helped you in any way.. People appreciate that.
Thx *_*
Sent from my GT-I5800 using xda premium
Need some help here guys, I accidentally froze the default clock app with Titanium. (The one with stopwatch, timer,alarm, timezones etc.)
Then when I realized that the alarms weren't ringing, I tried to restore it from Titanium Backup Pro, but it was hanging at the restore screen and now only the alarm symbol shows up in the status bar but there's no app.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: Restart doesn't fix the alarm symbol issue, and Titanium is constantly hanging at the restore screen. I tried running the clockpackage.apk in /system/app, but it says "not able to install".
Sent from my GT-I9300 using Tapatalk 2
if u are using a custom ROM just reflash it doing a full wipe...should sort it out
vsohail said:
if u are using a custom ROM just reflash it doing a full wipe...should sort it out
Click to expand...
Click to collapse
No I am on stock ROM LF2 with CF-Root.
I have flashed a lot of mods though, and don't want to lose them all in the wipe and reinstall process.
Is there a way to solve this without reflash?
Thanks!
Sent from my GT-I9300 using Tapatalk 2
this is from one of the issues on an S2...it should work on the S3
Here is how to solve the problem:
1. Find /data/system/packages.xml with Root Explorer or an equivalent
2. Make a backup of packages.xml right away in the same folder in case we mess anything up any need to restore it later
3. Copy packages.xml onto the root of your internal or external storage
4. Plug your device into your computer and copy packages.xml from the root of your storage over to your computer
5. Open the packages.xml on your computer with your editor of choice - I suggest Notepad++
6. Search for the string {enabled="2"} (without the { }). Every line ending in this represents a frozen app. The lines should look something like this:
for ex:
<package name="com.sec.android.widgetapp.socialhub" codePath="/system/app/SocialHubWidget.apk" nativeLibraryPath="/data/data/com.sec.android.widgetapp.socialhub/lib" flags="1" ft="11b7e237e00" it="11b7e237e00" ut="11b7e237e00" version="1" sharedUserId="10001" enabled="2">
7. Now for every app you wish to unfreeze, replace {enabled="2"} with {enabled="1"} (again, without the {})
7. Save packages.xml, move it back onto your phone's storage, and use Root Explorer or an equivalent to replace your original packages.xml at /data/system/packages.xml with your new one
8. Reboot
Plzzz Click the Thank Button if this helped!!!
vsohail said:
this is from one of the issues on an S2...it should work on the S3
Here is how to solve the problem:
1. Find /data/system/packages.xml with Root Explorer or an equivalent
2. Make a backup of packages.xml right away in the same folder in case we mess anything up any need to restore it later
3. Copy packages.xml onto the root of your internal or external storage
4. Plug your device into your computer and copy packages.xml from the root of your storage over to your computer
5. Open the packages.xml on your computer with your editor of choice - I suggest Notepad++
6. Search for the string {enabled="2"} (without the { }). Every line ending in this represents a frozen app. The lines should look something like this:
for ex:
<package name="com.sec.android.widgetapp.socialhub" codePath="/system/app/SocialHubWidget.apk" nativeLibraryPath="/data/data/com.sec.android.widgetapp.socialhub/lib" flags="1" ft="11b7e237e00" it="11b7e237e00" ut="11b7e237e00" version="1" sharedUserId="10001" enabled="2">
7. Now for every app you wish to unfreeze, replace {enabled="2"} with {enabled="1"} (again, without the {})
7. Save packages.xml, move it back onto your phone's storage, and use Root Explorer or an equivalent to replace your original packages.xml at /data/system/packages.xml with your new one
8. Reboot
Plzzz Click the Thank Button if this helped!!!
Click to expand...
Click to collapse
Thanks for that, but there's not a single instance of enabled="2" anywhere in that file.
Sent from my GT-I9300 using Tapatalk 2
Some apps use {enabled="false"} so u gotta delete that..ex in galaxy Note Stock....By the u indian right....just flash CM9 or paranoid android just amazing...any help just contact me..
---------- Post added at 03:03 AM ---------- Previous post was at 03:01 AM ----------
if it still does not work...then ill look into the matter and get back tomorrow..just temme u tried defrosting via titanium like more than once na ???
---------- Post added at 03:06 AM ---------- Previous post was at 03:03 AM ----------
i presumed it should be like the s2 so things should be the same...ill just look into it..
btw i came across this on the forum
http://forum.xda-developers.com/showthread.php?p=28146536
it seems u cant defrost apps on the s3 yet!!!so i think its bbye to stock kernel
however i think titanium working on it cause if you see their changlog you will understand
http://www.titaniumtrack.com/changelog/titanium-backup-changelog
Yes buddy I'm from Mumbai.
Ok, so here's what I did:
I reflashed official LF2 ROM without doing any wipes since I didn't want to lose my apps and settings.
Now the clock app has appeared in my app drawer, and I'm able to open it. However all the other apps that I had frozen are all back. No problem, I'll freeze them again later.
Original problem is solved, alarm icon is functioning fine. Though I will now have to do all the mods again. :-\
Thanks for all your help Sohail.
Sent from my GT-I9300 using Tapatalk 2
Yeah..your welcome..just try out the CM9 nightlies or the paranoid android ROM..its amazing..u can see the screenshots in my album..chal..later
Hi, I was wondering if anyone can help me.
My tablet is unable to mount my /efs directory, or whatever. And while I don't know if they are directly connected,
things like my lock screen, holding my power button to get options like Flight Mode, Data Network, Restart, Etc., is gone. And I have tried screen lock to work, it doesn't. Holding my power button shuts my tablet down (in the same amount of
time that holding it would normally bring up the options screen, as well). I also loose completely my 3g, no matter wish successfully installed rom I run. I am not new to flashing rom at all and navigate trough all kind of step regarding specifics to rom by heart. All I can remember was to try the latest Android 4.1.1 - CyanogenMod 10 Preview and failed to load it, I was stuck in the boot animation for half an hour. So I decide to go back to the new stuck 4.0.4 from my provider. That is where I found the problem. Since, I have try 4.0.4 stuck, 4.04 rooted. The problem occur the same way in every rom and everything else was juste fine. I try the 3.1 stuck and 3.2 stuck and the message E: failed to mount /efs appear when rebooting from odin install.Never been able to load any version of the latest 4.1.1 from pershot. I have found a thread about the same issues from another device http://forum.xda-developers.com/showthread.php?t=1766748. I pass the entire day reading the web for solution, but no cigars so far.
I have the a Telus samsung galaxy tab 10.1 3g.
Thanks in advance if you have any idea how to resolve the /efs mounting problem.
I will added these picture to show that I have lost all important information that is apparently store in some file inside this /efs folder. Apparently this folder as been corrupt when flashing the CyanogenMod 10 Preview especially made for my tablet. So my new question would be to ask.
Do anyone know how to restore this folder even if I have no backup of it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
on off on off
try to copy the content of the efs folder with any root browser. it will have files and folders like in the screenshot atached.
Solved.
i had exactly the same problem. Was working on it for the last two days (ofcourse i am a simpleton and rookie )
But yes at last the phone is fixed and working fine with all the parameters.
So dont worry dear. Try to follow these steps : -
1. flash a rom using odin or heimdall - either stock or Cyanogenmod. You can check the repartition if using with the pit file.
2. Root your phone if not already rooted
3. Install busybox
4. Install kTool.apk (Its a small and wonderful apk. Freely available)
5. Install any file manager that supports root browsing
6. Make a backup of your efs with the help of kTool.apk (Its simple)
7. Decompress your earlier backup and copy all the files in the root efs folder with the root explorer
8. Now rename the one that you decompressed the files from as efs.img and copy it into the internal sdcard root
9. Now retore the egs.img using the kTool.apk
This will solve the problem i guess.
Good luck
8.
No file in /efs folder, and no backup
Thanks a lot for the answer guys, but unfortunately there is nothing inside my /efs folder. It's completely empty and therefore I can't copy it, move it backup it,or anything. I also have no backup of this folder. As I understand some file in this folder contain the super important information of my own system like IEME, Serial, etc... So my concern is more like is there is a way to restore this folder even if it doesn't exist. I think the answer is no and the only solution for me is to send it back to Samsung with the stuck roms from my provider and hope for them to not deny the repair so I won't have to pay. I wonder if there is other thing to do but I am pretty sure not. If someone know something let me know. I have already contact Samsung and tell them that my 3g is broken and some strange behavior occur during OTA update. They are going to send me something for me to send the tablet for reparation. Til then I really want to know if there is something I don't understand and if there is still hope. Anyway thanks in advance for anyone who know better then me.
This is EXACTLY what's going on with my tablet, and yes, there's nothing to copy. What do we do?
I originally edited my old post with this, but I wanted to be sure the OP saw it.
I finally fixed mine. See my thread at http://forum.xda-developers.com/showthread.php?t=1876260
I hope it helps
Hey
owner of a rooted galaxy note 2 with Eclipse V9 rom android version 4.4.4
i recently replaced my default_gain file because the volume in my headset was way too low for me to hear it while riding.
so i changed it. it worked just fine for a couple of days but now i cant hear anyone and they cant hear me.
its not a problem with the headset since its work just fine with other phones.
i think returning the original default_gain file back but it did not help.
DrCow said:
Hey
owner of a rooted galaxy note 2 with Eclipse V9 rom android version 4.4.4
i recently replaced my default_gain file because the volume in my headset was way too low for me to hear it while riding.
so i changed it. it worked just fine for a couple of days but now i cant hear anyone and they cant hear me.
its not a problem with the headset since its work just fine with other phones.
i think returning the original default_gain file back but it did not help.
Click to expand...
Click to collapse
Ask this question in the respective ROM thread.
RAZERZDAHACKER said:
Ask this question in the respective ROM thread.
Click to expand...
Click to collapse
i can ask there..but i doubt its related..
i changed my rom to this one like a month ago
DrCow said:
i can ask there..but i doubt its related..
i changed my rom to this one like a month ago
Click to expand...
Click to collapse
You CAN but the devs for that ROM probably hang out in their ROM thread and not in the Q&A FORUM. Thread and forum are not the same.
This problem is not rom related since they changed one of the default files.
When you replaced the file, did you set the permissions correctly and reboot? If you did and it still did not work, it might be a good idea to put the stock firmware back on with Odin and redo the rom.
es0tericcha0s said:
This problem is not rom related since they changed one of the default files.
When you replaced the file, did you set the permissions correctly and reboot? If you did and it still did not work, it might be a good idea to put the stock firmware back on with Odin and redo the rom.
Click to expand...
Click to collapse
im not sure what do you mean by setting the right permissions.. but i did reboot afterward. its currently back on the default file that came with the room
Files in the system must have the correct permissions for read/write access. Generally this is done with a file manager that has root permissions such as Root Explorer, ES File Explorer, etc.
You can find more information about this here: http://forum.xda-developers.com/showthread.php?t=1431543
es0tericcha0s said:
Files in the system must have the correct permissions for read/write access. Generally this is done with a file manager that has root permissions such as Root Explorer, ES File Explorer, etc.
You can find more information about this here: http://forum.xda-developers.com/showthread.php?t=1431543
Click to expand...
Click to collapse
i used ES. i did gave it permissions to R/W the files if that what you mean
DrCow said:
i used ES. i did gave it permissions to R/W the files if that what you mean
Click to expand...
Click to collapse
Yes. Is it set to 0644 as mentioned in the link provided? If so and it still doesn't work, then you can try just reflashing the rom first so you might not need to wipe the device. Just make sure you wipe cache and dalvik cache and reflash Eclipse.
If that does not work, then reflash stock and then redo recovery and rom.
es0tericcha0s said:
Yes. Is it set to 0644 as mentioned in the link provided? If so and it still doesn't work, then you can try just reflashing the rom first so you might not need to wipe the device. Just make sure you wipe cache and dalvik cache and reflash Eclipse.
If that does not work, then reflash stock and then redo recovery and rom.
Click to expand...
Click to collapse
Im not sure im following..
These are my ES settings
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DrCow said:
Im not sure im following..
These are my ES settingsView attachment 3890167
Click to expand...
Click to collapse
Those settings have nothing to do with what I mentioned. Please check out the link provided in my previous post.
es0tericcha0s said:
Those settings have nothing to do with what I mentioned. Please check out the link provided in my previous post.
Click to expand...
Click to collapse
Im probably looking really stupid right now..but i have no clue what settings i need to check
DrCow said:
Im probably looking really stupid right now..but i have no clue what settings i need to check
Click to expand...
Click to collapse
You need to check the permissions of the default xml file that you were messing with. Navigate to the file with ES and long press on it (I think...it has been years since I have used the app and know that it has changed a bit since then) to see the option to view the permissions for that file.
es0tericcha0s said:
You need to check the permissions of the default xml file that you were messing with. Navigate to the file with ES and long press on it (I think...it has been years since I have used the app and know that it has changed a bit since then) to see the option to view the permissions for that file.
Click to expand...
Click to collapse
i um..well i ****ed up
im just gonna try to re-flash and do a fresh start
who know? maybe it a sign i need to replace this phone..i had it for 3 years
Ok. Not really sure how you messed up just viewing the permissions, but good luck!