Soft Bricked Nexus 6P - Nexus 6P Q&A, Help & Troubleshooting

Okay...So I feel like a complete ID10T (IDIOT). I managed to Soft Brick Nexus 6P. Currently it goes between the white Google Logo with the unlock icon at the bottom and the "Your device software cannot be check for corruption Please lock the Bootloader." Image. I have tried using WUGFresh Toolkit to flash the files as well as just using the factory image to no avail.
I can get into TWRP but even when flashing CM13 it just sits at the white Google logo and does not continue.
Does anyone have any suggestions?

Perhaps try manually flashing factory instead of using wugfresh's toolkit. I had a similar situation and that's what got me lot of my jam, but that may have been because wugfresh's kit wasn't updated for all the marshmallow shenanigans. So make sure you're on the latest version too

jasonftfw said:
Perhaps try manually flashing factory instead of using wugfresh's toolkit. I had a similar situation and that's what got me lot of my jam, but that may have been because wugfresh's kit wasn't updated for all the marshmallow shenanigans. So make sure you're on the latest version too
Click to expand...
Click to collapse
I tried that as well. I installed the Android SDK and put the angler-mmb29m-factory-8c31db3f files in adb folder on that's on the root of C:\ and ran the flash-all.bat. It goes though the process but I still get the same bootlooping issue.
C:\adb>fastboot devices
8XV5T15B10000200 fastboot
C:\adb>flash-all
target reported max download size of 494927872 bytes
sending 'bootloader' (3526 KB)...
OKAY [ 0.137s]
writing 'bootloader'...
OKAY [ 0.208s]
finished. total time: 0.347s
rebooting into bootloader...
OKAY [ 0.125s]
finished. total time: 0.126s
target reported max download size of 494927872 bytes
sending 'radio' (48472 KB)...
OKAY [ 1.611s]
writing 'radio'...
OKAY [ 2.170s]
finished. total time: 3.782s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.017s
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'
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
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-02.45
Baseband Version.....: angler-02.50
Serial Number........: MY SN
--------------------------------------------
checking product...
OKAY [ 0.020s]
checking version-bootloader...
OKAY [ 0.020s]
checking version-baseband...
OKAY [ 0.018s]
sending 'boot' (12045 KB)...
OKAY [ 0.428s]
writing 'boot'...
OKAY [ 0.184s]
sending 'recovery' (12981 KB)...
OKAY [ 0.453s]
writing 'recovery'...
OKAY [ 0.192s]
erasing 'system'...
OKAY [ 0.402s]
sending sparse 'system' (463062 KB)...
OKAY [ 15.904s]
writing 'system'...
OKAY [ 6.511s]
sending sparse 'system' (466961 KB)...
OKAY [ 16.220s]
writing 'system'...
OKAY [ 6.804s]
sending sparse 'system' (479253 KB)...
OKAY [ 17.006s]
writing 'system'...
OKAY [ 7.519s]
sending sparse 'system' (481623 KB)...
OKAY [ 16.713s]
writing 'system'...
OKAY [ 6.772s]
sending sparse 'system' (79148 KB)...
OKAY [ 2.786s]
writing 'system'...
OKAY [ 1.134s]
sending 'vendor' (185129 KB)...
OKAY [ 6.096s]
writing 'vendor'...
OKAY [ 3.017s]
erasing 'userdata'...
OKAY [ 1.012s]
sending 'userdata' (141002 KB)...
OKAY [ 4.674s]
writing 'userdata'...
OKAY [ 2.135s]
erasing 'cache'...
OKAY [ 0.091s]
sending 'cache' (5752 KB)...
OKAY [ 0.228s]
writing 'cache'...
OKAY [ 0.107s]
rebooting...
finished. total time: 116.562s
Press any key to exit...
Click to expand...
Click to collapse

I literally mean flash manual, like type it all out, I had issues with the flash all too

jasonftfw said:
I literally mean flash manual, like type it all out, I had issues with the flash all too
Click to expand...
Click to collapse
Thanks! I will try that and report back.
I tried manually typing out all the commands and it still just bootlooping at the Google logo. It will show it for about 22 seconds and then go black for 4 seconds. Any other suggestions?

What exactly did you do to softbrick it ?
If you connect with ADB, can you dump a log while booting ?
If not: what I'd try is do a factory reset, try a boot, when it loops, boot into TWRP. Then check if there's a log in /data/tombstones

gekkehenkie11 said:
What exactly did you do to softbrick it ?
If you connect with ADB, can you dump a log while booting ?
If not: what I'd try is do a factory reset, try a boot, when it loops, boot into TWRP. Then check if there's a log in /data/tombstones
Click to expand...
Click to collapse
Well when I received it, it was on 6.0.0 (MDB08L) so I rooted it and installed xposed framework. I was trying to install the OTA update for 6.0.1 and of course it failed with TWRP, so I decided I would just factory reset and start over and that was where the problem start. Once I rebooted it started bootlooping and has been doing so every since.

mxjcmxjc said:
Well when I received it, it was on 6.0.0 (MDB08L) so I rooted it and installed xposed framework. I was trying to install the OTA update for 6.0.1 and of course it failed with TWRP, so I decided I would just factory reset and start over and that was where the problem start. Once I rebooted it started bootlooping and has been doing so every since.
Click to expand...
Click to collapse
Hmm wish I knew a way how to help you but if you flashed all partitions to factory and also did a factory reset and if that still doesnt help, then I'd be out of idea's. I'd try to dump logs like I said in my previous posts, maybe there's something in there but still, it doesn't make any sense to me, so I doubt there's something in the logs to go by but who knows. ..
Maybe though it's encryption related ? I'm still a bit confused myself there how all that fits in.

