So I want to put carbon rom on my galaxy s4. I have look about everywhere I can think.
The current rom I have on it has a locked boot loader so I cannot get TWRP or CWM on it.
I have tried rolling back to 4.2.2 but it will not let me.
Also I am already rooted.
I tried using this root method because it had a different boot loader but that didn't work either. http://forum.xda-developers.com/showthread.php?t=2692825 But it did root my phone.
Is there any way I can get carbon rom on my phone at this point?
You can only add touch wiz based roms. Search for safestrap
work around?
mrao said:
You can only add touch wiz based roms. Search for safestrap
Click to expand...
Click to collapse
Do you know any work arounds?
Like a custom boot loader or a program that tricks the verifier?
other possibilities
Is there a way I could get 4.2.2 on my s4 with the old bootloader using Odin, maybe use pit to wipe all partitions and load in the boot loader.
Or trick the verifier.
Related
Hello all, I am new to the S4 and got the root process to take by following the guide. However right after gaining root I downloaded goomanager and tried to flash the recovery from inside the app. It said the recovery was flashed successful but upon restarting I get the downloading screen and it just sticks there. Did I miss a step with installing the custom recovery? Also, I am using the ME7 version on my phone. Any help is very appreciated. I am hoping to install hyperdrive rom.
There is no custom recovery for ME7 S4's.
««I used to be a Serial Flasher...now I'm just a Cereal Flasher.»»
Recovery is not possible for ME7 at this point. Root is the only thing we have thus far.
Is there no way to get the new ROM on that version or do I need to downgrade to the previous version (if possible).
smayer85 said:
Is there no way to get the new ROM on that version or do I need to downgrade to the previous version (if possible).
Click to expand...
Click to collapse
No, you can't install a custom recovery or a custom ROM on ME7.
No, you can't downgrade to the previous release (MDK) that would allow you to do the above.
smayer85 said:
Is there no way to get the new ROM on that version or do I need to downgrade to the previous version (if possible).
Click to expand...
Click to collapse
There is no way to downgrade from ME7. Bootloader is locked. ME7 only has root.
So there is no way to flash a custom rom on my phone....awesome lol time to theme and freeze the bloatware.
Yes unfortunately we have a rather small sandbox to play in right now BUT it's better than no sandbox at all.
««I used to be a Serial Flasher...now I'm just a Cereal Flasher.»»
Go here for ME7 discussion...http://forum.xda-developers.com/showthread.php?p=44920037#post44920037
Can anyone help a noob?
I recently purchased a Galaxy S4 from verizon and rooted it using the VRUAME7 Build. However, all the bloatware that remains on the phone is making me want to flash Cyanogenmod.
Problem:
Using ROM Manager (which has always worked on my previous phones) every time I flash into recovery mode it flashes onto Samsung Recovery 3e NOT into TWRP, which I have flashed on my phone and need to use to install any custom ROMS.
Could anyone tell me how to disable Samsung Recovery 3e so I can use TWRP and flash the new ROM?
Or how, using Samsung Recovery 3e, I can flash a new ROM?
Aury said:
Can anyone help a noob?
I recently purchased a Galaxy S4 from verizon and rooted it using the VRUAME7 Build. However, all the bloatware that remains on the phone is making me want to flash Cyanogenmod.
Problem:
Using ROM Manager (which has always worked on my previous phones) every time I flash into recovery mode it flashes onto Samsung Recovery 3e NOT into TWRP, which I have flashed on my phone and need to use to install any custom ROMS.
Could anyone tell me how to disable Samsung Recovery 3e so I can use TWRP and flash the new ROM?
Or how, using Samsung Recovery 3e, I can flash a new ROM?
Click to expand...
Click to collapse
Your only option at present is Safestrap. It's the only recovery that allows custom roms on the ME7. Developer is Hashcode.
http://forum.xda-developers.com/showthread.php?t=null
Also a thread about Roms that work with Safestrap. CM is not one of them. But you will enjoy Hyperdrive, Eclipse and others. Everything from a near AOSP to TouchWiz to the max.
Sent from my Hyperdriven Dev Edition Vzw SCH-I545 with KT kernel using Tapatalk 4
wtherrell said:
CM is not one of them.
Click to expand...
Click to collapse
I have an S4 that, of course, before I started this journey I updated to the MI1 build.
Just going through this myself. I have Safe Strap 3.6.2 flashed and am trying to get CM on my phone. Every time I boot up after flashing the ROM it just shows a black screen. I waited around 15 minutes (so far) to no avail. Watching this video makes me think that it is at least possible with Safe Strap and CM 10.1. Is it just not possible on the S4? Am I completely unable to get CM at current?
If this is the case why are they making builds for the S4? Is there an old stock ROM that I could flash, root and then install from or is it just a VZW thing? I don't understand why they'd make a build for a phone that can't install a recovery that can install their ROM...
alburdet619 said:
I have an S4 that, of course, before I started this journey I updated to the MI1 build.
Just going through this myself. I have Safe Strap 3.6.2 flashed and am trying to get CM on my phone. Every time I boot up after flashing the ROM it just shows a black screen. I waited around 15 minutes (so far) to no avail. Watching this video makes me think that it is at least possible with Safe Strap and CM 10.1. Is it just not possible on the S4? Am I completely unable to get CM at current?
If this is the case why are they making builds for the S4? Is there an old stock ROM that I could flash, root and then install from or is it just a VZW thing? I don't understand why they'd make a build for a phone that can't install a recovery that can install their ROM...
Click to expand...
Click to collapse
With the original build, (MDK), there was an exploit that let you bypass the bootloader, so you could flash any ROM. Since the updates, (ME7 and MI1) that exploit has been locked and there is no way, as of now, to bypass the bootloader. Also, there is no way to go back to MDK once the phone has been updated. The only option for ME7 and MI1 users is to use Safestrap, with the appropriate kernel module, and flash TW ROMs only.
alburdet619 said:
I have an S4 that, of course, before I started this journey I updated to the MI1 build.
Just going through this myself. I have Safe Strap 3.6.2 flashed and am trying to get CM on my phone. Every time I boot up after flashing the ROM it just shows a black screen. I waited around 15 minutes (so far) to no avail. Watching this video makes me think that it is at least possible with Safe Strap and CM 10.1. Is it just not possible on the S4? Am I completely unable to get CM at current?
If this is the case why are they making builds for the S4? Is there an old stock ROM that I could flash, root and then install from or is it just a VZW thing? I don't understand why they'd make a build for a phone that can't install a recovery that can install their ROM...
Click to expand...
Click to collapse
It is not possible to install CyanogenMod on any revision later than MDK at the moment.
They're building CM for the S4 for those fortunate enough to have revision MDK, which has a bootloader that can be bypassed.
Aury said:
Can anyone help a noob?
I recently purchased a Galaxy S4 from verizon and rooted it using the VRUAME7Build.
Click to expand...
Click to collapse
I see your question has been answered, let me add a little information that may save you reading a few billion posts here!
The Galaxy S4 has a locked bootloader that cannot be unlocked so far.
There is a workaround called Loki that bypasses the bootloader to allow a new bootloader such as CM or TWRP to be flashed.
The ME7 build "fixed" the exploit that Loki used to bypass the bootloader so you're now stuck with the stock bootloader.
Start reading up on SafeStrap, that allows some TouchWiz ROMs to be flashed to the SD card but, so far, no non-TW ROMs work.
Sorry but at least some devs are still working on unlocking the bootloader, let's hope they are successful.
I've never had any issues flashing ROMs until I tried flashing one of the beta builds of the 4.4.4 Google edition ROM. The creator of the ROM has been having issues with WiFi and data not locking correctly and released an APN zip to possibly resolve the issue. Flashing that zip though, which I'm pretty sure changed the radio, resulted in the phone having connection issues on any ROM. I also noticed that the baseband version was changed from MDK to NC5, so long story short, I used ODIN to revert back to MDK bone stock, reverted back to to MD2 (I believe) to root, then back to MDK.
Here's where I'm a little stumped. I tried to use the ROM manager app to install CWM touch recovery and every time it would say it's successful, but booting into recovery would give me the stock android version, which we all know is pretty useless other than for stock updates and erasing data/cache. So the only way to get CWM recovery installed was to use terminal on the phone to do the Loki flash method. I'm a little out of touch, so can someone explain to me what exactly Loki is other than a "workaround" for the bootloader, how it applies to MDK for running AOSP ROMs without the "unauthorized software" message, and what, if any was the unlocking method for the MDK bootloader? It's been so long that I can't remember how I set everything up initially, and doing a search didn't yield any kind of guide for newbies or those out of touch like myself.
Thanks for taking the time to read and help!
Saint Isaiah said:
I've never had any issues flashing ROMs until I tried flashing one of the beta builds of the 4.4.4 Google edition ROM. The creator of the ROM has been having issues with WiFi and data not locking correctly and released an APN zip to possibly resolve the issue. Flashing that zip though, which I'm pretty sure changed the radio, resulted in the phone having connection issues on any ROM. I also noticed that the baseband version was changed from MDK to NC5, so long story short, I used ODIN to revert back to MDK bone stock, reverted back to to MD2 (I believe) to root, then back to MDK.
Here's where I'm a little stumped. I tried to use the ROM manager app to install CWM touch recovery and every time it would say it's successful, but booting into recovery would give me the stock android version, which we all know is pretty useless other than for stock updates and erasing data/cache. So the only way to get CWM recovery installed was to use terminal on the phone to do the Loki flash method. I'm a little out of touch, so can someone explain to me what exactly Loki is other than a "workaround" for the bootloader, how it applies to MDK for running AOSP ROMs without the "unauthorized software" message, and what, if any was the unlocking method for the MDK bootloader? It's been so long that I can't remember how I set everything up initially, and doing a search didn't yield any kind of guide for newbies or those out of touch like myself.
Thanks for taking the time to read and help!
Click to expand...
Click to collapse
Loki is an exploit that allows the system to bypass bootloader checks and load custom software. If this happens again, restoring an EFS backup should fix your issue.
If you ever need to go back to stock MDK, you no longer need to do the downgrade to the prerelease MDL kernel. Just go to towelroot.com, install the towelroot apk, then hit the make it ra1n button. It's a new root method that came out a few months ago and works for a ton of devices. The easiest way to flash a compatible custom recovery for our device is to download Flashify from the play store and from there you can get the latest TWRP.
joshm.1219 said:
Loki is an exploit that allows the system to bypass bootloader checks and load custom software. If this happens again, restoring an EFS backup should fix your issue.
If you ever need to go back to stock MDK, you no longer need to do the downgrade to the prerelease MDL kernel. Just go to towelroot.com, install the towelroot apk, then hit the make it ra1n button. It's a new root method that came out a few months ago and works for a ton of devices. The easiest way to flash a compatible custom recovery for our device is to download Flashify from the play store and from there you can get the latest TWRP.
Click to expand...
Click to collapse
Gotcha, seems pretty straightforward. Wasn't there an actual unlock method for the bootloader though? I remember getting my download mode to read as custom as well as the boot logo, I just can't remember how and it seems like all traces of how to do it vanished.
Thanks for the help!
Also, what in the world does it mean to "Loki" a ROM after installing it? Kinda confused there
Saint Isaiah said:
Gotcha, seems pretty straightforward. Wasn't there an actual unlock method for the bootloader though? I remember getting my download mode to read as custom as well as the boot logo, I just can't remember how and it seems like all traces of how to do it vanished.
Thanks for the help!
Click to expand...
Click to collapse
No, never an actual bootloader unlock, besides Dev editions that came unlocked. My download mode still says "install custom ROM" or whatever. There's no discernable difference to the end user between an unlocked bootloader and an exploit like the Loki bypass.
joshm.1219 said:
No, never an actual bootloader unlock, besides Dev editions that came unlocked. My download mode still says "install custom ROM" or whatever. There's no discernable difference to the end user between an unlocked bootloader and an exploit like the Loki bypass.
Click to expand...
Click to collapse
OK, and I'm assuming the reason why being on MDK is so important is because upgrading to ME7 patches the vulnerability that can allow the boot loader to be bypassed, forcing you to use safestrap, which results in no custom kernal being able to be used?
And my question above: what does it mean to install, then "Loki" a ROM in the install steps?
Thanks again, you're awesome!
Saint Isaiah said:
OK, and I'm assuming the reason why being on MDK is so important is because upgrading to ME7 patches the vulnerability that can allow the boot loader to be bypassed, forcing you to use safestrap, which results in no custom kernal being able to be used?
And my question above: what does it mean to install, then "Loki" a ROM in the install steps?
Thanks again, you're awesome!
Click to expand...
Click to collapse
Yes exactly, ME7 patched it.
If you flash a TW ROM not built specifically for our device, The ROM (depending on kernel you flashed or if the ROM includes a kernel) may not have the files included to boot on a device with the Loki specific bypass. So you need to flash the " Loki doki zip " after the ROM and before initial boot. You can find the file on Google.
joshm.1219 said:
Yes exactly, ME7 patched it.
If you flash a TW ROM not built specifically for our device, The ROM (depending on kernel you flashed or if the ROM includes a kernel) may not have the files included to boot on a device with the Loki specific bypass. So you need to flash the " Loki doki zip " after the ROM and before initial boot. You can find the file on Google.
Click to expand...
Click to collapse
Awesome, thanks Josh! This might make a great sticky for the "what is Loki?" newvies and explaining the importance of MDK for those still on it and not sure why.
Phone Specs:
Samsung Galaxy S4 Verizon
Model: SCH-1545
Andriod Version: 4.4.2
Ive been trying to install clockwork but so far no luck...ive attempted to use loki method but i get something like loki does not match the device using terminal emulator, odin straight up fails and safestrap says its in installed but i only see the stock recovery. Ive moved on to install rom manager and i see the samsung logo with a lock that is unlocked but the recovery is still stock.
Ive spent a couple days on this so i feel its time to get direct help if anyone's up for it, and thx if give this a read and decided to help
BettermanAtlas said:
Phone Specs:
Samsung Galaxy S4 Verizon
Model: SCH-1545
Andriod Version: 4.4.2
Ive been trying to install clockwork but so far no luck...ive attempted to use loki method but i get something like loki does not match the device using terminal emulator, odin straight up fails and safestrap says its in installed but i only see the stock recovery. Ive moved on to install rom manager and i see the samsung logo with a lock that is unlocked but the recovery is still stock.
Ive spent a couple days on this so i feel its time to get direct help if anyone's up for it, and thx if give this a read and decided to help
Click to expand...
Click to collapse
you can only use safestrap. you cannot flash a ROM with a custom kernel as far as i've heard. you have the knox locked bootloader. you cannot downgrade the bootloader
FordNate said:
you can only use safestrap. you cannot flash a ROM with a custom kernel as far as i've heard. you have the knox locked bootloader. you cannot downgrade the bootloader
Click to expand...
Click to collapse
then do you know how i should install clockwork mod because anytime i try to i get installation complete/successful but nothing changes..(i also attempted to install resurrection remix but got the same result)
BettermanAtlas said:
then do you know how i should install clockwork mod because anytime i try to i get installation complete/successful but nothing changes..(i also attempted to install resurrection remix but got the same result)
Click to expand...
Click to collapse
you cannot install clockwork mod sorry
I've looked through these forums and haven't really gotten any clear answers. I have a Samsung Galaxy S4 SCH-I545 with the VRUFNC5 firmware. I tried to install CWM Recovery using Rom Manager. It looked as if it installed just fine. Says its installed, however, when I boot into recovery, its the stock recovery. I very much want to install CWM recovery on my phone. I would prefer the Touch version, but it's not necessary. Also, I really want to put Lollipop on there too. I'm running stock 4.4.2 now. Most everything I've seen is for every other model of S4 other than mine. Could you please lead me in the right direction if this is at all possible. I would greatly appreciate it.
friedtater22 said:
I've looked through these forums and haven't really gotten any clear answers. I have a Samsung Galaxy S4 SCH-I545 with the VRUFNC5 firmware. I tried to install CWM Recovery using Rom Manager. It looked as if it installed just fine. Says its installed, however, when I boot into recovery, its the stock recovery. I very much want to install CWM recovery on my phone. I would prefer the Touch version, but it's not necessary. Also, I really want to put Lollipop on there too. I'm running stock 4.4.2 now. Most everything I've seen is for every other model of S4 other than mine. Could you please lead me in the right direction if this is at all possible. I would greatly appreciate it.
Click to expand...
Click to collapse
I guess that you are on NC5 bootloader. You will be able to install Safestrap, but you wont be able to run an AOSP roms.
friedtater22 said:
I've looked through these forums and haven't really gotten any clear answers. I have a Samsung Galaxy S4 SCH-I545 with the VRUFNC5 firmware. I tried to install CWM Recovery using Rom Manager. It looked as if it installed just fine. Says its installed, however, when I boot into recovery, its the stock recovery. I very much want to install CWM recovery on my phone. I would prefer the Touch version, but it's not necessary. Also, I really want to put Lollipop on there too. I'm running stock 4.4.2 now. Most everything I've seen is for every other model of S4 other than mine. Could you please lead me in the right direction if this is at all possible. I would greatly appreciate it.
Click to expand...
Click to collapse
Can't run CWM nor TWRP you're only option is Safestrap. However check this ROM out has some Lollipop features etc. Not sure how stable it is though.
http://forum.xda-developers.com/galaxy-s4-verizon/development/rom-kitpop-v1-0-t3019132