[Q] another boot loop post.. - Kindle Fire Q&A, Help & Troubleshooting

Hey guys, before I begin, yes i read the '[HOW-TO] Before asking for troubleshooting help...' page as well as the '[GUIDE] Kindle Fire For Beginners' page, and am still in need of a bit of assistance due to my hilariously lacking knowledge of the workings of electronic equipment. :silly:
I just dug my kindle fire out of my dresser drawer where it has been sitting due to being 'bricked' for quite some time (stuck at the boot logo - white kindle text and orange fire text shimmering on a pure black background - holds a charge but is indefinitely at this screen). It is completely stock, having not downloaded or installed any ROMs or any other software, and initially began experiencing this problem the morning after running it out of battery while downloading a few books and games one night. I promptly plugged it in, went to bed, and woke up to it in this state that next morning.
I have tried downloading Kindle Fire Unbrick V1.1 by ZombiePiratez and running that to fix it, but it does not recognize my kindle fire. So, i downloaded Eclipse ADT with Android SDK for windows and followed some instructions i found for getting it to recognize my kindle as "Android Composite ADB Interface" in hopes that then the unbricking tool would recognize it and work its magic for me. But it didnt. I imagine this is because the process that I followed is flawed.
My question is, if i were to buy a "factory cable" would I be able to unbrick my kindle fire without having to do any of this command promp shamanism thats clearly over my head? Kinfauns states in his guide that "With a factory cable, unbricking just comes down to "plug it in and flash new stuff" in almost every bricking situation." But what does 'flash new stuff' mean; should I have picked that up from the guide as well? Or could I just use the factory cable in conjunction with ZombiePiratez unbricking tool to get back to the factory settings?
Thanks in advance for any pointers

See my How to flash twrp and firefirefire with a Fastboot cable
http://forum.xda-developers.com/showpost.php?p=53652317&postcount=2
Sent from my XT862 using Tapatalk

Hey @sd_shadow !
Thanks for the link to that, the videos you've created make it possible for even someone with my level of tech knowledge to work through this problem. Immensely better than trying to follow a written guide
Anyway, I finally got my fastboot cable and followed the steps in your videos to the tee, however I'm still encountering one small problem. When I get to the point where I'm installing update-kindle-prerooted.6.3.3.v1.zip in TWRP by swiping across the screen, it runs until it gets to the line thanking paulobrien and two others but then promptly freezes (or so i assume since it doesnt continue on and the loading bar halts in its tracks). I decided after a few tries to just hold the power button to get it to shut off and then booted the kindle in normal boot mode - and it worked! - despite not being able to complete the process as shown in your video. But this concerns me, as I do not have any of the additional apps shown in your video (not that this truly matters to me) and under settings -> device it shows that I am running version 6.3.1_user_#####. So I have two questions:
1) Did the fff and twrp processes work, but the 6.3.3 update fail thus enabling me to use my kindle as a v6.3.1 device again?
2) Will it harm my device in any way (e.g. re-bricking) if I just call it good and use it as it is now?
Thanks for all the help so far :highfive:

noobSaurus said:
Hey @sd_shadow !
Thanks for the link to that, the videos you've created make it possible for even someone with my level of tech knowledge to work through this problem. Immensely better than trying to follow a written guide
Anyway, I finally got my fastboot cable and followed the steps in your videos to the tee, however I'm still encountering one small problem. When I get to the point where I'm installing update-kindle-prerooted.6.3.3.v1.zip in TWRP by swiping across the screen, it runs until it gets to the line thanking paulobrien and two others but then promptly freezes (or so i assume since it doesnt continue on and the loading bar halts in its tracks). I decided after a few tries to just hold the power button to get it to shut off and then booted the kindle in normal boot mode - and it worked! - despite not being able to complete the process as shown in your video. But this concerns me, as I do not have any of the additional apps shown in your video (not that this truly matters to me) and under settings -> device it shows that I am running version 6.3.1_user_#####. So I have two questions:
1) Did the fff and twrp processes work, but the 6.3.3 update fail thus enabling me to use my kindle as a v6.3.1 device again?
2) Will it harm my device in any way (e.g. re-bricking) if I just call it good and use it as it is now?
Thanks for all the help so far :highfive:
Click to expand...
Click to collapse
1 yes installing TWRP and FFF reset boot, and allowed 6.3.1 to boot normally
2. the only problem should be that, when connected to wifi, update will redownload and try again once a day or so
Kindle will reboot to TWRP, but update should fail, if that does not bother you it is fine
3. what twrp version did you install? says in twrp if you are not sure

I installed TWRP v2.7.1.0-blaze because that is what you used in the video, even though i had read that 2.2.2.1 may be preferable for stock unrooted kindle fires. I did this so that I could follow your video exactly without having to change any steps except for switching otter to blaze in the cmd promt code I inputted.
Also, as I write this, Ive realized that I still may have made a mistake and installed one of the alternate test files for the 6.3.3 prerooted update and not the complete file itself, so ill get back with that info.

Yeah, i installed the alternate test file the first time :silly:
Went back through and followed your instructions to the 'tee' again and its up and running.
I do have one more question though; when I am using the device I dont get very far before selecting an application or making another command causes the screen to go black, only displaying the time and settings option at the top and the home button, back button, search button, etc at the bottom - none of which respond when selected. This happens with both the go launcher and the kindle launcher, and each time the only way I can stop it is resetting the device... Any suggestions to counteract this?

Related

[Q] Stuck on TWRP Screen

