Database Users

Avoid JI6 update.

From what I gather from trolling on both XDA and the Tmo forums this update is bricking phones regardless of root, voodoo, ocfl, kernel perhaps people should avoid the update pending a more in depth investigation of what exactly is going on. If gps is needed flash the JI2 files found here and that should hold you over for now. This is a worse problem than the ones that came in the captivate and the sprint galaxy s.
Sent from my SGH-T959 using XDA App

I updated manually through odin and it worked just fine. I first went back to stock and started fresh. Gps test found six birds and locked on four thats the best I ever had sitting in front of my doorstep in a heavily wooded area. It would usually find at the most two and would not lock to any. So far so good.

Only speaking for myself.... I flashed it and it's fine. I hope this isn't just a bunch of people freaking out that phone stays at the Galaxy S splash screen for a while and remove the battery or something, thereby f*cking up something. But I don't doubt you.

How to fix your phone and apply the update:http://forum.xda-developers.com/showthread.php?t=803492

My concern comes from the overwhelming amount of people that seem to have that problem I for one I'm going to play it safe and wait til a stable rom based on this release is well released.
Sent from my SGH-T959 using XDA App

Bernardos70 said:
Only speaking for myself.... I flashed it and it's fine. I hope this isn't just a bunch of people freaking out that phone stays at the Galaxy S splash screen for a while and remove the battery or something, thereby f*cking up something. But I don't doubt you.
Click to expand...
Click to collapse
It wasn't hanging on the Galaxy S splash screen. It was hanging at the Vibrant screen. The logcat clearly shows an endlessly looping segfault.
http://forum.xda-developers.com/showthread.php?p=8525623#post8525623
I have an excerpt of the log, which is similar to another user who had the same issue.
Points of commonality so far with another user who had stock + root + brick is we both disabled the boot sounds + titanium backup + rom manager.

yespinosa said:
My concern comes from the overwhelming amount of people that seem to have that problem I for one I'm going to play it safe and wait til a stable rom based on this release is well released.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Considering that the people who contribute to the XDA and T-mobile forums represent a fraction of the installed base, "overwhelming" may be an overstatement.
"Lots" of people also report successful installs.

i flashed through odin, so did my roomie, and his friend got the ota. everything went smoothly. i think that we are not hearing nearly as many people that the update went well compared to those who have had issues. we all had root, blackbar mod, mobile ap, captivate camera, and i had gps from ji5. no problems. do a nandroid and put it in a safe place then go for it.

Worked fine for me as well.

yespinosa said:
From what I gather from trolling on both XDA and the Tmo forums this update is bricking phones regardless of root, voodoo, ocfl, kernel perhaps people should avoid the update pending a more in depth investigation of what exactly is going on. If gps is needed flash the JI2 files found here and that should hold you over for now. This is a worse problem than the ones that came in the captivate and the sprint galaxy s.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
The only people who should probably avoid the JI6 OTA, are people who fail to understand they have a responsibility for their own potential grief when they mod their phones in ways T-Mobile and Samsung cannot easily account for.
Granted we should hold T-Mobile's butt to the fire if their OTA is indeed soft bricking or hard bricking bone stock unmodified phones, but I don't see any clear evidence of this at all. And it's not too surprising either, as very few people who come here have bone stock devices, and fewer still are willing to revert to bone stock simply to test.
Rather what I see are people utilizing these wonderful forums to do wonderful things to their phones without having to have developed anything remotely approaching a keen understanding of what they've actually done. It's ridiculously easy to mod these phones without having the first clue what you're doing. This leads to many mis-perceptions which easily turn into noise.
There is a level of responsibility you have to take upon yourself if you're going to participate actively in modifying your device. For some it's just easier to deny this responsibility and quest for someone to blame. That may not always be the case, but it's clearly taking place with some few people over this OTA.

