Related
trying to flash clockwork recovery using the What you need to know about the Dell Streak PDF. Got into fastboot on the streak, got the C:\streak part fine but when I type fastboot it says "fastboot is not recognized as an internal or external device" I changed the fastboot-windows to fastboot but it gives me that error code mentioned above. Any help would be greatly appreciated.
OK. Cool, I just got clockwork installed using these directions http://forum.xda-developers.com/showthread.php?t=754563 but when I go to make a backup or flash I just get a blank screen with the backlight on and the capacitive buttons will flash every so often. Any ideas? Im new at this. On my old CDMA Hero rommanager took care of all this.
I recommend that you use StreakMod recovery rather than CWM. It is customized for the Streak. There are some useful links in my signature.
You may need to press the power button after selecting the second option on the first screen to get to the rest of the CWM options.
Presssing the power button returns it to the clockwork menu. I have the streakmod recovery unzipped but haven't quite figured out how to flash it. This is my first time doing anything with fastbootn honestly I only got this streak to try to learn more of the fun side of android. I have a nexus s and a xoom wifi but since they're both running current versions I just wanted something to tinker with.
dodsonhaycattle said:
Presssing the power button returns it to the clockwork menu. I have the streakmod recovery unzipped but haven't quite figured out how to flash it. This is my first time doing anything with fastbootn honestly I only got this streak to try to learn more of the fun side of android. I have a nexus s and a xoom wifi but since they're both running current versions I just wanted something to tinker with.
Click to expand...
Click to collapse
You will need to flash streakmodrecovery over clockwork.
Some steps i posted elsewhere http://forum.xda-developers.com/showpost.php?p=15434274&postcount=36
OK guys, you're to kind. Ill follow the directions above tonight and let you know how I done. I appreciate the help more than you guys could ever realize. I can only hope to almost be as good at this as you are so I can share my knowledge one day!
dodsonhaycattle said:
OK guys, you're to kind. Ill follow the directions above tonight and let you know how I done. I appreciate the help more than you guys could ever realize. I can only hope to almost be as good at this as you are so I can share my knowledge one day!
Click to expand...
Click to collapse
Basically, you need to fastboot your phone then use the recovery flasher to flash the streakmodrecovery, let it reboot and you will have the streakmodrecovery installed. As usual, to access the recovery, just power up yr phone and hold the vol+ and vol- until the recovery screen appears. Cheers
Anyone know if there is a way to reboot directly to Download Mode from inside Stock Recovery? The only option I see "reboot system".
Anyone?
Thanks
http://goo.gl/pVRC0P
i605 running LiquidSmooth
Rootabaga said:
Anyone know if there is a way to reboot directly to Download Mode from inside Stock Recovery? The only option I see "reboot system".
Anyone?
Thanks
Click to expand...
Click to collapse
While I understand that everybody has to start somewhere, you really need to do some research first. If the first question is how to get into download mode from inside a stock recovery then you will soon end up with a paperweight. Im not answering your question because I'm an a$$, I'm not answering to save you the headache of having to deal with getting a replacement device.
QBall45 said:
http://goo.gl/pVRC0P
Click to expand...
Click to collapse
If you don't know the answer to my question, please, don't bother to respond. I searched extensively before posting my question, as I always do. If you actually read ANY of the responses in the google search that you so kindly posted, you would see that NONE of them answer my question. This is exactly why I posted the question here, thinking someone might be willing to help. I was obviously quite mistaken.
These links should be of interest to you:
http://bit.ly/1pVOBfQ
http://bit.ly/1rkxepU
TheBr0ken said:
While I understand that everybody has to start somewhere, you really need to do some research first. If the first question is how to get into download mode from inside a stock recovery then you will soon end up with a paperweight. Im not answering your question because I'm an a$$, I'm not answering to save you the headache of having to deal with getting a replacement device.
Click to expand...
Click to collapse
You guys really are something.
First of all, I have researched extensively. To suggest that I haven't is a gross error on your part, not to mention that your entire response is obscenely condescending and presumptuous. As a rule I only post here after I have made a significant effort to find the answer I am looking for on my own. I know exactly what I want to do and why. Furthermore, I am 100% responsible for my own actions. I really don't need you to save me from myself.
The ability to boot directly into Download Mode from recovery without booting the OS has many benefits, which is exactly why many custom recoveries have this feature built in. I would simply like to know if there is a way to do this with the stock recovery. If there is, great. Let me know. If there isn't, fine. If you don't know, either say so or don't answer at all. If you would like to alert me to the potential risks, thank you, that would be very nice of you. Nevertheless, responses like the one you gave are absolutely uncalled for.
I would direct you to the response I gave to Q-Ball. Neither of your responses add any value to this forum.
Our response was justified.
The answer you need is available in the stickied threads.
But... I will save you time. The simple answer is I don't think you can boot to download mode while in stock recovery. Just pull the battery, reinsert the battery, hold down volume + home + power. Once you see the Samsung logo release the power button while maintaining hold on vol down + home.
The bottom line is you must have really jacked up your device or you're attempting to recover from a soft brick. There's not much reason for using download mode with stock recovery... Unless you're in the process of rooting in which case thee thread you should be following will have detailed instructions laid out for you to follow.
i605 running LiquidSmooth
QBall45 said:
Our response was justified.
The answer you need is available in the stickied threads.
But... I will save you time. The simple answer is I don't think you can boot to download mode while in stock recovery. Just pull the battery, reinsert the battery, hold down volume + home + power. Once you see the Samsung logo release the power button while maintaining hold on vol down + home.
The bottom line is you must have really jacked up your device or you're attempting to recover from a soft brick. There's not much reason for using download mode with stock recovery... Unless you're in the process of rooting in which case thee thread you should be following will have detailed instructions laid out for you to follow.
i605 running LiquidSmooth
Click to expand...
Click to collapse
I'm just going to make a guess here but the op more than likely has the corrupt data partition problem which there is a sticky for in the general section. The instructions just say to odin a recovery after you use stock recovery to wipe with which is probably why he is asking if there is a way to reboot directly to download mode from stock recovery. Now like I said I am just guessing here.
Sent from my SCH-I605 using XDA Premium 4 mobile app
BluGuy said:
I'm just going to make a guess here but the op more than likely has the corrupt data partition problem which there is a sticky for in the general section. The instructions just say to odin a recovery after you use stock recovery to wipe with which is probably why he is asking if there is a way to reboot directly to download mode from stock recovery. Now like I said I am just guessing here.
Click to expand...
Click to collapse
Bingo! Give that man a cigar! :good: Are you psychic?:laugh:
That is exactly what I am dealing with. I was hoping there was a direct way to reboot to Download Mode from Stock Recovery to avoid booting the OS and without having to pull the battery.
Apparently there isn't a way. Thanks for the info
Rootabaga said:
Bingo! Give that man a cigar! :good: Are you psychic?:laugh:
That is exactly what I am dealing with. I was hoping there was a direct way to reboot to Download Mode from Stock Recovery to avoid booting the OS and without having to pull the battery.
Apparently there isn't a way. Thanks for the info
Click to expand...
Click to collapse
Sad that we had to get a psychic here in order to find out the issues you were having. If we had more info from the beginning, nobody would have been "assuming" anything
TheBr0ken said:
Sad that we had to get a psychic here in order to find out the issues you were having. If we had more info from the beginning, nobody would have been "assuming" anything
Click to expand...
Click to collapse
Stop. Just stop. Really.
Hey. I've downgraded from Nougat to Marshmallow using this guide: http://forum.xda-developers.com/lg-g5/how-to/downgrade-7-0-to-6-0-1-lg-g5-h850-t3511930. I've tried to install TWRP but the button combination doesn't work. I've followed the instructions to the letter, I've pulled out the battery, kept volume down pressed all the time etc., etc. I've tried different timings. Before the downgrade I was able to get into TWRP easily. My volume down button works, I've checked that. I'm able to get into the display IMEI mode (both VOL UP and VOL DOWN pressed down) and into the download mode. I can get into stock recovery with adb. I've upgraded back to Nougat, then reflashed boot and stock (Nougat version ofc) and then tried everything again but to no avail. I would appreciate any help.
Additional note: I've tried 3.0.2-0 and 3.0.2-1 on Marshmallow and 3.0.2-1 on Nougat.
EDIT: I have 2 ideas. First, manually reflash all the paritions from the unpacked KDZ. Second, use the Dirty Cow. First one will take time, but should be safe. Second one will probably take even longer, since I'm not really good with Linux and this method wasn't designed for H850, though it should work, unless LG patched it in Nougat.
EDIT 2: Most partitions are unflashable (FAILED (remote: cannot flash this partition in unlocked state)).
!WARNING! Useless discussion below, no need to read the current replies.
When you see the LG logo you have to let go of the power button and immediately press it again, then it should work. Takes a bit of practice sometimes
Nimueh said:
When you see the LG logo you have to let go of the power button and immediately press it again, then it should work. Takes a bit of practice sometimes
Click to expand...
Click to collapse
Come on, mate. I've made it very clear that I know how to do it, don't give me the obvious tips.
TH4N1X said:
Come on, mate. I've made it very clear that I know how to do it, don't give me the obvious tips.
Click to expand...
Click to collapse
Well excuuuuuuuuse me for trying to help ...
Nimueh said:
Well excuuuuuuuuse me for trying to help ...
Click to expand...
Click to collapse
Well, excuse me for expecting useful responses. I think I've made it very clear that the problem isn't that I can't press the buttons properly and yet you advised me to try it again.
TH4N1X said:
Well, excuse me for expecting useful responses. I think I've made it very clear that the problem isn't that I can't press the buttons properly and yet you advised me to try it again.
Click to expand...
Click to collapse
You wouldn't be the first one that didn't do it properly ... and probably not the last one either but ok.
Good luck *waves and ignores thread*
She was just trying to help, even if the answers weren't what you expected you don't have the right to be a Dickhead.
Good luck getting anyone else to help you with that attitude...
yilun said:
She was just trying to help, even if the answers weren't what you expected you don't have the right to be a Dickhead.
Good luck getting anyone else to help you with that attitude...
Click to expand...
Click to collapse
I don't really think that you can talk about about proper attitude and call people dickheads at the same time. It's one thing when you try to help but your solution doesn't work and it's another when you post a solution that's clearly not going to work from the start.
Hi there,
I have rooted kindle fire hdx 7.
I can't install twrp, so i decide to do it from flashify.
After Reboot, bootloop issue came
Help me till i decide to kill myself for stutipdness.
arshileus said:
Hi there,
I have rooted kindle fire hdx 7.
I can't install twrp, so i decide to do it from flashify.
After Reboot, bootloop issue came
Help me till i decide to kill myself for stutipdness.
Click to expand...
Click to collapse
Attempting to flash a custom recovery (TWRP) on a HDX with with 'standard' bootloader destroys the stock recovery which is required for FireOS to boot. Restoration is not easy and essentially involves rebuilding the device. There are posts throughout this forum that outline what needs to happen but no dedicated threads or step-by-step process. You'll either need to do a ton of reading or simply accept the device is borked and move on.
Davey126 said:
Attempting to flash a custom recovery (TWRP) on a HDX with with 'standard' bootloader destroys the stock recovery which is required for FireOS to boot. Restoration is not easy and essentially involves rebuilding the device. There are posts throughout this forum that outline what needs to happen but no dedicated threads or step-by-step process. You'll either need to do a ton of reading or simply accept the device is borked and move on.
Click to expand...
Click to collapse
or simply can kill myself, cause i spent a lot of money :/ oh, god... jesus...
arshileus said:
or simply can kill myself, cause i spent a lot of money :/ oh, god... jesus...
Click to expand...
Click to collapse
Sorry dude, flashify only works to upgrade/downgrade TWRP on this device, not to make a fresh intall
You forgot unlock bootloader first,neccesary to install TWRP, thats why your device its bricked, if you can get ADB connectivity on the PC using USB Cable, you could have some chance to revive the device.
The easy way : Find a used Kindle with dead display/battery or a new motherboard , to replace the bricked one.
Before do something in your device, always read about the necessary tools/ instructions/ procedures, and make all your questions here.
Tossing out a few clarifications for future readers:
Yousucks2 said:
Sorry dude, flashify only works to upgrade/downgrade TWRP on this device, not to make a fresh intall
Click to expand...
Click to collapse
Flashify can be used for a fresh install if bootloader is unlocked (always) or in special cases (eg: signed image).
Yousucks2 said:
You forgot unlock bootloader first,neccesary to install TWRP, thats why your device its bricked, if you can get ADB connectivity on the PC using USB Cable, you could have some chance to revive the device.
Click to expand...
Click to collapse
Yep - a real boneheaded move. Recovery is also possible by dumping device into 'bulk mode' which is an advanced recovery technique that requires both patience and some technical experience (not to mention attentive reading skills).
Yousucks2 said:
The easy way : Find a used Kindle with dead display/battery or a new motherboard , to replace the bricked one.
Before do something in your device, always read about the necessary tools/ instructions/ procedures, and make all your questions here.
Click to expand...
Click to collapse
HDX disassembly is not for the faint of heart due to copious use of glue; cracked screens are common trying to pry open the clam shell. Probably best to go the 'bulk mode' route first which itself is not easy. My recommendation is to sell the device for parts and pickup up another on an auction site.
Davey126 said:
Tossing out a few clarifications for future readers:
Flashify can be used for a fresh install if bootloader is unlocked (always) or in special cases (eg: signed image).
Yep - a real boneheaded move. Recovery is also possible by dumping device into 'bulk mode' which is an advanced recovery technique that requires both patience and some technical experience (not to mention attentive reading skills).
HDX disassembly is not for the faint of heart due to copious use of glue; cracked screens are common trying to pry open the clam shell. Probably best to go the 'bulk mode' route first which itself is not easy. My recommendation is to sell the device for parts and pickup up another on an auction site.
Click to expand...
Click to collapse
Can you show me any guidelines to understand how hard is it....
arshileus said:
Can you show me any guidelines to understand how hard is it....
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=71430759&postcount=736
Not sure...
Davey126 said:
https://forum.xda-developers.com/showpost.php?p=71430759&postcount=736
Click to expand...
Click to collapse
This will only work if adb or fastboot can still connect,
but in that case I'd suggest to try 1-Click pre-release to
click through a web-UI. No reading required... (-;
BTW, is recovery _really_ checked/needed for FireOS to boot?
I suspect that flashify (or the OP) did more than just overwrite recovery,
which can be _really_bad_ if the bootloader is still locked, since the key
combo to enter fastboot doesn't work...
draxie said:
BTW, is recovery _really_ checked/needed for FireOS to boot? I suspect that flashify (or the OP) did more than just overwrite recovery, which can be _really_bad_ if the bootloader is still locked, since the key combo to enter fastboot doesn't work...
Click to expand...
Click to collapse
In my experience 'yes' to boot although there are obviously exceptions including those running FireOS with a custom recovery on a locked (but still vulnerable) device. Whether the stock recovery contents are actually used or something else happens is unknown...at least to me. Symptom wise a borked recovery is almost always leads to boot issues.
draxie said:
BTW, is recovery _really_ checked/needed for FireOS to boot?
I suspect that flashify (or the OP) did more than just overwrite recovery,
which can be _really_bad_ if the bootloader is still locked, since the key
combo to enter fastboot doesn't work...
Click to expand...
Click to collapse
Seems the issue I'm experiencing
I have got another fire hdx 7.
How i can unlock bootloader? Where is guideline?
arshileus said:
I have got another fire hdx 7.
How i can unlock bootloader? Where is guideline?
Click to expand...
Click to collapse
Same thread as previously linked (here). It is NOT a step-by-step idiot proof guide. You will need to do some advance reading. Suggest digesting the OP then reviewing the last 2-3 months of posts to get a 'feel' for what is required and the questions you may have.
I have done this before on windows 10 . But i am on windows 7 now.
After i clicking on unlock.bat, device goes to fastboot mode. At this time i cant find "android" with warning sign in device manager. I have unrecognised usb device, so i cant set it to usb composite.
What to do? what i miss?
p.s when i am trying use google or amazon drivers set up after fastboot manually selecting from device manager, it says: incompatible.
arshileus said:
I have done this before on windows 10 . But i am on windows 7 now.
After i clicking on unlock.bat, device goes to fastboot mode. At this time i cant find "android" with warning sign in device manager. I have unrecognised usb device, so i cant set it to usb composite.
What to do? what i miss?
p.s when i am trying use google or amazon drivers set up after fastboot manually selecting from device manager, it says: incompatible.
Click to expand...
Click to collapse
Can you help me?
arshileus said:
Can you help me?
Click to expand...
Click to collapse
Could be a borked device, unstable usb interface (either device) or bad cable. Work backwards by trying different cables, different ports on the host (avoid USB3 and hubs) and different hosts. If results are the same you may have a bad device. Good luck.
I did a search on XDA and didn't find anyone quite with this problem. I have other HDX both 7" and 8.9" that I have unlocked bootloader, installed TWRP, and installed ROM's on so I am not new to it.
However, I acquired an 8.9" HDX and it is stuck on the Nougat logo and just stays there. I can boot into fastboot as well as TWRP. When I booted into TWRP I tried factory reset (as it will come up on my computer to where I can access the storage using my Windows 10 machine) as well as Advanced Wipe but it will not wipe the Internal Storage. It still shows all the files that were on there before. How do I go about completely getting it clean to install a nice fresh custom ROM on it?
Any help would be greatly appreciated thanks all!
alias4ever said:
I did a search on XDA and didn't find anyone quite with this problem. I have other HDX both 7" and 8.9" that I have unlocked bootloader, installed TWRP, and installed ROM's on so I am not new to it.
However, I acquired an 8.9" HDX and it is stuck on the Nougat logo and just stays there. I can boot into fastboot as well as TWRP. When I booted into TWRP I tried factory reset (as it will come up on my computer to where I can access the storage using my Windows 10 machine) as well as Advanced Wipe but it will not wipe the Internal Storage. It still shows all the files that were on there before. How do I go about completely getting it clean to install a nice fresh custom ROM on it?
Any help would be greatly appreciated thanks all!
Click to expand...
Click to collapse
There's a chance the eMMC is damaged or a prior owner botched an unlock attempt. Might try booting a freshly downloaded TWRP image from fastboot in case the one that is installed has an issue. This will only work if the bootloader is unlocked.
fastboot boot <twrp.img>
Davey126 said:
There's a chance the eMMC is damaged or a prior owner botched an unlock attempt. Might try booting a freshly downloaded TWRP image from fastboot in case the one that is installed has an issue. This will only work if the bootloader is unlocked.
fastboot boot <twrp.img>
Click to expand...
Click to collapse
If the bootloader is indeed still locked and I have access to the bootloader can I unlock it still and start fresh? I take it the above I do inside the platform-tools folder correct? Thanks Davey so much for your help. I did this multiple times but it's been a while so I'm just trying to refresh my brain!
alias4ever said:
If the bootloader is indeed still locked and I have access to the bootloader can I unlock it still and start fresh? I take it the above I do inside the platform-tools folder correct? Thanks Davey so much for your help. I did this multiple times but it's been a while so I'm just trying to refresh my brain!
Click to expand...
Click to collapse
Consider following the steps in this post which nicely sumarizes the unlock procedure. Not for the faint of heart nor excessively difficult. Ability to closely follow instructions and troubleshoot issues are the keys to success...assuming hardware is ok.
Before jumping in try booting a twrp image to rule out a borked install in the recovery partition. Unlikely, but also easy to check.
Davey126 said:
Consider following the steps in this post which nicely sumarizes the unlock procedure. Not for the faint of heart nor excessively difficult. Ability to closely follow instructions and troubleshoot issues are the keys to success...assuming hardware is ok.
Before jumping in try booting a twrp image to rule out a borked install in the recovery partition. Unlikely, but also easy to check.
Click to expand...
Click to collapse
So to check I would just do what you suggested above with the Fire HDX in Fastboot and connected to my PC correct? Which was:
fastboot boot apollo_twrp-3.2.3-1.img in CMD correct? I just want to make sure I have "all my ducks in a row."
alias4ever said:
So to check I would just do what you suggested above with the Fire HDX in Fastboot and connected to my PC correct? Which was:
fastboot boot apollo_twrp-3.2.3-1.img in CMD correct? I just want to make sure I have "all my ducks in a row."
Click to expand...
Click to collapse
Yup. No damage can come from this attempt. It will either work or not.
Davey126 said:
Yup. No damage can come from this attempt. It will either work or not.
Click to expand...
Click to collapse
This is what I get when I try that:
FAIL: boot not allowed for locked hw.
Any suggestions please? Thanks again!
alias4ever said:
This is what I get when I try that:
FAIL: boot not allowed for locked hw.
Any suggestions please? Thanks again!
Click to expand...
Click to collapse
Indicates bootloader is locked. See previous posts for path forward. Note cautions; don't expect a lot of hand holding if uncomfortable with tools/procedures. Good luck.
Davey126 said:
Indicates bootloader is locked. See previous posts for path forward. Note cautions; don't expect a lot of hand holding if uncomfortable with tools/procedures. Good luck.
Click to expand...
Click to collapse
Hey Davey, one last question I hope. I can't boot into a ROM (I can do either Fastboot or TWRP) to get the unlock code doing the following from the instructions:
2. Turn on ADB-Debuging Mode in Developer Mod by tapping 7 times the build numbers in settings and connect to your computer + trust your device.
3. Excecute "get_code.bat" in the folder above, you will get a new file: unlock.code in the folder.
I can't copy a ROM to TWRP as it won't let me. I have searched and searched and I am stuck again. Please if you don't mind helping me as I remember how to do most everything (it is coming back to me more and more the more I read and what not) but I have never been stuck with the unlock code. Thanks so much.
alias4ever said:
Hey Davey, one last question I hope. I can't boot into a ROM (I can do either Fastboot or TWRP) to get the unlock code doing the following from the instructions:
2. Turn on ADB-Debuging Mode in Developer Mod by tapping 7 times the build numbers in settings and connect to your computer + trust your device.
3. Excecute "get_code.bat" in the folder above, you will get a new file: unlock.code in the folder.
I can't copy a ROM to TWRP as it won't let me. I have searched and searched and I am stuck again. Please if you don't mind helping me as I remember how to do most everything (it is coming back to me more and more the more I read and what not) but I have never been stuck with the unlock code. Thanks so much.
Click to expand...
Click to collapse
Don't worry about the unlock code; you can grab that later. The more immediate task is to install a vulnerable bootloader (aka 'aboot') and update twrp. Keep in mind this may not help if your newly acquired device is severely borked or has a hardware issue.
Davey126 said:
Don't worry about the unlock code; you can grab that later. The more immediate task is to install a vulnerable bootloader (aka 'aboot') and update twrp. Keep in mind this may not help if your newly acquired device is severely borked or has a hardware issue.
Click to expand...
Click to collapse
Well so I followed this thread: https://forum.xda-developers.com/showpost.php?p=75284993&postcount=1006
Then I started here (just past the unlock code):
5. On the Computer go to Device-Manager and change driver in "Other Android" to "Fire Devices - Android Adb Composite Driver" . It should say "Ready" on the Kindle.
6. Now we need to enter Bulk-Mode like the instruction in this thread: Bulk Mode
Type:
Quote:
Code:
fastboot -i 0x1949 erase aboot
fastboot -i 0x1949 reboot
CMD shows that everything was successful but upon the reboot it just tried to boot into the OS instead of Bulk Mode that is installed that it can't boot into. I can still boot back into TWRP 3.1.1-1 as well as Fastboot.
ARGH! Any other suggestions Davey? I'm sorry to keep bugging you I just don't understand what is happening.
alias4ever said:
Well so I followed this thread: https://forum.xda-developers.com/showpost.php?p=75284993&postcount=1006
Then I started here (just past the unlock code):
5. On the Computer go to Device-Manager and change driver in "Other Android" to "Fire Devices - Android Adb Composite Driver" . It should say "Ready" on the Kindle.
6. Now we need to enter Bulk-Mode like the instruction in this thread: Bulk Mode
Type:
Quote:
Code:
fastboot -i 0x1949 erase aboot
fastboot -i 0x1949 reboot
CMD shows that everything was successful but upon the reboot it just tried to boot into the OS instead of Bulk Mode that is installed that it can't boot into. I can still boot back into TWRP 3.1.1-1 as well as Fastboot.
ARGH! Any other suggestions Davey? I'm sorry to keep bugging you I just don't understand what is happening.
Click to expand...
Click to collapse
Sounds like the device/firmware is borked. You can try to issue the erase cmd wothout "-i 0x1949" (fastboot erase aboot) although that too will likely fail. At that point you're pretty much out of options short of a deep technical dive that is fraught with risk. Such travels are above my pay grade; you'd want to reach out to @draxie.
Davey126 said:
Sounds like the device/firmware is borked. You can try to issue the erase cmd wothout "-i 0x1949" (fastboot erase aboot) although that too will likely fail. At that point you're pretty much out of options short of a deep technical dive that is fraught with risk. Such travels are above my pay grade; you'd want to reach out to @draxie.
Click to expand...
Click to collapse
I did send a PM to @draxie so hopefully he can help me and we can get this Fire HDX up and running. Thanks for all your help though @Davey. I really appreciate it. I am going to keep my fingers crossed still though in hopes that draxie can help me. :good::fingers-crossed: