[Q] Safestrap questions - Verizon Samsung Galaxy S 4

Thanks for the helpful responses.
For anyone viewing this I was attempting to consolidate my 5 hours of reading into a nutshell.

Yes me7 is so far not vulnerable for romming but safestrap is a option soon to be for all me7 users. Big mistake if you wanted a bootloader workaround like loki to have custom recovery. I mean we can't say to claim the device defective as that can be seen as warranty fraud but your actions..
Sent from my SCH-I545 using Tapatalk 4

Addiso said:
Yes me7 is so far not vulnerable for romming but safestrap is a option soon to be for all me7 users. Big mistake if you wanted a bootloader workaround like loki to have custom recovery. I mean we can't say to claim the device defective as that can be seen as warranty fraud but your actions..
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Thanks for the response. So then nothing can be flashed via Odin aside from a pure stock ME7 ROM?
Sent from my SCH-I545 using Tapatalk 2

AndroidSlave said:
Thanks for the response. So then nothing can be flashed via Odin aside from a pure stock ME7 ROM?
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Yep thats all that can be flashed in odin. On the s3 you could flash custom recovery via odin but that required an unlocked bootloader.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.

Related

System recovery opened for me today is that the same as bootloader?

I was messing around with optimizing my vruame7 build gs4 today and i opened system recovery? is that the same as bootloader? In tiny blue letters at top left it said system recovery.
somniferumrex said:
I was messing around with optimizing my vruame7 build gs4 today and i opened system recovery? is that the same as bootloader? In tiny blue letters at top left it said system recovery.
Click to expand...
Click to collapse
The bootloader is basically the ''set of instructions'' the phone uses to boot. Usually it instructs the device to boot the os kernel or the recovery environment. The bootloader loaded the system recovery because you either held volume up + power when booting, ran the reboot recovery command, accepted the ota, or your device was unable to load the os.
Sent from my XT912 using xda app-developers app
No recovery is not the same as the bootloader. Here is an explanation of what exactly it is
http://m.androidcentral.com/what-recovery-android-z
Just as a heads up im going to throw it out there. Currently there is no way to flash a custom recovery on the me7 firmware.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
Just as a heads up im going to throw it out there. Currently there is no way to flash a custom recovery on the me7 firmware.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
I thought you could use Odin to flash a hacked version of ME7?
Sent from my XT926 using Tapatalk 4
Xplorer4x4 said:
I thought you could use Odin to flash a hacked version of ME7?
Sent from my XT926 using Tapatalk 4
Click to expand...
Click to collapse
No, once on the me7 ota youre stuck without a custom recovery/roms. To flash an me7 based rom you have to be on mdk prior.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
No, once on the me7 ota youre stuck without a custom recovery/roms. To flash an me7 based rom you have to be on mdk prior.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for clearing that up. Not trying to thread jack but seemed l I'm me a good place to ask. What's the progress looking like towards custom recovery on ME7?
Sent from my XT926 using Tapatalk 4
Xplorer4x4 said:
Thanks for clearing that up. Not trying to thread jack but seemed l I'm me a good place to ask. What's the progress looking like towards custom recovery on ME7?
Sent from my XT926 using Tapatalk 4
Click to expand...
Click to collapse
Theres a couple threads in the general section outlining the process. The bounty thread and the safestrap thread.
Sent from my SCH-I545 using Tapatalk 2

What happened to the ME7 root awards?

