Hi all! I'm hoping I can get some help. I have a Kindle Fire HD 8.9 "Jem". I successfully rooted it the other day, and after switching laptops, finally was able to access fastboot on the computer and get the successful output. I followed the directions from this link:http://forum.xda-developers.com/showthread.php?t=2277105. I got all the way through it successfully to the end of step 3 to reboot into TWRP. However, once I rebooted, I get a constant bootloop on the static Kindle Fire logo. No twrp (I put 2.7.0.0 on there, and checked to revert to 8.1.4, but based on what I have read, I MAY have forgot to check the box to load stack).
I found SRT tool from this link: http://forum.xda-developers.com/showthread.php?t=2011126 and used it to successfully get the Kindle to show fastboot on the screen. However, now I'm at a loss as how to continue. I made backups per the 2ndBL+Twrp thread but I have no idea how to proceed. Any assistance on how to proceed would be greatly appreciated. I'm not very proficient in using the commands, but can follow the directions pretty well (or so I thought lol).
Thanks again for any guidance.
Ok I got it back. I figured out I needed to open up a new command prompt in order to enter the fastboot flash commands and flash my backups on to it that I made following http://forum.xda-developers.com/showthread.php?t=2128175. Now going to try this again and hope to get TWRP and CM working on it this time around.
UPDATE:
Okay, I'm now further than I have ever gotten before. I have successfully installed TWRP version 2.7.0.0, able to access it no problem. I installed CM11; I have tried both CM11 20140702-NIGHTLY-jem and CM11 20140504-SNAPSHOT-M6-jem. Before installing each one, I wiped system, cache and dalvik cache.
However, with each one, this is the problem I'm having. I am stuck at the cynogenmod boot screen (blue alien/android with the arrow circling). I have not been able to get past this. Is there any guidance that you all can offer me to get past this? When I saw that cynogenmod bootscreen pop up, I was so excited and relieved that I got past the blue kindlefire logo this time around, but am again deflated. I know I can boot back to rooted stock from my recovery files so it's not a total loss. I just so want to see it load up as android!!!
Thanks in advance...hope someone sees this. I didn't want to add another topic to the board, so the title doesn't reflect my current issue. So I hope that it'll get some answers. If I should make a new topic, please let me know. As my post count reflects, I am a newbie here. Thanks so much for all the hard work that you all do to help us!
Success!
Just wanted to update!
After wiping cache/dalvik cache/system and then wiping factory reset, and then reinstalling CM11 M6, it finally worked! SO now my kindle hd is now a beautiful full fledged android! I just want to thank all of the people here with all of their knowledge and guides, answers to questions in the threads...I finally figured it out and feel accomplished! LOL.
Maybe you can give me a hand as you've recently gone through this:
tried the 2nd bootloader instructions and the '8.9 Flasher' zip found on these forums, but right now I'm just stuck at the kindle fire logo (not moving). I can get into fast boot, but don't know what to put in there to get me either back to stock, or into CM11.
I (like a fool) didn't make a backup (i used the flasher zip first, and neglected the backup option), so are there stock images out there I can use?
dopepope said:
Maybe you can give me a hand as you've recently gone through this:
tried the 2nd bootloader instructions and the '8.9 Flasher' zip found on these forums, but right now I'm just stuck at the kindle fire logo (not moving). I can get into fast boot, but don't know what to put in there to get me either back to stock, or into CM11.
I (like a fool) didn't make a backup (i used the flasher zip first, and neglected the backup option), so are there stock images out there I can use?
Click to expand...
Click to collapse
When you restart your tablet do you see the blue KF splash screen? If you can you should be able to sideload a ROM onto TWRP.
If you can't get into TWRP then see this restore tool http://forum.xda-developers.com/showthread.php?t=2011126 you can flash the images manual from the tool if you'd rather not run the bat. Choose option 3 if you do as that includes the recovery as well.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
When you restart your tablet do you see the blue KF splash screen? If you can you should be able to sideload a ROM onto TWRP.
If you can't get into TWRP then see this restore tool http://forum.xda-developers.com/showthread.php?t=2011126 you can flash the images manual from the tool if you'd rather not run the bat. Choose option 3 if you do as that includes the recovery as well.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
thanks for your reply
im still in the process of fixing everything, but I was able to move past where I was (stuck on static kindle fire logo) by using fastboot to push the stock boot.img, recovery.img from hashcodes post, and then using the system.img from onemeila's rescue post (also wiping the cache)
im still in the process because my KF did an OTA update (!>@#) while I was pushing other files to it, so I had to start over again.
dopepope said:
thanks for your reply
im still in the process of fixing everything, but I was able to move past where I was (stuck on static kindle fire logo) by using fastboot to push the stock boot.img, recovery.img from hashcodes post, and then using the system.img from onemeila's rescue post (also wiping the cache)
im still in the process because my KF did an OTA update (!>@#) while I was pushing other files to it, so I had to start over again.
Click to expand...
Click to collapse
As soon as it boots into the OS, put it in airplane mode or kill your modem if nothing else.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Related
I flashed cm10.1 and latest gapps after rooting with kfu and going to twrp to flash zips. After rebooting the kindle stays on the rotating CM splash screen. Is there anything I can do to revive my kindle. I can't get my PC to recognize it and I can't get to recovery. I have the correct drivers installed bc i used the kfu only a few hours ago. Any help would be greatly appreciated
Sent from my Galaxy Nexus using xda premium
stewtang said:
I flashed cm10.1 and latest gapps after rooting with kfu and going to twrp to flash zips. After rebooting the kindle stays on the rotating CM splash screen. Is there anything I can do to revive my kindle. I can't get my PC to recognize it and I can't get to recovery. I have the correct drivers installed bc i used the kfu only a few hours ago. Any help would be greatly appreciated
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
When you plug in the usb to the computer do you get any change in windows device manager? like an unrecognized kindle fire (yellow triangle) under usb or similar?
stewtang said:
I flashed cm10.1 and latest gapps after rooting with kfu and going to twrp to flash zips. After rebooting the kindle stays on the rotating CM splash screen. Is there anything I can do to revive my kindle. I can't get my PC to recognize it and I can't get to recovery. I have the correct drivers installed bc i used the kfu only a few hours ago. Any help would be greatly appreciated
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Looks like you might need to reflash. Don't forget to do a wipe/factory reset...
seecay said:
Looks like you might need to reflash. Don't forget to do a wipe/factory reset...
Click to expand...
Click to collapse
I can't get to recovery and my pc doesn't recognize the kindle, so I can't reflash
Sent from my Galaxy Nexus using xda premium
stewtang said:
I can't get to recovery and my pc doesn't recognize the kindle, so I can't reflash
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
That's a strange problem. Have you tried to reinstall the drivers or use a different PC? If it can get into the boot animation, you should theoretically be able to get into recovery/TWRP... Sounds like a bad flash may have happened so try a newer/older build. I hope it goes ok...
Use this to replace the the one in kfu driver folder http://db.tt/vXXeuL10 and rerun the driver bat, that will get adb going again. Try reboot recovery to enter recovery or use kfu to set your bootmode to recovery. Bootloader? fff will take you to recovery as well.
Thepooch said:
Use this to replace the the one in kfu driver folder http://db.tt/vXXeuL10 and rerun the driver bat, that will get adb going again. Try reboot recovery to enter recovery or use kfu to set your bootmode to recovery. Bootloader? fff will take you to recovery as well.
Click to expand...
Click to collapse
I replaced the file and still shows ADB status as offline and boot status as unknown. The computer makes the noise that a device is connected once the kindle reaches the CM screen but the that is it, ADB is still offline. Also, the kindle fire logo at start up is no longer blue, it has reverted to the stock orange color.
stewtang said:
I flashed cm10.1 and latest gapps after rooting with kfu and going to twrp to flash zips. After rebooting the kindle stays on the rotating CM splash screen. Is there anything I can do to revive my kindle. I can't get my PC to recognize it and I can't get to recovery. I have the correct drivers installed bc i used the kfu only a few hours ago. Any help would be greatly appreciated
Click to expand...
Click to collapse
I have the same problem with CM 10.1 with the splash screen. It loads through FFF 1.4 and gets to the spinning splash screen which appears to be half off the screen and just sticks there. I used the 0102 version of the JB 4.2.1 CM10.1 SGT7 rom by twapriv. When I flashed it using TWRP 2.2.2.1 it said "successful". I try to install the 121212 Gapps zip and it wouldn't work, saying unable to unzip. However, after a reboot the splash screen does what I just mentioned.
It appears we aren't the only ones though (http://forum.xda-developers.com/showthread.php?t=2051331&page=24) according to stewtang's post. I guess I'll retry to flash an older version and see if that works. Anyone have this problem and found a fix for it?
Hah! OMG I so totally didn't realize that stewtang was the OP, LAWLEROFLCOPTEROMGWTFML...
guruizzy said:
I have the same problem with CM 10.1 with the splash screen. It loads through FFF 1.4 and gets to the spinning splash screen which appears to be half off the screen and just sticks there. I used the 0102 version of the JB 4.2.1 CM10.1 SGT7 rom by twapriv. When I flashed it using TWRP 2.2.2.1 it said "successful". I try to install the 121212 Gapps zip and it wouldn't work, saying unable to unzip. However, after a reboot the splash screen does what I just mentioned.
It appears we aren't the only ones though (http://forum.xda-developers.com/showthread.php?t=2051331&page=24) according to stewtang's post. I guess I'll retry to flash an older version and see if that works. Anyone have this problem and found a fix for it?
Hah! OMG I so totally didn't realize that stewtang was the OP, LAWLEROFLCOPTEROMGWTFML...
Click to expand...
Click to collapse
Any luck getting into recovery? If so, how did you do it?
stewtang said:
Any luck getting into recovery? If so, how did you do it?
Click to expand...
Click to collapse
I have always been able to get into recovery. However, I did find that my /system/bin/sh file and all other system files are completely missing. I have yet to fix this, as this could be some of my problems. I don't know I'm still a noob at this. I have reflashed TWRP 2.2.2.1 while in fastboot mode using a factory cable. I just bought one for $6 on ebay from a US seller. Using this cable I find that the KFU works more like it should. It actually tells what boot mode status is currently instead of just saying unknown.
I know I did something wrong or out of order when I tried to root my KF because it is very difficult to do an ADB PUSH command successfully. It takes a few reboots and then a trial and error until it works right. As for the latest 0102 update for CM10.1 and SGT7, I haven't been able to get passed the cyanogen splash screen.
I would like to know if that update includes all the files necessary to run JB 4.2.1 or is it a completely different OS altogether? Again, uber noob here.
guruizzy said:
I know I did something wrong or out of order when I tried to root my KF because it is very difficult to do an ADB PUSH command successfully. It takes a few reboots and then a trial and error until it works right. As for the latest 0102 update for CM10.1 and SGT7, I haven't been able to get passed the cyanogen splash screen.
I would like to know if that update includes all the files necessary to run JB 4.2.1 or is it a completely different OS altogether?
Click to expand...
Click to collapse
So a question for both of you. Did you do a clean install (wipe everything but SD card)? Also does it hang on the CM screen or does it endlessly reboot? Did either of you have previous ROMs installed?
When I installed CM10.1 on my friend's kf, at first that happened. I don't know what happened, but it took me a couple tries before it worked. Try redownloading the ROM and Gapps, and remember to wipe everything beforehand, and wiping cache before flashing Gapps.
jma9454 said:
So a question for both of you. Did you do a clean install (wipe everything but SD card)? Also does it hang on the CM screen or does it endlessly reboot? Did either of you have previous ROMs installed?
When I installed CM10.1 on my friend's kf, at first that happened. I don't know what happened, but it took me a couple tries before it worked. Try redownloading the ROM and Gapps, and remember to wipe everything beforehand, and wiping cache before flashing Gapps.
Click to expand...
Click to collapse
Yes. I performed a clean install and unfortunately I am unable to re-flash anything. When the kindle boots it endlessly stays on the cm splash screen and I can't enter recovery or use the kfu.
Sent from my Galaxy Nexus using xda premium
stewtang said:
Any luck getting into recovery? If so, how did you do it?
Click to expand...
Click to collapse
Looks like you may not have FFF so you probably can't get into TWRP... Have a look at this thread.
http://forum.xda-developers.com/showthread.php?t=1428428
stewtang said:
Yes. I performed a clean install and unfortunately I am unable to re-flash anything. When the kindle boots it endlessly stays on the cm splash screen and I can't enter recovery or use the kfu.
Click to expand...
Click to collapse
So for you, when you turn on from off, possibly from a hard force-restart, what do you see? The original orange kf logo? And it goes straight to the swirling cm logo?
jma9454 said:
So for you, when you turn on from off, possibly from a hard force-restart, what do you see? The original orange kf logo? And it goes straight to the swirling cm logo?
Click to expand...
Click to collapse
Yes that is what I see, but before I flashed it the kindle fire logo was blue.
Sent from my Galaxy Nexus using xda premium
I had the same thing happen to me when I flashed my kindle fire demo unit with CM10.1, it turned out to be some sort of an issue with the twrp recovery when I reflashed it with the cotr recovery that the kindle fire utility program also has as a alternate this worked just fine. I did notice that when I tried to use twrp to wipe my unit it didn't seem to fully wipe the unit. doing the same thing under cotr took longer.
The reason I think it was twrp is that no matter what version of CM10.1 I used be it a nightly or the M3 experimental build, it would still just show the distorted logo and never finish booting. this happened even after I wiped the /system and cleared cache and dalvik cache.
After I flashed cotr recovery I did the same thing again using the exact same zip files for CM10.1 and gapps and it worked this time.
I have a similar problem with you guys. My Kindle is showing the orange logo and then continues to the CyanogenMod animation where it loops infinitely. The logo is also off center, half of it is off the screen. I cannot enter the recovery mode in any way. KFU shows it as online but unknown boot status. ADB shows it as offline.
Any suggestions on how to fix it? Will I need a factory cable?
I'm in the same boat, tried soupkit in linux and no dice, windows recognize a device while the CM logo is looping but the kindle drivers or adb drivers do nothing.
andreasS2 said:
I have a similar problem with you guys. My Kindle is showing the orange logo and then continues to the CyanogenMod animation where it loops infinitely. The logo is also off center, half of it is off the screen. I cannot enter the recovery mode in any way. KFU shows it as online but unknown boot status. ADB shows it as offline.
Any suggestions on how to fix it? Will I need a factory cable?
Click to expand...
Click to collapse
yadspi said:
I'm in the same boat, tried soupkit in linux and no dice, windows recognize a device while the CM logo is looping but the kindle drivers or adb drivers do nothing.
Click to expand...
Click to collapse
In both of your cases, if you don't have FireFireFire installed which will allow you to access recovery with the power button, you need a factory cable. And remember to factory reset next time.
soupmagnet said:
In both of your cases, if you don't have FireFireFire installed which will allow you to access recovery with the power button, you need a factory cable. And remember to factory reset next time.
Click to expand...
Click to collapse
I did, I was going to sell it with CM10, I rebooted, did a factory reset, reinstalled cm.zip and gapps.zip and rebooted....lost firefirefire and stuck on CM logo. If I buy or make the factory cable, will it be easy to "revive"?
Edit: Saw it on eBay for $4.45 free shipping
Hey, I was stupid and tried to install a rom without factory-resetting my kindle. Now I am stuck at the splash logo boot loop. I tried the unbrick utility, but it can't find my kindle. I have access to fastboot commands, but not adb. Don't ask me why, I just can't use adb. I don't know how to restore my kindle to a working state. I have a fastboot cable available. Thanks in advance. Im a noob btw.:crying:
..
Kindle fire 2 bricked
Neeshers said:
I'm guessing it's looping from the kindle fire screen not the cm10.1 screen, correct? If so, you can use the command, "fastboot -i 0x1949 -w". That will wipe userdata and cache. But if it's looping without even loading the rom that's probably not going to fix it.
Click to expand...
Click to collapse
Ok, I am now not stuck on the splash logo. i reflashed the recovery and boot partitions and now it is trying to boot, but there is currently no os installed. Is this a good sign that I can fix it? I am in slc for the weekend and cant flash the system partition yet.
Another question. I tried installing twrp on my recovery, but i cant boot into it. it wont show the blue logo. do i need an os installed to use it?
Dill185 said:
Ok, I am now not stuck on the splash logo. i reflashed the recovery and boot partitions and now it is trying to boot, but there is currently no os installed. Is this a good sign that I can fix it? I am in slc for the weekend and cant flash the system partition yet.
Another question. I tried installing twrp on my recovery, but i cant boot into it. it wont show the blue logo. do i need an os installed to use it?
Click to expand...
Click to collapse
Yes. os MUST be installed for our recovery to function. Specifically a file called 'stack' has to reside on the system partition
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Kindle fire 2 bricked
mindmajick said:
Yes. os MUST be installed for our recovery to function. Specifically a file called 'stack' has to reside on the system partition
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Thanks a bunch. i restored the system partition last night, and it fixed. i plugged it in to charge, and this morning, it was back at the kindle fire logo. Did i do something wrong?
Doesn't sound like it.
Were you able to get it to boot back up?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
kindle fire 2 is bricked
mindmajick said:
Doesn't sound like it.
Were you able to get it to boot back up?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Ok, I figured out it was a OTA update that re-bricked it. I am downloading a custom rom right now. I finally got it to work! Thanks for all your help.:victory:
Kindle fire 2 cm10 help
Dill185 said:
Ok, I figured out it was a OTA update that re-bricked it. I am downloading a custom rom right now. I finally got it to work! Thanks for all your help.:victory:
Click to expand...
Click to collapse
Another question. I downloaded the CM10.1 zip shown here: http://forum.xda-developers.com/showthread.php?t=2100963
I try to flash it in twrp, but it keeps saying error flashing zip
What do I do?
Sounds like a bad download. Redownload and adb sideload from pc
--
Sent from my mind to your screen.
I've downloaded it like fifty times. I got a ROM I like though. I can finally use otg stuff. Thanks for all your help!
Sent from my Amazon Kindle Fire2 using xda app-developers app
i got similar problems. rooted it, but i got afterwards some problems with superuser applications. ran sveral rooting methods, but at some point, it stucked now with the orange "kindle fire" logo.
tried also to use different recoverys (kindle-fire-ultility2, KF2_SRT_10.2.3) but nothing helped. i cant reach the device anymore. adb says: no device in list and fastboot: <waiting for device>
actually i use the supplied cable. or am i wrong to use it for fastboot. thought the supplied one is similar to the special fastboot cables from e.g ebay
/edit: sry, just realized after reading the FAQs, that the factory cable is a different one. sorry.
Hi, I have an original KF that was running v6.3.2, I am trying to get it to run JB 4.2.
I successfully (I think) rooted it using SuperOneClick
I installed FFF and TWRP using KF Utilities
It can boot into TWRP
I try to flash Hashcode's 4.2.2_r1 and TWRP seems to complete although it does stick on "Updating partition details"
When I restart it it just goes to a screen covered in weird rotating triangles.Only thing I can do is hard shut down.
I did do backup and can restore it to original Amazon 6.3.2 KF firmware. Interestingly when I do this TWRP asks me to install SuperSU, which I do.I then boots as if its a new KF, except with SU app installed.
Can anyone give me any pointers as to where I might be going wrong?
Thanks
Gordon
Bad download/corrupted file?
Wait my reading caught up with me. You say it is still booting into stock? That doesn't sound like bad firmware download after all. Sorry... I don't know then! Someone else should have a thought.
I read it once again and realize you restored stock. Lol I go with my original suggestion. Redownload and reflash.
Sent from my GT-p511x
gordonj56 said:
Hi, I have an original KF that was running v6.3.2, I am trying to get it to run JB 4.2.
I successfully (I think) rooted it using SuperOneClick
I installed FFF and TWRP using KF Utilities
It can boot into TWRP
I try to flash Hashcode's 4.2.2_r1 and TWRP seems to complete although it does stick on "Updating partition details"
When I restart it it just goes to a screen covered in weird rotating triangles.Only thing I can do is hard shut down.
I did do backup and can restore it to original Amazon 6.3.2 KF firmware. Interestingly when I do this TWRP asks me to install SuperSU, which I do.I then boots as if its a new KF, except with SU app installed.
Can anyone give me any pointers as to where I might be going wrong?
Thanks
Gordon
Click to expand...
Click to collapse
The "weird rotating triangles" is the stock AOSP boot animation. 9 times out of 10, when your device gets stuck on the boot animation, it is from not wiping data in recovery before flashing the ROM. Boot into recovery, factory reset, then reboot to see if it fixes the problem.
Hi,
there are several threads on this forum dealing with nexus devices that get stuck at the google logo when booting up, however my case is a little different:
I can not even get into recovery.
Here's the symptoms:
The touchscreen became unresponsive. I read that fixing the cache partition helps and it did.
From time to time my device would get stuck at google logo on boot, but i was still able to get into recovery, wipe cache and it would work again. This happened 2-3 times over the course of the last 3 weeks maybe, so i thought its just some minor hangup
2 days ago the device became unresponsive again and i was unable to get into recovery. I have tried several times and once i was lucky to get into recovery (it showd google logo, but when i pressed the power button to turn it off i got into recovery)
now nothing will work. i can get into the bootloader no problem and fastboot is in a working condition
i have tried flashing the factory image using the files provided by google. So far no success
Does anyone know something else to try?
EDIT: aniket0317 suggested using Wugfresh's Root Toolkit which includes a script to unbrick in case of bootloops. That seems to have worked.
Flashing back to stock is a first step, to ensure it's nothing in the software. What do you mean by "So far no success"?
Use Wugfresh's Nexus Root Toolkit. There is a option named Stock Flash+Unroot (Bootloop). The device should be able to get into fastboot mode, though.
aniket0317 said:
Use Wugfresh's Nexus Root Toolkit.
Click to expand...
Click to collapse
This seems to have done it. I have followed the instructions in the toolkit and rebooted the device several times already successfully. The next days will tell whether the touchscreen freezes still happen. But for now, thank you.:good:
mistermabuse said:
This seems to have done it. I have followed the instructions in the toolkit and rebooted the device several times already successfully. The next days will tell whether the touchscreen freezes still happen. But for now, thank you.:good:
Click to expand...
Click to collapse
Press thanks if I helped you
Sent from my Nexus 7 using Tapatalk
Same problem
Hey,
my Nexus 7 2013 has the same error.
Im stuck in Google screen, only enter in fastboot mode.
Tried Nexus Root Toolkit and other methods but stays the same...
In TWRP, touchscreen doesnt work.
What can i do???
Thanks!
Hey thiago,
I don't really know what to do, but I have the same problem now...
I guess it should be possible to somehow boot clockworkmod recovery from fastboot,
but I'm not sure.
I'll mark this thread not solved again -.-
mistermabuse said:
Hi,
there are several threads on this forum dealing with nexus devices that get stuck at the google logo when booting up, however my case is a little different:
I can not even get into recovery.
Here's the symptoms:
The touchscreen became unresponsive. I read that fixing the cache partition helps and it did.
From time to time my device would get stuck at google logo on boot, but i was still able to get into recovery, wipe cache and it would work again. This happened 2-3 times over the course of the last 3 weeks maybe, so i thought its just some minor hangup
2 days ago the device became unresponsive again and i was unable to get into recovery. I have tried several times and once i was lucky to get into recovery (it showd google logo, but when i pressed the power button to turn it off i got into recovery)
now nothing will work. i can get into the bootloader no problem and fastboot is in a working condition
i have tried flashing the factory image using the files provided by google. So far no success
Does anyone know something else to try?
EDIT: aniket0317 suggested using Wugfresh's Root Toolkit which includes a script to unbrick in case of bootloops. That seems to have worked.
Click to expand...
Click to collapse
EDIT 2: Yes it worked, at first. Now the device is stuck in a bootloop again. I can boot into team win recovery, but touch doesn't work there so I can't do anything. Booting CWM from fastboot is also not suceessful.
What do you mean CWM is not successful, that there's no touch response? If all else fails, you can use the non-touch version of CWM, using the side buttons to navigate. But I'd be concerned if screen touches are not being recognized.
CWM dont start. Only twrp. Is there a TWRP non touch version?
There's no non-touch version of TWRP that I know of, since its design is based on touch.
What do you mean by CWM won't start? It just freezes? Did you flash the correct one?
6.0.4.3 for regular N7 2013: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.7-flo.img
6.0.4.8 for N7 2013 LTE: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.8-deb.img
6.0.4.3 for N7 2013 GSM: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.3-tilapia.img
still frozen
Pandae said:
There's no non-touch version of TWRP that I know of, since its design is based on touch.
What do you mean by CWM won't start? It just freezes? Did you flash the correct one?
[/url]
Click to expand...
Click to collapse
Yes, i used this version for Regular N7 2013, but still frozen in the google screen.
I have the same problem.
Stuck on google logo. It boots Fastboot only. It does not boot system or recovery.
What I have done so far:
Unlocked the bootloader
Flashed preview android L successfully But it did not boot. Then i Installed android 4.4.4. Successfully But still nothing. Then i flashed android 4.3 with the same result. Lastly i flashed TWRP to try and flash a zip, but again it does not go past the google logo. Everything i flash goes successfully or at least there are no errors on the logs. I have used wugs nexus toolkit to flash everything. I can see the bootloader version being changed after flashing different android versions, so i can confirm it is flashing bootloader at least.
My conclusion:
I think there is a hardware problem but I don't know how to troubleshoot what is wrong.
If anyone has any suggestion. It will be much appreciated.
Sent from my SM-G900F using XDA Premium HD app
Send it back to Google
gopin said:
I have the same problem.
Stuck on google logo. It boots Fastboot only. It does not boot system or recovery.
What I have done so far:
Unlocked the bootloader
Flashed preview android L successfully But it did not boot. Then i Installed android 4.4.4. Successfully But still nothing. Then i flashed android 4.3 with the same result. Lastly i flashed TWRP to try and flash a zip, but again it does not go past the google logo. Everything i flash goes successfully or at least there are no errors on the logs. I have used wugs nexus toolkit to flash everything. I can see the bootloader version being changed after flashing different android versions, so i can confirm it is flashing bootloader at least.
My conclusion:
I think there is a hardware problem but I don't know how to troubleshoot what is wrong.
If anyone has any suggestion. It will be much appreciated.
Click to expand...
Click to collapse
What if you flashed the stock factory recovery/ROM, or is that what you mean by 4.4.4 and 4.3? Don't use a recovery to flash the individual .img files, just run flash-all.bat and see what it does.
https://developers.google.com/android/nexus/images
Pandae said:
What if you flashed the stock factory recovery/ROM, or is that what you mean by 4.4.4 and 4.3? Don't use a recovery to flash the individual .img files, just run flash-all.bat and see what it does.
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Yes. I flashed the factory images using wugs nexus toolkit and ticked the option flash stuck + unroot (bricked or bootlooping) to see if it would work as mentioned by OP. All factory images flash successfully all partitions, but it does not boot recovery or system. I tried different android versions hoping it would make a difference and tried booting recovery after flashing each image (4.4.4 and 4.3). I haven't tried typing the command flash all.bat myself to flash the image as you suggested. I've used the toolkit to make it easier. I'll try flashing stock typing command flash all.bat myself and report.
Sent from my SM-G900F using XDA Premium HD app
Use your warranty, send it back to Google.
Ok so to start this was my first time roots and putting a custom os on an android device. It's a first gen kindle fire the firmware originally on it was 6.3.3. I rooted it using safe root with success. I then proceeded to install TWRP and that worked with out an issue. I basically followed lthis tutorial. I then booted into TWRP and cleared the cache then did a factory reset. I then install the newest version of CM 11 without issue then proceeded to install gaaps for it but it failed I figured it wouldn't matter (dumb thing to think). Then i rebooted it got stuck at the boot logo so i figured i messed up a step so I figured I'd just start from scratch just to be safe. I went back into TWRP and cleared all the caches and did a factory reset and installed the os from amazons website which i thought was the same firmware as before (6.3.3) but I later found out it was 6.2.1 and rebooted and got stuck at the boot logo again but this time there was no TWRP to boot into which is where I am stuck now. Windows picks it up as kindle in the device manager adb can pick it up too. I figured I'd try rooting it again all the commands it does fails because /system/bin/sh doesn't exist. Then it reboots and says something has deleted su looking for backup copy then says the back up is gone too and it can't recover. I then tried putting it into fastboot mode again with the commands and no luck it says /system/bin/sh doesn't exist so I can't do that. Im stumped now couldn't find anything through googling and searching the forums. Is my kindle bricked?
Think you need a fastboot cable
Sent from my XT907 using Tapatalk
sd_shadow said:
Think you need a fastboot cable
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
alright I was hoping I didn't have to. Is there any good places to buy it from other than ebay that ship to canada?
Edit: Nevermind I decided just to go to ebay. Thanks for the help.