Database Users

Infinite Loop

Hey all, first off, sorry if this is the wrong forum. If it is could one of the mods please move it.
OK, here's my issue. I had CyanogenMods latest build, 3.4 I think and decided to try The Dudes cupcake 1.RC1. I forgot to do a wipe before installing TheDudesCupcake but when my phone came up it worked ALMOST fine. Had a crash here and there of something, not sure what, but the phone still worked fine. Today, I had an issue with a video (is the SD Card) not being viewable with "Video Player" so I decided to remove the card and pop it back (hoping this would somehow refresh the player). Didnt unmount it so I got the error about i may loose data without unmounting. (i'd done it before without a problem). Well this time around my card was corrupted so I ended up formatting with the phone. tried going into settings to view the size of the drive not since I didnt know if the whole card was wiped or only the FAT32 partition. Kept getting an error while trying to go into settings so I decided to reboot. After reboot I was able to get into settings and saw the whole card was wiped (back to full 8GB of empty space). Thought I would wipe right there from settings since I was getting an error or 2 after reboots and since I had gotten that error when trying to get into settings and then updating back into Dudes Cupcake. (thought the wipe would get rid of any issues of going between Cyanogen to Dudes Cupcake). Once I clicked on wipe and android reboots, it's trying to do something but just keeps rebooting. I've got Cyanogens restore image v1.2 on. So I see the G1 logo, then comes up
Build CyanogenMod v1.2 + JF
Formatting DATA ....
and at the Formatting DATA part it does the reboot and goes back to the G1 logo and comes back to formatting data and reboot.
I tried doing a HOME + POWER but it just goes back to formatting data. I tried doing a CAMERA + POWER but it goes back to formatting DATA.
Any ideas would be appreciated.
Thanks and sorry for the long post, I just wanted to give all my steps.

Huascar82 said:
Hey all, first off, sorry if this is the wrong forum. If it is could one of the mods please move it.
OK, here's my issue. I had CyanogenMods latest build, 3.4 I think and decided to try The Dudes cupcake 1.RC1. I forgot to do a wipe before installing TheDudesCupcake but when my phone came up it worked ALMOST fine. Had a crash here and there of something, not sure what, but the phone still worked fine. Today, I had an issue with a video (is the SD Card) not being viewable with "Video Player" so I decided to remove the card and pop it back (hoping this would somehow refresh the player). Didnt unmount it so I got the error about i may loose data without unmounting. (i'd done it before without a problem). Well this time around my card was corrupted so I ended up formatting with the phone. tried going into settings to view the size of the drive not since I didnt know if the whole card was wiped or only the FAT32 partition. Kept getting an error while trying to go into settings so I decided to reboot. After reboot I was able to get into settings and saw the whole card was wiped (back to full 8GB of empty space). Thought I would wipe right there from settings since I was getting an error or 2 after reboots and since I had gotten that error when trying to get into settings and then updating back into Dudes Cupcake. (thought the wipe would get rid of any issues of going between Cyanogen to Dudes Cupcake). Once I clicked on wipe and android reboots, it's trying to do something but just keeps rebooting. I've got Cyanogens restore image v1.2 on. So I see the G1 logo, then comes up
Build CyanogenMod v1.2 + JF
Formatting DATA ....
and at the Formatting DATA part it does the reboot and goes back to the G1 logo and comes back to formatting data and reboot.
I tried doing a HOME + POWER but it just goes back to formatting data. I tried doing a CAMERA + POWER but it goes back to formatting DATA.
Any ideas would be appreciated.
Thanks and sorry for the long post, I just wanted to give all my steps.
Click to expand...
Click to collapse
when it says formatting data then done, are you pressing and holding home and back or just pressing and releasing. when the phone is powering on and you hold the home and back keys it will do a hard reset just like a wipe(same thing) or since there is no data to lose any more, try pulling the battery, this will not do any harm as you are not flashing anything
since you have the cyanogen recovery image you should have gone into the console at recovery and typed
fix_permissions.sh or sh fix_permissions.sh

