Database Users

***For those who are experiencing freeze ups***

Hello people, I thought I would inform you all of a much better and effective method to deal with your phone freezing. Many of us are using custom kernels such as nemesis2all's OTB or imnuts peanut butter jelly time in which have a tendency to freeze our phones due to the overclocking/undervolting. Or, we are on JT's new CM7 mtd or Andmer's GB MIUI and our screens will turn off and nothing that we do will turn them back on. The natural reaction to this occurrence is to take the back off the phone and pull the battery out. But, this is not good for it to be abruptly pulled in the midst of supplying power to your phone. Not to mention the severe battery drain that comes along with doing this, as I'm sure many of you have already noticed to be the case. No matter what rom/kernel you are on and no matter how frozen your phone is, if you simply hold both the volume up and volume down buttons and the power button at the same time for about 10 seconds, your phone will do a hard reboot. Problem solved without doing harm or damage to your phone and without excessive battery drain. This method even works for CM7 MTD/GB MIUI MTD. This is not the same thing as the three finger method that you are warned not to do with these roms. This method will lead to overall better battery life and phone life. Not to mention, a lot less frustration.

I think just vol UP + power works, but either way.. it's a useful trick to know!

And especially helpful if you have a case on
Sent from my SCH-I500 using XDA Premium App

Good to know. I broke my case by taking it off and on so many times. It's still useable but this will prevent further damage, and save me some time.
Sent from my SCH-I500 using Tapatalk

elarson006 said:
I think just vol UP + power works, but either way.. it's a useful trick to know!
Click to expand...
Click to collapse
+1. This is what I use. Just had to do it this morning as a matter of fact.

elarson006 said:
I think just vol UP + power works, but either way.. it's a useful trick to know!
Click to expand...
Click to collapse
Indeed. I never do battery pulls personally.

verizon techs have had me do battery pulls a couple different times lol.

droidstyle said:
verizon techs have had me do battery pulls a couple different times lol.
Click to expand...
Click to collapse
Yea, but not while the phone is on and in a frozen state with a steady stream of battery power being supplied to it, I assume. That is very different.
Sent from my SCH-I500 using XDA Premium App

kidserious said:
Yea, but not while the phone is on and in a frozen state with a steady stream of battery power being supplied to it, I assume. That is very different.
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
Power on but not frozen... but I agree its not good to pull battery in frozen state... volume up and power button is what I do in that situation. My SF has only froze two times and that was from overclocking... not very stable over 1200 on the stock rom. Srry hope my last post did not offend, I meant as verizon was dumb for having me pull the battery with power on!

droidstyle said:
Power on but not frozen... but I agree its not good to pull battery in frozen state... volume up and power button is what I do in that situation. My SF has only froze two times and that was from overclocking... not very stable over 1200 on the stock rom. Srry hope my last post did not offend, I meant as verizon was dumb for having me pull the battery with power on!
Click to expand...
Click to collapse
No, post was not offensive nor was it was taken that way. Sorry if I gave the wrong impression.

landshark68 said:
+1. This is what I use. Just had to do it this morning as a matter of fact.
Click to expand...
Click to collapse
It's what I use as well, power+both volume buttons does nothing for me, I think technically power+volume up is a soft reboot, but, it works.

I will use this next time... My phone froze up this morning. I thought I was going to have to pull the battery and just as I was tapping the battery out of the phone I saw the bootlogo. When I put the battery back in my /data was gone. Phone would boot, but there was no data partition. It was toast.
Had to Odin back to stock and start all over. My last Titanium Backup is from more than a month ago. I have a Super Manager backup from ~ a week ago. Will give it a shot.

Bricked or not bricked......

well I decided to mess around with cm7 once I saw that it had 4g.
I probably should have done some more research on the differences between mtd and bml before trying to go back to a bml rom from cm7.....
Now for the first time ever I think I bricked my phone since I can't even get it into download mode to restore with odin.
Just really wanted to see if anyone had any suggestions on something I might be missing before I take it back to sprint and probably have to pay something
Thank you

Hold the little pin down by the camera for 30 seconds. Cover has to be off to access it. Or try leaving the phone alone for an hour with the battery out, and then use odin, but do it with the battery out. The computer will power the phone for you.
Sent from my SPH-D700 using XDA App

best way to know is take battery out and hold power + 1, while holding them down plug usb in

