27 replies to this topic

[jpbardua]

Hi,

 

I am new to the whole rooting/unlocking bootloader functions.  So since my Razr HD (at 9.18.79) is out of warranty, I decided to see if I could root it, then protect root, and then take the update to 9.18.94.  So below are the steps I took.

 

1.) downloaded and ran motochopper v1.3 zip file

2.) ran the run.bat file

3.) installed root checker

4.) verified I had root access

5.) installed voodoo rootkeeper

6.) protected root

7.) downloaded 9.18.94 update and it fails on install  (I tried with and without doing the temp-unroot feature of rootkeeper)

 

Any help would be appreciated.

 

Thanks,

Jim

[Draxion]

After protecting root through Voodoo... Select 'temporarily unroot' in Voodoo then run the OTA. After the device updates and reboots, return to Voodoo to verify root is back.

Sent from my DROID RAZR HD using Tapatalk

[livinginkaos]

Just be advised, if you update to 9.18.94 and lose root you will not be able to get it back unless your bootloader is unlocked.

Sent From My DEV X

[Draxion]

I was successful with my RAZR Maxx HD. I haven't heard that issue before. How is gaining root dependent on the bootloader? I do know that since 9.18.79 we have lost the ability to unlock, but I've successfully rooted since then. Can you provide a link? Thanks in advance.

Sent from my DROID RAZR HD using Tapatalk

[livinginkaos]

If you are unlocked you can root regardless, but on the new update there is no root method for unlocked devices.

Sent From My DEV X

[johnthehillbilly]

Simply put.... if your boot loader was unlocked (prior to the previous update, which killed the ability to unlock).... then for root, you can flash a custom recovery and root.... if you are locked, there is no known root exploit for the current version..... Ninja'd by Kaos.... again... :::

[bshk4126]

...oddly enough.. im having the same problem.  :/

RAZR HD MAXX

-did a factory reset (all data, folders, and subs were deleted)

-rooted 9.18.79

-downloaded voodoo

-protected root

-temp un-root

-downloaded update 9.18.94

-install update (failed) ...  "update unsuccessful". 

 

...not really sure what im doing wrong? nothing was froze..nothing was modified.   any advised would be greatly appreciated. 

 

 

 

EDITED: forgot to mention.. not unlocked.  and not a complete noob. <- hope that helps.  

[SamuriHL]

Nothing was modified... Clearly your phone disagrees with you. It's failing an assertion somewhere. You'll need to install the ota manually in recovery and provide the entire error message. And I don't just mean error 7. The whole message.

Sent from my Xoom using Tapatalk 4

[jvargas]

I am having the same issue, I was on 9.18.79 and rooted with the tool found in this forum.  I've attempted to install the new OTA (9.18.94) several times and it always fails, even did a factory data reset to no avail.  Since the bootloader is locked, I've always had stock rom, never froze or uninstalled bloatware, I rooted for the purpose of running apps like TBU, Greenify, and RAM Manager.  At this point I am fine with losing root, I am fine just knowing that I will get Kit Kat.  Considering I am a newbie, what would be the easiest way to take the update?  

[johnthehillbilly]

If you truly are ok with losing root and want to take the update .... it won't hurt to FXZ back to 100% stock.... then simply take the OTA......

[jvargas]

Thanks.  Can you recommend a link with instructions?

[cmh714]

You will want to get Samuri's House of Moto, and read, read, read.

Please Login or Register to see this Hidden Content

 

You will also need the FXZ files which can be gotten here: sbf.droid-developers.org

 

HOWEVER, the sbf site is currently down due to a disk drive failure. So unless you have the files already, you will have to wait.

 

In the meantime, get Sams stuff downloaded and configured properly. This gives you the time to read.

 

Oh and did I mention to read...... just a wise arse.

[ibolski]

I am having the same issue, I was on 9.18.79 and rooted with the tool found in this forum.  I've attempted to install the new OTA (9.18.94) several times and it always fails, even did a factory data reset to no avail.  Since the bootloader is locked, I've always had stock rom, never froze or uninstalled bloatware, I rooted for the purpose of running apps like TBU, Greenify, and RAM Manager.  At this point I am fine with losing root, I am fine just knowing that I will get Kit Kat.  Considering I am a newbie, what would be the easiest way to take the update?  

 

Just be prepared that Titanium Backup will no longer work for you once you lose root.

[jvargas]

Worst case scenario, I have to bite the bullet and start from scratch.  Obviously I'd prefer to keep root but if i had to choose between KitKat and being rooted, I'll take KitKat.  I already feel I have an inferior device with the locked bootloader, imagine how I'll feel when everyone else is upgraded to KitKat.  

 

4.4 will at least give me some incentive to keep the phone a little while longer. I really don't understand why the update fails...really sucks.  If you guys have the patience to help a brother out, can someone help me understand what I can do to resolve this?  What would your course of action be?

[43616]

