• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root all my partions messed up

Greg kar

Greg kar

Lurker
I just go my nexus 6 yesterday and I already messed it up I had a slight hiccup and its a really long story but I've narrowed it down to my partions messed up so what i did is flashed the tgz file from Google but it gives me an error that it can not write to the system partion and the whole thing just fails it doesn't flash anything and I've cleared all my partions now i have no recovery no data no OS or anything for that matter can someone PLEASE HELP!!! I'm thinking I need to re size the system partion i tried the command fastboot format system but it told me that its a RAW partion type and cant be formatted.

if anyone helps they'd be my savior please help please.
 
Hello Greg, and welcome to Android Forums :)

Out of curiosity, what did you do before the partitions got messed up? Knowing where you started will help us be able to figure out what went wrong.

As long as the hardware hasn't actually failed (possible, but pretty unlikely), you should be able to get a Nexus device back to operational status by reflashing the factory image. There's a handy guide on how to do that here; feel free to post back here if you encounter any problems with that. :)

BTW, when you download the image here you'll also want to make sure that the MD5 hash matches what Google provides, a95f291164b5b438b5fc9e77c222d703.

Let us know how it goes! :D
 
codesplice said:
Hello Greg, and welcome to Android Forums :)

Out of curiosity, what did you do before the partitions got messed up? Knowing where you started will help us be able to figure out what went wrong.

As long as the hardware hasn't actually failed (possible, but pretty unlikely), you should be able to get a Nexus device back to operational status by reflashing the factory image. There's a handy guide on how to do that here; feel free to post back here if you encounter any problems with that. :)

BTW, when you download the image here you'll also want to make sure that the MD5 hash matches what Google provides, a95f291164b5b438b5fc9e77c222d703.

Let us know how it goes! :D
Click to expand...

Hey thanks sooooo much but I've used wugs and done it the manual way but that doesn't work. I'm still learning how to these things so I don't know what md5 is sorry
 
MD5 is just a hashing algorithm used for verifying file integrity - basically a way to make sure that a download wasn't changed or corrupted between the server and you. On Windows, you can use something like the free WinMD5Sum utility to calculate the MD5 hash of the downloaded file.

You didn't answer my question, though - what happened before the partitions got messed up? Knowing the cause of the problem can help us figure out a solution. Without it, we're kind of guessing in the dark from afar. :p
 
codesplice said:
MD5 is just a hashing algorithm used for verifying file integrity - basically a way to make sure that a download wasn't changed or corrupted between the server and you. On Windows, you can use something like the free WinMD5Sum utility to calculate the MD5 hash of the downloaded file.

You didn't answer my question, though - what happened before the partitions got messed up? Knowing the cause of the problem can help us figure out a solution. Without it, we're kind of guessing in the dark from afar. :p
Click to expand...

Oh sorry well I followed some instructions on the Internet for rooting and installing twrp on the nexus 6 I unlocked the boot loader that's when it told me to turn the phone back on into android. So I started the phone out the boot loader and then I got this thing that didn't show up on the instructions wich was an android figure with this blue thing spinning in its belly and it said erasing it did this for three mins. I started to look at the other institutions and it said I have to put the super su zip onto the internal storage through my computer but I was using a usb otg so without thinking I powered off the phone and booted into boot loader. Through fast boot I flashed the twrp image and booted into twrp and twrp got stuck in a boot loop that's when I checked to see that that wasn't the latest version of twrp so I flashed that over the old one and it kept boot looping so I decided to clear all the portions and flash the tgz but that failed like I said and now I'm here.
 
Okay, so it sounds like you (inadvertently) interrupted the phone while it was formatting (a necessary part of the fastboot oem unlock process).

When you said that you "cleared all the partitions", how did you do that? Was that through recovery or fastboot or something else?
 
codesplice said:
Okay, so it sounds like you (inadvertently) interrupted the phone while it was formatting (a necessary part of the fastboot oem unlock process).

When you said that you "cleared all the partitions", how did you do that? Was that through recovery or fastboot or something else?
Click to expand...

I used fast boot
 
For all of the partitions? or just system?

For whatever it's worth, that command just erases the contents of the partition - it doesn't actually delete the partition or otherwise muck about with the partition table.

Have you tried reflashing the individual file system images ("fastboot flash system system.img", "fastboot flash userdata userdata.img", etc)?
 
Ok i deleted userdata cache system recovery and boot and yes i have everything flashes correctly but system but once i tried boot into recovery after i flashed it with the img file from the tgz unpacked and it gave me that same figurine with no writing and it went on forever
 
oh i forgot to mension before i cleared all the partions i acully tried boot into the os but just went to recovery and recovery was in a boot loop
 
i cant tell you the ecsact words because im not at the terminal right now but it said something like cant allocate blah amount bytes error wirting to system
 
Last edited:
Is it something to the extent of could not allocate 721539744 bytes error: cannot load 'system.img'?

(Different number of bytes, but same story).

Have you tried redownloading the factory image just to be safe?

You may also want to make sure you have the latest version of fastboot. You can get it as a part of the SDK tools here: http://dl.google.com/android/android-sdk_r24.0.2-windows.zip
 
yes and no i downloaded the 5.0.1 but then tried downloading the 5.0 and they both didnt work
and i tried flashing 5.0.1 from the nexus tool kit wich i should have used it he first place to do this all

and yes that was the error it gave

and thanks for the link i'll use it the second i get home to my computer right now im on a different computer
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom