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.
Hello,
I'm really new to all this android thing, but I decided to root my Samsung Galaxy A7 2017 using magisk, for which I used this guide.
After some time of enjoying some root features I decided to try a custom ROM, the first one I tried was this one, since I heard that resurrection remix is one of the most feature rich ROMs. After flashing the zip file with TWRP I booted into system, I read that the first boot after flashing a ROM usually takes up to 10 minutes, but after just 1 to 2 minutes of showing the boot animation the device restarted and sent me back to TWRP. After this I did some searching here on XDA and watched some youtube videos that claimed to solve the problem, but none of them worked for me, as they mostly just said to reinstall the ROM and wipe dalvik cache and normal cache.
Since my phone came with stock android 8.0 I thought of installing LineageOS which was only official ROM based on android 8.0 that I could find for my device, but the same thing happened, boot animation for 1-2 minutes and then it sends me to TWRP.
In both of these attempts I downloaded everything to my pc and then moved it to my phone's internal storage.
I noticed that people were donwloading the files direcly from the phone itself, so I did that with LineageOS and after tring to boot it gave me the error "Encryption unsuccesful" with the option to reset my phone, I search in google about this problem but I'm doubtful of what to do now.
I would apreciate if someone told me what this error is, what could be the cause of it and how to fix it, and most important of all why won't my phone boot into a custom ROM and how can I get it to do so.
Thanks in advance!
Hello,
It all began that i just wanted to restart my Oneplus3 unlocked with lineage 15.
But then back in Lineage15 i wasnt able to use my pin anymore + it restarted after few seconds...
Afterwards i ended up in a lineage bootloop.
Ok, then i thought then i do a fresh flash with new lineage 16.
I tried to flash but it said i need to install new modem firmware for Lineage16.
I downdloaded the new 9.0.5 modem + firmware and flashed it from here : https://forum.xda-developers.com/oneplus-3/how-to/op3-flashable-firmware-modem-zips-t3816066
Then i tried to flash LOS16 again but it failed due to some errors on unable to mount some partitions (cache , system, etc).
So i thought i need to wipe or reformat them, as some people suggested to switch from ext4 to fat and back to reinit the partition.
I did this for at least system and internal storage. ( i learned that it was a dumb idea )
Afterwards i was not able to push anything anymore through MTP in TWRP, but i was still able to sideload or push images via adb.
Afterwards i tried to flash LOS16 or LOS15 via TWRP again but it always ends up to a "unable to mount /system (invalid argument" error at some point of the installation.
I thought: Okey maybe i go back to stock as i messed up the internal file system somehow, and go back to LOS afterwards.
So i flashed the stock recovery for nougat which i got from here: https://www.****************/2017/0...th-latest-oxygen-os-firmware-complete-unroot/
Then i tried to flash various stock Oxygen roms with the stock recovery, by using wipe + system reset + adb sideload:
4.02, 4.51, 5.08, 9.0.5
4.02 and 9.0.5 didnt run until the end.
Flashing 5.08 works but ends up in a black screen when starting it.
Flashing 4.51 works but when i start it i run into a bootloop ( 2 Dots circuling forever )
I also tried to use the 4.51 version to flash LOS again but it did not work out
I just tried again to flash 4.51 but it also didnt work out anymore. :\
So, what do you think i could do to get a working OS on my system again?
Did i do something on the installation of LOS or Oxygen ?
Can i use a backup from a friends Oneplus3_T to get a working system partition / full OS again?
Should i unbrick the phone by using one of various guides to go back to fully stock? I am kind of afraid of this, as some people describe some final brick in the threads which may be caused by modem firmware problems (Sahara issue). https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/ or https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Thank you so much, i kind of getting mad about it
@julledd
Backup from 3T seems like a bad idea.
You may have a hardware issue.
Your best bet is to use one of the tools available in the various unbrick guides. If one doesn't work, try another.
Best of luck!
Hi thx for your help!
i tried different unbrick tools (9.0.5 / 3.1.2 / 4.0.5) and after several attempts i get it flashed to the phone. But in the end it still ends up in a bootloop, either at the android logo or the circuling dots. Via Sideload i am also not able to flash a new OS. It always breaks somewhen >50%.
In very rare cases i am then able to go to the OS, but when i go to "About Phone" to unlock it for TWRP, it freezes before showing anything. I guess there is internally something broken which forbids it to show the internal state of the phone. Every boot is different, and i cannot see any system in this failure of my phone.
Do you have any more hint?
I am already at a point where i want to exchange the main PCB.. Is this possible for the Oneplus3? Can i also exchange it with a Oneplus3T PCB?
Hello everyone! I need some help because i'm out of ideas how to resolve the softbrick on my old phone. First i'll explain how i got it in this state. Brace yourself, it's a long story
So i have 2 meizu note 8 i don't use anymore (one with broken touch and lcd, and the other was perfectly fine), and because of boredom and covid restrictions i had the "brilliant ideea" to mess with them and update to android 10 with GSI treble roms. The original android was flyme os 7.1.6.1 EU. First i unlock the bootloader on both and installed twrp recovery. No problems so far , everything worked fine with flyme os. Then i tried to install gsi android 10 with twrp on one of the phone (the one that does not have the screen broken). I had an error with system partition not mounting , so i did a full format in twrp (cache, data, system,internal storage, boot,vendor) and then i managed to flash it. Android 10 GSI (Havoc Os) booted up but with problems : First i got a message right after boot "There's an internal problem with your device. Contact your manufacturer for details" then the config wizard crashed constantly, but i managed to finish the process and android is working (sort of ).The problem wich i called it soft brick is the fact that wifi, data sim,bluetooth, gps, sound are not working (not detected, nada....).Both IMEI are correctly recognized, but the basic functions of the phone don't work.
Having another identical phone with original firmware, i made a full twrp backup (21 partitions..with system,data,cache, modem,kernel,vendor ....everything) and restored it on the culprit. Flyme os booted up but with the exact same symtoms as with GSI 10. It seems i messed up somewhere so i reverted back to stock flyme os recovery and flashed the original software (update zip form their website). Still the same symtoms. So I went further and got the flyme os files for QPST / QFIL flash tool. Flashed it successfully with QFIL but no improvements. I suspected the modem firmware being corrupt and flashed it separately, but i just can't get it to work.
So any ideas? I have the msm partion table and trying to pull everything with adb root and adb shell from the other phone, and restore it back to the other, but got stuck somewhere....(i'm doing more research).
I'm asking a moderator, please delete this post. Got it resolved and I have another post with an explanation.
Trimis de pe al meu Redmi Note 9S folosind Tapatalk
Greetings!
An interesting and strange situation has appeared on the Poco F3.
Unlocked device, installed xiaomi.eu dev latest with their own TWRP, Magisk 25.2 (latest stable). I didn't install any DFE or other vbmeta etc patches.
After installing all this, after a couple of days of using the device, I get a bootloop (when I reboot the device it gets stuck on the MIUI logo), just with nothing. Before that, bootloop do not appear (I did a reboot on purpose and loaded into the system). Then, I thought the problem was in the recovery, I flashed orangefox - but the result is still the same. No any Magisk modules installed (specially tested without them). There is also a backup when everything works, it is restored, but it still does not load into the system, it just remains on the MIUI logo. In the recovery itself (what is skkk, what is ofox) is nothing red, without errors during firmware/actions. BTW, there is a problem on other ROMs based on MIUI: like Pulse, MiuiSR I tried to install on it.
I tried option to install a clean stock through miflash, and then put it through fastboot xiaomi.eu - but it also did not work.
I restored the backup when everything worked except for the data section and made data format, and only then it turned on according to the factory settings with the settings down. So the format data allows to revive it to the initial state, but this is not the way out.
On a local forum, I was told that this is some kind of problem with the encryption of the /data partition or android party rescue in recovery (red line) and it met on XDA, but no one found a clear solution.
Why does the bootloop appear only after some time (2-3 days)? This is some kind of hell and misunderstanding that this occurs specifically after a couple of days of using the device, and not right away. Where to dig and in what sequence? Thank you.
eduaaard said:
Greetings!
An interesting and strange situation has appeared on the Poco F3.
Unlocked device, installed xiaomi.eu dev latest with their own TWRP, Magisk 25.2 (latest stable). I didn't install any DFE or other vbmeta etc patches.
After installing all this, after a couple of days of using the device, I get a bootloop (when I reboot the device it gets stuck on the MIUI logo), just with nothing. Before that, bootloop do not appear (I did a reboot on purpose and loaded into the system). Then, I thought the problem was in the recovery, I flashed orangefox - but the result is still the same. No any Magisk modules installed (specially tested without them). There is also a backup when everything works, it is restored, but it still does not load into the system, it just remains on the MIUI logo. In the recovery itself (what is skkk, what is ofox) is nothing red, without errors during firmware/actions. BTW, there is a problem on other ROMs based on MIUI: like Pulse, MiuiSR I tried to install on it.
I tried option to install a clean stock through miflash, and then put it through fastboot xiaomi.eu - but it also did not work.
I restored the backup when everything worked except for the data section and made data format, and only then it turned on according to the factory settings with the settings down. So the format data allows to revive it to the initial state, but this is not the way out.
On a local forum, I was told that this is some kind of problem with the encryption of the /data partition or android party rescue in recovery (red line) and it met on XDA, but no one found a clear solution.
Why does the bootloop appear only after some time (2-3 days)? This is some kind of hell and misunderstanding that this occurs specifically after a couple of days of using the device, and not right away. Where to dig and in what sequence? Thank you.
Click to expand...
Click to collapse
Hello. To suggest in detail why this happened, unfortunately, is not advertising. but can be used in the reserve of the manufacturer of this phone?
Olesya13 said:
Hello. To suggest in detail why this happened, unfortunately, is not advertising. but can be used in the reserve of the manufacturer of this phone?
Click to expand...
Click to collapse
Hi,
What was meant and what is the meaning of your question?
Regards,
Eduard
developers still improving f2fs file system. I could imagine it's some unpatched bug (without knowing exactly if there is one)
alecxs said:
developers still improving f2fs file system. I could imagine it's some unpatched bug (without knowing exactly if there is one)
Click to expand...
Click to collapse
Hi, no idea but from some sources this indicates that the culprit is vbmeta when installing the initial twrp. But this is still being tested. A bug with a custom font in MIUI is also possible, many people know that this caused bootloops after a while in theme manager.