Database Users

Nexus 7 2012 (GSM) Booting Failed/No OS

i have access to ADB and fastboot mode.
i also try google factory image(see the attach picture for the result)

niceguy01 said:
i have access to ADB and fastboot mode.
i also try google factory image(see the attach picture for the result)
Click to expand...
Click to collapse
Yes, me too. I can't load anything except ADB & Fastboot. I used the Nexus 7 Toolkit to try to update to Kit Kat and now I have a soft bricked device. HELP!!!:crying:

Have you tried using adb shell command prompt to push the files to your device instead of a root toolkit?

cr0wnest said:
Have you tried using adb shell command prompt to push the files to your device instead of a root toolkit?
Click to expand...
Click to collapse
what file do i need to push in my device??

Effing toolkits again. When will they be banned for once and for all?
Oh that's right. They bring in ad revenue from lazy people.
Sent from my Nexus 5

niceguy01 said:
what file do i need to push in my device??
Click to expand...
Click to collapse
Check out this sticky here, it gives instructions on how to do it and what files are required. Its quite a lengthy guide, but its the safest method. http://forum.xda-developers.com/showthread.php?t=1907796

Pirateghost said:
Effing toolkits again. When will they be banned for once and for all?
Oh that's right. They bring in ad revenue from lazy people.
Sent from my Nexus 5
Click to expand...
Click to collapse
sorry im just a newbie:angel:

UPDATE: booting failed already gone by flashing cyanogen rom
the problem now is stuck in booting.see the attach picture
what is the meaning of
archive does not contain boot.sig
archive does not contain recovery.sig
archive does not contain system.sig

