Database Develop

4.1.2 fxz file

http://forum.xda-developers.com/showthread.php?p=40450744#post40450744
The link to the 4.1.2 fxz is above what i want to know is if anybody has tried this? what version of rsdlite did you use? im sure there will be a way to root in a couple of days

Umm.. Actually Dan has retired from exploiting the software for root access so I would not fxz unless absolutely necessary. Otherwise you will be root free, and possibly permanently.
Sent from my XT875 using Tapatalk 2

mtcrew said:
Umm.. Actually Dan has retired from exploiting the software for root access so I would not fxz unless absolutely necessary. Otherwise you will be root free, and possibly permanently.
Sent from my XT875 using Tapatalk 2
Click to expand...
Click to collapse
hmmmm...well that kinda sucks. Guess I have an excuse to get a Note 2 in two months when my contract expires.

I tried the fxz file
I tried the FXZ file. It worked, except now my internal storage is not mounted, and I cannot get it to mount. Naturally, most of my apps won't work.
Anybody have any suggestions?
Thanks.
---------- Post added at 08:58 PM ---------- Previous post was at 08:54 PM ----------
Scaredofsilence said:
I tried the FXZ file. It worked, except now my internal storage is not mounted, and I cannot get it to mount. Naturally, most of my apps won't work.
Anybody have any suggestions?
Thanks.
Click to expand...
Click to collapse
Well, I rebooted a few times. During the last time, a notification appeared and indicated my storage has issues (or something like that) and needed formatting. I hit okay, now it works. Thank God!!!!!!!

Scaredofsilence said:
I tried the FXZ file. It worked, except now my internal storage is not mounted, and I cannot get it to mount. Naturally, most of my apps won't work.
Anybody have any suggestions?
Thanks.
---------- Post added at 08:58 PM ---------- Previous post was at 08:54 PM ----------
Well, I rebooted a few times. During the last time, a notification appeared and indicated my storage has issues (or something like that) and needed formatting. I hit okay, now it works. Thank God!!!!!!!
Click to expand...
Click to collapse
Same thing happened to me, I corrupted my internal storage while OTA updating, and had to flash 4.1.2. After format, did you lost all the data in the internal storage?

cchderrick said:
Same thing happened to me, I corrupted my internal storage while OTA updating, and had to flash 4.1.2. After format, did you lost all the data in the internal storage?
Click to expand...
Click to collapse
Correct. I thought FXZ did this anyway so I backed up all the important stuff already.
You can just reformat your internal storage and voila, you have app memory.
PS - is anyone else's FXZ'ed JB horribly horribly choppy and unresponsive? Used the FXZ from the "Firmware Team"s thread in devlopment.
edit- my phone rebooted after battery died, much smoother now. not sure what happened there...

mrlinch said:
Correct. I thought FXZ did this anyway so I backed up all the important stuff already.
You can just reformat your internal storage and voila, you have app memory.
PS - is anyone else's FXZ'ed JB horribly horribly choppy and unresponsive? Used the FXZ from the "Firmware Team"s thread in devlopment.
Click to expand...
Click to collapse
This just happened to me after I fxz'ed with the jb file's I didn't notice and went on to install 20 app's will I lose them all if I format?

Lost storage space on phone 64gb

My 64GB Nexus is now saying it has 23gb of total storage and 21gb available. I had to reflash the stock ROM after a failed twrp flash. Is there anyway to fix this? I have already tried reflashing and wiping the phone 2 times but the storage decreases each time.

Use a factory image and start over.

ericsignals said:
Use a factory image and start over.
Click to expand...
Click to collapse
I've already done that twice

Pilz said:
I've already done that twice
Click to expand...
Click to collapse
Double check and make sure you have the latest SDK and/or just download the latest regardless. N5 folks have been having similar issues since the Lollipop release.

jhax01 said:
Double check and make sure you have the latest SDK and/or just download the latest regardless. N5 folks have been having similar issues since the Lollipop release.
Click to expand...
Click to collapse
I can try to redownload the SDK, but my question is what does the SDK have to do with losing space on my phone?

I don't pretend to know what the cause is behind it but when the 5.0 factory images were released, people who flashed it with an older version of fastboot were losing storage on the Nexus 5.
Sent from my Nexus 5 using Tapatalk

I fixed it after doing a factory reset then flashing it again. I double checked and I already had the latest SDK. Its really weird how it took flashing 3 times to work.

Pilz said:
I fixed it after doing a factory reset then flashing it again. I double checked and I already had the latest SDK. Its really weird how it took flashing 3 times to work.
Click to expand...
Click to collapse
I am in the same boat. Even did a factory reset and flashed the factory image but still stuck with 23GB on my 64GB. What exactly did you do to fix this?

