I need the community's help. I have never posted on XDA cause I have always been able to find the answers I was looking for by searching these forums. This time I am stumped. I am not a noob, but I'm also not a dev or programmer. I have managed, thanks to XDA, to unlock, root and flash a dozen different android devices I've owned without bricking any of them (I admit I'm a flash-a-holic and refuse to get treatment ).
I have a TFP (201) that refuses to download anything from anywhere except the Google Play Store. Cannot download via browser, Amazon app store, Goo Manager, Rom Manager or any other means. In each case it almost immediately tells me that the download was unsuccessful or download errored. I have done dozens of searches and have tried an equal number of so-called fixes with no luck. I have tried every custom rom on the forum, have switched between CWM and TWRP. I have flashed previous backups from TWRP. All to no avail.
Two other issues that may be related; 1- when i run the fix permissions script from inside Rom Manager or from Recovery screen, I get a "an error occurred while attempting to run priviliged commands!" 2- in CWM, when I try to flash older nandroid backups, it tells me that the files are not valid because it can't find the checksum (MD5) corresponding file.
I am currently running aokpcb_tf201_r2.1 with the kernel it comes with, everything else works except no downloading.
Any help would be greatly appreciated.
Can you check to see if your internal SdCard folder has the correct permissions using root explorer? I forget the details of exactly where it is, as I dont have my prime with me, however it is a folder within /data partition... something like /data/media/sdcard or something of that nature.
GooglePlay I believe uses the /cache partition for its downloads, thus I believe these are not throwing errors, whilst everything else is done into the internal sdcard folder.
Same oribkem
kokopuphz said:
Can you check to see if your internal SdCard folder has the correct permissions using root explorer? I forget the details of exactly where it is, as I dont have my prime with me, however it is a folder within /data partition... something like /data/media/sdcard or something of that nature.
GooglePlay I believe uses the /cache partition for its downloads, thus I believe these are not throwing errors, whilst everything else is done into the internal sdcard folder.
Click to expand...
Click to collapse
having the same problem , and you solution didn't work man .
kokopuphz said:
Can you check to see if your internal SdCard folder has the correct permissions using root explorer? I forget the details of exactly where it is, as I dont have my prime with me, however it is a folder within /data partition... something like /data/media/sdcard or something of that nature.
GooglePlay I believe uses the /cache partition for its downloads, thus I believe these are not throwing errors, whilst everything else is done into the internal sdcard folder.
Click to expand...
Click to collapse
This seemed to work. If you go to data/media/download and change the permissions this should fix the problem. I was unable to download anything using any browser or an email attachment.
Sent from my Transformer Prime TF201 using xda app-developers app
Related
THIS ZIP WILL FORMAT YOUR INTERNAL MEMORY CARD ALONG WITH SYSTEM AND CACHE. YOU WILL HAVE NOTHING BUT RECOVERY ON YOUR PRIME!!!
IF YOU DON'T WANT THAT TO HAPPEN, MOVE ALONG, THIS AIN'T FOR YOU!!!
AS WITH ANY FLASHING PROCESS, SOMETHING COULD GO WRONG!!!
NEITHER I NOR XDA SHALL BE HELD RESPONSIBLE FOR ANY DAMAGE
THAT YOU CAUSE BY FLASHING THIS ZIP!!!
Now that's out of the way, let me explain the reasons for this zip's existence.
I personally do not like having things left hanging around on my phone's SDcard
after I flash a new ROM onto it, I usually back up my data and format the card too.
It struck me that due to the nature of having an internal SDcard in the Prime
There most surely be stuff hanging around in there from all the flashing I've done.
I also find that hunting down application folders for apps that I have since deleted
can be rather tiresome as they are not always labelled as expected.
Maybe I'm just lazy, but there you go.
Now you can simply install this Zip and all of your partitions will be fresh and clean.
So that's why this zip was born unto the world.
ONCE AGAIN, THIS ZIP WILL FORMAT YOUR INTERNAL MEMORY CARD ALONG WITH SYSTEM AND CACHE. YOU WILL HAVE NOTHING BUT RECOVERY ON YOUR PRIME!!!
BEFORE STARTING, MAKE SURE YOU CAN ACCESS YOUR PRIME THROUGH ADB IN RECOVERY!!!!
INSTRUCTIONS: (THIS GUIDE ASSUMES YOU KNOW HOW TO SETUP AND USE ADB)
1. Download prime-full-wipe.zip to your Prime.
2. Backup everything from your internal SDcard to a location that exists outside of your Prime. USB Hard drive, flash drive or another SDcard.
3. After making certain that your data is safe, reboot your Prime to recovery. (zip will work in both CWM and TWRP)
4. flash the zip.
5. Once complete, you will need to reboot to recovery manually otherwise ADB push will not behave correctly.
6. After a successful reboot to recovery, open up Terminal or Command Prompt.
7. Push a new ROM.zip to your Prime via the command
Code:
adb push /path/to/rom.zip /sdcard/
If "/sdcard/" doesn't work, which sometimes happens use
Code:
adb push path/to/rom.zip /data/media/
for some reason it seems that "/sdcard/" is not seen all the time. So far seems to be a windows issue only.
8. Install your new ROM and enjoy that factory fresh taste.
I hope that these instructions are clear enough. If anyone needs help I or someone else will be happy to assist.
I STRESS AGAIN, THIS ZIP WILL FORMAT YOUR INTERNAL MEMORY CARD ALONG WITH SYSTEM AND CACHE. YOU WILL HAVE NOTHING BUT RECOVERY ON YOUR PRIME!!!
Credits to mero01 for the original idea and Team Virtuous for some sexy code used in the zip file.
KOUSH for CWM and Team Win for TWRP
Big thanks to swiss-prime and anthonyexmouth for being patient men/windows guinea pigs!
Thanks to Nandrew for pointing out that users may need to reflash CWM if experiencing ROM Manager errors after flashing this ZIP!.
UPDATE: 31/05/12
OK, so to anyone that has had problems pushing a new rom to the SD card after using this zip file. I have found some rather odd behaviour that sometimes occurs when formatting the Prime.
After many hours of testing yesterday, I found that when using CWM I simply couldn't push a file to the sdcard no matter whether I was pushing to "/sdcard/" or "/data/media/"
The only way I was able to get a rom onto the sd card was to eventually flash TWRP using fastboot and push the file after booting into TWRP. However after doing so and then getting a rom installed on the Prime, when looking through the file structure with Root explorer I found that the sdcard symlink had not actually been re-created properly, the file was there, but it was not showing as a folder, and as such, I believe that this is where the problem some people are having stems from.
The only solution that I found was to re-flash the full-wipe.zip again in TWRP and then push a rom onto the sdcard again. After successfully getting back into a working rom, I checked out the file structure and the alias had been properly re-created this time.
The behaviour is very weird and there seems to be no rhyme or reason to it. However, if you have had issues pushing to the sd card after using my zip, I can only apologise for your worry.
I hope that the above makes sense and helps people out who feel that they are now up sh*t creak without a paddle.
To be clear I do not believe this to be an issue caused by CWM, I believe it to be a Prime issue.
Update 01/06/12
Nandrew pointed out to me that you will receive non-critical error messages from CWM about a missing log file after using this ZIP. Once you have made a backup, a log file will be created and these error messages will cease.
You may also need to reflash CWM if you experience rom manager errors.
I think I should give it a shot!
john9 said:
I think I should give it a shot!
Click to expand...
Click to collapse
I'm heading out for about 20 minutes, but I'll be around after that. If you run into any issues.
This looks really helpful Dok - thanks! I seem to have accumulated a mass of crap on my SD card and I was wondering what to do with it...
I do have one question (not directly related to your zip). I have all this stuff on my SD card but I don't know which folders contain app user data and what can be safely deleted. Will TiBu restore all necessary user data to /sdcard after using this (obviously after copying the TiBu folder back to /sdcard ) or do I need to figure out what user data I need to keep for each of my apps before I wipe?
Hope that makes sense! Thanks again for this.
paddycr said:
This looks really helpful Dok - thanks! I seem to have accumulated a mass of crap on my SD card and I was wondering what to do with it...
I do have one question (not directly related to your zip). I have all this stuff on my SD card but I don't know which folders contain app user data and what can be safely deleted. Will TiBu restore all necessary user data to /sdcard after using this (obviously after copying the TiBu folder back to /sdcard ) or do I need to figure out what user data I need to keep for each of my apps before I wipe?
Hope that makes sense! Thanks again for this.
Click to expand...
Click to collapse
I haven't used TiBU yet, I made this zip and flashed it last night, then just flashed it again earlier, so I am currently with a Prime with no ROM.
I think though that TiBU should behave as normal, You may need to re-download app data for some of the biggies like games that have a separate download after the install.
Before I flashed it last night, I backed up the entire contents of the card to a USB hard drive, to make certain that I didn't lose anything at all.
<Edit> Nevermind... I read the whole post!
Doktaphex said:
I haven't used TiBU yet, I made this zip and flashed it last night, then just flashed it again earlier, so I am currently with a Prime with no ROM.
I think though that TiBU should behave as normal, You may need to re-download app data for some of the biggies like games that have a separate download after the install.
Before I flashed it last night, I backed up the entire contents of the card to a USB hard drive, to make certain that I didn't lose anything at all.
Click to expand...
Click to collapse
Thanks. I guess I am just not quite sure how TiBu works. When you do an normal factory reset thru CWM and leave /sdcard intact does TiBu restore a link to app user data located on /sdcard or does it completely rewrite it based on whats in /sdcard/TitaniumBackup/?
Doesn't really matter. I will just back everything up before I use this. I know I need to clean up /sdcard but am a bit chicken to use this
paddycr said:
Thanks. I guess I am just not quite sure how TiBu works. When you do an normal factory reset thru CWM and leave /sdcard intact does TiBu restore a link to app user data located on /sdcard or does it completely rewrite it based on whats in /sdcard/TitaniumBackup/?
Doesn't really matter. I will just back everything up before I use this. I know I need to clean up /sdcard but am a bit chicken to use this
Click to expand...
Click to collapse
Just finished restoring my TiBU and all my apps and relevant data are intact after only copying across the TiBU folder.
Im glad someone finally made this for everyone else. I had once had a problem with my prime that no matter how many times i wiped and reflashed my status bar was not working and when i tried to return to my back up of stock it was giving me read errors restoring the data section and would stop. I had to modify a zip to format what this does and then reflash and then everything worked again. Wiped my tf201 clean but hay it worked again and thats what mattered.
I would love to try this out but I am absolutely too scared of this ADB thing to work on pushing the Zip to the Prime...I figure I will brick it..
acdcking12345 said:
I would love to try this out but I am absolutely too scared of this ADB thing to work on pushing the Zip to the Prime...I figure I will brick it..
Click to expand...
Click to collapse
What operating system do you use on your computer?
adb is easier on Linux and Mac than on windows.
Doktaphex said:
What operating system do you use on your computer?
adb is easier on Linux and Mac than on windows.
Click to expand...
Click to collapse
It is windows. :-(
acdcking12345 said:
It is windows. :-(
Click to expand...
Click to collapse
I would have a look at the naked ADB driver thread here very useful for windows users and should help put some of those fears to rest.
Yes and if you follow this guide to install ADB it will be easy:
http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
ok, when you say reboot into recovery do you mean "fastboot"
cant find device in adb. using win7 with naked drivers.
Yeah, I dont think I am that gutsy to take this risk. But Ill keep researching it. I would like to start fresh as possible..
anthonyexmouth said:
ok, when you say reboot into recovery do you mean "fastboot"
cant find device in adb. using win7 with naked drivers.
Click to expand...
Click to collapse
No I mean exactly as I said. After flashing in recovery, you have to reboot back into recovery. It is a funny quirk that I may need to look into further.
No then, to your problem. Do you have an irc client on your computer? If so, come over to #asus-transformer on freenode irc and we can talk in real time.
If not, then I will endeavour to assist you here.
Gonna take the zip down for a moment until we can sort this out.
ok, rebooted into recovery and it now sees it in adb. i get a load of E: cant open lines but i guess thats cuz they aint there.
adb push "rom" /sdcard
all looks like its doing it but been stuck there for 20 mins.
leaving it just in case.
anthonyexmouth said:
ok, rebooted into recovery and it now sees it in adb. i get a load of E: cant open lines but i guess thats cuz they aint there.
adb push "rom" /sdcard
all looks like its doing it but been stuck there for 20 mins.
leaving it just in case.
Click to expand...
Click to collapse
I assume that you are abbreviating when you say adb push "rom" /sdcard
It should take no more than 3 minutes to push the rom
yeah full path is adb push c:\android\virtuousprime.zip \sdcard
So I flashed this ROM a bit earlier, and now, like a few other users in that thread, I cannot seem to be able to write anything to /sdcard. Installing and updating apps still works ok, but downloading anything with the browser, deleting any files in /sdcard, copying anything with wifi file explorer to /sdcard, or any I/O related thing to /sdcard fails.
Now here's the crazy thing. I've factory reset + wiped system and installed another ROM, as well as factory reset + wiped system and restored a backup, and still no go. Seems like something got borked pretty good...
Please advise.
Update...
Have tried a few more things, here's what works:
I can write to SDcard when connected to the computer via USB using the computer to send the files.
I can write to the SDcard when using TWRP's file manager.
I have tried fixing permissions, but that did not solve the problem.
TweakerL said:
Have tried a few more things, here's what works:
I can write to SDcard when connected to the computer via USB using the computer to send the files.
I can write to the SDcard when using TWRP's file manager.
I have tried fixing permissions, but that did not solve the problem.
Click to expand...
Click to collapse
have you tried this?
http://forum.xda-developers.com/showthread.php?t=1670824
then use ADB to push the ROM you want.. hope you know about pushing ADB... i just did it last night...
NOTE: I have searched and reviewed the existing threads on items with similar wording. Several on how to recover corrupted files within the backup etc.. Although the questions and issues are similar none describe the issue that I am experiencing.
Samsung Galaxy Note
Rooted on AOSP xXx FJ,(Flappjaxxx) / FJ Mod of ICS UCLF6
Currently on CWM Recovery 5.8.4.3
Situation:
No prior issues experience with nandroid backup, had 2 other backups plus the one I'm referring to (one of AOSP xXx and FJ Modded)
Performed a nandroid backup to try out CM09 from FJ AOSP. All went well... including the CM09 install and apps.
Missed the S-pen functionality and wanted to flip back to FJ Modded ROM.
Attempted to restore the most recent backup... Failed. Booted into CM09 and went to Root Explorer and looked into the backup file. I noticed that the file has a lot of what appears to be random ASCII characters for file names etc... (indicated to me that this file was corrupted).
Since I had other backups, I went to one of the older ones and restored.
Problem: this corrupted backup is taking up about 1.9 GB and I want to delete but it will not allow me. Looked at permissions and it has RW
Question: how the heck do I delete this thing without having to take my SD card out and formatting the sucker?
Thanks in advance
You should be able to plug in your phone to your computer via USB and open folder to view files on the /sdcard. Make sure USB connection is set to "USB Mass Storage" option when connected. Once you opened the folder to view files, you can navigate to the clockworkmod folder, open, and find the backups within that folder and delete that way...
Sent from my MB865 using xda's premium carrier pigeon service
Did you try to delete it in recovery (sorry if there is no such option, never looked for it...) or in root explorer? You could always get a terminal like https://play.google.com/store/apps/details?id=jackpal.androidterm and do like this:
su (if you're rooted)
cd /sdcard/clockworkmod/backup
rm -r 2012-07-12.13.37
Same commands should work in adb as well
Try. Android Commander.
jje
Sent from my GT-I9300 using xda premium
I think that plugging the USB charger into your computer and manually deleting it should do the trick :fingers-crossed:
OK...
Thanks guys for your responses...
- did try connecting to a PC in mass storage mode and tried to delete... did not work
- use Root Explorer to do a delete as well... did not work
- looked to see if there was a delete option in recovery (first thing I looked for) did not find it
I'll try the other options and see where that goes.
JohnnyQ1964 said:
Thanks guys for your responses...
- did try connecting to a PC in mass storage mode and tried to delete... did not work
- use Root Explorer to do a delete as well... did not work
- looked to see if there was a delete option in recovery (first thing I looked for) did not find it
I'll try the other options and see where that goes.
Click to expand...
Click to collapse
If you download clockwork mod (rom manager) you can delete it in the android application in manage and restore backups.
Empty recycle bin on PC sometimes helps when deleted stuff sticks, make sure do this when plugged in ofc
If you're using Windows, run chkdsk ("Scan this drive for errors" in drive's properties) when connected as a mass storage device.
That should help.
If it won't, the guaranteed method is to copy the files you need somewhere else, format the card and put those files back.
to clairfy, you were able to locate the back up files in the folder "clockwork mod-backup" but then it would not delete when you tried?"
Thanks again for all your input.
PC crapped out this past weekend... new hdd installed and re-building with Windows 7 pro-64 (hmmm... maybe I should dual boot to Ubuntu), will need to reinstall some of the linux/android tools.
@frdd... already had terminal installed tried the commands but no luck... it reports back I'm missing files and i get a lot of errors. I guess I'm gonna have to learn Linux/Android
@icomrade... I've got the purchase ver of ROM Manager and haven't fully gone down that rabbit hole but will investigate
@NeverGone\RU... will leave that as a last resort as i've got a 32GB SD card (sucks up time)
@mankows5... yes did find all the directories and files as it should be... just can't delete that 1 backup
Yeah, try Rom manager. Manage and Restore Backups>Select the one you want to delete, then delete it.
Hi, I'm using an LG Optimus L9 and running 4.3 bassed PAC-man rom.
The internal memory is 4GB and after installing a few apps, I started getting "Not enough storage space" warnings.
So, I checked the /data folder and found that there's directory called lost+found which is taking up a lot of space (Above 1.5GB).
I tried deleting files using ES Explorer with the data folder mounted as R+W, but it says "error deleting files"
Is it safe to delete the lost+found folder?
And if yes, how can I delete it since I'm unable to delete it with a file explorer app.
It would be really great if could recover thelost internal memory
void00 said:
Hi, I'm using an LG Optimus L9 and running 4.3 bassed PAC-man rom.
The internal memory is 4GB and after installing a few apps, I started getting "Not enough storage space" warnings.
So, I checked the /data folder and found that there's directory called lost+found which is taking up a lot of space (Above 1.5GB).
I tried deleting files using ES Explorer with the data folder mounted as R+W, but it says "error deleting files"
Is it safe to delete the lost+found folder?
And if yes, how can I delete it since I'm unable to delete it with a file explorer app.
It would be really great if could recover thelost internal memory
Click to expand...
Click to collapse
I don't think there is a problem doing that and change the permission to rwx-rwx-r try and report
sangalaxy said:
I don't think there is a problem doing that and change the permission to rwx-rwx-r try and report
Click to expand...
Click to collapse
I tried deleting the folder through adb shell.
Issued following commands:
adb shell
su
# cd /data
# rm -r lost+found
Click to expand...
Click to collapse
The output was "rm failed for lost+found. Operation not permitted"
Also tried this mounting /data as rw but no luck.
Tried chmod 775 on lost+found but no luck either.
Always getting operation not permitted message.
void00 said:
I tried deleting the folder through adb shell.
Issued following commands:
The output was "rm failed for lost+found. Operation not permitted"
Also tried this mounting /data as rw but no luck.
Tried chmod 775 on lost+found but no luck either.
Always getting operation not permitted message.
Click to expand...
Click to collapse
try r+w+x
sangalaxy said:
try r+w+x
Click to expand...
Click to collapse
Still getting the same error. Operation not permitted.
void00 said:
Still getting the same error. Operation not permitted.
Click to expand...
Click to collapse
may be something preventing it
try a reset and simply format the data in cwm do backup first
sangalaxy said:
may be something preventing it
try a reset and simply format the data in cwm do backup first
Click to expand...
Click to collapse
Using TWRP.
If I backup first, it will also back up the lost+found data
And restoring data will bring it back.
I did format data and system before flashing the rom. So I don't know why the lost+found has so large size.
What should I do?
void00 said:
Using TWRP.
If I backup first, it will also back up the lost+found data
And restoring data will bring it back.
I did format data and system before flashing the rom. So I don't know why the lost+found has so large size.
What should I do?
Click to expand...
Click to collapse
ok so don't backup
if anything goes wrong you can still flash the stock right??
sangalaxy said:
ok so don't backup
if anything goes wrong you can still flash the stock right??
Click to expand...
Click to collapse
hmm, i'll try flashing CWM and then do a format of every partition and freshly flash the rom.
Will report back if there's the same problem.
UPDATE:
Formatted all the partitions including /data/media using CWM
Did a fresh install of rom.
I've got my internal memory back
Thanks!
my 2 cents...
my 2 cents... I've opened the lost+found folder with the file manager (this https://play.google.com/store/apps/details?id=com.rhmsoft.fm), after enabling the root explorer functionality, and deleted a bunch of the biggest files, just checking they were at least 2-3 months old. Rebooted to make sure everything is fine and dandy, and now I've got enough free space, sun is chirping, birds are shining, life is beautiful :silly: :victory:
fabiosirigu said:
my 2 cents... I've opened the lost+found folder with the file manager (this *edited original link*), after enabling the root explorer functionality, and deleted a bunch of the biggest files, just checking they were at least 2-3 months old. Rebooted to make sure everything is fine and dandy, and now I've got enough free space, sun is chirping, birds are shining, life is beautiful :silly: :victory:
Click to expand...
Click to collapse
I was having the same problem. My phone is Samsung Galaxy S2 (GT-i9100). I was on stock Jellybean. But it was starting to feel sluggish and slow. So, having heard about the new Android Kitkat's lower memory requirements and smoother performance, i decided to install Cyanogenmod 11 on it.
Installation was not without problems. At first i flashed Clockworkmod Recovery 6.0.2.9. The phone bricked into a bootloop with a yellow triangle on it. Flashing the Cyanogenmod 11 resulted an error of "Status 7". So i searched for the latest Clockworkmod Recovery, which was at 6.0.4.5. After flashing the 6.0.4.5, Cyanogenmod 11 installed successfully. Performance was really smooth. No lags, no jitter, and everything worked like a charm.
The problem started when i re-installed my applications. Suddenly i got a message of "insufficient storage". This has never happened before. Note, that i previously had large games on my phone like Real Racing 3 and Bard's Tale. This time, i haven't even installed those large games. So i looked at my Storage, and found out that i only had 141mb of free space. But the weird thing is, my reported Apps was only 353mb, from 1.97GB internal storage. So there was over 1GB of storage just vanished.
I browsed for a solution to this problem, and landed on this thread. After reading reply from fabiosirigu, i decided to brave myself, and deleted the content of the lost+found folder (but not the folder itself). I accessed the folder with the built-in File Manager from Cyanogenmod, and set it to "Root Access Mode", and select all folder in the folder, and deleted it. The deletion took quite a few minutes, which felt like ages. Just sat on my bed, crossed my fingers, hoped that nothing will go wrong.
After the deletion, i rebooted my phone. the cyanogenmod logo appeared, and the system booted as usual. I just exhaled a massive sigh of relieve. I went straight to the internal storage, and now it is showing the correct report, 1.67GB of free space.
Thank you for your reply fabiosirigu. Really solved my problem.
lost+found genesis
Let somebody correct me if I'am wrong.
lost+found directory is standard for some unix/linux filesystems. All ext(s) 2, 3 and 4 contains it by default.
The operating system collects unidentified, broken files and its parts inside of l+f dir.
No one of these junks is used by running system.
So - you can look in l+f for some lost, missing files. If you don't miss for any (who knows it better?) then you don't need l+f content.
A little background first. Flashed stock recovery and my original first backup in order to take OTA for Marshmallow. OTA wouldn't take so I downloaded / installed MM update successfully. Currently at 6.0, 3.38.502.12. Then, re-unlocked bootloader (S-ON) and flashed TWRP 3.0.2.0. I then immediately created a full backup successfully before rooting.
Since that point, I've been unable to create another backup. I've also had countless problems trying to flash anything at all like custom ROMs and such. Keep having to revert to my unrooted backup post-MM update. The problem had to occur somewhere after my first successful TWRP backup post-MM update and now. Puzzling part is that I restored this same successful backup then without leaving TWRP, I immediately tried to do another backup and it fails the exact same way.
Recovery.log shows:
* MD5 Created.
Backing up System...
Error opening: '/system/app/Ds' (Not a directory)
I:Error in Generate_TarList!
Error creating backup.
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I've tracked this down and it does indeed appear to be a directory "Ds". Inside as a sub-directory called 'oat' with Ds.apk inside of that, which is the Dolby Audio service.
I'm completly stumped. Any ideas?
Update, in the /system/app/ (list of apps) it looks like there is an oat subdirectory followed by arm64 then filename.odex:
/system/app/BasicDreams/oat/arm64/BasicDreams.odex
However, when I browse to the problem app "Ds"... oat does not appear as a directory.
This could be a simple fix then?? Coudn't I just obtain root again, somehow change that oat to a directory and hope I see the rest of the subdirectories and files there?
OR... could I find Ds.odex somewhere and re-create the file structure?
Better yet! Would someone out there be able to give me or post a link for Ds.odex? Would it be as easy as me making a sub-directory called oat/arm64 and placing this Ds.odex file in there??
Any help would be much appreciated.
sirvalence said:
Update, in the /system/app/ (list of apps) it looks like there is an oat subdirectory followed by arm64 then filename.odex:
/system/app/BasicDreams/oat/arm64/BasicDreams.odex
However, when I browse to the problem app "Ds"... oat does not appear as a directory.
This could be a simple fix then?? Coudn't I just obtain root again, somehow change that oat to a directory and hope I see the rest of the subdirectories and files there?
OR... could I find Ds.odex somewhere and re-create the file structure?
Better yet! Would someone out there be able to give me or post a link for Ds.odex? Would it be as easy as me making a sub-directory called oat/arm64 and placing this Ds.odex file in there??
Any help would be much appreciated.
Click to expand...
Click to collapse
I don't have any oat directories under /system/app/(app name)/oat/ARM64/...
Only thing that is in the app directory (for me) is the .apk, and at times, a lib subdirectory (webviewgoogle is like that, which has an arm and arm64 directory under that).
I'm running VenomRom which may handle this differently.. it's prerooted and whatnot.
I also disabled boomsound which I think also disabled the Dolby sound system app from running. Viper is better [emoji2]
Id back up your internal storage again, ruu, flash twrp 3.0.0-2, boot into recovery, let it make system writable, reboot into recovery again, and see what happens.
Or flash a pre-rooted sense rom instead of stock.
I honestly couldn't get this stupid AT&T varient working correctly until I s-off'd, updated Sid to developer, then run dev ruu. Works great now.
Sent from my HTC One M9 using XDA-Developers mobile app
grandpajiver said:
I don't have any oat directories under /system/app/(app name)/oat/ARM64/...
Only thing that is in the app directory (for me) is the .apk, and at times, a lib subdirectory (webviewgoogle is like that, which has an arm and arm64 directory under that).
I'm running VenomRom which may handle this differently.. it's prerooted and whatnot.
I also disabled boomsound which I think also disabled the Dolby sound system app from running. Viper is better [emoji2]
Id back up your internal storage again, ruu, flash twrp 3.0.0-2, boot into recovery, let it make system writable, reboot into recovery again, and see what happens.
Or flash a pre-rooted sense rom instead of stock.
I honestly couldn't get this stupid AT&T varient working correctly until I s-off'd, updated Sid to developer, then run dev ruu. Works great now.
Sent from my HTC One M9 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks, yeah I'm having nothing but trouble since moving to MM. Each time, I can RUU back to stock ATT US and everything is fine. Not sure if it happens during my first TWRP pre-root backup, or the restore process. I looked at the recovery.log of said backup and nothing looked different regarding the /system/apps. I've since tried a few times and it just seems to throw a few /system/apps into another directory altogether, no rhyme or reason. Last try, there wasn't even a Ds directory as it disappeared. A Ds 0 byte file then appeared at /system level. This happened with 10 or so other random system apps. WEIRD! Maybe I should just S-OFF. I've never done that or changed my MID or SID for that matter. I'm still fairly new to this.
sirvalence said:
Thanks, yeah I'm having nothing but trouble since moving to MM. Each time, I can RUU back to stock ATT US and everything is fine. Not sure if it happens during my first TWRP pre-root backup, or the restore process. I looked at the recovery.log of said backup and nothing looked different regarding the /system/apps. I've since tried a few times and it just seems to throw a few /system/apps into another directory altogether, no rhyme or reason. Last try, there wasn't even a Ds directory as it disappeared. A Ds 0 byte file then appeared at /system level. This happened with 10 or so other random system apps. WEIRD! Maybe I should just S-OFF. I've never done that or changed my MID or SID for that matter. I'm still fairly new to this.
Click to expand...
Click to collapse
So worth the 25 dollars. But you need your system up and rooted for that to work.
But yeah, the dev edition SID 01 worked for me.
Made it way easier to work with and taking that ruu was magic.
Oh, also, do you have an sdcard? There is always the rom.zip method... placing the appropriate 0PJAIMG.ZIP in the root of the sdcard then rebooting into download mode works nicely.
Sent from my HTC One M9 using XDA-Developers mobile app