Develop Bugs

[Q]Is there a "true" factory restore for T-Mobile Galaxy S II?

We received our Samsung Galaxy II phones a few days ago.
My wife had a Swiftkey and Swiftkey X keyboard apps in her Amazon appstore account. She installed Swiftkey X, and she was presented with an "update" that showed Swiftkey (not the X; apparently this is an issue with Amazon appstore based on Swiftkey site). Thinking that it was an update to the Swiftkey X, she apparently applied it, and immediately there were number of FC notices (she remembers seeing TWLauncher among them) and a spontaneous reboot of the phone. Then, she couldn't get online either through WiFi or 4G. At that point she gave the phone to me to fix it
Comparing her phone side by side with mine it is very clear that there's an issue with network connectivity. While mine flies through the pages, market downloads, etc. either on WiFi or 4G, hers get stock for 3-5 seconds before opening pages or sometimes just displays a "webpage cannot be found" or "connection error".
I went ahead and did a factory restore, but that seems to only delete user account, personal files, etc. if I understand it correctly. Moreover, the issue is still there after the restore. So, is there a way to restore the system files to stock as well? Can it be done without rooting, or does it require loading a fresh ROM?
Sorry for the lengthy message and thanks in advance!

http://forum.xda-developers.com/showthread.php?p=27322
that's a full factory reset.
Sent from my SGH-T989 using Tapatalk

mikeyinid said:
http://forum.xda-developers.com/showthread.php?p=27322
that's a full factory reset.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply. Could you double check the link? I get "No Thread specified. If you followed a valid link, please notify the administrator".
Thanks again!

tenderidol said:
Thanks for your reply. Could you double check the link? I get "No Thread specified. If you followed a valid link, please notify the administrator".
Thanks again!
Click to expand...
Click to collapse
if you look at the sticky threads at the top of this forum there is one called index by AllGamer. Its at the bottom of the first post. Make sure you grab the Tmobile one and not the telus one
Sent from my SGH-T989 using Tapatalk

Here: http://forum.xda-developers.com/showthread.php?t=1323878
Everything goes back to stock.
You need to either:
1. Root
2. Install CWM through ROM Manager
3. Flash this
Or:
1. ODIN flash CWM
2. Flash this

513263337 said:
Here: http://forum.xda-developers.com/showthread.php?t=1323878
Everything goes back to stock.
You need to either:
1. Root
2. Install CWM through ROM Manager
3. Flash this
Or:
1. ODIN flash CWM
2. Flash this
Click to expand...
Click to collapse
Dude. That's a half ass way, it doesn't take you to stock. First of all its deodexed.. Just a sec
This is the only proper way to go back to stock THIS IS IT RIGHT HERE
Sent from my SGH-T989 using Tapatalk

Thanks again for the replies. So, I'm going to have to root it and put a stock image back I gues... I was hoping that SII had a fail safe similar to Nook Color where you can easily go back to stock if something was not right.

tenderidol said:
Thanks again for the replies. So, I'm going to have to root it and put a stock image back I gues... I was hoping that SII had a fail safe similar to Nook Color where you can easily go back to stock if something was not right.
Click to expand...
Click to collapse
you dont have to root it to run the odin package

mikeyinid said:
you dont have to root it to run the odin package
Click to expand...
Click to collapse
Oh, sorry about that. I'm a newbie for the SII rooting/modding (did quite a bit with Nook Color), and I need to do some reading first.

Smart man!
Sent from my SGH-T989 using Tapatalk

voidthedroid said:
Smart man!
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Alright, I'm halfway through. The rooting process for the SII is little different than NC, but the principles are the same.
By the way, is it safe to assume that some conflict between SwiftKey and SwiftKey X caused the problem on her phone? The reason I ask is because I'd like to put SwiftKey X on my SII (it has multi-language support) and I dont want to deal with the same issue if it was the culprit.

I believe I did enough reading at this point
Since this doesn't involve rooting (now I understand it), I'd like to get an "OK" from the guru before proceeding with the following "as newbie as it gets" steps:
1. Install Odin (v1.85)
2. Install Kies for the recent GSII drivers
3. Make sure Windows recognizes the phone in ODIN (seeing <ID:0/004> Added!! in the message box)
4. Turn off the phone
5. Turn on the phone by holding both the Vol-up and Vol-down buttons and plug the USB cable in while still holding both buttons
6. Select volume up button to proceed to download mode
7. Start Odin
8. Check the PDA button in Odin and browse to “T989UVKID_HOME_SGH-T989user_CL594724_REV00.tar.md5” file
9. Click Start in Odin and let it flash
10. Once it completes and reboots…..
Is that it? At Step 10, it should boot into a 100% T-Mo stock, right? Just to be sure, I’ll perform a factory reset after that point and start all over with the user files, apps, etc.
Thanks in advance!

Sounds good. But if you look in the stickied threads top of this forum the drivers for our phone are posted. No need to install kies but that does work also
Sent from my SGH-T989 using Tapatalk

tenderidol said:
Thanks again for the replies. So, I'm going to have to root it and put a stock image back I gues... I was hoping that SII had a fail safe similar to Nook Color where you can easily go back to stock if something was not right.
Click to expand...
Click to collapse
The "factory reset" you used IS the fail safe. The parts that "factory reset" doesn't remove is the part that won't be messed up unless you are rooted. So I don't even know how you touched /system etc without rooting...

mikeyinid said:
Sounds good. But if you look in the stickied threads top of this forum the drivers for our phone are posted. No need to install kies but that does work also
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Thanks a lot!
Just finished flashing the stock image and everything worked as expected. This was also a good practice to learn how to restore it to stock in case something goes bad.

513263337 said:
The "factory reset" you used IS the fail safe. The parts that "factory reset" doesn't remove is the part that won't be messed up unless you are rooted. So I don't even know how you touched /system etc without rooting...
Click to expand...
Click to collapse
The issue was created after installing a 3rd party keyboard and -by accident- applying an update that was supposed to be for a slightly different version, which resulted in numerous force closes and random reboots immediately. I might be wrong here, but that indicates that more than just the user files were affected, since deleting just user files via factory reset didn't help the network problem. However, flashing the stock image -without rooting- took care of the problem.

Rooting Gnex GSM/HSPDA v4.0.2 Optus Stock

Hey guys!!,
Yet another of my noob questions BUT, this time I think I'm going to take the plunge and root my Gnex!!! *scared* haha
I'm just having to many frustrating things happening on my stock Gnex, low responsiveness to the touch, slow-ish and well, isnt this what its all about!! =)
So a quick one, if anyone can point me in the most normal, simple and customizable direction, what do I do? I have searched for a while now so I have an idea where i want to go, either, Cynagon or AOKP...I'm hearing great things about AOKP...there from the same devs yeah?? (a guess)
So, I have a Samsung updated Gnex, in Aus and with optus. I'm technical so I'm getting a grasp on whats what but still not to clear on Kernels and radios....bit worried about that. Clockwork I'm guessing is like a boot manager?? Just asking that while I was here...
So Odin? Wug? CF-Root? I'm just not sure...
Thanks soooo much in advance guys.... I already appreciate your help. =)=)
*Excited!!!*
Cheers!!
P.S. I'd also very much like to return to stock form later on if I want...like locked oem and restored stock rom... =)

