Database Users

I think she bricked?

I was attempting to flash 2.x using behnaam and lox's rom.
Rom: http://forum.xda-developers.com/showthread.php?t=592596
Here is the HBoot info previous to my tinkering:
HERC XC
HBOOT-1.41.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-1.04.01.09.21
SEP 1 2009,19:18:45
Phone is rooted using adb.
I used unlockr's guide to flash a custom recovery image onto my CDMA hero and that worked fine, here is the guide I followed:
http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
I first moved the radio recommended for the rom by the dev to root on the sd and renamed it update.zip. After, I used the recovery image to wipe, then apply update.zip from sdcard. It seemed to flash fine, as it said please select reboot to complete, which I did, and it completed and rebooted the phone.
Once rebooted it gave me the android installing software image without anything else for a while, then turned off. I cannot seem to awaken my phone with any combo of keys or by plugging it into its use cable. The charging led doesn't even light up anymore.
Well I seem at the moment to be SOL, unless someone can come by and throw me a bone. I really am at a loss as to what I did wrong, as I have always read to do radio first. Not to mention as I watched it install radio it said it was installing radio.
Thanks for the help everyone.

You attempted to flash a GSM ROM to your CDMA phone, this is why your phone is bricked. I'm not sure if its possible to recover, people with more experience than I have can help you there. The problem was flashing a GSM ROM to CDMA. You are not the first to have done it, we all mess up from time to time.

Uuuh Umm...that software was for the GSM hero's NOT THE CDMA Hero.............bless your heart.

Ah **** I thought it was CDMA, guess it was a bad idea jumping into roms while still a noob.
Yea I only got the radio installed, not the rom, although that probably doesn't make a difference.

I don't think the phone can be recovered once you attempt to flash the Radio, but I could be wrong.

Hmm well if worst comes to worst I'm going with what I read on another thread and saying that I was installing the update that it found when I went to phone details and halfway through the update the phone just turned off and won't turn on anymore.
According to the other thread once it is bricked beyond belief and you play stupid they can't prove you wrong.
Best case scenario they replace it, and I won't feel bad seeing as it was a defective phone that is allowing dust to enter under the screen. But that who ordeal is an entirely different rant...lol
Sigh

ftp://xda:[email protected]_Hero_C_Sprint_1.29.651.1_signed_release.exe
Go......Now......Move with haste...

gu1dry said:
I don't think the phone can be recovered once you attempt to flash the Radio, but I could be wrong.
Click to expand...
Click to collapse
Yea, you're right. Flashing a GSM rom on the CDMA won't really break much. It's flashing the radio that bricked it.

flipzmode said:
Yea, you're right. Flashing a GSM rom on the CDMA won't really break much. It's flashing the radio that bricked it.
Click to expand...
Click to collapse
All is lost!!!!

Yep RUU brought back Error 170 cannot connect to phone.
Maybe the sprint repair stores will not be so asshole-esque this time around.
I'm hopeful though, as I have read a few posts about them exchanging it for a new one. Which after a bunch of calls I had hoped to have happen due to the dust thing, but oh well.
Maybe I will get lucky and my brick will actually turn out to be a phoenix in disguise.

unfortunately, flashing the GSM radio on pretty much destroys the phone.
i think its got something to do with the voltage and electricity used by the GSM radios. probably higher than what the CDMA radios use, so you didn't really brick your phone, you 'fried' it in a sense.
sorry bout that... but if you have the equipment protection plan you can probably get it replaced real easily, since the sprint people probably won't really understand what's wrong.

again I am reminded why I dont screw with radios

