Database Develop

[Tutorial][Bell Atrix]What need to be done before Warranty Service?

[Tutorial][Bell Atrix]What need to be done before Warranty Service?
It applies all the Bell Atrix, doesn’t matter you have Orange FR 2.1.1 or UK 2.2.3 on the phone or whatever
Simple Version:
Make sure you have CWM Recovery on it(http://forum.xda-developers.com/showthread.php?t=1019143)
Download the stock system.img (http://www.multiupload.com/T6L5RS2WH1), if you have the backup by nandroid, you can skip this step
Enter CWM Recovery to restore system.img only, then do Wipe out Data&Cache, or Force Close will be with you!
Install GingerBreak to root your phone, you can download from here: http://forum.xda-developers.com/showthread.php?t=1044765
Install CMW Recovery again, but this time, choose CHARGE MODE in order to uninstall the custom recovery
Use GingerBreak to un-root the phone
Do a factory again, then you are ready to throw this phone to any Bell Retail Store for repair
Just remind that Bell will take 4~6weeks to get your phone fixed, if you need a loaner phone, it’s $25+tax, ask before borrow since some store doesn’t even have smartphone to lend…
Full Detail Version coming soon...

Thanks, good tut to have.
Stock Bell Atrix on Rogers with updated radio, Rooted, deodexed, Honeycomb theme, and frozen!

With glad root and webtop mod on stock firmware would it be ok to just return the stock web top files and unrooted for warranty?

Why wouldn't you just a sbfflash...?
Sent from my MB860 using Tapatalk

hoodlikegaza said:
Why wouldn't you just a sbfflash...?
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Because there is no Bell SBF available (to date)

scorneil said:
Because there is no Bell SBF available (to date)
Click to expand...
Click to collapse
Yes, but in your tutorial you're just removing root access and custom recovery. You're not changing the firmware from the phone back to 0.3.7 (Bell firmware) because there isn't a Bell SBF to flash (you're right about that). If one was already running 2.1.1 or 2.2.3 with root access, they could simply reflash their respective SBF's and it would produce the same results as your tutorial. Maybe I'm missing something from your guide, but as far as I understand, once you've flashed a different SBF, there is no way of getting back to official Bell. Your guide seems to be a roundabout way to get back to stock 2.1.1 or 2.2.3 for warranty purposes, while a simple reflash would produce the same results.

thegregulator said:
Yes, but in your tutorial you're just removing root access and custom recovery. You're not changing the firmware from the phone back to 0.3.7 (Bell firmware) because there isn't a Bell SBF to flash (you're right about that). If one was already running 2.1.1 or 2.2.3 with root access, they could simply reflash their respective SBF's and it would produce the same results as your tutorial. Maybe I'm missing something from your guide, but as far as I understand, once you've flashed a different SBF, there is no way of getting back to official Bell. Your guide seems to be a roundabout way to get back to stock 2.1.1 or 2.2.3 for warranty purposes, while a simple reflash would produce the same results.
Click to expand...
Click to collapse
absolutely true.
best chances for full repair is flash stock SBF 2.2.3 and then if you really wanna get technical, simply edit your prop file for cosmetic purposes.
NFHimself has this crazy way of flashing close to stock images but thats pretty much retarded as there's no point as it really doesnt mean any closer to stock than this crap and is fickle/easy to detect as it is if Motorola was looking for it.

thegregulator said:
Yes, but in your tutorial you're just removing root access and custom recovery. You're not changing the firmware from the phone back to 0.3.7 (Bell firmware) because there isn't a Bell SBF to flash (you're right about that). If one was already running 2.1.1 or 2.2.3 with root access, they could simply reflash their respective SBF's and it would produce the same results as your tutorial. Maybe I'm missing something from your guide, but as far as I understand, once you've flashed a different SBF, there is no way of getting back to official Bell. Your guide seems to be a roundabout way to get back to stock 2.1.1 or 2.2.3 for warranty purposes, while a simple reflash would produce the same results.
Click to expand...
Click to collapse
You are right, however stock system.img(from original bell firmware, not 2.1.1 or 2.2.3) already has the right prop file and bell bloatware, comparing 2.1.1 or 2.2.3, im too lazy to look for bloatware and changing by root. this seems the easiest way for me.
other than the radio version, i dont think motorola could find out this is flashed Atrix but anyway, I am still waiting for my atrix back

