I understand that re partitioning is dangerous but once we get custom recovery do you believe that we'll be able to claim the additional system partition as userdata space?
Sent from my Pixel using Tapatalk
Related
Hello there! if I just want 1gb partition for games,apps, and I got a 8gb card, whats the correct way to do this on 4EXT recovery?
Also one of the things says....
Warning sd-ext2 is not formatted!
how do i format sd-ext2???
how do I go about clearing everything and starting again? there is a option in the wipe/format menu, called Wipe all Partitions (DANGEROUS!), does this clear everything? I dont want to do it without checking with experienced forum members first, so if you can help, please leave below....
You've got one solution
Make a backup from your sdcard on your PC, and format partition and increasing the size of three of them ( system, data, cache, sd_ext and ext2) with your recovery on EXT4.
Like this:
- system => Ext4
- data => Ext4
- Cache => Ext4
- SD-ext => Ext4
- SD-ext2 => EXt4 or Ext3
- sdcard => fat32
then, restore your files on your sdcard.
biggary said:
Hello there! if I just want 1gb partition for games,apps, and I got a 8gb card, whats the correct way to do this on 4EXT recovery?
Also one of the things says....
Warning sd-ext2 is not formatted!
Click to expand...
Click to collapse
Use the EXT4 recovery as suggested, although are you sure that you'll need this space as the DS had over 1GB of internal user storage available to you by default. Mine has over 700mb free with all my applications installed.
The un formatted message relates simply to the non existence of the partition and isn't anything to worry about.
To wipe everything, the easiest way is to simply perform a factory reset, either from bootloader or from settings
The wipe all isn't what you are after as this is used by ROM cooks and wipes all partitions, which should only be used when installing new roms
Swyped from HTC Desire S using XDA Premium
It has been mentioned with other devices that as JB is larger, the partition sizes need to be altered.
Therefore when flashing a custom rom on a Motorola Xoom should the extra step of formatting system and cache partitions (Recovery > mounts and storage) be done?
rodders66 said:
It has been mentioned with other devices that as JB is larger, the partition sizes need to be altered.
Therefore when flashing a custom rom on a Motorola Xoom should the extra step of formatting system and cache partitions (Recovery > mounts and storage) be done?
Click to expand...
Click to collapse
It is a necessity to wipe (data/cache/dalvik) and preferably format (system) if you are coming from STOCK or a different ROM..
Sick of the separate userdata and fakesd partitions in NexusS and familiar with Nexus 4's way of doing things (only userdata, ext4), I've tried repartitioning my device.
So I booted a recovery (twrp), then connected via adb shell and made the kernel share the whole mmcblk0 via usb_mass_storage.
The block device seems to have a GPT partition table, so with the help of gparted, I got rid of the "media" partition and then resized the userdata partition to cover all the gained space.
However, the whole partition layout resets (ouch) when I reboot at all. I do not know who if it's the bootloader or recovery's fault, only that any changes I make to the GPT partition table go away after I reboot.
I'm sure someone here knows exactly what's happening, please tell us.
li_suna said:
Sick of the separate userdata and fakesd partitions in NexusS and familiar with Nexus 4's way of doing things (only userdata, ext4), I've tried repartitioning my device.
So I booted a recovery (twrp), then connected via adb shell and made the kernel share the whole mmcblk0 via usb_mass_storage.
The block device seems to have a GPT partition table, so with the help of gparted, I got rid of the "media" partition and then resized the userdata partition to cover all the gained space.
However, the whole partition layout resets (ouch) when I reboot at all. I do not know who if it's the bootloader or recovery's fault, only that any changes I make to the GPT partition table go away after I reboot.
I'm sure someone here knows exactly what's happening, please tell us.
Click to expand...
Click to collapse
Is there nowadays a real solution for repartitioning and make a bigger userdate partition ?
skorzo said:
Is there nowadays a real solution for repartitioning and make a bigger userdate partition ?
Click to expand...
Click to collapse
Why don't you try this guide:
http://forum.xda-developers.com/nexus-s/general/howto-combined-emulated-storage-nexus-s-t2848752
i wanted to partition my ram and went to clockwork recovery v6.0.4.6 and selected advance but it didnt showed partition option..
Hi, thank you for using XDA Assist. There is no partition option in custom recoveries. I strongly advise you not to try to partition your ram. It's not necessary. Android has many partitions that make up the system. Unless you're very savvy on Android partitions you will permanently brick your device.
So first, I transferred a file to my phone. I was quite low on storage (about 3 gb left) before the transfer, but the file was around 2.4gb, so it fit. I wanted to transfer that file to another computer, so when I plugged it in the other computer, a local disk drive shows up as opposed to mtp. I figure that it was probably a glitch. When I restart the phone, it boots, but instead of having 600 mb of free space left, it has 1134mb left. Somehow the available space just increased, so I decide to reboot again. The bootloader shows up, but then it simply goes to a black screen with no boot logo. When I plug my phone back into the computer, it opens 4 disk drive prompts saying I need to format the drive so that it can be used, and one that shows something. When I go in the "drive", there is one folder called image, and in the folder there is a bunch of files like modem.b00 as shown in the image attached..
It seems that instead of mounting the internal storage, it is mounting the firmware.
I am able to boot into recovery however, but nothing I have done seems to help. I have tried flashing several firmwares again with different recoveries (2.8.7.0.5 and 3.0.0) and restoring the efs partition again. I cannot delete any files off my phone through recovery as it yields an ERROR=1 and through MTP when I delete a file, it appears the file is deleted, but when I unplug and plug the phone back in, the file is back. I can however transfer files from my phone to the computer, but not vice versa.
It is also able to read but not write, meaning that my internal storage may be faulty, or that the file caused a corruption on my phone. If anyone has any ideas on how to fix it or has any experience with this, please let me know.
Can you access fastboot?
Sounds like it may be an issue with the userimage data try a reflash using the link below but edit the bat file (or .sh file) to only include the following line:
Code:
fastboot flash userdata userdata_64G.img (or userdata.img if you have a 16GB model)
you can grab a zip with the entire OS here and you will need to setup fastboot drivers properly (which sounds like you would have already done)
Return OPO to 100% Stock
itechy said:
Can you access fastboot?
Sounds like it may be an issue with the userimage data try a reflash using the link below but edit the bat file (or .sh file) to only include the following line:
Code:
fastboot flash userdata userdata_64G.img (or userdata.img if you have a 16GB model)
you can grab a zip with the entire OS here and you will need to setup fastboot drivers properly (which sounds like you would have already done)
Return OPO to 100% Stock
Click to expand...
Click to collapse
Yep, fastboot works and I already have the drivers set up. Do I only need to restore the userdata?
f41lbl0g said:
Yep, fastboot works and I already have the drivers set up. Do I only need to restore the userdata?
Click to expand...
Click to collapse
Flashing the userdata partition via fastboot will wipe all data so I hope you have your stuff backed up. Best solution now is to fastboot flash COS12.1.1 and see if it turns on
Sent from my A0001 using Tapatalk
Renosh said:
Flashing the userdata partition via fastboot will wipe all data so I hope you have your stuff backed up. Best solution now is to fastboot flash COS12.1.1 and see if it turns on
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I'm currently in the process of backing everything up, but can't I just format /data through recovery since TWRP works?
Tried flashing the userdata_64G.img, here is what I get:
C:\adb>fastboot flash userdata userdata_64G.img
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 3.829s]
sending 'userdata' (56 KB)...
OKAY [ 0.016s]
writing 'userdata'...
FAILED (remote: Bogus size sparse and chunk header)
finished. total time: 3.860s
f41lbl0g said:
I'm currently in the process of backing everything up, but can't I just format /data through recovery since TWRP works?
Click to expand...
Click to collapse
You can try that but no guarantees it will work.
You can either wipe everything (/system /data /internal storage /cache and /dalvik) with advanced wipe for TWRP 2.8.6.0 (recommended version) then transfer the flashable version of COS12.1.1 from link below and flash
http://forum.xda-developers.com/showthread.php?t=2906746
Or you can fastboot flash the entire COS12.1.1 fastboot using commands manually from the previous link the other poster gave you. You will run into some problems if you decide you wanna try some AOSP ROMs after flashing the userdata from COS12.1.1 but if you stick to CM you'll be fine
Sent from my A0001 using Tapatalk
Renosh said:
You can try that but no guarantees it will work.
You can either wipe everything (/system /data /internal storage /cache and /dalvik) with advanced wipe for TWRP 2.8.6.0 (recommended version) then transfer the flashable version of COS12.1.1 from link below and flash
http://forum.xda-developers.com/showthread.php?t=2906746
Or you can fastboot flash the entire COS12.1.1 fastboot using commands manually from the previous link the other poster gave you. You will run into some problems if you decide you wanna try some AOSP ROMs after flashing the userdata from COS12.1.1 but if you stick to CM you'll be fine
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Ok I had to fastboot flash the entire COS2.1.1, and it is working well now. Why is there an issue with AOSP roms after flashing the userdata?
f41lbl0g said:
Ok I had to fastboot flash the entire COS2.1.1, and it is working well now. Why is there an issue with AOSP roms after flashing the userdata?
Click to expand...
Click to collapse
I don't know what is up with the userdata image for COS12.1.1 but its corrupted in some way and you cannot flash ROMs like Omni and OxygenOS. It acts as if you've encrypted the OS when you haven't, solution is to wipe using an older userdata partition like the one from COS12.1 or earlier.
Sent from my A0001 using Tapatalk
Renosh said:
I don't know what is up with the userdata image for COS12.1.1 but its corrupted in some way and you cannot flash ROMs like Omni and OxygenOS. It acts as if you've encrypted the OS when you haven't, solution is to wipe using an older userdata partition like the one from COS12.1 or earlier.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Do you have a link to an old userdata partition?
f41lbl0g said:
Do you have a link to an old userdata partition?
Click to expand...
Click to collapse
Sorry I don't you'll have to download from the link I shared earlier an entire fastboot zip to be able to do it
Sent from my A0001 using Tapatalk