Related
I'm sure people were getting pretty tired of hearing about the radio issues when people flashed cyanogenmod (ie, LTE worked, but no SMS, MMS, or voice calls, odin didn't fix, the only solution was to factory restore from WITHIN a TW ROM). After waiting a while for things to calm down, I'm ready to try to install Cyanogenmod again but I am naturally hesitant.
Has this issued resolved itself? I'm running rooted and unlocked MC3 with CWM installed. I heard somewhere that flashing the MJ9 radio BEFORE Cyanogenmod 10.2 / 11 fixed the problem?
I would really appreciate any input or personal experience here!
As far as I know, the issue has not resolved itself. I tried flashing the newest CM 11 a couple of days ago (I think it was the nightly build on the 22nd), and I still had the funky radio issues. However, I tried this, and it fixed all the radio issues with CM 11 (and any other Android 4.4 ROMS - I'm running Slim ROM at the moment)... Here is my post from another thread.
Hey all, I got it working (the data/network connection that is), with a little effort. Here is what I did in sequence...
1) Reflash the ORIGINAL VRALJB image via ODIN. I used the one found here. You want to make sure you get the one that replaces EVERYTHING, i.e., NOT the alternative restore.
2) I set up my phone and used it normally for about four hours. (This may or may not be necessary, I'm not entirely sure. I also rebooted the phone about five times during that time frame.)
3) I unlocked and rooted the phone via the method outlined here. After that was done, I installed CWM 6.0.4.3 via TWRP (which the unlocking process installs).
4) I then installed CM 11 and the respective Google apps. (I first did a backup, then a factory reset, then cache wipe, then dalvik wipe. The next thing I did was install CM 11, then Gapps.)
5) Restart the phone and success!
Click to expand...
Click to collapse
The reason why I found out that this method would work, is that I tried installing CM 11 on my dad's phone. He has had a TW ROM (Beans build to be exact) since the phone came out. And he has been running the stock VRALJB radio. With that said, I figured I would try flashing the stock ODIN files to restore my phone back to the VRALJB. (I think I was running the MJ9 prior to this) That worked, and the SlimROM has been working perfectly ever since!
[Also, if you wanted to check out SlimROM, you can find a link to it here.]
Still looking for some more feedback from users! Anyone successfully flashed CM 10.2 / CM 11 from MC3 without problems / fixed the problems?
Longtime XDA'er here with a problem.
I was rooted on stock 4.1.2 for over a year but wanted to update to take advantage of newer features such as chromecast mirror on kitkat. I had a perfectly working phone until I tried flashing updates. I followed instructions and only flashed the MJ9 baseband on roms that tell me too, and even flashed ND7 baseband for other ports. I was able to install multiple variants of 4.4.2 with both twrp and philz recoveries with the same result. I can't get sms/mms to come in. What's weird is upon bootup I will get the same test message only once, then nothing. I even tried flashing agni kernel with no luck. The phone works great with the exception of text messaging. Calls work, GPS locks, and no issues with wifi. APN settings look fine (compared to my wife's note 2 which is identical model still on 4.1.2). I popped my sim into an LG lucid I had as a backup and the text's sitting in limbo start streaming in, so I know my sim isn't bad. I even made sure to disable hangouts with no luck. Even tried Go Sms Pro with same result. I have since decided to go to 4.3 and am having the same issue on those roms on the MJ9 baseband and MJ9 stock kernel.
I'm pulling my hair out because I can't figure this out and I'm a pretty smart fella, this just has me stumped.
Ideas anyone? I have been researching like mad and nothing I try seems to resolve.
Thanks in advance!
timber03 said:
Longtime XDA'er here with a problem.
I was rooted on stock 4.1.2 for over a year but wanted to update to take advantage of newer features such as chromecast mirror on kitkat. I had a perfectly working phone until I tried flashing updates. I followed instructions and only flashed the MJ9 baseband on roms that tell me too, and even flashed ND7 baseband for other ports. I was able to install multiple variants of 4.4.2 with both twrp and philz recoveries with the same result. I can't get sms/mms to come in. What's weird is upon bootup I will get the same test message only once, then nothing. I even tried flashing agni kernel with no luck. The phone works great with the exception of text messaging. Calls work, GPS locks, and no issues with wifi. APN settings look fine (compared to my wife's note 2 which is identical model still on 4.1.2). I popped my sim into an LG lucid I had as a backup and the text's sitting in limbo start streaming in, so I know my sim isn't bad. I even made sure to disable hangouts with no luck. Even tried Go Sms Pro with same result. I have since decided to go to 4.3 and am having the same issue on those roms on the MJ9 baseband and MJ9 stock kernel.
I'm pulling my hair out because I can't figure this out and I'm a pretty smart fella, this just has me stumped.
Ideas anyone? I have been researching like mad and nothing I try seems to resolve.
Thanks in advance!
Click to expand...
Click to collapse
Odin back to stock should fix this issue.
DreamFX said:
Odin back to stock should fix this issue.
Click to expand...
Click to collapse
flashing stock 4.1.2 via Odin does fix it, but when I try to upgrade to any rom from there I have same problem. Pretty much all of the roms 4.3+ specify flashing with MJ9 firmware, which I have done. I have tried 4 roms today and same problem every time.
So annoying, it's like I can't get higher than 4.1.2
timber03 said:
flashing stock 4.1.2 via Odin does fix it, but when I try to upgrade to any rom from there I have same problem. Pretty much all of the roms 4.3+ specify flashing with MJ9 firmware, which I have done. I have tried 4 roms today and same problem every time.
So annoying, it's like I can't get higher than 4.1.2
Click to expand...
Click to collapse
I'm really surprised I'm the only one having this issue. After much research and countless attempts, it seems the most I can do is run stock 4.1.2 rooted, and can apply the MJ9 firmware... but if I try to update to any rom 4.3 or above, my text messaging stops working, otherwise the ROM's work great and phone calls, 4G Data, Wifi, GPS, etc all work perfect... only the sms/mms doesn't.
If I run the stock, rooted 4.1.2, with MJ9 radio everything runs great, including sms/mms, so my feeling is that I need a rom that doesn't flash kernel, or baseband, but jsut system, data, etc... then I might have a shot but it's a long shot at this point. I have even tried beans build 26 which is 4.3 and have EXACTLY the same problem.
The only other thing I've noticed is I have hardware version I605.07 whereas most people it seems have I605.06 from what I've noticed while browsing similar threads.
got it working with no help from anyone... a lot of steps but worth it. Definitely not the normal path everyone has been posting.
timber03 said:
got it working with no help from anyone... a lot of steps but worth it. Definitely not the normal path everyone has been posting.
Click to expand...
Click to collapse
Timber any chance you would be ale to point me to the fix? This has been driving me nuts
sugarfunk said:
Timber any chance you would be ale to point me to the fix? This has been driving me nuts
Click to expand...
Click to collapse
Absolutely... I will type up instructions in the morning. As for driving you nuts I know exactly what you mean... I was pulling my hair out and almost gave up hope but I tried something and it worked. It involves using beans 26 rom and a combination of Twrp and Philz recoveries and backup/restores... if you are having this problem, the main problem is the flashing of the MJ9 firmware.
I'll clue you in tomorrow
sugarfunk said:
Timber any chance you would be ale to point me to the fix? This has been driving me nuts
Click to expand...
Click to collapse
as promised, here's the steps it took for me to get working... It may seem a little bit of a long process but almost 4 days now and no more issues, so I trust this process. It must be something different in my hardware versus other, and I'm assuming yours is like mine.
Let me know if you have any questions
Start with 4.1.2 stock rooted
1. Install latest TWRP Recovery v2.7
2. Backup EFS and Modem as separate backups to your external SD card
3. In Recovery, Wipe.. Advanced Wipe and wipe everything (including Internal Storage) except external SD and USB-TG partitions
The next set of steps is to ensure you have a clean base to work with...
4. Reboot to download mode and using Odin 3.07 flash stock 4.1.2 firmware
in Pit select Sch-i605-16gb.pit
in PDA, select the stock 4.1.2 MC3 firmware
make sure only the following checkboxes are selected: "Auto Reboot", "Re-Partition" and "F. Reset Time"
Hit Start, wait till process completes and boots into o/s. Then skip all wizard options to get to home screen.
5. Root phone using casual
I had no issues using version "NoYouVerizon-GalaxyNote2-CASUAL R515.jar"
6. After root is successful, boot to Recovery and install latest TWRP recovery again since you will have twrp v2.5 due to the root process
7. Repeat step #3 (3 times to make sure everything is wiped clean)
8. IMPORTANT as this is what seemingly fixed the sms issue for me: using twrp recovery, restore the EFS backup you took in step #2 (do not restore the modem)
9. Install Beans 26 rom (Alliance 4.3) which will now give you a proper MJ9 base and kernel to work with. Again, skip all wizard prompts after it loads just so you can get to home screen.
10. Boot into recovery and now backup the new 4.3 EFS and modem partitions to your external SD.
You are not actually going to need the modem backup for the next steps, but if you have a problem installing a rom,
you now have working MJ9 EFS and Modem partitions should you have a problem with any roms from this point forward
11. Repeat step 7 & 8 (restore only the EFS 4.3 partition)
12. Important.. Now install latest Philz recovery
13. Install 4.4.2 rom using Philz recovery
At step 13 is where I installed the Ditto Note 3 rom v5.2, and chose "do not wipe" during the aroma install process.
14. once installed allow it to reboot, if it hangs on samsung boot animation for more than 5 minutes do the following:
a) pull battery and boot into philz recovery, then wipe only the following: Data, Cache, and dalvik cache
b)Install Agni Kernel (PSN_AGNi_pureSTOCK-v4.2.5_I605_4.4.2_AROMA-signed.zip)
c)reboot and you should get the android wizard for the rom in 2 or 3 minutes
If you have a problem like I did with regards to the Camera not working in the new rom, dirty flash the rom again (do not do any wiping)
Then re-install Agni Kernel since the rom installs it's own, otherwise it will break wifi, at least it did on mine.
There are a few more fixes to get tethering, etc working but I can provide those steps if needed. It basically involves installing xposed framework and the moto-x module.
timber03 said:
as promised, here's the steps it took for me to get working... It may seem a little bit of a long process but almost 4 days now and no more issues, so I trust this process. It must be something different in my hardware versus other, and I'm assuming yours is like mine.
Let me know if you have any questions
Start with 4.1.2 stock rooted
1. Install latest TWRP Recovery v2.7
2. Backup EFS and Modem as separate backups to your external SD card
3. In Recovery, Wipe.. Advanced Wipe and wipe everything (including Internal Storage) except external SD and USB-TG partitions
The next set of steps is to ensure you have a clean base to work with...
4. Reboot to download mode and using Odin 3.07 flash stock 4.1.2 firmware
in Pit select Sch-i605-16gb.pit
in PDA, select the stock 4.1.2 MC3 firmware
make sure only the following checkboxes are selected: "Auto Reboot", "Re-Partition" and "F. Reset Time"
Hit Start, wait till process completes and boots into o/s. Then skip all wizard options to get to home screen.
5. Root phone using casual
I had no issues using version "NoYouVerizon-GalaxyNote2-CASUAL R515.jar"
6. After root is successful, boot to Recovery and install latest TWRP recovery again since you will have twrp v2.5 due to the root process
7. Repeat step #3 (3 times to make sure everything is wiped clean)
8. IMPORTANT as this is what seemingly fixed the sms issue for me: using twrp recovery, restore the EFS backup you took in step #2 (do not restore the modem)
9. Install Beans 26 rom (Alliance 4.3) which will now give you a proper MJ9 base and kernel to work with. Again, skip all wizard prompts after it loads just so you can get to home screen.
10. Boot into recovery and now backup the new 4.3 EFS and modem partitions to your external SD.
You are not actually going to need the modem backup for the next steps, but if you have a problem installing a rom,
you now have working MJ9 EFS and Modem partitions should you have a problem with any roms from this point forward
11. Repeat step 7 & 8 (restore only the EFS 4.3 partition)
12. Important.. Now install latest Philz recovery
13. Install 4.4.2 rom using Philz recovery
At step 13 is where I installed the Ditto Note 3 rom v5.2, and chose "do not wipe" during the aroma install process.
14. once installed allow it to reboot, if it hangs on samsung boot animation for more than 5 minutes do the following:
a) pull battery and boot into philz recovery, then wipe only the following: Data, Cache, and dalvik cache
b)Install Agni Kernel (PSN_AGNi_pureSTOCK-v4.2.5_I605_4.4.2_AROMA-signed.zip)
c)reboot and you should get the android wizard for the rom in 2 or 3 minutes
If you have a problem like I did with regards to the Camera not working in the new rom, dirty flash the rom again (do not do any wiping)
Then re-install Agni Kernel since the rom installs it's own, otherwise it will break wifi, at least it did on mine.
There are a few more fixes to get tethering, etc working but I can provide those steps if needed. It basically involves installing xposed framework and the moto-x module.
Click to expand...
Click to collapse
Whatever works for you. Glad your back up and running.
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:
I have just recently tried to install the official cm11 images for my g3. They worked fine. Then, when I installed gel x-posed settings and activated it, I would get said error. It would pop up again and again. This would lead me to reflash my ROM. Then, I do not know what happened, when I would flash a ROM, I would get the error from the start. I eventually fixed this error. But then, when I tried to upgrade the nightly, I got the error again. So I flashed the ROM again, and let it sit. After a little while of perfection, the error came back up!
Here's what I have tried:
-reflashing the boot.IMG (unzipped)
-clearing cache (recovery)
-clearing Sim tool cache/data (said they were non existent when trying)
-reflashing stock, then reflashing cm11
I really want cm11 on my g3, but with these issues, I don't know whether I can now.
Any help would be appreciated!
Sent from my Nexus 7 using XDA Free mobile app
CM Nightlies are working perfect for me with no errors. Here is the process I went through:
I am still using TWRP 2.8.0 which is the version I installed when I originally Bumped! my phone.
I downloaded CM and Gapps to root of my internal SD storage
I chose to Wipe in TWRP
I chose Advance Wipe
I picked every option except for Internal Storage and External SD Card/Storage
I then Wiped
Out of habit, I do this 3 times (don't ask why, I just do it from when I had older android devices)
I then go back to wipe main screen and slide to do the standard wipe, 3 times
Yes, this is probably overkill!
I then go to install in TWRP
I install CM, then I install gapps (using the gapps that are on this list: https://itvends.com/gapps/
Yes, the date of those gapps are a little older, but that is what worked for me per OP'S instructions
I went through setup of my phone, fixing APN, Setting WIFI to USA, signing into Google after first loading into Rom instead of signing into Google on first bootup. Did a reboot
Installed Xposed, and the modules needed, reboot
I never received any error
I have done 3 nightly updates so far, as of 11/30. I am sure 12/1 will be ready in an hour or so.
I always click on about phone, download said update and let the process do its thing automatically, walk away and the phone is ready to use
Still no errors whatsoever. In fact, this has been the first version of AOSP I have used for the G3 with 0 errors. It is perfect, for me - No issues.
Hope that helps.
mwest316 said:
CM Nightlies are working perfect for me with no errors. Here is the process I went through:
I am still using TWRP 2.8.0 which is the version I installed when I originally Bumped! my phone.
I downloaded CM and Gapps to root of my internal SD storage
I chose to Wipe in TWRP
I chose Advance Wipe
I picked every option except for Internal Storage and External SD Card/Storage
I then Wiped
Out of habit, I do this 3 times (don't ask why, I just do it from when I had older android devices)
I then go back to wipe main screen and slide to do the standard wipe, 3 times
Yes, this is probably overkill!
I then go to install in TWRP
I install CM, then I install gapps (using the gapps that are on this list:
Yes, the date of those gapps are a little older, but that is what worked for me per OP'S instructions
I went through setup of my phone, fixing APN, Setting WIFI to USA, signing into Google after first loading into Rom instead of signing into Google on first bootup. Did a reboot
Installed Xposed, and the modules needed, reboot
I never received any error
I have done 3 nightly updates so far, as of 11/30. I am sure 12/1 will be ready in an hour or so.
I always click on about phone, download said update and let the process do its thing automatically, walk away and the phone is ready to use
Still no errors whatsoever. In fact, this has been the first version of AOSP I have used for the G3 with 0 errors. It is perfect, for me - No issues.
Hope that helps.
Click to expand...
Click to collapse
I did everything exactly as you did, including the 3 wipes, also out of habit. I too however, get the same error with the latest nightly. It starts popping up as I try to add my Gmail account at the initial setup. Previously, the 'unofficial' builds did not do this to me. This is the only rom that does this, I have tried them all out. I have yet to try to flash a different gapps package to see if that makes a difference. Apparently I dont get the data issues with cm12, but get phone issues with cm11.
I'm a bit relieved to see I'm not the only one having this problem. Been updating every night to see if maybe it's fixed, but I still get the same error. Didn't happen on the first nightly I flashed, though. It lol seems to be happening at random for me. Sometimes I'll set my phone down for a couple hours, working perfectly fine. Then I pick it up to check something and I suddenly start getting that error. I've tried every "solution" I find and none of them work for me. Even thought it was an issue with reading my sim card because when I get the error, it shows that my sim card isn't being read. But I still get it when I take it out. A normal factory reset doesn't fix it either. I have to do a complete data format to remove the error.
I found a quick little fix where i make a backup earlier in the day and just restore it whenever I start getting the error, but it's still very annoying.
Same issue
Hey bros,
Same thing here. It's a baseband radio issue. Notice in settings under About Phone it says 'Baseband Version: Unknown'. Either TWRP is flashing over our baseband (not likely, calls and texts can be made before the error message attacks come), or CM11 has some issue on certain builds with reading our SIM cards. I think having an official 10B or 11C flashable baseband radio to install at the time of the ROM install will fix this problem. Waiting on CM to patch the code will take too long. Let me know if you find one of these basebands or can find out how to extract it (from file manager or somewhere?) as I have not been able to find this info on XDA or anywhere.
EDIT: I FIXED IT
I'm a new member, and XDA won't allow me to post links..... look in the OP for JasmineROM (all credit to author for posting this 11C modem and fabulous stock LG debloated ROM) under downloads, you'll find the 11C modem. Download it.
1. Place 11C modem.zip on external or internal, whichever you want. I prefer external.
In TWRP:
2. Backup, unless youre livin' life on the edge.
3. Wipe it all except for external (or internal, if you prefer to flash from your internal storage)
4. Add to Install zip que in order:
a) latest CM11 nightly
b) 11C modem found in JasmineROM OP of main thread
c) GAPPs of your choice (I like nano PA GAPPs, and just install whatever else i want after)
5. FLASH
6. profit
7. PHAP
I have heard the 10B radio works great too. holler back and post results between the 2 stock radios for VS985.
Please hit thanks, as I am new and want to be helpful, where possible. Please share this so others know that we can overcome this nonsense.
CM11!!! Phappin' so hard right now!
Got it again.... totally blowed right now. maybe reconfig APN to match VZW and it will work?
Thanks for all the responses, it currently seems that the problem is cm11. I will probably wait for a stable build. For now, I'm using an unofficial cm12 ROM. Thanks for all the help!
Sent from my LG-VS985 using XDA Free mobile app
8pscott said:
Thanks for all the responses, it currently seems that the problem is cm11. I will probably wait for a stable build. For now, I'm using an unofficial cm12 ROM. Thanks for all the help!
Sent from my LG-VS985 using XDA Free mobile app
Click to expand...
Click to collapse
Are you using that PA GAPPs package that's in alpha? I think i'm going to give up and go to 12 too... I do know that the first official nightly of CM11 doesn't give me any errors, but Trebuchet is so buggy it won't take widgets. Had to download Nova
It makes me cry. My phone lasted through the night. Woke up at around 7 and it was fine. Went back to sleep and woke up at around 8:30 and I was crushed to see the problem happening again. There doesn't seem to actually be anything thy triggers it. :/
Yeah I think I'm gonna just try out cm12 and see how that goes.
Double check to make sure the phone isn't running in art. That fixed my problems! Xposed and art do not work together!![emoji2]
Im getting the same error on my phone usually a few says after using any of the nightlies. When i go to make a phone call it gives me the force close and doesnt stop. Ive since moved back to stock hoping someone had more info on the issue. My phone was not using Art but I did have xposed installed.
LineageOS Android Distribution 14
Lineage OS Android Distribution is the continuation of the now discontinued CyanogenMod.
Instructions1. Make a Nandroid backup using TWRP or similar custom recovery if flashing from a different ROM.
2. Download the latest LineageOS ROM (uploading) and copy it to either the internal storage, an SD card, or an OTG usb drive.
3. Download a Nougat (7.1) Google Apps Package (GApps) for ARM devices if desired (OpenGApps recommended).
4. Boot into the custom recovery to flash the ROM and/or GApps .
5. Factory reset if flashing from a different ROM.
XDA:DevDB Information
Unofficial LineageOS, ROM for the Sprint HTC EVO 4G LTE
Contributors
Source Code: https://github.com/LineageOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: HBOOT 2.10.0000 or 2.10.5555
Version Information
Status: Testing
Current Beta Version: lineage-14.1-20170302
Beta Release Date: 2017-03-02
Created 2017-01-22
Last Updated 2017-03-02
I'm going find this phone in one of the shoe box and install this thank you kind sir
Wow Los has finally arrived for the Jewel but my Jewel is no longer with me
I can't seems to use external sdcard as internal there's simply no option to do it while formatting. Other then this it's pretty snappy thanks again.
mecha2012 said:
I can't seems to use external sdcard as internal there's simply no option to do it while formatting. Other then this it's pretty snappy thanks again.
Click to expand...
Click to collapse
Thanks for testing! Try the new Nougat build—I wasn't able to move apps onto the SD card (that is a LineageOS bug), but I was able to format it as internal storage.
I couldn't install the latest build 14.1 well just keeps bootlooping at the HTC screen.
Wipe
Install latest build
Install Gapps 7.1 (tried without installing this also) still no go ?
mecha2012 said:
I couldn't install the latest build 14.1 well just keeps bootlooping at the HTC screen.
Wipe
Install latest build
Install Gapps 7.1 (tried without installing this also) still no go
Click to expand...
Click to collapse
There appears to be an error in the build. I will upload a new build within a day.
Edit: New build has been uploaded! Please report if it works.
Never thought my Jewel would ever see Nougat (let alone Lollipop or Marshmallow). Just flashed and all is working well so far. Awesome work!
God tier work here, I'm blown away. I misplaced my Moto G 3rd gen somewhere in my apartment, so I've given up and dusted off my Evo. I was set to just use the Viper 4.1.1 that was on there, but some apps weren't installing so I came on ol' XDA. This is much more than I expected, thank you.
With that said, any tips on getting this to activate on Sprint / Ting? It was working fine on the old rom, but not kicking in here.
I know this isn't totally related to this ROM, but maybe it can be. I'm having issue with this (and most other ROMs I try) where the per button works physically, but only the buttons light up. I have to press the power button several times to get the screen to wake. This isn't consistent though. Seems worse if the screen has been off for a while. Does anyone know of a fix, and if so, can it be incorporated into this ROM? I know there have other threads about this but it seems like they have been dropped.
idumych said:
God tier work here, I'm blown away. I misplaced my Moto G 3rd gen somewhere in my apartment, so I've given up and dusted off my Evo. I was set to just use the Viper 4.1.1 that was on there, but some apps weren't installing so I came on ol' XDA. This is much more than I expected, thank you.
With that said, any tips on getting this to activate on Sprint / Ting? It was working fine on the old rom, but not kicking in here.
Click to expand...
Click to collapse
I believe that the service must be activated on a stock ROM before flashing a custom ROM. Then, the correct APN has to be set according to the carrier under Settings > More > Cellular networks > Access Point Names.
Schiben said:
I know this isn't totally related to this ROM, but maybe it can be. I'm having issue with this (and most other ROMs I try) where the per button works physically, but only the buttons light up. I have to press the power button several times to get the screen to wake. This isn't consistent though. Seems worse if the screen has been off for a while. Does anyone know of a fix, and if so, can it be incorporated into this ROM? I know there have other threads about this but it seems like they have been dropped.
Click to expand...
Click to collapse
I am not sure of a fix, and I have not encountered this issue, but have you tried enabling Wake device using the Camera button under Settings > Buttons?
VitaTaf said:
I am not sure of a fix, and I have not encountered this issue, but have you tried enabling Wake device using the Camera button under Settings > Buttons?
Click to expand...
Click to collapse
I've tried that in the past. Forgot about it this time around. Tried it again and it seems to be about the same as the actual power button for getting the screen to come on correctly.
Good ol' Jewel. Is this rom working ok?
My wife is temporarily using my old Jewel because she dropped & broke her crappy samsung phone. can someone please tell me how this rom is working?
I appreciate your time!
King of the Couch said:
My wife is temporarily using my old Jewel because she dropped & broke her crappy samsung phone. can someone please tell me how this rom is working?
I appreciate your time!
Click to expand...
Click to collapse
The ROM is working fine for the most part. The battery is not great, but that may be due to the battery's age. Additionally, there is a bug with BoringSSL that sometimes prevents the Play Store or Gmail from working temporarily.
sounds good. yeah, I'm sure it's age. thanks man. take care-
Trouble with WiFi
Did a Full factory reset, installed rom, gapps, and supersu from TWRP, factory wipe again from TWRP; now the OS is installed and running but after connecting to my home network, says no internet access although the netork is up and running normally, all other devices connected. Any thoughts or suggestions. I have a backup of my previous state, so I can revert, but would like to keep this on 7.1 for consistency between this and my primary device. The primary use for this device is media streaming.
keysneptune said:
Did a Full factory reset, installed rom, gapps, and supersu from TWRP, factory wipe again from TWRP; now the OS is installed and running but after connecting to my home network, says no internet access although the netork is up and running normally, all other devices connected. Any thoughts or suggestions. I have a backup of my previous state, so I can revert, but would like to keep this on 7.1 for consistency between this and my primary device. The primary use for this device is media streaming.
Click to expand...
Click to collapse
I believe that the WiFi issue have been fixed in the latest build (20170522).
Thank you for this rom!
I had been using cyanogenmod 5.0 and dirtyunicorns 5.1 both were solid roms. Unfortunately the latest apps seem to run a bit slow on them. I thought it was the device but after installing this rom everything is snappy! It manages 1gig of ram better than any other rom and that 1.5ghz dualcore still runs strong. Snapchat is way more responsive on this rom, instagram and fb run without problems. GPS, 4g, sms, wifi, camera, sd storage, everything works! I've only noticed a few bugs. The wifi activity arrows don't show when something is downloading/uploading but wifi itself does work. Also, even tho I have working active cell service, it tries to activate itself again everytime I reboot and fails but calls-sms-data continue to work lol. The biggest bug is that auto-rotation stops working after 30-60 minutes and it stays stuck on portrait mode. Nothing but a full reboot will get it working again, a quick softboot won't fix it. I've tried changing the rotation settings and also added some lines to the build.prop but no solution thus far. I love this rom so much, if it's not fixed I might try some auto rotation apps. One last thing, it would be cool if the # in the status bar would go away after I close whatever app has root. The previous rom I had did that. Thank you so much to all the developers for bringing life to this phone!
familyjewels said:
I had been using cyanogenmod 5.0 and dirtyunicorns 5.1 both were solid roms. Unfortunately the latest apps seem to run a bit slow on them. I thought it was the device but after installing this rom everything is snappy! It manages 1gig of ram better than any other rom and that 1.5ghz dualcore still runs strong. Snapchat is way more responsive on this rom, instagram and fb run without problems. GPS, 4g, sms, wifi, camera, sd storage, everything works! I've only noticed a few bugs. The wifi activity arrows don't show when something is downloading/uploading but wifi itself does work. Also, even tho I have working active cell service, it tries to activate itself again everytime I reboot and fails but calls-sms-data continue to work lol. The biggest bug is that auto-rotation stops working after 30-60 minutes and it stays stuck on portrait mode. Nothing but a full reboot will get it working again, a quick softboot won't fix it. I've tried changing the rotation settings and also added some lines to the build.prop but no solution thus far. I love this rom so much, if it's not fixed I might try some auto rotation apps. One last thing, it would be cool if the # in the status bar would go away after I close whatever app has root. The previous rom I had did that. Thank you so much to all the developers for bringing life to this phone!
Click to expand...
Click to collapse
Thanks for trying out the ROM! The WiFi activity arrows are intentionally disable on LineageOS. I do not currently have an active cell service on this device, so I am unable to fix the activation bug for now. Could you flash the patch below in recovery and test if autorotation is working properly? It should also enable the option to hide the Superuser icon under "Status bar" > "System icons".