yashsingh1/xdaforums huggingface dataset:
[Droid Ultra Original Android Development] bzxzlg:
So for me, I had to make my device mount in "camera mode" to get the ADB drivers installed/activated on my laptop.

Did you get PIE loaded/installed?? If so, plug your device into your computer and run it ... Once you're rooted - temporarily because once you reboot, you've lost it - run MotoWpNoMo ... Once it reboots your device, you'll have to re-root your device with PIE - about 2 minutes or so after the reboot starts ... then MotoWpNoMo will continue and "do some stuff", rebooting your device again ... once your device reboots again, you'll have to re-root with PIE again ..... I think that's it, right?? Three (3) reboots?

Basically, everytime that MotoWpNoMo reboots your device, you'll need to re-root with PIE ... Once MotoWpNoMo says it's done, you should have permanent root!

---------- Post added at 06:08 PM ---------- Previous post was at 05:54 PM ----------

So I played with this over the weekend ... If you remove "<step operation="erase" partition="userdata" />" from the XML file (CFC-fastboot-obake-maxx_verizon-user-4.4-SU2-3-15-release-keys), your SD CARD partition won't get erased... Neither will the installed apps .... Because I was getting pressed for time, I was never able to effectively get the process to work for two reasons: 1) failed to remove SuperSU before I flashed back resulting in MotoWpNoMo failing (SuperSU kept reporting "'not supported in XBIN" and Survive was greyed out); 2) flashed back with the user data statement NOT removed and a fail because I was allowing Google to re-install apps which included, SuperSU - again resulting in MotoWpNoMo to not work correctly. What can I say, I've lost my engineer's touch at planning.

For those that aren't rooted, looking back at this it all should work with "<step operation="erase" partition="userdata" />" removed from the XML file.

