Hello, since Lineage OS came officially to Redmi Note 7 a couple of days ago, I've decided to install it. I was previously on Pixel Experience so this was the first time I was installing the gapps as well.
The installation of Lineage OS went fine but everytime I try reboot into the system after the installation of gapps, the phone is always booting again into recovery.
How can I solve this?
Thanks for the attention ?
Edit: everytime I try to setup my account the ui/ android configuration crashes and I can´t setup my account. I am currently using the arm64 stock version for android 10 and Lineage OS 17.1
Which gapps? U mount system, vendor and data before? Or better mount all before. Flash your rom, boot the system, boot in the recovery and flash the gapps package.
joke19 said:
Which gapps? U mount system, vendor and data before? Or better mount all before. Flash your rom, boot the system, boot in the recovery and flash the gapps package.
Click to expand...
Click to collapse
It worked thanks! I was flashing the rom, flashing the stock gapps and then boot into the system.
joke19 said:
Which gapps? U mount system, vendor and data before? Or better mount all before. Flash your rom, boot the system, boot in the recovery and flash the gapps package.
Click to expand...
Click to collapse
Now I can boot up the system but when I try to steup my google account the whole thing crashes. It says "Setup Wizard has stopped working" . I am trying to install the arm64 stock version for android 10 and Lineage OS 17.1. Do you know what can I do to solve this problem?
nokuteshimo said:
Now I can boot up the system but when I try to steup my google account the whole thing crashes. It says "Setup Wizard has stopped working" . I am trying to install the arm64 stock version for android 10 and Lineage OS 17.1. Do you know what can I do to solve this problem?
Click to expand...
Click to collapse
Opengapps stock? Test another gapps builder like bitgapps or nikgapps.
joke19 said:
Opengapps stock? Test another gapps builder like bitgapps or nikgapps.
Click to expand...
Click to collapse
It worked with bitgapps. Thank you for the help!
Related
Hi, i have on my N7-2012 TWRP 3.0.2.
I did Advanced Wipe for all partitions, and Format Data. I changed /data and /cache to f2fs and flashed a Nougat ROM from this form (DirtyUnicorn) I had no troubles.
I wiped system again (to avoid space problems during the flash of Gapps) and tried to flash GApps 'open_gapps_arm7.0-micro-20161018.zip', but i got this error:
*** Incompatible Android ROM detected ***
This GApp pkg is for Android 7.0.x ONLY
Please download the correct version for
your ROM: 5.1.1 (SDK 22)
*** GApps intallation failed ***
- Copying log to /usb-otg/Nexus 7 Asus
- NO changes were made to your device
Install will now exit...
Error code: 20
- Unmounting
I tried with other nougat ROM such as Carbon but i got the same error. The weirdness is that i tried also with a MM rom, and tried to flash GApps for MM... again, same error! He ask for a 5.1.1 GApps! So strange.
So, only for my curiosity, i reflashed DU ROm, downloaded and flashed GApps for 5.1.1. First time, i got the error:
*** Incompatible Android ROM detected ***
This GApp pkg is for Android 5.1.1 ONLY
Please download the correct version for
your ROM: 7.0.0 (SDK 22)
*** GApps intallation failed ***
i tried again and flash worked, i rebooted the device and..... bootloop... obviously.
Can you help me?
UPDATE: i forget to say that i tried also with: nano and pico gapps, and Banks Gapps. Same problem. if i reboot the device without gapps the rom work but if i download apk play store and install it doesn't work when i open it.
pls, noone can help me? :crying:
qwerweteryu said:
Hi, i have on my N7-2012 TWRP 3.0.2.
I did Advanced Wipe for all partitions, and Format Data. I changed /data and /cache to f2fs and flashed a Nougat ROM from this form (DirtyUnicorn) I had no troubles.
I wiped system again (to avoid space problems during the flash of Gapps) and tried to flash GApps 'open_gapps_arm7.0-micro-20161018.zip', but i got this error:
Click to expand...
Click to collapse
Are you wiping "system" after installing the ROM? If so, you are effectively removing the ROM you just installed which leaves the GAPPS script nothing to detect to install. The proper install would be: Flash ROM and the Flash Gapps (usually pico or nano to save space) and then reboot, no wiping in between.
I had this issue no matter what rom I tried after flashing an android 7.0 rom. I just did a factory reset by flashing back to a factory image now everything seems fine and google apps are working again.
I followed this guide http://forum.xda-developers.com/showthread.php?t=1907796 but used kit kat 4.4.4 image and didn't lock the boot loader. Then flash the recovery of your choice again and your good to go.
jbaumert said:
Are you wiping "system" after installing the ROM? If so, you are effectively removing the ROM you just installed which leaves the GAPPS script nothing to detect to install. The proper install would be: Flash ROM and the Flash Gapps (usually pico or nano to save space) and then reboot, no wiping in between.
Click to expand...
Click to collapse
Yes i wiped /system cause after the flash of the ROM when i try to install GApps i get error "not enough space". I followed the tips of a xda GUIDE wiping /system
@dinotyped: Are you telling me that there's no way to have Nougat on my N7? :crying::crying:
@qwerweteryu You should be able to use Nougat roms ok. I've not tried again. I'll likely stick to marshmallow for the time being just because of personal preference.
qwerweteryu said:
Yes i wiped /system cause after the flash of the ROM when i try to install GApps i get error "not enough space". I followed the tips of a xda GUIDE wiping /system
@dinotyped: Are you telling me that there's no way to have Nougat on my N7? :crying::crying:
Click to expand...
Click to collapse
Stick with "Pico" (or possibly) "Nano" Gapps to make sure you have enough space after flashing the ROM. You can always go back after booting / setting up and install the other Google Apps that you want.
jbaumert said:
Stick with "Pico" (or possibly) "Nano" Gapps to make sure you have enough space after flashing the ROM. You can always go back after booting / setting up and install the other Google Apps that you want.
Click to expand...
Click to collapse
omg! I did it! Thanks a lot!!
I recently flashed my ROM to Resurrection remix named RR-N-v5.8.5-20170925-a6000-Final and installed gapps named open_gapps-arm-6.0-stock-20171022 then I installed some apps from play store. SOme apps like Backdrops after installation makes my phone to restart and whet it boots up it shows "google has stopped responding " also "process system is not responding" and then is restarts again. I tried reflashing several times but nothing seems to work.
1. Wipe Art/cache system, data, internal
2. Install HEX Firmware
3. Install 5.8.5 RR
4. Install arm 7.1 pico gapps
5. wipe cache and reboot.
Rom take some time to Battery Collaboration and Performance.
so keep patience and enjoy.
rkunaal said:
1. Wipe Art/cache system, data, internal
2. Install HEX Firmware
3. Install 5.8.5 RR
4. Install arm 7.1 pico gapps
5. wipe cache and reboot.
Rom take some time to Battery Collaboration and Performance.
so keep patience and enjoy.
Click to expand...
Click to collapse
How can I install the firmware?
The link of hex firmware is in RR thread. And you flashed marshmallow gapps on a nougat rom. Flash arm 7.1 gapps.
ameyab97 said:
The link of hex firmware is in RR thread. And you flashed marshmallow gapps on a nougat rom. Flash arm 7.1 gapps.
Click to expand...
Click to collapse
Still the same problem
I think the problem is with new playstore every time I download certain apps it crashes.
raunak51299 said:
How can I install the firmware?
Click to expand...
Click to collapse
http://berbagikoleksi.blogspot.in/2015/06/solusi-lenovo-a6000-bootloop-gagal-flash.html?m=1
Sent from my Redmi Note 4 using Tapatalk
raunak51299 said:
I recently flashed my ROM to Resurrection remix named RR-N-v5.8.5-20170925-a6000-Final and installed gapps named open_gapps-arm-6.0-stock-20171022 then I installed some apps from play store. SOme apps like Backdrops after installation makes my phone to restart and whet it boots up it shows "google has stopped responding " also "process system is not responding" and then is restarts again. I tried reflashing several times but nothing seems to work.
Click to expand...
Click to collapse
First, I would like you to know that you DID NOT follow the instructions correctly. INSTRUCTIONS said, you will flash Opengapps 7.1.X ARM not 6.0 Marshmallow. Links were already given but still you did not follow.
Download the correct gapps package - ARM > 7.1 > Pico.
Code:
http://opengapps.org
Dirty flash it but if there's still an issue, you can clean install your RR 5.8.5 Final again and flash the gapps 7.1.
Good luck!
Hi you there,
I start this thread because I´m having some issues installing 8.0 and 8.1 Oreo Roms, every of them have the same problems when I try to install them in my device (REDMI 3X). Actually, I have install and running Resurrection Remix Nougat + Gapps Micro, and it works fine.
When I try to install some Oreo Rom, I have these 2 possible options:
1 - I install rom + gapps (no matter which one, cause I tried each one): phone restarts and stucks at logo and after maybe 30 minutes I must restart it manually and reinstall a nougat rom. It never starts, and it is f...ng annoying.
2 - I install rom, afterwards, I restart and it works fine, but I have no gapps. The I boot into recovery and after gapps are installed I restart the phone, then gapps never work.
Please, I just get 2 times an oreo rom working, but now they never work, I don´t know whta to do. I also tried different recoveries, flashing them from PC, installing them from .img with TWRP, nothing seems to work. As I said: F...NG ANNOYING. I need heeeeeeeeeeeeeeeeelp
I think I am not the only one with this problem, if anyone can help I will appreciate that.
Thansk in advance.
First of all, this should be in the Q&A section. Secondly, I can help you. I'm sure that you downloaded the gapps from the cloudkenzo something, right? Yeah those gapps do not have any issues, instead they make an issue. After flashing your rom and then these gapps file, the system partition normally unmounts. But usually when you boot into the ROM, the partition should re-mount. These unofficial gapps causes some issues with that. A simple solution- Just mount system in twrp, now reboot to system and you should be fine. I faced the same issue and this is my solution.
alopez_666 said:
Hi you there,
I start this thread because I´m having some issues installing 8.0 and 8.1 Oreo Roms, every of them have the same problems when I try to install them in my device (REDMI 3X). Actually, I have install and running Resurrection Remix Nougat + Gapps Micro, and it works fine.
When I try to install some Oreo Rom, I have these 2 possible options:
1 - I install rom + gapps (no matter which one, cause I tried each one): phone restarts and stucks at logo and after maybe 30 minutes I must restart it manually and reinstall a nougat rom. It never starts, and it is f...ng annoying.
2 - I install rom, afterwards, I restart and it works fine, but I have no gapps. The I boot into recovery and after gapps are installed I restart the phone, then gapps never work.
Please, I just get 2 times an oreo rom working, but now they never work, I don´t know whta to do. I also tried different recoveries, flashing them from PC, installing them from .img with TWRP, nothing seems to work. As I said: F...NG ANNOYING. I need heeeeeeeeeeeeeeeeelp
I think I am not the only one with this problem, if anyone can help I will appreciate that.
Thansk in advance.
Click to expand...
Click to collapse
Make sure using the latest twrp.
If u already have the latest twrp then the problem is in gapps, use gapps for oreo 8.1, maybe there is posted in ur rom thread
F4nno said:
Make sure using the latest twrp.
If u already have the latest twrp then the problem is in gapps, use gapps for oreo 8.1, maybe there is posted in ur rom thread
Click to expand...
Click to collapse
I already tried, it did not work, I have installed last gapps 8.1, last twrp, last everything and it never works, it keeps stucking again and again.
same ****ty problem with my 3s 2gb .. doesnt matter which oreo 8.1 rom i flash.. tried almost 4 oreo 8.1 roms.. all couldnt boot.. and if by chance it boots then cant add google account..
yet to try that 'Mount' thing solution suggested by Williams
You ask in wrong place stupid!
Ask in Q&A section stupid!
This section jus for downloading rom and kernel stupid!
I face the same issue with a Redmi 3 S (global version) with 3 GB RAM. Nougat ROM's are fine but all Oreo ROM's which I tried (most recent builds of PixelExperience, crDroid, Atomic-OS) show these boot loops. This is all with the latest TWRP installed (also tried custom builds), cleaned properly my device and was using the linked Oreo GAPPS. I usually flash in one instance 1) ROM, 2) GAPPS and 3) Magisk.
The only time I had a working Oreo ROM was after several tries with PixelExperience where on my last try I booted into safe mode and it somehow worked after that.
AidANiem said:
You ask in wrong place stupid!
Ask in Q&A section stupid!
This section jus for downloading rom and kernel stupid!
Click to expand...
Click to collapse
go **** your mother, she likes it
william.johhn7! said:
First of all, this should be in the Q&A section. Secondly, I can help you. I'm sure that you downloaded the gapps from the cloudkenzo something, right? Yeah those gapps do not have any issues, instead they make an issue. After flashing your rom and then these gapps file, the system partition normally unmounts. But usually when you boot into the ROM, the partition should re-mount. These unofficial gapps causes some issues with that. A simple solution- Just mount system in twrp, now reboot to system and you should be fine. I faced the same issue and this is my solution.
Click to expand...
Click to collapse
Thanks, it worked for me:
1 - full wipe and format
2 - install rom
3 - install gapps
4 - mount system
5 - reboot system
Download :
https://download.mokeedev.com/dragon.html
Installation:
1 - Boot into TWRP
2 - Wipe system, cache, dalvik and data partitions
3 - Sideload MK100.0-dragon-201912190517-NIGHTLY.zip
4 - Install Opengapps
5 - install Magisk.zip (Optional)
6 - Reboot into system
Thanks. Been meaning to try this.
Problem with getting magisk to install as "system-as-root"
I've tried the unmount/mount system partition
(Update) Also tried manually install of magisk/root/boot.img
And hints?
jamesthedisciple said:
Thanks. Been meaning to try this.
Problem with getting magisk to install as "system-as-root"
I've tried the unmount/mount system partition
(Update) Also tried manually install of magisk/root/boot.img
And hints?
Click to expand...
Click to collapse
Which version of TWRP are you using?
jamesthedisciple said:
Thanks. Been meaning to try this.
Problem with getting magisk to install as "system-as-root"
I've tried the unmount/mount system partition
(Update) Also tried manually install of magisk/root/boot.img
And hints?
Click to expand...
Click to collapse
Same problem here latest builds will not stay rooted using twrp-3.3.1-0
Also if you flash this Rom you should be aware it forces encryption, so not easy to move to another rom afterwards.
Twrp 3.3.1-0.
Root doesn't hold for Lineage 17 or asop10r9 either.
Not worried about encryption for the moment, tend to format data anyway until i can find a longtem "10".
When I have time I'll dive a little deeper. I have a twrp 3.3.1-2 to try out!
Root holds just fine on both below roms
[ROM][OFFICIAL][LineageOS][dragon] - [Lineage/17.0] -> 20191220
[ROM][UNOFFICIAL][PixelExperience][Ten/10.0][dragon] -> 2019/12/12]
I'm running PixelExperience and its solid everything's working good
Markeee said:
Root holds just fine on both below roms
[ROM][OFFICIAL][LineageOS][dragon] - [Lineage/17.0] -> 20191220
[ROM][UNOFFICIAL][PixelExperience][Ten/10.0][dragon] -> 2019/12/12]
I'm running PixelExperience and its solid everything's working good
Click to expand...
Click to collapse
That's good. Was that in twrp, unmount system, mount system, install magisk?
jamesthedisciple said:
That's good. Was that in twrp, unmount system, mount system, install magisk?
Click to expand...
Click to collapse
I didn't even bother with any of the unmount or mount options just formatted but I'm pretty sure just normal wipe will work also flashed PixelExperience then flashed latest Magisk-v20.1 in Twrp 3.3.1-0 no need to install OpenGApps its included in the PixelExperience Rom
Root works normally no issues
Markeee said:
I didn't even bother with any of the unmount or mount options just formatted but I'm pretty sure just normal wipe will work also flashed PixelExperience then flashed latest Magisk-v20.1 in Twrp 3.3.1-0 no need to install OpenGApps its included in the PixelExperience Rom
Root works normally no issues
Click to expand...
Click to collapse
That makes life easier!
Was that the same for the latest Lineage 17?
I'm running a google free pixel C!
jamesthedisciple said:
That makes life easier!
Was that the same for the latest Lineage 17?
I'm running a google free pixel C!
Click to expand...
Click to collapse
I haven't tried the very latest Lineage 17 build but was running the previous build before that and they were close but not quite as stable as PixelExperience Rom
There was no problems with root but the camera wasn't working.
I think i read its fixed in the latest build
Markeee said:
I haven't tried the very latest Lineage 17 build but was running the previous build before that and they were close but not quite as stable as PixelExperience Rom
There was no problems with root but the camera wasn't working.
I think i read its fixed in the latest build
Click to expand...
Click to collapse
Thanks. I now have LO17 latest build and root has held. Looking good.
The donate function is an error
The unique code is alway change when I change my Wifi. This problem make the tablet error. I cannot contract to the manager of Mokee because he uses Weibo
I used to have mokee on my moto x 2104 and this is the reason I will not use mokee without root. Here is a good explaination and a way to get round the problem of "mokee phone home". This works in mokee 9.
https://forum.xda-developers.com/moto-x-2014/general/opinion-x2-oreo-roms-fixes-roundup-t3809622
I have installed this ROM and everything works fine so far. The ads are okay since it is a free service. I can live with it. But one little suggestion for the developer: since this ROM is updated on a nightly basis, could you let us know the changes of each update? No details are necessary, just a couple words would be enough.
Thanks for keeping the development for Pixel C.
Problem with encryption
After installation I have the tablet with data encrypted and I can't use it!
How can I solve?
I use twrp 3.3.1-0
francoscala said:
After installation I have the tablet with data encrypted and I can't use it!
How can I solve?
I use twrp 3.3.1-0
Click to expand...
Click to collapse
Me too.
I use official version twrp-3.3.1-1-dragon.img
Grigori88 said:
Me too.
I use official version twrp-3.3.1-1-dragon.img
Click to expand...
Click to collapse
Do you have a problem with TWRP and decryption?
I been running this rom for a couple of months already theirs been a nightly update every single day rom is solid
The only issues I have is on reboots sometimes the rom gets hang at Google boot screen and the rom fails Safetynet Check ctsProfile in Magisk
Anyone alive in this thread I been running this rom since Dec updating it everyday but I can't seem to get today's 3/13/2020 build to boot past the Google screen any suggestions ?
Okay so I've tried Pixel experience, lineage os , omni rom treskmod and couple of other custom android 10 roms, all stable and official and also updated ones, the wifi just simply doesn't work, wifi hotspot won't turn on either. I've tried every solution on the internet. I've even factory reset my phone using msm download tool and no luck(did this countless times).
I'm back in OOS 10.3.2 and there's no issue apparently.
At one point , i flashed a custom rom and the wifi didn't work, so I flashed OOS in the two slots and checked , the wifi works in OOS apparently, and never in custom roms.
Has anyone got this issue before and knows a solution?
How is your installation procedure?
onliner said:
How is your installation procedure?
Click to expand...
Click to collapse
I flash OOS and twrp on both slots, reboot recovery,
And then flash the rom and twrp, reboot recovery,then format data and factory reset, reboot recovery, if needed for some gapps, then reboot system
ivanthomas said:
I flash OOS and twrp on both slots, reboot recovery,
And then flash the rom and twrp, reboot recovery,then format data and factory reset, reboot recovery, if needed for some gapps, then reboot system
Click to expand...
Click to collapse
That's a lot of unnecessary steps. OOS on both slots, reboot to bootloader, boot twrp, format data and flash the custom rom, reboot bootloader, boot twrp and flash gapps, don't install twrp permanently if you are not going to install Magisk.
onliner said:
That's a lot of unnecessary steps. OOS on both slots, reboot to bootloader, boot twrp, format data and flash the custom rom, reboot bootloader, boot twrp and flash gapps, don't install twrp permanently if you are not going to install Magisk.
Click to expand...
Click to collapse
I need magisk too, I usually permanently install twrp
Also you think it's the way I'm installing at fault here? Or the rom? Or is it something wrong with my device?
ivanthomas said:
it's the way I'm installing at fault here?
Click to expand...
Click to collapse
This.
I always install roms with the procedure i said above and have never had any problems.
onliner said:
This.
I always install roms with the procedure i said above and have never had any problems.
Click to expand...
Click to collapse
Alright so got one doubt, I used OOS 10.3.2 to flash, should it be oos 10.0 only?
Thought that didn't make a difference.
I am also facing the same issue. Were you able to find any solution ?
So I found out treskmod omni rom and Paranoid android quartz 2 work perfectly , try those out, it still doesn't solve the problem in the other roms though. So not exactly a solution.