yashsingh1/xdaforums huggingface dataset:
[Kindle Fire HDX 7" & 8.9" Android Development] Rovers82517:
Sorry, I was on on fire os 4.5.5 and have rolled back to 13.3.2.8_user_328003120, I have rooted Samsung's, Sony's in the past but with this I don't even know how find out what android this Amazon mess is wrapped over, jellybean/kitkat/lollipop I have no idea. I have factory reset my device with root, busybox and xposed in system/apps so permanent(ish) root. I have tried all apks I can find, had playstore working but then error after error "Google services has stopped working" I forget the exact wording, everything google related started failing.
[Kindle Fire HDX 7" & 8.9" Android Development] Cl4ncy:
You can NOT use TWRP then, it's for 3.2.3.2 and lower only. You can NOT downgrade below 3.2.8 due to rollback protection by Amazon.

So what you can do is to update to 4.5.2 (be sure to NOT do this by OTA! Will brick the HDX!), root with Kingroot, then install Safestrap v4 and use either Nexus or CM11. CM12 and SlimLP are NOT Safestrap compatible.

It so happens that CM11 works in secondary Slots, but it is recommended to use the stock slot due to higher battery usage of secondary slots (Nexus works in the stock slot only - WLAN won't work in secondary slots). Do NOT restore a backup of a secondary slot to the stock slot! This will overwrite Safestrap files and will brick the HDX!

[MENTION=5488402]Davey126[/MENTION] gave a good overview here, so read all the info and ask before you brick your HDX! If you don't follow the procedure 100% correctly, you will brick your HDX!

Kingroot requires a short internet connection, so just enable it to root, and disable right after success! Otherwise you will get updated to 4.5.5. and have to do the whole down- and upgrade process again, with all the risks!
[Kindle Fire HDX 7" & 8.9" Android Development] Rovers82517:
Legend, thank you, brain feels a little fried so having a vodka/monster drink lol, I'll get my head stuck in the link, cheers mate :)
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
FireOS v3 (eg: 3.2.8) is based on jellybean; v4 (eg: 4.5.2) is build on kitkat. The '13' prefix indicates you are using a 7" HDX; a '14' prefix refers to 8.9" devices.

You will be able to upgrade to FireOS v4.5.2, root, block OTA, install Safestrap v4 and the rom of your choice (Nexus v4 or CM11) without a USB tether. However, at times you will need to establish a brief network connection which also allows amazon to initiate an OTA update. It is very important you watch for this and break the connect before the entire file downloads (appx 800 MB). If the download completes/executes you will either be upgraded to an undesirable version of FireOS (best case) or your device will brick (most likely while on 3.2.8). Be prepared to do copious reading before attempting anything. Ask questions before acting; never guess.
[Kindle Fire HDX 7" & 8.9" Android Development] Rovers82517:
I think I'm blending completely different same but not threads here now, I've downloaded the relevant fireOs but ( I think this is the reason) I renamed the ota update file through system/etc/security to 'meh' now I download the 4.5.1 but "download failed" although it did in fact download all 800n odd mb... only bought this dang thing while I wait for a true next gen device (4gb ram, 3ghz processor) as I left my galaxy tab 4 10.1 in a taxi... £50 I paid for this '3rd gen Amazon' worse than a Tesco hudl tablet..... I might just snap the thing in half in a couple days.... some blinding cheap mtk devices out there... also tempted by the galaxy s... I need a noob proof single link... which having been a member of xda (pro but can't install pro without Google) I know is unlikely, people seem to enjoy saying the obvious "do some.searching, use the search function, read the getting started thread, meh" .... relentless reading has left me feeling drained, the update from the role back is saved on device but not installing.... should I just snap it in half now? Go back to Sammie?
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
Responded in an earlier post.

The 'noob proof' single link you seek simply doesn't exist. You'll need to do some legwork to upgrade your device. It's not a simple process but not terribly difficult either. If you can't invest the time (understandable...we all have lives) it is probably better to shelve your HDX and pick-up a easier device to mod. Suggest a 2103 Nexus 7 which is getting long in the tooth but readily available, easy to tweak and dirt cheap.
[Kindle Fire HDX 7" & 8.9" Android Development] Rovers82517:
I have the time, and the money, I go cheap because you become comfortable wasting cash... I've given this device 2 days attention now(ish) and with a couple more days will indeed had cm or nexus installed... I've been doing this for numerous devices, check my post history.... I never give, but smashing something because it's fundamentally wrong? I love doing it ;) others will read and see this... as far as I'm concerned the roll back was the challenge, gapps should be a simple zip. File... but Amazon and it's future drones to your door like all over android wrappers want y o u tied in, I dare say it's the same as jailbreaking a locked in iOS device.... titans rise, small fish die, remember Sega, even Nintendo? The noob versions out there... reason it's hard to find is this wrap-around open source alphabet os is.... why mess around when the next stage is ready by the time devs figure it out..... imo

---------- Post added at 11:16 PM ---------- Previous post was at 11:13 PM ----------

Not looking back, unless it's for passed family or friends... this gameboy shiz?..... I know you know....

---------- Post added at 11:30 PM ---------- Previous post was at 11:16 PM ----------

http://m.youtube.com/watch?sns=fb&v=O2_PAW_8fos
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
I do indeed remember ... plus a generation or two before (pwned a Timex Sinclair, Commodore 64, untold Trash 80s and regularly coded in Z80). All of which is irrelevant to today's devices and big money lockins. Glad to hear you have the time and experience to tinker with your HDX. Nice hunk of hardware. Everything you need is in the forums. Ask questions; lots of contributors here to help. Snap it if you must but it doesn't deserve that fate. Good luck.
[Kindle Fire HDX 7" & 8.9" Android Development] CrashThump:
There were several messages regarding installation of TWRP recovery through fastboot with unlocked bootloader.

I've tried without any success:

>fastboot -i 0x1949 flash recovery signed-apollo-twrp-2870.img
target reported max download size of 1073741824 bytes
sending 'recovery' (9350 KB)...
OKAY [ 0.406s]
writing 'recovery'...
OKAY [ 0.672s]
finished. total time: 1.078s

Recovery from Amazon has left untouched.

Can you please explain the issue here?
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
The messages appear normal. Curious the new image didn't take. Although I do NOT believe it will help you can try Flashify as it is capable of updating the recovery partition. Don't forget to backup the existing contents first (available within Flashify).

Your post history suggests other recent unexplained failures on your device (wifi, auto rotation, adaptive brightness) following an attempt to flash CM13. Also issues unlocking (although apparently it worked). Posts from late 2014 hint at crashing apps under Nexus v2 which as a strong track record for stability. I wonder if there is something subtly wrong with your device which is manifesting itself with the weird symptoms you are seeing.
[Kindle Fire HDX 7" & 8.9" Android Development] CrashThump:
Davey126, currently I have an unlocked bootloader, TWRP, working system (though with several issues).

I don't know how to lock the bootloader back but there can be a situation when both system and recovery are broken.

In this situation Flashify will be useless because if the device has a working system, recovery can be installed through adb using dd.

Thank you for a brief analysis, maybe you're right and my devices are faulty.

The real issue that I have 5 devices from 1 batch.

I've started to test a fresh ROMs on a 1 device because the Wi-Fi has been broken on it while using Nexus v2 under SafeStrap 3.72.

But 4 others are ok though there are some issues under Nexus v2.

Also I've found that on the device with a faulty Wi-Fi TWRP runs very bad: it crashes when running for around 30 minutes, it crashes when I unplug USB, etc. I have a garbage in adb terminal.

I was starting to think that this is a buggy Android.

Maybe there is a faulty RAM.

I'm going to start an upgrade for the 2nd device, will see if flashing from fastboot will be ok there.
[Kindle Fire HDX 7" & 8.9" Android Development] CrashThump:
I was able to write TWRP recovery on my 2nd device from the fastboot in a 1 try. Thank you.

On the 1st device previously recovery from Amazon somehow survived.

But I've tried to write TWRP from fastboot on the top of Amazon in the 2nd time for the 1st device: success.

I don't know what to do with the 1st one :( Maybe part of NAND is dead and read-only now, it can explain the issues.

On both devices I have a garbage in a command line of ADB in recovery:

~ # ←[6n

Does anybody have the same?
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
If reports from the field are representative 3rd gen HDX devices (8.9" models in particular) do seem to go flaky from time-to-time. Cruising Amazon feedback there are numerous posts from pure stock users claiming the device worked one day and died the next. Then again you don't know if junior used the tab for trampoline or dropped it in the toilet.
[Kindle Fire HDX 7" & 8.9" Android Development] CrashThump:
Garbage is present on 4 devices.

Recovery is very unstable.

Dimming of screen can cause the crash.

Also unplugging the USB oftenly causing the crash too.

One of my devices has turned off forever after the unplug. Brick, doesn't even charge. No harmful actions were performed under the recovery.

All other devices were able to boot ufter unplug but I had to press the button about 20 seconds.
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
- Interesting. Recovery stability (specifically TWRP 2.8.7.0) has not been an issue for the dozens/hundreds/thousands(?) who have flashed it over the past year. Yet you have difficulty on multiple devices.

- I may have lost focus on the nature of your inquiry/problem (didn't review post history). Perhaps you are trying to do something out of the mainstream.
[Kindle Fire HDX 7" & 8.9" Android Development] CrashThump:
Davey126, HDX aren't very popular models.

Unlock of the bootloader has became available later than a year after start of the sales.

Also it is not so easy for everyone to install custom ROM natively.

Amazon updates can't be rolled back to use unlock. I'm sure there are a lot of customers which are absolutely fine running latest FireOS.

The device is some kind of obsolete and it's not produced anymore.

All these facts limit the users of custom ROMs. I see there are not so many users of custom ROMs.

Also I'm the kind of person that will face each and every bug without any seeking of it. This was proved by several Android devices starting from 1.6. I'll never buy anything on Android anymore, Apple sometimes have the bugs too but there are no any broken custom ROMs and no need in them. My opinion is Android is broken by design. I'm happy that there are no any custom broken ROMs for my BlackBerry.

I see that every new ROM that made by ggow includes some old issues which sometimes can be found reported by lonely user somewhere in a thread. Each ROM has known issues.

Also I can see that ggow doesn't use HDX as a primary device anymore and he's not interested in development, these issues can't be unnoticed.

Just to prove my words regarding the bugs in HDX TWRP:
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
Thank you for surfacing your views on various devices. Very enlightening. I'm somewhat familiar with Amazon devices in general and the HDX in particular but will give your council the consideration it deserves. Have a great day.
[Kindle Fire HDX 7" & 8.9" Android Development] ggow:
- I share some of the same frustrations as you

- It is unfortunate that the hdx unlock didn't come sooner

- Amazon really went to town locking the devices down

- I am interested in developing the cm13 rom further. However I have a life with multitude of things going on and going through. This isn't a job, its something I enjoy, genuinely passionate about and share with the community here

- The HDX devices have been tough devices to develop due to lack of info or updated binaries and also my first

- its a miracle anything past KitKat actually works let alone been bug free

- to enable cm13 to run I had to use a mish-mash of binaries from various other devices to enable it to boot

- It doesn't look like Amazon is interested in these devices and Amazon if you are watching this it would be great to see some kind of support in providing hal source/drivers, updated proprietary blobs for marshmallow so we can get a stable user experience on aosp at least

- The HDX is still my primary tablet which I am still working on

- I have been working on other Amazon devices like the fire phone and Amazon fire tablet which is fully functional and 99.99% bug free

On Twrp recovery my device was faulty leading to the issue you mentioned- haven't had issues since.
[Kindle Fire HDX 7" & 8.9" Android Development] CrashThump:
I have five KFAPWI 16GB (Apollo) devices.

Some of them I had to roll-back to 14.3.2.3.2 from 14.3.2.4, some of them I had to upgrade to 14.3.2.3.2 from 14.3.1.0.

Then I used Multi-platform 1-Click bootloader unlock for 3rd Gen HDX (with VirtualBox).

I was unable to install the signed-apollo-twrp-2870.img recovery from fastboot - on a

couple

of working devices despite the successful installation text in fastboot.

However, installation using dd with su was always fine.

This recovery seems to be very unstable. All 5 devices had the same issues under recovery:

1. garbage in a command line of ADB

2. crashes (not always) when screen is turning off by timeout under TWRP - I recommend to turn this off immediately after installation

3. very often crashes when I unplug the USB cable under working TWRP (battery wasn't empty), devices were able to turn on only by holding pressing of the power button for about 20 seconds.
[Kindle Fire HDX 7" & 8.9" Android Development] EncryptedCurse:
What do you mean by the first one?

Anyways, I haven't run into any of these, but that may be because I have a thor.
[Kindle Fire HDX 7" & 8.9" Android Development] donharden2002:
I flashed it with flashify, works great. Still boots to safe strap though after I reboot twrp?

My own stupidity, had to download the safestrap app and uninstall it...lol
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
Cool. Don't forget to flash 3.2.3.2 bootloader update prior to flashing the rom of your choice (cm11/Nexus v4 if bootloader remains locked; those plus cm12/13 or SlimLP if unlocked). Be sure to verify md5; your device will brick if the bootloader update is corrupt.
[Kindle Fire HDX 7" & 8.9" Android Development] ka_putt:
Nothing to see here
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
According to several reports GPS on HDX does not work well for navigation. Slow to update and frequently looses its fix. Works better with static locations which makes sense given the device was never intended/marketed for navigation. Not an answer to your specific question but may temper additional efforts to get it working.
[Kindle Fire HDX 7" & 8.9" Android Development] ka_putt:
Ooops...i wrote in wrong forum...

It should be in orginal developemt selction by "[ROM] CM-13.0 + 3.4.0 Kernel [25 Jan 2016]"

Can any forum moderator move my post with logs there? Would be nice..^^
[Kindle Fire HDX 7" & 8.9" Android Development] laoman:
Can I install this while I am root with hdx nexus rom ?
[XDA Assist] gutek2184:
Hello friend i m new user, i have problem witch guophone G9500L

Quad core 6589

WVGA 854x480

Rom 4GB

Ram 1GB

problem is when i use oficial rom witch site needrom

now i have big problem phone work but lcd is white and have green line, nothing see.

How can i return to good condition phone ? I try to load many frimeware, and always show white lcd and line. LCD is good before flash all is good.

I think problem is driver lcd, can you hellp me ?
[XDA Assist] Darth:
Hi,

I can't find anything relevant on XDA for your device and issue. It sure looks like a hardware issue, but it could be software. Be sure the firmware you are flashing is for your exact model number, nothing else. If it still acts this way, I'd contact the manufacturer.

You can ask for other opinions here though if you wish,

> Android Development and Hacking > Android Q&A, Help & Troubleshooting

Good luck!
[XDA Assist] gutek2184:
So, can t use other rom, except chage botloader ??

I try to load many frimeware but always have white lcd?

Cant load similar frimeware ?
[XDA Assist] Darth:
You can try a custom rom.... But I'm not sure what you mean by you tried many firmwares? If you flashed firmware made for any other device, except your exact model.... You could have damaged the device.

But please, ask for further help in the thread I linked. I've found nothing that can help you unfortunately.

Thanks!
[XDA Assist] gutek2184:
i try to load rom via needrom with different firmware, and never brick phone, marked by botloader and upgrade frimeware, phone powers on but there are different forms of the white screen, on the other is completely white and the other with black and green line, can be heard as the phone starts up, running, but no image.

Can you send me link to custom rom ? witch i can try load.
[XDA Assist] Darth:
I already said, I can't find anything relevant on XDA for your device. And I gave you a link to post in for help.

XDA Assist is here to help navigate the site, not for support..... And I have pointed you to where to ask for help.

Thanks for understanding, thread closed.
[G3 Q&A, Help & Troubleshooting] baster72:
Is there any progress on this issue?
[G3 Q&A, Help & Troubleshooting] Neurom707:
Flash a stock Pre rooted rom problem solved
[G3 Q&A, Help & Troubleshooting] Ferindel:
A little bit of research never hurts, and you should've done that in the first place.
[G3 Q&A, Help & Troubleshooting] yasser1981m:
sorry for the silly question ... byt you mean using LG update tools !! and the ROM in this case should be Kitkat or lollipop ?

regards
[G3 Q&A, Help & Troubleshooting] GuestK00280:
There won't be a prerooted .kdz or root for 5.0. Never. Deal with it.

The only way to get root on lolipop is to flash 4.4.2 kdz, root it, install recovery and then install prerooted 5.0 rom

(i do understand that 5.0 MAY be rooted via an exploit at some point of time, don't make posts stating that.)
[Xposed Framework Modules] ZeroX7C:
My device isn't Samsung, but has a fingerprint reader, will this work?
[Xposed Framework Modules] invano:
Hi, I'm sorry but it won't work because it is built on Samsung Pass SDK
[Xposed Framework Modules] EXV:
This won't work on CM11 correct?
[Xposed Framework Modules] thering1975:
Galaxy tab s 8.4 can't get to settings it just force closes activated and rebooted
[Xposed Framework Modules] invano:
Yeah, I'm sorry for this. There is a bug with a library I am using in settings that causes fc also on galaxy S5.

I am working on it and I'll upload a new version in few hours.

Thank you for the info

Inviato dal mio SM-N910F
[Xposed Framework Modules] HorstiG:
Don't work on S5 (G900F) Stock KK 4.4 AllianceROM. Stock Fingerprint Sensor works.

HGT - Galaxy S3 - S5 - Tesla TTL7 - AllianceROM
[Xposed Framework Modules] JoshCiares:
Bug?

Samsung Galaxy S5 (NCE) (AT&T G900A)

Every time I open the app, it force closes. All I see is a white screen, and then the force close message. Whats going on?
[Xposed Framework Modules] invano:
There is something wrong with S5s and Tab Ss :confused: In the meanwhile I have just sent a pm to you guys to see if the new build finally solves this problem.
[Xposed Framework Modules] invano:
Ok, I have just uploaded a new version both on xposed repo and playstore. I think in few hours it will be up.

I have tested it on a Galaxy S5 with 4.4.2 and it seems to do not crash...let me know if there are still problems/crashes.
[Xposed Framework Modules] HorstiG:
Hi here a Log File

https://dl.dropboxusercontent.com/u/73964661/2015-01-03-02-38-41.txt

HGT - Galaxy S3 - S5 - Tesla TTL7 - AllianceROM

---------- Post added at 02:59 ---------- Previous post was at 02:43 ----------

Thanks for Update, now it works.

Does not work yet. I can now select an app. When I start it crashes FingerLock.

---------- Post added at 03:34 ---------- Previous post was at 02:59 ----------

New Catlogs, they are very large, but is not otherwise

https://dl.dropboxusercontent.com/u/73964661/Catlog.zip

HGT - Galaxy S3 - S5 - Tesla TTL7 - AllianceROM
[Xposed Framework Modules] invano:
New update on xposed repo and in few hours on PlayStore.

The problem is that the S5 does not support a transparency with value 0 imposed by Samsung.
[Xposed Framework Modules] HorstiG:
Very good, now everything works. Donation in the Playstore was made.

HGT - Galaxy S3 - S5 - Tesla TTL7 - AllianceROM
[Xposed Framework Modules] invano:
Honestly I don't know. I have to check it because that dialog is entirely managed by the Samsung SDK and it doesn't depend on the layout I have made.

I'll let you know.

Inviato dal mio SM-N910F
[Xposed Framework Modules] thahim:
Great I think this is first 3rd party app using finger print scanner.

I am using note 3 yet so cant use it.
[Xposed Framework Modules] HorstiG:
No Problem, it works great.

Thanks again for your App

HGT - Galaxy S3 - S5 - Tesla TTL7 - AllianceROM
[Xposed Framework Modules] deadtorights:
I notice you didn't put root requier but it's on google play. I just need an confirmation is for ROOT device only.

If so, you might want to add this in your first thread to avoid confusion.

Thanks!
[Xposed Framework Modules] invano:
I didn't write root required here since xposed already requires root... I wrote it on play store because it's easier there to have confusion. :)

Inviato dal mio SM-N910F
[Xposed Framework Modules] BlindWanderer:
I have this weird problem on my S5, I use this to lock firefox. As a result, sometimes during the unlock process, my default launcher is forgotten in the settings (so when the home button is pressed, I get a pop-up to pick one).

Firefox plus this do not seem like a happy combo. Task switching often causes Firefox to loose it's tabs.
[Xposed Framework Modules] invano:
Could you please send me a logcat taken when the launcher forgotten problem happens?

thanks

____ EDIT

you are right. at the moment firefox + fingerlock are not a happy combo..no way. On my note4 it is totally impossible to use firefox as locked app. I'll investigate on it
[Xposed Framework Modules] banttu:
Is it possible to make the white pop up black or dark? Great module it's much faster than the competing app FingerSecurity.
[Xposed Framework Modules] invano:
What do you mean with popup?

The one that shows up when the fingerprint is required?

If it is that, unfortunately it doesn't seem to me that Samsung SDK allows to change the color but my idea is to recreate it because the transparent layer is not supported by the s5. And yes... I can add the support to more colors or background images

Inviato dal mio SM-N910F
[Xposed Framework Modules] _Sofos_:
Subscribed, simple yet effective app. :)

A suggestion, adding a simple switch widget in the future allowing us to activate/deactivate it.
[Xposed Framework Modules] hatim369:
not working

On my galaxy s 5 it's not working I open apps and nothing happened :confused:
[Xposed Framework Modules] egren58:
So i tried it. Tested it for a while. I personally prefer fingerprint security atm but indeed keeping an eye on this.. I experienced lag n also noticed that sometimes when i would back out before unlocking it would send me to the main application.... Good job excited for this..
[Xposed Framework Modules] invano:
Could you please explain better the problem or send me a logcat?