yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S10e Questions & Answers] aug0211:
It would be very helpful and a life-changing safety enhancement for me to be able to remote view + control my son's S10e (he is age 6) when he is not with me, specifically for one app (Omnipod 5) to help manage Type 1 Diabetes.

When I first set up this phone, I tested with TeamViewer from a remote device to the S10e and was able to see the S10e screen, open the app I needed, tap around to control the app, etc.

Between that successful testing with TeamViewer and pairing the first glucose management device to the phone via the Omnipod app, I got 2 software updates to the S10e and took them both.

Now, when I use TeamViewer (or scrcpy or any similar tool), the Omnipod 5 app is controllable (ie, I can tap and issue clicks remotely), but the screen is not viewable - it is just a black screen on the remote device. Other apps/launcher/etc. work fine (can view and control remotely).

I suspect this might be something that was enabled as a security policy after taking one of those two updates that came through. The other option I thinDoes this sound right? If so, would downgrading to an earlier version of the stock OS perhaps resolve this issue? Looking for help on ideas to try to get remote control up and running on this app again.

Note: supposedly (according to the app manufacturer), the app has root detection (I am not currently rooted) and will block the app if rooted. I have not rooted for this reason, am happy to try it and can play with bypass solutions, but also want to be sure I can completely unroot if needed, to a stock state, to be sure the needed app will run if it detects root.

Thanks in advance for any help - I'm a bit rusty and this will truly be a life changing setup for my son if we can figure it out.
[Samsung Galaxy S10e Questions & Answers] aug0211:
Bump… anyone?
[Moto Edge X30] thaihoc1908:
Hi all, I have a problem with motorola edge x30.

My phone buy china, I unlock bootloader and flash rom global. But i have a problem. My phone stuck screen stylus, can not unlock screen, i must reboot phone, but when i lock screen, stylus screen reappeared

Can you help me fix it?

My english not good, i hope you can understand my idea.

Thank you very much
[Moto Edge X30] arcanjoking:
I'm also having the same problem!
[Moto Edge X30] arcanjoking:
Try this!View attachment 5660345
[Moto Edge X30] arcanjoking:
Try this
[Moto Edge X30] Abetterman2514:
Don't have motostylus service
[Moto Edge X30] arcanjoking:
On the search screen, did you go to the menu and the option "Show system apps"?
[Moto Edge X30] Abetterman2514:
Yes I did but it doesn't has that menu
[Moto Edge X30] Abetterman2514:
Are you Thai?
[Moto Edge X30] arcanjoking:
Try disabling this other app.
[Moto Edge X30] thaihoc1908:
I'm from Vietnam
[Moto Edge X30] مجــاهدـــــ:
Go to MOTO app /display/disable Folio display.
[Moto Edge X30] arcanjoking:
In my case it did! Thanks for sharing the tip!
[Moto Edge X30] thaihoc1908:
Thank you very much
[Touch GSM ROM Development] kokotas:
Hex Screenshots

​

This is like a scratch note - an easy accessed "guide".

Its purpose is to help everyone understand what are the numbers - bytes - that we are editing according to AMAN's guide for ULDR Removal.

As the title says it is a "hex view" at the latest Official Elfin 3.10.710.00 ROM

to figure out how all those hex-strings are related

and

to be able to change them, knowing what is going on;)!

Regards!
[Touch GSM ROM Development] !Aman!:
i would love to, but then u need to send me your Diamond for testing purposes :p
[Touch GSM ROM Development] Ameet:
Promise me you will also tell me about those imgfs values for the xip playing guide and i'll send it right now :D
[Touch GSM ROM Development] !Aman!:
yeah i promise once i get the ULDR removed from ur diamond :p, i'll tell u about the imgfs values also :D
[Touch GSM ROM Development] vadyarik:
Yes! :) ULDR Removal for Elf/Elfins - Work!!!

htctouchp,

Thank you very much!!! :)
[Touch GSM ROM Development] !Aman!:
welcome :)
[Touch GSM ROM Development] dsixda:
Good work!!
[Touch GSM ROM Development] Demo[95]:
Whaaaou!

