Hi!
I had PacMan Rom Milestone 1 on my tab. Then the official Jelly Bean rom from Samsung was ported to the p6810 and I wanted to try it because I had problems with wifi.
After flashing with Mobile Odin the tab was stuck at Samsung logo (the animated and colored one). (I waited for +10 minutes, maybe I wasn t patient enogh)
So I tryed reflashing with Heimdall (as I only have a linux machine at the moment):
-First I flashed with the GUI and it did flash all the files except sbl (No correct response (or something like that) at the end of the transfer of sbl.bin).
-So I tryed flashing form command line but the command line tool did completely ignore the sbl. I also tryed to flash only sbl but so it didn´t flash anything, but didn´t give out any errors.
-Ok let´s flash the new rom released by Samsung for Spain in September. Sadly now the tab is stuck at the first boot screen
$ sudo heimdall flash --cache cache.img --factoryfs factoryfs.img --hidden hidden.img --recovery recovery.img --secondary-boot Sbl.bin --kernel zImage --param param.lfs
Password or swipe finger:
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
100%
KERNEL upload successful
Uploading RECOVERY
100%
RECOVERY upload successful
Uploading CACHE
100%
CACHE upload successful
Uploading FACTORYFS
100%
FACTORYFS upload successful
Uploading HIDDEN
100%
HIDDEN upload successful
Uploading SBL1
100%
SBL1 upload successful
Uploading PARAM
100%
PARAM upload successful
Ending session...
Rebooting device...
Re-attaching kernel driver...
Click to expand...
Click to collapse
I read many threads about this problem and I´m trying to discharge the tab now but I don´t have the same problems (I can go into recovery without problems).
Can I do a "wipe data/factory reset" without risking the brick bug?
Thank you for reading the long explanation.
Teddy
Ok I got it running with PacMan flashed from CWM and I restted the flash counter . Now I'll see if get Stock GB running...
Hello! I installed an AP to be a superuser, but after I've done so (using a tutorial I can't link since I have less than 10 posts) the phone bricked. It was supposed to do that and then be able to root it, but it didn't work. Now I'm stuck. I downloaded the stock AP from this forum but when I try to install it says "model mismatch fail"
Can someone help me please?
Entering Download mode, this is the info I get.
ODIN MODE (HIGH SPEED)
PRODUCT NAE: SM-G930A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: OFF
WARRATY VOID: 0x0
QUALCOMM SECURE BOOT: ENABLE
AP SWREV: B4 (2, 1, 1, 1, 1) K1 S3
SECURE DOWNLOAD: ENABLE
I noticed I shouldn't have posted a question in this subforum. I apologize but I can't delete it.
Zyurat said:
I noticed I shouldn't have posted a question in this subforum. I apologize but I can't delete it.
Click to expand...
Click to collapse
Havr you trued downloading and flashin with ODIN the rom for your phone. Flash all the files, not only the AP. What does ODIN say appart from the "mismatch message"
Sent from my SM-G930F using Tapatalk
Hey! Found an S7 in June, no one claimed for three months so yeh... My phone now. I accidentally upgraded firmware to G930FXXS3ERHD. Is there a way to bypass the FRP lock with this version? I have tried everything I could find on the internet.
Download mode says:
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
Secure Download: Enabled
FRP LOCK: ON
AP SWREV: B:3 K:1 S:2
contact me via whtasapp +2347069605746
i am stuck with the same problem...
monsterkaka said:
Hey! Found an S7 in June, no one claimed for three months so yeh... My phone now. I accidentally upgraded firmware to G930FXXS3ERHD. Is there a way to bypass the FRP lock with this version? I have tried everything I could find on the internet.
Download mode says:
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
Secure Download: Enabled
FRP LOCK: ON
AP SWREV: B:3 K:1 S:2
Click to expand...
Click to collapse
i need help to ...i guess
same problem here pretty much, any solutions?
please disregard. accidently posted
disregard. mistake
I'm stuck in same issue
monsterkaka said:
Hey! Found an S7 in June, no one claimed for three months so yeh... My phone now. I accidentally upgraded firmware to G930FXXS3ERHD. Is there a way to bypass the FRP lock with this version? I have tried everything I could find on the internet.
Download mode says:
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
Secure Download: Enabled
FRP LOCK: ON
AP SWREV: B:3 K:1 S:2
Click to expand...
Click to collapse
BINARY: Samsung official
System status: official
FRP LOCK: ON
Secure Download: Enable
Warranty: 0x030c
RP SWREV: B:3 K:1 S:2
KERNEL REV. CHECK FAIL. DEVICE:1, BINARY:0
I tried Smart Switch recovery feature but it's now showing there. When I try to go to recovery mode. It said. "An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC software". Backstory. I install TWRP in the device from download mode without rooting it. And jump to TWRP on the first restart. And install SuperUser, Xpose etc then restart and enable Super User on boot. The phone is locked after installing new updates. I try to flash BL, AP using Odin 3.12 and 3.13.1. It's failing
Can't turn on the phone. What to do? Please help. Thanks
Step one: Download some marshmallow rom or some nougat rom which has some frp bypass exploit, download an oreo rom and download patched odin https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Step two: flash the oreo rom and boot your device, so you know that your device does actually boot and is not totally broken.
Step three: you need to mix up the two roms, its been a while since i've done this, so i don't remember how i mixed the roms up, i think i installed AP, CP and CSC of the marshmallow/nougat rom and BL of the Oreo rom. Just try this out, if it won't work, you need to try to mix them up differently, maybe install BL and CP of the Oreo rom and AP + CSC of the marshmallow/nougat rom. Just try out until odin says it passed and the phone boots into marshmallow/nougat
Step four: use an frp bypass exploit that works on the marshallow/nougat rom you installed
please don't be angry because of my bad english and bad formatting, hope it works for you. I did this on the second bootloader version, so maybe samsung fixed this on your bootloader version.
qamar.cyb said:
BINARY: Samsung official
System status: official
FRP LOCK: ON
Secure Download: Enable
Warranty: 0x030c
RP SWREV: B:3 K:1 S:2
KERNEL REV. CHECK FAIL. DEVICE:1, BINARY:0
I tried Smart Switch recovery feature but it's now showing there. When I try to go to recovery mode. It said. "An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC software". Backstory. I install TWRP in the device from download mode without rooting it. And jump to TWRP on the first restart. And install SuperUser, Xpose etc then restart and enable Super User on boot. The phone is locked after installing new updates. I try to flash BL, AP using Odin 3.12 and 3.13.1. It's failing
Can't turn on the phone. What to do? Please help. Thanks
Click to expand...
Click to collapse
Sorry for late answer, I think I can help. I can upload files later for you to download.
I followed this video and it works. (Verified on SM-G930F)
edit:
Cannot post outside links, but search on youtube for "BOOM!!!Without PC! Samsung S7 Edge SM-G935F Binary 3 Remove Google Account.Bypass FRP." on youtube.
Hope it helps
frp off binary3
monsterkaka said:
Hey! Found an S7 in June, no one claimed for three months so yeh... My phone now. I accidentally upgraded firmware to G930FXXS3ERHD. Is there a way to bypass the FRP lock with this version? I have tried everything I could find on the internet.
Download mode says:
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
Secure Download: Enabled
FRP LOCK: ON
AP SWREV: B:3 K:1 S:2
Click to expand...
Click to collapse
Bypass on the g930F starting Google Android 8 BINARY 3
download the firmware combination for it COMBINATION_FA60_G930FXXU3ARI2_CL7964511_QB19635501_REV00_user_mid_noship.tar
THE PHONE IS IN DONLOAD MODE AND WRITE <AP> WITH ODIN
after firmware and first shut down
we will go into recovery - the module deletes the data (the rest of the factory values)
after uploaded in the system allows the developer and debug mode with * # 0808 # ACTIVATE DM + DHW + ADB AND MAKE RESTART.
AFTER RESTART IS THE PHONE IN DONLOAD MODE Flash 8 Android i G930FXXS3ERHD - 8.0.0 - BTU (United Kingdom) - Multi Firmware + PIT
Extract from boot, system and boot (AP and BL)
!!!! Be the APs and BLs. WILL BE MODIFIED FROM MD5. RENEME .TAR (SHOW ARCHIVE RAR)
DONLOAD WITH ODIN AP + BL
Restart and wait. (after program optimization) TELEPHONE WILL BE FRP OF!
BOGDANCOSARCA said:
Bypass on the g930F starting Google Android 8 BINARY 3
download the firmware combination for it COMBINATION_FA60_G930FXXU3ARI2_CL7964511_QB19635501_REV00_user_mid_noship.tar
THE PHONE IS IN DONLOAD MODE AND WRITE <AP> WITH ODIN
after firmware and first shut down
we will go into recovery - the module deletes the data (the rest of the factory values)
after uploaded in the system allows the developer and debug mode with * # 0808 # ACTIVATE DM + DHW + ADB AND MAKE RESTART.
AFTER RESTART IS THE PHONE IN DONLOAD MODE Flash 8 Android i G930FXXS3ERHD - 8.0.0 - BTU (United Kingdom) - Multi Firmware + PIT
Extract from boot, system and boot (AP and BL)
!!!! Be the APs and BLs. WILL BE MODIFIED FROM MD5. RENEME .TAR (SHOW ARCHIVE RAR)
DONLOAD WITH ODIN AP + BL
Restart and wait. (after program optimization) TELEPHONE WILL BE FRP OF!
Click to expand...
Click to collapse
Thank you, but it is already fixed.
monsterkaka said:
Thank you, but it is already fixed.
Click to expand...
Click to collapse
Hi Someone please help me, im on binary 3 oreao firmware, ive tried various things but im learning also but would like a fix.
please help?
monsterkaka said:
Thank you, but it is already fixed.
Click to expand...
Click to collapse
Hi Mate how did you fix this?? is your last problem was something like this? if its YES help me. check atteachments.
pedropenduko said:
Hi Mate how did you fix this?? is your last problem was something like this? if its YES help me. check atteachments.
Click to expand...
Click to collapse
Yes something like that. PM me if you still have the problem. I might be able to help.
BOGDANCOSARCA said:
Bypass on the g930F starting Google Android 8 BINARY 3
download the firmware combination for it COMBINATION_FA60_G930FXXU3ARI2_CL7964511_QB19635501_REV00_user_mid_noship.tar
THE PHONE IS IN DONLOAD MODE AND WRITE <AP> WITH ODIN
after firmware and first shut down
we will go into recovery - the module deletes the data (the rest of the factory values)
after uploaded in the system allows the developer and debug mode with * # 0808 # ACTIVATE DM + DHW + ADB AND MAKE RESTART.
AFTER RESTART IS THE PHONE IN DONLOAD MODE Flash 8 Android i G930FXXS3ERHD - 8.0.0 - BTU (United Kingdom) - Multi Firmware + PIT
Extract from boot, system and boot (AP and BL)
!!!! Be the APs and BLs. WILL BE MODIFIED FROM MD5. RENEME .TAR (SHOW ARCHIVE RAR)
DONLOAD WITH ODIN AP + BL
Restart and wait. (after program optimization) TELEPHONE WILL BE FRP OF!
Click to expand...
Click to collapse
can you make it more clear plz from "we will go into recovery...." i cant understand what you typing here...
i have thesame problem
monsterkaka said:
Yes something like that. PM me if you still have the problem. I might be able to help.
Click to expand...
Click to collapse
mate... can u tell us the solution? thanks
Hi All,
I have a Samsung Galaxy Tab A SM-T380 that is not booting up. Upon trying to do a factory reset the following message is seen.
Code:
Android Recovery
samsung/gta2swifidx/gta2swifi
9/PPR1.180610.011/T380DXU3CSI5
user/release-keys
Use volume up/down and power
<Recovery menu here>
#Reboot Recovery Cause is [[check_boot_mode]RebootRecovryWithKey]
#
No Support SINGLE-SKU
File Based OTA
Supported API: 3
E: unknown volume for path [/odm]
E: unknown vloum for path [/vendor]
dm-verity verification failed...
E: Failed to clear BCB message: failed to open /dev/block/bootdevice/by-name/misc: No such file or directory
After selecting the factory reset option I get this message
Code:
--Wiping data...
Formatting /data...
Formatting /cache...
Data wipe complete.
E: Failed to clear BCB message: failed to open /dev/block/bootdevice/by-name/misc: No such file or directory
Upon selecting the bootloader option I get this
Code:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-T380
CURRENT BINARY: SAMSUNG OFFICIAL
FAP LOCK: ON
OEM LOCK: ON
WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A3, P1
RP SWREV: K 2, S 2
SECURE DOWNLOAD: ENABLE
DOWNLOAD MODE!!
Please I have not tried to install any custom ROM. No idea why this happened.
Any help in getting this working is appreciated.
Thanks and Regards
Used ODIN and stock firmware to reflash got it working
Used ODIN and stock firmware from sammobile to reflash it and got it working.
Thanks and regards,
cybarite said:
Used ODIN and stock firmware from sammobile to reflash it and got it working.
Thanks and regards,
Click to expand...
Click to collapse
I have the same problem. What Odin did you use and which slot did you use to flash the firmware? Please help. Thanks so much.
alias4ever said:
I have the same problem. What Odin did you use and which slot did you use to flash the firmware? Please help. Thanks so much.
Click to expand...
Click to collapse
Odin v3.14.4. I flashed it using by connecting the usb cable to the PC.
Regards
Cybarite
[Solved] Heimdall problem s10e "an error has occured while updating device software"
Hi there, I was trying to change my firmware (to prepare my phone before flashing a lineageos rom), I did so using heimdall (last samsung firmware downloaded from sammobile), and it crashed in the middle of the process (while copying VENDOR file). Not sure if it is a problem with the firmware or something else (but I guess not the cable as I tried with 2 cables and the problem arrives always at the same moment).
The phone is a SM-G970F, I was trying to flash the firmware U9DTJA.
Anyway, I can still flash with heimdall, although the screen is not the "standard" download mode screen… but I don't know what to do!? I tried to install virtualbox+samsung drivers + odin (standard version and then patched version), I can't get odin to recognize my phone. Windows just tells me "this device can perform faster" when I allow virtualbox to detect the phone (which appears as Samsung Gadget Serial [021B]). I also tried smart switch without success (I don't know what it is suppose to do, but looks like it does not recognize any phone). Do you think this is normal due to the fact that the phone is not truly in download mode? Or is it a problem with windows drivers? An idea to either fix things with heimdall or to get odin working?
I would appreciate if someone has any hints as it's my only phone and I'm kind of stuck
-------------- EDIT: this is what I get when flashing:
heimdall flash --BOOTLOADER sboot.bin --CM cm.bin --PARAM param.bin --UP_PARAM up_param.bin --KEYSTORAGE keystorage.bin --UH uh.bin --DTB dt.img --DTBO dtbo.img --BOOT boot.img --RECOVERY recovery.img --RADIO modem.bin --DQMDBG dqmdbg.img --VBMETA vbmeta.img --SYSTEM system.img --VENDOR vendor.img --PRODUCT product.img --CACHE cache.img --OMR omr.img --CP_DEBUG modem_debug.bin --USERDATA userdata.img
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOTLOADER
100%
BOOTLOADER upload successful
Uploading CM
100%
CM upload successful
Uploading PARAM
100%
PARAM upload successful
Uploading UP_PARAM
100%
UP_PARAM upload successful
Uploading KEYSTORAGE
100%
KEYSTORAGE upload successful
Uploading UH
100%
UH upload successful
Uploading DTB
100%
DTB upload successful
Uploading DTBO
100%
DTBO upload successful
Uploading BOOT
100%
BOOT upload successful
Uploading RECOVERY
100%
RECOVERY upload successful
Uploading RADIO
100%
RADIO upload successful
Uploading DQMDBG
100%
DQMDBG upload successful
Uploading VBMETA
100%
VBMETA upload successful
Uploading SYSTEM
100%
SYSTEM upload successful
Uploading VENDOR
21%
ERROR: Failed to send file part packet!
ERROR: VENDOR upload failed!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Click to expand...
Click to collapse
Well I found a workaround. Apparently:
- There is a bug with heimdall or libusb, I don't know at which level exactly but it does not work well with this device and I'm apparently not the only one for which it happened
- Altough the screen was not the "standard" download mode ,the phone was ready to be flashed, no problem with that.
- I managed to flash with odin by borrowing a windows computer… … …
- I have no idea why it does not work with virtualbox, but apparently this was really a virtualbox problem (or the way linux deals with usb, no idea) and nothing related to the phone in particular. It would be great to find a way to get that working, but I have no clue so far.
At least, I have a working phone now…