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
Hi buddies
As Grarak chose to close the thread of his rom and that maybe some of you want to have some more return and exchanges about the way the rom works, discuss about bugs etc, i open this thread, so that we will be able to do what a forum is done for : talk and exchange together.
New version is 12082014, any return?
Testing soon..
Is calling with sim 2 in 2g working Now?
If not how to use it Any tetsters!
Edit :still No sound from sim2
and there is No way to chose network type
and No 3g from sim 2 too
Im on 9-12-14 build....2g sim not working same as official cm11....3g sim is working......
i 've had terrible battery life, and searching on google lead me to a battery misc processus eating battery, problem solved with 5.0.1 by google
do you guys have the same experience, and have heard about a fix incorporation in the new builds? :good:
I had to go all the way back to the 11-20-14 build. I tried updating to the new builds 12-8, 12-9 and 12-10. No data at all on any of these builds.
Flashed the newest build! We're on Lollipop 5.0.1 now This update is supposed to help battery life. We'll see.
The new music app automaticaly force closes, and the DSPmanager was replaced with AudioFX.
thank you guys for these feedbacks.
Foxy, when you say the new music app, you mean the cyanogenmod one? strange, what could have change ?
Audio playback is fixed now ?
fabulous69 said:
thank you guys for these feedbacks.
Foxy, when you say the new music app, you mean the cyanogenmod one? strange, what could have change ?
Audio playback is fixed now ?
Click to expand...
Click to collapse
I don't know? It's just called "Music" but the icon is like a poorly designed not lollipop looking purple circle. But Apollo is gone so I suppose that's it. And audio playback works, just the app crashes right when I open it.
FoxyDrew said:
I don't know? It's just called "Music" but the icon is like a poorly designed not lollipop looking purple circle. But Apollo is gone so I suppose that's it. And audio playback works, just the app crashes right when I open it.
Click to expand...
Click to collapse
mhm then i think a change that has broke the app. I m sure Grarak will correct it in the next release
Ok, the ROM was going great for me, then yesterday at work my phone turned off when it was in my pocket. I tried turning it on, it booted, started doing the boot animation and then did that for five minutes before it shut off again. This time it wouldn't turn back on no matter how many times i tried power cycling or booting into bootloader. When I got home I tried charging it and the light wouldn't even come on. So I plugged it into my PC and the phone showed up as qhsusb_bulk. After researching that i found it means the bootloader got wiped somehow. My question is, how could my bootloader be gone, because as far as I know, no one has gotten their device S-OFF.
your device is bricked
seems there is a solution on the web but not working for everybody and for specific devices
i dont know what to advice you...
i dont know if it is rom related, but if it is, i wont flash this !
Yes that's what i figured. Luckily Amazon was nice enough to give me a new phone once I send that one in. I was just trying to figure out how it would even be possible that my bootloader got fried, considering my device was still S-ON.
any one who tried this rom found any bugs ???????? i want to know the bugs and want to know in htc 816 daul the second sim worked or not
DRAGONMM2010 said:
any one who tried this rom found any bugs ???????? i want to know the bugs and want to know in htc 816 daul the second sim worked or not
Click to expand...
Click to collapse
I'm on a single sim Virgin Mobile variant here. There are bugs, yes. This is basically an alpha going into beta of lollipop. There is no one else developing anything new for this device so this is our best bet yet. Aside for some minor niggles here and there, this ROM is very workable as a daily driver. I would recommend a backup, and try this one out. I like it a lot. Grarak is quite amazing actually, many thanks owed.
kr338r said:
I'm on a single sim Virgin Mobile variant here. There are bugs, yes. This is basically an alpha going into beta of lollipop. There is no one else developing anything new for this device so this is our best bet yet. Aside for some minor niggles here and there, this ROM is very workable as a daily driver. I would recommend a backup, and try this one out. I like it a lot. Grarak is quite amazing actually, many thanks owed.
Click to expand...
Click to collapse
Completely agreed.
kr338r said:
I'm on a single sim Virgin Mobile variant here. There are bugs, yes. This is basically an alpha going into beta of lollipop. There is no one else developing anything new for this device so this is our best bet yet. Aside for some minor niggles here and there, this ROM is very workable as a daily driver. I would recommend a backup, and try this one out. I like it a lot. Grarak is quite amazing actually, many thanks owed.
Click to expand...
Click to collapse
yes, no doubts on his knowledge there!
@FoxyDrew
do you experience better battery life now that we have 5.0.1 ? thx
fabulous69 said:
yes, no doubts on his knowledge there!
@FoxyDrew
do you experience better battery life now that we have 5.0.1 ? thx
Click to expand...
Click to collapse
Didn't test it. Haven't spent enough time on Lollipop because of the no data issue.
I've been playing around with the lastest builds, and I'm actually getting LTE to work without modifying anything, I just have to let it sit for a WHILE and it connects and works quite well.
HOWEVER, I have been getting a corrupt data partition issue with some non-google play apks. I assume that since the build are already not stable, adding homemade, root apks that modify data might cause some corruption. I'll keep playing with it and report back any further updates on how this may be happening.
thirteen_percent said:
I've been playing around with the lastest builds, and I'm actually getting LTE to work without modifying anything, I just have to let it sit for a WHILE and it connects and works quite well.
HOWEVER, I have been getting a corrupt data partition issue with some non-google play apks. I assume that since the build are already not stable, adding homemade, root apks that modify data might cause some corruption. I'll keep playing with it and report back any further updates on how this may be happening.
Click to expand...
Click to collapse
Yah data works...just not good. It has to do with not being able to access APN's.
No one want's to sit "for a WHILE" to open a webpage or read an email.
On the latest build, System UI crashes.
UPDATE: The ROM has been updated to version 2 where lot of bugs have been fixed!
First things first:
The ROM is strictly for those who are using an unlocked N910P on a GSM SIM globally!
This ROM has been ported by @anggara08 for the Snapdragon Powered Galaxy Note 4. He is the creator of this ROM and I'm only sharing the thread link here so that N910P users (which is generally not supported by the OP of original thread) can take a look at what this ROM has to offer.
I'm in no way associated with the ROM development & all the credit for the work goes to @anggara08.
Now, let me come to the main motive of why I am creating this (or sharing this thread) here on N910P thread...
The ROM is being developed keeping in mind the F & G variants of Note 4. However, I did download the ROM on my N910P and it booted successfully. The ROM has few bugs right now like Bluetooth, Flashlight, Hot-Spot cannot be controlled by the toggles, but certain workarounds have been posted by the some users which make this ROM a must try.
So, coming directly to the procedure for flashinf it on N910P:
1. Head over the following thread & read it properly with proper concentration to save your's as well as others time to solve problems that can or could have been avoided.
http://forum.xda-developers.com/note-4/snapdragon-dev/rom-t3440223
(All credit goes to @anggara08)
2. Download all the fixes posted by OP like camera-fix, & lock-screen fix.
3. Do note that the boot-loader & the modem required is PE2 or PG1 (I have tested it on these personally). Any other version does not work like OG5, OK1, PE1,etc.
4. Take a full back-up of your current ROM.
5. Make proper wipes (system, dalvik, data, cacke, internal memory,etc).
6. Flash the downloaded X-ROM. Once the flashing is finished, the ROM will automatically boot without any prompt from the TWRP Recovery.
7. It will take a long time to boot. My suggestion is to keep the phone plugged to a charger while the process is going on so as to prevent battery drain.
There's absolutely no need of flashing any Kernel or Super-SU or anything.
Let the ROM boot first.
8. Once it boots, you'll notice that there will not be any network. For it, you have to download following data fix:
(The zip file is as an attachment at the end of this post, Credit goes to @boot_sect for posting it)
9. Boot into TWRP & flash the Data-Fix. Reboot to the ROM and the network will be there. (Note: I am a GSM SIM user so the fix worked for me. Sprint users, try this out at your own will & risk.)
10. Once the ROM is up & running, flash the respective fixes (as mentioned by me earlier & available on original thread by OP) and you'll have an amazing ROM to play with. :good:
Few suggestions & fixes by @boot_sect:
Additional Notes:
Bluetooth not turning off: Seems to be ROM issue, or at least for us T/W8s. Even without data fix it does not want to turn off...
> Temp fix: Quick and dirty way to disable bluetooth is by going into your favourite app manager (eg. Titanium Backup) and disabling "Bluetooth Share", then re-enabling when bluetooth turns off. This will keep BT turned off until you manually enable it next time (or at least, for a very long time.)
Flashlight not turning off. Most likely ROM issue as many users are experiencing this.
> Temp fix: Use "Quick Tools" in the Edge Panel to turn it off. Thanks to @justforgot to finding this workaround.
I'm not posting any screen-shots of the ROM as a dedicated video of it on N910F can be found on the original thread.
Last but not the least, If moderators find this thread useless, they are free to close it.
@Robin...Thanks for hooking us up to this and taking time for the right up.
Sent from Nowhere
how long we have to wait?
how long we have to wait for the first boot?..and thanks
Was able to boot it up and play with it but no go on the data for sprint. I tried manually setting apn and nothing also the screen goes dim after a while. Nevertheless it is awesome seeing this thing running and cannot wait for the geniuses to stabilize it. One awesome thing I noticed it is how little bloat it had almost no apps aside from the essentials.
abel1233 said:
how long we have to wait for the first boot?..and thanks
Click to expand...
Click to collapse
It should not take more than 15-20 mins... If it does, pull out the battery (though not recommended in first place) and try again.
innthesun said:
Was able to boot it up and play with it but no go on the data for sprint. I tried manually setting apn and nothing also the screen goes dim after a while. Nevertheless it is awesome seeing this thing running and cannot wait for the geniuses to stabilize it. One awesome thing I noticed it is how little bloat it had almost no apps aside from the essentials.
Click to expand...
Click to collapse
Did you not get the data or the network??
Also,did you flash the data-fix for the network or it was available without flashing it?
As far as the bugs are concerned, I can help you out for a work-around.
Hello,
Was anyone able to fix the screen going dim?
robinhood1808 said:
Did you not get the data or the network??
Also,did you flash the data-fix for the network or it was available without flashing it?
As far as the bugs are concerned, I can help you out for a work-around.
Click to expand...
Click to collapse
I did not get data or network. I did flash the fix but it did nothing.
For these international GSM ports to work on cdma, especially our sprint variant, a LOT of work must be done in framework, csc and build.prop. no exceptions. I wish there was an easier solution but that's the only way because by default these GSM roms are setup for GSM networks. I'm working on my own S7/N5 port and this is the last thing i have to do... cell service isn't working. i am trying different ideas as time permits. I have been porting TW roms and doing this stuff for a while and i can say that there is a TON of work that has to be done to even get these new softwares to boot, let alone work fully on a different device all together. mostly hardware, driver and kernel related things which takes a huge amount of time. So you must thank these developers for theit time and patience with this stuff. It's the most difficult challenge when it comes to building out roms. It makes native custom rom building seem like a walk in the park. Trust me. LOL. We'll get it it sooner or later. give it time.
tx_dbs_tx said:
For these international GSM ports to work on cdma, especially our sprint variant, a LOT of work must be done in framework, csc and build.prop. no exceptions. I wish there was an easier solution but that's the only way because by default these GSM roms are setup for GSM networks. I'm working on my own S7/N5 port and this is the last thing i have to do... cell service isn't working. i am trying different ideas as time permits. I have been porting TW roms and doing this stuff for a while and i can say that there is a TON of work that has to be done to even get these new softwares to boot, let alone work fully on a different device all together. mostly hardware, driver and kernel related things which takes a huge amount of time. So you must thank these developers for theit time and patience with this stuff. It's the most difficult challenge when it comes to building out roms. It makes native custom rom building seem like a walk in the park. Trust me. LOL. We'll get it it sooner or later. give it time.
Click to expand...
Click to collapse
Can't wait for the S7 note 5 port! Check back daily for it!!!! ????
tx_dbs_tx said:
For these international GSM ports to work on cdma, especially our sprint variant, a LOT of work must be done in framework, csc and build.prop. no exceptions. I wish there was an easier solution but that's the only way because by default these GSM roms are setup for GSM networks. I'm working on my own S7/N5 port and this is the last thing i have to do... cell service isn't working. i am trying different ideas as time permits. I have been porting TW roms and doing this stuff for a while and i can say that there is a TON of work that has to be done to even get these new softwares to boot, let alone work fully on a different device all together. mostly hardware, driver and kernel related things which takes a huge amount of time. So you must thank these developers for theit time and patience with this stuff. It's the most difficult challenge when it comes to building out roms. It makes native custom rom building seem like a walk in the park. Trust me. LOL. We'll get it it sooner or later. give it time.
Click to expand...
Click to collapse
i can't wait for your rom!!
they are usually the best ones!!
@tx_dbs_tx: You are absolutely right that each and every developer works extremely hard in order to make a ROM boot. We should be really grateful to all the developers like you who make it possible for the users like me to experience difference ROMs on our phones.
It would be really shameful on our part if we can't even thanks a developer for all the hard work that he puts in..
Also, I'm using a GSM SIM (had even contacted you some time ago regarding it, if you remember.. ) on N910P so the above mentioned ROM worked for me without any network issues. I've edited the thread to mention that It's only for those who use GSM SIM on N910P.
tx_dbs_tx said:
For these international GSM ports to work on cdma, especially our sprint variant, a LOT of work must be done in framework, csc and build.prop. no exceptions. I wish there was an easier solution but that's the only way because by default these GSM roms are setup for GSM networks. I'm working on my own S7/N5 port and this is the last thing i have to do... cell service isn't working. i am trying different ideas as time permits. I have been porting TW roms and doing this stuff for a while and i can say that there is a TON of work that has to be done to even get these new softwares to boot, let alone work fully on a different device all together. mostly hardware, driver and kernel related things which takes a huge amount of time. So you must thank these developers for theit time and patience with this stuff. It's the most difficult challenge when it comes to building out roms. It makes native custom rom building seem like a walk in the park. Trust me. LOL. We'll get it it sooner or later. give it time.
Click to expand...
Click to collapse
I must say I was not expecting to even boot at all and was surprised when it did. I totally agree with the patience, I use your roms regularly and in fact am using one as we speak and loving it. Many thanks for your time and dedication, it very much appreciated.
I am here to say a BIG thank you. This Rom is working very well, just a few bugs like the bluetooth not turning off and a few other minor things.. Keep up the great work look forward to this Rom progressing.
Droidman61 said:
I am here to say a BIG thank you. This Rom is working very well, just a few bugs like the bluetooth not turning off and a few other minor things.. Keep up the great work look forward to this Rom progressing.
Click to expand...
Click to collapse
You got sprint LTE working?
Cool, will have to check out. I'm also an unlocked gsm user, and am always having to tweak build prop and apn conf files to get my ROMs working properly. Not that I mind.
But cool to see something else to try. Thanks
Awesome Dude
tx_dbs_tx said:
For these international GSM ports to work on cdma, especially our sprint variant, a LOT of work must be done in framework, csc and build.prop. no exceptions. I wish there was an easier solution but that's the only way because by default these GSM roms are setup for GSM networks. I'm working on my own S7/N5 port and this is the last thing i have to do... cell service isn't working. i am trying different ideas as time permits. I have been porting TW roms and doing this stuff for a while and i can say that there is a TON of work that has to be done to even get these new softwares to boot, let alone work fully on a different device all together. mostly hardware, driver and kernel related things which takes a huge amount of time. So you must thank these developers for theit time and patience with this stuff. It's the most difficult challenge when it comes to building out roms. It makes native custom rom building seem like a walk in the park. Trust me. LOL. We'll get it it sooner or later. give it time.
Click to expand...
Click to collapse
Your Rom is Amazing btw.
Successful
Im instal successful note 7 rom for note 4P
But im new member, i cant post my youtube chanel
youtu.be/ODPbW6S5yEU
Look more there
duc501613 said:
Im instal successful note 7 rom for note 4P
But im new member, i cant post my youtube chanel
youtu.be/ODPbW6S5yEU
Look more there
Click to expand...
Click to collapse
Would be a great daily ROM once 3g or 4g works!?
Sent from my SM-N910P using XDA-Developers mobile app
jglm4u said:
Would be a great daily ROM once 3g or 4g works!
Sent from my SM-N910P using XDA-Developers mobile app
Click to expand...
Click to collapse
3G working, vietnam haven't 4G yet
I wanted to start a thread in the AT&T forum for everyone to share there successes and workarounds after rooting with Samfail. I know there is a thread for the root process here https://forum.xda-developers.com/galaxy-note-8/development/root-samfail-galaxy-note8-t3685340 But i wanted this to be a place where we can share also what works for the AT&T phones.
I just rooted tonight, so far all i have done is disable the AT&T bootup sound but going to /system/omc/ATT/res/media/audio/ui and renaming PowerOn.ogg to read PowerOn.ogg.bak
As i figure out more things I'll keep updating the op.
Please feel free to share any tweaks you may know.
dirtydodge said:
I wanted to start a thread in the AT&T forum for everyone to share there successes and workarounds after rooting with Samfail. I know there is a thread for the root process here https://forum.xda-developers.com/galaxy-note-8/development/root-samfail-galaxy-note8-t3685340 But i wanted this to be a place where we can share also what works for the AT&T phones.
I just rooted tonight, so far all i have done is disable the AT&T bootup sound but going to /system/omc/ATT/res/media/audio/ui and renaming PowerOn.ogg to read PowerOn.ogg.bak
As i figure out more things I'll keep updating the op.
Please feel free to share any tweaks you may know.
Click to expand...
Click to collapse
As I sure you've seen my complaining in the root thread -- My main issue is the inability to get full calling features
It is very weird from my perspective in that everything seems to provision properly. I can make WiFi Calls but if I turn Wifi off then try ot make a call the call Ends suddenly unless I turn Enhanced LTE services off. But the really weird thing is that I can make calls in the area near my work (it is a bit more remote than where live) and it does appear that the calls are being made VoLTE. So why would the network in one place allow the calls to go through but in another the calls suddenly end ??? I think the answer to this might be the clue to getting this issue fixed for AT&T users.
I know many of you don't need the full calling features but for me it is essential and I would go without root if I can't find a solution :crying::crying:
jcrompton said:
As I sure you've seen my complaining in the root thread -- My main issue is the inability to get full calling features
It is very weird from my perspective in that everything seems to provision properly. I can make WiFi Calls but if I turn Wifi off then try ot make a call the call Ends suddenly unless I turn Enhanced LTE services off. But the really weird thing is that I can make calls in the area near my work (it is a bit more remote than where live) and it does appear that the calls are being made VoLTE. So why would the network in one place allow the calls to go through but in another the calls suddenly end ??? I think the answer to this might be the clue to getting this issue fixed for AT&T users.
I know many of you don't need the full calling features but for me it is essential and I would go without root if I can't find a solution :crying::crying:
Click to expand...
Click to collapse
Yea i never video or WiFi call (ok maybe have yo WiFi call about 2 or 3 times a year) so losing those two things don't bother me. I've always turned off enhanced lte services since they introduced it simply because it drains more battery plus from what I've googled about it, it don't really pertain to anything i need. I am hopeful though that once people start to use this root method, we'll start to figuring out how to fix everything like normal.
I'm not really sure the purpose to use this root method, its not even really root to begin with. What are your plans with using this method? I mean there are a few fun things to do but not worth a unstable system and 80% battery.
timmy10shoes said:
I'm not really sure the purpose to use this root method, its not even really root to begin with. What are your plans with using this method?
Click to expand...
Click to collapse
Why do you say "it's not really root to begin with"? By doing this method you gain access to root files and to the heart of your phone. SuperSU installs and works, you are able to deodex, theme, modify all as you want if you know what your doing. Sure there are a few issues with it (battery limited to 80%, WiFi calling, and camera) but none of this will get fixed we work on finding out the issue, but root has always brought about some type of issue one way or another in locked bootloader devices. My plan with rooting my phone is to build my rom with the tweaks and mods that i like, run the ad blockers that i like, possibly install xposed (haven't used it in a while). One of the main purposes of root in my opinion is to make your phone the way you like it. I mean you can sit around and wait for someone to make the phone how they like it and then possibly share it with others or you can take the initiative to learn yourself. Not really root to begin with? It's root, just not how it used to be. I hope someone does figure out a different root method that don't render the battery to 80%, i wish i knew how to look for exploits (I'm currently trying to learn) but until then, this is what we have. What are your reasons for believing this is not a real root method?
timmy10shoes said:
I mean its not really root because they are using a modified system file, not finding a real working exploit. It is a leaked factory image and a leaked factory kernel that needs to go with it. The 80% isn't going away. Its built into the kernel with can't be touched or motified. But we can always dream
Click to expand...
Click to collapse
Well that's why I'm still hoping for a different root method they don't have to use leaked files. But i can say that this root method runs a lot smoother than the method we had to use in the S7. This method hasn't been out very long, but is say within the next few months we'll start seeing more development happening . Or at least i hope. I've just recently started making my own roms (i don't release them to anyone being as I'm still learning and can't give a lot of trouble shooting assistance) but it's fun for me to pass the time at work. (I have a real laid back job with nothing to do a lot of times lol)
I mean its not really root because they are using a modified system file, not finding a real working exploit. It is a leaked factory image and a leaked factory kernel that needs to go with it. The 80% isn't going away. Its built into the kernel with can't be touched or motified. But we can always dream
---------- Post added at 04:48 PM ---------- Previous post was at 04:44 PM ----------
I get the fun part of it, thats why I use unlocked devices to flash the good stuff.
timmy10shoes said:
I mean its not really root because they are using a modified system file, not finding a real working exploit. It is a leaked factory image and a leaked factory kernel that needs to go with it. The 80% isn't going away. Its built into the kernel with can't be touched or motified. But we can always dream
---------- Post added at 04:48 PM ---------- Previous post was at 04:44 PM ----------
I get the fun part of it, thats why I use unlocked devices to flash the good stuff.
Click to expand...
Click to collapse
I've thought about buying am unlocked device but have read conflicting posts about service and radio bands messing that are used here in the US so I've always shyed away from them.
I have developed a few roms myself for the Bionic and Razr. Its highly entertaining and I want it myself but there hasn't been true root since the note 3 I believe.
---------- Post added at 04:54 PM ---------- Previous post was at 04:53 PM ----------
dirtydodge said:
I've thought about buying am unlocked device but have read conflicting posts about service and radio bands messing that are used here in the US so I've always shyed away from them.
Click to expand...
Click to collapse
I use unactivated devices. There is a ton on trial and error so I don't use my daily driver for that.
Are there any ROM anywhere for the snapdragon? Also anyone know where the stock firmware is located or can be found? When you go back,is it like it never happened ?
Don_Pachuco said:
Are there any ROM anywhere for the snapdragon? Also anyone know where the stock firmware is located or can be found? When you go back,is it like it never happened ?
Click to expand...
Click to collapse
No roms yet (on AT&T at least that i know of). Not trying to be rude but do you even search, see attached picture. Literally 4 post down from this thread.
I did search, and the one thread that I found, says "link removed". Then further down, it has files for the S8+.
Don_Pachuco said:
I did search, and the one thread that I found, says "link removed". Then further down, it has files for the S8+.
Click to expand...
Click to collapse
https://forum.xda-developers.com/att-galaxy-note-8/how-to/n950u-odin-5-files-stock-firmware-t3715770
Help!!! Please help!!!!
This is my first time with odin or basically anything computer related i am stuck at 2nd step of samfail. can some one please tell me what to do. it says fail (auth) thank you in advance. I have already done step 1 and it failed just like the instructions say but now in step 2 it fails every time. I'm stuck please help!
truly in over my head hear
jforest3026 said:
This is my first time with odin or basically anything computer related i am stuck at 2nd step of samfail. can some one please tell me what to do. it says fail (auth) thank you in advance. I have already done step 1 and it failed just like the instructions say but now in step 2 it fails every time. I'm stuck please help!
truly in over my head hear
Click to expand...
Click to collapse
This is a thread for mods done after rooting, post questions about getting rooted in your root thread please.
https://forum.xda-developers.com/ga...nt/root-samfail-galaxy-note8-t3685340/page323
the %80 max battery issue
I've enjoyed a rooted Note 8(sm-n950u) Nougat7.1.1 for over a week via samFAIL method and am quite thankful to the samfail/pwned team for providing it.
The max battery issue is the only drawback as far as I've noticed so far. I have a nice and speedy phone that is devoid of bloating apps, and vendor/carrier garbage.
As far as the max battery issue, I've done some digging and haven't found a cure yet.
I've noticed a couple things.
in /efs/Battery and in /sys/class/power_supply/battery there is a file named batt_capacity_max that has something to do with the max battery limit which is obvious by name of course.
Notes:
1. You can not change the value in /sys/class/power_supply/battery/. You can edit and write the file without any error or sign of failure; But checking the file immediately afterwards, you'll find that the contents did not change.
2. You can change the file in /efs/Battery/, but the contents are reset upon reboot.
3. The file contains only a number.
In my case, batt_capacity_max contains the number 1000 regardless of the charged state. i.e. It is 1000 when the phone if charged to max, and it is 1000 when the phone is nearly drained.
I change the value to see if it has any effect, and it does.
I interpreted the 1000 as binary 8, and changed to number to 1010 (binary 10). Then I charged the phone only to find that I could not charge the phone past 17% eep! This wasn't a problem though as rebooting the phone or returning the file to its original value restored the function to normal(rooted normal, that is..max 80%).
I've also deleted the file, then charged the phone to find that there was no effect.
I then came across a slightly older xda thread charge to 100 snapdragon root(s8 sampwn)
The thread had a great number of contributors and provided a great deal of background info, but the method described therein has become obsolete or does not apply to the Note 8 i believe.
If anyone has discovered anything effective regarding the battery max limit, I hope they will contribute that info here, or at least link to an existing thread that I may have missed.
One thing I would like to understand is what processe(s) are being employed in this battery limit system. Is it merely a sub-function of the SafetyNet, or something else? I've filtered what I believe are the pertinent logs(dmesg and logcat) trying to find reference to batt_capacity_max but have come up empty.
I have't tinkered with this in a couple days, but I plan to get back to it tomorrow. Anyone has ideas or suggestions, please contribute. personally I don't really care wether I "fix" this issue as much as I am using this pursuit to glean a better understanding of the android/samsung subsystems relative to it. .. to fix it, of course, is ideal.
delete
Sorry if this is wrong place or way to post on here. I am wanting to root the on5 but it is a learning experience. No pc to use. Is there a apk that actually works. Tried kingroot it says device not supported
I have developer options on and the oem toggle on am I ok with that. If anyone has the time and patience and could walk me through how to get going please let me know. Thanks
Jdaddy1 said:
Sorry if this is wrong place or way to post on here. I am wanting to root the on5 but it is a learning experience. No pc to use. Is there a apk that actually works. Tried kingroot it says device not supported
I have developer options on and the oem toggle on am I ok with that. If anyone has the time and patience and could walk me through how to get going please let me know. Thanks
Click to expand...
Click to collapse
Guess I came to the wrong place for advicre
I'm curious too.
You're not the only one who would like to know, but this is an older ( & apparently not widely used) phone that hasn't been sold for a few years so you may not get any answers.
Yea It's was one of my old ones. Wanted to use it to learn. Any suggestions on a older phone that rooting would be simple.? Can a phone be rooted without a computer I've read so much that says either but doesn't sound like it would.
Jdaddy1 said:
Yea It's was one of my old ones. Wanted to use it to learn. Any suggestions on a older phone that rooting would be simple.? Can a phone be rooted without a computer I've read so much that says either but doesn't sound like it would.
Click to expand...
Click to collapse
Sorry for the late reply. It's my current phone & the storage issues are just getting to be ridiculous otherwise I wouldn't be interested in rooting because of the risk of bricking/voiding warranty etc; but I don't know anything else to do. I know that it's possible to root with an app, but it depends on finding a vulnerability that can be exploited with your specific phone. It's different for every phone. If you choose to install a custom ROM you should find one made for your phone too otherwise you're likely to have problems if you try it on a phone that you intend to actually use for calls/texts etc; I had an HTC droid Eris years ago & used a one-click root app & it worked without any problem that I could tell, but it was a phone I wasn't using as my daily driver too, so I wasn't worried about voiding the warranty/radios not working etc;. Cell & sometimes bluetooth & wifi radios not working are common issues with newer ROMs or especially if you choose a ROM not made for your phone. With the Eris I just installed the app, pressed the button & it rebooted, installed a custom recovery & booted into the OS. With the On5 either there isn't a known exploit or there's just nobody willing or able to look for one or both. They would have to still have the phone to be able to look for one. If you have a flea market near you maybe you could go there & see if there's a phone store that you could get an old cheap one you could practice on? I don't remember the app I used, but I'm pretty sure it came from the play store. It seems like I read somewhere that HTC phones were easier to root, but I'm not sure.