Database Develop

[Q]Can someone help a beginner root to get rid of ATT bloatware?

New to the forums and the rooting scene. From me researching, it seems I can get rid of the ATT bloatware on my HTC One by rooting the phone. I've never rooted a phone in my life, and the vast majority of the tutorials on the site assume a working knowledge of what the heck they're talking about (which I don't...).
I was able to follow the tutorial in this thread (http://forum.xda-developers.com/showthread.php?t=2182792) to successfully unlock the bootloader.
(1) What does unlocking the bootloader mean?
(2) When I unlocked the bootloader, my phone completely reset. Is that normal?
(3) The tutorial continues as if your phone didn't reset. Should I reboot back into the fastboot mode and plug back in to the comp to continue the tutorial?
(4) By unlocking the bootloader, will I receive OTAs from ATT?
(5) If I root, will I receive OTAs from ATT?
(6) If I root, how can I still use the stock OS and just get rid of the ATT bloatware?
(7) I see things talk about "NAND backups" before one should root. What are those?
(8) What are RUUs?
(9) What does "Odexed" and "De-Odexed" mean...?
Thanks in advance for the help. I want to learn this stuff and can't find any explicit answers in these forums. I don't want to damage this brand new awesome phone.

jumi1174 said:
New to the forums and the rooting scene. From me researching, it seems I can get rid of the ATT bloatware on my HTC One by rooting the phone. I've never rooted a phone in my life, and the vast majority of the tutorials on the site assume a working knowledge of what the heck they're talking about (which I don't...).
I was able to follow the tutorial in this thread (http://forum.xda-developers.com/show...182792&page=21) to successfully unlock the bootloader.
(1) What does unlocking the bootloader mean?
(2) When I unlocked the bootloader, my phone completely reset. Is that normal?
(3) The tutorial continues as if your phone didn't reset. Should I reboot back into the fastboot mode and plug back in to the comp to continue the tutorial?
(4) By unlocking the bootloader, will I receive OTAs from ATT?
(5) If I root, will I receive OTAs from ATT?
(6) If I root, how can I still use the stock OS and just get rid of the ATT bloatware?
(7) I see things talk about "NAND backups" before one should root. What are those?
(8) What are RUUs?
(9) What does "Odexed" and "De-Odexed" mean...?
Thanks in advance for the help. I want to learn this stuff and can't find any explicit answers in these forums. I don't want to damage this brand new awesome phone.
Click to expand...
Click to collapse
i would ike many of the same answers
experts help us!

https://www.youtube.com/watch?v=rRkAHw_GmIs&feature=youtube_gdata_player
https://www.youtube.com/watch?v=QU7vi388dMk&feature=youtube_gdata_player
Sent from my HTC One using xda premium

Im still very new to all of this as well, but i wanted to share this toolkit with you just encase you havent seen it yet. http://forum.xda-developers.com/showthread.php?t=2183942 Its been a tremendous help to me, hopefully it will be to you.
As far as the AT&T bloatware is concerned, It was very easy to remove once i was rooted and had flashed a new ROM. Ive used both Titanium Backup, and Rom Toolkit Pro to remove the junk.
Best of luck with your devices, Ive had a great time learning with mine so far.

jumi1174 said:
New to the forums and the rooting scene. From me researching, it seems I can get rid of the ATT bloatware on my HTC One by rooting the phone. I've never rooted a phone in my life, and the vast majority of the tutorials on the site assume a working knowledge of what the heck they're talking about (which I don't...).
I was able to follow the tutorial in this thread (http://forum.xda-developers.com/show...182792&page=21) to successfully unlock the bootloader.
(1) What does unlocking the bootloader mean?
(2) When I unlocked the bootloader, my phone completely reset. Is that normal?
(3) The tutorial continues as if your phone didn't reset. Should I reboot back into the fastboot mode and plug back in to the comp to continue the tutorial?
(4) By unlocking the bootloader, will I receive OTAs from ATT?
(5) If I root, will I receive OTAs from ATT?
(6) If I root, how can I still use the stock OS and just get rid of the ATT bloatware?
(7) I see things talk about "NAND backups" before one should root. What are those?
(8) What are RUUs?
(9) What does "Odexed" and "De-Odexed" mean...?
Thanks in advance for the help. I want to learn this stuff and can't find any explicit answers in these forums. I don't want to damage this brand new awesome phone.
Click to expand...
Click to collapse
1. Unlocking the bootloader allows you to flash a custom recovery onto your device. It's a necessary step in the rooting process until s-off is obtained
2. This is 100% normal. It is strongly advised you backup everything before unlocking due to this.
3. The link in your post to that tutorial is broken so there is no way to see what you mean. Sorry.
4. You cannot receive OTA while the bootloader is unlocked. You would need to relock your bootloader to continue with an OTA update.
5. As of now, no due to having to unlock your bootloader. Please see answer 4.
6. You would need to flash a zip file in a custom recovery to debloat your phone. There are other ways but this is the best way for a very new user. Link to debloat zip: http://forum.xda-developers.com/showthread.php?t=2250403
7. Nandbackup or Nandroid are complete backups of your phone's firmware. It's recommended to have one good up to date backup so if something goes wrong on a new ROM you flashed, you can easily revert. Nandroids are created in custom recoveries like TWRP.
8. An RUU is a package for your phone that contains a set of stock images used to unroot your phone and return it to complete stock. It stands for ROM Update Utility.
9. Odexed is the default state of the stock ROM. What it means is that a separate .odex cache file is stored away from a system app. It allows the app to load faster as upon boot your phone loads these cache files into the Dalvik VM. When a developer De-Odexes a ROM it means they have taken away those cache files and instead compiled them within the system app. This, in theory is a bit slower, but only when you clear your Dalvik and cache from recovery, otherwise you will notice no difference. The reason a developer does this is it makes the system app easily modifiable and themable. In summary, Deodex equals easily modifiable, whereas odex means the app is more locked down.
Sent from my HTC One using xda app-developers app

Thanks RPelham,
I hate to piggyback on someone else's thread, but they may want the answer to my question as well.
Is it a good idea to clear system and Dalvik cache from within recovery every now and then? Im used to the PC world, where clearing cache from time to time helps keep things in order.

Snakemanc6 said:
Thanks RPelham,
I hate to piggyback on someone else's thread, but they may want the answer to my question as well.
Is it a good idea to clear system and Dalvik cache from within recovery every now and then? Im used to the PC world, where clearing cache from time to time helps keep things in order.
Click to expand...
Click to collapse
No. You only need to clear Dalvik and Cache when flashing a new ROM, Kernel or basically any ZIP package. It won't serve any good purpose to randomly clear it. =)
Android has a great built in way of keeping your phone running great and killing any app that has not been recently used to keep everything running smooth.
Sent from my HTC One using xda app-developers app

behrouz said:
https://www.youtube.com/watch?v=rRkAHw_GmIs&feature=youtube_gdata_player
https://www.youtube.com/watch?v=QU7vi388dMk&feature=youtube_gdata_player
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Awesome videos, thanks!
RPelham said:
1. Unlocking the bootloader allows you to flash a custom recovery onto your device. It's a necessary step in the rooting process until s-off is obtained
2. This is 100% normal. It is strongly advised you backup everything before unlocking due to this.
3. The link in your post to that tutorial is broken so there is no way to see what you mean. Sorry.
4. You cannot receive OTA while the bootloader is unlocked. You would need to relock your bootloader to continue with an OTA update.
5. As of now, no due to having to unlock your bootloader. Please see answer 4.
6. You would need to flash a zip file in a custom recovery to debloat your phone. There are other ways but this is the best way for a very new user. Link to debloat zip: http://forum.xda-developers.com/showthread.php?t=2250403
7. Nandbackup or Nandroid are complete backups of your phone's firmware. It's recommended to have one good up to date backup so if something goes wrong on a new ROM you flashed, you can easily revert. Nandroids are created in custom recoveries like TWRP.
8. An RUU is a package for your phone that contains a set of stock images used to unroot your phone and return it to complete stock. It stands for ROM Update Utility.
9. Odexed is the default state of the stock ROM. What it means is that a separate .odex cache file is stored away from a system app. It allows the app to load faster as upon boot your phone loads these cache files into the Dalvik VM. When a developer De-Odexes a ROM it means they have taken away those cache files and instead compiled them within the system app. This, in theory is a bit slower, but only when you clear your Dalvik and cache from recovery, otherwise you will notice no difference. The reason a developer does this is it makes the system app easily modifiable and themable. In summary, Deodex equals easily modifiable, whereas odex means the app is more locked down.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the awesome reply!
This is the link: http://forum.xda-developers.com/showthread.php?t=2182792
Sorry it was dead, I'll edit my original post.
Another question if you don't mind (may be a stupid question), if I root, will I still be able to purchase apps from the play store without any trouble?

behrouz said:
https://www.youtube.com/watch?v=rRkAHw_GmIs&feature=youtube_gdata_player
https://www.youtube.com/watch?v=QU7vi388dMk&feature=youtube_gdata_player
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
These videos are an absolute perfect example of how to unlock and root. Step by step. If you are new, this will be the perfect go to for help.
Sent from my HTC One using xda app-developers app
---------- Post added at 12:36 AM ---------- Previous post was at 12:31 AM ----------
jumi1174 said:
Another question if you don't mind (may be a stupid question), if I root, will I still be able to purchase apps from the play store without any trouble?
Click to expand...
Click to collapse
Yes, you absolutely can. The only thing Root is giving you is administration level access to your phone. Obtaining root gives you the ability to modify, remove or add core system files and gives apps a lot more functionality as they can integrate themselves into the system.
And to answer question 3:
Yes the phone resets after you unlock your bootloader and it boots back into your phone. Simply reboot back to your bootloader and enter fastboot mode to continue flashing your recovery.
After you flash the recovery, it will boot back into your phone again (once you select recovery from the bootloader menu for the first time after the flash). Don't be alarmed by this, just reboot once more, select your recovery option again and this time it will truely take you to recovery.
Sent from my HTC One using xda app-developers app

RPelham said:
Yes, you absolutely can. The only thing Root is giving you is administration level access to your phone. Obtaining root gives you the ability to modify, remove or add core system files and gives apps a lot more functionality as they can integrate themselves into the system.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for all the help. One more if you don't mind (I appreciate your patience with helping a beginner like myself), will my phone be reset again when I root?

jumi1174 said:
Thanks for all the help. One more if you don't mind (I appreciate your patience with helping a beginner like myself), will my phone be reset again when I root?
Click to expand...
Click to collapse
No. Once you unlocked your bootloader your phone will not reset unless you flash a custom ROM or specifically wipe your device. Rooting will retain all settings and apps.
P.s. I'm heading off for the night. I hope I answered everything for you and helped you obtain a better understanding over this whole process. Ill follow up tomorrow to see if everything worked out for you and answer any additional questions. =)
Sent from my HTC One using xda app-developers app

RPelham said:
No. Once you unlocked your bootloader your phone will not reset unless you flash a custom ROM or specifically wipe your device. Rooting will retain all settings and apps.
P.s. I'm heading off for the night. I hope I answered everything for you and helped you obtain a better understanding over this whole process. Ill follow up tomorrow to see if everything worked out for you and answer any additional questions. =)
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Excellent! Thanks for all the help, I really appreciate it! I'll edit this post if I have any more questions.
More questions:
(1) All the files on this thread: http://forum.xda-developers.com/showthread.php?t=2207874
What is the purpose of all these different files? Should I be familiar with them and will I ever need to use them?
(2) This package: http://forum.xda-developers.com/showthread.php?t=2250403
I'm not exactly sure how to install it. Any advice or tips?
(3) The instructions for this ROM: http://forum.xda-developers.com/showthread.php?t=2192324
-Download ROM
-Copy ROM to your sdcard
-Fullwipe in AROMA if you come from another ROM or base
-Flash the ROM
-Let the ROM boot (After a Fullwipe this takes some time)
-Enjoy TrickDroid
I understand the first 2 steps, but what does "Fullwipe in AROMA" mean?
(4) Difference between a ROM and a KERNEL?
(5) Are you familiar with Titanium Backup? I've tried reading their wiki, but I'm still not 100% sure what exactly it backs up and how that is different than the TWRP back up.

jumi1174 said:
Excellent! Thanks for all the help, I really appreciate it! I'll edit this post if I have any more questions.
More questions:
(1) All the files on this thread: http://forum.xda-developers.com/showthread.php?t=2207874
What is the purpose of all these different files? Should I be familiar with them?
(2) This package: http://forum.xda-developers.com/showthread.php?t=2250403
I'm not exactly sure how to install it. Any advice or tips?
Click to expand...
Click to collapse
Hi.
1) they are just ruu for many different carriers, countries, etc. There is a specific ruu for your device. That's why so many ruu there
2) no need for that. Just install titanium backup pro from play store after rooting and you can delete all bloatwares or freeze them. Which will also get rid of those unwanted apps from your phone.
---------- Post added at 03:06 AM ---------- Previous post was at 03:03 AM ----------
RPelham said:
1. Unlocking the bootloader allows you to flash a custom recovery onto your device. It's a necessary step in the rooting process until s-off is obtained
7. Nandbackup or Nandroid are complete backups of your phone's firmware. It's recommended to have one good up to date backup so if something goes wrong on a new ROM you flashed, you can easily revert. Nandroids are created in custom recoveries like TWRP.
8. An RUU is a package for your phone that contains a set of stock images used to unroot your phone and return it to complete stock. It stands for ROM Update Utility.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Hello mate
I have 2 questions.
Number 7, how do I make backup of your rom if you still haven't installed custom recovery?
Number 8 to unroot my phone I can also use the nandroid backup instead of ruu right?
Edit: 1 more Lol. Sorry.
I asked many places but didn't get an answer for it.
Let's say I have custom ROM, and I need to relock boot loader and flash stock ruu to go back to stock in order to receive ota update. Does the ruu contains the stock recovery? Cuz I read somewhere that in order to get ota update I also needed to flash stock recovery?
Thanks a lot! I think I'm all set after this kkk

If anyone has an answer to this question I'd appreciate it very much. I've rooted many phones but all of them have had SD cards. The HTC One is lacking an SD Card so when I back up data/apks etc is there a spot on the phone's storage that doesn't get wiped when wiping from recovery to install new roms?

gotrandom said:
If anyone has an answer to this question I'd appreciate it very much. I've rooted many phones but all of them have had SD cards. The HTC One is lacking an SD Card so when I back up data/apks etc is there a spot on the phone's storage that doesn't get wiped when wiping from recovery to install new roms?
Click to expand...
Click to collapse
Nope. All gets wiped. Backup on ur PC.

Uh oh. I just told him the opposite in another thread. I could swear I read that selecting a "wipe userdata" option in recovery would erase everything in the /data partition *except* whatever is below /data/media?
Did I get this wrong?
Sent from my PC36100 using xda app-developers app

Ive flashed a couple of different ROMs, and my media has not been erased when selecting "wipe user data". Im using CWM, if that's of any consequence.

Snakemanc6 said:
Ive flashed a couple of different ROMs, and my media has not been erased when selecting "wipe user data". Im using CWM, if that's of any consequence.
Click to expand...
Click to collapse
Sorry then. I saw a video on yt saying all would be deleted. I will try to find and post it here.
Edit. https://www.youtube.com/watch?v=7hvbwWTbZOU&feature=youtube_gdata_player

He was using TWRP, no idea if that makes a difference. Just passing on my experience, Im by no means well versed in all of this lol
Its great having such an active forum to learn from though :good:

ksarius said:
Hi.
1) they are just ruu for many different carriers, countries, etc. There is a specific ruu for your device. That's why so many ruu there
2) no need for that. Just install titanium backup pro from play store after rooting and you can delete all bloatwares or freeze them. Which will also get rid of those unwanted apps from your phone.
---------- Post added at 03:06 AM ---------- Previous post was at 03:03 AM ----------
Hello mate
I have 2 questions.
Number 7, how do I make backup of your rom if you still haven't installed custom recovery?
Number 8 to unroot my phone I can also use the nandroid backup instead of ruu right?
Edit: 1 more Lol. Sorry.
I asked many places but didn't get an answer for it.
Let's say I have custom ROM, and I need to relock boot loader and flash stock ruu to go back to stock in order to receive ota update. Does the ruu contains the stock recovery? Cuz I read somewhere that in order to get ota update I also needed to flash stock recovery?
Thanks a lot! I think I'm all set after this kkk
Click to expand...
Click to collapse
Im not 100% sure as I do not use Titanium, if someone could check that would be great, but I don't think titanium can permanently remove bloat yet. Freeze, yes, remove I'm unsure.
Our device has not achieved s-off which means that the partition the system apps sit on is not accessible to be altered from within the ROM, only by recovery / adb.
7. To my knowledge you must have a custom recovery to make a nandroid. You can't make a complete one without it. And once you nandroid, that backup is specifically for that recovery. I.e. you fly use a cwm nandroid in twrp
8. As long as your nandroid was created before installing the root package, yes.
RUUs will reflash stock recovery.
Sent from my HTC One using xda app-developers app
---------- Post added at 07:56 AM ---------- Previous post was at 07:52 AM ----------
jumi1174 said:
Excellent! Thanks for all the help, I really appreciate it! I'll edit this post if I have any more questions.
More questions:
(1) All the files on this thread: http://forum.xda-developers.com/showthread.php?t=2207874
What is the purpose of all these different files? Should I be familiar with them and will I ever need to use them?
(2) This package: http://forum.xda-developers.com/showthread.php?t=2250403
I'm not exactly sure how to install it. Any advice or tips?
(3) The instructions for this ROM: http://forum.xda-developers.com/showthread.php?t=2192324
-Download ROM
-Copy ROM to your sdcard
-Fullwipe in AROMA if you come from another ROM or base
-Flash the ROM
-Let the ROM boot (After a Fullwipe this takes some time)
-Enjoy TrickDroid
I understand the first 2 steps, but what does "Fullwipe in AROMA" mean?
(4) Difference between a ROM and a KERNEL?
(5) Are you familiar with Titanium Backup? I've tried reading their wiki, but I'm still not 100% sure what exactly it backs up and how that is different than the TWRP back up.
Click to expand...
Click to collapse
1 and 2 were answered above. I also elaborated on 2 above.
3. Aroma is an installation software made for recovery. It's a wizard that walks you through the ROM setup. You'll see an option for it while setting up the ROM
4. Kernel is the software that allows your hardware to communicate with your ROM as well as control boot screens, splash screens and overclocking and undervolting.
ROM is the phones operating system.
5. TWRP is a FULL backup, titanium is just an app, it can't backup 100% of everything like a recovery can. Titanium backs up your app and user data. Basically your settings and apps.
Sent from my HTC One using xda app-developers app

FireTV Partial Bootloader Unlock

Well it's a little early for Christmas... but here is a special gift. This will allow the bootloader to load things from boot or recovery without them needing to be patched. This is not a full unlock and will not enable fastboot boot or fastboot flash. Obviously this will only work if you are rooted.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Using this tool won't brick your Fire TV, but doing stupid things afterwards might. I will stress here that flashing something bad to boot is a guaranteed way to brick because if the kernel can't boot you have no way to get back to recovery. For testing kernels, it's best to flash recovery to the boot partition and the new kernel to test to the recovery partition.
To use:
Downgrade: You must first downgrade to 51.1.0.2. If you already have CWM installed, you can skip this.
adb push aftv-unlock /data/local/tmp/
adb shell
chmod 755 /data/local/tmp/aftv-unlock
su
/data/local/tmp/aftv-unlock unlock
Afterwards you should see this message:
Code:
Attempting to unlock...
All done!
If not, something went wrong. If for whatever reason you want to relock the bootloader, you can use this command:
Code:
/data/local/tmp/aftv-unlock lock
You can download it here.

WOW, just WOW, awesome work rbox!
I was definitely not expecting this.

rbox said:
Well it's a little early for Christmas... but here is a special gift. This will allow the bootloader to load things from boot or recovery without them needing to be patched. This is not a full unlock and will not enable fastboot boot or fastboot flash. Obviously this will only work if you are rooted.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Using this tool won't brick your Fire TV, but doing stupid things afterwards might. I will stress here that flashing something bad to boot is a guaranteed way to brick because if the kernel can't boot you have no way to get back to recovery. For testing kernels, it's best to flash recovery to the boot partition and the new kernel to test to the recovery partition.
To use:
Downgrade: You must first downgrade to 51.1.0.2. If you already have CWM installed, you can skip this.
adb push aftv-unlock /data/local/tmp/
adb shell
chmod 755 /data/local/tmp/aftv-unlock
su
/data/local/tmp/aftv-unlock unlock
Afterwards you should see this message:
Code:
Attempting to unlock...
All done!
If not, something went wrong. If for whatever reason you want to relock the bootloader, you can use this command:
Code:
/data/local/tmp/aftv-unlock lock
You can download it here.
Click to expand...
Click to collapse
Congrats to you
And Merry Christmas to us FTV users!
BTW, could you please tell me the console messages for lock failure and unlock failure? (may they never occur)

..

JJ-KwiK said:
Awesome!
Thanks man!
Click to expand...
Click to collapse
maybe we can get some real mods for this device now. different roms and what not.
just ran the unlock and it worked like a charm

Rbox do you know if the bootloader can boot from usb?

Does this require a minimal CWM version of yours?
I installed your Recovery (CWM) - on all 4 of my AFTVs - when you first released it ..
I've not had any reason to upgrade to the latest versions.... I'm just using the heck outta the AFTV as it is built, with all the nice rooted options. I really don't need anything else yet, so ...
with that said " can I just install this unlock-lock feature? "

Truly amazing. Can't wait for full fledged android on this.

Nice to see this, but it doesn't help much when you have a Fire TV with a non-rootable firmware.

jmandawg said:
Rbox do you know if the bootloader can boot from usb?
Click to expand...
Click to collapse
The bootloader will only boot from the boot partition or the recovery partition on the mmc. But I'm working on a boot menu that will allow you to easily boot additional kernels which can then load your os from wherever you want.
toe-rag said:
I installed your Recovery (CWM) - on all 4 of my AFTVs - when you first released it ..
I've not had any reason to upgrade to the latest versions.... I'm just using the heck outta the AFTV as it is built, with all the nice rooted options. I really don't need anything else yet, so ...
with that said " can I just install this unlock-lock feature? "
Click to expand...
Click to collapse
Yes. This is independent of anything. The only dependence is the latest version of CWM requires it.

I installed ccm when you first released it then upgraded to the latest firmware the other night. Thanks a lot btw! But, can I assume (as a novice) this is not something I need to do right now. What I mean is is this just for people that want to experiment with new kernels or is there some advantage I'm missing? Thanks again and sorry if my question is a little too basic for this thread. I'm just genuinely curious.

KLit75 said:
I installed ccm when you first released it then upgraded to the latest firmware the other night. Thanks a lot btw! But, can I assume (as a novice) this is not something I need to do right now. What I mean is is this just for people that want to experiment with new kernels or is there some advantage I'm missing? Thanks again and sorry if my question is a little too basic for this thread. I'm just genuinely curious.
Click to expand...
Click to collapse
If you don't care about updating your CWM version, or using any of the other cool things I'll release in the future that needs it, then no. You don't need to do this.

Thanks for the response. I did, in fact just update cwm and am running your latest fw update. I guess "need" isn't the right word. But if I unlock it tonight the cool stuff is still forthcoming.
Sorry just 2 questions:
1. Unlocking and keeping it unlocked indefinetly is ok?
And here's one that s on a slightly different subject...
2. I noticed updating with your fw saves my settings. Is there a safe way to factory restore using cwm without the risk of losing root?
That's actually the one I'm most interested in now. My aftv has been having issues that are hard to troubleshoot. An option to factory restore would be great. I mostly use it for xbmc so the only thing I care about losing is root. Thanks.

KLit75 said:
Thanks for the response. I did, in fact just update cwm and am running your latest fw update. I guess "need" isn't the right word. But if I unlock it tonight the cool stuff is still forthcoming.
Sorry just 2 questions:
1. Unlocking and keeping it unlocked indefinetly is ok?
And here's one that s on a slightly different subject...
2. I noticed updating with your fw saves my settings. Is there a safe way to factory restore using cwm without the risk of losing root?
That's actually the one I'm most interested in now. My aftv has been having issues that are hard to troubleshoot. An option to factory restore would be great. I mostly use it for xbmc so the only thing I care about losing is root. Thanks.
Click to expand...
Click to collapse
Of course keeping it locked is fine... i wouldn't have released the tool if it wasn't.
As I've stated in MANY OTHER THREADS... factory reset in CWM is perfectly fine and has nothing to do with root.

rbox said:
If you don't care about updating your CWM version, or using any of the other cool things I'll release in the future that needs it, then no. You don't need to do this.
Click to expand...
Click to collapse
That's great. Thanks again

Thanks for this! Was very happy that the AFTV i ordered from eBay was rootable.
at the risk of being "that guy", can someone explain to a relative dummy like me the future potential with an unlocked bootloader? are we talking maybe an Android TV rom down the road? .. Apologies in advance

Hi, I unlocked the bootloader and it was successfully. Thank you rbox

barrist said:
Thanks for this! Was very happy that the AFTV i ordered from eBay was rootable.
at the risk of being "that guy", can someone explain to a relative dummy like me the future potential with an unlocked bootloader? are we talking maybe an Android TV rom down the road? .. Apologies in advance
Click to expand...
Click to collapse
Nothing that people couldn't already do with my old CWM. Custom ROMs and whatnot has been possible for a while. This just makes things a little easier because kernels don't need to be patched.

Yea! Install failed yesterday. I've had SU problems I think. Couldn't get the # prompt. Reinstalled latest ROM and SL'd SU from the store. The Unlock finally took. Thanks.

nice, thanks rbox, you rock.

[Q] First Nexus

So this is my first Nexus device. I'm coming from and S4 followed by a Note 3 so I'm kinda used to the samsung environment and don't want to screw anything up. I have a couple of questions.
First, if I root with CF-Auto Root, does the tool wipe all of the current data?
Second, how will rooting the phone affect the OTA updates and their availability?
Third, are the root apps already compatible with 5.0/Nexus 6?
Thank you!

Cf auto root does not remove all data per se, but unlocking your phone will if it is not.. And it's part of the process.
Rooting probably doesn't affect OTAs, and if it does, can easily be undone.
Yes, I haven't found a common root app that isn't compatible.

Dankchild said:
So this is my first Nexus device. I'm coming from and S4 followed by a Note 3 so I'm kinda used to the samsung environment and don't want to screw anything up. I have a couple of questions.
First, if I root with CF-Auto Root, does the tool wipe all of the current data?
Second, how will rooting the phone affect the OTA updates and their availability?
Third, are the root apps already compatible with 5.0/Nexus 6?
Thank you!
Click to expand...
Click to collapse
1. No it does not wipe your data unless your bootloader was locked.
2. It has no effect. You'll be able to accept the OTA and lose root (you can enable a survival script).
3. Yes.

Dankchild said:
So this is my first Nexus device. I'm coming from and S4 followed by a Note 3 so I'm kinda used to the samsung environment and don't want to screw anything up. I have a couple of questions.
First, if I root with CF-Auto Root, does the tool wipe all of the current data?
Second, how will rooting the phone affect the OTA updates and their availability?
Third, are the root apps already compatible with 5.0/Nexus 6?
Thank you!
Click to expand...
Click to collapse
some people here are wrong, will it wipe data? for the first time (when unlocking the OEM) yes. Lollipop now has a different way to check ROOTING, once it detects you modified ANY file in the system core files, it aborts. To work around this, either use a ROM and upgrade via FLASHING (which i do) or use NEXUS ROOT TOOLKIT. Using the toolkit (which is very noob friendly) allows everything to be done by a click. BUT, to upgrade via toolkit, (ota) you need to flash stock which in the toolkit completely wipe system, then unroot, then update, then reroot and flash whatever ROM you want, which would again wipe your device. the way i do it is easier, it requires no wiping and i get to keep my ROM at all times and i get earlier versions (depending on ROM creators) then OTA, i currently have 5.0.2 on my nexus 6, which isnt ven out yet OTA. :fingers-crossed:

TheSkillfulTroll said:
some people here are wrong, will it wipe data? for the first time (when unlocking the OEM) yes. Lollipop now has a different way to check ROOTING, once it detects you modified ANY file in the system core files, it aborts. To work around this, either use a ROM and upgrade via FLASHING (which i do) or use NEXUS ROOT TOOLKIT. Using the toolkit (which is very noob friendly) allows everything to be done by a click. BUT, to upgrade via toolkit, (ota) you need to flash stock which in the toolkit completely wipe system, then unroot, then update, then reroot and flash whatever ROM you want, which would again wipe your device. the way i do it is easier, it requires no wiping and i get to keep my ROM at all times and i get earlier versions (depending on ROM creators) then OTA, i currently have 5.0.2 on my nexus 6, which isnt ven out yet OTA. :fingers-crossed:
Click to expand...
Click to collapse
People modify the OTA zip to remove the abort of installation if any system files are modified/removed. Of course this can lead to problems, but can also be successful most of the times. Depends on what the user modifies.
Nexus Root Toolkits, I highly do not encourage users to use this. As easy as they are, they prevent users from learning about fastboot and adb. They are essential things to learn and relying on a program to do them for you is not good practice especially when it is quite easy to do it manually. If everybody used the toolkit then no body would understand how its done.
The part about custom ROMs, I recommend using custom ROMs. There are many to browse through, it depends on what you're looking for. Its very exciting to look at all the ROMs to select one to try, just to be eager to try another ROM for fun.
You can read more about toolkits @ http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909
Very good read.

zephiK said:
People modify the OTA zip to remove the abort of installation if any system files are modified/removed. Of course this can lead to problems, but can also be successful most of the times. Depends on what the user modifies.
Nexus Root Toolkits, I highly do not encourage users to use this. As easy as they are, they prevent users from learning about fastboot and adb. They are essential things to learn and relying on a program to do them for you is not good practice especially when it is quite easy to do it manually. If everybody used the toolkit then no body would understand how its done.
The part about custom ROMs, I recommend using custom ROMs. There are many to browse through, it depends on what you're looking for. Its very exciting to look at all the ROMs to select one to try, just to be eager to try another ROM for fun.
You can read more about toolkits @ http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909
Very good read.
Click to expand...
Click to collapse
the toolkit helps alot of new comers who have no idea on what to do, sure they can try the manual way, but doing so can end up very bad as its not easy to revert, while the toolkit helps by being able to bring you back from bricks. i started off using the toolkit and now i just use flashify for rom installations, if anything goes wrong (a brick) i just have tbe option to use the toolkit to set me back to pure stock and factory condition.

TheSkillfulTroll said:
the toolkit helps alot of new comers who have no idea on what to do, sure they can try the manual way, but doing so can end up very bad as its not easy to revert, while the toolkit helps by being able to bring you back from bricks. i started off using the toolkit and now i just use flashify for rom installations, if anything goes wrong (a brick) i just have tbe option to use the toolkit to set me back to pure stock and factory condition.
Click to expand...
Click to collapse
Its very easy to do manually, if it was a long and tedious step such as G1 rooting or manually exploiting a phone then a toolkit is reasonable.
For Nexus 6, its as simple as.
1. install drivers & fastboot.
2. bootloader mode (vol down + power)
3. fastboot oem unlock
4. fastboot flash recovery <name-of-recovery>.img
5. flash supersu
A very good sticky guide is posted, http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
And we all know that regardless if you use a Root Toolkit, you MUST read before you do anything.
Toolkit doesn't really help you bring you back from bricks, in fact I would argue that it does the opposite. You're relying on a program to do what you're supposed to do. In my experience of helping people in XDA forums, they've used toolkits and got themselves into bad positions and wasn't sure how to fix their problem or the toolkit soft-bricking their device. They had to learn fastboot / adb to resolve their issue.
Read the dangers of toolkits, they're not as fancy as people view it to be. Its not difficult to do the tasks manually. Very easy to do. I was able to root/unlock my N6 in a minute since I already had the environment set up.
Think of it this way, you have math homework. You can either go input it into the calculator and have the answer. Congrats, you have the answer but did you understand how they got to that step? No not really.
Its imperative for any user on XDA to learn the fastboot/adb step, its not difficult as I've mentioned time and time again. It takes some reading, but it'll save you time because later down the line you'll understand why you did what you did and you can get yourself out of situations instead of going to Q&A and asking for someone help on how to get back to factory or a soft-brick situation.
A snippet from the link above,
The people who are using these scripts aren't learning what is actually happening when they press 1 on their keyboard. Boom, their phone is unlocked, su-binaries and cwm recovery installed. Then, they flash a rom without creating a nandroid. What happens if something goes wrong and they didn't place any safety nets to help them? They post a thread saying their phone is bricked. People take time out of their day to help these people out, but since the user doesn't understand what the helper is talking about, they can't fix it.
Just last weekend I spent 30 minutes replying to a PM with step by step instructions how to flash stock images and including links to files and resources. The person replied back. Instead of fixing his phone himself, he said he "claimed his phone as stolen and will be getting sent a new one lol". WTF?! Not only is that morally wrong, it's also insurance fraud. And we wonder why carriers and OEM's are trying as hard as they can to lock down non-nexus phones.
Please, take the time to learn how to get yourself out of a mess before you are in a mess.
Click to expand...
Click to collapse
If someone can't take a couple minutes out of their time to follow a step-by-step guide then they shouldn't be tinkering with their device.

For information sake (I have already rooted via TK) your post actually does prove a point. For myself and maybe others, would you be willing to P.M me the instructions to do it via ADB/Fastboot just in case , I , myself get screwed over. Thanks Z
Sent from my Nexus 6 using XDA Free mobile app

flash you phone manually you will learn a lot about how the toolkits work.
I find it faster to flash manually than to use a tool kit.
once an OTA is available you can grap the image from the google site and flash the files manually.
There is a way to manually flash you phone and save userdata so you keep all your apps.
One you learn and get a little practice It will be so easy you will be able to flash like it is second nature. (I was a noob that came from iphone and jailbreaking)
I can actually flash the files manually faster that an OTA can update a phone and I type with maybe a total of 6 fingers. because i never took a typing class

zephiK said:
Its very easy to do manually, if it was a long and tedious step such as G1 rooting or manually exploiting a phone then a toolkit is reasonable.
For Nexus 6, its as simple as.
1. install drivers & fastboot.
2. bootloader mode (vol down + power)
3. fastboot oem unlock
4. fastboot flash recovery <name-of-recovery>.img
5. flash supersu
A very good sticky guide is posted, http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
And we all know that regardless if you use a Root Toolkit, you MUST read before you do anything.
Toolkit doesn't really help you bring you back from bricks, in fact I would argue that it does the opposite. You're relying on a program to do what you're supposed to do. In my experience of helping people in XDA forums, they've used toolkits and got themselves into bad positions and wasn't sure how to fix their problem or the toolkit soft-bricking their device. They had to learn fastboot / adb to resolve their issue.
Read the dangers of toolkits, they're not as fancy as people view it to be. Its not difficult to do the tasks manually. Very easy to do. I was able to root/unlock my N6 in a minute since I already had the environment set up.
Think of it this way, you have math homework. You can either go input it into the calculator and have the answer. Congrats, you have the answer but did you understand how they got to that step? No not really.
Its imperative for any user on XDA to learn the fastboot/adb step, its not difficult as I've mentioned time and time again. It takes some reading, but it'll save you time because later down the line you'll understand why you did what you did and you can get yourself out of situations instead of going to Q&A and asking for someone help on how to get back to factory or a soft-brick situation.
A snippet from the link above,
If someone can't take a couple minutes out of their time to follow a step-by-step guide then they shouldn't be tinkering with their device.
Click to expand...
Click to collapse
Can you provide to me instructions on a manual way? Like the other poster said I would like to learn to manually flash OEM unlucks and root and Roms (if possible) thanks Z! P.M ME if you decide to thanks!
Sent from my Nexus 6 using XDA Free mobile app

if you have drivers installed already from first link above then you can follow these steps:
Download the required factory image files to your computer and extract them
1) Create an empty directory. All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory; (it is easier this way)
2) If all you want to do is unlock your bootloader, skip to step 6 in this section.
3) Download the version of Android you want to your new directory. Make sure you are using a nexus 6 image.
4) Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
5) Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
6) Reboot your device into bootloader mode (by turning it off, hold volume down, and press and hold power) and plug it into your computer;
7) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt. In Ubuntu just cd to the directory.
Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-some-description-number.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-some-description-number.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Optional, but read note. Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot format cache
14) Reboot: fastboot reboot
15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked.
No you can root or decrypt. Search for directions on the forum or the internet.
I'm not the original writer of these instructions, but I found these helpful to people wanting the step by step instructions.

