Develop Bugs

[Q] Does this method of rooting work with the nexus galaxy?

http://www.unlockroot.com/index.htm
It mentions galaxy nexus. I didn't unlock my phone right away and now I regret it. I don't want to lose my app data and since I don't have root I can't use TB to back up my apps.
So will this be a good alternative, or should I avoid it?
Is there a down side to using this method instead of doing it the old fashioned way?
if this is useless, any recommendations on how I can safely back up my app data before unlocking the bootloader?
Thank you for the help.

never seen or used this. you can, but i prefer doing it manually. not really that hard.,
and theres a thread somewhere in general that tells you how to back up your stuff without root or unlocked bootloader.
something involving ADB commands. might be just better off starting again from fresh

zephiK said:
never seen or used this. you can, but i prefer doing it manually. not really that hard.,
and theres a thread somewhere in general that tells you how to back up your stuff without root or unlocked bootloader.
something involving ADB commands. might be just better off starting again from fresh
Click to expand...
Click to collapse
Unlocked / rooted mine right after I got it. Wipes it (the unlocking part), but it was easy, but I'm pretty good with adb and fastboot. Give it a try, there seems to be a bunch of one click tools out now.
Sent from my Galaxy Nexus using Tapatalk

this method seems to implement security vulnerability in android to escalate user privileges and install super user.
So this method is not an automatic version of the regular (boot unlock using fastboot), meaning it skips the whole wipe after unlock requirement.
anyway, I am gonna try it when I get home and report results.

[Q]Regarding rooting

Hey guys, I recently got my Gnex(internation version from expansys) last week, but I'm a little bit on the fence when it comes to rooting as this is my first Android device. What are the benefits? I mean, I know that you guys get a ton of options with the variety of roms available to download/install, but I'm liking the stock ics that came with the device. If somebody cold convince on on doing it, then I'd be grateful. My baseband is XXLA2, is that the recommended one if I'm living in the US?

The ability to control your phone like you should. However being a really new person to android I wouldn't recommend you do it right away. Maybe browse the forum and learn somethings. Knowledge is power.
Sent From My Sprint Galaxy Nexus

Root gives you admin access to your phone. Definitely you should root, even if you want to stay on stock factory rom.

RogerPodacter said:
Root gives you admin access to your phone. Definitely you should root, even if you want to stay on stock factory rom.
Click to expand...
Click to collapse
Only if he sees the benefits for himself. There's absolutely no reason for him to root if he doesn't understand what it does or how it will help/hurt him.

As mentioned previously, root access is admin access to the phone. Some benefits of it include being able to use the Adfree app to block advertisements in apps or Titanium Backup to backup apps the data associated with them. I'd take the time to get to know the phone and operating system first and then decide if you have a need for apps that require root access.

Off the top of my head:
-Fastest updates
-Ad removal
-Firewall
-True call blocking
-Lightflow
-Theming
-Backups (titanium, nandroid)
-Custom ROMs and all the millions of features they have (you could write pages and pages about this alone)
-Custom kernels (better battery+performance, touch wake, etc)
Since you have the Galaxy Nexus(a dev phone) as opposed to another locked-down phone, rooting is very, very easy. Unless you do something totally retarded you'll be safe. Just don't use toolkits -- do it manually.

fredryk said:
-Fastest updates
-Lightflow
-Backups (titanium, nandroid)
Click to expand...
Click to collapse
-You don't need to root to get fast updates. You can flash update files the day they come out via fastboot w/ an unlocked bootloader.
-Lightflow also works w/o root.
-You can do backups with ADB also.

martonikaj said:
-You don't need to root to get fast updates. You can flash update files the day they come out via fastboot w/ an unlocked bootloader.
-Lightflow also works w/o root.
-You can do backups with ADB also.
Click to expand...
Click to collapse
I guess I was thinking of "root" being synonymous with unlocked bootloader. My old phone required root...still need root for TB.

fredryk said:
I guess I was thinking of "root" being synonymous with unlocked bootloader. My old phone required root...still need root for TB.
Click to expand...
Click to collapse
Yes this is usually the case with other phones. With the Nexus, its extremely easy to unlock the bootloader and not root. I'd recommend unlocking the bootloader on this phone, but I'm not so quick to recommend rooting. People on XDA or too quick to recommend rooting to people who have absolutely no idea what it is and end up bricking their device.

martonikaj said:
Yes this is usually the case with other phones. With the Nexus, its extremely easy to unlock the bootloader and not root. I'd recommend unlocking the bootloader on this phone, but I'm not so quick to recommend rooting. People on XDA or too quick to recommend rooting to people who have absolutely no idea what it is and end up bricking their device.
Click to expand...
Click to collapse
+1. Exactly.
You do not need root to flash custom ROMs, get updates, etc. if you have an unlocked bootloader. I totally agree with martonikaj: you SHOULD unlock your bootloader, but you shouldn't mess around with root until you know what root is and need it.
Sent from my Galaxy Nexus using Tapatalk 2

I would unlock the bootloader immediately if you think you'll ever want to root the phone. Reason why is that you can unlock the bootloader easily with a single command, but it will wipe your phone, and there's no good way to do a real backup without rooting it. Better to do it now, before you have everything set up the way you want it and all of your apps installed.
For rooting, I agree that you shouldn't do it until you have a better idea what it is and why you want to do it.

I've been back and forth between root and non-root (always unlocked bootloader) and other than a few things already mentioned (Ad-free, Titanium Backup) I'm the type that can live with Stock ICS. I do flash custom ROM's once in a while to see if I enjoy them but I've always come back to Stock (for now) because of random reboot issues.

I'm reading this thread while on my way to root my phone (virgin like the guy who started this thread) I've been reading about rooting for a year, what's the difference between root and unlocked bootloader
Sent from my SPH-D710 using xda app-developers app

kennwoodkenn said:
I'm reading this thread while on my way to root my phone (virgin like the guy who started this thread) I've been reading about rooting for a year, what's the difference between root and unlocked bootloader
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
From someone who knows just enough to get by....
Unlocking your bootloader allows you to flash custom recovery/ROM/Stock version/etc. You don't need root for this.
Root allows you full access to the phone with superuser permissions and install some apps that require full access to system files.

kennwoodkenn said:
I'm reading this thread while on my way to root my phone (virgin like the guy who started this thread) I've been reading about rooting for a year, what's the difference between root and unlocked bootloader
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
You couldn't have been doing a lot of good reading if you've been reading for a year and don't know the difference. But don't feel bad -- there are lots of senior members that use the terms interchangeably which is completely and utterly wrong.
Root means having root user access to the file system. Kinda like being the administrator user on Windows machines. You can access all the files and modify and delete anything. The process consists of placing two files on the /system partition of your device. The problems with this process, is finding a way to make /system write-able to place those two files there (as it is read-only by default when you are booted in Android). Chicken or the egg -- You need root to get root.
Think of the bootloader as the BIOS of a computer. It loads up before the operating system, and allows you to perform certain basic tasks. In our case, the bootloader allows you to flash images to your device, and to boot images on your devices (without actually writing them to the NAND). Unlocking the bootloader removes the security on the bootloader, which means that the bootloader no longer verifies the signature of images you are trying to flash or boot and, thus, allows you to flash or boot non-Google signed images.
Now, are rooting and unlocking your bootloader related? Well, to a certain extent yes. If you unlock your bootloader, you can easily obtain root access. This is true because you can flash or boot a custom recovery, which will allow you to write files to /system without being booted into Android. So, with an unlocked bootloader, "rooting" becomes trivial. However, there are other ways to root -- by using exploits. GNex Android builds up to ICL53F can be rooted by mempodroid (see link 4 in my signature), but to-date, an exploit has not been found for IMM76D and higher.

For the epic touch it looks pretty easy to root in Odin mode it seems to be a way to go I know I want root for all the reasons above
My process
Root with ODIN
Install CWM
And like what I see in the AOKP ROM
I HAVE NOT FORGOTTEN TO BACKUP
Am I on the right track
Sent from my SPH-D710 using xda app-developers app

kennwoodkenn said:
For the epic touch it looks pretty easy to root in Odin mode it seems to be a way to go I know I want root for all the reasons above
My process
Root with ODIN
Install CWM
And like what I see in the AOKP ROM
I HAVE NOT FORGOTTEN TO BACKUP
Am I on the right track
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Why don't you ask in the Epic Touch forum??

Rooting your gnex doesn't need to be seen as taking a dive off a cliff while blindfolded. This is a myth perpetuated by people who have either never rooted their devices or did something retarded and bricked it. It's easy, painless, and uncomplicated if you follow the instructions. If you can take advantage of the ad removal, backups, call blocking, etc with ease....why not do it?
Use this: http://forum.xda-developers.com/showthread.php?t=1529058

Thanks for all your help!
I'll proceed to unlock the bootloader, but will remain on stock for a while until I get the hang of it and want to expand my options.

[Q] How to root my Galaxy Nexus but still get OTA updates from Google?

Excuse my complete noobishness, but can someone help me root my Galaxy Nexus but still get OTA updates from Google? I found multiple sources from here and a video from QBKing77 but nothing answer my question completely. I would be really grateful if someone with experience could help me by give me step by step instructions.
Thank you.

Rooting your phone does not disable OTA updates.

Why would you want ota if you rooted? Just flash a rooted version of the updated rom when it's released.
Sent from my Galaxy Nexus using Tapatalk 2

eqjunkie829 said:
Why would you want ota if you rooted? Just flash a rooted version of the updated rom when it's released.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I want to root just for two or three apps that require root access and still get updates from Google. I want the process: root -> get OTA update -> root again etc...

ZlateWay said:
I want to root just for two or three apps that require root access and still get updates from Google. I want the process: root -> get OTA update -> root again etc...
Click to expand...
Click to collapse
That's what I do. I don't flash ROMS, just use a few apps that require root. Install OTA Root Keeper from the play store to retain root. Run the app before installing any updates to preserve root. Then when you receive an OTA, install the update then run OTA Root keeper again to get your root back. Worked for me on Verizon Galaxy Nexus coming from 4.0.4 to 4.1.1.
Sent from my Galaxy Nexus using Tapatalk 2

The_other_ray said:
That's what I do. I don't flash ROMS, just use a few apps that require root. Install OTA Root Keeper from the play store to retain root. Run the app before installing any updates to preserve root. Then when you receive an OTA, install the update then run OTA Root keeper again to get your root back. Worked for me on Verizon Galaxy Nexus coming from 4.0.4 to 4.1.1.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
That is what I'm looking for! Can you explain to me step by step how did you did that? It would be great if you help me.

Use the guide in my sig or stickied at the top of this forum.
Only change would be fastboot boot recovery cwm.img rather than flash.

Just root the phone, and don't flash any custom recovery, then download supercurio's OTA root keeper app from the playstore, to backup your root then enable root with the same app after you receive OTA
Sent from my Galaxy Nexus using Tapatalk 2

suprakarma said:
Just root the phone, and don't flash any custom recovery, then download supercurio's OTA root keeper app from the playstore, to backup your root then enable root with the same app after you receive OTA
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Sorry for replying this late, thanks for the advice, but can you explain to me the steps that I need to use with the GNexus toolkit to root like you did? Thanks

ZlateWay said:
Sorry for replying this late, thanks for the advice, but can you explain to me the steps that I need to use with the GNexus toolkit to root like you did? Thanks
Click to expand...
Click to collapse
Don't use the toolkit?
Sent from my Galaxy Nexus

Why not?
The toolkit is SUPER easy.
Open the tool kit and the DOS window guides you through what to do, by typing numbers or letters to get the desired option. I can post the guide on when to boot in recovery mode and what the phone will do but as for the Toolkit, it's self helping. Just install it, run it and follow the on-screen instructions.
I do exactly the same as what you want successfully; I have a completely stock Nexus, but it's rooted for the use of some apps. The OTA update tells me when there is an update, I install then simply root again. I'd rather not have an app to keep root as that will be yet another app to clog up my phone's app drawer.
A lot of the custom roms aren't to my taste so I am happy to keep the stock experience
Will post again the steps when I am on my home PC.

anotherxdauser said:
Why not?
The toolkit is SUPER easy.
Open the tool kit and the DOS window guides you through what to do, by typing numbers or letters to get the desired option. I can post the guide on when to boot in recovery mode and what the phone will do but as for the Toolkit, it's self helping. Just install it, run it and follow the on-screen instructions.
I do exactly the same as what you want successfully; I have a completely stock Nexus, but it's rooted for the use of some apps. The OTA update tells me when there is an update, I install then simply root again. I'd rather not have an app to keep root as that will be yet another app to clog up my phone's app drawer.
A lot of the custom roms aren't to my taste so I am happy to keep the stock experience
Will post again the steps when I am on my home PC.
Click to expand...
Click to collapse
simply because the toolkit is an excuse not to learn the FUNDAMENTALS of owning a nexus device.
what happens when something goes wrong? do you know what the toolkit is doing behind the scenes? most of the toolkit users DONT. there are more than enough 'HALP!1!1 I BriKt mah PhoneZ!1!!oneone' to prove this is the case....
if you understand what its actually doing, you understand how useless it truly is...

