Hi there,
I'll try to make this brief. My touch screen has a 1/2" slice that is unresponsive (middle of the default google bar and down) and I am under warranty so I figured hey, let's call and get the phone warrantied.
Motorola is sending me a new phone when should be at my apartment when I arrive back from my travels.
My bootloader is unlocked. I understand there is no physical or theoretical way to relock thee bootloader; I get that. I am on 4.5.91. I never did the OTA updates; every update or ROM or anything since 1.26 has been from here. I've read a LOT in the last 24 hours.. and I'm concerned that trying to SBF anything over 4.5.91 will end up bricking the phone that I'm slated to return for a faulty screen. So, I was then thinking about moto-fastboot. That works for system and boot, but not bootloader, right?
My main concern is this: I don't want them to turn my phone on and see "UNLOCKED" in the top left and immediately charge me $499 for voiding the warranty. I DO understand this is a risk I took, and I am willing to eat the charge should it happen; but that withstanding my screen is legitimately borked. I'd be willing to try something to overwrite this bootloader if there were a tangible means to do it without like >80% chance of bricking it. Every SBF I've flashed on here has been pudding.
Is there anything that can be done to get rid of "UNLOCKED" up there? I know it won't relock the bootloader; but I want the techs to see that the screen is broke before they start snooping through system settings. I may get lucky, I don't know.
Also, anyone with experience warrantying a phone with an unlocked bootloader? How did it work out for you?
As it stands now I'm downloading the stock 1.8.3 system and boot images. But they won't overwrite the bootloader. I have about 4 days to figure this out before I fly home.
Thoughts?
I'm pretty sure you're stuck man.
Sent from my MB860 using Tapatalk
Hey I would play it safe and just buy another ATRIX off craigslist. I picked up an ATRIX in my area for 200 that is in mint condition. That sure beats the 499 they are going to charge you when they power on the device to check for user related problems before they slap a new screen on it and put it their refurbish phones inventory.
Sent from my MB860 using XDA App
I'd need somebody else to confirm this:
I thought that when you installed 4.5.91 through the safe .zip files, you were able to flash back to a previous SBF safely. I remember people in the IRC doing just that, and reporting that once they had done so, the "UNLOCKED" message on startup disappeared until they reflashed pudding. I'm pretty sure that it didn't actually relock the bootloader, just somehow get rid of the "UNLOCKED", but again I'm not entirely sure.
tl;dr I think you are safe to flash an SBF if you got GB from a .zip and that way you won't show "UNLOCKED".
I thought about that but I'd rather just get one from them if I'll be spending any money period.
I read a few posts that stated that there was a way to remove the "UNLOCKED" on the bootloader by flashing stock SBF's but I'm not sure if that would result in a brick at this point.. which is why I haven't tried it.
Either way.. I was also thinking: when they were troubleshooting me on the phone, they had me do a factory reset. This was yesterday. So, if it does brick I may have a "I did a system update and something went wrong" way out.
Would love to hear from someone who has experience with warranty services.
Thanks to both of you for your replies. I am also slightly inclined to believe I am boned. :[
KF as soon as someone verifies that I'll be happy to. I still have the 1.2.6 and 1.5.7 stock SBF's. To the best of my knowledge, I never let the OTA update happen. On my XOOM yes but not on the Atrix. Just unlocked, flashed what ever rom/zip I wanted, and went to town. Sucks that my screen blew I just had it where I wanted it with 2.3.4 :[
There's an 4.5.91 SBF. It should be safe to flash per eval-'s post. This should get rid of your "unlocked" without the danger of attempting to flash an earlier version.
lauterm said:
There's an 4.5.91 SBF. It should be safe to flash per eval-'s post. This should get rid of your "unlocked" without the danger of attempting to flash an earlier version.
Click to expand...
Click to collapse
I agree...by flashing a rom via RSD should get rid of "UNLOCK" text..
here is another link...http://forum.xda-developers.com/showthread.php?t=1125944
deziguy420 said:
I agree...by flashing a rom via RSD should get rid of "UNLOCK" text..
here is another link...http://forum.xda-developers.com/showthread.php?t=1125944
Click to expand...
Click to collapse
I love you both. It worked and I'm on the stock stuff now.
Everything else is up to the fate of the universe. At least they'll see that my screen is messed up before they start prodding around.
What happened?
Can you let us know if this was successful? I'd really like to do the same thing if it was...
Related
i just update the 2.3.4 by recovery.
after it done, i change the fonts in the system.
I FORGOT TO CHANGE THE RIGHT FOR THE FILES
now, it cannot power on. even cannot enter RSD mode.
the screen just show __svf 105:1:2__
what can i do now.
Do you also see 0x1000 on the screen? Possible you bricked.
If so, you may want to read this --> http://forum.xda-developers.com/showthread.php?t=1165154
I see people with the same error as you also getting the 0x1000.
What were you on, and what had you done, i.e. unlocked bootloader, before flashing?
Which 2.3.4 did you flash?
yes, i saw that numbers.
after i OTA to 2.3.4, i flashed into 1.6.8. i didnt do unlock for it.
so, as you know, the phone become a brick.
before that, i dont know it cannot downgrades
0u0u05 said:
yes, i saw that numbers.
after i OTA to 2.3.4, i flashed into 1.6.8. i didnt do unlock for it.
so, as you know, the phone become a brick.
before that, i dont know it cannot downgrades
Click to expand...
Click to collapse
If there was no warning about downgrading after the OTA prior to you installing the upgrade, you could go to a store and argue with them that since there was no warning, you did not know you couldn't flash back.
lol.
even i argue with them, maybe my phone still sleep.
i dont want to arguing, just let it back.
thank you so much for providing many informations. im trying to unbrick it.
thanks a lot
CaelanT said:
If there was no warning about downgrading after the OTA prior to you installing the upgrade, you could go to a store and argue with them that since there was no warning, you did not know you couldn't flash back.
Click to expand...
Click to collapse
there does not need to be a warning as the sfb's are not supposed to be public at all. So in flashing them you are already going against theme. Not to mention anyone at a store will most likely have no idea what your talking about lol. Its worth a shot tho.
cool.
im look that thread, but got some problems.
do you know how to use nvflash.zip
i mean, after i download that, how to keep going the steps.
Continue reading at your own risk - I'm a noob
-------------------
I'm almost entirely a noob when it comes to phone development. But I've done a bit of research recently, and came across this thread:
http://forum.xda-developers.com/showthread.php?t=1136261
Now that we too are running 4.5.91, would this method actually work?
If I were a rich dude I'd just go ahead and attempt it, but I have no where near the funds to be able to get myself a new phone if this bricks it. (I'm not even 18 yet, heh)
Don't bash me if this is a stupidly stupid idea that has no potential for success
I'm just trying to see if maybe this gives one of you super smart people an idea or two.
--------------------
So I unpacked the SBF from the aforementioned thread (the one that was supposed to prep bootloader for unlock) and loaded the code groups with HxD (hex editor)
Using this http://forum.xda-developers.com/showthread.php?t=1205527 the CG3 indeed has the values for Atrix, but also using that table i wonder if the sbf file can be modified to include the X2 values instead?
Again I'm a noob and just throwing ideas out there
Maybe ill try it when I get to my computer. I have a spare dx2 i could try it on fortunately!
Sent from my DROID X2
uhh186 said:
I'm almost entirely a noob when it comes to phone development. But I've done a bit of research recently, and came across this thread:
http://forum.xda-developers.com/showthread.php?t=1136261
Now that we too are running 4.5.91, would this method actually work?
If I were a rich dude I'd just go ahead and attempt it, but I have no where near the funds to be able to get myself a new phone if this bricks it. (I'm not even 18 yet, heh)
Don't bash me if this is a stupidly stupid idea that has no potential for success
I'm just trying to see if maybe this gives one of you super smart people an idea or two.
Click to expand...
Click to collapse
Probably Not, Different signatures (and the risk of hard bricks), The2dcour is working tireless to bring the bootloader unlock to us, and don't feel bad we were all new once
ericerk said:
Probably Not, Different signatures (and the risk of hard bricks), The2dcour is working tireless to bring the bootloader unlock to us, and don't feel bad we were all new once
Click to expand...
Click to collapse
Probably not, but if IDMA.DROID.X2 is willing to risk hard bricking that spare x2, it might be worth a shot!
He might just get the worlds first unlocked Droid X2.
I'm willing to test anything on my X2 as well. I'm switching phones soon so unless my dad wants it, I'll either sell it or keep it for any future developments here..
uhh186 said:
Probably not, but if IDMA.DROID.X2 is willing to risk hard bricking that spare x2, it might be worth a shot!
He might just get the worlds first unlocked Droid X2.
Click to expand...
Click to collapse
All in the name of gloating haha
Ill try it tonight if time permits. I'm hoping that the signatures are the same!
The atrix is pretty much thr same spec wise right?
Sent from my DROID X2
Yes, besides the HSPA+ radio in the Atrix.
EDIT: Can I ask, what you are planning on doing? Just my curiosity.
So I unpacked the SBF from the aforementioned thread (the one that was supposed to prep bootloader for unlock) and loaded the code groups with HxD (hex editor)
Using this http://forum.xda-developers.com/showthread.php?t=1205527 the CG3 indeed has the values for Atrix, but also using that table i wonder if the sbf file can be modified to include the X2 values instead, and whether this might yield better/safer results?
Again I'm a noob and just throwing ideas out there
Less of a noob then me! Haha, I got lost reading that! I think we should mod it, seems like itmakes sense too.
I was going to try threw atrix unlock in the link in OP.
Sent from my DROID X2
The problem with modding it is that I don't know how the sbf file works... any modification with the files to make it reflect the x2 would require the insertion of bytes, I think... maybe not... either way we need multiple DROID x2s available for testing...
Sent from my DROID X2
uhh186 said:
The problem with modding it is that I don't know how the sbf file works... any modification with the files to make it reflect the x2 would require the insertion of bytes, I think... maybe not... either way we need multiple DROID x2s available for testing...
Sent from my DROID X2
Click to expand...
Click to collapse
This is a reply to most of the above posts as well as the quoted text.
The Pudding SBFs are signed by two or more source to specifically work with your phone / manufacturer / provider. There is basically no way to get around this besides getting the private signing keys from each source (and you think getting an sbf with unlockable bootloader is hard?)
I could make an sbf with the RDLs etc from the X2 and jsut the BL from Atrix, but the BL is still going to be signed for our(Atrix) phone. If someone seriously wants to brick their phone I'll do it for the lulz. You can probably even recover by stock sbf flashing (no guarantees, kiss your phone goodbye imho).
If you really want to give it a shot shoot me a PM, first come first brick. And please, don't give the file to anyone else, I don't want even more than one intentional brick.
the2dcour said:
This is a reply to most of the above posts as well as the quoted text.
The Pudding SBFs are signed by two or more source to specifically work with your phone / manufacturer / provider. There is basically no way to get around this besides getting the private signing keys from each source (and you think getting an sbf with unlockable bootloader is hard?)
I could make an sbf with the RDLs etc from the X2 and jsut the BL from Atrix, but the BL is still going to be signed for our(Atrix) phone. If someone seriously wants to brick their phone I'll do it for the lulz. You can probably even recover by stock sbf flashing (no guarantees, kiss your phone goodbye imho).
If you really want to give it a shot shoot me a PM, first come first brick. And please, don't give the file to anyone else, I don't want even more than one intentional brick.
Click to expand...
Click to collapse
Yeah that's basically it.
If you want to try to for the lulz, you would only want to flash the bootloader partition and not with the RDL partitions for the Atrix radio. Flashing the radio would instantly fail. You may need a more direct method in flashing like (dd if= of= ).
I wouldn't stop you from trying it. But you are messing with the bootloader and there's no guarantee that when you boot, you can get into a state where you can SBF again.
the2dcour said:
This is a reply to most of the above posts as well as the quoted text.
The Pudding SBFs are signed by two or more source to specifically work with your phone / manufacturer / provider. There is basically no way to get around this besides getting the private signing keys from each source (and you think getting an sbf with unlockable bootloader is hard?)
I could make an sbf with the RDLs etc from the X2 and jsut the BL from Atrix, but the BL is still going to be signed for our(Atrix) phone. If someone seriously wants to brick their phone I'll do it for the lulz. You can probably even recover by stock sbf flashing (no guarantees, kiss your phone goodbye imho).
If you really want to give it a shot shoot me a PM, first come first brick. And please, don't give the file to anyone else, I don't want even more than one intentional brick.
Click to expand...
Click to collapse
Ok, thanks for clearing that up.
I made it clear of my noobiness exactly for this reason. I don't know these things yet.
This thread should be deleted.
Sent from my DROID X2
uhh186 said:
So I unpacked the SBF from the aforementioned thread (the one that was supposed to prep bootloader for unlock) and loaded the code groups with HxD (hex editor)
Using this http://forum.xda-developers.com/showthread.php?t=1205527 the CG3 indeed has the values for Atrix, but also using that table i wonder if the sbf file can be modified to include the X2 values instead, and whether this might yield better/safer results?
Again I'm a noob and just throwing ideas out there
Click to expand...
Click to collapse
Yeah. We have the same partition table for the most part with the Atrix. The problem is that the at the bottom of the CG3 file is the signature and the signature is definitely NOT the same with the Atrix. Same goes for the bootloader, recovery and boot partitions.
Now we may be able to flash the Atrix bootloader since technically they have the same CPU and the the bootloader is nothing more than a BIOS. But there is no guarantee that the Atrix bootloader on the DX2 will work enough to the point where you can SBF out of it. Hopefully, you just fail the signature check and the phone allows you to SBF. We'll see if someone wants to try. And if you error, I want to know what the error says.
mostKnownUnknown said:
Yeah. We have the same partition table for the most part with the Atrix. The problem is that the at the bottom of the CG3 file is the signature and the signature is definitely NOT the same with the Atrix. Same goes for the bootloader, recovery and boot partitions.
Now we may be able to flash the Atrix bootloader since technically they have the same CPU and the the bootloader is nothing more than a BIOS. But there is no guarantee that the Atrix bootloader on the DX2 will work enough to the point where you can SBF out of it. Hopefully, you just fail the signature check and the phone allows you to SBF. We'll see if someone wants to try. And if you error, I want to know what the error says.
Click to expand...
Click to collapse
You are right on with everything you've been saying. I've in fact flashed unsigned / signed for other phone BLs on my Atrix. The result is a febe error (Failed to boot 4 or something). Basically it rejected the BL coz it wasn't signed properly but I could still recover.
That being said, what I did was idiotic and could have easily resulted in a hard brick.
@Uhh186 please msg a Moderator with a link to this post if you want it deleted. Honestly the best outcome of this would be a soft brick.
SwiftLegend said:
I'm willing to test anything on my X2 as well. I'm switching phones soon so unless my dad wants it, I'll either sell it or keep it for any future developments here..
Click to expand...
Click to collapse
Really!
PLEASE consider donating it to navenedrob.
Thanks
uhh186 said:
I have no where near the funds to be able to get myself a new phone if this bricks it.
Click to expand...
Click to collapse
No insurance?
If it in fact did flash, even if it soft/hard bricked the phone, would it be at all useful knowing that it actually passed the bootloaders sig check?
Edit: and what are the pros and cons of flashing, I'm thinking this(but could be way off base):
cons:
1. it doesnt pass sig check and fails but is more than likely recoverable
2. It passes sig check but the bootloader is incompatible with our phone( which from my perspective is unlikely because the hardware the bootloader depends on is similar/the same?) and is more than likely hard bricked
now for pro's:
1. It passes sig check, so now we know a little more about how the sign works if even a little?
2. It passes sig check and the bootloader is intact with the ability to unlock(score)
again I might be way off base, but only one out of four results in a hard brick(maybe) and thats only if the sig passes.
Am I close?
I also have another unrelated question. idk enough about the hardware, but would one be capable of physically flashing/backing up something from these partitions?
And by physically, I mean taking the phone apart and flashing straight to whatever memory our phone uses, effectively bypassing any soft/firmware on the phone. Basically, reflashing the "firmware" of our phone with an external NAND backup/restore which would mean no permanent brick and room to experiment.
the2dcour said:
@Uhh186 please msg a Moderator with a link to this post if you want it deleted. Honestly the best outcome of this would be a soft brick.
Click to expand...
Click to collapse
My main goal with this post was to spark some kind of a conversation between developers. I seem to have done that (woo) and because I'm still learning about all this stuff I'm going to leave it open so I get the chance to learn from all of you guys' smart posts.
Hello everyone
I unlocked my Atrix (MB860, NORDICS RETAIL) some months ago and then I installed NottachTrix1.3.1 Rom. The day after the new Rom installation I experienced a lot of stability issues so I flashed the stock SBF file to bring the phone into its original state.
But since that time my phone is working worse than before: it gets very hot sometime and the battery drains much faster, if before with an intense use it worked for more than a 24 hours now with a moderate use if doesn't reach night sometime. This happens even if I flash the SBF file and then I leave all only the original applications of the phone without a restore of the backed-up ones.
I've been reading many articles about Atrix problems till now, but there are so many that it's probably impossible to not get confused, and I haven't been able to find something that helps me to solve mine yet.
Now I have some doubts I would like to ask you:
1- Did I pick up the right sbf file for my phone (the package says MB860, NORDICS RETAIL my sbf file is 1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.1-release-keys-signed-NonEFIGSRetail-EU.sbf)?
2- There can be some components installed by custom rom that may still be working in the device(kernel,filesystem,radio or whatever) also after the sbf file flash and causing the problems I'm experiencing?
Thank you
Bye
Big-Bob said:
Hello everyone
I unlocked my Atrix (MB860, NORDICS RETAIL) some months ago and then I installed NottachTrix1.3.1 Rom. The day after the new Rom installation I experienced a lot of stability issues so I flashed the stock SBF file to bring the phone into its original state.
But since that time my phone is working worse than before: it gets very hot sometime and the battery drains much faster, if before with an intense use it worked for more than a 24 hours now with a moderate use if doesn't reach night sometime. This happens even if I flash the SBF file and then I leave all only the original applications of the phone without a restore of the backed-up ones.
I've been reading many articles about Atrix problems till now, but there are so many that it's probably impossible to not get confused, and I haven't been able to find something that helps me to solve mine yet.
Now I have some doubts I would like to ask you:
1- Did I pick up the right sbf file for my phone (the package says MB860, NORDICS RETAIL my sbf file is 1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.1-release-keys-signed-NonEFIGSRetail-EU.sbf)?
2- There can be some components installed by custom rom that may still be working in the device(kernel,filesystem,radio or whatever) also after the sbf file flash and causing the problems I'm experiencing?
Thank you
Bye
Click to expand...
Click to collapse
i donr know the anwser of the first question.
second no when you flash a sbf you erase everything on the phone so it looks like when you buy it even lock the bootloader again.
maybe one app runing in background or mobile data.
send it to technical support if youre in warranty.
cheers
Thank you lucamibel
lucamibel said:
second no when you flash a sbf you erase everything on the phone so it looks like when you buy it even lock the bootloader again.
Click to expand...
Click to collapse
Oh well it's not really like you said, for example the bootloader unlocking process is not reversible through the sbf file flash, because after it, the "Unlocked" text on the top-left corner is just hidden but if you try to re-take the unlocking procedure when you execute the unlocking command it will say that the device is already unlocked while when you execute it at the first time it unlocks the phone , so there is something that the sbf file flash procedure doesn't recover. I haven't tried to install the rom recovery tool without unlocking the phone yet, I'm try to avoid other dangerous actions on it now.
lucamibel said:
maybe one app runing in background or mobile data.
Click to expand...
Click to collapse
These issues will happen even if I leave the phone with the configuration in the SBF file image, so I would exclude that reason.
lucamibel said:
send it to technical support if youre in warranty.
Click to expand...
Click to collapse
I'm still in warranty, but the phone is unlocked
Bye
Big-Bob said:
Thank you lucamibel
Oh well it's not really like you said, for example the bootloader unlocking process is not reversible through the sbf file flash, because after it, the "Unlocked" text on the top-left corner is just hidden but if you try to re-take the unlocking procedure when you execute the unlocking command it will say that the device is already unlocked while when you execute it at the first time it unlocks the phone , so there is something that the sbf file flash procedure doesn't recover. I haven't tried to install the rom recovery tool without unlocking the phone yet, I'm try to avoid other dangerous actions on it now.
These issues will happen even if I leave the phone with the configuration in the SBF file image, so I would exclude that reason.
I'm still in warranty, but the phone is unlocked
Bye
Click to expand...
Click to collapse
You are correct in saying that the bootloader remains unlocked. Also, if you search the forums I think you will have a very hard time finding anyone who has had a warranty return rejected for an unlocked bootloader. I would get rid of the "unlocked" text and send it in for repair if you need to.
Thanks CaelanT
I think that would probably be the best thing to do. It's being too hard to find a solution by myself.
I've just bring the phone back at its factory status and as soon as it'll restart with the issues I'll send it to the assistance, if they won't matter about the unlocked status it would be only better.
Big-Bob said:
Thanks CaelanT
I think that would probably be the best thing to do. It's being too hard to find a solution by myself.
I've just bring the phone back at its factory status and as soon as it'll restart with the issues I'll send it to the assistance, if they won't matter about the unlocked status it would be only better.
Click to expand...
Click to collapse
sorry i think i dont express well when i said that, i mean it that the "unlocked" cartel hide and you can send it to technical support
cheers
Hello, I know it has been posted here million times but I would not like to brick my phone.
I just got my Moto Atrix before 5 months. Quite like the phone but I heard you need to root and unlock the device to experience a great and fast smarthphone so I did. I was using CM7 all the time.
I unlocked my bootloader / root using this thread. http://forum.xda-developers.com/showthread.php?t=1302423
Everything works great but my Wi-fi is starting to weird out and it does not want to work correctly. I wanted it to return it to the shop, so they could fix it / get me a new phone but when I was there the last time, the girl rebooted my phone and saw there the "unlocked" text on Moto logo. She just gave me the phone and said to go out. I would like to remove that Text from there but dont know how. I was reading a lot of posts but everyone was saying : once you unlock bootloader, its permanent. Yes, I know it. I read all FAQs before flashing.
All I want is to remove the text so I can return them the phone.
Thanks
The only known way to do this is to flash the stock SBF. But it has to be exactly the one that was installed before any modding. Yes, that means you'll have to remember what exactly version and variant of the stock firmware you had before. SBFs are extremely dangerous so make absolutely sure you know what you're doing.
ravilov said:
The only known way to do this is to flash the stock SBF. But it has to be exactly the one that was installed before any modding. Yes, that means you'll have to remember what exactly version and variant of the stock firmware you had before. SBFs are extremely dangerous so make absolutely sure you know what you're doing.
Click to expand...
Click to collapse
so if I mistake SBF and flash the bad one I will be bricked and I can use phone as hammer ? Am I getting it right?
nifelvind said:
so if I mistake SBF and flash the bad one I will be bricked and I can use phone as hammer ? Am I getting it right?
Click to expand...
Click to collapse
Very likely.
removing unlocked text
You may want to try this before flashing sbf. This method worked for me. . No guarantee it will work for you . but i think it just might. first thing is to flash the 2,3,4 4591 fruitcake. then update to 2.3.6 45141 from the official motorola software update. the unlock text should be gone if you are successful in doing this. I did this several months ago because my camera led burnt out. good luck. also you may want to try to go to a different store or service center. :fingers-crossed:
nifelvind said:
I wanted it to return it to the shop, so they could fix it / get me a new phone but when I was there the last time, the girl rebooted my phone and saw there the "unlocked" text on Moto logo. She just gave me the phone and said to go out.
Click to expand...
Click to collapse
You can't return to Motorola? I have not heard of, or read of anyone having issues with an unlocked bootloader when sending in for warranty. Is there a reason you have to return to the shop and not Motorola?
It doesn't need to be the same and exact SBF that was on it originally, it just has to be a SBF that is compatible with your phone. I remember I soft bricked an atrix while rooting it, and flashing an old AT&T SBF hid the UNLOCKED white text.
Basically you need to find out which SBF would be compatible with your phone. It shouldn't brick your phone unless you downgrade firmware, which is a huge no no on the atrix
CaelanT said:
You can't return to Motorola? I have not heard of, or read of anyone having issues with an unlocked bootloader when sending in for warranty. Is there a reason you have to return to the shop and not Motorola?
Click to expand...
Click to collapse
Got the phone from O2, I dont know if I can return it back to Motorola.
CaelanT said:
You can't return to Motorola? I have not heard of, or read of anyone having issues with an unlocked bootloader when sending in for warranty. Is there a reason you have to return to the shop and not Motorola?
Click to expand...
Click to collapse
In Singapore, Motorola would not even accept the phone if its only rooted. As long as the phone is modified in some way (unlocked bootloader/ rooted), your warranty is void.
Sent from that Atrix.
tatperson said:
As long as the phone is modified in some way (unlocked bootloader/ rooted), your warranty is void.
Sent from that Atrix.
Click to expand...
Click to collapse
Not necessarily my friend. When you unlock the bootloader the text displayed states that unlocking your bootloader MAY void your warranty. It at no time says WILL void your warranty. Now, in Singapore you may have problems returning a phone, but I am assuming he/she is in the UK if on O2. There are a number of threads where people have returned unlocked phones to Motorola and had them repaired or replaced without issue.
OP, doesn't matter if you bought your phone from O2. It will still have a Motorola warranty on it. As long as you are buying new or refurbished from a reputable dealer, then you should be fine. You can go to Motorola's website and check if your phone is in warranty or not.
At the end of the day, worst they can do is tell you that your warranty is void.
i just got mine fixed, no problem with unlocked text on
the only problem they will lock your phone forever before return to you
Bottom line is, no matter what you do, Motorola can easily tell if you've tampered with your phone in an "undesirable" way, and it's ultimately up to them whether that will be a problem or not. Sometimes they are generous and don't care, other times they are merciless *****es and will make your life hell (and charge you for it). YMMV.
Hey,
I was on CM7, then I flashed Stock Gingerbread using CWM (Fruitcake, I think), I want to remove root and the "unlocked" sign when booting. I was searching this forum (and the rest of the internet ) for a couple of days and didn't find a solution. Either the links are dead or there is a person threating with hard brick. Does anyone know how to do this safely and has necessary files, please? Thank you in advance.
Wait, what exactly do you want to do?
If you want to just remove the text while the BL and everything else remains unlocked... That is impossible, you cannot do that.
If you want to re-lock your BL... well, that would probably be the only time (apart from when unlocking the BL) when you should reach for a SBF. There is no other known way to re-lock the BL.
Yep, I need to re-lock the BL, to get the phone to factory state (I know it won't actually re-lock the BL, just the sign will disappear). But I didn't find any usable SBF's, everybody is writing about hardbrick or the links are down. I found a couple of US ATT SBF's , but really don't know which one to use, I really don't want to brick my phone
Okay, I found this site with SBF's:
http://www.filefactory.com/f/89f588286a560e39/
I guess this one SHOULD put my phone back to factory state without root access and unlocked sign. Does anyone know, if it's safe? And if it's the only file I need to flash. Thanks
All the SBFs were removed here because they are too dangerous. For that same reason, you won't find many people here who will be willing to help you with them, not even say "yes, this one is good" or "no, don't use this one". It's just too dangerous and nobody wants to take responsibility for other people's phones like that. Not to mention, you failed to give any relevant information on your phone, so even if someone wanted to help, they can't.
What information do you have on mind?
Currently I'm running rooted unlocked stock gingerbread 2.3.4 (System version: 45.31.20.MB860.NonEFIGSRetail.en.EU, Build number: 4.5.2A-74_OLE-31.20).
If flashing SBF is dangerous, is there any method to get back to factory state?
Yes, that would be the information needed.
Flashing a SBF is the only known way to remove the "Unlocked" text while booting; however you will still find very little support here for doing that - like I said, it is too dangerous, things can go wrong too easily.
You can flash a fruitcake to return the system to stock, but the "Unlocked" text will remain.
That's what I was afraid of So no one will tell me: "Yes, with your configuration you can flash this and you'll be fine."
Nevermind, I will send for repair like this (problem with touchscreen - fantom touches, quite common hardware problem on atrixes) and in the worst case I´ll just pay for the repair.
Anyways, thank you for help, I really appreciate it! :good:
People have been known to just flash over the stock firmware and send it in and be fine. A lot of service centers don't really care about the unlocked BL or even a custom recovery.
i think he can remove unlocked sign with flashing motorola logo. if i remember corectly
Sent from my MB860 using xda app-developers app
Nope.