Database Info

Some extremely noobish questions

my dad is going to get me a samsung captivate for my birthday next week, and I really want to get the most out of the device. I have several questions that I could not find the answers to:
1. what is the chance that loading a custom rom will brick the device? I see a ton of disclaimers on rom pages and stuff. how dangerous is this?
2. can you fix a "bricked" captivate? is it possible to flash it back to stock, or does bricked mean perminatly dead?
3. how long will it be until there is a gingerbread rom? I wanted to get the nexus s, but I have to go att. how long will I have to wait for that gingerbread tastyness?
thanks for the help.

ghost55 said:
my dad is going to get me a samsung captivate for my birthday next week, and I really want to get the most out of the device. I have several questions that I could not find the answers to:
1. what is the chance that loading a custom rom will brick the device? I see a ton of disclaimers on rom pages and stuff. how dangerous is this?
2. can you fix a "bricked" captivate? is it possible to flash it back to stock, or does bricked mean perminatly dead?
3. how long will it be until there is a gingerbread rom? I wanted to get the nexus s, but I have to go att. how long will I have to wait for that gingerbread tastyness?
thanks for the help.
Click to expand...
Click to collapse
1. There is always a chance to brick your phone even if it is .00009% it is still there.
2. Make sure you can get into download and recovery mode with the 3 button combo. As long as you can get there then you can just about always recover no matter what you do to it. Key word being almost. There are also other ways to recover, look around and I am sure you will find them.
3. That part is still up in the air. Untill we get a full port. Right now we are still waiting (well at least some of us) for an offical 2.2 update let alone a 2.3 update.
Make sure you read at least the first page in the rom thread you are gonna flash for any extra instructions

so pretty much it is unlikely that I will brick it, and even if I do, it is possible to fix?

ghost55 said:
so pretty much it is unlikely that I will brick it, and even if I do, it is possible to fix?
Click to expand...
Click to collapse
It is highly unlikely that you will brick it. Most bricks can be recovered from. The only time I have not been able to recover is when att did the OTA and it bricked my phone and I didn't know about jtag at the time so I sent back to att and it was replaced. Is it 100% umbrickable? No but i would say 99% as long as you read up first and follow the directions to a T you will be fine. I have flashed about 1500 times and nothing i could not recover from
Sent from my SAMSUNG-SGH-I897 using XDA App

thanks. I just wanted to make sure that it was fairly safe to modify, because the phone is not cheap,and it would kind of suck to brick the device 10min ito owning it.

ya I was the same way as you, kind of nervous about bricking my new phone. Just read up on all of the various rom threads. If you have a good idea what you're doing the chances of bricking should be quite small.

