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
Related
ok, i have a question, should i root my lg thirve (lg optimus one) just because i want to go from stock froyo to gingerbread made by cyanogen-mod.
thats all i would want, because my phone is not getting the update, and to get gingerbread i would need to root.
so should i do this, what are the dangers of it, i mean will my phone be vulnerable to dangerous things, will it break or mess up in any way?
No dangers, really. But yes, root. If you are interested in overclocking, tweaking, and installing any app that requires root (just search "root" on market and see what goodies come up), you should root, no questions asked. I highly recommend CyanogenMod as there are so many additional and useful features and it is pre-rooted (obviously). If you don't like modding or experimenting, then stick to the stock ROM.
I gotta be honest with you, when I first landed on the Android world I made myself that very same questions over and over again, until one day I said "what the heck!" and done it.
To be truth, isn't that big of a deal, rotting isn't difficult and isn't bad, you just gotta be carefully about what you do because you'r having access to the System folder, so you can really harm your phone, but if you don't mess up with it, you have nothing to worry about.
Some apps need root access because they use the system folder to make changes, so don't simply install any app that request you so, just those that are known and that you need.
So, in conclusion, Root your device, just don't go on the system folder and make changes if you have no idea what you'r doing.
Root is good and healthy to your phone. It gives you more freedom on using your phone. Really, it lets you do a lot more things that you can't do it on an unrooted stock ROM.
Most of us did that before, and it wont harm you phone's health provided that you don't root/unroot too many times in a week (it is similar to what my parents told me when I am still young and innocent)
Rooting process in most cases wont brick your phone unless you are trying to flash a rooted ROM without knowing it.
But anyway, if you want to try something new, you need to take the risk. And don't blame on others when you bricked your own phone. Maybe you can search on youtube videos or websites for those step by step rooting guides for your phone.
feenius danger
Yes.. root its worth it.. Speeds up your device by removing unnecessary crap, can customize the look much more, rather easy to do.. Just follow a guide on here and good luck .
YES!!!!!!!
rooting you phone adds infinitely more possibilities, and makes your phone a lot faster
also, cyanogen-mod is an amazing ROM,
go ahead, give it a try,
JUST REMEMBER BACK UP EVERYTHING BEFORE FLASHING CYANOGEN-MOD
good luck
dosage1 said:
Yes.. root its worth it.. Speeds up your device by removing unnecessary crap, can customize the look much more, rather easy to do.. Just follow a guide on here and good luck .
Click to expand...
Click to collapse
That's right, there a quite a few (a ton!) sites describing the benefits of it:
http://www.androidcentral.com/root
http://www.appsgeyser.com/blog/2012/03/20/should-i-root-my-android-phone/
http://www.androidpit.com/en/android/forum/thread/403299/So-what-exactly-is-rooting-and-is-it-for-me
http://www.addictivetips.com/mobile/top-10-reasons-to-root-your-android-phone-2/
The only thing I recommend is that you know what you're doing. If thats not the status: In the forums are a lot of posts
Definitely go for it.
The optimus one especially benefits from rooting/applying a new, better rom.
Don't root and unroot your phone too many times.Thats the caution,otherwise as said it gives you more control over your hardware than unrooted phone.
Sent from my LG-P350 using XDA
Gaining full control of your device is a big advantage. In addition to this some really useful apps just run with root.
ricky1001 said:
Don't root and unroot your phone too many times.Thats the caution,otherwise as said it gives you more control over your hardware than unrooted phone.
Sent from my LG-P350 using XDA
Click to expand...
Click to collapse
Actually, if that were true, ROM developers would have long given up and we wouldn't have any of the awesome ROMs floating around out there today. There's absolutely nothing wrong with rooting and unrooting repeatedly, as long you follow the correct procedure every time. Although why anyone would do that stumps me. Either you like your phone rooted, or not.
@singular9:
First off, "upgrade" is a very subjective term. Are you certain the ROM you're looking at will give you significant advantages over the one your phone's running now? While I don't doubt that the people behind the CM ROM for your phone are doing some brilliant work, always assume that something may go wrong. (Unlike Apple, other phone manufacturers source their hardware from all sorts of different places. Two phones, same model may have differently branded components.) If something DOES go wrong, are you prepared to undergo the arduous process that unbricking a phone will involve?
I'd say root your phone if - and ONLY IF:
1. You're a careful person who will read instructions and follow them to the letter, in the order they were set;
2. You're prepared to read up on what "root" is, what the terms used are, and accept that your "upgrade" may not quite offer you the benefits you were looking for (whatever they are, as you didn't specify)
If you're okay with the above, then yeah, I guess I'd say go ahead. My phone's rooted - I love it, and loved every step of the journey I took to root it.
terradune said:
Actually, if that were true, ROM developers would have long given up and we wouldn't have any of the awesome ROMs floating around out there today. There's absolutely nothing wrong with rooting and unrooting repeatedly, as long you follow the correct procedure every time. Although why anyone would do that stumps me. Either you like your phone rooted, or not.
Click to expand...
Click to collapse
haha, it is a joke dude, don't take it seriously. I don't see any reason for unrooting android unless you are preparing to send the phone back for warranty or get it repaired by its manufacturer and tell them : "ohh, I dunno what happened, it just stop working by it self this morning".
Cheers!
Root is the better way to take totally control of your phone !
Absolutely yes!
Yes U should, but read each instructions carefully before u root ur device.
.
Thread moved to Q&A due to it being a question. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
had an Infuse for about a year. loved it and was suprised as to what i was able to learn. i was actually able to trouble shoot some of other peoples issues. most of it was people not following OP correctly. some of them you would think they were scoring with a girl for the first time in high school. they just plug it in and blow their load.
However, day after thankgsiving AT&T had some incredible deals for a refurbed Note. cant beat $31.
I have been learking here for almost a month and reading as i did on the Infuse. trying to gain the confidence i need to take the leap and root.
one thing i am noticing or think i am noticing.....or maybe i dont understand.
stock rooted? you can root phone but not necessarily have CWM ?
Infuse had an all in one package.
from what i am gathering.....when i flash, do i need to flash rom, modem and kernal on 3 different flashes? trying to peice a package that works best? cant say that i notice in descriptions (as with Infuse) ex ; "Joe Blows ROM
UCLB3 modem
super nuclear kernal with OC/UV
i am sure this is in the Super Everything Thread, but sometimes my brain pan does not absorb everything. thats why i read read read and i will read some more. again responses from the more experience give me confidence.
probably my hugest issue is, it seems no matter what rom i look at the main issue is random reboots or phone just shutting down. to me does this almost negate some benefits of rooting?
everybody said the Infuse was unbrickable? for the most part i beleive that, usually somebody not following directions was the problem. regardless, super easy to unbrick and return to stock.
However, when i hear, Do you have a jig? or sending phone out to have fixed, makes me wonder if the Note bricks easier and harder to unbrick. I know that if I try, i can REALLY eff something up.
dont want to do that.
i know every phone is different and every rom works differently on those phones, so i know not to ask which rom is better for me. if i decide to, i will find which rom I like the best.
my Infuse HAS grown up to be a Note and i am happy to climb aboard this forum
To root this phone you flash a kernel to the stock rom. But to do this you have to flash a replacement recovery, and that is done with a pc using Samsung's software named Odin.
i am familiar with Odin. i have used it on many occasions and am comfortable with that. however even in the reading i have done this is the first i have heard of a "replacement recovery".
this sounds as if flashing the new kernal to the stock rom is what will root the phone?
i thought the tar file is what did this.
i will keep reading until i come up 2 threads or suggestions of rooting that sound as if the process is the same.
dont misunderstand, i am not saying that anybody is wrong. i am sure all of these methods work. again, if i want to i can really screw something up. i am sure some of these different methods are some different terminology. mainly i want to feel confident and have my process firmly embedded in my mind and act it out properly.
check this post out if you want a super easy way to get started...
http://forum.xda-developers.com/showpost.php?p=35499256&postcount=4
Its explained very well here. Step by step
http://rootgalaxynote.com/galaxy-no...y-note-sgh-i717-icsgingerbreadeasiest-method/
Sent from my Samsung-SGH-I717 using xda app-developers app
The stock recovery doesn't let you flash anything. So you flash the replacement recovery with Odin. You are replacing the stock with either CWR or TWRP.
Then, using the new recovery you flash the rooted kernel, or any rom you like.
As for your Super Everything Thread .. Here it is: http://forum.xda-developers.com/showthread.php?p=28040353
Also we have a Stupid Question Thread here:
http://forum.xda-developers.com/showthread.php?p=32925977 just in case you have the need.
Welcome to the Note.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Bubbajoe40356 said:
Also we have a Stupid Question Thread here:
http://forum.xda-developers.com/showthread.php?p=32925977 just in case you have the need.
Welcome to the Note.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
i am sure i will be getting plenty of use out of that one.
appreciate your help. both you and the captain explained it very plainly and simply, eliminating any confusion.
thank you both.actually very similar to Infuse.
now i just have to decide whether i would benefit from it.
hmmmmmm
Installing the recovery is worth the trouble. Besides the romantic flashing, you can change modems, install mods, make a backup.
rangercaptain said:
Installing the recovery is worth the trouble. Besides the romantic flashing, you can change modems, install mods, make a backup.
Click to expand...
Click to collapse
yeah, and i have done all that with the Infuse. other then mods, tweaks and themes, what else did i benefit from?
Infuse was on Froyo and had a multitude of ROMS and interfaces to choose from. GB, ICS and JB. i am already ICS and JB is the only step up. actually with the similarities between the two, how much am i really gaining or what am i changing?
im kind of shopping some ROMS and looking for something to catch my eye. i am not seeing too many differences. i do have a bigger screen though and i did like the tablet mode of PA. only that and CM10 were the only ones that had tablet mode there.
im really not in any hurry and there is the rumor of official JB for the Note, but i know how that went with GB for the Infuse. the pushed it out too quick and had many problems. unofficial releases were more reliable and theming was pretty cool.
once again, i appreciate the input there Ranger.
All this, but no where has it been said that you have indeed a i717 Note. This, I think is how most people find themselves with a brick. Being in the wrong device section of the forum. Trivial and redundant as it sounds no one can afford to get this confused.
:screwy:Never mind, see it now, just had to run my big mouth, didn't I ?:banghead:
BLACKSTAR XI -SGH-I717 xda-developers app SAMSUNG done right
Yeaaaah, ooops. Well there's another use for the Spen and a place to store it.
But you are correct, I have witnessed the destruction of at least ten notes and some S2's by being in the wrong forum.
This is dangerous business.
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.
I'm currently running an 8.9" HDX with a working AOSP - thanks to all the help I got on this forum and specifically followed this thread:
http://forum.xda-developers.com/showthread.php?t=2582773
but the main applications that I now need to use for work are iOS only (don't ask... NOT happy) so I'm back to carrying an iPad around everywhere and as such I'm going to sell my HDX. Before I do that I need to return it back to stock... I found a number of threads referencing how to do this but wanted to be extra careful. At present I'm just running Safestrap with a second ROM slot that I boot with all the non-standard stuff, I got there via SuperSU.
What's the right sequence of de-activates / un-installs / magic incantations to get this thing back to "boring, stock" just like it would come from Amazon? Is it as simple as re-enabling over-the-air updates and letting it "fix" itself? Or do I need to specifically back out some of the safestrap/superSU stuff first?
Help? (and THANKS)
ljwobker said:
I'm currently running an 8.9" HDX with a working AOSP - thanks to all the help I got on this forum and specifically followed this thread:
http://forum.xda-developers.com/showthread.php?t=2582773
but the main applications that I now need to use for work are iOS only (don't ask... NOT happy) so I'm back to carrying an iPad around everywhere and as such I'm going to sell my HDX. Before I do that I need to return it back to stock... I found a number of threads referencing how to do this but wanted to be extra careful. At present I'm just running Safestrap with a second ROM slot that I boot with all the non-standard stuff, I got there via SuperSU.
What's the right sequence of de-activates / un-installs / magic incantations to get this thing back to "boring, stock" just like it would come from Amazon? Is it as simple as re-enabling over-the-air updates and letting it "fix" itself? Or do I need to specifically back out some of the safestrap/superSU stuff first?
Help? (and THANKS)
Click to expand...
Click to collapse
Depends on how you used SafeStrap. If you ONLY installed in the stock rom, then an update likely would do it. If you installed safestrap a second time from the working rom-slot as well, then updates won't work, because the BL & Kernel CANNOT be flashed.
The best thing is to remove all wifi connections with "forget network", then go into safe strap & activate stock rom. Then go back to the boot options & delete the rom-slot you created. Boot back into stock partition, uninstall Safestrap & then reconnect to wifi & check for updates.
I would HIGHLY recommend you follow my directions about forgetting nearby, if not all, wifi networks. If you turn wifi off in a slot, but not in stock, or vice versa, it can cause boot issues , as well as wifi issues.
I would not return it to stock. That device could go for a premium right now to other users simply because you can get AOSP and so many cannot yet.
EniGmA1987 said:
I would not return it to stock. That device could go for a premium right now to other users simply because you can get AOSP and so many cannot yet.
Click to expand...
Click to collapse
Why would it go for a premium? It is absolutely 100% rootable. It has not been patched against the VolumeManager/vold ASEC exploit. In fact, I am nearly certain the bootloader can bed unlocked from my investigation. Unfortunately that part is beyond my abilities & exceeds the time I would need to get caught up on the msm89xx+ SoC, but I would just about bet the farm that it can be done.
GSLEON3 said:
Why would it go for a premium? It is absolutely 100% rootable. It has not been patched against the VolumeManager/vold ASEC exploit. In fact, I am nearly certain the bootloader can bed unlocked from my investigation. Unfortunately that part is beyond my abilities & exceeds the time I would need to get caught up on the msm89xx+ SoC, but I would just about bet the farm that it can be done.
Click to expand...
Click to collapse
Because when I posted that we had no root, and it was still a "hopefully sometime soon" with 9/10 of the HDX's on a version that couldnt be rooted.
It is nice that we have one Chinese method now and that you might get something soon, though I think you are suddenly pretty full of yourself on these forums with the little bit of knowledge you gained recently. Much better people at this have not been able to get the bootloader cracked. But best of luck to you.
EniGmA1987 said:
Because when I posted that we had no root, and it was still a "hopefully sometime soon" with 9/10 of the HDX's on a version that couldnt be rooted.
It is nice that we have one Chinese method now and that you might get something soon, though I think you are suddenly pretty full of yourself on these forums with the little bit of knowledge you gained recently. Much better people at this have not been able to get the bootloader cracked. But best of luck to you.
Click to expand...
Click to collapse
Actually, the little time I've been around is well over a decade. This ain't my first username. Secondly, there is already an ASEC based root that WAS created by someone better with this stuff than me, so it's not full of myself, it is FACT. I am rooted, have been each & every time, without blocking anything & without having to sacrifice connectivity, another FACT. Coincidentally, the reason it was never published, well I'd venture a guess that it's because of stupid posts & self-entitled people ignorantly writing or PM'ing to insist that things be done for them on their terms. Another fact, it was that kind of crap that made me leave this forum a few months ago. So, I don't know what "better people" you are talking about that have failed at it, but I do know the better people that have done it.
Another fact, anyone at all can read & discover just how small the patch for the ASEC vulnerability was. It doesn't take a genius to then decompile the vold & search for the that one event which was used to patch it, which subsequently tells all you need to know.
GSLEON3 said:
Actually, the little time I've been around is well over a decade. This ain't my first username. Secondly, there is already an ASEC based root that WAS created by someone better with this stuff than me, so it's not full of myself, it is FACT. I am rooted, have been each & every time, without blocking anything & without having to sacrifice connectivity, another FACT. Coincidentally, the reason it was never published, well I'd venture a guess that it's because of stupid posts & self-entitled people ignorantly writing or PM'ing to insist that things be done for them on their terms. Another fact, it was that kind of crap that made me leave this forum a few months ago. So, I don't know what "better people" you are talking about that have failed at it, but I do know the better people that have done it.
Another fact, anyone at all can read & discover just how small the patch for the ASEC vulnerability was. It doesn't take a genius to then decompile the vold & search for the that one event which was used to patch it, which subsequently tells all you need to know.
Click to expand...
Click to collapse
lol. I am glad you know your FACTS. No need to act so butthurt.