Fire TV Stick 2 (tank) Prerooted Stock Images [5.2.7.3_r1] - Fire TV Android Development

As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might.
First, you must be unlocked. You can follow the instructions here for making that happen.
If you are first starting, you should first unlock, then install this ROM, and THEN install Magisk for root or any other addons. This rom uses addon.d to preserve Magisk and any other addons, but any system modifications like Magisk, gapps, etc, that you have installed prior to this ROM will NOT be preserved.
If you've already unlocked and installed Magisk, then after installing this ROM you need to reinstall Magisk in TWRP.
Beyond that, Magisk and any other addons will be preserved as you flash newer roms. Consequently, if you would like to remove root, you will need to wipe /system in TWRP prior to installing this ROM. That will prevent it from being restored when installing the ROM.
WARNINGS
It is extremely important you never reboot after a failure. If recovery is hung, you can use adb shell to run
Code:
killall recovery
to restart it
It is also extremely important to never reboot after wiping /system.
If you wind up bricking, you will most likely have to follow the original unlock instructions again to get it recovered.
Thanks to @k4y0z, @xyz`, and @hwmod for the unlock.
Changelog and Downloads:
July 4, 2020 - 5.2.7.3_r1 (md5sum: 14c6ccb4ffb26418a84ef7ad6322ab01)
December 7, 2019 - 5.2.7.2_r3 (md5sum: c66d3128ab8b99f2f05aefed5ef7a527)
November 10, 2019 - 5.2.7.2_r2 (md5sum: 975b85849203555b924dd7facc96056c)
October 26, 2019 - 5.2.7.2_r1 (md5sum: f06045a91283f22ba5e2458e20036987)
September 21, 2019 - 5.2.7.1_r1 (md5sum: dcb2ec970f0f2937ef53bf6f4c824c28)
June 29, 2019 - 5.2.7.0_r1 (md5sum: ba6ca5312053628d4fc84d34b7c6cfd5)
March 30, 2019 - 5.2.6.9_r1 (md5sum: ff7669e329244dfebee2968777a37fc7)
March 17, 2019 - 5.2.6.8_r1 (md5sum: 8b68a96e4d6b908ddc9ee565d2ec2929)

very nice thank you very much!,
may i nicely ask if 5.2.6.9 could be also on your list?
https://forum.xda-developers.com/showpost.php?p=79075348&postcount=174

SoulInfernoDE said:
very nice thank you very much!,
may i nicely ask if 5.2.6.9 could be also on your list?
https://forum.xda-developers.com/showpost.php?p=79075348&postcount=174
Click to expand...
Click to collapse
It seems like 5.2.6.9 may have been put on hold by Amazon. Last I checked, it's not being pushed to any other device and I don't think it's actively being pushed to most tanks.

To be clear on this part of the first post;
rbox said:
This rom uses addon.d to preserve Magisk and any other addons, but anything you've installed prior to this ROM will NOT be preserved.
Click to expand...
Click to collapse
Installing this ROM will wipe our data, and the stick will be as new on the first boot. Except for anything we else have installed after the ROM in TWRP?

rbox said:
It seems like 5.2.6.9 may have been put on hold by Amazon. Last I checked, it's not being pushed to any other device and I don't think it's actively being pushed to most tanks.
Click to expand...
Click to collapse
My "tank" did recieve 5.2.6.9 am i good to roll back to your rom? And is there anything that would be useful that i could dump off of mine while it is on 5.2.6.9?

2WhlWzrd said:
To be clear on this part of the first post;
Installing this ROM will wipe our data, and the stick will be as new on the first boot. Except for anything we else have installed after the ROM in TWRP?
Click to expand...
Click to collapse
No. I meant system modifications like gapps or magisk. I'll make it a little clearer.

2FrEsH99 said:
My "tank" did recieve 5.2.6.9 am i good to roll back to your rom? And is there anything that would be useful that i could dump off of mine while it is on 5.2.6.9?
Click to expand...
Click to collapse
Yes, I've heard other people rolled back to .8 just fine. No. I have the .9 rom, I'm just waiting to see if they issue a new one or start rolling it out in force.

rbox said:
Yes, I've heard other people rolled back to .8 just fine. No. I have the .9 rom, I'm just waiting to see if they issue a new one or start rolling it out in force.
Click to expand...
Click to collapse
Alright cool man. I appreciate it.

it say prerooted. but had to install magisk and manager apk. what does this mean? it will stay rooted forever? like when update or factory reset? do ota updates work? the small ones or full update. be still root? or will update by new flashing new rbox rom update.

Hey @rbox thanks for everything including this new prerooted rom.
My question: is there a difference between firmware for the second gen stick and the Fire Stick 'Basic Edition', or are all the differences set server-side by Amazon? As far as I know it's the same hardware, but different software loaded on the device, depending on the device (but not the hardware?)

Fire TV Stick Basic (tank) post 5.2.6.9 incremental updates
rbox said:
Yes, I've heard other people rolled back to .8 just fine. No. I have the .9 rom, I'm just waiting to see if they issue a new one or start rolling it out in force.
Click to expand...
Click to collapse
I can confirm that the 5.2.6.9 OTA update seems to be in "on-hold" state.
I downgraded my stick to 5.2.6.8 since a week ago and I haven't been able to update to 5.2.6.9 in this week.
Also of note the fact that it seems Amazon is going to start again with incremental updates instead of full package updates.
I notice that after the first-time update to 5.2.6.9 I have received 19 incremental updates (files in .apk format) which I carefully captured just in case.
Attached to this message I uploaded the complete set of the 19 files update grouped in 2 different sets (apk1 and apk2).
The first set was found in the /cache directory while the second set was captured from /sdcard/Android/data/com.amazon.device.software.ota/files/.
Here is the file list preview of contents found in the linked archive:
Code:
Length Date Time Name
--------- ---------- ----- ----
19689856 02-17-2019 14:06 apk1/15.17.3.1.0.DigitalMusicAndroid3P-fireOS-partner-release-signed.apk
76775507 02-17-2019 14:07 apk1/AlexaMobileAndroid-2.2.237036.0-prodPhoenix-armeabi-v7a-release-signed.apk
21624784 02-17-2019 14:07 apk1/ATVAndroidFOS5TabletClient-release-prodSigned_241062110.apk
26805735 02-17-2019 14:07 apk1/com.amazon.gallery-fireTablet-release-signed-536543210.apk
13155243 02-17-2019 14:07 apk1/FreeTimeApp-fireos-fireos-release-signed.apk
11480109 02-17-2019 14:07 apk1/MASClientPlatter-tabletFos5-release-signed111.apk
3333353 02-17-2019 14:07 apk1/MayDayApk-fireOs-release-user-signed.apk
11613292 02-17-2019 14:06 apk1/OOBE-armeabi-v7a-release-signed_3.apk
598325 02-17-2019 14:07 apk1/signed_Cloud9ContentService-release.apk
7772927 02-17-2019 14:07 apk1/signed_DadetAndroidClient-fireOS5-release.apk
49037037 02-17-2019 14:07 apk1/signed_KindleForAmazonTablet-fos-release-14.15.136_1224836010_1.3.203908.0.apk
3489261 02-17-2019 14:07 apk1/signed_KindleStoreAPKv2-app-tablet-fireOS5-release.apk
1281070 02-17-2019 14:07 apk1/signed_NIMH-release1.apk
9296991 02-17-2019 14:07 apk1/signed_UnifiedSearchGen7-release_701.apk
6445765 02-17-2019 14:14 apk2/AudibleFireTabletApp-release-signed-2060150110.apk
50597344 02-17-2019 14:14 apk2/com.amazon.cloud9.apk
6495028 02-17-2019 14:14 apk2/com.amazon.cloud9.kids.apk
8032262 02-17-2019 14:14 apk2/FireLauncher5-release.apk
22877139 02-17-2019 14:14 apk2/MShopAndroidPhoneApp-16.0.222504.0-firefly-release-releasesigned.apk
--------- -------
350401028 19 files
Download post_5.2.6.9_incremental_updates.zip for Fire TV Stick Basic (tank)
Have fun.
.:HWMOD:.

xenyz said:
Hey @rbox thanks for everything including this new prerooted rom.
My question: is there a difference between firmware for the second gen stick and the Fire Stick 'Basic Edition', or are all the differences set server-side by Amazon? As far as I know it's the same hardware, but different software loaded on the device, depending on the device (but not the hardware?)
Click to expand...
Click to collapse
I don't know what the Basic Edition is. @AFTVnews.com, do you know?

xenyz said:
Hey @rbox thanks for everything including this new prerooted rom.
My question: is there a difference between firmware for the second gen stick and the Fire Stick 'Basic Edition', or are all the differences set server-side by Amazon? As far as I know it's the same hardware, but different software loaded on the device, depending on the device (but not the hardware?)
Click to expand...
Click to collapse
rbox said:
I don't know what the Basic Edition is. @AFTVnews.com, do you know?
Click to expand...
Click to collapse
From what I understood, the basic-edition is the same hardware but comes without Alexa.

k4y0z said:
From what I understood, the basic-edition is the same hardware but comes without Alexa.
Click to expand...
Click to collapse
If it's the same hardware, then it's very likely you'd be able to flash a tank software build on it. But I wouldn't recommend trying that unless there was a stock amazon image you'd be able to flash back to incase something bad happens.

hwmod said:
I can confirm that the 5.2.6.9 OTA update seems to be in "on-hold" state.
I downgraded my stick to 5.2.6.8 since a week ago and I haven't been able to update to 5.2.6.9 in this week.
Also of note the fact that it seems Amazon is going to start again with incremental updates instead of full package updates.
Click to expand...
Click to collapse
It also could be that the most notable change to the interface, the app pinning feature. Seems to viewed by a lot of users as an epic fail.
Maybe they are rethinking the change.

rbox said:
I don't know what the Basic Edition is. @AFTVnews.com, do you know?
Click to expand...
Click to collapse
Fire TV Stick Basic Edition is identical hardware to Fire TV Stick 2 "Tank". I see no reason why the tank ROM would not work on the Basic Edition stick.
The main issue is that Basic Edition Sticks have different system apps (or possibly just a flag set somewhere with the same system apps), such as Amazon Video, which are meant to be used by international Amazon accounts. If someone flashed a US rom on a Basic Edition stick, there is a chance they will no longer be able to access Amazon Video (and other default services/features) using their international Amazon account. They might not even be able to log into the device with an international Amazon account.
Worst case scenario, as I see it, is if you flash a US tank rom on a Fire TV Edition Stick (codenamed "Dozer", btw), you basically turned it into a US stick and need to now deal with the consequences of using US hardware abroad. I don't know what all of those consequences are.

AFTVnews.com said:
Fire TV Stick Basic Edition is identical hardware to Fire TV Stick 2 "Tank". I see no reason why the tank ROM would not work on the Basic Edition stick.
The main issue is that Basic Edition Sticks have different system apps (or possibly just a flag set somewhere with the same system apps), such as Amazon Video, which are meant to be used by international Amazon accounts. If someone flashed a US rom on a Basic Edition stick, there is a chance they will no longer be able to access Amazon Video (and other default services/features) using their international Amazon account. They might not even be able to log into the device with an international Amazon account.
Worst case scenario, as I see it, is if you flash a US tank rom on a Fire TV Edition Stick (codenamed "Dozer", btw), you basically turned it into a US stick and need to now deal with the consequences of using US hardware abroad. I don't know what all of those consequences are.
Click to expand...
Click to collapse
thats correct, the basic edition is the international stick so if you have lets say an amazon prime subscription from Mexico, and you use that amazon prime account on a us stick wile been in Mexico it wont work its ip restricted, so unless you are not using any amazon ip related subscriptions i don't recommend using the us rom , (the basic edition its easily recognizable by its smaller controller )

@rbox so if I wipe system and then flash this rom and lose root can I just flash magisk to get root back or do I need to redo the unlock method again?

MysticFTW said:
@rbox so if I wipe system and then flash this rom and lose root can I just flash magisk to get root back or do I need to redo the unlock method again?
Click to expand...
Click to collapse
Just reflash magisk.

rbox said:
Just reflash magisk.
Click to expand...
Click to collapse
Great thank you.

Related

Pre-Rooted 51.1.4.3

If your not running 51.1.4.1_514013920+fixed from rbox's Prerooted Stock Images thread; do not bother to load this one.
No support will be offered if your firetv screws up.
With that said, I have been running this for the past few days without issue and thought I would make it available to those that want it.
bueller-51.1.4.3_514020320-my_rooted.zip (md5sum: f54cec620785b04d1fcd5a660b9a79ff)
BBB
Going Shoeless.
realbbb said:
If your not running 51.1.4.1_514013920+fixed from rbox's Prerooted Stock Images thread; do not bother to load this one.
No support will be offered if your firetv screws up.
With that said, I have been running this for the past few days without issue and thought I would make it available to those that want it.
bueller-51.1.4.3_514020320-my_rooted.zip (md5sum: f54cec620785b04d1fcd5a660b9a79ff)
BBB
Going Shoeless.
Click to expand...
Click to collapse
What kernel is included in this?
rbox said:
What kernel is included in this?
Click to expand...
Click to collapse
The one included with your 51.1.4.1 release.
BBB
Slightly sloppy.
Thanks
Anything new at all?
jarayn said:
Thanks
Anything new at all?
Click to expand...
Click to collapse
Nothing visually different. Seems to be just bug fixes. Seems snappier, but that might just be a cache wipe or a placebo effect. [emoji6]
BBB
Something Grandiose
Installed with no problems. rboxes exposed stuff still works.. Thanks for putting this out...
Working fine for me. Thanks!
thanks you for your work.
As a note to remind myself of how to install future updates:
Firetv: system, about, network, get IP address.
Computer: command prompt, adb connect (ip address), adb push (rom.zip or the name of the rom file) /sdcard/,
To check if the amazontv is downloading rom file: WIFI, open network and sharing center, change network adapter, WIfi, status
when it is finishes transfering (eta 10-15 mins): adb reboot recovery, connect usb keyboard, install zip, /0/, /sdcard/, (rom.ziop or the name of the rom file), restart system. Done.
Great work! Thank you. I will install this tonight. Quick question: Is it a requirement to have a fully unlocked bootloader or no?
I'm partially unlocked at the moment, but will fully unlock it if necessary. Just haven't gotten around to it.
Newbie_from_NJ said:
Great work! Thank you. I will install this tonight. Quick question: Is it a requirement to have a fully unlocked bootloader or no?
I'm partially unlocked at the moment, but will fully unlock it if necessary. Just haven't gotten around to it.
Click to expand...
Click to collapse
Full unlock is not necessary. Though, I did apply the full unlock to mine.
BBB
Growing Tight.
What benefits are there to installing this over the previous pre-root version? I'm setup rather nicely and don't want to risk rocking the boat.
xm41907 said:
What benefits are there to installing this over the previous pre-root version? I'm setup rather nicely and don't want to risk rocking the boat.
Click to expand...
Click to collapse
I will hold off until there is a release that justifies the installation. There are no added benefits of this release. I was hoping Miracast from the windows PC would work. that is one big benefit for the Microsoft world.
navigates said:
I will hold off until there is a release that justifies the installation. There are no added benefits of this release. I was hoping Miracast from the windows PC would work. that is one big benefit for the Microsoft world.
Click to expand...
Click to collapse
That's what I was figuring.
Does my firetv need to be rooted to use this ROM?
death_entry said:
Does my firetv need to be rooted to use this ROM?
Click to expand...
Click to collapse
Yes, how else would you manage it to get it running on there?
does it matter which version I'm currently on before upgrading?
superkevx said:
does it matter which version I'm currently on before upgrading?
Click to expand...
Click to collapse
Read the first line in the first post....
Hi, will this work on fire tv stick? what about efuse and all that stuff from amazon blocking root?
This is not for the Fire TV Stick

Android 7.1.1 now available --- [Dead Thread about Preview]

[Dead Thread about Preview]
See this thread for discussing rooting 7.1.1 : -
Root Android Nougat 7.1.1 -- [NMF26F] -- SuperSU v2.78 SR5
Factory Image!
Successfully used flashfire to flash above factory image, along with SuperSU v2.78 SR4 ( instead of everroot) and ElementalX 5.05
Flashed with Flashfire. Root intact. Haven't looked at anything else yet.
Tapatalk on Nexus 9
ritchea said:
Flashed with Flashfire. Root intact. Haven't looked at anything else yet.
Click to expand...
Click to collapse
Did you use everroot option of flashfire? Which is still using su v2.78 SR1? I thought we would have needed SR4 for 7.1.
I need to make some backups and probably will flash this version on Thursday!
Made backups today (23/11) and successfully flash it! OP update with links!
Yes.
Tapatalk on Nexus 9
I flashed it a few minutes ago over stock 7.0 without wiping data and it seems to be the fastes and smoothest experience I ever had with this device. Can't say much more and didn't try to root, but I switched a few times between my two users und it's still fast and smooth. After switching between my users for two times with 7.0 a reboot was much needed! :fingers-crossed:
Mine is stuck at booting animation. No idea why first time this has happened to me before. Or does it just take like 20 minutes on first boot or what?
I flashed it manually through fastboot like normal.
jaju123 said:
Mine is stuck at booting animation. No idea why first time this has happened to me before. Or does it just take like 20 minutes on first boot or what?
I flashed it manually through fastboot like normal.
Click to expand...
Click to collapse
20 minutes is too long. Have you tried to just power off then on? Sometimes, that's all it takes. It's happened to me but not for this flash.
Tapatalk on Nexus 9
seems way faster than 7.0 so far.... I just did a full reset on 7.0 a week ago and experience immediate lag after I installed my apps. I flashed the 7.1 dev image today and went through the same process. So far so good. I'll report back after a couple of weeks of usage.
Did anyone enrolled in the beta program get the OTA yet ?
Previously I got it the same day an announcement was made. Nothing received yet. As a matter of fact, I didn't even receive the November security update this month.. Never rooted, never modified.
Had to post. Clean flashed new preview , temp boot of twrp to flash latest SU (SR4) for root and set up as new device. Best google effort yet! No problems adjusting build prop to enable assistant and both Pixel and Nova Launchers are go as is new systemless option adaway. Couldn't help notice how responsive UI is and chrome is stable for me 4-5 tabs in using sites like fark.com and no/very few redraws after pushing the tablet with moderate demands. Looking forward to the December release, noticed USB charging was still fairly slow still, hopefully the batt life is ok too. Go Google, they might just catch up to Craig's AOSP version/kernel performance if they're not careful !
Completed clean flash this preview
Rootless with supersu 2.78 sr4
Disable some app not use, very smooth
the.teejster said:
Did anyone enrolled in the beta program get the OTA yet ?
Previously I got it the same day an announcement was made. Nothing received yet. As a matter of fact, I didn't even receive the November security update this month.. Never rooted, never modified.
Click to expand...
Click to collapse
Same here. My device is enrolled but no update. I had to manually flash the November update. I did wonder if it was anything to do with flashing custom Roms. I am on full stock Google image but no update yet.
I never flashed a custom rom on my N9 nor has it ever been rooted. Still haven't received Nov update nor the Beta program update.
If you flash a factory image then you are fully stock and you should receive all updates from google.
Gold Ribbed said:
Same here. My device is enrolled but no update. I had to manually flash the November update. I did wonder if it was anything to do with flashing custom Roms. I am on full stock Google image but no update yet.
Click to expand...
Click to collapse
Has anyone received the ota yet? Or is google only doing a factory image this time for some reason?
Just manually flashed the stock preview. Much better than the stock 7.0 which is virtually unusable . This preview is solid and stable..
One of the main benefits of enrolling in the beta program was to be able to get OTA updates and not lose your data. Other devices in the program have received the OTA. Disappointing that the N9 hasn't to this date.
Gold Ribbed said:
Just manually flashed the stock preview. Much better than the stock 7.0 which is virtually unusable . This preview is solid and stable..
Click to expand...
Click to collapse
the.teejster said:
One of the main benefits of enrolling in the beta program was to be able to get OTA updates and not lose your data. Other devices in the program have received the OTA. Disappointing that the N9 hasn't to this date.
Click to expand...
Click to collapse
You can flash factory images without affecting your data partition. It is called "dirty flashing" for a reason.
My device has been through loads of updates, + the previous Preview images, by that method!
Checkout "Flashfire" app!
Flashfire
Click to expand...
Click to collapse
is the most advanced on-device firmware flasher available for rooted Android devices.
Click to expand...
Click to collapse
I realize this is the wrong thread for this discussion but to conclude. I'm not rooted and choose not to go down that path. My last comment still stands.
corkiejp said:
You can flash factory images without affecting your data partition. It is called "dirty flashing" for a reason.
My device has been through loads of updates, + the previous Preview images, by that method!
Checkout "Flashfire" app!
Click to expand...
Click to collapse
the.teejster said:
I realize this is the wrong thread for this discussion but to conclude. I'm not rooted and choose not to go down that path. My last comment still stands.
Click to expand...
Click to collapse
It is also possible to flash factory images with fastboot without wiping data.
Flashfire is just a convenient app for doing it (with needing a computer) for people who are rooted.

[KERNEL] Stock Kernel + SafetyNet Patch

Stock Pixel/Pixel XL Kernel + SafetyNet Patch
Current version: android-9.0.0_r0.111
Suitable for build(s): August 2019
Suitable for devices(s): Pixel XL (marlin) | Pixel (sailfish)
I compiled the stock kernel for the Pixel/Pixel XL and applied the SafetyNet patch by sultanxda. The kernel name says marlin, but this also works on sailfish. Google just created one kernel that works on both sailfish (Pixel) and marlin (Pixel XL) devices.
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay and Netflix.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- This kernel is only for the builds listed above!!!! This will not work on any prior build.
- All stock features will work with this kernel (since it's just the stock kernel + patch).
- If you do not have an unlocked bootloader there is no need to use this kernel. It's exactly the same as the stock kernel, except with the addition of the SafetyNet patch.
- This will not prevent SafetyNet from tripping for other reasons, like rooting.
- This will not remove the "device corrupted" warning when the phone is turned on or rebooted.
Installation:
- Be prepared with backups or the factory image from Google in case you do something wrong
- Extract kernel from zip file
- Test with command: fastboot boot <filename>
- Flash with command: fastboot flash kernel <filename>
**WARNING**
If flashing this kernel for whatever reason ruins your device, I am not accountable. Use this at your own risk!
The current version will always be attached to this post. Older versions can be found HERE.
(shamelessly copied from Sakete's kernel for the Pixel/Pixel XL, which is no longer being maintained. Thanks for the inspiration, Sakete!)
Wow. I literally just compiled the patched kernel myself just now. What a ninja! While I'll be running my own, thanks for posting this so I didn't have to
For those who already downloaded the kernel, I checked and saw a new mr2.1 update so I've attached an updated kernel.
iissmart said:
For those who already downloaded the kernel, I checked and saw a new mr2.1 update so I've attached an updated kernel.
Click to expand...
Click to collapse
Mine is based on that but mr2 and mr2.1 have the same commit so I'm pretty sure it's the same kernel.
Cheers
I'm running a pixel on the nof27b build I don't really want to flash a new kernel would it be possible for you to make the patch a flashable zip
Cardflip said:
Mine is based on that but mr2 and mr2.1 have the same commit so I'm pretty sure it's the same kernel.
Cheers
Click to expand...
Click to collapse
Good catch, I didn't look that closely before recompiling but they are indeed the same. Oh well! Maybe I'll start going off of tag names instead of branches...
ipeedalil said:
I'm running a pixel on the nof27b build I don't really want to flash a new kernel would it be possible for you to make the patch a flashable zip
Click to expand...
Click to collapse
Curious - what difference is there between flashing a kernel using fastboot and using a flashable zip? Isn't the end result the same?
iissmart said:
Curious - what difference is there between flashing a kernel using fastboot and using a flashable zip? Isn't the end result the same?
Click to expand...
Click to collapse
I think he's asking for the patch itself to be a flashable zip so he can patch the boot image while it's already compiled and on the phone. Which AFAIK is impossible
We need one for the Non-Verizon models (N2G47E) & (N2G47J). This modified kernel is only for the Verizon version. If you can compile two more versions for Non-Verizon builds.
puertorecon said:
We need one for the Non-Verizon models (N2G47E) & (N2G47J). This modified kernel is only for the Verizon version. If you can compile two more versions for Non-Verizon builds.
Click to expand...
Click to collapse
I was thinking the same thing, That K is for the Verizon model. good to know.
puertorecon said:
We need one for the Non-Verizon models (N2G47E) & (N2G47J). This modified kernel is only for the Verizon version. If you can compile two more versions for Non-Verizon builds.
Click to expand...
Click to collapse
I'll look into it tomorrow!
Thank you.
puertorecon said:
We need one for the Non-Verizon models (N2G47E) & (N2G47J). This modified kernel is only for the Verizon version. If you can compile two more versions for Non-Verizon builds.
Click to expand...
Click to collapse
I believe the kernel would still work.
It looks like the same kernel is used among NHG47K, N2G47J, and N2G47E, so my patched one should work for all of them. I'll update the post.
I'm just curious... So assuming you have the Google version and the oem unlock switch is fuctional and turned on, if you are not intending to root the device why would you unlock the bootloader? I mean you can always unlock it if you want or need to root, right?
bobby janow said:
I'm just curious... So assuming you have the Google version and the oem unlock switch is fuctional and turned on, if you are not intending to root the device why would you unlock the bootloader? I mean you can always unlock it if you want or need to root, right?
Click to expand...
Click to collapse
In the past I would always root or install a custom ROM on my phone. I would like to with the Pixel, but I want to keep Android Pay since I use it almost daily and I haven't been satisfied with the root solutions I've seen for the Pixel so far. It seems like Google is doing a good job of making it difficult to root, given the three or four different ways to root a Pixel that I've seen. Also, with the advent of monthly security patches I would imagine it is a growing headache to unroot, flash the update, then re-root each month. Google has also done a great job with the stock experience on the Pixel that the reasons I'd root are fairly minor.
It's also just been a habit of mine that the first thing I do with a phone is to unlock the bootloader. I don't like the idea of artificially restricting full access to a device, whether it's software or hardware. Plus I don't have to deal with the silly anti-theft checks that people encounter when they wipe the phone and sell it legitimately (like with Swappa or eBay). There was also a time when Nexus phones would bootloop after receiving an OTA, and if you weren't already unlocked before the OTA hit you'd be stuck with a bricked phone.
iissmart said:
In the past I would always root or install a custom ROM on my phone. I would like to with the Pixel, but I want to keep Android Pay since I use it almost daily and I haven't been satisfied with the root solutions I've seen for the Pixel so far. It seems like Google is doing a good job of making it difficult to root, given the three or four different ways to root a Pixel that I've seen. Also, with the advent of monthly security patches I would imagine it is a growing headache to unroot, flash the update, then re-root each month. Google has also done a great job with the stock experience on the Pixel that the reasons I'd root are fairly minor.
It's also just been a habit of mine that the first thing I do with a phone is to unlock the bootloader. I don't like the idea of artificially restricting full access to a device, whether it's software or hardware. Plus I don't have to deal with the silly anti-theft checks that people encounter when they wipe the phone and sell it legitimately (like with Swappa or eBay). There was also a time when Nexus phones would bootloop after receiving an OTA, and if you weren't already unlocked before the OTA hit you'd be stuck with a bricked phone.
Click to expand...
Click to collapse
Ok, fair enough. As I said I was just curious as to the reasoning. But what do you mean by anti-theft checks? I've never sold a phone so I don't really run into anything like that. But if you ever did need to sell it and you could unlock it at a moment notice wouldn't that suffice? I have a Verizon model locked bl so this is all rather moot to my situation, but I do have a 5x that I can unlock if I had to. I like the idea of being able to toggle the oem switch even though I would still remain locked. Something about being able to flash a factory image that I like. Thanks for your reasoning. Not that I agree or disagree with you entirely hehe. Personally, I just like the security of not being able to access my data if it's ever lost or stolen, but I suppose a concerted effort would get in.
bobby janow said:
Ok, fair enough. As I said I was just curious as to the reasoning. But what do you mean by anti-theft checks? I've never sold a phone so I don't really run into anything like that. But if you ever did need to sell it and you could unlock it at a moment notice wouldn't that suffice? I have a Verizon model locked bl so this is all rather moot to my situation, but I do have a 5x that I can unlock if I had to. I like the idea of being able to toggle the oem switch even though I would still remain locked. Something about being able to flash a factory image that I like. Thanks for your reasoning. Not that I agree or disagree with you entirely hehe. Personally, I just like the security of not being able to access my data if it's ever lost or stolen, but I suppose a concerted effort would get in.
Click to expand...
Click to collapse
If a locked phone is wiped/factory reset then only the Google account that was previously on the phone is allowed to be added back to the device. Tons of people were selling Nexus phones when this change rolled out, and the people that bought the phones were unable to add their accounts even after factory resetting. By unlocking the bootloader it disables this restriction. Yeah, I could do it at the time of selling the phone but there's always a chance I'd forget if I got out of the habit of unlocking the bootloader.
I thought about it a lot - and I've never lost a phone before so I'm OK with having my phone accessible in that regard. If I lose my phone I'll have bigger issues (like 2FA locking me out of my accounts) anyway.
I'm on Verizon, but I intentionally bought the phone from Google just to be able to unlock the bootloader .
iissmart said:
If a locked phone is wiped/factory reset then only the Google account that was previously on the phone is allowed to be added back to the device. Tons of people were selling Nexus phones when this change rolled out, and the people that bought the phones were unable to add their accounts even after factory resetting. By unlocking the bootloader it disables this restriction. Yeah, I could do it at the time of selling the phone but there's always a chance I'd forget if I got out of the habit of unlocking the bootloader.
I thought about it a lot - and I've never lost a phone before so I'm OK with having my phone accessible in that regard. If I lose my phone I'll have bigger issues (like 2FA locking me out of my accounts) anyway.
I'm on Verizon, but I intentionally bought the phone from Google just to be able to unlock the bootloader .
Click to expand...
Click to collapse
I've seen the term 2FA bandied about. I presume that's what you're talking about regarding the lockout. So to clarify, if you don't have an unlocked bootloader you can't sell the device? That seems weird. How do you get your account off? If I gave the phone to my wife she can't add her account?
I've never lost a device either although I have smashed one of them disastrously. But now I have a lot more stuff on the device including some personal pics and videos, password files, banking app and of course AP. I actually think my reasoning was more of like there is so much hacking and theft going on that rather than take a chance let me see what it's like being locked like normal people. It's hasn't been bad at all so far as I'm sure you know since you're not really modded either. I get the OTA on another slot and while it's updating I can use the device and a simple reboot updates it. But the bigger reason is that I got a Verizon model (Pixel 32gb) for $240 and not the $650 the Google one would have cost. I'm not sorry although I will revisit that once the Pixel 2 is released. Black Friday is your friend. I would even have bought the Google Pixel for $350 if they had a deal but they didn't. With a fully functioning 5X I just couldn't justify the full price.
Hmm I extracted the file and used fastboot flash kernel kernel_marlin-3.18-nougat-mr2.img and it gives me an error "error: cannot load 'kernel_marlin-3.18-nougat-mr2.img"
coldconfession13 said:
Hmm I extracted the file and used fastboot flash kernel kernel_marlin-3.18-nougat-mr2.img and it gives me an error "error: cannot load 'kernel_marlin-3.18-nougat-mr2.img"
Click to expand...
Click to collapse
After extracting the file I just renamed it to sailfish-image and used that in the command fastboot flash kernel sailfish-image. Flashed fine.
Sent from my Pixel using XDA-Developers Legacy app

The Nexus 6P May build has been pulled?

The May 2018 updates are on Google's site, except for the 6P. Anyone know why?
This article says it's been pulled:
https://www.droid-life.com/2018/05/...ity-update-goes-live-for-nexus-pixel-devices/
The links are still active. I got them from here:
https://9to5google.com/2018/05/07/android-may-18-security-patch-pixel-nexus/
I downloaded the image yesterday but going to delete it.
The update was actually pushed to my device today by Google... but it won't install due to an E3005 error related to the modem. I'm not sure, though, if the issue is with this update or if it's something specific to my device.
SpookyTunes said:
The May 2018 updates are on Google's site, except for the 6P. Anyone know why?
This article says it's been pulled:
https://www.droid-life.com/2018/05/...ity-update-goes-live-for-nexus-pixel-devices/
The links are still active. I got them from here:
https://9to5google.com/2018/05/07/android-may-18-security-patch-pixel-nexus/
Click to expand...
Click to collapse
Thanks for the heads up. Have you flashed it?
new update was sucessfully installed on my nexus via official ota update
tropical cactus said:
Thanks for the heads up. Have you flashed it?
Click to expand...
Click to collapse
Not yet without knowing what the issue with it is. I may get brave on the weekend though
SpookyTunes said:
Not yet without knowing what the issue with it is. I may get brave on the weekend though
Click to expand...
Click to collapse
OPM2. Sounds a bit scary to me. I thought angler was only either 3 or 5. I haven't flashed it either.:laugh:
It appears to have a new radio 3.87 , maybe there are some problems with that
tropical cactus said:
OPM2. Sounds a bit scary to me. I thought angler was only either 3 or 5. I haven't flashed it either.:laugh:
Click to expand...
Click to collapse
What do these even mean?
If I have OPM3 can I flash OPM5? Vice versa?
Ofrine said:
What do these even mean?
If I have OPM3 can I flash OPM5? Vice versa?
Click to expand...
Click to collapse
Normally you should always use the same build if available. I'm on OPM3. OPM5 is a build specifically for Japanese carrier SoftBank. Attempting to flash OPM5 over OPM3 is a bad idea.
I believe OPM2 is a merge of OPM3 and OPM5. Perhaps if you had OPM5 it isn't liking the merged radio file but for me on OPM3 I was able to upgrade to the May OPM2 Nexus 6P build without issue.
I did a non-destructive factory image flash to get to OPM2. YMMV.
rhardy613 said:
Normally you should always use the same build if available. I'm on OPM3. OPM5 is a build specifically for Japanese carrier SoftBank. Attempting to flash OPM5 over OPM3 is a bad idea.
I believe OPM2 is a merge of OPM3 and OPM5. Perhaps if you had OPM5 it isn't liking the merged radio file but for me on OPM3 I was able to upgrade to the May OPM2 Nexus 6P build without issue.
I did a non-destructive factory image flash to get to OPM2. YMMV.
Click to expand...
Click to collapse
So you installed the may update?,how is it so far.
side-loaded the may ota file via adb and it seems to work a-ok so far... i had installed opm5 before as well via this method so perhaps there is some under the hood issue nobody has noticed yet...
Not Yet Available
If you go to the Android News blogspot it states that the Nexus 6P update is "Not Yet Available" ...
I'd post the link, but it says new members are not allowed for 10 days or something like that, sorry!
Installed may update using flashfire.seems fine to me so far.seems little faster,but could be cause of clean install,rooted and debloated also.when Google releases new update I will probably install that too.just curious why it was pulled,a bug,or was there something we got that we weren't supposed too??
I cant say for sure what the issue was but I know after I did the update phone worked fine but then I restarted the phone and it told me my Android System was corrupted and that I had to factory reset.
VersusMe_ said:
I cant say for sure what the issue was but I know after I did the update phone worked fine but then I restarted the phone and it told me my Android System was corrupted and that I had to factory reset.
Click to expand...
Click to collapse
So far still running good for me,no message when I reboot either.
I just realized that the power save mode is not functioning on my 6P and was before may OTA ( cannot be toggled and does not turn on below 15%) not a game-changer but could be why it was pulled or it could just be a hiccup on an aging device
Ugh, where the update?
I was holding of flashing till the release of the next security patch.
[email protected] said:
Ugh, where the update?
I was holding of flashing till the release of the next security patch.
Click to expand...
Click to collapse
My phone says it has the OTA, but as I did some system modifications, I need the factory image, which yet has to appear.
Have any of you installed from the first link? If so, how did that go? I wan to do the OTA, but I am a bit worried it will be corrupt or that it isn't the correct file.

Fire TV Stick 4K (mantis) Prerooted Stock Images [6.2.8.1_r3]

As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might.
First, you must be unlocked. You can follow the instructions here for making that happen.
If you are first starting, you should first unlock, then install this ROM, and THEN install Magisk for root or any other addons. This rom uses addon.d to preserve Magisk and any other addons, but any system modifications like Magisk, gapps, etc, that you have installed prior to this ROM will NOT be preserved.
If you've already unlocked and installed Magisk, then after installing this ROM you need to reinstall Magisk in TWRP.
Starting with 6.2.6.6, Magisk is always installed.
Beyond that, Magisk and any other addons will be preserved as you flash newer roms. Consequently, if you would like to remove root, you will need to wipe /system in TWRP prior to installing this ROM. That will prevent it from being restored when installing the ROM.
Thanks to @k4y0z and @xyz` for the unlock.
NEVER FLASH A STOCK ROM >= 6.2.8.0 AFTER FLASHING 6.2.8.1_r2 OR LATER! THIS WILL BLOW AN EFUSE.
Changelog and Downloads:
October 24, 2021 - 6.2.8.1_r3 (md5sum: 3795edc2d640932a88da39da8a0811c5)
July 17, 2021 - 6.2.8.1_r2 (md5sum: e9e37a2d485a3397df041938818421e9)
This includes updated tz firmware to fix the device locking up when trying to play video.
April 3, 2021 - 6.2.8.0_r1 (md5sum: 2efdfc5728caba2953a351a082023a59)
December 26, 2020 - 6.2.7.7_r1 (md5sum: b835e29bb29458004063121a422c1bf7)
May 3, 2020 - 6.2.7.1_r1 (md5sum: 56ec885e5bd258682c90e8f08371301d)
November 10, 2019 - 6.2.6.8_r1 (md5sum: 8cdc16239df36c8640004232918c5477)
October 19, 2019 - 6.2.6.6_r1 (md5sum: df8f3d033fddf66a1b4aa3a6b228196b)
Starting with this version, Magisk will always be installed.
This includes updated tz firmware to fix LICENSE_ERROR with Prime video.
October 13, 2019 - 6.2.6.5_r1 (md5sum: bdde0303d8db5495ac6dc2aaf476d2f4)
Awesome!! Thanks!!
@rbox,
Quick question,
Initial unlocking and rooting was successful. However, I did what I usually do which is update Magisk using the manager and after the reboot, it is looping @ the amazon image. Any idea?
vasir13 said:
@rbox,
Quick question,
Initial unlocking and rooting was successful. However, I did what I usually do which is update Magisk using the manager and after the reboot, it is looping @ the amazon image. Any idea?
Click to expand...
Click to collapse
From the unlock page:
Important information
Don't flash boot/recovery images from FireOS (FlashFire, MagiskManager etc.)
rbox said:
From the unlock page:
Important information
Don't flash boot/recovery images from FireOS (FlashFire, MagiskManager etc.)
Click to expand...
Click to collapse
Yes .... I know ... called selective reading .... I got into TWRP and will try your image now ...
Happy to see the pre-rooted roms from you on mantis! It's starting to feel like the good old days again
Thank you, I feel safer already.
Any idea what version of gapps would work on this? Also, any idea if installing nanodroid, patched playstore & patching the ROM for signature spoofing be dangerous (as in bugger up the BL/TWRP)?
Awesome. This community is great.
Does this work for european (Italian) Sticks? (Prime video, Alexa etc etc).
Regards and Thanks a bunch!
Hi,
I successfully installed the hacked bootloader and TWRP a few days ago, but I did not do anything else. I was still on the original 6.2.5.8 version.
Today I wanted to flash the prerooted 6.2.6.5 and I can't manage to boot it (and since I did not expect problems, I did not make a backup of the old system). I cannot go past the "firetv" boot logo and in this stage "adb logcat" is not yet working, so I don't see any logs.
First boot was just installing the ROM. Second boot with previously wiping Cache / Dalvik. Finally I wiped also data (and Cache/Dalvik again). I cannot get past the boot logo.
So what can I do? Was there a firmware update between 6.2.5.8 and 6.2.6.5, which I need and is not included in the prerooted image? I'm just guessing since I cannot explain anything else...
Thanks Tim
tehlers said:
So what can I do? Was there a firmware update between 6.2.5.8 and 6.2.6.5, which I need and is not included in the prerooted image? I'm just guessing since I cannot explain anything else...
Click to expand...
Click to collapse
Have you compared the md5 of the download (push the md5file + ROM and let TWRP check this during install)?
Sus_i said:
Have you compared the md5 of the download (push the md5file + ROM and let TWRP check this during install)?
Click to expand...
Click to collapse
Yes, I have checked MD5 on my notebook after download, but not after pushing the file to the stick. I will do that now and post it here (with edit). But I doubt this being the issue.
EDIT: MD5 of the zip in the stick is also ok.
tehlers said:
EDIT: MD5 of the zip in the stick is also ok.
Click to expand...
Click to collapse
Ok. The prerooted Rom should be a full stock update, rbox said that a few days ago.
Any hardware damages or missing parts on your stick?
Edit: Have you flashed the magisk.zip behind the ROM?
Sus_i said:
Ok. The prerooted Rom should be a full stock update, rbox said that a few days ago.
Any hardware damages or missing parts on your stick?
Click to expand...
Click to collapse
The hardware is fully ok. The installation of hacked BL worked very smoothly and the stick did work with the original firmware until I flashed the prerooted one today. I have two guesses, but I don't know how to proceed:
1. I know there are sometimes firmware updates on specific fire OS versions, which need to be installed for later versions (for example version 5.2.6.7 on fireTV 2 [sloane]). So if I need a firmware update for 6.2.6.5 (from 6.2.5.8) I should probably flash 6.2.5.8 back and let the fire OS do the first update.
2. Or there is something left from the old version (in one of the partitions) which prevents this version from booting. This would mean that you need to be already on 6.2.6.5 (or at least on a higher version than me), that this ROM works.
In both cases, I would probably recover when getting the original firmware version 6.2.5.8 from somewhere.
EDIT: As I said in the first post, I did not do anything with the original ROM, except flashing the hacked BL and TWRP, no Magisk or whatever.
Best
Tim
tehlers said:
The hardware is fully ok. The installation of hacked BL worked very smoothly and the stick did work with the original firmware until I flashed the prerooted one today. I have two guesses, but I don't know how to proceed:
1. I know there are sometimes firmware updates on specific fire OS versions, which need to be installed for later versions (for example version 5.2.6.7 on fireTV 2 [sloane]). So if I need a firmware update for 6.2.6.5 (from 6.2.5.8) I should probably flash 6.2.5.8 back and let the fire OS do the first update.
2. Or there is something left from the old version (in one of the partitions) which prevents this version from booting. This would mean that you need to be already on 6.2.6.5 (or at least on a higher version than me), that this ROM works.
In both cases, I would probably recover when getting the original firmware version 6.2.5.8 from somewhere.
Best
Tim
Click to expand...
Click to collapse
OK :good:
Have you installed the magisk.zip behind the rom? May be it won't start without that? You may try that...
May be that dm-verity and/or SELinux enforcing is a problem without magisk, as magisk take care of that automatically...
No mouse Emulator support in TWRP with the 4K stick?
How do you install the rom if you don't have USB OTG cable?
Sus_i said:
OK :good:
Have you installed the magisk.zip behind the rom? May be it won't start without that? You may try that...
May be that dm-verity and/or SELinux enforcing is a problem without magisk, as magisk take care of that automatically...
Click to expand...
Click to collapse
Yes, that's it. Magisk needs to be installed after the "prerooted" image! Now the stick boots up!
Amazing, thank's!
I thought a prerooted image is prerooted.
@rbox: It would be nice, if you could mention this in the first post.
T1inkering said:
No mouse Emulator support in TWRP with the 4K stick?
How do you install the rom if you don't have USB OTG cable?
Click to expand...
Click to collapse
for example with ADB / TWRP Commands, something like that...
Code:
adb push ~/Desktop/mantis-6.2.6.5-rooted_r1.zip /sdcard/
adb push ~/Desktop/Magisk-v19.3.zip /sdcard/
adb reboot recovery
adb shell
twrp install /sdcard/mantis-6.2.6.5-rooted_r1.zip
twrp install /sdcard/Magisk-v19.3.zip
twrp wipe cache
twrp wipe dalvik
reboot -p
tehlers said:
Yes, that's it. Magisk needs to be installed after the "prerooted" image! Now the stick boots up!
Amazing, thank's!
I thought a prerooted image is prerooted.
@rbox: It would be nice, if you could mention this in the first post.
Click to expand...
Click to collapse
It is mentioned.. but not thats an issue without flashing magisk
Sus_i said:
It is mentioned.. but not thats an issue without flashing magisk
Click to expand...
Click to collapse
That's what I mean. It's not mentioned that you need Magisk in any case (to boot the image as such *and* probably also to get root [which is not prerooted then?]).
Thanks again!
puppinoo said:
Awesome. This community is great.
Does this work for european (Italian) Sticks? (Prime video, Alexa etc etc).
Regards and Thanks a bunch!
Click to expand...
Click to collapse
I reply to myself and happy to confirm I installed this "generic" image to my US Stick 4K and after I accept terms of use *Italian* Alexa and Prime video seem to wotk fine.
If I remember well my previous image was the 6.2.5.8 (basically the one I installed when the exploit for Fire TV Stick 2 (Tank) was released but can't be 100% sure.
Now I have to try it on my *Italian* Stick 4k (bought on amazon.it).
Amazing and thanks a lot again.
Puppinoo.
So great to see @rbox 'es prerooted roms for the Fire TV Stick 4k
There are some things that I am not familiar with:
1. What is magisk for and what if I don't install it?
2. Does root not work without magisk?
On the older Fire TV Devices we did never have to install magisk or so and it was prerooted with rboxes roms and root was working. Why is everybody talking about magisk? Can magisk break anything or be critical like xposed was on the Fire TV 2 box? I remember that xposed framework was a pretty messy issue for recent Fire TV 2 (Sloane) pre-rooted roms. Magisk seems to go deeply into the system, similar to xposed framework, isn't it?

Categories

Resources