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

Baseband = Unknown?

So this happened:
http://forum.xda-developers.com/lg-g2/help/vs980-twrp-bootloop-botched-lollipop-t3072133
and once that was "fixed" i was able to use the phone, but it was acting funky. like dialing numbers was oddly laggy and while i can successfully call someone, it disconnects almost immediately and the cell network appears to be ... cycling itself for lack of a better term. i went looking at the various versions/info etc in About Phone and see the following
Baseband "Unknown"
Software Status "Modified"
Warranty date code "Unavailable"
The IMEI looks fine, unlike many of the threads i saw in a search.
any advice?

ok, so after doing like 11 things that didnt work, or at least not completely, including losing my twrp access at one point early on (scaring the piss outta me) i have fixed it with a KDZ using:
this guide:
http://www.cellrabta.pk/2013/10/how-to-flash-big-kdz-files-optimus-g-gk-g-pro-g2-and-others/
and this KDZ:
http://forum.xda-developers.com/verizon-g2/development/stock-vs98039a05-kdz-lollipop-t3069041
it wasn't flawless, and some stuff didnt seem to work right, like at :
"Now click at ‘Normal web upgrade test’." the support tool opened but the option to "start upgrade" was greyed out so i went to "options > upgrade recovery" and let it download and install it on its own. oddly enough it looked (on the phone) like it listed both what the assistant downloaded and the one i chose within the flash tool but it seemed to work fine. i just spent about 1/2 hour on the phone with someone without losing connection so thats a bonus, and the baseband is listed now, the Software Status is "Official", and the Warranty date code is missing, or at least i cant find it again anyway. i lost my root, but i dont care at this point. no more taking chances for me, at least not till upgrade time anyway.
hope someone out there finds any of this useful, if for no other reason than to see why one should never tinker with something they cant afford to lose, especially when one is a novice at best.

Deviouz1 said:
ok, so after doing like 11 things that didnt work, or at least not completely, including losing my twrp access at one point early on (scaring the piss outta me) i have fixed it with a KDZ using:
this guide:
http://www.cellrabta.pk/2013/10/how-to-flash-big-kdz-files-optimus-g-gk-g-pro-g2-and-others/
and this KDZ:
http://forum.xda-developers.com/verizon-g2/development/stock-vs98039a05-kdz-lollipop-t3069041
it wasn't flawless, and some stuff didnt seem to work right, like at :
"Now click at ‘Normal web upgrade test’." the support tool opened but the option to "start upgrade" was greyed out so i went to "options > upgrade recovery" and let it download and install it on its own. oddly enough it looked (on the phone) like it listed both what the assistant downloaded and the one i chose within the flash tool but it seemed to work fine. i just spent about 1/2 hour on the phone with someone without losing connection so thats a bonus, and the baseband is listed now, the Software Status is "Official", and the Warranty date code is missing, or at least i cant find it again anyway. i lost my root, but i dont care at this point. no more taking chances for me, at least not till upgrade time anyway.
hope someone out there finds any of this useful, if for no other reason than to see why one should never tinker with something they cant afford to lose, especially when one is a novice at best.
Click to expand...
Click to collapse
Amen, Preach it
I'm trying the above right now- hopefully getting to a working phone by tomorrow. Thanks for sharing.
EDIT- Still no download mode for me so I guess this is another dead end.

damn, sorry youre having even more trouble than i did, which is saying something to be sure. good luck man, hope it all works out for ya. if i had a clue i'd give it to ya.
edit: actually, can you still get into the phone normally? if so try using autorec. thats how i got my twrp back and i think it fixed my download mode too which is how i was able to finally fix mine.

Deviouz1 said:
So this happened:
http://forum.xda-developers.com/lg-g2/help/vs980-twrp-bootloop-botched-lollipop-t3072133
and once that was "fixed" i was able to use the phone, but it was acting funky. like dialing numbers was oddly laggy and while i can successfully call someone, it disconnects almost immediately and the cell network appears to be ... cycling itself for lack of a better term. i went looking at the various versions/info etc in About Phone and see the following
Baseband "Unknown"
Software Status "Modified"
Warranty date code "Unavailable"
The IMEI looks fine, unlike many of the threads i saw in a search.
any advice?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3076993
Sent from My LG G Flex LG-F340K Stock KitKat V20D on LTE Network using XDA Free Mobile app

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...