Helmet321 said:
Hey guys!!,
Yet another of my noob questions BUT, this time I think I'm going to take the plunge and root my Gnex!!! *scared* haha
I'm just having to many frustrating things happening on my stock Gnex, low responsiveness to the touch, slow-ish and well, isnt this what its all about!! =)
So a quick one, if anyone can point me in the most normal, simple and customizable direction, what do I do? I have searched for a while now so I have an idea where i want to go, either, Cynagon or AOKP...I'm hearing great things about AOKP...there from the same devs yeah?? (a guess)
So, I have a Samsung updated Gnex, in Aus and with optus. I'm technical so I'm getting a grasp on whats what but still not to clear on Kernels and radios....bit worried about that. Clockwork I'm guessing is like a boot manager?? Just asking that while I was here...
So Odin? Wug? CF-Root? I'm just not sure...
Thanks soooo much in advance guys.... I already appreciate your help. =)=)
*Excited!!!*
Cheers!!
P.S. I'd also very much like to return to stock form later on if I want...like locked oem and restored stock rom... =)
Click to expand...
Click to collapse
Try my ToolKit in the dev forum. Its simple, straightforward, easy to understand, there is a 1-click option which will do everything and every step is explained in detail.
http://forum.xda-developers.com/showthread.php?t=1392310
You can also use my ToolKit to flash a Stock Google Rom if you ever want to in the future.
With regards to Roms there are lots available to try by very experienced developers that will make your phone better and plenty of kernels to make it run ALOT faster. I use bigxie's Rom and franco's kernel.
Mark.

Hi!!,
Thanks so much for your reply!
Funny as, I was JUST reading your guide. Awesome work man, very informative.=)=) and it would of taken some time to compile!. =/
Arm, I'm just wondering what file I need to backup to got back to the rom I'm on now? I want to be able to go back, if needed.
I don’t know what kernels are all about, and what do I need to do about Radios?? If I have the wrong one or something, does that mean I wont have signal?? Or bad call/signal reliability?
I'm looking at the build 23 of AOKP...I'm hearing its the go...and if i have a wrong kernal rom radio combo, what’s that going to do??, that’s if they correlate?? haha
Is security as issue?? Since these are built "freely" is there any exposure of private info?
I'm sorry for smashing you with all this, I'm just trying to get all the info before I do anything and to have a failsafe if I need to return for warranty.... =/
Thank you in advance!!! =)
Cheers.
P.S. Is Bigxie Apex?? I hear good things about that too!! haha. Its so hard, theres so many out there... Apex, Gummy, AOKP look great. I also really want a responsive, battery lasting, fast and importantly "stable" phone. So, not sure what you recommend. =)
Thanks already!! =)=)

Helmet321 said:
Hi!!,
Thanks so much for your reply!
Funny as, I was JUST reading your guide. Awesome work man, very informative.=)=) and it would of taken some time to compile!. =/
Arm, I'm just wondering what file I need to backup to got back to the rom I'm on now? I want to be able to go back, if needed.
I don’t know what kernels are all about, and what do I need to do about Radios?? If I have the wrong one or something, does that mean I wont have signal?? Or bad call/signal reliability?
I'm looking at the build 23 of AOKP...I'm hearing its the go...and if i have a wrong kernal rom radio combo, what’s that going to do??, that’s if they correlate?? haha
Is security as issue?? Since these are built "freely" is there any exposure of private info?
I'm sorry for smashing you with all this, I'm just trying to get all the info before I do anything and to have a failsafe if I need to return for warranty.... =/
Thank you in advance!!! =)
Cheers.
P.S. Is Bigxie Apex?? I hear good things about that too!! haha. Its so hard, theres so many out there... Apex, Gummy, AOKP look great. I also really want a responsive, battery lasting, fast and importantly "stable" phone. So, not sure what you recommend. =)
Thanks already!! =)=)
Click to expand...
Click to collapse
If you goto settings, about phone then it will tell you all about your current rom build. If its a yakju build then its a stock google rom and can easily be found and reflashed via my ToolKit. If its been put on by your operator then you wont be able to obtain it online and you are best backing it up (unless you dont mind putting the google stock rom back on).
To do that you will need to set your drivers up first. This is important as nothing else can be done without this step. If you have Windows xp or 7 then its pretty easy, you can install the drivers automatically via the GNex ToolKit, then reboot your pc. Goto settings, developer options on your phone and tick 'usb debugging' then connect the usb cable to your phone (with it booted into Android). This should install adb drivers which are needed for communication when your phone is booted into Android. Start the ToolKit and select your current build version (which can be found in settings, about phone). At the top of the Main Menu you should see a serial number under adb mode which means your device is recognised in this mode. Select reboot options (19) in the ToolKit and Reboot phone to Fastboot (3). This is a bootloader mode for the phone outside of Android where you can flash and manipulate certain parts of your phone. As this mode is at a much lower level then the operating system it can be your saviour if your phone locks or wont start and you need to flash back to stock.
Once the phone has rebooted to fastboot mode the fastboot drivers should be installed on your pc. If nothing happens try unplugging and replugging the usb cable to initiate the drivers. If the drivers have installed before the ToolKit refreshes then you should now see the serial number at the top under fastboot mode this time. You NEED both fastboot and adb drivers installed on your pc for everything to work.
After the drivers have been set up you will need to Unlock the Bootloader to be able to have access to system areas on your phone. BE AWARE that unlocking the bootloader will erase EVERYTHING all data on your phone including the Internal Storage (virtual SD Card) so copy anything you need to from your Internal Storage accross to your pc and use the Backup option in the ToolKit to save any installed apps and associated user data that you want to keep. This is done in adb mode so your phone will need to be in Android.
If you want to back up your current Rom then Unlock the Bootloader, reboot your phone into Android, go through the setup quickly (as the phone will have been wiped), then goto settings developer options and enable usb debugging. Start the ToolKit and in the Main Menu select 19, 3 to reboot back to fastboot mode. Then you can BOOT into CWM Recovery without flashing it (9) and select backup/restore to backup your Rom/user data/boot image to a datestamped folder inside a folder called Clockworkmod on your Internal Storage. The rebooting into Android step after unlocking the Bootloader is important as cwm will not work properly without doing that.
Once that is all done you are ready to reboot into Android from cwm, get back to fastboot mode as before and select 1-click option (7). You will get a message on the unlock stage saying that your device is already unlocked but then it will just skip to the next stage. Be aware that when the device boots into Android the first time this is to let the user enable usb debugging for adb operations and if you have already done this then the ToolKit will wait for about 3 minutes before carrying on. Be patient as the ToolKit hasnt frozen, its just set to pause before carrying on.
Ok now thats all over with, on to your other questions lol. I would advise trying either romanbb's AOKP (build 24 should be up today) or bigxie's Apex 1.02 to start. Personally I use Apex as it has loads of customisation and runs very well but saying that I will be trying romanbb's new build when it is out.
Kernels are like the drivers of your phone. They set up how it works and what it can do. Custom Kernels can give better battery life and more power, performance, stability so its well worth trying them once you are rooted. They will tell you what builds they are compatable with but if you are thinking about the above Roms then you will be on Android build 4.0.3 and most new kernels work with that. I use franco's kernel but there are ALOT of established kernel developers working with the Nexus so you could try fugumod by nikademus or trinity by morfic. These are all flashed via cwm (download file, copy to Internal Memory, reboot to recovery mode once you have cwm flashed). You can enter cwm by rebooting to fastboot and using the volume buttons to select recovery, then press power to select, or from the reboot phone options in the ToolKit (19,4 in adb mode).
Bootloaders and Baseband/Radio updates are something to think about but not really needed if your phone is running fine. You wont notice any change if you update the bootloader as its just like updating your bios on a pc. Just gives some extra functionality or updates some deep down settings. Radios control the communication part of your phone and updating to a new one may improve battery, signal, wifi, gps lock. You can update them by either grabbing a premade zip and flashing via cwm or download the .img file and flash that via the ToolKit.
Dont worry about malware included in custom roms as long as its by an established developer. They would never put anything dangerous to the end user in one of their roms as it would harm their reputation and if anything was found by a user the rom would be taken down imediately by us mods to keep you safe.
I think thats everything you will ever need to know lol. Sorry theres alot I wanted to make sure you had all the ammunition you needed to continue and it took soo long to write I had lunch half way through
good luck.
Mark.

