Related
Hey guys I've rooted a few phones for my friends since I rooted mines but that's when we were all running 2.2 froyo now I have a friend who wants me to root his phone too but he had the update 2.3 gb so can I still use unrevoked, the same method as froyo or do I have to wait for a different method for gb
Flip35 said:
Hey guys I've rooted a few phones for my friends since I rooted mines but that's when we were all running 2.2 froyo now I have a friend who wants me to root his phone too but he had the update 2.3 gb so can I still use unrevoked, the same method as froyo or do I have to wait for a different method for gb
Click to expand...
Click to collapse
As far as I know, there is no method available for rooting stock 2.3.
Got to wait. It will come.
Daaam, ok thanx I guess my buddy has to wait then, I told him to do it a few weeks back n he didn't want me to do it so now he'll have to wait...he should of done it when he had the chance
i thought i read a thread on here recently that said you could root by downgrading and then doing it. look around a lil n u will prob find it if u wanna try it out
{ParanoiA} said:
i thought i read a thread on here recently that said you could root by downgrading and then doing it. look around a lil n u will prob find it if u wanna try it out
Click to expand...
Click to collapse
You can only downgrade to 2.2 if you have s-off. The new 2.16 bootloader will not accept any known RUU, downgrade, or any other root method currently. I even tried to do the "old" GoldCard method, and of course, that didn't work either.
Here is the write up if interested on how to downgrade with s-off.........
http://htcevohacks.com/htc-evo-hacks/how-to-root-htc-evo-4g-gingerbread-2-3/
Check out the 4th comment, by Julian. Pretty much sums it up.........
"This procedure WILL NOT work if you have unrooted your Evo and updated via OTA from sprint!! New bootloader interface is included with the new RUU (2.3.3) which prevents recovery mode launch, reverting back to a prior ROM, or rooting"
you can root it if your bootloader says s-off, just flash recovery in a pc36img file and flash superuser for 2.3
skyline247 said:
You can only downgrade to 2.2 if you have s-off. The new 2.16 bootloader will not accept any known RUU, downgrade, or any other root method currently. I even tried to do the "old" GoldCard method, and of course, that didn't work either.
Here is the write up if interested on how to downgrade with s-off.........
http://htcevohacks.com/htc-evo-hacks/how-to-root-htc-evo-4g-gingerbread-2-3/
Check out the 4th comment, by Julian. Pretty much sums it up.........
"This procedure WILL NOT work if you have unrooted your Evo and updated via OTA from sprint!! New bootloader interface is included with the new RUU (2.3.3) which prevents recovery mode launch, reverting back to a prior ROM, or rooting"
Click to expand...
Click to collapse
thanks for this!
Well my friends phone has never been rooted so he wants to rooted so can I still go back to 2.2 using the methods y'all posted here
The new bootloader does not prevent recovery from launching. You can either turn off fastboot on settings-applications or instead of power off, choose reboot and start holding down vol-down when the screen goes black
Sent from my PC36100 using XDA App
vandon1 said:
The new bootloader does not prevent recovery from launching. You can either turn off fastboot on settings-applications or instead of power off, choose reboot and start holding down vol-down when the screen goes black
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
So ur saying I NEED TO GET TO BOOTLOADER to b able to do it right???
Flip35 said:
So ur saying I NEED TO GET TO BOOTLOADER to b able to do it right???
Click to expand...
Click to collapse
If the phone has never been rooted before, then you are going to be S-on. Since you have the new bootloader, AND you have S-on, there is nothing you can do to root the phone at this time. You cannot downgrade to 2.2, you cannot downgrade the bootloader. The only thing you'll be able to do is wait until someone figures out how to get S off on the new bootloader, or if someone figures out a way to downgrade the bootloader. The only way you can downgrade back to 2.2, is if the bootloader is S off. Also, if the bootloader was S off, downgrading to froyo to 'reroot' is a complete waste of time. All you need to do is flash a PC36IMG of a recovery image, and then use that recovery to flash a new rom. That's it. Anything more than that is a total waste of time, and a bunch of steps that don't need to be taken.
So, unfortunately, all you can do is wait until someone figures out a way around the new bootloader.
bootloader!!
kingdazy said:
As far as I know, there is no method available for rooting stock 2.3.
Got to wait. It will come.
Click to expand...
Click to collapse
Only option that I have found is to take it back to 2.2 and flash gingerbread rom, I personally only use z4root so ill have to wait
Desdoulas said:
Only option that I have found is to take it back to 2.2 and flash gingerbread rom, I personally only use z4root so ill have to wait
Click to expand...
Click to collapse
AGAIN......for those who just don't get it......
"This procedure WILL NOT work if you have unrooted your Evo and updated via OTA from sprint!! New bootloader interface is included with the new RUU (2.3.3) which prevents recovery mode launch, reverting back to a prior ROM, or rooting"
Sent from my PC36100 using XDA Premium App
Wow, don't you just hate repeating yourself?
HipKat said:
Wow, don't you just hate repeating yourself?
Click to expand...
Click to collapse
I think it might sink in eventually. Probably the day after a root method is found for Gingerbread.
k2buckley said:
If the phone has never been rooted before, then you are going to be S-on. Since you have the new bootloader, AND you have S-on, there is nothing you can do to root the phone at this time. You cannot downgrade to 2.2, you cannot downgrade the bootloader. The only thing you'll be able to do is wait until someone figures out how to get S off on the new bootloader, or if someone figures out a way to downgrade the bootloader. The only way you can downgrade back to 2.2, is if the bootloader is S off. Also, if the bootloader was S off, downgrading to froyo to 'reroot' is a complete waste of time. All you need to do is flash a PC36IMG of a recovery image, and then use that recovery to flash a new rom. That's it. Anything more than that is a total waste of time, and a bunch of steps that don't need to be taken.
So, unfortunately, all you can do is wait until someone figures out a way around the new bootloader.
Click to expand...
Click to collapse
Yea man the phone has never been rooted, is for my buddy n I told him to come to my house to get it rooted before the update he was procrastinating n now he's stuck but thanx a lot for the info everybody
skyline247 said:
AGAIN......for those who just don't get it......
"This procedure WILL NOT work if you have unrooted your Evo and updated via OTA from sprint!! New bootloader interface is included with the new RUU (2.3.3) which prevents recovery mode launch, reverting back to a prior ROM, or rooting"
No need to be rude kid, I watched a buddy install a ruu that worked perfectly, took about 20 min he was back to 2.2, there is a few youtube vids on it, I didn't do the code for it but I did watch it work to my disbelief, I said the same thing you did that there was no way
Sent from HTC_SUPERSONIC EVO
Click to expand...
Click to collapse
Then link us to this magical youtube video.
Kid? I'm 41 years old. I wasn't being rude. The same question was asked several times, so I was just restating the obvious. My goal on here is not to be rude, unlike many others, but to actually help. And I am sorry if you perceived as such.
Also, sorry to burst your bubble, but there is NO way to root if you have 2.3 AND the new 2.16 bootloader. Either you have S=off and run an RUU to get back to Froyo, or you do not have the new 2.16 bootloader.
That is all.
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
Hi All, I just got my Nexus one off ebay and it appears its not rooted as i do not see the padlock icon and i also cannot run the nexus torch.
What im looking to do is revert back to the stock software and than do all the OTA updates myself.
Can someone help me with this ? Im not looking to root though.
Im running the ATT version of the Nexus one.
Thanks all for your help.
To be root or not
if you do not see the padlock, then you are root!!
hi, yes i know and i do not see the pad lock so i have a unrooted phone. Im trying to find out how i can install the stock software this way i can do the OTA updates myself.
Thanks
If there's no padlock and you're sure it's not rooted... why do you think it's not already stock?
Well its running gingerbread and i wanted to go back to froyo and than OTA the updates myself
If its not rooted, root it! What version you on currently?
Sent from my GT-I9000 using Tapatalk
Im on the Nexus one ATT version, running the most recent gingerbread OS.
2.3.6???
Sent from my GT-I9000 using Tapatalk
If it is, try root using this... http://apachejava.blogspot.com/2011/06/root-nexus-one-gingerbread-234.html
My dad using my nexus one, so i dunno much... So, is your bootloader unlock, if it is, then go ahead with the link above... Then S-OFF using BlackRose...
Sent from my GT-I9000 using Tapatalk
Check this!!
Might help you.
http://answers.unity3d.com/questions/56512/downgrading-google-nexus-one-from-android-gingerbr.html
If you don't see the padlock it means the bootloader is still locked. If you don't have the SuperUser app then you are more than likely NOT rooted. Sounds like a stock phone if you ask me. Why do you want to roll back to Froyo then update? Sounds like you are already where you want to be. It sounds like a case of reaching around your ass to scratch your elbow. Heh. If you try to OTA update it and it says you are up to date, I would suggest leaving it alone or just root it! Good luck!
Sent from A VAN DOWN BY THE RIVER!
zinner526 said:
Well its running gingerbread and i wanted to go back to froyo and than OTA the updates myself
Click to expand...
Click to collapse
Why? Is there a problem with what is currently installed? If it's working fine, then I would expect downgrading to a previous version and applying the updates would just get you back to where you are now. I'm not criticizing, just trying to understand what you're looking to achieve
If you mean stock as in "original" that isn't Froyo either. The Nexus One originally came with Eclair (2.1). If you don't have root, I'm not sure if you can downgrade or how safe it would be. I've seen mixed results with downgrading. The only way to do a complete flash would be with an unlocked bootloader or root + custom recovery.
If you don't want to root or unlock the bootloader, why not just do a full wipe and use the version you have on it? You could also root it temporarily to restore to an unrooted Eclair or Froyo, then apply the updates.
Thanks Narbir, I'm going to try this. Does it matter I have AT&T ?
I hope So. I m usng Voda uk. Don't really brother me by that.
Well the phone reboots often for no reason so i thought if i started from the factory installed software and go forward it would help.
How hard is it to root to install enclar and than go forward ? Unless someone has another idea for the reboot issue ?
Install the latest stock ROM in PASSIMG format (complete ROM, all the partitions). No need to go back to Eclair or Froyo.
Prepare for the possibility of it not helping at all, and your phone HW being faulty. If you have ADB set up - you can run "adb bugreport" after the crash, and look for "ARM9 has crashed" line in the log dump that comes. If you'll see them - no amount of ROM switching will help.
Not to sound pedantic, but you seem a little confused (OP). Why don't you start by reading the FAQs regarding rooting and unlocking the bootloader, and understanding the ROM installation processes.
Couple of fundamentals to get you started:
1. The padlock (or absence of) is no indication of whether you are rooted or not. It merely indicates whether your 'bootloader' is unlocked or not, which is a completely separate concept from rooting.
2. Easiest method of seeing whether you are rooted is to see if you have the 'SuperUser' app in your app drawer.
If your objective is to install a stock/default ROM, search for a 'PASSIMG' for the latest available firmware for your device. Search these forums or Google it. The procedure is fairly straightforward and only involves putting the file on your SD card - and will restore your phone to a stock usable state.
If you're interested in custom ROMs, the fastest way to get started is to use SuperOneClick to root (Google, please). Then go to the market and download ROM Manager and just follow the instructions!
Has anyone been following the MotoX root method for Kit Kat seeing how it'll likely be the same for Ultra/Maxx? Wow! After seeing all the problems with RockMyMoto this method (assuming it'll work for us) is sure to be a doosie!
http://forum.xda-developers.com/showthread.php?t=2538896
SlapMyMoto 0.5c Beta (4.4 root, RW to system)
Sent from my XT1080 using xda app-developers app
What problems? Inability to follow directions?
Sent from my XT1080 using Tapatalk
Exactly!
Sent from my XT1080 using xda app-developers app
Lol one of the issues we won't face is downgrading I am so glad the moto x gets these updates before us. We get to see all the pitfalls.
Buy dev edition. Unlock bootloader. Install custom recovery. Install su. Profit?
Sent from my XT1060 using Tapatalk
arcanexvi said:
Buy dev edition. Unlock bootloader. Install custom recovery. Install su. Profit?
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Out of stock ATM
arcanexvi said:
Buy dev edition. Unlock bootloader. Install custom recovery. Install su. Profit?
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
I've been thinking of finding someone willing to trade a dev edition for a regular+cash. It didnt make sense to get it at the time when the Verizon store had them for $499 and the dev edition was $650-ish, but i'm starting to itch for some custom ROMs. All this waiting for official stuff is getting old.
bigv5150 said:
Lol one of the issues we won't face is downgrading I am so glad the moto x gets these updates before us. We get to see all the pitfalls.
Click to expand...
Click to collapse
And why wouldn't we have to down grade? And wipe all our date to update and root?
MonkeyMouth said:
And why wouldn't we have to down grade? And wipe all our date to update and root?
Click to expand...
Click to collapse
I'm glad you asked because were already on 4.2.2 why would we downgrade. The moto x got the update and jcase hadn't created the exploit yet which requires you to be on 4.2.2 so they had to down grade. Jcase just updated the exploit and is looking for droid testers his instructions say to downgrade unless your already on 4.2.2 My advie is to not install the update yet if you want root. You will just have to downgrade its more work. If you take the update pull it and put on your PC don't install it. I have the updater frozen so as soon as the update is posted I will attempt to root again on 4.2.2 and install the update hope it works smoothly.
bigv5150 said:
I'm glad you asked because were already on 4.2.2 why would we downgrade. The moto x got the update and jcase hadn't created the exploit yet which requires you to be on 4.2.2 so they had to down grade. Jcase just updated the exploit and is looking for droid testers his instructions say to downgrade unless your already on 4.2.2 My advie is to not install the update yet if you want root. You will just have to downgrade its more work. If you take the update pull it and put on your PC don't install it. I have the updater frozen so as soon as the update is posted I will attempt to root again on 4.2.2 and install the update hope it works smoothly.
Click to expand...
Click to collapse
That clears things up immensly! Thanks for taking the time to explain the process. I am currently on 4.2.2 and rooted. I'm just waiting for the update to drop so I can make a copy for people who need it. Then I'll try to root the new update.
MonkeyMouth said:
That clears things up immensly! Thanks for taking the time to explain the process. I am currently on 4.2.2 and rooted. I'm just waiting for the update to drop so I can make a copy for people who need it. Then I'll try to root the new update.
Click to expand...
Click to collapse
Here check this out http://forum.xda-developers.com/showthread.php?p=48648074#post48648074 im waiting for jcase to get back to me if we need to unroot. I would assume so a fxz of 4.2.2 would be the best platform to try this on. It seems fairly simple to be honest his instructions are very straight foward. I feel bad for the guys that took the update they have to downgrade.
Just FYI, adb shell getprop ro.boot.write_protect is still 0 after unrooting, stock 4.2.2, then taking the KitKat OTA. Might this make it easier to root 4.4 standalone? Or should I just go back down to 4.2.2 and follow slap?
dtreth said:
Just FYI, adb shell getprop ro.boot.write_protect is still 0 after unrooting, stock 4.2.2, then taking the KitKat OTA. Might this make it easier to root 4.4 standalone? Or should I just go back down to 4.2.2 and follow slap?
Click to expand...
Click to collapse
Would you be willing to:
1. Verify if downgrading back to 4.2.2 (12.15.15 firmware) is possible with the DROID line?
2. Verify if SlapMyMoto works with the DROID line?
dtreth said:
Just FYI, adb shell getprop ro.boot.write_protect is still 0 after unrooting, stock 4.2.2, then taking the KitKat OTA. Might this make it easier to root 4.4 standalone? Or should I just go back down to 4.2.2 and follow slap?
Click to expand...
Click to collapse
You can't root on 4.4 only 4.2.2 doesn't matter that write protection is off. i wish it was that simple.
tehcodeman said:
Would you be willing to:
1. Verify if downgrading back to 4.2.2 (12.15.15 firmware) is possible with the DROID line?
2. Verify if SlapMyMoto works with the DROID line?
Click to expand...
Click to collapse
I will when I get home. I have the files there, but I didn't grab my update.zip and I'm not sure if I can get it back after FXZing, so I may wait until I find it.
bigv5150 said:
You can't root on 4.4 only 4.2.2 doesn't matter that write protection is off. i wish it was that simple.
Click to expand...
Click to collapse
What I meant by my comment was "hey guys, MotoWpNoMo survived OTA! Would this make it easier to develop a 4.4 root method that does not require downgrading?"
dtreth said:
I will when I get home. I have the files there, but I didn't grab my update.zip and I'm not sure if I can get it back after FXZing, so I may wait until I find it.
What I meant by my comment was "hey guys, MotoWpNoMo survived OTA! Would this make it easier to develop a 4.4 root method that does not require downgrading?"
Click to expand...
Click to collapse
I don't think it matters but that is a ? For jcase.
So in my excitement to flash 4.4, I forgot to take into account losing the root. So I tried to downgrade as per JCase's suggestion, but there's a big problem if you already successfully installed the OTA. It is an updated security signature and software. Because of this, RSD Lite and fastboot return with the error of "Flash failed. Downgraded security version". Does anyone have a workaround or an updated FXZ that will flash over 4.4 to revert back to 4.2.2 so I can try the JCase's backdoor method?
ExceterM said:
So in my excitement to flash 4.4, I forgot to take into account losing the root. So I tried to downgrade as per JCase's suggestion, but there's a big problem if you already successfully installed the OTA. It is an updated security signature and software. Because of this, RSD Lite and fastboot return with the error of "Flash failed. Downgraded security version". Does anyone have a workaround or an updated FXZ that will flash over 4.4 to revert back to 4.2.2 so I can try the JCase's backdoor method?
Click to expand...
Click to collapse
Mad at you. How do you have the 4.4 update already.
After unlocking the booter, and following the instructions for SlapMyMoto, I was able to install the update for my Mini and retain root. You can do it!
zefyx said:
After unlocking the booter, and following the instructions for SlapMyMoto, I was able to install the update for my Mini and retain root. You can do it!
Click to expand...
Click to collapse
It doesn't unlock the bootloader. Just takes off the write protection so you don't need to reboot your phone into recovery to turn it off. Which allows you to use the actual stock recovery as well.
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.