Well, for starters the "fundamentals of owning a nexus device" don't include rooting at all. I know many people who use Nexus devices un-rooted and are fine.
Plus, I'm more than happy not learning too much about it as I'd rather spend my time eating cake.
Remember, not everyone here is in to tweaking settings, trying different radios, resetting their phone every 5 mins to test yet another ROM.
Some people are more than happy with the stock experience but just want root. The toolkit makes that simple.
Secondly, if the toolkit was doing things behind the scenes, I'm sure someone would have found that out and reported by now.
Thirdly, how do you know custom ROMs aren't doing the same thing? They are far more likely to be able to phone home without the owner knowing.
Fourthly, I personally tried rooting the manual way but the one line help of "just type this" I got never really worked with my phone.
Fifth, I've used the toolkit on my own phone and my partners many times, I've seen nothing bad, no bricking.
Don't see why you're so against something which makes life a lot easier for people who aren't too sure how to root the manual way?

anotherxdauser said:
Well, for starters the "fundamentals of owning a nexus device" don't include rooting at all. I know many people who use Nexus devices un-rooted and are fine.
Plus, I'm more than happy not learning too much about it as I'd rather spend my time eating cake.
Remember, not everyone here is in to tweaking settings, trying different radios, resetting their phone every 5 mins to test yet another ROM.
Some people are more than happy with the stock experience but just want root. The toolkit makes that simple.
Secondly, if the toolkit was doing things behind the scenes, I'm sure someone would have found that out and reported by now.
Thirdly, how do you know custom ROMs aren't doing the same thing? They are far more likely to be able to phone home without the owner knowing.
Fourthly, I personally tried rooting the manual way but the one line help of "just type this" I got never really worked with my phone.
Fifth, I've used the toolkit on my own phone and my partners many times, I've seen nothing bad, no bricking.
Don't see why you're so against something which makes life a lot easier for people who aren't too sure how to root the manual way?
Click to expand...
Click to collapse
And yet another person who fails at grasping why XDA exists....
Sent from my Galaxy Nexus

Actually, I do. I understand why XDA exists but I also understand the multi-uses it really has.
Not everyone who comes here has a desire to mess with their phones all the time...
If you're not a fan of the toolkit, why not flame the developer?
Here's a short guide on what the OP wanted to do.
1) Make sure phone is up to date. Make a note of your software version - probably 4.1.2 or 4.2 and build number (mine is JZO54K)
2) Turn on USB Debugging (Settings > Developer Options > USB Debugging)
3) Shut down the phone
4) Start in Bootloader (power button + vol up + vol down)
5) Run the Galaxy Nexus toolkit
This is where we use the toolkit. Read the info and select your build number. The windows will guide you through what options you have. If you want to root only, choose that option. Go through the menus and type YES to begin.
6) Phone will restart
7) After ~160 seconds, ToolKit will restart to Bootloader
8) Phone will restart
9) Toolkit will finish rooting by pushing the files to the phone.
10) Phone will restart back to Bootloader
11) Finish - Confirm in ToolKit
See pictures for further info.

Pirateghost said:
And yet another person who fails at grasping why XDA exists....
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
the toolkit also exists on xda..

k786 said:
the toolkit also exists on xda..
Click to expand...
Click to collapse
So does the person that thought I was saying the toolkit did something malicious... I never said any such thing.
Toolkits are pointless. It takes longer to learn the toolkit than it does the three commands needed to unlock and root a nexus. That's my ****ing point, yet this guy is going on about how easy the toolkit is to use. If it's so ****ing easy, why did you have to provide screenshots and instructions?
XDA-spoonfeeders.com
I miss XDA
Sent from my Galaxy Nexus
**edit**
i cannot believe that someone would actually think its NOT beneficial to understand the process, and rely solely on a toolkit...its amazing to think that there are people so wrapped up in their own little minds, that they refuse to take the time to learn to do things the right way and understand what they are doing to their device.
what happens when joe user, who only knows the toolkit, flashes a mod on his phone that was NOT intended for his phone/build/rom version, and he bootloops? he jumps on xda and posts a thread. HALP I JACKED MAH PHONE!!! how do i fix it with the toolkit?
please, for the love of tech, LEARN what it is you are doing. do us all a favor and help spread the KNOWLEDGE and stop with the damn toolkit. this website is designed for you to learn, not follow a damn prompt/menu to get instant gratification.

ZlateWay said:
Sorry for replying this late, thanks for the advice, but can you explain to me the steps that I need to use with the GNexus toolkit to root like you did? Thanks
Click to expand...
Click to collapse
Don't use a toolkit. Learn commands yourself and you won't have to worry about what a toolkit is or isn't installing.
Sent from my Galaxy Nexus using xda premium

