Related
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
I gave my uncle a brand new Nexus 10. He said after using it, not doing anything crazy, it suddenly shut off and he was unable to turn it back on again.
We've tried holding the power button for 1 sec, 10 sec, 30 sec, a minute... all result in a vibrate (and another and another after several seconds, while holding down) but the screen does not receive any power.
I can't boot into recovery, it does the same vibrate but no screen.
I CAN boot into Odin, and I CAN boot into fastboot.
He said after it not working, he tried unlocking the bootloader and such and different kinds of troubleshooting.
Fastboot says the bootloader is unlocked.
I've tried using the nexus toolkit to install stock recovery, it seems to install fine, but again, I can't boot into recovery. Also if I try to boot into CWM (without installing) from the toolkit, it seems to send and reboot the tablet, but again, it doesn't boot into anything.
Any suggestions? Is this completely bricked?
By the way I've tried to re-lock/unlock the bootloader. And I've tried to flash google stock rom in the nexus toolkit.
Royal2000H said:
By the way I've tried to re-lock/unlock the bootloader. And I've tried to flash google stock rom in the nexus toolkit.
Click to expand...
Click to collapse
Try flashing it without toolkit.
Sent from my Galaxy Nexus using XDA Premium HD app
fastboot flash recovery recovery.img
Or try
fastboot boot recovery recovery.img
With either one can you get into recovery?
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
fastboot flash recovery recovery.img
Or try
fastboot boot recovery recovery.img
With either one can you get into recovery?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Both but with the first one you will keep your custom recovery, with the second you van only boot into that recovery once.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Both but with the first one you will keep your custom recovery, with the second you van only boot into that recovery once.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Haha, I wasn't asking if this was the method, just asking if the op will try these commands and what the outcome is
But thanks
Sent from my Nexus 4 using XDA Premium 4 mobile app
mrgnex said:
Try flashing it without toolkit.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
demkantor said:
fastboot flash recovery recovery.img
Or try
fastboot boot recovery recovery.img
With either one can you get into recovery?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oops I thought I replied but didn't!
I tried both - neither worked. Still same issue unfortunately.
Can you write down all input/output from terminal/cmd when you run these, it makes it easier to help
Sent from my Nexus 4 using XDA Premium 4 mobile app
Code:
>fastboot flash bootloader bootloader-manta-manta
lj12.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.168s]
writing 'bootloader'...
OKAY [ 0.175s]
finished. total time: 0.353s
>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.008s
>fastboot -w update image-mantaray-jop40c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: ***********(removed)
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.003s]
sending 'boot' (4606 KB)...
OKAY [ 0.581s]
writing 'boot'...
OKAY [ 0.115s]
sending 'recovery' (5106 KB)...
OKAY [ 0.647s]
writing 'recovery'...
OKAY [ 0.119s]
sending 'system' (528847 KB)...
OKAY [ 66.310s]
writing 'system'...
OKAY [ 13.047s]
erasing 'userdata'...
OKAY [ 0.529s]
formatting 'userdata' partition...
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
sending 'userdata' (139141 KB)...
writing 'userdata'...
OKAY [ 26.627s]
erasing 'cache'...
OKAY [ 0.102s]
formatting 'cache' partition...
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
sending 'cache' (10372 KB)...
writing 'cache'...
OKAY [ 1.650s]
rebooting...
finished. total time: 109.788s
It tries to reboot (short vibrate)... goes to black (screen off). I can boot into fastboot (both volumes + power).
Code:
>fastboot flash recovery recovery.img
sending 'recovery' (5106 KB)...
OKAY [ 0.649s]
writing 'recovery'...
OKAY [ 0.127s]
finished. total time: 0.785s
I press reboot into recovery from the nexus 10, screen just turns off.
Code:
>fastboot boot recovery recovery.img
cannot load 'recovery'
From what I understand - that's because Google took out boot from fastboot. But when I tried to boot into recovery (without installing) from mskip's toolkit, it also didn't boot into the recovery.
Try a custom recovery like twrp image
Sent from my Nexus 4 using XDA Premium 4 mobile app
Royal2000H said:
Code:
>fastboot flash bootloader bootloader-manta-manta
lj12.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.168s]
writing 'bootloader'...
OKAY [ 0.175s]
finished. total time: 0.353s
>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.008s
>fastboot -w update image-mantaray-jop40c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: ***********(removed)
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.003s]
sending 'boot' (4606 KB)...
OKAY [ 0.581s]
writing 'boot'...
OKAY [ 0.115s]
sending 'recovery' (5106 KB)...
OKAY [ 0.647s]
writing 'recovery'...
OKAY [ 0.119s]
sending 'system' (528847 KB)...
OKAY [ 66.310s]
writing 'system'...
OKAY [ 13.047s]
erasing 'userdata'...
OKAY [ 0.529s]
formatting 'userdata' partition...
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
sending 'userdata' (139141 KB)...
writing 'userdata'...
OKAY [ 26.627s]
erasing 'cache'...
OKAY [ 0.102s]
formatting 'cache' partition...
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
sending 'cache' (10372 KB)...
writing 'cache'...
OKAY [ 1.650s]
rebooting...
finished. total time: 109.788s
It tries to reboot (short vibrate)... goes to black (screen off). I can boot into fastboot (both volumes + power).
Code:
>fastboot flash recovery recovery.img
sending 'recovery' (5106 KB)...
OKAY [ 0.649s]
writing 'recovery'...
OKAY [ 0.127s]
finished. total time: 0.785s
I press reboot into recovery from the nexus 10, screen just turns off.
Code:
>fastboot boot recovery recovery.img
cannot load 'recovery'
From what I understand - that's because Google took out boot from fastboot. But when I tried to boot into recovery (without installing) from mskip's toolkit, it also didn't boot into the recovery.
Click to expand...
Click to collapse
Hi, just spotted you typed in the wrong command it should be fastboot flash recovery recovery.img not fastboot boot recovery recovery.img
demkantor said:
Try a custom recovery like twrp image
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunately I've also tried twrp and cwm to no avail. Those were with the toolkit but I imagine it shouldn't matter.
maxal said:
Hi, just spotted you typed in the wrong command it should be fastboot flash recovery recovery.img not fastboot boot recovery recovery.img
Click to expand...
Click to collapse
Look at the command before that, I tried both.
I always recommend to stay away from tool kits but do as you please
Was the stock ROM you tried to flash from here
https://developers.google.com/android/nexus/images?hl=de
Sent from my Nexus 4 using XDA Premium 4 mobile app
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
I have a problem with my nexus 2012 WiFi version
I put twrp recovery 2.7.0.0 and omini ROM 4.4.2. Since then I have been unable to wipe anything on the device. I wipe or format in twrp when reboot every thing is same. Even with fastboot I format internal SD or wipe everything. It says it is OK but when u boot nothing is wiped. I can install apps but when I reboot they are erased and only apps which were there earlier stay. Please help. Another guy in the forum has same problem.
Default Can't wipe or factory reset Nexus 7 (2102) using multiple methods
A month or so ago my Nexus 7 (2012) started rebooting itself after a minute or so of turning on - I think this may have been during OTA upgrade from JWR66Y to new release. I tried to fix this by clearing app data and booting into CWM recovery and deleting cache and dalvik cache but the problem persisted. So I decided to reset the Nexus 7 back to factory image and have tried every means of doing so but every time I keep getting back to my original data and the app crashes and reboot continues. I have never had any issues connecting to the device on USB and ADB so this is not a driver issue. Things I have tried:
* Hard reset on phone from recovery (plus endless deleting of cache and dalvik)
* Hard reset using Wugfresh toolkit (plus near every other tool on there)
* Hard refresh from recovery mode
* Hard refresh using ADB and deleting user data etc.
* Flash recovery from ADB (also using Wugfresh as per above)
* ADB sideload from recovery of factory images, bootloaders and other ROM's
* Lock/unlock/root/unroot - using ADB commands as well as Wugfresh and other toolkits
* Delete data, system, cache
It seems like the Nexus 7 going into read only mode? Erasing /data and everything else in recovery has no effect and also when trying to overwrite the bootloader I get "writing 'bootloader'... FAILED (remote: (InvalidState))" using Wugfresh toolkit as per below. The device is still running JWR66Y.
I'm totally stuck now as to how I get my Nexus 7 back again! I have seen other people having issues with the JWR66Y bootloader (http://forum.xda-developers.com/show....php?t=1907796) but have tried all the workarounds and can't seem to find a way to overwrite the bootloader...
*** Trying with ADB manually ***
C:\android-sdk\platform-tools>adb devices
List of devices attached
4df17c816ec76f25 device
C:\android-sdk\platform-tools>adb devices
List of devices attached
015d165c520bf80f device
C:\android-sdk\platform-tools>adb reboot-bootloader
C:\android-sdk\platform-tools>fastboot devices
015d165c520bf80f fastboot
C:\android-sdk\platform-tools>fastboot oem unlock
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android-sdk\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android-sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android-sdk\platform-tools>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.016s]
finished. total time: 0.031s
C:\android-sdk\platform-tools>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-grouper-4.23.
img
sending 'bootloader' (2100 KB)...
OKAY [ 0.344s]
writing 'bootloader'...
OKAY [ 0.594s]
finished. total time: 0.938s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android-sdk\platform-tools>fastboot -w update image-nakasi-kot49h.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........: 015d165c520bf80f
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.031s]
sending 'boot' (4992 KB)...
OKAY [ 0.781s]
writing 'boot'...
OKAY [ 0.172s]
sending 'recovery' (5532 KB)...
OKAY [ 0.844s]
writing 'recovery'...
OKAY [ 0.188s]
erasing 'system'...
OKAY [ 0.016s]
sending 'system' (625382 KB)...
OKAY [ 95.203s]
writing 'system'...
OKAY [ 27.500s]
erasing 'userdata'...
OKAY [ 0.031s]
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 [ 38.453s]
erasing 'cache'...
OKAY [ 0.016s]
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 [ 2.203s]
rebooting...
finished. total time: 165.625s
*** Now using Wugfresh tool ***
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.031s]
finished. total time: 0.031s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.031s]
finished. total time: 0.031s
sending 'bootloader' (3911 KB)...
OKAY [ 0.609s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.828s
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
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........: 015d165c520bf80f
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.031s]
sending 'boot' (4992 KB)...
OKAY [ 0.781s]
writing 'boot'...
OKAY [ 0.172s]
sending 'recovery' (5532 KB)...
OKAY [ 0.844s]
writing 'recovery'...
OKAY [ 0.188s]
erasing 'system'...
OKAY [ 0.016s]
sending 'system' (625382 KB)...
OKAY [ 96.078s]
writing 'system'...
OKAY [ 27.484s]
erasing 'userdata'...
OKAY [ 0.031s]
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 [148.516s]
erasing 'cache'...
OKAY [ 0.016s]
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 [ 3.266s]
rebooting...
finished. total time: 1197.719s
Thanks[/QUOTE][/QUOTE]
Seems your firmware files are missing things, as noted in your logs.
Try getting the proper firmware from another source.
---------- Post added at 04:40 PM ---------- Previous post was at 04:39 PM ----------
Did you use this guide?
http://forum.xda-developers.com/showthread.php?t=1907796
Hey I did flash and updated my boot loader from right image posted on XDA. What firmware are you referring to
Hey can you help me please
Androgoo said:
Hey can you help me please
Click to expand...
Click to collapse
Follow the guide I linked... Exactly as it says and you should be fine.
Hey when I click the link I can't see any guide or steps to follow.
Also is the guide simple to use. I am very new to all this
The guide starts on first page with post number 1.
Hey I tried the guide. Every thing goes through fine but when tab reboots it still has old omni ROM on it. 4.4.2. I also tried to update twrp to v. 2.8 from 2.7 in fastboot but no joy. It stays on 2.7 on reboot even though fastboot flashes it and says OK done. Also I cannot relock the boot loader. I give the command in fastboot OEM lock its says OK button reboot its still unlocked. But I can boot into a new version of twrp or cwm touch temporarily using wgh tool and click boot custom recovery temporarily and it does it. But can't flash it permanently. What shall I do. Feel like smashing the tablet with a hammer. I am pissed because my son has no tablet any more. I was the one who put omni ROM on it. So I take the blame for ruining it. It was working fine but suddenly it rebooted on it'd own after few weeks and since then nothing works on it. Just the stuff that was on it. Can't install anything new. I wonder why I can't even change custom recovery from twrp permanently to a new version. Please give me your guidance.
Cant Restore / format / recovery
I had rooted the device, loaded dirty unicorns and then decided to try out Liquid. Got liquid flashed and let google restore apps and such. Came back and my girlfriend mentioned there was an update to 4.4.3 and she downloaded the "update" while I was making dinner. I came back in and she said the tablet had rebooted and now wouldn't boot. So I tried to get into TWRP which was working just fine. NO Luck.... So I tried the stock restore. it just hangs at the formatting data.
So i then tried the Nexus tool kit to reflash the stock system and unroot and I figured i would just start over. Well Im now Stuck.
I have tried everything i can.....
Included is a couple screenshots.
TIA
Nick
momule said:
I had rooted the device, loaded dirty unicorns and then decided to try out Liquid. Got liquid flashed and let google restore apps and such. Came back and my girlfriend mentioned there was an update to 4.4.3 and she downloaded the "update" while I was making dinner. I came back in and she said the tablet had rebooted and now wouldn't boot. So I tried to get into TWRP which was working just fine. NO Luck.... So I tried the stock restore. it just hangs at the formatting data.
So i then tried the Nexus tool kit to reflash the stock system and unroot and I figured i would just start over. Well Im now Stuck.
I have tried everything i can.....
Included is a couple screenshots.
TIA
Nick
Click to expand...
Click to collapse
Did you try fastboot?
KJ said:
Did you try fastboot?
Click to expand...
Click to collapse
I assume you mean via CMD
Yes, this guide here....
http://forum.xda-developers.com/showthread.php?t=1907796
KJ said:
Yes, this guide here....
http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
Yup. I'll go back through everything again. Uninstall and re install the drivers and SDK,
Thanks
Nick
momule said:
Yup. I'll go back through everything again. Uninstall and re install the drivers and SDK,
Thanks
Nick
Click to expand...
Click to collapse
Im confused. My device is not able to boot and therefore I cant enable debugging and use ADB. I have installed all the drivers and all the pkgs with SDK. and The toolkit finds myt fastboot device. hjowever CMD window does not.
Im not a cmd wiz and none of the cmds seem to be recognizable.
Use the guide linked. You'll be using fastboot from bootloader mode... Shouldn't need adb.
Read the guide carefully.
KJ said:
Use the guide linked. You'll be using fastboot from bootloader mode... Shouldn't need adb.
Read the guide carefully.
Click to expand...
Click to collapse
went through everything but writing the bootloader. Anytime it reboots into bootloader it just goes to black screen and get no response.
momule said:
went through everything but writing the bootloader. Anytime it reboots into bootloader it just goes to black screen and get no response.
Click to expand...
Click to collapse
I'm confused.. If you can't get into bootloader, then how are you using fastboot?
And, what exactly is your device (n7 2012..not 2013 right... And WiFi or 3g model) , and what exactly are you trying to flash? What firmware file?
KJ said:
I'm confused.. If you can't get into bootloader, then how are you using fastboot?
And, what exactly is your device (n7 2012..not 2013 right... And WiFi or 3g model) , and what exactly are you trying to flash? What firmware file?
Click to expand...
Click to collapse
N7 2012 - Wifi - The Tablet shows the current bootloader to be 4.18. What I mean is when the tab is manually put into bootloader its fine but when given a cmd prompt to reboot to booloader it goes to a black screen and no response from the PC connection or on the tab
I have tried flashing the following Stock images from
https://developers.google.com/android/nexus/images
4.2.2 (JDQ39)
4.3 (JWR66Y)
4.4.3 (KTU84L)
I extracted the files to SDK platform tools folder and like i said everything erases fine via fastboot cmd's. However when I get to the flash bootloader cmd its gives an error. (seen in pics posted above) I even tried the older version of the 4.23 img link in the guide you suggested.
anyone? Anyone offer a service to restore stock image for me. Thanks
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