Database Develop

How to REMOVE Sprint Hands Free Activation Setup!!!

through much trial and error, I am now "Activation Screen" Free.
Here is a list of what to do:
Download "root uninstaller" from Play store..(the version you need shows an Android Icon)
Use it to remove ALL Sprint related processes/APK's
Reboot your phone
This worked on mine, hope it works on yours.
Mine is rooted, s-off, TWRP flashed, and Custom "Bad Boys" Rom

Nice! Good job brother! Thanks for contributing to XDA

LOL
Sent from my HTC One using Tapatalk

pitbull8265 said:
through much trial and error, I am now "Activation Screen" Free.
Here is a list of what to do:
Download "root uninstaller" from Play store..(the version you need shows an Android Icon)
Use it to remove ALL Sprint related processes/APK's
Reboot your phone
This worked on mine, hope it works on yours.
Mine is rooted, s-off, TWRP flashed, and Custom "Bad Boys" Rom
Click to expand...
Click to collapse
All you need to do is delete "htcsetupwizard.apk" in system apps folder. If you don't want to wait until the setup wizard lets you into the system follow these directions.
1. Boot into recovery
2. Mount system
3. Use file manager to get to system/apps and delete "htcsetupwizard.apk"
4. Unmount system
5. Wipe dalvic
6. Reboot to system
7. Pick your butt and sniff your finger.
On second thought you can skip step 7 if you want to but that's entirely up to you.
Sent from my HTCONE using XDA Premium 4 mobile app

I am not able to get past the activation screen after I flash a ROM. Tell me what to do. Also OP could you please provide me with a list of files that need to be deleted?

shantanil said:
I am not able to get past the activation screen after I flash a ROM. Tell me what to do. Also OP could you please provide me with a list of files that need to be deleted?
Click to expand...
Click to collapse
Don't follow the OP's directions, just follow the method listed right above your question.
Sent from my SM-N900P using XDA Premium 4 mobile app

shantanil said:
I am not able to get past the activation screen after I flash a ROM. Tell me what to do. Also OP could you please provide me with a list of files that need to be deleted?
Click to expand...
Click to collapse
I had it hanging on activation after installing BadBoyz kitkat rom. I installed the newest Radio from Dec. rebooted, and didn't get hands free activation again at all.

Robert542 said:
All you need to do is delete "htcsetupwizard.apk" in system apps folder. If you don't want to wait until the setup wizard lets you into the system follow these directions.
1. Boot into recovery
2. Mount system
3. Use file manager to get to system/apps and delete "htcsetupwizard.apk"
4. Unmount system
5. Wipe dalvic
6. Reboot to system
7. Pick your butt and sniff your finger.
On second thought you can skip step 7 if you want to but that's entirely up to you.
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've tried this, but still does work, any way to get rid of this annoying thing?
Rooted Stock 4.4
Edit: A few questions to ask.
I am able to bypass HFA, but I had to delete the .apks associated with what ever makes it happen.
When I install a ROM I always encounter HFA*makes me not want to install others, since I set-up the ones I use now so I don't encounter it*.
Are devs just implenting this cause of it's sprint branding, I understand why they would ,but crap is annoying.
Anyways, I'm reluctant to remove it, but it gets quite annoying when installing a rom it so happens to rear it's ugly head.

Robert542 said:
Don't follow the OP's directions, just follow the method listed right above your question.
Click to expand...
Click to collapse
I followed those instructions too, well except #7, tempting as it is. No dice. HFA, pops back up again. I'm rooted, but am afraid the nasty HFA will muck up my Fire water S - Off process. Any other ideas?

v1ral said:
I've tried this, but still does work, any way to get rid of this annoying thing?
Rooted Stock 4.4
Edit: A few questions to ask.
I am able to bypass HFA, but I had to delete the .apks associated with what ever makes it happen.
Click to expand...
Click to collapse
Which apks did you delete/rename to disable it? I have been renaming quite a few with no luck. Are there more than one app that can run HFA?
Edit: Found the answer... http://forum.xda-developers.com/showpost.php?p=50392144&postcount=2287

Activation disable
If you use Rom Toolbox or any other rooted App Manager App, just remove Setup Wizard, and Self Service

shantanil said:
I am not able to get past the activation screen after I flash a ROM. Tell me what to do. Also OP could you please provide me with a list of files that need to be deleted?
Click to expand...
Click to collapse
bro finaly wat u hav done?

Titanium Backup>>>Remove file vHTC DM.

Robert542 said:
All you need to do is delete "htcsetupwizard.apk" in system apps folder. If you don't want to wait until the setup wizard lets you into the system follow these directions.
1. Boot into recovery
2. Mount system
3. Use file manager to get to system/apps and delete "htcsetupwizard.apk"
4. Unmount system
5. Wipe dalvic
6. Reboot to system
7. Pick your butt and sniff your finger.
On second thought you can skip step 7 if you want to but that's entirely up to you.
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi Robert, this problem strikes me recently. I just purchased a HTC 10 Sprint outside of the States (Vietnam to be exact), unlocked bootloader, S-off, install latest twrp, and finally flashed ICE 3.6.0 on it.
Everything run smoothly until I got to the 1st setup process, after choosing language, there is HFA and my phone could not activate and I stuck there forever.
I lets it run 5 times, didn't do the trick. I tried to delete htcsetupwizard.apk as you said but could not find it either. I googled around and ppl tell me to delete HtcOMADM_SPCS.apk but it still did not do the trick.
I tried to flash ROM several times again (the same one) with different Magisk & SuperSU but still same sh!t.
Could you please help out?