I've got a rooted razr maxx hd and my last update was 9.20.1 back during the summer.  Now it wants to install 9.30.1 but the install fails.  I tried to use ota snatcher so I could try a manual install and see what the error is but after the phone downloads the update and I use ota snatcher it always picks up the 9.20.1 update instead.  Any ideas on what's going on?

[livinginkaos]

The name of the update always matches the version that you are currently on. It is part of the verification process. Sent From My DEV X

[Draxion]

Maybe a noob comment, but could this issue have something to do with the root that's installed? I use SuperSU Pro and Voodoo Rootkeeper and have both protecting root. I used Voodoo for temp unroot. The update installed fine for me. Hope this is helpful.

Sent from my DROID RAZR HD using Tapatalk

[jvargas]

Before FXZ'ing back to 100% and losing all my data.  I want to make every attempt to fix this OTA problem.  I used OTA snatcher and then ran OTA verifier and this is the message I have.  Any ideas?

 

 

==================
   Detailed Analysis
==================

- you have no frozen system apps (good!)

- there were 20 failed expressions; see below for the details about these tests that will cause your OTA install to fail

- there were no bypassed expressions (good!)
-------------------------------
statistics:

frozen system apps: 0
success count:      438
fail count:         20
ignore count:       1298
partition count:    0
protected count:    19
bypassed count:     0

Device information:

Device:        vanquish
Maker:         motorola
Model:         DROID RAZR HD
Carrier:        Verizon Wireless
Board:          MSM8960
Name:          XT926_verizon
Bootloader: 0x109B
Android OS: 4.1.2

-------------------------------
updater-script analysis details:

FAILED: line #824:

assert(apply_patch_check("EMMC:boot:10485760:a1c699a6a7d07d1859b704359bd79f0e5eb65ab8:10485760:9b13358606bc93350c0ec2feef5c9cfa9a30dee9"));

apply_patch_check: file (boot) does not exist or cannot be accessed

----------------------
FAILED: line #828:

assert(apply_patch_check("/modem/image/dsps.b01", "bf66bb5baa2113e35c766e77015f902b2fce9e1c", "3714d02951c6a28c4e56dba16a694904f4f073d7"));

[the SHA1 checksum for file /modem/image/dsps.b01 (da39a3ee5e6b4b0d3255bfef95601890afd80709) does not match any SHA1 in the above expression]

----------------------
FAILED: line #829:

assert(apply_patch_check("/modem/image/dsps.b02", "73938583dd58252dd47fefadf6e21e459d9a6053", "4bf50ff5a33eb36fbf150ac124da0613b616ad8d"));

[the SHA1 checksum for file /modem/image/dsps.b02 (da39a3ee5e6b4b0d3255bfef95601890afd80709) does not match any SHA1 in the above expression]

----------------------
FAILED: line #830:

assert(apply_patch_check("/modem/image/dsps.b03", "0cfe54fc9a4fa49eec1ebd1de492b9f946a23838", "6fabb26ac9e913ce95d41aa75027dc1dc3a37767"));

[the SHA1 checksum for file /modem/image/dsps.b03 (da39a3ee5e6b4b0d3255bfef95601890afd80709) does not match any SHA1 in the above expression]

----------------------
FAILED: line #831:

assert(apply_patch_check("/modem/image/dsps.b04", "df5566ee986b9b6ad67a82f5f270ccca93b575a6", "bbd6779e90e82ab003f36ea9fe6c763cb1864f57"));

[the SHA1 checksum for file /modem/image/dsps.b04 (da39a3ee5e6b4b0d3255bfef95601890afd80709) does not match any SHA1 in the above expression]

----------------------
FAILED: line #832:

assert(apply_patch_check("/modem/image/dsps.b05", "f460f9c6185f536dd27e4f34ca064a462875615a", "89eb6597fafe4beecf78ca637426b1dc2a44a133"));

[the SHA1 checksum for file /modem/image/dsps.b05 (da39a3ee5e6b4b0d3255bfef95601890afd80709) does not match any SHA1 in the above expression]

----------------------
FAILED: line #833:

assert(apply_patch_check("/modem/image/dsps.mdt", "f7a1c10add83dbe2799d0880c2a899b31c85873f", "75dc508c4a005e360f83640872df0c2b10647779"));

[the SHA1 checksum for file /modem/image/dsps.mdt (da39a3ee5e6b4b0d3255bfef95601890afd80709) does not match any SHA1 in the above expression]

----------------------
FAILED: line #834:

assert(apply_patch_check("/modem/image/modem.b00", "270e3671205262eb4b008b4287d513e4358afde4", "c73f86f085611a09dfe817a8816625d27aa8c32f"));

[the SHA1 checksum for file /modem/image/modem.b00 (da39a3ee5e6b4b0d3255bfef95601890afd80709) does not match any SHA1 in the above expression]

----------------------
FAILED: line #835:

assert(apply_patch_check("/modem/image/modem.b01", "14561aaea1ae8e5ceb7358aa48791d4978a46617", "b6e84b09477642b69b6b38b840bf5d29f3ddb2cd"));

