Database Users

Bricked Nexus 10

My Nexus 10 stopped working after I've transferred about 14gb of movies on it. I copied them in windows 8 when nexus was plugged in USB.
It doesn't boot pass Google logo now, doesn't even reach Nexus symbol.
I can boot device in a bootloader and load a recovery. I did wipe/factory reset and also cleaned the cache, but that didn't help to solve the problem.
I have a suspicion that a filesystem is corrupt and e2fsck needs to run and fix the problems but I don't know how to start it.
I'm running a stock 4.2.1 not rooted or unlocked.
The battery level is above 70 and devices has been charging from the wall for 2 hrs at least.
Can anyone advice something to resolve the problem?

well, you still have a warranty.
that'd be my best bet, since if you hack it and its' still broken, you *might* not have a warranty.

Did you try flashing a stock image off the forums?
Sent from my Galaxy Nexus using Tapatalk 2

Less than a month old too..
Sent from my HTC PH39100 using xda app-developers app

I would replace it. It would suck to tinker with it and find out you can't fix it and the warranty is void.

Either get it replaced, or attempt to root it and flash a new ROM. I know you said wiping didnt help, but when you unlock it does a complete wipe of EVERYTHING so it might make a difference.
THe faster option to try is obviously rooting it, the safer option is probably just to get it RMA'd

Guys, Thanks for replies and suggestions.
So what I tried to do in last few days was:
I downloaded official 4.2 stock Rom and tried to reflash it together with a bootloader. I used "fastboot" to erase all partitions first, then flashed a bootloader and then flashed Rom. I had to run "oem unlock" otherwise fastboot didn't want to perform an operation.
The tablet still doesn't work, it's stuck on Google logo on a boot stage, not even reaching nexus symbol.
I didn't try to root it and install a custom Rom, because I'm afraid that I with loose a warranty. I believe the procedure above does wipe everything possible on a filesystem so I didn't go for a custom Rom solution.

I don't see a possible solution to restore a device now so I will return it on a warranty.

jodvova said:
My Nexus 10 stopped working after I've transferred about 14gb of movies on it. I copied them in windows 8 when nexus was plugged in USB.
It doesn't boot pass Google logo now, doesn't even reach Nexus symbol.
I can boot device in a bootloader and load a recovery. I did wipe/factory reset and also cleaned the cache, but that didn't help to solve the problem.
I have a suspicion that a filesystem is corrupt and e2fsck needs to run and fix the problems but I don't know how to start it.
I'm running a stock 4.2.1 not rooted or unlocked.
The battery level is above 70 and devices has been charging from the wall for 2 hrs at least.
Can anyone advice something to resolve the problem?
Click to expand...
Click to collapse
If you want to try e2fsck look at this quote/post: http://forum.xda-developers.com/showpost.php?p=34865732&postcount=162

wptski said:
If you want to try e2fsck look at this quote/post: http://forum.xda-developers.com/showpost.php?p=34865732&postcount=162
Click to expand...
Click to collapse
As I understand I need to be rooted with a custom recovery?
Can I run "adb" under a stock recovery?

jodvova said:
Guys, Thanks for replies and suggestions.
So what I tried to do in last few days was:
I downloaded official 4.2 stock Rom and tried to reflash it together with a bootloader. I used "fastboot" to erase all partitions first, then flashed a bootloader and then flashed Rom. I had to run "oem unlock" otherwise fastboot didn't want to perform an operation.
The tablet still doesn't work, it's stuck on Google logo on a boot stage, not even reaching nexus symbol.
I didn't try to root it and install a custom Rom, because I'm afraid that I with loose a warranty. I believe the procedure above does wipe everything possible on a filesystem so I didn't go for a custom Rom solution.
Click to expand...
Click to collapse
A custom ROM wouldnt help I dont think. The procedure you did is the important part before flashing a new ROM so if it didnt work then dont bother with anything custom.
jodvova said:
As I understand I need to be rooted with a custom recovery?
Can I run "adb" under a stock recovery?
Click to expand...
Click to collapse
ADB commands are run when you are booted into the tablet if I remember right.

Now that you've installed a stock ROM, go into recovery and factory reset. This may help your bootloop issue.
Sent from my Galaxy Nexus using Tapatalk 2