Ohhh man, thank you sooo much. That’s a lot of info and I really appreciate you taking the time to explain that to me Mark. Thank you!!!!
Ok, I’ve been watching some videos, one off of GalaxyNexusRoot.com. I think its his YouTube chan… He's seems pretty cool. Shows you what to do. I sort of want to do it manually so I'm understanding it all?, if that makes sense? I like to know exactly what my device is doing, why and how? haha. I'm a bit pedantic like that.
Arm, only a couple of things....I'm draining your life here...haha
I have a Samsung updated Gnex, throwing that in FYI. =) Not sure if the warranty centre would realise, probably so I should back it up as it is...on this note quickly, I do want to have a yakju (Google) updated phone though...hehe.
When I back up, does it flash everything? the rom, kernels and radios? (Mostly for my Stock setup for reversion, and understanding...)
With roms, where can I get the G'apps from? (If needed) And or the SupUser/Root files? (Separately I mean, so I can do this manually...if I'm understanding it properly... =/ )
Also, do these apps and others update as normal? Or di i have to update the whole ROM to update them? Like Maps (Navigation more importantly), GTalk, MarketPlace etc...?
And finally....phew...haha arm, sorry....
I'm looking at doing this because currently my device just seems a little non-responsive, laggy-ish and its turned off once.. =/ Is this all normal?? I thought for a minute my screen was faulty, like touches don’t always respond...I mean 90% of the time they do...I know, I'm nuts but it just ruins it for me... I uninstalled Beautiful Widgets and it’s sort of been better…maybe some apps aren’t configured with ICS yet also…I'm thinking it just could be the build? What do you think??
It's kind of weird to think that an individual dev has made. and is making more progress than the developers of the phone/software?? hahah...Anyway, I hope I've made some sense and I really, really, really appreciate all this Mark, all your time and patience with me. =)
Thanks again!!!!
P.S.... This should be it I SWEAR!! haha....
Just wanted to put these here...these are "some" of the problems I've been having... =/
http://forum.xda-developers.com/showthread.php?t=1500545
http://forum.xda-developers.com/showthread.php?t=1490335
http://forum.xda-developers.com/showthread.php?t=1500236
http://forum.xda-developers.com/showthread.php?t=1487946
Thank you...again!!!

I just want to thank the OP for asking the right questions and taking the time to figure out how "hack" his/her phone correctly instead of jumping in blind.
I hope other beginners follow the OP's lead.
That is all.
Sent from my Galaxy Nexus using xda premium

Helmet321 said:
Ohhh man, thank you sooo much. That’s a lot of info and I really appreciate you taking the time to explain that to me Mark. Thank you!!!!
Ok, I’ve been watching some videos, one off of GalaxyNexusRoot.com. I think its his YouTube chan… He's seems pretty cool. Shows you what to do. I sort of want to do it manually so I'm understanding it all?, if that makes sense? I like to know exactly what my device is doing, why and how? haha. I'm a bit pedantic like that.
Arm, only a couple of things....I'm draining your life here...haha
I have a Samsung updated Gnex, throwing that in FYI. =) Not sure if the warranty centre would realise, probably so I should back it up as it is...on this note quickly, I do want to have a yakju (Google) updated phone though...hehe.
When I back up, does it flash everything? the rom, kernels and radios? (Mostly for my Stock setup for reversion, and understanding...)
With roms, where can I get the G'apps from? (If needed) And or the SupUser/Root files? (Separately I mean, so I can do this manually...if I'm understanding it properly... =/ )
Also, do these apps and others update as normal? Or di i have to update the whole ROM to update them? Like Maps (Navigation more importantly), GTalk, MarketPlace etc...?
And finally....phew...haha arm, sorry....
I'm looking at doing this because currently my device just seems a little non-responsive, laggy-ish and its turned off once.. =/ Is this all normal?? I thought for a minute my screen was faulty, like touches don’t always respond...I mean 90% of the time they do...I know, I'm nuts but it just ruins it for me... I uninstalled Beautiful Widgets and it’s sort of been better…maybe some apps aren’t configured with ICS yet also…I'm thinking it just could be the build? What do you think??
It's kind of weird to think that an individual dev has made. and is making more progress than the developers of the phone/software?? hahah...Anyway, I hope I've made some sense and I really, really, really appreciate all this Mark, all your time and patience with me. =)
Thanks again!!!!
P.S.... This should be it I SWEAR!! haha....
Just wanted to put these here...these are "some" of the problems I've been having... =/
http://forum.xda-developers.com/showthread.php?t=1500545
http://forum.xda-developers.com/showthread.php?t=1490335
http://forum.xda-developers.com/showthread.php?t=1500236
http://forum.xda-developers.com/showthread.php?t=1487946
Thank you...again!!!
Click to expand...
Click to collapse
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.

What does stock stand for?

udmbrian said:
What does stock stand for?
Click to expand...
Click to collapse
It means the version that the manufacturer put on the phone before it was shipped or a version that is supplied by the manufacturer. Unaltered by developers.
Mark.

mskip said:
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.
Click to expand...
Click to collapse
Thanks again!!!!
Ok cool. So when new versions of the apps come out on the market, I wont be able to update them normally will I? Which is ok but just wondering how that is going to go down. Haha.
Lastly, sorry man, I'm almost there. Haha. CWM doesn't backup kernel? Like my stock one?
So it basically makes a "phone" image, ExtPartition and all? Or can you choose these options?
Right, I'm so close now I reckon, today will be the day... I can feel it!!! Haha.
Thank you again!!!!!!!!!
Sent from my Galaxy Nexus using XDA App

