Search This thread

ferrett1968

Senior Member
Mar 17, 2005
66
16
Thank you!

I flashed this Rom but... the device is still stuck at the boot screen.

Perhaps, when I flashed a ROM with a BL v2 I created a situation of stall.
I should try to downgrade the bootloader version.

Is there any way to do it? (Sdb shell...)

I neither can connect with heidendall ( I am writing with xda app so I can't check the name).

In any case thankyou for the support!
 
  • Like
Reactions: adfree

adfree

Senior Member
Jun 14, 2008
10,619
6,175
Samsung Galaxy Watch 4
Samsung Galaxy S22
At the moment it is totally unclear to me...

1.
What is all wrong at the device...

According to these Pictures:
https://xdaforums.com/showpost.php?p=73644320&postcount=16

Code:
CURRENT BINARY: Custom [COLOR="Red"][B](Module)[/B][/COLOR]

I ever thought it is if Kernel dzImage...

Maybe in your case modules.img...
:confused:

2.
In Odin Screenshot I saw set... instead get...
So I am not sure if you are trying to repartition :cyclops: :eek: :silly:

Better NOT play with PIT...

2.1
IMHO better focus on reading/dump PIT fiile from Phone...

We have several more methods...
We only need to find the easiest working method for you.

Btw.
I am using Heimdall NOT... because I remember it was not so easy for me... as Driver replace etc... :D :eek:

I am doing this not every day... so I need first to think about it...
But I have an idea...
PM about it later...

3.
SDB and other usefull stuff like this in Upload Mode:
https://xdaforums.com/showpost.php?p=72110199&postcount=45

Btw also Download wireless require working Kernel on device... dzImage

At the moment it seems... only your SBOOT Bootloader is the only piece of Software which is working... :eek:

Best Regards
 

adfree

Senior Member
Jun 14, 2008
10,619
6,175
Samsung Galaxy Watch 4
Samsung Galaxy S22

ferrett1968

Senior Member
Mar 17, 2005
66
16
Ok.
I Will read in Deep later.

In the meanwhile may we share our mobile numbers so we could message/talk with whatsapp?
 

adfree

Senior Member
Jun 14, 2008
10,619
6,175
Samsung Galaxy Watch 4
Samsung Galaxy S22
:good:

This is step forward...

Now compare your PIT with PIT file from SM-R765T
https://xdaforums.com/gear-s3/development/rom-samsung-gear-s3-sm-r765-att-t3588066

Feel free to check your other PIT files too from SM-R765...


You will see difference... 256 Byte RSA 2048 Signature crap...

And 01 or 02 for Bootloader Revision...

We have to find that Firmware, which matches same RSA Keys...

Please try to find an way to dump PIT from SM-R765F... to have Revision 02.

Best Regards
 

ferrett1968

Senior Member
Mar 17, 2005
66
16
I tried few times to dump the PIT file from the 765f but without success!

I tried with Heimdall on different OS (windows, Linux, Lubuntu and osx) but I always get the same error: Failed to send data.

Find attached the 2 modules.img files compressed:

1. from BL_R765TUVU2AQA6_usr
2. from BL_R765FXXU1AQA1_usr
 

Attachments

  • BL_765fXXU1AQA1_modules.img.zip
    5.9 KB · Views: 36
  • BL_R765TUVU2AQA6_usr_modules.img.zip
    17.1 KB · Views: 28
  • Like
Reactions: adfree

adfree

Senior Member
Jun 14, 2008
10,619
6,175
Samsung Galaxy Watch 4
Samsung Galaxy S22
Strange...
modules.img from SM-R765F 1AQA1 is only 5 MB and without 256 Byte Signature at the end of file...
:confused:


Anyway,

Please try attached TAR file... unzip ZIP first...


Flash only 1 file with Odin:
test_v1_smR765F_moduleOnly_1AQA1.tar


No need of screenshot, but Copy and Paste text output from Odin please... Example...
Code:
<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> csc.img
<ID:0/003> modules.img
<ID:0/003> ramdisk-recovery.img
<ID:0/003> ramdisk.img
<ID:0/003> system-data.img
<ID:0/003> user.img
<ID:0/003> zImage
<ID:0/003> zImage-recovery
<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!!

If flash success, then check Download Mode Screen... if Custom (Module) is gone or still present... I mean this... in first Photo:
https://xdaforums.com/showpost.php?p=73644320&postcount=16

Thanx in advance.

Best Regards
 

Attachments

  • test1.zip
    7 KB · Views: 33

ferrett1968

Senior Member
Mar 17, 2005
66
16
Strange...
modules.img from SM-R765F 1AQA1 is only 5 MB and without 256 Byte Signature at the end of file...
:confused:


Anyway,

Please try attached TAR file... unzip ZIP first...


Flash only 1 file with Odin:
test_v1_smR765F_moduleOnly_1AQA1.tar


No need of screenshot, but Copy and Paste text output from Odin please... Example...
Code:
<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> csc.img
<ID:0/003> modules.img
<ID:0/003> ramdisk-recovery.img
<ID:0/003> ramdisk.img
<ID:0/003> system-data.img
<ID:0/003> user.img
<ID:0/003> zImage
<ID:0/003> zImage-recovery
<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!!

If flash success, then check Download Mode Screen... if Custom (Module) is gone or still present... I mean this... in first Photo:
https://xdaforums.com/showpost.php?p=73644320&postcount=16

Thanx in advance.

Best Regards


done!
flash succeded:

<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> modules.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!

Custom (Module) is still present...
 

adfree

Senior Member
Jun 14, 2008
10,619
6,175
Samsung Galaxy Watch 4
Samsung Galaxy S22
  • Like
Reactions: kstephens98

adfree

Senior Member
Jun 14, 2008
10,619
6,175
Samsung Galaxy Watch 4
Samsung Galaxy S22
Service Manual
Code:
SM-R765A_Tshoo_7.pdf
SM-R765A_EVAPL_3.pdf
SM-R765A_EPLIS_11.pdf
SM-R765A-PSPEC_2.pdf
SM-R765A-Direy-6.pdf
SM-R765A-COVER_1.pdf

Please, if somebody have these files...
Please share. :angel:

Thanx in advance.

Best Regards
 

adfree

Senior Member
Jun 14, 2008
10,619
6,175
Samsung Galaxy Watch 4
Samsung Galaxy S22
Still I have no luck...

1.
Nobody share Service Manual of SM-R765...
:rolleyes:

2.
In theory it would be possible to "rebuild" full Firmware with old Binaries/Images from:
Code:
R765FXXU1AQA1/R765FOLB1AQA1/R765FXXU1AQA1
+
FOTA package from
Code:
R765FXXU2BQD1/R765FOLB2BQD1/R765FXXU2BQD1

2.1
With help of alive Gear Sx... only question is... if Delta Version is compatible from Gear S2 and S3... or if S3 uses new Delta update...

I can NOT try at the moment... because my USB Pinout is damaged on my SM-R732... :rolleyes:

2.2
I have bought dead SM-R770 and I am not able to repair... :rolleyes: :rolleyes: :rolleyes:

Otherwise I could do experiments to rebuild Firmware with Gear S3...

3.
Also out of luck to find alive SM-R765F users in Singapore nor anywhere else on earth...
All I can find on Google is something like this:
https://www.facebook.com/SamsungMobileSingapore/posts/10155038332587625:0

4.
All my requests in other ForumS SM-R765 Firmware related fails...

:eek:

5.
No idea how long Samsung need for Tizen 3 upgrade... and no idea if SM-R765F will get it too...


LOW chance to solve these problems in 2017... :(

Sorry.

Best Regards
 

adfree

Senior Member
Jun 14, 2008
10,619
6,175
Samsung Galaxy Watch 4
Samsung Galaxy S22
@ferrett1968

Can you try please only to flash this Kernel:
Code:
KernelONLYtest.tar

Attached as ZIP...

Taken from Tizen 3 Source...
Code:
linux-exynos7270-tw2-3.18.14-6.2.aarch64.rpm

If this work...
We could try to flash the Platform files... hopefully your device awake then... :eek:

Best Regards
 

Attachments

  • KernelONLYtest.zip
    5.6 MB · Views: 37

frs2308

Member
Sep 4, 2009
10
6
Have had the same situation - flashed R760 Frontier with bootloader v1 on top of bl v2. Got stuck with boot loop

Ended up buying R765A watch to take apart and use back cover with pins. Then - flashed stock FW and got it working again

For thouse who doesn't know: You can buy Samsung gear S charger like this
s-l300.jpg

take it apart and use those pins to connect to gear s2|s3 watches(via USB and ODIN). Pinout is the same, and you'd have no hassle with soldering
 
  • Like
Reactions: adfree

adfree

Senior Member
Jun 14, 2008
10,619
6,175
Samsung Galaxy Watch 4
Samsung Galaxy S22
@ferrett1968

:eek:

Really really sorry.

I have 0 idea why also SM-R765F Firmware is impossible to get... nowhere... nobody helped... :(
I have really tried all I can do.

Similar situation still with Korean SM-R765... :rolleyes: :( :crying:

I am working at the moment for solution to dump PIT from Gear S2/S3 over WiFi... progress is here:
https://xdaforums.com/showpost.php?p=75521087&postcount=444

Commands are the same for USB...

I hope in days to get working solution...
I hope user(s) confirm success...

So we could try to find users with alive SM-R765F and SM-R765 for dump PIT files...
Maybe later more possible...

Really sorry for this slow progress. :eek:

Best Regards

@frs2308

Thanx for info. :good:

Only to be sure...
You mean this connector from this Charger fits into the tiny hole inside Rear Case/Back Cover from SM-R765?

It could be... the part number for the SM-R765 variants is:
GH97-19294A
Code:
MEA REAR-SM-R765(BLK)
46 $

Now I need only confirmation... where to buy this...
Or maybe sites with Pictures somewhere...

I am from Germany...
In german Ebay nearly never SM-R765 to buy...

Also in my case toooo expensive... for only want Rear Cover/Back Case... :eek:

Best Regards
:confused:
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Dear friends,
    I found that the LTE connection is very useful when you have to leave your mobile somewhere and you can get calls and notifications through mobile connection.
    I bought a Gear S3 LTE (R765) from a Singapore site because in Italy it is not available.
    I sadly discovered that i couldn't register a TIM eSIM (Italian Mobile) because, while executing the registration process, I had the answer "...Can't connect to the server ...".
    So I kept reading around how to solve the problem...
    My first attempt was to flash a 765v hoping a different rom could help me in registering the italian eSIM on my device....: Yellow triangle brick!!!!!
    Thank to the senior member adfree I realized that I flashed a Version 2 Bootloader and I could not downgrade it back.
    I tried to flash another rom, a proper one for 765f, but with a BL ver.1 : brick again but in a different way: the device started with the starting screen (Gear s3 Frontier...) then it just seemed to switch off...
    Trying to enter again in the Odin menu ( home button for 8-9 sec - reboot - 3 times home button - download wireless )... it was just stuck in the Tizen logo.
    Here https://xdaforums.com/gear-s3/how-to/rom-samsung-gear-s3-classic-sm-r770-t3646789 I found this quote from xedaman about BokkieAndijk:

    Quote:
    ... i found info how to get my S3 back to live again. If you have the same problems with your (bricked) S3 then go to download wirelessly mode en as soon as you see the flower then push the power button 2 seconds en let it go for 1 second, than push it again for 2 seconds en let it go for one and so on til you get him in to download wirelessly mode. May take some attempts but it saves my ass a few times.

    I did it and i worked fine!

    It gave me the opportunity to flash a custom rom from 765v. I thought that a custom rom would have been accepted from a V2 BL.... NOPE!

    Now I am stuck again: the divice boots but remains to the booting screen (Gear s3 Frontier...). I tried to enter in Odin menu and every thing works but download wireless: It remains stuck on the Tizen Logo.
    I tried to apply the same technique I used to unbrick it before but seems unuseful.

    So I decided to open the device and I discovered that , as adfree said a few times, just the LTE versions have a side pinout near the strap band.
    Opening the device I saw that the side pinout (5 pins) is connectd to the motherboard well known 5 pins.

    I am now posting here the pics of the device opened hoping someone can help me to unbrick the device explaining how to connect the s3 pinout to a pc to let me flash it with usb odin and downgrade the BL... OR, if someone knows how to unbrick the device with another button combination, please post it!

    Best Regards
    P.S.
    Opening the device I ruined screws and back cover, do anyone knows where to by a new backcover and some F**** (freaking) normal screws of that size?
    2
    @frs2308

    Thanx for info. :good:

    Only to be sure...
    You mean this connector from this Charger fits into the tiny hole inside Rear Case/Back Cover from SM-R765?

    It could be... the part number for the SM-R765 variants is:
    GH97-19294A
    Code:
    MEA REAR-SM-R765(BLK)
    46 $

    Now I need only confirmation... where to buy this...
    Or maybe sites with Pictures somewhere...

    I am from Germany...
    In german Ebay nearly never SM-R765 to buy...

    Also in my case toooo expensive... for only want Rear Cover/Back Case... :eek:

    Best Regards
    :confused:

    Yes, it fits all Gear S2 models (wifi version - you have to open back cover to see pins | LTE - same connector as on S3), and S3 LTE. The only thing - you'd have to carefully cut plastic on every side with a rasp, as it is slightly thicker. I did it, and it worked for me. Please see attachment images

    Also, very important to use full USB cable. I've tried with several cheap chinese micro usb, and it didn't work. Probably, because they do not have all wires inside. Gear S3 original (thick) works perfectly fine
    2
    Here i am.
    It took time but...
    I just soldered wires ( with a little help from my friends...:D) on my 765f as you can see from the pics below.
    I soldered the wires on the outside pinout of the watch.... I connected but usb port.... now I think I need your help.
    2
    USB Pinout GW4...

    Here my tested SM-R870...

    Best Regards
    2
    Strange...
    modules.img from SM-R765F 1AQA1 is only 5 MB and without 256 Byte Signature at the end of file...
    :confused:


    Anyway,

    Please try attached TAR file... unzip ZIP first...


    Flash only 1 file with Odin:
    test_v1_smR765F_moduleOnly_1AQA1.tar


    No need of screenshot, but Copy and Paste text output from Odin please... Example...
    Code:
    <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> csc.img
    <ID:0/003> modules.img
    <ID:0/003> ramdisk-recovery.img
    <ID:0/003> ramdisk.img
    <ID:0/003> system-data.img
    <ID:0/003> user.img
    <ID:0/003> zImage
    <ID:0/003> zImage-recovery
    <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!!

    If flash success, then check Download Mode Screen... if Custom (Module) is gone or still present... I mean this... in first Photo:
    https://xdaforums.com/showpost.php?p=73644320&postcount=16

    Thanx in advance.

    Best Regards


    done!
    flash succeded:

    <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> modules.img
    <ID:0/003> RQT_CLOSE !!
    <ID:0/003> RES OK !!
    <ID:0/003> Removed!!
    <ID:0/003> Remain Port .... 0
    <OSM> All threads completed. (succeed 1 / failed 0)
    <ID:0/003> Added!!

    Custom (Module) is still present...