Hello everyone,
First of all, I do apologize if this is a duplicated post, as I haven't found any threads on this topic.
I've been playing with Android for a long time (flashing custom ROMs, rooting, etc.). I recently bought a Nexus 5X because of its Nethunter support and ongoing OTA support (although Google recently retired OTA for this product). After flashing TWRP, rooting, and flashing LineageOS and RessurectionRemix, I felt like I would be satisfied and stop flashing custom ROMs for a while. A few weeks later (after I've just been done setting up the phone fully), I switched to Republic Wireless, which is a hybrid cell carrier, meaning it uses both WiFi and cell to send/receive texts and calls.
Now the way Republic works to authenticate and allow phone service, it needs to detect if the phone is running an official stock build, because obviously custom ROM's dont support FDN's (correct me if I'm wrong). I've tried flashing MultiROM (MultiBoot) on my Nexus, but when I boot into the stock OS, it doesn't seem to boot with the custom boot image. And the same thing happens with other custom boot images. I am wondering if this is AVB (Android Verified Boot) complaining about either an unsigned image, or the functions inside the image itself, for example "Disabling dm.verity" or "Disable forced encryption on /data", thus intervening with the stock OS boot routine.
The main question is, how would I be able to flash a custom boot/kernel without messing up my stock OS?
Here are some specs on my phone:
Model: Nexus 5X
Rooted with SuperSU 2.82-SR5 Systemless Boot
OS: Android 8.1; October 2018 Security Patch; Build OPM7.181005.003
Sorry if I am missing an important obvious fact. FRP, AVB, etc. is all new to me.
Thanks in advance!
Related
I keep seeing all over the forums that you have to update your bootloader to be able to install Marshmallow and Nougat... I just jumped directly from 4.4.4 KitKat to 7. 1 Nougat without any problems at all. Nothing has failed to boot or anything abnormal. I have not touched this bootloader since I unlocked it for KitKat custom rom in June of 2016. I have installed both Lineage and then switched to CM14, and considering flashing Resurrection to try it out due to a couple of bugs I have found in CM14 --- videos zoom into the upper left quarter in Facebook app regardless of dpi setting and screen rotation occasionally acts stupid. The latter could potentially be a hardware issue, though. The former is driving me friggin bananas!
So I am curious why tons of people say it is required to update the bootloader or rom updates won't work. And if it is that big of a deal, should I just do that now and switch on over to Resurrection or can I/should I just update the bootloader now? Does that have to be done when installing a fresh rom or can you do it whenever? There is nothing anywhere that specifies that info.
You are installing AOSP roms. Since these are raw android, no update is needed. If you install a TouchWiz rom, which is more "stock", then certain features, like wifi will not work with the wrong bootloader. Also, some security updates are included. It's a quick easy flash.
Hi guys,
I have been having issues with my Australian Moto Z PLay. I have been Romming for a while now and tried to first return the phone to stock using the adb method. Which didnt work (I cant remember why, I think I finished it all and it would only boot to bootloader or recovery). Then tried updating only the modem using this method https://forum.xda-developers.com/moto-z-play/how-to/update-bootloader-modem-to-flash-stock-t3818253 then I tried flashing a few ROM's
The issue now is that the phone turns itself off and on a few times a day. I have launcher crashed quite often and the battery seems to have less life in it.
In short I'm not too sure what I have done wrong. Maybe a few things. Can anyone help me get back to a point where I can install custom ROM's like before relatively safely and reliably? I have tried a few different rom's and had lots of similar issues with each.
ROM - AOSP Extended v5.8 Official
Android - 8.1.0
Baseband version - M8953_10238.63.04.83.01R
Kernel Ver - 3.18.71-OPN28.49-2-g04699f27af49
SELinux Permissive
Hardware - Moto Z Play purchase in Australia retail from Harvery Norman
Boot messages
"There's an internal problem with your device. Contact manufacturer for details" (appears twice, once before needing password, once after. Never needed pin code before)
Thakn you in advance!
....also lots of lag. I'm going someone can guide me to the modem etc settings that should be in my device
Hi team
I recently purchased an ex Demo HTC One M9 as a cheap replacement to my broken Galaxy S7 Edge, as soon as I received it I decided to flash TWRP and a new ROM on it. I was able to unlock the bootloader via HTCDEV.com easily enough and I was able to flash TWRP onto it without issue but when it came to the ROM's I ran into many problems.
Any version of Android that is Nougat or lower would not boot, the phone would go straight to the white bootloader screen every time. Oreo and Pie ROMs were able to boot but I ran into separate issues with them, I could not make or receive phone calls as the whole phone would freeze and there was no audio in from the speaker. I was also unable to play any videos in Facebook, YouTube, Snapchat etc.
I tried every single ROM available here on XDA and ran into these issues. I stupidly also did not make a TWRP backup of my system so it was quite hard to revert back to what it came from factory, I managed to get a stock Marshmellow running thanks to a User here posting a TWRP backup so thanks.
Is anyone able to help me with upgrading to Nougat? I would really like to get the Viper ROM working if possible, is it a known issue getting stuck in the bootloader menu every time?
I've tried just updating through the OTA process in the menu but it says there is no update file available.
Cheers
Hello Everybody,
I rooted my SM-G960F without problems few months ago. I tried LineageOS but I cannot cope with the camera quality. Then I tried Ambassadii Rom which was working great, till the phone started deleted some of the apps data.
For example, I downloaded maps on Here WeGo, after 1 day they were gone. Same issue happened with Spotify, every day I had to redownload all the playlist that I saved for offline use and often I ended up without music when travelling.
So I decided to flash the Stock Firmware again, but losing all the privileges of the ROOT (i.e. Magisk, Netflix, Samsung Pay, etc.).
I tried to repeat the root process to install Magisk, but I found out that the build number is 7CSJ3 and EX Kernel is not available yet.
Therefore I tried to downgrade the firmware first, however, I could not find any old firmware with binary 7 or above and hence it seems rooting is not possible.
Does anybody have a solution for any of the above?
Thanks.
Spanish ROM , find the suitable for you
Hi Zoira,
The only available rom is the 7CSJ3 and there is no EX Kernel available for that. All the other firmwares have a bootloader binary lower than 7, therefore I cannot flash it.
Any other solution?
Hello XDA people. I'm an enthusiast of flashing and testing android ROMs, but I am kinda rookie using this device.
The problem in question is that I cannot successfully flash any Android 10 and later ROMs on my device, I always face several problems after flashing and booting any ROM, such as the wifi's not working (got the exclamation mark on the icon), audio problems, mobile data increiblely slow, bluetooth and GPS issues, etc etc. I tried to flash official and supported ROMs like lineageos, evolutionx, pyxisos, havoc as well as unofficial roms, but I always get the same problems (the wifi issue is the problem that I want to fix the most)
I tried flashing the original MIUI firmware through recovery and bootloader method, I dirty/clean flashed the roms after and nothing, I also used factory reset, used OrangeFox, TWRP (official and unofficial versions) and I still have the same result. I tried every method I know and it seems I won't have the problem fixed. I don't know if it's that the firmware is not properly flashed, or if I deleted a partition. What can I do?
The device only works using the MIUI original firmare but I don't like it because of the bloatware and the waste of resources. I currently use MMX rom (a modified MIUI rom) in my device right now. It works well but It's currently outdated. I just want to use an AOSP based ROM and having my device updated. Please HELP ME!