Database Users

Cannot flash system.img, df shows no system partition

Hi everybody!! I have a BIG issue: my nexus 4 is unlocked, with the CWM recovery and CyanogenMod 10.1 installed. Due to some technical problems, I decided to flash the factory rom again (following this guide http://forum.xda-developers.com/showthread.php?t=2010312) but I can't do it!! Indeed when I try to flash the factory rom the prompt says
file:could not allocate 544035848 bytes
error:cannot load system.img :not enough space
And when i checked the system capacity the result is that my system partition doesn't exist (as you can see on the pic attached)!
I wish to send my phone back to google with the RMA (it was delivered 7 days ago) but I'm not sure that the warranty is still valid (what do you think about that?). Indeed there is no OS now, and everything is unlocked.
Anybody could help me?
Thanks a lot!!

StefanoRedi said:
Hi everybody!! I have a BIG issue: my nexus 4 is unlocked, with the CWM recovery and CyanogenMod 10.1 installed. Due to some technical problems, I decided to flash the factory rom again (following this guide http://forum.xda-developers.com/showthread.php?t=2010312) but I can't do it!! Indeed when I try to flash the factory rom the prompt says
file:could not allocate 544035848 bytes
error:cannot load system.img :not enough space
And when i checked the system capacity the result is that my system partition doesn't exist (as you can see on the pic attached)!
I wish to send my phone back to google with the RMA (it was delivered 7 days ago) but I'm not sure that the warranty is still valid (what do you think about that?). Indeed there is no OS now, and everything is unlocked.
Anybody could help me?
Thanks a lot!!
Click to expand...
Click to collapse
use the fastboot commands to erase system, boot, and data. then use flashboot to flash bootloader, then stock recovery, then stock system.

EvoXOhio said:
use the fastboot commands to erase system, boot, and data. then use flashboot to flash bootloader, then stock recovery, then stock system.
Click to expand...
Click to collapse
Thanks!! Just a couple of questions: 1. the prompt commands are "fastboot erase system" "fastboot erase boot" and "fastboot erase data", right? 2. Have I to reboot the system between every erase and every flash?

StefanoRedi said:
Thanks!! Just a couple of questions: 1. the prompt commands are "fastboot erase system" "fastboot erase boot" and "fastboot erase data", right? 2. Have I to reboot the system between every erase and every flash?
Click to expand...
Click to collapse
That sounds right but Fiona search to be safe. No reboots needed.

StefanoRedi said:
Thanks!! Just a couple of questions: 1. the prompt commands are "fastboot erase system" "fastboot erase boot" and "fastboot erase data", right? 2. Have I to reboot the system between every erase and every flash?
Click to expand...
Click to collapse
I tryed to do it without results. I attach the screen.
Have you some other advises? I really don't know what i can do it with my phone. If i send it back to google, do you think that they will check if my phone is locked/unlocked, with/without os, ecc? Because I'm afraid to have wasted my money!

Have you tried booting into recovery and wiping everything before flashing system? Also you're sure you have the right system.img? Maybe re-download the files from google and try again?
---------- Post added at 09:23 AM ---------- Previous post was at 09:22 AM ----------
also, do you have any nandroids or downloaded ROMs on the phone? If so, you could try flashing CWM, and then booting into it and restoring the nandroid or installing a ROM.

R: Cannot flash system.img, df shows no system partition
We tried wiping everything trough fast boot, he does not have any nandroid backup and I think he tried to flash another ROM (cm) with no luck.
We downloaded the right images, we tried both 4.2.1 and JOP40D from the Google site and from the mirror that we found in some thread here on xda.
(I'm his friend and I was helping him via Skype, that's why I know these informations)
I think now we'll try to flash cwm and wipe everything trough it and install a stock ROM or a custom one.
Ty for the help.
Sent from my Nexus 4

squalluca said:
We tried wiping everything trough fast boot, he does not have any nandroid backup and I think he tried to flash another ROM (cm) with no luck.
We downloaded the right images, we tried both 4.2.1 and JOP40D from the Google site and from the mirror that we found in some thread here on xda.
(I'm his friend and I was helping him via Skype, that's why I know these informations)
I think now we'll try to flash cwm and wipe everything trough it and install a stock ROM or a custom one.
Ty for the help.
Sent from my Nexus 4
Click to expand...
Click to collapse
It really sounds like someone made a mistake and ran the wrong command and actually remove the /system partition. Not erased or formatted, but actually removed the mount point. I'm sure there is a way to recreate it, but I have no idea how.

R: Cannot flash system.img, df shows no system partition
That's what I think too... this error appeared before we tried any wipe/erase command trough fastboot... hope someone can help us in recrate the mount point for the system partition...
Sent from my Nexus 4

EvoXOhio said:
It really sounds like someone made a mistake and ran the wrong command and actually remove the /system partition. Not erased or formatted, but actually removed the mount point. I'm sure there is a way to recreate it, but I have no idea how.
Click to expand...
Click to collapse
Thanks guys! I really hope that someone knows how to recreate it and, if it's possibile, very soon, because the RMA expiration day is coming!!

This is generally to be avoided, but I think this may actually be a last resort situation. Download the full factory image extract down a few levels until you have flash-all.bat extracted, at that point you'll also see the radio, bootloader, an image zip, and some linux scripts. Make sure you've actually extracted them and that you aren't just looking in the zip. Run flash-all.bat Don't touch anything until it's done, if you disrupt the write to bootloader or possibly radio, you brick.
By the way, the factory image is here and you may need to use 7zip to extract it. 7zip will have shell integration, so just right click what you want, drop down to 7zip and extract to.
Also, you may be able to accomplish the same thing with:
Code:
fastboot -w update image-occam-jop40c.zip
so maybe try that first.

USSENTERNCC1701E said:
This is generally to be avoided, but I think this may actually be a last resort situation. Download the full factory image extract down a few levels until you have flash-all.bat extracted, at that point you'll also see the radio, bootloader, an image zip, and some linux scripts. Make sure you've actually extracted them and that you aren't just looking in the zip. Run flash-all.bat Don't touch anything until it's done, if you disrupt the write to bootloader or possibly radio, you brick.
By the way, the factory image is here and you may need to use 7zip to extract it. 7zip will have shell integration, so just right click what you want, drop down to 7zip and extract to.
Also, you may be able to accomplish the same thing with:
Code:
fastboot -w update image-occam-jop40c.zip
so maybe try that first.
Click to expand...
Click to collapse
Fine, I will try when I come back home. Just a question: what do you think about the warranty? Do you think that google will check if the phone is unlocked and without os? It is better for me risk with the last suggested process and (maybe) brick the phone or send it back as it is now? It's because I'm just a beginner with mod, scripts, prompts, ecc..sorry!

StefanoRedi said:
Fine, I will try when I come back home. Just a question: what do you think about the warranty? Do you think that google will check if the phone is unlocked and without os? It is better for me risk with the last suggested process and (maybe) brick the phone or send it back as it is now? It's because I'm just a beginner with mod, scripts, prompts, ecc..sorry!
Click to expand...
Click to collapse
The phone was damaged from user error. It is unethical and probably illegal to RMA it. Try to fix it yourself, and if you can't, man up and buy a new phone. RMAs are for faulty products, not products ruined by an inexperienced user doing something wrong.

EvoXOhio said:
The phone was damaged from user error. It is unethical and probably illegal to RMA it. Try to fix it yourself, and if you can't, man up and buy a new phone. RMAs are for faulty products, not products ruined by an inexperienced user doing something wrong.
Click to expand...
Click to collapse
You are completely right. I wrote that just because I messed up the phone (following guides, using toolkit, using cmd in a proper way) trying to fix it (from the first day it was impossible to call due to microphone/speaker software problem). And sometimes, while a was doing the same stuff that everybody do with good results, the phone didn't do what it was supposed to do. Consequently I wanted to RMA it because i think it's my fault (I know it and I admit it) but not completely. I really don't want to cheat anyone.

Well, I fixed it. I don't know the reason but the day after everything was fine (maybe it's because I erased everything from CWM; i wiped everything and then i wen on Mount and I erased everything). Btw, the day after I reflashed everything from prompt with the phone in fastboot and i flashed also system (the partition was "avaible" again); the .img flashed was the factory rom 4.2.0. Then I reboot it but the problem with microphone/speacker wasn't fixed; i updated to 4.2.1 and it still didn't work. Today I will call google to RMA it because now (just now) the phone is not working properly but not due to my errors. Thanks to everybody!!!! :laugh:

StefanoRedi said:
Well, I fixed it. I don't know the reason but the day after everything was fine (maybe it's because I erased everything from CWM; i wiped everything and then i wen on Mount and I erased everything). Btw, the day after I reflashed everything from prompt with the phone in fastboot and i flashed also system (the partition was "avaible" again); the .img flashed was the factory rom 4.2.0. Then I reboot it but the problem with microphone/speacker wasn't fixed; i updated to 4.2.1 and it still didn't work. Today I will call google to RMA it because now (just now) the phone is not working properly but not due to my errors. Thanks to everybody!!!! :laugh:
Click to expand...
Click to collapse
Make sure flash stock recovery and relock the device before sending it in.

