Database Users

I installed cyanogen 7 and all I get is boot logo

I installed cyanogen 7 and all I get is boot logo this keeps resting "the cyanogen" logo and I do have my atrix unlocked and rooted.

Lack of the following specifics:
How did you flash CM7? (ADB push or through CWM or twrp)
What version of CM7 did you try to flash?
AT&T atrix or international atrix?
Did you flash a kernel or any additional zips prior to booting?
Did you perform a full wipe before installing?
And many other questions may arise, should we get more specifics from you.

Wipe data. Cache. Dalvick and re-install
Sent from my MB860 using xda premium

SirFork said:
Lack of the following specifics:
How did you flash CM7? (ADB push or through CWM or twrp)
What version of CM7 did you try to flash?
AT&T atrix or international atrix?
Did you flash a kernel or any additional zips prior to booting?
Did you perform a full wipe before installing?
And many other questions may arise, should we get more specifics from you.
Click to expand...
Click to collapse
How did you flash CM7? (ADB push or through CWM or twerp) I used rom manager from market store
What version of CM7 did you try to flash? the regular builds non nightly
AT&T atrix or international atrix? att
Did you flash a kernel or any additional zips prior to booting? no

You need to have installed a recovery program that you can get to by holding the VOL DOWN button while booting. ROM manager is useless without a recovery program behind it.

Oh so how can I flash an rom without a rom manger just using the computer?

I would spoon-feed you this information, however it would be like handing a monkey a rocket-propelled grenade. You need to take time to read before you create a very expensive paperweight.
http://forum.xda-developers.com/showthread.php?t=1154600
Please take the time to read this, all the way through. If you haphazardly install things without full knowledge of what it does, people will have very little to no sympathy for you when you brick your phone.

Yes I did do the following
While in Recovery install CM7 from internal storage
After installation select Data Wipe/Factory Reset
Then Wipe Cache Partition
Reboot system now
Watch awesome boot animation.
I do not see nothing else after the boot animation?

sillyshyme said:
Yes I did do the following
While in Recovery install CM7 from internal storage
After installation select Data Wipe/Factory Reset
Then Wipe Cache Partition
Reboot system now
Watch awesome boot animation.
I do not see nothing else after the boot animation?
Click to expand...
Click to collapse
If you installed CM7, and then did a factory reset, you undid your first step.
\\FROM ANDROID RECOVERY MODE// (hold volume down button then scroll through the options until you get to Android Recovery, then press VOL UP to confirm. If you don't see Android Recovery in the list, then you're missing something crucial)
1. Wipe/Factory reset
2. Install CM7
3. Wipe cache (optional)
4. Reboot

reead the noob guide for xda google search will reveal this awsome guide and video hehe
Sent from my MB860 using Tapatalk

You would think that it would undo, but it doesn't. The factory reset doesn't "unflash" the ROM. All it does, is flush cache and a few other directories.
Sent from my MB860 using xda premium

How long did you let the phone sit after rebooting? It can take 15 minutes on initial boot after flashing a ROM. All that time all you will see is the boot animation.
Sent from my MB860 using xda premium

Wipe dalvik and cache partition and factory reset it in the cwm. Make sure your boot loader is unlocked. Made that mistake my first time.?
Sent from my Nexus S using xda premium

heinst said:
Wipe dalvik and cache partition and factory reset it in the cwm. Make sure your boot loader is unlocked. Made that mistake my first time.?
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Definitely. I made that mistake myself the first time I went to flash CM7. In fact, what took me the longest the first time around was that I unlocked out of order, so I could not boot into CWM for the longest time.
Sent from my MB860 using xda premium

I have twrp, but that is it.

I had cm7 and stupidly hit the reboot into recovery button. Then I was in the recovery bootloop. I tried to fix it but didn't have have adb access in twrp. I tried to install the stock update instead. It went through everything except installing the update. So it wiped every thing but recovery. I still don't have adb access, kindle is not showing as a storage device on my computer, and all I can get into on the fire is twrp. I'm kinda stuck. Any help would be very much appreciated.
Edited to add: I got it. I tried from another computer. It was a driver issue.
Sent from my MB860 using XDA App

Flashing Rom always ends in boot loop?

I have had my N7 for a week now, and have unlocked and rooted it. I flashed the jr5 rom and it worked ok, but i decided I wanted to try the pure AOSP rom, so I did a data/cache/dalvik wipe and flashed the rom. It proceeded to boot and freeze at the Google screen. I rebooted into recovery, and attempted to restore from my backup (failed), flash the jr5 rom (failed), and reflash the AOSP rom (failed). I then decided to follow the instructions on ROOTZwiki and restore back to stock (although still unlocked). I restored to the factory image, and attempted to flash the CM10 AOKP rom, and was again met with the frozen Google screen. I made sure to wipe data and both caches each time i tried to flash a rom, but I always end up stuck at the Google screen. What could be causing this? I would really like to know if anyone has any idea, because I fully plan on running the full version of CM10 when it is released.

By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app

redmonke255 said:
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
yes i did a factory data reset each time. I am currently running v5.8.0.2 of cwm

could that be the problem? that my cwm is just outdated already?

No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium

CharliesTheMan said:
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you for taking the time to help me. Before I do the goo-manager/twrp install, are there any inherent advantages or disadvantages of using twrp as opposed to cwm? Also, I hadn't thought to check md5s after moving the roms, so I will be doing that from now on.

Twrp works just fine.
In your recovery, can you mount and unmount all your partitions without any errors?
Sent from my Nexus 7

am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?

crache said:
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
Click to expand...
Click to collapse
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.

