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

Need help with CWM boot issue

Hey guys. I'm trying to figure out what's going wrong with my Transformer. I'm not experienced with Android development/ROM's so please bare with me.
Rooted my first Android device about a month ago. Made a stupid mistake placing the ROM I was planning to use on the external SD card & didn't backup the install I wiped. Recovered with an official Asus ROM & after about two hours fiddling around I managed to root & load my first ROM (Revolver, whoot!). Very pleased with myself!
Have been using the Revolver ROM for a month without any problems. No deep sleep etc, everything worked perfectly. Using the latest version of Clockworkmod, also no issues so far. Strange thing is that since last monday everytime I (re)boot the device it loads CWM instead of the Android OS. I can get back into Android bij holding volume down during boot & choose to cold boot. Not a big issue but very annoying & can't seem to find the fix.
Searched Google & XDA for a solution. Updated Revolver to 1.3.1 beta, also found the repack by Koush for CWM. Tried fixing permissions, clearing cache, clearing dalvik, wiping & starting over, etc. Everything I tried so far does not fix the CWM-loop I seem to be stuck in.
Would really appreciate some help, I'm probably looking in the wrong direction here. Thanks in advance.

Found something
Finally got out of the CWM loop, found a solution here: http://forum.xda-developers.com/showthread.php?t=1622814&page=2
Strange thing is that after I flashed it with the fix CWM changed to the touch mod I recently installed but never seemed to work. If I understand correctly the fix only deleted the first few lines in the config where the boot in recovery flag should be.
Afterwards I factory wiped the unit & flashed it with a clean ROM. Currently re-installing my apps. I do not have a good feeling on this, tablet seems sluggish last couple of days & I can hear a soft click when the unit reboots. Same sort of click a laptop hdd would make.
Think it's dying on me...

can't update past LineageOS 14.1 20171013

Thanks to XDA, I've been running LineageOS 14.1 on my LEX727 for months now, updating to most nightly releases with no issues. However, when the phone rebooted after updating to the 10/20/17 nightly, it got stuck on the boot animation screen (green circle moving right to left on the arc) and would go no further. I rebooted into TWRP and flashed back to 10/13 which has been working fine. Same results after attempted updates to the 10/27 and 11/3 releases. I even tried a manual update from TWRP using USB OTG with the same result.
Any ideas of what's gone wrong here? Anything I can try? All I know to do at this point is wipe and install clean but I'd rather not if possible. Thanks!

fraxby79 said:
Thanks to XDA, I've been running LineageOS 14.1 on my LEX727 for months now, updating to most nightly releases with no issues. However, when the phone rebooted after updating to the 10/20/17 nightly, it got stuck on the boot animation screen (green circle moving right to left on the arc) and would go no further. I rebooted into TWRP and flashed back to 10/13 which has been working fine. Same results after attempted updates to the 10/27 and 11/3 releases. I even tried a manual update from TWRP using USB OTG with the same result.
Any ideas of what's gone wrong here? Anything I can try? All I know to do at this point is wipe and install clean but I'd rather not if possible. Thanks!
Click to expand...
Click to collapse
I'd say do a clean install. If i have any issues with a rom booting i'll factory reset and install again. If i still have issues i'll just use another rom.

fraxby79 said:
Thanks to XDA, I've been running LineageOS 14.1 on my LEX727 for months now, updating to most nightly releases with no issues. However, when the phone rebooted after updating to the 10/20/17 nightly, it got stuck on the boot animation screen (green circle moving right to left on the arc) and would go no further. I rebooted into TWRP and flashed back to 10/13 which has been working fine. Same results after attempted updates to the 10/27 and 11/3 releases. I even tried a manual update from TWRP using USB OTG with the same result.
Any ideas of what's gone wrong here? Anything I can try? All I know to do at this point is wipe and install clean but I'd rather not if possible. Thanks!
Click to expand...
Click to collapse
I am in the same situation. Have tried all combinations of wiping and resetting with all 3 of the latest nightlies and still cannot boot. I can successfully boot into a stock rom but, I'd rather not. I guess I will go back to the 10/13 nightly since it worked (mostly) before this debacle. Hopefully next week's update will solve this problem.

