Database Users

Cannot update PRL or Profile Error codes

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

First impressions

I got mine from Amazon yesterday, I already bricked it a few hours ago by messing with the recovery. It should be an easy fix once I get hold of the stock firmware. I got another one coming tomorrow, so I'll focus on just extracting the rom from that one
Bricking aside, I got 20/10mbs down/up on speedtest using my T-mobile US SIM, and the signal indicator showed LTE. Forcing it off LTE I got 10/5mbs down/up.
Battery life is awesome, I used it constantly for 8hrs and only got down to 50%, my note4 would have been dead after that much use with the screen on. The overall feel of Android 6.0 was smooth, no stuttering. There is no bloatware, just a few utilities for fancy wallpapers.
The phone charges faster than any other phone I have. The included TPE case doesnt increase the thickness of the phone too much and I like that It keeps the camera lens off the desk when I set the phone down.
Dual SIM functionality works nice. It was one of the main features I was looking for, though I will miss T-Mobile wifi calling.
Some notes:
I used adb & fastboot in my attempts to root. After running
Code:
fastboot oem unlock
fastboot reboot
the display now showed
Code:
Orange state
Your device has been unlocked and can't be trusted
Your device will reboot in 5 seconds
So it appears that it is best to oem relock it when you're done updating, as the message goes away if you relock.

Backing up the ROM
I found SP Flash Tool v5.1632 for Linux and I've been practicing saving chunks of ROM from my bricked phone. I should be able to grab the recovery portion of the new phones' ROM tomorrow.
Based on the scatter.txt file I've found for the Gionee S8 AmigOS Marshmallow ROM, recovery starts at 0x8000 and is no more that 16Mb is size. So, in theory, I should be able to grab that range of the ROM and flash it using fastboot back to my bricked unit. I'm using the word "bricked", but its far from that, I should just say "unbootable" to be more clear.
Earlier today I was trying to get MTK droid tools to detect my Blu Pure XR so I could extract the scatter file, but It never was detected. All the drivers installed ok, so maybe its not compatible, I'm not sure yet. I'll get back onto that after my first unit is back up and working, hopefully tomorrow.
Edit: I just found a modified MTK Droid Tools for 64bit cpu phones, I'll give this a try too.
Edit next day: I got the second phone this morning. I used SP Flash Tool to grab the recovery.img portion of the new phone, then I used fastboot to flash it to the damaged phone, and it worked fine. The bootloader unlock/relock caused the phone to wipe itself and then re-encrypt the file system, so I lost a few test photos, no big deal. FWIW, I could have flashed the recovery back to the damaged phone using SP Flash Tool, but I wanted to make sure it worked with fastboot, which it did.
Heres the recovery.img for those that may need it and don't have two phones
View attachment xr-recovery.zip
Monday or so my mom gets her phone, so I'll be able to test LTE on AT&T with her SIM card. I just got 34Mbs download on a speed test (T-Mobile), which is is fine, considering all the naysayers reviewing on Amazon who didn't have the guts to buy the phone, saying LTE wouldn't work at all.

I just heard of this device today. I wonder how quick Android 7.x can be flashed over to this, but for $299 it's a good looking phone.

It may be a while since there's not much activity happening on this device yet.
I'm focusing on creating a rooted boot.img right now, as I'll be happy with 6.0 and root. I plan on having this done today. I've never created a custom twrp recovery, but I may try that next.
I need to figure out how to prevent the full wipe after oem unlocking/relocking, that's a real pain having all my setup deleted after every test, as it makes it hard to use the phone while developing.

Got root
Firstly, I'm still learning about Mediatek based devices, so I feel like a noob again. I haven't edited a ROM in several years and there's a lot of crap info on the internet. Most articles that write up "how to root a phone" basically say "Install twrp, then supersu", yeah, thanks
After struggling with all the selinux controls in 6.0, I switched to hack mode. As per phhusson's super-bootimg script, I used his sed technique to force the init in boot.img to not enforce security policy and added his bits to init.rc to load su. I put su and in system.img along with a suid root shell just in case. Its working, I have SuperSu installed, and it pops up to ask me to grant permissions. It won't update its su binary, I've got some permission problem there, but it's not a show stopper. Also,I found its easiest to just leave the bootloader unlocked while testing, I just have to get used to the annoying boot message and 5 second delay.
This week I'll start from scratch and document the procedure I used and hopefully make it repeatable for anyone else who may want to try it. Maybe someone will just port twrp and save me the time of learning how to do it
Some notes on the software I used:
Windows:
* SP Flash Tool with a bogus scatter file to grab the stock ROM sections of my phone as the Linux version would timeout reading large ranged of flash.
Linux:
* mktool to unpack/repack the boot.img
* loopback mounted the system.img to add su to it.
* used img2simg to convert system.img to a sparse image
* fastboot to flash the boot & system images to the phone.

