So the company I work for requires that you fully encrypt your mobile device if you want to check your company email account via Outlook. I charged my phone up to 92%, began the encryption process, kept the phone plugged into a 2.0 charger and 5 hours later its still stuck on the Verizon boot image. I have about 18gb of music on the internal storage, a literal **** ton of pictures (also on the internal), and another literal **** ton of apps. I have a 128gb micro SD card in there as well but never got around to moving much over to it.
So here's my question: is my rooted G4 bricked or could the process be taking so long because of how much literal **** I have stored throughout the phone?
I'd greatly appreciate any advice, my occupation revolves around our phones so I'm literally F'ed in the Aye if I'm without my phone in the field tomorrow.
Well scratch my plea for help off of your evening To-Do lists. As the 6th hour post-encryption drew near I said screw it and pulled the battery and was eventually greeted with my lock screen and the encryption password so all is well.
Related
Ok so this started happening when I switched to unofficial CM9 from this forum. Constant "your sd card was unexpectedly removed" errors. Usually right when I open the camera app, or try to play music. Go figure. Once I reset the phone (doesn't always work) the problem goes away until I leave the phone long enough for it to go idle I guess. First thing I figured was the OS change. So I restored a backup. Same problem. Backed up the sd card and wiped the phone and sd card. Reinstalled CM7.2. Nope. Same problem. Forgot to mention, I had already tried both of my spare 16 gig cards, two of which were from a different manufacturer. One I formatted with my computer, then other I left alone and just deleted the files from it with the phone to rule out my computers card reader going bad. Both had the same exact issues. I even switched to a sense based rom called UKB. Same. Problem. Although this time it seems to be a little better. Worked all day yesterday at least, problem only coming back after the phone was on charge all night. I could live with that but I doubt it'll keep that up all night. I've read just about every forum post on every forum. Loads of people suggesting reformatting without using quick format, formatting with different settings, using various apps that change the cache size. Regardless, none of this was necessary before, and definitely shouldn't be necessary now. I'm a couple months past my warranty or I would get a replacement like I did before when I had headphone jack issues. Really sick of my phones all going bad before upgrade. Maybe if I called they would see that I have not been a happy customer, but a customer nonetheless since like 1998. Who knows. But anyway, does ANYONE have any suggestions? And please don't suggest going to settings and hitting mount. That suggestion is in just about every forum post about the problem and it oddly drives me crazy. Probably because of how obvious it is. That option is always greyed out of course. Thanks in advance to anyone who's willing to help. I always want to smash this phone every time I need to take a picture of something really cool and my phone decides to act up.
Come on guys, nothing?
I'm having the exact same problem, and I'm 100% stock, always have been. I have no idea what's going on, but it's really frustrating, especially because of all my apps I keep on the SD.
Sent from my ADR6350 using xda app-developers app
lfrench0 said:
I'm having the exact same problem, and I'm 100% stock, always have been. I have no idea what's going on, but it's really frustrating, especially because of all my apps I keep on the SD.
Sent from my ADR6350 using xda app-developers app
Click to expand...
Click to collapse
Well the best part? Now the phone doesn't recognize the card at all. This phone has been in a case since purchase. Never been dropped. Has been tested with multiple cards in multiple formats. But looks like HTC is yet another company that designs phones to intentionally break over the course of a year or two. Go figure. Phone is only a little over a year old. Then again the board is older since it was a refurb. First phone had issues with the headphone plug.
alexmawdsley said:
Well the best part? Now the phone doesn't recognize the card at all. This phone has been in a case since purchase. Never been dropped. Has been tested with multiple cards in multiple formats. But looks like HTC is yet another company that designs phones to intentionally break over the course of a year or two. Go figure. Phone is only a little over a year old. Then again the board is older since it was a refurb. First phone had issues with the headphone plug.
Click to expand...
Click to collapse
Maybe try unexpectedly inserting the sd card? /s
But in reality, that stinks.
gtdtm said:
Maybe try unexpectedly inserting the sd card? /s
But in reality, that stinks.
Click to expand...
Click to collapse
Haha that one made me smile. I can just see myself in the dark with one of those long armed desk/work lamps shoving an sd card into my phone and yelling "SURPRISE!" while laughing like an evil villain. This truly has driven me nuts though. I've been stuck on my sad old OG Droid. You know, the one that made android popular but is painfully slow when you're used to a phone overclocked to 1.5 ghz. Even with this one at 900 mhz (all it can handle with a standard voltage kernel without crashing) it often freezes up multitasking. Navigation takes a good couple minutes to fully load a small route, and it simply isn't gonna happen if music is playing.
HOWEVER, I decided to try again. Dinc2 recognized a card again. Not sure why. Whatever. So because the card works even temporarily, I flashed a new radio and am now downloading unofficial cm10 and all that good stuff. Gonna flash everything after triple wiping, then I'll wipe cache again after flashing everything. Just maybe that new radio and lots of murdering the wipe button, it shall survive. It just doesn't make any sense to be a hardware problem since it's only intermittent when the sd card is suddenly active after not being accessed for some time. I can sit there taking pictures and video for hours while playing music. But once the screen is off for 10 minutes and I go look at those pictures, the sd card is suddenly removed. I'll keep you updated. Downloads are complete. Muahahahahaha
So I did end up flashing CM9 instead, because CM10 was just too buggy for my liking. However I used the newest kernel available. It was in the unofficial CM10 forum post.
Radio seems to have fixed the problem though. SD card hasn't unmounted once. We'll see how it works out over the course of the day but it copied all my music over wifi last night, finished at about 2AM, then sat there until I woke up at 6 completely idle. Picked it up and went straight to gallery, and it loaded pictures. Took a snapshot with the camera, then played a song. Everything looks to be in order. I flashed the radio that was apparently in the leaked ICS developer update.
Disregard the suggested fix I posted prior. I mean if you have the problem you can try it... since it seemed to fix it for a day. But it's right back to it again. Downloaded and installed ukb evolution 2.1, and it did the same on that as well. So I guess I live with it for the time being, never buy an HTC device again, hope like crazy a moto device lasts longer, and fork over the scam of an extra year of warranty when I upgrade. Really, what kind of world do we live in where we have to spend money for a company to stand by their product for longer than a lousy year? When standard contracts are for two years, it leaves an entire year where the device can just stop functioning properly, like this one, and then you're stuck paying 600 bucks for a device that cost HTC maybe 100 bucks to make. And even at that ridiculous cost, it still takes two iterations of android before they even suggest that they might update the device to the older version, over three years after launch. Awesome little fact, if the one year warranty restarted when I got the phone replaced in the first place for an issue with the headphone jack, I would still be under warranty. But nope, it wasn't replaced with a new device, but someone elses phone that was then fixed and then sent to me. I still hate that I can buy a brand new phone, and get a used one in return because these companies refuse to build a phone without trying to design it to die at the end of it's "useful" life. People will pay to upgrade if they want to. If the phone barely lasts the full two years if that, someone in their right mind simply wouldn't buy from them again. My original droid was out of warranty by 8 months when I had it replaced TWICE. Why? Because I had it replaced 5 times before that for headphone jack problems. Only reason I didn't buy another moto phone was because they decided to lock down bootloaders for good, while HTC was announcing that they were becoming dev friendly and unlocking their devices. Customers always get screwed. Alright end rant. Sorry guys, extremely frustrated.
I had the same problem on the Samsung Galaxy Y Pro, FWIW. Probably unrelated.
Same here with a 2 year old dinc2. SD card works fine as far as the phone is awake. Works fine in other phones and computers either...
Every 6-12 months, I have this problem and it's blindingly frustrating. As it turned out, my MicroSD card was starting to get tired, and swapping it out with a brand new flash card from Staples resolved it completely. Just like the OP, I had two used 32GB MicroSD cards -- one of them an expensive high-speed Sandisk -- that reported no errors under Windows or CWM. Installing it in my DInc2 (CM10), it would run for a while, but then just decide to unmount.
It may sound illogical, but try purchasing a new, inexpensive MicroSD card (I bought another Sandisk) and see if the problem goes away permanently.
- Dave
I tried two different sd cards on two different roms - cm7 and evervolv and the cards kept dismounting about twice a day. I then turned on "protect sd card" under developer options on evervolv rom. I don't know what it does but haven't had the problem for about a week. It might be a coicidence though. Will see...
fixed
surfthesummer said:
I tried two different sd cards on two different roms - cm7 and evervolv and the cards kept dismounting about twice a day. I then turned on "protect sd card" under developer options on evervolv rom. I don't know what it does but haven't had the problem for about a week. It might be a coicidence though. Will see...
Click to expand...
Click to collapse
I had the same problem for monthes. I had gone through all the efforts to fix it. finally I found a clue.
On the back cover, there are two pairs of pins which supposed to connected to the terminals on the phone, which are not connected well. so I bent the springs up a little bit and made connection well. (be very careful not break the springs). then SD card show up right away. It's being working for days and no more problem.
hope it helps everyone.
sd card issue
Same issue with my HTC incredible s.....phone not in warranty....plz help guys.....
Some says its software ...some hardware....all assumptions.....
tc truly sucks.....camera sucks...music sucks.....overpriced.....etc etc.....but wen u pay
Such a lot of money u expect something good....such an awesome name HTC INCREDIBLE ...incredible ma a$*..
Somebody plz help....
This is incredible 2 forum...but just busting your balls....try a new SD card
Sent from my ADR6350 using xda app-developers app
My dinc2 started with this problem about 3 months ago. I was running the psychochilly cm10.1. Then I decided to try the miui v5 ('alpha'?) rom which had a known bug that the SD card won't Mount. After about two minutes, it crashed, so I just decided to restore my psychichilly backup. Thenextday i noticed that the sd card was unmounted several times when I wanted to take or look at a pic. I found that if I took my otterbox off, along with the back plastic and tapped the back of the phone near the bottom on the edge of the table gently it would magically recognize my SD card. Not too long after it would pop up that 'SD card unexpectedly removed' message. So. Whether it's hardware or software related, I'm not sure. But I'm thinking hardware. On the other hand, I had to use the tacoroot method to s-off. Maybe an effect that took a whole year to happen. Either way I think the only way to fix this issue, besides reflowing the motherboard around the SD card slot, is to replace the motherboard, which I just might do. Kinda itching to flash the new PAC.
I used these searches before compiling this thread;
"how to recover data from a bricked SGN"
"data extraction from a SGN that will not boot"
"removing the HD from samsung galaxy nexus"
These searches did not yield results that replicate my situation. The only search that resulted in many entries were for people with "bricked phones" that (at least somewhat) responded to input. I associate the term "bricked" with a phone that does not respond to input, or show any indication of getting power.
My phone is a Samsung Galaxy Nexus on verizon wireless. It has been rooted and is running a custom ROM by...AOKP i think. I had some assistance each time I rooted and updated my ROM.
Here is my problem, what caused it,my troubleshooting steps, and what I'm trying to do. My phone was partially submerged in water for an unknown amount of time. The battery and SIM were removed and kept in a water proof container within an hour of submersion. The water damage indicator stickers (on both the battery and the phone have not been triggered). About 24hrs later, the phone was placed in a zip lock bag with 4 desiccant silica gel packs where it will remain for the next 24. Per vzw's tech support, I tried to power the phone on using the charger and the battery removed. No change. Verizon was not advised of the partial submersion, only the non triggered water damage stickers. This phone is under warranty and a replacement has been shipped. I confirmed that my contacts are backed up to google.
The reason for this post is, I have close to 30GB of pictures and videos that I stored on this device's "internal SD" that I want to recover. Looking through the searches I mentioned above, it sounds like this isn't so much a separate card, but more of a partition on the phone's HD. I have been told by vzw that neither their branch office tech support, nor their recovery/diagnostic team that analyzes returned phones has the capability to remove and return this data.
If someone here has hardware experience with cracking open a SGN and swapping the "internal SD card" I would greatly appreciate any information available for this task.
if it cant turn on, you cant retrieve data.
Zepius said:
if it cant turn on, you cant retrieve data.
Click to expand...
Click to collapse
Well..OK. I'm not ready to give up just yet. When my desktop PC's power supply failed, the PC was unusable, and didn't indicate power. I swapped that out and it now it works fine. This seems like it could be a similar situation. I at least want to exhaust every option I have before throwing in the towel.
Those 30GB contain hundreds of pictures of the first 2 years of my kid's life.
It seems to me that data recovery should still be possible if an replacement power source is utilized. Maybe more than just the power source has failed. Maybe every other hardware component in my wet phone has failed. But maybe, that "internal SD" is recoverable.
If anyone here knows what the "internal SD" looks like, and has successfully swapped one, I'll risk it. I know I can't trust vzw with such a task.
I realize this is a developers forum, and I'm asking for hardware failure advice. If anyone can refer me to a different forum that is more specialized to my specific task, I'll gladly take my trouble there.
Thanks for reading,
Jef
you're assuming 1 thing. the nand that houses the storage is in good health. When water is introduced, you have the unknown factors of what it does to circuitry.
im sure there is a ifixit teardown showing where the nand is. The problem is its soldered to the mainboard of the phone. You might be able to unsolder it, but thats a stretch.
Zepius said:
you're assuming 1 thing. the nand that houses the storage is in good health. When water is introduced, you have the unknown factors of what it does to circuitry.
im sure there is a ifixit teardown showing where the nand is. The problem is its soldered to the mainboard of the phone. You might be able to unsolder it, but thats a stretch.
Click to expand...
Click to collapse
Thank you very much Zepius. I googled "ifixit teardown samsung galaxy nexus" which lead me to a page (that I'm not able to paste here as a new user).
which is exactly what I was looking for. I wouldn't go so far as to say that I'm assuming the nand is in good health, just wishful thinking.
Anncoco - sorry, I don't remember what I did with this. It's been about 4 years, and this was 3 phones ago. I think I had some of the photos backed up somewhere else, enough that I never went to the trouble to disassemble the Nexus. From my notes - I remember the phone did not indicate it was getting power when plugged in.
Hi guys,
I'm using a Samsung GS3 L710 on Sprint. I'm on the Wicked Evo X 8.1 ROM and TWRP v2.7.1.0.
Had a dumb moment and got power steering fluid all over my phone. Immediately popped the battery out, wiped as much fluid as I could off, then (stupidly?) tried to rinse the fluid off with water, figuring I could dry the phone out later. My screen was already shattered so I thought the fluid would be more harmful than water getting in the cracks. Feel free to criticize that decision if it was indeed a poor choice.
Now, 24 hours of rice later, my phone is stuck in a boot loop. I can get it into download mode and recovery fine, but the phone will get 80% of the way through the normal boot and just reset. I've accepted defeat because this phone is destroyed regardless and I'm probably just going to get a new phone. Trouble is, I really want the data and texts off of it. The only things that aren't automatically backed up are my texts and there's a lot of sentimental value in them I'd like to keep.
I went into TWRP and tried to make a backup, only to see that my data partition might be corrupted. When selecting the backup option,
Boot takes up 10MB,
System takes up 1400MB,
Data takes up 8002456730111MB, and
Cache takes up 14MB.
One of those is a little off.
The phone isn't letting me make a backup because obviously I don't have 8002456731535MB of space left on my phone.
Is there any way to grab this data still?
Thanks in advance!
I posted a similar message on another forum and got an excellent reply but maybe there are other options. My unrooted, nearly fully charged, never damaged (no physical damage) 1 year and 3 month old Note 4 suddenly shut itself down while charging and has not turned on since (weeks ago). This was after a recent OTA update to Android Marshmallow.
From what I read the most likely cause was an eMMC failure. I had no idea what this meant before reading about it but it's interesting to understand how the phone works and how it stores information. I've tried a new battery, a new charging cord, computers (two different operating systems), and other solutions but device has no power and is not recognized by a computer.
The phone is pending an exchange but my concern is that I'm not able to access the data (wedding pictures, work notes, important old text messages and voicemails) to transfer the data. I did have a recent backup of certain information (pictures primarily) so I know the value of backups but the small amount of data on the phone that was not backed up is important to me.
Even if I can't access the data to transfer it, I worry very much about turning in a phone without wiping the data. I've never done that before. Is it that much of a risk in this situation (or will the carrier simply switch out the motherboard and melt down the old one for parts and sell the phone as a refurb)? There are some options to get the phone fixed but I don't know if any would guarantee the data will be preserved and who knows how the current device will do for the remainder of the contract. Also instead of an exchange, do you think the carrier would let me lease a phone so that I could keep this phone and try to fix it on my own. Is that even worth it?
Thanks for your help.
I have a one and a half year old LG G3. Since warranty covers for two years, I decided not to break it by rooting it or whatever. I'll do that in six months.
The phone has served me well for the most part, and I did my best to keep it malware free. I only installed apks from Google Play store (with exception of installing eduroam apk need for my colleges wifi to work - which was from a safe source, of course). However, lately, strange things started to occur. I thought I was going crazy at first - there were pictures that I took, that I knew that I took, that just aren't on the phone anymore.
Finally, the obvious answer has come to me - the devious storage elf must have took them for himself.
Also, the little bastard has been crippling my music collection. And in most devious way imaginable. Instead of deleting the whole albums, it left an average of first 6 songs in each folder. Some albums went from 20 to 3 songs, while others managed to end up unscathed.
I have to note that I do have a SD card in my phone (a 32GB, for collective device storage of 64GB), about as old as my phone. I also believe that all the missing data has gone missing from the said card. But I'm not sure. Some pictures might have been in the phone memory. Never thought I'd have to keep track of it.
My first though was that my SD card failed, but seriously, what the hell. How does a card fail and not only delete only some files (okay, that is entirely feasible), but delete all but the first six song in each album (and we are talking over 30 albums here, so it's not a statistical oddity). The other culprit could be the phone (which I totally wouldn't mind if the warranty could get me a new one). But it's an LG, it's a good brand.
Which leaves us with the obvious choice, which is the evil storage elf that eats music and pictures. I don't know what I did to wrong him, but reasoning with him did not help. I need a method of disposing of the tiny twat. I considered shooting him, but that might damage my phone. Do these elfs like analog data as much as digital? I thought I might leave some physical pictures near my phone and squash the beast when it pokes it's ugly head out. Or should I do poison? How do you poison a picture? Should I download some pictures of Donald Trump to my phone? Or would that outright break my phone (crack the screen)?
P.S. In all seriousness, my phone is malfunctioning exactly the way I described, if you leave out the mystical creatures. Files are going missing (again, I'm not sure if it was in a single batch or gradually), and are doing so in some weird fashion. Most of my albums only have the first six song left, others just gone (I checked with file explorer, they are not gone from cache, but gone gone). Honestly, the best thing I could hear is that I could get my device replaced with a new one, but I doubt it's going to happen. Something went wrong, and it might again, so I'd really like to identify what it was and fix it to make sure it doesn't happen again. Also I'm sorry if the elf story wasn't amusing to you.
Karlovsky120 said:
I have a one and a half year old LG G3. Since warranty covers for two years, I decided not to break it by rooting it or whatever. I'll do that in six months. ...
Click to expand...
Click to collapse
Are you running any app like Link2SD or similar?
You may test with another SDcard and check the behaviour it takes. Also I recommend re-formatting your SD.
I'm not running any apps that manipulate storage.
I could test it with another card, but since I can't force the error to happen or not happen (e.g. recreate the exact conditions, I don't know what triggered this) I can never be sure or do any reliable tests. I would have to stick in (a considerably smaller) card and just wait for it to fail or not fail. For how long would I have to wait to confirm it's the card?
But I really doubt it's an SD card failure since the deleted songs were all on the same range (e.g. from seven to twelve), and never at the start of the album. I'd expect more erratic behavior if the card had failed (random stuff deleted, or card not working at all). This seems too neat to be an error at a hardware level. Especially when you consider the fact that I copied all that data on one go some time before on a blank card - all of the data was probably physically adjacent on the chip making this kind of failure even more unlikely.