root toolkits are fine, if you already know what you are doing. the problem with root toolkits arises when a person that has no idea what they are doing uses them and messes something up, which happens often, just read all the threads that users start asking for help, that include the words "i used a root toolkit". you dont see any these thread with the words i used fastboot or adb. usually what happens is something simple gets messed up, then the situation becomes worse because the user didnt know/learn the basics, and messed something up after. this is the problem with root toolkits, they go around you having to learn the basics. then we get all these threads about "help, i bricked my device". just taking the little time needed to learn the basics prevent this from happening.
this is a nexus device, its meant to be able to root the device easily. this is the basic procedure.. fastboot oem unlock, fastboot flash a custom recovery, flash the su binaries or custom rom in your custom recovery, reboot. that is it. it takes me 3 minutes to do this. add on a little reading beforehand, and maybe itll take you 30 minutes. much better than getting lost after using the root toolkit, or even messing up your device messing with stuff that you shouldnt. and, occasionally, the root toolkit itself can mess things up.
btw, op, you can always install an official "ota" manually, without receiving it ota, and without having root too. also, if you flash a rooted stock rom(unmodified, only root), youll still receive otas

You can unlock and root without install a custom recovery. IF you don't install any custom recovery and leave the stock one you'll continue to receive the ota updates.
Bye
Sent from my Galaxy Nexus using xda app-developers app

[Q] HELP!! Have I bricked my new device!? SO WORRIED!!

Hey guys,
I'm kinda new to the HTC/Android world, found this community a damn good place to find support.. But now I've hit a road block.
Basically, I've been eager to root from day 1 of getting my first htc handset, I came across from jailbreak and loved the fact of customizability with Android.
So I had the Google play edition(I think, all geared towards Google) running Kit Kat 4.4.4. Love it, big Google user so this all tied together lovely.
Here is the Situation.
I found a video on youtube, cannot provide URL as I'm in work at the moment, but it was root guide from scratch. Fresh windows OS, seemingly a phone fresh out the box.. you get the idea.
I used the Hasoon2000 tool to root the device. Installed ADB etc on my pc, signed up as a a dev, got the Key for device, sent in and received my .bin file. I got up to actually rooting my device, well pleased and happy. Using TWRP via Hasoon2000.
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Queried this on another forum, decided to continue to be patient... but no replies, in the mean time I restored my apps and have a fiddle, see what the root function can do for myself.
I installed "Freedom 1.0.6" and a program called "Market Share"- Hate iAP, some games are ridiculously priced for the smallest of things, I just wanted to sandbox plague inc. ;(
Now the device is stuck in a boot loop, phone starts up, see the home screen for a bout 40 seconds/ one minute.. Some times I unlock the device and it goes back to flash screen then.. others I boot an app and its slides away once more.
This happened close to 15x before I left for work this morning and I imagine its just going to repeat this and run the battery - I tried to stop this loop by going into TWRP and possibly choosing to boot system this way may of stopped it.. but when I was on the boot screen with those options.. It said Tampered at top of screen and S-On- which has scared me quite a bit..
What the hell has happened!?
I'm desperate to know and don't want to have this damn thing bricked! Please help.. try explain like I'm 5, as said I'm new to a lot of this! >.<

first off, if the screen comes on, its not bricked.
esenfur said:
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Click to expand...
Click to collapse
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.

redpoint73 said:
first off, if the screen comes on, its not bricked.
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
Click to expand...
Click to collapse
Thank you for fast response.
Official OTA - being that the phone its self said "Update the OS" - I just accepted this, hit download and began install as a reboot- didnt spot implications. As said, noob, followed a tut. If it highlighted DO NOT UPDATE or.. IF U WANT UPDATE NOW FOLLOW THIS- Great, but nothing of the sort?
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Or do you have any links to tutorials I could possibly follow?
Side note- when this loop started I deleted

esenfur said:
Or do you have any links to tutorials I could possibly follow?
Click to expand...
Click to collapse
This is really your main issue. By following a YouTube video and using a Toolkit, you've failed to actually learn anything or gain any real understanding or knowledge. Do yourself a favor and ditch the tutorials and videos (and toolkit for that matter) and do it the old fashioned way . . . by reading. Videos and step-by-step guides do you no good when things go south (as you've now discovered). And with the prior proper knowledge (usually not gained by following tutorials) this whole mess probably would have never happened in the first place.
A cardinal rule of Android phone modding: DO NOT accept/download/install OTAs (official OS updates) on a modded device unless you know what you are doing, and what the result will be. If in any doubt, simply DO NOT do it.
esenfur said:
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Click to expand...
Click to collapse
.exe file is Windows specific. You are looking for a zip file, and it typically starts with "OTA". Don't remember where its saved to, so you will have to search for it. If you can't keep the phone running long enough to do so, mount the memory on your computer and search that way.
Deleting the OTA file worked for me on a past device, although one M8 user in the same position said deleting the file didn't get him out of the loop. Flashing your ROM again, or wiping the internal memory (backup any important personal data first) might be options for you.