the.emilio said:
I am in the same boat. Even did a factory reset and flashed the factory image but still stuck with 23GB on my 64GB. What exactly did you do to fix this?
Click to expand...
Click to collapse
I re-downloaded the latest SDK and then reflashed the images again. It took a few times before it reset. I also used fastboot erase system if I remember correctly.

Pilz said:
I re-downloaded the latest SDK and then reflashed the images again. It took a few times before it reset. I also used fastboot erase system if I remember correctly.
Click to expand...
Click to collapse
Did you flash each image individually since the flash all gives that no system.img error? Just want to make sure I can duplicate what you did.

the.emilio said:
Did you flash each image individually since the flash all gives that no system.img error? Just want to make sure I can duplicate what you did.
Click to expand...
Click to collapse
I flashed each one manually. The bat file doesn't work so that's the only way to do it. I don't remember the order I flashed everything in, but I remember that I used fastboot to wipe the phone before flashing. I kept trying different things until it showed the right storage then I decrypted it and flashed TWRP and used CF auto root. One of my mistakes was rooting before checking because it was a waste of time if I had to flash it again.
I may have done a factory reset st one point but I don't remember because it was late and I was watching TV with my wife whole doing this.

Pilz said:
I flashed each one manually. The bat file doesn't work so that's the only way to do it. I don't remember the order I flashed everything in, but I remember that I used fastboot to wipe the phone before flashing. I kept trying different things until it showed the right storage then I decrypted it and flashed TWRP and used CF auto root. One of my mistakes was rooting before checking because it was a waste of time if I had to flash it again.
I may have done a factory reset st one point but I don't remember because it was late and I was watching TV with my wife whole doing this.
Click to expand...
Click to collapse
Figured. I will keep trying. Thanks!
---------- Post added at 11:56 PM ---------- Previous post was at 11:08 PM ----------
After about 10 attempts it turns out all i had to do was fastboot format cache then fastboot format userdata. Reboot and boom restored to normal. LMAO! Wasted 4 hours tonight just for that. Live and learn!

Just do a factory reset in recovery WITHOUT reflashing and the problem is taken care of.
Seems a like a bug in the factory images that can cause of wrong partition sizes.
Worked on my N9 (which I already sent back to Google due to excessive lightbleed lol)

I had the same issue after trying to root the phone showed 23 GB.
I was able to get back to 53 GB after wipine cache and formatting user data, but that still seems like I'm missing something . I did not check how much storage was available before I started.
Can any one tell me what the storage numbers should be on like on a stock device with nothing installed please?

I remember hearing about this same issue with the Nexus 5. Don't recall the cause though. Sorry folks I know this post is useless I'm just excited to be getting my Nexus 6 so I perusing the forums.

Missing Storage Space?

Hey everyone,
I'm having a storage issue with my Nexus 6. My available space is showing up as 32GB even though I have 64GB of real space. When I was on full stock, it showed up correctly, but after I flashed the no-encrypt boot.img in Android Development, Its showing up as 32 GB instead of 64.
Help appreciated!

You're going to have to do a factory reset from the backup & reset menu. Back up anything you want to keep since it will wipe EVERYTHING on your device. That's the only thing that worked for me when I had the issue with my N5 and that's what is suggested in the toolkit

Hero_Guy said:
You're going to have to do a factory reset from the backup & reset menu. Back up anything you want to keep since it will wipe EVERYTHING on your device. That's the only thing that worked for me when I had the issue with my N5 and that's what is suggested in the toolkit
Click to expand...
Click to collapse
Quick question, I have the exact same thing happening with my Nexus 6P - will this same fix work for me?

Hero_Guy said:
You're going to have to do a factory reset from the backup & reset menu. Back up anything you want to keep since it will wipe EVERYTHING on your device. That's the only thing that worked for me when I had the issue with my N5 and that's what is suggested in the toolkit
Click to expand...
Click to collapse
Yeah well, that is why toolkits are worse then paying attention and learning things
http://forum.xda-developers.com/nexus-6/general/phone-gb-storage-to-factory-reset-t3225492
No need to factory reset, you can fix through TWRP

JNCHD said:
Hey everyone,
I'm having a storage issue with my Nexus 6. My available space is showing up as 32GB even though I have 64GB of real space. When I was on full stock, it showed up correctly, but after I flashed the no-encrypt boot.img in Android Development, Its showing up as 32 GB instead of 64.
Help appreciated!
Click to expand...
Click to collapse
Did you resolve this using the TWRP method? I can't get it to work and I'm at my wits end.

mrdannyaitch said:
Did you resolve this using the TWRP method? I can't get it to work and I'm at my wits end.
Click to expand...
Click to collapse
What did you do and what part didn't work?