willowmp said:
Yep RUU brought back Error 170 cannot connect to phone.
Maybe the sprint repair stores will not be so asshole-esque this time around.
I'm hopeful though, as I have read a few posts about them exchanging it for a new one. Which after a bunch of calls I had hoped to have happen due to the dust thing, but oh well.
Maybe I will get lucky and my brick will actually turn out to be a phoenix in disguise.
Click to expand...
Click to collapse
Once you do get it replaced and you want to put a custom ROM on it, look at the first page of this forum and you'll find sticky threads regarding four different ROMs you can put on your phone (two production release and two experimental betas).
I would suggest either MoDaCo's rom or Fresh rom. I use Fresh in mine and had no problems (although I have used MoDaCo's before and also had no issues).
Also, if you want to root the phone, there are also sticky threads that will tell you how to root your phone from Windows, Mac and Ubuntu.
Good luck.

Yep thanks everyone.
Yea I figured once no buttons would do anything and the leds wouldn't even light up for charging that it was pretty much fried. Definitely got that sinking feeling in the pit of my stomach.
I definitely should have come into this section specific to my phone and read this info instead of just doing tons of searches and getting mixed up.
Although I'm hesitant on flashing to a replacement phone if I get one, I think I will but this time make a post just to verify without a doubt. I'm sure many wouldn't mind a simple post asking if this will blow up my phone or not, lol.
Once again thought, thanks for the help. Especially to a noob that made a real noob mistake lol.
Edit: All is well, I contacted sprint chat and they confirmed I will be receiving a brand new phone when I arrive at a sprint store, and with the chat log sent to my email and printed out the repair stores cannot pull any of their gimmicks on me, they are getting a command from sprint HQ after all. This is nice, I kill my phone and I get a brand new one without dust, and this time the invisible shield goes on asap.

willowmp said:
Although I'm hesitant on flashing to a replacement phone if I get one, I think I will but this time make a post just to verify without a doubt. I'm sure many wouldn't mind a simple post asking if this will blow up my phone or not, lol.
Click to expand...
Click to collapse
Well once you are retry the flashing on your new phone, just msg me & I'll give you my contact info & I'll walk you thru it.

willowmp said:
Edit: All is well, I contacted sprint chat and they confirmed I will be receiving a brand new phone when I arrive at a sprint store, and with the chat log sent to my email and printed out the repair stores cannot pull any of their gimmicks on me, they are getting a command from sprint HQ after all. This is nice, I kill my phone and I get a brand new one without dust, and this time the invisible shield goes on asap.
Click to expand...
Click to collapse
while the attempted flash was boneheaded , this (what I quoted) was very smart. I've had them try to reverse the decision and noted on my account in the past. All ended well, but a hard copy of the convo between me and Corporate would have been nice to have.
props for a good idea.

if you don't want trouble with rooting and flashing new ROMs to your phone, try flipz's pre-kitchen. just to try it, i RUU'd my phone and re-rooted it through that app, and its simply amazing. you just sit back and watch, don't even have to do anything.

Ok so its pretty funny but whoever it was who says that once you flash for the first time its addictive, I do have to agree. I will be getting my phone tomorrow because they had to replace it and I will be flashing, although this time I will play it safe and triple check before I get click happy...lol
So what are the danger zones in flashing, like what can brick or kill your phone? I know playing with radios can kill it if the wrong one is flashed, and I know powering off or interrupting a flash will kill/brick, but what else.
I know people said firmware alone usually will not brick you.

willowmp said:
So what are the danger zones in flashing, like what can brick or kill your phone?
Click to expand...
Click to collapse
Well obviously it can brick your phone if you flash the Radio I kid, I kid
willowmp said:
I know playing with radios can kill it if the wrong one is flashed
Click to expand...
Click to collapse
With the CDMA Hero, you do not have to flash the Radio. So if your attempting to flash the Radio, you're doing it wrong.
willowmp said:
I know powering off or interrupting a flash will kill/brick, but what else.
Click to expand...
Click to collapse
Well if the custom recovery is installed (RA-heroc), if the phone looses power while flashing the firmware, you are usually still safe, because you (usually) still boot into the recovery without issues.
Like I already said, if you want I can walk you thru the entire process thru an IM client, Steam, or Skype.

Oh ok thanks, I'm actually headed up to PA for a little trip but definitely will hit you up on that offer when I get back.

