Related
Hello!
today i flashed the new ROM. First I had problems with my ROM Manager but after I updated that everything looked fine. I could install the ROM but when the phone finaly booted I could only unlock my SIM card but after that every application crashed....
I followed the instructions. The only thing I ignored was the kernel...
Copy the downloaded AOSB to your phone.
update recovery, is required for install android kitkat
Boot into your recovery
Back up your ROM
Enter recovery
Make full wipe "included "system"
Select Recommended kernel for first install - > which kernel is recommended/how do I select it??
Install the ROM
install GAPPS package - download it from here
Reboot - the first boot can take up to 2 minutes
Recommended to Reboot again after ROM is up for the first time
2 second to up ! and 1 second to restart or shutdown ! it is AOSB
could this be the reason for every application crash? And how can I fix it?
http://forum.xda-developers.com/showthread.php?t=2642605
bernbrun said:
Hello!
today i flashed the new ROM. First I had problems with my ROM Manager but after I updated that everything looked fine. I could install the ROM but when the phone finaly booted I could only unlock my SIM card but after that every application crashed....
I followed the instructions. The only think I ignored was the kernel...
Copy the downloaded AOSB to your phone.
update recovery, is required for install android kitkat
Boot into your recovery
Back up your ROM
Enter recovery
Make full wipe "included "system"
Select Recommended kernel for first install - > which kernel is recommended/how do I select it??
Install the ROM
install GAPPS package - download it from here
Reboot - the first boot can take up to 2 minutes
Recommended to Reboot again after ROM is up for the first time
2 second to up ! and 1 second to restart or shutdown ! it is AOSB
could this be the reason for every application crash? And how can I fix it?
http://forum.xda-developers.com/showthread.php?t=2642605
Click to expand...
Click to collapse
I think the kernel stuff is here because on others devices there are differents kernels.
On Vision, the recommended one is inside.
If not, the aroma installer would give you a choice.
So what else can cause all apps to crash
Kéno40 said:
I think the kernel stuff is here because on others devices there are differents kernels.
On Vision, the recommended one is inside.
If not, the aroma installer would give you a choice.
Click to expand...
Click to collapse
There is no aroma installer. I can just install the ROM without any choise. So what else can cause the phone to crash?
I can only enter the PIN, then pull down the status bar and "confirm" that all applications are closed or couldn't be started. :crying:
bernbrun said:
There is no aroma installer. I can just install the ROM without any choise. So what else can cause the phone to crash?
I can only enter the PIN, then pull down the status bar and "confirm" that all applications are closed or couldn't be started. :crying:
Click to expand...
Click to collapse
my installation was smooth I used 4EXT
1st backup system did :good:
2nd format and system date cache
3rd boot and tested all for a while ok
4th installed GAPPS form here CM11 http://wiki.cyanogenmod.org/w/Google_Apps small package :good:
5th boot and everything ok
So it's maybe the SD card?
Frogkiller said:
my installation was smooth I used 4EXT
Click to expand...
Click to collapse
My SD card is formatted is FAT32...so change this to 4EXT should help me?
No keep sdcard fat32, 4ext is the name of a recovery and Frogkiller was suggesting to use this one.
What I would do is check md5sum of ROM and gapps to insure you don't have a bad download.
Be sure you have a compatible recovery (latest cwm, 4ext or twrp)
Wipe everything again
(Probably even fastboot wipe or use a superwipe script)
Flash ROM
Flash gapps
Reboot
(And stay away from ROM manager)
If this still doesn't work give some more info on phone, write down everything from bootloader screen, version of recovery, etc
Sent from my Nexus 7 using XDA Premium 4 mobile app
Hi. I have an issue with 3G/Wi-Fi connections. After some time of Wi-Fi or 3G turned on connection to the Internet is not avaliable. It is showing me on status bar that Wi-Fi/3G is running correctly but whenever I'd like to open some web pages there's an info about not being able to connect to the Internet or when I'd like to download an app from Play Store it is simply not downloading. The only thing which helps is rebooting my HTC. It is annoying and I'd like to ask if there's anything I can do about it. The same was happening when I was using CyanKat 1.0.
EDIT: After a few hours of not rebooting device (the only possibility of making internet connection to work correctly) I see that the Wi-Fi doesn't even want to turn on. There's an info about Turning the WiFi on and nothing happens at all.
Solution!
Frogkiller said:
my installation was smooth I used 4EXT
1st backup system did :good:
2nd format and system date cache
3rd boot and tested all for a while ok
4th installed GAPPS form here CM11
small package :good:
5th boot and everything ok
Click to expand...
Click to collapse
This made the difference! Thanks for all your help. There was something wrong with the suggested gapps. Started without installing them and here we go!
osiol3k said:
Hi. I have an issue with 3G/Wi-Fi connections. After some time of Wi-Fi or 3G turned on connection to the Internet is not avaliable. It is showing me on status bar that Wi-Fi/3G is running correctly but whenever I'd like to open some web pages there's an info about not being able to connect to the Internet or when I'd like to download an app from Play Store it is simply not downloading. The only thing which helps is rebooting my HTC. It is annoying and I'd like to ask if there's anything I can do about it. The same was happening when I was using CyanKat 1.0.
EDIT: After a few hours of not rebooting device (the only possibility of making internet connection to work correctly) I see that the Wi-Fi doesn't even want to turn on. There's an info about Turning the WiFi on and nothing happens at all.
Click to expand...
Click to collapse
This is a kernel problem. But for turn on WiFi reboot your phone then you can do it
Sent from my Nexus 7 using Tapatalk
Can you tell me which kernel should I use? I've already updated recovery to newest 4EXT recovery.
EDIT: Flashing no matter what kernel ends with dead device. It tries to turn on but it doesn't happen. I obviously do something wrong but I can't figure out what it is on my own. Can I ask for some little advice?
http://forum.xda-developers.com/showthread.php?t=2290892
http://forum.xda-developers.com/showthread.php?t=2253023
That's what I've been trying to flash via recovery. Making full wipe, installing kernel then rom and it simply doesn't work.
bernbrun said:
Hello!
today i flashed the new ROM. First I had problems with my ROM Manager but after I updated that everything looked fine. I could install the ROM but when the phone finaly booted I could only unlock my SIM card but after that every application crashed....
I followed the instructions. The only thing I ignored was the kernel...
Copy the downloaded AOSB to your phone.
update recovery, is required for install android kitkat
Boot into your recovery
Back up your ROM
Enter recovery
Make full wipe "included "system"
Select Recommended kernel for first install - > which kernel is recommended/how do I select it??
Install the ROM
install GAPPS package - download it from here
Reboot - the first boot can take up to 2 minutes
Recommended to Reboot again after ROM is up for the first time
2 second to up ! and 1 second to restart or shutdown ! it is AOSB
could this be the reason for every application crash? And how can I fix it?
http://forum.xda-developers.com/showthread.php?t=2642605
Click to expand...
Click to collapse
Don't use gapps from this link. Use the modular Package from PAGapps
I recommend the MICRO MODULAR PACKAGE
osiol3k said:
Hi. I have an issue with 3G/Wi-Fi connections. After some time of Wi-Fi or 3G turned on connection to the Internet is not avaliable. It is showing me on status bar that Wi-Fi/3G is running correctly but whenever I'd like to open some web pages there's an info about not being able to connect to the Internet or when I'd like to download an app from Play Store it is simply not downloading. The only thing which helps is rebooting my HTC. It is annoying and I'd like to ask if there's anything I can do about it. The same was happening when I was using CyanKat 1.0.
Click to expand...
Click to collapse
I don't have an answer to your problem but just for the record I haven't had any problems with wi-fi. Back and forth between work and home, I was at a convention yesterday and turned off wifi to try and conserve battery, got home and turned it back on, then upgraded to 1.3.0.
So that being said it may just be you, sorry. I don't remember ever changing the kernel but it's been about 3 years since I installed CyanogenMod, and then about 18 months ago I tried a bunch of other ROMs (to great disappointment before switching back to CM7) so who knows what I actually did at the time.
I hope you figure out what causes the issue and manage to fix it, I have been extremely happy with this AOSB ROM, it's pretty amazing.
Ok, I recently installed Llama so it would automatically change stuff when I go between work and home. This includes turning the wifi off when I get to work (so I don't keep getting the "there is an open wifi" message for the wifi I can't connect to). When I get home it's supposed to turn the wifi back on: it did not. Manually trying to turn it back on it just sits at the screen saying "Turning on wifi" (or whatever the exact words are).
So yeah, there does appear to be a bug with the wifi. I'll check my logcat later, see if I can locate a problem but I doubt I have the tools to figure it out. In the meantime I guess I just don't turn wifi off.
Has anyone else had a problem with the Google "navigation" app? Tried using it for the first time this weekend. In the basic map I had no problem, it knew exactly where I was and the direction I was facing, but when I actually started navigating and it brought up the new app it was very inaccurate and showed me facing north always.
I'm just going to downgrade (as soon as I figure out how... any tips?) but wanted to see if anyone else was having this issue or just me.
Thanks.
osiol3k, and anyone else having the wifi issue, I think I fixed it.
I deleted the "/data/misc/wifi" directory in a adb root shell and rebooted my phone. It has now been several hours, I've turned wifi on and off, connected to different networks, turned wifi tethering on and off, turned it off for several minutes before turning it back on again, a few other things, nothing seems to break it.
It wiped out all my previously saved locations and wifi passwords, obviously, but that's easy enough to fix.
Hope this helps!
I used this asob 1.2.9 for a day and I found it very slow to use, is there a way to speed things up? thanks.
This is simply a stock AOSP otapackage build using the preview binaries from here https://developers.google.com/android/nexus/blobs-preview
Considering that Android L is not released and these are preview blobs you should understand that this may not be considered perfect as in there may be bugs (although i have not seen any)
Use my GAPPS otherwise **** will not work
You will lose twrp after installing this so you will need to reapply that afterwords… follow these instructions to a tee to get this working
I take no responsibility if you destroy your system , proceed at your own risk bla bla bla
Install… FOLLOW EXACTLY... I will know when you deviate and will not respond to messages for help afterwords
Copy gapps and ota to internal sdcard
Boot to twrp
Wipe data and system and cache via advanced (this must be done)
Install aosp_manta-ota-eng.kejar31.zip
Back to main menu
Select mount then unselect system (uncheck it)
Back to main menu
Install gapps-lp-20141106-signed.zip
reboot
Download
ROM - https://mega.co.nz/#!VZpgHTTa!_WYFnfmSm5aQAE3DyZ35x2PaRIzM-2U_nigqb6hlMEw
GAPPS - https://mega.co.nz/#!JdYCnSxZ!fn82nMs3mA0VdDBTYuguT9OXHjQtt7P9jnZUyndrtZA
if someone wants to host mirrors let me know.
Does this have the Wifi fix in it? or has Google not published that yet?
Can't wait to install this and try it. I was going to wait it out for the official release but I've broke I have to try it.
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
ChaosMinionX said:
Does this have the Wifi fix in it? or has Google not published that yet?
Click to expand...
Click to collapse
I don't think it will be as Google haven't released the version with the patch yet as that will be the OTA or factory image versions.
ChaosMinionX said:
Does this have the Wifi fix in it? or has Google not published that yet?
Click to expand...
Click to collapse
most likely not have not tested for any wifi bugs atm
Thank you I'm really excited about it. But I have a question. Can I have use my flash drives in this ROM without stickmount?
ROM
So is this a full-fledged ROM that I can install after wiping any ROM, or do I have to flash back to stock android 4.4.4 and then flash this??
I seem to be unable to install on my Nexus 10. I've followed the stages, but when I get to flashing the AOSP rom it stays on it forever!
I've updated my TWRP to v2.8.1.0 but it does the same thing.
Sorted the problem I think, some how the download I had on my Nexus was not a happy one haha. just on the boot logo now :3
Thank you, booted up and running. One question, I couldn't install Google+. It cannot be found on Play Store and installing from APK doesn't work neither.
Great work, thanks. Flashed about an hour ago, flawless so far!
seems my internal storage is not working ,I am not able to see any storage area, it gives an error. Might be a bad flash.
gabegom said:
So is this a full-fledged ROM that I can install after wiping any ROM, or do I have to flash back to stock android 4.4.4 and then flash this??
Click to expand...
Click to collapse
Same question here. Can we flash after any ROM or do we have to flash stock .imgs first then this?
Is anyone having problems with Wifi? I have flashed this twice and I cannot get Wifi to connect. It sees networks but won't connect to any of them.
ChaosMinionX said:
seems my internal storage is not working ,I am not able to see any storage area, it gives an error. Might be a bad flash.
Click to expand...
Click to collapse
internal storage is working here
Followed all the steps to the T, now it just boots up to the android logo and shuts down?
Anybody have the same problem?
chowynatt said:
Followed all the steps to the T, now it just boots up to the android logo and shuts down?
Anybody have the same problem?
Click to expand...
Click to collapse
For me it took a lot of time booting up, I was about to power it off and reinstall, but eventually it show the android logo and now is running well.
tavocabe said:
For me it took a lot of time booting up, I was about to power it off and reinstall, but eventually it show the android logo and now is running well.
Click to expand...
Click to collapse
Did you manage to install Google+?
kejar31 said:
This is simply a stock AOSP otapackage build using the preview binaries from here https://developers.google.com/android/nexus/blobs-preview
Considering that Android L is not released and these are preview blobs you should understand that this may not be considered perfect as in there may be bugs (although i have not seen any)
Use my GAPPS otherwise **** will not work
You will lose twrp after installing this so you will need to reapply that afterwords… follow these instructions to a tee to get this working
I take no responsibility if you destroy your system , proceed at your own risk bla bla bla
Install… FOLLOW EXACTLY... I will know when you deviate and will not respond to messages for help afterwords
Copy gapps and ota to internal sdcard
Boot to twrp
Wipe data and system and cache via advanced (this must be done)
Install aosp_manta-ota-eng.kejar31.zip
Back to main menu
Select mount then unselect system (uncheck it)
Back to main menu
Install gapps-lp-20141106-signed.zip
reboot
Download
ROM - https://mega.co.nz/#!VZpgHTTa!_WYFnfmSm5aQAE3DyZ35x2PaRIzM-2U_nigqb6hlMEw
GAPPS - https://mega.co.nz/#!lVYHAAjI!-478q0a5v6QAL9-6bDNzo7utJ1AXZD539CpTP6R63w8
if someone wants to host mirrors let me know.
Click to expand...
Click to collapse
So far so good! I'm in the setup... it's taking a long time checking my wifi connection.
edit:changing to 5ghz did the trick
edit2: after passing setup, changing back to 2.4ghz works just fine.
tavocabe said:
For me it took a lot of time booting up, I was about to power it off and reinstall, but eventually it show the android logo and now is running well.
Click to expand...
Click to collapse
Yeah all working now, took forever to boot, went black a few times and then started working.
Now the $64,000 Question: will it root?
because I've had my fun with it. And without root, I can't keep it. I doubt it can be, but I have to hope.
Flashed yesterday. My experience was as follow:
1) Dirty flash from PA, system erase command did t seem to work. After flashing it booted up all apps were there, 4.4 gapps were force closing.
2) Twrp advance factory reset and erase. normal flash afterwards with gapps 5.0. Setup wizard crash. Couldn't get past that error.
3) Factory 4.4 image. Complete erase, and flash to L, boot up and then TWRP and gapps flash. Tablet booted correctly and works since then.
Regarding the WiFi battery drain bug:
No issue here. Battery drain when idle is a flat line. No misc group with excessive battery is listed in the battery stats.
Further more performance is great, basic apps seem to work correctly. Haven't gotten much into detail.
Regarding the G+ question. It works fine.
Hey guys,
I have a HTC M9
I am trying to install the Xposed Framework on my Rooted M9 with stock ROM but inside the Xposed app it tells me that it's not installed.
I have TWRP installed.
I rooted my phone with SuperSU v2.65 (After trying a couple of versions that would result in boot loop)
I checked my phones CPU (ARM64) and downloaded "xposed-v86-sdk23-arm64" as well as "XposedInstaller_3.0_alpha4.apk".
I booted into TWRP and Installed the xposed-v86-sdk23-arm64 Framework, it gets to Placing Files and then my phone reboots (I don't know if this is normal or not).
My phone reboots and I open XposedInstaller, under Framework it says "The latest version of Xposed is currently not active, Did you install the Framework and reboot?"
Inside the Framework menu it says "The Xposed Framework is not installed. Please download the latest ZIP file from XDA and flash it manually via reocvery."
The options Install/Update, Uninstall, Recovery (Flash zip automatically) are grayed out.
When I press the Soft Reboot button the phone does restart but no change.
When I try to press the Reboot option I get this error:
Code:
sush: <stdin>[8]: /data/user/0/de.robv.android.xposed.installer/cache/busybox-xposed: not found
Reboot failed please use the device's normal reboot function.
I have restarted the phone normally a couple of times with no change.
I'm new to rooting but I don't find this stuff too difficult to understand, I had a lot of problems trying to get my phone to root in the beginning, I had to try a few SuperSU versions before I could get my phone past boot looping. When I run Root Check it tells me that my phone is Rooted.
I'm not sure what other information I can post to help yous help me but if there's anything you need to know just ask and I'll reply asap.
Cheers guys
I basically want access to Xposed so I can use the FakeGPS and the Hide Mock Location modules.
EDIT (29/07 2:00PM)
I re-downloaded xposed-v86-sdk23-arm64 and tried flashing it again, I read somewhere someone mentioning to clear the caches after the install has finished but when I start the install and it reaches "Placing Files" the phone automatically reboots itself, so I held Volume down and Power to go straight back into Download Mode > Boot Mode > Recovery Mode and cleared the caches, let the phone boot up and still have the exact same problem as the above post.
Seeing as though I haven't gotten any advice yet I am going to try an older version of the Installer app, I have 2 seperate backups of my device so if anything goes wrong I can restore, wish me luck!
I have almost the same problem, with the exception that I don't get to see errors.
I have it rooted with superSU 2.64 (beta) and with TWRP 3.0.2.
Start the flash process using TWRP and after a couple of seconds it just black screens and reboots. Some times it survives and boots, sometimes it doesn't boot.
Since I have backed up my whole system before rooting, I can return back to normal.
The funny thing is, I have managed to install Xposed on the first run, but after restoring a back up, it refuses.
No idea what to do
Wolf_vx said:
I have almost the same problem, with the exception that I don't get to see errors.
I have it rooted with superSU 2.64 (beta) and with TWRP 3.0.2.
Start the flash process using TWRP and after a couple of seconds it just black screens and reboots. Some times it survives and boots, sometimes it doesn't boot.
Since I have backed up my whole system before rooting, I can return back to normal.
The funny thing is, I have managed to install Xposed on the first run, but after restoring a back up, it refuses.
No idea what to do
Click to expand...
Click to collapse
You have described my situation perfectly.
I have a back up I can restore through TWRP if I soft brick it, which at this moment I just did.
I tried flashing the same superSU version again seeing as though it was the only one I could get to work (didn't try your version though) and then installed the latest Framework version right after without rebooting, cleared the two caches and rebooted, I get past the first boot screen, I see my mobile providers boot screen, I then get to the screen with One in big letters and it stops there, I'll try a few more reboots before I restore.
Xposed isn't stable on the m9 and is why I have avoided installing it. Some people get it running first time, no issues. Some people brick their phones. It really is a roll of the dice.
I'd stay away from it if i were you. Htc's can't be easily recovered.
Beamed in by telepathy.
it doesn't brick the phone, but there are a few tutorials with other methods of flashing xposed, should be inside software development of android forum. please try those solutions and please stop creating two threads, with nearly same problem. both things can be asked in one thread, thanks
stock rom has often problems. you need to install busybox to have it working properly
Hello,
[Sorry: can't edit title]
I've been trying to install Lineage 14.1 on my Samsung Galaxy Tab Pro (SM-T520), and haven't been successful.
I keep getting the message "Google Services Framework keeps stopping", sometimes alternating with the message "android.process.media has stopped".
I've used the following installation procedure:
1. Starting with the stock Samsung Android v4.4.2, I used Odin v3.1.2, to root the device, by installing
CF-Auto-Root-picassowifi-picassowifixx-smt520.tar.md
2. I used Odin to install picassowifi TWRP v2.8.7.0. I didn't use the latest v3.1.1-0, because it reboots the
device while making Nandroid backups. Available here
https://eu.dl.twrp.me/picassowifi/
3. I copied several versions of Lineage OS amd Gapps (see below) to the device's SD card
4. I used TWRP to wipe the cache/dalvic/data/system each time, using the Wipe->Advanced option
5. I used TWRP to install the Lineage OS amd Gapps as an atomic operation on the device
6. After installation, I rebooted from TWRP:
- without rooting: I get the message "Google Services Framework keeps stopping"
- with rooting, by installing SuperSU: The device enters into a boot loop, displaying the sliding Lineage logo
I followed the same procedure to update my Samsung Galaxy S4 Mini, and it worked flawlessly.
I tried the following Lineage OS versions, available here:
https://download.exynos5420.com/LineageOS-14.1/n2awifi/
lineage-14.1-20170506-UNOFFICIAL-n2awifi.zip
lineage-14.1-20170715-UNOFFICIAL-n2awifi.zip
I also tried the folowing Lineage OS versions, available here:
https://download.lineageos.org/n2awifi
lineage-14.1-20170608-nightly-n2awifi-signed.zip
lineage-14.1-20170713-nightly-n2awifi-signed.zip
I tried the following versions of Gapps, available here (32-bit arm, Android v7.1, stock variant):
http://opengapps.org/?api=7.1&variant=stock
open_gapps-arm-7.1-stock-20170505.ziip
open_gapps-arm-7.1-stock-20170711
I tried several combinations of these 2 packages. With all the combinations I tried, I got the results summarised above.
This post suggests installing Lineage OS alone without Gapps, and then install Webview Implementation, if not installed:
http://www.lineageosrom.com/2017/02/how-to-fix-google-play-services-error.html
When I tried this and reboot, I get the messages "android.process.media" has stopped, followed by the message "clock has stopped". When I click away these messages, and click on next on the Lineage OS screen, the device enters into a boot loop displaying the sliding Lineage logo. This agrees with the Lineage recommendation, that both packages need to be installed at the same time:
https://wiki.lineageos.org/devices/n2awifi/install
Can anyone please help? I really don't want to go back to Android v4.4.2 on my SM-T520.
Hello so to get rid of the error I would suggest downloading samsung kies 1 not 2 or 3 and flashing completely back to stock then try rooting and flashing rom should get rid of system errors and force closes. Kies will ask you for model and serial number. Serial is found on back of the tablet. As another suggestion I would try resurrection remix by cosmox. It is very stable everything works. I just posted a link in that thread with a link to download samsung kies for a 64 bit windows and other relevant files if you need. Let me know if you need any other help. Also closer inspection of your links. I think for sm-t520 u should be using twrp Picassowifi, not n2awifi so idk if that will work or not. Not sure about that part though because they may have made it work on Picasso.
Thanks paintball.
I confirm that I had used picassowifi TWRP. I've edited the original post to indicate this.
I've also tried what you suggested - I reinstalled the original stock Samsung firmware using Odin, and used TWRP to again install Lineage. Same result, still displaying the same Google Service errors.
I'll look at the Resurrection remix.
Paul
paintball,
I've found a solution, that I thought I'd post here in case anyone else has the same problem.
I wiped the cache/dalvic after each step of the installation:
Wipe-> Advanced -> wipe cache / data / dalvic / system
Install -> flash Lineage -> wipe cache/dalvic
Install -> flash Gapps -> wipe cache/dalvic
Reboot -> don't install SuRoot
I got a Music closed error during the first boot, which hasn't appeared since.
Afterwards, I used Odin to install CF-Auto-Root. The device rebooted twice after this step, but now appears to be OK.
A final problem I had was that it couldn't find my wifi SSID. I solved this by setting wifi region to Europe.
ppmoore said:
Thanks paintball.
I confirm that I had used picassowifi TWRP. I've edited the original post to indicate this.
I've also tried what you suggested - I reinstalled the original stock Samsung firmware using Odin, and used TWRP to again install Lineage. Same result, still displaying the same Google Service errors.
I'll look at the Resurrection remix.
Paul
Click to expand...
Click to collapse
I suggested using Samsung kies which I'm positive works, not Odin, but I'm glad you got it fixed.
ppmoore said:
Hello,
[Sorry: can't edit title]
I've been trying to install Lineage 14.1 on my Samsung Galaxy Tab Pro (SM-T520), and haven't been successful.
I keep getting the message "Google Services Framework keeps stopping", sometimes alternating with the message
<snip>
Click to expand...
Click to collapse
I'm having a similar issue. Mine differs in the following ways.
I was able to successfully install and run LineageOS with OpenGApps full, but reverted to a nandroid backup because I needed some information from the original install. Since then, I have been unable to get past the initial couple of screens for setting things up--and this with the constant "Google Services Framework keeps stopping" error.
I have tried most of the "fixes" I've found but to no avail. I notice that, (1) when I go to the drop-down menu and setup WiFi, as soon as the device connects to the Internet, I go to the Lineage bootup animation and get stuck there. If I hard boot from there, I can get in up to the point where I connect to the Internet (not just router, but actually get through to the Internet) and (2) I cannot enable Developer options--when I try, no matter how many times I click on the Build number, I get no indication of the options being enabled.
I have tried several permutations of Lineage OS nightlies along with various flavors of OpenGApps, with and without root, wiping cache/dalvik/data/system, wiping only some, wiping none.
I also cannot restore the backup of the running LOS that I had up (I did take a backup before going back to the original setup). When I try, I get the same results as above--as if I had backed-up an un-instantiated setup.
Any thoughts?
eckster said:
I'm having a similar issue. Mine differs in the following ways.
I was able to successfully install and run LineageOS with OpenGApps full, but reverted to a nandroid backup because I needed some information from the original install. Since then, I have been unable to get past the initial couple of screens for setting things up--and this with the constant "Google Services Framework keeps stopping" error.
I have tried most of the "fixes" I've found but to no avail. I notice that, (1) when I go to the drop-down menu and setup WiFi, as soon as the device connects to the Internet, I go to the Lineage bootup animation and get stuck there. If I hard boot from there, I can get in up to the point where I connect to the Internet (not just router, but actually get through to the Internet) and (2) I cannot enable Developer options--when I try, no matter how many times I click on the Build number, I get no indication of the options being enabled.
Any thoughts?
Click to expand...
Click to collapse
Hi Eckster,
I have exactly the same problem on a LG G2 with LOS 14.1. It ran July version perfectly but I didn't make a backup and now I'm stuck. Did you ever manage to fix this?
Thanks,
Kevin
Managed to solve it. I formatted all partitions _including_ data (which means you'll also loose all zips you wanted to install so make sure that adb is working). Then rebooted into the recovery. Installed as usual, worked.
detlef25 said:
Managed to solve it. I formatted all partitions _including_ data (which means you'll also loose all zips you wanted to install so make sure that adb is working). Then rebooted into the recovery. Installed as usual, worked.
Click to expand...
Click to collapse
how did you format the partitions? I can only find "format data".. thx
detlef25 said:
Managed to solve it. I formatted all partitions _including_ data (which means you'll also loose all zips you wanted to install so make sure that adb is working). Then rebooted into the recovery. Installed as usual, worked.
Click to expand...
Click to collapse
:thumbsup: I was on lineage 14, all was well. I tried an old stock rom NK2, that was fine. I tried to restore lineage backup via twrp, got this problem with the framework crashing. No amount of re-flashing twrp nor lineage, gapps, modem, bootloader, etc nothing worked; always crashed right after boot to lock screen. Finally twrp "format data" - yes. Now lineage boots to welcome, no crash; restore backup - after copying it back to internal - and all is good.
I'm glad it works but why is it needed in this case to remake the filesystem on data - does it work by removing some bad file or does it work by rebuilding the ext4 and security context? this is with latest twrp twrp-3.2.1-0-klte.
Hi,
don't know if you solved it eventually, or maybe helpful for other people with the same problem. I had the same problem, spent 6 days digging around on the internet why the framework keeps stopping and crashing.
I eventually found out that:
- TWRP 3.0.2.0 is WAY more stable than 3.1.1.0 (which never succeeded in installing gapps without crashing)
- Wiping system, data, dalvik recovery and internal storage is not the only thing that needs to be done. You also need to use the 'FORMAT DATA" button (everything will be wiped from your tablet, so, as always, backups )
- After that, install the lineageOS binary, after the installation, wipe dalvik/cache, go back and install the appropriate GApps package, wipe dalvik/cache and reboot
Say whatever you need to whatever deity you prefer and wait for the tablet to boot.
I hope to be of some help to other people having the same problem
Code:
Sent from my SM-S920L using Tapatalk
grammar
detlef25 said:
Managed to solve it. I formatted all partitions _including_ data (which means you'll also loose all zips you wanted to install so make sure that adb is working). Then rebooted into the recovery. Installed as usual, worked.
Click to expand...
Click to collapse
Was going crazy trying to figure out why LineageOS was encountering so many ANRs. The first time I flashed Lineage it worked beautifully but every time after that it just went nuts. This fixed it for me, thanks dude!
Note to others who may end up here, after formating data I had to install a stock ROM, then wipe and install Lineage. Lineage wouldn't install due to Updater process ended with ERROR: 7 which was because there was some bit of information that was on the data partition that showed the install script that the phone was actually a Note II. Formating data blows that info away but installing stock puts it back on.
LievenVanh said:
I eventually found out that:
- TWRP 3.0.2.0 is WAY more stable than 3.1.1.0 (which never succeeded in installing gapps without crashing)
- Wiping system, data, dalvik recovery and internal storage is not the only thing that needs to be done. You also need to use the 'FORMAT DATA" button (everything will be wiped from your tablet, so, as always, backups )
- After that, install the lineageOS binary, after the installation, wipe dalvik/cache, go back and install the appropriate GApps package, wipe dalvik/cache and reboot
Click to expand...
Click to collapse
Coming into this thread after a few hours of struggle with an old GS4 I can say that this method instantly worked for me as well.
Thanks!
Thanks for the help to resolve my issue of installation. Do you have a solution for Zoom , where my audio (cannot hear other speakers) and video is missing. Did enable access for Mic, Camera etc in App permission.
Look at this thread: https://forum.xda-developers.com/ga...-t520-unofficial-lineage-14-1-t3538770/page86 -- last two posts
hamudistan said:
Look at this thread: https://forum.xda-developers.com/ga...-t520-unofficial-lineage-14-1-t3538770/page86 -- last two posts
Click to expand...
Click to collapse
That solution didn't work. My Zoom audio still not working.
I installed the lineage-14.1-20170918-nightly-chagallwifi-signed.zip ROM a few days ago and it would not progress past the setup wizard after startup. After choosing the language, it announced a problem, and after a second try it closed the procedure and I couldn't move on to installing the ROM. I then downloaded the ROM from Linear directly, which was lineage-14.1-20170923-nightly-chagallwifi-signed.zip, and it went without a hitch. Not leaving well enough alone, I tried installing the next nightly, lineage-14.1-20170925-nightly-chagallwifi-signed.zip this morning, and ran into the same problem as last time. However, this time I also installed the version of TWRP recommended on XDA, twrp-3.1.1-0-chagallwifi.img. Unfortunately, now I can't get into recovery mode at all.
If I could just get past the setup wizard, I could use adb. Does anyone have any ideas on how to do that? Or how to install a recovery when the installed TWRP is not working? Of course, any assistance will be greatly appreciated.
Lineage itself is having issues regarding setup wizard on devices, it's being worked on.
Thanks!
If you can get in to download mode:
You could download the version of TWRP you were using before from here. Download the tar version.
Then go in to download mode and flash TWRP with odin. Choose AP for recovery.
Then you can get in to recovery again hopefully.
Regarding the difficulty getting through the setup wizard:
It might have to do with gapps. When I encountered this problem I chose to not flash gapps before I had completed the setup wizard.
I also had problems with BeansGapps that would not let me log in. When I flashed open_gapps-arm-7.1-pico it all worked like I expected it to.