Does this mean that it is safe to update to me7 and then root per the instructions?
When I look at the software update choice on the phone it says that settings failed??
pego99 said:
Does this mean that it is safe to update to me7 and then root per the instructions?
When I look at the software update choice on the phone it says that settings failed??
Click to expand...
Click to collapse
Not only, NO! But HELL NO! If you're on MDK do not take update to ME7. You can, however, flash roms based upon ME7 - - like Hyperdrive.
Sent from my SCH-I545 using Tapatalk 4
wtherrell said:
Not only, NO! But HELL NO! If you're on MDK do not take update to ME7. You can, however, flash roms based upon ME7 - - like Hyperdrive.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
I did and the root worked. Why was this a bad idea? I want to be able to move apps to the external SD card.
pego99 said:
I did and the root worked. Why was this a bad idea? I want to be able to move apps to the external SD card.
Click to expand...
Click to collapse
Because ME7 has a locked bootloader
Luke
pego99 said:
I did and the root worked. Why was this a bad idea? I want to be able to move apps to the external SD card.
Click to expand...
Click to collapse
Now, you cannot flash a custom recovery nor custom roms. I hope you gain much by moving perhaps a gig of apps to your SD card - - you have paid a very high price to do so. Now your only option for custom roms is safestrap. I wish you the best of luck.
Sent from my SCH-I545 using Tapatalk 4
I will not be running other Roms. Just would like a nandroid backup. Is safestrap safe for this?
Sent from my SCH-I545 using Tapatalk 2
Look at the general questions area.... I think somebody talks about ss and nandroid... they said that it can backup roms, but not stock.
This sounds plausible because HashCode, the SS Dev, said that he bas to work more on SS before you can do anything with stock rom... even backup
Sent from my SCH-I545 using xda app-developers app
lukesdiesel said:
Because ME7 has a locked bootloader
Luke
Click to expand...
Click to collapse
Wrong, VZW never had an unlocked bootloader...both MDK and ME7 are locked.
Why are so many people misinformed?
Sent from my SCH-I545 using xda app-developers app
richii0207 said:
Wrong, VZW never had an unlocked bootloader...both MDK and ME7 are locked.
Why are so many people misinformed?
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Because people think as long as they can flash ROMs, it's unlocked. You and I know it's only a workaround, but most users don't.
I'd much rather have to use Loki than SS, as cool as SS sounds.
Sent from my SCH-I545 using Tapatalk 4

Question about mdk and newer kernels

I'm on MK2 right now and it seems hope of bootloader unlock may be in the form of reverting back to mdk.
Of this is the case here is my question.
If on mdk can you flash any stock kernel like mk2 or are you stuck with mdk based kernel. I ask this as mj7 had charger issues but mk2 doesn't.
Sent from my SCH-I545 using Tapatalk
tshelby73 said:
I'm on MK2 right now and it seems hope of bootloader unlock may be in the form of reverting back to mdk.
Of this is the case here is my question.
If on mdk can you flash any stock kernel like mk2 or are you stuck with mdk based kernel. I ask this as mj7 had charger issues but mk2 doesn't.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Where did you see that we could revert, or are even close to being able to?
Sent from my NCC 1701 using Tapatalk 4
Not able to revert but has been talked about. I'm just preparing in case it happens and finding out info. It may never happen.
Sent from my SCH-I545 using Tapatalk
tshelby73 said:
I'm on MK2 right now and it seems hope of bootloader unlock may be in the form of reverting back to mdk.
Of this is the case here is my question.
If on mdk can you flash any stock kernel like mk2 or are you stuck with mdk based kernel. I ask this as mj7 had charger issues but mk2 doesn't.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
If you're on an MDK s4 you'd be able to flash any kernels that are made for the phone as well as any modems.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Thanks
Sent from my SCH-I545 using Tapatalk

Reset Knox? No Way!

