Related
I just rooted my Nexus 1 Froyo per instructions on theUnlockr.com. I installed ADB first, Then proceded to root. I then flashed a recovery rom: recovery-RA-nexus-v1.7.0.1-cyan.img. This was successful. I then booted phone into recovery mode. Selected recovery and the first couple times I received a black screen with an exclamation point in the middle of a triangle next to green android. I flashed recovery rom once again and this time it allowed me to enter. I made my backup image and even booted into recovery mode again�wiped phone clean and restored image. I thought I was golden! Later I tried to boot into recovery mode again and I received same problem as mentioned above. I tried again no luck. I even flashed recovery rom again and It still dose not work. Why could this be happening? I even went through the steps to root phone again (that went well). But still no recovery mode. I even tried another recovery rom: recovery-RA-nexus-v1.7.0.1.img. It did the same thing. Worked one time and then nothing! I need to fix this before I load custom Roms.
Sent from my Nexus One using XDA App
follow this guide
http://forum.xda-developers.com/showthread.php?t=636795
Amritttt said:
follow this guide
http://forum.xda-developers.com/showthread.php?t=636795
Click to expand...
Click to collapse
I was able to flash recovery via your instructions but phone STILL will not boot into recovery mode. I hold down the volume key and power.....all I get is triangle with droid net to it. Im going to try and Un-root my phone and start from scratch! Thanks for the help!
you are getting the triangle with the droid because the recovery did not flash correctly, try usung rom manager if for nothing else, just to install Amon/clockwork
Poseidon20 said:
I was able to flash recovery via your instructions but phone STILL will not boot into recovery mode. I hold down the volume key and power.....all I get is triangle with droid net to it. Im going to try and Un-root my phone and start from scratch! Thanks for the help!
Click to expand...
Click to collapse
Did you remove the two scripts like you were told? /system/etc/install-recovery.sh and /system/recovery-from-boot.p
you are getting the triangle with the droid because the recovery did not flash correctly, try usung rom manager if for nothing else, just to install Amon/clockwork
Cool thanks for the advice! I did try Rom Manager and used Amon/Clockwork recovery. After flashing the Recovery Image I booted into recovery from Rom Manger. No problem! BUT.....when I rebooted phone from recovery menu I again went in to Rom Manager and tried to Boot back in to recovery and I got the triangle with the Droid next to it. I pulled battery and started phone again. I flashed Amon/Clockwork recovery again from Rom Mang. and again I was able to successfully boot in to recovery. This pattern goes on and on. It seams that every-time I want to boot into recovery I need to flash Amon/clockwork image. Somewhere phone is not retaining the information. Everything looks to work just fine as long as I Flash before I go into recovery. I'm sure this is not the way it should work. Any ideas?
khaytsus said:
Did you remove the two scripts like you were told? /system/etc/install-recovery.sh and /system/recovery-from-boot.p
Click to expand...
Click to collapse
Khaytsus,
When was I told to remove the two scripts? Where did this come from? Please let me know what they are for and why removing them would help? Also, if I do need to remove these would it be done by using Root File Manager, finding file and selecting delete? Sorry if I sound new to this.....it's because I am! LOL. Thanks for any help you can provide!
Try this.
http://forum.xda-developers.com/showpost.php?p=7378018&postcount=47
Poseidon20 said:
Khaytsus,
When was I told to remove the two scripts? Where did this come from? Please let me know what they are for and why removing them would help? Also, if I do need to remove these would it be done by using Root File Manager, finding file and selecting delete? Sorry if I sound new to this.....it's because I am! LOL. Thanks for any help you can provide!
Click to expand...
Click to collapse
It's documented in random places, of course the post below also has the same info. I don't know precisely what the two files do, but they apparently try to restore the recovery.
Trust me, it will fix the problem. Remove them, re-flash recovery.
khaytsus said:
It's documented in random places, of course the post below also has the same info. I don't know precisely what the two files do, but they apparently try to restore the recovery.
Trust me, it will fix the problem. Remove them, re-flash recovery.
Click to expand...
Click to collapse
Khaytsus,
You saved my Droid! You were right! deleting those 2 files worked. I'm well into flashing Custom ROMs. Your the only one who got it right! Good job! Thanks Again!
khaytsus said:
Did you remove the two scripts like you were told? /system/etc/install-recovery.sh and /system/recovery-from-boot.p
Click to expand...
Click to collapse
So, I'm not the OP, but I am having trouble deleting the files despite the fact that they are both say "YES" in read and write in properties. I tried to reflash from ROM Manager and I keep getting an error there. Not sure what to do.
BTW, I'm using a Galaxy Nexus. Would love some help as this is all uncharted terrain for me.
sadako12 said:
BTW, I'm using a Galaxy Nexus. Would love some help as this is all uncharted terrain for me.
Click to expand...
Click to collapse
You are in Nexus One Q&A Forum. Did you tryed with Galaxy Nexus Recoveries files and guides ?
ldFxl said:
You are in Nexus One Q&A Forum. Did you tryed with Galaxy Nexus Recoveries files and guides ?
Click to expand...
Click to collapse
I tried pretty much everything other than wiping the whole thing again. It's quite unfortunate.
sadako12 said:
I tried pretty much everything other than wiping the whole thing again. It's quite unfortunate.
Click to expand...
Click to collapse
If I understand, your problem is that you can't actually flash a custom recovery from ROM Manager ?
Which do you use ?
Are you trying to flash a recovery in recovery mode ?
Please link here files you tried to flash.
ldFxl said:
If I understand, your problem is that you can't actually flash a custom recovery from ROM Manager ?
Which do you use ?
Are you trying to flash a recovery in recovery mode ?
Please link here files you tried to flash.
Click to expand...
Click to collapse
I can't flash from ROM Manager. Initially, I didn't want to purchase the download capability. So, first, I used the program tools and flashed from there. I got Clockwork Mod to work, but then when I restarted it and went into "recovery," I got nothing.
Now, I can't flash at all.
The galaxy nexus should have fastboot capabilities, this is the best and safest way to flash your recovery partition
Be sure to use the proper recovery image for your device
If you need help finding it or setting up fastboot let me know
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
The galaxy nexus should have fastboot capabilities, this is the best and safest way to flash your recovery partition
Be sure to use the proper recovery image for your device
If you need help finding it or setting up fastboot let me know
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have only ever found a guide for a temporary flash. I would follow the instructions and then CWM wouldn't stick. =\
So here is the typical steps to follow
fastboot oem unlock
fastboot flash recovery nameofrecovery.img
And that's it, were you using fastboot to just boot it? Were you doing another method? The more details you give the faster and more accurate your help will be
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
So here is the typical steps to follow
fastboot oem unlock
fastboot flash recovery nameofrecovery.img
And that's it, were you using fastboot to just boot it? Were you doing another method? The more details you give the faster and more accurate your help will be
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I used instructions from http://androidforums.com/internatio...root-samsung-galaxy-nexus.html#enter-recovery.
The ROM wouldn't "stick" and then the USB wasn't even recognized by the end of everything.
Start by booting into your bootloader and writing down everything word for word on that screen here. Next boot to recovery and write down what you see there. Even better upload pics of each. Again the more detailed you can be the more help you can get
Sent from my Nexus 7 using XDA Premium 4 mobile app
Hi, I've a Nexus1 stock FRF91 ROM Rooted, and with an unlocked bootloader.
I had Amon RA Recovery 2.0 installed and all worked fine. After I known that FRG83D has been released, I've wanted to update to this version. I've tried in many ways, but I've discovered that it needed a stock recovery to flash it. I've tried to restore stock recovery, but now when I try to access it, the screen remain stuck, black, and I must to pull the battery to start a reboot. Could you suggest me how I can repair stock recovery, to obtain latest release?
Just curious, but what version is your bootloader?
Sent from my Nexus One using XDA App
Did you get the stock recovery img from an older build? Is your phone SLCD? If both are true, you flashed a recovery incompatible with your display. Try the recovery from the FRG33 PASSIMG.zip.
Sent from my Nexus One using XDA App
BTW, if you have hboot 0.35, you may not be able to do the PASSIMG...
Sent from my Nexus One using XDA App
he can simply flash a compatible stock recovery through adb
Here is a compatible recovery coming directly from my SLCD phone: http://gravufo.kicks-ass.org/Android/mtd1_Stock_Recovery.img
If you do not have flash_image, get it from here: http://cyanogen-files.carneeki.net/flash_image.zip
Please unzip it and put both the recovery image and the flash_image binary into your SD card and run these commands from your phone terminal emulator or through adb shell in window command line
su
mount -o rw,remount /dev/block/mtdblock4 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 775 /system/bin/flash_image
flash_image recovery /sdcard/mtd1_Stock_Recovery.img
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
How to know if my display is a slcd?
I will try and tell you if resolve
Sent from my Nexus One using XDA App
antognio said:
How to know if my display is a slcd?
I will try and tell you if resolve
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=gUF4dLVdFKc
RIGHT = SLCD
LEFT = AMOLED
Hy, I have the same problem with my nexus one (from Videotron, Québec)
I try your stock recovery and all I got is this /!\ logo in my screen... Have to take off the batery.
Now, I have 2.2.1 FRG83 ( no D ... )
So I will re-flash amon_ra 2.0... And wait for a solution from other since I'm a newbee in all this.
Gregore said:
Hy, I have the same problem with my nexus one (from Videotron, Québec)
I try your stock recovery and all I got is this /!\ logo in my screen... Have to take off the batery.
Now, I have 2.2.1 FRG83 ( no D ... )
So I will re-flash amon_ra 2.0... And wait for a solution from other since I'm a newbee in all this.
Click to expand...
Click to collapse
Hey Gregore, please check my website, made especially for Vidéotron customers.
There is a tutorial on how to get the stock recovery back in place with the exact same recovery that came with your Vidéotron Nexus One! Check it out, it's the last one...I assume you speak French, since everything is in french there
http://gravufo.kicks-ass.org/android.html
PS: Garde en tête que ce site est hosté sur mon ordi, donc si jamais il est offline, c'est que je dors!
Gregore said:
Hy, I have the same problem with my nexus one (from Videotron, Québec)
I try your stock recovery and all I got is this /!\ logo in my screen... Have to take off the batery.
Now, I have 2.2.1 FRG83 ( no D ... )
So I will re-flash amon_ra 2.0... And wait for a solution from other since I'm a newbee in all this.
Click to expand...
Click to collapse
The /!\ logo *is* stock recovery. Once you've hit that screen, you press some combination of the power button and one of the volume keys, I forget exactly which... try them all out... and you'll hit the stock recovery screen.
cmstlist said:
The /!\ logo *is* stock recovery. Once you've hit that screen, you press some combination of the power button and one of the volume keys, I forget exactly which... try them all out... and you'll hit the stock recovery screen.
Click to expand...
Click to collapse
Oh damn lol I misread his post and thought he wasn't getting the stock recovery in... well yeah, you simply have to press PWR and VOL Down(-) OR VOL Up(+) simultaneously and you'll get in.
Ignore my earlier post then (although there are some interesting if you speak french and want some extremely detailed tutorials on stuff )
hum... so I have all right... sorry bothering you guys, and thank you!
Stock recovery restored succesfully, but I can't obtain FRG83D update
antognio said:
Stock recovery restored succesfully, but I can't obtain FRG83D update
Click to expand...
Click to collapse
Just download it yourself from here: http://android.clients.google.com/p...signed-passion-FRG83D-from-FRG83.ecb21b75.zip
I never understood peoples fascination with the OTA update...
efrant said:
I never understood peoples fascination with the OTA update...
Click to expand...
Click to collapse
Just a feel good freebee...but flashing feels much better
Now I've frf91, I've tried to force update manually but obtain signature error
Sent from my Nexus One using XDA App
antognio said:
Now I've frf91, I've tried to force update manually but obtain signature error
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Flash Amom_RA 1.9 recovery and try it again.
efrant said:
Flash Amom_RA 1.9 recovery and try it again.
Click to expand...
Click to collapse
No, that will not work.
You need to manually update to FRG83 before being able to apply this update.
gravufo said:
No, that will not work.
You need to manually update to FRG83 before being able to apply this update.
Click to expand...
Click to collapse
Obviously that depends on which file he is using. If he is using the FRG83D from FRF91 then he does not need to update... but if he is using the FRG83D from FRG83, then yes he does...
efrant said:
Obviously that depends on which file he is using. If he is using the FRG83D from FRF91 then he does not need to update... but if he is using the FRG83D from FRG83, then yes he does...
Click to expand...
Click to collapse
Obviously, but the file you told him to download earlier was from FRG83...skip the attitude, I'm trying to help him, not trying to be mean to anyone.
[04/23]
It couldnt be easier
Download openZIO-clockworkmod-recovery-pack.zip
Extract to C:\
Run "m6000_setup.msi" in the CWM folder and Follow install.
**you may encounter software signature issues, just 'install software/driver anyway'.
Plug in your phone to USB, power down.
Boot to fastboot (Hold Send/End simultaneously til fastboot starts)
open a command prompt and navigate to the "CWM" directory
Code:
cd\
cd CWM
Fastboot boot into openzio_clockwork-recovery image
Code:
fastboot boot clockwork-recovery.img
Profit.
***You will Lose your Kyocera Logo once you RESTORE (due to the way cwm dumps the boot partition).
Please download the openZIO Boot Fix and install the zip with CWM.
This will flash the correct boot image and restore your Kyocera Logo.
-------
[03/22]
I have edited this initial post because I have found a workaround to get clockwork recovery to load on the ZIO without wiping data/cache.
Unfortunately, until Koush gets the module fixed to run remotely from our phones, you will need to be connected to a PC, and know how to use Fastboot.
blah blah DISCLAIMER blah: I am not responsible IN ANY WAY for people screwing up/bricking their phones as a result of using this image.
....old method deleted by OP....
Thanks go out to Hotaru for compiling this recovery image, and obviously to Koush for making clockworkmod recovery.
Remember to hit the "Thanks" button if I helped you.
try downloading ROM Manager from the Market and then having it install the recovery.
Our phone isnt in the phone model list.
Install from sdcard prompts me to install clockworkmod recovery first.
Sent from my Zio using XDA App
isnt there a custom recovery option???? bet you can save that image from the page to the sd card and then run it through rom manager???
BTW I hate rom manager LOL.... I tryied to use it to format my sd card for link2sd.... and it tried to boot thephone into boot or recovery or something.... and ended up completely factory resetting my phone
hell I had even installed a handfull of apps before it happend LOL and my dumb ass didnt do a TI backup....
dreamstryder said:
isnt there a custom recovery option???? bet you can save that image from the page to the sd card and then run it through rom manager???
....
Click to expand...
Click to collapse
How would this be accomplished?
Everytime I choose to install from SD, it prompts me to install clockworkmod recovery first
*edit: "Flash Alternate Recovery" is grayed out as well.
Sent from my Zio using XDA App
Maybe someone still running 1.6 could try and flash the M6000 recovery?
Spz0 said:
How would this be accomplished?
Everytime I choose to install from SD, it prompts me to install clockworkmod recovery first
*edit: "Flash Alternate Recovery" is grayed out as well.
Sent from my Zio using XDA App
Click to expand...
Click to collapse
'
betcha you have to have the premium version of clockwork to bwe able to flash alternate recoveries... I dont trust it enough right now to buy it and find out lol
dreamstryder said:
'
betcha you have to have the premium version of clockwork to bwe able to flash alternate recoveries... I dont trust it enough right now to buy it and find out lol
Click to expand...
Click to collapse
odd thing about it, is that I _do_ have premium. o.0
maybe you have to drop the image into a certain directory then?????? for clockwork to find it???
dreamstryder said:
maybe you have to drop the image into a certain directory then?????? for clockwork to find it???
Click to expand...
Click to collapse
/sdcard/clockworkmod/*
Nogo either.
how did the people get rom manager to see thier custom recovery when they was experimenting with sprints 2.1 stuff???
dreamstryder said:
how did the people get rom manager to see thier custom recovery when they was experimenting with sprints 2.1 stuff???
Click to expand...
Click to collapse
Well, we used fastboot to load it up.
Then used adb to tell it to boot into recovery. There was also some key combo I forget. It's all around page 30 or so of the 1.6 thread.
What do we need to do to make clockworkmod work?
Sent from my from my rooted 2.2 no bloat Zio using XDA App
I'd suggest that we all send an email to koush at clockworkmod asking for support.
I'm working on building a compatible version, but I'm running into all sorts of build issues.
Sent from my Zio using XDA App
What's the email address?
Sent from my Zio using XDA Premium App
Those images generally need to be flashed through fastboot, and fastboot might not even work depending on the bootloader.
you need the sdk installed first, and adb working and added to your $path.
after that
Code:
adb reboot bootloader
Code:
fastboot flash recovery /path/to/recovery.img
obviously, replace path/to/recoery with the actual path that you downloaded the file to.
That revocery image (I found out) is for the 1.6 OS.
Being as we have 2.2 and an updated kernel: would this recovery still work?
Guess I'll be the guinea pig for this afternoon. o.0
edit:
adb reboot bootloader is for our modem download mode.
To access fastboot, we just power down, then hold the power/end and send key simultaneously.
recovery only cares about the hardware, not the os or kernel, thats why you use it to flash custom roms and kernels. It boots before anything else is loaded.
Spz0 said:
adb reboot bootloader is for our modem download mode.
To access fastboot, we just power down, then hold the power/end and send key simultaneously.
Click to expand...
Click to collapse
Thanks good to know. Thanks.
option94 said:
recovery only cares about the hardware, not the os or kernel, thats why you use it to flash custom roms and kernels. It boots before anything else is loaded.
Click to expand...
Click to collapse
Nice also good to know :-D
I'll flash it when I'm home and post results.
Sent from my Zio using XDA App
BEING UPDATED!!! Wait for revision!!!
EVERYONE READ THIS LINK FIRST ABOUT INTERNATIONAL PUDDING
.
ATT/Orange/Bell/Telestra/Latin America ONLY
.
.
.
ATT and International IHOP!
This guide will help you to unlock your atrix bootloader and flash gingerbread 2.3.4
.
You must update your phone to the latest firmware before doing this guide!
If you just bought the Atrix it is not up to date out of the box!
.
*att 1.8.3 required. 3 bricks confirmed from users not being on 1.8.3 before unlocking the bootloader!
* changed the thread to have the 1.8.3 pudding full rom instead of just the bootloader to have a higher success rate. July 14, 2011 10:00pm PST*
If you do not have version 5.1.0 of the motorola drivers uninstall your drivers and install the ones from this post.
Warning!!! After unlocking your bootloader do not flash any OTA updates or sbf roms after unlocking!
You can and will hardbrick your device!
MAKE SURE your BATTERY has a FULL CHARGE before your attempt to unlock or flash anything!
Flashing from a laptop? Use the back ports!
Click to expand...
Click to collapse
[Guide] Upgrading to Gingerbread 2.3.4
Download all software to start hacking your atrix.
1. Download and install rsdlite
http://forum.xda-developers.com/attachment.php?attachmentid=634879&d=1308872277
2. Download and install the motorola atrix windows drivers
64 bit
http://forum.xda-developers.com/attachment.php?attachmentid=634880&d=1308872277
32 bit
http://www.megaupload.com/?d=JS6SW5ZE[/QUOTE]
3. Reboot your pc after installing the drivers.
4. ATT Users download the ATT Pudding
5. Download my combined atrix tools package for windows. UPDATED WITH IHOP!
http://www.multiupload.com/TSV9YJGG2Z
6. Extract the zip for the combined atrix tools package for windows to C:\atrix
....If att extract the 183_pudding.rar with winrar to C:\atrix
When finished the contents of C:\atrix should look like this
adb.exe
adbwinapi.dll
adbwinusbapi.dll
fastboot.exe
moto-fastboot.exe
IHOP_Bell.sbf
183_pudding.sbf *att only
Unlock your atrix bootloader
1. Put the phone in RSD MODE
a) power the phone off
b) hold power and hold volume up
2. Flashing pudding
a) open rsdlite
b) connect the phone to the pc
c) click the ...
ATT USERS
d) browse and find C:\atrix\183_pudding.sbf
INTERNATIONAL USERS
d) browse and find C:\atrix\IHOP_Bell.sbf
Click to expand...
Click to collapse
e) select the phone in the lower panel after the status area says "connected..."
f) click start
g) wait for the flash to complete and reboot the phone
h) after the phone is all the way back in android to the lock screen unplug the phone
i) power the phone off
j) close rsdlite3. Put the phone in fastboot mode
a) power your phone off
b) hold power and volume down
c) hit volume up (this should start fastboot mode)
4. Unlock the phone
a) open a command prompt on your windows pc
b) type the following in the command prompt
cd C:\atrix
fastboot oem unlock
Click to expand...
Click to collapse
c) it should then display something like the following in your command prompt
Unlocking your device can permenently VOID your warranty.
This process cannot be reversed. If you wish to proceed,
reissue the unlock OEM command containing the unique ID
of your device: XXXXXXXXXXXXXXXXXXX
OKAY [ 0.002s]
finished. total time: 0.002s
Click to expand...
Click to collapse
d) type the following replacing XXXXXXXXXXXXXXXXXXX with the unique ID from the previous command prompt.
fastboot oem unlock XXXXXXXXXXXXXXXXXXX
Click to expand...
Click to collapse
e) Type the following to reboot your device
fastboot reboot5. Uninstall RSDlite from your computer using the (add remove programs) or (programs and features) control panel
How to flash CWM Recovery(tenfar's)
1. Download the tenfar's CWM recovery
http://forum.xda-developers.com/attachment.php?attachmentid=641508&d=1309404399
2. Extract the recovery.img from the zip file to C:\atrix
3. rename the extracted recovery image file from the zip from
recovery-en-goapk-XXX-XXX.img to recovery.img
4. Put the phone in fastboot mode
a) Power your phone off
b) Hold power and volume down
c) hit volume up (this should start fastboot mode)
5. Flash the recovery.img
a) open a command prompt on your windows pc
b) type the following in the command prompt
cd C:\atrix
moto-fastboot flash recovery recovery.img
moto-fastboot reboot
Click to expand...
Click to collapse
How to flash Gingerbread 2.3.4 via CWM recovery
do not flash an ATT radio to a international phone. search for your radio!
* You can also use this same procedure to install a custom kernel like faux123's
1. Choose the Rom/kernel you want to use from the Atrix Android Development forum
ATT Roms
kennethpenns 2.3.4 rom (very stable)
http://forum.xda-developers.com/showthread.php?t=1159385
Cherryblur rom is also available
http://forum.xda-developers.com/showthread.php?t=1160649
International Roms
[fruitcakes]2.3.4 stock for international is in the second post of the thread
advanced user rom ( not a cwm zip installation )
[ROM & FIX] (fastboot) 2.3.4 OrangeFR (Jul5: 4.5.2A-11) w/ RAM fix for Intl. unlocked
http://forum.xda-developers.com/showthread.php?t=1169409
Click to expand...
Click to collapse
2. Put the CWM zip file on your sdcard (sdcard-ext)
3. Load recovery
a) power off your phone
b) hold power and volume down
c) hit volume down 6-7 times to cycle through the menu to "Android Recovery"
d) hit volume up
Click to expand...
Click to collapse
4) Install the CWM Zip
a) use volume down to select install zip from sdcard
b) hit the power button
c) use the volume button to select external sdcard
d) hit power button
e) hit the volumme button until you reach the cwm zip you want to install
f) hit the power button
g) hit the volumme button until you reach the confirm install line
h) hit the power button
Click to expand...
Click to collapse
5) Clear /data and /cache and /davlike cache
* if your phone goes into a boot loop after flashing a rom or kernel this is always the first thing to try.
Put the phone in fastboot mode.
a) Power your phone off
b) Hold power and volume down
c) hit volume up (this should start fastboot mode)b) type the following in the command prompt
cd C:\atrix
moto-fastboot -w
moto-fastboot reboot
Click to expand...
Click to collapse
[/INDENT]
Click to expand...
Click to collapse
Grats!
FAQ
Q: Does this void my warranty?
A: Yes
Q: why after I flash CWM recovery do i get a android guy instead of the recovery menu?
A: Read this post for the solution. We said do not apply ota updates!
Q: How can I downgrade my atrix after I unlock?
A: Flash one of the FruitCake Roms
Q: Can I brick my atrix?
A: Yes they're is always that chance. Here are some simple things to remember that can save your phone from a hard brick.
1. Always make sure you have a full charge prior to flashing.
2. Once you are free of motorola stay that way.
3. Do not flash sbf files to restore to stock if you mess up. reflash the CWM zip or fastboot images
4. Do not flash ota updates.
3. After you unlock the only time you should ever have to use rsdlite again is to flash a radio.
4. moto-fastboot and cwm are the primary ways to flash a rom.
5. Again stop flashing with rsd lite after you unlock your bootloader.
6. update to the latest offical ota updates before unlocking.
Q: Why doesn't my mss/smms/data/etc work now
A: Read this thread on fixing your APN's
*More To be posted here when users have more questions.
Thanks and comments
I was getting tired of helping users in IRC and decided to create this thread to make the complete process easier to understand.
I wish to thank everyone of the dev's at xda atrix for making all of these solutions.
Thanks the2dcour, eval, unknown, edgan, eval, kennethpenn, sogarth, designgears, tenfar, Ronaldo9 and my girl friend Aubrey Strand for dealing with my flashing addiction. If I missed anyone please send me a pm and I will add you to this list of dev's that need credit in this thread.
Does it matter what version you are on to flash pudding?
Sent from my MB860 using XDA App
Javi97100 said:
Does it matter what version you are on to flash pudding?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
4.1.8.3 fresh is the best to start from.
Sent from my MB860 using XDA Premium App
Just to add, MAKE SURE your BATTERY has FULL CHARGE before your attempt to unlock. I had a HARD BRICKED phone when my Battery was around 40% charge while trying to unlock using SBF...
Thanks for this! It's always way more helpful when somebody takes all the various threads and information and consolidates it into one thread.
Maybe as questions are asked, edit the original post to include a FAQ section with all the questions and answers....this way, the same **** isn't being asked 25,000 times.
Well thanks for posting but I think this information is already out there. Unless you are looking for this to be stikied, this can be moved to general section.
Sent from my MB860 using XDA Premium App
ceo.mtcl said:
Well thanks for posting but I think this information is already out there. Unless you are looking for this to be stikied, this can be moved to general section.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
ceo.htcl,
I am very aware that the information is out their.
but the other guides in general are basically just links to other threads.
this is a actual complete guide.
If this needs to be in general then a mod can please move it, but a lot of the beginners look here in dev and never look in general.
faux123 said:
Just to add, MAKE SURE your BATTERY has FULL CHARGE before your attempt to unlock. I had a HARD BRICKED phone when my Battery was around 40% charge while trying to unlock using SBF...
Click to expand...
Click to collapse
adding this now. thanks faux123. btw I love your r2 release kernel. it is the bomb.
awesome thanks will be using this!
Great! Super helpful... Thanks!
sent from my Dual Core Tegra 2 Beast... the Motorolla Atrix 4G!
Well done. I concur that it was probably needed.
Great job. I seriously needed this Sunday/Monday after I went out and upgraded my Captivate to the Atrix. It took quite a while to compile all the information scattered out there to get the job done.
One thing I would add, which was driving me crazy, once you install the drivers, you need to reboot the computer, otherwise RSD Lite will not recognize the phone. I think this is for Windows XP only.
ceo.mtcl said:
Well thanks for posting but I think this information is already out there. Unless you are looking for this to be stikied, this can be moved to general section.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
I would like to add to this thread. I am unlocked with Ken's 2.3.4 Rom on my atrix, but it was very frustrating to get because of one prerequisite step- Tenfar's CWM.
Since all developers are using the CWM as a prerequisite, someone needs to write a clear guide on how to get it. I had to read through that entire thread, and ask for help to successfully flash it.
It was just aggravating to go through that much for a supposedly minor step. It took me 24 hours! BULLSH!T.
Sent from my MB860 using XDA App
Is there a chance of hard bricking my device if I flash pudding?
Sent from my MB860 using XDA App
Dell2 said:
I would like to add to this thread. I am unlocked with Ken's 2.3.4 Rom on my atrix, but it was very frustrating to get because of one prerequisite step- Tenfar's CWM.
Since all developers are using the CWM as a prerequisite, someone needs to write a clear guide on how to get it. I had to read through that entire thread, and ask for help to successfully flash it.
It was just aggravating to go through that much for a supposedly minor step. It took me 24 hours! BULLSH!T.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I am confused.
this is already in the guide.
the part for installing recovery is tenfars cwm recovery
Javi97100 said:
Is there a chance of hard bricking my device if I flash pudding?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
their is always a chance.
to prevent this make sure your phone is charged 100% first.
and read the pudding thread that is a sticky at the top of the dev forum for more information, risks, etc.
s2h2golf said:
Great job. I seriously needed this Sunday/Monday after I went out and upgraded my Captivate to the Atrix. It took quite a while to compile all the information scattered out there to get the job done.
One thing I would add, which was driving me crazy, once you install the drivers, you need to reboot the computer, otherwise RSD Lite will not recognize the phone. I think this is for Windows XP only.
Click to expand...
Click to collapse
thanks. added the reboot.
Dell2 said:
I would like to add to this thread. I am unlocked with Ken's 2.3.4 Rom on my atrix, but it was very frustrating to get because of one prerequisite step- Tenfar's CWM.
Since all developers are using the CWM as a prerequisite, someone needs to write a clear guide on how to get it. I had to read through that entire thread, and ask for help to successfully flash it.
It was just aggravating to go through that much for a supposedly minor step. It took me 24 hours! BULLSH!T.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
to make it more clear that this is tenfar's cwm recovery I added his name to that section.
joe ferreira said:
I am confused.
this is already in the guide.
the part for installing recovery is tenfars cwm recovery
Click to expand...
Click to collapse
Uh no, that's what I'm talking about, he states it as a step, that's it. He doesnt give you directions on how to do it, he just tells you to do it. It's supposed to be simple, but look at how many posts are in that thread. Too many posts for a simple step.
Sent from my MB860 using XDA App
Dell2 said:
Uh no, that's what I'm talking about, he states it as a step, that's it. He doesnt give you directions on how to do it, he just tells you to do it. It's supposed to be simple, but look at how many posts are in that thread. Too many posts for a simple step.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
oh i get it. your saying that I made it clear and understandable how to actually flash tenfars cwm recovery to the atrix. ok.
btw I also just added more information about bricking and how to avoid it.
I've been struggling installing custom roms on my phone so I figured I'd document the process to help out anyone else starting out. I'd like to thank everyone for helping me figure this out and for the hard work of the community for making this possible.
Edit: My goal was to come up with a way to install CM9 while leaving the original system it came with and all my settings and apps. I understand how to do TitaniumBackup and how to save specific apps/files to but I wanted an exact backup of my original system alongside any custom rom so I just wrote down the steps I used to make it happen.
Root the system
1.First apply one click root using this tool
Further instructions here: http://forum.xda-developers.com/showthread.php?t=1319653
http://dl.xda-developers.com/attach.../7/6/DooMLoRD_v4_ROOT-zergRush-busybox-su.zip
Droid 3 CWM (ClockWorkMod)
2. Install this apk onto the phone and click the first button then the second button
http://forum.xda-developers.com/attachment.php?attachmentid=882933&d=1328117678
3. Boot into recovery and make a backup of your system
4.Apply Fastboot package for UMTS XT860 Iusacell Mexico using RSD Lite 5.5
Further instructions here:
http://rootzwiki.com/topic/4370-sbf...959-and-56890/page__view__findpost__p__100987
XT860 Iusacell: http://www.fileserve.com/file/cgdZ2..._SLU-57M-111107-release-keys-Latam-01.xml.zip
RSD Lite: http://www.multiupload.com/T6NOEBKKLO
5. Reroot using 2.3.6 Zerg tool
Basically after flashing with RSD Lite then re-root using this tool:
http://dl.xda-developers.com/attach.../7/6/DooMLoRD_v4_ROOT-zergRush-busybox-su.zip
6.Re-install CWM (Droid 3 Bootstrapper from step 2) and then apply the Bell rar file as a nandroid restore.
Further instructions here: http://forum.xda-developers.com/showpost.php?p=21446640&postcount=112
https://rapidshare.com/files/1705579381/ClockworkMod_v.5.0.2.6_Bell_2.3.6.rar
7. Reboot into the system and let the OS load again then re-install cwm (no need to reroot) and reboot back into recovery.
the trick to booting into recovery the second time is to turn the phone off, hold the m key while pressing the power button, plug in the phone to usb, choose bp tools
source: http://forum.xda-developers.com/showpost.php?p=21474818&postcount=120
restore your original backup from step 3 using advanced restore and restore the Data only and then wipe cache and dalvik cache
8. Remove CWM and install safestrap instead it involves using adb shell and removing certain files instructions found here:
http://www.droidforums.net/forum/dr...d-help-removing-clockworkmod.html#post1801072
9. Install SafeStrap once CWM is removed just install it, reboot and press the menu key while booting
http://dl.xda-developers.com/attach...5/7/9/2/5/Droid3_Safestrap_Tweaked_v1.08d.apk
10. ICS Install, at this point you have prepped your system so you can install CM9 otherwise it won't boot on the stock Bell 2.3.4
Instructions here: http://forum.xda-developers.com/showpost.php?p=22254669&postcount=61 (start at step 8 or 9 in those instructions)
-Apply CM9 Alpha 6 Zip
http://www.hash-of-codes.com/files/cm9-droid3-20120130-1730.zip
-Apply XT860 Sub-Patch (by Rick#2) for ICS Zip
http://bit.ly/Ah5b6d
Further instructions here: http://hash-of-codes.blogspot.com/p/how-to-safestrap.html
Great tutorial
As a note, in step 6, you could flash any custom rom to /system. You might not be able to restore /data though. Can try and if no go do a data wipe. If you backup apps with titanium backup and call logs/sms/mms with mybackroot its not such a big deal. Just redownload those 2 apps and restore everything(honestly I rarely nandroid, only if im doing something im confident will end in a fastboot flash, I just use those 2 apps). Im running liberty in /systemorig and eclipse in /system
Sent from my XT860 using xda premium
Also zergrush should root anything I believe 2.2.x and up. You could save the hassle of getting one click. AFAIK anyways. When I first rooted I used the one click as well(way back when it first came out)but I know it roots 2.3.5 and 2.3.6 and works on other models as well. Originally for one of the Sony experia phone
Sent from my XT860 using xda premium
Endoroid said:
Also zergrush should root anything I believe 2.2.x and up. You could save the hassle of getting one click. AFAIK anyways. When I first rooted I used the one click as well(way back when it first came out)but I know it roots 2.3.5 and 2.3.6 and works on other models as well. Originally for one of the Sony experia phone
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Thanks for the tip I wouldn't have been able to get this far without your help Endoroid. I'll edit the How-To to use the same root twice, I wish mods would sticky more useful posts like zerg's root instead of pete's root and How-To such as this one.
Thanks for the detailed tutorial. I'm on Bell 2.3.6, rooted. Step 2 did not work for me. I could install the program (droid3 CW bootstrap) and click the first button (with "success" popup), but reboot into recovery would not work. It would simply boot up normally. If I held "m" down then I could get to the blackscreen menu, scroll down and select BP tools, but still, a normal bootup would follow.
I used root explorer to check for what the bootstrap program did. In /system/bin/ directory was the "hijack" file as well as a modified "logwrapper" and the original "logwrapper" which was renamed to "logwrapper.bin". Uninstalling the bootstrap did not remove these. To manually uninstall, I removed hijack, logwrapper and renamed logwrapper.bin to logwrapper.
I also tried Koush's Rom Manager from the Market and selected "Droid 3" as the device, but it also would not achieve a boot into CWM Recovery menu.
I tried the two programs separately and then together, but it made no difference.
My next step was to try Safestrap Recovery v1.08 from hash-of-codes. This installed and has allowed me to boot into the green recovery menu after powering down fully, holding "m" and pressing the power button. On the next black screen, scrolled down to "bp tools" with volume down button and then pressed volume up to select it. I went into "backup and restore" and created a nandroid backup of my current 2.3.6 Bell system. (volume up/down to scroll, power button to select).
Sorry if I'm being verbose with the button presses but thought it might help for future reference and maybe for others as well.
Question now is which step to go to now... do I try using RSDLite to flash the fastboot package for Iusacell Mexico file? If I understand correctly, this will change the radio and also there is no going back at this point to stock Bell.
I'm concerned about warranty service if something goes wrong and there's no still no Bell SBF to flash back to stock. Would it be that noticeable? If I restored my nandroid backup, would I still be on the upgrade path with Bell? If I restored the backup and deleted safestrap recovery, would it show?
ncho2233 said:
Thanks for the detailed tutorial. I'm on Bell 2.3.6, rooted. Step 2 did not work for me. I could install the program (droid3 CW bootstrap) and click the first button (with "success" popup), but reboot into recovery would not work. It would simply boot up normally. If I held "m" down then I could get to the blackscreen menu, scroll down and select BP tools, but still, a normal bootup would follow.
I used root explorer to check for what the bootstrap program did. In /system/bin/ directory was the "hijack" file as well as a modified "logwrapper" and the original "logwrapper" which was renamed to "logwrapper.bin". Uninstalling the bootstrap did not remove these. To manually uninstall, I removed hijack, logwrapper and renamed logwrapper.bin to logwrapper.
I also tried Koush's Rom Manager from the Market and selected "Droid 3" as the device, but it also would not achieve a boot into CWM Recovery menu.
I tried the two programs separately and then together, but it made no difference.
My next step was to try Safestrap Recovery v1.08 from hash-of-codes. This installed and has allowed me to boot into the green recovery menu after powering down fully, holding "m" and pressing the power button. On the next black screen, scrolled down to "bp tools" with volume down button and then pressed volume up to select it. I went into "backup and restore" and created a nandroid backup of my current 2.3.6 Bell system. (volume up/down to scroll, power button to select).
Sorry if I'm being verbose with the button presses but thought it might help for future reference and maybe for others as well.
Question now is which step to go to now... do I try using RSDLite to flash the fastboot package for Iusacell Mexico file? If I understand correctly, this will change the radio and also there is no going back at this point to stock Bell.
I'm concerned about warranty service if something goes wrong and there's no still no Bell SBF to flash back to stock. Would it be that noticeable? If I restored my nandroid backup, would I still be on the upgrade path with Bell? If I restored the backup and deleted safestrap recovery, would it show?
Click to expand...
Click to collapse
First, you may wish to just go with safestrap and try flashing g rom in safe mode. If it bootloops no harm done because your bell /system is intact
If that fails you can try using motofastboot instead of rsdlite to just flash /system. You can restore your /system with your nandroid.
As far as I know roms should work with bell 2.3.6.
If you do end up flashing the whole fastboot package with rsdlite you can make your phone appear to be bell stock. You can restore your nandroid and then mod the build.prop so about phone shows bell info. The warranty guys would have to look deep to see its been changed.
Its up to you ultimately but as I said I don't think you would have to flash the fastboot. Safestrap should work as is on bell 2.3.6. As long as you don't mess with /systemorig (nonsafe mode) its easy to remove the evidence. Uninstall safestrap recovery and remove su/superuser
If I recall correctly dasilva had his issue due to being on 2.3.4 and unable to update.
Sent from my XT860 using xda premium
Thanks Endoroid. I went ahead and tried installing Rick#2's latest patched version of CM9 and to my great surprise it worked and the phone has booted up running ICS. I'm pretty happy since I didn't think this was possible without losing the ability to get back to Bell stock and right now, I think it's still possible since I didn't flash any other country's fastboot files. Is this right?
ncho2233 said:
Thanks Endoroid. I went ahead and tried installing Rick#2's latest patched version of CM9 and to my great surprise it worked and the phone has booted up running ICS. I'm pretty happy since I didn't think this was possible without losing the ability to get back to Bell stock and right now, I think it's still possible since I didn't flash any other country's fastboot files. Is this right?
Click to expand...
Click to collapse
Correct
Safestrap was built with the idea of keeping your phone intact. You can still easily receive OTA updates and can return your phone to stock if you need to get warranty repair done
Sent from my XT860 using xda premium
dasilva333 said:
XT860 Iusacell: http://www.fileserve.com/file/cgdZ2..._SLU-57M-111107-release-keys-Latam-01.xml.zip
Click to expand...
Click to collapse
This file is necessary, but alas fileserve is gone... All the links on the web point to just that one location.
Does someone have it? Can someone upload it?
白い熊 said:
This file is necessary, but alas fileserve is gone... All the links on the web point to just that one location.
Does someone have it? Can someone upload it?
Click to expand...
Click to collapse
+1
1of16 said:
+1
Click to expand...
Click to collapse
Personally, I like the Bell version the most, it has the least amount of Blur. You can find an entire SBF database here:
http://sbf.droid-developers.org/
Sent from my XT860 running ICS
danifunker said:
Personally, I like the Bell version the most, it has the least amount of Blur. You can find an entire SBF database here:
http://sbf.droid-developers.org/
Sent from my XT860 running ICS
Click to expand...
Click to collapse
Thanks, and I can use it on my XT862 too?
is it possible to install the latest OTA (5.7.906), which I want to use as stock rom?