Files can't be deleted any more - Xoom Q&A, Help & Troubleshooting

Hi,
I hope it is o.k. to post this question in the Xoom forum!?
In the download folder of my Motorola Xoom there are several files that I can't delete any more.
These files are pdf- and/or mp3-files that originally had a German umlaut in their file name. By copying/pasting these files into the download directory, they were somehow damaged. Now, the filenames are showing some strange characters and the file sizes are 0 kB.
As soon as I try to delete one of those files, my Xoom shows a message, that the file can't be deleted.
I already tried out to use several different file explorers which didn't work.
Unfortunately, even "MyPhoneExplorer" can't delete the files by connecting the Xoom to the PC. There, the files don't show up.
Renaming of the files doesn't work either and overwriting the files using a new file with the same name also doesn't work.
Can somebody of you help me with this problem?
How can I get rid of these 0kB files?
Thanks a lot!

Its perfectly OK to ask questions, no problem this is to be a source of information. It should however be in the Q&A section. That said
You can try to delete the file using "android terminal emulator" app
In there enter the following command substituting the file name for whatever u r trying to delete
Code:
rm /sdcard/yourfilename.whatever
If that does not work and u r rooted you can try the same command after have superuser permission. Do this
Open terminal and enter
Code:
su
Press enter after that and allow superuser, then enter the same command above.
Attached is a screen shot of what it should look like
{
"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"
}
Sent from my Galaxy Nexus using Tapatalk 2

