Related
Hi everyone, looking for a little guidance.
Phone: Android G1 (Rogers Canada Dream) running Cyanogen 4.2.15.1, been running fine since 4.2.6.1
Removed SD card while it was on and it rebooted... when it restarted it showed no applications and said the SD card was inaccessible and required a format. After rebooting a few times with no success I bit the bullet and formatted it... all apps are gone except for the ones that are on that image for Cyanogen. I have no market app to download new apps and when I plug it into my PC and mount it I don't see it show up as a drive like it did so I have no way to get the apps back on.
Has anyone had this happen before? Phone still works but I need to get it back to a state where I can get access to the SD and install the market... Any suggestions appreciated!!
There is a thread on the HERO section of Modaco site called "no adb, no sd". I think the 1st post on the last page MIGHT help. There are adb commands you can run to see if the phone has randomly stopped accessing the SD. Worth a shot.
PM me if you have trouble finding the thread n I'll have a look when I'm at my laptop.
Sent from my HTC Hero using XDA App
I misunderstood I think.
So it is now showing an sd present? Have you tried formatting in a pc?
Tried reboot without the sd in, then insert once fully booted again?
Sent from my HTC Hero using XDA App
I remove the SD Card, formatted it in my PC put it back in the phone and I can store pics and vids on it and access them but cant see or access it from the PC when in the phone. I also have no file browser so I cant install any apps or even access the market icon is gone).
D RoiD said:
Hi there! I had posted on the forum with the G1 issue where my SD card seemed to have died.
http://forum.xda-developers.com/showthread.php?t=738105
I have since removed the SD card and reformatted it, I can store pics and vids and replay them so the card is fine. I tried letting it boot up then adding the SD card when booted, that caused it to reboot, same issue...
Not having access to the card, I cant install any apps or browse the SD to install from there... really sucks
I'd be willing to blow it away and restart too and install CyanogenMod-5.0.8 but I need some guidance.
Click to expand...
Click to collapse
I got your message pal....
Ok,.... So pictures and videos taken with your phone camera DO save to your SD?.... and you CAN access them on your phone OR if you put your SD into your PC/Lappy?... But not when trying to "mount SD"?
Or have I got that completely wrong?.... Did you put pics&vids onto it through your PC, and thats the only access you get to it?
ddotpatel said:
I got your message pal....
Ok,.... So pictures and videos taken with your phone camera DO save to your SD?.... and you CAN access them on your phone OR if you put your SD into your PC/Lappy?... But not when trying to "mount SD"?
Or have I got that completely wrong?.... Did you put pics&vids onto it through your PC, and thats the only access you get to it?
Click to expand...
Click to collapse
Pics taken DO save to me SD. I Can access them from a PC is I remove the SD and put it in the PC. Not when I plug the phone in via USB then tell it to mount.
I just did a low level format, same issue.
UPDATE: Just tried the Android System Recovery and Toggle USB-MS and it shows on my laptop now! Going to try the recovery backup now.
aha,... so its just a mounting issue, not that the hardware has turned itself off.
Once when using an older ROM (maybe Villain 10?) we had this same issue, not able to mount SD,... going into Settings --> Connect to PC --> and turning off Notify/ask me solved the problem.
I just partitionned it using:
parted /dev/block/mmcblk0
print (to verfiy we know what size card we are dealing with, the details should be straight forward)
rm 1
rm 2
mkpartfs primary fat32 0 7500
mkpartfs primary ext2 7500 7948
quit
upgrade_fs
reboot recovery
Then put CyanogenMod-5 For Dream/Magic on the SD and renamed it update.zip
I'm in Android System recovery now and just did a nandroid backup.
I should be able to WIPE then FLASH UPDATE IMAGE right?
D RoiD said:
I just partitionned it using:
parted /dev/block/mmcblk0
print (to verfiy we know what size card we are dealing with, the details should be straight forward)
rm 1
rm 2
mkpartfs primary fat32 0 7500
mkpartfs primary ext2 7500 7948
quit
upgrade_fs
reboot recovery
Then put CyanogenMod-5 For Dream/Magic on the SD and renamed it update.zip
I'm in Android System recovery now and just did a nandroid backup.
I should be able to WIPE then FLASH UPDATE IMAGE right?
Click to expand...
Click to collapse
Yes, if you have the ROM image on the SD Card (FAT32 partition), you can go flash the image.
akapoor said:
Yes, if you have the ROM image on the SD Card (FAT32 partition), you can go flash the image.
Click to expand...
Click to collapse
Stupid question but when I wipe will it delete my contacts as well?
I assume yes but...
D RoiD said:
Stupid question but when I wipe will it delete my contacts as well?
I assume yes but...
Click to expand...
Click to collapse
If your contacts are saved in the phone's memory, then yes. Any settings, apps, configurations that are stored on the phone will all be gone.
A wipe pretty much gives you the factory settings. (As if you just bought the phone) So you'll have to re-signin into your Google Account and let the Contacts Sync, etc..
EDIT: Depending on what you are flashing (flashing and wiping are two different things), you may not even need to wipe.
Hmmm I tried flash update image and got:
E: Cant open /sdcard/update.zip (No such file or directory)
When I mount it in system recovery I see the LOST.DIR and update.zip
D RoiD said:
Hmmm I tried flash update image and got:
E: Cant open /sdcard/update.zip (No such file or directory)
When I mount it in system recovery I see the LOST.DIR and update.zip
Click to expand...
Click to collapse
Try this:
-Confirm the Image-
1) Make sure you have the full image you are going to flash. (Compare MD5 Hashes and/or just redownload the image)
2) Make sure the image you are flashing is the in the ROOT directory of your SDCard. In other words, it shouldn't be in any folder.
-Flash the Image-
1) When in Recovery, choose to flash an image.
2) Depending on what recovery you have, you may have to select/find the Image you want to flash.
3) Flash the image
-Wipe (Depends)-
1) If you are coming from a different ROM base (ie anything -> cyan), you'll want to wipe.
2) After the phone successfully flashes the image, wipe the phone.
Reboot.
Let me know how it goes.
I pulled the new image from: Latest version: 5.0.8-DS - 06/19/2010
Download: http://cyanogen-upda...8-DS-signed.zip
but it says no such file or DIR... weird...
The only partition I can see on my PC to put it on is the main partition...
I just downloaded the file and renamed it update.zip
D RoiD said:
I pulled the new image from: Latest version: 5.0.8-DS - 06/19/2010
Download: http://cyanogen-upda...8-DS-signed.zip
but it says no such file or DIR... weird...
The only partition I can see on my PC to put it on is the main partition...
I just downloaded the file and renamed it update.zip
Click to expand...
Click to collapse
I just realized the main reason that you posted this topic. From what I am assuming, either:
a) Your SD Card reader is dead
b) The software isn't recognizing the SD Card reader.
Best bet at this point is to setup ADB (ADB For Dummies) and flash the image from your computer. It can get a slight bit complicated, but just slowly go through each step for installing ADB.
Once ADB is set up, you can flash the image from the computer.
akapoor said:
I just realized the main reason that you posted this topic. From what I am assuming, either:
a) Your SD Card reader is dead
b) The software isn't recognizing the SD Card reader.
Best bet at this point is to setup ADB (ADB For Dummies) and flash the image from your computer. It can get a slight bit complicated, but just slowly go through each step for installing ADB.
Once ADB is set up, you can flash the image from the computer.
Click to expand...
Click to collapse
The SD card reader in my phone? It has to work if I can read an write to it ( tested photos and videos) and in recovery I was able to make a backup.
If its the software I need to flash it then right? ADB does make me nervous as I only used it once... I just tried using the terminal emulator on the phone to flash a recovery image I had made while back:
cd /sdcard
flash_image recovery /sdcard/recovery-backup.img
and got the message "error writing recovery: Permission denied"
D RoiD said:
If its the software I need to flash it then right? ADB does make me nervous as I only used it once... I just tried using the terminal emulator on the phone to flash a recovery image I had made while back:
cd /sdcard
flash_image recovery /sdcard/recovery-backup.img
and got the message "error writing recovery: Permission denied"
Click to expand...
Click to collapse
If you can view the pictures that you saved on the SD card from the phone, then both the software and hardware are functioning correctly.
Regarding the permission denied:
1) What happens if you "su - " in terminal?
2) First try one(1) ^ and then try to reinstate the permissions. (In recovery, go to console and type : fix_permissions)
Not sure otherwise.
akapoor said:
If you can view the pictures that you saved on the SD card from the phone, then both the software and hardware are functioning correctly.
Regarding the permission denied:
1) What happens if you "su - " in terminal?
2) First try one(1) ^ and then try to reinstate the permissions. (In recovery, go to console and type : fix_permissions)
Not sure otherwise.
Click to expand...
Click to collapse
Ok I did a wipe and now I see the SD when mounted on the PC with the phone on.
I have my market icon back so I can reinstall my crap.
I'll leave it as is for a bit but appreciate everyones input!!!
Everyone,
I've written this a bunch of times but and putting it in
it's own thread so folks can read and use it.
Memory and Storage:
/sdcard -- internal memory of the tablet
/sdcard2 -- microSD card in the external slot
/usbdisk -- USB key slot
Stock Recovery Info:
Main method: Put your recovery folder and update.zip on /sdcard, turn off the tablet, the press power and volume + to initiate standard recovery.
Second method: Put your recovery folder and update.zip on a microSD card. Edit the command file in the recovery folder with Notepad to change the location from /sdcard to /sdcard2 and save it with the name "command" (NO
.txt or other file extension). Then boot recovery with power/volume + and the OS will use the sdcard (assuming you don't have a live recovery/update.zip file in /sdcard).
Third method: If you can boot recovery to CWM but can't get your ROM to work, go in recovery to the mount menu and go down to the mount USB memory option and choose it. Then plug your connector cable from the miniUSB port to your PC. When you plug into your PC an Explorer window should open and you should have a drive letter representing the G-Tablet (it's G: on mine) on your menu. You now can select that letter and you have access to your tablet memory (/sdcard). I've even had a time or two when not a single file showed!!! I added update.zip and recovery and loaded
a ROM!
The tablet boot process apparently checks /SDCARD. If it doesn't find a recovery file there it does the same check if you have a miniSD external card installed. The large USB slot is not useable for booting or recovery so far as I have determined or read.
I hope this helps you.
Rev
EDIT: I didn't put one fact in here about recovery that everyone should know. When you run a recovery operation, the system deletes the command file so you can't accidentally do it again. If you have to run a recovery or
attempt to load something again, make sure you have a command file in the recovery folder with the correct command in it!!! Sorry I omitted this first time around.
Placeholder
Placeholder
Hope everybody who needs this has seen it. I won't kick it up again.
Rev
Can you also add information about partitioning of /sdcard and why would one need it?
Is there another "hidden" flash memory available for firmware or all mods and custom ROMs go into /sdcard only?
Thanks so much, I thought I'm dead cuz I wiped out everything.
This may have been asked before, but how does one perform a full data wipe w/o using CWM? Thanks.
HackaMathecian said:
This may have been asked before, but how does one perform a full data wipe w/o using CWM? Thanks.
Click to expand...
Click to collapse
You need to use nvflash (nvidia tegra SoC flashing utility). There are alot of posts about it. Do be carefull if you go this route, as even though you will not damage your tablet, it may be difficult to put it back to a bootable state if you don't do it properly.
thanks!
thanks great. simple and to the point. should help people that get confused. thanks again!
Vlad_z,
It has been my experience that when somebody gets boot loops, it often involves a
partition problem. Also, sometimes the G-Tablet does flaky things. I have one I
just shut down. Restarted it with boot looping and had to rebuild.
The three locations listed above are the three memory places you can store stuff
unless you find software that custom sets up something else.
Rev
Os Money:
http://forum.xda-developers.com/showthread.php?t=861950
This thread completely explains the NVFlash process.
Rev
That's kind of odd, my removable sd card ended up with the label ex-sd. Doesn't seem to be messing anything up though.
sixtofive,
I've never seen or heard of that with the stock ROM. Are you running a different ROM?
Some of them do change the directories.
Rev
So simply put, we should copy and backup the recovery folder and update.zip in /sdcard (or tablet storage) and when things get f'ed up, we move the recovery folder and update.zip back into the /sdcard?
Maybe it's just me, but I looked into the recovery that was already in the tablet and there's nothing in it; is that normal? If not, can anyone provide the back up recovery folder and update.zip just in case?
sam,
Recovery is simply a folder which holds a file named "command" in it. Command is a file
that has the command line in it with the command and parameters to "recover" or "load" files onto your G-Tablet.
Sometimes when your tablet gets messed up, you can still use recovery and are lucky. But sometimes the recovery partition gets damaged and then you have to look
for other ways to get in and fix things.
http://forum.xda-developers.com/showthread.php?t=1010943
Many of us keep telling people there is a lot to learn here -- and Android doesn't have
all the stuff built into it Windows does. Nor is Android known for it's great documentation!
If everyone would read all the stickies at the start of the forums, it would provide
probably 80% of everything they need to know.
Rev
If OP also put links to stock ROMs, that would be great
interesting...even though I don't have a microSD card in mine /sdcard2 seems to be a valid directory within "root explorer"
what partition and memory structure should I be seeing on my brand new g-tablet? any suggestion on "mount" and "df" output?
Question, which is the best method or quicker to backup before attempting other rom installs?
Deleting CWM
How would one delete CWM so that the tablet can be returned?
Got my gtablet last evening. Seems there is a lot to learn.
thanks butchconner...
Thanks all the people who are contributing at xda. You are doing a wonderful job. In fact I bought this device because of you ( I think Viewsonic owes you guys a lot. At least they avoided a big loss because of you. )
Two questions:
1) Is it recommended to flash back to stock before changing roms?
2) Is there a link to the stock Rom files that I am missing?
Thanks
Hello everyone, albeit I have a substantial experience with Samsung Galaxy and Sony (Ericsson) Xperia devices, I am new to the HTC line of devices in the Android universe.
:silly:
A colleague from my workplace has entrusted with me her HTC Explorer A310e, to eventually root the device and consequently flash a compatible custom firmware of my choice, if I so choose to.
I intend on discussing my queries related to the aforementioned device within this single thread, rather than create separate threads for multiple queries.
I am all set to root, unlock the bootloader and subsequently flash a custom recovery on to the device by following this tutorial, http://forum.xda-developers.com/showthread.php?t=1415223 by @jaggyjags.
After the said processes have been completed, I am aware it is imperative to perform a NANDroid backup via the custom recovery, which I would be able to save to the external SD (memory card).
:good:
My queries, after performing the required procedures are -
When is it required to partition the SD?
Is it the internal SD, or the external SD, or both that require(s) partitioning?
How do I partition the required SD? Please point me to an appropriate guide/tutorial.
I intend on using Titanium Backup to perform a backup of the device's contents. I reckon restoring system data such as Phonebook, Messages, Calendar, etcetera should not cause any issues, right?
Some of the device's Software Information is
Android version
2.3.5
HTC Sense version
3.5
Software number
1.31.720.3
Baseband version
10.35d.80.09H_1.11.82.17
Build number
1.31.720.3 CL214721 release-keys
Click to expand...
Click to collapse
I await your knowledgeable responses, and I thank you for your patience with my naivety!
YLNdroid said:
Hello everyone, albeit I have a substantial experience with Samsung Galaxy and Sony (Ericsson) Xperia devices, I am new to the HTC line of devices in the Android universe.
:silly:
A colleague from my workplace has entrusted with me her HTC Explorer A310e, to eventually root the device and consequently flash a compatible custom firmware of my choice, if I so choose to.
I intend on discussing my queries related to the aforementioned device within this single thread, rather than create separate threads for multiple queries.
I am all set to root, unlock the bootloader and subsequently flash a custom recovery on to the device by following this tutorial, http://forum.xda-developers.com/showthread.php?t=1415223 by @jaggyjags.
After the said processes have been completed, I am aware it is imperative to perform a NANDroid backup via the custom recovery, which I would be able to save to the external SD (memory card).
:good:
My queries, after performing the required procedures are -
When is it required to partition the SD?
Is it the internal SD, or the external SD, or both that require(s) partitioning?
How do I partition the required SD? Please point me to an appropriate guide/tutorial.
I intend on using Titanium Backup to perform a backup of the device's contents. I reckon restoring system data such as Phonebook, Messages, Calendar, etcetera should not cause any issues, right?
Some of the device's Software Information is
I await your knowledgeable responses, and I thank you for your patience with my naivety!
Click to expand...
Click to collapse
1. You need to partition your SD card if you want to expand your internal memory, or some ROMs cannot be flashed without SD partition because our PICO has a limited internal storage.
2. there is nothing like internal SD card in PICO. you need to partition your SD card(external).
3. you can partition your SD card by using mini tool partition wizard.
hit thanks if it helped :good:
Bootloader Unlock
Is it compulsory to unlock the bootloader via the HTC Dev portal, or can it be done through another alternative?
:fingers-crossed:
Understandably, since it is necessary to have the Google Android SDK installed, which package should I download - the ADT Bundle, or the SDK Tools Only from http://developer.android.com/sdk/index.html?
YLNdroid said:
Is it compulsory to unlock the bootloader via the HTC Dev portal, or can it be done through another alternative?
:fingers-crossed:
Understandably, since it is necessary to have the Google Android SDK installed, which package should I download - the ADT Bundle, or the SDK Tools Only from http://developer.android.com/sdk/index.html?
Click to expand...
Click to collapse
1. Its mandatory to unlock bootloader via HTC Dev portal because the identifier token will only be provided by that portal
2. I had Android SDK, HTC Sync, Java Runtime Environment(All Provided in HTC Dev portal) in my system for the unlocking process...
Hit like if it helped :good:
Bootloader Unlock
aashking said:
1. Its mandatory to unlock bootloader via HTC Dev portal because the identifier token will only be provided by that portal
2. I had Android SDK, HTC Sync, Java Runtime Environment(All Provided in HTC Dev portal) in my system for the unlocking process...
Hit like if it helped :good:
Click to expand...
Click to collapse
@aashking, thank you for informing me that the bootloader unlock process is mandatory via HTC Dev.
:good:
As for the Google Android SDK, which package would you suggest I download and consequently install - the ADT Bundle or the SDK Tools Only, available at http://developer.android.com/sdk/index.html?
Download the one Android SDK zip provided in HTC Dev portal, you need not install it, HTC sync should be installed to connect your phone and to read commands, and follow the procedure given in HTC Dev its the simplest one
Hit thanks if it helped :good:
Sent from my HTC Explorer A310e using xda premium
Bootloader Unlock
aashking said:
Download the one Android SDK zip provided in HTC Dev portal, you need not install it, HTC sync should be installed to connect your phone and to read commands, and follow the procedure given in HTC Dev its the simplest one
Click to expand...
Click to collapse
@aashking, I have already installed HTC Sync on my computer. I believe the Android SDK zip file link provided at HTC Dev, which you are referring to, is the one mentioned within the Unlocking Bootloader Instructions procedural guide, http://www.htcdev.com/bootloader/unlock-instructions, right?
:fingers-crossed:
Absolutely mate, good luck let's hear for success :good:
Hit thanks if it helped :good:
Sent from my HTC Explorer A310e using xda premium
Bootloader Unlock
aashking said:
Absolutely mate, good luck let's hear for success :good:
Click to expand...
Click to collapse
@aashking, the link provided at http://www.htcdev.com/bootloader/unlock-instructions, redirects to http://developer.android.com/sdk/index.html, and hence the confusion over the package to be downloaded!
:silly:
Go with "android-sdk_r23.0.2-windows.zip" hoping that you are in windows,
Hit thanks if it helped :good:
Sent from my HTC Explorer A310e using xda premium
Partitioning the SD card
Now that my colleague's Explorer A310e has an unlocked bootloader, a custom recovery and root access, I am very keen on flashing a custom firmware and am inclined towards MiniCM9, http://forum.xda-developers.com/showthread.php?t=2169776, whose thread author is @thewisenerd.
Considering the limited internal storage capacity of the HTC Explorer, I understand it is rhetorically imperative to partition the external memory card (read as external SD, or plainly, SD card), and before I proceed with flashing the aforementioned custom Ice Cream Sandwich AOSP firmware, I would like to know what methodology should I apply, keeping in mind my colleague's primary/initial storage concern is with respect to using WhatsApp Messenger, an instant messaging app that is fixed to the internal storage.
My colleague's device came bundled with a 2GB microSD memory card. But, I have strongly suggested her to get a higher capacity memory card, perhaps an 8GB one.
:silly:
As usual, I await your valuable responses.
YLNdroid said:
Now that my colleague's Explorer A310e has an unlocked bootloader, a custom recovery and root access, I am very keen on flashing a custom firmware and am inclined towards MiniCM9, http://forum.xda-developers.com/showthread.php?t=2169776, whose thread author is @thewisenerd.
Considering the limited internal storage capacity of the HTC Explorer, I understand it is rhetorically imperative to partition the external memory card (read as external SD, or plainly, SD card), and before I proceed with flashing the aforementioned custom Ice Cream Sandwich AOSP firmware, I would like to know what methodology should I apply, keeping in mind my colleague's primary/initial storage concern is with respect to using WhatsApp Messenger, an instant messaging app that is fixed to the internal storage.
My colleague's device came bundled with a 2GB microSD memory card. But, I have strongly suggested her to get a higher capacity memory card, perhaps an 8GB one.
:silly:
As usual, I await your valuable responses.
Click to expand...
Click to collapse
As to partitioning your SDCard, I am assuming your objective is to "expand" you internal memory using "memory increasing scripts". This isn't a complex deal (I've explained how these work here), and mostly just involves one partition for reverse mounting the userdata (/data) partition.
You do not need to make two partitions, one would suffice. Also, you can make this partition before/after flashing the ROM. It makes not much difference. You could just flash the ROM, and then use an init.d script (explained here) to increse your memory (i personally recommend "int2ext", and not "int2ext+" or any other variants).
Since it is a 2 gB memory card, I am pretty sure it would be (<=) class 2. I would strongly recommend buying an SD Card that's atleast class 4, but a class 2 would splendidly do but performance would be slightly affected as it wouldn't be fast.
As far as Whatsapp is concerned, it has the option to backup messages to the SD Card. Since flashing an ICS ROM (coming from stock, I'm guessing), you would need to 'factory reset' the device (i.e. format the userdata + cache) partitions. You can safely restore the Whatsapp messages from the sdcard after flashing the ROM.
Partitioning the SD card
thewisenerd said:
As to partitioning your SDCard, I am assuming your objective is to "expand" you internal memory using "memory increasing scripts". This isn't a complex deal (I've explained how these work here), and mostly just involves one partition for reverse mounting the userdata (/data) partition.
You do not need to make two partitions, one would suffice. Also, you can make this partition before/after flashing the ROM. It makes not much difference. You could just flash the ROM, and then use an init.d script (explained here) to increse your memory (i personally recommend "int2ext", and not "int2ext+" or any other variants).
Since it is a 2 gB memory card, I am pretty sure it would be (<=) class 2. I would strongly recommend buying an SD Card that's atleast class 4, but a class 2 would splendidly do but performance would be slightly affected as it wouldn't be fast.
As far as Whatsapp is concerned, it has the option to backup messages to the SD Card. Since flashing an ICS ROM (coming from stock, I'm guessing), you would need to 'factory reset' the device (i.e. format the userdata + cache) partitions. You can safely restore the Whatsapp messages from the sdcard after flashing the ROM.
Click to expand...
Click to collapse
@thewisenerd, thank you very much for addressing my queries and providing links which further explain aspects relevant to the subject topics in question. I have exhausted my '8 thanks per day' quota, but nonetheless, I will definitely hit the thanks button once the quota has been renewed.
:good:
Keeping aside the default limited internal storage of the device, is it possible to have one desirable partition dedicated to installing apps, and another to store the end user's data such as images, videos, audio files, etcetera? Would this be an ideal scenario for the daily usage of the device?
Currently being on a stock Gingerbread firmware, I am gearing up to flash the MiniCM9 Build#7 custom Ice Cream Sandwich firmware, and once I have done that, I will need your assistance with partitioning/expanding the existing 2GB microSD memory card. I have suggested my colleague to purchase a higher capacity Class 4 memory card, perhaps an 8GB one, which she should do so by next week.
:silly:
After rooting the device, I have taken a backup of all user apps + system data. I am aware you have, in your thread http://forum.xda-developers.com/showthread.php?t=2169776, priorly suggested to refrain from restoring apps and data as they may lead to Force Closes, but is it absolutely compulsory to avoid restoring even contacts, text messages and calendar entries, as well as, apps (and their data) downloaded from the Google Play Store?
:fingers-crossed:
Keeping aside the default limited internal storage of the device, is it possible to have one desirable partition dedicated to installing apps, and another to store the end user's data such as images, videos, audio files, etcetera? Would this be an ideal scenario for the daily usage of the device?
Click to expand...
Click to collapse
er, you need to create two partitions (i.e. one fat32 (for files), and one ext4 (for installing apps)). You can easily create an ext partition by using the option in your recovery (usually found in the 'advanced' subcategory).
Currently being on a stock Gingerbread firmware, I am gearing up to flash the MiniCM9 Build#7 custom Ice Cream Sandwich firmware, and once I have done that, I will need your assistance with partitioning/expanding the existing 2GB microSD memory card. I have suggested my colleague to purchase a higher capacity Class 4 memory card, perhaps an 8GB one, which she should do so by next week.
:silly:
Click to expand...
Click to collapse
For partitioning, as said, the recovery can be used.
After rooting the device, I have taken a backup of all user apps + system data. I am aware you have, in your thread http://forum.xda-developers.com/showthread.php?t=2169776, priorly suggested to refrain from restoring apps and data as they may lead to Force Closes, but is it absolutely compulsory to avoid restoring even contacts, text messages and calendar entries, as well as, apps (and their data) downloaded from the Google Play Store?
:fingers-crossed:
Click to expand...
Click to collapse
for contacts, there's an "import/export from/to storage" option in the "people" app. For messages, I ain't sure. For Calendar entries, Google syncs it? Even otherwise, only contacts have been very 'important' to me, so I just export them to SDCard, and import them later.
NOTE: partitioning the sdcard WILL remove all data. In case you are backing up data on the sdcard, backup all the data on your SDCard on your PC too.
Partitioning the SD card
thewisenerd said:
You can easily create an ext partition by using the option in your recovery (usually found in the 'advanced' subcategory).
Click to expand...
Click to collapse
@thewisenerd, admittedly I am still quite confused about the partitioning business. The following is what I did -
Booted into the custom recovery (Yannou90 CWM-Based Recovery v5.0.2.).
Navigated to advanced and then to Partition SD Card.
Chose 1024M as the Ext Size and 0M as the Swap Size.
Pressed the power button to initiate the partitioning process.
After the partitioning process completed, I connected the device to my laptop and navigated to the Computer Management console under the Microsoft Windows platform. Within the Disk Management sub console, two partitions were listed for the removable storage, and while one partition had a drive letter assigned and file system denoted, the other partition did not. The partition which had a drive letter assigned and whose file system was denoted, displayed its capacity as nearly about 908MB, whereas the remaining 980-oddMB was displayed for the other partition.
I redid the partitioning process from the custom recovery, setting 2048M as the Ext Size and 0M as the Swap Size to go back to the memory card's initial state.
thewisenerd said:
er, you need to create two partitions (i.e. one fat32 (for files), and one ext4 (for installing apps)).
Click to expand...
Click to collapse
I implore you to kindly assist me with this.
:fingers-crossed:
YLNdroid said:
@thewisenerd, admittedly I am still quite confused about the partitioning business. The following is what I did -
Booted into the custom recovery (Yannou90 CWM-Based Recovery v5.0.2.).
Navigated to advanced and then to Partition SD Card.
Chose 1024M as the Ext Size and 0M as the Swap Size.
Pressed the power button to initiate the partitioning process.
After the partitioning process completed, I connected the device to my laptop and navigated to the Computer Management console under the Microsoft Windows platform. Within the Disk Management sub console, two partitions were listed for the removable storage, and while one partition had a drive letter assigned and file system denoted, the other partition did not. The partition which had a drive letter assigned and whose file system was denoted, displayed its capacity as nearly about 908MB, whereas the remaining 980-oddMB was displayed for the other partition.
I redid the partitioning process from the custom recovery, setting 2048M as the Ext Size and 0M as the Swap Size to go back to the memory card's initial state.
I implore you to kindly assist me with this.
:fingers-crossed:
Click to expand...
Click to collapse
The first 'process' was correct. why did you repartition with 2048 mB as the ext size?
the first 1024 mB (with a letter assigned) was the fat32 partition and the 'other' 1024 mB drive was the ext3/4 drive (not supported by windows) which is to be used for the reverse mounting process.
Partitioning the SD card
thewisenerd said:
The first 'process' was correct. why did you repartition with 2048 mB as the ext size?
the first 1024 mB (with a letter assigned) was the fat32 partition and the 'other' 1024 mB drive was the ext3/4 drive (not supported by windows) which is to be used for the reverse mounting process.
Click to expand...
Click to collapse
@thewisenerd, I appreciate your patience and guidance. I reckon I will go through the partitioning process again, create the 1024MB FAT32 partition, flash my preferred custom firmware and then, get to enabling the 'other' 1024MB ext3/4 drive. Which method would you suggest/recommend for the reverse mounting process?
:silly:
YLNdroid said:
@thewisenerd, I appreciate your patience and guidance. I reckon I will go through the partitioning process again, create the 1024MB FAT32 partition, flash my preferred custom firmware and then, get to enabling the 'other' 1024MB ext3/4 drive. Which method would you suggest/recommend for the reverse mounting process?
:silly:
Click to expand...
Click to collapse
"int2ext(4)", nothing more, nothing less.
Reverse Mount
thewisenerd said:
"int2ext(4)", nothing more, nothing less.
Click to expand...
Click to collapse
@thewisenerd, I downloaded, extracted and placed the 40int2ext script file, provided as an attachment within this thread http://forum.xda-developers.com/showthread.php?t=2389501 by @<Engine/>, to the root of the SD card, and following the consequent instructions, copied the said script file to /system/etc/init.d and set the permissions to all, as instructed within the aforementioned thread's guide.
However, when I navigate to Settings > Applications > Manage applications, the Internal storage at the bottom of the screen still displays 130MB free.
:silly:
Prior to copying the 40int2ext script file, I noticed the init.d folder has three pre-existing files, namely, 10mounts2sd, 33ng_tweaks and S70zipalign.
Should I try the CronMod-INT2EXT4_signed.zip file, provided by @croniccorey within the http://forum.xda-developers.com/showthread.php?t=1716124 thread?
:fingers-crossed:
I thank you for your continued assistance.
PS:
I forgot to mention the device is currently running on NExtGen 1.6 custom Gingerbread {Sense} firmware.
YLNdroid said:
@thewisenerd, I downloaded, extracted and placed the 40int2ext script file, provided as an attachment within this thread http://forum.xda-developers.com/showthread.php?t=2389501 by @<Engine/>, to the root of the SD card, and following the consequent instructions, copied the said script file to /system/etc/init.d and set the permissions to all, as instructed within the aforementioned thread's guide.
However, when I navigate to Settings > Applications > Manage applications, the Internal storage at the bottom of the screen still displays 130MB free.
:silly:
Prior to copying the 40int2ext script file, I noticed the init.d folder has three pre-existing files, namely, 10mounts2sd, 33ng_tweaks and S70zipalign.
Should I try the CronMod-INT2EXT4_signed.zip file, provided by @croniccorey within the http://forum.xda-developers.com/showthread.php?t=1716124 thread?
:fingers-crossed:
I thank you for your continued assistance.
PS:
I forgot to mention the device is currently running on NExtGen 1.6 custom Gingerbread {Sense} firmware.
Click to expand...
Click to collapse
you need to copy the script *after* flashing the ROM, and booting it. Also, you need to set the permissions (tick all the boxes!).
Hi all. Apologies for the wall of text, I have a few questions following all of the background below.
Device info: Samsung Galaxy S7 32GB running LineageOS 16.0, NOT rooted; SD Card in question is a 128GB Sandisk MicroSD. All commands being run on computer running Ubuntu 19.10.
Yesterday, my phone gave me the "SD Card Missing" notification suddenly, and in the settings it said it was corrupted. I had had it set up as adopted storage, so it isn't a matter of just losing photos and such unfortunately - it seems as though there's important app and system data on it.
After trying several recovery programs to no avail, I came across this thread:
https://forum.xda-developers.com/general/help/corrupted-sd-card-adoptable-storage-t3801250
Which is very similar to my situation. Unfortunately I didn't find a fix here, but I did manage to make a full .img copy of the card itself, and find the encryption key at "/data/misc/vold/expand_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.key" as per https://nelenkov.blogspot.com/2015/06/decrypting-android-m-adopted-storage.html . The problem I ran into with this guide was that I couldn't get the dmsetup command to work. However, when reading the comments of the post to see if anyone else had the problem, I saw someone mention retrieving the files through TWRP. So, I put the card back in the phone, and booted into TWRP.
In TWRP, I was able to browse through the SD Card perfectly normally with the file manager, despite the fact that it still read as corrupted when booting back into the system. So, I used adb pull (side question on this later) to retrieve the folders I was most worried about - largely what I could find of app data, my photos and videos, etc. I did not just pull the whole card at once, and I'll elaborate on why when I get to the side question about adb pull.
So, here are my questions:
1. Is it possible to mount this SD Card back to normal through TWRP? If so, how? I'd like just enough so that I can restore my apps as is onto the phone, and then convert the card to portable storage to avoid this mess again. While I do have the data pulled, it's little things like NewPipe playlists that I've got in mind here.
2. If above is not possible, how much loss am I looking at if I choose to 'forget' the adopted card? Will I have to do a factory reset?
3. (adb) When doing the adb pull, it was unable to skip any files it couldn't copy - i.e. corrupted images - and would simply stop on finding one. This means that, for example, in one folder it hit a corrupted file after 3400 successes, and stopped without copying the remaining 300. Naturally, if I had just done 'adb pull /external_sd/', then I probably would have lost a lot more because of this. Can I add any options to the command adb pull to circumvent this? I was unable to find any decent documentation on the command, but maybe I was searching for the wrong thing.
Any and all help is much appreciated, thanks in advance!
johnfr92 said:
Hi all. Apologies for the wall of text, I have a few questions following all of the background below.
Device info: Samsung Galaxy S7 32GB running LineageOS 16.0, NOT rooted; SD Card in question is a 128GB Sandisk MicroSD. All commands being run on computer running Ubuntu 19.10.
Yesterday, my phone gave me the "SD Card Missing" notification suddenly, and in the settings it said it was corrupted. I had had it set up as adopted storage, so it isn't a matter of just losing photos and such unfortunately - it seems as though there's important app and system data on it.
After trying several recovery programs to no avail, I came across this thread:
https://forum.xda-developers.com/general/help/corrupted-sd-card-adoptable-storage-t3801250
Which is very similar to my situation. Unfortunately I didn't find a fix here, but I did manage to make a full .img copy of the card itself, and find the encryption key at "/data/misc/vold/expand_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.key" as per https://nelenkov.blogspot.com/2015/06/decrypting-android-m-adopted-storage.html . The problem I ran into with this guide was that I couldn't get the dmsetup command to work. However, when reading the comments of the post to see if anyone else had the problem, I saw someone mention retrieving the files through TWRP. So, I put the card back in the phone, and booted into TWRP.
In TWRP, I was able to browse through the SD Card perfectly normally with the file manager, despite the fact that it still read as corrupted when booting back into the system. So, I used adb pull (side question on this later) to retrieve the folders I was most worried about - largely what I could find of app data, my photos and videos, etc. I did not just pull the whole card at once, and I'll elaborate on why when I get to the side question about adb pull.
So, here are my questions:
1. Is it possible to mount this SD Card back to normal through TWRP? If so, how? I'd like just enough so that I can restore my apps as is onto the phone, and then convert the card to portable storage to avoid this mess again. While I do have the data pulled, it's little things like NewPipe playlists that I've got in mind here.
2. If above is not possible, how much loss am I looking at if I choose to 'forget' the adopted card? Will I have to do a factory reset?
3. (adb) When doing the adb pull, it was unable to skip any files it couldn't copy - i.e. corrupted images - and would simply stop on finding one. This means that, for example, in one folder it hit a corrupted file after 3400 successes, and stopped without copying the remaining 300. Naturally, if I had just done 'adb pull /external_sd/', then I probably would have lost a lot more because of this. Can I add any options to the command adb pull to circumvent this? I was unable to find any decent documentation on the command, but maybe I was searching for the wrong thing.
Any and all help is much appreciated, thanks in advance!
Click to expand...
Click to collapse
Hey...did u get dmsetup to work?
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.