If I have time this weekend, I may attempt again.
[Droid Ultra Original Android Development] rhouse1983:
I think for me it ended up being the computer I was on because I switched from my wife's computer and couldn't get it to work after 2 days and countless times of trying to my roommate's computer which worked the very first time. And the directions that were given (droid4life? sorry I don't remember the exact name) and I'm back on the newest build for droid maxx and rooted/wp off. I'm so happy I was patient with it. It works folks. If you have trouble try a different computer.
[Droid Ultra Original Android Development] GnatGoSplat:
Kind of strange. First Droid Mini on 19.6.3 I rooted, I had to follow all the steps including Safestrap to get permanent root (although I skipped installing SuperSU Pro and survival mode because it's not needed).

2nd Droid Mini on 19.6.3 that I rooted, I didn't need to do Safestrap or flashing SuperSU.zip. MotoWpNoMo installed SuperSU and it was permanent even after reboots.

Not sure what I did differently.
[Droid Ultra Original Android Development] xDroid4Lifex:
Sometimes if you time running PIE perfectly with WPNoMo the program runs normally not knowing you're actually re-rooting each time. So it installs SuperSu and the binaries directly to system after disabling write protection. If the program fails before installing SuperSu but at least disables write protection you can flash SuperSu manually through Safestrap (which is how I originally figured this out, because I never actually got WPNoMo to finish running completely)
[Droid Ultra Original Android Development] rbgCODE:
Yeah, the best setup I have found for using this method is with vmware, I was running linux in vmware and then wpnomo, first you add the device to your vmware with the devices ant top and pie it up, then you disconnect it and open wpnomo, it does its thing, you choose Yes, then it reboots, and once it reboots you have 120 seconds to get it back rooted and on the windows box, so when the phone comes back up click on the devices in your vmware player, add the droid again, once it is recognized press the up arrow ./mxn.sh (or whatever) and enter, it will reroot,

Then you disconnect it from the virtual machine, and on windows wpnomo sees it like it just booted up and has root, so it does a few more things, and another reboot, do the same by adding the device to linux vmware and running the bash script again, then disconnect and windows wpnomo sees it as a fresh boted droid with rot, finishes up its goodness and installs su for you.

After that I installed Safestrap did a backup, booted up and installed SuperSU Pro, and tested my root rebooted etc. etc. everything was fine, then I went to the store and downloaded the actual superSU application, it opens and says it has to update, you press yes, not the twrp method but regular, takes about 45 seconds and you are now updated to SuperSU 2, and pro works, and no matter how many times I have rebooted or what not my write protection is 0 and root is good to go baby!!
[Droid Ultra Original Android Development] GnatGoSplat:
Ah, that makes sense. I probably got the timing just right partly due to VMware. I didn't use VMware for any part of this, but I had it running for unrelated reasons and I don't know why, but VMware likes to grab control of my USB devices when I plug them in. Then I have to right click to disconnect from the VM and let it reconnect to the local. So that gave me time to run the root.sh script for PIE before WPNoMo started doing its thing.

I did end up installing Safestrap anyway, because I wanted to flash SuperSU 2.00 into /system since the version WPNoMo installed was 1.75 and I like it installed on /system so I don't have to reinstall the app from the store if I do a clean wipe.
[Droid Ultra Original Android Development] Cgordon17:
Will somebody please put a list of all the stuff I need to download? Include things like fast boot adb and SDK and where I need to put them. I have rooted before but don't want to mess this one up. Should I extract the SDK? If so where
[Droid Ultra Original Android Development] josuearisty:
I think this should work:

http://xdaforums.com/showthread.php?p=53189750

Enviado desde mi XT1080 mediante Tapatalk
[Droid Ultra Original Android Development] rbgCODE:
If you want to know how to disable that feature of automatically grabbing it PM me, and I can send you instructions.
[Droid Ultra Original Android Development] Cgordon17:
Will you link the adb and fast boot you used. I watched a video on someone rooting it and they have fastbook SDK and stuff in the android folder. I just need to know just to make sure
[Droid Ultra Original Android Development] Stainless316:
No Joy on MIni

Hi,

I have been trying for a couple of hours and I am not having success.

I have a brand new Verizon Motorola Mini. I have rolled it back to 19.5.3. I have a root checker that confirms that the tethered root works.

MotoWPNoMo fails every time after the first reboot. I get

Test 2: Booting device
Waiting for ADB (88/120)
must play a little while longer...

it's so cold in here
hmm, hold please
..............................................
[---------------------------------------------]
FATAL: Download updated package
If you are running the latest version, and continue to receive this error
you have a network problem. Disable firewalls, antiviri, security softwares etc
Press ENTER to exit

This is on a Win7 x64 machine. No firewalls. No antivirus.

Adb returns "error: device not found" for probably a minute after the boot. I don't seem to be able to get the pie in before MotoWPNoMo starts working again. I don't know why MotoWPNoMo fails.

Any help would be greatly appreciated.

I'm also going to go onto the MotoWPNoMo thread and see if I can request the developers to put a pause in their code so that the phone can be "re-rooted" before continuing.
[Droid Ultra Original Android Development] GnatGoSplat:
Yeah, mine will sometimes do the "device not found" thing, and then I have to go into the debugging menu and toggle debugging on/off.

For PIE, do you have a 2nd window open to issue the PIE command? After you've done PIE the first time, this is all you need to do every other time.

adb shell /data/local/atvc/root.sh

No need to do the other commands. That should save you some time and allow you to re-root it before WPNoMo starts up again.
[Droid Ultra Original Android Development] Stainless316:
It only does the device not found thing for a about a minute, then it's available. While I see "device not found" WPNoMo is waiting as well, so I figured it was just not ready to respond to adb. I'll try toggling debugging and see if it changes anything.

Yes, I do have two elevated command windows open, and the command that I am issuing is the one that runs root.sh. That command is the one that returns the device not found error.

Here's what I have done: Ran WPNoMo. When it got to the first reboot it waits. While it is waiting I try to run the root.sh. I get device not found for about a minute. I just sit in that command window and use up-arrow to re-issue the command 2-3 times a second while I wait. As soon as it is accepted, WPNoMo stops waiting (not sure who starts first). Fails every time in exactly the same way.

Toggling debugging did not change anything... should I reboot between toggling off and toggling on?
[Droid Ultra Original Android Development] Cgordon17:
HELP

Will somebody please make a video on how to do the whole process? I mean like showing where to download EVERYTHING like sdk and adb and where to put it all and what to extract. I just need to watch on how to do the whole thing because i can mess this up. I still need to revert back to 19.5.3 so im at the beginning. If somebody can guide me to being able to do this whole thing i got $10.

---------- Post added at 07:55 PM ---------- Previous post was at 07:52 PM ----------

Will somebody please make a video on how to do the whole process? I mean like showing where to download EVERYTHING like sdk and adb and where to put it all and what to extract. I just need to watch on how to do the whole thing because i can mess this up. I still need to revert back to 19.5.3 so im at the beginning. If somebody can guide me to being able to do this whole thing i got $10. If you can just tell me everything i need to download like sdk adb fastboot and all and what code to type and when I would appreciate it a lot
[Droid Ultra Original Android Development] Cgordon17:
Do I need to extract this whole file that has adb, fast boot and all in it?
[Droid Ultra Original Android Development] Cgordon17:
Checking for updates failed

I was doing the steps as above and wasnt doing great as i couldnt get w/p to 0. Now whenever i try to run wpnomo it starts and fails at checking for updates. Do you know why its doing that now?
[Droid Ultra Original Android Development] xDroid4Lifex:
Not sure, maybe try deleting and re-downloading WPNoMo?

---------- Post added at 06:24 PM ---------- Previous post was at 06:22 PM ----------

Have you downgraded to 19.5.3 as well?
[Droid Ultra Original Android Development] Cgordon17:
Little better

Yes, im on 19.5.3. I just tried it again and it rebooted to bootloader and got to waiting on adb and at that time when i type in "adb devices'' my phone doesnt pop up until about 80 seconds out of 120 and ive gotton it rooted before the time ran out but then it goes to the part where it says its freezing and then says fatal error failed to download. When exactly do i need to root it again after it reboots. How exactly did you get it to work because mine only reboots once
[Droid Ultra Original Android Development] xDroid4Lifex:
You need to run the /data/local/atvc/root.sh IMMEDIATELY after the phone reboots. Don't waste time checking adb devices just immediately re-root. Keep trying you'll get it eventually, Many users confirmed this works.
[Droid Ultra Original Android Development] Cgordon17:
So should i copy that? i need to put adb shell in front of it right? When the phone reboots and i check for adb devices none pop up till 80 seconds. So what youre saying is dont worry about if its popped up just put that immediatly after it reboots and keep on trying till it works?
[Droid Ultra Original Android Development] xDroid4Lifex:
Exactly,

adb shell /data/local/atvc/root.sh

Then switch back to the wpbegone window and make sure its doing its thing. Whenever it has to reboot switch back to command prompt quick and re-run the above command.
[Droid Ultra Original Android Development] Cgordon17:
Okay, i tried doing that as soon as the phone rebooted to the home screen and kept doing it until it accepted it which was still at 89 seconds. It wont accept it until wpbegone says "must play a little longer" for some reason. Should i try to type that code in a soon as it tries to reboot like when the droid symbol pops up? I dont know why it wont find my phone it just says error: device not found until 89 seconds when it finds it and then its too late. It does get root when it works at 89 but wpbegone wont go any further i will attach a pic of what it says.
[Droid Ultra Original Android Development] bzxzlg:
OK ... This has been stated a number of times ... And I thought I put it in my posts ... Once the device reboots ... It takes close to 2 minutes (if that's the value of the timer that's shown in MotoWpNoMo) before ADB will see the device from your PC ... For me, once it hit "89" or so, I started running adb shell /data/local/atvc/root.sh continually in a separate CMD window until it took ... Once re-rooted with PIE, MotoWpNoMo will continue it's execution ...

Bottom line --> everytime that MotoWpNoMo reboots your device, you'll need to run the PIE exploit (adb shell /data/local/atvc/root.sh).
[Droid Ultra Original Android Development] Cgordon17:
Yeah the device has only rebooted 1 time and that's at the beginning and then I get it back rooted at 89 and then it doesn't keep going it just says "FATAL: Download updated packages" and it waits for another minute or so. I am checking right now to make sure my security and antivirus is off right now even though I'm sure it is
[Droid Ultra Original Android Development] bzxzlg:
Follow the outline in post #26 of this topic ...

http://xdaforums.com/showpost.php?p=53189750&postcount=26

Download all pieces parts ...

Of course, the very first thing to do is off-load your photos and music :)
[Droid Ultra Original Android Development] GnatGoSplat:
Also like someone already mentioned, once you've typed/pasted it the first time (before you run WpNoMo) use the up-arrow key to get to it instead of typing or even pasting it in as that's much faster.
[Droid Ultra Original Android Development] bzxzlg:
You can even use the F3 key! :laugh:
[Droid Ultra Original Android Development] cal4877:
OK I have a droid ultra and reverted back to previous version ..I was able to run jcase root exploit when it finishes I can't install super user for some reason any ideas? If I run wpbegone I get an error saying my phone is not rooted.. Any way that I can push su thru fastboot

