I tried to root my Samsung Galaxy Tab A (SM-T550) by loading this .tar (androidfilehost(dot)com/?fid=23991606952613365) with Odin 3.10.6 (also tried 3.10.7). After rebooting, it hangs eternally on the Samsung logo. Searching for other solutions, I tried rebooting in recovery mode and clearing the cache and doing a factory reset, then flashing the thing again. Didn't work. I'm very new to this, and don't know how else to proceed (or what most things even mean, I just followed a guide (consumingtech(dot)com/how-to-root-the-samsung-galaxy-tab-a-9-7). Any help would be greatly appreciated.
avikarto said:
I tried to root my Samsung Galaxy Tab A (SM-T550) by loading this .tar (androidfilehost(dot)com/?fid=23991606952613365) with Odin 3.10.6 (also tried 3.10.7). After rebooting, it hangs eternally on the Samsung logo. Searching for other solutions, I tried rebooting in recovery mode and clearing the cache and doing a factory reset, then flashing the thing again. Didn't work. I'm very new to this, and don't know how else to proceed (or what most things even mean, I just followed a guide (consumingtech(dot)com/how-to-root-the-samsung-galaxy-tab-a-9-7). Any help would be greatly appreciated.
Click to expand...
Click to collapse
Try flashing your stock firmware to repair the device.
Do a Google search for:
"Return to stock(your model number)"
Your device might have a locked bootloader, that prevents CF autoroot from working correctly. If it's locked, you need to unlock and then you can flash the device to root it.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Try flashing your stock firmware to repair the device.
Do a Google search for:
"Return to stock(your model number)"
Your device might have a locked bootloader, that prevents CF autoroot from working correctly. If it's locked, you need to unlock and then you can flash the device to root it.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I re-cleared my cache and did a factory reset, then flashed an 11 MB stock .tar that I found on xda. The issue persists. I also found a 1.3 GB zip file which apparently is different than the single tar because you have to use multiple fields in Odin instead of just AP, and I'll try this one next for lack of better options. I don't understand the massive size difference though if they are both supposed to be the stock firmware.
avikarto said:
I re-cleared my cache and did a factory reset, then flashed an 11 MB stock .tar that I found on xda. The issue persists. I also found a 1.3 GB zip file which apparently is different than the single tar because you have to use multiple fields in Odin instead of just AP, and I'll try this one next for lack of better options. I don't understand the massive size difference though if they are both supposed to be the stock firmware.
Click to expand...
Click to collapse
There is no difference is size, some Samsung stock firmware come in an all-in-one file that is placed in the AP slot in Odin, but some stock firmware come in a 4 part or 5 part firmware. The all-in-one firmware is placed in The AP slot in Odin, but the 4 part and 5 part firmware are meant to place each part of the firmware in its corresponding slot in Odin(i.e. BL-BL, AP-AP, CP(or Phone)-CP and CSC(the 5 part firmware have the option of using CSC or Home CSC in the CSC slot, Home CSC is for devices being used in their country/region of origin, CSC is for devices being used outside their country/region.
Sent from my LGL84VL using Tapatalk
Droidriven said:
There is no difference is size, some Samsung stock firmware come in an all-in-one file that is placed in the AP slot in Odin, but some stock firmware come in a 4 part or 5 part firmware. The all-in-one firmware is placed in The AP slot in Odin, but the 4 part and 5 part firmware are meant to place each part of the firmware in its corresponding slot in Odin(i.e. BL-BL, AP-AP, CP(or Phone)-CP and CSC(the 5 part firmware have the option of using CSC or Home CSC in the CSC slot, Home CSC is for devices being used in their country/region of origin, CSC is for devices being used outside their country/region.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks for the info. While the 11 MB .tar did not work, the 1.3 GB zip file containing BL and AP elements did work to clear my boot loop. Someone elsewhere mentioned that the original problem could have been caused by not ticking "OEM unlocking" in the developer options before trying to root, but I don't see this setting in my dev options menu. I checked USB debugging as required for the flashing, but don't see any entry for unlocking of any kind. Do you know what this could be referring to, if relevant?
avikarto said:
Thanks for the info. While the 11 MB .tar did not work, the 1.3 GB zip file containing BL and AP elements did work to clear my boot loop. Someone elsewhere mentioned that the original problem could have been caused by not ticking "OEM unlocking" in the developer options before trying to root, but I don't see this setting in my dev options menu. I checked USB debugging as required for the flashing, but don't see any entry for unlocking of any kind. Do you know what this could be referring to, if relevant?
Click to expand...
Click to collapse
The OEM unlock setting is the first step in the process of unlocking bootloader, bootloader must be unlocked before trying to flash anything that is not the stock firmware. The OEM unlock setting does not unlock the bootloader, it only puts the device in a state that the bootloader can be unlocked, similar to how the USB debugging setting does not flash a device but puts the device in a state that it can be flashed. Not all devices have the OEM unlock setting and not all devices can unlock bootloader, especially Samsung devices after 4.4 was introduced.
Find a method to unlock your bootloader.
Sent from my LGL84VL using Tapatalk
Related
Hi,
I've got an Samsung Galaxy S7 which won't boot android anymore. this was after the phone was hot.
Recovery and download mode works. Is there a way to copy photos to a computer or sdcard somehow?
Thanks
arjanv said:
Hi,
I've got an Samsung Galaxy S7 which won't boot android anymore. this was after the phone was hot.
Recovery and download mode works. Is there a way to copy photos to a computer or sdcard somehow?
Thanks
Click to expand...
Click to collapse
If you connect your phone to your computer - Does the computer see the phone?
If you have your music and photos on the external sd card (if your pc doesn't see the phone) you could copy from the external sd card with a sd card reader - I believe that if you can boot into recovery that you can cope files from the phone to the pc as well.
Sent from my SM-G930W8 using Tapatalk
shaggyskunk said:
If you connect your phone to your computer - Does the computer see the phone?
If you have your music and photos on the external sd card (if your pc doesn't see the phone) you could copy from the external sd card with a sd card reader - I believe that if you can boot into recovery that you can cope files from the phone to the pc as well.
Sent from my SM-G930W8 using Tapatalk
Click to expand...
Click to collapse
no external sd card, otherwise there was no problem
Could we have some more information please?
Is the device Knox tripped or otherwise modified? (Rooted, custom recovery, custom firmware)
What's the model number?
What's the firmware build number?(The stock recovery will say).
Is the device encrypted?
(If you've set up Samsung Cloud or Google Photos backup you might have better luck there)
I don't think you can enter MTP mode with the phone only working from recovery and download mode. Simply install a ROM via TWRP but do not wipe internal storage. Once the phone boots up to android, retrieve your files.
Good luck
I'm able to boot in download mode.
Odin recognize the phone. is flashing possible without loosing data(only care about stuff on the internal SD card. loosing settings and apps is not a problem.
added attachment/screenshot.
arjanv said:
added attachment/screenshot.
Click to expand...
Click to collapse
Official firmware, so likely encrypted. Boot into recovery and take note of the build number and CSC. Download the exact same firmware from a site like SamMobile. Using Odin, flash the BL, AP, CP and HOME_CSC(NOT the plain CSC) packages in the firmware package by placing them in their relevant slots. It will make like it's doing a system update and take long to boot, but should result in a workable device with your data intact.
hi seems that recovery not working either,i've tried but can't get into recovery. sometimes a red text appears on the top left screen. something about sandforcing.
CurtisMJ said:
Could we have some more information please?
Is the device Knox tripped or otherwise modified? (Rooted, custom recovery, custom firmware)
What's the model number?
What's the firmware build number?(The stock recovery will say).
Is the device encrypted?
(If you've set up Samsung Cloud or Google Photos backup you might have better luck there)
Click to expand...
Click to collapse
CurtisMJ said:
Official firmware, so likely encrypted. Boot into recovery and take note of the build number and CSC. Download the exact same firmware from a site like SamMobile. Using Odin, flash the BL, AP, CP and HOME_CSC(NOT the plain CSC) packages in the firmware package by placing them in their relevant slots. It will make like it's doing a system update and take long to boot, but should result in a workable device with your data intact.
Click to expand...
Click to collapse
What about this? https://www.youtube.com/watch?v=cyCileqUVFQ they seems to flash only AP. Whats the different in results of flashing only AP or Flash AP, BL, CP and HOME_CSC?
arjanv said:
What about this? https://www.youtube.com/watch?v=cyCileqUVFQ they seems to flash only AP. Whats the different in results of flashing only AP or Flash AP, BL, CP and HOME_CSC?
Click to expand...
Click to collapse
Samsung old and new style of firmware packaging. They used to place all parts into a single package(AP), customised per region. This had the disadvantage of requiring a complete different firmware package for every region with little actual differences. New Samsung firmware comes broken up into the BL(bootloader), AP(system, kernel, recovery), CP(modem firmware) and CSC(recovery package which applies all region settings) packages. This way only the CSC needs to be changed per region.
At absolute minimum you should flash the AP and HOME_CSC/CSC package. (Though only if you're sure you're flashing the same firmware as the current or you may trip knox)
The general rule is if you flash AP, then CSC must be flashed aswell, otherwise the firmware becomes very buggy.
The regular CSC file wipes storage, while HOME_CSC does not, but will only work if the current CSC matches the firmware package
If you like you may use Smart Switch Emergency firmware recovery instead, but beware, as it's known to mess up more often than not
arjanv said:
hi seems that recovery not working either,i've tried but can't get into recovery. sometimes a red text appears on the top left screen. something about sandforcing.
Click to expand...
Click to collapse
Did it perhaps say "SEAndroid not enforcing"? That means it's an unofficial recovery image. Not sure how that could happen. Seems like firmware was corrupted somehow.
thanks for explaining.
I've download the latest firmware from sammobile which contains these files:
AP_G935FXXU1DQE7_CL11104523_QB13505684_REV00_user_low_ship_meta.tar
BL_G935FXXU1DQE7_CL11104523_QB13505684_REV00_user_low_ship.tar
CP_G935FXXU1DQD7_CL11104523_QB13263377_REV00_user_low_ship.tar
CSC_PHN_G935FPHN1DQD1_CL10939265_QB13310839_REV00_user_low_ship.tar
HOME_CSC_PHN_G935FPHN1DQD1_CL10939265_QB13310839_REV00_user_low_ship.tar
I want to save photos, so i try to flash AP and HOME_CSC using odin right?
arjanv said:
thanks for explaining.
I've download the latest firmware from sammobile which contains these files:
AP_G935FXXU1DQE7_CL11104523_QB13505684_REV00_user_low_ship_meta.tar
BL_G935FXXU1DQE7_CL11104523_QB13505684_REV00_user_low_ship.tar
CP_G935FXXU1DQD7_CL11104523_QB13263377_REV00_user_low_ship.tar
CSC_PHN_G935FPHN1DQD1_CL10939265_QB13310839_REV00_user_low_ship.tar
HOME_CSC_PHN_G935FPHN1DQD1_CL10939265_QB13310839_REV00_user_low_ship.tar
I want to save photos, so i try to flash AP and HOME_CSC using odin right?
Click to expand...
Click to collapse
Wrong firmware I'm afraid. Notice your screenshot says the device is a SM-G930F, these are SM-G935F files for the Galaxy S7 Edge. Also, since we don't know what firmware revision the device is on, you *need* to flash the BL and CP parts too.
Could you please check the bottom of your box? You need the three-letter CSC code. If you get it wrong your data is toast.
So final process is:
1. Check your box for the CSC code
2. Select your CSC in the "Select Country" dropdown https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/
3. Download the latest firmware
4. Flash BL, AP, CP and HOME_CSC from the package.
5. Device should auto-reboot and will ask you for your lockscreen passphrase.
oops, sorry. copy paste the wrong files.
i meant these files:
AP_G930FXXU1DQE7_CL11104523_QB13505661_REV00_user_low_ship_meta.tar
BL_G930FXXU1DQE7_CL11104523_QB13505661_REV00_user_low_ship.tar
CP_G930FXXU1DQD7_CL11104523_QB13263348_REV00_user_low_ship.tar
CSC_PHN_G930FPHN1DQD1_CL10939265_QB13310834_REV00_user_low_ship.tar
HOME_CSC_PHN_G930FPHN1DQD1_CL10939265_QB13310834_REV00_user_low_ship.tar
arjanv said:
i meant these files:
AP_G930FXXU1DQE7_CL11104523_QB13505661_REV00_user_low_ship_meta.tar
BL_G930FXXU1DQE7_CL11104523_QB13505661_REV00_user_low_ship.tar
CP_G930FXXU1DQD7_CL11104523_QB13263348_REV00_user_low_ship.tar
CSC_PHN_G930FPHN1DQD1_CL10939265_QB13310834_REV00_user_low_ship.tar
HOME_CSC_PHN_G930FPHN1DQD1_CL10939265_QB13310834_REV00_user_low_ship.tar
Click to expand...
Click to collapse
If your CSC code is PHN then yes.
CurtisMJ said:
If your CSC code is PHN then yes.
Click to expand...
Click to collapse
this says the box. see attachment
tried to flash and now this message(see attachment)
what now?
found this on a other post.
just extract your firmware with win rar and copy recovery.img to your desktop
there is a tool for making .tar file from .img called tar-Tool .
with tar tool you can make .tar from .img files
convert recovery.img to recovery.tar with this tool
flash it in pda (AP) in odin . now you can go to recovery mode
then wipe data/factory reset and wipe cache
rebooot
arjanv said:
tried to flash and now this message(see attachment)
what now?
found this on a other post.
just extract your firmware with win rar and copy recovery.img to your desktop
there is a tool for making .tar file from .img called tar-Tool .
with tar tool you can make .tar from .img files
convert recovery.img to recovery.tar with this tool
flash it in pda (AP) in odin . now you can go to recovery mode
then wipe data/factory reset and wipe cache
rebooot
Click to expand...
Click to collapse
That means Odin didnt finish one of its operations. You need to use Odin 3.12+. The device wont let you do anything else until it registers a successful flash in download mode.
I think it's best to just use Smart Switch.
https://forum.xda-developers.com/tmobile-galaxy-s6-edge/help/flash-stock-firmware-using-samsung-t3079176
Video is for S6, but the process is the same.
Beware that the internal SD will be wiped, but since the CSC is nowhere to be seen I think thats the only way, sorry.
EDIT:
Getting back to download mode:
https://forum.xda-developers.com/showpost.php?p=68632831&postcount=5
So my galaxy amp prime(Cricket, SM-J320AZ) is stuck in a bootloop, and I have tried to research why, yet every reason seams plausible. So ill start at the beginning...
I used odin with a boot.tar in the ap slot so that kingroot could root my phone. it was successful at rooting my device but refused to switch with supersu me( I now know I needed kingroot 4.5) anyways kingroot deployed as a system app which in turn compromised my safetynet status. I couldn't use a number of apps and services, so I decided to flash the stock rom for my device (found here on xda) it was a little over 1gb and I followed directions. yet when odin successfully flashed it, the device rebooted and now is stuck in a bootloop. it loads the Samsung logo twice then reverts to the android recovery. I tried to wipe cache partition and reboot to no avail. I then tried to wide data/factory reset and reboot, but its still stuck in bootloop.
I originally made a backup with Samsung smart switch, but now it says the device is unsupported.
Is there anything I can do? ive read soft bricks and bootloops can be fixed, but I'm not finding much on my device. any help is greatly appreciated,
sorry if this is in the wrong area, I'm still new to xda
Rororoolz said:
So my galaxy amp prime(Cricket, SM-J320AZ) is stuck in a bootloop, and I have tried to research why, yet every reason seams plausible. So ill start at the beginning...
I used odin with a boot.tar in the ap slot so that kingroot could root my phone. it was successful at rooting my device but refused to switch with supersu me( I now know I needed kingroot 4.5) anyways kingroot deployed as a system app which in turn compromised my safetynet status. I couldn't use a number of apps and services, so I decided to flash the stock rom for my device (found here on xda) it was a little over 1gb and I followed directions. yet when odin successfully flashed it, the device rebooted and now is stuck in a bootloop. it loads the Samsung logo twice then reverts to the android recovery. I tried to wipe cache partition and reboot to no avail. I then tried to wide data/factory reset and reboot, but its still stuck in bootloop.
I originally made a backup with Samsung smart switch, but now it says the device is unsupported.
Is there anything I can do? ive read soft bricks and bootloops can be fixed, but I'm not finding much on my device. any help is greatly appreciated,
sorry if this is in the wrong area, I'm still new to xda
Click to expand...
Click to collapse
Point to the firmware you downloaded and also which version of odin you used.
ashyx said:
Point to the firmware you downloaded and also which version of odin you used.
Click to expand...
Click to collapse
I extracted this
AP_J320AUCS2AQA1_CL7663112_QB12351033_REV00_user_low_ship.tar
i believe is the firmware, and I'm using odin 3.11.1
I also asked in page 17 of the original thread
I'm just running out of options here lol
you actually posted right above me in that thread!
Rororoolz said:
I extracted this
AP_J320AUCS2AQA1_CL7663112_QB12351033_REV00_user_low_ship.tar
i believe is the firmware, and I'm using odin 3.11.1
I also asked in page 17 of the original thread
I'm just running out of options here lol
Click to expand...
Click to collapse
I suggest you flash the entire firmware not just AP.
ashyx said:
I suggest you flash the entire firmware not just AP.
Click to expand...
Click to collapse
Do u happen to know where i can find the rest?
Would i have to re partition it? Because im trying to research and learn, but i was under the impression that AP was the only spot to put firmware
I believe your proper firmware would be J320AZTUU1APC4
http://www.mediafire.com/file/skiapd1xqj3s7se/J320AZTUU1APC4_J320AZAIO1APC4_5.1.1_USA_4Files.zip
seaf0ur said:
I believe your proper firmware would be J320AZTUU1APC4
http://www.mediafire.com/file/skiapd1xqj3s7se/J320AZTUU1APC4_J320AZAIO1APC4_5.1.1_USA_4Files.zip
Click to expand...
Click to collapse
The files say md5 error, binary failed
I think im missing something here
You tried to flash only AP but for J320A, here you have full firmware for J320AZ: https://drive.google.com/file/d/0B5vkBxwCY_cCSkh0UHNZMmxmcVk/view
johnny.goldy said:
You tried to flash only AP but for J320A, here you have full firmware for J320AZ: https://drive.google.com/file/d/0B5vkBxwCY_cCSkh0UHNZMmxmcVk/view
Click to expand...
Click to collapse
Most these files worked, i checked auto reboot, re partition, and r reset. I set the pit file and all 4 others in correct spot. Yet it failed a few times. I unchecked the bl file and it succeeded. When i reboot it shows logo twice then shows android saying installing sys update.... then error... then goes back to recovery.
Essentially i flashed everything except the bl file. And when i try to flash it by itself it says
Initialization
Erase...
Set PIT file
DO NOT TURN OFF TARGET
get pit for mapping
Firmware update starting
Single download
Sboot.bin
NAND write start!
Fail!
Complete(write) operation fail
............
Im guessing the problem is with my BL file
When i go to boot phone it shows an android and says installing system update then says error very quickly and goes to recovery.
I feel like thats progress but why would only BL file be failing? The green bar in odin goes halfway then fails (with only bl file checked)
Rororoolz said:
Most these files worked, i checked auto reboot, re partition, and r reset. I set the pit file and all 4 others in correct spot. Yet it failed a few times. I unchecked the bl file and it succeeded. When i reboot it shows logo twice then shows android saying installing sys update.... then error... then goes back to recovery.
Essentially i flashed everything except the bl file. And when i try to flash it by itself it says
Initialization
Erase...
Set PIT file
DO NOT TURN OFF TARGET
get pit for mapping
Firmware update starting
Single download
Sboot.bin
NAND write start!
Fail!
Complete(write) operation fail
............
Im guessing the problem is with my BL file
When i go to boot phone it shows an android and says installing system update then says error very quickly and goes to recovery.
I feel like thats progress but why would only BL file be failing? The green bar in odin goes halfway then fails (with only bl file checked)
Click to expand...
Click to collapse
It WILL fail at the bootloader as it's not intended for your device. Just flash the correct firmware as advised.
ashyx said:
It WILL fail at the bootloader as it's not intended for your device. Just flash the correct firmware as advised.
Click to expand...
Click to collapse
Thats what i mean, i extracted all 5 files as advised(a few comments ago) it had
BL
AP
CP
CSC
PIT
I placed them in corresponding odin slot (even pit, with re partition) yet it fails at the BL slot)
I flash it all except bl its still in bootloop
Also Says dm-verity verification failed
Mind you, that i am flashing the right firmware now. I realize my original mistake by flashing the 320a. But these are the stock 320AZ files i am now speaking of...
Rororoolz said:
Thats what i mean, i extracted all 5 files as advised(a few comments ago) it had
BL
AP
CP
CSC
PIT
I placed them in corresponding odin slot (even pit, with re partition) yet it fails at the BL slot)
I flash it all except bl its still in bootloop
Also Says dm-verity verification failed
Mind you, that i am flashing the right firmware now. I realize my original mistake by flashing the 320a. But these are the stock 320AZ files i am now speaking of...
Click to expand...
Click to collapse
This probably means you had a newer firmware revision on your device.
ashyx said:
This probably means you had a newer firmware revision on your device.
Click to expand...
Click to collapse
So do i have any options left? Or should i just chuck it into the cornfield
Rororoolz said:
So do i have any options left? Or should i just chuck it into the cornfield
Click to expand...
Click to collapse
Of course you probably just need the revision 3 firmware. It's posted at the link below.
https://forum.xda-developers.com/galaxy-j3-2016/development/odin-j320a-j320az-links-t3631914
J320AZTUS3AQG1
Try this one: https://www.androidfilehost.com/?fid=817550096634792721
johnny.goldy said:
Try this one: https://www.androidfilehost.com/?fid=817550096634792721
Click to expand...
Click to collapse
IT WORKED! Omg IT wOrked!
ashyx said:
Of course you probably just need the revision 3 firmware. It's posted at the link below.
https://forum.xda-developers.com/galaxy-j3-2016/development/odin-j320a-j320az-links-t3631914
J320AZTUS3AQG1
Click to expand...
Click to collapse
It wasnt the firmware you said, but thank you so much for the help!
Rororoolz said:
It wasnt the firmware you said, but thank you so much for the help!
Click to expand...
Click to collapse
Doesn't matter it was still revision 3 firmware.
The one linked is the latest revision 3 firmware.
Hello i have a Galaxy S7 SM-G930W8 thats frp locked and i have been looking to unlock it for the past 4 days but could not find any solution on how to please help,thanks
Kemako121 said:
Hello i have a Galaxy S7 SM-G930W8 thats frp locked and i have been looking to unlock it for the past 4 days but could not find any solution on how to please help,thanks
Click to expand...
Click to collapse
Flash stock then log in with your Google credentials
*Detection* said:
Flash stock then log in with your Google credentials
Click to expand...
Click to collapse
well could you please link me the stock of my phone because i cannot find it myself.... i was looking for a while and tried some but now my phone is just stuck on the boot screen..
Stock sm-g930w8 firmware is here: https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/
This post may be helpful: https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
audit13 said:
Stock sm-g930w8 firmware is here: https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/
This post may be helpful: https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
Click to expand...
Click to collapse
thank you a lot but i have another question after i ran a boot.tar from firmware.obi my phone is stuck on the boot logo what can i do to move on and is it safe if i boot the files u sent me with the current state of my phone? also the download will be ages since the speed for non premium is 15kb/sec
To return the phone to a stock condition, you flash the ROM using Odin which will overwrite everything with the possible exception of the data partition.
If the phone is stuck at the boot logo, have you tried a factory reset from stock recovery?
You can try this link: http://samsung-updates.com/device/?id=SM-G930W8 or https://updato.com/firmware-archive-select-model?exact=1&q=SM-G930W8
I don't know about download speeds for the above-two links as I have never used them before but other XDA members have.
audit13 said:
To return the phone to a stock condition, you flash the ROM using Odin which will overwrite everything with the possible exception of the data partition.
If the phone is stuck at the boot logo, have you tried a factory reset from stock recovery?
You can try this link: http://samsung-updates.com/device/?id=SM-G930W8 or https://updato.com/firmware-archive-select-model?exact=1&q=SM-G930W8
I don't know about download speeds for the above-two links as I have never used them before but other XDA members have.
Click to expand...
Click to collapse
i have tried going into the boot menu for factory reset but no luck the phone just resets,im starting the odin method right now with the thing you provided, also do i fill all the blanks (like the csc,ap and cp?) in odin?
After downloading the file from sammobile.com, unzip the file once (I use 7zip) to yield the necessary files. Each file will be preceded by the blank or slot location.
Difference between CSC and Home CSC: https://forum.xda-developers.com/s7-edge/help/csc-home-csc-simple-t3464835 or https://forum.xda-developers.com/galaxy-s7/help/question-using-ap-bl-csc-instead-home-t3562545
audit13 said:
After downloading the file from sammobile.com, unzip the file once (I use 7zip) to yield the necessary files. Each file will be preceded by the blank or slot location.
Difference between CSC and Home CSC: https://forum.xda-developers.com/s7-edge/help/csc-home-csc-simple-t3464835 or https://forum.xda-developers.com/galaxy-s7/help/question-using-ap-bl-csc-instead-home-t3562545
Click to expand...
Click to collapse
help when i put in all the things it says: SW REV. CHECK FAIL DEVICE:2 BINARY:1
Odin recognizes the phone? Are you seeing the message in download mode?
audit13 said:
Odin recognizes the phone? Are you seeing the message in download mode?
Click to expand...
Click to collapse
so i managed to get this phone back to its original state when it was frp locked by downloading software from sammobile but it still remembers the google account... i will try to download a older version of android and run that to hopefully get the phone to 6.0.1 or whatever the original version was and try some older ways to frp unlock my phone because the older version will have less security patches. hopefully this works! thanks for the help so far .:good:
I'm not sure that you can downgrade once the phone has been updated.
Good luck.
same here, stuck without solutions. tried pretty much everything found on the internet carefully and taking the time to do it.. but still...
i still need help can someone find a way to unlock my phone?
One way to remove frp lock is to flash a custom recovery (like TWRP) for your phone and then use the wipe -> format data (and type 'yes' when asked, without the quotes). Restart the phone and let the system boot. After it boots you can procede to flash the stock rom
* P.S. 1: flashing a custom recovery will trigger KNOX so say bye bye to S Health if you are not planning to root the phone (so as to be able to edit the build prop and enable SHealth again) after flashing the stock rom again. Do not attemp to flash the stock recovery image on its own or your phone will be soft bricked and the dm-verity error will give you nightmares (happened twice to me, took me 6 hours to recover my phone). To get back the stock recovery you need to flash the stock rom again.
* P.S. 2: If your phone has the bootloader locked you will not be able to flash a custom recovery. In that case you can try to downgrade to 6.0 but there are not guarantees that it will work ok.
Sent from my SM-G930F using Tapatalk
coto39 said:
One way to remove frp lock is to flash a custom recovery (like TWRP) for your phone and then use the wipe -> format data (and type 'yes' when asked, without the quotes). Restart the phone and let the system boot. After it boots you can procede to flash the stock rom
* P.S. 1: flashing a custom recovery will trigger KNOX so say bye bye to S Health if you are not planning to root the phone (so as to be able to edit the build prop and enable SHealth again) after flashing the stock rom again. Do not attemp to flash the stock recovery image on its own or your phone will be soft bricked and the dm-verity error will give you nightmares (happened twice to me, took me 6 hours to recover my phone). To get back the stock recovery you need to flash the stock rom again.
* P.S. 2: If your phone has the bootloader locked you will not be able to flash a custom recovery. In that case you can try to downgrade to 6.0 but there are not guarantees that it will work ok.
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
hi could you please link the stuff i need to download in order to to this my phone is SM-G930W8
Hi,
Using latest Odin I am trying to return to my phone to stock but cannot
I have tried 4 different firmware’s already (over 20 times) and each one will PASS the flash process, phone rests, installing system update (stops at around 30%) and during the blue screen the update stops, resets, receive Erasing message for a bit and then NO COMMAND and phone will simply not boot. (with some flashes the stock recovery is not even available, working or present)
... only way to boot the phone is to install TWRP... installing the NO VERITY file seems to help in booting…
I have noticed when i plug the phone is it comes up as another device name (from a previous ROM) so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
Back in DOWLOAD MODE under system status = CUSTOM (after flashing stock firmware)
My guess is that the new firmware I flash simply wont stick, or is half installed, or could be something to do with encryptions,
Some of the logs I see include:
Failed to open recovery
Reboot recovery cause UNKNOWN
E: Failed setting up dirty target
Fail to mount /system as rw
i have no idea what else to try
GODSPD said:
Hi,
Using latest Odin I am trying to return to my phone to stock but cannot
I have tried 4 different firmware’s already (over 20 times) and each one will PASS the flash process, phone rests, installing system update (stops at around 30%) and during the blue screen the update stops, resets, receive Erasing message for a bit and then NO COMMAND and phone will simply not boot. (with some flashes the stock recovery is not even available, working or present)
... only way to boot the phone is to install TWRP... installing the NO VERITY file seems to help in booting…
I have noticed when i plug the phone is it comes up as another device name (from a previous ROM) so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
Back in DOWLOAD MODE under system status = CUSTOM (after flashing stock firmware)
My guess is that the new firmware I flash simply wont stick, or is half installed, or could be something to do with encryptions,
Some of the logs I see include:
Failed to open recovery
Reboot recovery cause UNKNOWN
E: Failed setting up dirty target
Fail to mount /system as rw
i have no idea what else to try
Click to expand...
Click to collapse
You flashed the wrong firmware and corrupted your device.
You should flash the newest available firmware for your specific model number. You might have to flash the PIT file for your model number along with the firmware with the "re-partition" option checked in Odin when you flash it.
Sent from my LGL84VL using Tapatalk
Droidriven said:
You flashed the wrong firmware and corrupted your device.
You should flash the newest available firmware for your specific model number. You might have to flash the PIT file for your model number along with the firmware with the "re-partition" option checked in Odin when you flash it.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I need to keep v3 bootloader, i am very sure that latest firmware will work but i am trying to avoid it, and i never flashed the wrong firmware, i have tried aroud 6 different v3 and none will stick, can you suggest where i can find the PIT files and possible guide? without the pit file the repartition option fails each time...
GODSPD said:
I need to keep v3 bootloader, i am very sure that latest firmware will work but i am trying to avoid it, and i never flashed the wrong firmware, i have tried aroud 6 different v3 and none will stick, can you suggest where i can find the PIT files and possible guide? without the pit file the repartition option fails each time...
Click to expand...
Click to collapse
If you didn't flash the firmware then how did it show up as a different device "from a previous ROM", as you said?
They might have been V3 firmware, but was it for the same model number of V3 as yours? Are the model numbers different? Is V3 the model number? Or is it the device branded name?
Sent from my LGL84VL using Tapatalk
Droidriven said:
If you didn't flash the firmware then how did it show up as a different device "from a previous ROM", as you said?
Thanks for the feedback.
They might have been V3 firmware, but was it for the same model number of V3 as yours? Are the model numbers different? Is V3 the model number? Or is it the device branded name?
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks for the feedback, several months ago i flashed G935FXXS3ERHD_G935FXEO3ERG2_XEO on the S7 Edge International, so firmware is correct, i flashed a custom ROM - Glamour ROM a S9+ Ported ROM for the S7E, everything worked fine until i tried to revert back to stock, every other V3 firmware apart from the one mentioned above wont flash correctly, either fails or boot loops, has no stock recovery, and system status is still showing CUSTOM, when i plug the device in it will come up as Galaxy S9+ ... for some reason i cannot do a proper flash on it,
I am almost certain i can do a proper flash with the latest firmware but i am trying to avoid that...
GODSPD said:
Thanks for the feedback, several months ago i flashed G935FXXS3ERHD_G935FXEO3ERG2_XEO on the S7 Edge International, so firmware is correct, i flashed a custom ROM - Glamour ROM a S9+ Ported ROM for the S7E, everything worked fine until i tried to revert back to stock, every other V3 firmware apart from the one mentioned above wont flash correctly, either fails or boot loops, has no stock recovery, and system status is still showing CUSTOM, when i plug the device in it will come up as Galaxy S9+ ... for some reason i cannot do a proper flash on it,
I am almost certain i can do a proper flash with the latest firmware but i am trying to avoid that...
Click to expand...
Click to collapse
Have you tried factory resetting the device then try flashing via Odin? Sometimes there is conflicting data that prevents from flashing the firmware.
You might not have a choice of which firmware to flash to repair your device.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Have you tried factory resetting the device then try flashing via Odin? Sometimes there is conflicting data that prevents from flashing the firmware.
You might not have a choice of which firmware to flash to repair your device.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
more than you can imagine, every possible wipe and combination has been done with no luck at all
GODSPD said:
more than you can imagine, every possible wipe and combination has been done with no luck at all
Click to expand...
Click to collapse
Well then, suck it up and flash the newest firmware, you are out of options.
Your device probably doesn't allow downgrading, in this case, you can only flash exactly what was on the device before you caused the issue or a newer firmware, you can't go backwards to an older firmware.
If you're trying to flash an older firmware in an effort to get past a locked bootloader, you are probably wasting your time, that doesn't work out most of the time.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Well then, suck it up and flash the newest firmware, you are out of options.
Your device probably doesn't allow downgrading, in this case, you can only flash exactly what was on the device before you caused the issue or a newer firmware, you can't go backwards to an older firmware.
If you're trying to flash an older firmware in an effort to get past a locked bootloader, you are probably wasting your time, that doesn't work out most of the time.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
That definitely makes sense that i cannot downgrade but i am flashing either the same firmware or slightly newer staying on the same bootloader version.
Hi, my phone has get the message "Custom binary blocked by FAP Lock"
And before flashing the firmware, I want to recover so much important files that I have in the device.
There's a method for recover the files in Download Mode or something?
Please, that happened six days ago and I really need this data.
Thanks so much.
LucasCordoba said:
Hi, my phone has get the message "Custom binary blocked by FAP Lock"
And before flashing the firmware, I want to recover so much important files that I have in the device.
There's a method for recover the files in Download Mode or something?
Please, that happened six days ago and I really need this data.
Thanks so much.
Click to expand...
Click to collapse
No, you can not recover the data via download mode, download mode can only be used to flash the device.
You need to download the full stock firmware for your model number and flash it via Odin but when you flash it, if there are two different CSC files that can be used when you flash it, use the one that does not wipe user data during flashing then you will have access to your data once the device boots properly.
If you know or can find out what the build number is for the stock firmware that was on the device before you tried to modify it, you need to flash that exact build number.
If you flash something that is newer than the stock firmware that was already on the device, it might have an upgraded bootloader which means it would wipe your data when you flash that firmware.
If you are very careful in choosing the exact same firmware that you already had on the device and if you use the CSC file that does not wipe the user data, you can achieve what you are trying to do, but if you choose the wrong firmware, you will probably lose your data.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
No, you can not recover the data via download mode, downloaded mode can only be used to flash the device.
You need to download the full stock firmware for your model number and flash it via Odin but when you flash it, if there are two different CSC files that can be used when you flash it, use the one that does not wipe user data during flashing then you will have access to your data once the device boots properly.
If you know or can find out what the build number is for the stock firmware that was on the device before you tried to modify it, you need to flash that exact build number.
If you flash something that is newer than the stock firmware that was already on the device, it might have an upgraded bootloader which means it would wipe your data when you flash that firmware.
If you are very careful in choosing the exact same firmware that you already had on the device and if you use the CSC file that does not wipe the user data, you can achieve what you are trying to do, but if you choose the wrong firmware, you will probably lose your data.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thank you so much for your help!