Blueback22 said:
Now that you've installed a stock ROM, go into recovery and factory reset. This may help your bootloop issue.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I did that couple of times, it didn't help.

Guys,
Looks like a partition table got screwed up, because when I run e2fsck on any of partitions (system, userdata, boot), it says: "attempt to read block from filesystem resulted in short read".
Does anyone know how to fix it?
Or where can I find Nexus 10 PIT file?

jodvova said:
Guys,
Looks like a partition table got screwed up, because when I run e2fsck on any of partitions (system, userdata, boot), it says: "attempt to read block from filesystem resulted in short read".
Does anyone know how to fix it?
Or where can I find Nexus 10 PIT file?
Click to expand...
Click to collapse
Have you tried to go into stock recovery, and select the adb side load and try manually push the files like that?
Sent from my Nexus 10 using xda app-developers app

evolishesh said:
Have you tried to go into stock recovery, and select the adb side load and try manually push the files like that?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Can you elaborate here?
Which files should I push? A Rom?

I am facing the same situation and it is not going past the nexus logo screen lol. I tried flashing factory images from here in fastboot mode but its still not working. In recovery, its showing can't mount SD card even after I tried mounting SD card and i tried wiping, factory reset and nothing. SD card still can't mount also and I wonder if that is the problem. I'm try some more.

So, I just fixed it and my nexus 10 boots up and all good again. Basically in bootloader, you just need to flash the userdata.img and cache.img also from the extracted files of the factory image file as I noticed it wasn't flashing those 2 files when I just flashed/updated the image.zip file with this command fastboot -w update image-mantaray-jop40c.zip and it was only flashing the system.img, recovery.img, boot.img so I extracted this image-mantaray-jop40c.zip file and I flashed the userdata.img and cache.img files manually and rebooted and its all good again back to stock.

NeverAlwaysEver said:
So, I just fixed it and my nexus 10 boots up and all good again. Basically in bootloader, you just need to flash the userdata.img and cache.img also from the extracted files of the factory image file as I noticed it wasn't flashing those 2 files when I just flashed/updated the image.zip file with this command fastboot -w update image-mantaray-jop40c.zip and it was only flashing the system.img, recovery.img, boot.img so I extracted this image-mantaray-jop40c.zip file and I flashed the userdata.img and cache.img files manually and rebooted and its all good again back to stock.
Click to expand...
Click to collapse
Just to clarify did you use fastboot to flash userdata.img? Which command did you use "fastboot -w update userdata.img"?

Also where did you find userdata.img ???
It doesn't come in nexus 10 factory image. It only has boot, cache, recovery, system and a bootloader.

For Those Who Semi-Bricked Their Nexus 7 0MB Interal Storage

Hopefully this helps people in my situation.
So on the first day of having my nexus 7 i found a way to have no OS and 0MB internal storage showing in TWRP. Yah i suck.
I tried tons of things but knew a system image was needed.
HOW: I was about to flash the superuser root for 4.3 newly released and forgot to put it on nexus so i then proceeded to exit TWRP, however upon exiting TWRP the recovery detected i havent installed supersu and asked do i want to install superuser? I though why the hell not!
I confirmed to install superuser and then tried to reboot but for 20 minutes device could not boot. TWRP showed 0MB internal storage and pushing adb files in this state yielded nothing as there was no directory
This is how i managed to have a working tablet again
1. FORMAT DATA in TWRP - after doing this your internal storage should be back and not show 0MB
2. reboot to the bootloader
3. On your computer download this file kindly given to us by phuduong and uploaded by Nburnes
https://mega.co.nz/#!PBIiEbBJ!bKpdHxegOVlde12nsu_ulEyRq7UsANLLQab1IZjLIGc
Credit to Nburnes http://forum.xda-developers.com/member.php?u=2918596[/QUOTE]
4. Once downloaded move that system.img file to your adb directory
5. With you nexus 7 in the bootloader, adb open, and file downloaded copy and paste this command into adb terminal
fastboot flash system system.img
6. Now you have an OS but it still would loop and wouldnt start
7. Boot into recovery and Format Data again, because for me 0MB interal storage was back again
8. Then Factory Reset
FINALLY YOUR DEVICE SHOULD BE BACK TO ITS ORIGINAL STATE!!!!!

Is that the factory image? Have you tried going from unlocked bootloader & rooted back to factory using that image?

