98.18.78 can't unlock bootloader? - Droid RAZR M Q&A, Help & Troubleshooting

So according to my reading, there's no way to unlock the bootloader if I'm at 98.18.78 or beyond, correct? Does this mean no KitKat also, not even stock? I can get root on my 4.1.2 Razr M, but motopocolypse, etc. fails to get me an unlocked bootloader; status remains locked at 0.

You are obviously getting outdated and wrong information. You can get any stock ROM (be it JB or KK) with a locked BL. Even better, version 18x.46.10 (mind the last 2 digits!!) is BL unlockable, while 18x.46.15 is not. Both are stock KitKat.
So if you want to unlock, just upgrade by RSD Lite to 18x.46.10 (again, mind the 2 digits) and do it from there. General section has the guides you need.
P.S. Some people took the OTA to .10 and succeeded, but I wouldn't suggest taking the risk, because you might be updated to .15 accidentally.
Sent from Google Nexus 4 @ CM12
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]

Related

Pure AOSP for Locked Bootloader?

I was wondering if there was any work being done with a pure AOSP rom or any other roms that will theme with a locked bootloader.
The answer is sort-of...
No, you cannot unlock the boot loader if you the latest ota.
Yes, you can root and install safestrap, then look for a desirable ROM.
The third option I played with is replace as many of the Motorola apps as you can with the aosp versions. It is dangerous, I only tried it with email and that worked great, but I moved on to contacts and totally screwed up the ROM forcing me to flash back to stock and redo everything.
Sent from my Nexus 10 using Tapatalk 2
There is a work around for the latest OTA hehehe
Flash the stock.IMG in fastboot with the toolkit. It will flash a compatible version where you can unlock and root from there.
If you want AOSP... Carbon ROM is the closest in my opinion so far...
Sent from my Nexus 7 using XDA Premium 4 mobile app
Can you elaborate more on this process? What do you mean unlock, I thought that was impossible now? Which toolkit? So confused.
Sent from my Nexus 10 using Tapatalk 2
lukkypuggy said:
There is a work around for the latest OTA hehehe
Flash the stock.IMG in fastboot with the toolkit. It will flash a compatible version where you can unlock and root from there.
If you want AOSP... Carbon ROM is the closest in my opinion so far...
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Has this method been tested and confirmed?
CrocadileUT78 said:
Can you elaborate more on this process? What do you mean unlock, I thought that was impossible now? Which toolkit? So confused.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
There is a Root Toolkit here in one of the forums, look for version 1.20
By unlock I mean unlocking the bootloader. It is only impossible if you don't flash an earlier version of the stock.img.
Yes it is confirmed, that is how I am running Carbon right now
Sent from my XT907 using XDA Premium 4 mobile app
So you had the 78 update, and downgraded, then unlocked bootloader? Everything else I read said that doesn't work. I'm so confused.
Sent from my XT907 using Tapatalk 4
I didnt think one could downgrade if they had a locked boot loader?! Anyone who had actually achieved this please chime in here.
lukkypuggy said:
There is a Root Toolkit here in one of the forums, look for version 1.20
By unlock I mean unlocking the bootloader. It is only impossible if you don't flash an earlier version of the stock.img.
Yes it is confirmed, that is how I am running Carbon right now
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Curious as well how did you go about this? I thought it was impossible to unlock on latest ota. If this is the case, why has this not been brought up earlier?
Sent from my XT907 using Tapatalk 2
CrocadileUT78 said:
So you had the 78 update, and downgraded, then unlocked bootloader? Everything else I read said that doesn't work. I'm so confused.
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Yes, I had the .78 OTA and then I downgraded to a compatible version to get root then unlock and flash a custom ROM.
I don't know if my case was for some reason special but I also never got the "Boot loader is unlocked warning" either.
Sent from my XT907 using XDA Premium 4 mobile app
lukkypuggy said:
Yes, I had the .78 OTA and then I downgraded to a compatible version to get root then unlock and flash a custom ROM.
I don't know if my case was for some reason special but I also never got the "Boot loader is unlocked warning" either.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I might be able to test this, but can you explain, by steps, how you did this?
Sent from my XT907 using Tapatalk 2
lukkypuggy said:
Yes, I had the .78 OTA and then I downgraded to a compatible version to get root then unlock and flash a custom ROM.
I don't know if my case was for some reason special but I also never got the "Boot loader is unlocked warning" either.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did you buy it used? If so, when? If you did, it may have already been unlocked...
Sent from my XT907 using Tapatalk 4
Here is the kit I use: http://forum.xda-developers.com/showthread.php?t=2249773
"Number 1 Explained -- This option requires your phone be in AP Fastboot mode. It will flash the official 4.1.2 System, Kernel, and Radio as well we wipe your data.
Number 2 Explained -- This option requires your phone be in AP Fastboot mode. It will flash the official 4.1.2 Stock Recovery.
Number 3 Explained -- This option requires your phone to be booted normally with USB Debugging enabled, and be already Rooted. This will flash TWRP Recovery by Hashcode.
Number 4 Explained -- This option requires your phone to be booted normally with USB Debugging enabled, and be already Rooted. This will flash CWM Recovery by Hashcode.
Number 5 Explained -- This is Dan Rosenberg's root exploit called 'Motochopper'. This option requires your phone to be booted normally, with USB Debugging enabled.
Number 6 Explained -- This option requires your phone to be booted normally, with USB Debugging enabled. It will install an App version of Dan Rosenberg's Motopocalypse exploit for unlocking the bootloader.
Remember, do not run this utility unless your phone is at 100% battery OR you have bought yourself one of Team Black Hat's Factory-Style Programming Adapters."
Click to expand...
Click to collapse
First backup your data and im not responsible if you cause the apocalypse
OK. chose option #1. It will flash a rootable version.
Next to root, choose option #5.
Next chose option #6 to ULOCK your bootloader.
Next chose either option 3 or 4 for a custom recovery. (I like CWM)
Have fun. that is exactly What I Did.
lukkypuggy said:
Here is the kit I use: http://forum.xda-developers.com/showthread.php?t=2249773
First backup your data and im not responsible if you cause the apocalypse
OK. chose option #1. It will flash a rootable version.
Next to root, choose option #5.
Next chose option #6 to ULOCK your bootloader.
Next chose either option 3 or 4 for a custom recovery. (I like CWM)
Have fun. that is exactly What I Did.
Click to expand...
Click to collapse
So just making sure, you were on the 4.1.2 ota prior to doing this right? Based on the notice posted on that utility thread, you are not suppose to use it if you were on the latest ota, which is the same one that locked the bootloader (unless stood corrected). So did you take a leap of faith and went ahead and did it even though it was warned to not do it, and did you ended up succeeding?
Was your phone bought new, or do you know if it's previous owner unlocked it before you got a hold of it, which would explain how you were able to, IF it wasn't used and modified prior?
Also, when you flashed the "compatible version" was it that you flashed the 4.1.2 update found in the utility or did you change it out to another image found here: http://sbf.droid-developers.org/scorpion_mini_xt907/list.php
Just wandering, because if so, this is phenomenal news for those who have do not possess the ability to unlock normally because they took the recent ota. I am sure that like everyone else, including myself, we just want to know if this is safe to follow or not, no pointing fingers or bad accusations.
Thanks
MistPhoenix said:
So just making sure, you were on the 4.1.2 ota prior to doing this right? Based on the notice posted on that utility thread, you are not suppose to use it if you were on the latest ota, which is the same one that locked the bootloader (unless stood corrected). So did you take a leap of faith and went ahead and did it even though it was warned to not do it, and did you ended up succeeding?
Was your phone bought new, or do you know if it's previous owner unlocked it before you got a hold of it, which would explain how you were able to, IF it wasn't used and modified prior?
Also, when you flashed the "compatible version" was it that you flashed the 4.1.2 update found in the utility or did you change it out to another image found here: http://sbf.droid-developers.org/scorpion_mini_xt907/list.php
Just wandering, because if so, this is phenomenal news for those who have do not possess the ability to unlock normally because they took the recent ota. I am sure that like everyone else, including myself, we just want to know if this is safe to follow or not, no pointing fingers or bad accusations.
Thanks
Click to expand...
Click to collapse
Yes, I did indeed took a leap of faith.
The phone was brand spanking new from Best Buy.
I flashed the one found in the utility.
If you dont trust it I TOTALY understand. I just wanted it so bad that I really didnt care.
lukkypuggy said:
Yes, I did indeed took a leap of faith.
The phone was brand spanking new from Best Buy.
I flashed the one found in the utility.
If you dont trust it I TOTALY understand. I just wanted it so bad that I really didnt care.
Click to expand...
Click to collapse
I believe you... Now the question is who is brave enough to take a leap of faith? I would love to unlock by boot loader to ensure I will get the latest Android versions moving forward. I don't trust Verizon to let an upgrade thru beyond 4.1.2. I would test your procedure myself, but I'm too dependent on my phone for work right now.
So... Anyone? Anyone? Be a hero folks, somebody take the plunge! Pretty please?
Sent from my Nexus 10 using Tapatalk 2
---------- Post added at 01:06 AM ---------- Previous post was at 12:51 AM ----------
Also, I feel obligated to mention this, and i do it with a heavy heart... A few weeks ago I seriously screwed up my phone playing with the contacts apk, breaking my ability to view my contacts or dial a number. I got desperate enough that even though I was on .78, used the utility and stock image to revert back everything fresh. I was so relieved when I saw it worked despite the warnings and being a slightly older rom version. Once I did that, I'm 75% sure I did trying unlocking the BL before installing .78 OTA, and it did not work. I figured I had nothing to lose at that point, and when it failed I just shrugged and continued getting my phone back to normal. Sorry if this discourages any brave souls, but again I am not 100% sure I followed the same steps Mentioned in this thread.
Sent from my Nexus 10 using Tapatalk 2
lukkypuggy said:
Yes, I did indeed took a leap of faith.
The phone was brand spanking new from Best Buy.
I flashed the one found in the utility.
If you dont trust it I TOTALY understand. I just wanted it so bad that I really didnt care.
Click to expand...
Click to collapse
Thank you for the response. I do plan on testing this later on today on a locked, new M so I will be able to verify completely. Everyone sit tight
Sent from my XT907 using Tapatalk 2
CrocadileUT78 said:
I believe you... Now the question is who is brave enough to take a leap of faith? I would love to unlock by boot loader to ensure I will get the latest Android versions moving forward. I don't trust Verizon to let an upgrade thru beyond 4.1.2. I would test your procedure myself, but I'm too dependent on my phone for work right now.
So... Anyone? Anyone? Be a hero folks, somebody take the plunge! Pretty please?
Sent from my Nexus 10 using Tapatalk 2
---------- Post added at 01:06 AM ---------- Previous post was at 12:51 AM ----------
Also, I feel obligated to mention this, and i do it with a heavy heart... A few weeks ago I seriously screwed up my phone playing with the contacts apk, breaking my ability to view my contacts or dial a number. I got desperate enough that even though I was on .78, used the utility and stock image to revert back everything fresh. I was so relieved when I saw it worked despite the warnings and being a slightly older rom version. Once I did that, I'm 75% sure I did trying unlocking the BL before installing .78 OTA, and it did not work. I figured I had nothing to lose at that point, and when it failed I just shrugged and continued getting my phone back to normal. Sorry if this discourages any brave souls, but again I am not 100% sure I followed the same steps Mentioned in this thread.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
BTW I never did get the unlock app to actually work (just remembered).
http://forum.xda-developers.com/showthread.php?t=2226729
http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
Download this .zip file once you have flashed the compatible stock version and have root.
As long as it says status code: 3 in the bootloader you are unlocked
Ok guys here are the results, sadly I could not achieve unlock with a unmodified, unrooted Razr M :
1. Turned off and started AP Fastboot mode. Used mattlgroff's Razr M Utility to flash to Android 4.1.2 98.15.66.XT907.Verizon.en.US system image. The flash worked perfectly I was able to downgrade to ota prior before the locked bootloader.
2. Used mattlgroff's Utility to root my device (step 5). I was able to root the device with SuperSU.
3. Used the seperate motopocalypse program by Dan Rosenberg found here http://forum.xda-developers.com/showthread.php?t=2226729. It ran and rebooted to AP fastboot mode. I received the folowing errors:
"TrustZone target address resolved to 2a020a02"
"TrustZone write failed: -11"
This indicated that the bootloader TrustZone which is needed to unlock, was still locked and that it couldn't make changes to properly unlock the device.
So for the time being, this method to unlock the bootloader does not work. I am thinking about trying the 4.1.1 system image instead, but I fear that since the bootloader is its own entity, that those that took the recent OTA had the TrustZone patched to the point where it cannot be written to period, even on a lower firmware. The best thing that could happen is for a miracle to occur and an exploit to be found to write to the TrustZone again.
MistPhoenix said:
Ok guys here are the results, sadly I could not achieve unlock with a unmodified, unrooted Razr M :
1. Turned off and started AP Fastboot mode. Used mattlgroff's Razr M Utility to flash to Android 4.1.2 98.15.66.XT907.Verizon.en.US system image. The flash worked perfectly I was able to downgrade to ota prior before the locked bootloader.
2. Used mattlgroff's Utility to root my device (step 5). I was able to root the device with SuperSU.
3. Used the seperate motopocalypse program by Dan Rosenberg found here http://forum.xda-developers.com/showthread.php?t=2226729. It ran and rebooted to AP fastboot mode. I received the folowing errors:
"TrustZone target address resolved to 2a020a02"
"TrustZone write failed: -11"
This indicated that the bootloader TrustZone which is needed to unlock, was still locked and that it couldn't make changes to properly unlock the device.
So for the time being, this method to unlock the bootloader does not work. I am thinking about trying the 4.1.1 system image instead, but I fear that since the bootloader is its own entity, that those that took the recent OTA had the TrustZone patched to the point where it cannot be written to period, even on a lower firmware. The best thing that could happen is for a miracle to occur and an exploit to be found to write to the TrustZone again.
Click to expand...
Click to collapse
Mine had the -11 error also but it also said status code 3 in the actually bootloader, Then I flashed CWM and that was it, now I have CM10.1.3 STABLE.
Maybe double check?