TheSkillfulTroll said:
Can you provide to me instructions on a manual way? Like the other poster said I would like to learn to manually flash OEM unlucks and root and Roms (if possible) thanks Z! P.M ME if you decide to thanks!
Click to expand...
Click to collapse
Read the first couple of posts of the following threads. The first talks about how to root, and the other, about how to flash the factory images. Very detailed.
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

If someone can't take a couple minutes out of their time to follow a step-by-step guide then they shouldn't be tinkering with their device.
Click to expand...
Click to collapse
How true. I certainly don't want a paper weight...

Larzzzz82 said:
How true. I certainly don't want a paper weight...
Click to expand...
Click to collapse
Exactly, and if they believe that everything is magical and click on a button "yay I rooted, unlocked my bootloader." Sure you saved time by clicking a button rather than following a step-by-step guide which is quite easy, what happens when you encounter a problem like a soft brick? Questions on whether or not you can flash a older radio etc?
A toolkit can't do that for you, by finding out why something works this way will be better in the long run. I don't mind answering questions but what I do mind is when people use toolkits for something that is already so easy. For Samsung and other manufacturers that lock down their bootloaders, I fully understand why toolkits are needed because they are not unlockable via bootloader mode (unless its HTC, OnePlus, and some other exception) and requires a exploit to obtain root access (e.g. Towelroot).
For Nexus devices (and HTC/OnePlus/etc) devices where the company gave you a "fastboot oem unlock." Use it very simple to do. The hardest part is installing a driver and fastboot executable, which if you have a mac you don't even need the driver. Once you do it once, you're set for life on that computer. When I unlocked my N6, I just literally plugged it in... activated the OEM unlock via developer options and went into bootloader mode and typed fastboot oem unlock.
Finished that all in one minute.

