yashsingh1/xdaforums huggingface dataset:
[Droid Ultra Original Android Development] Brenardo:
[/QUOTE]This is the command I am running in adb shell...

C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell

shell@obake-maxx:/ $ echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_help

er

.sh" > /sys/kernel/uevent_helper <

/system/bin/sh: can't create /sys/kernel/uevent_helper: Permission denied

Everything else has worked perfectly and I have the files on the /sdcard

I also have wp off too...

C:\Users\ROB> adb shell getprop ro.boot.write_protect

0

Anybody know how I can get passed this permission denied? [/QUOTE]

You are not alone.

There is currently no resolution to this. Something didn't not take during the SlapMyMoto process between steps 1-3.

This has been covered earlier in the thread.
[Droid Ultra Original Android Development] gatortuba:
Before I start how can I confirm that I am back to stock 4.2.2? What is the fastboot supposed to look like?
[Droid Ultra Original Android Development] grecho:
I already tried the re downloading the update twice,

Tried clearing the cache, and no luck, still had the same error

idk maybe i'll try house of moto again?
[Droid Ultra Original Android Development] Franzie3:
Try that and if not maybe call Verizon. Could be something screwy with phone. If they can't figure it out maybe you get a new phone. Just fxz it to stock before sending it back
[Droid Ultra Original Android Development] cmelby:
I think I know the answer to this one!

This happens to me all the time. For me, it means disconnecting the USB cable going between my phone and my laptop, and then plugging it in again. Somehow, I think, the USB connection gets "forgotten," and this retells the systems that they are connected.
[Droid Ultra Original Android Development] jkhouw1:
I was having the same issue - downloaded the latest Android SDK and ran adb.exe from there and it connected right up... the one I was using from all the prior steps wouldn't work after the kitkat update - may have been old.
[Droid Ultra Original Android Development] 92029:
Bounty Thread

I made my first post (yippie) and created the bounty thread. http://xdaforums.com/showthread.php?p=49498945

This is for creating the Root access on the 4.4 KitKat for those who upgraded unknowingly.
[Droid Ultra Original Android Development] cmelby:
Thanks so much for the complete explanation!

I used HouseOfMoto, did a full wipe (the file name is CFC-obakem_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml since I am on a Droid MINI), went through SlapMyMoto steps 1 through 3, downloaded the 4.4 update, tried to install the update, got the Error! message with the dead Android guy lying down (Update Failed error code 410), phone automatically rebooted, and I'm still on 4.2.2.

I KNOW WHY THIS DIDN'T WORK, AND HERE IS HOW IT DID UPGRADE TO 4.4:

I used HouseOfMoto to complete wipe and reload 12.7.7 (rather than complete wipe and reload 12.15.15 that I tried before). After 12.7.7 was loaded, Verizon OTA upgraded to version version 12.15.15 successfully. After 12.15.15 was on my Droid MINI, I was able to SlapMyMoto. After that, Verizon OTA successfully upgraded to version 4.4.

The reason I was getting the 4.4 upgrade Error! message and the dead Android (i.e. failure to upgrade from 12.15.15 to 4.4) is because I was starting from HouseOfMoto 12.15.15. Starting from HouseOfMoto 12.7.7 and letting Verizon OTA do the upgrade to 12.15.15 and then to 4.4 worked!

Then I completed the "Now that we are on 4.4, we can finish the process with adb shell" commands above, downloaded SuperSU from Google Play and success! The trick was using HouseOfMoto, Complete Wipe not Save Data option, to install 12.7.7, then let OTA to 12.15.15, then SlapMyMoto all except for last set of adb commands to be entered only after update to 4.4, then OTA to 4.4,, then SlapMyMoto last set of commands post 4.4.

So, these are the steps that I used to make it all work (some redundant I'm sure, but extra careful at each step):

1.) Download and set up HouseOfMoto for my phone model (Droid MINI is xt1030). Download and set up Cydia Impactor. Download and set up a version of "Adb and Fastboot" that includes an OPEN.CMD file (makes using adb easier). Download and set up RockMyMoto. Download and set up MotoWpNoMo. Download and set up SlapMyMoto.

2.) Use HouseOfMoto to wipe clean and install 12.7.7

3.) Allow OTA to update to 12.15.15

4.) Use RockMyMoto to root 12.15.15

5.) Use MotoWpNoMo to remove write protection

6.) Use HouseOfMoto to wipe clean and install 12.7.7

7.) Allow OTA to update to 12.15.15

8.) Use SlapMyMoto, except for last set of adb commands to use after update to 4.4.

9.) Allow OTA to update to 4.4

