Related
What's the best way to get rooted. I've tried te avalauncher way, they tell me I have to be rooted to use it. I've tried the simple root OTA, but when it's suppose to take you to factory restore, my phone goes to a backup/restore screen, so it fails cause I can't restore it. Please give me assistance.
I am running 2.2 from a manual install. No root.
You have to wait until the guys here find a way for p eople to root once they have 2.2 . That could take anywhere from a few days to a few weeks
Most likely you are NOT going to be able to root since you ran the OTA update for 2.2....
That is why you should read what you are flashing and know the consequences prior to doing so. Every thread that contained the download for the 2.2 leak said that it will make you lose root and the ability ( for now ) to gain root status.
You need to wait until one of the geniuses figure out a way to do it.
Sorry about your luck.
The best way is toast method...
Good luck!
Sent from my PC36100 using XDA App
UND3RTAK3R said:
The best way is toast method...you can email me if you have any problems [email protected]
Good luck!
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Not gonna work since he used the 2.2 update man.
EVOme said:
What's the best way to get rooted. I've tried te avalauncher way, they tell me I have to be rooted to use it. I've tried the simple root OTA, but when it's suppose to take you to factory restore, my phone goes to a backup/restore screen, so it fails cause I can't restore it. Please give me assistance.
I am running 2.2 from a manual install. No root.
Click to expand...
Click to collapse
1. wrong forum, should be in Q&A
2. if you did the manual update from Sprint, you will have to wait until the devs here create a root method for stock 2.2 is developed. Any existing root method will not work at all.
EVOme said:
What's the best way to get rooted. I've tried te avalauncher way, they tell me I have to be rooted to use it. I've tried the simple root OTA, but when it's suppose to take you to factory restore, my phone goes to a backup/restore screen, so it fails cause I can't restore it. Please give me assistance.
I am running 2.2 from a manual install. No root.
Click to expand...
Click to collapse
You installed the plain OTA update? The one that says "not rooted yet" on the thread title?
For each new update, HTC tries to protect its software from being rooted. The last update required users to exploit a Flash Lite vulnerability and took a while. You will probably have to wait a long time before you can root this, since it doesn't have Flash Lite.
For future reference, root first THEN update to a rooted rom released by our devs. You can't just install Ava's rom on top of stock 2.2, it prevents you from doing so.
I'm sorry but HOW MANY posts were there saying if you want to keep root, DO NOT INSTALL THE UPDATE?? Ugh...
And yes I know this isn't constructive but sometimes people just need a slap on the back if the head.
Sent from my PC36100 using XDA App
I'm in the same boat. After trying hard to resist the urge, I gave in and installed the leak. After finding the rooted version, I tried to use the 1.47 RUU to go back but it error-ed out. I'm so bummed I can't go back. Oh well; I knew the risk I was taking though so I guess I have to live with it...
Hours my my day wasted....HOURS!!!
Where's my AR-15
Wow, just wow.
I just had a thought: If there is no method for rooting yet, then how are the stock roms being rooted?
Here we go again
Sent from my PC36100 using XDA App
bludragon742 said:
I just had a thought: If there is no method for rooting yet, then how are the stock roms being rooted?
Click to expand...
Click to collapse
By digging thru it and finding an exploit.
Which will most likely happen for the 2.2 update as well, just not as of yet.
bludragon742 said:
I just had a thought: If there is no method for rooting yet, then how are the stock roms being rooted?
Click to expand...
Click to collapse
With a ROM, you can run through the zip file and essentially take out the parts that would remove root and modify as you see fit to put on an already rooted device -- the device isn't running all the security checks on the ROM, since it's already been rooted to remove those. Much easier, almost trivial.
If you have a non-rooted device, though, you have to find a way to get the device, not the ROM, rooted. The device isn't going to take an unofficial ROM. Big difference, since you have to exploit something already on the device somehow. With the last OTA update, it was Flash Lite that could be exploited for root access to the device. With this one, no one has found a method to root the device once the OTA has been applied (and probably won't really try that hard until the official version is released, in case it closes any exploits that are in the version floating around now).
xeno314 said:
With a ROM, you can run through the zip file and essentially take out the parts that would remove root and modify as you see fit to put on an already rooted device -- the device isn't running all the security checks on the ROM, since it's already been rooted to remove those. Much easier, almost trivial.
If you have a non-rooted device, though, you have to find a way to get the device, not the ROM, rooted. The device isn't going to take an unofficial ROM. Big difference, since you have to exploit something already on the device somehow. With the last OTA update, it was Flash Lite that could be exploited for root access to the device. With this one, no one has found a method to root the device once the OTA has been applied (and probably won't really try that hard until the official version is released, in case it closes any exploits that are in the version floating around now).
Click to expand...
Click to collapse
Beat me to it and said it better.
bludragon742 said:
I'm in the same boat. After trying hard to resist the urge, I gave in and installed the leak. After finding the rooted version, I tried to use the 1.47 RUU to go back but it error-ed out. I'm so bummed I can't go back. Oh well; I knew the risk I was taking though so I guess I have to live with it...
Click to expand...
Click to collapse
I have no idea how it was "hard to resist" when AVA's rooted version showed up at 5:30pm and netarchy's showed up around 9pm. They showed up before any official sprint OTA. Lets also not forget the hundreds of posts warning people that this would happen.
bludragon742 said:
I just had a thought: If there is no method for rooting yet, then how are the stock roms being rooted?
Click to expand...
Click to collapse
The "rooting method" allows you to get into restricted areas of the phone to install stuff. The act of rooting is breaking into the phone itself, not into the rom. The rom itself is fully accessable and can be hacked up, its just getting it onto the phone is the hard part.
Essentially your phone, stock, is a box that's locked from the inside. For older versions people figured out how to unlock it, so that you can put any hacked up rom onto it. The new OTA, no one knows how to get in yet.
Don't know if that makes sense. It's pretty easy to understand if you understand OS permissions.
EDIT: what the other guy said.
bludragon742 said:
I just had a thought: If there is no method for rooting yet, then how are the stock roms being rooted?
Click to expand...
Click to collapse
Because someone takes the CONTENT of the update, and applies it piece-by-piece to an already rooted image, ignoring the bits that replace HBOOT and etc.
Mad06STi said:
I have no idea how it was "hard to resist" when AVA's rooted version showed up at 5:30pm and netarchy's showed up around 9pm. .
Click to expand...
Click to collapse
I'll tell you why. The thread gets to 200 pages. There are people saying it works, sucks, bricks, awesome, hate it, stay away, success, etc. After reading 40 pages of it you have no idea up from down. Speaking from someone that is not familiar with Android rooting. It's frustrating. Then you go to one of the other 50 threads and it's all the same.
I never saw anywhere that if I installed the leak i'd be screwed. I'm fine with that though. I have 2.2 and can wait. Just annoyed i've spent hours of my day on this.
This thread was a funny read.
Sent from my PC36100 using XDA App
I've been considering rooting my phone at some point. I read in one post that the new OTA update might make rooting impossible. Is this true?
As a follow up question- Seems from the forum posts that some people end up with various problems after flashing. Is it really worth rooting and flashing? What are the most important advantages and improvements?
Thanks
Sent from my ADR6300 using XDA App
Dude just root your phone. Having complete control over your device is reason enough to do it. Some programs don't even work without it. Rooting is simple too btw with Unrevoked3. Make sure to get unrevoked3 because unrevoked forever will void any chance at a warrenty claim.
I'm a total noobie to rooting and flashing so please excuse me if I have this wrong.
I would be fine waiting for the official OTA update and then rooting and flashing a cooked ROM but I read on some posts that rooting may not be possible after the update. The advice seems to be to run unrevokedforever to get "s-off" and gain permanent root access. My biggest concern with this is voiding my warranty. I already had to return one of these for a bad speaker.
Can I just refuse the OTA until unrevoked gets s-on?
Before you do any rooting; consider the reason you want to root your phone. If you want official OTA updates then don't bother. IF you want to have the freedom and take on the responsibility of doing whatever you want to your phone and the consequences of not fully understanding what you're doing, then root your phone.
Rooting is not for everyone, decide what you want from your phone first, then consider what you'll gain from having root.
You can re-root your phone, but like anything else it carries risks, be ready to buy a new phone for $600 when you blow this one up. Then you are ready to root for certain.
Good advice DIC. I certainly don't want to shell out the dollars for a new phone. My main reasons for rooting and flashing would be:
- Better battery life
- wifi tethering
- having control for reasons I might realize later
- fun
Will the OTA update address the first 2 issues?
Will rooting still be possible after the OTA? If so I can just enjoy the benefits of that and then root and flash if I still want to.
Rooting after the 2.2 OTA
I ran across some older Unrevoked comments that were in the vein that all of their exploits had been plugged in the 2.2 OTA so finding new ones might take time. That was a few weeks ago so who knows what they have now. So if you accept the 2.2 OTA without the S-OFF mod, then you will have to wait for Unrevoked 4(?) to find a new exploit.
S-OFF on the other hand will let you accept any official, locked down update, load you own recovery (ClockworkMod) and from there load su/Superuser.apk.
I happen to be a Linux developer, so I'm interested in unlocking the phone so I can understand the lower levels (below the Android java machine). But I am also cautious, so I would prefer to start with stock and mod the system in bits and pieces as I need and understand it.
S-OFF on the other hand will let you accept any official, locked down update, load you own recovery (ClockworkMod) and from there load su/Superuser.apk.
Click to expand...
Click to collapse
So are you saying you recommend applying forever and s-off now before accepting the OTA update?
As a "cautious" linux developer what have you done with your phone at this point?
I think I will root the phone with unrevoked3 and just install wireless tethering from the app store for now.
I would also like to update the radio for better performance. I read I can only update to 2.05 without applying s-off and that it can brick my phone if I install it twice. Is this a good idea?
If the official OTA shows up can I run it on a rooted phone? I assume I can. More importantly, do I want to?
marcmarshall said:
So are you saying you recommend applying forever and s-off now before accepting the OTA update?
As a "cautious" linux developer what have you done with your phone at this point?
Click to expand...
Click to collapse
I applied the S-OFF mod specifically because I want to use stock as a starting point rather than relying upon a rebuilt or reconstructed MOD from someone else. Not that I don't trust the developers - they do a lot of great work. But with so many files flying around and very little source code behind those mods, I rather build the pieces myself (as much as is feasible). Koush has a lot of his work available on github, for example, and you can see exactly how he goes about replacing a kernel. I've also been able to recompile the kernel from the HTC released sources - now if I can find the configuration files that the Hydra Kernel developer uses, then I can roll my own kernels - again from stock sources.
To address your second question - I've done a network port scan on my phone to identify open TCP or UDP ports and found an unidentified UDP port listening. I posted a thread and some deductive reasoning from other XDA users narrowed down the source to the new Chrome to Phone feature. I'll be able to verify this after the stock 2.2 OTA comes through, but the phone is really a little Linux system under the Java machine that "traps" most of the Android apps. Root privilege bypasses the Android security and the hardware security (NAND lock) and could allow a "root" only app to install something under the hood. The phones are trapped in Verizon's network, so they are hard to get to, but the standard firewall (iptableS) is down by default.
So as Spiderman's Uncle Ben says, "With great power comes great responsibility". If you root your phone, but do not compile your own apps/mods from source, then you must rely upon the integrity of the community and file sharing systems for the mods that you install. S-OFF will let you install stock images and then as a minimum you need a replacement recovery (ClockworkMod) and the superuser package. But from there, you can work as you see fit.
It may benefit the community to have some form of central "Modding integrity verification" system for example where source codes, update zips and md5sums are fully documented so that if you pull down a mod from a file sharing site, then you have a good idea that the file is from the original developer. Then if the developer is good with changelogs and source, the user can feel reasonably good as to the integrity what's running on the phone. It would slow down innovation however.
I like the way you think Starfire. Last night I rooted with Unrevoked3, no s-off. I've only added a few root only apps and removed a couple bloats so far. I'm concerned about not being able to root after the OTA update so I think I will stop worrying so much and apply Unrevoked forever, update the radio, and apply the leaked or a custom ROM.
I like Sense and I would like a kernal with the adaptive cpu clocking, or whatever it is called, so I can improve battery life. Any suggestions?
Thanks much............mm
If you wait for the official ota its gonna be a while until a developer group like unrevoked finds a way to root it. If you want wifi tethering and froyo now I suggest rooting.
youtube.com/user/mejdam
^has several guides on how to root upgrade to baseband 2.05 and downgrade back to stock. Most roms can run on 2.05. If you want to extend battery life I suggest installing a hydra kernal that is undervolted or kingxkernal (if you want more control in oc). Also only way to get true wifi tethering for free is through rooting.
Sent from my ADR6300 using XDA App
marcmarshall said:
I like the way you think Starfire. Last night I rooted with Unrevoked3, no s-off. I've only added a few root only apps and removed a couple bloats so far. I'm concerned about not being able to root after the OTA update so I think I will stop worrying so much and apply Unrevoked forever, update the radio, and apply the leaked or a custom ROM.
I like Sense and I would like a kernal with the adaptive cpu clocking, or whatever it is called, so I can improve battery life. Any suggestions?
Thanks much............mm
Click to expand...
Click to collapse
I played with SkyRaider 2.2 Sense and liked it a lot. 2.5.2 sounds even better although I have not tried it because (1) I have my phone S-OFF, rooted stock 2.1 with the stock 605.2 recovery waiting a few more days for the OTA and (2) there was a lot of back and forth with boot loops, sound fixes, Hulu fixes, etc. so I'm letting it settle out a bit. The SkyRaider dev does a great job with extras and themes available through ROM Manager. If the OTA takes too much longer, I may give that one a shot again - and keep looking under the hood.
I think I will play a little wait and see also. I was also leaning to skyraider based on what I had read. I might use it and then patch this kernal http://forum.xda-developers.com/showthread.php?t=760050&highlight=cpu+rom+battery . It is optimized for battery usage. I need to do some homework about it though to see if Skyraider is not already using the same optimization and that it is stable.
Thanks!
Hey guys!
I just recently gotten T-mobile's G2! I already got it unlocked by paying $8 to get the unlock code .
Soo, I have been doing a lot of reading regarding rooting, perm and temp, android , etc! I was a iphone 3GS user, so I don't have that much experience or any at all with android.
What is OTA? Does it mean "over the air" update?!
I am interested in rooting my g2. I checked the wiki out. However, there are couple of things I am not sure of.
First of all, what does stock rom mean? Is it like the original android 2.2 (fyro)? that is unmodified by T-mobile and other such carriers?
Did my G2 come with stock rom? or came with T-mobile's stock rom?
Also, I did update my G2 via "OTA" i suppose. How do I know I have the latest OTA? I am really confused about this part. I have checked various threads about it, but they were not able to clarify it for me.
Any links that would explain it, would greatly help me!
thank you guys & gals for help and replying !
Just asked this question
1. http://theunlockr.com/2010/10/20/how-to-root-the-t-mobile-g2-htc-vision-visionary-method/
2. http://theunlockr.com/2010/11/30/how-to-gain-permanent-root-and-s-off-on-the-t-mobile-g2-htc-vision/
3. (Optional Custom ROM) http://theunlockr.com/2010/11/30/how-to-load-a-custom-rom-on-the-t-mobile-g2-htc-vision/
Watch the videos most helpful. Also OTA is over the air update that for offical updates t-mobile pushes out.
You know you've got the latest OTA when no more show up
Sent from my T-Mobile G2 running Cyanogenmod.
http://lmgtfy.com/?q=android+root
Sent from a Western Union telegram.
blackknightavalon said:
http://lmgtfy.com/?q=android+root
Sent from a Western Union telegram.
Click to expand...
Click to collapse
Haha that makes me laugh every time I see it
There's a lot of great reasons to root, but a lot of great reasons also to stay with stock (like warranty). You DON'T need root to use an unlocked handset with another carrier. Just the APNs for that carrier (see Android manual for how to add one).
So, that said, the XDA wiki under HTC Vision has a lot of great info on rooting and SuperCID and custom ROMs, as does Cyanogen's site.
Stock ROM basically means "official" or "pre-loaded" ROM -- the one that the phone came with.
But before you begin anything I strongly encourage you to Google what "root" means on Linux and what it allows you to do, and ask yourself if you really need root before you start trying to get it on your G2. If you're not a hacker and just plan on using apps from the market you probably don't need it anyway. But I'll leave that decision up to you.
Thank you for all your insightful replies!
Yes, I have read regarding rooting and linux . I am sort of an hacker , since I've worked on iphone stuff.
Thanks for the links. I will have a look at them! I appreciate all your efforts.
Ok you need to set up an androidsdk environment. You need jdk for it to work. And while not necessary putting the tools directory for the sdk in the path definitely saves a lot of typing copying and pasting.
Sent from my T-Mobile G2 using XDA App
LimitsX said:
I just recently gotten T-mobile's G2!
Click to expand...
Click to collapse
Congratulations!
I already got it unlocked by paying $8 to get the unlock code .
Click to expand...
Click to collapse
$8 isn't too but but you didn't need to spend that, the recommended method for obtaining root has an (optional) side effect of unlocking the phone. You will see this referred to as the "gfree" method.
What is OTA? Does it mean "over the air" update?!
Click to expand...
Click to collapse
Yes OTA means "Over The Air" when your carrier sends an update for your phone over the cellular airwaves it's an OTA update. These updates are official an only designed for the stock ROM.
First of all, what does stock rom mean? Is it like the original android 2.2 (fyro)? that is unmodified by T-mobile and other such carriers?
Click to expand...
Click to collapse
A "Stock ROM" is simply the ROM that came installed on your phone, any phones updated by an OTA update could also be considered to be running a stock ROM. Generally it refers to the OS version your carrier and manufacturer want/expect you to have. This is opposed to a "Custom ROM" which is a customized version of Android, there are a number of different custom ROMs for the G2 each with their own features and capabilities.
Did my G2 come with stock rom? or came with T-mobile's stock rom?
Click to expand...
Click to collapse
Every phone comes with a stock ROM, by definition.
Also, I did update my G2 via "OTA" i suppose. How do I know I have the latest OTA? I am really confused about this part. I have checked various threads about it, but they were not able to clarify it for me.
Click to expand...
Click to collapse
When a new OTA update is released, it takes a little while for the update to reach all the devices. There hasn't been a new OTA for the G2 in a while and AFAIK there has only been one so far. I would expect that if you just got your phone you would have received an OTA update within a day or two, and now would be up to date. As long as you are running a stock ROM you will receive new OTAs as they are released, if you root your phone but maintain the stock ROM (the state my own G2 is in right now) you would generally want to avoid installing any OTA because the update could cause you to lose root without the ability to get it back (if the OTA fixes the security hole that allowed root to be obtained)
Regarding temp vs permanent root. When the G2 first came out people had a hard time obtaining root, They first obtained "temp root" which persisted until the phone was rebooted. With a temp root any changes you make will be gone the next time you reboot your phone, because security settings of the phone prevent those changes from actually being committed to the phone. For example if you temp root your phone and remove the built in PhotoBucket application you will see that the app is back when you reboot next. Eventually they discovered how to obtain "permanent root" which will allow you to keep your root access across reboots and allows you to make permanent changes to your phone. An essential part of permanent root is defeating the security settings that prevent permanent changes to the phones memory. It should be noted that you first need to get temp root before you can get permanent root.
Just regarding the gfree method.... it does work quite well. But it did introduce a few unexpected quirks to my G2. I went back to all stock configs and decided I didn't need root so badly afterall. But it was nice to know how easy it was to do such a thing on a phone considered at one time to be unrootable.
Sent from my T-Mobile G2 using XDA App
Good afternoon guys,
I have a few set of questions and I will be glad if someone is able to kindly help me out. Please keep in mind that I am not an android expert as far as rooting, custom roms, etc... So I ask for patience from you guys!
Now... into the questions. I got my LG G2 2 weeks ago from Sprint. Great solid phone with killer specs. I previously had a Galaxy Epic 4G Touch. I was looking into rooting my LG G2 phone. However, somewhere in an article online, I read that, if I were to root my LG, I would no longer receive OTA software updates... Like an updated android version for example.. Is that true? I dont care about loosing root after updating. I just dont want to root my phone, receive an OTA update and then mess up my phone.. So thats my first question.
Next... I've done quite a few research online on how to root the G2 from sprint. What i am currently having issues with is finding the drivers. I know I must install them prior to attempting anything else. I read that I could use the Tmobile version drivers even though I am on sprint. But no luck finding those either. Could someone provide me with a link to download the drivers? Thanks! (Windows 8)
And last... I've seen many methods on rooting this device, that at the end, was confused on which one to use. Soo.. could someone share a link of a working method to root the LG G2 from Sprint (Android 4.4.2)
Thank you guys and I will be very grateful for any help. :good:
Any change of the android operating system with ota can fail. They are looking it seems note for any excuse to break the phone if you do anything. Best idea is to make sure you can unroot, then take ota.
Best way to root is go with ioroot25. I believe it is in lg g2 general.
Sent from my Nexus 7 using Tapatalk
Thank you for your reply.
How would I unroot my G2? Would I use ioroot25? Or is there some type of app that I would have to download? Correct me if I'm wrong, but... Is it possible to unroot with SuperSU ones is installed on your phone after a sucessful root?
Thanks.! :good:
SuperSU can unroot (and temp unroot, though anybodies guess if it'll survive an OTA). There's several other temp unrooters, I often use Hide My Root (try to get some perspective on what the device *actually* works like). Otherwise, removing su, supersu, busybox (if installed) and whatever else until /system looks unmodified works. If there's custom recovery, you (as well as I) probably need to flash that back to stock as well. Or.. quite likely there will be a version around to flash without taking the actual OTA update if there isn't already (haven't checked the other thread). That'll likely be the easiest rather than bother with redoing the work to fix it up again.
Nothing is risk-free of course, but unrooted and flashed back to stock recovery it should be at least fairly unlikely to hurt anything. Of course that's often the stuff I mess up.
Robles23 said:
Good afternoon guys,
I have a few set of questions and I will be glad if someone is able to kindly help me out. Please keep in mind that I am not an android expert as far as rooting, custom roms, etc... So I ask for patience from you guys!
Now... into the questions. I got my LG G2 2 weeks ago from Sprint. Great solid phone with killer specs. I previously had a Galaxy Epic 4G Touch. I was looking into rooting my LG G2 phone. However, somewhere in an article online, I read that, if I were to root my LG, I would no longer receive OTA software updates... Like an updated android version for example.. Is that true? I dont care about loosing root after updating. I just dont want to root my phone, receive an OTA update and then mess up my phone.. So thats my first question.
Next... I've done quite a few research online on how to root the G2 from sprint. What i am currently having issues with is finding the drivers. I know I must install them prior to attempting anything else. I read that I could use the Tmobile version drivers even though I am on sprint. But no luck finding those either. Could someone provide me with a link to download the drivers? Thanks! (Windows 8)
And last... I've seen many methods on rooting this device, that at the end, was confused on which one to use. Soo.. could someone share a link of a working method to root the LG G2 from Sprint (Android 4.4.2)
Thank you guys and I will be very grateful for any help. :good:
Click to expand...
Click to collapse
Well I took a OTA update this morning not thinking.....rooted but stock rom and now my phone wont come out of recovery.....Trying to fix this now...ugg! Not fun
I've got a nexus 7 (2013) on android 6.0. Over the two years I've spent with it, I've ran into many features that require root. Now I've finally decided to do it. Right now, I'm doing it for the multi window thing.
Q.1: How long will Nexus 7 OTA updates continue to come?
Q.2: Will I get a notification that I got a system update if I'm rooted? And will I be able to keep my root while updating?
Q.3: I found a way for rooting the Nexus on Lollipop through one click( I think wugtoolkit). Will it work on Marshmallow? If not, whats the easiest way, preferably without connecting it to a computer?
Q.4: Any risks or cons? I've heard its impossible to brick a Nexus, is it true?
Thanks 
Tranquility. said:
I've got a nexus 7 (2013) on android 6.0. Over the two years I've spent with it, I've ran into many features that require root. Now I've finally decided to do it. Right now, I'm doing it for the multi window thing.
Q.1: How long will Nexus 7 OTA updates continue to come?
Q.2: Will I get a notification that I got a system update if I'm rooted? And will I be able to keep my root while updating?
Q.3: I found a way for rooting the Nexus on Lollipop through one click( I think wugtoolkit). Will it work on Marshmallow? If not, whats the easiest way, preferably without connecting it to a computer?
Q.4: Any risks or cons? I've heard its impossible to brick a Nexus, is it true?
Thanks 
Click to expand...
Click to collapse
I'm not a dev, but I have some experience rooting the N7 (2012 and 2013).
1) Well, it looks like 6.0 isn't coming to the N7 2012, so there is a good chance support for major versions will be dropped soon (within the next year?). They might continue to release patches and security fixes for 6.x a year or two after that, like they appear to be doing with the N7 2012, but this is all speculation. There are probably number crunchers looking at the sales figures and survey results to gauge interest, and there were some rumors recently of a new N7 possibly in the works. Those will both factor into whether support will continue.
2) You will get a notification, but everything I've seen has indicated that the install will fail (won't brick the tablet, but will just show an error and reboot to its previous state). What I think most people do, including me, is just flash the stock image in 'no wipe' mode and re-root after the update. You can also sideload the OTA update, depending on rooting method (I think, but haven't done this myself). Lastly, if you don't mind reconfiguring all your apps or if you have a good backup scheme, you can just do a fresh install then root. I have never had trouble flashing stock in no-wipe and re-rooting, but I've heard some people have had problems. (It's worth noting that if your bootloader hasn't been unlocked, you will have to wipe the device anyways. The unlocking survives flashing, so it's a 'one and done' thing. You only really need to lock it again if you're sending it in for warranty service.)
3) Wug's toolkit is currently borked for most people (version 2.0.6), so avoid it until the thread in the N7 development subforum has some success stories. Also, rooting in Marshmallow is possible, but seek out instructions specifically for M and use the latest versions of any linked utilities (like SuperSU and TWRP). I used Wug's toolkit 90% of the time for updating and rooting, and when it works, it's a breeze. It might be worth waiting for it to be updated to address the current issues. You can use the previous version to do some basic things and as a launchpad for manual tweaking, but the main, one click and done options will not work - I tried and was greeted with a bootloop due to an out of date SuperSU. But, in version 2.0.5 you can unlock the bootloader and flash the latest stock (haven't tried the U or V versions, but MRA58K worked fine). From there you have to root mostly manually, but there are shortcuts for some of the steps in the Advanced Utilities section.
4) It's always possible to brick a device, but it's very rare. There are 2 kinds of 'bricks'. 'Hard' brick is what most people worry about - something happens that prevents access to even the lowest level of the device. It's as if there was a hardware failure. 'Soft' bricking is what less tech literate people equate to hard bricking because to them the device is useless. In reality, it's a software issue that prevents some early stage of the boot up process. It is almost always recoverable with enough time and research. In basic computer terms, hard bricking is failing to post and soft bricking is failure of the OS to load (basically, though there are nuances). With root, you have access to everything and you're trusting whatever you install that takes advantage of that power to use it wisely. An ad blocker shouldn't need to adjust the CPU voltages. This is rare if you don't intend to overclock or mess with low level hardware tweaks. It is much more likely, but still pretty rare, to soft brick the device, which means you just have to reflash the system image. Worst case is you have to wipe the device and start over, or spend a few hours researching exactly what caused it.
Hope that helps. I'm not an obsessive ROM flasher and my experience has been only with Nexus devices, but these are my impressions.
Thanks a lot for your detailed reply.
1) I was under the impression that 6.0 would be the last updated for Nexus 7. Guess I'm wrong.
2) How long would "flashing the stock image in no wipe mode" take?
3) I'll wait then for an updated version ._.
4) Guess if I follow the steps correctly that won't happen. Prepared to take the risk.
Tranquility. said:
Thanks a lot for your detailed reply.
1) I was under the impression that 6.0 would be the last updated for Nexus 7. Guess I'm wrong.
2) How long would "flashing the stock image in no wipe mode" take?
3) I'll wait then for an updated version ._.
4) Guess if I follow the steps correctly that won't happen. Prepared to take the risk.
Click to expand...
Click to collapse
Android M is the last official update for N7 2013, the first gen N7 is done with updates. Once rooted you will not get any OTA updates anyway.
Flashing usually takes about 3-4 minutes. Booting up can take up to 10-15 min.
Just don't root on M until a stable method has been discovered.
Kay thanks.
Could you please update me when a stable way is found? Or at least provide a link where I can check myself.
You can check the marshmallow and the beta thread for updates. http://forum.xda-developers.com/apps/supersu
Tranquility. said:
Kay thanks.
Could you please update me when a stable way is found? Or at least provide a link where I can check myself.
Click to expand...
Click to collapse
You can root 6.0 pretty easy if you have fastboot installed. I've done it and can confirm it works. You just need to download the ElementalX-N7 kernel and SuperSU to your device then flash TWRP in fastboot then flash the kernel and SuperSU in TWRP. There are threads on here I believe with instructions to help you. If you need any help you can message me.
The beta SuperSU and elementalx method worked great for me and seems totally stable. I'd recommend learning fastboot/adb as mentioned. That has saved me a few times from the dumb things I've done messing around with root access.
Sent from my Nexus 7 using XDA Free mobile app
Rooting
As I mentioned in a previous post rooting using TWRP, SU I don't think fully roots
the device. When I loaded Multi-Rom, it installed in the usual fashion but only boots to the TWRP recovery utility.
In the past, one could globally root the device but the problem appears new.
Kurt