Database Users

Bricked my nexus 7

I think i ruined my nexus 7 .... used 1 click root and had no problems
downloaded a ROM from clockwork and after flashing it wont turn on.
if i boot into recovery it sits at the google screen never goes
if i boot up it just loops
someone please help!

Power off then press and hold the power and both volume keys. Once in the bootloader, do a factory reset. Let me know if that works.
Sent from my SAMSUNG-SGH-I747 using xda premium

vegandroid said:
Power off then press and hold the power and both volume keys. Once in the bootloader, do a factory reset. Let me know if that works.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
if i try to boot in boot loader it never gets past the google screen, i cant find a factory reset option

bootloader is power button and volume down, not both volume buttons.

simms22 said:
bootloader is power button and volume down, not both volume buttons.
Click to expand...
Click to collapse
when i do that, it sits at the google screen with the unlocked pad lock

You can always reflash factory images as long as you can get to fastboot...download the Nexus 7 Toolkit and it will make it really easy for you.

jhotmann said:
You can always reflash factory images as long as you can get to fastboot...download the Nexus 7 Toolkit and it will make it really easy for you.
Click to expand...
Click to collapse
i got the tool kit, i selected the 1 click for all and it completed the entire process, but the tablet still wont boot. just on the jelly bean X screen

drocksmash said:
i got the tool kit, i selected the 1 click for all and it completed the entire process, but the tablet still wont boot. just on the jelly bean X screen
Click to expand...
Click to collapse
im trying the option 9 now

drocksmash said:
im trying the option 9 now
Click to expand...
Click to collapse
awesome it worked!
i am now selecting the all in 1 to see if i can get back to root status

[Q] Cant Get into AP Fast Boot!

I accidentally,... . unknowingly wiped the RED "system" button in Safestrap 3.12 on my Droid RAZR M today. (I was suppose to be wiping the cash and dalvik, but missed) I'm a retard I know. :crying:
Now I cant get into AP Fastboot to restore the phone from this hard brick!
When I press the power button along with the volume buttons, the only thing that happens is the red Motorola 'M" appears for a few seconds then the safe strap screen appears with the little sad robot, but that's it no AP Fastboot. Pressing the on screen buttons to enter Safestrap Recover do not respond. Oh boy I'm afraid I really did it this time. Its on the charger but i don't know if its even charging with out as OS?
Battery power was at 60% before i bricked it (i think). RSD Lite or my PC for that matter don't even see the phone when its plugged in.
Can this be saved? Or do I need to take a trip down to the Verizon Wireless store?
Droid RAZR M
4.1.2 OTA
Rooted
Locked Bootloader
Safestrap 3.12
Partitioned 64GB SD card utilizing Linked2SD

You need a different key combo to get into fastboot. You're not permabricked tho - that's just a really bad softbrick
Sent from my XT907 using Tapatalk 2

sloosecannon said:
You need a different key combo to get into fastboot. You're not permabricked tho - that's just a really bad softbrick
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
Really? Well I hope your right. It gives me some hope. lol So do you have any idea of what alternative key combo i might have to use? Thank you for the reply.

Try holding power & volume down until the screen flickers then hold power and both volume buttons. You gotta be quick
If your boot loader is locked you won't be able to fast boot back until the new fast boot files come out though if your on 4.1.2

http://forum.xda-developers.com/showthread.php?t=2207419&page=2
go to the last page new tools and utilities up from matt and it works just unbricked me be sure to thank him :good:

sloosecannon said:
You need a different key combo to get into fastboot. You're not permabricked tho - that's just a really bad softbrick
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
Thank you! You were right! was able to get into AP Fastboot with a different button combo like u said. :victory:

shane1 said:
Try holding power & volume down until the screen flickers then hold power and both volume buttons. You gotta be quick
If your boot loader is locked you won't be able to fast boot back until the new fast boot files come out though if your on 4.1.2
Click to expand...
Click to collapse
Shane you were right on the money brother!!! Thank you so very much. It worked perfectly. I'm up and running again.
much respect

bigrob1015 said:
http://forum.xda-developers.com/showthread.php?t=2207419&page=2
go to the last page new tools and utilities up from matt and it works just unbricked me be sure to thank him :good:
Click to expand...
Click to collapse
It worked! I utilized the NEWER version of Mat's utility and it did it!!! Woo Hoo!! Thank you so very much. Thank you all for all the speedy help.