EvoXOhio said:
Make sure flash stock recovery and relock the device before sending it in.
Click to expand...
Click to collapse
Of course! In theory it will not be a problem if there is the CWM recovery and if the phone it's unlucked (at least, I read that for Google and LG is not a problem), but I flashed the stock recovery and then I lucked the phone again. Thanks for your advises.

system.img cannot load, not enough space error
StefanoRedi said:
Well, I fixed it. I don't know the reason but the day after everything was fine (maybe it's because I erased everything from CWM; i wiped everything and then i wen on Mount and I erased everything). Btw, the day after I reflashed everything from prompt with the phone in fastboot and i flashed also system (the partition was "avaible" again); the .img flashed was the factory rom 4.2.0. Then I reboot it but the problem with microphone/speacker wasn't fixed; i updated to 4.2.1 and it still didn't work. Today I will call google to RMA it because now (just now) the phone is not working properly but not due to my errors. Thanks to everybody!!!! :laugh:
Click to expand...
Click to collapse
hey can anyone help me i have this error when i flash Stock 5.0.1 Lollipop, Kitkat flashing is working!

For Those Who Semi-Bricked Their Nexus 7 0MB Interal Storage

Hopefully this helps people in my situation.
So on the first day of having my nexus 7 i found a way to have no OS and 0MB internal storage showing in TWRP. Yah i suck.
I tried tons of things but knew a system image was needed.
HOW: I was about to flash the superuser root for 4.3 newly released and forgot to put it on nexus so i then proceeded to exit TWRP, however upon exiting TWRP the recovery detected i havent installed supersu and asked do i want to install superuser? I though why the hell not!
I confirmed to install superuser and then tried to reboot but for 20 minutes device could not boot. TWRP showed 0MB internal storage and pushing adb files in this state yielded nothing as there was no directory
This is how i managed to have a working tablet again
1. FORMAT DATA in TWRP - after doing this your internal storage should be back and not show 0MB
2. reboot to the bootloader
3. On your computer download this file kindly given to us by phuduong and uploaded by Nburnes
https://mega.co.nz/#!PBIiEbBJ!bKpdHxegOVlde12nsu_ulEyRq7UsANLLQab1IZjLIGc
Credit to Nburnes http://forum.xda-developers.com/member.php?u=2918596[/QUOTE]
4. Once downloaded move that system.img file to your adb directory
5. With you nexus 7 in the bootloader, adb open, and file downloaded copy and paste this command into adb terminal
fastboot flash system system.img
6. Now you have an OS but it still would loop and wouldnt start
7. Boot into recovery and Format Data again, because for me 0MB interal storage was back again
8. Then Factory Reset
FINALLY YOUR DEVICE SHOULD BE BACK TO ITS ORIGINAL STATE!!!!!