Agreed. We are an incredibly tiny segment of the universe of smartphone users out there. The vast majority of people buy an iPhone or Android make calls, sync their contacts and calendar, surf the web, email and text. If you started talking about rooting or jailbreaking they'd look at you like you're insane. The people rooting and modding their phones are a tiny minority, and we assume all the risk when we do it because this is not normal and customary use of the phone. Most people use their phones stock, and people who don't are assuming the risk of things going bad.
I'm fairly convinced after the Captivate OTA fiasco that you put your phone at real risk of not being able to get successful OTAs if you flash custom ROMs or kernels. The deepest I'm willing to go is rooting and lagfixing, but even then I know I'm playing with uncertainty.

masterotaku said:
The only people who should probably avoid the JI6 OTA, are people who fail to understand they have a responsibility for their own potential grief when they mod their phones in ways T-Mobile and Samsung cannot easily account for.
Granted we should hold T-Mobile's butt to the fire if their OTA is indeed soft bricking or hard bricking bone stock unmodified phones, but I don't see any clear evidence of this at all. And it's not too surprising either, as very few people who come here have bone stock devices, and fewer still are willing to revert to bone stock simply to test.
Rather what I see are people utilizing these wonderful forums to do wonderful things to their phones without having to have developed anything remotely approaching a keen understanding of what they've actually done. It's ridiculously easy to mod these phones without having the first clue what you're doing. This leads to many mis-perceptions which easily turn into noise.
There is a level of responsibility you have to take upon yourself if you're going to participate actively in modifying your device. For some it's just easier to deny this responsibility and quest for someone to blame. That may not always be the case, but it's clearly taking place with some few people over this OTA.
Click to expand...
Click to collapse
+1 to one of the most cogent comments I have ever seen here.
One footnote about the risks for ordinary end users: If T-Mobile's OTA process bricks a stock phone, apparently the carrier's typical procedure is to replace the phone. If the phone is not stock, the customer is probably on his own for a remedy. Pottery Barn rules are real. Smarphones are not cheap, and having your phone number tied to this handheld computer (or at least the carrier) by contract makes device failure harder to cope with.

Kubernetes said:
Agreed. We are an incredibly tiny segment of the universe of smartphone users out there. The vast majority of people buy an iPhone or Android make calls, sync their contacts and calendar, surf the web, email and text. If you started talking about rooting or jailbreaking they'd look at you like you're insane. The people rooting and modding their phones are a tiny minority, and we assume all the risk when we do it because this is not normal and customary use of the phone. Most people use their phones stock, and people who don't are assuming the risk of things going bad.
I'm fairly convinced after the Captivate OTA fiasco that you put your phone at real risk of not being able to get successful OTAs if you flash custom ROMs or kernels. The deepest I'm willing to go is rooting and lagfixing, but even then I know I'm playing with uncertainty.
Click to expand...
Click to collapse
I've flashed this phone more times than I can count at this point. Soft bricked it at least a dozen times. But all that self imposed grief has got me to where I am now, where I can (hopefully) reliably recover from just about anything. I still cross my fingers every time I crank up Odin3 v1.3, but I no longer visibly sweat!
We're fortunate in that these phones are surprisingly difficult to hard brick for the most part, and that given a bit of legwork one can recover from nearly any bad scenario.

It's better to flash stock ROM and then JI6 ROM manually like me and it works for me like a charm !

d01100100 said:
It wasn't hanging on the Galaxy S splash screen. It was hanging at the Vibrant screen. The logcat clearly shows an endlessly looping segfault.
http://forum.xda-developers.com/showthread.php?p=8525623#post8525623
I have an excerpt of the log, which is similar to another user who had the same issue.
Points of commonality so far with another user who had stock + root + brick is we both disabled the boot sounds + titanium backup + rom manager.
Click to expand...
Click to collapse
Then I don't know if what I'm about to tell you or not, but I have and use Titanium Backup and ROM Manager. Odin went through smoothly. That leaves the boot sound as the culprit. Had a couple of things metamorphed as well as mobile AP and the GPS files from JI2 installed, if that helps.

