Good night, install the mod Sound Project Meli and my radio no longer works opens but does not sound like to know how to uninstall the mod and return to the original thanks.
soujirock said:
Good night, install the mod Sound Project Meli and my radio no longer works opens but does not sound like to know how to uninstall the mod and return to the original thanks.
Click to expand...
Click to collapse
Assuming the mod did in fact break your radio, the easiest way to fix this is to simply dirty-flash the ROM and Gapps, then flash whatever else you need back.
kentexcitebot said:
Assuming the mod did in fact break your radio, the easiest way to fix this is to simply dirty-flash the ROM and Gapps, then flash whatever else you need back.
Click to expand...
Click to collapse
means I have to flash the rom again but without any wipe?
soujirock said:
means I have to flash the rom again but without any wipe?
Click to expand...
Click to collapse
Yes. Just need to wipe dalvik/cache.
But if it's still messed up, then you need to backup your stuff and clean flash.
kentexcitebot said:
Yes. Just need to wipe dalvik/cache.
But if it's still messed up, then you need to backup your stuff and clean flash.
Click to expand...
Click to collapse
ok thanks i will try
Related
my phone for some reason i turned it on and the phone app wasnt there so i cant dialer a number to call.I am running on DC 2.09.1 is there anything i can do?? If not could unroot my phone and take the davilk-cache and they not know my phone was rooting,rommed, partitioned, or overclocked??
damage rom is pretty outdated. try to flash a different current rom. taking the phone back because of a faulty custom rom is stupid.
fixxxer2008 said:
damage rom is pretty outdated. try to flash a different current rom. taking the phone back because of a faulty custom rom is stupid.
Click to expand...
Click to collapse
no its every time a flash the rom or a older version of the rom the phone apk is gone i think it is more than just the rom but i will try
ok i am trying the NFX-Hero 2.2.1 ODEX rom to see if that works
xxxk15 said:
ok i am trying the NFX-Hero 2.2.1 ODEX rom to see if that works
Click to expand...
Click to collapse
do a full wipe before you flash a new rom.
fixxxer2008 said:
damage rom is pretty outdated. Try to flash a different current rom. Taking the phone back because of a faulty custom rom is stupid.
Click to expand...
Click to collapse
thanks man it worked!
fixxxer2008 said:
do a full wipe before you flash a new rom.
Click to expand...
Click to collapse
yep always do
I flashed a sound mod that I'm not sure is having any effect, and would like to un-flash it. Is there such a method to doing so?
First...make sure you do a nondroid backup before u flashe anything...
Second...if you run a custom Rom just dirty flash the Rom one more time it will overwrite that sound mod...
99piotrek said:
First...make sure you do a nondroid backup before u flashe anything...
Second...if you run a custom Rom just dirty flash the Rom one more time it will overwrite that sound mod...
Click to expand...
Click to collapse
Sorry, I'm kind of new at this, but what does that mean? Wouldn't you lose all of your data and settings and stuff? Or does a dirty flash just overwrite all of the installed mods and none of the data?
Bseagull said:
Sorry, I'm kind of new at this, but what doesat mean? Wouldn't you lose all of your data and settings and stuff? Or does a dirty flash just overwrite all of the installed mods and none of the data?
Click to expand...
Click to collapse
Exactly...dirty flash mean you gonna keep all the settings all installed apps...
You gonna lose all extra mods you installed after you had flashed the rom the first time...
Also if you need after flashing Rom you can create backup on recovery...
You can do that after flashing every mod or theme...
So then you have sure that you can easily return to the "before" configuration if you don't like something you flashed...
Hi, sorry if this is in the wrong place, XDA won't let me post to the mahdi thread because I'm new.
I clean flashed the 6/28 Mahdi Rom for my Vs980 and audio didn't work whatsoever. Everything else was fine. Here are a couple of examples of what I mean:
Poweramp play button will be clickable but will return an error and revert to the play button
Youtube will constantly prepare to play (load, attemp to play then continue to load again)
Placing phone calls results in a black screen, then call ended screen 20 seconds later
Receiving phone calls don't show up, rings once (on the phone placing the call not my vs980) then goes to voicemail
Volume up and down doesn't give tones.
Apollo player gives "DSP manager crashed" errors
I tried freezing DSP manager, but that didn't work.
I should also mention I didn't restore using titanium, I tried reflashing 3 or 4 times, and I used the PA 4.4.4 gapps.
I can't find anyone else with this issue, hopefully someone knows what's up.
Thanks for helping if you respond!
Have you tried a different rom? One specifically for our service. I know Mahdi is compatible, but just to see.
Sent from my VS980 4G using XDA Premium 4 mobile app
[removed reply, see below]
njstein said:
Have you tried a different rom? One specifically for our service. I know Mahdi is compatible, but just to see.
Click to expand...
Click to collapse
Yes I have, I'm currently running a 4.4.2 build of Mahdi that works fine (2.4-g2-20140211). It's just the 6/25 and 6/28 that have the audio issues for me.
Nextcue said:
Yes I have, I'm currently running a 4.4.2 build of Mahdi that works fine (2.4-g2-20140211). It's just the 6/25 and 6/28 that have the audio issues for me.
Click to expand...
Click to collapse
Huh, that's weird. You probably can't post in that for trouble shooting, so have you tried a different gapps? Maybe PA is doing something? Banks gapps is an excellent package (just keep the convo going so you can hit 10 posts).
Here's a link to Banks:
http://forum.xda-developers.com/showthread.php?t=2012857
Sent from my VS980 4G using XDA Premium 4 mobile app
njstein said:
Huh, that's weird. You probably can't post in that for trouble shooting, so have you tried a different gapps? Maybe PA is doing something? Banks gapps is an excellent package (just keep the convo going so you can hit 10 posts).
Click to expand...
Click to collapse
Hmm, I'll check that out when I get a chance. Thanks so much for replying
Nextcue said:
Hmm, I'll check that out when I get a chance. Thanks so much for replying
Click to expand...
Click to collapse
I guess you are on the stock unmodded Kit Kat modem right?
JRJ442 said:
I guess you are on the stock unmodded Kit Kat modem right?
Click to expand...
Click to collapse
Maybe, how would I find out? When I first rooted I flashed Mahdi over 24a I think.
Nextcue said:
Maybe, how would I find out? When I first rooted I flashed Mahdi over 24a I think.
Click to expand...
Click to collapse
How did you get to 24A? If it was from an OTA its the stock modem. Post a picture of your baseband if you can
JRJ442 said:
How did you get to 24A? If it was from an OTA its the stock modem.
Click to expand...
Click to collapse
It was the OTA, so yes it is the stock modem.
Nextcue said:
It was the OTA, so yes it is the stock modem.
Click to expand...
Click to collapse
The current build you're on where everything works shouldn't even boot if you're on 24A. As old as that build is(2.4), its still using the JB kernel, requiring the 12b radio. I think you should go to the Malladus thread, download his baseband updater, and the ROM. And flash that. It should straighten out whatever happened. Some sound drivers are tied in with the modem/baseband for some reason on KK. That's what makes me think something with the baseband is messed up. I think I have the Malladus stuff in my Dropbox if you want links. After you get a good GPS lock in maps with Malladus. Then flash the newest build of Mahdi, not the 2.4 build you're running.
JRJ442 said:
The current build you're on where everything works shouldn't even boot if you're on 24A. As old as that build is(2.4), its still using the JB kernel, requiring the 12b radio. I think you should go to the Malladus thread, download his baseband updater, and the ROM. And flash that. It should straighten out whatever happened. Some sound drivers are tied in with the modem/baseband for some reason on KK. That's what makes me think something with the baseband is messed up. I think I have the Malladus stuff in my Dropbox if you want links. After you get a good GPS lock in maps with Malladus. Then flash the newest build of Mahdi, not the 2.4 build you're running.
Click to expand...
Click to collapse
Thank you so much, links would be very appreciated.
JRJ442 said:
The current build you're on where everything works shouldn't even boot if you're on 24A. As old as that build is(2.4), its still using the JB kernel, requiring the 12b radio.
Click to expand...
Click to collapse
Also I just checked, definitely still on the 12b radio.
Nextcue said:
Thank you so much, links would be very appreciated.
Click to expand...
Click to collapse
First question, are you using TWRP? The wipe instructions below are for TWRP
Here's the ROM https://copy.com/PDixihCzNxqLSBp
Here's the baseband updater https://copy.com/mVY1Qi2cVg3EgXS and the md5 is 941f657383ab5a6ddc8c6f4c0ee4183c make sure t matches before you flash.
Reboot to recovery and flash the baseband updater. Then hit the back button. Select wipe -> advanced wipe. Select dalvik, cache, system, data. Be absolutely sure you don't select internal. Flash Malladus and whatever gapps you prefer.
JRJ442 said:
First question, are you using TWRP? The wipe instructions below are for TWRP
Reboot to recovery and flash the baseband updater. Then hit the back button. Select wipe -> advanced wipe. Select dalvik, cache, system, data. Be absolutely sure you don't select internal. Flash Malladus and whatever gapps you prefer.
Click to expand...
Click to collapse
I am using TWRP. So after I follow your steps, go into the malladus rom and check the gps, then do I flash the latest Mahdi?
Nextcue said:
I am using TWRP. So after I follow your steps, go into the malladus rom and check the gps, then do I flash the latest Mahdi?
Click to expand...
Click to collapse
Yes, actually download maps and ensure it get a GPS lock on you. Then reboot to recovery, go to advanced wipe and select dalvik, cache, system, and data. Then flash the newest mahdi and the newest patch. The ROM is 6-28 and the patch is V6 I believe. Then gapps. You should be good to go then.
JRJ442 said:
Yes, actually download maps and ensure it get a GPS lock on you. Then reboot to recovery, go to advanced wipe and select dalvik, cache, system, and data. Then flash the newest mahdi and the newest patch. The ROM is 6-28 and the patch is V6 I believe. Then gapps. You should be good to go then.
Click to expand...
Click to collapse
Thank you so much, really, I appreciate all of your help!
Nextcue said:
Thank you so much, really, I appreciate all of your help!
Click to expand...
Click to collapse
No problem. Report back too please. And definitely make sure the md5 matches on your download for that baseband updater. That's super important
JRJ442 said:
No problem. Report back too please. And definitely make sure the md5 matches on your download for that baseband updater. That's super important
Click to expand...
Click to collapse
Will absolutely report back. I will be testing it later tonight.Just in case though: What do I do in the event I do not get a gps lock on maps?
Nextcue said:
Will absolutely report back. I will be testing it later tonight.Just in case though: What do I do in the event I do not get a gps lock on maps?
Click to expand...
Click to collapse
You'll get one. No need to worry about not getting one. You just have to do it because sometimes coming from 12B JB source, the sensors won't calibrate correctly on a ROM with true KK source. But I'm not really sure what you could do if you don't to be honest. You should get a lock fairly quick though. Just make sure location is on high accuracy and it will lock
Please if someone can take the time to help me save a lot of time.
So I had to restore my Nexus 6 back to stock from CM12 to unlock the phone so I could start using Project Fi. So I went back set it up and was ready to restore back to cm12. Well every time I try to go back to one of my updates it runs for maybe a min and then the phone restarts and then just stays on start up screen without starting up.
this has nothing to do with the unlocking of the phone because 2 months ago when I needed to restore from cm12 it did the same thing!
So why cant I restore using twarp on my device and what do I have to do to get back my restore.
also when I try to just reload cm12 it fails .
PLEASE HELP ME SOMEONE! LOL
CM is your first problem. LOL All that aside. Usually when it stops on startup screen the kernel is borked. Try fastbooting/flashing a compatible kernel.
Try wipe cache and dalvik from recovery. If it still doesn't boot, wipe data, then restore apps using titanium
Can you guys please look at clip I made of the issue. Thanks so much!
https://youtu.be/3C8LtPu9LsA
<iframe width="420" height="315" src="https://www.youtube.com/embed/3C8LtPu9LsA" frameborder="0" allowfullscreen></iframe>
No need. Follow our advice
enzosly said:
Can you guys please look at clip I made of the issue. Thanks so much!
https://youtu.be/3C8LtPu9LsA
<iframe width="420" height="315" src="https://www.youtube.com/embed/3C8LtPu9LsA" frameborder="0" allowfullscreen></iframe>
Click to expand...
Click to collapse
To start I would actually wipe. Dalvik and cache is not a wipe. This only affects apps saved in ram.. Wipe system. Your flashing over old system and data. It is different flashing images than it is flashing restores. Can have files that are not overwritten. Basically a full dirty flash. Can't go stock and then dirty flash rom over the top. Especially CM. Too much doesn't match. Your flashing different bases over the top of each other. This is why people need permission fixes. The UID's don't match between the different bases. Have never used fix permissions unless testing and then shows us need to fully wipe.
prdog1 said:
To start I would actually wipe. Dalvik and cache is not a wipe. This only affects apps saved in ram.. Wipe system. Your flashing over old system and data. It is different flashing images than it is flashing restores. Can have files that are not overwritten. Basically a full dirty flash. Can't go stock and then dirty flash rom over the top. Especially CM. Too much doesn't match. Your flashing different bases over the top of each other. This is why people need permission fixes. The UID's don't match between the different bases. Have never used fix permissions unless testing and then shows us need to fully wipe.
Click to expand...
Click to collapse
ok so do a full wipe is what your saying then? Ill give it a try
enzosly said:
ok so do a full wipe is what your saying then? Ill give it a try
Click to expand...
Click to collapse
Yes. Also make sure boot is checked when make a backup. If restore doesn't contain kernel CM won't boot with stock kernel.
prdog1 said:
Yes. Also make sure boot is checked when make a backup. If restore doesn't contain kernel CM won't boot with stock kernel.
Click to expand...
Click to collapse
Ok so I did a full wipe and still same thing. I also went into fixing permissions and nothing.
what should I do next I guess? again thank you for taking the time
enzosly said:
Ok so I did a full wipe and still same thing. I also went into fixing permissions and nothing.
what should I do next I guess? again thank you for taking the time
Click to expand...
Click to collapse
Backup may be bad. Wipe everything and flash a full image/rom. Stopping on the splash usually means corrupted kernel. Rom not booting. If get to boot animation it is rom related. Need to start fresh. Google saves your apps so it no big deal. Rather have clean working rom than worry about apps and resetup.
enzosly said:
Ok so I did a full wipe and still same thing. I also went into fixing permissions and nothing.
what should I do next I guess? again thank you for taking the time
Click to expand...
Click to collapse
NEVER fix permissions.
Download the rom and flash it. Then use titanium to restore apps.extracted from.your nandroid.backup, if it can.
danarama said:
NEVER fix permissions.
Download the rom and flash it. Then use titanium to restore apps.extracted from.your nandroid.backup, if it can.
Click to expand...
Click to collapse
I agree if have to fix permissions rom is borked. Still looks like corrupted backup. Wipe all and fastboot stock or flash clean rom.
danarama said:
NEVER fix permissions.
Download the rom and flash it. Then use titanium to restore apps.extracted from.your nandroid.backup, if it can.
Click to expand...
Click to collapse
fix_permissions works, but not via recovery. i use stericsons fix_permissions app. it goes through and fixes permissions, per each app, when you are fully booted.
simms22 said:
fix_permissions works, but not via recovery. i use stericsons fix_permissions app. it goes through and fixes permissions, per each app, when you are fully booted.
Click to expand...
Click to collapse
It fixes mismatched UIDs which means you have a corrupt install. LOL
simms22 said:
fix_permissions works, but not via recovery. i use stericsons fix_permissions app. it goes through and fixes permissions, per each app, when you are fully booted.
Click to expand...
Click to collapse
Thing is they can't know what permissions everything is supposed to have, so its guess work and can lead to more problems l. Besides, permissions should never need fixing anyway
prdog1 said:
It fixes mismatched UIDs which means you have a corrupt install. LOL
Click to expand...
Click to collapse
whatever.. last time i installed anything was when m came out. honestly, ill use that app maybe twice a year, but it does work.
---------- Post added at 03:10 PM ---------- Previous post was at 03:08 PM ----------
danarama said:
Thing is they can't know what permissions everything is supposed to have, so its guess work and can lead to more problems l. Besides, permissions should never need fixing anyway
Click to expand...
Click to collapse
na, it doesnt ever need fixin', its just something ill do every once in a while. kind of a habit leftover from the older android days.
simms22 said:
whatever.. last time i installed anything was when m came out. honestly, ill use that app maybe twice a year, but it does work.
Click to expand...
Click to collapse
Just saying after years as a tester and thousands of builds. Was a big thing when they were porting roms to a different device. UIDs were broke all over the place. See the same thing if dirty flash different bases like Lolli over KitKat or a complete base change as an example ( L to M). Don't see mismatched UID's on updates made on same base.
prdog1 said:
Just saying after years as a tester and thousands of builds. Was a big thing when they were porting roms to a different device. UIDs were broke all over the place. See the same thing if dirty flash different bases like Lolli over KitKat or a complete base change as an example ( L to M). Don't see mismatched UID's on updates made on same base.
Click to expand...
Click to collapse
im very known as a dirty flasher btw :angel:
(and i did dirty flash m over terminus)
simms22 said:
im very known as a dirty flasher btw :angel:
(and i did dirty flash m over terminus)
Click to expand...
Click to collapse
Some have the luck. Apparently this poster don't.
prdog1 said:
Some have the luck. Apparently this poster don't.
Click to expand...
Click to collapse
its not luck, its all about doing it properly
I have searched this forum topic and did not see any mention of a Marshmallow Release OTA for those running the M Preview 3. Not sure I want to risk things by not flashing some of the image files. Suggestions appreciated.
There will not be an OTA.
danarama said:
There will not be an OTA.
Click to expand...
Click to collapse
OK, thanks. Should I just skip the userdata.img or do a fresh install?
I'd say do a backup of your data and then wipe it clean. A fresh install now and then is nice.
Didgeridoohan said:
I'd say do a backup of your data and then wipe it clean. A fresh install now and then is nice.
Click to expand...
Click to collapse
I'm not rooted, so I guess a fresh install it'll be.
xwera43 said:
I'm not rooted, so I guess a fresh install it'll be.
Click to expand...
Click to collapse
I would try and flash without userdata first, but have your sdcard backed up because really a fresh install of a major OS is always best.
danarama said:
I would try and flash without userdata first, but have your sdcard backed up because really a fresh install of a major OS is always best.
Click to expand...
Click to collapse
Sound good. Appreciate your input.