AT&T Speed Tests
No good, ~500kbs up/down, even though signal strength showed 4 bars on 4G. No LTE at all. Changing the band set to 3g/4g had no real effect either way. Don't buy this phone I you plan on using it with AT&T, although my mother hasn't noticed the ****ty 4G in actual use yet (I'll switch her to T-mobile soon).
Update: After using the phone for 1 week, I am extremely pleased with it. I chuckle when I read the negative reviews on all the big phone web sites. Reviewers hate the wiggly button, LOL, but it doesn't bother me as I'm used to it on my Samsungs. Other than the wiggly home button, its a solid phone. I prefer the metal back as opposed to glass. By the way, who's brilliant idea was it who thought an all glass phone was a good idea?
It's not AOSP, but I find it's AmigOS Carefree launcher very pleasant to use, and I've used countless launchers over the years. It's got way better specs than the Nexus 5X and after struggling with the security in 6.0, I'm not in any rush to find out what security bull**** awaits me in 7.0 (for my benefit of course).
On the flip side, I don't use NFC payments, Google Pay, Google Play, no Google anything. All Google stuff disabled. I run my own calendar/contacts/tasks sync server, use oandbackup to save/restore all my apps and settings, the majority of my apps come from f-droid. I don't play games. So I'm not an average user. I've been using Android devices since the Nexus One and I have a pile of phones in front of me. Blu (or Gionee) has shown it can make quite a competitive device that I enjoy using all day, (though I wouldn't be using it at all unless it was rooted, so luckily for both of us that is the case).
Rant: Things that are actually more annoying than a wiggly button:
* Dozens of phone review websites that all publish a review of this phone within 2 days of each other after the phone was released on Aug 29th ,with all the same content. It's like they are all run by the same hack, just to get advertising dollars.
* Websites like rootoreviews.com that use a template on how to root this particular phone using twrp, when twrp doesn't exist yet for the device. WTF is that? Why would someone think this is a great idea? They have the same instruction set for every phone on the site with the make/model info swapped out. Are they just hoping twrp becomes available soon so they have the first post on the topic by default? Lame!

rotohammer said:
No good, ~500kbs up/down, even though signal strength showed 4 bars on 4G. No LTE at all. Changing the band set to 3g/4g had no real effect either way. Don't buy this phone I you plan on using it with AT&T, although my mother hasn't noticed the ****ty 4G in actual use yet (I'll switch her to T-mobile soon).
Update: After using the phone for 1 week, I am extremely pleased with it. I chuckle when I read the negative reviews on all the big phone web sites. Reviewers hate the wiggly button, LOL, but it doesn't bother me as I'm used to it on my Samsungs. Other than the wiggly home button, its a solid phone. I prefer the metal back as opposed to glass. By the way, who's brilliant idea was it who thought an all glass phone was a good idea?
It's not AOSP, but I find it's AmigOS Carefree launcher very pleasant to use, and I've used countless launchers over the years. It's got way better specs than the Nexus 5X and after struggling with the security in 6.0, I'm not in any rush to find out what security bull**** awaits me in 7.0 (for my benefit of course).
On the flip side, I don't use NFC payments, Google Pay, Google Play, no Google anything. All Google stuff disabled. I run my own calendar/contacts/tasks sync server, use oandbackup to save/restore all my apps and settings, the majority of my apps come from f-droid. I don't play games. So I'm not an average user. I've been using Android devices since the Nexus One and I have a pile of phones in front of me. Blu (or Gionee) has shown it can make quite a competitive device that I enjoy using all day, (though I wouldn't be using it at all unless it was rooted, so luckily for both of us that is the case).
Rant: Things that are actually more annoying than a wiggly button:
* Dozens of phone review websites that all publish a review of this phone within 2 days of each other after the phone was released on Aug 29th ,with all the same content. It's like they are all run by the same hack, just to get advertising dollars.
* Websites like rootoreviews.com that use a template on how to root this particular phone using twrp, when twrp doesn't exist yet for the device. WTF is that? Why would someone think this is a great idea? They have the same instruction set for every phone on the site with the make/model info swapped out. Are they just hoping twrp becomes available soon so they have the first post on the topic by default? Lame!
Click to expand...
Click to collapse
Hi theer just curious on how you get it to root then??

Thanks for potentially inspiring some activity here regarding this phone. It looks like an impressive device, but I won't pull the trigger until there're some solid rom options.

Hey brother hope you r doing well. Glad to see this thread with the smartphone similar to mine. My phone is symphony helio s20, mtk6755 helio p10 processors, 4gb ram 64gb rom with the similar system.img and boot.img of gionee s8 & blu pur xr.
I was desperately looking for a pre rooted rom or a custom, custom recovery and rooting tool for almost 2 months, requested so many times all around this site, but unfortunately didn't get any respons (really frustated). I just badly need to root my device but I'm just a noob on modding and tweaking with Roms. I got my stock rom from Service Center, when I bricked my phone flashing a custom recovery. Later I tried all the method found all over the website but non of them are working only misleading. Bricked my phone several times but luckily I managed to reflash the stock rom by sp flash tool. Please keep this good work up and help us root our devices without any hassle. You are doing a really great work so keep it up bro!
Here is the link of my stock firmware with sn write tool if you need it for anything bro.
Best regards
https://drive.google.com/open?id=0BywTv6KKZO4jX3BMMGRGVUFRa28
http://www.mediafire.com/download/7...N_Writer_tool_exe_v1.0_1604.00_All_In_One.rar
http://www.mediafire.com/download/pa2f3wqpf24t0db/Helio_S20_flashtool.zip

thanks in advance
Hey guys, thanks a lot for all your info and everything you posted Could you be so kind to describe how did you root your Pure XR devices??? Big hug from Cuba

I'm going to guess something with KingRoot. This is a rebranded Gionee S8, so China is already no stranger to this phone.

Not surprised about AT&T performance considering I've never seen an unlocked phone support so few LTE bands (2, 4, 7). Ridiculous. It supports less than half of all the LTE bands AT&T uses. Unless your area uses primarily band 2 or 4 you're screwed if you're on AT&T. Even worse if you're on T-Mobile. It only supports ONE band on T-Mobile. Does Blu even realize it's 2016?

bailsafe said:
I'm going to guess something with KingRoot. This is a rebranded Gionee S8, so China is already no stranger to this phone.
Click to expand...
Click to collapse
I tried every rooting tool, including KingRoot, none worked. There's an OTA update for the stock firmware, but I wont be able to install it until after I un-root. I probably retrace the steps I did the first time: backup all my apps, flash the stock firmware, do the OTA, then save/edit it to have root, then flash the result. The phone works so good right now that I'd hate to mess it up.

Tikerz said:
Not surprised about AT&T performance considering I've never seen an unlocked phone support so few LTE bands (2, 4, 7). Ridiculous. It supports less than half of all the LTE bands AT&T uses. Unless your area uses primarily band 2 or 4 you're screwed if you're on AT&T. Even worse if you're on T-Mobile. It only supports ONE band on T-Mobile. Does Blu even realize it's 2016?
Click to expand...
Click to collapse
This was a Gionee S8 originally, which only supported FDD-LTE bands not in use in the USA. It's a miracle they got FDD-LTE in here at all, I guess, but if you're gonna sell in the US market... they really need more bands.
Rotohammer said:
I tried every rooting tool, including KingRoot, none worked. There's an OTA update for the stock firmware, but I wont be able to install it until after I un-root. I probably retrace the steps I did the first time: backup all my apps, flash the stock firmware, do the OTA, then save/edit it to have root, then flash the result. The phone works so good right now that I'd hate to mess it up.
Click to expand...
Click to collapse
That's probably your best bet. I'm surprised KingRoot wouldn't work, even on the newer updates...

hey I was wondering for some reason my blu pure xr does not receive notifications at all except for certain apps and it keeps on disconnecting from messenger and such is there any remedy for this?

orlandotisk said:
hey I was wondering for some reason my blu pure xr does not receive notifications at all except for certain apps and it keeps on disconnecting from messenger and such is there any remedy for this?
Click to expand...
Click to collapse
Press left button to bring up the running apps list, long press the button with 3 rectangles in it, then press "Clean white list". Here, you press"Add into white list" and choose "messenger" and any other apps you don't want "auto cleaned".
For example, my white list includes Alarm Klock, K-9 mail, CSipSimple, Silence (all apps that I want running all the time)

rotohammer said:
I got mine from Amazon yesterday, I already bricked it a few hours ago by messing with the recovery. It should be an easy fix once I get hold of the stock firmware. I got another one coming tomorrow, so I'll focus on just extracting the rom from that one
Bricking aside, I got 20/10mbs down/up on speedtest using my T-mobile US SIM, and the signal indicator showed LTE. Forcing it off LTE I got 10/5mbs down/up.
Battery life is awesome, I used it constantly for 8hrs and only got down to 50%, my note4 would have been dead after that much use with the screen on. The overall feel of Android 6.0 was smooth, no stuttering. There is no bloatware, just a few utilities for fancy wallpapers.
The phone charges faster than any other phone I have. The included TPE case doesnt increase the thickness of the phone too much and I like that It keeps the camera lens off the desk when I set the phone down.
Dual SIM functionality works nice. It was one of the main features I was looking for, though I will miss T-Mobile wifi calling.
Some notes:
I used adb & fastboot in my attempts to root. After running
Code:
fastboot oem unlock
fastboot reboot
the display now showed
Code:
Orange state
Your device has been unlocked and can't be trusted
Your device will reboot in 5 seconds
So it appears that it is best to oem relock it when you're done updating, as the message goes away if you relock.
Click to expand...
Click to collapse
Hey bro how are you? How's family? I hope that everything is well for you and yours. Basically I just wanted to say thanks for sharing such great info. And I'm really glad that there's someone who's onto something like einstein. I just hope that you can figure out a way to get root with your own custom build of twrp recovery using chainfire's supersu to work with this smartphone. Cos that'll be super-awesome right? But I'm just a noob so all I can do is just wish you the best of luck. So best of luck until you crack the code. And I have complete faith in you. You will achieve it I know that for sure. Wish you and yours all the best. And thanks again in advance. Peace!

Does anybody succeed rooting ?
Please share the method!!

so no one knows how to root?

rotohammer was able to achieve root and said he would get back to us with the method on how it was done, but he hasn't posted it yet...

Samfail root success and workarounds

I wanted to start a thread in the AT&T forum for everyone to share there successes and workarounds after rooting with Samfail. I know there is a thread for the root process here https://forum.xda-developers.com/galaxy-note-8/development/root-samfail-galaxy-note8-t3685340 But i wanted this to be a place where we can share also what works for the AT&T phones.
I just rooted tonight, so far all i have done is disable the AT&T bootup sound but going to /system/omc/ATT/res/media/audio/ui and renaming PowerOn.ogg to read PowerOn.ogg.bak
As i figure out more things I'll keep updating the op.
Please feel free to share any tweaks you may know.

dirtydodge said:
I wanted to start a thread in the AT&T forum for everyone to share there successes and workarounds after rooting with Samfail. I know there is a thread for the root process here https://forum.xda-developers.com/galaxy-note-8/development/root-samfail-galaxy-note8-t3685340 But i wanted this to be a place where we can share also what works for the AT&T phones.
I just rooted tonight, so far all i have done is disable the AT&T bootup sound but going to /system/omc/ATT/res/media/audio/ui and renaming PowerOn.ogg to read PowerOn.ogg.bak
As i figure out more things I'll keep updating the op.
Please feel free to share any tweaks you may know.
Click to expand...
Click to collapse
As I sure you've seen my complaining in the root thread -- My main issue is the inability to get full calling features
It is very weird from my perspective in that everything seems to provision properly. I can make WiFi Calls but if I turn Wifi off then try ot make a call the call Ends suddenly unless I turn Enhanced LTE services off. But the really weird thing is that I can make calls in the area near my work (it is a bit more remote than where live) and it does appear that the calls are being made VoLTE. So why would the network in one place allow the calls to go through but in another the calls suddenly end ??? I think the answer to this might be the clue to getting this issue fixed for AT&T users.
I know many of you don't need the full calling features but for me it is essential and I would go without root if I can't find a solution :crying::crying:

jcrompton said:
As I sure you've seen my complaining in the root thread -- My main issue is the inability to get full calling features
It is very weird from my perspective in that everything seems to provision properly. I can make WiFi Calls but if I turn Wifi off then try ot make a call the call Ends suddenly unless I turn Enhanced LTE services off. But the really weird thing is that I can make calls in the area near my work (it is a bit more remote than where live) and it does appear that the calls are being made VoLTE. So why would the network in one place allow the calls to go through but in another the calls suddenly end ??? I think the answer to this might be the clue to getting this issue fixed for AT&T users.
I know many of you don't need the full calling features but for me it is essential and I would go without root if I can't find a solution :crying::crying:
Click to expand...
Click to collapse
Yea i never video or WiFi call (ok maybe have yo WiFi call about 2 or 3 times a year) so losing those two things don't bother me. I've always turned off enhanced lte services since they introduced it simply because it drains more battery plus from what I've googled about it, it don't really pertain to anything i need. I am hopeful though that once people start to use this root method, we'll start to figuring out how to fix everything like normal.

I'm not really sure the purpose to use this root method, its not even really root to begin with. What are your plans with using this method? I mean there are a few fun things to do but not worth a unstable system and 80% battery.

timmy10shoes said:
I'm not really sure the purpose to use this root method, its not even really root to begin with. What are your plans with using this method?
Click to expand...
Click to collapse
Why do you say "it's not really root to begin with"? By doing this method you gain access to root files and to the heart of your phone. SuperSU installs and works, you are able to deodex, theme, modify all as you want if you know what your doing. Sure there are a few issues with it (battery limited to 80%, WiFi calling, and camera) but none of this will get fixed we work on finding out the issue, but root has always brought about some type of issue one way or another in locked bootloader devices. My plan with rooting my phone is to build my rom with the tweaks and mods that i like, run the ad blockers that i like, possibly install xposed (haven't used it in a while). One of the main purposes of root in my opinion is to make your phone the way you like it. I mean you can sit around and wait for someone to make the phone how they like it and then possibly share it with others or you can take the initiative to learn yourself. Not really root to begin with? It's root, just not how it used to be. I hope someone does figure out a different root method that don't render the battery to 80%, i wish i knew how to look for exploits (I'm currently trying to learn) but until then, this is what we have. What are your reasons for believing this is not a real root method?

timmy10shoes said:
I mean its not really root because they are using a modified system file, not finding a real working exploit. It is a leaked factory image and a leaked factory kernel that needs to go with it. The 80% isn't going away. Its built into the kernel with can't be touched or motified. But we can always dream
Click to expand...
Click to collapse
Well that's why I'm still hoping for a different root method they don't have to use leaked files. But i can say that this root method runs a lot smoother than the method we had to use in the S7. This method hasn't been out very long, but is say within the next few months we'll start seeing more development happening . Or at least i hope. I've just recently started making my own roms (i don't release them to anyone being as I'm still learning and can't give a lot of trouble shooting assistance) but it's fun for me to pass the time at work. (I have a real laid back job with nothing to do a lot of times lol)

I mean its not really root because they are using a modified system file, not finding a real working exploit. It is a leaked factory image and a leaked factory kernel that needs to go with it. The 80% isn't going away. Its built into the kernel with can't be touched or motified. But we can always dream
---------- Post added at 04:48 PM ---------- Previous post was at 04:44 PM ----------
I get the fun part of it, thats why I use unlocked devices to flash the good stuff.

timmy10shoes said:
I mean its not really root because they are using a modified system file, not finding a real working exploit. It is a leaked factory image and a leaked factory kernel that needs to go with it. The 80% isn't going away. Its built into the kernel with can't be touched or motified. But we can always dream
---------- Post added at 04:48 PM ---------- Previous post was at 04:44 PM ----------
I get the fun part of it, thats why I use unlocked devices to flash the good stuff.
Click to expand...
Click to collapse
I've thought about buying am unlocked device but have read conflicting posts about service and radio bands messing that are used here in the US so I've always shyed away from them.

I have developed a few roms myself for the Bionic and Razr. Its highly entertaining and I want it myself but there hasn't been true root since the note 3 I believe.
---------- Post added at 04:54 PM ---------- Previous post was at 04:53 PM ----------
dirtydodge said:
I've thought about buying am unlocked device but have read conflicting posts about service and radio bands messing that are used here in the US so I've always shyed away from them.
Click to expand...
Click to collapse
I use unactivated devices. There is a ton on trial and error so I don't use my daily driver for that.

Are there any ROM anywhere for the snapdragon? Also anyone know where the stock firmware is located or can be found? When you go back,is it like it never happened ?

Don_Pachuco said:
Are there any ROM anywhere for the snapdragon? Also anyone know where the stock firmware is located or can be found? When you go back,is it like it never happened ?
Click to expand...
Click to collapse
No roms yet (on AT&T at least that i know of). Not trying to be rude but do you even search, see attached picture. Literally 4 post down from this thread.

I did search, and the one thread that I found, says "link removed". Then further down, it has files for the S8+.

Don_Pachuco said:
I did search, and the one thread that I found, says "link removed". Then further down, it has files for the S8+.
Click to expand...
Click to collapse
https://forum.xda-developers.com/att-galaxy-note-8/how-to/n950u-odin-5-files-stock-firmware-t3715770

Help!!! Please help!!!!
This is my first time with odin or basically anything computer related i am stuck at 2nd step of samfail. can some one please tell me what to do. it says fail (auth) thank you in advance. I have already done step 1 and it failed just like the instructions say but now in step 2 it fails every time. I'm stuck please help!
truly in over my head hear

jforest3026 said:
This is my first time with odin or basically anything computer related i am stuck at 2nd step of samfail. can some one please tell me what to do. it says fail (auth) thank you in advance. I have already done step 1 and it failed just like the instructions say but now in step 2 it fails every time. I'm stuck please help!
truly in over my head hear
Click to expand...
Click to collapse
This is a thread for mods done after rooting, post questions about getting rooted in your root thread please.
https://forum.xda-developers.com/ga...nt/root-samfail-galaxy-note8-t3685340/page323

the %80 max battery issue
I've enjoyed a rooted Note 8(sm-n950u) Nougat7.1.1 for over a week via samFAIL method and am quite thankful to the samfail/pwned team for providing it.
The max battery issue is the only drawback as far as I've noticed so far. I have a nice and speedy phone that is devoid of bloating apps, and vendor/carrier garbage.
As far as the max battery issue, I've done some digging and haven't found a cure yet.
I've noticed a couple things.
in /efs/Battery and in /sys/class/power_supply/battery there is a file named batt_capacity_max that has something to do with the max battery limit which is obvious by name of course.
Notes:
1. You can not change the value in /sys/class/power_supply/battery/. You can edit and write the file without any error or sign of failure; But checking the file immediately afterwards, you'll find that the contents did not change.
2. You can change the file in /efs/Battery/, but the contents are reset upon reboot.
3. The file contains only a number.
In my case, batt_capacity_max contains the number 1000 regardless of the charged state. i.e. It is 1000 when the phone if charged to max, and it is 1000 when the phone is nearly drained.
I change the value to see if it has any effect, and it does.
I interpreted the 1000 as binary 8, and changed to number to 1010 (binary 10). Then I charged the phone only to find that I could not charge the phone past 17% eep! This wasn't a problem though as rebooting the phone or returning the file to its original value restored the function to normal(rooted normal, that is..max 80%).
I've also deleted the file, then charged the phone to find that there was no effect.
I then came across a slightly older xda thread charge to 100 snapdragon root(s8 sampwn)
The thread had a great number of contributors and provided a great deal of background info, but the method described therein has become obsolete or does not apply to the Note 8 i believe.
If anyone has discovered anything effective regarding the battery max limit, I hope they will contribute that info here, or at least link to an existing thread that I may have missed.
One thing I would like to understand is what processe(s) are being employed in this battery limit system. Is it merely a sub-function of the SafetyNet, or something else? I've filtered what I believe are the pertinent logs(dmesg and logcat) trying to find reference to batt_capacity_max but have come up empty.
I have't tinkered with this in a couple days, but I plan to get back to it tomorrow. Anyone has ideas or suggestions, please contribute. personally I don't really care wether I "fix" this issue as much as I am using this pursuit to glean a better understanding of the android/samsung subsystems relative to it. .. to fix it, of course, is ideal.

delete

SM-N910A, Android 6.0.1, Just need to work via WiFi

Daughter had her Note 4 replaced a few months ago, and it had just been sitting there. Earlier this week got a DJI Spark, and the flight controller requires an Android or iOS phone. Got tired of pulling the case off and on MY phone (S8+), so figured I could use hers as a WiFi-only, dedicated device.
My main concern is that I don't think we ever got the phone formally unlocked by AT&T. I've gotten around that so far just by pulling out the sim. It doesn't seem "happy" about it, but hasn't stopped me configuring the phone to do what I need so far - though it would be nice to be able to uninstall all the AT&T apps that are on there even after a full reset/wipe.
So wondering if there is:
A) Some way to unlock this old thing so I can rest easy it won't have an issue waking up one day
B) A more recent ROM and/or security updates (while it mainly will access the Drone/Receiver WiFi I presume I need to still connect to the home LAN occasionally for app updates)
C) Anything I could flash to make it less of a phone and more of a small tablet (since that's how I'll be using it)
Thanks in advance!

If you are saying the phone is locked to AT&T and you want it unlocked then see here:
https://www.att.com/deviceunlock/#/
Apparently no one has been able to root your device before because they cannot unlock the bootloader:
https://forum.xda-developers.com/no...ty-att-note-4-root-knox-list-pledges-t2946770
My recommendation is to do a factory reset and use something like Package Disabler Pro app to freeze unneeded applications.

terminator911 said:
Apparently no one has been able to root your device before because they cannot unlock the bootloader:
https://forum.xda-developers.com/no...ty-att-note-4-root-knox-list-pledges-t2946770
My recommendation is to do a factory reset and use something like Package Disabler Pro app to freeze unneeded applications.
Click to expand...
Click to collapse
Ah... well that's too bad. I like that the phone has a replaceable battery, which makes it almost worth keeping as long as possible for that. Will try your suggestion on the other. Thanks anyway!

Samsung on5 SM-G550T1 easiest way to root.

Sorry if this is wrong place or way to post on here. I am wanting to root the on5 but it is a learning experience. No pc to use. Is there a apk that actually works. Tried kingroot it says device not supported
I have developer options on and the oem toggle on am I ok with that. If anyone has the time and patience and could walk me through how to get going please let me know. Thanks

Jdaddy1 said:
Sorry if this is wrong place or way to post on here. I am wanting to root the on5 but it is a learning experience. No pc to use. Is there a apk that actually works. Tried kingroot it says device not supported
I have developer options on and the oem toggle on am I ok with that. If anyone has the time and patience and could walk me through how to get going please let me know. Thanks
Click to expand...
Click to collapse
Guess I came to the wrong place for advicre

I'm curious too.
You're not the only one who would like to know, but this is an older ( & apparently not widely used) phone that hasn't been sold for a few years so you may not get any answers.

Yea It's was one of my old ones. Wanted to use it to learn. Any suggestions on a older phone that rooting would be simple.? Can a phone be rooted without a computer I've read so much that says either but doesn't sound like it would.

Jdaddy1 said:
Yea It's was one of my old ones. Wanted to use it to learn. Any suggestions on a older phone that rooting would be simple.? Can a phone be rooted without a computer I've read so much that says either but doesn't sound like it would.
Click to expand...
Click to collapse
Sorry for the late reply. It's my current phone & the storage issues are just getting to be ridiculous otherwise I wouldn't be interested in rooting because of the risk of bricking/voiding warranty etc; but I don't know anything else to do. I know that it's possible to root with an app, but it depends on finding a vulnerability that can be exploited with your specific phone. It's different for every phone. If you choose to install a custom ROM you should find one made for your phone too otherwise you're likely to have problems if you try it on a phone that you intend to actually use for calls/texts etc; I had an HTC droid Eris years ago & used a one-click root app & it worked without any problem that I could tell, but it was a phone I wasn't using as my daily driver too, so I wasn't worried about voiding the warranty/radios not working etc;. Cell & sometimes bluetooth & wifi radios not working are common issues with newer ROMs or especially if you choose a ROM not made for your phone. With the Eris I just installed the app, pressed the button & it rebooted, installed a custom recovery & booted into the OS. With the On5 either there isn't a known exploit or there's just nobody willing or able to look for one or both. They would have to still have the phone to be able to look for one. If you have a flea market near you maybe you could go there & see if there's a phone store that you could get an old cheap one you could practice on? I don't remember the app I used, but I'm pretty sure it came from the play store. It seems like I read somewhere that HTC phones were easier to root, but I'm not sure.