Develop Bugs

[Q] Boot stuck at Pink Unicorn (Team Kang) Help!

OK...I'm a first time poster to the Kindle Fire forum and I'm having issues. I'm a little above average with my Android knowledge. I've flashed CM9 onto three Toucpads and have been fooling with my phones for a few years. HOWEVER, I'm completely stumped. Here's what's happening and what I've done.
1) I downloaded Kindle Fire Utility to root. It all went fine, as far as I could tell.
2) I downloaded the aokp_otter_build-M5>0xD34D build for CM9
3) I downloaded the gapps-ics-20120429-signed zip
4) Booted into the TWRP recovery
5) Made a backup of the stock Kindle
6) Flashed the CM9 zip and the Gapps zip. Everything seemed fine with the TWRP. Never used it before. Very familiar with CWM and seemed similar
7 Rebooted.
The Kindle Fire logo came up and then went to a blank screen. It boot-looped (is that a verb?) five or six times. While I went surfing to find answers it looped once more and came up to this screen with a pissed off looking unicorn and the Team Kang logo. It's stuck there and won't go past. The screen is still animated. The battery is not dead. I've read dozens of posts where the first suggestion is to charge the Kindle. That's not the problem. I've restarted the Kindle a hundred times and nothing.
Here's what I've tried:
1) Every combination of holding down the power button/pressing the power button combination. Nothing.
2) Downloaded the Kindle Unbrick Utility. The computer isn't recognizing the Kindle, so this isn't doing any good. I've tried all of the six different UI buttons. Nothing.
3) I went back to the Kindle Fire Utility and reinstalled the drivers and then opened the CMD window. As I expected, it's telling me "waiting for device" and doing nothing.
I have no idea where to go from here. There's got to be a way for me to get this thing to be recognized on my computer. Please help. Any advice would be greatly appreciated. Thanks! -Jeff

It's like deja vu...
http://forum.xda-developers.com/showthread.php?t=1658205
Even the description of the bootanimation is eerily the same.
I think my assessment of his problem would apply to you as well. If you want to skip most of the discussion, my post is at (or very near) the end.

Wow...that is creepy. I did a search on here for pink unicor/team kang, etc. Nothing came up. It's almost 2am and I can hardly see straight. I'll read through everything in the morning. Where would I get one of these magic cables I'm reading about?

jeffjoleen said:
Wow...that is creepy. I did a search on here for pink unicor/team kang, etc. Nothing came up. It's almost 2am and I can hardly see straight. I'll read through everything in the morning. Where would I get one of these magic cables I'm reading about?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1550999
Probably wouldn't hurt for you to look this over either...
http://forum.xda-developers.com/showthread.php?t=1552547

I dont see anything mentioned in your post about doing a full wipe before flashing AOKP just I thats where your method above went haywire with twrp. When going from one system to another always factory/ data restore wipe cache wipe dalvik and yes wipe system before flashing your rom and gapps. Pretty high likelyhood that why your stuck in a bootloop. You need to get back into recovery wipe the heck out of it and restore your backup. Also didnt hear mention of a bootloader. Do you get to a screen with a yellow triangle or one with a white kindle and a blue fire both these screen are bootloader splash screens for two different bootloaders. If you come to the yellow triangle hold the power button down immediatly till it turns orange this will put you into recovery. Alternatly if your greeted by a white kindle with a blue fire rapidly push the power button till some small words come up at the bottom of the screen 1. Normal 2. Recovery 3. Reset bootmode use the power button to toggle through the selections till it looks like --recovery-- this will get you into twrp where you can do as I said above wipe wipe wipe wipe restore backup reboot. Or maybe you havent got a bootloader installed.

You said you rooted with the Kindle Fire Utility and all went well. If that's the case you should have access to recovery. If so, you don't need a "magic" factory cable to fix your problem.
When you first boot your Kindle, what does the boot logo look like, exactly?

