I had downloaded a version of this file from a post embedded deep inside one of the threads over here (sorry can't find it right now), but upon examination of its contents, I discovered some issues:
1. The checksums on the files in contained in the the original zip file showed that B&N had at least two versions of 1.3.0 update you can download from them, and the zip I got contained an older version so I put in the latest files in there.
2. There were unnecessary files included inside the original zip file, I deleted those, and only included what was needed.
3. There were errors in the script syntax, which I corrected, so that the proper commands are run during the update, and the proper sed substitutions are made during the editing of the unpacked init.rc inside the ramdisk.
What this zip will do is replace any older version of a B&N ROM on the alternate eMMC partitions of a dual booting configurations to the latest versions. This will prevent B&N from pushing the 1.3.0 update to you OTA, and messing up your dual boot setup. Just put the zip on your sdcard, boot into CWM recovery, and apply the zip. I apologize in advance for not giving credit to the original creators of the scripts here.
Note: There have been two different protocols for a dual booting u-boot.bin, with an older one relying on the files u-boot.altimg, and u-boot.altram to specify the names of the secondary boot ramdisk and kernel, and a newer one assuming that they are named uAltRam, and uAltImg respectively. This update conforms to the new u-boot.bin protocol. If you are still using the old one, you will have to get root access to /boot and edit the two files to point to uAltRam and uAltImg.
So if you want try it out, here it is:
http://www.mediafire.com/?gcrpzzc0kdoxcjx
MD5 Sum: 51e24c1e5eff11ba5ea481a63f7404eb
Update
I have now uploaded files for B&N Update 1.4.1.
The first file (MD5 Sum: 4ff1d9764663278c3f51e2e2c9d841a6) is meant to update a pre 1.4.1 Stock B&N ROM on secondary /system through CWM:
https://rapidshare.com/files/52135913/secondary_update_NC_stock_1_4_1.zip
The second file (MD5 Sum: c1506816fbfb8c419fbbc4afe1b12887) is meant to update a pre 1.4.1 Stock B&N ROM on primary /system through CWM without messing with recovery;
https://rapidshare.com/files/869435270/primary_update_NC_stock_1_4_1_keep_CWM.zip
The third file (MD5 Sum: ab1307c55a2c35c91d339c8037ce9a78) is meant to update a pre 1.4.1 Stock B&N ROM on primary /system through CWM, replacing recovery and all:
https://rapidshare.com/files/2059644016/primary_update_NC_stock_1_4_1.zip
None of these files will wipe user apps and data, so if you wish to do that, boot into recovery and wipe from there. [This will work on primary /data partition only]
Please note: If the B&N Stock ROM is rooted, you will lose root upon updating.
Thanks!
This worked beautifully! I flashed it from my sdcard after booting into CWM on my primary partition on emmc.
I'm betting you got the original from jasoraso in this dual boot thread: http://forum.xda-developers.com/showpost.php?p=17122342&postcount=142
What I would love is a straight CWM-flashable 1.3 ROM, to include in my up-to-date (for now) guide for setting up the dual boot, rather than having to set up and move 1.2, then update to 1.3.
That is possible to do by combining three of the steps. You need commands from the scripts from the prepare dual boot zip to resize /media and create the secondary system and data partitions, then the part of the script from the file that copies the contents of /data from primary to secondary and replaces u-boot.bin , and then my file which formats secondary /system and puts 1.3.0 there, and copies the latest kernel and patched ramdisk onto /boot. I can put such a file together, but I wouldn't be able to test it. The Nook belongs to my wife, and and you get the rest of the drift.
PS - You can use my file as is after running prepare dual boot and copy stock to secondary. It is not necessary to update secondary to 1.2 before going to 1.3.
Sent from my SAMSUNG-SGH-I897 using XDA App
rajendra82 said:
That is possible to do by combining three of the steps. You need commands from the scripts from the prepare dual boot zip to resize /media and create the secondary system and data partitions, then the part of the script from the file that copies the contents of /data from primary to secondary and replaces u-boot.bin , and then my file which formats secondary /system and puts 1.3.0 there, and copies the latest kernel and patched ramdisk onto /boot. I can put such a file together, but I wouldn't be able to test it. The Nook belongs to my wife, and and you get the rest of the drift.
Click to expand...
Click to collapse
Wait...what? What I'm talking about is a 1.3 zip made to work with CWM and in no way doctored to account for dual booting, just like the 1.2 zip one would otherwise use.
rajendra82 said:
PS - You can use my file as is after running prepare dual boot and copy stock to secondary. It is not necessary to update secondary to 1.2 before going to 1.3.
Click to expand...
Click to collapse
Have you tested this theory? I found that when I did not register my B&N install while it was on the primary partition, I was unable to boot into it on the secondary partition.
Taosaur said:
Wait...what? What I'm talking about is a 1.3 zip made to work with CWM and in no way doctored to account for dual booting, just like the 1.2 zip one would otherwise use.
Click to expand...
Click to collapse
Are you talking about updating an already rooted 1.0/1.1/1.2 Nook Color. I am sure the scripting to do that is exactly the same as what is in the 1.2 zip file. Just replace the 1.2 files inside the zip with the equivalent files from the 1.3 update. Make sure the portions which install su and busybox are included, and build.prop spoofig is applied. I am not sure it is worth it building such a zip file though. One is better off just applying the B&N update, and then rerooting with manual nooter. What I created was for people that have already doctored the setup for dual booting. In such a case, the B&N update would either fail, or would replace the primary partition instead.
Taosaur said:
Have you tested this theory? I found that when I did not register my B&N install while it was on the primary partition, I was unable to boot into it on the secondary partition.
Click to expand...
Click to collapse
No way to get around having to register the primary partition image first. Once that is done it could be moved to secondary and then updated straight to 1.3 instead of going 1.2 first.
I have a dual boot eMMC NC. I am not sure which setup I use but the last time I updated the CM7 nightly, I lost the dual boot until I installed the u-Boot again. I suspect I have the setup that looks for altFImg. So this is not going to work for me. I have 1.2 rooted which I use only occasionally. I am not even sure what is in 1.3 but I am curious.
yelloguy said:
I have a dual boot eMMC NC. I am not sure which setup I use but the last time I updated the CM7 nightly, I lost the dual boot until I installed the u-Boot again. I suspect I have the setup that looks for altFImg. So this is not going to work for me. I have 1.2 rooted which I use only occasionally. I am not even sure what is in 1.3 but I am curious.
Click to expand...
Click to collapse
All you need to do is boot into CM7, mount /boot as root, and then rename uFImg to uAltImg, uFRam to uAltRam, and then change the text inside u-boot.altimg and u-boot.altram to point to the new names instead of the old ones. This will keep you dual booting under the old u-boot.bin, and even after a new protocol u-boot.bin (like that installed by CM7) gets pushed to your Nook Color. Once you have done that, you can update the secondary to 1.3 using my zip file if you want.
rajendra82 said:
Are you talking about updating an already rooted 1.0/1.1/1.2 Nook Color. I am sure the scripting to do that is exactly the same as what is in the 1.2 zip file. Just replace the 1.2 files inside the zip with the equivalent files from the 1.3 update. Make sure the portions which install su and busybox are included, and build.prop spoofig is applied. I am not sure it is worth it building such a zip file though. One is better off just applying the B&N update, and then rerooting with manual nooter. What I created was for people that have already doctored the setup for dual booting. In such a case, the B&N update would either fail, or would replace the primary partition instead.
Click to expand...
Click to collapse
I wouldn't know what to change and what to leave alone, myself, but I think you're making this more complicated than it needs to be. I'm talking about installing 1.3 using CWM, regardless of how the device is partitioned or what was on the primary partition previously. Like the files in this thread, but 1.3: http://forum.xda-developers.com/showthread.php?t=1050520.
I understand that you were just cleaning up jaso's update-dualboot-to-1.3 file. I used the original and it worked fine, but it would have saved me a couple steps (and would be more useful in a guide for setting up dualboot) to simply install 1.3 rather than 1.2 to the primary partition when setting up. The reason I started with 1.2 is because it is the most current stock ROM available for CWM. What I would like is to avoid a historical re-enactment of stock OS development altogether. A general-purpose, CWM-flashable 1.3 ROM would be broadly useful, but is so far lacking as far as I've seen.
1. Do you envision this to be an uprooted stock 1.3 update ROM (either as primary or the only boot option) ? I just don't see the need for this to be CWM flashable. It is very easy to get there by resetting the device to stock, and then updating the device to 1.3.0 using the B&N file, and restoring dual boot as need be. If one has any older stock ROM running on primary, the B&N update will get them to 1.3 while losing root. There is no need to apply 1.2 update first.
2. Do you envision this to be for already rooted single or primary booting 1.1/1.2 users? There is once again no need to create any file for this. One can simply apply the B&N update, and then rerun manual nooter, and restore dual booting to the secondary.
3. The only users with no clear upgrade path are those who have already moved the B&N ROM to secondary. That's why I fixed up the zip file, and shared it. I am glad the original file worked for you despite the script errors. I can see other setups where it would have failed though.
I am not trying to make this more complicated than it needs to be. The Nook Color is just capable of being set up in so many ways, there isn't simply going to be a single update method that will work in all scenarios.
Sent from my SAMSUNG-SGH-I897 using XDA App
I'm envisioning it as a one step, starting-point-agnostic means of establishing a 1.3 stock install, whether for setting up a dualboot or for any other purpose. Its usefulness is made evident by the three-page thread devoted to CWM-flashable 1.2 images: http://forum.xda-developers.com/showthread.php?t=1050520
Taosaur said:
I'm envisioning it as a one step, starting-point-agnostic means of establishing a 1.3 stock install, whether for setting up a dualboot or for any other purpose. Its usefulness is made evident by the three-page thread devoted to CWM-flashable 1.2 images: http://forum.xda-developers.com/showthread.php?t=1050520
Click to expand...
Click to collapse
Then the best bet is two step process:
1. Wipe device and restore to factory stock.
2. Download B&N 1.3 update file from website and place it on the root of SD card. Let the device recognize it, and apply it.
Once the 1.3 update gets applied, you are free to reroot, install CWM, set up dual booting, or whatever the next step may be.
It is the only method that will work in all circumstance as it involves starting from scratch regardless of setup. If want to preserve any of your current setup, no one step file will work for all circumstances. Some people have the stock firmware rooted, others do not. Some have the stock as the only internal boot, others have it as primary option of a dual booting configuration, while others have it as a secondary option. Some have stock recovery and run CWM off the sdcard when needed and want to update their recovery to the latest stock version, others want to keep the CWM recovery, and not update the recovery. There simply is no way file to cope with all these options.
rajendra82 said:
All you need to do is boot into CM7, mount /boot as root, and then rename uFImg to uAltImg, uFRam to uAltRam, and then change the text inside u-boot.altimg and u-boot.altram to point to the new names instead of the old ones. This will keep you dual booting under the old u-boot.bin, and even after a new protocol u-boot.bin (like that installed by CM7) gets pushed to your Nook Color. Once you have done that, you can update the secondary to 1.3 using my zip file if you want.
Click to expand...
Click to collapse
You lost me at mount
Seriously, I am trying to see if what I have is compatible with your update before I apply the update. I have a couple of useful apps on my CM7 and I have lost the password. I don't want to be stuck without CM7 or start over again. I can live without the 1.3 update though. So I want to make sure I am up to the task of finding and renaming these files if I have to.
With that said, how do I mount the /boot partition? I go into terminal emulator and give the su command. Then I tried mount /boot but that didn't work.
Thanks for your help.
rajendra82 said:
1. Wipe device and restore to factory stock.
Click to expand...
Click to collapse
...the only means of doing so "that will work in all circumstance" and in any way resembles a single step is flashing a stock zip via CWM. Why not use an up-to-date zip? The usefulness of such files is demonstrated by the fact that:
such files exist for past stock versions
those files are in use
files like yours are used to work around the non-existence of up-to-date stock zips
If you're so comfortable working with update files, you very likely could have produced such a file in less time than you've spent rationalizing away the clearly demonstrated need for them. Tell you what, in all likelihood I can just swap a few files from B&N's 1.3 zip into the existing CWM-flashable 1.2 zips, correct? Which files do I replace?
Anyone?
---------- Post added at 02:15 PM ---------- Previous post was at 01:58 PM ----------
yelloguy said:
You lost me at mount
Seriously, I am trying to see if what I have is compatible with your update before I apply the update. I have a couple of useful apps on my CM7 and I have lost the password. I don't want to be stuck without CM7 or start over again. I can live without the 1.3 update though. So I want to make sure I am up to the task of finding and renaming these files if I have to.
With that said, how do I mount the /boot partition? I go into terminal emulator and give the su command. Then I tried mount /boot but that didn't work.
Thanks for your help.
Click to expand...
Click to collapse
I don't know for sure, but wouldn't rajendra's update create properly-named boot files alongside the old, improperly named ones? Wouldn't the multiboot built in to recent CM7 builds then look for and boot from the more recent, properly named files? I can't confirm that's how it would work, but it's what I would expect.
Taosaur said:
I don't know for sure, but wouldn't rajendra's update create properly-named boot files alongside the old, improperly named ones? Wouldn't the multiboot built in to recent CM7 builds then look for and boot from the more recent, properly named files? I can't confirm that's how it would work, but it's what I would expect.
Click to expand...
Click to collapse
Yes they would create properly named boot files. But I suspect my nook looks for improperly named files since I updated my u-boot after the CM7 nightly update.
The fix is simple: to rename the files. But I need to know how before I take the plunge.
yelloguy said:
Yes they would create properly named boot files. But I suspect my nook looks for improperly named files since I updated my u-boot after the CM7 nightly update.
Click to expand...
Click to collapse
Right, but if you run a CM7 update, it would replace your uboot again. I'm not saying do it, just wondering out loud if it would work.
yelloguy said:
Yes they would create properly named boot files. But I suspect my nook looks for improperly named files since I updated my u-boot after the CM7 nightly update.
The fix is simple: to rename the files. But I need to know how before I take the plunge.
Click to expand...
Click to collapse
In order to rename the files, you can do the following:
1. Boot into CM7 (or any other place where you have command line root access)
2. Create a temporary directory at a location where you have read write access.
3. Type su in a terminal session to gain root access and then mount mmcblk0p1 at the temporary location you created using the command:
mount /dev/block/mmcblk0p1 <full path to the directory you created>
4. Now use Astro to go over to the directory you created and mounted mmcblk0p1 into. You should see:
u-boot.bin which is the bootloader
u-boot.bin.stock which is the backup of the old stock bootloader
uImage and uRamdisk which are your primary kernel and ramdisk
uFImg and uFRam which are your secondary kernel and ramdisk (and whose names are mismatching the CM7 bootloader protocol)
u-boot.altimg and u-boot.altram, which are text files per the old bootloader method containing names of uFImg and uFRam
5. Rename uFImg to uAltImg, uFRam to uAltRam. And edit the contents of u-boot.altimg and u-boot.altram to match the new file names.
6. Reboot as usual into primary or secondary.
Now if an CM7 update ever replaces your u-boot.bin, you will not lose dual boot, as you have it set up as uAltImg and uAltRam per the new protocol.
Sent from my SAMSUNG-SGH-I897 using XDA App
---------- Post added at 03:24 PM ---------- Previous post was at 03:06 PM ----------
Taosaur said:
...the only means of doing so "that will work in all circumstance" and in any way resembles a single step is flashing a stock zip via CWM. Why not use an up-to-date zip? The usefulness of such files is demonstrated by the fact that:
such files exist for past stock versions
those files are in use
files like yours are used to work around the non-existence of up-to-date stock zips
If you're so comfortable working with update files, you very likely could have produced such a file in less time than you've spent rationalizing away the clearly demonstrated need for them. Tell you what, in all likelihood I can just swap a few files from B&N's 1.3 zip into the existing CWM-flashable 1.2 zips, correct? Which files do I replace?
Anyone?
Click to expand...
Click to collapse
I am sorry if you think I am rationalizing, but that was not my intention. I just wanted to point out that the files you linked to do not meet your own criteria.
Take for example the file update-nc-stock-1.2-keepcwm-signed.zip that you point to as missing in an up to date 1.3 version. That file will update a Nook Color to 1.2, but will keep CWM recovery. It however will make someone whose Nook Color 1.1 was rooted using autonooter lose root. A person that has been dualbooting to CM7 on secondary will lose that ability as well after applying that update. So unlike what you think, this is not a file to update stock 1.2 update under all circumstances regardless of what the starting point is. It has a specific use (update fro, a pre 1.2 stock primary eMMC boot, no dualboot, CWM recovery installed). Creation of an all situation stock restore file is impossible IMO, and the best you can do is wipe and apply 1.3 B&N stock update. You or I could technically create another equivalent file with update-nc-stock-1.3-keepcwm.zip /system files, kernel, ramdisk, etc., but this file would be subject to the same side effects as the original.
---------- Post added at 03:30 PM ---------- Previous post was at 03:24 PM ----------
Taosaur said:
Right, but if you run a CM7 update, it would replace your uboot again. I'm not saying do it, just wondering out loud if it would work.
Click to expand...
Click to collapse
It would work. If you apply my zip, there will be a uAltImg and uAltRam in /boot (in addition to uFImg and uFRam). If you apply another update that pushes the CM7 bootloader, it will then look for these files with trying to do an alternate boot, and would boot into a unrooted stock 1.3.
rajendra82 said:
In order to rename the files, you can do the following:
1. Boot into CM7 (or any other place where you have command line root access)
2. Create a temporary directory at a location where you have read write access.
3. Type su in a terminal session to gain root access and then mount mmcblk0 at the temporary location you created using the command:
mount /dev/block/mmcblk0 <full path to the directory you created>
Click to expand...
Click to collapse
I get an error:
mounting <paths> failed: Device or resource busy
Any ideas?
yelloguy said:
I get an error:
mounting <paths> failed: Device or resource busy
Any ideas?
Click to expand...
Click to collapse
I see a typo in my command (stupid Swiftkey X). It should be:
mount /dev/block/mmcblk0p1 <some directory>
Also try typing just mount in terminal to see if /dev/block/mmcblk0p1 is already mounted somewhere else.
rajendra82 said:
Take for example the file update-nc-stock-1.2-keepcwm-signed.zip that you point to as missing in an up to date 1.3 version. That file will update a Nook Color to 1.2, but will keep CWM recovery. It however will make someone whose Nook Color 1.1 was rooted using autonooter will lose root. A person that has been dualbooting to CM7 on secondary will lose that ability as well after applying that update. So unlike what you think, this is not a file to update stock 1.2 update under all circumstances regardless of what the starting point is. It has a specific use (update fro, a pre 1.2 stock primary eMMC boot, no dualboot, CWM recovery installed). Creation of an all situation stock restore file is impossible, and the best you can do is wipe and apply 1.3 B&N stock update. You or I could technically create another equivalent file with update-nc-stock-1.3-keepcwm.zip /system files, kernel, ramdisk, etc., but this file would be subject to the same side effects as the original.
Click to expand...
Click to collapse
Riiiiight... it would install stock 1.3 to the device. That's the intended behavior. The point is to avoid the unnecessary step of updating in any process that includes flashing stock to the sole or primary partition. One example of such a process would be a fresh dual boot setup. That it does not update or otherwise rely upon an existing install is the point.
Granted, such a file would not repartition the device, but it would install up-to-date stock in one step regardless of how a device is partitioned (1/5, 2/5, 5/1 or dual boot).
I see a lot of people are looking for a decent ROM for the Elephone P6i. This is the firmware that came with my device, plus a few slight modifications. The recovery included is the PhilZ touch Recovery CWM 6.0.5.1, and the SU binary is already installed, as well as busybox and SuperSU as a system app. I also installed fully customizable audio modifications, including XTREMEMusic, assembled by @androidexpert35 at xda, and Sony Atmos, which are both available for download here:
http://forum.xda-developers.com/android/software/mod-beatsaudio-e-xloud-installer-t3029951
I am also posting links to both the CWM-flashable zip and the CWM backup. You pretty much have to have a custom recovery already installed to flash this zip, unless you want to go through the trouble of extracting it, then converting it to SP Flash Tool files. I might upload the files for direct flashing myself depending on the amount of requests.
Update: SP Flash Tool files have been uploaded.
Files to download
------------------------------------------------------------------------------------------------------------
CWM Files:
CWM Flashable Nandroid ROM zip (Install downloaded zip file from custom recovery):
Link 1: https://www.dropbox.com/s/7eb8pvy4s0lhqus/Modified-Factory-Flashable.zip?dl=0
Link 2: https://mega.co.nz/#!oFd2RLoI!-CVCMlYdKnQyEoFw2277SY960f2ONaTjAe1dPEq3Pyg
CWM Nandroid Backup zip (Install by extracting the zip file to the clockworkmod\backup\ folder and choosing to restore from backup in CWM custom recovery):
Link 1: https://www.dropbox.com/s/ol7iru7hmjeq27q/Modified-Factory-Backup.zip?dl=0
Link 2: https://mega.co.nz/#!9IlBTRiJ!25hIaMjeP-mBscdeORF4tBx7h2g_fUbP6beAphEQF-U
------------------------------------------------------------------------------------------------------------
SP Flash Tool Files:
MTK Droid Tools Backup:
Link 1: https://www.dropbox.com/s/9mpqdmkmjiubdgs/Modified-Factory-FlashTool.zip?dl=0
Link 2: https://mega.nz/#!EUtgCSYR!NaQIrDNJBIN5zvEvfeU95Roc7YaPTamstDbKPKxfpF8
UserData and Cache (Required for the Format All + Download option)
Link 1: https://www.dropbox.com/s/8lpl1cfesgmoi9x/userdata+cache.zip?dl=0
Link 2: https://mega.nz/#!0FklTQpD!eLGXQDIhBfyKMfm5FOLrThJ0ah7VqKoeuOYue2pBBDA
Also, for those who are unaware, after a complete format and flash, you may need to change your IMEI numbers back to their original values. If you require assistance in doing this, let me know.
Let me know how it works for you!
TechManPro said:
I see a lot of people are looking for a decent ROM for the Elephone P6i. This is the firmware that came with my device, plus a few slight modifications. The recovery included is the PhilZ touch Recovery CWM 6.0.5.1, and the SU binary is already installed, as well as busybox and SuperSU as a system app. I also installed fully customizable audio modifications, including XTREMEMusic, assembled by @androidexpert35 at xda, and Sony Atmos, which are both available for download here:
http://forum.xda-developers.com/android/software/mod-beatsaudio-e-xloud-installer-t3029951
I am also posting links to both the CWM-flashable zip and the CWM backup. You pretty much have to have a custom recovery already installed to flash this zip, unless you want to go through the trouble of extracting it, then converting it to SP Flash Tool files. I might upload the files for direct flashing myself depending on the amount of requests.
Update: SP Flash Tool files have been uploaded.
Files to download
------------------------------------------------------------------------------------------------------------
CWM Files:
CWM Flashable Nandroid ROM zip (Install downloaded zip file from custom recovery):
Link 1: https://www.dropbox.com/s/7eb8pvy4s0lhqus/Modified-Factory-Flashable.zip?dl=0
Link 2: https://mega.co.nz/#!oFd2RLoI!-CVCMlYdKnQyEoFw2277SY960f2ONaTjAe1dPEq3Pyg
CWM Nandroid Backup zip (Install by extracting the zip file to the clockworkmod\backup\ folder and choosing to restore from backup in CWM custom recovery):
Link 1: https://www.dropbox.com/s/ol7iru7hmjeq27q/Modified-Factory-Backup.zip?dl=0
Link 2: https://mega.co.nz/#!9IlBTRiJ!25hIaMjeP-mBscdeORF4tBx7h2g_fUbP6beAphEQF-U
------------------------------------------------------------------------------------------------------------
SP Flash Tool Files:
MTK Droid Tools Backup:
Link 1: https://www.dropbox.com/s/9mpqdmkmjiubdgs/Modified-Factory-FlashTool.zip?dl=0
Link 2: https://mega.nz/#!EUtgCSYR!NaQIrDNJBIN5zvEvfeU95Roc7YaPTamstDbKPKxfpF8
UserData and Cache (Required for the Format All + Download option)
Link 1: https://www.dropbox.com/s/8lpl1cfesgmoi9x/userdata+cache.zip?dl=0
Link 2: https://mega.nz/#!0FklTQpD!eLGXQDIhBfyKMfm5FOLrThJ0ah7VqKoeuOYue2pBBDA
Also, for those who are unaware, after a complete format and flash, you may need to change your IMEI numbers back to their original values. If you require assistance in doing this, let me know.
Let me know how it works for you!
Click to expand...
Click to collapse
Sorry but it's not the correct forum to post this
Apologies. Would you be able to direct me to the correct forum?
TechManPro said:
Apologies. Would you be able to direct me to the correct forum?
Click to expand...
Click to collapse
You gotta move this to android general forum, ask the moderators to do so
I. Introduction
Samsung Stock Roms use a special .qmg format for the bootanimation. This makes changing the bootanimation difficult because of less support.
Android uses a binary called bootanimation (/system/bin) to run the bootanimations, and Samsung has tweaked it to load .qmg formates. But we can tweak that binary to load the bootanimation.zip instead of bootanimation.qmg.
NOTE: You must be rooted with TWRP installed.
II. Installation guide
1] Download the proper zip according to your android version
2] Reboot your device to the recovery and install bootanimationzipsupport.zip
3] Install PACM Bootanimation.zip (This is just to test bootanimation)
4] Reboot your device
Now, once you reboot your smartphone, you will see the stock Android Bootanimation:good::fingers-crossed:
Did you get a softbrick?
The zip automatically creates a zip that allows to restore the previous bootanimation binary. Reboot to recovery and install the StockBootanimationRestorer.zip inside the /vr-theme folder in you sd card.
Tested Deiveces
Galaxy A5 2016
(Actually this will work for any device)
Original Thread: http://forum.xda-developers.com/note-4/themes-apps/bootanimation-zip-support-note-4-t3157128
PRESS THANKS IF I HELPED YOU
Hi, thanks for guide, but the kk zip it's for 4.4, and ll zip it's for 5.1 (I take a look in updater-script before installing), works ll zip in 5.0.2???
I have a A500FU
TheAbraham696 said:
Hi, thanks for guide, but the kk zip it's for 4.4, and ll zip it's for 5.1 (I take a look in updater-script before installing), works ll zip in 5.0.2???
I have a A500FU
Click to expand...
Click to collapse
Yes, it should work. It will automatically create a backup of the original binary and place it in your SD Card in vrtheme folder so that you can restore it incase of any problem. Also as per my experience it will not cause a bootloop. Just a black screen will appear after bootlogo, and then it will boot.
To be in a safer side take a backup of /system.
BEST OF LUCK:good::fingers-crossed:
Siddhant NAik said:
Yes, it should work. It will automatically create a backup of the original binary and place it in your SD Card in vrtheme folder so that you can restore it incase of any problem. Also as per my experience it will not cause a bootloop. Just a black screen will appear after bootlogo, and then it will boot.
To be in a safer side take a backup of /system.
BEST OF LUCK:good::fingers-crossed:
Click to expand...
Click to collapse
works perfect in lp, but now are available android MM, works in MM???
Any nougat bootanimation.zip enabler?
MikeyIsHere123 said:
Any nougat bootanimation.zip enabler?
Click to expand...
Click to collapse
You can check out this thread. https://forum.xda-developers.com/note-4/themes-apps/bootanimation-zip-support-note-4-t3157128 Ive tried the MM bootanimation enabler zip on A310F/Nougat and it worked just fine.
tys0n said:
you can check out this thread. https://forum.xda-developers.com/note-4/themes-apps/bootanimation-zip-support-note-4-t3157128 ive tried the mm bootanimation enabler zip on a310f/nougat and it worked just fine.
Click to expand...
Click to collapse
thank you so much it worked!
Work on jellybean 4.2.2?
Debloated Rom For The Fire TV Stick 4K 6.2.7.1 93/6.2.7.7 Revised
NOTE: Firmware versions after 6.2.7.7 will not work with this debloated rom. It's been a few months since I've updated this guide so be cautious with installing this. The latest fw implements an efuse to prevent downgrading.
IMPORTANT!!!
NEVER FLASH A STOCK ROM >= 6.2.8.0 AFTER FLASHING 6.2.8.1_r2 OR LATER! THIS WILL BLOW AN EFUSE.
Steps: Boot into TWRP from either the OTG cable or through an ADB command by enabling ADB debugging in My Fire TV, Developer Options. After booting into TWRP, make sure to wipe system, dalvik, and cache before flashing but before doing any of that take a backup of the system image, vendor image, boot and finally your data. After restoring remember Amazon will automatically have a verification to sign you in again because of security reasons.
XDA:DevDB Information
Debloated Rom For Fire TV Stick 4K (6.2.7.1 93/6.2.7.7)
Contributors
Skel40
ROM OS Version: 6.2.7.7 Debloated Rom. Based off the Stock Image of 6.2.7.1/93. 6.2.7.7 Pre-rooted Image.
ROM Firmware Required: 6.2.7.7 and less, efuse is now blown in version 6.2.8.0
Version Information
6.2.7.7 Revised
Debloated Latest Rom with 146 applications left out of the 171 installed with this new version found in /system/priv-app. The folder lists the removed files along with built in build.prop tweaks. (New) I moved the rom to MEGA for easier access. A little bit more packages have been added back for stability reasons. The package, com.amazon.tv.turnstile is the problem when pairing remotes so the issue is fixed!
6.2.7.1 93
Debloated Rom with 126 applications in priv-app, same information as above. With Build.prop Tweaks and no boot animation on reboot. Read the Changelog in the 6.2.7.1 93 Rom below for more information in the Removed Files Folder.
Issues: Prime Video is still having problems downloading and installing an additional app after installing it from the Amazon Appstore. The incremental updates won't work on 6.2.7.1 93 because of attempting to update to 6.2.7.7
Current Stable Version: Revised Version 1.1 6.2.7.7
Stable Release Date: 2021-01-04 (6.2.7.7 revised)
Created 2020-04-18
Last Updated 2021-01-04
Debloated Rom 6.2.7.1 93 with Removed Files: https://drive.google.com/drive/folders/1bmZwmkyJw4e7Y9cjtiAfdr0KuQnA-CHK?usp=sharing
Debloated Rom 6.2.7.7 MEGA Revised 1.1
642.99 MB folder on MEGA
36 files and 45 subfolders
mega.nz
Changelog of 6.2.7.1 93
With this downgraded release of 6.2.7.1 93, expect a few problems with several packages that I've removed for a reason:
Changelog of the 6.2.7.1 93 Debloated Version (FTVLaunchX/Accessibility features are working)
The apps that aren't working is solely because of the missing "System Components" update
* Amazon FreeTime won't work
* IMDB won't work (Use the Free section on the Fire TV Home UI for Free Movies/TV)
* News won't work
* Updating won't go through unless you choose to upgrade to the latest OS (Meaning it'll keep downloading 6.2.7.7 but will fail because of otacerts.zip being removed)
* Build.prop Tweaks are added to this rom, use a computer to transfer the prop file if you choose not to have the tweaks yourself.(My post can be found here: https://forum.xda-developers.com/fire-tv/general/fire-tv-stick-4k-tweaks-root-keyboard-t4064269)
* Make a TWRP backup before flashing this rom of the following partitions: System Image, Boot, Data, and Vendor Image in case you want to go back however you want
* Most of things if not many of the packages and files are gone for maximum storage as possible (Removed Files can be found on the OP of this page)
* Please note that the mbcache.db file is a storage decreaser, use these commands for chmod 0 and make the file frozen with 0 MB
adb connect 192.168.x.x (change it to your IP)
adb shell
su
cd /data/data/com.amazon.tv.launcher/databases
rm mbcache.db*
touch mbcache.db
touch mbcache.db-shm
touch mbcache.db-wal
chmod 0 mbcache.db*
ls-all
To re-enable
adb connect 192.168.1.101 (change it to your IP)
adb shell
su
cd /data/data/com.amazon.tv.launcher/databases
rm mbcache.db*
touch mbcache.db
touch mbcache.db-shm
touch mbcache.db-wal
chmod 660 *.db
chmod 600 *.db-*
* All three files are zeros. Reboot and you'll now see more increased storage.
* Amazon Home will throw an error so enable Do Not Disturb in Settings
* Magisk is pre-installed, and the System is in RW mode.
* The Setup Wizard SHOULD go through no matter what. No need to worry about being stuck
Changelog of 6.2.7.7 Revised
* Magisk is pre-installed, and the System is also in RW mode.
*Priv-app, app, and media have been modified for debloating with a list of every file I've removed and being able to download the removed files as an apk without unzipping.
*Added Build tweaks except for the no boot animation
*Added packages back for stability
This guide is outdated but can still be flashed with this neat trick I learned from AFTVnews' guide about VoiceView found here:
How to Skip Software Updates during Initial Setup or Factory Reset on a Fire TV, Firestick, or Fire TV Cube
Since the latest software update for Fire TV devices is blocking the ability to use custom launchers, you may want to avoid updating a new or factory reset Fire TV.
www.aftvnews.com
I've pulled the 1.2 version to see what's wrong with the rom. Wip will be soon when I have time available
So far everything seems good .
Can you write the command to make a Backup
An how to restore over adb shell?
0815hoffi said:
Can you write the command to make a Backup
An how to restore over adb shell?
Click to expand...
Click to collapse
I just used a usb mouse hooked to a little hub I got off Amazon for about 6 or 7 dollars to use TWRP
Ok.
Thanks
0815hoffi said:
Ok.
Thanks
Click to expand...
Click to collapse
I used this one : https://www.amazon.com/gp/product/B07SZTHPPR/ref=ppx_yo_dt_b_asin_title_o07_s00?ie=UTF8&psc=1
I have been using your rom and it seems real snappy and smooth. So far no problems.
brick00444 said:
Tried it and am stuck on black fire tv screen. I will unbrick and try again in a bit.
Got it going, I wasn't on the 6.2.7.1 the first time and it didn't work. Updated using the 6.2.7.1 rom you posted in another thread then used your backup. So far everything seems good .
Click to expand...
Click to collapse
Maybe Skel40 should add a boot.img (suitable to his rom backup), in order to avoid such problems.
Sus_i said:
Maybe Skel40 should add a boot.img (suitable to his rom backup), in order to avoid such problems.
Click to expand...
Click to collapse
Updated the OP with the boot.img on Google Drive! Thank you!
brick00444 said:
Tried it and am stuck on black fire tv screen. I will unbrick and try again in a bit.
Got it going, I wasn't on the 6.2.7.1 the first time and it didn't work. Updated using the 6.2.7.1 rom you posted in another thread then used your backup. So far everything seems good .
Click to expand...
Click to collapse
Ok flashing the rom I posted on the other forum with this backup erases the modifications done for debloating due to the zip acting like its an update therefore re-adds the deleted apps I deleted myself!!!!! Try downloading the boot.emmc.win and boot.emmc.win.sha2 with the debloated rom you downloaded, and restore the boot.img along with the system image, vendor image. (Put the boot.emmc.win and boot.emmc.win.sha2 inside the ftvs4kdebloatedv1.0 folder IF downloaded already) Before doing this, wipe /system, data, and cache THEN restore the system image, vendor image, and boot! Get back to me as soon as possible!!!!
Skel40 said:
Ok flashing the rom I posted on the other forum with this backup erases the modifications done for debloating due to the zip acting like its an update therefore re-adds the deleted apps I deleted myself!!!!! Try downloading the boot.emmc.win and boot.emmc.win.sha2 with the debloated rom you downloaded, and restore the boot.img along with the system image, vendor image. (Put the boot.emmc.win and boot.emmc.win.sha2 inside the ftvs4kdebloatedv1.0 folder IF downloaded already) Before doing this, wipe /system, data, and cache THEN restore the system image, vendor image, and boot! Get back to me as soon as possible!!!!
Click to expand...
Click to collapse
The first time I tried it, I was on an older rom version. When I used your backup it was stuck at the black fire tv screen. I was able to get into TWRP and flash your 6.2.7.1 rom you posted then used your backup and it worked great. I should have made that clear. Sorry for that. That being said, with the new files you listed can a person use your backup on another rom version " say 6.2.6.8 " or should it be on 6.2.7.1.? I have another 4k stick I might have time tomorrow to test the new method on.
brick00444 said:
Twith the new files you listed can a person use your backup on another rom version " say 6.2.6.8 " or should it be on 6.2.7.1.? I have another 4k stick I might have time tomorrow to test the new method on.
Click to expand...
Click to collapse
A backup with boot.img should work, without it won't.
Can it be restored without otg .
Twrp Commandline?
Sus_i said:
A backup with boot.img should work, without it won't.
Click to expand...
Click to collapse
Thank you
Have tried this rom to pass updating configuration screen on my Fire TV 4k without success. Restored this rom from TWRP without a problem but stucked again at configuration updating screen.
WarrenDen said:
Have tried this rom to pass updating configuration screen on my Fire TV 4k without success. Restored this rom from TWRP without a problem but stucked again at configuration updating screen.
Click to expand...
Click to collapse
Any solution to skip updating screen?
Yes you must decompile com.amazon.tv.oobe.apk
with APK Easy Tool.
!!!!! For Sure save a backup of this file !!!!
and customize NativePageProvider.smali file
Replace the Update command like
Lines
??????? 》with NOP
example attached , decompile it and compare the file to understand how it works
than compile with APK Easy Tool and replace the file over twrp.
------‐-----------'
Easy way delete com.amazon.tv.oobe.apk over twrp.
Pair remote with use of TV-CEC Remote.
An then do the Configuration.
But then it is not possible to enable adb over the settings.
Can be done in twrp maybe.
in TWRP type:
echo -n 'mtp,adb' > /data/property/persist.sys.usb.config
echo '' >> /system/build.prop
echo '# Enable ADB' >> /system/build.prop
echo 'persist.service.adb.enable=1' >> /system/build.prop
echo 'persist.service.debuggable=1' >> /system/build.prop
echo 'persist.sys.usb.config=mtp,adb' >> /system/build.prop
Reboot
Do it at your own Risk!!!!!
If it works, run.
adb shell settings put global setup_wizard_has_run 1
adb shell settings put secure user_setup_complete 1
adb shell settings put global device_provisioned 1
To set oobe succesfully run.
----‐---------
Own Risk you can try replace com.amazon.tv.oobe.apk with the attached file, run the Setup Wizard and After that copy back the backuped com.amazon.tv.oobe.apk to /system/priv-app/com.amazon.tv.oobe/com.amazon.tv.oobe.apk
0815hoffi said:
Yes you must decompile com.amazon.tv.oobe.apk
with APK Easy Tool.
!!!!! For Sure save a backup of this file !!!!
and customize NativePageProvider.smali file
Replace the Update command like
Lines
??????? 》with NOP
example attached , decompile it and compare the file to understand how it works
than compile with APK Easy Tool and replace the file over twrp.
------‐-----------'
Easy way delete com.amazon.tv.oobe.apk over twrp.
Pair remote with use of TV-CEC Remote.
An then do the Configuration.
But then it is not possible to enable adb over the settings.
Can be done in twrp maybe.
in TWRP type:
echo -n 'mtp,adb' > /data/property/persist.sys.usb.config
echo '' >> /system/build.prop
echo '# Enable ADB' >> /system/build.prop
echo 'persist.service.adb.enable=1' >> /system/build.prop
echo 'persist.service.debuggable=1' >> /system/build.prop
echo 'persist.sys.usb.config=mtp,adb' >> /system/build.prop
Reboot
Do it at your own Risk!!!!!
If it works, run.
adb shell settings put global setup_wizard_has_run 1
adb shell settings put secure user_setup_complete 1
adb shell settings put global device_provisioned 1
To set oobe succesfully run.
----‐---------
Own Risk you can try replace com.amazon.tv.oobe.apk with the attached file, run the Setup Wizard and After that copy back the backuped com.amazon.tv.oobe.apk to /system/priv-app/com.amazon.tv.oobe/com.amazon.tv.oobe.apk
Click to expand...
Click to collapse
Should work even for 4k Fire TV? Or only for 2 gen?
@dadme
I have played around this with 4k , and it works.
But with the Restrictions i Described.
This i have testet 4k.
Flashable 4k Twrp zip attached.
It delete oobe and amazon launcher and install leanbacklauncher.
try it at your own risk
Error in zip fixed, please redownload
0815hoffi said:
@dadme
I have played around this with 4k , and it works.
But with the Restrictions i Described.
This i have testet 4k.
Flashable 4k Twrp zip attached.
It delete oobe and amazon launcher and install leanbacklauncher.
try it at your own risk
Click to expand...
Click to collapse
Thanks for the info! I make a try on the weekend. Restrictions.. I don;t have Amazon Prime... Just for Kodi and HBO Go. And mirroring phone display..
That would be another question. In case of an software update, the process of decompile and patching will probably have to be restarted?