I'm giving a try again to the xtrasmooth with M using the release from 14th July and seems stable, at least during this 3 days however, I have a notice for an android update that suddenly come up that I'm not able to flash because when I reboot into recovery there is not a way to flash it.
Have any one else the same problem?
MPZ44Q or MPZ79M
mickjmickj said:
I'm giving a try again to the xtrasmooth with M using the release from 14th July and seems stable, at least during this 3 days however, I have a notice for an android update that suddenly come up that I'm not able to flash because when I reboot into recovery there is not a way to flash it.
Have any one else the same problem?
Click to expand...
Click to collapse
I couldn't wait to understand how to make this update so I flashed the xtrasmooth MPZ79M and I find soon some differences like the dark team that was not availabile and the apps grid that is not divided by letters. At the end I've came back to the MPZ44Q that is still quite stable for my use.
Remain the issue about the android update notification.
Related
I was installing the most recent nightly update and after the phone restarted it began to flash on and off, I then rebooted it to try and fix the problem but this only made the phone stay of the cyanogenmod loading screen and will not boot after 20+ mins on this screen. How would I go about fixing this issue?
This is the update I installed: cm-12-20150116-NIGHTLY-bacon
What you need to understand is that "nightly" builds are highly experimental and far from stable. They are actually meant for developers if you ever dare to read the description of them.
Unfortunately you will not likely find much support for nightlies as they are updated daily for the most part. You're either going to have to flash a different rom or wait for the next nightly and try your luck.
Thank you
markbencze said:
What you need to understand is that "nightly" builds are highly experimental and far from stable. They are actually meant for developers if you ever dare to read the description of them.
Unfortunately you will not likely find much support for nightlies as they are updated daily for the most part. You're either going to have to flash a different rom or wait for the next nightly and try your luck.
Thank you
Click to expand...
Click to collapse
Ah okay I understood what I was getting into but here's the weird part, I was successful in adding a new ROM and trying to boot using a stable version of CyanogenMod which again was successful however when I rebooted the phone I got the same issue with it being stuck at the boot screen.
Thank you for your help.
Just wondering if anyone had a fix or explanation for my situation. I Received an update on the Blu Vivo 5R this Friday, Android 7.0. Then in the process today of unlocking the bootloader and flashing twrp, it got screwed up. so I downloaded the stock rom and flashed it, no biggie. fixed the boot freeze issue. but now I'm back to 6.0 because that was the most up-to-date stock rom. I tried checking for updates, supposedly I'm up to date. I even called Blu support to see if they could push it to my IMEI or something with no luck. they said they release it in batches and the software team deals with that, anyone know a way I could resolve this
You can try manually setting the date ahead a few days and reboot, sometimes that will bring an update.
Char_G said:
You can try manually setting the date ahead a few days and reboot, sometimes that will bring an update.
Click to expand...
Click to collapse
Didn't do anything, thanks for the quick response though.
About 3 weeks ago I updated to the current stock firmware and since then I have gotten stuck on the tmobile splash screen about once a week. The only fix for this has been a factory reset... Not entirely sure what's going on here or how to fix it but this is getting really old. Has there been any other reports of problems like this with the current firmware?
My wife is using the phone and at work so I can't give the exact firmware right now, just trying to get some idea of what I could try.
zadane said:
About 3 weeks ago I updated to the current stock firmware and since then I have gotten stuck on the tmobile splash screen about once a week. The only fix for this has been a factory reset... Not entirely sure what's going on here or how to fix it but this is getting really old. Has there been any other reports of problems like this with the current firmware?
My wife is using the phone and at work so I can't give the exact firmware right now, just trying to get some idea of what I could try.
Click to expand...
Click to collapse
My 7.0 nougat on my s6 stopped the phone from charging. I got around it by flashing Dr ketans note 5 rom. It's touch wiz based so you keep your samsung goodies plus get some tweaks. It's very stable. Just remember to flash the call audio fix zip. Download odin and twrp for your device. Put the zip onto your device. Wipe dalvik/sysyem/cache/data from twrp then flash the zip. Your photos and files on internal storage will stay. But your apps will not.
Dear all,
Hope you are doing great, I was downloading and installing automatic updates just fine and the other week got a notification about a new update of over 1.4 gbs and the automatic installer was not possible to do and requested me to download it and installing it manually. I downloaded the Rar and everything was going smooth and when I enter TWRP I installed at first shoot without doing any wipe or clear cache or data.
All was installed and it told me to restart the phone, I did that and vroom a vibrating sound happen and got me back to the main screen of Poco and then to TWRP and show me 3 workarounds to clear data and cache and the last resort do a clean flash rom.
I had to end with the last option since I was unable to install the update. What could be gone wrong here? I am back at stock now and I am very sad that this fricking update break all the custom firmware and got me bootlooped
I look for your inputs and maybe I can try again.
Thank you!
You must install Android 11 firmware for newer versions of Arrow as it has switched to OSS vendor.
I was on arrow os 11 so Android 11 was on there, the issue was when I was installing the new update from surija I believe si called the developer.
Do you guys have an idea what did I did wrong? Should You recommend staying vainilla stock miui 12 with root privileges or arrow 11?
Thank you!
I was able to flash the latest version update but I am having a System UI is not responding and got WIFI broken so if anyone is installing this update be careful, does anyone installed the last arrow OS update?
I am currently having issues with the last update, I think I will stick with no updates on the firmware
Sorry I am posting multiple updates on my thread, but I tested it and definetly the last update from Surya break the OS when you login you do not have WIFI and is showing the error I mentioned UI system unresponsive. I installed the version from April from Arrow OS and all works like a charm.
So if anyone reads this be careful with latest release from Surya 5/14 version
Yes, i can confirm. The version I used initially was from april 30. The update from may caused bootloop. I'll be turning off updates when I restore it with miflash.
The main reason I went with arrow is that it is selinux enforcing and supports safety net. But this really makes me think..
@SebixWolf The problem may have been that you flashed arrowos from the wrong miui version. I just miflashed back to the original regional version, flashed twrp again and flashed the R firmware. See https://forum.xda-developers.com/t/...ng-flashing-custom-rom.4274891/#post-85002889
Hello everyone!
I just download the last update via update in the phone and normally it boots me into TWRP then I search install it and thats it. The thing is that this last update unfortunately when the logo is installing in the middle throw me an error E1001 Error 1 and semi brick my phone, when I choose restart it literally throws me back to Fastboot.
Did anyone encounter the same fate? Or maybe my update file got corrupted?
Any ideas how can I fix this and have the last update installed for this ROM?
Thank you!
SebixWolf said:
Hello everyone!
I just download the last update via update in the phone and normally it boots me into TWRP then I search install it and thats it. The thing is that this last update unfortunately when the logo is installing in the middle throw me an error E1001 Error 1 and semi brick my phone, when I choose restart it literally throws me back to Fastboot.
Did anyone encounter the same fate? Or maybe my update file got corrupted?
Any ideas how can I fix this and have the last update installed for this ROM?
Thank you!
Click to expand...
Click to collapse
Try August 1st update. Dev quickly fixed it probably after 31st July build.
Where can I download that? on the webpage the last build with GAPPS is the 31st
Thanks for the reply
I just redownload the update for the 31st with GAPPS and now booted like a charm.
I believe my OTA Updater file got corrupted or something like that.
SebixWolf said:
I just redownload the update for the 31st with GAPPS and now booted like a charm.
I believe my OTA Updater file got corrupted or something like that.
Click to expand...
Click to collapse
Nice to hear that. Sometime, updating directly from phone turn out disaster (4 from 5 in my case). Thus I prefer to download the build in the PC then do the update manually. Please note that it may caused by my network stability also.