Database Users

I'm bricked .. Getting worries. (Yes I've read the forums ...)

Attempted to flash Liquid Jelly Bean, then got stuck on the animation boot screen. I've tried Root tool kit for unbricking and setting it back to stock. Tell me it's successful but stays stuck on the animation screen.
I've also tried to unbrick manually however even though I have the correct files placed in my Platform Tools folder of Android SDK ... I constantly get stuck at the CMD prompt steps. Any time I type in "ADB reboot loader" or ..."fastboot flash bootloader bootloader-grouper-3.34.img" or anything similar I get the error message in CMD saying "___ Is not recognized as an internal or external command"
I'm not sure what to do. The bootloader does say that my device is locked, I just can't get passed the splash screen!

Rovon said:
Attempted to flash Liquid Jelly Bean, then got stuck on the animation boot screen. I've tried Root tool kit for unbricking and setting it back to stock. Tell me it's successful but stays stuck on the animation screen.
I've also tried to unbrick manually however even though I have the correct files placed in my Platform Tools folder of Android SDK ... I constantly get stuck at the CMD prompt steps. Any time I type in "fastboot flash bootloader bootloader-grouper-3.34.img" or anything similar I get the error message in CMD saying "___ Is not recognized as an internal or external command"
I'm not sure what to do. The bootloader does say that my device is locked, I just can't get passed the splash screen!
Click to expand...
Click to collapse
Use Wugfresh's toolkit and press "return to stock"

rohan32 said:
Use Wugfresh's toolkit and press "return to stock"
Click to expand...
Click to collapse
"I've tried Root tool kit for unbricking and setting it back to stock. Tell me it's successful but stays stuck on the animation screen. "

Here's an update:
I think I've made it worse ...
Nothing will boot now and it's currently locked. Any time I hit "Start" it says "Booting Failed"
My CMD now says; Error: Cannot Load "Bootloader Grouper-3.34.img"
I'm seriously lost. I've been working on this for about 6 hours now ....

Can you get into bootloader and then recovery by holding the power and volume down buttons? Was ADB actually working before all of this??

markj338 said:
Can you get into bootloader and then recovery by holding the power and volume down buttons? Was ADB actually working before all of this??
Click to expand...
Click to collapse
Nope. Nothing is allowing me to get into recovery. At first it was just stuck on the google screen now it says "boot failed"

Rovon said:
Nope. Nothing is allowing me to get into recovery. At first it was just stuck on the google screen now it says "boot failed"
Click to expand...
Click to collapse
Where does it say boot failed? On the device?

markj338 said:
Where does it say boot failed? On the device?
Click to expand...
Click to collapse
Yes. Top left hand corner.

Rovon said:
Yes. Top left hand corner.
Click to expand...
Click to collapse
I know I have asked this before but I don't know if I was clear
You can't go to bootloader, and press the volume buttons to go to recovery?

markj338 said:
I know I have asked this before but I don't know if I was clear
You can't go to bootloader, and press the volume buttons to go to recovery?
Click to expand...
Click to collapse
No I can't get into the recovery at all. When I turn on the device I don't even need to use the rocker keys to get into bootloader either. Actually my bootloader is a bit different now too. I have the 'Google' logo and at the top the regular options for Start, Recovery, Power Off, etc.
In simple terms: I can't even get to the animated splash screen anymore

Open the command prompt IN the directly WITH fastboot
Fastboot oem unlock
Then wipe / flash factory images. Fastboot -w update image whatever the image name is.
Then uninstall / delete that stupid toolkit and never use them stupid craps again.

Are you still able to communicate with the device via fastboot? If you issue the command 'fastboot devices' does it return a serial number?
Edit: I'm going to bed so if you are able to use fastboot, download the factory image pack from https://dl.google.com/dl/android/aosp/nakasi-jro03d-factory-e102ba72.tgz
Extract the archive. Inside are there will be an install script, manually issue the commands contained in the script in fastboot. The only thing you need to add is the location of the .img and .zip files from the archive you extracted e.g. 'fastboot flash recovery c:/Users/name/desktop/recovery.IMG'
There is no reason this will not get you up and running again.
Sent from my Nexus 7 using xda app-developers app