Bernardos70 said:
Then I don't know if what I'm about to tell you or not, but I have and use Titanium Backup and ROM Manager. Odin went through smoothly. That leaves the boot sound as the culprit. Had a couple of things metamorphed as well as mobile AP and the GPS files from JI2 installed, if that helps.
Click to expand...
Click to collapse
Even though you installed ROM manager, have you used it to install Recovery? Did you have a current ROM backup update.zip file created on your internal sdcard?

I'm just gonna throw my 2 cents in here...i did the update over an edge network and everything was fine..I have rooted then unroot and the ocl
Sent from my SGH-T959 using XDA App

[Q] Damage By Flashing?

Hello, I'm new to the whole Android thing, but I managed to recently root my Shift, and I can attest to the addictive properties of trying out ROMS/Kernels and all that good stuff. But I was worried about the idea of all this flashing I'm doing, as in the month or so I've been rooted I've flashed about four ROMS, messed up a few times, done a good 5 or 6 Nandroid restores/backups. I was just curios to know if this is excessive, or if this could damage my phone in any way. Thanks for any help guys!
P.S., I apologize if this is either in the wrong thread, or has already been answered >_< I'm still a young'un

As far as I know by flashing a lot you can damage the relationship with your wife or g/f due to spending a lot of time doing it.. besides that I believe that the only way you can damage your phone is due to a bad flash or flashing something that wasn't exactly supported by the Shift.

I recall this discussion back when I had a TouchPro2, I don't know if it applies to the Shift as well but I assume it does. From my understanding it was determined by people far more informed than me that flashing would eventually wear out the NAND memory...but it would take more flashes than even the most fiendish flashaholic could complete in the phones lifetime to do. This is what I know from discussions of a past phone, I'm not claiming anything about the lifetime of the phone and take no responsibility if you flash 5000 ROMS tonight and your NAND burns out. lol

I think the only way you can actually brick your phone from flashing is if you flash a bad ratio from like a gsm carrier to a cdma phone. Might be wrong. Cause even if you flash a bad rom as long as you have a working recovery you can always just reflash a new rom or ruu

I think his underlying question may have to do with the fact that every NAND flash memory module has a limited number of writes in its lifetime before it can't write another bit and tell whether or not the module is in the 0 or 1 state.
This is also why data2ext/apps2ext etc anything that constantly writes information to your SD card will also degrade the lifetime of the SD card.
Basically yes, in principle the number of times you write new data to the phone's built-in memory, you shave off another write from its life. But I don't think this is significant at all. Just as a reference, I'm sure there are people with the original G1 who have flashed a countless number of times over several years and still have it working.

^^This.
If it gives you peace of mind, think about how many times a ROM chef's phone gets flashed in its lifetime and usually if the phone dies it's on account of flashing something experimental that bricks the phone (wrong radio, etc.) I've never heard of someones NAND actually burning out. I flashed my TouchPro and TouchPro2 quite literally hundreds of times if that makes you feel better.

kbrn said:
As far as I know by flashing a lot you can damage the relationship with your wife or g/f due to spending a lot of time doing it.. besides that I believe that the only way you can damage your phone is due to a bad flash or flashing something that wasn't exactly supported by the Shift.
Click to expand...
Click to collapse
THIS. Main danger.
^ Shift Faced

jesusice said:
THIS. Main danger.
^ Shift Faced
Click to expand...
Click to collapse
Agreed!
Sent from my PG06100 using XDA Premium App

Thanks for all the answers, you guys are great I really appreciate your help. You're replies have put my mind at ease seeing as my level of flashing honestly doesn't seem that excessive compared to that of a developer's.
Sent from my PG06100 using XDA App

On my HeroC I changed roms two to three times a week. When CM6 came out, it was everyday (with full wipe) thanks to the nightlies. Then aosp started releasing his stuff in IRC yada yada.
My heroc made it well over a year of that torture. My wife did as well, barely.