ks2hot4u said:
With glad root and webtop mod on stock firmware would it be ok to just return the stock web top files and unrooted for warranty?
Click to expand...
Click to collapse
better do a factory reset and unroot

I work for bell. and all I have to say about this thread is that it should be closed and deleted. I actually thought these kind of guides were frowned upon...
If the phone was working 100% before you starting screwing with it, we shouldn't have to honor your warranty. Thats why ROOTING VOIDS Warranty.
If you screw up your windows load, Best buy doesn't say, heres a new pc. They say, here's a bill for the techie. We work on commission in these stores, and i hate wasting my time with some moron who shouldnt have screwed with what he couldn't fix. /rant
Its annoying to deal with people who brick their phones, and then give bs excuses as to why its not working. I usually do my best to help people, but its better to tell us the truth and have us help, then lie through your teeth that its a problem with the device.
It costs me extra hours of work to deal with DOA phones, and it costs everyone including motorola tons of $$$ for stuff that is screwed up by the consumer.
Why can't the people who don't know what theyre doing, leave the dangerous stuff to the guys who know how to fix their own problems?
Edit: the exception to this is true hardware issues. But those don't seem to come up all too often with this phone, just battery life issues.

But thats the thing if you brick your device, this guide won't help as the phone is a brick.
As for hardware issues, this is the exact reason for this thread IMHO, something useful to me as my fingerprint reader is slightliy off physically which results in the device thinking that fast swipes are taking place when they are not. now I can use this when I am ready to take my device in without being harrassed about software.
With my N1 even with the bootloader unlocked they still took in the device if it was proven to be a hardware defect (again had a problem with my power button - just my luck i guess) Doubt bell would do the same.

binary110 said:
I work for bell. and all I have to say about this thread is that it should be closed and deleted. I actually thought these kind of guides were frowned upon...
If the phone was working 100% before you starting screwing with it, we shouldn't have to honor your warranty. Thats why ROOTING VOIDS Warranty.
If you screw up your windows load, Best buy doesn't say, heres a new pc. They say, here's a bill for the techie. We work on commission in these stores, and i hate wasting my time with some moron who shouldnt have screwed with what he couldn't fix. /rant
Its annoying to deal with people who brick their phones, and then give bs excuses as to why its not working. I usually do my best to help people, but its better to tell us the truth and have us help, then lie through your teeth that its a problem with the device.
It costs me extra hours of work to deal with DOA phones, and it costs everyone including motorola tons of $$$ for stuff that is screwed up by the consumer.
Why can't the people who don't know what theyre doing, leave the dangerous stuff to the guys who know how to fix their own problems?
Edit: the exception to this is true hardware issues. But those don't seem to come up all too often with this phone, just battery life issues.
Click to expand...
Click to collapse
who would use this for anything other than a hardware issue? anyone who can follow this guide can also follow a SBF flash instruction to solve their software issues

binary110 said:
I work for bell. and all I have to say about this thread is that it should be closed and deleted. I actually thought these kind of guides were frowned upon...
If the phone was working 100% before you starting screwing with it, we shouldn't have to honor your warranty. Thats why ROOTING VOIDS Warranty.
If you screw up your windows load, Best buy doesn't say, heres a new pc. They say, here's a bill for the techie. We work on commission in these stores, and i hate wasting my time with some moron who shouldnt have screwed with what he couldn't fix. /rant
Its annoying to deal with people who brick their phones, and then give bs excuses as to why its not working. I usually do my best to help people, but its better to tell us the truth and have us help, then lie through your teeth that its a problem with the device.
It costs me extra hours of work to deal with DOA phones, and it costs everyone including motorola tons of $$$ for stuff that is screwed up by the consumer.
Why can't the people who don't know what theyre doing, leave the dangerous stuff to the guys who know how to fix their own problems?
Edit: the exception to this is true hardware issues. But those don't seem to come up all too often with this phone, just battery life issues.
Click to expand...
Click to collapse
QFT, but......we are referring to hardware isssues here, not software.......and rooting has nothing to do with that.
Sent from my Blue Myst GladiAtrix on Bell using the XDA Premium App.