[the SHA1 checksum for file /modem/image/modem.b01 (da39a3ee5e6b4b0d3255bfef95601890afd80709) does not match any SHA1 in the above expression]

----------------------
FAILED: line #836:

assert(apply_patch_check("/modem/image/modem.b02", "39374c28e08bf422bc90b4f79230ad158c940331", "10c24af23277f8c40957bb7acc724ba56cbf0936"));

[the SHA1 checksum for file /modem/image/modem.b02 (da39a3ee5e6b4b0d3255bfef95601890afd80709) does not match any SHA1 in the above expression]

----------------------
FAILED: line #837:

assert(apply_patch_check("/modem/image/modem.b03", "6499588dc2fde2b25926d4df0a1a2f44cacad6bc", "1d72e67446a0ed2e2b100d8054db37301973102f"));

[the SHA1 checksum for file /modem/image/modem.b03 (da39a3ee5e6b4b0d3255bfef95601890afd80709) does not match any SHA1 in the above expression]

----------------------
FAILED: line #838:

assert(apply_patch_check("/modem/image/modem.b04", "4eb9326de549383d540d6c0123551ca9d97225ab", "172db7540a6f83aa1c75c220a0a47947a6441cee"));

[the SHA1 checksum for file /modem/image/modem.b04 (da39a3ee5e6b4b0d3255bfef95601890afd80709) does not match any SHA1 in the above expression]

----------------------
FAILED: line #839:

assert(apply_patch_check("/modem/image/modem.b06", "6e69f8491880c60003bbd7af885082c0c6ac1a7a", "e41177a041adbf4712fa347e6a0c9bd24a3bb326"));

[the SHA1 checksum for file /modem/image/modem.b06 (da39a3ee5e6b4b0d3255bfef95601890afd80709) does not match any SHA1 in the above expression]

----------------------
FAILED: line #840:

assert(apply_patch_check("/modem/image/modem.b07", "2e46f892fd7505e6cc5e57e9e9730974e5b14f0e", "052c90bbd395f2f08f87c72b0e1fa157d4888887"));

[the SHA1 checksum for file /modem/image/modem.b07 (da39a3ee5e6b4b0d3255bfef95601890afd80709) does not match any SHA1 in the above expression]

----------------------
FAILED: line #841:

assert(apply_patch_check("/modem/image/modem.mdt", "6a343cdaa74c94fdcb39eae8663ee2370d0bf47d", "079cea13a4c450fc785dbe3623149e8e3b63b6d3"));

[the SHA1 checksum for file /modem/image/modem.mdt (da39a3ee5e6b4b0d3255bfef95601890afd80709) does not match any SHA1 in the above expression]

----------------------
FAILED: line #842:

assert(apply_patch_check("/modem/image/wcnss.b00", "34659608442518a7805865e5a60721f6982f666c", "e897f83e262ecd0606c10ea61c1e751d1e2e1d49"));

[the SHA1 checksum for file /modem/image/wcnss.b00 (da39a3ee5e6b4b0d3255bfef95601890afd80709) does not match any SHA1 in the above expression]

----------------------
FAILED: line #843:

assert(apply_patch_check("/modem/image/wcnss.b01", "9e2a4f467f1d43653b103d86e217af2137256a27", "590b0b0766a6dce4cdb6da036517a010874e1452"));

[the SHA1 checksum for file /modem/image/wcnss.b01 (da39a3ee5e6b4b0d3255bfef95601890afd80709) does not match any SHA1 in the above expression]

----------------------
FAILED: line #844:

assert(apply_patch_check("/modem/image/wcnss.b02", "eb33e3c1d0866d0e7e5398666ae7d113ce43958f", "ec801e6bb0109067abe42dbd6a301c3280f95cef"));

[the SHA1 checksum for file /modem/image/wcnss.b02 (da39a3ee5e6b4b0d3255bfef95601890afd80709) does not match any SHA1 in the above expression]

----------------------
FAILED: line #845:

assert(apply_patch_check("/modem/image/wcnss.b04", "b5c003b07b62472b655e041b196c92a6747d68b8", "09c8983372671fddc7423d7e1867daa61f248a83"));

[the SHA1 checksum for file /modem/image/wcnss.b04 (da39a3ee5e6b4b0d3255bfef95601890afd80709) does not match any SHA1 in the above expression]

----------------------
FAILED: line #846:

assert(apply_patch_check("/modem/image/wcnss.mdt", "5bec4d9ac4034e3b2c3d4bac3f55d40d04eb3541", "b388a0f4bb9f83a32036cf330a83595b520968e3"));

[the SHA1 checksum for file /modem/image/wcnss.mdt (da39a3ee5e6b4b0d3255bfef95601890afd80709) does not match any SHA1 in the above expression]

[cmh714]

Basically it means that the OTA doesnt believe that your phone is ready to update since your not at the right version of the files its expecting.

[jvargas]

Basically it means that the OTA doesnt believe that your phone is ready to update since your not at the right version of the files its expecting.

So FXZ back to stock would be the easiest solution?