HumanXv2 said:
best way to know is take battery out and hold power + 1, while holding them down plug usb in
Click to expand...
Click to collapse
This. Also take sdcard out
Sent from my SPH-D700 using xda premium

Others have had success by popping the battery in and out a few times while attempting to get into download mode. But mostly try no battery, no sd card, connect to computer and try download mode.

Yea I ended up remembering this from way back when I first got the phone, took the battery out for 15 seconds and put it back in and got into download mode and restored the correct tar thsi time not just the modem tar i had....

Thanks for all the quick replies though

b16flybye said:
Hold the little pin down by the camera for 30 seconds. Cover has to be off to access it. Or try leaving the phone alone for an hour with the battery out, and then use odin, but do it with the battery out. The computer will power the phone for you.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Wow another "I believe in magical reset buttons" guy..... there's no button if you take it apart it was from leaving the battery out long enough that makes people believe this. Leaving the battery out usually drains the charge and resets the phone somehow....
Sent From My Cyan Samurai

Biggoron said:
Wow another "I believe in magical reset buttons" guy..... there's no button if you take it apart it was from leaving the battery out long enough that makes people believe this. Leaving the battery out usually drains the charge and resets the phone somehow....
Sent From My Cyan Samurai
Click to expand...
Click to collapse
No, no, no....if you listen, late at night, outside Sprint stores, the wind whispers tales of mythical Epics that have magical buttons that were installed by tiny technical elves. There have been sightings, those that will swear this has resurrected the dead...zombie Epics if you will....fact or fiction...you decide!

b16flybye said:
Hold the little pin down by the camera for 30 seconds. Cover has to be off to access it. Or try leaving the phone alone for an hour with the battery out, and then use odin, but do it with the battery out. The computer will power the phone for you.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Lol... I love this... have you ever taken apart ANY epic that had this "button"? I've taken apart more than 50 and still haven't found not 1 button! Please somebody post a picture of this so called button if it is real... not the hole by the camera but the actual button on the board... its not there trust me...
Sent from my SPH-D700 using Tapatalk

kennyglass123 said:
No, no, no....if you listen, late at night, outside Sprint stores, the wind whispers tales of mythical Epics that have magical buttons that were installed by tiny technical elves. There have been sightings, those that will swear this has resurrected the dead...zombie Epics if you will....fact or fiction...you decide!
Click to expand...
Click to collapse
Hahaha that's too funny
Sent From My Cyan Samurai

lol at least it gives faith to people who accidently soft brick! XD I use to believe so I'm not even poking fun lololol
Sent from my SPH-D700 using xda premium

kennyglass123 said:
No, no, no....if you listen, late at night, outside Sprint stores, the wind whispers tales of mythical Epics that have magical buttons that were installed by tiny technical elves. There have been sightings, those that will swear this has resurrected the dead...zombie Epics if you will....fact or fiction...you decide!
Click to expand...
Click to collapse
LOL ... LOL ......... That is CLASSIC !

When I saw this thread I was hoping it was a poll.

my xoom appears to be dead (?)

Hello, android developer here.
The other day my xoom drained all the way to 0% (this happened overnight while I was asleep). I noticed right away because I use the xoom as my alarm clock. I ended up sleeping in that day (doh!)
Anyways, now the darn thing simply wont turn on. I try to soft reset (vol up + power) but nothing happens. I tried plugging it in via usb thinking I could reboot it with adb, but my computer fails to see the device. So its turned off and simply will not turn on. I've even let it charge for 2 days straight (green charge light on device).
Nothing.
What the heck man?

Dumb question.... How long have you held the power button? My Xoom (maybe others?) won't turn on unless I hold the button for 2-3 seconds.

Ive gone up to 60 seconds of button pressing...when it doesnt work one tends to go to extremes lol
I can't believe this, first time I've ever had a device die like this :-/

Did you charge it before you tried to turn it back on? My Milestone tends not to turn on after it drained below zero for like ten minutes until the battery has at least some basic charge again.

Try turning on right 3~4 minutes later putting on a yiur charger
Sent from my MZ605 using XDA App

Zhenech said:
Did you charge it before you tried to turn it back on? My Milestone tends not to turn on after it drained below zero for like ten minutes until the battery has at least some basic charge again.
Click to expand...
Click to collapse
Yeah its been charged for 48 hours now, green light on power indicator as well.
It still wont boot. I tell ya its the strangest thing I've seen in a while...

did you try booting in recovery? vol down ±power