gekkehenkie11 said:
Hmm wish I knew a way how to help you but if you flashed all partitions to factory and also did a factory reset and if that still doesnt help, then I'd be out of idea's. I'd try to dump logs like I said in my previous posts, maybe there's something in there but still, it doesn't make any sense to me, so I doubt there's something in the logs to go by but who knows. ..
Maybe though it's encryption related ? I'm still a bit confused myself there how all that fits in.
Click to expand...
Click to collapse
I checked the Tombstone folder and found 10 files there. Here is the link to the dumps. I really hope it helps.

mxjcmxjc said:
I checked the Tombstone folder and found 10 files there. Here is the link to the dumps. I really hope it helps.
Click to expand...
Click to collapse
Your error is "couldn't find an OpenGL ES implementation". So what we know:
1) The kernel boots
2) System image loads, it runs libEGL.so, this lib is in your system image.
3) libEGL.so tries to access the OpenGL implementation. This stuff is located in the vendor partition. And this is where it goes wrong. It says it cant find that file. What this means ? Not really sure. It could mean that the vendor partition is not good, maybe try to flash it again ? Also, what happens if you try to make a logcat during boot ? Issue:
adb logcat > out.txt
And see if it saves something after the bootloop. Maybe there's a better hint in there.
*EDIT2* also see if the openGL implementation is even there ! It should look like this:
[email protected]:/vendor/lib64/egl # ls -al
-rw-r--r-- root root 47200 2009-01-01 04:00 eglSubDriverAndroid.so
-rw-r--r-- root root 103256 2009-01-01 04:00 libEGL_adreno.so
-rw-r--r-- root root 210776 2009-01-01 04:00 libGLESv1_CM_adreno.so
-rw-r--r-- root root 7288296 2009-01-01 04:00 libGLESv2_adreno.so
-rw-r--r-- root root 661552 2009-01-01 04:00 libq3dtools_adreno.so
-rw-r--r-- root root 361800 2009-01-01 04:00 libq3dtools_esx.so
[email protected]:/vendor/lib64/egl #

gekkehenkie11 said:
Your error is "couldn't find an OpenGL ES implementation". So what we know:
1) The kernel boots
2) System image loads, it runs libEGL.so, this lib is in your system image.
3) libEGL.so tries to access the OpenGL implementation. This stuff is located in the vendor partition. And this is where it goes wrong. It says it cant find that file. What this means ? Not really sure. It could mean that the vendor partition is not good, maybe try to flash it again ? Also, what happens if you try to make a logcat during boot ? Issue:
adb logcat > out.txt
And see if it saves something after the bootloop. Maybe there's a better hint in there.
*EDIT2* also see if the openGL implementation is even there ! It should look like this:
[email protected]:/vendor/lib64/egl # ls -al
-rw-r--r-- root root 47200 2009-01-01 04:00 eglSubDriverAndroid.so
-rw-r--r-- root root 103256 2009-01-01 04:00 libEGL_adreno.so
-rw-r--r-- root root 210776 2009-01-01 04:00 libGLESv1_CM_adreno.so
-rw-r--r-- root root 7288296 2009-01-01 04:00 libGLESv2_adreno.so
-rw-r--r-- root root 661552 2009-01-01 04:00 libq3dtools_adreno.so
-rw-r--r-- root root 361800 2009-01-01 04:00 libq3dtools_esx.so
[email protected]:/vendor/lib64/egl #
Click to expand...
Click to collapse
I'm not getting any output from logcat when trying to boot it seems.
I just sit there like this.
C:\adb>adb logcat > out.txt
- waiting for device -

mxjcmxjc said:
I'm not getting any output from logcat when trying to boot it seems.
I just sit there like this.
C:\adb>adb logcat > out.txt
- waiting for device -
Click to expand...
Click to collapse
Ok so it's not getting to that point, which makes sense I realize now, since first thing it does is trying to get display up (it's not even getting beyond that).
So, let's see if your vendor partition seems correct. boot into TWRP, connect via 'adb shell', then 'mount /vendor' and then:
Code:
ls -al /vendor/lib64/egl
and see if all the files are there that I listed in my post on the previous page of this thread

I'm having the same issue. I stupidly tried to flash the OTA update via TWRP and now the phone won't go past the Google logo. Even when I restore my backup, it still won't go past that screen.
I didn't back up the vendor partition though (didn't know that I needed to).
My phone was not rooted. All I had was the custom recovery so that I can install MoaAB.
Now I have to wait until tomorrow because my USB C to USB A cable is at work. Hopefully we can get this fixed soon.

gekkehenkie11 said:
Ok so it's not getting to that point, which makes sense I realize now, since first thing it does is trying to get display up (it's not even getting beyond that).
So, let's see if your vendor partition seems correct. boot into TWRP, connect via 'adb shell', then 'mount /vendor' and then:
Code:
ls -al /vendor/lib64/egl
and see if all the files are there that I listed in my post on the previous page of this thread
Click to expand...
Click to collapse
Sorry for the late reply...
Yes the files are there. I was able to mount the vendor partition in TWRP and then use the File Manager to see the directory.
https://www.dropbox.com/s/3yq97hs75me933m/IMG_20151211_002153.jpg?dl=0
Just another detail. Whenever I restarted the device prior to bootlooping. I would have to enter my pattern before Android would start.

Closed at OP's request.

Related

[Q] Updated Nexus 4 with Android 4.4 Factory image. Only seeing boot animation

