Database Users

[Q] Team EOS Help needed with latest nightlies

Hi Guys,
I am not sure if I am posting in the right place, but I could use some assistance on the Team EOS nightlies. They won't let me post in the DEV section yet, becuase I am mostly reader, not a poster. Anyway....
I've been running the EOS roms for a while, but I can't seem to run any nightly past 74. 74 runs great, when I tried to update to 75 (rom/gapps/wipe cache) it won't get past the "DUAL CORE" logo. I thought I bricked my xoom, but I am able to boot to recovery, reflash 74 (gapps/wipe) and it boot with no issue. I did a full wipe, and tried again with 76 but no joy (77 wasn't out at the time). I thought it was a problem with n75 and n76. I flashed back to n14 and it works fine, and I can upgrade back to n74. Tonight I tried to update again to n77, but still no dice. I let it sit for 15 minutes at the "Dual Core" logo, and all I noticed is that is got warm, but still no boot.
Any thoughts? All advise is welcome!
BTW, this is for a Stingray 4g xoom
And while I have your attention, I love the work you guys do, and this community, it really makes Android something special!

Weird. Try going into fastboot and do a full wipe of userdata, cache, and system. Then install. If need be, do a backup. This will totally wipe your device.

Wipe cache, wipe dalvik, flash ROM, flash GAPPS, fix permissions. Do it in that order and you should be fine.
Also make sure your using the latest GAPPS. It should be dated 2012-03-17.
Good Luck.

