Galaxy Watch Active 2 | SM-R820 | Soft Bricked - Samsung Galaxy Watch

Hello Guys,
I tried to change the region on my Galaxy Watch Active 2 to get the Samsung Pay, ECG worked. I followed TechnoProz's great tutorial, but did not succeed and my watch is soft bricked now. I am sharing what have I tried this far to recover the watch.
Step 1:
Tried to flash Tizen 5.5 Combination firmware (technoproz) via netodin3 wireless method, and that got failed with netodin3 red color fail error. Now my watch is not starting to OS, "firmware upgrade encountered an issue please select recovery mode in kies" is only getting when I power up the watch.
Step 2:
At this stage, I thought I missed something so I tried to flash stock Tizen 4.4 firmware (technoproz), to downgrade the version and start from scratch and to also recover my watch. Again this time, netodin3 flashing failed (takes around one and half hour to give error), my watch did not rebooted after netodin3 flashing error. So I manually restarted while holding power button and my watch stuck on bootloop. Everytime I power up the watch, the samsung branding is getting on screen nothing else.
Step 3:
I retried to flash stock Tizen 4.4 firmware (technoproz). Again flashing failed but this time it takes around 3 hours to get red color fail error. After watch restart, Step 1 error is coming again. Flashing error comes after "<ID:0/001> rootfs.img" line in netodin3 logs.
Step 4:
I thought, I need to flash same Tizen OS stock firmware in which my watch is in working condition (My Watch OS version was 5.5.0.2) to get everything working, so I purchased latest stock firmware "R820XXU1DUA3 Tizen 5.5.0.2" from here (it cost $3 to me). And tried to flash with netodin3. Unfortunately, Step 3 error is coming again .
Step 5:
I have tried flashing Stock 4.4(technoproz) , Stock 5.5 (the one which I have purchased) firmware 2 3 times, Only the Step 3 error is repeating, sometime it takes 4 to 5 hour to give the error on netodin.
Now, I am out of ideas. Someone please help me/suggest what should I do now. I am ready to spend some money if any new firmware is still required. I just want to see my watch alive It is okay if region is not changed. I am lucky that Watch recovery menu is working fine with download (wireless) mode also.
Watch and Flashing Tools Specification:​
Watch Model No: SM-R820 (SM-R820NZKAINU)
Tizen OS: 5.5.0.2
Specs: Bluetooth model, 44MM, Black Color
Region: Asia, India
Netodin3 version: v1.0 (options ticked> Auto Reboot, F. Reset Time)
Stock Tizen 4.4 firmware: R820XXU1ASHF
Stock Tizen 5.5 firmware: R820XXU1DUA3 Tizen 5.5.0.2
AP_R820XXU1DUA3_usr.tar.md5
BL_R820XXU1DUA3_usr.tar.md5
CSC_OXA_R820OXA1DUA3_usr.tar.md5

Adding netodin errolog and snapshot.
{
"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"
}
<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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> cm.bin
<ID:0/001> NAND Write Start!!
<ID:0/001> dzImage-recovery
<ID:0/001> param.bin
<ID:0/001> up_param.bin
<ID:0/001> dzImage
<ID:0/001> sboot.bin
<ID:0/001> ramdisk-recovery.img
<ID:0/001> ramdisk.img
<ID:0/001> user.img
<ID:0/001> system-data.img
<ID:0/001> rootfs.img
<ID:0/001>
<ID:0/001> XmitData
<ID:0/001> Complete(Write) operation failed.
<ID:0/001> Removed!!
<OSM> All threads completed. (succeed 0 / failed 1)

