So tired of searching for this file. Everyone keeps saying i need to find 2.3.6 .spf for RSD to unlock bootloader but all th elinks are broken. Can anyone get me a link to the 2.3.6 SPF please?
att atrix 4g 2.3.6
I foud 2.3.4....
http://www.filefactory.com/f/89f588286a560e39/
will this work? top one..or do i need 2.3.6 if im currently 2.3.6?..
edit: well top one isnt right... i dont know wich of these is for ATT US version heh...theres a 2.3.6 but its for Bell ...
Here ya go. das8nt is a big help here on xda and on the atrixforums. http://www.das8nt.com/sbffiles.html Make sure you got the motorola drivers, read the guide a couple times before attempting if you haven't used RSDlite before. Don't downgrade, use the version SBF that your on now currently. Downgrading will result in a hard brick! If you're looking to unlock your bootloader you need the pudding file here Unlocker for 1.8.3 and 4.5.91 ATT firmwares. It worked for me when I unlocked on 2.3.4, should work on 2.3.6.
smenes said:
Here ya go. das8nt is a big help here on xda and on the atrixforums. http://www.das8nt.com/sbffiles.html Make sure you got the motorola drivers, read the guide a couple times before attempting if you haven't used RSDlite before. Don't downgrade, use the version SBF that your on now currently. Downgrading will result in a hard brick! If you're looking to unlock your bootloader you need the pudding file here Unlocker for 1.8.3 and 4.5.91 ATT firmwares. It worked for me when I unlocked on 2.3.4, should work on 2.3.6.
Click to expand...
Click to collapse
Got it! Thanks! Now for some reason adb shell isnt working like it was yesterday. Shrug* sigh ideas?
After you flashed the pudding, did you boot to fastboot and issue the 'fastboot oem unlock' command to unlock the bootloader as described here? Do you have root? what do you get when you type 'adb devices' ? You have usb debugging enabled while booted in android?
smenes said:
After you flashed the pudding, did you boot to fastboot and issue the 'fastboot oem unlock' command to unlock the bootloader as described here? Do you have root? what do you get when you type 'adb devices' ? You have usb debugging enabled while booted in android?
Click to expand...
Click to collapse
Device says unlocked. Im good there. When i install a recovery per the suggested install it says written but when i try to go to it i get the aNDROID sitting there with a yeild ! sign, so i have to reboot....somethings wrong cause when i try to get CWM to install it for me from the phone itself it says error flashing... any ideas?
EDIT : i didnt think about renabling debugging one minute
not sure that did anything.
Edit: i only had to install super user lol thanks for all ur help
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
Failed to boot 2
Starting RSD mode.
I tried to flash the new Ninja Rom from the Gingerblur rom. I am now stuck on the dual core screen with the message above stuck there. Someone please help, I looked through the forms but it seems like I should be able to get into recovery still, which I cannot... If you need any other info please let me know....
rp2gardner said:
Failed to boot 2
Starting RSD mode.
I tried to flash the new Ninja Rom from the Gingerblur rom. I am now stuck on the dual core screen with the message above stuck there. Someone please help, I looked through the forms but it seems like I should be able to get into recovery still, which I cannot... If you need any other info please let me know....
Click to expand...
Click to collapse
Were you unlocked before trying to flash Ninja rom?
unlocked... no at least I dont think? Obviously I was rooted but unlocked i dunno...
That is why, your bootloader has to be unlocked.
Sent from my MB860 using XDA Premium App
rp2gardner said:
unlocked... no at least I dont think? Obviously I was rooted but unlocked i dunno...
Click to expand...
Click to collapse
Ah ok... gingerblur was a pseudo-rom... made before we were able to install custom roms because we couldn't unlock our bootloader. That changed last month when devs figured it out and thus the newer custom roms. To install them you need to unlocked your bootloader.
Please read this thread for information on how to unlock
http://forum.xda-developers.com/showthread.php?t=1136261
Now, since you're already softbricks, running that may not work right now. BUT it's start.
My suggestion- read the thread, follow the instructions and see if that gets you to boot up properly after running the oem unlock.
If not, then download a fresh stock 1.8.3 SBF form the development thread and RSD flash that.
Ok thank you for your help, will post a question if I come to one. How would I download the stock 1.8.3 SBF if I am stuck on the boot screen? Im feeling like Im in over my head, Paypal donation to anyone who can walk me through this....
rp2gardner said:
Ok thank you for your help, will post a question if I come to one. How would I download the stock 1.8.3 SBF if I am stuck on the boot screen? Im feeling like Im in over my head, Paypal donation to anyone who can walk me through this....
Click to expand...
Click to collapse
Stock SBFs are in the development forum as well.
I guess first things first, do you have the tools needed
Do you have or know how to use RSD?
How about Fastboot?
Just downloaded RSD lite and flashed the SBF..
"Open and extract the Fastboot package from above" is the step I am on.. Not sure where to go from here.
The phone rebooted to the same screen that it was at before with the error message but says PASS in RSDLite for the sbf flash
rp2gardner said:
Just downloaded RSD lite and flashed the SBF..
"Open and extract the Fastboot package from above" is the step I am on.. Not sure where to go from here.
The phone rebooted to the same screen that it was at before with the error message but says PASS in RSDLite for the sbf flash
Click to expand...
Click to collapse
Which SBF? The pudding/unlock?
If you flashed the pudding SBF, then you need to do the fastboot steps next.
Did you download and unzip the fastboot package to your computer?
I did, I just dont know what to do with fastboot. Do I run it or what?.. THANKS A TON BY THE WAY...
Ok, I still have the failed to boot 2, but I am now getting the Starting Fastboot protocol support. I dont understand this step..
Type the following command:
fastboot oem unlock
rp2gardner said:
I did, I just dont know what to do with fastboot. Do I run it or what?.. THANKS A TON BY THE WAY...
Click to expand...
Click to collapse
let's say you saved and extracted the fastboot files to c:\fastboot
then you have to open up CMD (start - run - cmd )
then cd to the directory it's saved (in this example c:\fastboot )
Now you have to get your phone into fastboot mode (directions are in the link), but in short, as you turn on your phone, hold the down button. THen it should say fastboot, then hit volume up, should say entering fastboot
Then back on computer in the command window
while your in the fastboot directory
type the oem unlock command (specific command in the instruction).
after it's all done, type fastboot reboot.
I have to go now for a while, but if all that doesn't work. I suggest flashing via RSD the 1.83 SBF with Pudding built in.
The download is in the pudding thread near the top "1. All phones If you have unlocked then try to use 2.3.4 update zip from Motorola servers, then revert back to a "pre-unlock" version(1.8.3 or earlier on ATT) you will get bricked! Do not use the OTA via experimental servers and revert to older versions WITHOUT pudding preinstalled in your sbf.
ATT ONLY Get your 1.8.3 with pudding from gitbrew or multiupload."
I cant figure out where to type the command in (fastboot oem unlock) i have the screen that came up when i located the fastboot. It has a list of commands, but nothing about oem unlock...
rp2gardner said:
I cant figure out where to type the command in (fastboot oem unlock) i have the screen that came up when i located the fastboot. It has a list of commands, but nothing about oem unlock...
Click to expand...
Click to collapse
Is your phone in fastboot mode and connected?
All you gotta do is just type the command in the command window
C:\fastboo\ fastboot oem unlock
Hello All,
I'm new here, so I'm not exactly sure if this is the correct forum to be posting this, but here's my question:
When I attempt to unlock my bootloader using fastboot and the "fastboot oem unlock" command, it simply returns:
Code:
... INFOOEM unlock is not implemented
OKAY [ 0.001s]
Has anyone else gotten this message or anything like it? Or am I doing something wrong?
I'm rooted and running the 4.5.91 (ATT) update, and I updated from Gingerblur 3.5 using the PC update program.
The only way to unlock bootloader at this time is flashing pudding and then running fastboot OEM commands
SevenandForty said:
Hello All,
I'm new here, so I'm not exactly sure if this is the correct forum to be posting this, but here's my question:
When I attempt to unlock my bootloader using fastboot and the "fastboot oem unlock" command, it simply returns:
Code:
... INFOOEM unlock is not implemented
OKAY [ 0.001s]
Has anyone else gotten this message or anything like it? Or am I doing something wrong?
I'm rooted and running the 4.5.91 (ATT) update, and I updated from Gingerblur 3.5 using the PC update program.
Click to expand...
Click to collapse
Sent from my MB860 using XDA App
Really? Huh- I found that fastboot method on this website
briefmobile(dot)com/how-to-unlock-the-atrix-4g-bootloader
It says to use the command prompt to run fastboot and unlock it- I'm not sure if this was disabled or something, because it seems to have worked for most people on the 2.3.4 beta.
SevenandForty said:
Oh, really? I found that fastboot method on this website
briefmobile(dot)com/how-to-unlock-the-atrix-4g-bootloader
It says to use the command prompt to run fastboot and unlock it- I'm not sure if this was disabled or something, because it seems to have worked for most people on the 2.3.4 beta.
Click to expand...
Click to collapse
if you're running the ota update, then you don't have an unlockable bootloader. you need to flash a pudding sbf to get one, which you can find instructions to on either the general forum or the dev forum.
Oh, I see. Thanks!
same problem
I also have the same problem but I have a stock 2.3 atrix does it make a difference?
I had to flash the 4.5.91 pre root sbf Via rsd lite then run that fastboot command.
Sent from my MB860 using XDA App
You need to flash the unlock sbf first. Just remember that if you're on 2.3.4, after you flash the sbf, the phone will reboot and soft brick - that's normal. Be ready to fastboot flash RomRacer's CWM recovery, and have the two 2.3.4 Fruitcake builds on your external sdcard beforehand.
Once you've flashed RomRacer's recovery successfully, pull the battery, put in your SIM and sdcard again, boot into recovery, and then install both fruitcake builds.
After that, your phone will boot and you can root it at your leisure.
SevenandForty said:
Hello All,
I'm new here, so I'm not exactly sure if this is the correct forum to be posting this, but here's my question:
When I attempt to unlock my bootloader using fastboot and the "fastboot oem unlock" command, it simply returns:
Code:
... INFOOEM unlock is not implemented
OKAY [ 0.001s]
Has anyone else gotten this message or anything like it? Or am I doing something wrong?
I'm rooted and running the 4.5.91 (ATT) update, and I updated from Gingerblur 3.5 using the PC update program.
Click to expand...
Click to collapse
Are you flashing the .sbf first? If not, that is your problem or you have the same luck as me.. One or the other. Anyway, this is how I fixed mine:
I had this issue too.. Very irritating. I was using Linux to get my phone unlocked. When I went home from work, I tried again on windows 7 this time using RSDLite. It kinda worked. RSDLite got to 98%, the phone crashed and the flash status displayed failed. However, at 98%, the only thing left to do was for the phone to turn back on and verify the flashed image as far as I was concerned. Anyway, the phone said "Operating system not found" and went into fastboot mode from there. I felt I had nothing to lose by moving on. I issued a fastboot oem restore, and was able to get my code. I then reissued the command and typed in the whole code as windows wouldn't let me copy/paste from the command prompt (thanks Bill..). After doing this and pressing enter, my bootloader was nice and unlocked in about half a second. I rebooted using fastboot, and it locked up, so a battery pull got me working just fine. Hope this helps someone.
same problem
i have the same problem
1. i did use the sdf. but in the end it says FAIL in RSD
2. cant continue
3. still searching for answer:crying:
---------- Post added at 06:18 PM ---------- Previous post was at 06:07 PM ----------
hammerlock13 said:
Are you flashing the .sbf first? If not, that is your problem or you have the same luck as me.. One or the other. Anyway, this is how I fixed mine:
I had this issue too.. Very irritating. I was using Linux to get my phone unlocked. When I went home from work, I tried again on windows 7 this time using RSDLite. It kinda worked. RSDLite got to 98%, the phone crashed and the flash status displayed failed. However, at 98%, the only thing left to do was for the phone to turn back on and verify the flashed image as far as I was concerned. Anyway, the phone said "Operating system not found" and went into fastboot mode from there. I felt I had nothing to lose by moving on. I issued a fastboot oem restore, and was able to get my code. I then reissued the command and typed in the whole code as windows wouldn't let me copy/paste from the command prompt (thanks Bill..). After doing this and pressing enter, my bootloader was nice and unlocked in about half a second. I rebooted using fastboot, and it locked up, so a battery pull got me working just fine. Hope this helps someone.
Click to expand...
Click to collapse
sir, could you kindly pls. give the codes step by step, it will help a lot, i can not use my Atrix Thanks in Advance
OEM unlock is not implemented
I also have this issue
I am desperately looking for a solution without luck for my rooted
Atrix 4G Buld 4.5.2A
GB 2.3.4
If someone can point me to a solution I will be very glad
Thanks
Eli
i'm in the same situation....
help please
FIXED it and now my phone is unlocked
you have to flash the phone with RSD this file http://diamantephoto.com/IHOP_Bell.rar
and rerun the command to give you the phone ID
hope it helps for you
Hello everyone. I am new to the world of android, but I'm a quick enough learner. Here is my specific problem:
I have an AT&T Atrix 4g. It is currently superuser rooted. It is currently running Android ROM 2.3.4.
Shortly after rooting the device, I downloaded ROM Manager and successfully installed through the application Clockwork Recovery. I tried to select the option to back up the current ROM (the stock android) on my SD card.. however, during the load screen, I got an error message stating
"Failed to boot 2
Starting RSD protocol support"
So doing some research, I came upon the conclusion that the reason I can't backup or really do anything with ROMs is that I needed an unlocked bootloader.
I went to Atrix4ghacks and followed the instructions on how to unlock bootloader and install permanent recovery.
This is the critical part: When I entered into the command prompt "fastboot oem unlock", instead of proceeding normally I got the return message:
"OEM unlock is not implemented"
Again, did a google search and read that Android 2.3.4 on Atrix 4g does NOT allow unlocked bootloaders.
So, the questions that I have that result from this are:
1.) Can someone here confirm that, in fact, I am unable to unlock the bootloader on my phone?
2.) If so, is there a viable workaround that is both reasonably safe and not overly complicated? Please note that I have no backup in case something goes wrong, leading me to
3.) Is there a way to backup my stock 2.3.4 ROM without an unlocked bootloader?
4.) Can I revert safely to an older android version that supports unlocked bootloaders?
5.) Can you actually install new ROMs without an unlocked bootloader?
6.) Am I totally screwed?
HUGE THANKS to anyone who actually bothered reading this, and even more thanks to anyone who can answer/point me in the right direction. Much appreciated!!!
thats becouse u havent flashed yet the bootloader ill give a post related to this and esay way to do it
http://forum.xda-developers.com/showthread.php?t=1182871
and you CANT go back to 2.2 or 2.3 u can hard brick your phone
tufo430 said:
thats becouse u havent flashed yet the bootloader ill give a post related to this and esay way to do it
http://forum.xda-developers.com/showthread.php?t=1182871
and you CANT go back to 2.2 or 2.3 u can hard brick your phone
Click to expand...
Click to collapse
Thanks a ton for that link. I'm sorry to ask once again, but I'm very wary of possibly bricking my phone... so I must ask: Is your solution possible with 2.3.4? Or will the phone softbrick?
If you did the Over The Air (OTA) update to 2.3.4 then yes your phone will softbrick after flashing the bootloader. Re-enter fastboot and issue the unlock commands and everything will be fine when you reboot.
Hi ,
i have a small problem actually i tried to unlock my bootloader recently , i used the automatic bootloader unlock file but it didn't work, don't know why ,so i tried the fastboot unlock thing..where we have to put unique id code, n put commands fastboot oem unlock code my phone when doing it says ur phone is unlocked but when i on my phone the boot screen doesn't show unlock symbol ....i heart that unlock symbol should be showed...i think i am missing some steps or like that...can u guys help me out to solve it....my phone is working fine now but i am confused is my bootloader unlock or not?????
tris_333 said:
Hi ,
i have a small problem actually i tried to unlock my bootloader recently , i used the automatic bootloader unlock file but it didn't work, don't know why ,so i tried the fastboot unlock thing..where we have to put unique id code, n put commands fastboot oem unlock code my phone when doing it says ur phone is unlocked but when i on my phone the boot screen doesn't show unlock symbol ....i heart that unlock symbol should be showed...i think i am missing some steps or like that...can u guys help me out to solve it....my phone is working fine now but i am confused is my bootloader unlock or not?????
Click to expand...
Click to collapse
Did you flash the pudding unlock sbf first, before entering fastboot? If not, see Pudding OP in dev section.
Sent from my CM7 Atrix 4G
Swiftks said:
Did you flash the pudding unlock sbf first, before entering fastboot? If not, see Pudding OP in dev section.
Sent from my CM7 Atrix 4G
Click to expand...
Click to collapse
but in this site http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloaderit says if u r using gingerbread u dont have to flash just can do the fastboot
but i tried to flash the sbf file but RSD AFTER 100%...... my phone just open to normal state n rsd says reboot it manually n results says in process i damn confused
i am using android version 2.3.4 and system version 4.5.74.mbb860.att.en.us
plz help me out
tris_333 said:
but in this site http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloaderit says if u r using gingerbread u dont have to flash just can do the fastboot
but i tried to flash the sbf file but RSD AFTER 100%...... my phone just open to normal state n rsd says reboot it manually n results says in process i damn confused
i am using android version 2.3.4 and system version 4.5.74.mbb860.att.en.us
plz help me out
Click to expand...
Click to collapse
I would grab the "Unlocker for 1.8.3 and 4.5.91 ATT firmwares" from the main Pudding thread: http://forum.xda-developers.com/showthread.php?t=1136261
It's under the Unlock part of the OP (ATT ONLY).
Flash that small sbf file with RSD Lite.
Once finished flashing the unlock sbf file, Reboot, enter fastboot mode then enter the unlock commands.
See if that works.