I agree (with all of the above) and there is an excellent how-to link to YouTube vids in the Development section (too late and heading to bed or I'd link it) that steps you through rooting and installing ROM. I've been there, done that but it's a great reference for anyone thinking about installing a custom ROM....nice to SEE someone do it to ease the fears.

TF700T and CleanROM 2.0

Update - scroll down.
First off, don't yell at me for asking these questions. I understand there are guides on xda about rooting and flashing ROMs. I'm just having a little trouble understanding which route I should take and the steps that come along with it.
I am on a TF700T (obviously), running JB with the latest update. I've never rooted or used anything other than what it came with.
I am really interested in CleanROM 2.0 and other tweaks such as browser2ram. Is it possible to a flash a ROM without voiding warranty? I understand that if the "bootloader" is unlocked, my warranty will be void. I understand that if I am rooted, I'll be able to further tweak the ROM I'm using. Does the bootloader need to be unlocked in order to gain root access?
I'm not really comfortable with following a generic guide. I'm more interested in having experienced users help me with my specific situation.
P.S. Is CleanROM 2.0 the best/fully working ROM?
I'm also open to having someone experienced guide me through the process via IM.
Update: I now understand that rooting does not require an unlock and is just for granting higher permissions. Now I am wondering if flashing a custom ROM is more effective than just rooting and tweaking. Aren't you essentially creating your own version by rooting and tweaking? I know there is a method for rooting the Infinity on ICS but will it work with JB?
Sent from my ADR6425LVW

same here..
i'm with the same issue,
after upgrading to jb, is there a way to use NVflash? downgrade maybe?
is there a safe way to install CleanRom?
if yes, what are the steps i need to do? (nothing touched except asus upgrades to jb.)

Joeful said:
Update - scroll down.
First off, don't yell at me for asking these questions. I understand there are guides on xda about rooting and flashing ROMs. I'm just having a little trouble understanding which route I should take and the steps that come along with it.
I am on a TF700T (obviously), running JB with the latest update. I've never rooted or used anything other than what it came with.
I am really interested in CleanROM 2.0 and other tweaks such as browser2ram. Is it possible to a flash a ROM without voiding warranty? I understand that if the "bootloader" is unlocked, my warranty will be void. I understand that if I am rooted, I'll be able to further tweak the ROM I'm using. Does the bootloader need to be unlocked in order to gain root access?
I'm not really comfortable with following a generic guide. I'm more interested in having experienced users help me with my specific situation.
P.S. Is CleanROM 2.0 the best/fully working ROM?
I'm also open to having someone experienced guide me through the process via IM.
Update: I now understand that rooting does not require an unlock and is just for granting higher permissions. Now I am wondering if flashing a custom ROM is more effective than just rooting and tweaking. Aren't you essentially creating your own version by rooting and tweaking? I know there is a method for rooting the Infinity on ICS but will it work with JB?
Sent from my ADR6425LVW
Click to expand...
Click to collapse
CleanROM 2 is by far the best ROM on the TF700 right now, untill official Cyanogenmod 10 is up and running at least...
Anyway to answer you question: Yes you can root your TF700 without unlocking the bootloader, but no you can't flash a custom ROM (such as CleanROM) without a custom recovery. To get this custom recovery you need to unlock your device, thereby voiding its warranty. So if you must have your warranty, the best you can do is root the device, but it won't make such a huge difference to the tablet. Also know that if you are rooted but not unlocked, and you break some part of the software, you won't be able to fix it at all. And you won't be able to unlock either. This one is probably just me, but I feel safer knowing I have a custom recovery that allows me to fix issue mysself, than I would feel if I still had warranty.... but if my drop my tablet and some hardware part of it breaks... I'm SOL. Hope this helps you.

What do you mean by "break some part of the software"? If I messed something up while rooted, couldn't I just reformat my Infinity back to square one?
I mainly wanted to root for browser2ram and some other tweaks. I love this tablet but the browsing issue is a little aggravating.
Sent from my ASUS Transformer Pad TF700T

pietpodlood said:
Also know that if you are rooted but not unlocked, and you break some part of the software, you won't be able to fix it at all.
Click to expand...
Click to collapse
You can always use the stock recovery to install the stock ROM and start over.

Joeful said:
Update: I now understand that rooting does not require an unlock and is just for granting higher permissions. Now I am wondering if flashing a custom ROM is more effective than just rooting and tweaking. Aren't you essentially creating your own version by rooting and tweaking? I know there is a method for rooting the Infinity on ICS but will it work with JB?
Sent from my ADR6425LVW
Click to expand...
Click to collapse
Well, yo uare indeed creating a custom version with tweaking and rooting for root access, but to be very frank, given your reluctance to follow even the very simple and detailed guides we have put up here, I do not think you have the skill or determination (yet) to follow through with that. A good example is your question regarding the rooting of JB -- has been asked over and over -- and there are several threads tut'ing the process.
Again, no offense meant, and I'm certainly not 'yelling at you', but I am not going to hold your hand in person when so much information is readily available that you obviously do not care to read and take in.
When you've read up a bit and undertake something and get stuck, chime in.

MartyHulskemper said:
Well, yo uare indeed creating a custom version with tweaking and rooting for root access, but to be very frank, given your reluctance to follow even the very simple and detailed guides we have put up here, I do not think you have the skill or determination (yet) to follow through with that. A good example is your question regarding the rooting of JB -- has been asked over and over -- and there are several threads tut'ing the process.
Again, no offense meant, and I'm certainly not 'yelling at you', but I am not going to hold your hand in person when so much information is readily available that you obviously do not care to read and take in.
When you've read up a bit and undertake something and get stuck, chime in.
Click to expand...
Click to collapse
If you aren't going to contribute to my thread, please don't post. Thank you.
It never surprises me when someone says "no offense" followed by something condesending and unhelpful.
Sent from my ASUS Transformer Pad TF700T

[q] rooting android

i have basic intelligence on software development and how to do simple stuff on android and on iphone... about a year ago i got this phone samsung galaxy s 4g and im thinking about finally rooting... but im affraid im going to brick my phone... anyone now the chances of that happening and if it does how to fix it? i know how to root i just need to know the chances of bricking your phone from root...

No chance. Look at guide in first link of my signature.

Follow the instructions and you'll be fine.
sent from me

There's about a 1% chance you will ever hard brick this device.....I've done a great deal of crazy things to mine and I've found it to be unbrickable.
There is a 99% chance you will atleast soft brick it atleast once in its life time,but soft bricking it just means you screwed up flashing a rom or something....but that is child's play and can be fixed easily.

Shortbus-Driver said:
There is a 99% chance you will atleast soft brick it atleast once in its life time,but soft bricking it just means you screwed up flashing a rom or something....but that is child's play and can be fixed easily.
Click to expand...
Click to collapse
Same, I've soft bricked at least 40 times.

Just don't flash roms or bootloader from another device and you should be fine. Using other phone roms and such will result in a hard brick (I had experience when I first started)
Sent from my Galaxy Nexus using xda app-developers app

Listen to everyone here. As long as you carefully follow directions you'll be fine! Rooting your phone is the easiest part I think, and probably has the least chance to brick your phone. It gets tricky when you get into flashing a custom recovery and moving to ICS and/or back to Gingerbread.

[Q] JB Stock Needs Help

Ok, I got a TF300t for christmas. I couldn't wait, powered it up, and before I even hit the forums I went ahead and applied the JB update. :crying: I know... So here I am, running stock. I'm at the most recent update as of a few days ago. I've been up and down the forum trying to figure out the root situation, and there's all sorts of instructions for different .17, .26, .29, etc. roms. 1st, which number are you looking at for that? My first guess was build number so I guess that puts me at JRO03C.US_epad-10.4.2.20-20121228 (which following the above I'm guessing would get shortened now to 2.20?)
1st Q Is the only way to currently root/TWRP this bad boy to DL the ASUS unlock apk and run it? From what I can see a LOT of people are having issues with it, and it doesn't even unlock NVFlash?! I'm used to Tegra based devices. I had a ViewSonic gTab before this. I've flashed and NVFlashed the hell out of that device so flashing itself doesn't make me uncomfortable, but the thing with that tab was as long as I could get APX, my ass was fine. I'm not so sure about the TF300t If the APK is the only way... sad panda.
2.) The APK voids the warranty right? Not a fan of that idea...what if I have a legit HW issue not caused by flashing? I'm screwed....damn. Is ANYONE working on a way to modify the bootloader without notifying ASUS? Hell, I'll even take some janky way of rerouting my IP traffic and sending back a false positive to unlock my tab.
I can't really think of a 3 right now. I had one earlier...I forgot. Normally I wouldn't post this since I know it's probably topics that have been covered, but there's SO MUCH info on this tablet and it seems to change with each release that ASUS puts out that I'm not sure which methods I can use and what exactly they will do. The gTab may have been stuck in Froyo, but the guys on TeamDRH are awesome and it was SOOOO easy to flash that thing 7 ways from Sunday. I'm really mad at ASUS's implementation....had I known that they screwed over the abilities to flash the tegra platform I'd have looked into a Sammy to at least match up better with my S3.
Any help or advice is appreciated. I'd really like to find a way to root/TWRP w/o voiding warranty. If it can't be done now does anyone at least know if it's being worked on by anyone?

NeoMatrixJR said:
Ok, I got a TF300t for christmas. I couldn't wait, powered it up, and before I even hit the forums I went ahead and applied the JB update. :crying: I know... So here I am, running stock. I'm at the most recent update as of a few days ago. I've been up and down the forum trying to figure out the root situation, and there's all sorts of instructions for different .17, .26, .29, etc. roms. 1st, which number are you looking at for that? My first guess was build number so I guess that puts me at JRO03C.US_epad-10.4.2.20-20121228 (which following the above I'm guessing would get shortened now to 2.20?)
1st Q Is the only way to currently root/TWRP this bad boy to DL the ASUS unlock apk and run it? From what I can see a LOT of people are having issues with it, and it doesn't even unlock NVFlash?! I'm used to Tegra based devices. I had a ViewSonic gTab before this. I've flashed and NVFlashed the hell out of that device so flashing itself doesn't make me uncomfortable, but the thing with that tab was as long as I could get APX, my ass was fine. I'm not so sure about the TF300t If the APK is the only way... sad panda.
Click to expand...
Click to collapse
For unlock your tablet, the only way is to use the UNLOCK TOOL V7
After, once your tablet unlocked without problem
You can just followed this guide : [ROOT/ROM] Root Stock/Deodex Firmware 10.4.2.20 (US/WW) | Insecure kernel !.
It's exactly for you.
2.) The APK voids the warranty right? Not a fan of that idea...what if I have a legit HW issue not caused by flashing? I'm screwed....damn. Is ANYONE working on a way to modify the bootloader without notifying ASUS? Hell, I'll even take some janky way of rerouting my IP traffic and sending back a false positive to unlock my tab.
Click to expand...
Click to collapse
No way by this side...If you use the Unlock tool, you loose your warranty, it's one fact
I can't really think of a 3 right now. I had one earlier...I forgot. Normally I wouldn't post this since I know it's probably topics that have been covered, but there's SO MUCH info on this tablet and it seems to change with each release that ASUS puts out that I'm not sure which methods I can use and what exactly they will do. The gTab may have been stuck in Froyo, but the guys on TeamDRH are awesome and it was SOOOO easy to flash that thing 7 ways from Sunday. I'm really mad at ASUS's implementation....had I known that they screwed over the abilities to flash the tegra platform I'd have looked into a Sammy to at least match up better with my S3.
Any help or advice is appreciated. I'd really like to find a way to root/TWRP w/o voiding warranty. If it can't be done now does anyone at least know if it's being worked on by anyone?
Click to expand...
Click to collapse
And actually and for my part the most functional as recovery is TWRP, but if you want to use CWM, no problem for use it too

How to avoid bricking your device.

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.