Helmet321 said:
Thanks again!!!!
Ok cool. So when new versions of the apps come out on the market, I wont be able to update them normally will I? Which is ok but just wondering how that is going to go down. Haha.
Lastly, sorry man, I'm almost there. Haha. CWM doesn't backup kernel? Like my stock one?
So it basically makes a "phone" image, ExtPartition and all? Or can you choose these options?
Right, I'm so close now I reckon, today will be the day... I can feel it!!! Haha.
Thank you again!!!!!!!!!
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Yes of course you can update google apps via the market as normal.
Cwm will back up your boot image which contains the kernel. So yes it does back up the kernel.
You can not choose which options to back up but you can choose which parts you want to restore via the advanced restore option in cwm.
Let me know how it all goes
Mark.

El Daddy said:
I just want to thank the OP for asking the right questions and taking the time to figure out how "hack" his/her phone correctly instead of jumping in blind.
I hope other beginners follow the OP's lead.
That is all.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Hey El Daddy,
Thanks man. I try to reframe from being a pain in butt.... not sure how I've gone with that but, Haha. I appreciate what your saying. I just want to be sure what I'm doing and to have, as Mark said, all the "ammo" I need.
Cheers.
Sent from my Galaxy Nexus using XDA App

Great questions and answers from both of you. Just got this phone and trying to figure out where to start. Briefly read the toolkit instructions. Just haven't had the time to sit down and plow through it. Thanks both of you.

mskip said:
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.
Click to expand...
Click to collapse
Thanks so much again Mark...This is Great!!
Ok, just before I do this...I'm like right here at the PC...ready! haha...
I understand all of it now, well. in theory...
Thank you for the DL link to the root.zip...
I DL'd the android SDK Kit zip also, but there’s no fastboot.exe??? Or anything like what I need?? haha, I may just be missing something here...
One of you links on you manual guide is broken...I think, that’s where you had it...I didnt want to harass you again but just some final things. =)
I'm really after all of what I need to this manually...for knowledge etc?? Hope you understand... You made this wicked awesome Kit, and I'm stupid and not using it...hahah...
So as far as I can see, I need:
- Samsung Drivers - which I have and that bits done... =)
- fasboot.exe etc (Android SDK Gear)
- Latest CWM.zip
- **Rom of my choice, which I'm going to take your advice and go with Apex. =) Latest 1.02 yeah??
- Franco Kernel, I'll try stock, but my feeling on it is that that’s probably been my major issue, or the cause of most of them... =)
Phew....I think that’s it...am I on the right track??
I cant thank you enough with all this Mark....seriously...your a very patience man. haha
Cheers. =)
**Update**
P.S. I have attached a file. Mark can you check it out and see if that what I need in regards to Android SDK stuff? I just got this now after I posted the above....
Thanks again... =)
***Update...again....haha***
Arm, just looking at these files, whats the boot.img? does that get copied over to the phone? Or is it just a command? The su & Superuser files in this zip are like a different size and modified later than your ones (newer??? =/)....I'm not sure what that would really mean...probably has nothing to do with anything but just thought I'd check with you....

Helmet321 said:
Thanks so much again Mark...This is Great!!
Ok, just before I do this...I'm like right here at the PC...ready! haha...
I understand all of it now, well. in theory...
Thank you for the DL link to the root.zip...
I DL'd the android SDK Kit zip also, but there’s no fastboot.exe??? Or anything like what I need?? haha, I may just be missing something here...
One of you links on you manual guide is broken...I think, that’s where you had it...I didnt want to harass you again but just some final things. =)
I'm really after all of what I need to this manually...for knowledge etc?? Hope you understand... You made this wicked awesome Kit, and I'm stupid and not using it...hahah...
So as far as I can see, I need:
- Samsung Drivers - which I have and that bits done... =)
- fasboot.exe etc (Android SDK Gear)
- Latest CWM.zip
- **Rom of my choice, which I'm going to take your advice and go with Apex. =) Latest 1.02 yeah??
- Franco Kernel, I'll try stock, but my feeling on it is that that’s probably been my major issue, or the cause of most of them... =)
Phew....I think that’s it...am I on the right track??
I cant thank you enough with all this Mark....seriously...your a very patience man. haha
Cheers. =)
**Update**
P.S. I have attached a file. Mark can you check it out and see if that what I need in regards to Android SDK stuff? I just got this now after I posted the above....
Thanks again... =)
***Update...again....haha***
Arm, just looking at these files, whats the boot.img? does that get copied over to the phone? Or is it just a command? The su & Superuser files in this zip are like a different size and modified later than your ones (newer??? =/)....I'm not sure what that would really mean...probably has nothing to do with anything but just thought I'd check with you....
Click to expand...
Click to collapse
Looks like everything in that zip is ok for what you want to do. The superuser.apk is a different size but im sure it doesnt matter.
In order to push the 2 files across to your phone you need to have booted into Android using an insecure boot image. This is a stock boot.img that has has some simple text changes to allow temporary root access (otherwise the files wouldnt copy across) Using fastboot you boot the boot.img file and then once you are in Android you push the files across and set their permissions. When you reboot your phone your original boot image will be used and you should have permanent root via the files.
Looks like you are all set
MArk.

Oh ok. So it doesn't stay on the phone?, its temporary??
So if this file say, is corrupted or malicious, (not really possible probably byt...) I'm in trouble? haha
Sorry, I have everything I think now, I grabbed the SDK of the Android website and I'm comfortable with that cause its "legit" I suppose. It doesn't have a boot.img file though. Can I make one myself so I know where its coming from? And where does this normally come from?
Silly stuff I know but, I told you, I'm CRAZY!! haha....
One very last thing...the permissions, whats that part all about...
Other than that, I'm pretty sure I'm sweet now...I also grabbed the latest CWM zip off the website too...so I'm cool with that.
......geez.... I'm killing you aren't I....I think you deserve (need) at LEAST 1 beer after all this....haha...
Thanks x 1,000,000...seriously.... =)

Helmet321 said:
Oh ok. So it doesn't stay on the phone?, its temporary??
So if this file say, is corrupted or malicious, (not really possible probably byt...) I'm in trouble? haha
Sorry, I have everything I think now, I grabbed the SDK of the Android website and I'm comfortable with that cause its "legit" I suppose. It doesn't have a boot.img file though. Can I make one myself so I know where its coming from? And where does this normally come from?
Silly stuff I know but, I told you, I'm CRAZY!! haha....
One very last thing...the permissions, whats that part all about...
Other than that, I'm pretty sure I'm sweet now...I also grabbed the latest CWM zip off the website too...so I'm cool with that.
......geez.... I'm killing you aren't I....I think you deserve (need) at LEAST 1 beer after all this....haha...
Thanks x 1,000,000...seriously.... =)
Click to expand...
Click to collapse
Its perfectly possible to make your own boot image but to be honest you might take another day or 2 to get all the required components and research what you need to do lol
If you go to your settings, about phone screen and tell me the build version (4.0.1, 4.0.2) and whether its a gsm or lte device (im assuming gsm as lte is america/canada) then I will attach the boot image I made for that device so it will definitely be right and safe. You can also use the su and superuser.apk files I attached earlier if you are unsure about them.
I dont mind all the questions as long as you end up feeling confident enough to get your phone rooted mate I would rather people ask too many (but the right) questions than just go blindly into something have no understanding about and end up in trouble.
Mark.

