CM7.2 successfully installed on Droid 2 with 2.3.4 firmware - Droid 2 General

Hi folks, I'm completely new -- not only to this forum, but to rooting phones and installing different firmwares in general. So I apologize if this post is somehow inappropriate. As far as I can tell though, nobody else has succeeded with this and posted about it before, so I just wanted to give a heads up that it is possible.
I've got Cyanogenmod 7.2 working on my Droid 2, which had a 2.3.4 firmware.
First I rooted the phone using phifc's process: http://forum.xda-developers.com/showthread.php?t=1773391
Downloaded CM7.2, and blanked out the /system/etc/check_kernel script to "exit 0" per this post on the CM forum: http://forum.cyanogenmod.com/topic/50469-installing-cm-from-234/#entry335479
Then I loaded CM7.2 with ClockworkMod Recovery.
Then a would get a boot loop with every reboot. I got past this by performing the following steps:
-Entered the recovery menu by holding 'X' and hitting the power button
-Brought the menu up by hitting both volume rockers simultaneously (The hourglass button didn't work)
-Cleared the caches
I wanted to make a post with all of this information in one place, to save others the hours of searching around I had to do.
EDIT: I forgot the kernel check script step.

D'oh, I just saw supercuttom's post on the CyanogenMod forum below the one I linked, so that's one person that got it working and posted about it. Sorry :-}
hrothmund said:
As far as I can tell though, nobody else has succeeded with this and posted about it before, so I just wanted to give a heads up that it is possible.
Click to expand...
Click to collapse

Related

[Q] Backing-up and flashing

Hey, guys (and girls? )! Just got a new DEFY+ couple of days back and I'd like to get the most out of it. It's already working all smooth and sexy, but I'm sure it can do better. So I need some assistance
Phone info:
DEFY+ (MB526)
Android 2.3.4
System 45.0.74.MB526.Retail.en.DE
Kernel 2.6.32.9-gbad50c3
Build 4.5.1-134_DFP-74
I've rooted it yesterday and I'm pretty sure it was successful, since the phone is working and I've got SuperUser on it since then (I've followed the root part of the all-in-one super DEFY guide thread)
About backing up, I would like to be able to go back to my old backup at any time. Is that even possible? I know I probably never will go back to it, but I like to play things safe. If it is possible, could you teach me how or point me to some nice guide/thread on that?
When it comes to flashing, I'd like to try CM, WAJKIUI and MS2G. Any more ROMs that are a must try? Now, I didn't quite understand... Are there different versions for defy and defy+? Or...which ROMs are compatible with defy+? I've read somewhere that all defy ROMs can't use defy+'s battery properly, so that's what concerns me. Nandload? How to?
I'm sorry if these are stupid questions, I've tried finding out everything from the guides, but I just didn't find enough information... I do have RSD (v5.0.0, is it okay?) and the drivers, all set up. I'm not asking for anyone to write an essay for me, it will be perfectly fine if you just point me to some (really really) good guides. I'll be grateful for any and every answer!
*EDIT #1* Well, I've tried to learn some more... Let's go step by step. Should I install 2ndInit app or some other custom recovery app?
I can beg if need be
"*EDIT #1* Well, I've tried to learn some more... Let's go step by step. Should I install 2ndInit app or some other custom recovery app?"
Hi,
as I've seen the guides, yes.
I've defy, so I didn't try it, but heard from many people with defy+ with CM or MIUI.
BUT before it I suggest to you:
- get a stock sbf of your rom. It is necessary if you want get back the original factory state. hope here you find it: http://forum.xda-developers.com/showthread.php?t=966537
- install titanium backup from market (I know this, but you can install any similar app) and make a full backup (all user and system app). It saves all data, installed apps with settings ...
- make backup of your contacts and sms-s with stock app (it is possible I think)
- make backup of your sd content
After that you can install 2ndinitdefy. Follow the instructions in the program. I suggest 1.4.2 version. If it doesn't work go to 2.0. The 2.0 has instructions not on the main screen but in its menu.
After the 2 reboot (regarding 2ndinit install) you can do a nandroid backup with clockworkmod recovery.
Reboot, push vol down at blue led (after start with 8-10 sec). You are at bootloader. Use vol up/down to navigate and power to enter a menu. Go to recovery-> custom recovery->backup and recovery->backup all. It takes some time. You can save this nandroid to computer (just for safety ) You find it in sd/clockworkmod/backup.
Now you have backups. Go ahead, install the custom rom of your choice.
I recommend WajkIUI. You find the link in my signature and you find installing instructions in Wajk's first post. And of course there are defy+ users in that thread as I remember, you can ask question there.
ps: everything is your responsibility
Was it helpful? Just use thank button
Good luck bro/sis !!!
Thank you for such a long reply!
I have installed 2ndInit, using the v2.0 installer, but I chose the stable version of the 2nd init itself, instead of the latest one. That stable one said it was meant for CM and MIUI, so I'm guessing I'll be alright with WajkIUI as well!
I'll follow the steps you gave me for making a complete backup of everything on my phone and then I'll start looking for a ROM that's fully mb526 compatible (I need >10 posts to be able to post in the development section :/ )
P.S. I'm a bro
I see. This 10 post rule a bit annoying. But as I know you can send private message to anyone. In the Wajkiui thread there are some people with 526.
I've got my 10 posts Thank you once more and I'm sure we'll be talking again soon!
I'm having a hard time finding a full SBF of my stock ROM...
It's 4.5.1-134_DFP-74 (Android 2.3.4)
I don't really understand the codes in that name, so can someone please tell me if I could flash some close to this sbf if I ever need to? I've found some with just that value after "...DFP-" different. Would they be okay?
Please let me know! I wanna load up something different, but don't want to do so until I have a full sbf as well, just in case of emergency
niksy+ said:
I'm having a hard time finding a full SBF of my stock ROM...
It's 4.5.1-134_DFP-74 (Android 2.3.4)
I don't really understand the codes in that name, so can someone please tell me if I could flash some close to this sbf if I ever need to? I've found some with just that value after "...DFP-" different. Would they be okay?
Please let me know! I wanna load up something different, but don't want to do so until I have a full sbf as well, just in case of emergency
Click to expand...
Click to collapse
You should ask Walter79. I found similar sbf as yours in his thread /forum.xda-developers.com/showthread.php?t=966537/ at "my roms" link:
www.4shared.com/folder/YpyTOtp4/Defy-roms.html
Bests
Mate, thanks for the info, but I've already found and flashed a full .sbf The topic said it was 2.3.4, while it turned out to be 2.3.5, but I don't mind, got my phone working again after a failed flashing of cm7.2..!
Cheers

