NOTE 8 sm n950f firmware error problems - Samsung Galaxy Note 8 Questions and Answers

i have a note 8 sm n950 i done the android update a few months ago and and it got my phone stuck in a boot loop, i installed new firmware which i was able to use the phone again but lost data signal, i fixed that but now my calls and text are coming through with a german number (im in the UK) i have tried to install stock firmware using odin and keep getting sw rev check fail device 11 binary 6 (and other variations of that error) i have also tried clearing the cache and wiping the phone from the boot menu but no luck, could anyone help, i would be very grateful

Have you check that you have downloaded and installed the correct version of the OS on your device?

pazler said:
i have a note 8 sm n950 i done the android update a few months ago and and it got my phone stuck in a boot loop, i installed new firmware which i was able to use the phone again but lost data signal, i fixed that but now my calls and text are coming through with a german number (im in the UK) i have tried to install stock firmware using odin and keep getting sw rev check fail device 11 binary 6 (and other variations of that error) i have also tried clearing the cache and wiping the phone from the boot menu but no luck, could anyone help, i would be very grateful
Click to expand...
Click to collapse
The binary error you are getting is because you are trying to flash older filmware than what is already on the phone., this is not possible because of security updates. Downloading the latest filmware for you device should resolve this error, and then hopefully fix the other errors you face.

stonedpsycho said:
The binary error you are getting is because you are trying to flash older filmware than what is already on the phone., this is not possible because of security updates. Downloading the latest filmware for you device should resolve this error, and then hopefully fix the other errors you face.
Click to expand...
Click to collapse
im pretty sure i have tried the latest one for my phone, as i have tried many others but i was never 100% certain it was, could you point me in the direction of one?

pazler said:
im pretty sure i have tried the latest one for my phone, as i have tried many others but i was never 100% certain it was, could you point me in the direction of one?
Click to expand...
Click to collapse
In post number 2 in the thread below, you can install "samfirm" on your Pc, this will give you the latest update to download, at a fast speed. For region (on samfirm) put your service provider, ie BTU or XEU for the UK.
https://forum.xda-developers.com/galaxy-note-8/how-to/official-stock-firmware-update-odin-t3677072

stonedpsycho said:
In post number 2 in the thread below, you can install "samfirm" on your Pc, this will give you the latest update to download, at a fast speed. For region (on samfirm) put your service provider, ie BTU or XEU for the UK.
https://forum.xda-developers.com/galaxy-note-8/how-to/official-stock-firmware-update-odin-t3677072
Click to expand...
Click to collapse
seems to of worked fine, no problems yet, thank you!

pazler said:
seems to of worked fine, no problems yet, thank you!
Click to expand...
Click to collapse
Glad to hear :highfive:

stonedpsycho said:
Glad to hear :highfive:
Click to expand...
Click to collapse
sooooo.... it was working fine for a couple days then the phone froze with a glitched horizontal line on the screen, i rebooted the phone and thought nothing more of it. A day later did the same thing (different place in the screen this time) i have wiped the cache a few time times but it hasnt improved. It is also freezing on the samsung loading screen and or getting stuck in a boot loop, the phone does work normaly for short amounts of time (few hours or so) but keeps happening, i managed to copy this log from the recovery menu if any help
p.s this is simlar to the original problem i was having before i changed the firmware
fail to open recovery_cause(no such file or directory)#
#reboot recovery cause is [unknown]#
support single-sku
file-based OTA
supported API: 3
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
# manual mode v1.0.0#
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT'(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/cid/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/cid/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/permissioins'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/permissioins'.(No such file or directory)
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree/firmware/android/compatible' : no such file or directory
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree/firmware/android/compatible' : no such file or directory

