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
Related
So I was given an galaxy note i717 att version the other day and I'd like to use it on tmobile. Anyways I unlocked the phone and flashed tmobiles radios/modems on it but I want to use a different rom on the phone. Will I mess up the phone if I put a rom on it because i changed the network modems?, and if not which rom should I use with my att note i717 on tmobile?
bluebeanie said:
So I was given an galaxy note i717 att version the other day and I'd like to use it on tmobile. Anyways I unlocked the phone and flashed tmobiles radios/modems on it but I want to use a different rom on the phone. Will I mess up the phone if I put a rom on it because i changed the network modems?, and if not which rom should I use with my att note i717 on tmobile?
Click to expand...
Click to collapse
You can run any rom you like if you've flashed the right version of recovery. There are several 4.4.2 roms available if you want to run the latest. Depending on your area, you may get as good a signal with an att modem. Personally I'm running the BlownFuze 4.4.2 with the UVLG3 modem, with no major issues.
jman315 said:
You can run any rom you like if you've flashed the right version of recovery. There are several 4.4.2 roms available if you want to run the latest. Depending on your area, you may get as good a signal with an att modem. Personally I'm running the BlownFuze 4.4.2 with the UVLG3 modem, with no major issues.
Click to expand...
Click to collapse
Oh ok. Im kinda new to this. Im gonna go ahead and try that rom but say it doesnt work right and I want to change it. Do i just go back to CWM recovery and restore from my backup?
bluebeanie said:
Oh ok. Im kinda new to this. Im gonna go ahead and try that rom but say it doesnt work right and I want to change it. Do i just go back to CWM recovery and restore from my backup?
Click to expand...
Click to collapse
Yes, make a CWM backup first in case something goes wrong. Also, make sure you're running CWM 6.0.4.3 before you flash a 4.4.2 rom
jman315 said:
Yes, make a CWM backup first in case something goes wrong. Also, make sure you're running CWM 6.0.4.3 before you flash a 4.4.2 rom
Click to expand...
Click to collapse
Ok thanks. Im new to this so im not trying to bug you but that will restore my gapps and stuff right?
bluebeanie said:
Ok thanks. Im new to this so im not trying to bug you but that will restore my gapps and stuff right?
Click to expand...
Click to collapse
Any JB and up roms, you will need to flash gapps again, but your apps will come back when you log in your gmail. Just read the OP for rom you use and there will be a link to appropriate gapps, though many are the same.
If your new though, I would advise you to read up a bit. Nobody is going to replace your phone if you dont understand and as far as I know, nobody has invented a time machine yet.
Welcome aboard, its fun, but nobody is responsible but you.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
captemo said:
Any JB and up roms, you will need to flash gapps again, but your apps will come back when you log in your gmail. Just read the OP for rom you use and there will be a link to appropriate gapps, though many are the same.
If your new though, I would advise you to read up a bit. Nobody is going to replace your phone if you dont understand and as far as I know, nobody has invented a time machine yet.
Welcome aboard, its fun, but nobody is responsible but you.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Click to expand...
Click to collapse
Ok. Thanks. Im really liking the community here. I think im going to try and build my own rom for my note.
I never changed the radio for T-Mobile on my at&t note. It works fine. Good luck to ya and welcome to the community.
Sent from my HTC One Max using Tapatalk!
Same here - never changed a radio. I have rooted and customized a few of i717 and the previous radio seems to either stay on or in some cases such as BeanStalk Rom it replaced my radio. Either way they are all on target with TMO.
Hi folks, I've beem looking forward to flash/use my AT&T galaxy note 2 on T-Mobile as well, can some one please share your experience and the links to flashing or unlocking it please?
Those on MK2 With safe strap and want to get rid of Touch Wiz ( which I do -.-) Get the Illusion ROM for your Galaxy S4 (Verizon). That's all. Except the only bug/s is WiFi doesn't even if you try flashing the MK2 Module's. And those On AT&T, T-Mobile, Straight Talk, NET10... Etc using there Verizon Galaxy S4 will not get Data to work. I have Straight talk and tried everything to get Data to work. I've flashed all Carrier Roms (the AT&T, Sprint, Verizon, and U.S. Cellular) together and see if that would help. Nope. But Messaging (just SMS) works and so does calls and Voice Mail (xD)
And if someone could extract this and try making another AOSP ROM that works with MK2 (or SafeStrap) and make CM11/10 to work, that would be excellent!
Credit for the ROM goes to the Developer. I am not endorsed with the development/developer nor do I hold responsible for your phone being a toaster
http://forum.xda-developers.com/showthread.php?t=2316312
How is a 4.2 ROM compatible with MK2, and how is it compatible with Safestrap? Not to mention the thread hasn't been updated since July...
RemnantKing2 said:
How is a 4.2 ROM compatible with MK2, and how is it compatible with Safestrap? Not to mention the thread hasn't been updated since July...
Click to expand...
Click to collapse
Crazy thing is it actually worked
elias98902 said:
Those on MK2 With safe strap and want to get rid of Touch Wiz ( which I do -.-) Get the Illusion ROM for your Galaxy S4 (Verizon). That's all. Except the only bug/s is WiFi doesn't even if you try flashing the MK2 Module's. And those On AT&T, T-Mobile, Straight Talk, nett... Etc using there Verizon Galaxy S4 will not get Data to work. I have Straight talk and tried everything to get Data to work. I've flashed all Carrier Roms (the AT&T, Sprint, Verizon, and U.S. Cellular) together and see if that would help. Nope. But Messaging (just SMS) works and so does calls and Voice Mail (xD)
And if someone could extract this and try making another AOSP ROM that works with MK2 (or SafeStrap) and make CM11/10 to work, that would be excellent!
Credit for the ROM goes to the Developer. I am not endorsed with the development/developer nor do I hold responsible for your phone being a toaster
http://forum.xda-developers.com/showthread.php?t=2316312
Click to expand...
Click to collapse
Its 4.2...mk2 is 4.3...is it possible to flash 4.2 modules on latest safestrap?...this is pretty cool to see even partially working aosp for SS users...might make a point of getting hashcodes attention on this...he may be able to fix WiFi and such or figure out what's allowing it to work and implement it in other ROMs...nice find
I was bored, so I started installing random ROMs and Walla... A AOSP ROM working!
And I Dont know... Crazy things happen in Life O.O
Sent from my SCH-I545 using Tapatalk
Possibly
If they could break down this rom and figure out how it works with safestrap we could possibly get all asop roms working:laugh::good:
And if I had a debit card I'd give all my money to the person that breaks it down
Sent from my SCH-I545 using Tapatalk
@Hashcode
Sent from my SCH-I545 using Tapatalk
MajorLeagueROM said:
If they could break down this rom and figure out how it works with safestrap we could possibly get all asop roms working:laugh::good:
Click to expand...
Click to collapse
If you guys are on 4.2.2, it would make since if it was a gpe rom, as gpe was somehow compatible with 4.2.2 safestrap. If I remember correctly, someone said that the differences between the kernels was negligible and could boot with the tw kernel.
I would say its safe to assume that its actual AOSP seeing that it uses the CM kernel source (or at links to it on the OP), however, there are no accounts in the thread of the rom cook saying that it is AOSP, only other posters.
Haven't tried to download it yet, but I'm going to convince myself that you guys are just pulling a sick April fools prank.
Kamaole said:
If you guys are on 4.2.2, it would make since if it was a gpe rom, as gpe was somehow compatible with 4.2.2 safestrap. If I remember correctly, someone said that the differences between the kernels was negligible and could boot with the tw kernel.
I would say its safe to assume that its actual AOSP seeing that it uses the CM kernel source (or at links to it on the OP), however, there are no accounts in the thread of the rom cook saying that it is AOSP, only other posters.
Click to expand...
Click to collapse
Well so far it's AOSP ROM. It has pure android, the weight of the zip is so light and if. And yes, A Dev did say it wasn't compatible with any AOSP ROM's. But I found a ROM that works! I'll post some screen shots of the AOSP ROM. And if it says AT&T its because I have a Straight Talk Sim Card in it.
So far people are eager with this. If we can get more people's attention we can probably get Hashcode to see what's making this ROM work on AOSP
Sent from my SCH-I545 using Tapatalk
elias98902 said:
Well so far it's AOSP ROM. It has pure android, the weight of the zip is so light and if. And yes, A Dev did say it wasn't compatible with any AOSP ROM's. But I found a ROM that works! I'll post some screen shots of the AOSP ROM. And if it says AT&T its because I have a Straight Talk Sim Card in it.
So far people are eager with this. If we can get more people's attention we can probably get Hashcode to see what's making this ROM work on AOSP
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
What BL version do you have?
Kamaole said:
What BL version do you have?
Click to expand...
Click to collapse
If BL stands for Bootloader than I have I have MK2 android 4.3
Sent from my SCH-I545 using Tapatalk
elias98902 said:
If BL stands for Bootloader than I have I have MK2 android 4.3
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
The android build is not necessarily the same as the BL just so you know.
Kamaole said:
The android build is not necessarily the same as the BL just so you know.
Click to expand...
Click to collapse
So where would I find the bootloader?
Sent from my SCH-I545 using Tapatalk
elias98902 said:
So where would I find the bootloader?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I believe it can be seen in recovery (actual recovery; not safestrap)
Kamaole said:
I believe it can be seen in recovery (actual recovery; not safestrap)
Click to expand...
Click to collapse
He he. Funny story... Um.... I tried flashing a CWM Recovery didn't work and it leads me to the Odin Flash screen. All I have is Safestrap 3.71
Is there another possible way?
Sent from my SCH-I545 using Tapatalk
elias98902 said:
He he. Funny story... Um.... I tried flashing a CWM Recovery didn't work and it leads me to the Odin Flash screen. All I have is Safestrap 3.71
Is there another possible way?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I believe theres an app that does it.
To anyone wanting to do this, I did it and its not booting into the system. Idk if theres a very special case or what. In recovery it is saying I have the kot49h kernel. Until I boot, Im still assuming its an april fools prank
Kamaole said:
I believe theres in app that does it.
To anyone wanting to do this, I did it and its not booting into the system. Idk if theres a very special case or what.
Click to expand...
Click to collapse
Well that happened to me as well. It wouldn't boot up to the system so I booted up to the actual Odin Flash and it said Volume Up=Continue and Volume Down=Cancel(Restart) and then I did the Volume down and it got into the system. Well I hope that helps!
Sent from my SCH-I545 using Tapatalk
elias98902 said:
Well that happened to me as well. It wouldn't boot up to the system so I booted up to the actual Odin Flash and it said Volume Up=Continue and Volume Down=Cancel(Restart) and then I did the Volume down and it got into the system. Well I hope that helps!
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
This didn't work. It boot loops and goes into recovery.
Edit: ****ed up and erase all my stuff in safestrap, ill mess with it later
Screenshots?
Sent from my SCH-I545 using Tapatalk
Hi! I am rebel1699. I have done work on the S4 i337 (root for 4.4.2). Recently, I bought an SCH-R960 for something to do. After messing with it for a while, I have discovered that custom roms are indeed possible, but with some things that need work. Here is my current configuration
SlimKat 4.4.4
Philz Touch Recovery
As you may know, the touch recoveries do not respond to touch on this model. However, the vol +/- and power for select still work fine. After getting this ironed out, it was time to experiment. I downloaded SlimKat, and made a few modifications. Booted to recovery and made my nandroid. Then, on to wipes and install. Results---
Upon reboot, I was greeted with the "Warranty bit:kernel" on the top of the sceen. I didnt care. Warranty was long gone anyways. But, it booted into SlimKat just fine. Heres where the dev needs to begin. There is NO TOUCH. I even made a flashable of the stock 4.4.2 kernel modules, but still no help. Not unexpected, considering the recoveries do the same. Using my otg, I connected a mouse for navigation. It is indeed the custom kernel. WiFi, bt, and everything else seem to work fine. I cannot test cellular operation as I am not a US Cellular customer. So, there is another issue. I guess it could be possible to flash a correct radio. Not sure.
First things first---We need touch drivers working on this to go any further. We get that, and sky is the limit.
You probably have to backported the input drivers for your model
Just pull official kernel sources from samsung open modify the drivers of cm kernel
Sent from my HTC D816w using XDA Free mobile app
Grarak said:
You probably have to backported the input drivers for your model
Just pull official kernel sources from samsung open modify the drivers of cm kernel
Sent from my HTC D816w using XDA Free mobile app
Click to expand...
Click to collapse
Same as I was thinking. Sound is also out, but I fully expected that to be the case. Pulling the sammy input drivers should also allow for a custom touch recovery to be modified for the device. TWRP 2.7.0.1, preferrably. I will see what I can do over the next few days. Just started using a new laptop, so I have to get the time to sit down and set up a new dev environment. But again, I wont be able to test cellular radio compatibility. I use AT&T, so nno good for that.
Personally, Im buying the i9200 intl for my own use. But ill do what I can to help these US Cellular folks. They have not seen any development at all. Craigslist is littered with this SCH-R960. I understand why.
Why
Why are you saying that the touch recovery's don't work on this model. I flashed philz on mine and used it to gain root. Worked just fine for me!
MeatHammer311 said:
Why are you saying that the touch recovery's don't work on this model. I flashed philz on mine and used it to gain root. Worked just fine for me!
Click to expand...
Click to collapse
Because after flashing both philz touch and twrp 2.7.1.0 meliusltexxx recoveries, touch works on neither. The boot image does not contain the touch input drivers for the SCH-R960. Manual navigation is still operable
I guess you only have to enable some options in defconfig
Sent from my HTC D816w using XDA Free mobile app
Grarak said:
I guess you only have to enable some options in defconfig
Sent from my HTC D816w using XDA Free mobile app
Click to expand...
Click to collapse
Good to hear. I just got a new laltop and have been getting my enviro set back up and going.
Grarak said:
I guess you only have to enable some options in defconfig
Sent from my HTC D816w using XDA Free mobile app
Click to expand...
Click to collapse
These options your talking about, are they options to enable touch on these recovery's??
MeatHammer311 said:
These options your talking about, are they options to enable touch on these recovery's??
Click to expand...
Click to collapse
The recoveries, and the roms. All either is lacking are those thing within thier perspective kernels. Roms will still need more work, eg...audio. And as I said, I cannot comment on the celluler end of it since I do not have US Cellular service.
Some of the roms need an edit to thier updater script to install. Others do not. They just have to be checked first. Just edit out anything that call to Format "0". I cant remember the mmcblk #
Any more progress with this? I have a sch-r960 and I would gladly help test roms or do what I can.
Cheers
helpfull
statikrage said:
Any more progress with this? I have a sch-r960 and I would gladly help test roms or do what I can.
Cheers
Click to expand...
Click to collapse
I just bought one of these as well... have nandroid and stock... attempting to build up first rom/port.... we shall see... so device tree anywhere... tried to flash meliusltexx roms, but always get error 7
so cm 11 installed... shows lte... no touch... not sure where to go from here.... new to this... always just been a flasher..... never tried to port....
antimidas said:
I just bought one of these as well... have nandroid and stock... attempting to build up first rom/port.... we shall see... so device tree anywhere... tried to flash meliusltexx roms, but always get error 7
Click to expand...
Click to collapse
Did you edit the rom updater script before installing?
hmmmmm
not sure what to change other than specific model... it points to /system/xbin/touch, but there is no file there... yet in deodexedf stock rom the updater-script points to /system/bin/touch... which also is not in that zip either. gonna try to compile aosp then pull my touch file from phone i guess..... a bt difficult to find specific info at this point
antimidas said:
not sure what to change other than specific model... it points to /system/xbin/touch, but there is no file there... yet in deodexedf stock rom the updater-script points to /system/bin/touch... which also is not in that zip either. gonna try to compile aosp then pull my touch file from phone i guess..... a bt difficult to find specific info at this point
Click to expand...
Click to collapse
I would help more, but sadly I do not have the phone anymore. Anything more from me would be no more than wild speculation, lol.
rebel1699 said:
I would help more, but sadly I do not have the phone anymore. Anything more from me would be no more than wild speculation, lol.
Click to expand...
Click to collapse
i need idea of what to edit.... just changing model names doesnt seem like it would work... but maybe im wrong... hardware is the same as meliusxx.... so i just dont get it... just gonna experiment i guess.... gonna go in and change all reference i see.... also may try to remove the part that lists the touch... maybe if it isn't flashed the orig firmware i lay over top of will keep driver intact.... i dunno, just gonna keep at it.... cant seem to get help anywhere. at least you responded!!! Thank You for that. /bow
R960 vs I9205
What is the difference. Appear exactly the same in specs. Only difference appears to be the cellular provider. Has anyone tried to flash a I9205 to an R960 Mega 6.3 to see what happens? If so, what was the result??
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