quick glance at TWRP makes me think all you need to do is go Wipe>advanced wipe>select data>repair or change file system>RESIZE. it seems like this should do it but having a 32gb n6 I can't test that. doesn't wipe anything so it could be worth a shot

Apologies, am typing from my phone and can't worm out how to link to another thread but there's also a thread where someone else has a 64gb showing 25gb which there are more details on.
Essentially I've flashed the December factory image using fastboot, using various methods:
All stages per the Q&A sticky, including flashing userdata and then using the TWRP method. Also all stages but replacing fastboot flash userdata with fastboot format userdata as I'm aware that the userdata.IMG is not intended for the 64gb.
Trying the TWRP method to resize always ends up with the same result, the red message saying my phone is unstable (or similar, I've seen other threads with the correct message, again apologies but am on my phone).
I've tried locking and relocking OEM lock to see if that helps or not, but nothing does.
My initial request for help on the other thread is because I got a replacement phone under insurance and didn't check if it was 32gb or 64gb and then noticed I only have 25, with the bootloader saying its a 32gb phone. I've asked but have had no answer yet whether the bootloader would change, is would it always actually know its a 64gb even if internal memory only shows it as a 32gb?
Believe it or not, I called Motorola and even with the IMEI and serial number, they could not tell me what my phone was!

Possible bricked LG G4

I tried flashing the marshmallow update that was just released (a very, very idiotic move) I flashed it the first time and all seemed well; everything flashed with no errors, and it rebooted. Well, upon reboot, I get the dreaded Factory Reset Status 2. Okay, no big deal, I just realized that I forgot to select "BOARD DL". I got to try to flash again, this time selected BOARD. Now, I get a dodownloaderror at 18s. Every time. I have tried everything, battery pulls, reflashing, I even tried reflashing ZV6 (this is probably what dug my grave). Nothing. I can still boot to recovery and DL mode, but nothing is working. I didn't put a stock img on my internal storage, so sideloading from recovery isn't an option either.
I am such an idiot. Now I have a paperweight, and it is going to cost me several hundred, if not a thousand, dollars to end my contract on the brick and then go out and buy a new phone.
Does anyone have an methods that I haven't tried?
Did I mention that I am a huge idiot?

ironbesterer said:
I tried flashing the marshmallow update that was just released (a very, very idiotic move) I flashed it the first time and all seemed well; everything flashed with no errors, and it rebooted. Well, upon reboot, I get the dreaded Factory Reset Status 2. Okay, no big deal, I just realized that I forgot to select "BOARD DL". I got to try to flash again, this time selected BOARD. Now, I get a dodownloaderror at 18s. Every time. I have tried everything, battery pulls, reflashing, I even tried reflashing ZV6 (this is probably what dug my grave). Nothing. I can still boot to recovery and DL mode, but nothing is working. I didn't put a stock img on my internal storage, so sideloading from recovery isn't an option either.
I am such an idiot. Now I have a paperweight, and it is going to cost me several hundred, if not a thousand, dollars to end my contract on the brick and then go out and buy a new phone.
Does anyone have an methods that I haven't tried?
Did I mention that I am a huge idiot?
Click to expand...
Click to collapse
Same here..

Why are you both flashing MM? Is there an official image to flash?

EmSeeMAC said:
Why are you both flashing MM? Is there an official image to flash?
Click to expand...
Click to collapse
That's why I'm an idiot. It's not an official .TOT.

ironbesterer said:
That's why I'm an idiot. It's not an official .TOT.
Click to expand...
Click to collapse
I fixed mines using LG UP
http://forum.xda-developers.com/sprint-g4/development/howto-downgrade-to-zv6-upgrade-to-t3265976
This should help you fix the dreaded 2

If you can boot into download mode, flash the ROM for your phone on sammobile

Just say you installed an update and it bricked your phone if it's still under warranty. I dunno how many times I botched my G Flex 2 and LG replaced it (ATT model).

Why is it gonna cost you $1000.00. At worst you just buy another phone.
But the cheapest is to add TEP and bring it in. You might want to brick it hard enough that they cannot see that it was every rooted though

He fixed it

ironbesterer said:
I tried flashing the marshmallow update that was just released (a very, very idiotic move) I flashed it the first time and all seemed well; everything flashed with no errors, and it rebooted. Well, upon reboot, I get the dreaded Factory Reset Status 2. Okay, no big deal, I just realized that I forgot to select "BOARD DL". I got to try to flash again, this time selected BOARD. Now, I get a dodownloaderror at 18s. Every time. I have tried everything, battery pulls, reflashing, I even tried reflashing ZV6 (this is probably what dug my grave). Nothing. I can still boot to recovery and DL mode, but nothing is working. I didn't put a stock img on my internal storage, so sideloading from recovery isn't an option either.
I am such an idiot. Now I have a paperweight, and it is going to cost me several hundred, if not a thousand, dollars to end my contract on the brick and then go out and buy a new phone.
Does anyone have an methods that I haven't tried?
Did I mention that I am a huge idiot?
Click to expand...
Click to collapse
Okay, if you can get to download mode, then use the 'send_command' batch file to adb push a stock image to /dev/media/0/ then dd it.
---------- Post added at 05:55 PM ---------- Previous post was at 05:52 PM ----------
mswlogo said:
Why is it gonna cost you $1000.00. At worst you just buy another phone.
But the cheapest is to add TEP and bring it in. You might want to brick it hard enough that they cannot see that it was every rooted though
Click to expand...
Click to collapse
Hahaha this.
With a bootloader that's totally locked down you can just say that you accepted an OTA and your battery died while it was flashing and now your phone is screwed.

agentfusion said:
Okay, if you can get to download mode, then use the 'send_command' batch file to adb push a stock image to /dev/media/0/ then dd it.
---------- Post added at 05:55 PM ---------- Previous post was at 05:52 PM ----------
Hahaha this.
With a bootloader that's totally locked down you can just say that you accepted an OTA and your battery died while it was flashing and now your phone is screwed.
Click to expand...
Click to collapse
It would be close to a thousand to pay off my current device (around $300 owed on it) and then go out and buy a new one. But, with autoprime and awesomeslayerg's help, I got my phone back to normal.

I'm glad I seen this before I tried that

Nexus 6 - 5.1. Update (Not Working)

So it's the problem that so many other people seemed to have before, I've just bought my new Nexus 6. And can't update it. It's brand new. I just get the message ''Error'' I reboot it and it works again. And it says it has the latest update, It don't. I now nothing about sideloading stuff. I'm swedish don't have a clue what to download or anything, Tried deleting cache memory, Factory reset and it still don't work. It's a god damn Nexus phone! Shouldn't it work out of the box especially with updates? Please help.

its a nexus, you can always manually flash a factory image

But how would i do that? If i might ask :3

jonisen said:
But how would i do that? If i might ask :3
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
---------- Post added at 09:38 PM ---------- Previous post was at 09:36 PM ----------
its actually much easier than it sounds, you'll realize that after.

simms22 said:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
---------- Post added at 09:38 PM ---------- Previous post was at 09:36 PM ----------
its actually much easier than it sounds, you'll realize that after.
Click to expand...
Click to collapse
Thank you! I'm just wondering, What factory Image should i download? from https://developers.google.com/android/nexus/images#bullhead I'm in Sweden with 4G network if that helps

jonisen said:
Thank you! I'm just wondering, What factory Image should i download? from https://developers.google.com/android/nexus/images#bullhead I'm in Sweden with 4G network if that helps
Click to expand...
Click to collapse
the very latest one, MMB29V

Now i have a problem, The update was a failure and now i can't go into my phone it's a loading screen and never goes away

jonisen said:
Now i have a problem, The update was a failure and now i can't go into my phone it's a loading screen and never goes away
Click to expand...
Click to collapse
How did it fail?
An error message / screenshot would help.
Did you use the flash-all script or flash each file manually?

Details, please... As already stated by murtaza02.
I just wanted to chip in and say that I hope you used the factory image for Nexus 6 (Shamu), since your link is to Nexus 5X (Bullhead). Bad things can happen if you use the wrong images...
And, if you want, I could help you out in swedish, if that would be any help. Just PM me...

So i got the phone replaced, It went fine. They didn't seem to care about it. New phone same problem. Can't update. C'MON GOOGLE. It's a software bugg? What am i supposed to do? I've already destroyed one lol

IIRC this was a relatively common problem around the time of 5.1.
Either the OTA update itself is corrupt or there's something on the phone that messes with the verification prior to updating. Before the screen with a dead android and "Error!", are you getting error messages along the lines of:
system partition has unexpected contents
E: Error in chace/update.zip
status 7
install aborted
You could try factory resetting and clearing cache in recovery. It might work, it might not...
1 - Turn off your phone
2 - Hold and press power button and volume down at the same time until you get to the bootloader screen (an android on its back with a bunch of information about your system).
3 - Use the volume buttons to select "Recovery mode" and press power.
4 - You'll get another android lying on it's back. Press both power button and volume up to enter the recovery.
5 - Use the volume buttons to highlight "wipe data/factory reset" and press power to confirm. Do the same with "wipe cache partition".
If you can get a working update after this, great. But, if the problem persists, you have two options. Get the phone replaced again or use a factory image to update to the latest android (currently 6.0.1 MMB29V). If you want to try flashing a factory image again, i'd suggest you first tell us EXACTLY (every singel detail) what you did last time, since it didn't seem to go too well...