Help! ICS bootloader v3 issue.

Can someone help me?
I installed ICS bootloader v3 exactly like Civato's guide told in the developers forum. All went fine. But now I have tried different roms on my device. Problem is like this. Rom boots normally and I can use it, but when device go to sleep example I press the power button. If I press the power button again tablet won't wake up. I need to press power button long time to shut it up and then boot the device again. What went wrong? Can someone help?
yawn....sleep of death
joucca said:
Can someone help me?
I installed ICS bootloader v3 exactly like Civato's guide told in the developers forum. All went fine. But now I have tried different roms on my device. Problem is like this. Rom boots normally and I can use it, but when device go to sleep example I press the power button. If I press the power button again tablet won't wake up. I need to press power button long time to shut it up and then boot the device again. What went wrong? Can someone help?
Click to expand...
Click to collapse
yeh. yeh its the SOD hundreds of posts about it!!! ....may have something to do with the different roms you've tried...but then it may not....
flash back to hc to get rid of it....and wait for the official ics ota..
reflash v3 again.....and hope it works
go read some of the posts and see if u can come up with your own fix
joucca said:
Can someone help me?
I installed ICS bootloader v3 exactly like Civato's guide told in the developers forum. All went fine. But now I have tried different roms on my device. Problem is like this. Rom boots normally and I can use it, but when device go to sleep example I press the power button. If I press the power button again tablet won't wake up. I need to press power button long time to shut it up and then boot the device again. What went wrong? Can someone help?
Click to expand...
Click to collapse
That is because all the custom ICS except Flexreaper install the wrong boot.img. go to my flexreaper thread and flash one of the kernels for ICS bootloader users. You can use it on my flexreaper and on lightspeed. Taboonay got its own ICS kernel for ICS bootloader users so look in that thead. Icylisous only works on HC bootloaders so that one you cannot use.
do this and.your sod will be gone.
I've got a question related to this here.
Please help me out.
Its regarding my CPUID
SOLVED
Thanks to all.
Does someone know download link for HC bootloader. And installation guide would be nice too. I am a newbie with tablets....
Sent from my GT-I9001 Broodrom RC5 using XDA
civato said:
That is because all the custom ICS except Flexreaper install the wrong boot.img. go to my flexreaper thread and flash one of the kernels for ICS bootloader users. You can use it on my flexreaper and on lightspeed. Taboonay got its own ICS kernel for ICS bootloader users so look in that thead. Icylisous only works on HC bootloaders so that one you cannot use.
do this and.your sod will be gone.
Click to expand...
Click to collapse
That finally answered my biggest question of the last days. Thanks.
Thanks a lot.
Now running Flexreaper 12.5, and works perfectly....
That's fine. But next time use the search function before creating a new thread.