Is that the factory image? Have you tried going from unlocked bootloader & rooted back to factory using that image?

plbelanger said:
Is that the factory image? Have you tried going from unlocked bootloader & rooted back to factory using that image?
Click to expand...
Click to collapse
Google has yet to release the official factory image for the new N7. However, a kind user was gracious enough to make their own. It is likely to be almost identical to what Google will eventually release and should work the same way.

Thank you! Thank you!

good stuff OP. glad you got it working again

You all are life savers! 1000X Thanks!

I tried running through this, but it didn't work for me. I think my situation is different though because I tried to install a factory image for the 2012 nexus, and during part of that process I ran the "flash-all" script which starts by deleting boot, cache, recovery, userdata, and system.
I think deleting boot screwed me up, because even though I can go into recovery now after reinstalling twrp and I can restore my system using system.img, I still can't boot (get stuck on the google logo). Any way to fix that?

So you first tried to restore from the OLD Nexus 7 Image?????
Sent from my Nexus 7 using xda app-developers app

petersellers said:
I tried running through this, but it didn't work for me. I think my situation is different though because I tried to install a factory image for the 2012 nexus, and during part of that process I ran the "flash-all" script which starts by deleting boot, cache, recovery, userdata, and system.
I think deleting boot screwed me up, because even though I can go into recovery now after reinstalling twrp and I can restore my system using system.img, I still can't boot (get stuck on the google logo). Any way to fix that?
Click to expand...
Click to collapse
So you first tried to restore the OLD nexus 7 factory image? Probably gonna have to wait for factory image or exchange yours
Sent from my Nexus 7 using xda app-developers app

