Samsung Gear S2 Classic is Stuck On Update Loop - Samsung Gear S2

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

Related

[Help] I soft bricked my phone, i am desperate.

I am so lost as to what to do next, i really need guidance.
I am offering a bitcoin tip or a paypal tip to whomever helps me get my phone to work ASAP.
So i was attempting to root my phone [GALAXY S6 - SM-G920F]
Got the file from: https://autoroot.chainfire.eu/ which should've matched my Phone.
First attempt failed, got back into my phone everything is fine. Tried the same thing again, failed this time i get this message:
An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." The logs for the times it has failed:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-zeroflte-zerofltexx-smg920f.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Tried connecting with Kies and Smart switch, none can find the device just keeps buffering and for smart switch it just say it's not supported. I am able to get into downloading mode, but that's it.
Got newest Kies, odin 3 v.10.7.exe however on my first go i noticed i had odin3 v.10.6 but now i got the latest i believe. After reading around i decided to try to fix it back to normal, so i downloaded my countries [sweden] firmware this one: http://www.sammobile.com/firmwares/confirm/57869/G920FXXU3COI9_G920FVDS3COI6_VDS/
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004>
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
And now i am here, i am truely nervous that i wont be able to get it to work.
Please Xda your my only hope. All i wanted was to free up space on my phone.. That's it.. :crying:
Ps. Worth mentioning, sometimes my usb is not recongnized and it flickers on and off (connectiong) but seems
to be fine most of the times and during the odin trials.
To root your phone, couldn't you simply flash twrp and then unikernel, like the guides say?
However, I'd try doing the following:
First of all, download the stock firmware for your version from samfirmware, then flash it via Odin (make sure the versione you download is the same you had before, or at least a more recent one).
From your logs, the problem seems to be pit file, so try reading here http://forum.xda-developers.com/showthread.php?t=1916936
If not, completely delete odin and download it again, maybe trying with a different firmware.
If everything goes well, let it boot into setup wizard, then you will able to root it again, this time following the standard procedure with odin:
- Make sure "Auto reboot" flag is NOT checked;
- Flash the twrp odin-flashable file (can't post links here, but you'll find them in General section);
- Manually reboot into recovery (Hold power+home+volume up).
- Once you're into twrp, flash unikernel and reboot.
Your phone will be rooted
Nicolò98 said:
To root your phone, couldn't you simply flash twrp and then unikernel, like the guides say?
However, I'd try doing the following:
First of all, download the stock firmware for your version from samfirmware, then flash it via Odin (make sure the versione you download is the same you had before, or at least a more recent one).
From your logs, the problem seems to be pit file, so try reading here http://forum.xda-developers.com/showthread.php?t=1916936
If not, completely delete odin and download it again, maybe trying with a different firmware.
If everything goes well, let it boot into setup wizard, then you will able to root it again, this time following the standard procedure with odin:
- Make sure "Auto reboot" flag is NOT checked;
- Flash the twrp odin-flashable file (can't post links here, but you'll find them in General section);
- Manually reboot into recovery (Hold power+home+volume up).
- Once you're into twrp, flash unikernel and reboot.
Your phone will be rooted
Click to expand...
Click to collapse
I just begain with youtubing easy way to root and i just said download odin, get the right firmware plug in an click odin.
That has failed and it's bricked, however i have tried to get my countries firmware, it didint work and produced my last log that i posted.
I am downloading another one there is two for Sweden however the other one says Sweden tre which is an operator over here and not one that i use so i doubt that will work?
i will attempt to download it but it takes 3h due to the limited speed at sammmobile.
So summarize, the sweden firmware from sammobile failed ;_;
What i do is, put phone in download mode, open odin, get the AP [Sweden from sammomobile] it finds it and press start, quickly after it says failed and i am back to square one.
I was reading the link you gave me about the pit files, it appears the error could be related to me having the wrong firmware?
I am seriously offering a bitcoin tip or a paypal tip to whomever helps me get my phone to work.
There are firmwares here for VDS.
Uninstall Kies and reboot your PC before using Odin.
blud7 said:
There are firmwares here for VDS.
Uninstall Kies and reboot your PC before using Odin.
Click to expand...
Click to collapse
Should i try all of those or just take the latest?
3H download, jesus my fiber is crying.
If you were on 5.1.1, then get 5.1.1
You can try the file you dl before. Just uninstall Kies before using Odin.
WaDoDem said:
Should i try all of those or just take the latest?
3H download, jesus my fiber is crying.
Click to expand...
Click to collapse
You dont need to download another rom dude...the problem is your usb dont get recognized and after a while it will disconnect...it happened to me aswell...searched on youtube did an easy fix and then i flashed stock rom with odin and joined marshmallow beta...
Tldr: search on youtube a fix for usb not recognized...i dont have a link sorry you have to search it by yourself its an easy fix..
Is it OK to flash with the latest stock roms? G920FXXU3? or should I flash only G920FXXU2? they are both 5.1.1 anyway.. If i flash with G920FXXU3, can i downgrade it to G920FXXU2? thanks for any help
anthonyrv03 said:
Is it OK to flash with the latest stock roms? G920FXXU3? or should I flash only G920FXXU2? they are both 5.1.1 anyway.. If i flash with G920FXXU3, can i downgrade it to G920FXXU2? thanks for any help
Click to expand...
Click to collapse
You're fine with either.
@WaDoDem
First of all, calm down. Believe me it's harder than you think to brick S6 in a not fixable way
If Odin doesn't flash official roms or you just cant suffer a slow a** download speed from SamMobile :
1. Press and hold all of 4 buttons on your device. (Volume up + Volume Down + Home + Power) your device will reboot.
2. As soon as device reboots release volume up and hold other 3 three. (Power + Home + Volume Down). Your device should boot into downloading mode.
3. Download this :
https://dl.twrp.me/zeroflte/twrp-2.8.7.2-zeroflte.img.tar.html
4. Connect your phone to your pc and flash above file with Odin. As soon as flashing process finishes, hold Power+Home + Volume Up. Now your device will boot into TWRP recovery.
5. Wait for drivers to be installed. Your pc should show phone's internal storage as connected device. If not, go to TWRP Mount section and enable MTP mode. (Or if it's enabled, disable and re enable it )
6. Download this rom :
http://forum.xda-developers.com/gal...rom-2013266107-arrow-rom-v1-0-0-fast-t3212318
And this kernel:
http://forum.xda-developers.com/gal...nified-development/kernel-vindicator-t3156281
Then put them on your phone.
7. Wipe system,data,cache and dalvik cache from twrp.
8. Install Arrow Rom first and then flash Vindicator Kernel.
9.Reboot, first boot can take up to 15 minutes
10.Continue celebrating new year [emoji14]
Sent from my SM-G920I using Tapatalk
sometimes if odin not working i restart my computer and put my mobile in downloadmode again and than i try again,most of the time it worked.....
If you think you can't find a wat at all, Samsung will help u. Download smartswitch to your PC and you can click in top corner emergency reinstall (or something like that) just put your serial number (as found on your backside of the phone)
4. Connect your phone to your pc and flash above file with Odin. As soon as flashing process finishes said:
Odin cant find the tar file.
I got odin 3V3.10.7 in options auto reboot and f. reset time are all bocked in is that right?
On files to download i am able to do, ap,cp,csc,bl neither of those help to find the recovery image that i am supposed to start?
Click to expand...
Click to collapse
Damientju said:
If you think you can't find a wat at all, Samsung will help u. Download smartswitch to your PC and you can click in top corner emergency reinstall (or something like that) just put your serial number (as found on your backside of the phone)
Click to expand...
Click to collapse
I cannot use recovery since none of the numbers i have on the back of my phone matches the one i need to enter.
i tried device initialization that led to FAILED TO UPDATE DUE TO AN ERROR.
and then smart switch recommends emergency software recovery the one you were talking about but i dont know how to get my code.
I assumed you meant to input my phones IMEI however that did not prove to be correct.
WaDoDem said:
I cannot use recovery since none of the numbers i have on the back of my phone matches the one i need to enter.
i tried device initialization that led to FAILED TO UPDATE DUE TO AN ERROR.
and then smart switch recommends emergency software recovery the one you were talking about but i dont know how to get my code.
I assumed you meant to input my phones IMEI however that did not prove to be correct.
Click to expand...
Click to collapse
Relax, flip your phone and on the bottom you'll see (barely visible) text. The last line it says: 'S/N:'
The code after is your serial number. So not your IMEI
The same code is found on the stickers you'd got with your phone
Damientju said:
Relax, flip your phone and on the bottom you'll see (barely visible) text. The last line it says: 'S/N:'
The code after is your serial number. So not your IMEI
The same code is found on the stickers you'd got with your phone
Click to expand...
Click to collapse
When i go to Smart switch Emergency Software recovery and input my S/N R58G52AMP1J
it says:
''Unable to find the recovery code. Check the recovery code in the PC's Emergency Software Recovery menu, or contact the samsung service center.''
When i did Device initialization used my model nr and S/N: R58G52AMP1J, halfway through completing the process, the first one did 100% then the next loading didint start got the error and that re-directed me to try Emergency Software Recovery.
WaDoDem said:
When i go to Smart switch Emergency Software recovery and input my S/N R58G52AMP1J
it says:
''Unable to find the recovery code. Check the recovery code in the PC's Emergency Software Recovery menu, or contact the samsung service center.''
When i did Device initialization used my model nr and S/N: R58G52AMP1J, halfway through completing the process, the first one did 100% then the next loading didint start got the error and that re-directed me to try Emergency Software Recovery.
Click to expand...
Click to collapse
HI
i know your problem , irecently f*cked my phone
I was bare worried however i was able to fix itnw
Download Both file and flash the pit first
and flash the Firmware
And make sure your using ODIN Odin v3.10.7
IF its fix let me know
[email protected] said:
HI
i know your problem , irecently f*cked my phone
I was bare worried however i was able to fix itnw
Download Both file and flash the pit first
and flash the Firmware
And make sure your using ODIN Odin v3.10.7
IF its fix let me know
Click to expand...
Click to collapse
This is the log from when i failed to start/flash the PIT. seconds later my usb was un recognised.
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006>
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
yes
Nicolò98 said:
To root your phone, couldn't you simply flash twrp and then unikernel, like the guides say?
However, I'd try doing the following:
First of all, download the stock firmware for your version from samfirmware, then flash it via Odin (make sure the versione you download is the same you had before, or at least a more recent one).
From your logs, the problem seems to be pit file, so try reading here http://forum.xda-developers.com/showthread.php?t=1916936
If not, completely delete odin and download it again, maybe trying with a different firmware.
If everything goes well, let it boot into setup wizard, then you will able to root it again, this time following the standard procedure with odin:
- Make sure "Auto reboot" flag is NOT checked;
- Flash the twrp odin-flashable file (can't post links here, but you'll find them in General section);
- Manually reboot into recovery (Hold power+home+volume up).
- Once you're into twrp, flash unikernel and reboot.
Your phone will be rooted
Click to expand...
Click to collapse
If Odin says no PIT, he'll need to Odin the PIT file for his device first then Odin the factory firmware.
PS...I'm just browsing threads and stopped here, hopefully to help. I'll keep reading. lol
---------- Post added at 04:43 PM ---------- Previous post was at 04:41 PM ----------
WaDoDem said:
This is the log from when i failed to start/flash the PIT. seconds later my usb was un recognised.
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006>
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Click to expand...
Click to collapse
Did you get the appropriate PIT file for your devices Internal storage? It does matter whether its the 32 64 or 128GB version.
sd_N said:
If Odin says no PIT, he'll need to Odin the PIT file for his device first then Odin the factory firmware.
PS...I'm just browsing threads and stopped here, hopefully to help. I'll keep reading. lol
---------- Post added at 04:43 PM ---------- Previous post was at 04:41 PM ----------
Did you get the appropriate PIT file for your devices Internal storage? It does matter whether its the 32 64 or 128GB version.
Click to expand...
Click to collapse
I just downloaded and tried the pit that above user posted.
https://drive.google.com/folderview...sharing&tid=0B40ItdHKfkyQd1hJQXVDU3dDU2c#list
It's a Galaxy s6 32GB.

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?