Safest way to root intercept for performance

I have a virgin mobile intercept.. second one due to bricking my first one.
I was woundering what the safest way would be to root the phone. I mainly want better performance.. not really worried about anything else.
Hopefully someone could tell me what the safest and most stable kernel and recovery would be. I've been reading up a lot but still confused about what to pick out and what method to use to flash the kernel and recovery.
Thanks all.
Sent from my SPH-M910 using XDA App

It is somewhat laughable all of these wannabe phone modders who brick their phones, then run right back to the retailer where they bought the phone and cry so that they get a new one, then go right back to attempting to brick their phone again.
Hey, here's a thought ....if you brick your phone while attempting to mod it ....its yours...live with it. Don't run back to the retailer like a baby, rather, attempt to unbrick the phone yourself. Maybe then you'll learn something, because lord knows you're not learning modding, 'responsibility' (or anything else) this way.

old_dude said:
It is somewhat laughable all of these wannabe phone modders who brick their phones, then run right back to the retailer where they bought the phone and cry so that they get a new one, then go right back to attempting to brick their phone again.
Hey, here's a thought ....if you brick your phone while attempting to mod it ....its yours...live with it. Don't run back to the retailer like a baby, rather, attempt to unbrick the phone yourself. Maybe then you'll learn something, because lord knows you're not learning modding, 'responsibility' (or anything else) this way.
Click to expand...
Click to collapse
dude you need to chill out, not everybody is technologically inclined. everybody messes up at one point in time, im sure you have. so how about instead of saying stupid **** you actually try to help people....hmmmm? how about that?

Lol, he's just the forum douchbag, and of course I'm going to get a new one if I'm under warranty. Far from technologically inclined, of done a lit, just didn't take my time. There's a reason I don't use XDA, the community seems to be filled with smart ass hot heads that don't care to help. Could of at least pointed me in the right direction then sit there and call me a... baby..? Lol.. amusing at the least.
Sent from my Optimus V running CM7 @ 825mghz

I would recommend
You head over to the dev section - there are a bunch of different ways to root this phone - i personally used the data cable method for my phone and the apk for my girlfriends phone - both have resorted in perma root.
Since you have bricked this device before when attempting to mod it - i recommend you don't worry about custom rom/recovery right away - focus on getting the device rooted and removing some of the annoying bloat with a tool like Root Toolbox or Titanium Backup.
Hope that helps a little. Let me know if I can be of further use.

Search "Samsung Intercept Root sdx" and look for the one about an apk. Worked flawlessly.
Sent from my SPH-M910 using XDA App

I am not as blunt as "old_dude" but I agree completely with his point. When I bricked my first droid, which was a LG Optimus. I spent about 40 hrs at the computer fixing it. But I got it back to perfect working condition. I learned more about "Android" in those 40 hrs than I can describe. Not to mention the pride of fixing something most can't. So if you want to be any kind of Droid person fix it your self. Also alerting retailers to the fact you are trying to root your phone is pretty dumb. Even if you think they don't know, the phone you turned in has a log that lists everything you did from the moment you first turned it on!

I just cant brick my phone - WARNING ON ODIN -

Dear all,
Maybe strange.........
I just cant brick my note! Not that i want to but how? before i knew the brickbug i did:
Odin flash to a leak ICS
Rebooted in CWM And wiped Factory default.. No problem
At one time i even formatted EMMC however its called.
At this time ICS brickbug shows up in this forum and i downloaded the APK brickbug app and i seem to be vulnarable.
Today a friend comes in with a bricked note.. tellin me he was flshing from odin and it hung on first part of flash without starting. He removed phone after 30 secs.
please take notice that it can take up to 2 minutes to start flashing.
any thoughts on this story?

