So, here's how it went. :crying:
I just bought my Note 8.0. Came with KitKat - don't remember which firmware. In Kies I tried to update it with latest firmware, when something happened and tablet rebooted with message:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
At first, it sounded simple to me. I tried connecting tablet in Kies, but it was looping in "Connecting", and it never did connect. At all.
I thought, fine, I can try Odin. Once I started flashing KitKat based stock firmware, it fails all the time and it goes like:
...
sboot.img
NAND Write start!
FAIL!
...
"NOT COOL"
Tried out flashing .pit file too but it gets stuck at "Get .PIT for mapping"
And I cannot do anything with my new tablet anymore and I'm stuck. I have tried re-installing drivers, trying out differen USB cables/ports, yet nothing has worked...
And yeah, it shows KNOX Warranty Void : 1, after trying out Odin, so I am screwed too.
And now after battery has depleted, the screen is flickering all the time, and when I try to charge it the charger and the tablet gets hot extremely fast. Does this mean I wasted my money? LOL.
Hi,
I have the exact same problem with my wifey's tablet.
I am working on it at the moment. (which model is yours? hers is SGH-I467)
I believe we should be able to bypass this error by manually flashing certain partitions (leaving out the sboot, which cannot be downgraded, thus causing the error)
I'll be putting together a package for this shortly. (or else my wifey is gonna hulk smash me)
re: battery being dead/screen flicker:
Use a higher wattage charger if you have one. The charger that comes with the gnote8 pulls 8 to 10 watts, random OEM chargers tend to put out less. I was getting the flickering while plugged into usb, but plugged into the charger i'm not.
Da_G said:
Hi,
I have the exact same problem with my wifey's tablet.
I am working on it at the moment. (which model is yours? hers is SGH-I467)
I believe we should be able to bypass this error by manually flashing certain partitions (leaving out the sboot, which cannot be downgraded, thus causing the error)
I'll be putting together a package for this shortly. (or else my wifey is gonna hulk smash me)
Click to expand...
Click to collapse
Mine's GT-N5110. 16GB Wi-Fi model.
Pretty lame that tablet got bricked under 24hrs. *achievement unlocked* :crying:
I have never had such terrible problems with any other Samsung device...
Actually, I tried the Kies again, with Firmware Upgrade and Initialization Tool, looked like it would install just fine, BUT it got a write fail....ffs... Gonna try it again soon. I am trying to charge it up for now.
Da_G said:
re: battery being dead/screen flicker:
Use a higher wattage charger if you have one. The charger that comes with the gnote8 pulls 8 to 10 watts, random OEM chargers tend to put out less. I was getting the flickering while plugged into usb, but plugged into the charger i'm not.
Click to expand...
Click to collapse
The flickering goes away if I leave it to charge it a bit. Just found that out. I just can't charge it for a long time, not going to talk about overnight, because it overheats too much.
I guess it only flickers when battery is going low, and connecting it with USB doesn't help it either.
Kies attempts to flash a full image, which contains an older sboot.img. Once the sboot has been upgraded, it can't be downgraded. This is why you are getting a failure each time.
Unless Kies updates to a newer version of the sboot.img, it won't work to fix this issue. The key should be using odin to flash everything but the sboot.img. I'm working on it now. I don't have the same model as you however, but the method to create an image should be exactly the same for that model, just have to start with a different set of files.
Da_G said:
Kies attempts to flash a full image, which contains an older sboot.img. Once the sboot has been upgraded, it can't be downgraded. This is why you are getting a failure each time.
Unless Kies updates to a newer version of the sboot.img, it won't work to fix this issue. The key should be using odin to flash everything but the sboot.img. I'm working on it now. I don't have the same model as you however, but the method to create an image should be exactly the same for that model, just have to start with a different set of files.
Click to expand...
Click to collapse
OK, so I tried to do this again. This time I let tablet charge so while firmware gets recovered, screen doesn't flicker and do weird stuff, aaand....
Recovered the firmware succesfully, BUT it got bricked and has a boot loop. That's just naaaasty.
Katflakes said:
OK, so I tried to do this again. This time I let tablet charge so while firmware gets recovered, screen doesn't flicker and do weird stuff, aaand....
Recovered the firmware succesfully, BUT it got bricked and has a boot loop. That's just naaaasty.
Click to expand...
Click to collapse
Done, I have found out that I repedeately tried to install the wrong firmware. Ex., I have tablet with stock XEO firmware, and I tried to install SEB firmware. Thats why it didnt let me install the firmware I wanted to, because I was stupid. well best 10gb ever spent!
Help Please!
Need help !!
my note 8.0 gt-n5110 get the same error when flashing the stock 4.4.2 kitkat
sboot.img
NAND Write start!
FAIL!
i can enter the recovery and download mode but when flashing i get the error
Pleeease HELP!!!!
Lemme see here... You stated it was already 4.4.2 and broke when upgrading f/w. I assume you are using keis for 4.2.2... You will need to uninstall it, and install the latest kies for 4.4.2. Then see if you can fix your broken flash.
Hey y'all... looks like I'm in the same miserable boat. I'm trying to sell my Sammy Note 8 to Amazon but had to remove the root and Cyanogen 4.4.4 ROM before sending it in. After reading a bunch of articles, I came to this page: http://forum.xda-developers.com/showthread.php?t=2773712 After waiting about 20 minutes and not seeing any progress, I thought it was stuck. So, I rebooted into recovery and tried again. Like the OP, Odin peters out at the recovery.img stage and Fails. Now, I'm getting the super fast screen flashing which I've learned is a low battery issue. It's on charge now and hope in an hour or two can try again. My question to you guys, am I using the right img for a US N5110? Or do you guys know a better way to flash this baby back to original the original unrooted, 4.2.2 state?
Any help is VERY MUCH appreciated!
Da_G said:
Kies attempts to flash a full image, which contains an older sboot.img. Once the sboot has been upgraded, it can't be downgraded. This is why you are getting a failure each time.
Unless Kies updates to a newer version of the sboot.img, it won't work to fix this issue. The key should be using odin to flash everything but the sboot.img. I'm working on it now. I don't have the same model as you however, but the method to create an image should be exactly the same for that model, just have to start with a different set of files.
Click to expand...
Click to collapse
HI! I have the same model as your wife and same problem! Can you please teach me how to do it!
You can't go from kk (4.4) to jb(4.2). Kitkat has a locked bootloader.
You might try stock kk flash.
Sent from my GT-N5100 using XDA Free mobile app
If you have the ATT SGH i467 the Kit Kat ROM is not available to the public.
I sat with mine in the exact same state as yours & the OP until I found out you can take your Note 8 to a Samsung Experience center (they are in a LOT of Best Buy stores!! 4 in Columbus Ohio) and they will flash Kit Kat on it for you for free!! I was stoked to get my tablet back to working order. The original issue that got me into this problem (my IMEI disappeared and no I have NEVER rooted this tab) is what I am currently trying to have them fix without as much luck as they had fixing the stuck in downloading mode. The quality of the employees varies GREATLY from store to store. The 1st tech fixed me up great and hung in there even though the low charge battery issue was looking like it would make the reflash fail but the next tech at a different store literally just sat and looked down not saying a word waiting for me to give up and leave because "their laptop didn't have enough free disk space to download the ROM". If ANYONE from Samsung would have watched the situation and his actions he would have been fired on the spot. So be patient if the 1st tech you talk to is clueless because they CAN fix your issue.
Related
Hello to everyone. This is my first adventure. I've read until my eyes have bleed but still haven't figured out a solution to my problem so I will ask scaringly...
I have a AT&T Samsung Note II SGH-I317 rooted.
My phone is currently stuck on "Samsung GALAXY Note II" screen after I did a factory reset.
Initially this worked but as I was setting everything back up, I received a ota system update. And it gave me a failure to upgrade error, try again in kies. Kies will not recognize my phone because it's stuck. I've done the hold up volume + home then power a hundred times but it won't let me go into recovery. I've read of everyones success but I'm still stuck! I used stock roms from at least 5 different sources but none have fully recovered my phone. It does however PASS in odin 3.07 and 3.09.
What other options have I missed? Please help....
poochieturner said:
Hello to everyone. This is my first adventure. I've read until my eyes have bleed but still haven't figured out a solution to my problem so I will ask scaringly...
I have a AT&T Samsung Note II SGH-I317 rooted.
My phone is currently stuck on "Samsung GALAXY Note II" screen after I did a factory reset.
Initially this worked but as I was setting everything back up, I received a ota system update. And it gave me a failure to upgrade error, try again in kies. Kies will not recognize my phone because it's stuck. I've done the hold up volume + home then power a hundred times but it won't let me go into recovery. I've read of everyones success but I'm still stuck! I used stock roms from at least 5 different sources but none have fully recovered my phone. It does however PASS in odin 3.07 and 3.09.
What other options have I missed? Please help....
Click to expand...
Click to collapse
Weird, ODIN should usually work without issue. Are you using the custom recovery or a stock recovery? You should be able to flash a new recovery with ODIN I believe.
Are you using the factory USB charging cable? Knock-off cables cause odin and kies errors.
Reply
They were all stock recovery. As I mentioned before, the first time I done it, it worked fine but once I received the update from at&t I've not been able to duplicate that process without get stuck. I can access download and that's it.
Yes, I'm using the usb that came with my phone. ODIN recognizes my phone immediately.
poochieturner said:
They were all stock recovery. As I mentioned before, the first time I done it, it worked fine but once I received the update from at&t I've not been able to duplicate that process without get stuck. I can access download and that's it.
Yes, I'm using the usb that came with my phone. ODIN recognizes my phone immediately.
Click to expand...
Click to collapse
I'm having this same exact problem under very similar circumstances. Has anyone found a solution?
Thanks Man
hylander2126 said:
I'm having this same exact problem under very similar circumstances. Has anyone found a solution?
Click to expand...
Click to collapse
Followed your post and got mine working also.. Bootloader did it! Thanks...
Earlier this evening, after texting a friend, my phone rebooted itself.
It appears to be in a boot loop. It will only reboot into rebooting. Never loads Android. I pulled the battery, let it sit for a few minutes, and tried again with no results.
I've not done modding to the phone (mainly because its locked), and will be returning it to my local AT&T store tomorrow. Thankfully I have insurance on my phone, so I shouldn't have an issue getting a new one.
Anybody else had this issue, however? It's really strange.
Majin Kaioh said:
Earlier this evening, after texting a friend, my phone rebooted itself.
It appears to be in a boot loop. It will only reboot into rebooting. Never loads Android. I pulled the battery, let it sit for a few minutes, and tried again with no results.
I've done modding to the phone (mainly because its locked), and will be returning it to my local AT&T store tomorrow. Thankfully I have insurance on my phone, so I shouldn't have an issue getting a new one.
Anybody else had this issue, however? It's really strange.
Click to expand...
Click to collapse
Read a guide on flashing back to stock. Use ODiN and flash the stock file of your choice in the ATT note 4 forum from Download mode. Google how to boot into download mode. Hold those buttons until phone powers off then keep holding until you see download mode. You will need to install samsung drivers and for ODiN on Windows go to Devices coms and ports and change port to 3 in advanced tab.
sudoBacon said:
Read a guide on flashing back to stock. Use ODiN and flash the stock file of your choice in the ATT note 4 forum from Download mode. Google how to boot into download mode. Hold those buttons until phone powers off then keep holding until you see download mode. You will need to install samsung drivers and for ODiN on Windows go to Devices coms and ports and change port to 3 in advanced tab.
Click to expand...
Click to collapse
I updated my post to add in a missing word. I havn't done any modding. I do not intend to do any flashing to the device.
I'll be returning it to AT&T tomorrow and getting a new one. My question was if anyone has had this issue before. Thanks for your response. Unfortunately, does not address my question.
sudoBacon said:
Read a guide on flashing back to stock. Use ODiN and flash the stock file of your choice in the ATT note 4 forum from Download mode. Google how to boot into download mode. Hold those buttons until phone powers off then keep holding until you see download mode. You will need to install samsung drivers and for ODiN on Windows go to Devices coms and ports and change port to 3 in advanced tab.
Click to expand...
Click to collapse
I have had my share of boot looping experiences, never from not doing any type of experiments with my devices. nonetheless myself and I'm sure many other people just do what was mentioned in the quote to alleviate that problem.
i know you (OP) mentioned you don't plan on doing any flashing, but i would do that before using insurance personally, even if there was no deductible
Majin Kaioh said:
I updated my post to add in a missing word. I havn't done any modding. I do not intend to do any flashing to the device.
I'll be returning it to AT&T tomorrow and getting a new one. My question was if anyone has had this issue before. Thanks for your response. Unfortunately, does not address my question.
Click to expand...
Click to collapse
This process is not dangerous if your phone is in a bootloop. Hell AT&T or whatever carrier probably does this themselves if a phone is in this kind of situation. If not rooted or any mods you will still have OTA updates. If you are worried about carrier recognizing if you modded it or something and they wont take it back dont worry just flash it using ODiN. I've rooted many devices hacked compiled roms flashed them and kernels s-offed etc. You can always get back to stock remove flags and your carrier will take it back no matter what just dont return a device with the actual mods on it.
Why not just try to reset the device from the recovery menu? If it's a stock phone it should fix the bootloop.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
jack man said:
Why not just try to reset the device from the recovery menu? If it's a stock phone it should fix the bootloop.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
Click to expand...
Click to collapse
It won't fix what sounds like a missing or corrupted boot file, had to deal with it on a LG g3.. restoring a full back up or a plain reset had no effect.. it was either doing a full flash or flashing the boot files
for that phone it would randomly happen when the OTA tried to upgrade the device while it was rooted, took me 3 times of dealing with it before I realized OTA was still live
Small update. My local AT&T store has a replacement being sent to me. I'm unhappy, however, since its apparently a refurbished device. I pay for insurance that covers a new device if something, anything, happens. They're refusing to send me a new one for some reason that they won't explicitly state to me.
My loyalty with AT&T has wavered, and I will probably be on another network in coming months. I'm thinking Sprint so that I can least have an unlocked Note 4.
Regardless, since this device is being sent back, I decided to try and Odin flash it anyways. It did not work. Still boot loops at the Note 4/Android screen. Doesn't even load the AT&T logo. I'm fairly certain something is fundamentally broken with the device. Probably a factory error. It's never been dropped, and has been inside a hard case since day one.
Being that it is a manufacturing error, I'm not to angry about that. These things do happen. AT&T's treatment of me, however, is just unacceptable. I've been a customer for about eight years, and have been on Android since the Motorola Backflip. I upgraded to a Samsung Captivate and never looked at another manufacturor.
Are you able boot to the recovery menu?
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
i have the bootloop issue before to put *#9090#
the loop is every aprox 3 mins
some sugestion?¡
sudoBacon said:
This process is not dangerous if your phone is in a bootloop. Hell AT&T or whatever carrier probably does this themselves if a phone is in this kind of situation. If not rooted or any mods you will still have OTA updates. If you are worried about carrier recognizing if you modded it or something and they wont take it back dont worry just flash it using ODiN. I've rooted many devices hacked compiled roms flashed them and kernels s-offed etc. You can always get back to stock remove flags and your carrier will take it back no matter what just dont return a device with the actual mods on it.
Click to expand...
Click to collapse
Good evening,
my n910A is stocked in Bootlop ,
I did try also to flash via odin the 4 zipped md5 files from this forum but nothing changed : http://forum.xda-developers.com/note-4-att/general/to-stock-files-latestcoc4-build-t3107391
when I press volume up+power+home it show LRX22C.N910AUCU1COC4 but the version on the label of my box is N910AUCU1ANIE ,
I don't know if I should go back to the previous version and how to do it ?????
or something else??????
please help because I am lost
thanks
thepinkpanter said:
Good evening,
my n910A is stocked in Bootlop ,
I did try also to flash via odin the 4 zipped md5 files from this forum but nothing changed : http://forum.xda-developers.com/note-4-att/general/to-stock-files-latestcoc4-build-t3107391
when I press volume up+power+home it show LRX22C.N910AUCU1COC4 but the version on the label of my box is N910AUCU1ANIE ,
I don't know if I should go back to the previous version and how to do it ?????
or something else??????
please help because I am lost
thanks
Click to expand...
Click to collapse
Try downloading one of sunderwares stock firmwares in a newer 3.10 odin after extracting the zip with contained files. I recommend latest OC4 just re flash it a different one or try again
sudoBacon said:
Try downloading one of sunderwares stock firmwares in a newer 3.10 odin after extracting the zip with contained files. I recommend latest OC4 just re flash it a different one or try again
Click to expand...
Click to collapse
I already did it but by using Odin 3.09 pls. see http://forum.xda-developers.com/note-4-att/general/to-stock-files-latestcoc4-build-t3107391/page5
maybe I did something wrong
or from where can I get / download a different N910AUCU1COC4 ?
thanks again for your kind help
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.
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+
Hello, I've tried my best but really am struggling.
When I first got the phone the only sign of life was when charging it there was a charging circle. I managed to play around and now while plugged in I am able to get into download mode while holding Volume Up + volume Down. However, the phone is continuously looping while plugged in (unless in download mode) & does absolutely nothing when not plugged in. When I get into recovery mode it instantly reboots, and whenever I try flash stock firmware I get PIT or bootloader error (<ID:0/004> Complete(Write) operation failed.). My suspicion is the fact I do not have the correct stock firmware but for whatever reason I cannot find the firmware for this model (SM-A505FZWDINS, Indian version).
Does anyone know what I should do? I'd like to give life to this phone but I'm really out of ideas.
Thanks in advance,
icecub
Bad battery.
blackhawk said:
Bad battery.
Click to expand...
Click to collapse
How definitive is this?
Is the battery know to be good?
If you don't know assume it's bad... everything you're stating indicates insufficient battery capacity.
Try twrp rooting formate then re flash stock firmware make sure Odin is the correct version this also happens when I don't have correct or upto date version hope this helps
same **** here. for me i cant charge the battery too. but before that with about the same problems i got it to work again for a few days.
funny that i saw more ppl at the last time here with the same problem. but i flash a stock firmware. R11 but it dosent solve it for a few days.
now it hangs allways on boot or warning logo for unlocked bootloader. i have used this phone over a year without this issue.