Alkaloid said:
Are you still able to communicate with the device via fastboot? If you issue the command 'fastboot devices' does it return a serial number?
Edit: I'm going to bed so if you are able to use fastboot, download the factory image pack from https://dl.google.com/dl/android/aosp/nakasi-jro03d-factory-e102ba72.tgz
Extract the archive. Inside are there will be an install script, manually issue the commands contained in the script in fastboot. The only thing you need to add is the location of the .img and .zip files from the archive you extracted e.g. 'fastboot flash recovery c:/Users/name/desktop/recovery.IMG'
There is no reason this will not get you up and running again.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your response.
I've followed the instructions in the file. From previous research, I've had these files. My device does communicate with Fastboot. When I give the command for Devices it gives me my serial. Also, when I ask it to reboot-bootloader in CMD it does.
My issue is when I get to "Fastboot flash bootloader-grouper-3.34.img". CMD states "Error: Cannot load bootloader-grouper-3.34.img"
I've followed the commands previous to that. (Erase boot, cache, recovery, system, userdata)
Open the command prompt IN the directly WITH fastboot
Fastboot oem unlock
Then wipe / flash factory images. Fastboot -w update image whatever the image name is.
Then uninstall / delete that stupid toolkit and never use them stupid craps again.
Click to expand...
Click to collapse
Yes my device is unlocked again, but I still can't get into recovery mode. It just tells me "Recovery Failed" in small text in the upper left hand corner of my N7.

UPDATE:
After unlocking the device again. I used the Nexus Root Toolkit to restore to factory settings and it worked
The Problem: My device was no responding correctly to the toolkit when locked.
Cheers for the help. I'll attempt to root again, hopefully no problems this time If there are I'll be sure to post again!
Thanks to everyone that replied.

Rovon said:
UPDATE:
After unlocking the device again. I used the Nexus Root Toolkit to restore to factory settings and it worked
The Problem: My device was no responding correctly to the toolkit when locked.
Cheers for the help. I'll attempt to root again, hopefully no problems this time If there are I'll be sure to post again!
Thanks to everyone that replied.
Click to expand...
Click to collapse
For the love of God..stop using the toolkit from here on out.. learn how to use ADB and Fastboot so you can avoid these issues.
Sent from my Galaxy Nexus using Tapatalk 2

So you erased the recovery then wonder why you could not boot into recovery....
You flashed or tried to flash the bootloader. You already had the same bootloader installed and there was no need to do so to try and fix your issue.
You still don't know what you're doing and are back using the tool that lead you to this issues. A toolkit. Learn what you're doing and you wont face this type of silly issue again.

Rovon said:
UPDATE:
After unlocking the device again. I used the Nexus Root Toolkit to restore to factory settings and it worked
The Problem: My device was no responding correctly to the toolkit when locked.
Cheers for the help. I'll attempt to root again, hopefully no problems this time If there are I'll be sure to post again!
Thanks to everyone that replied.
Click to expand...
Click to collapse
I think you should reread this post and hit the thanks button of everyone who took the time to help you out of this mess - its good manners. Oh, and learn how to use adb & fastboot
Sent from my Nexus 7 using xda premium

Inaccessible boot loader :/
If you try to fastboot flash all you get nothing?
Sent from my Nexus 7 using xda app-developers app
---------
nvm you fixed it, good job
Don't use toolkits. Most people don't have a clue what the toolkit is actually doing so if something goes wrong they aren't in a good position

Its always nice to see threads like these where the N7 in the face of death but in the end with cutting edge medical technology it is brought back to life and healthy.

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

Need help flashing bootloader. Nothing works!