GOOD WORK.
[Touch GSM ROM Development] letama:
Thanks for this, that's so great! I managed to get 74.9 Mb free storage on my Elf with a cleaned ROM.

A little addon to your great tutorial: If you have the last hybrid with the pagepool patch at the end, comment it or modify the offsets to match the new ones. My first flash was stuck on mobility screen because of this (or was it bad luck ?).
[Touch GSM ROM Development] !Aman!:
sorry, i didn't get it :confused:
[Touch GSM ROM Development] kokotas:
Thanx for this new finding Aman!

It's great!

I noticed that after this ULDR removal, there is only one address that we find the pp pattern(03 15 A0 ...)!

Is it normal or did I mess it up?:D

The offsets for the pp have been changed, so the script I wrote for the 2.2 Rom was aiming(&hexediting) the wrong offsets, resulting in a non-bootable rom..

Regards!
[Touch GSM ROM Development] !Aman!:
yes, its perfectly normal. if u check the PP offsets of the original payload of any ROM, the first HEX string is in the region of ULDR and the 2nd in the region of the XIP. So obviously u can see only one HEX string now. And as i said in PP changer thread a few days ago that only 2nd HEX string is responsible for the PP change, so even if u don't remove the ULDR, u don't have to edit the 1st HEX string.

:D ok, now i get it.
[Touch GSM ROM Development] dsixda:
Can you guys give the PP offset for a 2.2 ULDR ROM, as wel as a 3.xx ULDR ROM? I'll need to add more checks for the Universal PP changer :-)
[Touch GSM ROM Development] kokotas:
Found it:

lol:D:D

It sounds like you did some magic...hehe:D

Question:

When I followed your instructions and reached to the point of deleting ULDR section, imgfs start offset was 0x350400

and I had to delete some "FF" above to make that 0x350000.

Have you any idea about what went wrong?
[Touch GSM ROM Development] !Aman!:
0x350400 :eek:? impossible....u must have missed something...try again.
[Touch GSM ROM Development] !Aman!:
for the 3.XX based nk.exe ULDR removed ROM, the offset is 0x45210. didn't check the 2.XX ROM though.
[Touch GSM ROM Development] dsixda:
Ok, the Universal PP Changer has been updated and tested with your ULDR hack. All 3.xx ROMs are now supported. I haven't been able to check on 2.xx ROMs without ULDR, however.

Thanks htctouchp!!!!
[Touch GSM ROM Development] !Aman!:
welcome!!

i think we don't need to work with 2.2X ROMs now. all the ROMs from now onwards are going to be based on 3.3X ROMs anyway.
[Touch GSM ROM Development] Noonski:
All i'm hoping at the moment is that i removed the Bytes correctly :D.

"Delete all the HEX bytes from 0x400 upto 0x30FFFF"

I took that as a Starting from the beginning of 400 to the end of 30ffff.

Not directly my favourite stuff to do but what is there to loose ;)

Well IF It Boots It Works. (Should have noted storage before, but looks better)
[Touch GSM ROM Development] !Aman!:
yeah thats correct :D
[Touch GSM ROM Development] Noonski:
Now was it possible to edit the PP in the Payload?

And what would be the adresses to patch.

Really think the ELF should go to default 4 in new Rom as ATM little memory is left for ELF version.
[Touch GSM ROM Development] !Aman!:
nope, payload doesn't determine the PP. S000 of nk.exe decides this. so if u want to keep a default value of 4 MB PP for all of your ROMs, open S000 of nk.exe in Hex editor, search for the new Hex string that i mentioned in PP changer thread and edit it to be equal to 4 MBs ;)
[Touch GSM ROM Development] swordfish2009:
Where is payload file?????

how can i dump it and build it again?

Is tool provided in hypercore ?

I read in somewhere that there a tool to extract it..
[Touch GSM ROM Development] Demo[95]:
There is no payload in hypercore kitchen. If i can give you a simple advice, start using Hybrid kitchen like anybody else do in this thread.
[Touch GSM ROM Development] dsixda:
Payload is pretty much the OS.nb extracted from the original shipped ROM's NBH file.

Please correct me if I'm wrong. ;)