Ok, I am a nervous wreak! My 13 year old son borrowed my Kindle Fire and without my knowing, tried to root it. When I got it back and attempted to power it on, the yellow triangle with the fire symbol appeared. After waiting a few seconds, a black and gray screen with TWRP v2.0.0 appears.
He says that after he attempted the root and was unable to install the android market, he tried to do a restore under "device".
The Team Win Recovery Project (TWRP) screen that appears on the device has several options that I can choose from, including: Install, Backup, Restore, Wipe, Mount, Settings, Advanced, and Reboot. I am not familiar with what information you would need to help me get my device to boot back up.
If anyone can help me, I would greatly appreciate it.
Thank you so much in advance!
Kelly0247 said:
Ok, I am a nervous wreak! My 13 year old son borrowed my Kindle Fire and without my knowing, tried to root it. When I got it back and attempted to power it on, the yellow triangle with the fire symbol appeared. After waiting a few seconds, a black and gray screen with TWRP v2.0.0 appears.
He says that after he attempted the root and was unable to install the android market, he tried to do a restore under "device".
The Team Win Recovery Project (TWRP) screen that appears on the device has several options that I can choose from, including: Install, Backup, Restore, Wipe, Mount, Settings, Advanced, and Reboot. I am not familiar with what information you would need to help me get my device to boot back up.
If anyone can help me, I would greatly appreciate it.
Thank you so much in advance!
Click to expand...
Click to collapse
Don't panic... Start reading here...
http://forum.xda-developers.com/showthread.php?t=1552547
Familiarize yourself with the terminology so you know what steps you need to take. You'll eventually have to try resetting the bootmode to normal and restart the device. However, your OS may have been corrupted and you might not be able to boot back in to it. There's still no need to panic. You'll be able to get it working again. Just relax and follow along with the 1st post above. Look at the second post and just verify that your drivers are working right. Then you can try setting the bootmode back.
Kelly0247 said:
Ok, I am a nervous wreak! My 13 year old son borrowed my Kindle Fire and without my knowing, tried to root it.
Click to expand...
Click to collapse
Hey when this is all over, try to go easy on the kid. His adolescent brain is too underdeveloped to fully comprehend the consequences of his actions.
Sent from my Amazon Kindle Fire using xda premium
Oh my gosh, I am so ready to cry!!! All the information that I have read has really just confused me more. I asked my son what exactly he did and he told me he watched a video on youtube that required him to download the Kindle Fire Utility and install the drivers and root. He wasn't sure how to unroot it before he went into the device itself and "restore". I'm not sure if doing this caused the device to change the way it boots during restart, but I am at a lose. I am not familiar with how all this electronic software works and as sad as it may sound, I'm ready to just take away his allowance and just buy a new device.
Kelly0247 said:
Oh my gosh, I am so ready to cry!!! All the information that I have read has really just confused me more. I asked my son what exactly he did and he told me he watched a video on youtube that required him to download the Kindle Fire Utility and install the drivers and root. He wasn't sure how to unroot it before he went into the device itself and "restore". I'm not sure if doing this caused the device to change the way it boots during restart, but I am at a lose. I am not familiar with how all this electronic software works and as sad as it may sound, I'm ready to just take away his allowance and just buy a new device.
Click to expand...
Click to collapse
OK... you and your son sit down together and do the following...
1) Hook up your Kindle Fire to the computer and turn it on... let it boot to TWRP
2) Open the Kindle Fire Utility with the "run" file in the Kindle Fire Utility folder.
3) Near the bottom, it should say "ADB Status: Online"
4) Press the "1" key and hit ENTER
5) At the next menu, press the "1" key and hit ENTER
6) Wait and see if it will reboot
7) If it does not reboot on its own or it says "<waiting for device>" then press and hold the power button for 20-30 seconds until the device shuts off. Then press the power button again to turn it back on.
Hopefully, this will get the Kindle Fire to boot up again normally. Once you do that, you are going to have to try and reinstall the stock software (what your Kindle Fire came equipped with when you bought it), but that's probably letting the cart get ahead of the horse at the moment.
Let's see how the above works out first.
At step 3, the ADB Status says "Offline"
After trying to reboot normally, it sticks at <waiting for device>
Kelly0247 said:
At step 3, the ADB Status says "Offline"
Click to expand...
Click to collapse
Just go ahead and do what I said anyway... when it tells you "<waiting for device>" restart it using the button in TWRP or the power button like I indicated before.
Yes, I actually restarted the device and the Kindle Fire splash screen came up just as you posted the response. Will this remove the root from the device?
You have been so very patient with me. You are WONDERFUL!!!!!
Kelly0247 said:
Yes, I actually restarted the device and the Kindle Fire splash screen came up just as you posted the response. Will this remove the root from the device?
You have been so very patient with me. You are WONDERFUL!!!!!
Click to expand...
Click to collapse
All you've managed to do so far was to get the device to boot normally.
My guess is that your son never got far enough to actually root the device. However, he did get it to install a new bootloader (the part with the yellow triangle that comes up when you restart it) and a new recovery (TWRP). Right now, these things are harmless and you can leave it alone for the time being.
My suggestion to you would be to just keep using it as you would normally for now. If you can't get some of Amazon services to work or you have problems with it, come back and post another question about getting it back to stock. When the next Kindle Fire update comes along from Amazon, it will reinstall everything back to stock anyway (I'm mostly certain about this, but someone will correct me if I'm wrong).
And I agree with soupmagnet... don't be so hard on the kid about his little experiment.... no harm, no foul.
I've noticed now that I am unable to view any of the files on my device after connecting it to my PC. Is there any way to correct this or would it be too much of headache for me to attempt?
Thanks again for all the help you have given.
Oh, and I didn't harm my child, but he does know that he is not allowed to play around with my electronic devices anymore.
Kelly0247 said:
I've noticed now that I am unable to view any of the files on my device after connecting it to my PC. Is there any way to correct this or would it be too much of headache for me to attempt?
Thanks again for all the help you have given.
Oh, and I didn't harm my child, but he does know that he is not allowed to play around with my electronic devices anymore.
Click to expand...
Click to collapse
Something might have happened to your /sdcard (your storage space on the Kindle Fire) when your son was playing around with it. If you aren't too concerned about what's on there, you can just try formatting or erasing the contents of it. When you hook it up to your Windows machine, it might ask if you want to format it. In that case, it's very likely that you wouldn't be able to recover it even if you wanted, so I would just go ahead and format it. Another way to do this would be to reset the device to factory defaults. You would lose all installed apps, books, etc. and have to re-enter all your network and Amazon information afterwards, but the process will bring the /sdcard on the Kindle Fire to roughly the same as it was when you got it. You can find it in settings -> devices -> reset to factory defaults (this is from memory, so the wording might be slightly different). It all really depends on what you are willing to lose on the device. If you don't care... just erase it and start over.
Ok, i tried to reset the device to factory settings, but when it rebooted, it brought up the TWRP menu again. Any idea what else I can try?
I sent you a private message so you can get in touch with me for some live help if you need it.
Sent from my Amazon Kindle Fire using xda premium
Kelly0247 said:
Ok, i tried to reset the device to factory settings, but when it rebooted, it brought up the TWRP menu again. Any idea what else I can try?
Click to expand...
Click to collapse
If you haven't gotten things working yet...
If you are in TWRP, try the WIPE -> SD Card option to get your storage space reformatted. You can then use the MOUNT button in TWRP and it should show up on your Windows desktop again.
Then to get rid of TWRP altogether, you can download the software update from Amazon...
http://www.amazon.com/gp/help/customer/display.html/ref=hp_k6_updatesi?nodeId=200790620
Rather than follow the instructions on that page, rename the downloaded file to "update.zip" (without the quotes). You'll get a warning about file extensions... it's OK to change the name anyway. The file icon will change to a zippered folder after this. Copy the update.zip file over to your Kindle Fire.
Back in TWRP, hit the INSTALL button. Over in the right panel, you should see the update.zip file you transferred to the Kindle Fire. Touch that file name and you'll be able to continue installing that file onto your Kindle Fire. When it's done, you can reboot from the home menu.
It will take a few minutes for it to boot up for the first time, but when it's done, you should have a fresh, completely stock sytem and you'll be rid of TWRP.
This is an update to let you know that my Kindle is now back in perfect condition. Kinfauns, thank you so much for all the information and the attempts to help me fix this problem. Unfortunately, I needed more indepth help and wasn't able to correct my issues with the steps given.
Soupmagnet: Thank you, thank you, thank you, from the bottom of my heart for the many hours of trial and error that you spent helping me repair my device. Your patience with me was beyond belief and I will never be able to thank you enough!
You are totally AWESOME!!!!!
Please help.
I am also stuck on the TWRP screen.
When I:
1) Hook up my Kindle Fire to the computer and turn it on...let it boot to TWRP
2) Open the Kindle Fire Utility with the "run" file in the KFU folder
3) It registers "ADB Status: Online"
4) When I hit "1" for Normal it states:
"The system cannot find the drive specified.
The system cannot find the path specified.
"
"
"
"
What is the drive specified it is referring to?
Thank you.
KeaDe135 said:
Please help.
I am also stuck on the TWRP screen.
When I:
1) Hook up my Kindle Fire to the computer and turn it on...let it boot to TWRP
2) Open the Kindle Fire Utility with the "run" file in the KFU folder
3) It registers "ADB Status: Online"
4) When I hit "1" for Normal it states:
"The system cannot find the drive specified.
The system cannot find the path specified.
"
"
"
"
What is the drive specified it is referring to?
Thank you.
Click to expand...
Click to collapse
I *guess* it refers to the external Sd Card, since I got the same error.
In your case, since Adb status is online then just open a Terminal Emulator (cmd.exe in case of Windows) and change directoy to the tools folder inside Kfu, and run the command
adb shell idme bootmode 4000
Gửi từ Kindle Lửa của tôi qua Tapatalk 2
Same Issue except I want to finish rooting it
I'm running Kindle Fire 6.3.1
I ran Kindle Fire Utility v0.9.6 and hit option 2, install permanent root with superuser.
The process went smoothly until i ran into this
/sbin/sh;idme:not found 808 kb/s (22364 bytes in 0.027s)
attempt to remove root check
please wait..
and it got stuck there (no screenshots...sorry)
At that time, my KF had rebooted with blue fire, then it loaded TWRP v2.20
Apparently the instructions I initially followed was for KFU v0.9.4 and I've been searching for 2 hours on what the next steps are.
I restarted my laptop (Sony VAIO VPCEA46F) and my KF through TWRP 'reboot' --->'power off'
I plugged in my KF and ran KFU now it says
ADB Status: Online
Boot Status: Unkown
And now I am stuck in TWRP Recovery with my thumb up my ass..
I know, I know... I'm a fool for not checking things before starting this process. I appreciate any help and I'll accept any and all insults.
Thanks!
Yiz
Yizzie09 said:
I'm running Kindle Fire 6.3.1
I ran Kindle Fire Utility v0.9.6 and hit option 2, install permanent root with superuser.
The process went smoothly until i ran into this
/sbin/sh;idme:not found 808 kb/s (22364 bytes in 0.027s)
attempt to remove root check
please wait..
...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=31183986#post31183986
kinfauns said:
http://forum.xda-developers.com/showthread.php?p=31183986#post31183986
Click to expand...
Click to collapse
Thanks, that helped. Ultimately my KF is rooted.