[Q] Tmous Defy Green Lens - No stock recovery

I'm usually very resourceful; search, read, and try to resolve my own issues with the many threads online and here on xda but I am at a complete loss at this point and hope one of you can give me some guidance.
I have a Tmobile US Defy. Green Lens. I was able to root and install cwm. It was on Android 2.2.1.
I wanted to make sure everything was ok prior to beginning to flash anything so i downloaded JORDN_U3_6.36.0_SIGNED_USAJRDNTMOB1B4B5DE1028.0R_JORDANTMO_P022_HWp3_Service1FF.sbf
This obviously reverted my Android to 2.1 but upon completely booting it begins to slow to a freeze on my homescreen within a minute or two.Completely freezes. It did not prompt me to enter Blur account and if there isn't a SIM in, it will not allow me to interact with the phone beyond emergency calling. I can't update through OTA since it just locks up.
Thought I'd try to wipe/reset. I'm able to get to the android guy with the exclamation point but pressing vol up/down does not get me into recovery. I've tried many button variations as well.
I'm not sure what I need to do at this point anymore. I can enter bootloader (v9.10) still and use RSD but I'm afraid to flash non US sbf files.
Any help would be greatly appreciated. I apologize if this has already been covered. I've been searching and reading for the last 6 hours and have no idea what to do next.
If you under 2.1 and you are on the screen with the android guy have you touched the screen above the magnifier.
Much Appreciated
RATTAR said:
If you under 2.1 and you are on the screen with the android guy have you touched the screen above the magnifier.
Click to expand...
Click to collapse
I did not do that. Thank you! Sorry for such a ridiculous/pointless [Q]. I spent hours reading and never ran across such a simple solution. Everything was smooth sailing after that simple suggestion on your part; tried out a few different ROMs here and there already. Thank you again!

FIXED - Hard Brick Atrix

