[Q] 4.5.91 Clarification - Atrix 4G Q&A, Help & Troubleshooting

I updated with the official OTA to 2.3 and I've been reading a ton about the hardbrick mess that has surfaced along with the 2.3 update. Basically, I'm wondering what are my options as far as rooting, unlocking, and roms. Or am I SOL for the time being?

rooting, unlocking and roms are available for you. I OTA'd as well..couple days ago I unlocked my Atrix. Only thing you CAN'T do ..now that you've OTA'd.. is you CANNOT downgrade with RSD. That will cause a hardbrick.
Sent from my MB860 using XDA App

Okay, that's as far as my understanding of the matter went haha.
It may seem like a noob question, but what is the need to downgrade?

Hardbricks are from downgrading to a previous firmware.
Sent from my MB860 using XDA App

Yes, I'm aware of that. I want to know why I would need to downgrade?

thezoolander said:
Yes, I'm aware of that. I want to know why I would need to downgrade?
Click to expand...
Click to collapse
sometimes things go wrong when modding your phone. downgrading will restore your phone back to a factory state.

Okay, that's what I was thinking. So couldn't we just create a back up of our 2.3 OTA and revert back to that if something went wrong?

from what i understand you can sbf 4.5.91
"You can sbf 4.5.91 because it has the same identical bl bp pass"
quoted from here..right under the picture.
http://forum.xda-developers.com/showthread.php?t=1160408

thezoolander said:
Okay, that's what I was thinking. So couldn't we just create a back up of our 2.3 OTA and revert back to that if something went wrong?
Click to expand...
Click to collapse
That's the correct way of doing things without hardbricking, yes.
Unlock the BL, install CWM and create a backup of you system before modding.
Whatever you do DO NOT SBF back to earlier build.

Wow! This is the best answer I've been looking for for two days! There should be a lot of deleting and simplifying on this forum. People are going to mess up their phones. Just saying.

thezoolander said:
Yes, I'm aware of that. I want to know why I would need to downgrade?
Click to expand...
Click to collapse
For AT&T users, we had some good hacks that recommended that you went down to original stock Froyo.
Something like that is not an option anymore...

Makes sense, but I do prefer GB over Froyo in so many ways so its worth it for me, and hopefully new hacks and what not will surface in time. I'm patient lol.

well, some people also like to downgrade cause they like Froyo (huh?! who?!) and some people want back fingerprint (but im a patient one, so I won't ditch my gingerbread for something so silly =P). Like everyone said, if you DO need to SBF, just SBF back to 4.5.91. If you have an unlocked bootloader and flashed Tenfar's CWM, however, just eat your Fruitcakes and you'll be good to go. Those are totally safe (as far as I know =D Mmmmmmmm)
Happy upgrading! =]
~jojojohnson7410~

Related

[Q] Can http://www.multiupload.com/C0I82IXH7V be flashed over GingerBlur??