SARM1084 said:
Shane you were right on the money brother!!! Thank you so very much. It worked perfectly. I'm up and running again.
much respect
Click to expand...
Click to collapse
hey no prob! i try to help as much as i can !

bigrob1015 said:
http://forum.xda-developers.com/showthread.php?t=2207419&page=2
go to the last page new tools and utilities up from matt and it works just unbricked me be sure to thank him :good:
Click to expand...
Click to collapse
New to this, i accidentally the whole phone, same problem im in AP fastboot but registers as Device Locked
run through it on windows OS but says 'Fastboot" is not recognized as an internal or external command" and doesnt reboot as said
this process took 1min

Halp
This thread saved my life, then killed me. The suggestion about the different keys was spot on, i got into fast boot mode, then ran that utility. It totally failed me, I must have killed my phone pretty dead, and now there are no more key combos (the suggested one worked at first but now its just making the screen go blank) to try to get back into fast boot to try again. any more suggestions? on the up side verizon just pushed that update so i figure i can blame that to attempt an exchange

Did you take the update before using that utility? If you did, which version did you use? If you were already updated, then you needed to run 1.20. If you ran the wrong utility, that will cause issues. Now, since you can't boot, it sounds like your battery is dead. When you get to the blank screen, plug it in and leave it to charge for a while.

I'm no expert by any means but I'll try to help as best i can. If not me I'm confident someone else will. Now, I apologize because I didn't understand your original post.
Could you elaborate a little more please?
1. What were you trying to do with your phone prior to things going wrong, if they went wrong at all.
2. you mentioned AP Fastboot. So IM going to assume that at least you can access it. (not the same problem that I was having) that's a good thing! lol
3. Are you utilizing a utility like the one by Matt? Or are you doing something else? Like flashing firmware etc.
4. What were you in Fastboot for? What were your intentions?
I hope this doesn't come over a condescending. Just trying to get a Clearer understand of your issue so we can help.
Sent from my XT907 using xda app-developers app

Sorry double post

PartyOnINSANE said:
New to this, i accidentally the whole phone, same problem im in AP fastboot but registers as Device Locked
run through it on windows OS but says 'Fastboot" is not recognized as an internal or external command" and doesnt reboot as said
this process took 1min
Click to expand...
Click to collapse
Look at my previous post
Sent from my XT907 using xda app-developers app

Sorry, my post musnt have updated. As you can see I managed to fix my problem. If there's any issues in the future for anyone I will be sure to advise as best I can.
Sent from my XT907 using xda app-developers app

PartyOnINSANE said:
Sorry, my post musnt have updated. As you can see I managed to fix my problem. If there's any issues in the future for anyone I will be sure to advise as best I can.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
No problems brother. Glad to see your up and running.
Sent from my XT907 using xda app-developers app

Stuck in a Boot Loop
PartyOnINSANE said:
New to this, i accidentally the whole phone, same problem im in AP fastboot but registers as Device Locked
run through it on windows OS but says 'Fastboot" is not recognized as an internal or external command" and doesnt reboot as said
this process took 1min
Click to expand...
Click to collapse
Could you help me please?
I changed 2 lines in my build.prop file so i could see if I could get touchless control.
After I changed it, I restarted my phone. Now it is stuck in the Red M Boot, and it stays there, dosent black screen, dosent boot. I can get to the boot selection menu, but i cant choose anything, they all end up at the Red M. I Read that I can fix it in AP Fastboot, but I can get there. Also if i force it off (with power button and volume button) It just goes back to the Red M.
Everything I do ends up at the Red M
Help fast please, its my only phone, and I just got rid of my house phone
I have a
Droid Razr M
Rooted, no custom Roms or Recovery.
Changed my build.prop from XT907 to XT1087
Changed My Boot Animation to R2D2
A: 4.1.2
8gb Sd card on it.