jporter396 said:
So you first tried to restore from the OLD Nexus 7 Image?????
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I tried to restore from the old image. Obviously fastboot wont let you install the old image, but I didn't realize that until boot, system, cache, etc. were deleted

THANK YOU!!!
This worked perfectly! I had a wiped system folder (no ROM), and obviously no USB debugging enabled. And with the lack of a factory image, I've been counting seconds to seeing somebody post this!
Just follow the instructions carefully. Thank you guys!

petersellers said:
Yes, I tried to restore from the old image. Obviously fastboot wont let you install the old image, but I didn't realize that until boot, system, cache, etc. were deleted
Click to expand...
Click to collapse
You can flash old and new image through fastboot. I did 2 times ^_^
This is boot.img for who need
BOOT.IMG HERE

It gives me a fail when I try to wipe data.
Edit: never mind

jarjar124 said:
It gives me a fail when I try to wipe data.
Edit: never mind
Click to expand...
Click to collapse
How did you fix it? I still cant wipe data.

Balsta said:
How did you fix it? I still cant wipe data.
Click to expand...
Click to collapse
Have you formatted first?
Sent from my Nexus 7 using xda app-developers app

jporter396 said:
Have you formatted first?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I can't, get an error with that too
Sent from my SCH-I545 using Tapatalk 4 Beta

OP and nburnes saved my butt!

I did this and now it seems my device is booting and it shows up as N7 when I attach it to my PC. But the display shows nothing at all. It just goes blank after the Google screen. Any ideas?
After flashing everything I could think of and banging my head and the device against the wall for two hours, I finally got it to work. Not sure how exactly but the last thing I did was reflashing bootloader. So if anyone has the same problem, try that.

Thank you.
Note:
Give step 6 a little time be patient.

All main JSS15J .IMGS here: http://forum.xda-developers.com/showthread.php?t=2381438
Glad this helped some of you guys!

[Q] Nexus 4: Can't wipe/Flash factory image. Semi-bricked phone.

Earlier today my phone was working fine running Stock 4.4.1/Kernel. I decided I wanted to get the franco kernel so I got the .img file from the xda thread. I flashed the .img file onto the boot partition using fastboot, and restarted my phone. After a few minutes of sitting at the "Google" screen I rebooted into the bootloader. I tried flashing the 4.4 factory image using the "flash-all.bat" without wiping anything. My phone continued to get stuck at the "Google" screen after multiple reboots. I then tried to wipe my device using fastboot. However, when using the command "fastboot erase system" I got an error that said "Failed: unknown chunk type." I kept on retrying the wipe to no avail. I found this thread: http://forum.xda-developers.com/showthread.php?t=2347060 and followed the steps. All the steps seemed to work up until I had to flash the given factory image using fastboot. I got the same "Unknown chunk type" when the cmd was trying to write files to the "system partition." Before you ask, yes my fastboot/adb is updated to the newest version. (I triple checked) And all my drivers work properly. I just flashed the 4.4.1 firmware 3 days ago using fastboot and everything went perfectly, including the wipe. Please offer any solutions you think could get me out of this situation. Thank you.

