Im sorta confused and can't get my booloader unlocked on my razr m. I tried through the utility after i went back to stock 4.1.2 and rerooted. But i get an error trust zone write failed -11. Wat am i doing wrong. I have flashed back to stock so many times and rerooted through both utlitys. Help Please
twilightmsift said:
Im sorta confused and can't get my booloader unlocked on my razr m. I tried through the utility after i went back to stock 4.1.2 and rerooted. But i get an error trust zone write failed -11. Wat am i doing wrong. I have flashed back to stock so many times and rerooted through both utlitys. Help Please
Click to expand...
Click to collapse
Did you try Matt's utility in the DEV forum? Have usb debugging set?
aviwdoowks said:
Did you try Matt's utility in the DEV forum? Have usb debugging set?
Click to expand...
Click to collapse
yea already tried it the utlilty gives me the error.
twilightmsift said:
yea already tried it the utlilty gives me the error.
Click to expand...
Click to collapse
I'm getting the same exact issue. I have a refurb. I was able to root and unlock my previous razr hd. After that one broke and I got a replacement I followed the same steps and still I cannot unlock the bootloader...
You may have covered all of this but im throwing it out there in case something helps:
- Did you take or are you on the most recent OTA update? if so that blocks the unlock exploit (i think this was pushed out over the past couple weeks)
- are you sure you are rerooted and using a working version of superSU?
- have you tried using the Motopocalypse.zip and running that tool vs using Mats utility? Make sure you are giving root privileges when / if it asks.
PantherVT said:
You may have covered all of this but im throwing it out there in case something helps:
- Did you take or are you on the most recent OTA update? if so that blocks the unlock exploit (i think this was pushed out over the past couple weeks)
- are you sure you are rerooted and using a working version of superSU?
- have you tried using the Motopocalypse.zip and running that tool vs using Mats utility? Make sure you are giving root privileges when / if it asks.
Click to expand...
Click to collapse
I believe my phone came with the latest update. At this point, does that mean I can't flash back down to an older version and unlock the boot loader?
Sent from my DROID RAZR HD using xda app-developers app
Correct, you are, as they say, up the creek :/
But most people seem confident there will be another exploit... I dunno.
fcardona86 said:
I'm getting the same exact issue. I have a refurb. I was able to root and unlock my previous razr hd. After that one broke and I got a replacement I followed the same steps and still I cannot unlock the bootloader...
Click to expand...
Click to collapse
That utility will only work with the RAZR M
Sent from my XT907 using xda app-developers app
PantherVT said:
You may have covered all of this but im throwing it out there in case something helps:
- Did you take or are you on the most recent OTA update? if so that blocks the unlock exploit (i think this was pushed out over the past couple weeks)
- are you sure you are rerooted and using a working version of superSU?
- have you tried using the Motopocalypse.zip and running that tool vs using Mats utility? Make sure you are giving root privileges when / if it asks.
Click to expand...
Click to collapse
i took the update when i first got the phone but used the utlity to go back to 4.1.2 for the march version. im rooted with my supersu updated n yes i tried both the app n zip
twilightmsift said:
i took the update when i first got the phone but used the utlity to go back to 4.1.2 for the march version. im rooted with my supersu updated n yes i tried both the app n zip
Click to expand...
Click to collapse
What utility did you use to go backwards? I also took the update but would love to be able to go back and get root and unlocked bootloader.
jklong03 said:
What utility did you use to go backwards? I also took the update but would love to be able to go back and get root and unlocked bootloader.
Click to expand...
Click to collapse
There is a post on DroidRzr where they are working a root method for the update. It requires fast booting back to the previous update. However, you still won't be able to unlock because the new OTA patches the security vulnerability that allowed the unlock.
From what I've read, going backwards does not reopen the exploit.
Sent from my Droid Razr M using xda app-developers app
Related
TBH is in the process of right now releasing a leaked Moto build of Gingerbread 2.3.3. As of right now, they have been unable to root it, as all known root methods appear to no longer work. Anyone want to tackle it?
obviously not gonna be easy....if TBH can't do it.. I doubt anyone can
Don't think anything is impossible. They just got the release yesterday. It sometimes takes a collaboration of several devs to get root.
If my download ever finishes I gonna try like hello and throw everything I have at it. Lol.
Sent from my DROIDX using XDA Premium App
i have an idea about getting root but im not sure if it will work or not but pretty much instead of rebooting after installing 2.3.3 you install the su.zip file found somewhere on xda and you should have root but im not 100% sure
luigi90210 said:
i have an idea about getting root but im not sure if it will work or not but pretty much instead of rebooting after installing 2.3.3 you install the su.zip file found somewhere on xda and you should have root but im not 100% sure
Click to expand...
Click to collapse
That will soft-brick the phone and you'll have to SBF from RSDLite. You can't install any other zips directly after installing a ROM or it won't pass the signature verification on reboot.
Sent from my DROIDX using Tapatalk
I'll be waiting in hopes you all find root!!!
Anyone try the SuperUser app in the market... says it worked flawlessly in GB for N1..?
cbaty08 said:
Anyone try the SuperUser app in the market... says it worked flawlessly in GB for N1..?
Click to expand...
Click to collapse
Which app is it?
Doesn't the Nexus S on 2.3.3 have root?
Edit: nevermind. Locked bootloader.
Sent from my Xoom using Tapatalk
oshigeru said:
Doesn't the Nexus S on 2.3.3 have root?
Edit: nevermind. Locked bootloader.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Locked bootloader and root access are two different things.
tried SuperOneClick(special), same process for 3.4.2 blur..no go.
has anyone tried z4root?
wmedina1991 said:
has anyone tried z4root?
Click to expand...
Click to collapse
Yes, failed too..
wmedina1991 said:
has anyone tried z4root?
Click to expand...
Click to collapse
Several times. no luck
rocko73 said:
Locked bootloader and root access are two different things.
Click to expand...
Click to collapse
well the nexus s/one use a method which requires the bootloader to be unlocked in order to obtain root so technically speaking they are the same in this case
so far though i have been reading about a gingerbreak exploit from the same guy who released rageinthecage exploit
maybe if we contacted him he might release gingerbreak so we can have root access
that sucks
db306 said:
Which app is it?
Click to expand...
Click to collapse
Search the market for "Superuser" and there is an app that has comments stating it worked for GB on N1.
I downloaded it and ran it and it seemed to have done the first part of what it needed to do fine... but now the next step is flash this .zip update that is on the memory card through recovery...... I don't want to be the genea pig as I need my phone atm...
EDIT: Just read luigi's post.. not sure now...
luigi90210 said:
well the nexus s/one use a method which requires the bootloader to be unlocked in order to obtain root so technically speaking they are the same in this case
so far though i have been reading about a gingerbreak exploit from the same guy who released rageinthecage exploit
maybe if we contacted him he might release gingerbreak so we can have root access
Click to expand...
Click to collapse
Where did you see this?
Also, I wonder if the below Kernel exploit could be used..
http://seclists.org/fulldisclosure/2010/Dec/85
I may play around with this when I get home tonight. If anyone else wants to in the meantime, feel free.
luigi90210 said:
well the nexus s/one use a method which requires the bootloader to be unlocked in order to obtain root so technically speaking they are the same in this case
so far though i have been reading about a gingerbreak exploit from the same guy who released rageinthecage exploit
maybe if we contacted him he might release gingerbreak so we can have root access
Click to expand...
Click to collapse
looks promising, says in his quote he didnt want to release till more 2.3 devices were out ( so they couldnt fix his exploit ) but hopefully he will release it soon ish
Is there anyway to revert gingerbread back to froyo until the devs can root it? There has got to be a way. Need my net back
Sent from my PG06100 using XDA App
As of right now there is no way to revert back to froyo. Take a look at this thread.
http://forum.xda-developers.com/showthread.php?t=1142115
Sent from my PG06100 using XDA App
That sucks..... I cant beleive how much i screwed myself
Sent from my PG06100 using XDA App
well you r not the only one, I hate my self because i clicked upgrade. I lost lost my net on metropcs flashed evo
Yeah i live in a tech dead zone. The only net available is through my phone...
Sent from my PG06100 using XDA App
honorlost84 said:
Is there anyway to revert gingerbread back to froyo until the devs can root it? There has got to be a way. Need my net back
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Yes, you can but it's a pain in the butt. Go to this thread and then download the original stock firmware. Make sure USB debugging is turned on also.
To install the file you need to have HTC Sync installed and running. Double-click the file and it should recognize the phone and start installing after some input from you.
If you get a USB error, try booting into the bootloader and installing the exe in the same manner.
I just did this last night because I was in the same situation. It works.
Now you can re-root.
bnampel said:
Yes, you can but it's a pain in the butt. Go to this thread and then download the original stock firmware. Make sure USB debugging is turned on also.
To install the file you need to have HTC Sync installed and running. Double-click the file and it should recognize the phone and start installing after some input from you.
If you get a USB error, try booting into the bootloader and installing the exe in the same manner.
I just did this last night because I was in the same situation. It works.
Now you can re-root.
Click to expand...
Click to collapse
You were able to downgrade to Froyo with this RUU? If so, that's great.. your the only person I've seen post successfully downgrading and being able to root.
bnampel said:
Yes, you can but it's a pain in the butt. Go to this thread and then download the original stock firmware. Make sure USB debugging is turned on also.
To install the file you need to have HTC Sync installed and running. Double-click the file and it should recognize the phone and start installing after some input from you.
If you get a USB error, try booting into the bootloader and installing the exe in the same manner.
I just did this last night because I was in the same situation. It works.
Now you can re-root.
Click to expand...
Click to collapse
I think everyone that ran the factory upgrade has tried this and you seem to be the only one that it has worked for. It goes through the motions then you get error 140 or 170 i think: Bootloader version error. Please get the correct rom update utility and try again
I have rooted my phone and installed the rockmod_devroms_2.3.4.1-speedy and broke my root istalling "extras" can I just try the rooting procesess again or have to revert bak to froyo?
Sent from my PG06100 using XDA App
jimbowski51 said:
I have rooted my phone and installed the rockmod_devroms_2.3.4.1-speedy and broke my root istalling "extras" can I just try the rooting procesess again or have to revert bak to froyo?
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
What do you mean you broke root? Do you still have s-off and access to recovery?
Lancerz said:
I think everyone that ran the factory upgrade has tried this and you seem to be the only one that it has worked for. It goes through the motions then you get error 140 or 170 i think: Bootloader version error. Please get the correct rom update utility and try again
Click to expand...
Click to collapse
I guess I feel pretty lucky then. I'm fairly certain I didn't miss any steps.
When I upgraded to the gingerbread stock ROM I used this link and chose the "no hboot included" option. Maybe that saved me.
bnampel said:
I guess I feel pretty lucky then. I'm fairly certain I didn't miss any steps.
When I upgraded to the gingerbread stock ROM I used this link and chose the "no hboot included" option. Maybe that saved me.
Click to expand...
Click to collapse
That's not the same as accepting the ota.
Sent from my Gingerbread Speedy 4G using Tapatalk
bnampel said:
I guess I feel pretty lucky then. I'm fairly certain I didn't miss any steps.
When I upgraded to the gingerbread stock ROM I used this link and chose the "no hboot included" option. Maybe that saved me.
Click to expand...
Click to collapse
Yeah, you didnt do the ota update then.
Lancerz said:
Yeah, you didnt do the ota update then.
Click to expand...
Click to collapse
It's still the same update. Whether I installed it through an OTA update or from the bootloader doesn't matter.
You guys can get into the bootloader right? Take one of those modified "official" updates, rename it to PG06IMG.zip and flash it from the bootloader. Then do my first post and flash to Froyo so you can root again. May be worth a shot.
bnampel said:
It's still the same update. Whether I installed it through an OTA update or from the bootloader doesn't matter.
You guys can get into the bootloader right? Take one of those modified "official" updates, rename it to PG06IMG.zip and flash it from the bootloader. Then do my first post and flash to Froyo so you can root again. May be worth a shot.
Click to expand...
Click to collapse
This has already been tried and covered in this thread here: http://forum.xda-developers.com/showthread.php?t=1142115&page=2
I posted the same link in the beginning of this thread.
Unless you have an engineering bootloader, like after you rooted, you can only flash an an un modified pg0610.zip from htc. So any one who took an over the air update is SOL on that front. Best hope now is that the evo 3d root can be applied here
Sent from my PG06100 using XDA App
Wow, I almost just majorly screwed myself (again). I have the shift and its just been sitting in my drawer, waiting to be activated after carefully reading thru the forums so i do not true brick it again.
Anyway, for some weird reason, pulled it out just to charge the battery, and it requested to do an update (since it was connected via wifi), it tried and got stuck (praise the Lord) and Im just now reading this realizing I almost just GOOFED UP BIG TIME. So, wanted to take the time to thank the OP for this post which made me aware of the fact that I would be SOL if I had've upgrade and to prevent me from upgrading. THANKS!!!
xPSYB0RGx said:
Wow, I almost just majorly screwed myself (again). I have the shift and its just been sitting in my drawer, waiting to be activated after carefully reading thru the forums so i do not true brick it again.
Anyway, for some weird reason, pulled it out just to charge the battery, and it requested to do an update (since it was connected via wifi), it tried and got stuck (praise the Lord) and Im just now reading this realizing I almost just GOOFED UP BIG TIME. So, wanted to take the time to thank the OP for this post which made me aware of the fact that I would be SOL if I had've upgrade and to prevent me from upgrading. THANKS!!!
Click to expand...
Click to collapse
sooo.... hit the thanks button then
They've recently rooted the Sensation and EVO 3D...hopefully it will trickle down to us Shift owners....
Stuke00 said:
sooo.... hit the thanks button then
Click to expand...
Click to collapse
I thanked the OP, and I thanked u for reminding me to be "thankful"!!
I have found a lot of information on the forums about updating to 2.3.4 and ending up with a hard brick and am getting a little scared about it. I do think most of the bricks have to do with unlocking the bootloader (at least that's what I understood from the forums).
I currently have a rooted Atrix running 4.1.83. I don't have any other mods installed and I haven't unlocked my bootloader. At this point I just want to update my phone to 4.5.91 and have it be rooted. I don't care about unlocking the bootloader at all.
Which method is best for me? Can I just install the OTA update thru the notification I'm getting on my phone? Or do I need to follow one of the complex processes listed on the forums here. Once again, I don't really need to unlock my bootloader. I just need to be rooted after I update.
Thanks in advance.
if you dont want the bootloader unlocked just OTA..
then root here..
http://briefmobile.com/motorola-atrix-4g-root
or
http://forum.xda-developers.com/showpost.php?p=15872818&postcount=69
defnow said:
if you dont want the bootloader unlocked just OTA..
then root here..
http://briefmobile.com/motorola-atrix-4g-root
or
http://forum.xda-developers.com/showpost.php?p=15872818&postcount=69
Click to expand...
Click to collapse
I'm rooted on 4.1.83 & have my webtop modded...can I OTA and then root?
Sent from my "Emo" rooted Motorola Atrix! Emo Thinks Possible!
maybe ...no
I didn't modify system app bUT just a few settings files only to get status7 and failed to update in recovery (official )
then I tried Motorola software update via PC and It succeeded please try it
Sent from my MB860 using XDA App
blackangel104 said:
I'm rooted on 4.1.83 & have my webtop modded...can I OTA and then root?
Sent from my "Emo" rooted Motorola Atrix! Emo Thinks Possible!
Click to expand...
Click to collapse
From what I've read ..no. You have to OTA from a clean state ..meaning ..no mods. You may soft brick. Hopefully someone will correct me if im wrong..
Sent from my MB860 using XDA App
defnow said:
From what I've read ..no. You have to OTA from a clean state ..meaning ..no mods. You may soft brick. Hopefully someone will correct me if im wrong..
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Ok thanks because I don't want any bricks
Sent from my "Emo" rooted Motorola Atrix! Emo Thinks Possible!
defnow said:
if you dont want the bootloader unlocked just OTA..
then root here..
http://briefmobile.com/motorola-atrix-4g-root
or
http://forum.xda-developers.com/showpost.php?p=15872818&postcount=69
Click to expand...
Click to collapse
Worked like a charm. Thank you!
defnow said:
From what I've read ..no. You have to OTA from a clean state ..meaning ..no mods. You may soft brick. Hopefully someone will correct me if im wrong..
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I was rooted with webtop mod on 1.83 (no Pudding), and there was no soft brick - the install wouldn't get past verification and never actually modified the system. Rebooting after the failure would bring me right back to the previous state.
I ended up flashing 1.83 SBF, upgrading OTA, rooting, then restoring user apps from Titanium.
YMMV.
Sent from my Atrix using Tapatalk.
It seems, so far anyway, that if you OTA you get a new bootloader that will hard brick you if you try to revert to a previous version. DO NOT flash any sbf files that have a locked bootloader if you OTA! If you start with 4_1.8.3, unlock your bl with pudding, and install a KennethPenn or similar non-OTA based 2.3.4, you keep the original bootloader and can flash back to Froyo.
I have not seen it spelled out this clearly, so I hope this helps someone looking to upgrade. I recommend sticking to non-OTA versions for now.
After OTA update, what happen???
I have my Atrix rooted, and have sideloading. After downloading update (OTA), & start to instal the update, this appear to my screen.
Is this what called "brick"? What should I do now? Flash it?
elias.parasini said:
I have my Atrix rooted, and have sideloading. After downloading update (OTA), & start to instal the update, this appear to my screen.
Is this what called "brick"? What should I do now? Flash it?
Click to expand...
Click to collapse
No.
10
kimmikolter said:
No.
10
Click to expand...
Click to collapse
Could u be more specific, please? I try replace the batery (pull & put it back) & it run again, normaly, with the previous version.
Just want to know why, the file was corrupt or something. So I can prevent on my next try.
Sorry for my bad English. Thank anyway
Why on gods green earth would you ota update and eliminate the possibility of unlocking your bootloader? Just plain dumb if you ask me. Maybe at this point you see no purpose in it but I assure you that down the road you will wish you had not ran the ota. You don't have to worry about bricking your phone if the process is done correctly.
Sent from my MB860
RAZR HD and RAZR M Updates Fix the Kernel Exploit for Unlocking Bootloaders
The question I've yet to see answered is if it affects those who are already unlocked. Meaning, if I flash this will I have any problem putting custom recovery back on....I'm tempted just so we can answer that question.
SamuriHL said:
The question I've yet to see answered is if it affects those who are already unlocked. Meaning, if I flash this will I have any problem putting custom recovery back on....I'm tempted just so we can answer that question.
Click to expand...
Click to collapse
Once u unlock it can't be relocked because the Bootloader Qfuse is blown when u unlock the Bootloader
Sent from my XT926 using Tapatalk 2
krazyace35 said:
Once u unlock it can't be relocked because the Bootloader Qfuse is blown when u unlock the Bootloader
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
It's not that simple, I'm afraid. Having talked to Dan R about this subject, it's not as straightforward as that. Yes, one of the qfuses is blown and causes the phone to go into unlocked "mode" (for lack of a better description) but there isn't just one qfuse.....
SamuriHL said:
It's not that simple, I'm afraid. Having talked to Dan R about this subject, it's not as straightforward as that. Yes, one of the qfuses is blown and causes the phone to go into unlocked "mode" (for lack of a better description) but there isn't just one qfuse.....
Click to expand...
Click to collapse
I was just stating what I was told by several other developers but Dan should know since he unlocked it to start with. Thanks for letting me know that.
Sent from my XT926 using Tapatalk 2
krazyace35 said:
I was just stating what I was told by several other developers but Dan should know since he unlocked it to start with. Thanks for letting me know that.
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
I'm one of the ones that originally thought that since the qfuse was blown it couldn't be relocked, but, Dan corrected me and said it's technically possible since there's more than one qfuse. However, that being said, it's incredibly unlikely to ever happen. If they got it wrong and relocked a dev device, for instance, they could be in some trouble. So I'm not too concerned but it's something I like to at least consider with these OTA's.
SamuriHL said:
I'm one of the ones that originally thought that since the qfuse was blown it couldn't be relocked, but, Dan corrected me and said it's technically possible since there's more than one qfuse. However, that being said, it's incredibly unlikely to ever happen. If they got it wrong and relocked a dev device, for instance, they could be in some trouble. So I'm not too concerned but it's something I like to at least consider with these OTA's.
Click to expand...
Click to collapse
Yea they would have to unlock those devices for everyone. I won't have to worry about getting relocked because I love 4.2.2 and love flashing roms
Sent from my XT926 using Tapatalk 2
krazyace35 said:
Yea they would have to unlock those devices for everyone. I won't have to worry about getting relocked because I love 4.2.2 and love flashing roms
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
I just finished installing the update. I did get an assert failed at the end of the update, though. assert failed: motorola.bl.backup(). LOL. I can guess what that is and why it failed. As soon as it's done with the android upgrade script I'll put TWRP back on and try nandroiding it. I'm likely to go back to CM 10.1 shortly but I wanted the updated radios and to find out for sure if anyone had to worry about this update who's unlocked.
The current soak removes root but does not lock the bootloader.
Root can be kept with VoodooOTA.
I can attest to the above since I just went through it.
I have protected and unrooted via Voodoo, but how did you uninstall TWRP or get around that? Found the update in the cache directory, but obviously you can't just install from there.
Not so much an uninstall. You have to flash stock recovery. You can get the MR2 FXZ and flash it from that easy enough.
I'm not on this new update anymore. I don't want to scare people with my story, but, I actually managed to brick temporarily an unlocked phone. If I didn't have a backup to restore I could have been in quite a bit of trouble. I'm probably about to brick it again cause I need to know a few things about this stupid update and unlocked phones. And my curiosity won't allow me to leave it alone for long. I do wish we had an FXZ but such is life. It's possible I may not be able to get this update reinstalled without one though.
My apologies for coming into this discussion late... What update are we talking about? I am on 4.1.2, rooted, unlocked, but have no updates waiting in my "system updates". Or is my phone just one of the last to receive an OTA... AGAIN...
EDIT: Does it matter that I used the Utility 2.0 to get to 4.1.2 and not a previous OTA?
New soak test that got leaked this morning. Will be pushing out in a week or so most likely.
Thanks Samurai! Not only for keeping me informed, but also for working with the OTA leak to figure all of this out for us not-as-capable folk prior to full-scale release.
Don't mention it. Happy to help. This update is a pain in my....uh anyway. I got MR2 back on my phone...mostly. Backing it up and will attempt to install the update again.
---------- Post added at 03:27 PM ---------- Previous post was at 02:53 PM ----------
Update is now in fact installed, rooted, and is backing up in the new version of TWRP (2.6.0.0) that Hashcode just gave us. (It's up on goo). Finally.
the soak test has been released, i the received update about 2pm eastern today
So how do we update and keep all well?
Sent from my DROID RAZR HD using Tapatalk 2
SamuriHL said:
Don't mention it. Happy to help. This update is a pain in my....uh anyway. I got MR2 back on my phone...mostly. Backing it up and will attempt to install the update again.
---------- Post added at 03:27 PM ---------- Previous post was at 02:53 PM ----------
Update is now in fact installed, rooted, and is backing up in the new version of TWRP (2.6.0.0) that Hashcode just gave us. (It's up on goo). Finally.
Click to expand...
Click to collapse
How were you able to install the update. I am too rooted and unlocked. Before I started to install the update I used voodoo rootkeeper to temp unroot. Then when I installed the new updated I thought it went thru; the installation process went smooth and my phone started back up and said installing new apps so I thought the install was actually gonna take. Then after the apps installed I received message saying that the update failed!. Please Help!!
Sent from my DROID RAZR HD using xda app-developers app
nigezee said:
How were you able to install the update. I am too rooted and unlocked. Before I started to install the update I used voodoo rootkeeper to temp unroot. Then when I installed the new updated I thought it went thru; the installation process went smooth and my phone started back up and said installing new apps so I thought the install was actually gonna take. Then after the apps installed I received message saying that the update failed!. Please Help!!
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
Um, Hmmmm. Well, I can tell you how I did it but it might not be a whole lot of help. I'm the author of the House of Bionic, so, I whipped up my own personal House of RAZR_HD. I restored my MR4 backup (I run CM 10.1 usually) and then had to downgrade that to MR2 using my utility. Basically it's an FXZ of MR2 that doesn't wipe the data partition. I booted into stock recovery, applied the update, got the awesome motorola.update.bl.backup() assertion error (which is fine from what I'm told...happens on unlocked phones), wiped the cache in recovery, and rebooted. From there once it did the android upgrade script, I rebooted into AP Fastboot, installed TWRP 2.6.0.0 (new version Hashcode just put up on goo), directly rebooted into TWRP (if you allow the phone to boot, it'll overwrite recovery...shut it off from AP Fastboot, and boot up into the menu and select recovery), installed the supersu zip in TWRP, ran a nandroid, and now I'm done. Upgrade taken, rooted, and backed up.
So I've been reading on this for a bit and before I accept or prolong the update when it gets to my phone I just am curious about something. What are the chances of the bootloader getting unlocked again with the fix? Currently, I have absolutely no intention of unlocking the phone or rooting as for once I am pretty happy with the performance, battery life, and interface. I don't see myself needing to do it in the near future, but there might be a time where I want to (i.e., when KLP is released).
I understand that the soak update only JUST got to phone in the last day or so, so I don't necessarily expect a definite answer, but are people at least going to work on it? If they're not, I might as well unlock it now before I get the update.
Hey Guys,
So I have my Razr M rooted with an unlocked bootloader and I'm running CM 10.1 stable. My headphone jack is messed up due to some hardware issues so VZW is sending me a warranty replacement. As of right now I still have the warning message that pops up about my bootloader being unlocked...if I flash a new bootloader image, this should take care of the message so that if Verizon turns on my phone that it doesn't look like I've unlocked it correct?
http://forum.xda-developers.com/showpost.php?p=44816389&postcount=29
From - http://forum.xda-developers.com/showthread.php?t=1901444&page=1
Well if you flash the boot logo that will remove the bootloader unlocked image yes... But your still going to be on cm not to mention the custom recovery.... Then you have the built in root checker and it saying that its unlocked in the fast boot menu.... Then your going to get a device that cannot be unlocked maybe even unrootable... I would have replaced it myself rather then risk the up to $500 fee for sending back that device (if they look into it) and having a device that is not unlockable or rootable.... Normally yes the just inspect it for physically damage and toss it in a bin for later repair but I just always have bad luck with this kind of thing so I would have spent 6$ on a head phone jack and put it in....
Sent from my XT907 using xda app-developers app
ezknives said:
Well if you flash the boot logo that will remove the bootloader unlocked image yes... But your still going to be on cm not to mention the custom recovery.... Then you have the built in root checker and it saying that its unlocked in the fast boot menu.... Then your going to get a device that cannot be unlocked maybe even unrootable... I would have replaced it myself rather then risk the up to $500 fee for sending back that device (if they look into it) and having a device that is not unlockable or rootable.... Normally yes the just inspect it for physically damage and toss it in a bin for later repair but I just always have bad luck with this kind of thing so I would have spent 6$ on a head phone jack and put it in....
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
I've never repaired anything like that and from what I can tell it involves soldering which I have never done and don't own a soldering iron or anything. I'm okay with not having an unlocked bootloader as I figured it was a possibility when I bought the phone in the first place. I just want root mainly to get rid of bloat apps and have AdAway. Those are really the only things I use root for and I don't use a lot of the features that are in some of the custom roms. Especially since I know Kit-Kat is coming to the Razr M now it's not that much of a deal.
Is there a way to flash the stock image and relock the bootloader?
Use Matts utility to flash stock... Then update... There is no way to lock the boot loader... And no soldering needed it's a pressure connect
Sent from my XT907 using xda app-developers app
So I got my new RAZR M today and it's still running 98.16.3.
I'm having trouble finding which update fixes the exploit to lock the bootloader. Is that 98.18.78? It's not imperative that I unlock the bootloader but I don't want to update my phone if it's going to fix the exploit in case I feel like unlocking it in the future.
EDIT: Looks like the build is from May 29th 2013 which would seem like it can be unlocked since the update that broke the exploit was in July correct?
gjriehl said:
So I got my new RAZR M today and it's still running 98.16.3.
I'm having trouble finding which update fixes the exploit to lock the bootloader. Is that 98.18.78? It's not imperative that I unlock the bootloader but I don't want to update my phone if it's going to fix the exploit in case I feel like unlocking it in the future.
EDIT: Looks like the build is from May 29th 2013 which would seem like it can be unlocked since the update that broke the exploit was in July correct?
Click to expand...
Click to collapse
No you can not unlock the boot loader on that device.. You can root it tho with motochopper 1.3...if you update it you won't be able to root it yet...
Sent from my XT907 using xda app-developers app
ezknives said:
No you can not unlock the boot loader on that device.. You can root it tho with motochopper 1.3...if you update it you won't be able to root it yet...
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Darn. Not a huge issue to me now but who knows down the line. I was more worried about getting stuck on Jelly Bean which is why I rooted/unlocked early but now that I know we're getting Kit Kat I don't care as much. Rooting is really the issue for me but the current OTA can still be rooted correct?
gjriehl said:
Darn. Not a huge issue to me now but who knows down the line. I was more worried about getting stuck on Jelly Bean which is why I rooted/unlocked early but now that I know we're getting Kit Kat I don't care as much. Rooting is really the issue for me but the current OTA can still be rooted correct?
Click to expand...
Click to collapse
The neweset OTA can't be rooted.
gjriehl said:
Darn. Not a huge issue to me now but who knows down the line. I was more worried about getting stuck on Jelly Bean which is why I rooted/unlocked early but now that I know we're getting Kit Kat I don't care as much. Rooting is really the issue for me but the current OTA can still be rooted correct?
Click to expand...
Click to collapse
The version your on now can be with motochopper 1.3 ... If you update it no you cannot...
Sent from my XT907 using xda app-developers app
ezknives said:
The version your on now can be with motochopper 1.3 ... If you update it no you cannot...
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Okay so I rooted my phone but now it's saying that SU Binary is not installed. Everywhere I go everyone's just like oh install this .zip from recovery which obviously isn't possible for me. How can I install the SU binary?