Related
I bought it about 3 weeks ago, and everything has been working fine on it.
However, since root voids the warranty, I'm worried if something goes wrong hardware wise after the sucessful root.
So what could break down on it?
Rooting will not break your phone, unlocking the bootloader on the Nexus S is easy. And it you need to have it serviced/repaired, just unroot. Warranty unvoided.
The only way you'll break your phone is by not reading and researching what you're doing. Before modifying or flashing anything, always make a backup and know what you're doing (and why). Read thoroughly, and if there's something in the directions that you don't understand, research until you do.
It's highly unlikely that you'll experience hardware failure and not be able to unroot before taking it in.
On the other hand, don't root just because. Know why you're doing it and what you hope to achieve. Rooting because it seems like the "cool" thing to do is dumb. I'm not suggesting that you're doing that, just making a statement.
Sent from my Evo + MIUI using Tapatalk!
Here we go again (sorry ). Nothing can go wrong... if you follow all instructions carefully and correctly. Also not purposefully or foolishly flashing or installing something which you are not supposed to. Rooting... or Android in general is not for the weak hearted. Android was made to be customized and maxed out in performance (at least to me ). If you are going to use it, make good use of it. If you are still worried, just settle with how your device is or be brave and take control of your device.
Nexus s, unbrickable phone... what are you worrying on?
Accidentally sent from my Google Nexus S using XDA Premium
Thanks, I might root it then... Not sure if I will though, since I don't know what to expect after rooting in terms of what I'll be able to do.
KaiZ51 said:
Thanks, I might root it then... Not sure if I will though, since I don't know what to expect after rooting in terms of what I'll be able to do.
Click to expand...
Click to collapse
You will be able to do anything you want . This may help a bit: http://www.addictivetips.com/mobile/top-10-reasons-to-root-your-android-phone-2/ .
melvinchng said:
Nexus s, unbrickable phone... what are you worrying on?
Accidentally sent from my Google Nexus S using XDA Premium
Click to expand...
Click to collapse
+1
and amazing
you shouldnt worry about rooting since its very easy on nexus and also its kinda unbrickable and also by rooting u aint gonna damage any hardware.but jus keep in mind the bootloader hav it unloked frst and also aftr rooting u can try custom roms...
Hi guys, after waiting all day, the courier finally dropped off my awesome S3, then I had to run to the local Optus shop to have my simcard snipped, I'm loving the phone..... But I'm not the biggest fan of touchwiz, have no need for the bloaty apps, and it seems slower than it should be considering the specs, so I'm itching to root this baby and install an AOSP or AOKP rom. But I'm still undecided whether or not I want to keep this, or sell it and get the Nexus 4, so I really really can't afford to brick this phone, it's a very expensive piece of hardware and I just got it. So realistically and honestly, how dangerous is rooting/flashing on this phone? I do have rooting and flashing experience on multiple phones, and also have bricking experience on multiple phones. From my understanding because of "Download mode" the chances of hard bricking are pretty low and getting out of a softboot is pretty easy, I've heard some things about people losing IMEI numbers, how can I avoid that?
JDogg1329 said:
Hi guys, after waiting all day, the courier finally dropped off my awesome S3, then I had to run to the local Optus shop to have my simcard snipped, I'm loving the phone..... But I'm not the biggest fan of touchwiz, have no need for the bloaty apps, and it seems slower than it should be considering the specs, so I'm itching to root this baby and install an AOSP or AOKP rom. But I'm still undecided whether or not I want to keep this, or sell it and get the Nexus 4, so I really really can't afford to brick this phone, it's a very expensive piece of hardware and I just got it. So realistically and honestly, how dangerous is rooting/flashing on this phone? I do have rooting and flashing experience on multiple phones, and also have bricking experience on multiple phones. From my understanding because of "Download mode" the chances of hard bricking are pretty low and getting out of a softboot is pretty easy, I've heard some things about people losing IMEI numbers, how can I avoid that?
Click to expand...
Click to collapse
very dangerous if you do not know what you're doing. Very simple if you take the time to read and follow instructions. I'm not a technical guy or that good with computers but I spent a lot of time reading and finally decided to take a stab at rooting. My S3 is the 4th phone i rooted.
swift2fly said:
very dangerous if you do not know what you're doing. Very simple if you take the time to read and follow instructions. I'm not a technical guy or that good with computers but I spent a lot of time reading and finally decided to take a stab at rooting. My S3 is the 4th phone i rooted.
Click to expand...
Click to collapse
I know what I'm doing in general, never rooted an S3 specifically, have rooted a Desire Z, Atrix 2, and Galaxy S. So I've been around the block a few times when it comes to rooting and flashing, I had 3 Desire Z's with bad EMMC chips, they bricked even without me flashing anything, the first one had no warranty so I had to buy another out of pocket that's why I'm so paranoid. I might just keep it stock for another week or two, do some more reading, then when I finally flash a silky smooth bloatless rom I can enjoy it even more.
JDogg1329 said:
I know what I'm doing in general, never rooted an S3 specifically, have rooted a Desire Z, Atrix 2, and Galaxy S. So I've been around the block a few times when it comes to rooting and flashing, I had 3 Desire Z's with bad EMMC chips, they bricked even without me flashing anything, the first one had no warranty so I had to buy another out of pocket that's why I'm so paranoid. I might just keep it stock for another week or two, do some more reading, then when I finally flash a silky smooth bloatless rom I can enjoy it even more.
Click to expand...
Click to collapse
in that case it's very simple. I rooted 3 S3s using the same process and all were a success. I didn't bother to wait to root my phone. My wife bought me this phone for my bday and the same day I opened the box was the same day I rooted it. I hate touchwiz and i hate bloat.
swift2fly said:
in that case it's very simple. I rooted 3 S3s using the same process and all were a success. I didn't bother to wait to root my phone. My wife bought me this phone for my bday and the same day I opened the box was the same day I rooted it. I hate touchwiz and i hate bloat.
Click to expand...
Click to collapse
What methods do you recommend since you've done it 3 times already?
JDogg1329 said:
What methods do you recommend since you've done it 3 times already?
Click to expand...
Click to collapse
CF-Root
Sent from my GT-I9300
Hally79 said:
CF-Root
Sent from my GT-I9300
Click to expand...
Click to collapse
From my reading I've gathered that there is CF-Root and then the S3 Toolkit. For CF-Root do you recommend the auto one or the latest supported cf-root.
Use the cf root if you want root+ recovery, auto root for just root
It is very straight forward to do and safe as long as you read instructions
http://forum.xda-developers.com/showthread.php?t=1695238
[03.07.2012] CF-Root 6.4 - SuperSU+CWM5.5+CWMManager
slaphead20 said:
Use the cf root if you want root+ recovery, auto root for just root
It is very straight forward to do and safe as long as you read instructions
http://forum.xda-developers.com/showthread.php?t=1695238
[03.07.2012] CF-Root 6.4 - SuperSU+CWM5.5+CWMManager
Click to expand...
Click to collapse
Cheers for the help and recommendation mate, seems like a nice and simple rooting method, it's pretty late and I need to be up early tonight so I best not do it right now and risk screwing something up due to sore eyes. If I do it tomorrow I'll update the thread with how I went .
JDogg1329 said:
What methods do you recommend since you've done it 3 times already?
Click to expand...
Click to collapse
i use mac and rooted all the phones on mac. this is the method i used:
http://galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3-on-mac-osx/
very easy.
Easiest phone to root i've ever known.
Get the toolkit. That is literally it.
Follow the on screen instructions and download a custom rom for your model.
If you fail at this then your a doughnut.
Rooting FTW
Rooting is really good and it is not dangerous in my opinion. So you should go for it.
Great. I, like a dumbass, decided to try and root my new phone without a backup plan. I have had no luck using the XDA video, and now I'm stuck with the "Please select recovery mode in Kies" screen. Kies doesn't recognize it, and I have no way to restore the stock ROM. Is my only option to wait until a stock firmware ROM is released, like it was for sprint?
Based on the information we're currently provided with, I think it'd be safe to say you're screwed for now. Why you would even try to root a device that doesn't currently have any rooting methods is beyond me. You should definitely read up before you try anything you're not sure of.
The only other option you'd have at this point is taking the phone into Verizon, showing them the screen and telling them that this is how it has looked since it came out of the box. Although it's a lie, and you bricked it out of your own neglect, the reps can't really turn you away.
Can you return it?
Sent from my SCH-I605 using xda premium
I did some research, and nobody had any negative things to say about the rooting process, especially with all the videos and forums on it. I searched for how to root the Samsung note 2, versus the model number, which is different for different carriers.
MedicMillan said:
I did some research, and nobody had any negative things to say about the rooting process, especially with all the videos and forums on it. I searched for how to root the Samsung note 2, versus the model number, which is different for different carriers.
Click to expand...
Click to collapse
Every carrier is different. You must be new here.
I am new. I have rooted phones before, but never had this problem. Would it be an option to install a custom rom like Cyanogen until there is a public release of the stock firmware?
MedicMillan said:
I am new. I have rooted phones before, but never had this problem. Would it be an option to install a custom rom like Cyanogen until there is a public release of the stock firmware?
Click to expand...
Click to collapse
You will need to wait until the boot loader is unlocked to flash a rom, only way I can think of.
MedicMillan said:
I am new. I have rooted phones before, but never had this problem. Would it be an option to install a custom rom like Cyanogen until there is a public release of the stock firmware?
Click to expand...
Click to collapse
At this point in time, you can't flash anything, you can't root, and there are no recovery images to return to stock with. You either have to wait it out, or try to exchange it at Verizon.
You can exchange, they will not know the difference
Sent from my SCH-I605 using Tapatalk 2
Just take it to Verizon play dumb and get it replaced. It's within the 14 days so it will be swapped on the spot. They wont/don't care what's wrong with it.
The suggestion of just return it to the store, they won't notice, is a really **** move and I'm not saying that in defense of Verizon. I'm saying it that it is things like that that in the end cause more harm to the end user than good. They up costs and add charges, create obscene policies, etc. It may not negatively impact you immediately, but when multiple people do this all over the country it adds up.
DaRkL3AD3R said:
The suggestion of just return it to the store, they won't notice, is a really **** move and I'm not saying that in defense of Verizon. I'm saying it that it is things like that that in the end cause more harm to the end user than good. They up costs and add charges, create obscene policies, etc. It may not negatively impact you immediately, but when multiple people do this all over the country it adds up.
Click to expand...
Click to collapse
I have to say I agree 100%. If people just used common sense, or read up a bit, situations like these could be entirely avoided.
MedicMillan said:
Great. I, like a dumbass, decided to try and root my new phone without a backup plan. I have had no luck using the XDA video, and now I'm stuck with the "Please select recovery mode in Kies" screen. Kies doesn't recognize it, and I have no way to restore the stock ROM. Is my only option to wait until a stock firmware ROM is released, like it was for sprint?
Click to expand...
Click to collapse
Check the development section. There is a leaked ODIN .tar file that you can flash. It is a prerelease, but at least you will have a functioning phone until a proper root/unlock solution is found.
bork.it.consulting said:
Check the development section. There is a leaked ODIN .tar file that you can flash. It is a prerelease, but at least you will have a functioning phone until a proper root/unlock solution is found.
Click to expand...
Click to collapse
This Odin file fails. It will not flash. Someone was trying to flash it last night with the same screen you are on.
just odin the stock image in the dev section and you will be back up and running...do not I repeat do not anybody try any root methods for the other gn2 variants!
http://samsung-updates.com/device/?id=SCH-I605
if it fails then your screwed until the latest odin image is release, which im sure wont be too long.
Nit3mare said:
I have to say I agree 100%. If people just used common sense, or read up a bit, situations like these could be entirely avoided.
Click to expand...
Click to collapse
I'm not saying that everyone should go flash happy, attempt to root without knowing what they are doing destroy their phones and take them back to Verizon then rinse and repeat the process. But there have to be a few that are a tempting to get root for everyone else there is bound to be some hard bricks. Should they be out 700, and that's kinda harsh.
Check out this link for a fixed brick....
http://forum.xda-developers.com/showthread.php?p=34862234#post34862234
mrlaigle said:
I'm not saying that everyone should go flash happy, attempt to root without knowing what they are doing destroy their phones and take them back to Verizon then rinse and repeat the process. But there have to be a few that are a tempting to get root for everyone else there is bound to be some hard bricks. Should they be out 700, and that's kinda harsh.
Click to expand...
Click to collapse
But with a little reading in the correct forum, people could avoid owning a $700 paperweight. It's really not that difficult, and any issues that arise from lack of research are due to their own ignorance. I can't feel sympathy for anyone who flashes blindly.
Nit3mare said:
But with a little reading in the correct forum, people could avoid owning a $700 paperweight. It's really not that difficult, and any issues that arise from lack of research are due to their own ignorance. I can't feel sympathy for anyone who flashes blindly.
Click to expand...
Click to collapse
I'm not disagreeing with you. If you do not know what you are doing or if this is your first time you shouldn't be attempting to root an un rooted device. But there will always be those guinea pigs...
Sent from my SCH-I605 using Tapatalk 2
This is exactly the reason why everyone else who follows commense is punished with locked bootloader.
Hey everyone,
So I'm pretty new to the weird and wonderful world of rooting and custom ROMs, and as part of my research I just wanted to learn about the most common ways to completely ruin your phone. So bring on the horror stories!
joethesupercow said:
Hey everyone,
So I'm pretty new to the weird and wonderful world of rooting and custom ROMs, and as part of my research I just wanted to learn about the most common ways to completely ruin your phone. So bring on the horror stories!
Click to expand...
Click to collapse
Don't drop it in the toilet when your texting in the washroom.
Check the pockets of the clothes you are washing.....I lost many gameboy games that way when i was a child
And dont update with low battery and dont turn off the phone during an update/flashing a rom
Be patient. Seriously. I remember the first time I was backing up in recovery I got frustrated and terrified that I messed something up after 2 minutes, and shut off the phone. Thankfully this was just during a backup, but I've heard plenty of brick stories of the "I don't think anything's happening after __ time, I'll just kill it it."
Also, READING IS FUNDAMENTAL. There are often silly nuances of your phone giving you some type of message and your left to pick a command. Often every other install sees the same message, and it isn't necessarily true that the right option looks like the right option.
Read and be patient.
Back everything up as you go. It's easy and quick and can save you loads of time and effort if something goes wrong. In my experience, when following instructions and proceeding carefully it's difficult to brick your device.
Sent from my SCH-I545 using xda app-developers app
I like to get drunk and flash stuff on the weekends though!
You know what I do when I buy a video game? If you guessed read the instructions then play the game, you're dead wrong! I jump right in and start killing stuff!
Anyways, my point is, sometimes I'll just miss a step, or not pay attention, and was wondering is it easy to get out of a jam like that? I've never worked Odin, but have some adb experience. Can I just Odin back to the stock image and restore a nandroid after I get a recovery back on it?
Sent from my Nexus 7 using Tapatalk 2
As someone may use this thread to commit warranty fraud it is being closed
Moral of the story is: Backup backup backup
Do not flash anything not specifically for your model and carrier unless VERY specific instructions are given by someone who succeeded
And on that same note READ READ READ
There are dozens of threads about "bricked" phones. It's not always clear if the OP(s) managed to recover.
Just out of curiosity. Did anyone manage to brick their phone? It seems like it's fairly difficult to do so.
if you break the ROM. use recovery, if recovery is broke, use lg recovery or flash tool, if that doesn't work then you did something wrong or hardware issues
So afaik no hard bricks
Since I own android phones, I have not hard brick any. If you hard brick an android phone, you should not own an android phone, you A. did not read instruction B. did not follow instruction C. think your smarter than the instruction by skipping it.
I thought as well that it's not that easy to brick the phone. I am comming from GNex, there were not that many threads from people asking how to recover, so I thought that maybe something is different with G2
There is a HUGE difference between hard brick and soft brick. Most people soft brick their devices and that is normally pretty easy to recover from(if you can get into recovery just restore back up, or just use the native tool from your hardware manufacturer). Most posts come from people who soft brick their devices and don't know how to recover from it. The people who hard brick normally flashed wrong kernels(from other phones) or were playing around with something they shouldn't have been playing with. I have owned a lot of phones (see my sig) and hacked every one of them(well... the ones that could be, the dumb phones didn't offer much for hacking) and have not hard bricked a single one. I have soft bricked some and some took all night to recover from but never hard bricked
joshuadjohnson22 said:
There is a HUGE difference between hard brick and soft brick. Most people soft brick their devices and that is normally pretty easy to recover from(if you can get into recovery just restore back up, or just use the native tool from your hardware manufacturer). Most posts come from people who soft brick their devices and don't know how to recover from it. The people who hard brick normally flashed wrong kernels(from other phones) or were playing around with something they shouldn't have been playing with. I have owned a lot of phones (see my sig) and hacked every one of them(well... the ones that could be, the dumb phones didn't offer much for hacking) and have not hard bricked a single one. I have soft bricked some and some took all night to recover from but never hard bricked
Click to expand...
Click to collapse
True, the only case of a legitimate hard brick where the user wasn't at fault was back in the og EVO forums where an early/beta build of TWRP may have been able to corrupt/damage the nv partition. But of course even that was fixable, just out of the op's range of abilities.
rokfor2000 said:
There are dozens of threads about "bricked" phones. It's not always clear if the OP(s) managed to recover.
Just out of curiosity. Did anyone manage to brick their phone? It seems like it's fairly difficult to do so.
Click to expand...
Click to collapse
i did...not paying attention. doing too much too fast...
http://forum.xda-developers.com/showthread.php?p=48080169#post48080169
tornamac04 said:
i did...not paying attention. doing too much too fast...
http://forum.xda-developers.com/showthread.php?p=48080169#post48080169
Click to expand...
Click to collapse
Still work in progress so hopefully you'll find the way to sort it out, before you become first hard brick case
joshuadjohnson22 said:
... The people who hard brick normally flashed wrong kernels(from other phones) or were playing around with something they shouldn't have been playing with. ...
Click to expand...
Click to collapse
Flashing kernel from another phone, not another variant of the same phone, right? Flashing D801 kernel on D802 is still recoverable? Just curious because I think, I've seen a thread where someone did it.
I have another question though. Does it mean that kernel developers are at constant risk of hard bricking their phones? Are there any other "safety" mechanisms available to them?
rokfor2000 said:
Still work in progress so hopefully you'll find the way to sort it out, before you become first hard brick case
Flashing kernel from another phone, not another variant of the same phone, right? Flashing D801 kernel on D802 is still recoverable? Just curious because I think, I've seen a thread where someone did it.
I have another question though. Does it mean that kernel developers are at constant risk of hard bricking their phones? Are there any other "safety" mechanisms available to them?
Click to expand...
Click to collapse
That really depends on the hardware of both models.. If they are the exact same you may be ok.. Just be careful when flashing and don't be the guinea pig and wait to here if there are any issues first
Sent from my LG-D800 using Tapatalk
rokfor2000 said:
Still work in progress so hopefully you'll find the way to sort it out, before you become first hard brick case
Flashing kernel from another phone, not another variant of the same phone, right? Flashing D801 kernel on D802 is still recoverable? Just curious because I think, I've seen a thread where someone did it.
I have another question though. Does it mean that kernel developers are at constant risk of hard bricking their phones? Are there any other "safety" mechanisms available to them?
Click to expand...
Click to collapse
yes I done it, just enter recovery and flash your kernel
@Fma965, my lg g2 got hard bricked pl help me
pls