Hi Guys, After I rooted and installed the recovery (using autorec) I flashed CloudyG3 1.3, it got stuck on Android is upgrading: Starting apps. I reflashed it 3 more times and the same thing happened , so I flashed the backup that I made after installing the recovery, and that was stuck on starting apps too. Then I used the back to stock thread and flashed back to stock (which worked) I then re-rooted and Installed the recovery again then flashed cloudy again and the same thing happened.
So what do I do?
(I have the D802T)
Thanks!
Did you wiped /system, wipe data factoryreset, /dalvik-cache and flashed it?
wulsic said:
Did you wiped /system, wipe data factoryreset, /dalvik-cache and flashed it?
Click to expand...
Click to collapse
Yeah, I wiped the dalvik, and cache, I also wiped everything a couple of times and tried to sideload it, which resulted in the same error.
Its just weird that android is upgrading,upgrading from what? I gtg to school so i will do some research when im back xd
I wish you also luck to fix your problem.
According to this AutoRec dosn't work on the D802t.
I had flashed CM12 (by mukulsoni) 6 months ago. Everything was fine.
Suddenly my phone shutdown and is now bootlooping.
Can someone help me please?
Recovery Mode is working fine.
I wiped cache & dalvik cache.
Also did a factory reset.
Also flashed the same custom rom again, CM12 by Mukulsoni.
Thanks.
For every problem there is a solution, flash the stock rom. And then flash cm12 again!!
This started happening with a working RR android 7.1 ROM I have used for several days. Today, I wanted to try out LineageOS 14.1 so I made a nandroid backup of data and internal storage. When I rebooted into RR the screen was flickering and a message constantly popped up stating that com.android.phone stopped and Calendar stopped and com.android.media stopped etc etc.
So I went on and did a full clean flash
I tried t remove my sim and the clean flash but to no avail. I do advanced wipe --> Dalvik/ART cache, System, Data, Internal Storage, and Cache before every flash today. Then i flash ROM and latest gapps, wipe cache/dalvik and reboot.
Even without flashing gapps, the problem is still there.
Running on TWRP 3.0.0 (worked for several days on RR android 7.1 ROM), but tried on 3.0.2-2, 3.0.2, and 3.0.1 with the same results.
How did this happen? Is my EFS and IMEI f'ed because of the nandroid backup of data and internal storage?
How do I fix this?
Kind regards and a happy new year!
Same here. Twrp is the culprit, I'm afraid. It isn't taking good backups. Just fresh install RR and download all your apps, it'll work. Can't wait for twrp update...
i needed to format system to ext 4 and now everything works!
This is my first time updating any kind of ROM, so bare with me. What are the steps of correctly updating a ROM. Just want the steps so I can reflect on what I did wrong and fix it.
But what I did was clear the delvik/ART cache and Cache then flashed the updated ROM. I rebooted the device then the SYSTEMUI fail came up. I restarted the device many times and same result. Was I suppose to factory reset then install the updated ROM? or what?
Legwnd said:
This is my first time updating any kind of ROM, so bare with me. What are the steps of correctly updating a ROM. Just want the steps so I can reflect on what I did wrong and fix it.
But what I did was clear the delvik/ART cache and Cache then flashed the updated ROM. I rebooted the device then the SYSTEMUI fail came up. I restarted the device many times and same result. Was I suppose to factory reset then install the updated ROM? or what?
Click to expand...
Click to collapse
Maybe you accidentally wiped the System partition? Assuming you have TWRP if you are flashing ROM's. Because you already had 5.8.4 working, updating to 5.8.5 would seem to be simply flashing the dev's zip file in TWRP. Can't see how wiping cache or Dalvik would cause a failure to boot. Did you try reflashing the ROM again? Did the update finish with no errors? Maybe asking in the dedicated ROM thread may get you a more ROM specific answer. Next time just flash the ROM (no wipes) and let it completely boot up. You can always drop back down to TWRP and wipe if you feel it's necessary. Good luck.
Hi,
I have a problem installing 8.1 oreo roms on my phone. I follow standard procedure: wipe dalvik, cache, system, data -> install rom + gapps -> wipe cache. After my phone restarts, it displays rom logo, but doesn't load (even after 15-20 minutes of waiting). All I can do is load in fastboot and restore my backup. I use twrp 3.2.1-0, unofficial 8.1 pico gapps from 2018/01/30.
So far I tried:
-Installing rom and gapps separately.
-Installing rom, rebooting, installing gapps.
-Installing rom + gapps, then wiping data.
-Installing rom + gapps, then not wiping anything.
-Factory reset, then install rom + gapps.
-Installing rom + different gapps versions.
Additional notes:
-At one point I successfully installed NitrogenOS (about a month ago) and it is my current rom and backup. But I can't clean flash it again.
-When I install rom only (without any gapps) it boots up fine without errors or long loading.
Can anyone help?
Same problem I am also facing. Using Pixel experience ROM but now not able to flash cosmic official rom...remaining on bootanimation
Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
Flash
Rom
Gapps
Wipe to factory reset
Reboot
Done ! That's the only way it worked for me
metro20 said:
Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
Flash
Rom
Gapps
Wipe to factory reset
Reboot
Done ! That's the only way it worked for me
Click to expand...
Click to collapse
Thanks for answer. I tried that method too, but it still didn't work for me. I recently tried clean flash with gapps from https://forum.xda-developers.com/xiaomi-redmi-3s/development/rom-lineageos-15-1-t3718757 and it worked flawlessly. So maybe it's an issue with some gapps packages?
I also have the exact same problem.
Flashing ROM without gapps works perfectly.
adding gapps package, no matter if its pico aroma or mini, it results in stuck on boot animation.
wiping after flashing also did not work.
once made pixel experience boot, using it since...ota update worked without a problem.
any other suggestions?
devito666 said:
I also have the exact same problem.
Flashing ROM without gapps works perfectly.
adding gapps package, no matter if its pico aroma or mini, it results in stuck on boot animation.
wiping after flashing also did not work.
once made pixel experience boot, using it since...ota update worked without a problem.
any other suggestions?
Click to expand...
Click to collapse
Try this nano package https://androidfilehost.com/?fid=889964283620771808. It's the only one that worked for me.
sanchez8096 said:
Try this nano package https://androidfilehost.com/?fid=889964283620771808. It's the only one that worked for me.
Click to expand...
Click to collapse
Thanks for the Link!
But unfortunately still Not booting...tried atomic official and teammexs Rom...
metro20 said:
Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
*then tap back, FORMAT DATA and confirm by typing "yes"
Flash
Rom
Gapps
Magisk stable (if preferred if not next >>>)
Magisk beta (always flash after stable)
Busybox flashable zip (if needed)
Mods such as MIUI cam mod
Font package
Wipe to factory reset
Reboot
After 1st boot
Reboot to TWRP
Install Magisk modules ( USN or Viper4android etc)
Reboot system
Done ! That's the only way it worked for me
Click to expand...
Click to collapse
ftfy. But before this ensure that:-
1. Non corrupted ZIPs. Avoid if possible from using mobile data. A slower yet stable WiFi yields better success rate.
2. Currently this unofficial opengapps' builds works better and are more current.
Suo.Eno said:
ftfy. But before this ensure that:-
1. Non corrupted ZIPs. Avoid if possible from using mobile data. A slower yet stable WiFi yields better success rate.
2. Currently this unofficial opengapps' builds works better and are more current.
Click to expand...
Click to collapse
I didn't need to format data on Oreo nos
As mentioned in other threads on this topic, I just wanted to mention here as well that I am also affected by these Oreo boot loops and haven't found a solution yet. I somehow managed to get PixelExperience to install once, but downgraded now to a Nougat build for other reasons (better battery and GCamMod compatibility).
sanchez8096 said:
Thanks for answer. I tried that method too, but it still didn't work for me. I recently tried clean flash with gapps from https://forum.xda-developers.com/xiaomi-redmi-3s/development/rom-lineageos-15-1-t3718757 and it worked flawlessly. So maybe it's an issue with some gapps packages?
Click to expand...
Click to collapse
Use twrp 3.2.1-0 bcoz some Oreo ROMs aren't flash able by 3.1.1
Sunny Za said:
Use twrp 3.2.1-0 bcoz some Oreo ROMs aren't flash able by 3.1.1
Click to expand...
Click to collapse
I am using 3.2.1-0 twrp. Rom itself flashes fine, it's the gapps that create infinite boot.
Exact Same issue Here...
I have same problem too .. can't boot in to any Oreo ROM with Gapps .. really isn't any solution here?
This might not be a proper solution, but here's what I did:
1) Wipe data, cache, dalvik, system
2) Flash rom + gapps(I used NitrogenOS and pico gapps)
3) Wipe data again and restore data from backup(I restored data from previous build of NitrogenOS, so I don't know if restoring from different rom will be ok)
4) Boot into rom, ignore any "stopped working" errors and go to Settings-System-Reset options-Erase all data(Not sure if this will erase internal storage, backup just in case)
After that phone booted up and and did first time installation.
sanchez8096 said:
This might not be a proper solution, but here's what I did:
1) Wipe data, cache, dalvik, system
2) Flash rom + gapps(I used NitrogenOS and pico gapps)
3) Wipe data again and restore data from backup(I restored data from previous build of NitrogenOS, so I don't know if restoring from different rom will be ok)
4) Boot into rom, ignore any "stopped working" errors and go to Settings-System-Reset options-Erase all data(Not sure if this will erase internal storage, backup just in case)
After that phone booted up and and did first time installation.
Click to expand...
Click to collapse
Can someone upload me some backup? Pixel Experience would be a best ! Thanks a lot
Anyone have an idea what the problem might be?
I'm facing the same problem. I have a Redmi 3S (international, 3GB version). Doesn't matter what Oreo ROM I try (clean install), they all get stuck in bootloop on boot animation. It doesn't get far enough in the boot process to do a logcat with ADB, so I'm not able to post it.
I'm using TWRP 3.2.1-0 but have tried Red Wolf recovery as well and it yields the same results... I don't think it's a gapps issue since I've tried booting several ROMS without installing gapps.
I have rebooted several times while it's still in the boot process, remounted system in TWRP, wiped everything, ...
If anyone has an idea to get the logs, fire away. Can't boot so can't install liveboot or something like that.
bump
any solution?
The Problem still occurs...
Flashed PE successfully once, but since i went Back to official Nougat lineage os, No Oreo Roms can be booted with gapps