Can't boot into anything but fastboot (not even recovery) - Nexus 10 Q&A, Help & Troubleshooting

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

Related

[solved] Nexus 4 Soft bricked; not able to flash 'system' partition

While flashing TWRP something went wrong and i wants to go back to stock ROM.
So, downloaded factory image JWR66Y; verified md5sum.
flashed bootloader and radio successfully with fastboot.
While flashing zip; it stuck at sending 'system'
Code:
fastboot -w update occam-jwr66y/image-occam-jwr66y.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ20i
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.84
Serial Number........: 0194b441984d7557
--------------------------------------------
checking product...
OKAY [ 0.173s]
checking version-bootloader...
OKAY [ 0.000s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (6194 KB)...
OKAY [ 0.381s]
writing 'boot'...
OKAY [ 0.373s]
sending 'recovery' (6738 KB)...
OKAY [ 0.439s]
writing 'recovery'...
OKAY [ 0.404s]
erasing 'system'...
OKAY [ 0.041s]
sending 'system' (570670 KB)...
Nexus 4 is showing 'downloading...' and its there for 5 minutes.
I can manually flash all those images inside zip - boot, recovery, userdata - but not system.
What to do next ?
System partition courrupted ?
Try:
fastboot format system
fastboot flash system system.img
username8611 said:
Try:
fastboot format system
fastboot flash system system.img
Click to expand...
Click to collapse
Code:
fastboot format system
erasing 'system'...
OKAY [ 0.028s]
formatting 'system' partition...
Creating filesystem with parameters:
Size: 880803840
Block size: 4096
Blocks per group: 32768
Inodes per group: 7680
Inode size: 256
Journal blocks: 3360
Label:
Blocks: 215040
Block groups: 7
Reserved block group size: 55
Created filesystem with 11/53760 inodes and 6965/215040 blocks
sending 'system' (15680 KB)...
writing 'system'...
OKAY [ 1.605s]
finished. total time: 1.633s
Code:
fastboot flash system system.img
erasing 'system'...
OKAY [ 0.049s]
sending 'system' (570670 KB)...
Still stuck at sending 'system'
BTW, now nexus showed 'downloading..' for only a few seconds, after that it diappeared.
i think you need internet access.
Sent from my Nexus 4 using xda app-developers app
Maybe a bad download?
Did you check checksum of the factory zip?
Sent from my NookColor using Tapatalk 4
ayyub46 said:
i think you need internet access.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
What you mean ?
RASTAVIPER said:
Maybe a bad download?
Did you check checksum of the factory zip?
Sent from my NookColor using Tapatalk 4
Click to expand...
Click to collapse
Yes, i checked md5sum, and it matches..
BTW, Am using ubuntu 64-bit OS with full ADT Bundle downloaded from android dev.
Tried sideloading from stock recovery too.
Code:
adb sideload image-occam-jwr66y.zip
sending: 'image-occam-jwr66y.zip' 1%
Stuck at 1%
Am out of ideas..:crying:
Managed to solve the issue myself,
changed usb data cable and it went fine..!!
I wonder how fastboot detects device with previous faulty datacable ?
same problem for me, solved by changing usb port
stupid question, got it. sorry

[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

Xda forum help - Can't wipe using fast boot or recovery nexus 7 2012 wifi

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

Nexus 10 Bricked Black Screen

I tried to install TWRP, which seemed to work, but when I attempted to boot into the recovery I got nothing but a blank screen. Experimenting I can boot into fastboot and adb, but the bootloader is locked and I can't complete the on-screen portion of the unlock with the blank screen., so therefore can't fix the bootloader. Is there any way to unlock the bootloader from the fastboot command line without device interaction or possibly fix the image with Odin?
Looked up some images of the oem unlock screen and I thought it would be a volume up then power to execute the unlock, but that didn't work. A little annoying because it responds "OKAY" whether you choose yes or no and reboots, making it really confusing. In frustration I randomly hit the volume buttons then power and it worked.
However it still won't boot with the display. Went back into fastboot and tried the script:
Code:
fastboot flash bootloader bootloader-manta-mantamf01.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.164s]
finished. total time: 0.327s
Click to expand...
Click to collapse
Code:
flash-all.bat
erasing 'boot'...
OKAY [ 0.024s]
finished. total time: 0.024s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.041s]
finished. total time: 0.042s
erasing 'recovery'...
OKAY [ 0.027s]
finished. total time: 0.027s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.049s]
finished. total time: 0.049s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.236s]
finished. total time: 0.236s
sending 'bootloader' (1280 KB)...
OKAY [ 0.163s]
writing 'bootloader'...
OKAY [ 0.108s]
finished. total time: 0.272s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 14273216512
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3484672
Block groups: 107
Reserved block group size: 855
Created filesystem with 11/871408 inodes and 96018/3484672 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........: R32CA07MXHK
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4930 KB)...
OKAY [ 0.619s]
writing 'boot'...
OKAY [ 0.136s]
sending 'recovery' (5496 KB)...
OKAY [ 0.690s]
writing 'recovery'...
OKAY [ 0.146s]
erasing 'system'...
OKAY [ 0.036s]
sending 'system' (656846 KB)...
OKAY [ 82.208s]
writing 'system'...
OKAY [ 18.416s]
erasing 'userdata'...
OKAY [ 0.206s]
sending 'userdata' (137478 KB)...
OKAY [ 17.198s]
writing 'userdata'...
OKAY [ 4.077s]
erasing 'cache'...
OKAY [ 0.035s]
sending 'cache' (10372 KB)...
OKAY [ 1.299s]
writing 'cache'...
OKAY [ 0.324s]
rebooting...
finished. total time: 136.559s
Press any key to exit...
Click to expand...
Click to collapse
Unfortunately I still get a black screen. I suppose the screen could have conveniently chosen an rom upgrade to kick the bucket, but I kind of doubt it. Any ideas?
So your screen doesn't work at all? You don't see the bootloader menu when you boot into the bootloader (by holding both volume buttons + power button)?
Sent from my Nexus 6 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.

Categories

Resources