I've been using CM11 nightly on my i9500 and probably due to a lot of **** I'd done to this phone recently it has become quite unstable so I decided to wipe everything and do a clean installation when I remembered there's a way to enlarge internal storage up to 11.8G by flashing PIT, BL, AP, CP, CSC from I9500ZCUCMG1.
And I tried and it failed. So I only flashed PIT. Then I tried to flash BL and I see "SW Rev. Invalid magic string." on my phone. I googled it and it seems to be that Odin doesn't allow flashing an older version of bootloader. So I tried to flash I9500ZCUGNH4 but still fails with messages like "sboot.bin", "NAND write start fail".
Then I tried to flash a regular PIT provided here: http://forum.xda-developers.com/showthread.php?t=2269941
Then I tried to flash I9500ZCUGNH4 again, and this time it works. However when the device try to boot, it stuck at logo. I tried to go into recovery and it says:
E:failed to mount /data (invalid argument)
can't mount '/data'(Invalid argument)
E:failed to mount /data (invalid argument)
can't mount '/data'(Invalid argument)
Now I ran out of ideas and came here for help. Help plz. Thx in advance. :crying:
Almost forgot, I did a FULL 14.6G backup (probably all partitions) using method from this thread: http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
Is there any way to restore it now?
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
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:
SM-G530t FRP LOCK - Stuck at Galaxy Splash screen
Hi All, Im really stuck here. I have ODIN installed on my phone and have tried to install every ROM and image out there and am having trouble with the FRP . I need to unlock it to install a stock rom image ... i have tried the kies method, the smart switch method and they all run fine, but my e: partition is hosed
tried OF8_full.tar.md5
result to android system recovery <3e>
lmy47x.g530tuvu1a0f8
reboot system now
apply update from adb
" from external storage
" from cache
wipe/factory reset
wipe cache partition
reboot to boot loader
power down
recovery logs
--------------------------------------------------------------------
E: failed to mount /efs (invalid argument)
e: failed to mount /efs (invalid argument)
e: failed setting up dirty target
dm-verity failed...
e: failed to mount /system
PLEASE HELP WITH THE FRP LOCK WITHOUT BUYING A BOX
this is seriously affecting my business and cutting into my playing Destiny time!!
thanks in advance Mike
Help! My phone is now stucked on a boot logo. I tried rooting and flashing via odin on Oreo, after then, it stucks on boot loop, on which I know how to fix, going back to stock rom works, but then signal is gone (boot loop wasn't expected, didn't managed to see bandbased version) I then, flashed this: https://forum.xda-developers.com/showthread.php?t=2420881 through odin via AP, which is a wrong method on which I know I am stupid enough, right after then, OS won't boot up but stuck on boot logo, also tried using TWRP and Official Lineage OS 14.1 and the same thing happened, it starts to boot up, it rebooted after a few mins, then it goes back to TWRP.
HELP, I think the wrong method of flashing of this: https://forum.xda-developers.com/showthread.php?t=2420881 file is the mistake, idk what did I messed up with it, it was supposed to be used for EFS restore app not flash through Odin, what should I do? Any OS just stucks on boot logo but download menu and recovery mode (official/twrp) is still there, also the phone is still viable to be flashed.. Please help.. I just got this phone not even 24 hours ago.. Lol, I know stupid me, that I didn't checked the file carefully, I learnt my lesson, criticize me or anything.. But please, help if you can.
I had not known that the Marshmallow, Nougat and Oreo was pretty harder to do things on, I'm quite new with this new OS release, I was pretty confident because I was doing this all over the years (I only know step by step, not really in-depth information). Way back, odin only requires AP, now it requires 4 columns on which I cannot reflash without unchecking the Bootloader.
P.S. Before boot loop starts to happen I tried rooting on Oreo, downloaded my own country region openline version(I am openline, yes) and also tried Lineage OS 14.1, Now, I am trying to download Russia(not my country) Stock Rom Oreo, it might be the case that it doesn't allow me to flash bootloader as this was the downgrade, and I skipped right through it. But I am worrying about the wrong flash file and after the download finishes, the same thing happens and I won't be able to get passed out of boot
EDIT: I've did everything and ODIN works for the flashing the whole columns including bootloader with russian full stock ROM, but its still stuck on boot logo, EFS not detected on recovery. I'm losing hope, this is not recoverable yeah?
Here's the error code on recovery mode:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [Unknown]#
No Suppport SINGLE-SKU
E:Failed to mount /efs (Invalid argument)
File-Based OTA
E:Failed to mount /efs (Invalid argument)
Supported API: 3
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
dm-verify verification failed...
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
... and so on.
E:failed to clear BCB message: failed to find /misc partition
i have this problem too