simms22 said:
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
Click to expand...
Click to collapse
I don't like Twrp not being able to boot into recovery from holding the buttons, especially running into these loops during installs. Had the sameresults with cwm though.Now I am having this boot loop with TeamEOS as well as Skanky (neither package gapps) I however only loop if installing gapps after the rom or wiping caches.
If caches and system are wiped, gapps installed, then the rom I get a functioning system.Can anyone shed some light on what trigers specific loops or how to review tje errors / panics?

I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?

spked said:
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
Click to expand...
Click to collapse
Do you flash the rom and gapps and then reboot, or flash the rom, reboot, then flash gapps?

Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.

dirtyhamster73 said:
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
Click to expand...
Click to collapse
Can you get to bootloader?

If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2

Jordanooo said:
Can you get to bootloader?
Click to expand...
Click to collapse
I finally got in, so I'm all set. Thanks! I have no idea why I was having a hard time...twrp wouldn't pop up once I was in boot loader. I must of tried like 20 times. Anyway....I'm in and I just reflashed and it was fine.
---------- Post added at 05:42 PM ---------- Previous post was at 05:40 PM ----------
armyboy11b said:
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm using twrp...for whatever reason I couldn't get it to pop up to reflash. But I'm good now. Thanks!

A500 cannot mount, format, or wipe /data

Hello guys. After 48 hours of searching forums I couldn't not to find someone with my problem so here I go. My device is an Acer Iconia a500. I am using skrilax v6 unlocked bootloader and the A500 public recovery. I can install any ICS rom. After the acer screen and the rom specific animation appears, the animation runs for hours, going nowhere. Recovery will not let me mount, format or wipe /data. Power plus volume- gets me in recovery just fine. When I attempt to format or mount data in mounts and storage, all I get is "error mounting(or formatting) /data!" Mounting and formatting everything else seems to work just fine. I assume this is preventing my roms from booting. When i hold power plus volume+ I get a menu as follows:
Reboot
Fastboot Mode
Boot Recovery
Set Boot Secondary Kernel Image
Set Debug Mode Off
Wipe Cache
Using windows xp because windows 8 is still buggy, I've used fastboot to try other recoveries likes thor's newest touch recovery and I still get the same error. "error mounting(or formatting) /data!" I cannot use adb commands. I'm assuming /data is corrupt and preventing me from booting entirely. Please advise and I'll pay for your beer. Thank you!

In the android developement files for the iconia a500 search up either how to rollback from ics leak or how to fix a bricked acer a500 you are going to need your sbk and you will have to use nvflash... it will work eventually although you will have to reflash the bootloader
Sent from my A500 using xda app-developers app

Thanks!
startinoffsmall said:
In the android developement files for the iconia a500 search up either how to rollback from ics leak or how to fix a bricked acer a500 you are going to need your sbk and you will have to use nvflash... it will work eventually although you will have to reflash the bootloader
Sent from my A500 using xda app-developers app
Click to expand...
Click to collapse
Got my sbk and I'll check out what you said immediately. Thanks mate :good:

Don't mention it
Sent from my A500 using xda app-developers app

Worked!
I followed http://forum.xda-developers.com/showthread.php?t=1579490 and it worked smoothly and quickly. Thanks again! :victory:

thanks startinoffsmall and FXtreme. i had the same issue as you FXtreme and i performed the same steps and its back to stock. so glad. so FXtreme what did you do next? did you go back to a rooted ics rom or did you move to a jellybean one yet?

[Q] A500 hangs at booting primary kernel image

My Acer Iconia A500 was frozen, I turned it off by holding the power button, since then, I can not reboot the tab, it hangs at booting primary kernel image.
I have Skrilax_CZ V8 bootloader, CWM recovery 1.7.3, and the Flex-Resurrection_Rev1-Aroma-Public Rom.
-----------------------
I searched here, tried the methods by Moscow Desire
"Boot to recovery, and this time, do all your wipes
Wipes Menu
a. wipe Data/factory reset
b. wipe cache
c. wipe Dalvik
Go to Mounts and storage
a. Format system
b. Format Flexrom
Install rom, and make sure it's a rom with an ICS kernel.
As a last chance if the above normal things don;t work,
you may have corrupted data somewhere, and in this case, go to Backup and Restore and toggle Data Media."
------------------------
And tried method by Skrilax_CZ
"You can also wipe userdata from fastboot: "fastboot erase userdata".
-----------------------
I did it several times, after installed the Flex Rom, ( I also tried the Lightspeed_4.8,) it still stuck on the booting primary kernel image, What should be my next step?
I saw somewhere Dibb_nz mentioned that re-flash the BL, recovery.img, not sure if I should try. I do have the CPUID and SBK numbers.
Thanks for your help, anyone out there.

I'm having the exact same problem. I tried what you did, and it still didn't work. This is my first time flashing, so I'm not sure what to try next. I do have one idea - I thought the ROM did have a kernal, so I didn't flash one. I'm going to search for one and try that.

I switched to Skrilax's V9 bootloader thinking that might help but it didn't. When I do a recovery with the back up of my normal rom I made before flashing then and only then can I get past the bootloader. The backup says there's an error when recovering my data though, so I'm going to have to start over from fresh either way.
Any help would be greatly appreciated. I've been at this for over 7 hours now.

Run babsector file, download and instructions here http://forum.xda-developers.com/showthread.php?p=35500589
Sent from my GT-I9300 using Tapatalk 4

dibb_nz said:
Run babsector file, download and instructions here http://forum.xda-developers.com/showthread.php?p=35500589
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Thank you for replying. I went back to the normal ota rom from Acer, but will keep this in my notes if I try it again.