I've tried installing ClockworkMod Recovery 5.0.2.0 and ClockworkMod Touch Recovery 5.8.1.8 on my AT&T Atrix 4G with the same results:
Flashing partition recovery
Flashing MBR to device
Flashing Stormgr partition: SOS
The result is that I can boot to recovery and flash CM7 to the phone, but ROM Manager does not recognize the recovery partition. To install CWM I used "fastboot erase recovery" and "fastboot flash recovery <cwm filename>". It was unlocked and rooted using Pete's Motorola Tools.
This has appeared on other threads that have been closed and appear to end around November 2011. I can't find a definitive answer in the forums - there appears to be disagreement on whether or not there is a reliable ClockworkMod Recovery image. Some tips refer to removing /system/etc/install-recovery.sh, but this file is not present.
Is this a known issue? Is there a fix? Have I missed something obvious?
tbazett said:
I've tried installing ClockworkMod Recovery 5.0.2.0 and ClockworkMod Touch Recovery 5.8.1.8 on my AT&T Atrix 4G with the same results:
Flashing partition recovery
Flashing MBR to device
Flashing Stormgr partition: SOS
The result is that I can boot to recovery and flash CM7 to the phone, but ROM Manager does not recognize the recovery partition. To install CWM I used "fastboot erase recovery" and "fastboot flash recovery ". It was unlocked and rooted using Pete's Motorola Tools.
This has appeared on other threads that have been closed and appear to end around November 2011. I can't find a definitive answer in the forums - there appears to be disagreement on whether or not there is a reliable ClockworkMod Recovery image. Some tips refer to removing /system/etc/install-recovery.sh, but this file is not present.
Is this a known issue? Is there a fix? Have I missed something obvious?
Click to expand...
Click to collapse
Same problem, can't locate an answer. Can someone weigh in, point us to the solution, etc.?
Thanks.
Edit: never mind. Touch removed, issue solved.
Phone: Atrix 4G (2.3.6)
Carrier: AT&T
I began this process with a stock phone. I wanted to install Cyanogenmod and was following the instructions listed on their site. The title of the article was 'Motorola Atrix 4G: Full Update Guide'. I was able to install the unlocked bootloader, but when I go to try and install CWM I am also receiving the:
Flashing partition recovery
Flashing MBR to device
Flashing Stormgr partition: SOS
messages. I have booted into the OS and browsed my /system/etc for anything called install_recovery.sh, but this file does not exist. I would love to continue installing Cyanogenmod, but have hit a brick wall.
Also if I boot into fastboot and do a 'fastboot erase recovery' I receive a different error:
StorMgr Formatting SOS
Any help is appreciated!
matrixx333 said:
Phone: Atrix 4G (2.3.6)
Carrier: AT&T
I began this process with a stock phone. I wanted to install Cyanogenmod and was following the instructions listed on their site. The title of the article was 'Motorola Atrix 4G: Full Update Guide'. I was able to install the unlocked bootloader, but when I go to try and install CWM I am also receiving the:
Flashing partition recovery
Flashing MBR to device
Flashing Stormgr partition: SOS
messages. I have booted into the OS and browsed my /system/etc for anything called install_recovery.sh, but this file does not exist. I would love to continue installing Cyanogenmod, but have hit a brick wall.
Also if I boot into fastboot and do a 'fastboot erase recovery' I receive a different error:
StorMgr Formatting SOS
Any help is appreciated!
Click to expand...
Click to collapse
That is not an error actually. That's how fastboot shows you are currently formatting Recovery partition (and it calls it SOS).
It happens when you erase or flash recovery. If you look closely, when you tell moto-fastboot to erase webtop, the phone calls it "osh".
I personally only use TWRP recovery, and I would recommend that over CWM (or CWM Touch).
vladeco said:
That is not an error actually. That's how fastboot shows you are currently formatting Recovery partition (and it calls it SOS).
It happens when you erase or flash recovery. If you look closely, when you tell moto-fastboot to erase webtop, the phone calls it "osh".
I personally only use TWRP recovery, and I would recommend that over CWM (or CWM Touch).
Click to expand...
Click to collapse
Thank you for the fast reply, but I also receive the exact same message when trying to install twrp 2.2.
*sigh*
matrixx333 said:
Thank you for the fast reply, but I also receive the exact same message when trying to install twrp 2.2.
*sigh*
Click to expand...
Click to collapse
Did you try rom manager. download it from the market and flash CWM through it.
matrixx333 said:
Thank you for the fast reply, but I also receive the exact same message when trying to install twrp 2.2.
*sigh*
Click to expand...
Click to collapse
I've come to the conclusion that it is an error, probably due to hardware, and it's not going to be fixed. The main disadvantage is that the ROM Manager app doesn't recognize the recovery partition so you can't use any of the features there that require it. I just use CWM directly and it seems to work just fine. I've been running CWM Touch, switching between CM7 and CM9 several times, for the past 5 months and it's good enough for backing up, recovering, and flashing.
harishatrix said:
Did you try rom manager. download it from the market and flash CWM through it.
Click to expand...
Click to collapse
harishatrix,
From reading the 'THE BEGINNERS (N00B) GUIDE!!! N00BS LOOK HERE FOR YOUR HOW TOs' information I was under the impression that rooting and unlocking the bootloader are two seperate things. I did unlock the bootloader, but I thought you had to 'root' the device in order to install ROM Manager. Am I mistaken?
tbazett said:
I've come to the conclusion that it is an error, probably due to hardware, and it's not going to be fixed. The main disadvantage is that the ROM Manager app doesn't recognize the recovery partition so you can't use any of the features there that require it. I just use CWM directly and it seems to work just fine. I've been running CWM Touch, switching between CM7 and CM9 several times, for the past 5 months and it's good enough for backing up, recovering, and flashing.
Click to expand...
Click to collapse
tbazett,
You said you use CWM directly. How do you do this? I thought you were getting the 'SOS' error when you tried to install CMW. Was there a work-around that you used to bypass this message?
matrixx333 said:
harishatrix,
From reading the 'THE BEGINNERS (N00B) GUIDE!!! N00BS LOOK HERE FOR YOUR HOW TOs' information I was under the impression that rooting and unlocking the bootloader are two seperate things. I did unlock the bootloader, but I thought you had to 'root' the device in order to install ROM Manager. Am I mistaken?
tbazett,
You said you use CWM directly. How do you do this? I thought you were getting the 'SOS' error when you tried to install CMW. Was there a work-around that you used to bypass this message?
Click to expand...
Click to collapse
If I remember correctly, it just stays at the SOS error message so I had to pull the battery to turn it off. After putting the battery back in I was able to turn it on, access the boot menu (using volume down button), and then boot up to the recovery partition.
I don't know what causes the error, but my guess is there is something at the very end of the process that fails, like a checksum or some sort of signature. The result is that it actually works fine on it's own but the ROM Manager fails to recognize it.
Tbazett,
Do you remember how long you waited before you pulled the battery? Im curious if im just not waiting long enough for the install to complete.
Also, would i access CWM by powering down, holding vol down + power, then use the vol down button to cycle to 'android recovery'?
Sent from my MB860 using xda app-developers app
HA! I just rebooted into android recovery for the heck of it and twrp 2.2 was installed successfully!!!
Now im on my way to modding!
Thanks again to everyone, I found everyone's advise helpful!
Sent from my MB860 using xda app-developers app
matrixx333 said:
HA! I just rebooted into android recovery for the heck of it and twrp 2.2 was installed successfully!!!
Now im on my way to modding!
Thanks again to everyone, I found everyone's advise helpful!
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Cool - check out CM9 from Jokersax. You just download the cm9 zip and the google apps zip and flash both in that order.
Here's the forum for it: http://forum.xda-developers.com/showthread.php?t=1445052
Related
I am running 2.2.2 Froyo with 1.77 build.
I unlocked and rooted via Gingerbreak.
I went into CWM Recovery, erased all cache and flashed Alien Rom v3 and immediately flashed the Alien theme over it (I think that is where I made my booboo). The Rom appeared to load perfectly yet when the phone restarted the Moto logo animation appeared to run then the screen would go dark. This process repeats every few seconds non stop.
I can get into Android Recovery, RSD, everything. I tried flashing the 1.8.3 sbf through RS Lite 5.3.1 and while it said "PASS" it still hangs at the Moto animation.
I have no idea what to do. I think I can get out of it as I have done A LOT of searching through the forums and google but I am terrible with CMD.
Any helpful and/or useful advice?
Try restoring a backup, if not try to flash a fruitcake
http://forum.xda-developers.com/showthread.php?t=1163009
Sent from my MB860 using XDA App
Thanks for the thread. However it looks like I need CWM Recovery in order to flash a fruitcake? I cant get the phone to boot past animation so this wont work...
Also I didnt create backups
noxlo said:
Thanks for the thread. However it looks like I need CWM Recovery in order to flash a fruitcake? I cant get the phone to boot past animation so this wont work...
Also I didnt create backups
Click to expand...
Click to collapse
Are you unlocked and flashed cwm through fastboot, or did you use the system recovery app?
Sent from my MB860 using XDA App
System recovery app. I can access Androids recovery (obviously) but not many options...
Did you unlock your bootloader?
I ran into the same issue the first time I tried to flash Alien. Since you're flashing Alien, I assume your bootloader is unlocked (As it's required for Alien).
If you have an unlocked bootloader, do this:
EDITED: Apparently, I'm a new user and can't post links. Go to the address bar and replace the number with 1163342
Use Fastboot to flash the boot.img and the system.img files. This will give you Gingerbread/Motoblur like it comes out of the box. (It's a start!)
Thanks for the link. Will try when I get home. If I can just get past cmd...
Things went from bad to worst, I fixed my market update and had the utlities on the device i needed to i tryed flashing the Neutrino Rom.
After it was done it rebooted and said "failed to boot 2 starting rsd".
So I downloaded RSD Lite and found the unlock SBF which I applied. Now I can get into the FastBoot menu's and go to Android Recovery and try to do the back to stock option, it says it completes then reboots...
Then it just sits and sits and sits on the motorola Dual core logo.
Can someone please help me here. I cant seem to find any of my backups i made with system recovery or rom manager. I also didnt load RomRacers Recovery (which i just now noticed)
Any help is greatly appreciated.
So, did you unlock the bootloader before trying to flash the ROM?
Does it say "Unlocked" at the boot logo now?
Get back into fastboot and flash romracer's recovery and then try to mount the storage and get another rom on there.
SDRAKE101085 said:
Things went from bad to worst, I fixed my market update and had the utlities on the device i needed to i tryed flashing the Neutrino Rom.
After it was done it rebooted and said "failed to boot 2 starting rsd".
So I downloaded RSD Lite and found the unlock SBF which I applied. Now I can get into the FastBoot menu's and go to Android Recovery and try to do the back to stock option, it says it completes then reboots...
Then it just sits and sits and sits on the motorola Dual core logo.
Can someone please help me here. I cant seem to find any of my backups i made with system recovery or rom manager. I also didnt load RomRacers Recovery (which i just now noticed)
Any help is greatly appreciated.
Click to expand...
Click to collapse
i unlocked the bootloader after the update failed (i panicked) and yes it does say unlocked at the top now
Well, you mentioned you can get into fastboot so that's a start. You can try to flash a proper recovery and try to boot into recovery and see if you can mount the storage, or if you have a card reader you can just put a ROM on your sd card and then flash. If you can't get into recovery but you can get into fastboot you can flash a rom that way. You'll have to search for the procedure but I'm almost certain it can be done. If all else fails, you can install the unlocked "Full" SBF through RSD Lite, but it is not really recommended but should work.
SDRAKE101085 said:
i unlocked the bootloader after the update failed (i panicked) and yes it does say unlocked at the top now
Click to expand...
Click to collapse
Thanks so much. I got radracers on there and reflashed the neutrino rom again. Everything appears to be working. Now to just figure out the rest.
Thanks again.
Look tke the sd card and load the rom and google apps. Then go and fastboot wipe and re install the rom and try to boot honestly it just sounds like you got a corrupted rom
Hi!
Today my phone rebooted and stucked in fastboot mode. No recovery, no reboot is possible I don't know why...
So, I tried to download clockworkmod flashable img, and tried to flash it with:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.7-p500.img
But I receive a wrong dimension error. If after that I try another time to flash, it get stuck apparently sending the image (but in fact it doesn't send anything). If I reboot the situation doesn't change.
How can I get outside this loop, preferrably without flashing the original image?
Thank you!
there are guides for it all over the forum
No, if you read all my message i said that i receive that message, and this situation isn't covered in any of the forum guides.
Anyway, i succeded flashing the amon-ra recovery, then the clockworkmod recovery again and from that I could access my installed system without troubles (and after a nandroid backup of course).
I leave this if everyone else happens to see that error message. For me some patience, amon-ra and not the standard guides worked!
aleritty said:
No, if you read all my message i said that i receive that message, and this situation isn't covered in any of the forum guides.
Anyway, i succeded flashing the amon-ra recovery, then the clockworkmod recovery again and from that I could access my installed system without troubles (and after a nandroid backup of course).
I leave this if everyone else happens to see that error message. For me some patience, amon-ra and not the standard guides worked!
Click to expand...
Click to collapse
Happy for you, although maybe you had a bad file or something.. who knows at least you're good now
btw, when it happend to me i didn't use the guides in here as well, CMW did work.
I created this thread because I have looked all over and have been unable to find someone with the exact same issue(s).
I said "sort of" in the title because twrp is working. Ok, so before everyone asks if I have nvflash, the answer is no. I did not have the right version of firmware, and did not try to install it originally. Since I was able to install roms, I figured I was fine...oops.
Twrp is not properly installing roms. More on that later. I am getting to the asus splash screen that says my device is unlocked, but it is stuck there.
My last working rom was the deodexed stock JB rom from craig gomez. I installed it with goo and when I installed that, I lost custom recovery and root, so I decided to go back to a more custom rom so Titanium backup would work. When I did that, I tried also tried again to make nvflash work. I got through the first step, it said it was successful, except I never got the little message in the upper left corner that I was supposed to get. I did not think it was a big deal because my prime would still boot like normal.
Then I installed twrp 2.3.1.0 and I have tried flashing previous restore images. I have tried installing the roms on my sdcard. I cannot get past the asus splash screen.
If I try installing a rom with the force md5 check enabled, it does detect an md5 and then quits.
If I try intalling a rom without the force md5 check, i get an error that says E:Unable to mount '/staging'
When I try installing a backup everything seems to work okay, but then I get the same error E:Unable to mount '/staging'
When I try to install roms through fastboot, I get the following errors:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
When I try using adb, I do not see any devices.
I tried putting CWM on the prime to see if I could install from that instead, but it would not load after install.
I tried putting an older version of twrp on the prime, to see if that was the issue because I used to have an older version...I could not get that to load either...so I went back to this version.
Any ideas or suggestions would be awesome guys. I am stuck.
I even went to install the naked drivers again, and when I try to flash a different recovery, I get the <waiting for device> text that never goes away.
i'm sort of on the same boat. my prime just keeps booting into twrp recovery no matter what i tried. i'm still hoping to find a solution to this problem.
godlyitem said:
i'm sort of on the same boat. my prime just keeps booting into twrp recovery no matter what i tried. i'm still hoping to find a solution to this problem.
Click to expand...
Click to collapse
For me, I can let it try to boot normally, but I get stuck at the splash screen. This device is unlocked.
If I hold down the volume down button, I can go to fastboot, or RCK for recovery...but it does not work properly.
big time noob said:
For me, I can let it try to boot normally, but I get stuck at the splash screen. This device is unlocked.
If I hold down the volume down button, I can go to fastboot, or RCK for recovery...but it does not work properly.
Click to expand...
Click to collapse
i just tried to flash cwm in the terminal, it wrote stuff on the memory, but didn't seem to do anything. it booted straight back to twrp. i can't even get it to go to fastboot!!! only if i can go to fastboot, i could save my prime!!!
godlyitem said:
i just tried to flash cwm in the terminal, it wrote stuff on the memory, but didn't seem to do anything. it booted straight back to twrp. i can't even get it to go to fastboot!!! only if i can go to fastboot, i could save my prime!!!
Click to expand...
Click to collapse
Yeah, I thought that too, but fastboot does not work properly either...argh. I wish one of the gurus would chime in here.
Same Here.. It all happened when i restored my files using titanium backup and when i rebooted im stuck at boot scrren
EDIT: Guys I did a prime fullwipe and flashed stock jb and now prime is restored to its original state..
""I also got some errors like md5 file could not be found and could not find the /staging""..but after the reboot it works perfect
EDIT 1: Now after the prime fullwipe and flashing stock jb i flashed twrp recovery and now it works perfect without a single error even the above mentioned errors were gone
mercydia said:
Same Here.. It all happened when i restored my files using titanium backup and when i rebooted im stuck at boot scrren
Click to expand...
Click to collapse
EVERYONE i fixed it!!!!!!!!!!!!!!!!!! !!!! it's alive again!!!!!!!!!!!!!!!!!
godlyitem said:
EVERYONE i fixed it!!!!!!!!!!!!!!!!!! !!!! it's alive again!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
That doesn't really help us. If possible, can you edit/delete your message so that the guys that might help do actually help? Don't want them to think this is done.
Can you clarify what the Prime fullwipe is and how you got there?
I do not know if it will help me.
I can't even do the wipe command from fastboot.
Just says <waiting for device>
I have tried the wipe command form the boot screen (the one with fastboot and RCK as options), that did not work properly either.
Ryan
mercydia said:
Same Here.. It all happened when i restored my files using titanium backup and when i rebooted im stuck at boot scrren
EDIT: Guys I did a prime fullwipe and flashed stock jb and now prime is restored to its original state..
""I also got some errors like md5 file could not be found and could not find the /staging""..but after the reboot it works perfect
EDIT 1: Now after the prime fullwipe and flashing stock jb i flashed twrp recovery and now it works perfect without a single error even the above mentioned errors were gone
Click to expand...
Click to collapse
big time noob said:
Can you clarify what the Prime fullwipe is and how you got there?
I do not know if it will help me.
I can't even do the wipe command from fastboot.
Just says <waiting for device>
I have tried the wipe command form the boot screen (the one with fastboot and RCK as options), that did not work properly either.
Ryan
Click to expand...
Click to collapse
here is what i did. get into twrp recovery. flashed full prime wipe -> right after that flash the stock jb US version directly dled from Asus -> reboot then you will be stuck at the splash screen (that's a good news). Hold down power + volume down until your prime turns off and restart (keep holding those two keys) until the 3 icons appear then flash w/e rom you want in recovery. It's alive!
In twrp I do not see anything that says Full Prime Wipe. I see something that says wipe. Are those the same? I tried doing a wipe from this screen, but it did not work for me as expected.
godlyitem said:
here is what i did. get into twrp recovery. flashed full prime wipe -> right after that flash the stock jb US version directly dled from Asus -> reboot then you will be stuck at the splash screen (that's a good news). Hold down power + volume down until your prime turns off and restart (keep holding those two keys) until the 3 icons appear then flash w/e rom you want in recovery. It's alive!
Click to expand...
Click to collapse
big time noob said:
In twrp I do not see anything that says Full Prime Wipe. I see something that says wipe. Are those the same? I tried doing a wipe from this screen, but it did not work for me as expected.
Click to expand...
Click to collapse
no full wipe is a stand alone zip file you have to google and find dl it. put it in your prime then flash it
Thanks. That is what I needed to know.
I will see if I can make this work when I get back from work.
godlyitem said:
no full wipe is a stand alone zip file you have to google and find dl it. put it in your prime then flash it
Click to expand...
Click to collapse
I am pretty sure I am F***ed.
I tried the prime full wipe. It worked the first time, I think. Then went to install a rom.
I had to do both through external SD in twrp because my adb is not working. Also, fastboot only works to install a recovery. The only version of any recovery I can make work is twrp 2.3.1.0
If I try an older version or CWM, it freezes where I try to go into recovery.
Unable to mount data error.
Unable to mount system error.
Same as before.
I tried using unbricker software I found, but since adb does not work properly, the software does not work properly.
I am going to see if I can work my charm and get them to take back my tablet at best buy for an infinity. I have read about other people pulling it off.
I think as we get closer to xmas my odds improve...UNLESS SOMEONE HAS ANOTHER IDEA??? I would love to try something else.
Eyeballer suggested a chat room channel thing, but most of the people are in europe and I would need to do it in the morning...I do not have time for that, but I may try it.
big time noob said:
Can you clarify what the Prime fullwipe is and how you got there?
I do not know if it will help me.
I can't even do the wipe command from fastboot.
Just says <waiting for device>
I have tried the wipe command form the boot screen (the one with fastboot and RCK as options), that did not work properly either.
Ryan
Click to expand...
Click to collapse
Download the zip:
http://goo.gl/hiFHB
Goto to Twrp recovery and install the zip..Since it supports microsd u can transfer the zip to microsd.
Goto TWRP -> INSTALL -> CHOOSE EXTERNAL SD -> INSTALL THE ZIP
It will completely wipe the internal storage and then download the official STOCK JB FROM ASUS SITE and follow the same steps to install. Now install the latest twrp recovery using fastboot
big time noob said:
I am pretty sure I am F***ed.
I tried the prime full wipe. It worked the first time, I think. Then went to install a rom.
I had to do both through external SD in twrp because my adb is not working. Also, fastboot only works to install a recovery. The only version of any recovery I can make work is twrp 2.3.1.0
If I try an older version or CWM, it freezes where I try to go into recovery.
Unable to mount data error.
Unable to mount system error.
Same as before.
I tried using unbricker software I found, but since adb does not work properly, the software does not work properly.
I am going to see if I can work my charm and get them to take back my tablet at best buy for an infinity. I have read about other people pulling it off.
I think as we get closer to xmas my odds improve...UNLESS SOMEONE HAS ANOTHER IDEA??? I would love to try something else.
Eyeballer suggested a chat room channel thing, but most of the people are in europe and I would need to do it in the morning...I do not have time for that, but I may try it.
Click to expand...
Click to collapse
When I was doing the fullwipe the same errors happened to me.. But dont mind..I got errors like
1. No md5 file found
2. Mount error
3. Cannot find /staging
Just follow the above the steps ull get it right
did you even follow my step by step guide? you can move the stock rom from external SD to your internal SD in advance -> file manager.
godlyitem said:
did you even follow my step by step guide? you can move the stock rom from external SD to your internal SD in advance -> file manager.
Click to expand...
Click to collapse
Yeah, I should have said I tried that first. I also tried the stock rom from asus. When that didn't work, I tried the stock rom deodexed I found in goo.
There are a bunch of permission errors going on inside my prime. When I go into the mount area, it will not let me mount the data to move it. Or, when I try to copy it over I get a failed message.
Okay. I wiped it again, from twrp.
Then it let me move the file from the ext-sdcard to the sdcard.
I used the prime full wipe.
Then I tried to install the stock rom by transferring it in twrp file manager.
I got the file onto the sdcard, but when i tried to install, it said Failed.
That was it.
I even tried installing the ICS version I got from ASUS. Same thing.
Now, I am going to try to access via unbricker...don't know if it will work, but I am out of ideas.
godlyitem said:
did you even follow my step by step guide? you can move the stock rom from external SD to your internal SD in advance -> file manager.
Click to expand...
Click to collapse
Fixed?
I am alive!
us-tf201-jro03c-10.4.2.15-stock-deodexed.zip
That is the last rom I successfully used.
I used all sorts of different wipes. I was in twrp and noticed my pc installing the transformer adb driver. So I hopped into adb to see if it would see my device with that driver. (it did, but it wasn't before from the fastboot or adb commands with naked driver).
I tried sideloading the above rom from twrp. It worked.
Thought others might want to know.
I do not know if I can install other roms or not. I am a little scared to try just yet.
big time noob said:
Okay. I wiped it again, from twrp.
Then it let me move the file from the ext-sdcard to the sdcard.
I used the prime full wipe.
Then I tried to install the stock rom by transferring it in twrp file manager.
I got the file onto the sdcard, but when i tried to install, it said Failed.
That was it.
I even tried installing the ICS version I got from ASUS. Same thing.
Now, I am going to try to access via unbricker...don't know if it will work, but I am out of ideas.
Click to expand...
Click to collapse
big time noob said:
I am alive!
us-tf201-jro03c-10.4.2.15-stock-deodexed.zip
That is the last rom I successfully used.
I used all sorts of different wipes. I was in twrp and noticed my pc installing the transformer adb driver. So I hopped into adb to see if it would see my device with that driver. (it did, but it wasn't before from the fastboot or adb commands with naked driver).
I tried sideloading the above rom from twrp. It worked.
Thought others might want to know.
I do not know if I can install other roms or not. I am a little scared to try just yet.
Click to expand...
Click to collapse
You will have the jelly bean bootloader now so as long as you stick to it you should be fine. The only other thing I would suggest is check you version of twrp, you should be running the jelly bean version of it also. And if I am not mistaken, you need to be on ics to use nvflash (although I haven't checked the op recently so I could be wrong) so definitely stay away from that unless you downgrade.
Okay my Atrix 4g has unlocked bootloader, Android 2.3.6, and I flashed CWM recovery the other day, and it worked fine except whenever I plugged in my phone to wall charger, it would boot AUTOMATCALLY into that recovery. Followed this guide: LINK
I then installed CWM recovery 5.0.2.3 from here: LINK
Now again when I plug usb into wall to charge, it boots into the first recovery I installed. I can't see the battery charge symbol.
Now I downloaded this ROM - http://forum.xda-developers.com/showthread.php?t=1836674 and tried to boot into recovery from using the volume down button until "Android recovery" but that takes me to the stock 4 option crap.
So I tried to flash the MROM from ROM manager in the os, and it says restarting into recovery, AGAIN that takes me to the triangle exclamation point crap.
SO MY QUESTION is if I do a disk clear, format from the recovery, would my phone still work with T-mobile afterwards, and I can install the CWM again, and flash the new ROM?? I don't care about losing data, I have only few apps.
Here's a crazy idea - did you by any chance install the recovery image on the BOOT partition instead of the RECOVERY partition?
If you can't do it manually, there is no point in trying with ROM manager, since it can't do anything you can't do yourself.
ravilov said:
Here's a crazy idea - did you by any chance install the recovery image on the BOOT partition instead of the RECOVERY partition?
If you can't do it manually, there is no point in trying with ROM manager, since it can't do anything you can't do yourself.
Click to expand...
Click to collapse
Here's a crazier idea - do you mind explaining things in more detail, since I am a noob and this is a help forum.
--
When I install the the recovery, it just says hit yes to continue. Please help, rather than telling me that I am an idiot.
Apologies, didn't mean to imply you're stupid or anything. I said "crazy" because it is very unlikely but your symptoms kinda point to exactly that. This can easily happen actually - both the boot image and the recovery image are of the exact same structure (kernel + ramdisk) and the partitions that hold them are both exactly the same size (8 MB). The only difference is, with recovery the ramdisk launches an user interface and never leaves it, while with boot the ramdisk chains to booting your normaly system. Never tried it, but I believe if one flashes recovery on the boot partition, the end result would be that the phone boots into recovery every time you'd expect it to boot normally.
How exactly did you flash recovery? Don't link me to a thread or a procedure but rather describe what you did, what commands you issued and what was the response.
ravilov said:
Apologies, didn't mean to imply you're stupid or anything. I said "crazy" because it is very unlikely but your symptoms kinda point to exactly that. This can easily happen actually - both the boot image and the recovery image are of the exact same structure (kernel + ramdisk) and the partitions that hold them are both exactly the same size (8 MB). The only difference is, with recovery the ramdisk launches an user interface and never leaves it, while with boot the ramdisk chains to booting your normaly system. Never tried it, but I believe if one flashes recovery on the boot partition, the end result would be that the phone boots into recovery every time you'd expect it to boot normally.
How exactly did you flash recovery? Don't link me to a thread or a procedure but rather describe what you did, what commands you issued and what was the response.
Click to expand...
Click to collapse
No problem mate.
Well I guess I could tell you what I did, but I did exactly what the guides said:
downloaded the .zip archive, placed contents anyplace, and started cmd from that folder and entered:
adb install MOTOA4_Bootstrap_0408_1720-signed.apk
Then I opened up that app "System Recovery" and hit Install recovery, then I hit recovery mode from the app, and was told to connect the usb to the wall charger, not pc. And that was it for the first recovery. I then noticed that this specific recovery was missing some functions in the actual recovery so I installed 5.0.2.3 later.
I downloaded the .zip from the site and placed inside phone internal SD, the second link from OP here, turned on phone and went into Android recovery and it opened up the one I installed just a minute ago, and hit install zip from sdcard, I hit internal, and selected the .zip I downloaded from that site. I hit reboot recovery and it booted into that recovery, 5.0.2.3, the real one.
To go to this new one, I insert wall usb to phone and it boots in the first recovery, and I hit, reboot recovery, and it takes me to the new one.
NOW whenever I plug in usb to wall to charge, it boots in the old recovery, and I don't see charge symbol. I have calibrated my battery 3 times, and it is still CRAP (brand new 1800mah battery for mb860).
Anyways, I thought to ask here if I did a wipe data from the new recovery, or old, would it get rid of this whole mess?
Hmm ok.
I told you this before but here goes again. I'd give up on random guides from random sites. Everything you need is right here on this forum.
Not to mention, the recovery in that ZIP is slightly older, there is a newer one available.
Here's what I'd do if I were you.
Do you have fastboot installed? If not, search for it on the forum for moto-fastboot, it's just one .exe file (no installation). Also make sure you have Motorola USB drivers installed.
Download RomRacer's recovery from here (I linked you this before btw). Make sure to select the IMG version, not the ZIP. Choose whatever color you want.
Place the downloaded IMG into the same folder where moto-fastboot is, and rename it into something simple, say recovery.img.
Power off your phone and power it back on while holding Vol(-), make sure it says Fastboot on the screen, then confirm with Vol(+).
Start the command prompt and go into the folder with moto-fastboot, then connect the phone with the computer and enter this command:
Code:
moto-fastboot flash recovery recovery.img
Done. Reboot with Power+Vol(-) but this time select Android recovery (use Vol(-) to move the selection). You should enter the newly installed recovery.
The ZIP you downloaded seems fine, but it's somewhat likely your boot is also messed up too. If all this goes well, you can try finding the T-Mobile fruitcake (go over to the Atrix Reboot Project thread) and flashing it from the recovery. Be aware though that you might lose all data in doing this.
Once again, I told you all this before (not in as much detail though), hopefully this time you'll actually listen.
ravilov said:
Here's what I'd do if I were you.
Do you have fastboot installed? If not, search for it on the forum for moto-fastboot, it's just one .exe file (no installation). Also make sure you have Motorola USB drivers installed.
Download RomRacer's recovery from here (I linked you this before btw). Make sure to select the IMG version, not the ZIP. Choose whatever color you want.
Place the downloaded IMG into the same folder where moto-fastboot is, and rename it into something simple, say recovery.img.
Power off your phone and power it back on while holding Vol(-), make sure it says Fastboot on the screen, then confirm with Vol(+).
Start the command prompt and go into the folder with moto-fastboot, then connect the phone with the computer and enter this command:
Code:
moto-fastboot flash recovery recovery.img
Done. Reboot with Power+Vol(-) but this time select Android recovery (use Vol(-) to move the selection). You should enter the newly installed recovery.
Once again, I told you all this before (not in as much detail though), hopefully this time you'll actually listen.
Click to expand...
Click to collapse
ALRIGHT thanks for this actual guide.
It installed fine, works fine, AND AGAIN whenever I plug the wall charger in when the phone is off, it boots into the OLD OLD recovery, from the first link.
I still can't see the battery.
Please stop throwing sass at me. :crying:
Sorry, sorry.
Anyway, I'm thinking your recovery is fine, but I think somewhere down the line your boot partition got messed up. That's why I said you should try installing the T-Mobile fruitcake. (Fruitcakes are ROMs just like any other but contain the pure untouched stock firmware.)
When my phone is off and I plug it in, I get the boot logo and then the full-screen battery appears, just like it should be. However I'm not sure what this depends on. I always thought this graphics is contained within the bootloader (and thus no amount of messing around with flashing can interfere), but I could be wrong...
ravilov said:
Sorry, sorry.
Anyway, I'm thinking your recovery is fine, but I think somewhere down the line your boot partition got messed up. That's why I said you should try installing the T-Mobile fruitcake. (Fruitcakes are ROMs just like any other but contain the pure untouched stock firmware.)
When my phone is off and I plug it in, I get the boot logo and then the full-screen battery appears, just like it should be. However I'm not sure what this depends on. I always thought this graphics is contained within the bootloader (and thus no amount of messing around with flashing can interfere), but I could be wrong...
Click to expand...
Click to collapse
I can only find this: http://forum.xda-developers.com/showthread.php?t=1163009
I downloaded the 2.3.6 ROM from the backup thread. Says nothing about T-mobile.So do I just install this from the new CWM?
Is there just no way of getting rid of CWM recovery so I can install it just once, rather than you keep telling me to install this and that?
Wait, I'm confused. You want to get rid of CWM?
The point of my previous post was to make sure you have the latest RomRacer's CWM installed fully and properly. Now that you have it installed there is no need to install it again.
Not sure what's your final goal though...?
This is the thread for the Atrix Reboot Project: http://cleanimport.xda/index.php?threads/1805666/
I think the AT&T 2.3.6 ROM should work on T-Mobile too, but in all honesty, I'm not sure. I think it'd be best if someone else answers this part.
ravilov said:
Wait, I'm confused. You want to get rid of CWM?
The point of my previous post was to make sure you have the latest RomRacer's CWM installed fully and properly. Now that you have it installed there is no need to install it again.
Not sure what's your final goal though...?
This is the thread for the Atrix Reboot Project: http://cleanimport.xda/index.php?threads/1805666/
I think the AT&T 2.3.6 ROM should work on T-Mobile too, but in all honesty, I'm not sure. I think it'd be best if someone else answers this part.
Click to expand...
Click to collapse
YES!!! Because everytime I connect the damn charger it boots cwm. AND EVERYTIME I hit ANDROID RECOVERY I boot into the OLD OLD OLD OLD Recovery.
why is that hard to understand? I want to uninstall ALL the cwms, and install the one you sent me just to have that one, rather having 3 different cwms I have right now.
Also that thread is just a bunch of people talking about nothing really. HAS ABSOLUTELY nothing to do with T-mobile whatsoever.
I just want to make sure that this AT&T phone will still work with my t mobile sim card after I install ROMs!!!!
---
And for the love of all that is holy, don't reply with: "why won't it?"
BECAUSE THAT IS WHY I AM ASKING. I have never done this, that is why I ASK!!!!!
It is hard to understand because I don't know how is it even possible to have multiple recoveries installed.
At this point I would suggest you just go ahead and install the 2.3.6 fruitcake you downloaded. Make sure to boot into the CWM you just installed. (Man, even this last sentence feels weird... More than one recovery?!)
ravilov said:
It is hard to understand because I don't know how is it even possible to have multiple recoveries installed.
At this point I would suggest you just go ahead and install the 2.3.6 fruitcake you downloaded. Make sure to boot into the CWM you just installed. (Man, even this last sentence feels weird... More than one recovery?!)
Click to expand...
Click to collapse
SO there is NO WAY to remove CWM recoveries?????
LOL THIS IS FUNNY! Now when I plug charger in, it just boots into OS, and when I hit android recovery with VOL buttons, it shows the white triangle.
Still don't get what that rom did. Installed it, and nothing, except for losing all my data.
This forum made things worse.
Thank you.
EDIT: OKAY NOW it shows the battery when plugged in but still the white triangle crap in the recovery.
You must have SOME recovery. You can install TWRP if you like that better, but you must have SOMETHING. By following the procedure I described you properly installed RomRacer's CWM so that part is fine. Now, why are you still sometimes getting the stock 4-option recovery - only heaven knows.
I don't think there's a way to install the stock Motorola recovery other than installing the full SBF, however SBFs are VERY dangerous and nobody is going to recommend that.
I really can't imagine what you've done with your phone. The mere fact you have multiple recoveries raises a big red flag right there. I tried to help the best way I can, but since obviously it's not doing much good, I'm going to refrain from further comments and let someone else take over. Good luck.
Ravilov has said it all but its pretty spread out trying to figure out what happened so I'm hoping I can tie it all together.
If you attempt to boot into recovery and get the old android recovery but booting normally puts you into CWM Recovery then somehow you have flashed the BOOT partition with CWM image. To fix this just download the correct fruitcake and flash the BOOT.IMG to the BOOT partition using the moto-fastboot tool and reboot. I would recommend erasing the BOOT partition first just in case.
Sent from my Nexus 7 using xda app-developers app
Thanks for your patience and help Ravilov
Sent from my MB860 using xda app-developers app