[Q] 5.0 update issues - Nexus 10 Q&A, Help & Troubleshooting

I recently tried to update my Nexus 10 to lollipop and ran into a problem. I was able to download and begin the installation but then all i got was the android on its back with a red exclamation point above the chest. Info on the tablet is as follows:
Product Name: Manta
Variant: wifi
H/W Version: 8
Bootloader Version: Mantamf01
Lock State: Unlocked
Reboot Mode Flag: Recovery
When I start it in recovery mode it says "Downloading Do not turn off Target"
I have tried speaking with Google with no help and Samsung customer support has been beyond useless.
I am not really sure what to do to fix it. I was hoping someone here may have run into this issue in the past. If you need any more information from me, I will do my best to supply it.
Thanks

You might want to consider one of the tool kits, like Wug's (http://forum.xda-developers.com/showthread.php?t=2015467). I know some frown on such applications but when I ran into problems upgrading to 5.0.1, it was able to get me where I wanted to be (although I do not remember having this problem; mine was more getting my computer and my tablet to "talk" in order to update the bootloaders).
kmenard said:
I recently tried to update my Nexus 10 to lollipop and ran into a problem. I was able to download and begin the installation but then all i got was the android on its back with a red exclamation point above the chest. Info on the tablet is as follows:
Product Name: Manta
Variant: wifi
H/W Version: 8
Bootloader Version: Mantamf01
Lock State: Unlocked
Reboot Mode Flag: Recovery
When I start it in recovery mode it says "Downloading Do not turn off Target"
I have tried speaking with Google with no help and Samsung customer support has been beyond useless.
I am not really sure what to do to fix it. I was hoping someone here may have run into this issue in the past. If you need any more information from me, I will do my best to supply it.
Thanks
Click to expand...
Click to collapse

kmenard said:
I recently tried to update my Nexus 10 to lollipop and ran into a problem. I was able to download and begin the installation but then all i got was the android on its back with a red exclamation point above the chest. Info on the tablet is as follows:
Product Name: Manta
Variant: wifi
H/W Version: 8
Bootloader Version: Mantamf01
Lock State: Unlocked
Reboot Mode Flag: Recovery
When I start it in recovery mode it says "Downloading Do not turn off Target"
I have tried speaking with Google with no help and Samsung customer support has been beyond useless.
I am not really sure what to do to fix it. I was hoping someone here may have run into this issue in the past. If you need any more information from me, I will do my best to supply it.
Thanks
Click to expand...
Click to collapse
Have you tried holding the power button in for 20 or 30 seconds and booting normally, on a fully charged device? If not, and if you're looking at a completely unusable device and google/samsung aren't helping then perhaps it's worth following the steps to flash a new image from google's site.
https://developers.google.com/android/nexus/images
You want to follow the instructions for 5.0.1 (LRX22C)
You will lose all data on the device.

Related

new device wont bootup after firmware update

Hello, i have purchased the nexus7 yesterday and am abroad right now. so no use in bringing it back! it used to work fine for a few hours until i got a popup that updates where available and were going to reset the device after install.
i saw the device installing the updates but after that it did not bootup again to the main-screen. i was stuck on the colorful X for hours!.
i did some searching and tried the recovery where you hold volume up&down with power with no luck. i had read also to have it connected to my computer when trying this also with also no results.
i noticed that when you are in the recovery mode where you have the red triangle that i dont get an option when i press the volume up+power button to erase. nothing happens. after awhile it seems like it will reboot and i endup back to the colorful X.
i have also tried most of these options with not much results http://forum.xda-developers.com/showthread.php?t=1809195
when using nexus root toolkit -flash stock onroot option i get the following error im not sure what this means' (see attachement) this is where it stops. the device is in fastboot mode.
i hope i will be able to reset this device and that anyone here will be able to advice me. i just bought this device and am already disappointed!
any help is greatly appreciated and i thank you ahead of time!
Dino.
Which error are you talking about? Usually you have to wait a while when it restores. Plus, are you on the 4.1.1 Nexus 7 version on the Toolkit?
Sent from my Nexus 7 using xda app-developers app
the errors in the printscreen about " archive does not contain 'boot.sig', recovery.sig and system.sig'
i downloaded and used fw 4.1.1 from /developers.google.com/android/nexus/images website!
also wanted to mention whats on the device:
fastboot mode
product name - grouper
hw version -er3
bootloader version -3.34
baseband version -n/a
serial numer....
signing - not defined yet
lock state - unlocked
i tried re-downloading the fw 4.1.1 and executing with the same error's of archives'. its stuck on sending 'boot now!
booloader version 3.34
baseband n/a
serial numer...
checking product: okay 0.018s
checking version-bootloader: okay 0.019s
sending 'boot' 4890kb ..... waiting....