PandemicHD said:
Earlier today my phone was working fine running Stock 4.4.1/Kernel. I decided I wanted to get the franco kernel so I got the .img file from the xda thread. I flashed the .img file onto the boot partition using fastboot, and restarted my phone. After a few minutes of sitting at the "Google" screen I rebooted into the bootloader. I tried flashing the 4.4 factory image using the "flash-all.bat" without wiping anything. My phone continued to get stuck at the "Google" screen after multiple reboots. I then tried to wipe my device using fastboot. However, when using the command "fastboot erase system" I got an error that said "Failed: unknown chunk type." I kept on retrying the wipe to no avail. I found this thread: http://forum.xda-developers.com/showthread.php?t=2347060 and followed the steps. All the steps seemed to work up until I had to flash the given factory image using fastboot. I got the same "Unknown chunk type" when the cmd was trying to write files to the "system partition." Before you ask, yes my fastboot/adb is updated to the newest version. (I triple checked) And all my drivers work properly. I just flashed the 4.4.1 firmware 3 days ago using fastboot and everything went perfectly, including the wipe. Please offer any solutions you think could get me out of this situation. Thank you.
Click to expand...
Click to collapse
Never encountered something like this, but maybe from bootloader u can get into ur stock recovery & wipe cahce & wipe data.
once again I never had that issue...so its upto u...but might be worth a try...if u had made a backup or dont care about the data in ur phone then it did be easier for u u to try

Flash the factory images and erase all partitions on the device. If you want to get some data from the internal memory you could pull it through recovery. Next time read more do less. Franko's kernel uses different ram disk than the stock one. You could also try to flash a full stock kernel for your build first. Get it from the factory images and flash it through fastboot.
Sent from my Nexus 4 using xda app-developers app

i have the exact same problem here ! and i dont know what to do! its still stucked on the google logo!!!

alexvck said:
i have the exact same problem here ! and i dont know what to do! its still stucked on the google logo!!!
Click to expand...
Click to collapse
What's the exact same problem? Did you flash Franko kernel too. If so just dirty flash your current rom.

jd1639 said:
What's the exact same problem? Did you flash Franko kernel too. If so just dirty flash your current rom.
Click to expand...
Click to collapse
no i just had rooted it and loadedcwm and i was ready to flash paranoid anroid rom! and when it rebooted it stuck on the google logo! then i tried to reset my phone and load the official factory image with nexus root toolkit but when it did the usual procces with the command prmpt in some point after trying to write the new system it said "Failed: unknown chunk type." ! after that it rebooted and got stucked again in google logo!!

alexvck said:
no i just had rooted it and loadedcwm and i was ready to flash paranoid anroid rom! and when it rebooted it stuck on the google logo! then i tried to reset my phone and load the official factory image with nexus root toolkit but when it did the usual procces with the command prmpt in some point after trying to write the new system it said "Failed: unknown chunk type." ! after that it rebooted and got stucked again in google logo!!
Click to expand...
Click to collapse
Use this to flash the factory image http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312

jd1639 said:
Use this to flash the factory image http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Click to expand...
Click to collapse
my device is bricked i cant do these stuff :/

alexvck said:
my device is bricked i cant do these stuff :/
Click to expand...
Click to collapse
Can you get into bootloader mode. It's worth a try. Your not bricked if it can turn on. Your emmc may be bad and flashing the factory image won't work. But if that's the case then warranty or replacement are your only options.

jd1639 said:
Can you get into bootloader mode. It's worth a try. Your not bricked if it can turn on. Your emmc may be bad and flashing the factory image won't work. But if that's the case then warranty or replacement are your only options.
Click to expand...
Click to collapse
yes i can get in bootloader! but i cant do sth :/ ... whats the emmc ?!

Originally Posted by jd1639<br />
Can you get into bootloader mode. It's worth a try. Your not bricked if it can turn on. Your emmc may be bad and flashing the factory image won't work. But if that's the case then warranty or replacement are your only options.
Click to expand...
Click to collapse
<br />
<br />
yes i can get in bootloader! but i cant do sth :/ ... whats the emmc ?!
Click to expand...
Click to collapse
Emmc is the flash memory.

jd1639 said:
Emmc is the flash memory.
Click to expand...
Click to collapse
oo okay.. so is there sth else that i can try?!

alexvck said:
oo okay.. so is there sth else that i can try?!
Click to expand...
Click to collapse
have you tired the the toolkits?

I had problem with flash system.img, solved changing usb port. I hope help you.
Inviato dal mio Nexus 4 utilizzando Tapatalk

Android 5.1 bootloop problem

I'm currently having a boot loop problem on my nexus 10 device, where the boot animation goes on forever.
I was on android 5.01, then downloaded 5.1.
I Followed the instructions to apply the upgrade and everything look like it was fine. Tried to reboot the device and all I get is the spinning balls.
I didn't want to lose my data/wipe the device so I DID NOT use the -w command on the fastboot update command. I've done that before and it worked.
Can you someone give me advice on how to fix the problem.
Also, can it be fixed without doing a factory reset?
Thanks