Got the same problem...I used RTK to flash 4.4 and ended up with a soft bricked N7.
Well initially I haven't been able to update any newer versions of CM. I was stuck on 10.2 nightly. I got a notification that there's an update so I downloaded it and tried installing. I get stuck when my N7 will go into recovery, I'll always get the droid with the red exclamation point and I have to stop the update. But I will always be able to do a system reboot and use the N7. After flashing using the RTK, all I can do is boot into the Bootloader mode. Choice at that point it Recovery, Reboot Recovert, Reboot Bootloader and Power Off. If I choose Recovery nothing happens. So the real choice is only to power off or reboot the bootloader.
I tried using fast boot but the guide I got was asking me to put the tablet in debugging mode (which I can't really do). And I get an error when doing the steps in CMD. I think I wasn't able to properly load the drivers because I am not seeing my device listed with serial number when I run >dab devices.
Kindda stuck and waiting where this thread will lead to as well so I can fix my N7.
Also, when I get the factory image (JWR66V) and run 7-zip on it, I don't see these files: bootloader-grouper-4.23.img, image-nakasi-jwr66y.zip, flash-all.sh, flash-base.sh. I only see 1 file.

As mentioned in about 5 billion threads, USB debugging has nothing to do outside of a booted OS.
Fix your drivers.
Unzip the factory image archive.
Sent from my Nexus 5

^Fixed my drivers (via SDK). PC recognised the device via fast boot devices. Ran a set of commands fast boot erase boot, cache, recovery, system, and user data. Flashed boot loader and reboot boot loader. Flashed 4.3 factory image (extracted via 7zip). Flashing/Update FAILED (I think the error was 'too mani links') and it went back to a blinking cursor.
@niceguy01 - just wait for CMD to process the entire thing. I was worried as well when I saw the system does not contain boot.sig etc error. Waited for it and started getting some scripts after. Wasn't able to complete the flash though but little steps getting there.

where should i flash radio.img?
boot,bootloader,recovery.system or userdata??see the picture
thanks

None of the above
Sent from my Nexus 5

Pirateghost said:
None of the above
Sent from my Nexus 5
Click to expand...
Click to collapse
thanks:good:

finally i got manage to fix my N7,thanks anyone who help me:good:
-----------thread close------------
i use google nexus toolkit v4 and install sdk drivers

[Q] How to recover from Nexus 10 stuck in fastboot mode!

My Nexus 10 was on Android 4.3 rooted and unlocked. Upgrade to 4.4 via OTA would not work.
I used WugFresh Nexus Rootkit 1.79, and was about to upgrade from Android 4.3 to 4.4, but first ran Flash Stock and unroot so I would be able to accept OTA updates. Unfortunately, the program halted when it completed the requested action, and I am left in fastboot. The tablet is stuck in fastboot mode, and no matter which option I try it always comes back to fastboot mode. Also I have tried to initiate custom recovery, via power and Volume up, but again to no avail.
USB debugging was active, and I had CWM recovery and root.
When I go to 'Restart Bootloader', (or 'Recovery Mode' or 'Start') the tablet immediately reboots back to 'Start'. Thankfully the 'Power Off' button does actually stop the tablet.
I have tried to see if I could get to Stock Recovery from fastboot, but that gives no response beyond going to the next tab.
Is anyone able to provide assistance in recovering from this dilemma?

First make sure bootloader is unlocked, if not
fastboot oem unlock
Then fastboot wipe
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now grab latest twrp or clockwork image
fastboot flash recovery nameofrecovery.img
Then boot to new recovery
For fun format all partitions available to in there
Now go to advanced, adb sideload
adb sideload romofchoice.zip
Then probably need gapps
adb sideload gapps.zip
Now reboot
This will get you up and running, if you absolutely want stock and non rooted let me know and I'll help you get there, but I will advise not to bother with toolkits as most every "help me fix xxxxxx" is from a toolkit user
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
First make sure bootloader is unlocked, if not
fastboot oem unlock
Then fastboot wipe
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now grab latest twrp or clockwork image
fastboot flash recovery nameofrecovery.img
Then boot to new recovery
For fun format all partitions available to in there
Now go to advanced, adb sideload
adb sideload romofchoice.zip
Then probably need gapps
adb sideload gapps.zip
Now reboot
This will get you up and running, if you absolutely want stock and non rooted let me know and I'll help you get there, but I will advise not to bother with toolkits as most every "help me fix xxxxxx" is from a toolkit user
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Many thanks for your response demkantor.
Although I tried to clearly describe the status of the tablet and the problem, I did not intend that I should come across as one who is familiar with the complexities of programming of either the tablet, or rooting around in the registry of a PC.
I can however follow clear instructions.
Your message appears to give a list of what to do, and presumably in the tablet from within fastboot. But I am lost after that.
By the way, the bootloader is unlocked.
Since the fastboot is currently inoperable, how do I initiate fastboot wipe, and then the following 3 commands 'erase system-w, boot & recovery'?
If you can spare the time and expand on your listing, I would certainly appreciate it.

http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 4 using XDA Premium 4 mobile app

Wow demkantor many thanks! The link you provided will take a bit of reading after I get back from the gym. A full afternoon ahead I suspect! I'll let you know how I go.

Just let me know if you get stuck
Sent from my Nexus 4 using XDA Premium 4 mobile app

Hi demkantor,
All done and dusted. Many thanks for your help, My tablet is now running on KitKat 4.4.2.
Your contributions to XDA University are very well arranged and written, and logically guide us through the maze. I for one did not know XDA University existed, and it is a shame that you as the person who pulled your contributions together have to also point us to it!
Many thanks for your efforts!
Edit - I read somewhere that the [Q] at the start of the thread should be changed to something else when the problem is resolved. It certainly is! Can the moderator correct this for me please?

Demkantor, I think I may have screwed up big time. I am unlocked and rooted, running stock 4.4. I woke up yesterday and had a notification that a system update had been downloaded. I did a temporary unroot and took the update. Which failed. I went into twrp and wiped everything. Still no go.Then, like a dummy I rebooted after it gave me a warning about not having an os installed. It wont do anything now except go into bootloader. I must have wiped twrp, because it wont boot into that or stock recovery. When I plug it up to my computer,I get this message( fastboot status-failInvalid command). I've just about every option in wugs toolkit. I keep getting adb and fastbooterrors. Have I completely hardbricked my nexus 10? I would appreciate it if you could point me in the right direction or let me know if I'm just wasting my time. I've been messing with this thing since around midnight and I'm about ready to start pullnig hair out of my head. Thanks in advance my friend.

@63t061
Thanks for the kind words, ive been busy lately (finals and all) so normally i would helped more personally but im glad you were able to get it all working on your own through research, which is the best way as im sure you have learned much and will be able to share with the next! Great job! As for editing the thread title, just edit it in your first post @moejoe88
Can you post all input output from cmd/terminal as its easier to see the issue. And try not use tool kits
Start with
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery.img
Sent from my SGH-T699 using XDA Premium 4 mobile app

Thanks for replying so quickly. I've had to walk away from it for a little while and get some sleep. I'll get some rest and make a fresh start of it. Again, thanks for the quick reply.

I've tried running terminal and the computer wont even recognize the tablet. I believe the battery is drained because I can get it to the bootloader, but it shuts back off after a few minutes. I'm trying to charge for a while and I'll give it another shot. Thanks again.

[Q] Tried Rooting Nexus 4 following the guide, but now it's not working

I followed the guide from this forum on how to root a Nexus 4, but in the process I think I've broken my phone.
I first tried flashing AOKP and it's GApps, the phone booted fine, and I was able to get to the wifi set up screen, however, I couldn't get wifi to turn on.
So I tried to flash Paranoid Android and it's GApps. But now the phone won't get past the boot screen that comes after the google logo.
I've asked around and Googled around for a solution, but I can't find anything. I've been trying to get this fixed since yesterday.
Can anyone please help me? I just want to be able to use my phone again.

GuyWithBrokenPhone said:
I followed the guide from this forum on how to root a Nexus 4, but in the process I think I've broken my phone.
I first tried flashing AOKP and it's GApps, the phone booted fine, and I was able to get to the wifi set up screen, however, I couldn't get wifi to turn on.
So I tried to flash Paranoid Android and it's GApps. But now the phone won't get past the boot screen that comes after the google logo.
I've asked around and Googled around for a solution, but I can't find anything. I've been trying to get this fixed since yesterday.
Can anyone please help me? I just want to be able to use my phone again.
Click to expand...
Click to collapse
How are you flashing? Adb or a Toolkit?
Edit:: How long did you wait? Sometimes it might take awhile, especially with PA.
Sent from my Nexus 7 (2013)

Berrydroidcafe said:
How are you flashing? Adb or a Toolkit?
Edit:: How long did you wait? Sometimes it might take awhile, especially with PA.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
I flashed with ClockworkMod.
I left it on from 12AM to 6AM.

GuyWithBrokenPhone said:
I flashed with ClockworkMod.
I left it on from 12AM to 6AM.
Click to expand...
Click to collapse
It definitely shouldn't have taken that long. Can you boot into the recovery?
Sent from my Nexus 7 (2013)

Just put your phone in fastboot mode and flash factory image.

Okay now I have a new problem. I turned the phone off, booted back on and tried entering recovery mode, but now I have an image of an android with a red ! mark.
I was just about to try flashing an older version of the stock.

That's normal for stock recovery, you won't be able to sort your phone from there, stay in fastboot mode. You can use a toolkit to flash back to stock from there if you need it more noob friendly. Otherwise you can use the flash-all.bat script in the factory images.

GuyWithBrokenPhone said:
Okay now I have a new problem. I turned the phone off, booted back on and tried entering recovery mode, but now I have an image of an android with a red ! mark.
I was just about to try flashing an older version of the stock.
Click to expand...
Click to collapse
You mean the android is on it's back, press the volu+ button, press power, and that will take you into the stock recovery.

audit13 said:
You mean the android is on it's back, press the volu+ button, press power, and that will take you into the stock recovery.
Click to expand...
Click to collapse
Oh god thank you.
Okay. I'm trying to reinstall Paranoid Android now. I did the sideboot via ADB.
I couldn't seem to get the stock version of android on it though. I made sure to open the tar file and tried to move the .zip "image-occam-jdq39.zip" onto the phone, but it wouldn't accept it. So I'm trying Paranoid android again.
Edit: I got it booted. But now wifi won't work. Neither the speakers.

It didn't work because that's not how you flash a factory image. You need to be in fastboot mode and flash it from a PC using fastboot program. You used fastboot when you unlocked your bootloaders in the first place. You have stock recovery so you can't flash a custom rom, which is why your adb sideload of PA didn't work.
Like I said before you can use the flash-all.bat in the factory image. It runs the following commands which you can also use manually.
fastboot flash bootloader [path-to-bootloader.img]
fastboot flash radio [path-to-radio.img]
fastboot -w update [path-to-system-image.zip]
If that's too difficult use a nexus 4 toolkit to download and flash a factory image automatically. With your phone in fastboot mode, not recovery.
The above will fix your phone, trying to flash custom roms and system image zip in recovery mode will not.

DrFredPhD said:
It didn't work because that's not how you flash a factory image. You need to be in fastboot mode and flash it from a PC using fastboot program. You used fastboot when you unlocked your bootloaders in the first place. You have stock recovery so you can't flash a custom rom, which is why your adb sideload of PA didn't work.
Like I said before you can use the flash-all.bat in the factory image. It runs the following commands which you can also use manually.
fastboot flash bootloader [path-to-bootloader.img]
fastboot flash radio [path-to-radio.img]
fastboot -w update [path-to-system-image.zip]
If that's too difficult use a nexus 4 toolkit to download and flash a factory image automatically. With your phone in fastboot mode, not recovery.
The above will fix your phone, trying to flash custom roms and system image zip in recovery mode will not.
Click to expand...
Click to collapse
Doing so now. If I had known about this tool before, I probably would have been done with this a lot sooner.
Currently flashing stock and unrooting.

The toolkit is most certainly the way to go. No mess, perfect every time for me.
Sent from my Nexus 4 using Tapatalk

[Q] Wugfresh stucks on: send bootloader(1280kb)

Well, i tried to install stock Bootloader, stock recovery and stockrom with wugfresh tool under "Back to Stock", and so thats the problem:
When i try to send the bootloader, it stucks and the tablet posts under the infos on the bootloader screen: FASTBOOT STATUS - DATA00140000.
And thats it. I waited 2 hour, it still stucks on sending bootloader. So i downloaded the Unified Android Toolkit, install the fastboot driver and tick the option to install a new recovery... It still stucks on sending bootloader. In Youtube Videos, i saw, that the sending finished about 0,2 s. Thats 1280kb! Why doesnt work it on my tablet. I had root, but i didnt tick the usb debugging. So when i switch on my tablet, it comes to the bootloader, and its the activated bootloader( i can switch to recovery, reboot bootloader, power off, reboot system,..) and its unlocked. If i reboot into the recovery, it also comes to the activated bootloader. Its also when i tick the reboot system. So what can i do? Is it hardware bricked? Or whats the problem? I have the bootloader version MANTAMF01 and the H/W Version 8. Can anyone helps me?
And yes, i am the Admin on my PC

The problem is the toolkit, just use fastboot
fastboot flash bootloader nameofbootloader.img
And your done
But after doing so you effectively wipe a few of your partitions so then flash recovery and ROM as well, the method on doing so slightly varies depending if your going back to stock or what something custom
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
The problem is the toolkit, just use fastboot
fastboot flash bootloader nameofbootloader.img
And your done
But after doing so you effectively wipe a few of your partitions so then flash recovery and ROM as well, the method on doing so slightly varies depending if your going back to stock or what something custom
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am having the same exact problem, and I tried doing as you said with fastboot, but I still can't receive any files. Any other suggestions? Any help would be greatly appreciated.

funkym0nkee said:
I am having the same exact problem, and I tried doing as you said with fastboot, but I still can't receive any files. Any other suggestions? Any help would be greatly appreciated.
Click to expand...
Click to collapse
Are you trying to return to stock? Download the appropriate factory image (just Google android factory image) extract all and flash with fastboot.
If you want more detailed explanation boot to bootloader and write down all info on that screen, pet me know the os of your PC, and the explain a little more what's wrong, I'm not sure what can't receive any files means. It is often helpful to copy and paste all input/output from cmd/terminal
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Are you trying to return to stock? Download the appropriate factory image (just Google android factory image) extract all and flash with fastboot.
If you want more detailed explanation boot to bootloader and write down all info on that screen, pet me know the os of your PC, and the explain a little more what's wrong, I'm not sure what can't receive any files means. It is often helpful to copy and paste all input/output from cmd/terminal
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just resolved this issue on my own about a minute before your response lol. The problem was that I wasn't using the stock USB cord. Holy cheese and rice, I've been sitting here for the past 5 hours at wits end trying to figure out the problem. My problem was exactly like MrCreeper's, it was just stuck on "sending 'bootloader'" with no progress whatsoever on either PC or tablet. Who woulda thunk the problem was simply that I was using the incorrect USB cord -_- *sigh*
Anyway, thank you for your prompt reply. I did use a few of your tips from your other posts when I ran into other problems trying to flash stock image, so cheers for that!

[Q] Nexus 7 stuck at the google logo

Hello,
I've got a problem. On monday my Nexus 7 2012 (with lastest stock Android) froze and I had to reboot it. But then it got in a bootloop where it would boot to the boot-animation (the four moving dots) and then restart after half a minute. Then I went into the bootloader to switch it off. When I switched in back on it just got stuck at the google logo.
I tried to reflash the stock rom, but I haven't unlocked the bootloader yet and everytime I try to do unlock it, it fails with "unknown error code".
At first I used Wug's Toolkit. When that didn't work I used cmd, but that doesn't work either.
I would really appreciate some ideas to solve that

You dont have to unlock the bootloader to flash factory images.
You can flash it with fastboot or a toolkit.

Did you try to get into recovery?
Maybe you can wipe some thing like cache, dalvik cache and system,
And then install the firmware again.
I once installed a firmware without properly wiping and also got stuck in thjis animation logo.
After wiping in recovery and re-flashing the firmware it worked again.

Erovia said:
You dont have to unlock the bootloader to flash factory images.
You can flash it with fastboot or a toolkit.
Click to expand...
Click to collapse
As far as I know, you need to unlock the bootloader. Anyway, I tried a toolkit as well as fastboot via cmd but none worked.
See here: http://forum.xda-developers.com/showthread.php?t=1907796
In order to do anything useful in fastboot, the bootloader must be unlocked
Click to expand...
Click to collapse
Amlan90 said:
Did you try to get into recovery?
Maybe you can wipe some thing like cache, dalvik cache and system,
And then install the firmware again.
I once installed a firmware without properly wiping and also got stuck in thjis animation logo.
After wiping in recovery and re-flashing the firmware it worked again.
Click to expand...
Click to collapse
I dont't have any custom recovery installed. When I am trying to access the stock recovery mode via the bootloader then I get to the Google logo and "booting failed" is written in the upper left corner.
My guess is that the emmc is broken

Google search android factory images, download the appropriate one for your device
Then extract contents and double click the flashall.bat
If this fails then chances are your emmc has been severely corrupted, I've seen a few get to that point with the booting failed and its 50/50 if they resurrect their device
Best of luck
(Oh and don't use toolkits)
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
Google search android factory images, download the appropriate one for your device
Then extract contents and double click the flashall.bat
If this fails then chances are your emmc has been severely corrupted, I've seen a few get to that point with the booting failed and its 50/50 if they resurrect their device
Best of luck
(Oh and don't use toolkits)
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried that again the way you described it and sadly it didn't work. I have to accept that the emmc is corupted.
Thanks guys for your help anyway