Database Info

SM-G920 LIVE DEMO UNIT won't boot.

It stays on the booting screen flashing. "Samsung galaxy s6 live demo unit". I can't get it to boot hence can't set the usb debugging on to flash another firmware. What is there to do ?
EDIT: Managed to enter recovery mode and clear cache + do a factory reset. That not only did not solve anything but now i can't get into recovery or download mode at all. That "Samsung galaxy s6" thing flashes only when the phone is charging !
Alright, it has to be charging in order to get into recovery/download mode. Now, what shall i do ? What ROM should i flash since this is a SM-G920X ? Please help me, i couldn't find any useful information on google. Even if there was a suitable firmware to flash, the device is not recognized in odin. What shall i do ?

I had some problems with my account and i had to post from that other one. I downloaded samsung drivers and the phone is now recognized in odin but i cant flash the sm-g920 firmware, it fails just on start. Please help me out of this.
EDIT : FOUND THIS http://forum.xda-developers.com/galaxy-s6/general/g920x-master-thread-guides-firmwares-t3267738 . I think it will be a great help.
Alright, i tried flashing that verified ready-to-flash ROM that was provided there and it failed at around 40%. Now i cant flash it again, it stay locked at
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
I dont know what to do next.

<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Second time it fails.. I dont know why.
---------- Post added at 09:05 PM ---------- Previous post was at 08:42 PM ----------
I flashed that ready-to-go ROM successfully and now it boots further to that "welcome" screen but i encounter a big yellow triangle with an black exclamation mark in middle and a 'dead' android bot behind it. What should i do next ?
IMPORTANT NOTE : The phone won't show any kind of life unless it's CHARGING.
Can anyone really help me a little, what's up with this device ? Should i hope or try any further cause i really dont know what to do

Everything you guys need to know to get off the mess you created is here in this thread.
http://forum.xda-developers.com/galaxy-s6/general/g920x-master-thread-guides-firmwares-t3267738
Read and make sure you know what you're dealing with first, then start flashing ROMs!
I noticed the link was already found and posted by the OP in a later edit. Thanks.
One more thing i wanted to add is you can only flash a ROM that matches with your bootloaders. Since the LDU bootloader is Android 5.1.1 at the latest, you cannot flash Android 6. I suggest, if you manage to update bootloaders from 5.0.1 to 5.1.1, getting the latest 5.1.1 from sammobile, removing the *.bin files, and flash in ODIN.
Sent from my SM-G920F using XDA-Developers mobile app

Thanks god someone is willing to help me out of this ! I read the entire thread multiple times and i really really want to get out of this mess.
I took that ready-to-go ROM he provided there cause of the fact alone i have no clue what a unix machine is hence i can't remove these .bin files listed there. Also, i have no clue what bootloader this phone has or what that means in the first place, but i flashed a 5.1.1 one ( I guess) that i found on that thread successfully.
I would be extremely grateful if you could help me remove these files on my own or provided a 5.1.1 rom with these files removed.
Pure curiosity. Why does the phone 'play' dead when i'm trying to power it while not being charged ?
---------- Post added at 11:18 PM ---------- Previous post was at 10:20 PM ----------
Meh.. i seem to cant flash any ROM anymore. It would just fail mid-process saying "Removed".

Well if you're a windows user you can install Cygwin and use the commands, if you're a MAC user just open up terminal and use:
- to rename the md5 file to tar for unpacking:
mv filename.tar.md5 filename.tar
- to untar (extract) the tar file:
tar -xf filename.tar
- delete the .bin files:
rm *.bin
- repack the .img files into a tar:
tar -cf newfilename.tar *.img
- create md5:
md5sum -t newfilename.tar >> newfilename.tar
- add the md5 file extension so ODIN will recognize it:
mv newfilename. tar newfilename.tar.md5
now you have your "newfilename.tar.md5" to load into the "AP" of your ODIN and flash it.
I've zipped the one I just made while I typed up the commands in cygwin for you to make sure they worked. Uploading, but it's going to take a while. I will check back in ~hour to see if it timed out or not.
Ok download it, unzip it, and load the "G920FXXU3COI9_G920FXEU3COJ2_G920FXXU3COI9.tar.md5" in the AP segment of Odin. Try it first and if it didn't work again, since you've done multiple flashes, it won't be a bad idea to check "nand erase all" one time in ODIN options.
Link removed. Please use link in my next post.

