Related
I have noticed a few people complaining of call echo with AOSP ROMs (even with "noise suppression" checked), as well as some stock based ROMs. I was having the same problems. Stock based ROMs were better, but echo was still there. I tried several radios without avail.
What finally worked for me was going back to stock through Kies (keep in mind this will wipe your internal sd as well, so move your backups off your phone). I have since been able to flash PACman ROM without call echo. I have not tried any others but I assume the result would be the same. If someone is willing to test other ROMs/radios and report back that would be great. I just don't have the time.
Also, I did not flash a different radio after going back to stock. I assume it would be okay to do so, but I am not a dev so that is only a guess. What I think going back to stock fixes is some missing/corrupted libraries that are somehow surviving ROM flashes (like in a protected storage or something like that).
Anyway, I hope this helps someone else.
EDIT: This doesn't work all the time, and has only really worked for me once. I have done it twice and it worked great the first time, and not really the second. It's worth a shot, but just keep this in mind.
:::Specifics:::
Essentially all I did was go to the latest stock rom image from T-Mobile. Kies upgraded my phone to UVLI1, which is T-Mobile's latest 4.0.4 stock rom. Kies essentially wiped everything from my phone (except external storage) and imaged it with the latest factory image which includes the latest radio. I have since been able to root, install TWRP and flash an AOSP based rom without degradation in call quality. I did not flash over the radio that was installed by Kies, and I did not wipe android secure in TWRP (don't know if that made a difference).
What you should try if you are having call quality issues:
1. Go back to stock unrooted (use your method of choice, I used Kies but that doesn't work for everyone so try Odin or Heimdall)
2. If you didn't go to the latest stock unrooted image from T-Mobile and Samsung, do that through Kies which should now work for almost everyone (as of Jan. 1, 2013, the latest stock image is UVLI1/TMBLI1)
3. You should now be able to root and flash any rom you like without call quality degradation (if this is not true for you please let me know --- see above for what I did at this point)
I'd be interested in getting some feedback from this. Keep in mind that I am not always available and may only be able to reply once a day or less. Again, this is just what worked for me, it may not work for you. Please give yourself plenty of time when going through this process as Kies is not very fast (at least in my opinion).
UPDATE:
Here is how I got Kies to update my phone while still rooted and even running an AOSP rom. As always, do this at your own risk. I accept no responsibility for broken devices or lost data/pictures/music/etc. However, I have done this twice now, so just read and understand what you're doing and you should be fine.
Keep in mind that this WILL WIPE YOUR INTERNAL STORAGE! You have been warned.
1. Disconnect your phone from your computer
2. Launch Kies and click on Tools>Firmware Upgrade and Installation
3. Input model number (it's case sensitive !?) and hit OK
4. Input serial number (found under battery) and hit OK
5. Hit okay on windows until it starts downloading the latest firmware for your phone
6. After it's finished downloading it will tell you to put your phone in download mode and connect it to your computer. Do it, check "I understand..." and hit OK (I also opted out of the sending of information to Samsung)
7. Wait until it's finished. It will likely launch a window saying it's downloading a file for emergency recovery of your device.
8. When it's (finally) done it will tell you it was successful (hopefully). Your phone will automatically reboot and all will be well with the world and your phone.
Hope this helps.
kies fails recognize my phone. already have the phone drivers installed.
You have an interesting post, but it would be of more use to people if you specified the exact information about what's on your phone. Such as which stock ROM version you were able to flash through Kies and what radio version you are currently using.
There are different stock ROMs and radios on the forums, so it doesn't solve anything if you haven't told us what exactly works with your phone that others should try.
Here is the rub. I haven't been on stock unrooted rom since buying the phone in March. I have bounced around roms and radios quite a bit (probably at least one or two a week on average). My wife has complained of call echo for a long time (multiple roms, multiple radios and AOSP and touchwiz based roms). Touchwiz based roms had better call quality but echo was still present. I decided to Odin back to stock unrooted and see if it was a hardware issue or not. It wasn't a hardware issue because call quality was great. So I rooted the phone, installed the latest TWRP (2.3.3), but wasn't happy with stock rooted so I decided to try an AOSP rom. I wiped only cache, dalvik cache, system and data (not android secure, don't know if that made a difference or not). It works great; i.e. no call quality issues. I did not flash a radio.
So, essentially what I did was:
1. Went back to stock unrooted (Kies put me on latest 4.0.4 from T-Mobile, which flashed a radio, the rom and cleared internal storage)
2. Rooted and installed TWRP
3. Flashed my rom of choice, but not a radio and I didn't wipe android secure (not sure if that matters)
Honestly I don't know what about that process fixed the echo issues, all I know is it did. If you can't go back to stock unrooted through Kies then use Odin. There are great threads giving step by step instructions on how to do that. I just decided using Kies would be easiest for me, and it worked for me.
I hope these are the details you are looking for FineTalent. And thanks.
Excellent lol. If you own the d30 case from tmobile take it off. Worked for me as well.
I do have the d30 case but taking it off didn't seem to make a difference. Besides, the wife didn't like the idea of my phone going commando.
I used odin to go back to stock and the call quality was great. But as soon as i installed an AOSP rom (All Star Rom V6) the echo was back.
I did not know that LI1 was the latest 404 ROM ?
I can only get VLH1 as the latest ROM.
I know there is a LI1 radio available, but have never seen the LI1 rom itself, especially not on SamMobile/Firmware site.
Any links to the "official LI1 ROM"
Thanks
bert269 said:
I can only get VLH1 as the latest ROM.
I know there is a LI1 radio available, but have never seen the LI1 rom itself, especially not on SamMobile/Firmware site.
Any links to the "official LI1 ROM"
Thanks
Click to expand...
Click to collapse
It was simply the latest one Kies found for my phone. I believe it was labeled as UVLI1/TMDLI1, but I suppose I could be mistaken. If you install Kies on your computer (shudder, I know) and plug your phone in it will compare the rom version on your phone to the latest known rom from tmobile/samsung. You will need your phones serial number I believe. At least, it was needed when I "upgraded" anyway.
whytechapel_x said:
I used odin to go back to stock and the call quality was great. But as soon as i installed an AOSP rom (All Star Rom V6) the echo was back.
Click to expand...
Click to collapse
Can you give the following information:
1. Method of obtaining root
2. Custom recovery odined when obtaining root (I assume it's cwm 5.0.2.7)
3. Custom recovery used to flash AOSP rom
4. Steps taken to flash AOSP rom (I don't want this thread to become a "this is how I flash" thread, but I want to know what was different between your experience and mine, so wipe and install steps would be great)
5. Any mods flashed/done before testing call quality (or was it completely clean, i.e. just rom and gapps)
6. Which gapps did you flash (mine was latest for 4.1.2, so gapps released on oct. 11, anything later is for jb 4.2 and not compatible with 4.1.2 according to release notes)
monkeybuttons said:
Can you give the following information:
1. Method of obtaining root
2. Custom recovery odined when obtaining root (I assume it's cwm 5.0.2.7)
3. Custom recovery used to flash AOSP rom
4. Steps taken to flash AOSP rom (I don't want this thread to become a "this is how I flash" thread, but I want to know what was different between your experience and mine, so wipe and install steps would be great)
5. Any mods flashed/done before testing call quality (or was it completely clean, i.e. just rom and gapps)
6. Which gapps did you flash (mine was latest for 4.1.2, so gapps released on oct. 11, anything later is for jb 4.2 and not compatible with 4.1.2 according to release notes)
Click to expand...
Click to collapse
1.Well i didn't root my stock phone. After using odin
2.I used cwm 6.0.1.5
3.Same.
4. Well i followed the steps in the all star thread which is wipe data/factory reset. Then flashing rom and wiping cache and dalvik cache.
5. The all star rom is heavily modded so idk. I tried it with "noise suppression" on and off.
6. All star gapps.
I want to point out that as soon as i flashed jedi knight 6, the call echo was gone but i want to be able to use my AOSP roms without call echo.
Since I'm not a dev I can't really diagnose the problem. I only hoped that what worked for me would work for others as well.
When I went back to stock I rooted, but didn't like stock. TWRP has been my go to recovery for a while now and the options available in PACman rom have me by the heart strings, so those are the first things I tried. I wish I had time to fiddle around with it and truly try to find out why it worked for me but I just don't have that option right now. Sorry I'm not of more help.
Its OK. But can a dev clarify if maybe clockworkmod is what is causing the call echo? Probably not flashing AOSP ROMs right?
whytechapel_x said:
Its OK. But can a dev clarify if maybe clockworkmod is what is causing the call echo? Probably not flashing AOSP ROMs right?
Click to expand...
Click to collapse
CWM is in no way linked to the call echo issue, however, using the latest version will assist in ensuring your ROMs installs properly. Rather than using CWM I recommend flashing ROMs through TWRP 2.3.3.0, it is the most up to date recovery system for our phones at the moment.
FineTalent said:
CWM is in no way linked to the call echo issue, however, using the latest version will assist in ensuring your ROMs installs properly. Rather than using CWM I recommend flashing ROMs through TWRP 2.3.3.0, it is the most up to date recovery system for our phones at the moment.
Click to expand...
Click to collapse
OK. I went on and installed TWRP anyways and flashed tweakwiz and got call echo once more. I am aware that it flashes the blaze radio but still. Does this mean that my phone came out defective? But why is it that i get absolutely no echo on stock ics and luckily, jedi knight 6 neither? When i was using jedi knight 6,i was using the stock radio uvlh1? But if i have this same radio on AOSP roms or in other ones, i still get call cecho.
whytechapel_x said:
OK. I went on and installed TWRP anyways and flashed tweakwiz and got call echo once more. I am aware that it flashes the blaze radio but still. Does this mean that my phone came out defective? But why is it that i get absolutely no echo on stock ics and luckily, jedi knight 6 neither? When i was using jedi knight 6,i was using the stock radio uvlh1? But if i have this same radio on AOSP roms or in other ones, i still get call cecho.
Click to expand...
Click to collapse
I am not able to exactly help you with your issue as I am using a different ROM than you. However, if you have tried different radios and they did not seem to fix the issue, can you possibly try installing a different kernel? Also, check the phone settings and see if there is an option to turn on 'Noise reduction' which has been mentioned on here before, it seemed to have worked for some people.
So i noticed that i get call echo on all jellybean roms no matter if they are touchwiz or not...frustrating
whytechapel_x said:
So i noticed that i get call echo on all jellybean roms no matter if they are touchwiz or not...frustrating
Click to expand...
Click to collapse
Keep in mind the Touchwiz jb roms are actually built off the leak for the Skyrocket. The same thing happened with ICS way back when and call echo was a rampant problem then as well. I don't recall if anyone really solved the problem before official ICS dropped for Hercules, but I know a lot of devs were working on it.
Call echo in stable AOSP based roms shouldn't be happening. That's what we're trying to correct here.
If you have the time (or are willing), go back to stock unrooted (so you get the radio and everything) and try flashing cm10 stable. Then report back and let us know if call echo still exists. I'm not trying to knock All Star roms, I am just trying to get to the root of your problem and that involves avoiding flashing a radio. As far as I can tell, the flashing of the radio is the biggest difference between your experience and mine.
monkeybuttons said:
Keep in mind the Touchwiz jb roms are actually built off the leak for the Skyrocket. The same thing happened with ICS way back when and call echo was a rampant problem then as well. I don't recall if anyone really solved the problem before official ICS dropped for Hercules, but I know a lot of devs were working on it.
Call echo in stable AOSP based roms shouldn't be happening. That's what we're trying to correct here.
If you have the time (or are willing), go back to stock unrooted (so you get the radio and everything) and try flashing cm10 stable. Then report back and let us know if call echo still exists. I'm not trying to knock All Star roms, I am just trying to get to the root of your problem and that involves avoiding flashing a radio. As far as I can tell, the flashing of the radio is the biggest difference between your experience and mine.
Click to expand...
Click to collapse
will do. but if i remember, i would still get call echo on aokp milestone 1
whytechapel_x said:
will do. but if i remember, i would still get call echo on aokp milestone 1
Click to expand...
Click to collapse
Have you tried any ICS based AOSP roms? Like cm9.1 or AOKP (I can upload the file for you if you want; it is no longer on goo.im). I think I kept ICS AOKP the longest of any rom.
I rooted my SGH-I317 awhile ago using galaxynote2root method. I have CWM recovery v6.0.1.4. I have flashed multiple roms including JellyThunder, Diaphanes and now I'm running Clean Rom.
I dont believe it's rom related because its happened on multiple roms but my problem started on Diaphanes and has continued on Clean Rom. When I am connected to wifi I am almost always not in service and I cannot send or receive messages. I know that I am in an area where I usually get excellent service so I'm not sure what is causing this problem.
I am still learning but I've come a long way thanks to some of you guys and any help would be awesome!
Have you done a full device wipe and restore to stock at any point to test ?
The symptoms you describe sound like something is missing. ..
It's too early to assume a hardware issue. ..
And a stock rom restore that includes the files known to function properly would be a good idea.
I suggest a full wipe, and an Odin restore of a rooted stock build. ...then report the findings. ..g
gregsarg said:
Have you done a full device wipe and restore to stock at any point to test ?
The symptoms you describe sound like something is missing. ..
It's too early to assume a hardware issue. ..
And a stock rom restore that includes the files known to function properly would be a good idea.
I suggest a full wipe, and an Odin restore of a rooted stock build. ...then report the findings. ..g
Click to expand...
Click to collapse
Could you point me in the right direction for such tasks?
All I found was Imnuts guide for such a thing but that is for SGH-I605 I believe.
So maybe my brain was malfunctioning...
Are you saying that I just need to flash a stock rom as I found here...http://forum.xda-developers.com/showthread.php?t=1986556
I thought you meant back to an unrooted version but then I reread it.
I always do a full wipe when I flash roms, so I'd just do that like normal?
meat614 said:
I rooted my SGH-I317 awhile ago using galaxynote2root method. I have CWM recovery v6.0.1.4. I have flashed multiple roms including JellyThunder, Diaphanes and now I'm running Clean Rom.
I dont believe it's rom related because its happened on multiple roms but my problem started on Diaphanes and has continued on Clean Rom. When I am connected to wifi I am almost always not in service and I cannot send or receive messages. I know that I am in an area where I usually get excellent service so I'm not sure what is causing this problem.
I am still learning but I've come a long way thanks to some of you guys and any help would be awesome!
Click to expand...
Click to collapse
What Modem you running? You might not have to flash back to stock.
Try flashing a different modem like the MC3, thats the latest one
I've never messed with my modem so I'd assume its as its always been. Can you link me to it? Is it the same as flashing a rom? Does it matter what rom im on?
Edit: I believe I found the download for mc3. So I just dl, reboot to recovery and flash it?
meat614 said:
I've never messed with my modem so I'd assume its as its always been. Can you link me to it? Is it the same as flashing a rom? Does it matter what rom im on?
Edit: I believe I found the download for mc3. So I just dl, reboot to recovery and flash it?
Click to expand...
Click to collapse
Yes, just reboot to recovery and flash it. There have been some significant improvements for some people after they upgraded to the newest modem. My data speeds over LTE almost doubled after the update.
Hope you get it working.
Very sorry for the late response ...
The thread link you posted is very old ....as we have much newer versions of rooted stock roms.
The latest is UCAMC3....and is available in the development section in several different configurations.
In an attempt to simplify the return to stock, look at the web site in the link you posted. "Scottsroms.com" is found in the developers signature line.
The site contains a rooted, deodexed stock rom that is flashable from recovery, and will produce the desired results while side stepping the need to use Odin.
Simply download the rom to your SD card, then boot to your recovery.
Wipe data/factory reset the device, and flash the new build.
Your original radio image will remain untouched, and once booted, the device will be clean and ready to be set the way you wish.
Ultimately, a simple fresh start is the logical next step....g
wont connect to my data network
Hi I just flashed the hawkish supreme rom to my galaxy note2 att and for some reason it wont connect to my mobile network the imei still there is not wipe but the imei sv says 06 I don't now if it right but I did twice thw flash wipe verything and still no success can anybody help me thanks
itsmekilla76 said:
Hi I just flashed the hawkish supreme rom to my galaxy note2 att and for some reason it wont connect to my mobile network the imei still there is not wipe but the imei sv says 06 I don't now if it right but I did twice thw flash wipe verything and still no success can anybody help me thanks
Click to expand...
Click to collapse
You are likely missing the correct APN settings. ..
Not all roms contain the pre-loaded configuration. ..
Check them in your network settings and enter then save the correct entries. ..
The APN lists can be found in the development section. ...g
thanks
gregsarg said:
You are likely missing the correct APN settings. ..
Not all roms contain the pre-loaded configuration. ..
Check them in your network settings and enter then save the correct entries. ..
The APN lists can be found in the development section. ...g
Click to expand...
Click to collapse
thank you you are the best:good::good:
Always welcome. ...g
New Modem...
Alright guys I tried to take the easy way out and simply flashed the CM3 modem. It has failed me. I've been on it for a few days now and run in to the same problems and maybe even worse.
I just flashed the CA4 modem to try that out (mainly because I have to go to work and dont have time to try a permanent fix right now), so I'll see how it goes. Other than that I believe I will be hitting up scottsrom.com and doing what you mentioned to side step a few of the steps for returning to stock.
I do have 1 question.....I'm on Clean Rom 4.8 and I am aware that there is an updated 4.9. Does it come with a modem? Even if not is it possible that updating would help my problem?
I appreciate the help.
4.9 does not contain a modem...
None of the roms do...with the exception of stock Odin builds...
Seriously. ..I would consider an Odin restore to stock...
You'll get all of the needed files. ..and the issues may resolve. ...g
so it seems that after I moved to an AOSP rom (and then came back) I have a lot of problems. One that is confusing is the fact that I have 2 animations (even after flashing factory ODIN stock rom).
I am getting the samsung swirly graphic animation followed by the sprint 4g lte animation. The funny thing is that the sprint music plays over the samsung animation and then the sprint animation is without sound. Why does the ODIN not clear that old animation?
Anyone else run into this? I cannot seem to clear it even after several factory resets.
P.S.... dont install an AOSP rom unless you want a lot of issues.
I'm not exactly sure what you're describing about the Samsung boot animation. Which aosp ruin did you install? We need to know so that we can have a reference and an idea on how to help, cause not all roms are created equal.
Secondly, the factory reset in recovery mode only clears user data. It doesn't reset your phone to out-of-the-box conditions. So factory testing a million times wouldn't change the boot animation (or the Rom, for that matter).
If you want to try to manually change the boot animation, there's a thread over in the themes and apps section of the Sprint s3 forums, or you can download Rom toolbox pro and they have the option in there.
Finally, most aosp roms are fairly stable. I've been running them exclusively for the past 5 months and they've gotten much more stable over that time. Yes, there are some inherit things that are less stable than on tw roms, but all-in-all, they're fairly stable. The good thing about nandroid backups is that we can flash any number of roms and always go back to something we love. That is, assuming you made a nandroid backup.
Sent from my SPH-L710 using xda app-developers app
edufur said:
so it seems that after I moved to an AOSP rom (and then came back) I have a lot of problems. One that is confusing is the fact that I have 2 animations (even after flashing factory ODIN stock rom).
I am getting the samsung swirly graphic animation followed by the sprint 4g lte animation. The funny thing is that the sprint music plays over the samsung animation and then the sprint animation is without sound. Why does the ODIN not clear that old animation?
Anyone else run into this? I cannot seem to clear it even after several factory resets.
P.S.... dont install an AOSP rom unless you want a lot of issues.
Click to expand...
Click to collapse
I would suggest doing a FULL Wipe before Flashing when switching from AOSP, to TW. Or vis versa. It sounds like you have a bad flash.
What I do is :
DALVIK CACHE
CACHE PARTITION
FORMAT SYSTEM
FORMAT SD:EXT
FORMAT DATA
FORMAT CACHE
THEN WIPE ALL USER DATA/FACTORY RESET
I guess I should have been clear. I did a full wipe both ways... full wipe before installing AOSP (CM10 Stable), and a full wipe when I came back... and factory restore after odin. Even cleared internal storage. Nothing restores the original boot animation. Is there a way to make this thing fully stock out of the box?
Even since the CM10 flash (stable build), my battery now drains faster and GPS locks slower and drifts... it used to not drift.
You can flash freeza's Stock Rooted Rom. The link is below.
http://forum.xda-developers.com/showthread.php?t=1910947
TEAM MiK
MikROMs Since 3/13/11
prboy1969 said:
You can flash freeza's Stock Rooted Rom. The link is below.
http://forum.xda-developers.com/showthread.php?p=2586
Click to expand...
Click to collapse
Could you explain to me how a stock rooted rom is closer to out of the box than the shipped rom which has been factory reset?
Does his stock rooted ROM guarantee to remove the double animation and return the ROM to the original single sprint animation?
And will his rom somehow fix the anomalies that started after I flashed CM10? If so, how does it accomplish what the shipped ROM wont?
edufur said:
Could you explain to me how a stock rooted rom is closer to out of the box than the shipped rom which has been factory reset?
Does his stock rooted ROM guarantee to remove the double animation and return the ROM to the original single sprint animation?
And will his rom somehow fix the anomalies that started after I flashed CM10? If so, how does it accomplish what the shipped ROM wont?
Click to expand...
Click to collapse
What exactly do you mean by "shipped rom" from out of the box? What Android version was it? I know our phones originally shipped with Android 4.0.4, so if you're flashing a "true" out-of-the-box Rom, it'd be 4.0.4. Please help me understand what you've done so that I can help you fix it.
Was the "out-of-the-box" Rom a TAR file that you flashed via Odin? Where did you get it from? I'm getting a little confused when you say you did a "full wipe" (which is typically done in Recovery), but then flashed a Rom through Odin. Typically, people only use one or the other. It's making it more difficult to understand exactly what you did, and therefore it's making it difficult for me (and others) to help you.
As far as your most recent questions: I can't guarantee anything. I'm just a guy who has done a lot of work on his phone who is trying to help you out here. At the end of the day, I have about a 90% passing rate when I give people help (and they actually follow it). And when my directions don't work, I typically stick around and keep helping until they do get their phone working (or until someone else, like Ed or CNexus, picks up the case).
I can say that Freeza's stock rooted rom works exactly like a stock phone (with all updates), but just with Root. It should give you back the stock boot animation and reset everything to stock. The file you want is:
DeOdex:
Sprint Touchwiz Jelly Bean 4.1.2 L710VPBMD4
MD5: 77262D9D6CF1A6AF30A8981A95A75D57
Click to expand...
Click to collapse
You might as well flash the latest baseband/modem. That file is:
MD4 Firmware:
MD4 Firmware/modem/baseband update
MD5: EEEAFDBE59CF9C5B492B1A591EC92D02
Click to expand...
Click to collapse
Well then I appreciate your attempt to help, but that doesn't resolve my problem. I'm sure it can resolve other people's problems (if their problem isnt a double animation problem).
To answer you questions, there are 2 stock roms available that are considered "shipped" ROMS... as in... what the ROM was shipped with. Those ROMS can be flashed via odin and are featured in many of the threads here. When a person flashes these ROMs with odin, it covers everything... recovery, radio, kernel, etc. It removes custom recovery and root. After flashing, one would do a factory reset, either in the rom after it boots, or from the stock recovery. This brings you as close to "out-of-the-box" as you can get... "out-of-the-box" means the way it was when you bought it and opened the box. The problem I am having... is that even after this process, I still have a double boot animation. The samsung with a swirl, and the sprint 4g with flying wires.... and the sprint music plays out of sequence with the sprint part of the animation.
I hope this clears things up for you.
I dont need a new rooted or custom rom... what I do need is to get back 100% to out-of-the-box state. I am close, but the animation is obviously not covered when flashing a shipped rom.
edufur said:
Well then I appreciate your attempt to help, but that doesn't resolve my problem. I'm sure it can resolve other people's problems (if their problem isnt a double animation problem).
To answer you questions, there are 2 stock roms available that are considered "shipped" ROMS... as in... what the ROM was shipped with. Those ROMS can be flashed via odin and are featured in many of the threads here. When a person flashes these ROMs with odin, it covers everything... recovery, radio, kernel, etc. It removes custom recovery and root. After flashing, one would do a factory reset, either in the rom after it boots, or from the stock recovery. This brings you as close to "out-of-the-box" as you can get... "out-of-the-box" means the way it was when you bought it and opened the box. The problem I am having... is that even after this process, I still have a double boot animation. The samsung with a swirl, and the sprint 4g with flying wires.... and the sprint music plays out of sequence with the sprint part of the animation.
I hope this clears things up for you.
I dont need a new rooted or custom rom... what I do need is to get back 100% to out-of-the-box state. I am close, but the animation is obviously not covered when flashing a shipped rom.
Click to expand...
Click to collapse
When Flash, or ODIN the Stock Rom it should include the Stock bootanimation. But since the issue still persists. You can go to THIS thread and get the Stock bootanimation. Also you can use a File Explorer to navigate to system / media to make sure that the permissions are set, and that you only have one file in there.
prboy1969 said:
When Flash, or ODIN the Stock Rom it should include the Stock bootanimation. But since the issue still persists. You can go to THIS thread and get the Stock bootanimation. Also you can use a File Explorer to navigate to system / media to make sure that the permissions are set, and that you only have one file in there.
Click to expand...
Click to collapse
That's the animation that is currently on my phone and is followed by the sprint (Original) animation. The animation you link is not the one that is supposed to be on the phone... only the sprint one should be. The is the problem I am having... I have both on there. I need to figure out how to remove the other one.
edufur said:
That's the animation that is currently on my phone and is followed by the sprint (Original) animation. The animation you link is not the one that is supposed to be on the phone... only the sprint one should be. The is the problem I am having... I have both on there. I need to figure out how to remove the other one.
Click to expand...
Click to collapse
Using a File explorer navigate to system / media. Then delete the one you do not want, and reboot. It should be back to normal.
TEAM MiK
MikROMs Since 3/13/11
Hi all. I've been running a Sprint L710T and am a bit overwhelmed by the variety of opinions regarding what can and can't be currently done on this particular S3 model.
Disclaimer: I am quite new to rooting and ROMS!
How I rooted my Sprint L710T:
1. Used Odin3 v1.85 to flash Sprint CWM recovery v6.0.4.5.
2. Copied SuperSU v2.00 to internal storage on phone.
3. Rebooted into CWM recovery and installed SuperSU v2.00.
4. Rebooted into OS and ran SuperSU, disabled KNOX. Phone is now rooted.
After looking at a few roms, I decided to try Gummy ROM (M3.0-07-16-14-RELEASE-d2lte), Installed without a hitch along with gapps (pa-gapps-stock-4.4.4-20140629-signed). Bear in mind that up till this point I did not know I had a L710T! I was ignorantly working under the assumption that it was a regular Sprint L710. Regardless, I guess I was lucky since at this point all was working in Gummy ROM except for screen rotation being reversed. I then rebooted back into CWM and made a nandroid backup. THANK GOD I did this! After a few days I decided to try some other roms and in ALL OF THEM I had no baseband. Fortunately I was able to revert to my nandroid backup.
So this brings us to the present. I now am aware that I have a L710T so I have not tried any other roms. I want to try out some of the Touchwiz roms but am now concerned that I will mess something up.
Now for some questions I've been pondering:
1. Is there any "danger" in flashing L710 (Non T) roms?
2. Will reverting to my nandroid backup ALWAYS work? Can flashing a particular rom mess things up to the point my nandroid cant save me?
Hopefully we can keep this thread going and make it a source for all things Sprint L710T.
Cheers!
TujungaGuy said:
Hi all. I've been running a Sprint L710T and am a bit overwhelmed by the variety of opinions regarding what can and can't be currently done on this particular S3 model.
Disclaimer: I am quite new to rooting and ROMS!
How I rooted my Sprint L710T:
1. Used Odin3 v1.85 to flash Sprint CWM recovery v6.0.4.5.
2. Copied SuperSU v2.00 to internal storage on phone.
3. Rebooted into CWM recovery and installed SuperSU v2.00.
4. Rebooted into OS and ran SuperSU, disabled KNOX. Phone is now rooted.
After looking at a few roms, I decided to try Gummy ROM (M3.0-07-16-14-RELEASE-d2lte), Installed without a hitch along with gapps (pa-gapps-stock-4.4.4-20140629-signed). Bear in mind that up till this point I did not know I had a L710T! I was ignorantly working under the assumption that it was a regular Sprint L710. Regardless, I guess I was lucky since at this point all was working in Gummy ROM except for screen rotation being reversed. I then rebooted back into CWM and made a nandroid backup. THANK GOD I did this! After a few days I decided to try some other roms and in ALL OF THEM I had no baseband. Fortunately I was able to revert to my nandroid backup.
So this brings us to the present. I now am aware that I have a L710T so I have not tried any other roms. I want to try out some of the Touchwiz roms but am now concerned that I will mess something up.
Now for some questions I've been pondering:
1. Is there any "danger" in flashing L710 (Non T) roms?
2. Will reverting to my nan-droid backup ALWAYS work? Can flashing a particular rom mess things up to the point my nan-droid cant save me?
Hopefully we can keep this thread going and make it a source for all things Sprint L710T.
Cheers!
Click to expand...
Click to collapse
glad your rooted and the info for this model is spread out this forum and im going to post a video about what i know sometime this week on my YouTube channel you can link to my boost root thread if you want cause there is one more method to root this model and it's your kernel that is in charge of your rotation if you flash a custom TW rom you have to somehow restore your stock kernel for good rotation
New L710T
So I just ordered a GS3 from Virgin as it's on a good sale price and I'm desperate for a new phone, then I start googling about ROMs and get super excited to get either CM11 or an unofficial CM12 running...and then I find out I ordered an L710T.
So couple things. I would be more than willing to try and backup all of the factory set data from the phone--the stock ROM, stock modem, etc., since this stuff seems to be kind of hard to find and is scattered all about.
However, any ethical questions aside, has anyone ever bought a phone, made backup recoveries to put online and returned it? Because unless I can flash CM11 and then flash a backed up copy of the stock modem and use the phone with data, then I'm probably going to want to return the phone I ordered and get an L710 if I can find one. Does that seem reasonable, flashing stock recoveries after CM11? Or is that likely to break things? Half the reason I ordered a new "flagship" model phone was because my old cheapo had no roms available and not even an unlocked bootloader, so the idea of being stuck with TW roms is a huge disappointment.
I bring to you completely stock builds of Android TW-Lollipop 5.1.1 (N910PVPU4COG5) for the Sprint Samsung Galaxy Note 4.. I built both of these stock rooted ROMs myself from the official Samsung tar ball. The ROM will self root upon flash and it has init.d/busybox support. Knox and Sprint Itson has been removed completely. Both ROMs are completely stock with all of the original factory installed apps. Available in odexed and deodexed . Both ROMs are identical other than one being odexed and the other deodexed. Also included in both ROMs in this thread is the stock OG5 modem and HLOS APN patch to ensure you have the latest modem & APN's from the latest OG5 software.
Other than the removal of Knox and Sprint Itson, these roms are all stock in every other way. They are stock and will stay that way. Please don't ask for mods, changes, etc in this thread. These roms are intended for those people who want the stock roms in their original form with the addition of root and removal of Knox & itson, as well as other members who need a good solid base for their rom projects. I give permission for other dev's to use this rom as your base and I highly recommend that you do so because it is bug-free and built from the official Samsung tar ball. However I do expect credit if you use this rom for any other project. If you like my work please press that Thanks button, rate this thread and consider a kind donation! Enjoy!
Important Notes: Before flashing ANY Lollipop 5.1.1 TW-based ROM, including this one, you MUST first do one of the following:
1. Take the Lollipop OG5 ota update on your phone.
2. Odin flash the stock ALL_SPT_N910PVPU4COG5_N910PSPT4COG5_CL5303209_QB5691107_REV00_user_low_ship_MULTI_CERT.tar.md5
Thanks to @Sunderwear for the tar ball!!! Without him we would NOT have the official rom img's to build from. :highfive:
Once you have correctly updated your Note 4 to Lollipop 5.1.1, DO NOT... I repeat, DO NOT attempt to root your phone before flashing any of my OG5 Android 5.1.1 ROMs. ONLY flash the latest TWRP recovery using odin on your pc. Nothing else. the ROM zip will pre-root your phone as well as flash the stock OG5 pre-rooted OG5 kernel by @freeza
If you are still on any KK or Lollipop 5.0 TW-based ROM such as NIE, OB7, OE1 , OF5 or OB7 (including any KK AOSP/CM-based roms) then you MUST first update to Lollipop 5.1.1 OG5 by one of the two methods I mentioned above BEFORE flashing this ROM. Failure to properly update your device partitions to 5.1.1 OG5 firmware absolutely WILL cause problems. You have been warned, Please don't ask for help if you did not follow my simple instructions above.
Flashing instructions: ***Before beginning the flash/setup process MAKE SURE your battery has at least 50% charge and/or connected to the charger!!!***
1. Backup anything you don't want to lose off your internal and external storage to another location just to be safe.
2. Download the rom using your pc. (downloading with your phone has a much higher risk of file corruption. Not recommended with large files).
3. VERIFY the md5!!! Once the download has finished, compare the AFH md5 using a md5 tool on your pc. (Google "md5 checksum windows").
4. Put the downloaded rom onto your internal storage or external micro sd card.
5. With phone powered off, reboot into recovery by pressing and holding volume up, power and the home button until you see the Samsung logo then release all buttons.
6. Once in recovery choose the wipe button and do a factory reset three times. Optional but recommended is to wipe "Data". This will wipe all of your user data such as google accounts so MAKE SURE you backed up first like I said in step #1 above! Next go to "advanced wipe" and select all of the partitions EXCEPT micro-sd card and internal storage. Internal storage is optional but recommended when first updating to a major software revision such as 4.3 to 4.4 or 5.0.1 to 5.1.1. The reason is to remove left-over data from previous version of Android and start with a clean slate.
7. Choose the "Install" option and select the rom "Sprint_Stock_N910PVPU4COG5_xxx" from either your internal or external micro-sd card. It will flash the rom and give a confirmation once completed.
8. Press "Reboot" then "reboot system". You should get no prompts or warnings about not having root.
9. Initial rom "optimization" will take several minutes while ART builds its cache and the phone will remain on the yellow Sprint Spark screen for about 10 minutes (for the deodexed ROM). Let the phone optimize for at least 10 minutes and the screen WILL eventually turn off or show the setup wizard once it finishes. If the screen turns off then simply turn it on and proceed to setup your phone.
10. Once finished with the setup wizard, wait a few moments and the phone will automatically install the Sprint apps. You must either "accept" or "disagree" with each and every google prompt for these apps or else the installs pause until you do so.. Also you will be prompted for the "connections optimizer". Quickly set it to what you want and close it. That's it! You're done!
flashing anything on your device is done at your own risk. There is no way myself or any other developer can guarantee that flashing this ROM or any other file will not brick your device or otherwise cause some other type of damage. This is just a standard warning. I am not responsible for anything that you do to your device.
Sprint Stock N910PVPU4COG5 Odexed​Sprint Stock N910PVPU4COG5 Deodexed​
XDA:DevDB Information
Stock-Rooted-N910PVPU4COG5, ROM for the Sprint Samsung Galaxy Note 4
Contributors
tx_dbs_tx
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: OG5 or newer!
Based On: ALL_SPT_N910PVPU4COG5_N910PSPT4COG5_CL5303209_QB5691107_REV00_user_low_ship_MULTI_CERT.tar.md5
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2015-08-23
Created 2015-08-24
Last Updated 2015-08-24
General info for those new to building custom roms
Feel free to use this is a base for your rom projects. Here is some basic info for newcomers wanting to make their own custom rom.
# CSC is already setup correctly for sprint as the bootloader has a mind of it's own and I have to lie to it in order for it to properly flash the correct csc for the sprint version.
# For deodexing, I personally use SVA deodexer. It has been the most reliable 99.9% of the time with no fails. Make sure you use the correct version that's compatible with the Note 4... which is the 32bit version. Also, keep in mind that any deodexed apk or jar can still possibly be corrupt without any warnings or error reports from the deodexing tool. Remember this!!! If you suspect you have a bad deodexed file then replace it with the original odexed version from my stock odexed rom and see if the problem resolves. The odexed apk's & jars are 100% originals from the extracted img's of the official Samsung tar ball so they are 100% good. I don't typically deodex with rom kitchens unless they have been updated to fully support Lollipop 5.0 and newer including apktool. The stand-alone deodexers are easier and better in my opinion.
# If you want to change out the kernel, simply swap out the boot.img in the kernel folder. (you will also need to edit the updater-script to remove or edit the ui_script credit to freeza for his stock root permissive kernel. (not mandatory but it would make sense to do this).
# For debloating be careful what you remove from the rom. Don't just remove stuff willy nilly because you think you don't "need" it. Research the apk's and make an educated decision. "MobileInstaller.apk" and "ID.apk" are the two responsible for downloading the bulk of the bloat on first boot so you need to get rid of those two for sure. I personally leave Sprint zone in my roms in order to allow people to have access to their accounts as well as install any of the sprint apps if they do want some of them such as Sprint TV, etc. You can get most all Sprint apps from Google Play also.
# You will obviously want to edit the updater script to change the name of the rom, credits, etc. Just leave the very top line alone as that is my signature and it needs to stay intact. Everything else feel free to edit, just know what you're doing so you don't bork the script.
# Mods for Android 5.1.1 on TW based roms are going to come about as people make them and post guides, etc. Just know that ANY mod that is not specifically for android 5.1.1 on software OG5 WILL NOT work on our new OG5 software builds. All mods will need to be done from scratch specifically for the new OG5 software. So never flash or use a mod that was made for a previous software version or older version of Android. This includes mods for regular apps such as SecSettings, SystemUI, Samsung messaging, Samsung contacts, etc, etc.
So don't do it! The reason is very simple. There is new and different java code in all of the smali/classes. The only time you may be able to use mods from previous software versions is when the latest revision is a small revision with only a few patches. You definitely can't use mods from Android 4.4 on a 5.0 Lollipop rom or a mod from a 5.0 rom on 5.1 without issues. This is your official warning!
# Theming Lollipop (both 5.0 and 5.1) is easier in many ways than any previous version of Android. You will need to learn several things and do a lot of research before you get your feet wet, but I can say that theming is probably the funnest part of making a custom rom. You should definitely learn to theme first. I will not write any tutorials for theming or setting up apktool etc because this stuff can be too technical to explain here. Besides, other people have already written tutorials in the past. Most of the information still applies today. Just make sure you use the LATEST apktool and use a tool that is updated to support Lollipop. I will recommend
3Minit Android Studio for it's all-in-one capabilities and ease of use for those new to decompiling & recompiling apk's. Give it a try. You will find it at http://3minit.com/ I have used it just to try it out but I use VTS mostly. It's more difficult to learn and definetely much more intimidating for beginners but it does a whole lot more and automates a lot of stuff once setup properly.
# There are already guides, instructions, etc here at XDA to help you get started with building roms, working with apk's, jars etc, So do your own researching on the web and get the "latest" info you can find for Android development. The information is out there and it doesn't cost a penny... only a few brain cells to comprehend. However, If you need help with something and you can't find the answers you're looking for, feel free to PM me and I will try to help you or point you in the right direction.
# Also know that there are a LOT of fellow XDA members who each specialize in one or more areas of Android development. If you take a look around you will soon see these smart and very talented people participating in other development threads. If you find a member who you think might be able to help you, just ask your question(s) in an appropriate thread and tag them in your post or perhaps send them a kind pm asking for their help. Generally, most people are willing to help you as long as you are willing to help yourself by way of searching and taking the initiative to figure things out on your own. Nobody wants to hold your hand so don't expect the red carpet treatment from anyone including myself, especially on basic things that you can easily figure out on your own.
That's about it for now...
HAPPY ROM BUILDING!!! My work here is done. Check please!
Reserved
Thank you sir. I might use for my own if it's OK.
Awesome job tx thanks for all ur hard work for this community
Sent from my SM-N910P using Tapatalk
Thanks @tx_dbs_tx for the work you do. We appreciate it.
Just flashed deodexed..i dont have a status bar/notif panel. Ill re download and try again. Report back shortly
Thanks so much!
arrogant437 said:
Just flashed deodexed..i dont have a status bar/notif panel. Ill re download and try again. Report back shortly
Click to expand...
Click to collapse
Thank you for the report. I found the problem with the help of you and another friend and I am re-uploading the rom. It was a simple mistake on my part with the systemui folder. Sorry for the trouble. Deodexed rom link will be updated afterwhile or first thing in the morning since it's so late.
If you want to fix the problem yourself just unzip the rom and go to system/priv-app/SystemUI folder and delete everything EXCEPT the "SystemUI.apk". The other "SystemUI-1.apk" and other "SystemUI" folder needs to be deleted leaving only the one real "SystemUI.apk". I deleted the rom so nobody else downloads it until I get the new rom uploaded . Thanks again for the report.
Massive kudos on the OP! This is how a dev should start a new thread. Well thought out, informative, and best of all, explaining why you should follow directions to a "t". Most informative yet. I can understand somebody asking questions that are answered in the OP, only if there is a language barrier. So many threads get bogged down with the same questions, over and over again. Also, dev is quick to respond on any problems found! Looking forward to Hybrid-X 3.0. Take your time. Always a quality rom with @tx_dbs_tx! :good:
Thank you for the kind words! New deodexed rom is uploaded and the link has been updated. Both ROMs should be perfect. It's very late and I'm off to bed. Enjoy folks!
Haven't run? into u n some time my friend. Glad to c ur still hard at it. Thx for this :thumbup:
Sent from my trltespr using XDA Free mobile app
Just an FYI, this ROM requires the same Netflix fix like Freeza's Rom. It won't work without flashing the zip. Thank you for the Rom.
Great rom to bad I sold my n4 hopefully this will be on s6 edge plus
Sent from my SM-G928P using XDA Free mobile app
dvtmg704 said:
Great rom to bad I sold my n4 hopefully this will be on s6 edge plus
Sent from my SM-G928P using XDA Free mobile app
Click to expand...
Click to collapse
Why would you want a stock rooted rom from an older device ported to a newer device that will be better off with a rooted version of its own stock rom?
Sent from my SM-N910P using XDA Free mobile app
styles420 said:
Why would you want a stock rooted rom from an older device ported to a newer device that will be better off with a rooted version of its own stock rom?
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
Now I Won't have to root I did the msl
treak now I got tether working forget rooting
Sent from my SM-G928P using XDA Free mobile app
Waiting on my Note 4 to arrive. Would this be a good ROM to flash when I unbox it? Provided I do all the updates first. I want to get the rooting and such out of the way first before I activate it on my line. Thanks.
dh350nwo said:
Waiting on my Note 4 to arrive. Would this be a good ROM to flash when I unbox it? Provided I do all the updates first. I want to get the rooting and such out of the way first before I activate it on my line. Thanks.
Click to expand...
Click to collapse
If your going to update it, then yes indeed this this will be great. I'm on it still. Great build
Sent from my SM-N910P using Tapatalk
JoeBear1975 said:
If your going to update it, then yes indeed this this will be great. I'm on it still. Great build
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
This is a wonderful ROM. However, for me...
I wasn't getting calls or texts (I could place calls and send texts) with this ROM. Repeated tries at the ##72786# (or whatever, I'm typing that from memory) reset didn't fix the problem, and updating PRL and Profile didn't fix it, either. I called Sprint, and they did something at their end that fixed the problem. I should have asked exactly what, because I accidentally froze the wrong app and my phone wouldn't boot. So I re-flashed this ROM and then I couldn't get calls or texts again.
Anyone experience this and know of the fix? I fixed my phone by tying it to my Google Voice account, which is nice, because it not only allows me to get calls and texts again, it transcribes voice mails for me. But I'm still curious about what causes the problem and any potential fix.
Incidentally, Titanium used to let you unfreeze an app from the command line, but it appears the "pm" command doesn't exist anymore.
DaggettBeaver said:
This is a wonderful ROM. However, for me...
I wasn't getting calls or texts (I could place calls and send texts) with this ROM. Repeated tries at the ##72786# (or whatever, I'm typing that from memory) reset didn't fix the problem, and updating PRL and Profile didn't fix it, either. I called Sprint, and they did something at their end that fixed the problem. I should have asked exactly what, because I accidentally froze the wrong app and my phone wouldn't boot. So I re-flashed this ROM and then I couldn't get calls or texts again.
Sorry to hear that man, that's sucks. It's that r on Sprint never seem to b too lucky, lol.
Sent From My Emotional N910P
Click to expand...
Click to collapse