zephiK said:
Exactly, and if they believe that everything is magical and click on a button "yay I rooted, unlocked my bootloader." Sure you saved time by clicking a button rather than following a step-by-step guide which is quite easy, what happens when you encounter a problem like a soft brick? Questions on whether or not you can flash a older radio etc?
A toolkit can't do that for you, by finding out why something works this way will be better in the long run. I don't mind answering questions but what I do mind is when people use toolkits for something that is already so easy. For Samsung and other manufacturers that lock down their bootloaders, I fully understand why toolkits are needed because they are not unlockable via bootloader mode (unless its HTC, OnePlus, and some other exception) and requires a exploit to obtain root access (e.g. Towelroot).
For Nexus devices (and HTC/OnePlus/etc) devices where the company gave you a "fastboot oem unlock." Use it very simple to do. The hardest part is installing a driver and fastboot executable, which if you have a mac you don't even need the driver. Once you do it once, you're set for life on that computer. When I unlocked my N6, I just literally plugged it in... activated the OEM unlock via developer options and went into bootloader mode and typed fastboot oem unlock.
Finished that all in one minute.
Click to expand...
Click to collapse
I agree the hardest part for me was on windows trying to get the stupid drivers to work correctly.
Dumped windows for Linux and followed the manual steps i found on XDA and never looked back.
No drivers needed in Linux either.

