Related
CDMA GALAXY NEXUS> Hey guys, I was running Romanbb's 4.0.4 build earlier today. I clicked on a video (which may or may not have been on a porn site) all of a sudden my screen went all wacky. Where it was kind of fuzzy and running diagnal across the screen. I could only see part of it. I thought I might have gotten a virus or something because i have never had one of my devices do this before. So I immideatly rebooted the phone into recovery and wiped eveything including formatting system. I went to flash a nandroid I had of black ice and in the middle of flashing that my phone rebooted itself and stayed there (bootlooping at the google logo) I can get into fastboot and I can get into recovery about one out of every ten times but I cant do anything in recovery because the phone turns itself off insted of booting recovery most of the time (I have clockwork touch) When I do get into recovery without it turning off it reboots if I try to flash anything. It seems to be stable in fastboot (thank god!) but When I get it connected in Wugs Root tool kit and try to flash the stock image it goes through the motions and says FAILED on every step exept the first (which I believe is checking radio). It says ( error too many links) on the first two) and I cant remember the error on the last four but I have tried it a couple times so I can replicate it if needed. Can anyone tell me what to do from here? I really appreciate in advance!!! If this is a hardware error then I would like to get it back to stock to get it replaced. It is weird that it happened while running a rom. Its not like I messed up while flashing or anything.
ADB will recognize it in Fastboot. I already set all of that up when I rooted. when I try to flash the stock+unroot option on wugfresh's toolbox it errors out on every step like there is something wrong with my internal sd on my phone? Im wondering if I should try odin. IDK? Im hoping somebody who has seen this or had this happen before will save the day and tell me what to do.
lol why did you rush into CWM and start wiping things? you should have let it reboot and it probably could have been a one off..
you can try this http://rootzwiki.com/topic/14145-od...actory-odin-restore-402-with-radios-unrooted/
It is stable in fastboot but in cwr it is still geeking out
It still is glitching in cwr. most of the time it either turns off or reboots when I try to go into cwr. i can wipe but if I flash anything it freezes at the point where it starts writing to storage. I have never seen anything like this before.
I have now tried oden as well
It looks like it is a problem with the hardware. The phone is only a couple months old if that. So I really wish I could flash the stock image or at least get rid of cwm. but that is not looking likely. Here are a couple pics of odin showing the problem. Any guidace would be much appreciated. This SUCKS
Why in the heck are you trying to use Odin?
I can only get into fastboot and odin.
CWM wont let me do anything. it crashes and reboots into a bootloop if I try to flash anything. The poster above suggested odin. I dont know what else to do. Please help if you can!
Can you get a screencap of when it fails fastbooting the stock images?
yes
yes, give me couple min and I will post it. Thank you!
I guess I cant. This is all I get now
drumdestroyer said:
yes, give me couple min and I will post it. Thank you!
I guess I cant. This is all I get now
Click to expand...
Click to collapse
How are you attempting to access fastboot?
Vol + and Vol - and power all at the same time
Vol + and Vol - and power all at the same time from powered off
And oden was Vol - and power at the same time from powered off
Now no matter what I push it goes to the screen with the yellow triangle.
That screen says you (now) have a corrupt partition.
At this point, you must use Odin, which is unfortunate. What URL did you use to download the image? The current image in that thread was on multiupload.
drumdestroyer said:
Vol + and Vol - and power all at the same time from powered off
And oden was Vol - and power at the same time from powered off
Now no matter what I push it goes to the screen with the yellow triangle.
Click to expand...
Click to collapse
during my rooting attempt I had a problem with the two vol buttons. It was quite frustrating. Keep trying them and try pressing the power button a fraction of a second sooner.
I downloaded the one later in the thread
Here's the Modem: http://dl.dropbox.co...15.EK02_LTE.tar
Here's the System: http://dl.dropbox.co...L53F_signed.tar
from this thread on page 3 housry23 posted them from his dropbox:
http://rootzwiki.com/topic/14145-od...restore-402-with-radios-unrooted/page__st__30
there were a couple other posts right around the same time with it but they all were the same file name
I thought I saw the same files in the xda thread i found also
I used that thread because it is the one that the second post linked for me.
drumdestroyer said:
Vol + and Vol - and power all at the same time from powered off
And oden was Vol - and power at the same time from powered off
Now no matter what I push it goes to the screen with the yellow triangle.
Click to expand...
Click to collapse
Send it to me. I might be able to fix it. PM me.
Sent from my Galaxy Nexus using xda premium
loveubuntu said:
during my rooting attempt I had a problem with the two vol buttons. It was quite frustrating. Keep trying them and try pressing the power button a fraction of a second sooner.
Click to expand...
Click to collapse
no luck with that. it seems to only open to the "corupted partision" screen. Thanks for the suggestion.
ljwnow said:
Send it to me. I might be able to fix it. PM me.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I pm'd you to ask how you could fix it. Just wondering if I could do it. I can follow instructions well. I have never had a problem and have been flashing stuff for a year or so. IDK what happened here.
I can't help but I wanted to share that I had a similar experience. I was bonne stock and clicked on a you tube video and my phone immediately shut down and tried to reboot itself, but only would boot loop. I had to manually reformat my partitions to recover. Sounds like your case might be even worse. Still don't know what my problem was.
Sent from my Galaxy Nexus using XDA
Thanks. Any feedback is appreciated.
so you can't get into bootloader or odin screen any more? if so try using a Jig it works to get the phone into odin mode for me. i used the same usb jig i made for the captivate.
I got the same suggestion from someone else. I have to wait until radio shack opens in the morning and I will give it a shot. Otherwise, I went by verizon and they are having samsung send me a replacment. I would much rather keep this one if I can though
I tried flashing the stock image from fastboot and it failed though when I could get there, and I also tried flashing the stock image through oden when I could get there and both failed multiple times so I don't have much hope. I think something broke.
I am headed to radio shack now. Be back soon with a answer as to wheather I can save my baby or not.
Three days ago I went through the process of rooting my kindle fire using KFU. Being a noob, this took me many many hours. I got everything to work, GO Launcher, Google Play, Amazon App store. I even used the Voodoo OTA Rootkeeper to temporily un-root so that I can watch amazon streaming videos. I was feeling pretty good about my accomplishment.
Late last night, for no apparent reason, the Kindle Fire restarted itself and got stuck on the yellow triangle (is this FireFireFire?). I got nervous, freaked out a little. I plugged into my computer and tried to restart the Kindle after selecting 'Recovery (5001)'. No luck. I then tried the same thing after selecting 'Normal (4000)'. I could hear the USB connect/disconnect many times and then I saw the "Kindle Fire" screen and let out a sigh of relief. It booted up just fine. This was about 2 hours ago.
But, now, my Kindle randomly goes back to the yellow triangle and hangs there. I need to go through the same process above to fix things. This has happened at least four times already. It did not seem to happen while the Kindle was "connected" to my computer. It happens once I 'disconnect'.... usually after about 10 - 20 minutes. It has happened while using both GO Launcher EX and the Amazon Launcher. Any idea?
You've got the same issue I do - the kindle keeps trying to apply the new update, and it isn't working, dumping it into recovery mode. I haven't figured out an answer to getting the update successfully applied yet (will work on that tonight), but until that happens, you should be able to remove the update from the sdcard /kindleupdates, and through something like root explorer rename /etc/security/otacerts.zip to something like /etc/security/otacerts.bak (or better yet, move it to the sdcard). That will stop it from redownloading the update and auto-rebooting.
Look Here
Have you looked at this http://forum.xda-developers.com/showthread.php?t=1417234 thread. The video explains the most common fix, and he goes through it step by step.
Also, so you grow a thick skin for posting on this forum, check out this link http://forum.xda-developers.com/showthread.php?t=1633343.
Hope this helps
Thanks for listening.
Sincerely,
William
[Kindle Fire: gedeROM v1.2 {3.0 Kernel, CM9, Android 4.0.4} - Stock Kernel]
[HTC Evo 4G Supersonic: MikG 3.11 ROM - Chop Suey Custom Kernel]
[Retired: HTC CDMA Hero: Gingerbread Hero Deck ROM - Stock Kernel]
end.
Ok. I just tested it, and had it also confirmed in another thread, but here is one way to get 6.3.1 on when the update fails to apply, putting you into the recovery, force to normal boot, kindle updates, back to recovery loop:
if you have a copy on your device, copy the update to the root of the sdcard volume or download it from amazon. Rename the file update.zip, then reboot into recovery.
Under install, install the update.zip. Once it is done, you'll have 6.3.1 applied. Now, you'll have to both reroot, and reinstall recovery, but since you just did it with KFU a few days ago, it should be pretty quick. Then go move/rename the otacerts.zip file to prevent the next unexpected update.
There might be another way that doesn't blow away recovery, but this worked for me.
Thanks so much for all of the help! It looks like everything is working again. I got 6.3.1 installed (not really sure how that happened but it did!). Also got re-rooted and reinstalled TWRP and did a backup. I renamed the otacerts.zip. There is also a cacerts.bks file in the /etc/security directory... what does that do?
Also... will I ever want/need the updates? I assume renaming the otacerts.zip stops the updates indefinitely. Will this ever be a problem?
Thanks again!
Moving the otacerts.zip prevents the kindle from automatically downloading updates. When a new update has been released, you can download it from amazon's site manually, or put back the cert file to enable the download. Since updates often break root, this method will help keep you rooted until it is known how to root the new versions. As for want/needing them, it'll depend on what changes, but as long as they are rootable, they should generally bring improvements for the device.
The. bks file is a keystore for the certificate authority certs. You shouldn't need to ever touch that file.
powers down
Ok, I've got the exact same issue but one glaring difference. That after using KFU to boot to normal, it within 10-20sec powers down. Starting the bootloop all over. Don't know what to do, please help.
Does it actually fully boot into the kindle os? I haven't heard of it trying to apply the update that fast after start up, but not saying that it won't do that.
If using twrp, you can mount the kindle over usb from twrp - mount, and then move the update file out of kindleupdates. That should stop the boot cycle if it is being caused by the update. Another thing to check would be to look at the twrp console and make sure it is complaining about the update failing and not something else.
When I try to mount it ask me to format the drive, is that safe? Won't I lose everything then? Also, it won't allow me to select just the sd, it only allows me to select system.
ms6146 said:
Ok, I've got the exact same issue but one glaring difference.
Click to expand...
Click to collapse
That sounds eerily familiar...Where have I seen that before?
That after using KFU to boot to normal, it within 10-20sec powers down. Starting the bootloop all over. Don't know what to do, please help.
Click to expand...
Click to collapse
Only kidding...Actually that problem isn't the same at all and is described in detail here: http://forum.xda-developers.com/showthread.php?p=25400963
ms6146 said:
When I try to mount it ask me to format the drive, is that safe? Won't I lose everything then? Also, it won't allow me to select just the sd, it only allows me to select system.
Click to expand...
Click to collapse
Formatting your sdcard will erase everything on it. Besides trying to mount your sdcard, what are you trying to accomplish?
Well I'm stuck in bootloop with the powering off problem. The kindle is not recognized on the computer. All I want is to get the kindle back working. I have tried the unbrick utility but I think that made it worse. Getting back to a regular firmware even if its the latest would be fine. However being the noob that I am, I need step by step instructions. Thanks in advance.
ms6146 said:
Well I'm stuck in bootloop with the powering off problem. The kindle is not recognized on the computer. All I want is to get the kindle back working. I have tried the unbrick utility but I think that made it worse. Getting back to a regular firmware even if its the latest would be fine. However being the noob that I am, I need step by step instructions. Thanks in advance.
Click to expand...
Click to collapse
Your problem can still be fixed, but considering the fact you can't get the computer to recognize your device, you only have a couple of options left:
You could acquire a factory cable which would directly power your device in order to replace the bootloader.
If you don't have the means to acquire a factory cable you need to mount your sdcard in order to transfer FFF1.4 for flashing in recovery. From what I understand in your earlier post, it would in your case, require formatting your sdcard
yellow triangle and restart, please help
Jarden said:
Three days ago I went through the process of rooting my kindle fire using KFU. Being a noob, this took me many many hours. I got everything to work, GO Launcher, Google Play, Amazon App store. I even used the Voodoo OTA Rootkeeper to temporily un-root so that I can watch amazon streaming videos. I was feeling pretty good about my accomplishment.
Late last night, for no apparent reason, the Kindle Fire restarted itself and got stuck on the yellow triangle (is this FireFireFire?). I got nervous, freaked out a little. I plugged into my computer and tried to restart the Kindle after selecting 'Recovery (5001)'. No luck. I then tried the same thing after selecting 'Normal (4000)'. I could hear the USB connect/disconnect many times and then I saw the "Kindle Fire" screen and let out a sigh of relief. It booted up just fine. This was about 2 hours ago.
But, now, my Kindle randomly goes back to the yellow triangle and hangs there. I need to go through the same process above to fix things. This has happened at least four times already. It did not seem to happen while the Kindle was "connected" to my computer. It happens once I 'disconnect'.... usually after about 10 - 20 minutes. It has happened while using both GO Launcher EX and the Amazon Launcher. Any idea?
Click to expand...
Click to collapse
Hello Jarde, I have the same problem but I am super noob, my kindle is restarting at the yellow triangle every 3 seconds, you said " then tried the same thing after selecting 'Normal (4000)'. I could hear the USB connect/disconnect many times and then I saw the "Kindle Fire" screen and let out a sigh of relief", what do you mean selecting 'Normal (4000)', how can I do this?, and finally how did you solve the problem, thanks a lot and sorry for my poor english.
notforever said:
Hello Jarde, I have the same problem but I am super noob, my kindle is restarting at the yellow triangle every 3 seconds, you said " then tried the same thing after selecting 'Normal (4000)'. I could hear the USB connect/disconnect many times and then I saw the "Kindle Fire" screen and let out a sigh of relief", what do you mean selecting 'Normal (4000)', how can I do this?, and finally how did you solve the problem, thanks a lot and sorry for my poor english.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=25400963
I had the same issue - shutdown after a few seconds after boot, then the KF boots back into yellow triangle error.
I was able to get out of this loop by booting into recovery and wiping the cache partition (and the Dalvik cache for good measure) to remove the downloaded update file. After wiping the caches, my KF rebooted normally without issue. I could then us Root Explorer to rename the /etc/security/otacerts.zip file to something else as suggested in an earlier post. I have not had a problem since.
I saw a couple people had the same issue that im now having but none of there solutions solved my problem
i wiped my GS3 for ATT tried to go back to a stock with root rom and when it rebooted it now just hangs at the samsung logo at boot tried re-flashing via odin with no luck also tried flashing a CWM.tar since i cant get into stock or CWM recovery to flash from there is there something im missing i know its late and maybe my brain isnt working like it should
Solved the problem myself.....and rather then just say i figured it out ill share how i did this since i watched countless videos and read endless amounts of threads and since none of them helped mem
First also try t put your phone into stock recovery mode and wipe your phone then flash this should take care of things if it doesnt try what i tried below
and i hope this can help someone else out there who has the same problem that i had all you have to do is the following i did this with obviously an AT&T model should work with others but as always try at your own risk.....
First make sure your battery has a charge even if its stuck on the boot screen its still charging....
then download KIES from samsung update it and make sure you have the latest version.
Next plug in your phone if your stuck at the samsung screen your computer will recognize your phone still at least it did with mine.
Once your done with the above open up KIES goto the top and then TOOLS and Firmware upgrade click on that enter your phone model (ATT SGH-I747) i dont get this part but next it will ask you for your SN and for some reason it doesnt recognize the SN use your IMEI
Now it should ask you a couple questions tell you its wiping your device and you will lose everything etc.....but then it will download the latest FW and begin to install everything and in about 20-25 mins everything will be back to stock
Nvm.. misread.
I'm stuck too...and Kies can't find the phone. Anyone have any other ideas? I can't even get into recovery...only download mode.
dbdynsty25 said:
I'm stuck too...and Kies can't find the phone. Anyone have any other ideas? I can't even get into recovery...only download mode.
Click to expand...
Click to collapse
your computer is not seeing your phone when you plug it in or its just KIES that doesnt see it??
also im guessing you have all the correct drivers installed??
yearziro said:
your computer is not seeing your phone when you plug it in or its just KIES that doesnt see it??
also im guessing you have all the correct drivers installed??
Click to expand...
Click to collapse
Yes, all drivers are installed because that's how I ODIN flashed it in the first place! Just stuck on the damn Samsung screen and I can't get Kies to connect to the phone. Not in Download Mode or when it's just stuck on that screen.
you can just hold VOL UP, HOME , POWER same time enter stock samsung recovery mode and scroll down select wipe data and cache and reboot u should good to go....
whit3gh0szt said:
you can just hold VOL UP, HOME , POWER same time enter stock samsung recovery mode and scroll down select wipe data and cache and reboot u should good to go....
Click to expand...
Click to collapse
Worked, thanks! I appreciate it.
it doesnt work on mine
dbdynsty25 said:
Worked, thanks! I appreciate it.
Click to expand...
Click to collapse
my cellphone reboots by itself on the samsun screen and i cant get on the recovery mode! any ideas!"
me neither
mkstf said:
my cellphone reboots by itself on the samsun screen and i cant get on the recovery mode! any ideas!"
Click to expand...
Click to collapse
Yeah I can't get into recovery either, and its getting really annoying.
indieslap said:
Yeah I can't get into recovery either, and its getting really annoying.
Click to expand...
Click to collapse
With the phone off, hold down VOL UP + HOME + POWER until the phone vibrates. Then let go of the power button. When you see the blue text in the top left corner of the samsung boot screen, let go of the other 2 buttons
xBeerdroiDx said:
With the phone off, hold down VOL UP + HOME + POWER until the phone vibrates. Then let go of the power button. When you see the blue text in the top left corner of the samsung boot screen, let go of the other 2 buttons
Click to expand...
Click to collapse
Okay, this brought the menu up for me, but I removed the data,cache, and reset the phone and it is still not working. Also, my phone just goes black after the Galaxy Samsung S3 logo, but the blue light in the top left is still on. Can anyone help me out?
P.S. Sorry for reviving this thread if it is too old.
Edit: I should also mention that I can still hear the sound of the phone booting up (the sound that typically occurs when the phone is on the white loading screen). However, the screen is black at this point.
cabato said:
Okay, this brought the menu up for me, but I removed the data,cache, and reset the phone and it is still not working. Also, my phone just goes black after the Galaxy Samsung S3 logo, but the blue light in the top left is still on. Can anyone help me out?
P.S. Sorry for reviving this thread if it is too old.
Edit: I should also mention that I can still hear the sound of the phone booting up (the sound that typically occurs when the phone is on the white loading screen). However, the screen is black at this point.
Click to expand...
Click to collapse
You're going to have to tell us what you did (changed, flashed, etc) before all this so that we can help you
xBeerdroiDx said:
You're going to have to tell us what you did (changed, flashed, etc) before all this so that we can help you
Click to expand...
Click to collapse
Ah, sorry about not providing enough information. Please keep in mind that I am very inexperienced and I may get some things incorrect just due to that. To my understanding, I went to try and root my phone, but beforehand I used the guides below to get my phone ready for the root (yes I do realize at this point that using these outdated guides was a clear mistake and I should have come to XDA instead). I flashed my phone to the stock kernel using the file that site provided, and then encountered the problem above. In my panic I have tried to restore the phone through several methods, but every time I try to load anything onto it with Odin, it doesn't complete until my phone restarts (and my phone won't boot up completely) so I can't get the pass message. Interestingly enough I did manage to get clockwork mod installed as that is what shows up when I try a secure boot using the methods that you described.
Ah, I am unfortunately not allowed to post links. The guides were off of Android Authority.
If there is any other information needed to help me please let me know and I will do my best to obtain it.
cabato said:
Ah, sorry about not providing enough information. Please keep in mind that I am very inexperienced and I may get some things incorrect just due to that. To my understanding, I went to try and root my phone, but beforehand I used the guides below to get my phone ready for the root (yes I do realize at this point that using these outdated guides was a clear mistake and I should have come to XDA instead). I flashed my phone to the stock kernel using the file that site provided, and then encountered the problem above. In my panic I have tried to restore the phone through several methods, but every time I try to load anything onto it with Odin, it doesn't complete until my phone restarts (and my phone won't boot up completely) so I can't get the pass message. Interestingly enough I did manage to get clockwork mod installed as that is what shows up when I try a secure boot using the methods that you described.
Ah, I am unfortunately not allowed to post links. The guides were off of Android Authority.
If there is any other information needed to help me please let me know and I will do my best to obtain it.
Click to expand...
Click to collapse
Sounds like you need to clear your cache partition and clear your dalvik cache. There are several guides on this site to help you. Choose the one that is most appropriate to what you are trying to do and follow it EXACTLY. There is one to start. Follow it from the beginning.
http://forum.xda-developers.com/showthread.php?t=2042775
When nothing else works start over from search. You cab use download mode? First make sure you got right drivers as that can mess up Odin. Use one in my Sig if you want. Then flag stock recovery with root someone nice will part a link to it I'm on my phone can't do it. Well fix your phone
Sent from my SGH-I747 using xda premium
allow rldcess
Okay now I am running into another problem. I have tried downloading the drivers from many different places and they always seem to be correctly downloaded. That being said, I can't install the drivers after I plug my phone into the computer (after downloading and installing Samsung USB drivers). Therefore, I cannot access my phone storage to put the root zip file on it. I was still able to download the custom recovery.
Now I have gone to a different computer, and the drivers seem to install correctly, but the phone still does not appear under my computer.
Edit: I do already have a root zip file on my phone from my earlier attempt, but I install it and my phone still doesn't load up. Also, Odin still recognizes the phone.
Edit 2: Windows says that the drivers cannot recognize the device. Edit 3: "Hardware ID Missing"
Bump
Sorry, I really need help for this. I can't install the MTP drivers even through using some of the tips on this site. That seems to be the problem with me accessing the phones storage from my computer. Does anyone have an ideas for what else I could do? Should I just take it to the store and hope they can fix it?
cabato said:
Okay now I am running into another problem. I have tried downloading the drivers from many different places and they always seem to be correctly downloaded. That being said, I can't install the drivers after I plug my phone into the computer (after downloading and installing Samsung USB drivers). Therefore, I cannot access my phone storage to put the root zip file on it. I was still able to download the custom recovery.
Now I have gone to a different computer, and the drivers seem to install correctly, but the phone still does not appear under my computer.
Edit: I do already have a root zip file on my phone from my earlier attempt, but I install it and my phone still doesn't load up. Also, Odin still recognizes the phone.
Edit 2: Windows says that the drivers cannot recognize the device. Edit 3: "Hardware ID Missing"
Click to expand...
Click to collapse
go to your device manager on your computer, locate samsung drivers for your device, uninstall them
restart your computer
then plug in the phone and lets it reinstall by itself
Use my drivers in my signature
They are last good damaging drivers. Don't update them but install them and plug phone in with no internet. after install plug internet in. There good stable drivers
Sent from my SAMSUNG-SGH-I747 using xda premium
Hello all, so yesterday I went on my tablet (Nexus 7 2013 WIFI ver.) and browsed the net a bit and went to sleep. I recall having around 30% battery power. This morning I wake up to an apparently flat battery (power button didn't turn on anything) so I just plugged it in and did something else. After a while, I took my tablet and started it with the power button. However, it got stuck on the Google logo and never fired up anything. I've rooted the tablet quite some time ago (months) so the cause is not from there.
Things I haven't recently done:
Installing an app.
Rooting or flashing anything.
Updating an app.
Things I have tried doing to fix the problem:
Booting into FASTBOOT then trying the recovery mode = still stuck on the Google logo.
Booting a custom recovery image using Wug's toolkit = frozen at the team logo (TWRP) / black screen (CWM).
Flash Stock + Unroot (Soft-Bricked/Bootloop) = FAILED (flash write failure).
So now I'm really stuck and desperate to make the device work again. I've been reading all day long and trying all sorts of solutions to no avail. And it seems far-fetched to me for a device like this to just instantly brick itself without any reason at all.
Can anyone help me with this case ? Or does anyone has any idea what just happened to my tablet ? :crying:
EDIT: I'm afraid that warranty might not work as the device was unlocked and rooted so it's the last solution for me.
Bumpity bump
No one has any idea what happened to the tablet and how to fix it ? I've tried doing some more flashing but to no avail. It just refuses to flash and keeps failing to write the files.
I think you need to leave out on the charger for 1/2hr without doing anything with it. You are probably using what little power it has charged by trying to reboot it, etc.
I had to do that once and it did the trick.
Sent from my Nexus 7 using XDA Free mobile app
There is no reason you should not be able to get in to recovery (power and volume down).
You could call Motorola. They have good tech support.
The exact same thing happened to me. I rooted it months ago and haven't changed a thing since then. It just froze up a few days ago. I restarted and it just gets stuck on the google screen. I can get into the bootloader, but when I try to go to recovery, the google screen comes up and won't go away. I've tried every method I can find for flashing the stock image and absolutely nothing is working. I just get stuck on the google screen.
Please update this if you find a solution!
Do u guys have the most up to date version of whatever particular recovery that you're on?
Yep. I've flashed the stock recovery multiple times to no avail. :/
nexusjas said:
Yep. I've flashed the stock recovery multiple times to no avail. :/
Click to expand...
Click to collapse
If you can't get into recovery or flash any images it sounds to me like a hardware failure. Bad memory maybe? If you've tried everything then RMA to Asus before the one year warranty runs out.
Have you tried to see if your computer sees your N7 by typing fastboot devices if you have the sdk installed?
wantabe said:
If you can't get into recovery or flash any images it sounds to me like a hardware failure. Bad memory maybe? If you've tried everything then RMA to Asus before the one year warranty runs out.
Click to expand...
Click to collapse
Not what I wanted to hear, but you're probably right. Thanks :/
nexusjas said:
Not what I wanted to hear, but you're probably right. Thanks :/
Click to expand...
Click to collapse
I was to slow with my update. Does your computer see your N7 with fastboot?
wantabe said:
I was to slow with my update. Does your computer see your N7 with fastboot?
Click to expand...
Click to collapse
Yes, I can get into the bootloader just fine and I can use fastboot. I go through the flashing process and the command prompt says everything flashed successfully, but when I restart the device, it hangs on the google logo. The same thing happens when I try to boot into recovery.
nexusjas said:
Yes, I can get into the bootloader just fine and I can use fastboot. I go through the flashing process and the command prompt says everything flashed successfully, but when I restart the device, it hangs on the google logo. The same thing happens when I try to boot into recovery.
Click to expand...
Click to collapse
If you fastboot flashed the factory image and can't boot up then it sounds like a hardware problem. Out of ideas, sorry.
wantabe said:
If you fastboot flashed the factory image and can't boot up then it sounds like a hardware problem. Out of ideas, sorry.
Click to expand...
Click to collapse
I'm not sure what happened, but I just ran this little utility again (I've done it many times over the last week or so to no avail) and it actually worked. Hopefully it keeps working!
Thanks for your help!
Pretty sure that I screwed things up pretty good and its either bricked or I think stuck in fastboot every time it turns on!! Here's what I did:
So I downloaded the newest rooted rom (51.1.4.0_514006420 updated) from aftvnews.com...
not very patient so put it on an external drive and copied it to internal sd on the FireTV...
went into CWM (6.0.5.1.4a) and tried to flash it but got an error that it failed, wiped cache/dalvik just because and rebooted...
It kept on booting into CWM and finally realized I had another file on the sd just named rom - assuming that it was the version I was on before (51.1.3...) so wiped data/factory reset and flash that...
Immediately tried to flash the 51.1.4 over that - like an idiot - and that failed again...
wiped data/factory reset and tried to flash 51.1.3 and that failed...
wiped data/factory reset and rebooted...
Now I'm stuck on white Amazon logo and cant do anything with it!!
Any ideas would be greatly appreciated!!!! Is there any way to force it into recovery when it starts up
Mike3.14159 said:
Now I'm stuck on white Amazon logo and cant do anything with it!!
Any ideas would be greatly appreciated!!!! Is there any way to force it into recovery when it starts up
Click to expand...
Click to collapse
Does anyone know if the plain white amazon logo means it's stuck in fastboot??
If so, has anyone had any luck attaching a male-to-male usb to the back and do any fastboot commands??
If I can do a "fastboot reboot recover" then I can possibly fix it from CWM...
Mike3.14159 said:
Does anyone know if the plain white amazon logo means it's stuck in fastboot??
If so, has anyone had any luck attaching a male-to-male usb to the back and do any fastboot commands??
If I can do a "fastboot reboot recover" then I can possibly fix it from CWM...
Click to expand...
Click to collapse
Have you tried this:
http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/
cd2022 said:
Have you tried this:
http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/
Click to expand...
Click to collapse
Yeah, tried that like a dozen times before I posted again last time. Seems like that will only work if you soft bricked and the rom just wont fully boot. They were talking about the 'color logo' which I'm not even getting that far - gets hung up on the initial white logo. Appreciate the try though, thanks!
Mike3.14159 said:
Yeah, tried that like a dozen times before I posted again last time. Seems like that will only work if you soft bricked and the rom just wont fully boot. They were talking about the 'color logo' which I'm not even getting that far - gets hung up on the initial white logo. Appreciate the try though, thanks!
Click to expand...
Click to collapse
To quote the CWM post...
[size=+2]If something fails to flash DO NOT reboot. Try again and/or retransfer the file over adb.[/size]
Click to expand...
Click to collapse
If your /system is corrupt, it's not gonna boot. You can try the sysrq trick, but I don't think anyones ever been able to make that work with a bad /system.
Not sure what the 'sysrq' trick is but I will look it up and see what I can do, thanks! Saw on aftvnews late yesterday that the newest ota - after being rooted - did something crazy to yours so was actually waiting to see what had happened to yours and if you were able to get it back right then was hoping I could maybe learn some trick from that haha
Have you managed to fix this? i'm also stuck on the white logo
Looks like white logo without going to the colored logo means hard brick. Any USB attached will not work. There is no power coming out.
I wonder if there is a way to open up the unit and reflash the hardware from there.