Rooting/Cyanogenmod (Macbook) - AT&T Samsung Galaxy S II SGH-I777

I'm coming from an iPhone after having all previous gens so I'm completely clueless about Android and the ins/outs of the OS.
I only own MacBooks and curious if:
1. I can root my SGS2, if so how?
2. Can I install the Cyanogenmod's?
Also, what exactly are the Cyanogenmods? I've been watching YouTube vids but actually explain what they are and how to install from start to finish on SGS2 w/ Macbook.
thanks

See this thread:
http://forum.xda-developers.com/showthread.php?t=1311081

Gary's helping each other out, right on.
Definitely read that guide though. One of the single most important steps to become familiar with. Heimdall is what you'll be looking for. Odin isn't Mac compatible.
And a word of caution. IPhones are one of the harder things to 'brick' or ruin. Recovery mode is baked into it. For android that's kind of what download mode is. But having an issue while flashing bootloaders CAN break that, and there's usually nothing you can do to recover from a 'hare's brick.
The good news is 99% of things to do to your phone don't require flashing bootloaders. If ever in doubt, don't risk it. Just not worth it.
Sent from my páhhōniē

Please do not double post questions like this... You dont need to post the same question in two different boards.

Related

[Q] Question regarding rooting and roms

Hey guys, as you can see I am new to the whole wide world of android. I have had an iPhone since 2007 and recently dropped my iPhone 4 on the pavement which completely wrecked the screen. I seized the opportunity to buy an android. I got this s2 for 350 on eBay.
Anyway... I have absolutely no idea what I am getting into here. I have watched a ton of videos and still am really lost. (Sadly)
I have this s2 at 4.0.3 and am completely lost when it comes to how to flash a rom. I get we have to use ODIN, Kies and your rom. Am I missing anything else?
I want to use this. galaxys2root. com/att-galaxy-s2/aokp-ics-rom-for-att-galaxy-s2-sgh-i777-best-ics-rom/ << I cannot post links so its just a space in between the .com
I have seen videos where I have to root the thing first- or will this do it for me? I have also seen "roms" that are 400 MB in size but this one I like its 134... Am i missing any files or something? I have done searching but I end up more confused than I started. If someone could give me a push in the right direction that would be a great help!
This is the first phone I am actually confused with... I am sure it is easy, just not for a guy who has had an iPhone and developed for them since then... (I am co founder of whited00r )
Start with the links in the sticky. Be sure to read them all.
You said your phone is already on 4.0.3, which is Ice Cream Sandwich (ICS). That means it's not stock (aka factory settings, out of the box, etc). I'd personally suggest after reading all the links, returning to stock and starting over from scratch as it's the best way to ensure you don't have any problems, especially since you don't really know what the previous owner did to your phone. The links for returning to stock and for flashing custom ROMs are also in the sticky. Please don't read just these links, read at least all of the other links posted there. That's just the starting point mind you, you should probably do more reading after that on stuff in the posts that you don't understand. I know this will take a lot of time, but it's for everyone's benefit that you fully understand everything you do to your phone before you do it.
I'll even help you out with a couple other links I think may be useful which aren't in the sticky.
ROM vs. Kernel
Odex vs. Deodex
Please hit my thanks button if I helped you. Good luck and welcome to the forums!
pcamlin said:
Hey guys, as you can see I am new to the whole wide world of android. I have had an iPhone since 2007 and recently dropped my iPhone 4 on the pavement which completely wrecked the screen. I seized the opportunity to buy an android. I got this s2 for 350 on eBay.
Anyway... I have absolutely no idea what I am getting into here. I have watched a ton of videos and still am really lost. (Sadly)
I have this s2 at 4.0.3 and am completely lost when it comes to how to flash a rom. I get we have to use ODIN, Kies and your rom. Am I missing anything else?
I want to use this. galaxys2root. com/att-galaxy-s2/aokp-ics-rom-for-att-galaxy-s2-sgh-i777-best-ics-rom/ << I cannot post links so its just a space in between the .com
I have seen videos where I have to root the thing first- or will this do it for me? I have also seen "roms" that are 400 MB in size but this one I like its 134... Am i missing any files or something? I have done searching but I end up more confused than I started. If someone could give me a push in the right direction that would be a great help!
This is the first phone I am actually confused with... I am sure it is easy, just not for a guy who has had an iPhone and developed for them since then... (I am co founder of whited00r )
Click to expand...
Click to collapse
From now on, don't watch any videos. They tend to be incomplete and usually outdated. Also, don't use any files or methods you find anywhere else besides XDA.
Like karate104 said, read the stickies at the top of the forums; they will tell you everything you need to know in detail. Read this one in particular. It has links to a lot of useful guides.
you also need to be wary of what you read and watch on gs2root. com
when i first started i used the rooting technique with the kernel from there and ended up with no wifi and ended up having to flash entropy's daily driver to recover
as the guys above said, read the stickies here and go over it a million times until it makes sense
flashing can open up loads of features, but you can very easily make your phone unusable (easily fixable once not hard bricked) but better avoid the trouble than finding a fix
Another victim on galaxys2root!
Sigh!