TheSkillfulTroll said:
some people here are wrong, will it wipe data? for the first time (when unlocking the OEM) yes. Lollipop now has a different way to check ROOTING, once it detects you modified ANY file in the system core files, it aborts. To work around this, either use a ROM and upgrade via FLASHING (which i do) or use NEXUS ROOT TOOLKIT. Using the toolkit (which is very noob friendly) allows everything to be done by a click. BUT, to upgrade via toolkit, (ota) you need to flash stock which in the toolkit completely wipe system, then unroot, then update, then reroot and flash whatever ROM you want, which would again wipe your device. the way i do it is easier, it requires no wiping and i get to keep my ROM at all times and i get earlier versions (depending on ROM creators) then OTA, i currently have 5.0.2 on my nexus 6, which isnt ven out yet OTA. :fingers-crossed:
Click to expand...
Click to collapse
Yes, this is my main concern. Back in my Samsung days, i remember flashing ROMs everyday, but the whole wiping got really annoying. When i got my Nexus 5 i just kept it stock. Now I do want to root to use the double tap to wake and the LED, but i don't want to wipe everytime there's an update. From what I remember, whenever you flash a ROM you have to wipe the phone. So is there a way around having to wipe your phone completely everytime there's an update?

miike1106 said:
Yes, this is my main concern. Back in my Samsung days, i remember flashing ROMs everyday, but the whole wiping got really annoying. When i got my Nexus 5 i just kept it stock. Now I do want to root to use the double tap to wake and the LED, but i don't want to wipe everytime there's an update. From what I remember, whenever you flash a ROM you have to wipe the phone. So is there a way around having to wipe your phone completely everytime there's an update?
Click to expand...
Click to collapse
Say you flashed SimpleAosp which is currently 5.0.2, whenever 5.0.3 comes out you need to Download it on your phone, open flashify and boot into TWRP, in there you need click install then DONT WIPE, find the updated version and flash over the current one, reboot and bam, you have new version and you didn't lose anything. Only do this method if you are transition from the same ROM to a new one, if you decided to go from SimpleAosp to liquidsmooth you need to wipe.
Sent from my Nexus 6 using XDA Free mobile app

