Database Users

[Q] Bricked after trying 3.41 bootloader? Screen unresponsive

I'm ready to spike this thing into the pavement and redeem my squaretrade warranty.
I was tinkering with the recently released 3.41 bootloader and I was getting the bootloop issues, though I could alwasy fastboot back to 3.34 and be fine.
So just now I was following the advice of another user:
http://forum.xda-developers.com/showpost.php?p=32771308&postcount=133
After which I tried flashing the 3.41 bootloader and would get a FAILURE in the fastboot dialog. So I tried erasing/flashing recovery (TWPR 2.3) and bootloader (3.34) and each time got another FAILURE dialog on each erase and flash.
Now when attempting to boot, the screen is *completely* unresponsive. Even went as far as cracking it open and re-plugging in the battery. Nothing.
When plugging in a USB cable though on Windows 7, you get the familiar USB connection alert sounds. Although when plugging in USB devices, you should get the low-to-high sound (do-di), and unplugging you should get the high to low (di-do).
Well, you get the di-do sound when unplugging (keep in mind, screen is off), but when plugging IN, you get 3 low tones (do-do-do)... screen still off.
All the time the screen being completely blank. Did I actually kill this thing? Are there any steps to take to bring it back to stock, or at leats get the screen running. I am afraid at some point recovery or bootloader was erased and somehow not re-flashed... though I have done so numerous times in the past.
Any similar experiences or suggestions?

Did you adb erase bootloader? If so then you are truley bricked until the nvflash is available for this device. I believe that is what its called.

Travisdroidx2 said:
Did you adb erase bootloader?
Click to expand...
Click to collapse
Can't boot tablet, whether it be bootloader, recovery, or android. No matter what combination of power/volume I try, the screen remains blank. The only "responsiveness" I get is when plugging/unplugging USB cables in my pc, but even then I get the odd do-do-do as though the device drivers were unable to property install.
Sent from my Galaxy Nexus using Tapatalk 2

Did you ever run that command though? I see you said you tried to delete recovery and bootloader.

Everything leading up to this point was run in the bootloader via fastboot (fastboot erase recovery / fastboot erase bootloader / fastboot flash bootloader xxx.img / fastboot flash recovery xxx.img). I followed the steps I linked in the OP. Everything was running fine prior to booting to the bootloader to tinker with 3.41.
Now that I read what I've done, I am guessing I fried the bootloader. :\
Sent from my Galaxy Nexus using Tapatalk 2

Adb erase bootloader is where you went wrong. Sorry that sucks.

Anyway to get this thing running again short of dropping and replacing?
Sent from my Galaxy Nexus using Tapatalk 2

kbluhm said:
Anyway to get this thing running again short of dropping and replacing?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Not at this point in time.

Oof.. Of all things to accidentally erase.. The bootloader.. I'm sorry man, that's a hard lesson to learn. The erase option for me has giant blinking neon light on it that says "STAY AWAY".. In over two years of owning Android devices I've never once actually used that command option and have absolutely no plans to ever use it.

Hahaha, hard lesson to learn, I agree. This sucks, looks like my beloved Nexus 7 may be meeting with an untimely demise.
Sent from my Galaxy Nexus using Tapatalk 2

