Related
I've read countless forums on the rooting and roms and kernels and I have the most basic grasp of what each do. It seems that every time I read an article or forum post at some point something is mentioned that is over my head or that I don't fully grasp. I would love to not brick my phone. I need someone to explain my options and what I can do like I'm 5. What is Odex or Deodex? HOW do I find roms and kernels that work for my phone. What is clockworkmod and ADB? And what can I do to make sure I don't completely brick my phone.
I currently have an AT&T S4 that I rooted with Casual. Through casual it also loaded TWRP. I made a backup of everything it would let me check. I need to get a kernel onto this phone that will allow me to run Call Recorder "http://forum.xda-developers.com/showthread.php?t=1441643"
I am required to have a call recording feature on my cell phone or I'm tied to a landline for work. I had a Galaxy S2 Skyrocket that this program worked perfectly on.
I would like to for the most part keep the phone looking stock. Although I'm not sure what features I could add by going with a different rom.
I'm sorry for the noob questions.
There is a 1% chance of your device bricking if you follow all the correct root steps. Clockworkmod is like twrp. It is a custom recovery to let you put custom Roms on. ADB is the android device bridge. It let's you control your android from Ubuntu command prompt. Hope this helped
Sent from my SCH-I545 using xda app-developers app
No offense meant, I honestly can't suggest you Root or ROM your phone if you can't follow the root procedure without getting confused. If you don't understand the basics how are you going to take care of issues that will inevitably come up? Desperately asking for help when your phone is looping isn't a good answer.
ADB
Odex and Deodex
ATT galaxy s4 forums, kernels are under Original Development
TWRP and CWM are just different types of recoveries. I don't like CWM because the wipe options aren't all in one menu which is bothersome. But both work well. I suggest TWRP to all my friends to limit the amount of "my phone won't boot" phone calls I get.
And the only way to ensure you don't mess up your phone is by not messing with it at all.
Mebct76 said:
I've read countless forums on the rooting and roms and kernels and I have the most basic grasp of what each do. It seems that every time I read an article or forum post at some point something is mentioned that is over my head or that I don't fully grasp. I would love to not brick my phone. I need someone to explain my options and what I can do like I'm 5. What is Odex or Deodex? HOW do I find roms and kernels that work for my phone. What is clockworkmod and ADB? And what can I do to make sure I don't completely brick my phone.
I currently have an AT&T S4 that I rooted with Casual. Through casual it also loaded TWRP. I made a backup of everything it would let me check. I need to get a kernel onto this phone that will allow me to run Call Recorder "http://forum.xda-developers.com/showthread.php?t=1441643"
I am required to have a call recording feature on my cell phone or I'm tied to a landline for work. I had a Galaxy S2 Skyrocket that this program worked perfectly on.
I would like to for the most part keep the phone looking stock. Although I'm not sure what features I could add by going with a different rom.
I'm sorry for the noob questions.
Click to expand...
Click to collapse
Every last one of those questions can and would be answered through very few Google searches. Hell, searching this site will return a lot of the same results. There's even an XDA Wiki for such FAQ. And why are you posting in Verizon if you have AT&T and there's and AT&T section for the S4? Just sayin'
Wrong forum
I would also like to suggest you make sure to post in the correct forum for your device to ensure any answers you get are applicable to what you're using. The OP indicates you have an AT&T S4, yet you posted in the Verizon forum. Should you ever have an issue with your device and need further assistance, getting responses specific to the Verizon device versus your actual device could cause further problems for you.
EDIT: Didn't see Delakit's response before posting mine
Delakit said:
Every last one of those questions can and would be answered through very few Google searches. Hell, searching this site will return a lot of the same results. There's even an XDA Wiki for such FAQ. And why are you posting in Verizon if you have AT&T and there's and AT&T section for the S4? Just sayin'
Click to expand...
Click to collapse
Yeah I just noticed it was in the Verizon section. My bad. It appears I wasn't paying close enough attention when I posted that.
Dubbsy said:
No offense meant, I honestly can't suggest you Root or ROM your phone if you can't follow the root procedure without getting confused. If you don't understand the basics how are you going to take care of issues that will inevitably come up? Desperately asking for help when your phone is looping isn't a good answer.
ADB
Odex and Deodex
ATT galaxy s4 forums, kernels are under Original Development
TWRP and CWM are just different types of recoveries. I don't like CWM because the wipe options aren't all in one menu which is bothersome. But both work well. I suggest TWRP to all my friends to limit the amount of "my phone won't boot" phone calls I get.
And the only way to ensure you don't mess up your phone is by not messing with it at all.
Click to expand...
Click to collapse
I can follow the root procedure just fine and have rooted my phone. How can I learn if I just sit back and say "well guess I can't do it". Your right there are going to be the inevitable issues. The only way to ensure that I never learn this stuff is to not mess with it. I'm fully aware of the risks and potential rewards of this. But I'd like to figure it out. It is probably difficult for the senior guys such as yourself to remember what it was like first starting out. You've got multiple devices with multiple influences on the current setup of the phone at stock and because of the multiple hands in the making of each phone you have different rules and procedures for each one. The sprint S4 is different from the AT&T s4 which is different from the T-mobile S4. So following a guide doesn't always help if you don't completely understand the terminology. Can I use a mod kernel on a stock rom? From what i've read, yes but if it is AT&T it must be loki'd, ok What does loki do, why does it need to be loki'd, can I loki any S4 designed kernel, and HOW do i Loki something. I have yet to find something that answers all of those. Would you like to try? Maybe someone has answered them and I just can't find it.
Also, it appears I posted this in the Verizon forum instead of the AT&T forum. It was late and I wasn't paying that close of attention. My apologies.
Icculus760 said:
I would also like to suggest you make sure to post in the correct forum for your device to ensure any answers you get are applicable to what you're using. The OP indicates you have an AT&T S4, yet you posted in the Verizon forum. Should you ever have an issue with your device and need further assistance, getting responses specific to the Verizon device versus your actual device could cause further problems for you.
EDIT: Didn't see Delakit's response before posting mine
Click to expand...
Click to collapse
Thanks...I wasn't paying close enough attention when I posted that.
Mebct76 said:
I can follow the root procedure just fine and have rooted my phone. How can I learn if I just sit back and say "well guess I can't do it". Your right there are going to be the inevitable issues. The only way to ensure that I never learn this stuff is to not mess with it. I'm fully aware of the risks and potential rewards of this. But I'd like to figure it out. It is probably difficult for the senior guys such as yourself to remember what it was like first starting out. You've got multiple devices with multiple influences on the current setup of the phone at stock and because of the multiple hands in the making of each phone you have different rules and procedures for each one. The sprint S4 is different from the AT&T s4 which is different from the T-mobile S4. So following a guide doesn't always help if you don't completely understand the terminology. Can I use a mod kernel on a stock rom? From what i've read, yes but if it is AT&T it must be loki'd, ok What does loki do, why does it need to be loki'd, can I loki any S4 designed kernel, and HOW do i Loki something. I have yet to find something that answers all of those. Would you like to try? Maybe someone has answered them and I just can't find it.
Also, it appears I posted this in the Verizon forum instead of the AT&T forum. It was late and I wasn't paying that close of attention. My apologies.
Click to expand...
Click to collapse
Holy crap, hyper questions. Let me try to tackle them.
I remember what is was like. As weird as it sounds, I've never been hesitant about breaking my phone even when it was my only device. But everyone is different. I have learned the most when I've made my device unusable for a few days. Everyone learns and functions differently though. In Psychology they call it the Theory of Multiple Intelligences. Some people are brilliant but can't visualize anything. Some are brilliant and can't take tests. I could go on and rant about our school's piss poor management of teaching children correctly according to their "intelligences" but I'll just stop there.
GSM is different than the CDMA versions because the radios are looking for entirely different signals. Srint, USC, Metro, and Verizon all being CDMA. Radios are the biggest pain when trying to port IMO.
Loki is an exploit to work around the locked bootloaders of ATT and VZW. There is a thread somewhere on exactly how it works. But there are also loki patches posted and the better recoveries all automatically loki patch boot.img's for you.
Almost every gs4 version has their own versions of each kernel built off of the aboot and boot images of the stock files. For instance ktoonsez has a kernel available for all the carriers and one for touchwiz and one for aosp. If you are running stock you would simply flash his kernel for TW and it would install just fine on the stock ROM without you knowing anything about loki or how it works.
To be honest, I don't know enough about the actual vulnerabilities and exploits to FULLY understand loki. But I don't need to. It works. I plan to learn more about root vulnerabilities later. But I can only work on so much at once.
You can flash other carrier's kernels, but I wouldn't recommend it if there are kernels that suit your need for your carrier. I say this because I did loki the 4.3 kernel designed for the 9505 and got it working on my vzw gs4. BUT things may be broken or not fully working due to the differences in the kernels themselves. If you don't want to tear into things, it's best to just run the one for your phone.
I think I got it all. Maybe not though.
The best way to learn is with a nexus device. You can't brick that thing if you tried, and even if you were trying, you'd have to know what you were doing to brick it.
I mean, as long as you have the money to replace your phone, and don't mind not having an operational phone, dive right in. I've gone a weekend without a phone, stayed up til 2am trying to fix my phone when I had to be at work at 6:30, but I like to tinker with stuff and I'm fine with that.
Sent from my SCH-I545 using Tapatalk 4 Beta
Yeah I've bricked my gnex before and I learned a lot from it. There is almost always a way to fix a bricked phone whether its Odin or somehow flashing a new ROM. And like what was said before there is only a 1% chance you'll actually brick your phone. A lot of people think they are bricked when it is only a soft brick instead.
Sent from my Galaxy Nexus using xda app-developers app
I have an S4 on MDK. All this talk of the 4.3 update makes me want it. I want to update and am happy with the stock ROM after tweaking it with Apex and Xposed. I however don't want to lose the ability to install a custom ROM every once in a while. Is the bootstrap method good enough?
jeromeh said:
I have an S4 on MDK. All this talk of the 4.3 update makes me want it. I want to update and am happy with the stock ROM after tweaking it with Apex and Xposed. I however don't want to lose the ability to install a custom ROM every once in a while. Is the bootstrap method good enough?
Click to expand...
Click to collapse
Based on your concerns, I would stay on MDK and await word once this thing is out in the wild a bit if root is even possible let alone custom roms.
lazer9 said:
Based on your concerns, I would stay on MDK and await word once this thing is out in the wild a bit if root is even possible let alone custom roms.
Click to expand...
Click to collapse
Ok. I dislike the idea of losing all my current ability to change ROMs maybe I will just have to swim through more custom roms and find one I like. Notifications seem to look better on the Stock Touchwiz vs AOSP
There has to be 100 threads on here NEVER TAKE A OTA. If you were bone stock and had no idea what root even means then by all means go for it and update. But most users here on XDA want more out of their devices. A lot of users learned the hard way when they rushed from MDK to ME7. What a headache. Then it seems everyone rushed to MI1. I really do not understand why people don't just wait a couple of days and wait for the devs to give a bonestock rooted safe build to flash.
With that said, I bet once 4.3 drops it will get crazy in here!
Travisdroidx2 said:
There has to be 100 threads on here NEVER TAKE A OTA. If you were bone stock and had no idea what root even means then by all means go for it and update. But most users here on XDA want more out of their devices. A lot of users learned the hard way when they rushed from MDK to ME7. What a headache. Then it seems everyone rushed to MI1. I really do not understand why people don't just wait a couple of days and wait for the devs to give a bonestock rooted safe build to flash.
With that said, I bet once 4.3 drops it will get crazy in here!
Click to expand...
Click to collapse
I was more asking if I would be shooting myself in the foot by moving to a safestrap restricted device. It seems like most development is that way anyway. Not trying to be a pain or anything. I sure do miss a Nexus device.
jeromeh said:
I was more asking if I would be shooting myself in the foot by moving to a safestrap restricted device. It seems like most development is that way anyway. Not trying to be a pain or anything. I sure do miss a Nexus device.
Click to expand...
Click to collapse
stay away from the OTA for now
Hey All -
I've been digging, and I tend to be a lurker, but I'm not finding a safe place to put this.
In short, I am still running a rooted MDK. I have TWRP.
It used to be a huge deal for me to run a custom ROM et all because I needed to get the most out of my phone, but now that I have a great plan and an awesome phone, I found my need to flash not that big of a deal, so I'm toying with the idea of upgrading. I came here and started digging around. I found no real answer.
What I am looking for from the more seasoned and skilled members is, what would you do if you had MDK, unlimited Data/Wifi Hotspot? Would you just flash a 4.3 ROM and the new MJ7 Modem? Or would you just flash a stock ROM with the stock Recovery and take the OTA?
I'd like to keep Root, but (as I said) it's not necessary to have it at this moment, but if waiting long enough means I can basically get a stock MJ7 without the KNOX and pre-rooted, I'd be down.
Give me your thoughts.
mastridonicus said:
Hey All -
I've been digging, and I tend to be a lurker, but I'm not finding a safe place to put this.
In short, I am still running a rooted MDK. I have TWRP.
It used to be a huge deal for me to run a custom ROM et all because I needed to get the most out of my phone, but now that I have a great plan and an awesome phone, I found my need to flash not that big of a deal, so I'm toying with the idea of upgrading. I came here and started digging around. I found no real answer.
What I am looking for from the more seasoned and skilled members is, what would you do if you had MDK, unlimited Data/Wifi Hotspot? Would you just flash a 4.3 ROM and the new MJ7 Modem? Or would you just flash a stock ROM with the stock Recovery and take the OTA?
I'd like to keep Root, but (as I said) it's not necessary to have it at this moment, but if waiting long enough means I can basically get a stock MJ7 without the KNOX and pre-rooted, I'd be down.
Give me your thoughts.
Click to expand...
Click to collapse
I struggled when I had to type the response to this. Not because I didn't know the answer, but because I didn't know how to ask you why you didn't already know the answer? You're giving up what you already were taking for granted just for the sake of what? Not trying to be mean, just trying to understand.
Surge1223 said:
I struggled when I had to type the response to this. Not because I didn't know the answer, but because I didn't know how to ask you why you didn't already know the answer? You're giving up what you already were taking for granted just for the sake of what? Not trying to be mean, just trying to understand.
Click to expand...
Click to collapse
No worries man, I didn't take offense to your question at all . It's all good.
Well, it's not a matter of taking something for granted -- if that were the case, I'd just do it and through forethought to the wind. What I'm looking for is what experienced eyes may see which could offer me a path I didn't think of.
I like the open-ended ability a completely accessible (s-OFF, Custom Recovery, rooted, etc) allows for me to do. I like having the options, but I don't need them right now. This questions is, in essence, a "Just because I have the money, doesn't mean I need to save it."
I've seen people suggest waiting, flashing just the modem, upgrading for all the performance increases, upgrading just for the new release and all that, but no one tying it all together for the most open-ended "I have an MDK and want to get on 4.3" solution.
I know I can flash to ME1 then OTA it to get to Stock 4.3 with root but wind up with KNOX. Is there a better way? Is there a way I'm not thinking of?
Thanks for reading!
You'll potentially lose the freedom to run custom roms forever... there's no guarantee that the bootloaders on ME7 and later will be unlocked so there's a chance you'll be stuck when Verizon stops updating the S4. You can run a stock rom on MDK all you want so I'm not sure what would be your motivation to jump the gun here... I'm sure an MJ7 based rom to flash will show up in no time...
I'd you do want to update I'm sure there are some devs that would be glad to trade you phones.
Sent from my SCH-I545 using xda app-developers app
Crawshayi said:
You'll potentially lose the freedom to run custom roms forever... there's no guarantee that the bootloaders on ME7 and later will be unlocked so there's a chance you'll be stuck when Verizon stops updating the S4. You can run a stock rom on MDK all you want so I'm not sure what would be your motivation to jump the gun here... I'm sure an MJ7 based rom to flash will show up in no time...
Click to expand...
Click to collapse
Thanks -- I'm not motivated to jump the gun, just answering a question while I have time to. Ironically, I did get the B.S. line from support that my problem was due to not having the latest OTA.
When you say:
I'm sure an MJ7 based rom to flash will show up in no time.
Click to expand...
Click to collapse
, you're essentially stating that we'll have an MJ7 ROM that may carry some combination of Rooted, De-KNOX'd so that we can use 4.3 and still have our custom recovery? This would be what I'm looking for.
Sorry to be dense.
I'll probably just flash the modem then.
Just relax there should be a mj7 rom to flash before long.
Sent from my SCH-I545 using xda app-developers app
mastridonicus said:
Thanks -- I'm not motivated to jump the gun, just answering a question while I have time to. Ironically, I did get the B.S. line from support that my problem was due to not having the latest OTA.
When you say: , you're essentially stating that we'll have an MJ7 ROM that may carry some combination of Rooted, De-KNOX'd so that we can use 4.3 and still have our custom recovery? This would be what I'm looking for.
Sorry to be dense.
I'll probably just flash the modem then.
Click to expand...
Click to collapse
Yep exactly... there are already roms based on ME7 and MI1 that are close to stock with minor modifications, so of course there will be some of the same with MJ7 eventually. Just have patience and be glad you have the choices you do... some of us (like me) are stuck with a locked bootloader and we can only dream.
mastridonicus said:
No worries man, I didn't take offense to your question at all . It's all good.
Well, it's not a matter of taking something for granted -- if that were the case, I'd just do it and through forethought to the wind. What I'm looking for is what experienced eyes may see which could offer me a path I didn't think of.
I like the open-ended ability a completely accessible (s-OFF, Custom Recovery, rooted, etc) allows for me to do. I like having the options, but I don't need them right now. This questions is, in essence, a "Just because I have the money, doesn't mean I need to save it."
I've seen people suggest waiting, flashing just the modem, upgrading for all the performance increases, upgrading just for the new release and all that, but no one tying it all together for the most open-ended "I have an MDK and want to get on 4.3" solution.
I know I can flash to ME1 then OTA it to get to Stock 4.3 with root but wind up with KNOX. Is there a better way? Is there a way I'm not thinking of?
Thanks for reading!
Click to expand...
Click to collapse
The point that your missing is there is no back, I changed my mind, or let me try something else. Samsung is trying to get the corporate enterprise business, which means ultra secure bootloaders and blacklisted updates that cause changes in qfuses which a physical change can not be un done by any software. So the unlocked phone will become increasing rare and harder to maintain. So a more apt example is time. You can spend it, but you can never get it back. The only route is to wait or give up cannot be gotten back.
Sent from my BNTV250A using xda app-developers app
mastridonicus said:
No worries man, I didn't take offense to your question at all . It's all good.
Well, it's not a matter of taking something for granted -- if that were the case, I'd just do it and through forethought to the wind. What I'm looking for is what experienced eyes may see which could offer me a path I didn't think of.
I like the open-ended ability a completely accessible (s-OFF, Custom Recovery, rooted, etc) allows for me to do. I like having the options, but I don't need them right now. This questions is, in essence, a "Just because I have the money, doesn't mean I need to save it."
I've seen people suggest waiting, flashing just the modem, upgrading for all the performance increases, upgrading just for the new release and all that, but no one tying it all together for the most open-ended "I have an MDK and want to get on 4.3" solution.
I know I can flash to ME1 then OTA it to get to Stock 4.3 with root but wind up with KNOX. Is there a better way? Is there a way I'm not thinking of?
Thanks for reading!
Click to expand...
Click to collapse
I have to say that I was not expecting such a well thought out answer, but you have to realize that we've seen people upgrade from MDK just because they don't like how the "custom" splash screen appears and they wanted to get rid of it, or to get the newest S Voice or something. Interestingly enough, while you see it as "Just because I have the money, doesn't mean I need to save it."
I see it as "Just because it earns them more money, doesn't justify the existence and enforcement of having to use/see or be in the presence of the abomination that is Vz Navigator." But in all seriousness, my view is probably closer to this.
O gawd.... the hacker's manifesto lol.. you're making me feel old.
Sent from my Nexus 7 using Tapatalk 4
Crawshayi said:
You'll potentially lose the freedom to run custom roms forever...
Click to expand...
Click to collapse
Don't you think that, as KNOX implementation (and greater) grows, that there will be less custom ROMS for the device? My search shows many have past the point of no return with the first OTA.[/QUOTE]
Surge1223 said:
I have to say that I was not expecting such a well thought out answer, but you have to realize that we've seen people upgrade from MDK just because they don't like how the "custom" splash screen appears and they wanted to get rid of it, or to get the newest S Voice or something. Interestingly enough, while you see it as "Just because I have the money, doesn't mean I need to save it."
I see it as "Just because it earns them more money, doesn't justify the existence and enforcement of having to use/see or be in the presence of the abomination that is Vz Navigator." But in all seriousness, my view is probably closer to this.
Click to expand...
Click to collapse
I screwed up, I meant to say "Even though I have the money, I don't have to spend it." Sorry about that . I see your point though and while I'm more naturally your way, I did chuckle at the Hacker's Manifesto. While I still agree with the manifesto, it can't be all encompassing anymore. Technology is in our every day lives, and you'd have to approach your life like a monk with supreme dedication and limitation to maintain that view in it's entirety. It's better to maintain that focus in the areas that are most relevant to you in technology and maintaining the guidelines of simplicity there.
Surge1223 said:
I have to say that I was not expecting such a well thought out answer, but you have to realize that we've seen people upgrade from MDK just because they don't like how the "custom" splash screen appears and they wanted to get rid of it, or to get the newest S Voice or something. Interestingly enough, while you see it as "Just because I have the money, doesn't mean I need to save it."
I see it as "Just because it earns them more money, doesn't justify the existence and enforcement of having to use/see or be in the presence of the abomination that is Vz Navigator." But in all seriousness, my view is probably closer to this.
Click to expand...
Click to collapse
Omg a hacker's manifesto reference lol flashback.
Sent from my SCH-I545 using XDA Premium 4 mobile app
I rooted my Verizon S4, froze all of the bloatware with ROM Toolbox Pro, and now it's fast as hell. The battery lasts 2 days with moderate use, FoxFi hotspot works, and I don't get any security warnings (froze your ass KNOX). I've installed SafeStrap 3.71, and I've tried installing HypderDrive, but it hasn't been able to stick. The bootloader is totally locked down, so Hashcode's SafeStrap seems to be the only thing keeping any hope alive for something that will work.
I guess the real frustrating thing is that there is no real unity between developers here, and that no one can decide on a route to go with. This leaves a lot of us who just got the S4 with fewer, or no ROM options. Is it time we accepted that a bootloader solution might not be the way to go, and attack it using something like SafeStrap? I've been using SafeStrap on my Droid 4 for a long time, and it is the best alternative, and in many ways, superior to unlocking a bootloader. Sure you get issues regarding space for more than one ROM install, but having your stock ROM intact is an excellent fail safe. There are some other constrictions, but the manpower potential could really bring results to a dual-boot system like SafeStrap.
My deal here is, let's get behind HashCode on this, and maybe he can share his work with the rest of the developer community, and we can all contribute some funds to make something like SafeStrap work, which it most definitely can. Imagine if we could get Cyanogenmod developers working on SafeStrap with HashCode to come up with ROMs that would actually work like they do with an unlocked bootloader. There is a somewhat steep learning curve with SafeStrap, but with resources comes better documentation. People are too quick to jump on a 1-click rooting method, and leave the rest of us behind. If SafeStrap got enough attention, maybe it could someday be a one-click solution that no one at Samsung, Motorola, or HTC could ever lock down.
Let me know what you think.
RueTheDayTrebek said:
I've been using SafeStrap on my Droid 4 for a long time, and it is the best alternative, and in many ways, superior to unlocking a bootloader. Sure you get issues regarding space for more than one ROM install, but having your stock ROM intact is an excellent fail safe. There are some other constrictions, but the manpower potential could really bring results to a dual-boot system like SafeStrap.
Click to expand...
Click to collapse
I Love Hashcode and that he designed SafeStrap as i have used it on my Droid Bionic prior to getting the S4 (im still on MDK). But I would never say it's superior to unlocking a bootloader in any sense. I can say maybe convenient for quicker swapping of roms but I can't see SS being better then an unlocked Bootloader.
But the rest of you post im totally on board with. Id rather an unlocked Bootloader and be able to get OTA's with the correct kernels then a port where some things won't work since were still on the original or a previous kernel.
RueTheDayTrebek said:
I rooted my Verizon S4, froze all of the bloatware with ROM Toolbox Pro, and now it's fast as hell. The battery lasts 2 days with moderate use, FoxFi hotspot works, and I don't get any security warnings (froze your ass KNOX). I've installed SafeStrap 3.71, and I've tried installing HypderDrive, but it hasn't been able to stick. The bootloader is totally locked down, so Hashcode's SafeStrap seems to be the only thing keeping any hope alive for something that will work.
I guess the real frustrating thing is that there is no real unity between developers here, and that no one can decide on a route to go with. This leaves a lot of us who just got the S4 with fewer, or no ROM options. Is it time we accepted that a bootloader solution might not be the way to go, and attack it using something like SafeStrap? I've been using SafeStrap on my Droid 4 for a long time, and it is the best alternative, and in many ways, superior to unlocking a bootloader. Sure you get issues regarding space for more than one ROM install, but having your stock ROM intact is an excellent fail safe. There are some other constrictions, but the manpower potential could really bring results to a dual-boot system like SafeStrap.
My deal here is, let's get behind HashCode on this, and maybe he can share his work with the rest of the developer community, and we can all contribute some funds to make something like SafeStrap work, which it most definitely can. Imagine if we could get Cyanogenmod developers working on SafeStrap with HashCode to come up with ROMs that would actually work like they do with an unlocked bootloader. There is a somewhat steep learning curve with SafeStrap, but with resources comes better documentation. People are too quick to jump on a 1-click rooting method, and leave the rest of us behind. If SafeStrap got enough attention, maybe it could someday be a one-click solution that no one at Samsung, Motorola, or HTC could ever lock down.
Let me know what you think.
Click to expand...
Click to collapse
HD 12 is about as flawless as one would expect for a custom rom. Im happy with it and honestly if there were more options, I doubt I would move away from it. Thats just my opinion though. What do you mean it didnt stick?
Sent from my SCH-I545 using XDA Premium HD app
The development community on the S4 took a pretty big hit with the whole boot loader thing. Hopefully hash can figure out Kexec and hopefully we can get more dev support...
But until then safestrap IS here, it does have roms and it works great. Not sure exactly what your looking for?
Can you detail what your doing to advance the community, and how you want us to help you?
scryan said:
The development community on the S4 took a pretty big hit with the whole boot loader thing. Hopefully hash can figure out Kexec and hopefully we can get more dev support...
But until then safestrap IS here, it does have roms and it works great. Not sure exactly what your looking for?
Can you detail what your doing to advance the community, and how you want us to help you?
Click to expand...
Click to collapse
What are you talking about? Did you get my post mixed up with the op's?
Sent from my SCH-I545 using Tapatalk
Bradh024 said:
What are you talking about? Did you get my post mixed up with the op's?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yup. lol sorry just hit the "Reply" button with out noticing its the same as most forums Quote button.... Just meant to reply.
scryan said:
Yup. lol sorry just hit the "Reply" button with out noticing its the same as most forums Quote button.... Just meant to reply.
Click to expand...
Click to collapse
Ahh I gotcha. Had me confused for a minute there. lol
Sent from my SCH-I545 using Tapatalk
RueTheDayTrebek said:
I rooted my Verizon S4, froze all of the bloatware with ROM Toolbox Pro, and now it's fast as hell. The battery lasts 2 days with moderate use, FoxFi hotspot works, and I don't get any security warnings (froze your ass KNOX). I've installed SafeStrap 3.71, and I've tried installing HypderDrive, but it hasn't been able to stick. The bootloader is totally locked down, so Hashcode's SafeStrap seems to be the only thing keeping any hope alive for something that will work.
I guess the real frustrating thing is that there is no real unity between developers here, and that no one can decide on a route to go with. This leaves a lot of us who just got the S4 with fewer, or no ROM options. Is it time we accepted that a bootloader solution might not be the way to go, and attack it using something like SafeStrap? I've been using SafeStrap on my Droid 4 for a long time, and it is the best alternative, and in many ways, superior to unlocking a bootloader. Sure you get issues regarding space for more than one ROM install, but having your stock ROM intact is an excellent fail safe. There are some other constrictions, but the manpower potential could really bring results to a dual-boot system like SafeStrap.
My deal here is, let's get behind HashCode on this, and maybe he can share his work with the rest of the developer community, and we can all contribute some funds to make something like SafeStrap work, which it most definitely can. Imagine if we could get Cyanogenmod developers working on SafeStrap with HashCode to come up with ROMs that would actually work like they do with an unlocked bootloader. There is a somewhat steep learning curve with SafeStrap, but with resources comes better documentation. People are too quick to jump on a 1-click rooting method, and leave the rest of us behind. If SafeStrap got enough attention, maybe it could someday be a one-click solution that no one at Samsung, Motorola, or HTC could ever lock down.
Let me know what you think.
Click to expand...
Click to collapse
what makes you think there is no unity or communication between devs on this issue? The fact of the matter is, the security lockdown is pretty steep and in the end, no work around can be possible.
decaturbob said:
what makes you think there is no unity or communication between devs on this issue? The fact of the matter is, the security lockdown is pretty steep and in the end, no work around can be possible.
Click to expand...
Click to collapse
That's my point about the bootloader, that in time, every carrier is going to put their phones on lockdown. It just makes sense to move to a newer concept than trying to unlock the bootloader. Is hijacking the boot order, what SafeStrap does, the right way to go? What about overwriting the kernel and bypassing the bootloader altogether? I remember Hashcode was working with kexec, and for those of you who were there a couple of years ago when SafeStrap was first there for the Motorla RZR, D4, and Bionic, might remember this. It executes a live kernel overwrite, before the bootloader can even come up to verify the signed stock rom/firmware/bootloader.
I've read a couple of people mentioning this, but I'm not sure if its feasible. My point, SafeStrap and KEXEC are two options that need some blockbuster support. Hashcode is the Zeus of Mt. SafeStrape, but where is the God of War and the rest of the bunch to kick ass? Can we pick a direction?
Maybe I'm going about this the wrong way, maybe my message isn't the one that needs to be heard? I haven't posted much over the last couple of years, but I've done a lot of reading over the last few weeks, and I'm just curious if there is a Bat Signal they can use to summon the Justice League and put their collective boots up the ass of Lex Luthor (Verizon and co.)?
RueTheDayTrebek said:
That's my point about the bootloader, that in time, every carrier is going to put their phones on lockdown. It just makes sense to move to a newer concept than trying to unlock the bootloader. Is hijacking the boot order, what SafeStrap does, the right way to go? What about overwriting the kernel and bypassing the bootloader altogether? I remember Hashcode was working with kexec, and for those of you who were there a couple of years ago when SafeStrap was first there for the Motorla RZR, D4, and Bionic, might remember this. It executes a live kernel overwrite, before the bootloader can even come up to verify the signed stock rom/firmware/bootloader.
I've read a couple of people mentioning this, but I'm not sure if its feasible. My point, SafeStrap and KEXEC are two options that need some blockbuster support. Hashcode is the Zeus of Mt. SafeStrape, but where is the God of War and the rest of the bunch to kick ass? Can we pick a direction?
Maybe I'm going about this the wrong way, maybe my message isn't the one that needs to be heard? I haven't posted much over the last couple of years, but I've done a lot of reading over the last few weeks, and I'm just curious if there is a Bat Signal they can use to summon the Justice League and put their collective boots up the ass of Lex Luthor (Verizon and co.)?
Click to expand...
Click to collapse
Put it this way:
I'm with you 100%... WHAT DO YOU WANT ME TO DO?
Because right now, your basically saying "DEVELOP MORE STUFF FOR ME SO I DON'T HAVE TO, LOLZ".
You just saying we should do things better is not a plan, what are you actually doing here to move this thing forwards?
BTW:
forum.xda-developers.com/showthread.php?t=2578566
http://forum.xda-developers.com/showthread.php?t=2500826
Its not just like "BOOM! Here is Kexec!"
Its not like the people you are suggesting should put together a software package for you phone for free are not working on it... Its just hard.
RueTheDayTrebek said:
That's my point about the bootloader, that in time, every carrier is going to put their phones on lockdown. It just makes sense to move to a newer concept than trying to unlock the bootloader. Is hijacking the boot order, what SafeStrap does, the right way to go? What about overwriting the kernel and bypassing the bootloader altogether? I remember Hashcode was working with kexec, and for those of you who were there a couple of years ago when SafeStrap was first there for the Motorla RZR, D4, and Bionic, might remember this. It executes a live kernel overwrite, before the bootloader can even come up to verify the signed stock rom/firmware/bootloader.
I've read a couple of people mentioning this, but I'm not sure if its feasible. My point, SafeStrap and KEXEC are two options that need some blockbuster support. Hashcode is the Zeus of Mt. SafeStrape, but where is the God of War and the rest of the bunch to kick ass? Can we pick a direction?
Maybe I'm going about this the wrong way, maybe my message isn't the one that needs to be heard? I haven't posted much over the last couple of years, but I've done a lot of reading over the last few weeks, and I'm just curious if there is a Bat Signal they can use to summon the Justice League and put their collective boots up the ass of Lex Luthor (Verizon and co.)?
Click to expand...
Click to collapse
Dude. There are people working on this, believe me. And people who arent developers or cant contribute directly have posted a bounty to reward whoever can get a workaround. Safestrap does work, regardless of whether you are able to get it to work on your device. I'm guessing its user error. Not really sure what more you expect the community or Hashcode or any other dev to do that they arent already doing...
So after attempting the goomanager method of unlocking my Galaxy S4 and after getting stuck in odin mode, and after a little more limited research, I have read in a few forums that you CANNOT unlock the bootloader of this particular model. Can some please verify or repudiate this for me, and if this is not the case, can someone guide me to a forum that can help me, because I haven't read a forum that specifies whether or not their method will work on this model of the Galaxy S4.
Thanks for any and all help...
First off I'm guessing you didn't read any of the stickies on this forum about rooting and or unlocking this device. Secondly, it depends on which bootloader version you have as to if you can unlock it.
Sent from my SCH-I545 using Tapatalk
Idk exactly what you're talking about, but this phone is rooted and what are you talking about "bootloader version?" Are you making things up? If you're talking about my build number I am MK2. I'm not sure what you're talking about lol. Help me out here.
JACKc2402 said:
Idk exactly what you're talking about, but this phone is rooted and what are you talking about "bootloader version?" Are you making things up? If you're talking about my build number I am MK2. I'm not sure what you're talking about lol. Help me out here.
Click to expand...
Click to collapse
dude you cant unlock bootloader. Only if you were on mdk.... So you need to full wipe odin the factory mk2. then root and then use safestrap. Please read the forums dude
Marshmellow92 said:
dude you cant unlock bootloader. Only if you were on mdk.... So you need to full wipe odin the factory mk2. then root and then use safestrap. Please read the forums dude
Click to expand...
Click to collapse
Lol, I promise you I have searched up and down for a clear answer and I haven't seen it yet. Besides, most of these forums are several months old and I wasn't sure if anything has changed since the next version of this phone is about to be released. I didn't know if, perhaps, Verizon themselves had released an unlocked bootloader like HTC initially did with the DNA.... And I don't need to odin factory mk2, all I needed was a battery pull. I already have Safestrap installed. I'm way ahead of you. I'm not looking for a work-around. I want this damn bootloader unlocked so I can flash Cyanogemod. If that is still impossible I understand, but you people need to chill out. This is the QUESTION AND ANSWERING forum.
JACKc2402 said:
Lol, I promise you I have searched up and down for a clear answer and I haven't seen it yet. Besides, most of these forums are several months old and I wasn't sure if anything has changed since the next version of this phone is about to be released. I didn't know if, perhaps, Verizon themselves had released an unlocked bootloader like HTC initially did with the DNA.... And I don't need to odin factory mk2, all I needed was a battery pull. I already have Safestrap installed. I'm way ahead of you. I'm not looking for a work-around. I want this damn bootloader unlocked so I can flash Cyanogemod. If that is still impossible I understand, but you people need to chill out. This is the QUESTION AND ANSWERING forum.
Click to expand...
Click to collapse
XDA is actually one of the sites that most for the most part is updated daily. There are multiple threads on here stating how the retail version of the Verizon S4 after MDK build ( the 1st release ) cannot have a custom recovery enabling you to flash any aosp ROMs.
Just takes some getting used to when someone is new on here that's all. Browse to the Verizon S4 forums and you'll see a ton of Stickies created addressing these kind of things.
Go to Swappa and get an MDK S4 if you really want CM.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
XDA is actually one of the sites that most for the most part is updated daily. There are multiple threads on here stating how the retail version of the Verizon S4 after MDK build ( the 1st release ) cannot have a custom recovery enabling you to flash any aosp ROMs.
Just takes some getting used to when someone is new on here that's all. Browse to the Verizon S4 forums and you'll see a ton of Stickies created addressing these kind of things.
Go to Swappa and get an MDK S4 if you really want CM.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
See, that's actually helpful. Nice and concise. Believe it or not, I'm not new to XDA. I've been flashing ROMs since my O.G. A855. That phone was a beast! No locked bootloader b.s., one-click-root, simple clockworkmod installation... Those were the good ole days! I simply rarely post because I usually know what I'm doing. My last phone (Droid DNA, wouldn't recommend that phone to anyone) almost kicked my ass. I literally just purchased this Galaxy S4 today and couldn't believe the bootloader is still locked. But alas, Verizon are jerks and you'd probably need 100 years to crack their encryptions on windows 8 64-bit lol. Thanks for the input guys. I suppose I'll settle for Hyperdrive.
JACKc2402 said:
See, that's actually helpful. Nice and concise. Believe it or not, I'm not new to XDA. I've been flashing ROMs since my O.G. A855. That phone was a beast! No locked bootloader b.s., one-click-root, simple clockworkmod installation... Those were the good ole days! I simply rarely post because I usually know what I'm doing. My last phone (Droid DNA, wouldn't recommend that phone to anyone) almost kicked my ass. I literally just purchased this Galaxy S4 today and couldn't believe the bootloader is still locked. But alas, Verizon are jerks and you'd probably need 100 years to crack their encryptions on windows 8 64-bit lol. Thanks for the input guys. I suppose I'll settle for Hyperdrive.
Click to expand...
Click to collapse
LOL. "Settle" for Hyperdrive? I am on the developer edition S4 and can flash any of the ROM's for it, including the ASOP, Cyanogen, whatever. I still come back to Hyperdrive. Simply the best (IMHO). Easy to forget that it's TouchWiz based. All the customization one could want. As stable as any. Don't know exactly what limits safestrap may impose but HD is my DD.
wtherrell said:
LOL. "Settle" for Hyperdrive? I am on the developer edition S4 and can flash any of the ROM's for it, including the ASOP, Cyanogen, whatever. I still come back to Hyperdrive. Simply the best (IMHO). Easy to forget that it's TouchWiz based. All the customization one could want. As stable as any. Don't know exactly what limits safestrap may impose but HD is my DD.
Click to expand...
Click to collapse
I'll trade you my non dev S4... I'm missing CM so bad. HyperDrive isn't bad, it's Just not CM.
ericerk said:
I'll trade you my non dev S4... I'm missing CM so bad. HyperDrive isn't bad, it's Just not CM.
Click to expand...
Click to collapse
Thanks, but I'm hanging on to my DEV Edition. Hope you can find one, or at least an MDK.
wtherrell said:
Thanks, but I'm hanging on to my DEV Edition. Hope you can find one, or at least an MDK.
Click to expand...
Click to collapse
Meh... If the S4 doesn't get unlocked soon, I'll sell it.
JACKc2402 said:
Idk exactly what you're talking about, but this phone is rooted and what are you talking about "bootloader version?" Are you making things up? If you're talking about my build number I am MK2. I'm not sure what you're talking about lol. Help me out here.
Click to expand...
Click to collapse
Making things up? No. Apparently you seem to be missing the forest for the trees.
Start with reading this: http://forum.xda-developers.com/showthread.php?t=2606501
Then read this: http://forum.xda-developers.com/showthread.php?t=2578569
The important thing to know is NOT the build number, it's the bootloader version. You can run whatever build you want if you have the MDK bootloader, and can't if you don't have that bootloader. So, that's the important question, whether or not you understand it.
k1mu said:
Making things up? No. Apparently you seem to be missing the forest for the trees.
Start with reading this: http://forum.xda-developers.com/showthread.php?t=2606501
Then read this: http://forum.xda-developers.com/showthread.php?t=2578569
The important thing to know is NOT the build number, it's the bootloader version. You can run whatever build you want if you have the MDK bootloader, and can't if you don't have that bootloader. So, that's the important question, whether or not you understand it.
Click to expand...
Click to collapse
I see, I apologize to the commenter. But this is why I'm here, to get help with what I am not familiar with. I was a hardcore Moto fan for years, all the way from the A855 until they ruined the experience with the Bionic. That was a terrible device. My first non-Moto phone was the HTC DNA. I had that about 8 months before I just got this Samsung yesterday. They all work by the same basic principles but I am finding quirky little differences that throw me off a little. It seems that with every phone I get flashing gets a little more difficult and I am forced to learn more and more about this OS then I ever intended lol. I honestly appreciate the help guys.
wtherrell said:
LOL. "Settle" for Hyperdrive? I am on the developer edition S4 and can flash any of the ROM's for it, including the ASOP, Cyanogen, whatever. I still come back to Hyperdrive. Simply the best (IMHO). Easy to forget that it's TouchWiz based. All the customization one could want. As stable as any. Don't know exactly what limits safestrap may impose but HD is my DD.
Click to expand...
Click to collapse
HyperDrive is a quirky and clumsy version of CM with mediocre animations. It isn't up to par with a several ROMs, including Eclipse and especially not CM or Paranoid Android. That's my opinion. In fact, I'm about to flash to Eclipse from HD.
wtherrell said:
LOL. "Settle" for Hyperdrive? I am on the developer edition S4 and can flash any of the ROM's for it, including the ASOP, Cyanogen, whatever. I still come back to Hyperdrive. Simply the best (IMHO). Easy to forget that it's TouchWiz based. All the customization one could want. As stable as any. Don't know exactly what limits safestrap may impose but HD is my DD.
Click to expand...
Click to collapse
ericerk said:
I'll trade you my non dev S4... I'm missing CM so bad. HyperDrive isn't bad, it's Just not CM.
Click to expand...
Click to collapse
Agreed, I'd cut off my left nut to get CM on this device.
JACKc2402 said:
Agreed, I'd cut off my left nut to get CM on this device.
Click to expand...
Click to collapse
I'd just buy a dev edition... Save your left nut.