TheSkillfulTroll said:
Say you flashed SimpleAosp which is currently 5.0.2, whenever 5.0.3 comes out you need to Download it on your phone, open flashify and boot into TWRP, in there you need click install then DONT WIPE, find the updated version and flash over the current one, reboot and bam, you have new version and you didn't lose anything. Only do this method if you are transition from the same ROM to a new one, if you decided to go from SimpleAosp to liquidsmooth you need to wipe.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Ah ok, this is what i was looking for.

miike1106 said:
Ah ok, this is what i was looking for.
Click to expand...
Click to collapse
Or... You could live dangerously and try a dirty flash first every time... Worst case... You go back and wipe in recovery

miike1106 said:
Yes, this is my main concern. Back in my Samsung days, i remember flashing ROMs everyday, but the whole wiping got really annoying. When i got my Nexus 5 i just kept it stock. Now I do want to root to use the double tap to wake and the LED, but i don't want to wipe everytime there's an update. From what I remember, whenever you flash a ROM you have to wipe the phone. So is there a way around having to wipe your phone completely everytime there's an update?
Click to expand...
Click to collapse
You can dirty flash but this is only the case when you update from the same ROM to a newer update of the version.
When we say wipe, it only wipes the OS not internal storage.

Nexus 6 coming tomorrow

