Related
Hello, this is a sad history but i got my first s4 mini the last year, it worked arround 2 years but one day i was just using it an on my hands my phone freezes a few seconds and just power off. Then, never power on again!
No recovery, no download, no samsung logo, no vibration, nothing. it just is showed as qshusb_dload on windows 7.
As i read it died completely. but i read that some people are getting sucess with a file named debrick.img, that is obtained doing a backup of the first 128mb of the rom.
well ive tried maybe 3 different debrick.img that i found on web but i get the same, nothing.
the problem is that my phone was working with pacman rom before die, and the debrick.img`s that i ve found on the web are from stock roms on some different versions.
someone can do a debrick.img from a pacman rom and upload it to me? i will aprecciate too much
you can get the debrick img flashing this
forum.xda-developers.com/attachment.php?attachmentid=2500001&d=1389091779 <-direct link.
its completely safe i do a backup with this tool on my s4 mini before but as an idiot i just deleted from my pc and now i need that...
this is the link to the post of the tool if you want to read more, is from another model but im telling you its safe, works on s4 mini with no problems, i used before!
http://forum.xda-developers.com/showthread.php?t=2600976
:crying:
migueldvp said:
No recovery, no download, no samsung logo, no vibration, nothing. it just is showed as qshusb_dload on windows 7.
Click to expand...
Click to collapse
My phone was dead like yours, too, black and no life sign when pressing buttons. However i had success to "revive" it by removing battery and cables and putting them back (I don't remember if battery first and cable second or vice versa) while holding power button pressed (and maybe VOL.UP / VOL.DOWN / HOME or both/three) all the time. It needed some tries and I do not know the exact combination which worked, but it worked in multiple situations in the past too, when my phone was dead black and did not want to start. If your battery charger screen shows up finally you got it. Let it recharge at least a bit (better: full recharge) before you try to start the android system finally.
sumeruter said:
My phone was dead like yours, too, black and no life sign when pressing buttons. However i had success to "revive" it by removing battery and cables and putting them back (I don't remember if battery first and cable second or vice versa) while holding power button pressed (and maybe VOL.UP / VOL.DOWN / HOME or both/three) all the time. It needed some tries and I do not know the exact combination which worked, but it worked in multiple situations in the past too, when my phone was dead black and did not want to start. If your battery charger screen shows up finally you got it. Let it recharge at least a bit (better: full recharge) before you try to start the android system finally.
Click to expand...
Click to collapse
Thanks but this is not working for me, i tried everything! pressing all buttons on differents ways, with battery pulls usb cable, etc, etc nothing works.
That's sad.
As far as I've understood the cpu tries to boot from second partition if booting from first partitions fails. The debrick.img contains the first X partitions from booting process and even if those are the very first booting partitions of another rom for the same phone and are conflicting to your installed android system (and thus won't boot into full system), your phone should give at least a life sign.
Have you tried different sdcard sizes?
I think there is still hope. I don't know how it works, but you might try a JIG. And since your phone shows up as qshusb_dload you might try to connect to your phone while it is offline (my phone has even adb shell while in charge screen - which doesn't show up for your phone). I remember there was a special qshusb_dload driver for Samsung phones, different to the "usual" Samsung USB drivers (maybe look here)...
sumeruter said:
That's sad.
As far as I've understood the cpu tries to boot from second partition if booting from first partitions fails. The debrick.img contains the first X partitions from booting process and even if those are the very first booting partitions of another rom for the same phone and are conflicting to your installed android system (and thus won't boot into full system), your phone should give at least a life sign.
Have you tried different sdcard sizes?
I think there is still hope. I don't know how it works, but you might try a JIG. And since your phone shows up as qshusb_dload you might try to connect to your phone while it is offline (my phone has even adb shell while in charge screen - which doesn't show up for your phone). I remember there was a special qshusb_dload driver for Samsung phones, different to the "usual" Samsung USB drivers (maybe look here)...
Click to expand...
Click to collapse
Hmm i understand, i was thinking that the debrick.img should be from the same rom exactly... and i have two phones with the same problem, both fails by the same way, i was using it and just frezees and never woke up again. I buyed the second when the first died, but after a months the second died too.. Both have installed unofficial roms and dindt show any signal of life dont matter what i do, the JIG doenst works too i tied too.
Definitivelly S4 mini is not great choise for a phone that will be used with hard work.
migueldvp said:
Definitivelly S4 mini is not great choise for a phone that will be used with hard work.
Click to expand...
Click to collapse
As many cases of died S4 minis I've heard of the last two weeks here at XDA or from friends I got the impression Samsung built those phones with an expiration date.
sumeruter said:
As many cases of died S4 minis I've heard of the last two weeks here at XDA or from friends I got the impression Samsung built those phones with an expiration date.
Click to expand...
Click to collapse
i'm agree with this. And looks like the expiration time for the s4mini is one year and a half or two years till the EMMC die. The sandisk EMMC included on the s4 mini is not of a great quality.
well ****. exact same problem here, does this emmc has anything to do with hardware? and have you folks fixed it yet? how do you even get a phone with good emmc things?? sorry if iam late but it really sucks how that 1 year 9 months later it just dies. any help? thanks!
migueldvp said:
i'm agree with this. And looks like the expiration time for the s4mini is one year and a half or two years till the EMMC die. The sandisk EMMC included on the s4 mini is not of a great quality.
Click to expand...
Click to collapse
Interesting theory. My S4 mini died overnight for no particular reason and I am in the same situation now. Cannot get to download mode, JIG doesnt work either. Tried searching for debrick images, but all the older links are invalid. Would appreciate if anyone can provide one.
Thanks.
abhishek55 said:
Interesting theory. My S4 mini died overnight for no particular reason and I am in the same situation now. Cannot get to download mode, JIG doesnt work either. Tried searching for debrick images, but all the older links are invalid. Would appreciate if anyone can provide one.
Thanks.
Click to expand...
Click to collapse
Nah, Samsung wouldn't do that, however there definitely seems to be a problem with the S4 Mini if you look at the number of bricked S4 Mini's here on XDA and compare to say the S4 which sold more (I believe) and yet it has nothing like the number of failures. One poster on another thread said most of these were from a bad batch manufactured in Vietnam, but I have not been able to find definite proof of this.
As for a debrick image it should not matter what ROM the debrick image is made from as it only consists of a small block of data that is not changed by custom ROM's (according to what I read on another Samsung phone thread last year, where a debrick image was made from a phone running a Cyanogenmod rom that worked successfully on another phone. But again I have not found another ref to confirm this)
I would make you a debrick file but I have a I9195 LTE
IronRoo said:
Nah, Samsung wouldn't do that, however there definitely seems to be a problem with the S4 Mini if you look at the number of bricked S4 Mini's here on XDA and compare to say the S4 which sold more (I believe) and yet it has nothing like the number of failures. One poster on another thread said most of these were from a bad batch manufactured in Vietnam, but I have not been able to find definite proof of this.
As for a debrick image it should not matter what ROM the debrick image is made from as it only consists of a small block of data that is not changed by custom ROM's (according to what I read on another Samsung phone thread last year, where a debrick image was made from a phone running a Cyanogenmod rom that worked successfully on another phone. But again I have not found another ref to confirm this)
I would make you a debrick file but I have a I9195 LTE
Click to expand...
Click to collapse
Hi
Can you please make me the debrick file?
I have the I9195 and I have the exact problem. The thing is that I can't even go to Download Mode... What can I do?
PedroBarbosa said:
Hi
Can you please make me the debrick file?
I have the I9195 and I have the exact problem. The thing is that I can't even go to Download Mode... What can I do?
Click to expand...
Click to collapse
Did you try the I9195 debrick files from the @ValenteL thread here
https://forum.xda-developers.com/showthread.php?t=2625628&page=7
see my mega link or the other one
(note: they are NOT for I9192 phones)
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.
Hello,
My S4 Mini I9192 Suddenly died while charging overnight and now no response whatsoever. Only thing I know is that I am in 9008 mode.
QFIL Can see the phone, but i need a firehose programmer and some XML files. Can anyone tell me where I can find those files? Thanks in advance.
kasa ssg said:
Hello,
My S4 Mini I9192 Suddenly died while charging overnight and now no response whatsoever. Only thing I know is that I am in 9008 mode.
QFIL Can see the phone, but i need a firehose programmer and some XML files. Can anyone tell me where I can find those files? Thanks in advance.
Click to expand...
Click to collapse
I read a little about using qfil some time ago, and even if you can find the files I don't think it will work on Samsung phones, though I stopped researching when I read the following link (luckily my phone was not bricked, so I didn't need to), he says QFIL won't work as Samsung do not use the default options (well that was my understanding)
http://www.androidbrick.com/unbrick...-have-the-right-kind-of-rom-qhsusb_dload_edl/
I think the only option is take it to a repair shop for jtag or new emmc/motherboard, but I could be wrong. (or buy an old phone with cracked screen and use the motherboard from that)
While I was searching the web for files the phone was connected to the pc. It didn't show any signs of life until a battery icon suddenly popped on the screen. I was even able to boot into download mode, but when I went to recovery it said "No Command". Odin recognized the device, I flashed stock, but when i tried to boot it up, It was in a bootloop. I tried flashing many times with no success, still bootloops. Even after the flashing the recovery was in "No Command" mode. Yesterday i tried to flash it for the last time with the same rom, and this time it just booted to the Samsung logo and then turned off. Now I'm back to the 9008 mode. I tried the sdcard method with a debrick.img, no success. Any idea what might be wrong with the phone?
Okay so now I'm again in download mode, but everytime i boot up the samsung logo distorts and stock recovery shows up but it says E: Can't mount /cache or smth. I've read that i need the correct pit file, apparently the one I have is for the 8gb version. Can anybody send me the .pit file for the 16gb version?
kasa ssg said:
Okay so now I'm again in download mode, but everytime i boot up the samsung logo distorts and stock recovery shows up but it says E: Can't mount /cache or smth. I've read that i need the correct pit file, apparently the one I have is for the 8gb version. Can anybody send me the .pit file for the 16gb version?
Click to expand...
Click to collapse
I can't help as I have different model but yakapa40 can as usual, if nobody else has pit for you
https://www.sammobile.com/forum/showthread.php?t=30208
Exact Same Case
kasa ssg said:
While I was searching the web for files the phone was connected to the pc. It didn't show any signs of life until a battery icon suddenly popped on the screen. I was even able to boot into download mode, but when I went to recovery it said "No Command". Odin recognized the device, I flashed stock, but when i tried to boot it up, It was in a bootloop. I tried flashing many times with no success, still bootloops. Even after the flashing the recovery was in "No Command" mode. Yesterday i tried to flash it for the last time with the same rom, and this time it just booted to the Samsung logo and then turned off. Now I'm back to the 9008 mode. I tried the sdcard method with a debrick.img, no success. Any idea what might be wrong with the phone?
Click to expand...
Click to collapse
kasa ssg said:
Okay so now I'm again in download mode, but everytime i boot up the samsung logo distorts and stock recovery shows up but it says E: Can't mount /cache or smth. I've read that i need the correct pit file, apparently the one I have is for the 8gb version. Can anybody send me the .pit file for the 16gb version?
Click to expand...
Click to collapse
Hey, Hi.
So same thing happened with me, I was on Stock Kitkat S4 mini i9192, phone froze while using and never booted up. But then I left it connected to laptop and it vibrated and showed the battery icon and I got every problem same as you, like no command, boot loop, and again phone went into QHS_DLoad mode.
I want to know that how did you manage to get back into the Odin Download mode again because since the last time my phone didn't show any sign of life and I also want to know if you were able to fix it? I have not tried debrick.img yet. Please help to fix my phone :laugh:
geek_hsk said:
Hey, Hi.
So same thing happened with me, I was on Stock Kitkat S4 mini i9192, phone froze while using and never booted up. But then I left it connected to laptop and it vibrated and showed the battery icon and I got every problem same as you, like no command, boot loop, and again phone went into QHS_DLoad mode.
I want to know that how did you manage to get back into the Odin Download mode again because since the last time my phone didn't show any sign of life and I also want to know if you were able to fix it? I have not tried debrick.img yet. Please help to fix my phone :laugh:
Click to expand...
Click to collapse
Well, sorry to disappoint you, but I found out that the flash memory of the phone was dead. After all I've done the phone just turned off, and never turned on again. I also found out that this phone is known for dying memory chips.
Howdy. Does anybody know what happened here and how to fix it???
Claudio4780 said:
Howdy. Does anybody know what happened here and how to fix it???
Click to expand...
Click to collapse
Just press power button when rebootnow is highlighted by using volume buttons.....
HemanthJabalpuri said:
Just press power button when rebootnow is highlighted by using volume buttons.....
Click to expand...
Click to collapse
Thanks, tried it. But it just starts in Recovery Modus or Bootloader Modus
Claudio4780 said:
Thanks, tried it. But it just starts in Recovery Modus or Bootloader Modus
Click to expand...
Click to collapse
Flash TWRP and flash custom rom like you did before.....
And If you want stock rom then flash my stockrom lite in twrp
Thanks a lot for replying
kasa ssg said:
Well, sorry to disappoint you, but I found out that the flash memory of the phone was dead. After all I've done the phone just turned off, and never turned on again. I also found out that this phone is known for dying memory chips.
Click to expand...
Click to collapse
Thank you, I was thinking that once the battery is empty and when you connect it via USB mode, it reboots itself, so maybe that is why you got the second chance with it but when I got the phone turned on, I charged it up to 90 percent and now my battery is not draining. Previously my phone died when it was having around 35% of charge which was drained in 20 days. So I have avery strong reason to believe that its just a corrupt bootloader and I have to flash using pit.
geek_hsk said:
Thank you, I was thinking that once the battery is empty and when you connect it via USB mode, it reboots itself, so maybe that is why you got the second chance with it but when I got the phone turned on, I charged it up to 90 percent and now my battery is not draining. Previously my phone died when it was having around 35% of charge which was drained in 20 days. So I have avery strong reason to believe that its just a corrupt bootloader and I have to flash using pit.
Click to expand...
Click to collapse
I did try flashing with .pit, but to no avail. Actuall, it recalled to me right know, god knows how I managed to flash stock firmware., BUT, everytime the phone started booting, the samsung loading logo would become slowly more and more distorted, until all my screen became pink with white stripes. It was strange.
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+
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!