[SOLVED][Q] Will flashing the latest official firmware relock the bootloader?

Greetings to you all, will be getting my Droid RAZR M tomorrow so this is my 1st post around here
Alright, coming from a Photon Q, I have much experience with flashing custom ROMs, recoveries, etc. What I am now concerned with is that, from what I've read in some threads, the latest official firmware (98.30.1) and the one before it "locks the BL".
I purchased both my Photon Q and RAZR M from my resellers in pre-unlocked condition (i.e. they were on ICS and BL unlocked), and flashing the latest firmware on the Photon Q doesn't relock BL. If it DOES relock BL on RAZR M, does that mean if I want custom ROMs, I should start the steps directly from ICS? Then how would I be able to get the latest radios, BL and other additions (potentially affects custom ROMs)?
Thank you in advance for any clarification.
Sent from Google Nexus 4 @ CM11
AndyYan said:
Greetings to you all, will be getting my Droid RAZR M tomorrow so this is my 1st post around here
Alright, coming from a Photon Q, I have much experience with flashing custom ROMs, recoveries, etc. What I am now concerned with is that, from what I've read in some threads, the latest official firmware (98.30.1) and the one before it "locks the BL".
I purchased both my Photon Q and RAZR M from my resellers in pre-unlocked condition (i.e. they were on ICS and BL unlocked), and flashing the latest firmware on the Photon Q doesn't relock BL. If it DOES relock BL on RAZR M, does that mean if I want custom ROMs, I should start the steps directly from ICS? Then how would I be able to get the latest radios, BL and other additions (potentially affects custom ROMs)?
Thank you in advance for any clarification.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
While they could relock it - on the latest they have not. You are safe.
aviwdoowks said:
While they could relock it - on the latest they have not. You are safe.
Click to expand...
Click to collapse
Thanks, I'm relieved.
Then what are the complaints about? Is it that someone with bad luck purchased his BL-locked M with 98.30.1 preloaded and found that unlocking is impossible?
Sent from Google Nexus 4 @ CM11
Yea.
aviwdoowks said:
Yea.
Click to expand...
Click to collapse
Thanks again, just got my M and flashed latest successfully (that "DROOOOOOOOOOOOID" voice scared me a lot ).
Sent from Google Nexus 4 @ CM11