pazler said:
sooooo.... it was working fine for a couple days then the phone froze with a glitched horizontal line on the screen, i rebooted the phone and thought nothing more of it. A day later did the same thing (different place in the screen this time) i have wiped the cache a few time times but it hasnt improved. It is also freezing on the samsung loading screen and or getting stuck in a boot loop, the phone does work normaly for short amounts of time (few hours or so) but keeps happening, i managed to copy this log from the recovery menu if any help
p.s this is simlar to the original problem i was having before i changed the firmware
fail to open recovery_cause(no such file or directory)#
#reboot recovery cause is [unknown]#
support single-sku
file-based OTA
supported API: 3
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
# manual mode v1.0.0#
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT'(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/cid/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/cid/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/permissioins'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/permissioins'.(No such file or directory)
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree/firmware/android/compatible' : no such file or directory
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree/firmware/android/compatible' : no such file or directory
Click to expand...
Click to collapse
This is beyond my knowledge. I would take a guess that you have some sort of hardware issue as flashing stock filmware usually resolves any software bug. Hopefully someone who has faced the same or someone more knowledgeable will be able to help you further.

HI Experts i am getting the same issue in my note 8 sm-n950f according to my knowledge i lost its efs and baseband partition by mistake and my phone now stuck on Galaxy Logo now the OEM System is locked by default i am not able to flash TWRP please Suggest me how can i recover pretty phone back in Normal Condition :crying:

mehroz1234 said:
HI Experts i am getting the same issue in my note 8 sm-n950f according to my knowledge i lost its efs and baseband partition by mistake and my phone now stuck on Galaxy Logo now the OEM System is locked by default i am not able to flash TWRP please Suggest me how can i recover pretty phone back in Normal Condition :crying:
Click to expand...
Click to collapse
As we have said many of times before, if you lost your EFS folder and you never made a backup of it then you're screwed and you'll need to send it to Samsung for repair because you can't use anyone else's EFS because the EFS holds your IMEI and the phones serial numbers and such. It's information that's never supposed to be removed or deleted.. However someone else said if you delete certain stuff in the EFS folder and then reflash it that it would work and I tried this method and it failed to work so I don't know any other way except sending it to Samsung repair facility.. It also requires root access which you obviously can't do since it's OEM is not unlocked so I really doubt there's anything you can do short of sending it to Samsung..
https://forum.xda-developers.com/ga...i-detect-sim-card-t4134733/page2#post83127549
This is the link but like I said this didn't work for me..

Related

"E: Can't mount /dev/block/mmcblk0p2 (Invalid argument) E:/copy_data_default_apk:Can'