plbelanger said:
Is that the factory image? Have you tried going from unlocked bootloader & rooted back to factory using that image?
Click to expand...
Click to collapse
Google has yet to release the official factory image for the new N7. However, a kind user was gracious enough to make their own. It is likely to be almost identical to what Google will eventually release and should work the same way.

Thank you! Thank you!

good stuff OP. glad you got it working again

You all are life savers! 1000X Thanks!

I tried running through this, but it didn't work for me. I think my situation is different though because I tried to install a factory image for the 2012 nexus, and during part of that process I ran the "flash-all" script which starts by deleting boot, cache, recovery, userdata, and system.
I think deleting boot screwed me up, because even though I can go into recovery now after reinstalling twrp and I can restore my system using system.img, I still can't boot (get stuck on the google logo). Any way to fix that?

So you first tried to restore from the OLD Nexus 7 Image?????
Sent from my Nexus 7 using xda app-developers app

petersellers said:
I tried running through this, but it didn't work for me. I think my situation is different though because I tried to install a factory image for the 2012 nexus, and during part of that process I ran the "flash-all" script which starts by deleting boot, cache, recovery, userdata, and system.
I think deleting boot screwed me up, because even though I can go into recovery now after reinstalling twrp and I can restore my system using system.img, I still can't boot (get stuck on the google logo). Any way to fix that?
Click to expand...
Click to collapse
So you first tried to restore the OLD nexus 7 factory image? Probably gonna have to wait for factory image or exchange yours
Sent from my Nexus 7 using xda app-developers app

jporter396 said:
So you first tried to restore from the OLD Nexus 7 Image?????
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I tried to restore from the old image. Obviously fastboot wont let you install the old image, but I didn't realize that until boot, system, cache, etc. were deleted

THANK YOU!!!
This worked perfectly! I had a wiped system folder (no ROM), and obviously no USB debugging enabled. And with the lack of a factory image, I've been counting seconds to seeing somebody post this!
Just follow the instructions carefully. Thank you guys!

petersellers said:
Yes, I tried to restore from the old image. Obviously fastboot wont let you install the old image, but I didn't realize that until boot, system, cache, etc. were deleted
Click to expand...
Click to collapse
You can flash old and new image through fastboot. I did 2 times ^_^
This is boot.img for who need
BOOT.IMG HERE

It gives me a fail when I try to wipe data.
Edit: never mind

jarjar124 said:
It gives me a fail when I try to wipe data.
Edit: never mind
Click to expand...
Click to collapse
How did you fix it? I still cant wipe data.

Balsta said:
How did you fix it? I still cant wipe data.
Click to expand...
Click to collapse
Have you formatted first?
Sent from my Nexus 7 using xda app-developers app

jporter396 said:
Have you formatted first?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I can't, get an error with that too
Sent from my SCH-I545 using Tapatalk 4 Beta

OP and nburnes saved my butt!

I did this and now it seems my device is booting and it shows up as N7 when I attach it to my PC. But the display shows nothing at all. It just goes blank after the Google screen. Any ideas?
After flashing everything I could think of and banging my head and the device against the wall for two hours, I finally got it to work. Not sure how exactly but the last thing I did was reflashing bootloader. So if anyone has the same problem, try that.

Thank you.
Note:
Give step 6 a little time be patient.

All main JSS15J .IMGS here: http://forum.xda-developers.com/showthread.php?t=2381438
Glad this helped some of you guys!

4.3 Update: Stuck on Nexus Boot screen

I am stock everything and bootloader unlocked, I flash the 4.3 update via adb, but now it doesn't boot into the os, it get's stuck on the 'Nexus' boot screen.
Can someone assist me, thanks! I don't want to wipe data or reflash the rom.

Same problem here. Searching the forum for a solution... :/
Deeco7 said:
I am stock everything and bootloader unlocked, I flash the 4.3 update via adb, but now it doesn't boot into the os, it get's stuck on the 'Nexus' boot screen.
Can someone assist me, thanks! I don't want to wipe data or reflash the rom.
Click to expand...
Click to collapse

Go into custom recovery and factory reset
From my BLACKED OUT N4

spaceman860 said:
Go into custom recovery and factory reset
From my BLACKED OUT N4
Click to expand...
Click to collapse
I don't think you read my first post. I don't want to wipe data and have no custom recovery installed.

