Develop Bugs

[Q] Defy is dead on flashing

Hi,
I was flashing the UK Sbf on a unbricked phone using RSD Lite 4.9. During the flashing process, suddenly phone turned off and disconnected with RSD Lite displayed a message "Failed, Device disconnected error".
I actually had 40% battery b4 starting the process. is it the low-battery problem?? Now, I am not able to do anything with the phone. When I have plugged in for charging, it says nothing. Is it dead?? But, when I have connected to the USB, a white small light comes on the top.
How to get my phone back? My phone is from Honk kong and i have rooted it as well.
Would u please guide me if we can do something??
Many thanks in advance,
Regards,
Naga

Charge your battery in another phone or in an universal charger and try to flash once again. Or you can repeat flashing procedure on another PC.

nagnrik said:
Hi,
I was flashing the UK Sbf on a unbricked phone using RSD Lite 4.9. During the flashing process, suddenly phone turned off and disconnected with RSD Lite displayed a message "Failed, Device disconnected error".
I actually had 40% battery b4 starting the process. is it the low-battery problem?? Now, I am not able to do anything with the phone. When I have plugged in for charging, it says nothing. Is it dead?? But, when I have connected to the USB, a white small light comes on the top.
How to get my phone back? My phone is from Honk kong and i have rooted it as well.
Would u please guide me if we can do something??
Many thanks in advance,
Regards,
Naga
Click to expand...
Click to collapse
Don't worry.
If the white led brights on the phone, it is possibly charging.
If not, read the following thread, there's the solution:
http://forum.xda-developers.com/showthread.php?t=926012
BE CAREFUL WITH IT!

Well, thanks for the quick repsponse guys... I try this... Hope, it works...

I have tried it... no luck.... But, I am a bit sure I have connected those wires properly n mounted the battery..... I got this mobile from Honk-kong.. I was actually flashing a UK Firmware (SBF)... Does it matter?? I did not wipe or any resets prior to flashing.. I have successfully rooted the mobile after Hard trails... thought of flashing it to froyo... But, mistakenly did this... )..... It went well till 73% and suddenly disconnected error and phone turned off with a white light on the top..
Any other way other than sending it to Motorola support... And I am in Dubai now.. this mobile is still not available here... so no local support from Motorola end. I have to pack it to either UK or HK...
Any trails???
Many thanks in advance.....

What .sbf are you flashing? The 2.34 or 2.5.1?

nagnrik said:
I have tried it... no luck.... But, I am a bit sure I have connected those wires properly n mounted the battery..... I got this mobile from Honk-kong.. I was actually flashing a UK Firmware (SBF)... Does it matter?? I did not wipe or any resets prior to flashing.. I have successfully rooted the mobile after Hard trails... thought of flashing it to froyo... But, mistakenly did this... )..... It went well till 73% and suddenly disconnected error and phone turned off with a white light on the top..
Any other way other than sending it to Motorola support... And I am in Dubai now.. this mobile is still not available here... so no local support from Motorola end. I have to pack it to either UK or HK...
Any trails???
Many thanks in advance.....
Click to expand...
Click to collapse
Can you start it in flash mode or recovery mode?
(vol up + power or vol down + power)

Hi, I am not sure of this as I have downloaded too many files for rooting, froyo upgrade and other stuffs.. But the file name is "UK_rom.sbf" and size 370MB+. are there any consequences??

avers said:
Can you start it in flash mode or recovery mode?
(vol up + power or vol down + power)
Click to expand...
Click to collapse
Yeah, I have charged it for sometime and trying to POWER+VOLUME-UP for boot loader only... It looks like dead, no repsonse from it... when I have put it for charging, it did not show any indication that it is being chraged.... anything went wrong???

nagnrik said:
Hi, I am not sure of this as I have downloaded too many files for rooting, froyo upgrade and other stuffs.. But the file name is "UK_rom.sbf" and size 370MB+. are there any consequences??
Click to expand...
Click to collapse
Ok, go here http://and-developers.com/sbf:defy and download an sbf, I use 2.5.1, however once you flash it you cannot downgrade it,,, There is owever a lot of develpment more recently for it, im running a smooth froyo on it now.
Anways, pick one, extract that file to your RSD folder.
Open your RSD lite
Pull the battery from your phone, wait a few seconds, put it in, and boot into bootloader (vol up and power).
Plug the phone in, as long as the white light comes on you should be good...
select your new sbf file and hit start on RSD, you should work..
Now depending on what you had prior, your only option may be to flash 2.5 which is what I had to do.. Again, Id rather have a phone that turns on then complain about not being able to downgrade..
Let me know

good luck from my side
hint: never used a file called "UK_rom.sbf" - little unspecific ;===)
-nevermind- good luck once again, hope you bring it back to work!

Well, mobile it self is not turning on... It is a strange issue.. And fortunately, It has been launched here a 3 days ago in UAE.. I went to a store to check if the issue with the battery.. I have replaced and tested it out.. No luck.. I did not c the % of the charging. May be Bootloader requires more charging than normal powering... Anyways, I am decided to submit it to Motorola here, they must help us out...
Thanks everyone here for the wonderful support.... love XDA.... keep u posted as soon as it is fixed.... Many thanks again....

