Hi,
I'm quite new to operating with Android phones, anyway..
I had been running the stock MIUI 10 10.2.2.0 Stable ROM on my Redmi Note 6 Pro. I've decided to try PixelExperience ROM because it runs on Android Pie and I like design of pure Android. So I flashed twrp by MrR00t (it has to support Pie ROMs and it really worked), boot into twrp, canceled decrypting storage, wiped data partition, flashed disable dm-verity and force encryption, flashed pie firmware, rebooted to recovery again and installed latest PixelExperience.
Everything was fine (i mean camera worked) and I've decided to root the phone for changing emoji. I've changed them successfuly. And I wasn't fed enough so I was unhappy that the PIN is not 'entered' automaticaly (I mean after entering 5 or 6 numbers auto "enter" press). This feature provides GravityBox, so I've installed successfully Xposed for my device (not wrong version, I am pretty sure about that) and then wanted to install custom GravityBox for Android Pie (official is not avaiable yet). It needed two other modules installed before ('Magisk Riru Core' and 'Magisk EdXposed Beta'), I've installed them successfully, then I rebooted the phone and installed GravityBox from link given in the thread. Then activated GravityBox module in Xposed and rebooted for activating.
Unfortunately the phone soft-bricked, so I reinstalled PixelExperience and wiped Dalvik/Cache and rebooted to system. Camera stopped working (I mean camera app didn't even display any button, no settings, just black screen).
I have already tried installing stock stable MIUI ROM, beta ROM and camera doesn't work on either of them. Also tried hardware test and it stops working after trying to run camera test. No matter which camera (both front and both main doesn't work). BUT both LED flashes works.
Please, help me, I am out of ideas
btw. I know the issue seems to be physical, BUT it stopped working after flashing something.. Phone also bricked, I think there is some connection.. Thank you all for the time
EDIT: I have found out that it's caused by damaged file "persist" located in dir: /dev/block/bootdevice/by-name/persist. I did replace it with persist.img file extracted from fastboot version of latest pie beta ROM MIUI in twrp terminal. That file is probably responsible for system communication with all the sensors, as I read in internet, and Xiaomi devices are blocked to manipulate with it by just flashing ROM in fastboot (this function is called arb = anti rollback).
Related
Does anyone know what changed regarding wifi in Android 8 or MIUI 10?
I was happily using LOS 14 for a while (after having officially unlocked my bootloader at some point in the past, but became curios and wanted to try out the new MIUI 10. While I could not find anything official, I did find this chinese dev ROM (I DO NOT RECOMMEND YOU FLASH THIS). I flashed it, wasn't that impressed and then decided to try LOS 15 based on Android 8.
That was a bit too unstable for me, so I tried reverting back to LOS 14.
I did so using a backup I made to my pc (I did `adb backup` while in TWRP and selected every partition I think). After booting into LOS14, things seemed to crash an awful lot.
At this point I realized wifi wasn't working. It showed a MAC Address of 02:00:00 I think, but no networks were found. I tried restoring my phone using MiFlash normally. I then tried restoring it using Qualcomm's download mode. Older MIUI versions would not boot anymore (although I did manage to boot an old version of TWRP made for the pre-Nougat bootloader). I tried LOS14 again, and attempted using fastboot to erase various partitions (such as the bluetooth and modem partition, and then manually flashed the image again. Still no wifi.
Does anyone know what could have happened? My bootloader is still unlocked, and even downgrading the device to an old version of MIUI using Qualcomm mode did not make it work again? How come LOS15 and MIUI 10 are able to use wifi without problems?
tl;dr WiFi stopped working on any rom other then Lineage OS 15 or MIUI 10.
Hello! I have had my One plus 7 pro international running for months now, rooted, following this guide https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368. I had the OTA update notification for quite some time now, but I ignored it because I was lazy. A few weeks ago my phone must have auto updated however, as I started noticing banner ads again that adaway usually blocked, and I have had a few other minor issues like GPS taking longer to connect or find where I am, wifi disconnects, and google not understanding what it usually does. Phone still works just fine, just minor issues I didn't really experience before.
I would like to completely reset the phone to clean it up, and re root and setup TWRP again, but im not sure how to safely do that since my phone was updated improperly (automatically). I have magisk still installed, but the modules dont seem to be working properly. Rebooting to recovery will reboot me to one plus recovery instead of twrp. When I restart is still says my boot loader is unlocked, and some apps (like chase mobile app) still say my phone is rooted. Oxygen updater says im up to date on OxygenOS 10.0.3.gm21aa.
What would be the best option for me to clean everything up, get my root modules working again, and have the phone fully up to date and stable? Any information would be greatly appreciated.
follow the same steps you followed first time. Boot to TWRP flash magisk, No need to factory reset. Flash twrp again if you want and reboot to system
*SOLVED: see reply*
The ROM I used before was LineageOS [10.0] and used a custom ROM with Android 9 before that. Needed to unlock my phone, and couldn't do that on Lineage, and had troubles flashing firmware with Odin, so I ended up using FrankensteinS6. The Stock kernel seems to let me input the NCK, and unlock the phone. So that's luckily finally over.
For about 4 days now I've been formatting phone and trying again and again. FrankensteinS6 works, some other 6.0/7.0 ROMs work. But LineageOS now enters a bootloop, and Pixel Experience (9.0 and 10.0) and Evolution X 10.0 don't detect the SIM. The ones that don't detect SIM also show no IMEI, which was worrying at first because I though I lost a partition.
Possibly related, the ROM of Pixel Experience Android 10.0 for G920W8 will not install because (paraphrasing) "This device is zeroflte, this file is for zerofltecan, zeroflte***, zeroflte***" claiming that my phone isn't one of those models. I got this S6 from Bell Canada, and I still have even the sticker that says it is a G920W8, not G920F. However, the Pixel Experience ROM for G920F flashes fine (sans the main problem).
I don't know the exact LineageOS ROM I used before, but I've tried all of their 10.0 releases, tried redownloading, and I get the bootloop every time. I see some info online of flashing modem firmware, but... I don't even know where to start with that. As I mentioned at the start, Odin is crapping out. I couldn't flash firmware with it, because it would reject the phone right after I started flashing. Anything I could do within TWRP would be great. I moved it back to FrankensteinS6 for my sanity, I started doing this Sunday and I'm starting to repeat steps over and over hoping that it just solves itself.
I tried to keep this straightforward, and I'm sure I did a bad job. I can extrapolate on what I have attempted. Please tell me what I have to do to get an android 10 ROM working on this old beauty again.
I do not have all the solutions. As per my tests with my SM-G920W8. I have managed to find ROMS and try them out. I have only seen Nougat 7.0 ROMS to work almost flawlessly. NOT 7.1.2, important, 7.0 only.
I have also tested some Pie and v10 ROMS like Pixel Experience. The ROMS boot nicely but since I do not use a SIM card to call as I use SIP phone numbers and require WiFi. But that left asside, I came upon serious camera issues no matter what I try. Up to now, SamStock ROM is pretty much the best Stock ROM I found but I always need to run the Magisk UNINSTALLER before re-installing the latest Magisk version..
As for Kernels, well, Anything that is oriented with Lineage OS, I've had camera issues even with Nougat v7.0. So basically, the only ROMS I found good, as of today, for now, are stock ROMS v7.0. But, to do your tests, Even if you have a 920F ROM, you can download a 920W8 kernel as long as you download a kernel which supports your installed Android version. Also make sure to download the proper Stock or AOSP kernel (AOSP for LineageOS). There's not many but there's a few ones that work properly.
Another option is to download an AOSP ROM that works for W8 phones, unzip the file and grab the boot file inside corresponding to the W8 or T-Mobile version. You simply unzip your real ROM you want top install, replace the boot file for the one you got and rezip it. This made my phone boot properly for some F version ROMS but again, not without issues. That's why, I really suggest v7.0 Srock ROMS. I hope this helps you a bit. Again, you can have your own tests and other users may have other answers, but this is based off over 30 bootloops in my case of trying to mod a ROM for the W8 model. It's not easy to find a good one for Canada, I admit!!!
I flashed TWRP years ago, and I found out that I had a G920F version flashed. I don't know why Lineage allowed me to use SIM before, but rectifying this issue seems to made the SIM work in newer versions.
I don't know what the S6's predisposition to having crashing cameras is, but I have avoided this in the past by using custom camera apps, like Open Camera. This has saved me every time.
As for the boot loops... I think another thing that helped is that "format data" doesn't wipe the OS. When you are in recovery, having issues with bootloops in various ROMs, try advanced wipe, and wipe the system. It didn't fix right away, but the time I got Pixel Experience 10 up and running that was the trick.
Hi all,
Installing a custom rom on an XZ Premium; it's my first time dealing with this so its possible I missed something. I successfully installed TWRP and adb sideloaded the most recent Cherish OS rom. I was able to set up the phone with no issue, but upon rebooting for the first time back into system, it hits the boot logo, which animates correctly, but then hangs there indefinitely. I have wiped system memory, reformatted, and reinstalled, and the issue persists. I have also tried other ROMs. Arrow had the same issue, as did the Pixel experience, which leads me to believe that it's not an issue with the rom, but something with how I have configured the set-up.
I looked around for solution, but wasn't able to find much on the specific issue of only having issues on second boot, rather than initial. Any help would be appreciated.
I think your TWRP version is the Problem... (I think there were a lot of complaints about 3.3.?.? and higher) I had a similar Problem; TWRP wanted to use /data and if i formated the device, it would endless bootloop (I think because of the encryption the OS uses by default) So i decided to flash a older version (were this wasn't a problem) and I picked twrp-3.2.2-0-maple.img (maple because i have single SIM variant) and I didn't even needed to format the device and it still works (after i flashed Magisk and some other stuff/ "enhancements", that don't impact he OS) and everything still works smootly.
Maybe you should just flash a older version of TWRP (like 3.2.2-0) But i can't guarrantee, that it'll work on Pie(since i don't have it).
Hi,
kinda new to custom ROMs and running into my first real problems.
I installed TWRP, LineageOS 20.0, BitGApps Basic and Magisk 26.1 on my Samsung Galaxy S10e Exynos.
After setup everything works extremely well and fast. I installed Universal SafetyNet Fix, Viper4Android (programminghoch10/ViPER4AndroidRepackaged: A refined ViPER4Android installer. (github.com)) and Universal GMS Doze (gloeyisk/universal-gms-doze: Patches Google Play services app and its background processes to be able using battery optimization (github.com)). The phone still works fine and Viper4Android works too. SafetyNet also passes.
Now the problems arise. A few hours later and some reboots later, the phone won't boot anymore (maybe 20 reboots). I didn't even change any settings before the reboots. The boot animation plays and the phone is getting reset by a watchdog maybe. Also cannot use ADB during boot and the safe mode button combination doesn't work. I'm not experienced enough to understand the log files correctly. I already flashed the phone twice and the same problem occurred.
I attached some logs I could get from TWRP, but the main data partition is encrypted.
Full log files are here: logs.zip
Otherwise I'm extremely impressed with Lineage and would love to use it as my daily.
Thanks a lot for helping.
loriZyy said:
Hi,
kinda new to custom ROMs and running into my first real problems.
I installed TWRP, LineageOS 20.0, BitGApps Basic and Magisk 26.1 on my Samsung Galaxy S10e Exynos.
After setup everything works extremely well and fast. I installed Universal SafetyNet Fix, Viper4Android (programminghoch10/ViPER4AndroidRepackaged: A refined ViPER4Android installer. (github.com)) and Universal GMS Doze (gloeyisk/universal-gms-doze: Patches Google Play services app and its background processes to be able using battery optimization (github.com)). The phone still works fine and Viper4Android works too. SafetyNet also passes.
Now the problems arise. A few hours later and some reboots later, the phone won't boot anymore (maybe 20 reboots). I didn't even change any settings before the reboots. The boot animation plays and the phone is getting reset by a watchdog maybe. Also cannot use ADB during boot and the safe mode button combination doesn't work. I'm not experienced enough to understand the log files correctly. I already flashed the phone twice and the same problem occurred.
I attached some logs I could get from TWRP, but the main data partition is encrypted.
Full log files are here: logs.zip
Otherwise I'm extremely impressed with Lineage and would love to use it as my daily.
Thanks a lot for helping.
Click to expand...
Click to collapse
If it is an issue with the ROM itself, you will need to post your issue in the ROM thread where you got your ROM and see if there is something in the ROM that the developer of the ROM needs to fix in the ROM itself.
Hi, kinda new to custom ROMs and tried out Lineage and later Crdroid on my Galaxy S10e Exynos.
The OS works fine but after a few restarts the phone randomly bootloops and I can't find any way to fix it.
Currently installed is Crdroid recovery, Crdroid latest (the same problem happens with Lineage) with Android 13, MindTheGapps, Magisk 25.2
Magisk modules are Zygisk, Viper4Android and Universal SafetyNet Fix.
I attached some logs but I'm too inexperienced too read them correctly. It looks like the file
Code:
/data/misc_de/0/apexdata/com.android.permission/runtime-permissions.xml
is corrupted after a few restarts?? The bootlogo just repeats and nothing is happening. The logs say that the zygote process has crashed.
Does anyone know what to do? Thanks a lot!
Logs: log.txt
This used to happen on my Galaxy A50 on another ROM too, and since it's not an S10e problem it's probably a Magisk module