Related
I'm trying to update to 5.1.1 from 5.0.2 but I'm unable to get the pit file in Odin. Is there any place to download it? I have looked on Google but had no luck.
delete the hidden Img from the firmware
Alex-V said:
delete the hidden Img from the firmware
Click to expand...
Click to collapse
Will that method still work for flashing using Jodin?
mackay508 said:
Will that method still work for flashing using Jodin?
Click to expand...
Click to collapse
described it many times..here's one of it
http://forum.xda-developers.com/showthread.php?t=3141455
for g925f 64go i used ZEROLTE_EUR_OPEN_HIDDEN100M.pit = no more hidden error
Hey guys
I was rooting Galaxy Grand Prime SM-G531H with CF-AutoRoot while forgetting to enable USB Debugging, and to unlock FRP (ik thats stupid)
im just assuming that FRP= Factory Reset Protection.. maybe? anyway doesnt matter much ...
while rooting, FRP blocked the custom recovery > bricked
FRP blocks everything from odin
To fix with Kies, it wants to erase all data while *I cant lose them*
so i would appreciate if someone can upload the original boot.img and recovery.img of SM-G531H
I can't find them anywhere on the internet unlike other devices like S series
Info: tried installing a pre rooted official firmware but FRP blocked it, and can't downlaod the original non-rooted firmware becasue of very bad download sites (disconnect all the time, slow, not resumable downloads)
.
U can extract it from your stock rom that u used to flash with odin.
Here you go!
Here are my latest stock firmware files, you can download boot and recovery. Hope I helped you if you haven't solved the problem already! :good:
https://my.pcloud.com/publink/show?code=kZuzgPZx8konqA1xSjLBaDBEFeshHIss7pV
d1v1n3 said:
Here are my latest stock firmware files, you can download boot and recovery. Hope I helped you if you haven't solved the problem already! :good:
https://my.pcloud.com/publink/show?code=kZuzgPZx8konqA1xSjLBaDBEFeshHIss7pV
Click to expand...
Click to collapse
Thanks mate they do help :like:
is this okay to use it if mine sm-g530h/ds ?
GaviPras said:
is this okay to use it if mine sm-g530h/ds ?
Click to expand...
Click to collapse
no it cant be used for u'rs but if u need i can provide
.
d1v1n3 said:
no it cant be used for u'rs but if u need i can provide
Click to expand...
Click to collapse
How can I use boot.img and recovery.img . where does it go in odin?
registre said:
How can I use boot.img and recovery.img . where does it go in odin?
Click to expand...
Click to collapse
1. First u need to install 7zip on u'r PC
2. select boot.img and recovery.img then right click on them and choose add to archive
3. choose tar in the format instead of zip and click ok
4. now u have a .tar file that contains boot and recovery so place that file in the AP inside odin
5. flash the phone and that's it, u r good to go
registre said:
How can I use boot.img and recovery.img . where does it go in odin?
Click to expand...
Click to collapse
Sadly, i already went to Samsung Service centre. They said to me to replace the emmc because it can't be flashed anymore
my assume usb debugging not checked and also FRP
now it only used as a key chain :crying:
I see the frp problem in my gran prime
I flash the original rom with odin
And problem is solved
Flash official firmware it will fix ur problem
Please I need help it says the link is empty or deleted.
Send me the right link please....
link die
d1v1n3 said:
Here are my latest stock firmware files, you can download boot and recovery. Hope I helped you if you haven't solved the problem already! :good:
Click to expand...
Click to collapse
please help me! I have the same issue. Please re-up it. thank you so much
Hi
I have a samsung S7 running on android 7.0.
After running TWRP on phone the phone is on boot loop.
I can access the phone database and did a full copy with adb but the user data it seems to be encrypted.
Is there any way to salvage my information?
TWRP doesn't ask my password so is there another way to open the image.dd that I have
maybe try to flash the same original samsung 7.0 HOME SW (which was installed before trying to root).
Home SW shouldn't erase user data, and maybe will fix this, but I don't tried it on encrypted device.
legacik said:
maybe try to flash the same original samsung 7.0 HOME SW (which was installed before trying to root).
Home SW shouldn't erase user data, and maybe will fix this, but I don't tried it on encrypted device.
Click to expand...
Click to collapse
Thanks for the quick reply!!
I have downloaded the original firmware package and as I can understand flashing home_csc file doesn't erase data at all.
Any Idea do I have to install the other packages also or just the home_CSC?
l00p3r said:
Thanks for the quick reply!!
I have downloaded the original firmware package and as I can understand flashing home_csc file doesn't erase data at all.
Any Idea do I have to install the other packages also or just the home_CSC?
Click to expand...
Click to collapse
I think on Sammobile/Samfirmware you can get full package AP+CP+CSC in one. For example "G935FXXU1DQB7_G935FUUB1DQB7_ARO" but I'm not sure if there should be the same CSC as previously installed on your phone to NOT erase all data.
I don't test it so you're flashing this on your own risk Maybe someone else can confirm this. Few years ago I had similar issue with my galaxy note3 (stucked on boot after trying to root) and this solution works for me
SOLVED
I downloaded the same stock firmware that I had on the phone before flashing with TWPR.
Extracted the zip file to c:/ odin
I edited the HOME_CSC with Cygwin and used the following commands
cd /cygdrive/c/odin
file=HOME_CSC_PHN_G935FPHN1APBD_CL7162483_QB8754029_REV00_user_low_ship.tar.md5
tar xvf "${file}" cache.img hidden.img
tar -H ustar -cf "${file%.md5}" cache.img hidden.img
md5sum -t "${file%.md5}" >> "${file%.md5}"
mv "${file%.md5}" "${file}"
After that flashed all packages with odin
BL - Bootloader
AP
CP
HOME_CSC
None of my data was erased and all worked out well
After flashing the knox indicated that my phone was hacked .. maybe full factory reset would bring it back
l00p3r said:
After flashing the knox indicated that my phone was hacked .. maybe full factory reset would bring it back
Click to expand...
Click to collapse
As soon as the knox flag is broken its gone forever. Flashing root breaks knox.
The following is a guide for repairing failed to mount efs and dm-verify fail (drk error)
We finally did it ~~~
Warning - We will not take any responsibility for your device. Follow the steps at your own risk. If your device is Knox 0, This guide would convert it into Knox 1 due to TWRP. For solutions that does not convert to knox 1 check out payed remote solutions. Everything on your device will be reset, including efs partition. You will need backup of efs.
Test on N950F binary 4 may work on other exynos models comment below if it worked for other samsung devices.
Problem Detail -
Bootloop with samsung stock firmware boot logo.
Recovery error E:Failed to mount /efs (Invalid argument) or dm-verity verification failed...
Device cannot boot into Factory binary or Stock Rom
Actions that could cause this problem -
Flashing a non-signed efs.img by odin
Corrupt flash of efs partition.
Note - Must have efs backup for device to work (very important)
Any error that cause bootloop would show in recovery required if
Files Required
Latest Odin (recommend 3.13)
Working Stock firmware and Combination file (same binary as bootloader)
PC
Winrar or 7zip etc
Solution for efs failed bootloop-
Extract Stock firmware AP file (rename .md5 to .tar)
Rename dqmdbg.img to efs.img (or smallest image must be smaller than 8000 KB). Extract Dqmdbg.img.lz4 so it’s just “Dqmdbg.img” and then rename it to efs.img and put that one in a tar. Other option is downloading a file that’s already made this way if your bootloader is binary 4, Saves you trouble of extracting / renaming: http://www.mediafire.com/file/589wucja9rk2v8f/efs.tar/file (if you download this file just move onto number 3)
Add file new efs.img into tar archive.
Flash tar as AP file in odin + download mode
Reboot download mode
Flash Combination with odin + nand erase option on Edit: suggest you to flash stock rom first and oem unlock, don't need to wait for 7 days if imei is 0000 skip combination step
Device Should boot into Factory binary
Use IME to restore imei using *#06# (or imei 0000 in stock rom) Edit: This step is not required if efs backup is restored successful
Your device should have dm-verify failed in recovery due to drk error
Continue drk bypass for dm verify error below to continue
Solution for dm-verify error (also known as drk bypass - but temporary read note)-
Extract Stock firmware AP file
Make a copy of boot.img and delete recovery.img
Note - if files is boot.img.lz4 format change name to recovery.img.lz4
Rename boot.img copy to recovery.img
Add all the files (including other files extracted) to tar.
Flash Modded AP file with BL, CP, CSC (nand erase not required)
The phone will boot into stock firmware
Note- cannot reboot, will stuck at dm-verify error again and need to flash modded AP again.
Wait 7 days to oem unlock phone or use 7 day bypass by changing dates (not always work, keep trying, don’t reboot, worked for Samsunguser932 Edit: Imei must be 0000)
Edit: oem unlock will fix drk - if not you must follow next step
Once oem unlock flash TWRP and restore efs backup Edit: if you haven't fixed imei fix now by *#06# with combination file
Flash stock firmware once again by odin (stock, not modded)
Done - phone is back to normal
If you cannot be bothered doing by yourself you can pay https://www.facebook.com/gsm.xraxxx/ to do this.
(after he used plexihub to fix phone, i believe he is using similar method. It doesn’t seem fair to post this guide as i’ll be damaging his income but it seemed also unfair to keep this as a secret. If you want to donate to me please donate to him and his team instead at https://spacial-file.com/ or paypal [email protected] Thx)
Special Thanks to -
Samsunguser932 - testing this guide you can see his post on https://forum.xda-developers.com/galaxy-note-8/help/note-8-phone-booting-efs-restore-t3830209
Ravi Kumar - for his help in giving me clues how to fix.
Resources: (where i got most my info)
https://forum.xda-developers.com/galaxy-note-8/help/unbrick-methods-t3703767
https://forum.xda-developers.com/galaxy-note-8/help/to-fix-efs-secondary-note-8-t3785600
https://forum.xda-developers.com/galaxy-note-8/help/note-8-phone-booting-efs-restore-t3830209
http://forum.gsmhosting.com/vbb/f453/samsung-s8-g955f-2426383/
Comment below for help.
Give me a thanks if you find this guide very/extremely helpful. :angel:
Share it with those in need.
edit: not all images were able to upload
update: to skip 7 day oem unlock imei must be 0000
The best method for bypassing oem unlock for 7 days.
Requirements - clean phone with stock firmware, samsung account logged in, imei 0000
Go to setting and check for manual update. This will fail/stuck and oem unlock would appear in development settings
Reserved
hello , i have samsung j737t with bad efs ,
Recovery error E:Failed to mount /efs (Invalid argument)
any help please ,i have cert in hand
maxpatri9 said:
hello , i have samsung j737t with bad efs ,
Recovery error E:Failed to mount /efs (Invalid argument)
any help please ,i have cert in hand
Click to expand...
Click to collapse
Try the above guide. This guide isn't just designed for the note 8.
from what file i need to create efs.img for s8+ g955F?
ditternation said:
from what file i need to create efs.img for s8+ g955F?
Click to expand...
Click to collapse
You do not need an efs.img to repair efs failed to mount. It is only required for the functionality of the phone (sim). This guide would work without an efs.img, it is recommended to install a custom rom after the guide. Even though this guide can allow you phone to work, but due to drk/dm-verify errors, it is currently impossible to restore the phone to the original state.
Note - you'll need to find someone that is kind enough to share a copy/backup of their efs.img g955F. Most people think it is illegal to share as the efs.img contain imei, but with cpid devices, the imei would be overridden by your current device. Most importantly you need to change the serial number in the SVC (or else you will have the same serial number as the person sharing.
plz my problem is oem lock on, frp on and drk error. i have combination file and stock can your guide work for me?
soundn said:
plz my problem is oem lock on, frp on and drk error. i have combination file and stock can your guide work for me?
Click to expand...
Click to collapse
This would only work if you're still on binary 3. Follow the steps for DM verity fix with 7.1.1 firmware. Flash stock 7.1.1 with replaced boot.img using Odin and fix frp using adb (guides online to enable adb). Wait for 7 day OEM unlock (no method to skip do not restart). Flash twrp and use twrp to flash custom ROM or DM verify fix.
Note - this method would fix function ability of the phone only if efs is not corrupted. (If you had paid someone to fix efs, this would not work). Finally the phone will become Knox 1 and normal update functions might not work. Practically makes the phone unable to resell as a working phone.
Hello. My efs partition was erased by a z3x box. Or an octopus, I do not know. I followed your instructions. The IME combination is empty. I install a modified firmware, it works but I can not enter the Samsung account (crashing), I can not check the system updates (infinite device registration). Should I wait 7 days before the OEM unlock? Will it work?
@Alarg read post 2 to skip 7 days. Infinite device registration should make OEM unlock show with samsung account logged in. OEM unlock must be first done before installing modified firmware (suggest kernel). You must have backup of efs, a backup from another phone will not work.
bluecub1st said:
@Alarg read post 2 to skip 7 days. Infinite device registration should make OEM unlock show with samsung account logged in.
Click to expand...
Click to collapse
I can't log in Samsung account (processing failure). Imei unknown, s/n 0000000000 This method does not work for me.
@Alarg Which firmware ver are you using?
Have you tried nand flash combination file and then flash firmware (before boot, hold download mode buttons so the phone won't boot to factory mode). I do not see a reason why Samsung account would not work, try another ver maybe the version you downloaded is corrupted.
bluecub1st said:
The following is a guide for repairing failed to mount efs and dm-verify fail (drk error)
We finally did it ~~~
Warning - We will not take any responsibility for your device. Follow the steps at your own risk. If your device is Knox 0, This guide would convert it into Knox 1 due to TWRP. For solutions that does not convert to knox 1 check out payed remote solutions. Everything on your device will be reset, including efs partition. You will need backup of efs.
Test on N950F binary 4 may work on other exynos models comment below if it worked for other samsung devices.
Problem Detail -
Bootloop with samsung stock firmware boot logo.
Recovery error E:Failed to mount /efs (Invalid argument) or dm-verity verification failed...
Device cannot boot into Factory binary or Stock Rom
Actions that could cause this problem -
Flashing a non-signed efs.img by odin
Corrupt flash of efs partition.
Note - Must have efs backup for device to work (very important)
Any error that cause bootloop would show in recovery required if
Files Required
Latest Odin (recommend 3.13)
Working Stock firmware and Combination file (same binary as bootloader)
PC
Winrar or 7zip etc
Solution for efs failed bootloop-
Extract Stock firmware AP file (rename .md5 to .tar)
Rename dqmdbg.img to efs.img (or smallest image must be smaller than 8000 KB). Extract Dqmdbg.img.lz4 so it’s just “Dqmdbg.img” and then rename it to efs.img and put that one in a tar. Other option is downloading a file that’s already made this way if your bootloader is binary 4, Saves you trouble of extracting / renaming: http://www.mediafire.com/file/589wucja9rk2v8f/efs.tar/file (if you download this file just move onto number 3)
Add file new efs.img into tar archive.
Flash tar as AP file in odin + download mode
Reboot download mode
Flash Combination with odin + nand erase option on Edit: suggest you to flash stock rom first and oem unlock, don't need to wait for 7 days if imei is 0000 skip combination step
Device Should boot into Factory binary
Use IME to restore imei using *#06# (or imei 0000 in stock rom) Edit: This step is not required if efs backup is restored successful
Your device should have dm-verify failed in recovery due to drk error
Continue drk bypass for dm verify error below to continue
Solution for dm-verify error (also known as drk bypass - but temporary read note)-
Extract Stock firmware AP file
Make a copy of boot.img and delete recovery.img
Note - if files is boot.img.lz4 format change name to recovery.img.lz4
Rename boot.img copy to recovery.img
Add all the files (including other files extracted) to tar.
Flash Modded AP file with BL, CP, CSC (nand erase not required)
The phone will boot into stock firmware
Note- cannot reboot, will stuck at dm-verify error again and need to flash modded AP again.
Wait 7 days to oem unlock phone or use 7 day bypass by changing dates (not always work, keep trying, don’t reboot, worked for Samsunguser932 Edit: Imei must be 0000)
Once oem unlock flash TWRP and restore efs backup Edit: if you haven't fixed imei fix now by *#06# with combination file
Flash stock firmware once again by odin (stock, not modded)
Done - phone is back to normal
If you cannot be bothered doing by yourself you can pay https://www.facebook.com/gsm.xraxxx/ to do this.
(after he used plexihub to fix phone, i believe he is using similar method. It doesn’t seem fair to post this guide as i’ll be damaging his income but it seemed also unfair to keep this as a secret. If you want to donate to me please donate to him and his team instead at https://spacial-file.com/ or paypal [email protected] Thx)
Special Thanks to -
Samsunguser932 - testing this guide you can see his post on https://forum.xda-developers.com/galaxy-note-8/help/note-8-phone-booting-efs-restore-t3830209
Ravi Kumar - for his help in giving me clues how to fix.
Resources: (where i got most my info)
https://forum.xda-developers.com/galaxy-note-8/help/unbrick-methods-t3703767
https://forum.xda-developers.com/galaxy-note-8/help/to-fix-efs-secondary-note-8-t3785600
https://forum.xda-developers.com/galaxy-note-8/help/note-8-phone-booting-efs-restore-t3830209
http://forum.gsmhosting.com/vbb/f453/samsung-s8-g955f-2426383/
Comment below for help.
Give me a thanks if you find this guide very/extremely helpful. :angel:
Share it with those in need.
edit: not all images were able to upload
update: to skip 7 day oem unlock imei must be 0000
Click to expand...
Click to collapse
thanx! for your guide but i have this problem after taking an official OTA!
DM-Verity ERRor!
any help will be greatly appreciated!
Can someone explain me what is this EFS ?? I'm flashing roms many many times and I hadn't such problems etc
klisza1993 said:
Can someone explain me what is this EFS ?? I'm flashing roms many many times and I hadn't such problems etc
Click to expand...
Click to collapse
Just Google "EFS android"
pixel989 said:
thanx! for your guide but i have this problem after taking an official OTA!
DM-Verity ERRor!
any help will be greatly appreciated!
Click to expand...
Click to collapse
Follow
Solution for dm-verify error (also known as drk bypass - but temporary read note)-
Extract Stock firmware AP file
Make a copy of boot.img and delete recovery.img
Note - if files is boot.img.lz4 format change name to recovery.img.lz4
Rename boot.img copy to recovery.img
Add all the files (including other files extracted) to tar.
Flash Modded AP file with BL, CP, CSC (nand erase not required)
The phone will boot into stock firmware
Note- cannot reboot, will stuck at dm-verify error again and need to flash modded AP again.
Wait 7 days to oem unlock phone or use 7 day bypass by changing dates (not always work, keep trying, don’t reboot, worked for Samsunguser932 Edit: Imei must be 0000)
Once oem unlock flash TWRP and restore efs backup Edit: if you haven't fixed imei fix now by *#06# with combination file
Flash stock firmware once again by odin (stock, not modded)
Done - phone is back to normal
Click to expand...
Click to collapse
Note -
dm verify cannot be completely fixed, it can only be bypassed (in the system by flashing no dm verify).
You will need to wait for 7 days for oem unlock (there is no method to skip oem unlock)
Warranty will be voided (KNOX 1) - don't think there is a method to avoid tripping knox.
Suggest installing a custom rom after oem unlock (many reports that no dm verify on latest oreo does not work without root)
klisza1993 said:
Can someone explain me what is this EFS ?? I'm flashing roms many many times and I hadn't such problems etc
Click to expand...
Click to collapse
EFS partition is not touched when flashing roms (they actually do but in a safe way), only retards like I would try to mod efs partition.
Hi guys, will it work in my case? https://ibb.co/mJRcHK
Device is SM-N950N FRP ON and OEM ON.
What kind of solution should I follow?
@Anvar2005 - This looks like a drk verify error. Which binary are you on? frp bypass only works with binary 3. You will not find anything for frp unlock on this forum. Same steps for drk verify but use nougat.
"FRP Unlock SM-T377W, Unsuccessful on 7.1.1 ? Help Please"
I have SM-T377W with 7.1.1
I tried to flash it with this COMBINATIONS firmware
COMBINATION_OYA_FA60_T377WVLU3ARG1
Then I used the Z3x Tool to reset FRP, it says "OK"
however, then when I put it again on Download mode it is still Locked FRP
Also when I re-flash it with OEM it still ask for Google Verification
I also tried to flash it with TWRP to Root it but I keep getting
Custom Binary Block by FRP Lock
IS THERE A WAY TO REMOVE FRP FROM THIS DEVICE ?
--------- OEM flash in this device is ----------
Canada (Rogers)
PDA: T377WVLU3BRG4
Product Code: RWC
CSC: T377WOYA3BRG4
Phone: T377WVLU3BRG4
-------------------------------------
Any Suggestions Guys ?
Regards
msaithan said:
"FRP Unlock SM-T377W, Unsuccessful on 7.1.1 ? Help Please"
I have SM-T377W with 7.1.1
I tried to flash it with this COMBINATIONS firmware
COMBINATION_OYA_FA60_T377WVLU3ARG1
Then I used the Z3x Tool to reset FRP, it says "OK"
however, then when I put it again on Download mode it is still Locked FRP
Also when I re-flash it with OEM it still ask for Google Verification
I also tried to flash it with TWRP to Root it but I keep getting
Custom Binary Block by FRP Lock
IS THERE A WAY TO REMOVE FRP FROM THIS DEVICE ?
--------- OEM flash in this device is ----------
Canada (Rogers)
PDA: T377WVLU3BRG4
Product Code: RWC
CSC: T377WOYA3BRG4
Phone: T377WVLU3BRG4
-------------------------------------
Any Suggestions Guys ?
Regards
Click to expand...
Click to collapse
i am having the exact same problem as you with a samsung j1
cant get the custom recovery modes onto the phone.
odin flashes the stock rom no problem, but i cant get SR1-SuperSU-v2.78-SR1-20160915123031 or twrp on the phone.
DaDirtiest said:
i am having the exact same problem as you with a samsung j1
cant get the custom recovery modes onto the phone.
odin flashes the stock rom no problem, but i cant get SR1-SuperSU-v2.78-SR1-20160915123031 or twrp on the phone.
Click to expand...
Click to collapse
yea i have been trying for days now with no luck !
FRP Unlock solution for SM-T377W
msaithan said:
yea i have been trying for days now with no luck !
Click to expand...
Click to collapse
This is the only method that worked to solve the FRP lock issue. The video is not in English but you can still follow the instructions.
youtube_com/watch?v=NplMF8O2aTk&t=579s&index=2&list=LLWLJUl2J_mwEvi3FgXukeUA
Ray_D_2018 said:
This is the only method that worked to solve the FRP lock issue. The video is not in English but you can still follow the instructions.
youtube_com/watch?v=NplMF8O2aTk&t=579s&index=2&list=LLWLJUl2J_mwEvi3FgXukeUA
Click to expand...
Click to collapse
You are a Legend BRO (+ who made the video), finally i unlocked the Samsung SM-T377W from rogers
I had the correct files (combination + stock) its just that one step i was missing, the final step of combining the 3 correct files (sboot, boot + system)
I appreciate it bro
Ray_D_2018 said:
This is the only method that worked to solve the FRP lock issue. The video is not in English but you can still follow the instructions.
youtube_com/watch?v=NplMF8O2aTk&t=579s&index=2&list=LLWLJUl2J_mwEvi3FgXukeUA
Click to expand...
Click to collapse
i followed to youtube tutorial and succesfully flashed my A520w using COMBINATION_OYA_FA60_A520WVLU1AQC1 but i cannot get the phone to reboot any suggestions?
the odin operation was a success so are there other things i should push up in this phone and how can i get it to reboot its really weird i can only put it into download mode before it gave me the message about operating system error use samsung smart switch software, now it doesnt do that its just black screen of death when i choose rebooot
DaDirtiest said:
i followed to youtube tutorial and succesfully flashed my A520w using COMBINATION_OYA_FA60_A520WVLU1AQC1 but i cannot get the phone to reboot any suggestions?
the odin operation was a success so are there other things i should push up in this phone and how can i get it to reboot its really weird i can only put it into download mode before it gave me the message about operating system error use samsung smart switch software, now it doesnt do that its just black screen of death when i choose rebooot
Click to expand...
Click to collapse
You might want to try and do a factory reset at this point and see if that resolves the issue. Alternatively, maybe trying loading the stock software ROM through download mode and retry the process.
GuestD0091 said:
You might want to try and do a factory reset at this point and see if that resolves the issue. Alternatively, maybe trying loading the stock software ROM through download mode and retry the process.
Click to expand...
Click to collapse
did the 3 file combination
then flashed with stock rom
now finally into the phone, but
stuck at the frp lock screen
A520W with videotron