Nexus 7 2012 32GB wifi, Stock, Unlocked, Rooted, TWRP.
I am new to adb, but have used Wug's toolkit in the past. I attempted to sideload the Lollipop OTA zip through through Wug's toolkit. Everything was going well, but for some reason I got an error that stated that there was not enough room to install the update. I figured that was the end of that, but when I tried to reboot, it went straight to the stock recovery, and will not boot past that. Did some poking around in the toolkit, and found I didn't have fastboot anymore. (Also, I did not make a backup, stupid stupid, because I had recently wiped everything, and have the factory images downloaded). So, with the toolkit not getting me anywhere, I decided to try getting back to running through ADB. Read some tutorials, downloaded SDK, get that all set up so I can see where I am at. Command window, Type "adb devices", get "serial # sideload. Tried "adb reboot recovery", got no devices.
Probably should have just stopped but, since I knew I had USB debugging on, and all the newest drivers installed (just ran the toolkit) I figured why not try to sideload from here? Not enough Space again. Tried sideloading OTA 4.4.4(KTU84P) which is what I was running up to this point, and get unexpected contents error in "system/app/basicdreams.apk" "status 7".
Top of screen says:
Android system recovery (3e)
KTU84P
Long story short; Stuck in stock recovery, No Fastboot, Apply update from ADB works, but haven't anything to finish installing.
Thanks for any help, you guys are awesome, and give me way too much info for my own good, obviously.
Got back to working at this. WUG's toolkit fixed it. Just like every answer, in every thread with similar problems said it would. Using the flash stock +unroot and the soft brick/bootloop option. Since i was on Bootloader version 4.23, I flashed 5.0. Not sure what was different this time, as I tried the same process last night.
Anyway, anyone having the same troubles should give that a try.
Related
i was stuck in a bootloop after flashing a ROM, and didnt have any backups or other ROMs on the devices storage, so i was attempting to push files to it via ADB, but it wouldnt connect. i went back into the custom recovery image, and accidentally wiped the whole thing, so now i have no OS installed, and not even the seeminly 'faulty' ROM in /sdcard either. i can still get into the bootloader and the custom recovery, but cant seem to get it to connect to ADB. any ideas what i can do?
If you could boot into fastmode, then just flash stock rom.
Leonhan said:
If you could boot into fastmode, then just flash stock rom.
Click to expand...
Click to collapse
how do i boot into fastmode? all that i can access is the bootloader, and TWRP. when on the bootloader screen it sort of connects to my PC. i can go into device manager, and will see 'android bootloader interface' in there, and i have updated the drivers as per the instructions in the nexus root toolkit, but it wont seem to talk to ADB for some reason.
edit: ok, this is really odd. when i use the NRT to try pushing a zip file, if i start the it trying to push the file, then open a command line and use 'adb usb' NRT will say that it has connected to the device, and goes through its various steps, and ends up booting the device into recovery, but the actual zip it was supossed to have pushed isnt there...
it made it enter twrp, so it must be communicating in some way, but when i type 'adb devices' it doesnt show up...
bmoreyce said:
how do i boot into fastmode? all that i can access is the bootloader, and TWRP. when on the bootloader screen it sort of connects to my PC. i can go into device manager, and will see 'android bootloader interface' in there, and i have updated the drivers as per the instructions in the nexus root toolkit, but it wont seem to talk to ADB for some reason.
edit: ok, this is really odd. when i use the NRT to try pushing a zip file, if i start the it trying to push the file, then open a command line and use 'adb usb' NRT will say that it has connected to the device, and goes through its various steps, and ends up booting the device into recovery, but the actual zip it was supossed to have pushed isnt there...
it made it enter twrp, so it must be communicating in some way, but when i type 'adb devices' it doesnt show up...
Click to expand...
Click to collapse
Stop using the toolkit and read the sticky that's not too far above your post... the one titled, "[GUIDE] Flashing a Factory Image with fastboot / return to stock." Coincidentally, it happens to be exactly what you need.
najaboy said:
Stop using the toolkit and read the sticky that's not too far above your post... the one titled, "[GUIDE] Flashing a Factory Image with fastboot / return to stock." Coincidentally, it happens to be exactly what you need.
Click to expand...
Click to collapse
when i use ADB in a cmd window, it just says theres nothing connected. ive downloaded the stock image, and am currently writing it using the toolkits function, and it seems to be working so far, whereas doing it the other way, i cant seem to even get ADB to work. no idea whats going on, but it seems to be working with the toolkit
EDIT: the toolkit worked. am back on stock. thanks for your help guys.
bmoreyce said:
when i use ADB in a cmd window, it just says theres nothing connected. ive downloaded the stock image, and am currently writing it using the toolkits function, and it seems to be working so far, whereas doing it the other way, i cant seem to even get ADB to work. no idea whats going on, but it seems to be working with the toolkit
EDIT: the toolkit worked. am back on stock. thanks for your help guys.
Click to expand...
Click to collapse
You don't need ADB if you are in the bootloader- you use fastboot.
So I wanted to try Cataclysm, but was having issues switching to it from PA. It always kept booting into PA so I decided to do a full wipe. I did a full app backup and a nandroid backup using NRT. I first tried a regular factory reset, but eventually decided to wipe everything, even /system (a mistake, I now see). After I did that, I tried using NRT to flash stock + unroot. The NRT script gets through everything fine until it gets to the terminal part and says there's no 'boot.sig', 'recovery.sig', or 'system.sig'. It also fails the baseband version check. Don't know if it's even relevant, but it says something failed so I thought I'd include it. After that it tells me it will look like it's boot looping, but it just sticks in fastboot mode. If I wait 20 minutes nothing happens. If I push START it hangs on the Google screen but never gets any further, even 30 minutes later. I've tried pushing a custom zip and install in in TWRP. I've tried flashing a new kernel. Whatever I try I cannot seem to get any further than the boot screen. At this point I'd be happy with stock. I just want my phone back. What do I do?
I'm assuming NRT is a toolkit?
From here on, don't use a toolkit if you know how things work. Manual is the way to go.
Boot into fastboot, choose recovery, go into TWRP, advanced, ADB SIDELOAD.
Now use command prompt or terminal on your computer (depending on your OS), navigate to where you installed your toolkit, there should be a .exe or .sh called adb and fastboot.
Download your preferred rom and gapps, transfer it to this folder.
Now simply do a command "adb sideload *zipname*.zip " and it should transfer and flash your phone.
Don't flash a kernel yet, wait till you finish your first boot, then only you flash it.
I tried exactly what you said to flash the stock image. The terminal said it had transferred 100%, but TWRP said the sideload failed.
Hamalot said:
I tried exactly what you said to flash the stock image. The terminal said it had transferred 100%, but TWRP said the sideload failed.
Click to expand...
Click to collapse
that's because you can't flash the stock image like that.
Download CM and try.
It worked! Thank you so much!
I stupidly started the OTA update on my rooted device and it failed. Now I am stuck at the 4 circles animation after the Google logo.
I've tried following the guide to flashing a factory image with fastboot / return to stuck but at the step where I'm supposed to be able to list devices (step 3 of driver installation), no devices are listed.
In my Device Manager, the Nexus 7 is listed as MTP USB Device with a yellow warning triangle over the icon.
I've gone over the installation instructions many times and repeated the process 4 times.
What else can I do?
Now I see Android Device and under that Android Bootloader Interface in my Device Manager (using Windows 8) when I am in fastboot.
I tried updating the driver per instructions (although it only has instructions for up to Windows 7) and the message says that I have the most updated driver already.
However, my device is not listed once I try the command "adb devices"
I guess I am in "driver hell" but what how do I fix this? I've tried installing and uninstalling everything multiple times.
My N7 was rooted and has CWM. (Yes I know I know that I shouldn't have done OTA but I made a mistake.)
I had a similar problem, though on mine the installer ran after I said not to. Afterward my tablet would start up but stay on the four pulsing circles. I tried waiting and after an hour figured that wasn't going to work.
This is how I got my tablet working again. Mine is the wi-fi 2012 version. I first followed that same guide as you and it wouldn't work. So I tried a diffrent way.
after step 8 on that Flashing a Factory Image with fastboot / return to stock guide, installing the "Google USB Driver",
Download and install the Nexus Root Toolkit from Wugfresh (can't post links yet).
Set the tablet as the Nexus 7 (Wi-Fi Tablet) and Android build 4.3.0 JWR66Y
Then Flash Stock and Unroot under Back to Stock with Soft-Bricked/Bootloop chosen.
I chose the same factory image that I had set my tablet as, 4.3.0 JWR66Y.
Once it ran I was back on 4.3.0 and had a working tablet again.
annabwashere said:
However, my device is not listed once I try the command "adb devices"
I guess I am in "driver hell" but what how do I fix this? I've tried installing and uninstalling everything multiple times.
Click to expand...
Click to collapse
http://www.wugfresh.com/
Download and install Nexus Root Toolkit.
It comes with several ADB drivers and shows information about that.
Worked! Thanks!
Hey guys,
i'm really sorry to bother you, i'm normally not the type of guy who jumps to "help me" real quick. However, since there doesnt seem to be anyone else with my Problem, and i couldt fix it by reading stuff myself, here i go.
Basically, i started off with a brand new internat. G2, D802. I didnt accept any OTAS.
I rooted it with ioroot, no problem. Afterwards, i installed CWM 6.0.4.4. Semi-touch as described in this thread: http://forum.xda-developers.com/showthread.php?t=2468858. Still no problem. Everything booted fine, no bootsloops, no nothing. Perfect so far.
Made a Nanondroid, saved my EFS. Backed it up. So far so good.
Then, i dl´ed the newest CM 11 Nightly, 12.12.2013. I went into Recovery, and did FactReset -> Format Sys -> Wipe Cache -> Wipe Dalvik
When i tried to install CM, a "status 7 error" was returned, i can give the complete message any time. Maybe i hit a corrupt download, idk.
Well, under "mount storage", connect an usb storage didnt work, so i guess i´m stuck with sideload.
I read some tutorials, and when showing the devices with my phone being in recovery, it shows "XXXXXX (some number, guess my mac-adress), recovery". SO i guess thats fine.
I then enabled "install zip via sideload" in cwm, and did "adb sideload /PATH/NEWLYDOWNLOADEDROM.ZIP". Wont work, all it returns is the list of commands.
Doing "adb push /PATH/ROM.ZIP /sdcard/XXX" does seem to copy something, however, when accessing that folder, it says theres no zip there.
i'm kind of at a loss now. Entering CWM works without fail, but how to proceed? I still have the Nandroid on my phone to resort to, but well, id rather get stuff working.
Thanks for help guys. All your hard work is appreciated.
Well, i managed to push stuff to my phone successfully now, still that error: set_metadata_recursive: some changes failed.
Googling stuff returns that it seems to be an error with CWM. However, i am still using the latest version. Even so, how do i up/downgrade (maybe offical version) in cwm itself? Or do i have to use a 3rd party programm.
how were you able to push to the phone? I cant get ADB to read my phone through twrp
Owell, ended up fixing stuff myself.
What i did was:
Download an the official CWM from http://forum.xda-developers.com/showthread.php?t=2468858.
Then go to where your adb stuff on your pc is, shift+right click -> open command prompt here. Connect your phone to the pc via usb cable, while beeing i recovery (i guess cwm or twrp shouldnt matter).
In Cmd, do:
adb kill-server
adb start-sever
adb devices
that should bring up something like [Some Number, your phones mac-address] recovery
all the while, do not start "install zip via sideload" in your recovery. I did not need that at all.
in your command prompt, type:
adb push PATH_TO_YOUR_DOWNLOADED_RECOVERY/WHATEVER_ITS_NAME_IS.zip /sdcard/WHATEVER_ITS_NAME_IS.zip
it will copy the recovery to your /sdcard-folder.
Type "adb kill-server" and unplug phone (did it just to be sure, idk if its necessary)
In your recovery, just install the downloaded .zip-recovery, and under "advanced" do reboot recovery.
It left me with a touch version of cwm 6.0.4.4, the same version number as before. However, this time installing the latest cm-11 nightly worked just fine.
Idk if the unofficial one is bugged, but best someone post that in the cwm-recovery thread. I cant, since my post are not over 9000.
Hope it helps.
im having this issue on my VZW LG G2. Im stuck in CWM getting Status 7 abortions when trying to flash cm 10.2. Rooted with io. I was on OTA 12B and looking for a fix.
Fixed it myself, thanks.
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!