jeroen180 said:
Dear all,
Maybe strange.........
I just cant brick my note! Not that i want to but how? before i knew the brickbug i did:
Odin flash to a leak ICS
Rebooted in CWM And wiped Factory default.. No problem
At one time i even formatted EMMC however its called.
At this time ICS brickbug shows up in this forum and i downloaded the APK brickbug app and i seem to be vulnarable.
Today a friend comes in with a bricked note.. tellin me he was flshing from odin and it hung on first part of flash without starting. He removed phone after 30 secs.
please take notice that it can take up to 2 minutes to start flashing.
any thoughts on this story?
Click to expand...
Click to collapse
Go to the church and donate 10 euros...
You might not be so lucky next time around.
Because you didn't brick doing 1 wipe, doesn't mean that you cannot brick..
It's like getting struck by lightning, maybe you will survive the first, but it
might not save you a second time...

Well, it is a brick bug, so it is only a chance - not definitive. I have stock ICS infected with the bug, but haven't nor plan on flashing or anything like that so...

friedje said:
Go to the church and donate 10 euros...
You might not be so lucky next time around.
Because you didn't brick doing 1 wipe, doesn't mean that you cannot brick..
It's like getting struck by lightning, maybe you will survive the first, but it
might not save you a second time...
Click to expand...
Click to collapse
Back on first HTC android phone )G1) i got it bricked 3 times by flashing SPL 3 times. Anywayz Android is much better (for me) then IOS from crapple. Only HTC dreams where crap in quality since the board has been replaced 5 times due hardware failures...
Now back on business:
I know im lucky. But still .. what causes the randomness of bricking. I mean it is there or it is not? Maybe god exists. I love my note too much to brick it

jeroen180 said:
Back on first HTC android phone )G1) i got it bricked 3 times by flashing SPL 3 times. Anywayz Android is much better (for me) then IOS from crapple. Only HTC dreams where crap in quality since the board has been replaced 5 times due hardware failures...
Now back on business:
I know im lucky. But still .. what causes the randomness of bricking. I mean it is there or it is not? Maybe god exists. I love my note too much to brick it
Click to expand...
Click to collapse
It isn't random. There are just multiple conditions that need to come together to trigger it. Read the thread about it to understand better the hows and why's.

friedje said:
It isn't random. There are just multiple conditions that need to come together to trigger it. Read the thread about it to understand better the hows and why's.
Click to expand...
Click to collapse
Even if all the conditions are met there's still a good chance it won't happen. IIRC there are also versions of emmc chips that don't have the brickbug.

pboesboes said:
Even if all the conditions are met there's still a good chance it won't happen. IIRC there are also versions of emmc chips that don't have the brickbug.
Click to expand...
Click to collapse
Well the fact of having a dangerous chip is one of the conditions....
So if you don't have it then not ALL the conditions are met..
Believe me if all the conditions are met, it will brick, it"s not random.
Then, Jeroen stated that he tested with Chainfires app, and he does have the faulty chip.
Finally I haven't seen a Note in the wild yet that doesn't have a faulty chip.

I feel like the OP. Before I knew of the bug I flashed and wiped many times. But I only flash stock roms. I don't know if that helped or not.
Sent from my GT-N7000 using xda premium

Need to brick a SGT 10.1...

No, I'm not crazy! I'm actually attempting to use a home made program to see if I can unbrick it. Does anyone know how I could do this? Thanks!

Don't know sorry but it's so fun
We spend so much time to avoid that happen ...
Sent with my GT-P7500 CM10

corybantic said:
No, I'm not crazy! I'm actually attempting to use a home made program to see if I can unbrick it. Does anyone know how I could do this? Thanks!
Click to expand...
Click to collapse
Try flashing recovery in odin and disconnect it in the middle
...

Flash a rom with odin and use repartition.
This will brick your device.
Sent from my GT-P7500 using XDA Premium HD app

Flash a rom from another device works, too.

corybantic said:
No, I'm not crazy! I'm actually attempting to use a home made program to see if I can unbrick it. Does anyone know how I could do this? Thanks!
Click to expand...
Click to collapse
Well, the other ones pretty much covered your query. I want to ask what happens if your program fails? And you mean soft or hard brick?
Sent from my amazing 10.1 galaxy tab

