Since Verizon boot-loader MJ7 can't be unlocked and custom recovery can't be installed, have anyone tried so called "dirty installation" of a Custom ROM over the existing Official Verizon firmware?
I have Verizon I545VRUEMJ7 and I am particularly looking for the ROM with Wi-Fi Calling feature (lousy connection at home). I switched to Family-Mobile who's hanging on T-Mobile network, so T-Mobile wi-fi calling should work for me.
Does anyone have experience to flash any Custom ROMs over Verizon I545VRUEMJ7 without a custom recovery (CWM of TWRP) installed. Should be data cleaned up first, some apps maybe disabled or deleted, like KNOX, or Verizon security for instance. Any advices?
cromler said:
Since Verizon boot-loader MJ7 can't be unlocked and custom recovery can't be installed, have anyone tried so called "dirty installation" of a Custom ROM over the existing Official Verizon firmware?
I have Verizon I545VRUEMJ7 and I am particularly looking for the ROM with Wi-Fi Calling feature (lousy connection at home). I switched to Family-Mobile who's hanging on T-Mobile network, so T-Mobile wi-fi calling should work for me.
Does anyone have experience to flash any Custom ROMs over Verizon I545VRUEMJ7 without a custom recovery (CWM of TWRP) installed. Should be data cleaned up first, some apps maybe disabled or deleted, like KNOX, or Verizon security for instance. Any advices?
Click to expand...
Click to collapse
Won't work
Sent from my SCH-I545 using Tapatalk
cromler said:
Since Verizon boot-loader MJ7 can't be unlocked and custom recovery can't be installed, have anyone tried so called "dirty installation" of a Custom ROM over the existing Official Verizon firmware?
I have Verizon I545VRUEMJ7 and I am particularly looking for the ROM with Wi-Fi Calling feature (lousy connection at home). I switched to Family-Mobile who's hanging on T-Mobile network, so T-Mobile wi-fi calling should work for me.
Does anyone have experience to flash any Custom ROMs over Verizon I545VRUEMJ7 without a custom recovery (CWM of TWRP) installed. Should be data cleaned up first, some apps maybe disabled or deleted, like KNOX, or Verizon security for instance. Any advices?
Click to expand...
Click to collapse
Since the bootloader is locked, you can not flash custom firmware. If Hashcode gets Safestrap working on MJ7, you may be able to flash a ROM that does what you want, but not today.
Related
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.
Hi all,
Today I set aside my 900T and purchased a 900V on a contract. I got it home and Rooted it within minutes using Towel Root. I'm not 100% sure about Safestrap. I have never owned a locked bootloader phone before this, so this is new territory for me.
I want to be able to install a Modded Stock ROM at the very least, safely. I would also like a Custom Recovery for Nandroid backups.
Does anyone have any suggestions, tips or advice they may want to share? My 900T was owned outright, this V is under contract (no warranty obviously) so I just want to be that much more safe is all. The Rooting process was easy peasy, which surprised me. Is there anything I should be aware of when I install SafeStrap?
Thanks everyone. Glad to be back on the Verizon Network again.
Welcome to the locked bl club. Install safe strap. Download any TouchWiz rom and reboot. At the ss splash screen tap recovery. It's like twrp. Backup. Then do a factory reset. Install rom. Reboot to download mode. Odin the nc2 kernel. Reboot and enjoy!
What's gained or lost by flashing the NC2 kernel? Just curious. It's on build NC4 now.
Ed Murray said:
What's gained or lost by flashing the NC2 kernel? Just curious. It's on build NC4 now.
Click to expand...
Click to collapse
You are already on nc4 so don't bother with nc2 it is of no use to you. The good news is that you can use titanium backup to debloat your stock setup.
us cellular just sim unlocked my note 3 (android 4.4.2 NG5 stock unrooted rom) phone
of course the gsm radios are still disabled
I know this phone uses a sprint (hltespr) recovery (twrp for me) and I was wondering if I can do a radio swap from hltespr to hlteusc using odin after im rooted and also have the hltespr spring kitkat recovery up and running
I would really just like to convert this whole phone to a Verizon or Sprint knowing I would not be able to use it on Sprint or Verizon anyhow
this would allow me to use it as a GSM device if everything went correctly
can anyone tell me how this process can be done (either through jtag or radio swap)
thank-you
I really did not know what to title this, here goes:
I have a Verizon SGS 4 (SCH-I545), running stock 4.4.2, no custom recovery (am currently running the stock recovery B.S.), bootloader I545VRUFNK4, build ID KOT49H.I545VRUFNK4, release date 4/26/13 & have been rooted with KingRoot V. 4.8.0135 and is unlocked (haven't really any idea what that means, upon boot-up it shows an unlocked lock icon and says CUSTOM, the dealer I bought it from, just a shop where they buy & sell new/used phones, said that it is unlocked for use on any carrier I want.)
Now I don't know how important, if at all, all of that is but I want to update to the most up-to-date OS, reroot & maybe start flashing new custom roms.
The problem is I don't have access to a computer without install restrictions, meaning I can download things but I can't install them without admin name & password trying it directly from the settings (Settings/More/Software update) it keeps saying service unavailable...
I'm lost, is there any way to update via stock recovery or install a custom recovery (TWRP/CWM) via stock recovery or a root app?
I would suggest you to upgrade your phone with a custom rom, elseway if you do it with any official update your bootloader will be upgraded and there are a lot of cons with that.
We cannot have TWRP, CWM or other recovery (thanks to the bootloader), so the best you can do it's getting SafeStrap and then flash any of these custom roms:
stang5litre Ediition 5.0
Albe95 S6 FULL PORT 4.7
Albe95 ASTRA v2 Note 5 PORT
(I listed those because you want to update your phone). You can find SafeStrap and the roms in Verizon Samsung Galaxy S 4 Android Development sub-forum
SafeStrap must not be compatible with my phone cause I tried to use it multiple times but it is not installing any recovery, I'm still stuck on stock recovery.
AlphaTekk said:
SafeStrap must not be compatible with my phone cause I tried to use it multiple times but it is not installing any recovery, I'm still stuck on stock recovery.
Click to expand...
Click to collapse
I'm in the same bootloader so you should be able to install it, you just need SuperSU as your superuser app and busybox
Busybox, ya, I have it and ran it but KingRoot installed it's own supersu thing and it won't let me switch, if there'sa way to switch to supersu from the Play store, how?
The recovery is being overwritten by a script in the system. The title of the file is..
Install.recovery.sh
Rename this file with adding ".bak" then reinstall safestrap
Sent from my SCH-I545 using Tapatalk
I searched Root Explorer but have no idea where this is found, maybe you could point me in the right direction.
Ok, my phone's settings say I545VRUFNK1 for baseband but the build number says KOT49H.I545VRUFNK4 and Samsung Smart Switch comes up with FNK4 (VZW)! It is a Verizon SCH-I545 but how can I update it without Smart Switch cause it keeps saying its up to date?
Can I use Odin and what recovery would I use with Odin?