Guys I just have a question,
I will be receiving my nexus 6 tomorrow and I plan on unlocking the boot loader and rooting it, but what I am curious about from reading all the threads is a few things.
1) I plan on using adb to unlock boot loader and root
2) I plan on using flashify to install twrp so i can be able to get a backup of the stock recovery
My question is this. I plan on installing cm12 on my device and i like the idea of having my device descrpyted. I am told I have to flash the script I believe made by chainfire, but i also read u can flash another kernel. Which would i have to do? I read some say that u have to do the one made by chainfire first, and others said u just have to flash another kernel.
Also since the cm12 comes encrypted as default and lets say I "dont" want to descrypt do I have to before I flash cm12 even though its set as default encrpyted just like stock?

the_rooter said:
1) I plan on using adb to unlock boot loader and root
2) I plan on using flashify to install twrp so i can be able to get a backup of the stock recovery
Click to expand...
Click to collapse
1) You'll need to use fastboot to unlock the bootloader. YOu'll then need to use fastboot to flash the recovery. If you're going to flash a rom, you may not need to then root as some roms are already rooted
2) flashify needs root to flash the recovery and you need the recovery to flash root.

What chain fire thing? Chain fire doesn't have anything in relation to encryption from what I know. Go to Android development and find the unencrypt thread and from there you'll find out how to unencrypt.
Do note that your data will be wiped. You'll have to flash a custom kernel before your phone starts up otherwise your phone will be encrypted again.
Most custom kernels have encryption patches to accelerate the encryption i/o speeds. You're better off just leaving it enabled if you want to keep things simple.
Sent from my Nexus 6 using Tapatalk