Still not working right, very frustrated, but I have new information
dellenrules said:
Wipe cache, wipe dalvik, flash ROM, flash GAPPS, fix permissions. Do it in that order and you should be fine.
Also make sure your using the latest GAPPS. It should be dated 2012-03-17.
Good Luck.
Click to expand...
Click to collapse
bigrushdog said:
Weird. Try going into fastboot and do a full wipe of userdata, cache, and system. Then install. If need be, do a backup. This will totally wipe your device.
Click to expand...
Click to collapse
Thanks to both of you. I did try this. What I have discovered so far is that some of the flashing fun I have been doing with my may have caused so minor issues with my external SD Card. I backed up the internal to it, and pulled it. I went through the process of nuking the xoom entirely. I.E. Wiped Cache, dalvik, full wipe, factory reset, reset permission, and deleted everything off the internal SD (wasn't in this order, but it all got done) I was able to flash N77, without GAPPS fine. It seemed to run faster with nothing else installed. Rebooted a few times, no problem. I was stoked. I flashed gapps, 03-17 version (the latest). factory reset again so that it was fresh and wiped the cache (just in case). It booted again no problems, ran me through initial config, and then began downloading my apps back. It seemed to run much faster than it ever did before.
Then I rebooted it, without doing any titanium backup restores, just fresh tablet, N77 with my 90 or so apps freshly installed from the market, and it froze again at the "Dual Core" boot screen. I waited hoping for some delayed joy, but none came.
So I went back through the process once again, factory reset, N77 install, wipe cache, install GAPPs. Booted.....initial config, auto downloaded 90 apps from market, reboot......dead.
So then I just flashed N74 again, wiped cache, install GAPPS, initial config, app download.....reboot.......works fine.
<general frustration directed at tablet, not anyone here/>
What gives???? I can't tell what the difference in internal apps in the ROM are that could be conflicting with the ones installed from the market.
Why the hell is N74 working and N77 not, when the apps in both ROMs look the same?
Why does N77 work great when the apps aren't restored?????
Why don't I make a million dollars?????
Why aren't I emperor of the universe???????????????
</general frustration directed at tablet, not anyone here>
Thanks much for all your help!

alright.... i have 2 suggestions these may not work and the second one is a pain in the butt to do but it got me out of a jam way back when i lost my softkeys no matter what i flashed
firstly.. in the sequence of your flashing throw in the 'format /system' see if that has any effect it is 'possible' the system is not being flashed correctly or it could be possible that it is getting corrupted and causing the bootloops (i always format system when full wiping)
second... and this is a pain.. but you can always try flashing back to STOCK... there could be other factors that aren't being flashed or fixed correctly causing ya problems... you can then go through the process and flash directly to the latest build... as i noted earlier this fixed a problem that nothing else could for me and has helped others but really this is a last last resort as it takes alot of time and screwing around
lastly... i have no idea sorry these are all i can input.. if possible can always try and use logcat while booting to see what is causing the crash if im not mistaken and upload a log and one of the devs may be able to have a look at it...

I Would stop dinking around with n77 and go to n90 I had the same issues around those nightly numbers, so I went all the way back to stock... (honeycomb) didn't fix it but I redid the whole install on a higher number and it seems to work itself out..... long story short try another maybe the 1.0 stable by them.

fkntwizted said:
I Would stop dinking around with n77 and go to n90 I had the same issues around those nightly numbers, so I went all the way back to stock... (honeycomb) didn't fix it but I redid the whole install on a higher number and it seems to work itself out..... long story short try another maybe the 1.0 stable by them.
Click to expand...
Click to collapse
He has the STINGRAY not the WINGRAY Xoom.
N77 is the latest for the 4G version. The version he has.
Read the OP

EOS Nightlies hate my xoom, my Xoom wanted CM9 I guess
joshndroid said:
alright.... i have 2 suggestions these may not work and the second one is a pain in the butt to do but it got me out of a jam way back when i lost my softkeys no matter what i flashed
firstly.. in the sequence of your flashing throw in the 'format /system' see if that has any effect it is 'possible' the system is not being flashed correctly or it could be possible that it is getting corrupted and causing the bootloops (i always format system when full wiping)
second... and this is a pain.. but you can always try flashing back to STOCK... there could be other factors that aren't being flashed or fixed correctly causing ya problems... you can then go through the process and flash directly to the latest build... as i noted earlier this fixed a problem that nothing else could for me and has helped others but really this is a last last resort as it takes alot of time and screwing around
lastly... i have no idea sorry these are all i can input.. if possible can always try and use logcat while booting to see what is causing the crash if im not mistaken and upload a log and one of the devs may be able to have a look at it...
Click to expand...
Click to collapse
Thanks much for this. I had already attempted the formatting of everything except the SD card before.....but for sh*ts and giggles I tried it one more time. unfortunately that didn't work.
Using the second option, of reverting stock, I went through sleeplessnija's tutorial on reverting. It really didn't seem that bad, taking me longer to setup my work machine than it did to send the fastboot commands. I was able to get it to boot stock (of course I didn't re-lock it) just fine, and it was quick....so it seems like my hardware is fine.
I used fastboot to put the replacement tiamat recovery, and formatted everything in the mounts menu again. I also mounted my SD card as USB storage and used the full format for it under windows. Then i copied N77 and GAPPS back to it, and re-installed them. It got to the second boot logo (first was the shaking team eos, the second is the square thing with rounded corners that moves). It hung for about 10 minutes, and I shut it off. annoyed.
So I went back into recovery, mounted my SD for USB access from my desktop, and copied the unofficial (which I think is now official) CM9 distro from Team Rogue (Steady's Rom I believe?). I formatted everything, and wiped everything (except the SD) again, and installed CM9 and gapps. Booted fine. Configured account, downloaded 90 apps, rebooted, no problems. Played with it for a while, rebooted....no problems.
I like that my xoom is back up and running......however it seemed that Steadies rom is just a little less fully featured than Team EOS. THAT IS NOT A KNOCK AGAINST TEAM ROGUE OR CM9.....my Xoom is working again (so far) thanks to him (them), and I run CM9 on my AT&T GSII. I just really like Team EOS on my Xoom, and have been with them since the beginning. I would love to know why my xoom suddenly hates the latest nightlies (everything since 74).
Edit: I forgot to ask, Joshndroid.....you mentioned running logcat to see what going on. If it can't boot past the dual core logo or the second boot logo from Team EOS....how do I get the logs? I am not familiar with android's logging.....even though I am a flash-a-holic. I am just thinking that if this is happening to me, maybe I can help out the devs (and myself, and maybe someone else) with the log output.
Edit 2: And Josh.....I forgot to tell you .....good call on the revert to stock answer. I didn't think about that before and thought I was screwed!
Thanks!!

nexus 7 wont boot....... kinda

So ive had my n7 for a while and had over 10 different roms that i went through before landing on cookies and cream for 4.1.2 and cyanogenmod for 4.2.1
Well heres the problem. i was getting pissed off at all of the bugs and random reboots and incompatabilities so i fully wiped the device, minus bootloader, and flashed stock 4.1.2, it booted great
heres where it went wrong... i tried flashing cyanogenmod 10 via twrp, letting it use its stock kernel and even trying a different cm compatible kernel after booting failed.
when that didnt work i went back to stock, downloaded cookies and cream, wiped the rom, cache and dalvik cache. still bootloops
so i was like F**k it, and installed stock 4.2.1, booted fine.
tried again with the 2 latest cyanogenmod nightlies, which i know worked fine from before
still just bootloops with no idea how to fix it.
just to be clear, stock works, custom WILL NOT

bump guys, im kinda up **** creek without a paddle, emphasis on the kinda part

I have a similar problem(http://forum.xda-developers.com/showthread.php?t=2073977). Pretty much the only way I can get a ROM to stick is if I wipe /data as well. Not sure what's causing this, but I'm working on it. I think it could have something to do with the way that android stores some of it's /system data in /data at times
What's worked for me to flash a ROM other than stock, is to wipe the entire thing, and then use adb sideload to load the ROM.

Hey bro, i saw your thread before, by data, do you mean internal storage or just the system rom itself, because i wiped everything but the bootloader and started from scratch

I'm just talking about /data. An hour ago I noticed that as long as I use the Factory Reset option in TWRP, it will wipe it, and not touch the stuff on the sdcard(it could be just me though, my Nexus seems to be kinda weird). Then I wipe system, and flash whatever I need to.

Alright, one problem though, doing a factory reset deletes everything on the sdcard then when i try to use fastboot to flash cyanogenmod in a zip format it says stuff like android-product-info.txt is missing and whatnot, what do you do?
edit, dont read the part about wiping storage, i had a idiot moment there, ill give it a shot

[Q] Paranoid Android 3.15 rebooting several times a day Nexus 4

I have a Nexus 4 running PA 3.15, I love PA, but I get random reboots every few hours.
I rooted this phone and the only thing I flashed was PA. So it was a clean install. I tried factory resetting the phone and doing another clean install and the rebooting still exists.
I am not using an custom kernel, maybe flashing one would help my situation. I am at a crossroads, because PA and it's pie feature are amazing, but the rebooting is making me want to leave.
Any ideas on how to fix it?

Download it one more time then gapps. Wipe everything, flash PA, flash gapps wipe cache, wipe dalvik cache. It must work. Other apps install manually.

If it's using superuser, try disabling it and use supersu instead.
i found some apps hate superuser and strange stuff happens.

I will try using supersu and see what happens. Thanks.

trentgillham said:
I will try using supersu and see what happens. Thanks.
Click to expand...
Click to collapse
I am still having this problem despite clean install. did anyone find a definitive answer. thanks

jadsru1 said:
I am still having this problem despite clean install. did anyone find a definitive answer. thanks
Click to expand...
Click to collapse
I was also having the same problem, my phone sometimes get really hot and it keeps on rebooting. I tried flashing the stock ROM, new kernel everything I could but the problem still persisted. So I called up Google Customer care, as soon as I told them overheating and rebooting, they transferred my call to RMA and they replaced my phone. My phone was 5 months old and recently many people are having this problem, so its better to get it replaced. Before sending it, reflash the phone with Stock ROM and lock the bootloader. You should be fine

[Q] Problems with Process System on PA 3.98

Hi!
I recently updated my ROM to the Paranoid Android 3.98, I did a full wipe, flashed the ROM, latest Gapps (with TWRP) and ever since the tablet has been become really laggy on opening apps or doing anything. I realised something was wrong straight after I booted it up by how long it was taking to connect to the WIFI etc.
Anyway, its hanging a lot on the unlock screen and sometimes I get a "Process System is not Responding" prompt. I've tried going back into recovery and clearing the caches/data again and its still hanging. Ive also tried using CWM recovery to wipe the tablet, flash the ROM/Gapps etc and its still really slow. Lastly, I just tried a factory reset from the settings menu and again, its still the same!
Any ideas on whats up with it and how to sort it out? I was thinking about unrooting it back to stock although I think the problem will still probably happen. I came from the PA 3.95 build and did a clean flash.
Cheers!
Chris

I think I have fixed it by following a post by Chasmodo on how to do a super-clean install.
1) I booted into recovery.
2) Did the three wipes (Data, Cache, Dalvik) several times over.
3) Went to Mount & Storage and formatted both system & cache*.
4) Flashed PA 3.98 & latest PA-Gapps.
5) Wiped both caches again and rebooted.
As soon as connecting WIFI, signing into Google I could tell it was running a lot faster again and now the lag on the unlock screen & opening apps seems to have stopped, also haven't had the "System Process isn't Responding since."
*Chasmodos version of the super-clean install didn't say to format the cache as well although I had tried just formatting the system and it didn't fix the issue. So I thought I'd try the same process with a cache format as well and now all issues seem to have been rectified.
Cheers
Chris

[Q] CM & PA question

I got a question guys, i flashed the latest version PA for our device (PA4.5 beta 2) and notice i was having random reboots, i thought it was the rom, so i flashed CM latest nightly (2014815) & still was having reboots, so i figured it had to be an apk not playing nice & thought i was right when i noticed it was happening the most while using chrome, but it happened during the settings and some other apks, its not constant though, it very random, its like when you stay on an apk for a while, it just randomly reboots, anyone else been having this issue? or had this issue?, i both like two great theses for these roms & would feel like a fool if i cant use em lol, so any help would be appreciated, thanks

Are you wiping between flashes or dirty flashing?
If flashing clean, restore your apps (without data backups) one at a time. If you stop having the issue, then restore your app data one at a time.
If that doesn't fix it and you're flashing clean, going back to stock and doing a factory reset will almost certainly solve the issue.

frostedunit said:
Are you wiping between flashes or dirty flashing?
If flashing clean, restore your apps (without data backups) one at a time. If you stop having the issue, then restore your app data one at a time.
If that doesn't fix it and you're flashing clean, going back to stock and doing a factory reset will almost certainly solve the issue.
Click to expand...
Click to collapse
I always clean flash, I decided to flash sacs until a next major builds releases, thanks though

What kernel are you using?