Your a legend Mark, I swear!!....haha
Ok, well, its a GSM, 4.0.2 Samsung updated Nexus....I think... I can attach some images. =)
The end of the line here...haha, arm, I just watched a video that completely skipped the boot.img part...weird...anyway, with the "su" part, I have 2 files there, as you've kindly provided, but in that step doesnt it need to be a su.zip sort of configuration? Just running it by you before I do this...
P.S....again....haha, arm, if I'm thinking about this right, does the step with "fastboot boot boot.img" will that affect the stock image?? As I think, if I'm right you have to do that "before" you flash your recovery?? In my mind would it be right in assuming....
-Unlock bootloader
-Flash recovery
-Make a Back up (so to get all the rom, including the auto restore recovery??)
-Set SU perms...with su.zip or su+superuser.apk... (if I'm right also, this step only if you want root perms on stock?, not sure what you would do with it though, only if you want to remain this way I suppose... =/ )
Is this right??
I was reading your "manual" post and I'm a little confused...as in, you cant reboot into Android after flashing recovery (to back up) as it will delete it, but to do so, you need to reboot into Android to delete the auto recovery flash file?? And you need su perms yeah?? Am I right here, I'm probably going crazy-ier...haha cause I've been at this for 2 days...haha...
Seems the boot.img step is the same as if you would flash a su.zip...(which I dont have, only the su file (no extension) and the su.apk...) not sure if thats the same...just getting my head around it here.... =)
Maybe I'm thinking CWM will "back up" the su perms etc and affect the "stock rom"...if you back it up with the perms, wouldnt that be included?? Maybe thats were I'm getting it wrong...haha.
Finally...........serious.....
If and when you delete the auto recovery file (if that really does delete it completly, I'm probably wrong about that too...) how does it restore??
Thanks mate. =)=)
I think thats it...when I have my head around these final things...and the last couple of files...Its time.... =)=)

Helmet321 said:
Your a legend Mark, I swear!!....haha
Ok, well, its a GSM, 4.0.2 Samsung updated Nexus....I think... I can attach some images. =)
The end of the line here...haha, arm, I just watched a video that completely skipped the boot.img part...weird...anyway, with the "su" part, I have 2 files there, as you've kindly provided, but in that step doesnt it need to be a su.zip sort of configuration? Just running it by you before I do this...
P.S....again....haha, arm, if I'm thinking about this right, does the step with "fastboot boot boot.img" will that affect the stock image?? As I think, if I'm right you have to do that "before" you flash your recovery?? In my mind would it be right in assuming....
-Unlock bootloader
-Flash recovery
-Make a Back up
-Set SU perms...with su.zip or su+superuser.apk...
Is this right??
I was reading your "manual" post and I'm a little confused...as in, you cant reboot into Android after flashing recovery (to back up) as it will delete it, but to do so, you need to reboot into Android to delete the auto recovery flash file?? And you need su perms yeah?? Am I right here, I'm probably going crazy-ier...haha cause I've been at this for 2 days...haha...
Seems the boot.img step is the same as if you would flash a su.zip...(which I dont have, only the su file (no extension) and the su.apk...) not sure if thats the same...just getting my head around it here.... =)
Maybe I'm thinking CWM will "back up" the su perms etc and affect the "stock rom"...if you back it up with the perms, wouldnt that be included?? Maybe thats were I'm getting it wrong...haha.
Finally...........serious.....
If and when you delete the auto recovery file (if that really does delete it completly, I'm probably wrong about that too...) how does it restore??
Thanks mate. =)=)
I think thats it...when I have my head around these final things...and the last couple of files...Its time.... =)=)
Click to expand...
Click to collapse
There are 2 ways of rooting your phone. The easier (and non learning way) is to flash cwm recovery and flash the superuser.zip straight to the phone. If this is what you watched then tbh you might as well be using my ToolKit as you wont learn anything from the experience. The other way is the method my ToolKit uses which is to boot the phone with the insecure boot image to gain temporary root, then using adb to push the 2 files that I sent to your phone and set their permissions, then rebooting to complete the root procedure. The 2nd method is the one I thought you was gearing up towards and the best way if you want to actually learn something, otherwise as I said you may as well use the ToolKit.
I have attached every file you will need for the 2nd method and if yo uread below these are the instructions you will need to follow to root your phone. Extract the attached files to a folder on your pc, browse to this folder then HOLD the Shift button on your pc while right clicking on a blank area of the Windows Explorer. Select 'Open command window here' which will open a command prompt in the correct folder where your adb and fastboot files are.
These instructions are for after you have installed drivers:
fastboot-toolkit devices
Click to expand...
Click to collapse
this will return a serial number if your drivers are installed.
fastboot-toolkit oem unlock
Click to expand...
Click to collapse
and follow the instructions on the phone to unlock your bootloader.
Now if you boot into Android RIGHT after unlocking the bootloader it will restart the boot half way through so you want to do this normally BEFORE using your insecure boot or the reboot half way through will lose your insecure access (if you get me)
fastboot-toolkit reboot
Click to expand...
Click to collapse
to get your first boot in. Once the phone has booted up and you have gone through the setup wizard, go to settings, developer tools and select 'usb debugging' to enable adb control.
adb-toolkit devices
Click to expand...
Click to collapse
should return a serial number if your adb drivers are installed.
adb-toolkit reboot bootloader
Click to expand...
Click to collapse
to get back into fastboot so you can boot from the insecure boot image
fastboot-toolkit boot boot_gsm_ICL53F_insecure.img
Click to expand...
Click to collapse
to boot your phone into Android from the insecrure boot image. Once your phone has booted into the lockscreen you can carry on with
adb-toolkit root
adb-toolkit remount
Click to expand...
Click to collapse
to mount your /system folder for root access.
adb-toolkit push su /system/bin
adb-toolkit push Superuser.apk /system/app
Click to expand...
Click to collapse
pushes the 2 files across to the correct folders on your phone.
adb-toolkit shell chmod 06755 /system/bin/su
adb-toolkit shell chmod 06755 /system/app/Superuser.apk
Click to expand...
Click to collapse
sets their correct permissions.
Lastly if you are flashing cwm then you will need to rename the recovery restore file if you are on a samsung rom. If this file is present on your phone and cwm is flashed, then on the next reboot the stock recovery will be restored and you will lose cwm. To get back to stock recovery in the future you just flash a stock recovery image.
adb-toolkit shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p-old
Click to expand...
Click to collapse
will rename the file is it is present.
Thats it! Reboot your phone and you should have root You can check this by downloading root checker from the market or just download a root app such as adfree or setcpu.
Mark.

I see you are replying to my thread already as I was making some changes so re-read the instructions as I rearranged them a bit to make more sense lol.
MArk.

back to stock

I checked the forums and couldnt find my answer.
I am rooted and have twrp, and the android market installed. I would like to go back to bone stock.
I can just reset the KF under device right? How do I uninstall twrp?
Thanks

No thats incorrect you dont just reset the device you must wipe well and flash stock I must tell you numerous people are bricking themselves fairly bad attempting to do the same personally I would avoid it just flash modaco instead other than that the method to return to stock is in the second post http://forum.xda-developers.com/showthread.php?t=1638452

And actually it might even be a safer approach to revert to stock from a stock like rom http://forum.xda-developers.com/showthread.php?t=1439916