how to root with 4.1.2

i hate posting questions like this but i searched and cannot answer this on my own. probably due to the newer updates that have taken over the spotlight
i have a xt907 i got from my dad to use temporarily and cannot figure out how to root it. it has the 98.18.94.xt907.verizon.en.us under system version
if anyone could point me in the right direction i would greatly appreciate it
There are a few ways I've read about. The following link was reported to work on the last 4.1.2 update.
http://forum.xda-developers.com/showthread.php?t=2602592
You could update to the current 4.4.2 software, unlock the bootloader, and then return to 4.1.2 and use SuperSU with a custom recovery like TWRP, which is mostly covered in:
http://forum.xda-developers.com/showthread.php?t=2786016
I thought I read that towelroot may work on prior Android versions, but I have not read about people using it on 4.1.2 here.
I used towelroot on 4.1.2... But I recommend you to update to kk unlock your boot loader then if you want downgrade back to jb
Sent from my XT907 using XDA Premium 4 mobile app

[Q] RazrM Device Type Compatibility

I wanted to try out Slim Rom, and the official supported devices for Slim include "moto_msm8960
(unified xt925 and xt926)". Is it likely that installing this Rom would brick the xt907? or is it likely that it would work just fine? Please let me know your educated guess, if you're not 100% sure. Thanks in advance.
It says it's a "unified" build so it should work with all moto_msm8960 family devices, including our M.
Problem is, you gotta know whether this ROM is for JB Bootloader or KK Bootloader. I checked the SlimKat thread in Droid RAZR HD section and they say it's for KK BL, at least for the latest builds, so you'll also have to be on KK BL to even try it.
And as always, do a nandroid backup before even attempting!
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]