Im extremely grateful for your help, i will try to flash this one and if it won't work i'll check nand erase. I guess i can't screw it more than it already is.
EDIT : No success flashing either way.
---------- Post added at 06:05 AM ---------- Previous post was at 05:50 AM ----------
<ID:0/004> Added!!
<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> Erase...
<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> hidden.img
<ID:0/004> modem.bin
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<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> hidden.img
<ID:0/004> modem.bin
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<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>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
That's a log, 3 flash attempts in a row, different messages though.
In that g920x master thread it is said so " The only preparation required is the removal of the modem, bootloader, PIT, and related partitions.". I couldn't help but realize that while the flash was going on it still went through modem.bin, is that alright ? I have no idea myself, just trying to figure out why i can't this damned thing to work.

Ah I see the modem file in there. Sorry about that, although it seems that it flashed just fine. I would think the modem file will be there but not get used. But at any rate, I've redone the whole process from the original factory file, and i'm uploading now, no bin files this time! ETA 35 minutes ...
https://drive.google.com/open?id=0B31Omryqpl4nd2NLTG5nY3JxUk0

It still won't flash. I don't know what to do next.

Commodore 64 said:
Well if you're a windows user you can install Cygwin and use the commands, if you're a MAC user just open up terminal and use:
- to rename the md5 file to tar for unpacking:
mv filename.tar.md5 filename.tar
- to untar (extract) the tar file:
tar -xf filename.tar
- delete the .bin files:
rm *.bin
- repack the .img files into a tar:
tar -cf newfilename.tar *.img
- create md5:
md5sum -t newfilename.tar >> newfilename.tar
- add the md5 file extension so ODIN will recognize it:
mv newfilename. tar newfilename.tar.md5
now you have your "newfilename.tar.md5" to load into the "AP" of your ODIN and flash it.
I've zipped the one I just made while I typed up the commands in cygwin for you to make sure they worked. Uploading, but it's going to take a while. I will check back in ~hour to see if it timed out or not.
Ok download it, unzip it, and load the "G920FXXU3COI9_G920FXEU3COJ2_G920FXXU3COI9.tar.md5" in the AP segment of Odin. Try it first and if it didn't work again, since you've done multiple flashes, it won't be a bad idea to check "nand erase all" one time in ODIN options.
Link removed. Please use link in my next post.
Click to expand...
Click to collapse
Help me figure out the exact commands i have to type in cygwin for a filename. What do i have to do to let that terminal know where my file is located, cause i guess you have to mention the location.
Just write the exact command i have to write with the "Filename.tar" in cygwin while filename is located on desktop.
By the way, im requesting them cause i tried the commands you provided and i can't figure out how to use them.
"[email protected] ~
$ tar --delete --file[AP_G920XZCU1BOI2_LLK_CL5369277_QB6240453_REV02_user_low_ship] hidden.img
tar: unrecognized option '--file[AP_G920XZCU1BOI2_LLK_CL5369277_QB6240453_REV02_user_low_ship]'
Try 'tar --help' or 'tar --usage' for more information.
[email protected] ~
$ tar --delete--file[AP_G920XZCU1BOI2_LLK_CL5369277_QB6240453_REV02_user_low_ship] hidden.img
tar: unrecognized option '--delete--file[AP_G920XZCU1BOI2_LLK_CL5369277_QB6240453_REV02_user_low_ship]'
Try 'tar --help' or 'tar --usage' for more information.
"

