yashsingh1/xdaforums huggingface dataset:
[Fire TV Q&A, Help & Troubleshooting] Hannover2k:
Sorry is I'm missing something here. I've been trying to do your method and while I've been getting different error messages and results, I'm still not quite sure I'm doing it right.

After I get the first error after removing the short, you mention above to remove the USB then run the script again, etc. At what point do I plug the USB cable back in? Do I plug the USB back in after removing the power? When I do remove the power, do i need to reconnect the Jumper before plugging it back in?

Sorry if I'm lame, I've just done this jumper thing 100 times and can get many different results but not the one we're looking for! lol

UPDATE: Holy cow, I got it to work the very next time after posting the message! Here's what I did:

1) Ran the script, connected jumper and powered on the device.

2) Got error message.

3) Unplugged USB then re-ran script, pressing enter again after running the command.

4) Plugged USB back in.

I did not reconnect the jumper. When the USB cable was re-connected it did display a message to remove the jumper and press enter, however I did not have to do that. All kinds of stuff started flying all over the screen, then it got to;

Clearing Preloader Header

Flashing Tee

Flashing Bootloader

Flashing Unbrick Image

Flashing Boot

Booting to TWRP

I'm literally grinning ear to ear right now! Thanks for all your help with this! Even if it doesn't work at this point, I'm very happy to have gotten this far!

I can get these kiosk devices for $20 each. Box only, no power or remote. Does anyone think it would be worth it to buy a few of them and try to sell them off with refreshed imaged on them? There's a lot available so just wondering.
[Fire TV Q&A, Help & Troubleshooting] Bertonumber1:
[MENTION=8452071]Hannover2k[/MENTION] Yeah that's you got it sorted then, I tried to explain that method but didn't do a very good job of it lol, make sure you push pre-rooted rom and supersu 2.82 zip to /sdcard, and flash.

Please Remember and note that you cannot flash unsigned zips such as magisk to the Sloane as you're bootloader remains incarcerated , if you're device has cleared preloader and you've entered into twrp it should work

Ps. if you can get a Sloane for that price pm me and we'll sort something, doesn't matter about power cables, remotes etc
[Fire TV Q&A, Help & Troubleshooting] Hannover2k:
After flashing the pre-rooted image the first time, everything seemed to work except whenever I restarted via the settings menu, it would show the TWRP pre boot screen but allowing it to continue to boot normally would result in a boot loop. Performing a power cycle would cause the device to skip over the TWRP menu and boot right into the device.

Tried clearing the SD partition and dalvik to free up space as it was only showing about 1.2gb free after the flash. Got the free space back but still the same boot issue after flash, though it did work after a power cycle as opposed to restarting, which I rarely do anyways.

Remembering the Kiosk was for the original echo devices, I got to thinking about it having an older OS again and maybe not liking being flashed directly to the latest version so I re-flashed it to v5.2.6.7_r1. It would boot loop after the TWRP pre login screen but after the first loop it would boot properly. Went ahead and flashed it back to 5.2.7.3_r1 and everything seems to be working perfectly now. Restarts properly and all functionality seems to be present.

I really appreciate your assistance with this. I had them send me another one so I can try this method once more and if it works again, I'll definitely let you know and we'll work something out.

-Han
[Fire TV Q&A, Help & Troubleshooting] Bertonumber1:
The recovery partition maybe corrupted.

You may try updating twrp to the latest 3.0.05 from Sloane Twrp recovery page.

There you can download the file from here :

https://www.mediafire.com/file/brae6r8lu1np5jm/firetv2_recovery_v6.zip/file

,push it to Sloane /sdcard and run command

from pc

adb shell

Then run:

sh /sdcard/firetv2_recovery_v6.zip

Reboot

That should fix it.

As soon as you update TWRP

Reboot and flash the pre-rooted firmware and supersu 2.82.zip

Then wipe cache, dalvik

Let it boot up and then factory reset (data, dalvik, cache)

