Database Users

Boot Loop To Google Logo

My son brought me his Nexus S 4g and told me that it doesn't work anymore. He says that he didn't do anything and that it just started doing this on its own. Any help would be greatly appreciated.
When powered on, it quickly goes to the screen with the Google icon and a lock icon. It sits here for about 30 seconds, then reboots to the same thing. If I pull the battery and hold Vol Up and Power when inserting the battery I can get into Fastboot, but when I select Recovery or Reboot, I get the same Google screen.
When I gave him the phone, it was rooted with CWM recovery loaded and a ICS ROM running.
Any help would be greatly appreciated as I have been reading through threads all night long without finding much.

Sounds to me like you need to begin the rooting process again at the "fastboot oem unlock" part. Since you probably don't have anything on your SD card, you might have to push a new recovery via fastboot as well.
Look to this thread:
http://forum.xda-developers.com/showthread.php?t=1078213
for inspiration.
Once you get into the recovery loaded via fastboot, you can get whatever rom that you want onto the SD card by navigating to:
Mounts and Storage > Mount USB Storage
and leave it on that screen while you load the rom onto the SD card.
After that flash the new rom via CWM as normal.

Thanks for the reply. Since I was already unlocked, I followed the steps to return the phone to stock, including flashing boot, system, userdata, recovery and erasing cache. Now when I reboot, it just loops to the Google screen and reboots after 30 seconds. The only difference is that I don't see the lock icon at the bottom or the Google screen.
When I select Recovery, it just goes into the same Google loop. I am going to try to go through the root steps and see what happens. :-(

I was able to unlock the phone, but it will not boot into Recovery. I can get to Fastboot, but I am back to where I started.
When I gave the phone to my son, I had installed SetCPU and configured a profile to throttle the processor down when the screen was off to conserve battery. I am now wondering if he tried to overclock the processor and clicked "set at boot".
Any more suggestions? (please)

Did you successfully flash a recovery.img? Immediately after this you should hit Recovery, then mount the storage, copy a ROM over, do a Full Wipe and flash the ROM.
If all goes well, you'll boot fine. If not, it may be a hardware problem. Try to wipe most of it and lock the bootloader if you need to send it to samsung.

It looks like I successfully flashed a recovery image. I have tried version 5.x and version 3.x. Below is the result of the 5.x command. However when I select Recovery from Fastboot, I go to the Google screen loop.
C:\Program Files\Android\android-sdk\tools>fastboot flash recovery recovery-cloc
kwork-5.0.2.0-crespo4g.img
sending 'recovery' (4136 KB)... OKAY
writing 'recovery'... OKAY
C:\Program Files\Android\android-sdk\tools>

OK, go to http://wonderly.com/bb/CRESPO4G/OEM/GRJ22IMAGES.zip
That will download the GRJ22 stock images of your phone. Unzip them in your PC. Next, use fastboot like this.
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
After it finishes you can reboot your phone with "fastboot reboot". This will installed Stock GB 2.3.4 for NS4G. Setup your phone and you will get OTA to 2.3.5. After that you will get OTA again to 2.3.7. Good luck.
By the way, you must let it OTA all the way up to 2.3.7 to get the latest Radio and bootloader version.

Giving it a shot now. I'll let you know shortly how it goes.
Update: Same result. All commands completed successfully, but I end up in the Google logo boot loop. Is there a kernel .img file that I should flash, in case my son tried to flash an unsupported kernel?
C:\Program Files\Android\android-sdk\tools>fastboot flash bootloader bootloader
img
sending 'bootloader' (1536 KB)... OKAY
writing 'bootloader'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot reboot-bootloader
rebooting into bootloader... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot flash radio radio.img
sending 'radio' (15232 KB)... OKAY
writing 'radio'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot reboot-bootloader
rebooting into bootloader... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot flash system system.img
sending 'system' (174451 KB)... OKAY
writing 'system'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot flash userdata userdata.img
sending 'userdata' (18796 KB)... OKAY
writing 'userdata'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot flash boot boot.img
sending 'boot' (2904 KB)... OKAY
writing 'boot'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot flash recovery recovery.img
sending 'recovery' (3144 KB)... OKAY
writing 'recovery'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot erase cache
erasing 'cache'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot reboot
rebooting...
C:\Program Files\Android\android-sdk\tools>

That included stock kernel.
Man you might just want to fastboot oem lock and send the phone. Those were factory images... if they don't work it means hw issues.
Sent from my Nexus S 4G using XDA

rasengan82 said:
That included stock kernel.
Man you might just want to fastboot oem lock and send the phone. Those were factory images... if they don't work it means hw issues.
Sent from my Nexus S 4G using XDA
Click to expand...
Click to collapse
I agree. If this does not work, send the phone back to Sprint.

I really appreciate y'all trying to help. I will see if Sprint will be kind enough to exchange it. Thanks again.

Factory Restore - Archive does not contain... Help.

Hey guys. My brother got himself a Nexus 7 which is his first Android, and he was playing with some tweaks or mods or something and tried flashing via recovery and has messed something up. I have tried using the Toolkits as well as doing it manually with fastboot. I am able to flash a recovery and use that, but lose it after boot (the permanent option doesn't seem to stick). But, when I try to do a factory restore with the google image, it doesnt matter if i'm doig it manual or with the toolkit, the all respond with a "archive does not contain... " boot.sig, recovery.sig, or system.sig. Here is my output:
C:\Google Nexus 7 ToolKit>fastboot-toolkit.exe -w update "C:\Users\monkey\nakasi-
jro03d\image-nakasi-jro03d.zip"
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
getvar:version-bootloader FAILED (command write failed (Unknown error))
finished. total time: 0.836s
Even if I do them manually, one at a time:
C:\Google Nexus 7 ToolKit>fastboot-toolkit.exe flash boot nakasi-jro03d\image-na
kasi-jro03d\boot.img
sending 'boot' (4890 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.858s
I have also tried pushing a stock rom .zip to the /sdcard and it doesnt seem to make it either.
Feels like internal memory is corrupt. Any thoughts or ideas I can try? Also... should any custom recovery allow adb access? TWRP or CWM Touch don't seem to work.

Update... Just rebooted into bootloader and tried:
C:\Google Nexus 7 ToolKit>fastboot-toolkit.exe -w update "C:\Users\monkey\nakasi-jro03d-factory-e102ba72\nakasi-
jro03d\image-nakasi-jro03d.zip"
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 3.34
Baseband Version.....: N/A
Serial Number........: 015d256898080e19
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4890 KB)...
OKAY [ 0.608s]
writing 'boot'...
OKAY [ 0.390s]
sending 'recovery' (5234 KB)...
OKAY [ 0.655s]
writing 'recovery'...
OKAY [ 0.343s]
sending 'system' (438656 KB)...
FAILED (unknown status code)
finished. total time: 3.292s
That's the most progress I can get. System seems to fail though. Tried multiple times.

Another note... If I boot into Recovery and adb push a file to the /sdcard, the transfer looks like it completes, but when I go to flash zip in recovery it gives me an E: Can't mount /sdcard/. Same thing if I go to the mounts and storage option and try to mount /sdcard.
Any ideas guys? Never seen this before.

Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc.

Mr. Monkey said:
Update... Just rebooted into bootloader and tried:
C:\Google Nexus 7 ToolKit>fastboot-toolkit.exe -w update "C:\Users\monkey\nakasi-jro03d-factory-e102ba72\nakasi-
jro03d\image-nakasi-jro03d.zip"
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 3.34
Baseband Version.....: N/A
Serial Number........: 015d256898080e19
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4890 KB)...
OKAY [ 0.608s]
writing 'boot'...
OKAY [ 0.390s]
sending 'recovery' (5234 KB)...
OKAY [ 0.655s]
writing 'recovery'...
OKAY [ 0.343s]
sending 'system' (438656 KB)...
FAILED (unknown status code)
finished. total time: 3.292s
That's the most progress I can get. System seems to fail though. Tried multiple times.
Click to expand...
Click to collapse
The "archive does not contain *.sig" messages are normal. The FAILED messages on sending the system image is disconcerting. Use the platform tools from Google which includes fastboot. http://dl-ssl.google.com/android/repository/platform-tools_r16-windows.zip
There is a .bat file in the factory image archive that you can run to return to stock. If you don't want to run that, at least open it up and manually run the commands in sequence.

comminus said:
The "archive does not contain *.sig" messages are normal. The FAILED messages on sending the system image is disconcerting. Use the platform tools from Google which includes fastboot. http://dl-ssl.google.com/android/repository/platform-tools_r16-windows.zip
There is a .bat file in the factory image archive that you can run to return to stock. If you don't want to run that, at least open it up and manually run the commands in sequence.
Click to expand...
Click to collapse
I think that's the same thing I've been trying. I did download Google's platform-tools and try with that and still got the same error. Seems like I can't write to /system. Can't even erase it:
c:\android\platform-tools>fastboot.exe flash system C:\android\nakasi-jro03d\ima
ge-nakasi-jro03d\system.img
sending 'system' (438656 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.094s
c:\android\platform-tools>fastboot.exe erase system
erasing 'system'...
FAILED (command write failed (Unknown error))
finished. total time: 0.733s
c:\android\platform-tools>fastboot.exe format system
formatting 'system' partition...
FAILED (command write failed (Unknown error))
FAILED (command write failed (Unknown error))
finished. total time: 0.889s
What are my options? Flash stock recovery, re-lock bootloader and send it in for an RMA? Anyone else know what to try?

Mr. Monkey said:
I think that's the same thing I've been trying. I did download Google's platform-tools and try with that and still got the same error. Seems like I can't write to /system. Can't even erase it:
c:\android\platform-tools>fastboot.exe flash system C:\android\nakasi-jro03d\ima
ge-nakasi-jro03d\system.img
sending 'system' (438656 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.094s
c:\android\platform-tools>fastboot.exe erase system
erasing 'system'...
FAILED (command write failed (Unknown error))
finished. total time: 0.733s
c:\android\platform-tools>fastboot.exe format system
formatting 'system' partition...
FAILED (command write failed (Unknown error))
FAILED (command write failed (Unknown error))
finished. total time: 0.889s
What are my options? Flash stock recovery, re-lock bootloader and send it in for an RMA? Anyone else know what to try?
Click to expand...
Click to collapse
Two more thoughts - 1. try updating drivers. 2. verify the sha1 hash of the factory image

Did you try switching to a different usb port? Just a thought is all.

Wow. Can't thank you guys enough. Thought this was toast. I ended up trying all of the above, haha. Even though I had done it several times. I tried multiple computers, multiple factory images, multiple programs, multiple USB ports. But somehow, maybe your encouragement, something helped. I'll watch it and make sure nothing seems fishy, because I don't know how in the world that worked.... but it did. Thank you very much.

manasgirdhar said:
Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc.
Click to expand...
Click to collapse
Hi there
I was having the same problem but when I try to flash the system.img (or the 'image-nasaki-jop40d.zip file too for that matter) I get the following error:
"error: cannot load 'system.img': Not enough space
I have done ALL the steps found in this guide without any issues until I get to that part
Help please my wife just gave me this N7 for christmas and I can't believe I may have just bricked it!!

My solution
I understand this is an old thread but I came across it when I was having the same issues earlier today.
Oddly, using the USB cable that came with the N7 seemed to fix the multiple "FAILED" I was getting.
Using my Samsung USB cable seemed to cause the issues.
Hope this can be a solution to others that may come by this thread by googling the issue.

manasgirdhar said:
Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc.
Click to expand...
Click to collapse
This one helped me!:good::good::good:
Thanks a lot.

manasgirdhar said:
Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc.
Click to expand...
Click to collapse
Works, thanks. :good:

Unlock bootloader
Mr. Monkey said:
Hey guys. My brother got himself a Nexus 7 which is his first Android, and he was playing with some tweaks or mods or something and tried flashing via recovery and has messed something up. I have tried using the Toolkits as well as doing it manually with fastboot. I am able to flash a recovery and use that, but lose it after boot (the permanent option doesn't seem to stick). But, when I try to do a factory restore with the google image, it doesnt matter if i'm doig it manual or with the toolkit, the all respond with a "archive does not contain... " boot.sig, recovery.sig, or system.sig. Here is my output:
C:\Google Nexus 7 ToolKit>fastboot-toolkit.exe -w update "C:\Users\monkey\nakasi-
jro03d\image-nakasi-jro03d.zip"
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
getvar:version-bootloader FAILED (command write failed (Unknown error))
finished. total time: 0.836s
Even if I do them manually, one at a time:
C:\Google Nexus 7 ToolKit>fastboot-toolkit.exe flash boot nakasi-jro03d\image-na
kasi-jro03d\boot.img
sending 'boot' (4890 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.858s
I have also tried pushing a stock rom .zip to the /sdcard and it doesnt seem to make it either.
Feels like internal memory is corrupt. Any thoughts or ideas I can try? Also... should any custom recovery allow adb access? TWRP or CWM Touch don't seem to work.
Click to expand...
Click to collapse
You need the bootloader to be unlock. First run the command " fastboot oem unlock " . It works flawlessly after that! Awesome!

nexus 7 (mobile)
shap4th said:
You need the bootloader to be unlock. First run the command " fastboot oem unlock " . It works flawlessly after that! Awesome!
Click to expand...
Click to collapse
Hi!
I bought a second hand nexus 7 rooted. I had a problem with updating os via wifi because it doesn't update. some kind a problem. I tried to do a hard reset hoping I could just restore the device manually but I messed up so I am now stuck with just a google logo and can only access bootloader with start, bootloader, restore and power off option. I don't know what to do. please help me. I am not a tech person but if you can give me a specific instructions, I know i can manage. i saw a lot off post here that they were able to restore their device so I have faith in this site and the members are highly recommended.
thank you in advance

manasgirdhar said:
Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc.
Click to expand...
Click to collapse
Thanks man! This works for me..

manasgirdhar said:
Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc.
Click to expand...
Click to collapse
Thanks. This one works for my friend.
Same case, solved on spanish forum.
/showthread.php?t=748207 on htcmania(dot)com
*Note: damn spam filter

Try this website. If you have any question ask me.
You will need to install files one by one.
SImply open flash bat file see what they are doing. and do same but one by one.
Flash bootloader and radio (radio does not appear on all devices, if it's not in your tgz, you don't need it)
fastboot flash bootloader <bootloader file name here>.img
fastboot flash radio <radio file name here>.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
NEXUS 9 ONLY - flash this as well
fastboot flash vendor vendor.img
If you want to wipe cache and user data (full wipe), flash these
fastboot flash cache cache.img
fastboot flash userdata userdata.img
Finally, just reboot your device, and Android should start up.
fastboot reboot

Similar issue, please help
I'm using ubuntu 14.10 LTS. I had the same issue arise so i listened reextracted (even though boot.img, system.img & recovery.img were within .zip but im still getting "critical error: extent_create_backing: calloc: Cannot allocate memory
Mmap:invalid argument
Cannot generate image
FAILED()"
Anyone has a suggestion?
---------- Post added at 11:49 PM ---------- Previous post was at 11:18 PM ----------
So as my previous and maybe above msg said i was just about to attempt adb sideload to manually update to lollipop... From the bootloader i entered recovery... My nexus 4 shut down & got stuck @ wild new boot animation for lollipop. I waited 5 minutes while the fantastic yellow, red, blue & green orbs whizzed around, shut my 4 down & now "Android is upgrading... Optimizing app x of 68." How wild is this... But i still have to lock bootloader. Hopefully it doesnt screw anything up... I'll report back asap
---------- Post added 24th November 2014 at 12:19 AM ---------- Previous post was 23rd November 2014 at 11:49 PM ----------
So I relocked bootloader... Sent several test sms & so far so good. Wifi of course works, haven't tested bluetooth but ill report back. Boy I got lucky. No more linux for me... Jk

Everything You may need to install android 5.0.1
I'm writing this so that you all will not have to go through what I just experienced when trying to flash the android 5.0.1 OTA manual update. Here are some of the errors I've gotten out of and I will give you some tips to get fix these. I always seem to encounter issues that no one else has when flashing, so here we go.
Tip 1
1.)If you are trying to flash 5.0.1 (tip applies to any version) from the google website here: https://developers.google.com/android/nexus/images ....Make sure your computer can handle ".tgz" files. This took me a day and a half to figure out. If you try to download one of the files off this website without the proper software to do so you will simply get a ".tgz" file that you cannot extract the necessary files from.
*The solution is to download winrar from http://www.win-rar.com/predownload.html?&L=0 this website. Once you do and run it the ".tgz" file will become a folder (icon should look like stacked books) and you can proceed to actually follow the instructions on the page where you downloaded the file from. I learned this the hard way.
Tip 2
If you dont really understand how to us the "ADB" tools or "SDK" and everything related sounds like a foreign language to you then watch this video: http://highonandroid.com/android-ro...r-android-in-a-bootloop-with-no-os-using-adb/. It will explain how to copy files to your device while in bootloop. Pay special attention to the part about making sure your drivers are set up correctly. Drivers always get me when I installs. This knowledge will transfer over to downloading any rom or factory image in the future.
Links for Moving files to your device while in recovery:
Here are the appropriate drivers for copying files while in recovery to the nexus 5:
http://downloadandroidrom.com/file/drivers/Android/usb_driver.zip
Here is the fastboot link: http://downloadandroidrom.com/file/tools/fastboot.zip
Tip 3
The way I installed android 5.0.1 was:
1.)I downloaded the file from the google developer website that i pasted at the top
2.)I moved that file to a folder named "root" that i created on my desktop
*In this folder i have chainfire auto root http://autoroot.chainfire.eu/ in case i need to re-root my phone, I have the adb and fastboot.zip folders in my root folder as well.
3.)I moved the folder inside the FASTBOOT folder and extracted the file that i got from the developer website here. Once this is down there is another
3.)I extract the files here. After you extract there should be another folder called "image-hammerhead-lrx22c.zip." I copied those files to the fastboot folder as well so that they are outside of the zip file. I did not remove the zip file once I copied the insides to the outside. Right or wrong this is what I did.
4.)I used the Command prompt to navigate to this directory. Watch the how to copy files video to see how to navigate using the "cd" command
*basically i typed "cd desktop" which means change directory to the desktop. Then i did "cd root"....then "cd fastboot" ...YOUR PATH MAY BE DIFFERENT.
5.)Once i was here i could follow more of the instructions on the developer website. I could run that "flash-all.bat" command to begin flashing the 5.0.1. In order to run this command you literally type "flash-all.bat."
6.)After it finished it said,
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
helpful links: http://forum.xda-developers.com/showthread.php?t=1992063
This was okay, what you dont want is falures. While 5.0.1 is being installed, if you notice it say failure in the place where everything else is saying "OKAY" you have a problem. One guy on that xda link said:
"Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img"
You can type this into cmd and do each one by one and it may work.
7.)YOU MUST MAKE SURE TO EXTRACT THAT SECOND FOLDER inside the developer file! If you don't you will get failures because the program is looking for them. That's why manually installing them may work as well.
8.)IF YOU SEE THE ANDROID WITH NO LOADING BAR UNDERNEATH this does not mean that you are bricked. I thought it did and kept flashing 5.0.1 over and over and over again. Then i just waited a bit and my phone rebooted and i say the glorious dots rotating on my screen. I lived happily ever after.
9.)Once you are finished installing 5.0.1 you will loose root. Run that chainfire auto root program.You have to boot in to the bootloader screen...NOT RECOVERY...just the screen where you see the android and you can select "start" "recovery" etc. and open up that chainfire program and hit a key to start it. There are instructions on the actual program if you need help. If you are on the bootloader screen that i am talking about and you start the program it will "auto root" that is, automatically root your phone and thats that.
10.)Download root checker off the play store to see if you are actually rooted and have a blessed day. https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
Let me know if you need further explanation. I'm no pro but I've failed in soooo many ways i probably could help ya out! Jesus loves you all!

