So i wanted to get an idea of what more refined marshmallow builds will start looking like in the near future and decided to flash Resurrection Rmx 6.0 Flashed it and also flashed banks 6.0 gapps. Boots up thru "optimizing apps" dialogue then says "starting apps" but hangs there for eternity. So i go back re wipe and reflash RM 6.0 and this time tried the other recommended gapps slim zero and same process and same result. So i tried Xenon HD with both gapps packages and same result. Clearly it's a problem with my phone because others have no problems. I can boot Lollipop roms just fine. Could it be a partition issue? I'm on zv4/6 rpm and tz versions and ZVC modem. Any ideas?
I've been using this build of CM13 the last few days, its the first one that I got to boot past what you described.
https://ci.galliumos.org/job/cm13/device=ls990,jdk=OpenJDK7,label=android
using opengapps stock zip
Errors on boot.
So I tried clean flashing barebum v1 & v2 , illusion ROM and resurrection and while they do boot and everything I can not use them.
Barebums boots up but can not pass the green activation windows...after the WiFi connect it returns to first page.illusion and resurrection give google play services errors and lg keyboard error and you can't continue .
Related
So I had quite the experience upgrading to lollipop.
Started with:
CM11 4.4.4 Nightly
600mb system
Philz Touch
1) I flashed Flintman TWRP within Philz Touch 6.0.4.9.
2) Downloaded Milaq's CM12 and PA Gapps 5.0.2. Pico.
3) Booted into TWRP, and created a backup.
4) Ran a factory reset in TWRP, and attempted to flash CM12. I had no idea where the /Downloads/ folder was, and I ended up finding it by going to /Internal Storage/data/media/0/Downloads
5) Encountered an error in mounting system, nothing was flashing.
6) Booted the touchpad into Web OS Recovery, and ran TPToolbox. An error was detected in the system partition, and 'Repair Partition' failed.
7) I then booted into WebOS and ran Preware 'Tailor'. Tailor also failed on 'Check Filesystem'. I then proceeded to delete the Android system partition. I never figured out why my system became corrupted.
8) I removed 400 mb from Android Data, and created Android System with 1000mb.
9) I booted back into TWRP, and successfully flashed CM12, and gapps.
10) After booting, I then proceeded to download Xposed for lollipop. I activated root in developer settings,.
11) I booted in to TWRP, and flashed Xposed, and rebooted the tablet.
12) All subsequent apps resulted in a -504 error when installing. It was discovered that Xposed was the culprit.
13) I then reflashed cm12, without xposed.
14) I downloaded Trickster MOD and set my CPU to 1782 Mhz and performance governor.
15) I experienced odd slowdowns and crashes when any audio played (include keyboard taps). I then proceeded to flash Viper4Android. I installed the driver, rebooted, and now my Touchpad audio sounds great! Make sure to select the best audio quality, and play with the Viper settings!
I now have a blazingly fast lollipop tablet. I tried 5.1.1, but I find it too unstable for daily use. The next step is to figure out how to get Xposed working.
Thanks to the devs for the hard work in development!
fwiw, all 4.4.4 and 5.x roms that I have tried excepting the Evervolv 5.0.2 last nightly have problems with the sound locking up the system, unless you turn off "OK Google" detection completely.
EricBlade said:
fwiw, all 4.4.4 and 5.x roms that I have tried excepting the Evervolv 5.0.2 last nightly have problems with the sound locking up the system, unless you turn off "OK Google" detection completely.
Click to expand...
Click to collapse
I had similar issues with the exception of Evervolv. Their 5.1.1 is even pretty solid now at this point; they're setting their sights on Marshmallow next!
rfoster2009 said:
I had similar issues with the exception of Evervolv. Their 5.1.1 is even pretty solid now at this point; they're setting their sights on Marshmallow next!
Click to expand...
Click to collapse
I still gget that lockup in 511.. hoping 6 kills the weird bugs
Sent from my Touchpad using Tapatalk
Interesting yet annoying
BuffMcBigHuge said:
So I had quite the experience upgrading to lollipop.
Started with:
CM11 4.4.4 Nightly
600mb system
Philz Touch
1) I flashed Flintman TWRP within Philz Touch 6.0.4.9.
2) Downloaded Milaq's CM12 and PA Gapps 5.0.2. Pico.
3) Booted into TWRP, and created a backup.
4) Ran a factory reset in TWRP, and attempted to flash CM12. I had no idea where the /Downloads/ folder was, and I ended up finding it by going to /Internal Storage/data/media/0/Downloads
5) Encountered an error in mounting system, nothing was flashing.
6) Booted the touchpad into Web OS Recovery, and ran TPToolbox. An error was detected in the system partition, and 'Repair Partition' failed.
7) I then booted into WebOS and ran Preware 'Tailor'. Tailor also failed on 'Check Filesystem'. I then proceeded to delete the Android system partition. I never figured out why my system became corrupted.
8) I removed 400 mb from Android Data, and created Android System with 1000mb.
9) I booted back into TWRP, and successfully flashed CM12, and gapps.
10) After booting, I then proceeded to download Xposed for lollipop. I activated root in developer settings,.
11) I booted in to TWRP, and flashed Xposed, and rebooted the tablet.
12) All subsequent apps resulted in a -504 error when installing. It was discovered that Xposed was the culprit.
13) I then reflashed cm12, without xposed.
14) I downloaded Trickster MOD and set my CPU to 1782 Mhz and performance governor.
15) I experienced odd slowdowns and crashes when any audio played (include keyboard taps). I then proceeded to flash Viper4Android. I installed the driver, rebooted, and now my Touchpad audio sounds great! Make sure to select the best audio quality, and play with the Viper settings!
I now have a blazingly fast lollipop tablet. I tried 5.1.1, but I find it too unstable for daily use. The next step is to figure out how to get Xposed working.
Thanks to the devs for the hard work in development!
Click to expand...
Click to collapse
I have been hving fun running Milaq 4.4 and i seen this post but Milaq's link and the link to the gapps and Exposed all are well i have no Idea how to download from those sites. IE can't find a link, only more info into what they are. can you check this out? repost if needed , thanks for sharing.. I hope i can get these files downloaded...
Hey guys having trouble here. I recently tried to dualboot a ROM next to fulmics but couldn't really figure it out so I stopped the process. I then tried to flash resurrection remix with open Gapps and it started out all good but then it froze during the installation of apps from Google play. I'd remove the battery to reboot it, it'd boot again and freeze again. I then flashed back to fulmics then tried CRdroid today. Same issue. I had no issues flashing resurrection remix before I tried to dualboot. Fulmics and stock work fine but I'm missing AOSP based ROMs. Also to note I did full wipes both times and was using latest open Gapps. Any help or insight to my issues would be greatly appreciated.
Hi,
I've got a RN3, snapdragon version, 3GB of RAM. Unlocked bootloader. TWRP 3.0.2-2
I've been using CM for a while, android 6.0.1 and I've been trying now for a few days to move to Nougat.
I've tried different roms: NitrogenOS, lineage OS, resurrectionRemix.
I've also tried flashing different versions os miui firmware: 7.3.16, 7.3.23, 7.3.30
So, after all that, the result is always the same. The flashing seems successful, the phone boots but then I cannot go through the initial setup screen.
I choose the wifi network but when I try to enter the password, the screen resets every 5 seconds or so. I know it's resetting/reloading because the password I've typed so far goes away and I have to start again. It happens every few seconds and I cannot setup wifi properly.
I tried changing the password to aaaaaaaaaa to make it easy and quick to setup. Once I go through that, it stays for ever in the next screen "checking information" (or something like that). Again, it seems to be reloading this screen every few seconds.
is there something am I missing? Maybe I'm flashing firmware/rom in the wrong order?
I'm back with android 6.0.1 now and the phone works fine.
thanks in advance for your help.
Flash Kenzo Firmware , Rom & Nougat Gapps not MM , next reboot system
Sent from my Redmi Note 3 using Tapatalk
VaibhavKumar07 said:
Flash Kenzo Firmware , Rom & Nougat Gapps not MM , next reboot system
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
thanks @VaibhavKumar07
so, this is exactly what I've tried a few times.
what about wipes and all that stuff?
I don't mind doing a clean install and reinstalling/reconfiguring everything.
I've tried different things, but for example what is mentioned in the thread "CM13/14/14.1/AOSP N firmware for KENZO/KATE [VoLTE][12.1.2017]"
-Reboot to TWRP recovery
-Flash firmware
-Factory reset (data, cache and dalvik-cache)
-Flash your favorite Marshmallow or Nougat ROM
-Reboot your phone
is that still valid for the nightly builds from April 2017?
On Cm firmwares I was unable to get VoLTE working so recommend you to flash Miui beta firmware search in SD Rom or guide section you'll find em if not message me again .
Regarding procedure :
- First flash Twrp 3.1.1.0 from official site cuz that's latest
- Next go & wipe check everything except SD card & OTG
- Flash Firmware
- Flash Rom
- Flash Gapps Arm *64 Android N from Open apps
- Flash Any Add-ons if required like kernel or Sound enhancement mods ( optional )
- Clean cache/dalvik cache
- Reboot
Mention the Rom you're flashing!
Sent from my Redmi Note 3 using Tapatalk
So, I did all that several times, except for flashing the latest twrp version. I'm on 3.0.2-2 because it flashes ok but when rebooting it's back to 3.0.2-2. I'm doing this from fastboot. I'm not only loading, but flushing. It seems to be ok but then it's gone after reboot.
Anyway, I've tried this procedure with 3 different roms:
ResurrectionRemix
LineageOS
Nitrogen OS
flashing latest versions for each rom.
Could the twrp not updating properly have something to do with this issue? does the latest version fix some flashing issues with Nougat?
the thing is that if flashed and boots, but it doesn't run properly as mentioned.
I will try to get latest twrp version working and report back if that makes any difference.
VaibhavKumar07 said:
On Cm firmwares I was unable to get VoLTE working so recommend you to flash Miui beta firmware search in SD Rom or guide section you'll find em if not message me again .
Regarding procedure :
- First flash Twrp 3.1.1.0 from official site cuz that's latest
- Next go & wipe check everything except SD card & OTG
- Flash Firmware
- Flash Rom
- Flash Gapps Arm *64 Android N from Open apps
- Flash Any Add-ons if required like kernel or Sound enhancement mods ( optional )
- Clean cache/dalvik cache
- Reboot
Mention the Rom you're flashing!
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
so, still fighting with this.
i managed to upgrade to twrp 3.1.0-1, all good.
however, i still have the same problem with the initial screen, it keeps reloading every few seconds and can't finish the setup or even skip it.
i've tried different versions of firmware. I've also tried flashing the latest miui rom (dev and global) and then a custom rom.
i've tried different builds (different dates) of the following roms:
nitrogenOS
lineageOS
aospextended
mokee
resurrectionremix
exact same behaviour with all these roms.
what am I doing wrong? i'm on marshmallow and everything works fine, but stuck moving to nougat. do I have to flash something not mentioned already to move from custom MM to custom Nougat?
txutxe said:
so, still fighting with this.
i managed to upgrade to twrp 3.1.0-1, all good.
however, i still have the same problem with the initial screen, it keeps reloading every few seconds and can't finish the setup or even skip it.
i've tried different versions of firmware. I've also tried flashing the latest miui rom (dev and global) and then a custom rom.
i've tried different builds (different dates) of the following roms:
nitrogenOS
lineageOS
aospextended
mokee
resurrectionremix
exact same behaviour with all these roms.
what am I doing wrong? i'm on marshmallow and everything works fine, but stuck moving to nougat. do I have to flash something not mentioned already to move from custom MM to custom Nougat?
Click to expand...
Click to collapse
Try this once (Clean) :
Flash Nitrogen
Reboot
Flash gapps and firmware.
Hope it may work for you.
Hi all, Am new to the Nexus9, I picked one up quite cheap and thought I would have a go at flashing a decent Rom. I am having no problems flashing a rom but every time I try and flash Gapps the Tablet gets stuck in a bootloop. I have tried lots of versions of Gapps but mostly arm64. I managed at one stage to flash one via the internal memory that seemed to work but then couldnt get Play sevices to work. Tried another but stuck in bootloop again.
At the moment I am trying a version of Slimrom and have tried Lineage 14.1. Anyone got any suggestions?
I normally flash a new rom in this order if the new rom is in my Download folder:
- TWRP Wipe advanced, tick System,Data,Cache.
-Back
-Install, go to sdcard/Download
-Select rom.zip
-after finish go back
-Select gapps64.zip
-after finish installing I press clean Dalvik and Cache
- Reboot system.
Wait a while and install as new device.
This should work.
With a normal update of a rom I simply install the update without wiping my system.
johhnyhotrocks said:
Hi all, Am new to the Nexus9, I picked one up quite cheap and thought I would have a go at flashing a decent Rom. I am having no problems flashing a rom but every time I try and flash Gapps the Tablet gets stuck in a bootloop. I have tried lots of versions of Gapps but mostly arm64. I managed at one stage to flash one via the internal memory that seemed to work but then couldnt get Play sevices to work. Tried another but stuck in bootloop again.
At the moment I am trying a version of Slimrom and have tried Lineage 14.1. Anyone got any suggestions?
Click to expand...
Click to collapse
If you're using opengapps, they are having trouble booting on a fresh install on slim and LineageOS. Try an older build of slim or lineage, boot up and set up, then update to newest build.
Solution
johhnyhotrocks said:
Hi all, Am new to the Nexus9, I picked one up quite cheap and thought I would have a go at flashing a decent Rom. I am having no problems flashing a rom but every time I try and flash Gapps the Tablet gets stuck in a bootloop. I have tried lots of versions of Gapps but mostly arm64. I managed at one stage to flash one via the internal memory that seemed to work but then couldnt get Play sevices to work. Tried another but stuck in bootloop again.
At the moment I am trying a version of Slimrom and have tried Lineage 14.1. Anyone got any suggestions?
Click to expand...
Click to collapse
I had the same issue with my NEXUS 9 wifi, but this solution mentioned here worked for me!
I am using:
lineage-14.1-20180920-nightly-flounder-signed
open_gapps-arm64-7.1-mini-20180923
Vendor Version: n9f27m
wanderweg you are my hero!
Mods make this stickie in the first posts....
If the system doesn't start after flashing with gapps just do this...
After flashing, mount system from TWRP, go to the "Advanced" tab, click on Terminal and type the following command:
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
Just killed 2 days trying to figure it out and that's all it was.
P.S. Maybe roms can be updated to include the fix?
MOCKBA said:
wanderweg you are my hero!
Mods make this stickie in the first posts....
If the system doesn't start after flashing with gapps just do this...
After flashing, mount system from TWRP, go to the "Advanced" tab, click on Terminal and type the following command:
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
Just killed 2 days trying to figure it out and that's all it was.
P.S. Maybe roms can be updated to include the fix?
Click to expand...
Click to collapse
It's a gapps issue not a ROM issue. Every now and then the setup wizard is weird in opengapps.
Hey guys,
Googe play services keeps stopping
android.process.media keeps stopping
bluetooth keeps stopping
at the first start (google register)
I tried: 2 different roms: mcaosp + pixel, newest gapps (nano), flashed data, cache, dalvik + system
Do you have any solutions/ tipps? I want to try pie
Greetings
I had this problem too, tried all variants of gapps, bitgapps. All variants of twrp, all pie ROMs and same error. You can try and see that if you create a second user in the phone, suddenly all works perfectly.
tl;dr:Just try crdroid ROM, the one worked for me on the owner user
Flash the ROM first without gapps then boot normally.Turn off phone,go to TWRP and then flash GAPPS.
Had this issue many times and its quite annoying.
Thanks for the answers. I tried this 2 times ;(
It just dont work with your tipps. I will go back to oreo until I get news about this
no fix yet ;/
Flashed all except usb otg + sd card, installed firmware 9.6.2 and tried syberia + arrow rom. (Followed the install tutorials)
Android PIE dont like me ;(
EDIT: Got AOSP Extended to work but now it searches for updates since 10 minutes. (I have good wlan <.<)