I'm a a noob, and I just don't know where to look to unroot my phone. After rooting my phone which took me a while. I couldn't receive any calls. So I want to go back to stock. is there any step by step instructions written clearly or a video that could help me please. *best answer gets a prize. I really need the help.
There's nothing S-OFF can do to interfere with reception. What ROM are you running? Have you tried others? Try the stock rooted ROM here:
http://forum.xda-developers.com/showthread.php?p=16118438#post16118438
It is completely stock except for the busybox and su addons.
If that doesn't work, then you may have dmaged hardware and will need to exchange (if under warranty) or send off for repair. If so, flash it completely back to stock S-ON with this:
http://forum.xda-developers.com/showthread.php?t=1208507
Thank you for Responding! I'm using Cyanogen7 I think. But I may have to send my phone back to AT&T.
i really wish everyone would understand what root really is. it breaks my heart to see so many misguided and uninformed people.
root=system access to the ROM
'unrooting' is simply removing that access.
if you are on CM7, you cannot simply unroot. you need to flash a stock RUU and turn s-on if you are returning it....
also, you should know what rom you are running, i mean for pete's sake it tells you in 'about phone'
cm7 has a special cyanogen mod boot animation
you would had to have specifically flashed CM7 to your phone since it doesnt just magically install itself there....
how can you not know what you have done to your phone? when you say you cant make calls, are there any error messages or do you just assume that its 'root' causing it?
the more details you know about your device, the better people can help you.
I'm sorry :/ It's my phone I believe it's AT&T or the phone itself, I'm going to send it back though which is why I want it back to it's default. You're right I don't know what I was doing just following instructions and a friend online was helping me or instructing me over what to do.
teenphresh said:
I'm sorry :/ It's my phone I believe it's AT&T or the phone itself, I'm going to send it back though which is why I want it back to it's default. You're right I don't know what I was doing just following instructions and a friend online was helping me or instructing me over what to do.
Click to expand...
Click to collapse
you see the real problem here is that without knowing anything about your phone, you are assuming its a problem with the hardware. it could very well be some setting that needs to be changed. how could this be an AT&T problem? why would exchanging it fix it if it were?
instead of learning about your phone, you are wanting to do a warranty exchange on it. if you exchange it out, please make sure its completely back to defaults, with no remnants of a rom whatsoever. then with the new one, either leave it completely stock and unrooted, or learn what you are doing before you do it.
reading and comprehension go a long way.
i dislike the mentality of 'somethings not working, and rather than try and figure it out, i will just exchange it and hope the next one doesnt do it, because i dont want to take the time to figure out how i screwed it up in the first place'
Pirateghost said:
i really wish everyone would understand what root really is. it breaks my heart to see so many misguided and uninformed people.
root=system access to the ROM
'unrooting' is simply removing that access.
if you are on CM7, you cannot simply unroot. you need to flash a stock RUU and turn s-on if you are returning it....
also, you should know what rom you are running, i mean for pete's sake it tells you in 'about phone'
cm7 has a special cyanogen mod boot animation
you would had to have specifically flashed CM7 to your phone since it doesnt just magically install itself there....
how can you not know what you have done to your phone? when you say you cant make calls, are there any error messages or do you just assume that its 'root' causing it?
the more details you know about your device, the better people can help you.
Click to expand...
Click to collapse
im in this persons boat....i jus traded my iphone for this rooted inspire and i hate it and want it how it is out of the box but i have no idea what anyone is talking about im not this tech savy at all....ive clicked on a link that takes me to that forum xda developers site but the link isnt active....im lost and just want this thing back to factory.... HELP !!!!!
teenphresh said:
I'm a a noob, and I just don't know where to look to unroot my phone. After rooting my phone which took me a while. I couldn't receive any calls. So I want to go back to stock. is there any step by step instructions written clearly or a video that could help me please. *best answer gets a prize. I really need the help.
Click to expand...
Click to collapse
Use ace hack kit to return to stock. After downloading and extracting, fully read the manual. It's really easy. The manual is the best step by step guide you can get.
Ace Hack Kit
Sent from my Inspire 4G using XDA Premium.
Radio: 26.13.04.19
{
"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"
}
Related
Been on here for awhile, but never posted anything. I would post this on the original thread I used to root my first Photon Q (http://forum.xda-developers.com/showthread.php?t=1940594) but am unable to. Quick thank you to djrbliss.
My first Photon Q was rooted with Motofail2Go without any problems. Sadly, that phone met it's untimely end trying to make sure I didn't get sucked into a maelstrom and threw itself to a watery doom to protect me. It could also be said that it fell in the toilet, shorted out the battery and it was putting out 1mV while charging, but I digress.
Flash forward a few days and I have my replacement Photon Q (my provider is Sprint). Having USB debugging enabled, allowing applications from unknown sources, having the up-to-date drivers installed on my PC and connecting to said PC with the phone acting as a mass storage device, I cannot get my phone to root. I've done the bug report and gotten the distinct vibration, I've done a factory reset through the settings and 4 times through the recovery menu. I've done everything I can think of and I still cannot get root access and I miss my root.
Every time, I get [-] Exploit failed. (As indicated by my screen shot.) I'm stumped. I don't want to unlock my bootloader, mainly due to paranoia and the universe's vendetta it apparently has against me, so I'm unclear on what to try next. I have no idea why I'm having these issues because with my original phone I had absolutely no issues. Since I'm marking this as a question, I will finish off by asking a question or two:
1.) What should I try next?
2.) 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"
}
Unlock the bootloader with Motorola's official tool, flash CWM, then give yourself root.
psycho5898 said:
I don't want to unlock my bootloader, mainly due to paranoia and the universe's vendetta it apparently has against me, so I'm unclear on what to try next.
Click to expand...
Click to collapse
dpwhitty11 said:
Unlock the bootloader with Motorola's official tool, flash CWM, then give yourself root.
Click to expand...
Click to collapse
I'm trying to do it without unlocking my bootloader since I was able to do so on my last phone
You are probably on the ASA14 firmware, which has the exploit fixed.
psycho5898 said:
I'm trying to do it without unlocking my bootloader since I was able to do so on my last phone
Click to expand...
Click to collapse
Which is kinda confusing, as you said you threw it in the drink to prevent your provider from discovering you rooted it...
If you did that before, why not just do it again? lol.
Skrilax_CZ said:
You are probably on the ASA14 firmware, which has the exploit fixed.
Click to expand...
Click to collapse
^This.
The only way now is for you to unlock, or wait.
Sent from my XT897 using Tapatalk 2
arrrghhh said:
Which is kinda confusing, as you said you threw it in the drink to prevent your provider from discovering you rooted it...
If you did that before, why not just do it again? lol.
Click to expand...
Click to collapse
I don't recall saying that...? I was jazzing up saying that the phone was halfway out my pocket and fell into the toilet
Skrilax_CZ said:
You are probably on the ASA14 firmware, which has the exploit fixed.
Click to expand...
Click to collapse
Ah, I wasn't aware the exploit had been fixed; makes sense now.
Looks like I'm stuck with playing The Waiting Game: America's least favorite game show.
psycho5898 said:
Been on here for awhile, but never posted anything. I would post this on the original thread I used to root my first Photon Q (http://forum.xda-developers.com/showthread.php?t=1940594) but am unable to. Quick thank you to djrbliss.
My first Photon Q was rooted with Motofail2Go without any problems. Sadly, that phone met it's untimely end trying to make sure I didn't get sucked into a maelstrom and threw itself to a watery doom to protect me. It could also be said that it fell in the toilet, shorted out the battery and it was putting out 1mV while charging, but I digress.
Flash forward a few days and I have my replacement Photon Q (my provider is Sprint). Having USB debugging enabled, allowing applications from unknown sources, having the up-to-date drivers installed on my PC and connecting to said PC with the phone acting as a mass storage device, I cannot get my phone to root. I've done the bug report and gotten the distinct vibration, I've done a factory reset through the settings and 4 times through the recovery menu. I've done everything I can think of and I still cannot get root access and I miss my root.
Every time, I get [-] Exploit failed. (As indicated by my screen shot.) I'm stumped. I don't want to unlock my bootloader, mainly due to paranoia and the universe's vendetta it apparently has against me, so I'm unclear on what to try next. I have no idea why I'm having these issues because with my original phone I had absolutely no issues. Since I'm marking this as a question, I will finish off by asking a question or two:
1.) What should I try next?
2.) Help...?
Click to expand...
Click to collapse
I just unlocked and rooted my photon q. Had similar issues. See the thread I started a few days ago. I'm discipler. See my last couple of post on that thread to see what was the issue and how I got success.
Alright as to avoid any confusion I will be blunt:
I am not going to unlock my bootloader. I am not going to flash anything. It has already been pointed out that the previous exploit has been fixed, ergo I am stuck without root access for the time being.
I am fully aware that I can get root access by unlocking my boot loader through Motorola and dealing with fast boot and flashing CWR, however I am not interested so any further suggestions to do so will fall onto deaf ears (or blind eyes being that one would be reading).
Hello ;]
I have this same problem and that working for me.
youtube.com/watch?v=huAKkYZVj9U
I think it wheel help you.
(sorry for my English)
Cya
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.
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.
I just got a m8 , Verizon obviously. And am having trouble figuring out how to root and install recovery. I'm not a noob, but I've been out of the loop for awhile. Any help is greatly appreciated. I'm attaching a picture of my firmware settings. Thanks guys!!
{
"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 was about to tell you to go read the stickies but I don't know that they've been updated for our situation with 4.4.4.
The first way to root 4.4.4 is through weaksauce 2. That will get you what many call a "temp root" which re-roots each time upon boot and therefore has some limitations. To get "full root" you need to run sunshine which both unlocks your bootloader and turns s-off. It wasn't made to run on 4.4.4 but many people have reported it working alongside weaksauce 2. One you unlock, you can install a custom recovery and flash superSU.
Your first step is to read read read and make sure you still remember how to deal with the issues your about to open yourself up to. I know you said you're not new at this. Then you should read the weaksauce2 thread and probably the sunshine thread. Best of luck.
And to install recovery? Does it have to be done manually, or can I use goo manager or Rom manager
Enzopreme said:
And to install recovery? Does it have to be done manually, or can I use goo manager or Rom manager
Click to expand...
Click to collapse
The best and safest way is to flash recovery in fastboot. It's also very important to have fastboot working for troubleshooting. I would never flash a recovery any other way than fastboot, but it does work with TWRP Manager or Flashify.
Just make 100% sure those apps identify your phone correctly!!! Otherwise they could flash the recovery to the wrong partition and then you would be in deep doodoo for sure. ESPECIALLY if you did not set up fastboot/adb...
Get it working and use it. It'll save your bacon sooner or later.
GooManager, ROM Manager are outdated. Don't use them.
Edit: Use this version of fastboot/adb for the HTC M8: https://www.androidfilehost.com/?fid=95784891001612150
credits to @dottat
cntryby429 said:
I was about to tell you to go read the stickies but I don't know that they've been updated for our situation with 4.4.4.
The first way to root 4.4.4 is through weaksauce 2. That will get you what many call a "temp root" which re-roots each time upon boot and therefore has some limitations. To get "full root" you need to run sunshine which both unlocks your bootloader and turns s-off. It wasn't made to run on 4.4.4 but many people have reported it working alongside weaksauce 2. One you unlock, you can install a custom recovery and flash superSU.
Your first step is to read read read and make sure you still remember how to deal with the issues your about to open yourself up to. I know you said you're not new at this. Then you should read the weaksauce2 thread and probably the sunshine thread. Best of luck.
Click to expand...
Click to collapse
Do I run resistive, then I run sunshine on top of weaksauce? I can't seem to update my su binary when rooted by weaksauce...
I just looked in the weaksauce 2.0 thread and the OP tells you that it has been baked into recent versions of sunshine. My guess is that you just need to download sunshine from the "theroot.ninja" website and see if it tells you that it'll work. If so then pay for it and be done.
I'd you're having further troubles you should go to their support section on their website and I bet they'll get you straightened out.
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.