bflatmajor said:
I'm currently having a boot loop problem on my nexus 10 device, where the boot animation goes on forever.
I was on android 5.01, then downloaded 5.1.
I Followed the instructions to apply the upgrade and everything look like it was fine. Tried to reboot the device and all I get is the spinning balls.
I didn't want to lose my data/wipe the device so I DID NOT use the -w command on the fastboot update command. I've done that before and it worked.
Can you someone give me advice on how to fix the problem.
Also, can it be fixed without doing a factory reset?
Thanks
Click to expand...
Click to collapse
How long did you let the boot go for? The first boot takes a REALLY LONG time.

over 15 minutes..
Im rebooting it now.. lets see what happens
after more than 30 minutes, still no change in behavior

bflatmajor said:
over 15 minutes..
Im rebooting it now.. lets see what happens
after more than 30 minutes, still no change in behavior
Click to expand...
Click to collapse
You wouldn't happen to have an old ROM on your device would you? If so, maybe flash that and see if you can at least boot. If you can't even boot you may have to do a full wipe.

bflatmajor said:
I'm currently having a boot loop problem on my nexus 10 device, where the boot animation goes on forever.
I was on android 5.01, then downloaded 5.1.
I Followed the instructions to apply the upgrade and everything look like it was fine. Tried to reboot the device and all I get is the spinning balls.
I didn't want to lose my data/wipe the device so I DID NOT use the -w command on the fastboot update command. I've done that before and it worked.
Can you someone give me advice on how to fix the problem.
Also, can it be fixed without doing a factory reset?
Thanks
Click to expand...
Click to collapse
I noticed this has happened to me before when I would flash all the images (except userdata) and elect to only erase cache, and not flash the cache image. It would be stuck in the bootanimation forever. Once I started flashing the cache image when upgrading, I've never had an issue since. So my advice to you is to flash the cache image from the factory image and see if that fixes it. All your data will still be intact.

charesa39 said:
I noticed this has happened to me before when I would flash all the images (except userdata) and elect to only erase cache, and not flash the cache image. It would be stuck in the bootanimation forever. Once I started flashing the cache image when upgrading, I've never had an issue since. So my advice to you is to flash the cache image from the factory image and see if that fixes it. All your data will still be intact.
Click to expand...
Click to collapse
How did you do this exactly? My phone is in that exact cycle...

gundamslicer said:
How did you do this exactly? My phone is in that exact cycle...
Click to expand...
Click to collapse
You may also need to wipe dalvik if you have not tried that already.
The factory cache image is in the same zip file with system.img, boot.img, etc. You need to boot back to fastboot and do
Code:
fastboot flash cache <path_to_cache_image>
I recently upgraded to 5.1 by flashing only system.img and boot.img and wiping only cache and dalvik and I didn't have any issues.

gundamslicer said:
How did you do this exactly? My phone is in that exact cycle...
Click to expand...
Click to collapse
I usually follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. Obviously, just make sure you have the correct factory image files for the Nexus 10. MAKE SURE NOT TO FLASH USERDATA. If you do, you will wipe your device and you will lose all your data. So I always just skip that command when I'm flashing the image files. After you're done flashing the cache image, just unplug your device and select "Start" from the bootloader menu. It will boot up normally and then you will see the "Android upgrading app ## of ##" message. That means everything worked.

Same problem happened with me. After applying the ota update for 5.1, I got locked in the boot animation.
Tried to reinstall the 5.1 manually, same thing happened.
I also tried to downgrade to 5.0.2 and 5.0.1 with no lucky. Now the tablet is useless.
Anyone else is experiencing this problem. Any suggestion to solve it?

luizm.jr said:
Same problem happened with me. After applying the ota update for 5.1, I got locked in the boot animation.
Tried to reinstall the 5.1 manually, same thing happened.
I also tried to downgrade to 5.0.2 and 5.0.1 with no lucky. Now the tablet is useless.
Anyone else is experiencing this problem. Any suggestion to solve it?
Click to expand...
Click to collapse
How are "reinstalling 5.1 manually"? Are you following the steps (Method 2) in the link I posted in the post above yours?

No. I ran the batch on the original rom downloaded from google.
Sent from my HTC One_M8 using XDA Free mobile app

