Related
This tutorial will show you how to Upgrade / Change to a new SD card having an EXT2/3 partition. This tutorial is for Windows platform only and assumes that you are comfortable with doing some basic functions with your phone.
Disclaimer:
I take no responsibility for any damage (if it occurs) to your phone by following the the steps mentioned below. Use it at your own risk!!! You have been warned.
Prerequisites:
1. HTC Desire - Rooted
2. Clockworkmod recovery installed on your phone (my version is 3.0.0.5?)
3. Nandroid
4. Download and Install - Freeware: Easeus Partition Manager
5. A windows PC and HTC desire data cable.
Steps:
1. Create a full nandroid back up for your current ROM from Clockworkmod Recovery screen. [No Mybackup or Titanium Backup - Nandroid is Required]
Boot phone into Clockworkmod recovery -> backup/restore -> backup (takes a few minutes) will make a complete backup of you rom, stored in clockwordmod folder of your SD-card (folder named with date and time) [Thanks Papedo]
2. Connect your HTC desire to your PC via your data cable and save the whole "Clockworkmod" folder from your SD card to a folder in your PC. Save any other files which you may want to in that folder.
3. Safely Eject the SD card.
4. Turn off your phone.
5. Remove the Old SD Card and Insert the new one.
6. Boot phone into Clockworkmod recovery.
7. Now select the option - "Partitions Menu"
8. Select option - "mount USB storage"
9. Open Easeus Partition Manager.
10. Create two partitions on the SD *exactly* in this sequence (assuming you have a 16gb card - windows will show 14.98gb free):
a. Fat32 partition - Primary - 14gb
Method: Right click unallocated space on your SD card and select "Create" -
A create partition dialog will pop up - use the following values:
Create As: Primary
File System: Fat32
Partition Size: 13980
Hit: OK
b. Ext2/3 partition - Primary - 1 gb
Method: Right click unallocated space on your SD card and select "Create" -
A "Create Partition" dialog will pop up - use the following values:
Create As: Primary
File System: Ext2 or 3
Partition Size: 1000
Hit: OK
11. Your SD card partitions should look like this (see DISK 3):
{
"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"
}
11. Hit Apply button which will appear on the left hand side.
11. Go to Windows Explorer to ensure that you can see and access the newly created FAT32 partition.
12. Once you are satisfied with the FAT32 partition go and copy paste all the files and folders from the backup of your OLD SD Card made on your PC to the new SD Card.
13. Once this process if finished reboot the phone into recovery.
14. Go to Nandroid - Select Restore. Choose the Backup you want to restore.
15. Nandroid will take sometime to check MD5 sum of the recovery image, be patient. If everything is OK, Nandroid will start restoring the image and will start copying files.
16. Once finished it will display "Restore Complete". Press the back button now, select "Reboot System Now".
Go Crazy!
Now you have a full functional new SD card with EXT 2 / 3 partition.
[Credits if you post this elsewhere]
CS
Similar tutorials:
Using other freeware:
MiniTool Partition Wizard - Credits: Kneros
Parted Magic - Credits: Svennetjee
Good work, this will surely help some people.
Sent from my HTC Desire using XDA App
b3ndik said:
Good work, this will surely help some people.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Thanks. Have a good day.
Hi celestialspring,
Nice explaining with details.. I have problem before kicking off.
i used unrevoked to root, have rom manager installed , clock work mod 2.5.0.7 i am using the latest leedroid rom.
How do i obtain a Nandroid back up to backup as u have required apart from titnanium and backup pro? I don't know how to get nandroid back up from. please advice. thanks a million.
Boot phone into Clockworkmod recovery -> backup/restore -> backup (takes a few minutes)
will make a complete backup of you rom, stored in clockwordmod folder of your SD-card (folder named with date and time)
I know that this is a Windows-only tutorial, and thanks for sharing.
However, when dealing with Android and its (advanced) aspects is always a good thing to have a Linux OS handy: in this case, having native access to the sdcard's ext partition, one can simply copy/paste its contents making the whole process a matter of seconds. Moreover, the gparted utility that ships with most Linux distributions can play the Easeus Partition Manager's role perfectly.
@ngel said:
I know that this is a Windows-only tutorial, and thanks for sharing.
However, when dealing with Android and its (advanced) aspects is always a good thing to have a Linux OS handy: in this case, having native access to the sdcard's ext partition, one can simply copy/paste its contents making the whole process a matter of seconds. Moreover, the gparted utility that ships with most Linux distributions can play the Easeus Partition Manager's role perfectly.
Click to expand...
Click to collapse
Personally, I wouldn't want to copy and paste the data within an ext partition. nandroid will do a better job of that i feel,
However, Gparted would definitely be my weapon of choice. In my professional experience, windows based partition managers have never been great at handling alien file systems
About the pratition softwares please also add information about GParted, Partition Wizard, etc.
Those are similar freewares just like the one posted.
EASEUS Partition Manager didn't do the trick for me, but Parted Magic did.
Wrote another tutorial myself: http://www.everythinghtcdesire.com/tutorials/how-to-partition-your-microsd-card-for-app-storage
Svennetjee said:
EASEUS Partition Manager didn't do the trick for me, but Parted Magic did.
Wrote another tutorial myself: http://www.everythinghtcdesire.com/tutorials/how-to-partition-your-microsd-card-for-app-storage
Click to expand...
Click to collapse
Easeus will work but you need to create the partitions exactly as mentioned in the tutorial. If you create the EXT3 partition before the FAT32 partition it won't work. I learnt it by trial and error
Perhaps the biggest advantage of using Easues is that one does not need to burn a CD and then boot from it. I hate booting off my current work envoirnment just to partition an sd card.
This was the quickest and easiest way I found which worked for me. People who are more tech savvy can use Gparted or whatever.
aaa said:
About the pratition softwares please also add information about GParted, Partition Wizard, etc.
Those are similar freewares just like the one posted.
Click to expand...
Click to collapse
See reply above.
No need to reserve the last portion for linux swap? Just only two partition (FAT32 & EXT3)?
Great .... ! But i have one question...2GB for android .. is it possible ? Or 1gb is really enough ?
yuna75 said:
No need to reserve the last portion for linux swap? Just only two partition (FAT32 & EXT3)?
Click to expand...
Click to collapse
I am not quallified to answer that question. But in my day-to-day workings, I have no troubles after formatting the card as above.
ta. cs
Oggy972 said:
Great .... ! But i have one question...2GB for android .. is it possible ? Or 1gb is really enough ?
Click to expand...
Click to collapse
2gb. I don't see any issues.
1 gb -- Yes, it is possible only if you want to run older versions of many ROMs. If you intend to run DHD ports then I don't recommened it.
aaa said:
About the pratition softwares please also add information about GParted, Partition Wizard, etc.
Those are similar freewares just like the one posted.
Click to expand...
Click to collapse
Information added about two new freeware software. See updated original post. ta.
celestialspring said:
Easeus will work but you need to create the partitions exactly as mentioned in the tutorial. If you create the EXT3 partition before the FAT32 partition it won't work. I learnt it by trial and error
Perhaps the biggest advantage of using Easues is that one does not need to burn a CD and then boot from it. I hate booting off my current work envoirnment just to partition an sd card.
This was the quickest and easiest way I found which worked for me. People who are more tech savvy can use Gparted or whatever.
Click to expand...
Click to collapse
Afternoon all.
My 4GB card is full. I'm running a rooted Desire, S-off with Amon-Ra recovery. My PC is running Linux. I want to swap to a bigger card. I'm fine with partioning the new card with G-Parted, and also cool with copying the data between FAT32 partitions.
I'm not so sure I know what I'm doing with the ext4 partition. Will Amon-Ra Nandroid backup and restore do the whole contents of the ext4 partition? So does the process go a bit like this:
nandroid backup
copy FAT32 partition to PC
partition new card
copy FAT 32 data from PC to new card
take the old card out and put the new one in
boot into recovery
nandroid restore
reboot
Have i got that right, or have I misunderstood something?
That's correct.
Sent from my A7710 using Tapatalk 2
Trogladyte said:
Afternoon all.
My 4GB card is full. I'm running a rooted Desire, S-off with Amon-Ra recovery. My PC is running Linux. I want to swap to a bigger card. I'm fine with partioning the new card with G-Parted, and also cool with copying the data between FAT32 partitions.
I'm not so sure I know what I'm doing with the ext4 partition. Will Amon-Ra Nandroid backup and restore do the whole contents of the ext4 partition? So does the process go a bit like this:
nandroid backup
copy FAT32 partition to PC
partition new card
copy FAT 32 data from PC to new card
take the old card out and put the new one in
boot into recovery
nandroid restore
reboot
Have i got that right, or have I misunderstood something?
Click to expand...
Click to collapse
Just use 4ext recovery, waay better in every way and much more features. U can partition ur new sdard with it to (guide in my sig)
Using 4ext recovery to backup, simply go to
Backup/restore
Backup
Then copy "clockworkmod" folder to pc
Then once uv partitioned ur new sdcard, copy the clockworkmod folder back to new sdcard and in recovery go to
Backup/restore
Restore
Job done
CWM doesn't play with this phone, so I'm using Amon Ra
I just tried the process with Gparted as set out above, and it doesn't seem to have worked. Lots of apps are missing, I don't have the ext4 partition available, and no account details are loaded.
---------- Post added at 03:49 PM ---------- Previous post was at 03:45 PM ----------
And I also can't boot into recovery - it just boots normally
---------- Post added at 04:04 PM ---------- Previous post was at 03:49 PM ----------
Took the battery out, and put the old SD card back in and miracualously I can now get into recovery. Did a Nand resore but the screen is now flashing white every few seconds. What the hell?
I've done some searching and could not find an answer to this issue that I could understand.
My phone is running Dexter's Froyo v1.3. I was having the issue where Milestone Overlock would not autoload at boot (ie settings were reset every reboot), and wanted to create an ext3 partition to use Link2SD.
I downloaded MiniTool Partition Wizard and used it to create a ~512MB ext3 partition on the phone, as a logical partition. Didn't do anything else as far as setting boot partitions (thought it would keep the old settings, not sure if that's causing the issue).
Also, I installed the update from Mioze7Ae, by copying the .zip to the OpenRecovery/updates folder on my SD, doing a recovery boot, and applying the update. When the update was applied it said successful, but there was a message before this line saying:
E: Can't mount /dev/block/mmcblk0p2
(Invalid Argument)
Install from sdcard complete.
I think this is part of the issue, but I don't really know what I'm doing. After this I rebooted the phone, and got a notification Removed SD card, and when I connect to PC no drive is shown (just Removable Disk G:, and nothing in shown in MiniTool Partition Wizard.
I'm guessing the issue was caused my me not formating the SD properly. Can anyone help out? I would like to avoid loading Dexter's rom from scratch if possible, to keep my data/apps, but am willing if that's the only way.
Sorry for the long post and if this question's been answered before, as I said I did do quite a bit of searching and couldn't find any comprehensive solution. Thanks
berlin85 said:
I've done some searching and could not find an answer to this issue that I could understand.
My phone is running Dexter's Froyo v1.3. I was having the issue where Milestone Overlock would not autoload at boot (ie settings were reset every reboot), and wanted to create an ext3 partition to use Link2SD.
I downloaded MiniTool Partition Wizard and used it to create a ~512MB ext3 partition on the phone, as a logical partition. Didn't do anything else as far as setting boot partitions (thought it would keep the old settings, not sure if that's causing the issue).
Click to expand...
Click to collapse
From what I've read, I'm pretty sure you have to use primary partitions and logical's don't work on the phone. You also have to set the boot flag (a.k.a. active partition) on the fat partition. Based on what you've written (which was very good by the way, the detail was helpful), I don't think you have to reinstall the ROMs. I think you just need to repartition/format your card properly.
This is probably an even dumber question, but I'm not sure how to repartition/format the card at this point. Nothing is showing up in Windows, just Removable Disk with size shown of 0 bytes, and when I open MiniTool Partition Wizard, all I see is my PC drives, nothing for the SD.
I'm connecting with the SD in my phone if that makes a difference, I don't have a reader on my pc.
berlin85 said:
This is probably an even dumber question, but I'm not sure how to repartition/format the card at this point. Nothing is showing up in Windows, just Removable Disk with size shown of 0 bytes, and when I open MiniTool Partition Wizard, all I see is my PC drives, nothing for the SD.
I'm connecting with the SD in my phone if that makes a difference, I don't have a reader on my pc.
Click to expand...
Click to collapse
Maybe try a linux boot CD. Ultimately, you may have use an adapter and go directly to the PC, though. It could be that the phone doesn't understand the partition table with the logical partitions so it can't export it anymore.
The phone's software (even recovery) doesn't expect that partitions can change while it is booted. For example, (you don't have one working but if you did) when you export the partitions for USB access, the sd-ext partition is both *not* unmounted and also simultaneously exported as a raw device. This can cause all sorts of filesystem corruption on the ext partition because of kernel caching on the desktop and in the phone.
Yay, used a comp at school with a microSD reader, repartitioned the ext3 making it primary rather than logical... seems to be working fine
easy solution after all! thanks for the help, really appreciate it
berlin85 said:
I've done some searching and could not find an answer to this issue that I could understand.
My phone is running Dexter's Froyo v1.3. I was having the issue where Milestone Overlock would not autoload at boot (ie settings were reset every reboot), and wanted to create an ext3 partition to use Link2SD.
I downloaded MiniTool Partition Wizard and used it to create a ~512MB ext3 partition on the phone, as a logical partition. Didn't do anything else as far as setting boot partitions (thought it would keep the old settings, not sure if that's causing the issue).
Also, I installed the update from Mioze7Ae, by copying the .zip to the OpenRecovery/updates folder on my SD, doing a recovery boot, and applying the update. When the update was applied it said successful, but there was a message before this line saying:
E: Can't mount /dev/block/mmcblk0p2
(Invalid Argument)
Install from sdcard complete.
I think this is part of the issue, but I don't really know what I'm doing. After this I rebooted the phone, and got a notification Removed SD card, and when I connect to PC no drive is shown (just Removable Disk G:, and nothing in shown in MiniTool Partition Wizard.
I'm guessing the issue was caused my me not formating the SD properly. Can anyone help out? I would like to avoid loading Dexter's rom from scratch if possible, to keep my data/apps, but am willing if that's the only way.
Sorry for the long post and if this question's been answered before, as I said I did do quite a bit of searching and couldn't find any comprehensive solution. Thanks
Click to expand...
Click to collapse
Did you try to format sd card with your phone in sd card and memory setting and then to create again ext3 partition with MiniTool Partition Wizard ?
Be sure to save data in your card first.
Mine is a galaxy SII, but I'm facing the same problem. I've formatted my microSD to EXT3 via MiniTool Partition but phone does not recognize it.
It says it's damaged and asks if I want to format it, after formatting thru the phone it returns to FAT32 and works perfectly again.
I've read more than 20 threads among several forums but I'm still not able to fix it.
Can you guys help me?
{
"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"
}
Did you create a second partition as ext3? AFAIK the first partition must be FAT (and marked bootable). Maybe you got that backwards?
Are you trying to partition the internal SD or the external. Samsung already has the internal partitioned into one Fat and another for your apps and cache. That is why your phone specs show 16gb internal but you only really have 14gb to put music, pix,...on. 2gb are already allotted for apps and cache. You can and should only partition the external one. My question is why are you trying to do this on an SGSII when it is not needed. No SGSII rom needs to have a partition and any Voodoo kernel will convert your system, data, cache and DB.data files to Ext4 anyways. Seems needless.
Mioze7Ae said:
Did you create a second partition as ext3? AFAIK the first partition must be FAT (and marked bootable). Maybe you got that backwards?
Click to expand...
Click to collapse
Had no success doing this, it shows the same information saying that "SD card is damaged". I really don't know what to do to make this work.
---------- Post added at 09:26 PM ---------- Previous post was at 09:24 PM ----------
Woodrube said:
Are you trying to partition the internal SD or the external. Samsung already has the internal partitioned into one Fat and another for your apps and cache. That is why your phone specs show 16gb internal but you only really have 14gb to put music, pix,...on. 2gb are already allotted for apps and cache. You can and should only partition the external one. My question is why are you trying to do this on an SGSII when it is not needed. No SGSII rom needs to have a partition and any Voodoo kernel will convert your system, data, cache and DB.data files to Ext4 anyways. Seems needless.
Click to expand...
Click to collapse
I'm trying the external SD. It's a ADATA 32GB microSD.
The reason I want to do this is to be able to copy files over 4GB.
I rooted my TF this morning following androidroot.mobi instructions. Initially I installed the V5 blob and everything worked except bluetooth. I could have sworn I had the updated firmware but when I checked after the rooting process I found that I have 8.2.2.6.1-20110325. So I decided to update to the official 8.2.3.9 version.
I followed ASUS' instructions and got the triangle to notify me of the update. When the TF rebooted I got into CWM recovery and didn't know what to do so I simply rebooted again. Everything was just like before. I decided to try it again but I can't access CWM recovery anymore and the triangle doesn't show up when I insert the SD card (it works on another TF). I can't install CWM recovery from the ROM Manager app either since the TF is not listed.
Then I installed the blob V4 to at least regain BT functionality and it worked. However, I still can't access recovery. Does anyone have any suggestion?
Thanks!!!
EDIT: I can enter CWM recovery now but I can't mount the SD card. The internal memory also seems inaccessible
{
"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"
}
if you have clockwork recovery flashed, to access it... turn off the tf... hold the volume down button and power on... a script should show up on the top left... hit the volume up button and clockwork should boot
hope that helps
That got me into recovery but I can't access the µSD card Copied the Prime! ROM to the SDCARD folder in the eMMC and trying it this way.
EDIT: No luck... still saying "Can't mount /sdcard" Any other suggestions?
Solution found!
The solution was to use a different SD card. There have been similar reports in the Development Threads. So for people coming here through the search function: Try a different SD card or use another Android device to format the one that's not working and try again. Don't give up
funnycreature said:
The solution was to use a different SD card. There have been similar reports in the Development Threads. So for people coming here through the search function: Try a different SD card or use another Android device to format the one that's not working and try again. Don't give up
Click to expand...
Click to collapse
So you're able to access the sdcard from the doc? I can get the microsd card no problem and when I'm booted I can see the sdcard in the mmc/sd/sdhc slot but in cwm I can never see the mmc/sd/sdhc card/slot. Is there a different version of cwm I should be running? currently I have: v3.1.0.1 (solarnz-R3-230511-1902)
no, cmw only sees the microsd card. that's prolly what he meant
Im not able to see my micro from cwm either. Tried 2 sd cards with no luck. Am i missing a step?
Sent from my Transformer TF101 using XDA Premium App
Are either of you using an NTFS-formatted microSD, by chance? Although Prime supports NTFS on the removable storage, CWM will not mount the card if it's not FAT32.
Underwater Mike said:
Are either of you using an NTFS-formatted microSD, by chance? Although Prime supports NTFS on the removable storage, CWM will not mount the card if it's not FAT32.
Click to expand...
Click to collapse
I am not. Some info, I bought this already rooted with prime 1.7. I've spent time with my rooted nookcolor and htc incredible, but this seems to run a bit differently, expected since it is honeycomb. None of my apps read my micro sd, they use the internal memory, I guess its called an internal sd card. But it does detect it as a external storage. I don't know if that why it wont read it, since clock work goes off the sd card, maybe the path isn't right since it labels it different?
I tried two cards and reformatted it in ubuntu and it said it should be compatible with any FAT format. Am I missing something? Once recovery is set up does it work out of the box, or is there a step I'm missing?
I do boot to recovery from holding down the power button, should I buy the app that does it?
Thanks!
actorman46 said:
I do boot to recovery from holding down the power button, should I buy the app that does it?
Thanks!
Click to expand...
Click to collapse
No need to buy the app, your problems is not booting into recovry. It's teh same recovery no matter which method
you use to get there.
Try formatting with sdformatter program on pc.
Sent from my Transformer TF101 using Tapatalk
I've never had a problem with cwm seeing any micro-sd cards, but I can't get it to see the doc sd card slot. Another odd thing ... when I bought my Transformer I bought it with a doc/kb all in one package. A colleague purchased the tablet and then later purchased a doc/kb separately. They are the exact same part number the only 2 differences we can tell so far are 1) I have green mark up or hi ascii marks on my keys and 2) in cwm he can actually use the arrow keys on his kb and I can't
Another thing I found odd ... I flashed a cwm from a linux script and wanted to update to cwm_recovery-3201_roach-tf101-r1.zip so I did the flash from in cwm however my version still shows v3.1.0.1 (solarnz-R3-230511-1902) .... has anyone successfully flashed 3201? and if so how did you do it because I can't get it to work flashing from cwm although it says it flashed fine
Thanks guys!
Okay, well then it has to be a formatting issue. This weekend I'll try it on different computers / programs and report back if one works.
And I'm able to use the doc in recovery. It is wierd that some work and some don't.
Sent from my Transformer TF101 using xda premium
[UPDATE]
actorman46 said:
Okay, well then it has to be a formatting issue. This weekend I'll try it on different computers / programs and report back if one works.
And I'm able to use the doc in recovery. It is wierd that some work and some don't.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
With version 3.2.0.1 I can use my doc (arrow keys) but I still can not see the sdcard in the doc. Th only mounts in "Mounts and Storage" are the default ones off of root "/" and /sdcard is typically internal while running and the micro-sd while in recovery. I'm wondering if there's a different way to mount the sdcard in the doc. I'm going to poke around a bit
[EDIT] Ok so I checked the devices through adb and realized that the card slot in the doc shows up as sda/sda1. I used adb to mount /dev/block/sdb1 to /sdcard and am currently running a nandroid \o/
SpEnTBoY said:
With version 3.2.0.1 I can use my doc (arrow keys) but I still can not see the sdcard in the doc. Th only mounts in "Mounts and Storage" are the default ones off of root "/" and /sdcard is typically internal while running and the micro-sd while in recovery. I'm wondering if there's a different way to mount the sdcard in the doc. I'm going to poke around a bit
[EDIT] Ok so I checked the devices through adb and realized that the card slot in the doc shows up as sda/sda1. I used adb to mount /dev/block/sdb1 to /sdcard and am currently running a nandroid \o/
Click to expand...
Click to collapse
See, thats what I was thinking the problem was. Do you do those adb comands while in recovery?
Sent from my Transformer TF101 using xda premium
actorman46 said:
See, thats what I was thinking the problem was. Do you do those adb comands while in recovery?
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
I could write something more definitive and in shell but basically I looked in /dev/block for new devices when I plugged the card in ... the "device" is /dev/block/sda but the formatted partition was just /dev/block/sda1
What could be done is a action that shows all non mtdblock devices ion dev block and list them IE:
Code:
for i in `ls /dev/block | grep -e mtd`; do echo $i; done
I'll leave the last one in so people can make fun of me
This is overkill and I haven't tested it on the actual tablet, but it works on my laptop. All I did was change the path to the interpreter and it assumes you'd have busybox installed. Not sure what the shell is in cwm recovery either. The only required "command" is the mount command from adb listed last
Code:
#!/system/bin/sh
dev_list=`ls /dev/block | egrep "sda|sdb"`;
for i in ${dev_list}; do
if [ $i = 'sda1' ]; then
dev=$i;
fi
done
echo "Device /dev/block/$dev found in doc. Would you like to mount? [y/n]";
read response;
if [ "$response" = "y" ]; then
echo "Mounting /dev/block/$dev to /sdcard" && echo "mount /dev/block/$dev /sdcard";
else
echo "Exiting";
exit 0;
fi
that can be done a lot better but just as a one off ... anyway to mount it simply verify /sdcard does "not" show in the mounted filesystems, then:
Code:
mount /dev/block/sda1 /sdcard
There's literally hundreds of ways of doing this and way more efficient ways as well but whatever
ok, that sounds great, but could you be more "noob-friendly"? My recovery can't mount my sdcard :x
I hate to bump an old thread, but it seems as if "Cannot mount SD card in CWM on Transformer Prime" is an unresolved issue.
My SD card was formatted on another android device, it is FAT32, and I am not adb savvy.
I would like to be able to mount the SD in CWM in case I ever have the need. Any non adb suggestions?
Thanks!
Your recovery Must support it, since you have a Prime I'd head over to prime development here: http://forum.xda-developers.com/forumdisplay.php?f=1414
Search for Recovery or CWM or the like.
See if you find a Recovery that specifically states support for External-SD (/removable/MicroSD)
Thanks, Thing, I will check over there.
Via Tapatalk 2 on LG SPECTRUM Broken Out 3.0
How to solve on HTC flyer
SpEnTBoY said:
With version 3.2.0.1 I can use my doc (arrow keys) but I still can not see the sdcard in the doc. Th only mounts in "Mounts and Storage" are the default ones off of root "/" and /sdcard is typically internal while running and the micro-sd while in recovery. I'm wondering if there's a different way to mount the sdcard in the doc. I'm going to poke around a bit
[EDIT] Ok so I checked the devices through adb and realized that the card slot in the doc shows up as sda/sda1. I used adb to mount /dev/block/sdb1 to /sdcard and am currently running a nandroid \o/
Click to expand...
Click to collapse
I have a HTC flyer upgraded to Honey Comb. I got unlocked from the HTC dev site. CWM recovery is installed. But not able to flash the superuser zip file from SD card. In fact not even able to back up since SD card wont mount. The HTC flyer does not have SD card slot. it is only the internal SD card. ES file explorer shows a SD card folder in /mnt/sdcard. But CWM recovery wont mount it. Im just at amatuer at all this. So it would be great if you could show me what commands I can use with adb to mount the SD card in recovery.
Any help is greatly appreciated. All other related topics only talk about external SD cards so I'm a little lost.
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.
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.