Related
A friend of mine had some problems and asked if I could look into it for him. I've never owned an Incredible so I don't really know much about it. I figured I'd post here and see if you guys can help.
Here's what he sent me:
"So I've got an Incredible and recently its been prompting me to do updates when I'm pretty sure my phone is up to date. So I click update and it says its going to reboot and then never does. So this morning I wake up and its like internal SD card cannot be read or something to that extent. But what's weird is that all my music still works but all my custom ringtones are broke. It's like the 8GB SD card is working, but the internal memory is failing. What do? "
Any ideas?
McFluffnStuff said:
A friend of mine had some problems and asked if I could look into it for him. I've never owned an Incredible so I don't really know much about it. I figured I'd post here and see if you guys can help.
Here's what he sent me:
"So I've got an Incredible and recently its been prompting me to do updates when I'm pretty sure my phone is up to date. So I click update and it says its going to reboot and then never does. So this morning I wake up and its like internal SD card cannot be read or something to that extent. But what's weird is that all my music still works but all my custom ringtones are broke. It's like the 8GB SD card is working, but the internal memory is failing. What do? "
Any ideas?
Click to expand...
Click to collapse
I assume its rooted, thats why the update wont go thru. As for the memory, does a reboot fix it?
Does this user also understand the concept of safely ejecting his phone before removing it from the computer (most importantly after moving, editing, or pasting files)?
Chances are, his sd card and internal memory could use a good 'disc checking' from a windows computer.. Lol
cmlusco said:
I assume its rooted, thats why the update wont go thru. As for the memory, does a reboot fix
Click to expand...
Click to collapse
McFluffnStuff said:
"So I've got an Incredible and recently its been prompting me to do updates when I'm pretty sure my phone is up to date. So I click update and it says its going to reboot and then never does. So this morning I wake up and its like internal SD card cannot be read or something to that extent. But what's weird is that all my music still works but all my custom ringtones are broke. It's like the 8GB SD card is working, but the internal memory is failing. What do? "
Any ideas?
Click to expand...
Click to collapse
My cousin called me yesterday complaining of the same thing. He stated that he has been recieving OTA updates for the phone on a daily basis lately and since the first update has been getting an internal memory low popup on his Incredible.
His phone is NOT rooted and completely stock with the original SD card. Would like help from anyone else having this issue and knows what the deal is with the multiple OTA's coming in and killing memory.
Okay, here is what needs to happen if you are to get rid of that error..
Go to cyanogenmod and follow the wiki to root and ROM your phone...
Or, do the update...
Now, i would strongly recommend the first choice, as oppose to the second..
The stock software is disgusting.
Rooted cm7 will not only run a lot better for you, but you will be more up to date than the ota update.
You're phone most likely is running out of internal memory, because it is downloading the update and storing it in preparation.
Just do a google search for cyanogenmod, go to their site, click your device, then click the related wiki page..
Follow the instructions and check back here on xda if you have any questions.
Good luck
camo4x4 said:
His phone is NOT rooted and completely stock with the original SD card. Would like help from anyone else having this issue and knows what the deal is with the multiple OTA's coming in and killing memory.
Click to expand...
Click to collapse
For the update to succeed, the phone has to be plugged into the wall charger.
Sent from my ADR6300 using xda premium
Hello everyone,
I just rooted my beloved G Pad, as I'm fed up with the SD card issue of unmounting, mounting, ejected, removed by itself.
I am running 4.4.2 stock - no ROM, stock but rooted.
Installed SD Fix, ran the app. Was good for one day and this morning - BAM! I noticed that message saying - card was unmounted improperly...
So - correct me if I am wrong but I thought rooting my G Pad and installing the SD Fix app should have addressed this.
Am I missing anything? Such an annoyance this SD card issue.
Appreciate any inputs.
Bangjr said:
Hello everyone,
I just rooted my beloved G Pad, as I'm fed up with the SD card issue of unmounting, mounting, ejected, removed by itself.
I am running 4.4.2 stock - no ROM, stock but rooted.
Installed SD Fix, ran the app. Was good for one day and this morning - BAM! I noticed that message saying - card was unmounted improperly...
So - correct me if I am wrong but I thought rooting my G Pad and installing the SD Fix app should have addressed this.
Am I missing anything? Such an annoyance this SD card issue.
Appreciate any inputs.
Click to expand...
Click to collapse
SD Fix solves a permissions issue, not the unmounting/bad removal issue. In my case my bad removals dropped dramatically when I got a different sd card. However that fix doesn't work for everyone either. LG will tell you to factory reset, but please make sure to complain to their support line anyway since it might make them wake up to the issue and then try and address it.
muiriddin said:
SD Fix solves a permissions issue, not the unmounting/bad removal issue. In my case my bad removals dropped dramatically when I got a different sd card. However that fix doesn't work for everyone either. LG will tell you to factory reset, but please make sure to complain to their support line anyway since it might make them wake up to the issue and then try and address it.
Click to expand...
Click to collapse
Thanks Muiriddin for setting me straight with regards to SD Fix. :good:
I had replaced my SD card once and yes, it was not unmounting/mounting for about a month then BAM - dismounts, removals, etc, etc.
I have also called in LG Tech Support - they wanted me to ship my tab to them. The person I spoke said that they were unaware of the issue. I said, does this call make you aware of the issue now? Silence...LOL!!
Bangjr said:
Thanks Muiriddin for setting me straight with regards to SD Fix. :good:
I had replaced my SD card once and yes, it was not unmounting/mounting for about a month then BAM - dismounts, removals, etc, etc.
I have also called in LG Tech Support - they wanted me to ship my tab to them. The person I spoke said that they were unaware of the issue. I said, does this call make you aware of the issue now? Silence...LOL!!
Click to expand...
Click to collapse
If it was not happening at first and is now try reformatting the card. That can help sometimes...
muiriddin said:
If it was not happening at first and is now try reformatting the card. That can help sometimes...
Click to expand...
Click to collapse
Yup have done that too...to no avail.:crying:
Hi Guys,
I'm on Temasek's CM11, been using this Sony 64GB microSD card for over a year, and today, randomly while the phone was in use, I saw a message pop up, SD card unexpectedly unmounted. After that, it's not using up in the file systems, all the way down to the Recovery. I'm using TWRP.
I put the SD card in another Note 3 I have and everything seems to be fine on there, all the data is here.
So just posting here to make sure that is it safe to conclude that my SD card slot is fried?
And if so... What are my options... I have had the Note 3 for over a year and brought it off of Craigslist. It's unlocked and use it on AT&T...
So any ideas or advice friends? And yes, I pressed the SD card firmly in my Note 3 many times...
Thank you!
Anyone guys?
have you tried a different sd card? Also is your phone rooted if so try to access it in recovery. if so then something in the system messed up and a restart of your phone could fix it or a new rom. good luck hope it's not fried :-\
spriteboost said:
have you tried a different sd card? Also is your phone rooted if so try to access it in recovery. if so then something in the system messed up and a restart of your phone could fix it or a new rom. good luck hope it's not fried :-\
Click to expand...
Click to collapse
Thanks bud for your response! Yes, another sd doesn't show up in the phone, but works in another phone. And no, Recovery does not pick it up either .
Looking to move to another ROM, want to try Android 5.0, but really want to make sure I can come back to KK if I want to. The fact that sd is not showing up in recovery is really discouraging, but also, there are no signs of sd card slot being fried either like a smell or anything.
Please keep responding folks, if you have any ideas! Thank you!
Your using CM11 killed the sdcard slot in your Note 3. No use crying after spilled milk. Stick to stock rom next time.
jamesc760 said:
Your using CM11 killed the sdcard slot in your Note 3. No use crying after spilled milk. Stick to stock rom next time.
Click to expand...
Click to collapse
Hey bud, not crying, but just seeking knowledge, asking around. Are you saying my hardware (sd slot) is dead?
Thanks!
possible solution same problems s3 tho. second post he has a procedure by Icepick1337 hope it fixes it.
http://forum.cyanogenmod.org/topic/98618-micro-sd-card-killed-after-installing-cm/
Hello everyone, I also have a Redmi 1S but there's a problem, I don't know why but sometimes the sd card stops working, it means that no sd card is not getting mounted no matter which card I insert and the cards are working properly on all other Android devices, amd this problem gets fixed automatically sometimes, but I want a proper fix for it, please help me, if you help me I'll mention you on my YouTube Channel Geeky Android Tips which has 3.4K subs, I'll also promote a page of yours if you want to, but please help me...
Check the leads carefully for dirt and see if the slide lock is not loose or broken.
barrack1 said:
Check the leads carefully for dirt and see if the slide lock is not loose or broken.
Click to expand...
Click to collapse
nothing like that, hardware is all well it's a software problem, it'll get fixed when I install the stock ror for 3-4 times,but I don't want to that, I'm on AOSP Marshmallow by the way
geekyandroidtipsrocks said:
nothing like that, hardware is all well it's a software problem, it'll get fixed when I install the stock ror for 3-4 times,but I don't want to that, I'm on AOSP Marshmallow by the way
Click to expand...
Click to collapse
Do you mean to say that you have to flash the stock miui continuously for 3-4 times to fix it? That doesn't sound right, there could be a broken trace wire or something. Or the internal storage is failing.
Hello every one! so yesterday while doing nothing but leaving my phone on a markipilers youtube video, I see my screen go off I try to turn it back on and nothing happens. I tried power cycling and its still off, just not responding to anything, no sound no light no nothing. I tried then going to recovery mode but well... nothing happened. The only thing that actually makes any responses is when I connect it using a USB to my laptop, my laptop beeps, its not suposed to beep it is broken so is it bricked?
My device is a rooted Samsung galaxy s4 mini i19192 or so I hope it is.
I really hope that this is the right place to be redirected to assistant if not then Iam really sorry, thank you so much every one and have a fantastic day!
Edit: I forgot to mention two things.
1st: It does not seem to charge the battary, I kniw this because I have another identical one though the battary works fine in the working one
2nd: My PC reads it as (something?)_dload, Sadly I do not have acess to a computer just yet. Thanks again
Any help.. please?
Khaled125 said:
Hello every one! so yesterday while doing nothing but leaving my phone on a markipilers youtube video, I see my screen go off I try to turn it back on and nothing happens. I tried power cycling and its still off, just not responding to anything, no sound no light no nothing. I tried then going to recovery mode but well... nothing happened. The only thing that actually makes any responses is when I connect it using a USB to my laptop, my laptop beeps, its not suposed to beep it is broken so is it bricked?
My device is a rooted Samsung galaxy s4 mini i19192 or so I hope it is.
I really hope that this is the right place to be redirected to assistant if not then Iam really sorry, thank you so much every one and have a fantastic day!
Edit: I forgot to mention two things.
1st: It does not seem to charge the battary, I kniw this because I have another identical one though the battary works fine in the working one
2nd: My PC reads it as (something?)_dload, Sadly I do not have acess to a computer just yet. Thanks again
Click to expand...
Click to collapse
probably QHSUSB_DLOAD, which is a hard brick, you might be able to fix with a debrick image
Sent from my Galaxy S4 Mini using XDA Labs
its in fact qshusb_dload but iam still a bit clueless on the reason or which method to solve. I read its because the cpu is trying to boot from the sd card and has something to do with something called emmac that is terrible in the s4 so I read three methods to solve
1- Just your method
2- Cooling the emmc?
and three, this
http://cellphonetrackers.org/qhsusb_dload-fix-qualcomm-soc.html
so Iam a bit distracted on what to even do or how to do it, any help would be apriciated plus any further notices about how to even avoid the problem
and thank you so much @IronRoo for your noticable contributions to these stuff!
Khaled125 said:
its in fact qshusb_dload but iam still a bit clueless on the reason or which method to solve. I read its because the cpu is trying to boot from the sd card and has something to do with something called emmac that is terrible in the s4 so I read three methods to solve
1- Just your method
2- Cooling the emmc?
and three, this
http://cellphonetrackers.org/qhsusb_dload-fix-qualcomm-soc.html
so Iam a bit distracted on what to even do or how to do it, any help would be apriciated plus any further notices about how to even avoid the problem
and thank you so much @IronRoo for your noticable contributions to these stuff!
Click to expand...
Click to collapse
Yes, the eMMC is prone to fail/corruption on our phones, at least I think. The eMMC is the internal SD memory. Hopefully yours is just corrupt.
The cooling trick is probably only good if there is a bad soldier joint on the chip and will probably only work a few minutes as the board will heat up once turned on
I would try the debrick file as that's probably the easiest. See also Valenti's post on other Samsung device, as better write up on one (Samsung Mega maybe?) as well as by the others who originally come up with the debrick idea to get a better idea of what to do.
I guess (without researching) the method in your link is the same principle as the debrick file but may work even if debrick doesn't work as not dependant on having a matching file from phone with same bootloader (???? I don't know as haven't looked into that method)
Also you can send phone away for jtag if nothing else works
Sent from my Galaxy S4 Mini using XDA Labs
IronRoo said:
Yes, the eMMC is prone to fail/corruption on our phones, at least I think. The eMMC is the internal SD memory. Hopefully yours is just corrupt.
The cooling trick is probably only good if there is a bad soldier joint on the chip and will probably only work a few minutes as the board will heat up once turned on
I would try the debrick file as that's probably the easiest. See also Valenti's post on other Samsung device, as better write up on one (Samsung Mega maybe?) as well as by the others who originally come up with the debrick idea to get a better idea of what to do.
I guess (without researching) the method in your link is the same principle as the debrick file but may work even if debrick doesn't work as not dependant on having a matching file from phone with same bootloader (???? I don't know as haven't looked into that method)
Also you can send phone away for jtag if nothing else works
Click to expand...
Click to collapse
Thats great! thank you. however can you give me a link to download that file / tutorial as iam not sure google would help me in that. second off I have no idea where Valenti's post either so that would just be fantastic if you can, Thanks again for every thing!
Khaled125 said:
Thats great! thank you. however can you give me a link to download that file / tutorial as iam not sure google would help me in that. second off I have no idea where Valenti's post either so that would just be fantastic if you can, Thanks again for every thing!
Click to expand...
Click to collapse
There are some debrick files here for some of the S4 Mini models (some have broken links but some still work, or find others on internet. This is also one of the thread started by @ValenteL
http://forum.xda-developers.com/showthread.php?t=2625628&page=10
Sent from my Galaxy S4 Mini using XDA Labs
IronRoo said:
There are some debrick files here for some of the S4 Mini models (some have broken links but some still work, or find others on internet. This is also one of the thread started by @ValenteL
http://forum.xda-developers.com/showthread.php?t=2625628&page=10
Click to expand...
Click to collapse
Wanderful, Thank you! should I mark this as solved?
IronRoo said:
There are some debrick files here for some of the S4 Mini models (some have broken links but some still work, or find others on internet. This is also one of the thread started by @ValenteL
http://forum.xda-developers.com/showthread.php?t=2625628&page=10
Click to expand...
Click to collapse
I have been searching for ever and still zero luck on finding either a way through the s4 mini nor the actual debrick file... all I could find was for the s3 all over, any help?
Khaled125 said:
I have been searching for ever and still zero luck on finding either a way through the s4 mini nor the actual debrick file... all I could find was for the s3 all over, any help?
Click to expand...
Click to collapse
Did you try the two debrick images in my post dated the 22nd March in the thread I posted above?
Actually I also pulled one from my phone after I read you can generate one from Cyanogenmod phones that will also work, I will post that on the above thread also a bit later.
Sent from my Galaxy S4 Mini using XDA Labs
IronRoo said:
Did you try the two debrick images in my post dated the 22nd March in the thread I posted above?
Actually I also pulled one from my phone after I read you can generate one from Cyanogenmod phones that will also work, I will post that on the above thread also a bit later.
Click to expand...
Click to collapse
Just found it, Though if your link would have directed to page 8 rather than 10 that would have been fantastic! I thought You ment the main post which also helped me alot. How ever do I really have to downoad monster legands to be able to download the foking file?
oh never mind, Just a damn ad
IronRoo said:
Did you try the two debrick images in my post dated the 22nd March in the thread I posted above?
Actually I also pulled one from my phone after I read you can generate one from Cyanogenmod phones that will also work, I will post that on the above thread also a bit later.
Click to expand...
Click to collapse
Oh and how do you flash that thing to recovery, How do you pull that debrick file? is really confusing me
And please pardon me if my questions are spammy or annoying, There are a whole lot of steps through it and neither google nor the forum seem to be answering it so I might just consult you for that.
From what I understand, You flash the debrick file to the sd card using this 32 bit sd flasher thing and then it just works because the booting files are on the sd card but it will not boot without it. So how can you fix the corrupted boot loader AND how can I restore my sd card back to normal, I have seen a video for it but he is using ubuntu and command lines and stuff.
Khaled125 said:
Oh and how do you flash that thing to recovery, How do you pull that debrick file? is really confusing me
Click to expand...
Click to collapse
The original post by @ValenteL was a file to generate a debrick image, but you need a working phone to use that.
People with phones that are already bricked have to get a debrick file from someone else. This debrick image must be put onto an 16Gig (some report success with 32gig) SD card that is formatted (so you will lose everything else on it) and then the phone will boot with it instead of internal mmc to get your phone going (you have to keep the SD in) so you can then recover data and also hopefully flash a new rom later so you don't need to always boot from SD.
Sent from my Galaxy S4 Mini using XDA Labs
IronRoo said:
The original post by @ValenteL was a file to generate a debrick image, but you need a working phone to use that.
People with phones that are already bricked have to get a debrick file from someone else. This debrick image must be put onto an 16Gig (some report success with 32gig) SD card that is formatted (so you will lose everything else on it) and then the phone will boot with it instead of internal mmc to get your phone going (you have to keep the SD in) so you can then recover data and also hopefully flash a new rom later so you don't need to always boot from SD.
Click to expand...
Click to collapse
Yes, that was what I understood already but thank you anyway! My question was How? on both creating the debrick file and restoring both sd card (too make it work as a readable card rather than a booting device if it does not already) and fix the phones internal memory without actually reseting the whole phone and if there are no way else to fix internal memory... to back up the whole thing.
thank you!
IronRoo said:
Did you try the two debrick images in my post dated the 22nd March in the thread I posted above?
Actually I also pulled one from my phone after I read you can generate one from Cyanogenmod phones that will also work, I will post that on the above thread also a bit later.
Sent from my Galaxy S4 Mini using XDA Labs
Click to expand...
Click to collapse
WANDEFUL! My phone actually viperated and showed color!
however.. it gives this on a black screen.
boot recovery
check boot partitions
copy from t flash
boot recovery
write 139008
reboot
and obviously reboots, thoughts?
My last two posts are the most important now, if you or any one else can answer that would be fantastic!
some notes: after searching the thing does not mention emmc nor odin at all like for some others with the same issue... just this plain text.
I had upgraded my android version to 4.4.2 not 4.2.2 so I assume that is important, thanks again and please answer as soon as you can as that would be great! thank you for every thing @IronRoo
Khaled125 said:
My last two posts are the most important now, if you or any one else can answer that would be fantastic!
some notes: after searching the thing does not mention emmc nor odin at all like for some others with the same issue... just this plain text.
I had upgraded my android version to 4.4.2 not 4.2.2 so I assume that is important, thanks again and please answer as soon as you can as that would be great! thank you for every thing @IronRoo
Click to expand...
Click to collapse
I think the important thing is the bootloader (& pit must be the same) that if I recall was updated from the version you mention to ver 2. So you need a debrick with the ver 2 bootloader. (but I am not 100% sure about this, only read some stuff last year) My phone BL is ver 1
a guy on the below Mega thread with an I9195 did get a stop further by repeating multiple times
http://forum.xda-developers.com/showthread.php?t=2600976&page=4
But still didn't fix phone fully
read next few pages, one guy used freeze fix white partial success, might be useful if you want to get data off phone.
Also another link that may offer help
but probably your emmc is bad, is my guess
gotta go now, work calls
Sent from my Galaxy S4 Mini using XDA Labs
IronRoo said:
I think the important thing is the bootloader, that if I recall was updated from the version you mention to ver 2. So you need a debrick with the ver 2 bootloader. (but I am not 100% sure about this, only read some stuff last year) My phone BL is ver 1
a guy on the below Mega thread with an I9195 did get a stop further by repeating multiple times
http://forum.xda-developers.com/showthread.php?t=2600976&page=4
But still didn't fix phone fully
read next few pages, one guy used freeze fix white partial success, might be useful if you want to get data off phone.
Also another link that may offer help
but probably your emmc is bad, is my guess
gotta go now, work calls
Sent from my Galaxy S4 Mini using XDA Labs
Click to expand...
Click to collapse
Thats great! good luck at your work, when you are back though I need to tell you this
I have another device of the exact same model that is kikkat not rooted (kitkat will have bootloader version 2 right?) if only I knew how to get the file out and then do all the stuff again, ill keep searching since you are at work now, will keep you updated. please help about it though if you can*
so if someone say for example has android 5 on an s4 mini, he will never get his phone back to work unless some one made a debrick file for it? if the previous statments were true?
My questions are:
Extract that file from the other phone, if I managed to answer it ill tell you.
To get my SD card back to work and fix my emmc
Iam not giving up on my emmc yet though, iam sure there is a way to solve it, if not then how to fix that failed emmc?
thanks again!