Database Info

[new odin](3.09.3)

We got a new version of ODIN-3 - (3/09/3)
Version came with firmware service for S4
http://4pda.ru/pages/go/?u=https://mega.co.nz/#!AUJGABDS!QHrlq0_jaUsqpi1lJNE8ggVgH-x-053kETte7ySzilk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
use please))
View attachment 2436518

I wonder what's different...
Sent from my SM-N9005 using Tapatalk

Where You see 3.9.3? I see Odin3 v3.09

<id:0/004> fail!
Hi Everyone!
This is my 1st post in any fourms ever. I always get solutions by searching, but i guess am umable to find a correct solution for this . Am hoping if someone could re-direct me to fix my phone.
Issue:
My screen is stuck on the boot screen ( Galaxy Note 2 N7100 - screen). It doesnt go further.
Background:
I was using Diamond ROM for quite a long time. I have no clue, last night i was talking to someone and later i kept my phone in pocket and since then its stuck on that screen. I am not sure what happened or what caused it
I am using Philz Recovery, but when am booting to it
it has the below Error:
PhilX Touch 6.26.6
Clockworkmod v6.0.4.8
E:Could not mount /data to setup /data/media path!
E:Can't mount /cache/recovery/command
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
I Tried everything possible (restarted may times, tried to wipe off the cache - it was not wiping)
Then i thought to reinstall PhilZ.
WHen i went to the download recovery on my phone and connected to odin v3.09 (which i used last time when installing custom ROM and it worked) phone is getting added.
But when i select AP to the PhilZ recovery file (philz_touch_6.26.6-n7100.tar.md5) and click on Start it is giving me error and it failed
Error:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.26.6-n7100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Someone Please Help me

ajithravi said:
Hi Everyone!
This is my 1st post in any fourms ever. I always get solutions by searching, but i guess am umable to find a correct solution for this . Am hoping if someone could re-direct me to fix my phone.
Issue:
My screen is stuck on the boot screen ( Galaxy Note 2 N7100 - screen). It doesnt go further.
Background:
I was using Diamond ROM for quite a long time. I have no clue, last night i was talking to someone and later i kept my phone in pocket and since then its stuck on that screen. I am not sure what happened or what caused it
I am using Philz Recovery, but when am booting to it
it has the below Error:
PhilX Touch 6.26.6
Clockworkmod v6.0.4.8
E:Could not mount /data to setup /data/media path!
E:Can't mount /cache/recovery/command
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
I Tried everything possible (restarted may times, tried to wipe off the cache - it was not wiping)
Then i thought to reinstall PhilZ.
WHen i went to the download recovery on my phone and connected to odin v3.09 (which i used last time when installing custom ROM and it worked) phone is getting added.
But when i select AP to the PhilZ recovery file (philz_touch_6.26.6-n7100.tar.md5) and click on Start it is giving me error and it failed
Error:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.26.6-n7100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Someone Please Help me
Click to expand...
Click to collapse
OK so 1st question, is debugging mode on? 2nd, have you tried another recovery? Cwm or twrp? 3rd) have you tried a factory reset? Do you have a backup? If so try to restore it, failing all of the above try to flash stock ROM via Odin (as long as debugging mode is on)
Sent from my GT-I9195

I use Odin 3.10.6
http://forum.xda-developers.com/showthread.php?t=2711451
N9005 HLTE:
Rom: Audax_L
Kernel: Fulgor
Recovery: TWRP

