Database Users

[Q] Broken Xoom - Please Save Me

Just gonna throw this out there and hope that somebody will have some insight…
Right now, my Xoom won’t turn on... or atleast "all the way on".
If I hold in “Volume Up” and the power button for 3 seconds (as described on the support site), it boots, gets past the moto screen and to the honeycomb animation. The animation plays for a few minutes… yes minutes until it either goes dark/off or presents a bare-bones lock screen that doesn’t respond to touch input.
Occasionally, when it reboots, it gets to the screen that has the Motorola logo and in the upper left corner, it has the text: "Starting RSD Protocol support 0". When that happens, it just freezes there. This has only happen a couple of times and I believe it had to do with variable durations of holding down the power and volume buttons. The phrase quoted doesn’t appear in either bing or google’s indexes.
Right now, the honeycomb animation has been playing for several minutes and 2 notification sounds just played… WTF
Any help would be GREATLY appreciated.

FWIW
Whatever happen, it did so under the follwoing circumstances:
1. Sent gTalk invite
2. Changed background image
3. While it was applying the new background, gTalk popped up with an incoming call.
4. I accepted the call
5. I then saw my video image in the lower right and nothing else on the screen.
6. Approx 10-15 seconds later, the Xoom rebooted.
7. Never finished the reboot, just turned off during honeycomb animation.
8. Tried that again a few times.
9. Tried the hard reboot, where you hold in the volume and power in... no dice
Sometimes, it will play a notification sound when in the honeycomb animation.
Sometimes, it will get to a generic unlock screen that doesnt respond to touch input. When that happens, and once the screen goes to sleep, I'm back to square one.
Just got off the phone with Motorola. I explained to the lady on the phone the situation and she was confident that she could help. Unfortunately, the volume / power button combo was all she had up her sleeve. She advised me to return it to BestBuy tomorrow.
Willing to bet BestBuy wont have any tomorrow... This isnt the "experience" i was hoping to get.

Just return it and get a new one? its obviously defective...

martonikaj said:
Just return it and get a new one? its obviously defective...
Click to expand...
Click to collapse
Yeah, that's what I'll have to do. Just sucks because they probably won't have any and I'll end up having to wait for another. It's lame, but I suppose its one of those "it'll do what it do" scenarios.
Sent from my Evo using the XDA App

gigglebox said:
Yeah, that's what I'll have to do. Just sucks because they probably won't have any and I'll end up having to wait for another. It's lame, but I suppose its one of those "it'll do what it do" scenarios.
Sent from my Evo using the XDA App
Click to expand...
Click to collapse
The quicker you take it back, the better off you are. They'll get new stock in and you'll be better off.

If you see that it doesn't mean its defective, it means your stuck on the fastboot screen
do this:
"Holding vol up down & power does a force normal reboot"

I just returned the device to BestBuy, exchanged it for a new one… so I’m all set.
Here are my current thoughts as to what happened (and what may happen in the future):
It really seemed / behaved like an unhandled combination of circumstances exposed what might be a couple of holes in Honeycomb. Obviously, we’re still pretty early on in the life span of this thing and many things that fell through the software validation process will likely be corrected as they are found.
Best I can figure, while attempting to write a change to (what I imagine is) a config file somewhere (when changing the background image), the process was interrupted by an incoming connection (inbound gTalk video call). That, perhaps in conjunction with the set of apps that I had loaded and were likely still present in ram, somehow made Android lose its marbles.
Throughout the night, I tried lots of different ways to reboot, and lots of attempts with no luck. However, on 3 occasions, after 30-40 minutes of not touching the device, it would start to make noise. Each time, I found that the noise was that of an incoming gTalk call and the caller (that seemed to initiate the failure) appeared on the screen accompanied by the Accept, Deny buttons. The pressing of any of the on-screen buttons resulted in the powering off of the device. Whats puzzling is that the device maintained any awareness of a call, etc, hours after it was initiated and had been hard-rebooted several times. Something wasn’t getting flushed…
I assume that once folks get a solid handle on rooting and custom ROM procedures, there will be an iron-clad way out of the hole I found myself in.

Have the same problem
I am having the same problem. will not get past the honeycomb startup animation. Did try up/down volume + power with now luck. I can get to a screen that says Starting RSD protocol support 0 but wont get past that.

VanVlack said:
I am having the same problem. will not get past the honeycomb startup animation. Did try up/down volume + power with now luck. I can get to a screen that says Starting RSD protocol support 0 but wont get past that.
Click to expand...
Click to collapse
Thats the fastboot screen, you could try flashing it at your own risk. But if it was a software glitch that would fix it.

VanVlack said:
I am having the same problem. will not get past the honeycomb startup animation. Did try up/down volume + power with now luck. I can get to a screen that says Starting RSD protocol support 0 but wont get past that.
Click to expand...
Click to collapse
FastBoot or not, I never succeeded in getting it out of that funk (any combo of either proscribed or "creative" button pushing). I dicked with it for about 5-6 hours before I cut my losses and went to bed. In terms of flashing it, I would imagine that it would work, but I personally wouldnt be comfortable enough yet. The process will get a hell of a lot more tested and vouched for in the near future.
The day after launch, I just called around to see what BestBuys had them in stock and drove out there to exchange it.

