Database Users

Curious issues with Nexus 7

Okay, so I'm having what I believe to be a strange issue and was hoping someone here might be able to help.
One day my Nexus 7 (2012/wifi/grouper) started to reboot while sitting on my desk. It then would go into a boot-loop. I turned if off for a bit and every time since it does the same thing. Loads up correctly but after any amount of time it will do the same thing.
So I tried a Factory Wipe & Erase. It went through the whole deal and I rebooted it; but the device didn't wipe or erase, everything was still on the device. >.>
So I decided to flash back to stock. (device was/is unlocked/rooted). Updated the SDK and made sure adb and fastboot both work correctly and that I had the most recent updates to anything available. USB drivers are current and working correctly. Fantastic I say to myself as I go through the fastboot process of returning to stock.
Code:
C:\android-sdk\platform-tools>fastboot devices
015d2d42201c1213 fastboot
I hit fastboot devices and it shows me my device, so I go through the normal bits. This is what I get:
Code:
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.283s]
writing 'bootloader'...
OKAY [ 0.596s]
finished. total time: 0.879s
Awesome! It appears everything is working fine, so I figure I might as well continue.
Code:
C:\android-sdk\platform-tools>fastboot -w update image-nakasi-krt16s.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d2d42201c1213
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.019s]
sending 'boot' (4990 KB)...
OKAY [ 0.652s]
writing 'boot'...
OKAY [ 0.177s]
sending 'recovery' (5530 KB)...
OKAY [ 0.722s]
writing 'recovery'...
OKAY [ 0.184s]
erasing 'system'...
OKAY [ 0.021s]
sending 'system' (611886 KB)...
OKAY [ 78.120s]
writing 'system'...
OKAY [ 27.180s]
erasing 'userdata'...
OKAY [ 0.030s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [ 25.415s]
erasing 'cache'...
OKAY [ 0.012s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [ 1.655s]
rebooting...
finished. total time: 134.326s
Alright, we're booting back into the device and it appears to have gone fine! But then I notice I'm still seeing the Jellybean "X" boot screen and think to myself well, that's kind of strange...The Nexus 7 loads up and...nothing changed. The device still has everything on it that it had previously, nothing has been changed or deleted.
I've tried deleting (user data such as music or videos) using Windows Explorer. I've tried File Manager and ES File Explorer via the tablet. But every, single time I turn the device back on...everything is still there!
So I guess what I'm trying to figure out is...am I high? Did I die in my sleep and I'm just not aware of it yet? Has my Nexus 7 been cast for a sequel of Groundhog's Day?
What am I missing here? I've done this time and time again but I don't think I've ever seen something like on any of my previous devices (or with this N7 in question as well...)
Hopefully I'm missing something very minor here and someone will make me feel stupid for it. I don't mind feeling stupid if it means I learn something new! (Any and all help would be greatly appreciated.)

limbonik said:
Okay, so I'm having what I believe to be a strange issue and was hoping someone here might be able to help.
One day my Nexus 7 (2012/wifi/grouper) started to reboot while sitting on my desk. It then would go into a boot-loop. I turned if off for a bit and every time since it does the same thing. Loads up correctly but after any amount of time it will do the same thing.
So I tried a Factory Wipe & Erase. It went through the whole deal and I rebooted it; but the device didn't wipe or erase, everything was still on the device. >.>
So I decided to flash back to stock. (device was/is unlocked/rooted). Updated the SDK and made sure adb and fastboot both work correctly and that I had the most recent updates to anything available. USB drivers are current and working correctly. Fantastic I say to myself as I go through the fastboot process of returning to stock.
Code:
C:\android-sdk\platform-tools>fastboot devices
015d2d42201c1213 fastboot
I hit fastboot devices and it shows me my device, so I go through the normal bits. This is what I get:
Code:
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.283s]
writing 'bootloader'...
OKAY [ 0.596s]
finished. total time: 0.879s
Awesome! It appears everything is working fine, so I figure I might as well continue.
Code:
C:\android-sdk\platform-tools>fastboot -w update image-nakasi-krt16s.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d2d42201c1213
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.019s]
sending 'boot' (4990 KB)...
OKAY [ 0.652s]
writing 'boot'...
OKAY [ 0.177s]
sending 'recovery' (5530 KB)...
OKAY [ 0.722s]
writing 'recovery'...
OKAY [ 0.184s]
erasing 'system'...
OKAY [ 0.021s]
sending 'system' (611886 KB)...
OKAY [ 78.120s]
writing 'system'...
OKAY [ 27.180s]
erasing 'userdata'...
OKAY [ 0.030s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [ 25.415s]
erasing 'cache'...
OKAY [ 0.012s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [ 1.655s]
rebooting...
finished. total time: 134.326s
Alright, we're booting back into the device and it appears to have gone fine! But then I notice I'm still seeing the Jellybean "X" boot screen and think to myself well, that's kind of strange...The Nexus 7 loads up and...nothing changed. The device still has everything on it that it had previously, nothing has been changed or deleted.
I've tried deleting (user data such as music or videos) using Windows Explorer. I've tried File Manager and ES File Explorer via the tablet. But every, single time I turn the device back on...everything is still there!
So I guess what I'm trying to figure out is...am I high? Did I die in my sleep and I'm just not aware of it yet? Has my Nexus 7 been cast for a sequel of Groundhog's Day?
What am I missing here? I've done this time and time again but I don't think I've ever seen something like on any of my previous devices (or with this N7 in question as well...)
Hopefully I'm missing something very minor here and someone will make me feel stupid for it. I don't mind feeling stupid if it means I learn something new! (Any and all help would be greatly appreciated.)
Click to expand...
Click to collapse
I'm not an expert on these things but I basically have a question for you. If you're willing to wipe out the whole thing, have you tried doing the factory reset via settings?
Sent from my Nexus 7 (2013)

Thanks for the suggestion. I have tried Factory wipe from inside the device and it says it completes and I reboot to everything on the device.
I've also tried wiping everything out using TWRP and it to gives me a completion message, but after start up everything is still on the device.
I've also went into TWRP under advanced options, used the built in file explorer and deferred everything from the "sd card". But once again the device reboots, loads up...And everything is there once more!
That's why I wasn't sure if I might be high or dead. I am completely dumbfounded by what's occurring here. -.-
Sent from my Nexus 7 (2013) running 4.4

limbonik said:
Thanks for the suggestion. I have tried Factory wipe from inside the device and it says it completes and I reboot to everything on the device.
I've also tried wiping everything out using TWRP and it to gives me a completion message, but after start up everything is still on the device.
I've also went into TWRP under advanced options, used the built in file explorer and deferred everything from the "sd card". But once again the device reboots, loads up...And everything is there once more!
That's why I wasn't sure if I might be high or dead. I am completely dumbfounded by what's occurring here. -.-
Sent from my Nexus 7 (2013) running 4.4
Click to expand...
Click to collapse
Wow! Are you there's no cameras outside your window, shooting for the next Twilight Zone movie?
The only thing I can think of is using a Toolkit like WugFresh and see if that works, other than that, I'm at a total loss.
Sent from my Nexus 7 (2013)

Oh~ ho! I have also tried Wugfresh and ADB Sideload from within TWRP; same thing occurs.
I've also moved the zip to the device from Windows Explorer to the root directory, but when I reboot to recovery to install from TWRP the file is no longer there! >_<
Sent from my Nexus 7 (2013) running 4.4

limbonik said:
Oh~ ho! I have also tried Wugfresh and ADB Sideload from within TWRP; same thing occurs.
I've also moved the zip to the device from Windows Explorer to the root directory, but when I reboot to recovery to install from TWRP the file is no longer there! >_<
Sent from my Nexus 7 (2013) running 4.4
Click to expand...
Click to collapse
I've got exactly the same problem. N7 (2012) which is constantly booting into the same state. The same apps try to update themselves from the play store, the same screen etc etc.
I've tried the basic factory reset from the menus - when it reboots nothing has changed. I've removed the other user account from the N7 that I keep locked for work use. It seems to disappear, but when I reboot its there again. I've tried booting into recovery mode, selecting "wipe data/format" (or whatever it says), it says that has gone OK, then it reboots and nothing has been changed / deleted - its still in the same state.
I've rebooted into fastboot mode and used WUGS toolkit to flash stock + unroot in the soft-brick / bootloop mode (both with the force flash option on and off), they both report it is working fine, reboots and there are absolutely no changes at all made to the device.
I turn wifi off, reboot and wifi is back on again. I enable developer options / usb debugging, reboot and they are gone again. Its as if some part of the flash storage has gone completely unwritable, but what is really odd is that whilst the device is on, it behaves as if things are changing - apps appear to update, and be installed, options get changed etc. But nothing at all "sticks" after a reboot! Plus I am lucky if the device stays booted for more than a couple of minutes, it is constantly self--rebooting.
Did you ever find a fix for this, its driving me mad!!
Matt
(Edit - placed a call to google support, and they are sending me a replacement - despite it being 18 months since purchase! Impressed!!)

larkim said:
I've got exactly the same problem. N7 (2012) which is constantly booting into the same state. The same apps try to update themselves from the play store, the same screen etc etc.
I've tried the basic factory reset from the menus - when it reboots nothing has changed. I've removed the other user account from the N7 that I keep locked for work use. It seems to disappear, but when I reboot its there again. I've tried booting into recovery mode, selecting "wipe data/format" (or whatever it says), it says that has gone OK, then it reboots and nothing has been changed / deleted - its still in the same state.
I've rebooted into fastboot mode and used WUGS toolkit to flash stock + unroot in the soft-brick / bootloop mode (both with the force flash option on and off), they both report it is working fine, reboots and there are absolutely no changes at all made to the device.
I turn wifi off, reboot and wifi is back on again. I enable developer options / usb debugging, reboot and they are gone again. Its as if some part of the flash storage has gone completely unwritable, but what is really odd is that whilst the device is on, it behaves as if things are changing - apps appear to update, and be installed, options get changed etc. But nothing at all "sticks" after a reboot! Plus I am lucky if the device stays booted for more than a couple of minutes, it is constantly self--rebooting.
Did you ever find a fix for this, its driving me mad!!
Matt
(Edit - placed a call to google support, and they are sending me a replacement - despite it being 18 months since purchase! Impressed!!)
Click to expand...
Click to collapse
Now THAT'S support! :thumbup::thumbup:
Sent from my Nexus 7 (2013)

Free Beer to anyone who can help!!!

Free Beer* for anyone who can help!
I have a serious problem with my nexus 7 (2012) which I have been researching and working on for many months now to no avail. For this reason I am offering a free beer to anyone who can help (t's&c's apply)!
Background:
The device has stock 4.2.2 rooted installed along with Multirom which has CM10, paranoid android and Ubuntu (desktop).
All this ran fine for a while. I then noticed that if I made any change to the stock rom, update an app, download an app, change the wallpaper, download a file to any part of the filesystem... that when I rebooted the tablet that change would not be there... The wallpaper would be back as it was or the file simply didn't exist! It was as if the filesystem was mounted as non - persistent.
So I tried the other rooms on the tablet and realised they would not boot. All except Ubuntu which was working fine however doesn't mount the internal storage so I couldn't test any further.
I attempted to re flash back to stock. Using flashboot I cleared the cache, system, user data etc and had no errors and then flashed the stock rom. After rebooting my old system appeared to my surprise.
I have tried since then to re flash everything. Recovery won't update (currently TWRP) and the only time I get any error message is when trying to re flash the bootloader which is currently 4.18, everything seems to go well and then "signature match" appears on the tablet screen and it hangs leaving an error in the fastboot terminal reading "Remote: ()"
If anyone can help me fix this issue then the beer is yours... The only stipulation is you have to be in Ireland to claim it but what better excuse for a holiday
Thanks in advance.
Kieran

I have just used Wug's Toolkit to "Flash Stock + Unroot"
Below is th terminal output:
Code:
Flash Stock + Unroot...
--------------------------------------------------------------
erasing 'boot'...
OKAY [ 0.020s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'recovery'...
OKAY [ 0.020s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.020s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.030s]
finished. total time: 0.030s
sending 'bootloader' (2096 KB)...
OKAY [ 0.270s]
writing 'bootloader'...
OKAY [ 0.590s]
finished. total time: 0.860s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.18
Baseband Version.....: N/A
Serial Number........: 015d21d914481613
--------------------------------------------
checking product...
OKAY [ 0.040s]
checking version-bootloader...
OKAY [ 0.020s]
sending 'boot' (4944 KB)...
OKAY [ 0.610s]
writing 'boot'...
OKAY [ 0.160s]
sending 'recovery' (5446 KB)...
OKAY [ 0.670s]
writing 'recovery'...
OKAY [ 0.180s]
erasing 'system'...
OKAY [ 0.020s]
sending 'system' (471804 KB)...
OKAY [ 55.586s]
writing 'system'...
OKAY [ 20.822s]
erasing 'userdata'...
OKAY [ 0.030s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 bloc
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [ 24.063s]
erasing 'cache'...
OKAY [ 0.010s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [ 1.580s]
rebooting...
finished. total time: 103.951s
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...
I used the same stock rom I am using so I ddn't have to flash the bootloader which is an issue (see above).
I can't see any errors in that terminal, everything looks fine but when the tablet reboots it has not changed a single thing!! Multirom is still there as it was and my old rom and userdata and everything down to the crappy wallpaper I put on 8 months ago is still there!!
Can anyone PLEASE HELP!!!

So what do you want to do? Get rid of the multirom and get back to stock? If so do you care about your data?

kilometers4 said:
So what do you want to do? Get rid of the multirom and get back to stock? If so do you care about your data?
Click to expand...
Click to collapse
Exactly that! Don't care about data, just want a stock working image.

I'm having the exact same issue. Tablet reboots after 5 seconds after the lock screen loads so I thought I'd erase user data and re flash the rom. Except that it doesn't actually flash, or erase anything. I've tried toolkits and fastboot. And the log always says the flash has performed successfully but it always reboots to the same old rom, wallpaper, all data still intact.
It's almost like the partitions are write protected and won't allow any data changes.
If anyone can help with this issue, I'll double the free beer offer!
Sent from my iPhone using Tapatalk

mattsolberg said:
I'm having the exact same issue. Tablet reboots after 5 seconds after the lock screen loads so I thought I'd erase user data and re flash the rom. Except that it doesn't actually flash, or erase anything. I've tried toolkits and fastboot. And the log always says the flash has performed successfully but it always reboots to the same old rom, wallpaper, all data still intact.
It's almost like the partitions are write protected and won't allow any data changes.
If anyone can help with this issue, I'll double the free beer offer!
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Can I just ask, are you using multirom aswell? Your the only other person I've heard of with the problem, we should go more notes and try and narrow this down.

No multi-rom. I've found about a half dozen other threads with people experiencing the same thing. It's rare, but it's not just me. Being completely unable to wipe data has me thinking there might be a hardware issue at play.
I'll post links to some of the other threads. Thanks for offering to help. I'm willing to try anything at this point.
Sent from my iPhone using Tapatalk
---------- Post added at 01:00 PM ---------- Previous post was at 12:57 PM ----------
Four other threads describing the exact same problem:
http://forum.xda-developers.com/showthread.php?t=2588911
http://forum.xda-developers.com/showthread.php?t=2585440
http://forum.xda-developers.com/showthread.php?t=2514148
http://forum.xda-developers.com/showthread.php?t=1781250
Sent from my iPhone using Tapatalk

Can't flash my system

Hey,
one day my phone suddenly stopped working properly so i rebooted it. But instead of rebooting it had a bootloop.
I erased the whole phone and tried to flash the stock image but I get the following errors:
Code:
sending 'bootloader' (2203 KB)...
OKAY [ 0.109s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.125s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
< waiting for device >
sending 'radio' (45537 KB)...
OKAY [ 1.782s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 1.798s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'tos.img'
Creating filesystem with parameters:
Size: 14129561600
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3449600
Block groups: 106
Reserved block group size: 847
Created filesystem with 11/863264 inodes and 95427/3449600 blocks
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
--------------------------------------------
Bootloader Version...: MAKOZ30d
Baseband Version.....: M9615A-CEFWMAZM-2.0.1701.03
Serial Number........: XXXXXXXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.000s]
checking version-baseband...
OKAY [ 0.016s]
sending 'boot' (6366 KB)...
OKAY [ 0.250s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 0.343s
Press any key to exit...
Now I can not boot the phone or even open recovery mode...
What should I do? Is my Phone bricked? Can I repair it?
Hope you guys will help me.
Thank you for every hint

Seems like bad eMMC. RMA if the phone's under 2 years.

DrFredPhD said:
Seems like bad eMMC. RMA if the phone's under 2 years.
Click to expand...
Click to collapse
Is it for me possible to change the eMMC?
If yes where can I buy one ?

Forget about it. eMMC is a BGA part, you need professional tools or a lot of luck to change one at home successfully. If you could get a new motherboard it would be better, but I don't recommend it as a new motherboard would come blank or clone IMEI and you have no way of changing it to original one, and a used motherboard may have other problems/barred IMEI.

DrFredPhD said:
Forget about it. eMMC is a BGA part, you need professional tools or a lot of luck to change one at home successfully. If you could get a new motherboard it would be better, but I don't recommend it as a new motherboard would come blank or clone IMEI and you have no way of changing it to original one, and a used motherboard may have other problems/barred IMEI.
Click to expand...
Click to collapse
So what should I do now?
My phone is older than 2 years...

You could try follow this guide, but I don't think it will help (it's mainly for people who don't have working bootloader mode). http://forum.xda-developers.com/showthread.php?t=2347060
Failing that, new phone time. Moto G has similar specs at a good price.

Nexus 10: Stuck in Reboot, Tried Flashing Stock ROM With Error

Infinite reboot problem
I need help, my nexus has been continously rebooting by itself. It starts, goes to my homescreen for a few seconds and reboots. I can boot in the bootloader and have tried to do a factory reset, but it just stays a long time in formatting data. After waiting a complete day I decided to stop the process and start again my tablet. It just went to my home screen and again it kept rebooting. It didn't wipe anything.
Next I tried to fastboot flash a stock image, it never gave me any kind of error. My tablet rebooted, but it just went to my home screen, and clearly the image wasn't installed. And again it started the rebooting process.
C:\Users\Username\Downloads\fastboot>fastboot flash bootloader bootloader-manta-mantamf01.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.156s]
writing 'bootloader'...
OKAY [ 0.203s]
finished. total time: 0.359s
C:\Users\Username\Downloads\fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Users\Username\Downloads\fastboot>fastboot -w update image-mantaray-lmy48x.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 29783752704
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7271424
Block groups: 222
Reserved block group size: 1024
Created filesystem with 11/1818624 inodes and 158176/7271424 blocks
Creating filesystem with parameters:
Size: 553648128
Block size: 4096
Blocks per group: 32768
Inodes per group: 6768
Inode size: 256
Journal blocks: 2112
Label:
Blocks: 135168
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/33840 inodes and 4363/135168 blocks
--------------------------------------------
Bootloader Version...: MANTAMF01
Baseband Version.....: no modem
Serial Number........: R32CB03FJ1P
--------------------------------------------
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ -0.000s]
sending 'boot' (4982 KB)...
OKAY [ 0.626s]
writing 'boot'...
OKAY [ 0.016s]
sending 'recovery' (5548 KB)...
OKAY [ 0.688s]
writing 'recovery'...
OKAY [ 0.016s]
erasing 'system'...
OKAY [ 0.016s]
sending 'system' (656930 KB)...
OKAY [ 80.289s]
writing 'system'...
OKAY [ 5.318s]
erasing 'userdata'...
OKAY [ 0.020s]
sending 'userdata' (139141 KB)...
OKAY [ 16.687s]
writing 'userdata'...
OKAY [ 1.162s]
erasing 'cache'...
OKAY [ 0.016s]
sending 'cache' (10372 KB)...
OKAY [ 1.266s]
writing 'cache'...
OKAY [ 0.094s]
rebooting...
finished. total time: 106.464s
Click to expand...
Click to collapse
Also, I tried to re-lock the bootloader with fastboot oem lock, it said Ok, but the status didn't change (I have a warranty and I think is time to use it, but I need to lock the bootloader). Thanks in advance for your help.
C:\Users\Username\Downloads\fastboot>fastboot oem lock
...
OKAY [ -0.000s]
finished. total time: -0.000s
Click to expand...
Click to collapse

Uldar said:
I need help, my nexus has been continously rebooting by itself. It starts, goes to my homescreen for a few seconds and reboots. I can boot in the bootloader and have tried to do a factory reset, but it just stays a long time in formatting data. After waiting a complete day I decided to stop the process and start again my tablet. It just went to my home screen and again it kept rebooting. It didn't wipe anything.
Next I tried to fastboot flash a stock image, it never gave me any kind of error. My tablet rebooted, but it just went to my home screen, and clearly the image wasn't installed. And again it started the rebooting process.
Also, I tried to re-lock the bootloader with fastboot oem lock, it said Ok, but the status didn't change (I have a 3 year warranty that will expire this december, and I think is time to use it, but I need to lock the bootloader). Thanks in advance for your help.
Click to expand...
Click to collapse
Hello, did you try to boot on a custom recovery ?
fastboot boot recovery x.img will work.
From there you might try formatting / installing a custom rom.

Khaon said:
Hello, did you try to boot on a custom recovery ?
fastboot boot recovery x.img will work.
From there you might try formatting / installing a custom rom.
Click to expand...
Click to collapse
Yeah, I tried to do a factory reset with twrp, but it didn't work. It stays a long time in formatting cache using make_ext4fs function and doesn't make any progress. I left it like that for 6 hours after I decided to finish the process. It started again, went to my homescreen and kept rebooting.

Uldar said:
[/HIDE]
Yeah, I tried to do a factory reset with twrp, but it didn't work. It stays a long time in formatting cache using make_ext4fs function and doesn't make any progress. I left it like that for 6 hours after I decided to finish the process. It started again, went to my homescreen and kept rebooting.
Click to expand...
Click to collapse
What is the output of " adb shell dmesg" when you are inside the recovery mode ?

Seems that most likey your eMMC is dead.
timed out sending SET_BLOCK_COUNT command, card status 0x400d00
Click to expand...
Click to collapse
You could try formatting with f2fs but fi you already tried unlock/lock I don't think it will helpas it erase the whole storage.

Khaon said:
Seems that most likey your eMMC is dead.
You could try formatting with f2fs but fi you already tried unlock/lock I don't think it will helpas it erase the whole storage.
Click to expand...
Click to collapse
Thanks a lot for your help, I'm going to send it under warranty and see if they can fix it. I hope they don't reject it because the bootloader is unlocked.

PIT files
My nexus 10 has the boot loop problem and I think I have been left with the only option of Re-Partition but I need the PIT file. Can anybody help or provide this file?
I have tried everything else (fastboot, adb, temporary custom recoveries, Nexus Root Toolkit) with no success.

Soft bricked really hard

Hey guys, I've done something wonky in TWRP and simply cant get a clean factory imagine installed. I feel like ive tried everything and am now coming here in an attempt to get some help.
At this point, I am stuck at the Google logo booting indefinitely. When I flash the latest TWRP recovery and go into it, im pretty locked down in what I can do. I cant get ANYTHING to mount, it vibrates but wont let me mount anything.
When I go into advanced wipe settings in an attempt to repair partitions there is NO system or Data present and will not let me repair. When I do repair system, i get "/sbin/efsck -fp process ended with ERROR: 16 unable to repair system" Googling brings me nothing on error 16.
Despite trying to flash a multitude of different factory images through both WugFresh and Fastboot commands I havent been able to stick. I cant even wipe/factory reset in stock recovery.
I've attempted "fastboot format userdata" as well as flashing the modified boot.img to bypass encryption (not sure how this works?) But to no avail.
Could anyone help me diagnose this a bit? Help would be greatly appreciated.

tcardozo said:
Hey guys, I've done something wonky in TWRP and simply cant get a clean factory imagine installed. I feel like ive tried everything and am now coming here in an attempt to get some help.
At this point, I am stuck at the Google logo booting indefinitely. When I flash the latest TWRP recovery and go into it, im pretty locked down in what I can do. I cant get ANYTHING to mount, it vibrates but wont let me mount anything.
When I go into advanced wipe settings in an attempt to repair partitions there is NO system or Data present and will not let me repair. When I do repair system, i get "/sbin/efsck -fp process ended with ERROR: 16 unable to repair system" Googling brings me nothing on error 16.
Despite trying to flash a multitude of different factory images through both WugFresh and Fastboot commands I havent been able to stick. I cant even wipe/factory reset in stock recovery.
I've attempted "fastboot format userdata" as well as flashing the modified boot.img to bypass encryption (not sure how this works?) But to no avail.
Could anyone help me diagnose this a bit? Help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried flashing stock?
P. S. Reading your post, I feel like you don't have much knowledge of what you're doing and especially how the things work on your Nexus. But don't worry that is nothing to be ashamed of, all of us here have been through that stage. So once we have resolved your issue, I would advise you to read the stickies in different sections of the 6P.

DJBhardwaj said:
Have you tried flashing stock?
P. S. Reading your post, I feel like you don't have much knowledge of what you're doing and especially how the things work on your Nexus. But don't worry that is nothing to be ashamed of, all of us here have been through that stage. So once we have resolved your issue, I would advise you to read the stickies in different sections of the 6P.
Click to expand...
Click to collapse
Hey there, thanks for chiming in.
Despite my hastily typed out response, I have a relatively good idea of what I am doing, though I know I am no power user.
I have attempted to flash stock. I started with MTC20F once I realized I was having problems. After that failed to boot, I downloaded MTC 19X and attempted to flash that. I first started with going through Nexus Toolkit to get it up and running but that still left me at the Google logo after booting. Wondering what was up, I threw in TWRP as a means of taking a look at my partitions after the stock install which is when I realized something was fishy. Nothing is able to be mounted, repaired or resized and TWRP is telling me that both /system and /data are not present directly after reinstalling Stock. and said their size is 0mb. Essentially it seems no internal memory is being detected at all.
Also I am prompted that there is no OS installed when i go to exit recovery, despite having just flashed it.
The problem I am having seems quite simple, but makes no sense to me.

tcardozo said:
Hey there, thanks for chiming in.
Despite my hastily typed out response, I have a relatively good idea of what I am doing, though I know I am no power user.
I have attempted to flash stock. I started with MTC20F once I realized I was having problems. After that failed to boot, I downloaded MTC 19X and attempted to flash that. I first started with going through Nexus Toolkit to get it up and running but that still left me at the Google logo after booting. Wondering what was up, I threw in TWRP as a means of taking a look at my partitions after the stock install which is when I realized something was fishy. Nothing is able to be mounted, repaired or resized and TWRP is telling me that both /system and /data are not present directly after reinstalling Stock. and said their size is 0mb. Essentially it seems no internal memory is being detected at all.
Also I am prompted that there is no OS installed when i go to exit recovery, despite having just flashed it.
The problem I am having seems quite simple, but makes no sense to me.
Click to expand...
Click to collapse
Okay, I am guessing you missed something out while flashing stock. Plus, avoid toolkits for now.
Now, try re-installing stock from the steps mentioned here: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page1
Or to be simple, extract the factory image, and use flash-all.bat file on your PC. Let me know the results.

DJBhardwaj said:
Okay, I am guessing you missed something out while flashing stock. Plus, avoid toolkits for now.
Now, try re-installing stock from the steps mentioned here: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page1
Or to be simple, extract the factory image, and use flash-all.bat file on your PC. Let me know the results.
Click to expand...
Click to collapse
So I opted to go through Heisenberg's tutorial so I knew if anything happened at each step, and also locked the bootloader again after.
After going through all the steps with the MTC20F factory image (verified), it takes me right to the stock recovery with the android on his back after showing me the google logo.
Edit: it seems to be staying in stock recovery for a short period of time before going through a boot cycle continuously.
Edit2: When I go into recovery, it wont let me "apply update from SD card" or "wipe data/factory reset" or "wipe cache" It says:
Can't open /dev/block/platform/soc.0/f9824900.sdhci/by-name/misc (no such file or directory)
E: failed to mount /cache (no such file or directory)
E:unknown volume for path [/sdcard]
followed by a series of errors about not being able to mount other parts

tcardozo said:
So I opted to go through Heisenberg's tutorial so I knew if anything happened at each step, and also locked the bootloader again after.
After going through all the steps with the MTC20F factory image (verified), it takes me right to the stock recovery with the android on his back after showing me the google logo
Click to expand...
Click to collapse
To be safe, keep the bootloader unlocked. As for flashing stock, try the flash-all.bat script. Just a try, and let me know.
One more thing, you flashed the correct vendor image, right?

DJBhardwaj said:
To be safe, keep the bootloader unlocked. As for flashing stock, try the flash-all.bat script. Just a try, and let me know.
One more thing, you flashed the correct vendor image, right?
Click to expand...
Click to collapse
unlocked the bootloader again. Double checked and the vendor image is directly from the factory image. Went ahead and used the flash-all.bat and came to the same result; shows Google logo for about 20 seconds then right into stock recovery.
Also check my edits above about weird behaviour.

tcardozo said:
unlocked the bootloader again. Double checked and the vendor image is directly from the factory image. Went ahead and used the flash-all.bat and came to the same result; shows Google logo for about 20 seconds then right into stock recovery.
Also check my edits above about weird behaviour.
Click to expand...
Click to collapse
The above errors that mentioned probably indicate that your partition table is the culprit here. The stock factory image should have done it already. Might want to check out the service centre?

DJBhardwaj said:
The above errors that mentioned probably indicate that your partition table is the culprit here. The stock factory image should have done it already. Might want to check out the service centre?
Click to expand...
Click to collapse
Thanks for the advice. Unfortunately I'm located in Bangkok, Thailand, without an adequate service centre around that can help with Nexus devices.

Could you post out the complete log when the factory image is being flashed?
---------- Post added at 12:11 AM ---------- Previous post was at 12:09 AM ----------
tcardozo said:
Thanks for the advice. Unfortunately I'm located in Bangkok, Thailand, without an adequate service centre around that can help with Nexus devices.
Click to expand...
Click to collapse
I could see, there is one there: http://consumer.huawei.com/en/support/service-center/index.htm

DJBhardwaj said:
Could you post out the complete log when the factory image is being flashed?
How can I grab the log?
Click to expand...
Click to collapse

tcardozo said:
DJBhardwaj said:
Could you post out the complete log when the factory image is being flashed?
How can I grab the log?
Click to expand...
Click to collapse
Once the flashing is done, you just copy down the complete content of the CMD window, or Terminal, if you're using Linux or Mac.
Click to expand...
Click to collapse

deleted

DJBhardwaj said:
tcardozo said:
Once the flashing is done, you just copy down the complete content of the CMD window, or Terminal, if you're using Linux or Mac.
Click to expand...
Click to collapse
target reported max download size of 494927872 bytes
sending 'bootloader' (3526 KB)...
OKAY [ 0.104s]
writing 'bootloader'...
OKAY [ 0.203s]
finished. total time: 0.309s
rebooting into bootloader...
OKAY [ 0.144s]
finished. total time: 0.145s
target reported max download size of 494927872 bytes
sending 'radio' (48600 KB)...
OKAY [ 1.061s]
writing 'radio'...
OKAY [ 2.168s]
finished. total time: 3.231s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.009s
target reported max download size of 494927872 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 58688266240
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14328190
Block groups: 438
Reserved block group size: 1024
Created filesystem with 11/3588096 inodes and 271280/14328190 blocks
wiping cache...
Creating filesystem with parameters:
Size: 104857600
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 25600
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6400 inodes and 1438/25600 blocks
--------------------------------------------
Bootloader Version...: angler-03.54
Baseband Version.....: angler-03.61
Serial Number........: CVH7N16126000684
--------------------------------------------
checking product...
OKAY [ 0.020s]
checking version-bootloader...
OKAY [ 0.020s]
checking version-baseband...
OKAY [ 0.019s]
sending 'boot' (12201 KB)...
OKAY [ 0.288s]
writing 'boot'...
OKAY [ 0.181s]
sending 'recovery' (13133 KB)...
OKAY [ 0.298s]
writing 'recovery'...
OKAY [ 0.201s]
erasing 'system'...
OKAY [ 0.422s]
sending sparse 'system' 1/5 (478162 KB)...
OKAY [ 10.776s]
writing 'system' 1/5...
OKAY [ 6.765s]
sending sparse 'system' 2/5 (482961 KB)...
OKAY [ 10.917s]
writing 'system' 2/5...
OKAY [ 6.987s]
sending sparse 'system' 3/5 (480085 KB)...
OKAY [ 10.834s]
writing 'system' 3/5...
OKAY [ 7.450s]
sending sparse 'system' 4/5 (470078 KB)...
OKAY [ 10.611s]
writing 'system' 4/5...
OKAY [ 6.434s]
sending sparse 'system' 5/5 (55832 KB)...
OKAY [ 1.321s]
writing 'system' 5/5...
OKAY [ 0.797s]
sending 'vendor' (185181 KB)...
OKAY [ 3.997s]
writing 'vendor'...
(eventually this finishes, but I cant copy the final finished text because it closes the winow)
Click to expand...
Click to collapse

tcardozo said:
DJBhardwaj said:
target reported max download size of 494927872 bytes
sending 'bootloader' (3526 KB)...
OKAY [ 0.104s]
writing 'bootloader'...
OKAY [ 0.203s]
finished. total time: 0.309s
rebooting into bootloader...
OKAY [ 0.144s]
finished. total time: 0.145s
target reported max download size of 494927872 bytes
sending 'radio' (48600 KB)...
OKAY [ 1.061s]
writing 'radio'...
OKAY [ 2.168s]
finished. total time: 3.231s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.009s
target reported max download size of 494927872 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 58688266240
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14328190
Block groups: 438
Reserved block group size: 1024
Created filesystem with 11/3588096 inodes and 271280/14328190 blocks
wiping cache...
Creating filesystem with parameters:
Size: 104857600
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 25600
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6400 inodes and 1438/25600 blocks
--------------------------------------------
Bootloader Version...: angler-03.54
Baseband Version.....: angler-03.61
Serial Number........: CVH7N16126000684
--------------------------------------------
checking product...
OKAY [ 0.020s]
checking version-bootloader...
OKAY [ 0.020s]
checking version-baseband...
OKAY [ 0.019s]
sending 'boot' (12201 KB)...
OKAY [ 0.288s]
writing 'boot'...
OKAY [ 0.181s]
sending 'recovery' (13133 KB)...
OKAY [ 0.298s]
writing 'recovery'...
OKAY [ 0.201s]
erasing 'system'...
OKAY [ 0.422s]
sending sparse 'system' 1/5 (478162 KB)...
OKAY [ 10.776s]
writing 'system' 1/5...
OKAY [ 6.765s]
sending sparse 'system' 2/5 (482961 KB)...
OKAY [ 10.917s]
writing 'system' 2/5...
OKAY [ 6.987s]
sending sparse 'system' 3/5 (480085 KB)...
OKAY [ 10.834s]
writing 'system' 3/5...
OKAY [ 7.450s]
sending sparse 'system' 4/5 (470078 KB)...
OKAY [ 10.611s]
writing 'system' 4/5...
OKAY [ 6.434s]
sending sparse 'system' 5/5 (55832 KB)...
OKAY [ 1.321s]
writing 'system' 5/5...
OKAY [ 0.797s]
sending 'vendor' (185181 KB)...
OKAY [ 3.997s]
writing 'vendor'...
(eventually this finishes, but I cant copy the final finished text because it closes the winow)
Click to expand...
Click to collapse
Seems like it is flashing fine. I am out of clues now. Would still recommend you to go to the nearest service centre.
Click to expand...
Click to collapse