[Q] How to prevent bricking/messing up

Hey, I've seen many threads about people bricking their phone, and I don't wanna end up like them.
So, I want to unlock bootloader,root and flash kernel, I've read using TOOLKIT isn't the best thing to do, so I'll follow this tutorial.
My question is, what can go wrong? How to prevent anything from going wrong?
Sorry if it's a stupid question, but it's my first Android and I rather ask than be sorry, thanks in advance.

Ciclop said:
Hey, I've seen many threads about people bricking their phone, and I don't wanna end up like them.
So, I want to unlock bootloader,root and flash kernel, I've read using TOOLKIT isn't the best thing to do, so I'll follow this tutorial.
My question is, what can go wrong? How to prevent anything from going wrong?
Sorry if it's a stupid question, but it's my first Android and I rather ask than be sorry, thanks in advance.
Click to expand...
Click to collapse
Just make sure anything u do you read the thread and defiantly the op and only flash stuff that made for the N4 u should be good. Read read read and learn. I've only bricked one phone and I know what I did wrong its very hard to brick a phone so long as u don't just go flash stuff u dont know what it is.
Oh yea don't over clock your phone and run benchmarks its stupid and has fried a few also. I'm onderclocked to 1134 and I still run smooth as butta.
Sent from my Nexus 4 using Xparent Blue Tapatalk 2

Ciclop said:
Hey, I've seen many threads about people bricking their phone, and I don't wanna end up like them.
So, I want to unlock bootloader,root and flash kernel, I've read using TOOLKIT isn't the best thing to do, so I'll follow this tutorial.
My question is, what can go wrong? How to prevent anything from going wrong?
Sorry if it's a stupid question, but it's my first Android and I rather ask than be sorry, thanks in advance.
Click to expand...
Click to collapse
For a REAL hard brick on a Nexus device, you really have to do something wrong. Like I did with my Nexus S .
A real hard brick, one that isn't even repairable with a JTAG brick repair service, it never happens with a Nexus device. Well, ALMOST never. I made it happen. I don't even know what I did wrong, but apparently I screwed up the radio. Even the best of the best (Adam Outler) wasn't able to repair it. It happened the day after I installed a new ROM and a mod. The battery drained really fast. After it was dead, I plugged it in the charger, booted up my phone, started the browser, and BAM. Dead. Forever.
But I wouldn't worry about those things. Just don't do too much overclocking, because there are ways to screw up the hardware inside. Almost all bricks are fixable. If you can access fastboot mode you're okay. If you can't, there are still ways to fix it, but it might cost you some money. I don't know if Adam Outler's Unbrickable Resurrector tool works with the N4, but that's also an option if you think you really screwed up.

1) Make sure that you never flash a file that wasn't designed for the Nexus 4 (MAKO)
2) Make sure that you don't have empty batteries when you flash. 50% would be a safe minimum (though I personally frequently flash with much less than that)
3) Flashing radios / bootloaders is traditionally amongt the most dangerous operations that you can do. Make sure to check MD5 on all radios (you can check on every file if you want to be super careful)
Note: the reality is that with a nexus device, it's almost impossible to brick your device. Even if you do all of the things above wrong, you'r probably still safe. BUT, you were looking for advise--so follow those three points and you should be fine.

OP, read the link in my signature about toolkits and it will answer your question.
Sent from my Nexus 4 using xda premium

Thank you all for quick replies!
I only plan on flashing Franco's/Faux's kernel, hopefully everything will go well

unlocking the BL on a nexus is very easy. I am not sure if you need a toolkit for that.
but yeah use one if you feel more comfortable with it.
also as of now do not overclock the processor as that has been causing some bricks AFAIK.