sirius_black_9h said:
Hi Robert, this problem strikes me recently. I just purchased a HTC 10 Sprint outside of the States (Vietnam to be exact), unlocked bootloader, S-off, install latest twrp, and finally flashed ICE 3.6.0 on it.
Everything run smoothly until I got to the 1st setup process, after choosing language, there is HFA and my phone could not activate and I stuck there forever.
I lets it run 5 times, didn't do the trick. I tried to delete htcsetupwizard.apk as you said but could not find it either. I googled around and ppl tell me to delete HtcOMADM_SPCS.apk but it still did not do the trick.
I tried to flash ROM several times again (the same one) with different Magisk & SuperSU but still same sh!t.
Could you please help out?
Click to expand...
Click to collapse
Root your phone. Install any decent root app remover from play store. Search in its system apps for the keyword "sprint". And see what happens after removing them.
The problem is that HTC has put this service with different names on different models. So the same name may not be applicable for every model. So finally its a hit and trial.

Android L Developer Preview Install in 13 Easy Steps

Hi everyone,
there are obviously tons of Android L threads already, but I wanted to post simple instructions for getting the developer preview up and running and also back to your previous version.
Without talking much more, here are the steps...
1. Make sure you have a custom recovery installed (I suggest TWRP 2.7.0.0 or higher, I did not test with CWM so caution for those users)
2. Make a full nandroid backup (System, Data, Boot) of your current system. After the backup completes, restart your device and copy the nandroid backup file to your PC. (The file should be located in the TWRP/Backup section of your device)
3. Make sure you have Android SDK installed, https://developer.android.com/sdk/index.html (Open SDK Manager and check off Android SDK tools, platform-tools, and build-tools as well as the entire section of Android L. Click Install packages and make sure that all of those files install)
4. Download and extract the Developer Package from here http://developer.android.com/preview/setup-sdk.html#top (the download link is under step 1 in the "Install the L Preview System image" section)
5. Place the extracted Developer Package files into your platform-tools folder of your SDK folder location
7. Boot your device into fastboot mode by powering off and then powering back up by holding Volume Up + Down + Power (Let the device stay in this mode during the entire process)
8. Open command prompt and type "chdir (copy and paste the file directory of your platform-tools folder here)"
9. Type "adb start-server" this is just to ensure adb is running. Then, while still in the directory of your platform-tools folder, type "flash-all" (You may get errors with it unable to flash some ".sig" files, but that is ok. (After the files flash, your phone will automatically reboot to the boot animation, if you are on this screen for a while, just be patient. The first boot takes quite a while do to the change to ART)
Your phone should now be running on Android L. The next steps will be for returning back to your previous install, while also backing up Android L and being able to switch between the 2. Installing Android L deletes your custom recovery that you had and replaces it with a stock one. In order to make backups and return to your previous system, you must reinstall TWRP or CWM which is explained below.
10. You can install TWRP simply by using the Nexus Root Toolkit by WugFresh XDA Thread: http://forum.xda-developers.com/showthread.php?t=1766475 Mirror: http://www.softpedia.com/get/Mobile-Phone-Tools/Others/Galaxy-Nexus-Root-Toolkit.shtml (Open the Toolkit and click Launch under Advanced Utilities. Then, under Boot/Flash Image click the Flash (Permanent) radio and click recovery. Select latest TWRP and follow the instructions.
11. After TWRP installs, make a backup of your current system (Android L)
12. Reboot your device, when powered up, place your first backup that you made (Before "L") into your TWRP/Backups folder.
13. Now in TWRP you have both your L backup and your old backup. You can restore either and then switch between the 2.
14. Enjoy (Give thanks if this helped you) Thank you!!

Out of curiosity can we do multiboot with stock 4.4.4 and Android "L"? Any one tried?
Sent from my Nexus 5 using XDA Free mobile app

I am unsure of that especially because of the differences in radios and such. That's why I like this method because it's probably the closest I know how to get to it.
monilchheda said:
Out of curiosity can we do multiboot with stock 4.4.4 and Android "L"? Any one tried?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse

Hmm. Thanks
Sent from my Nexus 5 using XDA Free mobile app

My only question to @bcollado is why not just do fastboot flash recovery command for TWRP?! Faster than using a tool kit.

the.emilio said:
My only question to @bcollado is why not just do fastboot flash recovery command for TWRP?! Faster than using a tool kit.
Click to expand...
Click to collapse
some people dont know how to do things the right way. many think that root toolkits are easier and faster(when, for any nexus, they are not).

simms22 said:
some people dont know how to do things the right way. many think that root toolkits are easier and faster(when, for any nexus, they are not).
Click to expand...
Click to collapse
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-2.0.50.2.08.img
fastboot reboot-bootloader
fastboot -w update image-hammerhead-lpv79.zip
there you have "L". lol

I just figured this guide is aimed towards those who wouldn't know how to do that, obviously it can be done either way, but I assumed if you knew to do it manually, that you could choose to do it that way.
the.emilio said:
My only question to @bcollado is why not just do fastboot flash recovery command for TWRP?! Faster than using a tool kit.
Click to expand...
Click to collapse

Can anyone check to see if they have the Gallery? I had to download QuickPic to view my stuff. But I'm thinking maybe its with Picasa photos app but I removed it from my screen and now I can't find that app.. Can anyone help please. I don't like using 3rd party apps if I already have one working just fine.. Thank you.
Sent from my Nexus 5

Not the place to ask...but gallery is currently not in the developer preview and might be taken out of android when the release gets finalized, but no one knows. Right now the "Photos" app is included and thats basically the new gallery for now at least
noodles2224 said:
Can anyone check to see if they have the Gallery? I had to download QuickPic to view my stuff. But I'm thinking maybe its with Picasa photos app but I removed it from my screen and now I can't find that app.. Can anyone help please. I don't like using 3rd party apps if I already have one working just fine.. Thank you.
Sent from my Nexus 5
Click to expand...
Click to collapse

bcollado said:
I just figured this guide is aimed towards those who wouldn't know how to do that, obviously it can be done either way, but I assumed if you knew to do it manually, that you could choose to do it that way.
Click to expand...
Click to collapse
If they don't know how to do that, why the hell are they flashing the developer preview image? 99% of users are already taking the developer preview as a consumer release, and that is NOT what it is meant for.
If you don't know how to do it - then it's not damn meant for you.

I hate that attitude....I agree that people need to understand that it's not a consumer release. I 100% agree with that, but that doesn't mean people who don't know how shouldn't be able to check out the new features if they want, just because they don't know how. This is the whole point of this thread...so people can check out the new features on "L" and then go right back to where they were with no issues...please no more flaming on the fact that if people don't know how then they shouldn't, not on this thread anyway
Lethargy said:
If they don't know how to do that, why the hell are they flashing the developer preview image? 99% of users are already taking the developer preview as a consumer release, and that is NOT what it is meant for.
If you don't know how to do it - then it's not damn meant for you.
Click to expand...
Click to collapse

bcollado said:
I agree that people need to understand that it's not a consumer release. I 100% agree with that, but that doesn't mean people who don't know how shouldn't be able to check out the new features if they want, just because they don't know how.
Click to expand...
Click to collapse
That's a little bit of contradiction, don't you think?

Lethargy said:
That's a little bit of contradiction, don't you think?
Click to expand...
Click to collapse
Not at all...anyone who wants should be able to view new features, they just have to understand that it's not a final release and that it isn't meant to be used as such. Anyone who doesn't know how to do something and is brave enough to risk it and attempt to, deserves to learn

bcollado said:
Not at all...anyone who wants should be able to view new features, they just have to understand that it's not a final release and that it isn't meant to be used as such. Anyone who doesn't know how to do something and is brave enough to risk it and attempt to, deserves to learn
Click to expand...
Click to collapse
Unfortunately that isn't how it actually happens.. we wish it did, but it doesn't. As I said previously, 99% that are using it are already taking it as a "consumer release", most don't even know how to flash the .img files in fastboot and are just using a flashable zip.. not even doing it properly as it should be.

One question, can I dirty flash over 4.4.4 ??

onesolo said:
One question, can I dirty flash over 4.4.4 ??
Click to expand...
Click to collapse
You can, but it breaks things such as the lockscreen. I don't know what exactly breaks, but reading from the thread in General a bunch of things do. I recommend a proper clean flash.

onesolo said:
One question, can I dirty flash over 4.4.4 ??
Click to expand...
Click to collapse
you can. but i would not until i would make a backup in recovery. and the same for you. if you dirty flash, and have issues, you can always restore the backup and flash again with a wipe
---------- Post added at 07:12 PM ---------- Previous post was at 07:11 PM ----------
Lethargy said:
You can, but it breaks things such as the lockscreen. I don't know what exactly breaks, but reading from the thread in General a bunch of things do. I recommend a proper clean flash.
Click to expand...
Click to collapse
:silly:

sure, I never flash a thing without first make a full backup...
I also forgot to ask, after I flash, does this wipe my sdcard??

onesolo said:
sure, I never flash a thing without first make a full backup...
I also forgot to ask, after I flash, does this wipe my sdcard??
Click to expand...
Click to collapse
no, not if you dont wipe it. but i have read today of some people having issues of the phone seeing the storage. then they flashed back, and the storage was visable again.

[Q] Updating 5.0 to 5.1

Just a quick question. How would one update from 5.0.1 to 5.1 if they are on stock rooted rom with a few tweaks such as volume mod, hotspot enabled, and show percentage mod? I guess I am more worried about erasing everything and then re-installing.
Thanks

stas333 said:
Just a quick question. How would one update from 5.0.1 to 5.1 if they are on stock rooted rom with a few tweaks such as volume mod, hotspot enabled, and show percentage mod? I guess I am more worried about erasing everything and then re-installing.
Thanks
Click to expand...
Click to collapse
Flash the stock system.img to remove root. If you are unencrypted, flash the stock boot.img. And if you have TWRP, flash the stock recovery.img.
This is if you want to take the OTA. Or you can wait until someone makes a flashable zip.
Instructions are here, under Method 2 (only flash those files I noted above. No need to flash all of them.) > http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

cam30era said:
Flash the stock system.img to remove root. If you are unencrypted, flash the stock boot.img. And if you have TWRP, flash the stock recovery.img.
This is if you want to take the OTA. Or you can wait until someone makes a flashable zip.
Instructions are here, under Method 2 > http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
Thanks

cam30era said:
Flash the stock system.img to remove root. If you are unencrypted, flash the stock boot.img. And if you have TWRP, flash the stock recovery.img.
This is if you want to take the OTA. Or you can wait until someone makes a flashable zip.
Instructions are here, under Method 2 > http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
Just to correct what may be an error here...
If you are unencrypted and flash the stock boot.img, you will be encrypted on boot. So if you are unencrypted and wish to remain so, it would make sense to flash immediately whatever custom kernel you use to not force encryption.
But IMHO this is pretty much the best way as stated.
Flash system.img, boot.img and radio.img via fastboot individually, flash root (SuperSU) from recovery and boot. No wipes etc.

If you're going to follow method 2, you might as well just do it straight with the 5.1 image and call it good.

So just going from stock rooted 5.0.1 to stock rooted 5.1 is the factory reset needed? I know in the past it wouldn't have been, but lollipop changed a lot with this stuff so I'm not sure.

Can't we simply sideload the update using Wugfresh or something and re-root? I have taken OTAs on my OnePlus One and all it does is remove root. I don't understand why I'd have to completely reinstall and wipe just to take an OTA.

greyhulk said:
Can't we simply sideload the update using Wugfresh or something and re-root? I have taken OTAs on my OnePlus One and all it does is remove root. I don't understand why I'd have to completely reinstall and wipe just to take an OTA.
Click to expand...
Click to collapse
You cannot sideload an OTA on lollipop if you have modified anything in system, including adding root. We also discourage using toolkits for those who do not understand how to do the steps without one, because when those people get stuck and need help, we cant simply help and give instructions.. We have to teach them EVERYTHING they didn't bother to learn first - which is a result of using toolkits as shortcuts instead of as aids to existing knowledge

TriBeard said:
So just going from stock rooted 5.0.1 to stock rooted 5.1 is the factory reset needed? I know in the past it wouldn't have been, but lollipop changed a lot with this stuff so I'm not sure.
Click to expand...
Click to collapse
If you fastboot flash the stock system.img, you will be good to install the OTA, with no factory reset necessary. But EVERYTHING must be stock. Recovery, and encrypted kernel/boot.img.
---------- Post added at 01:19 PM ---------- Previous post was at 01:16 PM ----------
greyhulk said:
Can't we simply sideload the update using Wugfresh or something and re-root? I have taken OTAs on my OnePlus One and all it does is remove root. I don't understand why I'd have to completely reinstall and wipe just to take an OTA.
Click to expand...
Click to collapse
If your phone is back to 100% stock (everything, including recovery and encrypted kernel/boot.img), then you can ADB sideload the OTA. But be sure to do some research, so you know what you are doing.

Not to be rude to the veterans (I too know how to flash things manually) but you guys do realize the wug fresh toolkit does have an option to flash stock without wiping right?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

cam30era said:
If you fastboot flash the stock system.img, you will be good to install the OTA, with no factory reset necessary. But EVERYTHING must be stock. Recovery, and encrypted kernel/boot.img.
---------- Post added at 01:19 PM ---------- Previous post was at 01:16 PM ----------
If your phone is back to 100% stock (everything, including recovery and encrypted kernel/boot.img), then you can ADB sideload the OTA. But be sure to do some research, so you know what you are doing.
Click to expand...
Click to collapse
so basically you could flash the stock 5.0.1 system.img, take the update, then root again (assuming the root method doesn't change, or using a new method after one is found?)

TriBeard said:
so basically you could flash the stock 5.0.1 system.img, take the update, then root again (assuming the root method doesn't change, or using a new method after one is found?)
Click to expand...
Click to collapse
Yes, assuming you have stock recovery and are encrypted.

cam30era said:
Yes, assuming you have stock recovery and are encrypted.
Click to expand...
Click to collapse
Yeah, all I did was unlock the bootloader and run one of the automated rooting things, I think from chainfire, but I could be wrong. I didn't mess with unencryption or custom recoveries (yet).

Rooting is so easy. It requires one fastboot command after you're bootloader is unlocked(either to flash a recovery or boot into recovery temporarily) then you just use the SuperSU zip and boom you're rooted. That's why I love Nexus phones so much.

rootSU said:
You cannot sideload an OTA on lollipop if you have modified anything in system, including adding root. We also discourage using toolkits for those who do not understand how to do the steps without one, because when those people get stuck and need help, we cant simply help and give instructions.. We have to teach them EVERYTHING they didn't bother to learn first - which is a result of using toolkits as shortcuts instead of as aids to existing knowledge
Click to expand...
Click to collapse
Not trying to start and arguement but toolkits are here to help for people with busy lives. I know how to do both methods, but using a toolkit isnt all bad if directions are followed. Just about every device out there has some kind of toolkit similiarities.
nexus has its own toolkit, htc 1 m8 has a paid software that unlocks the device, heck even the newest moto E has a toolkit. Just because there are some developers on here that dont like toolkits doesnt mean they are bad. I agree though if people mess up bad and screwed up using a toolkit thats not the toolkits fault. Its user error. Toolkits are a good thing to use if used properly. I encourage everyone I know to use toolkits. I also make sure to tell them to read it twice then go.
---------- Post added at 02:59 PM ---------- Previous post was at 02:58 PM ----------
TriBeard said:
so basically you could flash the stock 5.0.1 system.img, take the update, then root again (assuming the root method doesn't change, or using a new method after one is found?)
Click to expand...
Click to collapse
what root method for nexus? all you have to do is flash custom recovery and then flash supersu within recovery and your good

the_rooter said:
Not trying to start and arguement but toolkits are here to help for people with busy lives. I know how to do both methods, but using a toolkit isnt all bad if directions are followed. Just about every device out there has some kind of toolkit similiarities.
nexus has its own toolkit, htc 1 m8 has a paid software that unlocks the device, heck even the newest moto E has a toolkit. Just because there are some developers on here that dont like toolkits doesnt mean they are bad. I agree though if people mess up bad and screwed up using a toolkit thats not the toolkits fault. Its user error. Toolkits are a good thing to use if used properly. I encourage everyone I know to use toolkits. I also make sure to tell them to read it twice then go.
---------- Post added at 02:59 PM ---------- Previous post was at 02:58 PM ----------
what root method for nexus? all you have to do is flash custom recovery and then flash supersu within recovery and your good
Click to expand...
Click to collapse
Like i said, its fine if you know both methods.
I don't care if someone has a busy life or not. If they don't have time to spend 10 minutes reading and following my fastboot thread, well they shouldn't really be rooting. Further more, how selfish is it for someone who thinks they're too busy to learn the basics to then have to fall back on other people who may also have busy lives for hand holding through something that should be simple just because they wanted to take a small shortcut to save them 3 minutes? Learn the basics and then you don't waste our time trying to not only help you but also teach the basics - which are essentials.
My point isn't that toolkits break things (although sometimes they do) or even user error using the toolkit... My point is if something else unrelated goes wrong and we say "fastboot flash x to fix" and they then reply " what's fastboot?" And then we have to teach the basics whilst they're frustrated and panicking. That is NOT the best time to learn... Or teach
Driving a car requires a licence. Sure, you can fake a licence but I don't want to have to explain what a car is if you need me to tell you how to start the car. Especially not whilst you're late for a job interview

rootSU said:
Like i said, its fine if you know both methods.
I don't care if someone has a busy life or not. If they don't have time to spend 10 minutes reading and following my fastboot thread, well they shouldn't really be rooting. Further more, how selfish is it for someone who thinks they're too busy to learn the basics to then have to fall back on other people who may also have busy lives for hand holding through something that should be simple just because they wanted to take a small shortcut to save them 3 minutes? Learn the basics and then you don't waste our time trying to not only help you but also teach the basics - which are essentials.
My point isn't that toolkits break things (although sometimes they do) or even user error using the toolkit... My point is if something else unrelated goes wrong and we say "fastboot flash x to fix" and they then reply " what's fastboot?" And then we have to teach the basics whilst they're frustrated and panicking. That is NOT the best time to learn... Or teach
Driving a car requires a licence. Sure, you can fake a licence but I don't want to have to explain what a car is if you need me to tell you how to start the car. Especially not whilst you're late for a job interview
Click to expand...
Click to collapse
So your saying if no one uses your fastboot method thread that they are in the wrong. I understand and agree that all users should learn fastboot, but to push your thread on everyone and then to say they shouldnt root at all if they dont is selfish. Theres always more than one method to do a task. Just because one is easier than the other doesn't make it bad.
best example and this still irks me is I knew a developer that had a thread for the ruu on the m8. he found out if you flash it twice(the same file) that it will clean install, and since it was "easier" other developers told him to take it down because its taking away people from using their method. Again i am not saying your in the wrong, but at the same time there is always more than one method, and like myself if I mess up(which i have) before I ask anything I get on here and search and search. I never ask because if ever there is a mistake done its usually the users fault. I have used toolkits for years, and still knowing how to do fastboot i prefer toolkits and never had any issues because I read the directions the minimum of 2 times. This is XDA there is always more than one way to do something. We need to support @WugFresh and his work he has done. Again dont take this to heart I am not bashing you in anyway. All I am saying is we all have options and any member on here should know that if u make a mistake which we all have at one point. We Search first (number one rule on XDA). The answers are always here in XDA. Youtube to an extent also has google back up videos on how to do stuff to. I follow @Tomsgt aka root junky on youtube, and google plus. He does these things.

the_rooter said:
So your saying if no one uses your fastboot method thread that they are in the wrong. I understand and agree that all users should learn fastboot, but to push your thread on everyone
Click to expand...
Click to collapse
You know that's not what I meant. My fastboot thread / any fastboot thread - its not relevant. I know mine describes everything a user needs to know and its succinct so it doesn't take long g to read. Its an example!
Basically learn fastboot. I'm not pushing anything on anyone except morals. Don't be selfish and we'll all get along. Don't and well, people will be less inclined to help.
the_rooter said:
Theres always more than one method to do a task. Just because one is easier than the other doesn't make it bad.
Click to expand...
Click to collapse
You're still completely missing the point. I didn't say toolkits are bad. I said lack of knowledge is bad.
And actually on a nexus, a toolkit isn't really easier at all.
I don't really want to get into a drawn out discussion about this.. I hope you understand where I'm coming from. Use toolkits if you know both methods, but if you don't, go the (ever-so-slightly) longer way the first time so that you're not a drain on our time and helpfulness later on in life, because you didn't learn the basic essentials when you needed to.

TriBeard said:
so basically you could flash the stock 5.0.1 system.img, take the update, then root again (assuming the root method doesn't change, or using a new method after one is found?)
Click to expand...
Click to collapse
instead of going back to stock and then flashing OTA, why not just flash the new system.img directly?

I was big in to rooting and custom roms for both my Epic 4g Touch (s2) and my M7. I just never got in to it with my M8, and this is my first nexus device, so it's been a while, and the process is a little new/different for me. I've used toolkits in the past, but also had to adb/fastboot my way back in to a working rom at times as well. I just used a script to root the nexus 6, and so I didn't use fastboot. I knew it was simple for nexus devices usually, but didn't know specifics.

Have a Question??

I just bought an unlocked nexus 6 about week ago off of swappa. I unlocked the bootloader and rooted it so I could use titanium backup and v4a... Well I noticed I'm on 5.0.1 and I want to goto 5.1.. I cannot receive the update from Google since I'm rooted right?? So I've been reading and would like some input as in to what I should do. I'm not a total noob I've just been out of the rooting and flashing game for few years since I had the note 3 and 4 from att ( never again lol )... So what's my best course of action? Can I use wugs toolkit and just flash the factory images or do I have to unroot first? Thanks in advance... I just don't want to be left with a paper weight
Sent from ressurected from the dead OPO

There are many threads about this.
You can simply download the images from Google and manually flash them.
You need adb and fastboot installed along with the drivers.
Not trying to be an ass, but search here and read carefully. A toolkit isn't necessary, flashing a nexus isn't difficult and you will learn what and how to do it.
The links aren't hard to find. It may sound mean, but it will help you more in the long run.

This is exactly why I never post stuff on XDA anymore...if I read my post I have been reading and searching ... I just had a simple couple questions. I've been reading as much as I can but with me being a single father of two and not having all day to read I just wanted to ask a couple quick questions so I don't brick my phone! I know I can flash them but can I do it rooted? Can I still get the ota while I'm rooted. Last I read u couldn't then someone Todd me you could! So I just wanted to be sure that's all!!!
Sent from ressurected from the dead OPO

ok2nvnexus said:
This is exactly why I never post stuff on XDA anymore...if I read my post I have been reading and searching ... I just had a simple couple questions. I've been reading as much as I can but with me being a single father of two and not having all day to read I just wanted to ask a couple quick questions so I don't brick my phone! I know I can flash them but can I do it rooted? Can I still get the ota while I'm rooted. Last I read u couldn't then someone Todd me you could! So I just wanted to be sure that's all!!!
Sent from ressurected from the dead OPO
Click to expand...
Click to collapse
you can not go through with an updated if you have root, or if you changed any system files. you can always do it manually, amd the right way. or you can just flash any of the compiled 5.1 roms with twrp recovery.

Just flash system.IMG from Google with adb commands
Sent from my GT-P3113 using XDA Premium HD app

Yes, you can do it rooted.
I did it while my 2 year old daughter pitched a fit because she couldn't have my PC to watch Bubble Guppies and I flashed an N5 while my 14 year old watched asking question after question.
Learned how to use adb and fastboot after working 10-12 hours and cutting/splitting wood before it got dark.
I know tired and I know time crushed.
Forgive me.

blacknikname said:
Just flash system.IMG from Google with adb commands
Sent from my GT-P3113 using XDA Premium HD app
Click to expand...
Click to collapse
wrong, not adb. fastboot. you need to use fastboot for it.

jfcooley said:
Yes, you can do it rooted.
I did it while my 2 year old daughter pitched a fit because she couldn't have my PC to watch Bubble Guppies and I flashed an N5 while my 14 year old watched asking question after question.
Learned how to use adb and fastboot after working 10-12 hours and cutting/splitting wood before it got dark.
I know tired and I know time crushed.
Forgive me.
Click to expand...
Click to collapse
That's funny kids are always asking me for my phone while I'm out to watch bubble guppies on it...one it actually watching it on my opo right now... Back on topic... I downloaded the factory image and I know how to use adb and fastboot but do I have to unroot to do so or just flash as normal.. Sorry if I'm sounding noob but last time I used or did any of this was with my nexus 4. Years ago lol
Sent from nexus 6

You don't have to unroot. Depending on what you flash you may have to re-root after flashing.
Flash boot loader then reboot
Flash radio then reboot
Flash system, boot, cache if you want. If you want to erase everything flash userdta as well. I usually skip user data.
After that fastboot flash custom recovery, boot into it and flash SuperSU. If you don't have SuperSU, twrp will see its not rooted and ask if you'd like to just by swiping.
You need to have boot loader unlocked. Be sure to go to settings/developer options/allow OEM unlock (tick the toggle) BEFORE you do any of this.
Sorry if its kinda convoluted, dinner time and I'm breaking rules by using phone at table, so going fast

jfcooley said:
You don't have to unroot. Depending on what you flash you may have to re-root after flashing.
Flash boot loader then reboot
Flash radio then reboot
Flash system, boot, cache if you want. If you want to erase everything flash userdta as well. I usually skip user data.
After that fastboot flash custom recovery, boot into it and flash SuperSU. If you don't have SuperSU, twrp will see its not rooted and ask if you'd like to just by swiping.
You need to have boot loader unlocked. Be sure to go to settings/developer options/allow OEM unlock (tick the toggle) BEFORE you do any of this.
Sorry if its kinda convoluted, dinner time and I'm breaking rules by using phone at table, so going fast
Click to expand...
Click to collapse
Thanks for your patience with me, now enjoy family time ...And thank you for your help!
Sent from ressurected from the dead OPO

True, fastboot fastboot, I mean from CMD )))
Sent from my Nexus 4 using XDA Premium HD app

jfcooley said:
You don't have to unroot. Depending on what you flash you may have to re-root after flashing.
Flash boot loader then reboot
Flash radio then reboot
Flash system, boot, cache if you want. If you want to erase everything flash userdta as well. I usually skip user data.
After that fastboot flash custom recovery, boot into it and flash SuperSU. If you don't have SuperSU, twrp will see its not rooted and ask if you'd like to just by swiping.
You need to have boot loader unlocked. Be sure to go to settings/developer options/allow OEM unlock (tick the toggle) BEFORE you do any of this.
Sorry if its kinda convoluted, dinner time and I'm breaking rules by using phone at table, so going fast
Click to expand...
Click to collapse
Further to this, be aware, if you need to unlock the boot loader (if it isn't already unlocked), back up any data you want to keep... pictures music..etc because unlocking the boot loader... will erase everything......

Easy to follow Root Steps for Stock Android 6.0?

Hi Everyone
I have recently returned my Nexus 6 back to stock from Rooted 5.1.X roms by manually flashing the official google Marshmallow images. Now that 6.0 Roms are making their way out, I would like to get back to having the ability to flash the different roms. However, I am a little confused on how to successfully and easily accomplish the root and TWRP install process. I see that some of the new 6.0 ROMS say they are rooted, but I am confused on what that means.
Does anyone have a link or steps with links that you can provide so I can get my Nexus 6 ready to have custom roms flashed?
Thanks in advance!

TPADroid said:
Hi Everyone
I have recently returned my Nexus 6 back to stock from Rooted 5.1.X roms by manually flashing the official google Marshmallow images. Now that 6.0 Roms are making their way out, I would like to get back to having the ability to flash the different roms. However, I am a little confused on how to successfully and easily accomplish the root and TWRP install process. I see that some of the new 6.0 ROMS say they are rooted, but I am confused on what that means.
Does anyone have a link or steps with links that you can provide so I can get my Nexus 6 ready to have custom roms flashed?
Thanks in advance!
Click to expand...
Click to collapse
First this does not belong in the Development sections, moved here. Secondly please read the Forum Rules on posting...thanks.

Thank you for moving to the appropriate location.

as it is for every nexus, regardless of what android version youre on..
1. unlock your bootloader
2. fastboot flash twrp recovery
3. flash the latest supersu in twrp recovery
4. reboot with root
on marshmallow, with the stock rom, you will also want to flash a custom kernel with as well.

Well you need an unlocked bootloader and a custom recovery to flash custom roms.
1. Make sure that you have OEM unlock ticked in dev options
2. Use fastboot oem unlock command to unlock bootloader (this will wipe your phone completely, make a backup before doing this)
3. Use fastboot to flash twrp recovery
4. If you would like to keep stock rom and have root then you need to flash root script from chainfire or install custom rom with root already built in
5. Download and flash any rom of your choice (You can use adb sideload to sideload roms instead of having to copy them to the phone to flash)
Here is a good place to start to learn how http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481

simms22 said:
as it is for every nexus, regardless of what android version youre on..
1. unlock your bootloader
2. fastboot flash twrp recovery
3. flash the latest supersu in twrp recovery
4. reboot with root
on marshmallow, with the stock rom, you will also want to flash a custom kernel with as well.
Click to expand...
Click to collapse
Thank you Simms
When you are referring to unlocking the bootloader, it seems pretty self explanatory, from the google search...but I have seen where there are new boot.img files to apply via adb....is this unlocking the bootloader in 6.0? Or am I making this more complicated than it really needs to be. It seems that most ROMS now have an embedded Kernel...so I would flash one immediately #3. The one ROM I would like to try first is Chroma on 6.0.
Getting TWRP installed, I completely get and every step after that one...its the modified boot.img files I have seen, that is confusing me.
Thanks!

TPADroid said:
Thank you Simms
When you are referring to unlocking the bootloader, it seems pretty self explanatory, from the google search...but I have seen where there are new boot.img files to apply via adb....is this unlocking the bootloader in 6.0? Or am I making this more complicated than it really needs to be. It seems that most ROMS now have an embedded Kernel...so I would flash one immediately #3. The one ROM I would like to try first is Chroma on 6.0.
Getting TWRP installed, I completely get and every step after that one...its the modified boot.img files I have seen, that is confusing me.
Thanks!
Click to expand...
Click to collapse
The boot.img files that your referring to are probably to un-encrypt your phone. I personally don't but other always have. Supposed to make it faster although i haven't been bothered by it being slow.
To unlock the bootloader all you have to do is used fastboot oem unlock via fastboot while your phone is in the bootloader mode.

You don't need a custom kernel anymore thanks to Chainfire. Just use the Nexus root kit. Be sure to change the root settings in the NRK to approve beta SuperSu by Chainfire as stated in wugfresh Google+ post in step 3.
plus.google.com/u/0/113329792100896065459/posts/93WR63UHuEp[

mbiscuits said:
You don't need a custom kernel anymore thanks to Chainfire. Just use the Nexus root kit. Be sure to change the root settings in the NRK to approve beta SuperSu by Chainfire as stated in wugfresh Google+ post in step 3.
plus.google.com/u/0/113329792100896065459/posts/93WR63UHuEp[
Click to expand...
Click to collapse
no more kernel then, cool. but this is not a good idea to tell a newbie to use a toolkit, as he wont learn a single thing about , ever. and root toolkits mess up on occasion. they mess up enough to make a newbie think they bricked their phone. sure, chances are that everything will be fine, but the op will come out of it learning absolutely nothing, when the proper way is very easy and faster.
---------- Post added at 12:21 PM ---------- Previous post was at 12:20 PM ----------
TPADroid said:
Thank you Simms
When you are referring to unlocking the bootloader, it seems pretty self explanatory, from the google search...but I have seen where there are new boot.img files to apply via adb....is this unlocking the bootloader in 6.0? Or am I making this more complicated than it really needs to be. It seems that most ROMS now have an embedded Kernel...so I would flash one immediately #3. The one ROM I would like to try first is Chroma on 6.0.
Getting TWRP installed, I completely get and every step after that one...its the modified boot.img files I have seen, that is confusing me.
Thanks!
Click to expand...
Click to collapse
thats a kernel thatll let you unencrypt, if you want.

simms22 said:
no more kernel then, cool. but this is not a good idea to tell a newbie to use a toolkit, as he wont learn a single thing about , ever. and root toolkits mess up on occasion. they mess up enough to make a newbie think they bricked their phone. sure, chances are that everything will be fine, but the op will come out of it learning absolutely nothing, when the proper way is very easy and faster.
Click to expand...
Click to collapse
He did say easy and it doesn't get any easier than the toolkit. But if you want to do it manually follow the easy to read instructions found here: androidmarvel.com/index.php/2015/10/15/402/

mbiscuits said:
He did say easy and it doesn't get any easier than the toolkit. But if you want to do it manually follow the easy to read instructions found here: androidmarvel.com/index.php/2015/10/15/402/
Click to expand...
Click to collapse
sure, the manual way is MUCH easier than the toolkit. is it hard typing fastboot oem unlock? is it hard typing fastboot flash recovery recoveryname.img? well, thats it. i just unlocked my bootloader and flashed the recovery.

simms22 said:
sure, the manual way is MUCH easier than the toolkit. is it hard typing fastboot oem unlock? is it hard typing fastboot flash recovery recoveryname.img? well, thats it. i just unlocked my bootloader and flashed the recovery.
Click to expand...
Click to collapse
I agree with you IF you know what you are doing and have everything setup. However that didn't seem to be the case which is why I recommended the toolkit.

mbiscuits said:
I agree with you IF you know what you are doing and have everything setup. However that didn't seem to be the case which is why I recommended the toolkit.
Click to expand...
Click to collapse
which is why i always recommend that someone new root their phone the proper way the first time, to learn how to do it, and to learn a general way to fix your phone in case you mess up. after the first time, use toolkits all you want. but the learning how to do it properly is a very important.

TPADroid said:
Thank you Simms
When you are referring to unlocking the bootloader, it seems pretty self explanatory, from the google search...but I have seen where there are new boot.img files to apply via adb....is this unlocking the bootloader in 6.0? Or am I making this more complicated than it really needs to be. It seems that most ROMS now have an embedded Kernel...so I would flash one immediately #3. The one ROM I would like to try first is Chroma on 6.0.
Getting TWRP installed, I completely get and every step after that one...its the modified boot.img files I have seen, that is confusing me.
Thanks!
Click to expand...
Click to collapse
That modified img allows for root because you cant just flash SU on the stock one (not yet anyway). Unlocking the bootloader is something different.

simms22 said:
sure, the manual way is MUCH easier than the toolkit. is it hard typing fastboot oem unlock? is it hard typing fastboot flash recovery recoveryname.img? well, thats it. i just unlocked my bootloader and flashed the recovery.
Click to expand...
Click to collapse
Anybody knows where is the correct toolkit?

cpugeeker said:
Anybody knows where is the correct toolkit?
Click to expand...
Click to collapse
in my opening, there is no 'correct" toolkit.

Jnewell05 said:
Well you need an unlocked bootloader and a custom recovery to flash custom roms.
1. Make sure that you have OEM unlock ticked in dev options
2. Use fastboot oem unlock command to unlock bootloader (this will wipe your phone completely, make a backup before doing this)
3. Use fastboot to flash twrp recovery
4. If you would like to keep stock rom and have root then you need to flash root script from chainfire or install custom rom with root already built in
5. Download and flash any rom of your choice (You can use adb sideload to sideload roms instead of having to copy them to the phone to flash)
Here is a good place to start to learn how http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Click to expand...
Click to collapse
Hey thanks for all of this information. So far I'm stuck on step 2. I'm about a year into owning this phone and don't want to lose everything. One of the main reasons I want to root is to use titanium backup. However, you say to be sure to back up your phone. How do you recommend doing this.

jtmartin22 said:
Hey thanks for all of this information. So far I'm stuck on step 2. I'm about a year into owning this phone and don't want to lose everything. One of the main reasons I want to root is to use titanium backup. However, you say to be sure to back up your phone. How do you recommend doing this.
Click to expand...
Click to collapse
If you haven't rooted for over a year why do it now? There are sure to be updates to how to root on the Nexus 6 and since I don't use my nexus 6 very much I hate to steer you in the wrong direction, as to backup information. I recently got the android 7.0 update and I haven't really had a chance to check it out yet. But I bet there are dozens of ways to backup if you would search Google.
Sent from my SAMSUNG-SM-G935A using Tapatalk

jtmartin22 said:
Hey thanks for all of this information. So far I'm stuck on step 2. I'm about a year into owning this phone and don't want to lose everything. One of the main reasons I want to root is to use titanium backup. However, you say to be sure to back up your phone. How do you recommend doing this.
Click to expand...
Click to collapse
By unlocking the phone you lose everything. That's why when buying a Nexus phone, the first step should be unlocking the bootloader.
But if you want to root it anyway, then you should copy all your media and camera files to your computer. Then if you unlock it, you'll only lose some app settings. Most apps save to the cloud anyway. You can backup your text messages, and Google backups a lot of data like wallpapers or WiFi passwords. Also it will reinstall all your use apps, and since Marshmallow it will restore some app data, but that's far from consistent. For that you really need TB.

istperson said:
By unlocking the phone you lose everything. That's why when buying a Nexus phone, the first step should be unlocking the bootloader.
But if you want to root it anyway, then you should copy all your media and camera files to your computer. Then if you unlock it, you'll only lose some app settings. Most apps save to the cloud anyway. You can backup your text messages, and Google backups a lot of data like wallpapers or WiFi passwords. Also it will reinstall all your use apps, and since Marshmallow it will restore some app data, but that's far from consistent. For that you really need TB.
Click to expand...
Click to collapse
Thank you very much!!!!