kbluhm said:
I'm ready to spike this thing into the pavement and redeem my squaretrade warranty.
I was tinkering with the recently released 3.41 bootloader and I was getting the bootloop issues, though I could alwasy fastboot back to 3.34 and be fine.
So just now I was following the advice of another user:
http://forum.xda-developers.com/showpost.php?p=32771308&postcount=133
After which I tried flashing the 3.41 bootloader and would get a FAILURE in the fastboot dialog. So I tried erasing/flashing recovery (TWPR 2.3) and bootloader (3.34) and each time got another FAILURE dialog on each erase and flash.
Now when attempting to boot, the screen is *completely* unresponsive. Even went as far as cracking it open and re-plugging in the battery. Nothing.
When plugging in a USB cable though on Windows 7, you get the familiar USB connection alert sounds. Although when plugging in USB devices, you should get the low-to-high sound (do-di), and unplugging you should get the high to low (di-do).
Well, you get the di-do sound when unplugging (keep in mind, screen is off), but when plugging IN, you get 3 low tones (do-do-do)... screen still off.
All the time the screen being completely blank. Did I actually kill this thing? Are there any steps to take to bring it back to stock, or at leats get the screen running. I am afraid at some point recovery or bootloader was erased and somehow not re-flashed... though I have done so numerous times in the past.
Any similar experiences or suggestions?
Click to expand...
Click to collapse
Hey,
Did Squaretrade fix your device? I just want to know if there warranty is still valid if you unlock or brick your tablet

Nexus 4: Boot loop with locked bootloader and no USB debugging - HELP!!!

Hi all,
First time posting on here (but I read the forums often - for guides etc).
Bought the Nexus 4 and I unlocked the bootloader and rooted the device. Kept to the stock Android (JB 4.2) however I locked the bootloader again.
The boot loop occurred after a restart after I did the following things:
1. Used Battery Calibration to calibrate the battery. Left the battery to drain and then charge to 100%.
2. Used VM Heap to change the amount and restarted the phone. Boot loop ocurred.
I have tried many things after reading this forums and other forums but there seems to be no answer to this issue.
Things I've tried are:
1. Booted into recovery mode and wipe data/factory reset many times - still has boot loop
2. Used Nexus Root Toolkit and tried the various functions on there. Fastboot doesn't detect the device (even though its in fastboot mode) in order for me to unlock the bootloader again and flash it with the stock ROM. Windows (8) does detect it but can't load drivers for it. Been through all the instructions on the Nexus Root Toolkit - reinstall drivers, cleared the device from device manager, cleared it from usb list etc. Fastboot just won't detect it to allow me to unlock!!
3. Let the battery drained and tried factory resetting but doesn't work (not tried fully charging it and then resetting though)
4. Been trying various other things which I read on the forum(s) but nothing seems to work!:crying:
Literally spent the whole day trying so many different things. Seems like I discovered a whole new unique problem to causing boot loop on the Nexus 4. I don't want to have to send this back to Google for a replacement if they give me one - hopefully with the locked bootloader and the data cleared, they won't know I've rooted, not to mention its micro-sim and my backup feature phone doesn't take micro-sim :crying:
Has any one had this issue before and fixed it!? Would really appreciate the help/guidance!
My first time rooting a phone, didn't do it before on other phones because thought knowing my luck I'd brick it beyond repair! Luck would have it, that exactly what has happened.
Appreciate the replies and help on this!

ThuanBui said:
Hi all,
First time posting on here (but I read the forums often - for guides etc).
Bought the Nexus 4 and I unlocked the bootloader and rooted the device. Kept to the stock Android (JB 4.2) however I locked the bootloader again.
The boot loop occurred after a restart after I did the following things:
1. Used Battery Calibration to calibrate the battery. Left the battery to drain and then charge to 100%.
2. Used VM Heap to change the amount and restarted the phone. Boot loop ocurred.
I have tried many things after reading this forums and other forums but there seems to be no answer to this issue.
Things I've tried are:
1. Booted into recovery mode and wipe data/factory reset many times - still has boot loop
2. Used Nexus Root Toolkit and tried the various functions on there. Fastboot doesn't detect the device (even though its in fastboot mode) in order for me to unlock the bootloader again and flash it with the stock ROM. Windows (8) does detect it but can't load drivers for it. Been through all the instructions on the Nexus Root Toolkit - reinstall drivers, cleared the device from device manager, cleared it from usb list etc. Fastboot just won't detect it to allow me to unlock!!
3. Let the battery drained and tried factory resetting but doesn't work (not tried fully charging it and then resetting though)
4. Been trying various other things which I read on the forum(s) but nothing seems to work!:crying:
Literally spent the whole day trying so many different things. Seems like I discovered a whole new unique problem to causing boot loop on the Nexus 4. I don't want to have to send this back to Google for a replacement if they give me one - hopefully with the locked bootloader and the data cleared, they won't know I've rooted, not to mention its micro-sim and my backup feature phone doesn't take micro-sim :crying:
Has any one had this issue before and fixed it!? Would really appreciate the help/guidance!
My first time rooting a phone, didn't do it before on other phones because thought knowing my luck I'd brick it beyond repair! Luck would have it, that exactly what has happened.
Appreciate the replies and help on this!
Click to expand...
Click to collapse
I'm having the same problem!