My wife's Nexus 7 is on the 4.13 bootloader. I've tried to change it before to no avail. I tried to use Wug's kit to flash the latest 4.4.2(coming from the 66Y build) but I got the error on the bootloader flash. So everything got wiped but the bootloader and left an empty device. All attempts to flash after that failed to get past the first line(erasing boot), I guess 'cause it was already erased? I flashed the individual img' s(boot, system, etc) and got the Nexus to boot up into kit Kat 4.4.2, but there is this little glitch in between the "google" splash screen and the boot animation where I can see recovery flash for a split second. I want to flash the proper bootloader and redo the process clean, but for the life of me I can't get the bootloader to take. I flash in Wug's, the same way I flashed the other img's, but fastboot screen still shows 4.13. Adb shows connected but says "offline" next to device, which is making the adb reboot command fail(unless I'm done now something else wrong there). Can anyone help? My wife is not pleased.
Sent from my SCH-I535 using Tapatalk

Your wife is displeased because of a momentary flash of the screen while booting? **
Or maybe she's displeased with the idea of you fooling with her tablet and that's the only straw to grasp at?
You need to say exactly what the error is, not "an error occurred". You can cut-n-paste right here into your posts.
Also, you should verify the checksum (e.g. MD5) of the bootloader image file you are attempting to flash to make sure you are really using a valid bootloader file.
(In particular, the one shipped in the KOT49H = 4.4.2 factory image is corrupted)
Note [WARNING][URGENT] N7 grouper (2012 WiFi) bootloader .img files from Google
Honestly, I would avoid flashing your bootloader unless it was absolutely, positively necessary. It's the riskiest flashing operation that you could possibly perform on your tablet. Unless I missed something, you didn't really indicate anything else was particularly wrong with the tablet.
good luck
** I think I saw a bug report about fleeting screen flashes in KitKat 4.4.2 (you see an "old" screen briefly appear when you are on your way to doing something else; they are quite noticeable because they are "out of sequence"). For instance I've seen my settings screen appear momentarily when I am moving between two running apps. I think I saw this reported as a KitKat bug - not something due to the bootloader.
.

Well, bootloader now says 4.23, but I still get the invalid state error when flashing the latest kit kat img. Is there a way to force request an OTA? The 4.4.2 OTA failed because I was on a custom rom/recovery, but now it seems to say I am up-to-date even if I downgrade. Is there a way to clear the memory or get the OTA to attempt?

How do you flash? Using a toolkit? Fastboot? ADB? On what operating system? What is the error message and at what step does occur?
It's a bit difficult to give suggestions how to solve a problem when one has only little information.
If you have a 4.23 bootloader installed, flashing boot.img and system.img is sufficient to get a running system, I.e.
Fastboot flash boot boot.img
Fastboot flash system system.img
While boot.img and system.img are extracted from the factory image, but without having detailed information ...
Sent from my Nexus 7 using xda app-developers app

I tried to update using Wug's NTK in fastboot. I got an "invalid state" error when it was flashing bootloader during 4.4.2 return to stock process, and that part fails. I've read this problem has to do with the current bootloader. So I flashed back to the V build and everything flashes fine in NTK. But I get the error again trying to flash stock and unroot to 4.4.2. So I flashed just the boot and system img files in NRK and it's running 4.4.2 now, but I can't flash it in Wug's the normal way. I've read others have solved this error but I haven't been able to.
Sent from my SCH-I535 using Tapatalk

jackdubl said:
I tried to update using Wug's NTK in fastboot. I got an "invalid state" error when it was flashing bootloader during 4.4.2 return to stock process, and that part fails. I've read this problem has to do with the current bootloader. So I flashed back to the V build and everything flashes fine in NTK. But I get the error again trying to flash stock and unroot to 4.4.2. So I flashed just the boot and system img files in NRK and it's running 4.4.2 now, but I can't flash it in Wug's the normal way. I've read others have solved this error but I haven't been able to.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
It may be that the file is corrupt, but it could also mean that your usb port is faulty. Try plugging it in on a different usb port.

First suggestion: try to avoid any toolkit
Second suggestion: get familiar with fastboot
Third suggestion: try to use a decent OS, i.e. Linux / OS X
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
First suggestion: try to avoid any toolkit
Second suggestion: get familiar with fastboot
Third suggestion: try to use a decent OS, i.e. Linux / OS X
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I thought I mentioned that I couldn't get adb to reboot into the bootloader because device said "offline" so I couldn't run in fastboot. The toolkit lets you flash in fastboot without using adb so that's how I flashed the system and boot. I'll just leave it the way it is. Seems to run fine and no slow charging issue.
Sent from my SCH-I535 using Tapatalk

Excuse me, but adb and fastboot are two completely different things ...
Btw. You can boot your device into bootloader (fastboot) mode by pressing vol-down + power while booting it.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
Excuse me, but adb and fastboot are two completely different things ...
Btw. You can boot your device into bootloader (fastboot) mode by pressing vol-down + power while booting it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I know that part. But how do you enter the commands after that?
Sent from my SCH-I535 using Tapatalk

[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

[Q] help please nexus 4 cant go back to stock

hello everyone
im pretty new to the forums but have always seeked help from here so i know this is probably the best place to get more help.
so my nexus four is a little messed up. i had an error regarding "com.android.systemui" so i tried to factory reset but it still popped up over and over. i then accidently wiped everythin off my phone including the OS.
so i used skipsoft toolkit do work on my phone so i tried to use it to help me but everytime i try to load google stock image from the options but i get an extraction error and keeps getting errors when extracting the .tar file.
and i cant seem to push files to my phone so i can install via recovery. so im all confused and i downloaded the stock firmware from google.
any advice would be great.
and im stuck on the google logo and i can get into recovery and fastboot mode and the lock state is unlocked.
thanks

You need to be able to boot into fastboot to flash a factory image. If your phone is rebooting in a loop hold vol down and power for about 10 seconds (until the phone shuts off) then let go of power, continue to hold vol down and it should boot in fastboot.
If that's successful then you can try flash a factory image, you'll need fastboot drivers working (I use koush universal driver) and fastboot.exe in the same directory as the factory image (or added to your cmd path). If everything's good you can click the flash-all.bat in the factory image to flash your phone back to stock.
The factory image comes a compressed tar, I've noticed when you download it the extension is wrong sometimes, make sure you have a .tgz file (rename if necessary) and winrar/7zip will extract it fine.
If you can't get into fastboot you need this guide http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060

Flash the factory image in fastboot. Google nexus 4 image for the image to flash.
Sent from my Nexus 5 using XDA Free mobile app

DrFredPhD said:
You need to be able to boot into fastboot to flash a factory image. If your phone is rebooting in a loop hold vol down and power for about 10 seconds (until the phone shuts off) then let go of power, continue to hold vol down and it should boot in fastboot.
If that's successful then you can try flash a factory image, you'll need fastboot drivers working (I use koush universal driver) and fastboot.exe in the same directory as the factory image (or added to your cmd path). If everything's good you can click the flash-all.bat in the factory image to flash your phone back to stock.
If you can't get into fastboot you need this guide http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Click to expand...
Click to collapse
hey thanks..so yes i can get into fast boot but im not too good cmd or anythin like that. so koush universal driver is that easy to use?

jd1639 said:
Flash the factory image in fastboot. Google nexus 4 image for the image to flash.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
ok silly question, how do i flash the image in fastboot ? sorry im still a noob haha

wink4lif said:
ok silly question, how do i flash the image in fastboot ? sorry im still a noob haha
Click to expand...
Click to collapse
Google 15 second adb install xda. That'll setup fastboot and install the drivers. After you download the factory image, extract it. In there you'll find a flash-all.bat. Boot into the bootloader, connect your device to the usb and simply double click the flash-all.bat. It'll wipe your device so back up first.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Google 15 second adb install xda. That'll setup fastboot and install the drivers. After you download the factory image, extract it. In there you'll find a flash-all.bat. Boot into the bootloader, connect your device to the usb and simply double click the flash-all.bat. It'll wipe your device so back up first.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
perfect thanks, once i manage to download it ill give it a shot. thanks