Related
My Transformer simply refuses to take any firmware updates!
I am currently still stuck on version HTJ85B.WW_epad-8.6.6.9-20110804.
I have not received any update notifications since the 3.2 update mentioned above (and I have pushed the Check Update button a lot lately).
I have also tried to install a newer version via the SOP method (download latest available version, UpdateLauncher_WW_epaduser8659.zip, from Asus, unzip to root of sdcard in ASUS/Update folder etc). unfortunately that does not work either. I have not rooted, just been running the official version of the OS.
I have cold booted the device and finally done a full factory reset. Still no update notification, and manual install via SOP is still not working either.
Does anyone have any idé how I can fix this?
When you say the root of the SD card, you are talking about an external micro SD card correct?, as that is the only way it will work...
larryk said:
When you say the root of the SD card, you are talking about an external micro SD card correct?, as that is the only way it will work...
Click to expand...
Click to collapse
Yes, I have used an external micro SD card for this.
I have tried it both in the plates SD slot and also in the SD slot in the keyboard dock.
Sent from my Transformer TF101 using Tapatalk
This is strange
As it turns out, the HTJ85B.WW_epad-8.6.6.9-20110804 version I have installed probably was installed when I had my Transformer sent in for service(my screen died). Not sure how they could make a mistake like that, but thats what it looks like.
This explains why I do not get any OTA notifications and why I do not succeed manually installing a new firmware version for the TF101, since it is expecting a version for the TF101G.
Note: I do in fact have the TF101 without 3G!
I went ahead with installing the latest version available on the ASUS site for the TF101G version via SOP, and that actually worked! (UpdateLauncher_WW_epaduserV8_6_6_10.zip)
Hopefully this will not cause any issues.
Is it possible for me to rollback/reinstall the correct version of the firmware for my TF101, instead og the TF101G version? I would prefer that since I will not get OTA notifications otherwise.
Anyone have any thoughts about how to fix that?
tHIS SHOULD HELP, IN CASE your tab has pre-b7 serial i.e b4,b5,b6(check at bottom base). it will format all partitions in nvflash mode, the process is automated.
http://tabletroms.com/forums/transf...stock-3-2-recovery-roms-unbricking-tools.html
Thanks mughalgxt!
That was exactly what I needed, worked perfectly ;-)
I also got the notification for 3.2.1 soon after I had flashed to the correct firmware for my TF101.
Awesome!
just wondering if anyone else has received this update? it was a small 17.18MB. not sure exactly what it did. still on 4.2.1 attached is a screen shot.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
kurtis.austin2 said:
just wondering if anyone else has received this update? it was a small 17.18MB. not sure exactly what it did. still on 4.2.1 attached is a screen shot.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Click to expand...
Click to collapse
Just checked after reading this and downloading it now ota. It says it for system stability. About to install we'll see.
wonderful, so i'm not dreaming that it just happened. i just got home from a 12 hour day at work, and opened up my tablet and the notification was there waiting for me. don't know where to check on the asus website for change log or anything?
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
kurtis.austin2 said:
wonderful, so i'm not dreaming that it just happened. i just got home from a 12 hour day at work, and opened up my tablet and the notification was there waiting for me. don't know where to check on the asus website for change log or anything?
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Click to expand...
Click to collapse
Yea just installed ok. Haven't gotten into it to if there were much changes yet. Probably nothing immediately noticeable except it reoptimizes the apps on first start up. If looking for log here's the site but doesn't yet look like it was posted and probably won't be for couple days but when does can check here.
http://support.asus.com/download.as...300T&p=28&s=1&os=32&hashedid=8BmzkQ4yoz5WzBrW
The other things to check is to see if motochopper and other root methods work and if any one loses root we'll have to see if any one with root by motochopper method loses it which tell you truth probably not too much danger in that as it's only a minor update. I'm still waiting to root myself but would like to see what happens? If some one tries to root after the update if any thing changed.
System update failure
I received a notification of an update which I downloaded and told the system to apply. It shut down the system and began the update and then failed with a dead android with a red explanation point and the message update failed.
I rebooted my tablet and got a message that the original configuration was restored.
If anyone has had success in applying the update (US version) please let me know where I can get a valid copy to try. The links to the Asus site seem to point to the old 4.2.1 version.
Thanks.
Who can lay out an update?
tomlogan1 said:
I received a notification of an update which I downloaded and told the system to apply. It shut down the system and began the update and then failed with a dead android with a red explanation point and the message update failed.
I rebooted my tablet and got a message that the original configuration was restored.
If anyone has had success in applying the update (US version) please let me know where I can get a valid copy to try. The links to the Asus site seem to point to the old 4.2.1 version.
Thanks.
Click to expand...
Click to collapse
Sorry to hear that but it'll be on asus website it just takes them a couple days to a week or so to post it. Were you rooted by perhapse the motochopper method. There's cases if there are frozen apps and etc and if everythings not back in place as in normal use it would fail. Not sure it always applies but have heard of this. Also not sure if you want to try a factory reset and see if you get a prompt for the update again again works in some cases but not always and if that doesn't work the last thing you can do is if your not unlocked and can still get otas is to downgrade back to 4.1.1 and just go through update process again after it reboot the downgrade.
I wonder if the update addresses some of the issues we have been experiencing, random reboots, bluetooth permissions issue. There are a couple others that were brought up on the CROMI ROM thread.
On a stock firmware no random reboots, it only on CROMI
Updated (europe). All good. I had to do a 'restore root' and reboot twice with Voodoo OTA, to successfully restore root.
I am on the 4.1 style launcher and I noticed the clock font (bottom-right) has changed in this update. Looks bold and condensed now. Obviously this hints to more than just stability changes. Anyone on the 4.2 style launcher? I am curious to see if it has been improved in this update.
ASUS TF300T Firmware Update v10.6.1.15.3
I'm running it now, checked online for release notes before installing but found nothing but this thread so screw it, I just installed.
I'm not rooted as I don't want to void my warranty just yet and I'm cool with the stock rom.
I did switch to stock 4.2 launcher before installing the update to see if any changes there as Evan_ was curious.
Don't like 4.2 launcher myself because of the location of the buttons swap to middle and the ASUS Custom settings bar is odd to me.
Anyways, its running and I'll check back in if I find any changes.
Successful System Update
JOP40D.US_epad-10.6.1.15.3-20130416
Noticed Time & Date in status bar drop-down. (Don't recall that shown)
Switching back to 4.1 Launcher. (Prefer it as configuration is better, I hate the back button in the middle on 4.2.)
Noticed a Font change for the clock and all the stock ASUS widgets.
Once again tbdawg has been kind enough to provide the new firmware download for those who didn't receive it.
Please see post #234 0f this thread and give him a thanks!
Here is the link for the download. - dlpkgfile_4.2.1_Update2
tobdaryl said:
Once again tbdawg has been kind enough to provide the new firmware download for those who didn't receive it.
Please see post #234 0f this thread and give him a thanks!
Here is the link for the download. - dlpkgfile_4.2.1_Update2
Click to expand...
Click to collapse
Thanks for the link. What is the process to manually install this update? I have only done the OTA updates. I am rooted, but otherwise stock.
tomlogan1 said:
Thanks for the link. What is the process to manually install this update? I have only done the OTA updates. I am rooted, but otherwise stock.
Click to expand...
Click to collapse
This post courtesy of atzhory
dlpkgfile install manual for unlocked dev
http://forum.xda-developers.com/show....php?t=1803090
Manually update rooted stock
tobdaryl said:
This post courtesy of atzhory
dlpkgfile install manual for unlocked dev
http://forum.xda-developers.com/show....php?t=1803090
Click to expand...
Click to collapse
I have placed the update file on a MicroSD card and the tablet just wants to unzip it It shows the zip file then the following:
FOLDER META-INF
FOLDER patch
FOLDER system
blob
At the bottom of the screen there are options to
Cancel Text encoding Extract
I am not sure how to proceed.
Thanks
tomlogan1 said:
I have placed the update file on a MicroSD card and the tablet just wants to unzip it It shows the zip file then the following:
FOLDER META-INF
FOLDER patch
FOLDER system
blob
At the bottom of the screen there are options to
Cancel Text encoding Extract
I am not sure how to proceed.
Thanks
Click to expand...
Click to collapse
I'm having trouble myself. This had worked in the past but is failing on this update.
I'll update you when I find the answer. I am feverishly searching.
Alexey71 said:
On a stock firmware no random reboots, it only on CROMI
Click to expand...
Click to collapse
No read the Q%A section, a lot of people were complaining about how horrible the OTA update was .
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
aerdely said:
Sorry to hear that but it'll be on asus website it just takes them a couple days to a week or so to post it. Were you rooted by perhapse the motochopper method. There's cases if there are frozen apps and etc and if everythings not back in place as in normal use it would fail. Not sure it always applies but have heard of this. Also not sure if you want to try a factory reset and see if you get a prompt for the update again again works in some cases but not always and if that doesn't work the last thing you can do is if your not unlocked and can still get otas is to downgrade back to 4.1.1 and just go through update process again after it reboot the downgrade.
Click to expand...
Click to collapse
Since I am not unlocked, what is the process to downgrade to 4.1.1? Every attempt to upgrade from the MicroSD have failed, and, yes, I have tried multiple MicroSD cards from 4 GB to 32 GB and had failures in each instance.
Thanks.
tomlogan1 said:
Since I am not unlocked, what is the process to downgrade to 4.1.1? Every attempt to upgrade from the MicroSD have failed, and, yes, I have tried multiple MicroSD cards from 4 GB to 32 GB and had failures in each instance.
Thanks.
Click to expand...
Click to collapse
Really no need for sdcard. As long as you downloaded the 10.4.2.20 firmware from asus website in my case I didn't have to rename it. Just download and unzipped once and placed on root internal memory. You can just initiate the update by either inserting or removing the sdcard if it on root of internal. Just to be safe after unzipping once make sure it's name {US_epad-user-10.4.2.20.zip} or depending on firmware version put WW or CN and etc. In place of US. Should pick it right up.
Just to be clear are you trying to upgrade or downgrade?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
aerdely said:
Really no need for sdcard. As long as you downloaded the 10.4.2.20 firmware from asus website in my case I didn't have to rename it. Just download and unzipped once and placed on root internal memory. You can just initiate the update by either inserting or removing the sdcard if it on root of internal. Just to be safe after unzipping once make sure it's name {US_epad-user-10.4.2.20.zip} or depending on firmware version put WW or CN and etc. In place of US. Should pick it right up.
Just to be clear are you trying to upgrade or downgrade?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I was attempting to get the new OTA upgrade that failed on my tablet. Found out something interesting about this upgrade approach. If I put in an upgrade of the same level like 10.6.x.x and was already at 10.6.x.x the system ignored it. But if I put in 10.4.x.x the system identified it and offered to do a downgrade, but would have erased everything and I wasn't ready to do that, but I may have to do so.
---------- Post added at 09:11 AM ---------- Previous post was at 09:09 AM ----------
tobdaryl said:
I'm having trouble myself. This had worked in the past but is failing on this update.
I'll update you when I find the answer. I am feverishly searching.
Click to expand...
Click to collapse
I have tried the SD card upgrade method with no luck but found that if I put in a lower level like 10.4.x.x the system saw it as a downgrade and would downgrade the system but would erase all my data, which I was not ready to do, but at least I have a path to should I so select.
So it appears that some people (myself included) are having issues with their new Nexus 7. Specifically, where it is failing to install the second OTA update, which brings the tablet to version JSS15J. The first update (which is almost instant) works, but the second 50+MB one fails after rebooting into stock recovery.
It is failing because the file "/system/app/PrebuiltGmsCore.apk" is failing the sha1 checksum check. Why is this happening? Because the tablet is looking for a different version of the file then what is installed on some of our tablets. Why do different people have different versions? I have no idea. But it's certainly an issue for a few people including myself. I tried various standard work arounds but came up with no fix to get the OTA update, as is, to install. Then I decided to see if that was the only issue present and develop a work around.
I'm pleased to say that:
1) The PrebuiltGmsCore.apk file is the only one that breaks the OTA update. Everything else is fine.
2) I was successful in fixing this by creating a custom OTA update zip and installing it on my tablet.
3) I'm providing this modified update.zip for people to load on their tablets if they are having the same issue.
A couple of notes first...
Obviously, flash this at your own risk.
You NEED TO HAVE A CUSTOM RECOVERY for it to work. TWRP has already been ported over, so install that first.
Once you are in custom recovery, flash this file just like any other update.
Lastly, you should only download/install this if you are having the problem where the second OTA update fails. If you are currently running JSS15J, this update will fail (as it should).
This is 98% stock OTA update. All I did was some minor tweaks to fix the issue. Specifically:
1) I removed both the check for the PrebuiltGmsCore.apk file as well as the patching of it (since this fails).
2) I took the full JSS15J version of PrebuiltGmsCore.apk and built it directly into the update.
3) I removed the parts of the OTA update that mess with custom recovery. It will not install the /system/boot-from-recovery.p or /system/etc/install-recovery.sh files.
Once you install this, your tablet should be running identically to one that didn't suffer this issue.
Outside of using this, the only other option (AFAIK) is to wait until Google releases the full factory images and flash everything manually.
A big thanks to ATGAdmin for providing the stock JSS15J system dump that let me extract the updated PrebuiltGmsCore.apk file.
So without further ado, here is the update:
http://core.routed.com/JSS15J-Update.zip
Enjoy, and let me know if you have any questions.
Question: was your nexus 7 missing the wallpaper that they've been marketing with?
Sent from my Nexus 4 using xda app-developers app
shredder47 said:
Question: was your nexus 7 missing the wallpaper that they've been marketing with?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yes.
And I bought mine from Best Buy, which seems to be a common denominator with both of those issues.
However, I just checked, and I have that wallpaper now after installing this update.
Yeah sounds like that's the common denominator... I'm out right now but I'll try this out when I get home, thanks man!
Sent from my Nexus 4 using xda app-developers app
Thanks so much! This worked for me after trying other options failed. Mine was from Best Buy also.
Oh, one other quick note:
As I wanted to leave this as close to the stock OTA update as possible, this WILL remove root. Technically, the 'su' binary will remain, but it will lose it's suid permissions. It will also remove the daemon launcher (which is installed as the install-recovery.sh file).
So make sure to flash the root zip after installing this update.
One more thing:
While there aren't many mods out there yet that will mess with the update, eventually there will be. This custom update will check and verify that everything else (except that one file) is stock. So if you made any other modifications to any other system file (ie: build.prop, etc.), it will fail just like any other OTA. Your best bet is to install this before tweaking.
Worked great man!
Also, your download was rather slow so if you don't mind I made a mirror on mega: https://mega.co.nz/#!aE4CwJZB!J7QtUlqXhthhZcpPOUriaQ_u861k7rAGdHffRCmkQao
I have one from best buy and it updated just fine (both updates). I guess it's just luck of the draw.
Sent from my Nexus 7 using Tapatalk HD
Nburnes said:
Worked great man!
Also, your download was rather slow so if you don't mind I made a mirror on mega: https://mega.co.nz/#!aE4CwJZB!J7QtUlqXhthhZcpPOUriaQ_u861k7rAGdHffRCmkQao
Click to expand...
Click to collapse
Awesome, glad to hear! And sure, that's perfectly fine with me.
It's on a 100Mb pipe, but the data center occasionally has some bad routing that makes certain destinations slow. Can't complain since I get a dedicated server for $59/month .
fosser2 said:
I have one from best buy and it updated just fine (both updates). I guess it's just luck of the draw.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Yeah, I believe it to be a minority of tablets. Maybe just a bad batch that all happened to get sent to Best Buy. As time goes on and more people get them we'll see how wide spread it is. I'm curious to see what Google's official fix will be.
Yeah, got mine from best buy too, the 2nd update stood at the boot screen. I just rebooted and it's back to normal
Sent from my Nexus 4 using Tapatalk 4 Beta
paranoid android85 said:
Yeah, got mine from best buy too, the 2nd update stood at the boot screen. I just rebooted and it's back to normal
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Did you check to see if the update worked? If your version is still JWR66N, then it failed and you will either need to flash this or wait for an official fix from Google.
phonic said:
Did you check to see if the update worked? If your version is still JWR66N, then it failed and you will either need to flash this or wait for an official fix from Google.
Click to expand...
Click to collapse
I brick my nexus. Can someone upload nandroid backup please?
phonic said:
... Why is this happening? Because the tablet is looking for a different version of the file then what is installed on some of our tablets. Why do different people have different versions? I have no idea. But it's certainly an issue for a few people including myself. ...
Click to expand...
Click to collapse
Interesting. My update worked (mostly because oldblue910 was doing it). LOL
I got mine at Walmart and noticed one of the box labels had been modified. There is an extra label covering one label on the box (also, there are labels on both ends). It is barely noticeable. I tried to remove the one on top (to peek) but it started to tear.
I theorize mine was part of a modification process. Do you think some of those failed units at Best Buy *might* have missed the modification process?
Bob Smith42 said:
Interesting. My update worked (mostly because oldblue910 was doing it). LOL
I got mine at Walmart and noticed one of the box labels had been modified. There is an extra label covering one label on the box (also, there are labels on both ends). It is barely noticeable. I tried to remove the one on top (to peek) but it started to tear.
I theorize mine was part of a modification process. Do you think some of those failed units at Best Buy *might* have missed the modification process?
Click to expand...
Click to collapse
I'm not really sure. After looking at the first OTA update that oldblue910 posted, it definitely indicates that it was modified by that. If so, it had to have initially passed that first check. Why some units fail the second check makes little sense to me. The lack of the official wallpaper is also weird.
Additionally, that first OTA clearly shows that these devices were rushed. The fact that they were sent out with developer keys is just really bad QA.
My device, hardware wise, seems to be perfect. So I don't want to roll the dice and try to get another one, especially if the only issue is some minor software glitch that I already corrected. I haven't had a chance to really play with it yet, as I've been spending my time backing up/restoring files, so I'll see how it goes.
Thanks for this. Bought mine at Best Buys too and had the update fail.
Edit: TWRP gave the option to fix SU after flashing that zip and it seemed to work. I'll probably refresh zip anyways but TB still works.
Sent from my Nexus 4 using Tapatalk 4 Beta
stab244 said:
Thanks for this. Bought mine at Best Buys too and had the update fail.
Edit: TWRP gave the option to fix SU after flashing that zip and it seemed to work. I'll probably refresh zip anyways but TB still works.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, you should reapply the root zip.
The OTA update does two things in this regard. It removes the two 'recovery recovery' files, and it also removes the suid bit from the su binary. The TWRP su fix will reapply the suid bit to 'su' (thus making it actually work), but it doesn't put back the SuperSU daemon launcher (/system/etc/install-recovery.sh). By applying the root zip again, it will fix both of these.
I thought about removing the part of the update that deletes this file, but again I wanted to keep it as stock as possible. Also, for people who hadn't rooted yet but do have a custom recovery, it would help keep it custom and not require them to manually remove those files that would (stock) reset the recovery back.
I also purchased mine at Best Buy, therefore I also have the problem.
What exactly does this 2nd update do? Is it a drastic improvement over JWR66N?
xene97 said:
I also purchased mine at Best Buy, therefore I also have the problem.
What exactly does this 2nd update do? Is it a drastic improvement over JWR66N?
Click to expand...
Click to collapse
If you are asking what files it changes, you can look inside the zip file and see all of that. It's fairly extensive. The vast majority are patches to many components of the operating system and included applications. The first OTA update was only a few hundred kilobytes, while this one is 50megs, so a lot was updated.
If you are asking what the end-user result or benefit is between the two, I am not sure. I spent most of my time working on trying to get the update working, and spent very little time using the tablet before I was successful. So I can't comment about whether the update improves anything. However, others have said that it did help to resolve some issues they experienced before hand.
In any case, the new N7 was released quite quickly and we know that the factory installed OS had some issues. The fact that there were two OTA updates before the device was even released show that Google needed to fix a lot of stuff. While future updates (Key Lime Pie anyone?) will be more optional as it focuses on enhancements and upgrades, these two updates are significantly more important.
phonic said:
If you are asking what files it changes, you can look inside the zip file and see all of that. It's fairly extensive. The vast majority are patches to many components of the operating system and included applications. The first OTA update was only a few hundred kilobytes, while this one is 50megs, so a lot was updated.
If you are asking what the end-user result or benefit is between the two, I am not sure. I spent most of my time working on trying to get the update working, and spent very little time using the tablet before I was successful. So I can't comment about whether the update improves anything. However, others have said that it did help to resolve some issues they experienced before hand.
In any case, the new N7 was released quite quickly and we know that the factory installed OS had some issues. The fact that there were two OTA updates before the device was even released show that Google needed to fix a lot of stuff. While future updates (Key Lime Pie anyone?) will be more optional as it focuses on enhancements and upgrades, these two updates are significantly more important.
Click to expand...
Click to collapse
Thanks for the clarification!
Hello to all,
I have a big problem. I own Nexus 7 (2012) version with 16gb, but when I flashed KitKat 4.4.2 (KOT49H) via Wug's Nexus Root Toolkit v1.7.9, my Nexus went down to 8gb version (actually, I got only 5.9gb free space).
How is this posible? To went from 16gb model to 8gb model and most important, how do I get back to original 16gb of storage?
edit:haha, I don't know how but solution was this: I did full wipe and format data via cwm. Then it said that I dont have OS installed. So, again I used Wug's Nexus Root Toolkit v1.7.9, only now I flashed 4.4 KRT16S. And on my biggest surprise, now I got 27gb free space. I loaded it with movies and it's real space.
I thought that I know something about android, but now I'm confused very much. Merry Christmas to me with this extra gift
P.S. And to all of you ofcourse.
P.P.S. Would somebody like to try this also? Maybe you get extra 16gb, too!
Screen shot?
Sent from CAMACHO, my Verizon G2 (VS980) running PAC ROM 4.3.
Do a search. This isn't a new phenomenon; it only happens to rooters. Somehow, an undersized ext4 filesystem gets created in the userdata partition (which is substantially larger).
The exact origin of the problem is not clear, but is probably a bug in the bootloader.
The solution is always the same - to backup the entire tablet and recreate the /data filesystem (either by having the bootloader do it via a fastboot command or using "mke2fs" with a custom recovery).
While it is technically possible for a device to come from the factory this way, I highly doubt that is what occurred. And no, this isn't some kind of voodoo magic - if you can build a 29 GB filesystem on your device, that's only because there is a 32 GB flash chip in there.
In any event, if you look in the kernel log (search for messages with "mmc" in them) shortly after the tablet has booted, youll see the kernel identify the chip and it's capacity. That's a whole lot easier than speculatively unloading and reloading many GB of files.
Vepaot said:
Screen shot?
Sent from CAMACHO, my Verizon G2 (VS980) running PAC ROM 4.3.
Click to expand...
Click to collapse
I'll hope that I will get screenshots available during this evening, because tablet is not with me for the moment.
bftb0 said:
Do a search. This isn't a new phenomenon; it only happens to rooters. Somehow, an undersized ext4 filesystem gets created in the userdata partition (which is substantially larger).
The exact origin of the problem is not clear, but is probably a bug in the bootloader.
The solution is always the same - to backup the entire tablet and recreate the /data filesystem (either by having the bootloader do it via a fastboot command or using "mke2fs" with a custom recovery).
While it is technically possible for a device to come from the factory this way, I highly doubt that is what occurred. And no, this isn't some kind of voodoo magic - if you can build a 29 GB filesystem on your device, that's only because there is a 32 GB flash chip in there.
In any event, if you look in the kernel log (search for messages with "mmc" in them) shortly after the tablet has booted, youll see the kernel identify the chip and it's capacity. That's a whole lot easier than speculatively unloading and reloading many GB of files.
Click to expand...
Click to collapse
I'll try this voodoo method with friend's nexus 7 which is 8gb version and post results. It is really very strange that I manage to do this. I know that somebody much smarter then me will already came up with this findings, but I live in a hope :laugh: I hope that I accidentally somehow unlocked disc space. I already got theory that all nexus 7 (wifi) devices are the same in hardware and that they are only with software locked to 8, 16 or 32gb :laugh:
I have a D802 with 32GB. I previously flashed ROMs on my LG G2 years ago, decided to move away from the custom ROMs after I semi-bricked it last year, it's now updated with fresh firmware, Lollipop 5.0.2.
However when plugged into my PC it says: Used Space: 1.02 GB Free Space: 10.6 GB
Should it not be closed to 32GB free??
Is there any software I can use to find/delete/free missing partitions?
I'm a little out of the loop at the moment, any help appreciated.
Don't rely on the pc for this - the MTP protocol can be weird at times.
What does Settings->Storage say on the phone?
runekock said:
Don't rely on the pc for this - the MTP protocol can be weird at times.
What does Settings->Storage say on the phone?
Click to expand...
Click to collapse
It says
Total Space: 32GB
Available: 9.60GB
Then there is a huge part of the bar in red which represents Misc: 21.40GB......
Doesn't sound good. On my 32 GB phone, misc is only 7.69 GB.
Maybe you flashed a 16 GB rom at one time? It has been known to resize the data partition.
There is a fix in this thread: http://forum.xda-developers.com/showthread.php?t=2470207&page=34
However, the fix is a bit dangerous. Ask yourself: are you feeling lucky?
runekock said:
Doesn't sound good. On my 32 GB phone, misc is only 7.69 GB.
Maybe you flashed a 16 GB rom at one time? It has been known to resize the data partition.
There is a fix in this thread: http://forum.xda-developers.com/showthread.php?t=2470207&page=34
However, the fix is a bit dangerous. Ask yourself: are you feeling lucky?
Click to expand...
Click to collapse
Not only am I not feeling lucky but I have nothing to lose. That looks complicated, surely there's an easier way?
So first I need to downgrade from Lollipop to KitKat (tutorial?).
I'm sorry, I don't know more than that. I never had the problem myself.