So here's the outline of the story, phone hard bricked, bought a new mainboard because I don't have 200+ for a new decent phone, main board comes in, works, but system takes up 18+gb of the 32, I flash a new factory image (using nexus root toolkit) in case something is in there thats shouldn't be, accidentally overwrite my recovery point trying to go fast, my phone now boots showing 16, if I go to bootloader it lists under variant bullhead lgh798 32gb, I've tried factory reset, doesn't fix it, tried different system files, still still nothing, tried twrp resize, leaves it the same size. Anyone know what I should do?
Edit for more info-Using a app called disk info I have a Data partition of 10.6 gb, and one called /mnt/runtime/default/emulated of the same size, system with 3.
Related
First off, this will not let you convert a 16GB phone to a 32GB phone. If you try this on a phone that really is a 16GB device, you run a large change of bricking the device and requiring a jtag. These instructions and the files linked are only intended to be used on a Sprint SGS3.
I recently received a Sprint SGS3 32GB that was flashed as if it was a 16GB SGS3. The sticker under the battery said it was a 32GB model and I confirmed that it really did have a 32GB emmc chip inside by using cat /proc/partitions which showed:
Code:
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
A 16GB model will look like this:
Code:
179 0 15388672 mmcblk0
However, because mine was flashed wrong, I only had 12GB of storage instead of 26GB. To correct this problem, you will need a few files:
32 GB pit file and linked just in case someone needs it: 16GB pit file
A full copy of the stock firmware. The one I used is here.
Odin 3.07
USB drivers
You'll also want to back up everything to your removable sdcard. This process will require you to format your entire /data partition which includes all your apps and anything on your "internal sdcard" which includes pictures, backups, etc.
Make sure that you have all of the above files downloaded and have installed the USB drivers. You'll need to extract Odin and the .tar file from inside the firmware zip to known locations on your computer. Make sure your battery has a good charge. Lastly, I take no responsibility if something goes wrong. Also this will *not* trip the flash counter. You're flashing signed Samsung images that do not count towards your flash counter.
Power off your phone.
Hold down volume down and the home button then press and hold power until a screen shows up on your phone.
Release the buttons and press volume up to put your phone in download mode.
Open Odin on your PC
Connect your phone to your computer.
A COM box should light up and Odin should say something like "Attached" after your phone is detected.
Click on the PIT button and browse to and select the 32GB pit file.
Click the PDA button and brose to and select the firmware file. After you select the firmware file, Odin may verify the md5 which may take a few moments.
Click on start and go grab a soda. It will take upwards of 10 minutes to fully flash your device.
Cross your fingers and knock on wood and hope that the phone reboots successfully. On first boot it may boot to stock recovery to wipe cache.
When it boots to Android you probably still only have 12GB of storage, but that's (probably) ok. We'll fix it now.
Go into Settings -> Backup & Reset -> Factory Reset and choose to reset your phone.
Your phone will reboot to stock recovery and perform a full format of all of your data then reboot.
When finished rebooting, you should now have ~26GB of internal storage. Congrats.
Note, if you have trouble getting your phone to be detected by Odin, try a different USB cable and USB port.
I've confirmed that everything works on my phone after doing this. I've been able to activate, do PRL and profile updates, get 3G, 4G LTE, SMS, wifi, bluetooth, NFC, front and rear cameras, etc are all still working.
Dees_Troy said:
First off, this will not let you convert a 16GB phone to a 32GB phone. If you try this on a phone that really is a 16GB device, you run a large change of bricking the device and requiring a jtag. These instructions and the files linked are only intended to be used on a Sprint SGS3.
I recently received a Sprint SGS3 32GB that was flashed as if it was a 16GB SGS3. The sticker under the battery said it was a 32GB model and I confirmed that it really did have a 32GB emmc chip inside by using cat /proc/partitions which showed:
Code:
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
A 16GB model will look like this:
Code:
179 0 15388672 mmcblk0
However, because mine was flashed wrong, I only had 12GB of storage instead of 26GB. To correct this problem, you will need a few files:
32 GB pit file and linked just in case someone needs it: 16GB pit file
A full copy of the stock firmware. The one I used is here.
Odin 3.07
USB drivers
You'll also want to back up everything to your removable sdcard. This process will require you to format your entire /data partition which includes all your apps and anything on your "internal sdcard" which includes pictures, backups, etc.
Make sure that you have all of the above files downloaded and have installed the USB drivers. You'll need to extract Odin and the .tar file from inside the firmware zip to known locations on your computer. Make sure your battery has a good charge. Lastly, I take no responsibility if something goes wrong. Also this will *not* trip the flash counter. You're flashing signed Samsung images that do not count towards your flash counter.
Power off your phone.
Hold down volume down and the home button then press and hold power until a screen shows up on your phone.
Release the buttons and press volume up to put your phone in download mode.
Open Odin on your PC
Connect your phone to your computer.
A COM box should light up and Odin should say something like "Attached" after your phone is detected.
Click on the PIT button and browse to and select the 32GB pit file.
Click the PDA button and brose to and select the firmware file. After you select the firmware file, Odin may verify the md5 which may take a few moments.
Click on start and go grab a soda. It will take upwards of 10 minutes to fully flash your device.
Cross your fingers and knock on wood and hope that the phone reboots successfully. On first boot it may boot to stock recovery to wipe cache.
When it boots to Android you probably still only have 12GB of storage, but that's (probably) ok. We'll fix it now.
Go into Settings -> Backup & Reset -> Factory Reset and choose to reset your phone.
Your phone will reboot to stock recovery and perform a full format of all of your data then reboot.
When finished rebooting, you should now have ~26GB of internal storage. Congrats.
Note, if you have trouble getting your phone to be detected by Odin, try a different USB cable and USB port.
I've confirmed that everything works on my phone after doing this. I've been able to activate, do PRL and profile updates, get 3G, 4G LTE, SMS, wifi, bluetooth, NFC, front and rear cameras, etc are all still working.
Click to expand...
Click to collapse
Fantastic!! Just a few things. I got me and my wife the 32GB S3 the same way you did :angel:, akmzero put me on to your thread. With mine, I followed the instructions to the letter, and there was no second factory reset needed. On my wife's, I flashed the only the 32GB pit and it worked. I got the idea from just flashing .pit's on my s1 years ago.
Thanks for this, you saved my brain.
Is that 16gb pit file the one for the 16gb phone? So I could re flash mine if I needed too?
Sent from my SPH-L710 using xda app-developers app
dav3wash said:
Fantastic!! Just a few things. I got me and my wife the 32GB S3 the same way you did :angel:, akmzero put me on to your thread. With mine, I followed the instructions to the letter, and there was no second factory reset needed. On my wife's, I flashed the only the 32GB pit and it worked. I got the idea from just flashing .pit's on my s1 years ago.
Thanks for this, you saved my brain.
Click to expand...
Click to collapse
The same way he did?
Awesome. Just had this happens to a friend and can fix it.
Worked perfectly thank you again
Sent from my SPH-L710 using xda app-developers app
freeza said:
The same way he did?
Click to expand...
Click to collapse
Hit me up on google talk: [email protected]
dav3wash said:
Hit me up on google talk: [email protected]
Click to expand...
Click to collapse
Sorry to kick a dead post, but would the 16gb pit work for the cricket s3? If not, could it be modded to work?
do you have a pit to v 4.1.2 ?
Isn't it possible there was a reason your phone was factory formatted from a 32 to a 16? Perhaps mem beyond the 16 mark was bad and they just repackaged as a 16 when they formatted it as such?
Would re-opening this other bank of memory potentially expose the phone to errors when a bad block is hit?
edufur said:
Isn't it possible there was a reason your phone was factory formatted from a 32 to a 16? Perhaps mem beyond the 16 mark was bad and they just repackaged as a 16 when they formatted it as such?
Would re-opening this other bank of memory potentially expose the phone to errors when a bad block is hit?
Click to expand...
Click to collapse
Yes, but most people mess up with Odin and just flash anything without research. Most likely the case.
So I'm brand new to Android (coming from iPhone) and my friend convinced me to try and get Cyanogenmod on my phone.
Somewhere along the line I used command prompt on windows to transfer a 2GB .zip file to /system or something. This folder is nowhere in the Nexus device when you plug it in to view files.
I have no idea how to locate it or delete it (along with any other files I transferred to various system locations).
I'm basically at factory reset with nothing on my phone and it still says I have 8GB free of 10.6 - so that 2GB file is hidden somewhere I imagine.
Any ideas/advice is appreciated.
if you just flash the factory system.img file it will override whatever you have in the system folder.
You won't be able to see that with a pc viewer.
My advise is flash the stock image and then take a week and learn what you are doing. Compared to the iPhone you just skipped like 5 grades. If you do something wrong and end up with a brick then you are out a ton of money and will have to get a new device.
Hello,
I have an Oppo Find 7 for a while and I always thought that the Color OS is not very good, and specially, it comes with a very limiting partition division.
So, when I could no longer decide on which Apps to keep and which to uninstall, since I had no longer space left on my phone due to the stupid small partition for applications, I decided to format my phone, reconfigure the partitions and install a new ROM (CM 13).
I had done it often on my lapton, how difficult could it be to do it on the phone?
It all seemed to work fine, but when I started my "new" phone with CM I noticed that something was wrong. I tried to use the camera and it showed an error saying I did't have a storage device.
Well, I was sure I had left enough space for photos in the other (not OS) partition, and I had also the SD card.
I went to Settings->Storage and I saw that my phone was recognising the OS partition only (about half of all internal storage) and had a portable storage device called "sdcard0" (not the actual SD card) reading "Damaged" below.
I've tried to erase and format that partition, but it shows an error reading "command '41 volume partition disk: 179_0 public' failed with '400 41 Command failed'".
I've tried to rearrange the partitions again, to reinstall CM13, but nothing worked, so I just accepted that my phone could not take pictures. Everything that did't require to have a file system worked fine (well, I cannot see the naked ladies pictures my friends share on whatsapp). This was a few months ago, so I don't remember precisely what I did.
Recently I decided that I actually need a phone that takes pictures, so I went back to trying to fix it.
Unfortunately, I can't. At least without some custom help. I've read plenty of tutorials, forum pages, but there's always something that doesn't work in my case.
Here's what I can do with my phone:
- It boots
- It works
- Computer recognises it
- adb recognises
Here's what I can't do:
- Have any files (the file system is broken)
- Take photos
- Restart with bootloader - when I tried, the screen just shows a sitting penguin for a few seconds and then turns off. I do remember to be able to do so, but I can't now.
I've tried to load bootloader though the phone's interface, through the power+volume down button combination and through adb. They all had the same result. The stupid penguin and then darkness.
Can someone help me?
Hello, you're phone is not bricked. What is the exact name of you're ROM ? Do you have make LVM, or chinese storage partion?
I recently bought a used Nexus 5x with an unlocked Bootloader running Marshmallow, MTC20K. On the Bootloader screen it says the model is an H791 with 32GB of internal storage but then when I boot it up to Android, I'm only seeing 16GB of storage (10.5ish for Data)). After flashing TWRP (I tried with 3.0.2 and 3.2.2) and checking the phone's vitals, TWRP reads: 10,807MB for Data, 2,975MB for System, 908MB for Cache. The weird thing is that TWRP is telling me that I'm only using 2,502MB of Data but that I've got 1,204MB of Data free.... so even here, it's pretty clear that something's whacked.
So, I found some other folks that seemed to have a similar problem (there’s more, but these illustrate the issue):
A1) https://productforums.google.com/forum/#!topic/nexus/gHNW3Xv8yp8
A2) https://www.reddit.com/r/nexus5x/comments/46w0nc/psa_if_your_32gb_n5x_is_showing_10gb_of_storage/
A3) www.**********.com/your-32gb-nexus-5-now-shows-only-16gb-here-is-how-to-fix-it/ -replace the asterisks with "droidreviews"
Unfortunately, none of the solutions offered in the above threads worked. So that brought me to more drastic potential solutions like these:
B1) https://forum.xda-developers.com/ne...to-unbrick-t3251740/post63889395#post63889395
-my phone isn’t bricked and I had bad luck with an HTC device years ago after re-locking the Bootloader, so I’m a bit hesitant to re-lock the Bootloader and I’m not even sure if this solution would fix the 32GB reading 16GB issue when the common solutions (points A1-A3) didn’t work.
B2) https://forum.xda-developers.com/google-nexus-5/help/nexus-5-32gb-wont-to-internal-storage-t3313593 and https://forum.xda-developers.com/go...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301 – these are both links for the Nexus 5 and I have no idea if they’d work on a a 5X or if the TOT from point B1 would essentially offer the same solution, by re-flashing the GPT partition, that the latter link in B2 articulates…
I’ve also tried flashing Nougat and Oreo builds (official flavors from Google), but they didn’t fix the storage issue and, in fact, just created another issue: I can no longer connect to WI-FI. Going back to Marshmallow allows me to connect to WI-FI, but I thought it was weird that Nougat and Oreo biffed it. I also tried the common solutions found through Googling for fixing alleviating this issue, but to no avail. Anyway, I’m bringing the WI-FI issue up in this thread because perhaps the issues, the issue with the misrepresented storage as well as the issue with WI-FI, aren’t mutually exclusive.
This may be be a little conspiratorial but since this solution: TWRP => "wipe" menu => checked "data" => "repair or change file system" => "resize" seems to work for so many people and it’s not working for me, I’m wondering if the person who sold me the phone somehow flashed a boot.img displaying 32GB when the phone is in reality 16GB… is that even possible?
Anyway, if anyone has faced similar quandaries and arrived at a solution or knows if the solutions in points B1 and B2 would solve my dilemma, I’d be game to hear your 2 cents.
Ok, so I tried this: https://forum.xda-developers.com/ne...to-unbrick-t3251740/post63889395#post63889395 (point B1 from my original post) but no go. Still only seeing 10,55gb after booting into Android and this time, when the setup wizard starts its magic, I'm greeted with a pop-up that there's some internal error and I should contact the manufacturer.
Any ideas?
I tried the solutions listed here too, but to no avail: https://forum.xda-developers.com/nexus-5x/help/incorrect-storage-capacity-stock-7-0-t3460425
Interesting discovery though; on MTC20K, when I install this cm-14.1-20161225-NIGHTLY-bullhead.zip my storage is visible as 32GB but the bulk of it appears to be devoured by the "System" partition (see attached screenshot). When I go back to Marshmallow however, my visible storage reverts back to what one would see if one had a 16GB Nexus 5X.
Any ideas?
jacksmack said:
I tried the solutions listed here too, but to no avail: https://forum.xda-developers.com/nexus-5x/help/incorrect-storage-capacity-stock-7-0-t3460425
Interesting discovery though; on MTC20K, when I install this cm-14.1-20161225-NIGHTLY-bullhead.zip my storage is visible as 32GB but the bulk of it appears to be devoured by the "System" partition (see attached screenshot). When I go back to Marshmallow however, my visible storage reverts back to what one would see if one had a 16GB Nexus 5X.
Any ideas?
Click to expand...
Click to collapse
Do a factory reset in the stock recovery. That will get your 32 gb.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Do a factory reset in the stock recovery. That will get your 32 gb.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Did that too but it didn't work. It seems my GPT table is somehow messed up. I got the phone 2nd hand so I have no idea what the original owner tried to flash (it was supposed to be a fresh "display model").
Hi, I have a Desire with a custom ROM on it, the system running from an SD card. The screen died in an instant with no apparent cause (the phone is working, because i got called and I could talk with the black screen). I tried the electronics part with an other screen (same SLCD, I didn't mess it up), but didn't work for some reason.
I have a spare Desire, so I inserted the SD card in it and made a nandroid backup of the ROM and reinstalled it (the phone worked with another ROM previously, so it couldn't boot with the card inserted). The system booted fien, I made the first steps to set it up, everything went well.
As I really would like to have my good old system back, I tried to replace gradually the parts of the system onto the new one, starting with the Data partition, but I only got bootloop. What did I mess up? Is there any way to get my good old system back with all its settings and so?
Have you tried booting the Bravo in recovery mode?
1. Vol(-) + Power
2. Wait 10 sec
3. Vol(-)
4. Power
Then from PC you have access to adb and can experiment with downloading partitions to PC.
Hi, yes, I tried to enter recovery mode but the phone is still dead, maybe the screen controller died.
No matter, cause i managed to make a full save tapping on the black screen (4Ext touch was a big help now) using the other Desire as a guide (I placed the two phones side by side).
I took the SD card out and inserted in the other phone and... after restoring the image, it gave me errors, I really don't know why. So I took a 5 years old recovery image of the same system and after making sure it worked (thank God it did), I did overwrite the System and the Data partitions (with the ones taken from the dead phone) and finally I have my nice system back, no data is lost. Now I'm happy!