10.) Use SlapMyMoto last set of adb commands after update to 4.4.

Please let me know if I've made an error in specifying these steps or their order.

Hope this helps, and thanks for all the help I received.
[Droid Ultra Original Android Development] SomeoneE1se:
So, I followed (attempted to I guess) and now I have a brick.

OTA wouldn't take so I tried to flash the 4.4 OTA.zip with the stock recovery. Now it wont boot (partition (boot) security version downgraded), recovery is borked (cant sideload anything), and Houseofmoto fails to flash anything, with success.

I'm open to suggestions, otherwise learn from my failure.
[Droid Ultra Original Android Development] cdfjr1975:
Write Protect Help Please

Tried to post in the MotoWpNoMo forum but got an error I haven't posted enough to ask a question there.

I'm trying to run the MotoWpNoMo and I get error messages

Running 4.2.2 12.15.15

RockMyMoto appears to be working since SuperSu is asking to grant permissions and showing them on the Apps tab

I get the write protect status of 1 when I do adb shell....

Ubuntu box error

WTF: Why are you even here?

SuperSU closes during operation

Windows 7 Box error

Fatal disable firewall ...etc

All firewalls are disbaled, Trend and Windows Firewall

Any advice would be greatly appreciated to complete this next step on my path to SlapMyMoto
[Droid Ultra Original Android Development] jkhouw1:
On windows box, if you get a fatal error downloading, it is most likely because you are not running it as administrator. right click on wpbegone and choose run as administrator.
[Droid Ultra Original Android Development] needshelp101:
What is this? I got this this morning after I did slap. Everything took so I have no idea.
[Droid Ultra Original Android Development] ihuntinde:
I think the only way to get rid of this is a factory reset. A quick google of that error has some saying it may be malware of some sort because of the "Im Feeling Lucky" button.

The other thing that points to malware is that it looks like it's been around for a few years affecting a multitude of devices and devices that are rooted and non-rooted. Running roms and completely stock.
[Droid Ultra Original Android Development] needshelp101:
If I do a factory reset on 4.4, will I lose root? I'm liking a rooted kit Kat :)
[Droid Ultra Original Android Development] ihuntinde:
That I can't tell you since my knowledge is pretty limited with exploits, especially this one since I went to 4.4 as part of the soak test. I knew I was going to lose root, but was more interested in testing the update.

It is also possible another fix is out there for the error you are seeing. Maybe an antivirus app or anti-malware app exists that can clean it up? IF that is what the error is caused by. It can't hurt to download one of those apps from the Play Store and see if it detects or fixes anything before doing a reset.
[Droid Ultra Original Android Development] needshelp101:
I tried a few, still getting the same error. I'm afraid to try the factory reset. I'm pretty sure root will stay, but I'm not sure.
[Droid Ultra Original Android Development] cdfjr1975:
Late night so forgot to add that I ran it as administrator. Thanks for the prompt reply I appreciate the assistance but think I'm doing something else incorrectly.

Would using house of moto put me back to stock and I could start over at RockMyMoto since it appears write protection is to maintain root through a factory reset?
[Droid Ultra Original Android Development] needshelp101:
A factory reset does not lose root. I just tried it. You just have to re download super user from the play store :)
[Droid Ultra Original Android Development] cdfjr1975:
Thanks for the advice. Tried that and still no go. Would there be a harm in using clockwork superuser app instead if chainfire app?

Thanks in advance for everyone's help!
[Droid Ultra Original Android Development] needshelp101:
I had to run the wpnomo like 6 times to take. If that's what you mean.
[Droid Ultra Original Android Development] cmelby:
Deleted

---------- Post added at 02:24 PM ---------- Previous post was at 02:12 PM ----------

I remember this message, but I think I ignored it with no bad effects so far.

Maybe not a real OS message? Maybe just trying to trick you into clicking I feel lucky? Maybe something part of " *stuff* " wpbegone installs?
[Droid Ultra Original Android Development] hdmunger:
Now that the 4.4 FXZ is available, will that change/simplify this process, or is it of no value except to recover from failed attempts (bricks)?
[Droid Ultra Original Android Development] NWKENT:
$50.00 + Will pay

Here >> https://docs.google.com/file/d/0B67RS0BDBp_iTUJNSGNYRWtGVEU/edit?usp=docslist_api

sent by my MZ617-32 XYBoard 10.1_SafeStrap v3.12_Jelly Bean 4.1.2

Please donate to: jcase & Hashcode (if you can)
[Droid Ultra Original Android Development] Teksu:
cannot be completed 3 times on one device... part of the process is accepting the 4.4 ota, once this is done the device cannot be downgraded to 4.2.2
[Droid Ultra Original Android Development] NWKENT:
Awesome..your paying attention..thank you..