Thepooch said:
I dont see anything mentioned in your post about doing a full wipe before flashing AOKP just I thats where your method above went haywire with twrp. When going from one system to another always factory/ data restore wipe cache wipe dalvik and yes wipe system before flashing your rom and gapps. Pretty high likelyhood that why your stuck in a bootloop. You need to get back into recovery wipe the heck out of it and restore your backup. Also didnt hear mention of a bootloader. Do you get to a screen with a yellow triangle or one with a white kindle and a blue fire both these screen are bootloader splash screens for two different bootloaders. If you come to the yellow triangle hold the power button down immediatly till it turns orange this will put you into recovery. Alternatly if your greeted by a white kindle with a blue fire rapidly push the power button till some small words come up at the bottom of the screen 1. Normal 2. Recovery 3. Reset bootmode use the power button to toggle through the selections till it looks like --recovery-- this will get you into twrp where you can do as I said above wipe wipe wipe wipe restore backup reboot. Or maybe you havent got a bootloader installed.
Click to expand...
Click to collapse
Honestly...don't remember if I did a full wipe of dalvik. I assumed I would have, but really don't remember. No...I don't get the yellow triangle and my kindle fire logo color is white "kindle" with a yellow "fire". I used the kindle fire utility and I think that installs the twrp by default. I don't have CWM installed. Wish I did. I'm comfortable with it. I just can't get to any kind of a recovery screen.

soupmagnet said:
You said you rooted with the Kindle Fire Utility and all went well. If that's the case you should have access to recovery. If so, you don't need a "magic" factory cable to fix your problem.
When you first boot your Kindle, what does the boot logo look like, exactly?
Click to expand...
Click to collapse
Yes...the KFU went fine, I think. I was able to access twrp and created my backup before I flashed the ICS. The Kindle logo has the white "kindle" and yellow "fire". Pauses for a few seconds or two...screen goes black...then that damned pink unicorn shows up and stays there. The unicorn screen is animated. I can power it down from there and start over without any problem. Any ideas?

without a bootloader you wont have access to recovery regardless of twrp/cwm

One other thing that I'm not sure matters, but when I do power it off and back on, I head the little "bong" on my computer telling me that a new device has been plugged in. I go to the device manager and under the "Other" category it shows "Amazon" with the yellow triangle the black exclamation point symbol.

Reinstall your drivers

Thepooch said:
without a bootloader you wont have access to recovery regardless of twrp/cwm
Click to expand...
Click to collapse
I guess that's where I am a little confused with definitions. I understand about the twrp and cmw recovery set ups. What exactly is a bootloader? Thanks for not laughing...

Thepooch said:
Reinstall your drivers
Click to expand...
Click to collapse
Through the Kindle Fire Utility? If so, I've done that several times. Would trying a different computer and installing them there make any difference?

the bootloader allows you to access recovery im not laughing cause its a bummer to see things go this way you need to get your drivers going to push a bootloader to your device

First, read this...
http://forum.xda-developers.com/showpost.php?p=23747567
You need to make sure your drivers are in order so you can change the bootmode to 5001 and reboot. A custom bootloader will let you do this easily but considering you don't have one you need to use adb instead.
Code:
adb shell
idme bootmode 5001
adb reboot

Thepooch said:
the bootloader allows you to access recovery im not laughing cause its a bummer to see things go this way you need to get your drivers going to push a bootloader to your device
Click to expand...
Click to collapse
So, without a functioning bootloader I won't even be able to get to the twrp to access my back up I made. Nice. Just bought this damn thing yesterday. I'm kinda missing the one-click jailbreak software from my old iphone a few years back!

if the adb method that soup posted above doesnt work which required your adb drivers working your next route is likely here http://forum.xda-developers.com/showthread.php?t=1430038
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
while your pondering your next move might wanna look at this http://forum.xda-developers.com/showthread.php?t=1552547

Thepooch said:
if the adb method that soup posted above doesnt work which required your adb drivers working your next route is likely here http://forum.xda-developers.com/showthread.php?t=1430038
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
while your pondering your next move might wanna look at this http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
I just read through the basic instructions. I'll grab a usb thumbdrive and give it a shot. Thx

good luck hope you get through this is the not so fun side of rooting

Thepooch said:
if the adb method that soup posted above doesnt work which required your adb drivers working your next route is likely here http://forum.xda-developers.com/showthread.php?t=1430038
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
while your pondering your next move might wanna look at this http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
Thanks. It answered some of my questions. I guess it helped me relax a little, too. I know this is a problem that can be fixed. Just need to dig in an try each suggestion until I find one that works.

no os for kindle fire

