I currently have a brand new Canadian S4 with the MDJ firmware/baseband version.
Most of the roms are MDL based.
Do i have to change the base firmware/baseband to MDL before flashing and MDL rom ?
My goad is to install CleanRom wich is MDL based.
Thanks for the guidance.
Xetalx
Xetalx said:
I currently have a brand new Canadian S4 with the MDJ firmware/baseband version.
Most of the roms are MDL based.
Do i have to change the base firmware/baseband to MDL before flashing and MDL rom ?
My goad is to install CleanRom wich is MDL based.
Thanks for the guidance.
Xetalx
Click to expand...
Click to collapse
You can just flash the ROM. Just make a Nandroid backup first. Some ROM's come with a custom kernel and you may need to flash a Canadian kernel directly after flashing the ROM.
blyndfyre said:
You can just flash the ROM. Just make a Nandroid backup first. Some ROM's come with a custom kernel and you may need to flash a Canadian kernel directly after flashing the ROM.
Click to expand...
Click to collapse
I did get the original Kernel file for my cell provider. It is a TAR file with boot.img into it.
What is the easyest way to apply it after flashing the Rom in TWRP ?
Thanks
Xetalx
TARs are flashed with Odin or Mobile Odin.
Xetalx said:
I did get the original Kernel file for my cell provider. It is a TAR file with boot.img into it.
What is the easyest way to apply it after flashing the Rom in TWRP ?
Thanks
Xetalx
Click to expand...
Click to collapse
If you are flashing the STOCK firmware for your specific carrier it will include the STOCK kernel.
If you are using a custom ROM like Mint Jelly or something, I'd say flash Adam kernel after flashing the ROM. You won't want to flash a STOCK kernel with a custom ROM.
Did you end up updating to MDL?
I also have the MDJ kernel and I installed CleanRom, I now cannot get wifi and TWRP will not boot in recovery mode. I thought it would be easier just to update to MDL to get wifi but mobile Odin did not work.
Thank you
travisobvs said:
Did you end up updating to MDL?
I also have the MDJ kernel and I installed CleanRom, I now cannot get wifi and TWRP will not boot in recovery mode. I thought it would be easier just to update to MDL to get wifi but mobile Odin did not work.
Thank you
Click to expand...
Click to collapse
Regarding wifi on CleanROM, did you check post #2 here?
bo8 said:
Regarding wifi on CleanROM, did you check post #2 here?
Click to expand...
Click to collapse
No I did not,
Truthfully I am a pretty big Noob to all of this and was afraid of changing my kernel to MF3 from MDJ. I really didn't know how that would affect my phone / carrier situation here in Canada. The main problem was that I could not get the phone into recovery mode. Turns out I just needed to re-root the phone. So when I got the phone to actually go into recovery I jumped at the CM Rom. When I find a forum that helps me understand what updating my Kernel does to my phone I will try to update Kernel and go back to CleanRom. I kind of miss multiwindow.... maybe a little bit of Touchwiz...
Thanks for the reply!
EDIT : I also found this : http://www.scottsroms.com/downloads.php?do=file&id=421 which is a version of CleanROM made for the MDJ but it is dated further back which threw me for a loop too.
travisobvs said:
No I did not,
Truthfully I am a pretty big Noob to all of this and was afraid of changing my kernel to MF3 from MDJ. I really didn't know how that would affect my phone / carrier situation here in Canada. The main problem was that I could not get the phone into recovery mode. Turns out I just needed to re-root the phone. So when I got the phone to actually go into recovery I jumped at the CM Rom. When I find a forum that helps me understand what updating my Kernel does to my phone I will try to update Kernel and go back to CleanRom. I kind of miss multiwindow.... maybe a little bit of Touchwiz...
Thanks for the reply!
EDIT : I also found this : http://www.scottsroms.com/downloads.php?do=file&id=421 which is a version of CleanROM made for the MDJ but it is dated further back which threw me for a loop too.
Click to expand...
Click to collapse
No worries and you're very welcome! Don't sweat, I'm still on stock ROM because I'm hesitant to make the ROM dive. Don't know how or if installing MF3 kernel via custom ROM would affect the phone in terms of rooting or custom recovery either. I'd probably be sticking with MDJ build if possible.
You and me both on multiwindow! Helps a ton when it comes to referencing something while emailing/texting! I'd miss the TW camera as well ... maybe. haha
Which version of TWRP are you on? Version 2.6 has an often-experienced issue where it just hangs at the "teamwin" splash screen. Downgrading to 2.5.0.2 resolves that.
Any updates?
bo8 said:
No worries and you're very welcome! Don't sweat, I'm still on stock ROM because I'm hesitant to make the ROM dive. Don't know how or if installing MF3 kernel via custom ROM would affect the phone in terms of rooting or custom recovery either. I'd probably be sticking with MDJ build if possible.
You and me both on multiwindow! Helps a ton when it comes to referencing something while emailing/texting! I'd miss the TW camera as well ... maybe. haha
Which version of TWRP are you on? Version 2.6 has an often-experienced issue where it just hangs at the "teamwin" splash screen. Downgrading to 2.5.0.2 resolves that.
Click to expand...
Click to collapse
Hey guys,
I am also a 1337m Rogers S4 (MDJ) owner, also a noob as well. I managed to flash my phone with CM and had a pretty good AOSP experience and learned a little bit on the way. I can legitimately say that I miss a couple thing about stock / Touch wiz, mainly the multiwindow support and camera. Cyanogenmod is also acting up and drains battery pretty bad when I am roaming in the states.
What did you guys end up doing? Did you update your base-band to mdk and install CleanRom? Right now that looks like it's my goal but I truthfully have no idea how to do it.
Did you guys go back to stock after changing? Do I just find a stock ROM on the forum and use ODIN to bring it back?
Is switching roms as easy as choosing something in Goo manager or do you need to go into a recovery in recovery mode?
Thank you!
Related
Hello guys,
I installed the ROM under this post http://forum.xda-developers.com/showthread.php?t=2288531&page=13
The flashing of the ROM was successful but the only thing that it's not working with this flash is that I'm unable to turn on my wifi feature.
Is there a way to fix this without remodifying the ROM?
Any help will do. Thanks guys!!
tones160 said:
Hello guys,
I installed the ROM under this post http://forum.xda-developers.com/showthread.php?t=2288531&page=13
The flashing of the ROM was successful but the only thing that it's not working with this flash is that I'm unable to turn on my wifi feature.
Is there a way to fix this without remodifying the ROM?
Any help will do. Thanks guys!!
Click to expand...
Click to collapse
First just an FYI questions go in the QA section. This will be moved there by a Mod so just giving you a heads up. Were you on MDC or MDL before you flashed the rom?
crawrj said:
First just an FYI questions go in the QA section. This will be moved there by a Mod so just giving you a heads up. Were you on MDC or MDL before you flashed the rom?
Click to expand...
Click to collapse
My S4 was running on MDL already.
tones160 said:
My S4 was running on MDL already.
Click to expand...
Click to collapse
That's what I was thinking. That Rom is MDC based. So you have MDL Firmware but MDC System. If you want to stick with that rom here is what I would do. Make a backup. Odin the stock MDC tar twice, don't ask just better this way . Install custom recovery back on. Restore only the system. You should be fixed. Or you could probably get away with just installing the MDC Kernel. You can find the tar and kernel from here http://forum.xda-developers.com/showthread.php?t=2256514
Flash a custom kernel and your Wifi will work.
Sent from my SPH-L720 using Tapatalk 2
crawrj said:
That's what I was thinking. That Rom is MDC based. So you have MDL Firmware but MDC System. If you want to stick with that rom here is what I would do. Make a backup. Odin the stock MDC tar twice, don't ask just better this way . Install custom recovery back on. Restore only the system. You should be fixed. Or you could probably get away with just installing the MDC Kernel. You can find the tar and kernel from here http://forum.xda-developers.com/showthread.php?t=2256514
Click to expand...
Click to collapse
That's a great suggestion there crawjr. I will try the kernal suggestion first if anything. Even though i feel uncomfortable messing with the kernel system. Sorry for the noob questions I haven't been on this page for ages since the G2 was first released lol. :good:
ok first i installed the SACS CUSTOM ROM then ChronicKernel AOSP-JB4.2 and now my phone starts up slow and it has a hard time loading TWRP some one please help my phone is acting up.
First off this Sac's is a TouchWiz and NOT AOSP ROM.
If you flashed the wrong kernel it won't boot right/well if at all.
I haven't tried Cronic's kernel on TW, and I do know he said it 'should' work on TW but I don't know.
You can try loading ktoonz TW one.
Also.
Were you on MF9 firmware(s) before you flashed?
leaderbuilder said:
First off this Sac's is a TouchWiz and NOT AOSP ROM.
If you flashed the wrong kernel it won't boot right/well if at all.
I haven't tried Cronic's kernel on TW, and I do know he said it 'should' work on TW but I don't know.
You can try loading ktoonz TW one.
Also.
Were you on MF9 firmware(s) before you flashed?
Click to expand...
Click to collapse
no i just installed rom and then kernel. do i install TW 4.3 or 4.2? also should i install the firmware you put?
fujirio said:
no i just installed rom and then kernel. do i install TW 4.3 or 4.2? also should i install the firmware you put?
Click to expand...
Click to collapse
You can't flash 4.3 because MF9 is 4.2
As for firmware what where you on before you flashed this?
You can always flash the firmware, flash, flash the ROM then flash the kernel and see if it gets going.
Kernel issue
fujirio said:
no i just installed rom and then kernel. do i install TW 4.3 or 4.2? also should i install the firmware you put?
Click to expand...
Click to collapse
Hello, you have to update your touchwiz rom to MF9 before you root it then you can install Sacs23 custom rom. His rom already comes with a Kernel I think its Agats so you dont ahve to flash any Kernels....so what i would suggest go to settings on your phone and about and check to see if you see MF9 firmware. if it does just go ahead and do a clean install, and you should be good to go.
leaderbuilder said:
You can't flash 4.3 because MF9 is 4.2
As for firmware what where you on before you flashed this?
You can always flash the firmware, flash, flash the ROM then flash the kernel and see if it gets going.
Click to expand...
Click to collapse
Lucky422 said:
Hello, you have to update your touchwiz rom to MF9 before you root it then you can install Sacs23 custom rom. His rom already comes with a Kernel I think its Agats so you dont ahve to flash any Kernels....so what i would suggest go to settings on your phone and about and check to see if you see MF9 firmware. if it does just go ahead and do a clean install, and you should be good to go.
Click to expand...
Click to collapse
thanks guys for all the help. I flashed the ktoonz TW one kernel and now its working flawlessly. You guys are amazing and thanks again for the fast reply's. :victory:
So I recently got this ROM: http://forum.xda-developers.com/showthread.php?t=2428254. I got the DEODEX version, and when I try to turn wifi on, it just switches back to off. I tried clicking the WiFi fix links in the thread, but they wouldn't work. What do I do? I have a SGH-I337, by the way.
Conmore said:
So I recently got this ROM: http://forum.xda-developers.com/showthread.php?t=2428254. I got the DEODEX version, and when I try to turn wifi on, it just switches back to off. I tried clicking the WiFi fix links in the thread, but they wouldn't work. What do I do? I have a SGH-I337, by the way.
Click to expand...
Click to collapse
What can you do?
For one thing you can flash a custom rom which is a finished product.
But if you want to fool around with Google Edition roms you can try this little trick,
reboot the phone and toggle the wifi on and off 3 or 4 times waiting about 10 seconds
between toggling. For some people this little trick temporarily fixed the wifi issue.
Misterjunky said:
What can you do?
For one thing you can flash a custom rom which is a finished product.
But if you want to fool around with Google Edition roms you can try this little trick,
reboot the phone and toggle the wifi on and off 3 or 4 times waiting about 10 seconds
between toggling. For some people this little trick temporarily fixed the wifi issue.
Click to expand...
Click to collapse
Would you happen to know of any Google Edition ROMS that are trustworthy for the GS4 that are compatible with Safestrap?
re:custom roms
Conmore said:
Would you happen to know of any Google Edition ROMS that are trustworthy for the GS4 that are compatible with Safestrap?
Click to expand...
Click to collapse
I am assuming that you have never done an OTA and updated to the official
MF3 4.3 firmware yet, if you have done an OTA MF3 update then ignore this post.
There are no google edition 4.3 roms which are safestrap compatible as of yet.
So far only the Jellybean Touchwiz 4.2.2 custom roms are compatible with it.
The only reason that your phone is working with the google edition rom
is because it's based on version 4.2.2 rom.
None of the developers are going to create a full featured custom google
edition 4.2.2 rom since the official 4.3 firmware is available.
However if you want to try a full featured Touchwiz Jellybean custom rom
which I would highly suggest.
This custom rom is based on the Samsung Galaxy S4 Touchwiz Jellybean 4.2.2 firmware.
It's called "Darthstalker v9" and it's really excellent.
Here is the link to it: http://forum.xda-developers.com/showthread.php?t=2426081
(safestrap compatible)
Give it a try, good luck! .
Misterjunky said:
I am assuming that you have never done an OTA and updated to the official
MF3 4.3 firmware yet, if you have done an OTA MF3 update then ignore this post.
There are no google edition 4.3 roms which are safestrap compatible as of yet.
So far only the Jellybean Touchwiz 4.2.2 custom roms are compatible with it.
The only reason that your phone is working with the google edition rom
is because it's based on version 4.2.2 rom.
None of the developers are going to create a full featured custom google
edition 4.2.2 rom since the official 4.3 firmware is available.
However if you want to try a full featured Touchwiz Jellybean custom rom
which I would highly suggest.
This custom rom is based on the Samsung Galaxy S4 Touchwiz Jellybean 4.2.2 firmware.
It's called "Darthstalker v9" and it's really excellent.
Here is the link to it: http://forum.xda-developers.com/showthread.php?t=2426081
(safestrap compatible)
Give it a try, good luck! .
Click to expand...
Click to collapse
MF3 4.3 firmware? I thought MF3 was 4.2.2, and 4.3 is MFJ or something like that. But I am on MF3, 4.2.2, I have Safestrap, and I can install ROM's. So should I still check out your suggestion?
re: roms/mf3
Conmore said:
MF3 4.3 firmware? I thought MF3 was 4.2.2, and 4.3 is MFJ or something like that. But I am on MF3, 4.2.2, I have Safestrap, and I can install ROM's. So should I still check out your suggestion?
Click to expand...
Click to collapse
Read this thread: http://forum.xda-developers.com/showthread.php?t=2428254
It will explain it all to you in great detail, the thread also has links where you can
go directly to the custom rom thread and download "Darthstalker v9" rom & others.
Currently there are only three full featured custom roms which are fully compatible with MF3.
Darthstalker v9 is one of them and it was very recently updated.
You will see the links to them on the very first post.
Good luck!
Remember it takes less time to click the "THANKS" button than it takes to type "thank you"
Misterjunky said:
Read this thread: http://forum.xda-developers.com/showthread.php?t=2428254
It will explain it all to you in great detail, the thread also has links where you can
go directly to the custom rom thread and download "Darthstalker v9" rom & others.
Currently there are only three full featured custom roms which are fully compatible with MF3.
Darthstalker v9 is one of them and it was very recently updated.
You will see the links to them on the very first post.
Good luck!
Remember it takes less time to click the "THANKS" button than it takes to type "thank you"
Click to expand...
Click to collapse
OK, so now I'm not getting WiFi on the rom you recommended, which is amazing by the way.
Edit: Fixed it, forgot to flash kernel modules, was looking at the wrong thread. :/
Kernel modules for MF3
Conmore said:
OK, so now I'm not getting WiFi on the rom you recommended, which is amazing by the way.
Edit: Fixed it, forgot to flash kernel modules, was looking at the wrong thread. :/
Click to expand...
Click to collapse
Hi, you said you forgot to flash the kernel modules to get wifi working with MF3, but when you did, wifi was working correctly. I cant FOR THE LIFE of me figure out how to get my wifi working. I flashed the "jflteatt-MF3-modules.zip" file from Hashcode's safestrap forum, but cannot get it to work. Ive also wiped everything and tried flashing the rom and module again, but no luck. Do you have links or can you tell me which kernel I should be flashing please? I really love Darthstalker and this is the only thing holding me back..
EDIT: Nevermind... Thank you anyway.. I re-downloaded the module and re-did the whole flashing process. Its working now.. Weird. Ive done the same thing atleast 5 times.. Oh Well.. Im happy now! :victory:
Conmore said:
So I recently got this ROM: http://forum.xda-developers.com/showthread.php?t=2428254. I got the DEODEX version, and when I try to turn wifi on, it just switches back to off. I tried clicking the WiFi fix links in the thread, but they wouldn't work. What do I do? I have a SGH-I337, by the way.
Click to expand...
Click to collapse
I didn't see anyone mention it so i'll tell you - this is a simple fix.
If you are running MF3 and are using this GPE Rom 4.2.2 via SafeStrap, you need to simply flash the kernel for MF3 AFTER you've flashed the GPE Rom.
You can A.) Wipe your current Rom-Slot, flash the ROM itself then immediately flash the kernel provided at (http://forum.xda-developers.com/showthread.php?t=2448925) ---> Just above "Manually remove SafeStrap"
Or you can B.) Just flash the kernel zip package over the same Rom-Slot you have the Google Play Edition Rom 4.2.2 on.
Hi all,
I am interested in the CM11 ROM. Last night I spent 6hrs trying and failed, epically.
Here is what I did already:
1. Downgraded from 4.4.2 back to factory
2. Successfully rooted
3. Installed ROM Manager
4. Successfully downloaded CM11 and latest GApps
Then when I tried to boot into recovery it kept going to a screen with a little android guy lying on his back with a red triangle!!! I tried six times.
I got frustrated and just updated back to 4.4.2 and have been dealing with it. I am still rooted and have been able to remove my bloatware and other things you need root access for.
Any thoughts or help as to how I can install the CM11 rom?? I am happy running NovaLauncher and using DynamicNotifications to approximate it but really want to try out CM11.
Cheers and thanks!
Lucky there is no way to root on 4.4.2 yet or atleast no Recovery's yet it could be worse you're atleast rooted and it didn't brick your phone
Sent from my VS980 4G using Tapatalk
Did you actually try flashing a recovery first? Just installing ROM manager won't install the custom recovery needed to flash ROMs. You have to do that step as well.
JRJ442 said:
Did you actually try flashing a recovery first? Just installing ROM manager won't install the custom recovery needed to flash ROMs. You have to do that step as well.
Click to expand...
Click to collapse
No, I didn't. I am super new with android. Had an iphone for a long time. How do I flash a recover? Can I still do it now on 4.4.2 b/c its rooted?
Sorry about the noob questions, everyone is being very helpful!
follow this step..
http://forum.xda-developers.com/showthread.php?t=2681205
android_nashville said:
No, I didn't. I am super new with android. Had an iphone for a long time. How do I flash a recover? Can I still do it now on 4.4.2 b/c its rooted?
Sorry about the noob questions, everyone is being very helpful!
Click to expand...
Click to collapse
LG blocked the Loki exploit with 4.4.2 so you can't flash recoveries currently. You'd have to flash back to 4.2.2 to do that. Which if you want custom ROMs now its going to have to be done sooner or later. Which carrier and model number do you have? If you have an international D802 the above post by @zekurosu will work for you, otherwise don't use that one. You're gonna have to find the method for your model number.
My first guess was that you missed the flashing the custom recovery step, which people above me have already helped ya out on. For being new to Android you did fairly well, you just missed that one step.
Good luck!
JRJ442 said:
LG blocked the Loki exploit with 4.4.2 so you can't flash recoveries currently. You'd have to flash back to 4.2.2 to do that. Which if you want custom ROMs now its going to have to be done sooner or later. Which carrier and model number do you have? If you have an international D802 the above post by @zekurosu will work for you, otherwise don't use that one. You're gonna have to find the method for your model number.
Click to expand...
Click to collapse
thanks, forgot to mention it was only for D802 :good:
zekurosu said:
thanks, forgot to mention it was only for D802 :good:
Click to expand...
Click to collapse
I have an ATT D800 running 4.4.2. I can't decide whether its worth it to flash back to 4.2.2 to try again. Pretty happy with NovaLauncher + widgetlocke and fairly closely approximates what I am looking for.
For what its worth, I was in 4.2.2 when I tried the first time and failed. I think mackster is right, I didn't flash the custom recovery. I basically flashed back to 4.2.2->rooted->tried to boot into recovery (OVER and OVER) then gave up and upgraded back to 4.4.2.
Thanks for all the help. At least I now have a rooted phone and have been able to do some cool stuff with that. My goal is to get nexus 5 software in an LG G2 body (battery, camera, etc)
@android_nashville There's a way to have the best of both worlds. You can flash back to 4.2.2 (10d preferably) root, flash a custom recovery with Flashify or FreeGee. Both available on the play store. Then actually update to 4.4.2 following this thread http://forum.xda-developers.com/showthread.php?t=2483043. Eventually, if you want to flash custom ROMs you're going to have flash back to 4.2.2 and do this process regardless. The 4.4 aboot image (bootloader) can't be bypassed with Loki. Its been blocked. But some brilliant devs basically found out they can make a hybrid setup, with the 4.2.2 aboot, and everything else 4.4.2. This way you can have the ability to flash custom recovery, kernels and ROMs.
So I had DarkLord N5 on my N9005 before, which was awesome, but it had performance issues (especially when gaming). Then i downgraded to Stock KitKat using Odin and after boot up It showed No Signal, and everything was freezing and force closing. I somehow went to settings and found that i also have issues with IMEI and Baseband version, it was all unknown. The worst part is i did not backup my EFS. Any help guys please :crying:
I also have no audio playback
Im no pro here, but as i found in my research it is hard to downgrade from lolipop to kitkat as in 5.0 new architecture has been presented which they called art. I think. So it gives lots of incompatibilities. I tried the same as you but i ended up going stock lolipop for a while.
Yesterday i flashed Ressurrection remix 6.0.1 Marshmallow based off Slim roms and CM and i admit this is so far best rom i have tested. (Unless you need all fancy spen features)
I'd try to stick to anything that is 5.1 or above since great battery life.
Sorry for not much info, but i couldn't get past your post unanswered.
oxoconstantineoxo said:
Im no pro here, but as i found in my research it is hard to downgrade from lolipop to kitkat as in 5.0 new architecture has been presented which they called art. I think. So it gives lots of incompatibilities. I tried the same as you but i ended up going stock lolipop for a while.
Yesterday i flashed Ressurrection remix 6.0.1 Marshmallow based off Slim roms and CM and i admit this is so far best rom i have tested. (Unless you need all fancy spen features)
I'd try to stick to anything that is 5.1 or above since great battery life.
Sorry for not much info, but i couldn't get past your post unanswered.
Click to expand...
Click to collapse
I had many experiences with downgrading from new version to old version with my S3 and my Note, but never had this issue. Something is causing this...
founded a old backup of CM11.. Flashed CWM and restored to CM. Works flawlessly, but still no sound and those stuff
Honix5962 said:
I had many experiences with downgrading from new version to old version with my S3 and my Note, but never had this issue. Something is causing this...
Click to expand...
Click to collapse
So i had problems with my either s2 or note 4.
But afaik if u have updated your bootloader there may be no way to get back. And lack of IMEI on reverted KitKat isn't anything new. I bet going simply to anything art. Based will do.
People here are arguing on same issues as yours. Just don't listen to these "flash with odin" guys.. This doesn't work. Even if u flash the stock one.
http://forum.xda-developers.com/gal...o-downgrade-lollipop-to-kitkat-t2990262/page2
Hope you will dig up something.
You could try this. It worked for me.
http://forum.xda-developers.com/showthread.php?t=2507403
Have you tried flashing to the latest stock rom for the phone using Odin?
audit13 said:
Have you tried flashing to the latest stock rom for the phone using Odin?
Click to expand...
Click to collapse
Nope, I downloaded the KitKat firmware from Sammobile, and I'm downloading the Lollipop one now.
deejhay14 said:
You could try this. It worked for me.
http://forum.xda-developers.com/showthread.php?t=2507403
Click to expand...
Click to collapse
I tried it, but still no use :c
I would not try any other ROMs before trying to flash the latest stock rom from sammobile.com. Hopefully, this will resolve the baseband and imei issue. Sometimes, the missing or wrong imei is caused by a mismatch between the bootloader and modem firmware.
audit13 said:
I would not try any other ROMs before trying to flash the latest stock rom from sammobile.com. Hopefully, this will resolve the baseband and imei issue. Sometimes, the missing or wrong imei is caused by a mismatch between the bootloader and modem firmware.
Click to expand...
Click to collapse
I hope so.
I have seen this sort of problem on the Samsung s3 and note 3 phones.
audit13 said:
I have seen this sort of problem on the Samsung s3 and note 3 phones.
Click to expand...
Click to collapse
I did downgrading from 5.0 (CM12) to Stock 4.4 KitKat in my S3, but never had issues like this.
Downgrading from a cm rom to a stock rom via Odin can be fine because installing a cm rom does NOT alter the phone's bootloader or modem. Trying to downgrade from stock 4.4.2 to stock 4.3 with Odin on an s3 cannot be done.
audit13 said:
Downgrading from a cm rom to a stock rom via Odin can be fine because installing a cm rom does alter the phone's bootloader or modem. Trying to downgrade from stock 4.4.2 to stock 4.3 with Odin on an s3 cannot be done.
Click to expand...
Click to collapse
Oh, never knew about this, thanks for the info
Sorry, I meant to say that installing a cm rom DOES NOT change the bootloader or modem. When you flash back to stock via Odin, you are simply writing over the existing modem and bootloader with the same bootloader and modem if you are flashing the same stock rom that was on the phone before installing cm.
I flashed between KitKat and LP official just fine.
audit13 said:
Have you tried flashing to the latest stock rom for the phone using Odin?
Click to expand...
Click to collapse
Never mind, It works. Thanks for the help.
Which method worked? Thanks.
Use gsii repair