New Update - BLU 06/01/2016 ?? - Blu Vivo XL

Has anyone else got this notification of update?
Version Number: BLU_V0030UU_V10_GENERIC_5.1_20160518-1813
Version Size: 100.21 MB
Release Date - 2016-06-01

Just got my phone in and yes i have that updates. so far it fails on the recovery screen on reboot. luckly holding power button and force reboot fixed it, not going to install the update again until i see its resolved..

hamilLewiston said:
Has anyone else got this notification of update?
Version Number: BLU_V0030UU_V10_GENERIC_5.1_20160518-1813
Version Size: 100.21 MB
Release Date - 2016-06-01
Click to expand...
Click to collapse
I updated yesterday and all I see different is that radio app got updated to Nextradio

help.
I installed the update and now my phone doesn't boot. I go straight to recovery. Not quite sure what to do. Anyone have any suggestions?
The thing is that I just rooted with KingoRoot other day, voiding the warranty.

hamilLewiston said:
Has anyone else got this notification of update?
Version Number: BLU_V0030UU_V10_GENERIC_5.1_20160518-1813
Version Size: 100.21 MB
Release Date - 2016-06-01
Click to expand...
Click to collapse
I've rooted and flashed tWPR recovery , so don't think can do such OTA update directly.
If anybody has latest ROM tWPR backup, I would like to try.

I restored y phone to original recovery and ROM, but after download and enter recovery, it shows ERROR

Im rooted. Unless its a big difference i dont see any means to uodate

Take out the SD card and then download the update. The phone get's funky if you have an SD card
---------- Post added at 11:22 AM ---------- Previous post was at 11:18 AM ----------
Insane PPC said:
Just got my phone in and yes i have that updates. so far it fails on the recovery screen on reboot. luckly holding power button and force reboot fixed it, not going to install the update again until i see its resolved..
Click to expand...
Click to collapse
If you have an SD card inserted to the phone, remove it before downloading the update. The phone doesn't react too well with an SD card.

AqueousBor said:
I updated yesterday and all I see different is that radio app got updated to Nextradio
Click to expand...
Click to collapse
yeah I received the notification as well. It's only an update to an app "radio" that I dont even use. I'm just patiently waiting for Android 6.0 as they promised the Vivo XL would get.

The Remedy said:
yeah I received the notification as well. It's only an update to an app "radio" that I dont even use. I'm just patiently waiting for Android 6.0 as they promised the Vivo XL would get.
Click to expand...
Click to collapse
Ditto. But I think we both know that's never going to happen.

xphyle1971 said:
Ditto. But I think we both know that's never going to happen.
Click to expand...
Click to collapse
tbh it looks that way but idk their was an official android 6.0 update for another BLU phone I saw on a website the other day but I cant think of which BLU model it was. So i'm still hopeful.

jason4962 said:
Im rooted. Unless its a big difference i dont see any means to uodate
Click to expand...
Click to collapse
Android security updates?
HandsomeFatty said:
Take out the SD card and then download the update. The phone get's funky if you have an SD card
If you have an SD card inserted to the phone, remove it before downloading the update. The phone doesn't react too well with an SD card.
Click to expand...
Click to collapse
Will the update go through even if using TWRP? Will it break root or cause a soft brick? I'm still running the original build that it shipped with (dated 26-12-2015 with 2015-11-01 security patch level).
The Remedy said:
yeah I received the notification as well. It's only an update to an app "radio" that I dont even use. I'm just patiently waiting for Android 6.0 as they promised the Vivo XL would get.
Click to expand...
Click to collapse
When did "they" (Gionee or BLU?) promise the Vivo XL would get MM?

rczrider said:
Android security updates?
Will the update go through even if using TWRP? Will it break root or cause a soft brick? I'm still running the original build that it shipped with (dated 26-12-2015 with 2015-11-01 security patch level).
When did "they" (Gionee or BLU?) promise the Vivo XL would get MM?
Click to expand...
Click to collapse
1. It wouldn't be Gionee doing anything even those this phone is based off of it. 2. Look at the sites that reviewed it, it's been posted many times that it was planned to get Android 6.0 . Android Central....check gsmarena it's out there if you look.