Gear S2 Firmwares R720 and R732

I got these 2 firmware for the gear.
R720XXU2EQH1
R732XXU2EQH1
https://drive.google.com/open?id=0B0M3TYEwiP9wSGhPZEdneTJvRjg
https://drive.google.com/open?id=0B0M3TYEwiP9weHNlUXNjaGxxdHc
I hope I have contributed
:good:
This sounds great. Thank you very much.
Need time for downloading... my Internet is very slow at the moment...
Please, maybe my mistake.... but I can see only AP file...
Maybe the other 2 parts are missing?
BL and CSC?
Code:
BL_R732XXU2EQH1_usr.tar
CSC_OXA_R732OXA2EQH1_usr.tar
Best Regards
The name of the zip is bad. but I assure you are all 3 files
CSC_OXA_R720OXA2EQH1_usr.tar
BL_R720XXU2EQH1_usr.tar
AP_R720XXU2EQH1_usr.tar
and
AP_R732XXU2EQH1_usr.tar
BL_R732XXU2EQH1_usr.tar
CSC_OXA_R732OXA2EQH1_usr.tar
adfree said:
:good:
This sounds great. Thank you very much.
Need time for downloading... my Internet is very slow at the moment...
Please, maybe my mistake.... but I can see only AP file...
Maybe the other 2 parts are missing?
BL and CSC?
Code:
BL_R732XXU2EQH1_usr.tar
CSC_OXA_R732OXA2EQH1_usr.tar
Best Regards
Click to expand...
Click to collapse
Thank you very much.
I have successfully downloaded both RAR files and after decompress I can see all 3 parts...
AP, BL and CSC. :good:
My fault.
Best Regards
Does this firmware support Samsung Pay?
Does this firmware support Samsung Pay?
Click to expand...
Click to collapse
Samsung Pay (Tizen Version) is inside EQH1 Firmware...
You can check by simple unpack/extract with Tool:
Code:
7zip
Check rootfs.img... you will find:
Code:
com.samsung.samsung-pay-app.tpk
But this is not what you want nor need... Samsung enable and DISABLE this app by selected CSC/Sales Code and few other Knox related Security crap...
Look at this Video... 1 way could be this... to force Spay...
https://forum.xda-developers.com/showpost.php?p=73982855&postcount=213
WARNING! This could create dangerous sideeffects...
I have only Retail Mode app from Gear S3...
This creates on my SM-R732 harder problems... CSA related...
Other attempt is CSC change...
BUT... Spay is security chain....
Maybe also handset part... like Spay Plugin or CSC of handset is mandatory...
Only as info...
Best Regards
I'm not able to flash this new firmware into my Gear S2. The beginning of the whole process always goes right, but at the end it always writes an error. And the result is always the same, which can be seen in the picture below.
@pRo_lama
You managed your problem?
If not:
1.
You have SM-R720 or SM-R720XXX...
Check in Download Mode if you see SM-R720 or SM-R720X
Other checkpoints... look at Rear Case... Back Cover... back side for:
Live Demo Unit... Not For Sale
2.
The beginning of the whole process always goes right, but at the end it always writes an error.
Click to expand...
Click to collapse
Copy & Paste Odin output... Example:
Code:
<ID:0/001> 192.168.49.1
<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/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> sboot.bin
<ID:0/001> NAND Write Start!!
<ID:0/001> param.bin
<ID:0/001> zImage
<ID:0/001> zImage-recovery
<ID:0/001> modules.img
<ID:0/001> rootfs.img
<ID:0/001> system-data.img
<ID:0/001> user.img
<ID:0/001> ramdisk-recovery.img
<ID:0/001> csc.img
<ID:0/001> ramdisk.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)
3.
Follow if I see some feedback from you...
Best Regards
I flashed older FW and then the smartwatches booted. I have SM-R720. What is the difference between R720 and R720X ?
in my case. I use them for live demo. and I had no problems.
What is the difference between R720 and R720X ?
Click to expand...
Click to collapse
The X...
X means Live Demo Unit... NOT FOR SALE
Demo Devices for Store...
If you are sure you have SM-R720...
Then check Odin Output as I told...
Or if your solution work and you are lucky. Then you can use official way with over the Air... depend on your CSC if you reach EQH1...
Btw... Which Version you flashed successfully? Maybe helpfull for other users too...
Best Regards
I'd love to upload a log, but I do not have it, because I try it last week and I immediately flashed R720XXU2AOJ3 (http://www.mediafire.com/download/zhultaz1dz3brlc/R720XXU2AOJ3_Gear_s2_sport.rar)
Right now I have R720XXU2EQC1.
EQC1 is, because Samsung "branded" device with CSC... Sales Code...
Not every country can download over the Air...
But EQH1 could run on more CSC...
If maybe for next attempts... here is BOKK for SM-R720:
https://forum.xda-developers.com/showpost.php?p=73948041&postcount=178
And here are few Links and my overview for SM-R732:
https://forum.xda-developers.com/showpost.php?p=72225177&postcount=137
Only as info.
Best Regards
i have a somewhat similar problem with a gear s2 classic...
i can get into download mode, i cant get into wireless download, recovery, or factory command, also cant boot... sits at gear s2 logo for a minute or 2... then goes to a snowy screen like post 7
also, 2 of the solder pads are borken but ive managed to be able to still connect in a very delicate manner..
everytime i try to flash in odin, it gets past the set download mode and such and then gets stuck right at writing param.bin... and sits there FOREVER.... doing nothing..
i know its connected properly as it shows up in device manager properly, and in odin,..
but it seems like the nand is messed up permanently
2 of the solder pads are borken but ive managed to be able to still connect in a very delicate manner..
Click to expand...
Click to collapse
:good:
Thanx for this info.
This gives me hope, as I have killed 1 pad...
Checklist for you.
1.
I saw 1 device on Ebay...
Anyway.
Check Download Mode screen for Model name/Product Name...
You see?
SM-R732 or SM-R732X
2.
Same screen shows more infos... like Reactivation Lock on...
RL is on or off?
Perfect and easier for me... if you can post Picture... to see all infos from Screen. :good:
3.
If you need Combination Firmware... then you can PM me.
Best Regards
so here is all the info from the bootloader screen
SM-R732
K: Official, P: Official
R/L: OFF, S/D:1, W/V:0, R/P:B2
i should have attached a pic too for reference
@tnap1979
Output on Screen looks good...
No Reactivation Lock :good:
Also the other infos with official offical looks good...
Screen is from normal Bootloader sboot.bin not from Combination Firmware... otherwise it looks different.
1.
Your Odin Version?
I have used successfully 3.12.3 for instance from here:
https://forum.xda-developers.com/showthread.php?t=2711451
2.
Suggestion... try BOKK Version... click through links here to find it:
https://forum.xda-developers.com/showpost.php?p=72225177&postcount=137
3.
Try package by package... for instance:
Code:
CSC_R732OXA2BOKK_usr.tar.md5
Select only 1 file in Odin...
Check if success...
Then next round if success... proceed with:
Code:
AP_R732XXU2BOKK_usr.tar.md5
Last round BL...
Best Regards
Hi all,
Just update a Gear S2 in France.
Got release R732XXU2EQJ2.
I'm unable to find info about this one .... Any inputs ?
Thx
Code:
R732XXU2EQJ2
Thanx for info.
I can not find changelog... like this:
http://doc.samsungmobile.com/SM-R732/CHC/doc.html
No idea what is inside the 23 MB FOTA package...
Seems for now only for XEF Sales Code... aka France.
Also US XAR is still on BQH1...
Best Regards
Tizen 3.0 now rolling out to the Gear S3 with Value Pack update.
It looks like Gear S2 does not get this update.

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.

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 .

Categories

Resources