Ok, this is as much a heads up to other P780 users as a desperate shoutout for help... I don't think I've seen anybody else with this problem so far, so here goes.
I purchased a P780 in december 2013, loved every bit of it and it worked flawlessly until about 1 month 1/2 ago. The phone was still brand new, but all of a sudden, it decided it will not charge unless I shut it down.
Basically:
- Phone powered ON, no charge, and not recognized when plugged into a computer => nothing happens. The funny thing is if I use the USB OTG cable, it will actually see and read USB flash drives...
- Phone powered OFF, will charge although the screen won't show anything, only the red led will let you know that it is charging. Also, it won't charge past 88%, meaning when I turn it off and charge it, the maximum battery % is 88% even if I let it charge for 2 days...
The phone has been like that for more than a month now... I considered sending it back for repair or exchange, given it's still under warranty but I am afraid to do so, since I would have to send it back to china and the seller who I bought it from won't help.
Ok, so what do you guys suggest I do? Do you think it's hardware related or software related? I am not sure it is hardware since it will actually charge albeit when powered off, and it will see USB flashdrives when using the USB OTG cable...
PS: I am running multinlingual S125 (Chinese P780).
The easiest solution is: Do a factory reset, if not working; Flash another ROM. Still not working? Sent back to service center, probably is hardware issue then.
Well that was my first reaction, when I first noticed it about 1 month 1/2 ago: I directly factory reseted it, which did nothing. I then proceeded to reflash the ROM (Multinlingual S125, Chinese base), which also did nothing. By the way, flashing was a bit of an ordeal since the tel would not be recognized when plugged into a computer. What I did was press Power + Volume Up, after launching flashtool and clicking on download or firmware upgrade. Only then would the computer recognize that something is being plugged in and start the flashing process. May be that info could help other people...
I proceeded to changing base to ROW P780 (using satanduck's ROW S123) a few days ago, in a last desperate attempt that it would change something, but alas... Really though, sending the phone back to China for repair scares the living f**k out of me, I don't even know how to proceed or where to begin...
Same here, i have charging problem with my p780. It wont charge with powered on, and only able to charge when switch it off. Been doing resets and flashes many time since then but nothing can fix my charging issue. Asked several times in local p780 forum including kaskus, also give no solution. I:ve read many complain bout lenovo SC in my country, make me think twice to take my phone there.
Sent from my Lenovo P780 using xda app-developers app
Same here
I have same problem. It's nice to know that phone will be recognized in recovery mode... so I can flash it.. since I have managed to damage its rom, so it wont boot. All in hope to solve this no-charging problem..
Still have same problem, even worse..
I have checked, unforunatly, my PC doesn't register my phone as any device when it's in recovery mode. With that said, I can't flash new rom, or recovery. Now I'm stuck with rom that doesn't boot, TWRP recovery that is incompatible with this phone (so I can't flash another rom), USB connection that makes phone unrecognizible by PC so I can't flash rom/recovery with flashtool..
I have gone to official Lenovo service here in Serbia, but since I have KIT (for China market) version of phone, there is nothing they could do to help. Pretty lame..
dario.alispahic said:
I have checked, unforunatly, my PC doesn't register my phone as any device when it's in recovery mode. With that said, I can't flash new rom, or recovery. Now I'm stuck with rom that doesn't boot, TWRP recovery that is incompatible with this phone (so I can't flash another rom), USB connection that makes phone unrecognizible by PC so I can't flash rom/recovery with flashtool..
I have gone to official Lenovo service here in Serbia, but since I have KIT (for China market) version of phone, there is nothing they could do to help. Pretty lame..
Click to expand...
Click to collapse
Try reinstall drivers for phone. Or try use another PC with different OS (win7 or winxp). Before your phone was recognized on your PC? Did you have installed drivers for phone before?
lenovo P780 Life 07 said:
Try reinstall drivers for phone. Or try use another PC with different OS (win7 or winxp). Before your phone was recognized on your PC? Did you have installed drivers for phone before?
Click to expand...
Click to collapse
I have read almost all topics regarding p780, and have found this post:
http://forum.xda-developers.com/showpost.php?p=52665841&postcount=16
That saved me... I have newer version of P780 that uses newer Preloader.img. That's why I couldn't flash anything. Now I still have that no charging while powered on problem, but at least I have 90% functional phone..
Leaked battery.
If anybody care to know why P780 has this problem. Driven by little madness I opened the device using mini screwdriver. Found lots off white crust on the right lower corner. I can conclude that mine has battery leaking problem which caused it loss 1/3 of its potential. A replacement need to be done by lenovo center.
Kevin Ismail said:
If anybody care to know why P780 has this problem. Driven by little madness I opened the device using mini screwdriver. Found lots off white crust on the right lower corner. I can conclude that mine has battery leaking problem which caused it loss 1/3 of its potential. A replacement need to be done by lenovo center.
Click to expand...
Click to collapse
Thanks for your info. I will check my phone in the morning. :thumbup:
Sent from my SMT TAB 704DC using XDA Free mobile app
Related
Hey guys, I'm new to XDA, I read the rules and everything but I couldn't fix my problem... I rooted my phone with superoneclick thingy... I had the superuser program.. any way, I was bumped when I found out that SE won't bring 2.2 on X10i so I wanted a new 2.2 ROM so I searched and found a thread I can't remember which one but it downloads a file named XAR.rar. It had 4 steps, on step one I don't know what happened but "THE USB DEBUGGING IS OFF AND THE SYSTEM IS BRICKED".
I start the phone, SE appears followed by a logo "docomo NTT" then the screen is pitch black... for several hours... Can't use flash tool, can't use SEUS... etc.
Please, is there a fix!!?
Can you try the suggestions from the following thread & see if it helps:
http://forum.xda-developers.com/showthread.php?t=1156837
Also quoting the actual suggestion made in that post by andrewddickey:
andrewddickey said:
Sounds like what happend to me when flashing custom kernels to MIUI ROMs.
Something wrong with the chargemon with the problem I was having.
But for you. Dunno.
You've tried re-flashing firmware but cannot get flashtool to recognize your phone?
Try taking the battery out, then get flashtool set up, plug everything in and hold the back button, and then put the battery back in and continue to hold the back button.
Sometimes, it takes a bit for the 'puter to recognize the phone with flashtool because it's had the USB ID re-assigned. Mine (on windows 7) will re-install the USB driver when I'm having severe issues.
Click to expand...
Click to collapse
Thanks for replying,
I tried flashtool and it did recognize it... it started but aborted due to "USB DEBUGGING" being unactivated. And now my phone battery is dead "I think" coz after a day and a half staying awake searching and trying stuff, I forgot it open on the dead screen and fell asleep. I woke up with a new problem... red light appeared. I searched for that and it appears to be "since I didn't do anything" the battery is dead. I put it on charger for like 9 hours and I came back and the light's still there. I don't know if the phone IS charging or not. I don't have another way to re-charge the battery except the charger and USB cable.
I have drivers, I have firmwares, I have flashtools... I just need it to work so I can install ANY android version.
japinder said:
Can you try the suggestions from the following thread & see if it helps:
http://forum.xda-developers.com/showthread.php?t=1156837
Also quoting the actual suggestion made in that post by andrewddickey:
Click to expand...
Click to collapse
Thanks Dude, I did it. Phone was dead... charger didn't work... I used usb cable again and it got charged and worked. I flashed it and it's ok. Now it's on charger. Thaaaaaaaaaaaaaaaaaaaaaaaanks
You're welcome.
Nice to be of service.
I have a problem with Galaxy s2. Basically it started to drain my battery like hell.
It gets empty in about 10 hours.
Now when I want to flash the phone once again in order to get everything back as it was when I bought it I cannot. This is due to MTP connection activating itself as soon as I turn on the phone. And I cannot enable usb debugging due to that as it says that I have to remove the USB cable.
In addition my phone charges itself really fast about 2 hours. And when I try to power it on without charger plugged in it gives me charging image and yellow triangle with ! in it and thermometer aside flickering. Does anyone have any ideas how to fix my phone?
Have you tried using CWM to wipe all data + clear all cache, then do a fresh re-install?
Yes I tried it now. It still says my USB is connected when its not. And now it doesnt unlock my sim card.
Factory reset that dont work return phone to a service centre ..
jje
Well thats the case I have voided warranty already. Wondering if there are any chances I could put old rom back before returning it?
Make a DIY USB JIG then flash it back to stock rom and have it checked.
EarlZ said:
Make a DIY USB JIG then flash it back to stock rom and have it checked.
Click to expand...
Click to collapse
Not sure what do you mean by DIY USB JIG but I cannot flash it because I cannot switch USB debugging on... Thats the case it shows me that USB is always connected when it isnt and when USB is connected it doesnt let to switch on USB debugging.
Route is source stock rom and Odin load stock rom into Odin enter download mode on phone and then connect cable and flash rom .
No download mode
http://forum.xda-developers.com/showthread.php?t=819551
jje
JJEgan said:
Route is source stock rom and Odin load stock rom into Odin enter download mode on phone and then connect cable and flash rom .
No download mode
http://forum.xda-developers.com/showthread.php?t=819551
jje
Click to expand...
Click to collapse
Thank you all who have replied. I have now managed to get over the USB issue somehow but still something is wrong either with battery sensor or battery. When I power off my phone it switches on automatically and shows the thermometer and battery charge icon. Anyone else have had this problem? It also charges up to 95% and it bursts to 100% very quickly.
EDIT: Now I tried my friends battery and I did not get the flickering temp error and my friend didnt get it with my battery as well. So something now I'm totally out of ideas.
Service centre .
jje
I am having the same issues here, wonder if the topic creator resolved this in any way? I am thinking of getting a new battery?
Just FYI wear a condom or something on your galaxy S II. As it turns out from service my phone supposedly has liquid damage which does not the warranty apply. I have to pay 240 euros in order to get it fixed :S
Hey Guys.
I had an S1 7 months prior to buying the S2, and have upgraded/fresh installed ROMS many many times over the past year. Once the S1 bricked during an upgrade and I was able to get it into Download Mode without using a micro-USB jig from instructions on this website. If my memory serves me correctly, it was a procedure something fairly simple like hold the Home, Volume Up and Power buttons continuously until the phone goes into forced Download Mode.
However, this procedure doesn't work with the S2 or I'm remembering it incorrectly, and I'm unable to find that instruction webpage again. Now my S2 is almost bricked showing a message I've not seen before, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
So far, I cannot get past this message and Kies 2.0.2.11071_128 doesn't recognize the device nor that emergency recovery is needed.
Unfortunately Samsung programmers haven't been quite smart enough or forward thinking enough to make Kies work from behind a proxy which requires authentication (I live and work on a university campus and the only way to the internet is via proxy and authentication) and it has never shown in the past 9 months of usage that it needs to update itself nor finds any official ROM releases. Therefore I've been forced to use Odin and ROMs from here or samfirmware.com for my updates. Until now, there has never been any major problems that I couldn't get around.
Do any of you have instructions on how I can get my S2 into download mode so as to get Odin to recognize the device? It is not possible for me to make my own JIG here in Thailand as there is nowhere for me to go purchase electronic equipment and parts such as soldering irons and resistors. I am a computer engineer and could easily build such if it were possible to get needed parts.
Thanks hugely in advance for any help offered.
Just order a high from ebay
Sent from my GT-I9100 using XDA Premium App
cmcole101 said:
Hey Guys.
I had an S1 7 months prior to buying the S2, and have upgraded/fresh installed ROMS many many times over the past year. Once the S1 bricked during an upgrade and I was able to get it into Download Mode without using a micro-USB jig from instructions on this website. If my memory serves me correctly, it was a procedure something fairly simple like hold the Home, Volume Up and Power buttons continuously until the phone goes into forced Download Mode.
However, this procedure doesn't work with the S2 or I'm remembering it incorrectly, and I'm unable to find that instruction webpage again. Now my S2 is almost bricked showing a message I've not seen before, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
So far, I cannot get past this message and Kies 2.0.2.11071_128 doesn't recognize the device nor that emergency recovery is needed.
Unfortunately Samsung programmers haven't been quite smart enough or forward thinking enough to make Kies work from behind a proxy which requires authentication (I live and work on a university campus and the only way to the internet is via proxy and authentication) and it has never shown in the past 9 months of usage that it needs to update itself nor finds any official ROM releases. Therefore I've been forced to use Odin and ROMs from here or samfirmware.com for my updates. Until now, there has never been any major problems that I couldn't get around.
Do any of you have instructions on how I can get my S2 into download mode so as to get Odin to recognize the device? It is not possible for me to make my own JIG here in Thailand as there is nowhere for me to go purchase electronic equipment and parts such as soldering irons and resistors. I am a computer engineer and could easily build such if it were possible to get needed parts.
Thanks hugely in advance for any help offered.
Click to expand...
Click to collapse
Well kiss my rosy red butt-cheeks! Speaking from personal experience as tech support, I know empirically to replicate something 52 times prior to asking for assistance. This instance shouldn't have been an exception!
Directly after posting this request for assistance, I decided to try Odin once again and DANGED if this time it found my device even with the "Firmware encountered" error showing. Odin stopped around 90% and forced me to reset my S2, but this time it went right into Download mode with nary a fuss. Now Odin just successfully installed KG6.
So if there is anything to be learned from this experience, either by other users with similar issues or myself, it is "if at 1st you don't succeed, try again and again and again and again."
Hi there, I have a problem. I flashed a ROM and i guess it also flashed a kernel, while im on a locked bootloader... uh oh. The phone can still charge the battery and I get to the SONY logo but nothing after that.
I have tried plugging in a USB cable with VOL - but then windows tells me it cannot recognize the device. I have installed the flashtool drivers and PC companion drivers but no go. Any help would be appreciated.
http://forum.xda-developers.com/showthread.php?t=2775411
Here is a recovery guide
I have tried this method. My problem happens when connecting the device after setting up flashtool. Windows tells me the device could not be recognized (device descriptor request failed), the phone flashes a red led when i plug in the USB cable and then green for a split second right after. then blank nothing, and the error shows up on my desktop.
Mortify1 said:
I have tried this method. My problem happens when connecting the device after setting up flashtool. Windows tells me the device could not be recognized (device descriptor request failed), the phone flashes a red led when i plug in the USB cable and then green for a split second right after. then blank nothing, and the error shows up on my desktop.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2635830
Here is everything you need
I have done all of these steps now and still have the same issue. The drivers installed with no problem when I enabled test signing, but the phone still will not recognize on my computer.
Please join me on https://webchat.freenode.net/ in #xperiaroms maybe we can fix this
Mortify1 said:
I have done all of these steps now and still have the same issue. The drivers installed with no problem when I enabled test signing, but the phone still will not recognize on my computer.
Please join me on https://webchat.freenode.net/ in #xperiaroms maybe we can fix this
Click to expand...
Click to collapse
Im busy right now, try messaging a dev or posting somewhere.
(yay college. Teacher is wondering why im staring at the floor )
Bump. I have a dead phone here, I've tried another computer and I am still getting these errors. I might have to replace the mainboard
we need more info to understand what happened and possible fix... what rom where you using before flash? lb or ub? what rom and kernel did you try to install and how?
ptmaniac said:
we need more info to understand what happened and possible fix... what rom where you using before flash? lb or ub? what rom and kernel did you try to install and how?
Click to expand...
Click to collapse
It's hard to remember, my phone was in for repair for an entire month, but because of one chip on the back plate they deemed the issue a physical problem and didn't cover it under warranty.
I think I was trying to flash back to eXistenz but I believe I flashed a kernel by accident, slip of the hand I guess. I went to restart the phone and it became frozen on the SONY logo. The phone is LB. I just need a fix!
Mortify1 said:
It's hard to remember, my phone was in for repair for an entire month, but because of one chip on the back plate they deemed the issue a physical problem and didn't cover it under warranty.
I think I was trying to flash back to eXistenz but I believe I flashed a kernel by accident, slip of the hand I guess. I went to restart the phone and it became frozen on the SONY logo. The phone is LB. I just need a fix!
Click to expand...
Click to collapse
i think Envious_Data is right, flashing a stock .ftf with flashtool should fix your problems as flashing wrong kernel shouldn't hard-brick your phone, only soft-brick.
But since you can't get your phone properly recognized on the pc you either have a bricked motherboard (i don't think that's the case) or you are having driver issues on the pc (most likely). maybe try flashing on windows xp?
I agree with the above
I followed the instructions provided at the MEGA UNBRICK something thread situated here http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108/
Anyway, when I hold the volume-up button for 10 seconds, followed by plugging the Onyx with the PC, the system does't detect the device. What can I do now? And is there any alternative method to unbrick a hardbricked phone? I urgently need help
If you installed the drivers and the computer is not reckognizing the device, that's bad news. How did you manage to accomplish that?
aredpanda said:
If you installed the drivers and the computer is nota reckognizing the device, that's bad news. How did you manage to accomplish that?
Click to expand...
Click to collapse
I don't know. And ijust in case if you were being sarcastic, I used the same computer to replace the recovery of this phone.
Im not being sarcastic. The problem with the Android modding scene is that people got too used to blindly following steps without really knowing how they are affecting their devices. In order to get better chances at getting help, you'll need to describe what and exactly how you were altering your phone.
aredpanda said:
Im not being sarcastic. The problem with the Android modding scene is that people got too used to blindly following steps without really knowing how they are affecting their devices. In order to get better chances at getting help, you'll need to describe what and exactly how you were altering your phone.
Click to expand...
Click to collapse
I was using Bliss ROM with BluSpark kernel. Anyway, I downloaded 2 ROMS today, Sailfish OS and the stock H2OS for OPX. I wiped the phone and first flashed the Sailfish OS, but the phone was stuck in a bootloop which only was showing the oneplus logo and the text "Powered by Anrdoid". After that, I entered recovery, and did the normal pre-flash wipe again. This time I flashed the H2OS, but after I gave "Reboot to System", my phone just wont do nor display anything. Hardbricked, dead
Can you boot it into recovery? Your bat may be dead from extensively flashing stuff, so plug the phone to the power cable and press and hold VolDown+Power for some good 30s, then you can conclude your phone wont boot into recovery and maybe need an unbrick.
aredpanda said:
Can you boot it into recovery? Your bat may be dead from extensively flashing stuff, so plug the phone to the power cable and press and hold VolDown+Power for some good 30s, then you can conclude your phone wont boot into recovery and maybe need an unbrick.
Click to expand...
Click to collapse
Yeah, it didn't boot into recovery
Does the led light up when you plug the phone to the wall? If it does let it charge for an hour before attempting anything else.
After that and before trying anything else, make sure driver signature check is off and test mode is on. This varies slightly for Windows 7/8 vs 8.1/10. Which version are you running?
aredpanda said:
Does the led light up when you plug the phone to the wall? If it does let it charge for an hour before attempting anything else.
After that and before trying anything else, make sure driver signature check is off and test mode is on. This varies slightly for Windows 7/8 vs 8.1/10. Which version are you running?
Click to expand...
Click to collapse
No, it doesn't
aredpanda said:
Does the led light up when you plug the phone to the wall? If it does let it charge for an hour before attempting anything else.
After that and before trying anything else, make sure driver signature check is off and test mode is on. This varies slightly for Windows 7/8 vs 8.1/10. Which version are you running?
Click to expand...
Click to collapse
I turned off the signature check, W8
If your led doesnt light when your phone is plugged to the wall, this is behind the hard unbricking procedure and your phone is indeed, dead.
Sent from my ONE E1003 using Tapatalk
This issue has been resolved via PM,
Can a mod please close this thread?
No idea what it could be besides corrupt firmware which I've never heard of happening before. The Qualcomm utility should work just fine. Leave it plugged in for an hour or two and see if anything happens
Did you install the qualcomm drivers? If not do it again carefully with driver enforcement off. It works like a charm. Have bricked my device twice as of now and it worked.
Conditon :
Can't boot up into anything (Fastboot, recovery)
No Mi Logo
No Vibration
*Phone goes into EDL WITHOUT having to touch the pins on the mobo*
So, my phone was working like 3 days ago, until today it just went to "Red Light Blinking and Nothing Else", So i searched around the internet and basically on YT i got videos like "Heating up the Power IC Fixes this" but i really didn't wanted to try it so i went again and thought maybe i need to flash the Phone so i downloaded the "Global Stock Rom" so i then took the back cover off of my phone and plugged it the USB Cable and i saw "QualComm HS-USB QLoader 9008" which is right i guess and tried to flash it via MiFlash Tool. And indeed i got error BUT in sequence.
1st one was "cannot recieve hello packet"
which i solved by reconnecting my phone
Then
2nd "Object reference not set to an instance of an object"
I only got this ONCE, searched around again and found out that it's something with WRONG ROM type. So i redownloaded the ROM and got the third error.
3rd "init:storage fail" Which i again searched around and found this could be related to "EMMC Fail" which i have no idea how it went there.
So please if anyone have any info or can lend me some help then please let me know as soon as you can.
Thanks in advance.
(I also have a Note 4 (mido) in the same condition (Red Light Blinking and Nothing Else, it DOEN"T EVEN go in EDL mode)
PRemBh0i said:
Conditon :
Can't boot up into anything (Fastboot, recovery)
No Mi Logo
No Vibration
*Phone goes into EDL WITHOUT having to touch the pins on the mobo*
So, my phone was working like 3 days ago, until today it just went to "Red Light Blinking and Nothing Else", So i searched around the internet and basically on YT i got videos like "Heating up the Power IC Fixes this" but i really didn't wanted to try it so i went again and thought maybe i need to flash the Phone so i downloaded the "Global Stock Rom" so i then took the back cover off of my phone and plugged it the USB Cable and i saw "QualComm HS-USB QLoader 9008" which is right i guess and tried to flash it via MiFlash Tool. And indeed i got error BUT in sequence.
1st one was "cannot recieve hello packet"
which i solved by reconnecting my phone
Then
2nd "Object reference not set to an instance of an object"
I only got this ONCE, searched around again and found out that it's something with WRONG ROM type. So i redownloaded the ROM and got the third error.
3rd "init:storage fail" Which i again searched around and found this could be related to "EMMC Fail" which i have no idea how it went there.
So please if anyone have any info or can lend me some help then please let me know as soon as you can.
Thanks in advance.
(I also have a Note 4 (mido) in the same condition (Red Light Blinking and Nothing Else, it DOEN"T EVEN go in EDL mode)
Click to expand...
Click to collapse
So u cant successfully flash rom using edl mode??
What windows pc u r using 32bit or 64 bit ?
Black_Stark said:
So u cant successfully flash rom using edl mode??
What windows pc u r using 32bit or 64 bit ?
Click to expand...
Click to collapse
I have a 64 Bit Windows 10 with drivers installed, it just get stuck on "init Storage : Fail" after 7 seconds.
I have attached a .log.
PRemBh0i said:
I have a 64 Bit Windows 10 with drivers installed, it just get stuck on "init Storage : Fail" after 7 seconds.
I have attached a .log.
Click to expand...
Click to collapse
Try window driver signature disabled.
Try with diffrent usb ports.
Redownload fastboot rom. Extract it and try.
If still getting storage error then Emmc is dead. Repair it or buy new phone.
Black_Stark said:
Try window driver signature disabled.
Try with diffrent usb ports.
Redownload fastboot rom. Extract it and try.
If still getting storage error then EmmC is dead. Repair it or buy new phone.
Click to expand...
Click to collapse
I've tried a different port and re-downloaded the ROM, but i haven't tried to "Disable Driver Enforcement" yet, But if the EMMC is dead then how do i deal with it? And how does it dies? I was using it like 3 days ago with no problem and suddenly it's just gone.
PRemBh0i said:
I've tried a different port and re-downloaded the ROM, but i haven't tried to "Disable Driver Enforcement" yet, But if the EMMC is dead then how do i deal with it? And how does it dies? I was using it like 3 days ago with no problem and suddenly it's just gone.
Click to expand...
Click to collapse
Its phone . not human body which comes with 80 yrs warranty.
If u r gamer then its faster. It has limited write cycles. Disk can go corrupt and dead. How old u r using phone?
Black_Stark said:
Its phone . not human body which comes with 80 yrs warranty.
If u r gamer then its faster. It has limited write cycles. Disk can go corrupt and dead. How old u r using phone?
Click to expand...
Click to collapse
Okay i understand nothing lasts forever but still there could've been some signs that it might be die some time ,i also have a Moto E (1st Gen) it even has gone through water submersion but still works just as fine but recently it's batter died to i decided to lay it in his grave, but alas it's gone, So i just needed to know if you could let me know What can i do to fix the EmmC? Like any tutorials or something? I also have a Note 4 with the same problem as this. Or maybe i'll just never buy a Mi phone again
But still thanks for your time.
PRemBh0i said:
Okay i understand nothing lasts forever but still there could've been some signs that it might be die some time ,i also have a Moto E (1st Gen) it even has gone through water submersion but still works just as fine but recently it's batter died to i decided to lay it in his grave, but alas it's gone, So i just needed to know if you could let me know What can i do to fix the EmmC? Like any tutorials or something? I also have a Note 4 with the same problem as this. Or maybe i'll just never buy a Mi phone again
But still thanks for your time.
Click to expand...
Click to collapse
Its not harddisk which will give u alert or noisy sound before it dies. Its Sd. Thats the demerits of solid drive.
Emmc means embedded multi media card or disk. Its cant be repaired. It can be replaced in service center. May be.
But better buy new phone.
Nothing wrong in buying xiaomi phone.
Most problems happen when u stay on miui and keep doing OTA update for entire life which creates lots of bugs and issues.
U must do factory reset once in a six months. Or flash fastboot rom clean all flash using computer is best to keep phone healthy. Its not true that stock rom is always best. Sometimes its bloated and hogs ur phone like hell like miui.
So installing Custom debloated roms are best here to keep rom smooth running and increasing phones health.
Only upgrading using OTA is not good. Userdata and internal sd must be wiped after few months to clear bugs.