---------- Post added at 09:34 PM ---------- Previous post was at 08:47 PM ----------

NVM got it working ..any Roms available.. Someone needs to make a video of this
[Droid Ultra Original Android Development] rds217:
For roms, you need an unlocked bootloader. If you don't have that, but have root, your best bet is to install the xposed framework and gravitybox.
[Droid Ultra Original Android Development] cal4877:
So now I can have my phone unlock the boot loader is that correct? I found a link but I don't see the model of my phone.. I have a ultra
[Droid Ultra Original Android Development] rds217:
Root isn't needed to unlock the bootloader, to do that you would have to purchase the unlock code. Instructions for purchasing the code are here: http://xdaforums.com/showthread.php?t=2679190; however it seems that unlock codes are only available for phones manufactured after January 2014.
[Droid Ultra Original Android Development] kdaz:
There is an eclipse ROM that works without having an unlocked bootloader. Not sure if its posted anywhere on here but I just Google searched eclipse ROM and got it from his site.
[Droid Ultra Original Android Development] Carrzy:
I rooted my device in the past so I do not have write protection. I had to revert due to my own doing.. I reverted back to 19.5.3 successfully but cannot get the "tether"method to work. tried multiple times and the outputs are the same as the expected outputs. when I open supersu it closes. when I run rootchecker it fails as well. any ideas?

