Hi all, first time posting here.
Details about my issue is below (a bit TMI)
Spoiler: How the OEM folder got deleted
[XZ F8331, Rooted]
- Tried to switch bootanimation.zip which was located in /OEM/Media
- Deleted the original 'bootanimation.zip' in the directory above using Root Explorer
- Tried to place a copy of new animation, did not work
- ANY interaction with OEM folder was prohibited (new folder, move or paste files, etc.) despite SU access on Magisk
Thinking I had a solution, I created a copy of OEM, placed the bootanimation.zip there, and tried to delete the original OEM folder but did not work. Said whatever and rebooted, and the "OEM - copy" was deleted, and the original "OEM" folder was somehow empty.
(tried to remount OEM etc, but did not get it to work)
My main concern is that the phone is working normally (so far) without the OEM folder, but I forgot what the OEM folder contained in the first place.
Does anybody know what the OEM folder is for (I remember there being .apk files), and would the phone be okay without it?
Would be awesome if someone could post their stock OEM folder here so I can maybe try to push it using ADB.
Sorry if this is all nonsense, first time rooting my device and had a lot of trouble along the way.
Related
In Root Explorer, if I try to paste a folder in a situation where it should overwrite the target folder, it is instead placed inside it. For example:
1) create /sdcard/test/
2) copy the new folder
3) paste into /sdcard/
The result should be that one test folder overwrites the other, with no structure change. However, you end up instead with /sdcard/test/test/
If I instead delete "test" before step 3, the pasted test ends up where it should (inside /sdcard/, rather than inside /sdcard/test/). The moral seems to be if you know you are going to overwrite a folder, you must manually delete it first (which makes backup restoration with multiple indentured over-writes problematic).
Try for yourself and see. Am I missing something? Is this a known issue?
Hi. I tried changing the boot up (and down) animation on my One S (S3). And it just doesn't seem to work. I don't get how. Here's all the things I did:
1. Copied the zip file to my phone, through USB. Renamed it to hTC_bootup_one.zip (as mentioned here: http://forum.xda-developers.com/showthread.php?t=1637870). Then moved it to /system/customize/resource using ES file manager.
2. Copied it to my phone. Booted into TWRP recovery. Moved the file from there.
3. Tried replacing the bootanimation.zip and hTC_downanimation.zp with the same zip file.
All three times, it moved the file just fine. ES asked me everytime if I wanted to replace the original file. And after I replaced it, I went into the zip file with the archive viewer, and checked the files, and they were the right ones.
But every time I shut down and restart, I still get the original animation. What am I doing wrong? Is it the wrong location? Please, please help!
I'm running TrickDroid v5.0.0. Could this be the issue?
Finally, this is the file I'm trying to use: http://forum.xda-developers.com/showthread.php?t=1732732
Did you set the permission correctly?
Goatshocker said:
Did you set the permission correctly?
Click to expand...
Click to collapse
Sorry, but what exactly do you mean? Permission for the zip file? Or permission to write onto the system folders? I've got the latter covered. I do have permission to write in the root folders. But if you're talking about permission for the zip file itself, I'm not sure how to do that!
Im talking about the step "- Set permissions to rw-r--r--"
Its done through a terminal or adb shell witrh the command 'chmod'. Im not sure what number rw-r--r-- translated to though, maybe 766 or something.
Goatshocker said:
Im talking about the step "- Set permissions to rw-r--r--"
Its done through a terminal or adb shell witrh the command 'chmod'. Im not sure what number rw-r--r-- translated to though, maybe 766 or something.
Click to expand...
Click to collapse
I just checked that. And yep, it's set to the correct permissions. rw-r-r. The odd thing is though, the original boot animations aren't even there anymore. Since I replaced them with the new one. So how it it even showing me the original one still? Am I doing this in the right location for the One S (S3)? /system/customize/resource?
No idea where its located actually... Try a search for the file and see if it pops up elsewhere (ES Fileexplorer can search, other explorers can probably too)
Goatshocker said:
No idea where its located actually... Try a search for the file and see if it pops up elsewhere (ES Fileexplorer can search, other explorers can probably too)
Click to expand...
Click to collapse
Right so I gave up, relocked, reflashed stock recovery, got the official JB update, unlocked, flashed TWRP, and viola, boot animation works. So basically the problem was with TrickDroid. I'm not sure what. But, there you go. Thanks anyway.
I recently Wiped my Phone completely and decided to Re-Flash Viper 1.2.1.
I noticed a problem prior to re-installing but thought nothing of if since it wasn't crucial at the time.
In Root explorer, I am able to delete [i normally delete boot animations] system files but not add where I need to add. Example, I wanted to add a ringtone to my system/media/ringtones folder. I normally [for the last six years] could just copy and paste such files using a root file manager.
However, when I any these files to for example /system/customize/resource/ it doesnt add it. BUT IT DOES rename the file and save it under a dif folder.
Example. Tried copying-copy to-moving to "androidtwirp.mp3" from sdcard to /system/media/notifications and a message pops up saying"notificationsandroidtwirp.mp3 successfully copied-moved to" and it saves notificationsandroidtwirp.mp3 to /system/media/ and it stays there. retrying from that location only results in "notificationsnotificationsandroidtwirp.mp3".
So not only does it rename the file but it saves it in the wrong location. I am at a loss for word. I tried the basics to tryand fix this but i cant seem to hit it on the head.
Thanks!
Edit: Not updating Super SU app, file explorer seems to have worked. Will attempt to duplicate problem to see what actually caused.it.
FOUND IT!
Updating my ES File explorer broke my system writing ability. DO NOT UPDATE is because when you do...
Any file you move, copy/paste to the system will not work properly.
This first happened when I tried to copy and paste a boot animation after I updated ES root explorer. It would rename whatever file i was trying to paste/move/copy over and save it under a sub folder.
example.
copying a ringtone [i.e. androidtwirp.mp3] from SDCard to System folder, the path is /system/media/audio/ringtones/ and it would rename it "ringtonesandroidtwirp.mp3" and save it under /system/media/audio/.
So basically not only was it renamed [which i didnt want it to be] but it would save it to the folder before the actual folder i needed it to be in, plus it would corrupt the file deeming it useless.
moving "ringtonesandroidtwirp.mp3" into the correct folder would only result in "ringtonesringtonesandroidtwirp.mp3"
this happened across the board with all files being moved around
The ES File Explorer version 1.2.1 comes with works flawlessly so don't update it.
I uninstalled ES [also any folders in SDcard related to it] and downloaded JRummy's root explorer and everything is back to normal except i have to reboot the phone to see files [like ringtones and notifications] that i added to the system.
I think it has something to do with our devices having an unlocked bootloaader, but still S-ON. There's S-OFF in the Dev section now if you really need to write to the system folder a lot.
I came from the Vibrant so I know what you're going through
Yeah, im on a low hboot so s-off might not be in my plans since I can practically flash what I want but it was ES file explorer, when I updated the apk the root permissions broke when writting to the system. I emailed the dev and they said they'd have it fixed on the next update.
echo en Android
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.
I accidentally deleted bluetooth. I flashed(?) the stock recovery found in this thread http://forum.xda-developers.com/pure-xl/general/twrp-recovery-root-blu-pure-xl-allview-t3269447 and had no luck. I also tried factory resetting it. Any ideas on how to get it to work again? Whenever I try to enable bluetooth I get the "Bluetooth share has stopped working" error.
gasmp said:
I accidentally deleted bluetooth. I flashed(?) the stock recovery found in this thread http://forum.xda-developers.com/pure-xl/general/twrp-recovery-root-blu-pure-xl-allview-t3269447 and had no luck. I also tried factory resetting it. Any ideas on how to get it to work again? Whenever I try to enable bluetooth I get the "Bluetooth share has stopped working" error.
Click to expand...
Click to collapse
Do you mean you uninstalled one of the Bluetooth apps in System > Advanced Settings > Apps > All?
If so, please use some sort of root explorer app (you have to be rooted first) to navigate to either /system/app/Bluetooth or /system/priv-app/Amigo_Bluetooth and install whichever .apk that appears to be not installed. I believe this should fix your issue.
Short Circuit said:
Do you mean you uninstalled one of the Bluetooth apps in System > Advanced Settings > Apps > All?
If so, please use some sort of root explorer app (you have to be rooted first) to navigate to either /system/app/Bluetooth or /system/priv-app/Amigo_Bluetooth and install whichever .apk that appears to be not installed. I believe this should fix your issue.
Click to expand...
Click to collapse
Alright so the .apk file is missing from system/apps/Bluetooth. The one in amigo_bluetooth is still there
gasmp said:
Alright so the .apk file is missing from system/apps/Bluetooth. The one in amigo_bluetooth is still there
Click to expand...
Click to collapse
Interesting.
I've uploaded my /system/app/Bluetooth folder here. Could you please download that, extract the folder inside to somewhere, and either:
Push the folder via adb using the command adb push Bluetooth /system/app/ while your command prompt/terminal is in the same directory where you extracted the "Bluetooth" folder (cd DRIVE:\your\directory\path\Bluetooth (Windows) or ~/your/directory/path/Bluetooth (Linux) ).
or
Transfer the extracted "Bluetooth" folder to either your microSD or a USB Drive, plug it into your phone and move the folder to /system/apps using your root file explorer app.
Finally, install the Bluetooth.apk inside (which I'm assuming is the one you uninstalled since it is missing).
Let me know how it goes, thanks!
Short Circuit said:
Interesting.
I've uploaded my /system/app/Bluetooth folder . Could you please download that, extract the folder inside to somewhere, and either:
Push the folder via adb using the command adb push Bluetooth /system/app/ while your command prompt/terminal is in the same directory where you extracted the "Bluetooth" folder (cd DRIVE:\your\directory\path\Bluetooth (Windows) or ~/your/directory/path/Bluetooth (Linux) ).
or
Transfer the extracted "Bluetooth" folder to either your microSD or a USB Drive, plug it into your phone and move the folder to /system/apps using your root file explorer app.
Finally, install the Bluetooth.apk inside (which I'm assuming is the one you uninstalled since it is missing).
Let me know how it goes, thanks!
Click to expand...
Click to collapse
You just saved my phone's Bluetooth! Thank you very very much.
gasmp said:
You just saved my phone's Bluetooth! Thank you very very much.
Click to expand...
Click to collapse
Glad it worked!
Do I creat app folder?
I don't have a /system/app/ folder, just a /system folder with subfolders, none are called app.
Do I create the app folder?
degarb said:
I don't have a /system/app/ folder, just a /system folder with subfolders, none are called app.
Do I create the app folder?
Click to expand...
Click to collapse
Can you check again? Make sure you go to your system folder from your phone's root directory. It should contain almost all of the default apps installed on your phone when it came out of the box (with the rest of it being in priv-apps).
I have the exact same problem as the OP - I tried downloading the said file but my phone says the file is corrupt - can someone please send an updated version?
Same problem, file corrupt.
Bluetooth got erased because the system detected that the app was sending sms by itself (or so it said) and thus deleted it. I have the same problem as the one above, the file seems to be corrupt and can't install the .apk
Please, if there is another way to solve this say so.
Same problem...
I have the same problem as above, my phone detected the SMS permission and said it might cost you money and recommend an uninstall. I never realised I would be able to uninstall Bluetooth without being rooted but it did it anyway - maybe it's an android bug?
Anyway, I tried downloading your Bluetooth.apk and reinstalling but it said file corrupt.
Any help would be much appreciated! Sounds like this is a bug that's been going around...
Hello, I cant find the Amigo Bluetooth folder in /system/priv-app. So Can anyone please provide me the folder here
Also any other solution for re enabling the Bluetooth
Moto 4 Bluetooth gone
Same problem here
Did anyone found a solution yet?
https://forum.xda-developers.com/pure-xl/help/guide-unbrick-softbricked-blu-pure-xl-t3371981
following this thread will allow you to reload the factory rom to default settings, including all factory apps and files. this is a "OEM reset"
to the fullest, bringing phone back to factory sent condition. (be prepared to do a few ota updates when done)
pay attn and read the whole thread (Yes I know its long) especially when it talks about SP Flash tool...
tbirdguy said:
https://forum.xda-developers.com/pure-xl/help/guide-unbrick-softbricked-blu-pure-xl-t3371981
following this thread will allow you to reload the factory rom to default settings, including all factory apps and files. this is a "OEM reset"
to the fullest, bringing phone back to factory sent condition. (be prepared to do a few ota updates when done)
pay attn and read the whole thread (Yes I know its long) especially when it talks about SP Flash tool...
Click to expand...
Click to collapse
Thanks for the info.
I dont know yet if a simple apk via adb could fix the problem here instead of flashing the complete device
Fixed
Hey, I had a look elsewhere and found a forum on the Lenovo website (can't post link here), hopefully this will work for you too.
Basically you want to go to Settings>Apps>Reset app settings and that'll do the trick.
Good luck!