Related
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
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...
Hello folks, new to the forum here. My wife and I both recently got Galaxy S7s from Sams, and our carrier is AT&T. For whatever reason, the push updates never happen on my phone, so I am still in 6.0.1, but my wife's has gotten 7.0 pushed to hers. Problem is that after a while (perhaps a couple of days), her phone starts to develop a persistent lag, where she can't really do anything at all, like typing or changing apps, so severe is the lag. The phone was basically useless at that point, so she would have to restart the phone to restore its normal function. But the lag would always return, and she would need restart multiple times per day.
Talking to Samsung and AT&T proved fruitless at getting any troubleshooting done other than factory resetting the phone. That of course fixed the problem, but as soon as the 7.0 push update happened, the lag came back. We eventually got AT&T to send us a new phone on warranty. But just recently her phone got 7.0 pushed and sure enough the lag is back. Clearly the problem is software related, as my phone is still 6.0.1 and runs perfectly.
I am pretty uninitiated in the Android world, and so I was hoping you folks might be able to help us restore her phone, as I am certain we will get no useful help through the "official" channels. We aren't looking to root or anything, but if there is troubleshooting or a guide we could walk through, we would sure appreciate the help.
Thanks!
I had the same problem when my S7 did the update from 6.0.1 to Android 7. I asked AT&T to change the phone and they did. When the new phone did the update the lag problems started again. I downgrade to stock 6.0.1 and disable the update service with Package Disabler. Now I keep on android 6.0.1 (which I like more than the Nougat) and I do not have lag problems.
You could try to flash the Nougat update manually. It's not exactly simple, but a fair amount of reading up on it should prepare you. Obviously you'll lose all personal data, and there's even a chance it might still be laggy for you. There is a guide on how to do this on droidviews.com that helped me tremendously. Make sure that if you try this, you plug in the phone only after it is in download mode and only after Odin is open. Plus you'll need the drivers and to make sure the phone is in USB Debugging mode via developer options, as well as turn on OEM unlock before you try this. Good luck!
Hello,
this question might seem somewhat stupid. I've run into serious bugs on my 3 year old Note 4, they come and go, sometimes they appear many times a week and sometimes not for several months in a row. I have insurance, which ends mid-July. I wanted to send it in over a week ago, but after I've read the terms, I thought that it would be hard to get something from them, since the bug doesn't appear every day. Since I moved the SIM card to another phone over a week ago, the Note worked perfectly. Before it would from time to time refuse to call, tell me that some system app had crashed and reboot. After reboot I'm unable to call again (no signal) and have to turn it off and on again, for it to work. Couple of times it froze completely (had to remove the battery) and some months ago I had WiFi problems (connected, but no data transmission) a couple of times.
I think that it's a hardware problem, but I doubt they would wait for weeks for a bug to appear and I want to rule out software problems first. I want to try "the best possible" ROM (I know, it's in the eye of the beholder). I took a look on the threads about LineageOS 15.1/14.1, 14.1 is called stable, but there are pretty much the same bugs mentioned. I need:
- Perfectly working cameras, phone calls (is it important that I have two numbers (normal and "landline") on the same card?), mobile Internet, WiFi, SD-card support, preferably docking station support (the 5in1-one, OTG, HDMI, SD and whatnot. I would like the S-Pen to work, if not to its full potential, then at least "somewhat". PlayStore/GApps (?) are important. I don't need Fingerprint sensor, NFC, Bluetooth. Though it would be nice if all the builtin sensors would work, since I might get to install FL Studio Mobile/IL Remote on it eventually or play some games (very unlikely).
- Ability to record calls automatically would be nice (I know, GDPR, but whatever)
- The most important thing is that it's as stable, as possible
It would be awesome if I could test the new FirmWare in DualBoot. I have a 32GB microSD card.
I'm not an idiot, but lately I'm seriously lacking free time and concentration skills (I don't feel my best mentally). I don't feel able to go through all the Firmware topics (LineageOS 14+15 alone are 1000 pages long), I would ask very kindly if someone could suggest a suiting Firmware and give me a link to a hopefully straightforward flashing how-to with all the latest download links. I would forever be in your debt. Especially if you could also give me a link on "how to get into that" (migration/getting started). I want to be done on Tuesday, if possible, so I'd have 2+ weeks to test everything as thoroughly, as possible.
I don't know anything about customizing one's phones, except for what's possible out-of-the box and with 3rd-party-apps. But I'm a fast learner. I understand English, German and Russian.
Regards,
k_u_
Hi
[Joke] The perfect ROM is the one YOU build :laugh: [/Joke]
As you speak English, German and Russian (too bad I'm French :laugh: ) I'll assume you live in Europe and you own a N910F.
To get all sensors working (heart rate included) you need stock: one just got out on Sam Mobile with updated BL and modem (DRD1) and April 2018 security update.
You also may consider Alexander's last built.
LOS 15.1 is pretty good as daily driver but I don't think it meets your needs (especially about sensors...), I've been using it for few months.
Can't help about any other custom ROM but in any cases you won't have all sensors on any of them.
You can use SPen Command for the stylus.
I hope this help...
Sent from my Zuk Z2 Pro using XDA Labs
Edit: you own a 910F! The title told me :silly:
IMHO you'd better keep on full stock (or close to) here is a link for Alexander's https://forum.xda-developers.com/no...se-multi-csc-safe-bloat-t3033881/post58925494
Dual boot is a hard work on N910F (never been able to get it work flawlessly :crying: )
barlu said:
Hi
To get all sensors working (heart rate included) you need stock: one just got out on Sam Mobile with updated BL and modem (DRD1) and April 2018 security update.
You also may consider Alexander's last built.
LOS 15.1 is pretty good as daily driver but I don't think it meets your needs (especially about sensors...), I've been using it for few months.
[...]
IMHO you'd better keep on full stock (or close to) here is a link for Alexander's https://forum.xda-developers.com/no...se-multi-csc-safe-bloat-t3033881/post58925494
Dual boot is a hard work on N910F (never been able to get it work flawlessly :crying: )
Click to expand...
Click to collapse
With "all sensors" I meant accelerometer, gyroscope and whatever else is used in games and music software. I don't need heart rate/o2/UV sensors, etc.
I see that there was a German update in February, which I didn't receive (maybe it's for Vodafone-BRANDED devices? I have DQ(I/J/A)1 installed, latest update came on January 1st, I believe) and the latest one is indeed the DRD1 for UK. Does EE stand for the British mobile network operator? Will the firmware work the same in Germany or what would differ? WIll OTA continue to work?
I'm already downloading, the best (first) thing to try would be the original firmware, of course. I just thought, Samsung gave up on that model.
One question:
Add each file to it's respective field in Odin v3.13.1. Use CSC_OXM if you want to do a clean flash and HOME_CSC OXM if you want to keep your apps and data.
Click to expand...
Click to collapse
Is "keeping apps and data" possible/"advisable" in my case? I want to keep everything, but if another firmware "branch" could install with new bugs, maybe it should be installed cleanly.
---
As for Alexander's stuff link - I took a quick look and it's all Chinese to me :laugh: If I'll keep having problems with UK firmware, maybe, I'll take another look on that or LOS 15.1/14.1.
Did you have any problems with LOS? Camera problems are mentioned in bugs (maybe would work fine with a different app?), GPS problems (didn't understand that exactly, "doesn't fix satellites"???). I'd like to have up-to-date Android without Samsung's bloatware, but mostly I'd like a STABLE system.
P.S. Oh, yeah, one more question - what do you mean with "updated BL"?
P.P.S. Will flashing the UK firmware "void my warranty" (I don't have warranty anymore, but will the insurance company see, that I flashed a different firmware? KNOX counter or whatnot. (I called my "meta-insurer" (a proxy company) today and asked if I'm allowed to flash a custom ROM, he said, he's not 100% sure, but thinks, I'm not. I would have to ask the actual insurance company tomorrow or re-read the policy, which I might do later.))?
Hi
My feelings are you're not used to mess with your phone , so you better (for now) stick with official firmware. (No Knox trouble or whatever its Samsung's firmware)
IMHO the best for you is to install the last full stock ( did you already download it?) and follow this tutorial step by step https://samsung-firmware.org/download/GALAXY__Note4__/o2ll/EVR/N910FXXU1DRD1/N910FEVR1DRD1/
You should keep your data and still be able to use your phone in Germany.
If you still have issues you should backup every things you can't afford to loose. Because the repair techs will obviously delete all your data (even if they don't fix anything )
In any cases, with you want to go for a custom ROM, I'll give you an help for it.
Sent from my Zuk Z2 Pro using XDA Labs
Hello Everyone,
Right, I'm just going to give a quick intro to the situation TLDR below.
So I've been on android for a long time, ever since I got rid of my Nokia brick but my girlfriend has been apple since her first phone, so of course, I've been singing androids praises to her about the battery life, rooting and other such android brilliance, then a few months back she said fine but she had a few features she wanted mainly a big screen, removable battery, fingerprint scanner, and a good camera so after looking at loads of phones we settled on the lgv20, and then my headaches with the phone started.
TLDRGot my girlfriend who has been on apple her whole life onto android, didn't work out so great and now I'm looking for some help.
So the current state of the phone is
it's a H910 that was updated to oreo with a H920 kdx then dirtysanterd, then flashed with a rootable oreo rom and rooted with magisk manager, forgive me if I missed anything I did all this a while ago so it's not fresh in my mind and I'm pretty tired right now so il probable edit this later.
But the issues are weird and unlike anything, I have dealt with before so call on the knowledge of any LG v20 gurus for help, the first problem was present out of the box but did seem to get worse after all the flashing and rooting ect, the phone will turn off seemingly at random and won't turn back on until plugged in, and it will also do this if you try to take a photo with flash but not if you use the flash as a torch.
Now the second issue is due to being in the UK and the LG v20 being a US phone and was the reason I started messing with ROMs and rooting, the signal is terrible, I did check to see if this would be an issue before getting the phone and it seemed to be fine for others, but after having this issue and looking a bit deeper I have seen some people having the same issue with signal and having success flashing a modified modem, but I'm worried that it might not work and may make the signal worse, but if anyone has had success getting signal in the UK please let me know how.
Finally, there are just a few annoying things like some pretty heavy slowdown at times and some general glitchiness with apps freezing and crashing, so if there are any good ways to make the phone a bit more optimized and stable while keeping root that would be nice.
Thanks to anyone who reads this, and thank you to anyone who takes the time to share any knowledge and ideas
A lot of stuff there.
Flash issue sounds like a hardware problem but it could be software gone wrong.
Same for signal problem.
I would flash back stock Nougat *US996 KDZ (usa version) to see if the problems go away. Do not root and trial it for a few days.
This will also change the modem which might help signal issue. There is guide to cross flashing variants on this forum and youtube. Search *LGUP patched V20*.
So try this first is my advise.
*is best clean stock rom without network restrictions or bloat