Related
Hey guys,
today i have made a OTA-Update over the Cyanogenmod-Updater (CWM-Version: 6.0.4.6) from Version cm-11-20140220-NIGHTLY-falcon to cm-11-20140227-NIGHTLY-falcon and everything went fine.
But after the first reboot i have got a bootloop issue. The only thing you can do is, to wait about 4-5 minutes; then the system starts normally und you can enter your pin-code.
Another interesting thing was that after the update my "es file explorer" get warning -> something like missing file and was deinstalled by itself without asking me.
Now i installed the es file explorer again and get the same warning again.
Hope you can help me.
Did you try to wipe cache and dalvic cache in CWM?
Dizzyrul3z said:
Did you try to wipe cache and dalvic cache in CWM?
Click to expand...
Click to collapse
No. I just make a dirty flash over the Cyanogemod-Updater under Settings.
So, i have made now a wipe cache and dalvik cache in CWM but this does not solve the bootloop issue and the strange deinstallation of my apps.
Whenever i start the Phone with the power button it tooks about 5 minutes to enter my pin code.
After each system start one app is in random order deinstalled by itself. This time my es file explorer is ok but gmail was deinstalled.
I have had never such issues on the cm-11-20140220-NIGHTLY-falcon.
The cm-11-20140227-NIGHTLY-falcon seems to be buggy and should be removed from the official OTA-Update.
Volkan66 said:
So, i have made now a wipe cache and dalvik cache in CWM but this does not solve the bootloop issue and the strange deinstallation of my apps.
Whenever i start the Phone with the power button it tooks about 5 minutes to enter my pin code.
After each system start one app is in random order deinstalled by itself. This time my es file explorer is ok but gmail was deinstalled.
I have had never such issues on the cm-11-20140220-NIGHTLY-falcon.
The cm-11-20140227-NIGHTLY-falcon seems to be buggy and should be removed from the official OTA-Update.
Click to expand...
Click to collapse
Hi, I have the same situation as you. I flashed from 24th to 27th, everything was OK. After that I flashed pink kernel from 21th.
After that flashing I had over and over bootloops. Wipe/factory reset - nothing changes. I formated internal card fully and now I would like to flash I don't know stock or maybe still CM but I'm sure not 27th release.
Volkan66 said:
Hey guys,
today i have made a OTA-Update over the Cyanogenmod-Updater (CWM-Version: 6.0.4.6) from Version cm-11-20140220-NIGHTLY-falcon to cm-11-20140227-NIGHTLY-falcon and everything went fine.
But after the first reboot i have got a bootloop issue. The only thing you can do is, to wait about 4-5 minutes; then the system starts normally und you can enter your pin-code.
Another interesting thing was that after the update my "es file explorer" get warning -> something like missing file and was deinstalled by itself without asking me.
Now i installed the es file explorer again and get the same warning again.
Hope you can help me.
Click to expand...
Click to collapse
What recovery do you have installed?
january waower
kieranc said:
What recovery do you have installed?
Click to expand...
Click to collapse
I have installed ClockworkMod-Recovery (CWM): cwm-6.0.4.6
I don't have any problems with the recovery but with the Nightly Update from 27th February.
I can't understand how the cm-11-20140227-NIGHTLY-falcon can get official, when a lots of people have the same problem: bootloops.
=dgim= said:
Hi, I have the same situation as you. I flashed from 24th to 27th, everything was OK. After that I flashed pink kernel from 21th.
After that flashing I had over and over bootloops. Wipe/factory reset - nothing changes. I formated internal card fully and now I would like to flash I don't know stock or maybe still CM but I'm sure not 27th release.
Click to expand...
Click to collapse
I totally agree with you. I won't do a full format of the internal card. Just waiting for the next Nightly in the hope that dhacker improves this issue.
Do you have also problems with GMAIL. After each restart GMAIL is lost. I must install it each time new.
I had the same problem and haven't fixed it yet. I had CWM 6.0.4.5 installed when CM updater tried to install 0227 and I'm wondering if that could be the problem as dhacker29 recommended an update to the CWM he specified to avoid "accidental wiping of critical partitions."
I dunno, but so far it looks like I'm going to have to restore stock firmware and start from scratch....
kieranc said:
I had the same problem and haven't fixed it yet. I had CWM 6.0.4.5 installed when CM updater tried to install 0227 and I'm wondering if that could be the problem as dhacker29 recommended an update to the CWM he specified to avoid "accidental wiping of critical partitions."
I dunno, but so far it looks like I'm going to have to restore stock firmware and start from scratch....
Click to expand...
Click to collapse
So, I installed by mfastboot for now the newest stock rom 4.4.2 DE, updated to the latest release and rooted.
Maybe I'll flash also kernel to faux's release. Very strange issue. I flashed CM several times and today's issue was the first time.
=dgim= said:
Hi, I have the same situation as you. I flashed from 24th to 27th, everything was OK. After that I flashed pink kernel from 21th.
After that flashing I had over and over bootloops. Wipe/factory reset - nothing changes. I formated internal card fully and now I would like to flash I don't know stock or maybe still CM but I'm sure not 27th release.
Click to expand...
Click to collapse
I've just wiped /data/media ("sdcard") and have successfully installed and booted feb 27th build. Strange problem but that looks like the solution....
I was at the 0224 build and flawlessly updated to the 0227 build... no issue so far. i am using twrp...
Hey guys,
i have flashed the newest Nightly cm-11-20140228-NIGHTLY-falcon.zip today and everything was solved. No bootloops or lost of apps.
With pink kernel the system rocks. This is awesome. Thanks to dhacker29, pinkflozd, faux123, razrqcom-dev-team :good::good::good:
Im Using Since last two nightlys no Pink Kernel anymore. The battery life under Stock cm Rocks now. Bat i have Crap Sounds in Calls Since then..
Android-CM11
hydromän said:
Im Using Since last two nightlys no Pink Kernel anymore. The battery life under Stock cm Rocks now. Bat i have Crap Sounds in Calls Since then..
Android-CM11
Click to expand...
Click to collapse
I can confirm your sound problem.
I am using the nightly version 0228 and pink kernel 0228 and would recommend you to use the pink kernel because you will feel the boost in performance.
Yes the battery will drain a little bit more than on stock-cm but it is worth it. I can use my phone with pink kernel two days long without charging it.
So I will try Again Pink Kernel =).. I hope the Sound in Call Problem get fixed soon
Android-CM11
I Flashed last Pink Kernel, youre right, really smoother than stock cm Kernel :thumbup:
Android-CM11
hydromän said:
I Flashed last Pink Kernel, youre right, really smoother than stock cm Kernel :thumbup:
Android-CM11
Click to expand...
Click to collapse
Yeah this version of pink kernel is great. I hope this kernel will leave soon the beta-stadium and will get official.
0303-NIGHTLY sometimes still has the problem
Sent from my Moto G using xda app-developers app
tohigh said:
0303-NIGHTLY sometimes still has the problem
Sent from my Moto G using xda app-developers app
Click to expand...
Click to collapse
Please flash the TWRP 2.6.3.3 recovery first then flash the newest nightly cm-11-20140304-NIGHTLY-falcon.zip .
I am using 0303-NIGHTLY with TWRP 2.6.3.3 and don't have such issues like bootloop again.
But it is very important to flash the recovery first, then flash cm-11-20140304-NIGHTLY-falcon.zip with Cyanogenmod-Updater under settings.
If you do otherwise flash cm first you will encounter the same problem.
I run CM 13 and want to back to color os because it is not run so smooth. I format and then flash stock recovery image (then recovery) via twrp and reboot to stock recovery.
In stock recovery i wipe data and cache. That's problem come. Before finish, the screen goes black. I try to power on the device, back to wipe data then the screen goes to black again. I try to boot to recovery and fastboot but it remain the same, back to wipe data and then the screen goes to black..
I try repair it using msm tool but because my comp not recognize the device, i use QFIL. And then i can use the fastboot to boot stock recovery. Suceed. But no os inside. Try and error many times, i can power on the device at the end.
But now the other problem comes. My wifi and bluetooth not work. And message nv backup appear.
Flash project spectrum. Wifi and bluetooth work. I flash back to stock os. Wifi and bluetooth not work again..
May someone help me to solve the problem (make bluetooth and wifi work again)?
To get back to ColorOS from spectrum flash this rom from internal storage.
http://community.oppo.com/en/forum.php?mod=viewthread&tid=41945
Sent from my R7plusf using XDA-Developers mobile app
uyab.com said:
I run CM 13 and want to back to color os because it is not run so smooth.
Click to expand...
Click to collapse
I think your initial problem was that you didn't flash open Gapps right after you flashed CM13.
Most users who are new to custom roms don't know that they have to flash Google apps separately.
kishd said:
To get back to ColorOS from spectrum flash this rom from internal storage.
http://community.oppo.com/en/forum.php?mod=viewthread&tid=41945
Sent from my R7plusf using XDA-Developers mobile app
Click to expand...
Click to collapse
I use color os now. Have no problem bout back to color from spectrum. The problem occures after that. Wifi and bluetooth do not work.
celoxocis said:
I think your initial problem was that you didn't flash open Gapps right after you flashed CM13.
Most users who are new to custom roms don't know that they have to flash Google apps separately.
Click to expand...
Click to collapse
I flashed pico after flash CM. Pico TTS unfortunately has stopped. I use browser, unfortunately stopped. Facebook stopped. Camera stopped. That's the beginning of all the problem because after that i format the phone.
uyab.com said:
I flashed pico after flash CM. Pico TTS unfortunately has stopped. I use browser, unfortunately stopped. Facebook stopped. Camera stopped. That's the beginning of all the problem because after that i format the phone.
Click to expand...
Click to collapse
Did you boot into CM after flashing CM? and then installed Gapps later on? This could explain corrupted cache.
Always follow these steps on custom roms. (first time install not upgrade)
Boot into TWRP, select wipe/factory reset.
1. Install CM Rom
after that select the next zip (or add more zips to flash)
2. install Gapps.
Let it boot and setup your phone.
If you follow this you will never have a problem in CM.
Especially the R7 series. Every change to the code is closely tripled (even quadruple) checked by devs.
Because the R5, R7, R7Plus, R7S all share the same base and its tested in on every phone.
celoxocis said:
Did you boot into CM after flashing CM? and then installed Gapps later on? This could explain corrupted cache.
Always follow these steps on custom roms. (first time install not upgrade)
Boot into TWRP, select wipe/factory reset.
1. Install CM Rom
after that select the next zip (or add more zips to flash)
2. install Gapps.
Let it boot and setup your phone.
If you follow this you will never have a problem in CM.
Especially the R7 series. Every change to the code is closely tripled (even quadruple) checked by devs.
Because the R5, R7, R7Plus, R7S all share the same base and its tested in on every phone.
Click to expand...
Click to collapse
Of course not. I flash CM and after that i flash pico right away. Not yet boot into CM. After CM and pico install then wipe dalvik then reboot.
uyab.com said:
Of course not. I flash CM and after that i flash pico right away. Not yet boot into CM. After CM and pico install then wipe dalvik then reboot.
Click to expand...
Click to collapse
But did you wipe factory reset before flashing all the above? Coming from ColorOS. Else those errors can't be explained.
celoxocis said:
But did you wipe factory reset before flashing all the above? Coming from ColorOS. Else those errors can't be explained.
Click to expand...
Click to collapse
Yes. I wipe all but not the internal storage. Is it the cause? I do not know why twrp cannot read otg. So i put CM file on internal storage.
uyab.com said:
Yes. I wipe all but not the internal storage. Is it the cause? I do not know why twrp cannot read otg. So i put CM file on internal storage.
Click to expand...
Click to collapse
I don't know about the R7Plus TWRP. I don't maintain that TWRP. I know that my R7S TWRP works with OTG.
Internal storage should have been fine. I think it will stay a mystery why you received those errors.
celoxocis said:
I don't know about the R7Plus TWRP. I don't maintain that TWRP. I know that my R7S TWRP works with OTG.
Internal storage should have been fine. I think it will stay a mystery why you received those errors.
Click to expand...
Click to collapse
wish me luck. I will try your suggestion.
uyab.com said:
I use color os now. Have no problem bout back to color from spectrum. The problem occures after that. Wifi and bluetooth do not work.
Click to expand...
Click to collapse
Once back on ColorOs from Spectrum. Flash this older version of ColorOs and then CM everything including bluetooth should work fine.
https://www.dropbox.com/s/xmh77xyinz2iero/R7plusfEX_11_OTA_012_all_201512251816.zip?dl=0
kishd said:
Once back on ColorOs from Spectrum. Flash this older version of ColorOs and then CM everything including bluetooth should work fine.
https://www.dropbox.com/s/xmh77xyinz2iero/R7plusfEX_11_OTA_012_all_201512251816.zip?dl=0
Click to expand...
Click to collapse
Oya.. Let me try it..
Solved. WiFi and Bluetooth work fine. Run smooth in CM.
uyab.com said:
Solved. WiFi and Bluetooth work fine. Run smooth in CM.
Click to expand...
Click to collapse
Which method fixed the issue in the end?
Maybe bad repaired or bad flashing. Persist folder is empty. Thats why i can not install CM and unvailable wifi and bluetooth address. So flashing persist.img after remove the old one.
uyab.com said:
Solved. WiFi and Bluetooth work fine. Run smooth in CM.
Click to expand...
Click to collapse
hi sir im having the same problem with my R7 plus can you help me
i already flash my phone using QFIL with Oppo_R7_Plusf_EX_11_A.15_160612_By(GsmTechSupport)
result is only OPPO Logo
flash the phone with Msm8x38 with Oppo_R7_Plusf_EX_11_A.15_160612_By(GsmTechSupport)
result is phone will boot normal but the problem is same with your problem with WIFI and Bluetooth also appear something with NV partion but can be manage with *#268# but with wifi and bluetooth i cant solve
please help me.
thank you in advance
I'm so sorry. I just log in after a long time and read your problem. Have you solved the problem?
same problem for me, no wifi and no bluetooth after flashing stock rom.
Any idea?
uyab.com said:
Maybe bad repaired or bad flashing. Persist folder is empty. Thats why i can not install CM and unvailable wifi and bluetooth address. So flashing persist.img after remove the old one.
Click to expand...
Click to collapse
hello,
please ask me where to find persist.img and the method for flashing it.
thanks in advance
Magisk 17 (Stable) was just released. I am uninstalled 16 via the official uninstall. I then rebooted to TWRP and flashed 17. The phone kept going back to recovery. I uninstalled and reinstalled 16 and I'm back up. Anyone else get 17 to work on the latest OOS?
same here, can not get it to work
I downloaded it, then flashed it in twrp, but i never uninstalled the older version, I just flashed over the older one. Mine booted up fine,
I'm on OOS 5.1.11
Updated from 16.7 beta to 17.0 via Magisk Manager (direct installation).
Everything worked fine, except the warning pop-up on boot that was also on 16.7.
I was on Magisk 16.4. After installed v17, root was broken. I had to uninstall it and redo V16.4.
I wound up having to wipe data. Now 17 seems to be OK. Time will tell.
Even after running the uninstaller and reinstalling 16, after about 5 minutes running fine, the system would just randomly reboot.
Be prepared if you install 17, you may have to wipe data
Mike02z said:
I wound up having to wipe data. Now 17 seems to be OK. Time will tell.
Even after running the uninstaller and reinstalling 16, after about 5 minutes running fine, the system would just randomly reboot.
Be prepared if you install 17, you may have to wipe data
Click to expand...
Click to collapse
How come you uninstalled magisk before reinstalling the newer version? Is that normal, i always flash over the older version without uninstalling the older version & reinstalling the newer version & never had any problems.
I'm running xxx module with ex kernel, i downloaded the update zip, flashed in twrp & rebooted, everything worked but i did get that boot internal storage message, so reflashed ex kernel & the message was gone. I'm not sure, maybe it was cause you uninstalled your older version of magisk that messed things up, or maybe it's that i had ex kernel already installed that helped me not have any problems.
Rebel7022 said:
How come you uninstalled magisk before reinstalling the newer version? Is that normal, i always flash over the older version without uninstalling the older version & reinstalling the newer version & never had any problems.
I'm running xxx module with ex kernel, i downloaded the update zip, flashed in twrp & rebooted, everything worked but i did get that boot internal storage message, so reflashed ex kernel & the message was gone. I'm not sure, maybe it was cause you uninstalled your older version of magisk that messed things up, or maybe it's that i had ex kernel already installed that helped me not have any problems.
Click to expand...
Click to collapse
I tried flashing right over 16.0. It just kept dumping me back into TWRP.
Rebel7022 said:
How come you uninstalled magisk before reinstalling the newer version? Is that normal, i always flash over the older version without uninstalling the older version & reinstalling the newer version & never had any problems.
I'm running xxx module with ex kernel, i downloaded the update zip, flashed in twrp & rebooted, everything worked but i did get that boot internal storage message, so reflashed ex kernel & the message was gone. I'm not sure, maybe it was cause you uninstalled your older version of magisk that messed things up, or maybe it's that i had ex kernel already installed that helped me not have any problems.
Click to expand...
Click to collapse
I did that. That is always the way I update it as well. It just booting back into TWRP.
1N1ghth4wk said:
Everything worked fine, except the warning pop-up on boot that was also on 16.7.
Click to expand...
Click to collapse
In Magisk Manager select Uninstall -> Restore images -> Flag the option "Preserve AVB 2.0/dm-verity" -> install -> direct install -> reboot.
Warning pop-up should not appear anymore
Mike02z said:
I tried flashing right over 16.0. It just kept dumping me back into TWRP.
Click to expand...
Click to collapse
Flash a kernel, I like ex kernel , It probably will fix it
I just let the Magisk app update itself and direct install the update and reboot. I always do that, works fine.
Sent from my ONEPLUS A6003 using Tapatalk
brossovitch said:
I just let the Magisk app update itself and direct install the update and reboot. I always do that, works fine.
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
Same for me, and everything works fine with the latest version.
I am on H2 os ob 02, Magisk 16.7.
I got message to update Magisk aplication. I did, then, message to update to Magisk 17.
Everything works fine.
I just let it update the Magisk Manager and now i'm without root (no idea how i ended like this i swear i just updated the Manager) and the Manager doesn't have the ability to install Magisk directly, just download zip only or patch boot image. Guess i'm up to reinstall TWRP and flash the Magisk zip manually, right?
Flashed Directly over 16.7 (H2os beta 2) without wipe or issues :good:
Happened to me too I got stuck in bootloop to twrp didnt need to wipe data. I used flash all partitions fastboot.bat from https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 to get back to normal without losing data. I had to reinstall twrp and magisk though. Now I'm on magisk 17.0 all fine.
So I do it just let it update the Magisk Manager. CustomRom AospExtended ROM V5.8
And running
Also got stuck in a bootloop after installing 17 over 16. Using the uninstaller fixed the issue, and when I re-tried installing 17 in TWRP it worked fine.
Installed 16.4 yesterday and it would not pass Safety Check, got the notification to install 17 which I did via the app
Installed without a hitch and Safety Check all passed with no issues
Hi people,
I've been struggling with this for the past 2 days and I'm trying really hard not to give up
I downloaded the stable rom from the MIUI website (for Mi Note 3 aka jason), installed it successfully via MiFlash, and tried flashing Lineage after I did a factory + data + system + cache wipe. It ended with me getting the dreaded error 7.
A bit later, I realized I had to get the dev build from the MIUI website and flash it before flashing Lineage OS. So I did - I updated to MIUI 10 using the dev build, made sure it was working and tried flashing Lineage OS on top of it (after wiping the partitions I mentioned earlier, following the Lineage OS instructions).
So eventually I got it to work - sort of.
Lineage OS is booting properly, but the device freezes before it can find any wifi networks to connect to (and then reboots), and that's why I think the culprit is the modem.
So, a few questions -
1. did it happen to anyone else? I searched endlessly but came up with nothing
2. If it is a modem issue - where can I find a working one? I looked it up and found nothing
3. If it isn't a modem issue - what should I do?
If I'm doing anything wrong - please tell me. I'm flashing custom roms since 2011 and this is the first time something like this has happened to me.
Thanks for all your help!
Hi, first of all you need an unencrypted phone - Format data in TWRP (3.2.3.1), then wipe system, data, cache, dalvik. Flash the Miui 10 china stable firmware 10.0.2 or 10.0.4, then rom, gapps and reboot.
Good luck, zaqm
zaqm said:
Hi, first of all you need an unencrypted phone - Format data in TWRP (3.2.3.1), then wipe system, data, cache, dalvik. Flash the Miui 10 china stable firmware 10.0.2 or 10.0.4, then rom, gapps and reboot.
Good luck, zaqm
Click to expand...
Click to collapse
You're a true lifesaver. Worked on the first try.
Thank you!
No problems ?
I recently installed pixel experience on my OnePlus 7 Pro Which was running OOS11.
I installed the latest plus edition with root. When the phone finally started I continued on with the setup but no wifi networks were shown. I thought it was just a bug and skipped the wifi step to do it later, but I later figured out I couldn't even turn on wifi it would just automatically turn itself off. And also the fingerprint sensor wasn't working. I reverted back to oos but is something wrong in my phone or the custom rom cause I saw videos with pe+ running on op7pros and nothing was wrong.
EDIT:I fixed it. I sideloaded ROM zip through adb without flashing it with twrp as usual.
Thanks
GamerX2010 said:
I recently installed pixel experience on my OnePlus 7 Pro Which was running OOS11.
I installed the latest plus edition with root. When the phone finally started I continued on with the setup but no wifi networks were shown. I thought it was just a bug and skipped the wifi step to do it later, but I later figured out I couldn't even turn on wifi it would just automatically turn itself off. And also the fingerprint sensor wasn't working. I reverted back to oos but is something wrong in my phone or the custom rom cause I saw videos with pe+ running on op7pros and nothing was wrong.
Thanks
Click to expand...
Click to collapse
Did you factory reset and wipe cache and dalvik cache in recovery after flashing Pixel Experience? When switching from stock to a custom ROM, not doing these wipes will cause issues when you boot into the new ROM.
Droidriven said:
Did you factory reset and wipe cache and dalvik cache in recovery after flashing Pixel Experience? When switching from stock to a custom ROM, not doing these wipes will cause issues when you boot into the new ROM.
Click to expand...
Click to collapse
Yes, but it's ok cause I fixed it. I sideloaded ROM zip through adb without flashing it with twrp as usual.