Although this is my first post, I have been reading hundreds of threads on this site for months now...
I know this post should be in the developer-related forums but being a newbie I am not allowed to post in that section.
My question is can that SBF be flashed over GingerBlur...here is what I am running with a LOCKED bootloader.
Version.4.1.83.MB860.ATT.en.US
Android 2.2.2
Baseband N_01.77.15P
Kernel 2.63.9-00007-g527fe10
Build GingerBlur 4
Please respond ASAP I just OTA Gingerbread onto my girlfriend's Atrix because she doesn't want to fool around with all this and am DYING to get my hands on a rooted, unlocked Gingerbread Atrix!
At least if you want an unlock bootloader the only option so far for an AT&T unit is flashing pudding no matter what version you have (1.83 or 2.3.4/4.5.91)
cwburns32 said:
Although this is my first post, I have been reading hundreds of threads on this site for months now...
I know this post should be in the developer-related forums but being a newbie I am not allowed to post in that section.
My question is can that SBF be flashed over GingerBlur...here is what I am running with a LOCKED bootloader.
Version.4.1.83.MB860.ATT.en.US
Android 2.2.2
Baseband N_01.77.15P
Kernel 2.63.9-00007-g527fe10
Build GingerBlur 4
Please respond ASAP I just OTA Gingerbread onto my girlfriend's Atrix because she doesn't want to fool around with all this and am DYING to get my hands on a rooted, unlocked Gingerbread Atrix!
Click to expand...
Click to collapse
Sent from my MB860 using XDA App
Seems like this question is asked a lot and I want to know the "straight" answer too. Would downgrading to deodexed 1.8.3 via recovery from Gingerblur be enough in order to flash SBF gingerbread and unlock? Or should I SBF back to an old AT&T version and update to 1.8.3 before going to Gingerbread? Thanks.
LivingChampion said:
Seems like this question is asked a lot and I want to know the "straight" answer too. Would downgrading to deodexed 1.8.3 via recovery from Gingerblur be enough in order to flash SBF gingerbread and unlock? Or should I SBF back to an old AT&T version and update to 1.8.3 before going to Gingerbread? Thanks.
Click to expand...
Click to collapse
I'd use this SBF to flash GB:
http://forum.xda-developers.com/showthread.php?t=1182526
LivingChampion said:
Seems like this question is asked a lot and I want to know the "straight" answer too. Would downgrading to deodexed 1.8.3 via recovery from Gingerblur be enough in order to flash SBF gingerbread and unlock? Or should I SBF back to an old AT&T version and update to 1.8.3 before going to Gingerbread? Thanks.
Click to expand...
Click to collapse
Exactly!! And can it be done over GingerBlur or CherryBlur as I have seen asked on here for the past day or so consistently with no concrete answers.
cwburns32 said:
Exactly!! And can it be done over GingerBlur or CherryBlur as I have seen asked on here for the past day or so consistently with no concrete answers.
Click to expand...
Click to collapse
If you're on 1.8.3 (I don't care what P-ROM you have installed), you can simply flash the above SBF to obtain GB w/o the consequence of not being able to revert to 1.8.3
mpalatsi said:
If you're on 1.8.3 (I don't care what P-ROM you have installed), you can simply flash the above SBF to obtain GB w/o the consequence of not being able to revert to 1.8.3
Click to expand...
Click to collapse
Cheers duude. Just outta curiosity how do you like Ninja Speed Freak v4.5?
cwburns32 said:
Cheers duude. Just outta curiosity how do you like Ninja Speed Freak v4.5?
Click to expand...
Click to collapse
Love it. It's clean, quick, and reliable.
So, using that link will it unlock the bootloader too? P-ROM would be gingerblur correct? I am sorry, I am kind of new to the Atrix scene. Gingerblur was really simple, but the rest is kind of out of my league at the moment.
LivingChampion said:
So, using that link will it unlock the bootloader too? P-ROM would be gingerblur correct? I am sorry, I am kind of new to the Atrix scene. Gingerblur was really simple, but the rest is kind of out of my league at the moment.
Click to expand...
Click to collapse
That's right, it will unlock your bootloader if you were on 1.8.3.
Make sure you have a full battery before flashing!
Charged that baby all night, today was the day I got Gingerbread. I just wanted to make sure everything is in order before flashing.
Just finished installing it, holy crap. Every app is saved. It seems I'm still rooting too. How do I tell if I'm unlocked?
edit: Ah, nevermind I'm not rooted. Guess thats something I'm going to have to do now.

[Q] Motorola Atrix Re-lock Bootloader