Deeco7 said:
I don't think you read my first post. I don't want to wipe data and have no custom recovery installed.
Click to expand...
Click to collapse
Did you try wiping cache
From my BLACKED OUT N4

I actually have the same problem. I had root, but I wasn't using a custom recovery. The OTA appeared as available in the notifications so I chose to install it. I set it aside and it appeared to install, but when it went to boot up, it got stuck on the X animation. I left it there while I tried to research the issue, but after 20 minutes of looking at the X I tried doing a factory reset with the stock recovery. It said it succeeded, so I rebooted. I've now been looking at the X animation for 7 minutes.

naxir said:
I actually have the same problem. I had root, but I wasn't using a custom recovery. The OTA appeared as available in the notifications so I chose to install it. I set it aside and it appeared to install, but when it went to boot up, it got stuck on the X animation. I left it there while I tried to research the issue, but after 20 minutes of looking at the X I tried doing a factory reset with the stock recovery. It said it succeeded, so I rebooted. I've now been looking at the X animation for 7 minutes.
Click to expand...
Click to collapse
edit: ^^^ same here. Root, no custom recovery.
After the update mine was stuck on the loading screen for a while, maybe a half hour. Gave up on that, did a factory reset from the recovery menus, but it still won't start up.
Any suggestions?

spaceman860 said:
Did you try wiping cache
From my BLACKED OUT N4
Click to expand...
Click to collapse
Yes, same problem.

Try reflashing, maybe something went wrong during the flash.
Sent from my Nexus 4 using Tapatalk 4 Beta

You use the stock recovery to clear cache, format I think is what recovery says, if that doesn't work then you have to do a factory reset weather you want to or not. This worked for me.
This is from efrant's guide to flashing in general section:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
If you have a 16GB device, and it now shows up as 8GB, reboot into recovery (hold power and press volume up when you are at the screen with the android and the red exclamation mark), and wipe cache. If that still doesn't work, boot back into recovery and do a factory reset. Or do this.

andyabc said:
Try reflashing, maybe something went wrong during the flash.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Tried reflashing, still no go.
kzoodroid said:
You use the stock recovery to clear cache, format I think is what recovery says, if that doesn't work then you have to do a factory reset weather you want to or not. This worked for me.
This is from efrant's guide to flashing in general section:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
If you have a 16GB device, and it now shows up as 8GB, reboot into recovery (hold power and press volume up when you are at the screen with the android and the red exclamation mark), and wipe cache. If that still doesn't work, boot back into recovery and do a factory reset. Or do this.
Click to expand...
Click to collapse
Looks like a factory reset is the only viable option. What is the best way to back everything up, if I cannot boot into OS?

Folks,
After trying a lot of option, I did a full restore flashing the entire 4.3 new image.
Worked, but lost everything on the phone.
kzoodroid said:
You use the stock recovery to clear cache, format I think is what recovery says, if that doesn't work then you have to do a factory reset weather you want to or not. This worked for me.
This is from efrant's guide to flashing in general section:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
If you have a 16GB device, and it now shows up as 8GB, reboot into recovery (hold power and press volume up when you are at the screen with the android and the red exclamation mark), and wipe cache. If that still doesn't work, boot back into recovery and do a factory reset. Or do this.
Click to expand...
Click to collapse

Deeco7 said:
Tried reflashing, still no go.
Looks like a factory reset is the only viable option. What is the best way to back everything up, if I cannot boot into OS?
Click to expand...
Click to collapse
You can backup data using adb, its a simple command to copy the internal storage but I'm not sure what the exact command is as I never had to use it.

I flashed 4.3 following efrant's guide, no dice. I tried erasing boot/recovery and formatting cache/system/userdata and then doing so again, no dice. I did a factory reset and then flashed using flash-all.sh, no dice. It hangs on X animation. I've been letting it go for 5+ minutes each time, should I be waiting longer? Is there something else I can try?

kzoodroid said:
You can backup data using adb, its a simple command to copy the internal storage but I'm not sure what the exact command is as I never had to use it.
Click to expand...
Click to collapse
Code:
adb backup-f boot boot.img
adb backup-f system system.img
adb backup-f data.img date
Would this be the commands?

