Related
[FYI: I don't a thing about tech stuff, but I can follow directions well enough if they're spelled out for me.]
I rooted my KF the day I got it using KF Utility. I don't remember what I did, and I certainly didn't understand much of it; I just followed the steps. That was several months ago (in December), and I haven't messed around with anything since. Everything worked fine, no problems. Haven't made any significant changes in months.
Then today, I tried to turn it on; the power light went on and the words "kindle fire" flashed for a second -- and then both disappeared. I connected it to a charger, and the same thing happened -- both, even the power light, disappeared after a second.
Same thing happens when I tried to connect it to my computer -- and my computer won't even recognize that it's there.
[It's now been connected to a wall charge for several hours, but the power light's not even glowing.]
What do I do? Is it "bricked"? And if so, how do I "unbrick" it, especially if my computer can't even recognize it?
Thank you in advance!
KF won't start, charge, or connect to PC
Absurd1 said:
[FYI: I don't a thing about tech stuff, but I can follow directions well enough if they're spelled out for me.]
I rooted my KF the day I got it using KF Utility. I don't remember what I did, and I certainly didn't understand much of it; I just followed the steps. That was several months ago (in December), and I haven't messed around with anything since. Everything worked fine, no problems. Haven't made any significant changes in months.
Then today, I tried to turn it on; the power light went on and the words "kindle fire" flashed for a second -- and then both disappeared. I connected it to a charger, and the same thing happened -- both, even the power light, disappeared after a second.
Same thing happens when I tried to connect it to my computer -- and my computer won't even recognize that it's there.
[It's now been connected to a wall charge for several hours, but the power light's not even glowing.]
What do I do? Is it "bricked"? And if so, how do I "unbrick" it, especially if my computer can't even recognize it?
Thank you in advance!
Click to expand...
Click to collapse
If you have the FIREFIREFIRE logo I hope this will help.
1. Make sure you still have the driver installed for you KF from KindleFireUtitly.
2. Open command prompt
3. change directory
cd C:\KindleADB
4. Check and see if adb services are running
adb devices
It will not come back with any device running and that is ok.
5. Look in the KINDLEFIREUTITLY folder for a bat file named Run.bat
double click and hit run and it will open a red command prompt.
After it has ran just a few short seconds it will give you a few number prompts. Chose number 5. and reboot Kindle and it will reinstall TWRP for you. These steps will also help if you ever get stuck in FIREFIREFIRE logo again.
I really hope this helps.
Thanks,
JohninLex
JohninLex said:
If you have the FIREFIREFIRE logo I hope this will help.
1. Make sure you still have the driver installed for you KF from KindleFireUtitly.
2. Open command prompt
3. change directory
cd C:\KindleADB
4. Check and see if adb services are running
adb devices
It will not come back with any device running and that is ok.
5. Look in the KINDLEFIREUTITLY folder for a bat file named Run.bat
double click and hit run and it will open a red command prompt.
After it has ran just a few short seconds it will give you a few number prompts. Chose number 5. and reboot Kindle and it will reinstall TWRP for you. These steps will also help if you ever get stuck in FIREFIREFIRE logo again.
I really hope this helps.
Thanks,
JohninLex
Click to expand...
Click to collapse
Well, like I said, I don't know much about any of this stuff, but here's what I can tell you:
I don't have FIREFIREFIRE. Not really sure what that is, but it's certainly never been on my Kindle.
What I did try doing was following those steps in Kindle Fire Utility anyway. I can get it to the point where it says:
ADB Status: Online
ADB Rooted: No
Boot Status Unknown
If from there I hit 5 (to "install latets TWRP recovery"), I get a whole bunch of
"The system cannot find the path specified." for each step it goes through, until finally it gets here:
"If we get stuck here a long time, check the ADB drivers in windows.
Fastboot uses a different device than ADB, so make sure it is installed as an
ADB device. If you see "kindle" in device manager, you need to install the
drivers. You can also try running install_drivers.bat in the drivers folder.
Do NOT unplug the kindle if we are stuck here, leave it plugged in and on.
Do NOT touch the kindle at all if we are stuck.
Setting Normal Bootmode.
Please wait..."
To reiterate again -- I don't know what any of this ADB stuff is, where to find it, etc.
We are in the same boat. Was messing around w/ someone's Bare Bones CM7, and as per instructions, clicked wipe SYSTEM, and since then my device has been with screen "on" but black; non response to power button weather plugged on AC adapter or USB. Will have to research the forums tomorrow (cant find search function now) and let you know if I find a fix and please do the same if you find something first.
Sincerely,
-RM
---------- Post added at 08:49 AM ---------- Previous post was at 08:37 AM ----------
Actually --- I've just resolved the issue.
I had it plugged into the computer (still unresponsive), held down the power button for about 25 seconds, heard the computer do the "tuh-rup" sound, prayed, could finally stop seeing the "black screen" while on, it was pure black due to it powering off. After it was off, I powered back up and was able to get back into TWRP. Restored, did not wipe system and presto... hopefully you can get yours fixed.
theartofbone said:
Actually --- I've just resolved the issue.
I had it plugged into the computer (still unresponsive), held down the power button for about 25 seconds, heard the computer do the "tuh-rup" sound, prayed, could finally stop seeing the "black screen" while on, it was pure black due to it powering off. After it was off, I powered back up and was able to get back into TWRP. Restored, did not wipe system and presto... hopefully you can get yours fixed.
Click to expand...
Click to collapse
Nope, that's not doing anything for me. My kindle won't power on. All it does is display "Kindle Fire" for one second, then go dead.
Does anyone have ANY advice?
oundsde good
Try a different charger and plug into the wall for a little while.
_Justin said:
Try a different charger and plug into the wall for a little while.
Click to expand...
Click to collapse
Tried that. No luck.
Do you have a chat program, or google talk? I'll help you out.
_Justin said:
Do you have a chat program, or google talk? I'll help you out.
Click to expand...
Click to collapse
..........
My device has the same issue, it powers down as soon as I connect it to a PC or charger. The interesting thing, that it is charging, but the led is dark. When I take it off the charger the next day, it boots up and fully charged. (when I connect a cable again it shuts down immediately)
If you find out something I would be also interester. (I've also rooted before 6.2, than I've lost root, than after I while I've faced these issues)
Alright, unless any folks have any other advice, I'm gonna go ahead and contact Amazon for a return.
try to charge it with the wall charger for some hours - check the charger - should have ~1.8A - maybe the orange light is showing up after half an hour
try to power it off by holding pwr ~20sec to allow better charging - if you can't let it on the charger - try to power it off later (eg after an hour)
look here about charger spec and contact problems:
http://forum.xda-developers.com/showthread.php?p=23035482#post23035482
some had success with a factory cable:
http://forum.xda-developers.com/showthread.php?p=23034046#post23034046
I've searched and found a few similar (not identical) problems that people were having, and tried some of the solutions, and none have worked.
I'm trying to fix this stock Acer A500 for a friend. It will boot up part way, goes past the acer screen and android screen, but then stops at a black screen with 'android system' in the upper left corner, the home and back buttons in the bottom left, and the time, signal, and battery life logos in the bottom right. Then there's the Power Off thing in the center of the screen, and it says shutting down but it never shuts down.
I boot into the stock recovery mode, and it says in the upper left on the acer screen:
erasing cache before SD update
SD update cmd: recovery
--update_package=sdcard:update.zip
booting recovery kernel image
then it shows the android with the turning gears, then goes straight to the android with the warning symbol.
Since I can't get into the OS, i have no idea which version or specific model this is, but i downloaded a few different honeycomb update.zips, and put those on the SD card, and when i tried booting with those, the loading bar pops up under the android logo, and it goes to about 1/3 of completion before switching back to the warning symbol.
I tried downloading what im pretty sure was a full version of jellybean for this tablet, and it went straight to the warning symbol, no loading bar. same when i tried renaming the file update.zip >.>
im clearly very new to all this, but i'd really like to get this thing working.
is there a way to do a factory reset without booting all the way into the OS?
im not sure because it seems like the only file its looking for in recovery mode is update.zip.
if anyone has any bright ideas, id appreciate the help.
Also, not sure if this is relevant, but when i boot it normally, and it goes to the 'shutting down' screen, the battery level indicator says its almost dead, but i can leave it plugged in for hours and nothing changes at all.
EDIT: Also, it won't even boot if the power cable is not connected.
Similar issue hope there is a solution
I have a similar problem. Tablet was working fine, sitting on docking station. Returned to it the next day and when I went to wake it, it would not wake. Rebooted it but will not reboot. Sits on the ANDROID screen after the ASUS title screen indefinitely. If I try and boot into recovery it fails at "update.zip" and I see the broken Android image laying there.
Is there a means to restore it from PC via the usb cable and can someone please post a very noob friendly walk through step-by-step?
Greatly appreciate any positive advice!
Probably the mmc failed. Same symptoms as mine. Non-recoverable.
Sent from my GT-N8000 using Tapatalk HD
zardoz99 said:
Probably the mmc failed. Same symptoms as mine. Non-recoverable.
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
So, dead chip? So soon? Nice.
NoOneSpecific said:
So, dead chip? So soon? Nice.
Click to expand...
Click to collapse
Yep.. 14 months old in my case. Contacted Acer and said "what about a fix?" They said, "no chance unless you cross our palms with lots of silver."
So, bought a Samsung Note 10.1 instead. Acer can "stuff it". I won't be buying a tablet from them again. Considering that I bought their "flagship" product of the A501 with the 64GB memory, this is truly unacceptable.
I was incredibly careful with it and certainly never did anything to void the warranty. But, you only get 12 months and then it's over.
NoOneSpecific said:
So, dead chip? So soon? Nice.
Click to expand...
Click to collapse
I wouldn't go as far as to say dead, have you tried booting into APX mode and then running BABsector?
skurtov said:
I wouldn't go as far as to say dead, have you tried booting into APX mode and then running BABsector?
Click to expand...
Click to collapse
Definitely more than I can manage but I've handed the tablet over to a friend who is capable of understanding and performing your suggestions. All are greatly appreciated.
Thanks!
NoOneSpecific said:
Definitely more than I can manage but I've handed the tablet over to a friend who is capable of understanding and performing your suggestions. All are greatly appreciated.
Thanks!
Click to expand...
Click to collapse
Certainly if your friends wants a point in the right direction have him post here or pm
Sent from my Transformer Prime TF201 using Tapatalk HD
skurtov said:
Certainly if your friends wants a point in the right direction have him post here or pm
Sent from my Transformer Prime TF201 using Tapatalk HD
Click to expand...
Click to collapse
I'll have him PM you when he is able.
Thanks!
skurtov said:
Certainly if your friends wants a point in the right direction have him post here or pm
Sent from my Transformer Prime TF201 using Tapatalk HD
Click to expand...
Click to collapse
Hey Skurtov,
Thanks for the offer to help my friend NoOneSpecific.
If my Android terminology is correct, APX mode is the diagnostic mode which invokes the Bootloader when a device specific combination is held while powering on, right? And while the Bootloader GUI is active, it is shown on a PC as an Nvidia device?
I believe the key combination on the A500 is Volume-Down and Power, but doing this causes the tablet to automatically boot from the recovery kernel image. The same message appears regardless of whether an SD card with a decrypted update.zip is present or not.
If I am mistaken, I would greatly appreciate your help in pointing me to the right step in getting my friend's tablet working again!
Cheers!
coluwyvurne said:
Hey Skurtov,
Thanks for the offer to help my friend NoOneSpecific.
If my Android terminology is correct, APX mode is the diagnostic mode which invokes the Bootloader when a device specific combination is held while powering on, right? And while the Bootloader GUI is active, it is shown on a PC as an Nvidia device?
I believe the key combination on the A500 is Volume-Down and Power, but doing this causes the tablet to automatically boot from the recovery kernel image. The same message appears regardless of whether an SD card with a decrypted update.zip is present or not.
If I am mistaken, I would greatly appreciate your help in pointing me to the right step in getting my friend's tablet working again!
Cheers!
Click to expand...
Click to collapse
You are quite right sir, however the button combination I am most familiar with is holding the power and the reset button (the one you have to stick the paper clip in) when you first start it up. It should then either say APX mode on the screen or be blank, either way the computer will identify it as a APX device and automatically install the drivers.
Going into APX MODE manualy
You enter APX mode by holding down the Reset button(with paper clip). Do not release it. Hold down power for 3 secs and then release it. After another second, release the reset button.
Your Windows PC should then detect your device and install the APX driver. You should then have an APX USB device installed. If you do not have an APX USB device listed in your system tray, you cannot proceed.
The screen of your tablet is black.
Quoted from Civato
Click to expand...
Click to collapse
The next course of action is to get the SBK, from what it sounds like the tablet didn't write a partition properly and that's why it's not booting. So what you can do is wipe out the partitions and install a custom bootloader and recovery. Not only does it fix things but it also opens up his world to custom roms . Okay, back to the matter at hand, I don't know if he has his SBK or not, and if he does skip the step to find it and just run babsector below. If not then follow the next step.
You'll have to pull the UID from the tablet using this method described here:
http://git.pappkartong.se/?p=a500/apxuid.git;a=snapshot;h=HEAD;sf=tgz
There's a readme
After getting the UID and calculating your SBK you'll just go to the next step.
All credit goes to user eppeP.
Click to expand...
Click to collapse
Run this file hosted here:
http://narod.ru/disk/53919831001.a235ea2225f319015f30c009629d2075/BabSector.rar.html
And this file basically rewrites and formats the partitions out installs a custom bootloader and recovery
Credit goes to Danny2 for finding this and posting it.
Click to expand...
Click to collapse
Once this is done, pick a new rom. I prefer the Civato ones, load it on a SD, boot to recovery, erase dalvik cache, cache, do a factory reset wipe (from the recovery menu!), then wipe system, flash the rom and go on your merry way
Many thanks for the reply.
As per your instructions, I have booted the tablet into APX mode. However, as I do not know the UID of the device, I've had to try to run the utilities to create a driver for the device and then pull UID from the tablet...
I am able to create the driver for the device and install it with driver signing off in Windows, but I can't figure out how to run the script to get the UID. I notice the file in the package you directed me to contains an .SLN file, which would indicate it is a programming solution file. I have Visual Studio on my system but it cannot open this particular .SLN file.
How would I run what's in the package to pull out the UID of the tablet?
Any help getting past this hurdle would be much appreciated!
Hey there.
I flashed a new ROM (Kaos Droid 7.0.0) and the fitting gapps some minutes ago from CWM Touch. Everything worked as supposed, no errors, no warnings, nothing. Then I rebooted the Nexus 7 and now it's stuck in the worst bootloop I have seen so far:
The Google Screen appears, stays for some seconds, then I see a screen with the CWM Logo and the text "ClockworkmodRecovery 6.0.38", after this the device seems to reboot and the sequence starts from the beginning again.
I can not get into recovery, I can connect to my PC via USB but connection and disconnection happens every few seconds (because of the bootloop).
I guess that's it for my Nexus 7 or does anyone have an idea what I can try to do. I'd be really thankful.
Jagutherrschaften said:
Hey there.
I flashed a new ROM (Kaos Droid 7.0.0) and the fitting gapps some minutes ago from CWM Touch. Everything worked as supposed, no errors, no warnings, nothing. Then I rebooted the Nexus 7 and now it's stuck in the worst bootloop I have seen so far:
The Google Screen appears, stays for some seconds, then I see a screen with the CWM Logo and the text "ClockworkmodRecovery 6.0.38", after this the device seems to reboot and the sequence starts from the beginning again.
I can not get into recovery, I can connect to my PC via USB but connection and disconnection happens every few seconds (because of the bootloop).
I guess that's it for my Nexus 7 or does anyone have an idea what I can try to do. I'd be really thankful.
Click to expand...
Click to collapse
Hi, Jagutherrschaften...
Try pressing VOLUME DOWN + THE POWER ON KEY and HOLD BOTH for 30 seconds (or as long as it takes to break out of the 'bootloop').
(or BOTH VOL KEYS + POWER ON if the above doesn't work... although it should).
Keep them pressed until you boot you into the bootloader....
You should now be free to run fastboot commands, to either fastboot flash back to factory stock... or you could attempt to just boot into recovery, and maybe do a Nandroid Backup restore from your previous setup (assuming of course, you created one).
Anyway... as long as you can still access the bootloader... all is not lost.
Rgrds,
Ged.
GedBlake said:
Hi, Jagutherrschaften...
Try pressing VOLUME DOWN + THE POWER ON KEY and HOLD BOTH for 30 seconds (or as long as it takes to break out of the 'bootloop').
(or BOTH VOL KEYS + POWER ON if the above doesn't work... although it should).
Keep them pressed until you boot you into the bootloader....
You should now be free to run fastboot commands, to either fastboot flash back to factory stock... or you could attempt to just boot into recovery, and maybe do a Nandroid Backup restore from your previous setup (assuming of course, you created one).
Anyway... as long as you can still access the bootloader... all is not lost.
Rgrds,
Ged.
Click to expand...
Click to collapse
Sorry, I forgot to mention that I can't boot into bootloader. I tried every single combination of keys. The bootloop goes on and is completely unimpressed by my keypresses. Bad bad thing.
Jagutherrschaften said:
Sorry, I forgot to mention that I can't boot into bootloader. I tried every single combination of keys. The bootloop goes on and is completely unimpressed by my keypresses. Bad bad thing.
Click to expand...
Click to collapse
How fast is the bootloop? and how long are you pressing the buttons for?
Lean on them, as it where, for a good minute or so... the device has to pick up the 'interrupts' sooner or later.
Rgrds,
Ged.
GedBlake said:
How fast is the bootloop? and how long are you pressing the buttons for?
Lean on them, as it where, for a good minute or so... the device has to pick up the 'interrupts' sooner or later.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thank you for your answers. I tried every combination and kept the keys pressed for 2 mins. Nothing. The only thing I can actually do is shut the device down by pressing POWER + VOL UP for a long while.
If bootloop doesnt stop and you cant get into bootloader....then just long press power button..that should stop the cycle...and then volm down plus power button....should get u into bootloader..atleast worked for me..
Sent from my Nexus 7 using xda app-developers app
Now here is what it looks like (doesn't matter if I press keys or not): https://dl.dropboxusercontent.com/u/12668781/Nexus7_bootloop.mkv
The normal method you described neo45215 doesn't work for me as well.
Jagutherrschaften said:
Thank you for your answers. I tried every combination and kept the keys pressed for 2 mins. Nothing. The only thing I can actually do is shut the device down by pressing POWER + VOL UP for a long while.
Here is a video what it looks like (if I press keys or not or keep keys pressed or not doesn't matter):
www.michi-fehr.de/Nexus7_bootloop.mkv
(Sorry, youtube messes with me as well. Seems not to be my day today.)
Click to expand...
Click to collapse
Mmm... this is a strange one...
Just had a look a your video... and I've seen a few bootoops, but never one involving a Custom Recovery and ONLY the Bootloader Unlock screen (yes, that is the Bootloader - it's just not normally recognized as such, because it's not in FASTBOOT mode).
If you've shutdown the tablet by pressing VOL UP + POWER ON, you've effectively booted the device into APX mode (it looks like it's shutdown, but it isn't) - if it is in APX mode, the device is now awaiting for you to run some nvFlash commands, which currently can't be done (though there is now, a very specific exception, which is not applicable here).
I agree with the previous poster, @neo45215, VOLUME DOWN (hold), then POWER BUTTON, (whilst still holding VOLUME DOWN), should boot you into the bootloader... but I think precise timing is required. Please read the following, carefully, several times.
----------------------------------------
QUOTE from http://forum.xda-developers.com/showthread.php?t=2133986
"Starting from booted or boot-looping OS:
Power (10-15 seconds) -> Normal OS Boot**
** Bootloader Interrupt: In any of the cases where you hold the power button down to try to break out of the current operating mode, if you press the Vol-Down button right after you first see the black and white screen with the Google logo, the tablet will proceed immediately to bootloader/fastboot mode, rather than booting the normal OS. You need to be ready though - you only get about 1 or 2 seconds to do this! (Thanks to RMXO for pointing this out) Note that this means you can get to the bootloader directly from any other mode!
This also explains why, when attempting a cold start using Vol-Down + Power, if you accidentally let go of the vol-down button when the screen first lights up, the Nexus 7 will boot to the normal OS. In this case, pressing Vol-Down initially is actually superfluous - what makes the device go into bootloader/fastboot mode is the Vol-Down press immediately following the google splash screen - there actually is no unique "Go to fastboot from a cold start" method."
----------------------------------------
I'm at loss to suggest anything more helpful... this looks like the bootloop from hell! But I'm convinced, that with the correct timing and persistence, some key-combo interrupt could break the Nexus 7 out of it.
Rgrds,
Ged.
GedBlake said:
Mmm... this is a strange one...
Just had a look a your video... and I've seen a few bootoops, but never one involving a Custom Recovery and ONLY the Bootloader Unlock screen (yes, that is the Bootloader - it's just not normally recognized as such, because it's not in FASTBOOT mode).
If you've shutdown the tablet by pressing VOL UP + POWER ON, you've effectively booted the device into APX mode (it looks like it's shutdown, but it isn't) - if it is in APX mode, the device is now awaiting for you to run some nvFlash commands, which currently can't be done (though there is now, a very specific exception, which is not applicable here).
I agree with the previous poster, @neo45215, VOLUME DOWN (hold), then POWER BUTTON, (whilst still holding VOLUME DOWN), should boot you into the bootloader... but I think precise timing is required. Please read the following, carefully, several times.
----------------------------------------
QUOTE from http://forum.xda-developers.com/showthread.php?t=2133986
"Starting from booted or boot-looping OS:
Power (10-15 seconds) -> Normal OS Boot**
** Bootloader Interrupt: In any of the cases where you hold the power button down to try to break out of the current operating mode, if you press the Vol-Down button right after you first see the black and white screen with the Google logo, the tablet will proceed immediately to bootloader/fastboot mode, rather than booting the normal OS. You need to be ready though - you only get about 1 or 2 seconds to do this! (Thanks to RMXO for pointing this out) Note that this means you can get to the bootloader directly from any other mode!
This also explains why, when attempting a cold start using Vol-Down + Power, if you accidentally let go of the vol-down button when the screen first lights up, the Nexus 7 will boot to the normal OS. In this case, pressing Vol-Down initially is actually superfluous - what makes the device go into bootloader/fastboot mode is the Vol-Down press immediately following the google splash screen - there actually is no unique "Go to fastboot from a cold start" method."
----------------------------------------
I'm at loss to suggest anything more helpful... this looks like the bootloop from hell! But I'm convinced, that with the correct timing and persistence, some key-combo interrupt could break the Nexus 7 out of it.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks a lot for your help, I have tried everything, I can't get anywhere... neither bootloader nor recovery.
Additionally I can't make the device do anything I want by adb.
And as a "bonus" I can't send my Nexus7 to repair because this stupid bootloop shows "ClockworkMod Recovery v6.0.3.8" :silly:
Jagutherrschaften said:
Thanks a lot for your help, I have tried everything, I can't get anywhere... neither bootloader nor recovery.
Additionally I can't make the device do anything I want by adb.
And as a "bonus" I can't send my Nexus7 to repair because this stupid bootloop shows "ClockworkMod Recovery v6.0.3.8" :silly:
Click to expand...
Click to collapse
Really sorry to hear this... it is baffling:.
I've been hanging around on XDA since January, and I've come across a lot of weird behaviour, reported by other posters. But this is something that is outside my experience.
A few questions... (no guarantees, but I'll try to see if I can come up with something)...
Can you post download links for EVERYTHING you've flashed...
The ROM, the Gapps, the CWM recovery.
Also, what order did you flash them in?
Did you use fastboot? or a Toolkit at any time?
Where you rooted BEFORE you embarked on this endeavour?
How did you acquire root?
How long have you had the Nexus 7?
Is it a WiFi only model or a WiFi and 3G model?
Have you flashed any other Custom ROMs prior to this one?
If, so, any problems?
Do you know your current bootloader version number?
What was the battery status (percentage) prior to you flashing this ROM?
Sorry for all the questions... but something, some tiny litlle detail, might set a 'eureka!' light bulb off in my head.
Rgrds,
Ged.
GedBlake said:
Really sorry to hear this... it is baffling:.
I've been hanging around on XDA since January, and I've come across a lot of weird behaviour, reported by other posters. But this is something that is outside my experience.
A few questions... (no guarantees, but I'll try to see if I can come up with something)...
Can you post download links for EVERYTHING you've flashed...
The ROM, the Gapps, the CWM recovery.
Also, what order did you flash them in?
Did you use fastboot? or a Toolkit at any time?
Where you rooted BEFORE you embarked on this endeavour?
How did you acquire root?
How long have you had the Nexus 7?
Is it a WiFi only model or a WiFi and 3G model?
Have you flashed any other Custom ROMs prior to this one?
If, so, any problems?
Do you know your current bootloader version number?
What was the battery status (percentage) prior to you flashing this ROM?
Sorry for all the questions... but something, some tiny litlle detail, might set a 'eureka!' light bulb off in my head.
Rgrds,
Ged.
Click to expand...
Click to collapse
OK, I'll try to answer as detailed as possible:
ROM KaosDroid7.0.0
FittingGApps
CWM Recovery (Touch) was installed through ROM Manager Premium
The order of what I did was: I made a backup in Titanium Backup Pro, then I made a nandroid backup by ROM Manager Premium. I went to recovery, wiped /cache and /data, then flashed KaosDroid7.0.0, flashed GApps and rebooted. After my Nexus7 had fully booted I restored some user apps and settings via Titanium Backup Pro. I had to reboot. After that I explored that clock was force closed whenever I tried to access the alarm clock. I wondered if I could possibly have overseen a checkmark when restoring with Titanium Backup Pro (maybe forgotten to untick a system app or setting) which could lead to the force close. So I decided to start over again.
This time I thought about using ROM Manager Premium for wiping and flashing. I started the app and it told me there was an update for CWM Recovery. So I installed this update through ROM Manager Premium - CWM Recovery Touch 6.0.3.8. I rebooted and went to recovery to flash ROM and GApps again the normal way. Before flashing I wiped /cache and /data again. Everything went fine until I rebooted the tablet and found myself in this "bootloop of hell" as you called it... After having tried a lot to break it, I opened the Nexus7 to remove battery for the first time.
OK, now the other questions:
I bought my Nexus7 about 11 months ago, it's the 16 GB WiFi only version. I aquired root by using this Toolkit and everything went really smooth. I tried several ROMs yes, after some time I came across KaosDroid (don't exactly know which version I started with, maybe v5.0.0) and really liked it. I flashed a new version whenever there was one and never had any problems before.
I am not sure about my current bootloader version, I have some not too long ago nandroid backups on my PC, can I find out anywhere in there? About battery, it was 55 % or so before I started flashing, maybe even more.
The way I see this is: It looks like ROM Manager has messed something up. I have never seen a screen like the ROM Manager screen that occurs in the bootloop right after the Google screen before. Unless maybe when making a nandroid backup through ROM Manager, not sure about this. But it shouldn't be there in a normal boot sequence as far as I understand it.
The only way I can access my Nexus7 is via USB on my PC. And I have like 5 seconds to act while this ROM Manager screen is on, that's the time frame when my PC says "Nexus7 connected" and even the Toolkit finds the device and says it's in "ADB mode", then prints the serial number, but sadly after that it waits for the device to enter adb mode forever.
EDIT: And of course I can get access in APX mode, but from what I have read there is no way to do anything because commands etc. to install a new bootloader are not known (yet?).
Thanks a lot for your help and patience, it actually helps to know there is someone who reads this :good:.
It's not the end of the world if I can't reanimate my Nexus7 but it served me so well for almost a year and I really like it .
Jagutherrschaften said:
OK, I'll try to answer as detailed as possible:
ROM KaosDroid7.0.0
FittingGApps
CWM Recovery (Touch) was installed through ROM Manager Premium
The order of what I did was: I made a backup in Titanium Backup Pro, then I made a nandroid backup by ROM Manager Premium. I went to recovery, wiped /cache and /data, then flashed KaosDroid7.0.0, flashed GApps and rebooted. After my Nexus7 had fully booted I restored some user apps and settings via Titanium Backup Pro. I had to reboot. After that I explored that clock was force closed whenever I tried to access the alarm clock. I wondered if I could possibly have overseen a checkmark when restoring with Titanium Backup Pro (maybe forgotten to untick a system app or setting) which could lead to the force close. So I decided to start over again.
This time I thought about using ROM Manager Premium for wiping and flashing. I started the app and it told me there was an update for CWM Recovery. So I installed this update through ROM Manager Premium - CWM Recovery Touch 6.0.3.8. I rebooted and went to recovery to flash ROM and GApps again the normal way. Before flashing I wiped /cache and /data again. Everything went fine until I rebooted the tablet and found myself in this "bootloop of hell" as you called it... After having tried a lot to break it, I opened the Nexus7 to remove battery for the first time.
OK, now the other questions:
I bought my Nexus7 about 11 months ago, it's the 16 GB WiFi only version. I aquired root by using this Toolkit and everything went really smooth. I tried several ROMs yes, after some time I came across KaosDroid (don't exactly know which version I started with, maybe v5.0.0) and really liked it. I flashed a new version whenever there was one and never had any problems before.
I am not sure about my current bootloader version, I have some not too long ago nandroid backups on my PC, can I find out anywhere in there? About battery, it was 55 % or so before I started flashing, maybe even more.
The way I see this is: It looks like ROM Manager has messed something up. I have never seen a screen like the ROM Manager screen that occurs in the bootloop right after the Google screen before. Unless maybe when making a nandroid backup through ROM Manager, not sure about this. But it shouldn't be there in a normal boot sequence as far as I understand it.
The only way I can access my Nexus7 is via USB on my PC. And I have like 5 seconds to act while this ROM Manager screen is on, that's the time frame when my PC says "Nexus7 connected" and even the Toolkit finds the device and says it's in "ADB mode", then prints the serial number, but sadly after that it waits for the device to enter adb mode forever.
EDIT: And of course I can get access in APX mode, but from what I have read there is no way to do anything because commands etc. to install a new bootloader are not known (yet?).
Thanks a lot for your help and patience, it actually helps to know there is someone who reads this :good:.
It's not the end of the world if I can't reanimate my Nexus7 but it served me so well for almost a year and I really like it .
Click to expand...
Click to collapse
Hello again, Jagutherrschaften...
Sorry for taking so long to get back to you, but I've been really busy with non-Android stuff all day.
Before I signed off XDA early this morning, (Fri, UK time)... and before you posted your explanation of how you got into your undesirble predicament, I was trying to think why your Nexus 7 is attempting to boot into CWM. It's something I've never seen before... it occurred to me, CWM may have been incorrectly flashed to the boot partition, instead of the recovery partition. This would go some way to explaining why your Nexus 7 is attempting to boot into CWM instead of normal Android.
So in an attempt to replicate your situation, I fastboot flashed CWM on my Nexus 7, to the boot partition with...
Code:
fastboot flash boot recovery-clockwork-touch-6.0.3.8-grouper.img
...instead of (and correctly)...
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.3.8-grouper.img
Upon completion of this flash, I hit START (from the bootloader)... and as expected my Nexus 7 booted into the Google logo, and then directly into CWM.
...but it didn't bootloop as depicted in your video, it just ran CWM as normal..
I booted several times into CWM, but no bootloop. (It's kind of weird having two custom recoveries installed... there's an option in CWM to restart Recovery, which upon tapping, my N7 booted straight into TWRP !, which is my Custom Recovery of choice. And resides correctly in the recovery partition. I had to make a conscious effort to reboot as normal, in order to boot into CWM).
Anyway, more puzzled more than ever, I fastboot flashed the Jellybean 4.3 stock boot .img back to it's rightful place, rebooted the tablet, to make sure everything was working as normal, and went to bed.
Later, after you posted, I re-read it many times (and took a look at the links), and re-watched your video several more times (by the way, Nandroid backups don't backup the bootloader), and nothing occurred to me; no 'euraka' ! moment.
The bootloader is obviously still intact... if it wasn't, then your Nexus 7 wouldn't boot at all. Besides, it's there, visible, with the unlocked padlock symbol !
I'm inclined to tentatively agree with your assessment that ROM Manager screwed something up. I haven't used ROM Manager for ages, due to known issues on my Advent Vega. And on the Nexus 7, I just use fastboot. On the Vega, you use a command called flash_image to flash images, and is syntactically very similar to fastboot.
Sticking with my Vega for a moment... some users are unable to boot into CWM at all. And nobody seems to know why. But a while ago, somebody did some research into this problem, and it was speculated that on some Vegas there are BAD NAND BLOCKS (like bad sectors on a hard drive, only on a chip instead) in the MISC partition, where a binary state flag is set, telling the tablet to boot into Recovery instead of Android.
Now it's a bit a leap... and hugely speculative... but I wonder if the MISC partition on your Nexus 7 may have become corrupted... ?POSSIBLY? as a result of using ROM Manager... and that is telling the tablet to boot into Recovery instead of Android.
This is a far from satisfactory explanation, though, for several reasons...
* I'm not sure how far you can extrapolate the partition structures of one completely different tablet to another completely different tablet.
* It doesn't explain why your tablet is bootlooping and mine didn't (after replacing the stock boot.img with the CWM recovery .img in the boot partition.
* And finally... I'm still baffled why VOL DOWN+POWER ON doesn't break out of the bootloop and boot directly into the bootloader. Everything I know about the Nexus 7 tells me that this should happen... and it's always been the case, that as long as you can access the bootloader, the tablet is recoverable.
I'm afraid I have nothing else to suggest or try... other than what you've tried already.
I can only offer my apologies that I was unable to assist you... maybe somebody with more technical expertise might offer some new insight or suggestions.
Rgrds,
Ged.
GedBlake said:
Hello again, Jagutherrschaften...
Sorry for taking so long to get back to you, but I've been really busy with non-Android stuff all day.
Before I signed off XDA early this morning, (Fri, UK time)... and before you posted your explanation of how you got into your undesirble predicament, I was trying to think why your Nexus 7 is attempting to boot into CWM. It's something I've never seen before... it occurred to me, CWM may have been incorrectly flashed to the boot partition, instead of the recovery partition. This would go some way to explaining why your Nexus 7 is attempting to boot into CWM instead of normal Android.
So in an attempt to replicate your situation, I fastboot flashed CWM on my Nexus 7, to the boot partition with...
Code:
fastboot flash boot recovery-clockwork-touch-6.0.3.8-grouper.img
...instead of (and correctly)...
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.3.8-grouper.img
Upon completion of this flash, I hit START (from the bootloader)... and as expected my Nexus 7 booted into the Google logo, and then directly into CWM.
...but it didn't bootloop as depicted in your video, it just ran CWM as normal..
I booted several times into CWM, but no bootloop. (It's kind of weird having two custom recoveries installed... there's an option in CWM to restart Recovery, which upon tapping, my N7 booted straight into TWRP !, which is my Custom Recovery of choice. And resides correctly in the recovery partition. I had to make a conscious effort to reboot as normal, in order to boot into CWM).
Anyway, more puzzled more than ever, I fastboot flashed the Jellybean 4.3 stock boot .img back to it's rightful place, rebooted the tablet, to make sure everything was working as normal, and went to bed.
Later, after you posted, I re-read it many times (and took a look at the links), and re-watched your video several more times (by the way, Nandroid backups don't backup the bootloader), and nothing occurred to me; no 'euraka' ! moment.
The bootloader is obviously still intact... if it wasn't, then your Nexus 7 wouldn't boot at all. Besides, it's there, visible, with the unlocked padlock symbol !
I'm inclined to tentatively agree with your assessment that ROM Manager screwed something up. I haven't used ROM Manager for ages, due to known issues on my Advent Vega. And on the Nexus 7, I just use fastboot. On the Vega, you use a command called flash_image to flash images, and is syntactically very similar to fastboot.
Sticking with my Vega for a moment... some users are unable to boot into CWM at all. And nobody seems to know why. But a while ago, somebody did some research into this problem, and it was speculated that on some Vegas there are BAD NAND BLOCKS (like bad sectors on a hard drive, only on a chip instead) in the MISC partition, where a binary state flag is set, telling the tablet to boot into Recovery instead of Android.
Now it's a bit a leap... and hugely speculative... but I wonder if the MISC partition on your Nexus 7 may have become corrupted... ?POSSIBLY? as a result of using ROM Manager... and that is telling the tablet to boot into Recovery instead of Android.
This is a far from satisfactory explanation, though, for several reasons...
* I'm not sure how far you can extrapolate the partition structures of one completely different tablet to another completely different tablet.
* I't doesn't explain why your tablet is bootlooping and mine didn't (after replacing the stock boot.img with the CWM recovery .img in the boot partition.
* And finally... I'm still baffled why VOL DOWN+POWER ON doesn't break out of the bootloop and boot directly into the bootloader. Everything I know about the Nexus 7 tells me that this should happen... and it's always been the case, that as long as you can access the bootloader, the tablet is recoverable.
I'm afraid I have nothing else to suggest or try... other than what you've tried already.
I can only offer my apologies that I was unable to assist you... maybe somebody with more technical expertise might offer some new insight or suggestions.
Rgrds,
Ged.
Click to expand...
Click to collapse
Hey again GedBlake.
The last thing you have to do is apologize for helping me a lot, reading through all my text and making things clear for me. And even more you flashed stuff to your device to test if my situation can be reproduced - good that it's not . You've spent a lot of free time just to help, that's really great :good:.
With my bootloader still being intact and the device being recognized by my PC I wonder if maybe I can manage to fastboot flash a different bootloader and/or a new recovery which might maybe break the silly loop when booting. That's my only idea left but if the bootloader isn't in fastboot mode at some time during the loop this won't work too. But I'll give it a try, it's better than cutting tomatoes on my Nexus7 :laugh:.
Thank you very much for your help. If there is anything worth reporting I will of course.
Jagutherrschaften said:
Hey again GedBlake.
The last thing you have to do is apologize for helping me a lot, reading through all my text and making things clear for me. And even more you flashed stuff to your device to test if my situation can be reproduced - good that it's not . You've spent a lot of free time just to help, that's really great :good:.
With my bootloader still being intact and the device being recognized by my PC I wonder if maybe I can manage to fastboot flash a different bootloader and/or a new recovery which might maybe break the silly loop when booting. That's my only idea left but if the bootloader isn't in fastboot mode at some time during the loop this won't work too. But I'll give it a try, it's better than cutting tomatoes on my Nexus7 :laugh:.
Thank you very much for your help. If there is anything worth reporting I will of course.
Click to expand...
Click to collapse
Thanks for your kind words... they're appreciated.
Unfortunately, before you can fastboot flash anything, the Nexus 7 needs to be properly booted into the bootloader (the screen with the green Android lying on its back, and the word START adjacent to the POWER BUTTON)... and that requires breaking out of the bootloop first.
Indeed, if the VOL DOWN+POWER ON button combo was working as it should... breaking out of the bootloop would AUTOMATICALLY boot your Nexus 7 into the bootloader.
Finally, your bootloader doesn't need to re-flashed. One you have a stable bootloader boot, normally, (and the easiest way), would just be to flash back to factory stock.
Rgrds,
Ged.
GedBlake said:
Thanks for your kind words... they're appreciated.
Unfortunately, before you can fastboot flash anything, the Nexus 7 needs to be properly booted into the bootloader (the screen with the green Android lying on its back, and the word START adjacent to the POWER BUTTON)... and that requires breaking out of the bootloop first.
Indeed, if the VOL DOWN+POWER ON button combo was working as it should... breaking out of the bootloop would AUTOMATICALLY boot your Nexus 7 into the bootloader.
Finally, your bootloader doesn't need to re-flashed. One you have a stable bootloader boot, normally, (and the easiest way), would just be to flash back to factory stock.
Rgrds,
Ged.
Click to expand...
Click to collapse
Hey again.
Thanks for your explanation, I am not really a newbie with PCs and Tablets etc. but some things are not very interesting until you really need to know them. Like bootloader and fastboot in Android.
So the conclusion in my case is that maybe some day someone will find out how to get access to the N7 via APX - or to be precise, someone finds out or gets to know the necessary commands to flash something to the N7 over the APX-interface. Right?
Because from what I've read it doesn't really make sense to send my N7 in for repair right? Although it hasn't even had its 1st birthday yet I have no chance to get a warranty repair or exchange as it's very obvious I rooted the device and flashed stuff (the damned ROM Manager-screen clearly shows this). And ASUS charges 90 $ (or €, don't know) just for diagnosis, that's a bit much for a device that cost 199 €.
Any further advise? Could I buy a broken N7 from eBay for example and repair mine this way? I would have to change the mainboard right?
Have a nice sunday everyone .
U said you opened the battery...so wen u plugged it back in again,u shouldn't be in bootloop technically... Just a boot!...wat happens if u press the volm down and power button combo just as u insert the battery?
Sent from my Nexus 7 using xda app-developers app
Jagutherrschaften said:
Hey again.
Thanks for your explanation, I am not really a newbie with PCs and Tablets etc. but some things are not very interesting until you really need to know them. Like bootloader and fastboot in Android.
So the conclusion in my case is that maybe some day someone will find out how to get access to the N7 via APX - or to be precise, someone finds out or gets to know the necessary commands to flash something to the N7 over the APX-interface. Right?
Because from what I've read it doesn't really make sense to send my N7 in for repair right? Although it hasn't even had its 1st birthday yet I have no chance to get a warranty repair or exchange as it's very obvious I rooted the device and flashed stuff (the damned ROM Manager-screen clearly shows this). And ASUS charges 90 $ (or €, don't know) just for diagnosis, that's a bit much for a device that cost 199 €.
Any further advise? Could I buy a broken N7 from eBay for example and repair mine this way? I would have to change the mainboard right?
Have a nice sunday everyone .
Click to expand...
Click to collapse
Hi, Jagutherrschaften...
Really sorry it had to end like this... but... perhaps it doesn't...
Nothing about your situation makes logical sense... but reading through your posts again, I find this- On the 3rd October, you posted...
Jagutherrschaften said:
Thank you for your answers. I tried every combination and kept the keys pressed for 2 mins. Nothing. The only thing I can actually do is shut the device down by pressing POWER + VOL UP for a long while.
Click to expand...
Click to collapse
QUOTE FOR EMPHASIS:- "...by pressing POWER + VOL UP for a long while..."
This key press combo doesn't actually shut down the device... it just pushes it into APX mode. It just looks like it's shutdown.
But that's not my point... my point is your Nexus 7 detected that key press interrupt... and acted accordingly.
It did what it was supposed to do.
Maybe you hit the buttons at JUST THE RIGHT INSTANT during the bootloop... and if it can do it for one key press combo... it can do it for another. Namely, POWER+VOL DOWN.
And for this reason... I think you need to try and try and try and try and try again... until you hit the same PRECISE TIMING SWEET SPOT... such that POWER+VOL DOWN takes you into the bootloader.
Vary the timings a bit here and there... alternate pressing the buttons, both before AND after when the Google logo appears.
By your own account... you've already done it once (you just got into the wrong mode... APX mode instead of bootloader mode).
But here's the danger... if after your Herculean efforts, you do manage, finally, to access the bootloader... you absolutely cannot afford to reboot the device normally until after you've fastboot flashed back to factory stock... otherwise the whole cycle will begin again.
So... you need, in preparation...
* A fully charged Nexus 7.
* All the drivers needed (if you don't already have them) installed on your PC.
* The Jellybean 4.3 Factory Stock image downloaded (see my Sig, second link) and unzipped and ready to go.
* A working knowledge of how to use Fastboot.
* And finally... an indomitable spirit! of perseverance... and, of course, a fair amount of free time.
------------------------------------------
I am convinced that your tablet is recoverable.
It's gotta be worth a shot... "once more unto the breach, dear friends", as old Bill Shakespeare would have it.
Anyway... the very best of luck.
Rgrds,
Ged.
GedBlake said:
Hi, Jagutherrschaften...
Really sorry it had to end like this... but... perhaps it doesn't...
Nothing about your situation makes logical sense... but reading through your posts again, I find this- On the 3rd October, you posted...
QUOTE FOR EMPHASIS:- "...by pressing POWER + VOL UP for a long while..."
This key press combo doesn't actually shut down the device... it just pushes it into APX mode. It just looks like it's shutdown.
But that's not my point... my point is your Nexus 7 detected that key press interrupt... and acted accordingly.
It did what it was supposed to do.
Maybe you hit the buttons at JUST THE RIGHT INSTANT during the bootloop... and if it can do it for one key press combo... it can do it for another. Namely, POWER+VOL DOWN.
And for this reason... I think you need to try and try and try and try and try again... until you hit the same PRECISE TIMING SWEET SPOT... such that POWER+VOL DOWN takes you into the bootloader.
Vary the timings a bit here and there... alternate pressing the buttons, both before AND after when the Google logo appears.
By your own account... you've already done it once (you just got into the wrong mode... APX mode instead of bootloader mode).
But here's the danger... if after your Herculean efforts, you do manage, finally, to access the bootloader... you absolutely cannot afford to reboot the device normally until after you've fastboot flashed back to factory stock... otherwise the whole cycle will begin again.
So... you need, in preparation...
* A fully charged Nexus 7.
* All the drivers needed (if you don't already have them) installed on your PC.
* The Jellybean 4.3 Factory Stock image downloaded (see my Sig, second link) and unzipped and ready to go.
* A working knowledge of how to use Fastboot.
* And finally... an indomitable spirit! of perseverance... and, of course, a fair amount of free time.
------------------------------------------
I am convinced that your tablet is recoverable.
It's gotta be worth a shot... "once more unto the breach, dear friends", as old Bill Shakespeare would have it.
Anyway... the very best of luck.
Rgrds,
Ged.
Click to expand...
Click to collapse
@neo45215:
Technically yes, but my N7 doesn't seem to know this . Of course I've tried to get into fastboot mode right after putting back the battery as well. No chance, same bootloop.
@GedBlake:
Thanks for the encouragement, I will for sure give this a try (or several long trys to be precise). Hopefully tonight I'll have a lot of time to press keys .
And my answer to what Bill says would be: "To infinity... and beyond!"
No success so far, I tried pressing buttons for at least 1 h, nothing...
Just wanted to update the status .
Gesendet von meinem Nexus 7 mit Tapatalk 4
Facing same problem
Hello guys. I've done pretty much the same thing and my tab is in the same boot loop that this thread is all about.
The interesting thing is that the ROM I flashed is also KaosDroid7.0.0. I'm unable to prevent any further insight. Sorry for bumping. My clockwork mod version is btw, 6.0.4.1 which proves that the problem might not be clockworkmods or even ROM manager's problem. Since I hadn't used ROM manager.
Also, Is there any way whatsoever to use this APX mode? To fix my nexus.
---------- Post added at 02:05 PM ---------- Previous post was at 01:57 PM ----------
Well, I followed OP's steps almost exactly. First I'd restored the Kitkat factory image, and then I'd proceeded to install the KD 7.0.0. And after that, I realised I'd forgotten to flash Gapps. So I rebooted and then went into CWM to reflash and after that is when my Nexus 7 became useless :crying:
---------- Post added at 02:14 PM ---------- Previous post was at 02:05 PM ----------
Jagutherrschaften, did you send in your Nexus 7 for repair?
Hi,
My brother is having trouble with his Nexus 4 and I was hoping I could get some help here.
The phone won't go past the boot animation, with the 4 floating balls.
It keeps showing that forever (left it for 20 minutes with charger, phone got really hot but did not get past the animation)
- Never rooted or changed firmware. Only updates from Google. (It was on 5.1.1/5.1/5.0.1)
- Sent to a shop, which claimed it can't be fixed (I do not know the reason they gave him).
My brother thinks it is because a weight was accidently dropped on the phone, but the problem only started 3 days after the incident.
No outer damage can be seen on the device, other then a small brake in the back glass.
Thanks in advance to anyone who will try to help
possibly?
Did you just update and it got stuck at the booting up????
opeller said:
Hi,
My brother is having trouble with his Nexus 4 and I was hoping I could get some help here.
The phone won't go past the boot animation, with the 4 floating balls.
It keeps showing that forever (left it for 20 minutes with charger, phone got really hot but did not get past the animation)
- Never rooted or changed firmware. Only updates from Google. (It was on 5.1.1/5.1/5.0.1)
- Sent to a shop, which claimed it can't be fixed (I do not know the reason they gave him).
My brother thinks it is because a weight was accidently dropped on the phone, but the problem only started 3 days after the incident.
No outer damage can be seen on the device, other then a small brake in the back glass.
Thanks in advance to anyone who will try to help
Click to expand...
Click to collapse
Do you have data on it that you want to keep? If you don't you can try booting into the bootloader and unlock it. Then try flashing a factory image. This will wipe all the data on the phone though so that should probably be a last resort.
ChainFires Son said:
Did you just update and it got stuck at the booting up????
Click to expand...
Click to collapse
No, it did not occur after an update.
theminikiller said:
Do you have data on it that you want to keep? If you don't you can try booting into the bootloader and unlock it. Then try flashing a factory image. This will wipe all the data on the phone though so that should probably be a last resort.
Click to expand...
Click to collapse
I have no important data on it.
Which is the safest way to do this? I'd appreciate it if you would be detailed or refer me to a guide, as I want to be careful.
Where should I download the factory image from?
As the name of it states, I wish to get the one from Google, without any changes or addons from users.
Follow this guide http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
You can download factory images from here https://developers.google.com/android/nexus/images
opeller said:
I have no important data on it.
Which is the safest way to do this? I'd appreciate it if you would be detailed or refer me to a guide, as I want to be careful.
Where should I download the factory image from?
As the name of it states, I wish to get the one from Google, without any changes or addons from users.
Click to expand...
Click to collapse
First we should check if you can boot into the bootloader at all. First turn the device off. Then hold down both the volume buttons and then press and hold the power key. Keep holding all the buttons until you see some different colored text. If that happens we should be able to install a factory image, if it still gets stuck on the Google logo I unfortunately don't have any more ideas.
Tried pressing both volume keys and power button. Google logo show for a second, then black for 2 second, thank flashing red notification light every 1/2 second until I let go of the buttons.
When I release the buttons, the phone goes back to charging battery screen.
I see people suggesting that the red light flashing means a battery problem, but the device keeps trying to boot up while it is not plugged to the charger, unlike what happened to them
Any Ideas why this is happening or what the red light means in this case?
You need to press volume down+power button to get into bootloader. Unplug the charger before doing this.
harishmenace said:
You need to press volume down+power button to get into bootloader. Unplug the charger before doing this.
Click to expand...
Click to collapse
Oh it was just volume down, not both. Heh, sorry.
Use the Nexus Root Toolkit (NRT), it's the easiest way to unlock, root, flash and manage your SuperUser needs!
http://www.wugfresh.com/nrt/
Not sure, but maybe?
You can try using the nexus root kit & unlock your bootloader and see if a factory reset can work. If it does you can always relock it again ☺..Flashing a factory image can work too also ...
Tried volume down+ power button while unpluged from charger.
Google logo show up with vibration, then goes away after 2 seconds, like before, but then the screen goes blank. But red led not flashing.
What should I do now? Even just to use the Nexus Root Toolkit I have to allow Developer mode, which I can't as the phone will not boot up.
opeller said:
Tried volume down+ power button while unpluged from charger.
Google logo show up with vibration, then goes away after 2 seconds, like before, but then the screen goes blank. But red led not flashing.
What should I do now? Even just to use the Nexus Root Toolkit I have to allow Developer mode, which I can't as the phone will not boot up.
Click to expand...
Click to collapse
I'm you can't get into the bootloader then I am unfortunately not aware of any way to help you. If you can't even get into the bootloader I think it is a high probability that it is a hardware problem.
I understand. Thank you for your attempt to help me so far, I apriciate it
Anyone else has any Idea what I can try?
opeller said:
I understand. Thank you for your attempt to help me so far, I apriciate it
Anyone else has any Idea what I can try?
Click to expand...
Click to collapse
First you have to ensure "The Situation" of your phone, diagnostic is very important to decide the kind of medicine or treat. Your N4 booting, stuck on google-logo with red blink, then black screen.
To check : Connect your N4 to PC on linux check on terminal command $ lsusb if output
Bus 001 Device 005: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode),
Click to expand...
Click to collapse
on windows (XP/Vista/7)
Qualcomm something QDL Mode or something like this on "device manager"
Click to expand...
Click to collapse
there is a big hope to revive but very long journey. You are lucky since N4 is very popular device.You can obtain required file like MPRG8064.hex and friends
x1123 said:
First you have to ensure "The Situation" of your phone, diagnostic is very important to decide the kind of medicine or treat. Your N4 booting, stuck on google-logo with red blink, then black screen.
To check : Connect your N4 to PC on linux check on terminal command $ lsusb if output
on windows (XP/Vista/7) there is a big hope to revive but very long journey. You are lucky since N4 is very popular device.You can obtain required file like MPRG8064.hex and friends
Click to expand...
Click to collapse
Hi, thank you for your will to help.
When I turn on the Nexus 4 and connect it to my pc, it show the device as Nexus 4 in device manager.
What do you want me to do?
opeller said:
Hi, thank you for your will to help.
When I turn on the Nexus 4 and connect it to my pc, it show the device as Nexus 4 in device manager.
What do you want me to do?
Click to expand...
Click to collapse
detected as Nexus 4 mean your device well alive. any respons from the phone if you check with adb command ? if the phone give respond to adb you can ask phone to turn to recovery $ adb reboot recovery ...
opeller said:
Tried volume down+ power button while unpluged from charger.
Google logo show up with vibration, then goes away after 2 seconds, like before, but then the screen goes blank. But red led not flashing.
What should I do now? Even just to use the Nexus Root Toolkit I have to allow Developer mode, which I can't as the phone will not boot up.
Click to expand...
Click to collapse
That sounds like the battery is completely empty. Put the device on charger over a night and try then to boot into the bootloader.
Once I had these symptoms (red light flashing) on my N4, it was enough to charge the battery for one hour. Then it booted properly. It's worth trying.
x1123 said:
detected as Nexus 4 mean your device well alive. any respons from the phone if you check with adb command ? if the phone give respond to adb you can ask phone to turn to recovery $ adb reboot recovery ...
Click to expand...
Click to collapse
How do I do that?
I was given a Fire HD 7th Gen. I cannot get into recovery on it.
The story is that is was on 5.6.2.0 and accidentally downgraded to 5.6.1.0, which in turn never booted.
My diagnosis is...
I plugged it into my pc and I can hear the windows usb connect chime every 10 seconds or so and 2 seconds after a usb disconnect chime.
I cannot do any key combo to get into recovery as i only have a black screen and no more.
Have adb (and am familiar with) installed and the bin downloaded ready to sideload...
any help is appreciated, thanks!!
Did you try holding all the buttons - Volume UP, Volume DOWN and POWER - together for 30 seconds? That may get you back to power on or to recovery.
Did you verify that you can downgrade from 5.6.2.0 to 5.6.1.0 without bricking due to different bootloaders or recoveries? That tablet may now be bricked.
mdvanness said:
I was given a Fire HD 7th Gen. I cannot get into recovery on it.
The story is that is was on 5.6.2.0 and accidentally downgraded to 5.6.1.0, which in turn never booted.
My diagnosis is...
I plugged it into my pc and I can hear the windows usb connect chime every 10 seconds or so and 2 seconds after a usb disconnect chime.
I cannot do any key combo to get into recovery as i only have a black screen and no more.
Have adb (and am familiar with) installed and the bin downloaded ready to sideload...
any help is appreciated, thanks!!
Click to expand...
Click to collapse
donslade said:
Did you try holding all the buttons - Volume UP, Volume DOWN and POWER - together for 30 seconds? That may get you back to power on or to recovery.
Did you verify that you can downgrade from 5.6.2.0 to 5.6.1.0 without bricking due to different bootloaders or recoveries? That tablet may now be bricked.
Click to expand...
Click to collapse
Yes, I have tried that combination to no effect. From what I have read it cannot be downgraded from 5.6.2.0 to anything.
black screen
donslade said:
Did you try holding all the buttons - Volume UP, Volume DOWN and POWER - together for 30 seconds? That may get you back to power on or to recovery.
Did you verify that you can downgrade from 5.6.2.0 to 5.6.1.0 without bricking due to different bootloaders or recoveries? That tablet may now be bricked.
Click to expand...
Click to collapse
my partner was playing a game put it down for a few mins and screen is black. tried power button method nothing. tried with volume and power button and it wont hard reset. hes even taken out the battery ( its 7th gen 10 inch with alexa) any ides what we can do please. i cant contact amazon as i put google play on it. thanks
von1uk said:
my partner was playing a game put it down for a few mins and screen is black. tried power button method nothing. tried with volume and power button and it wont hard reset. hes even taken out the battery ( its 7th gen 10 inch with alexa) any ides what we can do please. i cant contact amazon as i put google play on it. thanks
Click to expand...
Click to collapse
If still under warranty, return it to Amazon for replacement or refund. Otherwise you can try flashing stock firmware back to it. That's assuming you know what version of fire OS it was on.
mdvanness said:
I was given a Fire HD 7th Gen. I cannot get into recovery on it.
The story is that is was on 5.6.2.0 and accidentally downgraded to 5.6.1.0, which in turn never booted.
My diagnosis is...
I plugged it into my pc and I can hear the windows usb connect chime every 10 seconds or so and 2 seconds after a usb disconnect chime.
I cannot do any key combo to get into recovery as i only have a black screen and no more.
Have adb (and am familiar with) installed and the bin downloaded ready to sideload...
any help is appreciated, thanks!!
Click to expand...
Click to collapse
I have the same problem with my amazon fire hd 10 now downgraded it and screen is black same thing with usb sound when plugged into PC tried every possible buttons compilation to enter recovery still nothing happens device not recognized by ADB which I'm very familiar with as well..tried opening the device and unplugged the battery cable from inside then still nothing totally dissembled it and assembled it again same result please let me know if you find a way to bypass this problem..
Mahmud92 said:
I have the same problem with my amazon fire hd 10 now downgraded it and screen is black same thing with usb sound when plugged into PC tried every possible buttons compilation to enter recovery still nothing happens device not recognized by ADB which I'm very familiar with as well..tried opening the device and unplugged the battery cable from inside then still nothing totally dissembled it and assembled it again same result please let me know if you find a way to bypass this problem..
Click to expand...
Click to collapse
You are permanently bricked. However there will hopefully be a fix in a week or two that would allow you to unbrick any Amazon tablet and unlock the bootloader. I have to run a few small tests on my test devices. I have on bricked HD 10 and it just takes a few minutes to complete the test. If successful, it will immediately boot again. After that we have to modify the zip files and scripts for this device.
DragonFire1024 said:
You are permanently bricked. However there will hopefully be a fix in a week or two that would allow you to unbrick any Amazon tablet and unlock the bootloader. I have to run a few small tests on my test devices. I have on bricked HD 10 and it just takes a few minutes to complete the test. If successful, it will immediately boot again. After that we have to modify the zip files and scripts for this device.
Click to expand...
Click to collapse
I do really appreciate the effort, thanks for the fast reply as well will be waiting for the fix.. :fingers-crossed:
Mahmud92 said:
I do really appreciate the effort, thanks for the fast reply as well will be waiting for the fix.. :fingers-crossed:
Click to expand...
Click to collapse
I can't make any promises. We still need to figure out if its possible. I've only glanced at the board of the 10 and it looks like it will work, but I won't know until I can perform the few tests needed. Hopefully tomorrow I will have time.
Sent from my MotoG3 using XDA Labs
Seems I joined to bricked club today (black screen, USB sound wehen plugging in).
Was on newest version (greather than 5.6.2.0, i think 5.6.3.x) and flashed 5.6.2.0.bin (latest you can download from amazon) via adb sideload for a complete reset and a clean device. I thought downgrading would not work if it would lead to problems - hm seems i was wrong
I bought it on 16.01.2018 so the questions is should i try if i get a replacement from amazon or wait if there will be an solution from DragonFire1024 within the next weeks? Not sure if amazon will replace it without trouble
Bierfreund said:
Seems I joined to bricked club today (black screen, USB sound wehen plugging in).
Was on newest version (greather than 5.6.2.0, i think 5.6.3.x) and flashed 5.6.2.0.bin (latest you can download from amazon) via adb sideload for a complete reset and a clean device. I thought downgrading would not work if it would lead to problems - hm seems i was wrong
I bought it on 16.01.2018 so the questions is should i try if i get a replacement from amazon or wait if there will be an solution from DragonFire1024 within the next weeks? Not sure if amazon will replace it without trouble
Click to expand...
Click to collapse
I'm going as fast as I can to try and unlock this thing apparently I always get the crap end of the stick when it comes to things that are easy I always get the hard part. Until I can get out and get a kit to remove the board, we're stuck where we're at. the motherboard needs to be removed and the only way to do that as a special screwdriver and I do not have the tools. But if the weather lets up I will be able to get them.
Bierfreund said:
Seems I joined to bricked club today (black screen, USB sound wehen plugging in).
Was on newest version (greather than 5.6.2.0, i think 5.6.3.x) and flashed 5.6.2.0.bin (latest you can download from amazon) via adb sideload for a complete reset and a clean device. I thought downgrading would not work if it would lead to problems - hm seems i was wrong
I bought it on 16.01.2018 so the questions is should i try if i get a replacement from amazon or wait if there will be an solution from DragonFire1024 within the next weeks? Not sure if amazon will replace it without trouble
Click to expand...
Click to collapse
Try your luck by contacting Amazons Customer Service they seem quite helpful when I wrote to them, explained the situation about downgrading the version and what happened, they simply asked to do some steps like turning of and button compo etc after making sure its bricked they offered to replace it with a new one right away ..but unfortunately I'm not at USA and they can't ship the replacement to Turkey..so my only hope for now is @DragonFire1024 fix
Mahmud92 said:
Try your luck by contacting Amazons Customer Service they seem quite helpful when I wrote to them, explained the situation about downgrading the version and what happened, they simply asked to do some steps like turning of and button compo etc after making sure its bricked they offered to replace it with a new one right away ..but unfortunately I'm not at USA and they can't ship the replacement to Turkey..so my only hope for now is @DragonFire1024 fix
Click to expand...
Click to collapse
We have download mode on the HD 10 which means we can get our bootloader unlocked once we can execute the payload. There won't be such a thing as a bricked tablet. If you can hold off, we just need execution. We have the recovery already. Everything nearly works aside from the script to load and execute the payload. Hopefully we'll get unlocked today.
Bierfreund said:
Seems I joined to bricked club today (black screen, USB sound wehen plugging in).
Was on newest version (greather than 5.6.2.0, i think 5.6.3.x) and flashed 5.6.2.0.bin (latest you can download from amazon) via adb sideload for a complete reset and a clean device. I thought downgrading would not work if it would lead to problems - hm seems i was wrong
I bought it on 16.01.2018 so the questions is should i try if i get a replacement from amazon or wait if there will be an solution from DragonFire1024 within the next weeks? Not sure if amazon will replace it without trouble
Click to expand...
Click to collapse
Although there are (as yet unrealized) prospects of a hardware unlock/rejunivation I would reach out to Amazon. What can it hurt? You might just score a essentially new refurb vs tearing apart your existing 'brick' with the associated risk of damaging it further. You can still pursue that option if Amazon declines to help. Why hold off...keep all options open.
DragonFire1024 said:
We have download mode on the HD 10 which means we can get our bootloader unlocked once we can execute the payload. There won't be such a thing as a bricked tablet. If you can hold off, we just need execution. We have the recovery already. Everything nearly works aside from the script to load and execute the payload. Hopefully we'll get unlocked today.
Click to expand...
Click to collapse
I got the same problem with my Fire HD 10 after flashing rom. Since I don't live in the US, I can not take it back to Amazon. Hope for the fix from you
see this post
https://forum.xda-developers.com/hd...-fire-hd-10-unbricking-anti-rollback-t3896616
i solved this problem with the post
Mine got a black screen today what do i do?
mdvanness said:
I was given a Fire HD 7th Gen. I cannot get into recovery on it.
The story is that is was on 5.6.2.0 and accidentally downgraded to 5.6.1.0, which in turn never booted.
My diagnosis is...
I plugged it into my pc and I can hear the windows usb connect chime every 10 seconds or so and 2 seconds after a usb disconnect chime.
I cannot do any key combo to get into recovery as i only have a black screen and no more.
Have adb (and am familiar with) installed and the bin downloaded ready to sideload...
any help is appreciated, thanks!!
Click to expand...
Click to collapse
This full solution: https://forum.xda-developers.com/hd8-hd10/orig-development/unlock-fire-hd-10-2017-suez-t3913639