zylith said:
did you try booting in recovery? vol down ±power
Click to expand...
Click to collapse
Of course. I've tried every combo imaginable.
F this, I'm getting an ipad.

techs1200 said:
Of course. I've tried every combo imaginable.
F this, I'm getting an ipad.
Click to expand...
Click to collapse
If you really want the iPad, here's the perfect excuse.
However, if you want to save your Xoom, you might want to check out the Motorola Factory cable from Team Black Hat (Google it). If there was ever a use for this cable, your situation seems to define it. Your Xoom seems to think it's not charged (drained) or can't take a charge, but it sounds more like the former situation. The Factory/Programming cable obviously makes a different electrical connection and makes the Xoom think it's charged...something like that. Check it out.
Also, at least one person made one out of a usb cable and it saved his bacon. You'll have to do a search for his thread...it was a while back.
Good luck, what ever you do.

You need to make or buy the motorola factory cable. That will get you booting.
Sent from my Xoom using xda premium

Well I did buy an iPad2 a few days ago, but I will definitely be making one of those cables.
Wow, thanks so much! XDA never disappoints

Remove your SD card then restart... Happens to me all the time..
Sent from my GT-N7000 using XDA App

davidblaine021 said:
Remove your SD card then restart... Happens to me all the time..
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
Yes, I have seen this also. Pull out the SD card and the unit comes back to life.

Great its frozen

Running fine for a day, then suddenly when i looked at the screen it was at the "Asus" screen (with the logo and spinny thing below) - i touched the screen and it froze.
And now its frozen.
And I had just charged it...grrr - do i really have to wait 12 hours or however much it takes before the battery is depleted.
I wonder if there is a way to reset it.

Kermode said:
Running fine for a day, then suddenly when i looked at the screen it was at the "Asus" screen (with the logo and spinny thing below) - i touched the screen and it froze.
And now its frozen.
And I had just charged it...grrr - do i really have to wait 12 hours or however much it takes before the battery is depleted.
I wonder if there is a way to reset it.
Click to expand...
Click to collapse
Hold the power button down.
Sent from my Galaxy Nexus using XDA App

Happened to several guys.
Did you try to press and hold power for ten or more seconds? It should power off and you should be able to power it on again.

this is happened to me 3 times so far.
Hold the power button to power off and reboot.
For mine after it boots it'll run ok for a minute or so, then run horribly slow until the launcher crashes. after the launcher starts back up it'd be ok.
Did you hard reset before the OTA? Where you stock, stock rooted, cwm flashed? Just trying to get more info.

fone_fanatic said:
this is happened to me 3 times so far.
Hold the power button to power off and reboot.
For mine after it boots it'll run ok for a minute or so, then run horribly slow until the launcher crashes. after the launcher starts back up it'd be ok.
Did you hard reset before the OTA? Where you stock, stock rooted, cwm flashed? Just trying to get more info.
Click to expand...
Click to collapse
We are having way too many threads for the same issue...
Mine still experiences the problem after a factory reset.
As everyone mentioned, holding down the power button fix it temporarily.
Someone else reported that you can avoid the random reboot problem by disabling deep sleep using no sleep widget, although it's a crude walkaround.
Sent from my HTC Sensation 4G using XDA App

Just an idea but what if you use something like SetCPU and up the lower frequency. Had this issue on a kanged ICS rom for my phone. It wasn't the deep sleep that was the problem but the lowest frequency was too low to re-initialize the apps that were cached once you woke it up.
I did a full complete wipe and updated from .13 to ICS and am not going to jinx myself by saying what I am implying. If you know what I mean.