rootSU said:
1) You'll need to use fastboot to unlock the bootloader. YOu'll then need to use fastboot to flash the recovery. If you're going to flash a rom, you may not need to then root as some roms are already rooted
2) flashify needs root to flash the recovery and you need the recovery to flash root.
Click to expand...
Click to collapse
If i remember from previous devices doesnt flashify allow backup of the stock recovery? and also it flashes twrp within the app as long as root is done.
Edit:
Also I wasnt sure who made the descrypt file to flash, and yes i know it does a FDR, but wouldnt it be better just to flash a custom kernel? Most kernels are already descrypted. Sorry if i repeated anything.

the_rooter said:
If i remember from previous devices doesnt flashify allow backup of the stock recovery? and also it flashes twrp within the app as long as root is done.
Click to expand...
Click to collapse
Yes, but you wont have root at that point so, no...

rootSU said:
Yes, but you wont have root at that point so, no...
Click to expand...
Click to collapse
i am honestly not trying to pick a fight and i thank you for taking your time to help me out but if i follow this thread:
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
That gives me root via fastboot up to the end of obtaining root and not doing custom recovery.
Within flashify i know u can back up the stock recovery, and then flash twrp. After i flash twrp i will be making a back up of my system just in case something goes wrong.
That sound correct? I prolly will give a few days and wait till my usb otg sd adapter to get here before i actually flash a rom. Sorry should have mentioned that.

the_rooter said:
i am honestly not trying to pick a fight and i thank you for taking your time to help me out but if i follow this thread:
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
That gives me root via fastboot up to the end of obtaining root and not doing custom recovery.
Within flashify i know u can back up the stock recovery, and then flash twrp. After i flash twrp i will be making a back up of my system just in case something goes wrong.
That sound correct? I prolly will give a few days and wait till my usb otg sd adapter to get here before i actually flash a rom. Sorry should have mentioned that.
Click to expand...
Click to collapse
That uses a script to flash root... But lets break down your steps...
fastboot unlock
run script
boot into android
install flashify
flash recovery
Download rom
reboot recovery
flash rom
vs my steps...
fastboot unlock
fastboot flash recovery
put rom on sdcard
flash rom
It doesnt matter if you backup your stock recovery, because its all available on the google site anyway as this is a nexus device.

rootSU said:
That uses a script to flash root... But lets break down your steps...
fastboot unlock
run script
boot into android
install flashify
flash recovery
Download rom
reboot recovery
flash rom
vs my steps...
fastboot unlock
fastboot flash recovery
put rom on sdcard
flash rom
It doesnt matter if you backup your stock recovery, because its all available on the google site anyway as this is a nexus device.
Click to expand...
Click to collapse
thanks man that helps alot. Now still on the confusing about the encrypt and decrypt. Whats the advantages to disadvantages? because from what i here people say it should be decrpyted, and that i have to follow the step set up in that thread to do so, but wouldnt like i said before just be as easier to just flash a decrpyted kernel and be done with it?
Edit: Sorry with all the questions this is my first nexus device since i am on verizon.

