yashsingh1/xdaforums huggingface dataset:
[Nook Touch General] alexgs007:
Hi, i update my NST to version 1.2.2, and i rooted with NookManager, it was very simple, then i installed NTGAppsAtack, i had a google play application installed, but when i launch this app, an error ocurrs when it try to recover the google play terms of service, its can't load the page:

[IMG="google play terms"]https://pasteboard.co/IBQzZRH.png[/IMG]

I suppose for the string "%locale%". And for that reason i can't accept the terms, and the google play application can't start.

Any ideas? :confused:
[Nook Touch General] nmyshkin:
"Market" no longer works. Google ended support for Android 2.1 back in 2017.

Did you use the updated NTGAppsAttack: https://xdaforums.com/nook-touch/development/nst-g-updating-ntgappsattack-t3875957
[Android Q&A, Help & Troubleshooting] glaysonmestre:
my smartphone gave some problem in the software keys I thought of several possibilities to fix, I would like to literally turn the screen of my phone upside down I would like to do it in the root, that it was turned from boot to power would be possible? I would like to make that button that has three lines open the sliding menu these two modifications I would like to make someone can help me? my device is the lg g flex d956

https://youtu.be/FiW9mUXuOAY

http://prntscr.com/pitugf
[Tilt, TyTN II, MDA Vario III General] mrgoat:
I am using this theme as my today theme but for some reason my Cingular operator tag is showing up on top of the battery / volume / signal icons. Any tips on correcting this?

Also is there a way to use automatic profile switching with SPB mobile shell?
[Tilt, TyTN II, MDA Vario III General] bapssystupr3m3:
this issue has been asked before and please search the theme thread for the solution
[Tilt, TyTN II, MDA Vario III General] mrgoat:
i have searched but haven't stumbled onto the right keywords. Could you provide some insight or atleast a link?
[Tilt, TyTN II, MDA Vario III General] mrgoat:
i just used the operator personalizer and removed the operator all together.
[Xiaomi Redmi Note 4 Questions & Answers] prisoner1969:
So I bought a battery for my Mido and followed videos on youtube on replacing it. It all seemed to go well until I started to use my phone. The middle part of my screen doesn't register touches. I was able to install a touch screen test app and you can see that nothing is registering in the middle. Any Ideas? I've attached the screen shot.
[Xiaomi Redmi Note 4 Questions & Answers] T3sla:
Maybe it's software problem.If you have twrp installed check if the problem appear there too.If not then maybe it's indeed a software glitch.Then maybe you can try a factory reset or clean installation of the rom.

If that doesn't work maybe you can try reconnect the cables you had to disconnect during the battery change process and putting back the previous battery.Not an expert just some logical thoughts.
[Xiaomi Redmi Note 4 Questions & Answers] prisoner1969:
I'll test twrp in the morning. Doubt it'll be that. The only connectors I detached were the finger print sensor and battery. I hate prying my phone open. Was such a pain the first time. I'll have to open it up to see if maybe I knocked some other connection loose at all.
[Xiaomi Redmi Note 4 Questions & Answers] laneofmagic:
I am facing this exact same problem. Pretty much a vertical strip of screen on the right hand side of the screen is unresponsive for me. Screenshot: https://i.imgur.com/8Uqn2lp_d.jpg

I took the phone to the service center, while I had warranty. They pretty much said to my face that this kind of problem can pop up when you've dropped the screen too much and that I need to get the screen replaced to fix it.
[Moto G7 Power Questions & Answers] DustCore:
I noticed that there's now a TWRP recovery on TWRP's official app, but I just want to make sure I can root it before I buy it. I'm kind of a noob to rooting, but I haven't seen any posts about there now being a TWRP recovery. Any advice?
[Moto G7 Power Questions & Answers] sd_shadow:
Didn't need twrp to root.

Need to be able to unlock bootloader.

Stay a way from a branded phone like Verizon, AT&T and other carriers.
[Android Head-Units] ospanacar:
I bought a new Chinese radio with android that, as the box sais, has android 8.1,

with the system version: JCAC10H3-OB4-V1.0.04R6.

Also de MCU version is: JCST100M01-IA03V06.14-201907301757.

Kernel version: 3.18.79+