I included this in another thread but thought it might help more if it had its own thread.
Problem:
SVF:105:1:2
Failed to boot 0x1000
SOLUTION:
Download: http://dl.dropbox.com/u/23255832/Atrix Unlock/AUTOMATIC_UNLOCK_V4.2.zip
Download the program
- Once unzipped in a folder open the file MAIN
- Do the repair first (option 3)
- It gives you instructions as you go
- Then I did option 1, follow instructions and chose 2.3.4
- Phone is alive again
- Then I did option 3 and followed instructions.
Thats it, easy.
What a waste of a day. Do the repair first, then reload and you're good to go.
I just noticed the link doesn't work. It was an automatic root/cwm dos program that had a menu if anyone knows what I am talking about. I just cleaned up my pc and can't seem to find it either. Will keep looking for it.
Found it!
http://forum.xda-developers.com/showthread.php?p=24472332#post24472332
Its labeled AUTOMATIC_UNLOCK_V4.2
jjj133 said:
I just noticed the link doesn't work. It was an automatic root/cwm dos program that had a menu if anyone knows what I am talking about. I just cleaned up my pc and can't seem to find it either. Will keep looking for it.
Click to expand...
Click to collapse
Here it is, from the link you posted on the other thread (found it through the list of your posts):
http://forum.xda-developers.com/showthread.php?t=1182871
A few problems:
This tool already has it's own thread. And it is already known that this tool fixes failed to boot errors (I mean, it is Option 3).
You should not post the thing in multiple threads.
This post does not belong in the dev section.
Edit:
Forgot to mention that I am glad you got your phone working again.
My Phone is showing following message:
SVF:105:1:2
Failed to boot 0x1000
NVFlash...
Nothing more, and it is actually shutting down after few moments automatically.
Any hope? I had this issue long time ago, and it is still there.
yeah same here 0x1000 and it reboots so can't i fix this? I try holding down the volume down and it restarts any help?
has anybody tried on bell atrix?
thks
This is softbrich. Hardbrick not fix.
Sorry guys, meant soft brick but I couldn't change the title after I wrote it. I just wanted to put it up because when I bricked mine it took me like 7 hours to find all of the info on how to do this. Maybe is better documented now (this happened months ago to me). Still, I wanted to post to help others. Hope it helps

Installing Atrix-MROM on an Atrix 4G with 4.5.145 update.

