615 replies to this topic

[SamuriHL]

Neither.

 

Please Login or Register to see this Hidden Content

 

Use the KEEP DATA option if you're flashing KK, or UNIVERSAL if you're flashing JB.

[muppetsuppet]

Alrighty, I ran through the directions posted here

Please Login or Register to see this Hidden Content

I didn't receive any errors from the RSD program itself, though my phone is hanging in AP fastboot mode and says "Fastboot reason: Sticky bit factory_fastboot". 

 

I'm on an XT907

The filename I flashed was VRZ_XT907_9.8.1Q-94-1_CFC.xml

I ran the UNIVERSAL script

 

Here are the contents of the SWDL.txt file: 

 

07/01/14 21:34:10  --------------------------------------------------------------------------------

07/01/14 21:34:10  New Log Started For Software Download.

07/01/14 21:34:10  The FlashLog key is turned off.

07/01/14 21:34:13  00003ec0 Phone.cpp 531 0 ERROR Generic failure when sending command.

07/01/14 21:34:13  00003ec0 Phone.cpp 1778 0 ERROR GetTechnology failed: ERROR.

07/01/14 21:34:13  00003ec0 Phone.cpp 531 0 ERROR Generic failure when sending command.

07/01/14 21:34:13  00003ec0 Phone.cpp 1778 0 ERROR GetTechnology failed: ERROR.

07/01/14 21:34:13  00003ec0 Phone.cpp 531 0 ERROR Generic failure when sending command.

07/01/14 21:34:13  00003ec0 Phone.cpp 1778 0 ERROR GetTechnology failed: ERROR.

07/01/14 21:34:13  00003ec0 Phone.cpp 531 0 ERROR Generic failure when sending command.

07/01/14 21:34:13  00003ec0 Phone.cpp 1847 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.

07/01/14 21:34:13  00003ec0 Phone.cpp 531 0 ERROR Generic failure when sending command.

07/01/14 21:34:13  00003ec0 Phone.cpp 2005 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.

07/01/14 21:34:13  00003ec0 Phone.cpp 531 0 ERROR Generic failure when sending command.

07/01/14 21:34:13  00003ec0 Phone.cpp 1975 0 ERROR GetBootVerFlashMode failed: SendTC failed: ERROR.

07/01/14 21:34:13  00003ec0 Phone.cpp 531 0 ERROR Generic failure when sending command.

07/01/14 21:34:13  00003ec0 Phone.cpp 1894 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.

07/01/14 21:34:13  Multi upgrade started for 1 phones

07/01/14 21:34:13  [Device ID: 0] 1/17 flash sbl1 "sbl1.mbn"

07/01/14 21:34:13  [Device ID: 0] 2/17 flash sbl2 "sbl2.mbn"

07/01/14 21:34:14  [Device ID: 0] 3/17 flash sbl3 "sbl3.mbn"

07/01/14 21:34:15  [Device ID: 0] 4/17 flash rpm "rpm.mbn"

07/01/14 21:34:16  [Device ID: 0] 5/17 flash aboot "emmc_appsboot.mbn"

07/01/14 21:34:17  [Device ID: 0] 6/17 flash modem "NON-HLOS.bin"

07/01/14 21:34:26  [Device ID: 0] 7/17 flash fsg "fsg.mbn"

07/01/14 21:34:28  [Device ID: 0] 8/17 erase modemst1

07/01/14 21:34:29  [Device ID: 0] 9/17 erase modemst2

07/01/14 21:34:29  [Device ID: 0] 10/17 flash logo "logo.bin"

07/01/14 21:34:31  [Device ID: 0] 11/17 flash devtree "device_tree.bin"

07/01/14 21:34:32  [Device ID: 0] 12/17 flash boot "boot.img"

07/01/14 21:34:36  [Device ID: 0] 13/17 flash recovery "recovery.img"

07/01/14 21:34:40  [Device ID: 0] 14/17 flash cdrom "cdrom"

07/01/14 21:34:50  [Device ID: 0] 15/17 flash system "system.img"

07/01/14 21:37:08  [Device ID: 0] 16/17 erase tombstones

07/01/14 21:37:09  [Device ID: 0] 17/17 erase cache

07/01/14 21:37:10  [Device ID: 0] reboot

07/01/14 21:37:13  [Device ID: 0] Waiting for others to finish current operation.

07/01/14 21:37:14  The FlashLog key is turned off.

07/01/14 21:37:14  FlashLog file is turned off.

07/01/14 21:37:14  Multi upgrade finished.

 

Any ideas what's happening?

[SamuriHL]

Q: My RAZR HD or M is stuck in AP Fastboot mode with a sticky bit failure.  Help?

A: 

Please Login or Register to see this Hidden Content

  Follow that.

[muppetsuppet]

Well, after quite some effort over the last few days, I seem to be back in business on JB. 

 