If you guys want, I can upload the 3.xx OS.nb.payload tonight with the ULDR taken out, but then that would take the fun/work/learning out of doing it yourself.
[Touch GSM ROM Development] Demo[95]:
That's exactly what i've understood.... but i don't know where the OS.nb (acting as payload) must be placed in Hypercore.

I guess, i will try to do it manually, then writing a simple console application to do it.
[Touch GSM ROM Development] dsixda:
Sorry, forgot to mention.. it's goes under the ROM directory.. (well, for Hybrid Kitchen)..

ie. You should see this structure:

SYS/

OEM/

ROM/OS.nb.payload

ROM/XIP
[Touch GSM ROM Development] Demo[95]:
Thanks dsixda, but i know where it must be placed in Hybrid kitchen... but i can't find where to put it in Hypercore.... To tell the thruth, that's exactly why i move to Hybrid kitchen.
[Touch GSM ROM Development] kokotas:
ULDR Removal

I was wondering what changes should be applied in the MBR and MSLFSH50 regions if I decide to use less space for the XIP...

Instead of (0x350000 - 0x400 =)

3.31 MB

to use less.

For example, in my case I'd like to have :

2.8 MB

(=0x2CD0CD - 0x400)

Regards!

ps:I really think that Aman's Guide for ULDR Removal should be a separate thread..Just a suggestion:D
[Touch GSM ROM Development] Ameet:
Hey Koko. Just in time for my guide with Aman's help on that one ;)
[Touch GSM ROM Development] kokotas:
Oh..That's cool:D

I'll wait then for your guide guys!

Regards!
[Touch GSM ROM Development] Ameet:
Added ;) Check the link in my signature (not the donate :D) the much more guide :rolleyes:
[Touch GSM ROM Development] Soul_Est:
Thanks for the great guide !Aman! and kokotas for the reference guide! I'd also like to add that you need to edit the second pair of hex digits from the left as they are 'markers' for the XIP and IMGFS (31 and 66 to 00 and 35 respectively) and should be adjusted as well.
[Touch GSM ROM Development] ngochoangimsat:
I think this is Problem:

000001b0h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02

000001c0h: 01 31 23 7F 01 65 02 00 00 00 7E 1A 00 00 00 00

000001d0h: 01 66 25 7F 81 DF 80 1A 00 00 00 3D 03 00 00 00

000001e0h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

000001f0h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA

You should edit to:

000001b0h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02

000001c0h: 01 31 23 7F 01 65 02 00 00 00 80 1A 00 00 00 00

000001d0h: 01 66 25 7F 81 DF 82 1A 00 00 00 3D 03 00 00 00

000001e0h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

000001f0h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA
[Touch GSM ROM Development] !Aman!:
there is no problem.
[Touch GSM ROM Development] ngochoangimsat:
This is before remove ULDR:

000001b0h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02

000001c0h: 01 00 20 7F 01 30 02 00 00 00 7E 18 00 00 00 00

000001d0h: 01 31 23 7F 01 65 80 18 00 00 80 1A 00 00 00 00

000001e0h: 01 66 25 7F 81 DF 00 33 00 00 00 3D 03 00 00 00

000001f0h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA

I think after remove ULDR XIP start at 0x400 (02 00 00 00) and size 350000 (80 1A 00 00)

Therefore it is must be:

000001b0h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02

000001c0h: 01 31 23 7F 01 65 02 00 00 00 80 1A 00 00 00 00

000001d0h: 01 66 25 7F 81 DF 82 1A 00 00 00 3D 03 00 00 00

000001e0h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

000001f0h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA

why do you edit size of XIP (80 1A) to :

000001b0h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02

000001c0h: 01 31 23 7F 01 65 02 00 00 00 7E 1A 00 00 00 00

000001d0h: 01 66 25 7F 81 DF 80 1A 00 00 00 3D 03 00 00 00

000001e0h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

000001f0h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA

???? Sorry I would to understand more clearly. Do you edit XIP'Size from 80 1A to 7E 1A to MSFLSH Start at 350000? (If not edit 80 1A to 7E 1A MSFLSH will start at 350400)

