Related
Hi,
It just came into my mind. Since we can have custom recovery and android recovery also boots, can we have multi boot option in Defy as like in a PC's
Good question ..............i think there is no answer for this question
rvd_516 said:
Hi,
It just came into my mind. Since we can have custom recovery and android recovery also boots, can we have multi boot option in Defy as like in a PC's
Click to expand...
Click to collapse
some resources would have to be used by both ROMs..
with the current hacks it can't be done easily.
i guess some way of ramdisking the shared resources will have to be used.
basically, if you think about a hack for defy ask first:
can it be done in a completely open (=bootloader not locked) phone like nexus ?
if yes, ask:
is it WORKING?
if yes also, so maybe it can be done.
nevertheless, it's easy enough to create a script to backup & restore NANDROIDS.
but then every switch between roms will take like 25+ minutes, so it won't be a real multiboot.
Somebody at one point on the desire was working on something like this. Run rom from nand and other rom from sdcard.
Ephumuris.
ephumuris said:
Somebody at one point on the desire was working on something like this. Run rom from nand and other rom from sdcard.
Ephumuris.
Click to expand...
Click to collapse
I think there are two possibilities for this to happen: first of all, we should try NAND boot for the primary ROM, and try somehow to load the secondary ROM from the internal memory (it'll be faster than the SD Card, I think). The problem here would be allowing the bootloader to read from internal memory instead of NAND. I know this can be done based on the number of WinMo-Android and iOS-Android dual boot solutions, with a menu to choose which system to load, in the boot screen.
The second option is the method used by Wing Linux to run Android on old WinMo devices. In this method, you MUST boot in WinMo (or, in our case, in the primary ROM), then open the app that loads Android (the secondary ROM, for us). Android does NOT run emulated in this method, but, since the device can't dual boot directly, the app sends a signal for the device to restart running from the bootloader to the SD Card (for us, internal memory). This second option is, somehow, like the System Recovery app (not 2ndInit), that has an option that reboots directly into Recovery. So, if we can tell the phone to load from custom Recovery (which is, in fact, in internal memory, not in NAND), I think it's possible to make it load an entire ROM from the internal memory (without having to mount it everytime and waiting for the dalvik-cache to load).
However, it's surely a hard work to do.
Yes one from nand and one from sd card..........good......can we partition nand and use it both on the nand itself??
it should really work if we use virtual images or sdcard-partitions instead of system, data and cache partitions.
This can be changed in the init.rc-file(of 2nd-init).
The creator of the 2nd-init-bootmenu should implement this feature.
it is possible... just need 2 new partitions ext3 on sdcard for data and system...
you can use 2nd-boot profile in bootmenu to change dev block links and customize mount settings
Epsylon3 said:
it is possible... just need 2 new partitions ext3 on sdcard for data and system...
you can use 2nd-boot profile in bootmenu to change dev block links and customize mount settings
Click to expand...
Click to collapse
Did you try it?
Epsylon3 said:
it is possible... just need 2 new partitions ext3 on sdcard for data and system...
you can use 2nd-boot profile in bootmenu to change dev block links and customize mount settings
Click to expand...
Click to collapse
even i like to know tht did u tried tht?
I managed to boot from virtual system,data and cache partitions with the 2nd-boot-option of bootmenu like ep3 said.
It was a bit difficult because android-init remounts /dev so the changes will be lost but now I found a way.
And: I got recovery working for the virtual system so you don't need to prepare your images, BUT: only the wipe and restore are working. "install zip" will still affect your real system.
My scripts need some testing but after that I will release a first version.
the multboot works for me i writed a cutsom boot sh and init.rc and woila WORKS!
NOT PUBLUC because it not works for all rom
---------- Post added at 04:59 PM ---------- Previous post was at 04:36 PM ----------
this is a dualboot rom
http://forum.xda-developers.com/showthread.php?t=1225179
So here is the first (very early) version of 2nd-boot:
http://www.multiupload.com/Z17M0WO3SU
Before continuing please make a backup of your phone!
Installation:
Just install it via CWM.
This will place the script in your 2nd-boot and replace the "CWM-Lastest"-script so it will install into the images. BUt can still use the "CWM-Stable" option for your normal system.
I've created 3 empty 300MB ext3-images for system,data and cache so you don't have todo that. Download them here:
http://www.multiupload.com/VY3U4IXRO1
Just copy the folder "fsimages" to your sdcard.
Usage:
After installing the update-zip and copying the files to the sdcard you can reboot into bootmenu, select "Lastest Recovery" and Restore an backup.
Please DO NOT install a ROM with a zip-file. Currently this will affect your real system.
After you restored your backup into the virtual file-system you can boot them with the 2nd-boot-option in bootmenu.
I successfully installed CM7.1 and MIUI-Pikachu-Edition in the virtual filesystem.
I uploaded a new version of my multiboot-script(v0.2)
changelog:
- "Install zip from SDcard" works now
- changed hook-method so it works with more ROM's(including ICS)
Download:
http://www.multiupload.com/UT0TLPR3ZW
m11kkaa said:
So here is the first (very early) version of 2nd-boot:
http://www.multiupload.com/Z17M0WO3SU
Before continuing please make a backup of your phone!
Installation:
Just install it via CWM.
This will place the script in your 2nd-boot and replace the "CWM-Lastest"-script so it will install into the images. BUt can still use the "CWM-Stable" option for your normal system.
I've created 3 empty 300MB ext3-images for system,data and cache so you don't have todo that. Download them here:
http://www.multiupload.com/VY3U4IXRO1
Just copy the folder "fsimages" to your sdcard.
Usage:
After installing the update-zip and copying the files to the sdcard you can reboot into bootmenu, select "Lastest Recovery" and Restore an backup.
Please DO NOT install a ROM with a zip-file. Currently this will affect your real system.
After you restored your backup into the virtual file-system you can boot them with the 2nd-boot-option in bootmenu.
I successfully installed CM7.1 and MIUI-Pikachu-Edition in the virtual filesystem.
Click to expand...
Click to collapse
Thanks for your work.
Did the 2nd android system boots from sdcard?
Yes, but it's very flexible. By changing 2 lines you can let it boot from whereever you want.
I prefer storing it at the data-partition because it's over 1gb in size and my apps are using 200mb only.
I'm looking forward to better bootmenu-integration and boot-image-selection but for that I have to figure out how to compile bootmenu.
m11kkaa said:
Yes, but it's very flexible. By changing 2 lines you can let it boot from whereever you want.
I prefer storing it at the data-partition because it's over 1gb in size and my apps are using 200mb only.
I'm looking forward to better bootmenu-integration and boot-image-selection but for that I have to figure out how to compile bootmenu.
Click to expand...
Click to collapse
Ask pedrodh http://forum.xda-developers.com/member.php?u=2098689
He can help.
Nice work, thanks i will add this soon, in the future bootmenu versions
m11kkaa said:
Yes, but it's very flexible. By changing 2 lines you can let it boot from whereever you want.
I prefer storing it at the data-partition because it's over 1gb in size and my apps are using 200mb only.
I'm looking forward to better bootmenu-integration and boot-image-selection but for that I have to figure out how to compile bootmenu.
Click to expand...
Click to collapse
I released a dual boot version that uses 2nd-boot a few months back, hadn't have much time to improve it since.
I was using loop-back mount with /system and bind mount with /data since it's much more space efficient than just use an ext3 image.
Awesome job. I think u shud create a new thread for it. Dual booting cm7 and miui :O
Sent from my Moto Defy
UPDATE: This can't be used with CM10 Alpha 4 (or later) as it is due to the new partitioning system.
____
I made this thing time ago and I thought to share.
What it does is to boot a stock ROM from the external SD card. It's nothing special, I simply changed few things here and there. I did it because I needed a stock ROM for a couple of minutes and this was the faster way to get it.
I'm using CM and I made this with that in mind, so, don't use while using a stock ROM. It won't mess your current setup, but it won't work.
You need to change kernel to boot the stock ROM (reboot recovery > flash zip. Simple and fast). That's because, as you probably now, kernels made for stock ROMs are not compatible with CM.
Prepare you SD card
You need first to repartition your external SD like this:
Code:
1° partition (mmcblk1p1): FAT - it will be the usual external SD
2° partition (mmcblk1p2): ext4 - /system (make it around 300MB big, 254MB will be more or less the space used)
3° partition (mmcblk1p3): ext4 - /data
I can't help you with this, I did it with adb and parted (the command is available in CWM). Look for instructions on the web, it's full of guides out there. Your external SD card is /dev/block/mmcblk1 (mmcblk0 is the internal one).
If you'll use the zip linked to flash the ROM, the two partitions (mmcblk1p2 and mmcblk1p3) will be automatically converted, unless they are already two ext4/ext3/ext2 partitions.
It shouldn't matter which kernel you are currently using and it should be safe flashing it, the only important thing is to have three partitions. If mmcblk1p2 or mmcblk1p3 are not detected, the installation will be aborted (it means that your SD card is not partitioned). Nothing else will be touched.
If you don't want to use the zip, mount mmbclk1p2 and copy the ROM there.
/dbdata will be the usual one (it's not used in CM. This will also makes Samsung apps a lot faster when using a slow SD card), same for /cache.
The flashable ROM is a stock XXLE4 + su/Superuser.apk.
How to use the additional ROM
To use the ROM on your SD, flash kernel-stock-SD.zip (see below) from recovery.
To go back to the real ROM you have to flash its kernel. Here below you can find CM10 Alpha 2 kernel, flashable from recovery. If you have doubts, reflash the entire ROM, it won't wipe your data.
I only mentioned CM10 because it's what I'm using, but this thing should work with CM9 too.
Things to know
I built the kernel using the latest Samsung sources with inbuilt ext4 support (and ext3/ext2 compatibility). Nothing else was changes, so I think there's no need to publish the sources, they are available here.
I attached the tools I use to unpack/repack boot images (they are a modified version of skin1980's tools):
Code:
./unpack.pl boot.img
./repack.sh [gz|lzma|bzip2|xz]
To see the changes I made, compare "out/android" with the stock XXLE4 ramdisk and the other two directories with CM10 boot.img ramdisk.
I changed recovery.fstab accordingly, but I can't tell you if flashing stuff from CWM while using the additional ROM will work as expected. You should read the updater-script to know it for sure.
I can only tell you that dhiru's builds will be flashed into the real /system partition and not your SD card.
Backups should work too, but I didn't try.
Of course, performances depends on your SD card. Mine is not that good I think, I took it from an old phone and I really don't know anything about it. The ROM is still usable, but apps that intensely use databases are slow (not Samsung apps, those will use /dbdata). Maybe disabling journaling will help (search for more info).
The Galaxy SL screen will last more than usual because I intentionally added a delay (3 seconds, SD cards are detected after a while) and of course because of the slower load.
Please, use this if you have some experience.
Note: dual booting two ROMs with a single kernel is possible, but only if they use the same kernel image. See this and this.
Downloads
XXLE4-CWM.zip: CWM flashable ROM
kernel-stock-SD.zip: kernel to boot the ROM from the external SD, flashable from recovery
kernel-CM10-Alpha2.zip: CM10 Alpha 2 kernel, flashable from recovery
Wow ! thats dualboot for i9003 ! sweet gud to see development back in action
Good work.
The class of an SD card can be misleading. It is only a measure of the sequential Write access and that doesn't tell the whole story. Class 10 cards are great for cameras and applications that write or read sequential data, such as saving a picture and transferring a file. They are not so good for random access which is what the Android OS does when operating. In fact the random access speed for class 10 cards is lower than class 4 or 6 cards. From what I have seen, the sweet spot for smartphones is class 6.
Awesome. Only if we could achieve dual boot without flashing kernel everytime. But anyways awesome guide. Thanks.
Reminded me of dual booting of maemo and android on my brother's n900.
Whats the benefits of dual boot? I heard about it but i dont have an idea
juztinlee said:
Whats the benefits of dual boot? I heard about it but i dont have an idea
Click to expand...
Click to collapse
Dual Booting means you can have two OS's (here firmware) on the phone at the same time. You can choose on which you want to go. This, besides being awesomely cool, is really helpful in many scenarios.
But its not exactly a dual booting. On galaxy s2 dual booting uses a single kernel but in our case.we are still using two different kernels which has to flash saperately.
Really we should create a kernel which can be used for cm9/10 & for stock GB rom. Then real fun will begin
^But this can be useful when you have to go for a long trip and want to record videos which only our stock rom is capable of doing good. Thanks to the developer.
Also, if anyone can, please tell me what is the possibility we can create a dualboot kernel like siyah kernel?
vishal24387 said:
But its not exactly a dual booting. On galaxy s2 dual booting uses a single kernel but in our case.we are still using two different kernels which has to flash saperately.
Really we should create a kernel which can be used for cm9/10 & for stock GB rom. Then real fun will begin
Click to expand...
Click to collapse
I didn't say dual boot
Creating a single kernel for ICS/JB and GB is not possible, or at least not an easy thing.
CyanogenMod is using newer graphic drivers not compatible with GB. I tried to use my CM10 kernel with GB, just to see what could happen. Well, it works, but with no hardware rendering as expected. It doesn't mean "it's laggy", it's painfully slow. And if we'll have the 3.0 kernel working, I guess this will be even more difficult.
The only option I think is kexecing an additional kernel, but kexec is hard to implement.
However I dual booted CM10 and CM9 (SD) with a single kernel (there are traces of this in my unpack/repack tools), I simply added an additional "cpio.gz" inside the boot.img. There's an additional boot reason that we never use, so we can use it to choose the corrent "cpio.gz" by parsing /proc/cmdline. The only problem is that you need to boot the ROM first and the reboot, because to get the other boot reason you have to run this:
Code:
reboot arm11_fota #or arm9_fota
(if you are using a stock ROM and try to reboot with the command above, you'll see weird stuff, but nothing should happen to your phone. I did it once.).
Maybe there's something else possible, but dual booting never interested me. As I said, I did it because I needed it.
You can do a lot of things, I even stored a ROM in a subdirectory in /data and use it from there (=> fast).
santoshsadani009 said:
^But this can be useful when you have to go for a long trip and want to record videos which only our stock rom is capable of doing good. Thanks to the developer.
Also, if anyone can, please tell me what is the possibility we can create a dualboot kernel like siyah kernel?
Click to expand...
Click to collapse
I don't know how exactly dual booting with this kernel works. I actually don't know how usually dual booting is implemented in Android.
I just looked at it. It allows you dualbooting only two ICS+ ROMs (so no GB), it automatically creates an hidden partition, automatically stores the ROM there, provides additional tools in CWM and other nice things.
I guess is something possible, but don't expect it from me. As I said, I'm not interested in dual booting and this thing requires time and knowledge.
loSconosciuto said:
I didn't say dual boot
Creating a single kernel for ICS/JB and GB is not possible, or at least not an easy thing.
CyanogenMod is using newer graphic drivers not compatible with GB. I tried to use my CM10 kernel with GB, just to see what could happen. Well, it works, but with no hardware rendering as expected. It doesn't mean "it's laggy", it's painfully slow. And if we'll have the 3.0 kernel working, I guess this will be even more difficult.
The only option I think is kexecing an additional kernel, but kexec is hard to implement.
However I dual booted CM10 and CM9 (SD) with a single kernel (there are traces of this in my unpack/repack tools), I simply added an additional "cpio.gz" inside the boot.img. There's an additional boot reason that we never use, so we can use it to choose the corrent "cpio.gz" by parsing /proc/cmdline. The only problem is that you need to boot the ROM first and the reboot, because to get the other boot reason you have to run this:
Code:
reboot arm11_fota #or arm9_fota
(if you are using a stock ROM and try to reboot with the command above, you'll see weird stuff, but nothing should happen to your phone. I did it once.).
Maybe there's something else possible, but dual booting never interested me. As I said, I did it because I needed it.
You can do a lot of things, I even stored a ROM in a subdirectory in /data and use it from there (=> fast).
I don't know how exactly dual booting with this kernel works. I actually don't know how usually dual booting is implemented in Android.
I just looked at it. It allows you dualbooting only two ICS+ ROMs (so no GB), it automatically creates an hidden partition, automatically stores the ROM there, provides additional tools in CWM and other nice things.
I guess is something possible, but don't expect it from me. As I said, I'm not interested in dual booting and this thing requires time and knowledge.
Click to expand...
Click to collapse
so that means we can dualboot cm9/10 with miui v4 . right ? since they both use the same kernel
vishal24387 said:
But its not exactly a dual booting. On galaxy s2 dual booting uses a single kernel but in our case.we are still using two different kernels which has to flash saperately.
Really we should create a kernel which can be used for cm9/10 & for stock GB rom. Then real fun will begin
Click to expand...
Click to collapse
Ya a Universal kernel will do the trick.If later then we can achieve dual boot then the people who were holding back from CM9 or CM10 can flash that for features and a stock rom for stability and camera.
shriomman said:
so that means we can dualboot cm9/10 with miui v4 . right ? since they both use the same kernel
Click to expand...
Click to collapse
As long as the kernel is the same, yes.
If you want, here you can find the unpacked boot.img I (probably) used to dual boot CM10 and CM9 (SD).
There's no zImage in there, use the one you prefer, CM10 and CM9 are using the same kernel.
EDIT:
I almost forgot. "out/ramdisk/2ndROM" is for the ROM stored in your SD card, so you have to adjust the mount points there (already done in the one linked). "out/ramdisk/android" should be the "stock" ramdisk.
recovery will work only for the primary ROM in this case, maybe with some scripting you can make it works for both the ROMs, but I won't do it (if it's something possible).
The tools I posted will automatically take care of the additional ramdisk.
Possible to fix the download links? I want to boot rom from SD card since my internal is corrupted...
nick0016 said:
Possible to fix the download links? I want to boot rom from SD card since my internal is corrupted...
Click to expand...
Click to collapse
I don't know what happened to the links, probably I deleted the files by mistake on dev-host. Sadly I no longer have them and I currently don't have the time to make them again.
Anyway, I suggest you to follow other guides in order to replace only the corrupted memory instead (we have two different memories). This one for example, but there are other guides probably.
Thanks for your answer, problem is that my "device" memory is corrupted (as in read only).
I did the SD / USB storage swap but still have the problem that I cannot run/remove/install. So I need a ROM that loads completely from the external SD card and also uses it for data/storage...
I can flash a rom/kernel without problems, but changing version makes it only worse because the data does not get erased (background/applications/settings.... stays the same everytime, even after a wipe from the recovery).
If it helps I would love to pay/donate money to you as a thanks for your help and effort because the phone itself is working fine (except the corrupted memory of course) and would like to use it again
nick0016 said:
Thanks for your answer, problem is that my "device" memory is corrupted (as in read only).
I did the SD / USB storage swap but still have the problem that I cannot run/remove/install. So I need a ROM that loads completely from the external SD card and also uses it for data/storage...
I can flash a rom/kernel without problems, but changing version makes it only worse because the data does not get erased (background/applications/settings.... stays the same everytime, even after a wipe from the recovery).
If it helps I would love to pay/donate money to you as a thanks for your help and effort because the phone itself is working fine (except the corrupted memory of course) and would like to use it again
Click to expand...
Click to collapse
The guide I linked is fine then.
It explains how to repartition your SD card and the script Dipu K attached to his post is to use the newly created partition inside your external SD for /data. It's not to swap internal and external SD.
As I said, we have two memories, /data is in one, /system, kernel and other things are in the other memory. The corrupted one must be the one which holds /data.
Try to do as explained in the guide, if the problem persists, I'll see what I can do to help.
I followed the guide and got the Device memory replaced (data partition). Problem is now it is stuck in at boot because the partition is empty.... and when I copy the files from the corrupted data partition it boots fine but get message that I must wipe my data or the system will be unstable (which is correct because I get then flooded with unexpected errors which make it unusable). But formatting data partition gives stuck @ samsung boot logo??
So I need to get the "factory" data files from somewhere... I am running stock KPE ROM with BAM kernel (for init.d support).
Is it possible to extract the data partition from the stock rom?!
nick0016 said:
I followed the guide and got the Device memory replaced (data partition). Problem is now it is stuck in at boot because the partition is empty.... and when I copy the files from the corrupted data partition it boots fine but get message that I must wipe my data or the system will be unstable (which is correct because I get then flooded with unexpected errors which make it unusable). But formatting data partition gives stuck @ samsung boot logo??
So I need to get the "factory" data files from somewhere... I am running stock KPE ROM with BAM kernel (for init.d support).
Is it possible to extract the data partition from the stock rom?!
Click to expand...
Click to collapse
The content of /data is generated, there's nothing like what you asking for.
Maybe the problem is that the script posted in the guide copies the content of the old /data partition to the new partition inside the SD card. Wiping data shouldn't work because the path to the SD card is not specified.
Try the script attached. I zipped it to be able to upload it here, but it's not flashable. Since you've been able to follow the guide I assume you know how to use adb.
Wipe the content of the data partition you created inside you SD card (/dev/block/mmcblk1p2). You could reformat it with make_ext4fs, use a computer and so on. What's important is that it's ext4 formatted.
While in recovery, run:
Code:
adb shell mount /system
adb shell mkdir -p /system/etc/init.d/
adb push [I]PATH_TO[/I]/remount_data /system/etc/init.d/
adb shell chmod 777 /system/etc/init.d/remount_data
I'm sorry, but I currently don't have much free time to help more than this. With no logs or access to the device it's really hard for me to know what's the problem.
Hello everyone
This is CWM-Zip script to repartition our N7100 to gain 1.9 GB more for user data partition.
This script is originally from http://forum.xda-developers.com/galaxy-s3/development/guide-extra-1-3-gb-user-data-t2762594 It’s for GT-i9300. Made by @forumber2 :good:. Thanks to him, without his easy simple script, I wouldn’t be able to port this script.
This is how Samsung partitioned N7100
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After running the script
Please note that this script is not suitable to ROMs that require storing big files in CACHE and PRELOAD or HIDDEN, notably Official ROMs, as you can see that CACHE and PRELOAD got shrank.
I’m not sure if there are some custom ROMs that store files in CACHE and PRELOAD, so check the ROMs installation zip first before using this repartition script. Check by reading update-binary in META-INF and observing folder structure inside the zip file.
I’m using DN3 v5+ and it doesn’t store any files.
I checked Omega v29, it doesn't use PRELOAD to store files, even wiping it before install.
X-Treme v2.1 is safe to install, even wiping PRELOAD before install.
BIG UPDATE 1
For some ROMs like Phoenix ROM requires storing data to PRELOAD, but not CACHE.
Use partition script "Repartition_N7100_16GB_PreloadStockSize587MB.zip" instead of "Repartition_N7100_16GB.zip"
It will partition PRELOAD to size of Stock 587 MBs.
CACHE remains 100 MBs, and SYSTEM remains around 2 GBs. GAINED USERDATA FREE SPACE IS AROUND 1328 MBs.
If your ROM .zip installer doesn't store files in PRELOAD, use "Repartition_N7100_16GB.zip" instead.
FYI, Big CACHE partition is used to store official Samsung OTA updates file, if you are on custom ROMs, then you can’t use Samsung OTA updates anyway. Big cache partition is practically waste of free space, but it is still required for Google Play APK downloads. (Max Google Play APK size is 50 MBs) In fact, Google Play apk downloads are stored in /data/com.android.providers.downloads/files/, cache partition is used to store apk downloads in old Android version. This script will partition CACHE with size of 100 MBs. For any Google Play apps that are bigger than 50 MB, they will use expansion files called .obb to help, those obb are stored in "Internal SD Card/Android/obb".
Samsung Apps APK downloads sometimes can be seen large to something like 300 MBs, but these APK downloads are stored in "/data/data/com.sec.android.app.samsungapps/files" So it won't break Samsung Apps downloads.
PRELOAD or HIDDEN is used to store Samsung crap stuffs like ringtones, Wonders of Nature video, starter beautiful images, VODB folder that is used for S-Pen stroke recognition. When user make a factory reset, all data in internal sd card gets deleted, then stuffs in PRELOAD gets copy to internal sd card. That’s why after factory reset Wonder of Nature video comes back.
ALL USERDATA AND INSTALLED OS ARE GOING TO BE REMOVED, SO BACKUP FIRST!
So let’s get started. You will use "Repartition_N7100_16GB.zip OR Repartition_N7100_16GB_PreloadStockSize587MB.zip OR in the attachment
1.Backup of course, if you don’t do System Nandroid backup, be sure to have ROM installer zip ready in external sd card, if you do Nandroid backup or Titanium Backup, make sure to back up to external sd card because this process will erase internal sd card too.You may backup your internal sd card to external sd card, USB-OTG, or Windows PC.
2.You need to use PhilZ Recovery, it doesn’t work with TWRP, TWRP lacks of “parted” binary required for repartitioning.
I personally used PhilZ Touch 6.25.0 on my N7100. 6.41.6 reported to work as well.
3.Install the ZIP and the script will run, after it finished, it will reboot recovery again.
4.We are not done yet, this script still has some bug that formatted partition can’t be mounted. You can see that you can’t mount some partitions or maybe all, weird.
5.We need to fix mount problem manually by go to Mounts and Storage, then format System, Data, Cache, Preload or Hidden one by one, then go to Power Option and reboot recovery once. DO NOT FORMAT BOOT, MODEM, STORAGE/SDCARD1 (external sd card).
6.We have repartition successfully. Now restore data, install ROMs.
How to restore original stock partition table.
You will need to do this if you want to install stock official firmware.
1 - Download "Odin3_v3.07_with_PIT_16GB_GT-N7100.zip" and extract it somewhere
2 - Download any stock ROM from sammobile.com or samsung-updates.com and unzip it.
2 - Open Odin, click "PIT" button and select " PIT_N7100_16GB_20121102.pit"
3 - Click "PDA" and select official ROM that you've downloaded
4 - Click "Start"
5 - After installation, phone will be stuck at bootanimation, don't panic.
6 - Pull out battery, boot to recovery (you can see some mount errors, don't worry)
7 - Select "wipe data/factory reset" in recovery menu
8 - Select "reboot system now"
I recently update 4.3 MJ5 to 4.4.2 ND3 bootloader via odin successfully, just to inform that after repartition, bootloader update still works. If it fails, make sure to try new usb cable. Mine failed first time because of bad usb cable.
See ND 4.4.2 bootloader here http://forum.xda-developers.com/showthread.php?t=2472270 CTRL+F in the thread and find bootloader.
For some people who curious how to output partition table in Terminal.
First you need to install "parted" binary to /system/bin/
parted binary is in attachment,
then use these command in terminal
su
parted /dev/block/mmcblk0
print
Also programs to show partition tables in Google Play can't show partitions offsets, but this command could.
UPDATE 15/10/2014
I found out that in fact, Google Play apk downloads are stored in /data/com.android.providers.downloads/files/, cache partition is used to store apk downloads in old Android version.
UPDATE 24/10/2015
I also uploaded a new partition script cwm-zip file for AOSP users that will repartition system to size of 1 GB, preload 15 mb, cache 100 mb.
This will gain 3 GB of more userdata space.
Please note that once you have repartition with Repartition AOSP N7100 System 1 GB.zip
You will not be able to install Touchwiz based ROM, Touchwiz based ROMs are bigger than 1 GB.
You will have to repartition again with Repartition_N7100_16GB.zip OR Repartition_N7100_16GB_PreloadStockSize587MB.zip, note that all userdata will be deleted.
Note that I personally don't use Note 2 anymore, but this script should work. It's just simple script editing from previous files.
1 GB system partitioning for AOSP/CM is not working as
psndna88, AGNI kernel maker, tests
"it seems we cannot change SYSTEM size, else the bootloader boots only into download mode"
Thanks a lot. I will try it later.
I did repartition my device about a year ago, but I did it manually and used parted program that comes with cwm recovery. The process is fairly simple if you are familiar with unixlike OS'es. The advantage of parted us that you can resize /system partition too (CM11 requires just 400 mb on /system, and default is 1800mb).
I just tried it. It all went fine. Thanks!
My question is, can we have more space, or this is the max we can have?
I guess some space must be reserved though, so the phone can work properly.
steff195 said:
I just tried it. It all went fine. Thanks!
My question is, can we have more space, or this is the max we can have?
I guess some space must be reserved though, so the phone can work properly.
Click to expand...
Click to collapse
Yes we can have just a little bit more space. You may try to shrink cache partition to 60 mbs, shrink preload to 4 mb. That would gain 54 mbs only. I configured cache and preload to be bigger than this for safety purpose. Maybe it will be use to store small files in the future. We also need to keep the number of partitions to be the same as stock one, else everything will malfunction. I still have no ideas what does OTA and TOMBSTONES do.
Sent from my GT-N7100 using XDA Free mobile app
great guide, will try
reminds me of the htc days when we could s off and flash various hboots to increase/decrease various partitions
so, this will accomodate all current custom roms ? edit - just read your warning to check : thanks:
ninekaw9 said:
Yes we can have just a little bit more space. You may try to shrink cache partition to 60 mbs, shrink preload to 4 mb. That would gain 54 mbs only. I configured cache and preload to be bigger than this for safety purpose. Maybe it will be use to store small files in the future. We also need to keep the number of partitions to be the same as stock one, else everything will malfunction. I still have no ideas what does OTA and TOMBSTONES do.
Sent from my GT-N7100 using XDA Free mobile app
Click to expand...
Click to collapse
Then I'll just leave it this way. Don't want my phone to malfunction if I push this to the extreme.
Thanks again!
steff195 said:
Then I'll just leave it this way. Don't want my phone to malfunction if I push this to the extreme.
Thanks again!
Click to expand...
Click to collapse
only a small problem, it does not format anything and says that there is no sim inside, I sincerely hope that you manage to solve the problem ....
also the modem is not installed ...
I saw your post on the DN3 V5+ thread which led me... Seems to be a great concept, especially considering that one of the first things I do upon flashing a stock-based rom is to delete most Sammy things on it.
I understand that you need Philz to flash this; will the latest V6.41.4 do?
Also, do you know of anyway to save all system settings so as to restore them later? I can backup apps and their data but not the stock system settings themselves.
Can we increase system partition???
I need more space in system......
ulkika said:
only a small problem, it does not format anything and says that there is no sim inside, I sincerely hope that you manage to solve the problem ....
also the modem is not installed ...
Click to expand...
Click to collapse
Man, I tried via Philz 6.41.6, since it was recommended in OP. I usually use TWRP, had a nandroid backup of everything including Modem made with TWRP which I placed on external card.
Had the mounting problem after flashing script and rebooting recovery, but I manually solved them, as described in 1st post. Then reflashed TWRP and restored my nandroid from external card. Then also restored my internal sd files (music, games obb, etc) which I saved on pc.
I have no error, I have ND3 modem present, all fine, phone works as before. And 12.1gb total space instead of 10.4 which I had before.
Thanks again!:good:
ulkika said:
only a small problem, it does not format anything and says that there is no sim inside, I sincerely hope that you manage to solve the problem ....
also the modem is not installed ...
Click to expand...
Click to collapse
How come your modem firmware is gone?
Have you try installing ROMs again, most rom installer will flash modem firmware.
My script doesn't touch modem partition at all.
Just partition cache and after that, see the partition table.
Rickav said:
I saw your post on the DN3 V5+ thread which led me... Seems to be a great concept, especially considering that one of the first things I do upon flashing a stock-based rom is to delete most Sammy things on it.
I understand that you need Philz to flash this; will the latest V6.41.4 do?
Also, do you know of anyway to save all system settings so as to restore them later? I can backup apps and their data but not the stock system settings themselves.
Click to expand...
Click to collapse
steff195 used Philz 6.41.6, and it worked.
Well, DN3 v5+ update-script has the commands to delete Android Setting Database on install.
Because you restore data first, then flash DN3v5+ which triggering deletion of Android Setting Database.
So you have to backup android setting database using titanium backup before repartition, then restore after repartition.
Or after repartitioning, install DN3 v5+ first, then restore data using nandroid.
I also have weird problem after deleting Android Setting Database on DN3 v5+. New setting generated is really courrupted. It breaks home button, notification toggles expanding, lock screen, and much more. Everybody else seem to be fine of android setting database regeneration. Weird.
MBariya said:
Can we increase system partition???
I need more space in system......
Click to expand...
Click to collapse
Yes you can.
Extract my .zip script, then open the updater-binary with your favorite text editor, I prefer Notepad++.
Find these line
parted /dev/block/mmcblk0 mkpart primary 168MB 270MB -> CACHE
parted /dev/block/mmcblk0 mkpart primary 270MB 2417MB -> SYSTEM
parted /dev/block/mmcblk0 mkpart primary 2417MB 2432MB -> HIDDEN
parted /dev/block/mmcblk0 mkpart primary 2432MB 2440MB -> OTA
parted /dev/block/mmcblk0 mkpart primary 2440MB 15.8GB -> USERDATA
It is pretty easy to understand indeed, first number after word "primary" is the start offset of the partition, second one is the end.
You may change those number. But remember that CACHE partition must always be bigger than 50 MBs to store google play apk download. Google stated that google play apk max size is 50 mb, bigger than that will use .obb to help.
I recommend you to keep OTA size 8 MB, cause I don't know what it does.
HIDDEN can be shrink up to 5 MB I doubt. I suspect that shrink up to 4 MB can cause issue, I don't know if you set size for 4 MB, will it exceed minimum partition size required.
However, numbers in red can't be changed, they must be 168MB and 15.8 GB the same.
And do not change order of partitions, and there must be 5 partitions. You can't remove HIDDEN and OTA, else partition order and number will wrong, and I think a lot of things will break, including recovery.
After you modified the script. Zip them and put in your phone and flash! :laugh:
philz_touch_6.41.6-n7100.zip.md5 but the problem is that not format data,i solve whith reinstall nd3 and after root and restore system but the patch is not functionally at my device.
---------- Post added at 11:50 AM ---------- Previous post was at 11:45 AM ----------
ninekaw9 said:
How come your modem firmware is gone?
Have you try installing ROMs again, most rom installer will flash modem firmware.
My script doesn't touch modem partition at all.
Just partition cache and after that, see the partition table.
Click to expand...
Click to collapse
I do not know what happens because of it, I can not see the pictures because you do not know how to send to you but that happens on the screen while doing the second restart to do manually format the system tells me that the memory is not formatted.
then I tried to reinstall the old rom and told me that he could not find the modem, it does not restart no line present it tell insert telephone card ... in the end I had to reinstall ND3, before I tried it with the pit from you and given after but not without changing anything in the system memory space....
ulkika said:
philz_touch_6.41.6-n7100.zip.md5 but the problem is that not format data,i solve whith reinstall nd3 and after root and restore system but the patch is not functionally at my device.
---------- Post added at 11:50 AM ---------- Previous post was at 11:45 AM ----------
I do not know what happens because of it, I can not see the pictures because you do not know how to send to you but that happens on the screen while doing the second restart to do manually format the system tells me that the memory is not formatted.
then I tried to reinstall the old rom and told me that he could not find the modem, it does not restart no line present it tell insert telephone card ... in the end I had to reinstall ND3, before I tried it with the pit from you and given after but not without changing anything in the system memory space....
Click to expand...
Click to collapse
I am very confused with your language. After you used my script, did you go to "Mounts and Storage", then format SYSTEM DATA CACHE PRELOAD?
only an other question,i use x-treme rom 2.1 is possible that is the problem...
ulkika said:
only an other question,i use x-treme rom 2.1 is possible that is the problem...
Click to expand...
Click to collapse
I'm downloading it and will diagnose the installation file.
ninekaw9 said:
I am very confused with your language. After you used my script, did you go to "Mounts and Storage", then format SYSTEM DATA CACHE PRELOAD?
Click to expand...
Click to collapse
after reboot of first install, is impossible for me format prelod .system and cache....
ulkika said:
after reboot of first install, is impossible for me format prelod .system and cache....
Click to expand...
Click to collapse
Try this Philz Touch version. It is the version that I used to repartition on my device.
I'm still downloading your ROM, mediafire is quite slow today.
TURBO DATA - Get an 8GB Data-Partition!
Use SD-EXT as new Data partition
presented by
~~~~~~~~ delta-roh ~~~~~~~~
HIT THANKS for delta-roh (1st post) And, please, don't forget to Rate this Thread - thank you!
You love your Sensation, but:
The 1 GB of the data partition limits you?
You don't like Link2SD?
You don't want to use the to SDCard feature?
You don't want to use data2sd or similar scripts?
You are afraid of broken links?
Then this is the Turbo for your HTC Sensation
Features of TURBO DATA
Version 3.01 (release date 01st Nov 2016)
new corrected error in cpio to support 2nd level subdirectories
new Mod for Ivanich CM11 to get Data on SD-Ext, but have Dalvik internally (FAST!!!) - refer to Post 2
Version 3.00 (release date 29th Mar 2015)
new now my Delta-Roh cpio.bat is integrated
new Delta-Roh cpio without cygwin! - all tools integrated als always
new No need of Windows 8.1 administrative rights (as for cygwin)!
new Now manual changes can be done to all scripts of the ramdisk
new Very easy handling!
new This version now also supports ViperS-Roms!
new If you like, you can download only the Delta-Roh cpio package (see below)
Version 2.02 (release date 02nd Mar 2015)
new now also handles .img (boot-Image files)
new added loop for performing patterns more flexible
new added patch check - exit if no pattern was found
new added ramdisk size check
Version 1.04 (release date 21st Feb 2015)
First Version by delta-roh
new handles normal flashable zip, that include a boot.img
new works fully automatically
new support of command line call
new Drag+Drop support
new A lot of checks to make the procedure safe
new Writes a logfile parallel to the screen output
new Does not change your original zip
new the resulting zip can be flashed directly
Click to expand...
Click to collapse
Idea:
Our beloved Sensation comes only with 1 GB of available internal memory and that is too less to work, even if you don't install a lot of games. When I tried several thinks (app2sd, app2sd-ext, Link2SD etc.) I recognized, that modern SD-Cards are very fast and our Sennsation has got a very good interface to suppport high speeds. Even better, the SD-Cards of SanDisk (SanDisk Extreme Pro, SanDisk Extreme Plus and SanDisk Extreme) are even faster, than the internal memory. Therefore I got the idea, to make a seperate external SD partition (SD-Ext) to the new Data partition. It works flawlessly and fast. But how does it work? The first step of the Android startup process is to mount the boot image and to mount a ramdisk, that is part of the boot image. In this ramdisk you will find the mount table for the primary partitions - it is called fstab.pyramid. Here you will find, that the data partition is mounted to /dev/block/platform/msm_sdcc.1/by-name/userdata or to /dev/block/mmcblk0p23. The only thing to do is, to change this to /dev/block/mmcblk1p2, which is the second partition of the SD-Card.
The attached ZIP now contains a Batch file together with all necessary tools to do this job for you completely automatically. It extracts the boot.img file from your flashable zip, extracts the kernel and the ramdisk.gz, unpacks the ramdisk, patches the fstab.pyramid as described above, repacks the ramdisk, repacks the boot.img, makes a copy of the original flashable zip, exchanges the boot.img in this new zip - done! You have got a new flashable zip, that will mount the second SD-Card partition as your new data partition. I do this with an 8 GB sd-ext partition and therefore now have got a Sensation with 8 GB of available internal memory - no need to care about memory or tools like Link2SD any longer!
Click to expand...
Click to collapse
Installation:
Take these steps:
the attached zip contains the batch and all needed utilities
extract the directory tree in the zip to a location on your Windows harddisk
place your flashable zip or boot-Image in the main directory which also contains this batch
open a cmd-windows by clicking "Start here.bat"
call "MakeNewImage" with your flashable zip or boot-Image: MakeNewImage <your-rom-or-image.zip>
or
just Drag+Drop your flashable zip or boot-Image to MakeNewImage.bat
after processing you will find the new flashable zip or boot-Image in the subdir "new"
all original parts (boot.img, kernel, ramdisk(.gz)) are in the subdir "original"
all new parts (boot.img, kernel, ramdisk(.gz) and your new flashable zip) will be in the subdir "new"
if you call the batch another time (or Drag&Drop a new image to MakeNewImage.bat, the complete subdirs will be deleted before processing the new fashable zip; the batch will then create the directories again with the new parts
if you like, you can make additional changes to the fstab.pyramid or init.rc ...
Click to expand...
Click to collapse
YOU MUST READ THIS OR YOU WILL BRICK YOUR DEVICE:
You have to know this - read carefully:
Tested with a lot of CM11 and CM12 Roms
It will only work for fashable zips that contain a boot.img, like @SultanXDA CM11, @ivanich CM12, @shantur CM12 - it will NOT work e.g. for @mike1986 Android Revolution, as this does not contain a boot.img.
ViperS 5.2.1 / Viper 5.3.0 do not work at the moment.
You should only make your sd-ext to the new /data partition if you have got a highspeed sd-card e.g. SanDisk Extreme-series; otherwise it will work, but your Sensation will slow down.
You need a sd-ext partition on your sd-card as second (!) partition (/dev/block/mmcblk1p2); create it within the recovery or use e.g. MiniTool Partition Wizzard and create a first partition as primary fat-formated and a second partition as primary ext4 formated. IF YOU HAVE NOT A SECOND PARTITION, YOUR DEVICE WILL NOT BOOT!
This is ONLY for the HTC Sensation/XE; it can work also for flashable images of other devices, but then you have to make your changes to fstab and/or init.rc manually!
After flashing the new image the /data partition will be created on the second SD-Card partition (sd-ext).
After booting for the first time you can restore a backup by using e.g. Titanium.
If you want to look at /data within the recovery you have to mount sd-ext and then flash the Aroma Filemanager; there you can see the complete data partition by browsing to sd-ext.
You can make a nandroid backup within the recovery. Note, that the sd-ext tar file is your (new) data partition.
If you want to go back, then just flash a nandroid of a former backup or flash a not patched zip and make a clean installation.
If your rom thread provides a seperate zip for the kernel, then have a look at the provided zip! If it contains a boot.img, then it has to be patched at first by using MakeNewImage.bat in the same way as with a complete rom. If the kernel zip does not contain a boot.img but only the kernel, then you can flash it directly.
If you want to wipe Dalvik-Cache you can't do it with the "wipe Dalvik"-command in Recovery; instead go into Recovery, mount sd-ext, flash the Aroma Filemanager or use the TWRP-Filemanager, navigate to the directory sd-ext (your new /data) and delete the directory dalvik-cache.
You can not restore a data partition from a former installation to sd-ext, because the tar file also stores the partition name and, therefore, does not restore a data file to the sd-ext partition, even it you rename the backup file. As said before: Make a clean installation and then restore via e.g. Titanium.
Click to expand...
Click to collapse
Thanks:
Special thanks to:
carliv (http://forum.xda-developers.com/member.php?u=5186178)
for mkbootimg.exe (https://github.com/bgcngm/mtk-tools)
GnuWin32 (http://gnuwin32.sourceforge.net/packages.html)
for sed.exe and grep.exe (libiconv2.dll, libintl3.dll, pcre3.dll, regex2.dll)
Igor Pavlov (http://www.7-zip.de/)
for 7z.exe and 7z.dll
Karl M. Syring (http://unxutils.sourceforge.net/)
for dd.exe, gzip.exe, od.exe, printf.exe, rm.exe, sha1sum.exe, tee.exe
@danishaznita for testing the first version
Click to expand...
Click to collapse
USE IT AT YOUR OWN RISK - NO SUPPORT! READ SECTION 'MUST READ' ABOVE CAREFULLY!
DOWNLOAD TURBO DATA MOD V3.01
DOWNLOAD Delta-Roh cpio Package V1.51 (already integrated in Turbo Data Mod)
If you like my work, press
THANKS for delta-roh
And, please, don't forget to rate this thread - thank you!
If you want to use my work, please don't ask for permission, but leave my headers in my files, make a reference to me in your thread and respect the other persons in the thanks section, if you use their tools.
copyright by delta-roh 2016
Reserved
Mod for Delta-Roh MakeNewImage-V3.01
EXPLICITLY for Ivanich CM11 ONLY!!!
This mod mounts a sd-ext partition to /data and leaves the dalvik-cache on the internal
memory. Therefore you will get e.g. an 4 GByte (depends ob your sd-ext partition size) data
partition and the original 1.1 GByte internal memory as additional and fast memory for
the dalvik cache. This is the fastest way regarding the porformance of the Sensation.
Installation:
- Download and extract "Delta-Roh MakeNewImage"
- start "MakeNewImage.bat" with "cm-11-20160810-UNOFFICIAL-pyramid.zip"
- answer the question "Do you want to auto-patch fstab [y/n]" with "n" (no) - don't close the command box!
- an explorer will open in the subdir of the new ramdisk, now do the following mods:
--- override the existing "init.rc" with the new one from this zip (Download below)
--- override the existing "fstab.pyramid" with the new one from this zip (Download below)
--- create a new directory "data0" in addition to the already existing data directory
--- copy/paste (press Ctrl-C then Ctrl-V) the file "data.attrib"
--- rename the new file ("data - Copy.attrib" or named similar) to "data0.attrib"
--- now you can close the Explorer and answer the question "Manual changes finished [y/n]" with "y" (yes)
Now you will get a "sdext_cm-11-20160810-UNOFFICIAL-pyramid.zip" that can be flashed.
NOTE: You will need a sd-ext partition on your sd-card.
DOWNLOAD Ivanich CM11 DATA MOD
I think this a great idea, many thanks. I've been wanted to do it the since you mentioned the other day, I wanted a new phone too xD Well I did it today and then just seen your post. I did it on PC though (Linux) and mounted userdata as dalvik-cache so easy to wipe and maybe quicker loading (in theory). I may have mounted it differently to you (see screenshot), and are your attributes/flags the same?
hinxnz said:
I think this a great idea, many thanks. I've been wanted to do it the since you mentioned the other day, I wanted a new phone too xD Well I did it today and then just seen your post. I did it on PC though (Linux) and mounted userdata as dalvik-cache so easy to wipe and maybe quicker loading (in theory). I may have mounted it differently to you (see screenshot), and are your attributes/flags the same?
Click to expand...
Click to collapse
My Turbo Data mounts sd-ext to data (same to you) but don't mounts the old data to the dalvik-cache, because I have a SanDisk Extreme Plus and it is faster than the internal memory xD
BTW, my batch works completely with Windows and even without cygwin. At the moment I am working at a cpio batch that works with Windows without elevated rights and without cygwin as well...... xD
Question: what did you do to mount dalvik-cache to the original data partition? And which Filesystem manager did you use in the screen shots?
delta-roh said:
My Turbo Data mounts sd-ext to data (same to you) but don't mounts the old data to the dalvik-cache, because I have a SanDisk Extreme Plus and it is faster than the internal memory xD
BTW, my batch works completely with Windows and even without cygwin. At the moment I am working at a cpio batch that works with Windows without elevated rights and without cygwin as well...... xD
Question: what did you do to mount dalvik-cache to the original data partition? And which Filesystem manager did you use in the screen shots?
Click to expand...
Click to collapse
Yeah I must have the same SDcard as you by the sounds of it xD have so for ages and probably the reason I've been using Mounts2SD for so long but yeah got sick of it not working as expected as CM12/Android 5.x matures. Thanks to your idea/earlier post though and a bit of mucking around with it as I did have a few hiccups, eg. offset ramdisk address, all went well in the end and is quite a simple process once the know how. Over the time of using M2SD I felt like write speeds were slower (not actually tested but just how it felt) hence the reason why I use the f2fs file system on the sd-ext and I didn't want to leave my internal data partition all alone and unused. I was deciding and still am really for what to use it for, first ideas was for private storage or for app data but then I thought Dalvik-cache could be good because wiping it would be easier without modifying recovery or applying a script. I did this all on native linux (ubuntu) with a few binaries added, I was thinking of making a flashable zip to do the whole process if possible and I think it is but would be a bit of experimenting process and don't really have the time as yet and also you have got this underway already, so I probably wont. I don't mind posting the binaries I used and what I did if it will help, maybe you'd be into creating a version that doesn’t require a PC. The file manager I'm using is FX File Explorer (pro), I only just switched to it, well bout a month ago and I find it a good alternative to ES or Root explorer, it also has the material design theme which goes nicely with CM12 and has 90% of all the necessary features I need. I mounted internal data with fstab which I've attached for you and I've linked the /data/dalvik-cache/arm directory to it. You can name the internal data partition to whatever you like too.
This also could be good for those that corrupted their data partition too that was caused by the twrp recovery version from their site (not ivanich's version).
This is also good because I don't have to link things like Googles Drive cache to sd-ext anymore, for example it caches a copy into data say from a ROM downloaded with it.
Edit: Just checked my SDcard and it older than yours and probably not as quick but mines a 32Gb SanDisk Ultra SDHC-I and works fast enough for now.
hinxnz said:
Yeah I must have the same SDcard as you by the sounds of it xD have so for ages and probably the reason I've been using Mounts2SD for so long but yeah got sick of it not working as expected as CM12/Android 5.x matures. Thanks to your idea/earlier post though and a bit of mucking around with it as I did have a few hiccups, eg. offset ramdisk address, all went well in the end and is quite a simple process once the know how. Over the time of using M2SD I felt like write speeds were slower (not actually tested but just how it felt) hence the reason why I use the f2fs file system on the sd-ext and I didn't want to leave my internal data partition all alone and unused. I was deciding and still am really for what to use it for, first ideas was for private storage or for app data but then I thought Dalvik-cache could be good because wiping it would be easier without modifying recovery or applying a script. I did this all on native linux (ubuntu) with a few binaries added, I was thinking of making a flashable zip to do the whole process if possible and I think it is but would be a bit of experimenting process and don't really have the time as yet and also you have got this underway already, so I probably wont. I don't mind posting the binaries I used and what I did if it will help, maybe you'd be into creating a version that doesn’t require a PC. The file manager I'm using is FX File Explorer (pro), I only just switched to it, well bout a month ago and I find it a good alternative to ES or Root explorer, it also has the material design theme which goes nicely with CM12 and has 90% of all the necessary features I need. I mounted internal data with fstab which I've attached for you and I've linked the /data/dalvik-cache/arm directory to it. You can name the internal data partition to whatever you like too.
This also could be good for those that corrupted their data partition too that was caused by the twrp recovery version from their site (not ivanich's version).
This is also good because I don't have to link things like Googles Drive cache to sd-ext anymore, for example it caches a copy into data say from a ROM downloaded with it.
Click to expand...
Click to collapse
You mounted userdata to /dalvik-cache and I suppose you then changed the init.rc to link the dalvik-cache to /dalvik-cache - right?
delta-roh said:
You mounted userdata to /dalvik-cache and I suppose you then changed the init.rc to link the dalvik-cache to /dalvik-cache - right?
Click to expand...
Click to collapse
Yes that is correct.
Code:
# symlink dalvik-cache to internal location
symlink /dalvik-cache/arm /data/dalvik-cache/arm
hinxnz said:
Yes that is correct.
Code:
# symlink dalvik-cache to internal location
symlink /data/dalvik-cache/arm /dalvik-cache/arm
Click to expand...
Click to collapse
Why not this way?
Code:
symlink /data/dalvik-cache /dalvik-cache
delta-roh said:
Why not this way?
Code:
symlink /data/dalvik-cache /dalvik-cache
Click to expand...
Click to collapse
I did it this way because in the past, I've had issues with linking dalvik-cache to other locations due to SELinux but only on later versions of Android 5.x though.
But then again I haven't tried this approach with this configuration yet.
thanks delta roh..
so, at least how much R/W speed that need run this?
based on Sandisk Extreme spec, min speed is around 60MB/s for read. is it correct?
phan_tom said:
thanks delta roh..
so, at least how much R/W speed that need run this?
based on Sandisk Extreme spec, min speed is around 60MB/s for read. is it correct?
Click to expand...
Click to collapse
Sandisk Extreme is the highest u can go , i think any Class 10 sdcard can handle this , but with a little lower speed
Sent from my Note 2
phan_tom said:
thanks delta roh..
so, at least how much R/W speed that need run this?
based on Sandisk Extreme spec, min speed is around 60MB/s for read. is it correct?
Click to expand...
Click to collapse
The internal memory (original /data) has got about 30 MB/s read and about 15 MB/s write speed. The card has to match these values. But the speed declarations of the cards are allways higher, than they are in real life! A SanDisk Extreme matches these speeds in real live. The Extreme Plus and Pro are better and will give you REAL FUN!
Just try it - to have a Senni with e.g. 8GB internal memory is awesome!
danishaznita said:
Sandisk Extreme is the highest u can go , i think any Class 10 sdcard can handle this , but with a little lower speed
Sent from my Note 2
Click to expand...
Click to collapse
Right! Having 8GB of internal memory and no mem-problems any more is also worth a little bit less speed (in the case you got no SanDisk Extreme). BTW: Thank you for testing the pre-releases and did you try the release 1.04?
Unfortunately,
Your method does NOT suits me fine - extremely laggy and slow.
I have tried it with the latest ivanich CM11 and CM12 builds.
I have preliminary made an 8Gb ext4 partition on my 32GB class 10 MicroSD card.
I always set governor to intellidemand, clock to 1242MHz and use cfq for I/O.
Will test Links2SD method now.
Nevertheless,
keep up the good work!
ChimeyJimmey said:
Unfortunately,
Your method does NOT suits me fine - extremely laggy and slow.
I have tried it with the latest ivanich CM11 and CM12 builds.
I have preliminary made an 8Gb ext4 partition on my 32GB class 10 MicroSD card.
I always set governor to intellidemand, clock to 1242MHz and use cfq for I/O.
Will test Links2SD method now.
Nevertheless,
keep up the good work!
Click to expand...
Click to collapse
I tried the CM12 build of ivanich and it has got an extrem low performance of the runtime environment (in Antutu 77 compared to Sultans CM11 with 900) and I tested it with dalvik-cache in the data partition and not on sdext. It seems as if the runtime system was compiled with debug options.
delta-roh said:
I tried the CM12 build of ivanich and it has got an extrem low performance of the runtime environment (in Antutu 77 compared to Sultans CM11 with 900) and I tested it with dalvik-cache in the data partition and not on sdext. It seems as if the runtime system was compiled with debug options.
Click to expand...
Click to collapse
Huh I just downloaded Antutu from playstore to test myself, still on the same configuration and my score is way higher than you got on CM12 and even higher than your CM11 score, only ran the benchmark once so it not like the highest out of several either on stock frequency, governor, scheduler etc.
Will it work on viper sense5.0 and what if my mcard crashes because sometimes it stops working and I have to format my mcard. So what if it crashes will it affect my senny
cutejerk420 said:
Will it work on viper sense5.0 and what if my mcard crashes because sometimes it stops working and I have to format my mcard. So what if it crashes will it affect my senny
Click to expand...
Click to collapse
Nobody is able to answer these questions. Normally SD-Cards are absolutely stable. Make a regular nandroid backup e.g. every day.
hinxnz said:
Huh I just downloaded Antutu from playstore to test myself, still on the same configuration and my score is way higher than you got on CM12 and even higher than your CM11 score, only ran the benchmark once so it not like the highest out of several either on stock frequency, governor, scheduler etc.
Click to expand...
Click to collapse
Remarkable! Please post your configuration - do you use F2FS and on which partitions?
delta-roh said:
Remarkable! Please post your configuration - do you use F2FS and on which partitions?
Click to expand...
Click to collapse
I use f2fs on sd-ext and ext4 on userdata, I use the fstab which I posted earlier and added the symlink to init.rc, on line 319 to be exact xD
Unpacking, repacking and making boot image was done on Linux, not sure if that would make a difference though.
Hi guys, I unlocked the bootloader in my HTC ONE A9 and I installed the TWRP recovery it asks me how to screen whether to keep the read-only and therefore without modifying the partition system or allowing the changes ... I have the official rom and honestly not I currently intend to change rom..I haven't received + OTA updates for several years now ... I don't know what to choose in this screen because as I should put Magisk and how do you know the "safetyNet" check if it finds the modified system folder pass the control ... now you who are + experts than me I ask you the courtesy to clarify this doubt ... there is a fact that even a zip could modify the system folder ... so if I choose allow changes and install the Magisk zip automatically makes changes to the system folder and then the SafetyNet does not pass?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@Captain_Throwback
I ask for your help please, because only you can help me in this problem ... I just don't know how to solve. I am desperate
Practically I put the TWRP latest version 3.4 from this link h**ps://dl.twrp.me/hiae/ (I can't put the full link because I don't have 10 posts yet, it seemed right to write it to make you understand where I downloaded them from) , I load it via the windows cmd command and until I access recovery everything is working, as soon as I enter recovery the first time TWRP asks me as per the screen in the first post whether to keep the read only or allow the changes and I choose "allow changes by swiping down" ... then I restart and from that moment the phone restarts continuously in loop ... I then reflected the original rom (even before I had the original rom) , I change version this time and put the twrp 3.2.1.0 as usual, everything works before accessing recovery, as soon as I access recovery, a problem appears in the decryption and then manages to start the twrp menu I always put allow changes to the file system, I go out and loop again, restarting continuously ... now I am thinking possible that the problem is that I have to select keep read only? otherwise I can't explain why everything works and as soon as I enter recovery for the first time and I swipe on allow the changes then restart the phone in loop ... When it goes in loop I can access recovery and the strange thing is that the language is always in English although I select the Italian language, it is also strange that the setting is not saved ....
android version is 7.0 (software 2.17.401.2)
so now I'm reflecting the original rom a second time without putting any twrp waiting for your answer in understanding where the problem lies .. I hope you can help me .. thank you very much in advance. @Captain_Throwback
fabulas_ said:
@Captain_Throwback
I ask for your help please, because only you can help me in this problem ... I just don't know how to solve. I am desperate
Practically I put the TWRP latest version 3.4 from this link h**ps://dl.twrp.me/hiae/ (I can't put the full link because I don't have 10 posts yet, it seemed right to write it to make you understand where I downloaded them from) , I load it via the windows cmd command and until I access recovery everything is working, as soon as I enter recovery the first time TWRP asks me as per the screen in the first post whether to keep the read only or allow the changes and I choose "allow changes by swiping down" ... then I restart and from that moment the phone restarts continuously in loop ... I then reflected the original rom (even before I had the original rom) , I change version this time and put the twrp 3.2.1.0 as usual, everything works before accessing recovery, as soon as I access recovery, a problem appears in the decryption and then manages to start the twrp menu I always put allow changes to the file system, I go out and loop again, restarting continuously ... now I am thinking possible that the problem is that I have to select keep read only? otherwise I can't explain why everything works and as soon as I enter recovery for the first time and I swipe on allow the changes then restart the phone in loop ... When it goes in loop I can access recovery and the strange thing is that the language is always in English although I select the Italian language, it is also strange that the setting is not saved ....
so now I'm reflecting the original rom a second time without putting any twrp waiting for your answer in understanding where the problem lies .. I hope you can help me .. thank you very much in advance. @Captain_Throwback
Click to expand...
Click to collapse
Just don't allow changes. It's not that hard, lol.
Captain_Throwback said:
Just don't allow changes. It's not that hard, lol.
Click to expand...
Click to collapse
@Captain_Throwback
you are right, but since everywhere it says that you have to allow the changes it seemed very strange that if I allowed the changes it would go in a loop ... I reflected the rom again, put the Twrp 3.4 back and this time I gave "keep read only "and the problem did not arise ... but there are still a series of problems in TWRP, at the beginning when I start TWRP immediately after entering the encryption sequence, the screen appears where it says:" unable to mont storage "in red and then successfully decrypted and immediately the TWRP menu appears ..... I tried to make a backup but there are a series of errors as you can see from the screen below ... I also flashed magisk v21 from twrp and here too it gave me errors at the beginning similar to the ones it gave me for backup, although in this case it told me successfully installed at the end. After I did a check with a root checker and it tells me that the root was not done, also with magisk manager I did a SafetyNet check and it gives me both false, both CTS certified and base intefrity ... so there is something that it's not working properly ....
Before loading Magisk from recovery I had checked the SafetyNet with an app and it gave me CTS false and basic integrity true, then after loading Magisk both false ...
Then each time I select the Italian language in Twrp and the next time it always starts in English ... I don't understand why it didn't save the setting.
is there any particular version compatible with HTC One A9 of TWRP? I downloaded the hiae version from the link posted in the previous post ... I honestly don't know how to fix ..
Can you help me please to solve? thank you
fabulas_ said:
@Captain_Throwback
you are right, but since everywhere it says that you have to allow the changes it seemed very strange that if I allowed the changes it would go in a loop ... I reflected the rom again, put the Twrp 3.4 back and this time I gave "keep read only "and the problem did not arise ... but there are still a series of problems in TWRP, at the beginning when I start TWRP immediately after entering the encryption sequence, the screen appears where it says:" unable to mont storage "in red and then successfully decrypted and immediately the TWRP menu appears ..... I tried to make a backup but there are a series of errors as you can see from the screen below ... I also flashed magisk v21 from twrp and here too it gave me errors at the beginning similar to the ones it gave me for backup, although in this case it told me successfully installed at the end. After I did a check with a root checker and it tells me that the root was not done, also with magisk manager I did a SafetyNet check and it gives me both false, both CTS certified and base intefrity ... so there is something that it's not working properly ....
Before loading Magisk from recovery I had checked the SafetyNet with an app and it gave me CTS false and basic integrity true, then after loading Magisk both false ...
Then each time I select the Italian language in Twrp and the next time it always starts in English ... I don't understand why it didn't save the setting.
is there any particular version compatible with HTC One A9 of TWRP? I downloaded the hiae version from the link posted in the previous post ... I honestly don't know how to fix ..
Can you help me please to solve? thank you
Click to expand...
Click to collapse
If you're having issues with TWRP, please post them in the TWRP thread, and follow the instructions in that thread's OP for posting a log. I can then review the log and reply there.
P.S. And while you're at it, you should read the FAQ in the TWRP thread to get some better understanding of why that read-only page is there.
P.P.S. Ugh, I forgot my TWRP thread got lost when they flattened the forum. Well, recovery.log is in /tmp, so you can use adb pull to retrieve it, or if you have an SD card in the device, you can switch to it as your default storage in the Mount page and then use Advanced -> Copy Log.
P.P.P.S. I'm using TWRP and Magisk 21 without any issue on my device, but if you're on old firmware, then that could be why it's not working for you. Let me upload a debug TWRP version and we can see exactly where things are going wrong. Give me an hour or so to build it.
Captain_Throwback said:
If you're having issues with TWRP, please post them in the TWRP thread, and follow the instructions in that thread's OP for posting a log. I can then review the log and reply there.
P.S. And while you're at it, you should read the FAQ in the TWRP thread to get some better understanding of why that read-only page is there.
P.P.S. Ugh, I forgot my TWRP thread got lost when they flattened the forum. Well, recovery.log is in /tmp, so you can use adb pull to retrieve it, or if you have an SD card in the device, you can switch to it as your default storage in the Mount page and then use Advanced -> Copy Log.
P.P.P.S. I'm using TWRP and Magisk 21 without any issue on my device, but if you're on old firmware, then that could be why it's not working for you. Let me upload a debug TWRP version and we can see exactly where things are going wrong. Give me an hour or so to build it.
Click to expand...
Click to collapse
the firmware version is not old, it is android version is 7.0 (software 2.17.401.2) taken here on xda and it is the same version I had received via OTA.
Since the root with Magisk was not successful and, moreover, the safetyNET gave me both CTS and false basic integrity I reflected the rom again now so that we have a clean phone .. first we solve the problems with TWRP and then after I see to put Magisk ... now so I reflashed the rom and checking the Safetynet without having put the Twrp yet it gives me false CTS and basic integrity true, I then put the twrp 3.4 and the Safetynet remained the same ... my fear is that when I put Magisk back even the base integrity becomes false as before ... but for the moment I don't put Magisk ...
I did the backup again with the twrp to see if anything had changed but nothing, same errors ...
I am very willing to do what you ask me, the problem is that I am not an expert, so I can only do it if you tell me step by step what to do ...
You asked me for the recovery.log but I didn't understand how to recover it, could you explain me step by step in detail? you told me that you were preparing the debug that then I should load I don't know if this is enough or you always need the recovery.log ... anyway yes i have an sd card in the phone ...
As for writing in the TWRP room, I initially searched for it but couldn't find it and so I wrote in my phone section.
thank you very much for your willingness to help me
fabulas_ said:
the firmware version is not old, it is android version is 7.0 (software 2.17.401.2) taken here on xda and it is the same version I had received via OTA.
Since the root with Magisk was not successful and, moreover, the safetyNET gave me both CTS and false basic integrity I reflected the rom again now so that we have a clean phone .. first we solve the problems with TWRP and then after I see to put Magisk ... now so I reflashed the rom and checking the Safetynet without having put the Twrp yet it gives me false CTS and basic integrity true, I then put the twrp 3.4 and the Safetynet remained the same ... my fear is that when I put Magisk back even the base integrity becomes false as before ... but for the moment I don't put Magisk ...
I did the backup again with the twrp to see if anything had changed but nothing, same errors ...
I am very willing to do what you ask me, the problem is that I am not an expert, so I can only do it if you tell me step by step what to do ...
You asked me for the recovery.log but I didn't understand how to recover it, could you explain me step by step in detail? you told me that you were preparing the debug that then I should load I don't know if this is enough or you always need the recovery.log ... anyway yes i have an sd card in the phone ...
As for writing in the TWRP room, I initially searched for it but couldn't find it and so I wrote in my phone section.
thank you very much for your willingness to help me
Click to expand...
Click to collapse
TWRP thread has been re-created here: https://forum.xda-developers.com/one-a9/recovery-twrp-touch-recovery-t4185995
Please note the in the OP there how to pull a log, and then post your recovery log there. You don't need to perform a backup, just boot TWRP and then pull the log.
Captain_Throwback said:
TWRP thread has been re-created here: https://forum.xda-developers.com/one-a9/recovery-twrp-touch-recovery-t4185995
Please note the in the OP there how to pull a log, and then post your recovery log there. You don't need to perform a backup, just boot TWRP and then pull the log.
Click to expand...
Click to collapse
I have recovered the recovery.log file
I started the Twrp -advanced-copy log and saved it in the SD card .. is that correct?
I'm sorry I didn't understand if I have to post the log in the thread you linked from the TWRP or I have to put it here ... the file recovery.log I upload it to a host site and I'll put the link .. just tell me in which thread. Thanks.
fabulas_ said:
I have recovered the recovery.log file
I started the Twrp -advanced-copy log and saved it in the SD card .. is that correct?
I'm sorry I didn't understand if I have to post the log in the thread you linked from the TWRP or I have to put it here ... the file recovery.log I upload it to a host site and I'll put the link .. just tell me in which thread. Thanks.
Click to expand...
Click to collapse
TWRP thread.
Captain_Throwback said:
TWRP thread.
Click to expand...
Click to collapse
log loaded into the thread
fabulas_ said:
Ok perfect .. very kind. Thanks.
Before unlocking the bootloader and then doing the root I had a space problem as the internal memory is only 16gb ... now since the phone is still fine I wanted to find a solution.
And I saw that through the Link2SD app I can move some apps to the microsd (maybe the apps I use less), to do this I read that you have to make a partition in the microsd so that you can move the apps and that it is seen as "an extension of the internal memory" ... so I should connect the microsd to the pc to create the partition ... then there is another way which is to format the microsd as internal memory but this is not recommended ... while instead do as I wrote before a partition in the microsd and use it as an "extension of the internal memory" do you think it is a good solution to solve the app space problem? because I only have the apps in the internal memory ... the media are automatically saved on microsd ... so in theory by making a partition in the microsd the partition is an extension of the internal memory and the non-partitioned part should be used by the camera to save photos and videos .. do you think it's feasible?
One last thing as an app to remove the various system apps that I don't use like some Google apps, now that I have root I can do it ... which app do you recommend to do this?
Click to expand...
Click to collapse
Replying here as this conversation is no longer related to TWRP.
I'd actually recommend partially formatting the SD card as internal memory (depending on the size and speed of your SD card). If you have a large capacity UHS-3 card, you can set it up in Android with mixed adoptable storage, so that part of the SD card gets allocated as additional Phone Storage, and the rest can still be used as a standard SD card. That's how I have the card in my A9 set up because of the memory issues you mentioned.
The thread I used to convert mine is here: https://forum.xda-developers.com/idol-3/general/make-sd-card-semi-adopted-t3399510
An alternative link is here: https://android.stackexchange.com/q...into-two-parts-part-adoptable-storage-and-par
(both describe the same process)
Once that's done, you'll have an option to move data for each supported app to the SD card, or you can migrate all of your data to the new partition.
I don't recommend removing any system apps - rather I would just disable apps that you don't need in Settings. You can't really reclaim the space and do anything with it, since system is read-only. There are also ways to "remove" the apps systemlessly using Magisk, but you'll have to research that on your own if you choose to go that route.
EDIT: I have a 128GB card which I split into two 64GB partitions to give me more internal space, while retaining portable storage. This is what that looks like in Android.
EDIT 2: FYI - The TWRP you're currently using fully supports identifying and mounting mixed Adoptable storage, while the official TWRP doesn't. So you'll want to make sure you stay on that one if you decide to go that route.
Captain_Throwback said:
Replying here as this conversation is no longer related to TWRP.
I'd actually recommend partially formatting the SD card as internal memory (depending on the size and speed of your SD card). If you have a large capacity UFS-3 card, you can set it up in Android with mixed adoptable storage, so that part of the SD card gets allocated as additional Phone Storage, and the rest can still be used as a standard SD card. That's how I have the card in my A9 set up because of the memory issues you mentioned.
The thread I used to convert mine is here: https://forum.xda-developers.com/idol-3/general/make-sd-card-semi-adopted-t3399510
An alternative link is here: https://android.stackexchange.com/q...into-two-parts-part-adoptable-storage-and-par
(both describe the same process)
Once that's done, you'll have an option to move data for each supported app to the SD card, or you can migrate all of your data to the new partition.
I don't recommend removing any system apps - rather I would just disable apps that you don't need in Settings. You can't really reclaim the space and do anything with it, since system is read-only. There are also ways to "remove" the apps systemlessly using Magisk, but you'll have to research that on your own if you choose to go that route.
EDIT: I have a 128GB card which I split into two 64GB partitions to give me more internal space, while retaining portable storage. This is what that looks like in Android.
EDIT 2: FYI - The TWRP you're currently using fully supports identifying and mounting mixed Adoptable storage, while the official TWRP doesn't. So you'll want to make sure you stay on that one if you decide to go that route.
Click to expand...
Click to collapse
so if I understand correctly you did exactly what I would like to do and that is a partition in the microsd to be used as an extension of the internal memory and the rest to be used as an external memory .... in any case you are confirming that it is not convenient to format the microsd as internal memory but only make a partition .. you have 32gb of internal memory I think with only 16gb it is really insufficient memory.
I have a 64gb Lexar class 10 microsd (633x microSDXC UHS I class 10) it's not slow but not even super fast ... do you think it's good for performance or will I have to buy another one?
Now I take a look at the 2 links you gave me ..
As for the system apps that I would like to uninstall they are the various apps like:
Chrome (I use another browser)
documents
Drive
Sheets
Photo
Google Play Movies
Google Play Music
Presentations
and some others
You told me that I can not do it because I have the system in read only, but it would be that famous TWRP screen where I put "keep read only" or would it be something else?
I sincerely would like to uninstall them, they just take up space and put them in my apps just to mess with them so I'd rather delete them ..
fabulas_ said:
so if I understand correctly you did exactly what I would like to do and that is a partition in the microsd to be used as an extension of the internal memory and the rest to be used as an external memory .... in any case you are confirming that it is not convenient to format the microsd as internal memory but only make a partition .. you have 32gb of internal memory I think with only 16gb it is really insufficient memory.
I have a 64gb Lexar class 10 microsd (633x microSDXC UHS I class 10) it's not slow but not even super fast ... do you think it's good for performance or will I have to buy another one?
Now I take a look at the 2 links you gave me ..
As for the system apps that I would like to uninstall they are the various apps like:
Chrome (I use another browser)
documents
Drive
Sheets
Photo
Google Play Movies
Google Play Music
Presentations
and some others
You told me that I can not do it because I have the system in read only, but it would be that famous TWRP screen where I put "keep read only" or would it be something else?
I sincerely would like to uninstall them, they just take up space and put them in my apps just to mess with them so I'd rather delete them ..
Click to expand...
Click to collapse
Deleting them saves you no space. They are on the system partition, and you can't put anything else there anyway. Disabling them is the best way to go, and like I said before, because system is read-only, you can't really delete them anyway (I'm sure you recall what happened when you allowed modifications before in TWRP). But you'll have to deal with that yourself.
I'd recommend a UHS-3 card like I said before, but you can try it with the one you have and see how it performs, just to make sure you understand the process.
Captain_Throwback said:
Deleting them saves you no space. They are on the system partition, and you can't put anything else there anyway. Disabling them is the best way to go, and like I said before, because system is read-only, you can't really delete them anyway (I'm sure you recall what happened when you allowed modifications before in TWRP). But you'll have to deal with that yourself.
I'd recommend a UHS-3 card like I said before, but you can try it with the one you have and see how it performs, just to make sure you understand the process.
Click to expand...
Click to collapse
Ok then I turn them off as you said ..
The fact of having put "keep read only", in the future this thing can create problems for me? you wrote about "But you'll have to deal with that yourself." this sentence worries me because it makes me think that maybe that choice can create problems for me in the future ...
Thinking about it, about the fact that I had that loop problem when I put "allow changes", it could not be that the reason was because the memory was compromised given the various errors it gave me and having made the "format data" that I did it fix the errors I could also do "allow changes" without anything happening?
fabulas_ said:
Ok then I turn them off as you said ..
The fact of having put "keep read only", in the future this thing can create problems for me? you wrote about "But you'll have to deal with that yourself." this sentence worries me because it makes me think that maybe that choice can create problems for me in the future ...
Thinking about it, about the fact that I had that loop problem when I put "allow changes", it could not be that the reason was because the memory was compromised given the various errors it gave me and having made the "format data" that I did it fix the errors I could also do "allow changes" without anything happening?
Click to expand...
Click to collapse
I've guided you as much as I can - at this point you should research and figure out where to go from here. Or you can try allowing modifications and see what happens. If it works, great. If not, well then you know what you have to do. You should be able to recover from any situation at this point. If you run into issues with TWRP, you know where the thread is .
Captain_Throwback said:
I've guided you as much as I can - at this point you should research and figure out where to go from here. Or you can try allowing modifications and see what happens. If it works, great. If not, well then you know what you have to do. You should be able to recover from any situation at this point. If you run into issues with TWRP, you know where the thread is .
Click to expand...
Click to collapse
if you tell me that being read only will not give me problems in the future I keep it like this ... I certainly know what to do by now as you say ... only if you tell me that being read only it will give problems and it will be a strong limitation then I try to make the last effort and try again ... if instead you tell me that I could leave it even so that it will not be a problem then I leave it like this ... now in TWRP this screen does not appear + which allows me the choice although I have always chosen "keep read only" but I never checked the box "do not ask me again" .... the possibility to write to the file system is only from TWRP or could I get it in another way?
@Captain_Throwback
I mention you because it may be that you have already read my post and therefore you would not have seen this addition.
I managed to successfully uninstall some apps like play music and play movies via adb with commands given via cmd..it worked perfectly.
practically just enter on
adb shell
and then through this command:
pm uninstall -k --user 0 com.google.android.videos (just enter the package name)
obviously you will know these things for sure it was just to tell you how I did it.
as for what I had written before .. if in the future I need to write on the system I have the possibility to modify this in some way since the choice screen on TWRP does not appear +?
As for the partition of the Microsd I gave a reading and I saw that it is done via adb so if I understand correctly always where I deleted those apps from the system ...
In the meantime I would try with the microsd that I already have is 64gb .. I would put 32gb the internal partition and the rest external ...
In this case I insert the microsd in the pc and open adb and give these commands
adb shell sm list-disks adoptable
The name of my microsde will appear then in case it is disk: 179,128 I give this other command:
adb shell sm partition disk: 179,128 mixed 50
so to do 50% internal and 50% external ... only these 2 commands I have to do and stop? Thanks
@Captain_Throwback
I made the partition to the microsd, I take the liberty of writing to you just because you recommended this method ... if you prefer I ask in the thread you indicated ..
Basically the result is that I see the partition correctly while the remaining external memory tells me that it is damaged if I click on it it tells me "configure" and makes me format the microsd, doing this obviously also removes the partition ...
I tell you exactly the steps I took ..
I ejected the microsd from Settings / Storage after which I gave these commands:
adb shell sm list-disks adoptable
adb shell sm partition disk: 179.32 mixed 65
I didn't do anything else ... the result is what I wrote you before. I am attaching a photo so you can see it. I recognize that you have already helped me enough and thank you very much ... let me know .. Thanks.
fabulas_ said:
@Captain_Throwback
I made the partition to the microsd, I take the liberty of writing to you just because you recommended this method ... if you prefer I ask in the thread you indicated ..
Basically the result is that I see the partition correctly while the remaining external memory tells me that it is damaged if I click on it it tells me "configure" and makes me format the microsd, doing this obviously also removes the partition ...
I tell you exactly the steps I took ..
I ejected the microsd from Settings / Storage after which I gave these commands:
adb shell sm list-disks adoptable
adb shell sm partition disk: 179.32 mixed 65
I didn't do anything else ... the result is what I wrote you before. I am attaching a photo so you can see it. I recognize that you have already helped me enough and thank you very much ... let me know .. Thanks.
Click to expand...
Click to collapse
Did you read both links I posted?
Pretty sure one describes that scenario...
EDIT: You can also boot into TWRP and format your portable storage and that should fix it.
Captain_Throwback said:
Did you read both links I posted?
Pretty sure one describes that scenario...
EDIT: You can also boot into TWRP and format your portable storage and that should fix it.
Click to expand...
Click to collapse
I went to re-read both the link as per your indication and perhaps I found the solution in the second link (located at the bottom of the page) I will report here what is written for convenience.
____________________________
In addition though, you might get the error that your SD card on your device storage is corrupted. If so follow these steps.
After you have partitioned the disk and while your SD card is corruped enter In the terminal the following:
$> adb shell sm list-volumes all
Which will list your volumes, for example:
private mounted null
public:179,1 mounted B5B1-140C
private:179,3 unmountable null
emulated mounted null
Then enter the following replacing 179,3 with whichever disk numbers you are given:
$> adb shell sm format private:179,3
$> adb shell sm mount private:179,3
Now your SD card in device storage should be properly mounted and your portable storage will still be there.
______________________________
Attached I have put what I see in adb with the command
adb shell sm list-volumes all
In my case as you can see it is a little different there are some voices in + and also a little different ... for example there are 2 voices one "unmonted" and one "unmountable" according to the explanation it should be the unmountable one but it is " public "and not" private "as in the example.
So in my specific case I also have to change the command to be given after and write "public" instead of "private" like this?
adb shell sm format public: 179.33
adb shell sm mount public: 179.33
As for the formatting you told me in TWRP you had to do it now with the partition already done I guess, but doing it from TWRP does not format the entire microsd by canceling the partition (as happens if you format it from the phone menu) but only formats the external partition?
Can you tell me the exact procedure to do from TWRP because I tried but can't find how to format it ...
I tried to go to Advanced-partition SD, here it makes me select only Sd card lexar 21017Mb (which would be the internal partition), then there is Microsd card (0MB) which is not selectable because it is the one that says damaged ... not i know if this is the correct path..can you let me know please? Thanks always
fabulas_ said:
I went to re-read both the link as per your indication and perhaps I found the solution in the second link (located at the bottom of the page) I will report here what is written for convenience.
____________________________
In addition though, you might get the error that your SD card on your device storage is corrupted. If so follow these steps.
After you have partitioned the disk and while your SD card is corruped enter In the terminal the following:
$> adb shell sm list-volumes all
Which will list your volumes, for example:
private mounted null
public:179,1 mounted B5B1-140C
private:179,3 unmountable null
emulated mounted null
Then enter the following replacing 179,3 with whichever disk numbers you are given:
$> adb shell sm format private:179,3
$> adb shell sm mount private:179,3
Now your SD card in device storage should be properly mounted and your portable storage will still be there.
______________________________
Attached I have put what I see in adb with the command
adb shell sm list-volumes all
In my case as you can see it is a little different there are some voices in + and also a little different ... for example there are 2 voices one "unmonted" and one "unmountable" according to the explanation it should be the unmountable one but it is " public "and not" private "as in the example.
So in my specific case I also have to change the command to be given after and write "public" instead of "private" like this?
adb shell sm format public: 179.33
adb shell sm mount public: 179.33
As for the formatting you told me in TWRP you had to do it now with the partition already done I guess, but doing it from TWRP does not format the entire microsd by canceling the partition (as happens if you format it from the phone menu) but only formats the external partition?
Can you tell me the exact procedure to do from TWRP because I tried but can't find how to format it ...
I tried to go to Advanced-partition SD, here it makes me select only Sd card lexar 21017Mb (which would be the internal partition), then there is Microsd card (0MB) which is not selectable because it is the one that says damaged ... not i know if this is the correct path..can you let me know please? Thanks always
Click to expand...
Click to collapse
You seem to have figured out the command so you should just try it. You seem to want confirmation before you do any steps, and I'm not really here to hand-hold - you're going to have to just try these things and see what happens. I've found that's the best way to learn.
In TWRP, to format the portable partition on the SD card just Wipe -> check "Micro SD card" -> swipe to complete action.
Hopefully one of those methods will resolve your corrupted issue and you can use the card. I don't plan on replying here any further so please don't ask me anymore questions or mention me. Thanks.