Hello,
Due to the 10 post threshold I am unable to post in the "Samsung Captivate -
Captivate Android Development
[Guide] Encryption Unsuccessful - Reset Android [ICS Issue]" thread.
I have resolved this issue a couple months back.
So, due to the time that has gone by it is a little difficult to explain what I did.
Last night I reproduced the issue, but after a restore, I'm good as new.
So now I am compelled to post this here. Being a "noob" and like I said not able to completely remember what "exactly" was done to accomplish the fix.
I am willing to share any information you wish.
But in a nutshell, I flashed ( a ROM I can't remember at the moment, but I'm sure I will once I get down to it. at work and pressed for time, "lunch time" ) using Heimdall, then downloaded the rom "Imfinitum-blue-v1.1.0 to my external SD, ( using a 34 Gb SD card, seems that is the only card that I could use. From what I remember anyway. ) Mod version "aokp_galaxysmtd_milestone-4"
The kernel version currently being utilized on this device is "[email protected] #1.
Sorry for being so confusing, and vague, but I really wanted to get something out there. I see they are still working on a fix for this issue, I found this resolve before page 30, it's now at 57, and after recreating the issue and then resolving it after a restore.
So, ask any question you want and I will be happy to help.
Hope this helps.
Take care.
By "fixed" do you mean:
a) You have restored access to your INTERNAL sdcard?
b) You have used the emmc/sdcard swap method to use your external as the internal? (ie. your internal sdcard is still not useable)
It would help if you could mention whether your internal card is back in play. And esp. if you were able to access the data that was on there - ie. before you experienced the EU issue.
Or did using Heimdall wipe the internal sdcard - ie. yet you're now able to use the internal though?
Hello,
Because this would save a lot of people's phones including mine, would be great if you post your steps so we can follow.
Take this with a grain of salt guys.
There is very little information in his post, which is his very first post. There is also no information about the process he used. I'm not sure what a 34gb SD card is. I believe the methods he alludes to have been tried by other members with no resolution.
I have a feeling he had a different issue or is just trying to get attention.
For all our sakes I hope I'm just rushing to judgement.
I guess what we want to know is, what have you done?
Say you just got the Enc Unsuccessful screen, turned off the phone and then what?
He's to shy to give anymore details.
Sent from my SGH-I897 using xda premium
yosup said:
By "fixed" do you mean:
a) You have restored access to your INTERNAL sdcard?
b) You have used the emmc/sdcard swap method to use your external as the internal? (ie. your internal sdcard is still not useable)
It would help if you could mention whether your internal card is back in play. And esp. if you were able to access the data that was on there - ie. before you experienced the EU issue.
Or did using Heimdall wipe the internal sdcard - ie. yet you're now able to use the internal though?
Click to expand...
Click to collapse
I just duplicated the issue again, "no sdcard found"..etc... then using did a restore ("Semaphore CWM Recovery v5.5.0.4" by the way) restored the Captivate right back. After it boots I get "prepairing sdcard" then everything is back to normal.
Answer to "a." Yes, full access to both External and Internal drives. Also can mount and unmount all /system, /cache, /datadata, /sdcard, /data, /emmc.
Answer to "b." Sorry, can you elaborate on this. I'm just now sure what you mean by "swap"
You said: "It would help if you could mention whether your internal card is back in play. And esp. if you were able to access the data that was on there - ie. before you experienced the EU issue."
Now here it's difficult to say, I formatted and haphazardly (sorry, dumb I know!) flashed so many times attempting to get back control of this thing, I don't know. Google will restore my apps like before but I disabled this function. However it will detect application updates same 5 updated every time I restore it.
You said: "Or did using Heimdall wipe the internal sdcard - ie. yet you're now able to use the internal though?"
Damn!, I'm just not sure, I'm really sorry but I wish I would have THOUGHT of posting HERE before YESTERDAY!...
Now is there a log file I can send out? So people can see whats going on inside this thing. Like I said so much time has gone by, and once I was able to get the camera working and transfer apps to the external card, and all that I basically went numb and stopped messing around. And I would like to point out, that
"Encryption Unsuccessful" crap ( and knowing better, I DID press Restart by the way) started just a couple days before this thread started. So just to give you an example as to how long this frustration was. I became obsessed, I worked on this phone for most all my waking hours, and I'm sure some of you have, "dreamed" of possible fixes as well!.
If it wasn't for the 10 post threshold I could have been more help. I read every single post in this thread up to the point where I fixed the problem.
Had it all in my head at the time but when I found I couldn't post with-in the >>Encryption Unsuccessful<< thread?! I wasn't sure why.
I even started a separate identity ( Barney Fyfe ) thinking that would allow me to post something.
And from what I read at the time, I thought, rather understood it to mean that I was locked out by some Admin here... Or ?!
Sorry, really, I did not realize I had to get 10 or more posts >>here<<
You know I'm sure I can get details on pretty much exactly what I did. Right now I'm at work, so I'll need a little more time.
Wdustin1 said:
He's to shy to give anymore details.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
No just very busy. I just posted this yesterday!?
Wadda' ya want from me eh!?..............
swayjd said:
I guess what we want to know is, what have you done?
Say you just got the Enc Unsuccessful screen, turned off the phone and then what?
Click to expand...
Click to collapse
Read my first reply.
I did so much to find a resolve, none of the suggestions I tried in the "Encryption Unsuccessful" thread worked at all by the way. didn't attempt EVERY suggestion, but a lot of them.
I'm going to attempt to get the horrifying memories back!
Oh, now here is an odd change in event, not sure if this is related or not but I just realized last night that the phone won't charge, using three different batteries, all fairly new, nor is it being recognized USB wise.
I have a couple other Captivates I'm now having to use to charge my batteries for this one.
It's like the micro usb is damaged?
I'm usually very careful on how I insert them, 4 different cables too. That all work with the other Captivate. It's bricked but does charge the battery.
It's a GT-19000.
Oh and I almost forgot!!
The Samsung Galaxy S SGH-897/Captivate I'm using is fairly new, the date code is " 1111 "
Red_81 said:
Take this with a grain of salt guys.
There is very little information in his post, which is his very first post. There is also no information about the process he used. I'm not sure what a 34gb SD card is. I believe the methods he alludes to have been tried by other members with no resolution.
I have a feeling he had a different issue or is just trying to get attention.
For all our sakes I hope I'm just rushing to judgement.
Click to expand...
Click to collapse
RELAX! I'm not playing around.
It's comments like this that kept me from being more proactive in posting in the first place!
Good lord!!
See, now you could have waited at least another day before this flaming!
Losing interest in this now. I was trying to help.
- - - - - - - - -
Hey people, my name is Pat Doherty.
Because of this dork I'm about done. I Do not NEED this kind of thing. I got my own stresses to deal with these days. And don't need some immature nerd slamming my attempt at helping out here.
I can be reached if you put anything you want in front of patdoherty dot net.
my site patdoherty dot net.
c'ya!
P.S.
You said:
"I'm not sure what a 34gb SD card is."
Really now!?
Are you serious!?
A SanDisk 32GB micro SD chip, "32gb" ( screen printed right on the chip ) = 32 gigabytes
Barney Fyfe said:
RELAX! I'm not playing around.
It's comments like this that kept me from being more proactive in posting in the first place!
Good lord!!
See, now you could have waited at least another day before this flaming!
Losing interest in this now. I was trying to help.
Click to expand...
Click to collapse
but dude, you gave us nothing.
please as another noob could you post exact details of your discovery? like what you did to get the inscription unsuccesful to come up repeatably,and what did you do get your phone to access the internal memory? an what exactly did you flash to get it all to work
You brought up a fix to an issue that is getting very high attention right now. You were not able to tell people how to recreate the fix. People are looking for a scientific method (think repeatable steps) to fix this issue that is affecting quite a few people.
I'm sorry if I hurt your feelings. I've been watching the Encryption Unsuccessful thread for a very long time. I was stating only what I observed. There have been others who had suggested a similar fix, but it has not been repeatable.
You are a talented artist and obviously have alot going on. I hope for others' sake you can give them some steps to follow. If so, you may just be the "chosen one"
Barney Fyfe said:
It's comments like this that kept me from being more proactive in posting in the first place!
Losing interest in this now. I was trying to help.
Click to expand...
Click to collapse
First of all, I'll commend you for sharing a positive outcome despite experiencing this dreaded issue. However, this is something being dicussed at the DEV thread level, which assumes a deeper level of detail than the average General or Q&A topic.
Serious people are giving serious consideration to the matter. Example, Woodrube is a well respected Vibrant / Transformer / Nook user, and he's invested a lot of time collaborating with Captivate users to pool our resources and build our knowledgebase here.
Whether you continue your participation is up to you. Hopefully your method will be a viable part of the discussion.
Barney Fyfe said:
I did so much to find a resolve, none of the suggestions I tried in the "Encryption Unsuccessful" thread worked at all by the way. didn't attempt EVERY suggestion, but a lot of them. I'm going to attempt to get the horrifying memories back!
Click to expand...
Click to collapse
Barney Fyfe said:
You know I'm sure I can get details on pretty much exactly what I did. Right now I'm at work, so I'll need a little more time.
Click to expand...
Click to collapse
Regardless how anxious we get, life always comes first. Take care of business. Just keep in mind that a lot of XDA veterans are putting their minds to this issue, and more details will help isolate the cause & effect. In general, details on your ROM, kernel, and any specifics would be helpful.
Barney Fyfe said:
I just duplicated the issue again, "no sdcard found"..etc
Click to expand...
Click to collapse
By saying "duplicated the issue", we're all going to assume you encountered the "Encryption Unsuccessful" screen again. Do you recall any specific steps you took to "duplicate" this issue? Since you were able to duplicate it several times, people troubleshooting the issue will benefit to know how you induced the matter. The goal is to discover what actually triggers this. Then, we'll get closer to finding a resolution.
Were you using the phone at the time - ie. the EU randomly appeared? Did it just reboot on its own and result in a dimmed boot animation screen? After you hit "reset," did you simply go into recovery and perform a NANDROID restore? Was there anything specific you did after getting the EU screen? Battery pull, reboot into recovery, flash other roms or kernels, etc? Did you previously connect it to your PC using MTP?
Barney Fyfe said:
... then using did a restore ("Semaphore CWM Recovery v5.5.0.4" by the way) restored the Captivate right back. After it boots I get "prepairing sdcard" then everything is back to normal.
Yes, full access to both External and Internal drives. Also can mount and unmount all /system, /cache, /datadata, /sdcard, /data, /emmc.
Click to expand...
Click to collapse
It seems you "resolved" your issue by simply doing a NANDROID restore via recovery. Was it really that simple? Or was there anything else (other roms or kernels flashed) prior to doing the restore.
If this is the case, then your experience starkly contrasts what most others have experienced - ie. no longer having access to the internal sdcard even in recovery (so a saved NANDROID backup wouldn't be accessible, etc).
Barney Fyfe said:
Answer to "b." Sorry, can you elaborate on this. I'm just now sure what you mean by "swap"
Click to expand...
Click to collapse
The "swap" is the work around being used to swap emmc & sdcard in vold.fstab - ie. to then have the phone recognize the external sdcard as the internal (since the internal sdcard is no longer accessible for 99.9% of the others with this issue).
Barney Fyfe said:
Now here it's difficult to say, I formatted and haphazardly (sorry, dumb I know!) flashed so many times attempting to get back control of this thing, I don't know.
And I would like to point out, that "Encryption Unsuccessful" crap ( and knowing better, I DID press Restart by the way) started just a couple days before this thread started. So just to give you an example as to how long this frustration was. I became obsessed, I worked on this phone for most all my waking hours, and I'm sure some of you have, "dreamed" of possible fixes as well!.
Click to expand...
Click to collapse
Everyone who's gone through this has experienced that same level of dread and anxiety. We can all relate.
Thanks for the nod my friend and I am still on the case but as you say life comes first.
There have been some developments in the SGSII threads that I'll post in the Dev thread.
Barney Fyfe said:
Hello,
Due to the 10 post threshold I am unable to post in the "Samsung Captivate -
Captivate Android Development
[Guide] Encryption Unsuccessful - Reset Android [ICS Issue]" thread.
I have resolved this issue a couple months back.
So, due to the time that has gone by it is a little difficult to explain what I did.
Last night I reproduced the issue, but after a restore, I'm good as new.
So now I am compelled to post this here. Being a "noob" and like I said not able to completely remember what "exactly" was done to accomplish the fix.
I am willing to share any information you wish.
But in a nutshell, I flashed ( a ROM I can't remember at the moment, but I'm sure I will once I get down to it. at work and pressed for time, "lunch time" ) using Heimdall, then downloaded the rom "Imfinitum-blue-v1.1.0 to my external SD, ( using a 34 Gb SD card, seems that is the only card that I could use. From what I remember anyway. ) Mod version "aokp_galaxysmtd_milestone-4"
The kernel version currently being utilized on this device is "[email protected] #1.
Sorry for being so confusing, and vague, but I really wanted to get something out there. I see they are still working on a fix for this issue, I found this resolve before page 30, it's now at 57, and after recreating the issue and then resolving it after a restore.
So, ask any question you want and I will be happy to help.
Hope this helps.
Take care.
Click to expand...
Click to collapse
thinks, I wanna try it on t959 with the EU bug.
USB problem
Hello, the same happens to me an hour ago. No charging no connection to computer but if the phone is powered off as soon as I connect the charger the phone boots up but no charge.
Captivate with CM9.
Barney Fyfe said:
Oh, now here is an odd change in event, not sure if this is related or not but I just realized last night that the phone won't charge, using three different batteries, all fairly new, nor is it being recognized USB wise.
I have a couple other Captivates I'm now having to use to charge my batteries for this one.
It's like the micro usb is damaged?
I'm usually very careful on how I insert them, 4 different cables too. That all work with the other Captivate. It's bricked but does charge the battery.
It's a GT-19000.
Oh and I almost forgot!!
The Samsung Galaxy S SGH-897/Captivate I'm using is fairly new, the date code is " 1111 "
Click to expand...
Click to collapse
What the OP said seems more of luck.
B.S. ALERT!!!!
I cant believe i actually came back to this thread to waste my time again!!, reading a thread that is supposed to help fix a problem i am afflicted with, but is instead filled with A BUNCH OF [email protected]$%@# [email protected]#@#$T!!!!!
Dude, if want to help people you must understand that in order to do this you need to explain "exactly" what it is you are talking about. No one can trust your information based on your "belief" in it. Software is a very techinical thing, which means to explain it you need to speak in technical terms. If you cant do that, do some more reading. Otherwise you arent helping anyone but yourself....Thanks, but NoThanks.
I was wondering if anyone had any info on the status of roms for the Behold II. I just got one, used but in very good shape, and I am trying to get it to work better. I am fairly sure these phones were pretty popular, and I can't believe they were (almost) completely ignored. I found a pretty nice clean android 1.6 rom that I threw on it, but it has no vibrate.
Does anyone know of any stable gingerbread roms for this phone? If not, anyone know how to get vibration to work? Is there anyone out there willing to work on this phone at all?
Or can anyone point me in the direction of some information on taking the rom apart and figuring out how to get the vibration working? Basically I need to find out how to take apart a rom, then figure out how to get vibration working properly. It's driving me nuts that the phone doesn't vibrate when I get calls/texts.
Isn't that Donut? *throws up*
Couldn't find any ROMs above 1.6 with some googling. Its also likely that you would not be able to fix the vibrate issue, if the Dev couldn't. If you want to "take the ROM apart," just take the .zip file and unzip it.
But I recommend getting a new phone.
Sent from my Nexus 4 using xda premium
It is indeed Donut. That's why I wanted to try and find a gingerbread rom or figure out how to make my own.
I unzipped the rom and dug around in there. I found some other thread on these forums about vibration and the symlinks and vibrate.ko. I checked in init.rc (on the phone) and found some lines about inserting modules relating to VibeTonez and the module "vtmdrv.ko" but I don't know if it is commented properly or turned on or symlinked or whatever. I see nothing about an actual vibrate.ko or anything.
How do I check my updater-script for the correct symlink?
I found this thread that has given me some interesting information: http://forum.xda-developers.com/showthread.php?t=1946614
and also this one: http://forum.xda-developers.com/showthread.php?t=1405366
Thanks for the interest! Unfortunately, I cannot just get a new phone. I am basically stuck with this one for the foreseeable future.
nookle said:
It is indeed Donut. That's why I wanted to try and find a gingerbread rom or figure out how to make my own.
I unzipped the rom and dug around in there. I found some other thread on these forums about vibration and the symlinks and vibrate.ko. I checked in init.rc (on the phone) and found some lines about inserting modules relating to VibeTonez and the module "vtmdrv.ko" but I don't know if it is commented properly or turned on or symlinked or whatever. I see nothing about an actual vibrate.ko or anything.
How do I check my updater-script for the correct symlink?
I found this thread that has given me some interesting information: http://forum.xda-developers.com/showthread.php?t=1946614
and also this one: http://forum.xda-developers.com/showthread.php?t=1405366
Thanks for the interest! Unfortunately, I cannot just get a new phone. I am basically stuck with this one for the foreseeable future.
Click to expand...
Click to collapse
No prob. Always interested in the legacy devices.
I wouldn't try to fix the vibrate, the developer himself states it will likely never be fixed (http://androidforums.com/behold-2-all-things-root/54769-port-galaxy-1-6-behold-2-final.html). I didn't read into the thread, but usually some user asks why vibrate doesn't work, dev explains, etc. You don't know if the problem with the ROM is the same as the issues found in the threads you searched.
If you want Gingerbread, it looks like the device is pretty much dead, however you can port CM7 from a similar device. It would be quite a chunk of work though.
Sent from my DROID2 using xda premium
Yeah, I have been going over all those threads that have that guy's roms. He made a few of them for this phone, and I am trying to find one that is better. Or the best of them.
I think I may have found a pretty major bug in the one I have, though. I got a call, I didn't want to answer it, and I hit the volume down button to silence the ringer, but it force closed android.phone.com and dropped the call. That wasn't cool.
I am also (kind of half-heartedly) pursuing creating my own rom from scratch. It's quite daunting, but I have a lot of time for the next week or so. My sister is having a complicated pregnancy so I am spending a lot of time at the hospital. There are plenty of guides and tutorials for beginners, so I am reading those and trying to figure things out.
Or I can figure out how to work on the rom this guy made, that would make life much easier.
nookle said:
Yeah, I have been going over all those threads that have that guy's roms. He made a few of them for this phone, and I am trying to find one that is better. Or the best of them.
I think I may have found a pretty major bug in the one I have, though. I got a call, I didn't want to answer it, and I hit the volume down button to silence the ringer, but it force closed android.phone.com and dropped the call. That wasn't cool.
I am also (kind of half-heartedly) pursuing creating my own rom from scratch. It's quite daunting, but I have a lot of time for the next week or so. My sister is having a complicated pregnancy so I am spending a lot of time at the hospital. There are plenty of guides and tutorials for beginners, so I am reading those and trying to figure things out.
Or I can figure out how to work on the rom this guy made, that would make life much easier.
Click to expand...
Click to collapse
I wouldn't try to make a ROM from scratch. A better thing to do would be to port. Basically find a ROM made for a phone with similar internals (type of CPU and RAM) and port the ROM. Much easier than making a ROM from scratch which requires knowledge of a few computer languages (mainly java). There are a few porting guides available on the forum.. Lemme find a link
Sent from my Nexus 4 using xda premium
Hey, thanks for your help! It's much appreciated! And believe me, if I could get a new phone I would. This phone is on my parent's plan, and only used for calling and texting family. I can't use data or anything. At this point it's more for the sake of learning about how to build an android operating system than anything else. I just want a nice, stable, useful phone that is better than the old school flip phones (of which I have had quite a few over the years).
Once again no prob. I used a legacy device just last year but it had quite some development so all I had to do was flash Roms lol.
Anyways this is how you compile GB
http://forum.xda-developers.com/showthread.php?t=1183832
And this is how you port. I would port from a similar device like the My touch 3g
http://forum.xda-developers.com/showthread.php?t=1598713
Sent from my Nexus 4 using xda premium
Haha yeah I am in the same boat with my nook. I have been following the devs over in the nook sub-forum for a couple years now. I have had several iterations of gingerbread, a couple of ics, and now a few of jelly bean. I am used to just slamming the rom zip on the sd card and booting into recovery and flashing it over.
For this phone I had to do odin, which was a new experience for me. Went pretty painless, and I figured it out. I prefer the recovery method over odin.
I have one question about the second link, about porting. It says in the first post that if you don't have gb already compiled for your (my)device that guide is useless for you (me). Is that what the first link is for? Compiling specifically for my device? What if my device is not supported at all? Do I just pick a somewhat similar phone, compile, port, make a flashable rom, and put it on the phone and hope it doesn't brick it?
Yep thats what the first link is for. Don't compile and port for a different device, that is a sure way to brick your phone.
Is your device not supported at all? Usually legacy devices are since back then (lol) there weren't a whole ton of Android phones
Sent from my Nexus 4 using xda premium
I don't know if my device is supported or not. I have not got to that part in the guide yet. I will report back if it is or isn't.
Sorry for not getting back earlier, I've been real busy the past week or two.
I finally got ubuntu set up on a computer, and was following the first guide and ran into a few problems.
First, I wasn't able to install all the required packages. If you want to know what ones they are I wrote them down. Not sure how essential they are in the grand scheme, but they weren't available.
Second, I tried to install java and ran into a problem adding the repos for it. The second one, for src, would not work at all. So I went on sun's or oracle's website and downloaded the linux package and installed it. But apparently it didn't work because all I get after trying to lunch are lots of these:
Code:
/bin/bash: java: command not found
Basically anywhere it tries to use java I get those messages. Eventually it gives up and says I have
Code:
version: /bin/bash: java: command not found
and I should have
Code:
version 1.6
Third, after I issue
Code:
source build/envsetup.sh
I see it includes some devices, like htc passion and samsung crespo4g and samsung crespo. Is this normal?
Fourth, When I do lunch I get five options
Code:
1. generic-eng
2. simulator
3. full_passion-userdebug
4. full_crespo4g-userdebug
5. full_crespo-userdebug
Should I just pick generic-eng?
I will be out of town all week for work, and won't have access to the computer I am doing all this on. For the life of me I cannot get unbuntu to install on my laptop. Never did like ubuntu, always favored fedora.
Anywho, thanks for any suggestions.
Well first of all hi to all, and thanks for taking the time of reviewing this,
I cant seem to find an answer anywhere so literally any information on the subject would be apreciated.
I own a ntt docomo fujitsu arrow s, The phone has been working flawlessly for so long
so much that i just never consider even doing a backup, now im literally facing hell
Well ill try to explain my problem also keep in mind im not really good with android, but i fix pcs so i get some stuff.
Okay ill start, one day my phone was working as ussualy and i went to the gallery as always and i had the external storage not available message,
so then i went to storage and it reflected that my internal storage was 0.0g.
So the thing is, apparently my data is still there, my apps are there, my wallpaper didnt switched, just like my ringtones, also if i go to
clean master and in settings-apps my apps and the storage i had before the incident was exact, as in i had 18g of used memory and it still reflects me that,
but certain apps like file explorer dont show anything , i literally dont have anything in my storage, idk what to think of this.
Also ill post some extra information because if anyone have any info i guess you will need more info from my side.
If i connect the phone to usb storage , it reflects me my internal storage is at 0.0g and nothing is inside.
Ive never rooted and never even tried.
I didnt install anything lately that may cause a hardware change.
The phone didnt fall, didnt got wet.
i think the sd card was in the internal storage, as an emulation, i thik idk much about that. (but i never used one, just the internal storage)
If i try to mount an sd it just doesnt happens the only thing i can do sd wise is erase all data in the sd
So basically now idk what to do, i wish i could keep my stuff, idk its still there, i guess the term for this is my storage unmounted, so using adb to mount it back would work?
idk i also did the putting it in tmp and disconecting it and nothing im literally going insane and have slept like 2 hours per day, so thanks for taking your time to atleast review my problem
also sorry for the bad formatting, english isnt my native language.
Hi,
You have already made a post here on same topic. please do not make multiple posts/threads of same topic. wait for the experts to answer question.
Thread Closed.
Greetings. I've been trying to remove those sounds by myself, but it seems that I will need some help/advice on that.
First - it's a Mi4c, running lollipop 5.1.1, MIUI 7.4 /6.5.5 | Beta.
The device is not rooted (yet :angel: ). The reason "why" mostly comes from the old saying "If it ain't broken - don't fix it". Lately I've been using a rooted phone for the past 3 years and I don't really saw much benefits for my type of abusing so I've been perfectly happy with the new device without the extra power, so I haven't decided yet. Partly this, and partly the valid warranty
I have found the apk-file, where the two sounds are located, extracted them and left the copies blank. The problem comes when I try to replace the originals with the ones I have made. Now, I know that some of the properties of the files have changed, but I wanted to try this easy fix anyway. But the MIUI isn't letting me maybe because I am not rooted yet.
The question is - is there another workaround for that little sound problem, or I should dig deeper and try to root the phone?
Thank you in advance for your time reading this.
I am sorry, but this thread seems to be doubling an older one. I don't know how it slipped through my searches, but apparently I haven't used the right search words
This can be merged, locked or deleted without hesitation. Thank you.
Thread closed as a duplicate of http://forum.xda-developers.com/mi-4c/help/charging-notification-sounds-t3371467