[Q] Softbricked SMN900V Note 3 [Errors on device/Odin/etc] - Verizon Galaxy Note 3 Q&A, Help & Troubleshooting

As the title states, this a Verizon Galaxy Note 3 SMN900VZKE 32GB I picked up today from someone for around 40$. The only caveat is that she said her husband was messing with ROMS and whatnot, and now the device is, what I assume, soft bricked. I picked the device up as a challenge to myself, but I'm at wits end now.
When I go into recovery mode, I get a stack of errors down below that state the following
Code:
E:failed to mount /system (Invalid argument)
# MANUAL MODE #
-- Appling Multi-CSC...
E:failed to mount /system (Invalid argument)
can't mount '/system' (Invalid argument)
E:failed to mount /system (Invalid argument)
Data reset/factory reset/wipe of cache partition do nothing.
On normal bootup, it hangs at the Samsung Logo, and doesn't move.
Any suggestions? If additional information is needed I'll be happy to accommodate.
Box states that the SW Ver is: N900VVRUBMJE, and when asked what the last flashed rom version was , it was N900VVRUDNK1.
As to whether it was side loaded, or if it was an OTA I'm not sure. I don't even know whether the phone is rooted or not. In download/Odin mode the top of the device reads as follows:
Code:
ODIN MODE
PRODUCT NAME: SM-N900V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK(KK): OFF
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A4, P1
SECURE DOWNLOAD: ENABLED
UDC START
Take note: I am unable to get anywhere besides Odin/Download Mode and Recovery Mode, I am unable to load up Android at all, KIES (3.0 or older) does not recognize the phone, current Samsung Drivers are installed running Window 8, and am unaware of what the previous owner actually DID to brick the phone.

tendoman said:
As the title states, this a Verizon Galaxy Note 3 SMN900VZKE 32GB I picked up today from someone for around 40$. The only caveat is that she said her husband was messing with ROMS and whatnot, and now the device is, what I assume, soft bricked. I picked the device up as a challenge to myself, but I'm at wits end now.
When I go into recovery mode, I get a stack of errors down below that state the following
Code:
E:failed to mount /system (Invalid argument)
# MANUAL MODE #
-- Appling Multi-CSC...
E:failed to mount /system (Invalid argument)
can't mount '/system' (Invalid argument)
E:failed to mount /system (Invalid argument)
Data reset/factory reset/wipe of cache partition do nothing.
On normal bootup, it hangs at the Samsung Logo, and doesn't move.
Any suggestions? If additional information is needed I'll be happy to accommodate.
Box states that the SW Ver is: N900VVRUBMJE, and when asked what the last flashed rom version was , it was N900VVRUDNK1.
As to whether it was side loaded, or if it was an OTA I'm not sure. I don't even know whether the phone is rooted or not. In download/Odin mode the top of the device reads as follows:
Code:
ODIN MODE
PRODUCT NAME: SM-N900V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK(KK): OFF
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A4, P1
SECURE DOWNLOAD: ENABLED
UDC START
Take note: I am unable to get anywhere besides Odin/Download Mode and Recovery Mode, I am unable to load up Android at all, KIES (3.0 or older) does not recognize the phone, current Samsung Drivers are installed running Window 8, and am unaware of what the previous owner actually DID to brick the phone.
Click to expand...
Click to collapse
What's the recovery version? (on top in Recovery Mode)
It should be one of the following: MJE, NC2, NC4, NJ6, or NK1. Check the version, enter Odin/Download Mode & flash full tar of the exact firmware version.

Top of the device reads as follows:
Code:
Android system recovery <3e>
KTU84P.N900VVRUDNK1

Wanted to post an update, thanks to you, hsbadr, the device is now operational! Thank you very much, It is much appreciated. After several days of downloading countless PITS, TARS, acquiring several headaches, and many beers drank, I'ts working beautifully. Again, thank you for your help!

tendoman said:
Wanted to post an update, thanks to you, hsbadr, the device is now operational! Thank you very much, It is much appreciated. After several days of downloading countless PITS, TARS, acquiring several headaches, and many beers drank, I'ts working beautifully. Again, thank you for your help!
Click to expand...
Click to collapse
Now your on that hsbadr status son!
Sent from my SM-N910V using XDA Free mobile app

Related

Samsung Galaxy S4 Unbrick [System Magicode check fail: boot]