I typed the exact commands for you already. I put each command under the line that starts with a dash - which tells you what that following command is doing.
Did the file flash and go through on Odin? You probably know you need to reboot the phone freshly back to download mode every time it is connected to Odin or else you'll get a flash error. So open Odin put phone in DL mode and connect USB. If you disconnect USB, you shouldn't just plug it back in, you'll need to reboot the phone into DL mode again!
I think what it is about Cygwin that you're struggling with is that, cygwin isn't given permission to go out of its own folder environment and edit files in other places, such as your desktop. That is a good thing and we wanna keep it that way for security reasons so you don't accidentally damage the OS or delete other files/folders.
So what you'll do is copy the file you want to manipulate by cygwin to home directory of cygwin, and then it will see it and be able to edit it. Something like c:\cygwin\home\[Windows Username] depending on where you installed Cygwin. And yes you can change its home directory to somewhere else on your PC, but that is really not with in the scope of this thread.
Sent from my SM-G920F using XDA-Developers mobile app

Commodore 64 said:
I typed the exact commands for you already. I put each command under the line that starts with a dash - which tells you what that following command is doing.
Did the file flash and go through on Odin? You probably know you need to reboot the phone freshly back to download mode every time it is connected to Odin or else you'll get a flash error. So open Odin put phone in DL mode and connect USB. If you disconnect USB, you shouldn't just plug it back in, you'll need to reboot the phone into DL mode again!
I think what it is about Cygwin that you're struggling with is that, cygwin isn't given permission to go out of its own folder environment and edit files in other places, such as your desktop. That is a good thing and we wanna keep it that way for security reasons so you don't accidentally damage the OS or delete other files/folders.
So what you'll do is copy the file you want to manipulate by cygwin to home directory of cygwin, and then it will see it and be able to edit it. Something like c:\cygwin\home\[Windows Username] depending on where you installed Cygwin. And yes you can change its home directory to somewhere else on your PC, but that is really not with in the scope of this thread.
Sent from my SM-G920F using XDA-Developers mobile app
Click to expand...
Click to collapse
I am a total noob. I cant figure it out really, it may be your way of explaining too but i cant. Just do that, write the exact command you write to remove hidden.bin from the "Filename.tar" which is located in cygwin local director.
---------- Post added at 06:05 PM ---------- Previous post was at 05:54 PM ----------
Commodore 64 said:
Well if you're a windows user you can install Cygwin and use the commands, if you're a MAC user just open up terminal and use:
- to rename the md5 file to tar for unpacking:
mv filename.tar.md5 filename.tar
- to untar (extract) the tar file:
tar -xf filename.tar
- delete the .bin files:
rm *.bin
- repack the .img files into a tar:
tar -cf newfilename.tar *.img
- create md5:
md5sum -t newfilename.tar >> newfilename.tar
- add the md5 file extension so ODIN will recognize it:
mv newfilename. tar newfilename.tar.md5
now you have your "newfilename.tar.md5" to load into the "AP" of your ODIN and flash it.
I've zipped the one I just made while I typed up the commands in cygwin for you to make sure they worked. Uploading, but it's going to take a while. I will check back in ~hour to see if it timed out or not.
Ok download it, unzip it, and load the "G920FXXU3COI9_G920FXEU3COJ2_G920FXXU3COI9.tar.md5" in the AP segment of Odin. Try it first and if it didn't work again, since you've done multiple flashes, it won't be a bad idea to check "nand erase all" one time in ODIN options.
Link removed. Please use link in my next post.
Click to expand...
Click to collapse
Wow, im unbelievably dumb. I just figured out ! You wrote the commands i have to use, one by one. Im so ashamed of myself now. I thought there are some commands i could use not at all they are meant to be used in that order, im so sorry for wasting your time.
I'm afraid i'll still have to bother you one more time
$ tar -xf AP_G920XZCU1BOI2_LLK_CL5369277_QB6240453_REV02_user_low_ship.tar
tar: AP_G920XZCU1BOI2_LLK_CL5369277_QB6240453_REV02_user_low_ship.tar: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
Steps i went through : 1. moved the ROM to C:\cygwin64\filename.tar (renamed it manually, not via command)
2. Wrote tar -xf filename.tar and i got that error you can see there.
---------- Post added at 06:10 PM ---------- Previous post was at 06:05 PM ----------
I GOT IT RIGHT, GOD. I am really sorry to waste your time. Finally, i understood, i read it all once again and i understood. I had to copy the tar file to cygwin64/home/User/. I am extremely grateful and i hope i will get my device to work.
I'm really sorry you had to dealt with such a noob though. I thank you again for your help.

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?

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