kzoodroid said:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
Click to expand...
Click to collapse
My 'phone couldn't get past the X so I followed the above. Wiping the cache didn't work so I chose wipe data/factory reset, answered yes to delete all user data and the screen showed "Wiping data ... Formatting /data ... Data wipe complete". The menu then returns with reboot system now highlighted. What's supposed to happen next?
If I choose reboot system now, the 'phone just reboots to the bootloader. If I choose wipe data/factory reset, the data is wiped again and the menu returns again, same as before. If I do nothing, nothing happens, at least according to the screen. What am I missing?

I was able to use flash-all.sh in 4.2.2 and it booted fine. I tried the ota again and same issue. Some apps autoinstalled when I installed 4.2.2, so I guess I can re-flash 4.2.2, make sure no apps download, then try the OTA again, but I'm not sure what else I can try to get 4.3 to install.

Yeah I also had the same problem. Tried to apply OTA from rooted stock. I flashed 4.2.2 via fastboot without wiping user data and got it to start in 4.2.2 again. Backed up all the important files and app data with Titanium, factory reset and then flashed 4.3. Rooted and then restored all the app data. Had a small issue with the r/w permission on some of the folders that affected the Gallery app not being able to work properly but did a fix and it all works fine now.
Sent from my Nexus 4 using Tapatalk 4 Beta

Deeco7 said:
Code:
adb backup-f boot boot.img
adb backup-f system system.img
adb backup-f data.img date
Would this be the commands?
Click to expand...
Click to collapse
No that's not it. I saw a tutorial somewhere on how to backup the Nexus 4 using adb but I can't find it. Someone in here knows how to do it and/or there is already a thread on it.
it would be something like --- adb pull all storage/emulated/0 --- to get all your data off the sdcard but I'm not sure of the syntax I used plus you need to designate where to put the data you just pulled. I only looked at the how to once and very briefly as I didn't need to use it. I'm not sure how you backup user data but you would need to pull the image off the device.
I have most of my data backed up to either Google or in my Box account using Helium backup so I don't care about losing any doing a factory restore so I have no need to know how to do an adb backup.
---------- Post added at 09:24 PM ---------- Previous post was at 09:17 PM ----------
This isn't the guide I saw before but I think it will work. I cut out the relevant section from the article.
http://www.dotkam.com/2013/01/16/backup-and-reset-nexus-4-cracked-and-locked-screen/
One thing I knew I could do for sure is to backup the “sdcard”. I knew this because of two things: I have “USB Debugging” on, which means I can use adb, and “sdcard” is not owned by root, which means it can be “pulled”/”read” by adb. Hence the first step is clear:
./adb pull /sdcard/ /destination
At this point all the pictures / videos / music, etc.. are backed up. Now I need to backup my SMS, contacts, etc.. Information that lives in Android “databases”. For example contacts usually live here “/data/data/com.android.providers.contacts/databases”. Which can’t be simply “pulled” as pitures, since they are protected, and hence cannot be read by adb directly.
---------- Post added at 09:34 PM ---------- Previous post was at 09:24 PM ----------
I found this thread in the galaxy nexus forum and maybe it will work, it was using syntax similar to what you posted.
http://forum.xda-developers.com/showthread.php?t=1420351

So I have tried many things to flash 4.3, but none have worked. Flashing 4.2.2 works and it's how I recover from getting stuck on the nexus boot screen which happens whenever I flash 4.3.
I have tried:
Simple OTA. Performed when I had root and also from fresh 4.2.2 install.
Flash using fastboot and all .img files separately, wiping the cache afterwards.
Flash using flash-all.sh script included with the factory image.
I have tried doing the above wiping cache before/after and doing a factory reset before/after. The MD5 checksum of the .tgz is correct, so the file downloaded correctly. However, all roads lead to being stuck on the "X" animation during boot up. I always allow 5+ minutes for it to progress beyond, but it hasn't.

[Q] Nexus 4: Can't wipe/Flash factory image. Semi-bricked phone.