[Q] Is this thing completely bricked? Need some help!

Ok, I've got no idea what happened, but here it goes: I think I royally screwed things up when I tried to go from 4.2 back down to PA 2.54. The install froze in twrp, so I made the mistake of holding down the power.vol buttons. Now will boot into the bootloader screen, but won't get past the Google screen on reboot, and when I try to get to recovery it stalls as well.
adb and fastboot can't find the device, although my pc does "see" it when I plug in the usb.
Here's the info on the bootloader screen:
Product Name - Grouper
Variant - Grouper
HW Version - ER3
Bootloader Version - 4.13
Baseband Version - n/a
Signing - not defined yet
lock State - unlocked
I tried using the toolkit to reload and unroot, but it can't see it.
Is this thing toast? Or is there a way to get it rolling again?
Any help MUCH appreciated!!
Strangely when the device is stuck on the teamwin screen, I can get my pc to recognize it via adb devices, It returns: --015d21d9100bec0d recovery--
I've never seen it mention recovery before, but I'm far from an expert.
Being that the bootloader still loads and the pc at least somewhat recognizes it, there's got to be some kind of solution??

[Q] Nexus 7 Cannot boot into recovery and cannot

Hey guys,
So I recently bought a nexus 7 32gb (first generation) and used it for about 30 minutes, then I applied what I presume was a faulty update and it has soft bricked my tablet.
Heres the scenerio,
-I cannot get my nexus 7 into usb debugging mode because it wont boot up into the actual interface and such
-Everytime I try to install the ADB drivers, the system installs it as "google nexus 7 bootloader interface"
-recovery mode will not load up, it ends up at the google screen with a text on the topright saying "booting failed"
-I'm pretty sure my bootloader is locked which could be another reason why I cant do any of the methods involving cmd, nrt, or that manual android sdk toolkit thing.
As far as I know right now (which is barely anything since I'm new to using this tablet), I can't do anything because I cannot get into usb debugging, nor can I get the tablet to read as the ADB interface / pass the full driver test in NRT.
Hopefully someone can help (Very descriptively please!) , thanks!
Sidenotes : my boot loader menus states the following...
FASTBOOT MODE
Product Name - Grouper
Variant - Grouper
HW version - ER3
Bootloader Version - 4.23
Baseband Version - N/A
Serial Number - idk if I should actually post this but im going to assume it's irrelevant for this subject
Signing - not defined yet
Lock state - Locked
Also, It was fresh out of the box, I think the tablet was updated to 4.1
bump...
anyone?!??!?!
I'm having a problem that is a little similar to yours. I have a nexus 7 2013 wifi. It won't boot up all the way it gets stuck on the X screen. Bootloader is locked and usb debugging is off. I've been trying to figure out if I can do a pull or backup over the adb sideloader.
Does your nexus have that capability?
I did come across a method that would unlock the bootloader. You need to install a nexus 7 toolkit.
I don't know if that will help you but let me dig up the link to the instructions.
If you would take the time to actually read the guides around here you would know that USB debugging is not a requirement in fast boot or recovery mode. USB debugging only applies to a booted os. Why don't you follow the guides and manually install your drivers? Use fast boot commands to flash a stock image. This isn't difficult to do. Stop messing with toolkits and learn something. You're here on XDA, utilize the resources we have.
happyfuntimes7 said:
Hey guys,
So I recently bought a nexus 7 32gb (first generation) and used it for about 30 minutes, then I applied what I presume was a faulty update and it has soft bricked my tablet.
Heres the scenerio,
-I cannot get my nexus 7 into usb debugging mode because it wont boot up into the actual interface and such
-Everytime I try to install the ADB drivers, the system installs it as "google nexus 7 bootloader interface"
-recovery mode will not load up, it ends up at the google screen with a text on the topright saying "booting failed"
-I'm pretty sure my bootloader is locked which could be another reason why I cant do any of the methods involving cmd, nrt, or that manual android sdk toolkit thing.
As far as I know right now (which is barely anything since I'm new to using this tablet), I can't do anything because I cannot get into usb debugging, nor can I get the tablet to read as the ADB interface / pass the full driver test in NRT.
Hopefully someone can help (Very descriptively please!) , thanks!
Sidenotes : my boot loader menus states the following...
FASTBOOT MODE
Product Name - Grouper
Variant - Grouper
HW version - ER3
Bootloader Version - 4.23
Baseband Version - N/A
Serial Number - idk if I should actually post this but im going to assume it's irrelevant for this subject
Signing - not defined yet
Lock state - Locked
Also, It was fresh out of the box, I think the tablet was updated to 4.1
Click to expand...
Click to collapse
Use Nexus root toolkit and folow Full driver instalation guide for correct driver instalation
After this use Flash stock to repair, then you can continue to unlock/root or anithing else.

[Q] Old Nexus 7, New Issues

Hey guys!
I've been scouring these forums for two days now making sure my specific issue hasn't been discussed and, from what I've seen, I've won some sort of "annoying issue" lottery.
I was handed a Nexus 7 (ME370T) a few days ago and told "if you can fix it, it's yours."
I can get to the bootloader no problem but not the actual OS. Here's the data from the bootloader:
Fastboot Mode
Product Name - grouper
Variant - grouper
HW Version - ER3
Bootloader Version - 4.23
Baseband Version - N/A
Serial Number - xxxxxxxxx
Signing - not defined yet
Lock State - Locked
Long story short, I've installed the Android SDK and when I plug the tablet into my PC, I can see it as "Google Nexus 7 Bootloader Interface"
When I use fastboot devices, it sees the tablet just fine.
When I use adb devices, it doesn't see the tablet.
I've tried fastboot oem unlock and I get a FAILED (remote: (Unknown error code)) error.
I can run the unlock feature through the Nexus Root Toolkit but it reboots to a black screen (my device manager sees it as "Asus Transformer Prime APX Interface")
When I finally get the thing rebooted to the bootloader (manually powering off and then back on), it's still locked.
I have no idea if USB Debugging was turned on or not. I keep reading that, to flash a partition to a new file, the bootloader doesn't need to be unlocked but every single time I try to fun fastboot, i get Failed, Bootloader is locked.
Am I nuts? I know I'm new to this but I'm fairly certain I've done everything right! You guys seem super knowledgeable and I hope you can help me out!
Thanks!

an error has occurred while updating the device software

Hey,
First of all, im new here so I have no clue whether I posted this in the correct place, but I have a problem and cant figure it out.
I have the samsung A20e, SM-A202f
So I tried rooting my phone, following: topjohnwu,github,io/Magisk/install.html#samsung-system-as-root, but when I did step 7, odin kept loading on recovery and after some time it said failed and my phone gave the error: an error has occurred while updating the device software.
After this I went to download mode but I cant seem to actually download firmware onto the phone from odin, it doesnt show an ID: COM either.
I think this is because the system put the OEM lock back on, since in the top-right of the screen it says: OEM LOCK: ON(U)
Any ideas how I can fix this?
Thanks in advance
I cant post urls yet so thats why the link isnt working
Nielsvh05 said:
Hey,
First of all, im new here so I have no clue whether I posted this in the correct place, but I have a problem and cant figure it out.
I have the samsung A20e, SM-A202f
So I tried rooting my phone, following: topjohnwu,github,io/Magisk/install.html#samsung-system-as-root, but when I did step 7, odin kept loading on recovery and after some time it said failed and my phone gave the error: an error has occurred while updating the device software.
After this I went to download mode but I cant seem to actually download firmware onto the phone from odin, it doesnt show an ID: COM either.
I think this is because the system put the OEM lock back on, since in the top-right of the screen it says: OEM LOCK: ON(U)
Any ideas how I can fix this?
Thanks in advance
I cant post urls yet so thats why the link isnt working
Click to expand...
Click to collapse
These are the S20 forums, you need to be in the A20e forums here
https://forum.xda-developers.com/t/samsung-galaxy-a20e

Categories

Resources