[Q]Omni Xoom Wingray boot problem - Omni Q&A

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

Related

[Q] Help - trying to root, now I'm stuck

Sorry if this is a long post...I'm going to try to provide as much information as possible.
I got a brand new nook with version1.3 for my son for Christmas. I'm wanting to root it so I can put some games and stuff on it. I tried following the instructions for the ManualNooter (using ClockworkMod Recovery v3.0.2.8), but think I goofed up by not booting to the nook between the two MN files. When I tried to boot to the nook it just looped on the "nook color" screen.
I went back and tried installing just the first MN fine and booting the nook, but I got the same result.
I then found the two file for reverting to stock I ran both update-nc-stock-1.3-keepcwm and update-nc-stock-1.3 in that order (I'm assuming that there is no boot required in between) and am still stuck on that same nook screen.
I've also done tried to do some stuff like formating the syste, data, and cache, and clearing the Dalvik cache. I've noticed that I'm getting an error formating the data (not sure exactly when this started), and clearing the Dalvik cache causes it to lock up.
I'm not sure where to go at this point, and am concerned that I've hosed up my son's present. I know it's hard to brick a nook, but those issues with formatting data and clearing the Dalvik cache have me worried. Can anyone help me in getting this thing up and running (then hopefully rooted)?
quick question.....do you have the bootable sd card with cwm on it? can you boot to the cwm menu (i'm assuming you can since you said you formatted system, data and cache). what happens when you try to install cm7?
I'm going to show my ignorance here and say I'm not sure. I don't THINK so, since all I intended to do was root, I just followed the instructions to give me the recovery card. Unless maybe it's on there and I'm not don't realize it.
All that said, I think I'm back off the ledge now. I found this linked from another board: http://nookdevs.com/NookColor/RestoreToStock, and the 8 fialed boots method got me back to stock, so I think I'm okay (as long as I can get it rooted).

[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] 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] com.android.phone Crahes (VZW G2 - CM11 03/08 Snapshot)

Hi All,
I'm having an issue with my G2. I've been running the CM11 nightlies for a while now, they've been pretty decent.
I decided to flash the newest Snapshot today when I saw it pop up on my update list. As soon as I booted, I got the error "Unfortunately, the process com.android.phone has stopped".
This happened yesterday, so I booted into recovery, cleared cash, reinstalled the rom, cleared cache again, reinstalled gapps, cleared cache again, and it worked. Now I'm not getting so lucky. Anyone have any ideas on how to fix this? I'm really hoping this isn't going to be an issue with every CM nightly moving forward.
The best solution I could find seems to be specific to HTC phones, which involves reinstalling the boot.img. I don't think that applies to us, but if it does, how can I do that.
Thanks for your help.
EtherBoo said:
Hi All,
I'm having an issue with my G2. I've been running the CM11 nightlies for a while now, they've been pretty decent.
I decided to flash the newest Snapshot today when I saw it pop up on my update list. As soon as I booted, I got the error "Unfortunately, the process com.android.phone has stopped".
This happened yesterday, so I booted into recovery, cleared cash, reinstalled the rom, cleared cache again, reinstalled gapps, cleared cache again, and it worked. Now I'm not getting so lucky. Anyone have any ideas on how to fix this? I'm really hoping this isn't going to be an issue with every CM nightly moving forward.
The best solution I could find seems to be specific to HTC phones, which involves reinstalling the boot.img. I don't think that applies to us, but if it does, how can I do that.
Thanks for your help.
Click to expand...
Click to collapse
You've done a clean flash? Meaning you wiped Dalvik, Cache, System, Factory reset? I usually erase twice and then install CM and then GAPPS then restart the phone (Don't install custom kernel) some custom kernels are having trouble because looks like they updates some things in their kernels.
xxxrichievxxx said:
You've done a clean flash? Meaning you wiped Dalvik, Cache, System, Factory reset? I usually erase twice and then install CM and then GAPPS then restart the phone (Don't install custom kernel) some custom kernels are having trouble because looks like they updates some things in their kernels.
Click to expand...
Click to collapse
Thank you.
After some more digging, I had the idea to check the development thread of the CM ROM here. Apparently, a few other users have had the same issue.
It turns out, the newest version of CM needs to be cleanly installed, a dirty flash won't work. I just did a wipe and it's now downloading all my apps and reinstalling.
*sigh* such a pain, but whatever. Could be worse.
EtherBoo said:
Thank you.
After some more digging, I had the idea to check the development thread of the CM ROM here. Apparently, a few other users have had the same issue.
It turns out, the newest version of CM needs to be cleanly installed, a dirty flash won't work. I just did a wipe and it's now downloading all my apps and reinstalling.
*sigh* such a pain, but whatever. Could be worse.
Click to expand...
Click to collapse
Yeah it can be such a pain, I flashed nightlies when they sounded like they fixed an important issue (it'd be every other day) and I flashed clean all the time. Now im just going to stick to CM11 M4 until the next milestone.
try changin network type to GLOBAL.

Moto X Pure (Style) Bootlooping LOS 14.1

Hello
I have been searching for a while about this and I've decided to make my own thread to help me and others.
My Moto X Pure (Style) has been having trouble booting into Lineage OS 14.1. The Problem started when I flashed it to the phone, I got an TWRP Error 7, so I opened the ZIP file and deleted two lines of code to stop Error code 7 from returning, surprisingly enough, it worked.
I recompressed it back to ZIP then, did an Advanced Wipe. I wiped Dalvik/ART Cache, Data, System, Cache.
Then, I reflashed the ROM. When it finished, I wiped the cache then rebooted to the newly flashed OS.
It was just sitting there, unresponsive, and the phone was progressively starting to heat up to a abnormal temperature while vibrating slightly. So I had to turn it off to cool the phone down before I make another desperate attempt to re-flash the OS.
I retried so many times until I found XDA Dev, I found it interesting and I've thought you've guys might help me along with the great community.
Please XDA Community, I'm in desperate need of your help.
--Victor F. 3/29/18 11:04 PM
I have this problem also. Was able to get up and running with this:
Flash this TWRP: https://forum.xda-developers.com/sho...&postcount=917
Flash this LineageOS: https://forum.xda-developers.com/sho...postcount=1054
Device booted fine after flashing these older builds. Only problem now is my device does not see any future Lineage updates.
Victor F. said:
Hello
I have been searching for a while about this and I've decided to make my own thread to help me and others.
My Moto X Pure (Style) has been having trouble booting into Lineage OS 14.1. The Problem started when I flashed it to the phone, I got an TWRP Error 7, so I opened the ZIP file and deleted two lines of code to stop Error code 7 from returning, surprisingly enough, it worked.
I recompressed it back to ZIP then, did an Advanced Wipe. I wiped Dalvik/ART Cache, Data, System, Cache.
Then, I reflashed the ROM. When it finished, I wiped the cache then rebooted to the newly flashed OS.
It was just sitting there, unresponsive, and the phone was progressively starting to heat up to a abnormal temperature while vibrating slightly. So I had to turn it off to cool the phone down before I make another desperate attempt to re-flash the OS.
I retried so many times until I found XDA Dev, I found it interesting and I've thought you've guys might help me along with the great community.
Please XDA Community, I'm in desperate need of your help.
--Victor F. 3/29/18 11:04 PM
Click to expand...
Click to collapse
Victor F. said:
Hello
I have been searching for a while about this and I've decided to make my own thread to help me and others.
My Moto X Pure (Style) has been having trouble booting into Lineage OS 14.1. The Problem started when I flashed it to the phone, I got an TWRP Error 7, so I opened the ZIP file and deleted two lines of code to stop Error code 7 from returning, surprisingly enough, it worked.
I recompressed it back to ZIP then, did an Advanced Wipe. I wiped Dalvik/ART Cache, Data, System, Cache.
Then, I reflashed the ROM. When it finished, I wiped the cache then rebooted to the newly flashed OS.
It was just sitting there, unresponsive, and the phone was progressively starting to heat up to a abnormal temperature while vibrating slightly. So I had to turn it off to cool the phone down before I make another desperate attempt to re-flash the OS.
I retried so many times until I found XDA Dev, I found it interesting and I've thought you've guys might help me along with the great community.
Please XDA Community, I'm in desperate need of your help.
--Victor F. 3/29/18 11:04 PM
Click to expand...
Click to collapse
How did you edit the file to make it flashable?
frakkingcylon said:
I have this problem also. Was able to get up and running with this:
Flash this TWRP: https://forum.xda-developers.com/sho...&postcount=917
Flash this LineageOS: https://forum.xda-developers.com/sho...postcount=1054
Device booted fine after flashing these older builds. Only problem now is my device does not see any future Lineage updates.
Click to expand...
Click to collapse
I have the same problem and sove whits this older builds, but some one know how update the LOS after this flash?
Lol, it works now
It works now, i just decided to wait
its all good now!
Victor F. said:
It works now, i just decided to wait
its all good now!
Click to expand...
Click to collapse
Sorry, but wait what?

Categories

Resources