Related
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.
Hello, I was wondering for those who kept root going from 4.1.2 to kitkat 4.4, how did you do it? My phone is currently locked but rooted and I just downloaded the OTA kit kat update but haven't installed it yet. Any ideas would be greatly appreciated!
No current method so don't upgrade if root is essential. Only unlocked bootloaders can get root back.
Sent from my Nexus 5 using Tapatalk
We haven't seen anybody maintain root on a locked device across the OTA yet.
RikRong said:
We haven't seen anybody maintain root on a locked device across the OTA yet.
Click to expand...
Click to collapse
what about on a device that is unlocked?
voodoo?
On an unlocked device you can just flash SuperSU in recovery...
And Voodoo won't work with a KitKat OTA.
how do you flash if root was lost when updated..im unlocked and had twrp but heard that is no longer working..and what is stranger is that developers option in settings s not there
Sent from my KFTHWI using Tapatalk
davekaz said:
how do you flash if root was lost when updated..im unlocked and had twrp but heard that is no longer working..and what is stranger is that developers option in settings s not there
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
First off, in regards to TWRP, there is a newer version of CWM recovery that works with KK. Use that.
Second, the developer options have been hidden, but you have to pay me to get the info.
JUST KIDDING!
Here is what you do:
Go to settings.
Click on "About Phone"
Scroll down and then start mashing on "Build Number". It will inform you that you have so many presses before going to developer mode.
After that, it will give you a toast saying developer mode has been activated. You're done!
If someone could kindly put together a walk thru on
How to go from stock, rooted, and unlocked to kit Kat w/root
That would be greatly appreciated.
Thanks!
I am in the same boat, rooted on stock ROM. I don't want to lose root, but my phone keep popping up the update installer request. My phone has kept me so happy for so long that I have not kept up with the forums. I just haven't had any problems, and I'd like to keep it that way. So, is there no root for 4.2.2 yet? Or there just isn't a way to preserve it across the OTA? Should I go back to stock unrooted, update and re-root? I've been reading around the forums and I am just not seeing a whole lot of info about this yet.
gadsden said:
I am in the same boat, rooted on stock ROM. I don't want to lose root, but my phone keep popping up the update installer request. My phone has kept me so happy for so long that I have not kept up with the forums. I just haven't had any problems, and I'd like to keep it that way. So, is there no root for 4.2.2 yet? Or there just isn't a way to preserve it across the OTA? Should I go back to stock unrooted, update and re-root? I've been reading around the forums and I am just not seeing a whole lot of info about this yet.
Click to expand...
Click to collapse
this has been discussed many times.
if you have a LOCKED phone, there is NO way to have or preserve root going to KK
if you have a UNLOCKED phone, update to KK, flash the KK cwm, flash su zip in cwm, profit!
those are the only 2 options PERIOD.
bweN diorD said:
this has been discussed many times.
if you have a LOCKED phone, there is NO way to have or preserve root going to KK
if you have a UNLOCKED phone, update to KK, flash the KK cwm, flash su zip in cwm, profit!
those are the only 2 options PERIOD.
Click to expand...
Click to collapse
Ok, well, I am not unlocked. So is there a way to stop the OTA?
gadsden said:
Ok, well, I am not unlocked. So is there a way to stop the OTA?
Click to expand...
Click to collapse
you can freeze the updater. i dont recall the exact file name(s).
someone else can jump in, or you could google it.
bweN diorD said:
you can freeze the updater. i dont recall the exact file name(s).
someone else can jump in, or you could google it.
Click to expand...
Click to collapse
You are correct, just freeze the updater.apk. Well, it's worked for me anyway.
RikRong said:
You are correct, just freeze the updater.apk. Well, it's worked for me anyway.
Click to expand...
Click to collapse
Some people say it's better to rename System > etc>security > otacerts.zip. Equal amount of people say to freeze updater. I'll follow you and freeze updater for now.
I'm itching to update to KK, and I can almost part with a rooted phone since I am running stock ROM anyway. But life without Titanium Backup just doesn't seem like a life at all.
Thanks again for the tips.
Speaking of freezing the update app, I have been doing that since before the last update so I'm currently running 4.1.2 9.16.6.XT926 does anyone know if it will cause me any trouble skipping an OTA?
Thanks.
sheep348 said:
Speaking of freezing the update app, I have been doing that since before the last update so I'm currently running 4.1.2 9.16.6.XT926 does anyone know if it will cause me any trouble skipping an OTA?
Thanks.
Click to expand...
Click to collapse
you should unlock the bootloader first if you havent already. after you update you will no longer be able to ever.
as for the update, if you flash it with rsd there shouldnt be any issue that im aware of. if you unfreeze the updater and take the actual ota(s), it will not skip any, it will pull the next in line each time until you get to the most current.
however, you will still need to use rsd before taking or sideloading the KK ota or root will cause it to fail.
bweN diorD said:
you should unlock the bootloader first if you havent already. after you update you will no longer be able to ever.
as for the update, if you flash it with rsd there shouldnt be any issue that im aware of. if you unfreeze the updater and take the actual ota(s), it will not skip any, it will pull the next in line each time until you get to the most current.
however, you will still need to use rsd before taking or sideloading the KK ota or root will cause it to fail.
Click to expand...
Click to collapse
Thanks for the help but I don't have a lot of knowledge about rooting. If I don't care about keeping root can I just take the OTAs or are you saying they will they fail if I don't first unlock the boot loader?
"after you update you will no longer be able to ever" What will I not be able to update again? The bootloader?
Thanks.
sheep348 said:
Thanks for the help but I don't have a lot of knowledge about rooting. If I don't care about keeping root can I just take the OTAs or are you saying they will they fail if I don't first unlock the boot loader?
Thanks.
Click to expand...
Click to collapse
He's saying you could probably find someone who would be willing to pay you handsomely to trade phones.
Once you update your phone, the bootloader can't be unlocked....as far as we know, ever again. If you don't care, which it sounds like you don't, go ahead and update your phone.
sheep348 said:
Thanks for the help but I don't have a lot of knowledge about rooting. If I don't care about keeping root can I just take the OTAs or are you saying they will they fail if I don't first unlock the boot loader?
Thanks.
Click to expand...
Click to collapse
most people who dont unlock the bootloader when they had the chance regret not doing it. its not a problem if you dont want to, i was just giving you a heads up more or less.
as for the updates,(this has nothing to do with the bootloader) im pretty sure the first 2 will install fine but im positive the 3rd, KK, will fail because you had root before.
so if you want to go to KK, you really have no other option but to use rsd first to return your phone to stock.
gadsden said:
He's saying you could probably find someone who would be willing to pay you handsomely to trade phones.
Once you update your phone, the bootloader can't be unlocked....as far as we know, ever again. If you don't care, which it sounds like you don't, go ahead and update your phone.
Click to expand...
Click to collapse
Thanks bweN diorD and gadsden,
I appreciate the help. I only use my root access for killing music apps and I have some bloatware frozen. So personally I think I'll go ahead and update to KK since the benefits should outweigh the loss of root access for me. Should I do a factory reset first or should I be good to go taking the OTA?
Thanks again I'm always hesitant to do things to my phone because I don't have the knowledge to fix it or the money to replace it.
---------- Post added at 06:18 PM ---------- Previous post was at 06:15 PM ----------
bweN diorD said:
most people who dont unlock the bootloader when they had the chance regret not doing it. its not a problem if you dont want to, i was just giving you a heads up more or less.
as for the updates,(this has nothing to do with the bootloader) im pretty sure the first 2 will install fine but im positive the 3rd, KK, will fail because you had root before.
so if you want to go to KK, you really have no other option but to use rsd first to return your phone to stock.
Click to expand...
Click to collapse
Again thanks, I guess I'll have to look into finding out how to use rsd and go back to stock.
I take no credit for any of the work done in the links below, and am not the first to discover or prove any of this works. All I know is it works for now, and felt the best way was to start a brand new thread with both links contained to get the message to as many people as possible. And another soak test is coming from Motorola, so GET ROOT AND UNLOCKED WHILE YOU STILL CAN!!
Towelroot verified WORKING to root the 4.4.2 HD and HD MAXX:
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=135540530
Unlocking possible again as well, after using Towelroot:
http://forum.xda-developers.com/showthread.php?t=2783912
LifeAsADroid said:
I take no credit for any of the work done in the links below, and am not the first to discover or prove any of this works. All I know is it works for now, and felt the best way was to start a brand new thread with both links contained to get the message to as many people as possible. And another soak test is coming from Motorola, so GET ROOT AND UNLOCKED WHILE YOU STILL CAN!!
Towelroot verified WORKING to root the 4.4.2 HD and HD MAXX:
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=135540530
Unlocking possible again as well, after using Towelroot:
http://forum.xda-developers.com/showthread.php?t=2783912
Click to expand...
Click to collapse
Just read this on Android Authority and was wondering if it would work. Great to hear this. Again, users got REAL lucky on this one considering this wasn't created specifically for this phone, but for the general population of unpatched 4.4.2 kernels.
Word of warning, if you used my UNIVERSAL script to flash 183 onto your phone, you must either manually flash the TZ partition or use my KEEP DATA script before rooting an unlocking else it will fail.
BTW, I just received an email notification from Motorola stating there is another soak test coming, so definitely root and unlocked your phones NOW and I can't stress that more than enough or else, you can kiss root and unlocking good-bye, especially if this is an 4.4.3 update. Once 4.4.3 comes out, /system is no longer writeable and things will get really ugly.
So, root and then unlock your phones on the 4.4.2 KK OTA before the next one comes out or you will be sorry.
BTW, if you're so worried about voiding your warranty, once you root, you've voided your warranty and there is a root checker built into the device, so they can tell if you've rooted or not, so if you're going to root, you might as well unlock the bootloader.
The warranty concern is nonsense. PLENTY of people sent back unlocked phones and no one ever complained. Yes, the soak emails were known about last night which is why we've been trying like hell to get this message out to everyone to get it done NOW. It's an almost certainty that the TZ partition will be secured again. And root will almost assuredly be patched since it was patched in the linux kernel on june 3rd. Unlocking is the surefire way of keeping root forever, and getting to play with new roms which is awesome. Plus, don't like kitkat? Downgrade with my UNIVERSAL script. (Yes, the one that's causing some problems for people unlocking. LOL). We can not stress this enough...NOW is the time to unlock before it's too late. I can't even begin to describe how lucky you all are.
One question. After I unlock the bootloader and they send out 4.4.3, will it be possible to take the update OTA?
Sent from my DROID RAZR HD using Tapatalk
newmanx4 said:
One question. After I unlock the bootloader and they send out 4.4.3, will it be possible to take the update OTA?
Sent from my DROID RAZR HD using Tapatalk
Click to expand...
Click to collapse
yes but there may be some jumping through hoops like unrooting or sbfing but you will not lose any data and you can just reroot by flashing a superuser.zip . unless moto goes from nice to evil and this ota re locks boot loaders
That's what I'm wondering. Will they relock the bootloader or leave it be since these phones are nearly two years old.
Sent from my DROID RAZR HD using Tapatalk
billycar11 said:
yes but there may be some jumping through hoops like unrooting or sbfing but you will not lose any data and you can just reroot by flashing a superuser.zip . unless moto goes from nice to evil and this ota re locks boot loaders
Click to expand...
Click to collapse
Stop that. They're not going to relock the bootloader. However, screw OTA's. Wait for the FXZ to leak and use my RSD Script Generator to create a KEEP DATA or UNIVERSAL script and flash that with RSD. Flash custom recovery (CWM or TWRP) and flash supersu zip and be done with the whole thing. Forget unrooting and trying to make the OTA work. Too much effort. LMAO
---------- Post added at 11:13 AM ---------- Previous post was at 11:11 AM ----------
See what you've done? These poor people are now paranoid about bootloader relocking. LOL! They won't relock it. It's physically blowing an eFuse to do the unlock. Relocking would be extremely problematic and cause more problems than they'd solve. And given the likelihood that this was "accidentally" done (cough cough) in the first place, there's an almost 0 chance of relocking.
newmanx4 said:
That's what I'm wondering. Will they relock the bootloader or leave it be since these phones are nearly two years old.
Sent from my DROID RAZR HD using Tapatalk
Click to expand...
Click to collapse
i dont think they will and even if they did we could probably get around it with @SamuriHL universal script we would just have to wait until the sbf/fxz files come out
Which I'm recommending you do anyway.
I never unlocked the bootloader the first go round but I'm sure going to this time.
Sent from my DROID RAZR HD using Tapatalk
Good to hear. I want everyone with these phones to do so. This is a great opportunity. No one should be sitting on the fence this time.
Indeed great news. Too bad my XT926 is not by me right now(being used by my father) and I can get my hand on it till september.
My XT926 is bootloader locked and has JB 4.2. build is 9.18.94 I guess. I have my phone rooted and since then using safestrape 3.12 and has stock rom and RageHD ROM on it. I can remember last time trying to install OTA the update process failed even I have used voodoo root keeper to hide the root.
So now my questions:
1. Is the right procedure for me: Remove Safestrape->Install OTA KK->using methods described here for KK for unlocking?
2. What was the reason the OTA update failed? Safestrape?
3. Can I uninstall Safestrape through it's "uninstall" function?
4. After uninstall if I choose OTA update, will it be the current KK which contains this old exploit for bootloader unlocking?
5. If I wait till september to do it myself, if there is another OTA out which patches this exploit again, can I fake a Moto web site and pointing it to the current KK (183), lets say change the host file on XT926. Is this even possible?
xknobi said:
Indeed great news. Too bad my XT926 is not by me right now(being used by my father) and I can get my hand on it till september.
My XT926 is bootloader locked and has JB 4.2. build is 9.18.94 I guess. I have my phone rooted and since then using safestrape 3.12 and has stock rom and RageHD ROM on it. I can remember last time trying to install OTA the update process failed even I have used voodoo root keeper to hide the root.
So now my questions:
1. Is the right procedure for me: Remove Safestrape->Install OTA KK->using methods described here for KK for unlocking?
2. What was the reason the OTA update failed? Safestrape?
3. Can I uninstall Safestrape through it's "uninstall" function?
4. After uninstall if I choose OTA update, will it be the current KK which contains this old exploit for bootloader unlocking?
5. If I wait till september to do it myself, if there is another OTA out which patches this exploit again, can I fake a Moto web site and pointing it to the current KK (183), lets say change the host file on XT926. Is this even possible?
Click to expand...
Click to collapse
1.yes
2.yes
3.yes but ota will not install you will need to use what me and @SamuriHL posted to go to the ota
4.yes
5.no you you use the hack posted
billycar11 said:
3.yes but ota will not install you will need to use what me and @SamuriHL posted to go to the ota
Click to expand...
Click to collapse
Ok, maybe you mean the following method?
http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
xknobi said:
Ok, maybe you mean the following method?
http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
Click to expand...
Click to collapse
yes that is what i posted
Rooted and unlocked using the apk's. Doesn't get any easier than that. Now what is the preferred custom recovery for most of you?
Sent from my DROID RAZR HD using Tapatalk
billycar11 said:
yes that is what i posted
Click to expand...
Click to collapse
Thanks billycar11!
From the description I see that the script will flash a 760MB file, the KK 4.4.2 (KDA20.62-10.1). So I won't be afaid that when I wait for some months even if Moto patched their OTA for this bootloader exploit, the unpatched bootloader is still in (KDA20.62-10.1), which I assume is build 183, so I will still be able to use this exploit, as long as my phone is in JB (4.2) state?
newmanx4 said:
Rooted and unlocked using the apk's. Doesn't get any easier than that. Now what is the preferred custom recovery for most of you?
Sent from my DROID RAZR HD using Tapatalk
Click to expand...
Click to collapse
twrp by @dhacker29 http://forum.xda-developers.com/showthread.php?t=2776515
---------- Post added at 02:14 PM ---------- Previous post was at 02:11 PM ----------
xknobi said:
Thanks billycar11!
From the description I see that the script will flash a 760MB file, the KK 4.4.2 (KDA20.62-10.1). So I won't be afaid that when I wait for some months even if Moto patched their OTA for this bootloader exploit, the unpatched bootloader is still in (KDA20.62-10.1), which I assume is build 183, so I will still be able to use this exploit, as long as my phone is in JB (4.2) state?
Click to expand...
Click to collapse
there is no jb 4.2 i think you mean 4.1..2 . but you will not be able to use it on jelly bean you need to update to kitkat root then unlock.
Just got another email from Motorola to sign up for a preview of a new software release. Probably fixes issues that were discovered after the KK upgrade.
CAUTION FOR THOSE WITH LOCKED DEVICES: Considering you just got a new root method, I would steer clear from this if you want to keep root. I have a feeling Towelroot will not work after this since it only works for kernels dated before June 3, 2014. Also, this might break the current tethering hack as well for 4.4.2.
It would be nice if this were a 4.4.3 update, but I don't know at this time. Since I'm unlocked, I'm going to go ahead and sign up for it and see what happens.
Just wanted to get the word out to anyone with locked bootloaders to probably stay away from this unless you don't care about root and the tethering hack.
The bad news about this means the "can I unroot my KitKat phone" won't go away once the OTA comes out.
Pretty obvious that locked users should be careful with the new OTA, same as before, don't rush ahead of yourself and install every OTA that Moto pushes out. Also today is a great day, we've got a root and apparently locked users can unlock their bootloader while being on 183.46.10 update. So I'd rather recommend people to take root and unlock and do whatever the hell they want after that, considering rooting and unlocking is as simple as just installing and running 2 apks.
Flayzor said:
Pretty obvious that locked users should be careful with the new OTA, same as before, don't rush ahead of yourself and install every OTA that Moto pushes out. Also today is a great day, we've got a root and apparently locked users can unlock their bootloader while being on 183.46.10 update. So I'd rather recommend people to take root and unlock and do whatever the hell they want after that, considering rooting and unlocking is as simple as just installing and running 2 apks.
Click to expand...
Click to collapse
What? Locked users can unlock the bootloader? How? I didn't see that. Motopocolypse, from what I understand, doesn't work with anything after 9.16 OTA. I got lucky and was able to unlock mine about a year ago (didn't have 9.18 OTA applied from the factory). Still, if people can unlock their bootloaders with the KK, that's great, but again, I have not heard nor seen anything that states this. I only knew about Towelroot and that's it.
As for it being obvious, didn't matter after this past KK upgrade. People did it anyways and we got an unflux of "how do I root this sucker?" over and over again.
iBolski said:
What? Locked users can unlock the bootloader? How? I didn't see that. Motopocolypse, from what I understand, doesn't work with anything after 9.16 OTA. I got lucky and was able to unlock mine about a year ago (didn't have 9.18 OTA applied from the factory). Still, if people can unlock their bootloaders with the KK, that's great, but again, I have not heard nor seen anything that states this. I only knew about Towelroot and that's it.
As for it being obvious, didn't matter after this past KK upgrade. People did it anyways and we got an unflux of "how do I root this sucker?" over and over again.
Click to expand...
Click to collapse
I guess I'll be late and you've found that after upgrading to KK and rooting it, you can unlock bootloader with Motopocalypse ^^. Also idk why wouldn't anyone want to unlock BL, considering the phone is on its end of life cycle and won't get anymore android updates (e.g 4.5+) it seems rather wise to unlock and have all the goodies now and in the future.
iBolski said:
Also, this might break the current tethering hack as well for 4.4.2.
Click to expand...
Click to collapse
I see you guys have been using the tether mod I posted for the ultra. no problem, I developed a new mod for 4.4.2 and 4.4.3 so if it does break tether and can make one for the HD.
I used to have an HD so I'll help you guys out.
Droid Maxx "Developer Edition"
Topsnake said:
I see you guys have been using the tether mod I posted for the ultra. no problem, I developed a new mod for 4.4.2 and 4.4.3 so if it does break tether and can make one for the HD.
I used to have an HD so I'll help you guys out.
Droid Maxx "Developer Edition"
Click to expand...
Click to collapse
Awesome. Thanks a bunch for that. I'll definitely want to try it out once I the new OTA comes in. Since I have an unlocked bootloader, I'm not too frightened to do the OTAs, but to know that we can get another tether mod if it does indeed break with the next OTA, that's a relief.
tether seems broken..
Topsnake said:
I see you guys have been using the tether mod I posted for the ultra. no problem, I developed a new mod for 4.4.2 and 4.4.3 so if it does break tether and can make one for the HD.
Droid Maxx "Developer Edition"
Click to expand...
Click to collapse
I used to have an HD so I'll help you guys out.
Just to confirm, from what I can tell yes the tether hack seems to have broken, I am rooted, unlocked and all that good stuff so I can always flash back, but as a warning I tried to get it working again with no success.
Now I am not ruling out the possibility that I am a dope and screwed up the procedure somewhere, in which case I pray someone can confirm it works and maybe teach a fool to fish .
Thecat1080 said:
I used to have an HD so I'll help you guys out.
Just to confirm, from what I can tell yes the tether hack seems to have broken, I am rooted, unlocked and all that good stuff so I can always flash back, but as a warning I tried to get it working again with no success.
Now I am not ruling out the possibility that I am a dope and screwed up the procedure somewhere, in which case I pray someone can confirm it works and maybe teach a fool to fish .
Click to expand...
Click to collapse
Uh. the tethering hack still works. Go here -> http://forum.xda-developers.com/dro...d-native-tether-exploit-build-183-46-t2872547