luizm.jr said:
No. I ran the batch on the original rom downloaded from google.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Ah. That's what I had thought. That could be your problem right there. Unfortunately, the batch process hasn't worked properly since 5.0. Not sure if Google fixed this with 5.1, but I doubt it. Try flashing all of the images manually. DON'T FLASH USERDATA, unless you don't care about losing your data.

charesa39 said:
Ah. That's what I had thought. That could be your problem right there. Unfortunately, the batch process hasn't worked properly since 5.0. Not sure if Google fixed this with 5.1, but I doubt it. Try flashing all of the images manually. DON'T FLASH USERDATA, unless you don't care about losing your data.
Click to expand...
Click to collapse
I followed the method 2 and flashed everything except userdata and radio (bootloader, system, boot, recovery and cache). Still locked in the boot animation.
I noted that before accepting any flash command I sent, Nexus screen displayed "FASTBOOT STATUS - FAIL Invalid Partition". But at the end of flash it was displayed "FASTBOOT STATUS - OKAY"

luizm.jr said:
I followed the method 2 and flashed everything except userdata and radio (bootloader, system, boot, recovery and cache). Still locked in the boot animation.
I noted that before accepting any flash command I sent, Nexus screen displayed "FASTBOOT STATUS - FAIL Invalid Partition". But at the end of flash it was displayed "FASTBOOT STATUS - OKAY"
Click to expand...
Click to collapse
Hmm. That invalid partition message is odd. Were you stock before? Did the command window show "OKAY" after each image was flashed? I'm wondering if your userdata partition is messed up as well. Not sure if all your stuff is backed up, but I would probably flash everything again, including userdata to start fresh. Obviously, you would lose all your data.

I never had unlocked the bootloader before in this device.
Yes, I got an OKAY after every flash. But also the invalid partition message at the beginning.
I'll try to flash everything again, including user data and let you know.
Thanks
Sent from my HTC One_M8 using XDA Free mobile app

It worked! However I lost all my data. I thought the new lollipop cloud backup would restore the app data but it was a fresh install for everything including the Google Now launcher.
Thanks
Sent from my HTC One_M8 using XDA Free mobile app

luizm.jr said:
It worked! However I lost all my data. I thought the new lollipop cloud backup would restore the app data but it was a fresh install for everything including the Google Now launcher.
Thanks
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
That sucks about losing your data... But at least you have a functioning N10 now. :good: I'm thinking the data partition may have somehow got corrupted, which is why it wasn't completing the boot process. Glad it worked out for you in the end though.

OS wiped accidentally from TWRP recovery

I accidentally wiped the OS from advanced wipe option. How do I get my phone to work again. I tried to operate adb sideload from recovery but it failed. I have downloaded the stock rom but I do not know how to install it.
Please help.
Thanks.

Kalaxy said:
I accidentally wiped the OS from advanced wipe option. How do I get my phone to work again. I tried to operate adb sideload from recovery but it failed. I have downloaded the stock rom but I do not know how to install it.
Please help.
Thanks.
Click to expand...
Click to collapse
Just flash it from custom recovery, so download it into ur phone go to recovery and simply flash it and all should be good.
Sent from my Nexus 6P using Tapatalk

Exiwolfman said:
Just flash it from custom recovery, so download it into ur phone go to recovery and simply flash it and all should be good.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
How do I download it to my phone if I cannot boot into it. Is there any way I can copy a zip file (rom) onto the phone's internal memory.?

Your phone should boot into recovery, so as long as it goes on and boots all u do u is use ur pc to move file over and flash it...
Sent from my Nexus 6P using Tapatalk

Kalaxy said:
How do I download it to my phone if I cannot boot into it. Is there any way I can copy a zip file (rom) onto the phone's internal memory.?
Click to expand...
Click to collapse
Boot into bootloader (hold power and system on), flash the though recovery through adb, mount your .zip,, flash your .zip through recovery. Sorry if that doesn't make sense, I've been drinking with the roommates, lol.
Edit: if that doesn't work, send me an IM and I will help you in the morning
Sent from my Huawei Nexus 6P using XDA Labs

Which state is your phone in right now? Is it bootlooping or in recovery?
Sent from my HTC 10 using Tapatalk