Like all the folks before me, flashing wrong rom from other device probably would brick it... BUT to really, really brick it messing up the bootloader is always a good way to go.

Can you short it out?

Ooops,I guess I should've been clearer! I'm trying to brick it without rooting it, i.e., perhaps some code that I could input at the bootloader?

Panos_dm said:
Well, the other ones pretty much covered your query. I want to ask what happens if your program fails? And you mean soft or hard brick?
Sent from my amazing 10.1 galaxy tab
Click to expand...
Click to collapse
Well if it fails, then I guess I gotta try - or come up with - a different program. The thing is, I had two SGT 10.1, one recently went back to Best Buy after the ICS update started freezing up my internet (not tripping tho, I was able to get a raincheck for the Note 10.1! Good thing I got the Product Replacement Plan!: victory, so I have literally a spare SGT 10.1 to mess around with. I've already rooted it and flashed different roms as well as unrooted it back to factory settings. So, to be honest, I simply have a tablet for having a tablet's sake right now.
I'm actually trying to "hard" brick it. The thing is my little program works on a "soft" brick palette so it has (usually) been able to unbrick an inadvertantly bricked phone as well as the SGT 10.1. I'm trying to see if I can brick it without rooting it to see if I can resuscitate it back to working condition.

"hard"brick it means you'd have to produce an hardware faillure, You wouldn't be able to fix an hardware failure unless you change the part that failed.
IE: Your memory chip has fried, your CPU overheated FUBAR, this kinda things

Well mine is pretty screwed. Wish I knew how it happened so I can tell you, but I don't. Yesterday I watched a movie on it and put it on the table. Later when I wanted to use it, nothing happens.
If I plug it into my PC I can get it into APX mode, but thats all. The backlight doesn't even go on. On NVflash I get the rcm version = 0x4, which means I got a locked bootloader.
When on charge, also nothing happens. The camera flash just flashed about every 2 seconds. Same thing when I keep the power button held in.
I could try your app for you on mine if you want...

Terrified to Root but desperately want to

I just got my Moto X Pure Edition (THIS one) and I really want to root it and get all the things I had with my G3 and back when I had an JB'd iPhone 4s, but my experience with the G3 was terrible.
I ended up having to RMA it 4 times through my insurance because there was something I was using on the G3 that slowed it to a vista-esque pace, and despite lots of reading on this site and others I managed to brick it :silly: 4 times :silly: in 4 different ways just trying to put it back to stock. It cost me far too much money but I was stupid enough to keep trying before finally settling on stock to avoid more issues.
I love this new phone, but I know I could tweak it more to what I like and from what it looks like in Heisenberg's Guide it is fairly safe and simple as far as roots go. I feel so stupid having screwed up with the LG that I don't want to try it. I'm a CS major and I've spent so much time messing with all sorts of things I never thought it would be a problem.
So my question is, within the realm of using Xposed and a few root apps/functions (no custom ROMs or anything just because I can't afford not having a phone for a week if I ruin it again), is it relatively safe to root the X Pure and are these tools (Universal Tool, Restore to stock tool) or a manual set of steps a good bet for returning to stock and removing root? I just want to make sure if I end up over my head I can get back to stock and be happy with what is already a great phone. Sorry if I sound like a huge _____ but I'm still in school and I want to avoid further grief as best I can.

From what I've been hearing, the 808 is a tricky processor... Besides xposed and regular terminal code changes, such as screen density, you should be good. Although, if your going in and messing with code idk what to say, experienced devs are even having a tough time getting this thing to boot on their custom ROMs...

You probably shouldn't mess with your phones anymore.
Sent from my XT1575 using Tapatalk

Another thing just to keep in mind when talking people about your qualifications, saying you are getting your Computer Science degree is pretty broad. First, we don't know what year you're in and second we don't know your concentration. I have a BBA for instance. A BBA in what though? If I went applying to random jobs, or trying to network that would leave more questions than answers. What do I have a BBA in? Well mine is in Management, so yes I can do basic accounting, financing, marketing, but my concentration is being able to interpret financial data and making decisions that would benefit a company or organization. Does that make me advanced enough to be an accountant, even though we both have BBAs? Hell no! Same goes for CS. You may be getting your computer science degree, but are you majoring in Network Security, Hardware, C++, Java, Oracle, etc... There is so much information missing that just stating "I'm getting my CS degree" isn't enough for anyone to give you a solid answer, especially not knowing what year you are in. If you are a junior, then you've just barely scratched the surface of what you will be studying for the next 2 years. Just a little FYI for future sakes :thumbup:

PiousInquisitor said:
You probably shouldn't mess with your phones anymore.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Well that's helpful.

Didn't think to specify, my bad, yeah I'm just a junior and I feel like I haven't learned much in the way of things. I just want to get a few small things from xposed and others, no plans on changing anything myself

DrPhill94 said:
Well that's helpful.
Click to expand...
Click to collapse
You bricked 4 G3s. It's time to find a new hobby. I suggest one that doesn't include the destruction of expensive electronics.
Sent from my XT1575 using Tapatalk

I own Oneplus One and rooted immediately with blisspop rom. I can't use phn without root access coz almost all ma apps need root permission. Yes its risky to root a costly device but if u need it so desperately den u should definitely root it....

Again, thanks for the positive input. I bricked them following the stock flashing methods on this website, I wasn't just shooting in the dark. And out of another half dozen phones I've only ever had an issue with the G3. Can you not? I'd like to learn here, not argue.

U having plm installing recovery on ur g3???

When it comes to just simply rooting and installing xposed, I don't see how you can brick it following step by step instructions. I will say this. If you brick it and you can't figure out how to get it back to stock, Motorola has made it clear you're on your own. So there's that, but using a simple toolkit can make a worlds difference in preventing mistakes. Yes, you'll feel like an amateur, and let's be honest, you are right now, but it beats losing $400.
You also just got it and you have no idea if you have any hardware issues that many have had to RMA within the first week for. So maybe sitting on it for a week or 2 couldn't hurt to eliminate that possibility as well (Bad CPU/GPU, Speaker, Light Leakage, loose parts when shaken, excess battery drain/heat, and turbo charge randomly not working, etc.). Motorola/Lenovo were at first being lenient about replacing these even with unlocked bootloaders and even giving people a month to send these back, they are wising up and change the rules since people have been making such a big fuss about the bootloader thing, and posting about the one month holding time (now I've read recently it's 3 days?), so just be careful, that's all.

nikeman513 said:
When it comes to just simply rooting and installing xposed, I don't see how you can brick it following step by step instructions. I will say this. If you brick it and you can't figure out how to get it back to stock, Motorola has made it clear you're on your own. So there's that, but using a simple toolkit can make a worlds difference in preventing mistakes. Yes, you'll feel like an amateur, and let's be honest, you are right now, but it beats losing $400.
You also just got it and you have no idea if you have any hardware issues that many have had to RMA within the first week for. So maybe sitting on it for a week or 2 couldn't hurt to eliminate that possibility as well (Bad CPU/GPU, Speaker, Light Leakage, loose parts when shaken, excess battery drain/heat, and turbo charge randomly not working, etc.). Motorola/Lenovo were at first being lenient about replacing these even with unlocked bootloaders and even giving people a month to send these back, they are wising up and change the rules since people have been making such a big fuss about the bootloader thing, and posting about the one month holding time (now I've read recently it's 3 days?), so just be careful, that's all.
Click to expand...
Click to collapse
Sounds like a solid plan. With the G3 rooting was always easy but the only known way that I had found for the t mobile model was to use the LG flashing tool that looked a lot like the one they used in-house to restore it, and despite following a pretty straightforward guide there were 3 different errors I got right towards the end of the process that would lock the phone in a download mode state. After using TWRP to get it back to being usable I'd still be stuck with root, and trying a few other ways would screw me.
As far as using the tools, are the 2 I linked in the OP the proper ones to be using? I'll definitely hold off on it for a while to make sure nothing comes up, thanks for that info. I'm guessing the 2 year protection plan is moot if I'm stuck with no way to erase evidence of a software issue arising from root, so that's a thing to think about as well. Do you know if unlocking the bootloader voids that protection plan? I'm looking for the TOS.

PiousInquisitor said:
You probably shouldn't mess with your phones anymore.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I could not have said this any better.

Judging from the attitudes of you two it's a wonder I stopped using this forum. Thanks fellas, really shows the quality of the community here.

I have always rooted my phones from my original HTC incredible, galaxy nexus, HTC DNA, and HTC ONE M8... that being said I am very familiar with HTC and how they work and I always had the HTC RUU file ready in case of emergency but never had to use it. I'm not sure if Motorola has a RUU file or a Fastboot IMG like Nexus devices that can bring your phone back from the dead as this is my first Moto because I never wanted to deal with the encrypted bootloader on the VZW moto phones.
I honestly can say that I have been finding root less and less needed since my M8 and I dont think I will unlock or root my Pure Edition.
The reason is that there is no bloat that I cant get rid of, I see no need for a custom kernel since the newer processors are really fast, it basically runs stock android so its not bogged down by Sense or touchwiz.
I honestly can say I like the minor additions Moto has made with the Pure Edition... I have used exposed and I really dont see the use for most of its functions for more than a week before its just gimmicky.
Once updates are stopped or the Development community is way ahead of OTA updates we will still have an easy OEM process to unlock root and flash. But for now I'm sticking with what I paid for... The Moto experience

My favorite XDA line in ages, "I feel I haven't learned much in the way of things"
Sent from my XT1575 using XDA Free mobile app

If you follow step by step instruction you will be ok.... I have rooted tons of phones and bricked a couple but was able to fix them. Its a chance you take but hey if you mess up it is a excuse to get a new cell lol. But honestly your streak with rooting is bad, maybe you shouldn't try anymore.

DrPhill94 said:
Judging from the attitudes of you two it's a wonder I stopped using this forum. Thanks fellas, really shows the quality of the community here.
Click to expand...
Click to collapse
I'm sorry I offended you. Based on your history I think it a bad idea for you to mess with your phone. Not what you wanted to hear but I honestly think it's the truth. Not all computer science majors can handle phone tech. How many of your classmates have iPhones? How many of them with Android phones root?
Sent from my XT1575 using Tapatalk

jiggyb21 said:
My favorite XDA line in ages, "I feel I haven't learned much in the way of things"
Sent from my XT1575 using XDA Free mobile app
Click to expand...
Click to collapse
Come on, don't pigeon hole everyone on XDA. You had to have known you were going to receive some sarcastic replies. That's like Plaxico Burress asking what kind of gun he should buy next. The consensus here seems to be genuine. You shouldn't mess with root anymore but it's your money. Thing is, rooting is not hard and not dangerous if you follow directions closely, yet you've managed to brick several devices. I rooted my phone to install Xposed but due to battery issues I have stopped using it. Look in the Xposed thread for more info. I would say just wait, its not worth it now IMO.

IMO, the only reason to root is to install AdAway.
Can't stand Ads. But other than that, the experience that Motorola has set up for us is perfect. I won't be adding anything else like Xposed, or install a custom ROM until I get bored with my phone, which will probably be in another six months. I've set myself up with an unlocked bootloader and root for when the time comes though. But for now, I'm happy.
I gotta say that to me (sophmore in college as a Biology major, completely unrelated to compsci), it seems pretty hard to brick a phone just trying to root it. Especially with the very detailed guides that Hesisenberg has set up for us, thank that man.
You gotta decide if what you plan on doing with your root is worth it though. I spent about 1.5 hours rooting my phone, and I'm not even sure that the time was worth AdAway.