I hope that you guys are reporting your issues to Google...

never got it fixed
I never did get it out of that loop or what ever was going on. I am too an advanced user of android, from day one and it seem like more of a hardware or software problem then anything. Took it back to costco and they had me call up verizon. Went up a few tech levels. He tryed to help me get into the factory reset menu but no go on that. Got a replacement. I had my new xoom crash and go to the startup screen. Held my breath as it started back up.
Will send out a message to google and motorola letting them know.

All you had to do is hit sound up and power button it would have shutdown and once you power back up it will go into the regular boot

broken xoom
mine is stuck at the duo core screen with failed image lnx 0x002
starting RSD mode 2
i can hold the down volume button and put it in the fastboot protocol support. but when i plug it in and try to unlock it to run the factory reboot protocol from motorola my command prompt says waiting on device. i have the correct mot driver installed. any help out there

Try this post http://forum.xda-developers.com/showthread.php?t=973355
Sent from my HTC HD2 using XDA Premium App

[SOLVED (KIND OF)] Transformer display dead and stock ROM installed - warranty?!

Guys, thanks to all of you - especially frysee, who was a big help via Gtalk - the biggest part of my problem is solved:
My Transformer is still bricked and display won't turn on, but I was able to go back to stock ROM and wipe all personal data. So I won't get any trouble with warranty
If anyone is interested, me or frysee could write a How To for returning to stock ROM and retrieve warranty when screen is dead.
Thanks again!
qwer23
_____________________________________
Hi Guys!
I have a problem that is pretty common over at MoDaCo, but I haven't read anything about it here.
My Transformer sometimes doesn't turn on or wake up from sleep mode when turned on already. You can push the power button endlessly and nothing happens. Then suddenly it'll turn on as if nothing had happened.
I had this problem the first time right out of the box, so there's no bad software installed by me, don't know what ASUS did though. Perhaps it's one of the pre-installed apps.
As I said, normally it eventually comes to life again, but now I couldn't turn it on for a whole day! After I had no success, I left it on the charger over night, but still nothing this morning.
I feel I tried everything, pushed Vol Down + Power to go into recovery, pushed Vol Up + Vol Down and plugged USB to go into (useless) flash mode just to see the device to something, but no.
The only things that happen, if I push power:
- if I plug USB, the Windows plug and play sound plays and if I force shutdown the Transformer again (long-press power), the unplug sound plays. The device even appears in the Explorer and I can access SD card, but it only shows empty folders, no files in them.
- When I force-shutdown the device, I hear an internal "click" sound, similar to the one when you switch from front to rear camera, and you hear the speakers turn off. So it seems to initialize everything and stuff...
But all the time the Transformer screen stays dead
Any advice? Really need your help here guys! At MoDaCo there's no answer so far...
Regards,
qwer23

