Related
Pardon my ignorance -I have found some info from the forums as per the specifics of rooting and - im considering rooting my slide (as it seems 2.2 is never going to come) and go with CyanogenMod-6.1.1. Im never rooted a device but that part doesnt sound so hard (ive used linux before, etc) but my main concern question - is there a way i can make my own ROM code - or rather read out the rom code of my phone currently (pre-root), this way - should
a) i not have a good root experience (something not working right)
or
b) 2.2 comes out - via OTA
I can "go back" to my orinal rom code?
Moreover, is there a way I can go back and restore the original rom code that i backed up pre-root? I dont even know if reading out my own code can be done or if i must rely on some factory rom code available in some "slide bible" that has alluded me. Cant seem to find any slide rom bible as of yet.
Can anyone point me in the right direction or help ease my concerns...
Also ive read about "Titanium Backup" and 'Clockwork' and 'amon-ra' -- can any of these be used to backup current rom code prior to rooting ? or perhaps just after rooting?
New Bible:
http://forum.xda-developers.com/showthread.php?t=924793
Old Bible:
http://forum.xda-developers.com/showthread.php?t=704567
Old Bible definitely has stock rom. I glossed over the new one, didn't see them immediately, but I'm sure they're there.
Titanium Backup is for Apps, Clockwork and amon-ra are different types of Recovery. Within those two(or atleast Clockwork) you can make a "Nandroid Backup" which is what what you're looking for. It will backup your ROM/settings and stuff.
When you root you're going to be flashing an Engineer version that allows you to keep root, so you should make a nandroid of that. In the Bibles you'll find a link to a pretty easy root method:
http://forum.xda-developers.com/showthread.php?t=754020
Hope this helps.
i am new to this android stuff. but i flash or install new roms all the time to play with them, and in the old bible is the factory rom, i have tested it and gone back to factory and then rerooted just to see if i could. it is all possable with the little know how i have of linux.
Sent from my T-Mobile myTouch 3G Slide using the XDA mobile application powered by Tapatalk
Can some one please help
I have been trying to root my mytouch slide for quite some time. I have read post and followed directions on countless websites and even watched a few videos.
The first method i tried was the one where i had to go into command terminal, using sdk tools, and catch my phone in adb with "loop". This never worked because adb would only detect my phone when it was booted normally but when i would boot into recovery mode nothing would come up.
The second method was the one where i had to download a few files and put them in a folder in C:\ and from that directory in command terminal i had to run "my root" along with other commands that were supposed to push all the files I needed to my phones sd card. This didn't work because when i rebooted the phone into the bootloader the "ESPRIMG.zip" wasnt detected. So , im guessing, without that flashed first i cant install any other roms or upgrades.
I dont know what else to do and i would really appreciate it if someone would be able to help me finally root my fun
Sorry if i posted in the wrong spot or something.
Lenin809 said:
I have been trying to root my mytouch slide for quite some time. I have read post and followed directions on countless websites and even watched a few videos.
The first method i tried was the one where i had to go into command terminal, using sdk tools, and catch my phone in adb with "loop". This never worked because adb would only detect my phone when it was booted normally but when i would boot into recovery mode nothing would come up.
The second method was the one where i had to download a few files and put them in a folder in C:\ and from that directory in command terminal i had to run "my root" along with other commands that were supposed to push all the files I needed to my phones sd card. This didn't work because when i rebooted the phone into the bootloader the "ESPRIMG.zip" wasnt detected. So , im guessing, without that flashed first i cant install any other roms or upgrades.
I dont know what else to do and i would really appreciate it if someone would be able to help me finally root my fun
Sorry if i posted in the wrong spot or something.
Click to expand...
Click to collapse
Those two didn't work for me especially with the ota update. Try this: http://forum.xda-developers.com/showthread.php?t=754020 or http://forums.t-mobile.com/t5/myTouch-3G-Slide/Easy-root-unroot-Froyo-for-all/td-p/649239 <<This one should have screenshots w/ each step.
ima check it out
@han-shinibi
Thanks. Ima check it out and see how it goes.
Hopefully this is exactly what i need.
Ima post my results.
Also You can backup your current rom with clockwork and restore it whenever needed.
Sent from my T-Mobile myTouch 3G Slide using XDA App
If you want 2.2 OTA Go to CR's post in the development section and it should be one of the first. You have to root before installing as it is yet unreleased and it is unsigned. You can get all of the info on rooting/unrooting you need at theunlockr.com if you do not like root(which I highly doubt). There is an unrooting tutorial on theunlocker also.
Sent from my T-Mobile myTouch 3G Slide using XDA App
iDaZzLeFatHoeZz said:
If you want 2.2 OTA Go to CR's post in the development section and it should be one of the first. You have to root before installing as it is yet unreleased and it is unsigned. You can get all of the info on rooting/unrooting you need at theunlockr.com if you do not like root(which I highly doubt). There is an unrooting tutorial on theunlocker also.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
that all sounds great but my problem is that i cant root my phone so i wouldnt be able to install that anyway
@han-shinibi
thanx again for those links
i used the second one and i got it to work.
At first i was having the same problem with the hboot not recognizing the ESPRIMG.zip but after reading alot of comments someone gave me the idea to backup my sd card and to format the sd card and try again. I backup all the zip files i had from the previous attempt and i formated the card from the phone and then connected it to my laptop on "disk drive" and formatted it from windows also(I used FAT32). I uploaded all the zip files and started the process all over again and it work this time(attempt #23). Now im happily running cm6.
OK, I am far from new to this. I have unlocked many WinMo phones and now rooted many Android phones. I have an Evo that was rooted with ADB back on 2.1 and have rooted many friends phones.
I am using UnRevoked and I have installed the HBoot Drivers. Now it says connected, then Pushing Recovery, then stays there forever. I even let it stay connected overnight saying that, I woke up the next morning with the same screen, it isnt doing anything. Is there a different, better method??
UnrEVOked is the 'best' method.
Recommend this: http://forum.xda-developers.com/showthread.php?t=855515&page=3
It will have the answers for ya.
Have you installed the usb drivers, back in the day that gave me the biggest issue.
Sent from my Redeemed Incredible using the XDA App.
after reading literally thousands of posts about unrevoked and finding that most issues turn out to be simple fixes or retries, and having used it myself w no issues, this is probably the most supported and used way to root...the gold standard...not to say there arent weird curcumstances it might not work... But its a total work horse ...if you have the skills to hack the hack im sure you could use the exploit and manhandle it... I usually type something wrong, disconnect at the wrong time, or execute "doooh!" Moments, and with the swiftness....after making sure the drivers are right, give the autopilot of unrevoked another go...its really the way too do it....
Sent from my ADR6300 using XDA App
If all else fails, if you know someone with a Mac computer that version of Unrevoked is simplified and you do not need to install drivers. Simply download unrevoked and root.
A friend of mine helped me root my Inc using the Mac version and it was a quick process. I have no idea how the driver/pc version of Unrevoked works as it has steps that Mac users do not need in order to root. I've been rooted for about a month with no issues yet.
I've been using the GNex toolkit since I got my nexus and never had one issue. Even flashed stock 4.1.1 on it. My question is, why is everyone so against the toolkit? Why is it so dangerous? Please don't bash me because I came from an Atrix 2 and have only been using the nexus for a couple weeks but I'm just curious. Thanks.
Sent from my Galaxy Nexus using xda premium
http://forum.xda-developers.com/showthread.php?t=1469909
basically, the toolkits sometimes fail.. and fail hard. like at one point, the toolkit wanted to flash a verizon firmware on to a GSM phone (which can brick the phone). or something goes wrong, and the user has no idea how to fix it so the thread begins with "i used such and such toolkit, but i have no idea why my phone wont boot. HALP!"
I would like to say that the Toolkit actually is a shell of the adb command and fastboot command. That's all.
Using a toolkit means clicking a few buttons and not thinking about what you're doing.
%90 percent of all "OMG BRICKED" posts begin with "I used _______ toolkit to unlock and root. I've been on ____________ for ________ weeks and flashed ____________ and now it won't boot!"
This in itself speaks leaps-and-bounds about the user.
Using a toolkit to unlock and root should have no impact on future usage.
If you used toolkitA and she used toolkitB the information is not relevant.
This leads me to believe they think the toolkit is doing some mystical process (it isn't) specific to that "method" or "program."
Then, say, I want them to ADB push something to their phone.
Or ADB pull their SDCard to save it.
They have no idea what I'm talking about...and I (and others) are stuck trying to teach them how to set up ADB and get the drivers correctly installed with a broken device.
If you have ADB set up...and know it's working...it's 100x easier to fix things when they go wrong.
But if you're "bricked" and then tell us "adb devices" isn't showing anything and all commands list "no device found" we don't know if it's because ADB/drivers are set up incorrectly or if your phone is truly hosed to the point of being unrecognized...again, leading to more guesstimation in the debugging process.
Also, the toolkit will say "done" and not spit out any errors that help to debug if something goes wrong.
All-in-all...
Any user who chooses the toolkit over a few simple commands is going to end up with more problems...due to lack of knowledge.
Doing things manually is not only easy; but a learning process.
I'd recommend you look at my guide.
You don't need to unlock/root again or anything...
But get ADB/Fastboot set up and push a file to your phone to see how it all works.
Right packaged all in one folder with basic commands. But wouldnt the main cause of toolkit errors be user error? Because all the commands are set for each option example: if I choose to unlock the boot loader on GSM Maguro 4.1.1 then it'll 100% always unlock my boot loader correct? But if I, by mistake, choose the Toro etc and it messes me up then I could in theory blame the toolkit because I didn't pay attention therefore I would've suspected the toolkit as the culprit. So I'm saying, errors with the toolkit are all basically user errors right?
Sent from my Galaxy Nexus using xda premium
DarkJatrix said:
Right packaged all in one folder with basic commands. But wouldnt the main cause of toolkit errors be user error? Because all the commands are set for each option example: if I choose to unlock the boot loader on GSM Maguro 4.1.1 then it'll 100% always unlock my boot loader correct? But if I, by mistake, choose the Toro etc and it messes me up then I could in theory blame the toolkit because I didn't pay attention therefore I would've suspected the toolkit as the culprit. So I'm saying, errors with the toolkit are all basically user errors right?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
no. its not all user error. this is an example: http://forum.xda-developers.com/showthread.php?t=1803743
Jubakuba said:
Using a toolkit means clicking a few buttons and not thinking about what you're doing.
%90 percent of all "OMG BRICKED" posts begin with "I used _______ toolkit to unlock and root. I've been on ____________ for ________ weeks and flashed ____________ and now it won't boot!"
This in itself speaks leaps-and-bounds about the user.
Using a toolkit to unlock and root should have no impact on future usage.
If you used toolkitA and she used toolkitB the information is not relevant.
This leads me to believe they think the toolkit is doing some mystical process (it isn't) specific to that "method" or "program."
Then, say, I want them to ADB push something to their phone.
Or ADB pull their SDCard to save it.
They have no idea what I'm talking about...and I (and others) are stuck trying to teach them how to set up ADB and get the drivers correctly installed with a broken device.
If you have ADB set up...and know it's working...it's 100x easier to fix things when they go wrong.
But if you're "bricked" and then tell us "adb devices" isn't showing anything and all commands list "no device found" we don't know if it's because ADB/drivers are set up incorrectly or if your phone is truly hosed to the point of being unrecognized...again, leading to more guesstimation in the debugging process.
Also, the toolkit will say "done" and not spit out any errors that help to debug if something goes wrong.
All-in-all...
Any user who chooses the toolkit over a few simple commands is going to end up with more problems...due to lack of knowledge.
Doing things manually is not only easy; but a learning process.
I'd recommend you look at my guide.
You don't need to unlock/root again or anything...
But get ADB/Fastboot set up and push a file to your phone to see how it all works.
Click to expand...
Click to collapse
I'm very familiar with ADB I had an HTC amaze and a couple days after the release I had to learn adb really quick in unlocking the boot loader and flashing custom Roms. I just like convenience of having everything in one folder and one program. I do trust ADB but my issue has always been putting files in right folders and pushing and pulling files etc. Lol. But I appreciate the info you guys. I'll think twice before using toolkits again.
Sent from my Galaxy Nexus using xda premium
Zepius said:
no. its not all user error. this is an example: http://forum.xda-developers.com/showthread.php?t=1803743
Click to expand...
Click to collapse
Lest* better to use adb, I've used jubakuba's guide and worked flawless.
I don't hate toolkits but they seem to cause more problems rather then solve. Anyone who I see needs to root I direct them to jubakuba's thread.
Sent from my Galaxy Nexus using Tapatalk 2
withbloodskies said:
Lest* better to use adb, I've used jubakuba's guide and worked flawless.
I don't hate toolkits but they seem to cause more problems rather then solve. Anyone who I see needs to root I direct them to jubakuba's thread.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
That's what I'm saying. I am plenty smart enough to read before I flash, therefore I wouldn't of flashed that and I wouldn't of had an issue but if someone else would've flashed it then it would've technically been their fault for not paying attention. I understand that the toolkit had the mistake but if I pay close attention than I'll notice the mistakes and avoid them. Does that sou d pretty knowledgeable?
Sent from my Galaxy Nexus using xda premium
Got an Australian Gnex running 4.04. The OTS jellybean update is months away according to Vodafone AU so ive been looking into manual solution that causes the least disruption possible. Very tough diciphering the language on here. My apologies but there doesnt seem to be a specific thread that can help.
From what i have read - I can open the Bootloader and somehow flash the factory image without rooting?
Was on the dev page at google to get the latest firmware? - ive DL'd yakju Android 4.1.1 (JRO03C)
I have already unlocked the bootloader with a toolkit for mac found here on XDA. i just dont know what to do next? The file is a .tgz which ive never heard of? dont you normally copy the whole zip file to the SD card then boot into recovery and somehow flash the new firmware? Help.
bigdave78 said:
Got an Australian Gnex running 4.04. The OTS jellybean update is months away according to Vodafone AU so ive been looking into manual solution that causes the least disruption possible. Very tough diciphering the language on here. My apologies but there doesnt seem to be a specific thread that can help.
From what i have read - I can open the Bootloader and somehow flash the factory image without rooting?
Was on the dev page at google to get the latest firmware? - ive DL'd yakju Android 4.1.1 (JRO03C)
I have already unlocked the bootloader with a toolkit for mac found here on XDA. i just dont know what to do next? The file is a .tgz which ive never heard of? dont you normally copy the whole zip file to the SD card then boot into recovery and somehow flash the new firmware? Help.
Click to expand...
Click to collapse
All the info you need is in this post: http://forum.xda-developers.com/showthread.php?t=1626895
Petrovski80 said:
All the info you need is in this post: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Thanks - i had read that thread but im stuck at the directory commands. its not working on mac.
Did you download the proper platform tools for your OS?
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
Did you download the proper platform tools for your OS?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes. i dont know how use commands and directories. The thread is not clear for mac users.
The 'NEW!Install Stock Jelly Bean / Unroot to Stock Jelly Bean [Odin for Mac] ONLY GSM!' one click method didnt work.
Such a shame this has to be so complicated. Im stuck and now just have a wiped phone still on 4.04 and i cant ask any pertinent questions in the appropriate threads because im a new member.
Petrovski80 said:
Did you download the proper platform tools for your OS?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
bigdave78 said:
Yes. i dont know how use commands and directories. The thread is not clear for mac users.
The 'NEW!Install Stock Jelly Bean / Unroot to Stock Jelly Bean [Odin for Mac] ONLY GSM!' one click method didnt work.
Such a shame this has to be so complicated. Im stuck and now just have a wiped phone still on 4.04 and i cant ask any pertinent questions in the appropriate threads because im a new member.
Click to expand...
Click to collapse
Question remains - once the bootloader is unlocked - can you install the downloaded google factory image from recovery without any complex commands?
bigdave78 said:
Yes. i dont know how use commands and directories. The thread is not clear for mac users.
The 'NEW!Install Stock Jelly Bean / Unroot to Stock Jelly Bean [Odin for Mac] ONLY GSM!' one click method didnt work.
Such a shame this has to be so complicated. Im stuck and now just have a wiped phone still on 4.04 and i cant ask any pertinent questions in the appropriate threads because im a new member.
Click to expand...
Click to collapse
It is not complicated at all. If you don't know how to open a terminal window and type in commands, it has nothing to do with android or flashing. It has to do with knowing how to use your computer.
I already replied to you in the other thread: to switch directories in a terminal, you use the cd command, i.e., cd /this/is/where/my/files/are
Lack of knowledge on how to use your Mac should not be confused with anything Android... not related at all.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
It is not complicated at all. If you don't know how to open a terminal window and type in commands, it has nothing to do with android or flashing. It has to do with knowing how to use your computer.
I already replied to you in the other thread: to switch directories in a terminal, you use the cd command, i.e., cd /this/is/where/my/files/are
Lack of knowledge on how to use your Mac should not be confused with anything Android... not related at all.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I genuinely appreciate the help, but realise that 95% of computer users will never open a terminal and type a command. Ive typed your commands in terminal but its not working and i dont understand directories. If i dont ask questions ill never learn will i? I cant see your reply anywhere??
bigdave78 said:
I genuinely appreciate the help, but realise that 95% of computer users will never open a terminal and type a command. Ive typed your commands in terminal but its not working and i dont understand directories. If i dont ask questions ill never learn will i? I cant see your reply anywhere??
Click to expand...
Click to collapse
Asking questions if you don't understand is perfectly fine... and I'm willing to help. But complaining that a procedure is complicated and lengthy when it actually is not, is not cool.
As for your issue (although I've never used MacOS): if you save the files in a directory call junk, and junk is located in myname, the the command to reach junk would be something like: cd /myname/junk. Or, find a way to open a terminal in the junk directory to begin with -- I'm sure if you search any Mac help site (with something like how to open a terminal) you can easily find that out, no?
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Asking questions if you don't understand is perfectly fine... and I'm willing to help. But complaining that a procedure is complicated and lengthy when it actually is not, is not cool.
As for your issue (although I've never used MacOS): if you save the files in a directory call junk, and junk is located in myname, the the command to reach junk would be something like: cd /myname/junk. Or, find a way to open a terminal in the junk directory to begin with -- I'm sure if you search any Mac help site (with something like how to open a terminal) you can easily find that out, no?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The fact ive sat here for more than 4 hours reading through threads, searching forums, reading tech sites, asking friends, unlocking the bootloader, downloading firmware, trying desperately to make 'terminal' work with your method, and leaving posting in this forum as the last resort - is testmanet to how complicated this is to a new user - especially one on a mac system. Ive used one click root methods previously when i had access to windows - unfortunately i dont anymore. I think the guides are easy to follow as a PC user, not necessarily for a mac. Ive tried to use terminal to locate the files, i cant do it. dont understand the basic principals involved to understand the mistakes im making.
bigdave78 said:
The fact ive sat here for more than 4 hours reading through threads, searching forums, reading tech sites, asking friends, unlocking the bootloader, downloading firmware, trying desperately to make 'terminal' work with your method, and leaving posting in this forum as the last resort - is testmanet to how complicated this is to a new user - especially one on a mac system. Ive used one click root methods previously when i had access to windows - unfortunately i dont anymore. I think the guides are easy to follow as a PC user, not necessarily for a mac. Ive tried to use terminal to locate the files, i cant do it. dont understand the basic principals involved to understand the mistakes im making.
Click to expand...
Click to collapse
I think you are making it more complicated that it really is. When you open a terminal, in which directory does it open? In other words, what is the prompt that you see? THAT is the directory that you should download and extract all the files to.
That's the problem you need to fix. Read some basics about macosx. Get comfortable using it. Then proceed with flashing your gnex.
This looks like a good tutorial:
http://guides.macrumors.com/Terminal
Sent from my Galaxy Nexus using Tapatalk 2
I'm now rooted with super user acces. followed techfanatic9's guide in the Mac thread and keyed in the commands in terminal. But now how do i install the factory image from Google?Yakju-jro030c? Its not a rom is it??
Do i still need to learn terminal commands???
bigdave78 said:
I'm now rooted with super user acces. followed techfanatic9's guide in the Mac thread and keyed in the commands in terminal. But now how do i install the factory image from Google?Yakju-jro030c? Its not a rom is it??
Do i still need to learn terminal commands???
Click to expand...
Click to collapse
Another issue you are having is that you are trying too many different methods, and confusing them. There was no need to root if you are flashing a new rom.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Another issue you are having is that you are trying too many different methods, and confusing them. There was no need to root if you are flashing a new rom.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Okay, so now there is no way i can do this because im rooted? ...im a frustrated, technically struggling user that just wants to try and get jelly bean stock image - nothing more extravagant than that. ive tried to follow every instruction to the letter.....aside from having to learn terminal language for OSx, im doing my best. come on dude, not everyone has that kind of time
bigdave78 said:
Okay, so now there is no way i can do this because im rooted? ...im a frustrated, technically struggling user that just wants to try and get jelly bean stock image - nothing more extravagant than that. ive tried to follow every instruction to the letter.....aside from having to learn terminal language for OSx, im doing my best. come on dude, not everyone has that kind of time
Click to expand...
Click to collapse
You can still flash the stock jb as per my instructions. It's just that rooting made no difference - it was a wasted step.
And as I said before, you don't have to learn the commands, as I've written them out for you. You just need to find out how to save the files and open a terminal in the same folder, which doesn't seem like a difficult thing to do. Google should be able to tell you how to open a terminal in a specific folder. Or, as I mention before, save the files in the folder which you already have your terminal open.
The whole purpose of my guide was to learn -- and you are have a more difficult time than others because you have taken shortcuts (I.e. 1-click methods) in the past.
I agree, not everyone has that kind of time: I have 3 kids (with everything that comes along with that), work a high-stress, 70 hour a week job, and no IT/tech/linux/android background, but I managed.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
You can still flash the stock jb as per my instructions. It's just that rooting made no difference - it was a wasted step.
And as I said before, you don't have to learn the commands, as I've written them out for you. You just need to find out how to save the files and open a terminal in the same folder, which doesn't seem like a difficult thing to do. Google should be able to tell you how to open a terminal in a specific folder. Or, as I mention before, save the files in the folder which you already have your terminal open.
The whole purpose of my guide was to learn -- and you are have a more difficult time than others because you have taken shortcuts (I.e. 1-click methods) in the past.
I agree, not everyone has that kind of time: I have 3 kids (with everything that comes along with that), work a high-stress, 70 hour a week job, and no IT/tech/linux/android background, but I managed.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I didnt find how to move the terminal command subject and i did try many different pages via google and many different ways of phrasing the query. So i just dumped all the files onto the desktop as that was where terminal seemed to be referringand it seems to be working. im waiting for the final reboot - its taking a long time. :fingers-crossed:
bigdave78 said:
I didnt find how to move the terminal command subject and i did try many different pages via google and many different ways of phrasing the query. So i just dumped all the files onto the desktop as that was where terminal seemed to be referringand it seems to be working. im waiting for the final reboot - its taking a long time. :fingers-crossed:
Click to expand...
Click to collapse
I think you got it! The first boot will take significantly longer than usually.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
I think you got it! The first boot will take significantly longer than usually.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Still waiting. should it take 15 minutes plus??
40 minutes. Stuck on the black screen with google and the lock at the bottom?
take it this is bad news.
Excuse my complete noobishness, but can someone help me root my Galaxy Nexus but still get OTA updates from Google? I found multiple sources from here and a video from QBKing77 but nothing answer my question completely. I would be really grateful if someone with experience could help me by give me step by step instructions.
Thank you.
Rooting your phone does not disable OTA updates.
Why would you want ota if you rooted? Just flash a rooted version of the updated rom when it's released.
Sent from my Galaxy Nexus using Tapatalk 2
eqjunkie829 said:
Why would you want ota if you rooted? Just flash a rooted version of the updated rom when it's released.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I want to root just for two or three apps that require root access and still get updates from Google. I want the process: root -> get OTA update -> root again etc...
ZlateWay said:
I want to root just for two or three apps that require root access and still get updates from Google. I want the process: root -> get OTA update -> root again etc...
Click to expand...
Click to collapse
That's what I do. I don't flash ROMS, just use a few apps that require root. Install OTA Root Keeper from the play store to retain root. Run the app before installing any updates to preserve root. Then when you receive an OTA, install the update then run OTA Root keeper again to get your root back. Worked for me on Verizon Galaxy Nexus coming from 4.0.4 to 4.1.1.
Sent from my Galaxy Nexus using Tapatalk 2
The_other_ray said:
That's what I do. I don't flash ROMS, just use a few apps that require root. Install OTA Root Keeper from the play store to retain root. Run the app before installing any updates to preserve root. Then when you receive an OTA, install the update then run OTA Root keeper again to get your root back. Worked for me on Verizon Galaxy Nexus coming from 4.0.4 to 4.1.1.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
That is what I'm looking for! Can you explain to me step by step how did you did that? It would be great if you help me.
Use the guide in my sig or stickied at the top of this forum.
Only change would be fastboot boot recovery cwm.img rather than flash.
Just root the phone, and don't flash any custom recovery, then download supercurio's OTA root keeper app from the playstore, to backup your root then enable root with the same app after you receive OTA
Sent from my Galaxy Nexus using Tapatalk 2
suprakarma said:
Just root the phone, and don't flash any custom recovery, then download supercurio's OTA root keeper app from the playstore, to backup your root then enable root with the same app after you receive OTA
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Sorry for replying this late, thanks for the advice, but can you explain to me the steps that I need to use with the GNexus toolkit to root like you did? Thanks
ZlateWay said:
Sorry for replying this late, thanks for the advice, but can you explain to me the steps that I need to use with the GNexus toolkit to root like you did? Thanks
Click to expand...
Click to collapse
Don't use the toolkit?
Sent from my Galaxy Nexus
Why not?
The toolkit is SUPER easy.
Open the tool kit and the DOS window guides you through what to do, by typing numbers or letters to get the desired option. I can post the guide on when to boot in recovery mode and what the phone will do but as for the Toolkit, it's self helping. Just install it, run it and follow the on-screen instructions.
I do exactly the same as what you want successfully; I have a completely stock Nexus, but it's rooted for the use of some apps. The OTA update tells me when there is an update, I install then simply root again. I'd rather not have an app to keep root as that will be yet another app to clog up my phone's app drawer.
A lot of the custom roms aren't to my taste so I am happy to keep the stock experience
Will post again the steps when I am on my home PC.
anotherxdauser said:
Why not?
The toolkit is SUPER easy.
Open the tool kit and the DOS window guides you through what to do, by typing numbers or letters to get the desired option. I can post the guide on when to boot in recovery mode and what the phone will do but as for the Toolkit, it's self helping. Just install it, run it and follow the on-screen instructions.
I do exactly the same as what you want successfully; I have a completely stock Nexus, but it's rooted for the use of some apps. The OTA update tells me when there is an update, I install then simply root again. I'd rather not have an app to keep root as that will be yet another app to clog up my phone's app drawer.
A lot of the custom roms aren't to my taste so I am happy to keep the stock experience
Will post again the steps when I am on my home PC.
Click to expand...
Click to collapse
simply because the toolkit is an excuse not to learn the FUNDAMENTALS of owning a nexus device.
what happens when something goes wrong? do you know what the toolkit is doing behind the scenes? most of the toolkit users DONT. there are more than enough 'HALP!1!1 I BriKt mah PhoneZ!1!!oneone' to prove this is the case....
if you understand what its actually doing, you understand how useless it truly is...
Well, for starters the "fundamentals of owning a nexus device" don't include rooting at all. I know many people who use Nexus devices un-rooted and are fine.
Plus, I'm more than happy not learning too much about it as I'd rather spend my time eating cake.
Remember, not everyone here is in to tweaking settings, trying different radios, resetting their phone every 5 mins to test yet another ROM.
Some people are more than happy with the stock experience but just want root. The toolkit makes that simple.
Secondly, if the toolkit was doing things behind the scenes, I'm sure someone would have found that out and reported by now.
Thirdly, how do you know custom ROMs aren't doing the same thing? They are far more likely to be able to phone home without the owner knowing.
Fourthly, I personally tried rooting the manual way but the one line help of "just type this" I got never really worked with my phone.
Fifth, I've used the toolkit on my own phone and my partners many times, I've seen nothing bad, no bricking.
Don't see why you're so against something which makes life a lot easier for people who aren't too sure how to root the manual way?
anotherxdauser said:
Well, for starters the "fundamentals of owning a nexus device" don't include rooting at all. I know many people who use Nexus devices un-rooted and are fine.
Plus, I'm more than happy not learning too much about it as I'd rather spend my time eating cake.
Remember, not everyone here is in to tweaking settings, trying different radios, resetting their phone every 5 mins to test yet another ROM.
Some people are more than happy with the stock experience but just want root. The toolkit makes that simple.
Secondly, if the toolkit was doing things behind the scenes, I'm sure someone would have found that out and reported by now.
Thirdly, how do you know custom ROMs aren't doing the same thing? They are far more likely to be able to phone home without the owner knowing.
Fourthly, I personally tried rooting the manual way but the one line help of "just type this" I got never really worked with my phone.
Fifth, I've used the toolkit on my own phone and my partners many times, I've seen nothing bad, no bricking.
Don't see why you're so against something which makes life a lot easier for people who aren't too sure how to root the manual way?
Click to expand...
Click to collapse
And yet another person who fails at grasping why XDA exists....
Sent from my Galaxy Nexus
Actually, I do. I understand why XDA exists but I also understand the multi-uses it really has.
Not everyone who comes here has a desire to mess with their phones all the time...
If you're not a fan of the toolkit, why not flame the developer?
Here's a short guide on what the OP wanted to do.
1) Make sure phone is up to date. Make a note of your software version - probably 4.1.2 or 4.2 and build number (mine is JZO54K)
2) Turn on USB Debugging (Settings > Developer Options > USB Debugging)
3) Shut down the phone
4) Start in Bootloader (power button + vol up + vol down)
5) Run the Galaxy Nexus toolkit
This is where we use the toolkit. Read the info and select your build number. The windows will guide you through what options you have. If you want to root only, choose that option. Go through the menus and type YES to begin.
6) Phone will restart
7) After ~160 seconds, ToolKit will restart to Bootloader
8) Phone will restart
9) Toolkit will finish rooting by pushing the files to the phone.
10) Phone will restart back to Bootloader
11) Finish - Confirm in ToolKit
See pictures for further info.
Pirateghost said:
And yet another person who fails at grasping why XDA exists....
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
the toolkit also exists on xda..
k786 said:
the toolkit also exists on xda..
Click to expand...
Click to collapse
So does the person that thought I was saying the toolkit did something malicious... I never said any such thing.
Toolkits are pointless. It takes longer to learn the toolkit than it does the three commands needed to unlock and root a nexus. That's my ****ing point, yet this guy is going on about how easy the toolkit is to use. If it's so ****ing easy, why did you have to provide screenshots and instructions?
XDA-spoonfeeders.com
I miss XDA
Sent from my Galaxy Nexus
**edit**
i cannot believe that someone would actually think its NOT beneficial to understand the process, and rely solely on a toolkit...its amazing to think that there are people so wrapped up in their own little minds, that they refuse to take the time to learn to do things the right way and understand what they are doing to their device.
what happens when joe user, who only knows the toolkit, flashes a mod on his phone that was NOT intended for his phone/build/rom version, and he bootloops? he jumps on xda and posts a thread. HALP I JACKED MAH PHONE!!! how do i fix it with the toolkit?
please, for the love of tech, LEARN what it is you are doing. do us all a favor and help spread the KNOWLEDGE and stop with the damn toolkit. this website is designed for you to learn, not follow a damn prompt/menu to get instant gratification.
ZlateWay said:
Sorry for replying this late, thanks for the advice, but can you explain to me the steps that I need to use with the GNexus toolkit to root like you did? Thanks
Click to expand...
Click to collapse
Don't use a toolkit. Learn commands yourself and you won't have to worry about what a toolkit is or isn't installing.
Sent from my Galaxy Nexus using xda premium
root toolkits are fine, if you already know what you are doing. the problem with root toolkits arises when a person that has no idea what they are doing uses them and messes something up, which happens often, just read all the threads that users start asking for help, that include the words "i used a root toolkit". you dont see any these thread with the words i used fastboot or adb. usually what happens is something simple gets messed up, then the situation becomes worse because the user didnt know/learn the basics, and messed something up after. this is the problem with root toolkits, they go around you having to learn the basics. then we get all these threads about "help, i bricked my device". just taking the little time needed to learn the basics prevent this from happening.
this is a nexus device, its meant to be able to root the device easily. this is the basic procedure.. fastboot oem unlock, fastboot flash a custom recovery, flash the su binaries or custom rom in your custom recovery, reboot. that is it. it takes me 3 minutes to do this. add on a little reading beforehand, and maybe itll take you 30 minutes. much better than getting lost after using the root toolkit, or even messing up your device messing with stuff that you shouldnt. and, occasionally, the root toolkit itself can mess things up.
btw, op, you can always install an official "ota" manually, without receiving it ota, and without having root too. also, if you flash a rooted stock rom(unmodified, only root), youll still receive otas
You can unlock and root without install a custom recovery. IF you don't install any custom recovery and leave the stock one you'll continue to receive the ota updates.
Bye
Sent from my Galaxy Nexus using xda app-developers app