UPDATE : FIXED MY PROBLEM.
My 32gb nexus7 is now only 8gb!k Anyone know how to fix this?
I recently upgraded my nexus7 to kitkat and had problems with restoring my user data.
I decided to downgrade back to 4.3 and had a problem that left me without recovery, only bootloader.
I used NRT 1.8.2 to fix it, but had to enable "FORCE FLASH" for it to work.
Now it thinks its an 8gb tablet, which is really only 6gb. HELP! I really need my other 24 gb back!
Any ideas would be really appreciated.
THE SOLUTION :
I had to use the -w option to flash the system.
ex. fastboot -w flash system system.img
it recognized the size mismatch and reformatted during flashing.
NOTE : wipe in TWRP recovery did not help, maybe if i had restored the stock recovery.
I just had the problem with my 16GB showing only 8GB for me all i did was to a factory reset in recovery and fixed the problem with me.
Related
How to fix this? I followed all the procedures in the factory flash guide
Oops.
First plug it in and actually see if it's capacity is now 8GB or if it's just a text bug.
If so, Factory Restore, and if that doesn't work, Flash the Image again :/
I had this happen to me on the 7. And more then once.
It seems to happen when you flash each image separately instead of doing the -w update way.
Try that way if you didn't do it already. If you did try a factory reset recovery.
Hi guys, hoping you can help me out. Noob, yup.
Nexus 7 2012 Wifi.
My Nexus was getting slow, so I successfully converted my system, data, and cache to F2FS with SlimKat.
In the process of this, I converted my Cache, System, and Data to F2FS.
The SlimKat F2FS rom was working fine. All was well.
Here's where I made a series of errors...
I decided to restore the Nexus back to factory settings/stock 4.4.4. I had some problems with my nandroid files, so I decided just to convert things back manually in TWRP. My thought process was to: A. convert Data and Cache back to ext4, B. Install factory rom from System, C. convert System back to ext4.
My thought process was apparently wrong.
Here's what I did:
1. I copied the 4.4.4 Factory Image (.tgz) to the sdcard (first mistake. I assumed the official download was a .zip but it was a .tgz).
2. In TWRP, i converted the Cache and System to ext4.
3. Tried to install stock 4.4.4 rom but couldn't install it because it was .tgz.
4. Not knowing what else to do, I converted the Data to ext4 as well. So in my eyes, everything was "put back" to ext4 like it was before. Since everything was "back to normal", I thought Nexus Root Toolkit could take me the rest of the way back to normal.
5. In Nexus Root Toolkit, I tried to "Flash Stock + Unroot", but it gave me errors (picture is attached)
6. Now I'm in bootloader. Trapped. I can't even get back into TWRP anymore (and I don't understand why).
Sorry for the noob trouble. Hopefully there is still hope for my Nexus.
Thanks in advance for any help.
In fastboot mode (i.e. Bootloader), use fastboot to flash the latest TWRP or a factory image
thunderdust said:
Hi guys, hoping you can help me out. Noob, yup.
Nexus 7 2012 Wifi.
My Nexus was getting slow, so I successfully converted my system, data, and cache to F2FS with SlimKat.
In the process of this, I converted my Cache, System, and Data to F2FS.
The SlimKat F2FS rom was working fine. All was well.
Here's where I made a series of errors...
I decided to restore the Nexus back to factory settings/stock 4.4.4. I had some problems with my nandroid files, so I decided just to convert things back manually in TWRP. My thought process was to: A. convert Data and Cache back to ext4, B. Install factory rom from System, C. convert System back to ext4.
My thought process was apparently wrong.
Here's what I did:
1. I copied the 4.4.4 Factory Image (.tgz) to the sdcard (first mistake. I assumed the official download was a .zip but it was a .tgz).
2. In TWRP, i converted the Cache and System to ext4.
3. Tried to install stock 4.4.4 rom but couldn't install it because it was .tgz.
4. Not knowing what else to do, I converted the Data to ext4 as well. So in my eyes, everything was "put back" to ext4 like it was before. Since everything was "back to normal", I thought Nexus Root Toolkit could take me the rest of the way back to normal.
5. In Nexus Root Toolkit, I tried to "Flash Stock + Unroot", but it gave me errors (picture is attached)
6. Now I'm in bootloader. Trapped. I can't even get back into TWRP anymore (and I don't understand why).
Sorry for the noob trouble. Hopefully there is still hope for my Nexus.
Thanks in advance for any help.
Click to expand...
Click to collapse
Instead of doing these whole procedure via .bat file plss try it manually yourself and install latest twrp and then format your system and other partitions with desired format and then flash manually system.img and other stuff manaually
Solved!
Hey guys, thanks for the help.
Here's what got me through it:
1. Learn how to fastboot, adb, etc. WITHOUT Nexus Root Toolkit so you understand what's going on.
2. Don't assume that any USB port or laptop will give you the same results. My attempts to flash the system with a custom rom failed time and time again. On the advice of other threads, I tried the same thing again via a different USB port, and voila it worked! Perhaps it was not a 2.0 port.
In summary, I needed to fastboot erase, then fastboot flash the partitions. And most of all, I had to try it on a different USB port if it failed unexpectedly.
Hope this helps somebody else!
I have 5.0.2 (LRX22G) rooted + TWRP.
I flashed the original stock recovery from LRX22G, and still I cannot sideload OTA, I'm getting error "/system/bin/app_process32 has unexpected contents".
Is this because I'm rooted?
Is there another way to upgrade to 5.1 ? Can I just flash new bootloader, system, boot and recovery images (from the factory image LMY47D) and erase cache?
(Obviously I want to preserve my apps and data while upgrading...)
Found answer here:
http://www.theandroidsoul.com/fix-e...img-android-5-0-factory-images-nexus-devices/
The only missing (last) step for my setup:
flash latest TWRP, reboot into it, flash latest SuperSU, erase Dalvik and cache, reboot.
You can flash every partition for itself. No need to wipe. But I haven't done this so far so I can't tell if it will work.
But here is a guide.
http://highonandroid.com/android-sm...-android-5-1-manually-on-nexus-4-5-6-9-and-10
I always just manually flash all the images from the new factory image EXCEPT USERDATA. Never had any issues, and all my data stays the same as it was before flashing/updating.
And HOW exactly do you DO that (on a Zenfone 2e) because I cant find any Definitive Info on the phone variant. It seems that ASUS uses the same tools for the 2e as they do for the 2 (16 Gig) but they never say FOR Sure. I have a 2e and I'd REALLY like to be able to put the newer rom on it. I keep getting the same ...app_process32 Status 7 error.
So How would I go about GETTING the Factory Rom from ASUS ,
and 2 Where can I find the "Tools" i keep hearing about
Also, Im not a noob, I've used Fastboot and ADB before, I'm just not quite a "Pro"
hippopo said:
I have 5.0.2 (LRX22G) rooted + TWRP.
I flashed the original stock recovery from LRX22G, and still I cannot sideload OTA, I'm getting error "/system/bin/app_process32 has unexpected contents".
Is this because I'm rooted?
Is there another way to upgrade to 5.1 ? Can I just flash new bootloader, system, boot and recovery images (from the factory image LMY47D) and erase cache?
(Obviously I want to preserve my apps and data while upgrading...)
Click to expand...
Click to collapse
Hello,
you can flash yourself the content of the factory image.
Unzip the content , and then the newly extracted archive you will find.
you can do such tings ...
Code:
fastboot flash <partition> <path_to_img_file>
replace <partition> with system or bootloader
<path_to_img_file> should be the absolute path to your img fileSo if i were you I would simply flash the system partition and erase cache
Hi,
I have a 16GB Nexus 4, running Android 5.1.1 LMY48I. I had recently flashed Google's stock rom (Android 5.1.1 LMY48I) on my Nexus 4. Later, I noticed that my Nexus thinks my internal storage capacity is 5.6 GB, while I know it should be a little less than 16 GB. That was really strange, and I figured that re-flashing stock rom might solve the bug. Unfortunately, my phone still believes I have less storage than I actually have.
I'd be happy if someone could explain why it happened, and more importantly - How I can fix it.
Thank you!
SOVED:
I managed to fix it by formatting the CACHE, SYSTEM and USERDATA partitions, then re-flashing the stock rom. I encountered a bootloop, so I decided to format again only the CACHE and USERDATA. Everything works now.
ido_doron said:
SOVED:
I managed to fix it by formatting the CACHE, SYSTEM and USERDATA partitions, then re-flashing the stock rom. I encountered a bootloop, so I decided to format again only the CACHE and USERDATA. Everything works now.
Click to expand...
Click to collapse
In the future, all you need to do is boot into the stock recovery after flashing the factory image and do a factory reset.
Sent from my Nexus 9 using XDA Free mobile app
I actually did tried this, but from some reason TWRP failed wiping the userdata partition...
ido_doron said:
I actually did tried this, but from some reason TWRP failed wiping the userdata partition...
Click to expand...
Click to collapse
Trwp is not the stock recovery.
Sent from my Nexus 9 using XDA Free mobile app
However, as much as I know, it should be able to wipe cache and user data. I tried to flash the stock recovery, but from some reason all I got is a green Android with exclamation mark on it... By the way, I also tried CWM and it failed too.
I ended up improvising something with ADB...
I'm using a Asus Zenfone 5 LTE T00P (A500KL) that has been upgraded to the latest official 5.0 ROM for a few months. Phone has not been rooted & is completely stock.
Suddenly out of the blue today, a series of forced stop error messages started appearing and I was unable to cancel all of them without rebooting the phone.
I decided to reboot into the recovery mode and that's when I saw a string of error messages that the cache partition cannot be mounted.
I have not seen this before previously.
Even when I tried to clear the cache partition, the same error message appears.
Is there a way to recover from this error without factory resetting the whole device?
I have not backed up all the data since upgrading so I'm somewhat hesitant to proceed with the FR.
I have been able to run a ADB Backup but I'm not sure if the backup.ab would be useful after the FR.
Any advise from anyone familiar with this situation?
Try to flash the actual ROM again, it shouldn't erase anything but it could help.
have you fixed this issue?
I can not flash anything in my phone anymore