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 Memory loss 32GB version

I recently purchased a Google Nexus 7 32GB version and it worked amazingly well until I started losing data. I first noticed when I went to play a game and it wouldn't launch, I later found out that ES file manager wouldn't launch as well. Then I came to a conclusion, NONE OF MY APPs were working. I thought It was okay, I had a stock recovery I had made from a earlier time so no big deal. I flashed it and I had the same issue, I had missing data, usually at the /home directory. I thought maybe it was a jelly bean bug or something so I decided to flash cyanogenmod and it wont even launch it's stuck at the boot splash screen.
Ubuntu appears to be working fine and I've tried both clockworksmod recovery and TWRP. I even went as far as manually flashing the stock 4.2.1 factory recovery.
I really don't understand how Ubuntu works fine, but Android just refused to work for me. I'm not sure what caused it has anyone else run into this issue?

I had a somewhat similar problem once. Then, I flashed the stock rom with the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=1776860
It is post #10. Our issues were a bit different, but since both are memory allocation issues, maybe it will help you. Good luck!
Sent from my Nexus 7 using xda premium

we have the same problem. i lose all my files. what to do now? i was copying files from my laptop to n7. then when i checked the n7 other files were gone. i tried to wipe cache but nothing happens. can i still recover the files? the apps are still there when i try to launch them some apps are installing. im using pa stock kernel. please help

[Q] Stock Nexus became extremely slow after kitkat

I am all stock on my nexus 7 wifi, updated to kitkat using OTA. But the tablet has become laggy and unresponsive. SD card read write has slowed down, There used to be more apps loaded in memory while on 4.3 but only a few are there now. I wanted to know what are my options other than rooting and installing custom rom??
Sent from my Nexus 7 2012 wifi

I had the exact opposite from my N7 wifi. It had become barely usable before the update. Apps taking forever to load, apps hanging or crashing, real laggy. It's stock, just rooted.
The OTA update made a huge difference for the better. That's what I've been hearing from others too.
It can be a PITA but I would make note of the apps you want and get your saved stuff off (pics and docs etc) and wipe it with the factory kitkat image from Google.
You shouldn't be experiencing what you are.
Sent from my SCH-I535 using xda app-developers app

Reflash or just factory reset??
Sent from my Nexus 7

I have the same problem. KitKat has has made my nexus 7 so slow. When I looked on the net some people say a factory reset sorted this out but some say there was no change. Think its so bad Google put this update out without testing it properly. As there seems to be lots and lots of people with this problem.

like skrusrnmz said, i m beginning to think incremental updates break something about apps and system slows down. flashing fresh stock from scratch might solve it...lets see.

XperiaMT27 said:
like skrusrnmz said, i m beginning to think incremental updates break something about apps and system slows down. flashing fresh stock from scratch might solve it...lets see.
Click to expand...
Click to collapse
+1 Before the KitKat 4.4 OTA, the N7 2012 WiFi was already running on a series of patches and updated Apps via Play Store, getting sluggish & running low on space. For anyone that's on XDA, you know how easy it is to unlock the bootloader & get root after flashing custom recovery via ADB (try not to use toolkits - as a last resort or for the lazy ones, LOL)
If you have custom recovery already (and, I recommend & recommend TWRP over my long favorite - CWM) just reset, wipe cache & dalvik and use one of the flashable zip - after doing the proper TB backup & TWRP backup to a secured storage media. Push recovery again if necessary, along with Busy Box & SU v1.75) - reboot & setup the basics - then restore TB (w/o data to avoid errors) and let it stabilize with any newer update, finalize tuned settings. End result - a smooth rooted stock rom & kernel on 4.4 which is what I'm running for the last 2 weeks ... until developers can do their magics on both odexed & deodexed roms with their tweaks.
If you aren't happy with the results, you can always restore your saved images from custom recovery & go back to 4.3.1 or what now - but, IMO, you will appreciate & learn to like KitKat.

My 2012 Nexus 7 was slow before the KitKat update. Afterwards it was dog slow. So I did a factory reset. It's now back to being buttery smooth.
Sent from my Nexus 7 using Tapatalk 4

Yeah I think it's an issue with updating and not wiping. I just flashed the image myself and yeah it's smoother
Sent from my Nexus 4 using Tapatalk

i think it may be you have too many file on your device. try to delete some file. it should go faster

I had the same problem when upgraded from 4.2.2 to 4.3 and never resolved with stock firmwares.
Try a factory reset, but it's not guaranteed that it will work.

I have factory reset my device before installing fresh stock, its better than before. will test a few days, otherwise fresh installation.

Nexus 10 Random Reboots

