Hello All,
I am able to flash my phone to any other rom so I was looking for some help to get ICM up and running.
If I flash my phone with beta 0.4.3 or 0.4.4 cwm flashable i reboot my phone and it sits in the "unlocked" Motorola Dual Core Technology screen and won't boot. Any ideas or can I get you information off my phone to assist?
Thanks,
Olsookie
olsookie said:
Hello All,
I am able to flash my phone to any other rom so I was looking for some help to get ICM up and running.
If I flash my phone with beta 0.4.3 or 0.4.4 cwm flashable i reboot my phone and it sits in the "unlocked" Motorola Dual Core Technology screen and won't boot. Any ideas or can I get you information off my phone to assist?
Thanks,
Olsookie
Click to expand...
Click to collapse
Make sure to use Joker's Clockworkmod recovery, named cwm-v3, here.
Thanks gollyzila, I am using the Jokersax CWMv3 recovery image at this time. I meant to mention that earlier in my first post.
Thanks,
Olsookie
olsookie said:
Hello All,
I am able to flash my phone to any other rom so I was looking for some help to get ICM up and running.
If I flash my phone with beta 0.4.3 or 0.4.4 cwm flashable i reboot my phone and it sits in the "unlocked" Motorola Dual Core Technology screen and won't boot. Any ideas or can I get you information off my phone to assist?
Thanks,
Olsookie
Click to expand...
Click to collapse
I would recommend flashing 0.4.0 first, then Gapps if you want it, then boot up. Then wipe cache and flash to 0.4.4 and re-flash Gapps. This method has been posted for the previous couple versions to avoid problems and seems to resolve a lot of issues. Might give it a shot and at least see if 0.4.0 will boot. Also check to make sure your download is the correct size and not corrupted.
try pulling the battery and then booting again. if that doesn't work flash 0.4.0 first like ccallahan suggested
CCallahan said:
I would recommend flashing 0.4.0 first, then Gapps if you want it, then boot up. Then wipe cache and flash to 0.4.4 and re-flash Gapps. This method has been posted for the previous couple versions to avoid problems and seems to resolve a lot of issues. Might give it a shot and at least see if 0.4.0 will boot. Also check to make sure your download is the correct size and not corrupted.
Click to expand...
Click to collapse
wala! that worked. thank you very much CCallahan. much appreciated.
i was having the same problem heres what i did i factory reset cleared cache/dalvic installed 3.1 then reboot wipe cache/dalvic then i flashed 4.4 over it
when you first flash any cm9 fresh, not over a backup, you must flash twice. Joker has mentioned this many times that the scripts he has for the install have to run twice in order to fully install.
1. Flash cm9 (whatever beta you want)
2. Reboot recovery (in advanced in cwm)
3. Flash rom again
4. Flash gapps
5. Boot to system
You should be good to go now
sent from my Kick Ass MIUI MoPho using XDA premium
Related
OK so.... NONE OF THE CUSTOM ROMS BOOT!!!??!??!?!??!! :'(
Device Summary:Carrier unlocked AT&T, UNLOCKED BL, with a 2.3.4 fruit cake flash -No webtop [current state] ( fruit cake flashes perfectly)
Followed all instructions supplied by the Dev's on their respective threads/sites.
Alien 2 Beta: Stuck at "DUAL CORE" screen
Alien 3 Beta: Stuck at "DUAL CORE" screen
CherryPi .3: Stuck at "DUAL CORE" screen
piCrust .3: Stuck at "DUAL CORE" screen
Have wiped all user data and cache via CWM, and even 'fastboot -w in other cases. Also have resorted to wipe Dalvik cache which shouldn't need be done.
*****EDIT*****: I'm also on the latest radio, and latest 'CWM' from tenefar via 'fastboot flash recovery'
Worth asking, though you've probably considered it:
Did you wait upwards of 10 minutes for each? New ROMs wipe app cache among other things, and the first boot takes quite a while. Definitely avoid RSD until you get your answer, though. G/L
-omni
Just have to ask because I have been stuck on the Dual Core screen before... Are you sure you are unlocked? You have the unlocked text in the upper left hand corner??
omni_angel7 said:
Worth asking, though you've probably considered it:
Did you wait upwards of 10 minutes for each? New ROMs wipe app cache among other things, and the first boot takes quite a while. Definitely avoid RSD until you get your answer, though. G/L
-omni
Click to expand...
Click to collapse
LOL, post usually note that the initial boot after flash is ridiculously long..... but I definitely waited >10 mins, almost an hour at longest on the Alien 3 beta flash just now, then I pulled batt and Fruit caked to 2.3.4.
(worried I might turn the soft-brick to a Hard-Brick if the battery died)
bamastang said:
Just have to ask because I have been stuck on the Dual Core screen before... Are you sure you are unlocked? You have the unlocked text in the upper left hand corner??
Click to expand...
Click to collapse
Yup still have the unlocked text...... :-/ FRUSTRATING
same thing happened to me with Ninja and Alien ...i waited 30+ mins..
so i just fruitcaked back to 2.3.4 ..
defnow said:
same thing happened to me with Ninja and Alien ...i waited 30+ mins..
so i just fruitcaked back to 2.3.4 ..
Click to expand...
Click to collapse
lol, it seems like no-one who has had this problem has posted till now? xD
But did you finally get into the launcher? or a complete Boot animation???
do you using correct kernel?
What did you use to unlock/root the device?
As in method/tools/etc.
EDIT-
http://forum.xda-developers.com/showthread.php?t=1182871
I used this tool personally, on Windows 7 x64, and it worked without a hitch.
If you read the thread carefully, all of the instructions are in the OP, but if you have any additional problems, you can find fixes/help throughout the thread (or just post of course).
Otherwise, should go off without a hitch!
Jean-DrEaD said:
do you using correct kernel?
Click to expand...
Click to collapse
Tried stock GB and Faux's kernel, but this wouldn't matter cause rom's flash their own kernel right? According to the progress scripts on CWM..
Jonestown said:
What did you use to unlock/root the device?
As in method/tools/etc.
EDIT-
http://forum.xda-developers.com/showthread.php?t=1182871
I used this tool personally, on Windows 7 x64, and it worked without a hitch.
If you read the thread carefully, all of the instructions are in the OP, but if you have any additional problems, you can find fixes/help throughout the thread (or just post of course).
Otherwise, should go off without a hitch!
Click to expand...
Click to collapse
I used the pudding/fastboot oem unlock method for x64 windows, the application put together should do the exact same thing but without the user needing to do the actual steps individually, but any ways will give it a go
weaz_da_smel said:
Tried stock GB and Faux's kernel, but this wouldn't matter cause rom's flash their own kernel right? According to the progress scripts on CWM..
Click to expand...
Click to collapse
flash kernel after flash the rom because that... try FR an ATT kernels...
weaz_da_smel said:
OK so.... NONE OF THE CUSTOM ROMS BOOT!!!??!??!?!??!! :'(
Device Summary:Carrier unlocked AT&T, UNLOCKED BL, with a 2.3.4 fruit cake flash -No webtop [current state] ( fruit cake flashes perfectly)
Followed all instructions supplied by the Dev's on their respective threads/sites.
Alien 2 Beta: Stuck at "DUAL CORE" screen
Alien 3 Beta: Stuck at "DUAL CORE" screen
CherryPi .3: Stuck at "DUAL CORE" screen
piCrust .3: Stuck at "DUAL CORE" screen
Have wiped all user data and cache via CWM, and even 'fastboot -w in other cases. Also have resorted to wipe Dalvik cache which shouldn't need be done.
*****EDIT*****: I'm also on the latest radio, and latest 'CWM' from tenefar via 'fastboot flash recovery'
Click to expand...
Click to collapse
start from scratch...go back to stock via RSD...
DO NOT DO THIS
if the fuse is blown YOU WILL BRICK
I would fruitcake back to 1.83 then flash to the rom you want, since its voda I would try a working international rom first.
DO NOT GO BACK VIA RSD YOU MIGHT HARD BRICK.
wipe all data in fastboot -> flash stock 2.3.4 via fastboot -> wipe all data again
Not trying to hi-jack the thread but I have the exact same problem so I thought I'd post here and give a detailed description of what I've done instead of creating another thread just like this one.
I unlocked the bootloader using the latest version of pudding
Then I downloaded fastboot and installed CWM
I downloaded the ROM of my choice meaning Alien 3 and the theme, and later when that didn't work Redpill 3. Also for the record I've tried installing with Alien 3 standalone and wait for boot up, and with both - neither worked and Redpill produces the same result.
Anyway back to the process
After downloading and putting the file of my choice on the external sd card I boot up into android recovery (flashed to CWM) I go to advanced and wipe the dalvik and then wipe the regular cache partition.
I reboot and immediately go to fastboot,
I do the fastboot -w command and then the fastboot reboot command and immediatley go back to CWM
I install using the external sd card and choose the zip of my liking.
It installs great and I then wipe the dalvik and cache again.
I reboot and I get stuck at the red M dual core screen.
The only way to get unstuck is to reflash with 183-sb-release.zip which is the fruitcake release I think. I got this from someone on a forum describing a similar problem for which this was the solution. However afterwards he was able to reinstall a custom rom without problems, while my problem remains.
*Edit - I have an AT&T phone
diviluxfloss said:
After downloading and putting the file of my choice on the external sd card I boot up into android recovery (flashed to CWM) I go to advanced and wipe the dalvik and then wipe the regular cache partition.
I reboot and immediately go to fastboot,
I do the fastboot -w command and then the fastboot reboot command and immediatley go back to CWM
I install using the external sd card and choose the zip of my liking.
It installs great and I then wipe the dalvik and cache again.
I reboot and I get stuck at the red M dual core screen.
Click to expand...
Click to collapse
To double check -> Are you using latest unlocked CWM from xda or rom managers one?
Also to double check -> you did Wipe data / Factory reset as well?
You should do all three Wipe options before and after flashing the rom -> wipe cache, wipe data / factory reset, wipe davik.
After that reboot and give it a couple of minutes to boot.
If that doesn't work, do a battery pull and try booting again.
Thank you for the swift reply
I have the latest CWM from XDA.
I have tried several enumerations including wipe cache, wipe dalvik and wipe data/factory reset.
I've also tried removing the battery.
Still no success :/
diviluxfloss said:
Thank you for the swift reply
I have the latest CWM from XDA.
I have tried several enumerations including wipe cache, wipe dalvik and wipe data/factory reset.
I've also tried removing the battery.
Still no success :/
Click to expand...
Click to collapse
Alright, then the second thing I would try is flashing one of the custom ROMs via fastboot:
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
moto-fastboot -w
moto-fastboot reboot
p.s. and if you don't have the latest radio,-
moto-fastboot flash radio radio.img
Again thank you for the swift reply
Is flashing with fastboot dangerous in comparison to cwm? Ie. is there a larger risk of inherent soft/hard-bricking?
Also here comes a noob question so I hope you'll be lenient with me, but what is a radio per say and how will it help during the flashing of a rom?
Thank you I appreciate the help so far!
diviluxfloss said:
Again thank you for the swift reply
Is flashing with fastboot dangerous in comparison to cwm? Ie. is there a larger risk of inherent soft/hard-bricking?
Also here comes a noob question so I hope you'll be lenient with me, but what is a radio per say and how will it help during the flashing of a rom?
Thank you I appreciate the help so far!
Click to expand...
Click to collapse
The only truly dangerous method of flashing is SBF (RSDlite). CWM and fastboot are safe.
If you unlocked the bootloader youserlf, you already know what fastboot looks like. Often, fastboot helps where CWM fails.
Before using fastboot, make sure you have phone drivers installed, also make sure you have "moto-fastboot" version and not "fastboot", as the latter can't flash large files, e.g. - system.img.
Phone drivers for Windows x64 can be downloaded here (though your probably have them already if you unlocked the BL) -
http://forum.xda-developers.com/attachment.php?attachmentid=634880&d=1308872277
Download moto-fastboot for your operating system here (if you don't have it already, obviously) -
http://forum.xda-developers.com/showthread.php?t=1138092
"Radio" is software that handles cellular connection, mobile data, etc.
I've read that there could be a boot problem if wrong radio is used.
Besides, the latest 2.3.4 radio includes many bug fixes and better mobile data speeds.
You can check if you have the latest one under "About Phone" -> "Baseband version". Latest one for ATT is N_01.77.30P.
It can be downloaded here - http://bandbinnovations.com/xda/gingerbread/Gingerbread-4.5.91.zip
(The archive contains all stock 2.3.4 partitions, but you can simply extract radio.img and flash it separately via fastboot)
Cheers.
Great
I'll try flashing the radio and then the files as mentioned in your previous post. A problem though is that when I look through the zip files I only find a boot.img file for the custom rom.
Where is the system.img file located and if I simply install these through moto-fastboot (thanks for the heads up btw as I only had fastboot) what happens to the smaller files located on the zip which won't be associated to the img files?
*Edit I compared these to the fruitcake zip and in the custom roms I have a folder called system which I believe contains all the info while the fruitcake files have an img. I'm guessing not compatible? Or can I simply make an img file with the system folder and flash thusly?
Hi there, I need your help and advice please.
Here’s my problem. My phone is the SGS2 running KI3 rooted with CF-root KI3 flashed the secure kernel and then flashed the zImage so I still have root CWM and to get rid of the yellow triangle. I have downloaded CM nightly 88 to my laptop and transferred it to my S2 via usb cable into the download folder.
Here’s where the problem comes into play when I run CF’s CWM and choose reboot into recovery I do a wipe/factory reset / wipe cache and update via sdcard, I pick the cm88 from the download folder and it starts to update and then stops. I reboot and it’s stuck on the Samsung S2 page (boot loop). I then have to get into the recovery and restore my phone to the previous state. Can someone help me I would like to try the CM’s custom rom but don’t know what I’m doing wrong? Thanks.
i have the exact same problem!
InFa_ReD_1 said:
Hi there, I need your help and advice please.
Here’s my problem. My phone is the SGS2 running KI3 rooted with CF-root KI3 flashed the secure kernel and then flashed the zImage so I still have root CWM and to get rid of the yellow triangle. I have downloaded CM nightly 88 to my laptop and transferred it to my S2 via usb cable into the download folder.
Here’s where the problem comes into play when I run CF’s CWM and choose reboot into recovery I do a wipe/factory reset / wipe cache and update via sdcard, I pick the cm88 from the download folder and it starts to update and then stops. I reboot and it’s stuck on the Samsung S2 page (boot loop). I then have to get into the recovery and restore my phone to the previous state. Can someone help me I would like to try the CM’s custom rom but don’t know what I’m doing wrong? Thanks.
Click to expand...
Click to collapse
try download it again. Sound like a corrupted package
Sent from my GT-I9100 using Tapatalk
rembrandtlnx said:
try download it again. Sound like a corrupted package
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I tried and got the samething. I also tried a different cm nightly and got the same results.
InFa_ReD_1 said:
I tried and got the samething. I also tried a different cm nightly and got the same results.
Click to expand...
Click to collapse
me2 only stock roms work for me =(
I think there was an issue with the version of CWM used on the CF-roots since it's been modified by CF and because it's an older version.
After you've rooted with CF, try flashing a kernel on there with a newer version of CWM on there (I used codeworkx's kernel from the Cyanogenmod wiki I've attached below with CWM 4.0.1.4).
Once this kernel is on there, then try flashing the CM7 ROM as per this thread. I prefer flashing from recovery myself, but it's your call.
Make sure you flash it twice in a row if you're having issues.
The problem, as stated above is that cf root kernel installs a modified version of CWM that won't work with CM7. Another thing is you have to flash a stock KH3 because KI3 has the new bootloader (unless you flashed KI3 with the old bootloaders). Then, you have to flash the codeworkx kernel so you get a compatible version of CWM. Once in CWM clear data factory reset + clear cache partition + clear dalvik cache (from advanced).
THIS IS IMPORTANT: Flash the ROM from sd card and when finish do not reboot device, just flash it again without wiping anything in between, just 2 consecutives "install from sd card". When this is done you can reboot the system and then enter again to CWM to flash the google apps .zip file that you can download from the CM7 thread.
Hope this helped. When I flashed CM7 i had exactly the same problem and went back to stock cause it was a pain in the ass to flash it fr the first time. But once you get in CM7, everything becomes great and easy, and you can update the nighlies directly from ROM manager without doing any wiping. You just can't use ROM manager when getting to CM7 for the first time.
InFa_ReD_1 said:
Hi there, I need your help and advice please.
Here’s my problem. My phone is the SGS2 running KI3 rooted with CF-root KI3 flashed the secure kernel and then flashed the zImage so I still have root CWM and to get rid of the yellow triangle. I have downloaded CM nightly 88 to my laptop and transferred it to my S2 via usb cable into the download folder.
Here’s where the problem comes into play when I run CF’s CWM and choose reboot into recovery I do a wipe/factory reset / wipe cache and update via sdcard, I pick the cm88 from the download folder and it starts to update and then stops. I reboot and it’s stuck on the Samsung S2 page (boot loop). I then have to get into the recovery and restore my phone to the previous state. Can someone help me I would like to try the CM’s custom rom but don’t know what I’m doing wrong? Thanks.
Click to expand...
Click to collapse
DO NOT use cf-root to install CM7. It's stated by Codeworkx a lot of times in CM Q&A thread. Just flash his kernel to get cwm.
http://forum.xda-developers.com/showthread.php?t=1118693
Now you have the original cwm recovery (from Koush). Boot into recovery, Wipe data, cache, dalvik.
Install CM7 twice in a row without rebooting.
Then flash gapps (without rebooting) http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip.
Now reboot. Wait for a few mins since system has to build dalvik cache. And you're all good to go
Worried about yellow triangle? Get a usb jig.
Siyah kernel 2.0 supports CM7 and miui. So....have fun.....!!
droidphile said:
DO NOT use cf-root to install CM7. It's stated by Codeworkx a lot of times in CM Q&A thread. Just flash his kernel to get cwm.
http://forum.xda-developers.com/showthread.php?t=1118693
Now you have the original cwm recovery (from Koush). Boot into recovery, Wipe data, cache, dalvik.
Install CM7 twice in a row without rebooting.
Then flash gapps (without rebooting) http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip.
Now reboot. Wait for a few mins since system has to build dalvik cache. And you're all good to go
Worried about yellow triangle? Get a usb jig.
Siyah kernel 2.0 supports CM7 and miui. So....have fun.....!!
Click to expand...
Click to collapse
Thanks. Can i flash the orginal CWM over top the CF CWM?
InFa_ReD_1 said:
Thanks. Can i flash the orginal CWM over top the CF CWM?
Click to expand...
Click to collapse
I did it and didn't have any problems, just follow the steps as I posted above.
tomascunill said:
I did it and didn't have any problems, just follow the steps as I posted above.
Click to expand...
Click to collapse
Great thanks for the help it worked I'm now running CM7. One thing though I can make calls but have lost my network connection. Can someone help me with this? Sorry for all the questions I'm new to the whole smartphone business. Thanks.
Ok all fixed up thanks for all your help.
I've been shuffling through threads for the past 2 days trying to find a fix a no luck yet so i'm making my own noob post.
yesterday after flashing CM7 to my atrix, I was trying to install the Gapps package and after that install my phone wont boot past the logo screen.
Im still able to access fastboot and get into android recovery. I've tried to wipe everything and reinstall cm7 but still nothing.
i read that some people were able to get this issue resolved using command prompt and fastboot commands, but im totally lost when it comes to command prompt and couldn't get working correctly.
any suggestions or fixes would be greatly appreciated
DThimself said:
I've been shuffling through threads for the past 2 days trying to find a fix a no luck yet so i'm making my own noob post.
yesterday after flashing CM7 to my atrix, I was trying to install the Gapps package and after that install my phone wont boot past the logo screen.
Im still able to access fastboot and get into android recovery. I've tried to wipe everything and reinstall cm7 but still nothing.
i read that some people were able to get this issue resolved using command prompt and fastboot commands, but im totally lost when it comes to command prompt and couldn't get working correctly.
any suggestions or fixes would be greatly appreciated
Click to expand...
Click to collapse
Just to be clear:
1. You successfully booted into CM7 after installing it? Then you went to install gapps and couldn't get past the boot logo?
2. Or were you trying to install gapps right after flashing CM7 (i.e. stayed in recovery and did not boot into OS)?
i Successfully booted into cm7 then went back into recovery to install the gapps package and after that install it wouldnt boot past the logo
DThimself said:
i Successfully booted into cm7 then went back into recovery to install the gapps package and after that install it wouldnt boot past the logo
Click to expand...
Click to collapse
Hmm, well that definitely rules out an outdated recovery, which is what usually causes people to get stuck at the bootlogo. If you can't even re-install after wiping, then I would just restore a backup and start over.
Maybe try getting a fresh download of the gapps package. You may have possibly had a corrupted download?
Are you running CWM recovery or Rom Racer's? I had a problem where I was stuck at the boot logo while using CWM (latest one) but when I switched to Rom Racer's recovery and flashed everything worked.
I ended up having to use an older CWM recovery and wiping the phone and SD card with a lot of help from a friend of mine whos knows more about this than i do
DThimself said:
i Successfully booted into cm7 then went back into recovery to install the gapps package and after that install it wouldnt boot past the logo
Click to expand...
Click to collapse
How did you prep for the CM7 and GAPPS flash? If you did not wipe correctly, there was a first indication you might have problems.
How long did you wait after the phone first booted into CM7? If you rebooted as soon as the OS was up, that's more than likely your issue. You need to wait 10 minutes to let the phone build system files after flashing.
Also, an older CWM would have, if anything, caused more problems. If you had the latest ROM Manager or Romracer CWM then that was definitely not your problem, so your friend using an "older" CWM wasn't helping any.
DThimself said:
I've been shuffling through threads for the past 2 days trying to find a fix a no luck yet so i'm making my own noob post.
yesterday after flashing CM7 to my atrix, I was trying to install the Gapps package and after that install my phone wont boot past the logo screen.
Im still able to access fastboot and get into android recovery. I've tried to wipe everything and reinstall cm7 but still nothing.
i read that some people were able to get this issue resolved using command prompt and fastboot commands, but im totally lost when it comes to command prompt and couldn't get working correctly.
any suggestions or fixes would be greatly appreciated
Click to expand...
Click to collapse
I have run into this issue before when flashing any apps that update an app that is already there. I have found that a Dalvik wipe is needed before the flash. It is good practice to wipe Dalvik at least when flashing anything that changes the System Files. I also wipe the cache Partition before any flashes just to help mitigate issues like this.
I rooted my device using Gingerbreak.
I have 2.2.2 installed out of the box. I installed CWM. I installed busybox.
Busybox failed. I tried all the versions that it contains.
I checked root status, and RootCheckBasic says I'm rooted.
I installed Flash ClockworkMod Recovery. It will not reboot to CWM.
It only reboots to the standard Android recovery.
I'm trying to install Bumblebee ROM 2.4.
Here are some things I am having issues understanding with it...
Backup current apps and their data with Titanium Backup (available in the Market). Is this required? The phone is new. I have nothing to back up.
Do a nandroid backup in recovery before doing anything else below.
And the nandroid backup is done with CWM? Again CWM won't reboot, only the standard Android recovery boots.
Required if installing BB 2.x for the first time: Wipe. Wipe it all. Data, cache, system, dalvik-cache, sd-ext if you've got it (might need to look under Advanced or Mounts in recovery to do the last two, and while you're there format /system). I assume you wipe it all with CWM while in recovery?
If upgrading from BB 2.3, wipe cache (and only cache) in recovery.
Does not apply to me
If not upgrading from 2.3, install Wiper zip (see below), just to be extra sure that all is wiped. Don't reboot yet. Installing wiper.zip is done by sideloading using adb commands?
Install ROM zip (see below).
I assume this too is done by copying the zip to the external SD, then selecting update from SD card in recovery... right?
Please someone shed some light on this for me.
In standard Android recovery it says e3. I know on my Captivate I had to use Odin to install GB loaders to get it to work.
THANKS!
Flashwork mod recovery? Never heard of it.
Try downloading rom manager from the market and use that.
Everything else should be simple
tvall said:
Flashwork mod recovery? Never heard of it.
Try downloading rom manager from the market and use that.
Everything else should be simple
Click to expand...
Click to collapse
Flash ClockworkMod Recovery
It's in rom manager.
Which I installed from the market.
But I don't get the CWM recovery when I reboot into recovery mode.
I get the standard Android recovery
-you know... the one that just has "install update.zip"
bulltproof said:
Flash ClockworkMod Recovery
It's in rom manager.
Which I installed from the market.
But I don't get the CWM recovery when I reboot into recovery mode.
I get the standard Android recovery
-you know... the one that just has "install update.zip"
Click to expand...
Click to collapse
Oh, okay, um... are you using the reboot into recovery option in rom manager right after flashing?
After flashing what?
I reboot into recovery through rom manager and get:
Android system recovery <3e>
reboot system now
apply sdcard: update.zip
wipe data/factory reset
wipe cache partition
_________________________________________________________
Android System recovery...
Do not pull out the battery!!
After hitting flash clockworkmod recovery, immediately hit reboot recovery
After hitting anything in CWM it did nothing more than reboot into the standard android recovery.
This phone has 2.2.2 on it. Problem? Probably.
I followed instructions at androidcentral and got it to work.
Needed Xionia_CWMA_12518.6_VM
Installed BACKside-IHO-VM670-11222011
using Xionia_CWMA_12518.6_VM_Recovery-signed
Had a little problem today and needed to activate the phone. BUUUUT......
the rom didn't allow activation.
So I installed Bumblebee. No go.
Then I tried [rom] basic stock rom.
Neither of these will let my phone boot. It gets stuck at boot.
Nothing happens.
I can still boot into Xiona_CWMA. But no roms will work.
PLEASE HELP!!!!
Dude i m noob, and i m facing same problem,
I did root with super one click soc, and it is rooted and i am using root needed apps,
But when i m trying to clobk work recovery (i did flashing CWR from rom manager and aft that i select boot from cwr option from rom manager) it just factory reset i did this 3time all time just factory reset, then i again did but while rebooting i click home button so it gave me same option which came to above member said some e3............
And i try to select any option from it with menu button it was not applied, and no use so i removed battry and place again and start then device started dont know more what to do, help
Sent from my LG-P500 using Android-HQ App
Ok, so I CAN load different recoveries.
They work, or at least seem to.
I can flash roms, but nothing happens (bootloop) or the phone comes on and works with a black screen.
I can call my number and can hear the call, but can't see anything.
Bullet if u found solution pls tell me too
Sent from my LG-P500 using Android-HQ App
bulltproof said:
Ok, so I CAN load different recoveries.
They work, or at least seem to.
I can flash roms, but nothing happens (bootloop) or the phone comes on and works with a black screen.
I can call my number and can hear the call, but can't see anything.
Click to expand...
Click to collapse
I believe that may be due to the newer display in your phone (I'm new to this device so I dont know much yet). From the little bit of information I've gathered, devices manufactured recently have a different display that requires a kernel that supports it. In the iho roms this is included, on others you'll need to flash a kernel right after the rom.
For the stock rom I can upload what I use if you need it. Its basically the one posted here just with the boot.img swapped with one from a nandroid backup I made before switching roms
I think you're spot on with that idea.
I loaded CM7 variant, and it worked.
My question is, how do I get another ROM on it if it has the newer screen?
I loaded different kernels that were supposed to fix it, but no go.
Hello my friends.
I unlocked the BL and install the CWM. So i try to install a new ROM at my Atrix.
I made the installation of the Neutrino V1.4 GT, but after made the installation of the .zip , my atrix got stuck at the boot screen.
So i made the restore of the backup that I already made, and the smartphone starts ok.
After that i tried install other ROM , CM7-ICS-FINAL and I got the same stuck boot screen.
I found other Thread about that same problem, and the user found a solution but he forgot to post that solution, just wrote ''problem solve''.
Anyone know what can i make to install the ROM ? Thanks for your attention
blindox said:
Hello my friends.
I unlocked the BL and install the CWM. So i try to install a new ROM at my Atrix.
I made the installation of the Neutrino V1.4 GT, but after made the installation of the .zip , my atrix got stuck at the boot screen.
So i made the restore of the backup that I already made, and the smartphone starts ok.
After that i tried install other ROM , CM7-ICS-FINAL and I got the same stuck boot screen.
I found other Thread about that same problem, and the user found a solution but he forgot to post that solution, just wrote ''problem solve''.
Anyone know what can i make to install the ROM ? Thanks for your attention
Click to expand...
Click to collapse
You are most likely using an outdated CWM (my guess would be Tenfar's). If it doesn't support ext4 then any ROM based on CM7 will not boot. Either use the one that comes with ROM Manager, romracer's, or TWRP.
+1
That would be my guess, the recovery.
ghost_og said:
You are most likely using an outdated CWM (my guess would be Tenfar's). If it doesn't support ext4 then any ROM based on CM7 will not boot. Either use the one that comes with ROM Manager, romracer's, or TWRP.
Click to expand...
Click to collapse
yes use romracers recovery
and.wipe data
wipe cache
wipe dalvic.cache in advanced.options
Sent from my MB860 using Tapatalk
Thanks for all the support ! I will download the romracers recovery and retry install the new ROM!
ghost_og said:
You are most likely using an outdated CWM (my guess would be Tenfar's). If it doesn't support ext4 then any ROM based on CM7 will not boot. Either use the one that comes with ROM Manager, romracer's, or TWRP.
Click to expand...
Click to collapse
live4nyy said:
+1
That would be my guess, the recovery.
Click to expand...
Click to collapse
ltdanno360 said:
yes use romracers recovery
and.wipe data
wipe cache
wipe dalvic.cache in advanced.options
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Be sure to let us know if it worked in case anyone else with the same issue can find the answer much easier.
blindox said:
Thanks for all the support ! I will download the romracers recovery and retry install the new ROM!
Click to expand...
Click to collapse
Hello my friends..
I made the install of the romracers recovery.. and i installed the ROM ( Neutrino ROM ).
But Now it gets to the boot up screen that says "Neutrino ROM ... system loading" the screen will black out for a couple seconds and then come right back to that screen in a loop. its been happening for about 15 minutes.
obs : I forgot to make the backup
Thanks for the help!
Did you use the recovery for the factory data reset and wipe cache/dalvik cache? You might want to try fastboot wipe as well.
blindox said:
Hello my friends..
I made the install of the romracers recovery.. and i installed the ROM ( Neutrino ROM ).
But Now it gets to the boot up screen that says "Neutrino ROM ... system loading" the screen will black out for a couple seconds and then come right back to that screen in a loop. its been happening for about 15 minutes.
obs : I forgot to make the backup
Thanks for the help!
Click to expand...
Click to collapse
live4nyy said:
Did you use the recovery for the factory data reset and wipe cache/dalvik cache? You might want to try fastboot wipe as well.
Click to expand...
Click to collapse
hello my friend,
i just made the WIPE CACHE AND WIPE DALVIK CACHE and the install of the ROM.
When i saw the screen NEUTRINO I was happy, until the time the ''system loading" getting black out for a couple seconds and then come right back. I knew there was something wrong.
Now I will make the process again with the factory data reset and then i will post what happened
Thanks
MY FRIEND..
thanks for all the support! I made the again the process with the factory reset and now the ROM is installed correctly.
Let me ask a question. I want to install a new kernel to try the overclock 1.3GHZ. That new kernel can be installed with the romracers ?
Thanks for the attention
**HAPPY NEW YEAR
live4nyy said:
Did you use the recovery for the factory data reset and wipe cache/dalvik cache? You might want to try fastboot wipe as well.
Click to expand...
Click to collapse
Yes, romracer is recommended. It is the only recovery that is specifically developed for the Atrix 4G. You could also try the TRWP Recovery but romracer's recovery is proven to work well and recommended by most.
Glad everything worked out.
blindox said:
MY FRIEND..
thanks for all the support! I made the again the process with the factory reset and now the ROM is installed correctly.
Let me ask a question. I want to install a new kernel to try the overclock 1.3GHZ. That new kernel can be installed with the romracers ?
Thanks for the attention
**HAPPY NEW YEAR
Click to expand...
Click to collapse