Related
I hope its a simple mistake on my end of being blind, but i have not been able to locate ( if possible ) a way to root 4.2.2 with already running wpnomoto. I was hoping i could do that and get back on SS and run a ROM. Can someone point me in the right direction?
I was on 4.4 and went back to 4.2.2.....or am i out of luck and have to just settle for rooted stock 4.4?
With me being impatient i ended up going back to 4.4 I know that safestrap does not "work" on 4.4, BUT I was able to install it and flash the eclipse ROM on the stock slot! Booted up and seems to be running like a champ! Id still like to find out in regards to the OP though.
matt99017d said:
With me being impatient i ended up going back to 4.4 I know that safestrap does not "work" on 4.4, BUT I was able to install it and flash the eclipse ROM on the stock slot! Booted up and seems to be running like a champ! Id still like to find out in regards to the OP though.
Click to expand...
Click to collapse
i rooted mine then tried to put 4.4 update, and now it keeps rebooting.. won't stop. ideas?
xpsychox said:
i rooted mine then tried to put 4.4 update, and now it keeps rebooting.. won't stop. ideas?
Click to expand...
Click to collapse
Fastboot erase cache
Sent on my Moto X
flashallthetime said:
Fastboot erase cache
Sent on my Moto X
Click to expand...
Click to collapse
so after I do the root and click install 4.4, shoudl I go to fastboot and clear cache?
xpsychox said:
so after I do the root and click install 4.4, shoudl I go to fastboot and clear cache?
Click to expand...
Click to collapse
You can not flash the 4.4 ota with any form of custom recovery or root , it will bootloop as you found out. So to stop the bootloops you need to delete the ota in the cache folder. What method did you use to root?
Sent on my Moto X
flashallthetime said:
You can not flash the 4.4 ota with any form of custom recovery or root , it will bootloop as you found out. So to stop the bootloops you need to delete the ota in the cache folder. What method did you use to root?
Sent on my Moto X
Click to expand...
Click to collapse
rock my moto.. how do i delete the cache? and i didn't flash any 4.4.. i took the OTA like i was told. per the instructions.
xpsychox said:
rock my moto.. how do i delete the cache?
Click to expand...
Click to collapse
Fastboot erase cache, read the slapmymoto thread, I believe you need to be on 4.2 to root 4.4 kitkat
Sent on my Moto X
flashallthetime said:
Fastboot erase cache, read the slapmymoto thread, I believe you need to be on 4.2 to root 4.4 kitkat
Sent on my Moto X
Click to expand...
Click to collapse
yes, i was on 4.4 and put 4.2.2 back on and gained root access and then went to install 4.4 OTA like the rockmymoto instructions say, and then i get stuck in reboot..
xpsychox said:
yes, i was on 4.4 and put 4.2.2 back on and gained root access and then went to install 4.4 OTA like the rockmymoto instructions say, and then i get stuck in reboot..
Click to expand...
Click to collapse
Read slapmymoto, it says you need to install jar files and then you can take the ota
Try this thread http://forum.xda-developers.com/showthread.php?t=2573177
Sent on my Moto X
flashallthetime said:
Read slapmymoto, it says you need to install jar files and then you can take the ota
Try this thread http://forum.xda-developers.com/showthread.php?t=2573177
Sent on my Moto X
Click to expand...
Click to collapse
i did, i adb pushed rockmymoto, with su, and slapmymoto jar files... but then it says to take OTA 4.4 and that's when it reboots indefinitely...
xpsychox said:
i did, i adb pushed rockmymoto, with su, and slapmymoto jar files... but then it says to take OTA 4.4 and that's when it reboots indefinitely...
Click to expand...
Click to collapse
Wish I could help further but lucky me , I have a unlockable boot loader, ask in the thread that I linked in my previous post
Sent on my Moto X
flashallthetime said:
Wish I could help further but lucky me , I have a unlockable boot loader, ask in the thread that I linked in my previous post
Sent on my Moto X
Click to expand...
Click to collapse
i did, they're all offline.. *sad face* ...lol
matt99017d said:
With me being impatient i ended up going back to 4.4 I know that safestrap does not "work" on 4.4, BUT I was able to install it and flash the eclipse ROM on the stock slot! Booted up and seems to be running like a champ! Id still like to find out in regards to the OP though.
Click to expand...
Click to collapse
Matt, I guess that was what you did:
1. You had a root 4.4.
2. You run MotoWpNoMo to turn off WP permenently (yes, it is permenent).
3. You flashed the unit back to 4.2.2 for a reason (but you should lost the root) .
4. With 4.2.2 and WP off, you wished you can run RockMyMoto to gain the root again (in 4.2.2).
5. But you found that RockMyMoto stopped at the Step 1 since the WP is off or "0". No more Step 2 and 3. So basically, you wasn't able to re-gain the root.
6. So you decided to reflash the unit back to 4.4.
7. Then you installed again the Safestrape.
8. And you found that SS was still working.
But, after you lost your root, how did you make the SS to work? Very interesting!
danhe said:
Matt, I guess that was what you did:
1. You had a root 4.4.
2. You run MotoWpNoMo to turn off WP permenently (yes, it is permenent).
3. You flashed the unit back to 4.2.2 for a reason (but you should lost the root) .
4. With 4.2.2 and WP off, you wished you can run RockMyMoto to gain the root again (in 4.2.2).
5. But you found that RockMyMoto stopped at the Step 1 since the WP is off or "0". No more Step 2 and 3. So basically, you wasn't able to re-gain the root.
6. So you decided to reflash the unit back to 4.4.
7. Then you installed again the Safestrape.
8. And you found that SS was still working.
But, after you lost your root, how did you make the SS to work? Very interesting!
Click to expand...
Click to collapse
Update. SS is sketchy. I tried to use it and its rough around the edges. I think I flashed my phone via RSD today around 6 times..... I ended up back on rooted 4.4
I though I read somewhere that someone had altered the program so it'll root 4.2.2.......
FYI I was able to obtain root on just 4.2.2 using slapmymoto and NOT taking the OTA. I did every step and I was able to install super su and get root access.
That means I have tried SS ON 4.2.2 AND 4.4 I got the same result on both stock Roms. The only thing I tried to flash was ECLIPSE ROM. Maybe that ROM was what was being finiky and NOT SS......MAKE SENSE?
Sent from my XT1058 using XDA Premium 4 mobile app
matt99017d said:
Update. SS is sketchy. I tried to use it and its rough around the edges. I think I flashed my phone via RSD today around 6 times..... I ended up back on rooted 4.4
I though I read somewhere that someone had altered the program so it'll root 4.2.2.......
FYI I was able to obtain root on just 4.2.2 using slapmymoto and NOT taking the OTA. I did every step and I was able to install super su and get root access.
That means I have tried SS ON 4.2.2 AND 4.4 I got the same result on both stock Roms. The only thing I tried to flash was ECLIPSE ROM. Maybe that ROM was what was being finiky and NOT SS......MAKE SENSE?
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Matt, thanks for your quick response. I found that I wasn't able to gain the root for a WP-Off unit with 4.2.2 by the "old" SlapMyMoto. jcase released a new version that works perfectly for a WP-Off unit. Thanks, jcase!
Hi,
I have a Nexus 6 that I am going to start using for work.
My work has a policy that they do not allow rooted devices.
I rooted my Nexus 6 simply to get LED LightFlow to trigger the hidden LED.
When I rooted I used the Nexus Root Toolkit from Wugfresh. I did not use a Custom Recovery and I kept the stock OS (5.0.1 LRX22C)
I really would rather not have to do a wipe/reset if I don't have to. I just need the device unrooted to adhear to company policy.
(and ideally to be able to get the 5.1 OTA when it is released later this month)
D.
GADGTGUY said:
Hi,
I have a Nexus 6 that I am going to start using for work.
My work has a policy that they do not allow rooted devices.
I rooted my Nexus 6 simply to get LED LightFlow to trigger the hidden LED.
When I rooted I used the Nexus Root Toolkit from Wugfresh. I did not use a Custom Recovery and I kept the stock OS (5.0.1 LRX22C)
I really would rather not have to do a wipe/reset if I don't have to. I just need the device unrooted to adhear to company policy.
(and ideally to be able to get the 5.1 OTA when it is released later this month)
D.
Click to expand...
Click to collapse
Um how will you work know? do they have software they put on the phones? also if your worried just use root cloak. It hides root from set apps.
You can flash the images from the Google Stock image file, and skip userdata - that will restore your phone to stock, without wiping data. Look at the stickies in the general forum for N6
the_rooter said:
Um how will you work know? do they have software they put on the phones? also if your worried just use root cloak. It hides root from set apps.
Click to expand...
Click to collapse
They push a BES client that checks. They already told me they know the phone is rooted. (big brother)
jj14 said:
You can flash the images from the Google Stock image file, and skip userdata - that will restore your phone to stock, without wiping data. Look at the stickies in the general forum for N6
Click to expand...
Click to collapse
Thanks for this info....
I just noticed that in SuperSU there is a feature called: Full unroot
Can I simply do this and presto... the phone is unrooted?
Since I kept the stock OS and didn't put a custom recovery on the phone... do you think this might do the trick?
D.
GADGTGUY said:
I just noticed that in SuperSU there is a feature called: Full unroot
Can I simply do this and presto... the phone is unrooted?
Since I kept the stock OS and didn't put a custom recovery on the phone... do you think this might do the trick?
D.
Click to expand...
Click to collapse
It may - but it still won't get you direct OTA (since OTA now checks for any change to system files)
GADGTGUY said:
[snip]I just noticed that in SuperSU there is a feature called: Full unroot
Can I simply do this and presto... the phone is unrooted?
Since I kept the stock OS and didn't put a custom recovery on the phone... do you think this might do the trick?
D.
Click to expand...
Click to collapse
Just to echo what jj14 said. The "Full unroot" option in SuperSU will remove root, but it won't (at least it hadn't on the last version of it that I tried) revert one file that root modifies, so, while you won't have root, and the BES client should work, the update checks the entire file system, so it will fail. A quick flash of only the system.img file using fastboot will remove root and leave everything else untouched.
Thanks for all the advice guys!
I appreciate the assistance... this is why this community rocks!
D.
I should have paid closer attention to the Nexus Root Toolkit from WugFresh.
There is a built in option that unroots without a refresh.
D'oh
D.
GADGTGUY said:
I should have paid closer attention to the Nexus Root Toolkit from WugFresh.
There is a built in option that unroots without a refresh.
D'oh
D.
Click to expand...
Click to collapse
Many of us would recommend you learn fastboot commands manually rather than relying on toolkits. This helps you get out of trouble when things go wrong. That said, its too late now
Forgive me if this has been asked before. I did search, but I couldn't seem to find an answer to this.
I have a dev edition model. I really want to root, but have been holding off because there are bugs with the current build of Lollipop and I'm kind of hoping Moto will release a 5.02 update soon to kill the memory leak and other issues. That being said, I have really been itching for root.
If I did root, what would I have to do to this phone to update it to the new version? Would I have to completely return to stock and wipe? Or could I ADB sideload? Seems like I was reading that you can't update at all when you're rooted, even if you disable root.
Without any idea how much longer it'll be before the next update, I'm finding it harder and harder to hold off on root, but I don't want to go through hell to get it back to stock and update it.
Thanks for any help and sorry if this has already been asked.
From what I understand, root is fine. It is installing a custom recovery that will stop you from getting the OTA. You can very easily undo root. As a matter if fact, you can pretty easily reinstall the stock recovery also.
diggitydogg said:
From what I understand, root is fine. It is installing a custom recovery that will stop you from getting the OTA. You can very easily undo root. As a matter if fact, you can pretty easily reinstall the stock recovery also.
Click to expand...
Click to collapse
Thanks for the reply.
Most of the time, that's true. I have updated a lot of phones by simply unrooting, applying the update, and rooting again, or using ADB sideload and then just rooting. But from what I have been reading about the Moto X 2014, you have to completely restore it back to stock before doing anything, even if you just use the temp boot method to root.
Is that wrong? I can't seem to find any info that confirms either way.
I've installed custom recovery, how can I reverse it and install the original recovery for update?
One advantage of root is you'll have Titanium Backup, so even if you do have to do a full wipe before applying the update, you could just update it and restore everything back quickly using TiBu. With lollipop, apparently the update file checks for the entire system checksum as a whole instead of each file so any slight modification to the system will mostly require pure stock and this is the same even with the nexus. So yeah, you most likely have to wipe your device before updating. I'd say, wait till Xposed for Lollipop is out, its almost there, once it comes out go ahead and root it, it'll at least be worth the hassle then
If you're rooted with lollipop and want to take an OTA update you can flash stock recovery and the stock system image. At that point you should still have all apps/data and be able to take a OTA update. The recovery and system files should be the exact version you already have and of course anytime you flash realize you could lose data!
Steve-x said:
If you're rooted with lollipop and want to take an OTA update you can flash stock recovery and the stock system image. At that point you should still have all apps/data and be able to take a OTA update. The recovery and system files should be the exact version you already have and of course anytime you flash realize you could lose data!
Click to expand...
Click to collapse
Right. All you need to do is flash the stock /system partition and also the recovery if you replaced it. I don't know why everyone's talking about having to wipe the entire phone with the all the stock images.
I noticed that MRA58N (Android 6.0.0 with November 1, 2015 Android security patch level) was available tonight. Since I didn't see any posts about it so I downloaded and installed it. I was able to root with the method in #1 here and install BusyBox and everything is working so far. I haven't tried the "Root without modifying /system" in #2 of that same post so I'm very interested in seeing if it still works with that method or if something has been done to block that method in MRA58N.
alryder said:
I haven't tried the "Root without modifying /system" in #2 of that same post so I'm very interested in seeing if it still works with that method or if something has been done to block that method in MRA58N.
Click to expand...
Click to collapse
I was on MRA58K with the experimental "systemless" root method. I extracted and flashed the system.img from MRA58N and still had root afterwards. No need to reflash the modified boot.img or anything. I did have to reinstall BusyBox and edit my build.prop for lower dpi, multiwindow, etc again.
The only issue I'm having is SELinux Mode Changer can't gain root access and Titanium Backup can't delete any apps. I have to do that manually with Root Explorer.
Face_Plant said:
The only issue I'm having is SELinux Mode Changer can't gain root access and Titanium Backup can't delete any apps. I have to do that manually with Root Explorer.
Click to expand...
Click to collapse
Thanks for your update. I didn't run into that issue using the root method #1 that uses the modified boot.img and SuperSU 2.52. I was able uninstall five system apps and reinstall them as user apps. Looks like there is still a bit of work to be done on the "systemless" root method before it's ready for prime time.
hmm..
can i just flash system.img if i have stock rooted with elementalX, rooted using SuperSU.46 or whatever awhile back...
darthchilli said:
hmm..
can i just flash system.img if i have stock rooted with elementalX, rooted using SuperSU.46 or whatever awhile back...
Click to expand...
Click to collapse
Unfortunately I'm not sure about that. The only method I have used to root Marshmallow is to flash the shamu-mra58k-boot.zip system.img from here and then flash SuperSU 2.52 from here. I haven't tried any other methods for rooting. The steps I used are:
- flash/upgrade to Marshmellow
- flash modified boot.img
- flash/boot TWRP and sideload v2.52
Sorry I can't be more helpful on this.
I've been waiting for this first update to give me the incentive to look at decrypting my N6, which I managed to encrypt (duh...) when I flashed MRA58K. Although to be honest I see no difference, it annoys me to know that there must be some performance and battery hit (yeah, I'm an anal retentive... ).
A second wish is to switch from SuperSU to doitright's open-source superuser just because of the news that SuperSU has been sold to a commercial company, and like many others I don't like the sound of that. But as mentioned in doitright's thread, it's not for noobs (yet), so I'm not clear on the process.
Would someone please be kind enough to lay out a step-by-step guide to achieving this? I could just flash the system.img as described above, but that wouldn't decrypt nor would it swap Superuser, and I don't want to end up yet again with the "wrong" configuration.
some reason every time i try to use systemless root it just says binaries are not installed, and it doesnt work, OR the modified boot will not flash at all
I am stock rooted 6.0 with SuperSu 2.5. At&t has finally pushed the 6.0.1 update to my phone and I need to update to get rid of that notification. I am fairly new to using Macs and am not able to use Wugfresh's toolkit anymore. Should I switch to systemless root? Do I have to do anything special in order to go from system root to systemless root? Thanks for your help.
joshpdavis80 said:
I am stock rooted 6.0 with SuperSu 2.5. At&t has finally pushed the 6.0.1 update to my phone and I need to update to get rid of that notification. I am fairly new to using Macs and am not able to use Wugfresh's toolkit anymore. Should I switch to systemless root? Do I have to do anything special in order to go from system root to systemless root? Thanks for your help.
Click to expand...
Click to collapse
Hopefully you know how to use ADB and Fastboot. If not, here's a good tutorial > http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
From where you are at, you will start by downloading the latest factory image (MMB29Q) from here > https://developers.google.com/android/nexus/images
Then fastboot flash the bootloader.img, radio.img, boot.img, and system.img. Use Method 2 (Long Method). The "flash_all" script doesn't work. Here's a tutorial for that > http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
joshpdavis80 said:
I am stock rooted 6.0 with SuperSu 2.5. At&t has finally pushed the 6.0.1 update to my phone and I need to update to get rid of that notification. I am fairly new to using Macs and am not able to use Wugfresh's toolkit anymore. Should I switch to systemless root? Do I have to do anything special in order to go from system root to systemless root? Thanks for your help.
Click to expand...
Click to collapse
Take your time and make sure you have everything set up right. Macs are known for causing issues when working with android devices. Also never use a root kit. They only cause more issues then they fix. This is the reason people wont help others that have used one of the kits. You do yourself a great injustice by using them.