I may have to return my ATRIX due to Let'sTalk horrible customer service, but I was wondering if there is anyway to re-lock the Bootloader, or to hide the fact that it says, Unlocked. Thank you in advanced
Also, I'm sorry if this is in the wrong section, as this is urgent to me and I have yet to see any otherpost relating this topic.
There is another topic like this.
No you can't re-lock and no you can't "hide" the unlock wording. Sorry.
Sent from my AWESOME Atrix
Assume you installed 2.3 using CWM, if that is the case, you can flash the stock 1.8.3. Because the bootloader is not compatible with the unlocked phones, it won't show the "unlocked" text when you turn on the phone. I have tried it when I was trying to get rid if the unlocked text.
The down side is, you won't be able to flash custom ROM until you flash a compatible bootloader.
Sent from my Motorola Atrix 4G MB860 using XDA App
But downgrading will hard brick the phone.be very very carefully.
Reflash To Stock
Unfortunately, there is no way to relock a bootloader. Hence all of the warnings when you committed
but, if you use 4.5.91 the software at the address below should reinstall the newest stock software...
direct.motorola.com/hellomoto/motosupport/source/SoftwareUpdateSelect.asp?country=USA&language=ENS
be careful because Im not sure how motorola update will react to an unlocked bootloader. Ask around...do so at your own risk.
If you want to try a harder, albeit, safer method, and you are sure that you do not have a phone running 4.1.5.91, you can restore your phone to a factory SBF with this process:
briefmobile.com/motorola-atrix-4g-system-boot-file-sbf-leaked
DO NOT UNDER ANY CIRCUMSTANCES TRY TO RESTORE A 4.5.91 system to stock with RSD LITE.
To go to any of the blue webaddresses above, copy-paste them into your browser. Sorry, but I am not allowed to post links yet.
I wonder why nobody has created a CWM downgrade for US Atrixes. NFHimself made one for Bell or international users to go to 2.2.2 Bell and it works really well. Pretty much every partition is replaced. Great for masking that your boot loader is unlocked. Someone should probably do that for ATT to make downgrading less risky than flashing an sbf again...
drpratik said:
But downgrading will hard brick the phone.be very very carefully.
Click to expand...
Click to collapse
The downgrading and hard brick problem stems from using the OTA update, so you won't hard brick if for example you upgraded with KP's 4.5.91.
You also should be able to flash the 4.5.91 SBF. You just can't downgrade. There are other threads about this.
Sent from my Alienated Atrix
maledyris said:
I wonder why nobody has created a CWM downgrade for US Atrixes. NFHimself made one for Bell or international users to go to 2.2.2 Bell and it works really well. Pretty much every partition is replaced. Great for masking that your boot loader is unlocked. Someone should probably do that for ATT to make downgrading less risky than flashing an sbf again...
Click to expand...
Click to collapse
The reason the fruitcakes were created and deemed safe by the devs were because it didn't touch the BL, which people believe to be the culprit behind the hard bricks. NFhimself was brave enough to testing flashing the BL via cwm in his gobstopper on international phones, but I don't think any other devs are willing to risk hard bricking their phones by testing that theory on US phones.
There also isn't enough "reward" for doing so because if people want to downgrade they can use a fruitcake. The only gain is to get rid of the "unlock" text. But if you were really that concerned about it despite reading all the warnings of this will void you warranty, you shouldn't have unlocked in the first place.
maledyris said:
I wonder why nobody has created a CWM downgrade for US Atrixes. NFHimself made one for Bell or international users to go to 2.2.2 Bell and it works really well. Pretty much every partition is replaced. Great for masking that your boot loader is unlocked. Someone should probably do that for ATT to make downgrading less risky than flashing an sbf again...
Click to expand...
Click to collapse
Hi,
One of the reasons I did up a default CWM of 2.2.2 is to have a means of doing a reset after trying all ATT/ORANGE/TELSTRA/MOVIESTAR/etc firmwares out there which may have side effects or accumulated side effects. Hence the inclusion of the stock bootloader and radio and a write of the extra partitions to clean up whatever mix and match leftovers are in there from the various carriers. The other big one is just to be able to get a Bell OTA applied when it comes out, it will probably be similar to the leak, but best to be safe.
This is more of a Bell/Intl issue as ATT folks tend to run just ATT firmware or flash just boot and system via CWM/fastboot and don't have the same issues as flashing a sbf file.
Both the stock 2.2.2 and leaked ap20 OTA bootloaders from Bell are safe to flash after IHOP, this is not the case with ATT bootloaders and may be the case for any included in a sbf file. Finding out the hard way is not an option.
Cheers!
ken218 said:
Assume you installed 2.3 using CWM, if that is the case, you can flash the stock 1.8.3. Because the bootloader is not compatible with the unlocked phones, it won't show the "unlocked" text when you turn on the phone. I have tried it when I was trying to get rid if the unlocked text.
The down side is, you won't be able to flash custom ROM until you flash a compatible bootloader.
Sent from my Motorola Atrix 4G MB860 using XDA App
Click to expand...
Click to collapse
Say I unlocked it at 1.8.3 should I go down to 1.5.7? Is that safe?
moto helper update relocked mine flashed it to 4.5.91 and i had to reunlock and root agin i thought i was getting a driver update not ota.I was on rom homebase + extras but my win 7 64 bit wasent seeing my phone so i reinstalled drivers and updated drivers and updated moto helper and in the process flashed my phone to stock that pissed me off had to start over..I rebooted the phone several times and never seen unlocked on boot tried to fastboot into android recovery and got the triangle im all good now back on homebase ext4 just thought id share that you realy can relock at least it dont say unlocked i beleve its locked
defnow said:
and no you can't "hide" the unlock wording. Sorry.
Click to expand...
Click to collapse
Err...............yes you can!
care to share how?
Scolis said:
care to share how?
Click to expand...
Click to collapse
Read the thread from the start. It's already been said!
CaelanT said:
Read the thread from the start. It's already been said!
Click to expand...
Click to collapse
Trying this today. Seems like my vibrator motor quit working. Phone is 6 months old I should be under the year warranty or so right?
leperkuan said:
Trying this today. Seems like my vibrator motor quit working. Phone is 6 months old I should be under the year warranty or so right?
Click to expand...
Click to collapse
When I was at school 6 months < 1 year so yes!
This is where you need to look:
http://forum.xda-developers.com/showthread.php?t=1163009
CaelanT said:
When I was at school 6 months < 1 year so yes!
This is where you need to look:
http://forum.xda-developers.com/showthread.php?t=1163009
Click to expand...
Click to collapse
Lol well I wasn't sure it had a one year warranty. Found out my vibrator does work. Just sometimes doesn't on cm7. Weird. Well I may try this anyways. Tired of custom Roms.
Sent from my MB860 using Tapatalk
leperkuan said:
Found out my vibrator does work.
Click to expand...
Click to collapse
Think you should go to another site other than XDA with this. Something in the XXX domain should work for you. Too much information for me! LOL................
assuming it is still in warranty
hard brick the phone and return it
just tell them you was doing a software update and your kid unplugged the phone while doing so

