Just curious if I'm able to use the verizon ROM on my sprint apache as the verizon version is AKU2.2 and the sprint version is AKU2.0. Thanks in advance.
MJB
Is there a difference between the roms? Your post is the first I have read that says so. What are the changes?
Well I'm not exactly sure what the changes are, but the underlying operating system is simply a newer build. I figure it would have some minor advantages assuming the aku2.2 rom will work on our sprint devices. Also - I'm personally suffering from the "phantom turnon" problem where the ppc6700's screen turns itself on repeatedly which causes serious battery drain, so hopefully this would be fixed.
Best,
MJB
Regarding the "phantom turnon"
This is the first time I've seen someone mention this problem, so I'd like to shed some light on one possible cause (for all I know, someone's already found this out, so please forgive).
I started noticing that my PPC-6700 was getting turned on somehow while on my belt clip. In fact, every time I took it out, it was already on, unless the battery was already dead.
What I realized was that the magnets in the belt clip that keep the flap closed were actuating the leaf-switch in the case, and causing the phone to turn on when I closed or opened the lid. I mention "closed or opened" because my initial solution was to set a very short power off on battery setting, so even though the phone would turn on when placed in the clip, it would be off after a minute or so, but it would always be on when I took it out.
For a while there I thought I was dealing with the refridgerator lamp question all over again!
Hope this helps someone.
mbial said:
Well I'm not exactly sure what the changes are, but the underlying operating system is simply a newer build. I figure it would have some minor advantages assuming the aku2.2 rom will work on our sprint devices. Also - I'm personally suffering from the "phantom turnon" problem where the ppc6700's screen turns itself on repeatedly which causes serious battery drain, so hopefully this would be fixed.
Best,
MJB
Click to expand...
Click to collapse
Did you apply the ROM update from UTStarcom? They offer patches for every carrier here: http://www.utstar.com/handsets/view_phone_details.aspx?mcode=PPC6700&bID=30&sAct=0
First select your carrier then click on Download at the bottom right.
szlevi said:
Did you apply the ROM update from UTStarcom? They offer patches for every carrier here: http://www.utstar.com/handsets/view_phone_details.aspx?mcode=PPC6700&bID=30&sAct=0
First select your carrier then click on Download at the bottom right.
Click to expand...
Click to collapse
Back in Feb the Sprint 6700 received the Update you just posted. (AKU2.0)
The rest of the cell companies that also use the 6700 received the same update (AKU2.0) a month or so later.
Just recently the every other carrier except Sprint received a new rom update for their 6700, (AKU2.2)
Sprint and UTStarcom refuse to comment on why the ppc6700 didn't received the same update, or if it will ever.
Sprint put the PPC6700 on their discontinued list a few months back....
Thanks for all the replies...unfortunately my phantom turnon problem is not related to the case (in fact i dont even use the case) but rather seems to be related to the phone getting network broadcast notifications (such as new voicemails, or swapping cell) I have yet to try the AKU2.2 ROM but am enticed to do so in the next few days. I'll keep you all posted, hopefully I don't end up with a paperweight.
MJB
Hey where did u get the 2.2 rom from VZW i rly rly need it! please..
Device Self Service 1.1 Doesn't Work on ANY 1.5 based rom I try.. anyone else have this issue?
I havent gone back to stock to test it out in that regard....
Update-- according to Sprint Advanced Support, we are not allowed to update the PRL anymore... we must go to a Sprint store for that update.. this is as of 1.5 weeks ago..
Please check if you can update your PRL.. or is this all BS..
I *had* the same issue.
It's not a problem with your phone AT ALL. It's a problem on Sprint's end within your account, but everyone in Sprint's tech support department is too stupid to listen to reason... even after 5-6 calls and speaking with 7-8 different people.
"No, a hard reset does not fix the problem. Yes, I have turned my phone off and back on..."
The easiest solution is to activate a different phone (your old phone?) on your account, wait a bit, then re-activate your Hero. Be prepared to have Sprint magically declare that your Hero has been reported as being "lost or stolen".
When your Hero is re-activated, the Device Self Service app will likely work flawlessly.
ahhh, thats it.. it was replaced..
I called Sprint and they said that they have removed PRL updates from android users and that I have to go to a Sprint store for further updates. so the Device Self Service has been discontinued.
This came into effect 1.5 weeks ago..according to Advanced support..
very interesting..
Im waiting on a callback for further information..
tyrnight said:
I called Sprint and they said that they have removed PRL updates from android users and that I have to go to a Sprint store for further updates. so the Device Self Service has been discontinued.
This came into effect 1.5 weeks ago..according to Advanced support..
very interesting..
Im waiting on a callback for further information..
Click to expand...
Click to collapse
I don't know what that's all about. I'm obviously a Android user and I updated my PRL OTA less than a week ago and it worked just fine.
tyrnight said:
Update-- according to Sprint Advanced Support, we are not allowed to update the PRL anymore... we must go to a Sprint store for that update.. this is as of 1.5 weeks ago..
Please check if you can update your PRL.. or is this all BS..
Click to expand...
Click to collapse
BS. I updated to 60659 very recently. I can still run an update without issue. Also, my Device Self Service app works.
Both my PRL updates and DSS app were not working when I first got my phone. These issues were caused by problems within my account at Sprint's end, and had *NOTHING* to do with my phone/ROM/EPST/PRL/version/etc.
I jst tried my wifes phone and it still functioned.. using Modaco 2.2 no problems..
of course sprint says **** just to get you off the phone...
grr... their suggestion was to send me out a new phone.. I got it and reactivated.. still DOESNT WORK.....
and yes they are clueless..
lol... activate a non-Android phone on your account?
That's what I did... then re-activated my Hero and everything was good.
Weird I did a PRL update yesterday through self service
I called Sprint about this cause i tried mine and it didnt work. They said they were going to run some tests and found out I was running MoDaCo. They mentioned it by name. Hope they dont kill my warranty. Of course I denied it and flashed the stock ruu so if they test again it is back to stock.
I just wanted to let everyone know.
When they sent ne a replacement, which was stock, it didn't work. My wifes phone is on modaco and it works fine
AGAIN, the problem is not with your phone, but your account.
The problem is 100% on Sprint's end.
I completely agree..
and they realize it.. they just cant figure it out.. even though I told them what you said..
tyrnight said:
I completely agree..
and they realize it.. they just cant figure it out.. even though I told them what you said..
Click to expand...
Click to collapse
I just did a PRL and Profile update on Saturday and it seemed like it worked...Haven't tried Device Self Service though
yea. the old way works still..
just the DSS app fails..
as we speak Sprint is reprovisoning my phone to a pre and back to my hero to see if that works.. I lost data. and it hasn't returned yet.. grrrrr..
It'll come back in a bit.
Sprint says that data can take up to an hour to start working again. In my experience, it starts working within 15 minutes.
40 minutes. and still dead.. lol
I'm on the Gumbo rom and the device self service works fine for me.
animal7296 said:
I called Sprint about this cause i tried mine and it didnt work. They said they were going to run some tests and found out I was running MoDaCo. They mentioned it by name. Hope they dont kill my warranty. Of course I denied it and flashed the stock ruu so if they test again it is back to stock.
I just wanted to let everyone know.
Click to expand...
Click to collapse
You have got to be BSing us lol. How in the hell could they fiugre out your Rom lol. I wonder if it is possible for them to query the phone/build prop file....
I have to change my signature (look below). Sprint just really impressed me. My phone, for reasons idk, dropped my mobile connection. I tried all the ## fixes to no avail. I called Sprint and the guy tried to walk me through it only to really mess my phone up, by the end of the conversation I couldn't even make calls, in fact somehow I had gotten a completely different phone number! It was a mess!
So by this time I was like screw it, I'm taking it in. I have a years worth of titanium back up's, countless nandroids, and pretty much every ROM under the sun on my SD card. I was so frustrated though, I told the guy I don't care if you kill my root and have to reflash factory, just fix my phone.
I came back an hour and a half later to pick up my phone. To my surprise the phone was not only fixed (mobile network reconnected, my phone number restored), but still was on Mik 2.60! The guy told me that when they fixed my phone, not only did they try to fix it, but did everything they could to maintain my root and not reflash the factory!
Big Up to Sprint.
That's pretty sweet, the store I go to has the same type of employees. Very helpful and do whatever they can without making me unroot.
We're comin from a pure power source.
Similar experience here, the employees were actually running Cyanogenmod and know what they were doing.
So for a while now I have not been able to update my PRL or Profile. It hasn't bothered me because for the most part the phone has worked fine until recently. A friend texted me and said he was going to call me. He text back a few minutes later and ask why I didnt answer. Phone was next to me the whole time and it didnt ring or so any kind of notification that he had tried to call. Took him 3 calls before my phone rang and he got through.
I have applied for a few jobs within the past few weeks and have heard nothing from anyone which I am surprised because I was referred to one company by and friend who put in a good word for me and said that his supervisors were really impressed with my resume. So now I feel like this issue could possibly be costing me job opportunities and I want to get it figured out.
The errors are 6602 and 407. I've tried to do it over 4G and put my phone just in CDMA mode for 3G only and get the 407 code for 3G and the 6602 over 4G.
I am running Stock rooted/odexed MK2 and I just did a clean flash of the rom again clearing data/cache and dalvik seeing if that would help which it didn't. I have reflashed the modem seperately also with no help.
I have seen many threads of others having this issue but no answers on a fix. Has anyone experienced this and actually done something that has resolved the issue?
If you feel it may be costing you a job, why not flash a nand of a stock rom, assuming you have one
Sent from my SPH-L720 using XDA Free mobile app
I did, I flashed back to MF9 using this http://www.rwilco12.com/Files/Devic...H-L720)/Stock ROMs/MF9/Full Restore/Unrooted/
Which should be a stock factory restore, still would not update profile or prl. From there I updated to NG2 with Samsung Kies and I am still not able to update either.
tenaciousj said:
I did, I flashed back to MF9 using this http://www.rwilco12.com/Files/Devic...H-L720)/Stock ROMs/MF9/Full Restore/Unrooted/
Which should be a stock factory restore, still would not update profile or prl. From there I updated to NG2 with Samsung Kies and I am still not able to update either.
Click to expand...
Click to collapse
What kernel do you use?
(I fixed this issue I my phone, but SERIOUSLY, what seemed to fix it MADE NO SENSE, so I'm not going to to relate it again, you can look up my posts if you want, but I wouldn't waste your time. I'm more interested in what kernel you are using... if it isn't KT-SGS4, then it doesn't matter.)
Other than that, have you tried the ##72786# dialer code, which is supposed to reset that stuff (didn't fix it for me personally)? You may have to reactivate your phone though (I did), which isn't that much of an issue...
rsngfrce said:
What kernel do you use?
(I fixed this issue I my phone, but SERIOUSLY, what seemed to fix it MADE NO SENSE, so I'm not going to to relate it again, you can look up my posts if you want, but I wouldn't waste your time. I'm more interested in what kernel you are using... if it isn't KT-SGS4, then it doesn't matter.)
Other than that, have you tried the ##72786# dialer code, which is supposed to reset that stuff (didn't fix it for me personally)? You may have to reactivate your phone though (I did), which isn't that much of an issue...
Click to expand...
Click to collapse
For kernel version it shows 3.4.0-2162929 which I'm guessing is the stock NG2. I haven't flashed anything else since updating through Kies to NG2.
I've done the 72786 dial code a handful of times and it still didn't help. The only thing that solved was a issue I had after I first updatd to NG2 I had no working 4G. Phone would only connect to 3G and that was when it was in CDMA only mode. Aside from that it hasn't helped with the PRL/Profile update issue I'm having.
tenaciousj said:
For kernel version it shows 3.4.0-2162929 which I'm guessing is the stock NG2. I haven't flashed anything else since updating through Kies to NG2.
I've done the 72786 dial code a handful of times and it still didn't help. The only thing that solved was a issue I had after I first updatd to NG2 I had no working 4G. Phone would only connect to 3G and that was when it was in CDMA only mode. Aside from that it hasn't helped with the PRL/Profile update issue I'm having.
Click to expand...
Click to collapse
Yeah, that does sound like a stock kernel to me. Have you tried updating it through the Sprint Zone app? In Settings, More Networks, Mobile Networks, Network Mode, if it is not set to Automatic, you can try setting it to that and see if it lets you update after reboot, I have heard that can help but did not fix it for me (I have it set to LTE/CDMA). Have you seen this thread: Galaxy S4/Note 3/Mega - Update Profile/PRL/HFA Fix for Sprint/Boost/Virgin Mobile/etc? It is complex (don't IGNORE steps 5, 6, 7 and 8, which most people in the thread seem to...). I have not personally used this method, I was planning to before my issue resolved itself, but I didn't have a donor GS4 either (damn it, I JUST remembered that I DO, I f*ed up the USB port on my first one and completely forgot about that! BLOW MY MIND! But anyways...).
rsngfrce said:
Yeah, that does sound like a stock kernel to me. Have you tried updating it through the Sprint Zone app? In Settings, More Networks, Mobile Networks, Network Mode, if it is not set to Automatic, you can try setting it to that and see if it lets you update after reboot, I have heard that can help but did not fix it for me (I have it set to LTE/CDMA). Have you seen this thread: Galaxy S4/Note 3/Mega - Update Profile/PRL/HFA Fix for Sprint/Boost/Virgin Mobile/etc? It is complex (don't IGNORE steps 5, 6, 7 and 8, which most people in the thread seem to...). I have not personally used this method, I was planning to before my issue resolved itself, but I didn't have a donor GS4 either (damn it, I JUST remembered that I DO, I f*ed up the USB port on my first one and completely forgot about that! BLOW MY MIND! But anyways...).
Click to expand...
Click to collapse
Thanks for the link I'll check it later. My account is actually a SERO account but I did have working updates when I first got the phone. The phone was also new and activated on the account as soon as I got it.
Sent from my SPH-L720 using Tapatalk
tenaciousj said:
Thanks for the link I'll check it later. My account is actually a SERO account but I did have working updates when I first got the phone. The phone was also new and activated on the account as soon as I got it.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Yeah, I honestly don't really understand what that thread means when it talks about flashing to legacy accounts. I believe I have a SERO account (I don't know, my wife pays the bill... :silly: ) and the updates worked fine until I think messing with the APNs to try to fix my inability to send MMS messages messed things up. I never flashed any legacy accounts or anything.
So... at this point, even though IT MAKES NO SENSE, I will tell you what SEEMED to fix the issue for me. I STRESS, this MAKES NO SENSE TO ME, but after months of being unable to update my PRL/PROFILE, after doing the following, I was suddenly able to update them. It is likely an EXTREME coincidence, but for the hell of it I will now tell you.
Using the Pro version of Solid Explorer, I copied the Carrier folder from the root of my phone to my external SD card. THAT IS IT. YES... THAT IS IT. NOTHING MORE. I did NOT copy it back, I did not change anything. HOW this could possibly have cured the problem would seem to make very little sense, I can only conjecture that Solid Explorer, in the act of copying the folder to my external SD card, somehow 'refreshed' something in the carrier folder in the root of my phone... and I am grasping at straws here. I think you can probably understand WHY I did not want to reveal that this is what SEEMED to cure my issue, because it is so unlikely, and more likely an extreme coincidence and something else happened that I am not aware of, but that is the only thing I know of that I did related between when it was not working to when it was. So now you know at least (and as I have told a few others, there is no point in not trying, other than the crushing disappointment of it almost certainly not working)...
I should add as well however, now that it occurs to me, that I use the KT-SGS4 KitKat 4.4 TouchWiz kernel, and had for a long time suffered from a loss of mobile connection and GPS. requiring a reboot to get them back (within a similar time period to my PRL/PROFILE issues). I seem to have fixed the mobile connection/GPS loss by choosing the 'correct' governor to use with that kernel for my ROM, and it is not IMPOSSIBLE that THIS occurred at the time I was able to update my PRL/PROFILE, but I do not remember exactly, and I'm PRETTY CERTAIN I still had the issue with the mobile connection/GPS loss after updating my PRL/PROFILE, so I think that likely rules out KT-SGS4 as a culprit in this issue. (But then, I was forgetting that we already established that you were on a stock kernel...)
KNOWN issues with KT-SGS4 Sprint KitKat 4.4 TouchWiz kernel
rsngfrce said:
Yeah, I honestly don't really understand what that thread means when it talks about flashing to legacy accounts. I believe I have a SERO account (I don't know, my wife pays the bill... :silly: ) and the updates worked fine until I think messing with the APNs to try to fix my inability to send MMS messages messed things up. I never flashed any legacy accounts or anything.
So... at this point, even though IT MAKES NO SENSE, I will tell you what SEEMED to fix the issue for me. I STRESS, this MAKES NO SENSE TO ME, but after months of being unable to update my PRL/PROFILE, after doing the following, I was suddenly able to update them. It is likely an EXTREME coincidence, but for the hell of it I will now tell you.
Using the Pro version of Solid Explorer, I copied the Carrier folder from the root of my phone to my external SD card. THAT IS IT. YES... THAT IS IT. NOTHING MORE. I did NOT copy it back, I did not change anything. HOW this could possibly have cured the problem would seem to make very little sense, I can only conjecture that Solid Explorer, in the act of copying the folder to my external SD card, somehow 'refreshed' something in the carrier folder in the root of my phone... and I am grasping at straws here. I think you can probably understand WHY I did not want to reveal that this is what SEEMED to cure my issue, because it is so unlikely, and more likely an extreme coincidence and something else happened that I am not aware of, but that is the only thing I know of that I did related between when it was not working to when it was. So now you know at least (and as I have told a few others, there is no point in not trying, other than the crushing disappointment of it almost certainly not working)...
I should add as well however, now that it occurs to me, that I use the KT-SGS4 KitKat 4.4 TouchWiz kernel, and had for a long time suffered from a loss of mobile connection and GPS. requiring a reboot to get them back (within a similar time period to my PRL/PROFILE issues). I seem to have fixed the mobile connection/GPS loss by choosing the 'correct' governor to use with that kernel for my ROM, and it is not IMPOSSIBLE that THIS occurred at the time I was able to update my PRL/PROFILE, but I do not remember exactly, and I'm PRETTY CERTAIN I still had the issue with the mobile connection/GPS loss after updating my PRL/PROFILE, so I think that likely rules out KT-SGS4 as a culprit in this issue. (But then, I was forgetting that we already established that you were on a stock kernel...)
KNOWN issues with KT-SGS4 Sprint KitKat 4.4 TouchWiz kernel
Click to expand...
Click to collapse
Yeah that copying the carrier folder don't seem like it would do anything but maybe I'll give it a try. Whats the best way to root right now? I just want to make sure it will let me unroot the phone if it dont work and no trip knox incase I have to bring this in.
Do you know what bootloader you are on? You said you were on Sys MK2, then went back to MF9 and now are on NG2. When you went to NG2, unless you took very specific steps to keep the MF9 bootloader, you would be on the NG2 bootloader now, which includes Knox, and you can no longer go back beyond NAE I think. If you don't know what bootloader you have, get DeviceInfo https://play.google.com/store/apps/details?id=com.jphilli85.deviceinfo from the Play Store and under the Software heading, see what it shows for the last 3 digits for Bootloader. This makes a difference on the best root method.
rsngfrce said:
Do you know what bootloader you are on? You said you were on Sys MK2, then went back to MF9 and now are on NG2. When you went to NG2, unless you took very specific steps to keep the MF9 bootloader, you would be on the NG2 bootloader now, which includes Knox, and you can no longer go back beyond NAE I think. If you don't know what bootloader you have, get DeviceInfo https://play.google.com/store/apps/details?id=com.jphilli85.deviceinfo from the Play Store and under the Software heading, see what it shows for the last 3 digits for Bootloader. This makes a difference on the best root method.
Click to expand...
Click to collapse
Bootloader and software version both show up as NG2 on Device Info.
tenaciousj said:
Yeah that copying the carrier folder don't seem like it would do anything but maybe I'll give it a try. Whats the best way to root right now? I just want to make sure it will let me unroot the phone if it dont work and no trip knox incase I have to bring this in.
Click to expand...
Click to collapse
I'm not an EXPERT on this subject, but if you are on NG2 stock unrooted right now, I believe you can use: CF-Auto-Root to root it. Or, here is a stock rooted version of the NG2 ROM:
[ROM][NG2] Stock Rooted NG2 (which mentions that it has Knox removed).
As far as tripping stuff, I'm somewhat unsure about that to be honest. I have always used Triangle Away on my phone, but it has a warning now not to use it with a custom kernel (which I use). My counter is at 3, but I am out of warranty anyway.
I spent a few hours on chat with Sprint. They couldn't figure it out so I'm bringing it in tomorrow. Guessing I'll get a new phone. The people at the Sprint store seem rather limited in their knowledge, at least they were last time I was there.
Sent from my SPH-L720 using Tapatalk
tenaciousj said:
I spent a few hours on chat with Sprint. They couldn't figure it out so I'm bringing it in tomorrow. Guessing I'll get a new phone. The people at the Sprint store seem rather limited in their knowledge, at least they were last time I was there.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I guess if there are no signs that it has been rooted, that's probably a good way to go. You apparently had a phone pre-Knox and now I think you will get one with a Knox system, but it doesn't matter in your case since went beyond the point of no return already with the bootloader... I don't know if you have the new Spark model (tri-band), I don't know if the still make the old plain one like I have anymore...
rsngfrce said:
I guess if there are no signs that it has been rooted, that's probably a good way to go. You apparently had a phone pre-Knox and now I think you will get one with a Knox system, but it doesn't matter in your case since went beyond the point of no return already with the bootloader... I don't know if you have the new Spark model (tri-band), I don't know if the still make the old plain one like I have anymore...
Click to expand...
Click to collapse
I got the phone I have now about a month after the GS4 came out so its non sparks. I stayed on MK2 for so long because I couldn't find a newer rom that looked to be stable and not have to jump through a bunch of hoops to install it. The Odin screen shows everything being zero and offical software so I should be good. I am going to sign out of all of my accounts before I bring it in being I have a lot of apps bought through the store that only work on rooted phones. I hope I can get a tri band to replace it. My friend has a triband GS4 and it gets much better data speeds than mine.
Yeah, I mentioned elsewhere here before that I actually didn't know of the existence of the "Sparks" version of the G4. I screwed up the USB port on my G4 before upgrade time, so I had to buy another G4 on Amazon. Upgrade time has come up, so I was just looking and saw my phone listed as "Non-Sprint Sparks", which I thought meant that they called it the "Sparks" model because I hadn't bought it from Sprint... took me a while to figure out what that actually meant... :laugh:
Sprint online nor the store could fix it so I got a new one.
No rooting but error 407
As titled, I've not rooted the phone. I'm getting error code 407 on attempts to update PRL and Update profile. Download updates manually does nothing. Note I'm on a Samsung Note 4, Sprint. Had updated to Marshmallow 6.0.1 late March but then above actions persist since then. I'm using Wi-Fi only, Sprint service disconnected as I couldn't pay bill when I lost job during a disabling illness.
I haven't been able to update prl profile or firmware for over 8 months. I am not rooted never have been I have called customer service over and over replaced SIM card did the ## stuff nothing has helped. The phone works although service isn't as good as it could be and says there is a prl update available but I always get connection error 6 on all 3. I also have serious battery draining issues as far as my data I do get a strong 4g lte connection just service is low and sometimes drops when I am close to a sprint tower every other phone gets full bars really on any network especially sprint. I hope someone can help I like my sph-720 other that that and honestly I can't afford to keep up with the Joneses. Hopefully this is enough info please help
00Lee said:
I haven't been able to update prl profile or firmware for over 8 months. I am not rooted never have been I have called customer service over and over replaced SIM card did the ## stuff nothing has helped. The phone works although service isn't as good as it could be and says there is a prl update available but I always get connection error 6 on all 3. I also have serious battery draining issues as far as my data I do get a strong 4g lte connection just service is low and sometimes drops when I am close to a sprint tower every other phone gets full bars really on any network especially sprint. I hope someone can help I like my sph-720 other that that and honestly I can't afford to keep up with the Joneses. Hopefully this is enough info please help
Click to expand...
Click to collapse
Have you done a factory reset via recovery? Or you might want to flash latest full stock