[Q] Kindle Fire HD 8.9 - 8.4.6 - stuck on blue logo, or fastboot screen.

Hello, sorry for my bad english.
Im a noob and have been looking and trying different things for days now and can't fix my KFHD8.9", I would greatly appreciate any help. Sorry if this have been asked, but ive tried everything and nothing seems to work or match the same problems.
I rooted my kindle fire hd 8.9" (8.4.6) and tried to install the 2nd bootloader + twrp (to eventually install CM10.2) using this guide (http://forum.xda-developers.com/showthread.php?t=2277105), but stupidly, I didn't back up on step 2. I attempted to flash the bootloader using fireflash and, as long as I could make it I did everything that was needed. I rebooted and pushed the volume up while booting, and it went to the blue logo and then into fastboot screen and then stoped there.
My pc (Windows 8) didn't recognized the device while in the fastboot screen as a kindle but as a portable device called "jem-PVT-prod-04"
I rebooted my KFHD pressing power button, and when starting again, I saw the orange logo, then the blue logo and it just got stuck there.
So now I just can get to the fastboot screen (by pressing volume up while its booting) or get stuck in the blue kindle fire logo if i dont press anything.
I would like to add also that while on the fastboot screen , My PC wont communicate with my device. I have the Android SDK installed and could use ADB before this happened.
I have tried the commands -i 0x1949 getvar product and -i 0x1945 reboot as suggested on many posts, but both of them stays in "waiting for device" for ever.
Then i tried using Kindle Fire First Aide as suggested on other posts but after downloading everything it gave me an error about something not matching with my device and what i was trying to do.
In top of that, somewhere I got the impression that I just got stuck in the middle of the procedure and that I could still install TWRP or flash a rom,
So now I don't know if my device is bricked, or stuck in the middle of the procedure or what, but if anyone could help me get back to the stock firmware or to twrp or something other than this two screens (blue logo or fastboot screen) it would be spectacular
thanx in advance.
I'm having the same exact issue more or less, but I can't pass the orange Kindle logo. My computer will recognize the Kindle for about all of 2 seconds, but only as Jem_.... then disconnects so I can't enter fastboot or move forward at all. I'm hoping that someone can help with this.
You have to install the driver for the jem device with the drivers in my signature before fastboot commands will work. Try holding volume down instead of up, it should go into recovery instead of fastboot if I remember right.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Recd msg alert stunts513 to the error while using wallpaper fix 2.1
I am having a terrible time with this Kindle HD 2nd generation table I tried to root. I was following this guys post on You tube and got it rooted but something when wrong when I tried installing the 2nd bootloader and twrp. I ended up stuck with a blue kindle logo. I tried turning it on with the volume button pushed to the left and it went from orange to blue and then to the twrp recovery menu. That was a few days ago, Its been stuck in that mode ever since, there are no back up folders and I think was making the problem worse, as it seems I could do the adb push and now I cant, well at least i couldnt before running your wallpaper fix 2.1 I ran it once and it wouldnt take I dont remember the error, but my table was at the blue logo screen. I remembered reading about running something while you powered the device on because there was an few seconds of access to something, I cant remember so I tried that and unknown to me It appears from these notes i found that I suscessfully installed it - then tried again -then something about the backup??? I am going to cut and paste it here and not do a thing until I hear from you, as I dont want to mess it up. I didnt know the fix worked cause i was watching the command screen and not the side of the file where i have your tool on my desktop.
Here is everything from that run. in the attached file
OK so lemme get this straight, you are stuck in twrp without adb access? Also I will have to double check on my PC but when I download that file its not a PDF but a text file and its HTML with a 404 error message in it when I view it on my kindle.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
OK so lemme get this straight, you are stuck in twrp without adb access? Also I will have to double check on my PC but when I download that file its not a PDF but a text file and its HTML with a 404 error message in it when I view it on my kindle.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yes somehow I have twrp and I think when I first got into the bootloop I had adb access but in fumbling around trying to fix it I lost adb access.
If I turn the kindle off, and then push power and do nothing it powers up with the yellow logo and in 4 seconds that log turns blue and it stays that way until i turn it off. In this state checking device manager it shows the device as an android phone, Android ADB interface. If I unplug the device the device manager no longer shows it - If I power up the device and while the logo is still yellow push the volume button to the left it boots to twrp
I re did the notes in a new pdf file I hope you can access them now. I tried looking at them from my post on my pc and got that same access code error. I cant win on this thing tonight,
Thanks for getting back to me so quickly
John
The tutorial at: http://forum.xda-developers.com/showthread.php?t=2277105 tells you, in step 4, to place a custom ROM on the Kindle before you reboot into twrp. You then install that from from within twrp and then you get past the blue logo. If you didn't put the custom ROM on your kindle and adb isn't working then you need to install the abd drivers from stunts513's forum signature then do the twrp adb sideload.
Relevant sections from the tutorial:
Once you have the .zip files for the ROMs with GApps (Google apps, like Play Store), place them on the sdcard, and turn off the device. Turn it on, hold Volume-Up before the logo turns blue, and enter TWRP. Once there, immediately do two things: make a backup, and after that, wipes: system, factory reset, cache, and Dalvik cache. After these two things are done, go ahead and flash the .zip file, and wait for it to finish. After it finishes, go ahead and again, wipe cache and Dalvik cache, then reboot. After you rebooted, wait 5 minutes, then reboot again, and you're all done!
Click to expand...
Click to collapse
6. Wiped /sdcard, can't reboot from recovery: You thought you had the ROM file on the sdcard, but you didn't, and wiped everything, so without a ROM image, you can't boot into system.
Solution: Put the ROM file where your ADB binary is (usually inside platform-tools folder in Android SDK directory) and rename it rom.zip. On the device, boot into TWRP, select Advanced, then ADB Sideload. Connect device to PC. From here, run "adb" and hit Enter to check for your binary version, if it's anything lower than 1.0.3.0, you need to update the binaries by re-installing the latest Android SDK. Once the device is in sideloading mode and is connected to the PC, type "adb sideload rom.zip" and hit Enter. Now you'll find the ROM on the sdcard, flash, and you're done.
Click to expand...
Click to collapse
Hope this helps... someone.
pitcrawler said:
The tutorial at: http://forum.xda-developers.com/showthread.php?t=2277105 tells you, in step 4, to place a custom ROM on the Kindle before you reboot into twrp. You then install that from from within twrp and then you get past the blue logo. If you didn't put the custom ROM on your kindle and adb isn't working then you need to install the abd drivers from stunts513's forum signature then do the twrp adb sideload.
Relevant sections from the tutorial:
Hope this helps... someone.
Click to expand...
Click to collapse
Your post fixed my bricked tablet, THANK YOU SO MUCH. There is so much info that its confusing for a noob like me - I followed the directions you posted and I am in. thank you, thank you, thank you
Jdoki said:
Your post fixed my bricked tablet, THANK YOU SO MUCH. There is so much info that its confusing for a noob like me - I followed the directions you posted and I am in. thank you, thank you, thank you
Click to expand...
Click to collapse
Yeah, I know there's a lot of information. It took me a long time and a lot of research before I attempted it as a noob myself. An important thing is to follow the tutorials word for word and skip nothing, and cross your fingers.
Got fastboot comunication between PC and KFHD
stunts513 said:
You have to install the driver for the jem device with the drivers in my signature before fastboot commands will work. Try holding volume down instead of up, it should go into recovery instead of fastboot if I remember right.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanx a lot for the quick response! :good: I was finally able to install your great drivers. I had to be quick as you said in some other posts, because the pc only detects it for a little while, when the logo it's still orange on the kindle, I think. After that, and while on fastboot screen, my device manager would detect a Jem-something device, but could not install any drivers on it. So I had to install the drivers really fast while in the orange logo, oh, and had to disable the drivers signature check on windows 8 also.
Now I can use fastboot commands to reboot the kindle, but I can still only get to the blue logo or the fastboot screen.
I guess this means I now can use the kindle first aide to go back to stock and try again for the TWRP and 2nd bootloader. I'll post if I can't make my kindle boot normal again later.
Do you know if this was my kindle being bricked or was it something else?
Thanks a lot again, I was very worried that i wasn't getting anywhere. .:laugh:
Stuck on blue logo!
Hi!
I'm having a similar problem... I recently got a second hand Kindle 2nd Generation already rooted with Cyanogenmod 10.1.3.otter2 on it. Google Play and some other apps where having issues, so I decided to downgrade. After testing a couple of different ROMs, I got stuck on the blue logo, an infinite booting screen. Funny enough, I think the mistake was to install a Fire first generation ROM into a 2nd generation. Anyway, long story short, I've tried everything, Kindle First Aide (won't help because it seems that all the options need me to be in the desktop of the tablet and I can't get there), SDK ADB will see the device but return a device offline... I'm running out of options and don't really know what to do!
Any ideas guys??
EricMitjans said:
Hi!
I'm having a similar problem... I recently got a second hand Kindle 2nd Generation already rooted with Cyanogenmod 10.1.3.otter2 on it. Google Play and some other apps where having issues, so I decided to downgrade. After testing a couple of different ROMs, I got stuck on the blue logo, an infinite booting screen. Funny enough, I think the mistake was to install a Fire first generation ROM into a 2nd generation. Anyway, long story short, I've tried everything, Kindle First Aide (won't help because it seems that all the options need me to be in the desktop of the tablet and I can't get there), SDK ADB will see the device but return a device offline... I'm running out of options and don't really know what to do!
Any ideas guys??
Click to expand...
Click to collapse
You need to push a ROM onto TWRP. You should still be able to access TWRP. http://forum.xda-developers.com/showthread.php?t=2459498 be glad you did not hard brick it.

