Database Info

[Q] Writing a file back to a Marketplace apps Isolated Storage?

Hi All,
I've used Heathcliff's WP7RootTools 0.9 to extract a file from an installed apps IsolatedStorage. The app in question was installed from the Marketplace, but I want to modify some of the files it's saved to it's Isolated Storage.
I extracted the file I wanted to edit by using the Explorer utility in WP7RootTools to copy the file to the "My Documents" folder, and renamed the extension to docx. From there I could simply go into the Office Hub, where the file was now listed, and emailed the file to myself.
I have made the edits to the file, but now need to get the file back into the app's Isolated Storage. This is where I have now got a bit stuck
I've tried copying the file to SkyDrive, and using the Office Hub to download it from SkyDrive to my phone. The file downloaded and is cached on the phone somewhere, but the file location, according to Office is not "Phone". This is normal, as Skydrive downloaded documents are not saved to the "Phone" location until you open the document and do "Save as".
I cannot of course open the downloaded file, as it isn't really a .docx file. Files loacted in the "Phone" location show up in "My Documents" in the WP7RootTools explorer. SkyDrive downloaded documents I have no idea where they are located?
Can you guys help? Does anyone know the path to location of SkyDrive downloaded items on the phone. If so, then I can easily just use the WP7Roottools Explorer to copy the file back to the apps Isolated Storage.
Is there a better way to copy a non-Office file back onto the phone?
Regards,
Micro666

You could use one of these apps:
sh4d0w86 said:
i was going to suggest using WPV App Data Backup, but it seems i saved the Backups in the wrong location... (will fix in next release)
so,
you can use TouchXperience or WMDC Launcher.
Click to expand...
Click to collapse

I'm looking to do the exact same thing....

Options:
1. Do exactly what you've been doing, but save as .txt instead of .docx. The phone can still open this, even though its probably a binary file, and save it to the "Phone" location. Then you can copy it back and rename it.
2. Use an app that gives direct access to the phone's filesystem from the PC, like TouchXperience+WPDM, or Root Webserver (see my sig)+your favorite webbrowser.
3. Use any other way to get a file onto the phone, such as emailing it to yourself, using IsolatedStorageexplorer, or putting it in a XAP files and installing that file. Then move the file with WP7 Root Tools.
I recommend approach #2.