Reboot and it should be okay
[Fire TV Q&A, Help & Troubleshooting] Hannover2k:
Thanks for the info. The image I installed already had that version of TWRP installed on it but like I said in my last comment, flashing to an older rom then re-flashing back to the latest one seems to have resolved the issue.

No more Kiosk mode, though I wish I could have gotten a look at those files just to see what was going on there.

Anyways, all good now and I have another one of those kiosk units I'm going to try the process again on and if it works, I have access to a lot of these devices so I may refresh them and sell them cheap.

Thanks again for everyones input! Still surprised I got it working normal again.
[Fire TV Q&A, Help & Troubleshooting] Hannover2k:
Good news!

I was given a 2nd unit with the same 'issue' and was able to get it to start taking the image within a couple mins. The guy who has them can't do anything with them and has lowered his price per unit so are these worth anything to anyone?

Again, it's the box only, no power cords or remote but I don't expect that to be an issue for someone looking to replace one.

I hope I'm not breaking any rules by asking that but I'm open to any thoughts on this.

-Han
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
@Bertonumber1
[Fire TV Q&A, Help & Troubleshooting] Bertonumber1:
Yeah I've already replied via pm to @Hannover2k I've already bought one with power brick and remote for Roger @Sus_i hannover2k only has the Sloane itself AFAIK I got the full shebang for £27 so it's all good;) perhaps @Hannover2k can provide a spare and that's us got a couple to got to work on in the name of furthering development
[Fire TV Q&A, Help & Troubleshooting] thefrugalfilmmaker:
Just wanted to add my Order of Operations to this post. I also bought one of these "Kiosk" boxes without remote or power supply for $13 off of eBay. Great deal, I thought, if I can get it to root. It appears that the order in which you perform the steps is unique to your setup. After trying all the above suggestions with no success (similar errors as listed above), here's what worked for me:

1. Plug in male-to-male USB cable between FTV2 and Linux box

2. Short DAT0 pin on FTV2 board

3. Connect FTV2 AC power

4. Run script

5. Remove short, press enter once when prompted

After TWRP installed (and I figured out how to use it), I was successful in having a usable FTV2 with all of the perks this process brings. Thanks to all who contributed to make this possible, and an extra big thanks to @Hannover2k for being the first to try this on these specifically-challenged boxes. It was a huge help!
[Fire TV Q&A, Help & Troubleshooting] Bertonumber1:
There is a new unlock for this model in firetv original android development thread.

The bootloader is now unlocked so give that a try.

https://xdaforums.com/t/unlock-root-twrp-unbrick-firetv-2-sloane.4222331/
[Touch Pro, Fuze General] billu:
The spec for this device states 512MB ROM and 288MB RAM but how much is available after a hard reset?
[Touch Pro, Fuze General] billu:
So to answer my own question and for any others who might be interested:

Storage (ROM), total 322MB, free 275MB, Program (RAM) total 201MB, free 141MB (without tf3d, including tf3d adds about 10MB)

These figures are from a device after having been turned on for the very first time.
[Google Pixel 4 XL Questions & Answers] acomputerengineer:
A week ago I got the 10/5 security update. After the reboot I had a "No Service" cell status. After doing all the normal trouble shooting stuff, I did a factory reset. Surprisingly, I still had the "No Service" status. I also noticed that after the factory reset the device was still on the 10/5 update. I got a new sim from att and tried it on other devices and it works fine.

So I chat google support, they give me a little run around, but eventually I get an RMA device shipped to me.

A few days later I get the RMA device working as expected, things are fine. Then I get hit with the 10/5 update. I decline and decline, but eventually it rebooted and installed itself.....and again "No Service", but also this time, wifi is having issues too, connected to the network but "network has no internet". The network 100% does have internet.

So now I have 2 pixel 4 XLs with no cell connectivity and 1 with no wifi.

I've chatted google again, and they want to send me a 3rd phone, I'm all but convinced there's something broken with the security update.