Beings this is a fact..and there are some doubt that the Dev, may not release the "suspected" Root method, then we should work to perfect the "SlapMyMoto" process, simplify it, with accurate, understandable instructions for download..all the sporadic, mumbo jumbo here that NO ONE can follow from the OP til now..is absolutely so confusing that even the experienced ones fail the process, seems as thow the process is do'able, if we all work together, and work up a directions sheet, many devices will avoid brick condition..

Maybe the Dev is holding out for a worthwhile bounty, which is reasonable, I support his efforts, but if he keeps to himself this, then we should not wait another day, and make this "SlapMyMoto" work for everyone..the Dev has done the (hard work) for us..we should move along and glorify his work..by every device using his method.

PLEASE someone correct me if I'm wrong.¿

Whom here has a device on 12.15.15 and willing to try this method and keeps notes of exact process, since we have an FXZ now for 4.4..if we brick, we have the FXZ.?

+1

sent by my MZ617-32 XYBoard 10.1_SafeStrap v3.12_Jelly Bean 4.1.2

Please donate to: jcase & Hashcode (if you can)
[Droid Ultra Original Android Development] Teksu:
Honestly, the instructions in the OP seem pretty straight forward. If i hadn't already updated to unrooted 4.4 i would do this, but alas...
[Droid Ultra Original Android Development] NWKENT:
Well..tell that to those one's with bricks.. :)

My point with all this..straight forward..in what dialects.? Many have failed because they didn't/couldn't follow instruction exactly..

Maraming salamat ingat

sent by my MZ617-32 XYBoard 10.1_SafeStrap v3.12_Jelly Bean 4.1.2

Please donate to: jcase & Hashcode (if you can)

---------- Post added at 09:23 PM ---------- Previous post was at 08:46 PM ----------

For example, in the OP, the two lines above Step 1)

First you must use MotoWPNoMo, if you haven't then you will need to. Use RockMyMoto to gain root, then use MotoWPNoMo, and then restore to the 4.2.2 Camera update.

It states.. "First you must use "MotoWPNoMo"..then later is says to Root with "RockMyMoto"..then it states, "then use "MotoWPNoMo, Does one run the "MotoWPNoMo" twice.? Or only once.?

And the same line says: and then restore to the 4.2.2 Camera update..does one start with 12.7.7 because the camera update is 12.15.15..to me, the term "restore" means to return something to what is was..so the instructions mean to me, that the device should start with 12.7.7 which is (out of the box)..the OP is unclear..and there's more..

I'm absolutely not slandering the Dev, or the OP..because I certainly understand, he is VERY busy, and doesn't have time to hold our hands..

My point is, if we would work up a document, that explains in more exacting detail, even a newbie as myself could accomplish this..this thread would be 1/4 the posts it is, if one post where here, with more detailed (one document link)..simple really

sent by my MZ617-32 XYBoard 10.1_SafeStrap v3.12_Jelly Bean 4.1.2

Please donate to: jcase & Hashcode (if you can)
[Droid Ultra Original Android Development] mdav07:
I don't understand how this can be confusing.

1. Root with RockMyMoto

2. MotoWPNoMo

3. Restore to 15.15 (camera update) via RSD or House of Moto

4. Start SlapMyMoto steps 1-3

5. Take OTA 4.4

6. Finish SlapMyMoto step 4

One note is that I used telenet an PuTTYtel the same way as the RockMyMoto windows version I just used the SlapMyMoto commands instead of the RockMyMoto
[Droid Ultra Original Android Development] jfriend33:
http://xdaforums.com/showthread.php?t=2603051

Anyone try this on a droid maxx?
[Droid Ultra Original Android Development] SomeoneE1se:
I just tried this on a virgin Droid maxx and the OTA failed. Everything else went smoothly. Followed the instructions to a T?

The last time I tried to house of moto the 4.4 I downloaded to my computer things went sideways. Thoughts?
[Droid Ultra Original Android Development] cdfjr1975:
Still having issues with motowpnomo.

I get rockmymoto and have root access. Type su in terminal to verify I get root@obake.. # if I check at this point I have write protect 0. Not sure what motowpnomo does but seems as if I need it to keep write protect 0 so I still need to run the exploit.

Ubuntu 12.04 64 bit, op states linux 32 so is this a problem. It seems to work well up until suoersu closes. Before it starts clobbering 1 then I get the error message Wtf: why are you hear. Does this mean I'm set already to house of moto since my write protect is still 0. But if I house of moto I get write protect 1 and can't run slapmymoto.

