I have an ATRIX 4G MB860 from T-Mobile UK with 2.2.2 stock Froyo with just the bootloader unlocked. I also have had it sim unlocked using the unlock code.
My Question is, would this unlocked bootloader cause any issues whenever the T-Mobile OTA upgrades come.
Would I be able to use the OTA upgrade or would I need to flash a custom ROM using CWM or something?
I hope the OTA wont brick the phone cuz the bootloader is unlocked.
Any comments?
Thanx
Sent from my MB860 using XDA App
shabeepk said:
I have an ATRIX 4G MB860 from T-Mobile UK with 2.2.2 stock Froyo with just the bootloader unlocked. I also have had it sim unlocked using the unlock code.
My Question is, would this unlocked bootloader cause any issues whenever the T-Mobile OTA upgrades come.
Would I be able to use the OTA upgrade or would I need to flash a custom ROM using CWM or something?
I hope the OTA wont brick the phone cuz the bootloader is unlocked.
Any comments?
Thanx
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Erm... theoretically you can.... BUT YOU SHOULDN"T....
Official 2.3.4 "burns a fuse", meaning you can't go back to 2.2.2 or you will hard brick. Official OTA 2.3.4 also comes with a new bootloader that causes problems (you will most likely have to reflash pudding to get the phone unlocked again),
ANYWAY, you can upgrade to Official 2.3.4 without flashing OTA.
Since you have unlocked your BL, you do have experience with using fastboot?
Flash CWM, and then flash the Official rom from here via moto-fastboot:
http://forum.xda-developers.com/showthread.php?p=15970117#post15970117
This way, you will only flash the "boot" and "system" partitions. (It's also advisable to flash the "webtop" and "radio").
It's really the safest way to upgrade to Official rom without losing the BL unlock, burning the fuse, risking a brick, etc...
xploited said:
Erm... theoretically you can.... BUT YOU SHOULDN"T....
Official 2.3.4 "burns a fuse", meaning you can't go back to 2.2.2 or you will hard brick. Official OTA 2.3.4 also comes with a new bootloader that causes problems (you will most likely have to reflash pudding to get the phone unlocked again),
ANYWAY, you can upgrade to Official 2.3.4 without flashing OTA.
Since you have unlocked your BL, you do have experience with using fastboot?
Flash CWM, and then flash the Official rom from here via moto-fastboot:
http://forum.xda-developers.com/showthread.php?p=15970117#post15970117
This way, you will only flash the "boot" and "system" partitions. (It's also advisable to flash the "webtop" and "radio").
It's really the safest way to upgrade to Official rom without losing the BL unlock, burning the fuse, risking a brick, etc...
Click to expand...
Click to collapse
Yes, I have experience working with fastboot
Just one more question, does it make any difference that I have T-Mobile version of the phone. Would that cause any problems? Cuz the thread you have referred to is an AT&T thread ?
shabeepk said:
Yes, I have experience working with fastboot
Just one more question, does it make any difference that I have T-Mobile version of the phone. Would that cause any problems? Cuz the thread you have referred to is an AT&T thread ?
Click to expand...
Click to collapse
If you have T-mobile - DONT flash the radio. And you will be super duper safe.
p.s. just to be safe - backup your current rom with CWM before flashing.
I still haven't rooted the phone. What method do you recommend for my T-Mobile device?
Sent from my MB860 using XDA App
iv been looking for help on this too!
I put gingerblur on my rooted atrix yesterday using this video
youtube.com/watch?v=MvC0C2h95BY&list=FLqfb2F1A2s4Z08JTFsWNuGg&index=4&feature=plpp_video
and ever since my homescreen button and search button dont work and i no longer have a lock screen so i want to go back to stock
my phone before i put it on gingerblur was 2.2.2 froyo on tmobile uk (unlocked device with no tmobile branding on the rear cover)
i would really apreciate it if someone could guide me how to turn it back to the software it came with or an official less buggy software please?
i checked my ota upgrade and it says i can go to ATT gingerbread but then i msure this wouldnt work in the uk with the radio update
im not sure at all what im doing with this and i wish i didnt follow the tutorial in the first place can someone help me please!
Related
If i flashed the ota. And u have unlocked bl and cwm, can I flash custom roms from 2.3.4?
Sent from my MB860 using XDA App
Javi97100 said:
If i flashed the ota. And u have unlocked bl and cwm, can I flash custom roms from 2.3.4?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Yes you can
K thanks
Sent from my MB860 using XDA App
I too flashed the OTA( 2.3.4), I wasn't rooted or unlocked when i did it. will there be a way to get the official version when released on my device?
(didn't know if i had to start another thread since OP already started it)
velvetmxo said:
I too flashed the OTA( 2.3.4), I wasn't rooted or unlocked when i did it. will there be a way to get the official version when released on my device?
(didn't know if i had to start another thread since OP already started it)
Click to expand...
Click to collapse
Since it hasn't come out yet, no one knows if ota 2.34 we flashed will accept official updates properly. But if that's the case devs will definitely figure out ways to extract the files needed to install them either through fastboot or cwm most likely. You'll want to be unlocked and rooted.
mysticdrew said:
Since it hasn't come out yet, no one knows if ota 2.34 we flashed will accept official updates properly. But if that's the case devs will definitely figure out ways to extract the files needed to install them either through fastboot or cwm most likely. You'll want to be unlocked and rooted.
Click to expand...
Click to collapse
looks like i'm out of luck with the unlocking and rooting since it requires me to RSD flash to a different rom prior to updateing to 2.34 when they are saying it causes bricks. guess i'll wait for the official att and see if we can do the same update setup over the beta..love it though..just hate the fact my signal keeps going white then blue...any way thanks
I am currently waiting on the official Gingerbread to be released rather than flashing the custom 2.3.4 build that's floating around XDA. I'm basically wondering if, when the official Gingerbread is released, will the unlocking option be available in the update or will I have to do something else to actually unlock the bootloader? If it isn't an option that Motorola will provide, will it be easy after the update or should I update it now?
Lastly, I am using GingerBlur 4.5, so I'm assuming I will have to flash back to 4.1.8.3 to get the official update? I'm VERY worried about hard bricking my phone so what do I want to avoid (and why do I want to avoid so and so)??
Thanks for the help.
Kaaji1359 said:
I am currently waiting on the official Gingerbread to be released rather than flashing the custom 2.3.4 build that's floating around XDA. I'm basically wondering if, when the official Gingerbread is released, will the unlocking option be available in the update or will I have to do something else to actually unlock the bootloader? If it isn't an option that Motorola will provide, will it be easy after the update or should I update it now?
Lastly, I am using GingerBlur 4.5, so I'm assuming I will have to flash back to 4.1.8.3 to get the official update? I'm VERY worried about hard bricking my phone so what do I want to avoid (and why do I want to avoid so and so)??
Thanks for the help.
Click to expand...
Click to collapse
First part I'm not sure but you can unlock later. Second yes sbf to stock for updates
Sent from my MB860 using XDA Premium App
Bootloader for the official ota 4.5.91 update floating around the forums does not allow you to unlock it. At least not officially. You can still use pudding sbf to unlock. Check pudding thread.
Also updating to the official ota update 4.5.91 posted here you cannot SBF back to an old 4.1.26, .57, or .83 SBF or you will hard brick. This means don't flash anything besides the bootloader pudding sbf with RSD lite.
Chances are we already have gingerbread for AT&T Atrix but we will find out soon enough.
Sent from my MB860 using Tapatalk
You will probably need to SBF back to 4.1.83 to install the update, but u should be notified about the update when its available, unless you froze updater 2.2.1 with titanium backup.
Sent from my MB860 using Tapatalk
This thread might help clarify regarding the locked bootloader:
http://forum.xda-developers.com/showthread.php?t=1158428
Unlock it right now with pudding and flash lastest 2.3.4 with CWM. After that you are going to ask yourself: why didn't I do that before?
Sent from my MB860 using XDA Premium App
I may have to return my ATRIX due to Let'sTalk horrible customer service, but I was wondering if there is anyway to re-lock the Bootloader, or to hide the fact that it says, Unlocked. Thank you in advanced
Also, I'm sorry if this is in the wrong section, as this is urgent to me and I have yet to see any otherpost relating this topic.
There is another topic like this.
No you can't re-lock and no you can't "hide" the unlock wording. Sorry.
Sent from my AWESOME Atrix
Assume you installed 2.3 using CWM, if that is the case, you can flash the stock 1.8.3. Because the bootloader is not compatible with the unlocked phones, it won't show the "unlocked" text when you turn on the phone. I have tried it when I was trying to get rid if the unlocked text.
The down side is, you won't be able to flash custom ROM until you flash a compatible bootloader.
Sent from my Motorola Atrix 4G MB860 using XDA App
But downgrading will hard brick the phone.be very very carefully.
Reflash To Stock
Unfortunately, there is no way to relock a bootloader. Hence all of the warnings when you committed
but, if you use 4.5.91 the software at the address below should reinstall the newest stock software...
direct.motorola.com/hellomoto/motosupport/source/SoftwareUpdateSelect.asp?country=USA&language=ENS
be careful because Im not sure how motorola update will react to an unlocked bootloader. Ask around...do so at your own risk.
If you want to try a harder, albeit, safer method, and you are sure that you do not have a phone running 4.1.5.91, you can restore your phone to a factory SBF with this process:
briefmobile.com/motorola-atrix-4g-system-boot-file-sbf-leaked
DO NOT UNDER ANY CIRCUMSTANCES TRY TO RESTORE A 4.5.91 system to stock with RSD LITE.
To go to any of the blue webaddresses above, copy-paste them into your browser. Sorry, but I am not allowed to post links yet.
I wonder why nobody has created a CWM downgrade for US Atrixes. NFHimself made one for Bell or international users to go to 2.2.2 Bell and it works really well. Pretty much every partition is replaced. Great for masking that your boot loader is unlocked. Someone should probably do that for ATT to make downgrading less risky than flashing an sbf again...
drpratik said:
But downgrading will hard brick the phone.be very very carefully.
Click to expand...
Click to collapse
The downgrading and hard brick problem stems from using the OTA update, so you won't hard brick if for example you upgraded with KP's 4.5.91.
You also should be able to flash the 4.5.91 SBF. You just can't downgrade. There are other threads about this.
Sent from my Alienated Atrix
maledyris said:
I wonder why nobody has created a CWM downgrade for US Atrixes. NFHimself made one for Bell or international users to go to 2.2.2 Bell and it works really well. Pretty much every partition is replaced. Great for masking that your boot loader is unlocked. Someone should probably do that for ATT to make downgrading less risky than flashing an sbf again...
Click to expand...
Click to collapse
The reason the fruitcakes were created and deemed safe by the devs were because it didn't touch the BL, which people believe to be the culprit behind the hard bricks. NFhimself was brave enough to testing flashing the BL via cwm in his gobstopper on international phones, but I don't think any other devs are willing to risk hard bricking their phones by testing that theory on US phones.
There also isn't enough "reward" for doing so because if people want to downgrade they can use a fruitcake. The only gain is to get rid of the "unlock" text. But if you were really that concerned about it despite reading all the warnings of this will void you warranty, you shouldn't have unlocked in the first place.
maledyris said:
I wonder why nobody has created a CWM downgrade for US Atrixes. NFHimself made one for Bell or international users to go to 2.2.2 Bell and it works really well. Pretty much every partition is replaced. Great for masking that your boot loader is unlocked. Someone should probably do that for ATT to make downgrading less risky than flashing an sbf again...
Click to expand...
Click to collapse
Hi,
One of the reasons I did up a default CWM of 2.2.2 is to have a means of doing a reset after trying all ATT/ORANGE/TELSTRA/MOVIESTAR/etc firmwares out there which may have side effects or accumulated side effects. Hence the inclusion of the stock bootloader and radio and a write of the extra partitions to clean up whatever mix and match leftovers are in there from the various carriers. The other big one is just to be able to get a Bell OTA applied when it comes out, it will probably be similar to the leak, but best to be safe.
This is more of a Bell/Intl issue as ATT folks tend to run just ATT firmware or flash just boot and system via CWM/fastboot and don't have the same issues as flashing a sbf file.
Both the stock 2.2.2 and leaked ap20 OTA bootloaders from Bell are safe to flash after IHOP, this is not the case with ATT bootloaders and may be the case for any included in a sbf file. Finding out the hard way is not an option.
Cheers!
ken218 said:
Assume you installed 2.3 using CWM, if that is the case, you can flash the stock 1.8.3. Because the bootloader is not compatible with the unlocked phones, it won't show the "unlocked" text when you turn on the phone. I have tried it when I was trying to get rid if the unlocked text.
The down side is, you won't be able to flash custom ROM until you flash a compatible bootloader.
Sent from my Motorola Atrix 4G MB860 using XDA App
Click to expand...
Click to collapse
Say I unlocked it at 1.8.3 should I go down to 1.5.7? Is that safe?
moto helper update relocked mine flashed it to 4.5.91 and i had to reunlock and root agin i thought i was getting a driver update not ota.I was on rom homebase + extras but my win 7 64 bit wasent seeing my phone so i reinstalled drivers and updated drivers and updated moto helper and in the process flashed my phone to stock that pissed me off had to start over..I rebooted the phone several times and never seen unlocked on boot tried to fastboot into android recovery and got the triangle im all good now back on homebase ext4 just thought id share that you realy can relock at least it dont say unlocked i beleve its locked
defnow said:
and no you can't "hide" the unlock wording. Sorry.
Click to expand...
Click to collapse
Err...............yes you can!
care to share how?
Scolis said:
care to share how?
Click to expand...
Click to collapse
Read the thread from the start. It's already been said!
CaelanT said:
Read the thread from the start. It's already been said!
Click to expand...
Click to collapse
Trying this today. Seems like my vibrator motor quit working. Phone is 6 months old I should be under the year warranty or so right?
leperkuan said:
Trying this today. Seems like my vibrator motor quit working. Phone is 6 months old I should be under the year warranty or so right?
Click to expand...
Click to collapse
When I was at school 6 months < 1 year so yes!
This is where you need to look:
http://forum.xda-developers.com/showthread.php?t=1163009
CaelanT said:
When I was at school 6 months < 1 year so yes!
This is where you need to look:
http://forum.xda-developers.com/showthread.php?t=1163009
Click to expand...
Click to collapse
Lol well I wasn't sure it had a one year warranty. Found out my vibrator does work. Just sometimes doesn't on cm7. Weird. Well I may try this anyways. Tired of custom Roms.
Sent from my MB860 using Tapatalk
leperkuan said:
Found out my vibrator does work.
Click to expand...
Click to collapse
Think you should go to another site other than XDA with this. Something in the XXX domain should work for you. Too much information for me! LOL................
assuming it is still in warranty
hard brick the phone and return it
just tell them you was doing a software update and your kid unplugged the phone while doing so
What will happen if I try ti install a custom rom without unlocking my bootloader?
You might not have an access to your device.
Its wrong to do that, it will make you troubles.
Just read here and start doing things right: http://forum.xda-developers.com/showthread.php?t=1154600
Thanks for the link and that sucks things were so much easier when I was in froyo I could easily install about any rom I wanted.
So let me ask can I flash back to the last froyo firmware I had and still have on computer with RSD LITE this 2.3.4 gingerbread update was installed OTA.
Always_Jonezen said:
Thanks for the link and that sucks things were so much easier when I was in froyo I could easily install about any rom I wanted.
So let me ask can I flash back to the last froyo firmware I had and still have on computer with RSD LITE this 2.3.4 gingerbread update was installed OTA.
Click to expand...
Click to collapse
froyo/gingerbread, it didnt matter. there were no real roms until we got unlocked bootloader. i have no idea what you are talking about roms being easier to flash when you had froyo.....
unlock bootloader
flash rom
get bored
flash new rom
get bored
flash new rom
its REALLY easy to flash a rom.....what is your hesitation?
Before I updated to gingerbread I didn't have to have on a unlocked bootloader to install any p-roms or roms like a had gladiAtrix but now I keep hearing I have to be unlocked to install a rom but I don't want to unlock my ATRIX yet I might need my warranty
Always_Jonezen said:
Before I updated to gingerbread I didn't have to have on a unlocked bootloader to install any p-roms or roms like a had gladiAtrix but now I keep hearing I have to be unlocked to install a rom but I don't want to unlock my ATRIX yet I might need my warranty
Click to expand...
Click to collapse
P roms weren't real roms they were just a compilation of system edits to get around the locked bootloader. If you try to downgrade to froyo you'll brick your device. Your only option now is to unlock the bootloader. If you need you're warranty in the future you can flash a stock gingerbread sbf to goop back to stock with no visible sign of an unlocked bootloader
Sent from my MB860 using xda premium
Are there any p-roms for gingerbread and thanks for the info
Always_Jonezen said:
Are there any p-roms for gingerbread and thanks for the info
Click to expand...
Click to collapse
I don't believe so. The unlocked bootloader kind off made p roms outdated
Sent from my MB860 using xda premium
I got a used Motorola Photon that has Android 2.3.5 (build 254_12) and it has an unlocked bootloader. After going through numerous posts in XDA I came to know that 2.3.5 doesn't support bootloader unlocking. I asked the guy I bought it from and he said that initially it had MoPho 2.3.4 - he unlocked it, upgraded it to CM10 JB rom and then downgraded it back to 2.3.5 (as JB was unstable). I confirmed my MoPho has an unlocked bootloader from here ( http://forum.xda-developers.com/showthread.php?t=1650520 ). It's also rooted.
So I just wanted to know, are there any risks in installing a custom kernel/rom since my MoPho's OS ver is 2.3.5 ? Are there any internal conflicts that might occur since my OS version/build is different - one that doesn't allow unlocking of bootloader and root access?
No there aren't any major risks. Just make sure the kernel corresponds to the system you are using. For instance, if your using cm7 and want to overclock, make sure to use a kernel built for it.
Most ROMs are flashed with the kernel it needs to boot. Version 2.3.5 could be thought of as just another ROM. To flash something different, make a backup with your recovery then wipe and install the ROM of your choice.
Just be sure to us common sense and not to accept any ota update because it could lock your bootloader and brick your phone. Be sure to look at the stickies for a ton more information
Sent from my MB855 using xda premium
mystaku said:
I got a used Motorola Photon that has Android 2.3.5 (build 254_12) and it has an unlocked bootloader. After going through numerous posts in XDA I came to know that 2.3.5 doesn't support bootloader unlocking. I asked the guy I bought it from and he said that initially it had MoPho 2.3.4 - he unlocked it, upgraded it to CM10 JB rom and then downgraded it back to 2.3.5 (as JB was unstable). I confirmed my MoPho has an unlocked bootloader from here ( http://forum.xda-developers.com/showthread.php?t=1650520 ). It's also rooted.
So I just wanted to know, are there any risks in installing a custom kernel/rom since my MoPho's OS ver is 2.3.5 ? Are there any internal conflicts that might occur since my OS version/build is different - one that doesn't allow unlocking of bootloader and root access?
Click to expand...
Click to collapse
do as you please no risks with anything really. only phones that took the 2.3.5 OTA update are locked. or new factory restored ones. the previous user put the 2.3.5 update on their in a safe manor that doesn't lock the phone. :silly:
na7q said:
do as you please no risks with anything really. only phones that took the 2.3.5 OTA update are locked. or new factory restored ones. the previous user put the 2.3.5 update on their in a safe manor that doesn't lock the phone. :silly:
Click to expand...
Click to collapse
I've the 254_12 build. And (I think, I'm not sure) the OTA update is probably the only way to update your system to 254_12.
What I'm not able to understand is how he could have downgraded from a CM10 JB rom to 2.3.5(254_12) without locking the bootloader. Is there anyway to do so?
All the root/unlock guides in XDA and other forums warn us, before proceeding to unlock, to ensure that our MoPho has 2.3.5 (198_7)or below to unlock/root. Shouldn't I be worried about it?
Here's a screenshot of my system specs.
No. You're unlocked. That's just your system build information. It will change when you flash a different ROM.
The ota update is the only way to update your stock and locked phone without any sort of modification. Since you're unlocked and rooted you shouldn't have an issue flashing a custom recovery and ROM
Sent from my MB855 using xda premium
mystaku said:
I've the 254_12 build. And (I think, I'm not sure) the OTA update is probably the only way to update your system to 254_12.
What I'm not able to understand is how he could have downgraded from a CM10 JB rom to 2.3.5(254_12) without locking the bootloader. Is there anyway to do so?
All the root/unlock guides in XDA and other forums warn us, before proceeding to unlock, to ensure that our MoPho has 2.3.5 (198_7)or below to unlock/root. Shouldn't I be worried about it?
Here's a screenshot of my system specs.
Click to expand...
Click to collapse
My friend, as I mentioned, the previous user had downgraded or "upgraded" the stock firmware in a SAFE manner that does NOT lock the bootloader. It's done the same way custom ROMs work. It just another ROM basically. Pretty simple. Don't take everything so literal in terms of 2.3.5 only OTA updated or factory restored phones are locked. Which you don't have
Sent from my MB853 using XDA
na7q said:
My friend, as I mentioned, the previous user had downgraded or "upgraded" the stock firmware in a SAFE manner that does NOT lock the bootloader. It's done the same way custom ROMs work. It just another ROM basically. Pretty simple. Don't take everything so literal in terms of 2.3.5 only OTA updated or factory restored phones are locked. Which you don't have
Sent from my MB853 using XDA
Click to expand...
Click to collapse
Thank you, it's clear to me now
mystaku said:
Thank you, it's clear to me now
Click to expand...
Click to collapse
Great! I hope you have fun trying out ROMs!! It's always a blast!
Sent from my MB853 using XDA