I have a stock 5.0.1 model N910F and tried updating to 5.1.1 using Odin, however I got an "invalid ext4 image" error. When I took the battery out and tried rebooting it, it just showed a screen telling me to use emergency recovery mode in Kies however when trying to do that my device wouldn't show up in the menu. I then tried extracting the recovery file from the 5.1.1 tar file and flashing that but again it wouldn't work. I can still go into download mode, but my phone just won't boot. Now I'm trying to download another 5.1.1 file for my country from sammobile and seeing if that will work, but is there anything else I can do?
Edit: Nevermind, flash this and it worked.
Related
My S3 Neo I9300I ran stock 4.4.4 KitKat with TWRP 2.7.1 and I tried to install a custom Lollipop rom which did not work so I had to reflash the stock firmware.
After reflashing the firmware with Odin, everything was fine except that the Wifi option was greyed out and unresponsive so I coudn't connect to Wifi. I tried many of the options specified on threads related to this particular issue but to no avail.
Second time I tried to reflash the firmware with Odin, Odin showed "PASS" after which I unplugged the phone and found out that it didn't boot at all, even into Download Mode. No key combos etc worked.
After some Googling, I found out that writing a debrick file to an SD card and inserting it into the phone could get the phone into a bootloop while booting normally and into Download Mode while holding VOL DOWN+POWER+HOME. Without the SD card though, the phone was completely unusable as above.
I then tried flashing the firmware and TWRP again with Odin but still the phone won't boot at all, and inserting the debrick SD card could only get it into Download mode.
Would flashing a firmware from a different region help? Or have I ruined the bootloader? Any help would be greatly appreciated...
malinmva96 said:
My S3 Neo I9300I ran stock 4.4.4 KitKat with TWRP 2.7.1 and I tried to install a custom Lollipop rom which did not work so I had to reflash the stock firmware.
After reflashing the firmware with Odin, everything was fine except that the Wifi option was greyed out and unresponsive so I coudn't connect to Wifi. I tried many of the options specified on threads related to this particular issue but to no avail.
Second time I tried to reflash the firmware with Odin, Odin showed "PASS" after which I unplugged the phone and found out that it didn't boot at all, even into Download Mode. No key combos etc worked.
After some Googling, I found out that writing a debrick file to an SD card and inserting it into the phone could get the phone into a bootloop while booting normally and into Download Mode while holding VOL DOWN+POWER+HOME. Without the SD card though, the phone was completely unusable as above.
I then tried flashing the firmware and TWRP again with Odin but still the phone won't boot at all, and inserting the debrick SD card could only get it into Download mode.
Would flashing a firmware from a different region help? Or have I ruined the bootloader? Any help would be greatly appreciated...
Click to expand...
Click to collapse
did you use the india firmware? Yes try different regions.
YES!! The firmware I tried to flash earlier was the Sri Lankan firmware but I flashed another version from Trinidad and Tobago and now everything's back to normal Thanks a lot!!
Today i was trying to install the Android Marshmallow 6.0.1 on my Galaxy S5 Snapdragon via Odin, i downloaded the firmware from Sammobile, i verified that the phone model was exactly the same as named on the firmware, i place the .md5 file in the AP slot and everything was ready to go! (The phone was already plugged and in Bootloader mode, and drivers were up to date) then when finishing the flash Odin FAILS to complete the flash and the phone is left with nothing than the Download mode, i panic and try to access recovery mode but realize that there´s no recovery....I proceed to install the recovery.tar into my phone and it works, i start the phone and Samsung logo comes up, finally it loads and does al the process after you flash a Samsung phone.
Everything works just fine!...except for one thing, THERE´S NO RECOVERY!!!. The phone works perfectly but when i try to enter recovery mode, it sends me to Odin mode as it displays a message saying that failed to boot into recovery.
Please help me i don´t know what to do.
Thanks!
Just flash a custom recovery like twrp or cwm
Already did...same problem, recovery won't boot
adavicco said:
Already did...same problem, recovery won't boot
Click to expand...
Click to collapse
You need to flash a pit file to complete the install correctly.
Good night guys, so there's my problem:
I was on DN 0.6.1 custom ROM, TWRP 3.0.2.0 and rooted. Today, i wanted to go back to stock ROM, so, I downloaded the stock firmware throught sammobile, and tried to install it throught ODIN 3.11, but it's stopped at system.img, and remained stuck in it for a long time. so i decided to restart the phone..
Then it's showed the follow message:
firmware upgrade encountered an issue note 4. Please select recovery mode on kies and try again.
So, i tried to re-flash throught ODIN, but stucked at system.img again, after it, I downloaded KIES and tried restore it, but it's stopped at 2%.
I wasn't abble to go to recovery mode, only download mode, so, i extracted the ROM file, and flashed only the boot.img through ODIN. Now it's boot to recovery...
I wiped data/cache, but the following error showed up:
E: Failed to mount system (invalid argument).
and now i can't find a solution for it.. tried to do amost anything that i could find on the internet, but none solved my problem...
I'm wanting to flash PIT + CSC + PDA file, using the repartition option on ODIN, but i'm afraid that may brick my phone for ever...
I'm following this tutorial by now: http://forum.xda-developers.com/not...te-4-pit-files-repartiton-f-g-c-t-w8-t3282641
And i need this CSC file, because my phone is the C version, could someone give me link to download it ? couldn't find in any place.
ANd there's someone who could help me ? i'm very concerned about it because i don't have money to buy another phone at the moment...
Thanks, and yes, already looked at XDA for a answer but couldn't fine any.
THANK YOU :good:
Anyone ?
Hello guys,
I need extremely technical help as no longer know what to do.
I have a Galaxy S7 Edge device, which installed the rom BobCat and everything went well until then.
Later I decided to install another rom to test KingRom that left me unsatisfied, because I thought it had some bugs. Had the TWRP 3.0.0 recovery and decided to upgrade to 3.0.2, everything went well.
At one point I do not remember when or how if was when install back, downgrade to TWRP3.0.0, I do not remember if it was via Odin or TWRP, it happens that the installation stopped halfway. Then unplug the device, restarted in recovery mode and got the following message "E: falied to mount EFS (Invalid Argumen)", I could not restart the device (Boot Loop, and stucked at Samsung Logo) except in Recovery Mode, which also made to stay without IMEI number and Serial Number.
I googled until I came to this tutorial:
http://forum.xda-developers.com/s7-e...ssues-t3379516
I followed all the steps explained, I back up EFS_backup and RADIO_bakcup partitions.
Installed FACTORY BINARY G935, everything went well. After restarted, already had the correct IMEI number but still did not present the S / N.
After all that, i tried to install Stock Firmware via Odin, from here started the problems that could not solve.
In the first attempt Odin stucked in "System" (also used the PIT file with the same CSC ... .i do not know if I was right using PIT?). Restarted the device forcibly, entered the stock Recovery, did a complete wipe and always get this message "E: falied to mount System (Invalid argument), I returned to install Factory Binary, then reboot in Recovery and the same message no longer appeared.
Again I try to install the Stock Firmware and Odin always stucks in System, or NAND writing, or Partition, etc. I've tried various Stock Firmware, with and without PIT files, always without success.
Only Factory Binary that successfully installs. The TWRP via Odin also but when device restarts to enter Recovery Mode always get the message at the top of the display:
"Recovery image signature check Fail"
"Reboot to avoid Warranty bit set."
1. Does the partitions are in good shape? how can I check it?
2- I did good or bad using PIT file?
3- Does the problem is running Windows XP through a Virtual Machine?
4 What else can I do?
In all actions used and am using a Macbook 4.1, OsX Lion 10.7.5, Odin 3.11 Windows XP Professional 32bit through Oracle VM VirtualBox 3.4.38
Device:
Galaxy S7 Edge (SM-G935F) CSC = SWC SwissCom
1st Original Firmware: (I guess was 1?) G935FXXS1APG5_G935FVFG1APF3_SWC
Need help Please
Thank you so very much!
Backstory:
Received the message "Custom binary blocked by FRP lock" when restarting my phone. I had a custom ROM installed so this was probably why, but I had flashed no-verity-opt-encrypt previously so I don't know why I randomly got this message.
Tried to flash the latest Android 8.0.0 stock firmware from sammobile, successfully flashed through Odin but when the phone boots it keeps looping into recovery, followed by "No command".
When I try to access the recovery settings by pressing power+up it comes with:
fail to open recovery_cause(No such file or directory)#
Reboot Recovery Cause is [UNKNOWN]# No Support SINGLE-SKU
Along with a bunch of lines saying failed to mount /system and dm-verity failed.
I've tried flashing many different stock ROMs but only the factory binary combination ROM is able to boot up. Therefore, I cannot turn off FRP lock. I am struggling to find out why, even though Odin successfully flashed the whole stock BL, AP, CP and CSC, the recovery cannot be opened.
Any ideas would be greatly appreciated.
Edit: Managed to fix it through a YouTube video by Mr.Lee
Try downgrading to nougat or marshmallow. That should remove FRP.
Sent from my SM-G935FD using Tapatalk
I've tried but I cannot find any marshmallow/nougat version which does not result in a SW REV CHECK FAIL error, my kernel only accepts Oreo or higher it seems.