the_rooter said:
thanks man that helps alot. Now still on the confusing about the encrypt and decrypt. Whats the advantages to disadvantages? because from what i here people say it should be decrpyted, and that i have to follow the step set up in that thread to do so, but wouldnt like i said before just be as easier to just flash a decrpyted kernel and be done with it?
Edit: Sorry with all the questions this is my first nexus device since i am on verizon.
Click to expand...
Click to collapse
Do some reading off XDA on what encryption is and its advantages/disadvantages.
To be simplistic,
Encryption pro: more protection with your data
Encryption disadvantage: slower I/O speed
(Most custom kernels include patches that accelerate the speed of I/O with encryption on, Google's stock kernel does not include this)
Decryption pro: faster I/O speeds, possible increase in battery life as your phone is not using clock cycles to perform encryption (not by much, if any)
Decrypton disadvantage: less protection with your data, but if you're not carrying sensitive data, then who cares.
My suggestion to you is to leave it encrypted and if you don't notice anything slowing down then leave it. Keep it simple.

zephiK said:
Do some reading off XDA on what encryption is and its advantages/disadvantages.
To be simplistic,
Encryption pro: more protection with your data
Encryption disadvantage: slower I/O speed
(Most custom kernels include patches that accelerate the speed of I/O with encryption on, Google's stock kernel does not include this)
Decryption pro: faster I/O speeds, possible increase in battery life as your phone is not using clock cycles to perform encryption (not by much, if any)
Decrypton disadvantage: less protection with your data, but if you're not carrying sensitive data, then who cares.
My suggestion to you is to leave it encrypted and if you don't notice anything slowing down then leave it. Keep it simple.
Click to expand...
Click to collapse
Thanks for you help guys. With this being my first nexus phone i think i understand now.

the_rooter said:
Thanks for you help guys. With this being my first nexus phone i think i understand now.
Click to expand...
Click to collapse
Once a Nexus you won't go back Nexus devices are the devices to be on XDA, traffic is a lot higher here than the other phones.

zephiK said:
Once a Nexus you won't go back Nexus devices are the devices to be on XDA, traffic is a lot higher here than the other phones.
Click to expand...
Click to collapse
well yeah but like i said i am on big red and this is the first nexus device they are allowing since the gnex days

Bricked Nexus 6

Hi guys -
I'm somewhat a newbie here. I think I have bricked my Nexus 6. I had root and an unlocked bootloader. I had Chroma riom installed and was trying to go back to stock rom, unrooted with locked bootloader and through TWRP i deleted everything, including the OS I believe. So now my phone is locked on the Google startup screen (unlocked bootloader) . Suggestions?
Thanks -
John

if your bootloader is unlocked you should be able to fastboot clear cache and user data , then flash a rom from twrp. I would refrain from ever locking the bootloader back up since the update where you have to enable unlock bootloader in Dev Options.

droidstyle said:
if your bootloader is unlocked you should be able to fastboot clear cache and user data , then flash a rom from twrp. I would refrain from ever locking the bootloader back up since the update where you have to enable unlock bootloader in Dev Options.
Click to expand...
Click to collapse
me too I'm have Nexus 6 5.1.1 no recovery...except the bootloader that's locked Code: 2 , i can't unlock it, any solution !!?

hadifreestyler said:
me too I'm have Nexus 6 5.1.1 no recovery...except the bootloader that's locked Code: 2 , i can't unlock it, any solution !!?
Click to expand...
Click to collapse
no you are bricked unfortunately. the unlock bootlader option in dev options really seems to have caused more issues then good.
I am wondering if Jtag will fix these devices?

jpl81905 said:
Suggestions?
Click to expand...
Click to collapse
Stop.
Read.
A lot.
You have an unlocked nexus with custom recovery installed, and you don't know what to do? You shouldn't be messing with this stuff. You lack VERY basic understanding. Read the stickies.
https://developers.google.com/android/nexus/images?hl=en
Factory images. Follow their directions.

scryan said:
Stop.
Read.
A lot.
You have an unlocked nexus with custom recovery installed, and you don't know what to do? You shouldn't be messing with this stuff. You lack VERY basic understanding. Read the stickies.
https://developers.google.com/android/nexus/images?hl=en
Factory images. Follow their directions.
Click to expand...
Click to collapse
Thank you. I think.

jpl81905 said:
Hi guys -
I'm somewhat a newbie here. I think I have bricked my Nexus 6. I had root and an unlocked bootloader. I had Chroma riom installed and was trying to go back to stock rom, unrooted with locked bootloader and through TWRP i deleted everything, including the OS I believe. So now my phone is locked on the Google startup screen (unlocked bootloader) . Suggestions?
Thanks -
John
Click to expand...
Click to collapse
The easiest way if you are not familiar with ADB is to download the nexus tool kit located on these forums from WUGFRESH. That tool will walk you through a step by step process on how to flash stock back. You are far from bricked. I have deleted my entire phone many a times and just re flashed stock back easily. As long as your boot loader is unlocked you are fine
Link to toolkit: http://www.wugfresh.com/nrt/
The option you are going to want to use is on the front of the toolkit called flash stock + un-root. You can watch some videos on his website as well for flashing stock. That is all you need to do .
Any questions let me know, send me a PM

backdown00 said:
The easiest way if you are not familiar with ADB is to download the nexus tool kit located on these forums from WUGFRESH. That tool will walk you through a step by step process on how to flash stock back. You are far from bricked. I have deleted my entire phone many a times and just re flashed stock back easily. As long as your boot loader is unlocked you are fine
Link to toolkit: http://www.wugfresh.com/nrt/
The option you are going to want to use is on the front of the toolkit called flash stock + un-root. You can watch some videos on his website as well for flashing stock. That is all you need to do .
Any questions let me know, send me a PM
Click to expand...
Click to collapse
It is not the easiest option. The easiest option is plug the USB cable in, boot to TWRP, enable MTP mode and copy a rom to the sdcard.
Also, many senior members here will discourage the use of toolkits for those who are not familiar with adb or fastboot. It is best to learn these and use them at least once before starting to use toolkits. Toolkits do not "walk you through". They take you through without explaining anything.

danarama said:
It is not the easiest option. The easiest option is plug the USB cable in, boot to TWRP, enable MTP mode and copy a rom to the sdcard.
Also, many senior members here will discourage the use of toolkits for those who are not familiar with adb or fastboot. It is best to learn these and use them at least once before starting to use toolkits. Toolkits do not "walk you through". They take you through without explaining anything.
Click to expand...
Click to collapse
In a perfect world, I am sure we would all love to dive in and discover everything and be experts in all fields as time would not be a factor. I do not disagree it is helpful to learn ADB and fastboot commands and understand what they do. At this point in time though, the end goal here is to get his phone back up and running as fast as possible and then he can do the post-mortem to figure out what he did wrong and how to fix it .
I am guessing hes not very familiar with TWRP since he wound up in this situation. The toolkit alleviates the need for knowledge and gets the job done. I'm sure after this, the OP will research how to use his phone before trying to do anything next.

backdown00 said:
In a perfect world, I am sure we would all love to dive in and discover everything and be experts in all fields as time would not be a factor. I do not disagree it is helpful to learn ADB and fastboot commands and understand what they do. At this point in time though, the end goal here is to get his phone back up and running as fast as possible and then he can do the post-mortem to figure out what he did wrong and how to fix it .
I am guessing hes not very familiar with TWRP since he wound up in this situation. The toolkit alleviates the need for knowledge and gets the job done. I'm sure after this, the OP will research how to use his phone before trying to do anything next.
Click to expand...
Click to collapse
..but even so, your method is overkill. It is really simple to boot into TWRP and look in the menu for the "Enable MTP" option. Once that is done, the phone appears in "Computer" as an MTP device, just like when you boot into android. Then, simply dragging and dropping a ROM onto that device then flashing it via recovery will get him back up and running. There is nothing simpler or quicker than this.
Sorry, I do not intend to be confrontational here.