gjhkl said:
Could you help me please?
I changed 2 lines in my build.prop file so i could see if I could get touchless control.
After I changed it, I restarted my phone. Now it is stuck in the Red M Boot, and it stays there, dosent black screen, dosent boot. I can get to the boot selection menu, but i cant choose anything, they all end up at the Red M. I Read that I can fix it in AP Fastboot, but I can get there. Also if i force it off (with power button and volume button) It just goes back to the Red M.
Everything I do ends up at the Red M
Help fast please, its my only phone, and I just got rid of my house phone
I have a
Droid Razr M
Rooted, no custom Roms or Recovery.
Changed my build.prop from XT907 to XT1087
Changed My Boot Animation to R2D2
A: 4.1.2
8gb Sd card on it.
Click to expand...
Click to collapse
Holding the combination of buttons will only cause it to reboot, every time. Holding the power button down will make it shutdown. With that being said, what was your battery like before you started all of this? If it's below 50%, you're going to have a hard time. Shut the phone down and charge the battery ovenight, prior to attempting to fastboot.
If your battery is good, then you can fastboot. Hold all three buttons down, until you get the phone to power off. As soon as power goes off, you'll see a quick line flash at the top of the screen. As soon as you see this flash, quickly let go of the power button and then re-press it. If you got it right, you'll go into the fastboot menu. If you got it wrong, it will attempt to reboot. If it reboots, just try the button combo again. Once you get into the fastboot menu, use the vol- key to get to the option you need, and then hit the vol+ to choose that option.

RikRong said:
Holding the combination of buttons will only cause it to reboot, every time. Holding the power button down will make it shutdown. With that being said, what was your battery like before you started all of this? If it's below 50%, you're going to have a hard time. Shut the phone down and charge the battery ovenight, prior to attempting to fastboot.
If your battery is good, then you can fastboot. Hold all three buttons down, until you get the phone to power off. As soon as power goes off, you'll see a quick line flash at the top of the screen. As soon as you see this flash, quickly let go of the power button and then re-press it. If you got it right, you'll go into the fastboot menu. If you got it wrong, it will attempt to reboot. If it reboots, just try the button combo again. Once you get into the fastboot menu, use the vol- key to get to the option you need, and then hit the vol+ to choose that option.
Click to expand...
Click to collapse
I have done your steps and I get the menu up, but when I try to scroll down with the volume down button, it doesn't move. It just stays on "normal powerup". How can I fix this?

[Q] Nexus 7 3G is stuck in APX mode after failing to restart bootloader

Hi,
As a fairly new Android user, I think I managed to brick my Nexus 7. I'm not entirely sure what it is that broke it (probably my stupidity). After I interrupted the process (I was supposed to flash the radio, but had accidentally pasted the wrong filename...possibly flash-all.she or flash-base.sh), I tried to execute "fastboot reboot-bootloader", which failed before fastboot crashed. From then onward, the device didn't react when I tapped the power button. I had to do a hard reset in order for the phone to do something...but now I realise it might not have been the best idea. It is currently stuck in APX mode.
I have tried holding the power button for over 15 seconds, and holding power+down for over 15 seconds, but to no avail. Is there anything that I can do to fix this issue?
Thank you in advance for any help. I apologize if this is already covered in a different thread

me too help me ??? NEXUS7 APX MODE

kaizone said:
me too help me ??? NEXUS7 APX MODE
Click to expand...
Click to collapse
DON'T PANIC!
Disconnect from the computer......Hold the power button down....and press the volume button several times....this will get you into recovery!
You can then reconnect the Nexus!
I had to deal with this yesterday for a friend. Apparently it occurs when the process of files being pushed to the device, is interrupted.
Hope this works for you. :good:

ROLY5573 said:
DON'T PANIC!
Disconnect from the computer......Hold the power button down....and press the volume button several times....this will get you into recovery!
You can then reconnect the Nexus!
I had to deal with this yesterday for a friend. Apparently it occurs when the process of files being pushed to the device, is interrupted.
Hope this works for you. :good:
Click to expand...
Click to collapse
and press the volume button several times....this will get you into recovery!
VOLUME BUTTON UP OR DOWN ??? AND NOT HOLD

kaizone said:
and press the volume button several times....this will get you into recovery!
VOLUME BUTTON UP OR DOWN ??? AND NOT HOLD
Click to expand...
Click to collapse
Hold the Power button down...and...press the volume up button (off and on) a few times to get you into recovery.

Hold the Power button down...and...press the volume up button (off and on) a few times to get you into recovery.
Click to expand...
Click to collapse
cry not work ???? i update android 4.3 use Nexus 7 ToolKit update but reboot and dead ,go to mode apx
I made a mistake at your disposal ??? hold Power button "down ?? volume down ?" and off on button volume up

