Related
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Heatshiver said:
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Click to expand...
Click to collapse
Thank you, Heatshiver!
I always do a full wipe unless I'm doing a dirty flash for a ROM update. I will try reverting back to TWRP 2.5.0.2 (Whichever version that happens to be, I think it's .0.2) tonight and report my results. Also, just to clarify, I always make sure I have the most updated SuperSU/Superuser (Usually the former) and BusyBox.
I appreciate the suggestion.
-Travis
teemunknee said:
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
Click to expand...
Click to collapse
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
As much as I love AOSP, I would have to agree with the poster above. I know TW is a pain but there are some pretty good ROMs in that flavor that you shouldn't have any problems with. I've had the no call issue on AOSP, and even though they are nice and free up quite a bit of room it's not worth missing calls over or constantly flashing. Maybe once our bootloader is unlocked things will become different but I'd stick with TW until that happens. I can confirm that TWRP 2.6 is very buggy...you'll have to download the 2.5 version and flash it instead of goomanager they install they latest version everytime I believe.
andybones said:
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
Click to expand...
Click to collapse
Next time, I'll just say "Soft-bricked". Thank you for your reply.
-Travis
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
slim6596 said:
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
Click to expand...
Click to collapse
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
I also forgot to mention that I haven't been able to connect to 4G radios since before I started having issues with AOSP ROMs. Currently I'm on Eclipse's TW (With AOSP Styling) ROM. Everything appears to be working fine, other than 4G.
I've tried the SIM pull and reset, and nothing. I've tried manually setting it to LTE only, at least when I was able to do so when AOSP ROMs would boot for me, and nothing. I have a Galaxy Nexus that I booted up with this SIM in and I get 4G signal. Any Ideas?
Also, when I was on the stock image (MDK) I didn't have 4G either.
Has anyone else run across this issue? (MODS: Let a me know if I should create another thread, or search more intensively. I haven't seen a thread with this exact same situation. Plenty of 4G issue threads, but none with the same issues I've previously had, and I think it may have something to do with my past modding.)
-Travis
teemunknee said:
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
Click to expand...
Click to collapse
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks! I installed CWM 6.0.3.6 Touch and flashed Eclipse's TW/AOSP ROM and everything works well, but it's still no AOSP ROM.
-Travis
Hi all,
I'd like to thank everyone for the suggestions.
An update: Currently I'm on Eclipse's TW v2.0 ROM (TW, with AOSP Styling) and everything works properly. My current recovery is CWM 6.0.3.6 Touch, and I'm not experiencing any booting or calling issues. 4G is the only thing I don't have working.
I'm hoping that someone with my same problem can give me another idea so I can get an AOSP ROM working, preferably with 4G. I'm sure some, if not most, understand my dislike of TouchWiz and strong preference towards stock Android/stock Android based ROMs. Slim6596 said that he uses Philz Modded CWM Recovery and has no issues anymore. Could that really be my solution?
Again, thank you all for your help and ideas. I love XDA for this reason.
-Travis
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
teemunknee said:
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
Click to expand...
Click to collapse
Loki patched, I believe.
Sent from my SCH-I545
slim6596 said:
Loki patched, I believe.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I have stuck to TW ROMs. Pretty soon I'm probably not going to be flashing anything. Switching to Motorola and giving Vz my MDK S4 back. (Reception and dropped call issues.)
Sent from my SCH-I545 using Tapatalk 2
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
egore93 said:
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
teemunknee said:
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
Click to expand...
Click to collapse
Yes that's it give it a go.
Sent from my SCH-I545 using Tapatalk 4
CM11 is great, but the libraries it's got appears to be heavily targeted toward CDMA mode and less so GSM. If you're a traveler or want to use your device with AT&T/T-Mobile, you'll want to install this patch which loads the AT&T ril onto your device. Without it, I couldn't receive any incoming calls and calls I placed couldn't be hung up (I would be stuck at the "hanging up" screen).
This patch is just two files (libril-qc-qmi-1.so and libril.so) pulled from the AT&T version (jflteatt) of CM11 (specifically, this version: https://download.cyanogenmod.org/get/jenkins/53825/cm-11-20140104-SNAPSHOT-M2-jflteatt.zip).
I'm overseas right now, so I'm only able to test GSM mode, but it's working just fine for me now. If it's not enough for you, you might want to try the two other changes suggested here: https://jira.cyanogenmod.org/browse/CYAN-2362
To summarize, they are:
Set telephony.lteOnCdmaDevice=0 in /system/build.prop
loki_flash the jflteatt CWM with jfltevzw aboot - see here. Note that this is specific to MDK, so don't do this if you're on any other bootloader. Let me know if you want me to create a flashable version of this possible fix.
I didn't need to do either of these things to get it working for me, but you may need to do the first item if you want LTE (I'm currently in a country without LTE, so I can't test).
Flash this for GSM-optimized rils: View attachment jfltevzw-gsm-0.2.zip
Flash this to revert to CDMA-optimized rils: View attachment jfltevzw-cdma-0.2.zip
Are these the updated files?
linuxthinker said:
CM11 is great, but the libraries it's got appears to be heavily targeted toward CDMA mode and less so GSM. If you're a traveler or want to use your device with AT&T/T-Mobile, you'll want to install this patch which loads the AT&T ril onto your device. Without it, I couldn't receive any incoming calls and calls I placed couldn't be hung up (I would be stuck at the "hanging up" screen).
This patch is just two files (libril-qc-qmi-1.so and libril.so) pulled from the AT&T version (jflteatt) of CM11 (specifically, this version: https://download.cyanogenmod.org/get/jenkins/53825/cm-11-20140104-SNAPSHOT-M2-jflteatt.zip).
I'm overseas right now, so I'm only able to test GSM mode, but it's working just fine for me now. If it's not enough for you, you might want to try the two other changes suggested here: https://jira.cyanogenmod.org/browse/CYAN-2362
To summarize, they are:
Set telephony.lteOnCdmaDevice=0 in /system/build.prop
loki_flash the jflteatt CWM with jfltevzw aboot - see here. Note that this is specific to MDK, so don't do this if you're on any other bootloader. Let me know if you want me to create a flashable version of this possible fix.
I didn't need to do either of these things to get it working for me, but you may need to do the first item if you want LTE (I'm currently in a country without LTE, so I can't test).
Flash this for GSM-optimized rils: (removed - broken)
Flash this to revert to CDMA-optimized rils: (removed - broken)
Click to expand...
Click to collapse
I see above that the flashable zip files were removed due to being broken. Are the ones attached good now? Also, these are AT&T files so will they work the same way with T-Mobile service since its fixing the issue with GSM and is not carrier specific?
If so, I'll give it a shot tonight. Thanks!
mbastats said:
I see above that the flashable zip files were removed due to being broken. Are the ones attached good now? Also, these are AT&T files so will they work the same way with T-Mobile service since its fixing the issue with GSM and is not carrier specific?
If so, I'll give it a shot tonight. Thanks!
Click to expand...
Click to collapse
No. Attached files are no-good; I've now removed them. I made a mistake in building the packages that'll likely brick your phone. I quickly removed the links while trying to fix my own device but forgot to remove the attachments. I'll repost when it's working properly.
linuxthinker said:
No. Attached files are no-good; I've now removed them. I made a mistake in building the packages that'll likely brick your phone. I quickly removed the links while trying to fix my own device but forgot to remove the attachments. I'll repost when it's working properly.
Click to expand...
Click to collapse
Glad I didn't trust the files! I noticed that someone else in the same cyanogenmod ticket thread recommended an update to a line as a fix. On my mobile, or I would post a link. Thanks for trying to find a fix though!
mbastats said:
Glad I didn't trust the files! I noticed that someone else in the same cyanogenmod ticket thread recommended an update to a line as a fix. On my mobile, or I would post a link. Thanks for trying to find a fix though!
Click to expand...
Click to collapse
I just tried the fix in the CM thread - stuck in a segfault loop
Now that I've unbricked myself, I've updated the zip packages and they should be usable now.
Lesson learned: mount partitions by name whenever possible! I'm lucky I didn't blow away anything that I couldn't recover from. I was just unlucky that it was a partition not normally included in odin reset tars.
Recap of how to
linuxthinker said:
I just tried the fix in the CM thread - stuck in a segfault loop
Now that I've unbricked myself, I've updated the zip packages and they should be usable now.
Lesson learned: mount partitions by name whenever possible! I'm lucky I didn't blow away anything that I couldn't recover from. I was just unlucky that it was a partition not normally included in odin reset tars.
Click to expand...
Click to collapse
So to recap how this is done, please correct me or agree.
If someone was installing CM 11 for the first time, they would:
1) Download the CM rom.
2) Download the GAPPS they prefer.
3) Download your 2 zip files for GSM ril provided in this thread.
4) Flash into recovery (assuming they had a custom recovery in place already)
5) Wipe data/cache/dalvik
6) Flash ROM, Gapps, and the 2 GSM ril zips you provided. (I prefer to flash Gapps after the first boot)
7) Reboot and watch it boot up.
8) Calls should work (assuming the correct apn settings are in place)
Agree?
mbastats said:
So to recap how this is done, please correct me or agree.
If someone was installing CM 11 for the first time, they would:
1) Download the CM rom.
2) Download the GAPPS they prefer.
3) Download your 2 zip files for GSM ril provided in this thread.
4) Flash into recovery (assuming they had a custom recovery in place already)
5) Wipe data/cache/dalvik
6) Flash ROM, Gapps, and the 2 GSM ril zips you provided. (I prefer to flash Gapps after the first boot)
7) Reboot and watch it boot up.
8) Calls should work (assuming the correct apn settings are in place)
Agree?
Click to expand...
Click to collapse
Almost!
(2) is optional and can be done later. There's no dependency here.
For (3), you only need the GSM flash package. The cdma package is provided if you want to revert.
For (4), a custom recovery is a given, since CM can't be flashed on the vzw s4 without it
For (6), flash only the GSM package.
For (8), calls should work even if APN settings are broken.
The two things to test for is:
1. After you've placed a call and are connected to the other party (i.e. the call timer starts ticking), you can successfully hang up.
2. You can receive an incoming call.
And to answer the carrier specificity question -- I'm testing this with Taiwan Mobile, so it's most definitely not carrier specific.
I guess this would have to be re-flashed after each nightly update that is applied?
canaanp said:
I guess this would have to be re-flashed after each nightly update that is applied?
Click to expand...
Click to collapse
I haven't worked with nightlies, but I suspect the answer is yes since nightlies are full images and not deltas.
Sent from my Nexus 7
I just tested with a fresh install of the 2/5 nightly. I wanna have your baby. Works perfectly, thank you!
It worked!
You have solved a problem that so many people were having. It works!!! Thank you for contributing. Now I'm going to spend time manually packaging a ROM with this and the apps and features I want.
Thank you!!!
Thank you. I'm using my Verizon s4 on T-Mobile and you saved me the trouble of doing this manually every time
Sent from my SGH-M919 using Tapatalk
With the latest comment on the linked Jira thread (and a correct APN), I think that I have an AT&T SIM working in my Verizon S4 without this mod. Does anyone else have this experience? (I should note that I flashed the GSM zip from OP three days ago, but I have since wiped, installed Hyperdrive ROM, wiped again, and reinstalled CM11 without flashing the GSM zip.)
noobnl said:
add this line to your cdma ril ro.telephony.ril.v3=newDriverCallU
Click to expand...
Click to collapse
To clarify, here's what I did:
1. Wipe data and cache.
2. Install latest CM11 nightly and gapps.
3. Boot and confirm that everything is working.
4. Add the letter "U" to the build.prop line that said "ro.telephony.ril.v3=newDriverCall" by default.
5. Reboot and confirm that Verizon LTE still works.
6. Power off, insert AT&T SIM, power on.
7. Choose LTE/WCDMA/GSM in Mobile Network settings and select a working APN.
8. Get H or H+ icon in signal bars and use speed test to confirm the blazing fast 0.10M down, 0.13M up.
9. Place call to my Verizon number, check voicemail, and hang up normally (I didn't get stuck at "hanging up").
10. Place test call from Skype to AT&T number, pick it up on the S4, and hang up from the S4 normally.
Thanks!
aindfan said:
With the latest comment on the linked Jira thread (and a correct APN), I think that I have an AT&T SIM working in my Verizon S4 without this mod. Does anyone else have this experience? (I should note that I flashed the GSM zip from OP three days ago, but I have since wiped, installed Hyperdrive ROM, wiped again, and reinstalled CM11 without flashing the GSM zip.)!
Click to expand...
Click to collapse
Are you running CM11 nightly or the snapshot?
FWIW, I tried "ro.telephony.ril.v3=newDriverCallU,newDialCode" from this post: http://forum.xda-developers.com/showpost.php?p=50036251&postcount=1591 and it caused a segfault loop on bootup.
Given all the issues getting CM11 working well, I'm probably going back to stock MDK 4.2.2; it's still less bug-prone than CM11 is
I'm using the CM11 nightly. I didn't add the part after the comma to the build.prop line.
I am very grateful for this! I searched and searched for days for a way to fix my dialer not letting me hang up a call after switching to Straight Talk AT&T. Now if I could only figure out how to get 4g LTE instead of just H+, I would do backflips! I appreciate your post immensely!
Sent from my SCH-I545 using Tapatalk
arlissnd said:
I am very grateful for this! I searched and searched for days for a way to fix my dialer not letting me hang up a call after switching to Straight Talk AT&T. Now if I could only figure out how to get 4g LTE instead of just H+, I would do backflips! I appreciate your post immensely!
Click to expand...
Click to collapse
Are you using the latest (MK2) radios? Those should get you LTE if AT&T has refarmed AWS LTE in your area.
I will try flash mk2 right now. Thanks. I'll report back ASAP.
Sent from my SCH-I545 using Tapatalk
arlissnd said:
I will try flash mk2 right now. Thanks. I'll report back ASAP.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
FWIW, I flashed the non-hlos + modem.
Did you use the vruemk2 or the other one? I just did that one, but it was not the non-hlos. I read that you should only flash the non-hlos modem that matches your boot loader. I'm on mdk boot loader.
Sent from my SCH-I545 using Tapatalk
Please, i despet to your help.
I own a G3 from Sprint.
I use it out of u.s (the seller of the phone got msl code).
Today i flashed the cloudy G3 rom and since then NO celluar networks.
Cannot even accsess it from settings...it not "clickable".
I need this phoone ... I have a memory problem.
Pleasr help me, please!!!
shabydog said:
Please, i despet to your help.
I own a G3 from Sprint.
I use it out of u.s (the seller of the phone got msl code).
Today i flashed the cloudy G3 rom and since then NO celluar networks.
Cannot even accsess it from settings...it not "clickable".
I need this phoone ... I have a memory problem.
Pleasr help me, please!!!
Click to expand...
Click to collapse
Cloudy g3 wasn't built to flash onto a sprint g3, nowhere in cloudy g3s post does it mention ls990 or sprint support.
Did you make a nandroid backup including the efs within it?
Hi.
I made just a backup from twrp.
But when i restore that i getting com.android popups...
This is the rom that i flashed:
http://forum.xda-developers.com/lg-g3/development/rom-cloudyg3-1-0-t2917467
shabydog said:
Hi.
I made just a backup from twrp.
But when i restore that i getting com.android popups...
This is the rom that i flashed:
http://forum.xda-developers.com/lg-g3/development/rom-cloudyg3-1-0-t2917467
Click to expand...
Click to collapse
I see,
Looks like ls990 support was just added.
It's buggy from the support section I see for it. You need to restore your nandroid backup of your stock firmware. Did you include efs in your backup?
I wouldn't install this rom again until it is confirmed sprint variant is functional. It's very common for developers to add cdma variant support and have signal issues because there is a lot to account for sometimes.
That is so su*@s...
I made a backup from TWRP.
But when a restore i get a com.android poos'ups.
Is ther anything to do in iin order to unlock it again?
I'm not at the states!
I feels so bad...wannnna cry.
If its anything like how it was on the G2 you have to edit the buildprop and change the carrier option to spr or SPR
hellot1M said:
If its anything like how it was on the G2 you have to edit the buildprop and change the carrier option to spr or SPR
Click to expand...
Click to collapse
I experimented with this and after editing the build proper it still didn't let me do mobile data or voice. I followed the guide to the T and it still had a red x. Not sure what voodoo you have to perform to make it work but in my opinion the rom is hardly sprint compatible if I have to go through all that to be able to make phone calls and have data(it's a phone, I mean c'mon).
Try flashing different modems. I don't see how that would be the issue but was also something I had to do to get cloudy to work. But in my case i had to use KitKat modem with Jb base to run the g3 ROM on my g2. It was a mess. I like cloudys Roms but they are always a pain in the ass to get working on anything but gsm. Also for some Roms we had to use a modified modem for a lot of Roms. Maybe that's the case here. We just need someone to modify our g3 modem to work with other roms
The g3 has had like 2-3 updates since its release. See if you can extract the modem from the different releases and see if you have better luck
OK so I had the same issue yesterday took about 5 hours to fix but don't worry it's fixable. So download another ROM I used Barrens (still using it actually very nice ROM). Try getting to the carrier folder (its root directory) and yes you will be having phone force closing constantly but you can get there, once there go in to apps subfolder. There you should find 2 files they go something like "node.db" and node-journal.db can't recall exact names but copy them and back them up to your SD card. Now go into recovery, go into wipe menu, then format system, cache, dalvik cache, and data. Just to be safe, I like doing a factory reset wipe after in recovery but it isn't necessary more of a habit. Flash the Barrens ROM. Set it up and you may still not be getting signals and have a no Sim icon. If so, go to the 2 files that you backed up and replace them with the ones that were auto generated after flashing ROM. Make sure permissions are set correctly. Then reboot. You should have signal back. O I forgot to add I also restored the efs backup I had made with the whole nandroid not sure if that was needed but that in itself wasn't enough to get rid of the force closes hence the procedure mentioned above.
This whole process needs to be done after you have restored your nandroid though I think as that is the only way to confirm that the files in the carrier/app folder are the original ones and not some new auto regenerated files. So work past the constant force closes. I'm also using my phone internationally and had it officially unlocked by Sprint then took it off the account so while for others who are still on Sprint, all they have to do is update their profile/prl in settings and it's painless and fast for them. We don't have that luxury however, at least don't have to overpay for crappy slow service from such a joke of a company though.
I'll attach the files that I have just in case yours got corrupted, use mine as a plan B option, as I'm not sure if mine will work on your specific device.
https://docs.google.com/file/d/0B10a_HcQL642ZTFTT0RJWk1HVHc/edit?usp=docslist_api
Sent from my LGLS990 using XDA Free mobile app
Just want to step in and say thanks to both you guys for helping this guy...I don't know him, but I do remember a time when the forums were flooded with this..this kind of heart. Not begging for thanks. Just the eagerness to help. Neither of you said anything negative. You just offered help. Your sig isnt begging a trade off for helping. For that I thank you. :thumbup::thumbup:
Sent from rotary technology Phone
This forum and other sites are blessed with people that blessed with a huge heart, pepole that see that as a mission - to HELP others without any willing to have someting from that, other than helping.
I also want to thank you for this goodness that we have here bc's of you.
:angel:
shabydog said:
This forum and other sites are blessed with people that blessed with a huge heart, pepole that see that as a mission - to HELP others without any willing to have someting from that, other than helping.
I also want to thank you for this goodness that we have here bc's of you.
:angel:
Click to expand...
Click to collapse
Just glad your up and running brother. Enjoy your G3. When you see someone stuck. Wade through the non attempt of help. if it's a legit issue through your help. Indeed. Good.
Sent from rotary technology Phone
Restore your backup or flash a sprint rom. Cloudy rom did the same to me I just restored my backup I was all good.
There's already a fix for this noted in this thread.
Solution
Hi Friend, I have ls990. I had the same problem, but I Could solve after install ROM CyanogenMod 12 BETA – LS990. Now, my LS990 is Unlock and I can use whit any carrier. Good Look!
ROM CyanogenMod 12 BETA(Android 5.0) – LS990: s.basketbuild.com/devs/jholtom/ls990/cm12
help guys i know you can
Sent from my SM-N900P using XDA Premium 4 mobile app
R1000 said:
help guys i know you can
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You will need to give a little more information to get some help.
Please include:
model of your phone
modem/baseband currently on your phone (settings, general,about phone)
firmware version (same location)
recovery installed (if you're currently rooted) or recovery attempting to use
root method being used
flashing steps taken
ROM or ROMs flashed
I know its a long list but it will go a long way towards getting the help you need.
Good luck
Note 3 sm900p lean kernel now I flashed Cm 11
Sent from my SM-N900P using XDA Premium 4 mobile app
R1000 said:
Note 3 sm900p lean kernel now I flashed Cm 11
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What exactly is your question? I don't actually see what you were trying to do and what went wrong.
One of the biggest problems that people have when trying to flash a 4.4.4-based ROM is that their bootloader is still based on NC5, not NH7. If you want to flash anything newer, you'll have to update your phone to NH7 before flashing a 4.4.4 ROM.
I put together this post when helping another person out on another thread. I think it'll work as a step-by-step guide for you:
I'll explain how to install a custom ROM and some common things to think about/check prior to installing anything:
Installing a Custom ROM
Step 1 - Gather Information
First off, you need to know what version of Android your phone currently is running. This is easily done by looking in the Settings Menu -> General -> About Device.
The Main things we are looking at on this screen are Software Version, Model Number, Android Version, and Baseband Version. I'll explain these (to the best of my knowledge) below:
Software Version:
This is the "type" of Android that you're running. Rather than quoting the entire name, we typically only refer to the last 3 characters (MJ4, NAB, NC5, etc.). Stock Note 3 devices will (most-likely) be running one of 3 different versions of TouchWiz (TW):
MJ4 - This is the last Jellybean version of TW for the Sprint Note 3NAB - This is the first KitKat TW version for the Sprint Note 3NC5 - This is the second KitKat TW version for the Sprint Note 3NH7 - This is the latest KitKat TW version for the Sprint Note 3
The reason that we are concerned with the Software Version is that between the MJ4 and NAB versions, there were major changes. So if you're running MJ4, you will have to do additional steps before flashing a custom ROM based on a newer version. And if you're on NAB or NC5, you will not be able to go back to MJ4, so beware what you're flashing.
For the most part, if you're on NH7, you can flash either a NH7 or NC5 custom ROM, but just read the ROM's FAQ to see if there are any issues with doing so.
Model Number:
Most people don't worry about this, but I always do when looking at a new ROM. The Sprint Note 3 is different from the Verizon Note 3, which is also different from the International Note 3. It's always best to double-check that the ROM you're trying to install is truly meant for your device. This simple check will prevent a LOT of potential issues you'll get when installing a ROM.
Android Version:
This is just an additional check to the Software Version. Always best to know.
Baseband Version:
The Baseband is, unless I'm mistaken, the "kernal" for the phone's cellular and 4G radios. Sometimes upgrading (or downgrading) the Baseband can help with signal strength and reception. Some users have noted that they got better reception on older Baseband versions. I haven't personally looked into it and the reports from other users seem somewhat anecdotal, but it's good to know which Baseband you're on.
The Baseband is independent from the ROM version, so you can run an older Baseband (MJ4 or NAB) on a newer ROM (NC5), and vice-versa.
The last bit of information you need to know is the Bootloader Version. The way to find this information is to reboot your device. When you see the text on the screen, you should look for the Bootloader Version. It'll be a long string of characters, but you're only looking for the last 3 (MJ4, NAB, or NC5).
Once you have all the above information, you should be ready to start the fun process of preparing your phone to flash your first ROM.
Step 2 - Backup your Media
First thing: Backup all of your media to your computer. If there's pictures/music/videos/recordings you don't want to lose, back them up. It's just good practice. Don't lose all your cat pictures because you flashed something and it somehow erased your internal storage. I tend to keep everything of importance on the External Storage, but there are times where even external storage can be wiped, so it's best to back up everything to a PC.
Step 3 - Upgrade your Phone to the latest Stock ROM (NH7)
This only is a MUST applies if you're running an older version and want to install a NH7 ROM. Most continually-developed ROMs are either NC5 or NH7 now, so the first things first: Update your phone to NH7.
Go over to micmar's thread and download the One-Click File. It will remove Root, but don't worry, because when you install a new ROM, it will automatically include root access.
Follow the instructions in his thread and your phone will now be fully upgraded.
At this point, your "About Device" should show the following:
Software Version: N900PVPUCNH7
Android Version: 4.4.4
Baseband Version: N900PVPUCNH7
Reboot your phone and let it sit for a minute so it can get it's bearings.
Step 4 - Install a Custom Recovery
So far, we've been flashing everything in ODIN. Now, we're going to use ODIN one last time to flash a custom recovery, so that you can flash custom ROMs without the need of a computer.
The most-commonly used Custom Recovery is TWRP (XDA Link). You'll want to use the latest version, 2.8.0.
Flash this in ODIN. You should use the "PDA" or the "AP" Slot.
Reboot your phone to make sure it works correctly.
Step 5 - Make a Nandroid Backup of your device
If you don't know what a Nandroid backup is, don't worry. It's basically just taking your phone as is and making a backup of it. In case you make a mistake or flash a bad download of a ROM, this allows you to restore your system. I always keep my backups on the External Storage (microSD Card), so in case I have to wipe my internal storage, it's not a big deal. You can also copy the files over to your PC, just to be more paranoind about your nandroid backups (rhyming is fun!).
You do this by restarting into Recovery (power down device, hold down home button and volume up while powering on phone).
Once in TWRP, go to "backup." Make sure the storage selected is "external storage." This screen will have various options of what to backup. I typically choose everything except external storage. Typically, backups range from 1-2 Gigs.
For me, backups typically take 5-10 minutes to do. In my opinion, this is totally worth it, since I can always restore a backup with no issues.
Step 6 - Install a Custom ROM
Once you choose your custom ROM from the Development Section, follow the instructions on the original post to install it. I'll give a general outline of what I do whenever installing a new ROM, but sometimes a custom ROM will have specific instructions, so you want to make sure to read the posts carefully.
Generic Instructions for Installing a ROM:
Download ROM and check the md5
Internet being spotty in my area, I always check the md5 to make sure that the file downloaded correctly. You can check the md5 using this windows program or using a file explorer on your phone like ES File Explorer. I always copy the ROM zip file to my external SDcard.
Reboot to Recovery
Wipe Data, System, Cache, and Dalvik Cache
This is called a "Clean Wipe," meaning it will wipe out your installed Apps and the data associated with them. Some people will claim that "Dirty Flashing" (i.e. not wiping the above) is OK, but I've seen too many apps Force Closing (FC-ing) when dirty flashing. Also, if you dirty-flash and encounter an issue with a ROM, the first piece of advice is to do a clean install. Might as well do that initially and hopefully not run into any issues.
Install the Custom ROM
Pretty straight-forward on how to do this... just click "Install" and then browse to the place your copied the ROM zip file.
Reboot your phone and run through the typical initial start-up information (google account, etc).
Once you get your phone set up the way you like (apps, accounts, wifi passwords, etc), I'd make another Nandroid backup, just so you have one where it's setup with everything you need. This will make any issues less painful, since you'd restore a backup that's already setup.
Step 7 - Further Considerations
If you ever want to try a new ROM, all you have to do is repeat step 6. Beware, though, people easily become flashaholics when they first figure this stuff out.
If you were paying attention to my "Generic Instructions" when installing a ROM, you'd notice that every time you do a Clean Install of a ROM, you lose all your apps... All of your Angry Birds 3-Star levels are gone!
Well, there are ways to get prevent losing that data... One is by "Dirty Flashing" (Not wiping the "system" or "data" partitions before flashing a ROM in TWRP). This is common practice among users here on XDA, but is typically frowned upon by ROM devs. I've noticed that a good number of issues on ROM threads stem from people Dirty Flashing. It typically causes more problems than it solves.
The other way of backup up and restoring app data (prior to wiping) is by using Titanium Backup. I could write up a long post on how to use Titanium Backup (TiBu), but the main things to remember are the following:
White line items are fine to be restored (both Data and Apps).
Restoring Yellow line items is typically OK (Data only).
Restoring system apps or data (red line items in TiBu) is typically a bad idea.
I've been using TiBu for the past 2-3 years and it's typically worked like a charm. Sometimes, when there's a major Android Update (like from JellyBean to KitKat), it can become broken, but the Developer is really responsive and gets it to work within a few weeks. If you upgrade to PRO, you can schedule automatic app backups (I backup all my user apps every night at 3am). You can also restore apps/data from Nandroid Backups (which is great if you do a Nandroid backup but had forgotten to update your TiBu backups).
In Summary
Whew, that was a lot to write... I'm a Structural Engineer, not a Software Engineer, so I don't know the technical side of things like bootloaders or basebands, but hopefully none of the information I provided was false.
Anyways, let me know if you have any problems with the install. I appreciate any feedback!
Click to expand...
Click to collapse
I hope this helps, but please, in the future, write out your question clearly and provide as much information as possible, that way we can help you quickly and efficiently.
Cheers!
-Topher
OK I noticed that thanks again I finally found a 4.4.4 Cm Rom working awesome very little glitch but can deal with I have no way to update without pc
Sent from my SM-N900P using XDA Premium 4 mobile app
Why does titanium backup not save from deletion says no external backup detected
Sent from my SM-N900P using XDA Premium 4 mobile app
No data sorry
Sent from my SM-N900P using XDA Premium 4 mobile app
Running pac man rom Cm no data
Sent from my SM-N900P using XDA Premium 4 mobile app
Thanks
Sent from my SM-N900P using XDA Premium 4 mobile app
R1000 said:
Running pac man rom Cm no data
Click to expand...
Click to collapse
Ok, you haven't fully answered the questions myself and @jdelano asked you. If you cannot answer these questions, we will be unable to help you.
Phone Model: Note 3 sm900p
Phone Modem/Baseband: Unanswered
Firmware version: Unanswered
Recovery installed: Unanswered
Root Method: Unanswered
Flashing Steps: Unanswered
ROM flashed: CM11, pac man rom (no build number/date given, please provide a link to the thread you flashed from)
Are you a Sprint Customer, or have you flashed your phone to another carrier?
What is the issue you're having: No data when on CM 4.4.4 ROMs.
I am in the process of downloading/installing the PacMan ROM in this thread. The file I will be flashing is the pac_hltespr__20141110-124721.zip and the Gapps modular package from this thread, filename: pa_gapps-modular-full-4.4.4-20141121-signed.zip.
EDIT: By following the steps in my previous post, I was able to install the PacMan ROM with Gapps and all worked well. I had data, root access, and was able to wifi tether... Please answer the questions I asked before, especially what version is your baseband, as I suspect that's the main issue that you have.
Nc5
Sent from my SM-N900P using XDA Premium 4 mobile app
Y'all packing works great little glitchy phone turns on an off but all good all Cm roms I end up with no data I have Phil's recovery beast kernal average gapps had to update su binary any time I flash cm and it changes my recovery sometimes I cannot format SD card or I will loose all files I have no PC even if I use drop box titanium doesn't work the way it use to can save apps from deleting with confirmation so what's a stable cm Rom or slim rom and gapps or do you have knew updated tw rom rooted I have update my boot loader so
Sent from my SM-N900P using XDA Premium 4 mobile app
R1000 said:
Nc5
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Phone Model: Note 3 sm900p
Phone Modem/Baseband: NC5
Firmware version: Unanswered
Recovery installed: Unanswered
Root Method: Unanswered
Flashing Steps: Unanswered
ROM flashed: CM11, pac man rom (no build number/date given, please provide a link to the thread you flashed from)
Are you a Sprint Customer, or have you flashed your phone to another carrier?
What is the issue you're having: No data when on CM 4.4.4 ROMs.
Click to expand...
Click to collapse
As I stated in my first reply to you, the issue is that your phone is still on the NC5 bootloader. In order for 4.4.4 ROMs to play nicely on your phone, you'll need to update it to NH7. This is also stated in my previous post. You need to follow those instructions to the letter (particularly Step 3) in order to update it. You must use a computer to flash the update file, as Mobile ODIN is not able to update the bootloader. You need to get access to a computer (work, library, friend who owes you $20, someone at Starbucks).
Until you follow those steps, I doubt any 4.4.4 ROM will work correctly on your device.
Exposed frame work not compatible with roms only tw anyone have zip for NH7 u date with root
Sent from my SM-N900P using XDA Premium 4 mobile app
R1000 said:
Exposed frame work not compatible with roms only tw anyone have zip for NH7 u date with root
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is the first you've mentioned XPosed Framework... What exactly are you trying to do with it?
I don't know where you've gotten your information from, but I know for a fact that XPosed is compatible with all 4.4.4 AOSP ROMs as well as all TW ROMs. XPosed is NOT compatible with 5.0+ Roms. I'm currently using it on my "daily-driver" ROM, which is based on 4.4.4 AOSP.
R1000 said:
Y'all packing works great little glitchy phone turns on an off but all good all Cm roms I end up with no data I have Phil's recovery beast kernal average gapps had to update su binary any time I flash cm and it changes my recovery sometimes I cannot format SD card or I will loose all files I have no PC even if I use drop box titanium doesn't work the way it use to can save apps from deleting with confirmation so what's a stable cm Rom or slim rom and gapps or do you have knew updated tw rom rooted I have update my boot loader so
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok, lets get you to a known platform with your phone so you can use 4.4.4 TW or AOSP ROMs.
#1. Load latest stock firmware and software
[Stock ROM] Odin flashable N900PSPTDNH7Follow the instructions EXACTLY
Now make sure you boot stock NH7, let it get data and update your profile and PRL by doing:
go to Settings -> General -> System Update, then select Update PRL (wait for it to do its thing), then Update Profile (again wait for it.)
Now we know you're on the most current stock software available and we've updated your profile and PRL (preferred roaming list)
#2. Root stock NH7 acquired in step #1
Go here Download philz_touch_6.48.4-hlte.tar.md5 (save it in the same folder you have Odin in from Step #1)Go Download SuperSU-v2.37.zipCopy the zip to your phone's sd cardUse Odin to put philz_touch_6.48.4-hlte.tar.md5 on your phone (same basic steps you used to Odin NH7) - Make sure you UNCHECK rebootOnce odin is finished and you see PASSED on the screen, unplug your phone from your computer then press Volume UP + HOME + POWER and hold all 3 until the phone reboots and you see blue words "Recovery Booting ..." at the top of the screen - Philz recovery will startnow select install zip -> choose zip from /sdcard -> scroll all the way to the bottom and select the SuperSU-v2.37.zip file -> select Yesonce finished press back until you get to the main recovery menu and select Reboot to System
#3. Update SuperSU binaries
Once your rebooted, Open Apps drawer, open SuperSU, say no to disable knox, it will ask about updating binaries, select yes, select normal, wait until it says its finished.Now you are Rooted Stock NH7You can now flash any 4.4.4 TW-NH7 or AOSP hltespr ROM - make sure to follow each Post #1 instructions on the ROM you choose and of course backup before flashing anything new
I hope this gets you to where you want to be, good luck.
Theres a lot of patience being displayed here. One should never start messing with their phone unless they have even the slightest clue what they are doing from the start
piaa_nissan said:
Theres a lot of patience being displayed here. One should never start messing with their phone unless they have even the slightest clue what they are doing from the start
Click to expand...
Click to collapse
The amount of patience I am seeing is mind blowing! To the OP...Just some words of advice. I have been a member of XDA for alot of years now and I can tell you that you will get a tremendous amount of help from this community. My only suggestions would be,when looking for help:
1) Be very clear as to the question you are asking.
2) If someone is willing to help you, Give them all of the information that they are asking you for.
3) Punctuation goes a very long way when someone is trying to understand what you are asking. Try using a period to avoid run on sentences.
Please do not take this as anything other then what I have learned over the years to get the best and quickest help!
I hope these guys are able to help you with your issues! :fingers-crossed:
Edit: They do keep coming!
I looked into doing it, and there is no way in hell that I should be a) doing it, and b) unleashing it onto the world. It would be bad.
I only have the one phone to test it on and can't risk messing it up and I don't have the experience to work on it if it didn't come out perfectly.
I expect that it will be the last Sprint ROM released for this phone, We're nearing the end of support, so it would be good to have these final versions "fixed" and available
...on the off chance a few developers will jump right in and cook up a few mega ROMs for us.
DQG1 Root and Xposed (rewritten)
On a related note, I installed stock DQA1 DQG1, using the usual CF Autoroot, battery pull thingy process Odin for the ROM and TWRP, then booting once, booting into recovery, and then installing SuperSU and it rooted fine. No loss of settings or anything else as far as I can tell.
I did have to install the latest versions of the Xposed files. After rooting and custom recovery (TWRP works fine), install XposedInstaller_3.1.4.apk first like any other apk, then go to recovery and install Wanam v87.1-alt-sdk23-arm-custom-build, but everything (Xprivacy, etc.) worked fine. Keep in mind, you HAVE to use the "alt" (see the "alt" in the file name above?) version or else it won't work. Samsung made some changes, blah, blah, blah. Much thanks to Wanam!
New side note: I did do a factory wipe, and even after reinstalling everything, and using a ROM that contains bloatware, I still have like 40% more space on the phone. I truly don't know what happened there.
Anyone have any thoughts as to kernel? I downloaded Emotion r26 RC1, and BeastModeKernel 1.0BETA, but I haven't tried them yet.
EDIT: Emotion r26 RC1 works fine, but it doesn't seem like CPU freqs are ever going to stick.
No surprise that neither Emotion nor BeastModeKernel worked; I haven't seen anything else that may.
Thoughts anyone?
Both kernels are good, emotion has a few more options to tweak but I took an update a month or two ago and run NotEdge ROM fine , I just use SO launcher with it because I like TW, also latest xposed is 86.1 and I wish I could do what your asking but it probably would be just as bad you'll be fine with that ROM I just suggested it has everything u just requested just make a nandroid and do it at home in case you do something wrong you can always ODIN back your firmware
Sent from my HTC One M9 using XDA-Developers mobile app
D'oh!!
Eating a little crow here. So far, there have been two three 742 updates, maybe there will be more. Who knows?
But I edited the title of the first post. Again. Again. 741 times.
Do you guys have a link to the stock unrooted rom? My phone is royally screwed right now and still stock. I want to do a clean flash and see if that fixes it.
Over a year later, and the still keep coming.
Hmmmm.
I did take another gander around, but it seems that I would need Linux to do it correctly, so I am still opting out of doing it myself.
mictek said:
Do you guys have a link to the stock unrooted rom? My phone is royally screwed right now and still stock. I want to do a clean flash and see if that fixes it.
Click to expand...
Click to collapse
They all arrive here: https://www.sammobile.com/firmwares/galaxy-note-edge/SM-N915P/ eventually.
Hello i got a note 4 Sprint MM 6.0.1 N910PVPU5DQI5 . i am from Argentina, and i bought the phone used from a guy from USA. (i don`t know how but it`s working with the bands here but i dont know if 4g is working, the guy says it works, maybe i don`t have 4g singal in my zone) .
the phone works fine, but has some srpint stuff and ads that bother me. so i flashed TWRP , and now i am looking for any roms and kernels to flash.
for example, is safe to flash this: https://forum.xda-developers.com/note-4-sprint/development/rom-updated-1-14-2017-t3538051
or should i change something first ???.