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?
Related
I had android 4.4 Omnirom on my phone earlier today and yesterday. Today there was an update for the nightly. I decided to download it and updated through the recovery as a normal update would've. However, after waiting for almost an hour for the android is upgrading prompt to go away, I figured it was stuck in a boot loop. Well it turns out it more than likely was so don't say I'm impatient :d. So I forced it to shut down and it rebooted, but it didn't get past the Omni logo for almost an hour as well. So I decided to downgrade to the previous nightly. That didn't fix anything. After that, I tried to restore to cm 10.2 but it wouldn't let me for some reason. So I figured I was screwed. I downloaded Odin and attempted to restore to the stock rom. Well, Odin failed. So I was literally desperate and out of nowhere decided to try to downgrade the kernel. I attempted a downgrade to AJK 4.9 mic swap and it worked. So I installed MIUI after that (I'm too lazy to try adb) and it loaded up fine. I was so happy that at least something worked. After that I noticed the back and search buttons were not functioning. I decided to restore to cm 10.2 and it worked. Everything SEEMS fine but I'm not too sure if everything is. Can anyone tell me if my process is correct? Or if I messed up everything
Thanks!
I had to wipe the caches after i flashed the nightly to get it to boot.
The CM nightlies didnt work for me either. Something about the build.prop in Omni calling my phone both the ATT and ST version of the phone. I did what you did. Flashed AJ 4.7 i had, rebooted the Recovery, and Nandroid restored.
I liked Omni and ill be back but that battery life right now Ugh. Good luck Entropy and Co!
My partner's S III recently developed a problem using the standard Samsung 4.3 OS, it kept halting in the the middle of an application and later started continuously rebooting. As the phone was as far as I was aware, out of warranty and someone suggested there could be a s/w issue, I decided to root the phone and install a custom 4.4.2 ROM (I initially went for the one of the cyanogenmod 4.4.2 ROMs), to see whether that would resolve the problem. Initially, the ROMs I tried all generated error messages and failed to install,until I tried the Revolutioniary S5 V2 ROM, which installed perfectly.
However, it states that iti is a 4.3, rather than 4.4.2 ROM. I ran the ROM for 5 days without any major issues, so decided to try the V3 ROM, as ir was stated that this was 4.4.2 in a number of articles.. Again the ROM installed really quickly and without a hitch. However, again the ROM said it was 4.3, and as soon as I tried to install applications (well it was the third install, Skype if I remember), and the phone turned itself off. Then it started continuously rebooting, which is what was happening before the V2 ROM was installed. managewd to stop this by removing and then putting back the battery, and managed to get the V2 ROM installed again. Ther are three questions:
1) Does anyone have any idea what the initial problem might have been?
2) Why did the V3 ROM actually cause the problem to reoccur?
3) Is there a genuine 4.4.2 release of the Revolutionary S5 ROM (which I am genuinely impressed by and happy with), and will it work with my phone? (specific model i9300)?
[email protected] said:
My partner's S III recently developed a problem using the standard Samsung 4.3 OS, it kept halting in the the middle of an application and later started continuously rebooting. As the phone was as far as I was aware, out of warranty and someone suggested there could be a s/w issue, I decided to root the phone and install a custom 4.4.2 ROM (I initially went for the one of the cyanogenmod 4.4.2 ROMs), to see whether that would resolve the problem. Initially, the ROMs I tried all generated error messages and failed to install,until I tried the Revolutioniary S5 V2 ROM, which installed perfectly.
However, it states that iti is a 4.3, rather than 4.4.2 ROM. I ran the ROM for 5 days without any major issues, so decided to try the V3 ROM, as ir was stated that this was 4.4.2 in a number of articles.. Again the ROM installed really quickly and without a hitch. However, again the ROM said it was 4.3, and as soon as I tried to install applications (well it was the third install, Skype if I remember), and the phone turned itself off. Then it started continuously rebooting, which is what was happening before the V2 ROM was installed. managewd to stop this by removing and then putting back the battery, and managed to get the V2 ROM installed again. Ther are three questions:
1) Does anyone have any idea what the initial problem might have been?
2) Why did the V3 ROM actually cause the problem to reoccur?
3) Is there a genuine 4.4.2 release of the Revolutionary S5 ROM (which I am genuinely impressed by and happy with), and will it work with my phone? (specific model i9300)?
Click to expand...
Click to collapse
1) Not doing a full wipe/ formating system cache data etc or not using the latest recovery or combination of both
2) Not doing a full wipe/ formating system cache data etc or not using the latest recovery or combination of both
3) No
Also I find if switching between 4.3 roms and 4.4 roms (which I do alot) it is good idea to backup internal sd card and to format it (not all the time just if phone becomes really slow or has random reboots)
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.
This seems to be a weird issue that I'm having, and I hope I'm not missing a step...
Anytime I install a custom rom past 4.1.2; I get no phone audio. I can load up web pages fine, SMS/MMS works to my knowledge, but there is no phone audio. I'll call my house phone, and it will ring the house phone, but I cannot hear myself through the other line. I've tried flashing radios/modems, different combination of ROMs and kernels, and the only way I'm able to keep an active phone, that is able to make phone calls, is to stick with a stock ROM.
My first thought is maybe it thinks it's an unlocked phone? And that's causing it to act up, but I've never had an issue like this before. Any help would be appreciated.
tricky_tee said:
This seems to be a weird issue that I'm having, and I hope I'm not missing a step...
Anytime I install a custom rom past 4.1.2; I get no phone audio. I can load up web pages fine, SMS/MMS works to my knowledge, but there is no phone audio. I'll call my house phone, and it will ring the house phone, but I cannot hear myself through the other line. I've tried flashing radios/modems, different combination of ROMs and kernels, and the only way I'm able to keep an active phone, that is able to make phone calls, is to stick with a stock ROM.
My first thought is maybe it thinks it's an unlocked phone? And that's causing it to act up, but I've never had an issue like this before. Any help would be appreciated.
Click to expand...
Click to collapse
I don't believe the kernal is problem
What is your specific device model?
What have you tried to flash exactly?
Who is your carrier?
Are you flashing clean with all wipes?
Are you letting rom settle?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
tricky_tee said:
This seems to be a weird issue that I'm having, and I hope I'm not missing a step...
Anytime I install a custom rom past 4.1.2; I get no phone audio. I can load up web pages fine, SMS/MMS works to my knowledge, but there is no phone audio. I'll call my house phone, and it will ring the house phone, but I cannot hear myself through the other line. I've tried flashing radios/modems, different combination of ROMs and kernels, and the only way I'm able to keep an active phone, that is able to make phone calls, is to stick with a stock ROM.
My first thought is maybe it thinks it's an unlocked phone? And that's causing it to act up, but I've never had an issue like this before. Any help would be appreciated.
Click to expand...
Click to collapse
After u answer captemos questions… let me ask u this. You say stock 4.1.2, do u mean you have actually odin'd the stock release from sammy?
Gil81 said:
After u answer captemos questions… let me ask u this. You say stock 4.1.2, do u mean you have actually odin'd the stock release from sammy?
Click to expand...
Click to collapse
Apologize for the delay - been busy at work. I guess I could've been clearer.
I am using the SGH-i717 on AT&T. By stock, I meant a Touchwiz-based rom (i.e., Padawan JB). I have no problems with making or receiving phone calls. Whenever I flash a ASOP-based rom, (i.e., LiquidSmooth, BeanStalk, etc.) I have intermittent phone issues. The phone issues I'm having is not having audio when making or receiving phone calls. I know that it is actually placing the call, but I cannot hear the person on the other end, nor can they hear me. Now if I go into network operators, and select an operator that I know isn't going to work (i.e, Verizon, or T-Mobile), and then use "Choose Automatically", sometimes that works for a little bit. However, that has been working less and less now.
My process of flashing includes flashing the rom of choice after a full wipe and reset (right now, it's LiquidSmooth 4.4), wiping the cache and dalvik a couple of times, installing Polluti0n's rom patch, wiping cache and dalvik a couple of times, then installing PA Stock 4.4 Gapp, and finishing the whole process by wiping cache and dalvik a few times more. This is all done through gimmeitorilltell's TWRP Recovery 2.8.0.0
As stated before; I have no issues with Touchwiz-Based roms. I can make and receive phone calls with no problems. Also, before I rooted the phone, i updated it through Kies; so I assume that would update it to the latest radio available. That would be my first suspect, but I'm having difficulty finding a flashable radio for the device.
There also might be a step I'm missing, since all my experience previously with rooting and flashing came on CDMA devices, so there was no issues with radios.
tricky_tee said:
Apologize for the delay - been busy at work. I guess I could've been clearer.
I am using the SGH-i717 on AT&T. By stock, I meant a Touchwiz-based rom (i.e., Padawan JB). I have no problems with making or receiving phone calls. Whenever I flash a ASOP-based rom, (i.e., LiquidSmooth, BeanStalk, etc.) I have intermittent phone issues. The phone issues I'm having is not having audio when making or receiving phone calls. I know that it is actually placing the call, but I cannot hear the person on the other end, nor can they hear me. Now if I go into network operators, and select an operator that I know isn't going to work (i.e, Verizon, or T-Mobile), and then use "Choose Automatically", sometimes that works for a little bit. However, that has been working less and less now.
My process of flashing includes flashing the rom of choice after a full wipe and reset (right now, it's LiquidSmooth 4.4), wiping the cache and dalvik a couple of times, installing Polluti0n's rom patch, wiping cache and dalvik a couple of times, then installing PA Stock 4.4 Gapp, and finishing the whole process by wiping cache and dalvik a few times more. This is all done through gimmeitorilltell's TWRP Recovery 2.8.0.0
As stated before; I have no issues with Touchwiz-Based roms. I can make and receive phone calls with no problems. Also, before I rooted the phone, i updated it through Kies; so I assume that would update it to the latest radio available. That would be my first suspect, but I'm having difficulty finding a flashable radio for the device.
There also might be a step I'm missing, since all my experience previously with rooting and flashing came on CDMA devices, so there was no issues with radios.
Click to expand...
Click to collapse
first off i would flash the rom like so.
1. Factory Data reset
2. Wipe Cache/Dalvik
3. Format System/Data
4. Install rom from Sdcard
5. Wipe Cache/Dalvik
6.Reboot device
7.boot back into recovery
8.Wipe Cache/Dalvik
9. Flash gapps
10.Wipe Cache/Dalvik
Check to see if all is well once the rom is flashed and only the rom. Seems like over kill but can help narrowing down the issue, but i do agree with you as kies being the culprit I never did use it let alone trust it to update the device. Odin would be a better choice and no need to update the device for the latest radio as we have flashable zips. Blazes ics modem is what I'm currently using and has been great, one last thing I'd recommend is to go here http://www.sammobile.com/firmwares/ and grab the JB update and flash it via odin if all else fails.
I experiencing a similar symptom. Intermittently, not one can her me no I can hear anyone. I'm currently on Slimkat 4.4.4 and I have to reboot in order to make the call. Never had this problem when on stock JB 4.1.2.
Can some one point me to how to downgrade to Stock 4.1.2. Thinking about going back, I need a reliable phone.
Upgrade Radio
You must get the best radio for your location:
http://forum.xda-developers.com/showthread.php?t=1693545
tricky_tee said:
Apologize for the delay - been busy at work. I guess I could've been clearer.
I am using the SGH-i717 on AT&T. By stock, I meant a Touchwiz-based rom (i.e., Padawan JB). I have no problems with making or receiving phone calls. Whenever I flash a ASOP-based rom, (i.e., LiquidSmooth, BeanStalk, etc.) I have intermittent phone issues. The phone issues I'm having is not having audio when making or receiving phone calls. I know that it is actually placing the call, but I cannot hear the person on the other end, nor can they hear me. Now if I go into network operators, and select an operator that I know isn't going to work (i.e, Verizon, or T-Mobile), and then use "Choose Automatically", sometimes that works for a little bit. However, that has been working less and less now.
My process of flashing includes flashing the rom of choice after a full wipe and reset (right now, it's LiquidSmooth 4.4), wiping the cache and dalvik a couple of times, installing Polluti0n's rom patch, wiping cache and dalvik a couple of times, then installing PA Stock 4.4 Gapp, and finishing the whole process by wiping cache and dalvik a few times more. This is all done through gimmeitorilltell's TWRP Recovery 2.8.0.0
As stated before; I have no issues with Touchwiz-Based roms. I can make and receive phone calls with no problems. Also, before I rooted the phone, i updated it through Kies; so I assume that would update it to the latest radio available. That would be my first suspect, but I'm having difficulty finding a flashable radio for the device.
There also might be a step I'm missing, since all my experience previously with rooting and flashing came on CDMA devices, so there was no issues with radios.
Click to expand...
Click to collapse
follow dzee advice for flashing...rock solid method..but i still would like to know if you were ever on stock unrooted jb 4.1.2
what version of android were you on when you rooted the device the first time.
---------- Post added at 06:19 PM ---------- Previous post was at 06:11 PM ----------
dodgy1 said:
I experiencing a similar symptom. Intermittently, not one can her me no I can hear anyone. I'm currently on Slimkat 4.4.4 and I have to reboot in order to make the call. Never had this problem when on stock JB 4.1.2.
Can some one point me to how to downgrade to Stock 4.1.2. Thinking about going back, I need a reliable phone.
Click to expand...
Click to collapse
follow the li.k above ur original post. dzee gives a li.k to sammobile. download the correct tar file and fladh via odin
Hello all...
First of all, I'm not very experienced at flashing roms.. HOWEVER, I've flashed several roms across multiple phones over the years and have yet to brick a phone.. so I am fairly familiar with recoveries, etc... But I've run into a "wall" and don't know what to do.... hopefully someone can shine some light to my issue.
My TMobile S5 is currently running Twisted Lollipop (v7?).. but I want to switch now to a CM based rom. I had PREVIOUSLY used a CM based rom (a nightly) dated back from June before I switched to Twisted. My phone is rooted.. and I am using TWRP recovery. However, NOW if I do a full on wipe... and try to flash a rom (so far only the latest nightlies).. it seems to do some partitioning stuff.. and then stops saying COMPLETE... I never get the typical "install" text you see when installing a rom in recovery.. If when it's finished.. when I click REBOOT.. TWRP asks me if I want to.. and warns NO OS is installed..
I was able to load a backup of a CM 12.1 based build from a June nightly I had.... but I get the same thing if I go thru the CM updater. I honestly haven't tried to flash anything else..
Am I missing or overlooking something.. I'm on the DOB1 firmware.
Thanks
aenielida