Hi,
I hope this has not been covered more than once - I've really searched for it on this forum but couldn't find anything about it.
I rooted my Moto G. All I wanted was to use the "Greenify" App and to fix a wakelok that seems to happen occasionally, getting my battery time back to ~10 days again (I hardly use the phone). I don't need root for anything else.
I am very interested in the Android L update, though, because of a couple of features I have been waiting for for very long.
And of course I would appreciate getting rid of the "update available" notification.
What is the easiest/most foolproof way for me to update my Moto G, possibly using OTA?
fertchen said:
Hi,
I hope this has not been covered more than once - I've really searched for it on this forum but couldn't find anything about it.
I rooted my Moto G. All I wanted was to use the "Greenify" App and to fix a wakelok that seems to happen occasionally, getting my battery time back to ~10 days again (I hardly use the phone). I don't need root for anything else.
I am very interested in the Android L update, though, because of a couple of features I have been waiting for for very long.
And of course I would appreciate getting rid of the "update available" notification.
What is the easiest/most foolproof way for me to update my Moto G, possibly using OTA?
Click to expand...
Click to collapse
Download VooDoo OTA RootKeeper on the Google play store, it temporary disables root. After that, you can restore root. Hope that helps.
Sent from my SM-T310
thebestiam said:
Download VooDoo OTA RootKeeper on the Google play store, it temporary disables root. After that, you can restore root. Hope that helps.
Sent from my SM-T310
Click to expand...
Click to collapse
Thanks. This seems to be intended to keep root only, though. My problem is (sorry that I was unable to clarify this in my first post) that I can not use the OTA update for my Moto G at all because it is rooted. If I try to apply the OTA update the phone will get stuck in an endless reboot-loop because of some checksum failure or so (as desribed here: http://forum.xda-developers.com/moto-g/help/android-4-4-2-to-4-4-4-failed-t2819308
Is there a foolproof way to get around this issue as well?
This should help you.
I rooted my Moto G using this excellent tutorial: http://www.swedroid.se/forum/showthread.php?t=106595
As I see it, the only reason the OTA update does not work is the fact that the recovery partition was changed and thus the checksum does not match. I also assume that I would just need to restore the stock recovery in order for the OTA updates to work again. Is that correct?
As I said, I am really not interested in any custom tinkering at all. The only thing I wanted was root access and I have grown to like Greenify. It is my understanding that I do not need CWM in order to retain root access. What I would like to achieve now is to install the OTA updates without worries. I could live with having to root the device again after each update, provided that does not involve flashing recovery and unlocking again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mokkami said:
This should help you.
Click to expand...
Click to collapse
Thanks for the pointer. But maybe there is a different way.
fertchen said:
As I said, I am really not interested in any custom tinkering at all. The only thing I wanted was root access and I have grown to like Greenify. It is my understanding that I do not need CWM in order to retain root access. What I would like to achieve now is to install the OTA updates without worries. I could live with having to root the device again after each update, provided that does not involve flashing recovery and unlocking again.
Click to expand...
Click to collapse
You could reflash stock recovery and then OTA should work if that's what it was falling over on. If you lose root and need to re-root, you can do so by reflashing the recovery installable zip version of SuperSU from acustom recovery, which of course you now won't have.
However, you can always boot into a custom recovery from a PC without actually flashing it, i.e. get into fastboot mode and do:
Code:
fastboot boot yourfavouritecustomrecovery.img
that should boot you into CWM (or whatever) temporarily without overwriting your stock recovery so you can re-root. You won't need to unlock the bootloader again.
If you upgrade to the premium version of SuperSU it has a feature that attempts to survive OTA updates that may save you having to re-root, but YMMV.
fertchen said:
Hi,
I hope this has not been covered more than once - I've really searched for it on this forum but couldn't find anything about it.
I rooted my Moto G. All I wanted was to use the "Greenify" App and to fix a wakelok that seems to happen occasionally, getting my battery time back to ~10 days again (I hardly use the phone). I don't need root for anything else.
I am very interested in the Android L update, though, because of a couple of features I have been waiting for for very long.
And of course I would appreciate getting rid of the "update available" notification.
What is the easiest/most foolproof way for me to update my Moto G, possibly using OTA?
Click to expand...
Click to collapse
You can try to update the OTA by following the steps in the OP of this Post. It worked for me
http://forum.xda-developers.com/moto-g/general/ota-file-indian-dual-sim-4-4-4-t2810166
Just follow the steps below the text:
REVERT TO STOCK WITHOUT LOSING DATA OR ANYTHING ELSE
Basically you have to do this. Restore stock, do the OTA and than reroot using superboot to root.
Phone is unlocked, rooted and had xposed modules on it
Get back to stock ROM and check for updates
You can also try to find an official 4.4.4 firmware, flash it without wiping anything except the cache partition, and re-root afterwards.
So your phone is being updated, you won't lose anything and you still get root.
I did that with my Moto G 4G/LTE and it works beautifully.
Hope that helps.
Thanks for all your input.
Going back to stock recovery did not fix the OTA update problem/boot loop.
Even though I never installed a custom ROM I ended up re-installing the stock 4.4.2 firmware (without erasing userdata) and then just applying the OTA update.
Now I tried booting into CWM (fastboot boot recovery.img) but that just leads to "waiting for device", so I flashed CWM recovery again, rooted and then restored stock recovery. Works.
And I have learnt quite a bit in the process. That's always nice.
Thank you guys, you reign supreme.
Related
Just got my new TF300T and looking to root it but at the moment, not unlock bootloader if I can help it. I've read a good bit and aznmode provided some instructions from sparkym3 on using Debugfs ([ROOT][TOOL]Debugfs automated root [09/18/2012]). I'm checking to make sure it's all applicable to my version and won't create any issues. According to the info in the post, it supports versions beyond what I'm running. It does seem like the model I received is a few updates behind - I've attached a screen capture from Settings --> About tablet to make sure I'm reading it correctly!
As I read it, it's running ICS v4.0.3 with v9.4.3.17 firmware, and has a US SKU. I am curious about the kernel version being 2.6.39.4-00001. On Asus' website, the firmware/kernel versions are 9.4.3.x and 10.4.2.x for JB & ICS...
As for rooting it (and not unlocking), I should be able to use Debugfs given the info in the screen capture, right? Just need to follow the steps of run Debugfs, install SuperSU and run it at least once, install and run OTA Rootkeeper, run my OTA update (hopefully it's to a version of JB), and run OTA Rootkeeper to restore root? I added the SuperSU step because seemed like some couldn't restore root if this wasn't done. If I were to decide to unlock the bootloader later, will rooting first create any issues?
Also is it possible to install TWRP (preferably 2.x or if necessary, would go with CWM) after rooting but before upgrading to JB? Seems like I should be able to do this via Goo Manager or... Guess this will be lost during the update, and have read it possibly prevents push/receipt of new OTA's? I like the idea of creating a nandroid before upgrading and do regular backups after. Not sure makes sense since the firmware will be updated too...though couldn't I downgrade it if for some reason the need arose?
Plus I added a post below with some add'l findings/questions. Thanks and I know a lot of questions, but bottom line is want to root (but not unlock my bootloader if can help it) without creating problems now or if I decide to unlock later on. Also would like install TWRP for creating nandroids for now and later as I get to using my tablet.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this youtube video might help
in the youtube info he has more information posted
fred99u said:
this youtube video might help
in the youtube info he has more information posted
Click to expand...
Click to collapse
Thanks for the video, though I'm a bit dizzy after watching it (he needs much better camera control, lol)! It does show preparing for, and running Debugfs from start to finish which is helpful.
Before running Debugfs though, I do want to confirm whether there are issues created by rooting and then unlocking at a later time. Had come across that though not sure now which XDA post.
Also wondering about installing TWRP now as opposed to after the JB update. I just came across a post from Krabappel2548 ([GUIDE]Upgrade your TF300t to Jellybean, recovery, root & remove bloatware[Noobproof]) that says "First we need to install the 9.4.3.30 US update to be able to upgrade to the Jellybean software." Also says not to install a custom recovery image - if it is, it'll prevent the JB update from being automatically launched. So I'll be stuck with ICS and no OTA JB update if I install TWRP beforehand? I do have an OTA update waiting to be installed but can't tell what it is...but sparkym3's post implies the JB OTA will follow without needing to do a manual update to 9.4.3.30 first. I guess I better hold off on installing TWRP until I have the OTA JB update installed unless someone can tell me it's not an issue??
Seeing one other possibility or step: Since I'm still running stock ICS with the older firmware, I could unlock the bootloader and run NVFlash to back up everything. Then proceed with rooting and TWRP along with the OTA updates. Two questions before considering this - it'll protect me from bricking my tablet, but can I restore a locked bootloader for warranty purposes if I needed to later on? And unlocking the bootloader, do I lose the OTA update ability? Wondering if so, if Goo Manager might help on updates...
Again from original post and here, multiple questions but I hope someone can answer or provide some clarity. That way I can move forward on rooting, installing TWRP, and installing JB without having to backtrack/downgrade/etc.
Thanks in advance!
Did you get your answers? Did you get rooted?
Bigjohn_S said:
Did you get your answers? Did you get rooted?
Click to expand...
Click to collapse
Thanks and yes, I used a variety of sources - reading more, posting a new thread with some more specific questions, #asus-transformer, etc. but am at next step w/questions!
I'm unlocked, rooted (OTA Rootkeeper installed and backup made), TWRP v2.3.1 installed, and nvflash backups made (several, lol!) but still running stock v9.3.4.17.
Do have an OTA pending though can't tell what it is...thinking v.30 of ICS rather than JB. Should I go ahead and let it install? Also for future stock updates, figure I need to get from ASUS and manually flash since unlocking stops new OTA's? As for root, it'll be lost and will do some more reading, but independent of OTA being ICS or JB, can get it back, right (OTA Rootkeeper if ICS update or via another method if JB)? If take OTA I figure the next time I flash, I'll need to use a blob rather than an img file (due to the bootloader being updated - blob for stock bootloader or img file if using the nvflash custom bootloader)? Was reading ASUS' method of putting unzipped update file on sdcard, insert, and update via system update...anyone using this over flashing?
Also since I've only been testing various apps, etc am thinking of going back to a clean slate. Can I run a factory reset or will that mess things up? My thought is nvflash custom bootloader would be lost but I have my backups already. Also root lost, but again can get it back via OTA Rootkeeper or rerunning debugfs. Any other concerns (guess I'd lose the OTA but not a big deal as can manually update)?
wow, the questions keep piling up. I think I will keep tracking your threads then, before undertaking this
Bigjohn_S said:
wow, the questions keep piling up. I think I will keep tracking your threads then, before undertaking this
Click to expand...
Click to collapse
Maybe I should have come back and updated my post, but after a several days I forgot the questions were still there!
I think I figured everything out that I'd asked. I went ahead with the OTA and it doesn't appear to have done anything. I'm thinking could be given I'm unlocked and think that causes it to fail. That, or it wasn't an incremental update as I remained at v9.4.3.17. May be my imagination, but my notification area seemed to change appearance after trying to run the OTA update. When have time, I'll go between nandroids and see if it's just my memory playing tricks or see if it truly did install some kind of minor update.
Factory reset did clean off my user apps, etc with the AndroidRoot custom bootloader remaining in place. It stayed rooted, just had to reinstall Superuser.
Also got some additional info from one of the AndroidRoot.mobi devs on fully updating to JB. Recommendation was to flash JB bootloader and use a custom ROM such as CM10; not do the full ASUS OTA JB update. Doing a full update apparently doesn't always go smoothly. Do find it curious given the number of theads and posts discussing manually updating to JB. But then again, seems I'm in the minority at this point having a tablet running ICS, unlocked, rooted, and nvflash access... So those posts may be for others that are still fully stock.
So no need to worry about my questions. Only thing would be to comment on proceeding with manually updating full JB OTA (via manual flashing since OTA's are disable due to being unlocked) vs only JB bootloader and a custom ROM...
wha2do said:
Maybe I should have come back and updated my post, but after a several days I forgot the questions were still there!
I think I figured everything out that I'd asked. I went ahead with the OTA and it doesn't appear to have done anything. I'm thinking could be given I'm unlocked and think that causes it to fail. That, or it wasn't an incremental update as I remained at v9.4.3.17. May be my imagination, but my notification area seemed to change appearance after trying to run the OTA update. When have time, I'll go between nandroids and see if it's just my memory playing tricks or see if it truly did install some kind of minor update.
Factory reset did clean off my user apps, etc with the AndroidRoot custom bootloader remaining in place. It stayed rooted, just had to reinstall Superuser.
Also got some additional info from one of the AndroidRoot.mobi devs on fully updating to JB. Recommendation was to flash JB bootloader and use a custom ROM such as CM10; not do the full ASUS OTA JB update. Doing a full update apparently doesn't always go smoothly. Do find it curious given the number of theads and posts discussing manually updating to JB. But then again, seems I'm in the minority at this point having a tablet running ICS, unlocked, rooted, and nvflash access... So those posts may be for others that are still fully stock.
So no need to worry about my questions. Only thing would be to comment on proceeding with manually updating full JB OTA vs only JB bootloader and a custom ROM...
Click to expand...
Click to collapse
Stock updates can be flashed otherwise stock recovery is required.
I just picked up my m8 from Verizon. Here's what it's running. Is there a way to stop it from updating to the new ota it's wanting to install?
If I try weaksauce and then firewater can I accept the ota or should I not because it will lock the boot loader down? It's always been don't accept otas when unlocked with the s3.
Can anyone help me with the steps I should use? I'm thinking weaksauce, then firewater, then twrp install, then flash su zip? Then what do I do about otas trying to install? Besides flashing a new Rom?
Also, there is a way to go back to full stock right?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
From what I've read the ota doesn't break anything that would stop you from being able to s-off. However if you want to s-off before taking the ota then you can do so. There should be a thread around here that contains the zip of the latest ota firmware and radios, etc that you can flash and be up to date without going through the hassle of returning the recovery and such to stock.
On the Verizon m8? Cause I'm reading that firewater may not work on the newest ota. Any ideas?
Nobody has any input? Surely some here have experience on this device that they got recently from Verizon?
silver04v said:
Nobody has any input? Surely some here have experience on this device that they got recently from Verizon?
Click to expand...
Click to collapse
I used Firewater on mine without doing the OTA and I'd recommend you do the same just incase.
S1L3nTShaDoWz said:
I used Firewater on mine without doing the OTA and I'd recommend you do the same just incase.
Click to expand...
Click to collapse
What did you do afterwards to prevent the ota after soff was done? Did you install twrp and flash su in recovery after?
silver04v said:
What did you do afterwards to prevent the ota after soff was done? Did you install twrp and flash su in recovery after?
Click to expand...
Click to collapse
I believe after I went S-OFF I just flashed a custom ROM. On the other hand I think flashing SuperSU would make the updates fail in the future if thats good enough to you. & Yes I did that too I think.
I know on the Galaxy S4 you could freeze the app giving you notifications about the OTA updates, not sure if you can do that on the M8 or not as I haven't really needed to do it but you could check that out too if all else fails.
Maybe I'll just stop being a new device wuss and flash clean rom. As I want stable and no fussing right now.
What about going stock? Is it possible to lock it all back up if needed?
silver04v said:
Maybe I'll just stop being a new device wuss and flash clean rom. As I want stable and no fussing right now.
What about going stock? Is it possible to lock it all back up if needed?
Click to expand...
Click to collapse
It's not really being a wuss, honestly you're quite smart to ask questions before doing stuff. Let's just say for example, you did everything with no research no questions asked and pretended you were the master of everything you didn't know YET you would eventually screw up if not immediately. Sooo congrats to you for being smart : D!
Yes I'm quite sure you can lock it back up or at least to a point where it'd be extremely hard to tell whether it was or not. If you like trying new things I'd just try a few ROM's and find one you really like before you settle with one and then just set your stuff up and enjoy it
On the other hand if you like stock and prefer it over it then you can use Xposed and get some of the cool stuff you would from a ROM or even stuff you don't see in ROM's.
S1L3nTShaDoWz said:
It's not really being a wuss, honestly you're quite smart to ask questions before doing stuff. Let's just say for example, you did everything with no research no questions asked and pretended you were the master of everything you didn't know YET you would eventually screw up if not immediately. Sooo congrats to you for being smart : D!
Yes I'm quite sure you can lock it back up or at least to a point where it'd be extremely hard to tell whether it was or not. If you like trying new things I'd just try a few ROM's and find one you really like before you settle with one and then just set your stuff up and enjoy it
On the other hand if you like stock and prefer it over it then you can use Xposed and get some of the cool stuff you would from a ROM or even stuff you don't see in ROM's.
Click to expand...
Click to collapse
Yeah, I'm all for roms, been flashing since my droidx days. HTC is just new to me. I'm coming from a galaxy s3. So this is a bit different. But I think I'm understanding things.
Just nerve racking since I just paid outright for this to keep my unlimited.
Any other suggestions?
I'm thinking my steps are going to be weaksauce, then firewater, then download twrp and flash it. Then delete weaksauce and supersu then go into twrp and flash a super su zip for permanent root. Then start with cleanrom.
Sound about right?
I did firewater after taking the ota and it worked. Any way you choose to do it is fine. But taking ota definitely does not break the possibility of s-off on vzwM8
silver04v said:
Any other suggestions?
I'm thinking my steps are going to be weaksauce, then firewater, then download twrp and flash it. Then delete weaksauce and supersu then go into twrp and flash a super su zip for permanent root. Then start with cleanrom.
Sound about right?
Click to expand...
Click to collapse
That's almost exactly like I did it, except I don't think you have to flash SuperSU after installing TWRP since you will install CleanROM anyway. The rom is rooted out of the box.
The way I understand it (and I'm also new to HTC - have done all my flashing on Asus tablets and Moto phones), flashing a rom will format and overwrite /system anyway. And that's where root lives, right?
Well I got it done. Didn't take the ota and I used weak sauce, then firewater, then fastboot flashed twrp, installed SuperSU zip and I'm off and rolling. Ready to install clean ROM. I'm loving this device.
OK so I'm not a dev and my device is the LG Stylo 2, LS775. I found a way to make the root permanent for our device then another fellow came along asking for the stock recovery so he could port twrp for the Stylo 2 and he did he used the TWRP for the LG Stylo hence why I'm here. It's flashed and booted up just fine touch controls worked great the only problems I was having was it's not reading any partitions what so ever so I cant back up anything or choose files to flash. He tried fixing it and ended up bricking his own device in the process. I'm here to see if any Stylo developer could take a look and possibly fix it he was a newer dev so I believe that's why his device got fried.anyway if you could be so kind it would be much appreciated by me and other stylo 2 owners everywhere. Here is the stock recovery for the Stylo 2 LS775 https://drive.google.com/file/d/0B4Gofg_yEN9-NHNsQ0ZHVEcwQlU/view?usp=drivesdkand here is the ported version that boots fine just doesn't mount partitions https://drive.google.com/file/d/0B4Gofg_yEN9-Z2hqNFZEUHBzNk0/view?usp=drivesdk and here is some pictures of stuff it said in twrp I couldn't take a log as it didn't read a device to save it to
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any help would be great if not go ahead and kindly ignore this post, thank you.
DirtyPISTOLA said:
OK so I'm not a dev and my device is the LG Stylo 2, LS775. I found a way to make the root permanent for our device then another fellow came along asking for the stock recovery so he could port twrp for the Stylo 2 and he did he used the TWRP for the LG Stylo hence why I'm here. It's flashed and booted up just fine touch controls worked great the only problems I was having was it's not reading any partitions what so ever so I cant back up anything or choose files to flash. He tried fixing it and ended up bricking his own device in the process. I'm here to see if any Stylo developer could take a look and possibly fix it he was a newer dev so I believe that's why his device got fried.anyway if you could be so kind it would be much appreciated by me and other stylo 2 owners everywhere. Here is the stock recovery for the Stylo 2 LS775 https://drive.google.com/file/d/0B4Gofg_yEN9-NHNsQ0ZHVEcwQlU/view?usp=drivesdkand here is the ported version that boots fine just doesn't mount partitions https://drive.google.com/file/d/0B4Gofg_yEN9-Z2hqNFZEUHBzNk0/view?usp=drivesdk and here is some pictures of stuff it said in twrp I couldn't take a log as it didn't read a device to save it to
Any help would be great if not go ahead and kindly ignore this post, thank you.
Click to expand...
Click to collapse
How did you get root? I'm on the Metro PCS variant, I'm pretty sure that the software differs enough to not work for me.
mustangtim49 said:
How did you get root? I'm on the Metro PCS variant, I'm pretty sure that the software differs enough to not work for me.
Click to expand...
Click to collapse
its pretty universal if you can get kingroot to at least temp root you should be fine follow my guide here http://forum.xda-developers.com/android/development/boost-varient-permanent-root-t3435543 all i did was get temp root from kingroot then removed kingroot and installed supersu via terminal emulatore after that was done I installed busy box and flashfire then flashed the newest su binary with flashfire if it asks you to reboot just make sure to softboot because you wont lose temp root for that you can get a soft reboot app in the play store, but follow my guide let me know if it works for you that would be great.
DirtyPISTOLA said:
its pretty universal if you can get kingroot to at least temp root you should be fine follow my guide here http://forum.xda-developers.com/android/development/boost-varient-permanent-root-t3435543 all i did was get temp root from kingroot then removed kingroot and installed supersu via terminal emulatore after that was done I installed busy box and flashfire then flashed the newest su binary with flashfire if it asks you to reboot just make sure to softboot because you wont lose temp root for that you can get a soft reboot app in the play store, but follow my guide let me know if it works for you that would be great.
Click to expand...
Click to collapse
In there lies the problem, kingroot does not even get temp root on my variant yet. I have unlocked the bootloader via fastboot already, but with no root or any other development for that matter, doesn't really mean a thing.
mustangtim49 said:
In there lies the problem, kingroot does not even get temp root on my variant yet. I have unlocked the bootloader via fastboot already, but with no root or any other development for that matter, doesn't really mean a thing.
Click to expand...
Click to collapse
Yeah that's the problem with a lot of the stylo 2 they patched temp root in v4 of there software and a lot of people updated including me but luckily my wife wanted the same phone so I gave here mine and bought a new one on v3 well GL I hope you get root soon.
Hey, ya'll!
I'm planning to root my Moto G3 XT1550 on 5.1.1.
Can you suggest the best method to root my phone and probably the safest? I tried to look around obviously, but there are too much of topics that I can't even understand.
Also what would be your suggestion? Should I upgrade it to Marshmallow then root it, or whatever.
A quick response would be highly appreciated!
Thank you
If you root it on Lollipop, you will need to restore to stock to upgrade to Marshmallow... If you are going to leave it on Lollipop, rooting it is even easier though, there is nothing special that needs to be done, flash TWRP, then flash SuperSU, and your done.
Personally, I would upgrade it as far as possible first via OTA to the latest Marshmallow, then factory reset, then root. The rooting process is well documented and easy to follow, you should have no issues.
NEVER, NEVER EVER take an OTA when rooted or having custom recovery installed, no exceptions. And backup regularily, especially prior to rooting, in TWRP.
acejavelin said:
If you root it on Lollipop, you will need to restore to stock to upgrade to Marshmallow... If you are going to leave it on Lollipop, rooting it is even easier though, there is nothing special that needs to be done, flash TWRP, then flash SuperSU, and your done.
Personally, I would upgrade it as far as possible first via OTA to the latest Marshmallow, then factory reset, then root. The rooting process is well documented and easy to follow, you should have no issues.
NEVER, NEVER EVER take an OTA when rooted or having custom recovery installed, no exceptions. And backup regularily, especially prior to rooting, in TWRP.
Click to expand...
Click to collapse
Hey mate, thank you so much for the detailed explanation. Really appreciate it!
I have upgraded to Marshmallow 6.0.1 now, so if it is not too much to ask can you link me to the rooting process which would work for my phone? also the TWRP. I'm not being lazy here, it's just I don't want to mess anything up by trying different things which I'm not even sure of.
Sorry for the BUMP!
To root stock MM the process is the same as all Moto Marshmallow devices, TWRP use r5, I wrote tutorial the link is in my sig.
acejavelin said:
To root stock MM the process is the same as all Moto Marshmallow devices, TWRP use r5, I wrote tutorial the link is in my sig.
Click to expand...
Click to collapse
I did everything mentioned in the tutorial but my phone won't start up now.
There is this message showing up everytime. Help!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can boot into TWRP but not into the system
Well, it did manage to boot up to the system after I stayed on that screen for sometime. But oh well, when I checked on Root Checker, it says it's not properly installed. And also there is no SuperSU installed.
What can be done? It can get frustrating at times.
R37X said:
Well, it did manage to boot up to the system after I stayed on that screen for sometime. But oh well, when I checked on Root Checker, it says it's not properly installed. And also there is no SuperSU installed.
What can be done? It can get frustrating at times.
Click to expand...
Click to collapse
Flash the beta one supersu the 2.62-3 one
Dude, you're amazing! I flashed the beta SuperSU and it's working fine now.
Thank you so much, really appreciate all that you have done.
Just two quick questions, how do I get rid of the bootloader warning at startup? I mean can I change it with some logo or something since the phone is rooted now?
Also, the main reason for me to root the phone is because of xposed. So shall I install that as a normal apk or do something with twrp?
R37X said:
Dude, you're amazing! I flashed the beta SuperSU and it's working fine now.
Thank you so much, really appreciate all that you have done.
Just two quick questions, how do I get rid of the bootloader warning at startup? I mean can I change it with some logo or something since the phone is rooted now?
Also, the main reason for me to root the phone is because of xposed. So shall I install that as a normal apk or do something with twrp?
Click to expand...
Click to collapse
I don't use Xposed, but my understanding is you have to flash it. Make sure to backup first.
For the boot logo you can flash an alternative one or just deal with it... The delay will still exist, it's part of having an unlocked bootloader.
Hello all!
I cannot get root on my S7 as the title states.
I have loaded the ENG BOOT to my phone:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have followed this guide: https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
with this New ROOT.BAT:
Code:
**EDIT: @jrkruse on 5/29/17 has created a new ROOT.BAT including SuperSU v2.82, it has been outlined in this post #480 of his custom rom thread. As always, please take a moment to hit the thanks button! Without the work of these amazing dev's we would NOT have root PERIOD! It is free for you, and mean's a lot to everyone involved in bringing these releases to you the public!!!
Here is latest root zip with SuperSU 2.82 (5/29/2017)
Nougat_S7_Root_2_82_All_Carriers_V1.zip
I let the phone reboot and when I open SuperSU, I receive the error "SU Binary Occupied". This happened the absolute very first time I attempted to root the phone, nothing has ever been done to the phone, it was 100% stock. I then unrooted the phone with the unroot.bat. I have been getting device disconnects when running the root.bat. My phone is connected and it is not actually disconnecting as far as I can see. I am also getting a "Protocol Error" occasionally when the script is attempting to install SuperSU. I can run the command by hand and it installs no problem, it only errors out with the script. I then use the unroot.bat and start over which the script will run fine again. The apps uninstall when the unroot.bat runs and they then re-install when the root.bat runs.
I have yet been able to root this phone successfully.
I did get the error to not show at one point after I ran the unroot.bat. I installed SuperSU v2.79 via adb cmd prompt, and then opened the app. It then gave me the SU binary needs to be updated error, which it fails at doing.
I really do not want to reset the phone as I'm not even sure that would solve anything as it didn't work the first time from stock.
I have read that there is TWRP working for the S7 but i cant tell if it's for the US version or not, I didn't look into it very deeply.
Does anyone have any advice?
Well, bit the bullet and re-flashed my phone using QH7 odin files and attempted root again. This time it has worked successfully!
It appears that there may have been something that installed funny when the upgrade to Nougat occurred as my reboot time is about 20 seconds now, compared to the 60 seconds it took previously.
Guess if you are getting the same problems when you've never rooted before, a re-flash may result in these issues resolving themselves.
eweo911 said:
Hello all!
I cannot get root on my S7 as the title states.
I have loaded the ENG BOOT to my phone:
I have followed this guide: https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
with this New ROOT.BAT:
Code:
**EDIT: @jrkruse on 5/29/17 has created a new ROOT.BAT including SuperSU v2.82, it has been outlined in this post #480 of his custom rom thread. As always, please take a moment to hit the thanks button! Without the work of these amazing dev's we would NOT have root PERIOD! It is free for you, and mean's a lot to everyone involved in bringing these releases to you the public!!!
Here is latest root zip with SuperSU 2.82 (5/29/2017)
Nougat_S7_Root_2_82_All_Carriers_V1.zip
I let the phone reboot and when I open SuperSU, I receive the error "SU Binary Occupied". This happened the absolute very first time I attempted to root the phone, nothing has ever been done to the phone, it was 100% stock. I then unrooted the phone with the unroot.bat. I have been getting device disconnects when running the root.bat. My phone is connected and it is not actually disconnecting as far as I can see. I am also getting a "Protocol Error" occasionally when the script is attempting to install SuperSU. I can run the command by hand and it installs no problem, it only errors out with the script. I then use the unroot.bat and start over which the script will run fine again. The apps uninstall when the unroot.bat runs and they then re-install when the root.bat runs.
I have yet been able to root this phone successfully.
I did get the error to not show at one point after I ran the unroot.bat. I installed SuperSU v2.79 via adb cmd prompt, and then opened the app. It then gave me the SU binary needs to be updated error, which it fails at doing.
I really do not want to reset the phone as I'm not even sure that would solve anything as it didn't work the first time from stock.
I have read that there is TWRP working for the S7 but i cant tell if it's for the US version or not, I didn't look into it very deeply.
Does anyone have any advice?
Click to expand...
Click to collapse
The TWRP is not for S7 T-mobile sm-g930t, becouse it has the bootloader locked, and no way to unlock it.
Somebody found a way to unlock bootloader on verizon s7, can it waork also with a t-mobile version???
Thanks
pippone121263 said:
Somebody found a way to unlock bootloader on verizon s7, can it waork also with a t-mobile version???
Thanks
Click to expand...
Click to collapse
Pics or it didn't happen. JK but really though where'd you see that? That's very exciting!
pippone121263 said:
Somebody found a way to unlock bootloader on verizon s7, can it waork also with a t-mobile version???
Thanks
Click to expand...
Click to collapse
I highly doubt this...
There's a lot of people who get confused with carrier unlocks and bootloader unlocks. If you know what you are talking about and aren't confused please share a link or pictures.
Was this ever resolved? I'm having the exact same problem. Even tried flashing back to prior firmware. No success.
penn263 said:
Was this ever resolved? I'm having the exact same problem. Even tried flashing back to prior firmware. No success.
Click to expand...
Click to collapse
Use the latest root script and binary...
KillerClaw321 said:
Use the latest root script and binary...
Click to expand...
Click to collapse
I used Nougat_S7_Root_2_82_All_Carriers_V1.zip like the OP. No success because it's saying SU binary occupied. Isn't that the latest?
penn263 said:
I used Nougat_S7_Root_2_82_All_Carriers_V1.zip like the OP. No success because it's saying SU binary occupied. Isn't that the latest?
Click to expand...
Click to collapse
Did you by any chance try installing tinysu?
penn263 said:
Was this ever resolved? I'm having the exact same problem. Even tried flashing back to prior firmware. No success.
Click to expand...
Click to collapse
Yes, this was resolved by flashing back to stock and attempting root again through the exact same method.