yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III General] DaveShaw:
JBed.exe in \Windows
[Tilt, TyTN II, MDA Vario III General] DaveShaw:
And please don't post duplicate thread's. You will only anger people.

This is in no way related to Kaiser Upgrading and you have already asked about this in the SU2U post. And I have answered in there. There was no need for this thread.

Regards

Dave.:D
[Xiaomi Mi Mix 2 Questions & Answers] fabian_screta:
Hello,

I have on me Nexus 5X Android 8.1 (crashed by update(all Files Deleted, from Beta to Final 8.1)

I Have now a Mi Mix 2 and LineageOS 14.1, now i wanted setup the me Mi Mix 2 but the Backup from Google drive say Only a Other Phone but not Nexus 5X, i think its Android 7 :(

Comes in the Next Days a Unofficial Version if LineageOS 15 or 15.1?
[Android Q&A, Help & Troubleshooting] shanuflash:
Hi, I'm shanu

I want to know

I've searched a lot in Google, found many websites, but different websites use different ways to Port, but I don't believe those websites, so I came to XDA forums.

Is there any one who can teach me how to Port a rom for mt6592 device?

And i also want to port from nougat to oreo!

Thanks in advance! :D
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] The WiTcH Er:
Great job dude, used it, this has minimal features, xperia fans will like it.
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] kishore777:
Screenshots plz
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] potatoman4321:
Nice work bro, do you think fp gestures will work some day?
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] garvit girotra:
As the rom source is of aosp then fingerprint gesture may not work for future till there be any implementation .for gesture u can try any lineage source based rom. As there are many lineage based roms
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] The WiTcH Er:
See above over your comment.
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] Omer98:
Please fix fingerprint gestures.thanks

Lenovo P2 cihazımdan Tapatalk kullanılarak gönderildi
[Google Pixel XL Themes, Apps, and Mods] HACK3DANDR0ID:
Magisk has a Viper4Android Module you can download and install and reboot which you are going to use.

I have this working on my Pixel XL running 8.1:

-Installed ElementalX v3.0

-Installed Magisk v14.5

-Installed BusyBox Module found in Magisk

-Installed Viper4Android FX v2.5 (Created by ahrion ,zackptg5) This module give you option of new or old Viper.

-Installed The Magisk permissive script (Found Below)

-Restart

When you have completed the above steps, open Viper4Android and check the Driver Status. It should look like the screen below

Thanks to [MENTION=2337245]TWisTeD48[/MENTION] for the simple instruction over at the thread [12/13/17] ViPER4Android FX 2.5.0.5 [Unity/AML][v2.5] by ahrion
[Google Pixel XL Themes, Apps, and Mods] Scottay5150:
Will AP still work with this if I dirty flash?
[Google Pixel XL Themes, Apps, and Mods] alamo76:
Yeah, I'd like to know if AP will pass, too.
[Google Pixel XL Themes, Apps, and Mods] sulpher:
Ya safetynet is passing with this installed.
[Google Pixel XL Themes, Apps, and Mods] Poloasis:
Anyone tried this with Dolby add-on? Either Atmos or Digital?

Tx guys.
[Google Pixel XL Themes, Apps, and Mods] Rajaasim1980:
Can we uninstall super SU and suhide to flash magisk without wiping data and flashing factory image.. i see that arise amd viper mod need migisk
[Google Pixel XL Themes, Apps, and Mods] Donric13:
Try to unroot device through supersu app. This normally works on my device. If device doesn't boot after this flash factory image deletinng "-w" in flash-all.bat. In supersu thread you also find somewhere a unsu.zip to flash in recovery to totally unroot a device.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] draxie:
Unlikely...

What was the latest version of FireOS ever installed on this device?

If it's anything above 3.2.6 the flash-programmer won't work.

I do have the files somewhere though, if you want to try anyway...
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] fufu508:
Thanks in advance [MENTION=5828306]draxie[/MENTION] if you (or anyone else) can find the missing files.

I blocked OTA on this tablet as soon as I got it. The FireOS version was 13.3.2.3.2.

I kept it blocked until I installed Cyanogenmod 12 (downloaded that on 2015-07-12) which coincides with when I took the FireOS backups mentioned in my OP.

I think I may have actually bricked it trying to install CM 13 (I downloaded that on 2016-03-10, which coincides with the CM backup mentioned in my OP).

