Hello All.
I have OnePlus One with CM12 on it. I use CyanDelta to make fetch the nightlies from the server and install. This is working since the day i bought the phone. However, for some reasons i was unable to update the My phone using CyanDelta from some time.
I downloaded the latest "cm-13.0-20151130-NIGHTLY-bacon.zip" from official download page of cynogemod and imported the same on CyanDelta and installed it.
After the installation as per normal process it ran the updates and rebooted the phone.
after a long process of rebooting it gave an errors "SystemUI Crashed" and it is stuck there only.
i am unable to use my phone now as i can't see excpet this error. I have 2 options, "report" and "ok". whatever i press it is the same.
I have Very Very very important data and apps installed on my phone and i don't want to loose anything from there. As reinstalling app again will cause loss of very important data too. I don't know what to do but need to get my phone started.
Please help. I really really need steps to recover.
what if i go to recovery mode and select that same or another "*.*. NIGHTLY-bacon.zip" of version 12 and install from there.. will that remove all my Apps ?
Please advise.
So I'm definitely not an expert at all, but I am going through a similar situation as you. I believe the problem is from the fact that CyanDelta installed android 6.0 (marshmallow), but it didn't install the gapps 6.0, the gapps compatible for android 6.0. This is what maybe causing the crashes (Conformation of this would be appreciated). As for what to do about restoring your data I'm currently trying to figure out what to do my self. I was able to get in to twrp and I backed up my data then I connected my phone to my computer via usb and transferred the back up to my pc. I'm not sure if I can get back my data specifically my sms through the twrp back up, but I'll update you if I can so you can follow the process if you have twrp.
So here is situation.
Phone been running 8.x version of havocos for months, however I was never fully happy due to broken usb tethering and random lockups (blue light freeze).
I decided to work on the phone 2-3 days ago, this involved doing a manual backup of all of data/media, and a nandroid backup. As well as some exports of configs in tasker etc.
I then flashed OOS stock, and nolimits, discovered tethering was still broken (yet it works with same sim in samsung galaxy s7 and hauwei).
This was the only issue tho, everything else was functioning as expected, phone was still fast.
Then I needed quick access to something that was on my phone from havocos, so decided to do a nandroid restore, this nandroid backup had all partitions ticked. The restore I also had all ticked.
The restore failed with an error 255 during data restore, I googled and found out is a nasty known bug for 2 years on TWRP, this backup was done on 3.2.3, I know now is a newer 3.3.x where this particular bug with corrupt backups might possibly be fixed.
I decided to try and boot havoc anyway but it boot looped, so I then went back into TWRP, and restored the vendor partition which was skipped. As it stopped on data, still boot looped, but also now this created a device is corrupt error on every rom boot even on stock OOS.
I spent ages trying to fix this error and during the process, discovered my phone no longer can be detected in flash boot as a com device in windows so currently the phone cannot be used with the MSM tool.
Eventually I reflashed stock using a flash-all script from here, and also put back on twrp using that script, and noticed even more issues that were not there before.
1 - phone is now much slower, stock before booted in one second after first boot, now its way way slower. Over 10 seconds so 10x as slow.
2 - I think before was a cache partition but is now gone. Supposedly these arent a thing anymore tho.
3 - nolimits zip will no longer flash with an error 1, I did exact same process as before but simply doesnt work now, the twrp detailed log right before the error 1 says "Please install the latest Magisk!" which suggests its failing to detect magisk.
4 - camera app is way slower, and OOS feels slower, laggier in general than before the problem.
5 - MTP no longer works when phone is booted up, again this is stock OOS and even if phone isnt rooted no magisk etc. But still works in TWRP. Basically the device pops up, I can see internal storage, but the size information is missing, and is no visible files/folders.
From what I can see I think my EFS is fine, I see an imei number.
I did fix the corrupted device error using a reboot command someone posted in that thread, so that error is gone now at least.
Try to flash oxygen os beta version from the official download links, let it install the stock recovery, then boot into rom, finish the installation progress by just skipping it and then factory reset it twice from recovery mode.
after doing that and finishing the setup , try to take picture and see if its saves it to gallery ( if the picture delete it self try to factory reset it through recovery for 1 more time)
I think you have figured out whats wrong, it just clicked, and I went to post and found your post so sorry no reply yet.
Indeed the problem seems to be a lack of /data/media/0
I have multiple times wiped data, and twrp has been putting files directly in /data/media, I just discovered I Cannot even take screenshots, magisk cannot download modules as well.
So I guess the stock recovery creates this structure?
Pretty shocking that twrp doesnt fix this or even have an option to. I will report back and let you know how things go, thanks.
Issue still there after stock recovery reset, wow these phones are damn hard to work with.
Also it seemed to do nothing, no settings were lost etc.
So basically stock recovery even if I choose full wipe does nothing, there seems to be some kind of lock on the internal storage that anything made by one plus is refusing to write.
I wonder if this is due to the device is corrupt message I had before where it said the device can no longer be trusted.
I can confirm that files that are on there are now visible in file manager and root explorer. But file manager can do no writes. root explorer can create new stuff but cannot delete or overwrite anything there, gets access denied.
I propose to start over again following this guide, option flash-all-partitions.bat. Helped for me.
I already stated thats already been done.
I eventually got msm working. and that luckily worked.
@chrcol ..., but you've issues
chrcol said:
I already stated thats already been done.
I eventually got msm working. and that luckily worked.
Click to expand...
Click to collapse
In recovery, format data. Problem fixed. Wipe will never fix your problem but format will.
I have Xperia XZ running XZ_eXistenZ_Oreo_v8.0.0_patch_F883x_41.3.A.2.192. I have TWRP recovery on it. I flashed DRM, Safety net, Magisk 16.3, Magisk SE Linux Manager on it. Whenever I try connecting to the internet with magisk it crashes. Without connecting to the internet it works, but thats not really a fix, just a work around and even then the applications still do not work. however I noticed when I took Existence superuser rights off, it no longer crashed. This is not the main problem I am facing. I tried reading off of this website Look, I have flashed, re-flashed, done the advanced wipe, mounted data, wiped dalvik, cache. Am I missing a certain step that somebody could clue me into that perhaps I might be missing? Someone out there has solved it. Im new to magisk. I used to use SUPERSU but that was on an old phone that I cant remember the name of LONG ago. Where might I find the logs, I can post those and we can start getting somewhere
The module that did this was "liboemcrypto disabler" and was advertised as allowing DRM content to be viewed in full HD despite my bootloader being unlocked. It immediately put me in a boot loop after installing. I removed the magisk module from recovery but I was stuck in a boot loopstill and ended up having to wipe. I've done a full wipe, I've fully erased and decrypted the phone with ALL IN ONE tool and then installed a new stock ROM via fastboot. I then used TWRP to wipe EVERYTHING and then used ALL IN ONE TOOL to erase the phone and then used MSM tools to reflash a stock ROM and start from scratch while also choosing to wipe all data in the process. Netflix not working has persisted through all of this, it seems this module has touched a drm file that is normally out of reach in the wiping process / it's not replaced when doing a clean install. Another odd thing is that throughout this whole process, Nova Launcher stayed installed throughout all of the wipes. Any time I try to open Netflix it either says I need to update and clicking okay brings me to the play store where it tells me Netflix is not compatible on my device. Sometimes I get other error messages but it's always the same, Netflix doesn't work. The odd thing is I got it working on Pie in the process of unlocking my tmobile bootloader with the Android 10 DP3 so I could root it. Netflix actually worked for a second while I was on Pie, up until I updated to Android 10. This leads me to believe that the drm Android 10 is using is different from Pie and upgrading put me back to relying on the ruined drm file. I've even tried installing and uninstalling the magisk module that screwed all of this up hoping it would replace the original drm file but I've had no luck. This is such an odd problem. I had no clue any magisk module had the power to give your phone problems that literally can't be fixed through full wipes and reinstalls. I've tried removing netflix from ADB and reinstalling the apk manually but there's still no luck. The other streaming services that normally rely on this DRM are fine. If anyone has the slightest idea of what to do here I'd love to hear it! Are all drm files the same for everyone? If I were to aquire the drm file that was replaced while installing this thing could that possibly fix it? The file that is modified is under /vendor/lib/ and is named "liboemcrypto.so"
Hi everyone,
I hope some of you are still following up on this device or maybe my query is not too specific after all...
To give you some background: When I rooted my Zenfone 3 Ultra in April 2019 the storage was encrypted such that I had to enter a key each time I powered it up. After ~ 1 year or so I could not access the OS anymore after a reboot because it said the key I entered was wrong. So I went to twrp and did a wipe in order to set everything up again, this time not using device encryption. I noticed that after this wipe the flash light and third party apps using the camera would cause crashes (black screen or immediate reboot). I could live with it so far but recently I thought more and more often that it would be nice to finally use the camera in third party apps. So yesterday I had some time and decided to address the issue by doing a factory reset.
Now the factory reset did not resolve the issue. I remembered that when I had rooted the device (and everything was still working) I had created a nandroid backup in twrp which I then restored. I included everything in the restore which was offerd by twrp, i.e. Boot, Data (excl. storage), System and System Image. Still the same issue. I am not sure anymore if I created the one nandroid backup which I still have before or after rooting but when I boot up the device and install Magisk Manager, Magisk is shown with the version I installed back then.
According to the ZU680KL unlock/root thread unlocking is not possible anymore. However, I would like to keep root / be able to regain it. I assume the latest firmware (UL-ASUS_A001-WW-14.1010.1804.75-user.zip) as well as the corresponding boot.img and recovery.img which @ndi provided in this thread (thanks!) would allow me to go back further. However, I noticed that in my boot menu it says "DEVICE STATE - locked", which already makes me kind of nervous due to the unlocking issue above. I just don't want to try anything else on my own because I am afraid to do something foolish. So maybe you can help me with these two questions:
With everything being as it is, how could I start as clean as possible without loosing root / the ability to root again?
If I was willing to sacrifice root access, how could I proceed to bring everything back to stock?
Or maybe you have some other idea to fix the camera issue. Any help will be appreciated.
Many thanks!
Hello again everyone,
I decided to move on and go back to stock. Eventhough I was not able to maintain/regain root, there is an approach that might be applicable to our device as well. Also, I would like to share what I found out regarding my initial goals (i.e. camera issues and resetting a rooted device).
Camera issues: It seems to me that these appear on (some?) ZU680KL devices running Android 7 (Nougat). They can affect the flashlight or the camera in general, as you can read here. I decided to go back to the latest Android 6 (Marshmallow) realease as suggested in the same thread. The system no longer crashes when I use the flashlight or the camera is used by a third party app. However I sometimes still need to start the camera app in order to make it work in third party apps.
Going back to stock: A guide for the Zenfone 3 siblings can be found here. I went back to stock using TWRP and a MicroSD card (with boot.img, recovery.img and ROM zip file):
I first flashed the boot and recovery (i.e. TWRP) partition with the stock images for the ROM I was planning to flash.
Then I booted into stock recovery and flashed the ROM zip file. The key combination to get into stock recovery was a little weird ('volume -' followed by 'volume +' while keeping 'power' pressed). It had to be entered during the 'no command' notification that was shown after choosing recovery from the fastboot menu.
After successfully flashing the ROM, I wiped cache and data and rebooted. I ran into a "Dm-Verity in EIO mode" error (see attached). This error had already occured after my last try to restore a nandroid backup in TWRP but I could resolve it with the steps described in this youtube video and repeated (2.). When I think about it now I guess I should have started with (3.) right away because of the Dm-Verity issue.
Regaining root: I think this is something yet to be done but it does not seem completely hopeless.
I hope this can be of help if you face any of these issues.