Related
I've been running CyanogenMod 11 for about a month now. I like it a lot, however there are instabilities. Youtube cannot play videos at all, for example; Snapchat totally fails to work; and one or two apps I've tried to install wouldn't even open. Occasionally a program will crash with a "Such-and such service has stopped" error notice.
Can anyone suggest a more stable ROM? I'm a newbie to flashing, I'm not experienced or interested in trying out different ROMs. I'm not a power user, I just want a stable, reliable ROM. Is cm11 known to have the issues I'm experiencing? Can anyone suggest an alternative?
Thanks.
AidanBell said:
I've been running CyanogenMod 11 for about a month now. I like it a lot, however there are instabilities. Youtube cannot play videos at all, for example; Snapchat totally fails to work; and one or two apps I've tried to install wouldn't even open. Occasionally a program will crash with a "Such-and such service has stopped" error notice.
Can anyone suggest a more stable ROM? I'm a newbie to flashing, I'm not experienced or interested in trying out different ROMs. I'm not a power user, I just want a stable, reliable ROM. Is cm11 known to have the issues I'm experiencing? Can anyone suggest an alternative?
Thanks.
Click to expand...
Click to collapse
megalomanic14's MegaFire ROM works great. http://forum.xda-developers.com/showthread.php?t=2608110
AidanBell said:
I've been running CyanogenMod 11 for about a month now. I like it a lot, however there are instabilities. Youtube cannot play videos at all, for example; Snapchat totally fails to work; and one or two apps I've tried to install wouldn't even open. Occasionally a program will crash with a "Such-and such service has stopped" error notice.
Can anyone suggest a more stable ROM? I'm a newbie to flashing, I'm not experienced or interested in trying out different ROMs. I'm not a power user, I just want a stable, reliable ROM. Is cm11 known to have the issues I'm experiencing? Can anyone suggest an alternative?
Thanks.
Click to expand...
Click to collapse
Since cm-11.0 for this device is not in nightlies major bugs should be expected. Sorry, I don't have a suggestion, but I have a question. Does the headphone jack work on cm11?
interloper said:
Since cm-11.0 for this device is not in nightlies major bugs should be expected. Sorry, I don't have a suggestion, but I have a question. Does the headphone jack work on cm11?
Click to expand...
Click to collapse
Yes, the headphone jack works fine.
I've made the decision to return to the official Samsung ROM, so if anybody could point me in the direction of a safe, reliable download for that I'd be very grateful.
Incidentally, what's "nightlies "?
AidanBell said:
Yes, the headphone jack works fine.
I've made the decision to return to the official Samsung ROM, so if anybody could point me in the direction of a safe, reliable download for that I'd be very grateful.
Incidentally, what's "nightlies "?
Click to expand...
Click to collapse
Nightly is the first "Official" status of a device from CM. If the device is very stable, with all system working properly and with minimal buggy behaviors CM begins building the ROM officially as a "Nightly" assuming the dev is following best practices etc.
AidanBell said:
Yes, the headphone jack works fine.
I've made the decision to return to the official Samsung ROM, so if anybody could point me in the direction of a safe, reliable download for that I'd be very grateful.
Incidentally, what's "nightlies "?
Click to expand...
Click to collapse
I don't think that anyone has the stock rom for the Mega(s) yet, waiting patiently for the guys upstairs to crack the bootloader.
however you might try to restore with Kies.
Unicorn69 said:
I don't think that anyone has the stock rom for the Mega(s) yet, waiting patiently for the guys upstairs to crack the bootloader.
however you might try to restore with Kies.
Click to expand...
Click to collapse
You are not right, I for instance have stock ROM on my Mega and I am quite satisfied... Ohhh, maybe I'm a little lying... :silly: it is MegaFireMj2V5 from megalomanic14 which is based upon a stock ROM but is greatly improved - if you are looking for alternative to stock or CM11 rom's it's worth a shot.
As for return to stock ROM - be careful to choose right version: all new firmware (beginning from CNA1) are 'enhanced' with new bootloader and Samsung KIES which is new security system. If you upgrade your Mega by Kies or by Odin with newest firmware you will be lacked possibility to downgrade AND every attempt to root or flash custom recovery will result in tipping flashing counter without any possibility to clear it. So be extremely cautious if you want to mod your Mega with no problems.
You can choose older firmware on Sammobile an flash it thru Odin - then you will have fresh stock ROM on your unit. There are many tutorials how to do it.
trurl3 said:
You are not right, I for instance have stock ROM on my Mega and I am quite satisfied... Ohhh, maybe I'm a little lying... :silly: it is MegaFireMj2V5 from megalomanic14 which is based upon a stock ROM but is greatly improved - if you are looking for alternative to stock or CM11 rom's it's worth a shot.
As for return to stock ROM - be careful to choose right version: all new firmware (beginning from CNA1) are 'enhanced' with new bootloader and Samsung KIES which is new security system. If you upgrade your Mega by Kies or by Odin with newest firmware you will be lacked possibility to downgrade AND every attempt to root or flash custom recovery will result in tipping flashing counter without any possibility to clear it. So be extremely cautious if you want to mod your Mega with no problems.
You can choose older firmware on Sammobile an flash it thru Odin - then you will have fresh stock ROM on your unit. There are many tutorials how to do it.
Click to expand...
Click to collapse
Many thanks, guys.
I've been on Sammobile and selected "I9205XXUCNA2_I9205BTUCNA1_BTU.zip", which I intend to install in the next couple of hours unless anyone on here screams at me that I shouldn't! I'm in the UK with a GT-i9250, so I believe that's the right version for me.
To be honest, I'm not worried about tipping the flashing counter (if I even understand properly what that means). I rooted my phone some time ago, and liked that. Two weeks ago I decided to try Cyanogenmod since I've never used a different ROM. I wasn't impressed, and have decided I want to go back to Samsung original. If, in the process, I prevent myself from ever being able to flash another alternative ROM, or I void the phone's warrenty in any way, I can live with that.
AidanBell said:
Many thanks, guys.
I've been on Sammobile and selected "I9205XXUCNA2_I9205BTUCNA1_BTU.zip", which I intend to install in the next couple of hours unless anyone on here screams at me that I shouldn't! I'm in the UK with a GT-i9250, so I believe that's the right version for me.
To be honest, I'm not worried about tipping the flashing counter (if I even understand properly what that means). I rooted my phone some time ago, and liked that. Two weeks ago I decided to try Cyanogenmod since I've never used a different ROM. I wasn't impressed, and have decided I want to go back to Samsung original. If, in the process, I prevent myself from ever being able to flash another alternative ROM, or I void the phone's warrenty in any way, I can live with that.
Click to expand...
Click to collapse
OK, it's your choice... in fact newest firmware do not offer nothing new but bootloder without return and KNOX. CNA2 it's firmware with KNOX embedded. For mundane user this means nothing special, but for somebody who plan to root and mod it could be pain in... Try to read a little about rooting firmware with KNOX... but as I said, you are warned... tipping counter means setting flag which shows to e.g. service so there was installed unofficial software and it means so you are lacking your warranty. With firmware with KNOX this is irreversible because setting such flag physically burns efuse in system making hardware change. Cheers...
I stay on firmware without KNOX because of possibility to change ROMs and easy install custom software. Waiting for KK which for sure will have 'new type' bootloader and then will be no choice...
trurl3 said:
OK, it's your choice... in fact newest firmware do not offer nothing new but bootloder without return and KNOX. CNA2 it's firmware with KNOX embedded. For mundane user this means nothing special, but for somebody who plan to root and mod it could be pain in... Try to read a little about rooting firmware with KNOX... but as I said, you are warned... tipping counter means setting flag which shows to e.g. service so there was installed unofficial software and it means so you are lacking your warranty. With firmware with KNOX this is irreversible because setting such flag physically burns efuse in system making hardware change. Cheers...
I stay on firmware without KNOX because of possibility to change ROMs and easy install custom software. Waiting for KK which for sure will have 'new type' bootloader and then will be no choice...
Click to expand...
Click to collapse
You make a good case, and perhaps I should install an earlier version, then. Thanks. However, I've looked on Sammobile and they seem to offer only the latest version. Where can I download an earlier KNOX-free version, please?
trurl3 said:
OK, it's your choice... in fact newest firmware do not offer nothing new but bootloder without return and KNOX. CNA2 it's firmware with KNOX embedded. For mundane user this means nothing special, but for somebody who plan to root and mod it could be pain in... Try to read a little about rooting firmware with KNOX... but as I said, you are warned... tipping counter means setting flag which shows to e.g. service so there was installed unofficial software and it means so you are lacking your warranty. With firmware with KNOX this is irreversible because setting such flag physically burns efuse in system making hardware change. Cheers...
I stay on firmware without KNOX because of possibility to change ROMs and easy install custom software. Waiting for KK which for sure will have 'new type' bootloader and then will be no choice...
Click to expand...
Click to collapse
Like you,i still stay on old firmware,new firmware have knox,knox make your phone brick if you root.
rizky123 said:
Like you,i still stay on old firmware,new firmware have knox,knox make your phone brick if you root.
Click to expand...
Click to collapse
Agreed. You guys have convinced me that I should be flashing an old version of Samsung, not the latest with KNOX. But I can only do that if I can find one! Can anyone please point me in the right direction?
AidanBell said:
You make a good case, and perhaps I should install an earlier version, then. Thanks. However, I've looked on Sammobile and they seem to offer only the latest version. Where can I download an earlier KNOX-free version, please?
Click to expand...
Click to collapse
Hmmm, you are right... In such case i recommend you to install custom ROM MegaFireMJ2V6 made by megalomanic14 on basis stock MJ2 which you can find HERE.
Actually I am using this ROM and can say it is very good - looks like stock but is much faster. It's rooted already. Version X offer firmware stripped from unneeded apps to the extent.
trurl3 said:
Hmmm, you are right... In such case i recommend you to install custom ROM MegaFireMJ2V6 made by megalomanic14 on basis stock MJ2 which you can find HERE.
Actually I am using this ROM and can say it is very good - looks like stock but is much faster. It's rooted already. Version X offer firmware stripped from unneeded apps to the extent.
Click to expand...
Click to collapse
Thank you very much. Most of that sentences was Greek to me, but I get the idea! The truth is, I put my foot into the water of flashing custom ROMS, and decided it wasn't for me. I just want one, reliable ROM that I can live with for many months without having to change it. That's why I decided to go back to Samsung, because there were too many bugs in Cyanogenmod and I don't want to start testing one ROM after the next. I just want to install a reliable, bug-free ROM now, and have done with it. So you think that MegaFireMJ2V6 would be such a ROM in my case?
PS:
It seems MegaFireMJ2V6 can't be downloaded from that link anyway?
Type your phone model in the link below and choose the one you want. Create a free account if you need faster download speeds.
http://www.sammobile.com/firmwares/
Silesh.Nair said:
Type your phone model in the link below and choose the one you want. Create a free account if you need faster download speeds.
http://www.sammobile.com/firmwares/
Click to expand...
Click to collapse
Thank you, but I've tried this several times, and the only download available is the most recent.
You are wrong. It shows all the firmwares released for a model. I can see all the releases for GT-I9200. Attached is a screenshot of the older firmware without knox....
As far as I understand it, these are all the same ROM, simply different versions for different countries. When I put in my phone, GT-i9250, I am presented with a similar page, but it's only the one ROM; 4.2.2 with KNOX.
Ok man, I am done trying to explain things to you. The list you showed only displays Knox firmware, but what you said is not true. Here is another site with older firmware displayed for the I9205. There is no I9250 model Mega afaik..
Silesh.Nair said:
Ok man, I am done trying to explain things to you. The list you showed only displays Knox firmware, but what you said is not true. Here is another site with older firmware displayed for the I9205. There is no I9250 model Mega afaik..
Click to expand...
Click to collapse
I apologise if I have offended you in any way, that certainly wasn't my intention. I'm simply new to all of this and don't understand it well. I appreciate the new link, and thank you for your help.
Hi everyone! I need some help updating my S4. I rooted it awhile back and I'm very much of the mindset of "if it ain't broke, don't fix it," so since it was doing everything I wanted, I've just left it alone and kept dismissing the prompt to install the OTA update. Now I'm having some issues and want some features of the newer versions of Android, so I was looking around for the best way to update it while keeping my root access. All the guides I can find, however, talk about upgrading from 4.3 to 4.4 or 4.2 to 4.3. So I was wondering...
1. What version should I update to? On my last phone, a Droid Bionic, one of the big Android version updates ran so horribly on it that I ended up getting a new phone. Because of that, I'm very nervous about updating my phone and having the performance suffer.
2. There must be a way to go straight from 4.2.2 to whatever version I choose, right? Do I need to go dig up some old guides on how to update my phone so that the most recent guides are relevant?
I hope I'm not being a super noob about this. I tried Googling around, and I'm pretty tech savvy but just haven't had the time to keep up with recent developments, so some guidance would be very helpful!
About my phone:
Verizon Galaxy S4
Model #: SCH-I545
Android version: 4.2.2
Baseband version: I545VRUDMI1
Thanks so much!
Find out what base band you have, MDK, ME7?
If MDK, install recovery download rom.
Anything other check this thread out:
http://forum.xda-developers.com/showthread.php?t=2735172
Advice, better read about the bugs and issues each version has. Once you go up, you cannot go back. Not ever, no never.
Sent from my SCH-I545 using XDA Free mobile app
Well if he is one of those few lucky MDK people he could hop around versions as he please. But most of them already know that *Grin*
Sent from my SCH-I545 using XDA Free mobile app
Batttie said:
Find out what base band you have, MDK, ME7?
If MDK, install recovery download rom.
Anything other check this thread out:
http://forum.xda-developers.com/showthread.php?t=2735172
Advice, better read about the bugs and issues each version has. Once you go up, you cannot go back. Not ever, no never.
Click to expand...
Click to collapse
I put the baseband version of my phone in my original post. It's I545VRUDMI1. Or am I missing something? So that means I should use Odin to flash whatever rom I decide to go with, right? So if I went with something like this 4.4.4 Google Play Edition I can use Odin to put it on my device? But then if I decide I don't like that rom for whatever reason, I can't redo it with any roms based on an earlier version (4.4.2, 4.3, etc), but other 4.4.4 roms would work?
Thanks so much for the help!
Toubabi said:
I put the baseband version of my phone in my original post. It's I545VRUDMI1. Or am I missing something? So that means I should use Odin to flash whatever rom I decide to go with, right? So if I went with something like this 4.4.4 Google Play Edition I can use Odin to put it on my device? But then if I decide I don't like that rom for whatever reason, I can't redo it with any roms based on an earlier version (4.4.2, 4.3, etc), but other 4.4.4 roms would work?
Thanks so much for the help!
Click to expand...
Click to collapse
You need a custom recovery to flash that Play Edition ROM which is not possible with your MI1 baseband.
dodgingpixels said:
You need a custom recovery to flash that Play Edition ROM which is not possible with your MI1 baseband.
Click to expand...
Click to collapse
So how do I know/find which roms will work?
Toubabi said:
So how do I know/find which roms will work?
Click to expand...
Click to collapse
Here's a pretty good thread explaining the different basebands.
http://forum.xda-developers.com/showthread.php?t=2578569
OK, I think I'm starting to get it. So should I use Odin to flash the rom listed under "Recover by re-flashing stock" in this thread? Or should I use safestrap? What's the difference?
I'm helping my friend install CyanogenMod 12 on his S4 (jfltevzw). We've rooted it and we're currently doing a full backup through Safestrap in case anything happens. Once that's finished, I'm unsure as to what we should do. CyanogenMod's wiki has installation instructions for the Verizon S4, but it says in big bold letters to not attempt this if on a ROM newer than I545VRUAMDK. He's on the latest version that Samsung/Verizon have pushed out, which is I545VRUFNK1. Is there an alternate way to install CyanogenMod on top of the newer stock ROM, or is it not possible?
vaindil said:
I'm helping my friend install CyanogenMod 12 on his S4 (jfltevzw). We've rooted it and we're currently doing a full backup through Safestrap in case anything happens. Once that's finished, I'm unsure as to what we should do. CyanogenMod's wiki has installation instructions for the Verizon S4, but it says in big bold letters to not attempt this if on a ROM newer than I545VRUAMDK. He's on the latest version that Samsung/Verizon have pushed out, which is I545VRUFNK1. Is there an alternate way to install CyanogenMod on top of the newer stock ROM, or is it not possible?
Click to expand...
Click to collapse
its not possible. ONLY mdk builds will work.
Raymondlikesroot said:
its not possible. ONLY mdk builds will work.
Click to expand...
Click to collapse
Dang, so there's absolutely nothing whatsoever that can be done? The page says you can't downgrade, but is anything at all possible now that he's beyond the MDK build? He really wants to make the switch and is fine with doing a complete wipe or whatever is necessary.
EDIT: I've been trying to read up on the VZW S4 and why this isn't possible, but I don't quite get it. Reading other threads it seems like the reason is because the bootloader is locked, but that can't be the case if he was able to install Safestrap. I'm coming from a Nexus 5 where everything is incredibly simple, so I apologize for my ignorance. (I don't mean to say you're wrong or anything as I have no idea myself, I just don't understand why it doesn't work on newer ROMs.)
vaindil said:
Dang, so there's absolutely nothing whatsoever that can be done? The page says you can't downgrade, but is anything at all possible now that he's beyond the MDK build? He really wants to make the switch and is fine with doing a complete wipe or whatever is necessary.
EDIT: I've been trying to read up on the VZW S4 and why this isn't possible, but I don't quite get it. Reading other threads it seems like the reason is because the bootloader is locked, but that can't be the case if he was able to install Safestrap. I'm coming from a Nexus 5 where everything is incredibly simple, so I apologize for my ignorance. (I don't mean to say you're wrong or anything as I have no idea myself, I just don't understand why it doesn't work on newer ROMs.)
Click to expand...
Click to collapse
The reason we use Safestrap as opposed to twrp is because the bootloader is locked.
Surge1223 said:
The reason we use Safestrap as opposed to twrp is because the bootloader is locked.
Click to expand...
Click to collapse
Oh, okay. Really unfortunate that this isn't possible now. So he's just stuck with TouchWiz and can't do anything about it?
vaindil said:
Oh, okay. Really unfortunate that this isn't possible now. So he's just stuck with TouchWiz and can't do anything about it?
Click to expand...
Click to collapse
Yep
Sent from my my Lollipopped S4
vaindil said:
Oh, okay. Really unfortunate that this isn't possible now. So he's just stuck with TouchWiz and can't do anything about it?
Click to expand...
Click to collapse
you can install hyperdrive rom
its not lolipop but its worlds better then stock ...
also there is a chance of getting the 5.01 GPE edition rom running when Samsung releases the lolipop update for the vz s4
that would at least give us a working lolipop kernel to use with the gpe rombase
and hey you never know there could be a exploite in the lolipop rom/kernel that lets us get kexec working
Basically safestrap loads after the kernel but early enough to replace point to a different root for the system. So we can load what ever system we want... But are stuck with the kernel the phone booted. If the system is based on the stock kernel this is fine... But when it starts making calls to custom kernel stuff you will have trouble.
So Cyanogenmod only provides the GUI? I've installed CM on two B&N tablets and I've been asked to root a new Verizon Samsung Galaxy S4. I've assumed that, because it's new, it will have I545VRUFNK1 4.4.2. I rooted my VSG s3 years ago to 4.3 and there was no going back on that one. It looks like it's the same with VSG s4. So, if CM provides only the GUI, then a rooted VSG s4 can still access Google Apps? What is the concern with with TW based ROMs? Is it the recovery/backup feature or only being stuck with the VSG s4 GUI?
Raymondlikesroot said:
its not possible. ONLY mdk builds will work.
Click to expand...
Click to collapse
This explains why I bricked my phone when I tried to flash CM12...
ryant35 said:
This explains why I bricked my phone when I tried to flash CM12...
Click to expand...
Click to collapse
haha yeah, that could maybe potentially probably be the issue. Just maybe.
Couldn't you ODIN back to an older baseband version and then try to flash CM12?
Lockett said:
Couldn't you ODIN back to an older baseband version and then try to flash CM12?
Click to expand...
Click to collapse
Nope, in order to get CM, you'll need to be on MDK. Samsung prevents downgrading.
btw. the baseband version doesn't matter much. Its the bootloader version that is the toughie.
Boo! I just picked up my S4 yesterday after a 5 month run of using Windows Phone so I'm trying to figure this phone out. I'm on NK1 and trying to figure out how to root now.
vaindil where did you find a VRUFNK1 compatible version of Safestrip?
I have the note edge, still on kit Kat, it's rooted. But it's got a stock rom. I was thinking about upgrading to lollipop, but read I'd have to unroot kitkat, install the official lollipop, then root lollipop?
Are there step by step instructions, or maybe even an easier way out there?
I miss the days when we could just flash radio updates and any rom we wanted without doing anything else. Ha.
http://forum.xda-developers.com/showthread.php?t=2943993
primo523 said:
http://forum.xda-developers.com/showthread.php?t=2943993
Click to expand...
Click to collapse
Thanks but that thread is for T-mobile?
You have to Odin back to stock firmware. .. Let the OTA take place then re-root ..
Werd.
primo523 said:
You have to Odin back to stock firmware. .. Let the OTA take place then re-root ..
Click to expand...
Click to collapse
I assume that this hasn't changed at all?
OK2 isn't rooted yet, so flash the OG1 stock rom for lollipop and root that one. Don't take the OTA though cause you'll lose root.
Sent from my SM-N915P using Tapatalk
DevXen said:
I have the note edge, still on kit Kat, it's rooted. But it's got a stock rom. I was thinking about upgrading to lollipop, but read I'd have to unroot kitkat, install the official lollipop, then root lollipop?
Are there step by step instructions, or maybe even an easier way out there?
I miss the days when we could just flash radio updates and any rom we wanted without doing anything else. Ha.
Click to expand...
Click to collapse
Would you happen to have a nandroid of your KitKat have a friend who's battery can hardly last the day due to the constatnt drain issue on 5.1.1
cRiMiNaL_Genius said:
Would you happen to have a nandroid of your KitKat have a friend who's battery can hardly last the day due to the constatnt drain issue on 5.1.1
Click to expand...
Click to collapse
I'm sure I do somewhere. But it isn't a fresh install. It has my hacks and my own settings and my everything including any personal info they it stores? I. E. Google wallet info and lte encryption keys.
Thats no problem if you're still on KitKat make a new backup excluding the data and cache partitions, hopefully thas not too much for a friendly request lol
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.