Flashing 03.61 radio on NRD90U

I'm New to the forums here everyone.
Greetings!
I'm running NRD90U but I'm experiencing some issues with the recent radio update that came with nougat on Verizon. I've searched everywhere on the xda forums and found suggestions to others experiencing similar issues (simultaneous voice and data). With the 03.61 radio, everything worked just fine whereas with 03.72 I have to toggle airplane mode after every reboot in order to have simultaneous voice and data. I have performed all of the suggested things to no avail. HD voice is enabled on my line and I've tried taking it off and putting it back on. Enhanced LTE is set to on and I've toggled that. I've factory data reset. I've wiped cache. I've Tested SIM in another Verizon device and it works fine. I've Put another Verizon SIM in my device and still have the issue. I even gotten a new replacement device. I've sideloaded OTAs. I've flashed factory images. I've literally tried everything suggested here.
All said, I'm wondering if it's possible to flash the older 03.61 radio while keeping everything otherwise the same on my phone with stock Nougat-NRD90U.
I would appreciate input.
Thanks.

[email protected] said:
I'm New to the forums here everyone.
Greetings!
I'm running NRD90U but I'm experiencing some issues with the recent radio update that came with nougat on Verizon. I've searched everywhere on the xda forums and found suggestions to others experiencing similar issues (simultaneous voice and data). With the 03.61 radio, everything worked just fine whereas with 03.72 I have to toggle airplane mode after every reboot in order to have simultaneous voice and data. I have performed all of the suggested things to no avail. HD voice is enabled on my line and I've tried taking it off and putting it back on. Enhanced LTE is set to on and I've toggled that. I've factory data reset. I've wiped cache. I've Tested SIM in another Verizon device and it works fine. I've Put another Verizon SIM in my device and still have the issue. I even gotten a new replacement device. I've sideloaded OTAs. I've flashed factory images. I've literally tried everything suggested here.
All said, I'm wondering if it's possible to flash the older 03.61 radio while keeping everything otherwise the same on my phone with stock Nougat-NRD90U.
I would appreciate input.
Thanks.
Click to expand...
Click to collapse
If you are bootloader unlocked, you can fastboot flash any radio.img you want. If you are not bootloader unlocked, no you can't. The radio.img is universal btw, not specific to a carrier.
Edit: the guide below will help you unlock the bootloader and learn fastboot if you are unfamiliar.
http://forum.xda-developers.com/showthread.php?t=3206928
Sent from my Nexus 5X using Tapatalk

Thanks. I will do that. I appreciate the help.

Is this a problem for other Verizon users too? If so, I just won't upgrade the radio firmware on mine either.