Has this happened to anyone else (there are a few mentions on the pixel forums)?

Any advice for me?

info:

pixel 4 xl unlocked

att network

Android 11 build RP1A.201005.004
[Google Pixel 4 XL Questions & Answers] Keith W:
I had some issues after that update along with others, see here: https://xdaforums.com/pixel-4-xl/help/wireless-chanrging-issues-oct-update-t4178951

I have had a replacement 4XL sent to me via Google and phone is still on version 10 and working as expected

The phone keeps asking me to install version 11 but I am holding off doing that for as long as possible.
[Google Pixel 4 XL Questions & Answers] ibsk8:
I've been experiencing service issues as well. The last 2 weeks I've been losing sim provisioning for no apparent reason. The only way I can get service to return is via WiFi. The sim will re provision and work. This creates a huge problem for me as Im often away from WiFi while at work for 12 hours with no way to reset it.

I'm going to flash the newest factory image and see if it continues.

Current provider is Google Fi.
[Google Pixel 4 XL Questions & Answers] CharliexCharger:
Yep had the exact same issue. Looked to reboot in safe mode and received only a black screen. Eventually I just reflashed the latest update and it worked again. I still have this service issue intermittently.

As of today my Pixel 2 XL is without a working camera and the last camera update October 19th has my Pixel 4 xl without a camera. As of now I will strongly have to say this may be my last Google phone.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] Rizak kamal:
▪️ **Changelog** :

• Still September security patch

• Still A10, hope release this week for A11

• Merge linux-stable 4.14.202

• Enable Synaptics trackpoints

• Increase receive ring size

• Increase AES key storage size to 256 bits

• Other fixes and Improved performance

▪️**Notes** :

• EOL Build

• If you're currently on previous version, don't do dirty flash, you should flash another rom first then go to havoc, or wipe system by using fastbootd with lineage recovery

• This rom will boot on decrypt data, u have to do : Format data > Flash Rom > Flash DFE > Format data > Reboot

▪️Download : https://sourceforge.net/projects/ge...019-miatoll-EOL-Unofficial-GApps.zip/download
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] ghostranger047:
Finally Havoc has arrived. Everything seems to be working on gram.

ANXCamera works no force close.

Been waiting for Havoc for long.......

Awesome rom. Thanks devs.

Fingetprint app lock was one of the awaited missing feature in custom roms

---------- Post added at 12:14 PM ---------- Previous post was at 12:06 PM ----------

Hey can u please help me? When I boot into recovery, my sdcard shows a bunch of folders and not the original files.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] RayDeemer:
Should be ext_sdcard.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] savinjo22:
Format data
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] datadrop:
Wifidisplay and HW encryption not working, right? or only I have these errors
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] ghostranger047:
If by WiFiDisplay you mean casting, its working fine for me on gram. Casted my mhone on my android tv, working fine.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] datadrop:
That's Google cast, not Wifi display
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] Anonda:
Many many thanks for Bringing Havoc for our Device.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] javierl:
Hi, today i installed this rom on my n9s (curtana), in the lapse of 8 hours that i install, the phone freeze 3 times only when its locked, when it freeze i cant do anything, only restarting by pressing power on for few seconds.

What can it be? i only installed the rom, none apk rare.

Sorry for my bad english.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] purplefrozt:
Same here but I'm using a RN9pro global joyeuse, seems everything's working fine, except for face unlock doesn't exist on settings, and when phone on sleep/standby for a long time it shuts off/turns off everytime.

Thank you to anyone can help fix issue. :)
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] savinjo22:
Yes, this is my favotite ROM , but beacuse of this shut down issue , I can't use it anymore
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] AdamantiumBrain:
Did you do a dirty flash over the last one? Maybe that's the issue with the restarting problem...
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] purplefrozt:
i flash on a different havoc os with the same versions.

fixed:

re-flash a different rom then flash this rom over and the power off behavior is gone.