Not sure what kind, but my N8010 is bricked.

I picked up a 2nd hand n8010 a LONG while back, back when they were still relevant.
I had been using it peacefully, on all stock software the way i got it, and had upgraded my phone, so i left it off for a long while, about a year or two now. Just yesterday, I decided to fully charge and open it. So far so good.
Then the bootlogo shows up. It started looping, black screen, wait a bit, back to logo until battery dies.
I decided to leave it be for a bit charged. Still nothing, so i decided to enter recovery mode, but nothing happened. The backlight DOES flash for a second or two, but then it's back to the bootlogo shenanigans.
Now i have noticed after fully charging the device, it just stays stuck on the bootlogo, without flashing or looping. It is open right now.
I tried to flash TWRP 2.8.6.0 for GT-N8010, log says it succeeded, but there is nothing:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1205)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> efs.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/004> Added!!
I tried to flash a stock rom. It was a turkish N8010, So i picked up TUR-N8010XXUCMG1-2013101145051. Here is the failed repartition log:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1205)..
<ID:0/003> File analysis..
<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)
I have also tried to reflash a PIT file. Same repartition fail error. Weird thing to note is that while the device IS a 8010, the Odin Mode shows N8005 but i have no clue why.
One more thing to note: not booting to anything for ~5 minutes makes windows prepare SAMSUNG Device drivers, and shows on Device Manager as an MTP device.
Other than that I have tried
Flashing the following roms for diversity: XSG-N8010XXUDNF3-20141017163909 & N8010XXUCMK2 (no date)
Flashing I9300_Repair_efs.tar
Using device's own PIT, and the infamous Note10_PIT.zip copy from a N8000
Using Odin 3.12, 3.14.1 and 3.13.1, and trying all of the above reflash steps with each version
I'm okay with wiping everything, I have 0 important data left in it.
If i missed anything please ask, i will reply as soon as possible! I want to know how to solve if possible, or if my nand is gone

Fail on PIT often wrong size 16gb / 32 gb firmware used .

JJEgan said:
Fail on PIT often wrong size 16gb / 32 gb firmware used .
Click to expand...
Click to collapse
So i should find firmware for my 16gb model?
Recovery doesnt flash either, it just does RQT_CLOSE and takes 00:01 second to flash so it isnt actually flashing... When i reboot into recovery it goes black screen as i mentioned
I'll try look for firmware for my particular model, thank you

UPDATE: I found another pit. its for n8010 16gb, still the same PIT error.
I also tried TUR N8010XXUDNF3_N8010OJVDNF3-20140614 which is also tz.img fail.
I tried all of the above again with Odin 3.09, also same result except for TWRP.
TWRP now "flashes" and takes time to flash, like it's supposed to be. But booting to recovery still is a black backlight.

which is also tz.img f
You flash TAR through Odin not IMAGE .

JJEgan said:
which is also tz.img f
You flash TAR through Odin not IMAGE .
Click to expand...
Click to collapse
But i am, i am flashing .tar.md5, i do not extract. The log just shows tz.img before failing.
{
"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"
}
If you mean .tar.gz, i also tried renaming and it outright didnt work.
I never extract .tar files while flashing, unless if its twrp.

Are you using the Original Samsung USB cable you should .
You could find Philz Recovery on here flash that and then use it to update to TWRP .