Was trying to root kf . started "Install Permanent Boot, etc." all seamed to be going OK. Went as far as TWRP was installed. At that point the OS for the fire was GONE. Fire is hung at TWRP. No operating system for anything. Plz HELP

If TWRP is still functional, then you can just "mount USB," put a rom and gapps into the folder, flash them, then boom! You'll have an OS again; just basic protocol haha.
I would also wipe data/cache, dalvik, etc. just in case...
...But if you want stock Amazon Gingerbread then you're going to have to look way back in time in the forums for the stock rom.

What happens when you reboot system? Does it go right back to TWRP?

Me Too
I have no OS on my kindle fire. I wiped the memory and now I lost my roms and backups. I heard you can try ADB, but I couldn't get it to work. Mine just boots to the kindle fire logo but nothing else happens. It's basically collecting dust.

Take a breath, relax, and take comfort in the fact that there is nothing wrong with your Kindle. It is doing exactly what it was told to do. Your problem is easy to fix, but you need to know what's going on first.
http://forum.xda-developers.com/showpost.php?p=23747567
Read it. Then read it again. And while you're at it, go ahead and read it a third time. Do this before anything else.
[Edit:] Oh yeah, and read this too.
http://forum.xda-developers.com/showthread.php?p=25730650
Ahh, what the hell, read this one as well.
http://forum.xda-developers.com/showthread.php?p=26435498

soupmagnet said:
What happens when you reboot system? Does it go right back to TWRP?
Click to expand...
Click to collapse
Was not able to answer you as I was out town without internet connection-- When I boot I get a "Nornal Boot", "Recovery", and "Reset Boot Mode". The first two choices get a black screen with KindleFire, fire is blue after a bit fire turns red. also, upper right corner "V1.4"
If I go to #3, "Reset Boot", I get into TWRP. Saw on You Tube how to reinstall systen, however it would Reboot--NO OPERATING SYSTEM.

jerryhndy;31601922 ** said:
Was not able to answer you, as I was out town without an internet connection-- When I boot I get a "Nornal Boot", "Recovery", and "Reset Boot Mode". The first & last choices get a black screen with KindleFire, fire is blue after a bit fire turns red. also, upper right corner "V1.4"
If I go to #2, "Recovery", I get into TWRP. Saw on You Tube how to reinstall systen, however it would Reboot--"NO OPERATING SYSTEM"
QUOTE]
"
Click to expand...
Click to collapse

jerryhndy said:
Was not able to answer you as I was out town without internet connection-- When I boot I get a "Nornal Boot", "Recovery", and "Reset Boot Mode". The first two choices get a black screen with KindleFire, fire is blue after a bit fire turns red. also, upper right corner "V1.4"
If I go to #3, "Reset Boot", I get into TWRP. Saw on You Tube how to reinstall systen, however it would Reboot--NO OPERATING SYSTEM.
Click to expand...
Click to collapse
Wow, very interesting, and welcome back.
Weird. It's almost as if you have TWRP installed to the system partition. Selecting "reset boot" on FFF1.4 changes the idme value to 4000, so your device should boot to the system partition no matter what. But you said the boot logo changes from blue to red. What's actually happening, is the bootloader finishes doing it's thing and then boots to the system. The red and white Kindle Fire logo you see then is the stock boot animation, which makes everything really strange. "Recovery" boot shouldn't show the boot animation at all. And if you have recovery installed to the system partition, you shouldn't see the boot animation there either. WTF did you do to your Kindle?
My best advice would be to get into fastboot and reinstall TWRP to the correct partition so you can reinstall your ROM. From the sounds of it, you will likely have no access to the adb shell, in which case you would need to get a factory cable.
So, boot into recovery and enter the following command to see if you even have a working shell:
Code:
adb shell idme bootmode 4002

no os
jerryhndy said:
jerryhndy;31601922 ** said:
Was not able to answer you, as I was out town without an internet connection-- When I boot I get a "Nornal Boot", "Recovery", and "Reset Boot Mode". The first & last choices get a black screen with KindleFire, fire is blue after a bit fire turns red. also, upper right corner "V1.4"
If I go to #2, "Recovery", I get into TWRP. Saw on You Tube how to reinstall systen, however it would Reboot--"NO OPERATING SYSTEM"
QUOTE]
Sorry, above is the correct info that I sent in. #2 is "recovery. Sorry for the confusion.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Do you have the link to this youtube video?
Also, what ROM are you trying to install?

