Related
Hi there, first off please forgive me if I get any terminology wrong - I've been learning way more about this than I ever intended...
I have a Galaxy Note 4 (SM910F / trltexx) that's causing me problems with custom ROMs - the phone gets to various points of the startup process, then either shuts off or reboots.
I'm posting this in the Note 4 forum as it happens with all the following ROMs:
- LineageOS 14.1
- Resurrection Remix 5.7.4 / 5.8.0 / 5.8.3
I assume that either there's something screwed up about the phone itself, or I'm missing something fundamental about what ROMs I'm installing.
When I first install the OS (adb sideload), it will boot up the first time around just fine.
On occasion (with all of the above) the phone has gotten all the way to the initial configuration screen (e.g. select a wireless network). I've tried all types of wipe and format/reset, both clean and dirty flash, no difference. The point to which it gets in the boot process seems random. When the phone is connected to a charger, it will try to reboot. If it is not connected, it just shuts off.
Stock Samsung firmwares (5.0.1 and 6.1.1) with stock recovery all worked fine.
Recovery is TWRP v2.8.7.0 (that's the only one I could get running, 3.x would not start up)
I've recently had the screen replaced, the shop did a poor job (my proximity sensor started acting up, I first tried replacing it, then tried the electrical tape spacer trick, which worked.) I'm also using an aftermarket Anker battery, for what it's worth (they're great, btw).
Any ideas? As mentioned it seems to boot ok with stock firmware, but I don't want to run stock because that's no fun.
Thanks for any ideas!
Current Information
Hi there, UltimateROM is AOSP-based ROM with some features and optimizations added.
Everything I do with UltimateROM I always test personally on my phone, but anyway...
Code:
#include <disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modifications, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
What's working:
RIL (phone/SMS/3G)
Video (playback & recording)
Audio (playback & recording)
GPS
Wi-fi
Bluetooth
Camera (Front and rear)
2D/3D HW Acceleration
USB, MTP, ADB
all native tethers (Wifi/BT/USB)
external storage
What's not
Vibration doesn't work (disabled temporarily due to an userspace vibrator driver issues)
Formatting SDcard as adoptable storage will make it unusable
MTP bug with doubled folders in sdcard root folder
ROM features:
Dark Marshmallow Theme
long volume press to skip track
PA Pie control
SlimRecents / improved AOSP recents
Re-added task manager
Navigation Bar
System UI tuner
expanded desktop
storages are swapped by default
extended reboot menu
customizable button backlight settings
Viper4Android FX
superuser embedded
Download
UltimateROM
Installation
before installation make sure you have a TWRP recovery
install latest chrono kernel
reboot recovery
install ROM
install chrono kernel again
If you proceed with installing GAPPS, you might have running out of space on /system partition. If you are planning to flash Gapps, you're likely need to use sdcard repartition (see below how to). Below is installation sequence with the repartition of the internal sdcard:
like before, make sure you have kernel with TWRP recovery inbuilt
install latest chrono kernel
reboot recovery
flash ReParted zip. This will wipe system, data and cache partitions!
install ROM
install chrono kernel again
*please note a possibly undesirable effect of the repartition: cache partition will be decreased to 15 MB and some ROMs that rely upon this partition won't boot. To restore original sdcard partition layout, flash stock 4.1.2 ROM (with PIT file).
Sources:
https://github.com/UltimateROM/android_manifest
Thank Yous
SergeyL - many-many thanks for an initial set of patches, device tree and TWRP 3.0.0.0! Also thanks for helping me implementing some features to this ROM.
JDCTeam, BenzoROM - thanks for great cherry-picks!
MWisBest - this project was heavily inspired by his FML (Fork My Life) ROM
OptiPop - an initial set of optimizations that the currently used by me is based upon
@Meticulus - thanks for his great contributions on our devices!
@AGONTUK - thanks for an initial Marshmallow bring up!
@nieltg - Sources for Galaxy Ace 2 device
@golden-guy - thanks for great cherry-picks !
@TeamCanjica - vendor and hardware sources
@Unjustified Dev - Audio fixes
Google
CyanogenMod
AOKP
SlimROMs
EuphoriaOS
OmniROM
AOSPA
Viper4AndRroid Team
And many other devs, I could forget (please write me if I did so).
Special Thanks:
@isaak, @enkflr, @Pdevo, @prometej-zg for donating this phone!
[*]@S.AMU for providing FTP-Server
XDA:DevDB Information
UltimateROM, ROM for the Samsung Galaxy S Advance I9070
Contributors
ChronoMonochrome, SergeyL, JDCTeam, OptiPop Team, BenzoROM, OmniROM, AOKP, CyanogenMod, SlimRoms, AOSPA, Temasek.
Source Code: https://github.com/UltimateROM
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP recovery
Based On: AOSP, LineageOS
Version Information
Status: Stable
Created 2018-03-10
Last Updated 2018-08-20
Misc
Vibration fix
Due to issues, vibration was disabled on 10.03.2018 build.
In order to fix this, follow these steps:
install chrono kernel r5.8.2 or higher
remove file /system/lib/hw/vibrator.montblanc.so
reboot
Reserved
Changelog
20.08.2018 - build #2
sources update
switch to opensource sensors
switch more device libs to open source base
unified codina / janice build
10.03.2018 - build #1
initial release
You are a legend! Will take some more time to test your kernel and I will flash this as soon as possible, really excited
https://github.com/Epirex/android_device_samsung_janice/blob/cm-13.0/vibrator/vibrator.c
This code in device tree was for vibrator issue.
PolishVodka said:
https://github.com/Epirex/android_device_samsung_janice/blob/cm-13.0/vibrator/vibrator.c
This code in device tree was for vibrator issue.
Click to expand...
Click to collapse
Sorry for the stupid question, but how to apply this fix? I've tried using this source instead of vibrator.c from hardware/libhardware_legacy repo, but there were the same issues.
Should be as you said, replaced vibrator.c from libhardware_legacy Rom source. This code was the same for Janice from JB 4.2 and above as I remember. When I was made CM13, this fixed continuous vibration after Rom boot up on Janice.
Are u enabled vibrator driver in kernel config? Driver is diffrent than Codina's one.
Maybe something in build process. Try to remove first compiled binary in hardware/libhardware-legacy/libhardware_legacy.so and build again make <device> libhardware_legacy.
Dear ChronoMonochrome. I am SOO GLAD Thank you.I thought Janice is dead! Thanx a lot ?(It is still my main phone..)
What's the best ROM for this device that i can use as daily driver?
Vibration doesn't work mean totally unable or just keyboard vibration?
Recognized said:
Vibration doesn't work mean totally unable or just keyboard vibration?
Click to expand...
Click to collapse
Vibration is disabled totally on this build. But don't worry, it's a temporary solution I had to accept, so that I can work on other stuff in the meantime.
@ChronoMonochrome I followed the exact sequence reported in the main post, but I guess something must be wrong.
I started from a freshly installed LOS 11 by epirex, latest october build, everything wiped, then I proceeded flashing chrono kernel before going to flash UltimateROM and chrono kernel again.
At this point, as happening coming from stock 4.1.2 + CoCore R24, I can't get to recovery and instead obtain a bootloop that again need me to do an odin restore.
Am I the only facing this issue? doing something wrong?
Pdevo said:
@ChronoMonochrome I followed the exact sequence reported in the main post, but I guess something must be wrong.
I started from a freshly installed LOS 11 by epirex, latest october build, everything wiped, then I proceeded flashing chrono kernel before going to flash UltimateROM and chrono kernel again.
At this point, as happening coming from stock 4.1.2 + CoCore R24, I can't get to recovery and instead obtain a bootloop that again need me to do an odin restore.
Am I the only facing this issue? doing something wrong?
Click to expand...
Click to collapse
It's possible that there's a bug somewhere in the current installation method. I will review this as soon as I finish working on the kernel stuff. It's not necessary to flash a whole stock firmware image each time after you lose recovery mode working, you only need to flash a stock kernel.
In my experience, after flash most of Epirex's Rom will have bootloop in samsung logo, if u don't want go thru odin.
Easier way is just need flash leggera rom and proceed to recovery/other rom.
That's true, the problem in my situation is I can't get to recovery, so flashing leggera wouldn't be possible.
I solved following chrono suggestion, packing stock tar file with just kernel, so without the need of a full stock system flash from odin, but just the kernel/stock recovery.
Vibration fix
Vibration fix
Due to issues with an infinite vibration, a vibrator HAL was disabled on this ROM.
Until the next update, there is a fix to this issue:
install chrono kernel r5.8.2 or higher
remove file /system/lib/hw/vibrator.montblanc.so
reboot
Deleted
New build is up!
Changelog
20.08.2018 - build #2
sources update
switch to opensource sensors
switch more device libs to open source base
unified codina / janice build
Thank you so much chrono, just installed your new update, it took so much time to me to install the rom (by latest CK twrp recovery) but anyway it finished and booted fine.
Now I will be using it for a few days, had to do two reboots to have everything set up and working (got some issues with browser, music app and file manager not starting after first boot, while media scanner started working after the second reboot).
It seems smooth to me as the build #1, for this little first impression.
Will take some time to use it and report
UPDATE 31.08.2018
Ok, so far I am using it for days now and I can say I didn't found major probles at all, I kept everything as much stock as possible and it is fine.
To me seems like wi-fi signal strength is a bit lower than what I was used to, but need further days to say this safely (wheater conditions can influence this).
Multitasking is globally good, had some little glitches some times, I think this can just be tweaked a bit indeed by the user, on the base on what's the use of his terminal.
Had some troubles with gps when on mobile network, like it took too much time to get the fix and aborted, while this didn't happened when on wifi connection (a-gps related?).
Anyway I don't found these some important or unfixable issues at all and I am very happy with this update, I am using you rom without google apps (Opengapps) and I can say it is just fantastic.
Thank you Chrono
Hello, please tell me the solution to the problem with the auto-rotate screen. and the camera does not work at all. The rest of the firmware is excellent!
I have an SM-N900V (Note 3, Verizon variant, hltevzw).
Detailed timeline:
- I flashed it back to firmware OB6 using Odin 3.09.
- I rooted it using ArabicToolApp.
- I used this tool to unlock the bootloader
- I installed a build of LineageOS 14.1 for hlte
- It didn't recognize the SIM so I did a dirty flash of this build of LineageOS 15.1 for hltetmo on top (hltetmo actually has different hardware than hlte, and the correct one for SM-N900V)
- Messed around with the APNs until it recognized and connected to Verizon's network. I DO have functioning SMS and LTE data, but I have not tested phone calls yet
- Messed around some with SuperSU in system- and systemless-mode. Bricked my device more times than I could count, then unbricked over and over using SuperSU's impeccable installer. Messed around with this quite a bit
- Also messed around with Xposed some. The OS is too unstable to run Xposed Installer correctly, so I uninstalled it
- Removed SuperSU, installed Magisk. Phone now passes SafetyNet
So, my phone now runs 8.1 and a Lineage build from 9 days ago. Cool. But, if I was satisfied I wouldn't be making this post. There are multiple instances of the same kind of "app freeze" - App screen freezes, sometimes it'll go completely black. Interactivity doesn't work, obviously, the app is completely frozen. Hold Back to kill doesn't work (Application Killed toast shows, but nothing happens). ANR (when it comes up) Close doesn't work. Home button works and brings me away from the app, but it's still there. Swipe away in Overview doesn't actually kill the app. Even in App Info, Force Stop doesn't work. The app is forever frozen. Tapping the icon from the launcher no longer does anything, it doesn't even bring up the app. The app is permanently crashed and inaccessible until a reboot.
Issues:
- Sometimes when booting the phone will not recognize the SIM until a reboot. As in, "No SIM" message and everything
- Sometimes it will get stuck at boot, I have foxy-boot installed, so I can see the logs. I don't remember what it was all about, if it comes up again I'll update the post
- Google Chrome sometimes crashes when trying to download a file. I've gotten my phone to self-host before, but this issue always seems to come back, and when it does Google Chrome ALWAYS crashes when trying to download a file. App Freeze
- Netflix installs and logs in but freezes at the "can't connect to service (-9)" message. App Freeze
- Certain apps like NativeScript Playground get stuck at the splash screen. App Freeze
- Xposed Installer did this when opening the Settings, whether Xposed was installed or not. App Freeze
- F-Droid also sometimes crashes, although it's somewhat arbitrary, I can't reproduce it reliably. App Freeze
I have tried reflashing the ROM, flashing Xposed uninstaller, reinstalling Magisk, none of it seems to work. I have TWRP 3.3.0 so I can do pretty much anything that doesn't involve the SD card (the SD card is probably broken in hardware, it's so read-only that Android and TWRP both can't write to it at all, but they can both read the same half-broken filesystem).
I fear that this OS is just too unstable for the phone and there's nothing I can do. I sincerely hope this is not the case.
Try other ROMs or perform a clean installation.
Make sure you are on PL1 bootloader/modem.
Currently using Resurrection Remix v5.8.5 Nougat because it was the last Android version for this device with working Bluetooth calls but if you don't use that feature you could use their Pie version as well.
RR ROMs are solid and work extremely well.
Do a clean installation via TWRP if you go this route.
terminator911 said:
Try other ROMs or perform a clean installation.
Make sure you are on PL1 bootloader/modem.
Currently using Resurrection Remix v5.8.5 Nougat because it was the last Android version for this device with working Bluetooth calls but if you don't use that feature you could use their Pie version as well.
RR ROMs are solid and work extremely well.
Do a clean installation via TWRP if you go this route.
Click to expand...
Click to collapse
I did a clean installation of RR 6.0.0 (Android 8.1) and it works a lot better than LineageOS did, with even more configuration options. I really really hate Pie and its gesture-based gimmicks (Screw you Google for copying more of Apple's bad design decisions), so I assumed Oreo would be more stable, but the ROM I installed still has crashing apps. Google Chrome still won't download most things (I've gotten it to download before), trying to change the accent color crashes the 'LineageOS Settings' app, and F-Droid is seriously messed up, but most other things are stable, including the Verizon network which required no pesky APN setup.
I'm on the OB6 bootloader/modem, is that a problem? I doubt that would be an issue, but I can always back up and reflash via Odin. The cool thing is that I installed a patch to TWRP which backs up /data/media along with everything else, after installing the custom ROM. So, really, I can do anything and be perfectly fine. There's, AFAIK, no way to ruin the phone unless something exploits the eMMC brick bug.
If there's another ROM you'd recommend me install, I'd be happy to try it out. I would really like to have a stable OS on here, where Chrome will work and download files. I'd also love Camera2 API since the phone has the chip for it (Snapdragon 800), but none of the ROMs I have support it and there's been no discussion online other than some years-old threads with no answers. I know there have been some articles online listing Note 3 as a phone that'd support Camera2 API with a software update. Would updating the bootloader/modem do anything on that front?
I would upgrade to PL1 bootloader/modem for your device. This is what I have and have had 0 issues. I'd recommend you trying the Samsung Internet browser over Google Chrome; it's much better in my opinion.
You can find the modem here:
https://androidfilehost.com/?w=files&flid=160694
As far as ROMs are concerned you can either try the Nougat version of RR which is what I am currently using as my daily driver with no issues at all including Bluetooth calls:
[ROM][HLTE\TMO\CHN][OFFICIAL]*** Resurrection Remix N 5.8.5 ***[13.03.2018]
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
See here to check whether or not your phone has the Camera2 API capabilities; if not use OpenCamera.
https://www.androidexplained.com/camera2-api-support/
terminator911 said:
I would upgrade to PL1 bootloader/modem for your device. This is what I have and have had 0 issues. I'd recommend you trying the Samsung Internet browser over Google Chrome; it's much better in my opinion.
You can find the modem here:
https://androidfilehost.com/?w=files&flid=160694
As far as ROMs are concerned you can either try the Nougat version of RR which is what I am currently using as my daily driver with no issues at all including Bluetooth calls:
[ROM][HLTE\TMO\CHN][OFFICIAL]*** Resurrection Remix N 5.8.5 ***[13.03.2018]
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
See here to check whether or not your phone has the Camera2 API capabilities; if not use OpenCamera.
https://www.androidexplained.com/camera2-api-support/
Click to expand...
Click to collapse
Excuse me but custom ROMs don't have "the Samsung Internet browser". Additionally the modem shouldn't cause app crashes (if it does, correct me please).
I might try the Nougat ROM. Bluetooth calls don't matter to me, but stability does. I just kinda really like Oreo and all its customization options but it may be too new for this old phone from 2013. It still works as a phone though, Messages and phone calls work fine, so I may just deal with it.
I use Open Camera, and I've tried multiple Camera2 API enablers. The phone has a Qualcomm Snapdragon 800 and the necessary links (in hardware, between the camera/other things) to support Camera2, but nobody seems to have tried it. Probably because the Verizon Note 3 is really locked down, and can only be rooted on a special version of the samsung ROM, and can only be bootloader-unlocked via the eMMC brick bug... There are Magisk modules for Camera2 on Exynos-based devices, but none for the Verizon Note 3 AFAIK.
I just found out that RR 7 officially supports `hltetmo`, but RR 6 doesn't. That's kinda sad, I hate Pie, but I might try it...
I've had the SEPL stuff before, that's the one that can't be rooted. I suppose I didn't consider upgrading again after I unlocked my bootloader. I'll try SEPL1 firmware again, but with a custom ROM...
You can install the Samsung browser from the Play Store. Again, highly recommended.
As far as SEPL1 just update the modem to it; that shouldn't cause any issues but it will ensure your SIM is recognized and data works with the latest ROMs. That is one requirement you will see listed on all of these ROMs.
Not sure which one you are trying to install but here are all the Resurrection Remix versions:
Nougat:
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
Oreo:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrection-remix-n-6-0-0-t3748689
Pie:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrectionremix-v7-0-0-t3894244
If you don't care about Bluetooth audio during calls then you can safely use Oreo and Pie options.
terminator911 said:
You can install the Samsung browser from the Play Store. Again, highly recommended.
As far as SEPL1 just update the modem to it; that shouldn't cause any issues but it will ensure your SIM is recognized and data works with the latest ROMs. That is one requirement you will see listed on all of these ROMs.
Not sure which one you are trying to install but here are all the Resurrection Remix versions:
Nougat:
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
Oreo:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrection-remix-n-6-0-0-t3748689
Pie:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrectionremix-v7-0-0-t3894244
If you don't care about Bluetooth audio during calls then you can safely use Oreo and Pie options.
Click to expand...
Click to collapse
Yeah but, data and calling worked fine on the LineageOS and RR roms, so there's no reason to update the modem.
Besides, I flashed SEPL1 6 times using Odin (multiple times by flashing, rebooting directly into download mode and flashing it once more) and it doesn't want to update. Still on OB6. On the latest (official Pie) RR rom, data worked on first boot but doesn't work anymore (I'm going to mess around with the data settings until it works), but I have no reason to believe that my phone needs a modem update to function.
I did, many times, make calls to various phone numbers and they all worked flawlessly. SEPL1 is therefore not needed if that's all it does.
And I do know about all the Resurrection Remix versions: One is Nougat from their archive, one is the Oreo version I had installed just yesterday before flashing Pie, and the other one is Pie which is now officially supported.
I am currently working on getting RR7 to work, it's only crashed a few times, and I don't even remember what those times were (I think it was using the Back button in Overview/Recents at the same time as the Overview button?)
When updating modem via Odin you have to pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot. If you look at the ROM threads for anything newer than Android v5 they all recommend updating to the latest bootloader & modem for your device which in this case is PL1. This can be to prevent crashes/no signal /no SIM, etc...
Are you dirty flashing these ROMs? I have never experienced any crashes with any of the RRs on my phone but I always do a clean install and make sure to also delete the "Android" folder on my SD Card via TWRP after doing the "Advanced" wipe and deleting everything listed there except for the External SD Card.
terminator911 said:
When updating modem via Odin you have to pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot. If you look at the ROM threads for anything newer than Android v5 they all recommend updating to the latest bootloader & modem for your device which in this case is PL1. This can be to prevent crashes/no signal /no SIM, etc...
Are you dirty flashing these ROMs? I have never experienced any crashes with any of the RRs on my phone but I always do a clean install and make sure to also delete the "Android" folder on my SD Card via TWRP after doing the "Advanced" wipe and deleting everything listed there except for the External SD Card.
Click to expand...
Click to collapse
"pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot"
So...
- Reboot phone into Download mode
- Pull battery while in Download mode
- Flash thingy
- Reboot back into Download mode
- Flash thingy again
? That will be very difficult to do with my dodgy charging cable that doesn't like being repositioned...
I do that without pulling the battery, but I could try it with.
I'm downloading the full SEPL stock image to flash. Once that's done, I'll flash it, reflash TWRP, restore my backup, and see if the baseband has updated.
And no, never dirty flashed the ROM. Always completely wiped data, system, cache and everything. I always backup first. I currently have 3 backups: Lineage OS (before installing RR), RR6 (Oreo), and RR7 (right now before that stock image I'm going to flash).
My external SD card is nonfunctional and read-only with some trash files from the previous phone.
I flashed the stock SEPL ROM. Baseband still didn't change. Restored from backup, SIM now works. Network is detected, SMS and data both work reliably on all reboots.
I will mention that I did brick my phone by using Odin to erase the eMMC, but I fixed that from TWRP, and now everything works flawlessly. There are still some app crashes, but most things are very stable. Camera2 API still nonexistent, which is sad because I got used to it on my old phone, but I shouldn't hope for it.
I've been using LineageOS 15 (Oreo) for about two years. A few days ago, I flashed the stock Oreo ROM and then the stock Pie ROM, to see how the stock Pie ROM looks like. After this, I flashed LOS 16 (Pie) and found that there is no sound during phone calls. When I dial someone, there is no sound of the ring going through, and once the other person picks up, again no sound either way. Call recording during this time gives a file with no sounds. I played a Youtube video and it plays with the audio working; I also used the sound recorder to record my voice, and it recorded the audio, so I doubt this is a hardware issue (unless calling uses different hardware). Everything else works.
After this, I have flashed LOS 15 Oreo again, but it didn't solve the problem. I've tried restoring old working TWRP backups, but the problems remains. Today, I flashed the stock Android 10 ROM, but once it boots, it gets stuck at the Zenfone logo. After this, I flashed the CrDroid Android 10 ROM, but again, no sound during calls.
When flashing the various ROMs, I wiped everything (Dalvik, Cache, System, Vendor, Internal Storage) - everything except the Micro SDCard and USB OTG, so that nothing of the previous ROMs remained, and then flashed the new ROMs from the SDCard. Also, the touchscreen doesn't work when in TWRP, so I have to use an OTG mouse.
While searching on google, I came across a post on the XDA HTC 11 thread about flashing dsp.img, and I asked that person, but he was not able to help with this phone. Here's his post:
[ROM] Unofficial Lineage 16.0 (updated 2021-4-18)
Post 1 - Introduction, download, and changelog Post 2 - How to report bugs Post 3 - How to build LineageOS from my sources Disclaimer /* * Your warranty is now void. * * We are not responsible for bricked devices, dead SD cards, * thermonuclear...
forum.xda-developers.com
I've been stuck for almost a week now. Please help.
Edit:
I was able to solve the problem by following @AVinaSh_S's guide here:
[GUIDE] [UNBRICK] [BACK_TO_STOCK] Flash Stock ROM - Relock Bootloader - Remove TWRP
NOTE : PROCEED AT YOUR OWN RISK. Guide tested successfully to flash Stock WW-15.2016.1810.334 on primary device. Also I will try to help out in case of issues. This GUIDE is useful to achieve following, Unbrick your device Flash Stock Rom...
forum.xda-developers.com
Got a huge weight off my head.
Hi, after attempting to enable encryption I get an infinite boot loop animation, and after I force a hard reset (keeping the power button pressed) the phone boots back to normal as if nothing happened. This means that encryption was not even started (otherwise it would be needed to format partition again if the process was interrupted).
What are my options here? On previous Android versions, whenever I came across a Rom that didn't support encryption, I would just flash a stock recovery image alongside the custom rom and try encrypting again, successfully. However, there are no Android 11 stock recovery images for this device (it got abandoned in Android 8.1 I believe), so this isn't an option anymore.
Unfortunately this ROM doesn't seem to have a dedicated thread here on XDA and people on their Telegram channel have not been able to provide guidance so far...
Any tips are appreciated!
ROM: PixelExperience Plus 11 (Android 11) version 2021.05.14
Device: Moto G5 Plus (potter, XT1685)
Recovery image: TWRP 3.5.2_9-0-potter
I have found no v11 or v10 roms which work with encryption (even when they say they do). I have not tried many v9; Your answer is to go back to stock 8.1 and everything will work again (but you'll be on v8):
[Oreo][Stock][Rom] TWRP Flashable Stock Builds
About this project This project provides repackaged Stock Oreo roms that can be flashed by TWRP. Modifications from stock are listed below. As we are now moving into the Oreo world, I've decided that now is a good time to make a few changes...
forum.xda-developers.com
edit: note that i'm on xt1687 (usa) model of potter
edit2: I just tried Arrow v10(official) and it encrypts (after a number of reboots; give it time)
bravo97 said:
edit2: I just tried Arrow v10(official) and it encrypts (after a number of reboots; give it time)
Click to expand...
Click to collapse
hi, in the case of PE+ 11, it just goes to reboot the first time and stays in loading android screen forever (waited a couple hours last time), so I think "giving it more time" wouldn't solve it.
Good to know there's some Rom compatible with encryption though, although it's android 10... I also got a hint that crDroid 11 may be compatible with encryption on potter.