I'm pretty confident this tablet has never seen FireOS beyond the factory installed version.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Based on recent PM traffic looks like you are getting the assistance you need and are close to recovering your device. Excellent - good luck!
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] fufu508:
Thanks [MENTION=5488402]Davey126[/MENTION], yes I think I have all the stuff I needed, thanks again [MENTION=5828306]draxie[/MENTION] for the fw.zip file!

Based on what [MENTION=5828306]draxie[/MENTION] PMed me, I replaced the two files in fw.zip with the ones at the links below.

I have the correct (Thor) emmc_aboot from here, renamed a copy and put into fw folder as emmc_appsboot.mbn:

https://xdaforums.com/showpost.php?p=74269859&postcount=777

The extracted file (the first one, for Thor) matches:

66b7df0db97c7c2905d1d61199c816a5 emmc_appsboot-13.3.2.3.2_user_323001720.mbn
4a2be8e374c8d1fce8e6743ac2d09bb0 emmc_appsboot-14.3.2.3.2_user_323001720.mbn

And took this recovery.img, and put a renamed copy into fw folder as recovery.img:

https://xdaforums.com/kindle-fire-hdx/development/recovery-twrp-3-0-0-0-t3322547

Although the flash process reported success I observed no change to tablet behavior.

I'll continue digging through [HOW TO] Unbrick Kindle Fire HDX (QHUSB_BULK) with firmware <=1314.3.2.6

Is there any way to tell for sure if I have a newer firmware than 13.2.3.6, or better yet, what exact firmware I have? I know I never would have intentionally put FireOS back on the tablet, and without it, can the tablet do OTA updates?
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] draxie:
TWRP => fastboot => 1-Click

If the flash programmer didn't get stuck with the kind of messages

you find in the "unbrick thread", your firmware version is low enough.

If you can boot into TWRP (as you should) by holding Power+VolUp

(from fully powered off state), then you can always sideload a ROM

(by selecting Advanced and ADB Sideload), but you'll need to start

with a fake-signed ROM, unless you unlock first. If you boot into

fastboot mode from TWRP (by selecting Reboot and Bootloader),

you can use 1-Click to unlock first, and THEN load *any* ROM...

If you cannot get into TWRP the "normal" way, then apply this patch

and perform a new round with the flash programmer:

--- rawprogram0.xml.orig 2017-12-17 20:35:50.559954169 +0100
+++ rawprogram0.xml 2017-12-17 20:36:17.417952679 +0100
@@ -9,7 +9,7 @@
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="" label="misc" num_partition_sectors="4" physical_partition_number="0" size_in_KB="2.0" sparse="false" start_byte_hex="0x10000000" start_sector="524288"/>
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="emmc_appsboot.mbn" label="aboot" num_partition_sectors="4096" physical_partition_number="0" size_in_KB="2048.0" sparse="false" start_byte_hex="0x10000800" start_sector="524292"/>
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="rpm.mbn" label="rpm" num_partition_sectors="1000" physical_partition_number="0" size_in_KB="500.0" sparse="false" start_byte_hex="0x10200800" start_sector="528388"/>
- <program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="" label="boot" num_partition_sectors="20480" physical_partition_number="0" size_in_KB="10240.0" sparse="false" start_byte_hex="0x14000000" start_sector="655360"/>
+ <program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="recovery.img" label="boot" num_partition_sectors="20480" physical_partition_number="0" size_in_KB="10240.0" sparse="false" start_byte_hex="0x14000000" start_sector="655360"/>
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="tz.mbn" label="tz" num_partition_sectors="1000" physical_partition_number="0" size_in_KB="500.0" sparse="false" start_byte_hex="0x18000000" start_sector="786432"/>
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="" label="pad" num_partition_sectors="2048" physical_partition_number="0" size_in_KB="1024.0" sparse="false" start_byte_hex="0x1807d000" start_sector="787432"/>
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="" label="modemst1" num_partition_sectors="3072" physical_partition_number="0" size_in_KB="1536.0" sparse="false" start_byte_hex="0x1817d000" start_sector="789480"/>

All the above does is to instruct the programmer to flash 'recovery.img' to the 'boot'

partition (in addition to the recovery partition). Doing so causes the tablet to boot

