Database Users

Not able to run 6.0 based ROMs

Hi all,
I try to run a 6.0 based ROM, but when I first boot the phone after an install the phone reboots after half a minute. It looks like it boots normally, but after entering language and other settings (or also when skipping all) the phone reboots and the process starts over again.
I tried to install factory ROM via ADB, this doesn't give any errors while installing.
The same happens when I try another ROM like CM 13.
Only stable ROM for me is CM12, all other ROMS give reboot.
Any suggestions? Am I installing the wrong ROMs? I have a XT1562, run Squid kernel and latest TWRP.

knielen said:
Hi all,
I try to run a 6.0 based ROM, but when I first boot the phone after an install the phone reboots after half a minute. It looks like it boots normally, but after entering language and other settings (or also when skipping all) the phone reboots and the process starts over again.
I tried to install factory ROM via ADB, this doesn't give any errors while installing.
The same happens when I try another ROM like CM 13.
Only stable ROM for me is CM12, all other ROMS give reboot.
Any suggestions? Am I installing the wrong ROMs? I have a XT1562, run Squid kernel and latest TWRP.
Click to expand...
Click to collapse
You tried tesla rom. Also first just flash the rom and boot. Once it successfully boots up, go ahead with gapps.

Thanks for your answer, it indeed is caused by the Gapps package. When I install a ROM without Gapps, everything works fine. Trying to find a compatible Gapps package now.

K.khiladi said:
You tried tesla rom. Also first just flash the rom and boot. Once it successfully boots up, go ahead with gapps.
Click to expand...
Click to collapse
knielen said:
Thanks for your answer, it indeed is caused by the Gapps package. When I install a ROM without Gapps, everything works fine. Trying to find a compatible Gapps package now.
Click to expand...
Click to collapse
As far as i remember, ever since MM, it's recommended to flash both the ROM and GAPPS together.

varounmirchi said:
As far as i remember, ever since MM, it's recommended to flash both the ROM and GAPPS together.
Click to expand...
Click to collapse
Only 6.0 rom I found that works is DU with Banks Gapps, and yes, had to install them at the same time.
This rom is a battery drain and has gps fix issues for me, not sure if I stay with this rom or go back to CM 12
Sent from my du_lux using XDA-Developers mobile app

varounmirchi said:
As far as i remember, ever since MM, it's recommended to flash both the ROM and GAPPS together.
Click to expand...
Click to collapse
Nope, there's no such requirement. I have just flashed the rom first cause sometimes the Gapps cause stability issues.
Automated reply by JARVIS

Bootloop after first restart with multiple CFWs!

Hi guys,
I have the standard note III 9005 and I had always installed CFWs on it.
I wanted to update to newer 6.0.1 Roms (had 6 roms before) but I seem to have a VERY annoying bug:
I tried to install Temaseks rom and resurrection rom but I had huge issues with it. I got bootloops although I got the newest 3.0.2.0 Team Win Recovery Project
I installed rom, GAPPS (correct version of course 6.0.1) , install rom again then delete cache and then it worked on both roms.
So a simple "install rom, GAPPS, then clean cache" didnt work. I tried to install multiple times until I got the installation! YAY! BUUUT!
Here is the fun part:
If I restarted the phone acidentally or on purpose I got stuck in a bootloop. After that the phone was unuseable again so the installation was useless.
Only solution is to completely wipe and reinstall and experiment with the order of installation until it works!
I did install STOCK rom because I was so freaked out and then went with ODIN the complete rooting guide for clean rooting, but still problem exists.
I tried two other roms but the problem was that while flashing the phone restarted automaticly and then TWRP said no installed rom? ???
Huge thanks for helping me!

New info:
I was able to make the rom work. I restarted and got stuck into bootloop!
I could boot normally after deleting dalvik cache!
But after rebooting I got into bootloop. Tried deleting cache again but this time it never booted properly.
How can I avoid by always deleting dalvik whenever I have to restart my phone (if battery dies or purpose)?
PPS: Stock Rom flash works flavlessly. I am waiting in stock rom until I find a proper solution :"(

Suggest you read the roms faqs and Q&A particularly with regard to TWRP .

Flashed CM13, Cannot find Gapps package that works, help?