[Q] I think I can stump xda forums... seriously messed up 16gb

It's been a while since I've worked on this, and I still can't find anyone with a similar problem on xda. Does anyone have a clue what's going on with this thing?
First, I got it working just fine with CM7 installed to the nook itself, not running from an sd card. That worked for a bit, then it started just shutting off with no obvious reason.
Also, if I make any changes, like uninstalling apps, it goes right back after a reboot - which happens whether I want it to or not. This applies to changes done with CWM as well, even installing a new rom.
On top of that, it won't boot from an sd card, so that sucks too.
Lastly (I think, it's tough to keep track of all these problems) abd doesn't recognize the device, and for that matter the operating system doesn't either. I've been using Ubuntu Lucid if that matters, but it didn't have issues detecting the device before.
I'm pretty novice, but I think this is a very complicated problem in need of expert advice. Any answers, tips, advice, or pointing in the right direction for any of my problems here would be awesome. Does anyone have any ideas?
Thanks.
Dude you say your a novice thats one... Two you are being critical of people who volunteer on this stuff. You can't be serious. You obviously have not read the support threads because you are not the only one with these problems and those that have them also did not read enough initially and failed to follow some step. Moreover, even if your problem were unique who do you think you are getting upset at anyone but yourself for taking the risk. Read the support thread for cm7 Mr. Ungrateful... flash back to stock and leave this forum alone until you 1. Learn what it means to be grateful. 2. Learn to follow instructions. The end
it is impossible to stump xda...
rickyshortcuts said:
Dude you say your a novice thats one... Two you are being critical of people who volunteer on this stuff. You can't be serious. You obviously have not read the support threads because you are not the only one with these problems and those that have them also did not read enough initially and failed to follow some step. Moreover, even if your problem were unique who do you think you are getting upset at anyone but yourself for taking the risk. Read the support thread for cm7 Mr. Ungrateful... flash back to stock and leave this forum alone until you 1. Learn what it means to be grateful. 2. Learn to follow instructions. The end
Click to expand...
Click to collapse
Thanks, that reminds me, I did follow all steps to the letter without a hitch to get CM7 going. It wasn't until after it was running for a few days that this happened. Also, in the aftermath while trying to solve the problem, I did everything I can think of to completely brick the nook so that I might be able to use some of the methods here to unbrick.
And just to defend my good name, I think it's a stretch to imagine I've been critical of anyone. To reference your other post on these forums, perhaps you might reconsider how to be helpful. Let me help you out with that.
because it is SERIOUSLY a hard brick, then you gotta get serious about your attack on this sick puppy. get a #6 torx and open it up and get directly at the internal sd card ( which sounds like you have trashed... )
hth
.
let us know when you got it open...
Dude!!!
rickyshortcuts said:
Dude you say your a novice thats one... Two you are being critical of people who volunteer on this stuff. You can't be serious. You obviously have not read the support threads because you are not the only one with these problems and those that have them also did not read enough initially and failed to follow some step. Moreover, even if your problem were unique who do you think you are getting upset at anyone but yourself for taking the risk. Read the support thread for cm7 Mr. Ungrateful... flash back to stock and leave this forum alone until you 1. Learn what it means to be grateful. 2. Learn to follow instructions. The end
Click to expand...
Click to collapse
One: This was a completely pointless flaming. Two: For being a novice he seems to be a bit more informed than you are. This is an issue, however not a common one. And from what I have read in these forums there is not as yet a fix. Three: I didn't read any ungratefulness, criticism, nor any hint of being upset. And Four: If you can't help out or give any useful advice then maybe you should "leave this forum alone" until you learn to be more civil.
chuckweiss2 said:
Thanks, that reminds me, I did follow all steps to the letter without a hitch to get CM7 going. It wasn't until after it was running for a few days that this happened. Also, in the aftermath while trying to solve the problem, I did everything I can think of to completely brick the nook so that I might be able to use some of the methods here to unbrick.
And just to defend my good name, I think it's a stretch to imagine I've been critical of anyone. To reference your other post on these forums, perhaps you might reconsider how to be helpful. Let me help you out with that.
Click to expand...
Click to collapse
Well put, and Props.....
I don't know if I can help out but I think I can point you in the right direction.
http://forum.xda-developers.com/showthread.php?t=1619615
This seems to be a hardware problem, but I don't think anyone is sure what is causing this.
Good luck with finding a fix.
went and found a XDA link for res-erecting bricked devices. it by @adamoutler and looks like a goodie !
ModeDetect USBID Detector
http://forum.xda-developers.com/showthread.php?t=1257434
hth
.
( you can tell that Adam is passionate about his tech. what do they feed those boys down in Louisiana beside crawdads ? )
Alright, so thanks to old_fart and DavDoc I've determined two of my problems, and I think there are four.
First, DavDoc's linked thread describes perfectly what's happening with problem one, what I'm calling the Groundhog Day Syndrome for no particular reason. Any changes to my nook go right back after it's powered off.
Second, I checked out old_fart's linked thread and I'm pretty sure even though I have a blank screen it's still on in one mode or another. The program doesn't work though because of problem #3 (to be explained) but it seems sensible because to power it back on I must first hold the power button for an extended period of time and release, then hold it again for the normal power-up.
Problem number three is that the nook is not recognized by either Ubuntu or Windows when plugged in anymore. Thus that program not working, and also adb. I may be able to determine that one from error logs as soon as I figure out what in the world the error logs are saying.
Fourth and hopefully final, it won't boot from sd. I'll figure that out too.
Thanks for the advice so far, this forum is definitely indispensable for people who like to learn from playing with technology.

[Q] Better Rooting Methods

Before anyone flames me for creating this thread and then closing it, I just want to let staff know that I did indeed read the sticky threads.
All the instructions for how to root a C6806 on this site seem a bit complex with many steps and quite risky if you are not a Linux and Android phone geek who knows exactly what they are doing. It seems way too easy to make a mistake and permanently brick a phone or lose Dram keys or simply not be able to completely unroot for warranty's sake.
I used to work in the IT field over a decade ago with some training in Network Technology before I got married and I find these instructions too risky for an expensive phone that is too vital for personal and business needs to take a moderate to strong risk of damaging the phone beyond warranty. I can only imagine how someone with little to no Linux or Android experience would fare trying to follow all these steps.
I was hoping that someone could develop a program or app that could do this a lot easier. Not necessarily one click root easy as ideal as that might be but at least simplifying enough so the less than geekworthy can root this phone. Not making rooting feasible for the general public does only encourages future phone makers to keep phones locked and unrooted.
I would really like to use the 64GB SD Card for apps and I would like to use Avast Security for rooted users but there is no way I can trust myself through all the steps of flash software download, system backup, boot unlock, system version rollback, pre-flash procedures, flash, post-flash inspection and probably a few other things I missed.
Unfortunately it's a bit more complex than that.. Unless you unlock your bootloader or have root you won't be able to run the app that you want to unlock the bootloader and/or root with.
Good news is you are wrong re "easy to hardbrick" - flashing stock firmware always an option to recover the device.
At the end of the day to get the benefits of what you call "risky" you will have to take a few "risks"
Sent from my C6833 using Tapatalk
As buzzy said, there really is no risk in hard bricking the zu unless you really are inept. The steps are easy once you understand them:
1. Downgrade to 532 ftf (read my sticky)
2. Root with Bin4ry's or [NUT]'s tool (see my or lordmanhattan's threads)
3. Back up TA (see lord's thread)
4. Flash latest FTF
5. Unlock BL and flash a rootable kernel
The problem with a 'tool' is you never know what they have donr or not and how to recover.
Sent from CarbonROM on my Z-Ultra
It's already very easy to root the Ultra if you're either on .681 or .757 (latest firmware). All you have to do is to flash a kernel and then SuperSU. 2 minutes.
The real issue is what we have to do BEFORE rooting. The TA backup is a pain in the ass, and if Sony would've dropped the whole DRM thing, all we'd have to do would be to unlock the bootloader and flash a kernel.
It's not possible to make a "one click" solution that includes TA backup, so there really isn't any better way of doing it today. It's very easy once you've backed up the TA partition, and you'll only ever do it once per device.
Sent from my C6833 using Tapatalk
blueether said:
As buzzy said, there really is no risk in hard bricking the zu unless you really are inept. The steps are easy once you understand them:
1. Downgrade to 532 ftf (read my sticky)
2. Root with Bin4ry's or [NUT]'s tool (see my or lordmanhattan's threads)
3. Back up TA (see lord's thread)
4. Flash latest FTF
5. Unlock BL and flash a rootable kernel
The problem with a 'tool' is you never know what they have donr or not and how to recover.
Sent from CarbonROM on my Z-Ultra
Click to expand...
Click to collapse
Is that the order to do them in? Each step seems to be its own sticky thread.
LordManhattan said:
It's already very easy to root the Ultra if you're either on .681 or .757 (latest firmware). All you have to do is to flash a kernel and then SuperSU. 2 minutes.
The real issue is what we have to do BEFORE rooting. The TA backup is a pain in the ass, and if Sony would've dropped the whole DRM thing, all we'd have to do would be to unlock the bootloader and flash a kernel.
It's not possible to make a "one click" solution that includes TA backup, so there really isn't any better way of doing it today. It's very easy once you've backed up the TA partition, and you'll only ever do it once per device.
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
Impossible? Why? Unless I read the thread wrong awhile back, it appears that the TA backup thread had a link to a program just for TA backup. It just didn't have everything else that is relatively easy. Why can't a one click root program be built as an extension of that program?
Are the DRM keys the same or unique for every device of a specific model? My husband and I each bought a C6806 directly from Sony's Play Store the very first day they went on sale.
Do I need to flash a kernel or even unlock the bootloader if I'd like to keep the stock OS?
polargirl said:
Is that the order to do them in? Each step seems to be its own sticky thread.
Click to expand...
Click to collapse
Why would I post them out of order?
There is really only one sticky thread that is needed, Lordmanhattan's one. The one I wrote (for the first step) is also covered in LordManhattan's guide, just that if you read my thread you wont temporarily lose your imei no.
polargirl said:
Impossible? Why? Unless I read the thread wrong awhile back, it appears that the TA backup thread had a link to a program just for TA backup. It just didn't have everything else that is relatively easy. Why can't a one click root program be built as an extension of that program?
Are the DRM keys the same or unique for every device of a specific model? My husband and I each bought a C6806 directly from Sony's Play Store the very first day they went on sale.
Do I need to flash a kernel or even unlock the bootloader if I'd like to keep the stock OS?
Click to expand...
Click to collapse
No it's not impossible, but remember that all the dev work is done for free, in our spare time, and more often than not to itch a scratch the "we" have.
Yes the DRM keys are unique to each device
No you dont need to unlock the bootloader if you only want root, but it will make life alot easier in the longrun as you will then be able to flash a kernel that has recovery and is simple to install root on. As our phones get more secure you will have to run a custom kernel and recovery to have root
blueether said:
Why would I post them out of order?
There is really only one sticky thread that is needed, Lordmanhattan's one. The one I wrote (for the first step) is also covered in LordManhattan's guide, just that if you read my thread you wont temporarily lose your imei no.
No it's not impossible, but remember that all the dev work is done for free, in our spare time, and more often than not to itch a scratch the "we" have.
Yes the DRM keys are unique to each device
No you dont need to unlock the bootloader if you only want root, but it will make life alot easier in the longrun as you will then be able to flash a kernel that has recovery and is simple to install root on. As our phones get more secure you will have to run a custom kernel and recovery to have root
Click to expand...
Click to collapse
Please link me to that Lordmaahattan thread as he probably has quite a few.
I am quite happy and grateful that there are people like you guys who do this stuff even if it is just to "scratch the itch" and say "we have". I just wish some people would take the battle against the smartphone tyrants to a higher level as all. I have no right asking you guys to take it to a higher level but who else is more able and willing to do it? The need to render locking smartphones futile is a just and noble war.
Is there an Android equivalent to ghosting in Windows that copies everything on the phones' memory right down to the DRM keys or an other mirroring method? I'd feel a lot more comfortable making a clone image than just partial backups.
How can I tell if a TA backup is completely successful before I flash? I guess the Lordmanhattan thread should have info on how to relock and unroot?
polargirl said:
Please link me to that Lordmaahattan thread as he probably has quite a few.
I am quite happy and grateful that there are people like you guys who do this stuff even if it is just to "scratch the itch" and say "we have". I just wish some people would take the battle against the smartphone tyrants to a higher level as all. I have no right asking you guys to take it to a higher level but who else is more able and willing to do it? The need to render locking smartphones futile is a just and noble war.
Is there an Android equivalent to ghosting in Windows that copies everything on the phones' memory right down to the DRM keys or an other mirroring method? I'd feel a lot more comfortable making a clone image than just partial backups.
How can I tell if a TA backup is completely successful before I flash? I guess the Lordmanhattan thread should have info on how to relock and unroot?
Click to expand...
Click to collapse
The definitive thread is this one http://forum.xda-developers.com/showthread.php?t=2569904, quite complex to read, but simple when you understand it. The problem is that it caters for all, ie locked and unlocked, 4.2 to 4.4 etc
This thread http://forum.xda-developers.com/showthread.php?t=2593918 is how to first downgrade and keep the imei number, not strictly needed but might stop you from panicking when it vanishes.
I quite like the way sony do it, allowing you to unlock the bootloader from their dev site, although it does mean the loss of DRM keys.
You can back up the whole phone with dd (often called disk destroyer for how dangerous it can be), but you may need root first - never done it and I would not recommend doing it.
The TA partition is the only one that is really important to back up, and going back to 'factory' is as easy as using the same app to write the backup back then flashing a FTF
blueether said:
I quite like the way sony do it, allowing you to unlock the bootloader from their dev site, although it does mean the loss of DRM keys.
You can back up the whole phone with dd (often called disk destroyer for how dangerous it can be), but you may need root first - never done it and I would not recommend doing it.
The TA partition is the only one that is really important to back up, and going back to 'factory' is as easy as using the same app to write the backup back then flashing a FTF
Click to expand...
Click to collapse
I can't say I agree. Although Sony has been generous with the unlocking process, I find myself wondering why it was necessary to lock it in the first place. Polargirl isn't off mark, I spent half a day in frustration (and losing my DRM keys) before I managed to unlock and root. Once I did of course it was sweet, but the path there was a bit perplexing (a myriad of threads here) and quite scary (what if I brick it because I misread one of the 9 different threads?).
That being said, I came from Note II which was a cakewalk - I might be a bit spoiled :cyclops:
Edit: Not to mention, my very first post here was because a rooting thread was obsolete so I, on LordManhattan's advice got in touch with the mods to have said thread un-stickied. This forum is in fact a bit of a mess.
polargirl said:
Is that the order to do them in? Each step seems to be its own sticky thread.
Impossible? Why? Unless I read the thread wrong awhile back, it appears that the TA backup thread had a link to a program just for TA backup. It just didn't have everything else that is relatively easy. Why can't a one click root program be built as an extension of that program?
Are the DRM keys the same or unique for every device of a specific model? My husband and I each bought a C6806 directly from Sony's Play Store the very first day they went on sale.
Do I need to flash a kernel or even unlock the bootloader if I'd like to keep the stock OS?
Click to expand...
Click to collapse
Well okay then. Make a one-click solution that downgrades your device to a firmware that has the exploit that Bin4ry's root tool can root, then get a tool to backup the TA partition, while automatically granting it root access, and then unlock the bootloader without you having to enter your IMEI and unlock key, oh... and then update to the latest firmware and also automatically flash Jackie's kernel, boot into recovery, automatically flash SuperSU and reboot.
Not only would it potentially take several hours for the tool to finish, but it will never ever happen. Ever.
Sent from my C6833 using Tapatalk
Chima2 said:
I can't say I agree. Although Sony has been generous with the unlocking process, I find myself wondering why it was necessary to lock it in the first place. Polargirl isn't off mark, I spent half a day in frustration (and losing my DRM keys) before I managed to unlock and root. Once I did of course it was sweet, but the path there was a bit perplexing (a myriad of threads here) and quite scary (what if I brick it because I misread one of the 9 different threads?).
That being said, I came from Note II which was a cakewalk - I might be a bit spoiled :cyclops:
Edit: Not to mention, my very first post here was because a rooting thread was obsolete so I, on LordManhattan's advice got in touch with the mods to have said thread un-stickied. This forum is in fact a bit of a mess.
Click to expand...
Click to collapse
Thank you for posting that you agree with me and for also seeing the problem: The instructions are indeed complex and chaotically spread out over nine different threads making it easy to miss a step.
LordManhattan said:
Well okay then. Make a one-click solution that downgrades your device to a firmware that has the exploit that Bin4ry's root tool can root, then get a tool to backup the TA partition, while automatically granting it root access, and then unlock the bootloader without you having to enter your IMEI and unlock key, oh... and then update to the latest firmware and also automatically flash Jackie's kernel, boot into recovery, automatically flash SuperSU and reboot.
Not only would it potentially take several hours for the tool to finish, but it will never ever happen. Ever.
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
It doesn't have to be all (one click root) or nothing. Even partial simplification would help. Anything better than the several different steps over nine different threads that Chima2 was referring to would help. 3 or even 4 steps in one thread is better than the "solution" currently available.
polargirl said:
Thank you for posting that you agree with me and for also seeing the problem: The instructions are indeed complex and chaotically spread out over nine different threads making it easy to miss a step.
It doesn't have to be all (one click root) or nothing. Even partial simplification would help. Anything better than the several different steps over nine different threads that Chima2 was referring to would help. 3 or even 4 steps in one thread is better than the "solution" currently available.
Click to expand...
Click to collapse
Buy a ZTE if you want hard
Why should I or Lordmanhattan (or anyone) rewrite what has already been written. I, at least, have written the steps out more times than I care to remember. The process is not that hard, and the steps are well documented in well written english
blueether said:
Buy a ZTE if you want hard
Why should I or Lordmanhattan (or anyone) rewrite what has already been written. I, at least, have written the steps out more times than I care to remember. The process is not that hard, and the steps are well documented in well written english
Click to expand...
Click to collapse
Why? Because they aren't well written. They appear scattered and chaotic to everyone who isn't familiar with this site. Chima2 and I were just trying to give feedback is all. If more people just browsing for rooting solutions were to signup and post, they would probably agree as well. They just aren't here to give you even more feedback.
polargirl said:
Why? Because they aren't well written. They appear scattered and chaotic to everyone who isn't familiar with this site. Chima2 and I were just trying to give feedback is all. If more people just browsing for rooting solutions were to signup and post, they would probably agree as well. They just aren't here to give you even more feedback.
Click to expand...
Click to collapse
It took me about a week of reading in my spare time to get my bearings and feel confident that I could start to modify my phone. That is a small amount of effort to put forth for a device that I plan to have for at least the next year. Yes it was a little confusing but I managed and am certainly not gifted when it comes to intelligence. I feel that any average person that sets their mind to it can succeed, and any specific questions will generally be answered if possible.
adfurgerson said:
It took me about a week of reading in my spare time to get my bearings and feel confident that I could start to modify my phone. That is a small amount of effort to put forth for a device that I plan to have for at least the next year. Yes it was a little confusing but I managed and am certainly not gifted when it comes to intelligence. I feel that any average person that sets their mind to it can succeed, and any specific questions will generally be answered if possible.
Click to expand...
Click to collapse
Enough said! It might be worth it to you but probably not to most people.
polargirl said:
Enough said! It might be worth it to you but probably not to most people.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=2031989&postcount=45
polargirl said:
Enough said! It might be worth it to you but probably not to most people.
Click to expand...
Click to collapse
If a week of reading is to much for some then that is good, they shouldn't root their phones.
When people have really 'simple' ways of doing things they tend to skip steps and blame people for it. When something seems hard and daunting they read carefully and completely before starting, then read step by step as they go.
Could the 9 stickies be updated to 1 thread with all information? Why yes they could, and if it is important to you that it be done the best solution would be to write the new thread yourself. It would be a great way to give back to the community. If you notice something you find wrong, and its in your power to fix it, then do so.
Sent from my C6806_GPe using Tapatalk
_Dennis_ said:
If a week of reading is to much for some then that is good, they shouldn't root their phones.
When people have really 'simple' ways of doing things they tend to skip steps and blame people for it. When something seems hard and daunting they read carefully and completely before starting, then read step by step as they go.
Could the 9 stickies be updated to 1 thread with all information? Why yes they could, and if it is important to you that it be done the best solution would be to write the new thread yourself. It would be a great way to give back to the community. If you notice something you find wrong, and its in your power to fix it, then do so.
Sent from my C6806_GPe using Tapatalk
Click to expand...
Click to collapse
That is quite the cynical statement you posted and apparently contrary to even the spirit of this site let alone development and hacking in general. A better good for society is rending the need to root futile should be the goal and easily within reach of this site's members.
Another newbie, zxc1251, has indeed did just that and I have been helping that member with instruction simplification.
http://forum.xda-developers.com/showthread.php?t=2769782
The only problem with that is newbies tend to be quite limited in their tech knowledge thus limited in their usefulness when it comes to simplifying instructions for the tech ignorant and semi-ignorant public but I guess some relatively tech ignorant people need to start this if a revolution against unrooted, jailed or otherwise restricted access phones is to happen.
I am trying my best with the knowledge and tools that I have to get this going.
polargirl said:
That is quite the cynical statement you posted and apparently contrary to even the spirit of this site let alone development and hacking in general. A better good for society is rending the need to root futile should be the goal and easily within reach of this site's members.
Another newbie, zxc1251, has indeed did just that and I have been helping that member with instruction simplification.
http://forum.xda-developers.com/showthread.php?t=2769782
The only problem with that is newbies tend to be quite limited in their tech knowledge thus limited in their usefulness when it comes to simplifying instructions for the tech ignorant and semi-ignorant public but I guess some relatively tech ignorant people need to start this if a revolution against unrooted, jailed or otherwise restricted access phones is to happen.
I am trying my best with the knowledge and tools that I have to get this going.
Click to expand...
Click to collapse
The reason I had the 'do it yourself' attitude is all the information to make a new thread is there, just needed presentation, something tech geeks aren't well known for.
There should always be a need to root. Average use case for a phone, having security is important since you store a lot of sensitive information. If phones came rooted or came so rooting was extremely easy imagine how many people would loose their bank account info or their contact info to the not so nice side of the Internet.
Edit:
Let me use this analogy. If you wanted to change the transmission in you car would you
A) search the internet for 15 minutes and the open your hood and start disconnecting things or
B) Spend at least a few hours looking at the specifics for your car (if you've change a few transmissions before) or as long as it takes for you to feel comfortable you won't destroy your car?
If you wanted Linux on your laptop would to research the drivers, installation procedures, and distros first or just download the first one and hope you know how to install it?
All I'm saying in researching is not a bad thing, if more people did it, less would brick their phones.
Sent from my C6806_GPe using Tapatalk
_Dennis_ said:
The reason I had the 'do it yourself' attitude is all the information to make a new thread is there, just needed presentation, something tech geeks aren't well known for.
There should always be a need to root. Average use case for a phone, having security is important since you store a lot of sensitive information. If phones came rooted or came so rooting was extremely easy imagine how many people would loose their bank account info or their contact info to the not so nice side of the Internet.
Edit:
Let me use this analogy. If you wanted to change the transmission in you car would you
A) search the internet for 15 minutes and the open your hood and start disconnecting things or
B) Spend at least a few hours looking at the specifics for your car (if you've change a few transmissions before) or as long as it takes for you to feel comfortable you won't destroy your car?
If you wanted Linux on your laptop would to research the drivers, installation procedures, and distros first or just download the first one and hope you know how to install it?
All I'm saying in researching is not a bad thing, if more people did it, less would brick their phones.
Sent from my C6806_GPe using Tapatalk
Click to expand...
Click to collapse
PCs that ship with Windows serve the tech ignorant public just fine without restricting access for a common user. Developers is a whole different story when it comes to Windows but that is going off-topic.
I realize most geeks aren't comfortable with marketing and presentation issues with people like Erica Griffen (aka: Angel of Tech) being a huge exception. I don't have anywhere near her level of tech knowledge or even most members on this site but I am willing to help or even take over if needed. I just can't be of much help shortening process or making it more comfortable for the public but at least I haven't been totally useless.
Any help in shortening process or partially automating things wherever and whenever geeks can feel comfortable enough is not only appreciated by me but will be by the public as well.

[Q]What is the Best Way to Root Note SGH-i717??

Hello, I was just wondering the best way to root the AT&T Samsung Note SGH-I717. I have looked up many ways but every time I scroll down to the comments I read everyone is having problems. I would just like the best and most proven way to root the phone. I use the phone with straight talk, it is an unlocked att phone, will rooting the phone affect anything with Straight Talk? I am new to rooting so please be detailed and give me links to get everything I need. Thank You so much.
zeus1911 said:
Hello, I was just wondering the best way to root the AT&T Samsung Note SGH-I717. I have looked up many ways but every time I scroll down to the comments I read everyone is having problems. I would just like the best and most proven way to root the phone. I use the phone with straight talk, it is an unlocked att phone, will rooting the phone affect anything with Straight Talk? I am new to rooting so please be detailed and give me links to get everything I need. Thank You so much.
Click to expand...
Click to collapse
so here is the deal, here are 2 methods with very subtle differences. you didn't say what your phone was running now, so here are my suggestions.......
READ, READ, READ
I know you are new here, and I was once too. I went through all of this and was very nervous about the process. (no real reason to be)
I spent a good 2 weeks reading so I would feel confident about what I was doing. I would read through these and figure which is better for you or which you feel more confident in using. they would both work fine depending on your situation or what you phone is running. because these threads are older, you may run into an issue as to where the download files are not active anymore. that is where a recent Google search could come into play. you say you have read the comments for different methods have had negative results. problem is you don't know whether that person followed the directions correctly or whether they were just in a hurry and missed something.
that's why I posted both these threads. compare to what you have read. I have a habit of going to the back of the threads and read forward. this tells me what the most recent problems may have been and if there is a solution. though the files may or may not be active, you can always get the file. its the PROCESS which is correct. compare them.
as I said........... READ, READ, READ
it puts you in the situation to help yourself first
take your time, do as the process suggests. I even rehearsed it several times. due to my lack of experience, I wanted to be as prepared as possible in case something went wrong.
http://forum.xda-developers.com/showthread.php?t=1504218
http://forum.xda-developers.com/showthread.php?t=1518962
both of these threads are from very reputable members of the community. as all threads will suggest......they are NOT responsible for what you do. make sure you are ready. watch Youtube tutorals, compare processes, have your files loaded and where you have easy access, read and rehearse.
take your time
whatever you need to do to feel confident. if something goes wrong....KNOW what you are going to do next. if you don't know where you went wrong in process or deviated from it, then others cant help.
good luck and I hope I have helped
edit.......
just saw this...this is at the back of Da G 's thread. suggested by AGOATTAMER. he is the man when it comes to having old links to process. this IS the one I used, that I couldn't find.
http://rootgalaxynote.com/galaxy-no...y-note-sgh-i717-icsgingerbreadeasiest-method/
Thanl You Very Much. I am running 4.1.2 jelllybean.
Sent from my SAMSUNG-SGH-I717 using XDA Free mobile app

Need Help Getting Back to Stock Sense

Sooo, Ill start off by saying that I've unlocked, hacked, rooted, jailbroke pretty much every phone since it became available over the years. Im a careless tinkerer and have always stumbled across well written how to's to do everything I've need in forums like this and have great luck.
Well awhile ago, shortly after I got my AT&T M8, I decided to try and turn it into Google Play Edition. Somewhere along the way while in the process of doing S-OFF, something went wrong. I kept getting errors and couldn't get anything to flash. So I gave up and got the LG G3 and put the M8 aside for a bit. Well now I want to use it again, and along the way of "tinkering", I've managed to wipe TWRP, relocked the bootloader, have no OS and still S-OFF. I can boot into recovery or boot to the HTC screen so its not completely gone yet from what Ive researched.
Would anyone be willing to help me out in getting this thing back to stock Sense or point me in the right direction? I want it completely stock, without root or custom recovery. I'd rather a good step by step, if someone would be willing. I can't seem to piece together all of the information i need to do this myself. Thanks!
Have you tried this. http://forum.xda-developers.com/showthread.php?p=55094112
StupidN00b said:
Im a careless tinkerer and have always stumbled across well written how to's to do everything I've need in forums like this and have great luck.
Click to expand...
Click to collapse
Just RUU as suggested in the previous response.
I suggest leaving your phones stock, unless you are willing to put in the time to read, research, and obtain some real knowledge.
Step-by-step guides and toolkits are dangerous things. As you see, they just get you into trouble without giving you the knowledge or tools to get out of that jam.
I'm surprised you've modded as many phones as you say, and haven't gotten any real knowledge to this point. Either you are very humble; or your story is a testament to the fact that such step-by-step guides shouldn't be posted in the first place.
redpoint73 said:
Just RUU as suggested in the previous response.
I suggest leaving your phones stock, unless you are willing to put in the time to read, research, and obtain some real knowledge.
Step-by-step guides and toolkits are dangerous things. As you see, they just get you into trouble without giving you the knowledge or tools to get out of that jam.
I'm surprised you've modded as many phones as you say, and haven't gotten any real knowledge to this point. Either you are very humble; or your story is a testament to the fact that such step-by-step guides shouldn't be posted in the first place.
Click to expand...
Click to collapse
Thank you for your response but unfortunately I find it extremely arrogant and asinine. The fact is that I have put in a lot of time and knowledge to understand what I am doing. I may not have a conventional degree in coding as you might but I am able to successfully mod my phones by browsing forums like this where you can find an abundance of knowledge, especially step-by-step guides, as you are so against. If you are so against step by step guides then maybe you can be the voice about banning them from this forum. Do you see how I am a new member? I am one of the few that actually search the forums instead of posting another thread asking the same questions. Ive used tools and information from this site for a very long time without having to post one single thing until a few days ago. And this is the response I get? I was even humble enough in my screen name to call myself stupid because, with this specific issue, I knew it had to be something stupid that i was missing. You shouldn't tell people that step by step guides are dangerous things. All it takes is some balls and some command lines and you can accomplish many things. Have I messed up my phones and others before? Yes, but i had never run into a situation I haven't been able to get myself out of. To me, tinkering around, as a hobby, is fun. Like now, as I watch Sunday NFL Countdown, I am about to dust off my Nexus 5 and flash Lollipop on it. Guess what I am going to use? A STEP BY STEP GUIDE!!!! If I mess it up, then Im sure I wouldn't be the first to do so and Im sure Ill find a solution on great forums like this. Besides, my rooted/unlocked OnePlus One is my main phone. I wanted to play around with the M8 again to see if I would miss the smaller screen but I don't. So, thank you for just repeating the first response then proceeding to insult me because you think i don't have the skills needed to mod my devices. I will continue to do so however I please, just as many others will. Either contribute to threads or ignore them. No need for the insults. You've also insulted many other members who have posted tools and step by step guides on this specific site.
nuwayman said:
Have you tried this. http://forum.xda-developers.com/showthread.php?p=55094112
Click to expand...
Click to collapse
I actually did RUU but it ended up that I had a corrupt RUU file. I redownloaded it and put it on the MicroSD card and it worked like a charm. Thank you for your quick response.
StupidN00b said:
Thank you for your response but unfortunately I find it extremely arrogant and asinine.
So, thank you for just repeating the first response then proceeding to insult me
Click to expand...
Click to collapse
Quite frankly, incorrect on both points. You don't understand what an insult is, and there is nothing insulting in my post. If you read my post carefully, you will see there is no actual personal attack or insults.
redpoint73 said:
Just RUU as suggested in the previous response.
Click to expand...
Click to collapse
Contrary to what you suggest, backing up the previous suggestion is added value; as it adds credibility and consensus to the previous solution.
redpoint73 said:
I suggest leaving your phones stock, unless you are willing to put in the time to read, research, and obtain some real knowledge.
Click to expand...
Click to collapse
Its just a suggestion, and note that its conditional. Therefore, if you meet the latter part of the statement, the first part doesn't apply to you.
redpoint73 said:
Step-by-step guides and toolkits are dangerous things. As you see, they just get you into trouble without giving you the knowledge or tools to get out of that jam.
Click to expand...
Click to collapse
I stand by this statement. I've seen dozens dozens of instances where such tools just arm people with enough "knowledge" to get them into trouble, and don't equip them with any tools to get them out. Its then left to folks like me to even start to get these folks on the right track.
I'll step back a bit from my statement that these tools "shouldn't be posted in the first place". I'll agree that step-by-step guides and toolkits might be useful if combined with the proper research, learning and understanding. But in and of themselves, they can easily lead newcomers astray.
redpoint73 said:
I'm surprised you've modded as many phones as you say, and haven't gotten any real knowledge to this point. Either you are very humble; or your story is a testament to the fact that such step-by-step guides shouldn't be posted in the first place.
Click to expand...
Click to collapse
I already gave you the benefit of the doubt here, but you chose to react defensively and in my opinion, unreasonably.
In any case, as far as your knowledge and background, we can only go by what you've stated; and you clearly stated yourself as a "careless tinkerer" and "stumbled" upon solutions. Now in your later post you say "I have put in a lot of time and knowledge to understand what I am doing". So if you provide conflicting information as to your background, nobody can be blamed for making an incorrect assumption regarding your knowledge.

Categories

Resources