boot into TWRP automagically without having to hold any keys.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Great info as always [MENTION=5828306]draxie[/MENTION]. Posts like this tend to get referenced long after the current application has reached its conclusion.

As the vulnerable aboot (bootloader) is in place the other way to get TWRP to boot is via the following issued at fastboot ready:

fastboot boot <path><recovery>.img​

where: recovery = name of recovery images for the target device (eg: twrp.img)

Tip: put the '.img' file in the same folder where fastboot lives to simplify the command string.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] draxie:
Right... assuming that you can get the device into fastboot,

which is not always easy unless you have unlocked, or able

to boot into TWRP...
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] fufu508:
Thanks guys. I see the difference in the code block above is in filename attribute. I have made the modification and attached the resulting log.

Attempting reboot now.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] fufu508:
:victory: W¤òT!!! We have TWRP!! :victory: :highfive:

I've used TWRP to get the tablet into fastboot. Now to reboot into Linux and do a 1-Click! :D
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Cool! Note there is a relatively easy workaround if one click doesn't do the trick (which it should). Simply load up Fire Nexus KTU84Q which has a forged signature and then generate an unlock code using the tool provided by [MENTION=5828306]draxie[/MENTION] in the unlock thread (step #1). Don't worry if the code doesn't get applied automatically in step #3. Easy fix with a Windows driver tweak.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] draxie:
LOL

1-Click said the bootloader had been unlocked already. Go figure...
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] fufu508:
Yeah, it turned out to be (at least in part) due to bad volume controls, i.e. I had to use the special USB cable to get access to flash the latest TWRP and get out of the gray Kindle logo nightmare! :eek:
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
I think a *different* USB cable was likely the solution vs a special "fastboot"/"factory" cable which has prove to be largely ineffective on this device.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] fufu508:
Hey Davey126, I think it actually does make a difference :)

My tablet enters the Qualcomm QDLoader 9008 mode only when I plug this cable, which is electrically different, i.e. the 5-pin micro USB plug has a jumper between Vcc and ID pins.

[IMG=""Fastboot/Factory micro USB wiring connections""]https://xdaforums.com/attachment.php?attachmentid=1833714&d=1364255670[/IMG]

With all other USB cables I have, the tablet simply loads invokes one of the common Android or ADB composite drivers.

The MiFlash utility doesn't see the tablet with any other cable I have.

See attachment for view of Device manager with "show hidden devices" enabled, no cable attached currently.

Even my computer sees this cable differently. If I leave the special cable plugged into my computer with the Kindle attached, my computer won't finish booting (presumably the BIOS sees a weird USB device), until I reboot without that cable attached.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Thanks. I'm quite familiar with the wiring differences and the beneficial nature of such cables on many older devices. Also not surprised Windows exposed a different suite of 'devices' using this cable.

My poorly articulated point (sorry!) is a special cable is not needed although it appeared to make the job easier for you. Cable quality is huge with this device (HDX). I'd say 30-50% of persistent connectivity issues are solved by simply switching cables assuming the right drivers are available.

My purpose is not to second guess your findings! I simply want to encourage future readers to try a different micro USB cable that may already be lying around vs building/purchasing a "fastboot" cable that usually yields the same results.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] draxie:
Sahara needs fastboot cable

I hate to disagree with you, but you got this one backwards;

not in general, mind you, but in this particular case.

With the volume buttons not working and system messed up,

there was zero chance to get into either TWRP or fastboot,

and adb was toast (due to system not working properly).

No matter what cable were to be used...

The flash programmer was the only way out, and that one

_requires_ a fastboot cable, but you know that already.

On the other hand, this is likely NOT an option for most

other people, since this only works if the device had never

seen any FireOS version newer than 3.2.6, and I'm thinking

most people have 4.x.something by now...
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Fair points and clearly right on the money. I lost track of the particulars (sorry [MENTION=8790220]fufu508[/MENTION]!) servicing multiple threads in various forums. Yes, 3.2.6 (or lower) generation bootloader and busted buttons are important details that got overlooked. Glad you were there [MENTION=5828306]draxie[/MENTION] to kept things on course to a successful conclusion.