Hello,
My name is Rahul. This is the first time I am posting.
I flashed the latest factory image for Android Kitkat onto the Nexus 4. the image was occam KRT16O. I followed the instructions and used fastboot on mac and ran the flash-all.sh script that was provided.
The log of the script was as indicated below and the device rebooted. However, it was stuck in the boot animation for a long time.
What can I do next? The options I can consider are:
1. force reboot the nexus 4 by holding the power button [if that would work] and flashing the image again.
2. go to the bootloader (if reboot works) and switch away to the previous ROM (I was using CM and PAC for some time now flashing them nightly) and wait for a new more days.
I would love to try the new factory image for KitKat on my phone and would appreciate if you could provide some direction.
Thanks in advance for your help.
- Rahul
silverbook:Nexus4Root rahul$ ./flash-all.sh
ERROR: could not get pipe properties
sending 'bootloader' (2203 KB)... OKAY
writing 'bootloader'... OKAY
ERROR: could not get pipe properties
rebooting into bootloader... OKAY
sending 'radio' (45537 KB)... OKAY
writing 'radio'... OKAY
rebooting into bootloader... OKAY
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ30d
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.97
Serial Number........: 024443a016985273
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
checking version-baseband... OKAY
sending 'boot' (6336 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (6884 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (700500 KB)... OKAY
writing 'system'... OKAY
erasing 'userdata'... OKAY
erasing 'cache'... OKAY
rebooting...
Rebooted and trying again...fingers crossed.
i would download again, look down in the log and u see that it just erased usersdata partition(it needs to erase and flash userdata.img)
I have the exact same problem, please let me know what what the solution for you.
eran- said:
I have the exact same problem, please let me know what what the solution for you.
Click to expand...
Click to collapse
I opened the zip file image-occam-krt16o.zip and found userdata.img and i used fastboot to flash userdata with that image. I am still waiting for my phone to move ahead from the boot animation...crossed fingers.
rreiki said:
I opened the zip file image-occam-krt16o.zip and found userdata.img and i used fastboot to flash userdata with that image. I am still waiting for my phone to move ahead from the boot animation...crossed fingers.
Click to expand...
Click to collapse
I guess that you, like me, took the wipe flag off the fastboot bat file right?
Well I was told that 4.3 --> 4.4 needs a full wipe so I put that -w back in place and everything works, my 4.4 works
and my phone looks fresher than fresh.
Good luck
opssemnik said:
i would download again, look down in the log and u see that it just erased usersdata partition(it needs to erase and flash userdata.img)
Click to expand...
Click to collapse
opssemnik, I downloaded the file again, unzipped and tried again. It gave me the same log. I then opened the zip which contained user data.img and flashed it and it still waits at the boot animation for a long time. I think its already been twenty minutes.
Is there anything else I can try?
Thanks for your response.
rreiki said:
I opened the zip file image-occam-krt16o.zip and found userdata.img and i used fastboot to flash userdata with that image. I am still waiting for my phone to move ahead from the boot animation...crossed fingers.
Click to expand...
Click to collapse
rreiki said:
opssemnik, I downloaded the file again, unzipped and tried again. It gave me the same log. I then opened the zip which contained user data.img and flashed it and it still waits at the boot animation for a long time. I think its already been twenty minutes.
Is there anything else I can try?
Thanks for your response.
Click to expand...
Click to collapse
Did you fully wiped your device?
eran- said:
Did you fully wiped your device?
Click to expand...
Click to collapse
Yes. The flash-all.sh uses -w which fully wipes the device. I remember reading about -w somewhere.
rreiki said:
Yes. The flash-all.sh uses -w which fully wipes the device. I remember reading about -w somewhere.
Click to expand...
Click to collapse
I am now trying to download the latest adb and fastboot downloading the sdk and will retry flashing the image.
rreiki said:
I am now trying to download the latest adb and fastboot downloading the sdk and will retry flashing the image.
Click to expand...
Click to collapse
okay, interesting observation. I downloaded the new platform-tools (adb/fastboot) and re-ran flash-all.sh. the log looked like the one below.
and my phone started!!!!
silverbook:android rahul$ ./flash-all.sh
sending 'bootloader' (2203 KB)...
OKAY [ 0.115s]
writing 'bootloader'...
OKAY [ 0.287s]
finished. total time: 0.402s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
sending 'radio' (45537 KB)...
OKAY [ 1.889s]
writing 'radio'...
OKAY [ 2.535s]
finished. total time: 4.424s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ30d
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.97
Serial Number........: 024443a016985273
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (6336 KB)...
OKAY [ 0.203s]
writing 'boot'...
OKAY [ 0.339s]
sending 'recovery' (6884 KB)...
OKAY [ 0.235s]
writing 'recovery'...
OKAY [ 0.395s]
erasing 'system'...
OKAY [ 0.690s]
sending 'system' (700500 KB)...
OKAY [ 22.043s]
writing 'system'...
OKAY [ 40.629s]
erasing 'userdata'...
OKAY [ 0.572s]
formatting 'userdata' partition...
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
sending 'userdata' (137438 KB)...
writing 'userdata'...
OKAY [ 13.523s]
erasing 'cache'...
OKAY [ 0.022s]
formatting 'cache' partition...
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
sending 'cache' (10984 KB)...
writing 'cache'...
OKAY [ 1.082s]
rebooting...
finished. total time: 79.749s
I had the same problem, came from PA 3.99 and flashed the kitkat google image and phone got stuck in bootloop. Only way i could fix it was to get the new sdk studio and use the fastboot from that
the last log u gave looks like mine so i guess its ok, but u were using a really outdated adb huh? im using the minimal adb + fastboot from like 6 to 7 months ago(so the fastboot / adb is from that time witch means is old) and i can flash the stock images
rreiki said:
okay, interesting observation. I downloaded the new platform-tools (adb/fastboot) and re-ran flash-all.sh. the log looked like the one below.
and my phone started!!!!
silverbook:android rahul$ ./flash-all.sh
sending 'bootloader' (2203 KB)...
OKAY [ 0.115s]
writing 'bootloader'...
OKAY [ 0.287s]
finished. total time: 0.402s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
sending 'radio' (45537 KB)...
OKAY [ 1.889s]
writing 'radio'...
OKAY [ 2.535s]
finished. total time: 4.424s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ30d
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.97
Serial Number........: 024443a016985273
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (6336 KB)...
OKAY [ 0.203s]
writing 'boot'...
OKAY [ 0.339s]
sending 'recovery' (6884 KB)...
OKAY [ 0.235s]
writing 'recovery'...
OKAY [ 0.395s]
erasing 'system'...
OKAY [ 0.690s]
sending 'system' (700500 KB)...
OKAY [ 22.043s]
writing 'system'...
OKAY [ 40.629s]
erasing 'userdata'...
OKAY [ 0.572s]
formatting 'userdata' partition...
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
sending 'userdata' (137438 KB)...
writing 'userdata'...
OKAY [ 13.523s]
erasing 'cache'...
OKAY [ 0.022s]
formatting 'cache' partition...
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
sending 'cache' (10984 KB)...
writing 'cache'...
OKAY [ 1.082s]
rebooting...
finished. total time: 79.749s
Click to expand...
Click to collapse
I place all files in "platform tools" in the SDK and re-ran flash-all.sh. from there and works!!!! Thanks!
fidozgz said:
I place all files in "platform tools" in the SDK and re-ran flash-all.sh. from there and works!!!! Thanks!
Click to expand...
Click to collapse
can you send your "platform tools" somehow? I downloaded everything today and tried flashing 4.4. Stuck at boot screen. How long did you have to wait before it went past the boot screen?
prongs_rajat said:
can you send your "platform tools" somehow? I downloaded everything today and tried flashing 4.4. Stuck at boot screen. How long did you have to wait before it went past the boot screen?
Click to expand...
Click to collapse
just ask him for the link as of which he got it from probably easier.
Edit: May I ask you guys a question if you skimmed through this forum prior to making a decision to upgrade you would see so many people with the same issue and post day in and day out about flashing images. I am confused as to why those of you want to flash images instead of just flashing through a custom recovery. There is no difference? other than less headaches from what I see
playya said:
just ask him for the link as of which he got it from probably easier.
Edit: May I ask you guys a question if you skimmed through this forum prior to making a decision to upgrade you would see so many people with the same issue and post day in and day out about flashing images. I am confused as to why those of you want to flash images instead of just flashing through a custom recovery. There is no difference? other than less headaches from what I see
Click to expand...
Click to collapse
Yeah I'm kind of a noob. I installed CWM recovery. I boot into recovery and I see a bunch of options. Which one will fix my phone?
When I select "wipe data/factory reset", the output is the following:
-- Wiping Data....
Formatting /data...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
E:unknown volume "/sdcard/.android_secure"
Data wipe complete.
Click to expand...
Click to collapse
prongs_rajat said:
Yeah I'm kind of a noob. I installed CWM recovery. I boot into recovery and I see a bunch of options. Which one will fix my phone?
When I select "wipe data/factory reset", the output is the following:
Click to expand...
Click to collapse
factory reset with stock recovery after flashing everything
playya said:
factory reset with stock recovery after flashing everything
Click to expand...
Click to collapse
Already tried that. Didn't work. Always gets stuck at the boot animation. That's why I thought of trying a different recovery. Neither works
prongs_rajat said:
Already tried that. Didn't work. Always gets stuck at the boot animation. That's why I thought of trying a different recovery. Neither works
Click to expand...
Click to collapse
May have to start from scratch since this is how all others have gotten past that screen or simply why not flash a zip. So much easier than dealing with images
Sent from my Nexus 4 using Tapatalk

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

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

[+]RESTOCK - stock restore, repartition, repair and reset, including USB driver fix

RESTOCK is a new Nexus 7 2013 repair and factory reset tool for Windows. The NRT app (Nexus Root Toolkit) is similar but is old, closed-source, unsupported, abandoned, does no eMMC diagnostics and most importantly - it offers no repartitioning. Unlike NRT, Restock is specialized and optimized for Nexus 7'13 only, with streamlined operation and minimal user input.
If fastboot mode is available, then no matter what software problems like bootloops or softbricks are observed, or what custom ROM you had used before - Restock will restore your tablet to original, latest stock image, factory setup in 10 minutes (more time for one-off components download if necessary). Unforeseen issues should be reported in this thread and hopefully will be resolved within 24 hours.
If fastboot mode is not available, try the unbricking guide first.
For hardware issues, check this thread.
FEATURES
supports both flo and deb variants
small app download size (2.5MB)
automatic latest stock image (mob30x) and USB driver download from official google.com locations
robust, reliable USB device detection and driver installation - tested on Windows: XP-32, W7-32/64, W10-64(1809)
eMMC memory test and diagnostics
automatic device unlocking
option of repartition to original factory layout
- precise and reliable for any eMMC size, including 64GB and 128GB mods
- required for repartition scripts which check for original layout and flashing specific custom ROMs like e.g. Ubuntu Touch
- advised for selling in original factory condition and resolving difficult ROM flashing issues and starting from scratch
minimal user interaction and fully scripted auto-processing
the Restock script is open for inspection, corrections and improvements; post your comments and suggestions here
USAGE
download the attached zip file
unzip it
double-click on "restock.bat"
follow the prompts
SAMPLE OUTPUT
Code:
Nexus 7'13 Restock v1 @2019 k23m
SUPPORT - http://bit.ly/2C35sLZ
WARNING - installing factory image will ERASE ALL DATA from the device
Enter device name [flo OR deb]: flo
Downloading USB drivers and the latest factory image.
If not deleted, will not be downloaded again.
-- https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip
Resolving dl-ssl.google.com... 74.125.24.190, 74.125.24.91, 74.125.24.93, ...
Connecting to dl-ssl.google.com|74.125.24.190|:443... connected.
WARNING: cannot verify dl-ssl.google.com's certificate, issued by 'CN=GTS CA 1O1,O=Google Trust Services,C=US':
Unable to locally verify the issuer's authority.
HTTP request sent, awaiting response... 200 OK
Length: 8682859 (8.3M) [application/zip]
Saving to: 'latest_usb_driver_windows.zip'
latest_usb_driver_windows.zip 14%[======> ] 1.21M 383KB/s eta 19s
...
-- https://dl.google.com/dl/android/aosp/razor-mob30x-factory-52684dff.zip
Resolving dl.google.com... 172.217.25.46
Connecting to dl.google.com|172.217.25.46|:443... connected.
WARNING: cannot verify dl.google.com's certificate, issued by 'CN=GTS CA 1O1,O=Google Trust Services,C=US':
Unable to locally verify the issuer's authority.
HTTP request sent, awaiting response... 200 OK
Length: 505296115 (482M) [application/zip]
Saving to: 'razor-mob30x-factory-52684dff.zip'
razor-mob30x-factory-52684dff 86%[=============================> ] 417.98M 410KB/s eta 2m 57s
...
1. boot the Nexus in fastboot mode: when OFF press POWER + VOLUME DOWN
2. when in the bootloader menu, connect it to your PC
3. wait a few seconds, then...
Press any key to continue . . .
...
...
INFO: Successfull installation of 'd:\restock\data\usb_driver\android_winusb.inf'.
INFO: Returning with code 0x1
Device not found...
1. disconnect it from PC
2. reboot to bootloader again
3. reconnect it to PC
Press any key to continue . . .
Verify...
eMMC test...
If it freezes here, the chip is faulty and needs replacement.
eMMC OK
Lock status...
GPT...
Partitions had been changed.
Restore original partitions? [y/n]: y
Wait...
sending 'bootloader' (3911 KB)...
OKAY [ 0.141s]
writing 'bootloader'...
OKAY [ 1.518s]
finished. total time: 1.658s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: 0.008s
Wait...
sending 'gpt' (35 KB)...
OKAY [ 0.016s]
writing 'gpt'...
OKAY [ 0.109s]
finished. total time: 0.141s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: 0.012s
If error, copy and post it, include restock.log
http://bit.ly/2C35sLZ
Note: Android flash takes 2 minutes, initial boot takes 7 minutes.
Press any key to continue . . .
sending 'bootloader' (3915 KB)...
OKAY [ 0.125s]
writing 'bootloader'...
OKAY [ 1.377s]
finished. total time: 1.502s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.007s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.08
Baseband Version.....: none
Serial Number........: xxxxxxxxx
--------------------------------------------
checking product...
OKAY [ 0.016s]
checking version-bootloader...
OKAY [ 0.000s]
sending 'boot' (7422 KB)...
OKAY [ 0.234s]
writing 'boot'...
OKAY [ 1.000s]
sending 'recovery' (8166 KB)...
OKAY [ 0.266s]
writing 'recovery'...
OKAY [ 0.328s]
erasing 'system'...
OKAY [ 1.143s]
sending 'system' (843549 KB)...
OKAY [ 26.516s]
writing 'system'...
OKAY [ 39.986s]
erasing 'userdata'...
OKAY [ 23.750s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 28856791040
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7045115
Block groups: 215
Reserved block group size: 1024
Created filesystem with 11/1761280 inodes and 154578/7045115 blocks
sending 'userdata' (139085 KB)...
writing 'userdata'...
OKAY [ 12.434s]
erasing 'cache'...
OKAY [ 0.437s]
formatting 'cache' partition...
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
sending 'cache' (10984 KB)...
writing 'cache'...
OKAY [ 0.891s]
rebooting...
finished. total time: 107.057s
Press any key to exit...
RESTOCK 2
SCRIPTS
restock.bat - the main script: stock install, repair, repartition and factory reset
addons.bat - install TWRP custom recovery, mob30x-fix1, root/Magisk, ElementalX-N7-6.17 kernel
fstrim.bat - faster eMMC writes: dispatches TRIM command for all unused filesystem blocks
safe-unlock.bat - unlock without data loss
getlog.bat - diagnostics #1
relog.bat - diagnostics #2
ADDONS
These addons should be installed immediately after RESTOCK and before Android setup:
TWRP deb/flo custom recovery (it must be flashed before the other addon options)
MOB30X-FIX1 - improved Android 6.0.1 stock MOB30X installation, info: https://forum.xda-developers.com/showthread.php?t=4021757 In short, it adds WiFi 'Skip' setup option and removes old GApps to increase space on the system partition
root/Magisk - https://github.com/topjohnwu/Magisk
ElementalX-N7-6.17 custom kernel - I recommend to preset "doubletap2wake" and "battery life extender". For car use also preset "USB OTG + charge mode", info: https://forum.xda-developers.com/showthread.php?t=2389022
ERRORS
If you see errors, copy and report them. Run getlog.bat and include "getlog.log" in your post. If possible, also run relog.bat and attach "relog-xxxxxx.zip" to your post.
FSTRIM
For optimal eMMC performance run fstrim.bat from time to time.
SAFE UNLOCK
Unlock your device without data loss. MiFlash is described in the Unbricking Guide:
https://forum.xda-developers.com/showpost.php?p=75360854&postcount=199
Do not proceed unless you have read the unbricking guide and downloaded all components.
OPTIONS
Try mob30x-fix1 for improved Android 6.0.1 stock installation.
Next consider CROSS : 1-click installation of secure, up-to-date Android 7-to-11 custom ROMs, including TWRP, repartition, root, etc. as easily as RESTOCK.
NOTE
If Android is stuck on boot logo, with TWRP flash k23m-persist-fix2.zip
Did not even realize this was new! Thanks for making such a wonderfull tool! Currently using it to flash flo, and it works great!
Will install lineage after this tho
Code:
1. boot the Nexus in fastboot mode: when OFF press POWER + VOLUME DOWN
2. when in the bootloader menu, connect it to your PC
3. wait a few seconds, then...
Press any key to continue . . .
Verify...
eMMC test...
If it freezes here, the chip is faulty and needs replacement.
eMMC OK
Lock status...
GPT...
If error, copy and post it, include restock.log
[url]http://bit.ly/2C35sLZ[/url]
Note: Android flash takes 2 minutes, initial boot takes 7 minutes.
Press any key to continue . . .
sending 'bootloader' (3915 KB)...
OKAY [ 0.131s]
writing 'bootloader'...
OKAY [ 1.581s]
finished. total time: 1.719s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.014s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.08
Baseband Version.....: none
Serial Number........: 07206d7c
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7422 KB)...
OKAY [ 0.239s]
writing 'boot'...
OKAY [ 0.397s]
sending 'recovery' (8166 KB)...
OKAY [ 0.265s]
writing 'recovery'...
OKAY [ 0.448s]
erasing 'system'...
OKAY [ 0.743s]
sending 'system' (843549 KB)...
OKAY [ 26.422s]
writing 'system'...
OKAY [ 51.719s]
erasing 'userdata'...
OKAY [ 9.570s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 13342060544
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3257339
Block groups: 100
Reserved block group size: 799
Created filesystem with 11/814400 inodes and 91881/3257339 blocks
sending 'userdata' (137198 KB)...
writing 'userdata'...
OKAY [ 12.298s]
erasing 'cache'...
OKAY [ 0.051s]
formatting 'cache' partition...
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
sending 'cache' (10984 KB)...
writing 'cache'...
OKAY [ 1.029s]
rebooting...
finished. total time: 103.239s
Press any key to exit...
Dang that was timely.
It's a big hammer for what could sometimes be a small problem but it works quickly and perfectly. The alternative is pulling hair out for hours while trying to find the easy fix.
Thanks for sharing.
wow my nexus 7 was in boot loop and i had an old NRT tool which wouldnt work at all.
computer wouldnt detect next 7 2013 thru usb cable
cannot mount usb-otg in TWRP
boot loop in custom rom
your tool fixed it so fast and easy.
THANKS SO MUCH FOR YOUR TOOL!!!
Thanks for this k23m although I hope to never have to use it. My Kingston equipped Nexus 7 is still going strong and it's my most used android device. If I run the emmc memory test and diagnostics would it tell me if the emmc is about to die and determine its overall wear and health?
Tmzdroid said:
Thanks for this k23m although I hope to never have to use it. My Kingston equipped Nexus 7 is still going strong and it's my most used android device. If I run the emmc memory test and diagnostics would it tell me if the emmc is about to die and determine its overall wear and health?
Click to expand...
Click to collapse
Hello Tmzdroid, your Kingston was from a newer production batch and probably is OK but maybe do not try any major OS/ROM changes as this most recent case demonstrates. The eMMC generation used in N7 has no "SMART" flash wear diagnostics like in SSD. This feature was introduced in eMMC v5+. Restock can identify Kingston if it has standard partitions and checks for the terminal, most common, read-only condition Kingstons suffer from. In short, the test can not indicate eMMC degradation level. The only forewarning you may get is a period of slow-downs prior to going read-only. If you feel it is happening, do fastboot format cache and if it takes longer than 2 seconds, it is almost the end and time to get your data out of the tablet, while you still can.
:highfive:
Thank you for this! It fixed my deb model <3
I'm getting "Incorrect device" trying to use Restock to recover from flo-deb_clamor_repartition. It's definitely flo, I am looking at the bootloader right now. fastboot format cache completes in 0.086 seconds. flo 32G, rev_e, bootloader FLO-04.08, no carrier, secure boot enabled, lock state unlocked.
edit: got going again with https://forum.xda-developers.com/showthread.php?t=2381582
AiRMaX-360 said:
Thank you for this! It fixed my deb model <3
Click to expand...
Click to collapse
Thank you for confirming that it works on deb. I have 3 flo's but no deb to test.
drinkypoo said:
I'm getting "Incorrect device" trying to use Restock to recover from flo-deb_clamor_repartition. It's definitely flo, I am looking at the bootloader right now. fastboot format cache completes in 0.086 seconds. flo 32G, rev_e, bootloader FLO-04.08, no carrier, secure boot enabled, lock state unlocked. edit: got going again with https://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
Would you be able to post a log from the attached script? Unzip and run it in Restock's folder.
:fingers-crossed:
k23m said:
Would you be able to post a log from the attached script? Unzip and run it in Restock's folder.
:fingers-crossed:
Click to expand...
Click to collapse
Strangely, it won't run unless I run as administrator. I double-click it and nothing happens. If I run as administrator then it runs in c:\windows\system32 and doesn't list the contents of the directory you want... I even tried moving restock's folder into my user dir instead of under downloads just in case something about the path was causing problems. No idea WTF that is about. Perms look good. I went ahead and just ran the commands manually from a CMD shell in the proper directory, looks like they produced the output you were looking for... except the find command doesn't work there. Maybe it would work in command.com, dunno.
I'm not sure how much help this will be since I used other tools since trying to use restock, but here it is anyway.
drinkypoo said:
Strangely, it won't run unless I run as administrator. I double-click it and nothing happens. If I run as administrator then it runs in c:\windows\system32 and doesn't list the contents of the directory you want... I even tried moving restock's folder into my user dir instead of under downloads just in case something about the path was causing problems. No idea WTF that is about. Perms look good. I went ahead and just ran the commands manually from a CMD shell in the proper directory, looks like they produced the output you were looking for... except the find command doesn't work there. Maybe it would work in command.com, dunno. I'm not sure how much help this will be since I used other tools since trying to use restock, but here it is anyway.
Click to expand...
Click to collapse
It seems your Path env exceeds the limit:
Code:
Path=C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Python27\;C:\Python27\Scripts;C:\ProgramData\Oracle\Java\javapath;C:\WinAVR-20100110\bin;C:\WinAVR-20100110\utils\bin;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\PuTTY;C:\Programs\Argyll_V1.7.0\bin;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files (x86)\GitExtensions\;C:\Program Files\Git\cmd;C:\Windows;C:\ProgramData\ComposerSetup\bin;C:\Program Files\Calibre2\;C:\Program Files (x86)\sbt\bin;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Windows\system32;C:\Users\drink\AppData\Local\Android\Sdk\platform-tools;C:\Program Files (x86)\GNU Tools ARM Embedded\5.4 2016q3\bin;C:\Users\drink\AppData\Local\Android\Sdk\platform-tools;C:\Program Files (x86)\Nmap;C:\Programs\ffmpeg-20190208\bin;C:\Program Files (x86)\Atmel\Flip 3.4.7\bin;c:\programs\fastboot;C:\programs;"%~dp0data"
My path has only:
Code:
Path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\
Please do:
Edit the path - Control Panel / System / Advanced System Settings / Advanced tab / Environment Variables button / in System Variables select Path / click Edit
copy original and save for reuse later
replace it with: C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\
save
reboot
run Restock
It should work now. As your N7 is already fixed, just close the window when it stops at "Note: Android flash takes 2 minutes, initial boot takes 7 minutes" and nothing will be flashed. Also, don't go ahead with "Restore original partitions? [y/n]" if it is offered.
If it still does not work, login to Windows with an admin account and then run Restock.
k23m said:
It seems your Path env exceeds the limit:
Click to expand...
Click to collapse
Sigh. Windows is garbage in so many ways.
I was just thinking I want to restore my Nexus back to 100% stock, and magically this recent thread appears. Worked perfectly. Thank you.
Strangely, only custom ROMs are working for me. I always get bootloop whenever I flash any of the razor Nexus Factory Images. I also tried the script you provided and finishes successfully, but when booting, it always end in bootloop with Google logo on it. I have access to fastboot and even can flash and boot to TWRP with no problemas. Any idea?
EDIT: Attached logs after re-running the script
bamsbamx said:
Strangely, only custom ROMs are working for me. I always get bootloop whenever I flash any of the razor Nexus Factory Images. I also tried the script you provided and finishes successfully, but when booting, it always end in bootloop with Google logo on it. I have access to fastboot and even can flash and boot to TWRP with no problemas. Any idea?
EDIT: Attached logs after re-running the script
Click to expand...
Click to collapse
It is a very interesting case. We need internal logs, please 'install' get-logs-sdcard.zip in TWRP, find 'logs.tgz' in the root of internal storage and post it here.
k23m said:
It is a very interesting case. We need internal logs, please 'install' get-logs-sdcard.zip in TWRP, find 'logs.tgz' in the root of internal storage and post it here.
Click to expand...
Click to collapse
Thanks for the quick reply, here I attach the logs... Seems like the /persist partition is empty, maybe thats the cause of the problem?
However, I can understand why that happened, maybe because I used the /system partition script for increasing its size...
EDIT: Somehow the XDA file uploader says invalid file for .tgz format, I recompressed the folder to a .zip file
bamsbamx said:
Thanks for the quick reply, here I attach the logs... Seems like the /persist partition is empty, maybe thats the cause of the problem?
However, I can understand why that happened, maybe because I used the /system partition script for increasing its size...
EDIT: Somehow the XDA file uploader says invalid file for .tgz format, I recompressed the folder to a .zip file
Click to expand...
Click to collapse
The 'persist' partition is not empty, you can see its contents in the log's 'ls_persist' file, but its SELinux contexts appear incorrect. Try this:
in TWRP backup your original 'persist' with the attached p4-backup-int.zip
go to my old post here, get those files and restore my 'persist' partition
boot stock ROM
:fingers-crossed:
k23m said:
The 'persist' partition is not empty, you can see its contents in the log's 'ls_persist' file, but its SELinux contexts appear incorrect. Try this:
in TWRP backup your original 'persist' with the attached p4-backup-int.zip
go to my old post here, get those files and restore my 'persist' partition
boot stock ROM
:fingers-crossed:
Click to expand...
Click to collapse
Still no luck. I have re-run the get-logs script and some file permissions have changed in le_persist (checked with a diff comparer), as well as new file called settings. Flashed factory image MOB30X and bootloop, then flash UnLegacy rom android 8.1.0 and boots with no problem. Cant understand what is happening... Maybe it is possible to use UART debugging to get some logs?
EDIT: Attached the new logs
bamsbamx said:
Still no luck. I have re-run the get-logs script and some file permissions have changed in le_persist (checked with a diff comparer), as well as new file called settings. Flashed factory image MOB30X and bootloop, then flash UnLegacy rom android 8.1.0 and boots with no problem. Cant understand what is happening... Maybe it is possible to use UART debugging to get some logs?
EDIT: Attached the new logs
Click to expand...
Click to collapse
This new log is much better. The timing was right and it had captured 'last_kmsg' with mob30x bootloop log, note:
Code:
[ 4.865234] init: Starting service 'logd'...
[ 4.873748] EXT4-fs error (device mmcblk0p23): ext4_mb_generate_buddy:741: group 1, 32282 clusters in bitmap, 32356 in gd
[ 4.873962] Aborting journal on device mmcblk0p23-8.
[ 4.874664] Kernel panic - not syncing: EXT4-fs (device mmcblk0p23): panic forced after error
...
[ 7.987304] Rebooting in 5 seconds..
[ 12.994476] Going down for restart now
[ 12.994628] in panic
It can't use mmcblk0p23 - the cache partition, and has to restart. New custom ROMs no longer use the cache partition and that's why they work. For comparison here is my 'last_kmsg' with mob30x...
Code:
[ 7.072235] EXT4-fs (mmcblk0p23): recovery complete
[ 7.077087] EXT4-fs (mmcblk0p23): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=remount-ro
[ 7.086883] fs_mgr: check_fs(): mount(/dev/block/platform/msm_sdcc.1/by-name/cache,/cache,ext4)=0: Success
[ 7.162567] fs_mgr: check_fs(): unmount(/cache) succeeded
[ 7.171722] fs_mgr: Running /system/bin/e2fsck on /dev/block/platform/msm_sdcc.1/by-name/cache
[ 7.264678] e2fsck: e2fsck 1.42.9 (28-Dec-2013)
[ 7.269744] e2fsck: /dev/block/platform/msm_sdcc.1/by-name/cache: clean, 23/35840 files, 4726/143360 blocks
[ 7.285522] EXT4-fs (mmcblk0p23): mounted filesystem with ordered data mode. Opts: barrier=1,data=ordered,nomblk_io_submit,errors=panic
[ 7.296874] fs_mgr: __mount(source=/dev/block/platform/msm_sdcc.1/by-name/cache,target=/cache,type=ext4)=0
...
[ 8.289031] init: Starting service 'logd'...
[ 8.302368] SELinux: Context u:object_r:cache_recovery_file:s0 is not valid (left unmapped).
[ 8.312286] SELinux: Context u:object_r:cache_private_backup_file:s0 is not valid (left unmapped).
[ 8.342254] init: (Loading properties from /system/build.prop took 0.01s.)
[ 8.348266] init: (Loading properties from /vendor/build.prop took 0.00s.)
[ 8.355133] init: (Loading properties from /factory/factory.prop took 0.00s.)
[ 8.369842] init: Starting service 'vold'...
[ 8.373321] logd.auditd: start
Run fastboot format cache and compare it to the 'sample output' from the first post.
There may be a partial eMMC hardware fault affecting the cache partition.
If you wish to investigate it with UART, please check my post on the subject.
:highfive:
k23m said:
This new log is much better. The timing was right and it had captured 'last_kmsg' with mob30x bootloop log, note:
Code:
[ 4.865234] init: Starting service 'logd'...
[ 4.873748] EXT4-fs error (device mmcblk0p23): ext4_mb_generate_buddy:741: group 1, 32282 clusters in bitmap, 32356 in gd
[ 4.873962] Aborting journal on device mmcblk0p23-8.
[ 4.874664] Kernel panic - not syncing: EXT4-fs (device mmcblk0p23): panic forced after error
...
[ 7.987304] Rebooting in 5 seconds..
[ 12.994476] Going down for restart now
[ 12.994628] in panic
It can't use mmcblk0p23 - the cache partition, and has to restart. New custom ROMs no longer use the cache partition and that's why they work. For comparison here is my 'last_kmsg' with mob30x...
Code:
[ 7.072235] EXT4-fs (mmcblk0p23): recovery complete
[ 7.077087] EXT4-fs (mmcblk0p23): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=remount-ro
[ 7.086883] fs_mgr: check_fs(): mount(/dev/block/platform/msm_sdcc.1/by-name/cache,/cache,ext4)=0: Success
[ 7.162567] fs_mgr: check_fs(): unmount(/cache) succeeded
[ 7.171722] fs_mgr: Running /system/bin/e2fsck on /dev/block/platform/msm_sdcc.1/by-name/cache
[ 7.264678] e2fsck: e2fsck 1.42.9 (28-Dec-2013)
[ 7.269744] e2fsck: /dev/block/platform/msm_sdcc.1/by-name/cache: clean, 23/35840 files, 4726/143360 blocks
[ 7.285522] EXT4-fs (mmcblk0p23): mounted filesystem with ordered data mode. Opts: barrier=1,data=ordered,nomblk_io_submit,errors=panic
[ 7.296874] fs_mgr: __mount(source=/dev/block/platform/msm_sdcc.1/by-name/cache,target=/cache,type=ext4)=0
...
[ 8.289031] init: Starting service 'logd'...
[ 8.302368] SELinux: Context u:object_r:cache_recovery_file:s0 is not valid (left unmapped).
[ 8.312286] SELinux: Context u:object_r:cache_private_backup_file:s0 is not valid (left unmapped).
[ 8.342254] init: (Loading properties from /system/build.prop took 0.01s.)
[ 8.348266] init: (Loading properties from /vendor/build.prop took 0.00s.)
[ 8.355133] init: (Loading properties from /factory/factory.prop took 0.00s.)
[ 8.369842] init: Starting service 'vold'...
[ 8.373321] logd.auditd: start
Run fastboot format cache and compare it to the 'sample output' from the first post.
There may be a partial eMMC hardware fault affecting the cache partition.
If you wish to investigate it with UART, please check my post on the subject.
:highfive:
Click to expand...
Click to collapse
Yeah, I had the idea of checking last_kmsg just after my previous post. Saw that mounting mmcblk0p30 was causing kernel panic. Ran TWRP Format Cache and err well... Bootloop was now in the boot animation (maybe I had to reflash factory image, which I didnt). Didnt see about mmcblk0p24, will format cache and post feedback. Thank you!
:highfive:

Categories

Resources