runandhide05 said:
Its perfectly OK to ask questions, no problem this is to be a source of information. It should however be in the Q&A section. That said
You can try to delete the file using "android terminal emulator" app
In there enter the following command substituting the file name for whatever u r trying to delete
Code:
rm /sdcard/yourfilename.whatever
If that does not work and u r rooted you can try the same command after have superuser permission. Do this
Open terminal and enter
Code:
su
Press enter after that and allow superuser, then enter the same command above.
Attached is a screen shot of what it should look like
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your idea! ...unfortunately it doesn't work
Problem seems to be the filename. It was corrupted while unpacking files from a packed archive. The original filename contained several so called"umlaute" (German special characters) which the system on the Xoom obviously can't handle correctly. These "umlaute" characters were replaced by some other curious characters during extraction.
Example: "11. ڵoԠ(ڢer-unter-ober-Գterreicher).mp3" is the filename after unpacking the file. Before, it was " 11. Üuoö (Über-unter-ober-österreicher).mp3"
As soon as I try to remove the file, a message appears, telling me that there is no such file. At the same time, the terminal shows the corrupted filename, but suppressing the corrupted characters.
No chance to delete :crying:
I hope, I could explain it so that you can understand what happens (or what doesn't happen). Any further ideas?
Thanks a lot!
PS: corrupted files are not only mp3 but also some pdf and doc files. All of them show up with a size of 0Byte on the Xoom, while the original file size is shown as soon as I connect the Xoom to my PC using MyPhoneExplorer (which, btw, also isn't able to delete)

deb10042 said:
Thanks for your idea! ...unfortunately it doesn't work
Problem seems to be the filename. It was corrupted while unpacking files from a packed archive. The original filename contained several so called"umlaute" (German special characters) which the system on the Xoom obviously can't handle correctly. These "umlaute" characters were replaced by some other curious characters during extraction.
Example: "11. ڵoԠ(ڢer-unter-ober-Գterreicher).mp3" is the filename after unpacking the file. Before, it was " 11. Üuoö (Über-unter-ober-österreicher).mp3"
As soon as I try to remove the file, a message appears, telling me that there is no such file. At the same time, the terminal shows the corrupted filename, but suppressing the corrupted characters.
No chance to delete :crying:
I hope, I could explain it so that you can understand what happens (or what doesn't happen). Any further ideas?
Thanks a lot!
PS: corrupted files are not only mp3 but also some pdf and doc files. All of them show up with a size of 0Byte on the Xoom, while the original file size is shown as soon as I connect the Xoom to my PC using MyPhoneExplorer (which, btw, also isn't able to delete)
Click to expand...
Click to collapse
Are the files located in a directory by them selves? If so u can try to remove the directory itself
Sent from my Galaxy Nexus using Tapatalk 2

runandhide05 said:
Are the files located in a directory by them selves? If so u can try to remove the directory itself
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Some of them are, others not. It makes no difference. If I try to delete an entire directory, containing one of those corrupted files, the whole directory can't be deleted. Anyway, "normal" files (uncorrupted) in the relevant directory can be removed individually... except those 0-Byte-files

No more ideas? ....anyone?
I can't believe, that it should really be impossible to delete corrupted files

Are u rooted? I just had the same problem. Simple boot into twrp and delete thru the built in file manager
Sent from my Galaxy Nexus using Tapatalk 2

runandhide05 said:
Are u rooted? I just had the same problem. Simple boot into twrp and delete thru the built in file manager
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes, I am rooted. but I have CWM on my Xoom. I found the thread about TWRP in the Nexus section. will it also work for the Motorola Xoom?
Can I install it instead of CWM without loosing all my apps and data?
Thanks!

deb10042 said:
Yes, I am rooted. but I have CWM on my Xoom. I found the thread about TWRP in the Nexus section. will it also work for the Motorola Xoom?
Can I install it instead of CWM without loosing all my apps and data?
Thanks!
Click to expand...
Click to collapse
Look at my signature, its twrp for our xoom
Sent from my Galaxy Nexus using Tapatalk 2

when using the terminal rm command you need to escape special characters ( i.e spaces, parenthese etc ) with a backslash or put the file name in quotes. so you file name in question can be removed by
Code:
rm 11.\ Üuoö\ \(Über-unter-ober-österreicher\).mp3
or
Code:
rm "11. Üuoö (Über-unter-ober-österreicher).mp3"
you can also do wildcard deletion based on fragements of the file name i.e
Code:
rm 11*.mp3
will delete all files that start with 11 with the mp3 externsion or you could start with a wildcard so a named example_file_name.txt can be deleted using
Code:
rm *file*.txt
obviously that will delete ALL files that have the word file in the filename and an extension of .txt so BE CAREFUL WHEN USING WILDCARDS but you get the idea ( hopefully )
If that doesn't delete them then you've got problems.
---------- Post added at 01:06 PM ---------- Previous post was at 12:54 PM ----------
A little tip, If you're not from the old school you won't know that it best to avoid spaces and special characters in filenames especially as your transferring between different filesystem types, obviously unicode characters are kinda inevitable if that's you native language but a demestorated here there's not 100% support for it, mostly due to westernized developers not taking into account internationalization!
TRIVIA: Early versions of MSDOS only allowed eight characters for a filename with a 3 characters extension. Imagine working with those constraints!

I had the same problem. The only solution is:
Install TWRP http://forum.xda-developers.com/showthread.php?t=1782235
Reboot in recovery. Explore the files and delete whatever you want..

he e
trevd said:
when using the terminal rm command you need to escape special characters ( i.e spaces, parenthese etc ) with a backslash or put the file name in quotes. so you file name in question can be removed by
Code:
rm 11.\ Üuoö\ \(Über-unter-ober-österreicher\).mp3
or
Code:
rm "11. Üuoö (Über-unter-ober-österreicher).mp3"
you can also do wildcard deletion based on fragements of the file name i.e
Code:
rm 11*.mp3
will delete all files that start with 11 with the mp3 externsion or you could start with a wildcard so a named example_file_name.txt can be deleted using
Code:
rm *file*.txt
obviously that will delete ALL files that have the word file in the filename and an extension of .txt so BE CAREFUL WHEN USING WILDCARDS but you get the idea ( hopefully )
If that doesn't delete them then you've got problems.
---------- Post added at 01:06 PM ---------- Previous post was at 12:54 PM ----------
A little tip, If you're not from the old school you won't know that it best to avoid spaces and special characters in filenames especially as your transferring between different filesystem types, obviously unicode characters are kinda inevitable if that's you native language but a demestorated here there's not 100% support for it, mostly due to westernized developers not taking into account internationalization!
TRIVIA: Early versions of MSDOS only allowed eight characters for a filename with a 3 characters extension. Imagine working with those constraints!
Click to expand...
Click to collapse
Thanks, but it doesn't work. No matter if I use the backslash- or the paranthesis method, the emulator always tells me that it could not deleze as there is no such file or directory.

deb10042 said:
he e
Thanks, but it doesn't work. No matter if I use the backslash- or the paranthesis method, the emulator always tells me that it could not deleze as there is no such file or directory.
Click to expand...
Click to collapse
Just use TWRP if your unlocked. It will take care of it. ( see link in my sig)

Success!!
runandhide05 said:
Just use TWRP if your unlocked. It will take care of it. ( see link in my sig)
Click to expand...
Click to collapse
Finally, I gathered all my courage and installed TWRP over my old CWM Recovery without doing any backups
And...yes, it did the trick!!
I was able to delete all the corrupted files and folders and everything else is still in place :good:
Thanks for your good help!

deb10042 said:
Finally, I gathered all my courage and installed TWRP over my old CWM Recovery without doing any backups
And...yes, it did the trick!!
I was able to delete all the corrupted files and folders and everything else is still in place :good:
Thanks for your good help!
Click to expand...
Click to collapse
Glad you got it working! Now would be a good time to make a backup with twrp because cwm backups will not work with twrp and vice versa

runandhide05 said:
Glad you got it working! Now would be a good time to make a backup with twrp because cwm backups will not work with twrp and vice versa
Click to expand...
Click to collapse
Oups! :cyclops:
Thanks, that was really a good hint! Didn't know that and will do it at once after coming home this evening
Will it be difficult, to go back to CWM? ...just in case...

Related

[HOW-TO] Stock Apps for All!

After two days of fumbling around with adb, numerous nandroid backups, and ultimately wiping my system, I, with the help of my friend Kiraly (his xda username), have successfully installed the stock Messaging, Clock, Calculator and Browser apps onto my phone.
The Messaging app was of particular interest to me because I hate how the HTC Sense Messaging app always loads briefly when you enter a thread of messages, no matter how many messages are in the actual thread. Also, the stock Android Messaging app has a feature similar to BBM in that an icon within the thread notifies you when a message has actually sent.
By following the instructions contained hereunder, you agree to indemnify and hold harmless the original poster (the "OP"). I hereby disclaim all warranties and liability for any harm that may result by following the aforementioned instructions.
Installing these apps was fairly easy once we found out how it needed to be done. You will need the following:
A. Minimal knowledge of adb, or rather knowledge of how to copy and paste adb commands.
B. You will need full root (root and nand unlocked)
C. 1.47 kernel with the modified default.prop file http://forum.xda-developers.com/showthread.php?p=7138666
D. The Root Explorer app (this can be purchased in the Android Market)
E. You will need the following .apk files from BuglessBeast. They are the only apps that I have been able to successfully install. http://forum.xda-developers.com/showthread.php?t=700175
-Mms.apk
-Browser.apk
-DeskClock.apk
-Calculator.apk
STEP 1
Perform a nandroid backup.
STEP 2
Plug your phone into your computer via USB and mount the sd card.
STEP 3
Download the 1.47 kernel with the modified default.prop file. The stock kernel is also contained in the following link, and you can always revert back to it if need be. http://forum.xda-developers.com/showthread.php?p=7138666
STEP 4
Flash the modified 1.47 kernel .zip file to the root of your sd card (for all you rookies out there, simply drag the .zip file onto your sd card).
STEP 5
Reboot into recovery and install the kernel you just flashed. Then, reboot the phone.
STEP 6
Download the BuglessBeast ROM http://forum.xda-developers.com/showthread.php?t=700175
STEP 7
Unzip the BuglessBeast file. Open the unzipped file. Find the folder labeled "System", and open it. Then, find the folder labeled "App", and open it. Find the files labeled Mms.apk, Browser.apk, DeskClock.apk and Calculator.apk. Drag those files to your desktop.
STEP 8
Download and open the Root Explorer app. Scroll down to the bottom and click on the folder labeled "System." Then, at the top of the app, click "Mount R/W." After you click that, open the "app" folder. Each application has two files you need to delete. Do not delete any of the clock files. You will need to delete the following files and then quit the application when you have finished:
-Browser.apk
-Browser.odex
-Mms.apk
-Mms.odex
-Calculator.apk
-Calculator.odex
STEP 9
Open the Command Prompt if you are a Windows user or the Terminal application if you are a Mac user and navigate to the tools folder of the Android SDK. Do not boot into recovery.
STEP 10
Type the following commands in order. We will use the Browser.apk as an example, and I will assume the file is on your desktop:
Code:
adb shell
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
Code:
exit
Code:
adb push C:\Users\YourUserName\Browser.apk /system/app
Code:
adb shell
Code:
chmod 6755 /system/app/Browser.apk
Code:
exit
Code:
adb reboot
STEP 11
Rinse and repeat!
Thanks to frankenstein\ for the kenel, laydros for getting me started in the right direction, BuglessPete for the .apk files, and most importantly to Kiraly for all his assistance.
{
"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"
}
<3
10 char
I hope the push command is correct. On my Mac, when the files is on my desktop, the command is:
/adb push /Users/kpoz/Desktop/Browser.apk /system/app
Someone please let me know if the push command is not correct for Windows.
kpoz said:
I hope the push command is correct. On my Mac, when the files is on my desktop, the command is:
/adb push /Users/kpoz/Desktop/Browser.apk /system/app
Someone please let me know if the push command is not correct for Windows.
Click to expand...
Click to collapse
I'm using Ubuntu but I have a Windows lappy around with adb setup, I'll test it out and let you know.
neckface said:
I'm using Ubuntu but I have a Windows lappy around with adb setup, I'll test it out and let you know.
Click to expand...
Click to collapse
Great, thanks. I almost forgot to delete the "./" before "adb" when I was writing the tutorial. For whatever reason, on a Mac the command is ./adb, and on Windows it is simply adb.
kpoz said:
Great, thanks. I almost forgot to delete the "./" before "adb" when I was writing the tutorial. For whatever reason, on a Mac the command is ./adb, and on Windows it is simply adb.
Click to expand...
Click to collapse
Yup, same with Linux.
Just replaced the Sense Mms app with the stock one using this technique and it worked perfectly. Only thing I did differently was rather than deleting the stock files I just renamed them with a *.bak for easy restoring in case I ever need to.
Also I'm using Netarchy's kernel [FPS fix] and I did not need to do all the steps with the default.prop, I was able to mount the system folder with write permission.
And in case anyone is like me and just wants to replace the messaging app rather than all of them, I'll attach the apk for much quicker downloading. Its the apk straight out of the BuglessBeast ROM.
kpoz said:
I hope the push command is correct. On my Mac, when the files is on my desktop, the command is:
/adb push /Users/kpoz/Desktop/Browser.apk /system/app
Someone please let me know if the push command is not correct for Windows.
Click to expand...
Click to collapse
Push command is correct for windows. It may vary slightly depending on where you placed the apk files.
tehpsyc said:
Just replaced the Sense Mms app with the stock one using this technique and it worked perfectly. Only thing I did differently was rather than deleting the stock files I just renamed them with a *.bak for easy restoring in case I ever need to.
Also I'm using Netarchy's kernel [FPS fix] and I did not need to do all the steps with the default.prop, I was able to mount the system folder with write permission.
And in case anyone is like me and just wants to replace the messaging app rather than all of them, I'll attach the apk for much quicker downloading. Its the apk straight out of the BuglessBeast ROM.
Click to expand...
Click to collapse
Glad it worked for you! Thanks for attaching the Mms.apk.
I'm glad that slow, unresponsive Sense Messages app is long gone. You know there is something wrong with your app (*cough, HTC, *cough) when you get a "Loading" message when opening a thread, regardless of how many messages are in said thread.
initial said:
Push command is correct for windows. It may vary slightly depending on where you placed the apk files.
Click to expand...
Click to collapse
Thanks for confirming.
tehpsyc said:
Just replaced the Sense Mms app with the stock one using this technique and it worked perfectly. Only thing I did differently was rather than deleting the stock files I just renamed them with a *.bak for easy restoring in case I ever need to.
Also I'm using Netarchy's kernel [FPS fix] and I did not need to do all the steps with the default.prop, I was able to mount the system folder with write permission.
And in case anyone is like me and just wants to replace the messaging app rather than all of them, I'll attach the apk for much quicker downloading. Its the apk straight out of the BuglessBeast ROM.
Click to expand...
Click to collapse
What is the sense messenger app called? I can't find anything resembling it.
Here's a list of my HTC programs.
Code:
# ls /system/app/*htc*
/system/app/com.htc.MusicWidget.apk
/system/app/com.htc.NewsReaderWidget.apk
/system/app/com.htc.TwitterWidget.apk
/system/app/com.htc.WeatherWidget.apk
/system/app/htcbookmarkwidget.apk
/system/app/htccalendarwidgets.apk
/system/app/htccontactwidgets.apk
/system/app/htcmailwidgets.apk
/system/app/htcmsgwidgets.apk
/system/app/htcsearchwidgets.apk
/system/app/htcsettingwidgets.apk
I see the htc messenger widget but do I have to get rid of that? I don't think that's the messenger application file.
initial said:
What is the sense messenger app called? I can't find anything resembling it.
Here's a list of my HTC programs.
Code:
# ls /system/app/*htc*
/system/app/com.htc.MusicWidget.apk
/system/app/com.htc.NewsReaderWidget.apk
/system/app/com.htc.TwitterWidget.apk
/system/app/com.htc.WeatherWidget.apk
/system/app/htcbookmarkwidget.apk
/system/app/htccalendarwidgets.apk
/system/app/htccontactwidgets.apk
/system/app/htcmailwidgets.apk
/system/app/htcmsgwidgets.apk
/system/app/htcsearchwidgets.apk
/system/app/htcsettingwidgets.apk
I see the htc messenger widget but do I have to get rid of that? I don't think that's the messenger application file.
Click to expand...
Click to collapse
The Sense Messenger app is called Mms.apk. Delete the Mms.apk and Mms.odex files. It's in the OP
Do not delete htcmessengeruploader.
kpoz said:
The Sense Messenger app is called Mms.apk. Delete the Mms.apk and Mms.odex files. It's in the OP
Do not delete htcmessengeruploader.
Click to expand...
Click to collapse
Oh didn't realize it was the same. I'm using DamageControl's ROM and assumed HTC had a different label for some reason. Thanks for clearing that up.
In any case, I got a few FCs here and there and MMS is failing to send on the DC ROM. I'll tinker with it some more and see if I can figure something out.
btw, if anyone is doing this on DC's ROMs then don't bother looking for any *.odex files since his rom is de'odexed.
initial said:
Oh didn't realize it was the same. I'm using DamageControl's ROM and assumed HTC had a different label for some reason. Thanks for clearing that up.
In any case, I got a few FCs here and there and MMS is failing to send on the DC ROM. I'll tinker with it some more and see if I can figure something out.
btw, if anyone is doing this on DC's ROMs then don't bother looking for any *.odex files since his rom is de'odexed.
Click to expand...
Click to collapse
Originally, Kiraly and I tried pushing these files and then using a shell to install them, but it resulting in a ton of force closes. We couldn't open any of the apps.
Regrettably, I'm not savvy enough to attempt to fix this issue for you if you are running a ROM like DC, especially a deodexed ROM. Best of luck to you.
Maybe the install command will work for you where it failed for me.
Try the following:
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
exit
adb push :\Users\YourUserName\Browser.apk /sdcard
adb shell
install /sdcard/Browser.apk /system/app
exit
adb reboot

[Q] Nexus S voice/sound recorder hidden and not installed?

Hi,i was searching for the stock voice recorder in Ice Cream Sandwich,but i did not find it...
So I've searched into phone memory (root /system/app) and i found Soundrecorde.apk ,bu if i try to install it,installation aborts saying "This application cannot be installed".
Why?
No one use voice recording on Ics?
Neo on Nexus S with Tapatalk®
bump?.......
.:Crack:. said:
bump?.......
Click to expand...
Click to collapse
???
Neo on Nexus S with Tapatalk®
..
Election Day said:
It indeed doesn't seem to work. Just like Tag.apk, SoundRecorder.apk does not show up in the app drawer, even if it's in /system/app. Apparently it just isn't compatible.
What about some Market apps?
Click to expand...
Click to collapse
There is not much compatibility for this kind of apps and Ics...
Stock Sound recorder was perfect for me on Gingerbread,i don't understand why it's not compatible anymore...
Neo on Nexus S with Tapatalk®
not sure how you tried to install but you cant install system apps like other apk you have to sign it first....anyways i signed it and installed fine but dont give an option to open after install and still don't see it
edit
just for future reference if you edit an apk or want to install a system app like a normal apk
download Sighnapktic from the market its free and it does it right from your phone really easy to use
https://market.android.com/details?id=com.stericson.signapktic&hl=en
i used Sanity with gingerbread, but I don't know if it still works with ICS
https://market.android.com/details?..._result#?t=W251bGwsMSwxLDEsImNyaS5zYW5pdHkiXQ..
Election Day said:
It indeed doesn't seem to work. Just like Tag.apk, SoundRecorder.apk does not show up in the app drawer, even if it's in /system/app. Apparently it just isn't compatible.
What about some Market apps?
Click to expand...
Click to collapse
Both of those apps don't show in the drawer because the "LAUNCHER" intent lines in their respective AndroidManifest.xmls are not present/were omitted that instruct the app to be visible in the drawer.
To the best of my recollection, SoundRecorder never officially included the lines because it was supposed to be present solely as a function for other apps to use, despite it having an actual interface. Tag, on the other hand, appears to have had those lines removed in the transition to ICS. Adding the intents in their manifests will cause them to show up in the drawer again.
XK72 said:
Both of those apps don't show in the drawer because the "LAUNCHER" intent lines in their respective AndroidManifest.xmls are not present/were omitted that instruct the app to be visible in the drawer.
To the best of my recollection, SoundRecorder never officially included the lines because it was supposed to be present solely as a function for other apps to use, despite it having an actual interface. Tag, on the other hand, appears to have had those lines removed in the transition to ICS. Adding the intents in their manifests will cause them to show up in the drawer again.
Click to expand...
Click to collapse
Once added,will the app works with its interface?
Neo on Nexus S with Tapatalk®
..
(THE REAL) Neo said:
Once added,will the app works with its interface?
Neo on Nexus S with Tapatalk®
Click to expand...
Click to collapse
{
"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"
}
Correct.
Election Day said:
Probably yes. I'm trying to modify the xml's at the moment, but I can't get any usable output.
If I can get it to work I'll post the modded apk here.
Click to expand...
Click to collapse
Directly after this line:
Code:
<action android:name="android.intent.action.MAIN" />
Add:
Code:
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.LAUNCHER" />
..
You also just can use anycut from market and create a homescreen shortcut to soundrecorder.apk
Election Day said:
I guess this should be it. I unpacked the apk with apktool, added the lines, packed it again, unzipped it, added META-INF and rezipped it.
You can flash it with "adb push SoundRecorder.zip /system/app".
Click to expand...
Click to collapse
No changes here...i've copied the file in sistem/app,but nothing changes.
Neo on Nexus S with Tapatalk®
(THE REAL) Neo said:
No changes here...i've copied the file in sistem/app,but nothing changes.
Neo on Nexus S with Tapatalk®
Click to expand...
Click to collapse
I haven't looked at the attached APK yet, but try these steps:
I'm not sure if it's because the instructions have you install a ZIP file that doesn't exist (because the attachment is an APK).
The command should be: adb push SoundRecorder.apk system/app
If you happened to have changed the command to APK anyway, make sure that you specify the right path for the file
(e.g. adb push path/to/downloaded/file/SoundRecorder.apk system/app) or that you are in the same directory as the file (then use the command listed above).
If the file got pushed successfully, you may need to reboot your phone for the changes to take effect.
Try that out and if you're still not having any luck, let me know what ADB tells you. If it helps, I'll build a version with the Launcher icon visible that'll work.
XK72 said:
I haven't looked at the attached APK yet, but try these steps:
I'm not sure if it's because the instructions have you install a ZIP file that doesn't exist (because the attachment is an APK).
The command should be: adb push SoundRecorder.apk system/app
If you happened to have changed the command to APK anyway, make sure that you specify the right path for the file
(e.g. adb push path/to/downloaded/file/SoundRecorder.apk system/app) or that you are in the same directory as the file (then use the command listed above).
If the file got pushed successfully, you may need to reboot your phone for the changes to take effect.
Try that out and if you're still not having any luck, let me know what ADB tells you. If it helps, I'll build a version with the Launcher icon visible that'll work.
Click to expand...
Click to collapse
Tried this and it didn't worked for me. I get this error from adb:
failed to copy 'SoundRecorder.apk' to 'system/app/SoundRecorder.apk': Permission denied
XK72 said:
I haven't looked at the attached APK yet, but try these steps:
I'm not sure if it's because the instructions have you install a ZIP file that doesn't exist (because the attachment is an APK).
The command should be: adb push SoundRecorder.apk system/app
If you happened to have changed the command to APK anyway, make sure that you specify the right path for the file
(e.g. adb push path/to/downloaded/file/SoundRecorder.apk system/app) or that you are in the same directory as the file (then use the command listed above).
If the file got pushed successfully, you may need to reboot your phone for the changes to take effect.
Try that out and if you're still not having any luck, let me know what ADB tells you. If it helps, I'll build a version with the Launcher icon visible that'll work.
Click to expand...
Click to collapse
I've not used adb,but manually copied the .apk to system/app after renaming of original file.
Obviously i've used EsGestore File,with root permissions/root mounted read and write.
File copied perfectly,rebooted phone.
But nothing happens...
Neo on Nexus S with Tapatalk®
jitzbox said:
Tried this and it didn't worked for me. I get this error from adb:
failed to copy 'SoundRecorder.apk' to 'system/app/SoundRecorder.apk': Permission denied
Click to expand...
Click to collapse
This may not be the most efficient way of doing this, but it always works for me. Assuming that you have root permissions on the phone, try the following steps:
Access the phone through ADB:
Code:
adb shell
Mount the volume as writable:
Code:
mount -o remount,rw /dev/block/mtdblock4 /system
Remove the existing SoundRecorder.apk file:
Code:
rm system/app/SoundRecorder.apk
Exit ADB:
Code:
exit
Copy the APK file (attached below) from your system to your phone, replacing path/to/file with the location of your file (e.g. c:\android) as detailed in previous post.
Code:
adb push [I]path/to/file/[/I]SoundRecorder.apk system/app
Reboot phone (might be optional):
Code:
adb reboot
(THE REAL) Neo said:
I've not used adb,but manually copied the .apk to system/app after renaming of original file.
Obviously i've used EsGestore File,with root permissions/root mounted read and write.
File copied perfectly,rebooted phone.
But nothing happens...
Neo on Nexus S with Tapatalk®
Click to expand...
Click to collapse
I'm sorry, I'm not familiar with using third-party apps for file management duties. Assuming that everything else you're doing is correct, try using the APK file attached below.
XK72 said:
This may not be the most efficient way of doing this, but it always works for me. Assuming that you have root permissions on the phone, try the following steps:
Access the phone through ADB:
Code:
adb shell
Mount the volume as writable:
Code:
mount -o remount,rw /dev/block/mtdblock4 /system
Remove the existing SoundRecorder.apk file:
Code:
rm system/app/SoundRecorder.apk
Exit ADB:
Code:
exit
Copy the APK file (attached below) from your system to your phone, replacing path/to/file with the location of your file (e.g. c:\android) as detailed in previous post.
Code:
adb push [I]path/to/file/[/I]SoundRecorder.apk system/app
Reboot phone (might be optional):
Code:
adb reboot
I'm sorry, I'm not familiar with using third-party apps for file management duties. Assuming that everything else you're doing is correct, try using the APK file attached below.
Click to expand...
Click to collapse
Using this apk,the phone shows me an app called "Recorder" in the app drawer,but i can't tap it,and all the icons showed in the same page of the app drawer.If i change page,icons of other pages are selectable...weird thing...
Now i'm rolled back to previous apk file and everything works...so scary...
Neo on Nexus S with Tapatalk®

Supercharged Dropdown Toggles

Here's a couple alterations to the quickpanel toggles in the dropdown of Supercharged V4 (the 3rd one is the original if you want to revert back).
You need to replace your SystemUI.apk found in /system/app/
cogeary said:
Here's everything you need to do, make sure you follow the directions exactly (especially with renaming)
-Download one of the .apk's
-Rename it to "SystemUI.apk" without the quotes. Note that .apk is the file extension, and on windows by default you can't change the file extension just by a simple right click->rename, so just make sure that the file is called "SystemUI.apk" and not "SystemUI.apk.apk"
-Connect your phone to your computer. Select any type of USB Connection other than "Charge Only."
-Drag and drop the "SystemUI.apk" directly into your phone's storage "In "My Computer" or "Computer)
-You can change the connection type to "charge only" now
-Open up a command prompt (Start->Search/Run->cmd.exe
-Make sure you have the android SDK set up and you have adb in your PATH... or you have a functioning method to access adb
-Now inside the command prompt, type:
adb shell
su
cp /sdcard/SystemUI.apk /system/app/
reboot
-Your phone will reboot and the notification toggles should be installed!
Click to expand...
Click to collapse
Let me know how you all like it and if I should change them. I was going for toggles that were more distinct from their on/off states. Hit the "thanks" if you like 'em and enjoy!
First:
{
"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"
}
Second:
No Bars:
Thanks to lfaber06 for the great ROM we have available to us.
Hey so i was jw... will this be on supercharged v5? Either way. Nice job!
Deliberate said:
Hey so i was jw... will this be on supercharged v5? Either way. Nice job!
Click to expand...
Click to collapse
I have no idea if lfaber06 will include it. I'm perfectly fine with that if he chooses so. Thanks for the compliment!
Is he working on a v5? Jw. I guess I should of asked him. But still to new for the development section. Lol
Looks great. Was wondering if it was possible to remove the blue indicator line all together since its not really needed now. Would clean it up some and go better theme-wise for those who have different colors in their status bar icons.
Thanks a lot if you can do it!
loderjm said:
Looks great. Was wondering if it was possible to remove the blue indicator line all together since its not really needed now. Would clean it up some and go better theme-wise for those who have different colors in their status bar icons.
Thanks a lot if you can do it!
Click to expand...
Click to collapse
I can do that this evening when I get back home. Shouldn't be too hard (just set full transparency to 3 images).
Sent from my MB865 using XDA App
loderjm said:
Looks great. Was wondering if it was possible to remove the blue indicator line all together since its not really needed now. Would clean it up some and go better theme-wise for those who have different colors in their status bar icons.
Thanks a lot if you can do it!
Click to expand...
Click to collapse
It's up now. There is a way to get rid of the padding under the icons (since the bars are no longer there--well, they're actually there, but invisible), but I'd rather not tackle that right now. It involves xml edits that I've done before (back in my Captivate days ), but I don't remember exactly and would rather not spend the time right now (sorry).
I hope it's what you had in mind.
Awesome. Looks great. Thanks for the quick turnaround!
so i dont know what im doing wrong but when i put the file in the root of my sd and do all the adb shell stuff. IDK but it reads everything but the file?
what am i doing wrong?
Deliberate said:
so i dont know what im doing wrong but when i put the file in the root of my sd and do all the adb shell stuff. IDK but it reads everything but the file?
what am i doing wrong?
Click to expand...
Click to collapse
Do you mean you do the
cp /sdcard/SystemUI.apk /system/app/
but it doesn't actually copy it over? Do you get an error when you try this? If you do this with your phone on, you will get a force close right away and then you need to type "reboot" while still in the adb shell and then your phone will reboot and everything is cool.
Could you explain a little more of what you did? I'll try to help, but I'm not very experienced with adb yet (Jim or lfaber06 among others and tutorials can help better with this).
Ya i put adb shell
Su
Then that code and it said there was no such file. I renamed it though
Do you see the file on your sdcard as "SystemUI.apk" without the quotes? This is what it needs to be (I assumed that's what you mean when you renamed it, but just making sure). If it's not that exact name, it won't overwrite the old one in /system/app/. Also make sure you have permissions set to write to /system/ (I actually would just use rom toolbox or something and use the script in there).
If nothing else, have you tried to reboot both your phone and computer? Sorry I can't be more help. I personally had the files named on my computer to "SystemUI.apk" before putting it on my sdcard (instead of renaming it after it's already on the phone). That might be something else to try, but I doubt that would be the reason. Someone smarter than I could probably figure it out.
Ya im not so good with adb... and also is it possible to do this with the phone off? If so how? Thank u for your reply by the way!
Deliberate said:
Ya im not so good with adb... and also is it possible to do this with the phone off? If so how? Thank u for your reply by the way!
Click to expand...
Click to collapse
I'm in the same boat with you on the adb thing . I'm making guesses on what it might be without truly understanding how to efficiently use adb. I believe you can use it with the phone off, but I haven't tried yet. Ultimately, I hope to get around to making a flashable zip for things like this. However, I need to spend a little less time tinkering for right now (and I brought my phone back to stock in preparation/hope of the pre-release soak). Let me know if you figure anything out (I'd like to learn as well).
I tried renameing it from my computer and from my phone and it still didnt work. How do u set the permissions from adb? Sorry for so many questions. I just really suck at adb.
---------- Post added at 10:23 AM ---------- Previous post was at 10:10 AM ----------
Ya i will for sure. Prerelease soak? Are u gonna be one of the update testers? Has that been decided yet?
I used this to mount it as write (after "adb shell" and "su"):
mount -o rw,remount /dev/block/stl9 /system
I found this thread useful for adb:
http://forum.xda-developers.com/showthread.php?t=872128
Deliberate said:
I tried renameing it from my computer and from my phone and it still didnt work. How do u set the permissions from adb? Sorry for so many questions. I just really suck at adb.
---------- Post added at 10:23 AM ---------- Previous post was at 10:10 AM ----------
Ya i will for sure. Prerelease soak? Are u gonna be one of the update testers? Has that been decided yet?
Click to expand...
Click to collapse
I hope I will be...I filled out the survey pretty quick after getting the email [fingers-crossed]. I haven't heard anything since (Sunday).
One other thought I just had:
When you rename the file, did it show the extension (.apk) or just SystemUI_second (or whichever one you're trying to use)? I'm wondering if by renaming it "SystemUI.apk" that it's actually seeing "SystemUI.apk.apk" or something. Doubtful, but just another thing to check.
No i wonderd that 2 so i tried SystemUI without anything and it still didnt work. Idk. Thanks for all your help though and good luck with the soak!
Oops sorry forgot to turn the page, didn't see the whole next page of replies XD
Anyways... just making sure, when you say you did "Su" did you type in "su" or "Su"?
Here's everything you need to do, make sure you follow the directions exactly (especially with renaming)
-Download one of the .apk's
-Rename it to "SystemUI.apk" without the quotes. Note that .apk is the file extension, and on windows by default you can't change the file extension just by a simple right click->rename, so just make sure that the file is called "SystemUI.apk" and not "SystemUI.apk.apk"
-Connect your phone to your computer. Select any type of USB Connection other than "Charge Only."
-Drag and drop the "SystemUI.apk" directly into your phone's storage "In "My Computer" or "Computer)
-You can change the connection type to "charge only" now
-Open up a command prompt (Start->Search/Run->cmd.exe
-Make sure you have the android SDK set up and you have adb in your PATH... or you have a functioning method to access adb
-Now inside the command prompt, type:
adb shell
su
cp /sdcard/SystemUI.apk /system/app/
reboot
Click to expand...
Click to collapse
-Your phone will reboot and the notification toggles should be installed!

[MultiTool][28/5/13]ROM TOOLS v3(dex de/recompiler with extended features)

Hi guys,
Here is third version of my ROM Tools PC Version (Automatic decompile classes.dex file to edit smali content). It is major release of this tool but further updates will follow.
After testing the third version on bunch of Devices successfully, here is the general release of it. This tool has been mainly constructed to decompile and recompile classes.dex of apk's and jar files without having to tediously type whole commands. However, there are few features I have added in it which in my opinion are useful bt not that much connected to dex operations.
What's New ?
Here is list of New features and detailed description of them:
Note:- No other fetaure except decompiling/recompiling will work if you have not connected your phone via USB cable and USB debugging is on.
Reboot Options:
Reboot:
Will normally reboot the phone
Necessary when replaced some framework file or pushed a system file
Code used
Code:
adb reboot
Click to expand...
Click to collapse
Recovery:
Reboot your phone in recovery mode
Necessary when thinking of flashing something and want to save time and instead of pressing a combo while phone is turned off.
Code used:
Code:
adb reboot recovery
Click to expand...
Click to collapse
Hot reboot: *May not work on all phones*
Reboots your phone faster
It reboots your phone faster by just killing all system processes forcing the GUI to restart. Preferred as its fast and reliable when pushing themed files. Not recommended if doing more intensive replacing(Sometimes syetem needs rebooting normally to show changes)
Code Used:
Code:
adb shell killall system_server
Click to expand...
Click to collapse
Miscellaneous:
logcat:
1. Display logcat:
Displays logcat with v long formatting with 10000+ lines.
Easy than typing whole command. Its with formatting. Has more lines than normal command prompt display
Code Used:
Code:
adb logcat -v long
Click to expand...
Click to collapse
2. Save logcat:
Saves logcat in main folder. A random prefix is added to each locat so that they do not get replaced by newer one.
Easier than typing the command. With good formatting.
Code used:
Code:
adb logcat -v long > logcat%random%.txt
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Fix permissions: *ignore errors*
Fixes permissions of /system/app, /system/framework/, system/etc/init.d
Necessary when replacing many files in system and saving time to set correct permissions. Sometimes, due to incorrect permissions, phone won't boot or scripts won't run. Very useful command to save you from these headaches.
Ignore errors because there may not be init.d folder present in your device. So it will show error for that, but all other permissions will be corrected
Code Used:
Code:
adb shell chmod 644 /system/app/*
adb shell chmod 644 /system/framework/*
adb shell chmod 777 /system/etc/init.d
adb shell chmod 777 /system/etc/init.d/*
Click to expand...
Click to collapse
Reset Password: *May not work on all devices* *Ignore errors*
Resets your pin, password, pattern lockscreen
Ignore errors because it will try to delete 4 files and there will be only one correct file to be deleted based on what type of password you have set.
May not work on all devices because I have only tested it on Gingerbread Samsung devices. *Confirmed to be working on rooted mobiles only*
Code Used:
Code:
adb shell rm /data/system/gesture.key
adb shell rm /data/system/password.key
adb shell rm /sd-ext/system/gesture.key
adb shell rm /sd-ext/system/passwork.key
Click to expand...
Click to collapse
Screenshot:
{
"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"
}
Changelog :
Code:
Version 3
28 Ma 2013
-Added Reboot
-Added Recovery
-Added Hot Reboot
-Added logcat
-Added Fix Permissions
-Added Reset Password
-Added an ugly easter egg
Version 2
18 April 2013
- Changed it from a script to multi tool
- Added folders for convenience
- Made eye candy
- Made it noob proof
- It's like changing Baichung Bhutiya to Lionel Messi
Version 1
- Just one smali.bat file and one baksmali.bat file with one one line each of commands to Baksmaling and Smaling (duh!)
PHP:
I am not responsible for your device being dead,
you flashing stock ROM,
you using your device as a brick,
or the decrease in love of your Girlfriend because you use your mobile so much
What does it do?
As you are aware, there are smali files in jar files and apks you need to edit for adding 4-way boot into power menu, extending Power options, changing clock colour, adding CRT effect, changing the pop up that comes up when you touch the easter egg image, adding brightness slidebar, adding lidroid toggles, etc and so manyyyy things
In order to edit them, you need to decompile apk and classes.dex
It is not a problem in editing smali files of apk as they are decompiled itself by APK-Multitool(I use it)
But, it does not work for jar files
I know that there is smali.jar and baksmali.jar for it but I don't like repeatedly commading same operations when I can do it with one click
This program decompiles and recompiles classes.dex from any jar or apk in one click(very useful when you only need to decompile dex file only)
Pre-Requisites:-
*PC
*My Tool
*Java JDK(or JRE) (If you are running Windows 7 64 bit, you may need to add Java in environment variable)
*7-Zip (For in zip operations[pull out classes.dex])
*classes.dex file(on which you will operate)
*Android Phone to be connected to PC with USB Debugging on to use features other than decompiling and recompiling
Guide:-
1. Download my Tool.
2. Extract it in any folder.
3. Place classes.dex in the input folder. DO NOT RENAME IT.
4. Run script.bat. Choose Option 1, Decompile classes.dex . In a few seconds, there will be a prompt that it is "Done. Press anykey to continue" (Note:- If you have UAC [User Account Control] on, you may run it as administrator or it might not be able to create folder if you have extracted it in System Drive)
5. Go to decompiled folder. There will BE classout folder. Make any changes in smali in classout folder(ALWAYS USE NOTEPAD++). DO NOT RENAME CLASSOUT FOLDER.
6. Again open script.bat if you had closed it or if not, then return to the window.
7. Choose 2 option "Compile classes.dex" . A new classes.dex will be formed in output folder.
8. Enjoy
Note:- Once you change things in classout folder, and you decompile another classes.dex, previous version in decompiled folder will be deleted. So if you want backup of it, move it somewhere else
Same thing will happen to classes.dex on output folder when you compile another one.
Other options
1. Connect you phone to PC with USB Debugging on and not on USB Tethering. Make sure you aren't using adb before using the tool. If so, Go to Alt+Ctrl+Del and to Task Manager and close adb.exe process
2. Choose the option what you want.
a) Logcat, either view or save it
If you view it, a window will appear with logcat in it. If you are done, just close that window
If you save it, it will be saved in the same folder where Script.bat is present. To stop saving it, Press Ctrl+C and type Y and press Enter
b) Reboot, may take some time in rebboting and rebooting in recovery.
c) Fix permissions and Reset password
3. Try to find Easter Egg
Download:-
ROMToolsPCv3.zip
Reserved
Definitely easier than the "java -jar smali.jar..." command.
Thank you.
Trying it out...
Thank You all
If you have suggestions, please post them here.
Great tool .Try to make one for resources also :thumbup:
Sent from my GT-I9082 using Tapatalk 2
balliboxer said:
Great tool .Try to make one for resources.dex also :thumbup:
Sent from my GT-I9082 using Tapatalk 2
Click to expand...
Click to collapse
Sure
Didn't knew there were such files too
balliboxer said:
Great tool .Try to make one for resources.dex also :thumbup:
Sent from my GT-I9082 using Tapatalk 2
Click to expand...
Click to collapse
Can you tell me which file contain these?
I searched it but did not find much
Are you talking about resources.arsc?
iamareebjamal said:
Can you tell me which file contain these?
I searched it but did not find much
Are you talking about resources.arsc?
Click to expand...
Click to collapse
Yea resources.arsc mistakenly written.dex
Sent from my GT-I9082 using Tapatalk 2
balliboxer said:
Yea resources.arsc mistakenly written.dex
Sent from my GT-I9082 using Tapatalk 2
Click to expand...
Click to collapse
Umm. That is automatically done by apktool
I did not find any way to do it separately
iamareebjamal said:
Umm. That is automatically done by apktool
I did not find any way to do it separately
Click to expand...
Click to collapse
But in apktool we have to manually put commands and sometimes it give error.
Sent from my GT-I9082 using Tapatalk 2
balliboxer said:
But in apktool we have to manually put commands and sometimes it give error.
Sent from my GT-I9082 using Tapatalk 2
Click to expand...
Click to collapse
Use apk multitool or vts instead
Linux Multitool
iamareebjamal said:
Thank You all
If you have suggestions, please post them here.
Click to expand...
Click to collapse
Here is something equal written for Linux.
http://d-h.st/UEh
Hope you like it.
Greetings.
Version 3 Released and OP Updated *Major Release*
iits cool dude thanks it helps a lot
badagila said:
iits cool dude thanks it helps a lot
Click to expand...
Click to collapse
Thanks. But don't quote the whole OP for saying something.
It takes some extra scrolls to move down o the point.
So, can you please remove the quote from you post?
----------------------------------------------------------------------------------------------------------------------------------------------------------
And guys, reset lock feature is now confirmed to be only working on rooted phones
Cheers
I can confirm "reset password" worked on sgs3 i727 on aokp rom, it still asking for a patron but any patron unlock it, for pass lock or pin it just reset it to default, big work thx
juancollado2003 said:
I can confirm "reset password" worked on sgs3 i727 on aokp rom, it still asking for a patron but any patron unlock it, for pass lock or pin it just reset it to default, big work thx
Click to expand...
Click to collapse
Yes, it works like that only
It will show the password screen but phone will get opened if you input any password
Funny though (Good for trolling people)
juancollado2003 said:
I can confirm "reset password" worked on sgs3 i727 on aokp rom, it still asking for a patron but any patron unlock it, for pass lock or pin it just reset it to default, big work thx
Click to expand...
Click to collapse
Yes, it works like that only
It will show the password screen but phone will get opened if you input any password
Funny though (Good for trolling people)
Does this work on linux?

EFS Backup from device (without PC) [Update 11Feb14]

EFS Backup from device (without PC)
Why we need EFS backup ?
EFS folder contains some important and some basic info related to our device identity like Wi-Fi address, Bluetooth MAC address and the very main IMEI address (nv_data.bin).
Now if this EFS partition accidently corrupted then your phone’s IMEI number will get erased and you can not make voice call further. This kind of damage is often not accepted by the service center of your respected handset’s company.
Here your backup can only be savior for you
You needs device rooted, Here is guide how to root N7100.
NEW METHOD (Updated 11Feb14)
Install this app and select backup/Restore that's it. (keep USB debugging ON). Also read play store description.
Dr.Ketan EFS Tool N7100
Video guide
OLD METHOD
Backup EFS
1.Install Terminal emulator
2.Open it, you will get ***@android:/$
{
"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"
}
3.Now typebelow said command and enter
Code:
su
it will ask superSU permission, grant it (it will ask only if your superSU setting - default permission is set to 'prompt', if you have set to 'grant' it will not ask)
4.you will have now this
[email protected]:/ # (this # symbol suggest it got root access)
5.Now type below mentioned command (case sensitive) and enter (to make this step easy from device, i have attached 5.txt (5i for backup to Int sd card) file at end, just open and select text. later you can paste to emulator to avoid spell mistake)
Code:
dd if=/dev/block/mmcblk0p3 of=/storage/extSdCard/efs.img bs=4096
In case you don't have ExtSdCard and want to make backup to Int Sdcard then command should be like this
Code:
dd if=/dev/block/mmcblk0p3 of=/storage/sdcard/efs.img bs=4096
6.After successfull backup you will find msg as seen below in image, as well you can see 20MB file efs.img on Ext SD card
Now copy efs.img from Ext Sd card to safer place on pC/Laptop/media/online so you can find whenever you need it.
Restore
Make sure you have efs.img which you have got with backup, placed on Ext Sd card
Repeat step 1-4 as said above, and in step 5 you have to give below said command to restore it.(you can copy below command by opening R.txt file (Ri.txt for restoring from int SD )attached at end to avoid spell mistake)
Code:
dd if=/storage/extSdCard/efs.img of=/dev/block/mmcblk0p3 bs=4096
In case you restoring from IntSd card then command should be like this
Code:
dd if=/storage/sdcard/efs.img of=/dev/block/mmcblk0p3 bs=4096
- Reboot device
FOR SOME ROMs like AOSP mounting point is different, so in case above command doesn't work then you need to know mount point. for this do following
Follow first 4 step said above to make backup (upto grant SU permission)
then Type
Code:
ls /storage
This will show mounting point of storage on your device like below shown image.
Here storage mounting point is
extSdCard for Ext SD card
sdcard0 for Int Sd card
So make changes in command accroeding your storage mount point.
Edit 28June13 : Just to report, today i have lost IMEI and got chance to restore with above said method and it work like charm.
Click to expand...
Click to collapse
With all respect for ur great work and effort, but I learned from u last time u helped me...I found the easiest way for the efs story...every phone I use, directly after rooting I install root explorer copy the efs folder to my pc and ext-sdcard...no matter what happened to the phone I just paste the folder back to its place and restart the phonw...and thats it, or u have objection about it? Please let me know
Sent from my GT-N7100 using XDA Premium HD app
That's not good idea, when you copy folder with explorer it will messup permission.
Sent from my GT-N7100 using xda premium
dr.ketan said:
That's not good idea, when you copy folder with explorer it will messup permission.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
agree
via《t4p4t41k》
in trouble !
dr.ketan said:
That's not good idea, when you copy folder with explorer it will messup permission.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Hi there
I am in New Zealand, recently rooted with your help and installed PhilzCWM. Also on your advice, I backed up my EFS.
My problem: just today I realised I cannot send text, or make phone call. I am on X-Note ROM from 3-4 days ago. I am very sure that after installation, I had normal Mobile connectivity and was surprised to I didn't. Not sure if my EFS became corrupted, or other ROM setting is wrong.
My SERVICE STATE says Out of Service
My Mobile NETWORK STATE says disconnected.
My phone number says UNKNOWN
What's weird is
My IMEI lists a long number, assumed correct
So if my EFS partition is corrupted I assume I wouldn't see any IMEI at all.
Far as I know my SIM is activated (I am on a company plan & coworker's phones are normal)
Just now I restored my stock nandroid and .... same thing! No service. So I doubt it's even a modem problem.
Guys I'm screwed, any tips what settings to check etc??
OK update:
I sucked it up and decided to try restoring the EFS image I had earlier created. Mate, it worked! I have network service now.
Thanks to DrKetan. It was only because I read his advice to backup my EFS...and his advice how to restore. Very helpful bloke.
Thanks.
I flashed a ROM yesterday and my imei changed luckily I'd copied the full efs folder to my ext_SD so I just copy and pasted it back and that worked for me once I restarted.
Sent from my GT-N7100 using xda premium
Dr.Ketan thank you for the lovely Guide . I did a backup as per your instructions. I would like to know about the aroma installer which offers a backup option when installing a Rom.I have a backup of the Same . I note that there are two files which is only 268 kb & 40 kb respectively.My question- Does this backup help & if it helps how do we restore it (backup done during aroma installer)
Sent from my GT-N7100 using xda app-developers app
Here said method backup complete partition that's why size is big.
There may be option available in aroma, i have never tried aroma.
Sent from my GT-N7100 using xda premium
I too had the same problem, I then remembered that I had backed up my efs using this method. Thank You Dr.Ketan
Sent from my GT-N7100 using xda premium
I lost a lovely Galaxy Note 2 to a corrupt EFS before I even knew that such a thing could happen to a flasher of roms.
I probably have the most backed up EFS of all time, since that horrific incident.I never knew about this way , I was just using EFS proffesional, but you best be sure so I have used this method too, and uploaded the backup to Dropbox.
Many thanks dr.ketan, so many peoples saviour.
And any one who is thinking, EFS thing won't happen to me....BEWARE!!!
AND JUST DO IT!!!
You guys put back life to this thread, probably I forget even about this thread.
Sent from my GT-N7100 using xda premium
dr.ketan said:
You guys put back life to this thread, probably I forget even about this thread.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
I came from a Nexus S phone, and flashed a lot of stuff over the years. But never once did the topic of EFS/IMEI come up. It was simply not an issue discussed in that device's XDA forums. So when I upgraded to the Note and joined these forums, I assumed I knew most of the important stuff.
I read your EFS thread and thought....hmm imagine if I ended up with a bricked phone or unusable in some way....I would be mad at myself and out of $$...so I did the backup. Far out, I am fortunate to have done so. People like you do exist in other forums - very helpful and unselfish with their time and expertise; XDA is based on the spirit of such people. Major props to you!
cannot open for read: No such file or directory
dr.ketan said:
EFS Backup from device (without PC)
Why we need EFS backup ?
EFS folder contains some important and some basic info related to our device identity like Wi-Fi address, Bluetooth MAC address and the very main IMEI address (nv_data.bin).
Now if this EFS partition accidently corrupted then your phone’s IMEI number will get erased and you can not make voice call further. This kind of damage is often not accepted by the service center of your respected handset’s company.
Here your backup can only be savior for you
You needs device rooted, Here is guide how to root N7100.
Backup EFS
1.Install Terminal emulator
2.Open it, you will get ***@android:/$
3.Now typebelow said command and enter
Code:
su
it will ask superSU permission, grant it (it will ask only if your superSU setting - default permission is set to 'prompt', if you have set to 'grant' it will not ask)
4.you will have now this
[email protected]:/ # (this # symbol suggest it got root access)
5.Now type below mentioned command (case sensitive) and enter
Code:
dd if=/dev/block/mmcblk0p3 of=/storage/extSdCard/efs.img bs=4096
6.After successfull backup you will find msg as seen below in image, as well you can see 20MB file efs.img on Ext SD card
Now copy efs.img from Ext Sd card to safer place on pC/Laptop/media/online so you can find whenever you need it.
Restore
Make sure you have efs.img which you have got with backup, placed on Ext Sd card
Repeat step 1-4 as said above, and in step 5 you have to give below said command to restore it.
Code:
dd if=/storage/extSdCard/efs.img of=/dev/block/mmcblk0p3 bs=4096
- Reboot device
Click to expand...
Click to collapse
Hi @dr.ketan!
i cant remember if i had backed up my efs.
but just in case, i tried this steps.
i got this message after following the backing up procedure in terminal emulator:
cannot open for read: No such file or directory
what should i do?
im using note 2 n7100.
thank you.
tongueinamow said:
Hi @dr.ketan!
i cant remember if i had backed up my efs.
but just in case, i tried this steps.
i got this message after following the backing up procedure in terminal emulator:
cannot open for read: No such file or directory
what should i do?
im using note 2 n7100.
thank you.
Click to expand...
Click to collapse
Got the same message.. im presuming you must have wrote it wrong. make sure its exactly the way dr ketan has posted. after 2 tries i was succesfull.
Is this method better than doing a nandrod back up using the recovery? Thanks!
tongueinamow said:
Hi @dr.ketan!
i cant remember if i had backed up my efs.
but just in case, i tried this steps.
i got this message after following the backing up procedure in terminal emulator:
cannot open for read: No such file or directory
what should i do?
im using note 2 n7100.
thank you.
Click to expand...
Click to collapse
gnikolakis said:
Got the same message.. im presuming you must have wrote it wrong. make sure its exactly the way dr ketan has posted. after 2 tries i was succesfull.
Click to expand...
Click to collapse
Correct there should be something wrong
rq005 said:
Is this method better than doing a nandrod back up using the recovery? Thanks!
Click to expand...
Click to collapse
Both are different things
Sent from my GT-N7100 using xda premium
gnikolakis said:
Got the same message.. im presuming you must have wrote it wrong. make sure its exactly the way dr ketan has posted. after 2 tries i was succesfull.
Click to expand...
Click to collapse
What you are most likely getting wrong, when no file found or whatever, is,
dd if=/dev/block/mmcblk0p3 of=/storage/extSdCard/efs.img bs=4096
THE BIT AFTER mmcb is NOT a ONE its an L ...so l:cyclops:
dr.ketan said:
Correct there should be something wrong
Both are different things
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Can you be more specific? I recovered once my EFS using TWRP and worked fine... Maybe you can explain what's so different about. Thanks!
gnikolakis said:
make sure its exactly the way dr ketan has posted.
Click to expand...
Click to collapse
I was putting the S and C from sdcard in small letters and i was getting the same message,now i'm set.

Categories

Resources