I was initially having this problem with my Transformer (it would usually happen when it had gone on standby and it couldn't get it to turn back on again) until I ran the ASUS updates on it - have you been able to update your Transformer on the occasions it did turn on for you?
If you've rooted it and stopped the OTA updates going onto it, you might just have to undo that and get an official ASUS firmware build on there to help fix the problem.

demonotter said:
I was initially having this problem with my Transformer (it would usually happen when it had gone on standby and it couldn't get it to turn back on again) until I ran the ASUS updates on it - have you been able to update your Transformer on the occasions it did turn on for you?
If you've rooted it and stopped the OTA updates going onto it, you might just have to undo that and get an official ASUS firmware build on there to help fix the problem.
Click to expand...
Click to collapse
Hi!
First of all, thx for your answer.
Well as I said, the first time the problem occured, the device was out of the box and untouched before. So I don't think it has to do with something I did.
For me it normally also happened when device was in sleep mode, except the first time out of the box
I installed a custom ROM + Clockworkmod Recovery after that, hoping it'll fix the deep sleep problem. And it really didn't happen again - until now
I didn't turn off OTA updates as I first saw that thread when the device was already dead Perhaps it tried to OTA update itself but I guess I would have to confirm this manually right? And I didn't do that...
Reflashing another ROM or the stock ROM was my first idea, too. But hell, I can't even go to recovery! No matter what I do, press, plug or unplugg, the screen stays black!

Nice, another german Transformer
"playing the plug and play sound" means you propably have adb access? Tried getting a logcat?

frysee said:
Nice, another german Transformer
"playing the plug and play sound" means you propably have adb access? Tried getting a logcat?
Click to expand...
Click to collapse
yes, being unable to wait for the german release, i imported from uk
adb gives me "device not found". even though i'm not a total noob, i don't know what i have to change to make it work. any advice? sadly i'm working while my tf is charging @home so can't really try something. i only hope you guys have some ideas
Sent from my rooted X10i using awesome custom roms

qwer23 said:
Reflashing another ROM or the stock ROM was my first idea, too. But hell, I can't even go to recovery! No matter what I do, press, plug or unplugg, the screen stays black!
Click to expand...
Click to collapse
Ahh. I didn't realise the screen was completely dead, I thought you had it working some of the time as had happened to me.
If you're seeing it in Explorer, maybe it is just a hardware failure and you'll have to get Asus to look at it...

demonotter said:
Ahh. I didn't realise the screen was completely dead, I thought you had it working some of the time as had happened to me.
If you're seeing it in Explorer, maybe it is just a hardware failure and you'll have to get Asus to look at it...
Click to expand...
Click to collapse
no i guess that it is indeed the same thing that happened to you, sometimes it worked, sometimes not. only this time it doesn't come back from the not working part I guess you see yours in explorer too if it troubles to get out of deep sleep. i guess it's just the screen that sometimes doesn't turn on for all with that problem. but for me it doesn't even turn on for booting
Sent from my rooted X10i using awesome custom roms

It's possible. I don't think I tested connecting it to the Explorer while the screen was off, I assumed it just wasn't on.
Can you test it with the HDMI out and see if that shows you what would be on screen?

demonotter said:
It's possible. I don't think I tested connecting it to the Explorer while the screen was off, I assumed it just wasn't on.
Can you test it with the HDMI out and see if that shows you what would be on screen?
Click to expand...
Click to collapse
Yeah, good idea! Will try this asap when I'm back home. Do I have to press something on the TF to enable HDMI output or is it enough to plug it in?

qwer23 said:
Yeah, good idea! Will try this asap when I'm back home. Do I have to press something on the TF to enable HDMI output or is it enough to plug it in?
Click to expand...
Click to collapse
You just plug it in.

qwer23 said:
Hi Guys!
I have a problem that is pretty common over at MoDaCo, but I haven't read anything about it here.
My Transformer sometimes doesn't turn on or wake up from sleep mode when turned on already. You can push the power button endlessly and nothing happens. Then suddenly it'll turn on as if nothing had happened.
I had this problem the first time right out of the box, so there's no bad software installed by me, don't know what ASUS did though. Perhaps it's one of the pre-installed apps.
As I said, normally it eventually comes to life again, but now I couldn't turn it on for a whole day! After I had no success, I left it on the charger over night, but still nothing this morning.
I feel I tried everything, pushed Vol Down + Power to go into recovery, pushed Vol Up + Vol Down and plugged USB to go into (useless) flash mode just to see the device to something, but no.
The only things that happen, if I push power:
- if I plug USB, the Windows plug and play sound plays and if I force shutdown the Transformer again (long-press power), the unplug sound plays. The device even appears in the Explorer and I can access SD card, but it only shows empty folders, no files in them.
- When I force-shutdown the device, I hear an internal "click" sound, similar to the one when you switch from front to rear camera, and you hear the speakers turn off. So it seems to initialize everything and stuff...
But all the time the Transformer screen stays dead
Any advice? Really need your help here guys! At MoDaCo there's no answer so far...
Regards,
qwer23
Click to expand...
Click to collapse
When it seems dead, try holding the power button for about 5 seconds (or whatever time you hold it for when turning it off)
Leave for about 2 minutes then hold power button again (like you do when turning device on) and it should boot.

checkbox111 said:
When it seems dead, try holding the power button for about 5 seconds (or whatever time you hold it for when turning it off)
Leave for about 2 minutes then hold power button again (like you do when turning device on) and it should boot.
Click to expand...
Click to collapse
Tried that a lot of times already. No help.

Phone still won't turn on, but I just realized I cannot only access my SD Card, I can also access internal storage.
Is this of any help?

qwer23 said:
Tried that a lot of times already. No help.
Click to expand...
Click to collapse
Then your ****ed!

checkbox111 said:
Then your ****ed!
Click to expand...
Click to collapse
I guess so
I'm getting a mini-hdmi cable today to determine if the screen is broken, because i have the feeling that ***** is booting but not showing anything...But I'll have to send it to ASUS nonetheless. Has anyone ever sent a device in for warranty reasons with custom software (CWM, Custom ROM) on it? What kind of trouble will I have to face?

I'd say try it with the HDMI cable, see if you get anything up on it and if the touchscreen/everything else still works, see if you can get the latest official ROM on there, see if that fixes the problem.
If nothing else, you can then send it back with an official firmware on it.

Try holding the power button for 5-10 sec, then press power + volume down (might be volume up - try both) together for another 5-6 sec. You'll get to a reset screen where it asks you to confirm if you want to wipe everything. press volume down (I think!! - read the screen carefully) instead to boot normally.
hope this helps

Its 10+ seconds for a full power off by the way, nothing shorter than that. If you changed any system files either by flashing or by pushing via ADB then you will have invalidated your warranty. Unless you can restore it to the way it was before you fiddled with it, you'll have an expensive paperweight.

sbirsen said:
Try holding the power button for 5-10 sec, then press power + volume down (might be volume up - try both) together for another 5-6 sec. You'll get to a reset screen where it asks you to confirm if you want to wipe everything. press volume down (I think!! - read the screen carefully) instead to boot normally.
hope this helps
Click to expand...
Click to collapse
Not possible since I installed CMW.
stuntdouble said:
Its 10+ seconds for a full power off by the way, nothing shorter than that. If you changed any system files either by flashing or by pushing via ADB then you will have invalidated your warranty. Unless you can restore it to the way it was before you fiddled with it, you'll have an expensive paperweight.
Click to expand...
Click to collapse
Big bummer And sadly there are no "ASUS Stores" around where I could use a stupid employee who has no clue and is convinced it's hardware related.
Well I don't have my HDMI cable by now and will try this first, but if that doesn't work:
Can someone give me a step-by-step how I can access the restore function of CWM without seeing anything on my device? I did a backup in CWM before installing the custom ROM. Perhaps tell me sth. like this: "press power+vol. down on start, then after approx. x seconds press vol up, wait a bit to make sure CWM started, press vol down twice, to go to recovery, ..."
And can someone do the same for the stock recovery to reset the device? Perhaps there's a chance that a failed OTA update deleted CWM an there's the stock recovery.
I know the chance to save it like this are small, but otherwise a lot of money is lost
Regards,
qwer23

On the flip side however, you could probably make some money by being the first to dismantle your device, and sell the photos of the internals to some website like iFixit. Then you could also sell it off as parts on eBay. Obviously it might take more effort than you are willing to give it, but at least it's another option.
If you do decide to open it up I would love to hear what mA rating the battery has on its label. Not being able to find out the actual proper rating from any site has been driving me nuts. I believe it's 6800mA but im not 100% sure.

[Q] Stuck in APX mode after bootloop

I was running the 2.99 PA rom on my Nexus 7 with m-kernel without any issues until 2 days ago, when my device rebooted and entered a bootloop, got stuck on the Google screen first, then I managed to get into the twrp recovery and erased cache and dalvik cache. Then it booted until the "X" screen and got struck there until I resetted the device by holding the power button for a while. Since then, the screen is totally dead, the only response I can get is the Windows usb device connected sound. I've tried each and every button combination and also pulled the battery but it did not help. The tablet shows up as an APX device in the device manager. I have searched the forums and I only found other people who have accindentally erased their bootloaders and then got stuck in APX, but this is not the case with my nexus as there wasn't any bootloader tinkering involved at all.
Do you have any suggestions on what I should do/try to do?

Should take 18 seconds or so.
You can get to the bootloader (fastboot mode) FROM ANY STATE.
Read that again - from any state.
See "bootloader interrupt" in this thread:
[REF] Nexus 7 Button Combinations
cheers

bftb0 said:
Should take 18 seconds or so.
You can get to the bootloader (fastboot mode) FROM ANY STATE.
Read that again - from any state.
See "bootloader interrupt" in this thread:
[REF] Nexus 7 Button Combinations
cheers
Click to expand...
Click to collapse
I've read that thread and tried the methods listed there but it didn't help. Maybe there's something else that went wrong while the device was bootlooping and corrupted the bootloader?

wasab said:
I've read that thread and tried the methods listed there but it didn't help. Maybe there's something else that went wrong while the device was bootlooping and corrupted the bootloader?
Click to expand...
Click to collapse
Quite possibly. From my limited understanding of the Tegra3 boot process, it sounds freakishly complicated. And complicated is the same thing as "lots of opportunities for bug expressions".
Also, it sounds like you had a spontaneous failure that was not temporally coincident with a flashing operation. That smells like a hardware problem, but it's hard to be certain though as you were using a dev kernel and custom ROM.
If you plug it in to the PC and then hold down the power button for an extended period of time, do you see any activity in the Device Manager that suggests that Windows is seeing a hardware state change (even if it rolls right back into APX mode?)
I'm not aware of any rescue methods at this time via APX on the Nexus 7 at this time (apparently they do exist for other Tegra devices, but the N7 experimenters using those methods have come up empty-handed so far).

bftb0 said:
Quite possibly. From my limited understanding of the Tegra3 boot process, it sounds freakishly complicated. And complicated is the same thing as "lots of opportunities for bug expressions".
Also, it sounds like you had a spontaneous failure that was not temporally coincident with a flashing operation. That smells like a hardware problem, but it's hard to be certain though as you were using a dev kernel and custom ROM.
If you plug it in to the PC and then hold down the power button for an extended period of time, do you see any activity in the Device Manager that suggests that Windows is seeing a hardware state change (even if it rolls right back into APX mode?)
I'm not aware of any rescue methods at this time via APX on the Nexus 7 at this time (apparently they do exist for other Tegra devices, but the N7 experimenters using those methods have come up empty-handed so far).
Click to expand...
Click to collapse
Holding the power button for around 10 seconds causes it to disconnect and then reconnect 4-5 seconds later. Holding the power button with any(or both) of the volume buttons has the same effect.
I did read that apx recovery thread too before posting.. What do you recommend, should I try to get it repaired in warranty as the guys in that thread did, or is it a no-go because of the custom rom and kernel?

wasab said:
Holding the power button for around 10 seconds causes it to disconnect and then reconnect 4-5 seconds later. Holding the power button with any(or both) of the volume buttons has the same effect.
Click to expand...
Click to collapse
Uh-Oh. When you do the power-button-hold-thing with a tab that behaves normally (and is plugged into the PC) you see exactly that timing: APX disappears right around 10 seconds, and then the bootloader screen pops up about 4-5 seconds later. Good news is that your tab knows you are pressing the power button - bad news is the bootloader doesn't appear at the moment it should.
wasab said:
I did read that apx recovery thread too before posting.. What do you recommend, should I try to get it repaired in warranty as the guys in that thread did, or is it a no-go because of the custom rom and kernel?
Click to expand...
Click to collapse
I can't speak from experience, but my guess is there is a technician sitting someplace with a pile of returns, and his/her bosses are breathing down his/her neck to increase the number of units turned per day. They won't be doing a forensic examination; that isn't a cost-effective way to do business. More than likely they will be replacing the motherboard if their diagnostics show the smallest hint of trouble. But I don't know for sure.
Either that or you can take this as a gauntlet thrown down and become the person that cracks open APX for the N7

bftb0 said:
Uh-Oh. When you do the power-button-hold-thing with a tab that behaves normally (and is plugged into the PC) you see exactly that timing: APX disappears right around 10 seconds, and then the bootloader screen pops up about 4-5 seconds later. Good news is that your tab knows you are pressing the power button - bad news is the bootloader doesn't appear at the moment it should.
I can't speak from experience, but my guess is there is a technician sitting someplace with a pile of returns, and his/her bosses are breathing down his/her neck to increase the number of units turned per day. They won't be doing a forensic examination; that isn't a cost-effective way to do business. More than likely they will be replacing the motherboard if their diagnostics show the smallest hint of trouble. But I don't know for sure.
Either that or you can take this as a gauntlet thrown down and become the person that cracks open APX for the N7
Click to expand...
Click to collapse
Thanks for your help! I think that I will try to solve this the easy way, but if I have no luck with that then I'm sure that I'll do some serious digging about the apx recovery.

[Q] Is it possible to retrieve files from N7 whilst dead/bricked?

Hi all
Apologies at coming on here and immediately asking for help, but....
I've had my Nexus 7 since July and have been very happy until NOW!
I seem to have been cursed with the dreaded flat battery resulting in n7 being stuck in the boot up.
I get as far as the Google and X icon but then stalls.
I've tried all the methods of long push of buttons/multiple buttons/etc but to no avail.
I can bring up the factory restore option so I know I can get it working again, but....
I have an exam in a week which foolishly had work stored for on my n7 without back up (yes fool) so....
Please is there anyway to retrieve my files via PC etc before factory resetting
All help genuinely appreciated
Mark

rooted vs unrooted (or unlocked bootloader even if not rooted) makes a huge difference in the answer.
Please state which.

Sorry about that
Not rooted.
It is absolute stock, nothing changed or added from purchase other than jellybean updates
Thanks Mark

pleading said:
Sorry about that
It is absolute stock, nothing changed or added from purchase other than jellybean updates
Thanks Mark
Click to expand...
Click to collapse
I believe you are SOL in that case. Sorry.

Find someone with a Nexus 7, pop the back cover off and use their battery to boot up and retrieve your files. The back cover just pops off.
Sent from my Nexus 7 using xda app-developers app

bigbop said:
Find someone with a Nexus 7, pop the back cover off and use their battery to boot up and retrieve your files. The back cover just pops off.
Click to expand...
Click to collapse
pleading mentions the battery, but then says "stalls" - not "shuts down", which is what you might expect if the battery was drained:
pleading said:
I seem to have been cursed with the dreaded flat battery resulting in n7 being stuck in the boot up.
I get as far as the Google and X icon but then stalls.
Click to expand...
Click to collapse
But, bigbop could be correct if pleading meant "low battery shutdown"
One other very long shot - assuming that that the device is hung - is to see if either adb or MTP are available. Normally that happens very late in the boot & I have to imagine that he has already tried that though.

Hi again guys
Firstly thanks for not giving up on my situation!
Bad explanation by me I guess....
The battery went flat/dead (my bad)
Plugged in to charge and screen lit up again but showing the 'powering off' script
Left over night on charge, wouldn't switch on again next morning
Left on charge all day still no joy but if I try switching on whilst plugged in I first get the Google name, then the Google X but then gets 'hung' (probably a better description than freezes etc as it still pulsates the colours)
Only way to get out of this is to keep power button pressed which switches n7 off and starts the cycle again
If during the recycle I keep the volume down pressed then it accesses the option screen to recover/reboot etc
Hope this helps, and again thanks (desperate to recover course work)
Mark

Hi again
Update...
Battery is showing full now
But still same 'hung' situation
Regarding the 'ADB'
I can get to the 'apply update from ADB' option
And if I choose it states.... 'now send the package you want to apply to the device with "adb sideload <filename>"'
As always thanks for any help or suggestions
Mark

Mark,
It sounds to me like what you are describing is ADB in the stock recovery, not a ADB when the regular operating system is running. (Is that right?)
Unfortunately, the stock recovery is only good for 2 things: applying an OTA update, and doing a factory reset. Even if your tablet needed an OTA update (and it probably doesn't if it is up to date), it probably wouldn't fix the looping/wedged phenomenon: usually that is caused by stuff in the userdata partition.
Doing the stock recovery factory reset might cure the wedged/looping problem - but only if it wipes all the data from your tablet. (Including the /sdcard area too).
The only hope I held out was if your tablet was reachable via a ADB or MTP with the wedged operating system sitting there looping. Usually those facilities start up quite late in the boot sequence, however so probably you don't have that.
Sorry. I think you are still SOL when it come to retrieving files.

Thanks for the help anyway
I'm guessing that with no further responses that really is the end for my work.
Unfortunately for me personally it will mean the end off my relationship with the N7, as much as I've loved it I really can't justify the obviously common occurrence of this happening.
Thanks again all

pleading said:
Thanks for the help anyway
I'm guessing that with no further responses that really is the end for my work.
Unfortunately for me personally it will mean the end off my relationship with the N7, as much as I've loved it I really can't justify the obviously common occurrence of this happening.
Thanks again all
Click to expand...
Click to collapse
I had same sort of problem N7 went flat tried to charge but would not power on
Took back panel off and disconnected battery for 10 mins reconnected battery and put back on charge
it then booted up as normal

pleading said:
Thanks for the help anyway
I'm guessing that with no further responses that really is the end for my work.
Unfortunately for me personally it will mean the end off my relationship with the N7, as much as I've loved it I really can't justify the obviously common occurrence of this happening.
Thanks again all
Click to expand...
Click to collapse
Uhhh ... what?
The OP was about a tablet that you couldn't get into because
[a] it had a correctable soft-fault
you didn't want to exercise an available soft-fault recovery method because of a desire to reclaim user files not backed up
... and so far as we know the soft-fault recovery mechanism still is available to you.
How did that morph into "this is the end"?
You need to re-do your homework, perform a factory reset, and move on with your life.
You have used either software or hardware in the past haven't you? That thing isn't a toaster or a waffle-iron! No backups of important stuff? Come on!
OK, well then. Pack it up and send it to me with the charger and I'll pay for the shipping - UPS ground.

Doesn't the Nexus have a safe-boot mode?
Sent from my Nexus 7 using xda app-developers app

bigbop said:
Doesn't the Nexus have a safe-boot mode?
Click to expand...
Click to collapse
Just tried right now - held the Vol-down button down continuously from about 2 secs after the Google B&W splash screen appeared until the lock screen appeared. That worked. (Stock 4.2.2)
"Safe mode" appears in the lower left corner. I had access to all the market apps (that I tried), but did not see a toast notification from StickMount after the boot - suggesting that safe mode only inhibits apps from starting on boot.
I suppose this could work (although the OP's deadline has probably come and gone) for bypassing a hung boot - but only if the hang is due to a market app that normally starts on boot.

[Q] Nexus 10 stuck at bootloader screen, will not do anything else

I was sitting on my couch yesterday, and my nexus 10 froze up. This is pretty normal as it freezes up alot and i have to hold the power button down for 10 seconds and restart it. But it went to the bootloader screen and now its stuck in there. I have never rooted my device or have never even attempted to, my device has been stock since day 1. Pushing the RECOVERY MODE, RESTART BOOTLOADER, START buttons do nothing but restart the device into bootloader. I have searched up and down these forums for a solution and cannot find anything, everything thats related with this problem is because of a ROOT, once again i did not root or have ever attempted to root my device. please help. here is a youtube video with the problem. BTW my device is not recognized in windows either.
Edit: so i cant post a video cause im new on the sight. Im really stuck on what to do here.

razrus said:
I was sitting on my couch yesterday, and my nexus 10 froze up. This is pretty normal as it freezes up alot and i have to hold the power button down for 10 seconds and restart it. But it went to the bootloader screen and now its stuck in there. I have never rooted my device or have never even attempted to, my device has been stock since day 1. Pushing the RECOVERY MODE, RESTART BOOTLOADER, START buttons do nothing but restart the device into bootloader. I have searched up and down these forums for a solution and cannot find anything, everything thats related with this problem is because of a ROOT, once again i did not root or have ever attempted to root my device. please help. here is a youtube video with the problem. BTW my device is not recognized in windows either.
Edit: so i cant post a video cause im new on the sight. Im really stuck on what to do here.
Click to expand...
Click to collapse
So if you hold both volume buttons + power button, then select "Recovery Mode" with the power button, it just reboots back to that same exact bootloader screen? You don't see the Android laying on it's back with a red exclamation mark over him?
Sent from my Nexus 6 using Tapatalk

charesa39 said:
So if you hold both volume buttons + power button, then select "Recovery Mode" with the power button, it just reboots back to that same exact bootloader screen? You don't see the Android laying on it's back with a red exclamation mark over him?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I was finally able to get it to a screen by holding the down volume + power that says "downloading do not turn off target nexus 10", but that still did nothing. Thats the only thing that it will let me do besides constantly rebooting to the same bootloader screen, no matter which option i choose.

razrus said:
I was finally able to get it to a screen by holding the down volume + power that says "downloading do not turn off target nexus 10", but that still did nothing. Thats the only thing that it will let me do besides constantly rebooting to the same bootloader screen, no matter which option i choose.
Click to expand...
Click to collapse
That's the Samsung Download Mode, which is different from the bootloader. Could it be possible that your volume button may be stuck, and that's why it keeps bringing you back to the bootloader? I mean, you should at least be able to boot into Recovery Mode. If not, the only solution I can think of is unlocking the bootloader and flashing the factory image. Maybe your partitions got corrupted somehow?

charesa39 said:
That's the Samsung Download Mode, which is different from the bootloader. Could it be possible that your volume button may be stuck, and that's why it keeps bringing you back to the bootloader? I mean, you should at least be able to boot into Recovery Mode. If not, the only solution I can think of is unlocking the bootloader and flashing the factory image. Maybe your partitions got corrupted somehow?
Click to expand...
Click to collapse
I dont think the volume button is stuck, when i select recovery it just restarts and vibrates twice. When i power it off and start it it vibrates once, dont know if that helps. I also remember my battery being below 15% when it froze up. My device has froze up alot since the day i got it, is that normal? maybe it did destroy the partitions.

razrus said:
I dont think the volume button is stuck, when i select recovery it just restarts and vibrates twice. When i power it off and start it it vibrates once, dont know if that helps. I also remember my battery being below 15% when it froze up. My device has froze up alot since the day i got it, is that normal? maybe it did destroy the partitions.
Click to expand...
Click to collapse
Hmm. Well, I can tell you I've never had a freeze up on mine. However, I did only buy mine a year ago, back in April of 2014. So I've pretty much only run KitKat on it before Lollipop now. Also not sure if they made any hardware revisions to get more reliability later in the device life cycle. I also pretty much only use it for media consumption like watching videos, so I'm not really doing any taxing processing tasks on it. It's weird that it vibrates twice when you try to boot into recovery. You mention your battery was low when it locked up. Have you left it charging while powered off for a while?

charesa39 said:
Hmm. Well, I can tell you I've never had a freeze up on mine. However, I did only buy mine a year ago, back in April of 2014. So I've pretty much only run KitKat on it before Lollipop now. Also not sure if they made any hardware revisions to get more reliability later in the device life cycle. I also pretty much only use it for media consumption like watching videos, so I'm not really doing any taxing processing tasks on it. It's weird that it vibrates twice when you try to boot into recovery. You mention your battery was low when it locked up. Have you left it charging while powered off for a while?
Click to expand...
Click to collapse
Really? Never froze? mine would freeze all the time, especially watching youtube videos, i just thought it was normal haha, maybe something was actually wrong with it this whole time. Ive had it for a little over a year now. The battery did die when i left bootloader on over night, but automatically started itself up into bootloader when it had some charge. i might just contact google at this point to see what they say, like i said i never have rooted it or did anything other then normal usage. maybe they can help me.

charesa39 said:
Hmm. Well, I can tell you I've never had a freeze up on mine. However, I did only buy mine a year ago, back in April of 2014. So I've pretty much only run KitKat on it before Lollipop now. Also not sure if they made any hardware revisions to get more reliability later in the device life cycle. I also pretty much only use it for media consumption like watching videos, so I'm not really doing any taxing processing tasks on it. It's weird that it vibrates twice when you try to boot into recovery. You mention your battery was low when it locked up. Have you left it charging while powered off for a while?
Click to expand...
Click to collapse
Really? Never froze? mine would freeze all the time, especially watching youtube videos, i just thought it was normal haha, maybe something was actually wrong with it this whole time. Ive had it for a little over a year now. The battery did die when i left bootloader on over night, but automatically started itself up into bootloader when it had some charge. i might just contact google at this point to see what they say, like i said i never have rooted it or did anything other then normal usage. maybe they can help me.

So I called google and they transfered me to samsung, and samsung transferred me to google. no one seems like they could possibly help me. This is frustrating and i dont think ill buy another nexus tablet, or anything nexus for that matter. i dont even think i can sell this on ebay at this point, and if someone were to be able to get it up and running, all my data might still be on there. ARRRGGGHHH ive never owned something that has "bricked" and not been able to fix it. this one looks hopeless.

razrus said:
So I called google and they transfered me to samsung, and samsung transferred me to google. no one seems like they could possibly help me. This is frustrating and i dont think ill buy another nexus tablet, or anything nexus for that matter. i dont even think i can sell this on ebay at this point, and if someone were to be able to get it up and running, all my data might still be on there. ARRRGGGHHH ive never owned something that has "bricked" and not been able to fix it. this one looks hopeless.
Click to expand...
Click to collapse
That sucks. I can empathize as I (and I'm sure plenty of others) know how it feels to get the runaround. Always frustrating. Well, I am thinking the only shot at possibly getting it working again is to unlock the bootloader and flash a factory image. Chances are always good that with a Nexus (barring any hardware issues), flashing a factory image will get it running again. That's why it's Nexus only for me, as Nexus devices are virtually unbrickable. Not sure if you have any experience with Fastboot and ADB. If not, I'm sure you can find some useful research tools on the interwebs and here on XDA. Once you understand it, here are a couple threads with some simplified installers: http://forum.xda-developers.com/showthread.php?t=2588979 and http://forum.xda-developers.com/showthread.php?t=2317790. Do keep in mind that UNLOCKING THE BOOTLOADER ERASES YOUR DATA, so you will lose everything on your N10. But at this point, it's all about getting it working again so you're not stuck with a $300 paperweight.

charesa39 said:
That sucks. I can empathize as I (and I'm sure plenty of others) know how it feels to get the runaround. Always frustrating. Well, I am thinking the only shot at possibly getting it working again is to unlock the bootloader and flash a factory image. Chances are always good that with a Nexus (barring any hardware issues), flashing a factory image will get it running again. That's why it's Nexus only for me, as Nexus devices are virtually unbrickable. Not sure if you have any experience with Fastboot and ADB. If not, I'm sure you can find some useful research tools on the interwebs and here on XDA. Once you understand it, here are a couple threads with some simplified installers: http://forum.xda-developers.com/showthread.php?t=2588979 and http://forum.xda-developers.com/showthread.php?t=2317790. Do keep in mind that UNLOCKING THE BOOTLOADER ERASES YOUR DATA, so you will lose everything on your N10. But at this point, it's all about getting it working again so you're not stuck with a $300 paperweight.
Click to expand...
Click to collapse
Is it possible to flash even though it's not recognized by windows?

razrus said:
Is it possible to flash even though it's not recognized by windows?
Click to expand...
Click to collapse
It's not recognizing it because you need the drivers so it knows it's connected in bootloader mode.

charesa39 said:
It's not recognizing it because you need the drivers so it knows it's connected in bootloader mode.
Click to expand...
Click to collapse
i have the device up and working now! Thank you so much for you help! I had to unlock my device with the nexus root toolkit after installing that usb fix you suggested, then i had to flash it, but the 5.1 update would get stuck in a bootloop, so i installed 4.4 and it worked. Lost all my data but thats ok. Thanks so much.:highfive:
Edit: Google play was not working, tried updating android software and it got stuck in the bootloop again. will try and tweak it more tomorrow, im gunna look for other custom firmwares as well, dont have to have stock anymore.

razrus said:
i have the device up and working now! Thank you so much for you help! I had to unlock my device with the nexus root toolkit after installing that usb fix you suggested, then i had to flash it, but the 5.1 update would get stuck in a bootloop, so i installed 4.4 and it worked. Lost all my data but thats ok. Thanks so much.:highfive:
Edit: Google play was not working, tried updating android software and it got stuck in the bootloop again. will try and tweak it more tomorrow, im gunna look for other custom firmwares as well, dont have to have stock anymore.
Click to expand...
Click to collapse
That's great to hear. I'm glad it came back to life. :good: Although, I wouldn't suggest using a toolkit. In my experience from what I've seen around these forums, they tend to cause more harm than good. It's good if you understand everything that's going on, and they can prove useful for devices that have really complex unlocking and rooting procedures, but Nexus devices are so easy to unlock and flash manually. I always flash each image file manually so if something goes wrong, I know exactly where it went wrong and how to fix it. The Google Play issue you mentioned is a perfect example. Flashing manually also helped me learn the basics of Fastboot and ADB. So if you want to stay on stock 5.1, I would recommend reflashing the factory image manually. I always use this thread to help me out in case I forget something: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. Although it's for the Nexus 6, it's the same procedure for the Nexus 5, Nexus 10, Nexus 7, etc. That's the real convenient thing about Nexus devices as well, as they are all pretty much flashed the same way. Should all be really simple since you already have the drivers set up from installing the toolkit. Good luck! And have fun with your newly revived N10.