Hey everyone, I rooted my phone, unlocked the bootloader, flashed TWRP, and then flashed CyanogenMod 13 (Marshmallow). Everything worked perfectly, so I went back into my recovery to flash Gapps. I've tried Open Gapps and Slim Gapps, but both repeatedly crash setup wizard and clock among other things.
If anyone could help, I'd really appreciate it.

trent4071 said:
Hey everyone, I rooted my phone, unlocked the bootloader, flashed TWRP, and then flashed CyanogenMod 13 (Marshmallow). Everything worked perfectly, so I went back into my recovery to flash Gapps. I've tried Open Gapps and Slim Gapps, but both repeatedly crash setup wizard and clock among other things.
If anyone could help, I'd really appreciate it.
Click to expand...
Click to collapse
Same here I tried it, and it did the same for me also...
Sent from my SM-N920F using Tapatalk

These are the Gapps that worked for me
http://forum.xda-developers.com/slimroms/general/gapps-official-slim-gapps-trds-slimkat-t2792842

Thank you for the help wikked26, but it didn't work. Those Gapps still crash for me. I think it's something incorrect in the way my phone is configured, not a case of downloading the wrong Gapps.
If anyone has any other ideas, please share them! I haven't cracked the case just yet

I know I was having issues with the Slimroms version where I booted into CM and set it up before installing Gapps. Fixed it by reinstalling/wiping the cache and installing Gapps before booting anything. Don't know if that helps, but I'm running fine now.

I'm hoping this is similar to the issue I'm having. Do you get it where you can factory reset in TWRP, then flash CM13, but when you go to flash Slim Gapps? Because I figured out that after factory resetting TWRP will only successfully flash 1 zip file. I also tried to wipe the cacher, dalvik, data, and system, then flash cm13 but Gapps still wouldn't flash. Maybe its a bug with TWRP 3.0.2? I'm going to try to use a different version of TWRP and I'll update with my results
EDIT: TWRP 2.8.5 did not do anything different

Wow, thanks for all the great responses. I made sure to try and install CM13 and Gapps at the same time, before boot, after wiping everything one last time. It worked flawlessly, and I can now use Google Play Services.
I hope this thread helps anyone else who is also a little stuck. I also found that TWRP didn't have any issues flashing multiple zips at the same time, not sure whats going on with you, Orange Officer. Perhaps try removing your battery after CM13 flashes, and then boot into TWRP again and flash Gapps without booting up CM13 at all?

Oreo 8.0 8.1 installing issues

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

I have tried many ROMs for my A2017U, but non of them works well

First, I unlocked bootloader and installed twrp with axon7toolkit.
Then I have tried following roms.
1. AospExtended-v5.4-axon7-20180421-0700:
no sound when calling, /data does not shown, crashes when voice call from wechat.
2. BootleggersROM-Oreo4axon7.2.1-Stable-Unshishufied-20180331:
no sound when calling, have not test other
3. dotOS-O-v2.1-axon7-UNOFFICIAL-20180404
(downloaded but not tested)
4. A2017(U)(N-B35)_AROMA_SL!M1_DF!NR_by_raystef66
always crashes before I can finish initial setup
5.lineage-14.1-20180425-nightly-axon7-signed
password needed to start android, but I do not know what is the pass word
6. A2017Uv1.1.0B35_StockSystem_by_DrakenFX
this is the only one which calling works, wechat voice call works.
Rooted with Magisk16.0.
Problems with original ROM still exist:
1. battery drain pretty fast,
2. show 31000 and roaming for verizon.
New problem after unlock bootloader,
bootloader unlocked warning when startup
new problem after root:
crashes when start es file explorer:
testing others

The last resurrection remix(official nougat) is solid and so is AOKP. I'm just wondering what kernel would be best for a nougat Lineage-based rom on B35

thanks for reply.
I will temporally stay with stock rom B35. The unlocked bootloader warning is removed now.
The only two issues with stock rom are battery drain, verizon signal label.
I may give resurrection remix a try later.
Amer532 said:
The last resurrection remix(official nougat) is solid and so is AOKP. I'm just wondering what kernel would be best for a nougat Lineage-based rom on B35
Click to expand...
Click to collapse

Are you installing the bootstack too? I have the same model and don't have any of those issues. I run encryption so I'm stuck on the 2/24 build of AOSP-eXtended, but the only bug I have is a slow initial GPS lock. Otherwise it runs solid.
Sounds like you didn't follow all the directions.