I would highly suspect that the problem is for everybody on Verizon especially since I replaced my device and did all this SIM card changes and things. It is very unnoticeable in that the only time you experience it or see it is if you are making a call on the new nougat radio 03.72, you will see the LTE icon disappear as soon as you make your call, regardless of whether you are on an 'HD call' or not. If you are on the older radio 03.61 that is on marshmallow, then you never experience that problem, ever, ever. Everything is perfect with that "radio." I've done a lot of testing on it, as I said, up to replacing my device, all to no avail. unless using 03.61 which is again, perfect. I wouldn't change if you can avoid it. If you do get the nougat radio though (03.72), it's a nuisance because after the majority of reboots overall, you will come up with everything normal-'looking' with the LTE icon there but when trying to make a call it will disappear and you'll have an exclamation point there until you hang up from the call and LTE comes right back. (unless you're on wifi off course in which case none of this apples). The solution if you find yourself with the 03.72 nougat radio with this happening, is to toggle airplane mode and then you're good to go until the next time you have to reboot. I always check afterwards by calling voicemail to make sure the LTE icon stays while on the call. It will disappear immediately.
I'm going to assume there is some sort of an "initial-boot-handshake" that's not taking place correctly, but DOES communicate correctly coming out of airplane mode when the device is already booted.
Regards
Edit: This may be a regional VZW issue and not a phone or baseband issue.

Verizon has had issues where I live for more than a week.
I live in Northern Ca and they just sorted things out.
Funny, I flashed the Nougat radio on top of 6.x to see if my issue was fixed.
It's not the radio. Mine is finally stable. Not sure what VZW did.

tech_head
Everything was working fine on mine with the marshmallow radio. I didn't have an issue until I updated to nougat.
Hearing what happened with yours makes me think that it's a regional Verizon thing. Hopefully they will fix soon. I'm not holding my breath because it's been about a month here in Central Kentucky
I'm glad yours is working now man.
Cheers!

I'm having a similar problem for the last couple days after flashing the latest update. I may try stepping back to the older radio to see if that fixes my problem. I just hope it doesn't affect my bluetooth, as that's finally working fine again.

heffe2001 said:
I'm having a similar problem for the last couple days after flashing the latest update. I may try stepping back to the older radio to see if that fixes my problem. I just hope it doesn't affect my bluetooth, as that's finally working fine again.
Click to expand...
Click to collapse
Best of luck. Let us know how it goes if you get the chance. Thanks!

Holy crap, I thought it was just me! I did the exact same things (minus an RMA) as the OP to fix the issue with no luck, even downgrading to MTC20F and upgrading to MTC20L and finally Nougat, just to make sure something wasn't getting jacked in the flashing process. I spent an hour on the phone last night w/ a tier 2 tech guys from Verizon and the only issue he could see was that my PRL had an update for my SIM which should happen automatically. He pushed it through from their end but it didn't fix the issue. Normally I don't care about browsing/downloading when I'm on the phone since I hate talking on the phone and get off as soon as possible but it causes another problem which is not acceptable: if I am browsing chrome or doing anything with data, incoming calls go straight to voicemail. Tried switching the phone from "global" to "LTE/CDMA" with no luck-a reboot always kills simultaneous voice and data. I can rule out this being a Verizon issue on my end as when I flashed the MM images to update via OTA this morning, all worked perfectly fine.
Edit: I have called multiple people in my area that are on VZW after having them reboot their phones and all of them maintained simultaneous voice and data. I think it is safe to state that this issue is software/device specific.

bjoostema said:
Holy crap, I thought it was just me! I did the exact same things (minus an RMA) as the OP to fix the issue with no luck, even downgrading to MTC20F and upgrading to MTC20L and finally Nougat, just to make sure something wasn't getting jacked in the flashing process. I spent an hour on the phone last night w/ a tier 2 tech guys from Verizon and the only issue he could see was that my PRL had an update for my SIM which should happen automatically. He pushed it through from their end but it didn't fix the issue. Normally I don't care about browsing/downloading when I'm on the phone since I hate talking on the phone and get off as soon as possible but it causes another problem which is not acceptable: if I am browsing chrome or doing anything with data, incoming calls go straight to voicemail. Tried switching the phone from "global" to "LTE/CDMA" with no luck-a reboot always kills simultaneous voice and data. I can rule out this being a Verizon issue on my end as when I flashed the MM images to update via OTA this morning, all worked perfectly fine.
Edit: I have called multiple people in my area that are on VZW after having them reboot their phones and all of them maintained simultaneous voice and data. I think it is safe to state that this issue is software/device specific.
Click to expand...
Click to collapse
I have done and agree with what you said - other devices(non NEXUS 6p) work fine and 6p works fine on marshmallow. However, tech_head posted above that his I'd all good now and that it was a Verizon issue. I'm not sure where you live but based on tech_head's post, I can't rule out VZW as the problem. One thing is for sure it is an issue here in Central Kentucky on the two NEXUS 6ps that I have had and tried EVERYTHING, like you, on both of them to no avail without marshmallow radio. I haven't tried flashing marshmallow radio on top of nougat. I may just wait and see if VZW or Google work something out to fix it soon with a possible update. Not holding my breath but I believe it will eventually get fixed in the future, OFFICIALLY.
Thanks man.
I appreciate your input.

**

As mentioned earlier in the thread, the radio is independent of the OS version, so why not take 1 or 2 minutes and flash an earlier radio? There is a radio / modem repository thread on XDA with all versions you can just grab and try out. Literally takes less than a minute and if you don't like the results, then just flash it right back. I use Fastboot, but TWRP, FF, NRT, etc. all work equally well. You may also post what you find under "Phone Settings" when typing " *#*#4636#*#* " into the dialer. Report back on your findings.

Here are the screenshot links for my phone settings.
Thanks
OP
http://forum.xda-developers.com/attachment.php?attachmentid=3882483&stc=1&d=1474502181
http://forum.xda-developers.com/attachment.php?attachmentid=3882482&stc=1&d=1474502181

tech_head said:
Verizon has had issues where I live for more than a week.
I live in Northern Ca and they just sorted things out.
Funny, I flashed the Nougat radio on top of 6.x to see if my issue was fixed.
It's not the radio. Mine is finally stable. Not sure what VZW did.
Click to expand...
Click to collapse
Are You running stock nougat now. If so, what is your simultaneous voice and data status with respect to my post.
Thanks
OP

[email protected] said:
I have done and agree with what you said - other devices(non NEXUS 6p) work fine and 6p works fine on marshmallow. However, tech_head posted above that his I'd all good now and that it was a Verizon issue. I'm not sure where you live but based on tech_head's post, I can't rule out VZW as the problem. One thing is for sure it is an issue here in Central Kentucky on the two NEXUS 6ps that I have had and tried EVERYTHING, like you, on both of them to no avail without marshmallow radio. I haven't tried flashing marshmallow radio on top of nougat. I may just wait and see if VZW or Google work something out to fix it soon with a possible update. Not holding my breath but I believe it will eventually get fixed in the future, OFFICIALLY.
Thanks man.
I appreciate your input.
Click to expand...
Click to collapse
No problem bud! I haven't flashed another radio yet either. I will report back after I test a few more things.

Has anyone determined the cause of the problem? Was it the radio firmware after all? There seem to be conflicting answers here.

chaoticyeshua said:
Has anyone determined the cause of the problem? Was it the radio firmware after all? There seem to be conflicting answers here.
Click to expand...
Click to collapse
It is still kind of up in the air. What I do know is that there is a software incompatibility somewhere within nougat here in Lexington, KY, at least. I assume it's the radio software but I'm not certain. I'm not bootloader unlocked at this point so I haven't yet tried to flash marshmallow radio on to stock nougat. I will probably try this in a few days when I have the time to deal with the factory reset it involves. Please refer back to the original post for questions about my reasoning.
It's quite interesting, the problem, as everything with stock nougat - voice and data-wise, works just like marshmallow after I toggle airplane mode after reboot. With marshmallow, it just worked. Very weird. But given I can just toggle airplane mode 1 time for every time I boot, it's just a slight nuisance. Once I toggle airplane mode, everything is good just like marshmallow, as if nothing was ever wrong. It could be something about the boot sequence. It's very interesting. I'm open to ideas at this point.
Thanks.

My 2¢
When i was on 6.0.1 didn't have and issue with radio. i flashed the 7.0 radio while still on 6.0.1, still no issues.
Then i flashed 7.0 OS and that's when the issue started and it was only affecting upload speed download was great. Then i flashed the last radio from 6.0.1 and the issue went away.
P.S.
the data going off during a call is VZW. i had to call to have them fix this even before 7.0 they dont like the fact that we are using a non vzw branded cell.
I'm back on 6.0.1, never signed on to be a beta tester for 7.0?. These days its about profit and quantity and the hell with quality
Sent from my Nexus 6P using XDA-Developers mobile app

spjetrovic said:
My 2¢
When i was on 6.0.1 didn't have and issue with radio. i flashed the 7.0 radio while still on 6.0.1, still no issues.
Then i flashed 7.0 OS and that's when the issue started and it was only affecting upload speed download was great. Then i flashed the last radio from 6.0.1 and the issue went away.
P.S.
the data going off during a call is VZW. i had to call to have them fix this even before 7.0 they dont like the fact that we are using a non vzw branded cell.
I'm back on 6.0.1, never signed on to be a beta tester for 7.0?. These days its about profit and quantity and the hell with quality
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
I appreciate your input. It doesn't sound like our issues are quite the same. I'm not sure though.
What is it that Verizon did for you. That may be the answer to my problems.
Thanks. Best Regsrds.

Nexus 6p constantly dropping signals

Hi,
I have seen some posts here with lost cell connectivity. However my issue is slightly different and started to appear few weeks back. I was rooted running stock 7.1.1 OS with Franco kernel. My phone started to loose signal all the time. You can just look at the signal bar and see the signal strength going all the way from 100% to 0% in every few seconds. I have tried different radio versions, new ROMs, restoring my Nandroid backup etc. Nothing seems to work. Changing to 3g shows the same issue and I have no signal on 2g only mode. I am in AT&T.
Also wanted to add that I can make out going calls from my phone. The issue is when its idle. I don't get any incoming calls due to this issue.
Any help will be highly appreciated. Currently using my office iPhone and feels terrible.

amith007 said:
Hi, I have seen some posts here with lost cell connectivity. However my issue is slightly different and started to appear few weeks back. I was rooted running stock 7.1.1 OS with Franco kernel. My phone started to loose signal all the time. You can just look at the signal bar and see the signal strength going all the way from 100% to 0% in every few seconds. I have tried different radio versions, new ROMs, restoring my Nandroid backup etc. Nothing seems to work. Changing to 3g shows the same issue and I have no signal on 2g only mode. I am in AT&T. Also wanted to add that I can make out going calls from my phone. The issue is when its idle. I don't get any incoming calls due to this issue. Any help will be highly appreciated. Currently using my office iPhone and feels terrible.
Click to expand...
Click to collapse
I'd run up to AT&T and ask for a new SIM. It's free and you rule out something on their end, and the SIM too when they provision it. Is your phone carrier (SIM) locked to AT&T? If so, I'd see about getting it unlocked so you can test other carriers. If already carrier unlocked have you tried borrowing a friends SIM on another network? If signal continues to drop it could be a hardware issue.

v12xke said:
I'd run up to AT&T and ask for a new SIM. It's free and you rule out something on their end, and the SIM too when they provision it. Is your phone carrier (SIM) locked to AT&T? If so, I'd see about getting it unlocked so you can test other carriers. If already carrier unlocked have you tried borrowing a friends SIM on another network? If signal continues to drop it could be a hardware issue.
Click to expand...
Click to collapse
I have tried with another sim. The issue still persist. Also I have tried my sim on a new device and it seems to work fine. So I am almost certain that the issue is with my phone. All I wonder is whether its hardware or software.

amith007 said:
I have tried with another sim. The issue still persist. Also I have tried my sim on a new device and it seems to work fine. So I am almost certain that the issue is with my phone. All I wonder is whether its hardware or software.
Click to expand...
Click to collapse
You sound proficient enough with flashing ROMS, radios, restoring Nandroids to know this already.... you are probably just postponing the inevitable: Back up and pull off all your data, format the partitions, and flash the latest full factory image from your PC using flash-all.bat. You will have your answer very quickly- in fact you will know even before you begin to set up your phone. If you are still under warranty this will be step number one with Google or Huawei.

v12xke said:
You sound proficient enough with flashing ROMS, radios, restoring Nandroids to know this already.... you are probably just postponing the inevitable: Back up and pull off all your data, format the partitions, and flash the latest full factory image from your PC using flash-all.bat. You will have your answer very quickly- in fact you will know even before you begin to set up your phone. If you are still under warranty this will be step number one with Google or Huawei.
Click to expand...
Click to collapse
My Nandroid backup was actually a vanilla 7.0 image. I will give this a try with the flash-all.bat and update here

Any update?