redpoint73 said:
you've failed to actually learn anything or gain any real understanding or knowledge.
Click to expand...
Click to collapse
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
redpoint73 said:
Videos and step-by-step guides do you no good when things go south (as you've now discovered).
Click to expand...
Click to collapse
agreed.. theres FAR much more I need to learn.. its scary haha.
redpoint73 said:
DO NOT accept/download/install OTAs (official OS updates)
Click to expand...
Click to collapse
taken on board. I know with my jailbreaks in past it has been a pain, assumed Android would be alot more stable to over write- due to functionality of OS and unlocked features.
I was being generic when I said .exe- basically the installer..
I returned from work to see phone stopped looping.. i could stop the install and deleted the file ASAP.. but now what.. Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?

I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.

Try to re-flash the ROM, with stok ROM, using TWRP and clean install. It should work.

hack14u said:
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Click to expand...
Click to collapse
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8

esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
First of all once the bootloader is unlocked you don't have to relock it to get OTA.
As I undersand you have done the following:
1) Unlock using HTCDev-Method
2) flashed a custom revocery (TWRP in your case)
3) flashed a supersu too!?
To install the OTA means loosing root acces. Thus you have to re-root it after the OTA is done. The other problem ist that STOCK OTAs don't work with a custom recovery. Meaning you would have to flash a stock recovery first, install the OTA second (as long as you didn't change anything an just root), and re-root third.
Let's have a look which stock recovery you would need:
1) reboot to bootloader
2) connect the phone to you PC and open cmd in you adb/fastboot folder
3) enter "fastboot getvar all"
4) paste this information here (but DELETE the IMEI and SERIAL NUMBER before posting!!)
As soon as we know which stock recovery you need we will go on.

esenfur said:
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
Click to expand...
Click to collapse
I'm not saying there is anything "wrong" with the toolkit, per se. For the most part, it does what its intended to do.
But it also shortcuts the learning process, and facilitates folks rooting the phone without gaining the proper knowledge. This is a dangerous thing.
This is just my opinion. But I strongly believe it. If you can't accomplish these things without a toolkit, you shouldn't be rooting your phone in the first place.
Others use the toolkits, and love them. They are more than entitled to have their own opinion. But when things go south, the toolkits aren't going to help; and those folks don't have the proper knowledge and they come running here. So you tell me what is the "best" way to root the phone?
esenfur said:
I was being generic when I said .exe- basically the installer..
Click to expand...
Click to collapse
I already figured this was probably the case. But I found it better to provide the exact information on what file to delete; rather than leaving it open to the possibility of you and/or others being misinformed.
esenfur said:
Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
Click to expand...
Click to collapse
Sounds like you still have TWRP installed, so just flash SU or SuperSU to gain root.
After that, you can use Titanium Backup or similar app to find the update process and freeze it, to stop the update notifications.
Don't remember the exact process (this is where searching and reading comes in for you) but its something like "drm..." or "updater".

I have this situation before,what i do is find the right stock recovery and flash..after ota done flash back custom recovery..?

esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
At this point after seeing this, I would suggest you take some time and start reading. All of your answers are here in the forums. Knowledge is power and within the pages of this site you will find everything you need.
To take the OTA find a stock recovery, to flash ROM's find the one you like and flash via your favorite recovery.

Why did you root?

Like the title says. Why?
I used to root/ROM all my devices but as Android grew up I have found less reasons to. I haven't had my 6P rooted for the last 3 months at all and my Pixel isn't rooted currently. I may decide to later for the dual speaker mod though.
So why do you root? For a feature? a tweak? habbit? just because you can/feel you should as a power user?

System wide ad away, custom kernels, Xposed when it comes out, AppRadioUnchained and root Tasker. The power of root! (Can fix unforseen issues)
Ad away, Xposed and AppRadioUnchained are game changers for me, well worth the trouble of root.
Twrp is another really root, but usually has the same negative effect, aka warranty issues, but system backups are great too.
PS: Pixel has no Knox and can be unrooted 100% via flash a stock image or locking bootloader (causes factory reset) so why not?

Rooting is my way of saying "**** you" to the "man". I want full control of my phone, not just what the "man" thinks is adequate or best for me.

