I only know enough to be really dangerous.........Anyone with knowledge been playing with Flashfire?
http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Tool Belt said:
I only know enough to be really dangerous.........Anyone with knowledge been playing with Flashfire?
http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Click to expand...
Click to collapse
After initial tests I have moved full speed ahead with FlashFire as a Safestrap replacement on locked bootloader devices that I support, e.g.: http://forum.xda-developers.com/gal...-to-update-to-i337oc3-5-0-1-keeproot-t3075814
It is now up to Dev's to learn its potential and limitations and create safe and responsible guides. It has the ability to flash to the kernel parition so there is risk!
Thanks, I have been following your work on the ATT S4 column, keep at it my friend!
Tool Belt said:
I only know enough to be really dangerous.........Anyone with knowledge been playing with Flashfire?
http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Click to expand...
Click to collapse
It works great! I used it today to reflash NC5, then a ROM
npjohnson said:
It works great! I used it today to reflash NC5, then a ROM
Click to expand...
Click to collapse
Excellent! I am sitting back here at ME7 safestrapped Hyperdrive ver9. Just got away from flashing for....a while....
Flashfire FC's when I attempt a backup from the stock rom, and never gets past enumerating partitions on Hyperdrive.
Tool Belt said:
Excellent! I am sitting back here at ME7 safestrapped Hyperdrive ver9. Just got away from flashing for....a while....
Flashfire FC's when I attempt a backup from the stock rom, and never gets past enumerating partitions on Hyperdrive.
Click to expand...
Click to collapse
Haven't tried backup.
What if you have a non-functioning system (say a bootloop) would it be possible to restore without odin?
joshuabg said:
What if you have a non-functioning system (say a bootloop) would it be possible to restore without odin?
Click to expand...
Click to collapse
No, FF is only accessible via a fully functioning device. Unbricking will require Odin.
It appears that Flashfire has the ability to flash to the kernel partition... Would this include devices with the NC5 locked bootloader? Or would that just brick the device?
SnyderGuy said:
It appears that Flashfire has the ability to flash to the kernel partition... Would this include devices with the NC5 locked bootloader? Or would that just brick the device?
Click to expand...
Click to collapse
See here. These apply to all locked bootloader devices: http://forum.xda-developers.com/showthread.php?p=60070810
After looking around and installing it, I have a quick question.
How is this versus Safestrap? It appears to be more dangerous since it can fail if low memory is available, will cause softbrick if flash kernel partition, and is a little harder to navigate. However, it seems to be better since it can do everything Safestrap can whilst on the system bootup, is non-intrusive at boot pre-splash image, and is built by a bit more reliable developer.
After looking at this thread, it looks like it would be possible to update to an unoffical lollipop build on verzion. Could this be done?
Sorry for so many questions, just trying to see if this is a viable replacement for Safestrap 3.7.5
npjohnson said:
It works great! I used it today to reflash NC5, then a ROM
Click to expand...
Click to collapse
what android version were you on.....if oc1 then how did it downgrade
I thought if attempted through flashfire it would hard brick
:fingers-crossed: hopefuly a downgrade method finally
I am on the NK4 Bootloader, before the OC1 rollback was set, so I can go anything from NC5 through NK4.
No. If you flash an NC5 TAR via FF, and you were previously on OC1, you will 100% hard brick.
Tool Belt said:
I only know enough to be really dangerous.........Anyone with knowledge been playing with Flashfire?
http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Click to expand...
Click to collapse
I've used it on OC1 and installed a ROM and a volume boost mod and so far zero problems!
Sent from my stang5litre Edition 5.0 using XDA Free mobile app
So I'm in a situation with old MK2 firmware and currently using SafeStrap (I don't remember why I wound up using SafeStrap).
I've done so much reading to see if I can't get this thing from MK2 to OF1 safely, but I still don't quite understand if I can use FlashFire or not.
Looking to go to this ROM: http://forum.xda-developers.com/gal...-to-update-to-i545of1-5-0-1-keeproot-t3182544
pkopalek said:
So I'm in a situation with old MK2 firmware, an Unlocked Bootloader, and currently using SafeStrap (I don't remember why I wound up using SafeStrap).
Can FlashFire work just fine on an UNlocked bootlader as well? Or does it require a locked one?
I've done so much reading to see if I can't get this thing from MK2 to OF1 safely, but I still don't quite understand if I can use FlashFire or not.
Looking to go to this ROM: http://forum.xda-developers.com/gal...-to-update-to-i545of1-5-0-1-keeproot-t3182544
Click to expand...
Click to collapse
OF1 is supposed to patch stagefright...SUPPOSED TO. But, the update.zip and the VZW/Samsung documentation tell two different stories. Dates for files/folders in the update.zip from fota do not coincide with any modification Sammy or VZ made, therefore making OF1 nothing more than a wet bandaid.
IMHO...Stick with OC1 (or whatever you desire <OC1), disable auto-retrieve mms thru the stock messaging app settings and, viola...you've got OF1 (pretty much)...
You can use flashfire with unlocked or locked bootloader AFAIK, but as far as I've heard AROMA doesn't play nice with FF. I have flashed kitpop with flashfire and it worked fine.
ATGkompressor said:
OF1 is supposed to patch stagefright...SUPPOSED TO. But, the update.zip and the VZW/Samsung documentation tell two different stories. Dates for files/folders in the update.zip from fota do not coincide with any modification Sammy or VZ made, therefore making OF1 nothing more than a wet bandaid.
IMHO...Stick with OC1 (or whatever you desire <OC1), disable auto-retrieve mms thru the stock messaging app settings and, viola...you've got OF1 (pretty much)...
Click to expand...
Click to collapse
XxD34THxX said:
You can use flashfire with unlocked or locked bootloader AFAIK, but as far as I've heard AROMA doesn't play nice with FF. I have flashed kitpop with flashfire and it worked fine.
Click to expand...
Click to collapse
Thanks for your replies. You two are great.
I'm going to do the FF methods.
Oh damn -- I'm glad I randomly googled the right words first. Looks like you can't go MK2 to 5.0 with FlashFire
http://forum.xda-developers.com/showpost.php?p=60939906&postcount=2
Jeeeezz
So I have a galaxy note 3 sm900v verizon at 5.0....rooted with Arabic tool...locked bootloader tho...can I use flashfire too install a coustom rom?if so how please....
Related
Hi,
So I have a SGS4 with ME7 and and unlocked bootloader. I am looking to upgrade to MJ7(4.3?) and be able to keep my full root. Is there a good way to do such a thing yet? Most info I see says MJ7 is only for safe strap, I have a custom recovery so I am not sure if it will work or if it is worth it. Please advise and help me....
Thank you in advance!!!
If you are on ME7 you only have safestrap, which is not available for MJ7. MJ7 upgrade while retaining root is covered in the general section of this site. There are files you need to download and first install MI1. There are no rom options but the benefit of a rom are little on ME7 as you can't get off TW and are stuck on 4.2.2 becaise of kernel limitations.
Read a bit but I took the update from ME7 after losing MDK due to insurance replacement. Only if you really have a custom recovery such as TWRP or CWM on MDK are you losing much.
Sent from my SCH-I545 using Tapatalk
kdo23 said:
If you are on ME7 you only have safestrap, which is not available for MJ7. MJ7 upgrade while retaining root is covered in the general section of this site. There are files you need to download and first install MI1. There are no rom options but the benefit of a rom are little on ME7 as you can't get off TW and are stuck on 4.2.2 becaise of kernel limitations.
Read a bit but I took the update from ME7 after losing MDK due to insurance replacement. Only if you really have a custom recovery such as TWRP or CWM on MDK are you losing much.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I have CWM Touch Recovery V1.0.3.5 with my ME7 phone so it sounds like I should probably not take the update... I am pretty sure I don't have safestrap. I was on MDK then updated to ME7 and kept my unlocked bootloader and root. I just wish there was a way I could get 4.3 or 4.4... I will keep reading and searching... Thank you.
sonnycohopie said:
I have CWM Touch Recovery V1.0.3.5 with my ME7 phone so it sounds like I should probably not take the update... I am pretty sure I don't have safestrap. I was on MDK then updated to ME7 and kept my unlocked bootloader and root. I just wish there was a way I could get 4.3 or 4.4... I will keep reading and searching... Thank you.
Click to expand...
Click to collapse
You updated the radio I take it? That will show you on ME7 but have the MDK bootloader. Thus leaving your TWRP intact.
So anyway, I'm looking for the same thing. Not happening right now
kdo23 said:
If you are on ME7 you only have safestrap, which is not available for MJ7. MJ7 upgrade while retaining root is covered in the general section of this site. There are files you need to download and first install MI1. There are no rom options but the benefit of a rom are little on ME7 as you can't get off TW and are stuck on 4.2.2 becaise of kernel limitations.
Read a bit but I took the update from ME7 after losing MDK due to insurance replacement. Only if you really have a custom recovery such as TWRP or CWM on MDK are you losing much.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Up until today I had ME7 *with* CWM Recovery. I have no idea how that happened but I think it had something to do with flashing Hyperdrive while I was on MDK. I flashed a ton of ROM's through CWM since having ME7. However, lately I started to have a few bugs that seemed to carry over even after flashing a new ROM (like intermittent boot loops) so I decided to go back to a factory image (without knowing the limitations of ME7). Since I was on ME7, my understanding is that I had to flash an ME7 factory image, which I did and *now* I can't get recovery back, aside from Safestrap. It's a bit of a bummer but I just wanted to post to point out that it is possible to have ME7 and a custom recovery, it just seems like it isn't possible to flash a custom recovery *after* you have ME7. If you got it, keep it.
Super Sam Galaxy said:
Up until today I had ME7 *with* CWM Recovery. I have no idea how that happened but I think it had something to do with flashing Hyperdrive while I was on MDK. I flashed a ton of ROM's through CWM since having ME7. However, lately I started to have a few bugs that seemed to carry over even after flashing a new ROM (like intermittent boot loops) so I decided to go back to a factory image (without knowing the limitations of ME7). Since I was on ME7, my understanding is that I had to flash an ME7 factory image, which I did and *now* I can't get recovery back, aside from Safestrap. It's a bit of a bummer but I just wanted to post to point out that it is possible to have ME7 and a custom recovery, it just seems like it isn't possible to flash a custom recovery *after* you have ME7. If you got it, keep it.
Click to expand...
Click to collapse
You didn't have stock me7 which was my meaning. You had an me7 rom I think is what you're saying.
Sent from my SCH-I545 using Tapatalk
kdo23 said:
You didn't have stock me7 which was my meaning. You had an me7 rom I think is what you're saying.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Well, it wasn't stock ME7 for sure. I think it changed to ME7 when I first flashed Hyperdrive, but was that way for a while on every ROM I flashed after Hyperdrive so whatever change Hyperdrive made seemed to be permanent. Or else I may have just been flashing ROM's that were ME7 by coincidence - do all ROM's explicitly set the baseband or do some just use whatever is already on the device? I don't really understand basebands too well. Anyway, sorry about the mix-up, I wasn't aware you were referring to stock. I sure hope that someone is able to figure out a workaround that allows for a custom recovery because I really like KitKat and I suppose we won't be seeing any TW based KitKat ROM's until Samsung releases an update first. My understanding is that Safestrap only works with TW.
I find a certain degree of irony in the fact that I've never permanently damaged a device when rooting or flashing ROM's (which is pretty good for a noob like me), yet I've done something even worse just by inadvertently allowing an update that came straight from the manufacturer! Why do they have to make things so complicated? :crying:
Super Sam Galaxy said:
Well, it wasn't stock ME7 for sure. I think it changed to ME7 when I first flashed Hyperdrive, but was that way for a while on every ROM I flashed after Hyperdrive so whatever change Hyperdrive made seemed to be permanent. Or else I may have just been flashing ROM's that were ME7 by coincidence - do all ROM's explicitly set the baseband or do some just use whatever is already on the device? I don't really understand basebands too well. Anyway, sorry about the mix-up, I wasn't aware you were referring to stock. I sure hope that someone is able to figure out a workaround that allows for a custom recovery because I really like KitKat and I suppose we won't be seeing any TW based KitKat ROM's until Samsung releases an update first. My understanding is that Safestrap only works with TW.
I find a certain degree of irony in the fact that I've never permanently damaged a device when rooting or flashing ROM's (which is pretty good for a noob like me), yet I've done something even worse just by inadvertently allowing an update that came straight from the manufacturer! Why do they have to make things so complicated? :crying:
Click to expand...
Click to collapse
Baseband is separate, your rom base is what we were referring to. The baseband change happened with a file you flashed for sure but likely not hyperdrive but a radio file. With a custom recovery you could have had mj7 baseband and custom recovery. Look at build number in the future.
Sent from my SCH-I545 using Tapatalk
Edit: build number can change too with a rom. Mdk is the only starting stock firmware which can be exploited to allow a custom recovery. Since you had one it meant you rooted on mdk and should not have odined to a later release.
Super Sam Galaxy said:
Up until today I had ME7 *with* CWM Recovery. I have no idea how that happened but I think it had something to do with flashing Hyperdrive while I was on MDK. I flashed a ton of ROM's through CWM since having ME7. However, lately I started to have a few bugs that seemed to carry over even after flashing a new ROM (like intermittent boot loops) so I decided to go back to a factory image (without knowing the limitations of ME7). Since I was on ME7, my understanding is that I had to flash an ME7 factory image, which I did and *now* I can't get recovery back, aside from Safestrap. It's a bit of a bummer but I just wanted to post to point out that it is possible to have ME7 and a custom recovery, it just seems like it isn't possible to flash a custom recovery *after* you have ME7. If you got it, keep it.
Click to expand...
Click to collapse
Absolutely impossible to have a custom recovery on an ME7 boot loader. You could've flashed a ME7 radio or a ME7 based rom such as HyperDrive but your boot loader is still MDK. Which is why you lost your recovery, you flashed the wrong factory image.
Sent from my SCH-I545 using XDA Premium 4 mobile app
kdo23 said:
Baseband is separate, your rom base is what we were referring to. The baseband change happened with a file you flashed for sure but likely not hyperdrive but a radio file. With a custom recovery you could have had mj7 baseband and custom recovery. Look at build number in the future.
Sent from my SCH-I545 using Tapatalk
Edit: build number can change too with a rom. Mdk is the only starting stock firmware which can be exploited to allow a custom recovery. Since you had one it meant you rooted on mdk and should not have odined to a later release.
Click to expand...
Click to collapse
I figured out the part about not flashing to a later release after the fact, unfortunately. It was simply a matter of not thoroughly researching and it's a pretty big bummer now because I can't flash! But I suppose worse things can come of not researching, like bricking and thankfully that hasn't happened yet (though I'm certainly going go be more careful in the future). Thanks for explaining about all the baseband/radio stuff, that is a bit over my head. Sure hope an exploit for ME7 (or a way to revert to MDK) is found soon, though from the sound of it that isn't likely.
I was one of the idiots that accidentally upgraded to the newest firmware when it first came out. My device is totally rooted, but I've been reading that I'm required to use things such as SafeStrap or Loki to install custom roms. I'm not sure if this is still the case as its been months since this was discovered. I've been trying to search the forums extensively for a fix, but I've been unable to find one. One thing I came across: here seems to be a very simple way to install TWRP on the Galaxy S4, however, I don't wan to run the risk of bricking my phone and being SOL because I have ****ty firmware and no way to custom recover my phone.
Point blank, would I be able to install TWRP manager via GooManager given that I've updated to NC5? Or even if not, what are my options for custom recovery/roms? End game, I want to walk away with 5.0.1 GPE or Cyanogenmod 12. Hopefully.
I'd really appreciate any and all help. Attached is a screenshot of my phone information.
zQueal said:
I was one of the idiots that accidentally upgraded to the newest firmware when it first came out. My device is totally rooted, but I've been reading that I'm required to use things such as SafeStrap or Loki to install custom roms. I'm not sure if this is still the case as its been months since this was discovered. I've been trying to search the forums extensively for a fix, but I've been unable to find one. One thing I came across: here seems to be a very simple way to install TWRP on the Galaxy S4, however, I don't wan to run the risk of bricking my phone and being SOL because I have ****ty firmware and no way to custom recover my phone.
Point blank, would I be able to install TWRP manager via GooManager given that I've updated to NC5? Or even if not, what are my options for custom recovery/roms? End game, I want to walk away with 5.0.1 GPE or Cyanogenmod 12. Hopefully.
I'd really appreciate any and all help. Attached is a screenshot of my phone information.
Click to expand...
Click to collapse
Once you updated to anything past MDK there's no going back . Safestrap is the only option to install Touchwiz ROMS.
scrillakev said:
Once you updated to anything past MDK there's no going back . Safestrap is the only option to install Touchwiz ROMS.
Click to expand...
Click to collapse
Damn! That's what I figured. I followed [this guide](https://www.youtube.com/watch?v=BLHZfPwLkPM) and installed the SafeStrap APK, but stopped at the "install recovery" step. I've been reading that this can soft brick your phone. Do you have any input? Is it safe to do? If it does brick my phone will I be able to factory reset with Odin?
Sorry for the barrage of questions, I'm a bit of a noob.
-----------------------------------------------------------------------
EDIT:
Well, I decided to go ahead with it. It worked fine. I rebooted to SafeStrap and went right to do a backup. It failed. I tried to reboot into my stock rom, and it was 0MB. I really might blow up Verizon HQ.
zQueal said:
Damn! That's what I figured. I followed [this guide](https://www.youtube.com/watch?v=BLHZfPwLkPM) and installed the SafeStrap APK, but stopped at the "install recovery" step. I've been reading that this can soft brick your phone. Do you have any input? Is it safe to do? If it does brick my phone will I be able to factory reset with Odin?
Sorry for the barrage of questions, I'm a bit of a noob.
-----------------------------------------------------------------------
EDIT:
Well, I decided to go ahead with it. It worked fine. I rebooted to SafeStrap and went right to do a backup. It failed. I tried to reboot into my stock rom, and it was 0MB. I really might blow up Verizon HQ.
Click to expand...
Click to collapse
I never used SafeStrap so I doubt I will be much help. But once you rebooted your stock ROM is no longer there? Might have to just flash a stock image via ODIN and try again. Verizon isn't going to help you either with modding your phone, XDA is the place to be.
Has there been anything new since this thread was posted or is it impossible still?
mcbeat257 said:
Has there been anything new since this thread was posted or is it impossible still?
Click to expand...
Click to collapse
Sorry buddy you're SOL
Sent from my SCH-I545 using XDA Free mobile app
If you are rooted use a terminal editor app and type:
getprop ro.bootloader
If it says anything other than I545VRUAMDK your only choice is SafeStrap.
That means if you bought an S4 and it came with MK1, NC5, NK1, or anything other than MDK you cannot flash a custom recovery. The same applies if you took an OTA from VZW. This has been stated 1000's of times here.
Hint:
Look on the box that your S4 came in and read the last three characters where it says what build the phone has.
mcbeat257 said:
Has there been anything new since this thread was posted or is it impossible still?
Click to expand...
Click to collapse
Keep checking up on SS they are working on the ability to also use custom kernels on top which would make it essentially as efficient as a custom recovery, with some storage loss.
safestrap version
Well, I decided to go ahead with it. It worked fine. I rebooted to SafeStrap and went right to do a backup. It failed. I tried to reboot into my stock rom, and it was 0MB. I really might blow up Verizon HQ.[/QUOTE]
***Make sure you are using the correct version of safestrap for your current baseband
another good app from the google play store to download is samsung info
I have used safestrap in the past as I was in the same scenario as you. I currently now have a MDK phone
Illogi.xbone said:
Keep checking up on SS they are working on the ability to also use custom kernels on top which would make it essentially as efficient as a custom recovery, with some storage loss.
Click to expand...
Click to collapse
How come they haven't been able to unlock the bootloader when only the build version is changing......
There should have been an exploit awhile ago....and why haven't they made an odin option for MDK yet?
mcbeat257 said:
How come they haven't been able to unlock the bootloader when only the build version is changing......
There should have been an exploit awhile ago....and why haven't they made an odin option for MDK yet?
Click to expand...
Click to collapse
The exploit was weeded out after MDK
Sent from my SCH-I545 using XDA Free mobile app
The bootloader was never "unlocked" on MDK, there was just an exploit available that allowed the installation of a custom recovery. That exploit was closed in the first update from MDK and a new one has not been discovered. The bootloader itself has some pretty strong encryption so it may never be unlocked.
This was rooted a long while back and now with the OTA update I have i545vrufnk4 baseband version but I can't install lollipop. I don't care about lollipop I just don't want to be prompted to install it when it doesn't work (thanks knox).
What are my options? Odin? Rooting? I tried towelroot and it didn't work this time around. please help
bump
Well, nk4 doesn't have root. NK4 is the first step to lollipop. The qfuse isn't blown yet, so you can full wipe back to nc5, get root and safestrap. You can't disablet he update thing without root, so you have two options:
A)Odin back to nc5, then disable the OTA
B)Live with the notification
-I believe if you hold on the thing, click on settings, and disable the notification, that will stop any popup. I haven't done this in a while though.
XxD34THxX said:
Well, nk4 doesn't have root. NK4 is the first step to lollipop. The qfuse isn't blown yet, so you can full wipe back to nc5, get root and safestrap. You can't disablet he update thing without root, so you have two options:
A)Odin back to nc5, then disable the OTA
B)Live with the notification
-I believe if you hold on the thing, click on settings, and disable the notification, that will stop any popup. I haven't done this in a while though.
Click to expand...
Click to collapse
When I turn on the phone it shows custom with the unlock picture so I thought that meant the fuse was blown. I
No, it won't tell you if the qfuse is blown. That just means it detects root access on boot, and the system status is unnoficial
Just downgrade to NC5. There is a thread for that. Install towelroot and then using TB, freeze SDM. Good to go.
Sent from my SCH-I545 using Tapatalk
^^
That was the process to freeze OTA
XxD34THxX said:
^^
That was the process to freeze OTA
Click to expand...
Click to collapse
Does the phone need to be rooted to use odin? I saw a video on rootjunky where he does it pretty quick and easy (https://www.youtube.com/watch?v=GL8XwuRYoWU)
thisdarnphone said:
Does the phone need to be rooted to use odin? I saw a video on rootjunky where he does it pretty quick and easy (https://www.youtube.com/watch?v=GL8XwuRYoWU)
Click to expand...
Click to collapse
Root not required to odin.
Sent from my SCH-I545 using XDA Free mobile app
You just need towelroot
XxD34THxX said:
You just need towelroot
Click to expand...
Click to collapse
Towelroot doesn't work anymore for me. It did once but now it fails(this phone isn't currently supported) and I tried several codes. Is there something I should know before I try odin?
I guess what I'm asking is why do I need to root?
Secondly, does odin no longer work if I upgrade to lollipop down the road?
What firmware should I put on this phone?
You will have to use Odin to go back to nc5, with a FULL WIPE
Then, you have several options:
1)Use the stock deodex lollipop with Root
2)Echoe ROM v49(no dev though, so no more updates)
3)Super6(s6 port)
XxD34THxX said:
You will have to use Odin to go back to nc5, with a FULL WIPE
Then, you have several options:
1)Use the stock deodex lollipop with Root
2)Echoe ROM v49(no dev though, so no more updates)
3)Super6(s6 port)
Click to expand...
Click to collapse
I saw something about that, I was reading the Odin guide where they said after odin shows the green "passed", then you need to reboot the phone holding the power home and volume up keys and pick the "factory reset / full wipe" option. if you don't do that does that brick the phone?
appreciate the help, it's my first time but I'm picking this up quick
No. The Full Wipe will wipe it for you and it will automatically reboot the phone. It will be in an "out of box" state.
XxD34THxX said:
No. The Full Wipe will wipe it for you and it will automatically reboot the phone. It will be in an "out of box" state.
Click to expand...
Click to collapse
Oh then if I were to do a full wipe, then I wouldn't need Odin? That would take me back to MK2 from back in the day?
no. If you get the nc5 file, it will upgrade/downgrade you to nc5, which is 4.4 Kitkat
XxD34THxX said:
no. If you get the nc5 file, it will upgrade/downgrade you to nc5, which is 4.4 Kitkat
Click to expand...
Click to collapse
I'm sorry I just feel like I'm missing some key concept here.
So just to clear up my understanding here are the following firmwares avaiable for my galaxy s4 i-545
i545vrugOC1 5.0.1
i545vrufnk1 4.4.2
i545vrufng6 4.4.2
i545vrufnc5 4.4.2
i545vruemk2 4.3
i545vrudmi1 4.2
My phone says it's running VRUFNK4. I'm guessing that's the temporary OTA (1/2) upgrade.
Am I right?
Is that why you want me to flash NC5 and is that why if I do a factory reset using the home and volume keys it won't do anything but just keep me where I am now? Why not an NG6 or an MK2 for that matter?
I'm sure a lot of people have these questions I just can't find it anywhere. I just don't want to brick my phone (is that permanent?)
nk4 is part one of two yes.
Even if you do a factory reset, it still won't update because you once rooted, and knox takes note of this, and will block any OTA. nc5 is the last firmware that had towelroot working. ng6 doesn't work with towelroot. I don't see why you would go any further back since the ROMs are based off of nc5.
XxD34THxX said:
nk4 is part one of two yes.
Even if you do a factory reset, it still won't update because you once rooted, and knox takes note of this, and will block any OTA. nc5 is the last firmware that had towelroot working. ng6 doesn't work with towelroot. I don't see why you would go any further back since the ROMs are based off of nc5.
Click to expand...
Click to collapse
Ok that makes sense, I thought for a minute the phone wasn't capable of going back to an earlier version because it had a different boot loader? is that not the case?
That is only the case once you go to 0C1. It is not the bootloader. It is because a physical qfuse is blown, and it has two values, 0(unblown) and 1(blown). If it reads as one, no going back to an older version.
I've been having some terribly sluggish issues lately. Lagging when I text, browse the web, even listen to music.
I honestly do not remember which method I used to root, but I rooted & kept the stock rom. I just deleted the bloat.
Not sure if this will help
http://i.imgur.com/L9prnWv.png
I'm at a point where the lagging is really irking me, but I'm not sure which route I should go.
Since I'm rooted, can I just go ahead with the OTA update without any issues? If so, is there a method to root on lollipop?
If not...Should I just go ahead and flash another rom?
Don't take the ota! Follow he thread about upgrading to 5.01 keeping root! Totally worth going to LP. The speed is great! Give it a shot.
Sent from my SCH-I545 using Tapatalk
This one? http://forum.xda-developers.com/gal...-to-update-to-i545oc1-5-0-1-keeproot-t3096558
yes, that one
XxD34THxX said:
yes, that one
Click to expand...
Click to collapse
Did that, and it says i'm still on 4.4.2. Very strange.
I'm still getting the pop up for the OTA
Make sure to back up any data and do a full wipe to nc5. That can make a difference. Or, Odin back to nc5, and use the Echoe ROM or the Super6 ROM, both of which are on Lollipop.
XxD34THxX said:
Make sure to back up any data and do a full wipe to nc5. That can make a difference. Or, Odin back to nc5, and use the Echoe ROM or the Super6 ROM, both of which are on Lollipop.
Click to expand...
Click to collapse
This is all foreign language to me
Sorry.
OK, get a program called odin. It is leaked Samsung software that allows to flash stock firmware on your phone. You have to flash the stock nc5 firmware with this and THEN continue the upgrade to lollipop
Laziness and not knowing much has lead me to not doing anything about the issue until now.
The phone gets slower by the day, so it's time for a change.
I'd like to flash this rom http://forum.xda-developers.com/showthread.php?t=2550770 but i'm not too sure if I can flash this via the stock recovery?
If not, how would I go about installing TWRP? I did try to search, but the page kept timing out.
DO NOT TRY TO INSTALL TWRP. YOU WILL BRICK. Thanks to Verizon, we have a locked bootloader, which means we only have Safestrap and Flashfire. SS is based off of TWRP, but is a really really really gimped version. Flashfire is an app that functions like a recovery.
You cannot install that ROM at all, because of this POS bootloader.
What you CAN DO, is install Roms such as Eclipse,Kitpop,Hyperdrive, and Stang's 5.0.1 ROM.
OR, you could do the OTA with root method.
Warning: VRUGOC1 is impervious to previous bootloader bypass methods, and cannot be downgraded. Proceed with caution.
I managed to hose my phone while rooting it somehow, so I had to track down the factory image for I545VRUGOC1 / I545VZWGOC1. To actually flash it, I had to use Odin 3.10.6 rather than 3.09 for some reason, which is available in the links below. I also replaced Odin's SS_DL.dll with the one from the zip that contains the tar file, but I'm not sure if that was necessary.
Hope this helps anyone else from who's stuck
TAR
https://mega.nz/#!T0tTDZKA!tIw4ebWEWhsTJWTbyWVx9e07aSBSc_1_Xm2mWWkdu8I
Mirror: http://upple.it/4b1331ec4f4dd04e/VZW-I545VRUGOC1-20150502144520.zip
Slower / crappier mirrors I found in case the above doesn't work:
http://rapidgator.net/file/6f4fd8106796c1bba92dd20a7b5a5c51
http://uploaded.net/file/zcbqwyz5
Odin
http://odindownload.com/download/Odin3_v3.10.6.zip
Mirror: https://mega.nz/#!qh9UTJ6Q!gLDkj2xwXRb8Wa2YTbPODpdrhqowK-s6eZjXI_bTrhQ
kd- said:
Warning: VRUGOC1 is impervious to previous bootloader bypass methods. Proceed with caution.
Click to expand...
Click to collapse
Thanks! I found the file here too:
http://d-h.st/LNQV
My question is, I have a Kitkat Verizon phone here, I assume upgrading it restricts custom ROMs that can be loaded to it?
Thanks for another mirror - the more the better
Yes, I don't think any current custom ROMs work with the VRUGOC1 bootloader, etc. FlashFire has worked for a couple experiments I've run (flashing wireless hotspot fix, for example), but I'm hesitant to flash anything more substantial. I have not tried SafeStrap but I have not seen anything about it working yet.
kd- said:
Thanks for another mirror - the more the better
Yes, I don't think any current custom ROMs work with the VRUGOC1 bootloader, etc. FlashFire has worked for a couple experiments I've run (flashing wireless hotspot fix, for example), but I'm hesitant to flash anything more substantial. I have not tried SafeStrap but I have not seen anything about it working yet.
Click to expand...
Click to collapse
muniz_ri has posted a stock, de-odexed (and odexed, too of course) that should work with OC1 bootloader (it doesn't have a bootloader in it, so the current bootloader should stay)
http://forum.xda-developers.com/gal...ment/rom-i545oc1-5-0-1-100-stock-mdk-t3097902
I haven't installed flashfire yet, but i am on OC1 and already went through the rooting process.
Does this boot if I flash it and the NK4 bootloader?
Oishikatta said:
Does this boot if I flash it and the NK4 bootloader?
Click to expand...
Click to collapse
muniz_ri has a tar with the oc1 build and the nk4 bootloader, look in either general or Android development
^^
It's in android development. Only two or three ROMs work on OC1(at most). I only know of one confirmed.
XxD34THxX said:
^^
It's in android development. Only two or three ROMs work on OC1(at most). I only know of one confirmed.
Click to expand...
Click to collapse
muniz has a stock rooted ROM for the oc1 people, which makes sense if you're going from stock. you can flash deodexed ROM and be able to use xposed framework
skepticmisfit said:
muniz has a stock rooted ROM for the oc1 people, which makes sense if you're going from stock. you can flash deodexed ROM and be able to use xposed framework
Click to expand...
Click to collapse
Yep, it works just fine, flashed with FlashFire.
https://docs.google.com/file/d/0B4RU_ZH5QUASaU9LcDJ3WWZfdXM/edit?usp=docslist_api&pli=1 I found it here two
Can somebody please help me? First, my phone is locked and I was in NK1, so I decided to flash OC1 by the flashfire method (I don't remember who's the author of the topic), everything went fine and I started to use lollipop, but then I was about to sell my phone and I went to settings, then factory reset and the phone restarted, wiped data and cache by itself and then turned on, I thought everything was ok, but then it just stayed in the samsung's wizard screen, it never passed from that screen. So, I decided to manually enter recovery and do a factory reset again, but the result was the same. In order to unbrick the phone I had to use odin and install the NC5 original firmware .
So, my question is, If I want to install lollipop and I don't care to stay with an unlockable bootloader I justt need to use this Firmware and install it through odin? Or do I need to have an specific firmware (e.g nc5, nk1) and unlocked bootloader?
bayron_olaff said:
Can somebody please help me? First, my phone is locked and I was in NK1, so I decided to flash OC1 by the flashfire method (I don't remember who's the author of the topic), everything went fine and I started to use lollipop, but then I was about to sell my phone and I went to settings, then factory reset and the phone restarted, wiped data and cache by itself and then turned on, I thought everything was ok, but then it just stayed in the samsung's wizard screen, it never passed from that screen. So, I decided to manually enter recovery and do a factory reset again, but the result was the same. In order to unbrick the phone I had to use odin and install the NC5 original firmware .
So, my question is, If I want to install lollipop and I don't care to stay with an unlockable bootloader I justt need to use this Firmware and install it through odin? Or do I need to have an specific firmware (e.g nc5, nk1) and unlocked bootloader?
Click to expand...
Click to collapse
Yes, that sounds correct. Personally, I wouldn't flash the OC1 factory image unless you have to - I'd flash the NK1 image, which should reset everything, then upgrade to Lollipop using a method that doesn't upgrade the bootloader so whoever gets the phone next can downgrade if they want to.
Can anyone confirm the mega link is a no-wipe oc1 package?
persdata.img doesnt appear in it just making sure.
Edit : been tested it appears to be a no wipe Odin package