The Remedy said:
1. It wouldn't be Gionee doing anything even those this phone is based off of it. 2. Look at the sites that reviewed it, it's been posted many times that it was planned to get Android 6.0 . Android Central....check gsmarena it's out there if you look.
Click to expand...
Click to collapse
I can't imagine BLU is doing much ROM development. Gionee almost certainly has to provide them with the MM ROM since the Vivo XL is the Gionee Elife S Plus. BLU makes some changes, sure, but they likely aren't developing a MM ROM from scratch.
Anyway, I was just curious and not that interested in reading up on it. I got this phone to be a bedside clock (AMOLED screen FTW) and as a backup in case my DD runs into problems. It was $100 and a good deal at that price, but I have no belief that it will see anything but security patch updates (and even then, I don't expect much).

They arent going to update to 6.0. It used to say that on the Blu website but after the phone launched it was removed from the Blu Vivo XL and Vivo 5 pages.

Can anyone make a flashable zip? I'm using TWRP. I tried modifiing the updater-script, but no luck so far.

I updated the radio but went to an error and now the phone is stuck on boot menu. I can't flash it because it won't connect to any computer.

lemur394395 said:
I installed the update and now my phone doesn't boot. I go straight to recovery. Not quite sure what to do. Anyone have any suggestions?
The thing is that I just rooted with KingoRoot other day, voiding the warranty.
Click to expand...
Click to collapse
Check out http://forum.xda-developers.com/vivo-xl/how-to/rooted-kingroot-replaced-supersu-twrp-t3432078 .
Flash TWRP recovery and then load the backup from 2016-03. Then root with SuperSu.

any mm update ?

BLU on Google +
min1968 said:
I've rooted and flashed tWPR recovery , so don't think can do such OTA update directly.
If anybody has latest ROM tWPR backup, I would like to try.
Click to expand...
Click to collapse
If you check with these folks, they can help immensly!! BLU Development Team on Google+ a small community of BLU users that share information and have ALL kinds of information and links to STOCK, CUSTOM, and other ROM's, plus rooting tips, guides, and links to TWRP and CWM recoveries.

Related

Marshmallow Released

After more than 10 months after release, BLU has promised on delivering the marshmallow update. I just saw the notification today at around 4:00PM CMT.
Currently updating!
9000RPM said:
After more than 10 months after release, BLU has promised on delivering the marshmallow update. I just saw the notification today at around 4:00PM CMT.
Currently updating!
Click to expand...
Click to collapse
Screen Shots Please....
I just updated last night. Everything running smoothly. I had the phone rooted previously but the one click root app got removed in the update process. If anyone has success rooting after the upgrade, I'd love to know about it.
I upgraded this morning and I've been having lots of issues with my installed apps, like Facebook, Messenger, Whatsapp and more, and of course I lost Root which was previously accomplished by KingRoot which doesn't work anymore.
Also I noticed that during the update process, particularly while flashing the firmware, it was flashed using my TWRP recovery and afterwards it got removed.
I'm sure that if I start fresh by performing a factory reset, all will be fluid and in working order, minus TWRP and Root of course, at least for the time being.
All in all, the update to Mashmellow seems to be awesome, some new features.
Cheers!
I'm having issues with the update. It downloads just fine and when I go ahead and try to install...it just spins around on "unzipping" and then proceeds to restart..or turn off for that matter. The phone turned off...I didn't do anything to it just let it sit there for a while and then I saw the charge icon show up (the one you see when the phone is off and charging) at which point I started the phone up. The phone did not update and I can basically repeat the process. There is 4.30 GB of space free and no SD card. What do I do?
EDIT:
So I tried again, kept at it and it eventually worked. Updated just fine but now there are doubles of all folders in the phone. When I plug it into my computer, all the folders (Music, Download etc etc) are showing up twice with the same contents in the each of them...
What...is...going...on?
Was pretty laggy at first. Decided back up my files and do a factory reset. Works much better now.
disChapo said:
Was pretty laggy at first. Decided back up my files and do a factory reset. Works much better now.
Click to expand...
Click to collapse
Yeah, mine is working flawlessly after a factory reset! Much improvement compared to Lollypop!
Anyone found a Root for Marshmellow yet?
Unless Blu changed something other than the interface I'd guess TWRP won't be working on MM anytime soon. It's a problem seen in the Gionee phone and I would expect the same to happen to the Blu. As for root and a custom recovery (although not a great one) you could try following these instructions: https://forum.hovatek.com/thread-15270.html
I've played a bit with the Gionee Marshmallow firmware on my Vivo XL during the past month or so, and one thing that really bugs me is that it seems to be shipping with a kernel that is way older than it should be on an MM release. And the OTA service that is known for leaking info also seemed to still be present in the updated firmware.
Can someone who's got the Blu update check if these two things are the same for the Blu release please? Enter device info in the settings menu and check the Kernel version for me. And, if you guys manage to get root, check if AdupOTA is still lurking in there.
batoussai said:
Can someone who's got the Blu update check if these two things are the same for the Blu release please? Enter device info in the settings menu and check the Kernel version for me.
Click to expand...
Click to collapse
Kernel Version: 3.18.19
Build Number: MRA58k
Custom build version: BLU_V0030UU_V07_GENERICM14-11-2016
Does anybody with TWPR/root upgraded to official 6.0 successfully? What's exact procedure/steps?
I have my Blu Vivo XL with TWRP now, in last (small) OTA update a few months ago, I tried flashing back to original recovery and rom, but still failed OTA.

How to update R1 to the latest OTA Update?

Hey All,
I'm looking for some help nito update this device to the latest OTA update. I have installed TWRP 3.0.2.0 that came with the dirtycow method. The device found the latest updated released in the past few days but when going to install it, it brings up the TWRP (which is how it should install). Now I don't mind if I can't grab this latest version due to whatever reason, but how would I go about updating the device? Currently it's running the stock version 6.1 6/17/2016.
Sorry if this has been answered somewhere, but still kinda new with Android devices and the whole rooting process. I'd like to be able to keep TWRP if at all possible and keep this device updated. Also I saw there was a updated TWRP released, how would I go about updating the recovery?
Thanks a lot for the help anyone can give!
KyleStilkey said:
Hey All,
I'm looking for some help nito update this device to the latest OTA update. I have installed TWRP 3.0.2.0 that came with the dirtycow method. The device found the latest updated released in the past few days but when going to install it, it brings up the TWRP (which is how it should install). Now I don't mind if I can't grab this latest version due to whatever reason, but how would I go about updating the device? Currently it's running the stock version 6.1 6/17/2016.
Sorry if this has been answered somewhere, but still kinda new with Android devices and the whole rooting process. I'd like to be able to keep TWRP if at all possible and keep this device updated. Also I saw there was a updated TWRP released, how would I go about updating the recovery?
Thanks a lot for the help anyone can give!
Click to expand...
Click to collapse
As long as you have twrp installed, you can install the modified update 8.3 i just finished.
==>>it is here
mrmazak said:
As long as you have twrp installed, you can install the modified update 8.3 i just finished.
==>>it is here
Click to expand...
Click to collapse
Already tried it and it doesn't work. She uses the phone to play Pokemon Go and sadly the modified version you've made gives the error that the device or software is not supported. I believe this is due to the method you are using to remove the ads and custom changes made to the ROM, which I don't personally care if the phone has them or not. I'm wanting to install OTA updates without any heavy modifications made, just the ability to keep TWRP but have an updated phone.
KyleStilkey said:
Already tried it and it doesn't work. She uses the phone to play Pokemon Go and sadly the modified version you've made gives the error that the device or software is not supported. I believe this is due to the method you are using to remove the ads and custom changes made to the ROM, which I don't personally care if the phone has them or not. I'm wanting to install OTA updates without any heavy modifications made, just the ability to keep TWRP but have an updated phone.
Click to expand...
Click to collapse
Will be redoing the patch again and making not pre-rooted version. But if your app is not working on the modified 7.4.2 there is nothing I can do.
mrmazak said:
Will be redoing the patch again and making not predicted version. But if your app is not working on the modified 7.4.2 there is nothing I can do.
Click to expand...
Click to collapse
I see V8 but do not see a 7.4.2 on there.
EDIT: Nevermind I found it, will try the modified 7.4.2 and get back to you.
KyleStilkey said:
I see V8 but do not see a 7.4.2 on there.
EDIT: Nevermind I found it, will try the modified 7.4.2 and get back to you.
Click to expand...
Click to collapse
Non-rooted rom finished. uploaded to android file host.
Link and description in my other post.
==>>Unrooted rom
mrmazak said:
Non-rooted rom finished. uploaded to android file host.
Link and description in my other post.
==>>Unrooted rom
Click to expand...
Click to collapse
I want to say thank you a lot, this worked wonderfully! Only issue is Google Plus doesn't work (not a huge deal for the wife) but everything else is working great!
One last question, what is the recommended TWRP to use with this phone, I currently have the 3.0.2.0 Vampire version installed.
KyleStilkey said:
I want to say thank you a lot, this worked wonderfully! Only issue is Google Plus doesn't work (not a huge deal for the wife) but everything else is working great!
One last question, what is the recommended TWRP to use with this phone, I currently have the 3.0.2.0 Vampire version installed.
Click to expand...
Click to collapse
I have seen it mentioned that Google + does not work on 8.3 in general not just this modified one.
That recovery is the one I use and has advantage over the other one (lopestom's versio) in that in recovery you can use external sdcard and also mtp connection.

Just got my R1 HD - is it safe to update to current OTA release?

Before rooting/removing ads etc, I want to use the phone for a week or so stock so Ill have a baseline to compare it to.
Would it be OK to let the phone update fully while using it? I know with some devices (Amazon kindle) if you update it to a certain point, then there is no going back and the bootloader gets locked.
Lemme know what you think.
lourivellini said:
Before rooting/removing ads etc, I want to use the phone for a week or so stock so Ill have a baseline to compare it to.
Would it be OK to let the phone update fully while using it? I know with some devices (Amazon kindle) if you update it to a certain point, then there is no going back and the bootloader gets locked.
Lemme know what you think.
Click to expand...
Click to collapse
If you allow it to update, you will not be able to unlock bootloader, so if you want to root do not update.
The latest update has been posted in this forum, so you are not missing any of the update by rooting either.
mrmazak said:
If you allow it to update, you will not be able to unlock bootloader, so if you want to root do not update.
The latest update has been posted in this forum, so you are not missing any of the update by rooting either.
Click to expand...
Click to collapse
Is the root junky method still good?
https://youtu.be/KMobKWfZbJg
Or should I follow a different guide? I know some of his files on his website are outdated.
I also am having a problem when trying to use the flashtool. When I plug my phone in powered off, at first it says the battery is low no matter what, then disconnects, then says 95% or whatever it is. This is preventing me from using flashtool when in download mode.
Any idea why this is happening? My r1 hd is on 6.0 btw
lourivellini said:
Is the root junky method still good?
https://youtu.be/KMobKWfZbJg
Or should I follow a different guide? I know some of his files on his website are outdated.
I also am having a problem when trying to use the flashtool. When I plug my phone in powered off, at first it says the battery is low no matter what, then disconnects, then says 95% or whatever it is. This is preventing me from using flashtool when in download mode.
Any idea why this is happening? My r1 hd is on 6.0 btw
Click to expand...
Click to collapse
All the R1-HD line is on Android 6.0
The Blu release version is what changes.
I believe this was the order
6.1
6.4
6.5
6.6
7.4.2
8.3
8.4
The flashtool stopped working at v6.6
The new method was the use dirty cow. There is a tool thread for directions.
This new method stopped working at v8.3
mrmazak said:
All the R1-HD line is on Android 6.0
The Blu release version is what changes.
I believe this was the order
6.1
6.4
6.5
6.6
7.4.2
8.3
8.4
The flashtool stopped working at v6.6
The new method was the use dirty cow. There is a tool thread for directions.
This new method stopped working at v8.3
Click to expand...
Click to collapse
So the phone is brand new from Amazon, haven't touched it or even connected it to the internet. Not home right now, but I remember seeing software version 6.0 not Android 6.0.
Anyways, I guess I should look into the dirty cow method. Do you have the link?
Sent from my Moto G (5) Plus using Tapatalk
lourivellini said:
So the phone is brand new from Amazon, haven't touched it or even connected it to the internet. Not home right now, but I remember seeing software version 6.0 not Android 6.0.
Anyways, I guess I should look into the dirty cow method. Do you have the link?
Sent from my Moto G (5) Plus using Tapatalk
Click to expand...
Click to collapse
https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333
mrmazak said:
https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333
Click to expand...
Click to collapse
Thanks
Sent from my Moto G (5) Plus using Tapatalk
mrmazak said:
https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333
Click to expand...
Click to collapse
Is there a ROM i should flash afterwards?
I just installed twrp using the dirty cow method (steps 1-4), and then also did step 5-1 (install supersu).
At this point, in the past Ive always just flashed a brand new rom and gapps. Is there a "stock" rom that I should flash with twrp - which is just the stock rom with no ads? And which build should I? Im on 6.6 right now.
Ive read that lineage has some problems with the camera - no big deal ill roll will the stock non-ad rom for now.
Thanks again!
lourivellini said:
Is there a ROM i should flash afterwards?
I just installed twrp using the dirty cow method (steps 1-4), and then also did step 5-1 (install supersu).
At this point, in the past Ive always just flashed a brand new rom and gapps. Is there a "stock" rom that I should flash with twrp - which is just the stock rom with no ads? And which build should I? Im on 6.6 right now.
Ive read that lineage has some problems with the camera - no big deal ill roll will the stock non-ad rom for now.
Thanks again!
Click to expand...
Click to collapse
So the non-prime ROMs latest is v21 it comes with none of the prime ads.
Or v8.4 that came with the ads but they were removed. .some have said n-ify not working on 8.4 but does on 21. I do not know first hand.
https://forum.xda-developers.com/r1-hd/development/modified-8-3-stock-rom-t3602672
You will have to do SuperSU again after the rom
mrmazak said:
So the non-prime ROMs latest is v21 it comes with none of the prime ads.
Or v8.4 that came with the ads but they were removed. .some have said n-ify not working on 8.4 but does on 21. I do not know first hand.
https://forum.xda-developers.com/r1-hd/development/modified-8-3-stock-rom-t3602672
You will have to do SuperSU again after the rom
Click to expand...
Click to collapse
Last question(s):
So I installed V21, supersu, removed ALL amazon with dirtycow.
1. Is my phone now disabled from receiving OTA updates? Or do I have to do something else to make sure auto updates are OFF.
2. Is there a way to remove this stupid blu app (blu help) that keep requiring me to register my device? Every time I power on I have to force stop the app or I have a constant notification to do it.
Thanks again!
lourivellini said:
Last question(s):
So I installed V21, supersu, removed ALL amazon with dirtycow.
1. Is my phone now disabled from receiving OTA updates? Or do I have to do something else to make sure auto updates are OFF.
2. Is there a way to remove this stupid blu app (blu help) that keep requiring me to register my device? Every time I power on I have to force stop the app or I have a constant notification to do it.
Thanks again!
Click to expand...
Click to collapse
The debloat done with the tool supposed to have disabled the ota checker program.
And as a second method of not getting ota, having twrp and root will also make the ota fail even if it was to download.
The Blu app is called warrenteer. What I do is belete the whole folder.
/system/priv-app/warrenteer
You can take baby steps and just rename the apk inside that folder to add "-" or "_" to end of it's name
This can be done with a root explorer app or with recovery file manager. Either way.

Oreo OTAs

Close thread
Should I bother trying this? What's new? I'm on U firmware which I like but should I wipe to go to Oreo?
Anybody tried this?
vineet381 said:
Anybody tried this?
Click to expand...
Click to collapse
Personally I think is not worth it. This is not final build and will delete data from your device. Then next one will show up in couple days or even (maybe) tomorrow. If I will you I will wait for around another 3-4 weeks to get more stable build.
Sent from my SM-N950U using XDA Premium HD app
I tried it -- the installation took about an hour in Recovery, mainly stayed in the "Patching system files". This install *WILL* wipe your phone (not your SD card though).
The build was super fast (even faster than a fresh Nougat flash).
There were two things that caused me to flash back to Nougat.
- The Wi-Fi was extremely weak. At my desk at work, I can normally see 6 Wi-Fi networks. 4 of them are in my office. With Oreo, I could only see two of them, and it struggled to stay connected to the one that I normally have full signal on.
- Also, my AT&T Gear S2 Classic could not be connected. Upon attempting to pair (after confirming the PIN on phone/watch) Samsung Gear gave a message stating that I need to ensure my phone was compatible and that I had the latest Samsung Gear app. I confirmed that there were no available updates for ANYTHING in the Play Store and Galaxy Apps. Both stores showed that my app was up to date.
If it weren't for those two issues, I'd still be on the Oreo build right now.
Another point -- I experienced my first freeze/reboot on this phone in Oreo. I've had the phone since June of last year and never had any freeze/reboot issues previously. Never dropped or gotten the phone wet, etc.
Hope this helps anyone who is wanting to flash the build!
vineet381 said:
Anybody tried this?
Click to expand...
Click to collapse
DO you know can i install this update on my 935U model and how can i do it ?
You need to ODIN to 935A's latest build (BRA1) then you can upgrade to this Oreo build by flashing it in Recovery.
Janitor87 said:
DO you know can i install this update on my 935U model and how can i do it ?
Click to expand...
Click to collapse
Can you please provide me with the link on this Odin file because I can not find any working link. NOw i'm using BKQH1
nivron said:
You need to ODIN to 935A's latest build (BRA1) then you can upgrade to this Oreo build by flashing it in Recovery.
Click to expand...
Click to collapse
BRA1 ODIN Files
Thanks to @norbarb for that link. I downloaded it the other day. You will have to unRAR the files after you open the initial ZIP file -- otherwise ODIN won't find the files.
Janitor87 said:
Can you please provide me with the link on this Odin file because I can not find any working link. NOw i'm using BKQH1
Click to expand...
Click to collapse
I don't have a windows PC at the moment. Can you plz provide me with a OTA update files. I updated G935AUCS4BQH1-to-S4BQJ2
HOw much updates i should update to the G935AUCS4BRA1
Thank you.
nivron said:
BRA1 ODIN Files
Thanks to @norbarb for that link. I downloaded it the other day. You will have to unRAR the files after you open the initial ZIP file -- otherwise ODIN won't find the files.
Click to expand...
Click to collapse
Janitor87 said:
I don't have a windows PC at the moment. Can you plz provide me with a OTA update files. I updated G935AUCS4BQH1-to-S4BQJ2
HOw much updates i should update to the G935AUCS4BRA1
Thank you.
Click to expand...
Click to collapse
Without a PC, you cannot update to Oreo unless you're already on the AT&T G935A firmware.
Sent from my SM-G955U using Tapatalk
As far as I can tell, there's not an OTA sideload update path to BRA1. Someone else may be able to chime in with it.
I assume you are not an AT&T customer, otherwise you could use the official OTA method to get to BRA1.
Janitor87 said:
I don't have a windows PC at the moment. Can you plz provide me with a OTA update files. I updated G935AUCS4BQH1-to-S4BQJ2
HOw much updates i should update to the G935AUCS4BRA1
Thank you.
Click to expand...
Click to collapse
Janitor87 said:
I don't have a windows PC at the moment. Can you plz provide me with a OTA update files. I updated G935AUCS4BQH1-to-S4BQJ2
HOw much updates i should update to the G935AUCS4BRA1
Thank you.
Click to expand...
Click to collapse
https://samsung.firmware.science/download?url=48775/1488/SS-G935AUCS4BQJ2-to-U4BQK2-UP
https://samsung.firmware.science/download?url=48775/1488/SS-G935AUCU4BQK2-to-S4BQL1-UP
https://samsung.firmware.science/download?url=48775/1488/SS-G935AUCS4BQL1-to-S4BRA1-UP
https://samsung.firmware.science/download?url=48775/1488/SS-G935AUCS4BRA1-to-U4CRB5-UP
In that order
Sent from my SM-G955U using Tapatalk
You are right. I'm using the Verizon 935V model anbd now I flashed ATT firmware and wanna try to install OREO update
nivron said:
As far as I can tell, there's not an OTA sideload update path to BRA1. Someone else may be able to chime in with it.
I assume you are not an AT&T customer, otherwise you could use the official OTA method to get to BRA1.
Click to expand...
Click to collapse
Janitor87 said:
You are right. I'm using the Verizon 935V model anbd now I flashed ATT firmware and wanna try to install OREO update
Click to expand...
Click to collapse
You're in luck then, I've laid out all the OTAs you need to install to your device.
Sent from my SM-G955U using Tapatalk
I'm trying to update now.... I will inform if I will be a lucky man and successfully update my phone
FatalONEM8 said:
You're in luck then, I've laid out all the OTAs you need to install to your device.
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
---------- Post added at 19:49 ---------- Previous post was at 19:12 ----------
[email protected]:/home/alex/Downloads# adb sideload update.zip
serving: 'update.zip' (~31%) * failed to read command: Success
I can not update
---------- Post added at 20:02 ---------- Previous post was at 19:49 ----------
I found my issue I forgot to enable USB debugging mode. It has fixed my issue.
-------------------------------
Janitor87 said:
I'm trying to update now.... I will inform if I will be a lucky man and successfully update my phone
---------- Post added at 19:49 ---------- Previous post was at 19:12 ----------
[email protected]:/home/alex/Downloads# adb sideload update.zip
serving: 'update.zip' (~31%) * failed to read command: Success
I can not update
Click to expand...
Click to collapse
nivron said:
I tried it -- the installation took about an hour in Recovery, mainly stayed in the "Patching system files". This install *WILL* wipe your phone (not your SD card though).
The build was super fast (even faster than a fresh Nougat flash).
There were two things that caused me to flash back to Nougat.
- The Wi-Fi was extremely weak. At my desk at work, I can normally see 6 Wi-Fi networks. 4 of them are in my office. With Oreo, I could only see two of them, and it struggled to stay connected to the one that I normally have full signal on.
- Also, my AT&T Gear S2 Classic could not be connected. Upon attempting to pair (after confirming the PIN on phone/watch) Samsung Gear gave a message stating that I need to ensure my phone was compatible and that I had the latest Samsung Gear app. I confirmed that there were no available updates for ANYTHING in the Play Store and Galaxy Apps. Both stores showed that my app was up to date.
If it weren't for those two issues, I'd still be on the Oreo build right now.
Another point -- I experienced my first freeze/reboot on this phone in Oreo. I've had the phone since June of last year and never had any freeze/reboot issues previously. Never dropped or gotten the phone wet, etc.
Hope this helps anyone who is wanting to flash the build!
Click to expand...
Click to collapse
Thanks for the feeback, I tried this and I agree on weak Wifi on Oreo. I will keep and play with it for sometime before going back to Nougat. Hopefully new stable version shows up soon.
You are a lucky man because i'm flashing via adb and only 59 %. Which issue with a WiFi ? Can you please provide me more information and maybe do you know who will it fix ?
Thank you
vineet381 said:
Thanks for the feeback, I tried this and I agree on weak Wifi on Oreo. I will keep and play with it for sometime before going back to Nougat. Hopefully new stable version shows up soon.
Click to expand...
Click to collapse
vineet381 said:
Thanks for the feeback, I tried this and I agree on weak Wifi on Oreo. I will keep and play with it for sometime before going back to Nougat. Hopefully new stable version shows up soon.
Click to expand...
Click to collapse
I face the same issues you have described. Originally after applying the Oreo update, I was not able to enable Bluetooth nor WiFi. I had to reboot to recovery and wipe cache.
Once that was done, I was able to get WiFi and Bluetooth to work.
I have the Galaxy Fit2 and was not able to sync watch to the phone with the same error you received. ( I tried the version 3..1.80.80109 of Samsung Accessory Service as suggested in another thread, no luck.)
WiFi as you described is pitiful, luckily I don't rely on WiFi as much so I will continue on with this Oreo build.
Does anyone know how to turn off the red heart rate sensor light off? It is accidentally turning on even if I dont get my finger on it after oreo update
---------- Post added at 02:19 PM ---------- Previous post was at 02:08 PM ----------
Janitor87 said:
You are a lucky man because i'm flashing via adb and only 59 %. Which issue with a WiFi ? Can you please provide me more information and maybe do you know who will it fix ?
Thank you
Click to expand...
Click to collapse
Wifi issue meaning weak signals in Wifi connection on Oreo. I simply followed the steps in flashing through SD card and it took a while (40 mins or so) but eventually it went through the install.

Switching from official Oneui to custom rom/ unofficial rom/ downgraded versions

My device model is G781B. Sw bit U5. I'm facing battery issue lately on latest April security update. So I wanted to downgrade but as my software version is U5, I couldn't do it. So can anyone guide me which custom rom and recovery I can flash and Is there any way to downgrade to previous version of oneui.
Are you using android 13 (OneUI 5)
Samarimama said:
Are you using android 13 (OneUI 5)
Click to expand...
Click to collapse
One ui 5.1
kawsar4547 said:
My device model is G781B. Sw bit U5. I'm facing battery issue lately on latest April security update. So I wanted to downgrade but as my software version is U5, I couldn't do it. So can anyone guide me which custom rom and recovery I can flash and Is there any way to downgrade to previous version of oneui.
Click to expand...
Click to collapse
Oh God.
I'm sorry to read that you updated from binary, going back will be a bit impossible. through odin no longer.
You will have to wait for someone to work on something for those who are in binary 5.
upgrading to binary 5 in my point of view was totally unnecessary.
Good luck colleague, hope that someone can give you a solution through root or wait for an update in May.
mezacorleehone said:
You will have to wait for someone to work on something for those who are in binary 5.
upgrading to binary 5 in my point of view was totally unnecessary.
Good luck colleague, hope that someone can give you a solution through root or wait for an update in May.
Click to expand...
Click to collapse
I didn't know binary was gonna update
kawsar4547 said:
I didn't know binary was gonna update
Click to expand...
Click to collapse
MMMMMMM..
Every time that OTA sends an update, the software version comes out and therefore the binary.
if you download a system to flash via odin, you force the binary.
I even warned right here about that topic.
but unfortunately, nothing can be done at the moment.
mezacorleehone said:
You will have to wait for someone to work on something for those who are in binary 5.
upgrading to binary 5 in my point of view was totally unnecessary.
Good luck colleague, hope that someone can give you a solution through root or wait for an update in May.
Click to expand...
Click to collapse
the bootloader would need to be signed again after being modified, there's very little chance of this ever being fixed.
3mel said:
the bootloader would need to be signed again after being modified, there's very little chance of this ever being fixed.
Click to expand...
Click to collapse
It only remains to wait for Samsung to send an update that fixes that.
wait for a developer to send solutions via root.
I recommend you to use Kernel Bandido.
I don't know if it is compatible with binary 5.

Categories

Resources