Related
what the hell is Samsung doing? I did not update last time with broken firmware and I tried this time with kies.
Now the problem came again.. It only appears Downloading... Do not turn off target and in Kies , it says fail to convert into safe mode...
Now Tablet stayed at the screen with "Downloading ... Do not turn off target!!!" No any response!
-------------------------------------
BTW, I never rooted.
Update. Thank you for everyone in this post for response.
After google from internet, I found a solution.
1) first, after you had "Downloading ... Do not turn off target!!!" screen, Please do not panic ( I did when it happened and really said f*^@ word to Samsung..forgive me...).
2) Press power button + volume down, and hold until it turns off.
3) say "god bless me" or "Mom, please save me." and press whatever combination of buttons you can.
4) It suddenly reboot after that and please use OTA to update. not kies.
5) as far as I can tell, works fine now. However, connect to Kies with wifi does not work.
Were you on a custom rom prior or rooted? If so, did you reset your tab to factory before doing the OTA?
Get back in recovery and flash your back up. If it fails you will have to ODIN your rom in
No problems here using kies, I was only rooted though and I still have root
Do I have to be connected to a PC to get this update? Isn't wifi enough?
You can use wi-fi for OTA update. OP's issue is that even though the tablet went into Download mode, Kies still didn't think it is in download mode. The firmware update hasn't even started to push down to tablet yet.
Based on the earlier problems, you're better off using Kies. If it fails, like it did for OP, it's smart enough to know that and when you disconnect and reconnect the Tab it should automatically go in to emergency recovery mode. What happened to OP happens occasionally with Kies updates. A lot has to do with the PC it's running on and what else is running on that PC. Kies is far from perfect and I'm guessing OP's issue isn't with the new ROM it's with Kies.
I didn't get the update OTA, but just updated with Kies. Had to re-flash CWM and root, but everything works just fine.
Changing to another USB port solved the problem for me. The drivers for the download stage to the tablet could not been loaded for the port I was connected first.
BR
Sent from my GT-P7510 using Tapatalk
flyingstore said:
what the hell is Samsung doing? I did not update last time with broken firmware and I tried this time with kies.
Now the problem came again.. It only appears Downloading... Do not turn off target and in Kies , it says fail to convert into same mode...
Now Tablet stayed at the screen with "Downloading ... Do not turn off target!!!" No any response!
Click to expand...
Click to collapse
exactly the same problem. no solution for me yet...
I repeat this: if you think Samsung's firmware and firmware updates are buggy, Kies is even worse.
foxbat121 said:
I repeat this: if you think Samsung's firmware and firmware updates are buggy, Kies is even worse.
Click to expand...
Click to collapse
Quite true. Kies is terrible. My Galaxy 10.1 wifi won't connect to it at all -- it just sits there attempting to connect. No indication of what's wrong, no log files, nothing. I wasted over an hour last night trying to figure out what was wrong -- removed all "ghost" USB devices, installed Intel INF driver updates, de-installed all active USB hubs & devices, etc.
I even updated Kies to 2.1 ... nothing. Very frustrating.
still no luck with upgrading with kies. it connects to tab, downloads the update to the pc,
the tab goes into download mode in order to install the update, and then connection between kies and tab is lost....
i have the latest kies, i have the drivers, i tried another usb port, i have done a factory reset, but still nothing.
Hello
I have a big problem with my note. today i wanted to change rom from imilka's AOSP ICS [IMM76D/4.0.4] to newest version of rocket. after flashing Abbys 4.2 kernel I missclicked to reboot button, after reboot phone got stuck and starting screen "Galaxy Note" I can even enter recovery, but can't do anything because if I try to move up or down then cwm got rebooted. Download mode works also BUT... The main problem is that after that fail with flashing I can't connect to pc. I tried with another cable/another pc/ reinstalled drivers and kies and still pc can't recoginze this device. any solutions? thanks in advance
If while flashing with Odin you receive an error message or got stuck on factoryfs the only thing you can do is to go to Samsung Assistance..
URcasm said:
If while flashing with Odin you receive an error message or got stuck on factoryfs the only thing you can do is to go to Samsung Assistance..
Click to expand...
Click to collapse
I can't connect to odin because pc doesn't see my phone connected :/ THAT'S MAIN PROBLEM
Dont panic !
please remove kies please and install the Samsung Galaxy Note USB drivers.
I will be online for you.
Please connect to PC Odin.
Let me know if you are not getting connected still ....
I too have a focus that is stuck in a loop at the Samsung logo. I bought it like that thinking I might be able to resurrect it as another toy. I have had lots of experience with Samsung, HTC and Sony droid phones, this would be the first WP.
It is a I917R on Rogers, there is no hardware revision under battery. I am assuming it is V1.3 as I have only seen software for the that version posted. I do not know how the phone got to its present state. They just said it happened during normal use?
I can get to both download mode and factory reset. I have flashed the stock rogers files without errors, but I never get the screen connecting to pc. The phone just restarts after successfully flashing, only to reboot continuously. I have been able to install MAGLDR and flashed every v1.3 ROM i could download. All without errors, just the same outcome they all just keep displaying Samung logo and then reboot. Only thing I noticed is that when I flash MAGLDR and custom ROMs it takes the phone longer to reboot.
I never get the connect to pc if I hold camera and power, nor do I ever get that screen when I flash a ROM.
Not sure if situation is similar... I am puzzled?
Your situation is very similar with other folks' here, unfortunately. It's not clear what causes it and there's no solution as of yet. For some, re-flashing worked. For others, a new battery. Most are stuck on loop...
When you connect the phone to USB when in download mode, what do you get?
When I boot to download mode I can flash Rom with WP7. I get to the yellow triangle download mode and flashes ok, no errors. Just noticed that it never goes to connect to pc mode.
Same with when I format, no connect to pc mode.
Nothing I try seems to help.
blackangel21 said:
When I boot to download mode I can flash Rom with WP7. I get to the yellow triangle download mode and flashes ok, no errors. Just noticed that it never goes to connect to pc mode.
Same with when I format, no connect to pc mode.
Nothing I try seems to help.
Click to expand...
Click to collapse
I see. What messages do you get when you connect the phone to the PC via USB, in either mode?
No messages, just shows up as Samsung USB composite device, Samsung mobile modem and Samsung mobile modem diagnostic serial port in download mode.
In magldr it shows up add Microsoft USB sync.
The only thing I forgot to mention was that when I flash with WP7 it finished without error in 90 seconds, but on the phone it says it will take 10 minutes.
Not sure what more I can add...
You could try different downloaders. Please see this thread for 7.41 downloader, maybe that helps?
Tried both, same outcome... No errors, just keeps rebooting... No Connect to PC message.
Im having the same problem. And i can see many other people who are having the same issue also. So i think its time to dump those phones, not worth a penny. The one i have in here was actually working, i followed all the directions in order to flash it. And still the phone got stuck into that bootloop. Its ridiculous from what i can see. I think ive read once you put that SDmini in it the phone will use it for the OS. But the one i had was working actually without it, i could turn it off as many times as i wanted and nothing happened. But if i tried a factory reset data would stay and diagnosis mode wasnt working. So i decided to flash it. Big, huge mistake! Hope you have better luck than i did. Because im dumping this one....
Same problem here, ive checked a couple of threads and no solution so far
Hello guys i was trying out the new Kangabean 4.3. ROM for my AT&T and after flashing it in TWRP it appears I has softbricked my device. I can only boot into download (odin) mode and it stays on "downloading now".. Anyhow i cannot boot into recovery it just vibrates to confirm my input and just revibrates and revibrates... Looked all over for guides and tried to return it to factory settings on Kies but it does not detect my phone... Any help would be great i need this phone for work everyday!!!
Karbooo said:
Hello guys i was trying out the new Kangabean 4.3. ROM for my AT&T and after flashing it in TWRP it appears I has softbricked my device. I can only boot into download (odin) mode and it stays on "downloading now".. Anyhow i cannot boot into recovery it just vibrates to confirm my input and just revibrates and revibrates... Looked all over for guides and tried to return it to factory settings on Kies but it does not detect my phone... Any help would be great i need this phone for work everyday!!!
Click to expand...
Click to collapse
Please search for similar threads. This same issue is being posted over and over and over again. When you were making this post, what "similar threads" or "similar topics" showed up? Did you check them for a solution?
yes sorry i looked at all of them and they all involved well just flashing the stock rom but i cant get my computer to see my gs4 on download mode...i got the drivers and odin installed.
Well, this thread has a couple of ideas...
http://forum.xda-developers.com/showthread.php?t=2405991
or maybe here...
http://forum.xda-developers.com/showthread.php?t=2405127
You might also want to look at the TWRP thread in the development section.
Try again to get into recovery, the key sequence can be tricky, make sure you are doing it just right. "Doing it just right" has been discussed many times.
Also, look at this thread, maybe it will help...
http://forum.xda-developers.com/showthread.php?t=2398336
Yea, I realize that thread is about MF3, but it still has ideas that might help you.
There are also a ton of threads about how to get your PC to recognize ODIN.....search.......good luck.
yeah ive been at it for hours man those links can all access the recovery i cant... i tried everything got the drivers up tried all the odins and its just stuck on "downloading do not turn off target" and my pc doesnt see it...
Odin finally recognized it on the pc in download mode and i was able to flash the stock rom but it seems it wasnts successful...it still just vibrates and vibrates when i press the power...
Try flashing the open recovery.
Sent from a jedi extacy note II
If you mean the CWM recovery I tried it on Odin and it failed.... :""(
Sent from my Nexus 7 using xda premium
Take battery out, back in, power+volumedown, download mode, Install Samsung Kies, do Kies update, connect to PC, Tools-> firmware initialization, take battery out and type model/serial Number, wait patiently until it finishes.
Try different USB port or different PC. Use stock USB cable comes with original box.
If Kies screen get stuck at model number section, you did flash MF3 triangle thingy -> unsolveable brick. Have to go thorugh warranty replacement.
Sent from my SGH-I337 using Tapatalk 4
the Kies Emergency firmware utility worked it put my phone like the day i bought it...also rooted it successfully and installed TWRP on it thanks guys
I tried searching, but it appears to be broken most of the day today. I did try searching page by page, but didn't get any results.
My brand-new S4 is softbricked apparently. From stock, two night ago, I rooted the phone based on this guide.
I then installed GooManager and installed the TWRP 2.3.6.1 recovery manager. All seemed fine. I was going to install a custom ROM, but decided to back up the phone first. So I booted to recovery and made a backup. I rebooted and all was fine. Then I rebooted to recovery to wipe the phone. I went into the wipe menu and selected Delvik Cache, and a couple more options but I can't remember which. I know I did have USB-OTS (or whatever it is) and that didn't work, so I undid that. I did not have SD Card selected.
The backup appeared to work fine. I rebooted and the phone gets to the "Samsung" screen with the small lock that says, "Custom" under it. That's as far as it gets.
I found this thread to restore the stock. However, when I tried to connect the phone in Odin mode, it will not recognize the phone. The PC recognizes the phone (it makes the noise) and Kies sees the phone, but won't do anything with it. It detects that a phone is connected and tries to identify the device, but can't.
The PC detects my wife's S4 just fine. I'm using the same cable.
BTW, if I try to boot to recovery mode, I get the Samsung lock screen (the same one it hangs up on), then a black screen for a few seconds. Then it goes back to the Samsung lock screen and just sits there. Oh. BTW, the phone does appear to go into download mode just fine. Hitting the Vol Dn button to cancel, does reboot the phone.
So I'm looking for help trying to get Odin to detect the phone. Any suggestions?
BTW, the phone will enter download mode just fine and the Vol Dn button does work to reboot the phone (though it still locks up during the boot sequence).
re: kies
Yippee38 said:
I tried searching, but it appears to be broken most of the day today. I did try searching page by page, but didn't get any results.
My brand-new S4 is softbricked apparently. From stock, two night ago, I rooted the phone based on this guide.
I then installed GooManager and installed the TWRP 2.3.6.1 recovery manager. All seemed fine. I was going to install a custom ROM, but decided to back up the phone first. So I booted to recovery and made a backup. I rebooted and all was fine. Then I rebooted to recovery to wipe the phone. I went into the wipe menu and selected Delvik Cache, and a couple more options but I can't remember which. I know I did have USB-OTS (or whatever it is) and that didn't work, so I undid that. I did not have SD Card selected.
The backup appeared to work fine. I rebooted and the phone gets to the "Samsung" screen with the small lock that says, "Custom" under it. That's as far as it gets.
I found this thread to restore the stock. However, when I tried to connect the phone in Odin mode, it will not recognize the phone. The PC recognizes the phone (it makes the noise) and Kies sees the phone, but won't do anything with it. It detects that a phone is connected and tries to identify the device, but can't.
The PC detects my wife's S4 just fine. I'm using the same cable.
BTW, if I try to boot to recovery mode, I get the Samsung lock screen (the same one it hangs up on), then a black screen for a few seconds. Then it goes back to the Samsung lock screen and just sits there. Oh. BTW, the phone does appear to go into download mode just fine. Hitting the Vol Dn button to cancel, does reboot the phone.
So I'm looking for help trying to get Odin to detect the phone. Any suggestions?
Click to expand...
Click to collapse
Try opening taskmanager in windows ( run >taskmgr ) and before you plug the phone into
usb on your computer end the KIES process in task manager, Kies should not be running
when you plug the usb from phone to computer.
What I have done a long time ago is to uninstall KIES as well as all the samsung usb drivers,
then I downloaded and installed the official Samsung usb drivers from here: http://downloadcenter.samsung.com/c...ng_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
after doing that I have never had any more issues with Odin flashing.
Good luck!
Misterjunky said:
Try opening taskmanager in windows ( run >taskmgr ) and before you plug the phone into
usb on your computer end the KIES process in task manager, Kies should not be running
when you plug the usb from phone to computer.
What I have done a long time ago is to uninstall KIES as well as all the samsung usb drivers,
then I downloaded and installed the official Samsung usb drivers from here: http://downloadcenter.samsung.com/c...ng_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
after doing that I have never had any more issues with Odin flashing.
Good luck!
Click to expand...
Click to collapse
Kies is not running in the background. I couldn't get either phone to be recognized by Win7 originally. However, once I uninstalled the driver and Kies, rebooted and re-installed both, I could get Kies and Windows to see the phones. BTW, Linux always sees both phones.
So I'll try your suggestion, and let you know.
I followed your suggestions. I uninstalled the drivers and Kies. Reboot and install drivers. I connected my phone and Odin didn't see it. I connected my wife's phone and windows did the "new hardware found" thing and installed the drivers. As soon as that was done, Odin recognized her phone. I unplugged her phone and plugged mine in and it doesn't see it.
It's almost like the phone doesn't get far enough into the boot process for the computer to recognize anything. It hasn't booted far enough, or something like that.
What firmwire is it on?
Sent from my SGH-I337 using XDA Premium HD app
MDL firmware as installed when I bought it (I got lucky).
My Odin is 3 v1.85.
USB drivers are SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.25.0-retail
Yippee38 said:
MDL firmware as installed when I bought it (I got lucky).
My Odin is 3 v1.85.
USB drivers are SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.25.0-retail
Click to expand...
Click to collapse
And you are sure it didn't self update on it's own to mf3? Your Odin and drivers seem right, however kies/Odin don't support mf3.
Sent from my SGH-I337 using XDA Premium HD app
---------- Post added at 10:27 PM ---------- Previous post was at 10:23 PM ----------
If you're still on MDL and can get into recovery, Mount to usb and throw a ROM onto your internal; or use a sdcard and put it in your phone and flash a new system. Possibility your nandroid is broken, it can happen.
Sent from my SGH-I337 using XDA Premium HD app
I don't think so. Every time the update message came up, I just hit the home screen button to go away from it. I don't see how it could have.
I was under the impression that it wouldn't update if the phone was rooted, but maybe I'm wrong about that.
I guess, if it did update, I'm completely screwed, right?
And is there anyway I can find out if it did update?
Yippee38 said:
I don't think so. Every time the update message came up, I just hit the home screen button to go away from it. I don't see how it could have.
I was under the impression that it wouldn't update if the phone was rooted, but maybe I'm wrong about that.
I guess, if it did update, I'm completely screwed, right?
Click to expand...
Click to collapse
Only way it won't update to MF3 If you already had a custom rom on it , but if you rooted it while on MDL and didn't flash a custom rom then update will go in automatically!
Damnit. That sucks.
I guess I'll try the BB restore method. Hopefully, it will work. Thanks for the help all.
Well, good news and bad news.
The good news is that I've got the phone back to stock MDL!!!! <whew!> The bad news is that I'm an idiot.
Where I screwed up was that when I connected the phone, I had only done the VolDn, Home and Power button into download mode. What I didn't do was hit the VolUp from that screen to actually get into download mode. As soon as I did that, Odin recognized it. I was then able to use this method to reflash it with stock MDL. Now I'm back to stock and with MDL.
Hopefully, this if somebody else forgets this important step, this thread will help them.
Thanks to everybody for the help though! It got my mind thinking the right way to find the solution.
Yippee38 said:
I don't think so. Every time the update message came up, I just hit the home screen button to go away from it. I don't see how it could have.
I was under the impression that it wouldn't update if the phone was rooted, but maybe I'm wrong about that.
I guess, if it did update, I'm completely screwed, right?
Click to expand...
Click to collapse
You can only stop the update temporarily, in fact just pressing the home screen doesn't stop the process and it'll eventually force update even with the screen off at idle. Just a root won't stop the updating, unless you froze the necessary processes or flashed a different ROM and framework it'll find a way to update.
Sent from my SGH-I337 using XDA Premium HD app
---------- Post added at 12:34 AM ---------- Previous post was at 12:32 AM ----------
Good job at getting it back and up! Note make sure it won't update on you.
Sent from my SGH-I337 using XDA Premium HD app
Br4nd3n said:
You can only stop the update temporarily, in fact just pressing the home screen doesn't stop the process and it'll eventually force update even with the screen off at idle. Just a root won't stop the updating, unless you froze the necessary processes or flashed a different ROM and framework it'll find a way to update.
Sent from my SGH-I337 using XDA Premium HD app
Click to expand...
Click to collapse
I'm very worried about that now. I rooted my wife's phone. She doesn't want a custom ROM. I told her not to update it, but once it does, I have problems. I have to figure out which processes to freeze to prevent the update apparently before it tries to do it itself. At least she knows not to manually update it.
I found the stuff I needed to do to block the update on my wife's phone. All is good.