Can I go back to official stock sense if I flash GB

I am thinking about flashing the leaked GB but was wondering if I flash one of them would I be able to flash back to stock sense froyo?
Sent from my ADR6400L using XDA Premium App
i actually skipped a step ahead and flashed the leaked gb rom.. i thought it was just the radio because because you have to rename it in bootloader.. funny thing is i flashed the debloated version minutes before. now im stuck with a stock unrooted s-on device. im trying to reroot to flash back myself but im getting 'failed to set prot mask'... im still searching for answers. my conclusion just dl the debloated one.
alluzzion2o9 said:
i actually skipped a step ahead and flashed the leaked gb rom.. i thought it was just the radio because because you have to rename it in bootloader.. funny thing is i flashed the debloated version minutes before. now im stuck with a stock unrooted s-on device. im trying to reroot to flash back myself but im getting 'failed to set prot mask'... im still searching for answers. my conclusion just dl the debloated one.
Click to expand...
Click to collapse
I'm gonna say you should probably read my noob qANDa thread. You NEVER flash ROMs through hboot. You don't even have to rename your ROM. You, my friend, flash an RUU, which you should only do if you want a bone stock device. RUUs are put out there for devs to play with, generally speaking. The only thing you ever flash in hboot is the radio, and maybe a couple other things if you really know what you're doing. As for fixing your root situation, the process can be done exactly as it's laid out in jcase's guide, except you need to use a different exploit tool instead of the one supplied in that thread. A quick search for rooting the GB rom should locate that exploit. I can't speak for AlphaRevX yet. Last time I looked they were out of commission.
loonatik78 said:
I'm gonna say you should probably read my noob qANDa thread. You NEVER flash ROMs through hboot. You don't even have to rename your ROM. You, my friend, flash an RUU, which you should only do if you want a bone stock device. RUUs are put out there for devs to play with, generally speaking. The only thing you ever flash in hboot is the radio, and maybe a couple other things if you really know what you're doing. As for fixing your root situation, the process can be done exactly as it's laid out in jcase's guide, except you need to use a different exploit tool instead of the one supplied in that thread. A quick search for rooting the GB rom should locate that exploit. I can't speak for AlphaRevX yet. Last time I looked they were out of commission.
Click to expand...
Click to collapse
Guess I used the wrong choice of words there. I am aware that RUUs, radios are all that you flash from HBoot, and ROMs are flashed from the recovery. I just remember reading one post on here that someone asked if we flash GB can we get back to stock sense froyo and was told no. After taking a step back and thinking of what I was asking and how ROMs actually work I could have answered my own question.
jmc2543 said:
Guess I used the wrong choice of words there. I am aware that RUUs, radios are all that you flash from HBoot, and ROMs are flashed from the recovery. I just remember reading one post on here that someone asked if we flash GB can we get back to stock sense froyo and was told no. After taking a step back and thinking of what I was asking and how ROMs actually work I could have answered my own question.
Click to expand...
Click to collapse
I think "no" might have been true for a short time, but it wasn't long before I saw the exploit to root GB floating around. That one guy did seem a bit confused on the matter though.
loonatik78 said:
I think "no" might have been true for a short time, but it wasn't long before I saw the exploit to root GB floating around. That one guy did seem a bit confused on the matter though.
Click to expand...
Click to collapse
What is the new exploit? Fr3vo?
Sent from my HTC Thunderbolt