now :

as stated this rom has a face unlock which i did no have. after flashing the rom

and the Ok google, not working as well.

beyond those two rom is quite good for a daily for me.

dumb question:

should i be on default miui 11 stock. before flashing other roms?

thanks for responding
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] AdamantiumBrain:
The devs do tell you to flash the latest available firmware before flashing a rom but I guess that it's not required every time you flash unless the stock MIUI got a firmware update.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] purplefrozt:
cant make the "Ok google" and the face unlock to work. :confused: :(

thanks again :)
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] AdamantiumBrain:
Well, I haven't seen anybody else complaining about this so it's weird that it's happening to you... Maybe you should try by first flashing the latest firmware and then again flashing the ROM. Maybe that'll fix it.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] purplefrozt:
im back to oem miui 11.0.7.00 stock and lock bootloader.

this is what will do pls correct if wrong.

unlock bootloader

flash - pbrp recovery

flash vbmeta.img?

reboot to recovery

wipe Data, Dalvik, Cache

flash havoc os - ota,

this is the part im kinda lost....

thanks
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] AdamantiumBrain:
That's correct but make sure to only mount data, dalvik cache and cache after wiping and before flashing the ROM. Then, after flashing the ROM, remember to format data again before rebooting to system, or to recovery to install gapps or magisk.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] purplefrozt:
did this exactly on point.

still ni face unlock and "Ok google" :sad:

edit:

and random turn off during standby :sad: again

thanks
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] MPK99:
You can use KOUtility to force disable default encryption. Follow this tg tutorial, must use manual config, enable 6th option, keep all other options disabled & then flash. First time, you must format to have decrypted storage/data. Then afterwards, you can reapply Koutility on top of any rom without encryption initialization afterwards.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] MPK99:
It's upto dev's decision. It's system baked, so better leave it like that.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] MPK99:
It totally depends on rom builds. If a rom comes with forced encryption, it will encrypt internal storage on first boot. If it doesn't come, it wont do that. See my previous post for force decrypt rom guide👆
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] davidbejar:
I solved the problem, never managed to fix internal storage after format Data, but I found an old MicroSD card and installed from the MicroSD, and now everything is working again.

In case someone else is having this problem, they might just need a MicroSD to install the new version.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] Tortellio:
I have idle freeze problem, whenever i left the phone in a long time, the phone is idle but it wont wake up, i had to force shutdown the phone evertime it has the problem
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] alancash:
There is currently no R firmware for Joyeuse. The link you shared is for Curtana firmware. Things could get more worse if he flashed the wrong firmware.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] MPK99:
Then stick to A10 roms I assume.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] vlouis:
I have joyeuse too, don't know how is with Havoc A10/A11 rom, but I don't have any problem using other (now crdroid 7.3) A11 rom with A10 (V12.0.2.0.QJZMIXM) firmware. Maybe depend if the rom use or not features what presents only in A11 firmware...
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] JustAnAverageGuy_19:
When will we have an official 4.1 thread for miatoll??
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] Jas Grover:
means that KOutility should be flashed after flashing the rom or before?
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] Jas Grover:
the zip name was different and that 6th option? nothing was there like that!
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] MPK99:
Download koutility.zip from below link

- Miatoll Clouds

Steps to decrypt rom/storage

1. Flash roms

2. Flash koutility.zip tested on aosp only

3. Format data (required only first time after flashing koutility)

4. Reboot to recovery

5. Flash gapps (optional)

6. Boot into system

Congratulations your storage/rom is decrypted , you can switch roms without format

Next time when you want to switch roms

Steps

1. Wipe data,caches and dalvik caches

2. Flash rom

3. Flash koutility.zip

4. Reboot to recovery

5. Flash gapps (optional)

6. Boot into system

Remember you need to config koutility.zip in recovery

How to config koutility for decryption

-Set config (by pressing volume down)

-Yes (for edit config) by pressing volume up