kaizone said:
cry not work ???? i update android 4.3 use Nexus 7 ToolKit update but reboot and dead ,go to mode apx
I made a mistake at your disposal ??? hold Power button "down ?? volume down ?" and off on button volume up
Click to expand...
Click to collapse
You can follow these steps, (from a Google Search) posted a few months ago......You will get there eventually, Just Be Patient!
http://forum.xda-developers.com/showpost.php?p=30002160&postcount=10

If your bootloader is corrupt or deleted you are at a dead end. Your nexus is bricked.
I am in the same situation and I've done a lot of reading for the past few days it seems to be the answer I keep coming to. I keep finding threads like this one that give me hope and end without a solution.
I've tried every button combination I have seen and nothing works. Time to take my Nexus back to where I bought it and chance me arm.
Sent from my Nexus 4 using Tapatalk 2

So, time to use NVram
Enviado desde mi Nexus 7 usando Tapatalk 4 Beta

andyro2008 said:
So, time to use NVram
Enviado desde mi Nexus 7 usando Tapatalk 4 Beta
Click to expand...
Click to collapse
Do you mean nvflash? If so as far as I can find out it doesn't work on n7.
Sent from my Nexus 4 using Tapatalk 2

ChrisHRocks said:
If your bootloader is corrupt or deleted you are at a dead end. Your nexus is bricked.
I am in the same situation and I've done a lot of reading for the past few days it seems to be the answer I keep coming to. I keep finding threads like this one that give me hope and end without a solution.
I've tried every button combination I have seen and nothing works. Time to take my Nexus back to where I bought it and chance me arm.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
This is unfortunately true... 'you need a working bootloader to flash a bootloader'.
If the current bootloader (v4.18 under Jellybean 4.2.2) becomes corrupt whilst flashing the latest bootloader (v4.23 under Jellybean 4.3), the device is Hardbricked... and defaults to APX mode awaiting somebody to nvFlash a replacement bootloader.
Unfortunately nobody has yet figured out how to use nvFlash on the Nexus 7.
Flashing a bootloader is probably the single most riskiest operation you can undertake... even using Fastboot is not without it's risks. All it takes is one dodgy USB connection or some problem with the PC whilst mid bootloader flash... and you have a Hardbrick.
----------------------------------
The safest way to upgrade the N7 is via OTA (either a .Zip flashed in recovery) or naturally 'over-the-air'.
The reason being, is the new bootloader isn't immediately directly flashed to the bootloader partition... a file in the OTA called BOOTLOADER.RAW is dropped into the USP (Staging) partition... leaving the original bootloader temporarily untouched.
Upon successful completion of the OTA, the device will shutdown and re-boot.
Then and only then, is the new bootloader transferred/'flashed' from USP (Staging) into the bootloader partition proper.
----------------------------------
None of which helps anybody here of course.
I wish I could offer some useful practical advice, but other than try to crack the nvFlash/APX problem, there's not much can I say or offer.
Sorry..
Rgrds,
Ged.

Just returned mine to the shop. They are sending it to Asus. Let's just hope Asus don't smell a rat.
I'll should get it back in 10 days I'll report back then.
Sent from my Nexus 4 using Tapatalk 2

ChrisHRocks said:
Just returned mine to the shop. They are sending it to Asus. Let's just hope Asus don't smell a rat.
I'll should get it back in 10 days I'll report back then.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Any luck? I'm in the same boat and wondering if I can send it back... especially as I've got just weeks of my warranty left.

Cadabena said:
Any luck? I'm in the same boat and wondering if I can send it back... especially as I've got just weeks of my warranty left.
Click to expand...
Click to collapse
Yeah I got it back all was fine except it won't charge now so it's been sent back again to sort that!
Sent from my Nexus 4 using Tapatalk 4

ChrisHRocks said:
Yeah I got it back all was fine except it won't charge now so it's been sent back again to sort that!
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Returned mine and got it back today. Feel a little guilty, but happy to be running 4.3! Hope yours got sorted in the end.

[HELP THREAD] Nexus 4 with 4.3.3 "no command"