'My Nexus 10 started to randomly reboot several times a day after the Kitkat update and because it is outside the warranty period I cannot get it replaced.'
It reboots no matter what is running and sometimes it reboots immediately after a power up but never enters a reboot loop.
I've tried a factory reset and running it in safe mode but that didn't stop it.
I've not been able to replicate the reboot fault until yesterday when I ran the BBC iplayer and downloaded a 1-hour Horozon video of about 650Mb and when I tried to play it I got a reboot and that happened consistantly.
I tried a complete power down and reboot then tried to play the downloaded video but it always rebooted.
I tried deleting and re-saving the video incase it was corrupt but it still rebooted.
I tried deleting the video and streaming it and I could watch it that way without any reboot.
I've tried downloading three 1-hour Horizon videos of about the same size and only one plays without rebooting.
A check of running apps shows just the keyboard and a couple of system apps but I still get the reboot when I try to play the saved video.
I thought about removing apps one at a time to see if that would solve it but I've basically got the same apps I had before the Kitkat update.
I wondered if I could undo the Kitkat update and flash the previous rom to see if that would solve it for Kitkat was not a big improvement.
I've never used a custom rom and not run anyting other than stock software.
I would be most grateful for any suggestions on how to fix this rebooting problem and whether going to an earlier version of Android is feasable and how would I do it.
PS. There is a BBC iplayer option to download videos using less resolution and when I choose that option the Horizon file size falls to 344Mb which is about half the size of the original and it solves the reboot problem when playing the saved video.
So it would seem that the BBC iplayer reboot problem is related to file size.

It's fairly easy to downgrade, just Google "nexus factory images" and you should find all the old versions of android straight from Google. There should be guides online for how to flash a factory image. Just make sure to back up all your files to your computer as it will wipe everything.
Sent from my SGH-I747M using xda app-developers app

gc84245 said:
It's fairly easy to downgrade, just Google "nexus factory images" and you should find all the old versions of android straight from Google. There should be guides online for how to flash a factory image. Just make sure to back up all your files to your computer as it will wipe everything.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Thanks for your help.
I've found the factory images and I'm now looking for a simple detailed guide how to do the downgrade.
My Nexus 10 is on 4.4.2 (KOT49H) and I think I'll try downgrading one level to 4.4 (KRT16S) to see if that solves the reboots problem and if not then I'll try downgrading further to 4.3 (JWR66Y).