[Q] Last Question before I go through with it.

I'm rooted on like 1.8.3 I believe. Maybe 2.2, but definitely not gingerbread. Bootloader is not unlocked.
Can I simply flash this:
http://forum.xda-developers.com/showthread.php?t=1138204 - the 2.3.4 version, and be rooted and ready to install a ROM while being on gingerbread?
Thanks for your help.
rAFTA! said:
I'm rooted on like 1.8.3 I believe. Maybe 2.2, but definitely not gingerbread. Bootloader is not unlocked.
Can I simply flash this:
http://forum.xda-developers.com/showthread.php?t=1138204 - the 2.3.4 version, and be rooted and ready to install a ROM while being on gingerbread?
Thanks for your help.
Click to expand...
Click to collapse
So says the OP... I'd read a few pages first though, just to make sure.
rAFTA! said:
I'm rooted on like 1.8.3 I believe. Maybe 2.2, but definitely not gingerbread. Bootloader is not unlocked.
Can I simply flash this:
http://forum.xda-developers.com/showthread.php?t=1138204 - the 2.3.4 version, and be rooted and ready to install a ROM while being on gingerbread?
Thanks for your help.
Click to expand...
Click to collapse
I'd say this (and I say it with the most benevolent intentions):
1) You don't know that 1.83 is in fact 2.2 (froyo). 1.83 just refers to AT&T's software release, not the current android version on your phone. This leads to...
2) Flashing that will get you 90% of the way there, but I fear it won't get you that last 10%, which is the dealbreaker- ROOT. This is because I'm afraid you don't quite grasp ADB...but no matter, I'm here to help.
3) What I would do is flash the 2.3.4 SBF with the BL UL (bootloader unlock)...(all of this found in the thread you linked), but then I'd go here. It's a really simple automated process that works through the command prompt/ADB and, with it, it's very quick and easy to attain root without all the manual ADB commands. On top of that, it's very useful for many other things besides just obtaining root.
Also, you might want to just look at this thread to see if there's anything useful, helpful, or downright lifesaving. And you can thank responder #1 for that.
I hope you didn't take this in the wrong way (frankly, me being a ****). I just want you to know the proper terminology, and not FUBAR your phone.
Always better to ask (though maybe search, first) than to go ahead and brick your device and then be a screaming all about the forums begging for help.

