Related
Annoyed with the volume bug on your Galaxy Nexus? Well, i'm very proud to present the forthcoming official fixed boot image which resolves this problem. In order to flash this boot image, you need your bootloader to be unlocked at this time (use './fastboot-windows oem unlock' (or the appropriate version for your machine, included in the download). Note that the OEM unlock sequence wipes your device.
APPLY THIS AT YOUR OWN RISK! This is still in a testing phase internally. Although it works great for us, well, you never know.
Volume Bug Fix r3 - DOWNLOAD - MD5: 292ba3630f475b2f779a19057649200a
How to use - Windows, Linux and OSX
- Download the zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume up' and 'volume down' buttons both pressed to enter the bootloader (as pictured below)
- WINDOWS - double click 'install-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-mac.sh' followed by './install-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-linux.sh' followed by './install-linux.sh'
Please don't rehost this zip file - if you want to link to the fix, please link to this topic. That's all I ask. Enjoy!
P
Thanks a lot for your effort!
Does OEM unlock touch my guarantee?
Thanks Paul, I get the phone tomorrow morning & thanks to you we already have our hands on the fix. Thanks a million!
You can reverse the unlock with lock when required;
./fastboot-windows oem lock
I'm very curious as to whether the volume bug is also fixed for the bootloader, and if it affects CPU load in any way, anyone tested something along those lines yet?
Rubu said:
I'm very curious as to whether the volume bug is also fixed for the bootloader, and if it affects CPU load in any way, anyone tested something along those lines yet?
Click to expand...
Click to collapse
Me too. Can anyone confirm?
Sent from my Sensation using XDA App
This doesn't fix the bootloader, doesn't seem to affect the device in any other way.
P
paulobrien said:
This doesn't fix the bootloader, doesn't seem to affect the device in any other way.
P
Click to expand...
Click to collapse
I'm pretty sure you have tested the fix. Have you been able to reproduce the bug with this version ? (Other than in the bootloader) One word from you and I might buy the Nexus ;-)
Paul if you dont mind i will repack it to zImage flashable mod because your stock boot.img will disable all tweaks in my ROM if people flash it.
Sent from my HTC Sensation Z710e using Tapatalk
mike1986. said:
Paul if you dont mind i will repack it to zImage flashable mod because your stock boot.img will disable all tweaks in my ROM if people flash it.
Sent from my HTC Sensation Z710e using Tapatalk
Click to expand...
Click to collapse
Sure, that's what i've done for MCR, as long as you give appropriate credit that's cool!
P
And what's new kernel version? Or what's the base number it came from?
i have just applied this patch.
will report back if this helps.
mike1986. said:
And what's new kernel version? Or what's the base number it came from?
Click to expand...
Click to collapse
Still 3.0.1.
P
Thanks in advance(Nexus on its way)
With all credits to paulobrien, who delivered this stock kernel to us, I made recovery flashable .zip with zImage file (kernel) instead of whole boot.img, because I do some changes to ramdisk (another part of boot.img) and by flashing default boot.img over my ROM you will loose all my tweaks. Also there are no changes to ramdisk, volume button fix in only zImage related. So you can grab it from here
Just flash it in recovery. You can flash it on any ROM, not only mine.
Hope we get the updated kernel source soon!
P
paulobrien said:
This doesn't fix the bootloader, doesn't seem to affect the device in any other way.
P
Click to expand...
Click to collapse
Thanks for all your hard work! Cant wait for my GN, i hope ill get it this week!
Can you pleas tell me whats wrong with the bootloader? I only know the bug with the volume but ive never read something about bootloader bug ...
Thanks in advance
lichti1901 said:
Thanks for all your hard work! Cant wait for my GN, i hope ill get it this week!
Can you pleas tell me whats wrong with the bootloader? I only know the bug with the volume but ive never read something about bootloader bug ...
Thanks in advance
Click to expand...
Click to collapse
The phone suffers from the volume bug even when it's in the bootloader. A lot of people think now it could be a hardware problem because there isn't much going on the software side in this state.
Which means if it is a hardware problem and you fix it with a software patch then it could still cause some problems under the hood. For example the phone doesn't sleep proberly while it is in a 2G area.
But according to Paul it doesn't cause any reaction on the phone. Which makes the bug really strange.
Edit: At least for me.
Paul,
The .bat file is "fastboot boot *.img", which i understand wouldn't be permanent, can we also "fastboot flash boot *.img"
Cheers
ande_uk said:
Paul,
The .bat file is "fastboot boot *.img", which i understand wouldn't be permanent, can we also "fastboot flash boot *.img"
Cheers
Click to expand...
Click to collapse
i have manually run fastboot flash boot <image> on mine, and it worked.(i also backup a copy of my boot.img before hand just incase).
i believe what paul is trying to do is just a temporary fix (running it once) untill google release a proper update.
I'm completely new to flashing and modifying my phone in any way. But the improvements I see people talking about from flashing to new ROMs are compelling me to try it out.
I was sceptical about flashing my nexus a couple months ago when some ROMs had been released but from what I'm reading now people are pretty confident with how stable they are.
I'm looking for any of the following:
Smoother/More responsive OS
Improved Battery Life
4.0.3 fixes
I'm okay with slight modifications such as the removal of the Google search bar on home screen
Thanks, and if possible could someone link me to anything that would help/guide me through flashing my nexus.
AOKP
Hey,
I was sceptoical too but rooting was the best thing I could have done.
Check out AOKP BUild 15 on these forums for a really good rom and very customised. It is stable and has been working for me perfectly. Way better than stock!
Good luck.
jd1001 said:
Hey,
I was sceptoical too but rooting was the best thing I could have done.
Check out AOKP BUild 15 on these forums for a really good rom and very customised. It is stable and has been working for me perfectly. Way better than stock!
Good luck.
Click to expand...
Click to collapse
How does it compare to CM and could you tell me about some new features that build would give me?
Also, do I still receive updates from google if I used modified ROMs? If I flash to AOKP Build 15 will I be able to update to 4.0.4 later and continue to 4.0.5 etc
edit: Is this what you are talking about? http://forum.xda-developers.com/showthread.php?t=1432408
edit 2: seems that 'AOKP' isn't mutually exclusive with 'CM', kinda shows how much I know lol
edit 3: the thread says 'Compatibility:' with i9020 and i9023 which google tells me are Nexus S phones, will it still work with my Galaxy Nexus?
Get Android Revolution HD. Stock UI with performance tweaks
Sent from my Galaxy Nexus using xda premium
Hey
Cythreill said:
How does it compare to CM and could you tell me about some new features that build would give me?
Also, do I still receive updates from google if I used modified ROMs? If I flash to AOKP Build 15 will I be able to update to 4.0.4 later and continue to 4.0.5 etc
edit: Is this what you are talking about? http://forum.xda-developers.com/showthread.php?t=1432408
edit 2: seems that 'AOKP' isn't mutually exclusive with 'CM', kinda shows how much I know lol
edit 3: the thread says 'Compatibility:' with i9020 and i9023 which google tells me are Nexus S phones, will it still work with my Galaxy Nexus?
Click to expand...
Click to collapse
This is the one I am using and it's brilliant.
http://forum.xda-developers.com/showthread.php?t=1402341
There are cool features like putting data off when you switch the screen off, saves battery. Also you can add notification toggles which are very handy.
In terms of getting future updates from Google, the devs on here always have the latest source code and modify it so when 4.0.5. is out you will have a rom on here that you can flash.
Seriously root it dude and have fun. It just gives the phone something extra and generally makes things faster.
How exactly do I put that ROM on my phone lol
I have no idea what '4. Wipe Dalvik cache.' would require me doing.
Hey
Cythreill said:
How exactly do I put that ROM on my phone lol
I have no idea what '4. Wipe Dalvik cache.' would require me doing.
Click to expand...
Click to collapse
Ok you need to look at the rooting and modding guides on here. Wiping the davlik cache is something you do when you have the phone in recovery mode. It is very easy to do and the instructions are very well written. Out the guides here:
http://forum.xda-developers.com/showthread.php?t=1392310
Good luck and if all goes well I bet you won't regret it.
jd1001 said:
This is the one I am using and it's brilliant.
http://forum.xda-developers.com/showthread.php?t=1402341
There are cool features like putting data off when you switch the screen off, saves battery. Also you can add notification toggles which are very handy.
In terms of getting future updates from Google, the devs on here always have the latest source code and modify it so when 4.0.5. is out you will have a rom on here that you can flash.
Seriously root it dude and have fun. It just gives the phone something extra and generally makes things faster.
Click to expand...
Click to collapse
So no automatic updates? I guess I can deal with that.
Also, I shall read those guides now, thank you very much for your help I'll get on rooting it right away.
Hey
Cythreill said:
So no automatic updates? I guess I can deal with that.
Also, I shall read those guides now, thank you very much for your help I'll get on rooting it right away.
Click to expand...
Click to collapse
No probs, no automatic updates but generally you will have the latest Android OS because the devs on here do such a great job at releasing them.
Have fun!
So I'm at this part of the guide
'b. Enter CWM Recovery by first entering the Fastboot mode Screen (Disconnect the usb cable (if you have one plugged in), then shut down your phone. Keep holding the 'Volume Up' and 'Volume Down' buttons and press the 'Power' button to boot the phone into FastBoot Mode), then select 'Recovery mode' by pressing the 'Volume Down' button and then press the 'Power' button to enter CMW Recovery.'
But after I select Recovery Mode, I get an android on the floor with a red triangle sign with a ! in it over the android.
What's this mean?
Also what should I use 'MSKIPS' GALAXY NEXUS TOOLKIT' for?
One of the steps under that part of the guide is 'After you have finished you can either boot straight into CWM Recovery to flash a Custom Rom (if you have already downloaded one and copied it to the root of your Internal Memory on your phone)', should I proceed with that? I have the KANGY2Pack on the root of my internal storage.
Cythreill said:
So I'm at this part of the guide
'b. Enter CWM Recovery by first entering the Fastboot mode Screen (Disconnect the usb cable (if you have one plugged in), then shut down your phone. Keep holding the 'Volume Up' and 'Volume Down' buttons and press the 'Power' button to boot the phone into FastBoot Mode), then select 'Recovery mode' by pressing the 'Volume Down' button and then press the 'Power' button to enter CMW Recovery.'
But after I select Recovery Mode, I get an android on the floor with a red triangle sign with a ! in it over the android.
What's this mean?
Also what should I use 'MSKIPS' GALAXY NEXUS TOOLKIT' for?
One of the steps under that part of the guide is 'After you have finished you can either boot straight into CWM Recovery to flash a Custom Rom (if you have already downloaded one and copied it to the root of your Internal Memory on your phone)', should I proceed with that? I have the KANGY2Pack on the root of my internal storage.
Click to expand...
Click to collapse
Yeah if you can enter recovery mode you should be able to apply a rom.
Did you root it successfully?
jd1001 said:
Yeah if you can enter recovery mode you should be able to apply a rom.
Did you root it successfully?
Click to expand...
Click to collapse
Don't think so,
http://imgur.com/WLKAu
After I went through this process, it appears my phone is just as it would be if I did a factory reset.
Ok, like I said on the PM, just start over. You are very close to having it rooted.
And get this kernel: http://forum.xda-developers.com/showthread.php?p=19794530
Will give you an extra boost (especially the appdrawer).
Don't install any 4.0.1/4.0.2 based roms like ARHD. 4.0.3 based roms like Bigxie's rom or openkang are much faster!
Gesendet von meinem Galaxy Nexus mit Tapatalk
Every time I try to install the Kangy2 zip file from within CWM Recovery I get 'installation aborted', what would cause this?
deezid said:
And get this kernel: http://forum.xda-developers.com/showthread.php?p=19794530
Will give you an extra boost (especially the appdrawer).
Don't install any 4.0.1/4.0.2 based roms like ARHD. 4.0.3 based roms like Bigxie's rom or openkang are much faster!
Gesendet von meinem Galaxy Nexus mit Tapatalk
Click to expand...
Click to collapse
How do I install a kernel? I think I know how to flash a rom (just install the zip from root storage via CWM Recovery after you've rooted/unlocked bootloader).
What different changes does a different kernel give vs different ROM?
Cythreill said:
How do I install a kernel? I think I know how to flash a rom (just install the zip from root storage via CWM Recovery after you've rooted/unlocked bootloader).
What different changes does a different kernel give vs different ROM?
Click to expand...
Click to collapse
Woo hoo! Glad you got sorted after all the private messages. Flashing the kernel ios the same as flashing a rom, the same method I mean.
Kernels vary so I would recommend Apex build five kernel, that's not to say any of the other ones are bad but just the one I am using and it works well.
Glad you got all sorted anyway dude.
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.
[TOOL] Revert To Stock ICS for the VZW Galaxy Nexus
OVERVIEW
I have created an all-in-one script that will revert your Verizon Galaxy Nexus to stock ICS (Build IMM76K). I have found some of the 'toolkits' to be awesome resources, but a bit flaky when trying to return to stock. This tool is a self-contained EXE and can be run offline as it does not need the internet during the process to download any supplemental files.
!WARNING!
This process WILL WIPE ALL DATA on your phone! You must manually backup all user data, documents and media before performing this process. I take no responsibility for any loss of data to your phone. This script is clean and has been tested, but as with all online guides, this is done at your own risk. Make sure your phone has at least 75% battery before continuing.
WHAT THIS WILL DO
Reset radio, bootloader, and software to factory versions. Unroot your phone. Remove all settings and accounts. Delete all data/apps and replace system apps with old original ones.
WHAT THIS WILL NOT DO
Relock your bootloader or make you coffee.
INSTRUCTIONS
STEP 1: Make sure your phone is UNPLUGGED from your computer, then download and install the Samsung Galaxy Nexus drivers (VZW)
STEP 2: Download/extract my Revert To Stock Tool for the VZW Galaxy Nexus
STEP 3: Power off your phone, then boot into 'Fastboot mode' by holding down both volume buttons and then the power button until you see the screen with the green "Start" arrow (shown below).
NOTE: If your phone boots up normally into your Android OS, then you did not press the buttons correctly. Power off your phone again, and repeat the process until you see the correct screen.
STEP 4: Plug your phone into your computer and let Windows install any necessary device drivers that it detects.
STEP 5: Once it is finished, run the tool (filename: VZW-GNex-RevertToStock.exe), and follow the on-screen prompts to revert your phone to stock ICS (Build IMM76K)
CONCLUSION
Let me know if you have any questions or run into any hiccups along the way. I am always willing to modify the script or the guide to make it more user-friendly.
NOTE: If you receive any virus alert notifications when extracting or running my tool, then know that they are false positives. My executable is clean.
Thread Updates:
2012-02-23:
Added verbiage describing what this script will/will not do.
crobs808 said:
**reserved for thread updates**
Click to expand...
Click to collapse
Hi. I hope this doesn't sound too noobish. I just rooted for the first time the other day using the GNex Tookit Ver. 7.8. to the AOKP JB Rom. I have a Verizon Galaxy Nexus.
Basically I need to go back to stock. It was a CLNR phone and thought it was running great for a day until I started noticing a bunch of dead pixels. So I need it back to Stock.
Is it really as simple as running your tool? Also, will it revert back to the original googe apps? b/c im having some issues with apps now on this rom?
1 last question, I understand it'll go back to stock does that mean I lose root and the bootloader becomes unlocked?
Thanks well in advance!
CorkyRogers said:
Hi. I hope this doesn't sound too noobish. I just rooted for the first time the other day using the GNex Tookit Ver. 7.8. to the AOKP JB Rom. I have a Verizon Galaxy Nexus.
Basically I need to go back to stock. It was a CLNR phone and thought it was running great for a day until I started noticing a bunch of dead pixels. So I need it back to Stock.
Is it really as simple as running your tool? Also, will it revert back to the original googe apps? b/c im having some issues with apps now on this rom?
1 last question, I understand it'll go back to stock does that mean I lose root and the bootloader becomes unlocked?
Thanks well in advance!
Click to expand...
Click to collapse
Yes, this will take you back to the original ROM which includes the original Google Apps (Gapps). Yes, you will LOSE root, but this will NOT re-lock your bootloader. Very good questions - I have updated some of the verbiage in the original post to clarify these points.
crobs808 said:
Yes, this will take you back to the original ROM which includes the original Google Apps (Gapps). Yes, you will LOSE root, but this will NOT re-lock your bootloader. Very good questions - I have updated some of the verbiage in the original post to clarify these points.
Click to expand...
Click to collapse
Ok cool. If I wanted to lock the bootloader, could I use the toolkit after I've used ur script?
CorkyRogers said:
Ok cool. If I wanted to lock the bootloader, could I use the toolkit after I've used ur script?
Click to expand...
Click to collapse
If you wanted to lock the bootloader, just boot into the bootloader and run fastboot oem lock. Don't rely on toolkits.
Edit: HA! I just realized what thread I'm in.
Cilraaz said:
Edit: HA! I just realized what thread I'm in.
Click to expand...
Click to collapse
oops?
Zepius said:
oops?
Click to expand...
Click to collapse
Hopefully this is the last question. When I unlocked/rooted I was on build IMM76Q. Would that affect returning to stock?
Zepius said:
oops?
Click to expand...
Click to collapse
No oops, but it is like walking into an Obama rally and shouting how great Romney is (or vice versa).
Cilraaz said:
No oops, but it is like walking into an Obama rally and shouting how great Romney is (or vice versa).
Click to expand...
Click to collapse
Good thing this isn't a ToolKIT then, just a tool
Not sure why someone arbitrarily rated this thread with "1" star. Kinda uncool, since this will help people.
not working
It keeps saying echo off, plug in your device. I installed the drivers and still nothing,.
harshybar said:
It keeps saying echo off, plug in your device. I installed the drivers and still nothing,.
Click to expand...
Click to collapse
Try a different port, or a different computer. Or spin up a VM if you've got one.
Not restarting
Hi! I found this thread linked in the GNex Toolkit 7.8 thread when I was looking for a solution because it failed to flash the stock image & unroot. I followed all the instructions, and pressed enter after fastboot restarted twice, and got to where it says "Flashing stock rom/system". I have now waited 20mins (the tool estimates 5mins), and my phone isn't restarting out of fastboot mode. It has a blue highlighted line on the bottom that says "Fastboot Status - Okay1515.FA02".
Should I keep waiting? re-run the tool? just try restarting my phone manually?
Please help!
Thanks!
Oh! Was running LiquidSmooth 1.5MR1 prior to starting this...no idea if that would still be working or not if I restart now...
EDIT: I got brave - restarting from fastboot manually just restarted Liquid, so it didn't rewrite the system. Some more searching, and I found a different dl link to try for the system image, put it in the right folder, and the GNex Toolkit worked like it was supposed to. I have to say, though, this tool is much less intimidating haha! Thanks!
So, I am in quite the predicament:
First of all, my phone stopped fully booting into the OS. I can get into fastboot and recovery but when I reboot the system it gets to the android screen and then goes black. Second of all, my usb port is broken.
I am pretty sure that there is nothing to be done, but if anyone has any suggestions that would be AMAZING!
mwreeves said:
So, I am in quite the predicament:
First of all, my phone stopped fully booting into the OS. I can get into fastboot and recovery but when I reboot the system it gets to the android screen and then goes black. Second of all, my usb port is broken.
I am pretty sure that there is nothing to be done, but if anyone has any suggestions that would be AMAZING!
Click to expand...
Click to collapse
Try a different USB cable and a different USB port. It takes a lot to break those ports on your phone, you may just have a bad cable.
crobs808 said:
Try a different USB cable and a different USB port. It takes a lot to break those ports on your phone, you may just have a bad cable.
Click to expand...
Click to collapse
I thought that too. I tried 3 computers and 6 cables: nothing worked. It hasn't been able to connect to a computer for a month now and it stopped charging 2 weeks ago. I have looked at replacing the port with a new mic/usb module but the phone still won't boot so it wouldn't really be worth it.
i just did this and it saved my phone!!!! thank you so much
DadamsJR said:
i just did this and it saved my phone!!!! thank you so much
Click to expand...
Click to collapse
You're welcome
crobs808 said:
You're welcome
Click to expand...
Click to collapse
I wish it were easier to find this thread!
You saved my phone after I stupidly pulled the battery during the root process from the toolkit and got stuck in a reboot loop with the Google logo showing and the little unlock icon.
charlie.sears said:
I wish it were easier to find this thread!
You saved my phone after I stupidly pulled the battery during the root process from the toolkit and got stuck in a reboot loop with the Google logo showing and the little unlock icon.
Click to expand...
Click to collapse
Asks mods to sticky it
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.