This is going to be kind of hard to explain through text, so bare with me.
All of a sudden lately, my phone's microphone has been glitching out and it's really throwing me off. The microphone will stop working, but it's on a pattern. Every other call, the microphone will not work. Most of the time I get calls from people, it falls on the time when the microphone is not working, so I have to hang up & call them back and it works fine.
I've had the phone for a few months and I'm using TrueAncestor 2.3.7 but the issue has only been recent.
Did you already tried another rom ?
if not try that !
And if you have a backup before the problem, restore it !
If nothing helps try bringing it back to the store , let them see it mostly of the times it works
Hi I am new and I need help with the same problem. I flashed the R800at to all the versions that can be rooted of the R800i generic and the R800a and I have the same problem with the microphone muting itself and I cannot fix it since I am not a developer :S. Could it be the Apn? I tried downloading the Apn settings before putting it in manually, but it says that it cannot download load it. Any ideas?
Thanks!
Same issue, I'm pretty sure it's not a rom issue cause it happens to me also on every rom. Could it be kernel related perhaps?
GTDarthYoda said:
Same issue, I'm pretty sure it's not a rom issue cause it happens to me also on every rom. Could it be kernel related perhaps?
Click to expand...
Click to collapse
It is probably the kernel. I don't know how to edit the kernel though. The At&t kernel works, but not with the R800a system. I tried to flash it, but is there a way to edit the two kernels?
You must flash other kernel than one you're using
wuby said:
You must flash other kernel than one you're using
Click to expand...
Click to collapse
Are there any other kernels to use that can be used with Flashtool for locked bootloaders?
Perhaps an older version of DoomLord's kernel?
Would the stock modules Doomlord made would fix the issue?
GTDarthYoda said:
Same issue, I'm pretty sure it's not a rom issue cause it happens to me also on every rom. Could it be kernel related perhaps?
Click to expand...
Click to collapse
TreyChristopher said:
I've had the phone for a few months and I'm using TrueAncestor 2.3.7 but the issue has only been recent.
Click to expand...
Click to collapse
Okay, so, I did some digging and found this thread: http://forum.xda-developers.com/showthread.php?t=1589399&page=3. captain67 talks about the .42 and .62 basebands:
.62 is supposed to have some memory fixes. Personally I didn't see much of a difference. The AT&T version has had signal compatibility issues with certain a/i roms and basebands so if the current one is working well I'd leave it. Flashtool has an option to exclude baseband so you won't need to flash it separately
So what build are you (both) using? The r800i or a? Also, I'm testing out the different basebands that I have and seeing which one will work.
Archfeind2 said:
Okay, so, I did some digging and found this thread: http://forum.xda-developers.com/showthread.php?t=1589399&page=3. captain67 talks about the .42 and .62 basebands:
.62 is supposed to have some memory fixes. Personally I didn't see much of a difference. The AT&T version has had signal compatibility issues with certain a/i roms and basebands so if the current one is working well I'd leave it. Flashtool has an option to exclude baseband so you won't need to flash it separately
So what build are you (both) using? The r800i or a? Also, I'm testing out the different basebands that I have and seeing which one will work.
Click to expand...
Click to collapse
So how do i go about fixing it?
Your explanation lost me a little bit...
GTDarthYoda said:
So how do i go about fixing it?
Your explanation lost me a little bit...
Click to expand...
Click to collapse
Sorry, I forgot the explanation! We have to find the baseband ftf file that will work with the xperia play 4g. The original model's besband ends in 62. So, we have to find out how to get the 62 baseband. I tired flashing it from the AT&T ftf file, but no luck.
Edit:
Actually, I'm not running 2.3.4 anymore, but I'll try it from there. (I was running 4.0.4) No luck with 2.3.4 either..
I found the working baseband!!
Thanks to romico47 for the working baseband for the r800at!
Find it here to download
Working baseband for r800at (-36 baseband)
Note: I don't believe his lib files are necessary. It works for me without them, but you may need to flash them via CWM if it doesn't work automatically for you. Also, check everything off except for exclude baseband and wipe cache. That's how it worked for me w/o lib files.
Archfeind2 said:
I found the working baseband!!
Thanks to romico47 for the working baseband for the r800at!
Find it here to download
Working baseband for r800at (-36 baseband)
Note: I don't believe his lib files are necessary. It works for me without them, but you may need to flash them via CWM if it doesn't work automatically for you. Also, check everything off except for exclude baseband and wipe cache. That's how it worked for me w/o lib files.
Click to expand...
Click to collapse
so is this for gingerbread only I'm guessing?
Sends jelly bean into a boot loop...
GTDarthYoda said:
so is this for gingerbread only I'm guessing?
Sends jelly bean into a boot loop...
Click to expand...
Click to collapse
It worked for my 4.0.4 build I used also. And, did you just load up the bootloader? Or did you load everything and then the modules?
Archfeind2 said:
It worked for my 4.0.4 build I used also. And, did you just load up the bootloader? Or did you load everything and then the modules?
Click to expand...
Click to collapse
I flashed the ftf file and the modules... I may try again later. not right now tho.
edit: wait just the bootloader?
---------- Post added at 12:48 PM ---------- Previous post was at 12:08 PM ----------
I keep getting this error in CWM when I try to do almost anything
E:format_volume: no MTD partition "userdata"
GTDarthYoda said:
I flashed the ftf file and the modules... I may try again later. not right now tho.
edit: wait just the bootloader?
---------- Post added at 12:48 PM ---------- Previous post was at 12:08 PM ----------
I keep getting this error in CWM when I try to do almost anything
E:format_volume: no MTD partition "userdata"
Click to expand...
Click to collapse
Yes. Since we already have the fota from the previous R800i version, we just need the baseband only. The lib files aren't needed either. I only flashed my cache and my baseband and it worked. I still don't have any dropped calls, plus my close enough HSPA+ data.
I believe it worked for me as well (knock on wood). Flashed the apk and muting seems to be resolved. Thanks for this solution before my phone met an untimely end in a fit of rage.
go45cvi said:
I believe it worked for me as well (knock on wood). Flashed the apk and muting seems to be resolved. Thanks for this solution before my phone met an untimely end in a fit of rage.
Click to expand...
Click to collapse
I know the feeling.
Related
again as the title says.
whats the Best BaseBand and Libs for signal.? and the best rom for signal?
Search around dude it's been talked about lots
Sent from my R800a using XDA App
fma965 said:
again as the title says.
whats the Best BaseBand and Libs for signal.? and the best rom for signal?
Click to expand...
Click to collapse
i've been looking for the same thing, and i tried to flash .36 baseband, having .42 firmware. In the Arc forum you can find libraries and the baseband itself; flashed the baseband via flashtool, then flashed via recovery the libraries, clear cache, reboot, and i get no signal whatsoever. rebooted again, nothing, no signal, no gsm, no wcdma.
I don't know, maybe it doesn't work for my country, i'm from Italy...
same thing happened to me in uk
are you sure the libs are for PLAY not arc?
mulllen666 said:
same thing happened to me in uk
are you sure the libs are for PLAY not arc?
Click to expand...
Click to collapse
no i'm not
But i don't know, where i'm supposed to get this baseband? Doomlord in his (xplay) kernel topic said it's recomended to have this .36 baseband, but in xperia play's forum there's no topic and no baseband topic...
---------- Post added at 01:19 PM ---------- Previous post was at 01:12 PM ----------
actually i'm reading the baseband patch topic in arc forum and there doomlord said the libs works fine for him... so it's out problem
pelly_jelly said:
i've been looking for the same thing, and i tried to flash .36 baseband, having .42 firmware. In the Arc forum you can find libraries and the baseband itself; flashed the baseband via flashtool, then flashed via recovery the libraries, clear cache, reboot, and i get no signal whatsoever. rebooted again, nothing, no signal, no gsm, no wcdma.
I don't know, maybe it doesn't work for my country, i'm from Italy...
Click to expand...
Click to collapse
You can't use the radio from an arc rom, your lucky you didnt brick your phone just use one of the .ftf files from the play, and just flash the baseband using flashtool.
Sent from my R800i using Tapatalk
AndroHero said:
You can't use the radio from an arc rom, your lucky you didnt brick your phone just use one of the .ftf files from the play, and just flash the baseband using flashtool.
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
wait a minute, maybe i didn't explained myself...
i'm saying i'm on stock .42 xperia play firmware, then flashed the .36 baseband from the arc forum.
Or are there explicit xperia play baseband ftf around here?
Edit: oh crap i'm an idiot. You mean to download the entire firmware for the play and, when using flashtool, just flash the baseband from that... right? if that's so, i can find .62 firmware for the play, but can't find anywhere this .36 ... or is it a previous release?
May not be a huge deal, but I thought I'd ask.
I have cm9 nightly on a p935 Telus unit.
Everything works.
::
But why does it say unknown baseband in the about phone?
Just a guess, but did you flash HO!NO!'s ICS CWM-flashable leak? If so, that's why.
Malnilion said:
Just a guess, but did you flash HO!NO!'s ICS CWM-flashable leak? If so, that's why.
Click to expand...
Click to collapse
Nope.
But I did flash hohos bell rom before I flashed the nightlies.
Any fix?
typhoonk said:
Nope.
But I did flash hohos bell from before I flashed the nightlies.
Any fix?
Click to expand...
Click to collapse
Do you have original baseband/firmware images for your device?
This happened to me when I flashed a nightly about a week ago. It fixed itself when I flashed a later nightly.
kernelpan1c said:
This happened to me when I flashed a nightly about a week ago. It fixed itself when I flashed a later nightly.
Click to expand...
Click to collapse
did you clear all data before you flashed the new nightly?
are with Telus?
I just noticed I don't have LTE either (not a big deal, but could cause an issue)
drumist said:
Do you have original baseband/firmware images for your device?
Click to expand...
Click to collapse
No, as the P935 was unrootable, so no way to get those.
but the P930 would work. Do you know if there is a baseband flash?
typhoonk said:
No, as the P935 was unrootable, so no way to get those.
but the P930 would work. Do you know if there is a baseband flash?
Click to expand...
Click to collapse
I found some P930 baseband img
and followed these instructions -> http://forum.xda-developers.com/showthread.php?t=1582553
now it shows a baseband under phone info (and hopefully LTE will work now. Have to wait till I'm in an 'area').
typhoonk said:
No, as the P935 was unrootable, so no way to get those.
but the P930 would work. Do you know if there is a baseband flash?
Click to expand...
Click to collapse
I've been using the AT&T P930 v10j firmware/baseband images with CM9 and it's been working fine for me. I assume it will work fine on your phone too, but I can't promise anything.
These are the ones I'm talking about: http://forum.xda-developers.com/showpost.php?p=24505166&postcount=27
Also, I posted the correct MD5 sums here if you want to verify them before flashing: http://forum.xda-developers.com/showpost.php?p=25828353&postcount=73
---------- Post added at 10:05 PM ---------- Previous post was at 09:55 PM ----------
Oh, and as a side note, you probably don't need to do anything. Having an unknown baseband isn't a problem unless it's actually not working properly. In fact, here's a recent screenshot that aremcee posted, showing this his own device shows "unknown" under the baseband line:
https://plus.google.com/u/0/115049428938715274412/posts/Y3zcRM3aZEE
If you are not getting LTE signal, it's probably due to having incorrect APN settings.
drumist said:
I've been using the AT&T P930 v10j firmware/baseband images with CM9 and it's been working fine for me. I assume it will work fine on your phone too, but I can't promise anything.
These are the ones I'm talking about: http://forum.xda-developers.com/showpost.php?p=24505166&postcount=27
Also, I posted the correct MD5 sums here if you want to verify them before flashing: http://forum.xda-developers.com/showpost.php?p=25828353&postcount=73
---------- Post added at 10:05 PM ---------- Previous post was at 09:55 PM ----------
Oh, and as a side note, you probably don't need to do anything. Having an unknown baseband isn't a problem unless it's actually not working properly. In fact, here's a recent screenshot that aremcee posted, showing this his own device shows "unknown" under the baseband line:
https://plus.google.com/u/0/115049428938715274412/posts/Y3zcRM3aZEE
If you are not getting LTE signal, it's probably due to having incorrect APN settings.
Click to expand...
Click to collapse
don't know what md5 sums are. any link for info?
typhoonk said:
don't know what md5 sums are. any link for info?
Click to expand...
Click to collapse
It's a way to verify the file was not corrupted while being downloaded. If you try to flash a corrupted img it might make the phone unbootable (though you could recover using unbricking guide). It's unlikely, but just an extra precaution. Most file managers in Android can tell you what the md5 sums of the files are once you have them on the SD card. You just need to compare them against the correct sums to verify the file was not corrupted.
drumist said:
It's a way to verify the file was not corrupted while being downloaded. If you try to flash a corrupted img it might make the phone unbootable (though you could recover using unbricking guide). It's unlikely, but just an extra precaution. Most file managers in Android can tell you what the md5 sums of the files are once you have them on the SD card. You just need to compare them against the correct sums to verify the file was not corrupted.
Click to expand...
Click to collapse
cool thanks!!!!
found the file with that MD5 checksum, and put that one on my phone.
typhoonk said:
did you clear all data before you flashed the new nightly?
are with Telus?
I just noticed I don't have LTE either (not a big deal, but could cause an issue)
Click to expand...
Click to collapse
I just wipe cache and wipe dalvik cache before flashing new nightlies
No, I'm on an AT&T MVNO
You probably need to setup/verify your APN for Telus and also select the GSM/LTE option in the Mobile network menu in Settings.
kernelpan1c said:
I just wipe cache and wipe dalvik cache before flashing new nightlies
No, I'm on an AT&T MVNO
You probably need to setup/verify your APN for Telus and also select the GSM/LTE option in the Mobile network menu in Settings.
Click to expand...
Click to collapse
I've got the same APN's that I had when my phone was stock.
But since I only go into a town with LTE only like once a week, I can't say if it's working or not. But the last time I was there it didn't work.
so hopefully with this baseband in, everything will be peachy!! thanks again!
I'm doing this from work, so I'll have to clean this up later.
Standard Disclaimers Apply. I have personally tested this on my device multiple times.
WHAT DOES THE LG2 OTA UPDATE CONTAIN?
Simply put? ABSOLUTELY NOTHING. Well mostly nothing, I can't fully confirm that. But I can confirm two things:
1. Removes universal search from Google Quick Search (i.e. search apps, contacts, or anything besides web)
2. Limits your Wifi and 3G horribly (made my SGS3 reject my work wifi for being too weak, with 1-2 bars)
WHAT AM I PROVIDING HERE THEN?
Well, anyone who has received the notification for the OTA knows just how frustrating it is! This should get rid of that, while also updating your modem. Any other 'patching' is removed, as well as the Google Quick Search crippling.
And most importantly, this will flash through CWM no matter what you've changed or removed, so long as you're on LF9.
HOW TO USE:
1. Do not accept OTA update.
2. Download my file to your SD card.
3. Boot into CWM.
4. Flash my file.
5. Reboot phone.
6. Accept OTA update.
7. Reboot phone once OTA fails.
DOWNLOAD HERE
Custom LG2 for Custom ROMS
This is awesome!
Side question: what does this mean for future OTA's? Will subsequent "custom updates" be needed from here on out? Thanks!
Worked perfect! Thanks! :laugh:
Thanks again for the update! But my paranoid just wants to confirm I get everything flashed correctly...
I accidentally clicked "Update later" when I got prompted (step 6) because I wanted to check the device info. Now I don't get prompted to install the OTA anymore even though I didn't go through the process of downloading it. Should I be seeing the old baseband (LF9) or should that also be LG2?
Thanks!
MinimalistChris said:
Thanks again for the update! But my paranoid just wants to confirm I get everything flashed correctly...
I accidentally clicked "Update later" when I got prompted (step 6) because I wanted to check the device info. Now I don't get prompted to install the OTA anymore even though I didn't go through the process of downloading it. Should I be seeing the old baseband (LF9) or should that also be LG2?
Thanks!
Click to expand...
Click to collapse
The baseband is the modem, so LG2. If it's gone, then congrats. Everything else is in place. The only reason the notification remains in the first place, is because the update didn't go through the Android updater.
Sent from my SPH-L710 using XDA Premium HD app
RandomKing said:
The baseband is the modem, so LG2. If it's gone, then congrats. Everything else is in place. The only reason the notification remains in the first place, is because the update didn't go through the Android updater.
Sent from my SPH-L710 using XDA Premium HD app
Click to expand...
Click to collapse
Awesome! I figured everything was fine... I just get paranoid about these things
Thank you for the clarification and the dev work!
Must be on LF9... Have the script do those checks?
Don't i recall us going through this before on the OG Epic? =P
hoffman1984 said:
Must be on LF9... Have the script do those checks?
Don't i recall us going through this before on the OG Epic? =P
Click to expand...
Click to collapse
I could remove it easily... but for compatibility and making users happy i left it that way. ;-)
Sent from my SPH-L710 using XDA Premium HD app
RandomKing,
Thanks for the good work. I have my daughter's S3 still on a stock rom and might for a while till I find something really stable for her. What's the issue of using your file on a stock ROM? Will it just not work?
Jettubby said:
RandomKing,
Thanks for the good work. I have my daughter's S3 still on a stock rom and might for a while till I find something really stable for her. What's the issue of using your file on a stock ROM? Will it just not work?
Click to expand...
Click to collapse
No issue.
Sent from my SPH-L710 using XDA Premium HD app
RandomKing said:
No issue.
Sent from my SPH-L710 using XDA Premium HD app
Click to expand...
Click to collapse
Have you tested this on a stock ROM? So it will work?
I have flashed new ROMs but I still have the Baseband version of L710VPLEN.... I assume I need to flash both OTA updates in order to change my Baseband. If I'm not mistaken, flashing those updates will update my Baseband, but will also un-root my phone. Is there a way to update the baseband without losing root? I have tried to find the answers in the posts here, but I am unable to. Thank you in advance
does anyone have or can post LF9 Modem.zip?? i flashed the new LG2 modem but it killed my 3g speeds...please any help will be appreciated...
Is this zip suppose to end the update pop....I did it but am still getting the update pop up
hunterbeav said:
Is this zip suppose to end the update pop....I did it but am still getting the update pop up
Click to expand...
Click to collapse
Yes, the update popup should be gone after you flash this
klarthur said:
I have flashed new ROMs but I still have the Baseband version of L710VPLEN.... I assume I need to flash both OTA updates in order to change my Baseband. If I'm not mistaken, flashing those updates will update my Baseband, but will also un-root my phone. Is there a way to update the baseband without losing root? I have tried to find the answers in the posts here, but I am unable to. Thank you in advance
Click to expand...
Click to collapse
You shouldn't lose root by updating baseband. I didn't, make sure your use the team epic link for guidance http://www.epiccm.org/2012/06/team-epics-root-from-recovery.html just in case you do...
baseband only link...care of Blazer Rom post...http://forum.xda-developers.com/showthread.php?t=1746184&page=166
Naddict said:
You shouldn't lose root by updating baseband. I didn't, make sure your use the team epic link for guidance http://www.epiccm.org/2012/06/team-epics-root-from-recovery.html just in case you do...
baseband only link...care of Blazer Rom post...http://forum.xda-developers.com/showthread.php?t=1746184&page=166
Click to expand...
Click to collapse
worked for me perfectly!
---------- Post added at 08:39 PM ---------- Previous post was at 08:38 PM ----------
Jettubby said:
Have you tested this on a stock ROM? So it will work?
Click to expand...
Click to collapse
I just tested it on stock, rooted, works fine
joeyhdownsouth said:
worked for me perfectly!
---------- Post added at 08:39 PM ---------- Previous post was at 08:38 PM ----------
I just tested it on stock, rooted, works fine
Click to expand...
Click to collapse
Thanks for that clarification. I understand that this zip kills the update nag but does it also update the baseband to LG2 where people are having wifi and 3G issues? If so it would be nice to just have a nag killer zip? Or edit the build.prop to show LG2 so that the system thinks its updated?
MinimalistChris said:
Thanks again for the update! But my paranoid just wants to confirm I get everything flashed correctly...
I accidentally clicked "Update later" when I got prompted (step 6) because I wanted to check the device info. Now I don't get prompted to install the OTA anymore even though I didn't go through the process of downloading it. Should I be seeing the old baseband (LF9) or should that also be LG2?
Thanks!
Click to expand...
Click to collapse
I did zip but still showing Lf9 baseband....no more pop ups though...is that right?
Thanks for this :thumbup:
Sent from my SPH-L710 using xda app-developers app
Hello,
I've been having trouble getting WiFi to turn on for DocHoliday's T-Mobile 4.3 leak ROM. I'm coming from Stock UVDMD5 4.1.2. I performed a full wipe (formatted system, data, cache, dalvik cache) before installing the new modem and the rom. At first, data and wifi weren't working. After flashing the new modem again, data worked. WiFi however isn't fixed. When I turn WiFI on, it immediately turns off. Does anybody else have this problem? I also cannot access the internal storage on this phone via a computer.
T-Mobile 4.3 ROM:
http://forum.xda-developers.com/showthread.php?t=2509939
T-Mobile 4.3 Modem:
http://forum.xda-developers.com/showpost.php?p=46862241&postcount=575
I downloaded the PureStock version. I performed an MD5 check and it verified with the one posted on the site.
What time did you download it? The first upload was corrupted and would only be about 400-500mbps in size. That was kinda early this morning though. You may want to consider redownloading.
Another thing to try is go to saranhai's AT&T port and download and flash the kernel at the bottom of the first post.
http://forum.xda-developers.com/showthread.php?t=2501303
If that doesn't work, Odin flash.the root66 firmware, then try again.
And I don't ever suggest wiping /system prior to flashing a Rom. The Rom will do that for you, and if it won't flash for some reason you could get stuck with a device with no O/S!
The only time I had WiFi not work was due to a kernel btw. But I never released it so that shouldn't be the cause here...
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
What time did you download it? The first upload was corrupted and would only be about 400-500mbps in size. That was kinda early this morning though. You may want to consider redownloading.
Another thing to try is go to saranhai's AT&T port and download and flash the kernel at the bottom of the first post.
http://forum.xda-developers.com/showthread.php?t=2501303
If that doesn't work, Odin flash.the root66 firmware, then try again.
And I don't ever suggest wiping /system prior to flashing a Rom. The Rom will do that for you, and if it won't flash for some reason you could get stuck with a device with no O/S!
The only time I had WiFi not work was due to a kernel btw. But I never released it so that shouldn't be the cause here...
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I downloaded it after you edited the post saying that the upload was corrupted and that a new one was posted on the directory folder. I checked the MD5sum of the file that I downloaded and it matched the one on the site.
I'll download the kernel on the AT&T thread you mentioned. I'll keep you posted. I appreciate your help, Doc.
With due Respect, @Vigz if you had a suspected issue with Doc's Leaked Rom, why didn't you post it there ? What did you expect to achieve by opening another thread ?
Clearly you did know what the thread was and where it is.
http://forum.xda-developers.com/member.php?u=4848914
Perseus71 said:
With due Respect, @Vigz if you had a suspected issue with Doc's Leaked Rom, why didn't you post it there ? What did you expect to achieve by opening another thread ?
Clearly you did know what the thread was and where it is.
http://forum.xda-developers.com/member.php?u=4848914
Click to expand...
Click to collapse
Alright, my bad. Anyway DocHoliday, I was able to get WiFi working again thanks to the kernel on the AT&T port. Everything is working smoothly. Thanks once again DocHoliday!
EDIT: Uh oh, it seems like SuperSU keeps getting blocked. SELinux status is set to: Enforcing SEPF_SAMSUNG-SGH-I747_4.3_0010
Perseus71 said:
With due Respect, @Vigz if you had a suspected issue with Doc's Leaked Rom, why didn't you post it there ? What did you expect to achieve by opening another thread ?
Clearly you did know what the thread was and where it is.
http://forum.xda-developers.com/member.php?u=4848914
Click to expand...
Click to collapse
Post count too low to post in development.
Vigz said:
Alright, my bad. Anyway DocHoliday, I was able to get WiFi working again thanks to the kernel on the AT&T port. Everything is working smoothly. Thanks once again DocHoliday!
EDIT: Uh oh, it seems like SuperSU keeps getting blocked. SELinux status is set to: Enforcing SEPF_SAMSUNG-SGH-I747_4.3_0010
Click to expand...
Click to collapse
Try rebooting. That should solve it. If not flash the same kernel again. I know it's weird, but it's worked for others.
And you're not the only one who had this happen btw. I'm suspecting I made a little mistake and copied the wrong boot.img. If I did, I apologize for the problems.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Post count too low to post in development.
Try rebooting. That should solve it. If not flash the same kernel again. I know it's weird, but it's worked for others.
And you're not the only one who had this happen btw. I'm suspecting I made a little mistake and copied the wrong boot.img. If I did, I apologize for the problems.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Alright, SELinux is now set to permissive. But for some reason, the SuperSU app gets blocked. I receive a notification that says, "SuperSU attempted to access system on your device without authorization. This attempt has been blocked, etc."
That's Knox "protecting" you from you!
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
That's Knox "protecting" you from you!
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Lol, you know what they say, you're your own worst enemy.
Once you flash the insecure kernel from AT&T, you should maintain root most of the time, it will read "Permissive" instead of Enforcing-SGH-i747 blah blah
Doc and I have disabled KNOX/CarrierIQ/SELinux for the most part in the build.prop and even removed the files.
Since I didn't see anyone pull the modem and kernel from the last stagefright update in Sept., thought I'd do it for the few of us that still have this old device.
T889UVUCOH4 Modem: http://www.mediafire.com/download/85es0yrteawo879/T889UVUCOH4_Modem_9_28_15.zip
T889UVUCOH4 Kernel: http://www.mediafire.com/download/w6wdyb3fut6t8c6/T889UVUCOH4_Kernel-9_28_15.zip
Was there an OTA for T-Mobile? I'm currently on a AOSP Rom.
Sent from my SM-N910T using Tapatalk
James62370 said:
Was there an OTA for T-Mobile? I'm currently on a AOSP Rom.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Yeah, but you need to be on a stock ROM to get the OTA, or you can download the whole ROM from sammobile.com. It's a security fix for stagefright. I just wanted to try the new modem and see if it made any difference. I won't be able to test the kernel, since I switch back and forth between a 4.4.4 TW ROM and 5.1 CM ROM.
Appreciate the info, have you notice better signal with the new radio?
James62370 said:
Appreciate the info, have you notice better signal with the new radio?
Click to expand...
Click to collapse
Maybe a little better signal (?), but basically the same. Haven't been on it real long, I'll have to see if the standby improves after I've been on it a while.
kozmo21 said:
since I switch back and forth between a 4.4.4 TW ROM and 5.1 CM ROM.
Click to expand...
Click to collapse
Are you dual booting? Is it possible?
Warning, don't flash this modem. I did and it killed my baseband. I tried flashing 3 other roms which wouldn't even finish booting to my phone before I finally realized it and flashed my original modem back and all was working again.
xamindar said:
Warning, don't flash this modem. I did and it killed my baseband. I tried flashing 3 other roms which wouldn't even finish booting to my phone before I finally realized it and flashed my original modem back and all was working again.
Click to expand...
Click to collapse
yikes.. ok thanks. I was going to do this today. I'll wait
xamindar said:
Warning, don't flash this modem. I did and it killed my baseband. I tried flashing 3 other roms which wouldn't even finish booting to my phone before I finally realized it and flashed my original modem back and all was working again.
Click to expand...
Click to collapse
Working fine on mine. Did you maybe get a bad download? You could maybe try downloading again?
Which modem did you go back to?
Flashed fine and so far no issues. Previous user might have a bad download or different device.
Flashed via TWRP today.. I had no service after reboot but did another restart and it was working.
Don't know if its any better than the previous modem version but will give it a try. thx
Working great here no issues
With old bootloader md1 4.1.2 with ROMofTHRONESv1.0
Sent from my SGH-T889 using XDA Premium 4 mobile app
My wife's note 2 got this OTA and now the phone won't even turn on....:crying:
tsiah said:
My wife's note 2 got this OTA and now the phone won't even turn on....:crying:
Click to expand...
Click to collapse
You caused the problem when you altered the stock ROM. From your thread about it here (http://forum.xda-developers.com/note-2-tmobile/help/recent-tmo-ota-update-bricked-wifes-t3245890), you said "Had her note 2 with stock 4.3, Rooted it last year to titanium backup and uninstall a couple bloatware apps. " This is what caused your problem. It was no longer a stock ROM when you remove apps. I know it doesn't seem like it would be a big deal, but it is, and you found out unfortunately
kozmo21 said:
You caused the problem when you altered the stock ROM. From your thread about it here (http://forum.xda-developers.com/note-2-tmobile/help/recent-tmo-ota-update-bricked-wifes-t3245890), you said "Had her note 2 with stock 4.3, Rooted it last year to titanium backup and uninstall a couple bloatware apps. " This is what caused your problem. It was no longer a stock ROM when you remove apps. I know it doesn't seem like it would be a big deal, but it is, and you found out unfortunately
Click to expand...
Click to collapse
That's kinda what I was thinking had happened.
I suppose I shouldn't blame the OTA. I just noticed someone else had issues with it too.
so to the people that actually flashed this new modem and kernel, is it working better than previous iterations?
question:
I flashed the C0H4 modem on note 2 (nameless lollipop rom) seems ok...
DO I have to also flash the Kernel ? is there an advantage to flashing the kernel? thx
Hello! Thanks for this! I flashed this over TWRP 2.8.7.1, and wiping my dalvik cache. My phone's originally T889UVALK8 (16gb SGH-T889 t0ltetmo) and the signal drops but after flashing this (C0H4) the signal greatly improved, although I'm having some signal instability since I'm supposed to have full bars because my house is just in line of sight, 2km from the tower. Also I think I'll do a clean install of another custom ROM since I'm using the CM12.1 t0lte nightly, and maybe this affects my signal (I know I'm stupid for doing it but it works).
Welp. After rebooting, the phone lost signal again. I have to do a wipe of dalvik cache to restore my signal. I guess I'll try using another ROM instead.
Upodate: I may be experiencing hardware issues. I have yet to flash back to stock since my phone's signal drops. I can't flash the firmware because it says 'zip signature verification failed.'
kozmo21 said:
Working fine on mine.
Click to expand...
Click to collapse
BUT, "yours" seems to be a completely different phone! It says Galaxy Note 4, SM-N910C...
What's up with that?!
AuralArch said:
BUT, "yours" seems to be a completely different phone! It says Galaxy Note 4, SM-N910C...
What's up with that?!
Click to expand...
Click to collapse
It's just the ROM I flashed that makes it say that. That ROM is in my signature... DN4