For the toolkit to see the device, you need to put your device to fastboot mode by pressing vol (-) and then the power button (the phone should be in powered off mode to do this).

andr0idfreak said:
For the toolkit to see the device, you need to put your device to fastboot mode by pressing vol (-) and then the power button (the phone should be in powered off mode to do this).
Click to expand...
Click to collapse
I've done this many times but still no luck

ThuanBui said:
I've done this many times but still no luck
Click to expand...
Click to collapse
I had a boot loop issue. It was stuck on Google logo - the white logo.
I couldn't go into recovery either.
My fix was to flash the stock recovery.IMG
I too couldn't detect the device however I kept trying.
If you face a problem getting into fast boot mode try pressing vol up + vil down + power. Didn't work for me but worked for some.
Let me know how it goes I'm glad to help out if I can

Having USB Debugging ticked WHILE IN ANDROID has absolutely no effect on whether or not your computer can see the device WHILE IN RECOVERY OR FASTBOOT.

monkeying. around said:
I had a boot loop issue. It was stuck on Google logo - the white logo.
I couldn't go into recovery either.
My fix was to flash the stock recovery.IMG
I too couldn't detect the device however I kept trying.
If you face a problem getting into fast boot mode try pressing vol up + vil down + power. Didn't work for me but worked for some.
Let me know how it goes I'm glad to help out if I can
Click to expand...
Click to collapse
Didn't fix it in the end...no matter what I tried. I got a replacement from Google (thankfully they didn't charge me for the new one!).
BTW the batch of Nexus 4 released in end of Jan/early Feb has a much better battery life than the one I got from the batch released in early Dec. Won't be rooting the new Nexus 4 in case sh*t happens again but no doubt will get tempted again somewhere down the line!
Thank you to everyone who replied!~ :good:

sideloading 4.4.2 and stuck on boot loop
ThuanBui said:
Didn't fix it in the end...no matter what I tried. I got a replacement from Google (thankfully they didn't charge me for the new one!).
BTW the batch of Nexus 4 released in end of Jan/early Feb has a much better battery life than the one I got from the batch released in early Dec. Won't be rooting the new Nexus 4 in case sh*t happens again but no doubt will get tempted again somewhere down the line!
Thank you to everyone who replied!~ :good:
Click to expand...
Click to collapse
bro mime nexus 4 has stuck into boot loop after upgrading from 4.4 to 4.4.2 .i was sideloading the zip dont know whats the issue ......i was rooted but went to stock via nexus roottool kit to get OTA . any suggestion

​
joshnichols189 said:
Having USB Debugging ticked WHILE IN ANDROID has absolutely no effect on whether or not your computer can see the device WHILE IN RECOVERY OR FASTBOOT.
Click to expand...
Click to collapse
all you got to do is download the toolkit and flash the software your phone is using and put it in fastboot and begin
:good::good::good::good::good::good::good:

Unstoppable bootloop after flashing new ROM

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?

[Q] Brinked nexus 7 APX mode (only)

Hi guys yesterday my nexus freeze in gmail.. so i turn it down by pressing and hold te power button
then the tablet freeze in the Google LOGO
after taht i try to ge into Recovery mode,, it freeze aswell then i just reboot it on bootloader adn i leave it thre for about 1 hour charging
the i try to go to boot loader to fhasl stok rom..
but..!! it wont work.. never turns on..
and it shows in my pc as APX mode
no more than that y tri to start it in bootloader but i just cant with every method i find in internet even i try to charge it by pogo pins and nothing happends
i try to do soetring with nvflash but it said
Unknow devices found and do nothing
pls help me ,!!