I had previously tripped Knox.
So I updated to NAB using this method: http://forum.xda-developers.com/showthread.php?t=2657447
Everything worked like a charm.
Knox was reset to 0x0!
Did anyone else have this experience?
toviaheli said:
I had previously tripped Knox.
So I updated to NAB using this method: http://forum.xda-developers.com/showthread.php?t=2657447
Everything worked like a charm.
Knox was reset to 0x0!
Did anyone else have this experience?
Click to expand...
Click to collapse
Are you sure you had 0x0? Did you just rooted or Custom recovery?
slow_one said:
Are you sure you had 0x0? Did you just rooted or Custom recovery?
Click to expand...
Click to collapse
Absolutely certain I had 0x0 after flashing using that method.
Prior to manually updating I had Knox 0x1
I Rooted and Custom TWRP.
I followed EVERY step in that step-by-step. With ONE exception, I mistakenly flashed the Engineering Bootloader BEFORE following that tutorial.
toviaheli said:
Absolutely certain I had 0x0 after flashing using that method.
Prior to manually updating I had Knox 0x1
I Rooted and Custom TWRP.
I followed EVERY step in that step-by-step. With ONE exception, I mistakenly flashed the Engineering Bootloader BEFORE following that tutorial.
Click to expand...
Click to collapse
but how did you trip the Knox the 1st time?
slow_one said:
but how did you trip the Knox the 1st time?
Click to expand...
Click to collapse
The first day I had the Note 3 I tipped Knox when I rooted and flashed recovery,
Well if you could list what firmware you came from? What bootloader you had previously etc etc
It may help Developers with the fight against knox
Sent from my SM-N9005 using xda app-developers app
st3chn0 said:
Well if you could list what firmware you came from? What bootloader you had previously etc etc
It may help Developers with the fight against knox
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
I was on MJ4 running the MJ4 Engineering bootloader.
toviaheli said:
I was on MJ4 running the MJ4 Engineering bootloader.
Click to expand...
Click to collapse
As far as I know there is no MJ4 engineering bootloader. The engineering bootloader is NA4 which is the first kit kat leak and the bootloader is is unlocked.
Sent from my SM-N900P using Tapatalk
toviaheli said:
I was on MJ4 running the MJ4 Engineering bootloader.
Click to expand...
Click to collapse
You mean this http://forum.xda-developers.com/showthread.php?t=2655674 ??
Walter.White said:
You mean this http://forum.xda-developers.com/showthread.php?t=2655674 ??
Click to expand...
Click to collapse
I think what freeza did is morph the NA4 engineering with the NAB bootloader thus creating a daily usable NAB bootloader.
Sent from my SM-N900P using Tapatalk
JonSCSL said:
I think what freeza did is morph the NA4 engineering with the NAB bootloader thus creating a daily usable NAB bootloader.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I'm not so certain. I believe that unlocked bootloader was obtained the old-fashioned way, by it landing in the right hands. If what you've suggested were true, then why release it as unique? The OP of that thread makes it pretty clear that it's a very nice item to have and we won't know if another is coming.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
I'm not so certain. I believe that unlocked bootloader was obtained the old-fashioned way, by it landing in the right hands. If what you've suggested were true, then why release it as unique? The OP of that thread makes it pretty clear that it's a very nice item to have and we won't know if another is coming.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I thought that the only unlocked bootloader that we had was NA4. Didn't know we had 2 unlocked bootloaders
Sent from my SM-N900P using Tapatalk
toviaheli said:
I was on MJ4 running the MJ4 Engineering bootloader.
Click to expand...
Click to collapse
I just believe it's the fact you have an engineering bootloader..... The bootloader you are now on is that is the engineering one or stock?
Sent from my SM-N9005 using xda app-developers app
st3chn0 said:
I just believe it's the fact you have an engineering bootloader..... The bootloader you are now on is that is the engineering one or stock?
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Yes. Right now I am on the Engineering Bootloader for NAB
I was previously on MJ4 Stock Rooted.
I Flashed the NAB Engineering Bootloader
Then I flashed this: http://forum.xda-developers.com/showthread.php?t=2657447
toviaheli said:
Yes. Right now I am on the Engineering Bootloader for NAB
I was previously on MJ4 Stock Rooted.
I Flashed the NAB Engineering Bootloader
Then I flashed this: http://forum.xda-developers.com/showthread.php?t=2657447
Click to expand...
Click to collapse
can you post a screen shot? of the 0x0
kaos420 said:
can you post a screen shot? of the 0x0
Click to expand...
Click to collapse
Make a video
Sent from my SM-N900 using Tapatalk
Okay, so let me see if I have the steps correct on this.
1. You flashed a custom recovery and rooted your device, thereby tripping Knox. Did you use CFAutoroot or Kingo? The recovery would have tripped knox anyways, but just checking for root method.
2. You started with MJ4 or did you upgrade to MJ4 and if you upgraded, was Knox tripped before? (I started with MI3, some had MI5). This is mainly to find out if you tripped Knox before or after MJ4.
3. While on MJ4, you flashed the NAB engineering bootloader.
4. You ran the one-click to update to 4.4.2
If you can clear up points 1 and 2, you could probably turn this into a guide to help others.
evilvoice said:
Okay, so let me see if I have the steps correct on this.
1. You flashed a custom recovery and rooted your device, thereby tripping Knox. Did you use CFAutoroot or Kingo? The recovery would have tripped knox anyways, but just checking for root method.
2. You started with MJ4 or did you upgrade to MJ4 and if you upgraded, was Knox tripped before? (I started with MI3, some had MI5). This is mainly to find out if you tripped Knox before or after MJ4.
3. While on MJ4, you flashed the NAB engineering bootloader.
4. You ran the one-click to update to 4.4.2
If you can clear up points 1 and 2, you could probably turn this into a guide to help others.
Click to expand...
Click to collapse
any updates on this.. ??
procedure..methods..etc/..confirmation
xinfinityoO said:
any updates on this.. ??
procedure..methods..etc/..confirmation
Click to expand...
Click to collapse
I call BS all the way.
Sent from my SM-N900P using XDA Premium 4 mobile app
I think we all got trolled? :/