Hi to all
I updated my nexus 4.2.2 to 4.3.3 through the ota.
Now i tried to unlock&root with the nexus 4 toolkit(last version 1.6.8)
Never mind what i'm trying to do, when the device trying to get into recovery there is a lying android red icon with: "no command"
I believe this is a soft brick , but the device is working and the android is boot up normally,
I allso tried to press power key and after he was pressed i conitnue to hold him and press volume up, the only thing that happend is
a red light and no recovery menu, i tried every way to use the tool but the recovery isn't back!
Please help me guys!

You are in the future or what?
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 05:03 PM ---------- Previous post was at 05:03 PM ----------
Thibaultvw said:
You are in the future or what?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
And it is stock recovery.
Sent from my Nexus 4 using xda app-developers app

You mean't Android 4.3 and the recovery does this for security.
To access the recovery you have to press volume up and power until it unlocks the menu.
Sent from my Nexus 4 using Tapatalk 4

You didn't read my thread!!!
andyabc said:
You mean't Android 4.3 and the recovery does this for security.
To access the recovery you have to press volume up and power until it unlocks the menu.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
I did press power key and when it's hold I pressed the volume up - it did nothing!

eyalabush said:
I did press power key and when it's hold I pressed the volume up - it did nothing!
Click to expand...
Click to collapse
You have to keep pressing it and holding it until it unlocks.
Mine and the others unlocks fine so yours should work.
Sent from my Nexus 4 using Tapatalk 4

For how long?!
andyabc said:
You have to keep pressing it and holding it until it unlocks.
Mine and the others unlocks fine so yours should work.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
For how long should i press?
I tried 10 times at least, and the result: red light...

eyalabush said:
For how long should i press?
I tried 10 times at least, and the result: red light...
Click to expand...
Click to collapse
Wait, a red light?
Are you on low battery?
Maybe it is either a low battery command, access denied to to too many attempts or incorrect combination.
Try doing the same to the up and down keys followed by the power.
Sent from my Nexus 4 using Tapatalk 4

Battery are full
The battery are full,
I tried doing all the combination , my recovery is dead!!!
any ideas?

eyalabush said:
The battery are full,
I tried doing all the combination , my recovery is dead!!!
any ideas?
Click to expand...
Click to collapse
Pressing the volume up and power key in the same time continuously?
And no I do not mean hold.
Sent from my Nexus 4 using Tapatalk 4

I also have the exact same issue. I never tried entering stock recovery before now and I tried to do it now, after updating OTA to 4.3 and rooting with wugfresh toolkit, 1.6.8. Regardless of how many times I have tried, it just reboots normally and can't access the stock recovery.

aaatoel said:
I also have the exact same issue. I never tried entering stock recovery before now and I tried to do it now, after updating OTA to 4.3 and rooting with wugfresh toolkit, 1.6.8. Regardless of how many times I have tried, it just reboots normally and can't access the stock recovery.
Click to expand...
Click to collapse
So you cannot access the recovery using the bootloader?, if so then it is probably corrupted.
I have the stock recovery image file here which you can flash via Fastboot.
Sent from my Nexus 4 using Tapatalk 4

I imagined the same. The toolkit itself, is giving you the option of reflashing the stock recovery, I think that I will try this at first. The weird thing is that the phone boots up normally, works as it should and is rooted successfully.

Actually there was no need to flash anything new. I finally made it to work. When in the "No Command" screen, you have to press the following:
1) Press only the power button first
2) While holding the power button, press the vol up button for a couple of seconds
3) Let go ONLY of the vol up button, while still pressing the power button.
Tested and working!

Just looked this up for a customer at my shop and works like a champ. Thank you
aaatoel said:
Actually there was no need to flash anything new. I finally made it to work. When in the "No Command" screen, you have to press the following:
1) Press only the power button first
2) While holding the power button, press the vol up button for a couple of seconds
3) Let go ONLY of the vol up button, while still pressing the power button.
Tested and working!
Click to expand...
Click to collapse

aaatoel said:
Actually there was no need to flash anything new. I finally made it to work. When in the "No Command" screen, you have to press the following:
1) Press only the power button first
2) While holding the power button, press the vol up button for a couple of seconds
3) Let go ONLY of the vol up button, while still pressing the power button.
Tested and working!
Click to expand...
Click to collapse
Excellent. Thanks for that. It was doing my head in.
The question is though will OTA updates still work? And the answer is yes. I flashed back to 4.2.2 and the 4.3 update came through OK. Happy days as I may well pass my N4 on soon and it needs to work 100% for a non tech wife.

