Related
After I downlaoded the offical cm 14.1 nightly to my oneplus 2, I flashed. When starting the phone, i got the notification, that google play store and their service were stopped. So i went back to the recovery TWRP and wiped the dalvik cache and regular cache. After I did this, the phone went into a bootloop and i dont know how to fix this.
Hopefully I can repair the issue asap cause its my daily driver ands its important
It sounds like your data partition contains data structures from older CM13 or derivate ROM. In that case you will have to clean flash to get it going without bugs and boot problems. Also make sure you flash the latest nano or micro package of Gapps for 7.1 ROM 64-bit.
AxeltheWexel said:
After I downlaoded the offical cm 14.1 nightly to my oneplus 2, I flashed. When starting the phone, i got the notification, that google play store and their service were stopped. So i went back to the recovery TWRP and wiped the dalvik cache and regular cache. After I did this, the phone went into a bootloop and i dont know how to fix this.
Hopefully I can repair the issue asap cause its my daily driver ands its important
Click to expand...
Click to collapse
Same thing hapening to me tried everything even used network signal guru and selected band 3 and 5 then too i am facing the same problem and phone get random reboots now and the. please help.
AxeltheWexel said:
After I downlaoded the offical cm 14.1 nightly to my oneplus 2, I flashed. When starting the phone, i got the notification, that google play store and their service were stopped. So i went back to the recovery TWRP and wiped the dalvik cache and regular cache. After I did this, the phone went into a bootloop and i dont know how to fix this.
Hopefully I can repair the issue asap cause its my daily driver ands its important
Click to expand...
Click to collapse
1. Download latest GAPPS for 7.1 (ARM64). Here -> http://opengapps.org
2. Enter TWRP & Connect the phone to a PC (you can still access phone storage in recovery)
3. Copy GAPPS zip.
4. In TWRP go to "Wipe" & wipe Data + Cache + Dalvik Cache (Your internal storage won't be wiped)
5. Flash CM 14.1 zip.
6. Flash downloaded GAPPS.
7. Reboot System! Done!
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
TWRP on S8+ Oreo Exp9. Failed to mount '/data' (No such process)
Never have had this problem on TWRP before. Neither on my S6E, S7E and S8+ , always updated on latest firmware, rooted and with perfect TWRP.
Until now ..... with latest OREO/exp 9 update .... . Cant make any backup / restore for _ Failed to mount '/data' (No such process)_
How I did try it (for almost two days):
1:Flash G955FXXU1CRB7/ G950FXXU1CRAP (samfirm and WRoid) with odin 3.13.1 / 3.12.3 and Prince
2:Flash TWRP 3.2.1-0 latest
3:Format Data ( yes) + also tried Wipe Data, and Internal Data, Dalvik & Cache
4: Reboot recovery and Flash no-verity-opt-encrypt-6.0
5:Flash Magisk 16 , later on also tried 15.3
6:Reboot
7. Setup and phone works fine
but when booting into Twrp afterwards and try to make f.e. a backup get a "Failed to mount '/data' (No such process)" notice .
Already Tried:
differet odins, firmwares , magisks , partitioning SD, re-formating micro SD ext 3 / ext 4
always same error message after rebooring and never can "mount data" afterwards .
HELP .
Tnx in advance ,
El
here is a person who said that you have to stay 1 week without shutdown phone if y want twrp work with no costumed rom but y can use costumed rom no wipe needed
It's a problem with Magisk. You need to flash a custom kernel or use SuperSU instead of Magisk.
I'm having same issue have tried all of all of that already also have tried going into advanced wipe changing file system, it bring up the /data and will work to flash files but as soon as you reboot it goes back to failing. I'm getting fed up with restoring my phone and adjusting all my settings and apps everytime
Any help would be much appreciated
Ta
Sjant said:
It's a problem with Magisk. You need to flash a custom kernel or use SuperSU instead of Magisk.
Click to expand...
Click to collapse
How can I install supersu without wiping my data and having to restore again, I tried the magisk uninstaller but TWRP can't read /data. Also I tried to Download notorious kernel but I can't seem to get the link to download
I have the same problem. Formatted data multiple times, always the same problem, as OP described it. Is RMM state really the problem here? Or has anybody tried it with SuperSU instead of Magisk? I'm really tired of setting up my phone all over again...
ali112 said:
I have the same problem. Formatted data multiple times, always the same problem, as OP described it. Is RMM state really the problem here? Or has anybody tried it with SuperSU instead of Magisk? I'm really tired of setting up my phone all over again...
Click to expand...
Click to collapse
Just tried it with SuperSU, doesn't work either.
after so many tests I discovered that twrp can read and write data only if you flash last supersu beta, magisk and supersu official both doesn't work:
https://forum.xda-developers.com/app...v2-05-t2868133
Hello Guys Recently i decided to update my OP5 which was on rooted nougat for a year and some how after countless wipes, bootloops, rom flashes and data mounting errors in twrp, was able to flash OOS 5.0 instead of the OOS 5.1.4 , coz flashing 5.1.4 directly from OOS 4.1.5 ,resulted in "error 7" everytime
Device status is unlocked boot loader, decrypted and rooted with magisk. But after this when i check with TWRP(3.2.3) ,i found that its unable to mount data partion again and cannot flash upadte on it or do anything else in twrp, tried to mount the data partion but that resulted in loosing OS again and had to repeat the whole process to Install OOS 5.0 .
Any Idea how i can update my phone further to 5.1.4 or beyond that?
Akarsh Adithya.K said:
Hello Guys Recently i decided to update my OP5 which was on rooted nougat for a year and some how after countless wipes, bootloops, rom flashes and data mounting errors in twrp, was able to flash OOS 5.0 instead of the OOS 5.1.4 , coz flashing 5.1.4 directly from OOS 4.1.5 ,resulted in "error 7" everytime
Device status is unlocked boot loader, decrypted and rooted with magisk. But after this when i check with TWRP(3.2.3) ,i found that its unable to mount data partion again and cannot flash upadte on it or do anything else in twrp, tried to mount the data partion but that resulted in loosing OS again and had to repeat the whole process to Install OOS 5.0 .
Any Idea how i can update my phone further to 5.1.4 or beyond that?
Click to expand...
Click to collapse
Hello, do you read this similar thread already https://forum.xda-developers.com/oneplus-5/help/oneplus5-ota-update-4-1-15-to-5-0-1-5-1-t3859695 ?
strongst said:
Hello, do you read this similar thread already https://forum.xda-developers.com/oneplus-5/help/oneplus5-ota-update-4-1-15-to-5-0-1-5-1-t3859695 ?
Click to expand...
Click to collapse
Yeah, i checked the thread, but mine is a bit different, coz mine is rooted and has TWRP recovery, and it took me many bootloops and flashs to figure out ,that i have to flash every single version of OOS, for example 4.1 to 5.0 and then, 5.0 to 5.0.4 and then 5.0.4 to 5.1 and on.
You get the point. But now i cant update after 5.0 , as TWRP throws this "unable to mount storage" error and my internal storage doesnt even show up in install section
Akarsh Adithya.K said:
Yeah, i checked the thread, but mine is a bit different, coz mine is rooted and has TWRP recovery, and it took me many bootloops and flashs to figure out ,that i have to flash every single version of OOS, for example 4.1 to 5.0 and then, 5.0 to 5.0.4 and then 5.0.4 to 5.1 and on.
You get the point. But now i cant update after 5.0 , as TWRP throws this "unable to mount storage" error and my internal storage doesnt even show up in install section
Click to expand...
Click to collapse
What twrp(link) do you have?
Did you format internal storage or not?
Don't bother with root until you have undated your os. Updating with twrp is also possible and I did it a lot of times.
strongst said:
What twrp(link) do you have?
Did you format internal storage or not?
Don't bother with root until you have undated your os. Updating with twrp is also possible and I did it a lot of times.
Click to expand...
Click to collapse
Its twrp 3.2.3 and yeah before installing rom , i did a full wipe of dalvik, data, system, internal storage and then did a data format too
Akarsh Adithya.K said:
Its twrp 3.2.3 and yeah before installing rom , i did a full wipe of dalvik, data, system, internal storage and then did a data format too
Click to expand...
Click to collapse
Please link the twrp file you're running. Als also you aware that twrp won't stick if you flash full oos rom?
strongst said:
Please link the twrp file you're running. Als also you aware that twrp won't stick if you flash full oos rom?
Click to expand...
Click to collapse
"https://dl.twrp.me/cheeseburger/twrp-3.2.3-0-cheeseburger.img.html"
Yeah i m aware of it and i flashed twrp back every time i finish flashing full OOS
Akarsh Adithya.K said:
"https://dl.twrp.me/cheeseburger/twrp-3.2.3-0-cheeseburger.img.html"
Yeah i m aware of it and i flashed twrp back every time i finish flashing full OOS
Click to expand...
Click to collapse
Please use the latest blu spark recovery which needs to be installed for the vendor partition from 5.1.4 https://forum.xda-developers.com/devdb/project/dl/?id=30332 or codeworks recovery. If you decrypt internal storage and did not flash no verity zip to stay decrypted, after first boot oos will encrypt interval storage.
strongst said:
Please use the latest blu spark recovery which needs to be installed for the vendor partition from 5.1.4 https://forum.xda-developers.com/devdb/project/dl/?id=30332 or codeworks recovery. If you decrypt internal storage and did not flash no verity zip to stay decrypted, after first boot oos will encrypt interval storage.
Click to expand...
Click to collapse
Its Decrypted , but do i have flash no verity zip, again after flashing twrp img
Akarsh Adithya.K said:
Its Decrypted , but do i have flash no verity zip, again after flashing twrp img
Click to expand...
Click to collapse
If you want to stay decrypted: yes
But first update your twrp, check if data partition is accessible, otherwise format internal storage - easiest way.
strongst said:
If you want to stay decrypted: yes
But first update your twrp, check if data partition is accessible, otherwise format internal storage - easiest way.
Click to expand...
Click to collapse
Thanks man strongst, it worked.
Changing recovery to blu spark twrp made all the difference, now i m on OOS 5.1.4
Akarsh Adithya.K said:
Thanks man strongst, it worked.
Changing recovery to blu spark twrp made all the difference, now i m on OOS 5.1.4
Click to expand...
Click to collapse
To help others mark this thread as [SOLVED] in the the title :good:
strongst said:
To help others mark this thread as [SOLVED] in the the title :good:
Click to expand...
Click to collapse
Yeah And one last question,
I tried ti update it to 5.1.5, using same process, and it throws boot loop, is there any other specifc order to flashing magisk and no verity, Or do i have to use other version of verity.
currently the one i m using is no verity v2
Akarsh Adithya.K said:
Yeah And one last question,
I tried ti update it to 5.1.5, using same process, and it throws boot loop, is there any other specifc order to flashing magisk and no verity, Or do i have to use other version of verity.
currently the one i m using is no verity v2
Click to expand...
Click to collapse
Flash full rom Update 5.1.4, then 5.1.5 then
Just make sure that vendor partition is mounted correctly within twrp, before flashing no verity v2 and after then magisk.
Now you can reboot the first time. If it won't help, you should format internal storage again when you have copied files into it like the rom zip. This can cause a bootloop sometimes.
strongst said:
Flash full rom Update 5.1.4, then 5.1.5 then
Just make sure that vendor partition is mounted correctly within twrp, before flashing no verity v2 and after then magisk.
Now you can reboot the first time. If it won't help, you should format internal storage again when you have copied files into it like the rom zip. This can cause a bootloop sometimes.
Click to expand...
Click to collapse
Again , thank you soo much man .
Turns out enabling that vendor portion after flash rom for no verity and magisk will cause no trouble
and now i m on OOS 5.1.5!!(uninstalling Magisk before flashing new update was important to).
Now that
how do i mark this thread as Solved.
my galaxy s8 was rooted , and after a while i did factory reset through twrp -
format data
then advanced wipe - and wipe everything except system.
then i flashed again the latest version of twrp , magisk , rmm bypass, and no-verify-opt-encrypt 6.0
when i tried to flash no-verify-opt-encrypt 6.0 i got the error "failed to mount preload invaild argument"
however, my phone is rooted, and it is working.
is it should be an issue ?
how can i fix it?
i am using the stock firmware
AmirKar said:
my galaxy s8 was rooted , and after a while i did factory reset through twrp -
format data
then advanced wipe - and wipe everything except system.
then i flashed again the latest version of twrp , magisk , rmm bypass, and no-verify-opt-encrypt 6.0
when i tried to flash no-verify-opt-encrypt 6.0 i got the error "failed to mount preload invaild argument"
however, my phone is rooted, and it is working.
is it should be an issue ?
how can i fix it?
i am using the stock firmware
Click to expand...
Click to collapse
Won't cause any real issues.
If worried about it in twrp select
Wipe menu - advanced wipe - select preload - swipe to wipe
spawnlives said:
Won't cause any real issues.
If worried about it in twrp select
Wipe menu - advanced wipe - select preload - swipe to wipe
Click to expand...
Click to collapse
hey ! thanks for the reply .
i did wiped the preload, and flashed everything over again, but got "error installing zip file /external_sd/no-verify: error 1"
but again, everything working smoothly.
would i try flash stock firmware using odin and start over again?
AmirKar said:
hey ! thanks for the reply .
i did wiped the preload, and flashed everything over again, but got "error installing zip file /external_sd/no-verify: error 1"
but again, everything working smoothly.
would i try flash stock firmware using odin and start over again?
Click to expand...
Click to collapse
AmirKar said:
hey ! thanks for the reply .
i did wiped the preload, and flashed everything over again, but got "error installing zip file /external_sd/no-verify: error 1"
but again, everything working smoothly.
would i try flash stock firmware using odin and start over again?
Click to expand...
Click to collapse
The issue is with twrp not the system..
I don't know how you have set up twrp
If everyrhing else can be flashed in twrp except no verity zip maybe a possible corruption in zip file.
Note: lasted no verity zip is 6.1