Adaway
Call recording.

Substratum, Swift Black theme, Titanium Backup plus all of the above.
Sent from my Pixel XL

to put the clock in the center and get rid of the brightness slider in notification pull down. more seriously, adaway, EX kernel manager, and font change.
---------- Post added at 01:59 PM ---------- Previous post was at 01:16 PM ----------
FreeSoftwareServers said:
PS: Pixel has no Knox and can be unrooted 100% via flash a stock image or locking bootloader (causes factory reset) so why not?
Click to expand...
Click to collapse
I would go with unrooting by flashing a stock image but I would warn against locking the bootloader of a modified device. Put the stock image on and then lock the bootloader if you want but don't lock it while it's rooted, if you get into a bootloop, you won't be able to rescue if the bootloader is locked.
Not trying to pick a fuss, I just wouldn't want anyone to have a soft brick situation with a locked bootloader.
Maybe a Google store Pixel, you could re-unlock and restore from a soft brick with a locked bootloader but if it's Verizon and on 7.1.1, better not lock it while it's rooted.

3aucla1r3 said:
I would go with unrooting by flashing a stock image but I would warn against locking the bootloader of a modified device. Put the stock image on and then lock the bootloader if you want but don't lock it while it's rooted, if you get into a bootloop, you won't be able to rescue if the bootloader is locked.
Not trying to pick a fuss, I just wouldn't want anyone to have a soft brick situation with a locked bootloader.
Maybe a Google store Pixel, you could re-unlock and restore from a soft brick with a locked bootloader but if it's Verizon and on 7.1.1, better not lock it while it's rooted.
Click to expand...
Click to collapse
There is absolutely no reason to re-lock the bootloader. Even if you're sending back to Google (unlocked bootloader does not void warranty).

Ad away and titanium.
Sent from my Pixel XL using Tapatalk

Roms. Kernels. Debloat further. Greenify. Theming

3aucla1r3 said:
to put the clock in the center and get rid of the brightness slider in notification pull down. more seriously, adaway, EX kernel manager, and font change.
---------- Post added at 01:59 PM ---------- Previous post was at 01:16 PM ----------
I would go with unrooting by flashing a stock image but I would warn against locking the bootloader of a modified device. Put the stock image on and then lock the bootloader if you want but don't lock it while it's rooted, if you get into a bootloop, you won't be able to rescue if the bootloader is locked.
Not trying to pick a fuss, I just wouldn't want anyone to have a soft brick situation with a locked bootloader.
Maybe a Google store Pixel, you could re-unlock and restore from a soft brick with a locked bootloader but if it's Verizon and on 7.1.1, better not lock it while it's rooted.
Click to expand...
Click to collapse
I completely agree, personally, the only reason I'd do this is to return/sell the device, in which case, flashing a stock image via ADB is the way to go to totally wipe everything back to stock.

Why did I root
I had Samsung S5. Still on Alltell UDP. Used to use FoxFi for Wi-Fi on the go. I used to pay around $100 for comcast internet and basic cable. I came home one day and realized I am just stacking Wi-Fi on top of my comcast Wi-Fi. I figured why am I paying to Wi-Fi while I Wi-Fi. Then I had a decision, do I keep the comcast or the verizon. Well the verizon was mobile so that made it easy. Plus I don't watch TV other than some golf and college football. Go Spartans!! Then an OS updated caused FoxFi to stop working. My wife works from home and needs Wi-Fi. I had to figure something out fast.
I came here.
I couldn't get Samsung S5 to root, and since we needed new phones anyways, I bought 2 Nexus 6's. Best phone ever IMO. I read and studied for weeks. Only had time on weekends to figure out root. Finally I figured it out. Basically TWRP at that time. Anyways, it worked. Native hotspot and faster than comcast was.
Recently comcast threatened to kick anyone with UDP off "again". I was on Reddit trying to figure out how to stay on my plan via r/verizonUDP. There were all these crazy names for shady ways to keep your plan. Someone mentioned that they spoke to a Verizon rep and they stated they only way to be truly unlimited was to be under contract. He put up the legacy Verizon website. I went on there and was able to get mine and my wifes phones back under 2 years UDP.
By this time I was now a Nexus and soon to be Pixel guy. No way was I ever going back to any bloatware or non-stock type of phone. I realize root fixes a lot of this but with my love of the Nexus 6, I was sold on going with the Pixel XL. Let me tell you I had buyers remorse for a few months. 2k for 2 phones that were all getting pretty negative reviews. Glad I stuck with it thought. I love the Pixel XL.
I hook a bunch of people I work with up with my Wi-Fi. Network refresher was wokring for a bit. The 7.1.1 update nuked network refresher. I gave it a week or so then decided to root this phone.
Now with some experience under my belt I was able to root with CMD prompts and no TWRP. So proud of myself!!! Thank you to everyone here who has taken time to write down and explain the steps as well. Its not easy for someone who is not familar with the process and just started rooting within the past year. I realize this is a developer platform filled with experts well above my novice skill but those who care and explain things like they would to a golden retreiver really helps. I now encourage others I know to root and am even able to show them how. I don't think they would if they had to spend the time and effort I did by coming here and reading thread after thread.
Finally, I love TWRP and will go back. Just giving it some more time as Pixel is pretty good as is. I used to love some of the themes and kernels. I can't wait to get back to them but, work, 3 kids under 10, and a wife... Well all I can say is thank you to everyone here.

