Rooted with ODIN. The phone worked fine for weeks and then I received this message trying to charge it one day. I get "FAIL! (auth), "FAIL! (Size)," or "FAIL! (Erase)" anytime I try to flash -- whatever I try to flash. I am using ODIN3 3.10.7.
Kies 3 does not recognized this device.
Smart Switch does not recognize this device.
ADB disabled
External Storage disabled.
Using a PIT file and T Flash, it starts to work, but ultimately fails.
Any ideas? What information should I provide?
Flashed a new image, but it won't load. Phone is stuck on the first screen.
Found one to flash through odin, but it won't load on reboot. Kies is attempting to reimage, but last try it also would no reboot. Fails to load image.
zerowrst said:
Rooted with ODIN. The phone worked fine for weeks and then I received this message trying to charge it one day. I get "FAIL! (auth), "FAIL! (Size)," or "FAIL! (Erase)" anytime I try to flash -- whatever I try to flash. I am using ODIN3 3.10.7.
Kies 3 does not recognized this device.
Smart Switch does not recognize this device.
ADB disabled
External Storage disabled.
Using a PIT file and T Flash, it starts to work, but ultimately fails.
Any ideas? What information should I provide?
Click to expand...
Click to collapse
Finally worked. Tried to flash tar from sammobile 10 times. Finally took.
Hi Guys,
today I wanted to flash the latest Stock ROM for my device via ODIN. I've done this many times before and (thought) I knew what I was doing. It is my third Phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly I wasn't aware that this particular device was locked.
After downloading the international firmware I tried to install it and ODIN got stuck while writing the system.img. After that my phone did not boot up (of course). After that I downloaded and tried to isntall the firmware of the carrier, but I had the exact same issue. When I turn my device on I get to an error screen which tells me to execute an "emergency recovery" via the Samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
FRP hinders me to install a custom recovery and the stock one does not allow any isntallations via ADB or SD card.
My qustion is: Does anyone know how I can install a rom from here?
I know that I had to have made some changes prior to the flashing, but as I said I was not aware and an Idiot for not double checking.
Since it is not bricked yet I suppose there must be an answer but I can't find anything.
Thanks in advance
Edit:
After only installing the stock bootloader, I am autmaticly entering it when I boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"
Fix
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
fabivons said:
hi guys,
today i wanted to flash the latest stock rom for my device via odin. I've done this many times before and (thought) i knew what i was doing. It is my third phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly i wasn't aware that this particular device was locked.
After downloading the international firmware i tried to install it and odin got stuck while writing the system.img. After that my phone did not boot up (of course). After that i downloaded and tried to isntall the firmware of the carrier, but i had the exact same issue. When i turn my device on i get to an error screen which tells me to execute an "emergency recovery" via the samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
Frp hinders me to install a custom recovery and the stock one does not allow any isntallations via adb or sd card.
My qustion is: Does anyone know how i can install a rom from here?
I know that i had to have made some changes prior to the flashing, but as i said i was not aware and an idiot for not double checking.
Since it is not bricked yet i suppose there must be an answer but i can't find anything.
Thanks in advance
edit:
After only installing the stock bootloader, i am autmaticly entering it when i boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"
Click to expand...
Click to collapse
have u solved your problem ? This problem i am facing on the s7edge nougat ? Plz help ?
Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might be worth a try!
Good luck!
Fabivons said:
Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might me worth a try!
Good luck!
Click to expand...
Click to collapse
y i have done that and the device boots up but some applications force close and when i insert the memory card , the phone gets restarted everytime
Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Tell us in detail now.
SjDU said:
Tell us in detail now.
Click to expand...
Click to collapse
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?
suhaibahmad said:
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?
Click to expand...
Click to collapse
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.
Fabivons said:
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.
Click to expand...
Click to collapse
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally
suhaibahmad said:
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally
Click to expand...
Click to collapse
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.
Fabivons said:
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.
Click to expand...
Click to collapse
thats your kindness , yes i have performed the factory reset several times from recovery , but when i trying to reset it from settings , it goes after restart to recovery with dm-verity error , then i wipe and factory reset from there
Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model
SjDU said:
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model
Click to expand...
Click to collapse
Well FRP has to be turned off (the button in the menu is called "OEM unlock, the button has to be set to on which deactivates FRP). You don't mention using a PIT file - did you use one?
Summary: My tablet is soft-brick now. Can only access to Download (ODIN) mode. I have tried 2,3 different firmwares, tried 3 versions of ODIN. But it doesn't work.
Here is the story:
I bought this tablet from bestbuy (USA)
I only wanted to root my tab A 7.0 SM-T280.
I enabled the OEN unlock from the developer mode.
Then I tried to flash the TWRP by the tutorial from this topic by @ashyx :
To install TWRP:
1. Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
2. Load the respective file below into the AP slot and hit start.
3. After flashing when ODIN says PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
TWRP_3.0.2-1_SM-T280_261016
Click to expand...
Click to collapse
After flashing, on the download mode it showed: "SECURE CHECK FAIL: (RECOVERY)", then I reboot into recovery mode to access the TWRP but it said: "RECOVERY IS NOT SEANDROID FORCEFUL (although in ashyx topic said the SECURE FAIL is fine).
I still was able to reboot into the system this time.
And then I thought I should try another way. And then I came up with the TINKER ROM.
I tried to flash the Rom (v5) but somehow ODIN said FAIL.
I COULD NOT access the system since then.
Bu @zenful 's advices, I tried some different stock firmwares and different versions of ODIN just to get back to normal, but it never works.
Every time I flash, it always has the same problem:
- First try, ODIN fails at:
sboot.img
sboot2.img
complete (write) failed... (I don't remember though)
And in the download mode screen (from the phone) said:
SECURE CHECK FAIL (SBOOT)
SECURE CHECK FAIL (SBOOT2)
- Second try, ODIN fails at:
boot.img
system.img
Complete (write) fail...
And in the screen said:
SECURE CHECK FAIL (BOOT)
SECURE CHECK FAIL (RECOVERY)
I also tried emergency recovery mode in smart switch but it didn't solved the problem. One good thing (after I entered the tablet model and serial number) is that it showed "PHONE: QA4 CSC: PH3 (XAR)"
______________
I'm pretty sure that the problem doesn't come from fw nor from ODIN since I downloaded the fws from sammobile and updato and downloaded ODIN from xda (the latest version from samsungodin.com)
I'm seriously need a help right now. I just wanna have a rooted tablet so I can play game with my ps4 controller.
I have experienced with these flashing business. I rooted my galaxy s2, HTC desire c, HTC evo, etc. and so on, but have never done rooting in the last 1 year. I can attach some snapshots if you guys request
ngvhoang96 said:
Summary: My tablet is soft-brick now. Can only access to Download (ODIN) mode. I have tried 2,3 different firmwares, tried 3 versions of ODIN. But it doesn't work.
Here is the story:
I bought this tablet from bestbuy (USA)
I only wanted to root my tab A 7.0 SM-T280.
I enabled the OEN unlock from the developer mode.
Then I tried to flash the TWRP by the tutorial from this topic by @ashyx :
After flashing, on the download mode it showed: "SECURE CHECK FAIL: (RECOVERY)", then I reboot into recovery mode to access the TWRP but it said: "RECOVERY IS NOT SEANDROID FORCEFUL (although in ashyx topic said the SECURE FAIL is fine).
I still was able to reboot into the system this time.
And then I thought I should try another way. And then I came up with the TINKER ROM.
I tried to flash the Rom (v5) but somehow ODIN said FAIL.
I COULD NOT access the system since then.
Bu @zenful 's advices, I tried some different stock firmwares and different versions of ODIN just to get back to normal, but it never works.
Every time I flash, it always has the same problem:
- First try, ODIN fails at:
sboot.img
sboot2.img
complete (write) failed... (I don't remember though)
And in the download mode screen (from the phone) said:
SECURE CHECK FAIL (SBOOT)
SECURE CHECK FAIL (SBOOT2)
- Second try, ODIN fails at:
boot.img
system.img
Complete (write) fail...
And in the screen said:
SECURE CHECK FAIL (BOOT)
SECURE CHECK FAIL (RECOVERY)
I also tried emergency recovery mode in smart switch but it didn't solved the problem. One good thing (after I entered the tablet model and serial number) is that it showed "PHONE: QA4 CSC: PH3 (XAR)"
______________
I'm pretty sure that the problem doesn't come from fw nor from ODIN since I downloaded the fws from sammobile and updato and downloaded ODIN from xda (the latest version from samsungodin.com)
I'm seriously need a help right now. I just wanna have a rooted tablet so I can play game with my ps4 controller.
I have experienced with these flashing business. I rooted my galaxy s2, HTC desire c, HTC evo, etc. and so on, but have never done rooting in the last 1 year. I can attach some snapshots if you guys request
Click to expand...
Click to collapse
Try this: download your desire firmware via samfirm (BL+AP+CP+CSC when extracted) plus you need a pit file for your model with the same region as firmware and then flash (with 4 firmware files incl pit) via odin autoreboot+repartition+nand erase+f.reset time. At least you will get working stock tablet. It worked on my note 4 soft bricked.
Stixas said:
Try this: download your desire firmware via samfirm (BL+AP+CP+CSC when extracted) plus you need a pit file for your model with the same region as firmware and then flash (with 4 firmware files incl pit) via odin autoreboot+repartition+nand erase+f.reset time. At least you will get working stock tablet. It worked on my note 4 soft bricked.
Click to expand...
Click to collapse
Last time I tried download fw by using samfirm was last week and it didnt work. Can you test yours again?
And whre can I found the pit file? I dont think there is one in the internet right now.
So, I have here a great old Note 4.
It has the generic mmc errors that cause it issues when booting and sleeping so I decided to give it a new rom. I bumped it into developer options, enabled usb debugging and fastboot and turned it off. I opened up odin, found the right twrp file to flash as well as a stock rom. I loaded it up and fired. The issue then was that the PIT partition had issues. Pit partition failed on odin's side, and flash read failure as well as a pit error of some sort on the phone's side. So I did my homework. I then tried to flash a new .pit file, I made sure the boxes were filled out correctly, had the right pit file as well as a correct stock rom, and the right drivers. It failed again with exactly the same errors. I don't know how you can manage saying that you can't flash the file your trying to fix but whatever. So I did more research and continued to change the usb cable to the original one that came with the phone, change the usb port, change versions of odin, use administrator privileges, find another .pit file, and change the pc. None of these worked, they all gave the same errors no matter what I did. So I moved on to see what else I could do, there was only one more issue though, the phone wouldn't boot up to an OS, if I tried to boot up normally it would boot into recovery, and if I booted into recovery it would boot into download mode with a message saying that the mme error caused it to. SO I couldn't do anything like flashfire or rom manager nor could I do something like root the device! So I did more homework, I turned to adb, because I saw something about an alternative to odin. Unfortunately, the phone has to boot up so you can connect it properly before you boot into download mode. So I did more homework and can't get anywhere, I am completely lost as to what to do because I can't flash odin or adb and sd card can only flash .zip files. I have no idea where to find a .zip for cwm or twrp that will work for my phone and the 2 files that I thought would work only gave me errors. I definitely am drowning in error messages and hope someone who knows what in the world is going on can help me get out of this mess.
Sincerely,
TiffPiff
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.