I am sure I followed instructions strictly.
I have also tried to flash each ROM start from specified Bootloader, Modem, Bootstack, then ROM in the post.
TPMJB said:
Are you installing the bootstack too? I have the same model and don't have any of those issues. I run encryption so I'm stuck on the 2/24 build of AOSP-eXtended, but the only bug I have is a slow initial GPS lock. Otherwise it runs solid.
Sounds like you didn't follow all the directions.
Click to expand...
Click to collapse

llaalways said:
thanks for reply.
I will temporally stay with stock rom B35. The unlocked bootloader warning is removed now.
The only two issues with stock rom are battery drain, verizon signal label.
I may give resurrection remix a try later.
Click to expand...
Click to collapse
i'm pretty sure you're doing things wrong:
-No sound on calls is fixed by toggling speakerphone on and off
-Password on boot is because your internal storage is encrypted, because you installed a ROM and forgot to flash Magisk or SuperSU before booting for the first time.
-Everything crashing on slim roms can be because you failed to wipe. Anyways simply wipe evetrything and try flashing it again, it'll probably be fixed.
-5 second screen is not a problem, it's a feature. There are ways to fix that anyways: Remove unlocked bootloader inscription by Raystef66 should work, and it is safe. And also there's NFound's zip on the Themes and Apps section, but it'a very risky (you might end up having to unbrick your phone).

I'm running LineageOS 15.1 Oreo based room currently and all seems well except there seems to be no working camera. Ive tried many and no seem to work or install correctly no matter how I flash. I tried to go back to stock 35 but got stuck at boot screen for an extremely long time so I was force to pick another Oreo room to go back to in order for me to get my phone to work. Do you guys know of a working camera I can install that you have personally tried with Oreo and links would be helpful. I tried a lot on xda so far to no avail. Thanks in advance. Or link me to what I need to get back to stock 35. Also, LineageOS 15.1 has ridiculous battery life. In a good way.

King Ice said:
I'm running LineageOS 15.1 Oreo based room currently and all seems well except there seems to be no working camera. Ive tried many and no seem to work or install correctly no matter how I flash. I tried to go back to stock 35 but got stuck at boot screen for an extremely long time so I was force to pick another Oreo room to go back to in order for me to get my phone to work. Do you guys know of a working camera I can install that you have personally tried with Oreo and links would be helpful. I tried a lot on xda so far to no avail. Thanks in advance. Or link me to what I need to get back to stock 35. Also, LineageOS 15.1 has ridiculous battery life. In a good way.
Click to expand...
Click to collapse
Footej? Gcam? ZTE stock cam? Have you also tried AEX? I'm curious as to how it performs.

Victor13f said:
Footej? Gcam? ZTE stock cam? Have you also tried AEX? I'm curious as to how it performs.
Click to expand...
Click to collapse
I tried GCam but the rear camera didn't work. It's weird but that was the consensus that a lot of people was having. I heard that the ZTE Stock 13 v2 camera works but I haven't been able to find a link to anyone that actually has it. Everyone that I've come across has had a link, but when you get there it's for b04, 05, o7 Oreo or something else. I've tried those also and it hasn't work on LineageOS. I might go back to Nougat 7.1.1 if I can find the proper way to do so.

OK, I have resolved the problem with Password on boot.
I have tried many times, every time after flashed twrp, then I boot into twrp recovery, then do following steps:
1. advance wipe cache/dalvik cache/data/system,
2. install bootloader, modem, warning_patch, rom,
3. advance wipe cache/dalvik cache/data
4. install Magisk
5. advance wipe cache/dalvik cache/data
6. install Gapps
7. advance wipe cache/dalvik cache/data
then reboot to system, and the password is always asked on boot.
I have found out that instead of "advance wipe cache/dalvik cache/data", do a "factory reset" in twrp recovery, then the problem solved.
So the step should be
1. advance wipe cache/dalvik cache/data/system,
2. install bootloader, modem, warning_patch, rom, Gapps
3. install Magisk ( wipe cache/dalvik cache/data if fail to install, then install again)
4. factory reset.
After factory reset, boot into system and works.
There is still no sound on call problem, but fixed by toggling speakerphone on and off as you suggested.
Thanks.
Choose an username... said:
i'm pretty sure you're doing things wrong:
-No sound on calls is fixed by toggling speakerphone on and off
-Password on boot is because your internal storage is encrypted, because you installed a ROM and forgot to flash Magisk or SuperSU before booting for the first time.
-Everything crashing on slim roms can be because you failed to wipe. Anyways simply wipe evetrything and try flashing it again, it'll probably be fixed.
-5 second screen is not a problem, it's a feature. There are ways to fix that anyways: Remove unlocked bootloader inscription by Raystef66 should work, and it is safe. And also there's NFound's zip on the Themes and Apps section, but it'a very risky (you might end up having to unbrick your phone).
Click to expand...
Click to collapse