You seem nice. 

 

Thank you for your patience and prompt responses!!

[muppetsuppet]

Oh, one more question. Should I re-run the process after coming out of fastboot, since presumably there may still be errors as indicated in the text above?

[kadesxys]

I know someone else has asked and at times I start to get sick of trying to find the right answer. You and your posts have helped me a lot. So if it's already here please just reply the number. Question is what steps do I take in the case of being a person who use your 183 build and the TZ partition? The important note at start of this thread

[SamuriHL]

The op says it all. If you need to upgrade to, or fix, build 183 and then gives links to the appropriate thread.

Sent from my SM-P600 using Tapatalk

[pratul_09]

@samuriHL thanks for the wonderful writeup, I was able to upgrade my razr m to kitkat and unlock the bootloader.

[jtommyj]

Ya know, about 3 weeks ago I got the survey for another soak after I did this, and that was the last I heard. Wonder if they were going to update and went back to the drawing board after this process came out.

[SamuriHL]

It's likely they're going for 4.4.4 at this point.

Sent from my XT1053 using Tapatalk

[jtommyj]

It's likely they're going for 4.4.4 at this point.

Sent from my XT1053 using Tapatalk

I think you're right.

[SamuriHL]

I think you're right.

 

It would be the best move.  And the 2013 droids are getting their soak as we speak, so, yours might be a bit behind.

[nal]

It would be the best move.  And the 2013 droids are getting their soak as we speak, so, yours might be a bit behind.

do you think they'll patch it?

[SamuriHL]

I'm not sure what "it" means.

[pratul_09]

I'm not sure what "it" means.

bootloader loop hole I guess

Sent from my XT907 using Tapatalk

[SamuriHL]

That's widely believed to be patched in the upcoming build for the 2012 droids.  As is the current root exploit.  I thought I made my feelings on that pretty clear with the amount of effort I've put into getting people unlocked while this update is current.  There can be ZERO assumption that they won't patch the unlock exploit in the next build nor can you expect they won't patch up the kernel for known root exploits.  Neither issue should impact ANYONE in this thread.  Once you're unlocked, root exploits no longer matter.  There is a reason, however, that I've said now is the time to unlock with a sense of urgency.  We saw the first time that people who were on the fence, took the next update assuming they could just unlock later (ignoring the warnings that it would likely be patched), and then regretted not doing it. It's seriously foolish at this point not to unlock a device from 2012.  Warranty is not much of an issue at this point and your device is worth more on resale unlocked than it will be locked.  If the update comes and re-patches the hole, I'm not going to have a lot of sympathy for those who chose not to take advantage of it and then whine that they can't root their phone.

 

TLDR: Yes, I suspect root and unlock will be patched.  UNLOCK NOW.

[xKroniK13x]

That's widely believed to be patched in the upcoming build for the 2012 droids. As is the current root exploit. I thought I made my feelings on that pretty clear with the amount of effort I've put into getting people unlocked while this update is current. There can be ZERO assumption that they won't patch the unlock exploit in the next build nor can you expect they won't patch up the kernel for known root exploits. Neither issue should impact ANYONE in this thread. Once you're unlocked, root exploits no longer matter. There is a reason, however, that I've said now is the time to unlock with a sense of urgency. We saw the first time that people who were on the fence, took the next update assuming they could just unlock later (ignoring the warnings that it would likely be patched), and then regretted not doing it. It's seriously foolish at this point not to unlock a device from 2012. Warranty is not much of an issue at this point and your device is worth more on resale unlocked than it will be locked. If the update comes and re-patches the hole, I'm not going to have a lot of sympathy for those who chose not to take advantage of it and then whine that they can't root their phone.

TLDR: Yes, I suspect root and unlock will be patched. UNLOCK NOW.

Also, for those concerned about warranty, as stated, its essentially gone anyway. Only sort of warranties that could be left is insurance, who from what I've seen online, will still cover unlocked phones if the damage is hardware related. Win win for all involved.

Sent from my DROID RAZR M using Tapatalk

[SamuriHL]

BTW, once the update does come, and it's confirmed that it no longer allows for root and/or unlock, I AM locking this thread.  I will NOT be dealing with the dozens of "didn't work" posts.  I will help people root and unlock until that point.  After that, I'm done and will not be dealing with it in PM's either.  They'll go unanswered.  I've been on a crusade to get this done and make sure everyone gets unlocked.  I'm not going to waste any time after it's closed.

[rtbluzz]

Need Help process not working, i am trying to get wifi teather to work I have unlimited data. Phone  SV 182.46.10.xt926 I have installes all apps and no luck.

Thanks for any help

 

do you have to turn on toeowelroot v3 ever time you power on your phone because that is the only way it shows root access.

[SamuriHL]

"no luck" "not working"...."try harder?"  Cause with that much information, that's about all I can tell you.