Interesting, and I do agree that there are too many threads, since I am trying to get some idea of how common this is. I think I was the original poster on this, but in any case in my particular situation I tried holding the power button down, resetting it through the reset hole, and holding the power button in while pressing the volume button down (this did give me the option of reformatting which I tried) but in every case it simply flashed the eedpad screen. The battery finally appears to have died and I'm trying to recharge it now, but so far it is now completely dead. All of this happened after it went into deep sleep. This tablet is 100% original, never been rooted or tampered with in any way so, unless this is a coincidence or a combo of ICS and one of the apps I have in it, I expect this to become a very common occurence. Anyway, I'll let it charge for a bit and see what happens. I already have an RMA (the service person didn't seem too surprised and didn't really try much trouble shooting - when I asked if he had heard of this before he kind of said I wasn't the first) so I'm sending it back to Asus on Monday so that when I get it back I can sell it, but I'm just wondering what percentage of people are having this problem. Heck, if it's even just 5% Asus is going to have a major expense on its hand.

I had the dreaded Asus logo freeze twice now, since the ics update. Both times when I wasn't using the tablet.
Sent from my Galaxy Nexus using Tapatalk

Mine has frozen 2x already since the ics update. I performed a factory reset before and after the update.
Screen just goes black/blank and would have to hold the power button for 10secs.
Sent from my Transformer TF101 using Tapatalk

Hey thanks, I thought I had pressed power down for long enough - but apparently not.
I was on normal HC and just accepted the update when it prompted me for it.
But if a lot of people are seeing this i guess Asus made a little blunder in this version.

I just came in after leaving my Transformer asleep for about three to four hours, and found the asus logo flashing on for a few seconds and then off, repeating over and over. Had to do a reset with power and vol down to get it to reboot. Seems OK for now except it really drained the battery.
I guess there will be a few ICS bugs to work out.

jparity said:
We are having way too many threads for the same issue...
Mine still experiences the problem after a factory reset.
As everyone mentioned, holding down the power button fix it temporarily.
Someone else reported that you can avoid the random reboot problem by disabling deep sleep using no sleep widget, although it's a crude walkaround.
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
About the "No Sleep" widget, that was me. Well, this seems to be a widespread issue. Asus should take the update back and stop offering OTA...this is a pretty big issue.
Sent from my GT-I9100 using XDA App

msaraiva said:
About the "No Sleep" widget, that was me. Well, this seems to be a widespread issue. Asus should take the update back and stop offering OTA...this is a pretty big issue.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Well asus is good about providing prompt follow up updates so I wouldn't be surprised if we start getting bugfix updates in the coming weeks.

Yea seems like the TF only goes crazy when it's in sleep/not being used.
Mine is not rooted so I don't really want to go through the trouble changing processor frequency.
Where is the reset hole btw?...
Sent from my HTC Sensation 4G using XDA App

It's next to the hdmi port.
jparity said:
Yea seems like the TF only goes crazy when it's in sleep/not being used.
Mine is not rooted so I don't really want to go through the trouble changing processor frequency.
Where is the reset hole btw?...
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse

r_nt said:
It's next to the hdmi port.
Click to expand...
Click to collapse
Isn't that the mic? I don't believe that's a reset button. I could be wrong though
Sent from my Transformer TF101 using xda premium

eminembdg said:
Isn't that the mic? I don't believe that's a reset button. I could be wrong though
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
There isn't holding the power button for 15 seconds resets it.
Sent from my Transformer TF101 using Tapatalk

r_nt said:
It's next to the hdmi port.
Click to expand...
Click to collapse
I thought it's the mic too... Does your voice record still work after you "reset" your TF?...
Edit: Saw the dreaded Asus loading screen again when I came back from dinner... 3rd time today... It's getting on my nerves a bit now. Such a pity that the TF is perfect besides this issue... I don't care if it reboots every hour or so, as long as it doesn't hang and depletes the battery.

Just to clarify, and so others don't break their microphone,THERE IS NO RESET HOLE! if your device is frozen, hold the power button to reset.
Are we certain its the deep sleep causing this?
Didn't happen to me this morning. I stopped using it around midnight and woke up fine the next day.

fone_fanatic said:
Just to clarify, and so others don't break their microphone,THERE IS NO RESET HOLE! if your device is frozen, hold the power button to reset.
Are we certain its the deep sleep causing this?
Didn't happen to me this morning. I stopped using it around midnight and woke up fine the next day.
Click to expand...
Click to collapse
How do you it didn't happen? It doesn't get stuck at the ASUS logo for me, it simply reboots. Try leaving something open, like a browser window, turn off the screen and come back sometime later. If it's back to the homescreen and there are no recent apps, then it rebooted.
I don't know if it is the deep sleep that is causing it. All i know is that the bug is only triggered while sleeping. Every logcat i get stops at an AlarmManager event, before the reboot.
Sent from my Transformer TF101 using XDA Premium HD app

Help me get out of APX mode it is really jammed up.

This is not another just my Nexus 7 won't turn on after running out of battery or regular SOD problem. I dirty flashed to the latest LeanRom from Smoothrom 4.3 and it was running well through out the day with the exception of SOD's during the day about 3 or 4 times. I used it until 23% battery and it shut off. I plugged it in and it was rather difficult to get it to boot through button pushes holds and combos. It booted up and I used it while it was charging untill it was around 70% battery and I went upstairs with my tablet and got in bed and used it for a while... It was around 60% and I plugged it in again and went to sleep. Keep in mind I left it overclocked as I always do with M-kernel b35 *1.7ghz default kernel voltage. and GPUat 766mhz 1295mhz voltage. Keep in mind I always manage my Temps. via apps and it never gets hot in my hand not even very warm. Only spot it would ever get even a little warm is lower left back where I think the CPU or GPU is located because that is where the Heatsink is located. I am not sure if it possibly overheated and fried it.. But as I said I have had a generous overclock on it for 3 months. Again it never became very hot ever! Anyways that morning I grabbed it and hoped in my dads car and as usual it had SOD'ed overnight. I began holding the power button for a few mins. A couple of times. It went too the Google logo with the unlocked bootloader and then i tried to turn it off and boot it again because the kernel has never been friendly with the 3.34 boot-loader. It has always had a weird time starting the os and me having to hold the power button untill it goes black and starts the Google logo and then shows my boot-loader and will start up and I release the power button. Well after that last Google logo I have not been able to power it on at ALL not even backlight glow I have charged it 15 hours and nothing. I have spent HOURS researching this and there are no links on Google that have helped. It is not the regular SOD or out of battery not starting issue. It also it not recognized by my computer and I can only see that it thinks it is called APX or something by my computer. I was hoping that some one could help. I even removed my battery and plugged it back in. I have tried all button pushing nothing... I have called ASUS but there warrenty BLOWS. Any help would be much loved =] I love my nexus =[
@@[email protected]@-- [email protected]@[email protected]@--Haha so guess what Asus fu ( ked me royaly after paying $30 dollars for shipping to Grapevine Texas and my tablet is still not turning on. It's not the charger or cord I have tried enough of those to know its not that. Is there any hope at all or am I sending it in again... also there "tech repair" people ****ed the **** out of my tablet under the hood the battery was lose yes I know I tried that too. The copper heat sink was ripped and sticking up. Stickers ripped apart. They had better send me a refurb back. To the guy before I was simply refuring too when I dirty flashed. Not that the def had anything at all to do with it. It was my dirty flash. I am rather mad about sending it in again. Any advice.. Thanks!!!

I now realize that it is APX mode WTF how in the world can I get out of it without a replacement is there anyway at all???

http://forum.xda-developers.com/showthread.php?t=1789135&page=2
Mabey ill button jam while in comp for a while and see =/
situation seems grim...

If it is in APX mode, it will take 15+ seconds of holding the power button continuously to get a restart.
IF that is the case, the black-and-white Google logo will come up - if you press Vol-Down precisely at that moment, the tablet will proceed to the fastboot screen. If you don't press Vol-Down, the tablet will attempt a normal boot.
Assuming that the hardware is not damaged and the battery has a decent charge, you can always get to the fastboot/bootloader
...it was running well through out the day with the exeption of SOD's during the day about 3 or 4 times...
Click to expand...
Click to collapse
LOL. You seem unusually tolerant of non-determinism.
good luck

bftb0 said:
If it is in APX mode, it will take 15+ seconds of holding the power button continuously to get a restart.
IF that is the case, the black-and-white Google logo will come up - if you press Vol-Down precisely at that moment, the tablet will proceed to the fastboot screen. If you don't press Vol-Down, the tablet will attempt a normal boot.
Assuming that the hardware is not damaged and the battery has a decent charge, you can always get to the fastboot/bootloader
LOL. You seem unusually tolerant of non-determinism.
good luck
Click to expand...
Click to collapse
Hey, thanks for responding to my thread. The issue is that my tablet will not respond to anything that I do. When/if I get a new one I may not overclock the GPU as high as that may be why my tablets *****ed*

bump..

It'd be awesome if someone could be of assistance on this issue because I think it could come in handy in the future for people.
Thanks.

[QUOTE=Nexus7
As far as apx mode no one knows how to fix it yet your tablets basically a paper weight.. Sorry dude, you can attempt to send it back and see if they will fix it but that's basically all you can do right now, or sell it for parts
Sent from my Nexus 7 using Tapatalk HD

OK so now i'm wondering if ASUS RMA will know I'm rooted and charge me.. The guy on the phone asked me if I wanted my os restored I said no but I'm a lil worried. Also in USA does ASUS RMA take forever and will they prob. send me a shiity refurb?

xfrancis14 said:
As far as apx mode no one knows how to fix it yet your tablets basically a paper weight.. Sorry dude, you can attempt to send it back and see if they will fix it but that's basically all you can do right now, or sell it for parts
Click to expand...
Click to collapse
Uh, what? This is only the case if you borked the bootloader, which should still be intact in his case. Apx mode is basically a service mode that's even lower than the bootloader, it's just that we don't know how to use it.
I insist that you keep holding the power button or perhaps play with the charge more.
Sent from my SGH-I777 using xda premium

korockinout13 said:
Uh, what? This is only the case if you borked the bootloader, which should still be intact in his case. Apx mode is basically a service mode that's even lower than the bootloader, it's just that we don't know how to use it.
I insist that you keep holding the power button or perhaps play with the charge more.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
I have trust me it's not turning on at all. Thanks for replying any other suggestions are much loved and needed lol. I have until Monday when I mail it out to get it fixed.

Nexus7<3 said:
I have trust me it's not turning on at all. Thanks for replying any other suggestions are much loved. I have until Monday when I mail it out to get it fixed.
Click to expand...
Click to collapse
EDIT_ I ducked taped my power button down and i'll see if maybe it comes out of APX death-mode. Also what are the possibilitys I fried a internal inside such as power supply. CPU or GPU? with the overclock...

Nexus7<3 said:
EDIT_ I ducked taped my power button down and i'll see if maybe it comes out of APX death-mode. Also what are the possibilitys I fried a internal inside such as power supply. CPU or GPU? with the overclock...
Click to expand...
Click to collapse
Yepp deader than a door nail. Any ideas are helpful

Nexus7<3 said:
Yepp deader than a door nail. Any ideas are helpful
Click to expand...
Click to collapse
Out of the 400 ish people who have viewed the thread there are 0 suggestions or hints?

[QUOTE=Nexus7
Sorry dude there's no hope, not trying to be mean but there's simply no hope
Sent from my Nexus 7 using Tapatalk HD

766mhz was a silly number to go to for a chip that doesn't even have air cooling. Sorry, but you were asking for that to happen, whether you felt it getting hot or not... It was trying to tell you something by not starting up and crashing overnight all those times...
Sent from my Nexus 7 using Tapatalk HD

knuckles1978 said:
766mhz was a silly number to go to for a chip that doesn't even have air cooling. Sorry, but you were asking for that to happen, whether you felt it getting hot or not... It was trying to tell you something by not starting up and crashing overnight all those times...
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I don't really think I fried it now tbh. I think the Rom did it

Nexus7<3 said:
I don't really think I fried it now tbh. I think the Rom did it
Click to expand...
Click to collapse
I don't think so at all. I think YOU fried it. I don't mean to be harsh but you can't blame the dev's around here because you OC'd your tab way to high, and killed it.
As stated before, did you not think the SODs were trying to warn you of something.

Nexus7<3 said:
I now realize that it is APX mode WTF how in the world can I get out of it without a replacement is there anyway at all???
Click to expand...
Click to collapse
If you got in APX mode then the bootloader is gone for good. The tablet is not able to boot any more.
It happened the same to me while flashing the 4.2.2 stock ROM: something went wrong right after the "fastboot erase xxx" commands and my tablet died.
I have searched the internet for any solutions but I failed miserably. I reverted to ship the tablet back to Asus for assistance.
Well, they picked up the package on Thurs 21 and I got my tablet back on Tue 26.
Repair was covered by warranty even though I had the bootloader unlocked (that's a mandatory step in order to flash a stock rom from Google).
They actually replaced the mainboard instead of reflashing the firmware.
That suited me fine.

slvrbllt said:
If you got in APX mode then the bootloader is gone for good.
Click to expand...
Click to collapse
N7s that are operating correctly can enter and exit APX mode at will; by itself, APX mode does not necessarily indicate a problem. ( Failure to get the boot loader to appear obviously is a problem.)
For devices operating normally:
- From power off, Vol-Up+Pwr (3 seconds) puts the N7 into APX mode.
- From APX mode, holding power for 15+ secs loads the bootloader - which will attempt loading the (regular) boot partition. If the Vol-down button is pressed within about 1 second of the b&w Google logo appearing, this boot sequence is interrupted and the boot loader proceeds to fastboot mode.
Just a clarification that seeing APX mode does not necessarily equal disaster. As you were!