Database Users

[Q] Nexus 10 missing from USB connections in recovery

Hi All,
I've been trying to sideload the net OTA. The dvice shows up while it's running. I can do a 'adb reboot recovery' and it reboots OK, sits at a screen where it says "no command" but the Windows cannot see any kind of connected USB device, no unknown....nothing. I checked on all 5 ports. In Bootloader mode it shows up OK but not in recovery.
Any ideas?
Thx
Update: Now the piece of sh1t will only boot into recovery....how do I get out of that?!? I tried to reset, I can get into boot loader, but 'Start' or fastboot reboot does not get be back into Android.....and as I'm typing this it reboots itself into the OS.....oh well :-|

I'm having this exact same issue. Did you find any fix?

timesgodjillion said:
I'm having this exact same issue. Did you find any fix?
Click to expand...
Click to collapse
No but I worked around it:
Download and install the Nexus 10 Toolkit
download the latest TRWP recovery
rename it to that one supported and included in the Toolkit (I found no way to upgrade the Toolkit to 1.7.1 without paying!)
copy it into the right folder inside the toolkit structure
copy the OTA update into the SDCARD
start the toolkit and boot a recovery without flashing (Option 10 I think)
chose the TWRP recovery
once the recovery has booted you install the OTA zip
Mine failed with some assert error (system/bin/debuggerd) so you may need to use the updater script and remove the assert line (and ONLY the line causing you grief)
Make sure you use something like Notepad++ that doesn't mess up the script file
clear cache and dalvik and then reboot
worked for me

[Q] N10 *seriously* bricked after CF-Auto-Root and OTA

Since I'm a newbie here I can't post this problem to "[N10] CF-Auto-Root". If some kind person with permissions could alert the people there to this problem I'd really appreciate it.
I installed CF-Auto-Root on my Nexus 10, and after an OTA upgrade to 4.3 the tablet is seriously bricked. The sequence was as follows:
* Started from stock 4.2.2
* Downloaded the latest CF-Root (July 29)
* Manually re-rooted (as instructed on first page)
* Everything is peachy. su in adb shell works, get root prompt, etc. Browsed directories but made no changes.
* Attempted an OTA upgrade to 4.3 (Forgot to re-lock the bootloader). Upgrade failed, giving some generic (as in uninformative) error message. I think it was something about file check failed,
Now the tablet boot-up doesn't get past the colored X. I can get into bootloader/fastboot mode (robot on back with panel open). The device information is as follows:
Product Name: manta
Variant: wifi
H/W Version: 8
Bootloader Version: MANTALJ12
Carrier Info: NONE
Serial Number: <looks okay>
Lock State: UNLOCKED
Reboot Mode Flag: NONE
This is where I was when I first loaded CF-Root. However, now "adb devices" on the PC (Arch Linux) gives a blank list of devices. When I try to load the factory 4.3 image with "fastboot -w flashall" the PC prints the message:
< waiting for device >
and sits there. Not surprising since adb can't see the device.
I can get into recovery mode (robot on back with red triangle), and can access the menu. Performing wipe data / factory reset hasn't helped. From my PC "adb devices" still shows a blank list of devices.
When I start the "Apply update from ADB" utility from recovery mode, "adb devices" on the PC shows:
???????????? no permissions
If I then enter "adb sideload <file>" on the PC as the prompt on the tablet suggests (the file I used was an Android 4.3 upgrade zip file), the PC responds with:
error: insufficient permissions for device
Does anyone have any idea how I can get my tablet out of this mess? Right now all I want is to get my tablet working again. Any ideas are most welcome.

There's no point in running CF-Autoroot -before- updating to 4.3. You lose root after the update.
Also, just because you don't know what the error message means, doesn't mean it's not informative. What exactly was the error? Try fastboot mode and use the Nexus 10 toolkit located here: http://forum.xda-developers.com/showthread.php?t=2001868 to do a full flash. At this point it sounds like you've manually flashed a bunch of stuff so the regular update zip file is probably insufficient and you should be using the full factory image.

Solved
Got it solved (whew!). Had to run fastboot as root on the PC.

plastikowl said:
There's no point in running CF-Autoroot -before- updating to 4.3. You lose root after the update.
Also, just because you don't know what the error message means, doesn't mean it's not informative. What exactly was the error? Try fastboot mode and use the Nexus 10 toolkit located here: http://forum.xda-developers.com/showthread.php?t=2001868 to do a full flash. At this point it sounds like you've manually flashed a bunch of stuff so the regular update zip file is probably insufficient and you should be using the full factory image.
Click to expand...
Click to collapse
Yeah, I knew I'd lose root, but I'd already installed CF-Autoroot. Figured it would be easy to root again after. Foolish me!
Afraid I forgot to write down the error so it's lost. I was trying to do a full flash but failing (see my "solved post"). The update attempt was desperation, trying to get to the tablet somehow.
Anyway, I managed to do a full flash to the 4.3 factory image, so my tablet is no longer an expensive paperweight.
Thanks very much for yout input.