Ok i am trying to fix my samsung galaxy s4 for-ever now.
When i go into recovery it says:
E: failed to mount /System (invalid argument)
E: can't mount /System (invalid argument)
then when i try to install stock firmware back it gives me this message:
Secure Magicode check fail: boot
when i try to add pit file into that it says
Secure check fail: pit
Secure magicode check fail: boot
Whenever i start my phone it just freezes on the logo
and i tried to do emergency recovery in kies but it doesn't detect my device. But on the ODIN it detects it but doesn't work
HELP!!!
i think i am progressing towards this!!!
i think i am progressing towards this stage!!!
i wiped sd card in recovery mode including eveything else( wiped dalvik , device cache and all) then my samsung gt i9500 got soft bricked then tried wiping device cache and hard reset but couldnt boot then to my bad luck tried to root via odin and it show pass remark but again couldnt be booted ..
now wt shld i do???
samsung care guys says only option to install firmware ... but 50% chance of device getting dead at my own risk !!!:crying:

help with bricked phone

so long story short i havent been in the rooting game at all in around 4 years so i tried to downgrade my phone and it got disconnected in the middle of the update and now it wont get off recovery, splash logo, and download mode. it WAS on 6.0.1 (cant remember which update) but i tried to reflash a pf4 stock rom in odin and it wont do anything after it says aboot.mbn. in recover it says cant mount /system. download mode is as stands
ODIN MODE
product name:smg900v
current binary:samsung official
system status: official
reactivation lockff
qualcomm secureboot enable (csb)
ap swrev:s1 t2 r1 a2 p1
secure download:enable
udc start.
recovery says...
android recovery
mmb29m.g900vvru2dpg2
verizon/kltevzw/kltevzw
6.0.1/mmb29m/g900vvru2dpg2
user/release keys
use volume up/down and power.
then further down says support api: 3
e: failed to mount /system(invalid argument
#manual mode#
appling multi-csc...
E:/failed to mount /system (invalid argument)
failed to mount ' /system' (invalid argument)
E: failed to mount /system (invalid argument
its my daily phone and i kinda need it so if anyone can help me out thatd be awesome so i dont have to buy another phone thanks in advance!
Have you tried to Odin back to PB1 and start over rooting upgrading, etc?
Sent from my XT1650 using Tapatalk
every time i try to do the pb1 update it fails... i have no idea why
Put this pit (https://www.androidfilehost.com/?fid=24052804347765167) in the pit tab in Odin and put the pb1 tar (https://www.androidfilehost.com/?fid=24438995911970571) in the ap tab in Odin then try to restore

New phone bricked itself after just 2 weeks

So eh, I've posted here in hopes someone might be kind enough to offer me some help.
I received a brand new J3 (2016) for my birthday not even 2 weeks ago. I intended to root so I activated the dev options and the usb debugging but decided to not proceed with the rest of the process and left it at that. A couple of days later the phone simply refused to turn on, responding only to download mode (vol down, home, power) and nothing else. After pressing all the buttons at the same time I was able to access the other menu (vol up, home, power) only to be greeted with a lot of errors ranging from
E:failed to mount /cache (invalid argument)
to
E:failed to mount /cache/recovery/last_kmsg (invalid argument)
(I can provide a full list if it's relevant, just know that they are all related to cache and recovery)
Clearing the cache does nothing, as does the hard reset; the errors persist.
I then decided to reinstall the firmware using odin, but after I press start, it goes into recovery then says failed.
Meanwhile, on the phone this is written:
ODIN MODE
SECURE DOWNOAD: ENABLE
MDM DOWNLOAD BLOCK: 0
PRODUCT NAME: SM-J320H
CURRENT BIN: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: ON
USB Init Start!
USB core reset done!
Custom Binary(RECOVERY) Blocked by FRP Lock
If this is because I didn't activated "OEM Unlocking" in dev tools, I'm afraid I can't do that now anymore.
Is is salvageable or I might as well throw it out the window?
Please help me, I am at my wits' end.

Galaxy S8 Stuck on "Powered by Android" Screen After Android 9 Update.

Hi guys I own an S8, SM-G950F. The previous software I was on was Android 8 U2 (can't remember exact one). I flashed the new DBT Android 9 software via ODIN (using CSC, not home CSC). However the phone stays in the "Powered by Android" screen and does not go any further.
I can go into the Samsung recovery mode and have tried wiping both the cache and data/factory reset but this seems to make no difference. As an alternative I have tried flashing the Android 8 files (with bootloader U4), which is successful in ODIN but shows "No command" when booting.
USB debugging was also turned on before applying this update.
Other info:
FRP Lock: Off
OEM Lock: Off
RP SWREV: B:4 K:3 S:3
Any ideas what I could do?
Thanks.
Try Flash Same Firmware Reigon You have own in prev Version
MA7MOD_GSM said:
Try Flash Same Firmware Reigon You have own in prev Version
Click to expand...
Click to collapse
Thanks for your reply. I have tried this although it does not work as the boot loader version is now at V4, whereas the previous software I had was V2. I have tried flashing other Android 8 software with boot loader V4 but it goes into the “No command” state where I can’t access the recovery, only download mode is available.
hs102 said:
Thanks for your reply. I have tried this although it does not work as the boot loader version is now at V4, whereas the previous software I had was V2. I have tried flashing other Android 8 software with boot loader V4 but it goes into the “No command” state where I can’t access the recovery, only download mode is available.
Click to expand...
Click to collapse
Also a little more info. When the ODIN flash is successful it restarts to the "Install Software Update" blue screen. It reaches 32% but then begins erasing.
The following error message is also present in the recovery:
#fail to open recovery_cause (No such file or directory) #
#report 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]
dm-verity verification failed ...
E: [libfs_mgr] is_dt_compatible (): firmware info was not valid : '/ proc / device-tree / firmware / android / compatible': No such file or directory
I think you Flash worng Firmware send download mode photo
MA7MOD_GSM said:
I think you Flash worng Firmware send download mode photo
Click to expand...
Click to collapse
Firmware was fine not sure what the issue was.
Got around it by flashing latest TWRP and no verity and it loaded successfully.
Thanks
same as me. loaded twrp and no ver opt and magestic but thats all cool but all i want is official with no root or anything. why wont my damn phone boot without all the crap. this method will not allow any kind of ota. same issue when i flas pie via odin except it even worse. cant get to boot
hs102 said:
Firmware was fine not sure what the issue was.
Got around it by flashing latest TWRP and no verity and it loaded successfully.
Thanks
Click to expand...
Click to collapse
after TWRP your fone boot working ... because I have the same issue Samsung warranty center told me to replace the motherboard
hs102 said:
Also a little more info. When the ODIN flash is successful it restarts to the "Install Software Update" blue screen. It reaches 32% but then begins erasing.
The following error message is also present in the recovery:
#fail to open recovery_cause (No such file or directory) #
#report 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]
dm-verity verification failed ...
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
I also am seeing the same message in recovery mode. Also in odin mode(download mode) there is extra lines of text. Although in saying this the s8 boots and seems to function as per usual. The storage used from stock firmware is 12.4 GB... Is this normal??
All I am wanting to know is "is this normal for the exynos galaxy s8 running One UI, android 9" ?
or Did I Download a dodgy Rom?
Kdom81 said:
I also am seeing the same message in recovery mode. Also in odin mode(download mode) there is extra lines of text. Although in saying this the s8 boots and seems to function as per usual. The storage used from stock firmware is 12.4 GB... Is this normal??
All I am wanting to know is "is this normal for the exynos galaxy s8 running One UI, android 9" ?
or Did I Download a dodgy Rom?
Click to expand...
Click to collapse
Same here.
https://forum.xda-developers.com/galaxy-note-8/help/weird-message-recovery-e-libfsmgr-t3936625
Did you arrive to any conclusion?
Hey I have the same problem as well... I can't flash twrp because I have oem locked and I can't boot into my because it keeps restarting and getting stuck at some point, and the recovery is saying:
#fail to open recovery_cause (No such file or directory) #
#report 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]
dm-verity verification failed ...
E: [libfs_mgr] is_dt_compatible (): firmware info was not valid : '/ proc / device-tree / firmware / android / compatible': No such file or directory
How can I fix this?
Is there any update on this? I have the same issue as post #11 on a Samsung A8 sm-a530w.
Any help would be much appreciated.
I've got the same issue on a G950F.
I bought new (sealed, G950FXXU5DSFB), and tried to flash combination file G950FXXU5ASF1 . This did not work. (no boot).
So I flashed what I thought was stock rom matching CSC.
(AP_G950FXXU5DSFB_CL16290088_QB24491245_REV00_user_low_ship_meta_OS9.tar )
The phone boots and operates fine, except for the same message you guys are getting in recovery, as well as a message about no OTA updates.
---------- Post added at 05:54 PM ---------- Previous post was at 05:54 PM ----------
I've got the same issue on a G950F.
I bought new (sealed, G950FXXU5DSFB), and tried to flash combination file G950FXXU5ASF1 . This did not work. (no boot).
So I flashed what I thought was stock rom matching CSC.
(AP_G950FXXU5DSFB_CL16290088_QB24491245_REV00_user_low_ship_meta_OS9.tar )
The phone boots and operates fine, except for the same message you guys are getting in recovery, as well as a message about no OTA updates.
Any news about this? for me I bought used Galaxy Note 8 it was Korean N950N Converted to N950FD, I wanted to Install TWRP and ROOT but I kept getting Failed to Mount Preload error in TWRP and read smwhere its because of messed up partition so not knowing what official firmware it came with I flashed the carrier firmware which phone's IMEI info got me also it was closest to old converted FD baseband now I bypassed this nonsense via twrp but there is not even proper root to install any other custom ROM help me solve this or kindly help me find solution to Failed to mount /preload in twrp
techyrock said:
Any news about this? for me I bought used Galaxy Note 8 it was Korean N950N Converted to N950FD, I wanted to Install TWRP and ROOT but I kept getting Failed to Mount Preload error in TWRP and read smwhere its because of messed up partition so not knowing what official firmware it came with I flashed the carrier firmware which phone's IMEI info got me also it was closest to old converted FD baseband now I bypassed this nonsense via twrp but there is not even proper root to install any other custom ROM help me solve this or kindly help me find solution to Failed to mount /preload in twrp
Click to expand...
Click to collapse
Same problem but my phone s8 g950n korean, Failed to mount /preload, heres what i did to solve my problem:
- MOUNT everything in TWRP Without SDCard
- WIPE everything but NOT SDCard
- FORMAT DATA
- FACTORY RESET
- Reboot Recovery
after that no more Failed to mount /preload in twrp
- Flash Custom ROM
- Rooted my device by Flashing Magisk v20.4
nmx87 said:
Same problem but my phone s8 g950n korean, Failed to mount /preload, heres what i did to solve my problem:
- MOUNT everything in TWRP Without SDCard
- WIPE everything but NOT SDCard
- FORMAT DATA
- FACTORY RESET
- Reboot Recovery
after that no more Failed to mount /preload in twrp
- Flash Custom ROM
- Rooted my device by Flashing Magisk v20.4
Click to expand...
Click to collapse
There was some very simple fix for this mate I don't recall what worked for me, ever since I have change several phones I am on S10 5G right now, so It was just once a faced it and now I dont even remember lol what was it that fixed it for me, I think maybe different TWRP or I flashed Stock Rom the full rom with CSC and everything, just remember don't touch the partitions it was a simple fix of some sorts
hs102 said:
Also a little more info. When the ODIN flash is successful it restarts to the "Install Software Update" blue screen. It reaches 32% but then begins erasing.
The following error message is also present in the recovery:
#fail to open recovery_cause (No such file or directory) #
#report 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]
dm-verity verification failed ...
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
Hello Everyone!
I have the same problem with Galaxy Note 8 / SM-N950F
Is there a solution for this??
Please need help, please please.
Thank you

Samsung Tab E SM-T377P Sprint, Factory Reset

Hi, i am very new to the whole rooting process, so please forgive me of any ignorance.
i have a Samsung Tab E model is SM-T377P and it has Sprint service, my tablet got infected by a virus and its blocking me from doing a wipe data / factory reset.
so if i try to select the option wipe data / factory reset the virus gives me a message its not allowed and reboots the device, now i tried loading the firmware T377PVPU3CQI4_T377PSPT3CQI4_SPR\T377PVPU3CQI4_T377PSPT3CQI4_T377PVPU3CQI4_HOME.tar.md5 with Odin3 and it passed, but still got no luck to reset, so i tried with Nand Erase, but unfortunately this time i can no longer boot into android, it stays stuck at the sprint logo, i can still go to download mode, but i can no longer get this machine working, if i restart the tablet it stays stuck at the sprint logo.
another thing to note, i can also no longer see the device in my computer, only Odin3 is detecting it, even Samsung Kies is not detecting it anymore.
could anyone help me to get this recovered to a full factory reset?
here is some details of my screen in recovery mode.
samsung/gtesqltespr/gtesqltespr
7.1.1/NMF26X/T377PVPU3CQI4
user/release-keys
Use volume uo/down and power.
___________________________________________________
reboot system now (doesnt work, it gets stuck at the logo)
Reboot to bootloader
apply update from ADR
Apply update from SD card
Wipe data/factory reset (doesnt work, virus is blocking it)
Wipe cache partition
Mount /system
View recovery logs
Run graphics test
Power off
___________________________________________________
No Support SINGLE-SKU
Supported API: 3
E: ensure_path_unmounted failed to unmount /efs (Device or resource busy)
# MANUAL MODE v1.0.0#
-- Appling Multi-CSC...
Applied the CSC-code : SPR
Successfully applied multi-CSC
successfully verify for dmverity hash tree
E:failed to open /dev/block/bootdevice/by-name/misc: No such file or directory
****************************************************
here is my screen in download mode.
ODIN MODE
PRODUCT NAME: SM-T377P
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FAP LOCK: ON
WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, H1, R1, A3, P1
SECURE DOWNLOAD : ENABLE
auto9999 said:
Hi, i am very new to the whole rooting process, so please forgive me of any ignorance.
i have a Samsung Tab E model is SM-T377P and it has Sprint service, my tablet got infected by a virus and its blocking me from doing a wipe data / factory reset.
so if i try to select the option wipe data / factory reset the virus gives me a message its not allowed and reboots the device, now i tried loading the firmware T377PVPU3CQI4_T377PSPT3CQI4_SPR\T377PVPU3CQI4_T377PSPT3CQI4_T377PVPU3CQI4_HOME.tar.md5 with Odin3 and it passed, but still got no luck to reset, so i tried with Nand Erase, but unfortunately this time i can no longer boot into android, it stays stuck at the sprint logo, i can still go to download mode, but i can no longer get this machine working, if i restart the tablet it stays stuck at the sprint logo.
another thing to note, i can also no longer see the device in my computer, only Odin3 is detecting it, even Samsung Kies is not detecting it anymore.
could anyone help me to get this recovered to a full factory reset?
here is some details of my screen in recovery mode.
samsung/gtesqltespr/gtesqltespr
7.1.1/NMF26X/T377PVPU3CQI4
user/release-keys
Use volume uo/down and power.
___________________________________________________
reboot system now (doesnt work, it gets stuck at the logo)
Reboot to bootloader
apply update from ADR
Apply update from SD card
Wipe data/factory reset (doesnt work, virus is blocking it)
Wipe cache partition
Mount /system
View recovery logs
Run graphics test
Power off
___________________________________________________
No Support SINGLE-SKU
Supported API: 3
E: ensure_path_unmounted failed to unmount /efs (Device or resource busy)
# MANUAL MODE v1.0.0#
-- Appling Multi-CSC...
Applied the CSC-code : SPR
Successfully applied multi-CSC
successfully verify for dmverity hash tree
E:failed to open /dev/block/bootdevice/by-name/misc: No such file or directory
****************************************************
here is my screen in download mode.
ODIN MODE
PRODUCT NAME: SM-T377P
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FAP LOCK: ON
WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, H1, R1, A3, P1
SECURE DOWNLOAD : ENABLE
Click to expand...
Click to collapse
Are you saying in recovery mode you cannot wipe data/reset?
I've never heard of any virus being able to do this? Are you sure the device isn't MDM locked?
Also note that it can take anything up to 10-15 minutes for Android to load after a full wipe and fresh install.
ashyx said:
Are you saying in recovery mode you cannot wipe data/reset?
I've never heard of any virus being able to do this? Are you sure the device isn't MDM locked?
Also note that it can take anything up to 10-15 minutes for Android to load after a full wipe and fresh install.
Click to expand...
Click to collapse
yes, i cannot wipe data in recovery mode.
yes, you are right its MDM locked, but how can i get around that?
after fresh install i left it all night and it stayed at the sprint logo, nothing happened.
auto9999 said:
yes, i cannot wipe data in recovery mode.
yes, you are right its MDM locked, but how can i get around that?
after fresh install i left it all night and it stayed at the sprint logo, nothing happened.
Click to expand...
Click to collapse
That's the issue MDM. Who installed the MDM software?
Unfortunately now you've used Nand erase it makes it more difficult to bypass.
Your best bet is attempting to install the combination firmware and then factory resetting.
https://www.mediafire.com/file/29r6...51_T377PVPU3AQI1_SPTFAC_BoxWares.tar.zip/file
There is also the repair firmware which will wipe the device.
https://www.full-repair-firmware.com/2017/11/repair-firmware-t377p.html?m=1
Factory resetting is the key to removing it.

Categories

Resources