8 replies to this topic

[Exxplosive18]

I upgraded to JB fine, got root access...and after running this app called "mctweaker" my phone won't boot past the animation....I tried reinstalling through motorola recovery, but after wiping data I get "verifying current system...assert failed:apply_patch_check ("/system/app/backupassistanceclient.apk". installation aborted.....Is there anything that can fix this??

[JungleKing76]

I don't know anything about the app you mentioned and what changes it makes to the system and I am no dev but based on the last time we updated from GB to ICS and couldn't go back, I can only add what worked then.

If you are absolutely sure you are bricked and cannot boot up, you can try this but understand, you take responsibility if it does not work and you may have to wait for a dev to create something or for fastboot files to show up.

Repeat, this worked when I bricked on ICS before there was a fastboot file and we could not roll back to GB.

If you use the razr utility to flash the 211 (ICS) fastboot files, you will likely run into a few errors but most of it should flash. Your phone will essentially be a mix of ICS and JB and will not boot up. Go into recovery and flash the update zip for JB. As long as the file that is causing the failure now (/system/app/backupassistanceclient.apk), is restored, the update should (maybe) go through.

[Saik0Shinigami]

You can also try Fastbooting back to ICS using DroidRazrUtility 1.82 and then reapply the update. Although you cannot flash back to a running ICS, you can confuse the updater enough with the files being present to start the entire process over again.

A lot of people in the original thread ran through it this way to get to something working. The only issue with this is that you will not have root and there's no known root method right now.

[Exxplosive18]

I tried using Matt's RazrUtility, but after it finished uploading on to the device...it failed at the Motorola boot screen...I appreciate it the replies, thanks anyways

[Saik0Shinigami]

Well that's the point... It's not supposed to actually work. You're Fastbooting back to .211 so you can try to run the update again. Once you install the update there's no going back to ICS, BUT it appears you can revert back enough so that you can re-run the update itself.

What I would do in your position.

Fastboot back to .211
clear cache
load up the JB update through moto restore
Pray someone finds a root method soon.

Edit: This should get you a working phone WITHOUT ROOT. There is no known root method for this new build as of my knowledge right now.

[JungleKing76]

You can also try Fastbooting back to ICS using DroidRazrUtility 1.82 and then reapply the update. Although you cannot flash back to a running ICS, you can confuse the updater enough with the files being present to start the entire process over again.

A lot of people in the original thread ran through it this way to get to something working. The only issue with this is that you will not have root and there's no known root method right now.

Uuhhh....this is exactly what I said to do. You started out with, "can also try" but then just repeated my advice. Lol

Sent from my DROID RAZR using Xparent Purple Tapatalk 2

[jagman]

I was stuck in the same situation last night. I think I had a bad initial download of the JB leak as the email client wouldn't work and the phone app was stuck on speakerphone at full volume despite any setting change. anyways, SS 3.07 didn't work right with it and I happened to get stuck in a perpetual boot. couldn't get into SS.just a blank screen after the Motorola symbol. I couldn't power down no matter what. thankfully I had downloaded the JB leak again from a different mirror and moved it to the extcard prior to getting stuck in the bootloop. so, I got into ap fast boot and used Matt's 1.82 utility to flash 211.that caused enough confusion that I could then get into Motorola recovery, wipe cache and flash the second downloaded JB leak file. it worked . unfortunately I lost root but at least I don't have a bricked phone. I swear I followed Matt's instructions to a T but I still had problems. I just think I had a bad DL... just the risk of rooting. that was scary since I wasn't "safe" but all is well now. long story short, their advice in this thread works!

[canezila]

Exact same thing for me! Bad DL. Lost root in the end also. You are not alone

[dunderhead]

I was able to successfully upgrade to JB, but I did lose my root. I don't recommend upgrading to this yet until they find a way to root the device in JB itself unless you don't care...