[Q] Help: No OS installed message after lastest OTA update

Hi,
Following a tutorial on this site, I managed to root and install TWRP 2.6 on my nexus 4 and I had Android 4.3 running. After a notification about an OTA update (I believe the second very small security update), I'm now stuck on the Google name at boot. No coloured animation or anything.
I can still get into TWRP but it shows the "No OS installed" message (rebooting anyway gets me the white Google name).
It seems that fastboot is no longer working either.
adb devices works but fastboot devices does not.
I tried the TWRP sideload feature to install the latest OTA 4.3 image but that did not work either.
I searched for this error and one thread required fastboot, which does not work and the other suggested using adb push. I pushed the latest 4.3 OTA but the installation failed. I then pushed the stock 4.3 image but its installation failed as well. (the error was : "No MD5 file found" and "unable to mount /system"
I don't know much more about adb so I really need help to get my nexus 4 working again
Any suggestions?

Double_U said:
Hi,
Following a tutorial on this site, I managed to root and install TWRP 2.6 on my nexus 4 and I had Android 4.3 running. After a notification about an OTA update (I believe the second very small security update), I'm now stuck on the Google name at boot. No coloured animation or anything.
I can still get into TWRP but it shows the "No OS installed" message (rebooting anyway gets me the white Google name).
It seems that fastboot is no longer working either.
adb devices works but fastboot devices does not.
I tried the TWRP sideload feature to install the latest OTA 4.3 image but that did not work either.
I searched for this error and one thread required fastboot, which does not work and the other suggested using adb push. I pushed the latest 4.3 OTA but the installation failed. I then pushed the stock 4.3 image but its installation failed as well. (the error was : "No MD5 file found" and "unable to mount /system"
I don't know much more about adb so I really need help to get my nexus 4 working again
Any suggestions?
Click to expand...
Click to collapse
download a nexus 4 toolkit and try to adb sideload a rom. then flash it through twrp. had similar issue and the toolkit adb sideload option resolved my problem.

blankit said:
download a nexus 4 toolkit and try to adb sideload a rom. then flash it through twrp. had similar issue and the toolkit adb sideload option resolved my problem.
Click to expand...
Click to collapse
Wow, followed your advice and am now running CM 10.1.3.. Will see whether I keep it or try to return to stock but I'm so relieved that at least my phone is working again. Thanks ever so much!!

Your welcome.
Sent from my Nexus 4 using XDA Premium 4 mobile app

[Q] LollIpop installation failed: stuck in "No command"

Hi guys!
This is my first time on this website and I'm here because I need the help of you!
Yeah, I do have a Nexus 7 (2012), it was on 4.4.4 root. Of course, like an idiot, when I saw the OTA of Lollipop, I download it and install it right away. Of course, I didn't unroot before...
So yeah, actually, I'm stuck in a loop between the tablet rebooting and the "No command" section (I guess it's name recovery)
All this was yesterday. That night, I tried everything I could try from my expertise. I've used the Nexus Root Toolkit to flash stock + unroot but with no succes. The main problem is that the only way for my N7 to be recognize by my computer is by "Apply update from ADB" (Sideload from recovery). So my driver aren't good for beeing use with the NRTK and I can't do anything... Then, I can't fastboot or anything, if I try something, It keep rebooting up.
So I hope I've been enough clear. (I'm french so )
Please, take the time to help me! This N7 is very important for me!
Sincerely,
Gabriel

I tried the OTA update on modified stock android, and it failed locking me out, it would boot loop 3 times, then go to the 'No command' - you need to hold all three buttons, power and both the volumes when it's turned off, then it should boot into fastboot with recovery options. If you are stuck on 'no command' - if you hold power and volume up you'll get some options including reboot.
So from fastboot, I didn't do anything here because recovery didn't work for me, but if you are in fastboot, I connected it to my PC and opened nexus toolkit - I had no ADB access but fastboot was available, so I had to flash individual images using that software. So I downloaded the IMG files for android 5 for the nexus 2012 manually, its a tgz archive, extracted it and there was another tgz archive inside which had the individual files I needed to flash. Boot.IMG and system.IMG are the main ones.
In nexus toolkit I went to Advanced and in the first column near the top I clicked Fastboot, then in the next column at the top, I clicked the permanent option, and below that in the middle column it lists all the android flashable files, boot, recovery, system, user data. These will match your files in the archive that was inside of the IMG archive you downloaded from google, boot.IMG, recovery.IMG, system.IMG, user data.IMG. I only needed to do flsash boot and system, recovery didn't work as it said it needed ADB access, and I didn't do user data as I don't think it was important and it wasn't necessary.
I naturally flashed boot.IMG first, then I had to flash the system.IMG twice as it didn't seem to do anything the first time. The second time it took 2-3 minutes then rebooted, and started booting into Android 5, the first boot will take 10 minutes.

