Related
Hi, I just signed up to ask this question, but have been lurking for a fair while whilst contemplating rooting my Hero for 2.1, but it appears the day has come where I will get it officially (I know that many of you will see this as madness, seeing as the official update will quite probably destroy my chances of rooting, but I've survived this long and loved using my phone without, so I'm not too bothered.)
Introduction out of the way, I've read a lot about the update coming OTA, but there appears to be no function on my phone for any "check for software updates" or anything similar that I assume would be there were OTA enabled. I have a Non-Branded UK Hero with build number 2.73.405.5 and was wondering if anyone could shed some light on this confusing confusing situation. Sorry if this has been asked before as well, but I couldn't find it in the forum anywhere.
Thanks in advance for your replies
Apparently a message will pop up on your phone screen asking you accept the update and then it will download to your phone over the air so make sure you have a data plan or you will be charged for the data downloading to your phone by your phone company !
I'm at home all day today so can use my Wi-Fi, so getting charged isn't a problem. Is it safe for me to assume that the OTA option will pop up for me when it rolls out to the UK and everything will be hunky dory then or are there drastic actions to be taken ASAP to allow me to update without a hitch?
I was hit with the update before I knew better and it installed.
As soon as it restarted I can no longer access the top of the touch screen.
The notification bar, camera controls, web address bar, ect. there is basically a quarter inch dead spot at the top of my screen.
I tried factory and hard rests with no effect, the issue remains.
I did e mail HTC about this, but I'm not going to hold my breath on a reply, also the Sprint forums are down.
I installed the OTA last night.
My screen is not experiencing the issue you mentioned.
Might take it into a Sprint store for confirmation.
Good luck!
I am really enjoying mine.
I don't seem to be experiencing any issues since the OTA update either. It was the first thing I installed, even before my apps! I hope you get your problem worked out.
No problems here. I installed the OTA updates and have since rooted it as well. No problems.
3 Keyboards installed, Wifi-Tether(still working out the kinks) and its just moving along
no problem here either
Sent from my EVO using Tapatalk
Can we say it's pretty much safe now to go ahead and install the updates without worrying not being able to root after? Also did this update fix the SD Card issue for you? I've experience a couple times now that my card not being able to read until I remove it then place it back in. Even try formatting on the computer with a card reader but still no luck.
Both unrevoked and Toast's method still work after the OTA update.
Can we say it's pretty much safe now to go ahead and install the updates without worrying not being able to root after? Also did this update fix the SD Card issue for you? I've experience a couple times now that my card not being able to read until I remove it then place it back in. Even try formatting on the computer with a card reader but still no luck.
Click to expand...
Click to collapse
I don't know about being able to root after the update. But if you root before and do the update. You don't lose root. Well at least I didn't.
-------------------------------------
Sent via the XDA Tapatalk App
Take it back to the Sprint store and get a free replacement.
TheBiles said:
Take it back to the Sprint store and get a free replacement.
Click to expand...
Click to collapse
Save a trip. Make sure it's a service and repair site before you drive. Unlike other devices, sales only stores are not able to accept exchanges on the evo.
thecodemonk said:
Both unrevoked and Toast's method still work after the OTA update.
Click to expand...
Click to collapse
You should probably clarify that a bit. With Unrevoked, you actually apply the OTA and then root that version. With Toast's method, you're actually writing a version of the old rom onto the phone, thereby overwriting any OTA update you may have had. Then when you apply Flipz rom to it, it wants to update but can't because it fails.
So if you want the OTA, you gotta do Unrevoked for now. Just wanted to clarify that for folks.
sph33r said:
You should probably clarify that a bit. With Unrevoked, you actually apply the OTA and then root that version. With Toast's method, you're actually writing a version of the old rom onto the phone, thereby overwriting any OTA update you may have had. Then when you apply Flipz rom to it, it wants to update but can't because it fails.
So if you want the OTA, you gotta do Unrevoked for now. Just wanted to clarify that for folks.
Click to expand...
Click to collapse
Aha, thanks! I had just read that Toast's worked and hadn't looked much closer.
sph33r said:
With Unrevoked, you actually apply the OTA and then root that version. With Toast's method, you're actually writing a version of the old rom onto the phone, thereby overwriting any OTA update you may have had. Then when you apply Flipz rom to it, it wants to update but can't because it fails.
So if you want the OTA, you gotta do Unrevoked for now. Just wanted to clarify that for folks.
Click to expand...
Click to collapse
sph, since you seem to know what you're talking about, can I bug you with a noob question? Can I follow the first few steps of toast's root process (these):
- Power off the phone
- Hold volume down while powering the phone on. continue to hold volume down until you see the WHITE bootloader screen.
- After a few seconds it will begin to checking for files, and find PC36IMG.zip. while its doing this it will show a blue progress bar while its checking. (this takes 30 - 60 seconds to finish)
- It will then list all the images in the zip and ask you if want to flash. SAY YES
- When its finished it will ask you if you would like to reboot. AGAIN... SAY YES
- At this point it will boot into a rooted rom.
- YOU ARE NOW ROOT!!!
Click to expand...
Click to collapse
.....then just STOP and be able to run apps that require root access? Or, do I need to go through the whole process and load flipz ROM, which does not yet include the OTA update? Sorry if this is a dumb question, but I'm still learning the ins and outs of Android.
Hey I'm having the same problem with the notification bar only, I can access anything else just fine, but I can slide down the task bar at all. I bought the phone and the radio shack guy basically installed the ota as he handed me the phone, although my friend didn't install his ota yet and his task bar rolls down just fine. He postponed his ota because of this. BTW only way I can access it is by home screen menu button.
Ok just realised something since I was writing this from my evo in landscape mode.. I can open the task bar only in landscape not in normal mode. There's a bug right there, guess it only affects random users.
Update
I got my phone from the Sams Club (Radio Shack).
Called Sprint and they told me I am SOL as far as they are concerned, I have to deal with the place I got it from since it didn't ship from their warehouse (sounds like BS to me).
I can see why people are pissed at Sprint, they don't give a rats ass if my phone is having issues and will do nothing to help me get it replaced.
The guy at the Sams has been great the whole time and told me he will call as soon as they get one to replace it with, which since they are Radio Shack you have to figure that Sprint stores will be highest priority to get more phones so who knows how long it will take to get a replacement. I basically have a cool looking expensive battery eater.
I have had one e mail exchange with HTC and they told me to do a factory reset which I had already done twice before I resorted to "tech support". The reset does NOTHING to remove the OTA update. If this is in fact what caused this I can see nothing short of a wipe and reflash of the factory ROM to fix it. I am awaiting HTC's second reply.
I guess a rooted ROM may also be an answer, but since this phone is having issues already I don't know that rooting it would help my cause with getting it legitimately fixed.
A warning to all reading this, Sprint tech support will only tell you to remove the battery to try and remedy any issues you may have. They told me that is all they have been instructed to tell people with Evo issues.
chamelieon said:
Ok just realised something since I was writing this from my evo in landscape mode.. I can open the task bar only in landscape not in normal mode. There's a bug right there, guess it only affects random users.
Click to expand...
Click to collapse
Same here for me with the web browser I can use the upper right and left corners in landscape, but nothing in portrait; I can also drag the notification bar down in g mail in landscape. I will update my ticket with HTC.
Please log this problem...
with both Sprint and HTC.....I have the same problem. I "believe" it started after the OTA.
i'm having the same problem. just got my htc evo with sprint today. the notification bar was working fine until i installed the OTA update. everything else works fine except the notification bar will not work. the only way to access the notification bar is from the home screen by tapping menu and selecting notifications.
my brother got the phone friday when it came out and applied the OTA update and his is working fine.
i emailed HTC i will post the reply as well if anything is different.
i've googled this and apparently there are a few open forums on other sites with plenty of other people having this same issue. nobody seems to have a fix yet.
just a heads up when i called sprint they acted like idiots and told me they couldn't help and to take it to the sprint store to have them troubleshoot it.
that kinda irks me because after ending my 7 year relationship with t-mobile i really thought that sprint would be a little bit better. oh well... you win some, you lose some.
I didn't apply the OTA, but ran into this issue this morning. Taskbar would not roll down...It would start to for a split second, then snap back up.
A soft reset seems to have cured the problem for now.
Hi,
I travel a lot and do not want to do this froyo update on my vibrant for 2-3 months. T-mobile's answer is to "keep hitting postpone every day". It appears there is no way to actually disable the update other than to keep postponing it. I rooted my phone to see if I could stop the ota update.
I found a few things:
1) /system/etc/cacert.txt has t-mobile as a global CA. removing this breaks lots of the stock apps. Does this mean t-mobile is doing man-in-the-middle on all ssl connections? If so, horrid. However, it doesn't stop the ota update.
2) I see a blue and red double arrow in my notification bar stating the update is pending, but nothing in "ps" output that indicates a running application for it.
3) pulling the tmobile sim card and either leaving it out or putting in another sim card (from say etisalat) doesn't stop the update notification. This could mean the update is already on my phone, i just have to find it and delete it.
Thoughts?
The update you are getting notification for is not froyo. Also, there is a 50/50 chance that it will semi brick your phone. Good part is the update will unlock your hardware for download mode and recovery mode.
Sent from my SGH-T959 using XDA App
it seems a double-restart with sim removed means the "DM service" doesn't start, so I don't get the update notifications anymore.
Why wouldn't you want the update? You are doing yourself a disservice.
mr2t32 said:
The update you are getting notification for is not froyo. Also, there is a 50/50 chance that it will semi brick your phone. Good part is the update will unlock your hardware for download mode and recovery mode.
Click to expand...
Click to collapse
ok, whatever the new samsung/tmobile android update is, i don't want it now.
my 3-button recovery mode works fine, that's how i got root.
kangxi said:
Why wouldn't you want the update? You are doing yourself a disservice.
Click to expand...
Click to collapse
The main reason is I'm traveling for the next 2-3 months, and cannot afford to have the phone broken.
I'd like to wait to see what others experience, and possibly wait for a changelog to appear so I can see what's changed between versions.
There have been many threads about the experience and the changelog has been posted. Most of the changes are very positive including reducing the lag on the device and fixing the GPS.
Just search around a little bit and you will find everything you need. If you still have questions, let me know.
QUOTE]1) /system/etc/cacert.txt has t-mobile as a global CA. removing this breaks lots of the stock apps. Does this mean t-mobile is doing man-in-the-middle on all ssl connections? If so, horrid. However, it doesn't stop the ota update.[/QUOTE]
There is no MIM on SSL connections. That is the certificate that the stock apps are signed with.
kmdub said:
QUOTE]1) /system/etc/cacert.txt has t-mobile as a global CA. removing this breaks lots of the stock apps. Does this mean t-mobile is doing man-in-the-middle on all ssl connections? If so, horrid. However, it doesn't stop the ota update.
Click to expand...
Click to collapse
There is no MIM on SSL connections. That is the certificate that the stock apps are signed with.[/QUOTE]
Hi,
My best guess, and I suggested this in another thread about disabling the update, is to go into /system/app and rename wssyncmldm.apk and wssyncmlnps.apk both to .bak, then reboot into recovery, wipe cache, dalvik cache, fix permissions, and reboot.
hope it helps, cheers, =)
I found out 2 things:
1) /system/etc/security/otacerts.zip will disable the update, because the ssl cert check fails.
2) DO NOT rename /system/etc/security/cacerts.bks (the cert keystore) or the system won't boot. I apparently pushed a bad cert keystore to the device and well, soft-bricked it. Everything just goes bad from there.
Everything was so simple with the nexus one. I lost my nexus one when it fell out of my pocket on the escalators at Victoria Peak in Hong Kong. Let me tell you, the nexus one won't survive a 5 story fall onto marble floors.
I was running bionix1.7 when the update came out and never saw a notification for it. Just run a custom rom and it'll probably sidesteap the update and improve the overall quality of your phone.
Sent from my SGH-T959 using XDA App
I ended up following http://forum.xda-developers.com/showthread.php?t=798125 and doing the update myself and keeping root. I uninstalled all the crap tmobile and samsung install to stalk and lie to me. This phone is the new Dell computer, loaded with crap and no clean OS to install for yourself.
I'm getting to pilot having a Galaxy S5 for work since they're finally going to allow a choice of iphone or android instead of just bes5 blackberry devices.
Now I love me some rooted droid, like my Nexus7 and old classic galaxy s 4g.
What exactly is Knox? I read a little that its a bit that you can flag.
Also anyone familiar with Airwatch? When I used to test it i had my rooted devices as compromised.
I may be getting elevated rights to even white list myself but in the meantime since its a company phone, I need to keep it someone stock, so I was hoping for a simpler debloated stock with maybe a toggleable root if no work around for Airwatch is available.
Thelgow said:
I'm getting to pilot having a Galaxy S5 for work since they're finally going to allow a choice of iphone or android instead of just bes5 blackberry devices.
Now I love me some rooted droid, like my Nexus7 and old classic galaxy s 4g.
What exactly is Knox? I read a little that its a bit that you can flag.
Also anyone familiar with Airwatch? When I used to test it i had my rooted devices as compromised.
I may be getting elevated rights to even white list myself but in the meantime since its a company phone, I need to keep it someone stock, so I was hoping for a simpler debloated stock with maybe a toggleable root if no work around for Airwatch is available.
Click to expand...
Click to collapse
Knox is a flag system for Warranty void to my understanding.
Don't know about Airwatch, sorry.
Towelroot will root you in about 5 seconds SO LONG AS YOUR KERNEL DATE IS PRE-June 3rd. SuperSU can Un-root you too if needed. But you can also root, uninstall Towelroot.apk, and debloat the phone with the lists in other threads.
Good luckl
kprice8 said:
Knox is a flag system for Warranty void to my understanding.
Don't know about Airwatch, sorry.
Towelroot will root you in about 5 seconds SO LONG AS YOUR KERNEL DATE IS PRE-June 3rd. SuperSU can Un-root you too if needed. But you can also root, uninstall Towelroot.apk, and debloat the phone with the lists in other threads.
Good luckl
Click to expand...
Click to collapse
No problem. VZ phone should be brand new, delivered today. But then again, when I bought my wife and my Galaxy S 4g's, side by side from the stash, we had totally different setups. one had froyo, other eclair if I recall. even packaging was different. The sticker on my screen had no text, so I left it on. Hers had crap all over.
So hopefully it's got older kernel.
If it is newer, is it that I cannot root at all, or a more complicated method?
For reference air watch is an MDM solution so people can enroll with their personal device, so they can get the corporate email. Also adds an option to remotely wipe the corporate email accounts. Once it detects root it used to kill the email app and stop the emails.
Normally I love to play around with stuff but I don't want to be in limbo without email in between.
I think i should be able to hold off on activating the cell number and just play with it in Wifi mode for the time being, and rock the bold 9930 a few more days.
Thelgow said:
No problem. VZ phone should be brand new, delivered today. But then again, when I bought my wife and my Galaxy S 4g's, side by side from the stash, we had totally different setups. one had froyo, other eclair if I recall. even packaging was different. The sticker on my screen had no text, so I left it on. Hers had crap all over.
So hopefully it's got older kernel.
If it is newer, is it that I cannot root at all, or a more complicated method?
For reference air watch is an MDM solution so people can enroll with their personal device, so they can get the corporate email. Also adds an option to remotely wipe the corporate email accounts. Once it detects root it used to kill the email app and stop the emails.
Normally I love to play around with stuff but I don't want to be in limbo without email in between.
I think i should be able to hold off on activating the cell number and just play with it in Wifi mode for the time being, and rock the bold 9930 a few more days.
Click to expand...
Click to collapse
If it has the newer kernel, you may be able to flash back to NCG root, then modify what is needed, then update to NE9 again, and re-root after.
Nice, the box has SW Ver ending NCG, confirmed Kernel was on May xx.
I had it up but Airwatch kept failing.
I tried Rootcloak. Then saw that needed Cydia substrate.. then saw that needed SELinux changer... Then that needed Knox disabled...
That needs SuperSU.
Air watch still failed.
Removed all of that and installed fine. So I'll play with this some more later.
I guess I can just root up, kill bloatware, and then unroot again.
Well I went to reroot to play with it more, unrooted and still detected as Compromised.
It seems if it sees I have towelroot installed, not even if rooted, its compromised.
At least I narrowed that down. Ill retry rootcloak later and ensure I have towelroot uninstalled.
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