Just incase anyone with an Atrix 4G and 4.5.145 firmware, I followed the instructions in the following threads to successfully install Atrix-MROM on a brand new Atrix 4G ATT with the latest update.
1- Bootloader Unlock: http://forum.xda-developers.com/showthread.php?t=1182871
2- Root: http://forum.xda-developers.com/showthread.php?t=1769497
3- CWM Flash: http://wiki.cyanogenmod.org/w/Install_CM_for_olympus#Installing_recovery_using_fastboot
4- Atrix-MROM Flash: http://www.montuori.net/android-mrom/atrix-mrom/
Thank you Michael Montuori, the Atrix-MROM is awesome.
Rooting (step 2) is completely irrelevant and unnecessary. I've said this before. Still not sure why people constantly think rooting does anything if they're going to flash a new ROM anyway.
ravilov said:
Rooting (step 2) is completely irrelevant and unnecessary. I've said this before. Still not sure why people constantly think rooting does anything if they're going to flash a new ROM anyway.
Click to expand...
Click to collapse
I think this is because, normally, they would need it to flash CWM. But it doesn't happen on Atrix. .
Yeah, that's pretty much what I thought. People scarred/traumatized by other brands/phones and thinking everything is the same on all the other ones.
Oh well. Hopefully they'll learn one day. Hopefully a little sooner than the Atrix REALLY becomes obsolete.
ravilov said:
Yeah, that's pretty much what I thought. People scarred/traumatized by other brands/phones and thinking everything is the same on all the other ones.
Oh well. Hopefully they'll learn one day. Hopefully a little sooner than the Atrix REALLY becomes obsolete.
Click to expand...
Click to collapse
This is my first smart phone, and I am absolute noob in this field.
I have been using Nokia 1216 and similar monochrome display phones before it.
In that case, I gues you're actually doing quite well really... If you came from mono dumbphones straight to this and have already flashed a custom ROM, that's actually kinda impressive.
Thanks!!!
Much thanks my friend I thoght I was stuck in 145, I applied numbers 1 and 3 and now Im unlocked and have CWM
pinofly said:
Much thanks my friend I thoght I was stuck in 145, I applied numbers 1 and 3 and now Im unlocked and have CWM
Click to expand...
Click to collapse
Glad it helped you.
pinofly said:
Much thanks my friend I thoght I was stuck in 145, I applied numbers 1 and 3 and now Im unlocked and have CWM
Click to expand...
Click to collapse
Please can you tell me, where i found the tool for unlock bootloader of step 1, because the link is outdated, thank you.
aarizaga said:
Please can you tell me, where i found the tool for unlock bootloader of step 1, because the link is outdated, thank you.
Click to expand...
Click to collapse
It is in that thread. You can search: automatic_unlock_v4.2.zip
Or here it is:
h t t p s:// w w w . d r o p b o x . com/s/sr6ooho4zf9wqvo/automatic_unlock_v4.2.zip
Scan it first..
The MROM is simply amazing. Best battery life so far trying the cm7 based roms!
Sent from my MB860 using xda app-developers app
I am a neewbie, and when i learned how to flash custom roms, i was wondering, it is really necesary to root if you want a custom ROM?
now i was clarified.
So if want original firmware, and root acces, i just need an unlocked bootloader? And for rooting, can i just flash a fruitcake?
Sent from my MB860 using xda app-developers app
Hi, Thank you mmontuori for the excellent Rom and hard work to do it, and to Ravilov for the help.
I want to thanks in the post of the MROM in the development forum, but I can't do it because I don't have enough posts.
Well I finish yesterday to put all in order, only my contacts information I fail to restore.
The Go Backup didn't work.
One question, I don't installed the sv kernel, is necesary? because I feel that the battery it drain very quickly.
The rest appear so far to work very well, checking the holo launcher.
are you 100% sure everything on first post works with an ATRIX 4G 4.15.1455 from AT&T wiht the original motoblur?
i am newbee but wants to learn. its probably could i kill the phone?
thx!
Atrix 4g ATT 4.5.145 working well with CM 7.2
I have an Atrix 4g that was about to be retired or sold, and decided to instead make it an android project to learn about modding and possibly make something useful out of an old device.
After combing the forums on this site and others, realized there was some risk involved of a hard brick, but since this is not my main phone anymore, I wasnt too worried about. I'll share the results...
The phone was running gingerbread 2.3.6, ATT 4.5.145 build
#1) Root phone (http://forum.xda-developers.com/showthread.php?t=1769497)
Step 10 did generate an error for me, I had to issue the alternate command and it worked fine.
I downloaded root checker by JOEYKRIM on google play store to ensure it was rooted properly afterwards.
#2) Backup the phone in case of trouble (I used titanium backup from google play store, requires rooting from step 1)
Add a schedule to backup all and execute the schedule now. Pretty easy stuff
#3) Unlock bootloader (http://forum.xda-developers.com/show....php?t=1182871)
This is probably the most dangerous step. I used the link above and would like to add a few comments. The link above is a script written to automate the process for those not terribly familiar with the android tools ADB and fastboot. This script is capable of unlocking your bootloader, fixing some common problems that happen along the way, and installing clockworkmod so you can access android recovery mode to install custom ROMs. However, it seems to come with an older version of the clockworkmod, therefore I used it for the bootloader only (option 1 from main menu). I also had to execute option 3 afterwards as I did get the failure to boot 0x1000 error. Long story short.. I used option 1, then option 3 and skip the rest.
#4) PUSH ROM files of your choice to phone (I used Cryogenmod 7.2 latest from http://download.cyanogenmod.org/?device=olympus)
You should also copy any other addon ROMs of your choice to the phone at this time as well. Google store app is one that is not included with CM 7.2 and you can get here (make sure to pick the one for the version of CM you are choosing) http://wiki.cyanogenmod.org/w/Google_Apps
To push the files to your phone, simply boot your phone in the stock ROM, connect it to your PC with usb, and make sure the USB connection notification is set to USB mass storage. You can then copy the ROM files in zip form to the root directory of the drive letter of the phone from your PC just like you'd copy to a USB stick. Change the USB notification/communication mode on the phone back to stock setting of motorola phone app afterwards, as this dismounts the internal SDCARD storage and the phone wont remount it until you do.
This is out of order from some of the other guides. The reason to place the ROM files first before anything else, is so you can install clockworkmod to make recovery possible, then go right into it and install the ROMs from recovery mode. I had some issue with installing recovery with CWM first, then CWM not working if the phone booted into the stock rom (looks like the recovery was overwritten. I simply had to have the ROM files ready to go then do CWM all at once to make this work.
#5) Install CWM clockworkmod. (http://wiki.cyanogenmod.org/w/Install_CM_for_olympus#Installing_recovery_using_fastboot)
Follow the steps under installing recovery under fastboot. A link is provided for the latest CWM 5.0.2.0, which is what I used instead of the 4.0 version included in the unlock bootloader script mentioned in MY step 2.
At step 7, my phone appeared to hang at Flash boot: SOS. Some other users reported this as well. I just let the phone sit there for 3-5 minutes to make sure it was done with the operation. I then manually rebooted the phone holding down volume down button and holding power button until the phone powered down. If the phone is still connected to the PC, it will automatically power back on, so continue to hold the volume down until fastboot appears, then tapped volume down to cycle through the menu and chose Android recovery from the boot menu and press volume UP to execute it. CWM loaded up just fine and I was able to choose recovery ROMs we pushed in step #3 of my guide there and reboot.
Sorry if this is not as detailed as it could be, but I wrote this a bit after the fact without taking screenshots or writing down every step of the way. This is my best recollection of what I went through and figured I'd share as many consider this a gamble with the Atrix 4g and ATT 4.5.145.
Overall experience with the CM 7.2 ROM:
I've been running the phone for a bit now with cryogenmod 7.2 without issue. The battery life is fanastic and there are many nifty options included with CM 7.2 I have not experienced the random reboots or overheating some others have mentioned.
The only issues I've ran into so far, the latest youtube app from google store does not seem to play videos. You can install a QR code scanner app from google play store of your choice, then download the youtube app that worked for me via QR code from http://forum.xda-developers.com/showthread.php?p=18157961#post18157961
Additionally, internal storage (what's considered the SDCARD on this phone) was not mounted by default in CM 7.2. Reference this to fix it. http://forum.xda-developers.com/showthread.php?t=1481252
I hope this helps users out there with old Atrix 4g's considering giving them new life. I'm going to try CM 10.x soon to see how jellybean runs on the Atrix 4g. Wish me luck!
Vengaence
Vengaence said:
I have an Atrix 4g that was about to be retired or sold, and decided to instead make it an android project to learn about modding and possibly make something useful out of an old device.
After combing the forums on this site and others, realized there was some risk involved of a hard brick, but since this is not my main phone anymore, I wasnt too worried about. I'll share the results...
The phone was running gingerbread 2.3.6, ATT 4.5.145 build
#1) Root phone (http://forum.xda-developers.com/showthread.php?t=1769497)
Step 10 did generate an error for me, I had to issue the alternate command and it worked fine.
I downloaded root checker by JOEYKRIM on google play store to ensure it was rooted properly afterwards.
#2) Backup the phone in case of trouble (I used titanium backup from google play store, requires rooting from step 1)
Add a schedule to backup all and execute the schedule now. Pretty easy stuff
#3) Unlock bootloader (http://forum.xda-developers.com/show....php?t=1182871)
This is probably the most dangerous step. I used the link above and would like to add a few comments. The link above is a script written to automate the process for those not terribly familiar with the android tools ADB and fastboot. This script is capable of unlocking your bootloader, fixing some common problems that happen along the way, and installing clockworkmod so you can access android recovery mode to install custom ROMs. However, it seems to come with an older version of the clockworkmod, therefore I used it for the bootloader only (option 1 from main menu). I also had to execute option 3 afterwards as I did get the failure to boot 0x1000 error. Long story short.. I used option 1, then option 3 and skip the rest.
#4) PUSH ROM files of your choice to phone (I used Cryogenmod 7.2 latest from http://download.cyanogenmod.org/?device=olympus)
You should also copy any other addon ROMs of your choice to the phone at this time as well. Google store app is one that is not included with CM 7.2 and you can get here (make sure to pick the one for the version of CM you are choosing) http://wiki.cyanogenmod.org/w/Google_Apps
To push the files to your phone, simply boot your phone in the stock ROM, connect it to your PC with usb, and make sure the USB connection notification is set to USB mass storage. You can then copy the ROM files in zip form to the root directory of the drive letter of the phone from your PC just like you'd copy to a USB stick. Change the USB notification/communication mode on the phone back to stock setting of motorola phone app afterwards, as this dismounts the internal SDCARD storage and the phone wont remount it until you do.
This is out of order from some of the other guides. The reason to place the ROM files first before anything else, is so you can install clockworkmod to make recovery possible, then go right into it and install the ROMs from recovery mode. I had some issue with installing recovery with CWM first, then CWM not working if the phone booted into the stock rom (looks like the recovery was overwritten. I simply had to have the ROM files ready to go then do CWM all at once to make this work.
#5) Install CWM clockworkmod. (http://wiki.cyanogenmod.org/w/Install_CM_for_olympus#Installing_recovery_using_fastboot)
Follow the steps under installing recovery under fastboot. A link is provided for the latest CWM 5.0.2.0, which is what I used instead of the 4.0 version included in the unlock bootloader script mentioned in MY step 2.
At step 7, my phone appeared to hang at Flash boot: SOS. Some other users reported this as well. I just let the phone sit there for 3-5 minutes to make sure it was done with the operation. I then manually rebooted the phone holding down volume down button and holding power button until the phone powered down. If the phone is still connected to the PC, it will automatically power back on, so continue to hold the volume down until fastboot appears, then tapped volume down to cycle through the menu and chose Android recovery from the boot menu and press volume UP to execute it. CWM loaded up just fine and I was able to choose recovery ROMs we pushed in step #3 of my guide there and reboot.
Sorry if this is not as detailed as it could be, but I wrote this a bit after the fact without taking screenshots or writing down every step of the way. This is my best recollection of what I went through and figured I'd share as many consider this a gamble with the Atrix 4g and ATT 4.5.145.
Overall experience with the CM 7.2 ROM:
I've been running the phone for a bit now with cryogenmod 7.2 without issue. The battery life is fanastic and there are many nifty options included with CM 7.2 I have not experienced the random reboots or overheating some others have mentioned.
The only issues I've ran into so far, the latest youtube app from google store does not seem to play videos. You can install a QR code scanner app from google play store of your choice, then download the youtube app that worked for me via QR code from http://forum.xda-developers.com/showthread.php?p=18157961#post18157961
Additionally, internal storage (what's considered the SDCARD on this phone) was not mounted by default in CM 7.2. Reference this to fix it. http://forum.xda-developers.com/showthread.php?t=1481252
I hope this helps users out there with old Atrix 4g's considering giving them new life. I'm going to try CM 10.x soon to see how jellybean runs on the Atrix 4g. Wish me luck!
Vengaence
Click to expand...
Click to collapse
Cwm 5.0.2.7 is the up to date recovery (possibly outdated now, see new 4.3.1 for recovery (haven't tried it out yet))
Everything you just posted has already been mentioned over several threads over the past 3 yrs. We all are well aware of these instructions, long before you essentially copied, pasted, and edited into your own words, that detail the process of rooting, unlocking the bootloader, flashing a custom recovery, and flashing a custom ROM.
Sent from my MB886 using xda app-developers app
palmbeach05 said:
Cwm 5.0.2.7 is the up to date recovery (possibly outdated now, see new 4.3.1 for recovery (haven't tried it out yet))
Everything you just posted has already been mentioned over several threads over the past 3 yrs. We all are well aware of these instructions, long before you essentially copied, pasted, and edited into your own words, that detail the process of rooting, unlocking the bootloader, flashing a custom recovery, and flashing a custom ROM.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
The tone of your response implies that I'm trying to take some sort of credit for other people's work. The reason I posted is I've noticed some folks fairly recently with doubts about this process working specifically with this exact phone and ATT 4.5.145, and I wanted to share my experience and encourage others to do it if they were on the fence. I appreciate the work of this forum and other folks who have poured hours of time into these custom projects to make the android experience better.
I notice that you are a senior member. I'd suggest that replies are restricted on this forum to constructive responses, and not negative ones.
Thank you!
Vengaence said:
The tone of your response implies that I'm trying to take some sort of credit for other people's work. The reason I posted is I've noticed some folks fairly recently with doubts about this process working specifically with this exact phone and ATT 4.5.145, and I wanted to share my experience and encourage others to do it if they were on the fence. I appreciate the work of this forum and other folks who have poured hours of time into these custom projects to make the android experience better.
I notice that you are a senior member. I'd suggest that replies are restricted on this forum to constructive responses, and not negative ones.
Thank you!
Click to expand...
Click to collapse
Actually it was more along the lines of you were repeating things that have been said already time and time again. That was the true meaning of my post. I do apologize if it may not have been conveyed in a manner that my intention clear.
Also, the recovery. I just flashed the new one from the new 4.3.1 thread. It is indeed an update, bringing it up to revision 6.0.4.6. This is a huge step forward and lays the groundwork for 4.4 (most kk roms require at a minimum cwm 6.0.4.4)
Sent from my MB886 using xda app-developers app
CWM versions for Atrix 4g
palmbeach05 said:
Actually it was more along the lines of you were repeating things that have been said already time and time again. That was the true meaning of my post. I do apologize if it may not have been conveyed in a manner that my intention clear.
Also, the recovery. I just flashed the new one from the new 4.3.1 thread. It is indeed an update, bringing it up to revision 6.0.4.6. This is a huge step forward and lays the groundwork for 4.4 (most kk roms require at a minimum cwm 6.0.4.4)
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------------------
I notice you have an MB886, Atrix HD according to your signature. This thread is for the Atrix 4G. I'm not sure if you realized this. Maybe that is the reason why we are not seeing eye to eye. The Atrix 4g is older and is quirky and there have been many horror stories. I havn't seen many of those stories with the Atrix HD and things are more straight forward.
According to http://www.clockworkmod.com/rommanager
the latest CWM for the Atrix 4G is 5.0.2.0 and that's what is used by http://forum.xda-developers.com/showthread.php?t=2613829
as well to install later versions of CM such as 10.2 on the Atrix 4g. It's also what I used for CM 7.2
On your Atrix HD, CWM 6.0.4.x should be used.
Vengaence
Vengaence said:
--------------------------------------------------------------------------------------------------------------------------------
I notice you have an MB886, Atrix HD according to your signature. This thread is for the Atrix 4G. I'm not sure if you realized this. Maybe that is the reason why we are not seeing eye to eye. The Atrix 4g is older and is quirky and there have been many horror stories. I havn't seen many of those stories with the Atrix HD and things are more straight forward.
According to http://www.clockworkmod.com/rommanager
the latest CWM for the Atrix 4G is 5.0.2.0 and that's what is used by http://forum.xda-developers.com/showthread.php?t=2613829
as well to install later versions of CM such as 10.2 on the Atrix 4g. It's also what I used for CM 7.2
On your Atrix HD, CWM 6.0.4.x should be used.
Vengaence
Click to expand...
Click to collapse
Ah, correct and incorrect my friend. While my signature may point out what device i am currently on, it does not reflect my past. A peice of supporting evidence is over in AtrICS v2.0 (see home button fix)
As far as cwm goes, cwm has unofficial builds as well. Look through one of the threads, it will point you to a link about recoveries and there does exist a 5.0.2.8. EDIT It was Romracer's recovery, accesed through the unlock bootloadrr thread a few threads down from this one. The 5.0.8.x i think was more like a 5.8.1.8, but i think that was a touch version? Now CM and the other threads may say the 5.x is ok for all of our roms, but as android moves forward, so must our support from libs, apps, kernels, scripts, and of course, recoveries. That is why i promoted the 6.0.4.6 revision both here and in the new 4.3.1 thread.
Sent from my MB886 using xda app-developers app

Categories

Resources