Thanks for the response tubaking. My problem was that it didnt say done. right when the "Formatting Data...." line came up, it reboots, without saying done. And I couldnt get into the Home+Power or the Camera + power screens. Neither one would go there, just back into "Formatting Data:..." screen. After reading half way through the Brick thread I saw someone mention pulling the SIM card out, didnt think that would help but it finally dropped me back into the recovery console. Might I ask why something as simple as removing the SIM drops the loop and takes you to recovery?
thanks.

[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!!

[Q] Stuck on boot loop

I used manual nooter over weekend, everything has been working well, but I did have a hard time figuring out soft keys. For reasons I'm nott sure when I tried to use Nook color tools I could only get to BN tools, not the option for all settings which was originally there. I decided to power Nook off an turn back on as that often helps on my Bionic. Well, upon turning on I had the orange menu askin if I wanted to reboot, restore etc. I tried rebooting, was stuck on loop, powered back on and off, did a back up, tried to reboot again and stuck on loop. Do I need to do a complete wipe and start over? SD card seems to be working fine. Any thoughts? Everything else seemed fine, could use play store etc. I did download Firefox last night. thanks.
Updating, through another thread on this forum I went into CWM recovery, did a factory reset, cleared cache, wiped dalvik and rebooted. I think I am getting back to stock, Nook is trying to connect to WiFi, but my office router isn't showing up. Once I get past this, hopefully I can connect somewhere and try Manual Nooter again. Crisis averted, I think.
Last update, sorry for the panicky post. Was able to connect to Wifi, re-register Nook, then reinstall ManualNooter from SD card. Bootloop is gone, CWM recovery worked. After searching deep enough with the posts, everything is working as it should. Thanks for all of the info here and tolerating my Nooby panic.

[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]Omni Xoom Wingray boot problem

I recently rooted and installed OmniROM on my Xoom, but am having problems getting the tablet to boot. It makes it past the moto screen, but gets stuck on the blinking omni logo.
I followed the instructions in this thread, but I can't seem to get it to work. I have tried the entire process twice, and tried omitting gapps and even the update. Anyone have an idea what I am doing wrong?
If it means anything, TWRP is unable to wipe Dalvik, data or Internal Storage.
Thanks in advance!

Okay Scratch that. I did a reformat/reinstall and it finally booted. Now I just need to figure out that Text To Speech engine error.:good:

I have the same problem but with the Everest version
I have gone back to Gingerbread then back to EOS4
What did you do to reformat?
Did you successfully manage to wipe the dalvik cache and data etc?
OK in case anyone else had the problems I had then this repartitioning guide helped me. It was slightly different than the guide here, ie not just a wipe everything and expect it all to be ok kinda thing.
I was running my Xoom with the last EOS build and had an earlier version of TWRP. I started by upgrading in recovery to the NonBigPart TWRP and then followed the instructions from this link to repartition format etc and it worked for me.
http://forum.xda-developers.com/showthread.php?t=2506997

Same Problem - can you explain more?
Zaxxon8 said:
Okay Scratch that. I did a reformat/reinstall and it finally booted. Now I just need to figure out that Text To Speech engine error.:good:
Click to expand...
Click to collapse
I have the same problem. Can you explain what you mean by "a reformat/reinstall and it finally booted"? My Xoom is stuck on the Omni Android screen with the android blinking, but will not finish loading. My advanced wipe did not wipe all and I received a failed message. I'm guessing that is my issue, but I'm not sure what to do about it. Any help would be appreciated.

cagerbrandt said:
I have the same problem. Can you explain what you mean by "a reformat/reinstall and it finally booted"? My Xoom is stuck on the Omni Android screen with the android blinking, but will not finish loading. My advanced wipe did not wipe all and I received a failed message. I'm guessing that is my issue, but I'm not sure what to do about it. Any help would be appreciated.
Click to expand...
Click to collapse
Okay. I found out what to do. Thanks though. Persistence works.

Seriously? Can't anyone explain what they did to fix the problem? You guys are pretty quick to ask for help, but don't even take the time to explain what you did to people who have the same problem.

If there's anyone with the same problem, the solution is to go to the wipe option and instead of using advanced wipe, just use format to delete all internal storage, then reboot and clear dalvik cache, etc. then flash omni, gapps and superSU (in that order), then reboot and wait a few minutes on the omni loading screen and its done.

I am struggling to get past the blinking omni logo, tried all ways to get this to boot, am i missing some thing