[Q] nexus 10 Bootloop - CWM exits in 30 secs or so `

Hi,
I recently got a nexus 10, and started working on rooting. I have unlocked it, installed CWM recovery and booted it twice. I have not rooted it yet. Now I realized, that everytime I entered the CWM recovery mode, it automatically reboots back into recovery or normal boot in about 30 seconds or so. (this is not the main problem!)
But one booting up second time, I got a notification of sytem update for 4.2 jellybean (please note initially the device was on 4.2 JB JVP15P), I clicked on install, it booted into CWM recovery, but then it failed to continue with installation, as it complained about authentication failure for the zip fle or something of that sort. So I chose to boot the device without installing the update, now it entered a boot loop. I have tried erasing cache and userdata (both using fastboot commandline, and options in the CWM - in the 30 secs I get). It did not work.
After trying it for a few times, I tried restoring some backups I had made. Initially it complained about MD5 mismatch, and then later on it complained about unable to mount cache/* and unable to mount sdcard.
I have read around and the universal solution seems to be to restore stock images. Is that the solution for me as well?
Any help would be greatly appreciated, and I am noob in this area, so pardon me if I act like one.
cheers,
brickin

I'd like to know part of the answer to this as well. The tab is running fine and TWRP works fine, but CWM constantly reboots and I have the same mounting problems within both CWM and TWRP. I've tried flashing stock image and recovery but it's made no difference.

IIRC, the newest CWM has an issue with devices that allow multiple users (aka: N7 and N10). Flash TWRP and don't look back.
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 06:07 AM ---------- Previous post was at 06:05 AM ----------
Also, TWRP supports USB OTG while CWM doesn't.
Sent from my Galaxy Nexus using Tapatalk 2

I was having a similar issue with cwm. This explains everything.

Blueback22 said:
IIRC, the newest CWM has an issue with devices that allow multiple users (aka: N7 and N10). Flash TWRP and don't look back.
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 06:07 AM ---------- Previous post was at 06:05 AM ----------
Also, TWRP supports USB OTG while CWM doesn't.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hi Blueback22,
Thanks a lot for your reply.
Would flashing TWRP solve everything? And also is it ok to flash TWRP now, would it be able to restore the backups I have made using CWM?
Do I need to uninstall or remove the CWM recovery image that has alreday been flashed? or will TWRP image overwrite it?
How do I solve the bootloop issue?
I am unable to get a stock image for JB version: JVP15P. Do you know where I can find the factory image for that?
OR is it ok for me to flash the JOP40C image? Would it cause any problems - (like would it cry saying checksum mismatch or something like that)?
Also, what is the solution for unable to mount sdcard problem?
Sorry for asking so many questions, but I do not wish to brick my device, hence I wish to understand what I am going to do, and ensure that it is not going to harm my device.
Your replies to this post is and will be deeply appreciated.
Thanks,
brickin

brickin said:
Hi Blueback22,
Thanks a lot for your reply.
Would flashing TWRP solve everything? And also is it ok to flash TWRP now, would it be able to restore the backups I have made using CWM?
Do I need to uninstall or remove the CWM recovery image that has alreday been flashed? or will TWRP image overwrite it?
How do I solve the bootloop issue?
I am unable to get a stock image for JB version: JVP15P. Do you know where I can find the factory image for that?
OR is it ok for me to flash the JOP40C image? Would it cause any problems - (like would it cry saying checksum mismatch or something like that)?
Also, what is the solution for unable to mount sdcard problem?
Sorry for asking so many questions, but I do not wish to brick my device, hence I wish to understand what I am going to do, and ensure that it is not going to harm my device.
Your replies to this post is and will be deeply appreciated.
Thanks,
brickin
Click to expand...
Click to collapse
If I were you, I would use WugFresh's toolkit to flash back to stock. Then I'd flash TWRP and start from scratch.
I don't know if TWRP will fix your issue all together, but I do remember hearing that there's an issue with CWM on the N10 right now.
Your CWM backups won't work on TWRP IIRC.
Here is where you can get stock images:
https://developers.google.com/android/nexus/images
Sent from my Galaxy Nexus using Tapatalk 2

Hi Blueback22,
Thanks for the help. I was able to fix the problem.
Here are the questions I had and the answers I found, please correct me if I am wrong.
1. My JB version is JVP15P, is it ok to flash JOP40C stock recovery image?
ans: yes
2. Does TWRP work perfectly with nexus 10?
ans: Atleast in my case it did, I was able to root my device, and was also able to take backups.
3. a. CWM complains E: Can't mound /sdcard !
b. CWM Keeps restarting within 30 secs or so !
c. My device is stuck in bootloop !
ans: First, try to wipe your cache, and userdata and reboot. If it does not solve, then flash stock factory image for your device and flash TWRP recovery image.
4. CWM complains E: can't mount /cache/*
ans: Wipe your cache, userdata and reboot.
Reiterating blueback22's point:
DO NOT USE CWM WITH NEXUS 10. USE TWRP INSTEAD.
Cheers,
brickin

BRICKED: OLd bootloader version wont update
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-manta-mantalj12.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.168s]
writing 'bootloader'...
OKAY [ 0.143s]
finished. total time: 0.318s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.009s
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-manta-mantalj12.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.170s]
writing 'bootloader'...
OKAY [ 0.145s]
finished. total time: 0.323s
C:\android-sdk\platform-tools>fastboot -w update image-mantaray-jop40c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ09
Baseband Version.....: no modem
Serial Number........:
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'MANTALJ09'.
Update requires 'MANTALJ12'.
finished. total time: 0.063s
I tried one click root and wug's root kits, but there wasn't any luck in returning to stock and stuck in older bootloader without the possibility of returning to stock. I am stuck in Clockworkmod v6.0.1.9 loops. Tried to search the forum but I couldnt find anything.

ginsboon said:
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-manta-mantalj12.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.168s]
writing 'bootloader'...
OKAY [ 0.143s]
finished. total time: 0.318s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.009s
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-manta-mantalj12.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.170s]
writing 'bootloader'...
OKAY [ 0.145s]
finished. total time: 0.323s
C:\android-sdk\platform-tools>fastboot -w update image-mantaray-jop40c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ09
Baseband Version.....: no modem
Serial Number........:
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'MANTALJ09'.
Update requires 'MANTALJ12'.
finished. total time: 0.063s
I tried one click root and wug's root kits, but there wasn't any luck in returning to stock and stuck in older bootloader without the possibility of returning to stock. I am stuck in Clockworkmod v6.0.1.9 loops. Tried to search the forum but I couldnt find anything.
Click to expand...
Click to collapse
Can you get into the boot loader and flash TWRP to see if that fixes it?
Sent from my Galaxy Nexus using Tapatalk 2

ginsboon said:
returning to stock. I am stuck in Clockworkmod v6.0.1.9 loops. Tried to search the forum but I couldnt find anything.
Click to expand...
Click to collapse
Why don't you try cwm 6.0.2.3? I also loaded 6.0.1.9 and it would reboot in about 30sec time. After going to the latest, cwm has been stable. No more random reboots.
Link to download the latest version...
http://www.clockworkmod.com/rommanager

cowabunga said:
Why don't you try cwm 6.0.2.3? I also loaded 6.0.1.9 and it would reboot in about 30sec time.
I tried to flash cwm 6.0.2.3 and twrp but failed. Still searching for some clues.
Click to expand...
Click to collapse

For OP and other N10 users with stock 4.2 JB Build JVP15P experience:
Is it possible to use the available toolkits (Wug's or mskip's) to unlock the bootloader and root a N10 with the configuration above? Both toolkits ask for Build JOP40C. I've searched the developer forum for this build and found nothing. Thanks!

Bootlooping, ADB not detected, can't enable debugging

So, where do I start?
I bought this device (Nexus 2013 Wi-Fi) in late november and have not updated it since. I attempted to update it today (because I received a notification to do so) to 4.4.2 (I think).
It restarted after the update and I've been stuck in a bootloop at the "4 circles".
I have done the following:
- put the device into the boatloader
- installed the nexus root toolkit and attempted to flash stock + unroot the device to the images: 4.3 (JSS15Q), 4.3 (JSS15R), and (KOT49H)
- this was what my output looked like
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.006s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 08e8df8e
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.003s]
sending 'boot' (7018 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.027s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
​
- And no, I have not tried the force flash.
- I have tried all the drive options and maybe I'm not following the directions properly but that does not seem to work (and it may be the main problem for all I know).
- I'm also not sure if I thoroughly removed all google nexus-related drivers prior to running the nexus root toolkit, so there may be that.
- I've tried some brute-force methods inspired by things I've seen here, as in:
un-packing the factory image files into the platform tools part of the android sdk files and run the following commands in the cmd.exe: fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img​ - My guess is that the problem lies with the fact that I cannot put the device in debugging mode and I cannot have it recognized by adb.
I'm not sure where to go from here and I'm rather frustrated. Please let me know what solutions I should re-try (but perhaps more carefully?) and new ones that I should know of.
I appreciate all your help

rohanjoshi said:
So, where do I start?
I bought this device (Nexus 2013 Wi-Fi) in late november and have not updated it since. I attempted to update it today (because I received a notification to do so) to 4.4.2 (I think).
It restarted after the update and I've been stuck in a bootloop at the "4 circles".
I have done the following:
- put the device into the boatloader
- installed the nexus root toolkit and attempted to flash stock + unroot the device to the images: 4.3 (JSS15Q), 4.3 (JSS15R), and (KOT49H)
- this was what my output looked like
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.006s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 08e8df8e
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.003s]
sending 'boot' (7018 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.027s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
​
- And no, I have not tried the force flash.
- I have tried all the drive options and maybe I'm not following the directions properly but that does not seem to work (and it may be the main problem for all I know).
- I'm also not sure if I thoroughly removed all google nexus-related drivers prior to running the nexus root toolkit, so there may be that.
- I've tried some brute-force methods inspired by things I've seen here, as in:
un-packing the factory image files into the platform tools part of the android sdk files and run the following commands in the cmd.exe: fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img​ - My guess is that the problem lies with the fact that I cannot put the device in debugging mode and I cannot have it recognized by adb.
I'm not sure where to go from here and I'm rather frustrated. Please let me know what solutions I should re-try (but perhaps more carefully?) and new ones that I should know of.
I appreciate all your help
Click to expand...
Click to collapse
Hi, rohanjoshi...
You're actually on the wrong forum... this is the forum for the first generation Nexus 7 (2012). The forum for your second generation Nexus 7 (2013) is located here...
http://forum.xda-developers.com/nexus-7-2013
--------------------------------
However, looking through your output, it seems the failure to flash is due to the bootloader being locked...
rohanjoshi said:
...
sending 'bootloader' (3911 KB)...
FAILED (remote: Bootloader is locked.)
...
Click to expand...
Click to collapse
You need to unlock it with...
Code:
fastboot oem unlock
....or whatever the equivalent is in the toolkit you're using.
Good luck.
Rgrds,
Ged.

GedBlake said:
Hi, rohanjoshi...
You're actually on the wrong forum... this is the forum for the first generation Nexus 7 (2012). The forum for your second generation Nexus 7 (2013) is located here...
http://forum.xda-developers.com/nexus-7-2013
--------------------------------
However, looking through your output, it seems the failure to flash is due to the bootloader being locked...
You need to unlock it with...
Code:
fastboot oem unlock
....or whatever the equivalent is in the toolkit you're using.
Good luck.
Rgrds,
Ged.
Click to expand...
Click to collapse
woops, I'll get on that!

Soft-bricked my phone

FIXED
Hi all! Been a member of XDA for a few years now, but only just had the pleasure of becoming a nexus user. Yesterday I decided to install the Android N preview to try it out, but decided I didn't want it on my phone. So when I got home, I wiped the phone and proceeded to flash the factory image, but no matter which image I flash it, it says "error: update package missing system.img". I have tried manually flashing each file in fastboot as I have seen in many threads, but nothing is working. I have tried restoring old TWRP backups and flashing custom ROMs in TWRP, but nothing is working. Help!
This is what the Command Prompt is saying:
sending 'bootloader' (3526 KB)...
OKAY [ 0.106s]
writing 'bootloader'...
OKAY [ 0.206s]
finished. total time: 0.314s
rebooting into bootloader...
OKAY [ 0.118s]
finished. total time: 0.119s
< waiting for device >
sending 'radio' (48600 KB)...
OKAY [ 1.151s]
writing 'radio'...
OKAY [ 2.172s]
finished. total time: 3.327s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.009s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate -1733501396 bytes
error: update package missing system.img
Press any key to exit...

Did you download the right image from here?

Are you following THIS guide, TO THE LETTER?
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Specifically step 10

irule311 said:
Did you download the right image from here?
Click to expand...
Click to collapse
Yep, straight from the Angler section. I've tried the latest one, as well as a few older ones. Nothing.

Soulfly3 said:
Are you following THIS guide, TO THE LETTER?
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Specifically step 10
Click to expand...
Click to collapse
Hi, I followed the steps exactly, before updating my 6P to N developer preview, I had previously flashed the factory image. Thanks!

Unzip it yourself and flash em each manually.
Make sure you have the lastest fastboot tools. Im going to go out on a limb and say yours are out of date

Rxpert said:
Unzip it yourself and flash em each manually.
Make sure you have the lastest fastboot tools. Im going to go out on a limb and say yours are out of date
Click to expand...
Click to collapse
Tried that as well. Everything flashes, except the system.img.

g4slyness said:
Tried that as well. Everything flashes, except the system.img.
Click to expand...
Click to collapse
Had the same problem when ai first got it.
Wugs toolkit fixed me up!
http://forum.xda-developers.com/nexus-6p/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258493

The logs make me feel like the file you downloaded is corrupted. Check the md5 maybe?
Sent from my Nexus 6P using Tapatalk

g4slyness said:
Tried that as well. Everything flashes, except the system.img.
Click to expand...
Click to collapse
Probably a corrupt download, did you check the MD5 after downloading?

g4slyness said:
Tried that as well. Everything flashes, except the system.img.
Click to expand...
Click to collapse
It looks like you are not in the directory with the boot.img, et al. (your post shows no boot.img,, ... ) Make sure you unzipped the image. There are 2 files you need to unzip, the one containing the bootloader and radio. In that unzipped folder will be another zip. Unzip that second folder and you'll see the boot.img, cache.img, et al. The change in to that folder from your terminal or move those files into the folder you created (if following Heisenberg's guide), then proceed.

g4slyness said:
Hi all! Been a member of XDA for a few years now, but only just had the pleasure of becoming a nexus user. Yesterday I decided to install the Android N preview to try it out, but decided I didn't want it on my phone. So when I got home, I wiped the phone and proceeded to flash the factory image, but no matter which image I flash it, it says "error: update package missing system.img". I have tried manually flashing each file in fastboot as I have seen in many threads, but nothing is working. I have tried restoring old TWRP backups and flashing custom ROMs in TWRP, but nothing is working. Help!
This is what the Command Prompt is saying:
sending 'bootloader' (3526 KB)...
OKAY [ 0.106s]
writing 'bootloader'...
OKAY [ 0.206s]
finished. total time: 0.314s
rebooting into bootloader...
OKAY [ 0.118s]
finished. total time: 0.119s
< waiting for device >
sending 'radio' (48600 KB)...
OKAY [ 1.151s]
writing 'radio'...
OKAY [ 2.172s]
finished. total time: 3.327s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.009s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate -1733501396 bytes
error: update package missing system.img
Press any key to exit...
Click to expand...
Click to collapse
I think you are using an old version of fastboot. Update it and try again. Problem was fastboot couldn't allocate enough system ram to hold the whole image or something. In the newer fastboot the file transfer was broken in to several segments.
Maybe try another USB port too won't hurt.

Gytole said:
Had the same problem when ai first got it.
Wugs toolkit fixed me up!
http://forum.xda-developers.com/nexus-6p/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258493
Click to expand...
Click to collapse
Thanks!!! It actually worked. Not sure what was wrong before, seemed as though every file I downloaded off of the google website was corrupted. Cheers!

g4slyness said:
Thanks!!! It actually worked. Not sure what was wrong before, seemed as though every file I downloaded off of the google website was corrupted. Cheers!
Click to expand...
Click to collapse
You're welcome!
Like I said I had the same problem back in November. It ended up being an outdated version of fastboot like others have stated. I coyld flash my friends Moto X Pure but not my Nexus 6P..mit was awful and brain racking. Glad all is good!