Hello, i have 2 original cables. One that came with the box and one that i bought off of an official samsung store. Just in case the one i purchased was problematic, I found the one that came with the box, and tried it.
The issue persisted, so i do not think i have a problem there.
I did get a version of philz recovery and try to flash it, but it was the same was TWRP. Flashed as normal, I went to recovery, it gave black screen for 1-2 seconds, reboot.
I'm starting to believe I have a hardware failure. I dont think it would flash and still not work if it werent broken.
Thanks for sticking with me. If you have any more suggestions i am willing to try. But worse come to worse i will replace the motherboard and try an emmc replacement on the dead board as practice.
Just one question: Is it possible that i could trick the bootloader to booting from ExtSD? Maybe if EMMC is dead, i could boot from my 8gb microsd.

Bad emmc usually posts in Odin as Nand fail .

Question Can't install combination file on A12 through Odin

I have an A12 phone that I'm trying to install a combination file on. I've been struggling with it for quite a few days now, and I absolutely have no clue what I should do to get it working.
Here's the log from Odin:
<ID:0/008> Odin engine v(ID:3.1401)..
<ID:0/008> File analysis..
<ID:0/008> Total Binary size: 2766 M
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> preloader.img
<ID:0/008> lk-verified.img
<ID:0/008> param.bin
<ID:0/008> up_param.bin
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
After the attempt, it says on the phone - "Please get the approval to use factory binaries: param.
The combination file version I use is:
COMBINATION_FAC_FAQ0_A125FXXU1AUD3_FACFAC_CL21597094_QB39823247_REV00_user_mid_noship_MULTI_CERT
The pit file I used is A12_EUR_OPEN.pit.
Binary of my A12 is U1.
I need to install the combination file because I don't have access to the Google account tied to this phone.
Will be much grateful for any help... thank you.

Does download mode output anything? And if you could please share the combination file.

LAST_krypton said:
Does download mode output anything? And if you could please share the combination file.
Click to expand...
Click to collapse
"COMBINATION_FAC_FAQ0_A125FXXU1AUD3_FACFAC_CL21597094_QB39823247_REV00_user_mid_noship_MULTI_CERT" that's the combination, or do you want me to upload it somewhere?
Here's what I've got from download mode:
{
"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"
}

Unlock the bootloader, re flash the fimware to get rid of the perenormal state then flash combination file.

LAST_krypton said:
Unlock the bootloader, re flash the fimware to get rid of the perenormal state then flash combination file.
Click to expand...
Click to collapse
Sorry for asking, but how to do that if the phone is FRP locked? Thank you

xt123xt said:
Sorry for asking, but how to do that if the phone is FRP locked? Thank you
Click to expand...
Click to collapse
Use sp flah to flash new fimware so you can unlock the bootloader

LAST_krypton said:
Use sp flah to flash new fimware so you can unlock the bootloader
Click to expand...
Click to collapse
Sorry, never used sp flash tool before. Is there any good guide you can suggest to use to flash A12? I found one but it's not informative... i connected turned off A12 phone to computer, chose scatter file, started download but nothing happens

xt123xt said:
Sorry, never used sp flash tool before. Is there any good guide you can suggest to use to flash A12? I found one but it's not informative... i connected turned off A12 phone to computer, chose scatter file, started download but nothing happens
Click to expand...
Click to collapse
How to revive a totally dead Mediatek device
There are quite a number of reasons why your Mediatek device could not only be bricked but stay totally dead with no sign of life. In such a situation, pressing the power button will have no effect. T
forum.hovatek.com
How to use MTK Bypass to backup or flash secure boot MTK
This is a step by step guide showing how to flash or backup a Mediatek (MTK) secure boot device without using a custom download agent (DA). This tool disables the SLA / DAA bootrom protection A little
forum.hovatek.com

Hello, I have a similar problem, I have rooted my phone and had to go back, IMEI gone, I tried to flash combination but I'm getting the same error. Because it's rooted the bootloader is unlocked, right? Tried flashing stock and trying again but didn't work, any ideas? SM-A326B