shubham555 said:
Hello Guys,
I tried to change the region on my Galaxy Watch Active 2 to get the Samsung Pay, ECG worked. I followed TechnoProz's great tutorial, but did not succeed and my watch is soft bricked now. I am sharing what have I tried this far to recover the watch.
Step 1:
Tried to flash Tizen 5.5 Combination firmware (technoproz) via netodin3 wireless method, and that got failed with netodin3 red color fail error. Now my watch is not starting to OS, "firmware upgrade encountered an issue please select recovery mode in kies" is only getting when I power up the watch.
Step 2:
At this stage, I thought I missed something so I tried to flash stock Tizen 4.4 firmware (technoproz), to downgrade the version and start from scratch and to also recover my watch. Again this time, netodin3 flashing failed (takes around one and half hour to give error), my watch did not rebooted after netodin3 flashing error. So I manually restarted while holding power button and my watch stuck on bootloop. Everytime I power up the watch, the samsung branding is getting on screen nothing else.
Step 3:
I retried to flash stock Tizen 4.4 firmware (technoproz). Again flashing failed but this time it takes around 3 hours to get red color fail error. After watch restart, Step 1 error is coming again. Flashing error comes after "<ID:0/001> rootfs.img" line in netodin3 logs.
Step 4:
I thought, I need to flash same Tizen OS stock firmware in which my watch is in working condition (My Watch OS version was 5.5.0.2) to get everything working, so I purchased latest stock firmware "R820XXU1DUA3 Tizen 5.5.0.2" from here (it cost $3 to me). And tried to flash with netodin3. Unfortunately, Step 3 error is coming again .
Step 5:
I have tried flashing Stock 4.4(technoproz) , Stock 5.5 (the one which I have purchased) firmware 2 3 times, Only the Step 3 error is repeating, sometime it takes 4 to 5 hour to give the error on netodin.
Now, I am out of ideas. Someone please help me/suggest what should I do now. I am ready to spend some money if any new firmware is still required. I just want to see my watch alive It is okay if region is not changed. I am lucky that Watch recovery menu is working fine with download (wireless) mode also.
Watch and Flashing Tools Specification:​
Watch Model No: SM-R820 (SM-R820NZKAINU)
Tizen OS: 5.5.0.2
Specs: Bluetooth model, 44MM, Black Color
Region: Asia, India
Netodin3 version: v1.0 (options ticked> Auto Reboot, F. Reset Time)
Stock Tizen 4.4 firmware: R820XXU1ASHF
Stock Tizen 5.5 firmware: R820XXU1DUA3 Tizen 5.5.0.2
AP_R820XXU1DUA3_usr.tar.md5
BL_R820XXU1DUA3_usr.tar.md5
CSC_OXA_R820OXA1DUA3_usr.tar.md5
Click to expand...
Click to collapse
A very much thanks to @adfree , He solved my issue.
As suggested by @adfree, I Just changed the PC and the firmware got flashed in < 10 minutes.
MyPC specs:
1st PC , win10 64bit, 16 gigs of ram , i7 vPRO, 512GB SSD
2nd PC , 4GB RAM, 1TB HDD, dual core, also win 10 64bit,,, and this system flashed my firmware in just 10 minutes, (don't know what is wrong with netodin3)
I even managed to change my region, so earlier it was on INDIAN region (INU), I changed to XAR (USA) ,
Now, samsung pay is working flawless, Added HDFC CC and bunch of others, working fine. I have Redmi K20 Pro so, samsung phone is also not required for SPay.
What firmware/steps I have used finally?
Just follow the TechnoProz guide, to flash the firmware stock and combination.
Try firmware version with your current one, as my watch is on latest DUA3, Tizen 5.5.0.2.
I have purchased latest stock and combination firmware for Tizen 5.5.0.2 from here (www.fullstockfirmwaredownload.com), it cost me $3 for both. Both are working fine.
Why trying with other PC solved the issue?
If you are getting too much time to flash firmware using netodin3 and meet the error after rootfs.img/Xmit line , XMIT is something related to WIFI (according to @adfree ) , so changing the PC can help (works for me).
Still, I have not get ECG, BP even after the latest update and for XAR regions.

shubham555 said:
A very much thanks to @adfree , He solved my issue.
As suggested by @adfree, I Just changed the PC and the firmware got flashed in < 10 minutes.
MyPC specs:
1st PC , win10 64bit, 16 gigs of ram , i7 vPRO, 512GB SSD
2nd PC , 4GB RAM, 1TB HDD, dual core, also win 10 64bit,,, and this system flashed my firmware in just 10 minutes, (don't know what is wrong with netodin3)
I even managed to change my region, so earlier it was on INDIAN region (INU), I changed to XAR (USA) ,
Now, samsung pay is working flawless, Added HDFC CC and bunch of others, working fine. I have Redmi K20 Pro so, samsung phone is also not required for SPay.
What firmware/steps I have used finally?
Just follow the TechnoProz guide, to flash the firmware stock and combination.
Try firmware version with your current one, as my watch is on latest DUA3, Tizen 5.5.0.2.
I have purchased latest stock and combination firmware for Tizen 5.5.0.2 from here (www.fullstockfirmwaredownload.com), it cost me $3 for both. Both are working fine.
Why trying with other PC solved the issue?
If you are getting too much time to flash firmware using netodin3 and meet the error after rootfs.img/Xmit line , XMIT is something related to WIFI (according to @adfree ) , so changing the PC can help (works for me).
Still, I have not get ECG, BP even after the latest update and for XAR regions.
Click to expand...
Click to collapse
bro!! please help me!! each time I have a problem with my Xiaomi K20 Pro, always restarted the firmware and had to reconnect the active 2 to the phone, but the watch never reconiced the phone so have to enter recovery mode and rebooting, at the end...it always works....until now....every time I do the same method, it says contact to support or something like that,...COULD U PLEASE HELP TELLIN HOW TO FIX IT BY WIRELESS MODE OR ANY METHOD U USED?
THnks so much! answer here or text me +51927427022 (whatsapp or telegram)

Zecaronix1 said:
bro!! please help me!! each time I have a problem with my Xiaomi K20 Pro, always restarted the firmware and had to reconnect the active 2 to the phone, but the watch never reconiced the phone so have to enter recovery mode and rebooting, at the end...it always works....until now....every time I do the same method, it says contact to support or something like that,...COULD U PLEASE HELP TELLIN HOW TO FIX IT BY WIRELESS MODE OR ANY METHOD U USED?
THnks so much! answer here or text me +51927427022 (whatsapp or telegram)
Click to expand...
Click to collapse
pls share watch details, and proper steps also,, what have you followed till now.
If are able to go into wireless download mode than you u can try to flash stock firmware
If xmit error comes in netodi3 flashing, try with other pc.
if netodin3 failing with another errors, try to flash with USB.

shubham555 said:
pls share watch details, and proper steps also,, what have you followed till now.
If are able to go into wireless download mode than you u can try to flash stock firmware
If xmit error comes in netodi3 flashing, try with other pc.
if netodin3 failing with another errors, try to flash with USB.
Click to expand...
Click to collapse
Hi and thnks for answering! I have a bigger problem now. I used to fix my bluettoth connections with my watch and my phone flashing my watch and always worked, until now... Every time i try to flash with netOdin, it works and shows a GREEN PASS, but the phone, at the end, it always shows the same messagge.. COULDN'T CONNECT TO THE PHONE, TRY TO CONTACT SUPPORT...please help me!
*Maybe giving some different files to flash or another method....
*I always flashed it with wireless mode

@Zecaronix1
More details...
A
Exact Model Name?
SM-R820 or LTE Variant SM-R825F or Playstation or Gameboy?
B
Filenames you have used in netOdin?
This helps to identify if you used too old outdated Firmware... or other problems..
Best Regards

adfree said:
@Zecaronix1
More details...
A
Exact Model Name?
SM-R820 or LTE Variant SM-R825F or Playstation or Gameboy?
B
Filenames you have used in netOdin?
This helps to identify if you used too old outdated Firmware... or other problems..
Best Regards
Click to expand...
Click to collapse
A
SM-R820 bluetooth model
B
B.1
AP_R820XXU1ASHF_usr.tar
BL_R820XXU1ASHF_usr.tar
CSC_OXA_R820OXA1ASHF_usr.tar
B.2
AP_R820XXU1BSI9_usr.tar
BL_R820XXU1BSI9_usr.tar
CSC_OXA_R820OXA1BSI9_usr.tar
I used these 2 files some many times until some of them work but, now, any of them work....

These files now outdated... obsolete.
Because Samsung Rollback Prevention crap...
You need newer Files...
DUA3 for instance... because Tizen 5.5...
Tizen 5.5 files are somewhere... sorry less time to search now for you in XDA...
Later maybe more time...
Best Regards

adfree said:
These files now outdated... obsolete.
Because Samsung Rollback Prevention crap...
You need newer Files...
DUA3 for instance... because Tizen 5.5...
Tizen 5.5 files are somewhere... sorry less time to search now for you in XDA...
Later maybe more time...
Best Regards
Click to expand...
Click to collapse
I paid for these files:
AP_R820XXU1DUA3_usr.tar
BL_R820XXU1DUA3_usr.tar
CSC_OXA_R820OXA1DUA3_usr.tar
and it's the same CONTACT SUPPORT problem...
i have no idea of what to do.... sometimes worked with factory command but now NOTHING WORKS...
SOME ONE HELP ME PLEASE!

I have limited time and motivation... sorry...
A
DUA3 is here for free.
Firmware r820- r830
Hello NEW UPDATE FOR R820 - R830 To update with netOdin see here how to do it https://forum.xda-developers.com/showthread.php?p=78800094 0. This process will factory reset your Watch, so make sure you've backed up everything you...
forum.xda-developers.com
B
IMHO Combination Firmware Tizen 5.5 is also somewhere ... IMHO...
ATJ1 for Tizen 5.5 uploaded from me ...
File-Upload.net - COMBINATION-FT55_R820XXU1ATJ1.tar.md5.7z
Datei: COMBINATION-FT55_R820XXU1ATJ1.tar.md5.7z. Die Datei wurde von einem User hochgeladen. Laden Sie auch kostenlos Dateien hoch mit File Upload.
www.file-upload.net
Somewhere allready posted...
C
No idea yet, what you mean with nothing works...
Can you give exact status?
Maybe make Photos to bypass my limited English skills...
Best Regards

adfree said:
I have limited time and motivation... sorry...
A
DUA3 is here for free.
Firmware r820- r830
Hello NEW UPDATE FOR R820 - R830 To update with netOdin see here how to do it https://forum.xda-developers.com/showthread.php?p=78800094 0. This process will factory reset your Watch, so make sure you've backed up everything you...
forum.xda-developers.com
B
IMHO Combination Firmware Tizen 5.5 is also somewhere ... IMHO...
ATJ1 for Tizen 5.5 uploaded from me ...
File-Upload.net - COMBINATION-FT55_R820XXU1ATJ1.tar.md5.7z
Datei: COMBINATION-FT55_R820XXU1ATJ1.tar.md5.7z. Die Datei wurde von einem User hochgeladen. Laden Sie auch kostenlos Dateien hoch mit File Upload.
www.file-upload.net
Somewhere allready posted...
C
No idea yet, what you mean with nothing works...
Can you give exact status?
Maybe make Photos to bypass my limited English skills...
Best Regards
Click to expand...
Click to collapse
nothing works means that always has the message from the picture
I flashed with DUA 3 files and still the same thing....(wireless download mode)
help please!

shubham555 said:
Hello Guys,
I tried to change the region on my Galaxy Watch Active 2 to get the Samsung Pay, ECG worked. I followed TechnoProz's great tutorial, but did not succeed and my watch is soft bricked now. I am sharing what have I tried this far to recover the watch.
Step 1:
Tried to flash Tizen 5.5 Combination firmware (technoproz) via netodin3 wireless method, and that got failed with netodin3 red color fail error. Now my watch is not starting to OS, "firmware upgrade encountered an issue please select recovery mode in kies" is only getting when I power up the watch.
Step 2:
At this stage, I thought I missed something so I tried to flash stock Tizen 4.4 firmware (technoproz), to downgrade the version and start from scratch and to also recover my watch. Again this time, netodin3 flashing failed (takes around one and half hour to give error), my watch did not rebooted after netodin3 flashing error. So I manually restarted while holding power button and my watch stuck on bootloop. Everytime I power up the watch, the samsung branding is getting on screen nothing else.
Step 3:
I retried to flash stock Tizen 4.4 firmware (technoproz). Again flashing failed but this time it takes around 3 hours to get red color fail error. After watch restart, Step 1 error is coming again. Flashing error comes after "<ID:0/001> rootfs.img" line in netodin3 logs.
Step 4:
I thought, I need to flash same Tizen OS stock firmware in which my watch is in working condition (My Watch OS version was 5.5.0.2) to get everything working, so I purchased latest stock firmware "R820XXU1DUA3 Tizen 5.5.0.2" from here (it cost $3 to me). And tried to flash with netodin3. Unfortunately, Step 3 error is coming again .
Step 5:
I have tried flashing Stock 4.4(technoproz) , Stock 5.5 (the one which I have purchased) firmware 2 3 times, Only the Step 3 error is repeating, sometime it takes 4 to 5 hour to give the error on netodin.
Now, I am out of ideas. Someone please help me/suggest what should I do now. I am ready to spend some money if any new firmware is still required. I just want to see my watch alive It is okay if region is not changed. I am lucky that Watch recovery menu is working fine with download (wireless) mode also.
Watch and Flashing Tools Specification:​
Watch Model No: SM-R820 (SM-R820NZKAINU)
Tizen OS: 5.5.0.2
Specs: Bluetooth model, 44MM, Black Color
Region: Asia, India
Netodin3 version: v1.0 (options ticked> Auto Reboot, F. Reset Time)
Stock Tizen 4.4 firmware: R820XXU1ASHF
Stock Tizen 5.5 firmware: R820XXU1DUA3 Tizen 5.5.0.2
AP_R820XXU1DUA3_usr.tar.md5
BL_R820XXU1DUA3_usr.tar.md5
CSC_OXA_R820OXA1DUA3_usr.tar.md5
Click to expand...
Click to collapse
were files?

Hi There,
I bricked my Galaxy Watch Active 2 (CB15) while trying to change the region. I was trying to change the region from US to CANADA. But I think I flashed the wrong combination firmware.
Details about the watch:-
Model Number - SM-R825U
Serial Number - RFAMB0NW9CV
TIZEN - 5.5.0.2
Software - R825USQU1DUK3, SM-R825USSAXAR
Previously my watch was running totally fine then I tried to change my region from US to Canada. I followed the guide from TechnoProz YouTube channel. I downloaded (COMBINATION-FT40_R825USQU1ASL2.tar.md5) and flashed is on my watch. It was being flashed without a problem but a the end of the process. It failed on the last process. I don't know the exact error code, because I did close the NETODIN after that. After getting the error the watch stuck in the download mode and did nothing. Then I force rebooted the watch and it stuck in a boot-loop. After that I tried to restore it to the stock firmware. But I am unable to find the stock firmware (R825USQU1DUK3) that was installed on the watch previously.
Then I force turned off the watch and left if for a day. Then I rebooted the watch next day, now it is showing some error code that is like this
RST_STAT =0x1000000
ECT : PARA0022
LPDDR4 manufacturer = Samsung
LPDDR4 process ver =D18
LPDDR4 size = 1.50 gb
LOT_ID = NHAAZ
CHIP_ID = 03f51dbace46
[TMU] 27
nAsv_TABLE: 2
nAsv_CPUCL0: 4
nAsv_CPUCL1: 4
nAsv_G3D: 4
nAsv_MIF: 4
nAsv_INT: 4
nAsv_CAM_DISP: 4
nAsv_CP: 4
nAsv_PMIC: 0

Jags2901 said:
Hi There,
I bricked my Galaxy Watch Active 2 (CB15) while trying to change the region. I was trying to change the region from US to CANADA. But I think I flashed the wrong combination firmware.
Details about the watch:-
Model Number - SM-R825U
Serial Number - RFAMB0NW9CV
TIZEN - 5.5.0.2
Software - R825USQU1DUK3, SM-R825USSAXAR
Previously my watch was running totally fine then I tried to change my region from US to Canada. I followed the guide from TechnoProz YouTube channel. I downloaded (COMBINATION-FT40_R825USQU1ASL2.tar.md5) and flashed is on my watch. It was being flashed without a problem but a the end of the process. It failed on the last process. I don't know the exact error code, because I did close the NETODIN after that. After getting the error the watch stuck in the download mode and did nothing. Then I force rebooted the watch and it stuck in a boot-loop. After that I tried to restore it to the stock firmware. But I am unable to find the stock firmware (R825USQU1DUK3) that was installed on the watch previously.
Then I force turned off the watch and left if for a day. Then I rebooted the watch next day, now it is showing some error code that is like this
RST_STAT =0x1000000
ECT : PARA0022
LPDDR4 manufacturer = Samsung
LPDDR4 process ver =D18
LPDDR4 size = 1.50 gb
LOT_ID = NHAAZ
CHIP_ID = 03f51dbace46
[TMU] 27
nAsv_TABLE: 2
nAsv_CPUCL0: 4
nAsv_CPUCL1: 4
nAsv_G3D: 4
nAsv_MIF: 4
nAsv_INT: 4
nAsv_CAM_DISP: 4
nAsv_CP: 4
nAsv_PMIC: 0
View attachment 5537315
Click to expand...
Click to collapse
Dude How do you solved the Brick one. I m trying to do the same but unfortunately it is now showing nothing except a black screen do you have any idea?

Related

(HOW-TO) Flash FW JK1 over JJ4

You will need to register to gain access to this part of the site.
http://www.samfirmware.com/WEBPROTECT-p1000.htm
First thing you will need to do is download a few things from the page.
We need -
P1000XWJK1 ## P1.PIT Version 2.2 2010 November (Located in the Europe section at the bottom)
Then scroll to the bottom of the page and look for -
NEW Odin: DOWNLOAD Version 1.7
Once you have all the files in a folder on your desktop. Open up the Odin folder and extract and you will see 2 files Odin and a PIT file.
Open up Odin and look to the right, load up the PIT file that was included in the folder.
You then need to extract the .tar file from P1000XWJK1 that you downloaded. Once you have extracted it go back to Odin and load the .tar file in to the PDA section an tick the box.
Now that were ready to flash you must prepare the tab -
You will need to take both sim card and SD card out before we do this.
Once both have been removed turn the device off. Now power back on holding Volume down + home key.
You should now be in download mode - This is a black and yellow screen with an Android bot stood in a triangle digging. Once you are at this stage you are ready to flash.
Double check that the only options checked are -
Auto Reboot
F. Reset Time
PDA
Once you are happy hit the start button. You should now see Odin doing its thing and also the tab will show a progress bar. Once flashed you can check if the flash was successful by checking with *#1234#
As always
Remember to back up anything important that is stored on the phones memory as this may be lost during the flashing process.
Hope this helps
Funnily enough, I did this myself this morning.
I had to flash JJ4 first, and when I did it booted into Russian, however sticking JK1 over the top brought everything back to English.
Once JK1 booted, the only issue I had is that it wouldn't connect with Google servers when trying to setup my Gmail account. However, exiting out of the setup wizard and doing it manually worked fine.
I'm still setting my Tab up again, but two things I've already noticed are:
1. I can now use the Samsung Email app with the Google Apps for Domains accounts and Exchange ActiveSync - in the original firmware, whilst a normal Gmail account would work fine with Exchange ActiveSync, but none of my Apps for Domains would. Now they work ok.
2. I can get to non-Mobile web sites in a reliable manner! Woo hoo, full BBC iPlayer instead of the mobile version!
Regards,
Dave
UPDATE - I made a Titanium Backup for everything before I flashed my Tab, but I didn't think about it too much and now realize that Titanium didn't backup to external SD but to the internal memory which was wiped.
Not a particularly big deal as I can download it all and set it up again, but I did lose a few preinstalled items, including "Samsung Games" and NOVA.
A bigger concern was that I couldn't sign into Market over WiFi (though 3G worked ok). GTalk wouldn't start either and since Market uses the GTalk protocol, this was clearly related.
I factory reset my Tab again, and this time I could sign into Google via the setup wizard ok (unlike my previous attempt) and having done this Market worked fine.
Regards,
Dave
JJ4.. I have PDA - JJ3 and CSC JJ2. which one counts?
And also, how do I flash JJ4 ?''
EDIT: I tried flashing JJ4. Odin freezes -
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P1000XWJJ4-REV03-ALL-CL639474.tar.md5 is valid.
<OSM> MODEM_P1000XXJID.tar.md5 is valid.
<OSM> GT-P1000-CSC-SERJJ2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
what am I doing wrong ?
I have yet to flash a full rom on my tab yet so I cant help you. Id assume that its pretty much the same as flashing a partial rom.
I think if your flashing JJ4 then you should tick the 're-partition' box. Have you tried this?
My question is are you getting 3g after doing this flash??
bulldebeerman said:
My question is are you getting 3g after doing this flash??
Click to expand...
Click to collapse
Yes- Everything works fine for me.
Noob question, but what does flashing this ROM do that is beneficial? What does the new ROM do that the old did not?
Main reason for people flashing this partial rom is -
Issues with the UAString in all browsers. When trying to navigate to lets say bbc iplayer it would re-direct to the mobile version. After flashing you will be able to view 'full' sites. If you already can then Id say you do not need to flash...
mklass said:
Main reason for people flashing this partial rom is -
Issues with the UAString in all browsers. When trying to navigate to lets say bbc iplayer it would re-direct to the mobile version. After flashing you will be able to view 'full' sites. If you already can then Id say you do not need to flash...
Click to expand...
Click to collapse
Ah, makes sense. I was hoping this had something to do with getting the phone AND 3G to work . It seems right now I can either have one or the other, but not both. Then again, I can't even get my tab to work with my normal TMO sim card, it just redirects to the tmo website if you try to go anywhere besides google .
Ok thanks
Sent from my SGH-T849 using XDA App
languages are lost with the flash with jk1?
the Italian is lost?
this is probably a stupid question but how do i know which version do i have and whats the difference/benefits of one over the other?
Know my way around flashing on HTC phones and have dabbled in development in my time, but unfortunately on the Tab, I am a complete newb, so...
<newb>
..the how-to discusses flashing JK1 over JJ4. As far as I can tell, I have JJ3 - i.e. my build number is FROYO.XWJJ3 and my baseband is P1000XXJID.
Can I flash JK1 directly over JJ3? As far as I can tell, all of the firmwares on Samifirmware are now complete - i.e. they have an asterisk marked "no full firmware" but none of the European firmwares have this asterisk, by which I assume they're complete and stand alone?
Also, what are the benefits of JK1 v JJ3? About the only thing I don't like about my Tab at the moment is that it takes an inordinately long time to connect to my home wifi network. If I watch it connecting in the settings page, it seems to fail to get an IP address in the first attempt (in that it sits at that point for a while, then disconnects from the wifi network) - the second attempt gets an IP fine. (And before anyone says "it must be your router", I have about a dozen devices on my network, ranging from Macs, PCs, Android phones, iOS devices and nothing else has any trouble). Is JK1 likely to improve that?
</newb>
Main reason for people flashing this partial rom is -
Issues with the UAString in all browsers. When trying to navigate to lets say bbc iplayer it would re-direct to the mobile version. After flashing you will be able to view 'full' sites. If you already can then Id say you do not need to flash...
Im not sure about improving your signal as this would be to do with the radio..
I think you can flash JK1 over JJ4..
Filgaliel said:
JJ4.. I have PDA - JJ3 and CSC JJ2. which one counts?
And also, how do I flash JJ4 ?''
EDIT: I tried flashing JJ4. Odin freezes -
what am I doing wrong ?
Click to expand...
Click to collapse
if you figure something out plz do say (or PM) i am sitting here with 20 tablets just recieved from Telenor.

[Q] Firmware upgrade encountered an Issue

Hi,
I am a newb, so speak slowly and be gentle.
I recently bought a note 10.1 2014 edition. I rooted the device. then when KITKAT was released, I flashed back to stock and did the 4.4 update. Success. I then tried to root using CF-AutoRoot. this is where the problem occurred. ODIN 3.09 seemed to freeze for a long long time. I disconnected the USB cable and when trying to reboot the NOTE, I get this error message... Firmware encountered an issue...
So now it is in a boot loop of sorts. I can get the Note into download, but when I try to launch ODIN and re-flash the original stock file, it fails....
Enter CS for MD5..
Check MD5. Do not unplug the cable..
Please wait..
P600ueubkm1_P600XARBMK1_Home.tar.md5 is valid
Checking MD5 finished successfully..
Leave CS..
Added!!
Odin v.3 engine (ID:8)..
File Analysis
Setup Connection
Complete (write) operation failed
All threads completed (succeed 0 / failed 1)
I also see this message on the note display (SW Rev. Check Fail. Device:3, Binary:2)
And to top it off, I get USB connection errors (sometimes device not recognized) when I connect the NOTE to the computer.
Can anyone help ?
Many thanks...
biglug said:
Hi,
I am a newb, so speak slowly and be gentle.
I recently bought a note 10.1 2014 edition. I rooted the device. then when KITKAT was released, I flashed back to stock and did the 4.4 update. Success. I then tried to root using CF-AutoRoot. this is where the problem occurred. ODIN 3.09 seemed to freeze for a long long time. I disconnected the USB cable and when trying to reboot the NOTE, I get this error message... Firmware encountered an issue...
So now it is in a boot loop of sorts. I can get the Note into download, but when I try to launch ODIN and re-flash the original stock file, it fails....
Enter CS for MD5..
Check MD5. Do not unplug the cable..
Please wait..
P600ueubkm1_P600XARBMK1_Home.tar.md5 is valid
Checking MD5 finished successfully..
Leave CS..
Added!!
Odin v.3 engine (ID:8)..
File Analysis
Setup Connection
Complete (write) operation failed
All threads completed (succeed 0 / failed 1)
I also see this message on the note display (SW Rev. Check Fail. Device:3, Binary:2)
And to top it off, I get USB connection errors (sometimes device not recognized) when I connect the NOTE to the computer.
Can anyone help ?
Many thanks...
Click to expand...
Click to collapse
got it flashed to kitkat via kies3 and a different computer...if anyone else has a similar issue
biglug said:
got it flashed to kitkat via kies3 and a different computer...if anyone else has a similar issue
Click to expand...
Click to collapse
I'm having a similar issue but when I try to use Kies to do the firmware update it tells me "SM-P605V does not support initializing" Have you seen this message?
I have not.... I have the p600 wifi only and was able to enter my model # and serial # to update the firmware. Sorry I cant be of more help.
Sent from my SM-P600 using Tapatalk
biglug said:
I have not.... I have the p600 wifi only and was able to enter my model # and serial # to update the firmware. Sorry I cant be of more help.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Try using ODIN 1.85 or 3.07 instead of 3.09

[Q] Should I give up on my SGH-T999?

To start out, some basic information. I got my SGH-T999 about 2 years ago and used it for about a year on the Stock ROM before proceeding to root the phone. The firmware version before things when went wrong was android 4.1.2. Everything was working fine until about a few days ago when the phone would stop being responsive after putting it into sleep mode, or the screen will turn black and the whole unit is unresponsive (the latter only occurring while I was in the home screen, not while running any apps. Rather, the phone would be fine while an app is running).
Troubleshoot Stage 1
Initialy, I thought there was some sort of app update that was causing this problem, and so I tried uninstalling a few apps that might have been culprits. Didn't work. On occasion, the phone would freeze up while i was trying to uninstall the app. So reading around, someone mentioned that it was possibly the TouchWiz Home that was acting up and I should, clear cache. So I rebooted into recovery (I had the clockworkmod recovery from the initial root). Cleared user data/factory reset as well as clear cache. Didn't work. At this point, the phone was restarting itself almost instantly after booting into the lock screen. I searched a bit more about why this would happen, and came across a post saying that I could be a faulty power button. I actually didn't want to physically alter my phone in any way, so I decided to try to do something with the software first before resorting to altering the physical phone.
Troubleshoot Stage 2
Next thought process was that maybe somehow an OTA was pushed onto my phone and now the firmware is screwed up because of it. So reading through many posts on XDA, I came upon this thread (http://forum.xda-developers.com/showthread.php?t=1771687) for a pre-rooted version of 4.3. I figured, if I was going to re-flash the firmware, I might as well go to the latest one. I proceed to go through the process of flashing the firmware with Odin 1.85, leaving Auto Reboot and F. Reset Time checked. Odin flashes PASS message and I unplug the phone and wait for the reset. Phone starts up all the way past all the logos and to where the home screen was supposed to be. But there was no home screen, just a black screen with only the pull down menu at the top and a message saying "Unfortunately, Settings has stopped working". This message would keep repeating even after pushing the ok button. Next thought process is, maybe TouchWiz is acting up still. So I boot to recovery, reset/format to factory, clear cache, and reboot. Now the phone wont boot past the Samsung logo. Tried to boot to recover again, phone won't boot to recovery anymore. Tried to re-flash the same exact firmware again and this time, odin had some trouble. It would sometimes stop working where it is loading the main code at which point I check the task manager to see if it is still running processes or utilizing any of the computer resources to communicate with the device. I would then have to unplug the phone and reset by removing the battery. This kept occurring about 2 more times before it successfully finished and on doing so, the original problem when I first flashed it was still there.
Troubleshoot Stage 3
Ok, maybe my phone doesn't like the pre-rooted firmware. Looked around XDA again and found this thread (http://forum.xda-developers.com/showthread.php?t=1949687) and downloaded the stock firmware. I stayed with android 4.3 because i read that I can no longer downgrade to a previous android version. Proceeded to flash the Stock firmware 4.3 using Odin 1.85. The process completed on the first try. SUCCESS!! Boot up phone, got past logo, home screen appeared. SUCCESS!! Here, I thought that I was done and my phone was finally working again. So I begin to tweak the settings for my own preferences. I didn't flash anything else or try to root the phone again. I was just plain using the Stock 4.3 firmware that I got from the thread above. After about 10 or so minutes of using the settings, the phone freezes and becomes unresponsive. Won't restart by holding the power button or return to the home screen with the home button. Only other option was to remove the batter and restart the phone. This time, the phone doesnt make it past the Samsung logo screen, and I can no longer boot into recovery. It was stuck on a boot loop and could only be turned off by removing the battery. It didn't occur to me that I should flash Clockworkmod Recovery to reset/format to factory and clear cache as I have read previously and thought that I could just re-flash the stock again. Nope, the same issue came up in Odin as it did with the pre-rooted firmware. Again, I went through the process of checking that Odin was no longer communicating with the phone before unplugging and restarting the procedures to flash the firmware. After about 3 times, the 4th time after unplugging, the screen that tells you "Firmware upgrade encountered an issue, Please select recovery mode in Kies & try again". And when I try to flash again using odin, I get the following message
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Troubleshoot Stage 4
New problem! I now no longer have a PIT partition........and reading around, I found this thread (http://www.sammobile.com/forum/showthread.php?t=15719) of someone who has the same error message coming up in Odin. Thus, I found the PIT file via this thread (http://forum.xda-developers.com/showthread.php?t=1848267&page=4) using the link given by DocHoliday77. Downloaded the T999_16GB.pit as the back panel of my phone indicated that the phone was 16GB. I begin trying to flash with Odin 1.85, checking Auto Reboot, re-partition, and F. Reset Time, including the PIT file and using the Stock 4.3 firmware. This didn't work and only came up with the following error message
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Set PIT file..
<ID:0/012> DO NOT TURN OFF TARGET!!
<ID:0/012> Complete(Write) operation failed.
<ID:0/012> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Tried, the same procedure with the pre-rooted 4.3 firmware, still the same message. And haven't gotten past this point since.
Looking back at what I choose to do to try an fix this shutting down problem, I realize there were a few things I could have tried before moving on. But now what I really want to figure out is whether or not my phone can be saved. What have I not tired and what is the end of end to rescue this phone or if its even worth rescuing. I read that JTAG would be the final resort, and I will take that into consideration. Any feedback on what procedures I could've missed would be great as well (for future reference). Thanks for reading this long post and I really do hope I can get this resolved.
I'll try to answer some of this but tbh, tl:dr.
I can very much appreciate a very thorough and detailed post when someone is asking for help. Don't take this the wrong way, but this was a bit much. I could've answered hours ago, but didn't have the time to read it. More importantly though, the majority of people will see how long it is and just close the thread and move on. Like I said, details are good to include, but it gets to a point where it's too overwhelming. Right now I don't even remember a good chunk of what you wrote, and I wasn't able to read it all to begin with.
Not trying to lecture you or anything, but wanted to address it in case it can help you in the future.
I'll try to answer what i can real quick... first, don't use Odin 1.85. That is a very old version. You should only use 3.07 or above. Best to stick with 3.09 or 3.10.
Try the pit file with one of those.
Put the pit file in the pit section and make sure re-partition is checked. Put the firmware in AP. F-Reset time and auto reboot should also be checked, but nothing else.
It does sound a lot like a faulty power switch probably caused all of this. The constant rebooting, crashing and boot looping can and will cause corruption. This is probably what happened to its internal pit. if so, it is very highly likely there is more corrupted data on some of the individual partitions. Depending on which ones, you may or may not be able to fix it without a jtag service.
It is also possible the memory itself could be damaged. If this is the case, the only option is a motherboard replacement. You probably won't know this for sure though unless you try a jtag repair and it fails.
I will say that if the power button is faulty, you should absolutely get that fixed before doing much else. Otherwise it could just bring you right back to where you are now.
If it were me, I would look for a device on ebay with a broken lcd, but a good motherboard with clean imei. Then swap the board. Otherwise it seems to me you'd be spending money on repairs that may or may not work.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Thanks you so very much for the reply! Sorry that it was long and looking at it again, It really is TL: DR. I will keep that in mind for any future posts.
I have tried different versions of Odin 3.04, 3.06, 3.07, 3.09. The first two version also give the same message as version 1.85 while the latter two stall at initializing for more than and hour and there doesn't seem to be any progress. I will try Odin 3.10 and see what happens there.
I guess buying a broken LCD phone would be the best course of action cost-wise afterwards if Odin 3.10 doesn't work. Again I really can't thank you enough for all the help and taking the time to read my post.
Quick tip on buying used devices like that...Be Careful! Pay extra close attention to how every listing is worded. Only buy ones that say things like:
Fully functional except display
Powers on but no picture
Some will try to trip you up by using "clever" phrases, or trying to lead you to assumptions. Also, try to only but from sellers with excellent ratings and a large number of them. They will be more likely to help you if you have a problem.
Good luck!
Sent from my SGH-T999 using Tapatalk

Death S4 mini / hard brick

Hi, suddenly my S4 Mini crashed and it doesn't boot up anymore.
It doesn't enter into recovery mode, but enters into download mode.
So I flashed i flashed the stock firmware via Odin and the procedure freezes in the beginning, so i tried 2-3 times and now my phone is a paperweight, completely dead.
How can I fix it? the JIG USB will resolve the problem?
Thanks
Bye
I got same issue 1 year ago. My phone getting Samsung logo and restarting all the time. I flashed many roms in 1 day. Phone getting hot while flashing rom. Also weather is too hot. Unfortunately i burned my phone's hardware partition (I think I burned baseband).
I thought I gave my phone to phone repair shop which has jtag. I don't want to gave it Samsung service because I lost my guarantee with rooting it. But my father said "you already have guarantee. 2 years didn't exist after you bought your phone. You should gave your phone Samsung service"
I gave it to Samsung authorized service. I said that I was upgrading my phone via Kies. (I was too excited while I was saying this) After that my phone couldn't turn on. (I know I told lie but I need to get fixed my phone without money ? )
After 3-4 day i went there again to take my phone. They gave my phone and told me "your phone's mainboard and sub (charging input socket) were changed.
I was shocked ?. They didn't controlled my phone if it was attained knox counter.
Sorry for my bad English.
Maybe I can't help you but I wanted to share this event that I lived it.
GT-I9190 cihazımdan Tapatalk kullanılarak gönderildi
Odin blocks in this point:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9195XXUAMF5_I9195ITVAMF2_I9195XXUAMF5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> tz.mbn
<ID:0/008> NAND Write Start!!
Same thing happened to my S4 mini Duos on 11th February. My phone was on Stock Samsung Firmware, Custom Recovery, Custom Kernel, and of course rooted.
I changed to stock in December. It was working fine for a month. I texted my friends and after 15 minutes I took out my phone to make a call and I found it was powered off. Then I tried to power on. No response. Then I charged the battery using external battery charger as my phone was not showing charging logo.
After some time, it showed logo and entered Download mode. But didn't enter Recovery mode.
I did a complete flash (nandroid erase all) through ODIN. Not entering custom recovery as well as stock recovery. It shows "recovery booting" but restarts right after that. Stuck on Samsung logo. Just vibrates and reboots again and again.
I gave the phone to a Samsung Authorized Service Center, they declared my phone as hopeless. They say the motherboard is faulty and it needs replacement.
I never even dropped my phone or overclocked the cores. I had been using it gently. I really don't know what to do now. Here I am, looking for a solution.
So, I see that there are more and more people with a same problem and there is no clue what is the cause of the problem. I started a topic with a same question about month ago, but without any reaction.
Hi... I got something similar going on.
Samsung s4 mini running CM13 NIGHTLY (cm-13.0-20160214-NIGHTLY-serranoltexx.zip) Yesterday, I Downloaded Feb 18th nightly and decided to update other apps as well.
Today, as I updated some apps on the play store and got "insufficient message". Decided to make SD Card part of internal memory. Went thru the process and it transferred about 3GB into the SD Card. Afterwards, I proceeded with the CM update. A small screen came up saying it was preparing for upgrade and then it rebooted in recovery, as usual, but this time it blacked out. It just wont go into recovery mode.
Should I try to boot with a different SD Card with the CM update? Is there a way to do it on download mode?
Any suggestions would be great! thanks

Samsung S9+ Live Demo Unit (How Can I Flash?)

Hello there!
I have a S9+ Live Demo Unit and I want to remove the retail mode.
I made it with a Note 8 (N950X). It was easy, I installed Odin in my PC, and I installed the non-retail firmware.
Can I do the same in my S9+?
HELP PLEASE!
Short answer yes. How did you get a demo unit this quickly?
Why do you want to install original firmware into an LDU? Stolen from store?
stearic said:
Short answer yes. How did you get a demo unit this quickly?
Click to expand...
Click to collapse
I work in mobile phone sector.
Fozec said:
Why do you want to install original firmware into an LDU? Stolen from store?
Click to expand...
Click to collapse
Because I have one, it's a gift, and I want to use all the features (except SIM).
Can you help me? (IT'S NOT STOLEN, 100% LEGAL)
Help please, I need to use it as a normal phone (using only WiFi)
Do I have to install Odin in my PC and flash the S9 with the original firmware?
Cristianeon said:
Hello there!
I have a S9+ Live Demo Unit and I want to remove the retail mode.
I made it with a Note 8 (N950X). It was easy, I installed Odin in my PC, and I installed the non-retail firmware.
Can I do the same in my S9+?
HELP PLEASE!
Click to expand...
Click to collapse
Starting with the S8/Note8, Samsung has removed the baseband chips (actually has never included it in the factory) so even if you manage to flash it with stock firmware, it will never pick up a signal no matter what you do. And no, you can't solder in the baseband chips, they are custom chips and extremely difficult to solder being fine pitched surface mounts.
You best option is to try to flash it with the latest stock firmware, disable the MDM security, and use it on WiFi only.
By the way, the N950"X" version is not even a US Qualcomm model, but an international Exynos based main board, so don't waste your time trying to flash the "U/U1" firmware. Try the international "F" version, but most likely it will only accept the specially modified "X" firmware.
billa said:
Starting with the S8/Note8, Samsung has removed the baseband chips (actually has never included it in the factory) so even if you manage to flash it with stock firmware, it will never pick up a signal no matter what you do. And no, you can't solder in the baseband chips, they are custom chips and extremely difficult to solder being fine pitched surface mounts.
You best option is to try to flash it with the latest stock firmware, disable the MDM security, and use it on WiFi only.
By the way, the N950"X" version is not even a US Qualcomm model, but an international Exynos based main board, so don't waste your time trying to flash the "U/U1" firmware. Try the international "F" version, but most likely it will only accept the specially modified "X" firmware.
Click to expand...
Click to collapse
You are wrong. I made It by myself.
I'm Spanish, so I have the Exynos model.
I installed the F Firmware And everything OK.
Cristianeon said:
You are wrong. I made It by myself.
I'm Spanish, so I have the Exynos model.
I installed the F Firmware And everything OK.
Click to expand...
Click to collapse
In the US we have the "X" model which I have physically opened up and the baseband chips are missing, while on other models they removed the sim card contacts completely and it's not resolderable. Look they are not dummies, they know exactly what they're doing.
You can clearly see the empty solder pads which normally are populated with chips. So please don't jump to conclusions so fast before checking the facts.
Cristianeon said:
You are wrong. I made It by myself.
I'm Spanish, so I have the Exynos model.
I installed the F Firmware And everything OK.
Click to expand...
Click to collapse
so you already did it on Note 8 and need help with S9?
why dont you try it and let us know?
I HAVE SAMSUNG S9+ LDU TOO IN PAKISTAN BUT STILL FACING ISSUE TO FLASHING SM-G965X TO SM-G965F PAK FIRMWARE DOWNLOAD FROM UPDATO.COM
<ID:0/003> 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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> param.bin
<ID:0/003> dqmdbg.img
<ID:0/003> userdata.img
<ID:0/003> Home Binary Download
<ID:0/003> Total Binary size: 4886 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> up_param.bin
<ID:0/003> cm.bin
<ID:0/003> keystorage.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
SOFTWARE STILL WORKING ON IT NOTHING GOING ON PAST 20 MINS
FIRMWARE INFO
Country / RegionPakistan
PDAG965FXXU1ARC5
Product CodeAK
CSCG965FOXM1ARC4
PhoneG965FXXU1ARC4
So, did it work on the S9+? which firmware did you flash?
Software working good all option done only samsung account not working like samsung store,theme store etc.
what did you use to flash the s9+ live demo cause nothing is working for me
Kwamisky said:
what did you use to flash the s9+ live demo cause nothing is working for me
Click to expand...
Click to collapse
Share your phone systems details csc bootloader etc etc then ill send you download link for s9 or s9+
Cristianeon said:
Hello there!
I have a S9+ Live Demo Unit and I want to remove the retail mode.
I made it with a Note 8 (N950X). It was easy, I installed Odin in my PC, and I installed the non-retail firmware.
Can I do the same in my S9+?
HELP PLEASE!
Click to expand...
Click to collapse
yo tambien trabajo en telefonia movil y tengo un demo s9+ de una promo de samsung. me lo he quedado, consegui flashearlo y ponerle una room stock y quitarle el modo demo.. lo unico que no he podido es hacer que pueda tener una tarjeta sim y tener internet 4g o llamar.. incluso lo rotee pensando que podria asi meterle un imei a la fuerza con las aplicaciones para cambiarlo.. y nada.. no lo he conseguido.. ya no se que mas hacer..
Dude help me to which firmware you Installed please help me by saying via Odinsta?
Cristianeon said:
You are wrong. I made It by myself.
I'm Spanish, so I have the Exynos model.
I installed the F Firmware And everything OK.
Click to expand...
Click to collapse
Which f firmware you Installed please give me tutorial please:crying:
Thanks for your experience. I am stuck with same case. I have been trying to install the F version on the US Galaxy S9+. The greater problem my LDU has is that the date is incorrect and no settings is enabled to allow me make any adjustment. Every necessary settings greyed out. Odin flash attempts all failed and Samsung Kies will always say I should enable USB debugging to even see and recognize my device but that option in developers mode is all greyed out and not allowing enabling. Same thing with factory reset not allowed. What can I do to at least use the Wifi because now it cannot connect due to incorrect date setting still whowing March 2018?
shalomige said:
Thanks for your experience. I am stuck with same case. I have been trying to install the F version on the US Galaxy S9+. The greater problem my LDU has is that the date is incorrect and no settings is enabled to allow me make any adjustment. Every necessary settings greyed out. Odin flash attempts all failed and Samsung Kies will always say I should enable USB debugging to even see and recognize my device but that option in developers mode is all greyed out and not allowing enabling. Same thing with factory reset not allowed. What can I do to at least use the Wifi because now it cannot connect due to incorrect date setting still whowing March 2018?
Click to expand...
Click to collapse
If you want to factory reset but cannot enter recovery for whatever reason, set up security to wipe your device if the wrong code has been entered 10 times, then enter the wrong code 10 times
Samsung Galaxy S9+
*Detection* said:
If you want to factory reset but cannot enter recovery for whatever reason, set up security to wipe your device if the wrong code has been entered 10 times, then enter the wrong code 10 times
Click to expand...
Click to collapse
My problem is that those security settings are not enabled for change as they are greyed out. So I wouldn't even know where to go to set up security to wipe off device. Moreover, I don't usually log on to the phone with code. Are you suggesting I set up code to open the phone screen so that I can enter wrong one or which other code are you referring to? Thank you Sir.

Categories

Resources