I installed lineageOS and Nikgapps but gapps didn't install because the system partition is too small. Can I increase the system partition?
[GUIDE] [DANGEROUS] Resize system partition
WARNING This process is extremely dangerous. You may brick your device. Do it only if you know what you are doing! I am not responsible of bricked devices or dead sdcards. Hello guys, I've decided to write this guide since this seems to be the...
forum.xda-developers.com
Here is a post related to your issue.
Hope it helps.
aiSanaul said:
[GUIDE] [DANGEROUS] Resize system partition
WARNING This process is extremely dangerous. You may brick your device. Do it only if you know what you are doing! I am not responsible of bricked devices or dead sdcards. Hello guys, I've decided to write this guide since this seems to be the...
forum.xda-developers.com
Here is a post related to your issue.
Hope it helps.
Click to expand...
Click to collapse
This doesn't works for this device because it has dynamic partitions.
BlackMesa123 said:
This doesn't works for this device because it has dynamic partitions.
Click to expand...
Click to collapse
oh that's why it worked for my Nokia 1.
Thanks for Info.
Related
I heard talk of the partitions in these pixel phones being different than the Nexus phones were. Like how the Nexus phones had bootloader, radio, system, recovery, boot, userdata, and cache. What do they mean when they speculate "dual partitions"? And for that matter, how are they going to update older Nexus devices if the partitions are different than the Pixel? A lot of questions I know, but hell, figured why not ask away.
I want to know how much space the 32GB variants have left after the dual partitions are accounted for.
LLStarks said:
I want to know how much space the 32GB variants have left after the dual partitions are accounted for.
Click to expand...
Click to collapse
I think I saw a video that showed 29GB
Edit: formatted to 29 but 24.3 available
H4X0R46 said:
I heard talk of the partitions in these pixel phones being different than the Nexus phones were. Like how the Nexus phones had bootloader, radio, system, recovery, boot, userdata, and cache. What do they mean when they speculate "dual partitions"? And for that matter, how are they going to update older Nexus devices if the partitions are different than the Pixel? A lot of questions I know, but hell, figured why not ask away.
Click to expand...
Click to collapse
Current devices have a single "system" partition, containing the OS and included apps, which gets patched when an OTA update is released. You can't use the phone when the OS is being patched and it's a slow process.
With the new feature, the new phones will have two system partitions (let's call them A and B). The phone can run the OS from one of these partitions (A), while the other partition is upgraded by an OTA update in the background (B). When the upgrade has been downloaded and applied to partition B, the phone can quickly reboot into the OS on partition B, making the upgrade much faster from a user point of view.
The next time the phone installs an update, it can apply it to partition A in the background.
All existing devices will simply continue to use the existing partition structure and patching process.
Daveoc64 said:
Current devices have a single "system" partition, containing the OS and included apps, which gets patched when an OTA update is released. You can't use the phone when the OS is being patched and it's a slow process.
With the new feature, the new phones will have two system partitions (let's call them A and B). The phone can run the OS from one of these partitions (A), while the other partition is upgraded by an OTA update in the background (B). When the upgrade has been downloaded and applied to partition B, the phone can quickly reboot into the OS on partition B, making the upgrade much faster from a user point of view.
The next time the phone installs an update, it can apply it to partition A in the background.
All existing devices will simply continue to use the existing partition structure and patching process.
Click to expand...
Click to collapse
So basically, Android OS would be installed on both partitions? That's too weird. That will take some getting used to!
It's more than just 2 system partitions, as those aren't the only potential partitions affected by an update. llabtoofer posted the exact duplicate partitions a while ago on Twitter.
I want to the size of each partitions.
Please show below via adb shell.
cat /proc/partitions
ls -l /dev/block/platform/soc/7824900.sdhci/by-name
*7824900.sdhci is diffrent name folder.
Milly7 said:
It's more than just 2 system partitions, as those aren't the only potential partitions affected by an update. llabtoofer posted the exact duplicate partitions a while ago on Twitter.
Click to expand...
Click to collapse
Hey I know this post is a little old but do you happen to know where I can find that post ?
aholeinthewor1d said:
Hey I know this post is a little old but do you happen to know where I can find that post ?
Click to expand...
Click to collapse
Very old post lol. You should search XDA for a user named llabtoofer. He knows a lot about HTC phones. I'm quite sure he will answer. You can also search for him on Twitter which is where he originally posted it prior to the phones release date.
Hi there!
A year ago, I messed up in installing Omnirom and LVM on my Find 7a and I've been left with 2.95GB of internal storage since. The rest of my internal storage is corrupt and is now called SD Card/lvm2pv. See attached screenshot..
So I detailed what I did on post 1325 here: https://forum.xda-developers.com/fi...ilds-7a-7s-t3237065/post66783345#post66783345
But basically, when installing it looks like I wiped something by accident as I followed a ROM guide that said to wipe Dalvik Cache, System, Data, Cache.
Here's what it says in TWRP when installing a zip/backing up:
Creating Android Secure: /internal_sd/.android_secure
Failed to mount '/internal_sd' (No such device)
I:Actual block device: '/dev/block/mmcblk0p29', current file system: 'LVM2_member'
Unable to recreate and-sec folder.
Failed to mount '/internal_sd' (No such device)
I:Actual block device: '/dev/block/mmcblk0p29', current file system: 'LVM2_member'
I:Unable to mount '/internal_sd'
I want to get my 12GB of storage back but I'm not sure what's wrong or what I need to do to solve the problem.
I've looked extensively online and it seems some people have had similar problems:
(such as post 8 in here https://forum.xda-developers.com/fi...rom-dirty-unicorns-6-0-1-7s-08-05-16-t3434120 )
but no sure solutions.
I found this guide: http://community.oppo.com/en/forum.php?mod=viewthread&tid=44896
But people were commenting under it saying it had bricked their phones so I'm going to give that one a miss I think.
I've spent all day looking for a solution to this but to no avail. I swear I've trawled!!
Does anybody know what's wrong or what I could do to fix it?
I could run the unbricker tool but that seems overkill.
Try this Omni Patch first:
https://mega.nz/#!Iw5FHJID!tAbrqXIkgxNqiPO0yQDsJnXeYYOlHFxM6BK5CqumFzI
If it doesnt work, try this Second:
https://mega.nz/#!NsAz1DxJ!vtO22hWN_r_gcjP_abeiRhoBcHoJ2W8Mopq2Q0aE03E
If all fail, go here and start it over:
http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra=
Then go to Settings -> Storage -> Erase.
Side note: Stay away from Omni Rom, they give the Find 7a BSOD here and there
Zeus Hai said:
Try this Omni Patch first:
https://mega.nz/#!Iw5FHJID!tAbrqXIkgxNqiPO0yQDsJnXeYYOlHFxM6BK5CqumFzI
If it doesnt work, try this Second:
https://mega.nz/#!NsAz1DxJ!vtO22hWN_r_gcjP_abeiRhoBcHoJ2W8Mopq2Q0aE03E
If all fail, go here and start it over:
http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra=
Then go to Settings -> Storage -> Erase.
Side note: Stay away from Omni Rom, they give the Find 7a BSOD here and there
Click to expand...
Click to collapse
Thanks for the reply!!
What is this unified-storage-patch you link to? Is it... uhhh.. safe?
And if that doesn't work it looks like I'll be rolling the dice with the unbricker tool.. oh well..
jd9922 said:
Thanks for the reply!!
What is this unified-storage-patch you link to? Is it... uhhh.. safe?
And if that doesn't work it looks like I'll be rolling the dice with the unbricker tool.. oh well..
Click to expand...
Click to collapse
No, it is not safe. It triggers some self destruct IC inside the Find 7a, and makes it explode just like the Note 7, hahaha :laugh:
Oh, I almost forgot, before using the unbricker, this LVM setup and LVM remover may help:
https://forum.xda-developers.com/showpost.php?p=62169121&postcount=3
Zeus Hai said:
No, it is not safe. It triggers some self destruct IC inside the Find 7a, and makes it explode just like the Note 7, hahaha :laugh:
Oh, I almost forgot, before using the unbricker, this LVM setup and LVM remover may help:
https://forum.xda-developers.com/showpost.php?p=62169121&postcount=3
Click to expand...
Click to collapse
I hear all phones with the number 7 in the name have that curious IC that spontaneously combusts alright!
But flashing that omni-6.0.1-find7-unified-storage-patch .zip file won't brick the phone will it?
Or am I at the stage where I need to throw crap at the wall enough times to see what sticks? :silly:
And isn't the omni-6.0.1-find7-unified-storage-patch something to do with Chinese partition? I'm trying to understand it but I'm struggling....
jd9922 said:
I hear all phones with the number 7 in the name have that curious IC that spontaneously combusts alright!
But flashing that omni-6.0.1-find7-unified-storage-patch .zip file won't brick the phone will it?
Or am I at the stage where I need to throw crap at the wall enough times to see what sticks? :silly:
And isn't the omni-6.0.1-find7-unified-storage-patch something to do with Chinese partition? I'm trying to understand it but I'm struggling....
Click to expand...
Click to collapse
No, you're at the stage where you need to trust someone, flashing some craps onto the phone until it's fixed
Ok, joke aside, I tried all the stuffs mentioned above and still my stubborn Find 7a didnt brick
Zeus Hai said:
No, you're at the stage where you need to trust someone, flashing some craps onto the phone until it's fixed
Ok, joke aside, I tried all the stuffs mentioned above and still my stubborn Find 7a didnt brick
Click to expand...
Click to collapse
Got it fixed!!!
Thanks for all the help. I'll post a guide/what I did, in the next few days when I get time.
What ROM do you recommend though if not Omni? I'm looking for simplicity with good battery life!
hi guys, I am having trouble with my MI Max having 32GB internal memory.
From it's behaviour for last few days I have inferred it's system partition is the culprit.
On stock miui rom, it gives msg that encryption unsuccessful and I need to factory reset it. But even after doing factory reset it shows the same msg.
Its with locked boot loader but referring one thread I could install twrp latest version on it by replacing recovery image in stock rom and flashing with mi flash tool in edl mode.
So with two I tried installing few vision rooms like miui eu ROM, RR and crdroid based on Oreo. All the rooms while flashing fine error E1001, saying system image not updated and flashing failed.
I even tried repairing file system, fixing file system, Channing file system to fat, exfat, ext2, ext3, ext4 and f2fs several times (from advanced wipe menu) but things are not improving. Even tried formatting data partition as it's suggested at few places.
I am out of ideas after spending few days trying to fix it by flashing several times.
So please if some one can assist in resolving the issue, I would really appreciate.
Thank you in advance.
You need to format data not wipe . Go to twrp choose wipe , format data and type yes . Note, by doing this you will lose all of your data if you want to keep it make sure to save it to your PC or USB drive.
Zasnizas said:
You need to format data not wipe . Go to twrp choose wipe , format data and type yes . Note, by doing this you will lose all of your data if you want to keep it make sure to save it to your PC or USB drive.
Click to expand...
Click to collapse
Have already done it several times by now. Didn't make any difference.
harpy.eagle said:
Have already done it several times by now. Didn't make any difference.
Click to expand...
Click to collapse
As discussed yesterday on unofficial LineageOS (nijel8) thread the nand is damaged. You need to delate partition, compact unallocated space & then recreate the exactly the same partition. That way it won't be on the same spot & it will work.
Use a PC with an partition manager.
https://gparted.org/
Zola III said:
As discussed yesterday on unofficial LineageOS (nijel8) thread the nand is damaged. You need to delate partition, compact unallocated space & then recreate the exactly the same partition. That way it won't be on the same spot & it will work.
Use a PC with an partition manager.
https://gparted.org/
Click to expand...
Click to collapse
Tks a lot for the reply. It gave a ray of hope to me. Though I am hearing modifying partition on android device for the first time to fix it. That too for bricked device and to do it on PC. Is there any thread guiding about it? Would read a bit about how to do it in order to not mess things up even more.
harpy.eagle said:
Tks a lot for the reply. It gave a ray of hope to me. Though I am hearing modifying partition on android device for the first time to fix it. That too for bricked device and to do it on PC. Is there any thread guiding about it? Would read a bit about how to do it in order to not mess things up even more.
Click to expand...
Click to collapse
It's still ain't bricked so you can do this relatively easy. When it's bricked EDL programmer for used NAND chip used is needed.
So take a deep breath, see the exact size & type of the partition, delate it, create a new one exactly the same (type, size & name).
https://s10629.pcdn.co/wp-content/pictures/2010/01/captured_Image1.png51.png
https://helpdeskgeek.com/wp-content/pictures/2010/01/captured_Image1.png111.png
The tool I gave you URL is very good documented and with plenty examples & user guides available all which can be found on the site, it uses graphics GUI so it's as easy as it can be. So if you are inexperienced read/watch first how it's done. After you are done flash what you want in TWRP.
Best regards.
What I meant to ask is, how to access partitions of mobile on PC? I have used partitioning app on windows but never for android device. Anyway, as u have clued, I shall try accessing partitions with mobile connected in edl mode.
Hi,
after removing all the bloatware and some apps I will never use there is a little over 1G of free space in my system_root partition. Since both system a/b and userdata partitions are on sda I assume it is the same physical device. So in theory it should be possible to shrink the systems partitions and grow the userdata. Has anybody tried to do this? Does anybody know what type of encryption is used on userdata - it doesn't seem to be luks. I have a linux background and am quite surprised how much android differs from what I am used to...
Cheers
Paul
alpinista82 said:
Hi,
after removing all the bloatware and some apps I will never use there is a little over 1G of free space in my system_root partition. Since both system a/b and userdata partitions are on sda I assume it is the same physical device. So in theory it should be possible to shrink the systems partitions and grow the userdata. Has anybody tried to do this? Does anybody know what type of encryption is used on userdata - it doesn't seem to be luks. I have a linux background and am quite surprised how much android differs from what I am used to...
Cheers
Paul
Click to expand...
Click to collapse
In theory it's possible. But in practice it's extremely difficult, especially with all the partitions on todays devices. Changing a partition effects all partitions after it and they all need to be recreated. It's also extremely dangerous if you don't really know what your doing. I successfully did it on an old skyrocket just for fun. But I wouldn't want to try it on the pixel. I'm not even sure what the dual slots would entail.
Sent from my [device_name] using XDA-Developers Legacy app
alpinista82 said:
Hi,
after removing all the bloatware and some apps I will never use there is a little over 1G of free space in my system_root partition. Since both system a/b and userdata partitions are on sda I assume it is the same physical device. So in theory it should be possible to shrink the systems partitions and grow the userdata. Has anybody tried to do this? Does anybody know what type of encryption is used on userdata - it doesn't seem to be luks. I have a linux background and am quite surprised how much android differs from what I am used to...
Cheers
Paul
Click to expand...
Click to collapse
What bloatware did you remove?
airmaxx23 said:
What bloatware did you remove?
Click to expand...
Click to collapse
Everything that is not related to basic phone functionality or camera. Like two dozen apps. arcore, vrcore, all the carrier and e-sim stuff, play music/video, and a lot of other unnecessary stuff.
This is an answer to jd1609, I hit the wrong button:
Yeah, I thought so. Android has evolved quite a bit since cm14 (Android 7.1). I am just starting to understand whats going on with a/b partitions. I still don't quite understand why they had to go with sparse images instead of just raw images. Most probably to confuse me a bit more ....
But thanks a lot for sharing your experiences.
Cheers
Paul
The owner is kind, not the 2 XL
I messed up with mine while playing with modem partitions.
A "kind" of a rooted 2 XL owner, can you please send me the "sbl" partition of your phone? It's not related to anything private partition I assure you. You can use this command,
adb shell
su
dd if=/dev/block/sdf of=/sdcard/sdf.img
It should be 8 MB.
Thank you very much.
Wouldnt flashing an easy accessible factory image sort that out for you.....
Im new at the Pixel, and im not sending anyone a copy of a partition off my device that i dont understand....
The few references to it on here seem to potentially relate to imei data, and sorry, i aint posting that
73sydney said:
Wouldnt flashing an easy accessible factory image sort that out for you.....
Im new at the Pixel, and im not sending anyone a copy of a partition off my device that i dont understand....
The few references to it on here seem to potentially relate to imei data, and sorry, i aint posting that
Click to expand...
Click to collapse
I opened this topic after a full day of try, nothing works, phone is in bootloop. Like I said, that partition does not INCLUDE any private data.