Database Users

Nexus 7 wont boot pass google logo after root/unroot

I got a nexus7 a week ago but decided to root the device today just to try apps which require root, i rooted it fine but i decided to unroot and thats where the problem started i cant boot pass the google image, i can get into where you hold down volume and power for so many seconds and team win recovery which says i have no OS in the reboot section, i've tryed nexus 7 toolkit v3.2.0 and nexus root toolkit to restore back to factory system but no luck, so is it me doing something wrong or is my nexus 7 just a paper weight now.

Doubt it,
Being you still have a custom recovery you didn't follow the right steps to unroot, might need to unlock the bootloader again, but follow one of the many guides, and try to stay away from a tool kit
Sent from my HTC Vision using xda premium

Unlock bootloader
Flash boot, recovery, system, userdata.
Files are zipped in the factory images directly from google.
Wipe cache.
Relock bootloader.
Reboot into recovery.
Factory reset. (Nexus 7 will only see 8GB if you don't do this step)
That is the gist of how it's done.

I followed a step by step guide on laptop man website but when i come to flash the android image it says file too large, i used 4.2.1 from googles site, if i'm correct when you type fastboot -w update image-nakasi-jro03d.zip (in the walkthrough) i can replace it with a later newer android in this case 4.2.1 jop40d

You could do it that way. Some people have. Although I received an error every time I did.
I didn't receive an error when I flashed the files in the zip.
First make sure you have the correct factory image for your device downloaded.
Then make sure you extract the boot.img, recovery.img, system.img, and userdata.img files to your fastboot folder and perform the following actions...
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot-bootloader
fastboot oem lock
Lastly, boot your system up into recovery and perform a factory reset from there. If you don't do the last step they you will be stuck with ouly 8GB, vice 16 or 32.
It's that easy.

When i try to boot into recovery mode i get the android mascot with a red triangle, does that mean i have no recovery file.
OOOPS the system booted up into android as the recovery mode didnt work (as above) is there anyway i can reset to factory settings to get the 32GB back as it shows 6GB.
Update: I think i sorted it out now somehow as it shows up as 27.oddGB now (about same as i got it) instead of 6GB, anyway thanks for your help, it seemed complex well it is but once you know whats what it's not so, the hardest part is getting the files and putting them in the right places

When I try to reboot to recovery via the bootloader it just hangs... Can boot to recovery inside android (usually using Rom Manager or another reboot application)... any idea why?

I have read reports that it will hang when booting into recovery if not connected to a PC.
And as for that triangle you see.... That's normal.
That means that your in recovery mode. Your menu is just hidden.
Press power and volume up to view it.

[Q] Factory image restore fail : stuck at writing system

Hello everyone!
I tried to restore the stock image using Nexus 4 Tool Kit (both the original one and the Wug's one), and everytime I tried, the script stucked at "writing system".
I manually flashed system and userdata images with Wug's tool kit and everything went well but I only have 5Gb memory instead of 16.
Does anyone know why?

Try this http://forum.xda-developers.com/showthread.php?t=2033692
[HOW-TO] Fix internal storage if 16GB now shows 8GB
Sent from my Nexus 4

OP...
In future, don't use a toolkit. Do it yourself

I'm having a similar problem to the OP - I'm trying to do a factory restore, and am unable to flash the "system" image. I can't boot, recovery mode won't work anymore (I get a red warning sign instead)...
I think all of this has to do with me being naieve and following a youtube video instead of the CM wiki to install CM 10.1.
How can I unbrick my phone?

4OnTheFloor said:
I'm having a similar problem to the OP - I'm trying to do a factory restore, and am unable to flash the "system" image. I can't boot, recovery mode won't work anymore (I get a red warning sign instead)...
I think all of this has to do with me being naieve and following a youtube video instead of the CM wiki to install CM 10.1.
How can I unbrick my phone?
Click to expand...
Click to collapse
When going into recovery the warning sign is the splash screen for stock recovery. This likely means that you have not yet flashed a custom recovery yet, which is necessary to flash CM. First read this guide to unlock the bootloader (if you havent already), then flash a custom recovery (preferably TWRP). After you have installed the recovery, download CM as well as the latest gapps package and place them somewhere on your internal sd. Boot into recovery and go to the wipe menu, then swipe to factory reset. Finally flash the rom and gapps, and then reboot.

4OnTheFloor said:
I'm having a similar problem to the OP - I'm trying to do a factory restore, and am unable to flash the "system" image. I can't boot, recovery mode won't work anymore (I get a red warning sign instead)...
I think all of this has to do with me being naieve and following a youtube video instead of the CM wiki to install CM 10.1.
How can I unbrick my phone?
Click to expand...
Click to collapse
if you are doing a factory restore and DONT need to flash everything individually than don't. yes its good to know how to do it manually but if your flashing everything back just use the script that google provides.
reboot to bootloader/fastboot and run the flash-all.bat file and its all done for you. no toolkits no playing with commands that you dont know properly etc.
if you dont know how to do it right pick the least complicated option.

noobdeagle said:
if you are doing a factory restore and DONT need to flash everything individually than don't. yes its good to know how to do it manually but if your flashing everything back just use the script that google provides.
reboot to bootloader/fastboot and run the flash-all.bat file and its all done for you. no toolkits no playing with commands that you dont know properly etc.
if you dont know how to do it right pick the least complicated option.
Click to expand...
Click to collapse
I am using the .bat file... I've also tried the toolkit, and both appear to use the same basic procedure, and they stop at "writing system" no matter what.
Does anyone happen to know how the .bat file and toolkit get access to the phone? ...because I can't see it in adb (I'm guessing it's because I can't boot the phone.) However I can get into fastboot and recovery modes on the device.
I cannot get the device (nexus 4) to boot or connect in ADB mode to my computer. What can I do??
UPDATE - PROBLEM FIXED
I un-bricked my phone
SOLUTION this is what worked for me, your mileage may vary
Install ADB drivers, etc. from Android SDK (google how to do this)
Flash custom recovery (can be done easily with Nexus 4 Toolkit here on XDA) - I used TWRP Touch Recovery.
Once that is done, shut the phone off completely and boot into Fastboot (hold volume down and power)
Use volume keys to select Recovery Mode, then hit Power
In recovery mode:
Wipe > Advanced Wipe > Check off the box beside "System" > Swipe to Wipe
Go back to recovery mode main screen:
Wipe > Format Data > Follow the instructions on the screen
I think this step is what did it. When having problems with partitions, just format everything and start over
Now we should be able to write to the System partition, meaning you can flash a ROM and get your phone to boot again.
Follow the rest of these instructions to quickly flash the stock Android image from Google onto your phone.
Go back to recovery mode main screen, once again:
Reboot > Bootloader > Follow any additional instructions it gives you
Download Google Nexus 4 factory stock image "occam" (Google it)
When that is downloaded, open it with 7zip. Inside there are some files, one of which is called image-occam-jdq39.zip. Inside are some images - unzip those as well. You'll need the system.img file in a bit...
Using Wug's Nexus Root Toolkit (Google it - install it on your Windows PC):
Open the program
Launch advanced utilities
Hit the System button to permanently flash to System partition. Hit "ok" on the window that pops up.
Find the system.img file I mentioned back on step 10 and select that, when prompted, and open it.
If all went well, your device will now boot into the stock Android ROM.

noobdeagle said:
if you are doing a factory restore and DONT need to flash everything individually than don't. yes its good to know how to do it manually but if your flashing everything back just use the script that google provides.
reboot to bootloader/fastboot and run the flash-all.bat file and its all done for you. no toolkits no playing with commands that you dont know properly etc.
if you dont know how to do it right pick the least complicated option.
Click to expand...
Click to collapse
I too am stuck at writing system. I"m not sure what you mean when you said "run flash-all.bat". Where do I get that?
Thanks.

Soundchasr said:
I too am stuck at writing system. I"m not sure what you mean when you said "run flash-all.bat". Where do I get that?
Thanks.
Click to expand...
Click to collapse
The system takes awhile to write, how long have you guys wait before you say its "stuck"?
Sent from my Nexus 4 using Tapatalk 4 Beta

About 20-25 minutes.

Yea, that's way too long.
Sent from my Nexus 4 using Tapatalk 4 Beta

Stuck, but working
I was flashing the 4.3 image using the included flash-all.bat (but I edited it to remove -w parameter so that it wouldn't wipe my data).
In the 'writing system' step, the command window got stuck. In the phone screen, at the bottom, it said 'writing' for a while and then that also went away. I waited for ~40 min, and still the command window was at 'writing system', so I closed the command window, and booted my phone by selecting start from the bootloader.
And voila! It worked. Booted in under a minute, the flash was a success, I got JB 4.3 without losing any of my data.
Lost my root and custom recovery though. But I knew that would happen. Gonna try SuperSu for 4.3 now, after flashing TWRP.

Had the same problem, tried everything! With my tiny powers, but it kept stucking at "writing system" . I thought that I bricked the device, so for the last hope, I installed WugFresh's Nexus Toolkit and did a Fast Stock + unroot. It Installed everything flawlessly! I'm gonna donate to that guy! He's a godsend savior.

How to Root without flashing custom recovery

HOW TO ROOT YOUR DEVICE WITHOUT FLASHING RECOVERY
This can be done with two methods.
ADB or FASTBOOT.
I have tested both methods and they worked for me.
I tested this on JSS15J. I am not sure about any other versions but I guess it should work.
SOME BASIC INFORMATION
Usually when you want to root your device, you must have UNLOCKED BOOTLOADER.
A CUSTOM RECOVERY is usually used to flash SuperSU to gain root access.
CUSTOM RECOVERIES ARE USUALLY FLASHED (they permanently replace your stock recovery)
In this guide, You BOOT into custom recovery by going into BOOTLOADER and then using fastboot/adb tools to flash SuperSU .
Booting is temporary and thus once you restart from recovery, the custom recovery will be gone
Make sure, you have USB debugging mode enabled. To go into bootloader you can either use adb commands ( Type [adb reboot bootloader] in cmd in platform tools directory with your device connected) or do it manually by turning it off and then holding power and volume down.
You must also have platform tools of SDK (Fastboot and ADB) for this to work. MAKE SURE YOU OPEN CMD into the folder where platform tools are present.
Try it on OWN risk. I will not be responsible for bricked devices or any damage.
ADB METHOD
Connect to your PC and make sure USB debugging is on.
COMMANDS IN BRACKETS. DON'T WRITE THEM. COMMAND WOULD BE LIKE : fastboot boot recovery.img
MAKE SURE YOUR DEVICE HAS UNLOCKED BOOTLOADER
(fastboot boot [recovery.img])--------------------- Name of recovery to be here
Mount /system and push the necessary files once the recovery has started:
(adb push su /system/xbin)
(adb push Superuser.apk /system/app)
Set correct permissions:
(adb shell)------------------------------ You have got into your device's shell
(chmod 06755 /system/xbin/su)
(chmod 0644 /system/app/SuperSU.apk)
(exit)
Reboot:
(adb reboot)
FASTBOOT METHOD
This is relatively easier as you will boot into custom recovery temporarily and then flash ZIP of SuperSU. Afterwards I recommend to clear davik cache and restart.
UNLOCKED BOOTLOADER REQUIRED
Boot into bootloader.
Type these commands to boot into custom recovery. This will not flash recovery and you will have stock recovery once you restart.
fastboot boot recovery recovery.img where recovery.img will be the file name of recovery
(After 4.4, use this command "fastboot boot recovery.img" instead of above mentioned)
After booting into reccovery, flash SuperSU and you are done.
I recommend clearing dalvik cache before leaving and restart.
And you are done.
YOU CAN ALSO USE A PREROOTED KERNEL WHICH YOU CAN FLASH VIA FASTBOOT. I AM NOT SURE IF THERE IS ANY
For information on how to retain root after OTA, please refer to this :
Update Super SU is also taken from this guide.
http://forum.xda-developers.com/showthread.php?t=2415497
For Recovery/SuperSU/TWRP
http://forum.xda-developers.com/showthread.php?t=2382051
CWM
http://forum.xda-developers.com/showthread.php?t=2381544
PLATFORM TOOLS:
http://www.androidfilehost.com/?fid=9390355257214632011
If you are stuck in a bootloop, make sure you have cleared dalvik cache in custom recovery.
I got bootloop when i tried with fastboot method as I was new to twrp, I explored it a bit and tried to remove system and tried overwriting data to see how it is different from CWM and check its strength. I got an error clearing cache so I rebooted into custom recovery to clear dalvik and my nexus booted fine (DON'T TRY THIS, JUST CLEAR CACHE AND WIPE DATA and restart)
REMEMBER, UNLOCKING BOOTLOADER WILL DELETE ALL YOUR DATA AND DOING WIPES WILL ALSO DELETE ALL YOUR DATA.
DALVIK WON'T DELETE YOUR DATA BUT
MAKE SURE YOU HAVE MADE A BACKUP using BACKUP PRO (non rooted) or Helium (non rooted) and Titanium Backup Pro (Daah, you are not rooted so this won't work)
GOOD LUCK

Booting into custom recovery to install root works fine.
As you mentioned unlocking bootloader is still a prerequisite.
You may want to just use the SuperSU install zip though. Though I haven't tried Superuser on this tablet, it is my understanding it hasn't been modified to work with 4.3 security. That may have changed since I last looked so if you find differently please post. SuperSU added a daemon mode to deal with 4.3 security changes.

sfhub said:
Booting into custom recovery to install root works fine.
As you mentioned unlocking bootloader is still a prerequisite.
You may want to just use the SuperSU install zip though. Though I haven't tried Superuser on this tablet, it is my understanding it hasn't been modified to work with 4.3 security. That may have changed since I last looked so if you find differently please post. SuperSU added a daemon mode to deal with 4.3 security changes.
Click to expand...
Click to collapse
I got bootloop but then realised it might due to trying to wipe system in twrp. Clearing dalvik worked fine .SuperSU used

So you don't replace stock recovery if you boot into a custom recovery using fastboot?
Sent from my Nexus 7 (2013)

Muikkuman said:
So you don't replace stock recovery if you boot into a custom recovery using fastboot?
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
The trick here is to BOOT into custom recovery BUT not FLASH recovery permanently. Once you restart, the CUSTOM recovery will be gone.
You can use simple commands if using Fastboot
fastboot boot recovery [recovery name.img]
This way you will install SuperSU using recovery which is relatively easier than ADB commands.
You will only go into recovery temporarily.
I also read a forum where you can preserver root even after OTA/ Updates.
[UPDATE]
http://forum.xda-developers.com/showthread.php?t=2415497
Do check that out as well.
I tried this with Twrp and superSU.
I got bootloop as I have been always CWM person so I accidently tried to delete system too with dalvik cache and hard reset and I got an error
However, I boot again into recovery and cleared wipes and the bootloop was gone

Hnk1 said:
The trick here is to BOOT into custom recovery BUT not FLASH recovery permanently. Once you restart, the CUSTOM recovery will be gone.
You can use simple commands if using Fastboot
fastboot boot recovery [recovery name.img]
This way you will install SuperSU using recovery which is relatively easier than ADB commands.
This way you will only go into recovery temporarily.
I also read a forum where you can preserver root even after OTA/ Updates.
Do check that out as well.
I tried this with Twrp and superSU.
I got bootloop as I have been always CWM person so I accidently tried to delete system too with dalvik cache and hard reset and I got an error
However, I boot again into recovery and cleared wipes and the bootloop was gone
Click to expand...
Click to collapse
Thanks for your reply I'll make sure to check everything out.
Sent from my Nexus 7 (2013)

Muikkuman said:
Thanks for your reply I'll make sure to check everything out.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Anytime mate

How do we clear dalvik without a custom recovery?

Master619 said:
How do we clear dalvik without a custom recovery?
Click to expand...
Click to collapse
You restart your device. Boot into bootloader and use fastboot to Boot into custom recovery(command given in post above).Once Into recovery, you can easily clear dalvik cache.
And remember, it might not require clearing cache because I was exploring twrp n overwriting data n tried To delete system to see how powerful the recovery is. I will update guide now

muikkuman said:
so you don't replace stock recovery if you boot into a custom recovery using fastboot?
Sent from my nexus 7 (2013)
Click to expand...
Click to collapse
master619 said:
how do we clear dalvik without a custom recovery?
Click to expand...
Click to collapse
guide updated. Check it.
Platform tools are being attached

The "fastboot boot recovery recovery.img" command is not working anymore. The command prompt returns with a "cannot load recovery" error. At least that's what it does on my Nexus 7 running Android 4.4.2.
This seems to affect Android 4.3 and upwards according to this Nexus 4 thread: http://forum.xda-developers.com/nexus-4/help/solved-fastboot-boot-recovery-img-t2380675
There's a workaround with a different fastboot command line as mentioned in the thread. I wonder if there's also a fix for the Nexus 7. Any replies would be greatly appreciated.

gunner49 said:
The "fastboot boot recovery recovery.img" command is not working anymore. The command prompt returns with a "cannot load recovery" error. At least that's what it does on my Nexus 7 running Android 4.4.2.
This seems to affect Android 4.3 and upwards according to this Nexus 4 thread: http://forum.xda-developers.com/nexus-4/help/solved-fastboot-boot-recovery-img-t2380675
There's a workaround with a different fastboot command line as mentioned in the thread. I wonder if there's also a fix for the Nexus 7. Any replies would be greatly appreciated.
Click to expand...
Click to collapse
Did you try: fastboot boot recovery.img ?

mdamaged said:
Did you try: fastboot boot recovery.img ?
Click to expand...
Click to collapse
That worked a treat! Thanks a lot mate!

Those who finding difficulty in rooting Nexus 7 (2013) can use Wugfresh Nexus Root Toolkit. It is so powerful that you would find every function you would like to do on your Nexus 7, from the comfort of your PC. Also watch qbking77 's video on using the Toolkit for further information.

Softbrick?, stuck in fastboot

Hello,
I was attempting to update from 4.3 SlimBean to 4.4 SlimKat Weekly.
I booted into CWM Recovery, wiped system, cache, dalvik cache etc, and went to flash the rom.
The rom must have been corrupt or something, as I was unable to and received an error.
I rebooted and was stuck in fastboot.
From here, I've tried both Wug's Nexus Root toolkit, and the Skip Root toolkit.
Running the return to stock and unroot whilst in fastboot in either of them caused a crash of fastboot.exe and the Skip Root equivalent.
After a reboot Wug's allowed me to atleast run the program, but I received link errors, so tried again. This time it couldn't find it, unplug, replug. Link errors, cant find it and this repeated.
Skip also allowed me to after reboot, but gave the exact same faults.
That's as far as I've really got. I occasionaly get it to run, and it seems to work only for it to get part way in, sometimes after sending the bootloader, or on the bootloader and it can not find any devices.
For some extra info, this is Running Windows 8.1, using a USB 3.0 Front panel header and tried using default cable, samsung and kindle ones too.
I'm looking for any ideas? Worst case scenario is I can try when I'm back home at the weekend and there I have a PC with XP that I have used previously to fix this style of boot error.
Cheers,
WiiManic

Stop using toolkits, issues love to pop up for those who do
Make sure bootloader is still unlocked
If not
fastboot oem unlock
Flash latest twrp or cwm or whatever, just download the image and open cmd in this location
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
Now boot to new recovery
Go to advanced
Adb sideload
On PC go to ROM of choice, maybe slimbean
adb sideload nameofrom.zip
When complete
adb sideload nameofgappsoranythingelseneeded.zip
Reboot
Sent from my Nexus 4 using XDA Premium 4 mobile app

[Q] Boot Loop (CM Recovery)

First of all, I know that there are many people asking same thing. I have checked those threads and I guess I am just a little bit more clueless. Last time I was able to use my Nexus 10 was 3 months ago. Since then I tried to solve it many times, but no luck so far. I will try to explain some of the issues I'm experiencing, but I'm afraid I'm not too good with all the expressions people are using on this forum.
1. ADB vs Fastboot
I see this mentioned often and I don't know what exactly it means. It's amazing to me that I can't google it, I'm usually good with googling. I can see that my N10 is sometimes listed under ADB and sometimes under Fastboot devices but I have no idea what I did to change that. I do know that whatever I try to do at certain point, it's always in "wrong" mode, waiting for adb etc. So if someone can point me to a thorough explanation, a wiki or something, that would be very nice.
2. The Loop
I managed to get ClockworkMod v6.0.4.3 installed and it's this loop that device is now inside. I've tried pretty much all possible combinations, wiped both caches, did factory reset, rebooted to system/bootloader/recovery... nothing. Always ends up on same CM menu.
3. Android Toolkit
I have installed this on my computer and tried so many things that I forgot about all details. I tried flashing the big 400 MB stock image to the device, but haven't been successful (says waiting for ADB, even if the device WAS listed as ADB device before I started the procedure). I am also expecting to see the N10 as another "drive" from my desktop, if you know what I mean, so that I could copy files to it. However I don't see it that way, I only see it registered as a Nexus 10 device, like a mouse or any other non-drive device. Is this normal?
So what to do? Can anyone tell me in a simple way, because I am obviously stupid enough to find threads I've seen so far not clear enough. And I would actually think that my computer literacy level is rather high, I think that this Nexus 10 is the only thing that brought me to my knees in last 20 years of working with computers.
And when I say "simple wiki style" I'm thinking of something like this:
Ok. no links allowed, great. It's a redmondpie article named
/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
This is easy enough for me... but do I assume correctly that all this has already been done with me installing Android Toolkit? If so, it uses a different path structure and I don't see all those folders...

So u do have cmw installed, when u try to flash a ROM it just boots to recovery?
Sent from my Nexus 10 using Tapatalk

newellj79 said:
So u do have cmw installed, when u try to flash a ROM it just boots to recovery?
Click to expand...
Click to collapse
You mean flashing ROM only with CWM, not through android toolkit? Through CWM menu I have tried (many times):
- wipe data / factory reset
- wipe cache partition
- wipe dalwik cache
I don't see way to do anything with:
- install zip
- backup and restore
- mounts and storage
Rebooting menu items do following:
- Reboot system --> reboots to same CWM recovery menu
- Reboot to bootloader --> reboots to the stock bootloader "menu" where I can choose between Start, Power Off, Recovery mode (picking this will reboot to CWM recovery menu) and Restart bootloader (picking this will reboot to this same menu)
- Reboot recovery --> reboots to same CWM recovery menu

1 adb works only in os and recovery, fastboot works only in bootloader
2 it looks like your recovery is screwed up, flash this with fastboot
http://techerrata.com/file/twrp2/manta/openrecovery-twrp-2.6.3.1-manta.img
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
3try not to use toolkits, you have a nexus, toolkits are more complicated than manual methods and you won't learn anything from it
Once you have recovery
Wipe all, then you will will need to use adb sideload to flash ROM as you have no ROM on emulated sdcard
Go to advanced menu
adb sideload
adb sideload nameofROM.zip
adb sideload gapps.zip
For more info on fastboot
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
1 adb works only in os and recovery, fastboot works only in bootloader
2 it looks like your recovery is screwed up, flash this with fastboot
http://techerrata.com/file/twrp2/manta/openrecovery-twrp-2.6.3.1-manta.img
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
3try not to use toolkits, you have a nexus, toolkits are more complicated than manual methods and you won't learn anything from it
Once you have recovery
Wipe all, then you will will need to use adb sideload to flash ROM as you have no ROM on emulated sdcard
Go to advanced menu
adb sideload
adb sideload nameofROM.zip
adb sideload gapps.zip
For more info on fastboot
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The first part worked ok. The second part doesn't.
ADB sideload - I went there in the Nexus menu
adb sideload kitkat2501.zip
returns this:
* failed to write data 'protocol fault (no status)' *
If I do it without starting adb sideload on nexus, then it just says "error: closed", so it does recognize the change.
I downloaded the latest sdk tool, 64-bit, and the stock nexus 10 rom from 25th Janaury.

Let's do this, grab the latest stock for manta from here
https://developers.google.com/android/nexus/images
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
And extract and run the flashall.bat
This should bring you to the latest official software/firmware. Then with you up and running we can root and give you custom recovery,ROM,whatever
If you have an issues at all please copy and paste all input/output from cmd/terminal here
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
Let's do this, grab the latest stock for manta from here
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
And extract and run the flashall.bat
This should bring you to the latest official software/firmware. Then with you up and running we can root and give you custom recovery,ROM,whatever
If you have an issues at all please copy and paste all input/output from cmd/terminal here
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You are a wizard. I got it all ok now and I added CWM to it, it was easy to root it from there.