I bought an AT&T Atrix a couple of weeks ago, When I got it I unlocked the bootloader and installed the latest Allien Build. It was running everything great and didnt have any trouble at all.
About 10 days ago I sold that atrix and the new owner just wrote me telling me that his atrix shows a 0x1000 error and that he is unable to enter to fastboot and to rsd mode, he also told me that the ONLY think he did was to let the battery completely drain.
Now he want's his money back
Could it be possible to get such hardbrick ONLY after letting the battery completely drain?.
Were you ever on official 2.3.4?
Sent from my MB860 using XDA App
Javi97100 said:
Were you ever on official 2.3.4?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I got the phone with the 4.1.26 update (2.2), then I unlocked the bootloader, installed Rom racer's recovery and Installed Alien Release 4. Then I sold the phone, but everything was working well and the new owner even used the phone for a week.
Could it be possible to get an hardbrick only after letting the battery drain to 0%? Should I beleive him?
I read a lot on the forums and all the hardbrick cases are because they tried to downgrade.
josuetenista said:
I got the phone with the 4.1.26 update (2.2), then I unlocked the bootloader, installed Rom racer's recovery and Installed Alien Release 4. Then I sold the phone, but everything was working well and the new owner even used the phone for a week.
Could it be possible to get an hardbrick only after letting the battery drain to 0%? Should I beleive him?
I read a lot on the forums and all the hardbrick cases are because they tried to downgrade.
Click to expand...
Click to collapse
I'm on stock GB, rooted and unlocked and drained my battery down to 0 yesterday, and a few times before. I have never gotten a hard brick from it. With he crummy battery life of the atrix, surely this scenario would have been discussed around here before... if it was true. I think its likely he was toying around with things and screwed it up. Perhaps upgrading to Gingerbread, and then trying to downgrade via SBF.
Bender B. Rodgriguez said:
I'm on stock GB, rooted and unlocked and drained my battery down to 0 yesterday, and a few times before. I have never gotten a hard brick from it. With he crummy battery life of the atrix, surely this scenario would have been discussed around here before... if it was true. I think its likely he was toying around with things and screwed it up. Perhaps upgrading to Gingerbread, and then trying to downgrade via SBF.
Click to expand...
Click to collapse
This is exactly what I think he was doing. You mean the only way to get a hardbrick is to downgrade the wrong SBF?
josuetenista said:
This is exactly what I think he was doing. You mean the only way to get a hardbrick is to downgrade the wrong SBF?
Click to expand...
Click to collapse
I'm not an expert authority on the subject , but from what I have read on here so far.. It seems that way
From what I have read on here after upgrading to 4.5.91 SBF flashing anything lower than 4.5.91 will hard brick the device.
Also from this thread
http://forum.xda-developers.com/showthread.php?t=1182871
Note the warning
AFTER GET THE BOOTLOADER UNLOCK YOU CAN ONLY FLASH BY RSD SBF'S WITH "PUDDING" FOR NOW ON, SO IN OTHER WORDS BE CAREFULLY WHEN YOU USE RSD AFTER "UNLOCKED" BOOTLOADER
So I am highly skeptical that simply draining the battery would cause a hard brick. It seems more likely we wanted to play around with the cool features of his new phone and did something stupid.
Related
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...
Ok so i don't know what happen but my phone now says Failed to Boot 4 Starting RSD Mode
What i want to know if i use the SBF for 1.2.6 will it brick my phone ? I see people saying just use that one and then upgrade after that, but i do not want to take the chance of bricking my phone.
So i hope somebody can help
Im assuming youve already unlocked bootloader. Dont use sbf to flash anything. Use recovery or fastboot.
I voided my warranty.
pukemon said:
Im assuming youve already unlocked bootloader. Dont use sbf to flash anything. Use recovery or fastboot.
I voided my warranty.
Click to expand...
Click to collapse
Well the problem is i did try fastboot and when i did that it still did not work and it also REMOVED fastboot..... so now i dont have that as a option
I found this http://forum.xda-developers.com/showthread.php?t=1181932<br /><br />I
and it says im safe to do that one beings it was the same as what i had on my phone before this happended, but im just not sure
If you cant boot into fastboot it may be hardbricked. If rsd doesnt recognize your phone, youre screwed. If it does, cross your fingers and hope for the best.
I voided my warranty.
pukemon said:
If you cant boot into fastboot it may be hardbricked. If rsd doesnt recognize your phone, youre screwed. If it does, cross your fingers and hope for the best.
I voided my warranty.
Click to expand...
Click to collapse
RSD does recognize it and i heard as long as its the latest OS im doing i should be fine but im not sure if the link i posted is the most latest.
Well, read, reread and try to find a couple of threads or better yet experienced members that can help. I try to avoid situations that can possibly get you in a predicament like this.
I voided my warranty.
It all depends if you have "burned the fuse" or not. I can not tell you how to check that with 100% certainty, but if you have EVER flashed/downloaded/used any official update from att or motorola for version 2.3.4 then you have burned the fuse most likely. If that is the case then NEVER flash any older version or you will kill your phone. If you are sure you have never used any official version and only used versions from people that know what they are doing (e.g. Kenn's or fruit cake just to name two) then you can flash whatever you want....but if you are not 100% sure the outcome is on your head.
The safe road would be is if you can get into fastboot?? If so then load cwm recovery with fastboot then load the 2.3.4 fruit cake.
Tao_Man said:
It all depends if you have "burned the fuse" or not. I can not tell you how to check that with 100% certainty, but if you have ever flashed/downloaded/used any official update from att or motorola for version 2.3.4 then you have burned the fuse most likely. If that is the case then NEVER flash any older version or you will kill your phone. If you are sure you have never used any official version and only used versions from people that know what they are doing (e.g. Kenn's or fruit cake just to name two) then you can flash whatever you want....but if you are not 100% sure the outcome is on your head.
The safe road would be is if you can get into fastboot?? If so then load cwm recovery with fastboot then load the 2.3.4 fruit cake.
Click to expand...
Click to collapse
I did use the OTA! ugh
But if i use this SBF http://forum.xda-developers.com/showthread.php?t=1181932<br /><br />I should i not be ok beings its the latest OS for the atrix which is the one i had.
And i tried fastboot and after doing that i do not have fastboot anymore :-/
Sigh i just dont know what to do
I used the OTA but even if i use
RivKristopher said:
I did use the OTA! ugh
But if i use this SBF http://forum.xda-developers.com/showthread.php?t=1181932<br /><br />I should i not be ok beings its the latest OS for the atrix which is the one i had.
And i tried fastboot and after doing that i do not have fastboot anymore :-/
Sigh i just dont know what to do
I used the OTA but even if i use
Click to expand...
Click to collapse
If you did an OTA *official* update, never use an .SBF except to flash a radio ever again. If you do you RISK hard bricking, period. Sorry man, I know it sucks. I can tell you that I have done an OTA to 2.3.4 and then flashed the 2.3.4 SBF and was fine, but then again, it may not work like that for everyone. I now use fruitcakes even if it's to get back to stock 2.3.4, it's just safer. fruitcakes can be found here http://forum.xda-developers.com/showthread.php?t=1163009
Phalanx7621 said:
If you did an OTA *official* update, never use an .SBF except to flash a radio ever again. If you do you RISK hard bricking, period. Sorry man, I know it sucks. I can tell you that I have done an OTA to 2.3.4 and then flashed the 2.3.4 SBF and was fine, but then again, it may not work like that for everyone. I now use fruitcakes even if it's to get back to stock 2.3.4, it's just safer. fruitcakes can be found here http://forum.xda-developers.com/showthread.php?t=1163009
Click to expand...
Click to collapse
How are fruitcakes loaded through RSD Lite as well ?
Fruitcakes are not .sbf files because they do not need to be. They don't contain the amount of data a .SBF would, usually just system and necessary files. They are flashed with CWM *clockwork recovery mod*, as a .zip file. This makes it a ton easier and the chances of hard bricking your phone are almost zilch. CWM for unlocked bootloaders can be found here http://forum.xda-developers.com/showthread.php?t=1204500
fruitcake is cwm, so if you can not get cwm/recovery to work your only option it seems is to flash the offical 2.3.4 sbf and ONLY the 2.3.4 one, do not use an older version.
once you flash 2.3.4 then you should then be able to get your phone opened up again and get cwm working again, and be ok going forward, but never go back older then 2.3.4.
There are hacked sbf files for safe versions of 1.8.3 but I see no reason to go back to 1.8.3 if you are not going to follow the normal upgrade path anyway.
RivKristopher said:
RSD does recognize it and i heard as long as its the latest OS im doing i should be fine but im not sure if the link i posted is the most latest.
Click to expand...
Click to collapse
I have done this before. I believe your right but obviously there is still a risk. I flashed 4.5.91 over 4.5.91 without bricking. Be sure u flash the same OS to lower potential brick.
Sent from my MB860 using XDA App
Sass86 said:
I have done this before. I believe your right but obviously there is still a risk. I flashed 4.5.91 over 4.5.91 without bricking. Be sure u flash the same OS to lower potential brick.
Click to expand...
Click to collapse
^ this. Always the possibility. Kinda the risk we all take when joining and being a part of this community. I actually got mine soft bricked at one point, and thank God I was able to recover. Good luck in all you do, keep the gravy train rollin'
i want to update my unlocked atrix to 2.3.6 but i see that people say that it's gonna brick my phone so there is no way to update it?
my atrix is on stock 2.3.4
unlocked
rooted i guess
career unlocked by unlock code
plz someone help me :S
If you use a fruitcake, you'll be fine. If you wipe all data/system/etc and use the sbf, you will also be fine. The worst I've heard of is a soft brick that takes a hell of a lot of time and effort to fix. So, I'd go with fruitcake if I were you. I did it yesterday, and it worked like a charm.
http://forum.xda-developers.com/showthread.php?p=22552497#post22552497
Fun498 said:
If you use a fruitcake, you'll be fine. If you wipe all data/system/etc and use the sbf, you will also be fine. The worst I've heard of is a soft brick that takes a hell of a lot of time and effort to fix. So, I'd go with fruitcake if I were you. I did it yesterday, and it worked like a charm.
http://forum.xda-developers.com/showthread.php?p=22552497#post22552497
Click to expand...
Click to collapse
what about OTA ? will it hard brick my phone?
soudy1994 said:
what about OTA ? will it hard brick my phone?
Click to expand...
Click to collapse
There is risk that it can
Sent from my MB860 using Tapatalk
Fun498 said:
If you use a fruitcake, you'll be fine. If you wipe all data/system/etc and use the sbf, you will also be fine. The worst I've heard of is a soft brick that takes a hell of a lot of time and effort to fix. So, I'd go with fruitcake if I were you. I did it yesterday, and it worked like a charm.
http://forum.xda-developers.com/showthread.php?p=22552497#post22552497
Click to expand...
Click to collapse
Do you still have that file and can you post it some where?
The file you linked to is not valid anymore and I'm in desperate need to get it.
Thanks for any help
there is no other way? cuz i never used adb before and i'm afraid i will do something wrong
c'mon guys i need help
A few pages later on the new link is posted. I forget exactly where. It's a mediafire link if I remember correctly. And I wouldn't risk a hard brick if I were you. I flashed a SBF to return my broken phone back to Motorola and attempt warranty, but the phone was useless either way. It worked, but I had to wipe nearly every partition. Please don't risk. Fruitcake is proven
this thread isn't TOO dead
I thought there was a way to officially update the atrix to 2.3.6 since that is the official version O/S it supports?
Just picked one up yesterday and it has 2.3.4
redking117 said:
this thread isn't TOO dead
I thought there was a way to officially update the atrix to 2.3.6 since that is the official version O/S it supports?
Just picked one up yesterday and it has 2.3.4
Click to expand...
Click to collapse
Yeah I just went into "about phone" and hit update... what's wrong with that?
Can't you still root 2.3.6?
If your phone is working fine now do yourself a favor and leave it alone. OTA update has caused many problems like killing wifi and many people have had problems playing with roms and you can't go back. This is good advice.
Sent from my MB860 using XDA
I was subscribed to this and just want to add my data point:
on unlocked (bootloader) phone ("Unlocked" printed on boot screen), upgraded to 2.3.6 over the air. This caused Unlocked to disappear from boot screen but I believe I was still technically unlocked. I went through the unlock process again just to be safe. which put "unlocked" back on boot screen, then unrooted by normal flash recovery method, and running fine an dandy all along
I did have a problem with a bad sim card previously, which made it seem like 2.3.6 was a problem, but it is not, for me at least.
I'm very familiar with Samsung and Odin, but Motorola stuff its confusing as hell. I've got a Photon now (and my ET4G). I've been reading through the stickies and the general / Q&A section and can't seen to find a definitive answer to a few questions...
1. I am 2.3.4 running 4.5.1A-1_SUN-198_6. What is the latest root method?
2. Do I need an unlocked bootloader to flash roms and kernels?
3. Any fix for the random "sleep of death" without updating to 2.3.5?
Thanks in advance for any help you all can give!
- Z
zzelinka said:
I'm very familiar with Samsung and Odin, but Motorola stuff its confusing as hell. I've got a Photon now (and my ET4G). I've been reading through the stickies and the general / Q&A section and can't seen to find a definitive answer to a few questions...
1. I am 2.3.4 running 4.5.1A-1_SUN-198_6. What is the latest root method?
2. Do I need an unlocked bootloader to flash roms and kernels?
3. Any fix for the random "sleep of death" without updating to 2.3.5?
Thanks in advance for any help you all can give!
- Z
Click to expand...
Click to collapse
Funny because Samsung's are the complicated ones. All rooting info is listed in development section. One click root should work.
And yes you must of course unlock the bootloader to do any of that.
Sleep of death? Heard of it from like two random people. Never had it happen.
Sent from my SGH-I777 using XDA
zzelinka said:
I'm very familiar with Samsung and Odin, but Motorola stuff its confusing as hell. I've got a Photon now (and my ET4G). I've been reading through the stickies and the general / Q&A section and can't seen to find a definitive answer to a few questions...
1. I am 2.3.4 running 4.5.1A-1_SUN-198_6. What is the latest root method?
2. Do I need an unlocked bootloader to flash roms and kernels?
3. Any fix for the random "sleep of death" without updating to 2.3.5?
Thanks in advance for any help you all can give!
- Z
Click to expand...
Click to collapse
if you are familiar with odin then its gunna be a breeze, tars = sbf's, and odin = rsd lite. if you bork something youve gutta get into the proper mode (download mode = rsd mode) load up rsdlite and add the sbf in and click start.
shabbypenguin said:
if you are familiar with odin then its gunna be a breeze, tars = sbf's, and odin = rsd lite. if you bork something youve gutta get into the proper mode (download mode = rsd mode) load up rsdlite and add the sbf in and click start.
Click to expand...
Click to collapse
Cool. I am contemplating just updating to the newest update and not needing with anything for now. I pretty much bought it to use for my $59.99 lapdock. I actually bought two off Craigslist for $230. They are both pretty much brand new and came with original boxes, etc.
I'm still on the fence. It randomly shuts off and won't turn back on without a battery pull. Its frustrating as hell. Its done it probably 5-10 times tonight alone, and tonights the first night I've had it! I've read that updating to the newest system update takes care of the problem.
- Z
na7q said:
Funny because Samsung's are the complicated ones. All rooting info is listed in development section. One click root should work.
And yes you must of course unlock the bootloader to do any of that.
Sleep of death? Heard of it from like two random people. Never had it happen.
Sent from my SGH-I777 using XDA
Click to expand...
Click to collapse
It just seems like its so much more complicated. Seems like I can brick my phone more easily with all this Moto software.
- Z
zzelinka said:
It just seems like its so much more complicated. Seems like I can brick my phone more easily with all this Moto software.
- Z
Click to expand...
Click to collapse
I urge you not to take the 2.3.5 as if it doesn't fix your sleep of death, there is literally no way to get it off your phone. Our stuff only seems a bit confusing because there is an extra step in there (unlocking) that you people don't have to contend with. Also, we lack a definitive AIO that does everything within one program. It takes a bit of getting used to but as shabby said, the concept is generally the same and there are simple guides for each step.
-Root using torpedo method (aio will probably work but torpedo never fails)
-unlock bootloader
-install a recovery (twrp is fine but you're probably used to cwm)
-flash yo sheet
Acvice said:
I urge you not to take the 2.3.5 as if it doesn't fix your sleep of death, there is literally no way to get it off your phone. Our stuff only seems a bit confusing because there is an extra step in there (unlocking) that you people don't have to contend with. Also, we lack a definitive AIO that does everything within one program. It takes a bit of getting used to but as shabby said, the concept is generally the same and there are simple guides for each step.
-Root using torpedo method (aio will probably work but torpedo never fails)
-unlock bootloader
-install a recovery (twrp is fine but you're probably used to cwm)
-flash yo sheet
Click to expand...
Click to collapse
Werd. Was there ever a fix for sleep of death?
Do not update it with ota.
Flash 198_7 sbf and then flash only locked bootloader from 2.3.4 sv1 custom sbf thread.
It should solve the problem.
peetr_ said:
Do not update it with ota.
Flash 198_7 sbf and then flash only locked bootloader from 2.3.4 sv1 custom sbf thread.
It should solve the problem.
Click to expand...
Click to collapse
I'll check it out. Thanks for the info!
- Z
peetr_ said:
Do not update it with ota.
Flash 198_7 sbf and then flash only locked bootloader from 2.3.4 sv1 custom sbf thread.
It should solve the problem.
Click to expand...
Click to collapse
I saw the SV1 Locked Bootloader.sbf.zip but no 198_7 file. Am I missing something obvious. I probably am
EDITED: I'm a moron. Found it on Loikifish's site...
One more question, your phone is unlocked or locked, when the sleep of death problem occurs?
peetr_ said:
One more question, your phone is unlocked or locked, when the sleep of death problem occurs?
Click to expand...
Click to collapse
It's unlocked. Totally stock, nothing on it. No apps, nada. Just takes a nap on me and never wakes up... I switched back to my ET4G for now. At least until I can get the sleep of death figured out. Any help would be greatly appreciated. Gonna sell one of my MoPho's and maybe the second one w/ my lapdock if I figure out what to do about it. I don't want to pay to get a replacement either....
- Z
Ok so do what I wrote before, that should solve the problem an you will stay unlocked.
Actually you can try, that just flashing 198_7 sbf and not unlocking, will solve the problem.
I mistyped. It's LOCKED. Should I still just flash the 198 and the locked only?
EDIT: Shabby's AIO worked and I'm thinking about unlocking the bootloader. I can't remember if I saw somewhere where I can retain 4G with unlocking the BL. I can't seem to find it now...
Yes, if it's 198_6 now, you can flash 198_7 sbf, so that 2.3.5 update won't bother you and unlock only with bootloader, not derpunlock.sbf.
Tell me, if that helped with those deaths.
So I did an expirement to test a theory... I activated my Photon on my line the day before yesterday. I had a sleep of death if I let the phone sit too long (maybe 20-30 minutes). I was in good radio areas. I took the Photon off my line and let it sit to see if it would go to sleep and not wake up.
Guess what? I left it on for 12+ hours unattended and when I went to turn it on... No sleep of death! I'm going to put it back on my line and see if it sleeps hard again. I think we can then say the problem is most likely some sort of radio related. Am I correct?
- Z
It is possible. You could try to find out where is the problem on yours.
I only know, that one man had this problem everytime he tried to unlock his phone with derpunlock.sbf. When he flashed full 198_7 sbf, everything was fine. Once he tried to unlock different way, that sleep of death was gone.
But this looks like the cause of your problem could be somewhere else.
peetr_ said:
It is possible. You could try to find out where is the problem on yours.
I only know, that one man had this problem everytime he tried to unlock his phone with derpunlock.sbf. When he flashed full 198_7 sbf, everything was fine. Once he tried to unlock different way, that sleep of death was gone.
But this looks like the cause of your problem could be somewhere else.
Click to expand...
Click to collapse
I unlocked using the derpunlock and fastboot method for CWM. It went off without a hitch. Switched back to the Photon to see if the SOD's still occur. I'll keep this thread updating to see if the problem gets resolved. Thanks for the help!
Many helpful people here .
Thanks to all, I might get a photon soon
Buttery Smooth THS15 Deviled
lord dredd said:
Many helpful people here .
Thanks to all, I might get a photon soon
Buttery Smooth THS15 Deviled
Click to expand...
Click to collapse
We try
Hello guys!
I have troubles unlocking my Atrix for a while........
I am rooted with 2.3.4/4.5.91 AT&T stock version.
When I try to unlock my device I get OEM Unlock is not implemented....
Now I know that this is due to the fact that the bootloader is not unlockable. That's why I try to flash the sbf file with the one that is unlockable but this is where i actually fail...............
When I try to Flash the phone with RSD Lite (I have tried with both 4547-fix-try2.sbf and with the big one 1.4GB) it goes to 100% when the phone is suppose to reboot. The phone actually reboots but get stuck at the MOTO LOGO while the RSD Lite gives me the ERROR Unable to Re-enumerate something.... Even if i w8 an hour is still dosnt boot until i pull off the battery. Then my phone starts normaly.........
I have tried to go into fastboot after the freez and try the fastboot oem unlock but still I get the OEM Unlock is not implemented.....
I guess that the whole reason for not unlocking the phone is that I am unable to flash the sbf file.
I want to point out that I have all drivers installed and working correctly.
Also I am unable to Install 2.3.6 OTA Update. It downloads it from the servers and when the phone reboots it gets the triangle mark and unable to update then loads normally .....
So everything points out to not being possible to update sbf...
I am asking for any solution or sugestions since I have tried everything on the forums... I love the phone it's been surving me good for 1 and a half year already. I am not afraid of breaking it since it had its times. Only newer version would save it from replacement (tried of that laggy blur interface....)
PS: Thats wierld phone i cant even hardbreak....
I would be realy happy if someone can help ... ;(
Noone ;(
you've got yourself a blocked bootloader. No one has been able to get passed it. Unfortunately you can't unlock it.
Sorry bro... You got unlucky and got an atrix with an impossible boot lock. There is one method i know of.. It hard bricks so many phones it wasnt worth the devs time to finish.
Dohhh
Well may u link the thread so I can see it
Would be interesting to me..
pre4speed said:
you've got yourself a blocked bootloader. No one has been able to get passed it. Unfortunately you can't unlock it.
Click to expand...
Click to collapse
I am not sure if this is true. I have a permalocked boot loader and only know this to be a problem on 4.5.141. I may be wrong but I would keep at it.
But you do seam to get the same error on phone. It is strange that you cannot OTA. I was locked on 4.5.141 and just took the soak test OTA to I think it was 4.5.145 or something like that
affiatic said:
I am not sure if this is true. I have a permalocked boot loader and only know this to be a problem on 4.5.141. I may be wrong but I would keep at it.
But you do seam to get the same error on phone. It is strange that you cannot OTA. I was locked on 4.5.141 and just took the soak test OTA to I think it was 4.5.145 or something like that
Click to expand...
Click to collapse
Have you tried to unlock again after the OTA? Would be interesting to know if its unlockable now.
pre4speed said:
Have you tried to unlock again after the OTA? Would be interesting to know if its unlockable now.
Click to expand...
Click to collapse
Yes tried and failed. Same error message as 4.5.141.
affiatic said:
Yes tried and failed. Same error message as 4.5.141.
Click to expand...
Click to collapse
Damn Motorola. Wont give ice, wont give you the options to make your phone better. Makes me double glad I went to Samsung.
pre4speed said:
Damn Motorola. Wont give ice, wont give you the options to make your phone better. Makes me double glad I went to Samsung.
Click to expand...
Click to collapse
On the galaxy note here. Selling atrix Friday. Held off to try the soak. Nothing great in it so selling.
My wife is keeping her atrix on cm10 for now.
affiatic said:
On the galaxy note here. Selling atrix Friday. Held off to try the soak. Nothing great in it so selling.
My wife is keeping her atrix on cm10 for now.
Click to expand...
Click to collapse
Im not selling mine. Gonna keep as a backup. I've actually got 2 atrixes, one is my bf and I keep the other for the backup to his and in case my Sammy (skyrocket) dies. Its not a bad phone just the manufacturer has burned too many bridges over wide rivers.
pre4speed said:
Im not selling mine. Gonna keep as a backup. I've actually got 2 atrixes, one is my bf and I keep the other for the backup to his and in case my Sammy (skyrocket) dies. Its not a bad phone just the manufacturer has burned too many bridges over wide rivers.
Click to expand...
Click to collapse
Just put cm10.1 jelly beer on note today. Very smooth and fully functional. I recommend. Sorry to OP for off topic
affiatic said:
Just put cm10.1 jelly beer on note today. Very smooth and fully functional. I recommend. Sorry to OP for off topic
Click to expand...
Click to collapse
I agree, we got a little off topic.