So, I just flashed AOSP-CAF on my Mi 4i to bypass the xiaomi lock. I flashed opengapps nano 6.0 because AOSP-CAF is 6.0.1. When i booted the system, it was stuck at Please Wait. I can't login to my Google account. Also, I don't know what SuperSU I should flash. Please help.
edit: the google apps/system ui keep crashing
edit: i fixed it, its all good.
Related
Hey guys, i have a samsung s5 australian edition (kltedv) thats been running cm14.1 for some time. Anyway, found a few bugs blah blah, decided it was time to flash Lineage OS onto my phone. Used their funky experiment dirty install technique, and upon restarting im bombarded with "google play services keeps stopping" messages, too many of them to even navigate the phone. So i thought, screw it, and I factory reseted the phone, wiped /system with TWRP, and clean installed Lineage OS with the latest OpenGAPPS 7.1 nougat micro. Upon reboot, BAM! instant google frameworks keeps stopping. Cant even set up my account. So i use an older version of 7.1 OpenGAPPS. same problem. wipe /sytem again and clean install resurrection remix OS with OpenGAPPS.
Im at my wits end, is there any sneaky tips to installing these nougat roms? Older CM14.1 roms were working fine, nothing new is.
EX250 said:
Hey guys, i have a samsung s5 australian edition (kltedv) thats been running cm14.1 for some time. Anyway, found a few bugs blah blah, decided it was time to flash Lineage OS onto my phone. Used their funky experiment dirty install technique, and upon restarting im bombarded with "google play services keeps stopping" messages, too many of them to even navigate the phone. So i thought, screw it, and I factory reseted the phone, wiped /system with TWRP, and clean installed Lineage OS with the latest OpenGAPPS 7.1 nougat micro. Upon reboot, BAM! instant google frameworks keeps stopping. Cant even set up my account. So i use an older version of 7.1 OpenGAPPS. same problem. wipe /sytem again and clean install resurrection remix OS with OpenGAPPS.
Im at my wits end, is there any sneaky tips to installing these nougat roms? Older CM14.1 roms were working fine, nothing new is.
Click to expand...
Click to collapse
Hello and welcome to XDA-developers!
The correct steps to do a clean install of LineageOS or any other custom ROM are:
1. Factory Reset
2. Wipe System, Data, Cache/Dalvik/Art
3. Flash ROM
4. Flash Gapps (Optional)
5. Reboot
Hi, someone can help me with dualboot patcher???
my actual configuration is: Xiaomi Mi5s Plus (6/128), Twrp Official 3.1.0-1, Miui 8 7.4.20 (global beta), systemless supersu 2.79-SR3 + magisk v11.1 .
I wiped cache, dalvik, system, data, then i flash miui global beta, and then i patched a lot of build of lineage and resurrection remix.
The patching process ends with no errors. When i try to install patched rom into Data Slot i have error. I try to flash from twrp and from the app itself, but i have error in real-update script. Where is my error?
Help
I cant flash roms that dual boot patcher patched them
Same problem, maybe its impossible to get it working. I don't know why. Maybe the kernel doesn't love the patcher or idk. But i tried a lot of time for nothing.
I have the following installed:
[url]https://forum.xda-developers.com/oneplus-one/development/8-0-0r3-lineageos-15-0-t3670670[/URL]
Android: LineageOS 15.1 (8.1.0_r4) with latest magisk installed (15.3) with unofficial opengapps 8.1 mini package
When I try to downgrade to either Lineage 14.1 official or carbonrom 5.1 I am getting a boot loop at the oneplus logo. Restoring from backup to 8.1 resolves the issue.
1. factory reset
2. wipe system
3. Install Lineage 14.1 or carbonrom 5.1
4. Install recent opengapps mini package for 7.1.2
4. Reboot
The phone boot loops at the oneplus logo and I end up restoring from backup.
I have looked online and was struggling to find anything relevant. Some people report a new battery solved the issue but since It works when I restore from the backup It doesn't seem to be that. I do have a new battery on hand that I am eventually going to install though so I can do that.
Apologies if I am missing something obvious.
-Snowrider- said:
I have the following installed:
https://forum.xda-developers.com/oneplus-one/development/8-0-0r3-lineageos-15-0-t3670670
Android: LineageOS 15.1 (8.1.0_r4) with latest magisk installed (15.3) with unofficial opengapps 8.1 mini package
When I try to downgrade to either Lineage 14.1 official or carbonrom 5.1 I am getting a boot loop at the oneplus logo. Restoring from backup to 8.1 resolves the issue.
1. factory reset
2. wipe system
3. Install Lineage 14.1 or carbonrom 5.1
4. Install recent opengapps mini package for 7.1.2
4. Reboot
The phone boot loops at the oneplus logo and I end up restoring from backup.
I have looked online and was struggling to find anything relevant. Some people report a new battery solved the issue but since It works when I restore from the backup It doesn't seem to be that. I do have a new battery on hand that I am eventually going to install though so I can do that.
Apologies if I am missing something obvious.
Click to expand...
Click to collapse
Try the following :
-uninstall magisk using uninstaller(available in magisk forum)
-clear system,data,cache,dalvik
-install only the rom with out gapps
if it boots properly then you can install the gapps later or else if u find flashing gapps is causing the bootloop then use an older version and double check the compatibility.
if still not just try out another nougat rom
Thanks for the suggestion.
I tried your steps with the latest stable slimrom 7.1.2, lineage 14.1 and carbonrom 5.1 and I am still seeing the same issue. I was able to clean install the lineage 15.1 beta I linked to though in addition to restoring my backup as I have done before. I might try to clean install a different 8.1 (AOSP for example) and see if that one works. This will help narrow down if the issue is caused by 8.1 in general or specifically something that the lineage 15.1 beta has done.
I had a similar problem when I flashed Sultan's LOS14.1. I fixed it by flashing down to stock using wugfresh's bacon root toolkit. Keep in mind though that this will wipe EVERYTHING on your phone. Hope it doesn't come to that. Best of luck!
CedArctic said:
I had a similar problem when I flashed Sultan's LOS14.1. I fixed it by flashing down to stock using wugfresh's bacon root toolkit. Keep in mind though that this will wipe EVERYTHING on your phone. Hope it doesn't come to that. Best of luck!
Click to expand...
Click to collapse
This is what I ended up doing and it did the trick. Thank you for the suggestion.
So, I just installed Google Pay and wanted to connect it with my PayPal account. Everything was going fine until I finished the setup - the app showed me a message saying "Setup for paying in stores could not be finished - This smartphone can not be used to pay with in stores. This can be due to your phone being rooted or changed otherwise."
I have a completely vanilla LineageOS 15.1 (latest build) installed. No Magisk or Xposed. So this might be because I installed a custom ROM.
I will keep this thread updated - I will try to install the latest build of LineageOS 16, then if it does not work, continue to flash the latest stock ROM.
Flashed LineageOS 16, got the same issue. Flashed stock ROM now and hopefully it will work.
DKXC said:
Flashed LineageOS 16, got the same issue. Flashed stock ROM now and hopefully it will work.
Click to expand...
Click to collapse
Lineage builds for Samsung have that issue. They struggle to pass SafetyNet even if its not rooted. I'm running stock + Magisk and have Snapchat, Fortnite, Google Pay, and Pokemon Go all working no problem. Sac23's s9 port also has a good SafetyNet, just make sure to not use the Magisk included in the Aroma installer and use the latest zip
I've tried LineageOS 15 with Magisk. Google Pay works, but does not allow fingerprint use, only PIN/pattern. Same with WellsFargo app. It appears that something is incomplete or incorrect on the Samsung port of Lineage. Stock roms with Magisk do not have this issue.
So what's the best way to get android pay working? Just install Stock ROM and use Magisk to root?
Hey everyone,
i usually don't post questions but i've been on pretty much every forum the web has to offer and am still stuck so i'll try my luck here.
i'm currently running lineage 7.1 on my mi4c, i've used another phone for a while but now that my mi4c has a new battery i wanted to start using it again, is also decided this would be the time to update it to android oreo or pie, this however seems to be impossible.
i can only use twrp up to 3.1.1.1, all higher (and unofficial versions) will not boot via fastboot 'dtb not found' or when flashed via older twrp will freeze on boot screen.
whenever i try to install a new rom it tells me 'error code 7', when i remove the 'assert' lines in the update it gives me 'error code 6'
my device is unlocked, i have checked this in fastboot.
do i have to install miui again before installing another rom? do i have to go back to the standard recovery? i'm currently running out of ideas and hope you guys might be able to help me. maybe i'm overlooking something simple.
kind regards,
Monstreys
Hi! I don't know if this is a coincidence or not, but I was about to start a similar thread.
I try to do exactly what you are doing. I want to install LineageOS 16, unofficial ROM.
For this you need a newer TWRP, like 3.2.3.0, but it doesn't work 'dtb not found' like you said. I found out that this doesn't work because you need to have nougat bootloader. Most probably you have lollipop bootloader like I have, and thats why newer versions of TWRP are not working. I think the only way to update your bootloader to a nougat one is to flash the latest MIUI ROM. But, unfortunately, when you do that the bootloader gets locked, and I can't unlock it via MiUnlock due to Error:20091 when I try to link the phone to the Mi account. In MiUnlock it gives me the "this account cannot unlock the phone" or something like that.
Now I removed the "assert" lines from my rom and flashed it without the error 7 or 6. Some error still apears, but it also apears when I flash LineageOS 14.1, and that version is working even with those 2 errors I can't remember during flash.
After I flashed LineageOS, I flashed gapps and then superSU, and now my mi4c is stuck on mi logo for about 20 minutes, and I think it will remain that way.
So, there are 2 things we need to solve. We need to find a way to install latest MIUI without relocking the bootloader because I can't unlock it via MiUnlock, or to find out why after I flashed LineageOS 16 it gets stuck on MI logo.
I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...
makaveli97 said:
I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...
Click to expand...
Click to collapse
i
i was unable to install the patch file, this nonetheless fixed my problem, thanks!!
if above not working, another method to do it based on my method.
https://forum.xda-developers.com/showpost.php?p=81573941&postcount=199
makaveli97 said:
I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...
Click to expand...
Click to collapse
My MI4C has been successfully flushed into lineage-17.1-20200220-UNOFFICIAL-libra.zip. It has been updated on TWRP 3.1.1 and keeps reporting error 7, and then abandoned TWRP3.1.1 and flashed into OrangeFox-R10.0-1-Stable-libra.zip After brushing libra-aqua_firmware_7.2.9.zip on this REC, you can flash lineage-17.1. I do n’t think it will be impossible to refresh because of partition problems. If you only need to upgrade lineage-17.1, you can refer to this method.:good::good:（Translation is not easy to use）
celrau said:
There is a 3.2.x around. If you don't want to bother go in the zip, /META-INF/com/google/android/ and delete the first lines (the ones starting with "assert") from updater-script, save and flash again.
Click to expand...
Click to collapse
rianawirawan said:
Right now, i'm using 3.1.1 -1 btw
It's latest twrp ver from official
Click to expand...
Click to collapse
TWRP-20190418-3.3.0.0-libra.img for the Xiaomi Mi 4c, by GuaiYiHu :
https://androidfilehost.com/?fid=1395089523397945946
Latest firmware for the Xiaomi Mi 4c libra :
https://github.com/XiaomiFirmwareUp...iui_MI4c_V10.1.1.0.NXKCNFI_13b9b312d0_7.0.zip