Hey guys,
I am experiencing finger print issues with my atrix and would like to send it in for repair the problem is my atrix is unlocked with the latest cm7 weekly build.
I have been reading on forums" Just install stock version" is it advisable? Which steps should I follow?
Faizan1 said:
Hey guys,
I am experiencing finger print issues with my atrix and would like to send it in for repair the problem is my atrix is unlocked with the latest cm7 weekly build.
I have been reading on forums" Just install stock version" is it advisable? Which steps should I follow?
Click to expand...
Click to collapse
Full wipe and flash a fruitcake from here > http://forum.xda-developers.com/showthread.php?t=1163009
Thanks for the quick answer
I have 2 further questions
1. On boot will it show unlocked on the side?(boot loader unlocked)
2. Does this relock the bootloader? ex: Can i not reinstall cm7 after i get it back from warranty work?
1. Yes (only an SBF will "hide" the unlock text)
2. No
For the warranty work you will just have to cross your fingers that they will miss it or overlook it. And I think you will just need to re-root it after flashing a fruitcake (maybe?).
Faizan1 said:
Thanks for the quick answer
I have 2 further questions
1. On boot will it show unlocked on the side?(boot loader unlocked)
2. Does this relock the bootloader? ex: Can i not reinstall cm7 after i get it back from warranty work?
Click to expand...
Click to collapse
Fruitcake is kind of obvious and leaves the "unlocked" message. I would SBF if the phone is broken anyway. I just recieved a perfectly new Atrix after sending in my broken one with a flashed 2.3.6 SBF, so the chances are good. Make sure to clear all necessary partitions first! I forget exactly which, but there is ample documentation in development/Q&A. I
I had SBF'd and sucesss the Unlocked word has disappeared.
I flashed and the phone works perfectly(other than finger print original issue)and hope it wont be a problem with installing cm7 later. can anyone advise me on that?
" 1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf
any news did they fix your atrix for ya without to much problems?
Sent from my MB860 using Tapatalk
I received the phone today and boom everything works they didnt cause any issue with the bootloader being unlocked.
I had however sbf'd the phone so the unlocked word was hidden.
Now time to start messing with the phone again.
Hell I took the risk and completely bricked my phone by flashing the 1.8.3 sbf on it. The fail to boot message is pretty common among Atrixes. They didn't ask any questions and gave me a new one at the warranty ATT place. Just had to get there, in and out with a new atrix in 20 minutes. Too bad its acting up again, and I'm out of warranty
Looks like I'll be sending my Atrix to ATT soon. I will just flash a fruit cake and I won't even bother with the unlock text and hope for the best.
Related
Okay guys, i flashed the 2.3.4 ota as soon as it came out (before all this trouble with it of course) and now i am stuck because i was under the impression that the new bootloader would be unlocked so i had never even though about eating any pudding before the fact. Now i come to my trouble, im running a totally stock 2.3.4 att and i cant seem to find a way out.
Question #1- If i have a locked bootloader can i fruitcake back?
Question #2- Is there a possible way to unlock the new bootloader?
Question #3- How in heck do i get root, im on windows 7 and i recently tried the two bat files that one of the devs released and they were a no go, it didnt seem to flash the preinstall when i tried to look for it, it wasnt there. I have been quietly trying to fix this on my own for days now i am asking for a little help. Im stumped.
I got root using the /preinstall method with those 2 .bat files posted yesterday.
From page 30-35 is the guidance I followed from mramirezusa.
Other than that we are in the same boat.. I read puddings will flash relatively safely.http://forum.xda-developers.com/showthread.php?t=1159950&page=30
cthomas5714 said:
Okay guys, i flashed the 2.3.4 ota as soon as it came out (before all this trouble with it of course) and now i am stuck because i was under the impression that the new bootloader would be unlocked so i had never even though about eating any pudding before the fact. Now i come to my trouble, im running a totally stock 2.3.4 att and i cant seem to find a way out.
Question #1- If i have a locked bootloader can i fruitcake back?
Question #2- Is there a possible way to unlock the new bootloader?
Question #3- How in heck do i get root, im on windows 7 and i recently tried the two bat files that one of the devs released and they were a no go, it didnt seem to flash the preinstall when i tried to look for it, it wasnt there. I have been quietly trying to fix this on my own for days now i am asking for a little help. Im stumped.
Click to expand...
Click to collapse
Question #2- Is there a possible way to unlock the new bootloader? yes use pudding
cthomas5714 said:
Okay guys, i flashed the 2.3.4 ota as soon as it came out (before all this trouble with it of course) and now i am stuck because i was under the impression that the new bootloader would be unlocked so i had never even though about eating any pudding before the fact. Now i come to my trouble, im running a totally stock 2.3.4 att and i cant seem to find a way out.
Question #1- If i have a locked bootloader can i fruitcake back?
Question #2- Is there a possible way to unlock the new bootloader?
Question #3- How in heck do i get root, im on windows 7 and i recently tried the two bat files that one of the devs released and they were a no go, it didnt seem to flash the preinstall when i tried to look for it, it wasnt there. I have been quietly trying to fix this on my own for days now i am asking for a little help. Im stumped.
Click to expand...
Click to collapse
hey man first things first. dont panic, you are not stuck. this is temporary at best, in the mean while theres plenty of stuff you can do, sbf is not safe to begin with. so actually be gladd you only got to use RSD one time
first things first, get yourselfed unlocked, pudding will do the trick. once after pudding, you never have to touch RSD
Once you are done with pudding go ahead and get tenfars unlocked cwm
once you are done with that you are free to flash pretty much all the roms, as usually custom roms, or fruit cakes dont have bl, only the rest
enjoy
Okay guys, thanks for your help. but let me get this clear, i do not have a unlocked bootloader, im a pudding virgin. I can simply rsd the 1.83 with pudding and thats it? No worries no nothing?
cthomas5714 said:
Okay guys, thanks for your help. but let me get this clear, i do not have a unlocked bootloader, im a pudding virgin. I can simply rsd the 1.83 with pudding and thats it? No worries no nothing?
Click to expand...
Click to collapse
Yes but you still can't use any other sbf. I'd use the raw pudding sbf, unlock, then use CWM from here on out. No more rsd
Sorry about that. There is just the unlock and then the unlock packaged with 1.8.3. The one that has has been causing bricks from my understanding is the packaged one. Be sure you flash just the unlock.
Anyone know what exactly will be erased from /data after flashing the unlock? Also I don't want to restore backed up files that will conflict with new ones. Any guidance on this is appreciated.
snudmusk said:
Sorry about that. There is just the unlock and then the unlock packaged with 1.8.3. The one that has has been causing bricks from my understanding is the packaged one. Be sure you flash just the unlock.
Anyone know what exactly will be erased from /data after flashing the unlock? Also I don't want to restore backed up files that will conflict with new ones. Any guidance on this is appreciated.
Click to expand...
Click to collapse
All user data is wiped when unlocking. The 1.8.3 sbf with pudding is safe to flash but i recommend just using pudding and then CWM and ditch rsd.
jruweaver said:
All user data is wiped when unlocking. The 1.8.3 sbf with pudding is safe to flash but i recommend just using pudding and then CWM and ditch rsd.
Click to expand...
Click to collapse
Agree, just use the pudding only sbf. to unlock , then preinstall to get root.
Make sure to have 50 or so battery so you don't run into the trouble I had with battery being to low to fastboot. Also once you flash pudding you wont be able to boot the phone, don't panic just follow steps to fastboot oem unlock and phone will boot fine afterwards.
Sent from my MB860 using Tapatalk
woahh no bad idea, im scared. I did exactly as you all said and it acts like its hard bricked, SVF:105 error but then it says no OS detected and i have 14 options
1RSD
2Fastboot
3Nvflash
4-9BP something
9Android recovery
10Boot android (no bp)
11Device UID
12Console
13early usb enumeration
14BP tools
WHAT DO I DO?
cthomas5714 said:
woahh no bad idea, im scared. I did exactly as you all said and it acts like its hard bricked, SVF:105 error but then it says no OS detected and i have 14 options
1RSD
2Fastboot
3Nvflash
4-9BP something
9Android recovery
10Boot android (no bp)
11Device UID
12Console
13early usb enumeration
14BP tools
WHAT DO I DO?
Click to expand...
Click to collapse
Which did you flash? Pudding or 1.8.3 with pudding?
Try connecting your phone to pc select fastboot and finish the pudding instructions (fastboot oem unlock)
It might boot then.
Sent from my MB860 using XDA Premium App
Here is what I did.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
2. Flash pudding only SBF so you can unlock the bootloader. http://diamantephoto.com/fastboot.rar direct link. Flash this one.
http://forum.xda-developers.com/show....php?t=1136261 Original Post about pudding.
It will go to a text only 14 option screen and say something like boot failed 0x1000. Don't freak out and tell me you bricked you phone blah blah blah. You still have to unlock the bootloader by choosing fastboot from your phone and connecting it to the computer via usb. Make sure you have ADB with fastboot tools installed on you computer.
Open command prompt from you computer and type fastboot oem unlock. It'll display warning about voiding warranty and a unique device id. Type again fastboot oem unlock ############. The # are the unique device numbers. Don't type # it wont work. The instructions are posted on the pudding thread if you would like to read more about it.
Then type fastboot reboot to reboot. Unlock should be displayed on top left of screen and it'll take 5 long mins to boot up.
3.Then you need to install CWM and root.
You'll find instructions in the developers form. But if your lazy here is the CWM link. http://forum.xda-developers.com/show....php?t=1138541 follow the instructions or every time you reboot you will loose CWM. For root there are two available for gingerbread. http://forum.xda-developers.com/show....php?t=1140110 I used this one and got root.
http://forum.xda-developers.com/show....php?t=1138204 I hear this works too.. Haven't tested read the post if you want to use this method.
As always don't blame me for bricking if you happen to do so. DO IT AT YOUR OWN RISK. these are the steps I took to unlock and everything works great. Absolutely no problems with my phone after wards.
One thing unlocking your bootloader will format/erase data. Basically a factory data reset so make sure you backup everything with titanium or you favorite app. I would not restore system apps as i've had a few problems with email and motoblur force closes.
Is there a way to root without unlocking the bootloader?
five3zero said:
Is there a way to root without unlocking the bootloader?
Click to expand...
Click to collapse
Yes.
Follow the instructions listed on here:
http://forum.xda-developers.com/showthread.php?p=15023030
The 3rd post has the instructions I followed.
If you have problems be sure to read through the thread as someone else has most likely already had the same issue.
This worked for me.
cthomas5714 said:
woahh no bad idea, im scared. I did exactly as you all said and it acts like its hard bricked, SVF:105 error but then it says no OS detected and i have 14 options
1RSD
2Fastboot
3Nvflash
4-9BP something
9Android recovery
10Boot android (no bp)
11Device UID
12Console
13early usb enumeration
14BP tools
WHAT DO I DO?
Click to expand...
Click to collapse
Just do: fastboot oem unlock (or whatever tthe code is)
Them: fastboot reboot
Sent from my MB860 using XDA App
So guys I really wanna unlock the bootloader and flash some roms but this is my third atrix. Im using the 14 day grace period very very graciously. Anyways first atrix kept locking up- exchanged. Second one I tried to unlock it with pudding. Did the rsd thing with the. Sbf file and I was doing it. Then toward the end it failed. Complete brick- exchanged.
Anyways is there something else I should do, possibly a different route? Im using an AT&T atrix. Thanks.
Wait for official release and get it officially unlocked?
Sent from my MB860 using XDA Premium App
tsouza said:
Wait for official release and get it officially unlocked?
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
I can wait for the release, but are they unlocking it with it. For sure?
Well, IMO better hope for it than risk another brick...
Sent from my MB860 using XDA Premium App
tsouza said:
Well, IMO better hope for it than risk another brick...
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
True. Very true.
magicriggs said:
So guys I really wanna unlock the bootloader and flash some roms but this is my third atrix. Im using the 14 day grace period very very graciously. Anyways first atrix kept locking up- exchanged. Second one I tried to unlock it with pudding. Did the rsd thing with the. Sbf file and I was doing it. Then toward the end it failed. Complete brick- exchanged.
Anyways is there something else I should do, possibly a different route? Im using an AT&T atrix. Thanks.
Click to expand...
Click to collapse
I think you might have returned the first 2 prematurely.
1st one probably could have factory reset or flashed a new sbf
2nd one was probably a fixable soft brick.
So I'd say you're safe, but up to you as there's always a risk.
Here is what I did.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
2. Flash pudding only SBF so you can unlock the bootloader. http://diamantephoto.com/fastboot.rar direct link. Flash this one.
http://forum.xda-developers.com/showthread.php?t=1136261 Original Post about pudding.
It will go to a text only 14 option screen and say something like boot failed 0x1000. Don't freak out and tell me you bricked you phone blah blah blah. You still have to unlock the bootloader by choosing fastboot from your phone and connecting it to the computer via usb. Make sure you have ADB with fastboot tools installed on you computer.
Open command prompt from you computer and type fastboot oem unlock. It'll display warning about voiding warranty and a unique device id. Type again fastboot oem unlock ############. The # are the unique device numbers. Don't type # it wont work. The instructions are posted on the pudding thread if you would like to read more about it.
Then type fastboot reboot to reboot. Unlock should be displayed on top left of screen and it'll take 5 long mins to boot up.
3.Then you need to install CWM and root.
You'll find instructions in the developers form. But if your lazy here is the CWM link. http://forum.xda-developers.com/showthread.php?t=1138541 follow the instructions or every time you reboot you will loose CWM. For root there are two available for gingerbread. http://forum.xda-developers.com/show....php?t=1140110 I used this one and got root.
http://forum.xda-developers.com/show....php?t=1138204 I hear this works too.. Haven't tested read the post if you want to use this method.
As always don't blame me for bricking if you happen to do so. DO IT AT YOUR OWN RISK. these are the steps I took to unlock and everything works great. Absolutely no problems with my phone after wards.
One thing unlocking your bootloader will format/erase data. Basically a factory data reset so make sure you backup everything with titanium or you favorite app. I would not restore system apps as i've had a few problems with email and motoblur force closes.
Sent from my MB860 using Tapatalk
magicriggs said:
I can wait for the release, but are they unlocking it with it. For sure?
Click to expand...
Click to collapse
not sure. i got a leaked 4.5.91 build, it's not unlocked (although early beta does). you still have to flash the pudding img yourself.
delect this post
The returns were genuine. I did a factory reset on the first one and it still kept locking up, on the wake up. Had to pull battery out to turn back on. Multiple times. Second one was a complete brick. I couldn't get into rsd, wouldn't turn on and computer didn't recognize it in any mode. Im pretty familiar with rsd, used it with OG and X but this one got me walking om egg shells.
magicriggs said:
The returns were genuine. I did a factory reset on the first one and it still kept locking up, on the wake up. Had to pull battery out to turn back on. Multiple times. Second one was a complete brick. I couldn't get into rsd, wouldn't turn on and computer didn't recognize it in any mode. Im pretty familiar with rsd, used it with OG and X but this one got me walking om egg shells.
Click to expand...
Click to collapse
hmm you are very unlucky then. You're the only one to hard brick from pudding. Probably advise you not to do anything with your phone.
Jnewell05 said:
Here is what I did.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
Click to expand...
Click to collapse
im on build number 4_1.8.3 and i check for updates and it says my device is up to date. any
ideas?
magicriggs said:
im on build number 4_1.8.3 and i check for updates and it says my device is up to date. any
ideas?
Click to expand...
Click to collapse
4.1.83 is a great point to unlock the bootloader. DO NOT install the 4.5.91 OTA udpate, too risky to hard brick if you flashed an sbf. Of course, you don't have to sbf back anymore, but I would steer way clear of that when there are perfectly good options available. Only use customized ones like Kenneth's or the CherryBlur ROM. More will start flowing soon.
So what your advising is not to even unlock it. All I really want is volume wake.
magicriggs said:
So what your advising is not to even unlock it. All I really want is volume wake.
Click to expand...
Click to collapse
That's the exact opposite of what I'm advising. I knew I was taking some level of risk when I unlocked, but it's a risk well worth taking. Very, very low failure rate. Recoverable. But I can't accept the risk for your phone.
OSNPA said:
That's the exact opposite of what I'm advising. I knew I was taking some level of risk when I unlocked, but it's a risk well worth taking. Very, very low failure rate. Recoverable. But I can't accept the risk for your phone.
Click to expand...
Click to collapse
Oh gotcha. Thanks for the info.
Jnewell05 said:
Here is what I did.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
2. Flash pudding only SBF so you can unlock the bootloader. http://diamantephoto.com/fastboot.rar direct link. Flash this one.
http://forum.xda-developers.com/showthread.php?t=1136261 Original Post about pudding.
It will go to a text only 14 option screen and say something like boot failed 0x1000. Don't freak out and tell me you bricked you phone blah blah blah. You still have to unlock the bootloader by choosing fastboot from your phone and connecting it to the computer via usb. Make sure you have ADB with fastboot tools installed on you computer.
Open command prompt from you computer and type fastboot oem unlock. It'll display warning about voiding warranty and a unique device id. Type again fastboot oem unlock ############. The # are the unique device numbers. Don't type # it wont work. The instructions are posted on the pudding thread if you would like to read more about it.
Then type fastboot reboot to reboot. Unlock should be displayed on top left of screen and it'll take 5 long mins to boot up.
3.Then you need to install CWM and root.
You'll find instructions in the developers form. But if your lazy here is the CWM link. http://forum.xda-developers.com/showthread.php?t=1138541 follow the instructions or every time you reboot you will loose CWM. For root there are two available for gingerbread. http://forum.xda-developers.com/show....php?t=1140110 I used this one and got root.
http://forum.xda-developers.com/show....php?t=1138204 I hear this works too.. Haven't tested read the post if you want to use this method.
As always don't blame me for bricking if you happen to do so. DO IT AT YOUR OWN RISK. these are the steps I took to unlock and everything works great. Absolutely no problems with my phone after wards.
One thing unlocking your bootloader will format/erase data. Basically a factory data reset so make sure you backup everything with titanium or you favorite app. I would not restore system apps as i've had a few problems with email and motoblur force closes.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
i used update.zip ..did not flash back to 1.83...update.zip (blur 1.83 etc etc) was from leaked moto servers...i have new bootloader cause my andriod recovery is different...of course BL is locked....can i still unlock??
Hi I have a attic that has a data problem and am going to return it to warranty, I want to try out 2.3.4 but you need to unlocked the bootloader, but is there a way to relock it so I can still have it under warranty. Also I have been trying to flash the 1.26 SBF file from www.bandinnovations.com and everytime I try to unzip it says broken something or other. Is there another link to try? Thanks
Sent from my MB860 using XDA App
No way!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Void warranty
RPK925 said:
Hi I have a attic that has a data problem and am going to return it to warranty, I want to try out 2.3.4 but you need to unlocked the bootloader, but is there a way to relock it so I can still have it under warranty. Also I have been trying to flash the 1.26 SBF file from www.bandinnovations.com and everytime I try to unzip it says broken something or other. Is there another link to try? Thanks
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Look for 1.26 in the dev section
They probably won't even check. I warranted mine yesterday because my fingerprint scanner was peeling. I was rooted with gingerblur, and couldn't even do a factory reset, so I had to go into Android Recovery and wipe data from there, but the rep didn't even ask what I was doing, or anything. DSCs (Device Support Centers) are usually franchise stores; in other words, they don't really care too much, just there for their $8/hr.
RPK925 said:
Hi I have a attic that has a data problem and am going to return it to warranty, I want to try out 2.3.4 but you need to unlocked the bootloader, but is there a way to relock it so I can still have it under warranty. Also I have been trying to flash the 1.26 SBF file from www.bandinnovations.com and everytime I try to unzip it says broken something or other. Is there another link to try? Thanks
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
No way to relock after unlocking the bootloader. It's a hardware lock/unlock, not software.
It may be spotted at AT&T store or service center. If they turn the phone on the first thing they will see is "unlocked" in the upper left corner. Per what it says when you unlock your phone, this "MAY" void your warranty. Don't listen to advice saying they won't care at the service center. The one where I live does everything they can to get your phone back working before replacing it. Been there a couple of times.
You can remove the "unlocked" in the boot screen by flashing back to 4.1.26, 4.1.57, etc., but the phone is still unlocked, it just won't say unlocked anymore unless you reflash the unlock, after which it will be on the boot screen again.
I would say if you are returning it, don't unlock the bootloader.
So I started with an official 2.2.2 firmware from Bell. I think this thread might serve 2 purposes, because I had a really hard time figure out all the steps from start to finish as they were in separate threads. So if someone starts off with stock 2.2.2 and wants to get a custom rom, that's the way I manged to do it. Second purpose of this post is for me to find out how I could return my Bell Atrix to stock OTA and what it would imply. Thanks a lot in advance for your inputs.
-I rooted with SuperOneClick
-Unlocked BL with
http://forum.xda-developers.com/showthread.php?t=1136261
-Installed Tenfar's CWM
http://forum.xda-developers.com/showthread.php?t=1138541
-Verified which kernel to use D00 or 1100 and dled it:
http://forum.xda-developers.com/showthread.php?t=1169409
-Then I flashed Alien Rom Build #2 with Tenfar's CWM:
http://forum.xda-developers.com/showthread.php?t=1186537&highlight=bell
-Then tried to do the D00 Intl kernel in CWM without rebooting, that didn't work ... so I rebooted and went directly to fastboot and installed the kernel as the instructions say in the link:
http://forum.xda-developers.com/showthread.php?t=1169409
-Then booted for the first time, rebooted, and flashed the ninja theme in CWM
What I want to know is if ever I wanted to go back to stock with the new GB OTA from Bell 0.37.23 what would it imply:
-Rooting is still available, but is unlocking ? and could I still unlock the APN menu.
-My BL would get relocked? What would that imply for future updates.
Also if I decided to take that route; I would
1) http://forum.xda-developers.com/showthread.php?p=15975211#post15975211
2) Download the new OTA and install
3) Root and unlock...
Thank you for you input,
NiK
You just install the gobstopper. There is no new bell gb OTA from my understanding. Only the new ATT gb ota.
The gobstopper puts you on full 2.2.2.
Thought the latest OTA was for GB .. oh well ... what you be the implications of going back to stock ... would that affect the unlocked BL, would it relock it, would it make future mods more difficult of impossible .... I come from iPhone world so updating a firmware would have a lot of future implications ...
yes gobstopper would put you back to stock 2.2.2 and re-lock the bootloader...so yes you would have a boring ass atrix again...the only time (personal opinion) i would ever revert back is for warranty purposes. This way they can't tell you f'ed with your phone.
and yes it would make future mods impossible....basically all the mods and stuff out there right now would be useless to you...in fact if you did want to mod your phone you would only be able to deodex and theme..with a few other tiny modifications...that aren't even supported by the dev' who made them anymore because everyone is using GB now lol...i'm not sure why anyone would want to go back except for warranty purposes or they are selling to someone who is new to android and doesn't want to hack their phone...
/rant
cheers bro =)
J-Roc said:
yes gobstopper would put you back to stock 2.2.2 and re-lock the bootloader...so yes you would have a boring ass atrix again...the only time (personal opinion) i would ever revert back is for warranty purposes. This way they can't tell you f'ed with your phone.
and yes it would make future mods impossible....basically all the mods and stuff out there right now would be useless to you...in fact if you did want to mod your phone you would only be able to deodex and theme..with a few other tiny modifications...that aren't even supported by the dev' who made them anymore because everyone is using GB now lol...i'm not sure why anyone would want to go back except for warranty purposes or they are selling to someone who is new to android and doesn't want to hack their phone...
/rant
cheers bro =)
Click to expand...
Click to collapse
Hi,
That is incorrect. Once you are unlocked, you are always unlocked. You either have a bootloader that knows what unlocked means or you don't.
In this case you can always go back to IHOP to be unlocked. There is no permanent relock.
The point in going back to stock is to get OTA updates from Bell, not warranty claims because if you can get back to stock you don't need a warranty. It's when your phone is locked up that you want to use your warranty and by then it's too late.
Cheers!
Ok so once the bootloader has been unlocked, whatever happens I can't relock it even when applying an OTA upgrade that upgrades the bootloader ? That sounds like the exact opposite of what happened with iPhones or PS3s or whatever electronics that needed to be jailbroken, unlocked of whatever.
NiKTaMeR said:
Ok so once the bootloader has been unlocked, whatever happens I can't relock it even when applying an OTA upgrade that upgrades the bootloader ? That sounds like the exact opposite of what happened with iPhones or PS3s or whatever electronics that needed to be jailbroken, unlocked of whatever.
Click to expand...
Click to collapse
A fuse gets blown in this case. oem lock does nothing.
What you can do is install a bootloader that doesn't know about unlocking or that that paticular fuse means it's supposed to be unlocked, So the unlocked message doesn't show up on the main screen during boot and fastboot no longer works for signed partitions. However, restoring the unlocked bootloader restores the unlock by checking the blown fuse, and oem unlock no longer has to be done.
Cheers!
Thanks a lot to everyone for your replies.
P.S NF I'm waiting to try your gobstopper 2.3.4 stupid slow upload speeds
NiKTaMeR said:
Thanks a lot to everyone for your replies.
P.S NF I'm waiting to try your gobstopper 2.3.4 stupid slow upload speeds
Click to expand...
Click to collapse
It's done if you were waiting.
Sent from my MB860 using XDA Premium App
I need to take my beloved Atrix in for a warranty replacement (dust under camera lens, severe dropped calls, data connection issues, screen unresponsiveness), but i had a couple questions beforehand.
1. I have not installed the OTA 2.3.4, I unlocked bootloader and flashed AURA. Can I SBF to the 4.1.83 and then OTA to the 2.3.4 so that the "UNLOCKED" logo is gone at the boot screen?
2. If i receive a replacement Atrix that has 2.3.4, can I still flash the PUDDING (to unlock the bootloader) and then flash a custom 2.3.4 ROM? Or will this brick my phone?!?
Thanks so much everyone, I know that this may have been posted in other threads, but I looked everywhere and cannot find a clear and concise answer. Thank you.
I'm not sure about some of your questions, but I sbf'd to 2.3.4 last night and the unlocked text is gone. Not sure if it's safe to sbf to earlier builds.