Thanks in advance
[Droid Ultra Original Android Development] rmjones2006:
Try superuser instead of supersu
[Droid Ultra Original Android Development] miketoasty:
You're missing the Safestrap part which actually installs SU to your system. The temp root won't allow you to install SU (I tried).

As someone who went from rooted with WP off to stock (Still keeping WP off) back to rooted, here were my steps:

Revert to the 19.5.3 update (Which you are already on)

Use the PIE root method and Install Safestrap

Reboot to recovery and flash this: http://download.chainfire.eu/396/SuperSU/

Reboot to system, open SuperSU and install (Via Normal) the latest SU binary

Done.

No issues what so ever and after the SBF back to 19.5.3, it only took about 5 minutes to finish up the rest.
[Droid Ultra Original Android Development] Carrzy:
Thank you very much! I will be doing this tonight
[Droid Ultra Original Android Development] Carrzy:
Here's what I get. Something is not working as I can't even install safestrap
[Droid Ultra Original Android Development] miketoasty:
You're still rooted, that's what happens after the first time you run the PIE command. You need to also remove the write protection to use Safestrap.
[Droid Ultra Original Android Development] Carrzy:
Write protection is off. I ran the command to check for write protection from the MotoWpNoMo thread before I started PIE and it returns "0"

I've also tried PIE multiple times and I don't have any sign of a successful tethered root
[Droid Ultra Original Android Development] Carrzy:
which recovery do i use? safestrap or stock/ does it matter?
[Droid Ultra Original Android Development] Pacnet_:
Safestrap

Sent from my XT1030 (Droid Mini)
[Droid Ultra Original Android Development] Kodalades:
Does anyone know if this will survive the 4.4.4 update for the new Droid family? I don't want to take the update only to find I lose root because of it and not be able to go back and redo it.
[Droid Ultra Original Android Development] miketoasty:
You need to use the SuperSU survival mode and only Root will survive not WP which majorly cripples roots usefulness. But to answer your question yes it will survive the update.
[Droid Ultra Original Android Development] GnatGoSplat:
So far, all my apps that require root seem to be working fine even with WP on. I never actually altered anything in /system so losing WP off hasn't been a problem.
[Droid Ultra Original Android Development] rlmesq:
It will eventually cripple root apps as updates come along. You won't be able to update SuperSU, Xposed or BusyBox binaries.
[Droid Ultra Original Android Development] GnatGoSplat:
That's a good point. I only updated my spare Droid Mini, but not the one I use. I'm still debating whether I should. I saw one of the changes is improvement in battery life, and I sure could use better battery life.
[Droid Ultra Original Android Development] xDroid4Lifex:
Sure you can update them with w/p on, but you'll have to do it EVERYTIME you reboot the phone. Which to some will probably be annoying but most others will make do with what we have.
[Droid Ultra Original Android Development] GnatGoSplat:
What are the drawbacks of running an older SuperSU and su binary?