Earlier today my phone was working fine running Stock 4.4.1/Kernel. I decided I wanted to get the franco kernel so I got the .img file from the xda thread. I flashed the .img file onto the boot partition using fastboot, and restarted my phone. After a few minutes of sitting at the "Google" screen I rebooted into the bootloader. I tried flashing the 4.4 factory image using the "flash-all.bat" without wiping anything. My phone continued to get stuck at the "Google" screen after multiple reboots. I then tried to wipe my device using fastboot. However, when using the command "fastboot erase system" I got an error that said "Failed: unknown chunk type." I kept on retrying the wipe to no avail. I found this thread: http://forum.xda-developers.com/showthread.php?t=2347060 and followed the steps. All the steps seemed to work up until I had to flash the given factory image using fastboot. I got the same "Unknown chunk type" when the cmd was trying to write files to the "system partition." Before you ask, yes my fastboot/adb is updated to the newest version. (I triple checked) And all my drivers work properly. I just flashed the 4.4.1 firmware 3 days ago using fastboot and everything went perfectly, including the wipe. Please offer any solutions you think could get me out of this situation. Thank you.

PandemicHD said:
Earlier today my phone was working fine running Stock 4.4.1/Kernel. I decided I wanted to get the franco kernel so I got the .img file from the xda thread. I flashed the .img file onto the boot partition using fastboot, and restarted my phone. After a few minutes of sitting at the "Google" screen I rebooted into the bootloader. I tried flashing the 4.4 factory image using the "flash-all.bat" without wiping anything. My phone continued to get stuck at the "Google" screen after multiple reboots. I then tried to wipe my device using fastboot. However, when using the command "fastboot erase system" I got an error that said "Failed: unknown chunk type." I kept on retrying the wipe to no avail. I found this thread: http://forum.xda-developers.com/showthread.php?t=2347060 and followed the steps. All the steps seemed to work up until I had to flash the given factory image using fastboot. I got the same "Unknown chunk type" when the cmd was trying to write files to the "system partition." Before you ask, yes my fastboot/adb is updated to the newest version. (I triple checked) And all my drivers work properly. I just flashed the 4.4.1 firmware 3 days ago using fastboot and everything went perfectly, including the wipe. Please offer any solutions you think could get me out of this situation. Thank you.
Click to expand...
Click to collapse
Never encountered something like this, but maybe from bootloader u can get into ur stock recovery & wipe cahce & wipe data.
once again I never had that issue...so its upto u...but might be worth a try...if u had made a backup or dont care about the data in ur phone then it did be easier for u u to try

Flash the factory images and erase all partitions on the device. If you want to get some data from the internal memory you could pull it through recovery. Next time read more do less. Franko's kernel uses different ram disk than the stock one. You could also try to flash a full stock kernel for your build first. Get it from the factory images and flash it through fastboot.
Sent from my Nexus 4 using xda app-developers app

i have the exact same problem here ! and i dont know what to do! its still stucked on the google logo!!!

alexvck said:
i have the exact same problem here ! and i dont know what to do! its still stucked on the google logo!!!
Click to expand...
Click to collapse
What's the exact same problem? Did you flash Franko kernel too. If so just dirty flash your current rom.

jd1639 said:
What's the exact same problem? Did you flash Franko kernel too. If so just dirty flash your current rom.
Click to expand...
Click to collapse
no i just had rooted it and loadedcwm and i was ready to flash paranoid anroid rom! and when it rebooted it stuck on the google logo! then i tried to reset my phone and load the official factory image with nexus root toolkit but when it did the usual procces with the command prmpt in some point after trying to write the new system it said "Failed: unknown chunk type." ! after that it rebooted and got stucked again in google logo!!

alexvck said:
no i just had rooted it and loadedcwm and i was ready to flash paranoid anroid rom! and when it rebooted it stuck on the google logo! then i tried to reset my phone and load the official factory image with nexus root toolkit but when it did the usual procces with the command prmpt in some point after trying to write the new system it said "Failed: unknown chunk type." ! after that it rebooted and got stucked again in google logo!!
Click to expand...
Click to collapse
Use this to flash the factory image http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312

jd1639 said:
Use this to flash the factory image http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Click to expand...
Click to collapse
my device is bricked i cant do these stuff :/

alexvck said:
my device is bricked i cant do these stuff :/
Click to expand...
Click to collapse
Can you get into bootloader mode. It's worth a try. Your not bricked if it can turn on. Your emmc may be bad and flashing the factory image won't work. But if that's the case then warranty or replacement are your only options.

jd1639 said:
Can you get into bootloader mode. It's worth a try. Your not bricked if it can turn on. Your emmc may be bad and flashing the factory image won't work. But if that's the case then warranty or replacement are your only options.
Click to expand...
Click to collapse
yes i can get in bootloader! but i cant do sth :/ ... whats the emmc ?!

