I currently have a Wifi Xoom running EOS Wingray-62, and Gapps 10.5.
I have been on the nightly builds for awhile. The EOS ICS is great, and keeps getting better!!!!
Yesterday I turned my Xoom on and it got stuck at the Team EOS splash page.
I did a quick reboot, hoping this would fix the problem, but it didn't.
I can still get to ClockWorkMod, so I have done the following:
Wipe Data/Factory Reset
Wipe Cache Partition
Wipe Dalvik Cache
Still no luck....
Any idea's what I am doing wrong?
Kenar said:
I currently have a Wifi Xoom running EOS Wingray-62, and Gapps 10.5.
I have been on the nightly builds for awhile. The EOS ICS is great, and keeps getting better!!!!
Yesterday I turned my Xoom on and it got stuck at the Team EOS splash page.
I did a quick reboot, hoping this would fix the problem, but it didn't.
I can still get to ClockWorkMod, so I have done the following:
Wipe Data/Factory Reset
Wipe Cache Partition
Wipe Dalvik Cache
Still no luck....
Any idea's what I am doing wrong?
Click to expand...
Click to collapse
probably a bad download, restore a backup and redownload and try again
I checked to see if I had a bad download.
I downloaded the newest wifi nightly, and completed the following steps:
Wipe Data/Factory Reset
Wipe Cache Partition
Wipe Dalvik Cache
Loaded EOS-wingray-75.zip
Loaded GAPPS 10.5
I did get the new EOS splash screen in the lower right hand corner, but it just sits there.
Any ideas?
try to flash eos 1.0 wifi
Wipe Data/Factory Reset
Wipe Cache Partition
Wipe Dalvik Cache
flash eos 1.0 wifi
flash the gapps in the same cwm session!! then reboot
or try to flash an older version instead of 75
check md5 before flashing
Thanks for the reply....
I flashed an older version of the EOS nightly that had worked in the past.
The Xoom still didn't make it past the splash screen.
For fun, I also flashed CM9, and Bugless Beast for the Xoom Wifi. Still didn't make it past the splash screen.
Thanks for your help.
do you have anything important on your internal memory? If not, you could always try to "fastboot oem unlock" again, as that would clear your internal memory.
(For me, getting stuck at the boot-logo could always be fixed by wiping /data. With Tiamat recovery however, "wipe /data" will not really wipe /data as to conserve contents of /sdcard [which is linked to a folder beneath /data])
"fastboot erase userdata" might also do the trick, but I'm not positive on that one.
My Xoom is working again....
I was able to use the fastboot oem unlock command.
Thanks for all your help.
Related
As of now, I am trying to install the Wingray Nightlies #96 & GApps 4/22/2012.
I am trying to update my wifi xoom from nightly #90, and get stuck.
I began my endeavor with EOS 1.0.0. I installed nightly #90, ran for a while and then tried to update to #92. (Factory reset, cleared cache, cleared dalvik, installed #92, installed #GApps, reboot) and then get stuck at Motorola screen.
Rinse, repeat, and stuck at Motorola again.
So I do a restore and am back at #90.... I tried again every few days, downloading new copies of the .zips (Nightly & GApps) thinking something was corrupted, but no dice...
Today I tried to update to #96 and GApps 4/22/2012, but am getting the same result.
ALSO: I have tried the EOS Recovery, to see if the recovery was the issue... No luck.
After you clear cache and dalvik, format data and system.
Once you do that, flash the ROM, GAPPS, then fix permissions before you reboot.
Doing that will wipe everything but it should boot up to EOS from there.
First boot should take a while.
Enjoy
dellenrules said:
After you clear cache and dalvik, format data and system.
Once you do that, flash the ROM, GAPPS, then fix permissions before you reboot.
Doing that will wipe everything but it should boot up to EOS from there.
First boot should take a while.
Enjoy
Click to expand...
Click to collapse
Tried with no luck. Once again, fresh downloads, and followed step by step ^, then sat at Motorola for about 8 minutes...
Is there a set of .img files that I can push by fastboot?
TeamEOS posted some files that should help. Give it a try. The link is on the wingray thread in development.
Okay, so when I attempt to flash the CM9 nightly (7.2.12 edition) and the Google Apps ICS from CyanogenMod's wiki page I get a soft brick in reboot loop. What happens is three things (it's happened differently each time): First, I get the white SAMSUNG logo. After that, I get an extra-long black screen before a bootscreen. The first time it was an ANDROID logo with moving reflections. The second time it was the CM9 bootscreen. The third time it was simply a white screen. All three times, shortly after the bootscreen began, the phone froze at one frame early into the animation and rebooted. The same thing continually happened. To flash the ROM, I have the newest CWM Recovery for the T-Mobile Galaxy S II installed. From there, I did this (in this order): wipe data/factory reset, Wipe Dalvik Cache, and then Wipe Battery Stats. From there, I flashed the ROM from the internal SD card and then Google Apps for ICS from the internal SD card. After going to reboot from CWM Recovery, I always got that soft brick (three times now). After each soft brick, I have used CWM Recovery to recover a previous instance on the stock ROM.
Any help will be rewarded with imaginary thanks.
wipe cache, format system, format data
http://www.teamchopsticks.org/p/install-guide.html
Here are the steps but for me personally I do 3x cache/3x dalvik and I have installed every update just fine. :good:
Ends said:
wipe cache, format system, format data
Click to expand...
Click to collapse
Okay, worked on second try. Did steps first time, fail. Try again with usual steps, currently in boot screen lacking loop. Thanks!
P.S. UZ7 - Too late hehehe. Thanks anyways, have a cookie.
Sent from my MB860 using xda app-developers app
Okay, wipe cache, format system and data left my device in bootscreen all night. I'm trying the TeamChopsticks method now...
And...
Bootscreen not freezing...
Got soft touch button lights...
Success!
I have clockworkmod recovery installed and rooted. It's been a few months since I rooted, and can't remember exactly what I did, but OTA updates stopped working. Hence, I am still on gingerbread.
Trying to flash a custom rom now, CM9. I tried the rom manager method several times, found out that wasn't recommended, and then tried the recovery method.
The same thing happens either way: it boots into CM9, but the boot animation keeps playing.
With the rom manager method, I tried wiping nothing, then tried wiping dalvik only, then tried... whatever the other option was, wipe cache and data?
With CMW recovery I downloaded CM9 zip and the appropriate GAPPS, moved onto the internal SD card, booted into recovery mode Wipe data/factory reset, then Wipe cache partition, then install both.
I'm able to restore from backup each time, but this is annoying.
Thank you
1. Install ICS Radio (UCLF6)
2. Wipe Data/Factory Reset
3. Format /System
4. Install CM9.zip
5. Install Gapps.zip
6. Wipe Cache/Dalvik
7. Reboot
:good:
UZ7 said:
1. Install ICS Radio (UCLF6)
2. Wipe Data/Factory Reset
3. Format /System
4. Install CM9.zip
5. Install Gapps.zip
6. Wipe Cache/Dalvik
7. Reboot
:good:
Click to expand...
Click to collapse
So "UCLF6" appears to be rom that is similar to stock, I'm guessing the idea here is that I'm resetting the phone but retaining root, the idea being that something on my phone is messed up and preventing CM9 from booting but doesn't prevent the current rom from booting?
Two other questions
1. Won't format/system wipe out all my backups in addition to my data?
2. Have you had or seen this problem before? I'm hesitant to commit myself to something, especially with no backups, if it's just a theoretical fix. I do appreciate it either way.
UCLF6 is an ICS modem/radio you need if you're coming from gb.
If you back up though CWM you can restore again later if you want.
Formatting /system will delete the operating system.
Formatting /data will delete your apps/settings/wallpaper etc...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I had a similar boot animation loop when I went from stock GB to stock ICS. What seemed to fix it was updating my CWM from 5.0.2.6 (non-touch) to 5.5.0.4 (touch). (BTW, I couldn't find an advantage of stock ICS over stock GB. I have since put on CM9 which I'm liking).
UZ7 said:
UCLF6 is an ICS modem/radio you need if you're coming from gb.
If you back up though CWM you can restore again later if you want.
Formatting /system will delete the operating system.
Formatting /data will delete your apps/settings/wallpaper etc...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Still got the boot loop.
When I did the "Wipe data/factory reset" I did get an error message during one of the processes"
"Error mounting sdcard/.android_secure!
Skipping format"
I had a boot loop problem when I first tried to flash JB. I went from GB to ICS with a custom rom a few months back, but I couldn't get any of the new JB roms to work. I ended up having to upgrade my CWM to the touch version in order to get JB flash to work. Also, a tip-- the boot animation will take a minute or two even when it is working. Don't assume it is still a problem if you see it more than once.
Hi, this is the first android device I have played with so naturally I managed to mess it up.
The problem is with an Iconia A510, wrong forum but didnt find a Q&A for A510 so I tried here instead.
I rooted and installed CWM recovery. The custom firmware I have tried or stopped during boot and rebooted the device. Booted for 10-20 seconds, I see the animated logos before it reboots.
I upgrade with:
wipe data/factory reset
wipe cache
advanced -> format /system
advanced -> format /data
advanced -> format /cache
install zip from sdcard -> external sdcard
Am I doing something wrong with the upgrade? Can I upgrade CWM from inside CWM so I can try the latest Android version? Is there a firmware version that will work?
Info:
Files from: acer shreps fr
CWM version: CWM Recovery v6.0.1.9 by NoThrills for A510 tablets. Apparently can try KitKat with it, so only tried older Android.
All installed OK but stopped during boot:
7comp-JB-a510-Nightly-20130808
aokp_a510_jb-mr2_unofficial_2013-12-05
cm-10.1.3-20130925-UNOFFICIAL-a510
cm-10.2-20130826-UNOFFICIAL-a510
cm-10.2.1-20140201-UNOFFICIAL-a510
pa_a510-4.1-BETA2-20140315
did you try to wipe data or/and dalvik cache after you installed the rom? (DONT WIPE SYSTEM!)
sometimes this will work for me.
graafschap101 said:
did you try to wipe data or/and dalvik cache after you installed the rom? (DONT WIPE SYSTEM!)
sometimes this will work for me.
Click to expand...
Click to collapse
Thanks for the tip. I tried wiping the usual suspects, flashing a CM rom and then flash data and dalvik cache. Same thing; started booting, the CM logo comes up and starts spinning before it freezes and reboots.
I'll play around a bit more. Tried the 'fix permissions' in CWM recovery, no go.
Solved it. Formatted everything except external_sdcard, flashed with AOKP and booted fine. Magic!
Well, I'm coming from the stock 4.4 XT3032. Flashed CWM Touch, followed the steps, which are "WIPE (wipe data/factory reset + wipe cache partition and format system)", but nothing. I'm stuck at the (beautiful) Boot Animation.
I tried doing the same with TWRP, but I got no results.
Right now, I can easily sideload any ROM) with TWRP and flash it to survive, but the idea is to get C-Rom to work. Any ideas?
CM11 is also stuck on the Boot Animation, but MoKee IS working for me, but I don't want to stick with it for everyday use.