Like many people I had issues disabling voodoo lagfix, in spite of the well intended advice from others here. After trying all the possible methods (creating both disable-lagfix folder and files) I decided to review the voodoo logs and saw that it stated an error regarding a file called "fat.format". To put it plainly, seems in the process of disabling the lagfix, the file was missing, which in turn aborted the process.
I managed to remedy this by locating the aforementioned file and placing it in the appropriate folder. Afterwards, I rebooted and from recovery disabled lagfix, which finally went smoothly and enabled me to flash another rom. The file is supposed to reside in the system/bin/ folder and is titled "fat.format", no other prefixes or suffixes. I don't know what this file does except that it allowed me disable lagfix.
With a proper file explorer you can navigate to the folder and enable r/w permissions so that you can paste the file there (only if it's missing though). I can't guarantee this will work for you or if it will have an adverse effect on your phone's functionality. The only claim I make is that it worked for me. Making any changes to this folder is a risk so proceed with caution and consider yourself warned.
I'll try to upload the file when I can but I do believe the file can be located in one of these captivate forums with a simple search. Good luck.
Sent from my SGH-I897 using XDA App
Related
Hi there,
Is there a way to temporary root my Nexus S [I9020XXKD1] or alternatively a non-root way to access /data so that I can copy a file in and out? Essentially I want to be able to backup and restore some game saves
Most posts I've read basically have folks saying "Just root it", which is good advice to most but isn't right for me - I really don't want to have to wipe my phone and I'd also like to be able to dip my toe into rooting before taking a full leap. That, and aside from needing this one file in /data my phone works exactly as I'd like it to
I only need "su" access for a brief moment to copy off a file to and from /data. I set up the android sdk but ADB didn't work because of the protection of "production builds".
VISIONary seemed like the right kind of thing, but I don't believe it works for the Nexus S or recent firmware, so while temp rooting would be nice so would any solution that allows me to backup and restore some files in /data.
At the moment I am wondering if writing an apk of my own that copies/replaces this one file is the way to go - but that seems perversely long way around!
So any help/suggestions most appreciated
There is no temporary root for the Nexus S. You're either rooted, or you're not. However, if, perchance, you are on Android 2.3.2 or earlier, you might be able to root without wiping.
Without root, you cannot see the files in /data, but you can read/write the files directly if they have the proper permissions and you know the exact path/filenames. After poking around a bit, it seems that read & write permissions vary among apps. Most apps have full permissions reserved for the parent app. Some allow other apps/user to read some files, and read+write others. (The permissions being app-specific, if it can't be done by command line, I doubt it could be done by creating an app, either.)
So, what is the game? Perhaps I can do some exploring.
If you have the old bootloader (2.3.2 i think) you can boot a recovery without flashing. From you computer use "adb boot recovery.img" and boot clockwork recovery. From there you can mount and access the filysystems.
Sent from my Nexus S using XDA App
Maximilian Mary said:
There is no temporary root for the Nexus S. You're either rooted, or you're not. However, if, perchance, you are on Android 2.3.2 or earlier, you might be able to root without wiping.
Without root, you cannot see the files in /data, but you can read/write the files directly if they have the proper permissions and you know the exact path/filenames. After poking around a bit, it seems that read & write permissions vary among apps. Most apps have full permissions reserved for the parent app. Some allow other apps/user to read some files, and read+write others. (The permissions being app-specific, if it can't be done by command line, I doubt it could be done by creating an app, either.)
So, what is the game? Perhaps I can do some exploring.
Click to expand...
Click to collapse
Thanks I figured as much. The game is Dungeon Hunter 2 and essentially I am trying to implement a simple fix to make my save game work again (the fix is here: http://forum.xda-developers.com/showthread.php?t=1042675 a few posts down) but it requires root. So I do know the exact paths and filename.
Thank you for your helpful answer
Ok, I'm not having any luck here, and it's pissing me off. FYI, I don't have that game, so I'm testing it with Angry Birds. I can read and copy the file just fine, but I can't modify it without using root. The data file itself has read/write access, but the containing folder (files/) is read-only, so I can't overwrite the file after I've modified it. Since the file itself has r/w access, I wonder if it would work to modify the file directly, instead of using an outside program to modify it then overwriting it. (I'm a bit ignorant of the finer points of linux permissions.) This would require an app that would allow you to open and modify a file by typing the full path & filename, instead of just browsing the directory tree. You could also try < adb pull /data/data/com.gameloft.android.TBFV.GloftD2HP.ML/files/dh2_000.savegame dh2_000.savegame > (using the correct path, if that's not it). Then see if < adb push dh2_000.savegame /data/data/com.gameloft.android.TBFV.GloftD2HP.ML/files/dh2_000.savegame > works. The fact that you can copy the file out is promising, anyway. So even if you had to root, you could backup the file before rooting wipes everything, then fix it & back it up after you had root.
Btw, what version of Android are you on?
Edit: I think I'm getting somewhere. While you can't modify the file itself, you can modify the file contents. So something like this might work: < adb shell >
< more /sdcard/dh2_000.savegame > /data/data/com.gameloft.android.TBFV.GloftD2HP.ML/files/dh2_000.savegame >
So the next step is to get some help from someone who has the game and is rooted as to the exact path to the savegame file. Once we have that, I think we're golden. (Or, let me know if adb pull works with the path I guessed at.)
wow! Thank you for your help
In answer to your questions: my Nexus s is running 2.3.4 and you are correct about the file path (many other kind xda users died to bring us those paths ) is /data/data/com.gameloft.android.TB with the filename being dh2_000.savegame
I don't want to drive you to distraction! If I could back it up I probably would go ahead then and root the phone given how complexplaying with a non-rooted phone is!
I will try the adb pull method and let you know how I get on.
Thank you again for your help and for showing me why I probably do want to root!
I just applied Daoist's CWM stock ROM update (should still be rooted, right?). It came up first time.
Then, I modded my build prop (set dpi to 120 because I like it that way). But maybe I screwed up the file name in Root explorer, because now I'm in a boot loop and if I try ADB PULL /system/build.prop it says "file not found."
I can't get SU through adb, so can't push build.prop to /system. ADB remount returns an error. permission denied. Transformer won't boot, so I can't do anything from it.
I CAN get to cwm, and have been trying to create an update.zip that will just copy build.prop to /system, but everything I have tried quits with "install aborted" message.
What can I do?
restore a nand and dont try and **** with it again, lol. no but really, restore a nand and then copy your build. prop and make a flashable zip and place on your sd card in case it happens again, so you can just flash it in cwm.
Resolved..
Well, why go back when you can go forward?
I went ahead and installed the Prime ROM. Looks like it is eating all my currently installed apps.
Y'all should know, though, that if your system can't find a build.prop it won't start. You can ADB to it and have a rudimentary set of commands, but your ability to significantly alter anything in your file system will be prohibited.
Lesson learned.
glg
as a side note most editors in android rename system files when you change them to "nameoffileyouedited".bak so if you pull and rename that file that might have fixed your problem. also try lcd dencity changer from the market. its a little less hazordous
mrevankyle said:
as a side note most editors in android rename system files when you change them to "nameoffileyouedited".bak so if you pull and rename that file that might have fixed your problem. also try lcd dencity changer from the market. its a little less hazordous
Click to expand...
Click to collapse
That is true. I had backups. But without a build.prop, the virtual machine won't start. There is no way to do a file operation to replace the backup. At least none that I found. I had to flash the whole system.
glg
To the Admins, I'm not entirely sure where you guys would want this thread...troubleshooting seemed to be the most sensible.
all right everyone, I'll explain here how I fixed this, but keep in mind I have the ATT LG G2 running KitKat with TWRP 2.7.0.0 and I'm rooted. I only recommend this for advanced users. If you aren't an advanced user, well, make sure you have a backup. I'm sure there was a faster way to fix this, but my goal wasn't to find the fastest way initially, it was to find a working way. For example, you could just ADB everything. You could also, assuming you know how to use your OS to search that deep into the device files, done a rename, copy/paste etc. etc. Not all devices are made equal, so be CAREFUL! BTW, I was in debugging mode + charge only.
WARNING: I AM ONLY OFFERING THIS FOR INSIGHT TO ADVANCED USERS THAT KNOW WHAT THEY ARE DOING - I DON'T OFFICIALLY RECOMMEND THAT ANYONE DO THIS. I AM NOT RESPONSIBLE FOR ANY TRANSMUTATION FROM LG G2 TO BRICK.
Here's what I did:
1) I opened accessibility while hooked up to the debugger in Android Studio to see that it was producing a Null Pointer Exception.
2) I have a slightly modified version of the TOT file so that I can run TWRP and still be rooted in KitKat.
3) I am rooted, so I used Root Explorer to search for accessibility and found that the file is called "LGSettingsAccessibility.apk" and .odex - it's under (WITH ROOT ONLY) /system/priv-app/
4) I searched for a system dump copy online...I found this site: http://hunterspad.com/Domains/StorageCow/Xda/Users/garyd9/Extracted System/priv-app/
I found that by typing "LGSettingsAccessibility.apk" and initially found a Google Drive version but it was posted in September of 2013 - unlikely to be the odex and apk from KitKat hahaha. I used a Google Search that searched custom range between Feb 1st and today. I found 2 links, one of which is the above.
NOTE: I don't recommend anyone do the following unless you KNOW what you are doing and definitely have a backup to restore to if things go wrong
5) I sent the link for each file to myself on Google Hangouts. I used Hangouts to download the March 14th upload of the LGAccessibilitySettings.apk and LGAcessibility.odex
5.5) I copied each of the original files (.apk and .odex) from /system/priv-app/ to my /sdcard/LGBackup folder I created using the Root Explorer app.
6) I went into the app "Root Explorer" again after downloading both files (DID NOT INSTALL IT, though it probably won't let you anyway). I checked both files and copied them.
7) I went back to /system/priv-app/ and renamed the existing files to be replaced with the extension ".bak" so that the system no longer points to those files (NOTE: Root Explorer asked me to remount as R/W (read and write vs. read-only) a good feature of root explorer to be in read-only by default; dangerous territory.
8) Bottom right corner of Root Explorer it was waiting for me to "Copy Here" when arriving at the location where I wanted to copy the files: /system/priv-app/ and after copying them I decided to be a fool and install the apk and it told me something like "app not found" or something.
9) FINALLY went into Settings and touched Accessibility and VOILA! It worked! A lot of luck involved - the odexed and apk files may not have been the proper version. I could have checked with relative ease (though likely time-consuming) by using some of my android dev skills/utilities.
WARNING: I AM ONLY RECOMMENDING THIS FOR ADVANCED USERS THAT KNOW WHAT THEY ARE DOING.
Thanks to garyd9 on XDA - without your uploaded files on storage cow, I couldn't have fixed this problem!
After trying and trying and failing, I have finally figured out a way to port a rom to the Cube T7.
This has proven the only method (in my experience) to work. All the standard methods have failed
each time.
WARNING!!!!! THIS COULD BRICK OR DAMAGE YOUR PHONE
YOU ARE TRYING THIS AT YOUR OWN RISK. I WILL NOT BE HELD RESPONSIBLE
FOR WHAT HAPPENS TO YOUR DEVICE!!!!
Things you need.
latest Spftool
and the Rom package
NOTE:You need to know that you can't just flash the package I put together. You will
need to use the TWRP recovery that comes in the package to transfer file from your external sd to
the system folder and so forth. Also the proper permission to set.
Step 1: Flashing the images.
I've already pulled the correct img from each folder and put it together for you.
The only thing that you will need to do is extract the folder and use the spf tool to
install the firmware.
Note** In order to keep the 3.97 app storage, I've had to make sure to use the
Spf tool to do a full format except for the bootloader.
Step 2: Repairing the Rom
In the rar package, I included all the files need to fix the rom so
it will work smoothly on your phone. The files can be located in
the "system" folder which will need to be copied to your external sdcard
At this point you will already have flash the images and turn on the phone.
You will notice that the after you turn it on, you will get a warning that says "Cpu overheating"
or at least to that affect. This is not true by the way, this is from the fact the tp settings are off
from the original rom. Either way the warning will force boot your phone which again is fine.
Once this happens you will need to go to recovery.
Once in recovery make sure that you go ahead and mount your
system partition.
With this done you will be able to go to /system/etc/.tp
This folder contains the files that control the thermal manager for
the rom. You want to delete this folder. YES DETELE IT!!!
Once deleted, go to the system folder that you should have copied to your
external Sdcard. You need to copy /system/etc/tp to the exact location that you
just deleted the original.
Once you've done this you will need to set the permissions for the folder and the
files contained. The folder needs to be set to 0755 and the files inside need to be set to 0644.
Once done its best to go ahead and use the recovery to flash UPDATE-SuperSU-v2.46.zip to root your device before
restarting. Once restarted you will need to use root explorer or es explorer root function to
copy all the files to there correct locations and set their permissions. Each file is in its corresponding
folder as it should be in the system partition. All you will need to do is copy and past from the folder on the external and
paste to the same folder in the system partition. For those that may not know, all files will be set to 0644/rw--r--r-- and folders that you copy over will be 0755/rwxr-xr-x (if your using root explorer, just un check the group and others on the "Write" permissions.
Whats not working?
I can't figure out how to get the camera to working.
I've used standard tuts to try and copy the right files or libs
but not luck as of yet. If anyone figures out a way please share!!!
Also, if you have the fold case, the screen does not come on when you
open the fold. Also when double tapping the screen, this does not take it out of sleep
mode. From what I've seen those are the only things that dont work. If you see something
else, please report it to this thread.
Also in the package you will find the Carliv 3.3 recovery version for our phone.
Thanks to kushyree from needrom.com for building it for us.
He also has been assisting me in trying to port other roms to our phone. We owe him a lot of thanks.
Let me know if you guys need any help with this. I will do the best I can to try and help out. Enjoy.
Using SuperSU, BusyBox, ES File Explorer, and can't seem to get this app to process the audio. It's installed and the Viper app opens, but doing the thing where it asks me to install drivers everytime. I've tried these threads to troubleshoot:
https://forum.xda-developers.com/t/how-to-viper4android-install-the-proper-way-root-required.3691597/
I'm getting stuck at finding the soundfx folder in /system/lib/soundfx/
For some reason in File Explorer (and I've tried Root Browser too) I can't see the soundfx folder but I think it's there because when I try to create one it says can't use this name because folder already exists.
Also on step 4: 4. This step is dependent on your setup. If you are using a permissive kernel this is not necessary. If you're using SuperSU with an enforcing kernel you'll need to flash the ViPER4Android-supolicy.zip that is included in the attached zip file.
I am using SuperSU, but I have no idea how to flash the zip file they are talking about, and I don't know how to open a .zip files on this operating system.
I think there might be other ways to troubleshoot this problem because I've also found this link as well offering a different approach:
https://forum.xda-developers.com/t/...w-features-7-0-support.2191223/#post-39156761
The thing with this link above is I don't know the difference between a system app and a user app. I've been working on this for a few days now, and am trying to find a way to bounce ideas off of someone who understands this better than I do. Any help is greatly appreciated! Thanks again guys!