[Q] Bricked?

Hopefully someone can help me here.
I have the N10 and it is rooted. I flashed the stock recovery and flashed the stock kernel.
So I should have been pretty much stock cause I had the 4.4.4 factory image on it except it was unlocked.
So then I let it do the OTA for lollipop.
When it rebooted into recovery it got about 1/3 and then hit an error (just said error).
Now I can only get it to the recovery screen and the reboot Mode Flag is 'Recovery'
The only thing I can do at that point is hit the power button and it reboots to recovery with a "No Command" error.
Help please!
EDIT: The thing finally booted up on it's own. Should I leave it alone or try to take the OTA update again?

sl2222 said:
Hopefully someone can help me here.
I have the N10 and it is rooted. I flashed the stock recovery and flashed the stock kernel.
So I should have been pretty much stock cause I had the 4.4.4 factory image on it except it was unlocked.
So then I let it do the OTA for lollipop.
When it rebooted into recovery it got about 1/3 and then hit an error (just said error).
Now I can only get it to the recovery screen and the reboot Mode Flag is 'Recovery'
The only thing I can do at that point is hit the power button and it reboots to recovery with a "No Command" error.
Help please!
EDIT: The thing finally booted up on it's own. Should I leave it alone or try to take the OTA update again?
Click to expand...
Click to collapse
Same for me. I'm trying to even manually flash the factory image, but it will not detect fastboot. I'm trying to research this now. The device just keeps restarting itself over and over into No Command.

IT Rider said:
Same for me. I'm trying to even manually flash the factory image, but it will not detect fastboot. I'm trying to research this now. The device just keeps restarting itself over and over into No Command.
Click to expand...
Click to collapse
Hi, I have exactly the same problem after installing Android 5.0 OTA. Please post a solution here if you find it. Thanks!

I didn't try the OTA again. I installed Lollipopalooza from this thread...
http://forum.xda-developers.com/showthread.php?t=1998585
No problem with it so far

sl2222 said:
I didn't try the OTA again. I installed Lollipopalooza from this thread...
http://forum.xda-developers.com/showthread.php?t=1998585
No problem with it so far
Click to expand...
Click to collapse
But I cannot flash any rom as none of ADB commands can be run (device is not connected, though I connected it with OEM cable). I tried factory reset but it didn't help.

Just wanted to share what worked for me after the OTA update failed and flashing stock images didn't work. Put the tablet in fastboot. Installed stock image, tablet wouldn't boot. Restarted went into recovery got the android on its back with the red x coming out of it (did not say bad command at thia point). I presses volume up and power at the same time on this screen. Cleared cache and rebooted then the tablet booted up.

I cannot believe companies still get away with this inadequate device "killing" type of software. Did no-one at the company do any testing before release?????
Rant over, onto solution - for me anyway.
The issue I had was that I could not get ADB to be of any use so switched to fastboot. Should have used fastboot from the getgo. Hohum.
So, into recovery with android on it's back with red triangle and reboot into fastboot.
Connect N10 to PC with USB cable.
Downloaded "Minimal ADB and Fastboot"(MAF)
Downloaded Lollipop for Nexus 10 - image-mantaray-lrx21p.zip and saved to c: drive (this saves loads of typing at command prompt)
File path for update is c:\image-mantaray-lrx21p.zip
Open MAF and ensure folder path points to your MAF install folder..
At command prompt type fastboot update c:\image-mantaray-lrx21p.zip
If you want to wipe device prior to update then type fastboot -w update c:\image-mantaray-lrx21p.zip
This may take a while so go make a drink - or something.
If all goes well, mine did, you should eventually be presented with the lollipop opening screen and a working device.

Just finally got it working!
ROM updates from ADB Sideload or Fastboot failed every time for different reasons.
What I had to do is to flash custom recovery (latest TWRP) with "fastboot flash recovery <recovery.img>" command.
From TWRP flashing the official ROMs also failed. But flashing Lollipopalooza as sl2222 suggested finally succeeded.
Thanks for all the help!