I've been doing a lot of research and following some guides and I Have searched some posts here, but there's insutrctions burried inside of threads that are 75+ pages long and I hate to jump in the middle of a thread when I don't know any context.
I'm trying to flash LineageOS on a 3rd gen 8.9" (apollo) kindle. It's rooted and I'm running software 4.5.5.3.
I have done firmware flashing before, so I'm not new to this. My primary OS is linux and I just used ADB and fastboot there to fix my phone. I have a windows machine with fastboot and all the tools as well. I just need access to the proper instructions.
That's the keyword, PROPER Instructions. I don't want to jump in the middle of a thread with some instructions from an older software release that will brick my kindle.
RNZL3R said:
I've been doing a lot of research and following some guides and I Have searched some posts here, but there's insutrctions burried inside of threads that are 75+ pages long and I hate to jump in the middle of a thread when I don't know any context.
I'm trying to flash LineageOS on a 3rd gen 8.9" (apollo) kindle. It's rooted and I'm running software 4.5.5.3.
I have done firmware flashing before, so I'm not new to this. My primary OS is linux and I just used ADB and fastboot there to fix my phone. I have a windows machine with fastboot and all the tools as well. I just need access to the proper instructions.
That's the keyword, PROPER Instructions. I don't want to jump in the middle of a thread with some instructions from an older software release that will brick my kindle.
Click to expand...
Click to collapse
Appreciate the upfront legwork.
HDX bootloader must be unlocked to install a non-KitKat based custom ROM. Fortunately, that's an easy task given your familiarity with Linux. PM the OP in the linked thread for a copy of the 1-click unlock script. Same tool can also flash an appropriate TWRP image which is the preferred method for flashing custom ROM on this device. Bounce back with any immediate questions.
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
Davey126 said:
Appreciate the upfront legwork.
HDX bootloader must be unlocked to install a non-KitKat based custom ROM. Fortunately, that's an easy task given your familiarity with Linux. PM the OP in the linked thread for a copy of the 1-click unlock script. Same tool can also flash an appropriate TWRP image which is the preferred method for flashing custom ROM on this device. Bounce back with any immediate questions.
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
Click to expand...
Click to collapse
I did read through the first few pages of that thread. Why doesn't the Op just post the link up instead of dealing with PMs? I found that sketchy
RNZL3R said:
I did read through the first few pages of that thread. Why doesn't the Op just post the link up instead of dealing with PMs? I found that sketchy
Click to expand...
Click to collapse
Members don't read, misuse the tools, fain rage and demand support. There's always the manual approach if you prefer not to engage OP. I rarely post my work (here) for similar reasons.
Davey126 said:
Members don't read, misuse the tools, fain rage and demand support. There's always the manual approach if you prefer not to engage OP. I rarely post my work (here) for similar reasons.
Click to expand...
Click to collapse
I got the 1-click file, and...well....it isn't detecting my kindle. Developer options is enabled, and ADB is on. It's plugged in and fully charged. yet, 1-click says there's no device detected.
RNZL3R said:
I got the 1-click file, and...well....it isn't detecting my kindle. Developer options is enabled, and ADB is on. It's plugged in and fully charged. yet, 1-click says there's no device detected.
Click to expand...
Click to collapse
Have you validated the Linux host can see and communicate with the HDX when 'manually' tethered? Obviously that's a prerequisite. If not try a different cable (often the culprit!) along with different USB ports. Avoid external hubs. If still no joy try tethering to a different host (regardless of OS) to rule out a bad port on the tablet.
Davey126 said:
Have you validated the Linux host can see and communicate with the HDX when 'manually' tethered? Obviously that's a prerequisite. If not try a different cable (often the culprit!) along with different USB ports. Avoid external hubs. If still no joy try tethering to a different host (regardless of OS) to rule out a bad port on the tablet.
Click to expand...
Click to collapse
The tablet is definitely detected and I can browse the storage. It just doesn't get detected by the 1click.
Are there any other ways to unlock the boot loader and flash a Rom?
RNZL3R said:
The tablet is definitely detected and I can browse the storage. It just doesn't get detected by the 1click.
Click to expand...
Click to collapse
Reach out to the 1-click developer; he's pretty knowledgeable/resourceful and can probably help.
RNZL3R said:
Are there any other ways to unlock the boot loader and flash a Rom?
Click to expand...
Click to collapse
Linked 3 posts back.
I have followed this guide from @ReichMann and successfully unlock bootloader, install TWRP and get my HDX run both Apollo and Thor running Nougat in 1st try with no problem, he also attached all the file you'll need:
https://forum.xda-developers.com/showpost.php?p=75284993&postcount=1006
RNZL3R said:
The tablet is definitely detected and I can browse the storage. It just doesn't get detected by the 1click.
Are there any other ways to unlock the boot loader and flash a Rom?
Click to expand...
Click to collapse
I had some issues with Virtual box on Ubuntu. In case you are using a similar setup, check this post:https://forum.xda-developers.com/showpost.php?p=76730389&postcount=346
Related
Hey guys ive got a hdx 7' RUNNING FIRE OS 3.2.4 everything i have been reading is saying that this version is somewhat unique in that there are a few roms availible mostly from safestrapp but most are not, twrp requires 3.2.3 and earlier as well as the bootloader unlock procedure. Can anyone point me in the direction on how to downgrade to one of the earlier versions. Currently i am rooted, ota disabled via: hdxtookit, i had safestrapp and a asop rom installed but was getting google play services stopped working error messages and restored to factory because i havent used the kindle in a year. Anyways i'm looking to get back into it and got cm 12.1 on my sgs3 and wanted to get something similar but keep runninginto problems with my version fire os. So just need a quick link to a roll back procedure in english and i should be able to do the rest from unlock - twrp - roms etc. I've been searching off and on the past few weeks but do not find anything definitive so i decided to finally ask to get an answer thanks for any and all help.
131 views no replies can anyone guide me to a solution?
rbkelley89 said:
131 views no replies can anyone guide me to a solution?
Click to expand...
Click to collapse
So basicaly for unlock BL and real TWRP you need have FW between x.3.1.0 and x.3.2.3:
Depending on your computer skills rollback can be achieved easy (or not).
Guide in english? Here, but you must mess with build.prop and on hdx especialy its really dangerous procedure - if you made simple mistake, it could be your last with that device and deadly for it for sure.
Sorry, I will not guide you through the process, if you feel you are lost, you can ask davey126 for help, but he answered this type of question soo many times . . . you can try read his posts before you ask him, there is high posibility he answered it somewhere...
jeryll said:
So basicaly for unlock BL and real TWRP you need have FW between x.3.1.0 and x.3.2.3:
Depending on your computer skills rollback can be achieved easy (or not).
Guide in english? Here, but you must mess with build.prop and on hdx especialy its really dangerous procedure - if you made simple mistake, it could be your last with that device and deadly for it for sure.
Sorry, I will not guide you through the process, if you feel you are lost, you can ask davey126 for help, but he answered this type of question soo many times . . . you can try read his posts before you ask him, there is high posibility he answered it somewhere...
Click to expand...
Click to collapse
@jeryll is spot on. There are a ton of helpful posts from a variety of authors that could get you started. This one comes to mind although there are many others. Lots of folks here are happy to answer targeted questions but you have to do your homework first. Read (and read some more), go slow, stop and post a question if unsure, don't take chances. Good luck.
Random thoughts:
- I strongly encourage upgrading to 13.3.2.5 or 13.3.2.6 prior to rolling back to 13.3.1.0. Lower risk and clears out 'crud' that could ruin your day.
- Use HDX toolkit to block/unblock OTA. Don't mess with any other technique; bad day follows.
- Once OTA is unblocked stay off WiFi. Period. Do transfer/installs via tether. Belt-and-suspenders types engage airplane mode and delete existing WiFi profiles too.
- Double check every action before executing. Stop and ask questions if unsure. Juggling babies is safer than taking a wrong turn (ok ... maybe that's a bit extreme).
- Many guides suggest bootloader unlocking before installing TWRP recovery. My comfort meter goes the opposite way. Your call. There are decent arguments for both approaches.
Davey126 said:
@jeryll is spot on. There are a ton of helpful posts from a variety of authors that could get you started. This one comes to mind although there are many others. Lots of folks here are happy to answer targeted questions but you have to do your homework first. Read (and read some more), go slow, stop and post a question if unsure, don't take chances. Good luck.
Random thoughts:
- I strongly encourage upgrading to 13.3.2.5 or 13.3.2.6 prior to rolling back to 13.3.1.0. Lower risk and clears out 'crud' that could ruin your day.
- Use HDX toolkit to block/unblock OTA. Don't mess with any other technique; bad day follows.
- Once OTA is unblocked stay off WiFi. Period. Do transfer/installs via tether. Belt-and-suspenders types engage airplane mode and delete existing WiFi profiles too.
- Double check every action before executing. Stop and ask questions if unsure. Juggling babies is safer than taking a wrong turn (ok ... maybe that's a bit extreme).
- Many guides suggest bootloader unlocking before installing TWRP recovery. My comfort meter goes the opposite way. Your call. There are decent arguments for both approaches.
Click to expand...
Click to collapse
How can I upgrade to 3.2.5 or 6. I believe I blocked ota it's been so lo.g ago I searched.for.the files and didn't see them anywhere so I assume it's still active even after factory restoration. And it's possible to twrp without unlocked boot loader? I didn't know that. What are the pros and cons. I'm not a dev so I went need to play around with much just want to rid of fire os and use a cm or nexus. If I can do that safety id LOVE that but still willing to try the adk route. Thanks for the info guys.
rbkelley89 said:
How can I upgrade to 3.2.5 or 6. I believe I blocked ota it's been so lo.g ago I searched.for.the files and didn't see them anywhere so I assume it's still active even after factory restoration. And it's possible to twrp without unlocked boot loader? I didn't know that. What are the pros and cons. I'm not a dev so I went need to play around with much just want to rid of fire os and use a cm or nexus. If I can do that safety id LOVE that but still willing to try the adk route. Thanks for the info guys.
Click to expand...
Click to collapse
Locate HDX toolkit in the Android Development thread and try to remove the OTA block that way. Keep WiFi off or you might receive an unwanted update.
Although not recommended twrp can be installed with a locked bootloader.
Travelling this week so can't get into more detail. Suggest you keep reading. Don't do stuff unless you are absolutely confident in your skills, knowledge, risks and expected outcome(s). Post questions. Many folks willing to help if you have done your homework. Sorry for brevity ...
Yes, be ESPECIALLY careful with build.prop. I learned this the hard way. They is nothing like Odin for Samsung that can save you.
XxD34THxX said:
Yes, be ESPECIALLY careful with build.prop. I learned this the hard way. They is nothing like Odin for Samsung that can save you.
Click to expand...
Click to collapse
The path I am suggesting does not involve modifying build.prop.
Can't he just use the rollback Images provided by ggow?
Must stay on 3.2.4. then though.
Cl4ncy said:
Can't he just use the rollback Images provided by ggow?
Must stay on 3.2.4. then though.
Click to expand...
Click to collapse
Nice finding, I absolutely forgot that this existed, of course he can use that thread with rollback images to downgrade to x.3.1.0! Then he can install TWRP etc... (as I did in the past - proof below )
jeryll said:
Thank you sir, successfully rolled back to 14.3.1.0, installed TWRP 2.8.1.0 and now I will play a little with TWRP
Click to expand...
Click to collapse
Cl4ncy said:
Can't he just use the rollback Images provided by ggow?
Must stay on 3.2.4. then though.
Click to expand...
Click to collapse
Nice find! I had seen that post (long ago) but the significance never set in for Safestrap v3 users with FireOS xx.3.2.4 in the stock slot. Even if not rocking SS it is probably easier (and definitely a lot safer) to install SS vs rolling up just to roll back or messing with build.prop.
The OTA block could still be a problem as the @ggow's procedure still involves Amazon's native update mechanism.
Edit: Disregard OTA comment as modified 3.2.4 goes on first and should restore OTA capability (more importantly the ability to detect and process FireOS bin files in the appropriate location).
I upgraded from 13.3.2.4 to 13.3.2.5 and edited build.prop, so now my version shows 13.3.0.9. I downloaded 13.3.1.0 rom from Amazon server. When updating I always received the following error message "Unable to complete update because the update file is not valid. Please try downloading the file again" (I tried downloading 13.3.1.0 at least 5 times, but none of the downloaded file works). I suspect that something goes wrong with the rom file on Amazon server.
Anybody can help direct me to a non-amazon site or upload your working file to somewhere I can download from?
Thank you very much.
Davey126 said:
Nice find! I had seen that post (long ago) but the significance never set in for Safestrap v3 users with FireOS xx.3.2.4 in the stock slot. Even if not rocking SS it is probably easier (and definitely a lot safer) to install SS vs rolling up just to roll back or messing with build.prop.
The OTA block could still be a problem as the @ggow's procedure still involves Amazon's native update mechanism.
Edit: Disregard OTA comment as modified 3.2.4 goes on first and should restore OTA capability (more importantly the ability to detect and process FireOS bin files in the appropriate location).
Click to expand...
Click to collapse
pquan2009 said:
I upgraded from 13.3.2.4 to 13.3.2.5 and edited build.prop, so now my version shows 13.3.0.9. I downloaded 13.3.1.0 rom from Amazon server. When updating I always received the following error message "Unable to complete update because the update file is not valid. Please try downloading the file again" (I tried downloading 13.3.1.0 at least 5 times, but none of the downloaded file works). I suspect that something goes wrong with the rom file on Amazon server.
Anybody can help direct me to a non-amazon site or upload your working file to somewhere I can download from?
Thank you very much.
Click to expand...
Click to collapse
AFAIK after upgrading to x.3.2.5(or 6) you cant use downgrading via editing build.prop anymore (thanks to Amazon), check this thread for more info.
IF you decide to take further actions PLEASE READ INSTRUCTIONS CAREFULLY, so far you are lucky you didnt brick your kindle.
jeryll said:
AFAIK after upgrading to x.3.2.5(or 6) you cant use downgrading via editing build.prop anymore (thanks to Amazon), check this thread for more info.
IF you decide to take further actions PLEASE READ INSTRUCTIONS CAREFULLY, so far you are lucky you didnt brick your kindle.
Click to expand...
Click to collapse
if i go this route which looks relatively easy do i end up deleting safestrap because i thought twrp doesnt work with it installed? and which safestrap do i install ss 3.72 ... download links are down l?
rbkelley89 said:
if i go this route which looks relatively easy do i end up deleting safestrap because i thought twrp doesnt work with it installed? and which safestrap do i install ss 3.72 ... download links are down l?
Click to expand...
Click to collapse
Assuming you are on 13.3.2.4 (must be that version) you need Safestrap v3.75 b02 for Thor (here). See Safestrap OP for additional information on installing/configuring Safestrap. Or follow part 1-2 of this guide. You do not need to create secondary slots as you will be overwriting FireOS in the Stock ROM Slot. This obviously dangerous. If something goes wrong you could be left with an unbootable device. Make a backup of your current environment from Safestrap recovery before flashing the rollback file. Note rolling back to 3.1.0 is a two step process. Be sure you understand these instructions and have the correct files. Ask questions if unsure.
After you have successfully rolled back to 3.1.0 you should uninstall safestrap before flashing native twrp, bumping your bootloader to 3.2.3 and then unlocking. Alternatively, you can work on bootloader unlocking first while Safestrap is installed which will offer more robust recovery capabilities should something go wrong in subsequent steps.
Davey126 said:
Assuming you are on 13.3.2.4 (must be that version) you need Safestrap v3.75 b02 for Thor (here). See Safestrap OP for additional information on installing/configuring Safestrap. Or follow part 1-2 of this guide. You do not need to create secondary slots as you will be overwriting FireOS in the Stock ROM Slot. This obviously dangerous. If something goes wrong you could be left with an unbootable device. Make a backup of your current environment from Safestrap recovery before flashing the rollback file. Note rolling back to 3.1.0 is a two step process. Be sure you understand these instructions and have the correct files. Ask questions if unsure.
After you have successfully rolled back to 3.1.0 you should uninstall safestrap before flashing native twrp, bumping your bootloader to 3.2.3 and then unlocking. Alternatively, you can work on bootloader unlocking first while Safestrap is installed which will offer more robust recovery capabilities should something go wrong in subsequent steps.
Click to expand...
Click to collapse
thank you so much for the walk through and linking everything i am initiating the process and now have safestrap and backup installed. going through with the rollback then i will start the unlock rocedure. update with any questions or issues i run into. thank you again!
quick thing i ran into before doing factory reset and rebooting into modified stock 3.2.4 it says to have the stock 3.1.0 files where can i find that file it wasn't linked in the rollback instruction or under the modified stock 3.2.4 zip from what i could see?
rbkelley89 said:
thank you so much for the walk through and linking everything i am initiating the process and now have safestrap and backup installed. going through with the rollback then i will start the unlock rocedure. update with any questions or issues i run into. thank you again!
quick thing i ran into before doing factory reset and rebooting into modified stock 3.2.4 it says to have the stock 3.1.0 files where can i find that file it wasn't linked in the rollback instruction or under the modified stock 3.2.4 zip from what i could see?
Click to expand...
Click to collapse
You can grab stock images here. Be absolutely certain you snag the correct one for your device. Verify md5=c49c0363de4d8dfa5c87c1bdb88aa2ba with ES FIle Explorer (long click the file and select 'properties' from the 'more' menu). Note you will loose root and OTA blocking. Be sure to stay off wifi. Use HDX Toolkit (requires usb tether to Windows PC) to root 3.1.0 and reblock OTA if needed.
As the title states, I have an HDX 7 currently sitting with an older firmware and Safestrap 3.70 (TWRP v2.6.3.1).
I haven't touched anything on it since February 2014. My daughter has been using it primarily, but she finally got her own tablet, so I'm reclaiming this one.
Currently, I frequently get a blue screen followed by the tablet rebooting when attempting to watch YouTube videos via the app. Further, I have to uninstall all updates to Google Play for it function at all.
As I recall I also modified some system file to prevent Amazon OTA updates.
I'd like to get this device caught up in terms of current trends. If someone could direct me to my best options and perhaps a guide, I'd really appreciate it. Much of what I'm seeing is for later firmware versions.
Also, if there is a method to retain root and recover the extra storage used by Safestrap, that would be ideal.
Thanks in advance!
PariahNine said:
As the title states, I have an HDX 7 currently sitting with an older firmware and Safestrap 3.70 (TWRP v2.6.3.1).
I haven't touched anything on it since February 2014. My daughter has been using it primarily, but she finally got her own tablet, so I'm reclaiming this one.
Currently, I frequently get a blue screen followed by the tablet rebooting when attempting to watch YouTube videos via the app. Further, I have to uninstall all updates to Google Play for it function at all.
As I recall I also modified some system file to prevent Amazon OTA updates.
I'd like to get this device caught up in terms of current trends. If someone could direct me to my best options and perhaps a guide, I'd really appreciate it. Much of what I'm seeing is for later firmware versions.
Also, if there is a method to retain root and recover the extra storage used by Safestrap, that would be ideal.
Thanks in advance!
Click to expand...
Click to collapse
Given your firmware level:
- verify device is still rooted (use towelroot if needed)
- flash twrp recovery
- update bootloader to v3.2.3.2
- unlock bootloader (try 1-click method)
- flash rom of choice (Nexus, CM 11/12/13), SlimLP)
Search through the forums for relevant threads. Ask questions along the way. You have some work ahead (hours) but a nice reward at the other end.
Is there anything special I need to do to remove Safestrap? I forgot to mention I deleted all of the other rom backups on the device and moved the rooted rom to the default slot to free up space. Pretty sure I have the original rom backed up on my desktop. Do I need to revert before doing any of the above?
PariahNine said:
Is there anything special I need to do to remove Safestrap? I forgot to mention I deleted all of the other rom backups on the device and moved the rooted rom to the default slot to free up space. Pretty sure I have the original rom backed up on my desktop. Do I need to revert before doing any of the above?
Click to expand...
Click to collapse
Thoughts:
- moving roms between slots (specifically stock) via backup/restore is generally a bad idea in Safestrap; consider yourself lucky if you used this technique
- if the rom in the stock slot (assuming FireOS 13.3.1.0) boots properly then you can safely remove Safestrap v3 via the uninstall option in the apk
- do not wipe anything in Safestrap nor execute a 'factory reset' from the native Kindle recovery menu (bad outcomes)
- keep WiFi off / airplane mode engaged unless you are 100% sure the OTA block is working
- snag a copy of Flashify to install twrp and the 3.2.3 bootloader update
- check MD5 checksums with ES File Explorer or another tool before flashing; especially important for bootloader update!
- backup your existing recovery with Flashify before flashing twrp; leave a copy on the device
- enable USB debugging in Kindle settings (optional but offers additional recovery options should something go wrong)
- flash twrp first and make sure it works (reboot to recovery; have a look around but don't change anything)
- reboot FireOS and then use Flashify to update bootloader. Did I mention you should check MD5?
Post when above tasks are complete or if you have questions. Cover bootloader unlock next. Be aware the above steps carry some risk including permanently bricking the device. Make sure you have a clear understand on what is suppose to happen; double/triple check everything before committing changes. Good luck.
So, I understand everything above other than uninstalling Safestrap via the .apk. Is this accomplished via the original apk I installed Safestrap with, or something separate. Also, will I lose root by uninstalling Safestrap?
Ignore the previous post. I've successfully uninstalled Safestrap and reinstalled TWRP. So far, I've attempted to update the bootloader via both TWRP and Flashify, but it's still showing 13.3.1.0 under the device information\system updates. Could this be due to whatever modification I made a couple years ago to prevent OTA updates?
PariahNine said:
So, I understand everything above other than uninstalling Safestrap via the .apk. Is this accomplished via the original apk I installed Safestrap with, or something separate. Also, will I lose root by uninstalling Safestrap?
Click to expand...
Click to collapse
- use the original apk to remove (uninstall) Safestrap v3 recovery; you do not need to uninstall the apk itself
- uninstalling Safestrap will not impact root
---------- Post added at 10:37 AM ---------- Previous post was at 10:30 AM ----------
PariahNine said:
Ignore the previous post. I've successfully uninstalled Safestrap and reinstalled TWRP. So far, I've attempted to update the bootloader via both TWRP and Flashify, but it's still showing 13.3.1.0 under the device information\system updates. Could this be due to whatever modification I made a couple years ago to prevent OTA updates?
Click to expand...
Click to collapse
The FireOS version number will not change following bootloader update. It is a separate 'component' whose version can not be independently queried or verified. Typically the system (what you see, ie: FireOS) and bootloader are updated together and share the same version identifier. In this instance are only flashing the bookloader update as FireOS will soon be replaced by a different ROM. No need to update it and assume the associated risks.
Ahh, gotcha. Problem I'm having now is getting the bootloader unlocked. I downloaded the 1-click file, ran the batch file, and Virtual Box was installed. Once it finished installing it opened up and showed two instances of 1-click, but then nothing happens in either Virtual Box or the cmd window opened by the batch file. If I double click on either instance of 1-click, the last line says it's loading the kernel, but it stays that indefinitely. I attempted closing out Virtual Box multiple times, reran the batch file, all with the same results, sans the installation of course.
PariahNine said:
Ahh, gotcha. Problem I'm having now is getting the bootloader unlocked. I downloaded the 1-click file, ran the batch file, and Virtual Box was installed. Once it finished installing it opened up and showed two instances of 1-click, but then nothing happens in either Virtual Box or the cmd window opened by the batch file. If I double click on either instance of 1-click, the last line says it's loading the kernel, but it stays that indefinitely. I attempted closing out Virtual Box multiple times, reran the batch file, all with the same results, sans the installation of course.
Click to expand...
Click to collapse
Hum. Best handled by @draxie who developed 1-click. Generally pretty responsive to forum posts. If 1-click doesn't do it can always try the manual approach (a LOT more involved but not risky). Let's see what shakes out.
This is what I'm getting from the batch cmd window:
VirtualBox does not appear to be installed
Downloading 'https://www.virtualbox.org/wiki/Downloads' to 'C:\Users\Pariah\Down
loads\1-Click\1-Click\dwnlds'
Download complete.
Downloading 'http://download.virtualbox.org/virtualbox/5.0.12/VirtualBox-5.0.12-
104815-Win.exe' to 'C:\Users\Pariah\Downloads\1-Click\1-Click\VirtualBox-5.0.12-
104815-Win.exe'
Download complete.
Launching the VirtualBox installer momentarily
Please complete the installation with USB support enabled
Installation complete.
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Virtual machine '1-Click' is created and registered.
UUID: 6b44be97-c931-47a5-8eeb-b780f5783b78
Settings file: 'C:\Users\Pariah\VirtualBox VMs\1-Click\1-Click.vbox'
VBoxHeadless: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -23021 (0xf
fffa613) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume2\Windows\Syste
m32\acaptuser64.dll: None of the 1 path(s) have a trust anchor.: \Device\Harddis
kVolume2\Windows\System32\acaptuser64.dll
VBoxHeadless: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\system32\ac
aptuser64.dll': rcNt=0xc0000190
Oracle VM VirtualBox Headless Interface 5.0.12
(C) 2008-2015 Oracle Corporation
All rights reserved.
Click to expand...
Click to collapse
And the 1-click instance in Virtual Box is showing "Booting the kernel."
Here is the method I used to block OTA updates.
Originally Posted by berndt_toast
Yeah, I agree. Staying rooted is difficult, but doable. I am still on the rootable version (13.3.1.0) and have stayed on it even through the OTA updates that have been released. I have stopped them from auto-applying (and from even being seen as updates) by doing the following:
I renamed otacerts.zip to otacerts.zip.old in /etc/security/
I also renamed com.amazon.dcp.apk to com.amazon.dcp.apk.old in /system/app/
Doing those prevent OTA updates from working and if you check for updates from the device, it says none are found (at least it has worked for me).
Click to expand...
Click to collapse
Do I need to undo this before proceeding with the bootloader update and unlocking?
PariahNine said:
Here is the method I used to block OTA updates.
Do I need to undo this before proceeding with the bootloader update and unlocking?
Click to expand...
Click to collapse
No - tasks ahead have no dependence on Amazon's update engine.
10-4. I attempted to find the manual method for unlocking the bootloader with no success. Not sure if I'm looking in the wrong section of the forum, or just overlooking it.
PariahNine said:
10-4. I attempted to find the manual method for unlocking the bootloader with no success. Not sure if I'm looking in the wrong section of the forum, or just overlooking it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/kin...bootloader-unlock-procedure-software-t3030281
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
You're going to need a Linux.
EncryptedCurse said:
http://forum.xda-developers.com/kin...bootloader-unlock-procedure-software-t3030281
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
You're going to need a Linux.
Click to expand...
Click to collapse
Can be accomplished from Windows but a royal PiTA to get the drivers right. Tough having to hold but you probably want to wait on @draxie unless you are very comfortable with device manager and working around unsigned drivers on Win 8/10.
Davey126 said:
Can be accomplished from Windows but a royal PiTA to get the drivers right. Tough having to hold but you probably want to wait on @draxie unless you are very comfortable with device manager and working around unsigned drivers on Win 8/10.
Click to expand...
Click to collapse
I'm actually running Windows 7 64; not sure if that matters. Perhaps why 1-click isn't working?
I'm trying to get Minimal ADB and Fastboot to work, but while my HDX is being detected while booted into the OS or TWRP, it's not in Fastboot mode for whatever reason. I've cleared out the old ADB drivers and reloaded them after plugging the HDX into a USB while in Fastboot mode, and still nothing. It's not showing up under 'adb devices' or 'adb fasboot'.
PariahNine said:
I'm actually running Windows 7 64; not sure if that matters. Perhaps why 1-click isn't working?
I'm trying to get Minimal ADB and Fastboot to work, but while my HDX is being detected while booted into the OS or TWRP, it's not in Fastboot mode for whatever reason. I've cleared out the old ADB drivers and reloaded them after plugging the HDX into a USB while in Fastboot mode, and still nothing. It's not showing up under 'adb devices' or 'adb fasboot'.
Click to expand...
Click to collapse
Yup - that's the driver issue I referenced. Recommend waiting for response from 1-click developer before diving in. Win 7 x64 not an issue.
Davey126 said:
Can be accomplished from Windows but a royal PiTA to get the drivers right. Tough having to hold but you probably want to wait on @draxie unless you are very comfortable with device manager and working around unsigned drivers on Win 8/10.
Click to expand...
Click to collapse
PariahNine said:
I'm actually running Windows 7 64; not sure if that matters. Perhaps why 1-click isn't working?
I'm trying to get Minimal ADB and Fastboot to work, but while my HDX is being detected while booted into the OS or TWRP, it's not in Fastboot mode for whatever reason. I've cleared out the old ADB drivers and reloaded them after plugging the HDX into a USB while in Fastboot mode, and still nothing. It's not showing up under 'adb devices' or 'adb fasboot'.
Click to expand...
Click to collapse
Davey126 said:
Yup - that's the driver issue I referenced. Recommend waiting for response from 1-click developer before diving in. Win 7 x64 not an issue.
Click to expand...
Click to collapse
If you want to give manual unlocking a try:
- use these drivers; you likely need to reinstall when flipping between adb and fastboot
- detail procedure
- suggest browsing this thread for additional info/tips. Lots of noise but some diamonds in the rough too
- careful not to go down a rabbit hole; some solutions are one offs that worked great for the poster due to their familiarity with a particular too, platform or technique
- unlike almost everything else with HDX you can not harm your device with bootloader unlock attempts. It will either work or not with no adverse consequences either way
There are a few excellent posts by @Cl4ncy, @jerryl and others (possibly one of mine) in different threads; unfortunately I wasn't able to surface them in a quick search. Nature of the HDX forums. A gold mine if information that is a bxxtch to access.
Before diving in you may want to flash CM11 or Nexus v4 which can be done with a locked bootloader. Both are rock solid KitKat based roms that will expose the full capabilities of your device and offer continuity to CM13 once unlocked.
Good luck.
First off, I wanna extend a heartfelt thank you to @Davey126 for basically holding my hand through much of the process, and @EncryptedCurse for offering insight as well; folks like you are the reason I've been apart of this community for several years and always come to first when I'm looking for solutions revolving around Android products.
Secondly, I'd like to share a couple of my experiences as a novice that may have others in the future. For whatever reason, I couldn't get 1-click to work on either of my Windows 7 machines with two totally different installations; one being Windows 7 Professional 64-bit, and the other being Windows Home Premium 32-bit. Ultimately I ended up upgrading my system to Windows 10 and was able to unlock the bootloader without any difficulty at all. With the fresh upgrade to Windows 10, I simply uninstalled VirtualBox and reran the 1-click batch file. One thing that should be noted is that there's no reason to click the box to run VirtualBox at the end of the installation process, and may be something that contributed to my confusion and the confusion of others. Secondly, a window for PuttyTel should open up after VirtualBox is finished installing, and the PuttyTel window is where all of the "magic" takes place. I didn't find any of these distinctions in any of the numerous posts I scoured through, though I may have overlooked them.
Either way, thanks again to the three of you... now I just gotta figure out which ROM I'm gonna slap on this bad boy. Been waiting nearly 2 years for this moment.
PariahNine said:
First off, I wanna extend a heartfelt thank you to @Davey126 for basically holding my hand through much of the process, and @EncryptedCurse for offering insight as well; folks like you are the reason I've been apart of this community for several years and always come to first when I'm looking for solutions revolving around Android products.
Secondly, I'd like to share a couple of my experiences as a novice that may have others in the future. For whatever reason, I couldn't get 1-click to work on either of my Windows 7 machines with two totally different installations; one being Windows 7 Professional 64-bit, and the other being Windows Home Premium 32-bit. Ultimately I ended up upgrading my system to Windows 10 and was able to unlock the bootloader without any difficulty at all. With the fresh upgrade to Windows 10, I simply uninstalled VirtualBox and reran the 1-click batch file. One thing that should be noted is that there's no reason to click the box to run VirtualBox at the end of the installation process, and may be something that contributed to my confusion and the confusion of others. Secondly, a window for PuttyTel should open up after VirtualBox is finished installing, and the PuttyTel window is where all of the "magic" takes place. I didn't find any of these distinctions in any of the numerous posts I scoured through, though I may have overlooked them.
Either way, thanks again to the three of you... now I just gotta figure out which ROM I'm gonna slap on this bad boy. Been waiting nearly 2 years for this moment.
Click to expand...
Click to collapse
Happy to hear you were sucesfull. Thanks also for sharing your experiences and insights. Should be helpful to others as they navigate through the process. Every nugget of new information helps!
So i just decided to join the rest of the world and get myself a rectangle. so i researched the 1 to 200 dollar range for weeks until i found my new shiny metal friend with great specs and a price that wouldn't keep me up at night. the le max 2 x829. but i love tech and was really looking forward to pushing this phone and learn about all it could do! i was really excited.
Until i started to learn about the many confusing programs needed to install custom roms or make a recovery file. things like that All of which need like 6 different programs all of which seem to need some other program in order to functional. I can't seem to even find a starting point! I HAVE NEVER FELT THIS STUPID IN MY ENTIRE LIFE. Someone please help. what programs do i need for a new os ? How does adb fit into the chain of programs needed to mod android? is twrp the first program needed? how does it all sort...fit to gather? Thanks for any help!
Man, honestly this forum is made to help people, but also people should use the search button. This question has been answered a million times already.
Long story short:
- Connect the phone to the PC and install the drivers (including ADB)
- Unlock bootloader (usually it's already unlocked)
- Download TWRP on your PC
- Install TWRP following the developer's steps
- Download your custom ROM
- Put the ROM on the internal memory
- Boot into TWRP
- Install the new ROM according to the instructions given by the developer and you're done...
valy_cta said:
Man, honestly this forum is made to help people, but also people should use the search button. This question has been answered a million times already.
Long story short:
- Connect the phone to the PC and install the drivers (including ADB)
- Unlock bootloader (usually it's already unlocked)
- Download TWRP on your PC
- Install TWRP following the developer's steps
- Download your custom ROM
- Put the ROM on the internal memory
- Boot into TWRP
- Install the new ROM according to the instructions given by the developer and you're done...
Click to expand...
Click to collapse
including adb? what other drivers do i need? xposed? supersu? ...i have done my research by the way...its just not making alot of sense..thats all. i know all you old pros have probably been at it for years but i never even held a smartphone until 6 days ago ha ha
valy_cta said:
Man, honestly this forum is made to help people, but also people should use the search button. This question has been answered a million times already.
Long story short:
- Connect the phone to the PC and install the drivers (including ADB)
- Unlock bootloader (usually it's already unlocked)
- Download TWRP on your PC
- Install TWRP following the developer's steps
- Download your custom ROM
- Put the ROM on the internal memory
- Boot into TWRP
- Install the new ROM according to the instructions given by the developer and you're done...
Click to expand...
Click to collapse
Also how do you download twrp on you're pc ? it won't let me i have it on my phone but it just keeps leading me to a website to download again.
Serialjwalker said:
Also how do you download twrp on you're pc ? it won't let me i have it on my phone but it just keeps leading me to a website to download again.
Click to expand...
Click to collapse
Do you have it installed on the phone or just downloaded? If it's installed, jump over that step. If it's just downloaded, connect the phone to the pc by cable, transfer the files :cyclops:
I understand your concern. It's because there are a few ways of doing it, and so novices might be confused when comparing two different tutorials.
This one is very complete: https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
1. Connect your phone, it is supposed to install drivers automatically.
1.1 If not, you'll need to google it, but I believe this toolkit will help you. In fact, this tool is capable of doing all the process for you by simply clicking on some buttons.2. Install ADB Drivers. There are a few options and it is basically
2.1 @greenManGaming recommends 15 seconds ADB installer.
2.2 (Alternative) Minimal ADB and Fastboot. I've used this one.
2.3 (Alternative) ADB and Fastboot (newer) or Universal ADB and Fastboot (older) from the same dev.
OBS: I'm not sure if the toolkit requires or not one of these options to work properly or if it already does this task.3. Download TWRP (on your computer).
3.1 Follow the instructions from the official page. In short, put the img into the ADB folder.4. Follow the commands in the the tutorial mentioned.
4.1 In short, unlock the bootloader, boot twrp, complete backup, reboot into the system, copy the backup to your PC/Cloud service, get back to fastboot mode, flash twrp, then flash your ROM.
OBS: Suggestion for only booting TWRP at the first time is perfectly optional, you can flash it since the beginning but in this case you wouldn't be able to backup the original recovery and everything as the phone came, in case you need go back to request an RMA.
razmth said:
I understand your concern. It's because there are a few ways of doing it, and so novices might be confused when comparing two different tutorials.
This one is very complete: https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
1. Connect your phone, it is supposed to install drivers automatically.
1.1 If not, you'll need to google it, but I believe this toolkit will help you. In fact, this tool is capable of doing all the process for you by simply clicking on some buttons.2. Install ADB Drivers. There are a few options and it is basically
2.1 @greenManGaming recommends 15 seconds ADB installer.
2.2 (Alternative) Minimal ADB and Fastboot. I've used this one.
2.3 (Alternative) ADB and Fastboot (newer) or Universal ADB and Fastboot (older) from the same dev.
OBS: I'm not sure if the toolkit requires or not one of these options to work properly or if it already does this task.3. Download TWRP (on your computer).
3.1 Follow the instructions from the official page. In short, put the img into the ADB folder.4. Follow the commands in the the tutorial mentioned.
4.1 In short, unlock the bootloader, boot twrp, complete backup, reboot into the system, copy the backup to your PC/Cloud service, get back to fastboot mode, flash twrp, then flash your ROM.
OBS: Suggestion for only booting TWRP at the first time is perfectly optional, you can flash it since the beginning but in this case you wouldn't be able to backup the original recovery and everything as the phone came, in case you need go back to request an RMA.
Click to expand...
Click to collapse
more questions....twrp will only load onto my phone and not my pc? also there are no adb driver folders just an exe. what do i do about that?
someone tell me how to delete this thread...i am just going to sell my smartphone i can't look at it anymore. every thing i try to do with it it resists every single inch of the way. nothing works according to instructions. i thought this would be fun but its hell... i give up! ...it wins going to trade this thing for the first 30 dollar burner phone i can find
Huge drama for nothing. Sell the thing, it's obviously not for you. If you can't follow some simple instructions, then it's better to sell it to some guy who likes to try at least.
valy_cta said:
Huge drama for nothing. Sell the thing, it's obviously not for you. If you can't follow some simple instructions, then it's better to sell it to some guy who likes to try at least.
Click to expand...
Click to collapse
maybe they are laid out to be simple but nothing is working as instructed. i have been at it for a week . so far installing firefox is the best i can seem to do lol simple? theres nothing simple about the gangbang of programs you need to do stuff on these phones. none of which can actually be compelled to function under any circumstances at least for me.
Serialjwalker said:
maybe they are laid out to be simple but nothing is working as instructed. i have been at it for a week . so far installing firefox is the best i can seem to do lol simple? theres nothing simple about the gangbang of programs you need to do stuff on these phones. none of which can actually be compelled to function under any circumstances at least for me.
Click to expand...
Click to collapse
If you are not familiar with giving commands with command prompt, installing drivers and needed software (android studio or minimal adb install) then you are in for a challenge, if you are not willing to learn its better to sell the phone or use it with de preinstalled android.
i find myself quite skilled( have flashed several brands of phoned in the last 5 years) and it took me a couple of days to figure out what to do and how to install twrp and my first rom, there are no one click shortcuts for this phone
Why need to install rom? It already work.
Serialjwalker said:
more questions....twrp will only load onto my phone and not my pc? also there are no adb driver folders just an exe. what do i do about that?
Click to expand...
Click to collapse
Did you try watching different videos to have a big picture of the process? It would be the first step. Even if you don't understand English, simply watch it. You'll see what would happen after each action.
Then check the written tutorial. Not a big issue at all. Really. Even for newbies, I've been one when I had a Galaxy 5, my first android that doesn't even needed to flash a custom ROM.
Whether you think you can, whether you think you can't, you're right.
The command to load the TWRP will be done on your PC, however, only your phone will load it. In short, you'll be commanding your phone through your PC.
When you install Minimal ADB and Fastboot, it will install its files in a default folder. Inside its default folder is where you should place the TWRP image.
Sent from my Le X820 using Tapatalk
So I need help badly! And of course, I've even asked if I could pay someone. I'm new to phones/tablets/android. Very comfortable with all things computer though. I bought the Amazon Kindle Fire HDX 8.9 for the second time off Ebay that Amazon did not want to register without a receipt from my seller's purchase. I wanted this tablet for the specs and also we do a lot with Amazon. I've been customizing my computer for years and I don't care the specs of the $50 fires that are coming out in 2017. However both my sellers were honest and gave me everything but their social security cards and said they had it registered in their name and called Amazon as well. It seems almost like Amazon is finding a way not to register these secondhand Fires that are discontinued without a receipt from the original owner for "security". So this is when I found out about rooting while googling my problem. I have the 4.2 OS. And I've read a lot of warnings about this particular model. Most of the advice is over two years old so I want to know what can currently be done to turn this tablet into an Android. Is it possible?
And can I get simple detailed instructions so that I don't "soft brick" or "hard brick" my device.
I got full refund from my first seller. The second one told me he would give me partial credit if I kept it and tried to root it. If it bricks he says he will refund me completely. He is under the impression that rooting isn't difficult.
Can someone please help me?
Wendy
justyermama said:
So I need help badly! And of course, I've even asked if I could pay someone. I'm new to phones/tablets/android. Very comfortable with all things computer though. I bought the Amazon Kindle Fire HDX 8.9 for the second time off Ebay that Amazon did not want to register without a receipt from my seller's purchase. I wanted this tablet for the specs and also we do a lot with Amazon. I've been customizing my computer for years and I don't care the specs of the $50 fires that are coming out in 2017. However both my sellers were honest and gave me everything but their social security cards and said they had it registered in their name and called Amazon as well. It seems almost like Amazon is finding a way not to register these secondhand Fires that are discontinued without a receipt from the original owner for "security". So this is when I found out about rooting while googling my problem. I have the 4.2 OS. And I've read a lot of warnings about this particular model. Most of the advice is over two years old so I want to know what can currently be done to turn this tablet into an Android. Is it possible?
And can I get simple detailed instructions so that I don't "soft brick" or "hard brick" my device.
I got full refund from my first seller. The second one told me he would give me partial credit if I kept it and tried to root it. If it bricks he says he will refund me completely. He is under the impression that rooting isn't difficult.
Can someone please help me?
Wendy
Click to expand...
Click to collapse
Device can be rooted w/o registering and install the custom ROM of your choice. But it will take some work, patience and tech experience. I can point you to the technical documents early next week if interested. Travelling with limited/no network access this weekend.
Davey126 said:
Device can be rooted w/o registering and install the custom ROM of your choice. But it will take some work, patience and tech experience. I can point you to the technical documents early next week if interested. Travelling with limited/no network access this weekend.
Click to expand...
Click to collapse
:angel: So I really appreciate the quick response, and you have renewed my hope for this situation. That would be absolutely great. I once had Linux OS on a used computer I bought and quickly reformatted so I could install Windows. I found it to be not very user-friendly. However, while I'm waiting for next week to come, should I study the Linux OS or is there anything I should read or concentrate on learning, off the top of your head, to make my journey a little bit easier? Thanks again.
jymama
WAITING Patiently for Direction to root/flash Blacklisted Kindle Fire 8.9
justyermama said:
:angel: So I really appreciate the quick response, and you have renewed my hope for this situation. That would be absolutely great. I once had Linux OS on a used computer I bought and quickly reformatted so I could install Windows. I found it to be not very user-friendly. However, while I'm waiting for next week to come, should I study the Linux OS or is there anything I should read or concentrate on learning, off the top of your head, to make my journey a little bit easier? Thanks again.
jymama
Click to expand...
Click to collapse
Still Waiting to find out how to turn my blacklisted fire hdx 8.9 4th gen into a usable tablet. When I found out it was possible, I decided I would give it a shot and accepted $50 of the $130 I paid and kept it. Anyone who can help someone who is good with a computer, but I have no experience/knowledge with androids, I'm willing to learn if someone could point out the way. This particular model of tablet is supposed to not be easy to do, and please take into consideration my inexperience with this, I am willing to put time and effort if I could get the information/specific directions. I'm willing to compensate someone for their time. Please help.
Thank you, Wendy
jyermama
justyermama said:
Still Waiting to find out how to turn my blacklisted fire hdx 8.9 4th gen into a usable tablet. When I found out it was possible, I decided I would give it a shot and accepted $50 of the $130 I paid and kept it. Anyone who can help someone who is good with a computer, but I have no experience/knowledge with androids, I'm willing to learn if someone could point out the way. This particular model of tablet is supposed to not be easy to do, and please take into consideration my inexperience with this, I am willing to put time and effort if I could get the information/specific directions. I'm willing to compensate someone for their time. Please help.
Thank you, Wendy
jyermama
Click to expand...
Click to collapse
Hi - as noted in my original response time, patience and some technical expertise will be needed to root the device via the 'bulk mode' approach. Unfortunately, time is not an abundant resource at present so you're pretty much on your own outside responding to specific questions. Below is the initial technical document which will undoubtedly seem overwhelming on initial inspection. You will likely want to read through the next few posts to adsorb guidance from the author (@draxie). Better yet, scan/search the thread for the word 'bulk' for related posts. Also see this post for links to a couple 'tools' that you will need to install on a Windows host before getting started. Good luck; ask questions as they arise.
bulk mode doc: https://forum.xda-developers.com/showpost.php?p=71430759&postcount=736
main bootloader unlock thread: https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
auxiliary thread (lots of good info): https://forum.xda-developers.com/kindle-fire-hdx/general/thor-4-5-5-2-easy-to-root-unlock-t3571240
Davey126 said:
Hi - as noted in my original response time, patience and some technical expertise will be needed to root the device via the 'bulk mode' approach. Unfortunately, time is not an abundant resource at present so you're pretty much on your own outside responding to specific questions. Below is the initial technical document which will undoubtedly seem overwhelming on initial inspection. You will likely want to read through the next few posts to adsorb guidance from the author (@draxie). Better yet, scan/search the thread for the word 'bulk' for related posts. Also see this post for links to a couple 'tools' that you will need to install on a Windows host before getting started. Good luck; ask questions as they arise.
bulk mode doc: https://forum.xda-developers.com/showpost.php?p=71430759&postcount=736
main bootloader unlock thread: https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
auxiliary thread (lots of good info): https://forum.xda-developers.com/kindle-fire-hdx/general/thor-4-5-5-2-easy-to-root-unlock-t3571240
Click to expand...
Click to collapse
I have done all the step in the link of bulk mode you post. It works very well with many KFHDX7 I have done but one of mine can't flash any ROMs although it can boot to recovery and bootloader. Could you help me?
P/s: It stuck at the white kindle fire logo after I flash any ROMs but I can boot to TWRP and fastboot.
Chatchum said:
I have done all the step in the link of bulk mode you post. It works very well with many KFHDX7 I have done but one of mine can't flash any ROMs although it can boot to recovery and bootloader. Could you help me?
P/s: It stuck at the white kindle fire logo after I flash any ROMs but I can boot to TWRP and fastboot.
Click to expand...
Click to collapse
Be sure to wipe storage before attempting to flash a new/different ROM:
- make sure the latest TWRP build is installed (link)
- boot into TWRP
- tap Wipe followed by Advanced Wipe
- tick all partitions EXCEPT 'Internal Storage'
- execute wipe (may take a few seconds)
- return to main menu and flash ROM of your choosing
- only ROMs customized for this device can be flashed
- some require a GAaps package and/or SuperSU; read ROM OP for details
If the above fails perform a comprehensive wipe that includes all partitions. Then reboot device into TWRP, re-download ROM and supporting packages and attempt to flash again.
Davey126 said:
Be sure to wipe storage before attempting to flash a new/different ROM:
- make sure the latest TWRP build is installed (link)
- boot into TWRP
- tap Wipe followed by Advanced Wipe
- tick all partitions EXCEPT 'Internal Storage'
- execute wipe (may take a few seconds)
- return to main menu and flash ROM of your choosing
- only ROMs customized for this device can be flashed
- some require a GAaps package and/or SuperSU; read ROM OP for details
If the above fails perform a comprehensive wipe that includes all partitions. Then reboot device into TWRP, re-download ROM and supporting packages and attempt to flash again.
Click to expand...
Click to collapse
I forgot unlock bootloader before flash ROMs on that HDX7. Do you think it made that problem?
These ROMs are work very well, because I flash 3 HDX7s by the same way with this HDX7 but there is no problem.
Please help me!
Chatchum said:
I forgot unlock bootloader before flash ROMs on that HDX7. Do you think it made that problem?
These ROMs are work very well, because I flash 3 HDX7s by the same way with this HDX7 but there is no problem.
Click to expand...
Click to collapse
Wipe and flash this ROM. Work? If so proceed with bootloader unlock using Fire Nexus as a temporary base.
Chatchum said:
Please help me!
Click to expand...
Click to collapse
This ^^ is both annoying and unnecessary.
Davey126 said:
Wipe and flash this ROM. Work? If so proceed with bootloader unlock using Fire Nexus as a temporary base.
This ^^ is both annoying and unnecessary.
Click to expand...
Click to collapse
It works very well.
Chatchum said:
It works very well.
Click to expand...
Click to collapse
Great! You should now be able to generate an unlock code specific to your device (step #1) and unlock the bootloader (step #3), possibly with the help of these drivers to enable fastboot communications from a Windows host.
I flashed wrong TWRP file, and now my HDX7 couldn't boot to recovery or bootloader by press power + up (down) button and it stuck in white logo.
Chatchum said:
I flashed wrong TWRP file, and now my HDX7 couldn't boot to recovery or bootloader by press power + up (down) button and it stuck in white logo.
Click to expand...
Click to collapse
You're in a world of hurt if device can not be placed into fastboot mode via <power>+<vol-down>. Your may need to attempt a recovery via 'bulk mode' which is neither easy nor assured.
https://forum.xda-developers.com/ki...isted-kindle-fire-hdx-8-t3636657/post73104157
Davey126 said:
You're in a world of hurt if device can not be placed into fastboot mode via <power>+<vol-down>. Your may need to attempt a recovery via 'bulk mode' which is neither easy nor assured.
https://forum.xda-developers.com/ki...isted-kindle-fire-hdx-8-t3636657/post73104157
Click to expand...
Click to collapse
I have tried to do via bulk mode but I can't boot to fastboot to do all of it
Chatchum said:
I have tried to do via bulk mode but I can't boot to fastboot to do all of it
Click to expand...
Click to collapse
Sorry this happened. Bulk mode is the last option short of replacing boards.
hello i am using fire hdx 3rd gen, I am on fire os 4.5.5.3, I am trying to install TWRP, i can do adb devices and find my device, when I use 'fastboot flash recovery twrp.img, the kindle restarts and goes to a screen showing fastboot ready, but I still see 'waiting for device' on my pc. Please help.
bluejaysrs said:
hello i am using fire hdx 3rd gen, I am on fire os 4.5.5.3, I am trying to install TWRP, i can do adb devices and find my device, when I use 'fastboot flash recovery twrp.img, the kindle restarts and goes to a screen showing fastboot ready, but I still see 'waiting for device' on my pc. Please help.
Click to expand...
Click to collapse
There are so many things unstated/wrong it's hard to know where to start.
- rooted?
- vulnerable aboot/bootloader installed?
- using twrp image w/forged signature?
- experience dealing with windows driver issues?
Transforming this Amazon device into a generic Android gizmo is technically challenging and not for the faint of heart. You'll need to so your homework (likely hours of reading) as no one here is going to handhold as you stumble through the basics.
Start here; follow suggested links:
https://forum.xda-developers.com/kindle-fire-hdx/help/bootloader-unlock-twrp-guides-t3802443
I recommend these drivers:
https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,4222
Davey126 said:
There are so many things unstated/wrong it's hard to know where to start.
- rooted?
- vulnerable aboot/bootloader installed?
- using twrp image w/forged signature?
- experience dealing with windows driver issues?
Transforming this Amazon device into a generic Android gizmo is technically challenging and not for the faint of heart. You'll need to so your homework (likely hours of reading) as no one here is going to handhold as you stumble through the basics.
Start here; follow suggested links:
https://forum.xda-developers.com/kindle-fire-hdx/help/bootloader-unlock-twrp-guides-t3802443
I recommend these drivers:
https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,4222
Click to expand...
Click to collapse
Thanks for guiding me through the required documentation. I have successfully followed the below link and did bootloader unlock and did get twrp and flashed a custom ROM, could you please guide me to any Oreo based custom ROM for my device? Thanks.
https://forum.xda-developers.com/showpost.php?p=75284993&postcount=1006
bluejaysrs said:
Thanks for guiding me through the required documentation. I have successfully followed the below link and did bootloader unlock and did get twrp and flashed a custom ROM, could you please guide me to any Oreo based custom ROM for my device? Thanks.
https://forum.xda-developers.com/showpost.php?p=75284993&postcount=1006
Click to expand...
Click to collapse
Nougat only at present. My preference is AEX but many like Lineage. Can't go wrong with either choice.