So I changed the boot animation to something different. The animation is so heavy the phone lags halfway in between and now my phone can't even get past the boot animation screen. It's stuck at the boot animation. Anyway to revert this?
Download the default boot animation from here: http://forum.xda-developers.com/google-nexus-5/themes-apps/bootanimation-nexus-5-animations-t2789918
Scroll down a bit and you'll find the default Lollipop animation. Download the zip which is supposed to be manually installed.
Put it in system/media/bootanimation.zip
You can use Aroma File Manager for this. AromaFM is a flashable zip which brings up a file manager in your recovery
experience7 said:
Download the default boot animation from here: http://forum.xda-developers.com/google-nexus-5/themes-apps/bootanimation-nexus-5-animations-t2789918
Scroll down a bit and you'll find the default Lollipop animation. Download the zip which is supposed to be manually installed.
Put it in system/media/bootanimation.zip
You can use Aroma File Manager for this. AromaFM is a flashable zip which brings up a file manager in your recovery
Click to expand...
Click to collapse
I can't even access my phone's storage so how am I suppose to use the zip? Are you saying I can flash the zip file while the phone is in fastboot/recovery?
If you're using TWRP as a recovery you can access your storage. It does support MTP.
Yeah, the file manager has to be flashed just like a ROM.
experience7 said:
If you're using TWRP as a recovery you can access your storage. It does support MTP.
Yeah, the file manager has to be flashed just like a ROM.
Click to expand...
Click to collapse
And that's the problem. I'm running a stock rom (4.4.2) with no TWRP or CWM.
The phone is rooted and the boot-loader is unlocked.
Bootloader unlocked. So where's the problem?
Download latest TWRP and execute
fastboot flash recovery twrp.img
to flash it.
Or simply
fastboot boot twrp.img
to launch it once. You don't even need to flash it.
experience7 said:
Bootloader unlocked. So where's the problem?
Download latest TWRP and execute
fastboot flash recovery twrp.img
to flash it.
Or simply
fastboot boot twrp.img
to launch it once. You don't even need to flash it.
Click to expand...
Click to collapse
AYEEEEE!!! I see where you're going with this now. I think I get it now. I'll try tonight or maybe in a couple of hours and then I'll come back if any problems. Once finished I'll let you know with a thanks
By the way: After copying the new (default lollipop) bootanimation.zip to /system/media do a 'fix permissions' in TWRP. Not quite sure if the option is available in TWRP but if it is, just do it. It won't do any harm
Alright I flashed TWRP and it's working but the file manager kinda sucks. I mean it's picking up the files and their aren't any options to copy and paste. The boot animation is stored in /system/media and when I go into the system folder all I see is "bin" and nothing else. I don't understand what's the problem
Man, the file manager does not suck. A little more respect to the developer! You should be thankful, not disrespectful!
Enable hidden files in the file manager and you'll see them. And it also does provide copy/paste functionality. I've used it several times.
EDIT: If you still don't see them after enabling hidden files you have to mount the system partition.
experience7 said:
Man, the file manager does not suck. A little more respect to the developer!
Enable hidden files in the file manager and you'll see them. And it also does provide copy/paste functionality. I've used it several times.
Click to expand...
Click to collapse
I searched everywhere and I don't see an option to enable hidden files. How did you enable hidden files?
It's in the lower right corner if I remember correctly. Three dots which will bring up a menu.
...
experience7 said:
It's in the lower right corner if I remember correctly. Three dots which will bring up a menu.
Click to expand...
Click to collapse
What version of TWRP are you using? I don't see three dots anywhere. The bottom always has a back button on the right, a button to launch terminal in the center and a home button on the left
Dude. It has nothing to do with TWRP version at all. You didn't even launch Aroma File Manager... that's the point.
Read my previous posts again, take your time & don't double post (there's an option to edit if you have to).
experience7 said:
Dude. It has nothing to do with TWRP version at all. You didn't even launch Aroma File Manager... that's the point.
Read my previous posts again, take your time & don't double post (there's an option to edit if you have to).
Click to expand...
Click to collapse
Sorry for being impatient.
Do I flash Aroma the same way I flashed TWRP? If so will this cause any problems or anything? TWRP can't install Aroma from SD because my computer won't even pick up my phone
If you're in TWRP, connect your phone to your computer. It should be detected just like any Android phone since it's also using MTP.
Aroma File Manager has to be flashed in TWRP (install zip). That's why you had to flash TWRP in the first place.
experience7 said:
If you're in TWRP, connect your phone to your computer. It should be detected just like any Android phone since it's also using MTP.
Aroma File Manager has to be flashed in TWRP (install zip). That's why you had to flash TWRP in the first place.
Click to expand...
Click to collapse
Better yet as soon as I connected my phone to my PC, TWRP's file manager started working. I deleted the corrupted bootanimation.zip that made my phone lag in the first place. However it keeps failing to move the other bootanimation.zip into /system/media (I backed up the stock boot in /system/media by renaming it
EDIT: Never-mind I got it. I renamed the file from 0bootanimation.zip to "android" and then to bootanimation.zip
I restarted my phone and it's just stuck in the boot loop. The animation is occurring forever and nevermind it just started.
Thank you experience7!!! Massive vouch for you man. You saved me so much trouble. Much love from me =D
As said before... TWRP uses MTP to enable file transfer between your computer and your phone. However, you'll only see your internal storage (pictures, videos and stuff like that) - not the system partition. That's why you should use Aroma File Manager! It lets you access the system partition directly on the phone and provides everything you need (copy/paste/delete and so on).
I have no idea what file you actually deleted. But I'm pretty sure it was not the one in /system/media.
experience7 said:
As said before... TWRP uses MTP to enable file transfer between your computer and your phone. However, you'll only see your internal storage (pictures, videos and stuff like that) - not the system partition. That's why you should use Aroma File Manager! It lets you access the system partition directly on the phone and provides everything you need (copy/paste/delete and so on).
I have no idea what file you actually deleted. But I'm pretty sure it was not the one in /system/media.
Click to expand...
Click to collapse
And that's the most weird part of all...
1) TWRP file manager started working as soon as I connected my phone to my PC. I didn't need to flash AromaFM. TWRP worked like a charm
2) I deleted the laggy bootanimation.zip and replaced it with the stock one I backed up. I backed up the stock animation by renaming it to a different file. However TWRP always failed to rename the stock animation to bootanimation.zip. So I renamed it entirely different (to android) and then back to bootanimation.zip and it worked like a charm.
Does that make sense now? I don't know what the hell just happened but I ain't complaining
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 have tried changing the location, rebooting my phone, changing the file to a .zip, etc. but nothing is working. When i change it to a zip and try to open it, it says the archive is damaged. When i delete the backup file and then recreate a backup, its still just a "File" type of file. Am i missing a setting or something? No matter where i place the backup it's the same thing. Im trying to turn it into a folder so i can drag in other backup files. I keep breaking the phone due to the locked bootloader, and the other 3 times titanium made a folder with all the backup contents in it.
P.S. I dont want to back it up to something like google drive. Someone always says to do that on every thread i look at
I recently tried a failing technique to remove my password on my Moto G3 (Android 6.0) by removing a file and putting a copy of the file back. The .key file I copied is stored in Root→Data→System→ gatekeeper.pattern.key (gatekeeper.pattern.key is the actual file). I still have a original copy of this file. After I copied the file to my Internal Storage, I deleted it from the root area. I checked to see if my pattern password had been removed, which it had. At first I thought it was great, until I went to set another password. I went in to Settings→Security and tapped Screen Lock. A message popped up that said “Unfortunately, Settings has stopped working.” I would rather not have to reinstall my system, so if anyone knows how to fix this please tell me. Also if you know of any other ways to remove a password on android without knowing the password, that would be great. Thanks!
Hey,
Tired of seeing this message when trying to enroll a fingerprint?
I have seen many people asking for fix and there has also been a file around here for the fix zip. But it was always hard to find that file so here it is.
Steps for fixing fingerprint:
Code:
1. Reboot to recovery
2. In the file manager, go to /persist/data/
3. Delete all the files named finger_0_x and finger_0_x.bak (finger_0_1, finger_0_1.bak,...)
4. Reboot and try again.
If it still doesn't work, flash the attachment zip in recovery.
This works wonders!!!
EDIT: Please notice that I am not the owner of the file!
Your zip file just killed my phone
not working
KamiMK said:
Hey,
Tired of seeing this message when trying to enroll a fingerprint?
I have seen many people asking for fix and there has also been a file around here for the fix zip. But it was always hard to find that file so here it is.
Steps for fixing fingerprint:
Code:
1. Reboot to recovery
2. In the file manager, go to /persist/data/
3. Delete all the files named finger_0_x and finger_0_x.bak (finger_0_1, finger_0_1.bak,...)
4. Reboot and try again.
If it still doesn't work, flash the attachment zip in recovery.
This works wonders!!!
EDIT: Please notice that I am not the owner of the file!
Click to expand...
Click to collapse
sorry for reviving this old thread, but I have been digging around for solution for quite some time and can't really get to the bottom of this.
I am facing the exact same problem - after upgrade, did factory reset on stock 10 but did not remove fingerprints prior, and now enrolment simply fails each time. Files you listed above are not present inside /persist/data (using twrp file manager).
if I flash persist.img I am afraid that could kill my device since some are suggesting that there are device specific information on that partition...
any suggestions?
KamiMK said:
Hey,
Tired of seeing this message when trying to enroll a fingerprint?
I have seen many people asking for fix and there has also been a file around here for the fix zip. But it was always hard to find that file so here it is.
Steps for fixing fingerprint:
Code:
1. Reboot to recovery
2. In the file manager, go to /persist/data/
3. Delete all the files named finger_0_x and finger_0_x.bak (finger_0_1, finger_0_1.bak,...)
4. Reboot and try again.
If it still doesn't work, flash the attachment zip in recovery.
This works wonders!!!
EDIT: Please notice that I am not the owner of the file!
Click to expand...
Click to collapse
I've tried this method in the past when downgrading from GSI or Android 10 to Android 9 and it doesn't work (the above mentioned files are not present). What I do is flash Oreo OEM rom via EDL in MiFlash, then reboot to bootloader and flash the Oreo "persist.img". Then I flash Android 9 OEM rom via EDL in MiFlash (without flashing the Android 9 "persist.img"). This method always works for me.
go to file manager in twrp.
navigate to /data/system
1. delete the file locksettings.db
navigate to /data/system/user/0
1. delete everything inside the folder fpdata
2. delete settings_fingerprint.xml
now you can install persist fix zip.
This will remove any pattern lock/pin lock/password/fingerprint. leaving a slide lock when you boot.
did ANYONE actually manage to install persist fix from the first post in this thread WITHOUT losing data or having to have to factory reset?! thanks