The same thing happened to me also! The whole /data (incl. sdcard) partition went corrupt (showed up in TWRP as eemc instead of ext4) & the /vendor failed to mount.
First I had to repair the /data partition (unfortunately the data was lost, as it repaired to a blank partition). I ended up having to go home (was at work at the time) & hook the phone up to the PC & download the ROM & transfer it onto the sdcard. I'm not entirely sure why/how this happened, but I believe it was because a corrupt vendor IMG. Although that theory doesnt include why the /data partition corrupted, it only explains why the /vendor partition failed to mount.

Fastboot flash system system.img
?

removed

I have the same issue. The problem is, that my computer will not recognize the phone in bootloader mode or in recovery mode(MTP enabled). How can install usb drivers without being able to boot into phone OS???? I've tried Nexus Toolkit with no success. Please help?

Have a look here how to load in bootloader, flash, etc.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

So I did the same thing. I'm sitting in TWRP right now but have nothing on the phone. Will I be able to reboot from TWRP into the bootloader and just use the flash-all command to get my phone to boot back up, then just go through the process of custom recovery again?
Basically I'm worried about leaving twrp without an OS. I didn't wipe bootloader did I? Also, I tried to download a ROM and just drag it to internal memory, but I can't seem to add anything to the internal memory.

dbroer91884 said:
So I did the same thing. I'm sitting in TWRP right now but have nothing on the phone. Will I be able to reboot from TWRP into the bootloader and just use the flash-all command to get my phone to boot back up, then just go through the process of custom recovery again?
Basically I'm worried about leaving twrp without an OS. I didn't wipe bootloader did I? Also, I tried to download a ROM and just drag it to internal memory, but I can't seem to add anything to the internal memory.
Click to expand...
Click to collapse
Hi... Just boot into recovery and reflash system.img from the factory image of your choice in bootloader with fastboot. Also flash the vendor image from the same factory image. Done...
Or reflash the whole package with flash all (manually is better imho). But you'll waisted time... Let your phone reboot into Android and you'll have your internal storage back.

5.1 said:
Hi... Just boot into recovery and reflash system.img from the factory image of your choice in bootloader with fastboot. Also flash the vendor image from the same factory image. Done...
Or reflash the whole package with flash all (manually is better imho). But you'll waisted time... Let your phone reboot into Android and you'll have your internal storage back.
Click to expand...
Click to collapse
Thats what I thought. JUst wanted to make sure I could get into bootloader still

dbroer91884 said:
So I did the same thing. I'm sitting in TWRP right now but have nothing on the phone. Will I be able to reboot from TWRP into the bootloader and just use the flash-all command to get my phone to boot back up, then just go through the process of custom recovery again?
Basically I'm worried about leaving twrp without an OS. I didn't wipe bootloader did I? Also, I tried to download a ROM and just drag it to internal memory, but I can't seem to add anything to the internal memory.
Click to expand...
Click to collapse
Yes TWRP has a reboot to bootloader option available. So you can access fastboot via bootloader to flash the necessary images. Just don't forget to re flash TWRP image again in case the stock recovery image was flashed beforehand.

The odd thing was that I did choose that option to boot to bootloader in twrp and it didn't work. I ended up having to reboot to bootloader manually. Not a big deal. All is working now, but thought that was interesting.

Kalaxy said:
I accidentally wiped the OS from advanced wipe option. How do I get my phone to work again. I tried to operate adb sideload from recovery but it failed. I have downloaded the stock rom but I do not know how to install it.
Click to expand...
Click to collapse
Exactly which partitions did you wipe? system? data? Internal Storage (userdata)? all of the above? Hopefully you did not wipe userdata (all your stuff). Were you on a stock ROM? You should be able to d/l the Google image from the same build you were on, extract system and data and fastboot flash those. Don't flash userdata. All your stuff should be there. Follow the tutorial on how to set up fastboot and selectively flash partitions.
---------- Post added at 06:49 AM ---------- Previous post was at 06:44 AM ----------
This thread got hijacked at least 3 times. Let's hope OP can find his way back.

pocholo36 said:
I have the same issue. The problem is, that my computer will not recognize the phone in bootloader mode or in recovery mode(MTP enabled). How can install usb drivers without being able to boot into phone OS???? I've tried Nexus Toolkit with no success. Please help?
Click to expand...
Click to collapse
Try this Hope you get solution to your problem of installing adb and fastboot tools in the correct manner.

I just by mistake deleted my internal storage.
I have TWRP, how do i put the ROM on there and flash it? Someone please help.
Thanks