I flashed the TWRP recovery compatible with treble from the Screwd ROM thread because I was having a problem with the normal TWRP (that is it didn't show the date or hour correctly even if I changed them).
I flashed it using flashify, I went to recovery to see if everything was ok, it was so I rebooted. But after the reboot I noticed that my SD (exFAT) was shown as "corrupted" even though it was working perfectly fine before I flashed the recovery. I tried flashing the normal TWRP again from both, the app and the recovery itself but it didn't solve the problem.
I even clean flashed the ROM I was using but no luck. What it's weird is that both recoveries recognized my SD card. Also, the ROM recognizes other SD card (exFAT) but not the original I was using.
Does anyone know how to fix this? Please help.
You really shouldn't use apps to flash stuff. Only use TWRP. Recovery apps cause more problems than anything.
Take the card out, format it on your PC, boot into system and set it up again. Hopefully it's not completely dead, but I've heard plenty of stories of Android phones corrupting SD cards randomly. That's probably why no Google phones come with SD card slots--SD cards are unreliable even as portable media storage.
Related
The sd card works with the system, and I can mount it on the computer, but clockworkmod won't work if I try to do anything that would use it. It just says can't mount SD card. I have tried to use it several times, and I have rebooted many times. But no matter what I do, including formatting the sd card, and reflashing the recovery. I don't know why it won't work though.
Easiest thing to do would be to flash Amon-Ra's recovery. Generally considered the better choice for the Eris. If you aren't sure how to go about this, just use Rom Mananger. There is a free and paid version. I'm not sure if the free version has the flash new recovery, but think so.
Fixed
I tried both, and neither was working. I finally fixed it by formatting the sd card with the phones option, instead of with my computer.
Hi guys,
I can't work out why but when I go to wipe all settings then install custom rom from zip file in cmw recovery, it completes normally but after the reboot it just stays on the android bot. I went back into recovery and managed the phone through usb to my PC & saw that in the phone storage there was nothing where there is obviously supposed to be boot files. I have installed this custom rom before & it has been no problem. I also have tried a few other roms (all that i've tried before & they all work) and the same thing happens. I have found one rom that worked strangley and when I manged the phone on my PC i saw that it has placed the boot files on the sd card (not the phone storage).
how can i fix this.
i am very new to rooting so please no complicated talk
can someone not help? this is a big issue.
ill try and explain the problem in more detail below...
i have been messing with my phone lately using CMW TOUCH to wipe my data then install rom from zip. everything was going great until now.
i want to install a rom (that i have installed before.so i know its compatible with my phone), i go through tge same procedure of wiping data then installing from zip.all goes the way it should with it telling me its installing from zip, after a while it tells me to reboot the phone. when i do all that happens is it stay on the green android bot for 1 min then reboots. i went into CMW TOUCH to connect phone to pc & found out that it installed nothing, nothing on the phone storage and on the sd card except the custom rom.
i have tried this with few other roms all with the same results.
NOW...
ive managed to find a rom that will install so it is functional all except recently after a reboot it has stopped detecting the sim，weird.
i connected the phone to my pc to find that all boot files are stored on the sd card not phone storage like it used to.
i had an idea that i will try later today and that is to move the custom rom over to the phone storage from the sd card. remove the sd card during install. maybe that will force the install to use the phone storage for the boot files
will let you know the outcome
jamos
i have just tried to install the rom with the sdcard removed from phone & the same thing happened. even though during the installation it tells me that it is formatting system then installing it installs nothing to the phone storage.
When 2.7.0.1 came out, I tried that, but it wouldn't load any non-sammy firmware, so I reverted back to 2.6.3.1. When 2.8.0.1 came out, ROMs would install fine, but my MicroSD card wasn't recognized in any ROM reliably. I have it formatted in FAT32 for compatibility across ROMs. However, with 2.6.3.1, I have no issues at all with the MicroSD card, or installing any ROM. Why is this? Does anybody else have this limitation? Is there a way to fix it, so I can update to the latest TWRP. I also tried it with PhilZ Touch 6.43.x, and it doesn't even recognize my SD card. CWM does, but I prefer TWRP over CWM.
For me it's working fine: 2.8.0.1 and the previous version, too. Did you try to format sdcard in TWRP (after saving files of course)?
rp158 said:
For me it's working fine: 2.8.0.1 and the previous version, too. Did you try to format sdcard in TWRP (after saving files of course)?
Click to expand...
Click to collapse
TWRP recognizes it fine, it's just that no ROM I load on the phone with TWRP 2.8.0.1 recognizes it. Sammy ROMs say it's a 415MB MicroSD card, and says "Ready to remove" upon starting up. There is no way to get it to recognize the 64GB card that I have in there. AOSP ROMs simply don't recognize it at all. However, once I downgraded to 2.6.3.1, every ROM recognizes it flawlessly.
Recovery is the last place, I should suspect any reason for this behaviour. Sorry, no idea. Did you re-format the card with TWRP and computer?
If it's not accepted 100%-correctly in your roms, buy another one. Seems risky for me, to use something weak at this place. Downgrading TWRP is useless.
I was running Jasmine 5.0 with the 5.0.1 update, had no issues, was running perfectly with no FC's, no bugs, and I knew there was about to be a 5.0.2 update.. So I decided to prep for the update and create a backup in TWRP and have it saved to the ext-sd. My phone was connected to the computer, charging, and I rebooted into recovery, created a backup and when it was almost finished it went to backup the boot image, it said it failed. So I wiped caches, and rebooted just fine. I then downloaded the 5.0.2 update, and when I went to move it from the computer to the ext-sd card, I noticed that it didn't recognize my external sd card anymore. Both the computer and multiple file explorer apps on my phone can't read my ext-sd card anymore. But the weird thing is, when I am in recovery, TWRP recognizes my external sd card and even let me restore a backup perfectly.. (so it's not corrupt) So I then tried to factory reset, format data and restore a backup from my external sd card, which worked and rebooted just fine. But both my phone and computer still don't recognize my external sd card.. I have tried flashing the sd card fix permissions file and still no luck.. If anyone has any pointers or help, please let me know. I have a 64gb sd card that has all my important and needed ROOT information for the slight chance that I bootloop or softbrick my phone.. All information needed is on it!
Thanks for the help, if you took the time to read this I greatly appreciate it.
pahlerc1 said:
I was running Jasmine 5.0 with the 5.0.1 update, had no issues, was running perfectly with no FC's, no bugs, and I knew there was about to be a 5.0.2 update.. So I decided to prep for the update and create a backup in TWRP and have it saved to the ext-sd. My phone was connected to the computer, charging, and I rebooted into recovery, created a backup and when it was almost finished it went to backup the boot image, it said it failed. So I wiped caches, and rebooted just fine. I then downloaded the 5.0.2 update, and when I went to move it from the computer to the ext-sd card, I noticed that it didn't recognize my external sd card anymore. Both the computer and multiple file explorer apps on my phone can't read my ext-sd card anymore. But the weird thing is, when I am in recovery, TWRP recognizes my external sd card and even let me restore a backup perfectly.. (so it's not corrupt) So I then tried to factory reset, format data and restore a backup from my external sd card, which worked and rebooted just fine. But both my phone and computer still don't recognize my external sd card.. I have tried flashing the sd card fix permissions file and still no luck.. If anyone has any pointers or help, please let me know. I have a 64gb sd card that has all my important and needed ROOT information for the slight chance that I bootloop or softbrick my phone.. All information needed is on it!
Thanks for the help, if you took the time to read this I greatly appreciate it.
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=nextapp.sdfix
My ext. SD card has stopped being recognized only by TWRP. It is still fully functional for all other apps I use. I have tried 3 different SD cards, all formatted to fat32, and all show the same behavior. I have TWRP 2.8.5.1 installed and have tried reverting to previous versions that worked before but they too now are not recognized by TWRP. I have no idea what I did that messed up TWRP but doing nandroid backups using a OTG connector is getting old. What could prevent only TWRP from using the SD card? In TWRP I can't even select the ext. SD circle - just internal storage or OTG storage. I am running SkyDragon 2.0.1
One thing you can try is go to Google play store and get TWRP manager app. After you install it go to settings and at the bottom you will see where you can apply an SD card patch. Worked for me.
Thanks for the suggestion. Unfortunately, that choice is grayed out and says it is already done/not needed. This one really has me stumped.