I agree, its totally cool for hardware issues, but i'm thinking about the guys who have the lower half of the touch screen not working because they screwed the software up. 9/10 issues with any smartphone is software related.

binary110 said:
I agree, its totally cool for hardware issues, but i'm thinking about the guys who have the lower half of the touch screen not working because they screwed the software up. 9/10 issues with any smartphone is software related.
Click to expand...
Click to collapse
since no one seems to be able to replicate this issue (to my knowledge) that would imply that it IS hardware related and not software

Rediculous
binary110 Your completly in the dark if you think this phone or any other smartphone wont have defects and hardware malfunctions.
My Atrix has wicked bad screen response when plugged into any power source with stock charger or other... im not returning mine as this is a minor issue. Although my roomates cant hold gps, drops calls constantly, misses calls and msgs for lack of signal and has constant reboots since stock with only root to obtain webtop mod.
So according to your logic he dosent deserve to have his 500+ $ phone replaced cuz it will cost motorola money and your lazy ass some commision ??
THIS IS THE WRONG FORUM FOR YOU !

binary110 Your completly in the dark if you think this phone or any other smartphone wont have defects and hardware malfunctions.
My Atrix has wicked bad screen response when plugged into any power source with stock charger or other... im not returning mine as this is a minor issue. Although my roomates cant hold gps, drops calls constantly, misses calls and msgs for lack of signal and has constant reboots since stock with only root to obtain webtop mod.
So according to your logic he dosent deserve to have his 500+ $ phone replaced cuz it will cost motorola money and your lazy ass some commision ??
THIS IS THE WRONG FORUM FOR YOU !
Click to expand...
Click to collapse
I never said the phone was not capable of being defective. I said that when someone brings it in for an issue that they caused themselves. The phones are more often screwed up by a customer, than they are actually defective.
90% of the charger issues are from using a charger different than the motorola one that came with the phone. Especially the ones with the screen response. I noted it on my atrix as well. I also have replaced a customers phone for this.
This IS a valid reason to replace the phone.
But this is also easily noticeable BEFORE you go through the process of rooting/modding the phone. and as such, you should take it up with the place your purchased it before modding it.
Its like buying a car, ripping the engine apart right away. only to find that it runs like crap after you've ripped it apart... You probably should have done a test drive before purchasing. Do you understand what i mean?
Furthermore, your friend has a legitimate issue, I'm talking about people who brick their phones and play stupid. As well, I can tell you're a part of the generation who feels they're entitled to everything under the sun from the carrier you deal with. Yet, no cable company fixes your damn television. And especially not if you screw it up yourself.
Its not apples to apples, in the sense that the cable company doesn't subsidize your tv. but even if you got a tv as a promotion through them, they'd send you to the manufacturer. Which is what i'd prefer to do with people who do stupid stuff and want it fixed.
Don't act like my time isnt worth money just because youre a needy consumer. What i'm saying is just man up, tell us you screwed it up, and we will do everything we can help.
For you to be trolling the way that you are, its obvious that this ISNT THE FORUM FOR YOU.
Thank you.
By the way, Watch your language on the forums.

seven2099 said:
absolutely true.
best chances for full repair is flash stock SBF 2.2.3 and then if you really wanna get technical, simply edit your prop file for cosmetic purposes.
NFHimself has this crazy way of flashing close to stock images but thats pretty much retarded as there's no point as it really doesnt mean any closer to stock than this crap and is fickle/easy to detect as it is if Motorola was looking for it.
Click to expand...
Click to collapse
Uhm, what? How did I get dragged into this PMS fest?
Ridiculous.