-After that "No" till 5th option (by pressing volume down)

-Then "yes" for 6th option (by pressing volume up)

-Rest "No" till 16th option (by pressing volume down)

-Last "yes" to flash (by pressing volume up)
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] MPK99:
I hope you follow all instructions. If you need any help, you can pm me.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] HyperionAlpha:
This latest build just gives me the spinning animation at boot. Updated firmware also. Any updates forthcoming to this rom?
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] Jas Grover:
1. the name is not same as koutility.zip(its koutil_16.2.zip)

2. "

Set config (by pressing volume down)

-Yes (for edit config) by pressing volume up

-After that "No" till 5th option (by pressing volume down)

-Then "yes" for 6th option (by pressing volume up)

-Rest "No" till 16th option (by pressing volume down)

-Last "yes" to flash (by pressing volume up) "

these steps are not same, it just verifies the input, it says:- press vol -then press vol+, then it says the install is complete.

but the device isn't decrypted(completedthe steps ahead too)
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] Jas Grover:
ohk thanks
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] MPK99:
The zip module has menu that asks you whether you wanna edit the config or not. You need to hit yes on it, then it'll start asking the config list...

0. Flasher?

Proceed with usual config setup?

Hit "Volume Down to setup the config"

Do you want to edit the config?

Volume up - "Yes"

After decrypt v5, if the message "Forced Encryption not found" appears, means you successfully decrypted the rom.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] shadowstep:
THREAD LOCKED

Due to incorrect kernel source link mentioned.

Regards,

shadowstep

Forum Moderator
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] Rizak kamal:
Try change kernel for now
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] purplefrozt:
any suggestions so i know where to start. :D

thank you
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] :
There are 3 Kernels available in this forum. Choose one, go to Recovery, Backup boot (!), then install kernel zip.

If your device does not boot: restore boot partition.

For me Yuki works only if I install it via Pitch Black Recovery (also available in the Forum).
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] purplefrozt:
does this fix “ok google“, faceunlock and random reboots?

any benifit to the kernel itself?

thank you ☺ ☺
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] :
I´m without gapps, faceunlock and did not have random reboots.

I´m just sharing some experiences about how to change to custom kernel.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] purplefrozt:
oh, flashed the yuki kernel via pbrp recovery and no random reboots occurring so far.

thanks
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] Hymix:
Any chance of a Curtana version? I always liked Havoc on my Motorola in the past (or was that on a Nokia??)

NVM, my mistake!
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] Rizak kamal:
U can flash on curtana too
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] Paulicat:
Great work dev! Please don't abandon this as you've really done a great job.

Only thing I had to do like mentioned above by purplefrozt was flash yuki kernel, no reboots and no lock ups since.

Edit: Which vendor source are you using?

Thanks for posting kernel and device tree, but vendor would be helpful too please!
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] purplefrozt:
what do you mean by vendor source?

the mistake i did was, i came from a different havoc os same versions. to fix shutdowns i did this via pbrp (pitch black recover official beta joyeuse)

from oem stock miui 11

bootunlock

flash lr-twrp

flash vbmeta.img

reboot recovery

flash pbrp official beta (joyeuse)

reboot recovery

mount - data, meta data, cache only

format data - yes

mount - data, metadata, cache only

flash ota havoc os

flash disable dm verity forcencrypt

format data - yes

reboot to os once setup is done

reboot recovery

mount - system, vendor, data, metadata, cache only

flash gapps - nano (miro and up has a launcher pre installed in may experience it may mess up rom, lag, crashes)

flash magisk 20.4

reboot

to pass safetynet - enble magisk hide

to flash yuki kernel use pbrp only

boot recovery

back up boot only

flash kernel

reboot

that's what i did, no face unlock though

as ive read aro und the "Ok google" seems to be remove by google itself, to all roms ive tested almost half has no faceunlock and ok google, other half has faceunlock still no ok google function

hope this helps.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] cchalk:
Anyway to hide the notch?