soupmagnet said:
Do you have the link to this youtube video?
Also, what ROM are you trying to install?
Click to expand...
Click to collapse
Link to you tube-- "youtube.com/watch?v=41ccbahk"
I am trying to get back to stock kindle fire so that I can start over. Or, am I beyound that?
Can I locate the orignal programing for the fire? That way I could download it ??
Would a factory cable do me good at this point?

jerryhndy said:
Link to you tube-- "youtube.com/watch?v=41ccbahk"
I am trying to get back to stock kindle fire so that I can start over. Or, am I beyound that?
Can I locate the orignal programing for the fire? That way I could download it ??
Would a factory cable do me good at this point?
Click to expand...
Click to collapse
There is no video at that address
Reverting to stock would only compound your problems right now as it would wipe out your custom recovery and bootloader, which are necessary to fix any problems should they arise.
Your best bet, as I mentioned earlier would be to reinstall TWRP, if that is actually the problem, but I'm not quite sure yet. I would be very helpful to know what ROM you tried to install when this problem started, and what steps you took to install it.

soupmagnet said:
There is no video at that address
Reverting to stock would only compound your problems right now as it would wipe out your custom recovery and bootloader, which are necessary to fix any problems should they arise.
Your best bet, as I mentioned earlier would be to reinstall TWRP, if that is actually the problem, but I'm not quite sure yet. I would be very helpful to know what ROM you tried to install when this problem started, and what steps you took to install it.
Click to expand...
Click to collapse
the address for the vido http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/
I have reinstalled TWRP Same problem. Not shure what you mean of "what ROM that I tried to install". Am I dead in the water??
factory cable would that me get out of this ?? I had downloaded the program from XDA site Kindle_Fire_Utility_V0.9.6

jerryhndy said:
the address for the vido http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/
I have reinstalled TWRP Same problem. Not shure what you mean of "what ROM that I tried to install". Am I dead in the water??
factory cable would that me get out of this ?? I had downloaded the program from XDA site Kindle_Fire_Utility_V0.9.6
Click to expand...
Click to collapse
There is still no video at that address.
If reinstalling TWRP doesn't fix the problem, there may be a problem with your file system.
Run the following commands and post the results here:
Code:
adb shell
parted /dev/block/mmcblk0
print
And a factory cable will only put the device in fastboot, not help you to install a ROM.

soupmagnet said:
There is still no video at that address.
If reinstalling TWRP doesn't fix the problem, there may be a problem with your file system.
Run the following commands and post the results here:
Code:
adb shell
parted /dev/block/mmcblk0
print
And a factory cable will only put the device in fastboot, not help you to install a ROM.
Click to expand...
Click to collapse
I found a keyboard in TWRP in the KF, however it would only let me type #'s. I think I am lost here. Do you accept KF's (sent to you), for
repair or what ever to get it to root ?? If so, I could sent it to you etc. [email protected]

Soupmagnet would be the one of the very best to send it to if he allows you I'm sure you wouldn't be disappointed

Thepooch said:
Soup magnet would be the one of the very best to send it to if he allows you I'm sure you wouldn't be disappointed
Click to expand...
Click to collapse
I have not heard from Soup Magnet. Is it possable that your answer got in the way of my response to Soup Magnet??
If SM does want to receive my KF for repair, do you another person how could look at the KF ??
Please advise Jerry

jerryhndy said:
I have not heard from Soup Magnet. Is it possable that your answer got in the way of my response to Soup Magnet??
If SM does want to receive my KF for repair, do you another person how could look at the KF ??
Please advise Jerry
Click to expand...
Click to collapse
doubt it soups my bud In fact Jerry if you ship it to me I would happy to take a look at it for you.

Thepooch said:
doubt it soups my bud In fact Jerry if you ship it to me I would happy to take a look at it for you.
Click to expand...
Click to collapse
OK, glad to. Send me your ship to address via E-Mail, [email protected] Also, can you give me approx cost on this?
Thanks, Jerry
You can see by all the correspondance that I am not getting anyware on this KF. The Kf was left to me by my brother who recently past away.
to