Androyed said:
For a REAL hard brick on a Nexus device, you really have to do something wrong. Like I did with my Nexus S .
A real hard brick, one that isn't even repairable with a JTAG brick repair service, it never happens with a Nexus device. Well, ALMOST never. I made it happen. I don't even know what I did wrong, but apparently I screwed up the radio. Even the best of the best (Adam Outler) wasn't able to repair it. It happened the day after I installed a new ROM and a mod. The battery drained really fast. After it was dead, I plugged it in the charger, booted up my phone, started the browser, and BAM. Dead. Forever.
But I wouldn't worry about those things. Just don't do too much overclocking, because there are ways to screw up the hardware inside. Almost all bricks are fixable. If you can access fastboot mode you're okay. If you can't, there are still ways to fix it, but it might cost you some money. I don't know if Adam Outler's Unbrickable Resurrector tool works with the N4, but that's also an option if you think you really screwed up.
Click to expand...
Click to collapse
My N4 its bricked, I contact Google for RMA. Now, my history...
N4 bought 13/nov.
-Rooted with Nexus 4 Toolkit
- ROMS installed: 1- Stock (default) 2- Minco 3- Xylon (when i got bricked)
- Kernels:1- Stock (default) 2- Franco 3- Faux (when i got bricked)
In kernel Ops: (Last Faux beta kernel)
- Underclock: (YES, READ, UNDER): 1mgz at max
- Undervolt: -137 mv all freqs
- GPU Downgraded to 200mhz
- Screen settings changed
- Hapatic feedback downgraded to 50%
That was my config. Now comes the drama...
My phone was perfectly OK at less for 2 days with that kernel and ROM combination (because i've updated few days before got bricked) So, my phone even with the downgrade config was so smoth and everything was perfectly ok.... the night of new year, when I was taking a shower, my N4 was charging SO SLOW, i dont give a f*ck and continue my night so normal, then I went out to my gf house, i have like 30 % and decide to charge again, starts charging slow again, now im worried about it so i decide to restart the phone, and problem still there... but now the device was overheating so much and the phone got discharged because i got to go, when I come to my house in the morning, i put the charger, the only thing it do is blink red led, nothing else.
Conclusion:
When your phone got bricked doesn't mean you have the guilty, because mine was STABLE for at least 2 days, for my, it was an hardware prob.
Now, the only way, RMA.
So if I was you, I lock my bootloader again.

Why are there so many bricked topics here?

It seems everyday someone bricks their phone and pleads for help, never seen anything like this with all the previous phones i had. Been here with my g2 only a month and its almost comical to read who will brick their phone next.

peachpuff said:
It seems everyday someone bricks their phone and pleads for help, never seen anything like this with all the previous phones i had. Been here with my g2 only a month and its almost comical to read who will brick their phone next.
Click to expand...
Click to collapse
Yeah, it seems they are a bit easy to brick. I've unbricked mine, luckily (took about 8 hours of research and complete repartitioning to do it, too), though now, contrary to my memory of the phone before, it's possibly running hotter. Any ideas what might cause that?

Because people are too lazy to read...90% of the problem...only a few are due to rom error/bad flash...i have never in the year+ i have had my g2 had anything that i couldn't fix in recovery...i also refuse to flash these "frankenstein" roms that are missing elements and require that you hold your tongue in perfect position when flashing...read as much info as given and you should be fine

peachpuff said:
It seems everyday someone bricks their phone and pleads for help, never seen anything like this with all the previous phones i had. Been here with my g2 only a month and its almost comical to read who will brick their phone next.
Click to expand...
Click to collapse
Most of the users who have bricked their devices have between 0 and 9 posts. This fact alone says a lot.
And like James said, they don't read a thread fully or research enough before modifying their partitions.
They came to XDA for a "QUICK FIX" on Rooting or Flashing a Custom ROM, and don't bother thinking about what they're doing.

Probably we need a great threads clean, because a lot of that 'omg I bricked my phone' deliver to nothing.
_____________________________________Read more write less and be smart

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.