I'm getting some Windows Update errors (0x80244019 and 0x8007139f) which I'm 99% certain are caused by an incomplete download of the update.
Updating from Creators Update (RS2) to Fall Creators Update (RS3). I need it for some UWP API features. Prefer not to reset the device if I don't have to.
I just need to be able to clear the C:\Windows\SoftwareDistribution folder where the new build is downloaded to (unless it's different on mobile?). Is there any way to get access to this folder and delete/rename it? As far as I can tell, this would allow the update to download for real and install.
IIRC there used to be a way to browse system files in the built-in file explorer, using a shortcut, but that doesn't seem to work.
Interop Tools from the store lets me browse system files on PC and Xbox, but not on the x3. I can only access registry.
I couldn't find any guide that both applied to the x3 (all seem to be for Lumia and sometimes Samsung), and that I understood to follow. I think I need to enable mass storage mode, or get a different file manager installed?
@Kyle_N
Try his guide for accessing the files/file system in question on the X3. Should still work fine.
You need to focus on the section labeled ENABLE SYSTEM REGISTRY ACCESS INSTRUCTIONS-->For all other OEM devices.
This gives you the ability to unlock capabilities and full file system access.
Related
Hi.
I am new to Android and need your help.
I can not find files or file manager in the apps confused.
do I need to download anything to be able to do this?
And I do not know how to install apps if I copy one from my mac to the phone.
Lastly, I also do not understand why my mac can not see the folders of the phone even though it is connected via usb.
Finally, I tried to transfer data via bluetooth, but again I did not manage.
It says time over or something I do not know.
It looks very basic, but I need your help.
Please , help.
There is no default file manager. Most people will never need one.
If you want one, search the market for one, there are dozens. Astro is very popular.
to install ones you copy over, you need to go to home>menu>settings>applications
tick the box to 'allow unknown sources'
then, in whichever file manager you download, open the APK file on the card and it should install.
You can only browse the files of the SD card. the phone memory is system memory and protected. you do not eed to access it. All storage is done by the memory card, not the phone memory.
Bluetooth functions are limited on android. you can send files (as long as they are files the phone supports i believe) but you cannot use isync or anything like that.
If you want more sophisticated sync options for android, have a look at the missing sync for android at www.markspace.com
simples.
Thanks.
I downloaded Astro and it seems nice.
Now I can see how it works little bit.
Thanks for your help.
I haven't found anything on the forums about this (I have searched) so forgive me if it's a basic question. Is it possible to either:
1) Dump all data on a mango phone (in my case, a Samsung Focus, no interop-unlock) to a file on my computer, or alternatively
2) Access the data stored in the umpteen files created during a WP7 backup.
If anyone knows how to do either of these things (without interop unlocking -- I have data I need to pull off, but my firmware is too old to get interop unlocked, and I get error messages when I try to manually update the firmware), it would be greatly appreciated.
Thanks,
Beakin
Note: edited to clarify
I doubt it's even possible *with* interop-unlock.
1) A native app could map a large region of memory, but the WinCE kernel uses process isolation (same as every other modern OS) so there's no way for one app to access the full physical memory.
2) They're encrypted with a key that appears to be stored in the device itself. Nobody has yet figured out how to reverse this encryption.
GoodDayToDie said:
I doubt it's even possible *with* interop-unlock.
1) A native app could map a large region of memory, but the WinCE kernel uses process isolation (same as every other modern OS) so there's no way for one app to access the full physical memory.
2) They're encrypted with a key that appears to be stored in the device itself. Nobody has yet figured out how to reverse this encryption.
Click to expand...
Click to collapse
On #1, I should have been more specific -- I meant dump the phone's storage; what's in non-volatile memory, not RAM.
Still no without interop-unlock, then - standard apps don't have the privileges to access the filesystem (aside from a few very specific locations, like their isolated storage folder). That probalby means no access to the storage device itself either, although I admit to not knowing how that works on CE (NT or Linux, but that's it). If the app was initially sideloaded you can use the Isolated Storage Explorer to pull files from that app specifically, but if it's a marketplace app or something built-in like the SMS store, no such luck.
Of course, you can get more permissions if you can call into a driver - which is what ID_CAP_INTEROPSERVICES allows you to do, and ID_CAP_INTEROPSERVICES is why you need interop-unlock. I'd suggest you focus on figuring out why you can't interop-unlock and fixing that. Unfortunately I can't really help you there; I don't have a Samsung phone and the steps to IU an HTC phone are very different.
GoodDayToDie said:
Still no without interop-unlock, then - standard apps don't have the privileges to access the filesystem (aside from a few very specific locations, like their isolated storage folder). That probalby means no access to the storage device itself either, although I admit to not knowing how that works on CE (NT or Linux, but that's it). If the app was initially sideloaded you can use the Isolated Storage Explorer to pull files from that app specifically, but if it's a marketplace app or something built-in like the SMS store, no such luck.
Of course, you can get more permissions if you can call into a driver - which is what ID_CAP_INTEROPSERVICES allows you to do, and ID_CAP_INTEROPSERVICES is why you need interop-unlock. I'd suggest you focus on figuring out why you can't interop-unlock and fixing that. Unfortunately I can't really help you there; I don't have a Samsung phone and the steps to IU an HTC phone are very different.
Click to expand...
Click to collapse
Thanks for the clarification. I've spent the last month trying to figure out how to get the interop unlock working on my phone to no avail, which is why I was changing tact by asking this. Oh well, back to the old drawing board.
BTW if you or anyone know how to take a windows phone firmware CAB file and alter it (removing items) I'd appreciate it. My problem with updating the firmware is that I get a "file name conflict" error pointing to specific items in the CAB. At the risk of bricking my phone, at this point I'd try removing those items and installing it anyway.
Editing a CAB is easy; Win7 Explorer can open them natively and many third-party tools also exist. Editing a CAB so that it can still be isntalled may take a little bit more effort, but the important point is that as soon as you edit it, you'll invalidate the signature on the CAB. That means it will no longer install through the default update-OS at all. On HTC phones, you can use RSPL (or HSPL) to install custom updates, but on a phone with a retail bootloader (such as a Samsung), you can only install official updates.
Hi Folks
on 3.1.3 I had downloaded the OTA update via the ROM-inbuild functionality (Settings->System Update).
But, instead of using following the ROM-update function I decided to download the full 3.2 ROM and update via TWRP, as recommend on several locations.
Things are running fine now under 3.2, but System Update is constantly (after each reboot) nagging to update the system - I assume because it sees the update file somewhere and wants to proceed.
Does anybody here know where to look for this file ? I searched under a number of locations, so far without success.
Your help is much appreciated, thanks
Axel
You'll find the update in the internal storage under Android/data/com.oneplus.ota/files/.OnePlusOta (beware, the last one is a hidden folder!)
In my case, the file was inside the
Code:
.Ota
directory, which is root folder. Note that is a hidden directory, so make sure your preferences are set to see hidden files.
Hi, so I have a Surface RT, I was able, after a lot of effort to jailbreak it and enter Test Mode so any desktops apps that are meant for arm are working fine.
The problem is that now my Windows Store went bananas, I tried fixing it with some tutorials I found online, but nothing I can't revive it. Only option I would have would mean I recover the full tablet, install all updates only to later have to uninstall half of them and go trough the pain of installing the jailbreak again. Winch seems alot to get a app to work.
So I tried appx files, I tried installing using the powershell command as seen on some tutorial, winch gives me a bunch of errors, most of them are for libraries that are missing winch I do understand some of them just won't work for rt, others because the "app model" is set to 0 where it should be 1, I tried changing it to 1 but another error pops up saying the recourses.pri is missing or faulty or something on those terms. Tried with other apps but all just eventually ended in the same resources.pri error. Or that the os version it was requesting was higher. Since the appx were from nifty online sources I figured they would not be that compatible.
Later I tried Windows Apps Boss, this time i went to the official windows store (using IE) and downloaded the offficial files for the apps that I knew where compatible with ARM and this device. Anyone wondering I used this https://store.rg-adguard.net/ you just need to copy the URL from the windows store and it gives you the files.
First I tried downloading only the appx files and ran them on windows app boss, install, enable sideload, add package, the same recource.pri error appear, I tought maybe I need all the other files that were on the page meant for arm so I tried adding them as dependencies in windows app boss, added libraries to dependencies, and the other file that was a .blockmap I added to provisioned custom data, still nothing but closer, this time it only told the that the appxmanifest.xml was not on the package root whatever that mean, although I went to the windowsapps folder and the folder for the game in question and the file were there, but I noticed it was in the same path but in a different folder, with this I mean that I add 2 separate programs folders with 2 separate windowsapps folders, ok maybe windows apps boss created this one I thought, so I just moved them to the official folder and tried again, still nothing. Can it be because the original windowsapps folder is hidden? (just thought of this)
At this point I just want to flinch this thing at a wall or into a volcano, because every problem I fix just leads to another one, but since I got it for 50 bucks (I knew what I was getting into), and since now use it as my main pc since I don't have anything else or will have in a later future (its not that bad I just use mainly to watch movies, series now that I have the torrents desktop app, its relatively fast and works really well for basic stuff apart from the fact that Microsoft completely ruin the devices potential),I would like to at least be able to install metro apps or in this case games.
Can please someone help me out in figuring this, or guiding me another way to install them since every information in the internet is scattered and not always compatible with this device?
I successfully rooted my Samsung Galaxy A320FL following more or less this guide (I know, it's a video and that's annoying, but it's also very clear. And there is a text version linked in description), with some modifications though.
I will write here what differs / is not specified in that guide.
I also attach all the files I used; they can also be found on the internet with some search.
Make sure to have installed on your PC Samsung USB driver for mobile phones, available on Samsung website.
I used different versions of the files needed (that guide is for Samsung 8). With the following files, everything worked well:
twrp-3.4.0-0-a3y17lte.img.tar
no-verity-opt-encrypt-6.0.zip
RMM_Bypass_v3_corsicanu.zip (learned this from another guide on this forum)
Magisk-v20.4.zip
Once TWRP is installed, the guide instructs you to install no-verity, then reboot to recovery and immediately after that reboot to system; only later, transfer and install magisk. THIS MESSED UP everything, in my case at least.
The solution was even faster: once TWRP is installed
plug USB and transfer all needed files (listed above) at once
install no-verity and reboot to recovery;
install RMM_bypass and reboot to recovery;
install magisk and reboot to recovery
reboot to system
Now you proceed following the rest of the guide.
After rooting, you may want to fix a few problems you may encounter: see next post.
HOW TO FIX FINGERPRINT AFTER ROOT
When your Galaxy A3 is rooted, unfortunately fingerprint will not work properly to log in on your apps (but it will work to unlock your phone). To fix this:
install from Google Play a file manager (like Solid Explorer)
in the left menu select ROOT folder, then rename
/system/priv-app/SamsungPass_1.3/SamsungPass_1.3.apk
to
/system/priv-app/SamsungPass_1.3/SamsungPass_1.3.apj
remove /data/app/com.samsung.android.samsungpass-1
reboot
This will remove SamsungPass. You will not be able to use SamsungPass anymore on your rooted phone, so forget the ability of saving passwords on websites and confirm them with fingerprint (you can still save passwords in browser or use google autofill; you just can't confirm them with fingerprint).
But, with the method above, at least you will be able to use fingerprint to log in those apps which natively support fingerprint login (like banking apps).
HOW TO MAKE BANKING APPS WORK ON A ROOTED PHONE
...Banking apps, though, tend to stop working when they detect a rooted phone. You can try to fix this using Magisk Hide feature.
Open Magisk and tap on the shield icon
Tap MagiskHide
Check your bank apps and any other app that want to prevent from detecting root. (According to the guides I read, hiding too many apps can be a problem: stick to what is really needed).
HOW TO MOVE WHATSAPP MEDIA FOLDER TO SD CARD
This was the main reason why I decided to root my phone: I was running out of storage. So I bought a high-quality and fast sd card (yes, it deserves your 20 €) and did the following:
Download "Apps2SD" (the original by Vicky Bonick; it's free) and follow instructions on how to create partitions.
You can create upto 3 partitions: 1st fat32/exfat/f2fs/ext4/ext3/ext2 (it's your SD card), 2nd ext2/ext3/ext4/f2fs (it is used to link the apps), 3rd swap partition (it's optional).
IMPORTANT: With Apps2SD you can LINK apps (they will end up in 2nd partition) or use FOLDER MOUNT (the chosen folder will end up in 1st partition, the one that looks like your normal SD card).
Please note that for Whatsapp media folder you will use FOLDER MOUNT method: so it will end up in the 1st partition. Create the 1st partition large enough for your whatsapp media.
Use "folder mount (app analyzer)" feature: it's like folder mount, but it's pre-set for some common apps, including Whatsapp. With this feature, you can successfully move Whatsapp media folder to SD, in one clic.
To understand what folder mount means: see FAQ.
In my case everything worked fine. When I reboot I have to re-mount folder, but it takes one second (just open Apps2SD, tap Folder Mount, slide "whatsapp other").
By the way, with App2SD you can do much more: you can move virtually any app to your SD card using the "Link apps to SD card" feature, as explained in Vicky's video.
...Hope this will save you some time!
airali said:
I successfully rooted my Samsung Galaxy A320FL following more or less this guide (I know, it's a video and that's annoying, but it's also very clear. And there is a text version linked in description), with some modifications though.
I will write here what differs / is not specified in that guide.
I also attach all the files I used; they can also be found on the internet with some search.
(...)
Click to expand...
Click to collapse
Thank you! I successfully used your compilation for a T-Mobile branded unit, all works after some tinkering. I didn't have the fingerprint problem, possibly the Samsung security thing is not the same on the carrier-modified ROM.
I had problems first making root work because of the succession of operations - basically, everything needs to be formatted in TWRP so it can mount partitions. Once I boot up the ROM, TWRP won't mount anymore → every zip you want to install, you need to do in one go before you reboot to Android.
I tried to root mine, but it didn't show up in odin, it did show up in device manager but I can't do anything with it, no transfering files via usb, etc.
The drivers are installed, I reinstalled them a couple of times, tried a different USB port, etc...
No sucess so far, I hope someone here can help me
Tap tap tap