Windows 7 64 bit I get the firewall warning but supersu doesn't crash. I've turned off windows firewall and my trend micro internet security. I connect modem directly to laptop to eliminate possible errors but it still fails. I'm running as administrator.

I have repeated process many times with no success on both systems.

Any other thoughts would be greatly appreciated.
[Droid Ultra Original Android Development] nubia11:
I will second this as exactly put here with!
[Droid Ultra Original Android Development] fuzzychinsagrero:
Could someone please tell me how they did their last step? I'm fine up until echo "/data.... Where do I hit, is it all one line or what?

Edit: for example how many total command lines are there? 4 or 5?
[Droid Ultra Original Android Development] Teksu:
"First you must use MotoWPNoMo, if you haven't then you will need to." - This is a stand alone statement, denoted by the presence of a period, traditionally used to end a sentence.

The sentence that follows is a rough description of how to accomplish this, as the exact instructions for installing motowpnomo are located in the OP of the thread linked to ( MotoWPNoMo)

The "restore" term is used to indicate that you will need to "return to stock 12.15.15" to eliminate root files, else the ota 4.4 update will fail. Again, the instructions for MotoWPNomo indicate that you must be on the 4.2.2 12.15.15 "camera update" when starting.

After you restore, and BEFORE you accept the OTA, run SlapMyMoto, this will prep your device to take the OTA and be able to root afterward. Part of this process should make your phone reboot, this seems to be where most people have issues. I would not proceed with the ota update if your device does not reboot.

When the device comes back from the reboot, run slapmymoto again, triggering another reboot.

Once this process completes, you may then take the OTA. Upon completion of the update, you should then run the install script, your device will reboot, and you will have root.

I realize that this information is a little spread out, its tough to read 3 different posts at the beginning of 3 different threads. But there are links to them all, saying "go do the stuff here, then the stuff here, return to stock, then do the stuff in this thread. so im having a hard time seeing why your having problems.

Step one: Read

Step two: Read MORE

Step Three: take a break

Step Four: Read EVEN MORE

Step Five: Follow instructions, If you are not yet comfortable with the instructions, return to step one.
[Droid Ultra Original Android Development] cmelby:
1. Root with RockMyMoto <==== This worked for me after I HouseOfMoto'ed to 12.15.15

2. MotoWPNoMo <==== This worked for me after RockMyMoto

3. Restore to 15.15 (camera update) via RSD or House of Moto <==== This worked for me after I HouseOfMoto'ed back to to 12.15.15

4. Start SlapMyMoto steps 1-3 <==== This worked for me.

5. Take OTA 4.4 <==== This DID NOT work for me. Using HouseOfMoto to flash to 12.15.15 somehow left issues on my device, 4.4 OTA would not install and gave a Update Failed error 410. I had to HouseOfMoto all the way back to 12.7.7, let the Verizon OTA update to 12.15.15, and then let Verizon OTA update to 4.4 to successfully get 4.4 on my device.

6. Finish SlapMyMoto step 4 <==== This worked for me after I successfully updated via OTA to 4.4

Problems I encountered included making sure that antivirus and firewalls are off during any steps involved, setting up HouseOfMoto correctly (must put the support files and correct FXZ files for your phone model in exactly the right place), remembering to re-enable Developer Options menu and associated USB Debugging options after each HouseOfMoto, realizing that messages indicating loss of contact between PC and phone via USB require unplugging and replugging in USB cable, remembering to run (HouseOfMoto?) as Administrator, finding the IP address needed by Impactor: About Phone===>Status===>IP Address, in ADB, doing an ADB DEVICES and realizing if the phone is not "seen," then a USB cable unplug/replug is necessary.
[Droid Ultra Original Android Development] mdav07:
The last step in slapmymoto is all single commands. Cut an paste them it worked for me that way. The echo is a single command too.
[Droid Ultra Original Android Development] fuzzychinsagrero:
Okay there was definitely an error somewhere else because I already tried copying and pasting. Thanks.
[Droid Ultra Original Android Development] mdav07:
So are you rooted on 4.4 now?
[Droid Ultra Original Android Development] Topsnake:
Working on this right now with Kent. Coming down the pipeline soon guys.
[Droid Ultra Original Android Development] SomeoneE1se:
I've updated to 4.4 and finished step 4 but got this error

/system/bin/sh: can't create /sys/kernel/uevent_helper: Permission denied

does this mean no root for me?
[Droid Ultra Original Android Development] tehcodeman:
Update download is here if you know how to adb sideload or install from internal storage:

http://xdaforums.com/showpost.php?p=48656786&postcount=111
[Droid Ultra Original Android Development] Metfanant:
to sideload the zip, i just...