[Q] Accidentally deleted my kindle fire OS

Hi, i accidentally deleted everything, including my OS while trying to restore my kindle to its original state. Your help would be appreciated!
-its stuck in the KF logo (white and orange, meaning original bootloader)
-I cannot access TWRP
-when i try to use KFU, it says ADB status: online ; boot status : unknown
-when i try to install TWRP via KFU, it gets stuck in " waiting for device" ( i guess i cant go into fastboot mode)
-i'm not accessible to a factory cable because im not from the us
Help me please
Thank you!
I did something very similar.
june726 said:
Hi, i accidentally deleted everything, including my OS while trying to restore my kindle to its original state. Your help would be appreciated!
-its stuck in the KF logo (white and orange, meaning original bootloader)
-I cannot access TWRP
-when i try to use KFU, it says ADB status: online ; boot status : unknown
-when i try to install TWRP via KFU, it gets stuck in " waiting for device" ( i guess i cant go into fastboot mode)
-i'm not accessible to a factory cable because im not from the us
Help me please
Thank you!
Click to expand...
Click to collapse
I am having a similar issue like yours. Yesterday I tried downloading Jellybean onto my Kindle. I did all of the precautions, TWRP, KFU, etc.
And right as I thought I was done, boom, I get stuck in an infinite re boot. Every time it finally boots up it says android.process.phone for not even a full second and immediately reboots. I am not the smartest, but if someone could walk us through a way to restore our kindles or fix the problem. I would be most gracious! I am not sure what the ADB is as well. Is that what I am missing?
june726 said:
Hi, i accidentally deleted everything, including my OS while trying to restore my kindle to its original state. Your help would be appreciated!
-its stuck in the KF logo (white and orange, meaning original bootloader)
-I cannot access TWRP
-when i try to use KFU, it says ADB status: online ; boot status : unknown
-when i try to install TWRP via KFU, it gets stuck in " waiting for device" ( i guess i cant go into fastboot mode)
-i'm not accessible to a factory cable because im not from the us
Help me please
Thank you!
Click to expand...
Click to collapse
Have you guys checked this out???
http://forum.xda-developers.com/showthread.php?t=1428428
lj50036 said:
Have you guys checked this out???
http://forum.xda-developers.com/showthread.php?t=1428428
Click to expand...
Click to collapse
Yes, i've tried downloading that. But i can't seem to run it correctly. When i open it, it just opens a command promt and then closes immediately.
SDK
june726 said:
Yes, i've tried downloading that. But i can't seem to run it correctly. When i open it, it just opens a command promt and then closes immediately.
Click to expand...
Click to collapse
OK well go get this for your PC make sure you get the one for your os....make sure you get the zip not the exe.... It will be like a 400 to 500 meg dowload....
http://developer.android.com/sdk/index.html
Controverly areadvia
lj50036 said:
OK well go get this for your PC make sure you get the one for your os....make sure you get the zip not the exe.... It will be like a 400 to 500 meg
I downloaded the sdk and i can now use adb. But, my problem now is that i cannot copy the fbmode to my kindle via adb. When i push it to a location, it says that my kindle is read only. So without the fbmode, i cannot boot into fastboot, cannot install fff and twrp and no os again. what should i do now?
Click to expand...
Click to collapse
june726 said:
I downloaded the sdk and i can now use adb. But, my problem now is that i cannot copy the fbmode to my kindle via adb. When i push it to a location, it says that my kindle is read only. So without the fbmode, i cannot boot into fastboot, cannot install fff and twrp and no os again. what should i do now?
Click to expand...
Click to collapse
Ok.. Well than lets see here.....When can you use adb??? I need as much info as possible... What file are you moving..... Where are you trying to move it to... Copy and paste your commands and outputs this will make it much easier for me and anyone else that would like to help....Thx lj
Phil700 said:
I am having a similar issue like yours. Yesterday I tried downloading Jellybean onto my Kindle. I did all of the precautions, TWRP, KFU, etc.
And right as I thought I was done, boom, I get stuck in an infinite re boot. Every time it finally boots up it says android.process.phone for not even a full second and immediately reboots. I am not the smartest, but if someone could walk us through a way to restore our kindles or fix the problem. I would be most gracious! I am not sure what the ADB is as well. Is that what I am missing?
Click to expand...
Click to collapse
Well your problem is nowhere near the same as June's, but I'll go ahead and try to help your anyway. I've had this happen to me once or twice. My suggestion is to redownload your rom and gapps, and then try flagging them again. Hopefully that should work. There is an option in TWRP to mount your kindle on your computer.
Sent from my Nexus 7 using Tapatalk
So far.
Guys, sorry I might not have explained the issue in enough detail. Although the information is full of things that are helpful. It didn't quite help me.
Sorry about having to deal with a compete noob here...
---I'll list my issues to isolate confusion.---
-I cannot boot ADB, I click on it, a cmd window pops up and then immediately closes each time I proceed to open it. for a start, if someone could perhaps tell me what I am doing wrong, because I know I must not be doing what all of you pros are doing.
-Although I had TWRP installed on both my pc and kindle. Whenever I boot up my kindle, I do not get the blue and gray "Kindle Fire" logo before the Orange and White logo. So that for me was very frustrating.
-The Kindle Fire Utility is not detecting my device at all. Which is worrying me to death, the Kindle Fire Unbrick utlity is not working either which is killing me inside.
-For a detailed description of what my kindle fire does when I press the power button goes as so: I press the power button, the orange and white Kindle Fire logo pops up for a few seconds like normal, then it proceeds to boot or "Attenpt" to boot the Jellybean OS, after waiting 5 minutes, the OS lock screen pops up with "android.phone.com" or "phone.android.com" pops up, for a second, then it proceeds to fully rebooting the OS for another 5 minutes. It does it indefinitely.
So does this mean my kindle is officially done for? Bricked? Or is there still hope for me. This is really depressing, I spent most of my money on this, money is tight for me right now ant I use my kindle for school and research. It is a vital tool to me. I need all the help I can get.
Thanks for all of the help so far. You guys really know what you are doing, thanks!
System deleted Need Help !!!! Please
Recently I tried to install android in my Kindle Fire HDX 7 and I install a thing called FireFireFire I think to my kindle then It messed up everything, so I don't know what to do and I wiped all my data and even the Option called SYSTEM. after that I reboot my Kindle and all I have is KINDLE FIRE on the screen that's it. I can't use my Kindle at all ,and the computer won't let me install the driver all it told me is MTP USB device.and I tired to use all kind of tool to fix my kindle and CMD told me Can't Find Device. I m really not good at android so I really need someone help me !!!
Happyy said:
Recently I tried to install android in my Kindle Fire HDX 7 and I install a thing called FireFireFire I think to my kindle then It messed up everything, so I don't know what to do and I wiped all my data and even the Option called SYSTEM. after that I reboot my Kindle and all I have is KINDLE FIRE on the screen that's it. I can't use my Kindle at all ,and the computer won't let me install the driver all it told me is MTP USB device.and I tired to use all kind of tool to fix my kindle and CMD told me Can't Find Device. I m really not good at android so I really need someone help me !!!
Click to expand...
Click to collapse
Nothing here works for the HDX result=permabrick. All support for HDX is here http://forum.xda-developers.com/kindle-fire-hdx .
Phil700 said:
Guys, sorry I might not have explained the issue in enough detail. Although the information is full of things that are helpful. It didn't quite help me.
Sorry about having to deal with a compete noob here...
---I'll list my issues to isolate confusion.---
-I cannot boot ADB, I click on it, a cmd window pops up and then immediately closes each time I proceed to open it. for a start, if someone could perhaps tell me what I am doing wrong, because I know I must not be doing what all of you pros are doing.
-Although I had TWRP installed on both my pc and kindle. Whenever I boot up my kindle, I do not get the blue and gray "Kindle Fire" logo before the Orange and White logo. So that for me was very frustrating.
-The Kindle Fire Utility is not detecting my device at all. Which is worrying me to death, the Kindle Fire Unbrick utlity is not working either which is killing me inside.
-For a detailed description of what my kindle fire does when I press the power button goes as so: I press the power button, the orange and white Kindle Fire logo pops up for a few seconds like normal, then it proceeds to boot or "Attenpt" to boot the Jellybean OS, after waiting 5 minutes, the OS lock screen pops up with "android.phone.com" or "phone.android.com" pops up, for a second, then it proceeds to fully rebooting the OS for another 5 minutes. It does it indefinitely.
So does this mean my kindle is officially done for? Bricked? Or is there still hope for me. This is really depressing, I spent most of my money on this, money is tight for me right now ant I use my kindle for school and research. It is a vital tool to me. I need all the help I can get.
Thanks for all of the help so far. You guys really know what you are doing, thanks!
Click to expand...
Click to collapse
Hey Phil. Doesn't look like you've posted anything else, so you probably won't see this. But oh well... Sorry your problem got left in the dust. I didn't mean for that to happen. You need to shift + right click in the folder with adb.exe and click "open command window here" and then you can do your things. As far as everything else: does your computer do anything when you plug your kindle into it?
I accidentally did this once (at least I think it's the same) and what I did was I went into ADB and side loaded a custom ROM I used CM

Kindle Fire 8.9 Black Boot Scren

I have successfully rooted my smaller Kindle Fire HD. I tried to root my 8.9 Fire HD and now I'm stuck with what I think is brick.
I started off with this link.
http://rootkindlefire.com/kindle-fi...t-kindle-fire-hd-8-9-into-pure-android-tablet.
I worked great until I got to step 20 when the device rebooted and it ran super slow and the display was not right a visible line running through the display. No apps showed up and command took more than 20 seconds to register. Unable to fixed it at this point I did a factory reset and all was good. No line through the UI and response time was back to normal. I tried couple of more times to root it and each time was meet with the same result. I left it lay for a while but took it back up again after doing some more research. I finally settled on this root solution and it worked.
http://wiki.cyanogenmod.org/w/Install_CM_for_jem
It worked and I was able to boot into TWRP and check its various settings then a problem occurred when I tried to move files to the device. I got message unable to mount cache. After some poking around I notice the internal storage at 0. No space for to move any files from my computer to the device. Try as I might I wasn't able to copy anything to the device. So one final time I attempted to do a factory reset and this is where things went to hell. The device rebooted but I got neither the standard Orange fire logo or the blue TWRP loading Fire Logo, all I got was a truly black screen like all the pixels where dead and no back light. The Kindle no longer shows up as a Kindle in my Device manager and its name is actually something cryptic like 'Kolwr29'. I am able to assign it the Andriod ABA Device but it cycles in/out of the device manager like its being connected and disconnected from my laptop. I've read most of the links listed as suggested on this forum but the device doesn't respond to any Fastboot commands and any command I give continually says 'waiting for device.' I've tried to do this on both my laptop and desktop but the device exhibits the same behavior. I also in desperation ordered a Fastboot cable even though I was fairly certain from what I read that it wouldn't work my Fire 8.9. Nothing same problem.
I'm at lost. The device will not respond to any commands and think I truly have a brick on my hands. I'm at the point where I'm just going to pay to replace it than wash my hands of trying to root it. We'll just live with the crappy apps from the amazon store. Any help you guys can give me would be greatly appreciated.
I've read the following posts and gone through all the steps in them but to no avail.
http://forum.xda-developers.com/showthread.php?t=1552547
http://forum.xda-developers.com/showthread.php?t=1850192&page=2
http://forum.xda-developers.com/showthread.php?t=2010353
http://androidcowboy.com/2014/01/root-kindle-fire-hdx-8-9/

Bricked my Fire TV Stick 1?

Hi there!
I think I may have bricked my Fire TV Stick 1 (bought at launch in Germany)...
Current situation:
- stick turns on, shows white amazon logo on black background
- continuously rebooting; ~5s black screen, ~5s amazon logo
After months not having it used, I found out I may be able to root it by now. So I did research over the vast amount of threads and posts and was overwhelmed by the information... So I tried to get started but struggled to find the right steps and therefore maybe failed.
I updated it to 5.0.5 (stock) and tried King Root, then Kingo Root, which was a success.
I tried to use the TWRP 3.0.0-7 v2 zip and used the sh command from the respective thread (I thought that was it, since all my devices before used either TWRP or CWM).
To this point, all went through and I wanted to reboot into recovery, but there was only this generic (stock?) red text recovery screen. I waited to be sure, nothing happened and I unplugged it to reboot.
It booted fine and I reflashed the TWRP zip, in case I didn't do it properly. Again it did as expected.
I then pushed the latest prerooted 5.2.0.1 zip and rebooted to recovery, but again this generic screen, so I unplugged it early, I think.
From there on, I got stuck at the white amazon logo, see above.
I did not unlock the bootloader, adb shell confirmed it not being unlocked before.
During bootloops, I did not manage to get any control via adb or fastboot.
So, is it bricked once and for all? If not, how can I save it?
I don't care about anything stored on it.
I also have a Y-USB-OTG cable and connected a keyboard before, but could not interfere yet.
(If bricked, would a Teensy be of any use? I have one from CCast rooting days)
Thanks for reading and in advance.
I had same problem with my fire stick when used the USB power of my TV.
Did you try to power the fire stick TV with the power point and USB adapter?
l_aios said:
Hi there!
I think I may have bricked my Fire TV Stick 1 (bought at launch in Germany)...
Current situation:
- stick turns on, shows white amazon logo on black background
- continuously rebooting; ~5s black screen, ~5s amazon logo
After months not having it used, I found out I may be able to root it by now. So I did research over the vast amount of threads and posts and was overwhelmed by the information... So I tried to get started but struggled to find the right steps and therefore maybe failed.
I updated it to 5.0.5 (stock) and tried King Root, then Kingo Root, which was a success.
I tried to use the TWRP 3.0.0-7 v2 zip and used the sh command from the respective thread (I thought that was it, since all my devices before used either TWRP or CWM).
To this point, all went through and I wanted to reboot into recovery, but there was only this generic (stock?) red text recovery screen. I waited to be sure, nothing happened and I unplugged it to reboot.
It booted fine and I reflashed the TWRP zip, in case I didn't do it properly. Again it did as expected.
I then pushed the latest prerooted 5.2.0.1 zip and rebooted to recovery, but again this generic screen, so I unplugged it early, I think.
From there on, I got stuck at the white amazon logo, see above.
I did not unlock the bootloader, adb shell confirmed it not being unlocked before.
During bootloops, I did not manage to get any control via adb or fastboot.
So, is it bricked once and for all? If not, how can I save it?
I don't care about anything stored on it.
I also have a Y-USB-OTG cable and connected a keyboard before, but could not interfere yet.
(If bricked, would a Teensy be of any use? I have one from CCast rooting days)
Thanks for reading and in advance.
Click to expand...
Click to collapse
I guess you did not read enough.
At this point in time you can only root (kingoroot or kingroot) and replace root with SuperSu on a Firestick. TWRP (recovery) can not be installed because it was not released by rbox as of yet, that particular recovery\pre-rooted image is for firetv1 upgraded to OS5 and not for firestick.
Sorry man.
Have you tried to connect to a computer via USB and run kingoroot or kingroot for windows (whatever you used)? It is a small chance that will recover but it is a slim one....
mjnman said:
I had same problem with my fire stick when used the USB power of my TV.
Did you try to power the fire stick TV with the power point and USB adapter?
Click to expand...
Click to collapse
I could not remember, so I just retried it with two different chargers and two different cables (both used to power my Nexus 5).
Unfortunately resulting in the very same loop... But thanks nonetheless.
bula1ca said:
I guess you did not read enough.
At this point in time you can only root (kingoroot or kingroot) and replace root with SuperSu on a Firestick. TWRP (recovery) can not be installed because it was not released by rbox as of yet, that particular recovery\pre-rooted image is for firetv1 upgraded to OS5 and not for firestick.
Sorry man.
Have you tried to connect to a computer via USB and run kingoroot or kingroot for windows (whatever you used)? It is a small chance that will recover but it is a slim one....
Click to expand...
Click to collapse
Dang... Usually I don't make mistakes this dumb. Guess I learned my first lesson. I'll try to trace my mistake though, for future attempts.
I rooted it with the Kingo app, I think, and got that typical "stuck at 90%" and rebooted it like others did. It rebooted fine and Kingo verified it rooted.
I did not use Windows, I use Ubuntu, occasionally with Wine, yet I had no luck passing USB devices to it. (And always these missing libs...)
Normally, adb and fastboot (console) work fine (i.e. with my phone).
Now I have no chance to interfere with the bootloop, I think.
IIRC, sometimes I could spam commands and at one point adb was stuck at "waiting for device".
I tried to reproduce it just now, but could not get it again.
So, should I try adb or fastboot on another computer to be sure?
Would King(o) for Windows be of any help at this point? If so, what would be my best bet to catch it at some point I can recover it?
Is there any other way I could try? From my nooby perspective, could the bootsplash be an entrance for fastboot? Could it be just stuck trying to access erroneous partitions?
At this point I would try the most crazy and risky idea, since it is unusable anyway.
Thanks both of you for your answers.
l_aios said:
I could not remember, so I just retried it with two different chargers and two different cables (both used to power my Nexus 5).
Unfortunately resulting in the very same loop... But thanks nonetheless.
Dang... Usually I don't make mistakes this dumb. Guess I learned my first lesson. I'll try to trace my mistake though, for future attempts.
I rooted it with the Kingo app, I think, and got that typical "stuck at 90%" and rebooted it like others did. It rebooted fine and Kingo verified it rooted.
I did not use Windows, I use Ubuntu, occasionally with Wine, yet I had no luck passing USB devices to it. (And always these missing libs...)
Normally, adb and fastboot (console) work fine (i.e. with my phone).
Now I have no chance to interfere with the bootloop, I think.
IIRC, sometimes I could spam commands and at one point adb was stuck at "waiting for device".
I tried to reproduce it just now, but could not get it again.
So, should I try adb or fastboot on another computer to be sure?
Would King(o) for Windows be of any help at this point? If so, what would be my best bet to catch it at some point I can recover it?
Is there any other way I could try? From my nooby perspective, could the bootsplash be an entrance for fastboot? Could it be just stuck trying to access erroneous partitions?
At this point I would try the most crazy and risky idea, since it is unusable anyway.
Thanks both of you for your answers.
Click to expand...
Click to collapse
Do you still have root? Is your stick responding to the su command?
If so read this post: http://forum.xda-developers.com/fire-tv/help/guidance-recovering-bootloop-firetv-t3446902
If not:
Try kingoroot for windows however it is a slim change in my opinion as you wrote a FireTv image to your FireStick.
Copy and paste from: http://forum.xda-developers.com/fire-tv/development/guide-fire-stick-replace-king-o-root-t3440923
"IF YOU RUN INTO SOFTBRICK ISSUE (stuck at fire tv logo)
Make sure you have ADB drivers properly installed in your windows pc/laptop.
connect a genuine usb lead to the firestick/pc.
download the windows version of KINGO ROOT and install it.
open KINGO ROOT on the pc with Fire Stick connected up to pc and tv.
wait for the button to pop up and click root.
if you dont see AFTV or get enable debugging in the KINGO ROOT program on pc/laptop please unplug the stick from usb and replug it back in.
if this still wont work restart the pc/laptop or try another pc/laptop.
you should after clicking root boot back up into your homescreen, if it doesnt boot back into your homescreen automatically, wait around 5 minutes and unplug usb and re-plug it again. "
bula1ca said:
Do you still have root? Is your stick responding to the su command?
If so read this post: http://forum.xda-developers.com/fire-tv/help/guidance-recovering-bootloop-firetv-t3446902
If not:
Try kingoroot for windows however it is a slim change in my opinion as you wrote a FireTv image to your FireStick.
Copy and paste from: http://forum.xda-developers.com/fire-tv/development/guide-fire-stick-replace-king-o-root-t3440923
"[...]"
Click to expand...
Click to collapse
Thanks for the links, but from what I see, I need to get past the bootloader splash for adb to work. I'm stuck at the white "amazon" splash, not the colored "FireTV Stick" splash after the amazon one.
Sorry for not making it clear (and for that amount of text that maybe hid it)...
From what I understand and recall, I did only flash the recovery, right? Or does it automatically flash the zip I pushed to internal storage?
And what confuses me, the first attempt booting into recovery AFTER flashing the wrong one I got the former mentioned screen with red text. Reboot worked and the Stick was running. So I did retry and got the same red text after rebooting to recovery. I assumed it did not flash again and unplugged it earlier than the first attempt. Since then it got stuck at the white bootsplash.
Since I am still a noob, it seems to me the system wasn't touched, maybe a faulty recovery integrity forcing the bootloader to loop.
l_aios said:
Thanks for the links, but from what I see, I need to get past the bootloader splash for adb to work. I'm stuck at the white "amazon" splash, not the colored "FireTV Stick" splash after the amazon one.
Sorry for not making it clear (and for that amount of text that maybe hid it)...
From what I understand and recall, I did only flash the recovery, right? Or does it automatically flash the zip I pushed to internal storage?
And what confuses me, the first attempt booting into recovery AFTER flashing the wrong one I got the former mentioned screen with red text. Reboot worked and the Stick was running. So I did retry and got the same red text after rebooting to recovery. I assumed it did not flash again and unplugged it earlier than the first attempt. Since then it got stuck at the white bootsplash.
Since I am still a noob, it seems to me the system wasn't touched, maybe a faulty recovery integrity forcing the bootloader to loop.
Click to expand...
Click to collapse
I have no idea what you did however it will not automatically flash your zip, problem is you installed TRWP that was not meant for Firestick and overwrote its booting sequence. You most probably would had recover from your first attempt by re-installing a new image but once you tried to install it again it most probably finished writing the whole thing and damaged booting sequence.
bula1ca said:
I have no idea what you did however it will not automatically flash your zip, problem is you installed TRWP that was not meant for Firestick and overwrote its booting sequence. You most probably would had recover from your first attempt by re-installing a new image but once you tried to install it again it most probably finished writing the whole thing and damaged booting sequence.
Click to expand...
Click to collapse
Yeah, sad thing I got the wrong device, should have taken my time even more...
I googled the screen I got to two times before getting stuck:
http://forum.xda-developers.com/showpost.php?p=65968901&postcount=60
First time I waited approx. 15 minutes before pulling the plug to reboot. Since I noticed no difference I tried again and got the same screen. But this time I pulled the plug earlier, <1 minute.
I'd like to add that my bootloader was locked. Can I damage the booting sequence by corrupting the recovery or was my mistake that major to be able to do that?
I googled some key combinations to get into recovery or to bypass it, but I don't know if I get the right keys.
With my remote control I don't think I have enough time to hold the keys. Additionally I have a USB keyboard (Cherry KC1000; if possible, which keys btw?) and may be able to connect it via powered Y OTG cable.
So if anyone got any further input or ideas for me to rescue my FTVS, I'd be glad to receive it.
Thanks to all.
Anyone else maybe an idea?
The thing is, I cannot believe it is unsavable.
To summarize the current state (please see full details above):
- stuck in bootloop, white amazon logo
- flashed wrong recovery, after first flash the system booted, after second flash it got stuck (characteristics above)
- never flashed anything other than recovery
Strange thing it booted in first place, but now it refuses. Also I got the screen I mentioned above and unplugged as described above.
Can I possibly bypass the recovery check and try to boot directly to system? Or maybe interrupt for fastboot access?
If connected to PC, can you see it thru 'lsusb'? Or 'dmesg | tail'?
Kramar111 said:
If connected to PC, can you see it thru 'lsusb'? Or 'dmesg | tail'?
Click to expand...
Click to collapse
I tried both
watch -n 0.5 'dmesg | tail'
and
watch -n 0.5 'lsusb'
but with no identification whatsoever.
I double-checked with my Nexus 5 on the same port with the same cable, it identified fine.
One last bump for ideas before putting it into the trash.

Categories

Resources