Related
The SD card slot on my phone seems to be broken. I've tried multiple SD cards and none of them seem to get read, so I've concluded that it must be the phone.
Im trying to unroot it so I can send it to verizon for a replacement. I was kind of depending on this method to do it:
http://forum.xda-developers.com/showthread.php?t=792026
but obviously I need the use of the SD card. So I'm kind of in a pickle.
Is there any other way to do it? Something that doesnt need an SD card?
The "Official" 2.1 RUU Utility (= Leak-V3) requires no SD Card
MultiUpload.com - RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed _with_driver.exe
It runs on your Windows PC.
Charge your phone well (say, > 80%)
Turn it off
Plug it in to your PC (still off)
Start the Eris up in fastboot mode (Send+End)
Run the above (HTC) utility - follow the instructions on the screen.
Thanks, man. Just ran it. Worked perfectly.
Just got to install a few apps before I take it in so that it doesn't look too barebones >_>
This is really strange. I just put in the SD card, to see if it was still broken and it magically worked again @[email protected]
I tried with the same SD cards that I used when I was rooted and they all worked as well.
I guess this means I dont have to turn it in, but this is still very strange.
McFluffnStuff said:
This is really strange. I just put in the SD card, to see if it was still broken and it magically worked again @[email protected]
I tried with the same SD cards that I used when I was rooted and they all worked as well.
I guess this means I dont have to turn it in, but this is still very strange.
Click to expand...
Click to collapse
Bummer or Not Bummer? I'm not sure. Nothing like an intermittent problem to give you plenty of confidence.
Well, if you don't take it in, at least you will get more practice at rooting.
If you want to be one of cool kids on the block, you can update the unrooted RUU (= Leak-V3) software to the July 2010 OTA using the honest-to-goodness factory codes. You might want to do this anyway, because it will install the July 2010 HTC radio, if not for the "fun" involved.
Go visit this thread:
Consolidated HTC RUU, Leak, and OTA Downloads
and grab the "4th OTA" which converts 2.36.605.1 -> 2.37.605.4; the file name is
OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip
You rename it to "update.zip", and put it on your SD card in the root folder, then:
- verify the file length and MD5 checksum (of the copy of the file on the SD card)
- charge your phone fully
- power your phone off and boot into recovery mode
(either Vol-Up+End, or HBOOT(Vol-Down+End) -> recovery)
- you will get that screen with the triangle and exclamation point; when that is showing, press Vol-Up+End again, and you will see the stock recovery menu.
- Choose the one that says something about SD:update.zip (or similar)
- Let it run through until it reboots (I can't recall, it may reboot twice).
Then, when you root this, you can take a Nandroid backup - then you will have a Nandroid backup of the July 2010 "Factory" configuration. The "cool kid on the block" part is that almost nobody has ever done this - most Eris rooters were already rooted when July 15-17 rolled around, or if they were stuck not rooted on Leak-V3, they got the OTA automatically. Very few people have actually ever used the factory recovery menu on the Eris. (I have done it just to look at it.)
Cheers
bftb0
McFluffnStuff said:
This is really strange. I just put in the SD card, to see if it was still broken and it magically worked again @[email protected]
I tried with the same SD cards that I used when I was rooted and they all worked as well.
Click to expand...
Click to collapse
Did you happen to partition your SD cards for apps2sd on a rooted 2.1 ROM and then try installing a Froyo ROM? If so, that is an explanation - (most) of the Froyo ROMs will not mount an SD card with more than one partition on it.
If this is the case, and you still want a Froyo ROM, you can backup the contents of your SD card, use Amon's Recovery to partition it again (setting the size of the ext2 and swap partitions to 0 bytes), and you should be ok. If the fact that your SD cards were partitioned was the issue...
Good catch doogald - I just assumed that this wasn't the case because the OP mentioned more than one SD card.
No, I was using a Froyo rom.
Also, I forgot to point out that it wasn't the first time it's happened. The Last time, however, I was able to get it to work again after a reboot. When I did get it to work, half the stuff on the card was missing. Luckily I had it all backed up, so it wasn't too much of a hassle.
This time, I couldn't get it to recognize the card at all, even after several reboots and trying several different cards.
But like I said, it works now. Ill probably re-root it again this weekend when I have the time. Hopefully, things work out differently this time.
Seams to have started just after I S-Off'd my rezound. Took me forever to initially get it working and get cleanrom back onto it, where it immediatly started to reboot randomly after a minute or two, usually under quick/hard loads, it does it every time consistently when I try to Dial or Text someone. I also tried to upgrade to the leaked RUU and rom to fix this, nothing. The stock rom I could dial, but it did reboot once on lock screen. Custom roms reboot consistently. Help?
Did you flash the leak twice?
No, I followed instructions off of theandroidsoul,com rezound ics upgrade page to the 'T' since they supplied download links.
I'd post the page directly but I haven't reached my required post count.
It's a kernel upgrade via hboot, and a shell/rom flash via recovery, so I'm not sure if your expecting a different upgrade meathod.
Which am I expected to flash twice? And what is expected to change?
Check android community site with march 16 story to download rooted version for the leak. It should just be a ph98img.zip. before you do though, have you tried wiping everything in recovery, possibly 2 or 3 consecutive wipes, and then a completely clean install of Scott's stuff again? Also, are you on amon ra?
Edit- it would be the kernel to do twice. When it prompts at bootloader to update, you pick yes and if it doesn't hit all the entries, you have to run it again.b
I flashed the rom and the kernel twice earlier, stock seams to run flawlessly, I can dial, and the phone doesn't reboot Speed Ex 3D like it did earlier, though it plays double screened, weird. Anyway, I'll try flashing some various roms to see what happens.
Good to hear.
Ran into an issue, Stock ICS isn't mounting my SD card, simply says unavailable under storage. HBoot still finds the kernel upgrade, rather annoying when I'm trying to remove it to access recovery.
The format check earlier said Ext4, I assume RUU should be able to handle that. Would be unthinkable that I'd have to flash the GB fix.
have you checked under settings--about phone--software and made sure that it says android 4.0.3? I ran into a similar (maybe same) problem when I first tried flashing the leak firmware. It didn't fully flash correctly, so the first time it said I was still on GB and it could not mount my SD, the second time I flashed the ph98img.zip it said I was on 4.0.3 but still would not mount my SD. So I flashed it once more and everything was fine after that.
What the hell... I just noticed by radio is 1.22, I flashed the leaked radio awhile after the S-Off. Kinda screwy. I removed the external SD card, got into recovery, but when I mount the internal sd to the computer, I can't edit anything. Says full up to 1200kb if i read that right.
Btw, says 4.0.3 under software
SD Card reads normally under CleanRom DE, but still crashes
BAMF Senseless v2 crashes when I try to dial too.
Wait, is it the same sd you had in it when you did the S-off procedure? If so, have you reformatted it? If this is the problem, see sindroidx's how-to in the rezound general forum. If not, it still sounds like your sd card has either been corrupted/misformatted somehow. That's for external. If it is internal SD, see graymonkey44's "S-off is Official!!!" thread. It contains the fix for both, by the way.
swilbert80 said:
Wait, is it the same sd you had in it when you did the S-off procedure? If so, have you reformatted it? If this is the problem, see sindroidx's how-to in the rezound general forum. If not, it still sounds like your sd card has either been corrupted/misformatted somehow. That's for external. If it is internal SD, see graymonkey44's "S-off is Official!!!" thread. It contains the fix for both, by the way.
Click to expand...
Click to collapse
Definately, sounds like your SD card needs to be reformatted. Numerous posts on it , but some have had success just formatting in Windows ( might have to do it more than once to finally get it to show your full capacity) . I used Gparted Live CD to repartition and reformat to fat 32 and it worked great. Whatever your comfortable doing will work, but needs to be reformatted regardless. Also sounds like you should just RUU from scratch after your SD card is fixed , then start over once you know the phone is operating properly.
I RUU'd back to the OTA 2.011 and it fixed some odd issues I was having , now running the Sense 4 roms using the old firmware patch and everything is fine.
I formatted through recovery and RUU after I used a spare SD to install/update. Well this is what I don't get, under other Roms, my SD card mounts fine, but not under Leaked RUU, how ever if I'm on, say cleanrom and mount it to to the computer, windows acts like the external SD needs to be scanned/fixed, how ever I can still open and explore it just fine.
Ig I'll try reformatting my SD once more, then flash some GB kernels/fix
Will it matter if I'm on the GB or ICS bootloader?
sounds like the symptoms of not having the firmware patched.
What patch are you referring to?
In the meantime I'm going to try this kernel and run the GB > ICS fix
http://forum.xda-developers.com/showthread.php?t=1467793
swilbert80 said:
Wait, is it the same sd you had in it when you did the S-off procedure? If so, have you reformatted it? If this is the problem, see sindroidx's how-to in the rezound general forum. If not, it still sounds like your sd card has either been corrupted/misformatted somehow. That's for external. If it is internal SD, see graymonkey44's "S-off is Official!!!" thread. It contains the fix for both, by the way.
Click to expand...
Click to collapse
As I stated, Leaked RUU wont recognize either SD, CleanRom and others recognize both but reboot alot. I tried the internal fix by flashing the ICS Hboot for S-Off last night which changed nothing. I just now flashed a GB Kernel and ran the SD card fix to test with CleanRom and it still freezes/reboots.
-Edit-
Just checked, and it still says 4.0.3 under software. This is such a pain...
Also I can't access the internal SD card from the computer when I USB mount in recovery. It simply opens up blank.
http://forum.xda-developers.com/showthread.php?t=1560363 Sounds just like my problem.
The first guide I followed to upgrade was trash,
this guide has fixed everything:
http://www.teambamf.net/topic/3528-guide-to-install-ics-ruu-and-firmware-windows/
I did a nandroid restore (from this same external SD card). Android (ICS 4.0.3 , Sense 3.6) doesn't recognize the card. A root explorer shows the internal SD card as a folder, but the external SD card as a file of unknown type. The same card is read correctly by AmonRa Recovery, and through a card reader on the 'puter. Has this happened to anyone before?
I tried backing it up, reformatting (FAT32), and recopying, no difference.
Trying to mount it in AmonRa yields :
E: Can't mount /dev/block/mmcblk1p2
(File exists)
Talking to yourself again?
You're not s-off are you? I've seen a thread about an issue with the cards when s-off. It might also have to do with old firmware mixed with a newer ROM. Have you updated to the latest RUU, the global one?
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
Might not have anything to do with it but can't hurt to get updated. Remember, I'm not an expert, I just play one in your threads. And you seemed so lonely in here I had to say something.
Hello? Hello? I thought I heard someone. Anyway, yeah, s-off, and not the latest RUU, but I thought it was the RUU the original ROM was based off. Could be mistaken. Next step IS to take that global RUU and try again, worst case, just start over from scratch.
Here, found this thread since you're s-off:
http://forum.xda-developers.com/showthread.php?t=1615418
feralicious said:
Here, found this thread since you're s-off:
http://forum.xda-developers.com/showthread.php?t=1615418
Click to expand...
Click to collapse
Hmmm... that looks..... risky. I'll try it when I get home tonight. Then if it fails I'll have time to go the new RUU route.
Thanks
So, of course, right after I posted that, I gave it a try anyway.... no go. Card reads/writes fine from recovery, but the Android OS refuses to see it. Back to original plan, re-RUU it tonight.
DIncLover said:
So, of course, right after I posted that, I gave it a try anyway.... no go. Card reads/writes fine from recovery, but the Android OS refuses to see it. Back to original plan, re-RUU it tonight.
Click to expand...
Click to collapse
Before you RUU again, try backing up the card, then reformatting it on your pc then pop it back in. I just remembered that I've read where that's fixed it for a few people.
You need to update to ICS firmware or use the old firmware patch if you're still on GB firmware, otherwise that shouldn't be the problem. What version of hboot are you on? Also what version of AmonRa?
feralicious said:
Before you RUU again, try backing up the card, then reformatting it on your pc then pop it back in. I just remembered that I've read where that's fixed it for a few people.
Click to expand...
Click to collapse
Tried that before.... no go.
mjones73 said:
You need to update to ICS firmware or use the old firmware patch if you're still on GB firmware, otherwise that shouldn't be the problem. What version of hboot are you on? Also what version of AmonRa?
Click to expand...
Click to collapse
HBoot = 2.25 , AmonRa=3.15 .... If I'm s-off, isn't the (ICS) firmware loaded with nandroid restore ?
DIncLover said:
HBoot = 2.25 , AmonRa=3.15 .... If I'm s-off, isn't the (ICS) firmware loaded with nandroid restore ?
Click to expand...
Click to collapse
Nandroid doesn't touch the firmware, you are running ICS firmware though.
mjones73 said:
Nandroid doesn't touch the firmware, you are running ICS firmware though.
Click to expand...
Click to collapse
You can tell that .... how? Through my HBOOT version?
Strangest thing happened last night. During the day I attempted the External SD-card fix linked to by feralicious, to no apparent avail. Last night, though I, out of the blue, saw an android notification that I had a blank SD card ... Do you want to format? I said OK. Afterwards, I went to Settings -> storage, and saw the SD was still unavailable .... rebooted, no change. I shut down the phone and put the SD card in a card reader and saw from my PC there was a sole LOST.DIR folder on the card. I restored my SD backup from PC, thinking maybe my problem is miraculously solved. Upon phone reboot, though, no change. SD card is still unavailable, though it can be seen from recovery. Tonight is (global) RUU night unless any more suggestions?
DIncLover said:
You can tell that .... how? Through my HBOOT version?
Strangest thing happened last night. During the day I attempted the External SD-card fix linked to by feralicious, to no apparent avail. Last night, though I, out of the blue, saw an android notification that I had a blank SD card ... Do you want to format? I said OK. Afterwards, I went to Settings -> storage, and saw the SD was still unavailable .... rebooted, no change. I shut down the phone and put the SD card in a card reader and saw from my PC there was a sole LOST.DIR folder on the card. I restored my SD backup from PC, thinking maybe my problem is miraculously solved. Upon phone reboot, though, no change. SD card is still unavailable, though it can be seen from recovery. Tonight is (global) RUU night unless any more suggestions?
Click to expand...
Click to collapse
Yes. Firmware refers to hboot and radios. Your hboot is the official ICS OTA.
shrike1978 said:
Yes. Firmware refers to hboot and radios. Your hboot is the official ICS OTA.
Click to expand...
Click to collapse
AmonRa nandroid gives the opportunity to backup and restore boot --- doesn't this mean I can effectively change firmware by restoring a different nandroid backup?
DIncLover said:
AmonRa nandroid gives the opportunity to backup and restore boot --- doesn't this mean I can effectively change firmware by restoring a different nandroid backup?
Click to expand...
Click to collapse
No, boot is just the kernel. There's no way to back up and change the firmware on the phone with nandroid.
OK, all good now. Had to re-RUU to the global, then reinstall latest version of ROM, then restore my apps and home screens, etc. Titanium backup was useful.
I still don't really understand how my card became unreadable, but c'est la vie (loose translation : $hit happens)
Hey everyone.
I have been experiencing a huge problem for me, with my p760. I`m on latest PAC version, and about a week ago i had problems with UMS, while copying files from computer to my LG, suddenly the task froze, i couldn't turn off Mass Storage from phone either, so i just unplugged the device after aprox. 6 min of waiting. The result was in phone shutdown. I turnt back on, and tried once more, sadly the same happened, but this time i received a nice present of soft brick. I couldn't even turn my phone on in recovery (thanks to TWRP), i managed to flash CWM through fastboot, then made a factory reset, and phone booted up, but ever since the time, i am unable to copy files to SD card through UMS, and MTP doesn't work at all. So i'm stuck now. I want to reinstall phone, upgrade to new ROM, i know possibilities are just to download a new ROM through phone, but i like the PAC, so do you have any solution or tips to fixing this? Oh, also everytime i connect phone, it shows me that my SD card needs to be scanned for errors, i always skipped, 'til i tried, and no luck. 20min of waiting to tell me, it is all right with SD.
First use an external SD reader to scan for errors and eventually try substituting the SD to see if it's a phone or a SD problem. Second you can always flash a rom from internal SD!
Lamba92 said:
First use an external SD reader to scan for errors and eventually try substituting the SD to see if it's a phone or a SD problem. Second you can always flash a rom from internal SD!
Click to expand...
Click to collapse
I didn't thought about the internal SD, but still a KK disables Internal SD Emulation, i can't copy files to it through PC the "normal" way. How can i copy from PC to Internal SD?
The phone pop-up just said "security updates". No link was provided in the notice or on the "LAST SYSTEM UPDATE" screen.
I haven't looked on Verizon's web pages to see if it's listed there.
Thanks! https://www.verizonwireless.com/support/lg-g3-update/ only says:
Software Version: VS98549A
The current software update gives you the most up to date Android™ security patch on your device.
Click to expand...
Click to collapse
and LG's site doesn't list 49A yet http://www.lg.com/us/support/product-help/CT10000027-1414534794596-software-updates?search=&categoryId=CT10000027&superCategoryId=CT10000003&symptom=&subsymptom=&sort=
roirraW "edor" ehT said:
Thanks! https://www.verizonwireless.com/support/lg-g3-update/ only says:
and LG's site doesn't list 49A yet http://www.lg.com/us/support/product-help/CT10000027-1414534794596-software-updates?search=&categoryId=CT10000027&superCategoryId=CT10000003&symptom=&subsymptom=&sort=
Click to expand...
Click to collapse
I doubt this fixes Dirty Cow. I think it's what was announced not too long ago about the latest Google patches.
https://source.android.com/security/bulletin/2016-09-01.html
iBolski said:
I doubt this fixes Dirty Cow.
Click to expand...
Click to collapse
Yeah I doubt it too.
Well, I took the OTA today. So far, the only issue I had was that it kept ejecting my SD card. A reboot nor power down didn't work, so I allowed it to finally tell me it ejected the card, opened the back with the phone still on, pulled the SD card down to eject it, then pushed it back in and after several reboots, things are working again. Not sure what happened, but it's okay now. The SD card is good as I've verified it via file system checks, so not sure why the OTA caused it to burp like that, but so far, the new OTA is working fine.
I don't know if I can still downgrade. Since this is my daily driver phone, I don't feel like trying to attempt to downgrade back to 10b. My feeling is, this was mainly fixing all the other security issues (minus Dirty Cow more than likely since that is at the kernel level and the kernel is still v3.4 which is dirty cow vulnerable).
Hopefully someone else can test if you can TOT back to 10b.
UPDATE: Hmm. I'm getting sporadic "SD Card has been ejected" messages. It almost appears as if it's not seated tightly enough. But this issue only started AFTER taking the 49A OTA. I've never had this issue before. Going to have to keep looking at what the issue is. When I get home, I'll copy all the data off, reformat it and try again. It almost seems like it's not sitting tight enough in the slot any more (maybe). Not sure if the OTA has something to do with it or it's just coincidence.
UPDATE #2: Inserted a different SD card and so far, no issues. So, it might be the SD card. It's relatively new and I limit the amount of writing I do to it. Mainly, pictures and music. The card giving issues is a 64GB card and it's been in the phone for over a year. The current card not giving issues is a 32GB card, so we'll see how it goes. I'll try to format the card when I get home tonight and see if that fixes the 64GB card. It's just strange that this issue began immediately after the OTA was done upgrading and rebooted the phone today. I've never seen an issue with the card before this.
UPDATE #3: Okay, it's happening with ANY SD card I insert. So either the SD Card slot is bad all of a sudden (I haven't had ANY issues until AFTER I did the OTA), or else the OTA did something. Tonight I'm going to try and downgrade to 10b, so I guess that test is coming after all! LOL
I have been having similar issues since the last OTA update, only with both my SIM and SD card. Sometimes it only happens once a day, sometimes it happens every ten minutes, but I now get frequent errors of "No SIM Card Inserted," "SIM Card Not Readable," and "Your SIM Card is not from Verizon." When I reboot the phone, it will read the SIM card again (for awhile) and usually pops up a message "An SD Card has been inserted." This started happening the day I downloaded the previous update (currently on VS98548A).
Kiruvi said:
I have been having similar issues since the last OTA update, only with both my SIM and SD card. Sometimes it only happens once a day, sometimes it happens every ten minutes, but I now get frequent errors of "No SIM Card Inserted," "SIM Card Not Readable," and "Your SIM Card is not from Verizon." When I reboot the phone, it will read the SIM card again (for awhile) and usually pops up a message "An SD Card has been inserted." This started happening the day I downloaded the previous update (currently on VS98548A).
Click to expand...
Click to collapse
Thanks for the feedback. So it appears I'm not the only one then. I'm going to factory reset first and see how that goes. If that doesn't work, then I'm going back to 10b, then upgrade all the way to 48A and then stopping there. I'll just have to deal with the update notifs as I do not root. I use NFL Mobile and Android Pay, so I cannot root.
Well, I'm screwed. The download mode won't come on now. It got interrupted in the middle of the TOT flash and now I can longer get into download mode. When holding the Vol Up button (after powering down), and then plugging in the USB cable, some text comes up at the top left about no download mode or something. It says "Boot Certification Verify. Secure Booting Error" and then goes blank, and flashes between red and blue for the LED light. I think I'm screwed.
I can get into the stock recovery, but factory data reset, safe mode, continue power on all result in the same error message. Is there any way to fix this?
UPDATE: Okay. Had to use the hard brick recovery option.
http://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928
Wow! Never had to take apart the phone before. Had to manually flash each piece (after extracting from TOT file) until I could get it back to boot into DL mode. Then I was able to flash via LG Flash tool because I couldn't get the final partition (sbl1) to flash that way. Holding the wires was fun (I don't do solder) but I'm back up and operational. Whew!
I did notice I was still having issues with the SD card in 10b, so maybe it's the SD card slot in the phone because it's happening with all SD cards. Darn. I wonder how much a new motherboard is? Now that I know how to take it apart, I'm comfortable with doing that (just unhooking all the stuff from the motherboard is a little hairy for me, but it looks easier than when I had to fix my daughter's iPod screen once. That was a pain!)
BTW, this proves you CAN still downgrade to 10B from 49A, so that is still possible.
However, I'm still having issues with the SD card, and it occurred also with 10B and all the subsequent OTAs after it. Not sure if the 49A OTA started something, but it looks like the SD Card slot might be bad. It's just suspicious that the SD card issue started happening after I accepted the 49A OTA. Before that, never had na issue with the SD card being unmounted.
This morning I also saw one time where it couldn't sense my SIM card. Uh oh. That's not good. I really wanted to hold off on getting a new phone as this phone works just fine for me and has been good with minimal to no issues.
I feel comfortable enough to replace the motherboard since I had to open it up last night to fix the hard brick issue. Motherboards are around $110 USD it appears from what I can tell. Verizon was going to get me a new G3 for $150 USD if we couldn't get it fixed. I'm going to take it to a cell phone repair shop in town and see what they say. Maybe they have the motherboard for cheaper and I'll just buy the board and replace it myself.
Oh, and I am back on 49A since the SD card issue was prevalent throughout all the OTAs after I was able to recover my phone. Although, I have noticed it's not happening as much now. Not sure why. I'm still going to see how much it would cost to repair the SIM/SD slot.
UPDATE: Wow. Murphy's Law struck me bad! After thinking everything was fixed, this morning I found out that I couldn't receive or send texts nor phone calls. My wife had to call my work phone asking why I wasn't answering her texts nor her phone calls. Finally got it working after various factory resets and working with Verizon. Still getting the SD card messages, so definitely going to see if Cell Phone Repair+ can give me a good estimate on repairs. But at this point, I'm now fully operational. That was an exercise in frustration!
No problems here
As the OP, I have not seen any such problems with the 49A update. I have a (FAT32) 32GB SanDisk microSD card inserted. I do see a "SD card unmounted" message upon completion of booting, but it is immediately followed by a "SD card inserted" message. Access to the microSD card works fine.
Notes:
I run with the internal eMMC storage encrypted, but the microSD card is NOT encrypted. Before the 49A update, I briefly tried encrypting the microSD card, only to decide that was a bad idea: Unlike Microsoft's BitLocker encryption of "To-Go" storage, the Android encryption of a microSD card is tied to the device, which means encrypted files on a microSD card are USELESS for backup (think about it).
Due to the above, shortly before the 49A update, I inserted a blank 32GB microSD card (which the G3 formatted) and started over with loading content to it. It was about 1/2 full at the time of the 49A update.
DeanGibson said:
As the OP, I have not seen any such problems with the 49A update. I have a (FAT32) 32GB SanDisk microSD card inserted. I do see a "SD card unmounted" message upon completion of booting, but it is immediately followed by a "SD card inserted" message. Access to the microSD card works fine.
Notes:
I run with the internal eMMC storage encrypted, but the microSD card is NOT encrypted. Before the 49A update, I briefly tried encrypting the microSD card, only to decide that was a bad idea: Unlike Microsoft's BitLocker encryption of "To-Go" storage, the Android encryption of a microSD card is tied to the device, which means encrypted files on a microSD card are USELESS for backup (think about it).
Due to the above, shortly before the 49A update, I inserted a blank 32GB microSD card (which the G3 formatted) and started over with loading content to it. It was about 1/2 full at the time of the 49A update.
Click to expand...
Click to collapse
It seems to have calmed down. I normally never see this sort of behavior ever, so it was very alarming. Especially when I couldn't send or receive phone calls nor texts. But as I think back on it, I did restore some system apps that I had backed up with LG backup (or at least system settings), so maybe that caused the issue. Once I did a factory reset (twice - must have been a lot of gunk), I saw the dismount then a remount a few times after the boot and then things were fine.
I'm just glad things appear to be working fine. Fingers, toes, and eyes crossed!
Let's just put it this way: I was not ready to get a new phone. I really still enjoy this phone as it does everything I need and it does still very well. The camera is fine for me for the type of pictures I take (casual). It plays music, games, etc fine. I always hate getting a new phone because then sometimes, some of the apps I enjoy don't work on the new phone for whatever reason. So at this point, I want to stick with this phone as long as I can.
@DeanGibson or anyone else who is on the 49A OTA, I expect the Android software version still says 6.0 (as opposed to 6.0.1 or other), correct? I was at a point I could've flashed the 49A KDZ and check myself (which I'm uploading now) just a little while ago but I couldn't think of a reason I would want to, and I just finished restoring my phone back the way I had it.
Version
The 49A OTA reports 6.0, patch level 2016-10-01, build MRA58K.
I have a similar issue with the SD card. Only in my case I found that my old card was corrupted. I went out and got a new one today, but it doesn't show up in the phone. In the Settings menu there's no option to even do anything with an SD card. I did get ONE message about ejecting an SD card when I pulled it out when the phone was still running, but otherwise I don't see any options. You're saying the solution is to roll my phone back two or so versions? Or to roll back to the factory settings and then update to the latest and see how it goes? Will that wipe out all my photos and everything?
nulloverride said:
I have a similar issue with the SD card. Only in my case I found that my old card was corrupted. I went out and got a new one today, but it doesn't show up in the phone. In the Settings menu there's no option to even do anything with an SD card. I did get ONE message about ejecting an SD card when I pulled it out when the phone was still running, but otherwise I don't see any options. You're saying the solution is to roll my phone back two or so versions? Or to roll back to the factory settings and then update to the latest and see how it goes? Will that wipe out all my photos and everything?
Click to expand...
Click to collapse
Yes, flashing back to an older version will wipe everything, so whatever is on your internal memory needs to be copied down off the phone to your PC before you flash back to 10b. But, I don't know if 49A really is the culprit here. I really do think now that it is my SD card slot. It must have been ironic coincidence that the issues started showing up right after I took the 49A OTA. That's all I can say because going back to 10b, I saw the same issue, so I really do believe that my SD card slot is bad.
The 49A_04 KDZ is now in the same place as my other KDZ and TOT uploads, linked to at the bottom of the first post in @annoyingduck 's stickied return to stock thread in this section.
iBolski said:
Yes, flashing back to an older version will wipe everything, so whatever is on your internal memory needs to be copied down off the phone to your PC before you flash back to 10b. But, I don't know if 49A really is the culprit here. I really do think now that it is my SD card slot. It must have been ironic coincidence that the issues started showing up right after I took the 49A OTA. That's all I can say because going back to 10b, I saw the same issue, so I really do believe that my SD card slot is bad.
Click to expand...
Click to collapse
I don't think the slot is bad unless however many people's phones decided to go bad all at once. Mine started acting up a week or so ago after my phone spent all night plugged in but didn't charge and was really hot. I think that coincided with some device update as well. The problem then was that it wouldn't recognize the SIM card. I took it to the shop and they gave me a new SIM which seemed to solve the problem (I thought the excess heat had fried the SIM card). Then the 11/11 update happened and my SD Card started acting up. I thought the same thing could be true of the SD card so I got a new card and when I downloaded the SanDisk recovery tool I saw a bunch of corrupted files from the old card. Now, having had the new card in my phone since the afternoon, I am seeing a lot of error messages involving the card not ejecting properly or the files being corrupted (there's no files, yet - it's a clean format). So, it's definitely something resulting from either the overheating a couple weeks ago, or the 11/11 update or a combination of the two. I would really hope LG and/or Verizon wouldn't send us the Order 66 code for our phones, but if they really did trash it I'll be getting a new phone and they damn sure better not want their deductible.
---------- Post added at 05:17 AM ---------- Previous post was at 04:43 AM ----------
I actually just spoke with Verizon's support people. It turns out the device is not compatible with the latest Android updates. Maybe going back to square one with it will fix the problem, but they said they would give me a new device with the updates disabled until the problem is fixed. I don't know if that means I'll have to give them the new phone back when the updates are working or what. I'm kind of partial to this one, now. But I do know that possibly bricking my phone with this KDZ or TOT stuff is a less appealing option than getting a free replacement and/or upgrade. I'll find out more tomorrow.
nulloverride said:
I actually just spoke with Verizon's support people. It turns out the device is not compatible with the latest Android updates. Maybe going back to square one with it will fix the problem, but they said they would give me a new device with the updates disabled until the problem is fixed. I don't know if that means I'll have to give them the new phone back when the updates are working or what. I'm kind of partial to this one, now. But I do know that possibly bricking my phone with this KDZ or TOT stuff is a less appealing option than getting a free replacement and/or upgrade. I'll find out more tomorrow.
Click to expand...
Click to collapse
Nice find there! I can concur as well. I'm currently back at 48A and have NOT had one sdcard issue. That really sucks. Means they didn't test very well. I hope they have another update to address that issue. So 48A is the latest I'll go to. Wish I could disable the update myself so it doesn't notify me of 49A.
Sent from my VS985 4G using Tapatalk
Rom tekcafe vs985 49A
https://www.youtube.com/watch?v=3FxIk7x-CaE
More normal
DeanGibson said:
As the OP, I have not seen any such problems with the 49A update. I have a (FAT32) 32GB SanDisk microSD card inserted. I do see a "SD card unmounted" message upon completion of booting, but it is immediately followed by a "SD card inserted" message. Access to the microSD card works fine.
Click to expand...
Click to collapse
In order to increase my external storage, today I replaced the above 32GB card (formatted FAT32 by the G3, as I recall) with a SanDisk 128GB card (formatted exFat by Windows 10). Did the same thing on my two LG G Pad X8.3 (VK815) tablets (which is running the same build/patch level as the G3). No problems so far.