Hi all
I'm currently sitting on 2.2 and am not receiving any ota update. Friends of mine on the same network and phone have received the latest updates so I really feel my phone is being needlessly held back. I've rang HTC who say its my providers fault, while they say its htcs fault... all a bit annoying!
I've now started to consider rooting and installing android revolution.
I have a couple if q on rooting and installing something like android revolution in general...
1) can I still download all apps from market? Is there any impact here
2) from what I've read if I do get the update to 2.3.3 I can't root and will need to downgrade... is this correct?
3) is the risk of bricking your phone now non-existent? Their seems to be a lot of fixes/work arounds mentioned
4) I Havnt found it yet but is there a guide that explains the basics and differences between rooting/applying roms/kernels etc
Thanks to all for any help, I'm excited about my entrance into the rooting world
Sent from my Desire HD using XDA App
peustace said:
Hi all
I'm currently sitting on 2.2 and am not receiving any ota update. Friends of mine on the same network and phone have received the latest updates so I really feel my phone is being needlessly held back. I've rang HTC who say its my providers fault, while they say its htcs fault... all a bit annoying!
I've now started to consider rooting and installing android revolution.
I have a couple if q on rooting and installing something like android revolution in general...
1) can I still download all apps from market? Is there any impact here
2) from what I've read if I do get the update to 2.3.3 I can't root and will need to downgrade... is this correct?
3) is the risk of bricking your phone now non-existent? Their seems to be a lot of fixes/work arounds mentioned
4) I Havnt found it yet but is there a guide that explains the basics and differences between rooting/applying roms/kernels etc
Thanks to all for any help, I'm excited about my entrance into the rooting world
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I'm on ARHD too.
1. No problems at all, just the same as normal.
2. Yes you have to, you just need to make a Goldcard to downgrade if u had to. http://forum.xda-developers.com/showthread.php?t=1152233
3. Just follow instructions, and there is hardly a chance for bricking.
4. I doubt so, but the greatest fix roms give are mostly battery life, newer Android version.
Basics on Flashing/Rooting/S-Off, can be found here,
http://forum.xda-developers.com/showthread.php?t=855403
http://forum.xda-developers.com/showthread.php?t=857537
Have fun in the rooting industry. No need to purchase a newer Handset as you can get the newest android version
I had rooted my SGS3 while on 4.0.4 using the stock Samsung rom and Odin without issue no custom ROMS were installed just root access. Early August of 2013 the OTA for 4.1.2 was rolled out and I had accepted the update which was installed without issue, which apparently should not have been the case (everything I can find says OTAs will fail if you have root access, but this was not the case). I now want to either return to a full stock to get the 4.3.3 update at which point I may remain unrooted, or gain root again and update to 4.3.3 with root. I'm cautious about how to proceed here since I've read about a lot of people bricking their phones while attempting to root after 4.3.3. My primary concern is that my flash counter is tripped at 1, but I don't have root access and am not sure how to proceed with out potentially damaging my phone. So I'm essentially getting the worst of both worlds (unable to receive stock updates from carrier, no root access to update otherwise.) and don't want to be stuck on 4.1.2 for the life of this phone. I still have SuperSU installed, but when I open it it says "There is no SuperSU Binary installed and Super SU cannot install it. This is a problem!"
I have searched these forums and a few related to it, and from what I can gather I should just reroot the phone following instructions for 4.1.2, but if I want to make the jump to 4.3.3 I wasn't clear if this would be needed or not, but none of the threads I could find directly addressed the issue for the ATT SGS3 i747. The closest I found was a thread posted last month where the OP was directed to the CF Root procedures, but there was no followup after that. I'm just a little leery about what might happen if I reroot with another method and end up with duplicate files/.apks etc related to the root process on my phone.
I also wanted to be sure that rerooting using a different method wouldn't somehow damage my phone.
Can someone with some experience please advise of the safest best practice for me to either recover root and update, or remove root and update so I can start fresh later? From what I can gather this should be an easy fix, but I would prefer to rely on the expertise of someone more knowledgable as opposed to winging it on a gut feeling I will be ok.
This might come as late issue, since everybody already moved to 4.3 or 4.4.2, but the thing is I got stuck from my own insecurity to install a Custom Rom, and standing behind is starting to hurt my device.
Since it's rooted, I cannot update automatically trought Kies, but I just don't get to understand all the variables implied on flashing or installing a Custom Rom, from bootloaders, Knox, constantly appearing new versions of required software, hipertextual installation guides whose requirements link you to either obsolete utilities, or utilities for which my device became obsolete, and seas of prerrequisites whose end I cannot manage to find.
So, I would like to know if there's any short way for getting out 4.1.2. Would TriangleAway help me?
I'm interested to know if anyone is working on rooting the most current firmware?
I'm new to the scene and have read that things got tricky (possibility to brick?) a few releases back, is that correct?
I hope people are working on this device and that people who are without root get the opportunity.
Since now there is only a hardware root method available if you are on the latest firmware. You can find the specific thread in this forum. If you read something about a blown efuse, don't misunderstand this with rooting. This just means you can no more downgrade to an earlier firmware. Still, rooting via hardware is possible (but with somehow great risk of bricking your device if you don't know what you are doing).
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