Hi i installed custom rom to my samsung note 3 with cwm recovery it was working good.After a time later i need to format it.I opened cmw recovery and
-formatted system
-formatted cache
-formatted data
after that i installed custom rom it installed succesfully.I restarted the phone,sound and note 3 writed and it stacked at the "Samsung"writings.I waited a lot but it doesnt opened.How can i solve this problem.
I tried wipe
dalvik wipe cache
wipe cache
but not solved my problem.
I can still reach the cmw recovery 6.0.4.7.
Thanks.
try to flash this file and let me know if it works
btw wrong section to talk about problems
baba17 said:
Hi i installed custom rom to my samsung note 3 with cwm recovery it was working good.After a time later i need to format it.I opened cmw recovery and
-formatted system
-formatted cache
-formatted data
after that i installed custom rom it installed succesfully.I restarted the phone,sound and note 3 writed and it stacked at the "Samsung"writings.I waited a lot but it doesnt opened.How can i solve this problem.
I tried wipe
dalvik wipe cache
wipe cache
but not solved my problem.
I can still reach the cmw recovery 6.0.4.7.
Thanks.
Click to expand...
Click to collapse
Probably tried to flash a KK rom if you where running JB before.
Or the other way around, trying to flash a JB rom on a KK device.
Sent from my SM-N9005 using Tapatalk
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!
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
Hello friends how are you? I will try to be very brief and excuse me for my English
I recently bought a second-hand redmi note 7, and it came with the ROM Pixel Experience 2019 (Android 10) ... The fact is that I wanted to install the updated ROM Pixel Experience (Android 11 2021) and did the procedure to install the Recovery Fox Orange (The phone came with the recovery from Xiaomi).
In doing so, I performed the WIPE (Dalvik, Cache, Data, System) and proceeded to install the ROM from internal memory.
The ROM was installed correctly but when restarting it enters a Bootloop in the FastBoot and I have not been able to start ...
It is in Fastboot bootloop ... Please I need help, what can I do to start the Pixel Experience or what are the steps to follow? I heartily appreciate your help
Format data. you will need to type "YES" when doing it!!
so, format data, wipe evertyhing again, reboot to recovery, then install your rom and then have fun. hope it helps.
papppsanyi said:
Format data. you will need to type "YES" when doing it!!
so, format data, wipe evertyhing again, reboot to recovery, then install your rom and then have fun. hope it helps.
Click to expand...
Click to collapse
Bro i just did it but it is still in FastBoot ... What I did exactly was the following:
- Enter OrangeFox
- I did Format Data
- Then I Wipe from: Dalvik / ART Cache, Cache, System, Data
- Then copy the ROM Pixel Experience Plus Lavender 11 (PC to Phone USB)
- I gave Install and then restart
But still in Fastboot Boot .. D:
Try latest global stable firmware.
Had this problem with other rom and it was FW related
matthias1976 said:
Try latest global stable firmware.
Had this problem with other rom and it was FW related
Click to expand...
Click to collapse
Resolved! I just had to install the ROM from Xiaomi.EU (which started correctly) and then I proceeded to reinstall the Pixel Experience and this time it worked perfectly: D Thank you both very much