Bricked beyond all recognition baby!
Thepooch said:
No thats incorrect you dont just reset the device you must wipe well and flash stock I must tell you numerous people are bricking themselves fairly bad attempting to do the same personally I would avoid it just flash modaco instead other than that the method to return to stock is in the second post http://forum.xda-developers.com/showthread.php?t=1638452
Click to expand...
Click to collapse
android.process.acore
process.android.providers.calendar
These are wise words indeed. Installed Twrp and MiUI ics rom and played with it but gave up after day or so and was headed back to stock... battery was/is apparently too low AND I keep getting 2 force close errors for (right after boot) ...
-android.process.acore
-process.android.providers.calendar
(happens right after the UI starts loading ... if Im quick enough I can get one of the homescreen apps to load, but I notice the settings menu item or none of the software buttons for home, etc are there
... then after I click the force close button it just starts to boot again... not enough time to try to get twrp back on to handle boot so I can wipe and try to flash update.zip (the fires stock rom).
Oh well, its only 200.00 and I'll be getting another one I guess. glad it was with this and NOT one of my smartphones I tinker with from time to time. lesson learned about playing with rom flashing when battery is low I guess.

putney1477 said:
I checked the forums and couldnt find my answer.
I am rooted and have twrp, and the android market installed. I would like to go back to bone stock.
I can just reset the KF under device right? How do I uninstall twrp?
Thanks
Click to expand...
Click to collapse
Even if you want to go back to pure stock, keeping/reinstalling both TWRP and FFF are the safest and smartest things to do.

Thepooch said:
No thats incorrect you dont just reset the device you must wipe well and flash stock I must tell you numerous people are bricking themselves fairly bad attempting to do the same personally I would avoid it just flash modaco instead other than that the method to return to stock is in the second post http://forum.xda-developers.com/showthread.php?t=1638452
Click to expand...
Click to collapse
Wow.....looks complicated. I just rooted and flashed twrp yesterday, wish I never had. I want to sell my kf, but I want it stock. Reading the post, it looks like I will mess it up pretty badly. I dont know how to use adb
Sent from my GT-P3113 using Tapatalk 2

putney1477 said:
Wow.....looks complicated. I just rooted and flashed twrp yesterday, wish I never had. I want to sell my kf, but I want it stock. Reading the post, it looks like I will mess it up pretty badly. I dont know how to use adb
Sent from my GT-P3113 using Tapatalk 2
Click to expand...
Click to collapse
The only mention of ADB is "adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip", which you can easily avoid if you don't want to touch ADB.
Just rename your downloaded file to update.zip (watch out for the file extension, Windows hides most of them on default settings), then just copy it into your KF like you do any other file. Do not place it in any subfolder.
Be sure to follow the steps carefully, or else you may end up with a soft brick (fixable).

Dasanko said:
The only mention of ADB is "adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip", which you can easily avoid if you don't want to touch ADB.
Just rename your downloaded file to update.zip (watch out for the file extension, Windows hides most of them on default settings), then just copy it into your KF like you do any other file. Do not place it in any subfolder.
Be sure to follow the steps carefully, or else you may end up with a soft brick (fixable).
Click to expand...
Click to collapse
Ohhh ok so i just change the file to update.zip and flash it In twrp? Will that break root too? So thats all i have to do to get back to stock? Should i wipe in twrp before i flash?
Sent from my GT-P3113 using Tapatalk 2

tamaker said:
android.process.acore
process.android.providers.calendar
These are wise words indeed. Installed Twrp and MiUI ics rom and played with it but gave up after day or so and was headed back to stock... battery was/is apparently too low AND I keep getting 2 force close errors for (right after boot) ...
-android.process.acore
-process.android.providers.calendar
(happens right after the UI starts loading ... if Im quick enough I can get one of the homescreen apps to load, but I notice the settings menu item or none of the software buttons for home, etc are there
... then after I click the force close button it just starts to boot again... not enough time to try to get twrp back on to handle boot so I can wipe and try to flash update.zip (the fires stock rom).
Oh well, its only 200.00 and I'll be getting another one I guess. glad it was with this and NOT one of my smartphones I tinker with from time to time. lesson learned about playing with rom flashing when battery is low I guess.
Click to expand...
Click to collapse
I have the same problem, but my battery was 100% when flashing back. Is this good night for the kindle then?
It boots in to the 6.2.2 software, but these errors pop up and force close then eventually does a restart. Dammit!

putney1477 said:
Ohhh ok so i just change the file to update.zip and flash it In twrp? Will that break root too? So thats all i have to do to get back to stock? Should i wipe in twrp before i flash?
Sent from my GT-P3113 using Tapatalk 2
Click to expand...
Click to collapse
No, that's not all you should do to get back to stock... follow ALL the STEPS. Wiping is VERY important. Ie, don't just rename the file to update.zip and flash it right away, or you'll most likely end up with a soft brick. I was only clarifying that one specific step.

Dasanko said:
No, that's not all you should do to get back to stock... follow ALL the STEPS. Wiping is VERY important. Ie, don't just rename the file to update.zip and flash it right away, or you'll most likely end up with a soft brick. I was only clarifying that one specific step.
Click to expand...
Click to collapse
oh ok, thanks

Just a side note after restoring to stock you need to then perform a factory restore as well which will wipe your sd card if all goes well it should smooth out from there

Dasanko said:
The only mention of ADB is "adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip", which you can easily avoid if you don't want to touch ADB.
Just rename your downloaded file to update.zip (watch out for the file extension, Windows hides most of them on default settings), then just copy it into your KF like you do any other file. Do not place it in any subfolder.
Be sure to follow the steps carefully, or else you may end up with a soft brick (fixable).
Click to expand...
Click to collapse
Anyone know how to check to see if windows adds .zip? Like how do I check the default settings for file extensions. Also do I need to unroot before I flash back to stock? or will flashing take care of that for me?

putney1477 said:
Anyone know how to check to see if windows adds .zip? Like how do I check the default settings for file extensions. Also do I need to unroot before I flash back to stock? or will flashing take care of that for me?
Click to expand...
Click to collapse
http://windows.microsoft.com/en-us/windows-vista/show-or-hide-file-name-extensions That applies for Vista/7. XP is almost the same.
Flashing back to stock will undo anything you've ever done or had on the device, except for the contents of /sdcard (the stuff you've copied to it from the computer).

Dasanko said:
http://windows.microsoft.com/en-us/windows-vista/show-or-hide-file-name-extensions That applies for Vista/7. XP is almost the same.
Flashing back to stock will undo anything you've ever done or had on the device, except for the contents of /sdcard (the stuff you've copied to it from the computer).
Click to expand...
Click to collapse
OMG! I can't thank you enought for taking the time to answer all of my questions!!! It worked!!!! I am back to stock! (I had no doubt, thanks to you!) THANK YOU!!!
Heather

Sudden Boot Loops - I'm Lost

I've been using my Galaxy Nexus for a month or so, with the official JB ROM (JR30C or whatever, deodexed and rooted) and today I opened Gmail.
That's it. I opened GMail, switched accounts, and my phone has been bootlooping ever since.
I wiped everything in CWM multiple times and reflashed it, and I can't get the phone to do anything else.
Any clues?

