As title, looking for the 4.3 touchwiz based rom's that work with the old bootloader.
Almost all custom roms you can flash from recovery won't update your bootloader. I recommend omega.
Read OP of any rom and you will sure notice that the bootloader will remain untouched after flashing.
dkreventon said:
Almost all custom roms you can flash from recovery won't update your bootloader. I recommend omega.
Read OP of any rom and you will sure notice that the bootloader will remain untouched after flashing.
Click to expand...
Click to collapse
There will be no issues like lack of sound, wifi etc?
Been using GE roms since the new bootloader was introduced but I have read posts from users having problems flashing new firmware with old bootloader, or is that just for the official roms?
As long as you have the latest modem (MJ5) there won't be any issues.
http://forum.xda-developers.com/showpost.php?p=48972299&postcount=18311 - Check the installation instructions.
dkreventon said:
As long as you have the latest modem (MJ5) there won't be any issues.
http://forum.xda-developers.com/showpost.php?p=48972299&postcount=18311 - Check the installation instructions.
Click to expand...
Click to collapse
I'm already using that modem so might just give it a try.
Thanks for the help.
Be sure to have the latest philz touch and you're good to go!
Flashed Omega V19, all working.
Definitely not as smooth as the GE roms but it 's not bad, also it's nice to have the Samsung Camera back again.
Also give echoe rom ago, I'm on old bootloader and mk9 modem, working much better than 4.2.2 stock
Sent from my GT-I9505 using xda app-developers app
ranger4740 said:
Also give echoe rom ago, I'm on old bootloader and mk9 modem, working much better than 4.2.2 stock
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Thanks, might give that a try as Omega just started rebooting randomly..
Will try another kernel, if that doesn't fix it then ill try echoe.
All custom roms since 4.3 gave me random reboots once every couple of days.
I'm currently running omega v19 and the uptime is 48h.
Well I got Omega stable with KT kernel, but found the lag a bit annoying so tried echoe rom anyway.
Sadly the lag is much the same, I guess it's a feature of touchwiz and nothing can be done about it.
Why havent Samsung fixed this? it's almost the same as the original roms that phone shipped with.
Related
I bought S4 yesterday.. rooted it and installed Wicked V4.
I'm not sure if my phone was updated to MF9 already.
My question is, since Wicked M4 is an MDL based ROM, if I go to "about my device" and I do in fact have MF9 installed, will it appear MDL since I have an MDL based rom installed, or will it show MF9 despite that?
Also, I read a 20+ thread and it's like half and half. Some people say it's not necessary to do a software/firmware update on your phone and to just install the newest and latest ROM, what are your thoughts?
And if I do want my phone to stay updated with the latest software/firmware, how do I do this? I did read somewhere that people said to flash a stock-based rom and do an update and then re-flash whatever custom rom, but, how do I know which is a stock-based rom? (lol) also, is that the correct way to updated your phone when you're rooted and are running a custom rom? Thanks!
Just install the latest Rom unless other wise directed in the instructions of the Rom.
Sent from my SPH-L720 using xda premium
And wicked is a port from Verizon I believe where MDL was an ota for both sprint and Verizon.
Sent from my SPH-L720 using Tapatalk 4 Beta
dennissly said:
And if I do want my phone to stay updated with the latest software/firmware, how do I do this? I did read somewhere that people said to flash a stock-based rom and do an update and then re-flash whatever custom rom, but, how do I know which is a stock-based rom? (lol) also, is that the correct way to updated your phone when you're rooted and are running a custom rom? Thanks!
Click to expand...
Click to collapse
If you are already rooted with custom recovery everything you need to upgrade your device to rooted stock MF9 is here: http://forum.xda-developers.com/showthread.php?t=2357471
Just follow the steps in post #2 and you will be current on everything.
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.
I have been using the CM11 rom from Temasek until I decided to have a go at the Omega Rom. After installing through recovery, my note cannot get out of the Samsung Logo. It just refused to start. Tried installing latest stock rom through odin, same issue. Saw three lines of messages on the top left hand corner and the Samsung logo and that's it. Can only get it working if I revert back to Temasek's rom.
Help anyone...
redviper52 said:
I have been using the CM11 rom from Temasek until I decided to have a go at the Omega Rom. After installing through recovery, my note cannot get out of the Samsung Logo. It just refused to start. Tried installing latest stock rom through odin, same issue. Saw three lines of messages on the top left hand corner and the Samsung logo and that's it. Can only get it working if I revert back to Temasek's rom.
Help anyone...
Click to expand...
Click to collapse
which versions of omega and stock rom did you flash ? i read you said the newest, just asking to be sure.
if its the newest omega rom, you must flash 4.4.2 stock rom first.
when you upgrade to 4.4.2, you can no more use cm11 and you cant go back to any 4.3 based rom.
A.N.Droid said:
which versions of omega and stock rom did you flash ? i read you said the newest, just asking to be sure.
if its the newest omega rom, you must flash 4.4.2 stock rom first.
when you upgrade to 4.4.2, you can no more use cm11 and you cant go back to any 4.3 based rom.
Click to expand...
Click to collapse
I tried the 7.1 Omega Rom and then the 4.4.2 version of the stock rom.
You have to flash the stock 4.4.2 via Odin. Is that what you did?
Sent from my SM-N9005 using XDA Premium 4 mobile app
lyall29 said:
You have to flash the stock 4.4.2 via Odin. Is that what you did?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I did.
Try to boot into recovery after flashing the stock 4.4.2 and factory reset. Maybe that will work.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Flash stock 4.3 with odin, then 4.4.2 stock with odin. Then install recovery, and Omega after.
redviper52 said:
Can only get it working if I revert back to Temasek's rom.
Help anyone...
Click to expand...
Click to collapse
that shouldnt be possible if you done everything right.
as soon as you are on the new bootloader that you get when you flash 4.4.2, you can definatley not revert to temasek, it wont boot.
i think you are still on the old bootloader and that is why your kitkat based roms dont boot.
A.N.Droid said:
that shouldnt be possible if you done everything right.
as soon as you are on the new bootloader that you get when you flash 4.4.2, you can definatley not revert to temasek, it wont boot.
i think you are still on the old bootloader and that is why your kitkat based roms dont boot.
Click to expand...
Click to collapse
Thanks all... Its done. Went back to stock rom 4.3, then the 4.4.2, then followed by the usual rooting process for 4.4.2. Phone's working fine now. Doing update to Omega 7.2 as I am writing now... Thanks again all...
Mafle93 said:
Flash stock 4.3 with odin, then 4.4.2 stock with odin. Then install recovery, and Omega after.
Click to expand...
Click to collapse
That did it... Thanks
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.
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