aaatoel said:
Actually there was no need to flash anything new. I finally made it to work. When in the "No Command" screen, you have to press the following:
1) Press only the power button first
2) While holding the power button, press the vol up button for a couple of seconds
3) Let go ONLY of the vol up button, while still pressing the power button.
Tested and working!
Click to expand...
Click to collapse
Thank you, i was going crazy

Did my Nexus 7 just die on me?!

Hi guys, just got a new Nexus 7, and I love it - or loved; 'cause it doesn't power on anymore.
When I took it out of the box, it told me it had to update to 4.3, which it succesfully did (I checked the about tablet section in the settings to make sure). After installing 4.3, I set it up and used it for a few days, until this afternoon. I was on the train and it said it had downloaded an update. I clicked it to see the changelog and was suprised to see that it said it had to upgrade to 4.3 again.
I ignored the update and stuffed the tablet in my bag.
Here's when the trouble starts. When I took it out, it was powered off. Holding the power button for a few seconds did nothing, neither did holding it long or pressing it shortly, or vol+ and vol- and power for fastboot. Suddenly it turned on again, but it was unusable because it kept spamming "unfortunately, process.gapps. has stopt. I rebooted it into safe mode, but this didn't help. After turning it off again, it now won't start again. I don't have USB debugging enabled and couldn't get to the setting so using fastboot commands won't work.
Could anyone please help?
Thanks a ton in advance!

It was stock? Sounds like it sit down in the middle of the update. I berry flashing the latest gapps would fix..
Sent from my Nexus 7 using xda app-developers app

markvdn said:
Hi guys, just got a new Nexus 7, and I love it - or loved; 'cause it doesn't power on anymore.
When I took it out of the box, it told me it had to update to 4.3, which it succesfully did (I checked the about tablet section in the settings to make sure). After installing 4.3, I set it up and used it for a few days, until this afternoon. I was on the train and it said it had downloaded an update. I clicked it to see the changelog and was suprised to see that it said it had to upgrade to 4.3 again.
I ignored the update and stuffed the tablet in my bag.
Here's when the trouble starts. When I took it out, it was powered off. Holding the power button for a few seconds did nothing, neither did holding it long or pressing it shortly, or vol+ and vol- and power for fastboot.
Click to expand...
Click to collapse
Isn't it volume down + power button to get into the bootloader?

BTW, it's not repeatedly updating TO 4.3, the updates are FOR 4.3. You'd see the build number in About changing, while version stays the same (4.3)

You do NOT need USB debugging on to use fastboot, only adb. Fastboot works independent of anything system related. That's the whole point of fastboot.

Where have you bought your device?
I think it's the best solution to return your device to the shop you bought it and request for a new one...

just power + vol down for fastboot (after power off)
than flash factory image.... lots of guides here.

Flashing the new gapps via cwm should fix it
Sent from my GT-I9505 using Tapatalk 2

meekrawb said:
Isn't it volume down + power button to get into the bootloader?
Click to expand...
Click to collapse
Yeah, some ****ty site got it wrong. I found out and unlocked the bootloader, which factory reset it. But now it won't boot at all.

Richieboy67 said:
It was stock? Sounds like it sit down in the middle of the update. I berry flashing the latest gapps would fix..
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
That might be the case, power button must have been pressed in my pocket.
I'll try a flash of the stock rom later. I unlocked the bootloader and now it won't boot at all.

di11igaf said:
You do NOT need USB debugging on to use fastboot, only adb. Fastboot works independent of anything system related. That's the whole point of fastboot.
Click to expand...
Click to collapse
Yeah, figured that one out today. Problem was, fastboot and adb needed to be updated to verify the device.

GoneTomorrow said:
BTW, it's not repeatedly updating TO 4.3, the updates are FOR 4.3. You'd see the build number in About changing, while version stays the same (4.3)
Click to expand...
Click to collapse
Ah right, that makes more sense. Probably a wonky translation or i've misread the text. It didn't make any sense to me

Maybe you can try to use "Nexus Root Toolkit 1.7.2" and install a stock rom 4.3 from Google's repositories. But I'm not sure your tablet will let the computer modify anything if you did not accepted his ID on debugging menu.