Hey people, I am slightly new to xda developers but I am an experienced rooted user. So I saw many people who are inexperienced at rooting their phones brick their phones very easily. Yes I did notice a few "how to avoid bricking your phone" threads but they are quite old. Since the new versions of updates and apps are rolling out, I thought it might be a good time to post a newer thread.
Ways to avoid bricking your device.
* When flashing a custom rom or kernel, ALWAYS use the kernel or rom that is for your device and your device only.
I realized that online it does not say anything about always flashing the custom rom or device that is for your device only. Many users are out there who brick their phones by flashing the wrong rom or kernel. ( I myself have once bricked my phone like this).
*Avoid apps that can brick your device.
Many people brick their phones like this because once you have a rooted device, you want to try out all the cool root apps. Also please people name some apps that will brick your device as well.
*** APPS THAT CAN BRICK YOUR DEVICE***
Fonts installer(root), Chain fire 3D when installed on AOS 4.0 and above, switchme when installed on a custom rom, and so on. (I have more apps I could list but I am sure people out there will post it). The basic idea is read the comments about the app and see if the app is safe. Many people just get the apps online without researching and end up bricking their phones. EDIT: Any type of font installer app that is for rooted phones only have a high chance of bricking your device. One tap root apps can give a virus to your device without knowing and have chances that it will brick. After all, it is an application that roots your device, there is always a catch. z4 root for example will give you a virus and brick your device. Rom manager *can* brick your device if you try to flash a custom recovery. For Rom manager, there are users who have successfully flashed a custom recovery and users who have bricked their phones. There is definitely a risk, so I recommend flashing a custom recovery on a safer application like goo manager. Goo manager will be safe if you READ the instruction, if you do not, you will be carrying a brick in your pocket.
*When flashing/installing or in a rooting progress be patient
When flashing or rooting be patient. Do not unplug or turn off the device when in a rooting or flashing progress because that will brick the device, and I am not talking about boot loop/soft brick. Im talking about hard brick, a black screen no sign of life brick. (Once bricked my phone like that lol).
*Research and follow instructions.
Many people tend to skip the reading and researching and do it by their feeling. Then what happens? They carry around a brick in their pocket.
Research about your phone and learn it. All I got to say for this one is, READ READ AND READ.
Anyways everyone that is all I got to say, I have more things but they are minor and someone will definitely post it. Please everyone take the time to comment your thoughts and ideas on how to avoid bricking your device. I hope many users found this helpful.
Good informative article, but .... when your phone have to brick, it will brick hehe
aamirrajpoot said:
Good informative article, but .... when your phone have to brick, it will brick hehe
Click to expand...
Click to collapse
lol
Tell us , what other apps to avoid/be careful with? Pls.
Btw this thread is good idea..
raze_da_noize said:
lol
Click to expand...
Click to collapse
Can i recover my phone from brick without any backup of old stock rom?
raze_da_noize said:
Hey people, I am slightly new to xda developers but I am an experienced rooted user. So I saw many people who are inexperienced at rooting their phones brick their phones very easily. Yes I did notice a few "how to avoid bricking your phone" threads but they are quite old. Since the new versions of updates and apps are rolling out, I thought it might be a good time to post a newer thread.
Ways to avoid bricking your device.
* When flashing a custom rom or kernel, ALWAYS use the kernel or rom that is for your device and your device only.
I realized that online it does not say anything about always flashing the custom rom or device that is for your device only. Many users are out there who brick their phones by flashing the wrong rom or kernel. ( I myself have once bricked my phone like this).
*Avoid apps that can brick your device.
Many people brick their phones like this because once you have a rooted device, you want to try out all the cool root apps. Also please people name some apps that will brick your device as well.
*** APPS THAT CAN BRICK YOUR DEVICE***
Fonts installer(root), Chain fire 3D when installed on AOS 4.0 and above, switchme when installed on a custom rom, and so on. (I have more apps I could list but I am sure people out there will post it). The basic idea is read the comments about the app and see if the app is safe. Many people just get the apps online without researching and end up bricking their phones. EDIT: Any type of font installer app that is for rooted phones only have a high chance of bricking your device. One tap root apps can give a virus to your device without knowing and have chances that it will brick. After all, it is an application that roots your device, there is always a catch. z4 root for example will give you a virus and brick your device. Rom manager *can* brick your device if you try to flash a custom recovery. For Rom manager, there are users who have successfully flashed a custom recovery and users who have bricked their phones. There is definitely a risk, so I recommend flashing a custom recovery on a safer application like goo manager. Goo manager will be safe if you READ the instruction, if you do not, you will be carrying a brick in your pocket.
*When flashing/installing or in a rooting progress be patient
When flashing or rooting be patient. Do not unplug or turn off the device when in a rooting or flashing progress because that will brick the device, and I am not talking about boot loop/soft brick. Im talking about hard brick, a black screen no sign of life brick. (Once bricked my phone like that lol).
*Research and follow instructions.
Many people tend to skip the reading and researching and do it by their feeling. Then what happens? They carry around a brick in their pocket.
Research about your phone and learn it. All I got to say for this one is, READ READ AND READ.
Anyways everyone that is all I got to say, I have more things but they are minor and someone will definitely post it. Please everyone take the time to comment your thoughts and ideas on how to avoid bricking your device. I hope many users found this helpful.
Click to expand...
Click to collapse
I bricked my poco X3 NFC by installing a recovery image by *flashify* app
p.s: i had root access and i already have TWRP, but the reason i wanted to switch to orange fox it's because i haven't access to the whole storage on TWRP recovery so i wanted to install Orange Fox to try it out, and i was too lazy to install it by PC, and i said to myself , why not installing it by the phone it self! After installing it on *Flashify* it asks to reboot, after that i got a bootloop and i don't even know if it's installed . Now the phone it's returned to the shop so it can be fixed...
But altough it's happened, i'm planning to flash more custom rom, ad try the cool Kernel s cause it's fun.
simonbigwave said:
Tell us , what other apps to avoid/be careful with? Pls.
Btw this thread is good idea..
Click to expand...
Click to collapse
Bro i bricked my poco x3 by *Flashify* app it's on google play and it bricked my phone.
Those members posted in 2016! So don't expect a reply... Flashify app hasn't been updated since 2015...be ware.
galaxys said:
Those members posted in 2016! So don't expect a reply... Flashify app hasn't been updated since 2015...be ware.
Click to expand...
Click to collapse
Didn't know that but thx for tye info
Bricking is a condition when a device is usually interrupted in an attempt to update the device. There can be 6 steps to avoid bricking
(1) custom recovery,
(2) know ADB and Fastboot commands;
(3) keep a factory image on your phone;
(4) keep a Nandroid backup on your phone;
(5) keep copies of both backups on a computer;
(6) if you can't replace your battery, know how to hard reset your phone.
Adameur said:
I bricked my poco X3 NFC by installing a recovery image by *flashify* app
p.s: i had root access and i already have TWRP, but the reason i wanted to switch to orange fox it's because i haven't access to the whole storage on TWRP recovery so i wanted to install Orange Fox to try it out, and i was too lazy to install it by PC, and i said to myself , why not installing it by the phone it self! After installing it on *Flashify* it asks to reboot, after that i got a bootloop and i don't even know if it's installed . Now the phone it's returned to the shop so it can be fixed...
But altough it's happened, i'm planning to flash more custom rom, ad try the cool Kernel s cause it's fun.
Click to expand...
Click to collapse
U gave ur phone in shop what did they said?
Honestly one of the most laughable things imo is to return your phone to the shop or any technical expert shop.
Guys what you want the shop to do for you? Factory Reset? Don't think them as a real experienced ones, they just know the basics. Any any one who have an experience of installing custom ROMs or TWRP & Rooting, is better than most of the shop repairs.
They are just experiencers for the AVERAGE people. I maybe even when I sometimes go to the shop to fix my devices, I tell the employee what to do, because they hardly know about their tools.
IF YOU DON'T WANT TO SPEND A LOT OF TIME, DON'T ROOT. Basic Logic, Root isn't for normal users and wont give you a huge advantages. Root is ONLY for fun and amusing, there are no real need of Root. So if you're too lazy to search for solution and trying many methods of solving your problem, and you just hurry to fix your device. DON'T ROOT IT.
Related
Ok, I'm ashamed to admit it.. but I'm unrooted.
I saw the sticky yesterday saying stop flashing. And it scared the hell outta me!
I don't fancy a random brick! If u ask me.. the only real issue with an unrooted phone, is the internal storage. Everything else just works.
Yeah I'd love to be tryin, and compilin my own roms. And I really wanna try cyanogenmod. But it ain't worth the randomness of the bricks were gettin.
So who is working on a way to flash the recovery? We need rw access sharpish!
I will even have a go at porting froyo, if we can get this done.
Tagged the topic as a think tank, in case people wanna collaborate.
EDIT
Ok guys... I found this...
forum.xda-developers.com/showthread.php?t=589642
It's about hacking spls. Any dev help is appreciated
-------------------------------------
Sent via the XDA Tapatalk App
philicibine said:
Ok, I'm ashamed to admit it.. but I'm unrooted.
I saw the sticky yesterday saying stop flashing. And it scared the hell outta me!
I don't fancy a random brick! If u ask me.. the only real issue with an unrooted phone, is the internal storage. Everything else just works.
Yeah I'd love to be tryin, and compilin my own roms. And I really wanna try cyanogenmod. But it ain't worth the randomness of the bricks were gettin.
So who is working on a way to flash the recovery? We need rw access sharpish!
I will even have a go at porting froyo, if we can get this done.
Tagged the topic as a think tank, in case people wanna collaborate.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
if you do everything in the tutorial, you will not brick your phone, many people have done it and just because some dont know how to use a console und dont have to be scared.
starchildx said:
if you do everything in the tutorial, you will not brick your phone, many people have done it and just because some dont know how to use a console und dont have to be scared.
Click to expand...
Click to collapse
dude, are you out of your mind????????????
what do you mean? we did not do as the tutorial???? i have flashed my phone over 20-30 times. i did the root perfectly and the brick happenned after 20-30 flashes.
there are even developers who bricked their phones. think before making such comments and better inform yourself first!!!!
starchildx said:
if you do everything in the tutorial, you will not brick your phone, many people have done it and just because some dont know how to use a console und dont have to be scared.
Click to expand...
Click to collapse
Please, stop this kind of message .... You will pay a new one to the guy who will brick it ? No ...
And you are talking of something you seems to don't know very well... Some devices have been bricked only by appliyng the 2 steps of the simple root process (without custom rom, a2SD ..) ...
if you do everything in the tutorial, you will not brick your phone, many people have done it and just because some dont know how to use a console und dont have to be scared.
Click to expand...
Click to collapse
Man, maybe you should first read and than not post such a s**t. I bricked mine, too, and i think i know what i'm doing. If you would know about what you talk you would see that the cause for the bricked desires is not yet adressed, and that it could happen to anyone who rooted the phone
philicibine said:
Ok, I'm ashamed to admit it.. but I'm unrooted.
I saw the sticky yesterday saying stop flashing. And it scared the hell outta me!
Click to expand...
Click to collapse
You are easily scared
I just dont understand why you unrooted. If you have root then you are out of harms way. The brick only occurs while flashing in recovery. If you already done that - there is absolutely no risk to brick your usb that way.
stingerpl said:
You are easily scared
I just dont understand why you unrooted. If you have root then you are out of harms way. The brick only occurs while flashing in recovery. If you already done that - there is absolutely no risk to brick your usb that way.
Click to expand...
Click to collapse
I dunno man? My usb has been playing up recently. Been rooted since r1 and now I'm having trouble getting in recovery. Get a new and wonderful message everytime!
I've just put it down to my pc being a lazy f*ck! Hahahaha!! I just keep trying 'til it decides to do what I'm telling it to. Always get there in the end, there's no way I'm "unrooting". If I brick my Desire somehow, well, then I'll just cross that bridge when I come to it.
MrBadgerMilk said:
If I brick my Desire somehow, well, then I'll just cross that bridge when I come to it.
Click to expand...
Click to collapse
Ditto!
10char
Seriously guys, i just don't know how you manage to **** up your phone. Just don't be a maverick installing any old custom rom out there, do as I did : root the phone and stick with the stock rooted rom.
I've tried quite a bunch of custom roms and their different revisions, and I still find the stock rooted one (without any of the experimental A2SD crap) is by far the most stable.
phentex said:
Seriously guys, i just don't know how you manage to f**k up your phone. Just don't be a maverick installing any old custom rom out there, do as I did : root the phone and stick with the stock rooted rom.
I've tried quite a bunch of custom roms and their different revisions, and I still find the stock rooted one (without any of the experimental A2SD crap) is by far the most stable.
Click to expand...
Click to collapse
Good for you, you rooted and found a rom you liked. Other people have different reasons for rooting, and for you to simply say 'do as you did' isn't exactly helpful or useful.
The primary reason people rooted was for the A2SD. Now to be clear, it doesn't matter one bit what ROM you flash with, there is still a fair chance you can brick the device during the flash process. There is no pattern, no particular issue and no particular rom that causes the fault to occur.
No one has yet actually found the reason for the problems. If people want to go ahead and flash their devices, then fine, but at least with threads like this and the sticky, people are made well aware of the risks and potential problems.
By the way, stop swearing on the forum. Children post and read here.
since HTC released the kernel code, I thought it would be easier to revert back to enterily stock
Re: Unrooted :( til we get a stable root. Who's working on this? [THINK TANK?]
Well,i made some roms for my desire, some didnt work and i was stuck in the bootloader,but i could fix it everytime. I Flaschen my device over 20 times.
-------------------------------------
Sent via the XDA Tapatalk App
starchildx said:
Well,i made some roms for my desire, some didnt work and i was stuck in the bootloader,but i could fix it everytime. I Flaschen my device over 20 times.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
And ? Like a lot of those who have bricked their device the 21th flash ....
Seeing as you can't flash over the SPL and radio anyway, once you are successfully rooted, it's probably impossible to get to a state of full bricking. Anything will be recoverable with a gold card and/or a RUU.
Unlike many others, I only got root because I wanted access to paid apps. AFAIK root is needed for that. So I'm running the stock rooted ROM, and the radio update, provided by Paul. I won't flash anything until a rooted 2.2 ROM is out...and who knows...maybe after 2.2 the bricking problem will be gone?
socktug said:
Good for you, you rooted and found a rom you liked. Other people have different reasons for rooting, and for you to simply say 'do as you did' isn't exactly helpful or useful.
The primary reason people rooted was for the A2SD. Now to be clear, it doesn't matter one bit what ROM you flash with, there is still a fair chance you can brick the device during the flash process. There is no pattern, no particular issue and no particular rom that causes the fault to occur.
No one has yet actually found the reason for the problems. If people want to go ahead and flash their devices, then fine, but at least with threads like this and the sticky, people are made well aware of the risks and potential problems.
By the way, stop swearing on the forum. Children post and read here.
Click to expand...
Click to collapse
There is actually a reason found if you have been reading the threads over at Modaco, When the phone hits the bootloop in the flashing process, it seems after the third boot loop, the phone stays in a constant debug mode. I did have the boot loop after one flash, but i was VERY lucky as had the back of the phone off and pulled the battery befor the third bootloop, i truely belive that has saved my bacon.......
Have flashed a fair few times using all the methords posted on the modaco and XDA forums. all worked flawlessly..... but i too have kept on stock ROM.
Wont flash Customem ROMs untill im either a developer or the spl gets fully opened.
And socktugs right watch your launguage please all
EDIT: As per Stingerpl Suggests if you notice a bootloop occuring take the battery out ASAP!!
It is generally a good idea to take your battery out on first bootloop, go to recovery and nandroid restore. Might save your USB from bricking
I still can't understand why someone would want to unroot because of this. You're already past the risky procedure.
I guess a fully function root need some info about the current root. Anyone know what exploits was used and how its been applied?
maybe the problem is exotic hardware in the pc/laptop. i'm using a standart motherboard with a intel chipset, i never had any problems with rooting or unlocking or flashing any device.
for the people that have problems under linux, what do dmesg say ?
potter1984 said:
There is actually a reason found if you have been reading the threads over at Modaco, When the phone hits the bootloop in the flashing process, it seems after the third boot loop, the phone stays in a constant debug mode. I did have the boot loop after one flash, but i was VERY lucky as had the back of the phone off and pulled the battery befor the third bootloop, i truely belive that has saved my bacon.......
Click to expand...
Click to collapse
Maybe the boot loop has something to do with it... but there are simple ways to avoid a boot loop.
I flashed my desire several times... and had bootloops occur several times. None bricked my phone.. fortunatley!
The reason i found for my boot loops, was NOT WIPING EVERYTHING!
I have read on modaco forums, that Paul's recovery does not clear the dalvik cache, when it is on a partitioned sd card. Maybe it is something to do with the rooting process (no rw access).
The only answer I found, was to re-partition the sdcard everytime. thus wiping all partitions.
So as with any rom you download... READ THE F`ING MANUAL!! its always best to do a FULL wipe. Then your getting the rom, as the developer wanted you to have it.
So not a solution, but some words of advice for noobs! And hopefully we can avoid too many more bricks!!
I will keep monitoring this thread and will update the title if / when we have any developments.
Maybe we need to pray for an engineering SPL
Hey folks,
I'm sorry this is probably a newbee question but I would like to have an answer.
I root my phone (Optimus One) and I try to back-up ROM on sd card and reeboot
and stuck at Lg logo. What to do?
Please help.
gabrielpet said:
Hey folks,
I'm sorry this is probably a newbee question but I would like to have an answer.
I root my phone (Optimus One) and I try to back-up ROM on sd card and reeboot
and stuck at Lg logo. What to do?
Please help.
Click to expand...
Click to collapse
You probably shouldn't have rooted in the first place. You should have learned and researched first.
Despite popular belief, having root does NOT in fact make you cooler.
Way too many new users are trying to root because they think it's cool or heard it's cool. Well; it's not cool to be a n00b and attempt root. You need to learn your device first.
If you don't know how to perform a Nandroid backup, or restore a previous ROM backup, flash updates, install custom ROM's, boot into Safe mode, Mount R/W, run shell commands or Terminal Emulator etc, then you should NOT root. You should browse the forums here, read and re-read everything until you know it well. Google search related topics. Exhaust all available avenues, then ask questions. After you've executed all of these options you might consider rooting and starting to tinker with your device.
If you don't even know what some of the things are that were mentioned, then you should absolutely NOT root your phone. You will likely brick or screw up your phone and then be right back here begging for help in a new thread most definately created by you out of haste or costing HTC/T-Mobile money by sending your phone back and asking for a replacement simply because you had no idea what you were doing. JMHO
#include <std_disclaimer.h>
/*
* Rooting voids your warranty.
*/
CBConsultation said:
You probably shouldn't have rooted in the first place. You should have learned and researched first.
Despite popular belief, having root does NOT in fact make you cooler.
Way too many new users are trying to root because they think it's cool or heard it's cool. Well; it's not cool to be a n00b and attempt root. You need to learn your device first.
If you don't know how to perform a Nandroid backup, or restore a previous ROM backup, flash updates, install custom ROM's, boot into Safe mode, Mount R/W, run shell commands or Terminal Emulator etc, then you should NOT root. You should browse the forums here, read and re-read everything until you know it well. Google search related topics. Exhaust all available avenues, then ask questions. After you've executed all of these options you might consider rooting and starting to tinker with your device.
If you don't even know what some of the things are that were mentioned, then you should absolutely NOT root your phone. You will likely brick or screw up your phone and then be right back here begging for help in a new thread most definately created by you out of haste or costing HTC/T-Mobile money by sending your phone back and asking for a replacement simply because you had no idea what you were doing. JMHO
#include <std_disclaimer.h>
/*
* Rooting voids your warranty.
*/
Click to expand...
Click to collapse
Couldn't have said it better. But, I jumped in myself without really testing the waters when rooting my main usage device. But, what I did was read the same steps over and over again as I went along and took my time to make sure where I was going to go next and what would go wrong if I changed my mind and didn't want to root anymore out of difficulties.
What you should do at this point, is go back on the steps that you've followed and see what you may have done wrong. The best thing you can do is go back into your recovery menu and try reflashing a stock rom to your phone in hopes of reversing what you've done. Once you've done that, read different guides to give you a sense of what's going on. Pick a guide that makes the most sense to you, perhaps even a dumbed-down guide that will take you literally STEP BY STEP and assist you in rooting. Also make sure your phone isn't a pain to root. Some devices are easier than others.
hello everyone
im in need of help of installing a new rom on my mytouch 3g 32b. im trying to install the ginger yoshi rom properly however i don't know were to start. Im pretty much lost in what is the first step to install this rom. no i don't have the phone "rooted" in fact what is this rooting mean anyways? the radio and SPL are up-to-date, can someone help me get start in this? thanks
1st root the phone that is get access to the phone's system files
2nd install custom recovery
3rd download rom file
4th flash zip from the option of custom recovery
DONT DO IT IF U WANT TO USE UR PHONE FOR SOMETIME!!! COZ AFTER USING A ROM PEOPLE FACE LOT OF PROBLEMS.. OR PROBABLY BRICK UR PHONE, IN WHICH ITS BETTER TO THROW UR PHONE OUT THE WINDOW INSTEAD OF TAKING IT TO THE VENDOR COZ U WILL VOID THE TOTAL WARRANTY.. TRY AT UR OWN RISK!
try checking other topics or search within this website. i bet you'll find answers to those questions you are looking for right now.
zeemar007 said:
DONT DO IT IF U WANT TO USE UR PHONE FOR SOMETIME!!! COZ AFTER USING A ROM PEOPLE FACE LOT OF PROBLEMS.. OR PROBABLY BRICK UR PHONE, IN WHICH ITS BETTER TO THROW UR PHONE OUT THE WINDOW INSTEAD OF TAKING IT TO THE VENDOR COZ U WILL VOID THE TOTAL WARRANTY.. TRY AT UR OWN RISK!
Click to expand...
Click to collapse
Okay, not to be rude, but this is way off. The ALL CAPS really helps though.
Rooting my phone took only a few minutes. Backing up my current rom + flashing a new one = 15 minutes, tops. Plus, I couldn't imagine being back on the stock rom. My phone runs smoother, looks better, and does more than it could out of the box.
That being said, I'm not familiar with your phone, so the rooting process could be more difficult & lengthy. There are automatic root apps, but there are manual methods as well. Auto-root methods take less time & work, but when something goes wrong, it can be difficult to troubleshoot as you're not fully aware of what's happening. Manual methods require more work, and when something goes wrong there are more solutions because you're fully aware of the state of your phone. Another plus to doing it manually - you learn something.
For the record, rooting your phone is technically gaining access to system files. This includes the apps that come preinstalled, the framework, the entire operating system. There are many benefits to rooting, however you do void your warranty. You can return your phone to it's stock, non-rooted state if you need to take it in.
Before doing anything, I would read as much as possible. Read the stickies in the forum related to your phone, read any noob guides you can find, and be certain you know what you're doing before you do it. Also know why you're rooting - don't just do it because it's something that seems "cool".
Once you've read & found a method you're comfortable with, go ahead and root. Be sure to do a backup in recovery, and if you want to save your apps + data, back that up with Titanium Backup. Then download and flash the rom in recovery.
If you need anything else or have any questions (be sure to read first!) ask here or send me a pm & I'll be glad to help out.
Good luck!
So I've been reading all these articles about rooting the Samsung Captivate and they all seem to say that rooting gives you the equivalent of admin access and basically its really useful.
What I want to know is if it is safe? I'm not really good at these things and I'm afraid that if I root it I might just screw up my phone because I don't understand what I'm doing. Also I've read that rooting your phone can sometimes render your phone unusable...is that a serious issue for the captivate?
I mainly want to just be able to have a complete backup, and be able to download apps from third party websites. (I have AT&T) I think rooting lets you do all that.
Also, I see all this talk about ROM's or something and I really don't understand what that is.
If i root my phone, will it wipe any data I have stored on my phone, like contacts and apps or something? Will I still be able to receive software updates from AT&T?
Please help...Thanks sooo much!!!
Hello there,
In first place, ROMs it's the name we usually call for the OS images that you run in your phone. You have the manufacturer ROM, with (probably) operator stuff in it. You can have a very different OS image, with different layout, more options (there are beautiful things around like CyanogenMod), etc. So, installing new ROMs sometimes is like installing a new Android OS on your phone (not exactly but something like that).
Rooting your phone doesn't clean your data, but it's always a good practice to do an application/data backup. Backup software: Titanium Backup (i use it and i really like it).
By adding an Android Recovery loader, you will have the possibility to make a nandroid backup which really allows you to keep EVERYTHING! (that happens after you root the phone, of course).
Advantages of having a rooted phone:
* removing operator applications you don't like in the standard ROM
* run 'root-only' software
* installing new ROMS
* upgrading the OS version of your phone to higher than supported by the manufacturer (some features may not work in this case)
Disadvantages:
* you may void your warranty
* you may brick your phone
* you can be messing around for a long time before having your phone stable once again (if you are curious to keep trying different ROMS, and app2sd and other add-ons)
Bricking your phone may happen if in the procedure to root your phone you need to flash it. In my case, I have a LG P500 and had the Android 2.2.2 - to root it I had to flash a 2.2 version and that was the risky part (some people say that 1 in every 4 phones get bricked in this procedure which I find very exagerated!)
So read the procedures carefully and have your phone with battery full before doing any rooting procedures. Do things calmly, follow every single step and if your get unsure of something, stop, ask, and after that move forward. You will be really happy when your phone is rooted !!
thank you!
The previous responder was a little zealous with the warnings. I have a Captivate, which is rooted and running a custom ROM (CyanogenMod 7).
First, rooting will not brick your phone. In theory, you void your warranty by doing so, but it's really easy to restore to factory state.
I don't recommend a custom ROM for someone who has basic questions like you've just asked. I'd reccommend first trying to get root, and run apps like Titanium backup, SGS Tools, etc. Be careful, research what you're doing, and make lots of backups. So long as you can enter download mode, you can flash back to factory.
Sent from my SGH-I897 using XDA Premium App
I was right where you are last August. I agree with ADT who says that you should root first and then work with apps that require root. Titanium Backup has been the most valuable for me out of all of those.
The chances of bricking your phone when you only root it is minimal. I guess it's possible, but honestly, I cannot see how. There are 2 files that are required called Bootloaders. Think of these as the AT&T screen and then the Samsung screen in a stock Captivate. If you do anything that changes/replaces these, you stand a great chance of bricking your phone. You don't do this when you root, only when you do something like try a custom ROM.
When you root your phone, you won't really notice anything different at first. However, if you look at your apps you will see a new one called Superuser. It is the app that is needed to run "rooted" apps. Also, once you root your phone, you will be able to take advantage of Amazon's market which has a free app a day.
If you decide to "unroot", it can be done rather easily, and you will lose the ability to do things like run rooted apps and Amazon apps (including any you downloaded).
I would recommend that you read as many posts about rooting as possible before you finally make the plunge. Read, read and read again. Make sure you know what you are doing before you do it and the risk of damage is minimal. I have bricked my phone many times, including the power button not working and was lucky to get it back. I learned the hard way by not knowing to read, read and read again.
Good luck!!
One other quick point. If you decide to play with custom ROMs, I recommend you stick with the ones that run Froyo, not Gingerbread. The Gingerbread ROMs are just starting to come out and I believe are not for someone just starting out. The instructions are a bit more complicated and the chance of bricking your phone are much greater.
The Froyo ROMs are much easier to install. However, as said in my last post, I'd get used to rooting your stock phone first before going that way.
stick with froyo and play with custom roms. To install custom roms just flash the custom rom in the recovery mode.
You're right guys. I mean, changing the bootloader is the risky part of the process, not the rooting itself. But the risky part is flashing a ROM (if that's needed to root the phone)...
In my case I had to downgrade my phone (LG P500) before applying root, so it was risky from the start - anyway, depending on the phone model, rooting / installling bootloader can be more or less risky...
Samsung. Couldnt he always ODIN back?
Sent from my ADR6300
Hello i'm new in here and i think this is an awesome forum
Anyway, i'm willing to root my phone but i just don't want to reach the point where my phone got Hard Brick or useless. So how long does rooted phone live? Would it only take a months? because i can read some topics in other forums that their phone got bricked. Why is that happening? Is that normal? And how to avoid soft brick or hard brick? I will not be downloading some Rooted Apps if i root my phone. I just want to use this Wifikill app, dsploit and etc. but i will not be flashing customized ROM or themes. So would it still "soft brick or hard brick" my phone?
Thanks !!!!
Rooting isn't dangerous if you're careful
Hi there, I'm not sure what you mean by "how long does a rooted phone live", but I'll try to answer as best as I can.
Rooted phones 'live' as long as a non-rooted phone, the only risk of rooting a phone is the flashing part. For todays rooting methodes it's actually hard to hardbrick a phone, espescially when you just follow the steps provided by the rooting process.
Hardbricking a phone means that you messed up the flashing soo badly that there is no way to recover the phone. I actually tried on purpose to hardbrick an old SGS3 and even when I removed the USB cable while flashing the recovery, I was still able to revive the phone.
Softbricking however is much more common, but actually quite easy to revive from. All you need to un-brick the device includes having ADB/FastBoot on your PC or access to the recovery.
This way you can allways reflash the recovery or ROM if this gets corrupted.
You'll need a custom recovery to root your phone. You can brick your device if you pick the wrong recovery, but this is easy to check. Always match up the modelnumer of your phone with the one for the recovery.
After the rom has been installed, you'll need to flash the SuperSU zip to succesfully root your device and after that, you're all set.
So, bottomline is: as long as you make sure your phone is fully charged, and your PC won't randomly shutdown (that's why I always flash from a laptop). There is no way you can mess up.
For the lifetime of your phone: If you aren't planning on overclocking, you don't have to worry about shortening the lifetime of the device.
If you're going to root, always make a backup of your data, just in case something does go wrong!
For the apps you're mentioning: Just make sure you use those apps on your own network!
Flashing
So you mean flashing is the most common reason that bricks your phone? What if i want to play games, listens to music, texting or calling, does it brick your phone(soft or hard?)? And is it possible for the unrooted phone to be brick bit by bit if you keep on flashing wrong recovery file? I hope you can answer all my questions
No it's not possible to brick your phone by playing games, music ect. Flashing (Writing another recovery or updating your ROM) is the one and only way to brick your device.
If you flash the wrong recovery image to your device, it will be bricked. It 'should' be fixable in most cases.
The question about unrooted phones... Well, you can flash an custom recovery on your phone and get it bricked that way, but there is no need to flash another recovery if you're not going to root the device afterwards.
So just to clarify, you're not going to brick your device by normal use, rooted or not. The bricking part is when you're installing the recovery and root. When you succesfully rooted your device, there is no way you can brick it, until you're going to install another ROM on your device.
The worst thing that could happen with installing another ROM is getting stuck in a bootloop, but that can be fixed by going into the recovery and reflash(or install, if you prefer that term) the ROM. Unless it's the first time you're installing a custom ROM, in that case you will be stuck in a bootloop because you'll need to wipe the data, system and cache partition before installing a ROM. This prevents getting in a bootloop after installing a new ROM
Thanks !
Ok so i think i will root my phone tomorrow Im not in a purpose of installing custom ROM or kernel. I just want to use apps like dsploit or wifikill and it needs a proper root access. So its all clear and now i understand how bricky part happen. THANKS !