If I were true. All of the member have to delete offset from 0x350000 to 0x350400 of XIP to MSFLASH start at 0x350000 corectly

Fomular for all (after remove ULDR):

1. Start LBA of XIp always is ($1C6 - $1C9): 02 00 00 00 -> resever is 00 00 00 02 = 02 (sector)

2. Size of XIP = 00 00 1A 80 (Old XIP size ) - 02 (Start LBA of XIp) = 00001A7E -> resever is: 7E 1A 00 00 ($1CA - $1CD)

3. Start of MSFLSH = 02 (Start LBA of XIp) + 1A7E (Size of XIP)= 1A80 -> resever is: 00 00 80 1A ($1D6 - $1D9)-> Ofset is: 1A80 x 200 = 350000

4. MSFLSH50 Region ($21C) is: 350000/10000 = 35
[Xiaomi Poco X3 Pro] khusika:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

Pixys is a butter smooth Android aftermarket firmware. We handpicked the best features around and are adding our own juice into it.

Get ready to taste the unique features it brings with itself.

We aim to deliver an experience with original ideas and features along with the useful things the community is accustomed to.

Subinsmani

rahul9999

@ki

Shreejoy Dash

kvijaya

AxelBlaz3

Psycho-Mods

aswin_a_s

Gero

melvingarcia

Support Us if you like our work

* 3 finger screenshot

* long press music control

* scramble numers on pin entry

* custom pattern grid sizes

* smart space

* new gen assistant [optional]

* 90fps in pubg and simliar apps (for devices that support content based refresh rate)

* Bt battery level on statusbar

* kdragons monet theme engine with customisation

* assistant voice typing in gboard [optional]

* unlimited original quality backup on photos

* burn in protection

* AOD,cafeine and headsup qs tiles

* gesture bar length customisation with hide

* network traffic indicators

* pixel 6 live wallpapers [optional]

* ability to hide notification headers

* extreme battery saver

* in call vibration options

* vibration intensity customisation

* icon pack and font customisations

* pocket judge to prevent accidental wake up

* brightness slider customisations

* statusbar icon tuner

* playback control gesture

* advanced reboot options

* added more themed icons on launcher

* privacy indicators

* face unlock

* lockscreen media art

* less boring headsups

* custom vibration pattern

* exFAT support

* quick tap from pixel

* google pixel game mode

* Option to force full screen for apps

* Hotspot: hidden SSID mode

* Hotspot: customize the auto-off timeout

* Hotspot client manager

* charging ripple animation

* black theme

PixysOS | Device Tree

RECOVERY | ROM

- Backup your personal data (Important)

- Flash firmware

- Flash rom.zip

- Do format data/factory reset

- Reboot

You tell... :p
​

Credits​

- Google for AOSP

- Dirty Unicorns

- Pixel experience

- AOSP extended

- LineageOS

- Nitrogen OS

- Superior OS

- Statix OS

- YAAP

- Krypton AOSP

- AICP & POSP Team for thread template idea

- Also many pro devlopers who all help us to bring this rom to you..

- Please let us know if we forgot to mention your name in credits..​

Contributors:

kubersharma001 for the device-tree

ROM OS Version: 12L

ROM Kernel: Linux 4.14.190

Based On: AOSP

Version Information

Status: Stable

Current Version: v5.1.6

Release Date: 2022-10-12
[Xiaomi Poco X3 Pro] khusika:
Reserved for another post
[Xiaomi Poco X3 Pro] roirraW "edor" ehT:
Hi @khusika! Thank you for sharing. Question: The thread title says "PixelOS", but the rest of the OP says "PixysOS". Does the thread title need fixing?

Thanks and Cheers!

This post will self-destruct in 5....4...3...2...1... Just kidding. I'll delete this post when it's no longer necessary.
[Xiaomi Poco X3 Pro] khusika:
Thanks for the reminder, i have changed the title.
[Xiaomi Poco X3 Pro] knigge111:
Hello kuhsika,