I deserve a beer for this!!!
Did the same goof up....got greedy for froyo and couldn't resist f&(*ing my defy........was cribbing for 8 hours while figuring out the solution.... escaped office for this.....but finally finally .......i saved it.......man.....if blood is the answer for blooood....then it has to be 2.51 for 2.51....
please click the link below for the only feasible 2.51 sbf....flash your defy in a standard manner and kabbooooom........defy reincarnated...
:
hope it works for all the good people in need....it worked for me (Atleast my defy turned on still observing how it works)..
Defy 2.51 sbf

Sorry for being late to the party, but how did this turn out eventually?

Think ive killed it :/ Tab S2 T813

ok so bottom line is, I was in the middle of flashing official rom when at about 25% it failed. Don't ask why! (i still had recovery at this point) so I went ahead and cleaned absolutely everything thinking i'll just try and reflash as before. Now with power lead out it won't switch on at all and when power is supplied it shows message "An error has occured while udating the device software." loops at approx 3 sec intervals cant do anything with it.
Ive tried everything I can think of all to no avail! yes its my own fault bla bla bla just wondering if i act have f***** it.
Thanks to anyone with any ideas

You probably going to get a better help at TAB S2 board this is for the tab S1.
If it is hard bricked there is JTAG methods that can help, just need to find one for your device, not easy though.
But all I can do is share my experience with something like this, in a more "cheap" way than JTAGs, dunno if it helps:
I never had a similar problem on the tab S. But in the past a galaxy player 5.0 of mine had a very similar problem (as far I remember the screen just powered the back light but without any letters or simbols)
in 2012, I bricked it trying to mount a swap partition (280mb RAM ftw) accidentally pointing the wrong partition, and got the entire internal storage corrupted.. everything.. system, bootloader, recovery etc
My player was turning on only connected to a USB or charger, like yours. in fact It was hard bricked
I was able to recover it using Linux (because it is the only system able to communicate with the bricked device I had)
The problem is that everything need to be very specific, for example I used a software made for the galaxy s1 to "revive" my player 5 (both have the same hardware) it just made the device be detected via ADB. So I needed to prepare a SD with the same size as the internal storage (in this case 8gb) using the Linux terminal to mount in the SD an exactly schematic of the internal memory using a dump of another device that a xda user shared, (the dump was empty only with the bootloader, recovery etc) but it still had 8gb decompressed. So after that I used ADB to push the SD card content to the internal memory. And it get back to life \○/
Well.. it took me 1 week with a guide!! On the trial and error method. But it worked.. not perfectly, I get bootloops every time I try to flash a rom via Odin, but recovery works, and I have the device working until today

Hi, I Greatly appreciate your reply and advice. Think tho that your solution is a bit beyond my know how I know a little about ADB etc but i would have difficulties in compiling necessary files to sideload. Also many tanks for the link din't realise. Thanks Pal!

Alpha1BA said:
ok so bottom line is, I was in the middle of flashing official rom when at about 25% it failed. Don't ask why! (i still had recovery at this point) so I went ahead and cleaned absolutely everything thinking i'll just try and reflash as before. Now with power lead out it won't switch on at all and when power is supplied it shows message "An error has occured while udating the device software." loops at approx 3 sec intervals cant do anything with it.
Ive tried everything I can think of all to no avail! yes its my own fault bla bla bla just wondering if i act have f***** it.
Thanks to anyone with any ideas
Click to expand...
Click to collapse
If you can get it in to download mode you can flash stock rom back on it.......refer to xda samsung tab s2 for more details on this........

thx for reply but it reboots approx every 3 seconds so I dont have enough time to do anything with it :/

Alpha1BA said:
thx for reply but it reboots approx every 3 seconds so I dont have enough time to do anything with it :/
Click to expand...
Click to collapse
Plug in changer and push power and volume up and down all together and you will see the battery charger icon then you can get it in to download mode from there.....

stinka318 said:
Plug in changer and push power and volume up and down all together and you will see the battery charger icon then you can get it in to download mode from there.....
Click to expand...
Click to collapse
Stinka ure a superstar (atm!) I did as you suggest to no avail but I noticed a slight increase in the time it took to start rebooting again. I do not know which buttons did this but some 20 later it lasted long enough for me to be able to flash twrp. Now i havent actually tried that as yet as i wanted to check with you first... I have the battery logo on screen, i tried recovery and it started as it should but then rebooted, now im unsure at this time whether the battery is almost dead or not so i got it on charge and have the grey battery with a white flash inside... is this what i want for now until its charged? if so i'll keep you informed thamnks more than u know if uve helped me fix this, the reason i was flashing was because when i received it (no warranty!!) the screen sometimes flickered and it would constaly end up rebboting after digging around re that im lead to believe it need a new battery and for the connecting wires to be resoldered. Anyways thanks again n as I say i'll keep this updated
Cheers
Tony