jimbomodder said:
OK so 1st question, is debugging mode on? 2nd, have you tried another recovery? Cwm or twrp? 3rd) have you tried a factory reset? Do you have a backup? If so try to restore it, failing all of the above try to flash stock ROM via Odin (as long as debugging mode is on)
Sent from my GT-I9195
Click to expand...
Click to collapse
Thanks for your kind response
So for the 1st one: Am not sure as my phone is not booting (It is stuck at Samsung Galaxy N7100 screen).
2nd: I tried to put another recovery via odin, it still didnt work ( got the same error as mentioned earlier)
3rd: In PhilZ recovery i tried all the possible options (wiping everything/factory reset but nothing works .... it gives Installation aborted .... or format aborted.....and above that it fails on opening the recovery path (E: )
and next:
I tried everything possible with the current recovery, but it fails on every step as its unable to access.
And i tried to flash it again with Odin, but it fails. I guess if am able to flash via Odin, the issue could be resolved. But itsays fail as mentinoed on the earlier error (under Odin error)
Hoping you could help me how to get another recovery installed or something.
---------- Post added at 07:51 PM ---------- Previous post was at 07:32 PM ----------
Ryya said:
I use Odin 3.10.6
http://forum.xda-developers.com/showthread.php?t=2711451
N9005 HLTE:
Rom: Audax_L
Kernel: Fulgor
Recovery: TWRP
Click to expand...
Click to collapse
Tried with all versions of Odin .... nothing worked

ajithravi said:
Thanks for your kind response
So for the 1st one: Am not sure as my phone is not booting (It is stuck at Samsung Galaxy N7100 screen).
2nd: I tried to put another recovery via odin, it still didnt work ( got the same error as mentioned earlier)
3rd: In PhilZ recovery i tried all the possible options (wiping everything/factory reset but nothing works .... it gives Installation aborted .... or format aborted.....and above that it fails on opening the recovery path (E: )
and next:
I tried everything possible with the current recovery, but it fails on every step as its unable to access.
And i tried to flash it again with Odin, but it fails. I guess if am able to flash via Odin, the issue could be resolved. But itsays fail as mentinoed on the earlier error (under Odin error)
Hoping you could help me how to get another recovery installed or something.
---------- Post added at 07:51 PM ---------- Previous post was at 07:32 PM ----------
Tried with all versions of Odin .... nothing worked
Click to expand...
Click to collapse
Sounds like debugging may be off which is stopping you flashing anything, have you tried downloading stock firmware?
Sent from my GT-I9195

Try to flash TWRP 2.6.0.1, before flashing pull the battery out of the phone for a good minute.
N9005 HLTE:
Rom: Audax_L
Kernel: Fulgor
Recovery: TWRP

galaxy j7 2016 SM-J710FN PROBLEM

Hi guys , good evening to all of you.
i have galaxy j7 sm-j710fn , the phone keep rebooting after ( samsung galaxy j7 (6) powered by android ) then few seconds and the phone restart again.
i tried to flash stock firmware by using odin , os 6.0.1 , everything is okay , flash done , but the same problem "" phone keep restarting ""
i when i try to access to stock recovery , a blue screen with a droid , and under the droid thing , it says : installing system update then Eraze ... then installing system update then Eraze , forever
i said , why i didn't install custom recovery , so i installed TWRP
when i try to wipe dalvik and cach and system or data a page of errors show's up
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
when go to mount it looks like all things are not mounted !!!!!!!!!!! thats why recovery can't spot the storage
help guys , what should i do ?

Maybe eMMC/Pit File problem
I no Nothing about this
So Wait for an expert

qounik said:
Maybe eMMC/Pit File problem
I no Nothing about this
So Wait for an expert
Click to expand...
Click to collapse
yes , i think its PIT FILE
but i did not find firmware with pit file for my phone

HACKIMTOSH said:
yes , i think its PIT FILE
but i did not find firmware with pit file for my phone
Click to expand...
Click to collapse
Search deep in Google
Maybe your luck will favour You
I once found Pit for my GT9192

qounik said:
Search deep in Google
Maybe your luck will favour You
I once found Pit for my GT9192
Click to expand...
Click to collapse
yeah, i'm trying so hard to find the pit file but the problem is samsung mobiles names are so closed to each other , even google goes crazy

help please anyone ? i'm trying but nothing

ODIN LOG
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> cm.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

I managed to something similar to my phone a while back. Only solution that i found was restoring the phone using Samsung Smart Switch app on PC. There are a few stepts the app tells you to do, after that it flashes the stock firmware, modem, recovery...evrything.

sesamo said:
I managed to something similar to my phone a while back. Only solution that i found was restoring the phone using Samsung Smart Switch app on PC. There are a few stepts the app tells you to do, after that it flashes the stock firmware, modem, recovery...evrything.
Click to expand...
Click to collapse
i tried it before ......... smart switch restore the phone and no error during Procedure
when the phone reboot , boom........same problem....keeep restarting
i need PIT file for this phone , anyone ?

Looks like you've flashed the wrong recovery to me.

ashyx said:
Looks like you've flashed the wrong recovery to me.
Click to expand...
Click to collapse
Don't we have only one recovery??? That official one TWRP?

qounik said:
Don't we have only one recovery??? That official one TWRP?
Click to expand...
Click to collapse
Is your device a J7 or ON8?
Please post the full specs of your device from the device itself.

Bravoo do not work......Why break the device?

S6 stuck on Samsung logo screen; Recovery mode = no, Odin mode = yes

I've got a Samsung Galaxy S6 (SM-G920F) which stucks on the Samsung logo screen after booting (Samsung Galaxy S6 powered by Android). I got it from a friend, he doesn't know what happened. Knox wasn't affected so it was just stock.
First I thought it was a dead battery because the phone didn't do anything. Only when the charger was connected, it would show a charging empty battery but no percentage. But after a hour in the charger I could boot into the Samsung logo where it get stuck (still no battery percentage however). I can also boot into download/odin mode. But I can't boot into recovery.
I already tried to flash the latest firmware for the S6 (PHN Netherlands G920FXXU6ERF5 https://www.sammobile.com/firmwares/galaxy-s6/SM-G920F/PHN/download/G920FXXU6ERF5/226355/) but that didn't help. It still doesn't boot and I still can't boot into recovery. Should I use some other options in Odin?
I also tried to flash TWRP, but even then I can't boot into recovery.
Flashing both stock firmware and TWRP give no error in Odin.
I found this guide:
https://forum.xda-developers.com/galaxy-s6/help/guide-downgrade-sm-g920f-nougat-to-t3639253
I want to try this, but I already get stuck in step 5.
5. Open SkipSoft Android Tool Kit and wait until you see the main menu. Then go to the installation folder of this tool and you should see an "INPUT" folder. Copy ONLY the boot.img, cache.img, recovery.img and system.img into that folder.
Click to expand...
Click to collapse
When I go to the installation folder (I'm not on the computer right now, something in C:\Program Files\nameofprogram ) there is no INPUT folder.
And in step 6, on my screen there is no option for 99. I got something like this: (picture is from google, not exactly what I got. But almost the same)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I don't know what these steps do. Can't I just make the flashable file with winrar or 7zip or something?
Are there other options I can try? What can cause this behavior? Is it a faulty bootloader? If so, can't I just reflash just the bootloader?
Maybe I should try to flash 5.0.2 or 5.1.1, but I can't find these files on sammobile and updato.com. I found the original url to sammobile but those aren't working anymore:
5.0.2: G920FXXU1AOE3 G920FPHN1AODQ PHN
http://www.sammobile.com/firmwares/download/47427/G920FXXU1AOE3_G920FPHN1AODQ_PHN/
5.1.1: G920FXXU2BOGB G920FPHN2BOG8 PHN
http://www.sammobile.com/firmwares/download/52406/G920FXXU2BOGB_G920FPHN2BOG8_PHN/

Or can someone help me to get the 5.0.2 and/or 5.1.1 files for the G920F?

Typing 99 in the menu worked for me. Even though I also didn't see the corresponding option. It seems to be an update command, downloading the latest packages of adb, adb-fastboot and magisk.
Can you verify that you tried starting recovery mode IMMEDIATELY after flashing the TWRP? The original system seemed to override any changes, if you give it the chance to reboot normally.

Yes I tried TWRP with auto-reboot in Odin and immediately press VOL_UP+POWER+HOME after auto reboot. And TWRP with auto-reboot unchecked. So flash TWRP, force reboot with VOL_DOWN+POWER+HOME switch to VOL_UP+POWER+HOME before the Samsung logo appears. Bot both methods won't let me boot into recovery.

When I try to flash this rom:
G920FXXU3DPBG_G920FPHN3DPB2_PHN
I get this error in Odin (tried v3.10.6 and v3.12.4_4)
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU3DPBG_G920FPHN3DPB2_G920FXXU3DPB6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> cm.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Why?
Phone says:
Code:
[CM] SW REV. CHECK FAIL. DEVICE: 6, BINARY: 3

Hi,
Were you able to figure out what the issue was? I'm in the exact same situation and have tried similar things with no success. I've kind of given up on it being a software issue at this point..

Nope, I'm going to sell it for parts.

Markos said:
Nope, I'm going to sell it for parts.
Click to expand...
Click to collapse
This happened to me after trying to get unstuck from a bootloop. I think I solved it by flashing it again a couple more times. And I remember it taking quit a while to actually boot up when it finally did.

I already flashed it a lot of times. Both original firmware as TWRP. Nothing helped.
I wanted to try early stock rom but can't find downloads

Markos said:
Or can someone help me to get the 5.0.2 and/or 5.1.1 files for the G920F?
Click to expand...
Click to collapse
I just want to suggest the SamMobile. Hahaha.

heidisteen said:
I just want to suggest the SamMobile. Hahaha.
Click to expand...
Click to collapse
As I said, they don't have it anymore

Markos said:
As I said, they don't have it anymore
https://youtu.be/zXSHe3oorIM
Click to expand...
Click to collapse
I found a video about fixing Samsung Galaxy Android system issues, sound helpful with you.

Samsung Gear S2 Classic is Stuck On Update Loop

I've flashed the R732XXU2AOJ3 firmware form this link https://forum.xda-developers.com/smartwatch/gear-s2/tutorial-downgrade-gear-s2-sport-t3334123 using Odin v3.13.1 and the USB method because the WiFi option in the bootloader was damaged. The watch started properly and I could connect to it with my phone and the damaged connection with the WiFi option in the bootloader was fixed as well.
The Samsung phone app suggested an update (I don't remember the version). After going through the update process the watch has restarted itself and performed the 0 to 100% update step. After reaching the 100% it just shuts down, every time I turn it on it goes again through the update process
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and shuts down.
Using the normal bootloader factory reset doesn't work and the phone it stuck on the boot logo when using that. Now even if I flash the R732XXU2AOJ3, R732XXU2AOJ4 or the R732XXU2EQH1 firmware successfully using NetOdin3 I’m still stuck on the update process as shown here . I've tried flashing using the AP, BL and CSC files and also using AP, BL, CSC and PIT files, the watch was always updated with its official stock firmware.
Those are my set NetOdin3 options for the flash:
And this is the flash log:
Code:
<ID:0/001> 192.168.49.1
<ID:0/001> Odin engine v(ID:1.0000)..
<ID:0/001> File analysis..
<ID:0/001> SetupConnection..
<ID:0/001> Initialzation..
<ID:0/001> Set PIT file..
<ID:0/001> DO NOT TURN OFF TARGET!!
<ID:0/001> Get PIT for mapping..
<ID:0/001> Get PIT Transmission
<ID:0/001> Firmware update start..
<ID:0/001> SingleDownload.
<ID:0/001> zImage-recovery
<ID:0/001> NAND Write Start!!
<ID:0/001> sboot.bin
<ID:0/001> param.bin
<ID:0/001> zImage
<ID:0/001> modules.img
<ID:0/001> user.img
<ID:0/001> system-data.img
<ID:0/001> ramdisk-recovery.img
<ID:0/001> ramdisk.img
<ID:0/001> rootfs.img
<ID:0/001> csc.img
<ID:0/001> RQT_CLOSE !!
<ID:0/001> RES OK !!
<ID:0/001> Remain Port .... 0
<ID:0/001> Removed!!
<OSM> All threads completed. (succeed 1 / failed 0)

Idea 1...
Flash Combination Firmware... to check if SM-R732 boot
Idea 2...
No idea why you started with Odin... so my first idea is... Live Demo Unit ?
SM-R732X
Idea 3.
Few threads about dead devices...
Still no idea why you flashed with Odin
Idea 4...
If you have enough time... I could help you to dump Log files from device...
Maybe this answer why fail...
Best Regards
Edit 1...
By mistake saw your tiny Pic... clicked weired around...
Those are my set NetOdin3 options for the flash
Click to expand...
Click to collapse
Re-partition
No idea if this is good idea...
So I really suggest you to flash Combination Firmware...
Hint... Be carefully not to use LDU Firmware... with 1 more X in Filename...
R732XX :good:
R732XXX :cyclops:
Best Regards

adfree said:
Idea 1...
Flash Combination Firmware... to check if SM-R732 boot
Idea 2...
No idea why you started with Odin... so my first idea is... Live Demo Unit ?
SM-R732X
Idea 3.
Few threads about dead devices...
Still no idea why you flashed with Odin
Idea 4...
If you have enough time... I could help you to dump Log files from device...
Maybe this answer why fail...
Best Regards
Edit 1...
By mistake saw your tiny Pic... clicked weired around...
Re-partition
No idea if this is good idea...
So I really suggest you to flash Combination Firmware...
Hint... Be carefully not to use LDU Firmware... with 1 more X in Filename...
R732XX :good:
R732XXX :cyclops:
Best Regards
Click to expand...
Click to collapse
Thank you for the response I thought the post will never get any attention. I flashed with Odin the first time because the device was stuck on the logo and I couldn’t rest it. After the first flash using the R732XXU2AOJ3 I could start the watch and use it normally. The problem occurred after I tried to install an official update though the Galaxy Wearable app. I don’t know if I can get any logs from the watch since the debugging is not enabled so a connection with sdb is not an option, I can ping the local IP addres of the watch with CMD .
Do you know any working free links to some Combination Firmware for the SM-R732? The model says SM-R732 so I don't think that it is a live demo unit. I have the R732XXU2AOJ3, R732XXU2AOJ4, R732XXU2AOJD, R732XXU2EQC1 and R732XXU2EQH1 and I thought that they all were Combination Firmware.
Update 1:
I've flashed this Combination Firmware COMBINATION-FTMA_R732XXU2AOJ2.tar.md5 successfully. The watch started with the problematic 0-100% update process on boot and shut down after reaching 100%.
Is there any difference between flashing with Odin and USB and flashing with NetOdin and Wi-Fi?

Is there any difference between flashing with Odin and USB and flashing with NetOdin and Wi-Fi?
Click to expand...
Click to collapse
I have never tried Re-Partiblabla Setting... and according to Samsung Documents... in theory netOdin can NOT do this...
I mean Doc in this Package...
https://forum.xda-developers.com/showpost.php?p=73503787&postcount=150
You were able to find ""latest"" FRC1 Firmware for Download?
Maybe stupid Securtiy sh... or Bug or..
Best Regards

adfree said:
I have never tried Re-Partiblabla Setting... and according to Samsung Documents... in theory netOdin can NOT do this...
I mean Doc in this Package...
https://forum.xda-developers.com/showpost.php?p=73503787&postcount=150
You were able to find ""latest"" FRC1 Firmware for Download?
Maybe stupid Securtiy sh... or Bug or..
Best Regards
Click to expand...
Click to collapse
Yes, I've found the FRC1 Firmware, I didn't know it was the "latest". If you want it I can upload it and give you a download link in a PM.
Best regards

adfree said:
I have never tried Re-Partiblabla Setting... and according to Samsung Documents... in theory netOdin can NOT do this...
I mean Doc in this Package...
https://forum.xda-developers.com/showpost.php?p=73503787&postcount=150
You were able to find ""latest"" FRC1 Firmware for Download?
Maybe stupid Securtiy sh... or Bug or..
Best Regards
Click to expand...
Click to collapse
It is wired. When I flash with NetOdin then the flash succeeds but when I use ODIN + USB then it fails with:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 908 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The Re-Partition setting is not set and I understood that it is not supposed to be set. In both cases of NetOdin and Odin + USB I've used the COMBINATION-FTMA_R732XXU2AOJ2.tar.md5

Remove partition.pit from TAR... repack...
1 way is with 7Zip tool to create valid TAR file...
In case of 3 file crap... AP BL CSC bla bla crap...
partition is inside CSC file...
In normal working Gear no PIT file necessary...
Best Regards

adfree said:
Remove partition.pit from TAR... repack...
1 way is with 7Zip tool to create valid TAR file...
In case of 3 file crap... AP BL CSC bla bla crap...
partition is inside CSC file...
In normal working Gear no PIT file necessary...
Best Regards
Click to expand...
Click to collapse
I ended up removing all the files causing the fail message until I was left with no files at all .

A
Odin Version?
B
Try to flash only this param file...
Try both... Odin and netOdin...
Hope to enable Upload in Reboot menu... to use RDX Tool...
https://forum.xda-developers.com/showpost.php?p=72110199&postcount=45
Best Regards
Edit 1.
I mean menu like this:
Code:
[B]REBOOT MODE[/B]
Continue
[B]Upload[/B]
[B]Upload (wireless)[/B]
Download
Download (wireless)
Factory command
Recovery
PowerOff

adfree said:
A
Odin Version?
B
Try to flash only this param file...
Try both... Odin and netOdin...
Hope to enable Upload in Reboot menu... to use RDX Tool...
https://forum.xda-developers.com/showpost.php?p=72110199&postcount=45
Best Regards
Edit 1.
I mean menu like this:
Code:
[B]REBOOT MODE[/B]
Continue
[B]Upload[/B]
[B]Upload (wireless)[/B]
Download
Download (wireless)
Factory command
Recovery
PowerOff
Click to expand...
Click to collapse
A. Odin v3.13.1 and NetOdini v1.0
B. Odin shows fail and NetOdin shows success
The extended menu doesn't appear .
Best Regards

Maybe you are out of luck...
Look here:
https://forum.xda-developers.com/smartwatch/gear-s2/fail-to-hard-softreset-t3746359
https://forum.xda-developers.com/smartwatch/gear-s2/gear-s2-wont-perform-factory-reset-t3737448
It is not 100 % sure to me... if really eMMC damaged... (Hardware)... or some Security crap enabled... and write protect eMMC...
Sorry, I have no solution nor more ideas to try... :crying:
Best Regards

Development [AOSP-11] [OFFICIAL] Samsung SM-A125F TWRP

DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS
Install instructions:
1. Download an arbitrary SM-A125F firmware zip package on SamMobile.com, whose Android version is 11. I used A125FXXU2BVB4 firmware.
2. Clean install firmware (means, no magisk boot module, etc. Flash with ODIN full firmware (BL, AP, CP and CSC _A125FXXU2BVB4*.TAR.MD5. Tick in ODIN options: NAND ERASE; Re-partition. Make sure AUTO REBOOT is OFF!!!
3. Let ODIN flash all, on completion, click reset, disconnect and connect USB, Select recovery.img (below post) in AP slot, and nulled VBMETA.img (below) in USERDATA slot. again; Make sure AUTO REBOOT is OFF!!!
4. Let ODIN flash all. Once all succeeded; Hold <VolDn> + <Power> to shut down, then Hold <VolUp> + <Power> to reboot to TWRP
5. Once TWRP has booted, do full factory reset (wipe caches and data). After that, format data completely. Reboot to recovery once done.
6. Once TWRP has re-booted, go to advance, terminal and execute command: multidisabler.
This will protect data partition from becoming encrypted again, and secure recovery partition from being replaced.
7. Reboot to system, and setup device as normal. After this, you could install Root or what ever you want.
Important: device must boot directly to recovery or stock recovery will be restored if you boot direct to OS.
8. Enjoy!
What is working:
Mounting, flashing *.img to superpartitions, MTP also fixed now.
What is not working:
ADB sideloading;
You tell me...
Samsung Galaxy A12
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Device tree: https://github.com/edward0181/android_device_samsung_a12
Kernel tree: https://github.com/00p513-dev/android_kernel_samsung_a12

10/05/2022
Rebuild kernel to fix issues with dynamic partitions. Backups and flashing img now doesn't break twrp and doesn't reboot anymore.
17/04/2022
Updated with latest FSTAB issues.
Will fix not being able to flash GSI to system partitions etc.
Will be online in TWRP.ME downloads soon, but below post is most recent.
https://eu.dl.twrp.me/a12/ Can be flashed from current recovery (TWRP) as IMG into recovery slot.
12/04/2022
Rebuild from A125FXXU2BVB4 firmware. Updated kernel to custom kernel. Modified FSTAB points to flash *.IMG files to dynamic partitions. Fixed FBE decryption of data partition.
04/10/2021
Updated to fix being able to install GSI in system-image partition. See below post
15/09/2021
* Fixed MTP, mount points of Dynamic_Partitions. All is working now, except Decrypting. As mentioned earlier, not important now as you can use OTG, or External_SD or MTP.
15/09/2021
* Redid whole tree, fixed partition errors. Works as system_root.
* FSTAB fixed
Still data decrypt issues, MTK is a pain... not important now, when using external_sd
20/08/2021
* Fixed FSTAB issues.
* Fixed Sideload and ADB issues
* Mounts of partitions fixed
Still to do: Decryption of DATA partition failing as soon as stock ROM is factory resetted. WIP.
09/08/2021
Initial entry; decrypt isn't working.
Is still Work in Progress.
to be updated

For those who wants to install GSI, etc:
Boot to recovery, flash IMG and select what partition you want to flash to.
No need for aditional tools with latest update.

And for the a125M?: ((

Elholas said:
And for the a125M?: ((
Click to expand...
Click to collapse
Both run on same hardware. Test and you tell me hihi. I only have A125F to test.

But will that not generate an error when flashing or could it damage the cell phone? I'm not sure

edward0181 said:
Both run on same hardware. Test and you tell me hihi. I only have A125F to test.
Click to expand...
Click to collapse
But will that not generate an error when flashing or could it damage the cell phone? I'm not sure

edward0181 said:
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS
Install instructions:
1. Download an arbitrary SM-A125F firmware zip package on SamMobile.com, whose Android version is 11
2. Flash by Heimdall by PIT partitions or by Odin by BL, AP, CP, and CSC tar packages
3. Back to the stock ROM > go to Developments settings > allow OEM unlocking (Developments settings could be enabled by tapping 7~10 times somewhere in About Device)
4. If OEM unlocking is unseen to you, take software updates first
5. Also inside Developments settings, enable USB debugging
6. Download the TWRP image, and unzip.
7. Hold <VolUp>+<VolDn> with device tethered to USB-C with your PC
8. Hold <VolUp> to unlock OEM
9. Hold <VolUp>+<VolDn> again with device not disconnected of USB-C
10. Press <VolUp> without holding to enter Download mode
11. Open ODIN to flash the downloaded TWRP in AP slot with my TWRP image.
12. Hold <VolDn> + <Power> to shut down, then Hold <VolUp> + <Power> to reboot to TWRP
Important: device must boot directly to recovery or stock recovery will be restored if you boot direct to OS.
13. Enjoy!
What is working:
Mounting, flashing, sideloading.
What is not working:
Decrypting USERDATA
You tell me...
Device tree: https://github.com/edward0181/android_device_samsung_a12
Click to expand...
Click to collapse
Any pictures of the twrp it self? I'm curently testing something on android 10 and I don't want to revert back to android 11 yet.
Thanks.

LAST_krypton said:
Any pictures of the twrp it self? I'm curently testing something on android 10 and I don't want to revert back to android 11 yet.
Thanks.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

will can i flash gsi roms using this twrp?

Yes You can flash roms.

Idk what I'm doing wrong but when I flashed twrp image through odin I just get to the samsung secured by knox with a normal warring that I'm not using samsungs official software. I'm going to try something else.

Never mind, just held vol up for a min and it works.

LAST_krypton said:
Idk what I'm doing wrong but when I flashed twrp image through odin I just get to the samsung secured by knox with a normal warring that I'm not using samsungs official software. I'm going to try something else.
Click to expand...
Click to collapse
Remove tick auto reboot, flash with odin. Once done disconnect usb and hold power and vol down till black screen. Release and direct vol up and power till you get into twrp.

edward0181 said:
Remove tick auto reboot, flash with odin. Once done disconnect usb and hold power and vol down till black screen. Release and direct vol up and power till you get into twrp.
Click to expand...
Click to collapse
For me it wount boot in to twrp untill i flash the vbmeta.

It installs like any twrp, right? I installed android 11 by Odin and my question was if it only put the image in AP to have the twrp, and in that case, all rom gsi are compatible?

LAST_krypton said:
For me it wount boot in to twrp untill i flash the vbmeta.
Click to expand...
Click to collapse
Could be. I’ve pre rooted my device with magisk to overcome this

edward0181 said:
Could be. I’ve pre rooted my device with magisk to overcome this
Click to expand...
Click to collapse
Yea, just tested you need to flash a vbmeta or pre disable dm-verity

<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1207)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> RQT_CLOSE !!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
:c

Elholas said:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1207)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> RQT_CLOSE !!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
:c
Click to expand...
Click to collapse
Is that on the A125M ?