Originally Posted by jd1639<br />
Can you get into bootloader mode. It's worth a try. Your not bricked if it can turn on. Your emmc may be bad and flashing the factory image won't work. But if that's the case then warranty or replacement are your only options.
Click to expand...
Click to collapse
<br />
<br />
yes i can get in bootloader! but i cant do sth :/ ... whats the emmc ?!
Click to expand...
Click to collapse
Emmc is the flash memory.

jd1639 said:
Emmc is the flash memory.
Click to expand...
Click to collapse
oo okay.. so is there sth else that i can try?!

alexvck said:
oo okay.. so is there sth else that i can try?!
Click to expand...
Click to collapse
have you tired the the toolkits?

I had problem with flash system.img, solved changing usb port. I hope help you.
Inviato dal mio Nexus 4 utilizzando Tapatalk

6p Bootloop of death softbrick

I was flying yesterday, and noticed that the phone went into a bootloop when I took it out of my pocket during the flight.
My phone is on purenexus with TWRP installed already. When I got back home I tried clean flash the latest Feb ROM update, wiping all partition besides storage partition before the flash. Also flashed the latest vendor image. I did not see any error during the flash process.
No matter what I try, the phone would not get past the google screen and reboots just before it gets to the boot screen.
I am now backing up data on my phone via TWRP. It's going to be a PITA if I need to RMA the phone as it was bought in the US but I am now using it overseas.
Any magical fix to this issue?

Prior to the phone had issue, it was running Nougat Purenexus rom Jan 2017 version.

I got it yesterday. Try to flash the factory image in this post https://forum.xda-developers.com/showpost.php?p=62924118&postcount=2 (Step 10)
Add some more steps before the above:
fastboot format system
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
It will works. Try it.

nhatminhng said:
I got it yesterday. Try to flash the factory image in this post https://forum.xda-developers.com/showpost.php?p=62924118&postcount=2 (Step 10)
Add some more steps before the above:
It will works. Try it.
Click to expand...
Click to collapse
As I do not want to format internal storage, I tried option 11 - How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)
I followed all the steps and phone is still in bootloop.

Just backup your internal storage to somewhere in your PC and then you're free to go. Why dont try?

nhatminhng said:
Just backup your internal storage to somewhere in your PC and then you're free to go. Why dont try?
Click to expand...
Click to collapse
I haven't seen any evidence of wiping the internal storage will fix this issue.

Me. Yesterday. It's up to you to try.

nhatminhng said:
Me. Yesterday. It's up to you to try.
Click to expand...
Click to collapse
Just tried step 10 and format userdata - does not work. Phone is still stuck in bootloop.

The fact that you have access to the recovery means you have a high chance of getting the phone back to the should. The real BLOD only has boot loader available but nothing else besides the bar code screen.
Sent from my Nexus 6P using XDA-Developers Legacy app

CyberpodS2 said:
The fact that you have access to the recovery means you have a high chance of getting the phone back to the should. The real BLOD only has boot loader available but nothing else besides the bar code screen.
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have access to bootloader, and recovery (TWRP). Problem now is finding a solution to boot the phone past the google screen without going into a loop.

fustyler said:
I have access to bootloader, and recovery (TWRP). Problem now is finding a solution to boot the phone past the google screen without going into a loop.
Click to expand...
Click to collapse
Format your sytem, userdata and cache partitions then flash the latest full stock image using flash-all.bat.

v12xke said:
Format your sytem, userdata and cache partitions then flash the latest full stock image using flash-all.bat.
Click to expand...
Click to collapse
I have formatted every partition, and flashed latest full stock image. Still the same, google, google, google. Even tried the solution to format EFS partition and still bootloops.

So you have TWRP access still, and you have used the flash-all.bat method through the boot loader and it's still boned??
Sent from my Nexus 6P using XDA-Developers Legacy app

CyberpodS2 said:
So you have TWRP access still, and you have used the flash-all.bat method through the boot loader and it's still boned??
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
I followed step 10 in this guide (which is the same as doing flash-all.bat, and it is still bootlooping. I then reflashed TWRP into recovery.
https://forum.xda-developers.com/showpost.php?p=62924118&postcount=2