I obviously know of specific cases that require a fastboot cable but tend not to expose those unless the situation warrants as this long favored path among Android enthusiasts is usually ill advised on HDX devices. This is obviously one of those cases that flew right over my head and didn't even leave a hair part. Sigh ...
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] fufu508:
Thanks [MENTION=5828306]draxie[/MENTION] [MENTION=5488402]Davey126[/MENTION]

Do I understand correctly now that Amazon eventually defeated the ability to use the flash programmer and that I got lucky by having not allowed my Kindle to upgrade fire OS too far?
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Basically, yes.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] fufu508:
Thanks and is the risk still there if this tablet never runs fire OS again? I assume Amazon has no idea that this is a Kindle Fire XD nor any control over it unless it's running fire OS? In other words if I never flash a stock ROM on here the tablet should be immune from that sort of interaction with Amazon?
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Yep - there is no need to (ever) restore FireOS or risk an unwanted OTA update from Amazon once the bootloader has been unlocked.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Sv01a:
[MENTION=8790220]fufu508[/MENTION] can you post a link to your fw archive? Maybe in pm.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] iksel:
Complete archive with all of contents needed for unbricking Thor

Ask for DL limk via PM

;)
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Sv01a:
Thanks!)
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Sv01a:
[MENTION=8790220]fufu508[/MENTION] [MENTION=4912761]iksel[/MENTION] big thanks! tablet successfully unbricked!
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] fufu508:
[MENTION=4156423]Sv01a[/MENTION] Awesome news to hear another Thor is alive and kicking!

Thanks [MENTION=4912761]iksel[/MENTION] for sending a copy while I was away.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] dancinns:
I sent you a PM [MENTION=8790220]fufu508[/MENTION]. I'm hoping that I can join the club of unbricked HDX 7's.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] nitinm79:
Can you please share the files and the process to unrbrick kindle hdx 7 ?

Am detecting my kindle as Qualcomm HS-USB QDLoader 9008.. i tried downloading the files from various forums for QFIL but no success. Is it possible for you guys to share the details along with the necessary files.

Am a newbie to the whole flashing process.....Thanks....
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Waschbeton:
I'd also would like to have the fw files, even though I'm on appollo
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] lokalkey:
thanks for DL link :highfive:
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] SirRedwind:
Hey folks, can anyone help me here?

My Fire HDX (Thor) is stuck on the "fastboot" screen and I have QDLoader 9008 access but other than that, nothing works.

I had Lineage 14 installed on it and when I installed an update (via TWRP), nothing ever worked again.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] ignat.cristi:
Hi, I have an Apollo 8.9 tablet that I broke. now it is in Qualcomm HS-USB QDLoader 9008 and I can say that I tried Miflash where I get error "Catastrophic failure 0x8000ffff:", I also tried Qfil but here I also get error. please if you can help me with rawprogram0 and patch0.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] drumcats:
@fufu508

Ask for DL link via PM
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Minicharl:
Hi there,

can someone help me please?

Can someone please share the files and the process to unrbrick kindle hdx 7?

Unfortunately, I bricked my hdx7 while it was stuck in a bootloop. I have all the drivers and the QDLoader 9008 has access to the tablet, but that's where it ends for me. It would be a shame if I had to throw it in the trash

thanks
[Lenovo Yoga Book Questions & Answers] Adilost:
Dear XDA Community,

So yesterday I recieved my Lenovo Yoga Book - Android Version.

Today I installed a few apps on the Yoga Book im using to watch my favorite TV Series & Movies. It has got to my attention that something very wierd is happening on the Yoga Book that NEVER happend on any other Andoird devices im using (like Samsung for instance), with the exact same applications.

Videoplayers like VLC / MX Player and Kodi have the abbility to zoom in on a video (fit to screen / full screen) so that there are no upper and lower black bars on the screen, since most tablet screens have a 16:10 ratio and TV Series are 16:9.

Here is my problem on the Yoga Book:

When a video is played, watching in normal mode everything looks fine (whole video is within screen):

[IMG="Video Normal Mode 1"]https://i.imgur.com/lb0ghLw.jpg[/IMG]

[IMG="Video Normal Mode 2"]https://i.imgur.com/YI0OGXA.jpg[/IMG]

However..

As soon as i zoom in on a video (fit to screen / full screen, or manually by pinching in and out) it is shown in full screen mode but, the screen also shows a black bar on the right side of the screen and starts "cutting out" de video:

[IMG="Video Full Screen Mode 1"]https://i.imgur.com/D0I304A.jpg[/IMG]

[IMG="Video Full Screen Mode 2"]https://i.imgur.com/iZAvwnt.jpg[/IMG]

As i zoom in further, the black bar takes even more space on my screen.

[IMG="Video Gone Wild!"]https://i.imgur.com/oBqva80.jpg[/IMG]

Every video player i've tried (as mentioned above) shows the same caracteristics.

I also did a full factory reset on the Lenovo Yoga Book, still no succes..

Is it a hardware related problem? Or is it something within a code of some video player settings within the Android OS?

Can somebody please help me?
[Galaxy S 5 Android Development (Snapdragon)] sunilpaulmathew:
Extras & Screenshots

***Extras***

(Flashable in twrp)

S8 Launcher

Downlaod (credits: [MENTION=7143167]huawei92[/MENTION])

S8 MyFiles

Download

S8-SystemUI&Settings

Download

N7 Launcher

Download

Screenshots

N7 Calculator

Download

N7 Gallery

Download

N7 Keyboard

Download

N7 MyFiles

Download

Gello Browser (Lineage-OS)

Download

Screenshot

Email (Lineage-OS)

Download

Screenshot

AudioFX (Lineage-OS)

Download

Screenshot

SmartPack-Kernel Manager (a modified version of KernelAduitor by myself)

Download apk

Screenshots

***Screenshots***

Fullly stock look
[Galaxy S 5 Android Development (Snapdragon)] sunilpaulmathew:
Change-logs

7. April 07, 2018

Release status: stable-v5.1

Please note: it will be the last update of this ROM unless Samsung releases new firmware for our device (very unlikely).

Changes in ROM: Fixed Samsung Weather.

Changes in Kernel: Merged some patches from latest Samsung code release. Updated fast charge into v2 (own modifications), which includes i. Enabled Custom Mode by default, ii. Bump USB and Wireless levels up to 1600, iii. Set default AC: 2000; USB:700; Wireless:900 (need more testing), iv. Reduced lower charge current for USB (400) and Wireless (600) and v. Miscellaneous changes.

6. February 21, 2018

Release status: stable-v5.0

Changes: Fully rebased over the latest Samsung firmware (G900FXXU1CRA2). Removed all the ported apps to retain the stock look and feel.

5. January 25, 2018

Release status: stable-v4.1 (minor update)

Changes: Mainly includes fixes for emergency service (UPSM) and some kernel level updates to improve performance & battery life.

4. January 12, 2018

Release status: stable-v4.0

Changes in ROM:

Heavily de-bloated. Added Voice recorder from N7.

Changes in Kernel:

Added USB gadget (keyboard & mouse) support (App).

3. December 29, 2017

Release status: beta-v3.0

Changes in ROM:

Added support to kltedcm via an AddOn package.

Removed N7 Calendar with Stock SPlanner.

Added System UI, My files and TouchWiz Launcher (optional) from S8.

Added TouchWiz Launcher, SFinder & Email from Note 7.

Updated Jelly browser with latest LineageOS commits.

Much more debloated (Removed Kids Mode, Easy Launcher & Galaxy Apps).

Changes in Kernel:

New CPU hotplug (Lazyplug) is introduced as a replacement to intelli_plug.

2. December 23, 2017

Release status: beta-v2.0

Changes in ROM:

Added support to klte (via an AddOn package)

Added Calendar, Gallery, My files, SNnotes, Calculator, Email & Keyboard apps from Note 7 (Credits:

[MENTION=8367804]A.nagi[/MENTION])

Changes in Kernel:

zzmove native hot-plugging is enabled.

UKSM default sleep is extended to 1000 ms to improve battery life.

Enabled a bunch of features (e.g: REISERFS, NTFS, JBD & JBD2 file systems) in the Kernel.

1. December 16, 2017

Release status: beta-v1.0

Initial release
[Galaxy S 5 Android Development (Snapdragon)] Bosket:
For klte it's safe to flash?
[Galaxy S 5 Android Development (Snapdragon)] sunilpaulmathew:
By-default No. Because the "boot.img" of this ROM is packed with kltekor dtb (which is too different from klte) and zImage.

However, it will mostly work (and should be safe) if you flash a klte kernel over this ROM (PS: preferably anykernel zip contains zImage and dtb for klte).