And my issue is about it own radio app, which every time I open it, it stays around a few seconds till it crash and ask for restart the app.
[Android Head-Units] Tbizzness:
I think the best thing to do would be contact the seller and explain the problem to them. If you can't use the radio because it constantly crashes you might as well remove it and exchange it for a different model.
[Android Head-Units] LoGeo:
Hello! I don't have any problems with the current firmware. I put a different launcher and a different music player. I haven't found the radio yet. The seller gave me the new firmware.
[Android Head-Units] emta43:
Hello, what latest firmware do You have?

Can You share it?

I have similar radio and the radio cannot remember setting: "Use GPS provided time." after power cycle. Every time only network provided time or MANUAL time setting is possible. I want to save setting GPS provided time.

Thank You
[OnePlus 7 Pro Questions & Answers] ktimque:
Can someone please link me or send a PM? I know someone has it, and the replies saying "patch your own" or "why use a patched boot image" aren't helpful.

Would really appreciate it, cheers.
[OnePlus 7 Pro Questions & Answers] shooterlgk:
[MENTION=1021666]vinoratheesh[/MENTION] was kind enough to share it with me, it's in the patched boot image forum.

https://drive.google.com/file/d/17dQzp1ClkLC18iHizmxbATKR8gS_AmmG/view

U just gotta patch it with magisk manager
[OnePlus 7 Pro Questions & Answers] ktimque:
Much thanks. Which forum?
[OnePlus 7 Pro Questions & Answers] vinoratheesh:
I extracted the boot image using Payload dumper. Yes you have to patch it in your phone.
[OnePlus 7 Pro Questions & Answers] ktimque:
Can someone please link/PM me? The one from the other thread broke my wifi. Would really appreciate it
[OnePlus 7 Pro Questions & Answers] valeriee:
What is a patched boot file? I'm on Android 10 without flashing it, do I need it? THanks
[Palm Treo 750] Evetsllub:
I have a Treo 750 (Telstra, Australia) and today decided to update to WM6.

I have it synced to my PC running Vista Ultimate. Did this just before the install, then ran the install and half way through it crashed. After resetting the Treo, it came up with the initial install screen (date/country/etc). After completing all this it went in and it was still WM5... so obviously the update failed. But all my settings are gone (including email/contacts/etc, which are still on my PC).

BUT, now the computer won't recognise it when i plug in via USB, so I cannot even sync all my stuff back to WM5, let alone install WM6.

I have had a read of these forums, and it seems that to do an installation through a SD card, you need to do some of the steps through sync first, so unless i can work out how to sync it, i think i am screwed. Can anyone help?

Thanks
[Fire TV Android Development] rbox:
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)
[Fire TV Android Development] asislife20:
Awesome!! Thanks!!
[Fire TV Android Development] vasir13:
[MENTION=3991724]rbox[/MENTION],

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?
[Fire TV Android Development] rbox:
From the unlock page:

Important information

Don't flash boot/recovery images from FireOS (FlashFire, MagiskManager etc.)
[Fire TV Android Development] vasir13:
Yes .... I know ... called selective reading .... I got into TWRP and will try your image now ...
[Fire TV Android Development] iLLNiSS:
Happy to see the pre-rooted roms from you on mantis! It's starting to feel like the good old days again :)
[Fire TV Android Development] TitanUranus:
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)?
[Fire TV Android Development] puppinoo:
Awesome. This community is great.

Does this work for european (Italian) Sticks? (Prime video, Alexa etc etc).

Regards and Thanks a bunch!
[Fire TV Android Development] tehlers:
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
[Fire TV Android Development] Sus_i:
Have you compared the md5 of the download (push the md5file + ROM and let TWRP check this during install)?
[Fire TV Android Development] tehlers:
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.
[Fire TV Android Development] Sus_i:
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?
[Fire TV Android Development] tehlers:
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
[Fire TV Android Development] Sus_i:
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...
[Fire TV Android Development] T1inkering:
No mouse Emulator support in TWRP with the 4K stick?

How do you install the rom if you don't have USB OTG cable?
[Fire TV Android Development] tehlers:
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. :)