Updating Android with root/ss

Hi all, I got a couple questions. I'm currently still on 4.3, running a safe-strapped Rom (Galaxy s4, VZW). I'd like to upgrade to KK.
Is the latest firmware available OTA still NC5?
What method will I need to upgrade, OTA or flash stock? Since I'm rooted, is an OTA even an option? I do have SuperSU pro's survival mode (I heard that worked for a couple people). I'm guessing otherwise I'd have to Towel root.
Finally, I assume I should delete the custom ROM slot and factory wipe my stock slot before updating. Will doing a reset affect safe strap, or will it leave it alone?
Thanks!
Sent from my SCH-I545 using Tapatalk
marbertshere said:
Hi all, I got a couple questions. I'm currently still on 4.3, running a safe-strapped Rom (Galaxy s4, VZW). I'd like to upgrade to KK.
Is the latest firmware available OTA still NC5?
What method will I need to upgrade, OTA or flash stock? Since I'm rooted, is an OTA even an option? I do have SuperSU pro's survival mode (I heard that worked for a couple people). I'm guessing otherwise I'd have to Towel root.
Finally, I assume I should delete the custom ROM slot and factory wipe my stock slot before updating. Will doing a reset affect safe strap, or will it leave it alone?
Thanks!
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2606501
decaturbob said:
http://forum.xda-developers.com/showthread.php?t=2606501
Click to expand...
Click to collapse
Thank you for the link, and everything else you've done around here, Bob. I read around a little but I couldn't figure this out: do I have to use Surge's method to upgrade or can I take an alternative route (in guessing Odin) , now that towel root exists?
I'm hesitant only bc I tried to use his downgrade /upgrade methods on a different phone and had some problems. Thanks.
Sent from my SCH-I545 using Tapatalk
Nvm, I'm going to try to giglie's method. Guess I'm going to wipe my 2nd Rom slot and factory reset my stock slot. Hope I'm on the right track?
Sent from my SCH-I545 using Tapatalk
marbertshere said:
Nvm, I'm going to try to giglie's method. Guess I'm going to wipe my 2nd Rom slot and factory reset my stock slot. Hope I'm on the right track?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
You can't use ROM slots with 3.72 safestrap. ROM must be installed to stock slot. Take and research this info.
sent by slimkat
I went back to stock using Odin. took update, rooted with towelroot installed Safestrap 3.72 . Then installed custom KK rom. All worked without any issues
Here is a link with videos
http://forum.xda-developers.com/showthread.php?t=2337590
Sent from my SCH-I545 using Xparent Green Tapatalk 2
spjetrovic said:
I went back to stock using Odin. took update, rooted with towelroot installed Safestrap 3.72 . Then installed custom KK rom. All worked without any issues
Here is a link with videos
http://forum.xda-developers.com/showthread.php?t=2337590
Sent from my SCH-I545 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
Thanks for the info. I was just curious, could I do a full unroot/reset (I rooted with saferoot) instead of flashing stock with odin? I mean, same end result, right
Sent from my SCH-I545 using Tapatalk
decaturbob said:
You can't use ROM slots with 3.72 safestrap. ROM must be installed to stock slot. Take and research this info.
sent by slimkat
Click to expand...
Click to collapse
Thanks for the link again. I meant I would wipe my current custom ROM slot before I flash to stock or update anything.
Sent from my SCH-I545 using Tapatalk
marbertshere said:
Thanks for the info. I was just curious, could I do a full unroot/reset (I rooted with saferoot) instead of flashing stock with odin? I mean, same end result, right
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I would recommend Odin full wipe tar. This gets your phone 100% stock. It's safe, simple and proven to work.
Watch the videos they help a lot.
I haven't done it the other way!
Don't want to miss lead you.
Sent from my SCH-I545 using Xparent Green Tapatalk 2
spjetrovic said:
I would recommend Odin full wipe tar. This gets your phone 100% stock. It's safe, simple and proven to work.
Watch the videos they help a lot.
I haven't done it the other way!
Don't want to miss lead you.
Sent from my SCH-I545 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
No, thank you! Videos are incredibly helpful. I was just curious.
Sent from my SCH-I545 using Tapatalk

Categories

Resources