GoodDayToDie said:
Options:
1. Do exactly what you've been doing, but save as .txt instead of .docx. The phone can still open this, even though its probably a binary file, and save it to the "Phone" location. Then you can copy it back and rename it.
2. Use an app that gives direct access to the phone's filesystem from the PC, like TouchXperience+WPDM, or Root Webserver (see my sig)+your favorite webbrowser.
3. Use any other way to get a file onto the phone, such as emailing it to yourself, using IsolatedStorageexplorer, or putting it in a XAP files and installing that file. Then move the file with WP7 Root Tools.
I recommend approach #2.
Click to expand...
Click to collapse
I used TouchExperience.
1.On my Fully unlocked Device(I assume you can do this with root tools), I installed a file manager that gives full access to the device.
http://forum.xda-developers.com/showpost.php?p=24636416&postcount=23
2. I installed TouchEperience on my PC. After giving the WP7 app, Root tools rights, it should show most of the file system(on the PC) but, not all of it. So I created a new folder in \Windows (temp).
3. On the Phone, I hunted down the file I was looking for from Isolated Storage, I copied it to the \windows\temp folder.
4. Used the PC TouchExperience and browsed to \Windows\temp, there was my files, I copied them to my PC. USed the File Explorer to delete the files in my \temp folder(to make sure they were gone).
5. I edited the files, copied them back to \Windows\Temp on my device via TouchExperience on the PC. Then used the file explorer to copy them back to the Isolated Storage.
Note: The file explorer I posted a link to is GREAT, it can even edit files (basic text editor) in Isolated storage. I found a way to Cheat on a marketplace Xbox live game (didn't try others), right before the achivements, so they were really easy to get
I'm sure there is easier methods but, this worked for me...
Can I ask, what app did you try this on ?
Hope this helped...

FYI DavidinCT: Cheating XBL games is very risky. Microsoft often can detect it (for example, if you get one achievement that would have required getting another first) and they can and will permanently ban your Xbox Live account for doing so.
That all said... why didn't you just use WPDM (on the PC) to copy the file straight to the IsoStore of the app? So much easier...

GoodDayToDie said:
FYI DavidinCT: Cheating XBL games is very risky. Microsoft often can detect it (for example, if you get one achievement that would have required getting another first) and they can and will permanently ban your Xbox Live account for doing so.
That all said... why didn't you just use WPDM (on the PC) to copy the file straight to the IsoStore of the app? So much easier...
Click to expand...
Click to collapse
To be honest, I only did it with a game that had an error when I got so far, so the final achivements of the game. A Game with a Known issue but, no fix.
And I just really wanted to see if I COULD do it...
I used WPDM but, the PC version even with my phone fully unlocked (custom rom on my VZW HTC Trophy) and using Root tools 0.9 to give full to TouchExperince root, would not see all the folders and would not see the IsoStore. SO I had to copy the files to a folder that WMDM could see.
Personally, the new File Explorer above is awsome, it's even got a editor in it, I didn't even need to go through all that......

[Modify BOOT LOGO!] Samsung Galaxy S6

Welcome. Today I am going to teach you how to modify your android boot logo!
Modify at your own risk! I strongly recommend that you do not try this. But if your going to attempt this, make a BACKUP! I will explain the backup process down the page!
This method has been tested on the Galaxy S6. I RECOMMEND you do NOT attempt this method on any other smartphone other than the S6!
I own a Samsung Galaxy S6 [SDK21 ARM64] and my carrier is Straighttalk. This method might possibly work with the newer Android smartphones. In other words, attempting to do my method will probably not work with androids running 4.4.2 or lower. I will first explain why.
According to what I researched, there is a file in the root directory of the Android system that contains a file called "initlogo.rle". That is your boot logo. Older Android phones had this. The .rle is a bitmap extension and cannot be edited with Android. Actually, let me rephrase that, the .rle COULD MAYBE possibly be edited if you were to download the right tools off of the Play Store but computers can identify .rle as a bitmap very easily and can be opened. Windows computers can open .rle according to what I researched.
The initlogo.rle is also part of the boot.img. The boot.img contains the kernel and the boot files (like init.rc), that are necessary for the phone to boot up. Modifying your boot.img requires a computer. You can't just replace the initlogo.rle with another one. To make changes to a boot.img, you need to unpack the ramdisk, replace or modify the files, repack, and THEN flash the modified boot.img to make the changes.
Newer Android smartphones don't have initlogo.rle. Or at least MINE doesn't. Instead, I had to search for my boot logo which took my quite a while. After searching deep into the android system and messing around with the files, I came accross PARAM.
If you were to go in the /dev/block/platform directory, you would come accross a file called PARAM. Mine was in the directory /dev/block/platform/15577000.ufs/by-name. Inside that directory is basically the whole system. You will find files like BOOT, EFS, OTA and all that. You will also notice that all those files look empty. They all show 0.00B. I don't know exactly why that is, but they aren't really empty files.
My official boot logo was in the file "PARAM". What I did was copied it to my internal directory and attempted to extract it. After trying different extensions, I founded out that .tar is the correct extension. So to extract it, I renamed "PARAM", to "PARAM.tar". After doing that, you will be able to actually extracted it and be left with files with .jpg. Basically pictures inside it. I used root browser. :good:
Inside, you should find "logo.jpg". And whatta ya know! It's your boot logo!
I used PicArt to create a custom boot logo. It is a really great app! You can get it off the Play Store. Then I renamed it to logo.jpg and replaced the original logo.jpg with my newer one. Make sure it is named "logo.jpg" or there will be errors!
Now the last step is to archive the files through .tar format. I used root browser to do that. To correctly archive the files, multi-select the .jpg files. In other words, DON'T SELECT THE "PARAM" FOLDER!!!
When archiving the files, use LZMA compression option along with tar.(Look for that with root browser). This will not compress the files as much which will reduce the risk of errors.
Once it's archived, rename the new archive file to just "PARAM".
LAST STEP! Before overwriting your PARAM, copy your modified PARAM into the /system folder and set the correct attributes (PERMISSIONS) to -rwxrwxrwx. Now you are ready. Copy "PARAM" to the same director where you originally got your unmodified PARAM file. It will ask you if you want to overwrite. Say yes.
I was now introduced with a different boot logo. My phone never got bricked during the process. However, with Android, ANYTHING can happen, so I will give you some advice. If you have a custom recovery, you can easily restore PARAM. Make a copy of your original PARAM and put it in your internal directory. If something ever goes wrong, you can use the file manager (like with TeamWin) and replace the currupt PARAM with your backup PARAM. Then set the permissions to -rwxrwxrwx or 0777
I strongly recommend that you do not try this. Yes, I took the risk and was able to safely change my boot logo. However, not all Android devices are the same so be very careful if you are attempting to do this one an Android device OTHER than the Galaxy S6.
Leave comments if you have any questions!

Saved File using Hancom HWord (Factory) and Now Can't View/Access File

So, I edited a word doc from an email, using the built-in Hancom HWord viewer/editor. I used Save As from the menu. I wasn't paying attention to the file path and just added a suffix to the file name. Turns out I was saving in a protected folder. HWord cannot be opened directly from the Applications on the phone, but only by opening a Word doc from email, etc., but that doesn't present an Open option.
So, since I can't open the app and get an Open option, and because the file is in a protected folder, I can't get to this file.
The only method I've found out there for rooting my phone involves deleting the phone. Not an option when all I need to do is get to the file and copy it somewhere else.
I tried installing the latest HWord, and of course it does not have access to the original HWord's folder.
Do any of you know a method I can get to the file? Again, just need to copy it to a readily accessible folder.
Thanks in advance for any help you can offer.

Add APK - repack system.img

I was looking for a similar topic but I did not find one. Refers to problems with running applications added to "system.img".
I bought UMIDIG S for my father-in-law. It is based on a mediatec chipset. Unfortunately, soft is tragic, and there is no full translation, so I decided to bury it a bit in "system.img".
I can easily install the file in Linux and make changes in it. I can delete applications, I can make changes in configuration files and "buikd.prop".
Unfortunately, all APK files were uploaded to "system.img" even though I set permissions 755 for directories, and 644 for directories. Although the files are root: root, after uploading such "system.img" none of these applications works for the phone. The system sees them and tries to load. Unfortunately, applications hang because of errors. The system informs that the application hangs, and does not load its window. The icons of these applications and the names do not appear either (applications have green robocik as icon, and domain name, e.g. com.android.clock ....)
I am asking for advice. How to add APK files to the unzipped "system.img" so that after packing and uploading to the phone there were no errors ???

Do you have found how add app in system.img?

It's all around, but you can replace apps with others. In the linux system, unpack the img, and mount them. Then you can freely rename files as well as move files within the .img mount point
I chose the applications or other files I did not need, and moved them to the directories (which I named my applications). If the application needed libraries, you also had to get files in a similar way, and place them in arm or arm64 directories.
Then prepared files "stuffed" with data, using the command DD. That is, dd if = (source file) of = (the recipient file at the system.img mount point).

Thanks for reply, so this only on Linux? For Windows there is something?

Markosv76 said:
Thanks for reply, so this only on Linux? For Windows there is something?
Click to expand...
Click to collapse
I do not know, I do not use Windows. Certainly you can in a similar way from BSD systems, probably from Android and MacOS. I read something that Microsoft can somehow support linux shell, but I do not know the details. You can always use some distribution that works with a pendrive.

Thanks, I will try again

Markosv76 said:
Thanks, I will try again
Click to expand...
Click to collapse
You can use Virtual Box to run a Linux distro inside Windows or you can try using Cygwin.
Sent from my LGL84VL using Tapatalk

jaroslawstrauchmann said:
I was looking for a similar topic but I did not find one. Refers to problems with running applications added to "system.img".
I bought UMIDIG S for my father-in-law. It is based on a mediatec chipset. Unfortunately, soft is tragic, and there is no full translation, so I decided to bury it a bit in "system.img".
I can easily install the file in Linux and make changes in it. I can delete applications, I can make changes in configuration files and "buikd.prop".
Unfortunately, all APK files were uploaded to "system.img" even though I set permissions 755 for directories, and 644 for directories. Although the files are root: root, after uploading such "system.img" none of these applications works for the phone. The system sees them and tries to load. Unfortunately, applications hang because of errors. The system informs that the application hangs, and does not load its window. The icons of these applications and the names do not appear either (applications have green robocik as icon, and domain name, e.g. com.android.clock ....)
I am asking for advice. How to add APK files to the unzipped "system.img" so that after packing and uploading to the phone there were no errors ???
Click to expand...
Click to collapse
did you find a solution to this? please reply if yes, I am having the same problem

It is possible to avoid folders (and files) auto creation? Unexpectedly, YES.

Dear friends,
for months I was struggling with the auto-created folders named LazyList and LOST.DIR
These are folders that are created automatically by the file system, but sometimes I have found, especially in the LOST.DIR folder, duplicated and previously deleted files, also big, very big ones.
Why a so great waste of storage?
So I wanted to get rid of that!
And after some "Guru meditations" I have found the trick to achieve it.
It is a very simple trick, that's related to the file system itself.
Since it is a rule that where there is a folder there cannot be a file with the same name, simply creating a file with a specified name will make it impossible, even to the system, to create a folder with the same name, and vice-versa.
So, if we want to get rid of the infamous folder LOST.DIR, simply delete it and create, a, even empty, file with the same name!
The file system will be forced to not create that folder, anymore!
Freedom to manage storage.
Man vs Filesystem: 1-0
Hope this will be useful to everyone that takes care of their storage

Uranya said:
Since it is a rule that where there is a folder there cannot be a file with the same name, simply creating a file with a specified name will make it impossible, even to the system, to create a folder with the same name, and vice-versa.
So, if we want to get rid of the infamous folder LOST.DIR, simply delete it and create, a, even empty, file with the same name!
The file system will be forced to not create that folder, anymore!
Click to expand...
Click to collapse
I must say I didn't believe it, so I tried to create a lost.dir folder and lost.dir file in the same directory on my computer.
And you were right!
Thanks for sharing!