Related
Hello Everyone, first post after several hours of research and first attempt to root and flash a device.
A little about the device, it is a Kindle Fire (non-HD)
I did a factory reset on the device before doing anything.
I followed the instruction i found on this forum to install Kindle Fire Utility 9.6
Following this, I downloaded and installed, JB-AOKP_otter_unofficial_Oct-17-12.
I followed this install with: gapps-jb-2012-0726-signed
Everything was going great. All of the sudden I got a pop-up stating Process com.android.phone has stopped. As fast as I press "OK" it returned.
The only resolution I have been able to get is to force the tablet back into TWRP and restore it, as once it appears there is no way around it.
has anyone encountered this issue and found a solution?
Thanks in advance, I am new to rooting (first shot ever) and eager to learn what I can about it.
Adam
Good morning,
As a follow up, I tried to re-install the Android system. Somehow I managed to delete too much by way of wiping the system and basically locked the KF up until I was able to mount it as a USB drive. I placed the OS file back in the directory (the original KF software was gone). I reloaded the OS and seemingly it works correctly.
Up to this point I have not had the error return, so the only real change was the complete removal of the KF software. The unfortunate part, is if I were to ever want to sell the KF I have no way to return it to stock, Atleast not that I have figured out yet.
Now on to searching for a volume control, that is easy to use....
ResqComm said:
Hello Everyone, first post after several hours of research and first attempt to root and flash a device.
A little about the device, it is a Kindle Fire (non-HD)
I did a factory reset on the device before doing anything.
I followed the instruction i found on this forum to install Kindle Fire Utility 9.6
Following this, I downloaded and installed, JB-AOKP_otter_unofficial_Oct-17-12.
I followed this install with: gapps-jb-2012-0726-signed
Everything was going great. All of the sudden I got a pop-up stating Process com.android.phone has stopped. As fast as I press "OK" it returned.
The only resolution I have been able to get is to force the tablet back into TWRP and restore it, as once it appears there is no way around it.
has anyone encountered this issue and found a solution?
Thanks in advance, I am new to rooting (first shot ever) and eager to learn what I can about it.
Adam
Click to expand...
Click to collapse
Can't get any computer or OS to recognize my kindle fire HD 7 even with the factory cable. Help!!!:crying:
I was in fastboot mode and did a reboot and when it booted back up it stuck on the start screen and won't let me do anything anymore. The fastboot cable I bought doesn't put it into fastboot mode and it is not recognized by any of my computers or OS. Tried everything but my mac so far. That includes XP, 7, 8 and Ubuntu.
I'll try a hard reset again. I've done that several times hoping that one time it would get recognized by the computer.
Before you panic too much, you need give more information. What were you doing to "brick it"?
Have you tried a hard reset btw? (Hold the power button down for 30 seconds) then let go and turn on?
Worked for me before when I thought messed up
Kgyuszko
Sent from my KFTT using xda app-developers app
duncanidahoe said:
Can't get any computer or OS to recognize my kindle fire HD 7 even with the factory cable. Help!!!:crying:
I was in fastboot mode and did a reboot and when it booted back up it stuck on the start screen and won't let me do anything anymore. The fastboot cable I bought doesn't put it into fastboot mode and it is not recognized by any of my computers or OS. Tried everything but my mac so far. That includes XP, 7, 8 and Ubuntu.
I'll try a hard reset again. I've done that several times hoping that one time it would get recognized by the computer.
Click to expand...
Click to collapse
You were doing something in fastboot mode, What was it? did you try to install the 2nd bootloader by hashcode or just restoring your device?
duncanidahoe said:
Can't get any computer or OS to recognize my kindle fire HD 7 even with the factory cable. Help!!!:crying:
I was in fastboot mode and did a reboot and when it booted back up it stuck on the start screen and won't let me do anything anymore. The fastboot cable I bought doesn't put it into fastboot mode and it is not recognized by any of my computers or OS. Tried everything but my mac so far. That includes XP, 7, 8 and Ubuntu.
I'll try a hard reset again. I've done that several times hoping that one time it would get recognized by the computer.
Click to expand...
Click to collapse
I did something similar and have what i though 'bricked' the kindle. Have another good read through hashcode 2nd bootloader thread, others have has similar, and there are some instructions on how to resolve fastboot cable not recognised, and kndle is bricked. if not, go down the firstaide thread, that also deals with bricked kindles.
good luck
kgyuszko
have you successed to fix it ?
unluckily, I have the same problem.
factory cable is no use.
gogolovedell said:
have you successed to fix it ?
unluckily, I have the same problem.
factory cable is no use.
Click to expand...
Click to collapse
I just had same problem. Factory cable no use. I intalled Kinology but thought to restore to a Kindle version. When the bootloader was being flashed, a black brick ... Anyone knows how to deal with this? I even opened the case and unplug battery.
qiudongxiao said:
I just had same problem. Factory cable no use. I intalled Kinology but thought to restore to a Kindle version. When the bootloader was being flashed, a black brick ... Anyone knows how to deal with this? I even opened the case and unplug battery.
Click to expand...
Click to collapse
Your problem will be overcome if you follow here
Hi, I also ahve a black brick. It won't start after I used the wrong bootloader(the one for KFHD8 isntead if KFHD7)
I do have a factory cable but still nothing.
duncanidahoe said:
Can't get any computer or OS to recognize my kindle fire HD 7 even with the factory cable. Help!!!:crying:
I was in fastboot mode and did a reboot and when it booted back up it stuck on the start screen and won't let me do anything anymore. The fastboot cable I bought doesn't put it into fastboot mode and it is not recognized by any of my computers or OS. Tried everything but my mac so far. That includes XP, 7, 8 and Ubuntu.
I'll try a hard reset again. I've done that several times hoping that one time it would get recognized by the computer.
Click to expand...
Click to collapse
gogolovedell said:
have you successed to fix it ?
unluckily, I have the same problem.
factory cable is no use.
Click to expand...
Click to collapse
qiudongxiao said:
I just had same problem. Factory cable no use. I intalled Kinology but thought to restore to a Kindle version. When the bootloader was being flashed, a black brick ... Anyone knows how to deal with this? I even opened the case and unplug battery.
Click to expand...
Click to collapse
kindleuser01 said:
Hi, I also ahve a black brick. It won't start after I used the wrong bootloader(the one for KFHD8 isntead if KFHD7)
I do have a factory cable but still nothing.
Click to expand...
Click to collapse
You all have a paperweight on your hands. The factory cable was the very last resort. If you're in warranty, send it in for a replacement.
possible solution
searching i found this page where explain how to fix the hard brick, black screen no sing of life, cant post links so, search in google "new life for a dead Kindle fire hd, is in mascote..... can any expert try it and explain that to the rest of us,
bryanfeanor said:
searching i found this page where explain how to fix the hard brick, black screen no sing of life, cant post links so, search in google "new life for a dead Kindle fire hd, is in mascote..... can any expert try it and explain that to the rest of us,
Click to expand...
Click to collapse
A while back, I brought this question up to Pokey9000, the developer of FireFireFire and Firekit for the Original Kindle Fire. His exact response to me was...
When the OMAP USB boots, it first waits a bit to handshake with a host. If the handshake is successful, the host sends a small loader to the OMAP that then does some hardware init and handshakes again with the host to get a payload to shove into RAM. This loader is similar to x-loader in that it has to be small to fit in the SRAM of the OMAP, and does low level initialization like mux, clock, and memory setup. However it differs in that it replaces the MMC and FAT handling in x-loader with USB loading as there's not enough room for a generic x-loader that does MMC and USB.
On HS (fused) OMAPs this initial USB loader payload must be signed just like x-loader has to be for eMMC boot. If the payload doesn't have a signature that checks out, the OMAP halts until it's reset. This is enforced by hardware, so short of finding a sploit in the OMAP ROM code or a copy of Amazon's USB boot tools used in factory it's not going to work.
TL;DR not likely.
Click to expand...
Click to collapse
Considering his knowledge of bootloaders and low level hardware stuffs far exceeds mine, and the fact that he's been looking at this issue ever since the B&N Nook devices (maybe even longer), I have to assume he knows what he's talking about.
The information on the page at Mascote seems to contradict what Pokey9000 says because usbboot uses an a-boot(x-loader) instead of this not-so-typical USB loader mentioned previously. And the answer to whether or not the author was actually successful in reviving the KFHD using this method has been left a little ambiguous.
But, as much as it would suck for me to have been the d*ck that told everyone that it couldn't be done, I would LOVE to be proven wrong.
I'd say, if you have a hard-bricked KFHD, then I guess there's not much else you can lose by testing it out.
soupmagnet said:
A while back, I brought this question up to Pokey9000, the developer of FireFireFire and Firekit for the Original Kindle Fire. His exact response to me was...
Considering his knowledge of bootloaders and low level hardware stuffs far exceeds mine, and the fact that he's been looking at this issue ever since the B&N Nook devices (maybe even longer), I have to assume he knows what he's talking about.
The information on the page at Mascote seems to contradict what Pokey9000 says because usbboot uses an a-boot(x-loader) instead of this not-so-typical USB loader mentioned previously. And the answer to whether or not the author was actually successful in reviving the KFHD using this method has been left a little ambiguous.
But, as much as it would suck for me to have been the d*ck that told everyone that it couldn't be done, I would LOVE to be proven wrong.
I'd say, if you have a hard-bricked KFHD, then I guess there's not much else you can lose by testing it out.
Click to expand...
Click to collapse
I have tried this on the 2012 KFHD (tate) and found it to work. After trying every recovery option via adb/fastboot. plus using factory cable. i was left with no choice. i used a pin needle with grounding wire attached to chassis of the kindle. be carefull the top is power(button?), bottom is restart. if you lose contact at all during the process. It will boot/reboot as normal.
with this method you must use CMD(in admin mode from pc) and adb push/pull/install/uninstall as needed. device has no input in this boot.
bryanfeanor said:
searching i found this page where explain how to fix the hard brick, black screen no sing of life, cant post links so, search in google "new life for a dead Kindle fire hd, is in mascote..... can any expert try it and explain that to the rest of us,
Click to expand...
Click to collapse
Were you able to get yours going using that?
go8soccer said:
Were you able to get yours going using that?
Click to expand...
Click to collapse
sadly no, it´s been more than 3 years now that my kindle brick.
Djskizo said:
I have tried this on the 2012 KFHD (tate) and found it to work. After trying every recovery option via adb/fastboot. plus using factory cable. i was left with no choice. i used a pin needle with grounding wire attached to chassis of the kindle. be carefull the top is power(button?), bottom is restart. if you lose contact at all during the process. It will boot/reboot as normal.
with this method you must use CMD(in admin mode from pc) and adb push/pull/install/uninstall as needed. device has no input in this boot.
Click to expand...
Click to collapse
I just recently bricked mine. Black screen. And all it does is charge. I can tell because the cable and device gets hot. Before i waste my time, would this help me. And yes i have that exact version
Otak98 said:
I just recently bricked mine. Black screen. And all it does is charge. I can tell because the cable and device gets hot. Before i waste my time, would this help me. And yes i have that exact version
Click to expand...
Click to collapse
A few hours ago I was given a Tate to fix, and having read around the subject, Djskizo's post sounds either like a complicated homemade factory fastboot cable, or to be honest a fake. Perhaps the OP meant fastboot instead of ADB, but that combined with vague details puts me off trying it. Try a factory cable perhaps, I'm gonna try making one (short out micro usb pins 1 and 4) and I'll get back to you on the results.
Any updates?
Any updates on this? I hard bricked mine yesterday flashing the wrong bootloader. Can't believe how easy it is to brick it. I just have myself to blame, I know...
I saw this post on Mascote and it seems like a post for KFHD Gen 1. Is this the one being referred to, by you guys?
Only Djskizo seems to claim that this works for KFHD Gen 2(tate) so far. Is this true?
Djskizo said:
I have tried this on the 2012 KFHD (tate) and found it to work. After trying every recovery option via adb/fastboot. plus using factory cable. i was left with no choice. i used a pin needle with grounding wire attached to chassis of the kindle. be carefull the top is power(button?), bottom is restart. if you lose contact at all during the process. It will boot/reboot as normal.
with this method you must use CMD(in admin mode from pc) and adb push/pull/install/uninstall as needed. device has no input in this boot.
Click to expand...
Click to collapse
I cant seem to figure out how to do the usbboot trick. I have a fire hd 3rd gen. On the board there is actually a point that says usb boot next to it but when i ground that out and plug it in it's still froze at the unanimated boot screen, sometimes the background also turns white? What am i doing wrong or is this point labeled just to confuse me
Added photos
Here is the pic of the usb boot and the board name.
I WAS BACKING UP MY KINDLE FIRE WITH KF First Aide AND TO MY HORROR IT HAD INSTALLED THE ORIGINAL KINDLE FIRE 2 OS INSTEAD OF MY 7" KINDLE FIRE HD OS I DID NOT COMMAND KF First Aide TOOL TO DO THIS AND I SWEAR TO GOD I DIDN'T. I SELECTED FOR IT TO BACK UP MY ORIGINAL OS TO THE BACK UP FILE. NOW ALL IT DOES IS BOOT DISPLAYS KINDLE FOR A SECOND THEN GOES BRIGHT RED AND I HAVE NO IDEA HOW TO GET IN TO FAST BOOT MODE FROM HERE!!! I AM VERY ANGRY AT THE THE DEVELOPER OF KF First Aide TOOL!!! CAN SOMEONE HELP ME PLEASE. :MY QUESTION IS IF YOU COULD SO KINDLY HELP ME....HOW DO I GET IN TO FAST BOOT MODE WHEN YOU CAN NOT ENTER THE OPERATING SYSTEM CAN YOU DO IT MANUALLY OR NOT?........
I HAVE MANAGED TO CAPTURE THE KINDLE LOGO IN THE 1 SECOND IT IS DISPLAYED AND A PICTURE OF THE RED SCREEN
IF THAT HELPS
ANY HELP WOULD BE AMAZING I AM SO UPSET AND FRUSTRATED :crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
pretty much the same thing just happend to me but in different words. We will both get through this together. I'm searching right now on what needs to be done.
plottr said:
pretty much the same thing just happend to me but in different words. We will both get through this together. I'm searching right now on what needs to be done.
Click to expand...
Click to collapse
Thanks buddy I will help you as much as I can with info I find. iv been told I need to get it in to fast boot mode with a factory cable but then saying that I read in another post that does not work iv purchased one of eBay to try out so ill let you know if that works
You can reflash stockboot.img and stockrecover.img files by following step 5 and it will be work well.
putin86 said:
You can reflash stockboot.img and stockrecover.img files by following step 5 and it will be work well.
Click to expand...
Click to collapse
I know that but can't enter fastboot mode
jmar8124 said:
I know that but can't enter fastboot mode
Click to expand...
Click to collapse
That's why you need the factory cable; It's used to boot the Kindle directly into FastBoot mode. From my understanding, the only way a factory cable would fail is if the bootloader is damaged.
Protomartyr said:
That's why you need the factory cable; It's used to boot the Kindle directly into FastBoot mode. From my understanding, the only way a factory cable would fail is if the bootloader is damaged.
Click to expand...
Click to collapse
Ok iv just got one of eBay now how do I use it sorry for the noody question do I just power it on and plug it in and its in fastboot? Also how could I have damaged the bootloader I hope I haven't how will I know if the bootloader its damaged? All I did was install the wrong os from the wrong kindle do your restore packages contain a bootloader?
thanks for your help
jmar8124 said:
Ok iv just got one of eBay now how do I use it sorry for the noody question do I just power it on and plug it in and its in fastboot? Also how could I have damaged the bootloader I hope I haven't how will I know if the bootloader its damaged? All I did was install the wrong os from the wrong kindle do your restore packages contain a bootloader?
thanks for your help
Click to expand...
Click to collapse
I will try to answer to the best of my ability (as I am still a noob with the Kindle HD). If anyone more knowledgeable is reading, you're input would be much appreciated
- Using the factory cable: I think you need to plug in the cable to the Kindle HD (powered off). Then plug in the other end to the computer, and it should power on to FastBoot mode. As far as what to do in FastBoot mode and what commands to use, you will probably have to ask someone more knowledgeable than me.
- Bootloader: When people say 'the bootloader is damaged' they are most likely referring to the fact that the device cannot accept FastBoot commands. When you turn on the Kindle, the bootloader decides whether to turn on the kindle in normal mode or fastboot mode. So if you can't get into fastboot mode, then the bootloader is not functioning properly for some reason.
As far as how you would damage the bootloader? Well... Iike I said before I'm a noob with the Kindle so I can't really answer this. From what I've read, the most common mistake is that people have flashed something onto the Kindle Fire HD 7 that was meant for another version of the device.
I suggest you to try working with one of the senior members/developers to troubleshoot and fix your problem.
Protomartyr said:
I will try to answer to the best of my ability (as I am still a noob with the Kindle HD). If anyone more knowledgeable is reading, you're input would be much appreciated
- Using the factory cable: I think you need to plug in the cable to the Kindle HD (powered off). Then plug in the other end to the computer, and it should power on to FastBoot mode. As far as what to do in FastBoot mode and what commands to use, you will probably have to ask someone more knowledgeable than me.
- Bootloader: When people say 'the bootloader is damaged' they are most likely referring to the fact that the device cannot accept FastBoot commands. When you turn on the Kindle, the bootloader decides whether to turn on the kindle in normal mode or fastboot mode. So if you can't get into fastboot mode, then the bootloader is not functioning properly for some reason.
As far as how you would damage the bootloader? Well... Iike I said before I'm a noob with the Kindle so I can't really answer this. From what I've read, the most common mistake is that people have flashed something onto the Kindle Fire HD 7 that was meant for another version of the device.
I suggest you to try working with one of the senior members/developers to troubleshoot and fix your problem.
Click to expand...
Click to collapse
thanks for all your help its been great ill let you know if the fast-boot lead works unfortunately the stock charging/data lead did not work because it does not supply power to 4th pin like the fastboot leads do to enter fastboot. im normally a wiz with android but the kinle fire hd 7 is one of the worst tabs i have ever owned. im not sure if you are familiar with the AOSP but part of the rules and agreements manufacturers make with Google if they choose to use android is that the system is open source and the ability for advanced super users to modify and customize android how they want it not how the device manufacturer puts it e.g. apple ios (closed source) the manufacturer is allowed to add a boot-loader and stock recovery to prevent accidental damages like wiping partitions etc.... and due to people complaining a lot of manufacturers have not included a boot-loaded unlock tool like htc dev web site but unfortunately you have got amazon...who have locked the boot-loader, disabled button combination and installed a very minimal recovery with just factory reset and reboot, this is actually against the AOSP and i do not know why Google have not done something about this its very frustrating for all of us we have to make our own system recovery tools because amazon do not include one and other such features like 2ndinit boot-loader < (thanks for that) they have actually refereed to the device os as kindle os when its an android 4.0.1 SDK build they make me so angry now i have literally got a £159 brick! i understand its an ebook but they agreed to install android as the default os so they should do it properly haha!!
but im sure in the end google will do something about it an sue them for millions well fingers crossed haha
Hello there!
First of all, sorry for my bad english :/
Well i have the Kindle Fire HD 7. Tate Version.
So i had the Customrom Knology. After a year or so i developed some bugs, so i wanted to set it new etc.
Well i accidently erased the whole bootloader etc. :/
I have a factory cable. Via the Laptop of my Girlfriend i can connect the Kindle with factory cable in fastboot.
Then i ran the KFHD_SRTv1.3.5
Also SR-Tool.
After use Function 1 or 2.
Restore factory rooted etx.
I cant Start the kindle and its still in bootloop. Means Logo repeat and repeat Blinking.
Well when i try to erase the cache and userdata it takes LOOONG time for the userdata. i let it for hours but no result.
Well on PC itselfs i can Use the adb commands in the CMD window. But its waiting for Device. Both PC and Laptop have Windows 7 64 Bit
Pls help me :/
Trailerpark1 said:
Hello there!
First of all, sorry for my bad english :/
Well i have the Kindle Fire HD 7. Tate Version.
So i had the Customrom Knology. After a year or so i developed some bugs, so i wanted to set it new etc.
Well i accidently erased the whole bootloader etc. :/
I have a factory cable. Via the Laptop of my Girlfriend i can connect the Kindle with factory cable in fastboot.
Then i ran the KFHD_SRTv1.3.5
Also SR-Tool.
After use Function 1 or 2.
Restore factory rooted etx.
I cant Start the kindle and its still in bootloop. Means Logo repeat and repeat Blinking.
Well when i try to erase the cache and userdata it takes LOOONG time for the userdata. i let it for hours but no result.
Well on PC itselfs i can Use the adb commands in the CMD window. But its waiting for Device. Both PC and Laptop have Windows 7 64 Bit
Pls help me :/
Click to expand...
Click to collapse
Its gonna be hard to do anything if your PC doesn't recognize it or if your tablet doesn't respond to anything. Sounds to me like you're gonna have to get the stock firmware back on the device and start over with getting the second bootloader installed.
N_psycho_PD_uh? said:
Its gonna be hard to do anything if your PC doesn't recognize it or if your tablet doesn't respond to anything. Sounds to me like you're gonna have to get the stock firmware back on the device and start over with getting the second bootloader installed.
Click to expand...
Click to collapse
Well as i said with the laptop i can connect... how do i Install the Stockrom?
If you have a stock firmware .img then you should be able to flash it through fastboot.
Y?
Well which is the right firmware for me?
Trailerpark1 said:
Y?
Well which is the right firmware for me?
Click to expand...
Click to collapse
Its been a while since I've messed with a kindle so I'm not sure what firmware you need. That is decided by which model/version of kindle you have. I have the very first kindle, its been almost two years since I did any custom stuff to it and I've gone through many other devices since then. I wish I could help with an exact answer, I was only trying to get you headed in the right direction. Find your firmware based on which kindle you have.
Well i know which my kindle is. The CMD Command said, that the firmware is on the kindle. and then still bootloop
Trailerpark1 said:
Well i know which my kindle is. The CMD Command said, that the firmware is on the kindle. and then still bootloop
Click to expand...
Click to collapse
OK, so your firmware is still there and still shows but your bootloader is wiped out? OK, same answer, reflash your stock firmware to see if it will repair the bootloader and see if it will boot, if you've already tried flashing and it did nothing to restore your bootloader then I'm not sure what you can do about that, I don't understand the stock kindle stuff as well as I do other android devices, its kind of in its own class of android because its more android-ish than it is actual full on android so I don't know its elements are quite different.
Well thankl you then. Maybe anyone can help instead of u :/
Trailerpark1 said:
Well thankl you then. Maybe anyone can help instead of u :/
Click to expand...
Click to collapse
As I said, I wasn't trying to give you a definite answer, I was just trying to get you in the right direction. It IS the only response you've gotten so I wouldn't be so snide if I were you, I could have not answered and you would still be waiting for an answer from someone even now. I've told you what you can do to get straight, from what I've experienced the only thing you can do from the point that you're at is do some extensive searching on Google to find the build number of the stock firmware your device shipped with based on which version of kindle that you have and install it through fastboot, I know of nothing else that will restore a device from the state yours is in. If it doesn't work then the device is probably dead and useless.
Sorry pal, i doesnt want to be rude or snyde.. Im rly grateful to you.
as i said my english is bad.. and i had a long day... Sorry for being inpolite.
Trailerpark1 said:
Sorry pal, i doesnt want to be rude or snyde.. Im rly grateful to you.
as i said my english is bad.. and i had a long day... Sorry for being inpolite.
Click to expand...
Click to collapse
No problem, I was only trying to help in the capacity that I could. Have you taken what I've told you and asked around in other threads how to go about using it to get your kindle fixed?
Have you tried getting someone with the same device as yours that still has the stock firmware like yours to do a ROM dump in terminal emulator to create an .img for you then upload it so you can download it then try pushing it to your device through terminal on PC? It may work for you. Can you even boot to recovery? I expect not since you killed your bootloader. Have you tried flashing recovery through fastboot then trying to boot to recovery? I'm not sure that will work either but its worth trying.
Found my fire tablet with a black screen and in Amazon system recovery <3e> this morning - not sure how it got into that state & how to get out of it. To my knowledge I didn't press any combination of keys that would get me into that state. It had been only very low battery when I plugged it into the electrical socket last night but I didn't touch it until the morning when I found it in this black screen state.
From searching I think this is the Amazon version of Android System Recovery screen. The exact options are:
-------
Amazon system recovery <3>
Volume up/down to move highlight;
enter button to select.
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
----------
I haven't rooted the tablet although I did apply the "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)"
(http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122)
I've had it for about a month without problems although a couple of days ago it kept trying to update several times in succession.
It has attempted to update a couple of times in the past, which put me into a panic at the time but when I'd check afterwards it would still show 5.0.1. firmware. Also the difference this time was that in the past it would only attempt to update the once, not several times in succession.
I'd assumed that installing "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)" doesn't stop the fire downloading updates but prevents them being installed. So when it happened in the past I didn't worry.
I'm not sure what to do (logically I'd assume I should just select the 1st option and reboot) but I'm not sure how I even got into this screen and if there's a reason for it so hoped someone might be able to advise me.
With thanks & crossed fingers
Frankie
Sorry - one other question!
Which key is the "enter button"?
FrankieChen said:
Sorry - one other question!
Which key is the "enter button"?
Click to expand...
Click to collapse
I've not used it but as we only have three buttons I'm going with the power button.
Pond-life said:
I've not used it but as we only have three buttons I'm going with the power button.
Click to expand...
Click to collapse
That's what I suspected!
Update
Well I ran out of power so the tablet switched off.
When I plugged it into an electricity socket, I decided to try the "reboot system now" option but it just rebooted and cam back to the same screen. I tried it about 4 times with the same result so I tried the "power down" option but it still returned to the same screen when switched back on.
Would really appreciate anyone's help.
Hmm, is there anything in the recovery logs?
Maybe reboot to bootloader, and see if it'll let you twrp to it from a pc, head to the twrp thread and grab the files.
fastboot boot TWRP_Fire_2.8.7.0.img
If it'll do that it's not on 5.1.1 at least, if not it might have tried to get there.
I haven't followed your instructions yet as after I posted last, it started to flash an error message along the lines of battery was too low to "factory reset" and something else - I don't recall what though. I didn't actually select any options apart from reboot and power down.
It was plugged in at the time but I unplugged it & replugged it in, in case for some reason it wasn't charging.
Since then the error message has stopped flashing and I just have a blank screen although you can see it is backlit. Pressing the power button has no effect
And that's on the charger it came with?
It's not looking good.
FrankieChen said:
...I haven't rooted the tablet although I did apply the "Installing Google Framework/Playstore...
...I'd assumed that installing "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)" doesn't stop the fire downloading updates but prevents them being installed....
Click to expand...
Click to collapse
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.
julianpaul said:
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.
Click to expand...
Click to collapse
True but the thread he's referring to does offer that function as an option in the batch file.
http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122
Tomsgt has put together a little install bat (Amazon-Fire-5th-Gen-Install-Play-Store.zip)
Now includes Removing Advertising and Blocks Over the Air System Updates (02 Nov 2015)
Click to expand...
Click to collapse
julianpaul said:
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.
Click to expand...
Click to collapse
It's still useful information - thanks
It's on the charger it came with and it has finally returned to the same Amazon system recovery screen.
In regards to preventing the updates - I think I did that when I installed the google apps but it was the 1st time i ever did this (it's my 1st tablet), and as it was over a month ago I can't be sure - this is all very new to me.
There are 4 recovery logs, completely meaningless to me.
/cache/recovery/last_kmsg
/cache/recovery/last_log
/cache/recovery/last_log1
/cache/recovery/last_log2
the kmsg log zooms past too fast to read with endless pages dealing with "swapper/0"
the last_log seems to have stuff reffering to tzdata, build, product.cpu, ro.product, dalvik and so on . Log1 and log2 seem to be similar stuff but shorter.
Any idea what I should be looking for?
I hoped it would be readable, build number might yield clues.
Given it will show something seems worth trying to see if twrp can see it in bootloader.
It may not have any thing to do with the updates as it was working after the updates had tried to install though I have to admit I only used it for a few minutes and I didn't check it before I plugged it in to charge the night before I found the black screen.
I don't actually have a clue what you mean when you say "twrp can see it in bootloader." so I will have to spend some time reading the forums to figure out what to do.
In desperation this morning I took the wipe data/factory reset option but it didn't work. It returned with the same screen and the error message
E:Error in /cache/recovery/dropbox_last_kmsg (Read-only file system)
I had installed the dropbox app but I had never actually signed in so there wouldn't be any data there.
After rebooting and being returned to the same screen, I attempted again to wipe data/factory reset.
This time it gave the message "data wipe complete" but still returned to the Recovery screen.
I've read the term "bricked" in several of the forums - is this what has happened to my device?
I wondered if I should contact Amazon about it as it's still under warranty but wondered if by installing gapps (and most likely having prevented updates as I followed all the instructions), whether I'd have invalidated my warranty.
FrankieChen said:
After rebooting and being returned to the same screen, I attempted again to wipe data/factory reset.
This time it gave the message "data wipe complete" but still returned to the Recovery screen.
I've read the term "bricked" in several of the forums - is this what has happened to my device?
I wondered if I should contact Amazon about it as it's still under warranty but wondered if by installing gapps (and most likely having prevented updates as I followed all the instructions), whether I'd have invalidated my warranty.
Click to expand...
Click to collapse
At this point, if you have adb drivers (or are comfortable installing them) you may as well try sideloading an update bin file. Links are here. I'd get the 3820 file.
If you want to do this, post back and I or someone will give you the steps. Otherwise, Amazon has been good about replacing tablets if you just describe what you say in the 1st paragraph of your post.
FrankieChen said:
It may not have any thing to do with the updates as it was working after the updates had tried to install though I have to admit I only used it for a few minutes and I didn't check it before I plugged it in to charge the night before I found the black screen.
I don't actually have a clue what you mean when you say "twrp can see it in bootloader." so I will have to spend some time reading the forums to figure out what to do.
Click to expand...
Click to collapse
use the reboot to bootloader option
set pc up with fastboot and see if it can be booted into twrp by fastboot
http://forum.xda-developers.com/showpost.php?p=63635664&postcount=9
http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548
Thank you for the replies. Sorry not to have responded earlier, I had a busy few days and although I have spent a lot of hours trying to read through the forums and find out about twrp, this is the 1st opportunity I have had to get back to trying to resolve the problem.
If I understand correctly, DoLooper has suggested sideloading an update bin file. (3820). I just started trying to do this but as the file to be downloaded is over 600MB and I am on a very slow connection it's showing it's going to take between 7-8 hours to download. If I take this option I will need to wait until tomorrow when I can get to a faster internet.
Pond-life, you have suggested that I
1. "use the reboot to bootloader option"
I'm presuming that this means that I have to select this option from the recovery screen on the tablet - does the tablet have to be attached to the pc via the USB cable when I select the option?
What should I expect once I have selected this option?
Would the tablet not need to be rooted to access the bootloader (as it isn't)?
2. "set pc up with fastboot and see if it can be booted into twrp by fastboot"
When I 1st got the tablet I had difficulties getting the adb drivers to install on my pc and after several days of trying I ended up doing it on another pc which I no longer have access to.
I have tried again to reinstall the drivers using rootjunkies file but again without success. I tried doing it using that method as I remember trying to do it that way (what felt like a billion times) though I don't remember if I finally ended up succeeding with that method or another.
I followed your link "http://forum.xda-developers.com/showpost.php?p=63635664&postcount=9" and tried the 1st method
"[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by Snoop05"
running the "adb-setup-1.4.3.exe" I get "0 files copied" after selecting "Yes to install ADB system-wide" which I recall was the problem (zero files copied) that I had previously.
Openning Device Manager after this does show any Fire or Android devices even when the tablet is connected so I'm assuming that the adb driver installation is failing.
I tried again with "adb-setup-1.3.exe". This time I had 4 files copied and got fire listed in the device manager but when I tried to update the driver I am not given the Android option in the list when I select the option to install driver.
I googled to see if anyone else had this error and I found that some peoplehad difficulties installing on XP but seems that MTP not being supported is the reason and it is resolved by installing WMP v10 and above. I have v11 so presume that's not the problem.
I don't have access to another computer at the moment to try and install the adb drivers but should be able to use another one tomorrow. Last time when I got the drivers to install it was on a vista machine so I wondered if that might have something to do with it.
The other thing that occurred to me was maybe there is something wrong with the cable as I only get the fire shown in the device manager for a few moments before it refreshes and then the fire is no longer shown.
I wondered if I should try to use USBDeview (as per http://www.inlovewithandroid.com/android-usb-connection-problems.html) to see if that is the problem. Certainly if I can the drivers installed on another pc it might suggest that there's a problem with mine.
Anyway, if I get the adb drivers to install successfully on another pc, could you explain what I am trying to do by "booted into twrp by fastboot"? Sorry to be so useless!
Huge thanks
Yeah the files needed will all be pretty hefty. So if thinking about going to a custom rom this would be a good time. Though wouldn't download one or the stock until you've seen if you can use it.
1. Yeah I did mean choose that option on that menu you have onscreen. Doesn't need to be attached to go to the screen technically, but won't be able to do anything there until it is connected so no benefit in not waiting until you are. No doesn't need to be rooted. You'd expect it to go to an almost blank screen with =>FASTBOOT mode.... on it in landscape.
2. On plus side you wouldn't need the adb drivers... But the fastboot ones are probably similarly tricky. These ones worked for me https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
Though I've not used XP.
If it will fastboot into twrp then you can put the original stock rom on or either of the custom ones from there, so it's not dead and can get to downloading. (or 5.1.1 stock using the safe twrp method)
Did you use a different cable on the machine you got it to work on then? If not probably not the cable.
Pond-life said:
Yeah the files needed will all be pretty hefty. So if thinking about going to a custom rom this would be a good time. Though wouldn't download one or the stock until you've seen if you can use it.
1. Yeah I did mean choose that option on that menu you have onscreen. Doesn't need to be attached to go to the screen technically, but won't be able to do anything there until it is connected so no benefit in not waiting until you are. No doesn't need to be rooted. You'd expect it to go to an almost blank screen with =>FASTBOOT mode.... on it in landscape.
2. On plus side you wouldn't need the adb drivers... But the fastboot ones are probably similarly tricky. These ones worked for me https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
Though I've not used XP.
If it will fastboot into twrp then you can put the original stock rom on or either of the custom ones from there, so it's not dead and can get to downloading. (or 5.1.1 stock using the safe twrp method)
Did you use a different cable on the machine you got it to work on then? If not probably not the cable.
Click to expand...
Click to collapse
Thanks for all your help Pond Life.
I had such difficulties get the files to download that in the end I gave up and rang Amazon and they offered to send me a replacement.
Sorry to bail out, this is all new to me and most of what everyone has said has me completely baffled so I've decided to take the easy way out.
Thank you again - I really appreciated all your advice.
FrankieChen said:
Thanks for all your help Pond Life.
I had such difficulties get the files to download that in the end I gave up and rang Amazon and they offered to send me a replacement.
Sorry to bail out, this is all new to me and most of what everyone has said has me completely baffled so I've decided to take the easy way out.
Thank you again - I really appreciated all your advice.
Click to expand...
Click to collapse
Better luck with the new one