Hi, folks - my first post on XDA, and boy do I need help.
Short version, it seems like my Tab4 7'' might be bricked - I've got a "Firmware update encountered an issue" yellow triangle when I tried rooting it and Odin decided to crash three seconds in and can't get past it. The tablet isn't recognized in device manager anymore, with a "A request for the USB device descriptor failed." and KIES keeps trying to connect to it, but without effect.
Digging around online gave me contradictory, vague and often out-of-date results - most of them recommend using Odin to reflash it with a stock image {which I may or may not have}, but when I try to, it waits at SetupConnection.
Any ideas? I have a replacement plan for it, but I'd rather not cash it in unless I have to.
Related
Hi all!
I have a rather major problem.
Today Kies told me that I have a new upgrade for the firmware of my Samsung Galay S i9000. It ran stuck rom with only a few apps installed. I said i want to upgrade so it started to check everything, done a backup of my contacts, started to download the firmware on my PC. So far everything is good.
After that the phone rebooted into an android working logo and said "Downloading..." it stayed like this for a while and after that Kies gave an error. Now the phone is stuck on this screen. Disconecting the device from the usb cable and pluging it back in does't do anything. Kies tries to connect to it but after a couple of minues gives an error that the device is not responding and I should try to rebot the device.
Any idea what to do? This is the work phone so I have to fix this.
Any help is appreciated.
EDIT: Fixed the problem with odin. I know I should get a warning for not searching first...but I panicked.
Easy stuff to fix, start by posting in the right section.
Sent from my GT-I9000 using XDA Premium App
I was trying earlier to install a custom recovery and after finally getting AutoRec to install TWRP decided to reboot into Android so I could fully backup my apps, data etc as I don't have enough storage space on the device to do it locally. Unfortunately I got stuck in a boot loop that showed me the LG logo then after a few seconds it displayed "security issue" underneath.
I ran through a few things I've found elsewhere and it was in the process of doing something via "firmware update" and got to 4% when the program crashed. I had no option other than to power off the phone but now I'm stuck in "Firmware Update" mode. I've not got a clue how to fix this and after searching I did find a guide but it involves telling my phone to use a different COM port in Device Manager but I don't have that option.
Right now I have my phone stuck like this and if nobody can help it's gone from being slow but usable to a brick. The fact that I can get the Firmware Update mode gives me slight hope. If anyone can help I'd really appreciate it. This is the first time I've not been able to fix an issue with an Android phone myself but this G2 has been a nightmare and the sluggish performance made me finally look for a custom ROM but rooting, installing custom ROMs .... it just doesn't want to do it and now this.
I managed to fix this after my brain woke up and found the required options in Device Manager. If anyone ever looks back for this issue I used the guide below.
http://forum.xda-developers.com/showthread.php?t=2432476
There are two guides there with a 2015 option using a different program and method. I used the 2015 method after the first one crashed during the flash process.
Hi. I have a SM-G900T and tried to root it today using Chainfire. I got a message that it passed, but it entered into a loop where is starts to reboot, displays a message "Set Warranty Bit : kernel" at the top, and restarts after a few seconds. Looking around I saw a lot of advice to essentially try again if you get the "Set Warranty Bit : kernel" error, however when I get into the download mode now windows (and Odin) no longer see the device. I tried getting the latest drivers from Samsung to see if it helped, but it did not.
When it's stuck in the reboot loop I can hear the windows sound for USB connecting, but it restarts before I can verify anything in device manager.
Can anyone help me out? Thanks!
Ok. I'm a fool. As soon as I hit the up volume from the warning the USB connected.
I tried to install the Chainfire root again, but I got the same error. I'm now downloading the stock firmware from Sammobile to try and get my phone functional again.
So I gifted my mother a Galaxy Tab (SM-T355Y) a few years back and it was behaving fine until a few weeks back. Now it gets in an infinite bootloop when we try turning it on (I see the black screen with Galaxy Tab written in white, and it boots again and again) and it simply won't budge. I cannot access recovery in this state as pressing the required buttons still keep me in the loop.
Now flashing the stock firmware on Odin would be the logical go-to in such case, but I cannot get Odin to recognize the device when plugged in on Download mode. I keep getting a message saying 'Windows doesn't recognize the device', but it recognizes my S10 perfectly and I did install all necessary drivers when I had plugged in my S10 for the first time.
I think the drivers for both S10 and the Tab should be the same. Am I missing something here? I hate it when I'm not able to fix an android device myself, but I seem to have hit a roadblock in this case.
PS: I don't come from a tech background and I've learnt all things android on XDA, so excuse any gaps in my understanding.
Cheers!
So while looking around the house I found my old phone, the Samsung Galaxy J5 and I tried to turn it back on. It looped on the logo screen and that's when I remember that I bricked it when I was playing around with rooting device all those years back. As someone who never tried to play around with my phone data ever since then, I decided to just check a lot of thread relating to the topic and conclude that all I need to do is to flash the device with a newer version of the android OS(?)
I get to work and download Odin and manage to find some of the data needed. All is fine until when the bar was about 90%, it says
"Custom Binary(system) Blocked by FRP lock"
After a lot of reading, I found out that it's a safety system so people can't just steal and reset the phone to be sold again. Understanding that, I kinda gave up on the whole "fixing" this phone thing and just decide to reset the whole thing since the stuff inside the phone shouldn't even be that valuable; perhaps a lot of photos and memories but nothing other than that.
Now my smart ass decide to just unplug it from the PC and just turning the phone off by taking the battery off. Turning it back on now shows a new page
"An error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software"
I tried to flash the OS from Odin again, it stopped at the same exact 90% line with the same "Blocked by FRP lock" on the top left corner. I tried downloading smart switch, there's nothing on the emergency recovery function page other than "403 Forbidden". I tried to download an older version of it and tried to just use the device initialization and it says that it isn't supported for some reason.
At this point I'm lost and stuck with a bricked phone asking me to use the emergency recovery function. I cannot even go to download mode or the "Home+power+volume up" mode anymore.
At first I want to save the data but now as long as I can reset it I'm just happy. Can anyone give me a guide on how to fix this? I feel like I manage to pile problems on top of problems and now this phone is basically hard bricked.
My phone is Samsung Galaxy J5 (SM-J500G/DS). All help is appreciated!