I'm very excited to hear about the upcoming OTA, and that we can now unlock the bootloader, but my question is, should I unlocked it now or wait for the official release, cause if I brick my atrix and can't get it exchanged, then ima be stuck with my old aria ......also is there a sbf that could relock it just incase I needed to make an exchange?
Sent from my MB860 using XDA App
http://forum.xda-developers.com/showthread.php?t=1139101
Related
DO NOT ACCEPT THE OTA AT THIS TIME WHETHER YOU ARE ROOTED OR NOT IF YOU HAVE ANY PLANS TO ROOT IN THE FUTURE. THE NEW BOOTLOADER IN THE OTA IS LOCKED. Is this a joke HTC?
Damn. Good looking out. Even though I don't plan on it, its good to know.
Already done but I don't root so bleh
Sent from my PC36100 using XDA App
treckin said:
Already done but I don't root so bleh
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
But its always nice to have the option.
The main way I see of getting around this in the future is by finding a way to downgrade hboot.
FACK!!
Too late for me..... I trusted HTC and I got stabbed in the back
Sent from my PC36100 using XDA Premium App
I thought they weren't locking the bootloaders anymore?
Sent from my PC36100 using XDA Premium App
RileyGrant said:
DO NOT ACCEPT THE OTA AT THIS TIME WHETHER YOU ARE ROOTED OR NOT IF YOU HAVE ANY PLANS TO ROOT IN THE FUTURE. THE NEW BOOTLOADER IN THE OTA IS LOCKED. Is this a joke HTC?
Click to expand...
Click to collapse
When you say locked, do you mean locked in the same way that every other bootloader with the Evo has been? Locked in a way that can be cracked and rooted still?
OR
Do you mean they cryptographically signed it? (encrypted?)
If it's encrypted, then yes, I agree with you. WTF HTC??
I have seen people say they got into the bootloader to reinstall Amon Ra.....
HTC may have verbally negated their future bootloader policy, but this plus the Sense SDK, their Sense services and stores are just proof that they are out to create a psuedo propriety OS, Android ecosystem be damned.
Sent from my Nexus S 4G using Tapatalk
k2buckley said:
When you say locked, do you mean locked in the same way that every other bootloader with the Evo has been? Locked in a way that can be cracked and rooted still?
OR
Do you mean they cryptographically signed it? (encrypted?)
If it's encrypted, then yes, I agree with you. WTF HTC??
Click to expand...
Click to collapse
From the looks of it, it looks to be a little more serious, post from Toast's twitter:
toastcfh:
@htc you promised us no more locked bootloaders and the EVO 4G OTA has a LOCKED bootloader? WHY?!
However the one thing we have going for us is that, unlike most instances involving devices with locked bootloaders, we have a number of older hackable bootloaders to fall back on. If hboot can be downgraded then that serves as a possible means of rooting once again.
HipKat said:
I have seen people say they got into the bootloader to reinstall Amon Ra.....
Click to expand...
Click to collapse
Only because they took the OTA after they had already used Unrevoked forever. Therefore, S-off remained after the OTA (lucky for those guys who did that..) Since after the OTA they still had S-off (thanks to unrevoked forever), they were able to just reflash Amon Ra. They don't know how lucky there are.
screenshots or it didn't happen.
AbsolutZeroGI said:
screenshots or it didn't happen.
Click to expand...
Click to collapse
lulz, there'sa few unlucky souls who reverted to stock then updated, maybe they'd give us a looksie?
RileyGrant said:
From the looks of it, it looks to be a little more serious, post from Toast's twitter:
toastcfh:
@htc you promised us no more locked bootloaders and the EVO 4G OTA has a LOCKED bootloader? WHY?!
However the one thing we have going for us is that, unlike most instances involving devices with locked bootloaders, we have a number of older hackable bootloaders to fall back on. If hboot can be downgraded then that serves as a possible means of rooting once again.
Click to expand...
Click to collapse
Damn, that really sucks. This kind of makes me worried a little bit. This is right after they promised us no locked bootloaders, and here we are with a locked bootloader on the OTA. There really was no reason for them to even 'update' the bootloader, other than to lock it.
HTC better stick to what they said, especially with the Evo 3d
That's why never trust ota like that just be patient plus I believe virus already has this Rom rooted
Customized EVO
k2buckley said:
Only because they took the OTA after they had already used Unrevoked forever. Therefore, S-off remained after the OTA (lucky for those guys who did that..) Since after the OTA they still had S-off (thanks to unrevoked forever), they were able to just reflash Amon Ra. They don't know how lucky there are.
Click to expand...
Click to collapse
Thats pretty smart. I can flash unrevoked forever in recovery right? And will unrevoked forever s-on undo it? Sorry, newb questions.
I think Samsung just won a customer. I wanted to wait for the Sensation but I'm going for the SGS II. Thanks for the info.
f.
Sent from the Dark Side using Sith knowledge of The Force
The htc announcement was about a week ago. This OTA was most likely already in sprints hands when that was said. So, just give it some time i guess.
knowledge561 said:
Thats pretty smart. I can flash unrevoked forever in recovery right? And will unrevoked forever s-on undo it? Sorry, newb questions.
Click to expand...
Click to collapse
Don't do that man. It's not worth even risking it. What if unrevoked forever didn't do it's job, and you ended up with S on, on an unrootable bootloader?
Just go to xHausx's thread and download and flash the rooted version of the rom. Screw taking it OTA, that's for people who don't root their phones (the general public and masses). For us who are rooted, we just download from XDA and flash. I cannot for the life of me understand people's obsession with wanting to take the 'official' OTA and risk breaking root, when you can just safely flash the same exact update, except it's been rooted. I don't get it.
I just got my replacement atrix today, im trying to figure out whether I should update it to the 2.3.4 OTA or not. My old atrix I had unlocked on 1.83 and was running cherryblur. Is it easier to unlock on 1.83 or the new OTA or are both easy now?
Sent from my MB860 using XDA App
Basically, if want to be adventurous with the ROMS and crazy modifications, then root and unlock bootloader, or if you are fine with the official OTA update. Then just stick with those. I am sticking with OTA since I don't want to brick since I am using my ATRIX for college and job and need a reliable phone. I might root it though if I can figure it out.
My modding fun is with my Sony Ericsson Xperia X10. That's my xda fun.
Sent from my Atrix 4G with XDA Premium App
I was glad OTA keeps ALL of your settings and applications. I did it, only because Motorola says they will unlock the bootloader. When that happens I figure I'll finally root and go wild with ROMs, because my 1 year warranty may be close to expiring anyway.
For me, with no other changes but the OTA upgrade, my battery life BLOWS me away. I used to get down to 10-15% after 9 hours, casual internet and lots of mp3 playback.
Now I only get down to 45% doing the same exact stuff! Astonishing.
If you are waiting for unofficial unlock support from Motorola, do the OTA. you will be happy in the interim
Im already planning to unlock it and put roms on it, just wondering if its easy to unlock on 2.3.4 or if I should just keep it at 1.83. Cause froyo sucks and I wont have time to do anything on it til sunday.
Sent from my MB860 using XDA App
sunshine1982 said:
Im already planning to unlock it and put roms on it, just wondering if its easy to unlock on 2.3.4 or if I should just keep it at 1.83. Cause froyo sucks and I wont have time to do anything on it til sunday.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
According to this thread here:
http://www.atrixforums.com/forum/mo...official-2-3-4-build-4-5-91-can-i-unlock.html
you can still unlock but there is a small risk of bricking -- unlocking before flashing to 2.3.4 OTA is advised (or do what I did and click the first link on this thread http://forum.xda-developers.com/showthread.php?t=1136261 , run the SBF via RSD Lite 5.31 & motorola's drivers (you can find them on their site in the Atrix section)), send the unlock command via fastboot, and follow the rooting instructions -- all of which are again on the same first link on that page.
EDIT:
This allows you to flash an unlocked bootloader, GB 2.3.4 update, as well as root, all via one file. Remember that there are instructions to follow, it doesn't unlock or root for you, but provides all three as part of a flashable file.
Others feel free to chime in -- I'm only explaining what I did and worked for me. I understand that the general concensus is that SBF file carry a higher risk than other methods of flashing.
I have an unlocked and rooted Atrix 4G running on 4.1.83, and I know once I do the 4.5 update I will loose the ability of RSD Lite to flash back to previous sbf's. I have put off this update due to the fact of possibly limiting my options with the phone. I havn't had enough time to really look into different roms or even start studying up on developing something (which I want to in the future; just busy with job interviews and a big move coming up). But to get to the point, is it worth it for me just to do the update or not? I am curious of everyones thoughts on this....
Thanks
Personally, I think it's not worth updating since we will soon have CM7. It's all up to you though. I enjoy my freedom when customizing my phone. Do you?
Sent from my MB860 using XDA App
you can use fruitcakes to flash 1.83 if froyo is your thing.
Personally even the buggy CM7 build is miles ahead of the assorted 2.3.4 Roms if you don't need a camera or wifi tether. I will never run 2.2 again
Sent from my MB860 using XDA Premium App
moto's own bootloader unlock
Isn't moto going to unlock the boot loader anyway? Wouldn't that mean it would be possible to continue the stock ROM updates and then choose to unlock after the next update from moto and have the ability to flash arbitrary ROMs as current unlocked owners can? Perhaps I'm missing something between the curren unofficial unlock and moto's future unlock.
i ran the update and have lost my tethering hack... looking for a fix now.
razholio said:
Isn't moto going to unlock the boot loader anyway? Wouldn't that mean it would be possible to continue the stock ROM updates and then choose to unlock after the next update from moto and have the ability to flash arbitrary ROMs as current unlocked owners can? Perhaps I'm missing something between the curren unofficial unlock and moto's future unlock.
Click to expand...
Click to collapse
They did unlock the BT but locked it again...
Sent from my Motorola ATRIX™ 4G using XDA Premium App
No offense but the mods probably want this in Q&A. That being said, CWM Recovery is the safest route post 2.3.4 update. That is actually the preferred method anyway. All of the Atrix firmwares are available as CWM flashable zips in samcripp's fruitcakes thread. You don't really lose anything but the ability to use RSD which is least preferable anyway.
It seems that phone companies rolled out an update to 4.5.141 Im on cm7 but asking in the behalf of the people that were wondering. Is it still possible to sbf pudding and fastboot unlock from there or are we still waiting for another patch? And is it 2.3.7? I wouldn't know. My phone doesn't have the 4.5--- firmware numbers thanks for anyone who replies
Sent from my MB860 using XDA App
From what I know it is 2.3.6. As for flashing, as far as I'm aware using sbfs isn't safe (Could be wrong). If you're looking to get the stock rom for whatever reason, I've seen it on the fruit cakes page (http://forum.xda-developers.com/showthread.php?t=1163009), although most roms (cm7 or blur based) basically have this. I hope I answered some of your questions.
Oh thanks hha. I know they aren't but I thought that's what you need to unlock the boot loader. I'm trying to help someone j lock their phone and all you see are root unlovks for it and not boot loader unlocks :/
Sent from my MB860 using XDA App
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?