Be nice guys... We are all Canadian, we love peace, don't we?!
In my case, my touchscreen's digitalize is 100% broken, it's either hypersensitive or non-sensitive at all... It happened on Bell Stock rom but I was trying to flash sfb to see if it could be fixed...
Unfortunately, i got my repair back today and still the same issue, i asked the bell staff to try the touchscreen and she said the phone is not boot up properly...
Oh well, after 90s, I ask her to try again, she clicked "BACK" 10 times in order to get back, and 5 times to run Bell Self-serve
well, I really unsatisfied with the result and I had to left the phone there and waiting for another 2 weeks, AGAIN!!!
I have 3yr contract with Bell so it has to waste time and money to get my phone fixed cuz its carelessness and impatience are wasting my money and time... The $30 loaner phone sucks and cannot even been changed...
well, looks like a little away from the topic but I've just out of the store...
even according to the repair menu, the bell stock sbf has been applied on and change of the part which i know its not the digitalize, the phone is still unusable...
AT&T users are lucky since they have their own stock sbf to flash when they wanna a repair but poor Bell users they have to use those tutorials like mine to do repair, OR UNLOCK THE BOOTLOADER AND I WONT ASK FOR WARRANTY
btw, maybe that's the reason why Apple is cool, they can get your iPhone replaced in maximum 60min not 60days even there is just a dust in screen

NFHimself said:
Uhm, what? How did I get dragged into this PMS fest?
Ridiculous.
Click to expand...
Click to collapse
see what you caused?
jk
I understand where binary was coming from but again this thread isn't for that reason. At the same time I bet we can all say we wish carriers like bell and rogers were completely full of staff like you that come with the line we will do whatever we can to help. most times reps come off as just going through the motions or looking for whatever reason to close the case.

[Q] Simple Question(s)

