Related
Here are prerooted stock images for use with my recovery. Note that these contain addon.d support, so any 3rd party things you install to /system need an addon.d script to be retained between flashes.
If you are currently on FireOS3 and CWM you MUST install TWRP recovery from the link above before using these.
Can't cd to /sdcard after using su? Install this TWRP flashable zip to fix it.
Changelog and Downloads:
July 4, 2020 - 5.2.7.3_r1 (md5sum: 92824186b5eec7e86792897bfb9593b7)
December 7, 2019 - 5.2.7.2_r1 (md5sum: 8dd08a41900a75794f28c455e173141f)
June 29, 2019 - 5.2.7.0_r1 (md5sum: 97b9ffef275d7dffcae085b2325aa9cc)
March 30, 2019 - 5.2.6.9_r1 (md5sum: 2f00ee478118ccf034b70236357ee0a3)
November 27, 2018 - 5.2.6.7_r1 (md5sum: cc455830d78f2d545760f1705dbe4f63)
October 7, 2018 - 5.2.6.6_r1 (md5sum: de48df30cadf9f88865698d3a3e514ef)
June 24, 2018 - 5.2.6.3_r1 (md5sum: c4fcecc0d3dda3f5c58ba9bbc1fddbdc)
January 28, 2018 - 5.2.6.2_r1 (md5sum: facfcc900ac21e70023b6fbf7259b5b0)
October 8, 2017 - 5.2.6.0_r1 (md5sum: 126fffd4f2384a483792b336b0c89b83
July 3, 2017 - 5.2.4.1_r2 (md5sum: ee25fe57cce08dce6c5962871916c7e3
May 1, 2017 - 5.2.4.1_r1 (md5sum: 64451a8f88cb5a3fff53f14c80ba2267)
January 31, 2017 - 5.2.1.2_r1 (md5sum: 4a01e9a4e6bdcb98da97d2438bf5066d)
September 3, 2016 - 5.2.1.1_r1 (md5sum: 4c4cc2b9dc01cf8397905712b8c91ae3)
July 4, 2016
5.2.1.0_r1 (md5sum: c465bbbddaf3254f805bddbf2d162637)
5.0.5_r2 (md5sum: 32c869fff5e39a5c0d2f5f48b3a10ef5)
This includes the same 2ndinit as before and TWRP version 3.0.0-7. This version of TWRP has support for 720p and fixes the crashing/looping.
May 20, 2016 - 5.0.5.1_r1 (md5sum: 5398851cb37ecd6c5df80abe1cc85447)
This includes 2ndinit version a7a48c and TWRP version 3.0.0-6.
May 20, 2016 - 5.0.5_r1 (md5sum: 924dadb59d73083704844bb27f189449)
This includes 2ndinit version a7a48c and TWRP version 3.0.0-6.
Everything below here is FireOS3.
September 7, 2015 - Added 51.1.6.3_516012020 (md5sum: fcf1a8ddf2f3bc93280af03dcf408ac8)
This update requires FireTV Boot Menu.
If you don't already have 51.1.4.0 or newer, you must flash 51.1.4.0 first.
August 20, 2015 - Added 51.1.6.2_516011120 (md5sum: 3fd1cc67fdd3351b470d09cff586fbf8)
This update requires FireTV Boot Menu.
If you don't already have 51.1.4.0 or newer, you must flash 51.1.4.0 first.
July 21, 2015 - Added 51.1.6.1_516010220 (md5sum: 61ae1e646c970faf137e9a31d64a1316)
This update requires FireTV Boot Menu.
If you don't already have 51.1.4.0 or newer, you must flash 51.1.4.0 first.
July 9, 2015 - Added 51.1.6.0_516009820 (md5sum: a1b550d1a7b21a348ca6bd0d7127427c)
This update requires FireTV Boot Menu.
If you don't already have 51.1.4.0 or newer, you must flash 51.1.4.0 first.
May 24, 2015 - Added 51.1.5.3_515040320 (md5sum: a12852edbe6dc24146533f43e0ae4a05)
This update requires FireTV Boot Menu.
If you don't already have 51.1.4.0 or newer, you must flash 51.1.4.0 first.
Apr 15, 2015 - Added 51.1.5.0_515030720 (md5sum: de2ab7f2d3072e10d3e592b73ca52750)
This update requires FireTV Boot Menu.
If you don't already have 51.1.4.0 or newer, you must flash 51.1.4.0 first.
Mar 26, 2015 - Added 51.1.5.0_515020820 (md5sum: b7005dd3cc0b6a15dae21b0170aeae85)
This update requires FireTV Boot Menu.
If you don't already have 51.1.4.0 or newer, you must flash 51.1.4.0 first.
Nov 21, 2014 - Added 51.1.4.1_514013920+fixed (md5sum: 4429327daeed0df852731d81fa9b1f54)
Starting with this update, this requires FireTV Boot Menu.
You also must ensure you have already flashed 51.1.4.0.
Nov 19, 2014 - Added 51.1.4.1_514013920 (md5sum: 348c8b23d785177f7dfd45cc2ef19626)
Oct 30, 2014 - Added 51.1.4.0_514006420+updated (md5sum: b1b48348cb56c0b83a3affc9fd06e07e)
This fixes the Netflix problem from the original 51.1.4.0. After flashing and rebooting, you might get a hung black screen. If that is the case, just pull the power and plug it back in. Also, Netflix might be broken for International people using DNS unblocking. Please let me know if it works/doesn't work for you when using DNS unblocking.
Oct 29, 2014 - Added 51.1.4.0_514006420[/URL] (md5sum: 98074ae3dead5c12ce77d735c2126b80)
Oct 02, 2014 - Added 51.1.3.0_513011820 (md5sum: 8a7b02691760abf11db4c1c583c20d8f)
Sep 20, 2014 - Added 51.1.3.0_513011520 (md5sum: 2dbd022eacbad0b001753d7519f0ad1b)
Sep 19, 2014 - Added 51.1.1.0_511070220 (md5sum: f98fe5b7de4acb5d2dfa4d8586179b98)
Here are some guides with step by step instructions:
How to install ClockworkMod Custom Recovery on the Amazon Fire TV
http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/
How to update ClockworkMod Custom Recovery on the Amazon Fire TV
http://www.aftvnews.com/how-to-update-clockworkmod-custom-recovery-on-the-amazon-fire-tv/
How to remotely control ClockworkMod on the Amazon Fire TV using ADB
http://www.aftvnews.com/how-to-remotely-control-clockworkmod-on-the-amazon-fire-tv-using-adb/
How to install a Custom ROM Image on the Amazon Fire TV
http://www.aftvnews.com/how-to-install-a-custom-rom-image-on-the-amazon-fire-tv/
How to update a Rooted Amazon Fire TV to the Latest Version Without Losing Root
http://www.aftvnews.com/how-to-upda...tv-to-the-latest-version-without-losing-root/
How to Revert back to Stock Recovery and Stock Software
http://www.aftvnews.com/how-to-revert-an-amazon-fire-tv-back-to-stock-recovery-and-stock-software/
..
@rbox when flashing the pre-rooted image, does it also rebuild/replace the recovery?
I'm just curious how these work, and if CWR would then need to be 'dd' again. I did a quick compare between the pre-rooted image and the stock, and the only differences I see are su binary, superuser.apk, and the removal of every file from the root of the zip but:
boot.img
NON-HLOS.bin
prod_cert_swap.sed
sed
Luxferro said:
@rbox when flashing the pre-rooted image, does it also rebuild/replace the recovery?
I'm just curious how these work, and if CWR would then need to be 'dd' again. I did a quick compare between the pre-rooted image and the stock, and the only differences I see are su binary, superuser.apk, and the removal of every file from the root of the zip but:
boot.img
NON-HLOS.bin
prod_cert_swap.sed
sed
Click to expand...
Click to collapse
No. It doesn't touch the recovery. These images are basically just the regular image with the bootloader and nonessential images pulled out. And as you can see, it comes with su.
rbox said:
No. It doesn't touch the recovery. These images are basically just the regular image with the bootloader and nonessential images pulled out. And as you can see, it comes with su.
Click to expand...
Click to collapse
Doesn't android typically rebuild & flash the recovery partition from boot.img and /system/etc/recovery-resource.dat when it detects it's been changed? I was just curious when that normally would occur on a stock FireTV, and what prevents this from happening on your pre-rooted images. I haven't used any prerooted images. Already had root and just dd'd your cwr_recovery.img. CWR asks you if you want to disable the stock recovery process. As a test I picked no, and CWR didn't get replaced. So should I assume that Amazon doesn't run any scripts at boot that check the recovery and rebuild/flash it?
To make a long story short. I was just curious if your pre-rooted images disabled the recovery replacement, since I still saw the recovery-resource.dat used to build them in the zip. But I guess FireOS doesn't do that at boot
edit: I guess that may have been disabled by towelroot, since the install-recovery.sh is being used to start the /system/xbin/daemonsu --auto-daemon &
Luxferro said:
Doesn't android typically rebuild & flash the recovery partition from boot.img and /system/etc/recovery-resource.dat when it detects it's been changed? I was just curious when that normally would occur on a stock FireTV, and what prevents this from happening on your pre-rooted images. I haven't used any prerooted images. Already had root and just dd'd your cwr_recovery.img. CWR asks you if you want to disable the stock recovery process. As a test I picked no, and CWR didn't get replaced. So should I assume that Amazon doesn't run any scripts at boot that check the recovery and rebuild/flash it?
To make a long story short. I was just curious if your pre-rooted images disabled the recovery replacement, since I still saw the recovery-resource.dat used to build them in the zip. But I guess FireOS doesn't do that at boot
Click to expand...
Click to collapse
51.1.3.0 was actually the first version to include an updated recovery. If you look in the stock 51.1.3.0 image, you'll see a recovery directory with recovery-from-boot.p and install-recovery.sh. I removed that from my image. The install-recovery.sh is the one that updates the recovery.
I'm not quire sure why it asked you about disabling stock. I'm guessing you booted into it, did nothing, and then rebooted. The only thing I can guess is whatever you had installed already had a /system/etc/install-recovery.sh script there. That doesn't seem to be included in the stock update images. Maybe the stock recovery writes it if it doesn't exist... Either way, I think people have said the install-recovery.sh script that came with stock didn't do anything. And then when you install one of my updates, it definitely doesn't come with it.
Also, I just uploaded 51.1.3.0.
rbox said:
51.1.3.0 was actually the first version to include an updated recovery. If you look in the stock 51.1.3.0 image, you'll see a recovery directory with recovery-from-boot.p and install-recovery.sh. I removed that from my image. The install-recovery.sh is the one that updates the recovery.
I'm not quire sure why it asked you about disabling stock. I'm guessing you booted into it, did nothing, and then rebooted. The only thing I can guess is whatever you had installed already had a /system/etc/install-recovery.sh script there. That doesn't seem to be included in the stock update images. Maybe the stock recovery writes it if it doesn't exist... Either way, I think people have said the install-recovery.sh script that came with stock didn't do anything. And then when you install one of my updates, it definitely doesn't come with it.
Click to expand...
Click to collapse
The contents of my install-recovery.sh had to do with the su daemon. So i assume it was from towelroot. edit: actually probably one of the variations of superuser?
Basically I was curious what changes you were making so the stock recovery wasn't being flashed back, just in case I wanted to mess around with later revisions that aren't rootable and might flash the stock recovery back and leave me w/ an unrootable system. Like 51.1.3.0. But I see that you just created a pre-rooted 51.1.3.0 Anyway, it was more of a curiosity than me wanting to have the latest version.
Upgrading to Pre-Rooted 51.1.3.0_513011520
Hi rbox,
Great work... Just a quick question to clear up any confusion.
I currently have 51.1.1.0_user_511070220 install and rooted with towelroot.
If I want to update to Pre-Rooted 51.1.3.0_513011520 do I still need to downgrade to the Official Stock Software Package version 51.1.0.2_user_510058520.
Install ClockworkMod Custom Recovery .
Then upgrade via Custom Recovery to Pre-Rooted 51.1.3.0_513011520?
Or
Can I just upgrade to Pre-Rooted 51.1.3.0_513011520 via the firmware upgrade script http://forum.xda-developers.com/showthread.php?t=2796067?
imtiajmeah said:
Hi rbox,
Great work... Just a quick question to clear up any confusion.
I currently have 51.1.1.0_user_511070220 install and rooted with towelroot.
If I want to update to Pre-Rooted 51.1.3.0_513011520 do I still need to downgrade to the Official Stock Software Package version 51.1.0.2_user_510058520.
Install ClockworkMod Custom Recovery .
Then upgrade via Custom Recovery to Pre-Rooted 51.1.3.0_513011520?
Or
Can I just upgrade to Pre-Rooted 51.1.3.0_513011520 via the firmware upgrade script http://forum.xda-developers.com/showthread.php?t=2796067?
Click to expand...
Click to collapse
As the post says... the prerooted images are only for use with my recovery. So yes, you have to downgrade and install it.
Read Again
imtiajmeah said:
Hi rbox,
Great work... Just a quick question to clear up any confusion.
I currently have 51.1.1.0_user_511070220 install and rooted with towelroot.
If I want to update to Pre-Rooted 51.1.3.0_513011520 do I still need to downgrade to the Official Stock Software Package version 51.1.0.2_user_510058520.
Install ClockworkMod Custom Recovery .
Then upgrade via Custom Recovery to Pre-Rooted 51.1.3.0_513011520?
Or
Can I just upgrade to Pre-Rooted 51.1.3.0_513011520 via the firmware upgrade script http://forum.xda-developers.com/showthread.php?t=2796067?
Click to expand...
Click to collapse
Regarding these images, the OP states clearly: "These will not work with the stock recovery". You will not be able to update to them without first installing CWM.
rbox said:
As the post says... the prerooted images are only for use with my recovery. So yes, you have to downgrade and install it.
Click to expand...
Click to collapse
For the sake of clarity and semantics, is the "Pre-Rooted Stock Software" the same as "Pre-Rooted Stock Images"? The word Images is throwing off my understanding.
Hi there,
Just one question i didn't find an answere.
Can i use this stock images on German fire TV?
Thx. For a quick reply
Zetup-EXE said:
Hi there,
Just one question i didn't find an answere.
Can i use this stock images on German fire TV?
Thx. For a quick reply
Click to expand...
Click to collapse
I wasn't aware that anyone had gotten the German Fire TV, so... I'll just whip out my crystal ball...
All signs point to it coming with 51.1.3.0, which is unrootable. So... no.
Awesome work rbox!
I´m on pre-rooted 51.1.3.0 by now. As soon as i can i´ll keep donating to you! This is exactly why i bought my FTV!
Thanks!
mjbxx said:
For the sake of clarity and semantics, is the "Pre-Rooted Stock Software" the same as "Pre-Rooted Stock Images"? The word Images is throwing off my understanding.
Click to expand...
Click to collapse
Yes, they are the same.
Stock Image, Stock Software, Stock ROM, Stock OS, and Stock Package all mean the same thing. The only important distinction to remember is that there is a difference between a Recovery image and the rest of the software that runs on the Fire TV.
"Pre-Rooted Stock Images" do not include the recovery image within them, whereas the official 51.1.3.0_user_513011520 update from Amazon does include a recovery image. rbox has stripped out the recovery image from the official update because if he didn't, installing his pre-rooted version would overwrite ClockworkMod recovery.
I assumed this was done, but I wasn't 100% sure so I verified that the updating mechanism has been blocked on these prerooted images.
Code:
[email protected]:/ # pm list packages -d
pm list packages -d
package:com.amazon.dcp
[email protected]:/ #
mastermind278 said:
I assumed this was done, but I wasn't 100% sure so I verified that the updating mechanism has been blocked on these prerooted images.
Code:
[email protected]:/ # pm list packages -d
pm list packages -d
package:com.amazon.dcp
[email protected]:/ #
Click to expand...
Click to collapse
i was just about to ask the same thing, thanks. now im just wondering if i can install cwm from 51.1.0.1 as i've been blocking updates since day one or if i should just update to 51.1.0.2 and then install cwm.
nhumber said:
i was just about to ask the same thing, thanks. now im just wondering if i can install cwm from 51.1.0.1 as i've been blocking updates since day one or if i should just update to 51.1.0.2 and then install cwm.
Click to expand...
Click to collapse
I am wondering the same thing.
Sent from my SCH-I545 using Tapatalk
Here are prerooted stock images for use with my recovery. Note that these contain addon.d support, so any 3rd party things you install to /system need an addon.d script to be retained between flashes.
Managing Stock Recovery
Starting with 5.0.5_r3, stock recovery gets disabled. This means you cannot reboot in to stock recovery manually or automatically because of a system update. This will make it safer for people who forget to disable updates. You should still disable updates though. If for whatever reason, you want to reenable it, or verify it is disabled, you can use the manage_recovery program. Under normal circumstances, you should never need to use manage_recovery.
Connect to adb and start a shell
Switch to root with su
Run manage_recovery (if you do not run su first, it will seem to run, but won't actually be able to do anything)
Code:
manage_recovery
There are 3 different scenarios that manage_recovery will detect and prompt for.
The first is when stock recovery is disabled, it will look like this:
Code:
Checking current stock recovery status... NOT STOCK
Checking for reason... DISABLED
Stock recovery is currently disabled,
Would you like to enable it?
Type 'yes' to enable it, anything else to quit.
The second is when a stock recovery is flashed that does not match the current system version:
Code:
Checking current stock recovery status... NOT STOCK
Checking for reason... WRONG VERSION
Would you like to disable stock recovery?
Type 'yes' to disable it, anything else to quit.
And finally, the third is when stock recovery is enabled and the correct version:
Code:
Checking current stock recovery status... STOCK
Would you like to disable stock recovery?
Type 'yes' to disable it, anything else to quit.
After changing the recovery status, you can run the program again to verify it changed.
WARNING: DO NOT FLASH 5.0.5.1 OR EARLIER IF YOU STARTED WITH VERSION 5.2.1.0 OR LATER
NOTE: If you were at 5.2.6.6 or below, you MUST flash 5.2.6.7 before going to 5.2.6.8 or later.
Changelog and Downloads:
December 26, 2020 - 5.2.7.6_r1 (md5sum: 01178aecf55cd895cbfdeb64d5a19e62)
July 4, 2020 - 5.2.7.3_r1 (md5sum: 875436574974c3603aef179b898a4c60)
December 7, 2019 - 5.2.7.2_r1 (md5sum: b91c6b596ef5daae085ddf08c1c504e5)
September 21, 2019 - 5.2.7.1_r1 (md5sum: 0d72e930cee2652d324d2fceebdd4202)
June 29, 2019 - 5.2.7.0_r1 (md5sum: 1e402185cefb91276d811f1321494863)
March 30, 2019 - 5.2.6.9_r1 (md5sum: a3e23a7f337346a4638f8c8895632046)
February 10, 2019 - 5.2.6.8_r1 (md5sum: bd0daa677635e04e368d1b2b235e03e9)
December 2, 2018 - 5.2.6.7_r2 (md5sum: b50a1fddb3e01c18c353195c9f7f50cd)
This ROM contains updated DRM firmware.
November 27, 2018 - 5.2.6.7_r1 (md5sum: b0ee16b57b37a934778ca1436f29916a)
This ROM contains updated DRM firmware.
September 28, 2018 - 5.2.6.6_r1 (md5sum: 37ce0c6dda850fa2d462835496b68576)
June 24, 2018 - 5.2.6.3_r1 (md5sum: 08982269022c01c9a1eac8ff94adf637)
January 28, 2018 - 5.2.6.2_r1 (md5sum: 0967de2a707f173ca8715356a20ea88e)
October 8, 2017 - 5.2.6.0_r1 (md5sum: 84eedbb2e9fd4b57679747ecb8fae797)
July 27, 2017 - 5.2.4.2_r2 (md5sum: a96e73478cdbe8659f6758a5d27b4738)
This includes updated firmware to fix Hulu and HBO.
July 3, 2017 - 5.2.4.2_r1 (md5sum: 0719fde0db90702c2407461003217977)
May 1, 2017 - 5.2.4.1_r1 (md5sum: 64915fceb4e7d1c0de9d1ef625db48e7)
December 10, 2016 - 5.2.4.0_r1 (md5sum: 77af47d3c43fe79e82740d0cc0c4bce5)
September 10, 2016 - 5.2.1.1_r1 (md5sum: fd7c06bce26d4aa611eef402ef156322)
July 4, 2016 - 5.2.1.0_r2 (md5sum: a69981f6d4dce77cf1f9907f8a39b391)
This is the same as the previous 5.2.1.0, just with the updated version that Amazon released.
June 1, 2016 - 5.2.1.0_r1 (md5sum: 81693eae0ce3b497cf425691bc4ad041)
This includes 2ndinit version dee776 and TWRP version 3.0.0-5.
April 8, 2016 - 5.0.5.1_r1 (md5sum: c6d8a11b7ca7a0b45a38af4f9f70cf2d)
The updated TWRP in this version should disable auto flashing amazon updates.
This includes 2ndinit version dee776 and TWRP version 3.0.0-5.
February 14, 2016 - 5.0.5_r4 (md5sum: 9145c8f6d52fda2c3cfdd1d091bcb331)
The updated TWRP in this version should fix the issues certain keyboards were having.
This includes 2ndinit version dee776 and TWRP version 3.0.0-4.
February 13, 2016 - 5.0.5_r3(md5sum: 92d08a12d240cf9bf6d25005a65bd82d)
Starting with this update, stock recovery will be disabled to prevent stock updates from being flashed. Please refer to the instructions above for managing stock recovery.
This includes 2ndinit version dee776 and TWRP version 3.0.0-3. Because this comes with a newer 2ndinit version, do not flash an older recovery package. Doing so will disable su.
February 12, 2016 - 5.0.5_r2
OTA updates are permanently disabled, otherwise the same as r1.
[*]
This breaks booting with a factory reset.
February 12, 2016 - 5.0.5_r1(md5sum: 211a15f949e317b02c637b2927a7c8ba)
This includes 2ndinit version 743aa4 and TWRP version 3.0.0-3.
February 8, 2016 - 5.0.4_r2(md5sum: ebcecf89e9b81c02f22ed2706fe5f796)
This comes with TWRP 3.0.0-2
This comes with the same 2ndinit version
February 6, 2016 - 5.0.4_r1(md5sum: 87ce4f7802d21bd1f14c45d473783713)
This comes with 2ndinit version fe3362 and recovery version 3.0.0-1
February 6, 2016 - 5.0.3.1_r1(md5sum: e38d66dce235c9c0122dfbde2db5a6b6)
This comes with 2ndinit version fe3362 and recovery version 3.0.0-1
Awesome work!
For those who need a step-by-step guide with screenshots:
[GUIDE] How to Root a Fire TV 2 by installing rbox's Pre-Rooted Image
[VIDEO GUIDE]
Awesome! Thanks !
wadisnake said:
Awesome! Thanks !
Click to expand...
Click to collapse
Awesome! Thanks for all your great work!
Any one with Mac Guide Please help
awesome sauce!
Hi,
I ended up with following message during image installation:
Code:
[...]
Coping system image...
Updater process ended with signal: 7
Error installing zip file '/usb/sloane-5.0.4-rooted_r2.zip'
Updating partition details...
...done
And, no wonder... after power cycling (I had to do so, since recovery seemed to be frozen) it stuck in a bootloop.
But I still can access recovery!
Any ideas? Is there any way to get a more verbose output?
(Used recovery 3.0.0-2 and recovery_installer v3)
Edit:
Now there is no /system Partition mounted
Edit2:
I was able to mount /dev/block/mmcblk0p13 manually to /system but it seems that I can't mount it in rw mode.
If I do so, it switches back to ro when I there the folder. (I think, that could be the error during image installation)
What's strange is: If I enter /system/lib I can't execute any command (like "ls" "touch" etc. only cd is working) I get following output:
Code:
/system/lib # ls
CANNOT LINK EXECUTABLE DEPENDENCIES: "libc.so" is 32-bit instead of 64-bit
# echo $LD_LIBRARY_PATH
.:/sbin
File libc.so is existing, but I can't finde a way to get the file type data
Edit3:
More strange things:
I was wrong! I am able to write to /system till the point when I execute a "ls"
Than its back to ro.
Edit4:
I tried to reflash recovery and the following error:
Locating the target file...
Code:
[...]
Reading 05055F000: 100%
Opening the target file...
Reading 01D947000: 100%
error: source file is larger than target file!
No shure if that was there when I flashed it first.
Related to this post
re-rooted works fine !
its full Google Play Store Support possible ?
Hoggels said:
its full Google Play Store Support possible ?
Click to expand...
Click to collapse
yes.. its been done already but some users are having issues
Takeoo111111 said:
Hi,
I ended up with following message during image installation:
Code:
[...]
Coping system image...
Updater process ended with signal: 7
Error installing zip file '/usb/sloane-5.0.4-rooted_r2.zip'
Updating partition details...
...done
And, no wonder... after power cycling (I had to do so, since recovery seemed to be frozen) it stuck in a bootloop.
But I still can access recovery!
Any ideas? Is there any way to get a more verbose output?
(Used recovery 3.0.0-2 and recovery_installer v3)
Edit:
Now there is no /system Partition mounted
Edit2:
I was able to mount /dev/block/mmcblk0p13 manually to /system but it seems that I can't mount it in rw mode.
If I do so, it switches back to ro when I there the folder. (I think, that could be the error during image installation)
What's strange is: If I enter /system/lib I can't execute any command (like "ls" "touch" etc. only cd is working) I get following output:
Code:
/system/lib # ls
CANNOT LINK EXECUTABLE DEPENDENCIES: "libc.so" is 32-bit instead of 64-bit
# echo $LD_LIBRARY_PATH
.:/sbin
File libc.so is existing, but I can't finde a way to get the file type data
Edit3:
More strange things:
I was wrong! I am able to write to /system till the point when I execute a "ls"
Than its back to ro.
Edit4:
I tried to reflash recovery and the following error:
Locating the target file...
Code:
[...]
Reading 05055F000: 100%
Opening the target file...
Reading 01D947000: 100%
error: source file is larger than target file!
No shure if that was there when I flashed it first.
Related to this post
Click to expand...
Click to collapse
If you reboot in the middle of flashing the ROM, you're /system is going to be corrupt. It's a miracle recovery is still working. The reason the installer is failing is because you can only use it for 100% stock roms. Once you start using recovery and flashing things, you cannot (and should not) use the installer. I will add a warning.
If recovery hangs again, you can run
Code:
killall recovery
from adb shell and it will restart. It is extremely important never to reboot if you have a failure. As for logs... /tmp/recovery.log has the full log. Have you verified the file transfer properly before trying to flash?
Google Playstore
elliwigy said:
yes.. its been done already but some users are having issues
Click to expand...
Click to collapse
Who can find it? Itsca zip to Flash with Recovery or gapps.org?
For gapps.org what for options i must select it? Thx
Hoggels said:
Who can find it? Itsca zip to Flash with Recovery or gapps.org?
For gapps.org what for options i must select it? Thx
Click to expand...
Click to collapse
Read this tread: http://forum.xda-developers.com/fire-tv/help/q-guide-to-getting-google-play-rbox-t3310974
bula1ca said:
Read this tread: http://forum.xda-developers.com/fire-tv/help/q-guide-to-getting-google-play-rbox-t3310974
Click to expand...
Click to collapse
haha thx for posting the link..
amazing how much tunnel vision exists as theres threads for most anything but somehow some fail to find them lol
elliwigy said:
haha thx for posting the link..
amazing how much tunnel vision exists as theres threads for most anything but somehow some fail to find them lol
Click to expand...
Click to collapse
LOL
Success!! I have the issue with the recovery screen being scrambled. Switched to another tv got through recovery and installed rom, then the screen would be blank when booting to system. After 2 hours of reading and trying.... Went back to the original tv , the tv recognizes the home screen display. Apparently whatever the issue with the recovery screen is prevented the home screen from being visible on the second tv. anyway all good now!
TorqueWrench001 said:
Success!! I have the issue with the recovery screen being scrambled. Switched to another tv got through recovery and installed rom, then the screen would be blank when booting to system. After 2 hours of reading and trying.... Went back to the original tv , the tv recognizes the home screen display. Apparently whatever the issue with the recovery screen is prevented the home screen from being visible on the second tv. anyway all good now!
Click to expand...
Click to collapse
i think someone else had the same issue and i think it was the tv lol
what do you have the fire tv set to in the display settings? If you had it set to a certain setting such as 1080p but the tv is in a different setting could be the issue.. or something like that lol
5.0.5_r1 installed perfectly
krawhitham said:
5.0.5_r1 installed perfectly
Click to expand...
Click to collapse
how did you install....did you update recovery first then flash 5.05_r1?
thanks
TorqueWrench001 said:
Success!! I have the issue with the recovery screen being scrambled. Switched to another tv got through recovery and installed rom, then the screen would be blank when booting to system. After 2 hours of reading and trying.... Went back to the original tv , the tv recognizes the home screen display. Apparently whatever the issue with the recovery screen is prevented the home screen from being visible on the second tv. anyway all good now!
Click to expand...
Click to collapse
elliwigy said:
i think someone else had the same issue and i think it was the tv lol
what do you have the fire tv set to in the display settings? If you had it set to a certain setting such as 1080p but the tv is in a different setting could be the issue.. or something like that lol
Click to expand...
Click to collapse
Someone in the comments of my guide said the scrambled screen issue was due to incompatibility with 1080i TVs. I'm curious @TorqueWrench001 is your scrambled TV a 1080i set that's not capable of 1080p ?
AFTVnews.com said:
Someone in the comments of my guide said the scrambled screen issue was due to incompatibility with 1080i TVs. I'm curious @TorqueWrench001 is your scrambled TV a 1080i set that's not capable of 1080p ?
Click to expand...
Click to collapse
Mine is a 1080i tv. Old sony bravia. Great picture and sound though. The display is most definitely tits up on twrp. However, I have a broken tiny cheap wall mounted 1080i flatscreen, with no sound, which is now my dedicated 2nd aftv monitor, just for twrp purposes. It even fits snug under my living room tv unit out of sight.
I am awaiting funds for a new samsung curved 55inch beast. But, I think it will have to wait until the sony bravia dies on me! lol
Hi
I received the OTA Update from Jan. (20 MB) If i accept the download and install it, i receive just an error (that robot picture).
I have a rooted pixel C.
I assume the root might be the problem.
Can i download that update and install it via adb sideload?
I only found complete images.
br & tnx for the help
I've been trying to root my device for a few days. I patch the AP file with the magisk application in the software I downloaded from the sammobile site with magisk. I installed it on my phone with odin. but above the samsung text, under the exclamation mark, the red color ''this phone is not running samsungs official software. you may have problems with features or security, and wont be able to install seoftware updates'' remains. The phone turns off after a certain period of time, it seems to turn on, but the same screen appears again and so on. Also, I enter the recovery mode, I do a wipedata/factory reset and it says something like this.
Wiping data...
Formatting /data...
[PDP] lstat /c___/pdp_b___ :0 - no Pdp scenario
formatting /cache...
formating /metadata
data wipe complete
[libfs__mgr]eariError updating for slot select
nothing?
Rooting a device's Android is adding a suitable su cmdlet to Android's filesystem and make it executable, nothing else. This can get achieved by means od ADB.
same issue here - bootloop after patching boot.img with Magic. B
ut new version - 24 is relased today to open beta channel. Maybe?
Succesfully patched boot.img from M526BPUU1AUI5 with latest Magisk Manager, flashed with ODIN and after wipe got rooted M52 (m-m52b/ds). You must patch exactly your firmware version boot. Also, flashing empty vbmeta disables verity protection - needed for custom recovery flashing. My goal now is to make TWRP working, but no success so far.
See here for root
GALAXY M52 5G - UNLOCK AND ROOT
Unlock and Root Galaxy M52 5G I just share my experience. Do it at your own risk Tested on M526BRXXU1AUK2 firmware I. Unlock bootloader 1. Enable developer options by tapping build number 7 times 2. Go to Developer options, turn on OEM...
forum.xda-developers.com
ThinRom A13
Based on Android 13 N986B N986BXXS5GWB1 February 2023 firmware
Supported Devices: Note 20 Ultra N986B N985F
The "NEW" ThinROM now has a full option off apps to debloat in the aroma, along with fullscreen/halfscreen in call mods, system mods, build.prop mods and alot more!!!
The code is highly optimised and the battery consumption and fluidity has seen a huge increase along with over all performance.....
ROM Features
Supported devices: N986B N985F
Stock Samsung kernel
CSC features: camera shutter sound menu, real time network speed in statusbar, etc
Knox partially removed and full debloat options
Removed dm-verity, automatic encryption, proca & vaultkeeper services
Build.prop tweaks
Warning boot screen removed, custom boot animation
Automatic EFS backup
Full aroma debloat options
Not working
knox related apps: Samsung Pay,
February A13 v7
February 2023 patch level N986BXXS5GWB1
Added option of full or half screen caller in aroma
New build.prop mods
Added different Magisk options in aroma
Fixed Android Auto not working
Fixed a few typos in flashing scripts
December A13 v5/v6
January 2023
Completely forgot to post here due to being Ill over the holiday period
December A13 v4
December 2022 patch level N986BXXS5GVK9
New full debloat options in Aroma
Added b2k Mod
Added Full screen caller mod
Highly optimised build for a smoother experience, better performance and better battery
New ThinROM Boot logo and wallpapers. Choice of White or Blue
New Software info in phone settings
November A13 v3
nOVEMBER 2022 patch level N986BXXU5GVK4
New full debloat options in Aroma
Added b2k Mod
Added Full screen caller mod
Highly optimised build for a smoother experience, better performance and better battery
New ThinROM Boot logo and wallpapers
November A13 v2
November 2022 patch level N986BXXU5GVK1
New full debloat options in Aroma
Added b2k Mod
Optimised build for a smoother experience
November A13 v1
November 2022 patch level N986BXXU5GVJE
Updated magisk to v25105
New aroma splash
New boot animation
ThinROM wallpaper applied automatically when installing clean
Changelog October v1.5
October 2022 patch level N986BXXS5FVI5
Updated magisk to v25105
New aroma splash
New boot animation
ThinROM wallpaper applied automatically when installing clean
Changelog July v1.8
July 2022 patch level N986BXXS4FVG1
Updated magisk to v25101
Changelog June v1.7
June 2022 patch level N986BXXS4FVEA
Updated magisk to v25001
Changelog May v1.6.1
May2022 patch level N986BXXU4FVE7
Updated magisk to v24312
Changelog May v1.6
May2022 patch level N986BXXS3FVD6
Updated magisk to v24309
Changelog April v1.5
April 2022 patch level N986BXXU3FVC8
Updated magisk to v24306
Changelog March v1.4
Updated to ONEUI 4.1
March 2022 patch level N986BXXU3FVC5
Updated magisk to v24303
Changelog March v1.3
March 2022 patch level N986BXXU3EVB1
Added all CSC mods by default
Changelog v1.2
Unreleased (Personal build)
Changelog v1
Unreleased (Personal build)
Credits
- John Wu for Magisk
- Mr. Waehere for CRB kitchen
- corsicanu for N20 TWRP
- aliwaris for incallui mods
- dutchman89 for the new boot animation
- Alan Thomas for sammy disarm script
- All testing team
- @starbucks2010 for helping me from day one and still doing so
- All people who helped me with ROM (especially to @starbucks2010 @ZonalRipper and @aaatso)
Download Links
Official TWRP
Installation procedure
IS MANDATORY TO BE ON ANDROID 13 FW BEFORE FLASHING ThinROM !!!
0) Backup ALL your important files to PC, ext drives, etc
1) Download and copy the latest ThinROM zip into your external storage or USB stick if you're on stock fw encrypted
2) Download GWB1 stock FW for your phone model using Frija or Samfw and unpack it on your PC
3) Boot in download mode (Vol Up + Vol Down + plug the USB cable connected already to PC) and load up Odin on PC
Don't use USB adapters otherwise you might get issues flashing FW in Odin
Turn off Auto Reboot in Odin
4) Select files BL, AP, CP & HOME_CSC (keep data)
**do not start flash yet
5) Download latest compatible TWRP for your specific device from the official TWRP xda thread (link above), rename it to recovery.img. Download the patched vbmeta.img file from above and rename vbmeta.img. Using 7Zip app add the 2 files (recovery.img and vbmeta.img) into a .tar file.
6) Add the above twrp + vbmeta patched.tar file into the USERDATA slot in Odin
7) Uncheck the auto reboot option in Odin and start the flashing
8) When flashing completes (keep usb plugged in !!!), hold Vol Down + Power buttons and then as soon as the screen goes black hold Vol Up + Power buttons to boot to recovery
*be warned first time you boot into recovery it will initialize and then reboot so just keep the buttons Vol Up + Power buttons pressed longer
**if you boot in stock FW, your data will be encrypted and you'll need to wipe your data before flashing ThinROM
9) When boot in TWRP, wipe your data if you're encrypted, flash ThinROM zip and then reboot to system
10) After the first boot, open Magisk Manager and reply with YES (agree to reboot) after MM have setup your root environment
*after reboot, go to Magisk Manager settings and toggle On Zygisk
10) Enjoy....
1. Backup to PC all your important files: documents, pictures, contacts, SMS, etc. BEFORE starting to flash anything
2. If you have issues booting the ROM, try the clean flash
3. To boot into TWRP you need to use a USB cable connected to PC (same for DL mode) or a USB stick
4. If you like my work, consider buying me a coffee.
Enjoy!
Great human, great rom creator.
Respect.
To make less stupid questions, please read before asking
Does secure folder and call recorder work?
manngoooo9 said:
Does secure folder and call recorder work?
Click to expand...
Click to collapse
Call recorder doesn't for me but a tester said it did for him and no, secure folder isn't included.
Any chance of snapdragon support?
elmor0 said:
Any chance of snapdragon support?
Click to expand...
Click to collapse
Unfortunately not.
Fist post updated to latest FW that's based on ONEUI 4.1
Bravo.
Everything is perfect.
Flying like Ferrari.
Thank you!!!!
Does using this rom cause loss of warranty?..
Also for my region there is only EVA9. Will there be any issues using EVA9 over the absence of EVB1?
Fist post updated to April FW.
aloysius987 said:
Does using this rom cause loss of warranty?..
Also for my region there is only EVA9. Will there be any issues using EVA9 over the absence of EVB1?
Click to expand...
Click to collapse
It will void warranty in certain countries but that's for you to check. Please download the latest FW for DBT and then the rom will flash just fine.
Respect, Maestro
Hi @sevsman,
is Dex working in this rom or it is removed too? Thank you for response
Mitoush said:
Hi @sevsman,
is Dex working in this rom or it is removed too? Thank you for response
Click to expand...
Click to collapse
It's been removed mate.
sevsman said:
ThinRom V1.4
Based on Android 12 N986B XXS3FVC5 firmware
Supported Devices: Note 20 Ultra N986B
This is an MPB (my personal build) that is heavily debloated and has pretty much only edge panels left in it. Everything that could be removed safely (except edge panel) has been removed however system apps like camera, calandar, calculator, play store etc are still included.
The aroma only has a choice of clean or dirty and will automatically flash a full screen caller mod, boot animation and all available csc mods.
The rom is only 2.97gb in size and because it's my personal build I will not be adding things back into it.
If you're after an extremely light rom that's optimised for speed and battery then this is for you!
ROM Features
Supported devices: N986B (N20 Ultra)
Stock Samsung kernel
CSC features: camera shutter sound menu, real time network speed in statusbar, etc)
Knox fully removed and ROM light debloated
Screenshots in secure apps allowed
Removed dm-verity, automatic encryption, proca & vaultkeeper services
Build.prop tweaks
Warning boot screen removed, custom boot animation
Automatic EFS backup
For Safetynet use kdrag0n patch v2.2.x
Not working
Some knox related apps: Samsung Pay, Samsung AutoFill
Changelog v1.5
April 2022 patch level N986BXXU3FVC8
Updated magisk to v24306
Changelog v1.4
Updated to ONEUI 4.1
March 2022 patch level N986BXXU3FVC5
Updated magisk to v24303
Changelog v1.3
March 2022 patch level N986BXXU3EVB1
Added all CSC mods by default
Changelog v1.2
Unreleased (Personal build)
Changelog v1
Unreleased (Personal build)
Credits
- John Wu for Magisk
- Superr for kitchen
- Ian Mcdonald
- anan1211 for watchdog fix
- aliwaris for incallui mods
- dutchman89 for the new boot animation
- @starbucks2010 for helping me from day one and still doing so
- All people who helped me with ROM (especially to @starbucks2010 @ZonalRipper and @aaatso)
Download Links
Telegram link
N986B ROM Link
TWRP + VBMETA
Volume booster
Installation procedure
0) Backup ALL your important files to PC, ext drives, etc
1) Download and copy the latest TR ROM zip into your external storage or USB stick if you're on stock fw encrypted
2) Download latest EVB1 stock FW for your phone model and unpack it on your PC
3) Boot in download mode (Vol Up + Vol Down + plug the USB cable connected already to PC) and load up Odin on PC
Don't use USB adapters otherwise you might get issues flashing FW in Odin
Turn off Auto Reboot in Odin
4) Select files BL, AP, CP & HOME_CSC (keep data)
**do not start flash yet
5) Download Android 12 compatible TWRP (For-odin-twrp-c2s-3.6.0_11-A12-1a7_ianmacd+vbmeta.tar) from above link.
6) Add the above twrp + vbmeta patched.tar file into the USERDATA slot in Odin
7) Uncheck the auto reboot option in Odin and start the flashing
8) When flashing completes (keep usb plugged in !!!), hold Vol Down + Power buttons and then as soon as the screen goes black hold Vol Up + Power buttons to boot to recovery
*be warned first time you boot into recovery it will initialize and then reboot so just keep the buttons Vol Up + Power buttons pressed longer
**if you boot in stock FW, your data will be encrypted and you'll need to wipe your data before flashing ThinROM 4.x
9) When boot in TWRP, wipe your data if you're encrypted, flash TR 1.x zip and then reboot to system
10) After the first boot, install Magisk Manager if necessary; when you'll start Magisk Manager for the first time, reply with YES (agree to reboot) after MM have setup your root environment
*after reboot, go to Magisk Manager settings and toggle On Zygisk
10) Enjoy....
1. Backup to PC all your important files: documents, pictures, contacts, SMS, etc. BEFORE starting to flash anything
2. If you have issues booting the ROM, try the clean flash
3. Starting with Android 11, to boot into TWRP you need to use a USB cable connected to PC (same as DL mode) or a USB stick
4. If you like my work, consider buying me a coffee (PayPal link)
Enjoy!
Click to expand...
Click to collapse
Hi,
I followed the steps, but my phone memory is -250gb, how to fix that ?
Thanks
triconix555 said:
Hi,
I followed the steps, but my phone memory is -250gb, how to fix that ?
Thanks
Click to expand...
Click to collapse
Can you post a SS because I don't really understand what you're saying mate.
How is battery in this ROM compared to stock?
Banking apps working?
Banking apps work fine as long as you know how to use zygisk and battery is different for every user but for me it is alot better.
First post updated with May firmware.
I love this ROM. One thing is bugging me as I use two SIMs and nned two accounts on WhatsApp but Dual Messenger option is greyed out, how to enable it