Hi all,
I would really appreciate some clarification as to my situation-- I had a stock MDK build S4, and rooted, installed custom recovery, and then loaded Hyperdrive. Since then I've replaced CWM with TWRP and kept up with Hypderdrive updates up to 17.1.
Coming from MDK, do I have to worry about upgrading my modem / baseband / anything else like that? I'd really appreciate some insight.
Also, what KitKat ROMs are you guys using now? AOSP / AOKP / TW-based, I'm curious as to the other options that exist out there that people seem to be liking.
Thanks in advance.
You don't *have* to update your modem, but generally newer modems are better and more refined. Plus, the newer ones are AWS enabled, so if you have band 4 in your area you should benefit from better LTE speeds. It takes 10 seconds to flash a modem, I say flash until you find the best for you.
---------- Post added at 11:12 PM ---------- Previous post was at 11:11 PM ----------
Oh and as for ROMs..I'm just using Dan's GPE ROM and use lots of Gravity Box mods. Pretty stable ROM.
soad1789 said:
Hi all,
I would really appreciate some clarification as to my situation-- I had a stock MDK build S4, and rooted, installed custom recovery, and then loaded Hyperdrive. Since then I've replaced CWM with TWRP and kept up with Hypderdrive updates up to 17.1.
Coming from MDK, do I have to worry about upgrading my modem / baseband / anything else like that? I'd really appreciate some insight.
Also, what KitKat ROMs are you guys using now? AOSP / AOKP / TW-based, I'm curious as to the other options that exist out there that people seem to be liking.
Thanks in advance.
Click to expand...
Click to collapse
thesoldier said:
You don't *have* to update your modem, but generally newer modems are better and more refined. Plus, the newer ones are AWS enabled, so if you have band 4 in your area you should benefit from better LTE speeds. It takes 10 seconds to flash a modem, I say flash until you find the best for you.
---------- Post added at 11:12 PM ---------- Previous post was at 11:11 PM ----------
Oh and as for ROMs..I'm just using Dan's GPE ROM and use lots of Gravity Box mods. Pretty stable ROM.
Click to expand...
Click to collapse
Just make sure you only flash the modem only--it is pretty clearly marked in the modem thread in general
+1 on Gravity Box with Dan's ROM. GPE is far and away the smoothest, best performing ROM...proprietary drivers + AOSP leanness = smooth. The only thing I think comes close is Kantjer's SaberMod Slim (its in the international S4 forum general development--it is unified, though, and works fine with our S4).
thesoldier said:
You don't *have* to update your modem, but generally newer modems are better and more refined. Plus, the newer ones are AWS enabled, so if you have band 4 in your area you should benefit from better LTE speeds. It takes 10 seconds to flash a modem, I say flash until you find the best for you.
---------- Post added at 11:12 PM ---------- Previous post was at 11:11 PM ----------
Oh and as for ROMs..I'm just using Dan's GPE ROM and use lots of Gravity Box mods. Pretty stable ROM.
Click to expand...
Click to collapse
brizey said:
Just make sure you only flash the modem only--it is pretty clearly marked in the modem thread in general
+1 on Gravity Box with Dan's ROM. GPE is far and away the smoothest, best performing ROM...proprietary drivers + AOSP leanness = smooth. The only thing I think comes close is Kantjer's SaberMod Slim (its in the international S4 forum general development--it is unified, though, and works fine with our S4).
Click to expand...
Click to collapse
Thanks for the quick replies guys-- OK, so my current baseband is ME7, to be correct. I'm going to try flashing the developer edition NC5 modem and see how that fares, and I also think I'm going to try Dan's GPE ROM (it's gotta be this one, right? derp) because Hyperdrive does feel a little bloated, and I'm not totally sold on TW-styling.
Do you think I'd expect any issues with TitaniumBackup from my Hyperdrive ROM to Dan's GPE? Apparently, people recommended you to re-install everything after upgrading to KitKat, which I failed to read before doing so... maybe I should take this approach instead of using Titanium to ensure stability. For the most part, Hyperdrive was stable and KitKat has been a noticeable performance improvement, but I was getting hot reboots occasionally.
Thanks again thesoldier and brizey:victory:
soad1789 said:
Thanks for the quick replies guys-- OK, so my current baseband is ME7, to be correct. I'm going to try flashing the developer edition NC5 modem and see how that fares, and I also think I'm going to try Dan's GPE ROM (it's gotta be this one, right? derp) because Hyperdrive does feel a little bloated, and I'm not totally sold on TW-styling.
Do you think I'd expect any issues with TitaniumBackup from my Hyperdrive ROM to Dan's GPE? Apparently, people recommended you to re-install everything after upgrading to KitKat, which I failed to read before doing so... maybe I should take this approach instead of using Titanium to ensure stability. For the most part, Hyperdrive was stable and KitKat has been a noticeable performance improvement, but I was getting hot reboots occasionally.
Thanks again thesoldier and brizey:victory:
Click to expand...
Click to collapse
Yup, that's the one. Just make sure you flash the Loki doki zip as well like the instructions say.
I would definitely go in with as little restores as possible, but generally it is fine to restore user apps and NOT system apps, as that will almost always cause an issue. I've restored plenty of user apps + data without issues, but if you do run into any, I'd start over fresh.
Also, I'm running the Dev NC5 modem and so far I feel like it's been the best for me. Just make sure you flash the modem only and not the one with nonhlos.
soad1789 said:
Thanks for the quick replies guys-- OK, so my current baseband is ME7, to be correct. I'm going to try flashing the developer edition NC5 modem and see how that fares, and I also think I'm going to try Dan's GPE ROM (it's gotta be this one, right? derp) because Hyperdrive does feel a little bloated, and I'm not totally sold on TW-styling.
Do you think I'd expect any issues with TitaniumBackup from my Hyperdrive ROM to Dan's GPE? Apparently, people recommended you to re-install everything after upgrading to KitKat, which I failed to read before doing so... maybe I should take this approach instead of using Titanium to ensure stability. For the most part, Hyperdrive was stable and KitKat has been a noticeable performance improvement, but I was getting hot reboots occasionally.
Thanks again thesoldier and brizey:victory:
Click to expand...
Click to collapse
Re: Titanium...I would restore data on anything that takes a while to set up. Frankly, I just restore everything, apps+data, and 99% of the time I have no issues. Heck, I have even moved games between devices using TiBU with no issues. But for a lot of stuff, the data is kind of irrelevant to restore.
The only issue with Dan's GPE is that some folks have some issues with data. I maybe have to cycle airplane mode once a week. But I am on wifi a ton--we have BYOD guest wifi at work, so I am not super dependent on data.
brizey said:
Re: Titanium...I would restore data on anything that takes a while to set up. Frankly, I just restore everything, apps+data, and 99% of the time I have no issues. Heck, I have even moved games between devices using TiBU with no issues. But for a lot of stuff, the data is kind of irrelevant to restore.
The only issue with Dan's GPE is that some folks have some issues with data. I maybe have to cycle airplane mode once a week. But I am on wifi a ton--we have BYOD guest wifi at work, so I am not super dependent on data.
Click to expand...
Click to collapse
Ah that is true, I sometimes have to toggle airplane mode to get data back, but it is rare. For example, I was on the subway last night and when I got off it wouldn't restore my data automatically so I had to cycle airplane mode. Going home though it came back automatically when I got off, so it doesn't happen all the time. Literally the only gripe I have, everything else is great.
Related
Hi friends,
Specs:
SCH-I545
Android 4.2.2
Baseband: I545VRUAMDK
Build Number: JDQ39.I545VRUAMDK
Rooted
I have a (what seems to be rare) rooted, stock ROM MDK Galaxy S4 running 4.2.2 (Jelly Bean?). Is there a way to update to Kit Kat (and keep root and my MDK status) so I can play with some of the ROMs I see? I know there are ROMs that apply a Kit Kat update (Hyperdrive RLS16 for ex) and I've tried flashing that, but I can't get any other ROMs to stick after that (Like CyanogenMod Nightlies... can't get that to take. What am I doing wrong??), and sadly there's some little glitches in Hyperdrive that are frustrating to me, so sticking with it is not something I want to do at this point.
I feel like I might get burned for asking this but I'm trying to approach this as methodically as possible and I can't seem to find, even with a good amount of searching through the Verizon G S4 forums, a straightforward explanation of how to do this, or if it's even possible. Am I approaching this in the wrong way or asking the wrong questions?? If so, can someone offer a simple explanation of why what I'm asking is not possible, or (more preferably) how I can approach it another way to get my Android Version updated but not lose root or the versatility that comes with managing to maintain my MDK status?
Thank you all for your help!
I'm not too familiar with aosp roms, but hyperdrive was my daily driver before moving on to the note 4. I last updated to hyperdrive rls 18.1 and it had been good to me. Rls 19 is having mixed reviews and never updated my phone to that version because if some minor glitches. I strongly recommend Rls 18.1. I had no issues with my mdk gs4.
onearmsysiphus said:
Hi friends,
Specs:
SCH-I545
Android 4.2.2
Baseband: I545VRUAMDK
Build Number: JDQ39.I545VRUAMDK
Rooted
I have a (what seems to be rare) rooted, stock ROM MDK Galaxy S4 running 4.2.2 (Jelly Bean?). Is there a way to update to Kit Kat (and keep root and my MDK status) so I can play with some of the ROMs I see? I know there are ROMs that apply a Kit Kat update (Hyperdrive RLS16 for ex) and I've tried flashing that, but I can't get any other ROMs to stick after that (Like CyanogenMod Nightlies... can't get that to take. What am I doing wrong??), and sadly there's some little glitches in Hyperdrive that are frustrating to me, so sticking with it is not something I want to do at this point.
I feel like I might get burned for asking this but I'm trying to approach this as methodically as possible and I can't seem to find, even with a good amount of searching through the Verizon G S4 forums, a straightforward explanation of how to do this, or if it's even possible. Am I approaching this in the wrong way or asking the wrong questions?? If so, can someone offer a simple explanation of why what I'm asking is not possible, or (more preferably) how I can approach it another way to get my Android Version updated but not lose root or the versatility that comes with managing to maintain my MDK status?
Thank you all for your help!
Click to expand...
Click to collapse
What recovery are you using? Clockwork or TWRP? What do you mean by the ROM isn't sticking? Are you getting stuck on a boot screen?
I'm using TWRP and flashed the Google Play Edition ROM which is on 4.4.4 Kitkat with root, I'm still on an MDK bootloader also.
OK, I'll keep that in mind, and thanks for the recommendation.
Any other thoughts on my questions about updating to 4.4.2?
To SkrillaKev - I'm using TWRP. I mean that after I flash Hyperdrive, I'm unable to get any other ROM to flash. It will fail in recovery (Eclipse) or will get stuck on the load screen (as with CynogenMod Nightlies)
I guess an easier question is - Can I flash any custom ROM that is made for 4.4.4 when I'm running 4.2.2??
I'll give the Google Edition ROM a go.
scrillakev said:
What recovery are you using? Clockwork or TWRP? What do you mean by the ROM isn't sticking? Are you getting stuck on a boot screen?
I'm using TWRP and flashed the Google Play Edition ROM which is on 4.4.4 Kitkat with root, I'm still on an MDK bootloader also.
Click to expand...
Click to collapse
Welp.... I wiped system/cache/dalvik and tried flashing Google Play Edition. got a yellow triangle and the message about having software not approved by Verizon and please report to the nearest Verizon store for bar-code tattooing and sterilization lol
Then I re-wiped sytem/cache/dalvik and tried flashing EclipseTW-S4-v4.0.2-KitKatNC5. Now I'm stuck on a boot screen...
At least when I screw something up I screw it up REALLY good.
onearmsysiphus said:
Welp.... I wiped system/cache/dalvik and tried flashing Google Play Edition. got a yellow triangle and the message about having software not approved by Verizon and please report to the nearest Verizon store for bar-code tattooing and sterilization lol
Then I re-wiped sytem/cache/dalvik and tried flashing EclipseTW-S4-v4.0.2-KitKatNC5. Now I'm stuck on a boot screen...
At least when I screw something up I screw it up REALLY good.
Click to expand...
Click to collapse
You got the yellow triangle and message because you have to flash the Loki zip after flashing the ROM . ...here ya go https://www.dropbox.com/s/3m3wclsx6ryynhg/loki-doki.zip?dl=0
heath2805 said:
You got the yellow triangle and message because you have to flash the Loki zip after flashing the ROM . ...here ya go https://www.dropbox.com/s/3m3wclsx6ryynhg/loki-doki.zip?dl=0
Click to expand...
Click to collapse
Many thanks!! I knew I was missing something but didn't have time to get back to that thread before I left work for the day. I'll give that a shot right meow
onearmsysiphus said:
Many thanks!! I knew I was missing something but didn't have time to get back to that thread before I left work for the day. I'll give that a shot right meow
Click to expand...
Click to collapse
No prob... Also I'd let it sit after flashing. You may have to select the correct APN: "Verizon Internet " and change mobile network to "LTE/ CDMA" and reboot. Should stick after that.
---------- Post added at 11:01 PM ---------- Previous post was at 10:52 PM ----------
Just realized this is in the development section lol This thread will probably get moved to Q&A
onearmsysiphus said:
Many thanks!! I knew I was missing something but didn't have time to get back to that thread before I left work for the day. I'll give that a shot right meow
Click to expand...
Click to collapse
Keep MDK!!!! After you flash a ROM. If it gets hung up on boot, hold volume up, home key and power key until the phone resets. Then let it boot up. Don't know why it happens but I have the same problem from time to time and rebooting seems to fix it. I've been using eclipse for 4or5 months now. It's pretty sick
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
149ThemedGoogleKeyboards!!!!!!
Friends don't let friends buy iPhones!
MyColorScreen
heath2805 said:
No prob... Also I'd let it sit after flashing. You may have to select the correct APN: "Verizon Internet " and change mobile network to "LTE/ CDMA" and reboot. Should stick after that.
Did that and it seems to be holding steady. Thanks for the tip there.
---------- Post added at 11:01 PM ---------- Previous post was at 10:52 PM ----------
Just realized this is in the development section lol This thread will probably get moved to Q&A
Click to expand...
Click to collapse
Ooops!! Well, hopefully it'll help someone else with noob problems like me.
Shaftamle said:
Keep MDK!!!! After you flash a ROM. If it gets hung up on boot, hold volume up, home key and power key until the phone resets. Then let it boot up. Don't know why it happens but I have the same problem from time to time and rebooting seems to fix it. I've been using eclipse for 4or5 months now. It's pretty sick
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
149ThemedGoogleKeyboards!!!!!!
Friends don't let friends buy iPhones!
MyColorScreen
Click to expand...
Click to collapse
Oh yes most definitely gonna keep MDK. It's magic lol
onearmsysiphus said:
Ooops!! Well, hopefully it'll help someone else with noob problems like me.
Oh yes most definitely gonna keep MDK. It's magic lol
Click to expand...
Click to collapse
Its also worth about $100 dollars more according to what they are selling for on swappa.
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
149ThemedGoogleKeyboards!!!!!!
Friends don't let friends buy iPhones!
MyColorScreen
InUh
Shaftamle said:
Keep MDK!!!! After you flash a ROM. If it gets hung up on boot, hold volume up, home key and power key until the phone resets. Then let it boot up. Don't know why it happens but I have the same problem from time to time and rebooting seems to fix it. I've been using eclipse for 4or5 months now. It's pretty sick
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
149ThemedGoogleKeyboards!!!!!!
Friends don't let friends buy iPhones!
MyColorScreen
Click to expand...
Click to collapse
you just have to make sure you have. Loki enabled recovery and you can pretty much flash anything here most of the roms have an MDKprocedure and all the information is still here for the old bootloader it is just not as common so you will have to look and older discussions as in not the first page there are several pages to each one of these sections if you look at the you can read through all the pages..the threads are organized in the latest they have been posted in so all your information is going to be considered old school until you get educated and then you just pop right into the current roms..I still have an s4 MKD 32...I gave to my significant because I refused to send it in on a trade and for my m8 upgrade on edge...btw I prefer phil recovery latest edition go to the phil thread and read toward the end and you'll find a link to his current inside the recovery in settings you can toggle Loki. Just leave it on.then it is just like any other unlocked phone.....and never flashed anything into this phone using ODIN unless its MDK ...or the latest radios... make sure you do your homework on whatever you are going to flash and Odin because it very well could contain a later bootloader and completely screw you. and the great thing is that we and other like us on MDK are the only ones that get to play with anything in the original development section....and in case you didn't know safestrap is for locked bootloaders not uswell technically we are still locked but Loki is the key. And that key only works on MDK bootloader.....and I'm sorry but I used hyperdrive before and the old lady that is now on the latest more than likely your problems with hyperdrive stem from not having flash the kernel properly in the proper recovery and not having the latest radios flashed to your device.
moderators please move to Q&A
onearmsysiphus said:
Hi friends,
Specs:
SCH-I545
Android 4.2.2
Baseband: I545VRUAMDK
Build Number: JDQ39.I545VRUAMDK
Rooted
I have a (what seems to be rare) rooted, stock ROM MDK Galaxy S4 running 4.2.2 (Jelly Bean?). Is there a way to update to Kit Kat (and keep root and my MDK status) so I can play with some of the ROMs I see? I know there are ROMs that apply a Kit Kat update (Hyperdrive RLS16 for ex) and I've tried flashing that, but I can't get any other ROMs to stick after that (Like CyanogenMod Nightlies... can't get that to take. What am I doing wrong??), and sadly there's some little glitches in Hyperdrive that are frustrating to me, so sticking with it is not something I want to do at this point.
I feel like I might get burned for asking this but I'm trying to approach this as methodically as possible and I can't seem to find, even with a good amount of searching through the Verizon G S4 forums, a straightforward explanation of how to do this, or if it's even possible. Am I approaching this in the wrong way or asking the wrong questions?? If so, can someone offer a simple explanation of why what I'm asking is not possible, or (more preferably) how I can approach it another way to get my Android Version updated but not lose root or the versatility that comes with managing to maintain my MDK status?
Thank you all for your help!
Click to expand...
Click to collapse
I have two suggestions:
First, make sure you flash the loki-doki.zip RIGHT AFTER you flash a new ROM in your zip queue, just like what was suggested previously.
Second, in case anything goes wrong, you should always have a current NANDROID backup first and this emergency wipe TAR on hand for Odin. There have been 4 separate times, in the span of about a week, that I gave myself the unauthorized software screen, and had to do this. So I would emergency wipe back to stock MDK, re-root, use Rashr to flash TWRP 2.7.1.0, and then I'd restore my NANDROID backup from my sd card. Rashr only works for flashing TWRP because only TWRP in that app is already Loki'd.
I'm still using RSL7 and it works great with no glitches I tried the newest one rsl20 and hated its look and didnt like any off the new features so i went back to RSL7, if you have not tried it you may want to, it is very different from RSL20 and imo way better.
Im not sure if this is the correct area to post this, so please feel free to move me if needed.
Im coming from NC5 HyperDrive release 19. Im realizing i dont use the majority it has to offer and would like a way to flash the stock version. It would be great if i could also remove the safestrap program. I am thinking about flashing a GPE rom and use xposed for what tweaks i do need, that way i have full control over what bloatware i have on my phone.
Any help would be appreciated
ShadyPossum said:
Im not sure if this is the correct area to post this, so please feel free to move me if needed.
Im coming from NC5 HyperDrive release 19. Im realizing i dont use the majority it has to offer and would like a way to flash the stock version. It would be great if i could also remove the safestrap program. I am thinking about flashing a GPE rom and use xposed for what tweaks i do need, that way i have full control over what bloatware i have on my phone.
Any help would be appreciated
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2287475
ShadyPossum said:
Im not sure if this is the correct area to post this, so please feel free to move me if needed.
Im coming from NC5 HyperDrive release 19. Im realizing i dont use the majority it has to offer and would like a way to flash the stock version. It would be great if i could also remove the safestrap program. I am thinking about flashing a GPE rom and use xposed for what tweaks i do need, that way i have full control over what bloatware i have on my phone.
Any help would be appreciated
Click to expand...
Click to collapse
yeah wrong subforum, but you need safestrap if youre gonna use a GPE rom simply because we can't flash a ROM any other way on this useless device. also, good luck. I'm stuck with HD until i try GPE again, I personally have not had a fully functional GPE ROM. Sure they run great but either WiFi, or data, or voice is broken at any given point. Hope they gives you an answer
fatapia said:
yeah wrong subforum, but you need safestrap if youre gonna use a GPE rom simply because we can't flash a ROM any other way on this useless device. also, good luck. I'm stuck with HD until i try GPE again, I personally have not had a fully functional GPE ROM. Sure they run great but either WiFi, or data, or voice is broken at any given point. Hope they gives you an answer
Click to expand...
Click to collapse
I'm running the Pure Nexus ROM from this thread and have had few issues. Only notable problem so far is phantom vibrations sometimes. This is the most stable Safestrap compatible GPE ROM I've found.
06sharpshot said:
I'm running the Pure Nexus ROM from this thread and have had few issues. Only notable problem so far is phantom vibrations sometimes. This is the most stable Safestrap compatible GPE ROM I've found.
Click to expand...
Click to collapse
I see this is in the AT&T forum. If i flash this on a verizon build, will it be stable?
Been away from the development section because I'm so far satisfied with stock rooted by beanstown. I know the dev took off but I wanted to ask if there are any other ROMs completely or mostly stock running the latest VZW update. His is running 11c before he left but I don't have the advanced calling features of the newest update. Any help?
SkyDragon - http://forum.xda-developers.com/ver...9-skydragon-g3-vs985-kvt49l-vs98512b-t2967868
Jasmine - http://forum.xda-developers.com/verizon-lg-g3/development/rom-jasminerom-v1-0-t2904641
Eclipse (if you want a little AOSP mix with stock) - http://forum.xda-developers.com/ver...rom-eclipse-g3-v0-2-12b-1-19-15-time-t3007306
I've been using SkyDragon as my daily for stock while I test some other things. Haven't used either of the other 2 but I don't think you could go wrong with either. Both should be pretty solid.
Good post I'll try them out. Thanks
They're on the newest OTA?
Yes. All are based on 12b
06stang said:
Good post I'll try them out. Thanks
They're on the newest OTA?
Click to expand...
Click to collapse
I have to say, I'm a huge AOSP fan personally, but I've been running Eclipse for a while and it has a very nice mix of stock stability and AOSP styling. One day I even somehow managed 5 hours of screen on time and was still at 25% battery lol....most days closer to 4 hours and totally dead lol, but overall great rom!
For stock rom, I swear by Jasmine. It's fantastic and I've been using it for months.
CondemnedSoul said:
Yes. All are based on 12b
Click to expand...
Click to collapse
they are based on 12b but do they have the 12b modem? That is a separate flash I think.
---------- Post added at 08:04 AM ---------- Previous post was at 08:00 AM ----------
06stang said:
Been away from the development section because I'm so far satisfied with stock rooted by beanstown. I know the dev took off but I wanted to ask if there are any other ROMs completely or mostly stock running the latest VZW update. His is running 11c before he left but I don't have the advanced calling features of the newest update. Any help?
Click to expand...
Click to collapse
There's a twrp flashable stock, rooted 12b rom. The 12b modem is a separate flash.
Yeah I figured the modem would be separate as usual.
Tried Jasmine but had to switch back. Fresh install but kept getting random app closings, shadows on the home screen like I had icons were there were none, and the screen jumped around randomly. MD5 checked out on the downloads.
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