Database Users

Bricked Acer Iconia A501, Need Help Plz

I have a brick A501 that when turn on, it stays at android logo and wont boot...i tried to flash it with SD card, vol- +power with full package file, update.zip, but the phone just wont boot to flash mode....tried vol+ power it shows update pack=sd.update.zip..booting recovery kernel image and stuck there...
phone was brought in this stage and don't know the history..how to unbrick this phone please?

I'll take it you bought this used? And didn't bother to check it first?
Or if it was bought from a legitimate retail store. it would be just as easy to return or exchange it?
Regardless, 2 things you can try.
1. Hold vol - and power. Hold until you see small words in the upper left corner. Then release and wait 30 seconds. If it had a custom recovery installed, then probably somebody tried installing custom roms and messed things up. If you do indeed have a custom recovery, then don't do something stupid. Just power down the system, and post the results here.
2. You can try the pinhole reset near the power on/off button. Not sure of the exact procedure, but maybe tablet off. Hold in the pin then power on. You might do a google for the exact procedure.
The bad thing, is that you give very little history, so we'll have to try several things.
EDIT: Forgot to tell you, it is a Tablet, not a phone.

this is the solution .... but it works only if you were debugging active on usb
http://forum.xda-developers.com/showthread.php?t=1276227
but uses this file http://www.multiupload.com/04TU1DYHIZ

tresed said:
this is the solution .... but it works only if you were debugging active on usb
http://forum.xda-developers.com/showthread.php?t=1276227
but uses this file http://www.multiupload.com/04TU1DYHIZ
Click to expand...
Click to collapse
Thanks for your reply...First of all my customer brought the phone to me for repair. Maybe he was playing around with the updates and custom roms...
Anyways phone now cannot boot, only shows android...I followed the EUUs procedure, power off, push and hold reset, then power, it shows as APX device and install automatically after I did the reset+power...but the EUUs cannot find the phone after done reset+power...
As I mentioned, when I tried SD card method, Vol down +power, it won't go into flash mode..again the phone state now is when turn on, it's stuck at android..when i press vol up + power, it shows boot recovery then show and stuck at green android guy and sometime stuck at acer logo....thanks for taking time to help...i appreciate that.

No Problem.
The fact you still have life, means it can probably get up and running again.
In the 500 forums, there is some info about APX mode, and a couple users that managed to get it running again. You'll just have to look hard.
If I find it, I'll post a link here later. I just can't remember where it was
---------- Post added at 05:11 PM ---------- Previous post was at 04:48 PM ----------
Also, refine your search for the term "APX" to search within the threads. Not the title. I remember it being buried within a thread.
And now, must do some work.
---------- Post added at 05:36 PM ---------- Previous post was at 05:11 PM ----------
Another thing,
Saw a user who couldn't flash a rom (data wasn't getting wiped)
Although he did still have a recovery menu, it wouldn't wipe the data (probably a corrupted recovery.
Somehow, he installed the AcerRecovery to his pc, and was able to communicate with the tab, and re-flash a fresh recovery.
He managed to be able to install a rom.
So, you might also try that as well. AcerRecovery is in the market.
Also, booting to the normal recovery (if installed), is PWR and Vol -. Not +. Hold till you see the text in upper lt corner.

Thanks again for your help..but up until now, after many hours of searching for solution, I still cannot fix this tab..I got the phone to be in APX mode (reset +power), on the screen it does not show anything but PC recognize and device manager under USB shows as NVIDIA USB Boot-recovery driver for Mobile Device..I tried to use USBView to get UID, it shows weird numbers and letters under Instance ID,USB\Vid_0955&Pid_7820\6&d26abb4&0&4, instead of 15 # and letters as it suppose to.
Besides that, when I run the EUUS software update when it tells me to press reset +power, and YES, it didn't see the phone in APX mode and won't proceed...
I notice there's SNID # and IMEI # under the simcard and SDcard cover..can we use one of these # to get UID?
Any hope I can revive this dead phone? Thanks in advice...

[Q] Nexus 10 won't boot or fastboot after attempted unlock

