Hi,
I ordered an Atrix 4g yesterday on amazon.de and since flashing a custom rom on my previous phone was such and improvement I wanted to do the same with the atrix. But after reading some threads in the dev section I must admit i'm very confused and I have some questions.
- How do I know if my phone is unlocked? if not how to unlock?
- I think it ships with 2.2, update to 2.3.4 or just flash custom rom?
- Can anyone tell me all the steps I need to do to go from stock 2.2 to a custom rom? (CM7 Mod ICS FINAL or Neutrino ROM 1.4-S) (including unlocking, recovery etc) this part is very confusing because a lot of roms have different types of flashing and some are talking about fastboot, does my phone have this?
- How do I know what version of the phone I have? ATT? Tmobile?
- Is there any chance of bricking when doing this? With my previous phone you could ony soft brick.
I'm sorry if these things are already written somewhere but I just couldn't find em.
Thnx for all info you can tell me.
Check the noob guide in the gerenal section, its at the top of the forum,
To figure out your software version just go to settings >about phone
As for bricking you can only hard brick if you use the ota gingerbread update THEN use rsd to downgrade. So if you only use rsd to unlock then you are safe
sent from my Atrix via XDA premium
So I got my atrix a few days ago and have been looking to unlock/flash it since.
I read most posts/guides and I think I know what to do, but I'm still scared of bricking so I wanted to dubble check if I got it right
My atrix:
System: 45.31.0.MB860.Retail.en.DE
Android: 2.3.4
Build number: 4.5.2A-74_OLE-31
What I think I have to do:
1st: Flash SBF file (the IHOP file from the house of pudding) with RSDlite
2nd: Fastboot unlock
3th: Install clockworkmod with Fastboot like in:
ww w.addictivetips.com/mobile/how-to-install-clockworkmod-recovery-on-motorola-atrix-4g/
(remove the space between the WWW, not enough posts to post a link)
4th: Do a backup with clockworkmod
5th: Flash a custom ROM with clockworkmod and clear cache,dalvik cache and data.
Could someone plz comfirm that all this is correct?
Greetings!
That sounds about right
Be sure to follow any specific installation instructions for the Custom ROM you choose. Some prefer you wipe via fastboot, some want you to wipe certain partitions *after* installation, etc.
phnord said:
That sounds about right
Be sure to follow any specific installation instructions for the Custom ROM you choose. Some prefer you wipe via fastboot, some want you to wipe certain partitions *after* installation, etc.
Click to expand...
Click to collapse
ok, i'll be sure to pay attention to that, one more question.
Do I need root for any of this?
M_K_ said:
ok, i'll be sure to pay attention to that, one more question.
Do I need root for any of this?
Click to expand...
Click to collapse
ofcourse you would you can just download the gingerbreak.apk from this site; )
Sent from my MB860 using Tapatalk
OK, this all worked perfect and have been running Neutrino's since. But I wanted to try darkside now, can I just flash this in clockwork? Because I read somewhere when you flash an earlier version you get brick and neutrino's is 2.3.7 and darkside 2.3.5?
Related
i have version 1.8.3 with root and with unlocked bootloader if i want to upgrade 2.3.4, i need to flash a clean 1.8.3 and after that to unlocked again ?
or if i do that i will be in risk getting a hard brick??
liranm2 said:
i have version 1.8.3 with root and with unlocked bootloader if i want to upgrade 2.3.4, i need to flash a clean 1.8.3 and after that to unlocked again ?
or if i do that i will be in risk getting a hard brick??
Click to expand...
Click to collapse
When in doubt, use the fruit cakes! =D Mmmmmmm
But yeah, honestly, you don't need to re-lock or un-root. You can just use the Automated Upgrade found here. That will save all your data and stuff, and it'll upgrade you to Gingerbread! =D
BEFORE YOU DO ANYTHING THOUGH (I don't know how many times i emphasize this, but I guess it's worth emphasizing), BACK UP ALL YOUR DATA. In the event you lost all of it, we MIGHT be able to recover some, but expect to loose it all if you just screw my warning over. Oh, and if you want to root again, use the pre-install method. That works well for lots of people (use search bar above to find it =])
Happy upgrading!
BTW if you want unlocked bootloader again, it doesn't come with this Gingerbread build (god only knows why). Just use pudding and you'll be good to go =]
~jojojohnson7410~
jojojohnson7410 said:
When in doubt, use the fruit cakes! =D Mmmmmmm
But yeah, honestly, you don't need to re-lock or un-root. You can just use the Automated Upgrade found here. That will save all your data and stuff, and it'll upgrade you to Gingerbread! =D
BEFORE YOU DO ANYTHING THOUGH (I don't know how many times i emphasize this, but I guess it's worth emphasizing), BACK UP ALL YOUR DATA. In the event you lost all of it, we MIGHT be able to recover some, but expect to loose it all if you just screw my warning over. Oh, and if you want to root again, use the pre-install method. That works well for lots of people (use search bar above to find it =])
Happy upgrading!
BTW if you want unlocked bootloader again, it doesn't come with this Gingerbread build (god only knows why). Just use pudding and you'll be good to go =]
~jojojohnson7410~
Click to expand...
Click to collapse
The link in your post points to the official OTA.
It contains the new bootloader as a part of the payload.
This bootloader will make it impossible to go back to 1.8.3 SBF (or any other SBF) without the risk of hard brick.
For your safety, use Fruit Cakes or any of the ROMs floating around.
Stay away from official OTA or anything that does not have the new bootloader disarmed (or removed).
liranm2 said:
i have version 1.8.3 with root and with unlocked bootloader if i want to upgrade 2.3.4, i need to flash a clean 1.8.3 and after that to unlocked again ?
or if i do that i will be in risk getting a hard brick??
Click to expand...
Click to collapse
In general, you do not need to go back to anything to flash a new ROM.
Just back up your phone (through CWM) and flash a zip file with the ROM of your choice.
Most of the time, you will need to recreate your setup (download the apps and regenerate your preferred settings). To make your life much easier, I would highly recommend investing in Titanium Backup.
lol sorry forgot to mention the fruitcake part X_X made so many posts in the past hour or so, I tend to leave out information I've repeated over a lot of times. I honestly don't have a problem with the OTA (minus the fingerprint, but i think that's with everyone), so that is another viable method. So long as he stays away from SBF (which we technically should anyways) and sticks with eating his Fruitcake, I don't see what's the big deal =]
That's just my two cents on that matter. However, feisty_noodles is probably right about flashing ROMs, as they are usually well tested and don't blow the Odmfuse like the new bootloader does when you unlock with it. It's really your choice, but I preferred having an OTA (until my ROM-itis kicks back in >.>), so I just gave you the method I used.
Good luck!
~jojojohnson7410~
feisty_noodle said:
In general, you do not need to go back to anything to flash a new ROM.
Just back up your phone (through CWM) and flash a zip file with the ROM of your choice.
Most of the time, you will need to recreate your setup (download the apps and regenerate your preferred settings). To make your life much easier, I would highly recommend investing in Titanium Backup.
Click to expand...
Click to collapse
Oh, and yeah. These are important too =] Kenneth made a ROM from the Gingerbread, so you can probably use that (make sure it's not fastboot images though! A lot of people (soft?)bricked their phones that way. And Titatium ftw =D
~jojojohnson7410~
jojojohnson7410 said:
Oh, and yeah. These are important too =] Kenneth made a ROM from the Gingerbread, so you can probably use that (make sure it's not fastboot images though! A lot of people (soft?)bricked their phones that way. And Titatium ftw =D
~jojojohnson7410~
Click to expand...
Click to collapse
There is nothing wrong with fastboot images. I am running a stock from system.img (from Ken's archive) at the moment.
1.8.3 with unlocked bootloader you have 3 way to have official GB 2.3.4/4.5.91
1. Flash 1.83 "WITH" Pudding and then apply OTA by settings->about phone->system update
2. Flash 2.3.4/4.5.91 Official Motorola SBF, you can get this one by Motorola Software Updater or Development forum -> stickie -> SBF thread
3. Download 2.3.4/4.5.91 extract img's and moto-fastboot
Option 1 and 2 update the bootloader
Option 3 preserve old bootloader
liranm2 said:
i have version 1.8.3 with root and with unlocked bootloader if i want to upgrade 2.3.4, i need to flash a clean 1.8.3 and after that to unlocked again ?
or if i do that i will be in risk getting a hard brick??
Click to expand...
Click to collapse
Sent from my MB860 using XDA App
thanks you all....
i will decide today what to do.
mramirezusa said:
1.8.3 with unlocked bootloader you have 3 way to have official GB 2.3.4/4.5.91
1. Flash 1.83 "WITH" Pudding and then apply OTA by settings->about phone->system update
2. Flash 2.3.4/4.5.91 Official Motorola SBF, you can get this one by Motorola Software Updater or Development forum -> stickie -> SBF thread
3. Download 2.3.4/4.5.91 extract img's and moto-fastboot
Option 1 and 2 update the bootloader
Option 3 preserve old bootloader
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Continuing on with the list--options that do not mess with the bootloader:
4) Flash the .img files from Ken found here plus the CWM-flashable radio
5) Fruit cakes!!!
I bricked one Atrix already a few weeks ago, and have since gotten another...(don't wanna think about it)..
I had toyed with unlocking it, and 'rooted' using the gingerbreak method. I was then, bored, one day and installed CWM paid version(Since I had it on my Nexus One, and it popped up under 'my apps'). Out of curiosity I installed the bootloader via CWM, thinking it would fail before it broke anything..wrong.. It froze after a reboot, but after taking the battery out and back in came back up. Didn't think any more about it, and figured i'd finish the unlocking/flashing part some other time..
Meanwhile the annoying pending system update kept going off, and I inadvertently clicked download... it downloaded, so I figured might as well install and not worry about roms since with root I was able to use the google adhoc wifi apk, which is what I care about most. The install was stuck in an infinite loop. It would 'fail to load RSD', if you took the battery out it boot to android then reboot automatically for system update over and over. I tried using the RSD lite program at this point to flash back to stock rom, and ended up hard bricked...
So, forgive me for being a complete noob as I never had an issue with my nexus one. I am at 4.1.83, android 2.2.2. and baseband 1.7.15.. Which of the many tutorials and post should I follow? How safe are they? Did I brick because I had a partial 2.3.x install, and flashed back to a pre 2.3 base? I've read many post, but definitely a bit gun shy of bricking another Atrix. The phone keeps bugging me to update, and I keep hitting 'cancel'.
I'd like to unlock the boot loader for custom roms.
I'm also a heavy linux user, majority of tutorials seem to only imply windows with RSD lite? can this not be done with adb, and fastboot via linux?
http://forum.xda-developers.com/showthread.php?t=1154600
I would personally go HERE Read through the entire post, then read it again. And go with the ATT 2.3.4 pudding+root
That of course is after reading and re-reading THIS post! (also linked in the post above mine.
Just my opinion.. and make sure you read and nkow what to expect!
xploited said:
http://forum.xda-developers.com/showthread.php?t=1154600
Click to expand...
Click to collapse
That references 4.5.91 and unless I missed it, doesn't explicitly state it's backwards compatible with 4.1.83 and 2.2.2. is it?
Should I update first, to be at those levels and just know not to flash to an earlier build(pre 2.3.4/4.5.91)?
jmorgan6 said:
That references 4.5.91 and unless I missed it, doesn't explicitly state it's backwards compatible with 4.1.83 and 2.2.2. is it?
Should I update first, to be at those levels and just know not to flash to an earlier build(pre 2.3.4/4.5.91)?
Click to expand...
Click to collapse
Nope, don't update. It's safer to unlock BL while you are still at 4.1.83, you just need to download the correct unlock file from the pudding thread.
Otherwise the unlocking steps are exactly the same.
The easiest steps to unlocking are here:
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
From there you can flash CWM in one minute.
From there you can flash any rom via CWM in two minutes.
Good luck and don't do anything stupid.
About to get my first Android Phone, leaning towards to Atrix because of the Telstra Blue Tick.
If I do get the Atrix I would like to root/custom rom install (gingerblur/bread or CM7 not sure yet) and remove the motoblur crap.
How hard are these too root/custom install roms on the telstra supplied handset?
I have been reading a lot about rooting and installing custom roms, but all the steps point towards those with a Bell/AT&T imported handsets. So not sure which are the correct steps I should follow. I don't want to brick my phone.
The (un)-locked bootloader is the first problem. Because you need and unlocked bootloader to install root/custom rooms?
I've been reading - http://forum.xda-developers.com/showthread.php?t=1182871
Reading these steps it says this "AFTER GET THE BOOTLOADER UNLOCK YOU CAN ONLY FLASH BY RSD SBF'S WITH "PUDDING" FOR NOW ON, SO IN OTHER WORDS BE CAREFULLY WHEN YOU USE RSD AFTER "UNLOCKED" BOOTLOADER"
Does this mean i cannot use the ROM Manager trick to install ClockWorkMod and CM7?
How do I also determine the actual version of the phone I have – 1.26/1.57/1.83/4.5.91?
Really confused, trying to find the correct steps to root/install custom rom/clockworkmod install on a Telstra provided Atrix phone.
Doing lot of research before I commit to getting a Atrix. Other option is a Samsung Galaxy S2.....
Any help is appreciated.
Thanks
mckinnon81 said:
About to get my first Android Phone, leaning towards to Atrix because of the Telstra Blue Tick.
If I do get the Atrix I would like to root/custom rom install (gingerblur/bread or CM7 not sure yet) and remove the motoblur crap.
How hard are these too root/custom install roms on the telstra supplied handset?
I have been reading a lot about rooting and installing custom roms, but all the steps point towards those with a Bell/AT&T imported handsets. So not sure which are the correct steps I should follow. I don't want to brick my phone.
The (un)-locked bootloader is the first problem. Because you need and unlocked bootloader to install root/custom rooms?
I've been reading - http://forum.xda-developers.com/showthread.php?t=1182871
Reading these steps it says this "AFTER GET THE BOOTLOADER UNLOCK YOU CAN ONLY FLASH BY RSD SBF'S WITH "PUDDING" FOR NOW ON, SO IN OTHER WORDS BE CAREFULLY WHEN YOU USE RSD AFTER "UNLOCKED" BOOTLOADER"
Does this mean i cannot use the ROM Manager trick to install ClockWorkMod and CM7?
How do I also determine the actual version of the phone I have – 1.26/1.57/1.83/4.5.91?
Really confused, trying to find the correct steps to root/install custom rom/clockworkmod install on a Telstra provided Atrix phone.
Doing lot of research before I commit to getting a Atrix. Other option is a Samsung Galaxy S2.....
Any help is appreciated.
Thanks
Click to expand...
Click to collapse
You can use all the same steps as the bell atrix. (international).
Flashing using rsd has nothing to do with cwm or rom manager. You can safely use those
As for version number go to settings> about phone> build number
The whole process is actually very easy I just recommend doing all your reading and follow all the steps exactly
sent from my Atrix via XDA premium
Thanks for your reply marko!
I went to a Telstra shop and looked at a phone they had on display so the phone I get will be the same if not close too it.
System Version: 4.1.47.MB860.Telstra.en.AU
Android Version: 2.2.2
Kernel 2.6.32.9 [email protected]
Build Version: OLYEM_U4_1.4.7
From everything I have been reading once the bootloader is unlocked I can then easily install CWM then update my ROM.
sorry if i am asking a question asked for too many times already,but i can't seem to find a solution to my case,or either the thread is no longer active since the TS did not update his results,thus making me confused if he hassuccessfully or unsuccessfully rooted his atrix
i'm using atrix mb860 ofw 2.3.4.and i'm trying to install neutrino 2.2 rom gt
so here are what i had done until now:
1.rooted my atrix using Pete's One Click Root : http://forum.xda-developers.com/showthread.php?t=1258599
2.installed titanium backup and backed up batch of everything.superusered.
3.Installed cwm from market and got superusered.
4.flashed cwm recovery for atrix 4g
5.tried to install romracer using cwm.selected to restore previous roms and also chosen both wipes but failed.atrix reboots and shows "failed to boot , starting rsd mood"
what my concern is about,is just "rooting" enables me to already install roms?if it does,what did i do wrong in my steps?if it does not,please show me the way.i do not know if i should or should not flash my sbf files and bootloader
also,i read that to show that my atrix is rooted,it shold show at the top right corner during boot.but i don't see any
please help me because i really don't know what i'm doing here.i'm still new and the guides provided by the developers are for experienced people.it does not provide the detailed steps.also,please do explain some of the terms used like what is the difference between rooted and unlocked devices.
if you are too tired to explain everything all over again,then just give me the required links.i'll learn my way.btw,if you are able to give me a working link,and updated threads that would be very hopeful since some don't re-edit their first post,thus needs us to find the answer in a 1000++ replies
thank you in advance
You need to unlock your bootloader. The text you're referring to in the upper left corner of the Motorla screen is "unlocked" and it only appears after you unlock.
You can do it manually. See here.
Or automatically. See here.
You CANNOT install a CWM without unlocking your bootloader first. Rooting does not let you install ROMS, unlocking the BL does.
thanks for the reply.so that's what i'm missing.is it necessary to flash my sbf?and since neutrino rom gt changes my kernel(i think).
so after unlocking my bl,i can then install romracer->neutrino then?i'll update again and see what happens
graphidz said:
thanks for the reply.so that's what i'm missing.is it necessary to flash my sbf?and since neutrino rom gt changes my kernel(i think).
so after unlocking my bl,i can then install romracer->neutrino then?i'll update again and see what happens
Click to expand...
Click to collapse
Yes, the pudding unlocker is a small 10mb sbf file. After flashing that with RSD, you'll run the fastboot oem unlock commands.
The kernel (boot.img) is completely different from the bootloader. (if I'm reading your ? correctly).
Correct: Unlock BL>install romracer CWM> BACKUP! > install your ROM of choice
okay,this is starting to get on my nerves.i went to pudding,then scrolled down to "RSDLite/Windows Drivers/Sbf_flash"->go to hxxp://goo.gl/vfUXc link->tried but failed as it's for at&t.mine is international then.just great!
went back topudding's thread.read again..."unlock"...YES!solution for international phone!heck,this is an sbf file,what am i going to do with an sbf file?if it's just copy and paste,that will be easy.
ok,so what i really need now is a real solution to an international atrix and not at&t's atrix.or is there actually another thread for just international atrix?i just don't understand at all.please help
http://www.youtube.com/user/TheSmokingAndroid
Ck the earlier videos that he has posted on unlocking the atrix, helped me quite a bit.
FINALLY DID IT!now to install neutrino gt!thanks for all your help guys!.this guide was indispensable:
hxxp://forum.xda-developers.com/showthread.php?t=1302423
a new question : how do i install romracer?the guide did say to install itbut i don't see the app?
nvm,finally able to install neutrino.thanks a lot guys!now where's the close thread button...
no wait,again another problem!i wanna ask at neutrino's thread but this stupid 10 posts rule is preventing me.so i need to ask here.after installing neutrino,my internal memory is left with 2gb only.where is the other 8gb?when i plugged into usb,i did find them.
to note,i used cwm to install neutrino gt.the zip file was in internal.does that have anything to do with it?any way to get it back?do i need to flash neutrino again?if so,please teach me
also,how to get the market back?
Well, I've pretty much had it with this latest update (ATT, 4.5.145). I'd like to go back to .141 as its easily rootable. My Atrix is boot unlocked, and I have no interest in the custom ROMs. I dont have squat on the phone I need to keep, so I can blow the whole thing away as needed. I have the latest USB drivers and RSDlite ready to go.
I located the following ROM, and downloaded it... "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", appears to be the correct one.
I've been reading and reading and reading on the forums here (i.e. I've searched a lot), but theres a lot of cross-info, its hard to tell whats applicable in some situations.
So the question....
Which HowTo/Method/Guide would be most appropriate for my situation? Or is there something that would prevent this back-rev?
Thanks for any help or suggestions.
K
KetoSoi said:
Well, I've pretty much had it with this latest update (ATT, 4.5.145). I'd like to go back to .141 as its easily rootable. My Atrix is boot unlocked, and I have no interest in the custom ROMs. I dont have squat on the phone I need to keep, so I can blow the whole thing away as needed. I have the latest USB drivers and RSDlite ready to go.
I located the following ROM, and downloaded it... "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", appears to be the correct one.
I've been reading and reading and reading on the forums here (i.e. I've searched a lot), but theres a lot of cross-info, its hard to tell whats applicable in some situations.
So the question....
Which HowTo/Method/Guide would be most appropriate for my situation? Or is there something that would prevent this back-rev?
Thanks for any help or suggestions.
K
Click to expand...
Click to collapse
Never flash an SBF unless you have no other choice. Major hard brick risk.
In this section I have a stickied thread with the answers you need.
If your bootloader is still unlocked and you still have a custom recovery installed, flashing a fruit cake should work fine.
upndwn4par said:
Never flash an SBF unless you have no other choice. Major hard brick risk.
In this section I have a stickied thread with the answers you need.
If your bootloader is still unlocked and you still have a custom recovery installed, flashing a fruit cake should work fine.
Click to expand...
Click to collapse
At this point, I dont have much choice. Unless some one figures out what motorola/att did with 145 to completely screw root (its beyond my abilities), I need to press forward. If I brick it, I brick it. I'll use your sticky as my guide then, seems reliable.
Bootloader is unlocked, though I've never installed a 'custom recovery'. Looks like the various fruitcakes links are unavailable for download?
What is the advantage of the fruitcake version over the version I posted?
Thanks for the guidance
K
KetoSoi said:
At this point, I dont have much choice. Unless some one figures out what motorola/att did with 145 to completely screw root (its beyond my abilities), I need to press forward. If I brick it, I brick it. I'll use your sticky as my guide then, seems reliable.
Bootloader is unlocked, though I've never installed a 'custom recovery'. Looks like the various fruitcakes links are unavailable for download?
What is the advantage of the fruitcake version over the version I posted?
Thanks for the guidance
K
Click to expand...
Click to collapse
I just sold mine but will look in PC history. My matrix was stock 4.5.145 and I rooted it. I remember failing a few methods till I found one that worked. If I figure out what I did I will post it for you. If not fruitcake is best way
KetoSoi said:
At this point, I dont have much choice. Unless some one figures out what motorola/att did with 145 to completely screw root (its beyond my abilities), I need to press forward. If I brick it, I brick it. I'll use your sticky as my guide then, seems reliable.
Bootloader is unlocked, though I've never installed a 'custom recovery'. Looks like the various fruitcakes links are unavailable for download?
What is the advantage of the fruitcake version over the version I posted?
Thanks for the guidance
K
Click to expand...
Click to collapse
The difference between what you posted (an SBF) and what I suggest (a fruit cake) is that an SBF is full stock firmware (bootloader, boot, system, radio, etc). It is the bootloader that causes the problems. Flashing an SBF is a crap shoot. You might do it 10 times without a problem, and the 11th time you hard brick your device. By hard brick I mean hard brick = your device is now a paperweight.
A fruitcake is essentially the same as a custom ROM. You are only flashing the boot and system images. This is always the best option for returning to stock.
However, you are in a different situation - uncharted waters so to speak. No one knows what to expect from 145. And since you don't have a custom recovery installed (CWM, TWRP, etc.) you can't just flash a fruit cake like you would flash a ROM. You should be able to use the fastboot method to flash the fruit cake, but again...uncharted waters.
I suggest trying the following in this order based on your current situation (options 1 and 2 assume you do in fact have an unlocked bootloader):
1) Fastboot flash a custom recovery, then try to flash the zip I posted on my rooting guide thread. If this works you will have rooted 145.
2) Fastboot flash a custom recovery, then flash the 141 fruit cake I made.
3) Fastboot flash the boot and system fruitcake images.
All the files and info you need can be found on my "Answers" thread and my rooting guide.
Do not flash an SBF until all else has failed. Let me know how things go with the above before you even consider this.
Edit:
Before you try any of the above, did you try UnlockRoot? It may work.
upndwn4par said:
A fruitcake is essentially the same as a custom ROM. You are only flashing the boot and system images. This is always the best option for returning to stock.
I suggest trying the following in this order based on your current situation (options 1 and 2 assume you do in fact have an unlocked bootloader):
1) Fastboot flash a custom recovery, then try to flash the zip I posted on my rooting guide thread. If this works you will have rooted 145.
2) Fastboot flash a custom recovery, then flash the 141 fruit cake I made.
3) Fastboot flash the boot and system fruitcake images.
All the files and info you need can be found on my "Answers" thread and my rooting guide.
Do not flash an SBF until all else has failed. Let me know how things go with the above before you even consider this.
Edit:
Before you try any of the above, did you try UnlockRoot? It may work.
Click to expand...
Click to collapse
Understood, thanks for the explanation.
UnlockRoot couldnt gain root access
I will attempt your suggestions Thanks very much for the guidance, its invaluable
http://forum.xda-developers.com/showthread.php?t=1769497.
I am pretty sure this is the method I used to root 4.5.145 before I sold it
KetoSoi said:
Unless some one figures out what motorola/att did with 145 to completely screw root ...
Click to expand...
Click to collapse
From what I hear, the only thing that Moto "screwed up" (I wouldn't really call it that) is that on .145 they filled up /system. That is actually trivial to resolve - delete a few apps from /system/app that you don't need/want (you can install them later if you want to, some can live happily on /data) and - this is crucial - wipe /preinstall, since that is what fills up /system. If you don't wipe /preinstall, just deleting apps from /system will only last until next boot. Or, well, you don't need to wipe /preinstall, you can just flash the rooting preinstall image.
upndwn4par said:
Let me know how things go with the above before you even consider this.
Click to expand...
Click to collapse
I was able to flash CWM Recovery no problem. I was able to flash your superuser zip as well, however it did not root the system. All indicators showed it as being successful, but ultimately it was a no-go.
At that point I flashed your fruitcake 141 images, good to go there. I then applied the preinstall method, and viola, rooted again.
I am good to go, thanks to your knowledge and skills Thank you!
Now, all I have to do is email a scan of my middle finger to motorola/att.... lol
ravilov said:
From what I hear, the only thing that Moto "screwed up" (I wouldn't really call it that) is that on .145 they filled up /system. That is actually trivial to resolve - delete a few apps from /system/app that you don't need/want (you can install them later if you want to, some can live happily on /data) and - this is crucial - wipe /preinstall, since that is what fills up /system. If you don't wipe /preinstall, just deleting apps from /system will only last until next boot. Or, well, you don't need to wipe /preinstall, you can just flash the rooting preinstall image.
Click to expand...
Click to collapse
I tried several variations of what youre refering to, however it was to no avail.
I went as far as to delete several useless items (apps) out of the dir, the free space indicated never changed. The amount I removed was more that enough copy su in... yet, it always reports not enough space.
I tried an experiment. I renamed the 'fake' su (always zero bytes) in the bin dir to 'su.old'. Within 30 seconds, *something* renamed it back to 'su', happened right in front of my eyes in Root Explorer.
When you say 'wipe preinstall', specifically you mean?
KetoSoi said:
I tried several variations of what youre refering to, however it was to no avail.
I went as far as to delete several useless items (apps) out of the dir, the free space indicated never changed. The amount I removed was more that enough copy su in... yet, it always reports not enough space.
I tried an experiment. I renamed the 'fake' su (always zero bytes) in the bin dir to 'su.old'. Within 30 seconds, *something* renamed it back to 'su', happened right in front of my eyes in Root Explorer.
When you say 'wipe preinstall', specifically you mean?
Click to expand...
Click to collapse
Wow, that's just bizarre. Not sure what to think here.
I meant something like
Code:
moto-fastboot erase preinstall
KetoSoi said:
I was able to flash CWM Recovery no problem. I was able to flash your superuser zip as well, however it did not root the system. All indicators showed it as being successful, but ultimately it was a no-go.
At that point I flashed your fruitcake 141 images, good to go there. I then applied the preinstall method, and viola, rooted again.
I am good to go, thanks to your knowledge and skills Thank you!
Now, all I have to do is email a scan of my middle finger to motorola/att.... lol
Click to expand...
Click to collapse
Awesome!
I really don't understand why the superuser zip did not give you root access.
Moreover, I don't understand why some users seem to be able to root 145.
I guess I shouldn't be surprised since this device has always been a PITA.
upndwn4par said:
Awesome!
I really don't understand why the superuser zip did not give you root access.
Moreover, I don't understand why some users seem to be able to root 145.
I guess I shouldn't be surprised since this device has always been a PITA.
Click to expand...
Click to collapse
Very odd some cannot root. I was on permalocked bootloader and still rooted after soak
Its sad, because the 145 update seemed like it made the phone a little snappier, and the screen was a pinch smoother.
What do you guys think about applying the CWM Zip for update 4.5.145 in my situation? Would that be safer?
Uh oh.... you guys ran away! LOL
I was able to flash the 145 update via CWM from NYG-SBXLII's handy zip file
No real problems, 145 running fine WITH root intact. Awesome
Had to blow away the recovery-from-boot.p file afterwards, and re-flash CWM Recovery, but it was all good.
Updated SU and bin's, good to go.
affiatic said:
http://forum.xda-developers.com/showthread.php?t=1769497.
I am pretty sure this is the method I used to root 4.5.145 before I sold it
Click to expand...
Click to collapse
This worked for me too with 4.5.145, followed it exactly and had no problems. Thanks!
KetoSoi said:
Well, I've pretty much had it with this latest update (ATT, 4.5.145). I'd like to go back to .141 as its easily rootable. My Atrix is boot unlocked, and I have no interest in the custom ROMs. I dont have squat on the phone I need to keep, so I can blow the whole thing away as needed. I have the latest USB drivers and RSDlite ready to go.
I located the following ROM, and downloaded it... "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", appears to be the correct one.
I've been reading and reading and reading on the forums here (i.e. I've searched a lot), but theres a lot of cross-info, its hard to tell whats applicable in some situations.
So the question....
Which HowTo/Method/Guide would be most appropriate for my situation? Or is there something that would prevent this back-rev?
Thanks for any help or suggestions.
K
Click to expand...
Click to collapse
How did you unlock the bootloader for firmware 4.5.145? I've been looking everywhere on how to do it safely!
upndwn4par said:
The difference between what you posted (an SBF) and what I suggest (a fruit cake) is that an SBF is full stock firmware (bootloader, boot, system, radio, etc). It is the bootloader that causes the problems. Flashing an SBF is a crap shoot. You might do it 10 times without a problem, and the 11th time you hard brick your device. By hard brick I mean hard brick = your device is now a paperweight.
A fruitcake is essentially the same as a custom ROM. You are only flashing the boot and system images. This is always the best option for returning to stock.
However, you are in a different situation - uncharted waters so to speak. No one knows what to expect from 145. And since you don't have a custom recovery installed (CWM, TWRP, etc.) you can't just flash a fruit cake like you would flash a ROM. You should be able to use the fastboot method to flash the fruit cake, but again...uncharted waters.
I suggest trying the following in this order based on your current situation (options 1 and 2 assume you do in fact have an unlocked bootloader):
1) Fastboot flash a custom recovery, then try to flash the zip I posted on my rooting guide thread. If this works you will have rooted 145.
2) Fastboot flash a custom recovery, then flash the 141 fruit cake I made.
3) Fastboot flash the boot and system fruitcake images.
All the files and info you need can be found on my "Answers" thread and my rooting guide.
Do not flash an SBF until all else has failed. Let me know how things go with the above before you even consider this.
Edit:
Before you try any of the above, did you try UnlockRoot? It may work.
Click to expand...
Click to collapse
hello, ive been using 4.5.145 and was unable to root it, the problem with mine is that when I try to use the preinstall method it chokes when i type the "cp /preinstall/su /system/bin/... there was a message cp write error: no space left on device.. I have tried everything (almost) to root it but was unlucky.. then i saw this thread http://forum.xda-developers.com/showthread.php?t=2153422 ... i wanna try your suggestion but cant find the zip file in suggestion 1 and the 141 fruitcake you made on suggestion 2 and cant find file on option 3.. please do help me.. I have unlocked bootloader and have rom racers cwm.. thank you and more power..