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.
Related
Like the title says, on every 5.1 ROM I keep getting random reboots. They happen indiscriminately, with no clear reason at all. Other people report no issues at all. On 5.0.2 I have no issues at all. I have no idea what causes it could be or no knowledge on how to diagnose it...I want to use 5.1, but if this keeps happening I don't think I can ?.
I've not had any issues with random reboots, been running euphoria rom (updating with each new build) and glitch kernel for weeks with no issues.
Assuming you're doing clean flashes, with no extra mods, and not restoring system data, yes? Its even possible that restoring app data from backups can cause weird things to occur at times. If you haven't yet, wipe everything and clean flash, restore apps only from play store, and see if it still happens.
Otherwise, maybe a specific app is causing problems? You could try and grab some logs to narrow down the cause, but I know that's very tough to do if the issue is intermittent and seemingly random. Still it is the only way to tell for sure what's happening.
Here's a guide on how to grab the different logs if that helps at all: http://forum.xda-developers.com/showthread.php?t=1520508 .
LucentBirch said:
Like the title says, on every 5.1 ROM I keep getting random reboots. They happen indiscriminately, with no clear reason at all. Other people report no issues at all. On 5.0.2 I have no issues at all. I have no idea what causes it could be or no knowledge on how to diagnose it...I want to use 5.1, but if this keeps happening I don't think I can ?.
Click to expand...
Click to collapse
The random reboots are caused by outdated 5.0.2 binaries, if you update to 5.1 it should mend it random reboots. Also if your ROM developer might or will update the ROM to 5.1 with the updated binaries!
Killah1994 said:
The random reboots are caused by outdated 5.0.2 binaries, if you update to 5.1 it should mend it random reboots. Also if your ROM developer might or will update the ROM to 5.1 with the updated binaries!
Click to expand...
Click to collapse
Well I know for a while that some 5.1 roms were using the 5. 0. 2 binaries because the 5.1 weren't released yet... And they never really said whether or not they updated the binaries or if they were even released...I updated my tablet to a 5.1 R_5 this morning and it hasn't rebooted all day...so maybe they have?
LucentBirch said:
Well I know for a while that some 5.1 roms were using the 5. 0. 2 binaries because the 5.1 weren't released yet... And they never really said whether or not they updated the binaries or if they were even released...I updated my tablet to a 5.1 R_5 this morning and it hasn't rebooted all day...so maybe they have?
Click to expand...
Click to collapse
5.1 binaries and factory image for this device were just rolled out today. This may indeed resolve your issues, but give the custom rom devs some time to catch up, they'll need to grab the latest source and post new builds for the latest binaries to be included.
Same thing here
I excitedly loaded up the 5.1 build on my 2013 wireless today. SAME ISSUE. I can't do anything .
I didn't wipe the device when I upgraded. I was rooted - unrooted / flashed / rooted using the Nexus Root Tooklit as I have since Jelly Bean. I used the option to use NO WIPE MODE to try and keep my apps intact.
Any help appreciated.
mrdrumsc said:
I excitedly loaded up the 5.1 build on my 2013 wireless today. SAME ISSUE. I can't do anything .
I didn't wipe the device when I upgraded. I was rooted - unrooted / flashed / rooted using the Nexus Root Tooklit as I have since Jelly Bean. I used the option to use NO WIPE MODE to try and keep my apps intact.
Any help appreciated.
Click to expand...
Click to collapse
in that case you should try wiping then flash the 5.1 factory image and see if it works.
PrizmaticSmoke said:
5.1 binaries and factory image for this device were just rolled out today. This may indeed resolve your issues, but give the custom rom devs some time to catch up, they'll need to grab the latest source and post new builds for the latest binaries to be included.
Click to expand...
Click to collapse
cm12.1. rebooted once today while using chrome.
Reboots better!
I concur with the messages I've been seeing. After several app updates over the weekend, culminating in some Chrome updates, the tablet seems stable. I haven't re-rooted it yet.
I wonder if something has to do with the "notification crash" error listed in the changelog for 5.1.1.
Either way, looking forward to 5.1.1!
Ever since the MM update, my wife's SM-T807R4 (US Cellular version) freezes frequently when browsing and using any app which requires touchscreen input. It's almost unusable unless one doesn't mind closing and opening the case every 2 or 3 minutes (or hitting the power button twice.) I have recently rooted it and disabled many of the Samsung apps as well as some Google apps we don't use. It hasn't helped. I have not yet flashed TWRP but I have instructions on how to do so.
I don't know if the MM update caused the problem or there's a hardware issue that just didn't seem to arise until after that update. In any case, I'd like to return to Lollipop and see if that improves things. Once TWRP is available, can I just wipe everything and flash the Lollipop ROM with TWRP or do I have to flash it with Odin? Anything else I need to do to prepare?
So i just updated my moto z play to OREO via the official OTA last month. Since then i've been experiencing bad battery life. I already did a factory reset and monitored the battery with just the stock apps installed and the battery bug "system ui' is always the culprit. Booted to safe mode and that bug is gone.
So here is my scenario
Safe Mode: SYSTEM UI bug NOT PRESENT
Normal Mode with NO third party apps: SYSTEM UI BUG STILL PRESENT
I can maybe conclude that it was the OREO update that was causing this. Maybe a corrupt download or something.
Issues i'm facing
1.Battery bug "system ui' always on top of my battery charts
2.Navigation bar changing positions each unlock, some say its an oreo feature to prevent burn in but when i booted to safe mode the nav bars are not changing positions. So which is which?
3. Wifi sometimes doesn't wanna turn on, if i hit turn on it just resets back to off regardless. Needs a phone restart to work again.
4. Interface sometimes freezes and lags while scrolling.
My question is that is it possible to re install the stock oreo update AGAIN even if i'm already on official 8.0? I'm not rooted and never did rooted my z play. Already did multiple factory resets but the same scenario above happens. Any help is appreciated, thanks!
I knew the soak test were out but did not know that Oreo release was available ota. It will change your booltloaders. Every time I google for oreo I get a bunch of problems listed but you may find more help there than here since this tends more toward custom ROMs. Make sure none of the apps you have added are loading things...
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
My whyred RN5pro come with global rom miui 10 with android pie I think ?
I unlocked the bootloader and flash PE pie latest version, it required pie firmware, and I flash latest pie firmware from https://xiaomifirmwareupdater.com/firmware/whyred/
After usage for half year, I decided to use oreo rom, there's a few reason.
1. I thought always keep update will make it more stable and safe. But I was wrong, the more I update the PE rom, the more unstable it was. After usage a few days, it will freeze and need reboots, sometimes it slow on animation.
2. I need call recorder, but android pie restrict this function.
3. The latest build now come with wifi drop or something, sometimes my internet access is unavailable while my wifi was working fine.
After that I think a lot whether to use pie or oreo, and which custom rom suits my need ?
After reading and searching, and thinking a lot in these 3 days, I come up with a solution.
1. Because the pie keep get updating, it always got bug and some glitches stuff, and I don't have a lot of time and don't like to keep flashing new custom rom, I decided to use Oreo Custom rom final version instead.
2. After a lot of research I come upon RR, PE, havoc OS, liquid remix, lineageos, and decided on lineageos 15.1 final version as my custom rom.
3. Because I don't need a lot customisation, I think lineage os is the best for me, as I only need privacy guard, network traffic indicator, and stability.
So I changed to lineageos 15.1, here is what I do
1. wipe dalvick cache, data , internal storage
2. flash oreo latest firmware V10.3.1.0.OEIMIXM from xiaomi updater site
3. flash lineage-15.1-20180709-UNOFFICIAL-whyred.zip
4. flash magisk 19.3
5. flash opengapps pico
6. flash lazyflasher no verify opt ( ended up failed / error ) Because I read some user getting bootloop caused by encrypted phone or something, I don't know about this part, so I just flash lazyflasher as the instructions said for uncencrypted phone ( ended up failed / error ) ( I don't know if my phone encrypted or not, so I just flash it as additional file)
7. reboot, after getting in, it shows android encrypting, and reboot again, after a few minutes, I thought it stuck on boot loop, but finally it gets into the welcome screen. I tried reboot a few times to see if it stuck or not, but it was working fine. Tested the rom 24 hours by now, and everything seems to work fine.
What I want to ask is,
1. Does my step on changing from pie custom rom to oreo custom rom correct ?
2. lineage-15.1-20180709-UNOFFICIAL-whyred.zip Is this the final version of oreo lineageos 15.1 whyred custom rom ?
3. Sometimes I saw my sim network bar gone completely, but I can make call and check balance, and in the sim status, it show -100dbm and 99 asu. Is this normal ? Or is it because I flash wrong firmware or something ? Or is it caused by my area unstable tower network so the bar completely gone ?
4. Should I use pie or oreo firmware in this custom rom lineageos 15.1 android 8.1 ? Or it's irrelevant because the firmware is flashed by the lineageos custom rom ?
5. Do I need custom kernel ? And what's the best custom kernel for android oreo ?
Other than that, I am satisfied with everything it offers. Thanks for reading and replying.
1. Yes. I've never flashed lazyflasher though.
2. Yes.
3. If you can call, it's probably just very weak signal and the indicator goes off. Otherwise it's a bug in LOS, I doubt the firmware has anything to do with it (I'm on Oreo too).
4. Oreo.
5. No, but it wont hurt you if you try a couple - just make sure they work in Oreo firmware. I'm on KangarooX R4.4 and getting over 10 hours of SOT.