I've unlocked/rooted/flashed many Android devices in the past, including many Nexus devices. I've run into some problems here and there, but I've always been able to get around them. This time seems to be different, so far anyway.
I started with the WugFresh Nexus Root Toolkit - I know how to do it manually but this just has everything included, the drivers, adb.exe, fastboot.exe, etc.
I told it to unlock the tablet, and it rebooted the device into Fastboot. The tablet asked me if I wanted to unlock it and I said yes. Then, NRT booted me into TWRP and gave me instructions to do a factory reset from TWRP (a step I've never had to do manually before). I tried to factory reset but TWRP told me it failed. Weird. Anyway, I decided to reboot the device from TWRP and see what happened.
All I see is the swirly, colourful "X" logo forever. It never boots into Android. I can reboot by holding down the power button, and I can get into fastboot by holding down the power button with Vol-. In Fastboot, I only have the "start" option (which works, but never gets past the "X"). I can't use the volume keys to select "recovery", etc.
From Fastboot, my computer does not show the tablet under "fastboot devices" in the command prompt. It does, however, show my (working) nexus 4 in fastboot devices.
So, without working android, I can't use ADB. Without fastboot connecting with fastboot.exe, I can't push through recovery. Without a working fastboot menu on the physical device, I can't try to go into whatever recovery is there or whatever.
And worst of all, at this stage I can't even turn my device off. It's just sitting here either in the fastboot menu or with the colourful "X". It's just sitting in its original box getting warm and using up its battery.
Any ideas? This is supposed to be a present for my wife for tomorrow - I don't really want to give it to her like this.

Just used wug's kit to root my second nexus device. Both times, it said failed during the factory reset. Wierd.
Put it in bootloader mode by pressing BOTH volume keys and power. There you should see the arrows and you can go to recovery but you shouldn't have a recovery installed yet. Instead, use the wugkit to download and flash a system image, hit the flash stock + unroot button. I also had to do that on both devices for some reason. After it flashes, your bootloader will remain unlocked and you will have a clean, bootable 4.2.2 rom. Then you can root from there.
---------- Post added at 10:29 PM ---------- Previous post was at 10:26 PM ----------
Sorry I may have misread. If you are already in fastboot mode and your having a problem with your computer recognizing it, check your device manager for an uninstalled item, either adb something or android something. Then just follow the instructions in the toolkit to install the drivers. But try the flash and unroot button first and see what the toolkit says.

Same thing happened to me but luckily I had found this video before I started the unlock, root process.
Watch: https://www.youtube.com/watch?feature=player_embedded&v=T1Se7Hr9Cww
Seeing this guy missing getting the proper recovery menu really helped in understanding that it can be tricky.
I took the sage advise of others and did all the manual steps to unlock and root (no toolkit). The following link below is super whether your N10 is on Android 4.2.1 or 4.2.2 with instructions for Linux, OSx and Windows. Includes videos and pictures:
http://nexus10root.com/nexus-10-root/how-to-root-nexus-10-easiest-method/

hlaalu said:
Just used wug's kit to root my second nexus device. Both times, it said failed during the factory reset. Wierd.
Put it in bootloader mode by pressing BOTH volume keys and power. There you should see the arrows and you can go to recovery but you shouldn't have a recovery installed yet. Instead, use the wugkit to download and flash a system image, hit the flash stock + unroot button. I also had to do that on both devices for some reason. After it flashes, your bootloader will remain unlocked and you will have a clean, bootable 4.2.2 rom. Then you can root from there.
---------- Post added at 10:29 PM ---------- Previous post was at 10:26 PM ----------
Sorry I may have misread. If you are already in fastboot mode and your having a problem with your computer recognizing it, check your device manager for an uninstalled item, either adb something or android something. Then just follow the instructions in the toolkit to install the drivers. But try the flash and unroot button first and see what the toolkit says.
Click to expand...
Click to collapse
Hey mate, just wanted to say thanks. I don't know what is was that made the difference in the end, but your suggestion to use both Vol+ and Vol- together with power did the trick. I got it all working brilliantly now, thanks to you.
I'm still so confused. Why does Vol- and Power get into fastboot that doesn't work? I've never seen this behaviour on a Nexus device, or any Android device in general. It's wrapped up in a box ready to be given away in a few hours - but I will have a play with this fastboot because it's certainly weird. Definitely not like my Nexus 4 or 7.
Big thanks again. Hours of pulling my hair out and you saved me!

I believe the reason is the volume buttons are reversed. So when you think your pressing vol- your really doing vol+ lol.. That's what I did. Vol+ + power = download mode and it won't do anything from your computer. J think its an Odin mode.
Also for future reference you cannot unlock, and then use TWRP to do a factory reset. You will get a cache error. The only way it works the first time is to unlock, wipe through stock recovery, flash twrp and boot to success. But have to complete 1 boot before changing your ROM.
I've gone through multiple N10's and each of them had this behavior, I think its a bootloader bug since unlocking the device is supposed to perform a factory reset automatically.
Sent from my Nexus 10 using Tapatalk HD

Glad you're up and running!
Sent from my Galaxy Nexus using Tapatalk 2

[Q] Help! Phone boots only into fastboot then have to plug into computer to continue

Ok, this may be multiple issues. First I fell of a ladder this week and landed on phone. Screen is good, but ever since it died from battery loss while i was in hospital it only boots into fastboot. I have never flashed and update nor rooted this phone as I have never needed it on this device. Second, about a week before the fall I bought a 32gb pny class 10 card and installed. I do not believe this is the cause of the problem but who knows. This still happens with my sandisc 8gb card that is why I do not think it is the card.
Anyways, the only work around i have when this happens is to connect to my computer, start up the adb server and enter "fastboot continue".
the phone then boots fine and seems to be working great, but it is like a memory leak or something is going on because it keeps slowing down, almost freezing.

drovecrazie said:
Ok, this may be multiple issues. First I fell of a ladder this week and landed on phone. Screen is good, but ever since it died from battery loss while i was in hospital it only boots into fastboot. I have never flashed and update nor rooted this phone as I have never needed it on this device. Second, about a week before the fall I bought a 32gb pny class 10 card and installed. I do not believe this is the cause of the problem but who knows. This still happens with my sandisc 8gb card that is why I do not think it is the card.
Anyways, the only work around i have when this happens is to connect to my computer, start up the adb server and enter "fastboot continue".
the phone then boots fine and seems to be working great, but it is like a memory leak or something is going on because it keeps slowing down, almost freezing.
Click to expand...
Click to collapse
Seems clear you broke our indestructable phone!
There is a thread on the virtues of it's durability.
---------- Post added at 12:39 PM ---------- Previous post was at 12:32 PM ----------
What is your sw build?
As a long shot you could restore with rsd.
Durability
http://forum.xda-developers.com/showthread.php?t=2329367&highlight=dropped

details
aviwdoowks said:
Seems clear you broke our indestructable phone!
There is a thread on the virtues of it's durability.
---------- Post added at 12:39 PM ---------- Previous post was at 12:32 PM ----------
What is your sw build?
As a long shot you could restore with rsd.
Durability
http://forum.xda-developers.com/showthread.php?t=2329367&highlight=dropped
Click to expand...
Click to collapse
Not sure what you are asking for besides maybe the build number which is 9.8.1Q-94-1
System Version 98.30.1.xt907.Verizon.en.US
Might add that when I fell off the ladder landing on my rear, my phone was in my back pocket.
Not much cushion as I am skinny as 7734.
Glad I took out the extra insurance. Guess I will call verizon after Christmas to see what they suggest and maybe someone will have a suggestion.
Not sure about RSS, scared to touch the thing atm because of the extra insurance.

drovecrazie said:
Not sure what you are asking for besides maybe the build number which is 9.8.1Q-94-1
System Version 98.30.1.xt907.Verizon.en.US
Might add that when I fell off the ladder landing on my rear, my phone was in my back pocket.
Not much cushion as I am skinny as 7734.
Glad I took out the extra insurance. Guess I will call verizon after Christmas to see what they suggest and maybe someone will have a suggestion.
Not sure about RSS, scared to touch the thing atm because of the extra insurance.
Click to expand...
Click to collapse
Rss? Rsd.
Seems within the relm of the possible that the shock could cause a memory disruption yet leave the hardware functional.
A restore is worth a try.
Just load rsd lite & with the (press all 3 keys & hold till screenout, toggle power, vol down to scroll to ap fastboot & vol up once on the ap fastboot) phone plugged in see if rsd recognizes it!
My stickys has a rsd link.

RSD help
aviwdoowks said:
Rss? Rsd.
Seems within the relm of the possible that the shock could cause a memory disruption yet leave the hardware functional.
A restore is worth a try.
Just load rsd lite & with the (press all 3 keys & hold till screenout, toggle power, vol down to scroll to ap fastboot & vol up once on the ap fastboot) phone plugged in see if rsd recognizes it!
My stickys has a rsd link.
Click to expand...
Click to collapse
Never get a fastboot menu, am I missing something?
Ok, held down all three buttons until screen went out (powered down), then hit power (not connected to PC), device went to fastboot reason "Flash Failure". Hit power button, hold volume down and hit power, reason changed to button press.
connected phone to computer and launched rsd lite. (sorry about my fat fingers before, I am still hoping the nerves in my hands recover from surgery)
Attached is the image of my RSD with Phone attached. When I hit "Show Device" nothing happens, only notification of anything is line 1 saying connected.

Progress
drovecrazie said:
Never get a fastboot menu, am I missing something?
Ok, held down all three buttons until screen went out (powered down), then hit power (not connected to PC), device went to fastboot reason "Flash Failure". Hit power button, hold volume down and hit power, reason changed to button press.
connected phone to computer and launched rsd lite. (sorry about my fat fingers before, I am still hoping the nerves in my hands recover from surgery)
Attached is the image of my RSD with Phone attached. When I hit "Show Device" nothing happens, only notification of anything is line 1 saying connected.
Click to expand...
Click to collapse
Ok, got into fastboot menu buy holding both vol up and down then toggling power. then pressed vol down then up to select normal boot.
got red M then android on his back with red exclamation point. held down both volume buttons (IAW Verizon's "How To Restore"), now I have wiped cache and I am about wiped data /factory reset, but do I need to reflash something before I do this?
Did I miss anything?

drovecrazie said:
Never get a fastboot menu, am I missing something?
Ok, held down all three buttons until screen went out (powered down), then hit power (not connected to PC), device went to fastboot reason "Flash Failure". Hit power button, hold volume down and hit power, reason changed to button press.
connected phone to computer and launched rsd lite. (sorry about my fat fingers before, I am still hoping the nerves in my hands recover from surgery)
Attached is the image of my RSD with Phone attached. When I hit "Show Device" nothing happens, only notification of anything is line 1 saying connected.
Click to expand...
Click to collapse
You are good to browse (... button) to the unzipped xml (fxz) file & start!
---------- Post added at 03:44 PM ---------- Previous post was at 03:34 PM ----------
http://forum.xda-developers.com/attachment.php?attachmentid=2448565&d=1386790010

Failed
aviwdoowks said:
You are good to browse (... button) to the unzipped xml (fxz) file & start!
---------- Post added at 03:44 PM ---------- Previous post was at 03:34 PM ----------
http://forum.xda-developers.com/attachment.php?attachmentid=2448565&d=1386790010
Click to expand...
Click to collapse
Well that did not go so well. Flash failed. Image attached displaying why. Did Verizon's version of a restore. Still powers on to fastboot with Reason being flash failed.

drovecrazie said:
Well that did not go so well. Flash failed. Image attached displaying why. Did Verizon's version of a restore. Still powers on to fastboot with Reason being flash failed.
Click to expand...
Click to collapse
Why did you flash ...78?
Your build is ...94
You are locked & there is no downgrade.
Flash the link I posted.

Does the RAZR go into fast boot with the cable? If it does then I have to think he broke his USB port and if that is then why are you flashing?
I'd wager if you took it apart you'd find power going to pin 4 for some reason or I've seen corrosion do this on the kindle fire hd
Sent from my GT-P3110 using xda app-developers app

Tried both files and still have fail step one
aviwdoowks said:
Why did you flash ...78?
Your build is ...94
You are locked & there is no downgrade.
Flash the link I posted.
Click to expand...
Click to collapse
I have been through your signatures, all of them. I have found two "roms" and one from anouther source:
VRZ_modv5_XT907_9.8.1Q-78-1_1FF.xml.zip, VRZ_XT907_9.8.1Q-78-1_1FF.xml.zip, and VZW_XT907_4.1.2-9.8.1Q-66_1FF.xml.zip
all three failed at step one. None of them look like 98.18.94. You have a link that brings me to a link about how this rom can not be rooted, but never gave the stock rom.
If one of those is not the correct rom then can you provide a link?

Thanks, but has nothing to do with the cable
mrkhigh said:
Does the RAZR go into fast boot with the cable? If it does then I have to think he broke his USB port and if that is then why are you flashing?
I'd wager if you took it apart you'd find power going to pin 4 for some reason or I've seen corrosion do this on the kindle fire hd
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
This happens all the time when returning from a powered off state.
Oh and I completely removed the micro sd card and it still powered up into fastboot. So definately not the sd card as I had been hoping.

drovecrazie said:
This happens all the time when returning from a powered off state.
Oh and I completely removed the micro sd card and it still powered up into fastboot. So definately not the sd card as I had been hoping.
Click to expand...
Click to collapse
There is slim chance of your hardware working!
...94 link paste to chrome or get the mega app.
Click on this:
http://forum.xda-developers.com/attachment.php?attachmentid=2448565&d=1386790010

drovecrazie said:
I have been through your signatures, all of them. I have found two "roms" and one from anouther source:
VRZ_modv5_XT907_9.8.1Q-78-1_1FF.xml.zip, VRZ_XT907_9.8.1Q-78-1_1FF.xml.zip, and VZW_XT907_4.1.2-9.8.1Q-66_1FF.xml.zip
all three failed at step one. None of them look like 98.18.94. You have a link that brings me to a link about how this rom can not be rooted, but never gave the stock rom.
If one of those is not the correct rom then can you provide a link?
Click to expand...
Click to collapse
Every single one of those are old OTAs, grab the new one from here. The last one:
http://sbf.droid-developers.org/phone.php?device=8

an actual working link, thanks
RikRong said:
Every single one of those are old OTAs, grab the new one from here. The last one:
http://sbf.droid-developers.org/phone.php?device=8
Click to expand...
Click to collapse
Thanks. The link actually work and I am downloading now. I went to my local verizon store and (wait for it) the tech was clueless. He went ahead and ordered a replacement. I will still try the link and hope for the best.
I will post the results later tonight.

mrkhigh said:
Does the RAZR go into fast boot with the cable? If it does then I have to think he broke his USB port and if that is then why are you flashing?
I'd wager if you took it apart you'd find power going to pin 4 for some reason or I've seen corrosion do this on the kindle fire hd
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
That sounds like a possibility with the physical damage that occurred it may have shorted pin 4 to a power source causing it to boot that way and it becoming slow and laggy ...
Sent from my XT907 using xda app-developers app

Downloading Do not turn off target SCEEN

I try to install CyanogenMod on my GT N8013 and I get the famous screen Downloading Do not turn off target.
I try everything in the book from the forum, nothing work. To make thing worse now the USB is not recognized by the computer.
I drain the battery completely and soon I connect the charge BOOM the famous screen. LOOK to me that this is the end of MY NOTE? PLEASE any advice before I send it to sleep.
Thanks

Go to odin and reformat it.
Sent from my GT-N8013 using Tapatalk

thurmanbr549 said:
Go to odin and reformat it.
Sent from my GT-N8013 using Tapatalk[/QUOTE
I GOT Odin screen, but I can't do anything, just turn it off , there is no option
Click to expand...
Click to collapse

Can you get into stock recovery?

thurmanbr549 said:
Can you get into stock recovery?
Click to expand...
Click to collapse
NO. I have no access by USB, Is not recognized by any computer with the samsung driver.. I only can get to the Odin screen via the Power and Vol-Down.

Hold the power button and volume up until you see the samsung logo then let off of the power button. Then clear everything any do a factory reset. This should work
---------- Post added at 12:58 PM ---------- Previous post was at 12:56 PM ----------
Do not connect to your computer
---------- Post added at 01:13 PM ---------- Previous post was at 12:58 PM ----------
Do lots of research before embarking on something like this. Make absolutely sure you know how to recover your tablet before doing any kind of modifications to it.

thurmanbr549 said:
Hold the power button and volume up until you see the samsung logo then let off of the power button. Then clear everything any do a factory reset. This should work
---------- Post added at 12:58 PM ---------- Previous post was at 12:56 PM ----------
Do not connect to your computer
---------- Post added at 01:13 PM ---------- Previous post was at 12:58 PM ----------
Do lots of research before embarking on something like this. Make absolutely sure you know how to recover your tablet before doing any kind of modifications to it.
Click to expand...
Click to collapse
I hold the Power and Up Vol in a second I get the"Downloading Do not turn of screen and nothing happens. If I hold the power and down-vol a selection page come, Warning A custom OS can cause critical problem etc.... Volume up: Continue or Volume Down; cancel (restart phone) if a press Vol Up it show another screens with odin mode in red , product name: gt n8013,custom binary count: yes 6 count, Current Binary : samsung official, System status: official
and the downloading message. and It freeze.
By the way thanks for your time, I really don't now what to do. Maybe send it to the moon jajaja

Thy holding vol down and see if it takes you to a recovery screen...your welcome I hope I can help. I didn't have anyone when I was learning it sucked.
---------- Post added at 08:23 PM ---------- Previous post was at 08:13 PM ----------
Hold the power and volume up and just keep holding and holding and see what happens

wichiepr said:
I hold the Power and Up Vol in a second I get the"Downloading Do not turn of screen and nothing happens. If I hold the power and down-vol a selection page come, Warning A custom OS can cause critical problem etc.... Volume up: Continue or Volume Down; cancel (restart phone) if a press Vol Up it show another screens with odin mode in red , product name: gt n8013,custom binary count: yes 6 count, Current Binary : samsung official, System status: official
and the downloading message. and It freeze.
By the way thanks for your time, I really don't now what to do. Maybe send it to the moon jajaja
Click to expand...
Click to collapse
Got good info in previous posts.
Holding volume DOWN + power button brings you to a recovery screen, either stock(factory) or TWRP / CWM recovery.
Holding volume UP + power button brings you to odin which then gives an option to continue or Restart.
You first need to root before flashing roms and also need to flash whichever recovery you prefer. You didn't mention if you had done so or not so I must ask.
If you can get into odin download the latest odin on your computer and your computer will install the drivers once you connect it via USB.

KDKobes said:
Got good info in previous posts.
Holding volume DOWN + power button brings you to a recovery screen, either stock(factory) or TWRP / CWM recovery.
Holding volume UP + power button brings you to odin which then gives an option to continue or Restart.
You first need to root before flashing roms and also need to flash whichever recovery you prefer. You didn't mention if you had done so or not so I must ask.
If you can get into odin download the latest odin on your computer and your computer will install the drivers once you connect it via USB.
Click to expand...
Click to collapse
OK
I try both method with the Vol up and down with the power, The unit just turn off for about 3 seconds then the samsumg logo appear and inmidiatly the "Downloading page" and keep on a loop if I keep the buttom down. As I say before the only diferent is to get to the odin screen that I explain in my last reply. I don't have USB access, when I connect it it say USB not recognize

wichiepr said:
OK
I try both method with the Vol up and down with the power, The unit just turn off for about 3 seconds then the samsumg logo appear and inmidiatly the "Downloading page" and keep on a loop if I keep the buttom down. As I say before the only diferent is to get to the odin screen that I explain in my last reply. I don't have USB access, when I connect it it say USB not recognize
Click to expand...
Click to collapse
Do you have odin on your computer?

KDKobes said:
Do you have odin on your computer?
Click to expand...
Click to collapse
Yes I do, but the computer is not recognizing the USB. I can't connect to the Tablet, that is the problem

wichiepr said:
Yes I do, but the computer is not recognizing the USB. I can't connect to the Tablet, that is the problem
Click to expand...
Click to collapse
When your phone is in odin download mode connect to the computer open odin then go to your control panel and into "device manager" and check if your device shows up in there as an unknown device or not. If you have adb run the command "adb devices" as well and see if you get anything.

KDKobes said:
When your phone is in odin download mode connect to the computer open odin then go to your control panel and into "device manager" and check if your device shows up in there as an unknown device or not. If you have adb run the command "adb devices" as well and see if you get anything.
Click to expand...
Click to collapse
I try to install all he adb driver and all the ADB Interface, Samsung Android Composite ADB Interface etc., all of them say "This device cannot start. (Code 10)" and that is a genetic error. IS hard to find the cause

wichiepr said:
I try to install all he adb driver and all the ADB Interface, Samsung Android Composite ADB Interface etc., all of them say "This device cannot start. (Code 10)" and that is a genetic error. IS hard to find the cause
Click to expand...
Click to collapse
Did you check you "device manager" on your computer to see if it is even showing the device either as an unknown or maybe an error. Are you running Windows 7? Just to be clear, when you try holding volume down + power then when it turns on release the power button while still holding volume down until recovery screen comes up all you get is "Downloading...etc .."
As far as plugging the device in while in odin mode after pressing volume up to continue and plugging into computer you said you get an error on your computer correct? Just trying to gather all the info I can to see if you can fix it.
If its a driver issue or not recognized it might be due to the MTP which would lead you here for a solution.
What has happened at this point is you tried flashing a custom ROM on an un-rooted device with a stock recovery. Now at this point your phone doesn't likely have any of the original software in it to allow you to boot let alone even do a a recovery from stock recovery. Your lucky the device even powers on first off because if it was a hard hard brick the device wouldn't boot, charge, or flicker the screen regardless of button combinations and would need jtagd. Now even if you could return it they most likely wont because of the custom binary count at a 6.
most of all I need to know if your device shows up in device manager on your computer most likely located under portable devices. You might need different drivers at this point.
See if any of this information can help.

KDKobes said:
Did you check you "device manager" on your computer to see if it is even showing the device either as an unknown or maybe an error. Are you running Windows 7? Just to be clear, when you try holding volume down + power then when it turns on release the power button while still holding volume down until recovery screen comes up all you get is "Downloading...etc .."
As far as plugging the device in while in odin mode after pressing volume up to continue and plugging into computer you said you get an error on your computer correct? Just trying to gather all the info I can to see if you can fix it.
If its a driver issue or not recognized it might be due to the MTP which would lead you here for a solution.
What has happened at this point is you tried flashing a custom ROM on an un-rooted device with a stock recovery. Now at this point your phone doesn't likely have any of the original software in it to allow you to boot let alone even do a a recovery from stock recovery. Your lucky the device even powers on first off because if it was a hard hard brick the device wouldn't boot, charge, or flicker the screen regardless of button combinations and would need jtagd. Now even if you could return it they most likely wont because of the custom binary count at a 6.
most of all I need to know if your device shows up in device manager on your computer most likely located under portable devices. You might need different drivers at this point.
See if any of this information can help.
Click to expand...
Click to collapse
My answer by points
Did you check you "device manager" on your computer to see if it is even showing the device either as an unknown or maybe an error
YES is showing under USB as Unknown Device.
https://www.dropbox.com/s/nqbchoxg9u7e7mb/Screenshot 2014-05-14 15.47.56.png
Are you running Windows 7?
YES I am running W7
Just to be clear, when you try holding volume down + power then when it turns on release the power button while still holding volume down until recovery screen comes up all you get is "Downloading...etc .."
YES
As far as plugging the device in while in odin mode after pressing volume up to continue and plugging into computer you said you get an error on your computer correct?
YES the USB s not recognize
Just trying to gather all the info I can to see if you can fix it.
If its a driver issue or not recognized it might be due to the MTP which would lead you here for a solution.
IS a tablet GT N8013
What has happened at this point is you tried flashing a custom ROM on an un-rooted device with a stock recovery. Now at this point your phone doesn't likely have any of the original software in it to allow you to boot let alone even do a a recovery from stock recovery. Your lucky the device even powers on first off because if it was a hard hard brick the device wouldn't boot, charge, or flicker the screen regardless of button combinations and would need jtagd. Now even if you could return it they most likely wont because of the custom binary count at a 6.

wichiepr said:
My answer by points
Did you check you "device manager" on your computer to see if it is even showing the device either as an unknown or maybe an error
YES is showing under USB as Unknown Device.
https://www.dropbox.com/s/nqbchoxg9u7e7mb/Screenshot 2014-05-14 15.47.56.png
Are you running Windows 7?
YES I am running W7
Just to be clear, when you try holding volume down + power then when it turns on release the power button while still holding volume down until recovery screen comes up all you get is "Downloading...etc .."
YES
As far as plugging the device in while in odin mode after pressing volume up to continue and plugging into computer you said you get an error on your computer correct?
YES the USB s not recognize
Just trying to gather all the info I can to see if you can fix it.
If its a driver issue or not recognized it might be due to the MTP which would lead you here for a solution.
IS a tablet GT N8013
What has happened at this point is you tried flashing a custom ROM on an un-rooted device with a stock recovery. Now at this point your phone doesn't likely have any of the original software in it to allow you to boot let alone even do a a recovery from stock recovery. Your lucky the device even powers on first off because if it was a hard hard brick the device wouldn't boot, charge, or flicker the screen regardless of button combinations and would need jtagd. Now even if you could return it they most likely wont because of the custom binary count at a 6.
Click to expand...
Click to collapse
Thats good news now you need the proper drivers and or fix the file causing the issue. Follow the previous link I had posted.

KDKobes said:
Thats good news now you need the proper drivers and or fix the file causing the issue. Follow the previous link I had posted.
Click to expand...
Click to collapse
I did follow the link, I find the RegKey,but there is no UpperFilters under under the portable device.

wichiepr said:
I did follow the link, I find the RegKey,but there is no UpperFilters under under the portable device.
Click to expand...
Click to collapse
Read all the posts through the second page depending on your system you might have to do a different step. Wish I could explain more but without being in front of your computer its too hard. There is also a link in the first post to download the latest drivers also. Make sure you're using the factory usb cable that came with the tablet.
You're tablet is repairable just need to get the drivers working just dont go do anything else to the tablet itself until the drivers are working.

brick
KDKobes said:
Read all the posts through the second page depending on your system you might have to do a different step. Wish I could explain more but without being in front of your computer its too hard. There is also a link in the first post to download the latest drivers also. Make sure you're using the factory usb cable that came with the tablet.
You're tablet is repairable just need to get the drivers working just dont go do anything else to the tablet itself until the drivers are working.
Click to expand...
Click to collapse
Sorry for the delay, I was looking for the original cable. I just find it but is still not recognizing the USB. I did follow up the link. Is say that the driver is update. The Samsung driver also say is installed but I don't see it on the Device manager. I don't really have a clue. I try to go to the Samsung folder and look for the .ini but I don't know which one if there is any for the Device manager. I try also. IS you have time I can gave you access to my comp via Teamviever is you want.

[Q] Nexus 10 stuck in bootloop after Lollipop flash no ADB and no Fastboot

So .... I flashed the mantaray-lrx21p image from Nexus Factory Images on my Nexus 10 (16GB Wifi) and now it's stuck in a bootloop.
No problem, I thought, I can get into recovery and fix it, right? Maybe do a wipe and try again? Yeah, not so fast. I get the bootloader screen, but the only option is 'Start' which just boots into the system that bootloops.
That's OK, I'll just use fastboot to wipe it. Nope. Fastboot doesn't detect a device.
I've tried both ADB and fastboot on Mac & Linux. Same issue (neither fastboot nor adb detect a device).
Ideas?
Observations
In case you think I'm just being impatient, it has been doing the boot animation for about 25 minutes now.
It doesn't like to stay off. If I hold the power button for 10 seconds it turns off, but it turns itself back on in about 5 seconds.
If I power it on while holding the volume button closer to the power button, I can get into a half-assed bootloader ... meaning that I can only push the power button again to 'Start'. I cannot cycle through the options with the volume buttons.
During the mentioned (half-assed) bootloader screen, fastboot does not detect a device.
During the boot animation, adb does not detect a device.

copolii said:
So .... I flashed the mantaray-lrx21p image from Nexus Factory Images on my Nexus 10 (16GB Wifi) and now it's stuck in a bootloop.
No problem, I thought, I can get into recovery and fix it, right? Maybe do a wipe and try again? Yeah, not so fast. I get the bootloader screen, but the only option is 'Start' which just boots into the system that bootloops.
That's OK, I'll just use fastboot to wipe it. Nope. Fastboot doesn't detect a device.
I've tried both ADB and fastboot on Mac & Linux. Same issue (neither fastboot nor adb detect a device).
Ideas?
Observations
In case you think I'm just being impatient, it has been doing the boot animation for about 25 minutes now.
It doesn't like to stay off. If I hold the power button for 10 seconds it turns off, but it turns itself back on in about 5 seconds.
If I power it on while holding the volume button closer to the power button, I can get into a half-assed bootloader ... meaning that I can only push the power button again to 'Start'. I cannot cycle through the options with the volume buttons.
During the mentioned (half-assed) bootloader screen, fastboot does not detect a device.
During the boot animation, adb does not detect a device.
Click to expand...
Click to collapse
The reason starts the only option is because your only holding volume up when going into fastboot. Hold power and volume up AND DOWN. All at the same time. Trust me I had the same issue but googling helped me find out you gotta hold both buttons
Sent from my VS980 4G

Same problem here, I'm stuck in a bootloop
I can access the bootloader and retry, but I'm still stuck in a bootloop.
I have checked the hash of the zip so I don't know what the problem can be.
Maibe I don't have the very last version of the sdk, that's the only guess I can do, let's try this...
---------- Post added at 10:07 PM ---------- Previous post was at 10:05 PM ----------
supermamie said:
Same problem here, I'm stuck in a bootloop
I can access the bootloader and retry, but I'm still stuck in a bootloop.
I have checked the hash of the zip so I don't know what the problem can be.
Maibe I don't have the very last version of the sdk, that's the only guess I can do, let's try this...
Click to expand...
Click to collapse
I launched a 3rd flash while I downloaded the sdk and this one worked...
Absolutely no idea why.

I finally got it to boot.
boot into bootloader (hold vol-up+vol-down+power)
choose reboot bootloader
choose shutdown
turn it back on
Seems like it needed to be shut completely off not just rebooted after the flash. Perhaps a reboot maintains weird memory fragments or something? Crazy talk, I know.
Edit: you shouldn't have to wait long to see if it works. Mine jumped to the "Upgrading apps ..." screen straight away.

The very first boot on my n7 and n10 took about 20 min, after that they have normal boot time, I believe this may have something to do with encryption but never bothered to check as I just did something else while it booted
Side note, the n9 has an initial boot time of at least 5-10 min (can't recall but it took forever it felt like) and this is optimized hardware for the software so no surprise that there is a huge long boot time on the first go
Also I flashed both manually erasing all partitions first through fastboot then flashing each one individually... Just another side note

supermamie said:
Same problem here, I'm stuck in a bootloop
I can access the bootloader and retry, but I'm still stuck in a bootloop.
I have checked the hash of the zip so I don't know what the problem can be.
Maibe I don't have the very last version of the sdk, that's the only guess I can do, let's try this...
---------- Post added at 10:07 PM ---------- Previous post was at 10:05 PM ----------
I launched a 3rd flash while I downloaded the sdk and this one worked...
Absolutely no idea why.
Click to expand...
Click to collapse
Ive tried to connect to the device in adb, fastboot, I can only get it to adb sideload mode.
Sideloading gives the message Wrong footer instalation aborted.
How did you manage to flash the image? All drivers did install properly it seems.

Boot loop
thedarksavant said:
I finally got it to boot.
The same was happening to me, after unlocking it it began to loop, even after I wipe it was still looping.
I followed your steps of going into reboot recovery then power off. -- issue resolved!!
Thanks!
******
Click to expand...
Click to collapse