one of the probs i hab/have with this unit is that it takes approx a day to fully charge!!! when i received it the screen flickered on the odd occasion but it was rebooting much more frequently. It came with stock n not messed with previously (i new this prior to purchase so got it for right price thinking it only needed flashing, how wrong was I!!!) so I flashed and encountered the above mentioned problems! thanks to stinka I surprisingly managed to flash a recovery... now provided all goes to plan, which rom would one suggest for stability and generally hassle free and prusuming the aforementioned probs, rebooting etc are still there what could i try to stop that? other than a debloated stock I found Lineage an excellent rom but still the problems got so bad the unit became unusable and was lucky not to go out the window. Im thinking do i start with a replacement battery and check the wires etc or could this still be a software issue??

if i endevoured to do the hardware myself would I attempt it by removing screen or the base for access to battery/connector??
Thanks again

In the tab s1 the best way is removing the back cover, but for some reason tab s2 seen to be the screen... at least in this guide: https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+S2+Battery+Replacement/56616
Look like alot more complex than the s1 :/

RoIlingThunder said:
In the tab s1 the best way is removing the back cover, but for some reason tab s2 seen to be the screen... at least in this guide: https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+S2+Battery+Replacement/56616
Look like alot more complex than the s1 :/
Click to expand...
Click to collapse
Thanks for that!!!
Tony
does look somewhat OTT!!!

will i have to odin stock first then flash rom i want or will it go straight from first flash via twrp considering there is absolutely nothing on phone at mo apart from twrp.

Alpha1BA said:
if i endevoured to do the hardware myself would I attempt it by removing screen or the base for access to battery/connector??
Thanks again
Click to expand...
Click to collapse
My guess is your issue is lack of charge in the device. That's the reason for the flashing failure and the reboot loop with the firmware error.
Bang it on charge for a while then irrespective of what it's doing, whether it's looping or not, hold POWER + HOME + VOL DOWN until download mode appears.
Reflash the stock firmware with odin.

swapped battery and reflashed stock via odin. It has helped although the issues are all still there its just they happen less frequently which doesnt mean its any less frustrating.

Odin fails to flash

Hello, just picked up a used tab s t705w bell in good shape. Ive tried to flash the original 5.02 as well as autroot and another original image as well. All of them fail. Im using the latest version of Odin. The connection says its ok as per com port than when it gets to boot.img it stops and fails. Ive tried 2 USB cables as well as all my USB ports to no avail. Please help as to what I'm doing wrong, thanks.

Heres a pic

Update: tried with laptop still same thing, is there anybody that can offer a suggestion? I even unplugged the battery and plugged back in. I also tried several older versions of Odin.

Well since nobody knows what to do my research indicates possibly nand chip has failed meaning hardware issue. Gonna look at returning it.

cesandoid said:
Well since nobody knows what to do my research indicates possibly nand chip has failed meaning hardware issue. Gonna look at returning it.
Click to expand...
Click to collapse
Hi,
Did you end up fixing the issue? I think I have the same issue as yours on a SM T800. It came with 4.4.2 so when I tried to update to Marshmellow it failed and it restarted fine, and it told me to update via my pc using Kies or smarth switch. So I did so and guess what happened Smart Switch failed as well but now it bricked the tablet. So when Smart switch tries to install the recovery, same thing. So I now have a brick! So I am trying to find out if there was a solution or not. If not I will just have to wear it.
Thanks.

hello, identical problem ,ODIN does not complete the procedure,Tablet locked in the emergency screen.... no key combination works........
any ideas?
TEX

tex_kit said:
hello, identical problem ,ODIN does not complete the procedure,Tablet locked in the emergency screen.... no key combination works........
any ideas?
TEX
Click to expand...
Click to collapse
You're saying you can't get it back into the Odin download mode?
Hold HOME+ VOLUME UP+VOLUME DOWN+POWER. (Keep holding)
When the Samsung splash screen comes up, let go of the VOLUME UP button.
When the Odin warning screen comes up, let go of all buttons and click VOLUME UP.
Even when I was sure mine was soft-bricked, I was able to get it into Odin download.