I can confirm that WEEKLY Resurrection Remix Oreo ROM works perfectly. No bugs for me, not event the call one. Give that a try!

baconboy said:
I can confirm that WEEKLY Resurrection Remix Oreo ROM works perfectly. No bugs for me, not event the call one. Give that a try!
Click to expand...
Click to collapse
Download link?

Sure. I will try it later.
Just need stay with lineage 14.1 for couple of days to test it.
baconboy said:
I can confirm that WEEKLY Resurrection Remix Oreo ROM works perfectly. No bugs for me, not event the call one. Give that a try!
Click to expand...
Click to collapse

NFound has both RR-O-v6.0.0-20yymmdd-axon7-Weekly.zip, and RR-O-v6.0.0-20yymmdd-axon7-ENCRYPT-VERSION.zip on his androidfilehost page.
https://androidfilehost.com/?w=profile&uid=817550096634750733
Kranoner has RR-O-v6.0.0-20yymmdd-axon7-Unofficial.zip on his androidfilehost page.
https://androidfilehost.com/?w=profile&uid=457084094631641923
Victor13f said:
Download link?
Click to expand...
Click to collapse

llaalways said:
OK, I have resolved the problem with Password on boot.
I have tried many times, every time after flashed twrp, then I boot into twrp recovery, then do following steps:
1. advance wipe cache/dalvik cache/data/system,
2. install bootloader, modem, warning_patch, rom,
3. advance wipe cache/dalvik cache/data
4. install Magisk
5. advance wipe cache/dalvik cache/data
6. install Gapps
7. advance wipe cache/dalvik cache/data
then reboot to system, and the password is always asked on boot.
I have found out that instead of "advance wipe cache/dalvik cache/data", do a "factory reset" in twrp recovery, then the problem solved.
So the step should be
1. advance wipe cache/dalvik cache/data/system,
2. install bootloader, modem, warning_patch, rom, Gapps
3. install Magisk ( wipe cache/dalvik cache/data if fail to install, then install again)
4. factory reset.
After factory reset, boot into system and works.
There is still no sound on call problem, but fixed by toggling speakerphone on and off as you suggested.
Thanks.
Click to expand...
Click to collapse
That's still wrong. It works but it's unnecessary. You have to use the FORMAT DATA button instead of just advanced wipe data

llaalways said:
NFound has both RR-O-v6.0.0-20yymmdd-axon7-Weekly.zip, and RR-O-v6.0.0-20yymmdd-axon7-ENCRYPT-VERSION.zip on his androidfilehost page.
https://androidfilehost.com/?w=profile&uid=817550096634750733
Kranoner has RR-O-v6.0.0-20yymmdd-axon7-Unofficial.zip on his androidfilehost page.
https://androidfilehost.com/?w=profile&uid=457084094631641923
Click to expand...
Click to collapse
Cheers! Which one do you recommend? Kranoner or NFounds build?

I have not tested them yet.
Victor13f said:
Cheers! Which one do you recommend? Kranoner or NFounds build?
Click to expand...
Click to collapse

All Oreo 8.1 ROM have problem with dual SIM.
I have tried Lineage, RR, AEX, BootLeggers, dotOS.
llaalways said:
I have not tested them yet.
Click to expand...
Click to collapse

Im using AEX 8.1 with hell Kernel and it performs awesome. No buggs so far, only dual sim not working but its a know Problem.

llaalways said:
All Oreo 8.1 ROM have problem with dual SIM.
I have tried Lineage, RR, AEX, BootLeggers, dotOS.
Click to expand...
Click to collapse
Well maybe LOS 15 won't since they got the oreo files from ZTE. Which rom felt the smoothest to you from all the ones you tried?