Rooted a atrix 4g AT&T US.
I had the stock rom running after root, then when I tried to setup a custom rom it wont get past the M logo. I can get into fastboot but when I try to flash any system.img it says the file is too large. I tried erasing system, boot and data, then got into CWM and tried to install from zip. It runs and says it finished. but still no boot. I dont know what else to try. any ideas?
did you format system, data, cache in advanced menu in recovery?
Sent from my MB860 using xda app-developers app
I noticed only one important thing missing from your post, did you unlock the bootloader first? Rooting is totally separate from being able to install custom roms.
jpaytoncfd said:
Rooted a atrix 4g AT&T US.
I had the stock rom running after root, then when I tried to setup a custom rom it wont get past the M logo. I can get into fastboot but when I try to flash any system.img it says the file is too large. I tried erasing system, boot and data, then got into CWM and tried to install from zip. It runs and says it finished. but still no boot. I dont know what else to try. any ideas?
Click to expand...
Click to collapse
So I used fastboot to flash a new recovery (http://forum.xda-developers.com/showthread.php?t=1204500) Worked like charm, Roms load correctly and are loading great. (Although the one I am trying right now is stuck on the boot animation) I did have one loaded and working in only a few seconds after updating the recovery.
Hope this helps someone else.
jpaytoncfd said:
Rooted a atrix 4g AT&T US.
I had the stock rom running after root, then when I tried to setup a custom rom it wont get past the M logo. I can get into fastboot but when I try to flash any system.img it says the file is too large. I tried erasing system, boot and data, then got into CWM and tried to install from zip. It runs and says it finished. but still no boot. I dont know what else to try. any ideas?
Click to expand...
Click to collapse
Try to restore to the stock rom with the RSDlite method, it's the most simple.
Then check the automatic unlock and root for the atrix, it's a command line program that makes everything by itself, it must be somewhere here in the top guides of this forum
joelorona said:
Try to restore to the stock rom with the RSDlite method, it's the most simple.
Click to expand...
Click to collapse
Do NOT use RSD or SBF files. Use fruitcakes.
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
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
Okay so today I decided to try to install an ICS rom to my phone and I flashed the PH98IMG in fastboot and then after that was done my phone would only boot to a black screen. So I deleted to PH98IMG from my sd card and now my phone will only let me into the hboot and I can't do anything else!! I've re-locked my bootloader but not sure where to go from here. Any help getting my phone back to any working state whether it is rooted or not would be great!
If you still have the from on unlock the phone boot into boot and flash the kernel manually(fastboot flash boot boot.img). You may not have seen the mainver error flash by when you flashed the rom
Sent from my ADR6425LVW using Tapatalk
Well I've unlocked the boot loader and rebooted my phone and now it is letting me get back to the clockwork recovery.
chickltt7 said:
Well I've unlocked the boot loader and rebooted my phone and now it is just on a black screen
Click to expand...
Click to collapse
Can you reflash your nand to get back to ground zero?
I've been having to use the PC to flash boot.img since all the mainver errors
My backup is hosed which I'm okay with. I just want my phone to work again Well I installed a custom rom in recovery and it said that installed okay but now it still only boots to a black screen. So now I'm just wondering if I'm having an issue with the ph98img.
chickltt7 said:
My backup is hosed which I'm okay with. I just want my phone to work again Well I installed a custom rom in recovery and it said that installed okay but now it still only boots to a black screen. So now I'm just wondering if I'm having an issue with the ph98img.
Click to expand...
Click to collapse
I believe you are.
Are you familiar with using cmd.exe and adb?
If you can get into recovery, mount you external card and pull the ph98ing file to the PC.
inside that zip file is a file called boot.img.
use the command "fastboot flash boot boot.img" and it will load the kernal.
I'm skipping a lot assuming you know what I'm talking about.
Read this post and it will help out tremendously. It did for me.
http://forum.xda-developers.com/showthread.php?t=1418659
Well guys I think that may have worked my phone is booting up normally now. But now I have a question if I want to factory reset my phone should I have any problems doing that or will I have to go through a bunch of stuff to do that?
What ROM are you running currently?
chickltt7 said:
Well guys I think that may have worked my phone is booting up normally now. But now I have a question if I want to factory reset my phone should I have any problems doing that or will I have to go through a bunch of stuff to do that?
Click to expand...
Click to collapse
Should not have any problem factory resetting just make sure that you deleted the PH98IMG file from the root of your sd card.
Right now I'm running BAMF Rezound Cubed 1.0.2 Stockish and Themed but I want to go back to the stock gb rom and just leave it rooted
I don't know what mainver that BAMF ROM is on but if it is different than the OTA stock you can use this tool con247 just made to help in situations where mainvers differ.
http://forum.xda-developers.com/showthread.php?t=1497984
If the BAMF ROM is 2.x mainver you can run the RUU for that version and get yourself back to stock, then flash Amon Ra recovery and install su and you'll be stock GB and rooted.
I have the Evo LTE S-on (HTC bootloader unlocked) and TWRP installed. The only problem I'm having is that I cannot seem to get .zip files to open from the install menu in TWRP (recovery). I factory reset and try to open the zip from the install menu but it just says "Failed". Specifically I am trying Kushdeck's new CM10 ROM. Any help would be greatly appreciated. Thanks.
PS. Not sure if this will help but on the install menu my files show up twice, the first time with the normal naming and the second with "/." in front of them.
Did u try and re download it again? Sounds like a bad DL if it keeps failing after a couple of attempts
Sent from my EVO using Tapatalk 2
Ok I'm trying that now. I'm also wondering if there's a problems with my /ext-sd because everytime I factory reset it says it couldn't access that. Do you think that has anything to do with it? Is reinstalling TWRP an option?
Ok thanks so much the re-download did it. But now I'm at a black/blank screen after start up. I factory reset, installed the CM10 ROM then Gapps and wiped the dalvik/cache. Then when I reboot it just goes to the HTC screen and after that nothing. Ideas?
This is going to sound strange but try factory restet, wipe cache/dalvik and then just reboot without trying to flash anything.. I've been having some similar issues as mine isn't recoglizing any MD5 when i try to flash a new rom.. I wiped my phone and have tried to flash a few roms and it fails every time and in wiping my phone it somehow took out my backup so without any other options (that I knew of) I just rebooted and luckily it loaded a completely bare vipor rom like what I started out with when I originally rooted.. BTW, did you create a backup before trying to flash? Should always make a backup....
Ya I had backed up. Turns out I needed to manually flash the boot.img which fixed the issue
elitelimfish said:
Ya I had backed up. Turns out I needed to manually flash the boot.img which fixed the issue
Click to expand...
Click to collapse
Thanks for this. I had the same problem, (S-ON, TWRP. black screen on boot). I was able to flash stock-based ROMs, but not CM10, so I suspected it had something to do with the things that HTCDev won't allow the recovery access to, but the logs from TWRP didn't throw any errors, so while I suspected boot, I didn't know what to do about it. And everyone knows that it's easy to be caviler with everything is working, but as soon as you start having problems, you get gun shy about trying things.
Your post was the solution for me. Extract the boot.img file found inside the zip or your chosen ROM, and flash it using fastboot:
"fastboot flash boot boot.img"
heywetried said:
Thanks for this. I had the same problem, (S-ON, TWRP. black screen on boot). I was able to flash stock-based ROMs, but not CM10, so I suspected it had something to do with the things that HTCDev won't allow the recovery access to, but the logs from TWRP didn't throw any errors, so while I suspected boot, I didn't know what to do about it. And everyone knows that it's easy to be caviler with everything is working, but as soon as you start having problems, you get gun shy about trying things.
Your post was the solution for me. Extract the boot.img file found inside the zip or your chosen ROM, and flash it using fastboot:
"fastboot flash boot boot.img"
Click to expand...
Click to collapse
Hey out of curiosity did you like any of the stock based ROMs? If so which ones? I kinda wanna try one out but haven't settle on one