Hey,
I was on CM7, then I flashed Stock Gingerbread using CWM (Fruitcake, I think), I want to remove root and the "unlocked" sign when booting. I was searching this forum (and the rest of the internet ) for a couple of days and didn't find a solution. Either the links are dead or there is a person threating with hard brick. Does anyone know how to do this safely and has necessary files, please? Thank you in advance.
Wait, what exactly do you want to do?
If you want to just remove the text while the BL and everything else remains unlocked... That is impossible, you cannot do that.
If you want to re-lock your BL... well, that would probably be the only time (apart from when unlocking the BL) when you should reach for a SBF. There is no other known way to re-lock the BL.
Yep, I need to re-lock the BL, to get the phone to factory state (I know it won't actually re-lock the BL, just the sign will disappear). But I didn't find any usable SBF's, everybody is writing about hardbrick or the links are down. I found a couple of US ATT SBF's , but really don't know which one to use, I really don't want to brick my phone
Okay, I found this site with SBF's:
http://www.filefactory.com/f/89f588286a560e39/
I guess this one SHOULD put my phone back to factory state without root access and unlocked sign. Does anyone know, if it's safe? And if it's the only file I need to flash. Thanks
All the SBFs were removed here because they are too dangerous. For that same reason, you won't find many people here who will be willing to help you with them, not even say "yes, this one is good" or "no, don't use this one". It's just too dangerous and nobody wants to take responsibility for other people's phones like that. Not to mention, you failed to give any relevant information on your phone, so even if someone wanted to help, they can't.
What information do you have on mind?
Currently I'm running rooted unlocked stock gingerbread 2.3.4 (System version: 45.31.20.MB860.NonEFIGSRetail.en.EU, Build number: 4.5.2A-74_OLE-31.20).
If flashing SBF is dangerous, is there any method to get back to factory state?
Yes, that would be the information needed.
Flashing a SBF is the only known way to remove the "Unlocked" text while booting; however you will still find very little support here for doing that - like I said, it is too dangerous, things can go wrong too easily.
You can flash a fruitcake to return the system to stock, but the "Unlocked" text will remain.
That's what I was afraid of So no one will tell me: "Yes, with your configuration you can flash this and you'll be fine."
Nevermind, I will send for repair like this (problem with touchscreen - fantom touches, quite common hardware problem on atrixes) and in the worst case I´ll just pay for the repair.
Anyways, thank you for help, I really appreciate it! :good:
People have been known to just flash over the stock firmware and send it in and be fine. A lot of service centers don't really care about the unlocked BL or even a custom recovery.
i think he can remove unlocked sign with flashing motorola logo. if i remember corectly
Sent from my MB860 using xda app-developers app
Nope.
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...
I am reviewing PUDDING information to unlock the bootloader and I have some concerns.
PUDDING Link: http://forum.xda-developers.com/showthread.php?t=1136261
1. This guide posted in PUDDING says your phone must register as NS Flash Olympus and mine is registering (now) as SE Flash Olympus. Why is that? My phone "used" to register as NS Flash Olympus but no longer does and I am concern with any "issues" that may arise in RSD Lite due to that discrepancy.
Is there any way to get my phone to register back as NS Flash Olympus? Does it matter?
Guide: http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
2. I see this post regarding my situation from OTA Gingerbread (official, not the beta that was easily unlocked via the guide) to unlocking the Bootloader via PUDDING:
http://forum.xda-developers.com/showpost.php?p=15953305&postcount=362
While it seems that people are getting by this fine, with my first issue I am skeptical and I also saw this thread that made me a bit more weary of the situation and hard bricking:
http://forum.xda-developers.com/showthread.php?t=1165154
Is this something I should be concerned or worried about? The only note in that thread that concerned me was "If you managed to un-brick:" section.
System Version: 4.5.91.MB860.ATT.en.US
Android Version: 2.3.4
Rooted: No
Please, save yourself time. If you just plan on being rude, flaming, etc...I don't care. I am just attempting to ensure I don't hard brick and the guides do not match exact specs in my situation. If I had a "fraction" of the time available to investigate, work, test, etc I wouldn't be here.
I used this on the official OTA and it worked perfectly: http://forum.xda-developers.com/showthread.php?t=1182871
I had the soft brick error as was to be expected, but just put the phone in fastboot mode and chose option 3 to fix it.
It did reset /data for me unfortunately, so I had to re-setup and reinstall my apps.
jkrohn said:
I used this on the official OTA and it worked perfectly: http://forum.xda-developers.com/showthread.php?t=1182871
I had the soft brick error as was to be expected, but just put the phone in fastboot mode and chose option 3 to fix it.
It did reset /data for me unfortunately, so I had to re-setup and reinstall my apps.
Click to expand...
Click to collapse
Did you share the same problem as my concern #1?
Never even checked to be honest. I had used RSD to flash a few SBFs in the past though for this atrix, so I was not concerned.
Well, in short...I just used the method you posted above -
http://forum.xda-developers.com/showpost.php?p=16520624&postcount=2
Worked just fine. No brick, safe and sound... I really do appreciate the extra info I somehow missed looking around for.
That's it! You just made me realize my problem. After my official update back to stock my phone comes up se flash not nf flash and it does not allow rsdlite or the moto software upgrade to see my phone when connected to pc hence I am unable to unlock again. Please post back if unlock is successful. I am betting its not while coming up se flash but maybe I am wrong.
Sent from my MB860 using Tapatalk
I have a 2.3.4 (45.3.6.MB855.Sprint.en.US) Photon 4g. After reading a bunch of threads, I still want to ask some questions to make sure I'm understanding this all correctly, so I can best decide what I want to do.
I had been putting off rooting, but now I've got this annoying nag screen about upgrading to 2.3.5, and it seems the only way to get rid of the nag screen is to be rooted, right? [EDIT: it's a good month later now. i've actually forgotten what I did to get rid of the nag screen, but it involved finding a file on the part of the system files that gets revealed when you root the phone, and then changing some value in a file from 1 to 0 or vice-versa.]
If I only want to root to have access to the full internal file structure of my phone, I don't need to rom flash, right?[EDIT: right]
Once rooted, I can unroot and upgrade at a later time if some future version comes out that I do want to update to, right? Do I even need to unroot to upgrade if I'm comfortable with never rooting* again and I haven't rom flashed but only rooted? For example, would a 2.3.5 upgrade hurt a rooted 2.3.4 phone or just unroot it?
Rooting will delete everything** and cause me to have to reinstall every app, right? [EDIT: no, it doesn't; bootloader unlocking could though.] If that's true, can I make a backup first that would make reloading apps easy?
What about eFuse? No one's mentioning it as a problem though this older article says it should be.
Type "bad-news-root-crew-the-droid-3-has-a-locked-bootloader" into Google, b/c I can't post hyperlinks as a new user.[EDIT: I dont' know about efuse, but having rooted now, I never ran into a problem caused by it.]
*Actually, the below copy-pasted reply from another thread makes it sound like even after upgrading to 2.3.5, the device can still be rooted, presumably using the photon torpedo method.
"My opinion is do not do the update right now .. It will lock your bootloader.. yes you can root your phone again but thats basically it.. You wont be able the flash any unlocked custom roms"
**This youtube video seems to suggest so: "deleting all yo ****" Go to youtube for qbking77's "How to root the Motorola Photon 4G and get Free Wifi Wireless Hotspot"
If you update to 2.35 you should be able to root. Rooting should not wipe your device. You won't be able to unlock your bootloader. So don't do it. If you must update to 2.35, root first and see if you can find a version of it on these forums with a bootloader that won't permanently lock yours. I think I read a post somewhere about that. Google is your friend.
Sent from my MB855 using xda premium
Really depends on how you intend to use the phone. If you ever want to flash custom kernels as of right now you need to unlock the bootloader. With the update to 2.3.5. right now you cannot unlock your bootloader. The update to 2.3.5. brings really negligible upgrades to the phone and in my opinion the update is really only meant to lock the phone down further.
Rooting does not delete any system files(apps and such) the AIO root seen in the video by QBKing77 prints out deleting all yo ****, shabbypenguin intended this as a joke I think. You can unroot by flashing one of the sbf images floating around.
Hope this helps some.
Thanks for the input JohnH4 and mof9336. My paranoia about the phone getting wiped comes from...
"Warning: Unlocking your phone’s bootloader voids its warranty. It also completely wipes (formats) your Android phone’s internal memory including applications, contacts, SMS and MMS messages etc."
from googling "what-is-bootloader-and-how-to-unlock-bootloader-on-android-phones-complete-guide"
...though I guess "unlocking your phone's bootloader" is not the same thing as rooting.
Exactly. They're two seperate critters.
Sent from my Magical MoPho using xda premium
Hello everyone
I unlocked my Atrix (MB860, NORDICS RETAIL) some months ago and then I installed NottachTrix1.3.1 Rom. The day after the new Rom installation I experienced a lot of stability issues so I flashed the stock SBF file to bring the phone into its original state.
But since that time my phone is working worse than before: it gets very hot sometime and the battery drains much faster, if before with an intense use it worked for more than a 24 hours now with a moderate use if doesn't reach night sometime. This happens even if I flash the SBF file and then I leave all only the original applications of the phone without a restore of the backed-up ones.
I've been reading many articles about Atrix problems till now, but there are so many that it's probably impossible to not get confused, and I haven't been able to find something that helps me to solve mine yet.
Now I have some doubts I would like to ask you:
1- Did I pick up the right sbf file for my phone (the package says MB860, NORDICS RETAIL my sbf file is 1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.1-release-keys-signed-NonEFIGSRetail-EU.sbf)?
2- There can be some components installed by custom rom that may still be working in the device(kernel,filesystem,radio or whatever) also after the sbf file flash and causing the problems I'm experiencing?
Thank you
Bye
Big-Bob said:
Hello everyone
I unlocked my Atrix (MB860, NORDICS RETAIL) some months ago and then I installed NottachTrix1.3.1 Rom. The day after the new Rom installation I experienced a lot of stability issues so I flashed the stock SBF file to bring the phone into its original state.
But since that time my phone is working worse than before: it gets very hot sometime and the battery drains much faster, if before with an intense use it worked for more than a 24 hours now with a moderate use if doesn't reach night sometime. This happens even if I flash the SBF file and then I leave all only the original applications of the phone without a restore of the backed-up ones.
I've been reading many articles about Atrix problems till now, but there are so many that it's probably impossible to not get confused, and I haven't been able to find something that helps me to solve mine yet.
Now I have some doubts I would like to ask you:
1- Did I pick up the right sbf file for my phone (the package says MB860, NORDICS RETAIL my sbf file is 1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.1-release-keys-signed-NonEFIGSRetail-EU.sbf)?
2- There can be some components installed by custom rom that may still be working in the device(kernel,filesystem,radio or whatever) also after the sbf file flash and causing the problems I'm experiencing?
Thank you
Bye
Click to expand...
Click to collapse
i donr know the anwser of the first question.
second no when you flash a sbf you erase everything on the phone so it looks like when you buy it even lock the bootloader again.
maybe one app runing in background or mobile data.
send it to technical support if youre in warranty.
cheers
Thank you lucamibel
lucamibel said:
second no when you flash a sbf you erase everything on the phone so it looks like when you buy it even lock the bootloader again.
Click to expand...
Click to collapse
Oh well it's not really like you said, for example the bootloader unlocking process is not reversible through the sbf file flash, because after it, the "Unlocked" text on the top-left corner is just hidden but if you try to re-take the unlocking procedure when you execute the unlocking command it will say that the device is already unlocked while when you execute it at the first time it unlocks the phone , so there is something that the sbf file flash procedure doesn't recover. I haven't tried to install the rom recovery tool without unlocking the phone yet, I'm try to avoid other dangerous actions on it now.
lucamibel said:
maybe one app runing in background or mobile data.
Click to expand...
Click to collapse
These issues will happen even if I leave the phone with the configuration in the SBF file image, so I would exclude that reason.
lucamibel said:
send it to technical support if youre in warranty.
Click to expand...
Click to collapse
I'm still in warranty, but the phone is unlocked
Bye
Big-Bob said:
Thank you lucamibel
Oh well it's not really like you said, for example the bootloader unlocking process is not reversible through the sbf file flash, because after it, the "Unlocked" text on the top-left corner is just hidden but if you try to re-take the unlocking procedure when you execute the unlocking command it will say that the device is already unlocked while when you execute it at the first time it unlocks the phone , so there is something that the sbf file flash procedure doesn't recover. I haven't tried to install the rom recovery tool without unlocking the phone yet, I'm try to avoid other dangerous actions on it now.
These issues will happen even if I leave the phone with the configuration in the SBF file image, so I would exclude that reason.
I'm still in warranty, but the phone is unlocked
Bye
Click to expand...
Click to collapse
You are correct in saying that the bootloader remains unlocked. Also, if you search the forums I think you will have a very hard time finding anyone who has had a warranty return rejected for an unlocked bootloader. I would get rid of the "unlocked" text and send it in for repair if you need to.
Thanks CaelanT
I think that would probably be the best thing to do. It's being too hard to find a solution by myself.
I've just bring the phone back at its factory status and as soon as it'll restart with the issues I'll send it to the assistance, if they won't matter about the unlocked status it would be only better.
Big-Bob said:
Thanks CaelanT
I think that would probably be the best thing to do. It's being too hard to find a solution by myself.
I've just bring the phone back at its factory status and as soon as it'll restart with the issues I'll send it to the assistance, if they won't matter about the unlocked status it would be only better.
Click to expand...
Click to collapse
sorry i think i dont express well when i said that, i mean it that the "unlocked" cartel hide and you can send it to technical support
cheers
Hey all. I am actually from the Samsung Galaxy W community and since I'm gonna get the Atrix from my mom soon, I thought I should get a little heads up on how to root it and all. However, the guides here (no offense) freaked me out cuz they had lots of warnings and since the phone I use now is really simple to root (flash update.zip and you're rooted), I realised that rooting the Atrix isn't as easy as rooting the W. Thus I consulted my best friend, Google. He gave me this link: http://www.android-advice.com/2012/root-the-motorola-atrix-4g-running-4-5-141/
Is this the proper way to root? If so, then what do I do next? Because my motive for this phone is to install a custom recovery (ClockworkMod if possible) and (50% chance) stop it right there... I will really appreciate all the help I can get. Thank you, Atrix community.
---EDIT---
I got the method of installing the recovery. Now I just need you guys to verify if that is the proper way.
This looks like the well-known preinstall method. Yes, this is the most common (and IMO the most reliable) way to root the Atrix.
However, a common misconception when it comes to the Atrix is that you need root to get custom recovery. Those two probably couldn't be farther apart - one has nothing to do with the other. You not only don't need root to get custom recovery, it is in fact completely irrelevant because it operates on a much lower level. Instead, you need to unlock the bootloader (because fastboot is implemented in the bootloader, and because you need fastboot that isn't locked down), and then you simply flash your custom recovery via fastboot.
Now here's the problem. First, unlocking the bootloader is by far the most risky step of all. To do that you need to flash a piece of code (the unlocked bootloader, also known as pudding) in the most sensitive part of the phone. You screw this up and you got yourself a brick. Second, when you finally do unlock the bootloader, sometimes you'll be left in an unbootable state (the infamous Failed to boot XXX error). No worries, there's a fix for that too (it is called a softbrick btw). Point is, in that case you cannot just install the custom recovery and then "stop there", you'll need to install an OS too. If you prefer to stick to stock firmware, you should go with so-called fruitcakes, which is just stock firmware prepared to be flashed through custom recovery.
Nothing much to worry about though, everything is explained in detail here. You don't need to google or search in other places, everything you need is right here on XDA (in fact it is probably preferred that you stay within XDA instead of trying to follow random procedures from random places). I suggest you start with some basic noob stuff like this and this. (Some of the stuff in there is somewhat outdated, take any version info mentioned with a grain of salt.)
One big point. You will inevitably come across "SBFs" and advices to flash them. SBFs are inherently dangerous because they contain full complete systems (bootloader, radio, pds, and all the other very sensitive parts of the system), and they are flashed without any error checking, so it's very easy to brick (also known as hardbrick) your phone if you don't know exactly what you're doing. (That is also why all SBFs have been removed from XDA.) Unlocking the bootloader is the only time you should ever be dealing with a SBF, it should be avoided any other time if at all possible.
What I want to do is to get root and at the same time, get a custom recovery. Which means, I want to stick to stock ROM (again 50% chance of sticking to it). And that exactly what I meant by scary warnings... I have no idea what SBFs are (are they like .zip files that Galaxy W users use to flash files?). Anyway, the PUDDING thread was really, and I mean really, scary. Considering the fact that if I screw this phone, my mom will make me own the Galaxy W again...
Sent from my Samsung Galaxy W (GT-I8150) with CM9 RC 6
Yes, it can be scary, and for a reason. It is not for the faint hearted, although it goes without a hitch at least 95% of the time. The idea is that you get familiar with the process until the point where you feel comfortable with doing it.
SBFs are nothing like flashable ZIPs (well, except that both are used to flash stuff onto a device). Fruitcakes and custom ROMs come in flashable ZIPs. SBF stands for "single binary file" and is a proprietary Motorola file. It is created and signed by Motorola. Other than the pudding SBF which is the hacked unlocked bootloader, not much is known about them really, except that in some cases they can easily brick a device if misused.
There's another thing. If your atrix is too new, you might have a newer, non-unlockable bootloader. In that case all you can do is root the phone, no way to get custom recovery on it. Good news is, trying to unlock a non-unlockable BL won't do any harm, it just won't work.
If your goal is to have a custom recovery and root, I suggest you first deal with the recovery and then do the rooting. If you end up having to flash a fruitcake, by doing so you might get root anyway, depending on the fruitcake you choose (some are completely untouched, meaning no root, while some are completely stock but also rooted).
There is also an automated unlock method which you can try if you want. It should be slightly less scary to deal with. Personally, I dislike automated anything, I prefer to do the whole process myself (that way I also learn a bunch of stuff in the process), but to each their own.
ravilov said:
Yes, it can be scary, and for a reason. It is not for the faint hearted, although it goes without a hitch at least 95% of the time. The idea is that you get familiar with the process until the point where you feel comfortable with doing it.
SBFs are nothing like flashable ZIPs (well, except that both are used to flash stuff onto a device). Fruitcakes and custom ROMs come in flashable ZIPs. SBF stands for "single binary file" and is a proprietary Motorola file. It is created and signed by Motorola. Other than the pudding SBF which is the hacked unlocked bootloader, not much is known about them really, except that in some cases they can easily brick a device if misused.
There's another thing. If your atrix is too new, you might have a newer, non-unlockable bootloader. In that case all you can do is root the phone, no way to get custom recovery on it. Good news is, trying to unlock a non-unlockable BL won't do any harm, it just won't work.
If your goal is to have a custom recovery and root, I suggest you first deal with the recovery and then do the rooting. If you end up having to flash a fruitcake, by doing so you might get root anyway, depending on the fruitcake you choose (some are completely untouched, meaning no root, while some are completely stock but also rooted).
There is also an automated unlock method which you can try if you want. It should be slightly less scary to deal with. Personally, I dislike automated anything, I prefer to do the whole process myself (that way I also learn a bunch of stuff in the process), but to each their own.
Click to expand...
Click to collapse
So I was looking through the threads of the QnA section. And I came across this. Should I use the method mentioned in post #2 and #3? It looks pretty straightforward to me...
No, you cannot. The procedure you found assumes you have an unlocked bootloader.
I told you clearly what you need to do. Do not try to short-circuit the procedure. You need to go through ALL of those steps, there is no skipping ahead. It might seem scary, but either deal with it or give up on it. Do or do not, there is no try.
Oh, so is it like, you need to unlock bootlkader then root? If so, then I've finally got it!
Sent from my Samsung Galaxy W (GT-I8150) with CM9 RC 6
i rooted then was forced to unlock the boot loader when i screwed up my phone un-installing apps
used rescue root to one click root my atrix 4g (http://rescueroot.com/)
download clockwork mod recovery (http://www.clockworkmod.com/rommanager)
i installed clockwork mod recovery from fastboot (http://wiki.cyanogenmod.org/w/Install_CM_for_olympus)
unlock the boot loader following this guide (http://forum.xda-developers.com/showthread.php?t=1302423)
as an added bonus here how to bypass that stupid motoblur crap (http://www.youtube.com/watch?v=wXDj-h1DEAM)... not nessicery for anything other then turning off the blur social media thing that comes installed with the phone
now i'm rooted, got the boot loader unlocked and running neutrino rom 2.91 GT+ for the last week, and so far i couldn't be happier
also it helped me to have a second computer, one to have all the how to running on and another to do all the work with