[MENTION=3991724]rbox[/MENTION]: It would be nice, if you could mention this in the first post.
[Fire TV Android Development] Sus_i:
for example with ADB / TWRP Commands, something like that...

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

It is mentioned.. but not thats an issue without flashing magisk ;)
[Fire TV Android Development] tehlers:
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!
[Fire TV Android Development] puppinoo:
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.
[Fire TV Android Development] c3po_droid:
So great to see [MENTION=3991724]rbox[/MENTION] '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?
[Fire TV Android Development] WarrenDen:
Yes, please share you recipe. I have unlocked the stick, installed TWRP and whatever I do i still stuck at updating screen.
[Fire TV Android Development] rtdo:
Will this ROM (or any other after unlock) fix the error below or do we have to wait for a Amazon?

github.com/amzn/exoplayer-amazon-port/issues/94
[Fire TV Android Development] Michajin:
This is basically a stock rom, pre-rooted. I am curious, What is ExoPlayer and what is it used for?
[Fire TV Android Development] Cagnulein:
Is there a way to bypass the installation wizard on the very first startup?
[Fire TV Android Development] rbox:
As I suspected. The current 6.2.7.1 is different than the one at the end of March. So they must have pulled it and then issued a correction. I have updated the OP with 6.2.7.1.
[Fire TV Android Development] puppinoo:
Great news. Thanks as always.

I'd like to ask if people like me who always kept update blocked on router and on the device (disabling OTA binaries) need to do something additional to simply install this rom. I read elsewhere single apps updates are sent to the devices, which I could have missed.

Regards.

Pino.
[Fire TV Android Development] Sus_i:
If you're curious, update to the latest from rbox, then enable the ota update app with:

pm clear com.amazon.device.software.ota
pm enable com.amazon.device.software.ota

Click search for updates in settings.

You can watch with adb what is pushed to the stick (apk's and/or bin's) with

adb shell
su
cd /cache
ls

