Galaxy Tab S 8.4, SM-T700. Received the lollipop update and that worked fine. Immediately tried to run CF-Auto-Root on it using Odin 3.07 and CF-Auto-Root-klimtwifi-klimtwifixx-smt700.tar.md5. I booted into download mode, started Odin and clicked Start. Only the first progress block in Odin lit up and the Tab S only showed about an inch of blue progress line. That was it for about 4 hours.
The tab was not responsive, shutting down Odin did nothing and trying a different Odin version also did nothing. So I had no choice but to disconnect the Tab S. Immediately rebooted to the "Firmware upgrade encountered an issue...." message. Running Kies does not recognize the tablet, running different versions of Odin with the stock firmware does nothing and the Tab won't do anything but restart into the "Firmware encountered an issue" screen. Won't go into download mode at all and nothing I do in Kies or Odin seems to work.
Last several times I've used CF-Auto-Root went flawlessly. This time, not. So if it continually reboots in to the "Firmware encountered an issue" screen, is there any recourse?
I have let it run out of juice and left it plugged in long enough to recharge fully but no matter what I do, it won't do anything but get to that one annoying screen!
Maybe there's a sequence of steps I'm missing. Anyway, been trying everything I can find out there on this but it's not working.
Thoughts?
You likely have a bad cable there. That's what happens.
You should be able to get download mode if it boots to the firmware failed screen
If you can boot to recovery then just wipe cache and it should boot.
From the firmware failed screen hold POWER + VOL DOWN + HOME until it restarts then immediately change to VOL UP whilst still holding the other buttons.
If that doesn't work try again with POWER + VOL DOWN + HOME until download mode boots.
If you still can't get either you can try the usb jig, which apparantly does work on this device.
Ask skOrPn which one to use, he use to build these things.
Hmmmm, you're right. I was using the Samsung cable that came with the tablet so figured there wasn't anything wrong with it (since one of the popular solutions is to not use a generic and make sure to use the Samsung).
So I dug deep in the vault for a slightly older Samsung cable from a previous phone and tried it. Sure enough - it worked. Odin completed the CF-Auto-Root in the 10 seconds it usually takes.
Clearly even Samsung cables go bad.
Thanks for pointing out the obvious but not so obvious!
Bob
Related
Hi all,
I just trade my old phone for a tmobile gs2, everything was fine until I decided to do a factory reset, now I'm stuck on factory mode with a screen saying
"product name: sgh-t989
custom binary download: no
current binary; samsung official
Downloading...Do not turn off target!!"
What should I do? Help please, thanks in advance.
Hold the power button for 10 seconds.
Sent from my SGH-T989 using XDA App
Hi Alphadog32,
If you can still look at this 3-yo thread, can please help with a variation of this problem?
The same Download mode message came up permanently after I simply rebooted my GS2. It has been running a branch of AOKP 4.4.4 ROM for about four months. It had occasional problems - apps sometimes crash randomly and data mode sometimes goes down to EDGE until a reboot. I rebooted it because it was stuck in EDGE data mode again.
I held it for 10 seconds while the Up/Down Volume buttons. The phone started vibrating constantly both times until I let go, then came up to download mode again. It did not respond to Volume + key.
I also connected to Odin 3.07. Windows says that the last USB device has malfunctioned and Windows cannot recognize it. Hence Odin also does not see the phone on any COM Port. I am plugged with OEM cable.
Since the phone is running a non-Samsung ROM, maybe I need to install USB drivers other than Samsung's to have Odin work?
If so, which ones are correct?
Can you suggest anything else?
Hey guys. I have a samsung galaxy S3 SGH-i1747M Running ICS on Bell.
It asked me to do an update today, a full software update (Not jellybean clearly). I accepted it. It automatically turned off saying that it was going to re-boot. It never re-booted. Now it wont even boot. When I try and turn it on, it vibrates, splashes the samsung logo, says "Recovery Boot" in the top left corner, then just gives me a black screen. I cant get into download mode and Kies wont recognize my phone when plugged in. Im pretty stumped on what to do.
If you guys could help me out that would be great.
Thanks
ZiiC
ZiiC said:
Hey guys. I have a samsung galaxy S3 SGH-i1747M Running ICS on Bell.
It asked me to do an update today, a full software update (Not jellybean clearly). I accepted it. It automatically turned off saying that it was going to re-boot. It never re-booted. Now it wont even boot. When I try and turn it on, it vibrates, splashes the samsung logo, says "Recovery Boot" in the top left corner, then just gives me a black screen. I cant get into download mode and Kies wont recognize my phone when plugged in. Im pretty stumped on what to do.
If you guys could help me out that would be great.
Thanks
ZiiC
Click to expand...
Click to collapse
Don't panic simple to recover, what you need to do is flash your ROM manually using ODIN.
1 Of course you need to get ODIN
2 Since you already have kies, it should recognize the phone as soon as you plug in to PC when you get in Download modem you can only tell if it gets recognized in Kies you will see COM PORT number ON (Yello) or Blue
3 download the ROM from Bell...Here: http://samsung-updates.com/get/2569/Samsung_Firmware_SGH-I747M_BMC_I747MVLALH1_Android_4_0_4.html
once all all the files are ready, while phone off get it in Download mode
How to get into Download Mode (For Odin)need to extract the zip
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode
Open odin, CHECK ONLY PDA and direct to file (rom) you downloaded (might need to be extracted first)
Plug the phone, which by now should be showing the Download mode screen, WAIT until the computer is done recognizing and installing then Hit start button and wait be patient it might take some time, and the first boot will take a long time...
The above information is solid. However Bell has a 30 day "DOA" policy. So, if by chance you've only had it 29 days, you should rush to the bell store and tell them your newish phone couldn't handle a stock ICS update and they will swap it out. I tried updating mine (stock rom via kies) 5 hours after I bought it and I could never turn it on again... Complete brick. Bell store swapped it out no questions (I did not have the optional insurance).
If your past 30 days... See above post
Sent from my SGS3 i747m (Bell) on CM10 using TapaTalk2
I can`t get the phone in recovery mode.
Here is the issue:
Running Jedi mind trick rom three weeks. One day the phone restarted and got stuck in the boot screen.
The phone restarted and eventually keeps vibrating without display
After trying many times i did got in recovery mode so i could install the rom again (using darkside super wipe and then the rom). After one day it crashed again and again i installed an different rom which also crashed after several hours.
Now i can`t even get to download mode, Is this hardware related or do i need to use an usb jig to get this working again?
Does your phone screen turn on and at least show the Samsung logo? If not, and you said button combo presses do not work using a USB Jig will be your way to go to get back in to download mode.
By the way, did you flash the correct ROMs specifically for our phones? You shouldn't have experienced and crashes. Also, for the vibrating issue without the display, it had been mentioned that it could also be due to a stuck/dirty power button. If you can try, clean up around it.
FineTalent said:
Does your phone screen turn on and at least show the Samsung logo? If not, and you said button combo presses do not work using a USB Jig will be your way to go to get back in to download mode.
By the way, did you flash the correct ROMs specifically for our phones? You shouldn't have experienced and crashes. Also, for the vibrating issue without the display, it had been mentioned that it could also be due to a stuck/dirty power button. If you can try, clean up around it.
Click to expand...
Click to collapse
Yes it does show the samsung logo at starting up but after that it turns off with 1-2 seconds vibrating intervals.
I already cleaned the power button but without any satisfaction.
I did dropped the phone monday but not from a great heigth.
estimated: 1mtr above ground
Yes i did. I used the guides from galaxy2root.com
Well, if you were able to use a USB Jig to get into 'Download mode', get a stock ROM from here and flash it through Odin which is also included in the link. Good luck!
Ok so, Galaxy note 2 Gt-n700.
One day randomly turns off (not rooted/flashed). Go to turn the device back on and it gets stuck in a boot loop on the first screen, keep rebooting till it ran out of battery.
tried to go into recovery mode Vol up +middle +power. Nothing.
Then tried the other one.. Vol down + middle + power
hit continue at the firmware install and get RPMB: INVALID RPMD Data
Now googling this comes across alot of advice for PIT files and ODIN. when i tried to "install" this it comes up with an error that i cannot remember at the moment on ODIN basically saying cant its broke.
I have now got the phone saying that there is a firmware update and to connect to KIES and do emergency recovery. The damn phone will not connect to KIES and i have reinstalled KIES and all the drivers 500 times. Tried all usb ports.
Now im about 5 minutes from throwing this phone off a wall.
Can anyone help.
Much helps needed.
What ROM did you use before that happened?
If you not on 4.3 bootloader, try to flash oldest stock, one file, firmware through odin.
iJaake said:
Ok so, Galaxy note 2 Gt-n700.
One day randomly turns off (not rooted/flashed). Go to turn the device back on and it gets stuck in a boot loop on the first screen, keep rebooting till it ran out of battery.
tried to go into recovery mode Vol up +middle +power. Nothing.
Then tried the other one.. Vol down + middle + power
hit continue at the firmware install and get RPMB: INVALID RPMD Data
Now googling this comes across alot of advice for PIT files and ODIN. when i tried to "install" this it comes up with an error that i cannot remember at the moment on ODIN basically saying cant its broke.
I have now got the phone saying that there is a firmware update and to connect to KIES and do emergency recovery. The damn phone will not connect to KIES and i have reinstalled KIES and all the drivers 500 times. Tried all usb ports.
Now im about 5 minutes from throwing this phone off a wall.
Can anyone help.
Much helps needed.
Click to expand...
Click to collapse
Is your phone still going in bootloops?Try to enter download mode by pressing volume down+home button without pressing power and see if still goes into download mode.If it does then your power button is faulty.Two scenarios to that either power button is stuck on "pressed" mode which you can resolve by taking out the cover and screws and pushing out the power button (look up youtube video) or worse the power button needs to be replaced totally.If power button is working fine try what the above user stated flash the previous working stock version or flash the latest 4.4.2 stock ROM and see if it bootloop is resolved.
im having the same problem how did you fixed it ??
I wanted to root my Note10+.
It is a Note10+ SM-N975F. It is not locked to any carrier.
I enabled dev options, unlocked OEM, booted into download mode, and unlocked the bootloader. This was apparently successful.
I then tried to use Odin to flash stock rom. Odin fails at "system.img". I tried to flash with Chimera Tool. Chimera also fails at "system.img". I tried different stock roms (older versions etc.), the error perists. I tried on a different computer, the error persists.
So I decided to flash a patched TWRP, then I was gonna flash ROM throught TWRP.
I flashed TWRP and that leads me to now. My phone is effectively dead:
If I plug it in or turn it on, it boots to the "Samsung Galaxy Note10+" screen, it will tell me to press power to confirm that I understand that the phone's security has been bypassed/non-official software is installed. Then it will hang forever on the "Samsung Galaxy Note10+" screen.
There doesn't seem to be anyway to turn it off other than letting the battery drain, but even with the battery drained, if I plug it in, it will just boot to the "Samsung Galaxy Note10+" screen.
If I hold power + volume down, it will reset back into the "Samsung Galaxy Note10+" screen.
Whether it's on or off, power + volume up appears to do nothing
Any ideas? If I can get into download/recovery mode it should be fixable... But I can't even get there at this point!
Try different Odin.
Holding the power button for more than 10 seconds should always shut down.
Im happy to help if you are struggling?
Had the same bootloop symptoms, fixed!
i had the same bootloop when trying to update to beta android 10, let your phone drain completely, hold volume up and down at the same time, connect a usb cable and it should turn on to a download mode screen, flash latest rom (BL+AP+CSC+CP) and you re all set
Yep - solved in line with the above:
I let it it drain, then held vol up and down and plugged into computer - got into download mode recognised by Odin!