Related
I have a problem with a goophone i5. First I had problems with it not having a signal but that got solved. Now a second problem came up. I plugged the phone in the laptop, clicked on 'turn on usb', after a while I clicked the 'turn off usb' on the phone. It was off, I unplugged and then it gave a warning "not safely removed, sd damaged", while it was safely removed! Now I can't do anything with it like download apps to it etc. It keeps giving that memory is full. So I assume the 8GB is damaged. I have no idea how to fix it, since I searched already, but it's not like I can take the 8GB out, since it's not removable. Do you know a solution or can you help me? Thank you in advance. When I plug the phone the card is just unrecognisable, therefore I can't format it in anyway :crying:
-Loren
Goophone I5 Lite
pardolorev said:
I have a problem with a goophone i5. First I had problems with it not having a signal but that got solved. Now a second problem came up. I plugged the phone in the laptop, clicked on 'turn on usb', after a while I clicked the 'turn off usb' on the phone. It was off, I unplugged and then it gave a warning "not safely removed, sd damaged", while it was safely removed! Now I can't do anything with it like download apps to it etc. It keeps giving that memory is full. So I assume the 8GB is damaged. I have no idea how to fix it, since I searched already, but it's not like I can take the 8GB out, since it's not removable. Do you know a solution or can you help me? Thank you in advance. When I plug the phone the card is just unrecognisable, therefore I can't format it in anyway :crying:
-Loren
Click to expand...
Click to collapse
Hi mate!
You have there a problem! First of all goophone do not come with 8GB sd card storage. There are 2 different options: the 16GB and 32 GB so, first of all, try to see if you have a real goophone i5.
Then, there is a way to format the SD card. For that you must buy a Screw Driver to open it. After that take out the screws, pull up the display and you will see the sd card inside. Just unplug it, put it on a SD card Adapter and format it on your desktop.
It can give you SD card Damage for a few times, but ignore it and keep formating it until the warning disapears.
For the screw driver you just need to search on ebay. They are very cheap. So all you have to do is to buy one.
Hope this information helped you out.
Regards
Loren can I ask how you got a signal? I just have no service at top of screen. Driving me nuts,
Changed SDCARD
Hi everybody,
Please help me i have a problems with my phone.
I want change my sdcard because now the phone do not recognize my sdcard.
Do you have any instruction for how to open and change the sdcard?
Thanks you .
lychat said:
Hi everybody,
Please help me i have a problems with my phone.
I want change my sdcard because now the phone do not recognize my sdcard.
Do you have any instruction for how to open and change the sdcard?
Thanks you .
Click to expand...
Click to collapse
I`ve got the same problem as you but I don't know how open it...
If you find something, tell me please.
you can first try to re-flash the phone to the original ROM using SP Flash Tool...
Is there a trick to getting the glass to pull up? I've taken out the screws, and put the suction cup down near the home button, but when I pull the glass wants to separate from the bracket that holds it to the phone. There is a tearing sound, like adhesive giving away, and it's fighting me. I don't want to pull any harder for fear that I'm going to damage it.
The reason I'm doing this, is that my SD card has also died, and is no longer recognized by the phone, and I'm wanting to replace it.
AllanBjorklund said:
Is there a trick to getting the glass to pull up? I've taken out the screws, and put the suction cup down near the home button, but when I pull the glass wants to separate from the bracket that holds it to the phone. There is a tearing sound, like adhesive giving away, and it's fighting me. I don't want to pull any harder for fear that I'm going to damage it.
The reason I'm doing this, is that my SD card has also died, and is no longer recognized by the phone, and I'm wanting to replace it.
Click to expand...
Click to collapse
Can't this help? :got this from android website: ((((( I have been fighting this issue for 6 months, off and on. Used to think it was the SD Cards, but have concluded its got to be software. I used different methods to fix it, but over trial and error I think I found the easiest way.
Reboot into Recovery, go to advanced options. Select to mount via USB, then connect to a pc. May take a few times plugging in and out, till you get the sd card drive to appear on your pc. Once you get it, back out of usb mount. Disconnect the cord, and verify your sd card is mounted. I just go into the install a zip from sd card option, if I see files/folders I know its mounted. back up and select the restart device.
This method I stumbled on, in my efforts to just try and get my phone back. After I made the mistake of formating everything includeing the boot, and other internal components. Was pure luck, but it works. I know now it wasn't the format of the SD Card nor the sd card itself, cause I have tried several. Also used to think it was the file system, cause I used to get the cards working again by formating and then pasteing saved files/folders from an earlier back up. Also have factoy reset many times, that doesn't fix it, and reflashing a ROM sometimes does appear to work, but I think its because of restucture of the file system during that process. Anyway let me know if this helped you.))))
I have same problem with SD card, but I think it is not really broke but rather software problem.
I want to fix problem without removing screen or anything, can anyone help?
I have the Chinese recovery installed.
DaltonMaltese said:
Can't this help? :got this from android website: ((((( I have been fighting this issue for 6 months, off and on. Used to think it was the SD Cards, but have concluded its got to be software. I used different methods to fix it, but over trial and error I think I found the easiest way.
Reboot into Recovery, go to advanced options. Select to mount via USB, then connect to a pc. May take a few times plugging in and out, till you get the sd card drive to appear on your pc. Once you get it, back out of usb mount. Disconnect the cord, and verify your sd card is mounted. I just go into the install a zip from sd card option, if I see files/folders I know its mounted. back up and select the restart device.
This method I stumbled on, in my efforts to just try and get my phone back. After I made the mistake of formating everything includeing the boot, and other internal components. Was pure luck, but it works. I know now it wasn't the format of the SD Card nor the sd card itself, cause I have tried several. Also used to think it was the file system, cause I used to get the cards working again by formating and then pasteing saved files/folders from an earlier back up. Also have factoy reset many times, that doesn't fix it, and reflashing a ROM sometimes does appear to work, but I think its because of restucture of the file system during that process. Anyway let me know if this helped you.))))
Click to expand...
Click to collapse
Thanks for the suggestion. Unfortunately, it didn't help.
Got exactly the same problem.. and this is what I have found out so far
If you go to mnt folder using programs like root explorer or rom tool box you will notice 2 folder.. 1st called sdcard which is your internal card and sdcard2 which is the external card
under scard card there are some letters which indicate the permission level it has but under sdcard2 it only shows -----, I manually changed the permission for sdcard 2 (normally long click on the folder name and select permission from the menu) once I done that the external sdcard started to work fine, however when I reboot the phone the sdcard2 lose the permission again
Also, I contacted the guy who I bought the phone from (efit) who told me to open the phone and take the sdcard out and then put it in again and that should make it work, I managed to remove the screen off (not really sure but I think the 2 screws beside the lightning connector is for decoration only).. as you can see from the phone there is no way to access the sd card (unless I did something wrong here)
I contacted efit asking him for some instructions on how to open the phone but I couldn't find the sd card and now he is telling because I opened the phone myself I lost the warranty... what a scum bag !!!
tried the mount to usb thing but that didn't work..
hopefully will find a solution soon
Thanks for this, I almost opened my phone for nothing.
I went to a store to get it open but one of the screws would not come lose, so they didn't try further.
Stupid problem with SD, hope someone will find solution soon.
But you managed to get it working until reboot?
With my phone in mnt folder: sdcard has no permissions and sdcard2 has ---rwxr-x as permission.
What should I change there?
Thanks
ciao
alduleimi said:
Got exactly the same problem.. and this is what I have found out so far
If you go to mnt folder using programs like root explorer or rom tool box you will notice 2 folder.. 1st called sdcard which is your internal card and sdcard2 which is the external card
under scard card there are some letters which indicate the permission level it has but under sdcard2 it only shows -----, I manually changed the permission for sdcard 2 (normally long click on the folder name and select permission from the menu) once I done that the external sdcard started to work fine, however when I reboot the phone the sdcard2 lose the permission again
Also, I contacted the guy who I bought the phone from (efit) who told me to open the phone and take the sdcard out and then put it in again and that should make it work, I managed to remove the screen off (not really sure but I think the 2 screws beside the lightning connector is for decoration only).. as you can see from the phone there is no way to access the sd card (unless I did something wrong here)
I contacted efit asking him for some instructions on how to open the phone but I couldn't find the sd card and now he is telling because I opened the phone myself I lost the warranty... what a scum bag !!!
tried the mount to usb thing but that didn't work..
hopefully will find a solution soon
Click to expand...
Click to collapse
DaltonMaltese said:
Thanks for this, I almost opened my phone for nothing.
I went to a store to get it open but one of the screws would not come lose, so they didn't try further.
Stupid problem with SD, hope someone will find solution soon.
But you managed to get it working until reboot?
With my phone in mnt folder: sdcard has no permissions and sdcard2 has ---rwxr-x as permission.
What should I change there?
Thanks
ciao
Click to expand...
Click to collapse
Do you have manuxo rom or pure ICS installed on the phone because I've noticed that with manuxo rom sdcard2 have no permission but with pure ICS sdcard is the one with no permission.. which I thought it's a bit strange
I have asked before in this forum if anyone with working sdcard to share what permission they have but no one answered !
alduleimi said:
Do you have manuxo rom or pure ICS installed on the phone because I've noticed that with manuxo rom sdcard2 have no permission but with pure ICS sdcard is the one with no permission.. which I thought it's a bit strange
I have asked before in this forum if anyone with working sdcard to share what permission they have but no one answered !
Click to expand...
Click to collapse
I Installed the Manuxo rom v1.28, sd card problem happened week later.
I installed like viber, skype, whatsapp, facebook, soundcloud, simpsons tapped out, angry birds and all that stuff on phone, transferred to sd.
And just all of a sudden, when phone was lying there, it gave error, I rebooted and I lost everything..
But I can still see the fotos on sd card2 through file explorer. Weird stuff.
OK, let's wait for answers of other users I guess.
I also mailed to androidsale what to do, he said try to pull it out and try it a few times, maybe not good connected with sd slot pin, but I can't believe that because phone still finds SD in ROM TOOL lite.
Thanks for your time and effort in this problem!!
vnman said:
you can first try to re-flash the phone to the original ROM using SP Flash Tool...
Click to expand...
Click to collapse
Can you tell me how to do this?
Getting desperate...
Thanks
Hello, I have the same problem with my goophone i5 v88 I can't mount the sd card (16GB)
I have try to remove my screen but I have the same problem I can't found the sd card (just my sim card...)
Adb shell
you can connect the phone to pc and use adb available with mtk droid tools to force format the sdcard.
Adb shell
Fdisk (search google for how to use fdisk)
If the phone is rooted and has cwm you can format sdcard via cwm.
vnman said:
you can connect the phone to pc and use adb available with mtk droid tools to force format the sdcard.
Adb shell
Fdisk (search google for how to use fdisk)
If the phone is rooted and has cwm you can format sdcard via cwm.
Click to expand...
Click to collapse
Thank you very much for the response!!
But I am a noob and don''t know how to do it all, first adb is installed and made available.
Then I installed mtk droid tools. It gives this in info :Free space: system- 251M; data- 153M; sdcard2- 1G; C:\ 75544M
But I don't know how to format now.
Do I have to enter a command in the adb terminal?
Do I have to combine Fdisk and adb shell?
I's not rooted cwm with me, its the chinese recovery from Mayiaandjay from youtube.
Many thanx for the help, almost was going to use it as a picture frame
I do not have access to my PC right now but...
On the right of MTK Droid Tools there are 3 buttons "Root" "ADB Terminal" "Reboot"
Root the phone by pressing "Root", and follow instructions...
Pres "ADB Terminal" to enter Windows command shell, type "adb shell" (without the quotes) to enter the phone shell. Next type fdisk then "enter" and see what comes up...
type "mount" also to find out where your sdcard mounted...
Then search with Google for how to format sdcard...
vnman said:
I do not have access to my PC right now but...
On the right of MTK Droid Tools there are 3 buttons "Root" "ADB Terminal" "Reboot"
Root the phone by pressing "Root", and follow instructions...
Pres "ADB Terminal" to enter Windows command shell, type "adb shell" (without the quotes) to enter the phone shell. Next type fdisk then "enter" and see what comes up...
type "mount" also to find out where your sdcard mounted...
Then search with Google for how to format sdcard...
Click to expand...
Click to collapse
Ok, great, but I can't find the root Button on MTK :/ .
Guess it's alreay rooted..
I'm now in adb shell but where do I check mount usb.
Also my sdcard is not recognised by windows so how can I format?
Thanks and sorry for my noobness
DaltonMaltese said:
Ok, great, but I can't find the root Button on MTK :/ .
Guess it's alreay rooted..
I'm now in adb shell but where do I check mount usb.
Also my sdcard is not recognised by windows so how can I format?
Thanks and sorry for my noobness
Click to expand...
Click to collapse
This is where I got.:
How can I mount or unmount the SD Card using ADB?
The sdcard can be umounted by using the umount command.
unmount /mtn/sdcard/.android_secure
how can it be remounted again :
mount /mnt/sdcard/.android_secure
.
Type mount sdcard next to the "#" sign & press enter...
You will need to know the mount point also if you intend to mount the external card.
As an example:
su mount -o bind /mnt/emmc /sdcard/external_sd
.....................
Like this? And I need to write sdcard2 instead of sdcard I guess?
or this:
First, on your phone, go into Home -> Settings -> SD card & phone storage, then click on "Unmount SD card"
Then, in your shell, do the following.
Code:
adb shell
mkfs.vfat /dev/block//vold/179:1
Then go back to the phone and mount the SD card again. Of course, it would probably be easier to just click "Format SD card," rather than going through adb.
.....
Difficult, don't want to brick my phone..
Many thanks
Not sure if this is the right place to post this, if not a moderator please move it to the right place.
I rooted my Samsung GT-S7580, following the tutorial on this forum, everything went ok. After rooting I wanted to use an app called GL to SD (tried FolderMount first but it didnt work due to some faulty thing) after I opened it it said that it needed to change some folder/files issues and rebooted.
Now I can;t access "device storage" anymore, can't install anything. If I plug in the USB cable all I can see is the external sd card and Phone 127MB/128MB but if I open it's empty. I cant copy anything to either locations. Same thing with the phones file explorer I can only access the external sd card, if I click "Device Storage" it's empty for a second then it backs up.
I did a factory rest ... same thing. Please tell me there is a way to fix this and I didn't just make my phone a paper weight.
I can still use odin and android recovery system.
Phyxious said:
Not sure if this is the right place to post this, if not a moderator please move it to the right place.
I rooted my Samsung GT-S7580, following the tutorial on this forum, everything went ok. After rooting I wanted to use an app called GL to SD (tried FolderMount first but it didnt work due to some faulty thing) after I opened it it said that it needed to change some folder/files issues and rebooted.
Now I can;t access "device storage" anymore, can't install anything. If I plug in the USB cable all I can see is the external sd card and Phone 127MB/128MB but if I open it's empty. I cant copy anything to either locations. Same thing with the phones file explorer I can only access the external sd card, if I click "Device Storage" it's empty for a second then it backs up.
I did a factory rest ... same thing. Please tell me there is a way to fix this and I didn't just make my phone a paper weight.
I can still use odin and android recovery system.
Click to expand...
Click to collapse
Iif this isn't a Note 3 (N9005) you aren't going to get any help here...
Each device has its own way to root and different recovery. If you flashed something from this forum in all likelyhood you have (possibly) bricked your phone...
My suggestion would be to find your stock rom and flash that... Then (hope you backed up) wipe everything and try again...
I used a tutorial for my phone model and like I said the rooting went fine. I was able to install and uninstal apps, even rebooted it a few times. The problem was after that gl to sd app did something to my file system. Most things still work, I'm on it right now. It seem that I can't access its internal memory
Phyxious said:
Not sure if this is the right place to post this, if not a moderator please move it to the right place.
I rooted my Samsung GT-S7580, following the tutorial on this forum, everything went ok. After rooting I wanted to use an app called GL to SD (tried FolderMount first but it didnt work due to some faulty thing) after I opened it it said that it needed to change some folder/files issues and rebooted.
Now I can;t access "device storage" anymore, can't install anything. If I plug in the USB cable all I can see is the external sd card and Phone 127MB/128MB but if I open it's empty. I cant copy anything to either locations. Same thing with the phones file explorer I can only access the external sd card, if I click "Device Storage" it's empty for a second then it backs up.
I did a factory rest ... same thing. Please tell me there is a way to fix this and I didn't just make my phone a paper weight.
I can still use odin and android recovery system.
Click to expand...
Click to collapse
Click top-right corner.
Press samsung restore.
tnslf2k said:
Click top-right corner.
Press samsung restore.
Click to expand...
Click to collapse
Going to need a little more details than that ...
Anyway it seems that I can install apps if I transfer their apk on my sdcard on another phone and then put the sd card in my samsung, I installed es file explorer and I can access some parts like /sdcard/ but not /storage/emulated/legacy that one is "not found", maybe it's a permission issue?
Start gl to sd.
Then click top-right corner(three dots).
Press "Restored samsung".
tnslf2k said:
Start gl to sd.
Then click top-right corner(three dots).
Press "Restored samsung".
Click to expand...
Click to collapse
I would do that, if I could find some place to download gl to sd apk .. I can't install using google play and seems all links lead there.
EDIT: The newest version I could find (2.2.0) only has "move data". "Show mounted folders", "Purchase PRO" and "Setting" under those 3 dots and none of these show a restore setting or any mounted folders.
Please update v2.2.22
Only new version has this feature.
Phyxious said:
I would do that, if I could find some place to download gl to sd apk .. I can't install using google play and seems all links lead there.
EDIT: The newest version I could find (2.2.0) only has "move data". "Show mounted folders", "Purchase PRO" and "Setting" under those 3 dots and none of these show a restore setting or any mounted folders.
Click to expand...
Click to collapse
I poked around more and it seems the only place I can;t access is /storage/emulated (it's empty). Added some screenshots
Phyxious said:
Not sure if this is the right place to post this, if not a moderator please move it to the right place.
I rooted my Samsung GT-S7580, following the tutorial on this forum, everything went ok. After rooting I wanted to use an app called GL to SD (tried FolderMount first but it didnt work due to some faulty thing) after I opened it it said that it needed to change some folder/files issues and rebooted.
Now I can;t access "device storage" anymore, can't install anything. If I plug in the USB cable all I can see is the external sd card and Phone 127MB/128MB but if I open it's empty. I cant copy anything to either locations. Same thing with the phones file explorer I can only access the external sd card, if I click "Device Storage" it's empty for a second then it backs up.
I did a factory rest ... same thing. Please tell me there is a way to fix this and I didn't just make my phone a paper weight.
I can still use odin and android recovery system.
Click to expand...
Click to collapse
I have the same problem, but the system writes "Not enough memory to install applications". Installed via Google Play, through the apk files - nothing works. Does anyone know what exactly this program is changing? I am excruciated wildly. I do not want to reflash the phone.
Please help I am new to this stuff and yesterday I got my phone to cm 10.1 but I realized the .zip from the thread was wrong and now i have 4.2.1 running on my phone but 4.3 gapps and because of that my phones keyboard wont work. Also I cant flash new gapps because it doesn't let me install from my external sd and i haven't found a way to connect my phone to my computer.
Can someone please help me?
Tell me ways I can connect to my pc?
charminster said:
Please help I am new to this stuff and yesterday I got my phone to cm 10.1 but I realized the .zip from the thread was wrong and now i have 4.2.1 running on my phone but 4.3 gapps and because of that my phones keyboard wont work. Also I cant flash new gapps because it doesn't let me install from my external sd and i haven't found a way to connect my phone to my computer.
Can someone please help me?
Tell me ways I can connect to my pc?
Click to expand...
Click to collapse
You can't just... Plug it in to your PC? Don't you have a USB cable?
Connor Baker
No it doesn't connect to my computer. Even tried with other computers and wires
charminster said:
No it doesn't connect to my computer. Even tried with other computers and wires
Click to expand...
Click to collapse
If you cannot turn developer mode on and use ADB push, then, you should be able to in CWM.
Failing that, does Google Play work?
If so, install (from your PC via Google Play page) WiFi File Transfer Pro, fire up an FTP session and push the needed GApps over.
And if all else fails...
ODIN back to stock.
I really don't get it
Can you explain this in detail?
charminster said:
I really don't get it
Can you explain this in detail?
Click to expand...
Click to collapse
Sure thing.
ADB is the debug program for Android. You can use it specifically to push files to the device. But it is not turned on on the device by default. You will need to go into developer options under settings and turn USB debugging on (if Developer Options is not there, go into About Phone and tap Build Number 7 or 8 times tom unlock the feature).
For this to work, you will need a linux PC with an ADB binary (if using Debian/Ubuntu, can "apt-get install adb", then run adb as superuser or sudo) or a windows computer with adbsetup installed. The latter will install the program to C:\adb. So open a command prompt and (with the device plugged in and developer options turned on) type:
Code:
c:
cd \adb
adb devices
You should get a listing of your device, raring to go. If so, great! Copy the the appropriate Gapps package to C:\ADB and type:
Code:
adb push gapps-4.2.zip gapps-4.2.zip
...or whatever the filename is called (there twice as it needs the local and remote file name).
So if that works, can reboot into recovery (CWM) via the three finger salute (turn device off fully, wait a few seconds, hold down both volume buttons while pressing the power button), wipe dalvik cache, and flash the right GApps.
Another option is if you can add Google Play apps to your device. Don't imagine, but if it is possible, fire up your computer and log into your Google Play account. Search for "WiFi File Transfer Pro" and install. With a Wifi connection on the device, it should download and install. If it doesn't, try the scorched earth option below. If it does install, open Wifi File Transfer Pro, turn on FTP server, and keep note of the IP address and Port (Will be noted as IPort). Open or install an FTP client like FileZilla on your PC, and open a connection using that IP address and Port. Transfer the Gapps package over to the device, in the root folder. Then like above, reboot into recovery and wipe dalvik, flash gapps.
The last option, the scorched earth method, is to bring everything back to stock, mind you with root and CWM. Pick option D from the above link (previous post). Download and install adbsetup for the drivers. Option D download will come with a program called ODIN, and that link will have detailed instructions (download and extract the files, open ODIN, put the phone into download mode by turning the device off, hold down both volume buttons while inserting the MicroUSB cable, place the extracted files inthe right sections of ODIN, and flash away).
Hope this helps.
Ok one of my main problems is that I can't use keyboard...which means no internet because I can't type any passwords
And the other big thing is that none of my computers connect toy phone even with USB debugging on from setting and even in recovery
I was wondering if I get a connection with no password will I be update from the phone because there is an option to do so.
charminster said:
Ok one of my main problems is that I can't use keyboard...which means no internet because I can't type any passwords
And the other big thing is that none of my computers connect toy phone even with USB debugging on from setting and even in recovery
I was wondering if I get a connection with no password will I be update from the phone because there is an option to do so.
Click to expand...
Click to collapse
Because Google Play is part of Gapps, there is no guarantee that will work either to update. If you can find an unsecured network (or temporarily turn off WPA on your router), you can test this, but at this point, I would be doing the scorched earth method. You would only be going back to Gingerbread, and however you play your cards (whether you disable lagfix or flash ICS as an intermediary), you would only be one or two flashes away from a functional Jellybean.
Ok my phone doesnt connect with usb ive tried several different times.
I did the adb method everything was fine except i didnt get the device list ,it was empty.
So if it cant connect how will i connect it to my computer to use odin?
Ps. I did download the drivers
charminster said:
Ok my phone doesnt connect with usb ive tried several different times.
I did the adb method everything was fine except i didnt get the device list ,it was empty.
So if it cant connect how will i connect it to my computer to use odin?
Ps. I did download the drivers
Click to expand...
Click to collapse
True enough. Lets try this (as I just thought about it via some other weird, more convoluted way). CM 10.1 comes with a file manager right? Download the 4.2 Gapps onto your mcroSD card, insert it into your device. Fire up the file manager. Copy the Gapps file from the external SD card to the internal card, root folder (where the offending Gapps lies). Reboot into ClockworkMod and wipe Dalvik and install the appropriate zip.
If this does not work, my more convoluted way wouldn't either (search and download "wifi file transfer pro apk" to SD, open with file manager, install, follow the rest of above option 2), and would be out of options except getting your hardware fixed (as it sounds like your device not connecting via USB is a hardware issue).
Ive tried with micro sd before and it hasnt worked
The thing is that All of this stopped working after the update and the thing that i disliked the most was that when i was getting the update it said jb 4.2 gapps but proved wrong
:crying:
charminster said:
Ive tried with micro sd before and it hasnt worked
Click to expand...
Click to collapse
You tried mounting the microSD with the proper Gapps, and copying it with CM's File Manager (to the internal disk to be picked up by CWM later)? Just being clear, and making sure you are not talking about trying to install a zip directly from the MicroSD with CWM (as mentioned, and ruled out before). Because these are two completely different things. Is the MicroSD readable at all on your device? Is it formatted properly (FAT32, or even Ext2/3/4, but not NTFS)?
Can you explain the formatting stuff?
charminster said:
Can you explain the formatting stuff?
Click to expand...
Click to collapse
Sure. Insert the microSD into your computer, and open up Windows Explorer. There will be a new drive that appears. Right click on that removable drive, and select Properties. Confirm the File System. If it is FAT32, you are okay. If it is NTFS, or exFAT, you will need to format (as the Infuse will not recognize these formats). Press Cancel.
Before beginning, make a backup of the MicroSD card, as we are going to wipe and start from scratch. Then, right click on the removable drive again (and only this drive, or you will cause damage to your computer) and select Format. Change the file system to FAT32. If this is not an option, find and download a disk utility that will (I'm not familiar with them, but google "removable storage format fat32 download" for one). Press start, and wait a few minutes. When done, you can reload your files on the drive (restore your backup), and try inserting it in your Infuse again.
Hope this helps.
I followed all your steps bit the phone still doesnt read it i opened setting..storage..mount external sd
But it wasnt letting me and the same thing trying through recoveryCWM
charminster said:
I followed all your steps bit the phone still doesnt read it i opened setting..storage..mount external sd
But it wasnt letting me and the same thing trying through recoveryCWM
Click to expand...
Click to collapse
Probably not, IIRC external SD did not work in CWM for the Infuse. But re-read post #10, what I'm suggesting is getting CWM to read the proper Gapps from the internal card, but placing it there with CyanogenMod's file manager.
CM 10.1 comes with a file manager right? Download the 4.2 Gapps onto your mcroSD card, insert it into your device. Fire up the file manager. Copy the Gapps file from the external SD card to the internal card, root folder (where the offending Gapps lies). Reboot into ClockworkMod and wipe Dalvik and install the appropriate zip.
Click to expand...
Click to collapse
I cant get it there because i cant do anything with the sd card it doesnt show in file manager either
charminster said:
I cant get it there because i cant do anything with the sd card it doesnt show in file manager either
Click to expand...
Click to collapse
Sorry, I misread your previous post. Thanks for the clarification. What are the details on the microSD card? Make, model, speed, capacity? If it is a 64+ GB card, it would spell problems as the Infuse was never rated for a capacity that large.
It's a sandisk 16 gb
Sd card
Fat32
No reason why the microSD won't work in the Infuse.
If you have a Bluetooth keyboard you can borrow - or try buying (not sure if it will connect) - but if you can get your hands on one, you could use that (never had to use one so I don't know how they connect) to download the right GApps package to your phone (via the built-in browser).
I'm curious as well, if the speech-to-text works. You could use google now search to find the gapps package ("okay google, xda developers") and browse to the right page. Of course you will need a unsecured network to attempt.
Other than that, unfortunately I'm out of ideas.
Hey guys, I've found a way to recover files from the INTERNAL Memory of the Samsung Galaxy S4.
A lot of people have said that it's not possible, but I'm here to prove them wrong.
You have to have rooted your phone before carrying out these steps. Don't post here asking for help rooting, there's plenty of other threads that can help you with that.
I hold zero liability in the event that you make a nice brick out of your phone. If you do not feel comfortable working with these commands, then please don't follow them.
You're going to need an SD Card that's at least the size of the internal memory on the phone. A smaller one would work, but keep in mind not all the files are going to be recovered.
If the SD Card is brand spanking new, you can skip step number 1.
Format the SDCard with a layer of 0's. This is done so that none of the old data will interfere with your recovery. This step is optional.
Root the Device
Install Terminal Emulator
Insert the SDCard
In Terminal Emulator run the command to gain super user privileges
Code:
su
Grant Terminal Emulator super user privileges
Run this command,
Code:
dd if=/dev/block/mmcblk0p29 of=/storage/extSdCard/raw.dd
Wait. Leave your phone plugged into an AC Adapter, and go grab a can of pop. This command will take a looong time. Couple hours to a day.
Once the command is finished running, shutdown your phone.
Remove the SDCard, and connect it to a computer
Download TestDisk
Open PhotoRec
Select the SDCard and press enter
Use the first option of "Unknown"
Then press "Other"
Select the Directory to backup the files to
Profit
'
How it works:
By dd'ing the internal memory to a file on the SDCard, you're doing a raw copy of the data.
Once the data is copied onto the SDCard, PhotoRec will scan the SDCard for deleted data, doing so will scan the raw file for photos. Not just photos, all files can be recovered using this method.
This method works on all rootable phones, provided you can figure out where the dev block for the internal memory is.
Hope you guys get your files recovered. I know I did
Or just install a file recovery app from play store on a rooted phone and follow app instructions...
Worked a charm for me. lol
jamieridler said:
Or just install a file recovery app from play store on a rooted phone and follow app instructions...
Worked a charm for me. lol
Click to expand...
Click to collapse
Any app you recommend in particular?
Bingley said:
Any app you recommend in particular?
Click to expand...
Click to collapse
Tbh I just downloaded the first app I came across that was free and had half decent reviews, can't remember what one, it was a little while ago, but there are loads of them in the store.
jamieridler said:
Or just install a file recovery app from play store on a rooted phone and follow app instructions...
Worked a charm for me. lol
Click to expand...
Click to collapse
A lot of those apps are for the external SD Card, only support the FAT filesystem, and not as robust as PhotoRec from TestDisk.
Newer devices(Such as the S4) have an ext3 filesystem I believe, and a few paid apps claim to offer support for it.
... Not to mention TestDisk is Open Source :angel:
zzarzzur said:
A lot of those apps are for the external SD Card, only support the FAT filesystem, and not as robust as PhotoRec from TestDisk.
Newer devices(Such as the S4) have an ext3 filesystem I believe, and a few paid apps claim to offer support for it.
... Not to mention TestDisk is Open Source :angel:
Click to expand...
Click to collapse
Although some might well be limited to FAT filesystem, some are not, its up to the user to check before downloading and installing. After that rather simple search and install, I managed to recover every img file on my phone, current and deleted, and back it all up to external memory, all with a free app, which offers img file recovery for free and any other file type of your choice for a small, one off, cost, if you needed it. I recovered almost 1gb of img files in under 10 minutes.
Am I correct in assuming your method copies the entire contents of the internal memory, or a portion of it, to an SD card before starting the search for deleted files? I'm just an amateur with little knowledge trying to figure out how your method works. Sorry don't mean to bash your method of doing it either, just commenting on this as your post suggest no one has ever been able to do this before and your method is the one and only way it can be done.
But if the device is factory reset, will you be able to get files? If i sell my device i don't want anyone sneaking on my photos.
problems
zzarzzur said:
Hey guys, I've found a way to recover files from the INTERNAL Memory of the Samsung Galaxy S4.
A lot of people have said that it's not possible, but I'm here to prove them wrong.
You have to have rooted your phone before carrying out these steps. Don't post here asking for help rooting, there's plenty of other threads that can help you with that.
I hold zero liability in the event that you make a nice brick out of your phone. If you do not feel comfortable working with these commands, then please don't follow them.
You're going to need an SD Card that's at least the size of the internal memory on the phone. A smaller one would work, but keep in mind not all the files are going to be recovered.
If the SD Card is brand spanking new, you can skip step number 1.
Format the SDCard with a layer of 0's. This is done so that none of the old data will interfere with your recovery. This step is optional.
Root the Device
Install Terminal Emulator
Insert the SDCard
In Terminal Emulator run the command to gain super user privileges
Code:
su
Grant Terminal Emulator super user privileges
Run this command,
Code:
dd if=/dev/block/mmcblk0p29 of=/storage/extSdCard/raw.dd
Wait. Leave your phone plugged into an AC Adapter, and go grab a can of pop. This command will take a looong time. Couple hours to a day.
Once the command is finished running, shutdown your phone.
Remove the SDCard, and connect it to a computer
Download TestDisk
Open PhotoRec
Select the SDCard and press enter
Use the first option of "Unknown"
Then press "Other"
Select the Directory to backup the files to
Profit
'
How it works:
By dd'ing the internal memory to a file on the SDCard, you're doing a raw copy of the data.
Once the data is copied onto the SDCard, PhotoRec will scan the SDCard for deleted data, doing so will scan the raw file for photos. Not just photos, all files can be recovered using this method.
This method works on all rootable phones, provided you can figure out where the dev block for the internal memory is.
Hope you guys get your files recovered. I know I did
Click to expand...
Click to collapse
So i've followed your guidelines to a 'T' with a brand new 64g (huge, i know) Sd card, but the command line responds with, "writer error: file to large". Any advice as to how to proceed?
Really appreciate your efforts on this issue, btw!
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.