While trying to research RIL/baseband for CM13, I have tested virtually every ROM for n900v with various combinations of KK and LP modems.
So far, these are the only two that have worked for me...and I must say that the first works VERY well... tempted to use their sources to build out CM13.
1. Dirty Unicorns v9.8 (http://forum.xda-developers.com/galaxy-note-3/orig-development/rom-dirty-unicorns-v9-0-t3006601)
With the OF1 modem/non-hlos, DU 9.8 has working LTE right out of the box, and seems to be a very mature ROM.
2. LiquidSmooth 4.1 (http://forum.xda-developers.com/galaxy-note-3/development/rom-liquidsmooth-v4-0-lollipop-t3008474)
Liquidsmooth is the only other ROM I have been able to have establish reliable cellular and mobile data. Also using the OF1 modems, but LTE is NOT working reliably. Setting to 3G as preferred works fine and persists through reboots.
3. UPDATE: CM11 OFFICIAL works if you install and boot Dirty Unicorns first, then wipe and flash CM11.. **not working after further testing**
4. CM13...
http://forum.xda-developers.com/ver...opment/rom-temaseks-unofficial-build-t3364382
I have been on my own modded version of Temaseks CM13 for over a week and have had no issues whatsoever. Rock solid.
Anyone else have anything working?
Thats awesome thanks for sharing the information.
What does "non-hlos" mean? Dirty Unicorns looks pretty nice until a real CM rom comes out.
tomixnscale89 said:
What does "non-hlos" mean? Dirty Unicorns looks pretty nice until a real CM rom comes out. Is it based on LP?
Click to expand...
Click to collapse
It is a .bin file that is part of the radio
... Nothing you will need to worry about unless you have been flashing different ones already
If you ODINed OF1 to root/unlock, you should be all set to run this.
Yes, it is LP 5.1.1 and is very well put together. I am still trying to figure out why it runs so well... Looks like a combo of straight AOSP with cherry-picked CM12 features.
I flashed the OFI partial firmware back when I put Jasmine on my phone. Should that be enough?
tomixnscale89 said:
I flashed the OFI partial firmware back when I put Jasmine on my phone. Should that be enough?
Click to expand...
Click to collapse
No..you would need to be unlocked to install this which would have required an ODIN flash to OB6 or OF1
mightysween said:
No..you would need to be unlocked to install this which would have required an ODIN flash to OB6 or OF1
Click to expand...
Click to collapse
I am unlocked though with TWRP installed.
tomixnscale89 said:
I am unlocked though with TWRP installed.
Click to expand...
Click to collapse
Probably didn't need that partial firmware then. You must have flashed OF1 and rooted at some point, so yes it should be good to go.
if you wanna try, backup your current ROM first in TWRP!
mightysween said:
Probably didn't need that partial firmware then. You must have flashed OF1 and rooted at some point, so yes it should be good to go.
if you wanna try, backup your current ROM first in TWRP!
Click to expand...
Click to collapse
I was on 4.4.2 Kitkat with root and went to Jasmine 6.1.
Yup, already have a backup since I already tried CM 13 once with no success. :good: Thanks!
so right now i can wipe data/cache/dalivk and factory reset then install either of the above zips if im on OF1 BL-Unlocked?
grabbing http://download.dirtyunicorns.com/f...hltevzw_5.1.1_20151113-1513.v9.8-OFFICIAL.zip as i type this
which gapps?
Hmmm... you may still be on NC4 or NK1 modems. I am not sure how coming from 4.4.2 would work...and I didn't think unlock was even possible on 4.4.2 yet.
en11gma said:
so right now i can wipe data/cache/dalivk and factory reset then install either of the above zips if im on OF1 BL-Unlocked?
Click to expand...
Click to collapse
I have done just that with about 20 different ROMS already. So yeah
BTW every ROM has worked great except for the radios (no cell and/or 3g/LTE)
en11gma said:
so right now i can wipe data/cache/dalivk and factory reset then install either of the above zips if im on OF1 BL-Unlocked?
grabbing http://download.dirtyunicorns.com/f...hltevzw_5.1.1_20151113-1513.v9.8-OFFICIAL.zip as i type this
which gapps?
Click to expand...
Click to collapse
I use open gapps nano...but would imagine any 5.1 should work.
mightysween thank-you so much for doing all this testing.
that is so awesome as its been running through my head for about a solid 24hrs.
i was getting ready to do some more research and go get the best cm 12 out.
ill test on mine with the dirty unicorns 9.8
will report any issues with anything i notice
what about NFC and GPS.....Camera?
nfc i read you have to something more then just disable on some other thread. not sure if it pertains but i wouldnt be surprised
en11gma said:
mightysween thank-you so much for doing all this testing.
that is so awesome as its been running through my head for about a solid 24hrs.
i was getting ready to do some more research and go get the best cm 12 out.
ill test on mine with the dirty unicorns 9.8
will report any issues with anything i notice
what about NFC and GPS.....Camera?
nfc i read you have to something more then just disable on some other thread. not sure if it pertains but i wouldnt be surprised
Click to expand...
Click to collapse
GPS and camera seem fine, NFC doesn't appear to work...I know there were some workarounds for various ROMS
mightysween said:
GPS and camera seem fine, NFC doesn't appear to work...I know there were some workarounds for various ROMS
Click to expand...
Click to collapse
im pretty sure i read somewhere about nfc showing that it was off but really being on. there was a fix but i think it involved a zip or two
en11gma said:
im pretty sure i read somewhere about nfc showing that it was off but really being on. there was a fix but i think it involved a zip or two
Click to expand...
Click to collapse
Yeah...as far as this thread goes, mainly looking for working radios as that seems to be the stumbling block for hltevzw until we get CM13 running
mightysween said:
GPS and camera seem fine, NFC doesn't appear to work...I know there were some workarounds for various ROMS
Click to expand...
Click to collapse
mightysween said:
Yeah...as far as this thread goes, mainly looking for working radios as that seems to be the stumbling block for hltevzw until we get CM13 running
Click to expand...
Click to collapse
makes sense to me
It is worth noting that DU 9.8 is a dead project... so there aren't going to be any changes unless a new maintainers comes along
mightysween said:
While trying to research RIL/baseband for CM13, I have tested virtually every ROM for n900v with various combinations of KK and LP modems.
So far, these are the only two that have worked for me...and I must say that the first works VERY well... tempted to use their sources to build out CM13.
1. Dirty Unicorns v9.8 (http://forum.xda-developers.com/galaxy-note-3/orig-development/rom-dirty-unicorns-v9-0-t3006601)
With the OF1 modem/non-hlos, DU 9.8 has working LTE right out of the box, and seems to be a very mature ROM.
2. LiquidSmooth 4.1 (http://forum.xda-developers.com/galaxy-note-3/development/rom-liquidsmooth-v4-0-lollipop-t3008474)
Liquidsmooth is the only other ROM I have been able to have establish reliable cellular and mobile data. Also using the OF1 modems, but LTE is NOT working reliably. Setting to 3G as preferred works fine and persists through reboots.
Other than these two, every other ROM has major radio issues. All of the CM11 based stuff seems to connect LTE/3G just fine, but will not hold it...the radio constantly cycles. All of the CM13 stuff has radio connected at the base level, but needs some tweaks in order to make it available to the OS properly.
Anyone else have anything working?
Click to expand...
Click to collapse
Dirty Unicorns wouldn't pick up 4G LTE on Straight Talk (Verizon)
Only data working with Dirty Unicorns and that MVNO was 1G
Screen went blank while calling with speaker phone on and wouldn't come back on unless the power button
was pressed in constantly while I changed the display settings to only blank at 30 minutes.
Samsung SM-N900V OF1 rooted and then bootloader unlocked,
did not flash OF1 after the bootloader unlock and then straight to Dirty Unicorns latest version.
Related
I've been running AOSP 4.2 on my S4 for quite a while with no issues. Upon trying to upgrade to 4.3 though, boots take upwards of 5 minutes and the baseband isn't recognized (it literally shows "Baseband Version: Unknown"). I then tried to revert to one of the various 4.2 ROMs still out there, and am encountering quite a bit of general instability (lots of FCs), however, the baseband works fine. Any idea what is going on?
I should add that though I am using the ME7 modem, everything else is MDK and that these symptoms are pervasive through several different ROMs.
Update:
When trying to switch to RUIM/SIM in the Radio Settings, I get the following logcat:
Code:
/CdmaSubscriptionListPreference( 1762): Setting Cdma subscription source failed
I/Use2GOnlyCheckBoxPreference( 1762): get preferred network type, exception=com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE
have you gone into network settings and verified that your subscription is set to RUIM/SIM instead of NV?
Did you compile the AOSP yourself? What build are you using? Project Elite's baseband and network all work out of the box no problems. I'm not sure if they posted it yet though.
Dubbsy said:
have you gone into network settings and verified that your subscription is set to RUIM/SIM instead of NV?
Click to expand...
Click to collapse
Yes; Whenever I do that I get the logcat I mentioned above and the setting doesn't stick (ie it immediately changes back to NV).
Edit:
When I retried, I got:
Code:
E/CdmaSubscriptionListPreference( 1618): Setting Cdma subscription source failed
Dubbsy said:
Did you compile the AOSP yourself? What build are you using? Project Elite's baseband and network all work out of the box no problems. I'm not sure if they posted it yet though.
Click to expand...
Click to collapse
No; this is with several 4.3 based ROMs including CM and Pacman.
Edit 2:
I'm downloading the Darkslide ROM to try to get that baseband installed and will keep this thread up to date with the result.
murphycr said:
Yes; Whenever I do that I get the logcat I mentioned above and the setting doesn't stick (ie it immediately changes back to NV).
Edit:
When I retried, I got:
Code:
E/CdmaSubscriptionListPreference( 1618): Setting Cdma subscription source failed
No; this is with several 4.3 based ROMs including CM and Pacman.
Edit 2:
I'm downloading the Darkslide ROM to try to get that baseband installed and will keep this thread up to date with the result.
Click to expand...
Click to collapse
Oh you aren't running pure aosp. Gotcha.
I was able to hold subscription on PAC, Slim, and CM10.2
Did you edit anything prior to install? Was your phone's data working just before switching to 4.3?
Dubbsy said:
Oh you aren't running pure aosp. Gotcha.
I was able to hold subscription on PAC, Slim, and CM10.2
Did you edit anything prior to install? Was your phone's data working just before switching to 4.3?
Click to expand...
Click to collapse
Yes. It also works if I switch back to 4.2, but then other things break. Anyway, I'm about to flash the baseband you referred to, so I'll see where that gets me.
Thanks!
murphycr said:
Yes. It also works if I switch back to 4.2, but then other things break. Anyway, I'm about to flash the baseband you referred to, so I'll see where that gets me.
Thanks!
Click to expand...
Click to collapse
the baseband used in all 4.3 builds I've used was MDK.
Me7 baseband is not as good as some people like to claim. It is buggy, and in my opinion it was rushed to release because Verizon wanted to quick kick everyone in the nuts. I tried me7 a few times and everytime I had worse spottier service.
The project elite aosp I was talking about is actually full aosp. And I haven't seen a post for it yet.
Another thing I've noticed in general... What recovery are you using? I don't trust CWM(any variation) at all anymore. I've seen too many installs act up and just not work right at all with CWM and after trying it on twrp 2.5.0.2 the same exact installer worked fine. :silly: I don't know why, but regardless the layout of CWM is piss poor anyway. If you are using CWM, click the link in my sig to go to my GE build. In the second post I have flashable recoveries posted. You can try one out just to see and if you get the same results just flash back to your desired/current recovery:good:
I was having the same problem with my own cm10.2 builds. I blew out my device and vendor repos several times and finally decided that there had to be something in frameworks that doesn't like the dev edition radios. The nightlies wouldn't even work. I ultimately wound up using the official cwm (non-loki only) and was finally able to change from nv to ruim/sim.
Sent from my SCH-I545 Dev Edition using xda app-developers app
So you used the non-loki'd CWM to do what fixed it? (I presume simply having it installed didn't fix it automatically)
On the dev edition, the general consensus in the beginning was that philz touch(cwm based) was the recovery to use probably because he offered a non-loki version. We don't need loki fortunately because of our unlocked bootloader. I later found out that official cwm was also not lokified. If you have the retail version, unfortunately you are stuck with the loki recovery. I was just suggesting that you might try a different cwm since they are not all created equal.
Edit: I guess what I was really trying to say is just try another recovery. Not necessarily one over the other (cwm vs. twrp). It's not the non-loki part that will make the difference. Hopefully you'll find one that works for you. But who would have known that would cause it.
Sent from my SCH-I545 using xda app-developers app
OLD&SLOW said:
On the dev edition, the general consensus in the beginning was that philz touch(cwm based) was the recovery to use probably because he offered a non-loki version. We don't need loki fortunately because of our unlocked bootloader. I later found out that official cwm was also not lokified. If you have the retail version, unfortunately you are stuck with the loki recovery. I was just suggesting that you might try a different cwm since they are not all created equal.
Edit: I guess what I was really trying to say is just try another recovery. Not necessarily one over the other (cwm vs. twrp). It's not the non-loki part that will make the difference. Hopefully you'll find one that works for you. But who would have known that would cause it.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I've tried both TWRP and PhilZ. Neither seemed to do it. At this point I'm just going to do a full ODIN.
Thanks for all the help though!
No problem, I just hope you figure it out. There are too many people using aosp 4.3 roms with no problems for this to be impossible. :thumbup:
Sent from my SCH-I545 using xda app-developers app
murphycr said:
I've tried both TWRP and PhilZ. Neither seemed to do it. At this point I'm just going to do a full ODIN.
Thanks for all the help though!
Click to expand...
Click to collapse
I have an already Loki patched cwm touch posted in my list if you wanted to try it too.
I've found Odin helps clean all the garbage out though. So either way
Good luck!
sent from my Verizon Galaxy sIV
Sorry guys, I been reading so much about rooting my brain is starting to go numb. I just rooted / unlocked bootloader and flashed twrp with CASUAL and wanted to know if its worth it to go to MJ9, Just wondering what your opinions are.
Thanks!
loccoelf said:
Sorry guys, I been reading so much about rooting my brain is starting to go numb. I just rooted / unlocked bootloader and flashed twrp with CASUAL and wanted to know if its worth it to go to MJ9, Just wondering what your opinions are.
Thanks!
Click to expand...
Click to collapse
NOOOOO!!! Don't go to MJ9!!! You WILL get a locked bootloader for which there's no unlock method.
Stick to unlocked VRAMC3 and just try custom 4.3 roms by using a custom recovery
ahh
lvov7342 said:
NOOOOO!!! Don't go to MJ9!!! You WILL get a locked bootloader for which there's no unlock method.
Stick to unlocked VRAMC3 and just try custom 4.3 roms by using a custom recovery
Click to expand...
Click to collapse
Any reason why you say 4.3 ? I'm on 4.4.2 gummy nightly and its great. Am I missing the goodness?
loccoelf said:
Any reason why you say 4.3 ? I'm on 4.4.2 gummy nightly and its great. Am I missing the goodness?
Click to expand...
Click to collapse
Well 4.3 is the latest Touchwiz where as 4.4.2 is AOSP. And the goodness really depends on the user.
Also, you can update to the MJ9 firmware without locking your bootloader. ONLY using the OTA will lock your bootloader. You can flash the firmware in ODIN to update, and then install a custom 4.3 ROM.
OK
jcollier said:
Well 4.3 is the latest Touchwiz where as 4.4.2 is AOSP. And the goodness really depends on the user.
Also, you can update to the MJ9 firmware without locking your bootloader. ONLY using the OTA will lock your bootloader. You can flash the firmware in ODIN to update, and then install a custom 4.3 ROM.
Click to expand...
Click to collapse
would you recommend that or should i just stay on the older firmware if you had to pick?
loccoelf said:
would you recommend that or should i just stay on the older firmware if you had to pick?
Click to expand...
Click to collapse
To each, their own I think. I haven't had any problems and everything works for me. If you like where you are at, then you may not want to bother.
k
jcollier said:
To each, their own I think. I haven't had any problems and everything works for me. If you like where you are at, then you may not want to bother.
Click to expand...
Click to collapse
I have not had any issues yet, is there any definite fixes in MJ9 that you noticed personally that were definitely because of the firware?
loccoelf said:
I have not had any issues yet, is there any definite fixes in MJ9 that you noticed personally that were definitely because of the firware?
Click to expand...
Click to collapse
The modem/radios are updated but I haven't seen any positive or negative consequences.
loccoelf said:
Any reason why you say 4.3 ? I'm on 4.4.2 gummy nightly and its great. Am I missing the goodness?
Click to expand...
Click to collapse
Do you use exchange for email at all? I can't get it working on any of the 4.4.2 builds out (CM11 or OmniROM). I'll have to check out gummy though.
jcollier said:
The modem/radios are updated but I haven't seen any positive or negative consequences.
Click to expand...
Click to collapse
I've updated to 4.4.2 for both CM11 and OmniROM and in both cases, my signal strength has decreased. Maybe it's my area? I've seen posts about updating the modem/radios outside of the ROM, which seemed to help a small amount.
jdustinb said:
Do you use exchange for email at all? I can't get it working on any of the 4.4.2 builds out (CM11 or OmniROM). I'll have to check out gummy though.
I've updated to 4.4.2 for both CM11 and OmniROM and in both cases, my signal strength has decreased. Maybe it's my area? I've seen posts about updating the modem/radios outside of the ROM, which seemed to help a small amount.
Click to expand...
Click to collapse
I definitly notice a Sig drop..I don't use exchange
I have been on 4.3 since the leak came out..flashed N3bula, Sophisticated and am on Nephilium now. I was a Beans devotee for a long time on 4.1.2 and will definitely be trying 23 when it comes out.
All that said, I can only point to one noticeable improvement with 4.3 and that is apps to SD card (I never wanted to do an SD card swap). If anything I have given up a bunch of features from Beans 22 that I liked. Hopefully 23 will be everything from 22 and more on 4.3.
Many of you know exactly what "oversharpening" is... for those who not, just google "g3 oversharpening" or check this article.
After hours spent trying almost everything i finally managed to remove that. Check in the 2nd thread to see the difference.
Here you go... just flash the kernel in recovery but remember to make a backup of the boot partition before, just in case it will not works.
Remember... the only weird thing is that you have to turn off the screen and then on again to make it works. Just the 1st time after the boot.
DOWNLOADS:
D855 Kitkat Lollipop
D851 Kitkat
D850 Kitkat
LS990 Kitkat
F400 Kitkat
VS985 Kitkat
D852 Kitkat
...i'm currently building for all the variants
Of course, tell me what you think.
Like always... DONATIONS are wellcome!!!
Lollipop Source
Kitkat Source
tnx to @Tectas for the kernel source
Thanks try and report tomorow.
Awesome job! Tectas and/or I plan on pulling this to the rin repository. Credit will be given, thank you!
Is this for the new zv6 update, or does it matter which version?
bizzzle said:
Is this for the new zv6 update, or does it matter which version?
Click to expand...
Click to collapse
bump
Sent from my LGLS990 using XDA Free mobile app
mrkrabs said:
bump
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
Zv4 and zv6 are nearly identical. I've been running rin kernel for zv4 on zv6 for days with no issue. Kernel source looks the same.
HPTesla said:
Zv4 and zv6 are nearly identical. I've been running rin kernel for zv4 on zv6 for days with no issue. Kernel source looks the same.
Click to expand...
Click to collapse
I was under the impression that the new ZV6 update came with a new kernel. I thought that's what fixed the AUX problems, as well as some other issues. I guess maybe that was in the ROM and not in the kernel?
Your OP says this file is a Kernel. Are we actually flashing a full kernel, or does this file modify our existing kernel?
I gave this a shot last night on my LS990 before I read your reply. It does indeed fix my oversharpening issue. No bugs have been noticed so far. Thanks! I'm surprised there isn't more discussion on this thread so far!!!
BTW, I updated to ZV6 a couple days ago via dirty flash over stock rooted.
bizzzle said:
I was under the impression that the new ZV6 update came with a new kernel. I thought that's what fixed the AUX problems, as well as some other issues. I guess maybe that was in the ROM and not in the kernel?
Your OP says this file is a Kernel. Are we actually flashing a full kernel, or does this file modify our existing kernel?
I gave this a shot last night on my LS990 before I read your reply. It does indeed fix my oversharpening issue. No bugs have been noticed so far. Thanks! I'm surprised there isn't more discussion on this thread so far!!!
BTW, I updated to ZV6 a couple days ago via dirty flash over stock rooted.
Click to expand...
Click to collapse
I did say "nearly". So close in fact that I have run kernels for one on the other without issue. That's all I meant.
I never really noticed the sharpening but now it does look way more natural to me. Thanks man.
Does this do anything if we are running cm11 or cm12. I'm currently running cm12 11/25 build. But yesterday I flashed bar-rin vz6 rom, now I'm on cm12
Sent from my LG-ls990 using Xparent Green Tapatalk 2
aheeejd said:
Does this do anything if we are running cm11 or cm12. I'm currently running cm12 11/25 build. But yesterday I flashed bar-rin vz6 rom, now I'm on cm12
Sent from my LG-ls990 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
No it doesn't do anything because Cm has its own kernel. Unless the dev includes it into his cm kernel sources then it would. The kernel changes as you flash between Roms especially between stock based and aosp Roms.
This worked great, thank you very much. Definitely noticed an improvement to the point where it took me by surprise when I looked at the phone. So much more detail. Just like on an HDTV, turn the sharpness off!
Skin1980 said:
Many of you know exactly what "oversharpening" is... for those who not, just google "g3 oversharpening" or check this article.
After hours spent trying almost everything i finally managed to remove that. Check in the 2nd thread to see the difference.
Here you go... just flash the kernel in recovery but remember to make a backup of the boot partition before, just in case it will not works.
Remember... the only weird thing is that you have to turn off the screen and then on again to make it works. Just the 1st time after the boot.
DOWNLOADS:
all I have is the stock recovery , How is that done ? Thanks .
Click to expand...
Click to collapse
Houndog101 said:
Skin1980 said:
Many of you know exactly what "oversharpening" is... for those who not, just google "g3 oversharpening" or check this article.
After hours spent trying almost everything i finally managed to remove that. Check in the 2nd thread to see the difference.
Here you go... just flash the kernel in recovery but remember to make a backup of the boot partition before, just in case it will not works.
Remember... the only weird thing is that you have to turn off the screen and then on again to make it works. Just the 1st time after the boot.
DOWNLOADS:
all I have is the stock recovery , How is that done ? Thanks .
Click to expand...
Click to collapse
You have to be rooted and bumped in order to flash this or anything else that is custom.
Click to expand...
Click to collapse
Thanks , I'm rooted (stump root) , I'll search for Bump..
Houndog101 said:
Thanks , I'm rooted (stump root) , I'll search for Bump..
Click to expand...
Click to collapse
Here
http://forum.xda-developers.com/showthread.php?t=2900588
And use Flashify to flash the image easy
Coming from somebody with 20/16 vision, THANK YOU! I thought something was weird with the screen... couldn't tell what it was but knew something was off. I've had AMOLED screens for a while now, so though it was related to switching from AMOLED to IPS.
THANKS OP!!!
Working great on a Sprint LS990 stock rooted/bumped.
Just posting in here that I tried this and it is very, very nice! It took me a few times of flashing this vs Stock ZV6 kernel to really notice it but once I did, it is night and day difference.
Cheers for this, maybe we can get this implemented in future kernels if LG doesn't?
So ive used this before and seemed to work ok but now when i try it, it hangs at the boot screen and flashes blue and orange on the lcd, black screen. Tried different downloads and all... Baron's ROM atm...
jr71x said:
So ive used this before and seemed to work ok but now when i try it, it hangs at the boot screen and flashes blue and orange on the lcd, black screen. Tried different downloads and all... Baron's ROM atm...
Click to expand...
Click to collapse
I've already added this to Barrin 3.0.1
UPDATE: SOLVED, as of 07 FEB 2016; I needed to find an .MD5-compiled ROM with an NC5 bootloader; my last working bootloader was NC5 and using Odin to flash ROMs with other bootloaders had failed.
My phone has been rooted for over 2 years now and I've run a handful of ROMs, with Hyperdrive probably the most stable of the lot. Last fall I was losing some functionality (bad microphone) and I figured I might as well try a new ROM in case that helped. I install CM 12 and life was okay. I set it to download updates (mistake) and it upgraded me from CM 12 to CM 13. Much as I like the new Marshmallow features, my S4 steadily degraded in function over time, to the point where I stopped making or receiving phone calls.
Last week half of my installed apps disappeared, and attempting to install anything through the Google Play store failed. No clue how that might happen, but I knew it was time to flash a new ROM.
That was when I discovered I could no longer boot into TWRP; it hung on the TEAMWIN logo screen. Then I started getting the Verizon screen claiming it had detected unauthorized software.
Since I could no longer operate the phone, I went ahead and put it into download mode and ran Odin3 v3.10.7 and used that to flash an OC1 ROM, the only one I had that was in .MD5 format.
Now I can't get past a bootloop that leaves me hanging at the Verizon logo screen.
Any thoughts?
What is your bootloader right now? And/or what was it while on Hyperdrive?
Edit: wait....I see where u Odin'd oc1...was it the stock image? If so u may have flashed the oc1 boot.img. If that's the case, I suggest you download FlashFire and read up on it. Because if u were on nc5 or anything before you should be able to ODIN back down. But if u have an oc1 bootloader you're permalocked.
Huh. I tried to respond to this hours ago. Didn't upload, apparently.
Anyhow, thanks for responding. I have not been able to get an .MD5 version of the stock image to flash. The only complete .MD5 I've successfully downloaded is called "I545VRUGOC1_Neutered_Full_Odin.tar.md5". The last ROM running on this device was CyanogenMod 13, which is Android 6 with NC5 kernel.
I'm currently attempting to download "VRUFNC5 Full-Wipe Verizon SCH-I545 4.2.2 562219 Stock Restore.tar.md5" but it is slow going.
As for FlashFire, how could I install it to my phone? I cannot get past the bootloop. Odin seems to be my only option for flashing at this point, right?
Have you tried going to recovery after flashing OC1? maybe there are some leftovers of previous process, if your phone can go into recovery you should try to do some wipes
Edgardo_Uchiha said:
Have you tried going to recovery after flashing OC1? maybe there are some leftovers of previous process, if your phone can go into recovery you should try to do some wipes
Click to expand...
Click to collapse
Great suggestion; unfortunately, TWRP is blocked by the Verizon notice now (the one that tells you Verizon's identified unauthorized software on the phone).
Okay, I'm going to try an NC5.MD5 that I was able to download. Here's hoping it moves this process forward....
I can help you! I have everything! PM me here, or send me a message on hangouts!
Sent from my SCH-I545 using Tapatalk
Cincinnatux said:
Huh. I tried to respond to this hours ago. Didn't upload, apparently.
Anyhow, thanks for responding. I have not been able to get an .MD5 version of the stock image to flash. The only complete .MD5 I've successfully downloaded is called "I545VRUGOC1_Neutered_Full_Odin.tar.md5". The last ROM running on this device was CyanogenMod 13, which is Android 6 with NC5 kernel.
I'm currently attempting to download "VRUFNC5 Full-Wipe Verizon SCH-I545 4.2.2 562219 Stock Restore.tar.md5" but it is slow going.
As for FlashFire, how could I install it to my phone? I cannot get past the bootloop. Odin seems to be my only option for flashing at this point, right?
Click to expand...
Click to collapse
You're on the right path. ODIN the nc5 full wipe. And from there you can use Safestrap to flash whatever. But I'm wondering if you've locked the bootloader to oc1 or of1. If that's the case, you can go to sammobile.com and register and sign-in and download any factory image flashable thru ODIN.
The nc5.md5 worked! It's not particularly stable (yet), but at least the phone boots up and seems to work.Thanks to those who took the time to read over the issue and offer suggestions!
May i ask how you had cm13 running on nc5? @Cincinnatux
klabit87 said:
May i ask how you had cm13 running on nc5? @Cincinnatux
Click to expand...
Click to collapse
Yeah me too?!...I was confused throughout this whole post, but I'm glad he took the advice and got nc5 full wipe. Does the trick everytime (on a downgradeable bootloader of course).
ATGkompressor said:
Yeah me too?!...I was confused throughout this whole post, but I'm glad he took the advice and got nc5 full wipe. Does the trick everytime (on a downgradeable bootloader of course).
Click to expand...
Click to collapse
Perhaps I am mistaken. I had NC5 the last time I had checked, which was when I installed CM12. Sometime around December or so CM12 upgraded itself to CM13. The only thing I remember having to change was GAPPS, moving that from 5.1 to 6.0.
Cincinnatux said:
Perhaps I am mistaken. I had NC5 the last time I had checked, which was when I installed CM12. Sometime around December or so CM12 upgraded itself to CM13. The only thing I remember having to change was GAPPS, moving that from 5.1 to 6.0.
Click to expand...
Click to collapse
Regardless of whether it was CM12 or CM13, I would still like to know how you did it and where you got the files from.
Thanks.
klabit87 said:
Regardless of whether it was CM12 or CM13, I would still like to know how you did it and where you got the files from.
Thanks.
Click to expand...
Click to collapse
While I used to troll XDA for ROMs, for CM I'm sure I went to their website and downloaded whatever was current at the time, which was a Lollipop ROM. I used TWRP to install, but I no longer have any of my notes for that install so I couldn't verify any of this, really.
Cincinnatux said:
While I used to troll XDA for ROMs, for CM I'm sure I went to their website and downloaded whatever was current at the time, which was a Lollipop ROM. I used TWRP to install, but I no longer have any of my notes for that install so I couldn't verify any of this, really.
Click to expand...
Click to collapse
If that's the case then you actually had the mdk bootloader. There is no way to have any cm based rom on nc5.
klabit87 said:
If that's the case then you actually had the mdk bootloader. There is no way to have any cm based rom on nc5.
Click to expand...
Click to collapse
That's what I was assuming as well. When I had the s3, I was able to install a cm Rom thru Safestrap. Actually the other thread we were in by mohammad.afaneh, he was a dev on the Safestrap for s3 and got it to support a cm Rom, but it didn't have working data signal or Wi-Fi.
ATGkompressor said:
That's what I was assuming as well. When I had the s3, I was able to install a cm Rom thru Safestrap. Actually the other thread we were in by mohammad.afaneh, he was a dev on the Safestrap for s3 and got it to support a cm Rom, but it didn't have working data signal or Wi-Fi.
Click to expand...
Click to collapse
So he got kexec working? That would be nice.
Maybe he can provide some insight on this.
I know many others that would love to use cm based roms.
Would be even better if he could get safestrap to work on oc1/of1 bootloaders
klabit87 said:
So he got kexec working? That would be nice.
Maybe he can provide some insight on this.
I know many others that would love to use cm based roms.
Would be even better if he could get safestrap to work on oc1/of1 bootloaders
Click to expand...
Click to collapse
I don't think it was kexec. But go to the s3 forums and/or search his afh. We could probably modify it, or figure out exactly what he changed and incorporate it into the SS we have. Depending on what he changed, it may be possible to implement nc5flasher, gain support for AOSP bases (aka get them to boot). But in order to have a fully functional modem/firmware, the kernel would need to be built from source. I do know there is a thread (I think in s4 unified development) on a proof of concept project that will enable insecure modules on locked bootloaders. I could be wrong about the actual forum it's in and exactly what's involved. I believe it can be done, it's just gonna take many minds focused on a common goal with positive intent.
PS. There's a bounty and it would be nice if we could do it.
---------- Post added at 11:47 PM ---------- Previous post was at 11:45 PM ----------
SORRY FOR HIJACKING YOUR POST @Cincinnatux!!!!!
klabit87 said:
So he got kexec working? That would be nice.
Maybe he can provide some insight on this.
I know many others that would love to use cm based roms.
Would be even better if he could get safestrap to work on oc1/of1 bootloaders
Click to expand...
Click to collapse
No, he modded CM enough to work with SS...
klabit87 said:
If that's the case then you actually had the mdk bootloader. There is no way to have any cm based rom on nc5.
Click to expand...
Click to collapse
Just to reduce my ignorance a little, maybe one of you can point out the error in my thinking/memory. I thought NC5 vs MDK vs OC1 was whatever was listed in About Phone as the Baseband Version, right? While my phone was MDK at the time of purchase (July 2013), I changed the baseband a few times while upgrading to newer flavors of Android. My current baseband is I545VRUFNC5, which is what I remember it being last fall as well. Where am I mistaken? Thanks!
Cincinnatux said:
Just to reduce my ignorance a little, maybe one of you can point out the error in my thinking/memory. I thought NC5 vs MDK vs OC1 was whatever was listed in About Phone as the Baseband Version, right? While my phone was MDK at the time of purchase (July 2013), I changed the baseband a few times while upgrading to newer flavors of Android. My current baseband is I545VRUFNC5, which is what I remember it being last fall as well. Where am I mistaken? Thanks!
Click to expand...
Click to collapse
Baseband does not equal bootloader.
You can update the baseband no problem but can't update the bootloader without being able to go back.
There is an app that you could use to check your bootloader called samsung phone info I believe our something like that.
Just noticed CM11 official for hltevzw is now getting monthly builds... funny, we have no CM12 or CM13!
http://download.cyanogenmod.com/?device=hltevzw&type=
It got me thinking, though... there are a ton of KK/based roms that are very smooth. In fact, I still think kitkat is the best base for this device as far as stability and battery life. Just look at the size of some of the custom ROMS like DU (180-190 MB) and the fact that they boot in under 20 seconds... even on the initial boot. Crazy efficiency.
I am sure that most people here disagree and interest in running CM11 is pretty low. But it still seems like it should be an option... especially since it is the most current official CM we have (last build is 6-12-2016)
The problem is that the radio in Kitkat doesn't work when coming from OF1. Theoretically, it should work if you ODIN back to KK... but that is not an option given the root/unlock scenarios we have.
So, question is...how do we get the radio working on CM11 coming from OF1... hmmm
I like your thinking mightysween. I saw the same thing last week and wondered myself. Can this be done?
Droidify said:
I like your thinking mightysween. I saw the same thing last week and wondered myself. Can this be done?
Click to expand...
Click to collapse
It would seem that flashing the modem would work... but I tried two KK modems with no luck.
Will post some logcats, and maybe we can figure out the right combo.
IDK I am now strongly considering downgrading to 4.4.2. There are a whole lot more stable ROMS available for KitKat than Lollipop for this device. I might pull the trigger this weekend. Currently investigating viability.
Any luck on this?
Sent from my SM-N900V using Tapatalk
bishop0114 said:
Any luck on this?
Click to expand...
Click to collapse
Not yet... but wow. If you put a new looking theme on any of the refined CM11 based stuff (like DU), people would be abuzz about how smooth and responsive this "new" rom is. I think these older devices are just happier with the older android versions.
Just can't seem to make the radio work...
Have tried as far back as NC4/NK1 modems... but they either don't work at all or exhibit the same problems as OF1.
I wonder if @Moepda might have any insight having worked on sm900 ROMS through the 4.4 to 5.1 updates...
Seems that there must be a modem that would work...or is the newer bootloader version a problem in running 4.4 based roms?
Well... Stupid me never checked to see if ODIN flashing the modems was actually working. It is not! I have tried both tar.md5 versions and directly flashing the modem.bin, and while it appears to work and ODIN says "pass", the modem stays on OF1.
So that's the issue...
That said, it is not a radio problem in general, it is an LTE registration issue. So, when set to 3g only it works AOK!
If I can figure out how to get the flash of NK1 or NC4 modem to stick, I believe LTE would work...
mightysween said:
Well... Stupid me never checked to see if ODIN flashing the modems was actually working. It is not! I have tried both tar.md5 versions and directly flashing the modem.bin, and while it appears to work and ODIN says "pass", the modem stays on OF1.
So that's the issue...
That said, it is not a radio problem in general, it is an LTE registration issue. So, when set to 3g only it works AOK!
If I can figure out how to get the flash of NK1 or NC4 modem to stick, I believe LTE would work...
Click to expand...
Click to collapse
Sounds promising. I wonder if there is a zip we can install via TWRP.
Sent from my SM-N900V using Tapatalk
bishop0114 said:
Sounds promising. I wonder if there is a zip we can install via TWRP.
Click to expand...
Click to collapse
There used to be flashable modems here on XDA, but all the links are dead. I suppose I could just make one and try.
FWIW, I am running an OLD Dirty Unicorns moepda build from 2014, and it is quite refreshing after so long with cm12 and cm13. Fast, stable, and seemingly lacking nothing I use compared to CM12/13
mightysween said:
FWIW, I am running an OLD Dirty Unicorns moepda build from 2014, and it is quite refreshing after so long with cm12 and cm13. Fast, stable, and seemingly lacking nothing I use compared to CM12/13
Click to expand...
Click to collapse
Sounds interesting. Can you provide an installation guide based upon what you've done? Versions used, steps taken, etc. If you don't want to publish it to prevent people from damaging something you can PM me.
Thanks
Droidify said:
Sounds interesting. Can you provide an installation guide based upon what you've done? Versions used, steps taken, etc. If you don't want to publish it to prevent people from damaging something you can PM me.
Thanks
Click to expand...
Click to collapse
No steps at all, really... it just works. Flashed and then switch to 3g preferred.
I don't need LTE... so I haven't spent much time trying to figure it out. Both this old DU and CM11 monthly are working fine as long as LTE is shut off
Obviously, CM11 is available from get.cm
...
the last version of DU 4.4.4 is here:
https://www.androidfilehost.com/?fid=95784891001606282
mightysween said:
Obviously, CM11 is available from get.cm
...
the last version of DU 4.4.4 is here:
https://www.androidfilehost.com/?fid=95784891001606282
Click to expand...
Click to collapse
I am going to give this a whirl. I have always had trouble with finding the right gapps for KitKat though. Which did you select?
Notice much drop off in using 3G instead of LTE?
BTW In an earlier post I mentioned I was going to downgrade. Well, that's not really possible and you might already know that. I attempted 4.4.2 and was abruptly stopped by the bootloader. I did read though that 4.4.4 was possible, but if we can do all this and get a stable ROM that has GPS and Bluetooth functional why bother?
Droidify said:
I am going to give this a whirl. I have always had trouble with finding the right gapps for KitKat though. Which did you select?
Notice much drop off in using 3G instead of LTE?
BTW In an earlier post I mentioned I was going to downgrade. Well, that's not really possible and you might already know that. I attempted 4.4.2 and was abruptly stopped by the bootloader. I did read though that 4.4.4 was possible, but if we can do all this and get a stable ROM that has GPS and Bluetooth functional why bother?
Click to expand...
Click to collapse
I am on wifi about 90% of the time, and when I am not it is usually while driving. So having only 3g doesn't bother me.
Bluetooth and GPS seem to work fine... GPS is certainly faster and more stable than LP/MM
Droidify said:
I am going to give this a whirl. I have always had trouble with finding the right gapps for KitKat though. Which did you select?
Notice much drop off in using 3G instead of LTE?
BTW In an earlier post I mentioned I was going to downgrade. Well, that's not really possible and you might already know that. I attempted 4.4.2 and was abruptly stopped by the bootloader. I did read though that 4.4.4 was possible, but if we can do all this and get a stable ROM that has GPS and Bluetooth functional why bother?
Click to expand...
Click to collapse
Oh, and I just use open gapps nano... works fine
I take that back... You need to set the preferred network to LTE, let it connect (and then fail), and THEN set to 3G in order for it to stick.
Love the feature set from DU, but have to say that the 6-12-2016 nightly is pretty smooth.
So is LTE working on the 4.4.4 build?
Sent from my SM-N900V using Tapatalk
bishop0114 said:
So is LTE working on the 4.4.4 build?
Click to expand...
Click to collapse
No... It connects, but then disconnects and reconnects repeatedly.
3G works fine