radeon9550 said:
Hi guys yesterday my nexus freeze in gmail.. so i turn it down by pressing and hold te power button
then the tablet freeze in the Google LOGO
after taht i try to ge into Recovery mode,, it freeze aswell then i just reboot it on bootloader adn i leave it thre for about 1 hour charging
the i try to go to boot loader to fhasl stok rom..
but..!! it wont work.. never turns on..
and it shows in my pc as APX mode
no more than that y tri to start it in bootloader but i just cant with every method i find in internet even i try to charge it by pogo pins and nothing happends
i try to do soetring with nvflash but it said
Unknow devices found and do nothing
pls help me ,!!
Click to expand...
Click to collapse
Ok as far as I have herd there is no way to rescue a bricked nexus 7 using NVflash if there are no Backed-up Blob files on it. If you just ended up in apx mode without doing anything to its bootloader then it is probably out of charge or needs to have a particular button combo to sort it out
if on the other hand you corrupted the bootloader and after that the device is in a sleep of death then you have hardbricked your nexus 7 'apparently'
good luck

No Custom Bootloader
Hill well i never done something to the bootlaoder no Multibot no Custom bootloader ( factory only )
i try a lot of key combination but nothing happend :/
but my questin is i got a second n7 same specs how can i pull the blob files and,
can i use this files to unbrink the other
if i can pls explainme that
i love my tablet i dont wanna see her die
thnaks..

don't give up
radeon9550 said:
Hill well i never done something to the bootlaoder no Multibot no Custom bootloader ( factory only )
i try a lot of key combination but nothing happend :/
but my questin is i got a second n7 same specs how can i pull the blob files and,
can i use this files to unbrink the other
if i can pls explainme that
i love my tablet i dont wanna see her die
thnaks..
Click to expand...
Click to collapse
Ok if you want to know about how to set up a link between the NVflash tool (on your computer) and your new n7 just use the following proceedure here www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean
As far as your old n7 is concerned if it is definitely hard-bricked and you have not made a backup using NVflash before the brick then there is no known way to save it with only a computer and n7 connected via USB however there is a slim chance your old n7 might just be in a state where it can't access the bootloader because of some power shortage or incorrect button states so do keep trying the key combos and recharging etc because there are a lot of stories of people who escaped using this random strategy. Normally to get into apx mode one would press all three buttons at once so to get out you could do the same so it is worth a try
BTW I have one more trick up my sleeve, if you download WugFresh's toolkit for the n7 (make sure its 2012 edition) then you could try pressing the 'reboot bootloader' option in the advance options menu in the lower left.
good luck

Gloftking said:
Ok if you want to know about how to set up a link between the NVflash tool (on your computer) and your new n7 just use the following proceedure here www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean
As far as your old n7 is concerned if it is definitely hard-bricked and you have not made a backup using NVflash before the brick then there is no known way to save it with only a computer and n7 connected via USB however there is a slim chance your old n7 might just be in a state where it can't access the bootloader because of some power shortage or incorrect button states so do keep trying the key combos and recharging etc because there are a lot of stories of people who escaped using this random strategy. Normally to get into apx mode one would press all three buttons at once so to get out you could do the same so it is worth a try
BTW I have one more trick up my sleeve, if you download WugFresh's toolkit for the n7 (make sure its 2012 edition) then you could try pressing the 'reboot bootloader' option in the advance options menu in the lower left.
good luck
Click to expand...
Click to collapse
Same deal here - and frickin ASUS wanted $165 JUST for the motherboard part. So I said no to the RMA and they sent it back.
NOW my question is - can I order a motherboard and just swap it out? Does that work? http://www.ebay.com/itm/Asus-Nexus-...2GB-ASUS-Google-ME370T-Ship-Fast/121330719361