jerryhndy said:
OK, glad to. Send me your ship to address via E-Mail, [email protected] Also, can you give me approx cost on this?
Thanks, Jerry
You can see by all the correspondance that I am not getting anyware on this KF. The Kf was left to me by my brother who recently past away.
Click to expand...
Click to collapse
I sent you a pm Jerry. I would not charge you. Lets take a look and see if we can`t fix it without you even having to ship it.

[Q] Rooted HD 8.9 stuck in fastboot mode after attempted fw update.

I obtained a demo version 8.9 that I successfully rooted and installed 8.1.3 on. it worked perfect until like an idiot i tried to update to 8.1.4, manually. When it rebooted, after i started the update, a red screen scrolled across the screen and it went back into fastboot mode and has remained there since. I tried to use ADB in the android sdk to do a restore and everything seems to work, the 8.9's screen even shows the process in the upper LH corner like you'd expect but when it reboots I get the fastboot mode again. I can only select fastboot options with ADB, so I don't think I can install a second bootloader or a backup....can someone please help me

Um in fast boot you cant use adb commands only fast boot commands, so try flashing the stock recovery and system, I think your boot loader still works because you getting into fast boot without trying.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Rooted HD 8.9 stuck in fastboot mode after attempted fw update.
stunts513 said:
Um in fast boot you cant use adb commands only fast boot commands, so try flashing the stock recovery and system, I think your boot loader still works because you getting into fast boot without trying.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Can you provide info or a link on how to do that?

I just realized how vague my instructions are going to sound lemme try to find some actual instructions. Hmm maybe you shouldn't follow my instructions to avoid worse brick. Most everything I have read says to flash a custom recovery to recover stock but those weren't on already bricked devices ... Researching.....
I believe this will be a lot more helpful so I will delete what in said to do in this post and say this is probably a lot more useful. I believe it comes with the boot loader, recovery and system images, you probably don't need to flash the bootloader though.
http://forum.xda-developers.com/showthread.php?t=2011126
Hope this is helpful, I'm slightly half asleep so it wasn't my best research, but I think I'm right.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Thank You
stunts513 said:
I just realized how vague my instructions are going to sound lemme try to find some actual instructions. Hmm maybe you shouldn't follow my instructions to avoid worse brick. Most everything I have read says to flash a custom recovery to recover stock but those weren't on already bricked devices ... Researching.....
I believe this will be a lot more helpful so I will delete what in said to do in this post and say this is probably a lot more useful. I believe it comes with the boot loader, recovery and system images, you probably don't need to flash the bootloader though.
http://forum.xda-developers.com/showthread.php?t=2011126
Hope this is helpful, I'm slightly half asleep so it wasn't my best research, but I think I'm right.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I don't even know how I can thank you enough, the link you gave me was perfect. Everything works great now!

[Q] [Nexus 7 - 2013, wifi, 16G]Got stuck at Google logo

Hi everybody,
I'm so angry with my Nexus 7 (wifi 2013) because I just made it mess up.
Let me tell you how stupid I was.
First, I tried to root but it failed.
Second, I used 'Back to Stock' with 'Nexus Root Toolkit v1.7.2'. Finally, I got stuck at Google logo
I tried some solutions on the internet but it still unchanged anything.
Could you show me how to fix it, please?
Thank you so much.
This is the images of error that I got (I'm sorry I cannot insert image because I'm a new member of this forum, could you go to the link below to see more details?)
s1019.photobucket.com/user/namserious/media/Error_Nexus7.png.html

Your /system is broken.
Try restoring factory defaults using this post:
http://forum.xda-developers.com/showthread.php?p=45671279#post45671279

Restoring Successfully
sfhub said:
Your /system is broken.
Try restoring factory defaults using this post:
http://forum.xda-developers.com/showthread.php?p=45671279#post45671279
Click to expand...
Click to collapse
Awesome, sfhub :good: :laugh:
Thank you so much. I have restored successfully.
This is my result
i1019.photobucket.com/albums/af319/namserious/WP_20131018_001.jpg

How did you do that?
namserious said:
Awesome, sfhub :good: :laugh:
Thank you so much. I have restored successfully.
This is my result
i1019.photobucket.com/albums/af319/namserious/WP_20131018_001.jpg
Click to expand...
Click to collapse
Hey namserious,
How did you get it working? Did you use the Mini guide given by sfhub? I'm having the same issues with my nexus 7 (2013). I only used for one day. Restarted on the second day and never got anything after the Google logo. Also, my phone wasn't rooted, so I didn't have developer options turned on and since I can't get into the system, I can't turn it on either. Will that make a difference?
Thanks.

nexussucks said:
Hey namserious,
How did you get it working? Did you use the Mini guide given by sfhub? I'm having the same issues with my nexus 7 (2013). I only used for one day. Restarted on the second day and never got anything after the Google logo. Also, my phone wasn't rooted, so I didn't have developer options turned on and since I can't get into the system, I can't turn it on either. Will that make a difference?
Thanks.
Click to expand...
Click to collapse
If you didn't root the device or do anything else with it, you should be able to get into Recovery Mode and do a factory reset.
https://support.google.com/nexus/answer/2668187?hl=en

Even recovery doesn't work
I'm not able to get into recovery mode. When I select recovery mode, the tablet starts and displays Google logo again and gets stuck there again.

nexussucks said:
I'm not able to get into recovery mode. When I select recovery mode, the tablet starts and displays Google logo again and gets stuck there again.
Click to expand...
Click to collapse
When you get into recovery you will see just the droid and the red triangle. At this screen you will need to push the power button then Vol Up and release. I had to do that about 3 times then I was able to get the menu items. From there I did a factory reset. After that I was good to go. Hope this helps!
Kind Regards,
Rb

RenderBroken said:
When you get into recovery you will see just the droid and the red triangle. At this screen you will need to push the power button then Vol Up and release. I had to do that about 3 times then I was able to get the menu items. From there I did a factory reset. After that I was good to go. Hope this helps!
Kind Regards,
Rb
Click to expand...
Click to collapse
Thanks Rb, But the thing is I don't get the droid and red triangle at all after I select recovery mode. I have tried everything but nothing happens. I still end up with dreadful Google logo. Suddenly I'm beginning to really hate it.

nexussucks said:
Thanks Rb, But the thing is I don't get the droid and red triangle at all after I select recovery mode. I have tried everything but nothing happens. I still end up with dreadful Google logo. Suddenly I'm beginning to really hate it.
Click to expand...
Click to collapse
You could try re-flashing the factory image.
http://forum.xda-developers.com/showthread.php?t=2487757
Latest factory image build is JSS15R
https://developers.google.com/android/nexus/images#razor

nexussucks said:
Thanks Rb, But the thing is I don't get the droid and red triangle at all after I select recovery mode. I have tried everything but nothing happens. I still end up with dreadful Google logo. Suddenly I'm beginning to really hate it.
Click to expand...
Click to collapse
Im sorry, I didnt read correctly. I had issues too restoring back to Stock since my setup was all changed. I had to use these steps. I am going to assume you know how to use fastboot and what it is.
DISCALAIMER! These steps will delete your user data!!!!
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader BOOTLOADER.img
> fastboot reboot-bootloader
> fastboot -w update IMAGE.zip
So after that I was able to get past the google logo but just stuck at the boot logo (Multi Colored X) I then had to get into recovery using the steps I stated above then did a factory reset.

Success
Rb, I just tried your instructions. YOU ARE A SAVIOUR :laugh:. After 2 days of continous troubleshooting, I had given up my hopes and was thinking of returning it. But suddenly after getting used to seeing the Google logo, I just noticed the android robot on the screen. And after a few seconds I saw the welcome screen... Viola.
Thanks man, I really appreciate your help. :good:

nexussucks said:
Rb, I just tried your instructions. YOU ARE A SAVIOUR :laugh:. After 2 days of continous troubleshooting, I had given up my hopes and was thinking of returning it. But suddenly after getting used to seeing the Google logo, I just noticed the android robot on the screen. And after a few seconds I saw the welcome screen... Viola.
Thanks man, I really appreciate your help. :good:
Click to expand...
Click to collapse
Glad to help! The best thing about Nexus devices are the different fail-safes. If the Rom is screwed up you can flash a new one from recovery. If recovery is screwed you flash a new one from the boot loader. If the boot loader is screwed you can flash another from recovery. Also the N7 2013 tablet is the best for the money. I user mine for work. I am a tech admin for a school district and have certain tools located on my desktop (Active Directory, Printer Manager, etc) and I have RDP installed on my N7. Now when I need to reset a password or whatever i can just RDP to my desktop. This tablet has made my life easier and hopefully yours will too now.
Kind Regards
Rb

Name change
RenderBroken said:
Glad to help! The best thing about Nexus devices are the different fail-safes. If the Rom is screwed up you can flash a new one from recovery. If recovery is screwed you flash a new one from the boot loader. If the boot loader is screwed you can flash another from recovery. Also the N7 2013 tablet is the best for the money. I user mine for work. I am a tech admin for a school district and have certain tools located on my desktop (Active Directory, Printer Manager, etc) and I have RDP installed on my N7. Now when I need to reset a password or whatever i can just RDP to my desktop. This tablet has made my life easier and hopefully yours will too now.
Kind Regards
Rb
Click to expand...
Click to collapse
This is my first experience with a Nexus device and I might have judged it in a wrong way. But I think the problem is not the device but the information regarding the latest Nexus devices. Hopefully there will be more workarounds of the new Nexus devices.
I guess I will have to change my username

nexussucks said:
This is my first experience with a Nexus device and I might have judged it in a wrong way. But I think the problem is not the device but the information regarding the latest Nexus devices. Hopefully there will be more workarounds of the new Nexus devices.
I guess I will have to change my username
Click to expand...
Click to collapse
This is the price we pay for the cutting edge. Also , at least for me, this is part of the fun. Now I have a much better understanding of Android than if I did being an avg. user. I was thinking the same about the name change. lol

RenderBroken said:
Glad to help! The best thing about Nexus devices are the different fail-safes. If the Rom is screwed up you can flash a new one from recovery. If recovery is screwed you flash a new one from the boot loader. If the boot loader is screwed you can flash another from recovery. Also the N7 2013 tablet is the best for the money. I user mine for work. I am a tech admin for a school district and have certain tools located on my desktop (Active Directory, Printer Manager, etc) and I have RDP installed on my N7. Now when I need to reset a password or whatever i can just RDP to my desktop. This tablet has made my life easier and hopefully yours will too now.
Kind Regards
Rb
Click to expand...
Click to collapse
Hey, know it's been a little bit but my nexus 7 says no OS in TWRP recovery. I tried flashing it back to stock but it doesn't work. The bootloader is locked and when I try to do anything manually it just hangs on stuff like erasing 'system'/cache etc... in fastboot. I have not been able to find anything to work. And when I try to fastboot oem unlock it gets stuck when i press volume up and power to accept unlocking it. I have tried different cables and another computer. maybe I should try a third computer.. Do you have any suggestions?

RenderBroken said:
Im sorry, I didnt read correctly. I had issues too restoring back to Stock since my setup was all changed. I had to use these steps. I am going to assume you know how to use fastboot and what it is.
DISCALAIMER! These steps will delete your user data!!!!
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader BOOTLOADER.img
> fastboot reboot-bootloader
> fastboot -w update IMAGE.zip
So after that I was able to get past the google logo but just stuck at the boot logo (Multi Colored X) I then had to get into recovery using the steps I stated above then did a factory reset.
Click to expand...
Click to collapse
I know this is an old thread, but I'm having this exact issue. I'm just stuck on the google screen. I can get into the bootloader just fine, but not the recovery. I followed these directions. Flashed the factory image and everything. But I still can't get past the google logo. I've followed every bit of advice I could find on this issue and I can't seem to get it working. Any help would be greatly appreciated!

*bump*
Does anyone know what's going on? I've tried everything I could find. Multiple times. From the suggestions listed here to the WUG kit to this http://forum.xda-developers.com/showthread.php?t=2381582
Nothing is working. I goes through the reflashing successfully. The command prompt says that everything is done. And then it just gets stuck at the Google screen again. I'm at my wits end and have no idea what to try next. I know that because I can get into the bootloader still, there has to be SOMETHING that will work. But I just don't know. Any ideas?

is there a android L Developers Preview flashable zip? thanks
Sent from my Nexus 7 using XDA Free mobile app

Anyone figure out what is causing this? I got a remanufactured 2nd Gen N7 16G yesterday. Updated to 4.4.4 over the air. Then unlocked the bootloader and rooted. Everything went fine. I installed Franco's latest kernel (r17) over stock and all was well. However, this morning, while using the device in the middle of GoW, it rebooted to the Google Screen and froze there. I could boot into the bootloader and have my comp recognize the device, so could ADB and Fastboot, however, I could not get into recovery. (I had installed TWRP 2.7.1.1 when I rooted). Trying to get into recovery would just freeze at the Google Screen.
So, I then tried both manually ADB'ing commands, as well as using Wug's Toolkit, and both methods seemed to complete successfully without error (I was using the latest Razor-Flo 4.4.4 files from Google's Dev Page so it is not an issue where I am using the Gen 1 files for Grouper or anything like that in error), however, neither method allowed me to boot into recovery, and left me at the same place. No matter what I did, I was stuck at that screen. I ended up calling Asus to RMA.
So, while it is not a current issue for me, I am interested to know if anyone has sorted what the root cause is, and whether it is an issue on the hardware side. I am not a complete noob to the N7 (I have 2 Groupers), and have been modding for a few years on Samsungs, and until this morning, have never had a soft brick I could not fix. This time, I gave up.

Same problem here, I have a Deb 32g, it went a little wonky and then rebooted. No amount of flashing and wiping and fastbooting has been able to recovery it. Gets stuck on Google Logo no matter what I do. Can't get recovery. Can't boot past Google. It will do fastboot without errors, but that's the only thing it will do.

Have a bricked kindle , stuck in fastboot mode - tried all-Please Help

I have a bricked kindle (8.9). i have followed ALL guide but still get red screen and then fast boot screen.
i have pushed boot and recovery and still get the same . i used first aid package and kfhd, but still boot to fastboot screen.
I would appropriate any help or guidance.

gs4n said:
I have a bricked kindle (8.9). i have followed ALL guide but still get red screen and then fast boot screen.
i have pushed boot and recovery and still get the same . i used first aid package and kfhd, but still boot to fastboot screen.
I would appropriate any help or guidance.
Click to expand...
Click to collapse
you ever get this straight? i had the very same issue and after several DAYS of reading/flashing/swearing i finally got it straight back to factory, let me know if you still need help and i will try to find the thread that ultimately helped me bring mine back to life
Thanks
Mike

11fan said:
you ever get this straight? i had the very same issue and after several DAYS of reading/flashing/swearing i finally got it straight back to factory, let me know if you still need help and i will try to find the thread that ultimately helped me bring mine back to life
Thanks
Mike
Click to expand...
Click to collapse
Hi,
i am still down. how did you get it to boot up. ? How did you fix it ? Mine is completely blank now. Thanks,

OK..let me find the thread that should get u going..I have it bookmarked on my PC but using mobile ATM, I will try to find it

this here should get you going! just follow EXACTLY! (with the exception of using KFFirstAide) just use regular command prompt run as admin) probably will not have to go past 8 in most cases, usually after you flash that recovery image and erase cache and user data it will reboot in it's OWN recovery on next reboot, and also when erasing user data, it could take up to 45 mins maybe depending on how long you had been using it before it got corrupted so don't panic when it sits there forever after you issue erase user data command. IF it reboots back into it's own recovery it will give you two options on the Kindle screen to either boot into OS or RESET to factory, in my experience I would definitely choose to RESET TO FACTORY DEFAULTS, but thats your choice, and if you need help I will try to walk you through it on some type of IM or google hangout or something. keep me posted as im curious to here the outcome. I know this has fixed two Kindles with the same problem as yours http://forum.xda-developers.com/showpost.php?p=37278819&postcount=193

can you still access fastboot?
my KFHD 8.9 was stuck in fastboot mode also a few days ago (http://forum.xda-developers.com/kin...lp/help-stuck-kindlefire-boot-screen-t2971768), and @11fan helped me. (Thanks a lot!). That thread that he posted was the one that helped me revive my kindle. I also tried the KFHD SRT where i tried the option to restore with the SU app. I actually didnt know if that helped but when i was finally able to get my kindle going, it was on version 8.1.4 (i was on 8.5.1 before). Then i used that thread, the thing is, it took me 37 minutes to erase the userdata (as was mentioned by @11fan), and when i rebooted to system, i didnt go the restore factory settings (probably because i erased all the userdata already).
I hope you get to fix your kindle. i know the feeling of being in that situation.

? ?. ? ?