So if I were to install a rom on an hdx,
Would the correct procedure be sideload the rom zip wiping dalvik/cache? Then sideloading gapps zip or whatever for apks?
Or would pushing the rom and gapps to sdcard and installing the 2 zips with twrp be alright?
Am I missing anything important? I read people talk about safestrap but oblivious as to what it is or if it matters.
I tried searching for a guide on the correct way to flash custom rom but didnt find anything.
Is there only 1 rom option these years for hdx? I only found 2 lineage options.
I read of AEX, aospextended, etc. but couldnt find them or links 404d. since those files are absent now I guess they are discontinued or deleted by their creator?
Any advice is appreciated.
AstralA said:
So if I were to install a rom on an hdx,
Would the correct procedure be sideload the rom zip wiping dalvik/cache? Then sideloading gapps zip or whatever for apks?
Or would pushing the rom and gapps to sdcard and installing the 2 zips with twrp be alright?
Am I missing anything important? I read people talk about safestrap but oblivious as to what it is or if it matters.
I tried searching for a guide on the correct way to flash custom rom but didnt find anything.
Is there only 1 rom option these years for hdx? I only found 2 lineage options.
I read of AEX, aospextended, etc. but couldnt find them or links 404d. since those files are absent now I guess they are discontinued or deleted by their creator?
Any advice is appreciated.
Click to expand...
Click to collapse
Hi, flashing ROMs usually will come device specific instructions. It can depend on the generation of your device. I searched flash custom ROM on HDX and got this. I hope it helps or at least gets the ball rolling for you.
flash custom rom on hdx - Google Search
[ROM][apollo, thor] Lineage-14.1 [17 MAR 2022]
Disclaimer /* * 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 the products you find...
forum.xda-developers.com
Does seem like theres directions but the directions seem to presume I know enough before hand. Lol
I dont know how to wipe data, it doesnt say much specifically.
Guess I can just go for it and see what happens.
But id rather know exactly so I know my ignorance wont end in a brick or faulty rom install.
I did read ggow say dirty flash was alright. But im not even sure what constitutes dirty flash.
Total green noob here. The only thing im not a noob at is bricking phones by modifying root files. Lol
Thanks for the quick response jonpjingleheimler. Awesome name btw.
Well if I ever figure out the proper way to do this I will write a guide with every possible specific I can muster.
AstralA said:
[ROM][apollo, thor] Lineage-14.1 [17 MAR 2022]
Disclaimer /* * 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 the products you find...
forum.xda-developers.com
Does seem like theres directions but the directions seem to presume I know enough before hand. Lol
I dont know how to wipe data, it doesnt say much specifically.
Guess I can just go for it and see what happens.
But id rather know exactly so I know my ignorance wont end in a brick or faulty rom install.
I did read ggow say dirty flash was alright. But im not even sure what constitutes dirty flash.
Total green noob here. The only thing im not a noob at is bricking phones by modifying root files. Lol
Thanks for the quick response jonpjingleheimler. Awesome name btw.
Well if I ever figure out the proper way to do this I will write a guide with every possible specific I can muster.
Click to expand...
Click to collapse
a lot of us started out not knowing a dirty flash from a clean flash. I think if you are serious about installing a custom ROM it would wise to locate the stock ROM for your device first. Most if not all stock roms for amazon tablets are available for download by Amazon. This way you can at least get back to stock usually without much hassle. YouTube is also a great resource for device specific instructions and sometimes a bit easier to follow. just keep that stock rom on hand. If you get into a bootloop or other crappy situation it's usually possible to get into the stock recovery perform a factory reset or use ADB sideload to flash the stock ROM.
Good to know. Thanks for the advice. I will definitely do that.
I look forward to getting to use apps that are from more recent years that actually work alongside website development.
Its rough finding functional apps when relegated to android kitkat.
Related
I am sure you all must have come across people who have bricked their phones. It mainly hurts to see some of your favorite developers brick their phones whilst developing kernels/roms/tools/scripts/etc and then you no more can enjoy their work without donating a new phone or money to buy a new one, understandably no dev would want to buy a new SGA again with their money, they would prefer a better device to explore and exploit :silly:.
There are some threads that give a basic idea as to how to avoid bricking. mainly these instructions would ask to follow exact instructions while flashing. But I assume the devs definitely do this and yet end up bricking, this increases my curiosity as to what led to bricking their devices. I am interested in knowing the stages during development that can cause bricking. But this thread is not limited to bricking during development, but in general what all can get your SGA bricked.
If you have ever bricked your device (or know someone who has and how), if you could please list down
how it happened
what did you try to recover
whether it was successful
I will list it out, though there are countless more possibilities...
Wrong kernel
Wrong meta-inf
Wrong recovery
Buggy recovery
Flash failure
Messed up boot loader(could be caused by many things)
Wrong ROM(rom created for another phone)
Using apps which are incompatible for a certain device, like Rom manager
That's all that is coming to my head right now..
(By wrong, I mean, things from another device)
Controversies,controversies everywhere :what:
Prawesome said:
I will list it out, though there are countless more possibilities...
Wrong kernel
Wrong meta-inf
Wrong recovery
Buggy recovery
Flash failure
Messed up boot loader(could be caused by many things)
Wrong ROM(rom created for another phone)
Using apps which are incompatible for a certain device, like Rom manager
Click to expand...
Click to collapse
Thanks Prawesome!!!
I am also looking for particular instances, from people who have bricked. Directly from the horses mouth if you may
jugalthakkar said:
Thanks Prawesome!!!
I am also looking for particular instances, from people who have bricked. Directly from the horses mouth if you may
Click to expand...
Click to collapse
Unfortunately for you and fortunately for me, I haven't ever bricked my device
Controversies,controversies everywhere :what:
I was a noob back then and installed clockworkmod recovery by rom manager. Was hardbricked and never booted back up. Tried every thing. Was not successful. Luckily gave it to service centre with a lame excuse.
2nd time i bricked it is when i accidently formated sdcard in clockworkmod recovery when i was going to install rom. Luckily was a softbrick, so i fixed it with odin. Good old noob days
Sent from my GT-S5830 using xda app-developers app
Hi,
I just got my HDX und now i want to install custom recovery and root the device. I have just a few questions before i do so an got no exect answers by searching the forum:
1. If I do a backup with custom recovery can I go fully back to stock?
2. Is there some sort of Factory Image to download to override custom revocery?
3. Can I Undo and go back to stock recovery If i have to send the device back to Amazon?
I just want to know if I can totaly revert all changes bevore I change something.
thx
maroc84 said:
Hi,
I just got my HDX und now i want to install custom recovery and root the device. I have just a few questions before i do so an got no exect answers by searching the forum:
1. If I do a backup with custom recovery can I go fully back to stock?
2. Is there some sort of Factory Image to download to override custom revocery?
3. Can I Undo and go back to stock recovery If i have to send the device back to Amazon?
I just want to know if I can totaly revert all changes bevore I change something.
thx
Click to expand...
Click to collapse
If you are new to this device you probably should read the first post here http://forum.xda-developers.com/showthread.php?t=2786190.. And the answer to all your questions are technically yes. If you do not brick or break your tablet anywhere along the way and providing that you are willing to do all homework necessary and then some before attempting to do anything.. You probably need to read through all the threads about brick devices to know what things not to attempt that will cause you to break your device.. Remember all the information is here if you learn how to use this forum and remember each section of the forum has several pages of threads of information.. You have a whole lot of reading to do if you do not want to end up another of this devices victims lmao
Don't get me wrong. I own a nexus 5 and the nexus 7 (2013) (rooted, custom kernel, exposed etc.) but due to the open system and bootloader so as the asop makes it easier to handle it. I already read the warnings but the Windows supported root tool should be a easy way.... not?
Okay obviously
maroc84 said:
Don't get me wrong. I own a nexus 5 and the nexus 7 (2013) (rooted, custom kernel, exposed etc.) but due to the open system and bootloader so as the asop makes it easier to handle it. I already read the warnings but the Windows supported root tool should be a easy way.... not?
Click to expand...
Click to collapse
there is not a problem getting it rooted you may have read the warning but you're not understanding it.The problem is not rooting the device. The problem is what people are deciding to do with their root access . And it may be my imagination or may not but this seems to be a favorite tablet for mommy and daddy to buy the kiddies.. Then they come here not knowing how to do their own research and find the easy way to root their device , There n fine there again not a real problem it's what they are doing ...BRICKING! There again not really a problem for me but when they come to this forum acting like somebody owes them something or somebody better step up and hurry hurry come help them fix their device before mommy and daddy find out ... Burying perfectly good information that I like to access under redundant questions because they are too lazy to do their own homework .. Repeatedly asking the same questions over and over again that have already been answered over and over again they just refuse to read the information and expect others to first to come to their special lil thread and inform them like this is kindergarten again . And somebody should be holding their hand because mommy and daddy bought them a special kindle fire..THAT IS LOCKED DOWN.. With no fast boot capabilities currently working there is a lot of talk about it but no consistent.... Repeat there is not a one click fix for this device ....... unlike most other tablets like I said one of your questions asked if you can just flash and fix ... At this time NO. If you really know what you are doing and you are not afraid of or can afford to turn your tablet into a paperweight.. There are ways to get your system flashed too repair mistakes or goofy behavior (even return to stock) but not from BRICK STATE. Long story short your 1 Click Easy Way to root.. Through ignorance, laziness , and the comprehension level of a fruit fly .. For this device in the wrong hands might as well be a sledge hammer ... Repeat in no way is a Nexus 5 ,at the moment remotely similar other then android base, to this tablet... Is what you should have gotten from the thread that I posted a link to... flash and modify at your own risk and Responsibly.. Nobody here is responsible for anything you do to your tablet. Or responsible for coming to rescue you if or when you screw it up... Please read all the brick threads to save everybody lots of famed face palms and headaches... Us and yourself trust me.
Thanks. I know it can be depressing to tell people "you question or problem was answered just two days ago, just read and collect the right information you need" I don't want to change necessary files like build.prop or do things where there is an exact warning to do so because it's not really stable...
The warning pinned to this forum just got me unquestioning if there are serious problems in every usually customisation (root, custom recovery, gapps) so doing just that could probably brick the tab because maybe the closed system makes everything risky and unpredictable in contrast to a vanilla android device.
well
maroc84 said:
Thanks. I know it can be depressing to tell people "you question or problem was answered just two days ago, just read and collect the right information you need" I don't want to change necessary files like build.prop or do things where there is an exact warning to do so because it's not really stable...
The warning pinned to this forum just got me unquestioning if there are serious problems in every usually customisation (root, custom recovery, gapps) so doing just that could probably brick the tab because maybe the closed system makes everything risky and unpredictable in contrast to a vanilla android device.
Click to expand...
Click to collapse
Well for example I am only a mechanic I'm 42 years old I am not well-versed in computers but android have been a hobby of mine for about five years .. But I have very little problems following directions. And I have been able to accomplish anything I wanted to do with many many phones and tablets including this one... So if you're willing and have the understanding that this thing is very fickle and likes to actup
Where other devices would not be problems... It can be a very nice device for the right person and a very big headache for the wrong one. There are currently a lot a bugs with pretty much anything that you try to do with this thing if not done with absolute precision and patience. And perseverance. I currently own three different HDX tablets with several other Samsung.. And I switch frequently. I do have Google on my HDX but I do not depend on them for all of my Google needs. Remember at least for now while these things are locked up tight they are pretty much only an Amazon media device along with if you are willing to brave and yada yada yada you may get some Google services working like many of us have. Enjoy all of my HDX thoroughly but I also have a understanding of the current limitations.
Years ago I flashed wrong images to some Samsung, and it didn't welcome that. Now I want to get that thing alive again, and I'm trying around.
I used the bootloader to give me some info's: re-wrote the updater-script of some rescue package, and realized that the system partition - AKA /dev/stl9 - can't be mounted.
No prob, the knowing says. I took heimdall and flashed some - think so - reliable image. Bad luck. After that, my pretty good rescue didn't run any more, no chance to get any info from the device.
I tried CWM, version 5.0.2.6, with various procedures recommended in the internet, but also: bad luck.
Now I'm asking you, most experienced gents, for help. I'd better say, informations:
I need to know
* what machine is that thing, and what compiler do I have to take? (I'm familiar with gcc; my host cross-compiles kernels targetting RPI's, Beagle's ...)
* where's the CWM source code? G didn't bring any sufficient result.
because I intend to
* start adbd on the device despite any problems with failed mounts
* see what's wrong
* partition and install the system from scratch, if needed.
Thanks for any advice. And recommendations going another way.
SM
softmirko said:
Years ago I flashed wrong images to some Samsung, and it didn't welcome that. Now I want to get that thing alive again, and I'm trying around...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to take a look at the following threads and post your question, if needed, within one of them.
https://forum.xda-developers.com/showthread.php?t=2089279
https://forum.xda-developers.com/showthread.php?t=1551156
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Update March 23, 2019: I'd like to apologize to everyone. It looks like I am not going to be able to actively keep this thread updated like I used to. I have had too much going on at home an work and it doesn't look like it's going to settle down any time soon. The thread is still usable so I will leave it open for discussion.
Team Win Recovery Project​
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, fires, rigged elections,
* specks of dusk sitting on cursors, cursors that mock you--waiting for cursor
* revenge, thermonuclear war, or you getting fired because the alarms failed
* and you could not call in.
*
* Please ensure you have an advanced understanding of this device before
* flashing it! YOU are choosing to make these modifications or your own free will.
This is the first official build of TWRP for the Motorola Moto G6 (ALI)!
Notes:
Decryption is finicky: Currently only vold decryption is working. This image must be flashed to properly decrypt. Updates may cause issues with decryption.
If you format data (Not just factory reset) after decrypting you must reboot into recovery and format again.
If you are unable to unlock your phone after restoring a data backup that had a lock code on it (and TWRP is able to decrypt using default password) you'll need remove the '/data/system/locksettings.db' while in TWRP. After that you should be able to reboot into Android and set a lock code. If you cannot then please use this thread as a guide and try again. Bascially you just delete more, however I was able to boot after just deleting the one file with a pattern set (Maybe random luck, maybe not)
If you have any other issues please let me know and I'll work toward fixing them! AS ALWAYS, IT'S YOUR RESPONSIBILITY IF YOU USE THIS SOFTWARE
Known Issues:
I have just noticed some odd behaviour if you input an incorrect decryption password/pattern/etc in twrp. It can cause an issue while entering the lockscreen password/pattern/etc while booting up. Under normal circumstances these two are the same, hence why restoring can also cause a similar issue, though that one is easily fixable. The onIy way to clear the decryption pass is to format. I am unsure at the moment what is causing this, but clearly it has something to do with the decryption. At this time I'd say it'd be best to remove your current lockscreen password/pattern/etc before booting into twrp to avoid this issue. A possible work-around would be to reboot to twrp, enter the correct password, back up your data, format (reboot to twrp and format again), then restore your backup (and possibly need to delete the '/data/system/locksettings.db' file. Your data would still exist that way. I am going to work to fix this asap and maybe see if I can get another build without decryption made for official use for now.
Flashing zips that require BusyBox will not work with the official version right now. I've built an unofficial version to use until a new official build is triggered.
ALI's Changelog: Post #2
Download: twrp.me Download
Unofficial Download (updated more often): twrp-v3.2.3-unofficial-ali-20181110.img
Simple Installation Method:
1) boot to fastboot
2) fastboot flash recovery <twrp-image-name>.img
Other instructions are available on the Official download page. It's up to you to backup your factory recovery first if you wish to have a backup: Post #3
Thanks to the TWRP team and everyone who has put in effort to make these things possible!
@Jleeblanch - Wonderful advice and guidance
@Dadud - testing
@ Everyone at github
@ XDA and the people who provided TWRP compiling threads
If I've forgotten someone who you think needs mention please let me know!
* This page will continue to be edited as more information comes
XDA:DevDB Information
[RECOVERY][OFFICIAL] TWRP v3.2.3 [2018-10-20], Tool/Utility for the Moto G6
Contributors
dejello
Source Code: [url]https://github.com/TeamWin/android_device_motorola_ali[/URL]
Version Information
Status: Stable
Current Stable Version: 3.2.3-0
Stable Release Date: 2018-10-20
Current Beta Version: 3.2.3 Unofficial
Beta Release Date: 2018-11-10
Created 2018-10-21
Last Updated 2018-11-10
Changelogs
TWRP Changelog:
v3.2.3 changelog
ALI's Official Changelog:
v3.2.3-0 (Oct 20, 2018)
- N/A, first build!
ALI's Temp. Unofficial Changelog:
v3.2.3 (Oct 31, 2018) (This log will get moved to official when it gets updated with these changes)
- Stop using toybox (Use busybox!)
- Added vendor image mount point
Factory Backup Information
It's up to you to determine if you want/need a factory recovery image backup before flashing:
To boot twrp first (it will fail decryption, don't worry about it) just do the following while replacing <twrp> with the actual file name.
Code:
fastboot boot <twrp>.img
Then to back up your stock/factory recovery while booted in TWRP do the following.
Code:
adb pull /dev/block/bootdevice/by-name/recovery stockrecovery.img
First [emoji14]
For real tho, nice work and congrats [emoji41]
Woot Woot! Congrats bro?
Lockscreen after restore
Hello, this method (delete lockscreen) after restore backup works for me to ?
Decryption doesn't work for me. XT1925-6 Ali
giant22000 said:
Decryption doesn't work for me. XT1925-6 Ali
Click to expand...
Click to collapse
I'll need more details if I'm to look into it. I also have an xt1925-6. Any logs? What version software are you running? What kind of lock screen are you using (pin, password, pattern, none, etc)? What happened from booting twrp up to the point of decryption failure? The more information I have the better chance I have at rectifying the issue.
[EDIT] I just did some messing around and came across something I hadn't seen before:
I have just noticed some odd behaviour if you input an incorrect decryption password/pattern/etc in twrp. It can cause an issue while entering the lockscreen password/pattern/etc while booting up. Under normal circumstances these two are the same, hence why restoring can also cause a similar issue, though that one is easily fixable. The onIy way to clear the decryption pass is to format. I am unsure at the moment what is causing this, but clearly it has something to do with the decryption. At this time I'd say it'd be best to remove your current lockscreen password/pattern/etc before booting into twrp to avoid this issue. A possible work-around would be to reboot to twrp, enter the correct password, back up your data, format (reboot to twrp and format again), then restore your backup (and possibly need to delete the '/data/system/locksettings.db' file. Your data would still exist that way. I am going to work to fix this asap and maybe see if I can get another build without decryption made for official use for now.
I have added this to the first post.
Damn thanks !
Hi. First thank for the contribution.
I would like to know if someone has the stock twrp, modeled 1925-1. When I modified my stock twrp, I made a back up, but I lost it.
I would like to update my security patch, but I can not because it has modified the twrp.
aaleej0 said:
Hi. First thank for the contribution.
I would like to know if someone has the stock twrp, modeled 1925-1. When I modified my stock twrp, I made a back up, but I lost it.
I would like to update my security patch, but I can not because it has modified the twrp.
Click to expand...
Click to collapse
So I guess I will be the one to say it. I'm giving you one warning about this. It's against forum rules to post on multiple threads with the same subject. I've answered your question on the Ali stock firmware thread also. Please read guides and threads instead of skimming through them because it's been answered multiple times. Next time you do this and post the same thing on multiple threads I will be the one reporting you. Have a good day.
I have added an unofficial build tonight (Oct/31/2018) to fix an issue flashing zips that need busybox (Resurrected Kernel, etc) versus toybox. It also adds a 'vendor image' mount point for use in backups and flashing. Once official gets updated this unofficial build will be removed.
Hello, could you consider supporting the Moto g 6 play xt922-4 I'm welling to help out with logs or anyfile if needed.
jglm4u said:
Hello, could you consider supporting the Moto g 6 play xt922-4 I'm welling to help out with logs or anyfile if needed.
Click to expand...
Click to collapse
There are certain reasons there is no official twrp for our moto g6 play devices yet. Is there issue your having?. Dejello supports the regular g6 and for all intensive purposes I've being doing support for the g6 play.
jglm4u said:
Hello, could you consider supporting the Moto g 6 play xt922-4 I'm welling to help out with logs or anyfile if needed.
Click to expand...
Click to collapse
ninjakira said:
There are certain reasons there is no official twrp for our moto g6 play devices yet. Is there issue your having?. Dejello supports the regular g6 and for all intensive purposes I've being doing support for the g6 play.
Click to expand...
Click to collapse
I don't have access (well, sort of but not really) to a g6 play. My son has one, but it's not unlocked or anything and I won't experiment on his phone without having everything backed up.... Besides, getting the damn thing away from him for extended periods when he isn't in trouble would be something.... I thing it's glued to his face or something.
I am also not up to date on any issues or reasons why twrp isn't official for the g6 play. Be aware that even this version for the g6 has some issues (workarounds are available for everything so you won't lose anything) still.
I've been debating looking into it, but haven't yet for reasons above.
dejello said:
I don't have access (well, sort of but not really) to a g6 play. My son has one, but it's not unlocked or anything and I won't experiment on his phone without having everything backed up.... Besides, getting the damn thing away from him for extended periods when he isn't in trouble would be something.... I thing it's glued to his face or something.
I am also not up to date on any issues or reasons why twrp isn't official for the g6 play. Be aware that even this version for the g6 has some issues (workarounds are available for everything so you won't lose anything) still.
I've been debating looking into it, but haven't yet for reasons above.
Click to expand...
Click to collapse
I just had a good laugh about your son's g6 play being glued to his face ??I could definitely say I don't look at or use my phone as much as the kids now a days and I'm 27 lol I worked ina mall so I seen that alot lmao and what all would you need from someone to attempt an official twrp for it? Ill do my best to provide you with what's needed. The patched twrp for the g6 play should be a good start. I would have already started on it myself but i am not able to get it going because i don't trust my laptop (it came with Vista) and it likes to randomly reboot and all this marvelous stuff lol
ninjakira said:
I just had a good laugh about your son's g6 play being glued to his face ??I could definitely say I don't look at or use my phone as much as the kids now a days and I'm 27 lol I worked ina mall so I seen that alot lmao and what all would you need from someone to attempt an official twrp for it? Ill do my best to provide you with what's needed. The patched twrp for the g6 play should be a good start. I would have already started on it myself but i am not able to get it going because i don't trust my laptop (it came with Vista) and it likes to randomly reboot and all this marvelous stuff lol
Click to expand...
Click to collapse
When I get a chance I can take a look at some things. But looking at github I do see at least one device tree being worked on for jeter
ninjakira said:
I just had a good laugh about your son's g6 play being glued to his face [emoji23][emoji23]I could definitely say I don't look at or use my phone as much as the kids now a days and I'm 27 lol I worked ina mall so I seen that alot lmao and what all would you need from someone to attempt an official twrp for it? Ill do my best to provide you with what's needed. The patched twrp for the g6 play should be a good start. I would have already started on it myself but i am not able to get it going because i don't trust my laptop (it came with Vista) and it likes to randomly reboot and all this marvelous stuff lol
Click to expand...
Click to collapse
I wouldn't trust Windows either. Personally, I'd wipe Windows right off it and run Linux. Linux would breathe new life into a laptop that came with Vista lol.
Jleeblanch said:
I wouldn't trust Windows either. Personally, I'd wipe Windows right off it and run Linux. Linux would breathe new life into a laptop that came with Vista lol.
Click to expand...
Click to collapse
I do have it on dual boot with Ubuntu 18.10 it's Just the the random rebooting is persistent still but yeah I personally use use linux distos over Windows lol. My next paycheck I'm having our local computer store called microcenter help me out with a new laptop at least lol
dejello said:
When I get a chance I can take a look at some things. But looking at github I do see at least one device tree being worked on for jeter
Click to expand...
Click to collapse
I'm not able to send the screenshot of termux so here they are. Recovery is 16 mb
I have an old Fire and I want to install a custom ROM on it but I need some help figuring out how to proceed. I've been reading a lot of threads around here (primarily this one, this one, this one, and this one) and I've successfully unlocked the bootloader but I'm hesitant to start flashing things without knowing what's current and correct. I've seen a lot of different approaches and different files and commands in various threads and some of those commands don't work anymore (e.g. any fastboot command with -i flag) and some of the links to files are dead (both goo.im and teamw.in seem to be defunct and pretty much all the links here are broken) and just the sheer volume of information here is a bit overwhelming. I also read somewhere that TWRP v. 2.7 would be better for this device than 2.8 but now it's in version 3.5 I think and I'm not sure if I should still try to find 2.7 or not?
So, I guess the main thing I'm trying to figure out is what versions of FFF and TWRP I should be using and where I can get them. It would also be great if someone could point me to the guide or guides that will be most current and relevant for my device.
Thanks!
Kindle Fire HDX (3rd Gen, Thor)
Fire OS 4.5.5.3
Windows 10 Pro 21H1
I would install latest TWRP:-
[RECOVERY][UNLOCKED BL] TWRP 3.5.0_9-1
/* * 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 the products you find here...
forum.xda-developers.com
Best 2 custom Roms in my opinion are LineageOS 14.1 & Divest OS, both are based on Android 7.1.2
Divest OS i think has bit better battery life and performance but you wont be able to use some apps that require google. LineageOS can have root if you want and install google playstore.
I use DivestOS and installed Aurora Services to go with Aurora Store (great alternative to google playstore, i think this is way better). And i have F-droid. Slight glitch with DivestOS is you cant switch it off via power button and tapping on power off, you have to press down on power button for about 20 seconds so its not an issue really.
The creator of LineageOS 14.1 is apparantly going to continue with it with some updates. DivestOS has monthly updates.
Thanks! I went with LineageOS.