Related
Hi all
I have a new Kindle Fire HD 7". According to 'About' it's version is 7.3.1. The model number on the back is X43Z60
I've read just about every thread in this forum about rooting, flashing recoveries, using adb, fastboot etc etc.. I even made my own factory cable. I have been successful in rooting the device, I can access it via adb with no issues and I have even managed to install SafeStrap on it (though no ROM's will install) but I can NOT get it to boot into fastboot mode. I have successfully written to the idme bootmode 4002 and rebooted it but it has no effect. Windows does not detect any device other than the adb interface at any point. I even tried this while booted into safestrap and it too had no effect.
I'd like to know if anyone is able to say definitively what it is I need to do to get a custom ROM working. It doesn't help either that people seem to refer to the devices they have written their software for simply as "Kindle fire HD 7" with no mention of version, etc. meaning I have little indication as to the suitability of the instructions.
I saw mention of a 'short' mod where I am able to take the cover off and short a particular exposed connector to the frame and enable fastboot mode, but couldn't actually find any further information. Not afraid to give it a go but I need to know what to do.
Any help is appreciated
Thanks
A fast boot cable just puts five volts on pin 4 on the micro usb...that's the short mod....you short the five volt pin 1 to pin 4...note this has to be on the micro usb side you will blow up your usb port if you do it on the usb end
Safe strap is not the route you want to take I would at this point restore back to stock and install twrp as your second boot loader then installing a Rom should be simple
Sent from my GT-P3110 using xda app-developers app
TimTams said:
Hi all
I have a new Kindle Fire HD 7". According to 'About' it's version is 7.3.1. The model number on the back is X43Z60
I've read just about every thread in this forum about rooting, flashing recoveries, using adb, fastboot etc etc.. I even made my own factory cable. I have been successful in rooting the device, I can access it via adb with no issues and I have even managed to install SafeStrap on it (though no ROM's will install) but I can NOT get it to boot into fastboot mode. I have successfully written to the idme bootmode 4002 and rebooted it but it has no effect. Windows does not detect any device other than the adb interface at any point. I even tried this while booted into safestrap and it too had no effect.
I'd like to know if anyone is able to say definitively what it is I need to do to get a custom ROM working. It doesn't help either that people seem to refer to the devices they have written their software for simply as "Kindle fire HD 7" with no mention of version, etc. meaning I have little indication as to the suitability of the instructions.
I saw mention of a 'short' mod where I am able to take the cover off and short a particular exposed connector to the frame and enable fastboot mode, but couldn't actually find any further information. Not afraid to give it a go but I need to know what to do.
Any help is appreciated
Thanks
Click to expand...
Click to collapse
Visit the thread in my signature for the Kindle Fire HD 7". I addressed the issue of Amazon OS 7.3.1 with Step 1: Rooting.
Thanks for the info about the cable, ended up not needing it
seokhun said:
Visit the thread in my signature for the Kindle Fire HD 7". I addressed the issue of Amazon OS 7.3.1 with Step 1: Rooting.
Click to expand...
Click to collapse
Thanks!! I must have overlooked your guide, the titles of a few threads are very similar
Yours is the only one that didn't require the use of fastboot to get TWRP on the device, it worked flawlessly!
Cheers
One very happy TimTams :laugh:
Hey, I recently rooted my Kindle Fire HD and everything was working great, until I installed an Xposed tweak that caused my Kindle to start boot looping and then thereafter I went ahead and screwed it up even worse - by messing with various fastboot methods to get it working again. Yeah... I should have just left it as it was, I know...
I've read about how there are signature checks whenever the Kindle boots up which I'm assuming I don't have anymore. So, I'm curious if there is anyway to come back from this? From what I've read, if I had backed up the partitions, technically I should have been able to restore them - but unfortunately here we are.
I've also downloaded the latest update from Amazon 'update-kindle-11.3.1.0_user_310084920' and after converting it to a zip file, there is a 'boot.img' and a 'recovery.img' which I would assume would have the signatures already within them, but no system.img. Is there anyway for someone to create an exact backup of that file, or is that not possible right now without a second bootloader?
I'm honestly really unsure of what to do here, I've tried a myriad of different approaches and still it looks like this is a bad brick... However I do hope someone out there has a solution, I'd love to get this device working again.
Oh and what happens whenever I start it up, is that I just get the Amazon Kindle Fire Logo (Pure White), without any changes. It doesn't turn gold with the animation or anything.
Hyperiunn said:
Hey, I recently rooted my Kindle Fire HD and everything was working great, until I installed an Xposed tweak that caused my Kindle to start boot looping and then thereafter I went ahead and screwed it up even worse - by messing with various fastboot methods to get it working again. Yeah... I should have just left it as it was, I know...
I've read about how there are signature checks whenever the Kindle boots up which I'm assuming I don't have anymore. So, I'm curious if there is anyway to come back from this? From what I've read, if I had backed up the partitions, technically I should have been able to restore them - but unfortunately here we are.
I've also downloaded the latest update from Amazon 'update-kindle-11.3.1.0_user_310084920' and after converting it to a zip file, there is a 'boot.img' and a 'recovery.img' which I would assume would have the signatures already within them, but no system.img. Is there anyway for someone to create an exact backup of that file, or is that not possible right now without a second bootloader?
I'm honestly really unsure of what to do here, I've tried a myriad of different approaches and still it looks like this is a bad brick... However I do hope someone out there has a solution, I'd love to get this device working again.
Oh and what happens whenever I start it up, is that I just get the Amazon Kindle Fire Logo (Pure White), without any changes. It doesn't turn gold with the animation or anything.
Click to expand...
Click to collapse
The 2013 Kindle Fire HD is not setup for Xposed yet. There is no bootloader access yet therefore there is no way to recover yet. You have two options at this point. Wait until there is a bootloader exploit or contact Amazon for an exchange.
The only things available are root, remove OTA updates and remove lock screen ads. Even Google Play is only for window shopping at the moment.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
The 2013 Kindle Fire HD is not setup for Xposed yet. There is no bootloader access yet therefore there is no way to recover yet. You have two options at this point. Wait until there is a bootloader exploit or contact Amazon for an exchange.
The only things available are root, remove OTA updates and remove lock screen ads. Even Google Play is only for window shopping at the moment.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For anyone wondering, xposed actually works perfectly with a good number of modules, but don't install Xthemeengine, that'll cause the bootloop.
Fastboot
As long as you can boot into fastboot-mode nothing is lost. (if you can't -> buy a fastboot-cable. it is much cheaper than a new Kindle. They cost about 15$).
I used this useful tool. It just flashes the old system, boot and recovery on your Kindle. (all files are included in the downloadable zip file).
This tool was very useful for me and saved my Kindle very often (I am a real flashoholic...). Maybe there is something like this for the new 2013 KFHD too?
Gamingmayr said:
As long as you can boot into fastboot-mode nothing is lost. (if you can't -> buy a fastboot-cable. it is much cheaper than a new Kindle. They cost about 15$).
I used this useful tool. It just flashes the old system, boot and recovery on your Kindle. (all files are included in the downloadable zip file).
This tool was very useful for me and saved my Kindle very often (I am a real flashoholic...). Maybe there is something like this for the new 2013 KFHD too?
Click to expand...
Click to collapse
Nah nothing so far for the 2013 unfortunately. I don't think there's been much interest in this model as of yet.
Hyperiunn said:
Nah nothing so far for the 2013 unfortunately. I don't think there's been much interest in this model as of yet.
Click to expand...
Click to collapse
I've been interested. Unfortunately, my mother won't let me touch her new 2013 Fire HD. Still, if you can find someone who's rooted and not bricked, maybe they could backup their boot, system, and recovery .imgs for you and post them for you. And since they're already rooted, you would be too (someone correct me if I'm wrong). If I could get a temporary root or find a way to remove root later I would back them up for you.
The system restore tool for the 2012 Fire HD flashes the boot, recovery, and system partitions. Theoretically, the same tool would work, but only if you replaced the .img files with the ones for the 2013 Fire HD.
Gamingmayr said:
As long as you can boot into fastboot-mode nothing is lost. (if you can't -> buy a fastboot-cable. it is much cheaper than a new Kindle. They cost about 15$).
I used this useful tool. It just flashes the old system, boot and recovery on your Kindle. (all files are included in the downloadable zip file).
This tool was very useful for me and saved my Kindle very often (I am a real flashoholic...). Maybe there is something like this for the new 2013 KFHD too?
Click to expand...
Click to collapse
There is no confirmation that a fastboot cord even works with the 2013 model nor are the stock images available yet. The 2012 KFHD and the 2013 KFHD do not use the same images.
---------- Post added at 11:28 PM ---------- Previous post was at 11:26 PM ----------
Hyperiunn said:
For anyone wondering, xposed actually works perfectly with a good number of modules, but don't install Xthemeengine, that'll cause the bootloop.
Click to expand...
Click to collapse
It won't work on the 2013 Kindle fire HD yet though. Since that is the topic here I guess that narrows it down to this tablet not all the others don't it.
Fastboot cable works just fine with the one I have.
Hey everyone I totally screwed up my new KFHD and I would love some help. I tried to root it a couple days ago with the KFSOWI all in one tool and it seemed to work for a few minutes. SuperSU installed correctly and installed its binary but when I tried to use the root explorer in ES File Explorer it said that it failed so I opened up SuperSU again and it told me it needed to install the binary again as if it wasn't rooted. It failed to install it and Root Checker told me it wasn't rooted so I tried to re-root it with the same KFSOWI tool.
This is when it got messed up. The tool said it rooted successfully again but when I tried to boot it up normally (I had been using a factory cable to get into Fastboot) it got stuck on the Kindle Fire logo screen (the white one not the orange one). I thought maybe it was a problem with the root so I tried to unroot it with another tool and ever since then it briefly shows a red screen at boot and then stays on the Fastboot logo. I've tried holding the power button down for 20 seconds, restoring the firmware to stock (got an error about system.img saying that it wasn't a sparse file), and restoring to an older firmware. None of this has made any difference.
I read somewhere that the red screen is a sign of a missing bootloader but if that's true how do I get back to the stock bootloader? I had 11.3.2.2/7.4.8 installed before all this happened if that helps. I'm willing to try anything at this point. I would like to at least be able to use the Play Store but if I have to stick to stock FireOS I'll just endure it. If you have any questions ask away! Thank you all for your help.
pgautraud said:
Hey everyone I totally screwed up my new KFHD and I would love some help. I tried to root it a couple days ago with the KFSOWI all in one tool and it seemed to work for a few minutes. SuperSU installed correctly and installed its binary but when I tried to use the root explorer in ES File Explorer it said that it failed so I opened up SuperSU again and it told me it needed to install the binary again as if it wasn't rooted. It failed to install it and Root Checker told me it wasn't rooted so I tried to re-root it with the same KFSOWI tool.
This is when it got messed up. The tool said it rooted successfully again but when I tried to boot it up normally (I had been using a factory cable to get into Fastboot) it got stuck on the Kindle Fire logo screen (the white one not the orange one). I thought maybe it was a problem with the root so I tried to unroot it with another tool and ever since then it briefly shows a red screen at boot and then stays on the Fastboot logo. I've tried holding the power button down for 20 seconds, restoring the firmware to stock (got an error about system.img saying that it wasn't a sparse file), and restoring to an older firmware. None of this has made any difference.
I read somewhere that the red screen is a sign of a missing bootloader but if that's true how do I get back to the stock bootloader? I had 11.3.2.2/7.4.8 installed before all this happened if that helps. I'm willing to try anything at this point. I would like to at least be able to use the Play Store but if I have to stick to stock FireOS I'll just endure it. If you have any questions ask away! Thank you all for your help.
Click to expand...
Click to collapse
ok first ting i wanna ask is what do you mean 11.3.2/7.4.8, because 11.x.x is for teh 2013 and 7.x.x is for teh 2012 kindle. Also red screen doesnt mean you are missing the bootloader, if you were missing that the device wouldnt even turn on. That error you got when trying to restore the device is probably part of why its not working, probably need to fix that to fix the device, it never reflashed the system partition when it errored and said that the image was not sparse, which is a bit odd in itself considering how the method we use to fix it works.
stunts513 said:
ok first ting i wanna ask is what do you mean 11.3.2/7.4.8, because 11.x.x is for teh 2013 and 7.x.x is for teh 2012 kindle. Also red screen doesnt mean you are missing the bootloader, if you were missing that the device wouldnt even turn on. That error you got when trying to restore the device is probably part of why its not working, probably need to fix that to fix the device, it never reflashed the system partition when it errored and said that the image was not sparse, which is a bit odd in itself considering how the method we use to fix it works.
Click to expand...
Click to collapse
I have the 2013 version, I just bought it from Amazon two weeks ago and it said the firmware version was 11.3.2.2. I had said 7.4.8 because whenever I searched for a way to root 11.3.2.2 the most recent information I could find talked about 7.4.8 so I thought they were the same thing. So is there a way for me to sparse the system image? Or are there system images out there that are sparsed? If you have a tool that you prefer over others I would love to try it.
Try this, I think this was the thread I was looking for and if its the same one you posted a link to then my bad because I'm half asleep.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Try this, I think this was the thread I was looking for and if its the same one you posted a link to then my bad because I'm half asleep.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
What am I supposed to try?
Wow I was half asleep after all I didn't post the link... Lemme get my bearings and retrace my line of though.
Edit: here's the link I was intending on posting: http://forum.xda-developers.com/showthread.php?t=2685090
Weird thing is i remember copying the URL for the thread, Idk why I never pasted it.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Wow I was half asleep after all I didn't post the link... Lemme get my bearings and retrace my line of though.
Edit: here's the link I was intending on posting: http://forum.xda-developers.com/showthread.php?t=2685090
Weird thing is i remember copying the URL for the thread, Idk why I never pasted it.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thanks for the link! I actually tried the newest version of his tool and it works up until it says "waiting for boot..." I assume it means it's waiting for a normal boot but since I can't get it to boot past the Fastboot logo (even with a normal cable or no cable at all) it never gets any further. Any suggestions?
Sounds like the bootimg needs to be reflashed. Sometimes a bad bootimg causes it to kick into fastboot upon boot.
Sent from my Amazon Kindle Fire HD using Tapatalk
I have a Kindle Fire HD that has never been rooted (although I tried like heck last night when it was 7.4.8) and today I see it is 7.4.9 and have been told this is unrootable? Is this correct?
If so, is there anyway to add the Google Play store without rooting. I bought this on eBay listed as unable to be registered but I didn't care because I didn't want the Fire OS, my plan was to make it a full fledged android tablet with a custom ROM.
What can I do now?
GameGuru41 said:
I have a Kindle Fire HD that has never been rooted (although I tried like heck last night when it was 7.4.8) and today I see it is 7.4.9 and have been told this is unrootable? Is this correct?
If so, is there anyway to add the Google Play store without rooting. I bought this on eBay listed as unable to be registered but I didn't care because I didn't want the Fire OS, my plan was to make it a full fledged android tablet with a custom ROM.
What can I do now?
Click to expand...
Click to collapse
Fastboot with a fastboot cable or maybe a "adb reboot bootloader" if you get lucky, then downgrade the os with kindle fire first aid, proceed with the usual procedure.
Sent from my Amazon Tate using Tapatalk
Ok I ordered a fast boot factory cable today. Do I have to downgrade or can I just use the cable install a custom ROM?
GameGuru41 said:
Ok I ordered a fast boot factory cable today. Do I have to downgrade or can I just use the cable install a custom ROM?
Click to expand...
Click to collapse
I just flashed my 7.4.9 KFHD 2012 with CM11 - I used the tutorial on the CM wiki...Worked perfectly.
medeman said:
I just flashed my 7.4.9 KFHD 2012 with CM11 - I used the tutorial on the CM wiki...Worked perfectly.
Click to expand...
Click to collapse
Did you first root your device? Did you use a fastbootcable?
Thx in common
Even though this says for the 2013 version of the Kindle Fire HD, it does work on the the HD 7 running 7.4.9. It is how I rooted mine. You will have to manually install SuperSu which you can get from Chainfire's site.
medeman said:
I just flashed my 7.4.9 KFHD 2012 with CM11 - I used the tutorial on the CM wiki...Worked perfectly.
Click to expand...
Click to collapse
Im trying that tonight on a kfhd 8.9 with the 8.4.9 Hoping i can get in to go to fastboot. If i can not get this going soon i may fix it permanently using the microwave technique (as in putting the kinlde fire in a 1000watt microwave oven for 10 minutes and cooking it...)
If it comes down to this maybe ill record it for all to see haha.
Stupid amazon and their forcing us in to the x.4.9 update. This should not be legal for any company to do period. Would be like a auto maker sneaking in to your driveway and removing your performance enhancing upgrades and using a welding torch to put their factory garbage back on. And yes it is the same idea. We all root or kindles and other android devices (and apple products) to give us a better performing and or more feture rich device. Those who do this understand this voids the warranty and are not worried about that at all. Heck many of us own tablets etc that are long out of warranty so amazon etc will not even need to worry about that side of thing.
Sorry for the venting but yeesh this is irritating
$yr0 said:
Did you first root your device? Did you use a fastbootcable?
Thx in common
Click to expand...
Click to collapse
No my device wasn't rooted and barely used at all at this point.
I did use a fastboot cable, yeah...
I also have 7.4.9 and rooted it with Root with Restore by Bin4ary, using Option 1, via ADB. Worked just as it did with previous OS.
KFFirstAide didn't root it.
What did you try to root it with?
Issue with rooting 7.4.9
I tried using the root with recovery binary to root my kindle fire hd, but it won't run fireflash, and busy box was not included when it rooted. Am I missing something here? It's a Kindle Fire HD 7", running 7.4.9.
Downgrade it with SRT or kffa, it will be pre-rooted. You may need a fastboot cable to do this though if "adb reboot bootloader" doesn't do the trick.
Safestrap users, see ggow's thread instead.
Using draxie's tool (upHDX), I've created TWRP-friendly ZIPs of the stock firmware that leave the recovery and bootloader intact. Moreover, I've disabled OTA updates as well as lockscreen ads.
I'll try to keep this thread up-to-date should Amazon push any new versions. Feel free to make requests for any previous releases.
4.5.5 (user_455001320)
thor
apollo
Side note: if anyone's ever worked with the AROMA installer, shoot me a PM.
That‘s really great.
Maybe someday we will have the whole family of TWRP flashable HDX Fire OS. :smile:
---
BTW
any way to root it?
FotixChiang said:
That‘s really great.
Maybe someday we will have the whole family of TWRP flashable HDX Fire OS. :smile:
---
BTW
any way to root it?
Click to expand...
Click to collapse
I think you should be able to just flash a SuperSU ZIP over it.
Excellent - Thank you!!
EncryptedCurse said:
Safestrap users, see ggow's thread instead.
Using draxie's tool (upHDX), I've created TWRP-friendly ZIPs of the stock firmware that leave the recovery and bootloader intact. Moreover, I've disabled OTA updates.
I'll try to keep this thread up-to-date should Amazon push any new versions. Feel free to make requests for any previous releases.
4.5.5 (user_455001320)
thor
apollo
Side note: if anyone's ever worked with the AROMA installer, shoot me a PM.
Click to expand...
Click to collapse
I can't get this to work after wiping my system, dalvik cache, and cache partitions. It gets stuck at "Finishing startup..." or "Starting applications...".
Edit: Wiped /data and now it boots, but the setup screen force closes.
bmccoy11 said:
I can't get this to work after wiping my system, dalvik cache, and cache partitions. It gets stuck at "Finishing startup..." or "Starting applications...".
Edit: Wiped /data and now it boots, but the setup screen force closes.
Click to expand...
Click to collapse
Sorry, I didn't bother testing. Looks like I renamed one too many APKs that are required during setup.
I've uploaded the new versions (which should also disable lockscreen ads).
EncryptedCurse said:
Sorry, I didn't bother testing. Looks like I renamed one too many APKs that are required during setup.
I've uploaded the new versions (which should also disable lockscreen ads).
Click to expand...
Click to collapse
Looks like my Kindle is softbricked, for now, at least. For some reason, USB storage no longer works on my HDX and neither of my PCs recognize it in recovery or fastboot mode. Could you tell me the APK you renamed so I can rename it back in TWRP?
Anyone else having same issues?
Sent from my Kindle Fire HDX using XDA Premium 4 mobile app
---------- Post added at 09:42 AM ---------- Previous post was at 09:39 AM ----------
I
And mega app wants to be used to download this .. Thanks for keeping this great tab relative..I'll hold a spell until the wrinkles are worked out
Sent from my Kindle Fire HDX using XDA Premium 4 mobile app
bmccoy11 said:
Looks like my Kindle is softbricked, for now, at least. For some reason, USB storage no longer works on my HDX and neither of my PCs recognize it in recovery or fastboot mode. Could you tell me the APK you renamed so I can rename it back in TWRP?
Click to expand...
Click to collapse
Try removing the .bak extension on /priv-app/DeviceSoftwareOTAContracts.apk and /app/otaverifier.apk.
Everything is working fine on my end, so I'm not sure what else to tell you.
EncryptedCurse said:
Try removing the .bak extension on /priv-app/DeviceSoftwareOTAContracts.apk and /app/otaverifier.apk.
Everything is working fine on my end, so I'm not sure what else to tell you.
Click to expand...
Click to collapse
I renamed those two applications back in TWRP, and it still isn't booting... :/
bmccoy11 said:
I renamed those two applications back in TWRP, and it still isn't booting... :/
Click to expand...
Click to collapse
You may want to refocus your efforts on getting device to communicate with a host in fastboot and then repair (reflash) twrp from there. Assuming you have an unlocked bootloader as that was a prerequisite for previous steps. I know it sounds stupid but try switching USB cables; amazing how often that works. Also do the driver dance on your preferred host, get rid of any hubs, only use USB2 ports, etc. Anything to get it communicating again.
You'll need to research how to flash twrp from fastboot. This is obviously dangerous and to my knowledge has not been attempted on a HDX. Theoretically possible and one of the many reasons for running with an unlocked bootloader. Good luck.
I have an unlocked bootloader (Apollo, have been running on 14.3.1.0 in a safestrap slot for the past two years, waiting for unlock, then flashed the bootloader update to 14.3.2.3 and TWRP 2.8.7.0), I did a basic wipe in TWRP, then flashed this ROM via TWRP, but after rebooting, then connecting to WiFi and entering my Amazon registration info, it asks for language selection then starts the normal UI temporarily then immediately goes back to asking for language selection, repeating over and over.
Davey
126 did it work for you. Love to try it
Sent from my Kindle Fire HDX using XDA Premium 4 mobile app
davekaz said:
Davey
126 did it work for you. Love to try it
Click to expand...
Click to collapse
Not yet - waiting for reported issue(s) to play out. Currently on Nexus v4 (v2 prior) and not missing out any Amazon functionality so would only flash this to confirm install procedures and basic functionality. Personal preference item; I understand some prefer FireOS UI and don't need access to Google Play/Services.
Davey126 said:
Not yet - waiting for reported issue(s) to play out. Currently on Nexus v4 (v2 prior) and not missing out any Amazon functionality so would only flash this to confirm install procedures and basic functionality. Personal preference item; I understand some prefer FireOS UI and don't need access to Google Play/Services.
Click to expand...
Click to collapse
Same I was just curious. I was on v4 and loving it but google services updated and started crashing continually so im on slim and besides Bluetooth issues its great. Thanks for reply
Sent from my Kindle Fire HDX using XDA Premium 4 mobile app
bmccoy11 said:
I renamed those two applications back in TWRP, and it still isn't booting... :/
Click to expand...
Click to collapse
adb works IN twrp, so as long as you have working adb and twrp, you can adb push a new zip to /sdcard to install...
Sent from my Kindle Fire HDX using Tapatalk
_Alex_ said:
fyi, adb works IN twrp, so as long as you have working adb and twrp, you can adb push a new zip to /sdcard to install...
Sent from my Kindle Fire HDX using Tapatalk
Click to expand...
Click to collapse
Of course, I've already tried ADB and fastboot. It won't show up in the device manager at all, I've tried different USB cables, different PCs, I even disassembled it to make sure the connections from the back plate to the mainboard were good. My mainboard must be bad.
bmccoy11 said:
Of course, I've already tried ADB and fastboot. It won't show up in the device manager at all, I've tried different USB cables, different PCs, I even disassembled it to make sure the connections from the back plate to the mainboard were good. My mainboard must be bad.
Click to expand...
Click to collapse
I just looked at the apollo image zip and noticed that the modem is still installed from the updater script... (hmm, your 4.5.2 for Thor also has the modem install too). I was just about to test drive this too, but I'm not up for modem backups tonight.
Has anyone ever gotten this to work?
Sent from my Kindle Fire HDX using Tapatalk
davekaz said:
Same I was just curious. I was on v4 and loving it but google services updated and started crashing continually so im on slim and besides Bluetooth issues its great. Thanks for reply
Sent from my Kindle Fire HDX using XDA Premium 4 mobile app
Click to expand...
Click to collapse
As an aside I'm running v4 with the latest Google Services (7.8.99) and have not experienced any problems. FCs, etc are rare.
Davey126 said:
... how to flash twrp from fastboot. This is obviously dangerous and to my knowledge has not been attempted on a HDX. Theoretically possible and one of the many reasons for running with an unlocked bootloader. Good luck.
Click to expand...
Click to collapse
Just FYI @Davey126 flashing TWRP from fastboot is the easiest task that can be done with working fastboot (plus in case of HDX with unlocked bootloader, which is necessary). I did flash TWRP several times via fastboot just to confirm to me that I have unlocked bootloader...
Code:
fastboot flash recovery recovery_image_name.img
Obviously there is a lot of space for user error (faulty usb cable, corrupt download, drunk dude trying to do something he seen, hear, watched somewhere, etc.), and that is what is really dangerous here... irresponsible peoples trying to do something they do not understand (at least partially)...
Sorry, I often include screenshots to prove my assertions, but right now I am not in the mood to fight again with fastboot drivers for windows, which are probably live their own life thinking "G**O user, we are not going to flash ANYTHING today!"