Related
http://forum.xda-developers.com/showthread.php?t=2472301
i have too many times try download the file but when i check the md5 i see that is different
i'm portuguese and a noob, but i love try new custom roms, but since 4.4 updated, i'm stuck, pls help
thanks in advance
It is possible that the newest MD5 has not been updated yet.
EDIT: Checksum I got from X-Note_Aroma_Build_9.0_NA7_KitKat_Public Matches fine.
294A97B7C4F4BCBF385318B6176D9596
radicalisto said:
It is possible that the newest MD5 has not been updated yet.
EDIT: Checksum I got from X-Note_Aroma_Build_9.0_NA7_KitKat_Public Matches fine.
294A97B7C4F4BCBF385318B6176D9596
Click to expand...
Click to collapse
So i have to try and try until the download file matches with md5?
Another question, do i have to update stock firmware to MBMENA7 before install the new rom v9 NA7?
Markudsc said:
So i have to try and try until the download file matches with md5?
Another question, do i have to update stock firmware to MBMENA7 before install the new rom v9 NA7?
Click to expand...
Click to collapse
Well it's supposed to match, but I never ever check my downloads..
Yes you need to update to Stock first before flashing (NA6 is OK no need for NA7)
radicalisto said:
Well it's supposed to match, but I never ever check my downloads..
Yes you need to update to Stock first before flashing (NA6 is OK no need for NA7)
Click to expand...
Click to collapse
Thanks a lot
but this only happen with the x note custom roms, :-$
I'm using the bobcatrom v4.1 actually, would be because of that?
only with the stock firmware which we can install de x note rom?
I would like very much if i can install the rom.
:-$
Markudsc said:
Thanks a lot
but this only happen with the x note custom roms, :-$
I'm using the bobcatrom v4.1 actually, would be because of that?
only with the stock firmware which we can install de x note rom?
I would like very much if i can install the rom.
:-$
Click to expand...
Click to collapse
Try flashing it even if the MD5 doesn't match, just have another ROM ready in case it doesn't work. Might just be an anomly that is causing the checksum issues.
radicalisto said:
Try flashing it even if the MD5 doesn't match, just have another ROM ready in case it doesn't work. Might just be an anomly that is causing the checksum issues.
Click to expand...
Click to collapse
I have the bobcatrom just i said for precaution. But i have tried 3 times until now and the result is always the same.
but i will try to do this
Install the stock firmware of polland NA6 with the bootloader update checked
intall a cwm compatible with kk
no using cf-root just i see the xnote rom is prerooted
Download again just to eliminate doubts
and then try to install one more time the xnote v9 NA7,
THANKS FOR YOUR ATTENTION
Muito obrigado pela atenção,
(In portuguese ^^^)
try turning off firewall/anti virus
Markudsc said:
I have the bobcatrom just i said for precaution. But i have tried 3 times until now and the result is always the same.
but i will try to do this
Install the stock firmware of polland NA6 with the bootloader update checked
intall a cwm compatible with kk
no using cf-root just i see the xnote rom is prerooted
Download again just to eliminate doubts
and then try to install one more time the xnote v9 NA7,
THANKS FOR YOUR ATTENTION
Muito obrigado pela atenção,
(In portuguese ^^^)
Click to expand...
Click to collapse
Can't hurt to root, if x-note doesn't flash you may need to anyway....
ultramag69 said:
Can't hurt to root, if x-note doesn't flash you may need to anyway....
Click to expand...
Click to collapse
Do you have the x-note rom v9?
what do you do previously before intall the rom v9 NA7?
What rom you had before?
pls explain to me step by step just for me could to see what i am doing wrong and correct my self, :-$
Thanks in advance
Markudsc said:
Do you have the x-note rom v9?
what do you do previously before intall the rom v9 NA7?
What rom you had before?
pls explain to me step by step just for me could to see what i am doing wrong and correct my self, :-$
Thanks in advance
Click to expand...
Click to collapse
Upgrade to Stock Kitkat via Odin > Flash a custom Recovery > download custom ROM > flash via custom Recovery.
radicalisto said:
Upgrade to Stock Kitkat via Odin > Flash a custom Recovery > download custom ROM > flash via custom Recovery.
Click to expand...
Click to collapse
I usually add Upgrade to Stock Kitkat via Odin >Root with cf-autoroot > Flash a custom Recovery > download custom ROM > flash via custom Recovery.
But thats because I need root and want to make sure my phone has rooted properly.....
Oh, and make sure the KK you flash ISN'T a branded rom - supplied by a foreign carrier as this can cause problems and may fail near end of ODIN flash...
No need to root when flashing a recovery :good:
EDIT: Re-Read your reasoning for doing so!
ultramag69 said:
I usually add Upgrade to Stock Kitkat via Odin >Root with cf-autoroot > Flash a custom Recovery > download custom ROM > flash via custom Recovery.
But thats because I need root and want to make sure my phone has rooted properly.....
Oh, and make sure the KK you flash ISN'T a branded rom - supplied by a foreign carrier as this can cause problems and may fail near end of ODIN flash...
Click to expand...
Click to collapse
Hi again,
I will try those steps of the official XEO Polland NA6 stock firmware and next I will post the result
I will be so graceful if I will succeded, that ROM is AWESOME,
Markudsc said:
Hi again,
I will try those steps of the official XEO Polland NA6 stock firmware and next I will post the result
I will be so graceful if I will succeded, that ROM is AWESOME,
Click to expand...
Click to collapse
Just make sure you have the latest cf-autoroot and that the CWM you install is greater than version 4.0.4.6... These are KK friendly, anything else will cause issues...
ultramag69 said:
I usually add Upgrade to Stock Kitkat via Odin >Root with cf-autoroot > Flash a custom Recovery > download custom ROM > flash via custom Recovery.
But thats because I need root and want to make sure my phone has rooted properly.....
Oh, and make sure the KK you flash ISN'T a branded rom - supplied by a foreign carrier as this can cause problems and may fail near end of ODIN flash...
Click to expand...
Click to collapse
How can I see if the KK I flash isn't a branded rom or not?
I'm using the cwm 6.0.4.7 (it said friendly KK )I think so, I no longer near my pc but I will confirm that later.
Use XEO (Poland) KK which is unbranded
HERE'S a fast link for it.
I am new to flashing so sorry if I have asked some stupid questions.
I have SGH-I337 (ATT) and would like to root and then maybe install Cyanogenmod or any other custom ROM.
Device Details:
Baseband - NC1
Build No. - NC1
Android Version - 4.4.2
I tried to root NC1 directly using motochopper. Then I read and I am now trying to downgrade.
I have got ODIN 3.09 but it does not say support to I337. I have gone through Noob Helper
I have downloaded all zips from Downgrade
After reading the article of Modems; I got confused about my bootloader.
I also have gone through the thread but after that confusion, I did not proceed ahead.
Could anyone please help me?
How to identify boot-loader?
Which ODIN to use or do I need to use SAFETRAP (not sure if bootloader is MF3) ?
mayurd said:
I am new to flashing so sorry if I have asked some stupid questions.
I have SGH-I337 (ATT) and would like to root and then maybe install Cyanogenmod or any other custom ROM.
Device Details:
Baseband - NC1
Build No. - NC1
Android Version - 4.4.2
I tried to root NC1 directly using motochopper. Then I read and I am now trying to downgrade.
I have got ODIN 3.09 but it does not say support to I337. I have gone through Noob Helper
I have downloaded all zips from Downgrade
After reading the article of Modems; I got confused about my bootloader.
I also have gone through the thread but after that confusion, I did not proceed ahead.
Could anyone please help me?
How to identify boot-loader?
Which ODIN to use or do I need to use SAFETRAP (not sure if bootloader is MF3) ?
Click to expand...
Click to collapse
Dont worry about Odin saying the device is i9505 or so. The flash will work.
For samsung phones running full stock firmware, all the components have the same version. Since your build is NC1, your bootloader is also NC1.
You are in the right track. Follow the downgrade thread to partial downgrade to MK2. Then use saferoot to root. Then install safestrap v3.72. Then use the deadly venom kitkat magic tool to install any kitkat rom of your choice from this list (post 3).
You cannot install any AOSP based rom. So, no CM. Even google play edition roms dont work.
You can install AOSP themed roms (like BlackBox3.0)
jmjoyas said:
Dont worry about Odin saying the device is i9505 or so. The flash will work.
For samsung phones running full stock firmware, all the components have the same version. Since your build is NC1, your bootloader is also NC1.
You are in the right track. Follow the downgrade thread to partial downgrade to MK2. Then use saferoot to root. Then install safestrap v3.72. Then use the deadly venom kitkat magic tool to install any kitkat rom of your choice from this list (post 3).
You cannot install any AOSP based rom. So, no CM. Even google play edition roms dont work.
You can install AOSP themed roms (like BlackBox3.0)
Click to expand...
Click to collapse
Thank you for the response. I have downgraded to MK2 and have done the root.
I was wondering if you could tell me if it is possible to install Liquid Smooth ROM. I have seen the video and I have downloaded from here which says S4 unified. Also, there are some videos claiming CM on S4.
Could anyone please help on the same?
mayurd said:
Thank you for the response. I have downgraded to MK2 and have done the root.
I was wondering if you could tell me if it is possible to install Liquid Smooth ROM. I have seen the video and I have downloaded from here which says S4 unified. Also, there are some videos claiming CM on S4.
Could anyone please help on the same?
Click to expand...
Click to collapse
As already stated, no AOSP based roms will work (ROMs that are built by compiling AOSP code). Only TouchWiz based roms will work. If you need AOSP look and feel, you can install an AOSP themed rom.
CM/AOSP on ATT S4 is only possible if you have the MDB/MDL bootloader. Anything above that, it wont work.
jmjoyas said:
As already stated, no AOSP based roms will work (ROMs that are built by compiling AOSP code). Only TouchWiz based roms will work. If you need AOSP look and feel, you can install an AOSP themed rom.
CM/AOSP on ATT S4 is only possible if you have the MDB/MDL bootloader. Anything above that, it wont work.
Click to expand...
Click to collapse
Sorry for the repeated questions.
I tried to update through Safestrap with BlackBox. But I got stuck on the boot screen where it shows Samsung Logo. I might have done something wrong. I just clicked next on BlackBox 3.0. Could anyone please help me !
Edit:
When I tried to reboot into recovery mood (Vol Up + Home + Power) it says:
" Secure Fail Kernel
(Warning Sign) System Software not authorised by ATT has been found on your phone"
Don't select the reboot now option in the aroma installer at the end. Then, after the ROM flash is complete and before you reboot the phone, you need to put the phone back in download mode and flash the MLD ap/bl/cp files from the tool
Sent from my GT-I9505 using Tapatalk
jmjoyas said:
Don't select the reboot now option in the aroma installer at the end. Then, after the ROM flash is complete and before you reboot the phone, you need to put the phone back in download mode and flash the MLD ap/bl/cp files from the tool
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
I flashed the NB1 using ODIN but it still stays on Samsung Logo with custom logo. I am not able to navigate any where else from that screen.
Edit:
I was able to go into system recovery. Please let me know if I can fix the error somehow.
Thanks a lot !
Get into stock recovery and factory reset. I am not sure why you flashed NB1 though, as there is no direct root method for it yet
Sent from my GT-I9505 using Tapatalk
jmjoyas said:
Get into stock recovery and factory reset. I am not sure why you flashed NB1 though, as there is no direct root method for it yet
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
He probably was following the steps that were provided elsewhere here that had you go from nc1 to nb1 then back to the M (I can't remember which M) one.
jmjoyas said:
Get into stock recovery and factory reset. I am not sure why you flashed NB1 though, as there is no direct root method for it yet
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
I had rooted MK2 and the installed the custom ROM (Blackbox) and then was suppose to flash NB1.
So, if I just did a factory reset it would solve my error?
Thanks for the help!
Edit:
I tried doing the factory reset. It just wipes all the user data. And I am still stuck on the same screen with Samsung and the custom logo.
mayurd said:
I had rooted MK2 and the installed the custom ROM (Blackbox) and then was suppose to flash NB1.
So, if I just did a factory reset it would solve my error?
Thanks for the help!
Edit:
I tried doing the factory reset. It just wipes all the user data. And I am still stuck on the same screen with Samsung and the custom logo.
Click to expand...
Click to collapse
I have sent you a PM. Probably I can assist better on hangout.
I'm rooted and unlocked running custom ROM TW 4.4.4 with Koontz kernel using TWRP and for the life of me I can't get CM11 installed.
I'm using the KLTEVZW version and the recommended GAPPS. I'm stumped. Any ideas?
A1Barrett said:
I'm rooted and unlocked running custom ROM TW 4.4.4 with Koontz kernel using TWRP and for the life of me I can't get CM11 installed.
I'm using the KLTEVZW version and the recommended GAPPS. I'm stumped. Any ideas?
Click to expand...
Click to collapse
i would be sure to follow the instructions.. is there a aosp kernel you should use or do you use the stock tw kernel?
I'm using Koontz TW Kernel currently. But the CM zip file should contain the new CM Kernel. ?
I am getting this message when it fails, 'this package is for device KLTEVZW, this device is KLTE'. So I guess I'm flashing the wrong zip. But my phone is an Verizon S5 developer model.....confused?
A1Barrett said:
I am getting this message when it fails, 'this package is for device KLTEVZW, this device is KLTE'. So I guess I'm flashing the wrong zip. But my phone is an Verizon S5 developer model.....confused?
Click to expand...
Click to collapse
which cm11 rom are you flashing? from verizon s5 original development section?
Yes, from Ablinoman887 and official cm 11, KLTEVZW. I did flash the KLTE version and it didn't fail but it bootlooped. However I did flash fusion 4.4.4 for KLTEVZW and its working great.
Try using the Version of TWRP from this thread: http://forum.xda-developers.com/showthread.php?t=2794674
Bkuschel u rock. It work. Thanks man
A1Barrett- How did you flash this? ODIN v3.09 doesnt seem to like it, it just errors out after awhile.
Neodawg- I flashed using the TWRP that bkuschel recommended 2 posts up.
A1Barrett said:
Neodawg- I flashed using the TWRP that bkuschel recommended 2 posts up.
Click to expand...
Click to collapse
Right, but how did you flash it? With ODIN? or use TWRP to flash it? The link only provides a .img file and if I tar it ODIN wont flash it, not sure if I am doing something wrong with tarring it or if the img isnt setup to be flashed by ODIN.
Thanks, for your help
Flash the new twrp using the old twrp. Use the zip. Twrp-kt.all-in-one.zip
A1Barrett said:
Flash the new twrp using the old twrp. Use the zip. Twrp-kt.all-in-one.zip
Click to expand...
Click to collapse
Thanks, that worked great, wasnt aware TWRP could even do that.
Yeah no worries.... Glad it worked out for ya
neodawg said:
Thanks, that worked great, wasnt aware TWRP could even do that.
Click to expand...
Click to collapse
lol twrp could always flash zips/recoveries on unlocked bootloaders
elliwigy said:
lol twrp could always flash zips/recoveries on unlocked bootloaders
Click to expand...
Click to collapse
Hmm, suppose so, never really thought about it, I came from a Motorola phone last time and not a Dev device either, so this whole ODIN, unlocked thing is new to me. Either way *facepalm*....hahaha
So it looks like this is only working for the dev version of the verizon GS5? Or at least that's what this page says (http://forum.xda-developers.com/showthread.php?t=2794674)
Guess i'm SOL?
hi all , sorry but my english is so bad
i just bought a galaxy s4 att secondhand , this had bassband UCUAMDL . and i checked the lastest version of it is 4.2.2
can i upgrade my phone up to 4.4 ?
and i dont know terminology about "MF3 - MK2 ............."
could you tell me ?
thanks so much :victory::victory::victory:
Root. Install TWRP recovery. Flash a rom 4.4.4 or try some lollipop love!! You are lucky enough to have an unlocked bootloader..
HORiZUN said:
Root. Install TWRP recovery. Flash a rom 4.4.4 or try some lollipop love!! You are lucky enough to have an unlocked bootloader..
Click to expand...
Click to collapse
thanks so much ,
can you get me links :crying:
but MF3 - MK2 ............. what is it ?
when i flash rom , what i have to notice ?
I hope you don't have MF3. If that's the case, I'm pretty sure that SafeStrap is your only recovery option.
HORiZUN said:
I hope you don't have MF3. If that's the case, I'm pretty sure that SafeStrap is your only recovery option.
Click to expand...
Click to collapse
but i dont know MF3 >"<
what is it ?
how check it on my phone ?
HORiZUN said:
I hope you don't have MF3. If that's the case, I'm pretty sure that SafeStrap is your only recovery option.
Click to expand...
Click to collapse
i am in 4.2.2
sonluyen94 said:
but i dont know MF3 >"<
what is it ?
how check it on my phone ?
Click to expand...
Click to collapse
I have the same question. hopefully someone will be able to explain it to us.
MF3 would be the last three digits of your system software version
HORiZUN said:
MF3 would be the last three digits of your system software version
Click to expand...
Click to collapse
my baseband : I337UCUAMDL
kernel version : 3.4.0-453947 - [email protected] #1
android version : 4.2.2
build number : JDQ39.I337UCUAMDL
it is my phone >"<
You don't have MF3, and that's a good thing. You can install a custom recovery. You need to root, install a custom recovery, and then you can start flashing roms.
sonluyen94 said:
my baseband : I337UCUAMDL
kernel version : 3.4.0-453947 - [email protected] #1
android version : 4.2.2
build number : JDQ39.I337UCUAMDL
it is my phone >"<
Click to expand...
Click to collapse
nogods said:
I have the same question. hopefully someone will be able to explain it to us.
Click to expand...
Click to collapse
Ok, use TowelRoot.com to root the phone, and use TWRP manager to install TWRP on your device. After that check out the development section of this very forum and flash any ROM you wish. 4.2.2 or 4.4.4 or 5.0 or anywhere in between (Just read the thread and instructions first!!!). Whatever you do, never update using the OTA updater on the stock ROM! Also, dotn ever flash an image in Odin that isn't MDL, because if you go higher than MDL, you lose the ability to have a custom recovery. You are one of the lucky ones, cherish the ability, and read through threads before flashing, stuff. Good Luck!
Also, you don't have to worry if the ROM says safestrap compatible, because you don't have to use Safestrap, you can have TWRP instead (which is better), because all Safestrap ROMS are TWRP compatible, but not vice-versa.
npjohnson said:
Ok, use TowelRoot.com to root the phone, and use TWRP manager to install TWRP on your device. After that check out the development section of this very forum and flash any ROM you wish. 4.2.2 or 4.4.4 or 5.0 or anywhere in between (Just read the thread and instructions first!!!). Whatever you do, never update using the OTA updater on the stock ROM! Also, dotn ever flash an image in Odin that isn't MDL, because if you go higher than MDL, you lose the ability to have a custom recovery. You are one of the lucky ones, cherish the ability, and read through threads before flashing, stuff. Good Luck!
Also, you don't have to worry if the ROM says safestrap compatible, because you don't have to use Safestrap, you can have TWRP instead (which is better), because all Safestrap ROMS are TWRP compatible, but not vice-versa.
Click to expand...
Click to collapse
thanks so much :fingers-crossed:
but can you talk to me what rom is good about battery ?
sonluyen94 said:
thanks so much :fingers-crossed:
but can you talk to me what rom is good about battery ?
Click to expand...
Click to collapse
Most if not all. They're all built from either GPE or CM.
All good advice. Plus when you root and get Twrp recovery installed do a backup thru Twrp (Nandroid) and keep on phone and put a copy on pc. That way you have something to restore if you get in trouble. Also, your bootloader is not unlocked. No Att i337s are. Instead devs use an exploit called Loki-Doki to bypass Sammy's security checks to allow custom roms/kernels etc to flash. You can google Loki Doki and read up on it. If the rom or kernel is not loki'd you will have to flash the zip thru recovery to allow the rom or kernel to flash. You will come across this when flashing International roms and kernels. I don't have link any more so maybe someone else can link it. Keep it on SD card. Like noted read OP carefully and last 20 pages of rom thread. Builds newer than MDL are blocked by Att from using Loki and require SafeStrap. Which you don't need to worry about. Although you can read up on it. Good Luck. [emoji1]
Sent from my iPhone 6 Plus using Tapatalk
I hope you won't mind me jumping in your thread.,
I've recently had to odin my mdl phone back to stock. I haven't done that in a long time. I have root, and supersu, and busybox. The TWRP Manager app is malfunctioning and I cannot use it to install recovery. They list the crash I am experiencing in the play store as a known problem, and they say it will take time to fix. I have a good loki'd copy of twrp but the stock recovery doesn't want to install it. I even changed the name to "update.zip" and it fails. So my problem is I need a recovery. I am considering installing Clockworkmod's ROM Manager to install their recovery, and then using their recovery to install the good loki'd twrp that I want. Does this sound like a good plan? I have been away from this hobby for a while.
plasticglock said:
I hope you won't mind me jumping in your thread.,
I've recently had to odin my mdl phone back to stock. I haven't done that in a long time. I have root, and supersu, and busybox. The TWRP Manager app is malfunctioning and I cannot use it to install recovery. They list the crash I am experiencing in the play store as a known problem, and they say it will take time to fix. I have a good loki'd copy of twrp but the stock recovery doesn't want to install it. I even changed the name to "update.zip" and it fails. So my problem is I need a recovery. I am considering installing Clockworkmod's ROM Manager to install their recovery, and then using their recovery to install the good loki'd twrp that I want. Does this sound like a good plan? I have been away from this hobby for a while.
Click to expand...
Click to collapse
You can flash a recovery zip in a custom recovery. So if you have the loki'd twrp in a zip file, flashing cwm first will work
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You can flash a recovery zip in a custom recovery. So if you have the loki'd twrp in a zip file, flashing cwm first will work
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks man, that's exactly what I was planning. I remember avoiding CWM last year due to some issue on this device so I just wanted to make sure it wasn't going to do more harm than good. :good:
plasticglock said:
Thanks man, that's exactly what I was planning. I remember avoiding CWM last year due to some issue on this device so I just wanted to make sure it wasn't going to do more harm than good. :good:
Click to expand...
Click to collapse
ROM manager didn't work. It said it installed cwm recovery but it didn't. I was able to install the latest TWRP with this ROM Installer and it worked like a charm! I then installed my custom TWRP from there, rebooted recovery, and installed Danvh's Google edition. I'm setting it up right now. I'm so happy to get my phone back. I just hope the odin flash fixed my problems.
To the OP try ROM installer to get your custom recovery going. Also if you like simple and fast AOSP check out Danvh's google edition rom, but stick to 4.4.4 for now. 5.0 is out but its buggy. Here's a link to the custom version of twrp that I use. https://www.dropbox.com/l/iDQQqlzNbyiFbQrMF4XcRc It's already loki'd so you can flash it if you have any problems with the latest build.
I seem to be unable to successfully flash ROMs on my phone...
I am not sure what's going on.
Yes, I am rooted. Yes, I am flashing ROMs made for my phone, and flashing the appropriate firmware to match the ROM. Yes, I perform a clean flash by wiping everything first.
I have tried wiping cache/dalvik after flashing, still no luck. I have tried not flashing gapps, still nothing...
No matter what I do, it never boots. I sit at the Verizon screen for hours on end.
Any ideas?
G900V Verizon Samsung Galaxy S5
If it's any help, here is a list of ROMs I have tried...
Alliance
Jasmine
Eclipse
Optimal
MiUi
FreedomROM
sgirard1991 said:
If it's any help, here is a list of ROMs I have tried...
Alliance
Jasmine
Eclipse
Optimal
MiUi
FreedomROM
Click to expand...
Click to collapse
What build are you on? Do you have safestrap, flashfire?
Nk2. & I use safestrap
Sent from my SM-G900V using Tapatalk
sgirard1991 said:
Nk2. & I use safestrap
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Never heard of this. You might have flashed the wrong thing. We don't flash gapps with our Roms. Start over by using Odin to flash a full stock tar of NGC and root again.
I'll give it a try later. Thanks.
sgirard1991 said:
Nk2. & I use safestrap
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
If you're on NK2 then most of the Roms I read you flashed won't work on that build. After you flash a ROM built for OC4, like FreedomROM for example, you need to Odin over the OC4 firmware (which includes modem and kernel) to the device otherwise Roms won't start. Same thing goes for everyone other ROM with the firmware except it has to be for the respective build.
mrjiggywiggy said:
If you're on NK2 then most of the Roms I read you flashed won't work on that build. After you flash a ROM built for OC4, like FreedomROM for example, you need to Odin over the OC4 firmware (which includes modem and kernel) to the device otherwise Roms won't start. Same thing goes for everyone other ROM with the firmware except it has to be for the respective build.
Click to expand...
Click to collapse
Yeah, I've got that all figured out now. Never really had to do that with any other phones I've had, it was always just flash and go, never really messing with different firmware and whatnot. I have since tested 4 different ROMs and they have all flashed with success..
Thanks
Can a mod please mark this thread as answered/closed ? I got it all figured out. Thanks.