Hello respected members, I yesterday flashed that btu oreo rom through odin on my S7 edge G935FD , all went well and phone is working good, but in recovery there are these type of messages, I have seen on forums that many people are experiencing this recovery issue, is there a solution for it? Apparently they don't effect phone in anyway or cause any issues, but still why are these messages showing ? I am just worried about bootloops. Those messages are :
(fail to open recovery_cause(No such file or directory)
Reboot Recovery Cause is [UNKNOWN])(This is still showing in ERG2)
No Support SINGLE-SKU
File Based OTA
Supported API: 3
MANUAL MODE v1.0.0
Sucessfully verified dmverity hash tree
E:Failed to clear BCB message : failed to find /misc partition
Issues updated (OREO ERG2) :
1. First of all those weird "failed to find misc partition" messages in recovery. Don't know if they cause any issues but they are annoying. No bootloops or any other issues though. Happening since first oreo release of 1st May. (Fixed in ERG2 release).
2. Can't go into download mode anymore from recovery by using option " reboot to bootloader ". It just reboots the phone normally. Happening since I flashed the first oreo release using odin. (Still in ERG2)
3. If phone battery gets to 0% and discharges completely, then when plugged in the charger it goes into recovery mode instead of that charging screen. I used power off so that it exits recovery and goes into charging screen, but it again booted in recovery, when I selected " reboot phone " option it turned off and got in charging screen.. strange thing, I never experienced this on nougat, its happening since the first oreo release. (Still in ERG2)
4. Cell standby drain not that high after the 18th may btu update, but still high before it was 33% and screen 20%, now its 2-3% above screen battery usage. Happening since first oreo release. A note here that after flashing 18th may release I think battery life is good and SOT is somewhat same as last nougat release.. (Still in ERG2 release but somewhat more less.. but battery life on ERG2 is a little less than previous builds..)
5. Phone rebooted randomly before 18th may update, now after updating it seems to be fixed. Note that I experienced random reboots but no bootloops or other issues etc. (Already fixed)
6. Fingerprint scanner issues:
Fingerprint scanner becomes unresponsive randomly and I had to unlock using password. This is occuring from approx december or january security patch update and still isn't been fixed in latest oreo. This issue has surely increased in oreo, and now it happens more often and is very annoying to the point I disabled fingerprints.. (still in ERG2, for me, don't know if its hardware related)
Also in oreo, fingerprint requires more time to open the lockscreen, some 1 sec delay approx. Can't say if its requiring more time to match the fingerprints or its taking more time to unlock the lockscreen..
Note : I didn't experienced any connectivity issues in bluetooth, wifi or mobile data..
Some times I had to re-select default network mode for my sim in settings if internet gets hanged and don't works, but it happens very few times and changing network modes in network settings will instantly solve it, and it was also happening on nougat before. And didn't increase in oreo at the moment for me..
Also to tell you all, I flashed back last nougat release for my region successfully, but it looked too much slower and laggy as far as I remember before flashing oreo btu, maybe its because I got accustomed to oreo ( which is faster than nougat ) or maybe downgrading caused some issue maybe. But I don't think downgrading should cause performance issues. Also when I downgraded on nougat I couldn't go into download mode from recovery mode using option " reboot to bootloader " and it reboots to normal mode. I don't remember this, because always this option worked in nougat for me before flashing oreo. Don't know what's the reason but not a big deal. Also I didn't tested after downgrading about fully discharging battery and then putting phone on charger whether it goes in recovery or normal charging screen. Btw those fingerprint issues are a real pain.
Had the same experience, with the phone hanging on bootup and the same message in the recovery screen.
... so I went the factory reset route .... painful, but I could find no option to recover.
I see that there is an entry in the recovery menu for a firmware update from the SD card; can anyone suggest how that can be done? (In case there's a next time).
Did I can to flash without HomeCSC
Because I am in different country????
bonegang said:
Had the same experience, with the phone hanging on bootup and the same message in the recovery screen.
... so I went the factory reset route .... painful, but I could find no option to recover.
I see that there is an entry in the recovery menu for a firmware update from the SD card; can anyone suggest how that can be done? (In case there's a next time).
Click to expand...
Click to collapse
I flashed via odin, then did factory reset, but the message is still there, but phone works fine and smooth , but with occasional reboots and a strange high cell standby drain. My phone never rebooted even once on marshmallow and nougat.
Abo_Moaaz said:
Did I can to flash without HomeCSC
Because I am in different country????
Click to expand...
Click to collapse
You have to flash either CSC or home csc, home csc won't wipe your data, but I will recommend flashing normal csc and then factory reset and clear cache too, as to avoid any issues like bootloops etc.
Sent from my S7 Edge using XDA Labs
shah22 said:
Hello respected members, I yesterday flashed that btu oreo rom through odin on my S7 edge G935FD , all went well and phone is working good, but in recovery there are these type of messages, I have seen on forums that many people are experiencing this recovery issue, is there a solution for it? Apparently they don't effect phone in anyway or cause any issues, but still why are these messages showing ? I am just worried about bootloops. Those messages are :
fail to open recovery_cause(No such file or directory)
Reboot Recovery Cause is [UNKNOWN]
No Support SINGLE-SKU
File Based OTA
Supported API: 3
MANUAL MODE v1.0.0
Sucessfully verified dmverity hash tree
E:Failed to clear BCB message : failed to find /misc partition
Click to expand...
Click to collapse
How did you flashed on SM-G935FD? Since so far it's only available for SM-G935F and SM-G930F.
MisterX01X said:
How did you flashed on SM-G935FD? Since so far it's only available for SM-G935F and SM-G930F.
Click to expand...
Click to collapse
I flashed through odin, the firmware is same for dual sim models , hence G935F firmware works on G935FD too, just be sure that model number is correct, i.e not to flash a G935FD with a G930F firmware or flashing a snapdragon variant with exynos or vice versa.
But now the btu oreo update have been pulled back from the OTA server, due to bootloops / recovery bugs, its better to wait now for your own region oreo update. If you still want that btu oreo, you can download the corresponding rom for your model from sammobile or updato(for faster speeds). But I suspect oreo update is halted and will be resumed again with these bugs fixed along with may update patch near the end of may globally.
Sent from my S7 Edge using XDA Labs
shah22 said:
I flashed through odin, the firmware is same for dual sim models , hence G935F firmware works on G935FD too, just be sure that model number is correct, i.e not to flash a G935FD with a G930F firmware or flashing a snapdragon variant with exynos or vice versa.
But now the btu oreo update have been pulled back from the OTA server, due to bootloops / recovery bugs, its better to wait now for your own region oreo update. If you still want that btu oreo, you can download the corresponding rom for your model from sammobile or updato(for faster speeds). But I suspect oreo update is halted and will be resumed again with these bugs fixed along with may update patch near the end of may globally.
Click to expand...
Click to collapse
I already have installed it on SM-G935F and it works totally fine. The only problem so far I have detected is that when I play a song on Samsung Music with earphones connected, it crashes but it plays normally with phone speaker and secondly this BTU firmware doesn't have Bixby in it.
it seems it was a beta nougat for s7 edge ,because the update is not available anymore only on sammobile.....I received notification last week to update to android 8,but I didn't update and now when I check I don't see the notification anymore ,it says like my current version is the latest...
emilutzzu said:
it seems it was a beta nougat for s7 edge ,because the update is not available anymore only on sammobile.....I received notification last week to update to android 8,but I didn't update and now when I check I don't see the notification anymore ,it says like my current version is the latest...
Click to expand...
Click to collapse
It is already mentioned that the update is no more available through OTA because its been pulled back from the server due to bugs in recovery, wait for the resume till the end of the may hopefully
Sent from my S7 Edge using XDA Labs
G935FD w/BTU NO ISSUES
shah22 said:
It is already mentioned that the update is no more available through OTA because its been pulled back from the server due to bugs in recovery, wait for the resume till the end of the may hopefully
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
I downloaded the BTU files straight from Sam Firmwares and only flashed AP, HOME CSC and CP with ODIN 3.13.1 and have no issues at all. So fare everything is stable no reboots lags or freezing. That version of ODIN is updated to handle the compression of OREO.
i hv only one issue
cell standby battery drain as huge as 30%
Omegastorm said:
I downloaded the BTU files straight from Sam Firmwares and only flashed AP, HOME CSC and CP with ODIN 3.13.1 and have no issues at all. So fare everything is stable no reboots lags or freezing. That version of ODIN is updated to handle the compression of OREO.
Click to expand...
Click to collapse
Yes v 3.13.1 handles the latest firmware, but the update had bugs in recovery and some users faced bootloops, I faced auto reboots whenever I rebooted phone and used fingerprint at a faster rate to lock and unlock phone.
saurabh808 said:
i hv only one issue
cell standby battery drain as huge as 30%
Click to expand...
Click to collapse
Same here, high cell standby drain. Also battery life is a little less compared to last nougat release.
Sent from my S7 Edge using XDA Labs
Can anyone with the oreo update tried using phone in airplane mode? Or without sim card inserted? See if that cell standby drain still occur in airplane mode or without sim? It may only be a bug or android's wrong report of the battery usage ..
Sent from my S7 Edge using XDA Labs
saurabh808 said:
i hv only one issue
cell standby battery drain as huge as 30%
Click to expand...
Click to collapse
I am experiencing "Cell standby" battery drain as well. Any solution?
ppihoo said:
I am experiencing "Cell standby" battery drain as well. Any solution?
Click to expand...
Click to collapse
I have it too guess we wait till Samsung sends out the update
ppihoo said:
I am experiencing "Cell standby" battery drain as well. Any solution?
Click to expand...
Click to collapse
I guess even Samsung couldn't figure it out thats y there is delay in ota updates for other regions
Got BTU oreo through ota. No issues whatsoever yet.Phone feels a lot smoother in day to day usage!
I can confirm that there's high cell standby drain.
Battery life is a bit of a letdown as it's a little less compared to last nougat release.
Is it possible to downgrade same way?
Install nougat again and wait for good oreo?
ppihoo said:
Is it possible to downgrade same way?
Install nougat again and wait for good oreo?
Click to expand...
Click to collapse
I wouldn't recommend going this route, its better to wait for the next oreo update then downgrading which could brick your device..
Sent from my S7 Edge using XDA Labs
Cell standby drain for me.. on light usage without any gaming and with every connectivity disabled such as gps, wifi, bluetooth, nearby and auto sync disabled too. Not such a great battery life, little less as compared to last nougat release as I mentioned few posts earlier.
Sent from my S7 Edge using XDA Labs
I purchased my nexus 6p last week through ebay. It was running well, but the battery life was not what I expected. It had locked bootloader, so there is no problem because of rooting or installing custom roms. I didn't know about the bootloop issue before purchasing this phone. I read battery life degraded after nougat update. I'm currently on oreo and I tried installing the stock marshmallow image from google but I get a device has became corrupt error, I just want to observe if the battery life becomes better after I install marshmallow. I can live with the old version if I can use it more than being on the latest version. Any help would be appreciated as I want to use this phone as a daily driver.
AmeyDude said:
I purchased my nexus 6p last week through ebay. It was running well, but the battery life was not what I expected. It had locked bootloader, so there is no problem because of rooting or installing custom roms. I didn't know about the bootloop issue before purchasing this phone. I read battery life degraded after nougat update. I'm currently on oreo and I tried installing the stock marshmallow image from google but I get a device has became corrupt error, I just want to observe if the battery life becomes better after I install marshmallow. I can live with the old version if I can use it more than being on the latest version. Any help would be appreciated as I want to use this phone as a daily driver.
Click to expand...
Click to collapse
To flash stock Google ROM you have to have an unlocked bootloader. If the message you are referring to appears like the image below, it is normal with unlocked bootloader. The battery on these phones are notoriously awful with age (3 hours or less SOT) , marshmallow or not. If you want to use phone as your regular device I'd have the battery replaced.
Aimless Rambler said:
To flash stock Google ROM you have to have an unlocked bootloader. If the message you are referring to appears like the image below, it is normal with unlocked bootloader. The battery on these phones are notoriously awful with age (3 hours or less SOT) , marshmallow or not. If you want to use phone as your regular device I'd have the battery replaced.
Click to expand...
Click to collapse
The message I get says " Your device is corrupt and it may not function properly." It's quite difficult to replace the battery at my place, so I'd first like to try a workaround.
AmeyDude said:
The message I get says " Your device is corrupt and it may not function properly." It's quite difficult to replace the battery at my place, so I'd first like to try a workaround.
Click to expand...
Click to collapse
You may want to go through the guide below.
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Just flash stock marshmallow on it. There are plenty of guides here. Unlock bootloader, install adb bridge, instal the nexus 6p adb drivers, and flash the stock firmware. Im also noticing battery life decreased so ill be going back to M too and test it out