wellersl said:
You're saying you can't get it back into the Odin download mode?
Hold HOME+ VOLUME UP+VOLUME DOWN+POWER. (Keep holding)
When the Samsung splash screen comes up, let go of the VOLUME UP button.
When the Odin warning screen comes up, let go of all buttons and click VOLUME UP.
Even when I was sure mine was soft-bricked, I was able to get it into Odin download.
Click to expand...
Click to collapse
thanks ,executed the procedure and finally I’m back in the Odin screen.Unfortunately the error has recurred ........ the end of the procedure shall be interrupted .....
[/IMG]
end of the test.
More info:last update to Android 6...enter in Odin Mode . I manage to start the installation but towards the end of lock , tried both with FIR. OMN-T805XXU1ANFB-2014,(European generic), both with OMN-T805XXU1CPL1_T805OMN1CPK1-20161212(dedicated version

tex_kit said:
thanks ,executed the procedure and finally I’m back in the Odin screen.Unfortunately the error has recurred ........ the end of the procedure shall be interrupted .....
[/IMG]
end of the test.
More info:last update to Android 6...enter in Odin Mode . I manage to start the installation but towards the end of lock , tried both with FIR. OMN-T805XXU1ANFB-2014,(European generic), both with OMN-T805XXU1CPL1_T805OMN1CPK1-20161212(dedicated version
Click to expand...
Click to collapse
In my limited experience with Odin, I find it to be a very stable, robust, and reliable application. Having said that, and not knowing what version you're using, the usual suggestions are:
Try another (older) version of Odin.
Try another USB cable.
Always use a USB 2 port.
Try a different firmware package making *certain* it's for your model tab. (<- This is what's most suspect - IMHO.)
As long as you can still invoke the Odin downloader on your tab, there's still hope.

Good morning, Sir
News update, detailed search carried out, found the latest specific Samsung Firmware, (XEH-T805XXU1CPL1-20170111202424 with MM.)
The procedure with Odin has been successfully completed. (end of good news) At the end of the operation the tablet remains with the logo samsung bright intermittently . performed hard reset but remains stuck on the initial logo samsung always bright intermittently.
Suggestions?
TEX

tex_kit said:
Good morning, Sir
News update, detailed search carried out, found the latest specific Samsung Firmware, (XEH-T805XXU1CPL1-20170111202424 with MM.)
The procedure with Odin has been successfully completed. (end of good news) At the end of the operation the tablet remains with the logo samsung bright intermittently . performed hard reset but remains stuck on the initial logo samsung always bright intermittently.
Suggestions?
TEX
Click to expand...
Click to collapse
PM SENT.
Yup. Been there. Done exactly that. I fixed it by subscribing to SamMobile, then paying for and downloading the OEM firmware. That's probably the best news, You can always get back to a box-stock condition. If you have the patience, you can download the firmware for free.
EDIT: Once I got back to stock, I looked for and found:
DAMMIT! I keep forgetting we have two different tabs. Obviously Klimtwifi is wrong for you.
lineage-14.1-20200321-UNOFFICIAL-klimtwifi, installed it with Odin3_v3.11.2 (Not sure it matters.)
Then rooted it using Odin: https://android.gadgethacks.com/how-to/android-basics-root-with-cf-auto-root-0167401/
And, once rooted, installed the Official TWRP app from Google Play. I always use the next older version of TWRP (twrp-3.3.0-0-klimtwifi) because TWRP doesn't like me much.
Then, rebooted into recovery and flashed GApps (open_gapps-arm-9.0-nano-20200417)
FWIW - This is from feeble memory, and I still have all the files - both those that worked and those that didn't - all in the same folder. So if something doesn't work for you, I've got what worked for me.
All said, getting LineageOS on this thing was far, far simpler that trying to get it back to stock.

All said, getting LineageOS on this thing was far, far simpler that trying to get it back to stock.???
IS A build guide available ??
The Samsung Galaxy Tab S 10.5 LTE is no longer maintained.
I just thought I’d switch to android 4.4 ....
The problem comes from the loss of boot files?
TEX

tex_kit said:
All said, getting LineageOS on this thing was far, far simpler that trying to get it back to stock.???
IS A build guide available ??
The Samsung Galaxy Tab S 10.5 LTE is no longer maintained.
I just thought I’d switch to android 4.4 ....
The problem comes from the loss of boot files?
TEX
Click to expand...
Click to collapse
This should get you where you want to be: http://www.lineageosdownloads.com/download-galaxy-tab-s-10-5-lte-lineage-os/
I'm not sure what caused the problem in the first place. I was just very relieved to see it boot when i got the stock ROM back on it.
Did you restore yours back to stock? It's good practice.

wellersl said:
This should get you where you want to be: http://www.lineageosdownloads.com/download-galaxy-tab-s-10-5-lte-lineage-os/
I'm not sure what caused the problem in the first place. I was just very relieved to see it boot when i got the stock ROM back on it.
Did you restore yours back to stock? It's good practice.
Click to expand...
Click to collapse
Good morning,
The tablet is Hungarian (made search via samsung and s n), I install unique files (extension .md5).
installed the version K.K. 4 , the only novelty the presence during the first restart of the colored logo, performed manual restart and hard reset /wipe ,
At the end it remains with the Samsung logo bright intermittently (Samsung logo power etc.etc.). Found the multifile firwarware.
Odin does not recognize extension . enc4 and (oddly ) I find nothing to extract Files...
TEX

tex_kit said:
Good morning,
The tablet is Hungarian (made search via samsung and s n), I install unique files (extension .md5).
installed the version K.K. 4 , the only novelty the presence during the first restart of the colored logo, performed manual restart and hard reset /wipe ,
At the end it remains with the Samsung logo bright intermittently (Samsung logo power etc.etc.). Found the multifile firwarware.
Odin does not recognize extension . enc4 and (oddly ) I find nothing to extract Files...
TEX
Click to expand...
Click to collapse
Did you find your model number on the SamMobile website? That's really where you need to start. Once you have the correct OEM firmware, using Odin to install it is a no-brainer. You need to get back to stock before you can move on to custom.
What is your complete model number?
Send me a private message. I think I may be confused and am causing you extra confusion.

wellersl said:
Did you find your model number on the SamMobile website? That's really where you need to start. Once you have the correct OEM firmware, using Odin to install it is a no-brainer. You need to get back to stock before you can move on to custom.
What is your complete model number?
Send me a private message. I think I may be confused and am causing you extra confusion.
Click to expand...
Click to collapse
Good morning,
Downloaded and installed the latest version SM-T805_t805xxu1cpl1_marshmallow(Android 6.0.1)_Xeh_factory Rom (4 File)_20170111.zip.enc4. (decrypted with an earlier version of samfirm (3.9 ).
the installation procedure of the 4 files, AP, BL, CP, CSC, does not involve problems.
Unfortunately at the end of the procedure the Tablet does not restart automatically, and after its hard wipe reset remains locked on the initial logo samsung always bright intermittently.
During the tests I noticed that holding down the power button tries to start. The second samsung logo stands out completely but does not pass the stage.
The feeling he can’t make it.
A new PIT file?
Tex

wellersl said:
Did you find your model number on the SamMobile website? That's really where you need to start. Once you have the correct OEM firmware, using Odin to install it is a no-brainer. You need to get back to stock before you can move on to custom.
What is your complete model number?
Send me a private message. I think I may be confused and am causing you extra confusion.
Click to expand...
Click to collapse
Good morning, first of all
I want to thank you for your patience and time.
Performed yet another installation test with Odin this time with Android 5 (XEH-T805XXU1BOJ1-20151111094815) similar result, you have precedents.
But with a novelty
.At the end of the installation, the tablet remains off, as in the pretending tests, I try to start it normally but nothing, in addition to the ever-present Logo (Samsung Galaxy tab S) flashing intermittently.
I press the power button for several seconds with the result of making the second samsung logo appear (colored) with an Android loading start, release the button, the device turns off.
By re-activating the flashing logo (Samsung Galaxy tab S) normally.
Holding down the power button starts
Android update - optimization of the accompanying application (192 tot), a few minutes later always with the power pressed, the process ends and the installation of applications begins, after a few seconds, the first APP starts., the tablet turns off.
By turning it on again and the intermittent luminous logo (Samsung Galaxy tab S) reappears.
Repeating the procedure (power button pressed continuously) you get colored samsung logo and the writing (alkalmazàsok telepitèese) installation of applications and turns off.
I perform a wipe data / factory reset obtaining:
--wiping data—
Formatting / data ...
Formatting / cache ...
Formatting / sbfs ....
E: unknow volume for path [/ sbfs]
E: unknow volume "/ sbfs"
Complete data wipes.
I run reboot system now.
The tablet turns on with the intermittently lit Logo (Samsung Galaxy tab S).
By repeating the whole procedure previously described, no changes are obtained.
TEX

alkalmazàsok telepitèese?
Neither Google nor I understand that phrase. Do you?
Irrespective of that, I'm at my wit's end. And, assuming you're following the published directions, you may be looking at a hardware failure.
Just to confirm, before all this started for you, this was a working tablet?

wellersl said:
Neither Google nor I understand that phrase. Do you?
Irrespective of that, I'm at my wit's end. And, assuming you're following the published directions, you may be looking at a hardware failure.
Just to confirm, before all this started for you, this was a working tablet?
Click to expand...
Click to collapse
good morning,
the tablet was working, during a game session started to reboot, always and only with the logo (Samsung Galaxy tab S) bright intermittently, performed hard reset, I did not fix anything. The only news, these days, after Odin, is the complete installation of android 5 with the power key pressed all the time.releasing the tablet key turns off . At the next power on I get the logo (Samsung Galaxy tab S) bright intermittently.
thank you for your patience and professionalism
Tex

This is the screen you see *before* you invoke Odin and connect the tab to your PC?
View attachment 5009263

Galaxy S20 Ultra stuck in Recovery Mode after failed Smwart Switch Update

Hi guys,
I attached my brand new Galaxy S20 Ultra to my PC and started Smart Switch today. The Software showed an update for my device so I downloaded it and started the update process. Unfortunately, Smart Switch got stuck during the update process at 68%. Nothing happened, cables and all still attached. It just didn't proceed any further for hours.
I decided to take the path of stopping the process, using the key combination shown on my device. It now said, recover your device software with Smart Switch Emergency recovery function. I started this and guess what: it also stopped at 68%.
I "rebooted" the device (volume down + power for approx. 10 seconds) and it starts again in recovery mode.
I manually filled in the recovery code and it seemed like Smart Switch was downloading the OS again. Started the recovery process and it is stuck at 68% again.
Now I am just super afraid that I bricked the device by using Samsungs original software.
Anyone her to help or have similar experiences?
Thanks for any advice on how to proceed.
Julius

What exactly were you trying to do? I mean normally you hook up old phone and use smart switch to update new phone. So why was you connected to a PC? It does sound like you bricked it.
So now you probably need to flash the ROM.

I read that smart switch is a good and valid source to check for updates. I never thought that an official Samsung software can be so bad at something so basic, resulting in bricking my phone...

Stop using smart switch to update your phone. You haven't hard bricked it because you still have recovery. It's called a soft brick. Download Odin 13.3_3B from here on xda. Do not use the 13.4 because it's suspected to have a fishy call back to a server from a dll that's in the program folder. Download the atch firmware for your model from sammobile or get it in this s20 ultra forum. You should be able to flash the new firmware.

Thanks @freebee269. Does flashing the firmware with Odin void my warranty or does this only count for rooting devices? (Sorry for stupid questions)

Julius_GER said:
Thanks @freebee269. Does flashing the firmware with Odin void my warranty or does this only count for rooting devices? (Sorry for stupid questions)
Click to expand...
Click to collapse
Odin uses official firmware from Samsung so no warranty voided.

Julius_GER said:
Hi guys,
I attached my brand new Galaxy S20 Ultra to my PC and started Smart Switch today. The Software showed an update for my device so I downloaded it and started the update process. Unfortunately, Smart Switch got stuck during the update process at 68%. Nothing happened, cables and all still attached. It just didn't proceed any further for hours.
I decided to take the path of stopping the process, using the key combination shown on my device. It now said, recover your device software with Smart Switch Emergency recovery function. I started this and guess what: it also stopped at 68%.
I "rebooted" the device (volume down + power for approx. 10 seconds) and it starts again in recovery mode.
I manually filled in the recovery code and it seemed like Smart Switch was downloading the OS again. Started the recovery process and it is stuck at 68% again.
Now I am just super afraid that I bricked the device by using Samsungs original software.
Anyone her to help or have similar experiences?
Thanks for any advice on how to proceed.
Julius
Click to expand...
Click to collapse
What kind of USB Port did you use?
Try again using a USB 2.0 port, Samsung always had problems with it's software and USB 3.0 ports.
Use USB 2.0 and try again.

Hi guys, i have a similar problem as (xReem).
Attached my GT SM-T515/10.1 tab to smart switch where the software was unable to recognise my device!? Was advised to use the Emergency Code function but i have no code due to backing up my data to sd card! I have Magisk and TWRP installed where my device was working beforehand, but since attaching to smart switch, my device is now totally "dysfunctional"!!!
Error message as follows...
...An error as occurred while updating the software. Use the Emergency Recovery function in the Smart Switch PC software. ...
Like i sad, i have no code!!!
I am able to get to the device unlock choice screen and if i choose to restart, my device always boots to the Smart Switch Emergency Code screen?! If i choose the device unlock or download screens, both screens are accessible! Tried to flash my original firmware (BTU-T515XXU3ASK5-20191224095700) using Odin3_v3.14.1 and twrp-3.3.1-6-T515XXU3ASK5-20200215 with no joy (Fail!)
Although i'm totally @"#$%* off about this, as its a new device, i am also curious if someone has ever cracked this... 'Smart Switch No Code' problem before. Hmm...
Anyways, any help appriciated...
Oh! Cannot access recovery at all...
Any help appriciated.

klantee said:
Hi guys, i have a similar problem as (xReem).
Attached my GT SM-T515/10.1 tab to smart switch where the software was unable to recognise my device!? Was advised to use the Emergency Code function but i have no code due to backing up my data to sd card! I have Magisk and TWRP installed where my device was working beforehand, but since attaching to smart switch, my device is now totally "dysfunctional"!!!
Error message as follows...
...An error as occurred while updating the software. Use the Emergency Recovery function in the Smart Switch PC software. ...
Like i sad, i have no code!!!
I am able to get to the device unlock choice screen and if i choose to restart, my device always boots to the Smart Switch Emergency Code screen?! If i choose the device unlock or download screens, both screens are accessible! Tried to flash my original firmware (BTU-T515XXU3ASK5-20191224095700) using Odin3_v3.14.1 and twrp-3.3.1-6-T515XXU3ASK5-20200215 with no joy (Fail!)
Although i'm totally @"#$%* off about this, as its a new device, i am also curious if someone has ever cracked this... 'Smart Switch No Code' problem before. Hmm...
Anyways, any help appriciated...
Oh! Cannot access recovery at all...
Any help appriciated.
Click to expand...
Click to collapse
Did you ever get things working ? If not, when you flashed with Odin - did you use the PATCHED Version ? THis is necessary when flashing firmware via Odin on the S20 Ultra.....
You can download Odin 3.14.1_3b here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Be sure to download the PATCHED version of 3.14.1_3b (it is located as an attached file at the bottom of the first post in the OP at the link above. Hope this helps.

Geekser said:
Did you ever get things working ? If not, when you flashed with Odin - did you use the PATCHED Version ? THis is necessary when flashing firmware via Odin on the S20 Ultra.....
You can download Odin 3.14.1_3b here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Be sure to download the PATCHED version of 3.14.1_3b (it is located as an attached file at the bottom of the first post in the OP at the link above. Hope this helps.
Click to expand...
Click to collapse
No, to answer your first question, and yes used the patched version of Odin you state but with no joy.
(would another version of Odin be better for my device model?)
I just need to find a way to flash the original stock recovery. Having the TWRP installed as mentioned earlier is blocking my path, and I have now tripped knox! So no more options available to access the unlock oem screen. Now frp is off, oem is on!
Also, I was wondering if anyone had thought about a totally updated version of the old "ALL IN ONE TOOL" which was available for some earlier makes of phone devices? I think due to manufacturers security upgrades of today's phones we could all do with something like this?
I heard you can do a NAND/Reset wipe via the Odin options screen which would allow you to install a new rom???
Oh, my predicament was based on Julius's post, not xReem. Sorry for the confusion.

klantee said:
No, to answer your first question, and yes used the patched version of Odin you state but with no joy.
(would another version of Odin be better for my device model?)
I just need to find a way to flash the original stock recovery. Having the TWRP installed as mentioned earlier is blocking my path, and I have now tripped knox! So no more options available to access the unlock oem screen. Now frp is off, oem is on!
Also, I was wondering if anyone had thought about a totally updated version of the old "ALL IN ONE TOOL" which was available for some earlier makes of phone devices? I think due to manufacturers security upgrades of today's phones we could all do with something like this?
I heard you can do a NAND/Reset wipe via the Odin options screen which would allow you to install a new rom???
Oh, my predicament was based on Julius's post, not xReem. Sorry for the confusion.
Click to expand...
Click to collapse
Sorry for your troubles - wish I could help you but you have done everything I would have tried. Maybe, if you haven't already done this - leave the phone on until the battery runs out completely. Then, recharge the phone for a while so the battery has some juice again and then get the phone back into download mode by pressing volume up and volume down at the same time - then plug in the USB - it shoul.d launch into download mode again - then try flashing again with the patched odin.
If you have already done this - then I don't know how what else to suggest.
I wish you luck and hope you are able to get things working again.

Geekser said:
Sorry for your troubles - wish I could help you but you have done everything I would have tried. Maybe, if you haven't already done this - leave the phone on until the battery runs out completely. Then, recharge the phone for a while so the battery has some juice again and then get the phone back into download mode by pressing volume up and volume down at the same time - then plug in the USB - it shoul.d launch into download mode again - then try flashing again with the patched odin.
If you have already done this - then I don't know how what else to suggest.
I wish you luck and hope you are able to get things working again.
Click to expand...
Click to collapse
Thanks for the advice. I'll try what you suggest and see what happens. Stay well!

Julius_GER said:
Hi guys,
I attached my brand new Galaxy S20 Ultra to my PC and started Smart Switch today. The Software showed an update for my device so I downloaded it and started the update process. Unfortunately, Smart Switch got stuck during the update process at 68%. Nothing happened, cables and all still attached. It just didn't proceed any further for hours.
I decided to take the path of stopping the process, using the key combination shown on my device. It now said, recover your device software with Smart Switch Emergency recovery function. I started this and guess what: it also stopped at 68%.
I "rebooted" the device (volume down + power for approx. 10 seconds) and it starts again in recovery mode.
I manually filled in the recovery code and it seemed like Smart Switch was downloading the OS again. Started the recovery process and it is stuck at 68% again.
Now I am just super afraid that I bricked the device by using Samsungs original software.
Anyone her to help or have similar experiences?
Thanks for any advice on how to proceed.
Julius
Click to expand...
Click to collapse
Hey Julius, did you get your phone to work. I am having the same issue.
Update:
I am good now. I was using the thunderbolt cable that came with the phone and update would get stuck at the same point everything with odin 3.13 and 3.14.
I used a USB 3 to thunderbolt cable that I had from an older phone and it work.
What I used:
Windows 10 x64 1909
USB 3 to thunderbolt cable
USB driver downloaded from Samsung support. I think it is the same driver that comes with smart switch because when I installed it, it prompted
to reinstall driver.
Odin3 v3.13.3_3B_PatcheD from here https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572. ( I think 3.14 will work too.
I really think the cable was the only problem)
Firmware downloaded with SamFirm

klantee said:
Thanks for the advice. I'll try what you suggest and see what happens. Stay well!
Click to expand...
Click to collapse
Open Odin as administrator and if using a stock AP file always use the HOME-CSC of the same firmware in CSC slot. Sometimes Odin plays the fool and gets stuck.

ASHLEY117 said:
Open Odin as administrator and if using a stock AP file always use the HOME-CSC of the same firmware in CSC slot. Sometimes Odin plays the fool and gets stuck.
Click to expand...
Click to collapse
Wow! This nearly worked!!!
Managed to get a (((PASS))) on Odin and my tab actually rebooted into the Samsung logo!!!
Soon after this though tab immediately Boots back into download mode??? Tried the same steps but without any progress???
I feel I'm close to cracking this but need some more advice on how to build on such "progress"!?
Many thanks for your advice...

klantee said:
Wow! This nearly worked!!!
Managed to get a (((PASS))) on Odin and my tab actually rebooted into the Samsung logo!!!
Soon after this though tab immediately Boots back into download mode??? Tried the same steps but without any progress???
I feel I'm close to cracking this but need some more advice on how to build on such "progress"!?
Many thanks for your advice...
Click to expand...
Click to collapse
Try with all slots filled but with CSC file not HOME-CSC. That may help as it flashes pit file to factory reset

ASHLEY117 said:
Try with all slots filled but with CSC file not HOME-CSC. That may help as it flashes pit file to factory reset
Click to expand...
Click to collapse
Tried your suggestion with no joy. Will keep trying though as I feel this issue can be cracked. Many thanks...

Geekser said:
Sorry for your troubles - wish I could help you but you have done everything I would have tried. Maybe, if you haven't already done this - leave the phone on until the battery runs out completely. Then, recharge the phone for a while so the battery has some juice again and then get the phone back into download mode by pressing volume up and volume down at the same time - then plug in the USB - it shoul.d launch into download mode again - then try flashing again with the patched odin.
If you have already done this - then I don't know how what else to suggest.
I wish you luck and hope you are able to get things working again.
Click to expand...
Click to collapse
(((SUCCESS)))!!! :laugh::laugh::laugh:
Done what you suggested by waiting until my battery ran out!
I downloaded a different software version and as soon as I plugged my tab into my PC with USB, i flashed the new software with no problems!!!
Flashed TWRP, Magisk and Multidisabler problemless the same!
The lesson learnt here...
...(ONLY FOR THOSE WHO KNOW WHAT THEY ARE DOING)...
...is to probably only have 30% battery when flashing!!! This way you won't have to wait weeks for such a large capacity battery to run down, like I did!
I knew I'd crack it!

klantee said:
(((SUCCESS)))!!! :laugh::laugh::laugh:
Done what you suggested by waiting until my battery ran out!
I downloaded a different software version and as soon as I plugged my tab into my PC with USB, i flashed the new software with no problems!!!
Flashed TWRP, Magisk and Multidisabler problemless the same!
The lesson learnt here...
...(ONLY FOR THOSE WHO KNOW WHAT THEY ARE DOING)...
...is to probably only have 30% battery when flashing!!! This way you won't have to wait weeks for such a large capacity battery to run down, like I did!
I knew I'd crack it!
Click to expand...
Click to collapse
Glad I could hel;p- I know how frustrating it is when things seem like you can never get things to work - anyway - best of luck - and be sure to hit thanks If I helped you.

Hi Do you lose your data (vids and pics) via this method? i have had same thing happen on my s20+

Question A52s random “Can’t load Android system.” when rebooting

Hi all,
I am encountering this strange bug randomly: sometimes the device Is rebooting itself and it goes automatically in recovery mode, sometimes after a reboot it does the same. The error is always: Can’t load Android system. clicking on “try again” solves the issue (sometimes at the first retry, sometimes after some retries).
I’m attaching the error screens, also because the error message is not every time the same (Attaching also a normal way to enter recovery).
Has someone encounter this bug?
Any hints on how to solve this? I haven’t already do a full reset of the phone, but i think it wilL be the next step I’ll do if the phone is continuing like this.
Thanks!

Hi Arobase40, thanks for your answer.
Yes i know that this things could happen if you do some strange things to the phone (and in my past i was used to that ) but in this case, all is pure and untouched, no unathourized apk and no modding at all. (My use is quite noob-ish now eheh)
And that's seems very strange! :/ I made only ota update and this happened both with android 11 and 12.

Arobase40 said:
This mostly happens when you did some tricky things on your phone. lol
If full reset is not enough (specially when the system is missing....) you'd have to restock it with an official Samsung firmware... ^^
Click to expand...
Click to collapse
Hi Arobase40, thanks for your answer.
Yes i know that this things could happen if you do some strange things to the phone (and in my past i was used to that ) but in this case, all is pure and untouched, no unathourized apk and no modding at all. (My use is quite noob-ish now eheh)
And that's seems very strange! :/ I made only ota update and this happened both with android 11 and 12.

Arobase40 said:
Well ok, in your case try to flash back a stock firmware from Samsung with Frija or Samfw (don't forget to supply the correct model and CSC) using PC Odin.
If that don't fix the problem then get in touch with your local Samsung website and you should find a phone number for the after sale service and they will give you the nearest Samsung official repair center from your home.
They should fix this issue very quickly using most probably the same tool which is PC Odin.
If you go to the repair center don't forget to backup all your apps and data, remove your scard if you have one and also your sim card...
Click to expand...
Click to collapse
Thanks for your help and explanations.
Just to be updated and make some laugh: today the phone while was charging has become completely unresponsive, showing "Samsung Galaxy" on a black screen when touching Power Button or connecting to Power. After a while (hard pressing Power Button and Power+vol up) it restart itself and works again. Never had such an experience with a phone (a COMPLETELY stock phone)

IvanCattaneo95 said:
Thanks for your help and explanations.
Just to be updated and make some laugh: today the phone while was charging has become completely unresponsive, showing "Samsung Galaxy" on a black screen when touching Power Button or connecting to Power. After a while (hard pressing Power Button and Power+vol up) it restart itself and works again. Never had such an experience with a phone (a COMPLETELY stock phone)
Click to expand...
Click to collapse
Idk, seems like a hardware issue to me. Try and have a go at where you've bought it and have them check it over.

My first thought too is hardware.
A few years ago I had something similar with a different phone (Moto G) - as a last ditch effort I popped out the SIM and SD cards and reseated them and it worked perfectly after that. If you have an SD card you might even want to leave it out a few days just to see.
Not saying this is your issue but couldn't hurt to try!