Hi,
I'm just going to go through my experience with this as the symptoms seem to be the same for a number of people but the fixes seem to be quite different.
Having just recently re-purchased a Nexus 10 replacement for a faulty unit sent to me a few months ago (still waiting for the company to give me a refund on that!) I decided to go ahead and root the device.
Yes according to the documentation this should be quite easy!, however several people have been experiencing issues after flashing the boot loader with CWRM.
I tried both CWRM and TWRP however, none of them managed to solve my issue which in turn was the infamous "boot loop".
Google'ing around a little I found a few links which were helpful:
http://xdaforums.com/showthread.php?t=2588236
https://developers.google.com/android/nexus/images
http://www.androidegis.com/how-to/install-official-clockworkmod-recovery-for-nexus-10-guide/
http://www.droidforums.net/threads/stock-recovery-red-triangle.205716/
http://xda-university.com/as-a-user/how-to-recover-from-a-bootloop
http://xdaforums.com/nexus-4/help/unable-to-mount-cache-twrp-t2393833
http://www.teamw.in/OpenRecoveryScript
http://xdaforums.com/google-nexus-5/general/howto-repairing-corrupted-data-partition-t2577447/page3
http://xdaforums.com/showthread.php?t=2265817
So before anyone starts screaming Arrrrggghh! How to get through all those links, this was the issue with my device:
Basically it seems that somehow for whatever reason the /cache and /data partitions including the /data/sdcard mount was corrupted.
Using TWRP first of all I managed to find that the a fore mentioned partitions where showing up as having no capacity. This scared the heeby jeebies out of me as the tablet only arrived on the same day, and my first thought was "not again!". Could this be flash memory gone bad?
After a bit of digging and error messages showing up regarding to corrupted links with the /dev partition, it seemed obvious that I needed to somehow do a linux esque:
finally stumbling across Philz Recovery in one of the links I decided to test my theory. I recreated the /data and /cache partitions using the "Format" tool then mounted them. It worked pretty nicely.
The next stage was to get the OS installed and bootable.
Using the Google ROM recovery script I re-flashed the original 4.2.2 ROM and tested to see if I got boot. I was unlucky, as this went straight into another "boot loop".
Reflashing Philz Recovery I again rebuilt the /cache and /data... /data/sdcard partitions using the format tool and tested with mounting. All was good!
Now booting into the OS with fingers crossed, I managed to achieve boot again and all partitions where/are fine. I then went through the series of updates and finally rooted the device and now all is good.
I don't understand why the:
commands messed things up during the ROM Reflash but at least the tablet is back to a stable and usable state.
It's a really odd but interesting issue....
So hopefully someone will find this useful next time they get into a boot loop and errors crop up about the /data and /cache partitions not being mountable......
I'm just going to go through my experience with this as the symptoms seem to be the same for a number of people but the fixes seem to be quite different.
Having just recently re-purchased a Nexus 10 replacement for a faulty unit sent to me a few months ago (still waiting for the company to give me a refund on that!) I decided to go ahead and root the device.
Yes according to the documentation this should be quite easy!, however several people have been experiencing issues after flashing the boot loader with CWRM.
I tried both CWRM and TWRP however, none of them managed to solve my issue which in turn was the infamous "boot loop".
Google'ing around a little I found a few links which were helpful:
http://xdaforums.com/showthread.php?t=2588236
https://developers.google.com/android/nexus/images
http://www.androidegis.com/how-to/install-official-clockworkmod-recovery-for-nexus-10-guide/
http://www.droidforums.net/threads/stock-recovery-red-triangle.205716/
http://xda-university.com/as-a-user/how-to-recover-from-a-bootloop
http://xdaforums.com/nexus-4/help/unable-to-mount-cache-twrp-t2393833
http://www.teamw.in/OpenRecoveryScript
http://xdaforums.com/google-nexus-5/general/howto-repairing-corrupted-data-partition-t2577447/page3
http://xdaforums.com/showthread.php?t=2265817
So before anyone starts screaming Arrrrggghh! How to get through all those links, this was the issue with my device:
Basically it seems that somehow for whatever reason the /cache and /data partitions including the /data/sdcard mount was corrupted.
Using TWRP first of all I managed to find that the a fore mentioned partitions where showing up as having no capacity. This scared the heeby jeebies out of me as the tablet only arrived on the same day, and my first thought was "not again!". Could this be flash memory gone bad?
After a bit of digging and error messages showing up regarding to corrupted links with the /dev partition, it seemed obvious that I needed to somehow do a linux esque:
Code:
fdisk -l
fisk /<partition>
e2fsck -t <type> /<partition>finally stumbling across Philz Recovery in one of the links I decided to test my theory. I recreated the /data and /cache partitions using the "Format" tool then mounted them. It worked pretty nicely.
The next stage was to get the OS installed and bootable.
Using the Google ROM recovery script I re-flashed the original 4.2.2 ROM and tested to see if I got boot. I was unlucky, as this went straight into another "boot loop".
Reflashing Philz Recovery I again rebuilt the /cache and /data... /data/sdcard partitions using the format tool and tested with mounting. All was good!
Now booting into the OS with fingers crossed, I managed to achieve boot again and all partitions where/are fine. I then went through the series of updates and finally rooted the device and now all is good.
I don't understand why the:
Code:
fastboot erase cache
fastboot erase datacommands messed things up during the ROM Reflash but at least the tablet is back to a stable and usable state.
It's a really odd but interesting issue....
So hopefully someone will find this useful next time they get into a boot loop and errors crop up about the /data and /cache partitions not being mountable......