I'm just thinking on the lifespan of a smartphone which is probably maybe 1-2yrs, will SuperSU and SU binary get old enough that it causes issues?
[Droid Ultra Original Android Development] empoweredh22:
Perhaps your battery life issue can be solved without updating. Have you looked at what's eating it all?
[Droid Ultra Original Android Development] GnatGoSplat:
Mostly Phone idle (27%) and Android OS (27%).

I'd also really like the improved camera since I take lots of pics.

Although all my root-requiring apps will work fine with WP on, I'm still a bit hesitant to update my daily Droid Mini because I bet the very next day after I do it, someone will say they figured out how to preserve WP off, but it has to be done before updating. That would be my luck.

I think there is some hope though. On my spare Droid Mini that I updated, I tried MotoWpNoMo. It didn't work, but I had installed SuperSU to /system before updating, so it was still there after. Somehow, MotoWpNoMo was able to uninstall SuperSU. It completely uninstalled it from /system, which I verified by doing a factory reset and it didn't come back. So one of the tricks WpNoMo does in the background is able to do some writing.
[Droid Ultra Original Android Development] pyromaniac1:
Can't downgrade back to 19.5.3 after i took the ota to 4.4.4. Anyone else face the same issue?
[Droid Ultra Original Android Development] GnatGoSplat:
If you have an unlocked BL, you probably need to remove some things from the fxz's .xml file like gpt.bin and tz.mbn.

If you have a locked BL, that's normal.
[Droid Ultra Original Android Development] johnny567:
Would there be any way to downgrade with a locked bootloader?
[Droid Ultra Original Android Development] rmjones2006:
Nope
[Droid Ultra Original Android Development] josuearisty:
Of course, just if motorola wants! [emoji1]
[Droid Ultra Original Android Development] Topsnake:
Whether unlocked or not, you cannot downgrade. Bootloader and gpt versions were updated and wont revert or run the old system.
[Droid Ultra Original Android Development] wooddale:
Why do people want to go back data suck on 4.4.4? Im getting a 1080 Thursday with 4 14 assembly and want to try middle man.
[Droid Ultra Original Android Development] Topsnake:
Because 19.6.3 was the last version to have full root access unless you have an unlocked bootloader
[Droid Ultra Original Android Development] wooddale:
You had to revert back to 19.5.3 to get PIE didnt you? So pretty much from what I have read there is curently no root for 4.4.4. whether or not your un locked or not.
[Droid Ultra Original Android Development] Topsnake:
Incorrect. Full root is still available for unlocked bootloaders. Partial root is available for 4.4.4 given you have it on 19.6.3
[Droid Ultra Original Android Development] wooddale:
Im sorry if your unlocked you have full root but can you even get 4.4.4 if your unlocked?
[Droid Ultra Original Android Development] Topsnake:
Being unlocked has no impact on the ability to receive updates.
[Droid Ultra Original Android Development] wooddale:
Maybe not just being unlocked but if your on a custom recovery like twrp no way in hell your gonna get an update. Ive never been unlocked and not on a custom recovery whats the point?
[Droid Ultra Original Android Development] Topsnake:
Even if you're on twrp you'll still receive the OTA. In some cases you may even be able to flash it without reverting to the stock recovery but its not recommended.

What the point of being unlocked you ask? Freedom.
[Droid Ultra Original Android Development] wooddale:
I meant whats the point of being unlocked if you dont get a custom recovery. I have a dev edition Moto X on twrp and you cant get an OTA you can download it and try to flash but it will fail Ive tried it. When it tries to update it looks for stock recovery and cant find it and fails
[Droid Ultra Original Android Development] Topsnake:
We have custom recovery. And that happens here to. Its a simple as flashing the stock recovery, updating, and reflashing twrp then rooting. You should already know this since you have a dev ed.
[Droid Ultra Original Android Development] wooddale:
I do know that just was saying you cant do it when your on a custom recovery