Hey, thanks for taking the time to read this, I appreciate it. Well, let's get to it. This is my first phone a plan, all my other phones prior had been using a sim card and I had paid for it fully. This is the first time I bought a phone that I am paying off monthly on a Basic Sprint plan.
Will Rooting or Flashing my device cause any issues with my carrier or incur any extra fees. (I can't afford that atm)
Once my device is flashed/rooted will I lose connection to my account?
(Super Silly question) To Root my device will I lose all my information?
Seeing that I am content with the stock ROM, I'm just looking for the benefits of being rooted, should I go ahead and root my device?

BeNicePlz said:
Hey, thanks for taking the time to read this, I appreciate it. Well, let's get to it. This is my first phone a plan, all my other phones prior had been using a sim card and I had paid for it fully. This is the first time I bought a phone that I am paying off monthly on a Basic Sprint plan.
Will Rooting or Flashing my device cause any issues with my carrier or incur any extra fees. (I can't afford that atm)
Once my device is flashed/rooted will I lose connection to my account?
(Super Silly question) To Root my device will I lose all my information?
Seeing that I am content with the stock ROM, I'm just looking for the benefits of being rooted, should I go ahead and root my device?
Click to expand...
Click to collapse
No
You might have to have Sprint reprovision your phone.
Yes
I've had mine since launch without root, and it's honestly the first phone I've ever had where I didn't really find the need to root it. And I like fully stock phones.

eXplicit815 said:
No
You might have to have Sprint reprovision your phone.
Yes
I've had mine since launch without root, and it's honestly the first phone I've ever had where I didn't really find the need to root it. And I like fully stock phones.
Click to expand...
Click to collapse
Thanks for answering!
I have this feeling the Sprint will give me sh*t for rooting it for some reason. Like make things complicated for me.

I rooted and changed roms within 5 minutes of owning mine. Have sent 2 back now for device issues. The guy that works at sprint thought it was cool that I was doing that.
For troubleshooting reasons it would be a PITA to fix but if you know what you are doing you could take care of most stuff on your device.

Stellarex said:
I rooted and changed roms within 5 minutes of owning mine. Have sent 2 back now for device issues. The guy that works at sprint thought it was cool that I was doing that.
For troubleshooting reasons it would be a PITA to fix but if you know what you are doing you could take care of most stuff on your device.
Click to expand...
Click to collapse
Yeah, I think I'm going to keep stock for now. People usually thinks it's some big thing to flash roms and root.

BeNicePlz said:
Yeah, I think I'm going to keep stock for now. People usually thinks it's some big thing to flash roms and root.
Click to expand...
Click to collapse
I did because I was really sick of sense

If you have to send your phone to htc for any reason outside of Sprint (warranty issue), and they find out you unlocked your bootloader, they could charge you a few hundred dollars to repair or refuse to help you at all. There are ways around this, but nobody else mentioned this scenario. Just throwing it out there.

[Q] Question about buying a bricked moto x

Hi everyone, I'm planning on buying a bricked moto x because it's cheap and it's new. In the past I already bought a bricked phone and made it work, however I'm not sure I will be able to this time so I wanted to know if you guys can help me understand:
-IF it can be unbricked/fixed, I don't care if it's difficult but I need to know if it's possible first.
-if the above is possible then what procedures should I follow
I'm probably asking for too much, sorry, but from what I tried to investigate it looks like it has more than one single problem so im not sure if all of them have a solution.
What the seller said:
The old owner sold it with the bootloader unlocked, I didn't knew that, so I updated via OTA (in the phone) and ended like that.
Looks like it can't have an unlocked bootloader if OTA updating, I don't even know please help me.
*since I still don't own the phone I can't test anything, I just need to know if those errors shown above have a solution, or at least are not a death declaration so I can still try something if I buy it.
Sorry for the bad quality of the images but that's what the guy selling it uploaded.

brurhh said:
Hi everyone, I'm planning on buying a bricked moto x because it's cheap and it's new. In the past I already bought a bricked phone and made it work, however I'm not sure I will be able to this time so I wanted to know if you guys can help me understand:
-IF it can be unbricked/fixed, I don't care if it's difficult but I need to know if it's possible first.
-if the above is possible then what procedures should I follow
I'm probably asking for too much, sorry, but from what I tried to investigate it looks like it has more than one single problem so im not sure if all of them have a solution.
What the seller said:
The old owner sold it with the bootloader unlocked, I didn't knew that, so I updated via OTA (in the phone) and ended like that.
Looks like it can't have an unlocked bootloader if OTA updating, I don't even know please help me.
*since I still don't own the phone I can't test anything, I just need to know if those errors shown above have a solution, or at least are not a death declaration so I can still try something if I buy it.
Sorry for the bad quality of the images but that's what the guy selling it uploaded.
Click to expand...
Click to collapse
You'll be rolling the dice on that one. MAYBE it can be fixed using the de-bricking procedures, but if anyone tells you that it can FOR SURE be fixed...well...I'd question their source.
If its cheap enough that you don't mind throwing that amount of money down the drain....give it a shot. Your call.

brurhh said:
What the seller said:
The old owner sold it with the bootloader unlocked, I didn't knew that, so I updated via OTA (in the phone) and ended like that.
Looks like it can't have an unlocked bootloader if OTA updating, I don't even know please help me.
Click to expand...
Click to collapse
I call BS on that account of what happened... The bootloader is LOCKED STATUS 0. That device was never bootloader unlocked. (and having an unlocked bootloader doesn't interfere with taking an OTA)
It could be that someone used one of the older procedures to root and disable write protection, took and OTA (losing root/write protection) and later tried to downgrade to root & disable write protection again, thus causing the brick.
It could be as simple as flashing the latest ROM (4.4.4) using mfastboot. I could be as complex as using -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057 ... or it could just be a brick that can't be recovered.
Either way, like @samwathegreat said... its a roll of the dice. There is no way of knowing until after you buy the phone and try.

KidJoe said:
... or it could just be a brick that can't be recovered.
Either way, like @samwathegreat said... its a roll of the dice. There is no way of knowing until after you buy the phone and try.
Click to expand...
Click to collapse
I'll try, after all it's almost new, even if I need to replace something it would be cheaper than buying an used one, I'm worried about that CID stuff because I read that it has something to do with a unique file that has to be backed up and without that file there is nothing you can do to unbrick.

brurhh said:
I'll try, after all it's almost new, even if I need to replace something it would be cheaper than buying an used one, I'm worried about that CID stuff because I read that it has something to do with a unique file that has to be backed up and without that file there is nothing you can do to unbrick.
Click to expand...
Click to collapse
I'd be worried too. There's a great chance the device can't be fixed... And you're simply out X amount of dollars.
I'd pocket your money and add a bit when you can and buy a used fully working device. At least the money won't be wasted... Potentially.
For all you know he fastbooted a rom or firmware for another device entirely. If so, you're done. Paperweight. He could have brought it somewhere and already been told it's unsalvagable.
You just don't know.

KJ said:
I'd be worried too. There's a great chance the device can't be fixed... And you're simply out X amount of dollars.
I'd pocket your money and add a bit when you can and buy a used fully working device. At least the money won't be wasted... Potentially.
For all you know he fastbooted a rom or firmware for another device entirely. If so, you're done. Paperweight. He could have brought it somewhere and already been told it's unsalvagable.
You just don't know.
Click to expand...
Click to collapse
Thanks, what the seller says doesn't match with the fastboot screen thats my fear, I guess he don't know or perhaps doesn't want me to know how the phone really ended like that, this phone is amazing, I just got excited about getting it so cheap, i guess i'll wait more thanks again

brurhh said:
Thanks, what the seller says doesn't match with the fastboot screen thats my fear, I guess he don't know or perhaps doesn't want me to know how the phone really ended like that, this phone is amazing, I just got excited about getting it so cheap, i guess i'll wait more thanks again
Click to expand...
Click to collapse
I don't blame you!
There's some bricks you can recover from, and some you can't.
Your odds are the same if you just go to the casino and put your money for the phone on red or black at the roulette table. If you lose you lose... But if you win... You can buy a working phone. ?

Is it just me or is this phone a devepors dud?

So I understand that we have locked bootloader but it seems that these forums are dying. This is the first LG phone ive ever owned but it really feels dead even compared to my Galaxy note 3. It's like nobody is even trying to do anything with it and its made me quite sad. Anyone have any suggestions as to how to make this phone feel fun and different like I remember doing to my Galaxy s2 or s3? I miss the good old days when a new rom came out every week and new exploits came out almost instantly.

Since there is no official unlock method, it's very tough to develop. Even if there was a workaround to unlock, these money hungry CDMA carriers lock us out of fastboot and adb, so it wouldn't be possible either way. I really wish I would've waited for the new Nexus phones or the OnePlus Two.

ironbesterer said:
Since there is no official unlock method, it's very tough to develop. Even if there was a workaround to unlock, these money hungry CDMA carriers lock us out of fastboot and adb, so it wouldn't be possible either way. I really wish I would've waited for the new Nexus phones or the OnePlus Two.
Click to expand...
Click to collapse
The one plus 2 isn't for CDMA, but yeah, the nexus phone would have been great.

EmSeeMAC said:
The one plus 2 isn't for CDMA, but yeah, the nexus phone would have been great.
Click to expand...
Click to collapse
Wasn't saying it was. I'm saying I wish I would've waited for it. I didn't want a carrier phone to begin with, but the G4 made me want it. Big mistake
Sent from my LGLS991 using Tapatalk

I know how you feel. I had mine since release and though I think its an all around great phone root for the most part has done me justice. I just think the general idea of bootloader locking is bull**** and should be illegal. I would love a nexus phone but I will not buy into googles push to cloud storage and their services. I can deal with no removable battery but non expandable memory is a no go. Honestly if/when we get android M on the G3 and we get a custom rom I will go back to it provided the bluetooth issues are ironed out. But thats just my 2 cents

kangta05 said:
I know how you feel. I had mine since release and though I think its an all around great phone root for the most part has done me justice. I just think the general idea of bootloader locking is bull**** and should be illegal. I would love a nexus phone but I will not buy into googles push to cloud storage and their services. I can deal with no removable battery but non expandable memory is a no go. Honestly if/when we get android M on the G3 and we get a custom rom I will go back to it provided the bluetooth issues are ironed out. But thats just my 2 cents
Click to expand...
Click to collapse
Bootloader unlock, illegal... Really? Please don't be that guy. We bought the phone, we should be able to do what we want to it. That's like buying a car and it being illegal to change your own oil.

You might want to read that again. Where did I state that UN locking it should be illegal. I said the whole boot loader locking thing is bs ie we should not be locked out from it.

I called LG and talk to a tech who told me if I send my phone to them they would unlock my bootloader but it would void my warranty and of course I already knew that but I was just shocked that they said yes instead of telling me no.

Just got a Droid Turbo after selling my LG G4, is it worth the Root?

I havent rooted a device before but the idea of getting rid of the bloatware that came on the phone and extending battery life as well as increasing performance is appealing to me.
Is your device rooted? and do you feel its worth it?
I also dont really know where to start with rooting it, I had a friend reccommend Kingoroot, but I am not sure which root is 'best' per se.
I also believe I need to unlock my bootloader...Not sure if it is unlocked already, it is a refurbished verizon unloicked phone.
Pardon my ignorance I am just getting into this stuff.

zwalk said:
I havent rooted a device before but the idea of getting rid of the bloatware that came on the phone and extending battery life as well as increasing performance is appealing to me.
Is your device rooted? and do you feel its worth it?
I also dont really know where to start with rooting it, I had a friend reccommend Kingoroot, but I am not sure which root is 'best' per se.
I also believe I need to unlock my bootloader...Not sure if it is unlocked already, it is a refurbished verizon unloicked phone.
Pardon my ignorance I am just getting into this stuff.
Click to expand...
Click to collapse
Yes. Hopefully you didn't do any updating. http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684

Its on 5.1 currently and trying to get me to update I cleared my cache to get rid.of the update file

Wow that's a long and slightly intimidating process.
Hopefully the performance battery life and lack of bloat is worth it

I owned two XT1225 (the international version of the Droid Turbo) and won a FREE, NEW AT&T LG G4 last summer, when it was first released. (I'm on AT&T.) Stayed in the box. The LG G4 is an excellent phone, but just doesn't hit all the cumulative features of the Quark. I even bought a Qi wireless back plate for the LG G4, to enable that feature -- but still never used the phone.
Sold it on eBay a few months ago and bought a 3rd XT1225 to keep as backup for me and my wife. So, yeah, it's worth it.

I love the phone. It's awesome, I'm just getting cold feet on the root. It's the first time I've tried it.
So the root makes a big difference?

zwalk said:
I love the phone. It's awesome, I'm just getting cold feet on the root. It's the first time I've tried it.
So the root makes a big difference?
Click to expand...
Click to collapse
Unlocking the phone lets you do the following things:
Remove bloat
Use the Xposed framework to customize your phone in almost any way you can imagine
Install custom roms, including roms that are a more recent version of Android than what Motorola slowly rolls out
Use security programs like Cerberus to give your phone remote commands if it is lost/stolen
Use battery optimization programs like Amplify and Greenify
Tweak your kernel to favor power over battery life, or vice versa
Other stuff that I can't think of right now

Another reason is to install a custom recovery (TWRP) after boot loader is unlocked. TWRP allows you to make a back up of everything on your phone.

It's worth it just to keep your phone relevant. Odds are we'll see android n with the unlocked boot loader I doubt we'll see it without
Sent from my DROID Turbo using XDA-Developers mobile app

There are youtube videos showing the Sunshine unlock, root, and TWRP process. It's really easy and takes only a few minutes.
The first phone I rooted was the Samsung Intercept back before all of the "One Click Root" apps came about. I had to mate it with my computer and run a long string of ADB commands. That's when I learned about Paths and Environmental Variables. Then installing ClockworkMod Recovery... You had to pull the battery out at a precise moment to get the recovery to stick before the first boot or else the phone reverted to stock recovery. But all of that hinged on if you got the Samsung drivers to work right. If that's wasn't intimidating, then I don't know what is.