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.
Hi there,
Firstly I apologise, this post may be a little vague, as am having trouble getting the truth out of my son. I was wondering if anyone might be able to help me identify what the heck he has done to his Kindle Fire HD 7"
When you turn the device on, despite initially saying Kindle fire HD, this text is soon replaced with a boot screen animation that simply reads "DROID".
When you begin to use the Kindle there is a small carousel of apps over the larger carousel. Also when you rotate the screen to landscape it doesn't seem to reorientate the display and only shows the top half of the screen. It also seems to crash and won't come out of the lock screen.
I am guessing he has tried to either root it or flash a custom rom, he says he installed an app called root master? But cannot see how an app would grant root access?
We bought this for him as a Christmas present, and whilst am sorely tempted to tell him "tough" as he's obviously tried to do something without fully understanding what he's doing, I would like to be able to sort this as soon as I stop being cross.
So whilst I appreciate this is all a bit vague, does anyone recognise any symptoms, and have any insight into what he might have done and/or installed and is there any sure fire method to get this back for him?
A couple of questions:
-> Is it the 2012 version with the camera and HDMI output, or is it the 2013 version that has neither of these?
-> Can you access the settings and enable ADB?
-> Can you solder or are willing to shell out $10-$15 to fix this?
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<
hi there,
Thanks for the reply.
We got it for him for Christmas 2012.
Can get to settings. I have enabled ADB (just to see if I could, and I can).
Does this mean I might not need a soldering iron?
Do not claim to be any sort of expert, so please assume no knowledge here.
But will carefully follow instructions if there are any.
Am hoping to be able to hand him back a working device when he's learnt his lesson.
Thanks again
I would suggest you to use the Kindle Fire First Aid if fastboot works. That way you can go totally stock. And a few more questions:
Do you have the Android SDK installed on your PC? If yes,try using "adb devices" to see if it recognizes the Kindle
Shut down the Kindle. Boot it up. Do you see an orange Kindle animation only or a blue animation?
I suggest you buy a factory adapter from Team BlackHat here if fastboot doesn't work.
PS: Don't be too cross on him. It's perfectly understandable if he wanted to flash a custom ROM. I ended up hating Amazon after realizing what they did to Android....
SafinWasi said:
I would suggest you to use the Kindle Fire First Aid if fastboot works. That way you can go totally stock.
Click to expand...
Click to collapse
Is this what is being described here?
http://forum.xda-developers.com/showthread.php?t=2096888
If so, I will have a look this evening..
I like the fact that it has "noob" in the post description.
Although I flashed a custom rom onto my Samsung Galaxy S2 a couple of years back (using ODIN) a lot of the instructions in this Kindle Fire section seem to be very confusing. I wish I'd known he was planning to do something like this, as I'd have read up on it for him (and, most likely warned him off, amazon look like they have locked down this tablet to a horrific degree)
SafinWasi said:
And a few more questions:
Do you have the Android SDK installed on your PC? If yes,try using "adb devices" to see if it recognizes the Kindle
Click to expand...
Click to collapse
Okay, that sounds a good first place to start. I don't think I have the SDK currently installed but I guess I can grab it again from google.
I take it if the SDK can "see" it we're halfway there?
Just to clarify:
The device is "quite" responsive.
It will boot up (although I cannot find anything on the internet about this boot animation that just draws the word "DROID" - if I could, I might be able to figure what he's tried to do at least) and you can sort of use it (although there are onscreen glitches as described above) and it freezes up when the screen locks (so you have to reboot every time it locks the screen). But, at least it's not totally D.O.A, I guess.
SafinWasi said:
[*]Shut down the Kindle. Boot it up. Do you see an orange Kindle animation only or a blue animation?
Click to expand...
Click to collapse
It does initially flash up Kindle..
I thought I had solved the problem with a factory reset last night (I'll admit for a second I cheered), but after initially showing Kindle Fire, it then starts going to this blue DROID animation..
SafinWasi said:
I suggest you buy a factory adapter from Team BlackHat here if fastboot doesn't work.
Click to expand...
Click to collapse
Okay, cool I take it this is step three if the Kindle Fire First Aid doesn't work?
SafinWasi said:
PS: Don't be too cross on him. It's perfectly understandable if he wanted to flash a custom ROM. I ended up hating Amazon after realizing what they did to Android....
Click to expand...
Click to collapse
I am a lot calmer today, am sorry that the first post was written in "Angry Dad" mode
I was just annoyed that he tried to deny doing anything to his device, and claimed it was "just an amazon update" (when it was obvious it wasn't).
This is why I am hoping to fix it for him, it was a Christmas present after all, and I would like to (eventually, not right away) hand him back a working Kindle device.
I just wish I wasn't flying so blind.
Thing is I'm not 100% sure he know's what he's done, I think he's just blindly followed a YouTube video or similar and he's ended up with this.
I really, really appreciate you guys taking the time to reply to my post.
Thanks so much for reading and responding.
silentbazz said:
Is this what is being described here?
http://forum.xda-developers.com/showthread.php?t=2096888
If so, I will have a look this evening..
I like the fact that it has "noob" in the post description.
Although I flashed a custom rom onto my Samsung Galaxy S2 a couple of years back (using ODIN) a lot of the instructions in this Kindle Fire section seem to be very confusing. I wish I'd known he was planning to do something like this, as I'd have read up on it for him (and, most likely warned him off, amazon look like they have locked down this tablet to a horrific degree)
Okay, that sounds a good first place to start. I don't think I have the SDK currently installed but I guess I can grab it again from google.
I take it if the SDK can "see" it we're halfway there?
Just to clarify:
The device is "quite" responsive.
It will boot up (although I cannot find anything on the internet about this boot animation that just draws the word "DROID" - if I could, I might be able to figure what he's tried to do at least) and you can sort of use it (although there are onscreen glitches as described above) and it freezes up when the screen locks (so you have to reboot every time it locks the screen). But, at least it's not totally D.O.A, I guess.
It does initially flash up Kindle..
I thought I had solved the problem with a factory reset last night (I'll admit for a second I cheered), but after initially showing Kindle Fire, it then starts going to this blue DROID animation..
Okay, cool I take it this is step three if the Kindle Fire First Aid doesn't work?
I am a lot calmer today, am sorry that the first post was written in "Angry Dad" mode
I was just annoyed that he tried to deny doing anything to his device, and claimed it was "just an amazon update" (when it was obvious it wasn't).
This is why I am hoping to fix it for him, it was a Christmas present after all, and I would like to (eventually, not right away) hand him back a working Kindle device.
I just wish I wasn't flying so blind.
Thing is I'm not 100% sure he know's what he's done, I think he's just blindly followed a YouTube video or similar and he's ended up with this.
I really, really appreciate you guys taking the time to reply to my post.
Thanks so much for reading and responding.
Click to expand...
Click to collapse
Okay,I'll guide you through a step-by-step tutorial to restore your Kindle.
Download and install the Android SDK. That is the first thing any Android modding guy must have. It provides you with the ADB and Fastboot executables which you're gonna need.
Download and install the Kindle Fire HD ADB drivers. You're gonna need them since the official Google drivers that came with the SDK are not supported by Amazon.
Modify your path variable. To do this,right-click on 'My Computer' and select properties. Click on "Advanced System Settings" and then "Environment Variables". At this point,you should copy the path to the tools and platform-tools folders of your SDK and paste them in the "path" system variable . If you want a video tutorial:http://www.youtube.com/watch?v=oaNM-lt_aHw
See if ADB and fastboot works. Open CMD from Run and type in ADB or fastboot. If it returns a lot of text,it's working.
Now type in:
Code:
fastboot -i 0x1949 getvar product
It'll return <waiting for device>
Turn off the Kindle and plug it in. If it boots into fastboot,you're good to go with KFFA
If it doesn't boot into fastboot,you'll have to buy a fastboot adapter or make one.
---------- Post added at 06:53 AM ---------- Previous post was at 06:51 AM ----------
Although I have no idea how he got the Droid animation....
SafinWasi said:
Although I have no idea how he got the Droid animation....
Click to expand...
Click to collapse
Okay, apparently, he went to this 1mobile market to get a one click root app.
I have not been able to find the app myself, but am very worried that he's been downloading apps from an unofficial app store.
The change to the boot animation seems to have been achieved using a Xposed app (that requires XBlast?). It was after installing this, and changing the boot animation that he says the Kindle started to behave weirdly.
Have not had the time yet to sit down and go through the instructions provided, thank you for those, I will set time aside at the weekend as I don't want to rush it.
At least now I know where the weird boot animation came from
I provide this info as a warning to others.
silentbazz said:
Okay, apparently, he went to this 1mobile market to get a one click root app.
I have not been able to find the app myself, but am very worried that he's been downloading apps from an unofficial app store.
The change to the boot animation seems to have been achieved using a Xposed app (that requires XBlast?). It was after installing this, and changing the boot animation that he says the Kindle started to behave weirdly.
Have not had the time yet to sit down and go through the instructions provided, thank you for those, I will set time aside at the weekend as I don't want to rush it.
At least now I know where the weird boot animation came from
I provide this info as a warning to others.
Click to expand...
Click to collapse
1mobile is an OK place to download apps from. You just have to make sure the dev is reputable. XBlast can mess a tablet up if you play to much with it.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
I agree. It's tricky,XBlast. Any progress?
Sent from my device running CyanogenMod 11
SafinWasi said:
I agree. It's tricky,XBlast. Any progress?
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
Alas, not good..
Am stumbling at the first hurdle really, have installed the AndroidSDK all okay but am trying to add the Kindle Fire drivers into the SDK as per amazon's instructions here .
But the SDK they describe doesn't seem to match the SDK environment I have installed (I have version 23.0.0.1245622 of eclipse installed, which seems to have a different menu structure to the one amazon describe?) and whenever I try and get
Eclipse to access the URL amazon has told me to (http://kindle-sdk.s3.amazonaws.com/addon.xml) I get the message "No repository found at http://kindle-sdk.s3.amazonaws.com/addon.xml"
Am really not sure what I'm doing wrong..
silentbazz said:
Alas, not good..
Am stumbling at the first hurdle really, have installed the AndroidSDK all okay but am trying to add the Kindle Fire drivers into the SDK as per amazon's instructions here .
But the SDK they describe doesn't seem to match the SDK environment I have installed (I have version 23.0.0.1245622 of eclipse installed, which seems to have a different menu structure to the one amazon describe?) and whenever I try and get
Eclipse to access the URL amazon has told me to (http://kindle-sdk.s3.amazonaws.com/addon.xml) I get the message "No repository found at http://kindle-sdk.s3.amazonaws.com/addon.xml"
Am really not sure what I'm doing wrong..
Click to expand...
Click to collapse
Don't do that. Just download my Flasher and extract it. There is another zip inside,which has the drivers. Just install them normally.
Sent from my device running CyanogenMod 11
silentbazz said:
Alas, not good..
Am stumbling at the first hurdle really, have installed the AndroidSDK all okay but am trying to add the Kindle Fire drivers into the SDK as per amazon's instructions here .
But the SDK they describe doesn't seem to match the SDK environment I have installed (I have version 23.0.0.1245622 of eclipse installed, which seems to have a different menu structure to the one amazon describe?) and whenever I try and get
Eclipse to access the URL amazon has told me to (http://kindle-sdk.s3.amazonaws.com/addon.xml) I get the message "No repository found at http://kindle-sdk.s3.amazonaws.com/addon.xml"
Am really not sure what I'm doing wrong..
Click to expand...
Click to collapse
Hi! One click root app was probably called VROOT. VROOT is still not identified as safe as there may be malware, sorry :\ However if you have a FASTBOOT cable go on this website and you should be able to restore it without SDK.
http://androidcowboy.com/2013/07/how-to-recover-bricked-kindle-fire-hd/
by the way once choosing an "option" please wait for at least 20 minutes as restoring the device takes a long process.
silentbazz said:
Am really not sure what I'm doing wrong..
Click to expand...
Click to collapse
Your tablet still has fastboot access which means it's almost surely restorable. The flasher offered above will work and so will the System Restore Tool. You just run the bat and wait to be restored. Make sure your drivers are installed properly. Windows 8/7 64bit need to be put in test mode so your drivers will install right.
Windows is not going to let you do this until you disable device driver signature enforcement.
Disable device driver signature enforcement in Windows 7 read on. Windows 8 has different steps.
Both must be done from the administrator profile to work right
Both of these are for Windows 7 X64 users.
Windows 7 X32 and earlier version users do not have this issue
A.*
1. Reboot and on start up press F8 a couple times.
2. Scroll down to "Disable Driver Signature Enforcement."*
Note: This must be done on every bootup you want to install something not MS signed.*
B. For a more permanent solution.*
1. First go and uninstall the driver (delete driver) you want to replace and then restart your computer.*
2. Now go to the start menu and type cmd.
3. Right click on "cmd" and open a command prompt with elevated privileges (run as administrator.)
4. Now type these in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set TESTSIGNING ON
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
4. Now install the driver you want.
5. Restart the computer.
6. Profit.
Note: If you do this right, you will see "Test Mode Windows 7 Build 7601" (or something comparable) in the lower right corner of your screen. This means that drivers not signed by MS can be installed without getting the Windows has installed the best driver already bit.*
If you opt to take your computer out of test mode, the drivers will more than likely be replaced by MS drivers next time. To exit test mode follow steps 1,2 and 3 in part B of my writeup and type these commands in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS*
bcdedit.exe -set TESTSIGNING OFF
Now restart computer.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
SafinWasi said:
Okay,I'll guide you through a step-by-step tutorial to restore your Kindle.
Download and install the Android SDK. That is the first thing any Android modding guy must have. It provides you with the ADB and Fastboot executables which you're gonna need.
Download and install the Kindle Fire HD ADB drivers. You're gonna need them since the official Google drivers that came with the SDK are not supported by Amazon.
Modify your path variable. To do this,right-click on 'My Computer' and select properties. Click on "Advanced System Settings" and then "Environment Variables". At this point,you should copy the path to the tools and platform-tools folders of your SDK and paste them in the "path" system variable . If you want a video tutorial:http://www.youtube.com/watch?v=oaNM-lt_aHw
See if ADB and fastboot works. Open CMD from Run and type in ADB or fastboot. If it returns a lot of text,it's working.
Now type in:
Code:
fastboot -i 0x1949 getvar product
It'll return <waiting for device>
Turn off the Kindle and plug it in. If it boots into fastboot,you're good to go with KFFA
If it doesn't boot into fastboot,you'll have to buy a fastboot adapter or make one.
.
Click to expand...
Click to collapse
Okay, I got the amazon drivers installed on my machine, and had fastboot and adb working from the command prompt after adding all of the paths to the PATH environment setting.
I typed in:
Code:
fastboot -i 0x1949 getvar product
and I got the prompt <waiting for device>
However when I attach the device, it just boots (with the weird droid animation) - I cannot see anything to say that it has fastbooted. Does it display any different?
I have also typed adb devices and I don't think my PC is seeing the Kindle Fire HD as I get no devices shown in the List of Devices?
Does this mean I need a fastboot cable?
Would installing cyanogenmod on this be an option now? Or would that just make matters worse at this stage?
++ EDIT ++
Actually, uninstalled and reinstalled amazon adb drivers, and retyped:
Code:
adb devices
and it output:
D025A0A0241220KP device
so tried the fastboot -i 0x1949 getvar product command again, but still the device booted normally
SafinWasi said:
Don't do that. Just download my Flasher and extract it. There is another zip inside,which has the drivers. Just install them normally.
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
By the way just wanted to say thanks for providing the Flasher.
Amazon drivers extracted and installed like a charm (once I allowed them to install to the default location)
silentbazz said:
Does this mean I need a fastboot cable?
Click to expand...
Click to collapse
The only time you don't need one is if you can access the OS and you have functioning root. If you don't have this then you must have a fastboot cable. If you have a Motorola cord laying around try that.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
The only time you don't need one is if you can access the OS and you have functioning root. If you don't have this then you must have a fastboot cable. If you have a Motorola cord laying around try that.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Ahh okay, I understood that I might be able to get the device to enter fastboot without a cable.
I must have read this wrong.
Okay, as I am not in the United States I am guessing eBay.co.uk is my best option?
Will something like this do the trick?
silentbazz said:
Ahh okay, I understood that I might be able to get the device to enter fastboot without a cable.
I must have read this wrong.
Okay, as I am not in the United States I am guessing eBay.co.uk is my best option?
Will something like this do the trick?
Click to expand...
Click to collapse
Should work fine.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
Should work fine.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Okay, great, have got one ordered, so will hopefully be able to get this sorted soon.
A sincere thanks to everyone who has offered sage advice above.
Some ace tips here, hopefully I'll get this sorted for him
Thanks again!!!!
silentbazz said:
Okay, great, have got one ordered, so will hopefully be able to get this sorted soon.
A sincere thanks to everyone who has offered sage advice above.
Some ace tips here, hopefully I'll get this sorted for him
Thanks again!!!!
Click to expand...
Click to collapse
You're welcome. Keep us updated.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
I'm having trouble locating current info to answer my question. I've read on older threads that installing a custom rom on my Fire would then require me to use Fastboot every time I needed to restart it. Is that still true?
I have a 5.1.1 device that I'm thinking of putting CM on. I know that I can't install TWRP on it but can I at least turn the device on/off without using my pc to boot up CM?
I just order another Fire and am hoping it comes with 5.0. Would that mean that once TWRP is installed, I'm finished with fastboot?
Thanks. Sorry for the n00b questions. I'm coming from a trusty HP Touchpad and the Fire seems a bit complicated when it comes to the details.
theechap said:
I'm having trouble locating current info to answer my question. I've read on older threads that installing a custom rom on my Fire would then require me to use Fastboot every time I needed to restart it. Is that still true?
I have a 5.1.1 device that I'm thinking of putting CM on. I know that I can't install TWRP on it but can I at least turn the device on/off without using my pc to boot up CM?
I just order another Fire and am hoping it comes with 5.0. Would that mean that once TWRP is installed, I'm finished with fastboot?
Thanks. Sorry for the n00b questions. I'm coming from a trusty HP Touchpad and the Fire seems a bit complicated when it comes to the details.
Click to expand...
Click to collapse
Well if you are rooted there will be many apps to use so you can just reboot. Cm should already have those baked into the rom. In cm you may need to turn that reboot function on in dev tool after clicking build number 10 times. Hope this helps
Sent from my LG-H901 using XDA Premium HD app
You'll root your device, install FlashFire, then use FlashFire to install CM 12.1 + Open GApps + SuperSU. I have installed CM 12.1 on 3 devices so far; you don't need to use a computer after CM is installed to aid in the booting process.
Hi folks,
I'm using a Fire 7 5th Gen rooted and with the excellent Nexus Rom (02/12/2017 version). Following the upgrade I've had an issue whereby as soon as the screen goes to sleep the device appears to power off. It takes several presses of the power button to turn on again and booting into fastboot doesn't seem to work. The battery monitor shows approx 52% power (which seems about correct to me, based on how I've used it since last charge) so I didn't think it would be a battery issue. Does anyone have any idea what might be going on here and what I might do to fix it? Any help would be massively appreciated.
Thanks,
Jonathan
jonathanmoneill said:
Hi folks,
I'm using a Fire 7 5th Gen rooted and with the excellent Nexus Rom (02/12/2017 version). Following the upgrade I've had an issue whereby as soon as the screen goes to sleep the device appears to power off. It takes several presses of the power button to turn on again and booting into fastboot doesn't seem to work. The battery monitor shows approx 52% power (which seems about correct to me, based on how I've used it since last charge) so I didn't think it would be a battery issue. Does anyone have any idea what might be going on here and what I might do to fix it? Any help would be massively appreciated.
Thanks,
Jonathan
Click to expand...
Click to collapse
Symptoms are similar to a recently reported issue in the Lineage 12.1 thread if you applied the latest Nexus update. If that's the case simply roll back to the prior build.
Hi Davey,
Thanks for the update, I saw that thread after my OP and did wonder. I'm going to either roll back to an earlier version of the Nexus ROM or try a stable version of the Lineage ROM. As I can't get the device to stay on long enough to use FlashFire, I'm assuming an ADB sideload will be my best bet. Slightly off topic but is there one of those ROMs you'd recommend over the other?
jonathanmoneill said:
Hi Davey,
Thanks for the update, I saw that thread after my OP and did wonder. I'm going to either roll back to an earlier version of the Nexus ROM or try a stable version of the Lineage ROM. As I can't get the device to stay on long enough to use FlashFire, I'm assuming an ADB sideload will be my best bet. Slightly off topic but is there one of those ROMs you'd recommend over the other?
Click to expand...
Click to collapse
If the device shuts down while the Amazon logo is being displayed then it may be hardware related. ADB sideload of FireOS (be sure to get the build right) is your best option, preferably starting from stock recovery.
At present only two Custom ROMs are under active maintenance: Fire Nexus and LineageOS 12.1. Both are stable and feature complete. While I generally prefer pure AOSP (favoring Nexus) Lineage works well with this device and requires less customization to get the UX I prefer. Note: This device is not my daily driver so keeping things simple takes priority. Nexus is akin to a blank sheet of paper just waiting for some love while Lineage already has a few lines drawn in.
Davey126 said:
If the device shuts down while the Amazon logo is being displayed then it may be hardware related. ADB sideload of FireOS (be sure to get the build right) is your best option, preferably starting from stock recovery.
At present only two Custom ROMs are under active maintenance: Fire Nexus and LineageOS 12.1. Both are stable and feature complete. While I generally prefer pure AOSP (favoring Nexus) Lineage works well with this device and requires less customization to get the UX I prefer. Note: This device is not my daily driver so keeping things simple takes priority. Nexus is akin to a blank sheet of paper just waiting for some love while Lineage already has a few lines drawn in.
Click to expand...
Click to collapse
Thanks for the ROM advice. I love the Nexus ROm but I've been tempted by lineage for a while so I might take this opportunity to give it a go
In relation to sorting my current issues, the device doesn't shut down while the grey logo is being displayed, the OS loads and I usually get about 30-90 seconds of functioning before it dies again. Sorry if this seems like a NOOB question but is there any reason not to ADB sideload my chosen Lineage or Nexus ROM directly? Or if I'm going to reinstall fireOS just choose the factory reset option from fastboot (on those rare occasions I can get fastboot to work).
jonathanmoneill said:
Sorry if this seems like a NOOB question but is there any reason not to ADB sideload my chosen Lineage or Nexus ROM directly? Or if I'm going to reinstall fireOS just choose the factory reset option from fastboot (on those rare occasions I can get fastboot to work).
Click to expand...
Click to collapse
Amazon's crippled bootloader disables most commands and (obviously) ADB isn't an option from native fastboot. I doubt sideload will permit installation of a custom ROM from stock recovery. However, if you have done it before (and it works) great!
Davey126 said:
Amazon's crippled bootloader disables most commands and (obviously) ADB isn't an option from native fastboot. I doubt sideload will permit installation of a custom ROM from stock recovery. However, if you have done it before (and it works) great!
Click to expand...
Click to collapse
I hadn't tried this before and just as you predicted it didn't work. I was wondering how can I find out which version of the stock fireOS I need? Or will a factory reset from recovery still permit me to root again from scratch....
jonathanmoneill said:
I hadn't tried this before and just as you predicted it didn't work. I was wondering how can I find out which version of the stock fireOS I need? Or will a factory reset from recovery still permit me to root again from scratch....
Click to expand...
Click to collapse
You can try a factory reset. Failing that and w/o knowledge of the FireOS build that was previously installed go with 5.3.1 which is the last rootable version and will avoid a potential (recoverable) brick scenario if you inadvertently attempt to downgrade the bootloader.
Davey126 said:
You can try a factory reset. Failing that and w/o knowledge of the FireOS build that was previously installed go with 5.3.1 which is the last rootable version and will avoid a potential (recoverable) brick scenario if you inadvertently attempt to downgrade the bootloader.
Click to expand...
Click to collapse
Factory reset from the recovery screen seems to have solved my issues, tablet is purring like a kitten. Also saved myself the .bin for 5.3.1 in case of emergency. Thanks again for the advice on this
jonathanmoneill said:
Factory reset from the recovery screen seems to have solved my issues, tablet is purring like a kitten. Also saved myself the .bin for 5.3.1 in case of emergency. Thanks again for the advice on this
Click to expand...
Click to collapse
I was the one having the update issues, but it was on the Lineage ROM! Looks like whatever ggow did, it's affecting both Nexus and Lineage. I think I'll just roll back to the previous build then restore apps.