In case you want install that stuff, simply press update in settings, its safe (in case a full or partial OS *.bin update is loaded, the stick boots into TWRP if you let it reboot, no harm to the unlock as the stock recovery isn't there).

In case you don't want install anything

pm disable com.amazon.device.software.ota
pm clear com.amazon.device.software.ota

Then rm the files on /cache.
[Fire TV Android Development] puppinoo:
Thanks. Great tip.

If I don't want to install anything I can clear manually the /cache folder with something like rm * and disable OTA again?

Is it useful stuff (Since nobody seems to care about these updates)?

Regards.

Pino.
[Fire TV Android Development] Sus_i:
rm the files is enough and ofc disable/clear the updater.

Useful or not, idk, some people call it bloat, but if you have prime it isn't bad at all.
[Fire TV Android Development] raphael.e:
Thanks a lot!

Not sure what went wrong. I went to twrp and flashed your prerooted image and then rebooted my fire tv stick. Once started I went to Magisk and it looks like I lost root: Magisk not installed

I flashed the rom a second time in twrp and same issue. Hence I installed Magisk.zip manually in twrp and then I gained root again.
[Fire TV Android Development] chinkster:
If I flash this update, do I have to disable OTA updates again from ADB again?
[Fire TV Android Development] Sus_i:
That should be true if you wipe data too (not recommended).
[Fire TV Android Development] chinkster:
So as long as I flash over to new update, and don't wipe data, then I don't have to disable updates again?
[Fire TV Android Development] Sus_i:
Yeah :good:
[Fire TV Android Development] Flakie:
Thanks for providing this but after using it, with only a few apps installed, there is not enough space left for a full twrp backup on the stick.

All my others, with the stock image I rooted myself and setup identical have several hundred MB left after a backup.

Any reason why? Is anything else installed apart from magisk?
[Fire TV Android Development] T1inkering:
How can i use mouse emulator on ADBLink so i can press the right key to boot to recovery, can't remember how i used to achieve this..

edit: never mind, seems like i've asked this question before xD
[Fire TV Android Development] SpaceMan5:
Edited: Fixed it via otg.
[Fire TV Android Development] SoulInfernoDE:
[MENTION=3991724]rbox[/MENTION] any update about 6.2.7.3 - it's been a while outside and members confirm that this fixes some HD content playings. :)

Thank you very much for all your work!

br SoulInferno
[Fire TV Android Development] mattress:
//Edit:

Disregard. It seems the power supply I was using on the temporary test bench was too small. How embarrassing

Sorry for my ignorance nice been struggling with the software side of things. I’m getting a boot loop after the white fire loading screen

I was able to unlock the bootloader and install TWRP, using the 2 step process.

I wiped pretty much everything, and flashed the latest stock pre-rooted image from this thread mantis-6.2.7.1-rooted-r1 then wiping dalvik and cache again

After booting, I go through the initialization process, connecting to WiFi , etc,

I’m having an issue with the device trying to update during this process, and I think that’s causing me problems. I’m bootlooping. I tried cutting the internet connection before it checks for updates, but that method doesn’t seem to work anymore.

I don’t know if TWRP should be read-only or allow system access when it asks me.

I understand there are ways to use ‘adb shell pm’ commands to turn off ota updates, but I don’t know how to connect adb with anything other than IP address — and I can’t enable adb on the device until after the initialization process.

Can someone help explain how I connect my pc to the device to run twrp shell commands? Am I going about this the correct way?

Thanks for any info.
[Fire TV Android Development] SweenWolf:
Actually there are differences in some sticks, if you have a stick like mine then it doesn't matter what you do with the stick in TWRP it will not make any change to the /system partition.

I have not used any rooted images yet but you can use any unauthorized by editing boot.img.

You can use USB cable to connect your Stick to the PC and do things from there.

In TWRP you will see

System

System Image

Vender

Vender Image

You should wipe every partitions and only write to

System Image and Vender Image

And not on System and Vender, if you have anything on system and vender partition and have magisk patched boot images then your stick will bootloop.

Its a mess.
[Fire TV Android Development] mattress:
You seem very knowledgeable, and a lot of this stuff is over my head. Do you think you could explain like I’m 5 how to get out of boot loop ... at this point I don’t care if I’m rooted or not anymore. This hasn’t been fun lol

I’ve tried flashing pre-rooted, debloated, and stock many times
[Fire TV Android Development] SweenWolf:
Open twrp, wipe every partition. Reboot into trwp.

Flash any stock image (don't do anything, let it finish and reboot then wait. If you want Accessibility functions then flash 6271 image)

Remove any accessories and let it boot up, if it download any update (in the setup process) let it, when it finishes the setup, disconnects the internet, disable updates.

Your stick will be back to stock (partially)

https://xdaforums.com/showpost.php?p=81897273&postcount=1 (link to stock image, i recommend 6271)
[Fire TV Android Development] mattress:
How embarrassing. That ended up being my problem. The power supply I was using. with my otg cable and (unpowered) usb hub and a usb a-a cable to an iPhone charger brick
[Fire TV Android Development] KR_83:
Bootloop after flashing prerooted stock image and updating Magisk

Hi,

I opened my Fire 4K and shortened the pin, then I flashed the prerooted Stock Image 6.2.7.1_r1 and booted into FireOS. Magisk Manager informed me, that the prerooted image has Magisk v20.1 installed and there is an update available to Magisk v20.4

So I did update from within the Manager and did a reboot. As I learned afterwards that was stupid, should have downloaded the 20.4.zip instead and installed it via TWRP.

Now I'm stuck in boot loop (dark grey FireTV screen showing for 1 minute, then restarting). I cannot access TWRP, so I tried to start from scratch, opening the case and shortening the pin, but when I run the kamakiri bootrom-step.sh, it never continues but is stuck saying "Waiting for bootrom"

Dmesg also looks strange, it shows the stick is recognized as MT65xx Preloader from MediaTek, saying nothing about Amazon Fire (as I think it should). Please see attachment.

Any advice what I could do? Thanks a lot.
[Fire TV Android Development] l@nd1ng3ar:
Flash with a Factory Firmware

Have patience it works, you are not shorting properly, I had the same problem yesterday as I updated the Magisk, landed me in the black amazon logo, so start the process again, ensure you remove the foil carefully and once you do that make sure you push the factory firmware to the sdcard, go to twrp recovery and flash it.
[Fire TV Android Development] thecoonx:
deletet
[Fire TV Android Development] KR_83:
You're right, I was able to do that, thanks a lot!