"E: Can't mount /dev/block/mmcblk0p2 (Invalid argument) E:/copy_data_default_apk:Can'
I know you guys don't like new posts, but I've spent the past 2 days trying to figure this out and I am about to give up.
I'll just lay this out in bullets and this is just a last attempt before I throw this phone out:
Phone: GT-i9000 bought full price from Bell, unlocked running on Fido
Rom Installed: ROM Name: All In One Edition Version: 7.0 Developer: Spike_M Firmware: XXJPY
I shut the phone off because it stopped responding to any touches, turn it back on and its stuck on the SAMSUNG GALAXY S Logo.
Can enter DOWNLOAD mode using three button combo, but not RECOVERY mode.
This means that I tried to flash a new FW using ODIN. What I tried to flash:
Used:
Odin3 v1.3
PDA = I9000XXJPU-REV03-PDA-low-CL747761.tar
PIT = s1_odin_20100512.pit
PHONE = MODEM_I9000XXJPU.tar.md5
CSC = GT-I9000-CSC-MULTI-OXAJPU.tar.md5
When I click Start on Odin with either ☐ Re-Partition or β˜‘ Re-Partition, it reboots into RECOVERY mode, "Wipes Data", and gives me this error message:
HTML:
"E: Can't mount /dev/block/mmcblk0p2 (Invalid argument) E:/copy_data_default_apk:Can't mount DBDATA: your storage and not prepared yet. Please use UI menu for format and reboot actions."
and just hangs.
I found this link: forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage
and tried the solution. I can access the adb shell when the phone is stuck in recovery mode, but I don't have root access so I can't push any files like parted onto the /sbin folder because it says "Permission denied"
If anyone can tell me if phone is a lost cause, I can stop trying already and get on with my life. If anyone can help, I would really appreciate it. Thanks a lot.
my "E: can't mount /dev/block/mmcblk0p1" problem has been solved by this.
It may not be the same problem but the following solved my "E: can't mount /dev/block/mmcblk0p1" problem, not "E: can't mount /dev/block/mmcblk0p2". I used JM2, 512 pit.
Credit to Margaliini
1. Enter your phone in dl-mode, but don't connect yet.
2. Open Odin, tag re-partition, auto reboot and f.reset time, make sure efs clear and bootloader -fields are NOT checked. select CORRECT PIT-file (2.1 ROMS usually 512, 2.2 ROMs many times 803, samfirmware always tells which one to use next to the dl-link of a ROM-file), enter your phone in dl-mode, plug, wait it to be recognized by Odin.
3. Click start, wait until Odin shows PASSED, unplug your phone, remove the battery for 30 seconds, enter dl-mode again, don't plug just yet.
4. In Odin, click Reset. Then select PDA, Modem and CSC files compatible with the PIT-file used in re-partition, plug your phone, make sure re-partition NOT checked and no PIT-file selected (once again, make sure you use correct PDA for the PIT you flashed). auto-reboot and f.res.time should be selected. Make sure efs clear and bootloader -fields are NOT checked.
4- Plug your phone and when recognized, click start. Wait to be passed. Now your phone will boot (or if not, boot manually) and should work just fine.
Edit: Try to put Eclair ROM, for example JM2, not jpa, and see if it works better.
Thanks, I'll try that and report back to you...
Please help me I have this problem your suggestion did not work please help
and thanks
alaaflashaliraqi said:
Please help me I have this problem your suggestion did not work please help
and thanks
Click to expand...
Click to collapse
u can try this
Solved
If problem is still valid, I have found a kind of solution (or rather workaround) which can be found on YT.
www youtube com/watch?v=zdMhYYdMB08
Best regards
fteller said:
If problem is still valid, I have found a kind of solution (or rather workaround) which can be found on YT.
www youtube com/watch?v=zdMhYYdMB08
Best regards
Click to expand...
Click to collapse
Using some advice from your guide along with the fix found here, I was able to revive my once unresponsive internal sdcard http://forum.xda-developers.com/showthread.php?t=1665123
How did you mange to fix this Mount problem finally ?
E: Can't mount/dev/block/mmcblk0p2 (invalid argument
E:copy_data_default_apk:Can't maount DBDATA
Mu phone gets into download mode , and recognized by Odin (i have tried to put I9000xxJPU the download process was finished with no error, but when the phone made restart to start the update process i got the error message above). since the the phone is stuck in endless loop on the main samsung opening screen.
I tried to do this tip : (with the I9000xxJPU)
http://www.youtube.com/watch?v=zdMhYYdMB08
but got the same result ...i am not convinced that's the same error as mine ...
Please , any replay will be of great help.
Ran:fingers-crossed:
find dbdata
u can see here for i9000
http://forum.xda-developers.com/showthread.php?p=38025542
Sent from my GT-I9000 using xda premium
Apply again stock with pit file ...this error will finish.
Sent from my GT-I9000 using xda app-developers app
Dont work still
Hi ,
Thanks for your replay.
I tried to put the dbdata.tar file in the link that you said .
The phone seems to update dbdata when its satrted, but still get stucked with the same error...
Do you think a new stok will solve it ? i tride already 3 of thoes...(if you can give a link for somthing that you think that is recommanded i will be greatfull)..
Any outher guesses?
---------- Post added at 08:42 AM ---------- Previous post was at 08:38 AM ----------
Hi ,
Thanks for your replay.
I tried to put the dbdata.tar file in the link that you said .
The phone seems to update dbdata when its satrted, but still get stucked with the same error...
Do you think a new stok will solve it ? i tride already 3 of thoes...(if you can give a link for somthing that you think that is recommanded i will be greatfull)..
Any outher guesses?

