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
Related
Hello,
My girlfriend bought new Galaxy A5 2016 (gold) on 15/03. Already while I was completing some settings (Google acc / Sams acc "in" and install of such mere apps as viber, skype, facebook..) the phone restarted on its own twice, without any logical explanation (no significant load, no root, since the divice was almost stock).
This bug has occured while this week two or three times a day. Unfo I cannot associate it with any app or particular action. The phone reboots even in sleep mode or when screen is active.
It doesn't look like hardware deficiency. I tried to delete Google Play Services updates (suggested by local Sams support), hardreset and etc., however - no success. The phone continues to restart its own
Have no idea what to do Can you help me?
best regards
Teleri said:
Hello,
My girlfriend bought new Galaxy A5 2016 (gold) on 15/03. Already while I was completing some settings (Google acc / Sams acc "in" and install of such mere apps as viber, skype, facebook..) the phone restarted on its own twice, without any logical explanation (no significant load, no root, since the divice was almost stock).
This bug has occured while this week two or three times a day. Unfo I cannot associate it with any app or particular action. The phone reboots even in sleep mode or when screen is active.
It doesn't look like hardware deficiency. I tried to delete Google Play Services updates (suggested by local Sams support), hardreset and etc., however - no success. The phone continues to restart its own
Have no idea what to do Can you help me?
best regards
Click to expand...
Click to collapse
Are you use memory card/sd card? Try to remove that...
It happened to me the same thing on my old Desire S... The battery were not firmly pushed in its location... So, you could verify that!
hi,
i have the same trouble with my new A5 2016. the phone reboot from itself during the night or the day without any reason... happened 4-5 since March, 14.
a friend with the same a5 2016 has same issues.
We have no SD card, no root, stock.
if anyone have a solution, that would be great !
Model : SM-510F
HellBouy said:
hi,
i have the same trouble with my new A5 2016. the phone reboot from itself during the night or the day without any reason... happened 4-5 since March, 14.
a friend with the same a5 2016 has same issues.
We have no SD card, no root, stock.
if anyone have a solution, that would be great !
Model : SM-510F
Click to expand...
Click to collapse
Reflash stock rom...
I don't have this issue at all , try a factory reset or flash a stock rom.
Hi,
I've bought a A5 2016 in February (Rom stock, No root, dev options unmasked) - Since then, I've Had 3 power off on its own. I've followed forums and wiped my cache. But this morning I had my phone restart on its own.
I'm quite mad at Samsung for now.
Maybe try calling samsung support?
I have had this problem with my A5 too. Whenever the device updates some app, it re starts.
What exactly occurs during the restart? Does the phone vibrate and show "samsung galaxy a5 (6) powered by android" or does it simply play the boot animation without audio.
If the second option is happening with you., then I suggest you re flash the stock Rom. You can get the stock rom from you mobile or San mobile.
I have the A5(2016) from 2/3 weeks but I never had this problem. If you have the A510F model you can try the German firmware (A510FXXU2APC4 - (build version LMY47X.A510FXXU2APC4). Flash it via odin and donwload the firmeware from sammobile.com. for odin guide see here http://forum.xda-developers.com/samsung-a-series/help/rom-stock-firmware-samsung-galaxy-a5-t3305863
To Ahmad89:
Thanks for your response. I actually had logo A5-6 powered by android during restart. I remember to have switched on WiFi connection before it restart (i know that updates occurs only when WiFi's on). That may be an explanation. there may may have been an attempt to update. But the "switch off on its own" event seems more annoying. I did remember one time my phone went off when charging and at that time i used non official Samsung charger. perhaps it was linked to fast charging and a powerless charger that shuted the phone off. What about the two others occurrences when it went off? (the phone being in stand by mode). I can imagine every scenario but no valid explanation.
To zyxw :
I've had the phone update to XXU2APC4 since 3 hours.
I'll do my best to stay in touch for relevant news.
Thanks.
Parmaggedon said:
To Ahmad89:
Thanks for your response. I actually had logo A5-6 powered by android during restart. I remember to have switched on WiFi connection before it restart (i know that updates occurs only when WiFi's on). That may be an explanation. there may may have been an attempt to update. But the "switch off on its own" event seems more annoying. I did remember one time my phone went off when charging and at that time i used non official Samsung charger. perhaps it was linked to fast charging and a powerless charger that shuted the phone off. What about the two others occurrences when it went off? (the phone being in stand by mode). I can imagine every scenario but no valid explanation.
To zyxw :
I've had the phone update to XXU2APC4 since 3 hours.
I'll do my best to stay in touch for relevant news.
Thanks.
Click to expand...
Click to collapse
which one ?? Germany (DBT) firmware ??
Tell me if you will have again the random reboots!
zyxw-androidiani said:
which one ?? Germany (DBT) firmware ??
Tell me if you will have again the random reboots!
Click to expand...
Click to collapse
I had the update by Kies I presume. I did it by updating the phone in settings/software update. I had several times used Odin for my note 3 but for my A5 i didn't want to flash the whole ROM. My country is France. The New baseband is A510FXXU2APC4 and the version Number is LMY47X.A510FXXU2APC4.
At this time no restart or shut off by its own - but too soon to validate.
I will do a wipe cache very soon.
I'll warn you once restart or shut down happen, if so. :fingers-crossed:
We have the same build version so maybe you will not have the problem!
I have PC4 too , no issue so far.
Sent from my SM-A510F using XDA-Developers mobile app
I have the phone fro 7 days and reboot it himself one time. I dont remember if do this after or before update to apc4. Will see. For now, I'm happy with this phone. I'm dissapointing about no screenmirror.
Trimis via Tapatalk
No restart on its own since my 8 day's last post. Hope this will last...
Pd1 firmware version, 128mo usd kingston, official usim from provider, no reboots at all, same with february and march update, everything fine, everything smooth...
i had also same problem in my new galaxy A7 2016 but after hard reset it works fine..and i observed this happens bcoz of poor ram managment n samsung touch wiz software issue ...so might b it will ressolve after marshmallow update..i m also waiting for new update.
i have same problem when i use VPN
I have android 6 and not use touchwiz. I use another launcher and OpenVPN and work fine from 1 year.
Trimis via Tapatalk
G935FD Exynos, stock firmware updated via air.
Now it says Android 7.0 G935FXXU1DQEM, DQG1.
I often face the bug when the phone is expected to automatically connect to my home or job's WiFi, but in 50% cases it doesn't. When examined i found out that sometimes SSID list is outdated and stuck, and it won't refresh as I tap on refresh button. The only solution yet is to turn wifi off and then on. After such procedure the phone behaves as expected for some period of time.
Anybody has a remedy for this bug? Forgive me ROM makers and fans, nevertheless I won't take an advice to flash a custom firmware. Thanks.
Yes , since july update there are wifi issues that i am suffering from , and august update didnt solved either , the only way would be download stock firmware from may patch from sammobile and flash via odin or wait for next update to solve these issues
Hi there. The strangest thing happened to me today.
Didn't have the patience to wait an oreo update on my galaxy s8 and downloaded it (official firmware not beta version), installed it using odin and ran the software for a week without any issues. I admit the firmware was ment foe germany, not for my country but i know that it doesn't matter as long as the firmware is an official one. Today in the morning got a notification that phine memory is almost full and notices that my oreo saw only 16gb of memory instead of 64. Did a quick factory reset and from this point on my pfone went crazym enterd into a nasty bootloop, couldn't do a thing with my phone. Tried erase/restore factory setting /erase cache partition, the same result. Ok, downloaded nougat, installed it, phone seems ok with one exception. My nougat looks kinda oreo! Some icons in the phones settings look like oreo icons, bixby under oreo does not have a disable key option under nogat there is a disable key - i don't have that though i use nougat, some icons in the settinga menu are doubled and so many other weird things. If i check software version it states 7.0. Ok, later in the afternoon saw that there was released oreo for my country, checked software update...says that it is up to date. My friends's phone is identical to mine, he got the oreo update, i didn't. Any idee what is going on? How in the world can i have nougat on my phone with oreo icons after a fresh nougat install? I know it sound weird but i have had several samsung phones and have played around with official firmwares but never saw such a great mess my phone is in. Or maybe i am missing something. Thanks alot for your time. Cheers.
Lolobacsi said:
Hi there. The strangest thing happened to me today.
Didn't have the patience to wait an oreo update on my galaxy s8 and downloaded it (official firmware not beta version), installed it using odin and ran the software for a week without any issues. I admit the firmware was ment foe germany, not for my country but i know that it doesn't matter as long as the firmware is an official one. Today in the morning got a notification that phine memory is almost full and notices that my oreo saw only 16gb of memory instead of 64. Did a quick factory reset and from this point on my pfone went crazym enterd into a nasty bootloop, couldn't do a thing with my phone. Tried erase/restore factory setting /erase cache partition, the same result. Ok, downloaded nougat, installed it, phone seems ok with one exception. My nougat looks kinda oreo! Some icons in the phones settings look like oreo icons, bixby under oreo does not have a disable key option under nogat there is a disable key - i don't have that though i use nougat, some icons in the settinga menu are doubled and so many other weird things. If i check software version it states 7.0. Ok, later in the afternoon saw that there was released oreo for my country, checked software update...says that it is up to date. My friends's phone is identical to mine, he got the oreo update, i didn't. Any idee what is going on? How in the world can i have nougat on my phone with oreo icons after a fresh nougat install? I know it sound weird but i have had several samsung phones and have played around with official firmwares but never saw such a great mess my phone is in. Or maybe i am missing something. Thanks alot for your time. Cheers.
Click to expand...
Click to collapse
Flash it again with the current release for your region using ODIN with CSC that will wipe your phone also.
Should fix it.
rigocalin said:
Flash it again with the current release for your region using ODIN with CSC that will wipe your phone also.
Should fix it.
Click to expand...
Click to collapse
Hi,
Found out what was the problem. Each and every time when i was using odin to flash my phone, used only the AP file. Saw somwhere that someone added in odin the AP, BL, CP, CSC files too. Sammobile says that ony the AP file should be used (no doubt) but didn't work in my case.
So, added all 4 files in odin and could sucessfully flash nougat, then update to oreo. Got curios if i flashed oreo only, would my phone lose it's mind and flashed it BUT added in odin all the 4 files and worked like a charm.
Thanks alot for your time.
Cheers.
Im using a Galaxy s7 edge exynos and I have been trying ALL day to return to stock firmware. (was aiming for 6.0, but when that didnt work I started trying 7.0 with slightly more success...) I was previously rooted via magisk using TWRP. I am not able to flash all 4 files at once via odin, (BL, AP, CP, CSC) I quickly get an error on both the device and odin (decive says binary 2 device something... Odin stops at either Param.bin or cm.bin depending on which CSC I use) the BL file seems to be the one that refuses to flash (from any of the 4 versions of odin i have and using different firmware versions that previously worked on the phone)
I am able to flash just the AP, CP, and CSC but when android loads up my mobile data doesnt work and many other things dont work correctly as well ...
I am so confused as to what I can even possibly do now. Im sitting here with a phone that wont correctly software update that I cant correctly root and has no mobile data. No full 4 files will correctly flash without odin error. TWRP gives me crap now too. I have wiped and formatted all the data many times hoping id missed something.
Send help
also
I try to manually update and it says "registering device" for a sec and then "Process failed" Like android 7.0 is running but not how it was before. I did update to newest update via the phone before i decided to try to revert to android 6.0 again because I was having issues connecting my pokemon go+
Hmmmm I still have problems with 5ghz and mobile data but i got magisk to install... luckily im not using this for phone purposes. this is the best i can do without help
What is yohr phone model ?
G935f
G935f
Currently running g935fd
Did you flash and Oreo rom by anychance?
"Maybe", i say maybe if you did thats why you cant go back to a < 8.0 version
riseofsand said:
Did you flash and Oreo rom by anychance?
"Maybe", i say maybe if you did thats why you cant go back to a < 8.0 version
Click to expand...
Click to collapse
I didn't try anything with oreo until like 10 hours of failing everything and reading everything I could find. It was unofficial and apps wouldn't install or update correctly. So actually what I got to semi work was 7.0 again. Build G935FXXU1DPLT. It doesn't show cell tower signal or work with 5ghz anymore but I got magisk installed and I can run apps off of wifi. (Same as before 8.0 but got magisk working this time)
I'd still like to try to get my 5ghz and cell signal (just in case something happens to my main phone) but I'm scared to soft brick my phone for the 1000th time in 2 days when I managed to get it semi working.
CactuarKing said:
I didn't try anything with oreo until like 10 hours of failing everything and reading everything I could find. It was unofficial and apps wouldn't install or update correctly. So actually what I got to semi work was 7.0 again. Build G935FXXU1DPLT. It doesn't show cell tower signal or work with 5ghz anymore but I got magisk installed and I can run apps off of wifi. (Same as before 8.0 but got magisk working this time)
Click to expand...
Click to collapse
Last time something like that happend to me, is because i was flashing the wrong stock rom (same model but wrong original carrier) sometimes it does matter, sometimes not
I was worried I might have messed it up for good as well luckily I'm not completely stuck but I still dont understand why I couldnt just 100% flash my OS via odin like I always do. Although I got cocky and started without following instructions up on the computer this time. Just my luck
double check mod #it can change with different roms my s5 tmobile g900t originally now its grown into g935f S7 edge
Hi All,
So, I have spent 2 days trying to get my Galaxy s8+ back to normal. However, I seem to only have made it worse. It all happened when I decided to change the /data partition from ext4 to another format and then back again to get the /data partition to mount in TWRP after flashing Pascal Rom. However when I rebooted, nothing worked, no boot up screen, no recovery, no life, but all I could get was download mode. It then must of froze up after another restart and I couldn't get anything for 12 hours or so.
The next step I tried once i got download mode again was to flash stock firmware for the G955F, I can't remember the version of this firmware, but I still had nothing change. So then i flashed the latest firmware from SamFirm's downloading client, which was G955FXXU2CRF7 - Australian Optus Branded Firmware (OPS). I was able to get as far as the "hello start screen" and then my phone restarted, it then tried to upgrade my system again, then started "erasing" and then it rebooted and I still had the same issue, nothing but download mode and still no recovery, it still wouldn't turn on. So I flashed the latest International/Unbranded Australian firmware (XSA) - G955FXXU3CRGH, still the same result. I now can't go back to the OPS version of firmware because I get the Check error with the bootloader (since it's a more recent version), so I can't go backwards. I also can only flash "Official Binaries" now. Oh and to make things worse, I read that Odin Option "Nand Erase" just erased user data, so I thought I might as well try it, and as a result, I now can't flash even the (XSA) firmware because of ODIN failing and I now have an "An Error has Occurred while updating the device software. Use the emergency recovery function in the smart switch PC Software.". I am a bloody idiot :good: . Oh, I have tried multiple versions of Both Samsung Kies & Smart Switch (Which both had the option for "recovery & initialisation"), however, I get a message that my device is unsupported after adding in my device model and S/N. I tried a PIT file and then found out it's now included in all the latest firmware img files.. so yeah lol. Fun times. Soooo I feel like I am out of Options, nothing I do is working. The worst of all this is my wife is not happy haha which means after years of tinkering with android phones (flashing custom ROMS, Kernels, Root Solutions, e.c.t ), this may be the end of the road for me if I can't fix this phone. I really hope this thread isn't true too : https://forum.xda-developers.com/galaxy-s8+/help/sm-g955fd-access-download-mode-t3748228
So Please, someone help me out if it is at all fixable even if it requires opening the phone up lol.
The stats i have on download mode are the following:
RMM State as Prenormal
OEM Lock: OFF
FRP Lock: OFF
CARRIER_ID: OPS (which is super weird because it only accepts XSA to be flashed :S )
Secure download: Enabled
System Status: Custom
Warranty Void: 1
Current Binary: Samsun Official
If you need more, just let me know.
Ok, quick update: I have got rid of the error that I mentioned. I managed to flash XSA firmware again, it went to the blue Andriod is updating the system screen, then started "erasing" then rebooted and nothing again, still only download mode available. Nothing happens when I try to turn it on or try recovery mode.
This firmware you mentioned XSA - G955FXXU3CRGH i would double check. As far as I know Australia doesn't have a version 3 bootloader yet whether unbranded.telstra or Optus.
Quick Update: Maybe Fixed now!
Even though no one has replied yet, as it's only been an hour or so. I just wanted to let anyone else know who is experiencing a similar issue in the future on how to possibly fix it.
This was a real nightmare, however quick disclaimer, I am not responsible for any damage incurred to your device/property by following my instructions.
So the way I have fixed it, is I flashed the AP file only (from the firmware zip i had downloaded from SamFirm) with "Auto Reboot" Off. When ODIN finished, I held the Vol Down + power button, to reset it. It gave me a blue "No Command" Screen, I then waited and it then went black and the recovery screen appeared. I cleared the cache, rebooted to bootloader, which it didn't turn back on, so I left it because I thought it was the same thing. Came back 10 mins later and turned it on (or hard restarted, can't remember) and it worked. It booted!
I did soon learn it looks like it was having a charging problem because it had no charge and kept telling me there was water in the port (even though it was dry), I restarted it again after putting it on a wireless charging pad and it is seeming fine so far with the USB charger. So big note to anyone in the future, that it could be possibly bugging out with charging as well if you can't get it back on. I did have the device tell me here and there the last two days that there was water in the port when it was off. So kinda weird.
I know this all sounds a little hocus pocus, superstitious almost, but hey, my phone is working, so maybe replicating my actions may just help lol. :cyclops:
spawnlives said:
This firmware you mentioned XSA - G955FXXU3CRGH i would double check. As far as I know Australia doesn't have a version 3 bootloader yet whether unbranded.telstra or Optus.
Click to expand...
Click to collapse
Oh right, well, I did hear that SamFirm is not supported anymore, as that's where that firmware came from. Maybe it's dishing out incorrect firmware now? Possible the structure of where ever it is getting its firmware from (pretty sure it's pulled from samsung) has possibly been altered?
Just for reference I use www.updato.com for downloading firmware it is usually up to date. No reference to the firmware you mentioned (not for Australia anyway)
The screenshot I took: Imgur link:
https://imgur.com/a/lqyzWW7
Interesting I'll keep a lookout for it. Still on nougat 7.0 (XSA) no plans to upgrade yet until some issues are fully resolved ( out of beta stage that is ).
spawnlives said:
Interesting I'll keep a lookout for it. Still on nougat 7.0 (XSA) no plans to upgrade yet until some issues are fully resolved ( out of beta stage that is ).
Click to expand...
Click to collapse
Yeah, it's seeming to work now, but my fast charge isn't working. However, my other oreo ROM didn't work with fast charge either. So i am unsure if it is my phone or an orio bug :/ lol
Well at least you got it working and not using as a door stop
that was really sad story man.....
spawnlives said:
Well at least you got it working and not using as a door stop
Click to expand...
Click to collapse
Yeah haha, so glad it's not a door stop haha