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.

[Q] All methods of factory/hard reset seem to work, but then boots into old system

I'm having the weirdest problem and I'm wondering whether it is hardware or software. I have searched everywhere and only found one person with a similar situation and he had already sent it back for repair before anyone responded with things for him to try.
My 16gb Nexus 7 is rooted/unlocked using the Nexus Root Toolkit and at the latest OTA version. It had been working fine for months. Suddenly one day I had serious problems (which I can discuss if anyone cares, but I don't think the original problems are relevant at this point.) I gave up troubleshooting and decided to do a factory reset. But no matter what method I do, the next time I boot the device it comes back into my same buggy system and nothing was wiped or reset at all. All of these methods appear to work and give the normal messages you would expect, but then nothing changed. It's like the Flash ram is somehow set to read-only so attempts to write to it are failing.
What I have tried:
Settings Factory Data Reset and press the Erase Everything button. The tablet pauses a while, then shuts down and reboots. The old system comes back.
I go into recovery mode, choose function wipe data/factory reset, scroll down to Yes to confirm it. A bunch of progress messages show on the screen that the partitions are being formatted. I boot afterwards and the old system comes back.
I follow all the steps in articles like this: http://forum.xda-developers.com/showthread.php?t=1907796
Every fastboot command completes normally with progress messages showing that it worked. I reboot and the old system comes back.
Here is another clue: The fastboot oem lock command completes normally, but nothing changes. The padlock icon at the next boot is still open.
That's why I say that the tablet is acting as though the Flash memory is set to read-only somehow because nothing ever changes. Is it possible that this is a hardware problem, or is there something else I can do in software?

Bump One for OP
hope your problem gets solved...

I go into recovery mode, choose function wipe data/factory reset, scroll down to Yes to confirm it. A bunch of progress messages show on the screen that the partitions are being formatted. I boot afterwards and the old system comes back.
Click to expand...
Click to collapse
1. If you wipe this way and then do not install another rom, then the old system will just reload.
2. Which recovery are you using TWRP or CWM? Maybe try an alternative recovery?
3. Go into recovery/mounts and storage/ then select format system and then install another rom such as stock and see what happens..

killall said:
1. If you wipe this way and then do not install another rom, then the old system will just reload.
2. Which recovery are you using TWRP or CWM? Maybe try an alternative recovery?
3. Go into recovery/mounts and storage/ then select format system and then install another rom such as stock and see what happens..
Click to expand...
Click to collapse
1. I guess my wording was ambiguous. When I said that the old system comes back, I didn't mean only that the old OS comes back, but that EVERYTHING comes back immediately including all my apps, settings, wallpaper, widgets, everything looks like it always did. I don't get the first-time screens inviting me to log in, or anything like that. The system boots completely normally as though I hadn't used those methods of wiping the user data.
Also one of the things I tried was loading a new system using fastboot commands and the new system seemed to get loaded OK. But I reboot and the buggy system is back and my user data has not been wiped.
2. I'm not sure what you mean and will research that later this evening. For now, I can tell you that I used the Nexus Root Toolkit and I am using whatever it installed.
3. I'm not sure what you mean, but will research that and if I can figure it out, I will try it this evening.
Is it a clue that the command "fastboot oem lock" seems to work, but the lock status doesn't change?

What I am trying to say (very badly) is the system on your phone will hold all your settings along with the OS. When you factory reset/wipe data, it will clear everything out....but, if you then reboot the phone, it will have to reload the old OS as it has nothing to load otherwise. This will include all your previous apps and settings.
When you have wiped all your data, you need to install another 'system/rom' to allow the phone to boot it. Or as I said, it will just reboot the old one.
Try looking for a rooted stock rom in a zip file like this one and put it on your sd card. When you have entered recovery and wiped data/factory reset, then select install from sd card, find the zip and select. The recovery will then flash it and when you reboot, you should be at the setup pages.
Using the Nexus toolkit and ADB is challenging at the best of times. Maybe it is easier if you just use the recovery method as explained above.

killall said:
What I am trying to say (very badly) is the system on your phone will hold all your settings along with the OS. When you factory reset/wipe data, it will clear everything out....but, if you then reboot the phone, it will have to reload the old OS as it has nothing to load otherwise. This will include all your previous apps and settings.
When you have wiped all your data, you need to install another 'system/rom' to allow the phone to boot it. Or as I said, it will just reboot the old one.
Try looking for a rooted stock rom in a zip file like this one and put it on your sd card. When you have entered recovery and wiped data/factory reset, then select install from sd card, find the zip and select. The recovery will then flash it and when you reboot, you should be at the setup pages.
Using the Nexus toolkit and ADB is challenging at the best of times. Maybe it is easier if you just use the recovery method as explained above.
Click to expand...
Click to collapse
When I go into the recovery mode at boot time, the menu says I am using "Android system recovery <3e>"
According to all documentation I have seen, erasing the user partition is all I should need to do to wipe out all of my data, and this works perfectly on a different tablet that I have. I really shouldn't need to do anything else, which is why my situation is so strange.
The Nexus 7 doesn't have an SD card slot so I can't do the things you are saying that involve installing things from sd. Maybe there is a way to do the same thing via the portion of Flash that simulates an sd card, but the recovery menus don't have any way to do that, at least not that I can find.

I saw that you are rooted then I assumed you were using a custom recovery like Clockworkmod or TWRP.
When I wrote SD I meant the internal storage, sorry for the confusion.
I would be flashing a recovery again, it seems to be causing the problem. You can do this through Nexus tools.

killall said:
I saw that you are rooted then I assumed you were using a custom recovery like Clockworkmod or TWRP.
When I wrote SD I meant the internal storage, sorry for the confusion.
I would be flashing a recovery again, it seems to be causing the problem. You can do this through Nexus tools.
Click to expand...
Click to collapse
When you say to use "Nexus tools", do you mean the the tools that are part of the Nexus Root Toolkit? I did use those tools to format and rebuild the recovery partition, and it didn't help at all.
If you mean tools that I need to install as apps within Android, that isn't possible at the moment because the tablet is so unstable that when I reboot, I get all my old stuff for a few seconds so I know nothing changed, and then it reboots before I have a chance to do anything.
If you mean that I should mount the Android flash ram as a folder on my PC, I only seem to be able to do that for the few seconds that the system is booted and then the folder drops off. The only mode where I can keep the tablet powered on and stable is the boot menu and the recovery menu. Is there a way to mount the drive at that time?

Phonetrips said:
When you say to use "Nexus tools", do you mean the the tools that are part of the Nexus Root Toolkit? I did use those tools to format and rebuild the recovery partition, and it didn't help at all.
If you mean tools that I need to install as apps within Android, that isn't possible at the moment because the tablet is so unstable that when I reboot, I get all my old stuff for a few seconds so I know nothing changed, and then it reboots before I have a chance to do anything.
If you mean that I should mount the Android flash ram as a folder on my PC, I only seem to be able to do that for the few seconds that the system is booted and then the folder drops off. The only mode where I can keep the tablet powered on and stable is the boot menu and the recovery menu. Is there a way to mount the drive at that time?
Click to expand...
Click to collapse
Fast boot a custom recovery. Fastboot recovery c:/path/recovery.IMG
Path being whatever path you have to the recovery you chose to download. Then wipe data/factory reset, maybe wipe cache and dalvik since you're there. Then reboot, see what happens. Still buggy, download another ROM, there are stock-ish ones out there, or you can choose cm or AOKP
Sent from my Nexus 7 using xda app-developers app

VonEsch said:
Fast boot a custom recovery. Fastboot recovery c:/path/recovery.IMG
Path being whatever path you have to the recovery you chose to download. Then wipe data/factory reset, maybe wipe cache and dalvik since you're there. Then reboot, see what happens. Still buggy, download another ROM, there are stock-ish ones out there, or you can choose cm or AOKP
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Iv'e done all that and nothing changes whatsoever. The problem isn't that I have a buggy Android system, but rather that all commands to format and erase that system are ignored.

Actually I was wrong, I never did load a recovery image like you said, although I did at one point use one that the Nexus Root Toolkit installed.
So I found a recovery image, downloaded it, and did this:
fastboot flash recovery openrecovery-twrp-2.3.3.0-grouper.img
But nothing changes, partly because maybe I don't know what to do with this thing that I just loaded. If I use the menu to go into recovery mode, I get the normal recovery menu I have always gotten.

Phonetrips said:
Actually I was wrong, I never did load a recovery image like you said, although I did at one point use one that the Nexus Root Toolkit installed.
So I found a recovery image, downloaded it, and did this:
fastboot flash recovery openrecovery-twrp-2.3.3.0-grouper.img
But nothing changes, partly because maybe I don't know what to do with this thing that I just loaded. If I use the menu to go into recovery mode, I get the normal recovery menu I have always gotten.
Click to expand...
Click to collapse
Flash the cwm one, maybe that will work?
Sent from my Galaxy Nexus using xda app-developers app

Phonetrips said:
Iv'e done all that and nothing changes whatsoever. The problem isn't that I have a buggy Android system, but rather that all commands to format and erase that system are ignored.
Click to expand...
Click to collapse
VonEsch said:
Flash the cwm one, maybe that will work?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Before I try a different one, can you please tell me what is supposed to happen after I give that fastboot command to flash the recovery image, Should the tablet go into that recovery manager immediately, or do I need to do something first to make it show up?
I went ahead and found/downloaded the cwm one. The same thing happened: I don't see it running and if I go into recovery mode I get the normal recovery, not this one.

killall said:
What I am trying to say (very badly) is the system on your phone will hold all your settings along with the OS. When you factory reset/wipe data, it will clear everything out....but, if you then reboot the phone, it will have to reload the old OS as it has nothing to load otherwise. This will include all your previous apps and settings.
When you have wiped all your data, you need to install another 'system/rom' to allow the phone to boot it. Or as I said, it will just reboot the old one.
Click to expand...
Click to collapse
Sorry, but this is completely wrong. When you do a factory reset, it wipes /data and /cache, which doesn't affect the OS at all because the OS resides on the /system partition. When you do a factory reset and reboot, you will run into the initial setup screen for whatever ROM you have installed. No user data/apps will be present.
Phonetrips said:
Before I try a different one, can you please tell me what is supposed to happen after I give that fastboot command to flash the recovery image, Should the tablet go into that recovery manager immediately, or do I need to do something first to make it show up?
I went ahead and found/downloaded the cwm one. The same thing happened: I don't see it running and if I go into recovery mode I get the normal recovery, not this one.
Click to expand...
Click to collapse
This seems really screwy. I'd say either your device is defective, or... Well I don't really know what else it could be. The fact that fastboot commands fail is a good indicator that something is screwed up. Have you tried wiping things through fastboot? It may be worth a shot, just know how to flash a ROM through it when you're done. I'm talking "fastboot erase -----" where ---- is replaced by system, data, or whatever. Just DO NOT erase the bootloader. Boot, however, is fine.
If all of this fails, it would seem that the device memory is defective.
About your recovery question, it will only go into recovery when you tell it to either from bootloader or ADB. And stock Android will try to remove CWM, so first time you need to go to recovery straight from the bootloader and let it make itself permanent when it asks.
Sent from my Nexus 7 using Tapatalk HD

korockinout13 said:
Sorry, but this is completely wrong. When you do a factory reset, it wipes /data and /cache, which doesn't affect the OS at all because the OS resides on the /system partition. When you do a factory reset and reboot, you will run into the initial setup screen for whatever ROM you have installed. No user data/apps will be present.
Yes, this is what is supposed to happen, but on my machine when I do all those things, there is absolutely no change and the system continues to boot exactly as it was.
This seems really screwy. I'd say either your device is defective, or... Well I don't really know what else it could be. The fact that fastboot commands fail is a good indicator that something is screwed up. Have you tried wiping things through fastboot? It may be worth a shot, just know how to flash a ROM through it when you're done. I'm talking "fastboot erase -----" where ---- is replaced by system, data, or whatever. Just DO NOT erase the bootloader. Boot, however, is fine.
If all of this fails, it would seem that the device memory is defective.
About your recovery question, it will only go into recovery when you tell it to either from bootloader or ADB. And stock Android will try to remove CWM, so first time you need to go to recovery straight from the bootloader and let it make itself permanent when it asks.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I have used fastboot erase ---- and fastboot format --- for system and everything else. Whether or not I flash new code to those partitions, all of this is ignored and the system continues to boot as it always has, with all my stuff.
After flashing the alternate recovery images, absolutely nothing changes when I choose Recovery Mode from the fastboot menu.

I talked to Google Play support and they sending out a replacement one. They never asked whether I had ever unlocked or rooted it and I didn't volunteer anything, just told them the symptoms I am having. But I have to send the old one back after I receive the new one, and there is a chance they won't accept if for warranty service when they see it,

Phonetrips said:
I talked to Google Play support and they sending out a replacement one. They never asked whether I had ever unlocked or rooted it and I didn't volunteer anything, just told them the symptoms I am having. But I have to send the old one back after I receive the new one, and there is a chance they won't accept if for warranty service when they see it,
Click to expand...
Click to collapse
That is true, since you can't change anything, they will probably know you voided the warranty. The only thing you could do is brick it permanently by erasing the bootloader... Not sure if that would work/help.
Sent from my Nexus 7 using Tapatalk HD

[SOLVED] Broken android after changing partition rights

Guys, i made a noob mistake... Again
I was using "Antek Explorer XS" and set my root -> system partition to RW. I changed rights and suddenly my whole android crashed and android recievers stopped working.
Now the phone goes into Custom recovery because it fails to boot.
Fixing permissions in TWRP does not work.
I don't know what i did, but because of my root and ME changing stuff my android is broken. Is there a way to revert this by for example only flashing the system.img? Or do i have to reflash my stock android?
I had a NANDROID made, but i lost this one when i decided to backup only data instead. It now is nowhere to be found.
Rooted Nexus 4 on android 4.3 JWR66Y

Try just flashing system.img first. If it doesn't work flash factory image!
Sent from my Nexus 4 using xda app-developers app

Thanks, im a complete noob. Will i lose data or specific settings when flashing system.img and is there need to wipe specific caches?
My bootloader is still unlocked.
If i do lose data i will try to backup some, just in case.
If i have to reflash the whole image, will this cause data loss too (my main concern are apps)?
I found back my NANDROID backup, is it wiser to restore that one instead of flashing a factory image?
This all is new to me and i hate data loss. Detailed info is very much appreciated.
EDIT: Flashing system.img solved my problem. Thanks for the advice (again).
Again i learned a lot today.. Also how to use manual flashing instead of a toolkit + finding out that in some cases it's far more trustworthy and stable then a one click toolkit.
For everybody who makes the same uber dumb mistake as i did... Here some detailed explanation.
Flashing system.img will NOT cause data loss. Couldn't find an answer on that anywhere.
Today i also found out using a toolkit isn't always helpfull. I tried a sdcard pull but because the toolkit rebooted my phone it messed up. When just using command prompt and the "adb pull \sdcard/Destination folder\Destination file" command it pulled just fine.
Moments after the pull and having flashed the system.img (reboot into bootloader use command prompt to command "fastboot flash system C:/Destination folder/system.img") i got my phone back.. With all data intact!

DecypherT said:
Thanks, im a complete noob. Will i lose data or specific settings when flashing system.img and is there need to wipe specific caches?
My bootloader is still unlocked.
If i do lose data i will try to backup some, just in case.
If i have to reflash the whole image, will this cause data loss too (my main concern are apps)?
I found back my NANDROID backup, is it wiser to restore that one instead of flashing a factory image?
This all is new to me and i hate data loss. Detailed info is very much appreciated.
EDIT: Flashing system.img solved my problem. Thanks for the advice (again).
Again i learned a lot today.. Also how to use manual flashing instead of a toolkit + finding out that in some cases it's far more trustworthy and stable then a one click toolkit.
For everybody who makes the same uber dumb mistake as i did... Here some detailed explanation.
Flashing system.img will NOT cause data loss. Couldn't find an answer on that anywhere.
Today i also found out using a toolkit isn't always helpfull. I tried a sdcard pull but because the toolkit rebooted my phone it messed up. When just using command prompt and the "adb pull \sdcard/Destination folder\Destination file" command it pulled just fine.
Moments after the pull and having flashed the system.img (reboot into bootloader use command prompt to command "fastboot flash system C:/Destination folder/system.img") i got my phone back.. With all data intact!
Click to expand...
Click to collapse
Good to hear that! Enjoy your N4!
Sent from my Nexus 4 using xda app-developers app

Yeah just for your reference.
All your downloaded apps, data and sdcard is stored on the data partition.
Apps = /data/app/
Data = /data/data/
Sdcard = /data/media/
Sent from my Nexus 4 using xda app-developers app

Well this is a bit late, but you could have fixed the problem using chmod in adb shell and set the folder permission back to 755.
xda app

@Alex240188, Thanks!
@eksasol, better late then sorry. Would be good to know earlier. But still good if somebody makes the same mistake and finds this thread.
Send from my Nexus 4

[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

Freezes on Google screen after attempted SU Install from TWRP

Ok I am sure I did this before without any problem, but this time, through TWRP on the NRTK, I installed Magisk, no problems, and then went back to install the SU with the zip file in TWRP again and then on the reboot it freezes on the Google startup screen.
I didnt even want to install the SU zip, but when I ran SU after Magisk installed after reboot, SU gave an error, so I decided to install SU from TWRP.
Did I do something wrong there, so I dont repeat the same error next time?
And how do I get out of this locked state?
I've tried wiping all cache to factory reset without deleting internal storage data... I am hoping I dont have to delete and wipe everything and start all over. I did not have a chance to eve install TiB yet.

Dathaeus said:
Ok I am sure I did this before without any problem, but this time, through TWRP on the NRTK, I installed Magisk, no problems, and then went back to install the SU with the zip file in TWRP again and then on the reboot it freezes on the Google startup screen.
I didnt even want to install the SU zip, but when I ran SU after Magisk installed after reboot, SU gave an error, so I decided to install SU from TWRP.
Did I do something wrong there, so I dont repeat the same error next time?
And how do I get out of this locked state?
I've tried wiping all cache to factory reset without deleting internal storage data... I am hoping I dont have to delete and wipe everything and start all over. I did not have a chance to eve install TiB yet.
Click to expand...
Click to collapse
Flash the stock boot.img from the image/rom you were using before this and reboot. You will have to re-root (properly) afterwards, but your phone should boot up. If you use Magisk, you don't need SU, and vice versa. Use only one method to root.

v12xke said:
Flash the stock boot.img from the image/rom you were using before this and reboot. You will have to re-root (properly) afterwards, but your phone should boot up. If you use Magisk, you don't need SU, and vice versa. Use only one method to root.
Click to expand...
Click to collapse
Hmmm ya I prob should have posted that SU error message instead of what I did, douche move.
But how do I flash the boot.img... I have an original copy of it on my PC... can I somehow while in TWRP on the phone connect to my PC via cable and run commands from my PC in CMD and execute that old boot.img flash? Or is there a location in the stock Nexus already I can use? Because there is no file in the root drive after I did the soft wipe.
P.S. Everything I have done so far has not deleted my whole storage, yet.... not sure if that is necessary at this point bec it seems reflashing the boot.img wipes absolutely everything again? If I have to it is what it is... just painful when this happens before I could get TiB running... unless my Nandroid backup file I have will restore and work after I do this?

Dathaeus said:
Hmmm ya I prob should have posted that SU error message instead of what I did, douche move.
But how do I flash the boot.img... I have an original copy of it on my PC... can I somehow while in TWRP on the phone connect to my PC via cable and run commands from my PC in CMD and execute that old boot.img flash? Or is there a location in the stock Nexus already I can use? Because there is no file in the root drive after I did the soft wipe.
Click to expand...
Click to collapse
While in TWRP you have MTP (file transfer) so you can add files to your device. Transfer the boot.img over to your device via MTP and then use TWRP to flash. Just be sure to select flash IMAGE rather than ZIP. Lesson here is when you get back up and running, install fastboot/adb and make sure it is working well and communicating with your PC. Then you can learn how to use it. This would take literally 5 seconds to flash via fastboot (device in bootloader mode).
---------- Post added at 01:29 PM ---------- Previous post was at 01:26 PM ----------
Dathaeus said:
P.S. Everything I have done so far has not deleted my whole storage, yet.... not sure if that is necessary at this point bec it seems reflashing the boot.img wipes absolutely everything again? If I have to it is what it is... just painful when this happens before I could get TiB running... unless my Nandroid backup file I have will restore and work after I do this?
Click to expand...
Click to collapse
NO, flashing boot.img will not delete any of your files. It will only write to the boot partition. If using fastboot the command is fastboot flash boot boot.img

v12xke said:
While in TWRP you have MTP (file transfer) so you can add files to your device. Transfer the boot.img over to your device via MTP and then use TWRP to flash. Just be sure to select flash IMAGE rather than ZIP. Lesson here is when you get back up and running, install fastboot/adb and make sure it is working well and communicating with your PC. Then you can learn how to use it. This would take literally 5 seconds to flash via fastboot (device in bootloader mode).
NO, flashing boot.img will not delete any of your files. It will only write to the boot partition. If using fastboot the command is fastboot flash boot boot.img
Click to expand...
Click to collapse
Yep I actually had those platform files already, and yes the MTP was active there, I just never tried that before so didnt know it was even a possibility or the right way.
So I tried via flashing my very old boot.img and also the one from
https://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
via TWRP "Install" via image install (not zip) and to the "boot partition"
and no change, same stuck on Google logo screen.
I tried the fastboot command from CMD and it says
< waiting for any device >
and doesnt do anything. I had it on the default TWRP menu screen.... I waited over 20 min although I know it shouldnt take near that long, just in case.
My bootloader is unlocked BTW, I dont want to assume anything here.

You need help getting the latest fastboot/adb binaries working on your PC. So many tutorials on how to do this. Ugh.

Dathaeus said:
Yep I actually had those platform files already, and yes the MTP was active there, I just never tried that before so didnt know it was even a possibility or the right way.
So I tried via flashing my very old boot.img and also the one from
https://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
via TWRP "Install" via image install (not zip) and to the "boot partition"
and no change, same stuck on Google logo screen.
I tried the fastboot command from CMD and it says
< waiting for any device >
and doesnt do anything. I had it on the default TWRP menu screen.... I waited over 20 min although I know it shouldnt take near that long, just in case.
My bootloader is unlocked BTW, I dont want to assume anything here.
Click to expand...
Click to collapse
Which OS security patch were you running? Flash the system (to the system partition in TWRP) and boot images (again) from the 6P factory image of the same name:
https://developers.google.com/android/images?hl=en
See if this helps.
Sent from my Nexus 5X using Tapatalk

v12xke said:
You need help getting the latest fastboot/adb binaries working on your PC. So many tutorials on how to do this. Ugh.
Click to expand...
Click to collapse
Not sure what you mean... I JUST did all that when I redid my phone completely back to factory etc etc.... just few weeks ago and then again on my new replacement. But just to be sure, I downloaded all those files again today and it didnt make any difference.
Still stuck on the
< waiting for any device >
I have to be missing some other step or something else is wrong here.
FYI not sure if this matters but when phone boots to recovery there's a red error message
"Unable to mount storage"
but it loads to TWRP fine anyways.

SlimSnoopOS said:
Which OS security patch were you running? Flash the system (to the system partition in TWRP) and boot images (again) from the 6P factory image of the same name:
https://developers.google.com/android/images?hl=en
Click to expand...
Click to collapse
Yep thats what I been doing.....
So the CMD command still doesnt work, which I think is weird in itself... and when I try to install from recovery, it goes through the whole process, both boot.img and system.img, but then it freezes on the Google logo again, so no change.
Sorry I am not sure what security patch, I just got this used from eBay, and one thing, not sure if this means anything, it says its a beta version or something and that message came up all the time when I rebooted when the phone was working.

Do I need to suck it up and redo the whole phone again........ :/