I have Prestigio Multipad pmp5197d.
I use the built in system update in the Settings. It downloads an update.zip file and then reboots to recovery, but update package does not show up, so can't select it for installation. Just shows an emty root folder.
File explorer shows the zip file.
I have tried copying the file to external SDcard and everywhere the File Explorer allows me to, still no luck.
I have been googleing for some hours, no solution for the specific questions.
I need to update because YouTube is not working (can't update YouTube app) anymore due to system not being updated.
Anyone seen something like that?
Its a super low end device, not much info around for the specific model. But I doubt it's a model specific problem.
Related
I have Galaxy 3 with Kyrrilos 8.1 and in root of my sdcard is hidden file .config_c38
Does anybody knows what this file is and from which application? Does anyone have this file too?
I tried to delete it but it always immediately appears again.
It's a text file obviously with some configuration setting. Inside is a text of about 100 characters without spaces and starts with zdyFt8GYHJH....etc
Interests me too.
I had that file on SD at the time I was testing various apps for my phone, so the file was from one of that apps. But now I don't have that file anymore, so it has to be from some of the app I don't use anymore. I never found out which one.
More than that I can't help you.
I have two separate issues which I believe are caused by the same thing.
1. When I try to alter platform.xml in the /system/etc/permissions folder via ES File Explorer to enable 3rd party apps to have write capability to the SD card, the edit is unsuccessful and my phone reboots. When I pull a copy of the file to my PC, alter it, and then try to push it via ADB, the same thing happens. I previously used the ADB pull/push method to edit my hosts file and had success with that after doing it while in Recovery, but this time around both ways (in recovery and with the device booted up) result in my device rebooting. For the SD card fix, I've also tried the app that does it for you and encounter the same issue.
2. When attempting to update the SuperSU binary, the update fails my device reboots. This happens with either update method - normal and recovery.
So both issues seem to have the same root cause... my phone will not allow any editing of system files. Anyone have any suggestions?
For reference I'm on a Galaxy Note 4 (model SM-N910T) on T-Mobile.
Baseband version N910TUVU1ANJ7
Android version 4.4.4 (stock ROM)
Kernel version 3.10.0-2796035
Build number KTU84P.N910TUVU1ANJ7
I'm also running Wanam Xposed - not sure if that has anything to do with anything but just fyi.
Thanks
bump... anyone have any ideas?
replace the altered xml with a original/stock one..
If u have a backup
abhinavp649 said:
replace the altered xml with a original/stock one..
If u have a backup
Click to expand...
Click to collapse
I have the stock .xml in there right now... my problem is that I want to replace it, but I can't because my phone reboots every time I try.
Gakuseinozen said:
I have the stock .xml in there right now... my problem is that I want to replace it, but I can't because my phone reboots every time I try.
Click to expand...
Click to collapse
Is your Phone is rooted? If yes:
place the altered .xml somewhere in your sd card.
1. Install an app called Total Commander.
2. Navigate to the location where your stock file is located.(delete it)
3. Now goto sd card where you placed your altered file.
4. Tap on Icon of the .xml file, You will see a green tick mark on it.
5. When your file is selected. Tap on Copy/Move to Icon.( u will see two files one on one with a blue arrow)
6. Now Click on '>>' button to browse the location where you have to Copy/Move the File.
7. Now Tap Copy if You want a backup placed in sd card of the file or move if you just want one file to be there.
(Through all the Process I am assuming that your phone is rooted and you Have Granted SuperUser permissions to Total Commander)
abhinavp649 said:
Is your Phone is rooted? If yes:
place the altered .xml somewhere in your sd card.
1. Install an app called Total Commander.
2. Navigate to the location where your stock file is located.(delete it)
3. Now goto sd card where you placed your altered file.
4. Tap on Icon of the .xml file, You will see a green tick mark on it.
5. When your file is selected. Tap on Copy/Move to Icon.( u will see two files one on one with a blue arrow)
6. Now Click on '>>' button to browse the location where you have to Copy/Move the File.
7. Now Tap Copy if You want a backup placed in sd card of the file or move if you just want one file to be there.
(Through all the Process I am assuming that your phone is rooted and you Have Granted SuperUser permissions to Total Commander)
Click to expand...
Click to collapse
I'm assuming this will end with the same result as when I try it through ES File Explorer. ES has the same capability and I have given it root access already. Something is causing all attempts to alter system files to fail, regardless of root access.
Gakuseinozen said:
I'm assuming this will end with the same result as when I try it through ES File Explorer. ES has the same capability and I have given it root access already. Something is causing all attempts to alter system files to fail, regardless of root access.
Click to expand...
Click to collapse
This was not successful. Anyone else have any ideas? I tried posting logs in the SuperSU update failure thread, with the logic that if I get that issue fixed my other issue will be resolved also, but Chainfire hasn't responded to any of the requests in a while.
I recently rooted my G3. Step two was to download a recovery and make a backup. Recovery downloaded fine. Started making my backup and everything seemed to work. It said it successfully made the backup, but I can't find the nandroid file anywhere. I've read some other threads about where they are typically located, and forgive me if I'm overlooking one here on XDA, but my backup isn't in any of the locations those threads suggest. There is no folder that I can find named TWRP. I've looked in media, backups, storage, mnt, nothing. This is looking from both The file explorer within the TWRP Manager app, and ES File Explorer. The most I can find are these three files with question mark icons called "TWRP", "oldrecovey", and "newrecovery" (see screenshot, files are at bottom left). Nothing there though under the file name I saw when I created the backup....which was the date, and then a few more numbers, and then I added the word "stock" to the end.
I did notice a prompt when I opened TWRP the first time that said I didn't have busybox installed and would I like to install it. I clicked on to install it but it didn't seem like anything happened. Could that be the issue?
I'm sure it's something simple but I'm new to all this.
Thanks!
Update on this. I figured out that ES File Explorer has to have root access enabled. So, I did that, and now I can find the recovery file in ES File Explorer. Still not seeing it in the file menu of the TWRP Manager app though. I'm glad to know my backup does in fact exist, however it seems like I'm going to want to be able to navigate to it through TWRP Manager if I ever really need to use it.
Still can't navigate to backup in TWRP Manager
I can navigate to /data/media/0/TWRP/BACKUPS with ES File Explorer, but not from within TWRP Manager. Gotta be a fix for this. Anyone??
Hi,
I own a No.1 D5+ (smart watch - runs a standard Android 5.1, not Android Wear). The watch works well enough for what I had in mind when buying it, but there is one annoying thing: during bootup and shutdown it plays a melody at full volume regardless of the volume settings.
My plan was to root the device and delete / replace the file containing the melody. I searched for instructions specific to my model but couldn't find much, so I tried my luck with Kingoroot. That seems to have worked, though the root explorer app installed during the process still says it's not rooted, contrary to what the Kingoroot says.
Anyway, I tried renaming / deleting / overwriting the file both through Android Studio's Device Explorer and via adb shell, but always get an error "remote Read-only file system".
I'm guessing that means the /system/ folder is in ROM and can't be changed, or could it still be a software write protection? Is there anything else I could try to silence booting/shutting down?
I'm pretty new to all this, so any help is appreciated!
Hi guys,
I was checking my download folder today using the default Files app and saw this .apk file that I didn't download. Naturally, I wanted to remove the .apk but when I tried to remove it, the function failed.
I tried to get more information but there's nothing I can do to the .apk. I can't open it, copy it, rename it, etc.
Next step, I plugged my phone into my computer and looked at the internal Downloads folder via USB file transfer. I could not see that specific .apk, even with view hidden objects on.
So, I went into my file manager app (Amaze with root access) and went to the emulated Downloads folder, same thing. The folder did not show the .apk at all.
I opened up SD Maid and see if they can find and remove the file, but nope, didn't work.
Now, I'm thinking it's probably just a bug with the Files app so I deleted user data and cache, restarted my phone and all that but still, that .apk persists.
I'm at my wit's end and I have no clue how to remove this file. Any help will be appreciated.
I'm using Google Pixel 3, Android 10.
SeraphChaos said:
Hi guys,
I was checking my download folder today using the default Files app and saw this .apk file that I didn't download. Naturally, I wanted to remove the .apk but when I tried to remove it, the function failed.
I tried to get more information but there's nothing I can do to the .apk. I can't open it, copy it, rename it, etc.
Next step, I plugged my phone into my computer and looked at the internal Downloads folder via USB file transfer. I could not see that specific .apk, even with view hidden objects on.
So, I went into my file manager app (Amaze with root access) and went to the emulated Downloads folder, same thing. The folder did not show the .apk at all.
I opened up SD Maid and see if they can find and remove the file, but nope, didn't work.
Now, I'm thinking it's probably just a bug with the Files app so I deleted user data and cache, restarted my phone and all that but still, that .apk persists.
I'm at my wit's end and I have no clue how to remove this file. Any help will be appreciated.
I'm using Google Pixel 3, Android 10.
Click to expand...
Click to collapse
Same is happening with me right now
Using Oneplus 5 Android 10