Database Users

MOTOACTV ROMs

Rooting and updating your MotoActv is about to get significantly easier! No more waiting games for developers to update their ROMs or tools when Motorola pushes a new OTA; now you can do it yourself! I honestly have not seen these types of files ANYWHERE else, so I had to create these myself (with quite a bit of help from [mbm]). But enough blabbing, here are the files and how to use them:
(Note: all these methods assume we have full fastboot access! -- Which we still have at this point)
- Stock Images:
These are not just mere update.zips that you might be accustomed to elsewhere in Android. Nor are these mere fxzs that you might be accustomed to elsewhere with newer Motorola devices. They are in fact both and more. There are 3 main ways to flash these files onto your device, giving you options based on what OS you run and how comfortable you are flashing files to your device.
1) FXZ:
- Operating System: Windows
- Requires: RSD Lite with FXZ Support
- Instructions: Simply load up the file as any standard fxz (it is very straight-forward)
2) Recovery:
- Operating System: Anything that can mount your device
- Requires: The ability to get into recovery
- Instructions: Place the file on the sdcard, boot into recovery, flash as normal
- Note: Recovery does not wipe your device, it is suggested that you do so before flashing stock images
3) Fastboot:
- Operating System: Windows/Linux/Mac
- Instructions (Windows): Unpack the zip, run flash-all.bat (if it fails, run as administrator)
- Instructions (Linux/Mac): Unpack the zip, run flash-all.sh (it should already have proper permissions)
Miscellaneous Images:
These miscellaneous images are nothing you haven't seen before at this point, but their purposes are new, so they too require explanation.
1) AnyRoot:
AnyRoot is based on koush's AnyKernel in the sense that it unpacks and repacks the boot.img on the fly. However, as the name suggests, AnyKernel is meant for kernels, while AnyRoot, actually roots the device on the fly. This will work on any MotoActv device. It is flashed as a normal update.zip and everything is done in the background so you won't noticed much. However, for ease of access, the stock and rooted boot.img is exported to your sdcard in /sdcard/recovery/. Also note, that if you happen to flash AnyRoot over an already rooted device, nothing will happen as it has built-in error checking.
2) rebootRecovery:
rebootRecovery is another fxz type zip, the same as the stock and rooted images, except it can't be flashed in recovery (would be a little redundant don't you think?). This flashes a specially made misc.img by [mbm] that tells the device to reboot into recovery from boot. This means you can flash AnyRoot on any stock device.
How Tos / FAQs:
Now that you know what the files do, I can explain in short steps how to use these files to get what you want:
1) How to Return the Device to Stock?
- flash a stock image using any of the 3 methods
- you can now update via Motocast if you so wish
2) How to Root a Stock Device?
- update your device via Motocast to the latest version (suggested)
- place AnyRoot on your sdcard
- boot into fastboot, and flash rebootRecovery using either of the 2 methods
- flash AnyRoot in recovery
- reboot
3) How do I update my Rooted Device?
- flash a stock image using any of the 3 methods
- update your device via Motocast to the latest version
- place AnyRoot on your sdcard
- boot into fastboot, and flash rebootRecovery using either of the 2 methods
- flash AnyRoot in recovery
- reboot
Q: After using rebootRecovery I can't get out of recovery!?
A: You are using an old recovery that doesn't clear the 'reboot-recovery' command; use the newer recovery: https://dl.dropbox.com/u/5849675/android/f100/CWMR5x_F100_recoveryB2.img
Q: What do these ROM offer over other custom ROMs?
A: Nothing, they are simply stock images, but you can upgrade with them.
Q: How much battery should I have when I flash?
A: Performing any kind of these flashes will drain at least 10% of your battery, I wouldn't suggest you flash below 60% ESPECIALLY IF YOU FLASH rebootRecovery!
Q: What happens if I flash a 16gb zip on my 8gb or visa-versa?
A: Don't freak, it will still boot, but it's not the best thing in the world to do, just go back and flash the correct model zip.
Q: Can I extract the images from your zips and flash them my own way?
A: yep (couldn't really think of anything else to say)
Q: I manually flashed the stock-boot.img from AnyRoot, and now I can't update. Why?!
A: The boot.imgs need to be truncated before they can be flashed to correctly work with Motorola's updates, just use the stock images.
Q: What's next?
A: HyprActv -- What's this?
Stock Images (w/ md5sums):
8gb-NA: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_8GB_NA.zip (5e228bf56a67aced012c8cbb2d7f7c76)
16gb-NA: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_16GB_NA.zip (21b067dc629f7ccd18b43799d8d5fb17)
8gb-EU: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_8GB_EU.zip (5b79a46d87728303fc2c920eec71c2e8)
Miscellaneous Images (w/ md5sums:
AnyRoot: https://dl.dropbox.com/u/5849675/android/f100/MA_AnyRoot.zip (2f867b006da42865ef861094db0eb6e6)
Reboot Recovery: https://dl.dropbox.com/u/5849675/android/f100/MA_RebootRecovery.zip (1623c9c61462db9bb20b55bc8f1144aa)
Mirror (thanks Iownox!): http://www.androtransfer.com/?developer=lownox&folder=MotoACTV

This is Reserved.

I rooted and flashed in recovery (the stock 4.55.97 and the the rooted version 4.55.97) and I stay on 4.55.78 no matter what! The flashes go through successfully... But nothing has changed and the System version still says 4.55.78... But like I said, the flashes both completed! I did a factory reset... and the updater-script wipes system, so what could be my issue?

Moose8106 said:
I rooted and flashed in recovery (the stock 4.55.97 and the the rooted version 4.55.97) and I stay on 4.55.78 no matter what! The flashes go through successfully... But nothing has changed and the System version still says 4.55.78... But like I said, the flashes both completed! I did a factory reset... and the updater-script wipes system, so what could be my issue?
Click to expand...
Click to collapse
It sounds like you flashed that old boot.img. Do you have the battery percentage in the status bar? According to TheEndGame7 that is another surefire way to tell if you are on 4.55.97, if you used any of the root tools, it's possible that they automatically flash the old boot.img.

CEnnis91 said:
It sounds like you flashed that old boot.img. Do you have the battery percentage in the status bar? According to TheEndGame7 that is another surefire way to tell if you are on 4.55.97, if you used any of the root tools, it's possible that they automatically flash the old boot.img.
Click to expand...
Click to collapse
I think I did flash the old boot.img (root tools :O ). I'll try flashing the modified boot img again. Thanks! I had no idea the root tool took me back to the old boot img

Moose8106 said:
I think I did flash the old boot.img (root tools :O ). I'll try flashing the modified boot img again. Thanks! I had no idea the root tool took me back to the old boot img
Click to expand...
Click to collapse
Yes, any and all tools that exist so far will need to be updated.

I wiped data / cache and used recovery (b) to install the rooted-4.55.97 zip and didn't have any luck either. I did not use the root tools to flash. Also wiped dalvik cache after and fastboot -w for fun.

innovatelife said:
I wiped data / cache and used recovery (b) to install the rooted-4.55.97 zip and didn't have any luck either. I did not use the root tools to flash. Also wiped dalvik cache after and fastboot -w for fun.
Click to expand...
Click to collapse
Did you end up doing any restore of some kind after you flashed?

Update
There are "new" instructions that might fix the issue where the rooted 4.55.97 appears to not flash. Simply wipe the boot.img image before you flash. And don't use the root tools until they are updated.
Also, if you have success, please post it. Usually "Thanks, it works" is annoying, but in this case where I don't have the device, I need to make sure this is working on some level.

I formated everything from recovery, now I got stuck with Moto logo with no animation when it starts, how to get out of this?
NA

Is there any mirrors for the download of these roms? the dropbox links are down

NORCALkID said:
Is there any mirrors for the download of these roms? the dropbox links are down
Click to expand...
Click to collapse
They were pulled, they're not working. There has been some form of mis-communication when I did my testing. I am not working on these until I can get the device from utkanos. Check Update 2, in the initial post.

Success
CEnnis91
I was lucky the second time, first time I succeeded to upgrade to rooted 4.55.97 but for some reason I didn't get the battery percentage on the status bar but all other issues are OK and status indicated version number 4.55.97, I repeated flash from recovery but after wiping and remounting all folders, this time for stock 4.55.97
Now I'm on stock 4.55.97 with battery percent on status bar and syncing from my mac.
thanks CEnnis91
NA

I went into recovery>mounts, and didn't see any wipe for boot. I took a shot at system since I had already wiped cache and data. Didn't seem to help either. Tried 'fastboot erase boot" and re-flashed. No go. Couldn't start back up the device at all. Tried flashing the latest rooted image using "fastboot flash boot boot.img". No go.
I messed around trying to get the device to boot back up for a while, but it won't even charge right. Only charges long enough to kick off the Motorola 'M', and that is it. On attempts at loading fastboot, I just keep getting an error saying that the battery is low. I know I can only blame myself for this. No fastboot access and no adb access. All attempts at resetting the device have failed.
Before I attempted all of this, my battery was full. Unfortunately, wouldn't charge anymore even plugged into the wall. Any ideas?
Hopefully nobody else makes my mistake.

Man I can't wait till this is perfect, you guys are fricken awesome. I raped your thanks buttons op lol
MoPhoACTV Initiative

Will be working on this tonight. I just found out how to make the flash script clear cache and dalvik for you, pre-install. That'll probably save some headache, but it works only in edify format. Not sure what the stock recovery uses...
Anyways, I'm home!

ClearD said:
Will be working on this tonight. I just found out how to make the flash script clear cache and dalvik for you, pre-install. That'll probably save some headache, but it works only in edify format. Not sure what the stock recovery uses...
Anyways, I'm home!
Click to expand...
Click to collapse
All recoveries will now use edify, amend is old and depreciated, you will only find that on old devices.

Corrupt Kernel...
innovatelife said:
I went into recovery>mounts, and didn't see any wipe for boot. I took a shot at system since I had already wiped cache and data. Didn't seem to help either. Tried 'fastboot erase boot" and re-flashed. No go. Couldn't start back up the device at all. Tried flashing the latest rooted image using "fastboot flash boot boot.img". No go.
I messed around trying to get the device to boot back up for a while, but it won't even charge right. Only charges long enough to kick off the Motorola 'M', and that is it. On attempts at loading fastboot, I just keep getting an error saying that the battery is low. I know I can only blame myself for this. No fastboot access and no adb access. All attempts at resetting the device have failed.
Before I attempted all of this, my battery was full. Unfortunately, wouldn't charge anymore even plugged into the wall. Any ideas?
Hopefully nobody else makes my mistake.
Click to expand...
Click to collapse
This is a classical case of a corrupt Kernel. Not that the images are corrupt, but somewhere along your update, your boot.img did not install the kernel properly and now you have a broken power manager within kernel.
What I would do is the following:
Hook your watch to the charger and let the M sign show up.
Even if it hangs on the M, leave your watch hooked over night.
Try downloading an older image and use fastboot to erase everything and then flash everything back again. This should return your watch to a working state again.
You may then choose to customize it as you see fit.

Root tool > "return to stock"
Sent from my HTC Inspire 4G using XDA-funded carrier pigeons

simx said:
CEnnis91
I was lucky the second time, first time I succeeded to upgrade to rooted 4.55.97 but for some reason I didn't get the battery percentage on the status bar but all other issues are OK and status indicated version number 4.55.97, I repeated flash from recovery but after wiping and remounting all folders, this time for stock 4.55.97
Now I'm on stock 4.55.97 with battery percent on status bar and syncing from my mac.
thanks CEnnis91
NA
Click to expand...
Click to collapse
I'm about to try this.. but it's making me think... Do you think the updater-script doesn't correctly format system? Think about it... our devices say 4.55.97 (mine changed to that after a reboot or two), and we only had partial features... sounds like something isn't wiping correctly.

Flash any kernel or modem on CWM

- I made some ZIPs with scripts for you to flash any kernel or modem on CWM.
- It's simple, just drag and drop your file to the correct ZIP.
#Put zImage on the "Flash Kernel [zImage]"
#Put boot.img on the "Flash Kernel [boot.img]"
#Put modem.bin on the "Flash Modem [modem.bin]"
1. Extract the ZIPs from the 7z file first.
2. Just open your ROM file [Cyanogenmod {Also other AOSP, AOKP, etc...}, Samsung Stock, Samsung-based], extract the file, and drag and drop to the ZIP, then you install on CWM Recovery, very simple,
Download

in the meta-in folder, there are some cert files and stuff, do i need to move them in as well?

Good work Marcello
Enviado do GalaxyS2 usando Tapatalk 2.1.3

LogeshMenon said:
in the meta-in folder, there are some cert files and stuff, do i need to move them in as well?
Click to expand...
Click to collapse
There are just binary and script, no need for certs. Just drag and drop or extract and compress the file you want to flash,

Re: boot.img -- have you never had problems with wifi using just the boot.img? Especially across firmwares such as AOSP <-> Samsung?
I always thought you also had to flash dhd.ko, among other modules. The advice here is what I have been following: http://forum.xda-developers.com/showthread.php?t=1059412

stone_ship said:
Re: boot.img -- have you never had problems with wifi using just the boot.img? Especially across firmwares such as AOSP <-> Samsung?
I always thought you also had to flash dhd.ko, among other modules. The advice here is what I have been following: http://forum.xda-developers.com/showthread.php?t=1059412
Click to expand...
Click to collapse
No. Never had any problems. And maybe those libs are already inclued in the ROM, don't know. And all I know is that boot.img = zImage. I've seen a thread saying that you can rename boot.img to zImage.

Unfortunately this didn't work for me - the first time.
I ended up stuck on the boot screen - ie samsung galaxy siii logo appears, no boot animation to imply it's starting up
I tried restore from a CWM backup but there was a checksum mismatch (scrath that idea)
I thought i'd give it one last try.
I flashed your flash modem.zip first, then reflashed my ROM (Ripper ROM v7) with no data wipe, and it WORKED!
I'm pretty happy now because for a while there I thought I had bricked my device!
Now i just have to install a few more zips as addons to my ROM and i'm back in business. (just installed those, restarting now)
*edit* restarted, mods working ok, 4G/LTE connected, everything is good again
Just realized this thread was for the SGS2 whereas I have a i9305 SGS3 4G/LTE. Whoops. Well it worked, but in my case i had to reflash the ROM.
I think I have done it right, but my baseband version in About Phone still shows I9305ZHALI2 (it should read I9305TDVLI5)? The ROM i reflashed does not come with a radio, it uses the one already on your device.

jjcoolaus said:
Unfortunately this didn't work for me - the first time.
I ended up stuck on the boot screen - ie samsung galaxy siii logo appears, no boot animation to imply it's starting up
I tried restore from a CWM backup but there was a checksum mismatch (scrath that idea)
I thought i'd give it one last try.
I flashed your flash modem.zip first, then reflashed my ROM (Ripper ROM v7) with no data wipe, and it WORKED!
I'm pretty happy now because for a while there I thought I had bricked my device!
Now i just have to install a few more zips as addons to my ROM and i'm back in business. (just installed those, restarting now)
*edit* restarted, mods working ok, 4G/LTE connected, everything is good again
Just realized this thread was for the SGS2 whereas I have a i9305 SGS3 4G/LTE. Whoops. Well it worked, but in my case i had to reflash the ROM.
I think I have done it right, but my baseband version in About Phone still shows I9305ZHALI2 (it should read I9305TDVLI5)? The ROM i reflashed does not come with a radio, it uses the one already on your device.
Click to expand...
Click to collapse
This is very old. If you tried on your S3 lte, of course it won't work. Be more careful next time,
Sent from my GT-I9300 using xda premium

[RECOVERY][KANG] TWRP 3.0.2 recovery for u8800pro/u8860

Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOGS
Changelogs can be found from TeamWin site TeamWin - TWRP
BUGS:
- No off mode charging, boots straight in to recovery.
INFORMATION:
- Supports the f2fs file system.
2016-05-10
- TWRP version 3.0.2-0
2016-02-06
- TWRP version 3.0.0-1
2015-12-10
- TWRP version 2.8.7.0
2014-10-26
- TWRP version 2.8.1.0
2014-10-15
Today (2014-10-15) I announce a build with F2FS support, today's and upcoming build's will have support for F2FS file system. Read more about F2FS from post #18.
DOWNLOAD:
For u8800pro
Stable:
TWRP_2.8.1.0-20141026-u8800pro.zip
Unstable:
TWRP_3.0.2-0-u8800pro.zip
TWRP_3.0.0-1-u8800pro.zip
TWRP_2.8.7.0-20151210-u8800pro.zip
For u8860
TWRP_2.8.1.0-20141026-u8860.zip
Looking for the u8800 version?
It can be found here: [RECOVERY] TWRP 2.8.1.0 recovery for u8800.
Big thanks to @Dees_Troy, @bigbiff and @Captain_Throwback. Also I want to thank you @desalesouche from his help.

Thanks Lihis and everyone else, I'm glad you are still supporting this device Thumbs up!

CrysisLTU said:
Thanks Lihis and everyone else, I'm glad you are still supporting this device Thumbs up!
Click to expand...
Click to collapse
Thanks and thanks to you and other dev's who was part of this forum, you have made a job which can't be forgotten!

Great. This must be a record. Not so famous device, still getting superb support from devs. Lets see what happens to Android L.

It seems that I must be doing something wrong.
I am using TWRP manager to install the recovery img
choose the downloaded img from the SD card
but when I try to install I get a WARNING that says
1><p> The requested URL /install_command/ was not found on this server. </p>
any idea what I am doing wrong.
obviously rebooting into recovery mode does not work

Greekguy74 said:
It seems that I must be doing something wrong.
I am using TWRP manager to install the recovery img
choose the downloaded img from the SD card
but when I try to install I get a WARNING that says
1><p> The requested URL /install_command/ was not found on this server. </p>
any idea what I am doing wrong.
obviously rebooting into recovery mode does not work
Click to expand...
Click to collapse
I have not never used TWRP manager so I do not have experience with it. I suggest you to use pink screen to replace the recovery.

Lihis said:
I have not never used TWRP manager so I do not have experience with it. I suggest you to use pink screen to replace the recovery.
Click to expand...
Click to collapse
I have access to the pink screen, but it seems it is locked and don't have access to the internal storage.
I suppose I need some custom bootloader for that. Any ideas which is appropriate for the B928 version I am using from Huwaie ?
and once I get access to the internal storage where do I place the new recovery image ?
thanks in advance for all the help.

Greekguy74 said:
I have access to the pink screen, but it seems it is locked and don't have access to the internal storage.
I suppose I need some custom bootloader for that. Any ideas which is appropriate for the B928 version I am using from Huwaie ?
and once I get access to the internal storage where do I place the new recovery image ?
thanks in advance for all the help.
Click to expand...
Click to collapse
Yes, you need unlocked bootloader, take a look in here: Official ICS 4.0.3 V100R001C00B928 with unlock pink screen. When you boot your phone to pink screen the recovery can be found from "image" folder.

Lihis said:
Yes, you need unlocked bootloader, take a look in here: Official ICS 4.0.3 V100R001C00B928 with unlock pink screen. When you boot your phone to pink screen the recovery can be found from "image" folder.
Click to expand...
Click to collapse
I tried those instructions and they don't seem to work.
If I attempt it from the normal recovery screen I get a
Code:
update package;s ext name error
E:ota_pre_update error
Maybe will try to flash everything ie reinstall B928 as well and not just try to unlock the pink screen.
Will keep you posted.

Greekguy74 said:
I tried those instructions and they don't seem to work.
Click to expand...
Click to collapse
What is the error? No, you cannot flash the update.app via recovery.

Lihis said:
What is the error? No, you cannot flash the update.app via recovery.
Click to expand...
Click to collapse
If I try to flash outside the recovery it fails and in dload directory the sd_update.log says
Code:
dload_sd_ram_data_proc->(retry >= DLOAD_RETRY) failed!
I formattted the SD card but that was not the problem.
Interestingly enough if I try to flash with the official Huawei ROMs same thing happens. I am bit at a loss

Greekguy74 said:
If I try to flash outside the recovery it fails and in dload directory the sd_update.log says
Code:
dload_sd_ram_data_proc->(retry >= DLOAD_RETRY) failed!
I formattted the SD card but that was not the problem.
Interestingly enough if I try to flash with the official Huawei ROMs same thing happens. I am bit at a loss
Click to expand...
Click to collapse
In that case unfortunately I can't help you much but you can't flash update.app via recovery, they must be applied via "force update" method which is that dload thing or via stock rom "update" option. You don't have a recovery or a OS now? One thing you can test is to take off the battery and power your phone with USB cable only to apply the update.app, I have heard it helped someone's.
btw, why you didn't unlocked your pink screen in the first place when you upgraded to ICS?

Lihis said:
In that case unfortunately I can't help you much but you can't flash update.app via recovery, they must be applied via "force update" method which is that dload thing or via stock rom "update" option. You don't have a recovery or a OS now? One thing you can test is to take off the battery and power your phone with USB cable only to apply the update.app, I have heard it helped someone's.
btw, why you didn't unlocked your pink screen in the first place when you upgraded to ICS?
Click to expand...
Click to collapse
At the moment my phone works fine with the stock 4.0.3 official android version from Huawei after I managed to replace the bootloader.
I tried without the battery and just the USB cable still no joy.
As for the why I did not unlock it, good question. At the time cyanogenmod was behind ver 4.0.3 for my phone so decided to stick with the official ROM and then to be frank I forgot about it.
I will contact the TWRP manager devs to see if they can fix their app so it applies TWRP without the need for going through the pink screen.

Greekguy74 said:
At the moment my phone works fine with the stock 4.0.3 official android version from Huawei after I managed to replace the bootloader.
I tried without the battery and just the USB cable still no joy.
As for the why I did not unlock it, good question. At the time cyanogenmod was behind ver 4.0.3 for my phone so decided to stick with the official ROM and then to be frank I forgot about it.
I will contact the TWRP manager devs to see if they can fix their app so it applies TWRP without the need for going through the pink screen.
Click to expand...
Click to collapse
Good! Try eg. with RootExplorer to replace the recovery.img. It can be found from /.cust_backup/image

Lihis said:
Good! Try eg. with RootExplorer to replace the recovery.img. It can be found from /.cust_backup/image
Click to expand...
Click to collapse
I did just that and now the phone is in even bigger trouble.
When I boot it it says
Code:
Image signature verify fail!
Your boot/recovery image may have an incorrect signature.
Please update your image to a signature official one.
You can remove battery for power down.
USB in pink screen mode is not functioning and it seems I cannot flash with any of the official ROMs (which is VERY weird since I did update the phone to 4.0.3 at some point in the past).
:crying:

Greekguy74 said:
I did just that and now the phone is in even bigger trouble.
When I boot it it says
Code:
Image signature verify fail!
Your boot/recovery image may have an incorrect signature.
Please update your image to a signature official one.
You can remove battery for power down.
USB in pink screen mode is not functioning and it seems I cannot flash with any of the official ROMs (which is VERY weird since I did update the phone to 4.0.3 at some point in the past).
:crying:
Click to expand...
Click to collapse
Ouch.. This is hard situation :/ sometimes I really hate Huawei.. Adb is not accessible in any point? So you can't push files to device?

Lihis said:
Ouch.. This is hard situation :/ sometimes I really hate Huawei.. Adb is not accessible in any point? So you can't push files to device?
Click to expand...
Click to collapse
adb is not accessible but fastboot seems that it is. even though I cannot flash anything since they are locked.

Support for F2FS file system
Added support for F2FS file system.
What is F2FS file system?
F2FS (Flash-Friendly File System) file system is a flash file system initially developed by Samsung Electronics for the Linux operating system kernel (source). Here is some benchmark made with Xperia Z1 [Benchmarks] File System Performance: F2FS vs EXT4.
For now there is no ROM which uses F2FS file system but in future there may be.

Lihis said:
Added support for F2FS file system.
What is F2FS file system?
F2FS (Flash-Friendly File System) file system is a flash file system initially developed by Samsung Electronics for the Linux operating system kernel (source). Here is some benchmark made with Xperia Z1 [Benchmarks] File System Performance: F2FS vs EXT4.
For now there is no ROM which uses F2FS file system but in future there may be.
Click to expand...
Click to collapse
Found one bug with f2fs its fail in restore f2fs system backup data and cache are ok.
If you need you need f2fs backup just backup your current rom
Then rename and replace every "ext4" with f2fs.

mohammad.afaneh said:
Found one bug with f2fs its fail in restore f2fs system backup data and cache are ok.
If you need you need f2fs backup just backup your current rom
Then rename and replace every "ext4" with f2fs.
Click to expand...
Click to collapse
Thanks! Are you working a F2FS enabled rom?

[Q] Bootanimation Help

Ok so I wanted to install one of these bootanimations from here http://forum.xda-developers.com/showthread.php?t=2334927
I installed one that is 1080x1920 but it doesn't flash. In Philz recovery it says aborted. So then I went as far as trying to create my own from awesome gifs I found around the web using Boot Animation Factory.
I tried 480x800, 720x1280, 800x1280, and 1080x1920. I am still getting the same result. Nothing. Yes I am naming them bootanimation. If anyone could let me know what I'm missing I would appreciate it. If someone helps me I have some cool boot animations for the Galaxy S4 that I will share. I'm on Sac's ROM if that makes a difference.
Edit: I notice Touchwiz boot animations are different since there is no bootanimation.zip I tried to install the S5 boot animation for the Galaxy S4 and only the audio worked. I'm on Sac's ROM
Edit: Ok so I figured it out. You need to flash this zip called Bootanimation4U.Samsungani.Only.zip and then you are able to place the bootanimation in the system/media folder and you'll have a custom boot animation

Rooted Samsung s4 custom boot animation won't work?

Hello guys, I need help trying to get my boot animation that I downloaded to work. I rooted my device with kingroot and it works perfectly that my device is rooted correctly. I used the root browser and boot animations app by Jrummy or something like that then I grabbed a watchdogs bootanimation on the net named bootanimation.zip, it is has two parts and has the resolution of my s4 at&t i337. I installed the zip to data/local (didn't work) I checked the permission status and made sure they read rw-r-r. Then I installed it to system/media and that still didn't work. I realized that the boot animations were not being overwritten so I tried to rename the boot animation.zip to bootsamsung.qmg to replace the stock manafactuar boot animation and no luck. I searched everywhere on the Internet for a answer and they provided the same one that didn't work. If you guys want screenshots or the zip I can try to post it. But I would appreciate some help ASAP.

Have you tried deleting the original boot animation zip, leaving only the custom one?
This should not cause any serious problems.
The worst thing that can happen is that you will have a black screen (because the boot animation was deleted) during the boot process.

Stock firmware doesn't support .zip bootanimation. You need to convert manually the bootanimation into .qmg.
Sent from my ASUS_Z00A using XDA Labs