Thanks for your reply, islandlife98. I'm not super-confident at this ROM thing yet so backing up, wiping and reinstalling is something I'd undertake reluctantly. I was hoping this was a common situation with a simple fix that I just had been unable to find. Always prefer to actually solve a problem if possible rather than just wipe it out. (Although when it comes to tech, wiping it out is often the best or only solution. Almost always the quickest.)
JBealZy, thank you for letting me know you're in the same boat! After seeing no mention of this issue here, I assumed it was some weird glitch with my phone rather than a problem with the updates. If you've done a full wipe and re-install but still haven't been able to boot into any of the last three releases then I'm glad I hesitated. (That was a concern I'd had: that it might not work even after a clean install.) Think I'll stick with 10/13 for now and keep trying the new releases; easy enough to roll back if it fails now that I've figured it out.

Lmao same problem here with the 2017-11-11 and 2017-11-03 udpate. Not tested yet with 2017-10-27 or 2017-10-20 but that's my last choice because after 2017-10-13 update all links are removed. I do a clean install every time .. What other rom is better ?
Problem resolved .. i have wiped internal storage too and able to install the last version. I think i'm gonna use another ROM because i don't really want to reinstall all of my applications everytime i do an update. :/

Deediezi said:
Lmao same problem here with the 2017-11-11 and 2017-11-03 udpate. Not tested yet with 2017-10-27 or 2017-10-20 but that's my last choice because after 2017-10-13 update all links are removed. I do a clean install every time .. What other rom is better ?
Problem resolved .. i have wiped internal storage too and able to install the last version. I think i'm gonna use another ROM because i don't really want to reinstall all of my applications everytime i do an update. :/
Click to expand...
Click to collapse
I am using Paranoid ( latest version) and everything works flawlessly.
Sent from my LEX727 using XDA Labs

Deediezi said:
Lmao same problem here with the 2017-11-11 and 2017-11-03 udpate. Not tested yet with 2017-10-27 or 2017-10-20 but that's my last choice because after 2017-10-13 update all links are removed. I do a clean install every time .. What other rom is better ?
Problem resolved .. i have wiped internal storage too and able to install the last version. I think i'm gonna use another ROM because i don't really want to reinstall all of my applications everytime i do an update. :/
Click to expand...
Click to collapse
Another victim! So weird, I wonder what's going on there. None of the updates since my original post have worked so I've come to the conclusion that I'm going to have to do a clean install. Just need to find a time do it. Good to hear it worked for you.
LineageOS is the only ROM I've tried but since I have to wipe my phone anyway I may try some others. Paranoid Android looks interesting and Tsongming says it's working well.

fraxby79 said:
Another victim! So weird, I wonder what's going on there. None of the updates since my original post have worked so I've come to the conclusion that I'm going to have to do a clean install. Just need to find a time do it. Good to hear it worked for you.
LineageOS is the only ROM I've tried but since I have to wipe my phone anyway I may try some others. Paranoid Android looks interesting and Tsongming says it's working well.
Click to expand...
Click to collapse
Yea i'm downloading Paranoïd right now for testing it .. Don't want a broken operating system on my phone haha

If anyone's still interested, I first tried flashing Lineage after wiping all but internal storage and still couldn't get past the boot animation. Then did a full factory-reset wipe including the internal storage, re-flashed, and it finally booted. The first OTA update since then came through today and went off without a hitch so all seems well for now.
I did take a look at Paranoid before going back to Lineage. One big reason I use a custom ROM is to get security updates quickly and LOS reports the security patch level in the settings; I couldn't find this info in PA. Also, I use a pattern to unlock my phone and there didn't appear to be a way use a larger grid than the default 3x3. On the plus side (sort of), PA includes the LeEco remote control app, which seems to be the only way to use the IR hardware on this phone, but it asks for more permissions than I want to give (which, of course, is not PA's fault). So admittedly I didn't really give it a full and fair trial but those few little issues sent me back to the (usually) reliable familiarity of LOS.

I received a new LEX722 yesterday. The TWRP for zl1 is working fine, but I cannot get lineagos working.
I deleted:
- dalvik,
- system,
- cache
- data
- and also the internal storage
after rebooting into twrp I enabled usb debugguung and pushed the lineageos and gapps images via adb push to the phone.
I installed lineageos and gapps nano, but after booting to system, I get stuck in a black screen looping to a dark grey luminated display (no graphics at all).

Heistergand said:
I received a new LEX722 yesterday. The TWRP for zl1 is working fine, but I cannot get lineagos working.
I deleted:
- dalvik,
- system,
- cache
- data
- and also the internal storage
after rebooting into twrp I enabled usb debugguung and pushed the lineageos and gapps images via adb push to the phone.
I installed lineageos and gapps nano, but after booting to system, I get stuck in a black screen looping to a dark grey luminated display (no graphics at all).
Click to expand...
Click to collapse
Sorry, can't help you with that since I have a LEX727 which is apparently quite different from the LEX722. Official LineageOS is only supported on the LEX720 and LEX727: [ https://wiki.lineageos.org/devices/zl1 ]. The LEX722 (Elite) has it's own section here on the LeEco Pro 3 forum so check that out and see what they've come up with.

Weird bootloop

Have had my OnePlus 2 since 2015, and it's been a solid performer up to today.
I had the crDroid ROM (8.1) installed, along with Magisk, and it's been working fine for over a month with zero issues.
Today, I went to remove an app that was being troublesome, and then rebooted. And it just bootlooped. Animation is playing, but that's it. It sits there for 10-15 mins doing nothing. I hold the Power button to shut it down, and then try booting again. Same thing, just a straight bootloop for 15 mins. So I reboot to recovery (TWRP 3.2.1.0) and flash the Magisk uninstaller, to see if restoring the stock boot partition would help. It didn't, and just gave the same bootloop. So I go back into TWRP, wipe /system /cache and /dalvik and reinstall the ROM and gapps. Reboot. Same bootloop.
Now I'm starting to get a little concerned. Right now I'm restoring a backup from 10 days ago that I made before I last updated the ROM, but assuming this fails, does anyone have any good ideas? I'm not an expert, but I'm not a novice either, and this isn't making much sense. Unless my OnePlus 2 is getting ready to check out, which would suck...

idk if you had any mods like kernel or whatever or what app you removed (and if it had root acces) but first make sure you are on latest twrp, then try to clean flash a rom like normal. try to boot it it should work.

Thanks for the reply. No mods, other than Magisk. Just a stock 8.1 ROM with Magisk on top. Wiping /system, /cache and reflashing the ROM did not work. In the end, restoring a backup from a week ago was the only thing that worked. I have no idea why or what happened, but I guess it's yet another reason to keep a good backup on your phone in case of situations like this.

Gaffadin said:
Thanks for the reply. No mods, other than Magisk. Just a stock 8.1 ROM with Magisk on top. Wiping /system, /cache and reflashing the ROM did not work. In the end, restoring a backup from a week ago was the only thing that worked. I have no idea why or what happened, but I guess it's yet another reason to keep a good backup on your phone in case of situations like this.
Click to expand...
Click to collapse
This means that a date/time overflow occurred in your system
You restored a backup from 10 days ago, I'm assuming an older version of the ROM? So the newer version has an overflow bug
Even if nothing changes on the system your system time is always changing and if the ROM or kernel is somehow messed up then this value can cause an overflow and if a security module of some sort (like fortify_source or stack_buffer_protection) finds out about the overflow it can prevent boot from happening
Note: below example not completely valid in the real world, I've removed some stuff and is just for clear understanding.
Let's elaborate, "signed int" accepts values from -32768 to +32768 (0 inclusive)
What do you think happens when a value below -32768 is passed? That's an underflow and it's not defined what would happen below that limit (actually stuff does happen but see below notice)
If you pass a value over 32768 you cause an overflow
Note: I'm not going to go into details about what exactly happens. This would add too much information and cause more confusion than it would clear
What does this have to do with the date? Well every second your system date increases and if you got one of these limits you're going to run into problems
This is the only possible explanation for what could have happened

Thanks for the explanation. i think I understood most of it.
The backup from 10 days ago was from an older version of the ROM, though I have since installed the latest ROM version on top of the restored backup without issue, as I did when I first made the backup.

DooGee X5 Max Pro best clean Custom Rom<Solved>

Updated!
Having tried many of the Custom roms around for the above phone some of which still had malware installed or were buggy I finally tried Lineage 14.1 based,"Mokee".
https://www.getdroidtips.com/mokee-os-doogee-x5-max-pro/
The flashing it took quite a long time to boot e.g around 15 mins plus but once installed acts as normal.
I can only speak for the 32 bit version as that is what my phone is.
All my fave apps are working.Battery life as normal if not better.No crashes.
Zip was checked with Avast anti-virus before moving to phone and then with Eset and Sophos Anti-virus/Anti-Malware once installed and found clean.
I've also monitored the rom using No-root Firewall over the week and nothing seems to be,"Calling home" that shouldn't.
Unless something changes this is the best clean Rom I've had on the phone.
HTH

Update:1 month on.
Still running fine.This ROM is a keeper for me

Hey, is the rom still running nicely? I got an "x5 pro" and think about flashing mookee but im still afraid:cyclops:

Double post glitch

mia.backkind said:
Hey, is the rom still running nicely? I got an "x5 pro" and think about flashing mookee but im still afraid:cyclops:
Click to expand...
Click to collapse
Yes.Totally rock solid and no problems to date
On the old original Malware infested Stock rom there must have been some kind of hidden timer as it was well behaved for around a year and the just after a year loads of ads started coming up even after Factory restores.
I tried loads of Malware/Anti-virus apps and it was only ESET security that found some hidden Trojans
https://play.google.com/store/apps/details?id=com.eset.ems2.gp&hl=en_GB
See this thread and my tip at the end to get the rom/s to flash,
https://forum.xda-developers.com/doogee-x5/how-to/doogee-x5-max-pro-root-recovery-ota-t3501830/page4

Puts me into a boot loop. Did you follow instructions to the letter? Because instructions include wiping system before flashing mokee (but wiping system removes the chinese recovery (power + volume(-)). After I restored nandroid backup, was still in a boot loop. Had to reflash stock firmware
Had to "cook" my own twrp recovery (none of the ones i found around worked) so maybe I will have to do the same with mokee, like merge it with stock rom to make it work?

I can't remember if I wiped it first
I think I just did a Factory Reset on the rom that was in before flashing with Mokee.
I had no trouble with the files from,
https://www.getdroidtips.com/mokee-os-doogee-x5-max-pro/
When you say Boot Loop do you mean you see the Mokee icon for a long time and it seems like it's doing nothing?
Also mine is the 32 bit version,not the 64 bit.
Also what I had to do at the end of this post,
https://forum.xda-developers.com/doogee-x5/how-to/doogee-x5-max-pro-root-recovery-ota-t3501830/page4

Boot loop like seeing the silver doogee logo. Then shuts down and restarts.
I got mine from the same place. Mine is 32 bit as well
There are 2 factory resets. The advanced reset, that the instructions mention, includes system wipe.

K3rb3r05 said:
Boot loop like seeing the silver doogee logo. Then shuts down and restarts.
I got mine from the same place. Mine is 32 bit as well
There are 2 factory resets. The advanced reset, that the instructions mention, includes system wipe.
Click to expand...
Click to collapse
I'd just try it the other way round from what you have tried.Without being there it's hard to get an idea.As I said it's been a few months now so I can't remember the exact sequence
Also it did take a long long time to first boot.Also try a Factory reset after the rom has flashed..