many thanks for this rom! I will it install immadiatly!
[Xiaomi Poco X3 Pro] khusika:
Enjoy it :coffee:
[Xiaomi Poco X3 Pro] elizabethangelalorenza:
Wowwww. Nice work sir!
[Xiaomi Poco X3 Pro] simbirskiif:
Hello! This system consumes less battery power than, for example, pixel experience 12.1?
[Xiaomi Poco X3 Pro] khusika:
Thread updated alongside with the official-release 🎉 🎉

***Do clean flash if you having problem with dirty flash

Changelogs:

5.1.4 changelog

* merged july 2022 security patch
* added hw key customisation for supported devices
* added touch gestures for supported devices
* Fixed updating app disabling applock
* Fixed dual sense controller support
* Fixed random settings crashes
* Fixed minor crashes in gapps build
* Enabled lte+ icon
* Synced medium navbar style to a13 beta
* Toggle data usage view on QS footer
* Add support for ignoring secure windows
* Added background process killer
* Add support for strict standby policy
* fixed logo in recovery
* updated apns
* Show Android version as 12L
[Xiaomi Poco X3 Pro] droid2014:
hey i installs the rom as per the instructions: clean flash> format data> reboot and my phone stuck in boot screen for a few seconds then reboots and again. I have no ideas how to solve it. Any idea how to fix it?

ps my recovery: twrp 3.6.2_ 12 nebrassy
[Xiaomi Poco X3 Pro] khusika:
Seems like you wipe all data/system partition, clean flash mean doing format data/factory reset after installing flashable.zip.

Install MIUI fastboot image to fix your problem, and then follow pixys's installation instruction if you want to install this rom
[Xiaomi Poco X3 Pro] droid2014:
thanks, everything works good
[Xiaomi Poco X3 Pro] khusika:
If there anyone wants a specific feature for this ROM just ping me in this thread. Currently i'm pushing some of good features for PixysOS through my gerrit changes
[Xiaomi Poco X3 Pro] samsungics1200:
Add screen resolution changer like the oView attachment 5657451ne I see from miui or one ui 720p to 1080p
[Xiaomi Poco X3 Pro] khusika:
Those feature is similar to display-colors control on OSS-ROM, those only change display-color intensity.
[Xiaomi Poco X3 Pro] samsungics1200:
not display color theyre different what I suggest changing the density and resolution itself like the wm adb size
[Xiaomi Poco X3 Pro] khusika:
Nothing difference with display-control and dpi changer, only repacked with different UI.
[Xiaomi Poco X3 Pro] d3zone:
looks like a great Rom just two questions does it trip safety net and how long and how often will the Rom be updated (approximately)
[Xiaomi Poco X3 Pro] khusika:
Safetynet passed without root and the update comes when there is a major change from source
[Xiaomi Poco X3 Pro] knigge111:
Hello @khusika ,

very nice rom! I have updated from .3 to .4 via dirty flash and all works like a charm!

Many thanks!

Greets Martin

P.S.: @khusika today i tested a few games with youre rom. After 20 minutes playtime a massiv temperature jump happens. Where the camera module is, i could not hold longer then 30 seconds. I play only casino games. The same problem i have with Elexir, Pixel OS and Arrow OS. What could i do to solve this problem?
[Xiaomi Poco X3 Pro] knigge111:
@khusika Wich audio improvements could you implement? Kernel settings that are really make sense? More customization tools for the ui? A special tweak entry in the settings with all the best tools do you know? I miss the old times where the rom´s have a plenty of tweaks integrated. Or maybe a second rom for the tweakers? ;-)
[Xiaomi Poco X3 Pro] khusika:
I won't implement 3rd party audio tweaks for this rom
[Xiaomi Poco X3 Pro] knigge111:
Okay, thank you for the reply.
[Xiaomi Poco X3 Pro] khusika:
New build is up

Source Changelogs:
* Bump to 5.1.5
* merged august 2022 security patch
* Added statusbar clock customisation
* Improved refresh rate options
* Option to block sensors for apps
* Added new Settings UI as optional
* Introduced hint promt system
* Added partial screenshots
* misc improvements

Device Changelogs:
*Add Per-app refresh rate
*Fix various sepolicy denials
*Optimized rootdir
*Switch to dot product for CPU variant
*msm_irqbalance: Correct the arch_mem_timer interrupt
*nfc: Enable config to support extended APDU