bshiznit said:
Same deal here - and frickin ASUS wanted $165 JUST for the motherboard part. So I said no to the RMA and they sent it back.
NOW my question is - can I order a motherboard and just swap it out? Does that work? http://www.ebay.com/itm/Asus-Nexus-...2GB-ASUS-Google-ME370T-Ship-Fast/121330719361
Click to expand...
Click to collapse
Haven't done it myself, but understand it does work. https://www.ifixit.com/Guide/Nexus+7+Motherboard+Replacement/9943

PrizmaticSmoke said:
Haven't done it myself, but understand it does work. https://www.ifixit.com/Guide/Nexus+7+Motherboard+Replacement/9943
Click to expand...
Click to collapse
Thanks! Ordered it and will be attempting

[Q] Nexus 7 Wifi 2012 32GB Kitkat Stops booting/Soft brick?

Hi,
i never touched my Nexus 7 with any other ROMs or such. It was still rooted and kinda original. Now i can't do anything with it anymore.
I talked to the google hotline already and i was trying to start the bootloader which works fine, but nothing more.
1. When i choose Start, Restart Bootloader, Recovery Mode oder Power Off nothing happens, beside Booting failed (Recovery Mode).
2. When i start the phone just with the power button i just see the google logo.
3. When i plugin the power cable i don't see the battery for loading.
I got another device from google with horrorable battery power, so now i wanna try on my own the save my Tablet. I flashed my Galaxy Nexus and HTC HD2 couple of times, so i'm not a 100% Noob.
I was already looking in like 10 threads i found about problems nearly like mine, but i don't got the golden clue yet, sry.
I hope you can help me please.

lordmao said:
Hi,
i never touched my Nexus 7 with any other ROMs or such. It was still rooted and kinda original. Now i can't do anything with it anymore.
I talked to the google hotline already and i was trying to start the bootloader which works fine, but nothing more.
1. When i choose Start, Restart Bootloader, Recovery Mode oder Power Off nothing happens, beside Booting failed (Recovery Mode).
2. When i start the phone just with the power button i just see the google logo.
3. When i plugin the power cable i don't see the battery for loading.
I got another device from google with horrorable battery power, so now i wanna try on my own the save my Tablet. I flashed my Galaxy Nexus and HTC HD2 couple of times, so i'm not a 100% Noob.
I was already looking in like 10 threads i found about problems nearly like mine, but i don't got the golden clue yet, sry.
I hope you can help me please.
Click to expand...
Click to collapse
I encountered identical problem on an N7 (2012) 32gb and try everything that I know how and always get the message ADB not found. Finally I use Skipsoft ToolKit and use option #9 Download, Extract and Flash Google Factory Stock Rom and it works . My N7 was returned to stock with latest firmware.. Of course you will lose all data and still have to unlock and root again
I am not a techie so I cannot explain the details but only share my experience.
I hope it will work for you

lordmao said:
Hi,
i never touched my Nexus 7 with any other ROMs or such. It was still rooted and kinda original. Now i can't do anything with it anymore.
I talked to the google hotline already and i was trying to start the bootloader which works fine, but nothing more.
1. When i choose Start, Restart Bootloader, Recovery Mode oder Power Off nothing happens, beside Booting failed (Recovery Mode).
2. When i start the phone just with the power button i just see the google logo.
3. When i plugin the power cable i don't see the battery for loading.
I got another device from google with horrorable battery power, so now i wanna try on my own the save my Tablet. I flashed my Galaxy Nexus and HTC HD2 couple of times, so i'm not a 100% Noob.
I was already looking in like 10 threads i found about problems nearly like mine, but i don't got the golden clue yet, sry.
I hope you can help me please.
Click to expand...
Click to collapse
If you can't see the white battery picture when plugging in the power cable, I suggest you use AC power, and if you are, try using a different USB Micro cable.