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
Hello. The subject matter says it all.
I currently have a rooted and unlocked AT&T Atrix on 1.26 version (yeah...still in ice age ) with a locked bootloader. Im with a non-US telco carrier. It came unlocked and rooted so that was great. No hassle but now I have started doing research on custom roms and webtop mods. I am trying to get around the info overload, so pls bear with my questions.
The overall goal is to have a stock/custom rom devoid of all the bloatwares and can run webtop2sd, and if that is not possible then, webtop. Very simple needs.
Option 1
======
To remain on stock rom and update to 1.83 version, and then to install the webtop2sd mod. Ideally I would like to boot off Debian from the microsd card. There was a post in which a forumer mentioned that he was able to "frankenstein" the webtop2sd and webtop mods. Thats great if I understood correctly.
Option 2
======
To update to 4.5.91 (probably a custom rom like Aura) and then install the webtop2sd/webtop mod.
What should be done?
I am going to update 1.26 -> 1.57 -> 1.83 -> 4.5.91 via system update. (which means I now have to signed with moto account...yes I have not as I read that there were some privacy issues.)
Through the update process, I would lose root. To keep everything clean, I am going to go through factory reset and then perform the update.
Once I am in 1.83 or 4.5.91, I will apply the root and unlock the bootloader. Which is the best way to go about this? Should I just follow the instruction here or this way. Or is there any other better way?
This is all I have for now until I install the webtop mod or the custom rom...
update your phone to wherever you want it at, then use this script to unlock the bootloader:
http://forum.xda-developers.com/showthread.php?t=1182871
after that, you can easily root your phone using the preinstall method found here:
http://forum.xda-developers.com/showthread.php?t=1138204 (second post)
if you update to 4.5.91 though, as you attempt to unlock the bootloader you will get a semi-hard brick, just have it boot up into fastboot mode and continue using the script. easy as pie!
I never got a semi-hard or *soft* brick from unlocking but that's just cause I must love to eat pudding =D . Do all the OTA updates, unlock / root, and then install the 2.3.4 fruitcake and install webtop. Best option by far, IMO, as far as the ease of transition goes. Should be cake. That's what I did and as long as you don't RSD lite with an .SBF back once on 2.3.4 OTA yer good to go.
eat yer fruitcake once updated to 2.3.4 OTA *stock gingerbread*-http://forum.xda-developers.com/showthread.php?t=1163009
Install a custom kernel if ya wanna overclock or undervolt, I would personally suggest Faux123's. -http://forum.xda-developers.com/showthread.php?t=1156040
aaand freeeze all that bloatware!-http://forum.xda-developers.com/showthread.php?t=972459
I read that its easier to update via SBF than OTA? What have your experiences been so far?
Alcapone263 said:
if you update to 4.5.91 though, as you attempt to unlock the bootloader you will get a semi-hard brick, just have it boot up into fastboot mode and continue using the script. easy as pie!
Click to expand...
Click to collapse
Maybe I should try to unlock it now... And then update.
tech_girl said:
I read that its easier to update via SBF than OTA? What have your experiences been so far?
Click to expand...
Click to collapse
well, i can't find it anymore but there is an SBF in the development forum that will allow you to update to 2.3.4 android without getting the brickable bootloader, but i personally don't see a point in using SBF. it's not meant for the end user, and using it can be risky.
SBF flashing is faster i believe, but as i said can also potentially harm your device if you're unsure of what you're doing.
SamCripp, one of the most esteemed devs here, suggests for the average person to completely stay away from sbf flashing after you've unlocked your bootloader unless you absolutely have to use it for something.
remember though, if you use the OTA update you CANNOT downgrade your device through SBF flashing, you HAVE to use the fruitcakes method. it WILL brick your device to downgrade, but only with the OTA update.
EDIT: and it's a semi-hard brick, it doesn't hurt your device in the least. you might panic at first, but it's as simple as booting into fastboot mode and finishing the script. or if you're more tech inclined, you can just do the fastboot oem unlock command through fastboot.
Phalanx7621 said:
....
eat yer fruitcake once updated to 2.3.4 OTA *stock gingerbread*-....
Click to expand...
Click to collapse
Alcapone263 said:
......
remember though, if you use the OTA update you CANNOT downgrade your device through SBF flashing, you HAVE to use the fruitcakes method.....
Click to expand...
Click to collapse
Fruitcakes??? All this jargon.... Hmmm...gotta check this out.
http://forum.xda-developers.com/showthread.php?t=1163009
yep, Fruitcakes. it's a CWM alternative to sbf flashing, much safer since it doesn't edit the bootloader at all, so there's no risk in hard bricking your device.
after you unlock your bootloader, you should install Romracer's CWM recovery here: http://forum.xda-developers.com/showthread.php?t=1204500
do all of your flashing through CWM after you unlock your bootloader, just remember to clear cache/dalvik/data between each ROM or you might get stuck in a bootloop.
Ok...CWM sounds more familiar....
If I understand correctly, I actually dont have to go via OTA. As long as I have the img file for flashing to each version, I could just use the CWM and not via OTA, right?
tech_girl said:
Ok...CWM sounds more familiar....
If I understand correctly, I actually dont have to go via OTA. As long as I have the img file for flashing to each version, I could just use the CWM and not via OTA, right?
Click to expand...
Click to collapse
well, you have to have an unlocked bootloader to get CWM. and to unlock your bootloader, you have to update to 1.8.3 or later.
after you unlock your bootloader, you can install CWM and proceed to just use CWM for your flashing needs.
i repeat again though, after you unlock your bootloader you should stay away from SBF flashing altogether. it's the quickest way to brick your device.
Alcapone263 said:
well, you have to have an unlocked bootloader to get CWM. and to unlock your bootloader, you have to update to 1.8.3 or later.
after you unlock your bootloader, you can install CWM and proceed to just use CWM for your flashing needs.
i repeat again though, after you unlock your bootloader you should stay away from SBF flashing altogether. it's the quickest way to brick your device.
Click to expand...
Click to collapse
+1
Once you unlock and get CWM installed its just a case of wiping the device and flashing zip files.
Yep after unlocking and getting rom racers cwm in, you get to have lots of fun and almost zero chance of hard bricking. Make sure you understand the pudding part. After you unlock throw rsd lite away.
After updating to 1.83 and unlocked, can I immediately installing a GB custom rom like Aura or Alien? Or do I need to update to 4.5.91 stock before I can install a custom rom? Which I assume is pre-rooted, which mean I dont have to root it..
tech_girl said:
After updating to 1.83 and unlocked, can I immediately installing a GB custom rom like Aura or Alien? Or do I need to update to 4.5.91 stock before I can install a custom rom? Which I assume is pre-rooted, which mean I dont have to root it..
Click to expand...
Click to collapse
You should be able to start flashing if you used pudding. No need to upgrade to .91 stock. I didn't. I think most roms are pre rooted now. Not that the rooting method was hard for the atrix.
I voided my warranty.
pukemon said:
You should be able to start flashing if you used pudding. No need to upgrade to .91 stock. I didn't. I think most roms are pre rooted now. Not that the rooting method was hard for the atrix.
I voided my warranty.
Click to expand...
Click to collapse
Yep thats how it works. once BL unlocked and CWM installed you can flash anything, including yes .91 stock.
Note that .91 stock OTA is not only the operating system but also modifies the bootloader hence all the hard brick warnings about flashing sbfs. When you flash zip files you don't touch the bootloader, so there is no chance of hard bricking. i.e. if you flash .91 stock from zip file from CWM as opposed to OTA, you get only the OS, not the bootloader update (which doesn't matter ).
I am wanting to relock my bootloader. I have unlocked bootloader with CWM alien rom. I am returning my phone thus the need for relocking. Or is there a rom I can flash that will not have unlocked on motorola screen while it is booting.
In the same place you found the unlock .sbf, you can find a file called "nopuddingforu.rar." This is the bootloader locker, follow the instructions EXACTLY on that page as to locking the phone again. Also, you can flash the MR5 .sbf if you want 100% stock. Be sure to do a factory reset before flashing back to stock.
-Jason
ERROR MESSAGE FAILED TO BOOT 4....RELocking Bootloader
I flashed CM5 recovery, installed nopudding.rar via rsdlite...my phone reboots and I get FAIL on rsdlite. When I cut my phone on it is stuck on Motorola screen with Failed to boot 4 at top of screen and starting RSD mode below it...
when I boot into fastboot I get same thing failed to boot 4 and I have starting fastboot protocol support....
I didnt see the do factory reset before I flashed back to stock......
rslawson said:
I flashed CM5 recovery, installed nopudding.rar via rsdlite...my phone reboots and I get FAIL on rsdlite. When I cut my phone on it is stuck on Motorola screen with Failed to boot 4 at top of screen and starting RSD mode below it...
when I boot into fastboot I get same thing failed to boot 4 and I have starting fastboot protocol support....
I didnt see the do factory reset before I flashed back to stock......
Click to expand...
Click to collapse
just flash the full MR5 .sbf with rsdlite
Thexfactor2011 said:
just flash the full MR5 .sbf with rsdlite
Click to expand...
Click to collapse
That should fix your problem. Forgive me if I'm wrong, but when you flash things with RSDLite you are flashing an actual partition image. The phone internal memory is broken up into multiple partitions, such as /system, /data, etc. When you flash the full MR5.sbf file, I believe it actually flashes all the partitions in the phone with the stock images.
Where is the full MD5 .sbf file located? I didnt see it in the pudding thread....
sorry MR5.sbf
Now that I realize it, I was actually seeing the full MR5.sbf WITH unlock... I can't seem to find one that is locked. Here is the one to the unlock though: http://mophoforum.com/the2dcour/pudding_stock.rar I imagine you could flash that and then flash the nopudding4u to relock it.
EDIT
Here is the nopudding4u file: http://diamantephoto.com/photon_nopudding4u.rar
It consists of only the locked bootloader. So flashing the full MR5.sbf (unlocked) will return your phone back to stock but with an unlocked bootloader. After you have flashed the full MR5, flash the nopudding4u file I linked so that it relocks the bootloader.
It's here in the developer forum. Look for the post from 8/11 about the "Final" sbf. Can't miss it. Good luck!
mrinehart93 said:
Now that I realize it, I was actually seeing the full MR5.sbf WITH unlock... I can't seem to find one that is locked. Here is the one to the unlock though: http://mophoforum.com/the2dcour/pudding_stock.rar I imagine you could flash that and then flash the nopudding4u to relock it.
EDIT
Here is the nopudding4u file: http://diamantephoto.com/photon_nopudding4u.rar
It consists of only the locked bootloader. So flashing the full MR5.sbf (unlocked) will return your phone back to stock but with an unlocked bootloader. After you have flashed the full MR5, flash the nopudding4u file I linked so that it relocks the bootloader.
Click to expand...
Click to collapse
I was thinking I could flash the unlock again and then flash the lock....
rslawson said:
I was thinking I could flash the unlock again and then flash the lock....
Click to expand...
Click to collapse
That's what I told you in the post you quoted
Jason_Thames said:
In the same place you found the unlock .sbf, you can find a file called "nopuddingforu.rar." This is the bootloader locker, follow the instructions EXACTLY on that page as to locking the phone again. Also, you can flash the MR5 .sbf if you want 100% stock. Be sure to do a factory reset before flashing back to stock.
-Jason
Click to expand...
Click to collapse
Yea, this should not be told to people, because as far as I know you HAVE to have the original recovery and as far as I know we have no zip or img file of it currently. So telling people to flash this will only cause problems.
Here is the nopudding4u file: http://diamantephoto.com/photon_nopudding4u.rar
It consists of only the locked bootloader. So flashing the full MR5.sbf (unlocked) will return your phone back to stock but with an unlocked bootloader. After you have flashed the full MR5, flash the nopudding4u file I linked so that it relocks the bootloader.
Click to expand...
Click to collapse
Also, if you flash the full MR5 you do not need to flash the nopudding4u file because you just flashed the complete MR5 file. Meaning you just flashed the whole img file of the phone, meaning that the original recovery is there and it already relocked your phone. The nopudding4u was suppose to just make it so you don't have to flash the MR5, just the small file, so it doesn't take much time. But it wasn't really made clear that you need to have the original recovery, or how to get said recovery.
-DJ
So I just flash the pudding stock rar file?
rslawson said:
So I just flash the pudding stock rar file?
Click to expand...
Click to collapse
No, flash this. http://forum.xda-developers.com/showthread.php?p=16328237
Sent from my MB855 using Tapatalk
To all that replied to my post
I would like to thank everyone for your assisstance. I have my phone back up and working. I am returning my photon and going to pick up the Epic 4G Touch....any of you heard anything I should know about Epic before I get it? I have an EVO that I love...I have it rooted and flash Roms and such so Im not a newb. The support on XDA from people like yourselves is in a worx F#%$ING AWESOME!!!!
I had to use MR3. Once I flashed it I was able to download the MR5 update from the phone. Nothing else worked for me.
MR3 SBF - will relock bootloader
Here is the link to MR3 if anyone needs it
http://forum.xda-developers.com/show...1225220&page=2
M
Need some help please.
I have Telstra Atrix with ota gingerbread, unlocked BL, rooted.
I can't get it to boot into cwm recovery.
I installed ROM Manager from market, flashed CWM 2.0.2.0 , selected Reboot into Recovery but it only gets to the triangle. From there I can hold down Vol Up+VolDown and get to Basic Android recovery.
I have deleted the racing car app as suggested in one thread to make room, but no help.
If I power off and boot it from Power+Vol Down it comes up "Failed to boot 2"
Can't find a solution in XDA or Google. Any help appreciated.
See if you can fastboot flash a recovery image
sent from my Atrix via XDA premium
Most likely need to delete "install-recovery.sh" @ /system/etc, if it's there, then try re-installing CWM Recovery, and see if that works.
Thanks fellas.
Turns out I had lost my unlock BL by flashing the Telstra Froyo sbf from the xda Atrix Firmwares Superthread.
Reflashed the pudding and it's unlocked again. Actually romracer explained it better in his thread. I thought you couldn't relock bootloader. CWM recovery works now.
Thanks fellas.
Turns out I had lost my unlock BL by flashing the Telstra Froyo sbf from the xda Atrix Firmwares Superthread.
Reflashed the pudding and it's unlocked again. Actually romracer explained it better in his thread. I thought you couldn't relock bootloader. CWM recovery works now.
U can't actually relock the boot loader, it "Burns a fuse" inside the unit when u unlock. But flashing an .sbf makes it appear as if it's locked again.
Sent from my MB860 using Tapatalk
Phalanx7621 said:
U can't actually relock the boot loader, it "Burns a fuse" inside the unit when u unlock. But flashing an .sbf makes it appear as if it's locked again.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Yeah thanks. Romracer explained it to me. It doesn't seem to be common knowledge at all. So people flashing sbf's of stock roms are effectively losing root. I spent hours trying to figure it out and get info searching and asking questions. Anyway, all good now and I appreciate the assistance.
On another point do you know how I can get the Telstra radio so I can use it with custom roms? My phone use is way better since installing Telstra stock Gingerbread ota. If I flash another rom I'll lose it won't I? It is N_01.100.00R
Edit: thanks to @Msd24200 and @marko! for pointing out that Radio remains unchanged when flashing cm7. Also discovered where to get the zip of this radio if I lose it http://forum.xda-developers.com/showpost.php?p=15787709&postcount=1
Hi guys! I have a couple of questions. I just updated my Atrix to 2.3.4 by OTA update, so i created a brickable device, haven't i? I would like to know what i have to do know, i want to root the phone and unlock the bootloader to install custom roms, but im afraid to brick my new phone. I have read a lot the past two hours, but im still not sure about what to do now in order to unlock the phone and achieve root.
Also, the device will brick if i try to flash any 2.2 rom, no matter how i flash it (via CWM for example)? Or only if i flash a 1.8.3 SBF via RSDLite? Are there any other files that i have to avoid if i don't want to brick my phone?
Thanks for helping me out guys!
djluis48 said:
Hi guys! I have a couple of questions. I just updated my Atrix to 2.3.4 by OTA update, so i created a brickable device, haven't i? I would like to know what i have to do know, i want to root the phone and unlock the bootloader to install custom roms, but im afraid to brick my new phone. I have read a lot the past two hours, but im still not sure about what to do now in order to unlock the phone and achieve root.
Also, the device will brick if i try to flash any 2.2 rom, no matter how i flash it (via CWM for example)? Or only if i flash a 1.8.3 SBF via RSDLite? Are there any other files that i have to avoid if i don't want to brick my phone?
Thanks for helping me out guys!
Click to expand...
Click to collapse
After you unlock the boot loader, do not flash any sbf prior to 4.5.91. In fact after you unlock the boot loader, there's no need to flash a sbf at all, b/c you can just flash a fruitcake to return to stock.
As far as picking a ROM, it doesn't really matter... any ROM that requires a unlocked boot loader (which they all do), it is at least based off of gingerbread Android 2.3.4+
Use the pudding unlock sbf to unlock your boot loader. Most rooms include root. See my sig for further info.
Sent from my CM7 Atrix 4G
Swiftks said:
After you unlock the boot loader, do not flash any sbf prior to 4.5.91. In fact after you unlock the boot loader, there's no need to flash a sbf at all, b/c you can just flash a fruitcake to return to stock.
As far as picking a ROM, it doesn't really matter... any ROM that requires a unlocked boot loader (which they all do), it is at least based off of gingerbread Android 2.3.4+
Use the pudding unlock sbf to unlock your boot loader. Most rooms include root. See my sig for further info.
Sent from my CM7 Atrix 4G
Click to expand...
Click to collapse
Thanks for your fast response! So, if i use the auto-unlocker on that thread, it wont brick my device right? Thanks for pointing me that, it seems very usefull. Now, this leads me to the next question, i also have to SIM Unlock my Atrix, because its locked to ATT and im trying to use it outside the US, so i need to SIM unlock it, i have seen several threads of users reporting problems SIM unlocking the phone, should i wait for the SIM Unlock code before proceding to unlock the bootloader? I have already ordered one, the guys should email it any time now, it will take less than 24hrs, and no less than 2hrs (which have already passed).
Thanks for your answers guys!
EDIT: Couldn't resist, unlocked the bootloader and achieved root. It was super easy with the automated batch. I hope i don't run into problems when i try to SIM unlock the phone lol