Kernel Changelogs:
*Fix various clang warn reported by google clang-r416183b1
*Fix various driver error
*Optimize dts panel for Vayu
*Update wireguard to v1.0.20220627
[Xiaomi Poco X3 Pro] interferometry4:
is this rom based on miui?
[Xiaomi Poco X3 Pro] khusika:
New build is up with the latest October 2022 security patch. This is the last version of Android 12. Android 13 will coming up when it's ready
[Xiaomi Poco X3 Pro] Obi-Juan:
Great! I'm moving from crDroid and this seems a fine alternative. I definitely will wait for a version with Android 13.
[Xiaomi Poco X3 Pro] Boccajr:
Nfc does not work, it is as unavailable.

x3 pro
[Xiaomi Poco X3 Pro] javaClass:
Does this ROM have problems with fast charger? I tested several, Pixel OS, Pixel Experience, Lineage OS and all but MUIU have problems with fast charging.
[Xiaomi Poco X3 Pro] SmartJuwel:
ArrowOS/CrDroid (Android 12L) charge in <1h, when battery is near 10%.
[Xiaomi Poco X3 Pro] blor:
Hello, and installed the ROM, only Bluetooth does not work correctly for me, when connecting it to the car, the music information is not seen, both with Spotify and YouTube, it is not seen artist details Do you know if this has a solution, it also happens to me with ROMs with Android 13
[Fire TV Q&A, Help & Troubleshooting] mikewolski:
Hi guys,

I have a fully customized and rooted mantis stick, and I have 3 other mantis sticks that unfortunately I cannot root due to their software versions. I was just wondering, with prime day coming up, are there any devices that we can buy that will be able to be rooted? What are your recommendations for Amazon devices to purchase on prime day?
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
Idk if you're aware of it, but kamakiri 2.x works up to <6.2.8.7 without shorting (i.e. the sticks OS needs to be lower than 6.2.8.7).

Maybe a fireTVstick lite or the fireTVstick 3rd gen...

[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 3 and Fire TV Stick Lite (sheldon/p)

Read this whole guide before starting. This is for the 3rd gen Fire TV Stick (sheldonp) and Fire TV Stick Lite (sheldon). NOTE: FireOS < 7.2.7.3 required NOTE: This process does not require you to open your device. What you need: A Linux...

xdaforums.com
[Fire TV Q&A, Help & Troubleshooting] mikewolski:
Thanks, but I just checked and they are on 6.2.9.
[Fire TV Q&A, Help & Troubleshooting] Finnzz:
There are no rooting methods for any of the current FireOS versions. But if you buy a new FireTV device, they are shipped with older firmware versions that are rootable.

When you first setup the device, it will try to update to the most recent firmware. Skip that update process by following this guide:

How to Skip Software Updates during Initial Setup or Factory Reset on a Fire TV, Firestick, or Fire TV Cube

Since the latest software update for Fire TV devices is blocking the ability to use custom launchers, you may want to avoid updating a new or factory reset Fire TV.

www.aftvnews.com

I believe the 3rd gen FireSticks and 2nd gen Cube are shipped with firmware that is rootable. You may even be able to find a 4k Stick shipped with older firmware that is rootable.

Fire TV Original Android Development

Original Android development for the Amazon Fire TV

xdaforums.com

Only the 4k Max currently has no rooting method.
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
(y)

In case of the fireTV-Stick lite or the 3rd gen Stick, it's best to keep the device offline and try/do the unlock first...
[Fire TV Q&A, Help & Troubleshooting] mikewolski:
Good to know, thank you!
[Fire TV Q&A, Help & Troubleshooting] mikewolski:
Hey guys, so I'm looking at going with either the 3rd gen firestick or the 2nd gen cube or maybe I'll grab one of each. I was only able to find the thread about a temporary root for the cube. Is that the only way to root it? The 3rd gen stick looks promising since it can be rooted and loaded with custom roms, but it's kind of a bummer it can't do 4k. Do you think the 4k max will ever be rootable?