1. place the zip in the directory where adb is

2. enter adb sideload whatevertheupdateiscalled.zip

do i have that correct?
[Droid Ultra Original Android Development] tehcodeman:
Yep. Be sure to extract the actual obake .zip update file from the download and place in your adb directory.

Also, be sure that USB debugging is enabled and that you have selected "apply updated from ADB" in recovery.
[Droid Ultra Original Android Development] Dragon31337:
Well, first post is confusing... Especially this string:

Right now I have 4.2.2 with camera update (12.15.15). no root, pure stock. Do I really need to rollback to the stock 4.2.2 in order to get root and make it survive the 4.4 update?

If I got it right - no, as soon as RockMyMoto works on 4.2.2 with camera update (12.15.15). So I have to do is:

1) Follow instructions on RockMyMoto, get root

2) Follow instructions on MotoWPNoMo to get permanent write protection off

3) Follow instructions at the first message of this thread to get 4.4 installed and preserve root

right? No any rollbacks required, etc.

Thank you in advance.
[Droid Ultra Original Android Development] mistermojorizin:
Your 1 and 2 are correct, then before starting with slap my moto, he said to RESTORE TO STOCK (CAMERA) 4.2.2 - this means unroot. then you can do your 3.
[Droid Ultra Original Android Development] Metfanant:
just want to make sure im on the right page here...

Step 1: RockMyMoto

Step 2: MotoWpNoMo

Step 3: SlapMyMoto

Now...for SlapMyMoto

Step 1: no changes

Step 2: no changes

Step 3: no changes

after the phone reboots after step 3, instead of taking the OTA i have "Blur_Version.12.15.15.obake-maxx_verizon.Verizon.en.US" in the platform-tools directory...my next steps will be

1. turn off phone

2. boot into stock recovery

3. select "apply update from adb"

4. adb sideload Blur_Version.12.15.15.obake-maxx_verizon.Verizon.en.US

once that is done...

Step 4: no changes
[Droid Ultra Original Android Development] rlmesq:
And that restore/unroot can be done with House of Moto?
[Droid Ultra Original Android Development] tehcodeman:
Correct. If you skip this step then you will be stuck in a bootloop when attempting to install the OTA! The reason you restore to stock 4.2.2 (via HouseOfMoto for example) is to re-install the stock recovery (the RockMyMoto recovery is modified).
[Droid Ultra Original Android Development] Dragon31337:
on the first page it says:

So I believe that means that I have to be on 4.2.2 (12.15.15) already, and that is where I am already...
[Droid Ultra Original Android Development] tehcodeman:
See my note in red above. You can do that with HouseofMoto. Don't skip this step or you'll be in a bootloop when attempting to install 4.4.
[Droid Ultra Original Android Development] Metfanant:
yes, caught that in your last reply....
[Droid Ultra Original Android Development] Topsnake:
Ok so quick question. Is the step four one large string of code? Or is each line a new command?
[Droid Ultra Original Android Development] tehcodeman:
Each is a different command.
[Droid Ultra Original Android Development] Dragon31337:
4.2.2 (12.15.15) is not a stock, that the latest version before 4.4. Please either clarify or do not confuse.

And what is wrong with current 4.2.2 which is rooted with RockMyMoto and tuned with MotoWpNoMo?
[Droid Ultra Original Android Development] Topsnake:
You need to read more. This has already been explained. I hate when people come into these threads trying to take shortcuts and get some sort of justification for every step.
[Droid Ultra Original Android Development] Metfanant:
other than your note, im good to go yes? my steps for sideloading the update are good? also, when i run House of Moto...do i need to do a wipe? or can i keep data?
[Droid Ultra Original Android Development] Topsnake:
I prefer to just go FXZ which will wipe for you. You need to be back on stock 12.15.15. You can load the update in recovery if thats easier for you. Then dont forgot the code in step 4
[Droid Ultra Original Android Development] Metfanant:
- full FXZ not a keep data?

- not necessarily easier to load in recovery...i just cant pull the OTA yet, so thats the only way to get it...
[Droid Ultra Original Android Development] Topsnake:
Full fxz wipes it. You can remember the file update.zip and place in storage. Then select update from storage in recover
[Droid Ultra Original Android Development] Metfanant:
i realize a full fxz wipes everything...i was simply asking if i had to do that..or if a keep data fxz was ok??...

as for the update...the file that i was pointed to in the "who is gonna leak the soak test thread" was "Blur_Version.12.15.15.obake-maxx_verizon.Verizon.en.US.zip" booting into recovery and updating from adb and sideloading that file should work right?