Question on the unrooting, I am one of 7 or 8 people in the US who want to use AndroidPay. If I unlock and root and then relock and unroot any idea if it will work again? I know it is a tough question, hoped someone would have an idea about it.
FreeSoftwareServers said:
System wide ad away, custom kernels, Xposed when it comes out, AppRadioUnchained and root Tasker. The power of root! (Can fix unforseen issues)
Ad away, Xposed and AppRadioUnchained are game changers for me, well worth the trouble of root.
Twrp is another really root, but usually has the same negative effect, aka warranty issues, but system backups are great too.
PS: Pixel has no Knox and can be unrooted 100% via flash a stock image or locking bootloader (causes factory reset) so why not?
Click to expand...
Click to collapse

Okmed said:
Question on the unrooting, I am one of 7 or 8 people in the US who want to use AndroidPay. If I unlock and root and then relock and unroot any idea if it will work again? I know it is a tough question, hoped someone would have an idea about it.
Click to expand...
Click to collapse
Right now someone made a modified kernel and put in a safety net patch. I was able to use Android pay and play Pokémon Go with an unlocked bootloader. I am in rooted but have twrp installed......
I personally have not needed root yet, tibu isn't something I need anymore. The battery life is so great compared to my n6 that I haven't even have greenify installed yet.

xocomaox said:
There is absolutely no reason to re-lock the bootloader. Even if you're sending back to Google (unlocked bootloader does not void warranty).
Click to expand...
Click to collapse
There is. Android pay doesn't work. So that's just one
---------- Post added at 12:20 PM ---------- Previous post was at 12:19 PM ----------
chapelfreak said:
Right now someone made a modified kernel and put in a safety net patch. I was able to use Android pay and play Pokémon Go with an unlocked bootloader. I am in rooted but have twrp installed......
I personally have not needed root yet, tibu isn't something I need anymore. The battery life is so great compared to my n6 that I haven't even have greenify installed yet.
Click to expand...
Click to collapse
Which kernel was that?

boober78 said:
There is. Android pay doesn't work. So that's just one
---------- Post added at 12:20 PM ---------- Previous post was at 12:19 PM ----------
Which kernel was that?
Click to expand...
Click to collapse
Since they have safteynet patch kernels available, that bypasses bootloader check with android pay.
So please don't re-lock your bootloader. It's very dangerous.

xocomaox said:
Since they have safteynet patch kernels available, that bypasses bootloader check with android pay.
So please don't re-lock your bootloader. It's very dangerous.
Click to expand...
Click to collapse
Yo can only re-lock it if you're fully stock, that's pretty obvious.

boober78 said:
Yo can only re-lock it if you're fully stock, that's pretty obvious.
Click to expand...
Click to collapse
Yet people do it anyways..

boober78 said:
There is. Android pay doesn't work. So that's just one
---------- Post added at 12:20 PM ---------- Previous post was at 12:19 PM ----------
Which kernel was that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/pixel-xl/development/kernel-stock-kernel-safetynet-patch-t3516596

Questions:
Where are (or are there) mods for:
1 Call Recording (figured it out)
2 Battery Percentage in status bar (figured it out)
3 Screenshot in power menu (that shortcut with vol+power does not work for me...I can never get it)
4 Switching multiwindow and back button on bottom (like Samsung)

funkydude101 said:
Questions:
Where are (or are there) mods for:
1 Call Recording (figured it out)
2 Battery Percentage in status bar (figured it out)
3 Screenshot in power menu (that shortcut with vol+power does not work for me...I can never get it)
4 Switching multiwindow and back button on bottom (like Samsung)
Click to expand...
Click to collapse
How did you get battery percentage in status bar? I can only get it inside the battery icon..