[Q] i9000 bricked, help!

so my brother's phone got bricked for some reason. I tried searching for answers but I can't find answers. I'll be detailed as possible so imma list down the problems
Problems:
1. When turning on the device, it gets stuck on the Samsung Galaxy S logo
2. I can open recovery mode (CWM v3.0.0.5) but then these errors show up:
"E: unknown volume for path [/data]
E: Unable process volume! Skipping...
E: can't mount /cache
E: can't open /volume"
...etc
3. ADB can't see/detect the device
4. Went to Download mode but then Odin does not detect it. (I have the latest drivers from Samsung. I also tried connecting my Note 2 and Odin can detect it. I also tried different cables but none would work)
5. Tried inserting an SD card but i cant seem to find a way to flash from a zip file
6. Also tried restoring but errors appear (see #2)
How it got bricked:
My brother said that he simply rebooted the phone because of lag and that happened.
I'm not sure if USB debugging's on before this phone got bricked.
It's running Optimum Jellybean by Likeman and yes it's rooted
Help please (

Huawei P10 Lite, TWRP Error 9, pls HALP

Hello everyone,
My phone is in what it seems to be erecovery loop, I tried flashing images via fastboot extracted from update.app file, didnt work at all.My phone is unlocked, I flashed twrp again and downloaded latest stockrom version for my country(asked a friend about it since he has the same phone), I put those 3 files on my usb and connected it to my phone.Opened it in twrp, when i try to flash update.zip i get Error 9.I tried pretty much anyting i could find on this forum and other sources from google, nothing rly seems to work and there isnt anything at all for error 9.Do u guys by any chanse know what is the problem here?
device: Huawei P10 Lite WAS-LX1C432B194 (latest version for my country, Serbia, Eu)
phone unlocked, twrp installed, can do fastboot commands
This is what i get when trying to flash that update.zip
Code:
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Formatting Cache using make_ext4fs...
Wiping data without wiping /data/media ...
Done.
Updating partition details...
...done
Installing zip file '/usbotg/update.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
mountencrypt: failed to mount /data: Success
script succeeded:resut was []
check_write_data_to_partition,write data error
[COLOR="Red"]E:unknown command [errno][/COLOR]
update_huawei_pkg_from_ota_zip: update package from
zip failed
[COLOR="red"]Updater process ended with ERROR: 9
Error installing zip file '/usbotg/update.zip'[/COLOR]
Updating partition details...
...done
There is already a thread for this problem: https://forum.xda-developers.com/mate-7/help/softbricked-device-fix-t3159742/page5
LwannaCM said:
There is already a thread for this problem: https://forum.xda-developers.com/mate-7/help/softbricked-device-fix-t3159742/page5
Click to expand...
Click to collapse
I already firgued it out, but tnx for the response.
I bought sd card(didnt have one), did dload method, since normal one approach didnt work i used force update approach(dload moved to sd card, power off, hold vol+ + vol- + power button and it installed) also i needed to flash stock recovery beforehand(so it removes twrp, used fastboot to do it, phone was unlocked, power off connect to PC via usb cable and hold down vol- right away, then flash it through fastboot), it cant do force update with twrp still installed.Once it was done i normally booted to stock rom, phone was no longer unlocked, now i unlocked it flashed twrp and rooted it, everything works just fine.Hope it helps some1 with the same problem.
source: https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097 , there is guide thing for both normal and force update
Thank for the help. It gives me a clue but I am still struggling as the force update approach get stuck at 5%. Thanks anyway.

Android Q update problems

Hello,
I'm struggling with my s10, SM-G973F, i was rooted and twrp etc, then i decided that i want the q beta, went to ASII signup for the members ap to get the beta and tried 3 way's to run the update by SD card - could not mount the sd card and adb way and this failed, and offcourse i tryed trough the phone Software update but this had failed as well, can anyone give me a hint hot get this done.
When i'm on ASII if i try by card i get:
Reboot recover Cause is [BL: Recovery Mode is set by key)#
Support SINGLE-SKU
#Manual Mode v1.0.0#
E: Failed to mount /sdcard: no such file or directory
-- Couldn't mount sdcard.
Installation Aborted
When i do it trough adb is say it successful but i get every time on botloop , and i have downloaded the update from different sources.
Updated firmware to BTU: ASJD trough smart switch and then followed the the steps and downloaded the update ZSK3 (it showed directly beta 3) trough the software update from settings, after all done i end up in bootloop again.
Can anyone help with this, i spent my Saturday on this silly thing.
Many Thanks
Did you relocked the bootloader?

Accidentally Disabled OEM Unlock on SM-N950N (w/ SM-N950F CSC), how to Recover Data?

Hey guys,
Here's the situation. I was in the process of completing the setup of my 768GB Note 8 (SM-N950N) with Dr.Ketan P12 custom ROM, and RZ Kernal (for DriveDroid support). Out of nowhere, my Note 8 camera just stopped working, and the Dr.Ketan ROM Tools and Tweaks Pro apps could no longer be opened. I began back-tracking my steps; tried reverting magisk back to v20.1, tried dirty flashing the ROM again, all to no avail. In the process of troubleshooting, figured it could be something I toggled under developer settings. Noticed that my OEM Unlock toggle was turned on, even though I recall seeing it turned off earlier during the configuration process (as explained by @dr.ketan here, scroll to Note for OEM Issue). Thinking it's ineffective, I turned it off and was prompted to reboot my device, just to get stuck at the boot screen
I came across the following forum post describing how to recover from the boot loop, without needing to delete any data, by flashing the latest available official firmware AP***.tar (removed the .md5 extension) file using Odin3:
https://forum.xda-developers.com/sprint-galaxy-s6/help/custom-binary-blocked-frp-lock-how-t3581010
The problem is, during the flashing of the Dr.Ketan P12 custom ROM, I chose to flash the SM-N950F OMC for SM-N950N, in order to use a Korean-Free CSC (more details on why explained here). So, even though I've attempted all of the following:
- flashed the current latest available official firmware AP***.tar file for SM-N950N,
- simultaneously flashed the current latest BL/CP/HOME_CSC***.tar.md5 and AP***.tar firmware files via Odin,
- flashed the latest TWRP***.tar custom recovery (failed probably due to OEM unlock being disabled),
- wiped cache via the stock recovery,
- tried booting via the "Lacking storage booting" option in the stock recover,
- tried booting to safe mode,
- tried using Smart Switch for PC, it (nor its Emergency Software Recovery) never detected my Note while stuck at the Samsung boot logo, nor did it detect it in Recovery mode,
- etc.​it still won't boot-up, and I think it's due to the CSC (UK Unbranded - BTU) not being available in the official firmware.
When I boot into recovery mode, I get the following message:
Code:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
Support SINGL-SKU
File-Based OTA
Supported API: 3
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
# MANUAL MODE v1.0.0#
can't open directory '/system/omc/SUP/etc/sysconfig' . (No such file or directory)
can't open directory '/system/omc/SUP/etc/cid/sysconfig' . (No such file or directory)
can't open directory '/system/omc/SUP/etc/permissions' . (No such file or directory)
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree/firmware/android/compatible' : No such file or directory
Would any of you folks have suggestions on how I could recover from this mess without needing to delete any data? Perhaps if there was a way I could add the UK Unbranded CSC to the official SM-N950N firmware and flash it via Odin, maybe that'll allow it boot? Please kindly advise, thanks in advance.
Bump
please i have the same proplem what to do
i dont know the meaning of bumb
please help
ah_1st said:
please i have the same proplem what to do
i dont know the meaning of bumb
please help
Click to expand...
Click to collapse
No luck on my end, lost months worth of data on my internal storage. Had to perform a factory reset on my Note 8 via Odin, reflash TWRP via Odin, then reflash my Custom ROM and tweaks. Lesson learned for real though

Categories

Resources