Do you have a working nandroid? Have you tried flashing a different ROM?
Allons-y

Xfanatic said:
Do you have a working nandroid? Have you tried flashing a different ROM?
Allons-y
Click to expand...
Click to collapse
I do not have a working NANDROID. I wasn't sure about the Internet policies at work, but it looks like I can at least make it on here, I'm not sure I'll be able to download another ROM.
I'm confused though, I mean I know it would help to try as many options as possible (to fix it) - but this ROM has been working for weeks. And the phone died randomly, not due to a recent file change or a botched program. The only boot loops I've experienced before were on the Nexus One, and it was always due to a buggy/bad flash or a corrupted ROM download - this one just developed epilepsy on its own...

Here's my plan, since these are the only things I can manage to download due to restrictions on Internet usage at work.
Factory 4.1.1 takju image from here : https://developers.google.com/android/nexus/images#takju
Modified ODIN software here: http://forum.xda-developers.com/showthread.php?t=1586807
ODIN won't rewrite my bootloader, recovery, or userdata, since I already OEM unlocked, but will reflash a stock image.
EDIT: ODIN won't do anything with my device. Trying this ROM instead:
http://forum.xda-developers.com/showthread.php?t=1801664 was using bigxie OTA before.

is your (sd)storage recognized? thus is a similar symptom to when the stirage goes bad.

Hook the phone up to adb, boot it, and let logcat run. Maybe that will turn something up.
Sent from my Galaxy Nexus using Tapatalk 2

simms22 said:
is your (sd)storage recognized? thus is a similar symptom to when the stirage goes bad.
Click to expand...
Click to collapse
Hmm, you know, I'm not able to find the option to mount to USB in CWM...and just in case I forgot where that is, when I plug it in, I get the "hardware failed" noise from Windows and not the usual friendly "plug in" sound.
infazzdar said:
Hook the phone up to adb, boot it, and let logcat run. Maybe that will turn something up.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm at work, and I only have my work computer. Group/secpolicy won't allow me to install anything, no admin rights, etc.
Would it even do anything? The phone barely makes it through one second of the boot animation before it loops.

sheik124 said:
Hmm, you know, I'm not able to find the option to mount to USB in CWM...and just in case I forgot where that is, when I plug it in, I get the "hardware failed" noise from Windows and not the usual friendly "plug in" sound.
Click to expand...
Click to collapse
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.

Zepius said:
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.
Click to expand...
Click to collapse
Oy. Then how do I get another ROM on here? fastboot/adb?

sheik124 said:
Oy. Then how do I get another ROM on here? fastboot/adb?
Click to expand...
Click to collapse
Adb push.
Sent from my Galaxy Nexus using Tapatalk 2

Zepius said:
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.
Click to expand...
Click to collapse
sheik124 said:
Oy. Then how do I get another ROM on here? fastboot/adb?
Click to expand...
Click to collapse
Got more than one additional ROM on there via adb/recovery - my clue that CWM hasn't actually been able to do anything since the phone start looping is I'm still getting my custom boot animation.
I'm using the toolkit to reflash a stock image now. What a mess.
Even reflashing a stock image via fastboot did nothing. WTF happened to my phone? Won't stay on long enough to get a logcat

I'm having the same problem as this guy:
http://forum.xda-developers.com/showthread.php?t=1827685&page=2
I just got finished trying to flash 4.1.1 using ODIN. It still shows me the custom animation from bigxie's ROM (which has supposedly since been overwritten 2-4x times).
Screw you Samsung...this phone is a month old, I flashed -once- to rooted Jelly Bean, and the phone dies when I open the GMail app.
EDIT: WTF - I write screw you Samsung, it boots to the Welcome screen! Just long enough for me to see that my files aren't on it anymore, then it bootloops again. And again. Now it's re-stuck in a bootloop.
And now I'm at the homescreen. I can't rely on this thing like this...is my flash dying or something?

Nobody?
It worked long enough for me to re-enter all of my different Google account information and now it's dead again. Now it only flashes the boot animation for a split second for bootlooping.

I'm thinking of a hardware defect.
Beamed from my Grouper

Mach3.2 said:
I'm thinking of a hardware defect.
Beamed from my Grouper
Click to expand...
Click to collapse
Mee too. As you can see from my signature, I gave up and bought a One S yesterday night from Craigslist. Feels like a true successor to the Desire / N1. It's nice to finally have an AMOLED screen that actually seems color calibrated after the ugly mess that was my RAZR and my less than perfect GNex. It's a damn shame how much more painless flashing a recovery was on this thing.
Sent from my HTC VLE_U using xda app-developers app

How many here are rooted/running custom ROMS?

I used to be extremely heavy into the rooting game. I started with the Galaxy s2 all the way to the Note 5 but then it kind of seemed to me like rooting lost some of it's appeal and development seemed to slow down for some devices. After the Note 7 issue with the recall I switched to iPhone for a little while. I am back now though and I'm highly looking into rooting. I see the Pixel XL has tons of development and am just wondering what do you guys think, is it worth it to root? Many people I have talked to say Android has come so far, that it's not really even necessary anymore. What are the Pro's/cons?
If this is a topic that has been posted before, I apologize, I tried looking and couldn't find anything. Also, this is my first stock google phone, in the past I have always been a galaxy/note user.

rbtrucking said:
I used to be extremely heavy into the rooting game. I started with the Galaxy s2 all the way to the Note 5 but then it kind of seemed to me like rooting lost some of it's appeal and development seemed to slow down for some devices. After the Note 7 issue with the recall I switched to iPhone for a little while. I am back now though and I'm highly looking into rooting. I see the Pixel XL has tons of development and am just wondering what do you guys think, is it worth it to root? Many people I have talked to say Android has come so far, that it's not really even necessary anymore. What are the Pro's/cons?
If this is a topic that has been posted before, I apologize, I tried looking and couldn't find anything. Also, this is my first stock google phone, in the past I have always been a galaxy/note user.
Click to expand...
Click to collapse
I still root because of theming and my call regarding app. Imo, custom roms are still smoother.
Sent from my Pixel XL using Tapatalk

just_visiting said:
I still root because of theming and my call regarding app. Imo, custom roms are still smoother.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I was always a huge fan of theming! Hmm, perhaps it's time to pull the trigger!

I've always rooted every device, starting with my HTC Hero years ago, but I have to admit, the stock Pixel experience was the first time where I've had to ask myself is it really worth it this time.
So I tried it un-rooted for a couple of months, (which is a personal record for me!) and I loved it. But I eventually made the decision to root because I missed:
1)Dark U. I (Using Substratum)
2 Adaway Adblocker
3)Custom Roms
Now I'm on PureNexus, and couldn't be happier.
With Google seemingly tightening the screw by making it harder to modify our devices, I just hope Root access will continue to be available to me in the future.

Just like buzzboy for the most part:
- Theming. (Domination from daveyannihilation on the playstore)
- Ad blocker.
- Custom ROM.
- For pushing theme ready apps to system/data partition.
- Kernel manager app (EXKM)
- Certainly other things I forget right now...
Cheers...