Gaugerer said:
Thanks for your help.
I've found the factory images and I'm now looking for a simple detailed guide how to do the downgrade.
My Nexus 10 is on 4.4.2 (KOT49H) and I think I'll try downgrading one level to 4.4 (KRT16S) to see if that solves the reboots problem and if not then I'll try downgrading further to 4.3 (JWR66Y).
Click to expand...
Click to collapse
Here is a good guide (sorry, I would have posted it earlier but I didn't have my computer with me at the time and was posting from my phone):
http://forum.xda-developers.com/showthread.php?t=1907796

gc84245 said:
Here is a good guide (sorry, I would have posted it earlier but I didn't have my computer with me at the time and was posting from my phone):
http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
Thanks for the guide link.
Unfortunately, my laptop is running Windows 8.1 and it is difficult to install the USB driver and Android Development Kit needed to flash previous Android versions, so I've given up until I can find the way to do it.
PS. I've found a way of installing the ADB and Fastboot drivers on my Windows 8.1 laptop and here is a link:
http://forum.xda-developers.com/showthread.php?t=2588979
So I'm back on track to solve my random reboots using an earlier version of Android.

I noticed the iPlayer hard crash thing too. I can play downloads, but as soon as I pause it and attempt to restart, or just slide the progress bar to move to a different part of the video, the tablet hangs then reboots. It's completely reproducible, and doesn't happen on any of my other devices.
Apart from that, my n10 has now gone 20 days since the last random reboot, so it's a lot more stable in general than it used to be!

I've found a easy way to downgrade to 4.3 and would be grateful for any opinion on how safe it is and if anyone has tried it.
http://forum.cyanogenmod.com/topic/83985-nexus-factory-images-to-revert-to-stock/

AleT said:
Apart from that, my n10 has now gone 20 days since the last random reboot, so it's a lot more stable in general than it used to be!
Click to expand...
Click to collapse
Arghh...this thing is a POS. I haven't used it in 2 months. Today I fired up chrome for some browsing. It hard locked within 5 minutes. I left it for an hour plus with the screen on and still locked up. Just frustrated. Worst Android device I've owned.
Sent from my XT1053 using Tapatalk

Either you have a faulty app or your tablets have a hardware defect. The random reboot issue, where the GPU driver would leak memory and force a kernel panic, has been fixed since Android 4.3 in July. This includes the Chrome reboot issue. I've had 2 reboots over 13 months, and both were cause by a ROM issue. I assure you, there is nothing wrong with the Nexus 10. Try a 4.4.2 factory image and see if that solves anything.

Koopa777 said:
Either you have a faulty app or your tablets have a hardware defect. The random reboot issue, where the GPU driver would leak memory and force a kernel panic, has been fixed since Android 4.3 in July. This includes the Chrome reboot issue. I've had 2 reboots over 13 months, and both were cause by a ROM issue. I assure you, there is nothing wrong with the Nexus 10. Try a 4.4.2 factory image and see if that solves anything.
Click to expand...
Click to collapse
I still get random re-boots in `safe mode` which is supposed to only allow apps installed with the system to run which leaves a bad 4.4.2 which could be checked by a re-flash of the factory image or faulty hardware.
I was planning to downgrade to 4.3 to see if that solved the re-boots but I might try a re-flash of 4.4.2 first to see if that works..
I'm not very confident about flashing and I've had the additional problem of working on windows 8.1 on my laptop.

I am running the factory image, 2nd one with same issues. I'm not necessarily disputing what you are saying but there were plenty of people telling me they had a perfect tablet when the memory leak wasn't fixed.
Sent from my XT1053 using Tapatalk

rxnelson said:
I am running the factory image, 2nd one with same issues. I'm not necessarily disputing what you are saying but there were plenty of people telling me they had a perfect tablet when the memory leak wasn't fixed.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
The memory leak was fixed but apparently, it's reappeared for me with the latest kitkat update. Quite frustrating, you'd think Google would be on top of these things. What's the point of fast updates if you're waiting months on end for a fix. If I don't powerdown my tablet when I'm finished using it I can guarantee a reboot during use. In the last 24hrs, it has rebooted on me twice while using Chrome. Quite irritating to be honest

It seems from previous posts that re-flashing 4.4.2 does not solve the reboots and I've not found a way to downgrade to 4.3 on Windows 8.1 to see if that works.
So I've tried another factory reset, but this time I've not allowed any non-Google apps to be installed other than the Photon browser which I need for flash Websites and the Re-boot logger app to record any reboots.
I'm using my Note 3 for the rest of my apps as that is still on 4.3 and doesn't have the reboot problem, but that might change after the KitKat upgrade.
I was getting at least 2 or 3 reboots a day so I should soon know if running 4.4.2 after a factory reset with just two 3rd party apps solves the problem and if so then that will suggest a rougue app. which I can reveal by re-installing the apps piecemeal.

I've just had another random reboot so I've done another factory reset but not signed in to Google so there have been no downloads and the only program I've run is Settings to increase the screen timeout to 30 - minutes.
If I still get random reboots then it is nothing to do with 3rd party apps or updates for I've not downloaded any.
That just leaves the hardware or the original 4.4.2 assuming the factory reset returns to that.

I didn't experience any reboots when not signed into google after a factory reset so I signed in and restored my tablet using Google backup.
I soon started to get reboots again, but I noticed that since the KitKat upgrade a website I use very often was sometimes automatically loading the Play store to try and get me to use their much inferier app. It doesn't happen on my Note 3 which is still on 4.3.
If I tried to close the Play store app to get back to the browser by swiping it away then it crashes and keeps trying to load over and over. If I hit the home button the Play store automatically re-appears still loading over and over, but after swiping it away several times it goes away or stops with an error message asking me to report the crash which I did and the browser is closed.
In order to fix this I disabled the Play store app so that it did not appear in my list of apps.and the website instead of loading the Play store app re-directed the browser to the Play store website which was better for I was still in the browser.
Since I stopped this particular website loading the Play store by removing it, I've just had one re-boot instead of several and my tablet is no longer overheating. I am a heavy user and have my tablet on many hours a day, so one re-boot is acceptable to me.
I've downloaded a Play store apk which I can install if needed but always remove it before using the website which tries to automatically load it.
It is a nuisance and I wish I'd stayed with 4.3, but I can live with the occaisional re-boot that might not be noticed if I only used my tablet lightly.
I'm annoyed that a website can automatically load the Playstore without me requesting it and that KitKat allows it.
I hope my experience helps others who are getting several re-boots a day.
PS
I did a factory reset then removed the Play store app before using the problem website so that it never loaded it in case that was needed.

Flashing the 4.3 factory image downgrades everything. For what it's worth, I noticed that the userdata partition is constructed differently than in 4.2.2(my last factory flash). That could have something to do with it. But also, I've been on custom ROMs since I got the tablet, yet I've never rebooted on 4.4.X. I guess try a vanillish ROM(like RastaKat) to see if that reboots.

Koopa777 said:
Flashing the 4.3 factory image downgrades everything. For what it's worth, I noticed that the userdata partition is constructed differently than in 4.2.2(my last factory flash). That could have something to do with it. But also, I've been on custom ROMs since I got the tablet, yet I've never rebooted on 4.4.X. I guess try a vanillish ROM(like RastaKat) to see if that reboots.
Click to expand...
Click to collapse
Now that I'm just getting one reboot a day and my tablet is running cooler I can live with that and I don't mind re-installing the Play store when needed for continuous updates can be a nuisance.

I finally managed to downgrade to 4.3 and I'm hoping that will solve all the problems I had with 4.4.2
But all seems well at the moment.
I'm not being booted from websites to the Play store, I can use the BBC iPlayer to download and run 1-hour videos and flash player works better.
Google has downloaded 4.4.2 (KitKat) but I'm not going to install it.

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.