[Q] Critical Update for 4.5.141.en.us from motorola- OK to update?

My info-
on ATT
Unlocked
Rooted
4.5.91
Android Version 2.3.4
Alien #4
ROM Manager v5.0.0.7
Should I install the "critical update" from Motorola? I just started to see the notices.
Will it cause issues with my current setup?
Thanks,
Sean
MagSea said:
My info-
on ATT
Unlocked
Rooted
4.5.91
Android Version 2.3.4
Alien #4
ROM Manager v5.0.0.7
Should I install the "critical update" from Motorola? I just started to see the notices.
Will it cause issues with my current setup?
Thanks,
Sean
Click to expand...
Click to collapse
wat
There's an update?
Since you're on Alien/rooted/unlocked BL I would recommend against taking any OTA update. It would most likely fail anyway.
EDIT- I just noticed you're on 4.5.91, you must be seeing the notifications for the 4.5.141 update. You had me all excited that there was some other update out.
Thanks Stewart- poor reading comprehension on my part.
That answers it.
No!
S Do not update, there are multiple posts of people bricking their phone attempting to update, if you continually get requests to update you can freeze updater with titanium backup. If you want to update with newer firmware I would suggest taking a look at the many newer gb roms or even a move to cm7 if you really want something a bit different, as far as I am aware there aren't going to be any more updates to Alien.
I'm on a stock 4.5.141 myself, with a few enhancements. I had an unlocked bootloader on 4.5.91, updated using the 4.5.141 SBF, and could re-unlock the bootloader. Then CWM and start flashing zips (like root).
I'm still waiting with bated breath for an ICS leak.
MagSea said:
My info-
on ATT
Unlocked
Rooted
4.5.91
Android Version 2.3.4
Alien #4
ROM Manager v5.0.0.7
Should I install the "critical update" from Motorola? I just started to see the notices.
Will it cause issues with my current setup?
Thanks,
Sean
Click to expand...
Click to collapse
I would flash your current version sbf through rsd lite then OTA update your phone then unlock it again.
Sent from my MB860 on CM7
Soldier-2Point0 said:
I would flash your current version sbf through rsd lite then OTA update your phone then unlock it again.
Sent from my MB860 on CM7
Click to expand...
Click to collapse
Dont do this. You're unlocked, treat RSD as if it doesnt exist. If I were you, I'd try to find either a .141 fruitcake (CWM flashable versions of RSD files) or switch to a .141 based rom if you want to stick with blur.
Jotokun said:
Dont do this. You're unlocked, treat RSD as if it doesnt exist. If I were you, I'd try to find either a .141 fruitcake (CWM flashable versions of RSD files) or switch to a .141 based rom if you want to stick with blur.
Click to expand...
Click to collapse
I have done what I said I would and it did not brick my device. There is a risk if you flash the wrong sbf or downgrade.
Soldier-2Point0 said:
I have done what I said I would and it did not brick my device. There is a risk if you flash the wrong sbf or downgrade.
Click to expand...
Click to collapse
Most don't reccomend this however as too many possible things can go wrong. Also is alot more work to fix if something goes wrong. A flashable fruitcake or rom is more simple to do in the first place and if something does go wrong is easier to fix. Also the roms available kick butt over the stock rom.
kooldadof4 said:
... Also the roms available kick butt over the stock rom.
Click to expand...
Click to collapse
Yeah, well, you know, that's just, like, your opinion, man.

Categories

Resources