Related
Fat fingers the touch recovery......I just killed the internal SD,
Can I just reinstall ROM ? or do I need to do something else, first...
I tried to reinstall rom from external but stuck on boot animation, but not boot looping.
Thanks
Ignore!
Its almost like it cant find the internal card.
I tried to instal from internal SD...just to see if I can see any directories
and say no files found, and kicks me out.
When I do mount USB storage, only my EXT shows up, no internal no longer pops up.....am I screwed ?
How can I confirm my internal SD card is mounted/unmounted properly.
Thanks for any help
Can you get into recovery or download mode?
If you can get into download mode I would probably just reflash stock firmware and start over.
I tried that, I did ODIN to stock, it loaded the bootloader, but was stuck on boot loops again.
As far as I can tell, phone isnt seeing the internal SD card. Or I am missing the steps to make the phone see it via clock work.
I can access CWM, and DL mode.... in CWM, I can do mount USB, only my EXT shows up.
I format the internal sd(emmc) before every rom flash. Just install rom from external sd card. There is nothing left on the emmc, you wiped it
I think I m hosed....
I think something went wrong with format.
I tried to reinstall ROM, and during install
error: cant mount csdard.adnoird.secure etc...
what version of cwm?
It touch clock work mod recovery. v.5.8.1.3
Error message is
Formatting /sdcard/.andoird_secure...
Error mounting /sdcard/.android_secure!
Question, are able to mount and see internal SD, after the format emmc via usb storage on PC ? Right now only the EXT shows up for me if I USB mount
Ptrout said:
It touch clock work mod recovery. v.5.8.1.3
Error message is
Formatting /sdcard/.andoird_secure...
Error mounting /sdcard/.android_secure!
Question, are able to mount and see internal SD, after the format emmc via usb storage on PC ? Right now only the EXT shows up for me if I USB mount
Click to expand...
Click to collapse
I don't use that recovery. I use 5.8. I don't use internal to do anything, I always use external to flash from and store my important stuff. After a while of flashing things the emmc gets jammed up with nonsense.
Just use 5.8 touch, the have to mount and put hidden process folders in that version you have sucks.
Any chance you can link me to the recovery you use, I want to make sure I have the same one.
Thanks you again for the help. Its very appriciated
Ptrout said:
Any chance you can link me to the recovery you use, I want to make sure I have the same one.
Thanks you again for the help. Its very appriciated
Click to expand...
Click to collapse
I'll give you a direct download of the one I personally use...Hold on a second
Ok here it is, flash it in odin. Put it in pda and make sure repartition IS NOT checked
http://d-h.st/Rxr
You rock....
Im back up, wow guess CWM makes a difference
Ptrout said:
You rock....
Im back up, wow guess CWM makes a difference
Click to expand...
Click to collapse
Theres a bit of messing around you have to do with that version you had. I don't use it, but there are instructions in his thread for getting it to work. I just don't like messing with all that dumb ****.
xcrazydx said:
Theres a bit of messing around you have to do with that version you had. I don't use it, but there are instructions in his thread for getting it to work. I just don't like messing with all that dumb ****.
Click to expand...
Click to collapse
Awesome job xcrazydx, helping this guy out!!
Good to see a potential train wreck that I'm not part of, get fixed so quickly & expertly!!
Just curious, what's the difference between the two versions of CWM Touch, I'm wondering because I am also using 5.1.8.3? Is it the recovery image, or is this Touch the one developed on xda?
Sent from Down The Rabbit Hole, using Tapatalk 2.
shaggyskunk said:
Awesome job xcrazydx, helping this guy out!!
Good to see a potential train wreck that I'm not part of, get fixed so quickly & expertly!!
Just curious, what's the difference between the two versions of CWM Touch, I'm wondering because I am also using 5.1.8.3? Is it the recovery image, or is this Touch the one developed on xda?
Sent from Down The Rabbit Hole, using Tapatalk 2.
Click to expand...
Click to collapse
The 5.8 is actually a hercules version for the tmo variant. The sk8er 5.5 or whatever it is, is a version adapted specifically for the rocket, and supposedly it performs the wipe and fix functions correctly. As long as you set it up right and put the hiddenprocess folder and mount sd every time you use it. Last I knew it still won't see both sd cards at the same time. I just don't like dicking around with all that stuff.
Sk8er could probably give you a better explanation of them, I think it even mentions it throughout his thread. I have no problems with the 5.8 version and I couldn't recommend the OP on how to navigate the version he had because I don't use it. So I just moved him to the version I use. Lol
i used 5.8.1.3 and have never had any problems.... i even wipe emmc between flashes. should i not be using this one? how can i get the other?
OFWGKTADGAF said:
i used 5.8.1.3 and have never had any problems.... i even wipe emmc between flashes. should i not be using this one? how can i get the other?
Click to expand...
Click to collapse
I use the same one you have, it's fine.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Since he had his problem solved, and I see xcrazydx here, I want to ask how is the lte in Hammond? I've been working in Texas plus I got throttled for the month. I heard it doesn't reach Amite yet.
jeff210 said:
Since he had his problem solved, and I see xcrazydx here, I want to ask how is the lte in Hammond? I've been working in Texas plus I got throttled for the month. I heard it doesn't reach Amite yet.
Click to expand...
Click to collapse
It's decent. I get around 30mb/s most of the time
Problem when I reboot my phone the internal SD is not available only the external micro-SD. I remove the micro-SD and then I can see my internal SD. I am beginning to think my Infuse is on it's last leg. Good thing I can upgrade on 1st January.
I have tried Wipe Cache Partition and Advanced/Wipe Dalvik Cache. No help. This is the second time, thought I had it fixed by returning to stock then back to CM10 4.2 all was well then I saw a post about the new camera that I didn't have yet so I flashed it. Now I am back to SD problem.
If anyone has an idea what is causing this, other than me. I would greatly appreciate it.
Does anyone have a suggestion on how to fix or advise on new phone to get?
Thank you!
swub1
Here is my boot.log contents.
Wed Dec 5 00:35:21 GMT 2012
umount: can't umount /sdcard: Invalid argument
cpio: dev not created: newer or same age file exists
cpio: proc not created: newer or same age file exists
cpio: sys not created: newer or same age file exists
cpio: system not created: newer or same age file exists
1263 blocks
Wed Dec 5 00:35:21 GMT 2012
Also I noticed that the date time stamp on microSD says 31 Dec 69
The above is the same with it working or with it not so thats not the problem and it doesn't help to solve it.
I have found that as long as I don't have to restart my phone when it is working it will remain working. If I think I have a reason to reboot I must make sure I really want to do this.
As the work to get it straight involves remove micro-SD, wipe/format reinstall of ROM and GApps and then restore enough to edit build.prop for tweaking lockscreen powerdown install micro-SD then powerup to restore rest of the apps.
If anyone knows what might be causing this I would really appreciate it. Even if you could point me to the log file to look at that might give me a clue that would be very nice.
swub1
If it works with out microsd just don't use one. 14 gigs is plenty. Otherwise maybe format the microsd? Or try a full stock wipe and see if it all comes back.
Sent from my SGH-I997 using xda app-developers app
cpio I believe means copy in and out.
Since phone works without micro-sd and fails with it try a new micro sd or a different rom.
As for the date you mentioned, it is not unusual to find files with dates that are years in the past. Upgrade? If you are staying with AT&T pick 3-5 phones from their website that based on specs and price meet you needs and spend some hands on time with each. No one can make a better decision as to your next phone than you. Well, maybe bigjoe could...
USB Storage unmounts?
swub1 said:
Problem when I reboot my phone the internal SD is not available only the external micro-SD. I remove the micro-SD and then I can see my internal SD. I am beginning to think my Infuse is on it's last leg. Good thing I can upgrade on 1st January.
I have tried Wipe Cache Partition and Advanced/Wipe Dalvik Cache. No help. This is the second time, thought I had it fixed by returning to stock then back to CM10 4.2 all was well then I saw a post about the new camera that I didn't have yet so I flashed it. Now I am back to SD problem.
If anyone has an idea what is causing this, other than me. I would greatly appreciate it.
Does anyone have a suggestion on how to fix or advise on new phone to get?
Thank you!
swub1
Click to expand...
Click to collapse
your post is the closest example to the SAME problem i am having so i will see if we are experiencing the same thing.
Im running Scott's 4.2.1 Unofficial CM10 - 12/02 build and ever since the 11/30 build, my internal ~14GB sdcard (called USB Storage when i look under system settings / storage) will not mount. the 2GB "internal" Storage and my 64GB External are always visible.
whats strange, is that when i reboot into recovery, i can still get all the data in this "sdcard" partition, it just will not mount when booted.
When i 1st boot from a new flash, its there, but after a reboot (and every reboot after that) it shows for a split-second, then disappears.
I come into this thread and seen it may have something to do with my External SD, i tried it removing the External SD, rebooted, and sure enough, it brought back my internal SD.
i shut down, re-inserted my External SD and powered up, and the USB Storage did NOT disappear but i cant leave well enough alone, so I rebooted 1 more time... POOF... USB Storage GONE....
How could the External SD have such an impact on the mounting of the Internal SD?
In Scott's thread he mentions that external (micro) sd should be removed before flashing the rom... don't know if that is the case, just sayin'.
Pony Express said:
In Scott's thread he mentions that external (micro) sd should be removed before flashing the rom... don't know if that is the case, just sayin'.
Click to expand...
Click to collapse
I have flashed & reflashed with and without, no change. I have reformatted the External SD, no change.
I think i have isolated the issue to the physical presense if the External SD, but this is not an issue with the 11/4 build. I just go back to 4.1.2 till the next release
Downgrading back to 11/04 now
I am downgrading to see if that fixes it will let you know. Did it work for you?
Some one had a point. How is it not available? No media can be seen. Or is it non existent in root explorer. PR under system settings> storage.
If its the first it might be a .nomedia file in the root directory.
Sent from my SGH-I997 using xda app-developers app
swub1 said:
I am downgrading to see if that fixes it will let you know. Did it work for you?
Click to expand...
Click to collapse
After downgrading back to 4.1.2 of CM10 my problem goes away. Another thing that I noticed is that the default APN's are now editable and I can delete them as well. While on 4.2 the only thing I could do was create a new one and set it to be the one in use. I guess part of the system is read only. Trying to save us from messing something up.
swub1
Pony Express said:
In Scott's thread he mentions that external (micro) sd should be removed before flashing the rom... don't know if that is the case, just sayin'.
Click to expand...
Click to collapse
When first told to remove external micro sd prior to flash I did just that. Later I supposed that I had nothing to loose so I tried leaving it in. Didn't see anything go wrong so I thought it was just a cover my a$$ thing.
Skwerl23 said:
Some one had a point. How is it not available? No media can be seen. Or is it non existent in root explorer. PR under system settings> storage.
If its the first it might be a .nomedia file in the root directory.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
Well for me, not available means not mounted & unmounable, the sdcard directory can be seen, but it empty through root explorer.
the "other way in" through Storage/Sdcard0 shows the dame, nothing, REMOVE the external SD, the internal SD (called USB Storage in settings/storage) Mounts in reboot. .nomedia is not the issue as when the External SD is present, i can play media (from the External SD, but the camera and other apps that rely on the internal SD for storage, can not function.
When i reboot into recovery, i can see and access all the files (typically where the flashable files reside when i drag them over from my PC) both internal and external, and when i reboot, the MOMENT the unlock screen appears i dash over to settings/storage and the internal drive appears, but collapses in a less then a second. (as unmounted)
swub1 said:
I am downgrading to see if that fixes it will let you know. Did it work for you?
Click to expand...
Click to collapse
yes, returning to the 11/4 (4.1.2) ROM I do not experience this issue.
I tried scott.hart.bti 4.2.1 12/11
Went up to try 4.2.1 12/11 - No difference - The only thing I was able to do in this one was delete unused APN and edit save new one.
Wish I knew how to program and spot the differences in the code somewhere. I'd really like to stay on 4.2.1 but without my micro-SD it seems like a waste.
I have not had issues with 12/12, thought I'd share my process: wipe data/factory, wipe cache, wipe dalvik (advanced), format system (mounts and storage), install ROM, wipe dalvik, install Scott's gapps, reboot. I also don't auto restore apps. There are still compatibility issues with some apps and 4.2
hiya i wonder if any1 can help!
basically my phone was telling me my sd card had been removed (no big deal i thought, this seems to happen to my phone from time to time since running this ROM (bruce2728's cm10)).
i can usually either remove the sd card and put back in, or the same with the battery to get it working again. but no matter how many times i try it wont work. also when using this ROM (and before this problem) every time that i try to enter storage from the settings menu, settings force closes.
so completely out of ideas i tried doing a wipe and trying again. now u see im fairly new to all this and that seems to get touted as a way to fix some things, so i thought id give it a go.
but now my phone wont get past the white with green HTC logo, its been sat like that for about an hour! and in recovery it just says that it cannot mount sd card!!
i feel im firmly up **** creek. is there any way to fix this? perhaps a way to flash a ROM without using sd card to a phone that wont boot up?
i feel i might need to flash a new bootanimation.img as i changed this from the default in the ROM, could i also do this without an sd card or a phone that wont get past HTC logo?
i hope there is someone out there that can help!
thank you in advance,
Max
I would install ARHD from Mike1986 it seems to help resettle the device running a sense ROM. Make sure you follow his instructions using ext4 and super wipe
Sent from my HTC Sensation using xda app-developers app
if you are S-ON enable smartflash first from 4ext and then flash the rom
rzr86 said:
if you are S-ON enable smartflash first from 4ext and then flash the rom
Click to expand...
Click to collapse
yeah thats what i always do but because i cant access my sd card i cant flash the ROM which is saved on it. it just keeps saying cant mount /sdcard
Max792 said:
yeah thats what i always do but because i cant access my sd card i cant flash the ROM which is saved on it. it just keeps saying cant mount /sdcard
Click to expand...
Click to collapse
The recovery won't pick up the SD card? That is very odd. Do you have any others around to test with?
tapped out from my sexy sensation XE
heavy_metal_man said:
The recovery won't pick up the SD card? That is very odd. Do you have any others around to test with?
tapped out from my sexy sensation XE
Click to expand...
Click to collapse
I'm assuming you've tried pulling the battery, unseating the sd card, reseating it, putting battery back, and going to recovery right?
If that doesn't work I'd suggest trying to read the sd in card in a PC... is it readable there?
All in all you can get to recovery so you arent that bad off, just need to figure out what's up with the SD.
Yes I can view my SD card on both my PC and my tablet :/ but when I boot into 4ext it says problem mounting SD card, may take longer without. Then when 4ext loads I can't manually mount SD or browse for zip file. You think this is more likely a hardware issue with my sensation?
Sent from my Transformer Prime TF201 using XDA Premium HD app
Max792 said:
Yes I can view my SD card on both my PC and my tablet :/ but when I boot into 4ext it says problem mounting SD card, may take longer without. Then when 4ext loads I can't manually mount SD or browse for zip file. You think this is more likely a hardware issue with my sensation?
Sent from my Transformer Prime TF201 using XDA Premium HD app
Click to expand...
Click to collapse
On your PC, copy all your files off your SD card, format your SD card (makes sure the filesystem is set to fat32), and then just put 1 file on it, a ROM, and see if the recovery detects it. If that doesn't work then you can always try using a different SD card.
android1234567 said:
On your PC, copy all your files off your SD card, format your SD card (makes sure the filesystem is set to fat32), and then just put 1 file on it, a ROM, and see if the recovery detects it. If that doesn't work then you can always try using a different SD card.
Click to expand...
Click to collapse
Okay thanks I will try this, but I think its the SD card tray that has gone because I just squeezed it and it was able to mount, however only for a second then 4ext rebooted
Sent from my Transformer Prime TF201 using XDA Premium HD app
Max792 said:
i can usually either remove the sd card and put back in, or the same with the battery to get it working again. but no matter how many times i try it wont work. also when using this ROM (and before this problem) every time that i try to enter storage from the settings menu, settings force closes.
Click to expand...
Click to collapse
This isn't part of your SD card problem. This was a ROM bug that was fixed in the Jan 9th update. Any use of the storage menu from the settings on the late December to Jan 6th builds caused a FC.
So if you are using one of those builds, don't factor in th esettings FC in your diagnosis of the problem.
SD card ejections were also an issue on the Dec 21 - Jan 3rd builds if I recall correctly. I had one day where the SD card would just unmount and refused to remount. It was a problem experienced by only a handful of people and seemed to be very limited. Though if you can't mount in recovery than that's probably not the issue.
Also, you said you could press the SD card into the slot and it mounted for a second...
2 things on that note.
First, your SD card might be the problem. Maybe the contacts are worn out. Take a lcose look at it and make sure it looks okay. No corrosion, etc...
Second, the metal housing around the SD card...that can be mashed in slightly to put more pressure on the card. Take the card out and press the middle of that housing in. It could create enough force to hold the card in more securely. Be VERY careful with this option though.
Also, did you make sure another SD card got the same problem? If another card works, then your card is just f'ed.
Skipjacks said:
This isn't part of your SD card problem. This was a ROM bug that was fixed in the Jan 9th update. Any use of the storage menu from the settings on the late December to Jan 6th builds caused a FC.
So if you are using one of those builds, don't factor in th esettings FC in your diagnosis of the problem.
SD card ejections were also an issue on the Dec 21 - Jan 3rd builds if I recall correctly. I had one day where the SD card would just unmount and refused to remount. It was a problem experienced by only a handful of people and seemed to be very limited. Though if you can't mount in recovery than that's probably not the issue.
Also, you said you could press the SD card into the slot and it mounted for a second...
2 things on that note.
First, your SD card might be the problem. Maybe the contacts are worn out. Take a lcose look at it and make sure it looks okay. No corrosion, etc...
Second, the metal housing around the SD card...that can be mashed in slightly to put more pressure on the card. Take the card out and press the middle of that housing in. It could create enough force to hold the card in more securely. Be VERY careful with this option though.
Also, did you make sure another SD card got the same problem? If another card works, then your card is just f'ed.
Click to expand...
Click to collapse
cheers mate helped a lot. i did actually see that kind of talk in the thread but kind of passed over it because it hadnt affected me... yet!
if it was a ROM bug i feel im totally f'ed as i cant flash a new version due to the inaccessible sd card.
yeah ive been doing this exact mashing you speak of lol, hopefully it will work or i am completely out of ideas :\
cheers everybody for your help tho guys really appreciate it
Max792 said:
cheers mate helped a lot. i did actually see that kind of talk in the thread but kind of passed over it because it hadnt affected me... yet!
if it was a ROM bug i feel im totally f'ed as i cant flash a new version due to the inaccessible sd card.
yeah ive been doing this exact mashing you speak of lol, hopefully it will work or i am completely out of ideas :\
cheers everybody for your help tho guys really appreciate it
Click to expand...
Click to collapse
Find the exact rom you were on and take the boot IMG out of it. Wipe your data and cache and then boot to fastboot. With the boot.IMG
In your adb folder do fastboot boot boot.IMG and see if it boots into the rom.
Tapped out from my sexy nexus 7
OK... I searched on this one.. and probably someone will point me RIGHT to the thread as soon as I post this...
Keep in mind that I am a NOOOOOOOb.... and probably don't belong in here... but hey.... everybody has to learn
so... I downloaded and flashed the SD/ Internal Memory swap... and was thinking of flashing an updated ROM to play with some more... my question is... do I copy the ROM zip to my SD card which NOW reads as my internal storage? OR do I copy it to the Internal Storage because that now shows as my SD card??
Or... should I scrap the whole thing, and flash it back to nothing, fresh install on ROM, and then reflash the SD card / Internal storage swap?
Thx for any help
I'm assuming you flashed the swap that @InkSlinger420 graciously provided for us? If so, it's my understanding that the recovery doesn't recognize the swap, just the rom. So if you put it on internal (which WAS external) when you go into recovery it'll be external again, if that makes sense. I would say put the rom on your now internal, then go into recovery and see where it is placed. Either way, recovery will flash it regardless of where it is. Just make sure (and always make sure) you have a backup of what you have now just in case. I can't stress that enough. I working backup is critical when doing the modding game! Also, are you using Philz recovery? If so, for the love of pete, backup your efs partition. Also very, VERY, important!
Sent from my GT-P5113 using XDA Premium 4 mobile app
Wholeheartedly agree...backup or kick yourself later..?
Sent from my Nexus 7 using Tapatalk
njstein said:
I'm assuming you flashed the swap that @InkSlinger420 graciously provided for us? If so, it's my understanding that the recovery doesn't recognize the swap, just the rom. So if you put it on internal (which WAS external) when you go into recovery it'll be external again, if that makes sense. I would say put the rom on your now internal, then go into recovery and see where it is placed. Either way, recovery will flash it regardless of where it is. Just make sure (and always make sure) you have a backup of what you have now just in case. I can't stress that enough. I working backup is critical when doing the modding game! Also, are you using Philz recovery? If so, for the love of pete, backup your efs partition. Also very, VERY, important!
Sent from my GT-P5113 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Philz recovery ... no... I guess I should back up? It's kind of a spare phone that I have been tinkering with just to try and learn... so I figured worst case scenario, I could reformat, and start fresh I'm probably wrong about that too?
Anyway, I went ahead and loaded the swap that yes @InkSlinger420 very graciously gave out.... so... here is what happened...
I loaded the new ROM onto the SD card (which showed as internal memory) Flashed it... and it ran perfect, it UNDID the Swap, so I had to reflash that file as well... now we are back to where we were, with a new ROM, and no backup maybe I will go check out Philz...
Philz is wise as @njstein had said backs up your efs partition that holds all the identifiers for your device to receive service and such.and, yes, if you flash a new ROM, you will need to reflash the swap zip, but as I have been messing with it,it still keeps your apps and such so after you flash ROM,gapps,and swap, your app data will still be there for apps/games..just need to re get them from play store manually or automatically, also may want to get a good cleaner for your device such as SD maid or clean master to help keep up with removing residual leftovers as well..
Sent from my Nexus 7 using Tapatalk
I just wanted to post this here in case it might help someone.
If you have ever had the SD card corrupted issue after installing a ROM or an update the first thing you should check is the kernel. I have found that every time I've had this issue I could still see the SD card in TWRP you couldn't figure out what was going on. I have since learned that the issue usually stems from the kernel. So take and reflash your current kernel or try a new kernel. Hope this helps someone good day
I reformatted my card to FAT32 which solved those issues for me. Be sure to backup anything before doing that as it reformatting will erase the card obviously.
AngryManMLS said:
I reformatted my card to FAT32 which solved those issues for me. Be sure to backup anything before doing that as it reformatting will erase the card obviously.
Click to expand...
Click to collapse
Why format the SD card if just flashing another kernel will fix the issue lol
shadavis08 said:
Why format the SD card if just flashing another kernel will fix the issue lol
Click to expand...
Click to collapse
I could think of a reason, that being (and this is an Android-wide rule) the kernel dictates support for file formats.
If you're using a kernel that has better features than a stock one on a ROM (let's say Gamma vs the stock LineageOS kernel in this case) the better kernel might not support the file-system format the stock one does. It comes down to support for what file-systems a kernel dev chooses to implement.
At least personally, I'd rather move 64GB off my microSD card, format it and move it all back on if it means I get to keep using a better kernel.
Your thought process is flawed. Since the source of the issue is the stock kernel. Geesh
Thinking that it's easier to remove everything and then put it back rather than, simply flashing a different kernel than the stock kernel, first to see if that is the issue, by the way is flawed.
shadavis08 said:
Your thought process is flawed. Since the source of the issue is the stock kernel. Geesh
Click to expand...
Click to collapse
shadavis08 said:
Thinking that it's easier to remove everything and then put it back rather than, simply flashing a different kernel than the stock kernel, first to see if that is the issue, by the way is flawed.
Click to expand...
Click to collapse
I'm not entirely sure what makes my thought process flawed. If the issue is the stock kernel, then the stock kernel likely doesn't support the format the SD card is using, in which case, like you said, swapping kernels would fix that.
I don't disagree with you there.
I also wouldn't call moving everything off, formatting and moving everything back on is a flawed process either.
If I have to choose between massive screen retention using a stock kernel on the V20, or little to no screen retention and better performance by using a custom kernel like Gamma, Gamma is going to win every-time. Even if I have to spend 20 minutes moving stuff off, formatting my SD card and moving it all back on.
It might not be a process that's worth it for some people, but it's by no means flawed.
Your "flash a different kernel to see if that's the issue first" is like me saying I'll plug my desktops Windows 10-formatted SSD into my Windows 7-formatted laptop and see if it'll work.
It could, but I run the risk of it not working properly, which is something you want to avoid in most cases.
And I did say
At least personally
Click to expand...
Click to collapse
which, again, doesn't make my process flawed.
Redline said:
I'm not entirely sure what makes my thought process flawed. If the issue is the stock kernel, then the stock kernel likely doesn't support the format the SD card is using, in which case, like you said, swapping kernels would fix that.
I don't disagree with you there.
I also wouldn't call moving everything off, formatting and moving everything back on is a flawed process either.
If I have to choose between massive screen retention using a stock kernel on the V20, or little to no screen retention and better performance by using a custom kernel like Gamma, Gamma is going to win every-time. Even if I have to spend 20 minutes moving stuff off, formatting my SD card and moving it all back on.
It might not be a process that's worth it for some people, but it's by no means flawed.
Your "flash a different kernel to see if that's the issue first" is like me saying I'll plug my desktops Windows-formatted SSD into my Linux-formatted laptop and see if it'll work.
It could, but I run the risk of it not working properly, which is something you want to avoid in most cases.
And I did say
which, again, doesn't make my process flawed.
Click to expand...
Click to collapse
Wow really dude? I was giving some advice for people that could potentially keep them from losing all their data on the SD card. By simply flashing a different kernel before just wiping a card when the android system throws up an error saying sd card corrupted. You are only here to argue and I would like you to stop. Thank you for over thinking the situation and good day.
shadavis08 said:
You are only here to argue and I would like you to stop. Thank you for over thinking the situation and good day.
Click to expand...
Click to collapse
That's precisely the opposite of the reason why I'm here.
I was here to point out the benefits and potential downsides to doing it either way, but okay.
I don't get t flash kernels on my variant but if ever i saw a corrupt sd card message i'm wondering whether just deleting the android folder (on the card say on a PC) and then re-inserting the card would be enough.
You could simulate this just by pulling the card without un-mounting it and then reinserting and android thinks the card is corrupt
I don't know. I don't have a computer to test with lol
One Twelve said:
I don't get t flash kernels on my variant but if ever i saw a corrupt sd card message i'm wondering whether just deleting the android folder (on the card say on a PC) and then re-inserting the card would be enough.
Click to expand...
Click to collapse
This shouldn't be the case. I say shouldn't because I'm not sure how Android does it exactly, but telling you the SD card is corrupt either means it is, or it can't read the file system itself, not the files.
Deleting the Android folder probably won't do anything, that folder just has data for apps and such that want to store things on the SD card.
I'd imagine you could achieve the same thing with internal storage if you formatted it weirdly from TWRP or something.
Redline said:
This shouldn't be the case. I say shouldn't because I'm not sure how Android does it exactly, but telling you the SD card is corrupt either means it is, or it can't read the file system itself, not the files.
Deleting the Android folder probably won't do anything, that folder just has data for apps and such that want to store things on the SD card.
I'd imagine you could achieve the same thing with internal storage if you formatted it weirdly from TWRP or something.
Click to expand...
Click to collapse
My mistake not Android folder but lost.dir folder needs to be deleted
Back on nougat this happened to me twice on the same card. Formatted once and it happened again and this was back before I tried any custom ROMs or Kernels. Was purely stock rooted with SuperSU so it was definitely something screwy with LGs kernels
Kinda fuzzy but I think it happened first on 10J for TMobile and then again on 10K for my H918
I've not had any problems with my sandisk extreme 128GB for over a year now. On N.
I don't take the card out and swap it about, its been in all this time.