[Q] Best ROM upgrade for 98.15.66

Hello,
My wife has RAZR M running stock and rooted 98.15.66 rom. Bootloader was never unlocked but I think it's still possible with this version of rom. am I right? Last time I was doing something with her phone was almost 2 years ago and I'm more samsung guy so need some directions here She loves this phone and doesn't want to get anything new. Phone is getting to run slower so it needs cleanup. Is it worth to upgrade it to KK rom or just do factory restore and set it up from scratch on this 4.1.2 rom? Any major bugs on stock KK rom? CM12 has too much bugs as of now for her. What about CM11, is there fully functional and bugs free version for RAZR M available?
.66 is indeed unlockable right away, but just so you could experience stock KitKat and see if it's more fitting, simply upgrade to 183.46.10 (ATTENTION: not .15!!!) and unlock the bootloader there. Guides are there in the General section. Note that you will lose data and internal storage contents, so back up properly.
After that if you feel uncomfortable with KitKat, you can freely downgrade to Jelly Bean whenever you prefer.
Haven't met any serious bugs even in CM12, let alone CM11. Don't know what kind of deal-breaking bug you're talking about.
Sent from Google Nexus 4 @ CM12
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
AndyYan said:
.66 is indeed unlockable right away, but just so you could experience stock KitKat and see if it's more fitting, simply upgrade to 183.46.10 (ATTENTION: not .15!!!) and unlock the bootloader there. Guides are there in the General section. Note that you will lose data and internal storage contents, so back up properly.
After that if you feel uncomfortable with KitKat, you can freely downgrade to Jelly Bean whenever you prefer.
Haven't met any serious bugs even in CM12, let alone CM11. Don't know what kind of deal-breaking bug you're talking about.
Click to expand...
Click to collapse
According to Strife89 post here: http://forum.xda-developers.com/showpost.php?p=58531079&postcount=80 there are couple of bugs that I know my wife is not gonna like for example microphone level and able hear own voice when using headphones.
Do you think it's better to unlock bootloader before upgrading to KK or it's doesn't matter? Thanks.
SotYPL said:
According to Strife89 post here: http://forum.xda-developers.com/showpost.php?p=58531079&postcount=80 there are couple of bugs that I know my wife is not gonna like for example microphone level and able hear own voice when using headphones.
Do you think it's better to unlock bootloader before upgrading to KK or it's doesn't matter? Thanks.
Click to expand...
Click to collapse
I would suggest that you unlock the bootloader now before you upgrade.
Sent from my Moto G™
Unlock unlock unlock. It worth the candle. I think your wife will be happy with cleaned up 4.1.2 or 4.4.2. Last one is more stylish, and comfortable in use, as for me.
OK is that correct order to get it upgraded?
1. Unlock boot loader using apk or Motopocalypse from this thread: http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
2. Flash KK firmware using RSD Lite but I'm not sure which image from this: http://www.drdevs.com/devs/FXZ-files/XT907 (Droid RAZR M)/ website is safe to use. Can I use latest one 20.62-15.1 after unlocking boot loader or do I have to stay stay with 20.62-10?
3. Flash TWRP from this thread: http://forum.xda-developers.com/showthread.php?t=2776515
4. FLash SuperSU from recovery
Is that correct way to handle it?

Categories

Resources