buzzboy said:
I've always rooted every device, starting with my HTC Hero years ago, but I have to admit, the stock Pixel experience was the first time where I've had to ask myself is it really worth it this time.
So I tried it un-rooted for a couple of months, (which is a personal record for me!) and I loved it. But I eventually made the decision to root because I missed:
1)Dark U. I (Using Substratum)
2 Adaway Adblocker
3)Custom Roms
Now I'm on PureNexus, and couldn't be happier.
With Google seemingly tightening the screw by making it harder to modify our devices, I just hope Root access will continue to be available to me in the future.
Click to expand...
Click to collapse
Ya, I was looking into that PureNexus rom too.

rbtrucking said:
Ya, I was looking into that PureNexus rom too.
Click to expand...
Click to collapse
Hello... Been using it since the Nexus 6, Nexus 6P and now Pixel XL. I have never been disappointed. Pixel stock firmware features + just enough customization in my opinion.
Cheers...

pure nexus + elementalx because perfect performance

Forgot about AdBlock and custom kernel. Also few other things that are escaping me at the moment.
Sent from my Pixel XL using Tapatalk

5.1 said:
Hello... Been using it since the Nexus 6, Nexus 6P and now Pixel XL. I have never been disappointed. Pixel stock firmware features + just enough customization in my opinion.
Cheers...
Click to expand...
Click to collapse
What's the best tutorial for rooting in your opinion? Been looking on YouTube and trying to decide which one to follow.

rbtrucking said:
What's the best tutorial for rooting in your opinion? Been looking on YouTube and trying to decide which one to follow.
Click to expand...
Click to collapse
No, no and no! Don't go on YouTube when you have the best on XDA. That doesn't make sense...
Download TWRP: https://dl.twrp.me/marlin/twrp-3.0.2-0-RC1-fastboot-marlin.img
Download SuperSU 2.79 sr3: https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip?retrieve_file=1
And place in the root of your internal storage
Reboot your phone in bootloader.
You must have latest ADB/fastboot from Google: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Unzip it and place TWRP image inside platform tools folder with ADB/fastboot.
Open a command prompt on your computer and boot into TWRP:
fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img
It will boot TWRP. Once booted, tap "install" and select SuperSU. Swipe to install and let it do its job.
Once done, just reboot. It will likely reboot two or three times. Don't worry, that's normal. You'll have Root with full stock. TWRP will vanish after the reboot.
Don't try to flash this TWRP image or you may have to reflash a full stock image... Read TWRP thread for more infos!
I think you could have found the same how-to here either in the guide or Q/A section though... :good:
Good luck...

5.1 said:
No, no and no! Don't go on YouTube when you have the best on XDA. That doesn't make sense...
Download TWRP: https://dl.twrp.me/marlin/twrp-3.0.2-0-RC1-fastboot-marlin.img
Download SuperSU 2.79 sr3: https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip?retrieve_file=1
And place in the root of your internal storage
Reboot your phone in bootloader.
You must have latest ADB/fastboot from Google: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Unzip it and place TWRP image inside platform tools folder with ADB/fastboot.
Open a command prompt on your computer and boot into TWRP:
fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img
It will boot TWRP. Once booted, tap "install" and select SuperSU. Swipe to install and let it do its job.
Once done, just reboot. It will likely reboot two or three times. Don't worry, that's normal. You'll have Root with full stock. TWRP will vanish after the reboot.
Don't try to flash this TWRP image or you may have to reflash a full stock image... Read TWRP thread for more infos!
I think you could have found the same how-to here either in the guide or Q/A section though... :good:
Good luck...
Click to expand...
Click to collapse
Hmm I may have jumped the gun here I actually attempted before you responded and followed Max Lee's video on youtube and now I am stuck in a bootloop. What can I do? it's saying your devices software cab't be checked for corruption please lock the bottloader, then it says visit link on another device g.co/ABH

rbtrucking said:
Hmm I may have jumped the gun here I actually attempted before you responded and followed Max Lee's video on youtube and now I am stuck in a bootloop. What can I do?
Click to expand...
Click to collapse
Why?
You are on the forum where SuperSU and Magisk, likely the two best Root method are released. And you go somewhere else looking how to install it...
What did you do to get stuck? How did you proceed?

5.1 said:
Why?
You are on the forum where SuperSU and Magisk, likely the two best Root method are released. And you go somewhere else looking how to install it...
What did you do to get stuck? How did you proceed?
Click to expand...
Click to collapse
I've followed Max Lee's videos many times before and they have always worked. I guess I shouldn't have. What I did was download fastboot, the root marlin pixel and the usb driver and basically boot into the stock recovery by holding down power and volume down and doing the comman in command prompt to unlock the bootloader and then boot to root.img now it's stuck in a bootloop

rbtrucking said:
I've followed Max Lee's videos many times before and they have always worked. I guess I shouldn't have. What I did was download fastboot, the root marlin pixel and the usb driver and basically boot into the stock recovery by holding down power and volume down and doing the comman in command prompt to unlock the bootloader and then boot to root.img now it's stuck in a bootloop
Click to expand...
Click to collapse
You used the old root method for 7.1
If you know how to flash a Kernel then flash the factory Kernel and then use the directions above. If you dont the easiest way is ro just flash back to stock without a data wipe. First post in thw thread below.
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478/page16

rbtrucking said:
I've followed Max Lee's videos many times before and they have always worked. I guess I shouldn't have. What I did was download fastboot, the root marlin pixel and the usb driver and basically boot into the stock recovery by holding down power and volume down and doing the comman in command prompt to unlock the bootloader and then boot to root.img now it's stuck in a bootloop
Click to expand...
Click to collapse
No offence here. Just, the method you tried is not up to date... If you took the time to search a little bit before proceeding you would have known that. All infos you need to flash/root/mod are most likely already posted here. All questions have already been answered as well. Use the search function next time or at least, wait for someone to reply :good:
Good luck...
PS: hoping you'll get it fixed. 3am here, I'm off to bed...

TonikJDK said:
You used the old root method for 7.1
If you know how to flash a Kernel then flash the factory Kernel and then use the directions above. If you dont the easiest way is ro just flash back to stock without a data wipe. First post in thw thread below.
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478/page16
Click to expand...
Click to collapse
I really appreciate all the help for some reason now my computer is not showing the phone in my computer so I can't access the files on it. I think it's got something to do with what I did to root it, I changed the driver for the phone. I used the file called android_winusb

rbtrucking said:
I really appreciate all the help for some reason now my computer is not showing the phone in my computer so I can't access the files on it. I think it's got something to do with what I did to root it, I changed the driver for the phone. I used the file called android_winusb
Click to expand...
Click to collapse
These are the drivers you want. Sounds like what you have. It needs to be booted to see the files. Did you get it flashed?
https://developer.android.com/studio/run/win-usb.html
EDIT... Nope you got the wrong drivers, use my link.

TonikJDK said:
These are the drivers you want. Sounds like what you have. It needs to be booted to see the files. Did you get it flashed?
https://developer.android.com/studio/run/win-usb.html
EDIT... Nope you got the wrong drivers, use my link.
Click to expand...
Click to collapse
Yes I did get it booted but the usb is still not working and it's saying the file in the link you provided is not compatible.

Well it looks like this is a problem with the phone because i cant access anything when I hook it to my mac either.