Many have this problem please help! - Galaxy Tab Q&A, Help & Troubleshooting

After upgrading the firmware successfully according to odin our P1010 wifi-only galaxy tabs are stuck in an infinite reboot sequence that happens so quickly that we cannot use our galaxy tabs for anything. Right before it reboots we are all getting:
"Process android.process.media stopped unexpectedly. Try again"
This occurs immediately after the upgrade when you are doing the initial setup of the device. It is rebooting about every 15-30 seconds.
Please help us. We can still download using odin but we do not have the stock firmware. Someone out there help please. We are all going absolutely bonkers insane. Thx.

Try this : http://forum.xda-developers.com/showthread.php?t=961732

bongski55 said:
Try this : http://forum.xda-developers.com/showthread.php?t=961732
Click to expand...
Click to collapse
Dont mean to be rude but i just read that whole thread and it has absolutely nothing to do with the problem we are having. not once in that thread is mentioned any problems after upgrading firmware. in fact the thread seems to be about the P1000 with only a small bit about the P1010 which is unrelated to our problem.
Does anyone else have a solution or anything helpful?

frootloops said:
Dont mean to be rude but i just read that whole thread and it has absolutely nothing to do with the problem we are having. not once in that thread is mentioned any problems after upgrading firmware. in fact the thread seems to be about the P1000 with only a small bit about the P1010 which is unrelated to our problem.
Does anyone else have a solution or anything helpful?
Click to expand...
Click to collapse
sorry for not explaining. I thought you might want to use/flash the particular p1010 firmware discussed in that thread instead of what you have right now so as to eliminate/erase your error/problem.
I don't have a p1010 so I cannot verify. Next time I will not respond anymore to avoid misunderstanding.

frootloops said:
Does anyone else have a solution or anything helpful?
Click to expand...
Click to collapse
Did you solve your problem?

andrewin said:
Did you solve your problem?
Click to expand...
Click to collapse
no, i just gave up. my tab has been sitting on my desk for like 3 months unused. i guess i'll try recharging it if i can find it buried under the pile of papers and giving it another attempt at finding a solution.
not going to hold my breath tho... since it appears to be impossible to find the official united states p1010 firmware or whatever u guys call it.

bongski55 said:
sorry for not explaining. I thought you might want to use/flash the particular p1010 firmware discussed in that thread instead of what you have right now so as to eliminate/erase your error/problem.
I don't have a p1010 so I cannot verify. Next time I will not respond anymore to avoid misunderstanding.
Click to expand...
Click to collapse
sorry, didn't mean to offend you. i am just so utterly miserable about this device. i was so excited to get it, then i read about updating to fix some speed issues and increase battery life so i followed the guide and so i have only been able to use my device a total of about 1 day in about 5 months. very frustrating.
also, i am deathly afraid of "just trying" to flash anything as i dont want to make my device even worse than it already is.
i'll tell u one thing, i will never ever ever ever buy another samsung product again. they so very clearly dont give a rat's a** about the suffering of their customers. it doesn't matter if we did this to ourselves, they should still help. it is a stupid software fix that costs them nothing. do they think if they dont help us we will break down and buy a second one? i dont f'ing think so.

I had the same problem once.
Maybe the files are not matching like .PIT with Modem or bootloader thats why it keeps on restarting.
You should reinstall .PIT file then install accurate PDA , CSC and MODEM files for your own region.

omr911 said:
You should reinstall .PIT file then install accurate PDA , CSC and MODEM files for your own region.
Click to expand...
Click to collapse
Yea, this is the problem. Cant get United States region files. That is the whole issue.

SOLVED !!!
if you are having the infinite reboot problem on your US galaxy tab gt-p1010 do this:
1. download this rom (it is the hong kong rom)
http://www.multiupload.com/KJO2KALU2O
password: nomoreuncheckedfirmwares
2. put your tab in download mode by holding down the volume down button first then press and hold the power button.
3. start odin3 version 1.7, plug your tab into your pc.
4. verify you have the yellow in the ID:COM area in odin then select the pit file, the csc file and the pda file (the only file remaining) and hit start.
5. wait patiently while it downloads everything and reboots.
note that it will start up in chinese or japanese (not sure which, guessing chinese). also note that i am using windows xp, probably works in 32-bit windows 7 but may have problems with 64-bit windows 7. not sure cause i have not tried it. seems that i read that though.
good luck !!!
thanks to stsights for the solution and waqypaqy for uploading the file to a more accessible site!!! you guys make me more happy than u can possibly know...

frootloops said:
Yea, this is the problem. Cant get United States region files. That is the whole issue.
Click to expand...
Click to collapse
If US firmware is not available then install European Firmware

NO NO NO
omr911 said:
If US firmware is not available then install European Firmware
Click to expand...
Click to collapse
NO NO NO!!! This is what got the problem started in the first place. do NOT install european firmware on a US galaxy tab P1010. That will land u in infinite reboot hell. just dont do it.

Related

[Q] Firmware need for Tablet bought from a trip in Saudi Arabia

Hi all,
I bought the P1000 galaxy tab back from Saudi Arabia when I was visiting there for business. After coming back home I wanted to flash a European firmware on to it.
Unfortunately following this attempt, the tablet just displays a battery charging symbol with no actual progress and does not go into download mode.
As the device was built to be sold in the Middle East, can you advise on what firmware should be used to reflash this device? All firmware I've tried from samsfirmwares.com has not worked and all have failed to boot. The best I could get was the Samsun Galaxy TAb logo during startup and that's it, it hung there. Now it's even worse, just displaying the battery symbol and nothing happens.
Thanks for your help in advance,
Try These instructions with Rotohammer JMIv2 firmware:
IF your Tab does not boot after flashing the kernel and hangs at the Samsung Galaxy Tab screen, you must follow the following procedure
Get a stock rom package (any of Rotohammer's firmwares will work)
Get P1_add_hidden.zip attached to this post and extract the P1_add_hidden.pit file
Using Odin 1.7, put stock rom (Roto-JME-Full-v4.tar for example) in PDA slot.
Put P1_add_hidden.pit in Pit slot
Check repartition box
Put Tab in download mode by holding Volume Down and Power, connect to the computer, and press start.
After this, the Tab will reboot normally.
Thanks DarkPal, appreciate the quick response. I'll give this a try and update this thread. In the meantime, can you let me know where I can get the rotohammer firmware? I'll definitely search for it but if there is a known good location I'd appreciate it.
oguzhanf said:
Thanks DarkPal, appreciate the quick response. I'll give this a try and update this thread. In the meantime, can you let me know where I can get the rotohammer firmware? I'll definitely search for it but if there is a known good location I'd appreciate it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=939360 Here you Go. Hope you boot successfully. Don't use Samfirmware ROMs they have locked bootloaders.
Unfortunately I have the same Galaxy Tab logo and Samsung on the bottom. It just stays there. I've lost trust that this tablet will revive. Do you have any further ideas?
I tried
1. PIT + RePartition + Start + PDA ROM + Start --- Result same
2. PIT + PDA + RePartition + Start --- Result same
Just do one step at a time.
1. Get into download. Connect to pc. See the yellow box in odin. Pit file and check repartition, flash. Disconnect from pc.
2. Reboot into download. Connect to pc. Rom in pda, no check for repartition. Flash. Reboot into normal mode. If ok start, go back and flash your modem.
Captain, thanks for the steps. I've tried exactly word by word what you've sent earlier. Same thing happens.
There is a way to get into download mode, where you do something like squeeze the battery screen while holding power and volume down, but I'm not sure of the exact steps. Also one method involves the usb cable.
Can someone get us those alternate methods to get into download mode?
Is this stuff in the stickies for development?
rangercaptain said:
There is a way to get into download mode, where you do something like squeeze the battery screen while holding power and volume down, but I'm not sure of the exact steps. Also one method involves the usb cable.
Can someone get us those alternate methods to get into download mode?
Is this stuff in the stickies for development?
Click to expand...
Click to collapse
If you looking for the touch screen reset procedures, I think this link will bring you there, look for Beards threads. http://forum.xda-developers.com/showthread.php?t=921848
For me, it doesn't work when I have issue with the battery indicators. But you can try it to reset.
Thank you henrylam for the link.
oguzhanf said:
Hi all,
I bought the P1000 galaxy tab back from Saudi Arabia when I was visiting there for business. After coming back home I wanted to flash a European firmware on to it.
Click to expand...
Click to collapse
I have the exact same scenario as this but have yet to change the Rom as I'm not sure what benefit there actually is?
Custom roms aside, will my Tab actually be any better with a Euro rom on it as it can currently do everything I think it's supposed to.
Will I loose or gain anything?
*Bump*
Can someone please help with my question above?
maplebank said:
*Bump*
Can someone please help with my question above?
Click to expand...
Click to collapse
Phone capability only.
rangercaptain said:
Phone capability only.
Click to expand...
Click to collapse
Sorry, I don't follow your answer?
I've already got full phone capability using a UK sim (the unit is unlocked).
Why would this change by swapping the rom?
Was about to say warantee but they can tell from hardware
Sent from my GT-P1000 using XDA App
maplebank said:
Sorry, I don't follow your answer?
I've already got full phone capability using a UK sim (the unit is unlocked).
Why would this change by swapping the rom?
Click to expand...
Click to collapse
It won't. But you said you hadn't flashed the euro rom, which normally is done to gain phone capability.
Your phone had already been rom-modified by someone, because phone capability isn't a stock feature for any carrier.

Need the touchscreen firmware

Hi guys. Fist of all, sorry for my bad english.
I bricked my phone's touchscreen, with update firmware in the *#*#2663#*#* and its wrote 'update failed' . My bad, dont do this. Dou you know any solutions? I tried factory reset, flashing roms ( froyo and gongerbread too), but nothing helped. The touchscreen stopped responding. But i think, if i can reflash the touchscreen firmware, it will working. It is possible flash the touchscreen firmware from sd card? Actually where are the files of the driver in the file system?
Can we explain, what happened actually when click on update on the tsp firmware screen? Which application/ script started? I thinks, the touchscreen files are in the tsp ic, which is separated from the flash, so just flashin a new rom dont write data to the tsp ic. But the files must be in the rom too, because some people did the update without problem, and the firmware version is changed, and the touchscreen works better then before. Do you have some ideas? If you have root acces, please browse the system folder, i thinks there is somewhere a "tspupdate" or similar named shell script/application what i need. But dont run it, it can brick your touchscreen too!!!
Sorry for my bad englis.....
problem solved
salmaj said:
problem solved
Click to expand...
Click to collapse
How did you solve it?
Yeah! How did you solve it? I currently have the same problem on my Bell's Vibrant. I also tried reflashing my Gingerbreak and factory reset without any success.
You don't know what you got til it's gone! Back button is really useful!
tasp update
salmaj said:
problem solved
Click to expand...
Click to collapse
Hi buddy, i m facing the same problem, plaease share your solution, as i am stuck and my touchscreen becomes unresponsive after wake up. Really tired of reading the forums. Thanxs a ton budddy
galaxy tab p1000 india
please
salmaj said:
problem solved
Click to expand...
Click to collapse
Please, How did you solve it?
How?????????????????????
salmaj said:
problem solved
Click to expand...
Click to collapse
Please tell me how did you do it
guess op bricked or lied or...
is just being a greedy attention whore?
THIS MAY MAKE THINGS WORSE, BUT SOME DO NOT CARE. DRAGONS AHEAD....
Either way hoarding knowledge is a big peev of mine. I have read about this issue from as many google'able places as possible. I started reading after I went thru the release notes from some of the sX series. I notices that some carriers listed ghost/glove tsp firmware update/support. I also noted as the original poster did, that the files are in the rom. I would guess look thru all the updates your carrier made available and download the specific whole rom update and factory restore / apply it. Should this not work look thru the system folder for the file. When you have it copy it to your sd card where the tsp update screen tells you to put it. Try running the update again.
If this works please confirm this.
I think possible looking in system folder I recall a firmware folder possibly inside lib or modules somewhere.
I read that tsp modes are controlled from, so logically the files should be nearby.
/sys/class/sec/tsp
or depending on phone/model
/proc/touchpanel
I will keep an eye here, I am busy with some debricking and roms in general.

[Q] Need help - My Galaxy Tab SPH-P100 Bricked

​
I have tried installing EA24 stock (http://forum.xda-developers.com/showthread.php?t=1133053) but still Freeze when booting. The error message shown on the picture. I am clueless and need your help.
gtabspring said:
​
I have tried installing EA24 stock (http://forum.xda-developers.com/showthread.php?t=1133053) but still Freeze when booting. The error message shown on the picture. I am clueless and need your help.
Click to expand...
Click to collapse
I had a more complicated version of this. couldn't format, couldn't mount, nothing. My tab showed this, I tried flashing several different kernels/roms/cwm, everything, nothing. Actually made it worse. It got to a point where when I powered on, I only got the backlit softkeys. A few times I got a weird image I've never seen before. Something about bad or unknown upload mode (with a little droid in teh corner....should have taken a picture). And finally I would get nothing; HOWEVER, if I plugged my tab into my laptop and gave it a few seconds, ODIN would see it. I could try flashing a kernel, but it would never process, just hang at the first step so....
with the tab plugged into the laptop and ODIN showing a connection, I would hold VOL DOWN + POWER until I see it disconnect (this is evident of a power down since I have no lights to indicate that). Once it disconnects (yellow box disappears) you can let go of POWER but do NOT release VOL DOWN. It will reconnect shortly thereafter. You are now in Download mode (whether or not you actually see anything on the tablet. You can test this theory by flashing something. What fixed it for me? I downloaded firmware from samfirmware.com. Specifically I downloaded JJ7 v2.2 (full file name I used was P1000XWJJ7.rar) I think what made the difference was using all 3 files. I did not use a PIT file, I put P1000XWJJ7-REV03-ALL-CL669843.tar.md5 in the PDA box, MODEM_P1000XXJK5_REV_00_CL690077.tar.md5 for Phone, and GT-P1000-CSC-MULTI-OXXJK2.tar.md5 in CSC. I did NOT check repartition. Now, this was after I had tried several things like flashing PIT by itself, different stock kernels, full ROMs, etc.... This was the final step I took. Now I'm back to normal.
I'd be interested to see if this solves anyone else's problem. I am so thrilled that I just fixed my "bricked" tab (no power, no response, no apparent charging even) that I'm hoping my time and effort can help someone else.
Let us know what happens. I am actually scouring the forums now because I know at least 2 others were having similar problems as I and maybe this will help them as well.
BTW, I did lose EVERYTHING on the internal SD, including all my backups. Thankfully I always made backups to External
P.S. I should mention it is an AT&T (GSM) Tab.
swedishcancerboi said:
I had a more complicated version of this. couldn't format, couldn't mount, nothing. My tab showed this, I tried flashing several different kernels/roms/cwm, everything, nothing. Actually made it worse. It got to a point where when I powered on, I only got the backlit softkeys. A few times I got a weird image I've never seen before. Something about bad or unknown upload mode (with a little droid in teh corner....should have taken a picture). And finally I would get nothing; HOWEVER, if I plugged my tab into my laptop and gave it a few seconds, ODIN would see it. I could try flashing a kernel, but it would never process, just hang at the first step so....
with the tab plugged into the laptop and ODIN showing a connection, I would hold VOL DOWN + POWER until I see it disconnect (this is evident of a power down since I have no lights to indicate that). Once it disconnects (yellow box disappears) you can let go of POWER but do NOT release VOL DOWN. It will reconnect shortly thereafter. You are now in Download mode (whether or not you actually see anything on the tablet. You can test this theory by flashing something. What fixed it for me? I downloaded firmware from samfirmware.com. Specifically I downloaded JJ7 v2.2 (full file name I used was P1000XWJJ7.rar) I think what made the difference was using all 3 files. I did not use a PIT file, I put P1000XWJJ7-REV03-ALL-CL669843.tar.md5 in the PDA box, MODEM_P1000XXJK5_REV_00_CL690077.tar.md5 for Phone, and GT-P1000-CSC-MULTI-OXXJK2.tar.md5 in CSC. I did NOT check repartition. Now, this was after I had tried several things like flashing PIT by itself, different stock kernels, full ROMs, etc.... This was the final step I took. Now I'm back to normal.
I'd be interested to see if this solves anyone else's problem. I am so thrilled that I just fixed my "bricked" tab (no power, no response, no apparent charging even) that I'm hoping my time and effort can help someone else.
Let us know what happens. I am actually scouring the forums now because I know at least 2 others were having similar problems as I and maybe this will help them as well.
BTW, I did lose EVERYTHING on the internal SD, including all my backups. Thankfully I always made backups to External
P.S. I should mention it is an AT&T (GSM) Tab.
Click to expand...
Click to collapse
Thanks for the suggestion. I think your version of galaxy tab is different with mine and I am not sure that it will work. I am really desparate for solution. This disaster started when the tab's battery is low and suddenly off and when it's charged and turned on it bricked
Point being, tabs are tabs. You will need to use the same procedure, but a different ROM that is designed for your tablet. Go there and find a ROM. There is a thread about unbricking your tablet, I think in the Android Development section that should have a link to samfirmware.com and may provide you with a ROM version that should work. something that may help: plug your tab into the charger at least overnight. I used the stock charger and cable and charged it for 12 hours or so. I did not get any indication that it was charging since the screen and softkeys would not respond, but it did charge.
Of course, I look back and I think you have an indicator, but still a good idea. Try it anyway. Can't make it worse, eh? Mine seemed hardbricked, but it wasn't. I was real close to taking it apart before I found something that works. I believe, IMO, what really fixed it is flashing ROM (PDA), Modem, and CSC files all at once. It could have been something else, but that was the last thing I did before it finally booted.
Go to samfirmware.com, create a free account, and sign in. Then go here (I think your tab is a P1010, correct?) http://www.samfirmware.com/WEBPROTECT-p1010.htm
and Download this:
1010XWKC1 ## MULTI - CSC - OXXKC1 P1WIFI 2.2.1 2011 March DOWNLOAD
(click on DOWNLOAD)
Unzip that file you just downloaded
Start ODIN
Hold VOL DOWN and plug in tab to computer
I believe 3 files should be in the .rar (you can use 7-zip to open, Google it)
the MODEM file goes in Phone.
the CSC file goes in, you guessed it, CSC
last one is PDA.
I think I just rewrote instructions that can be found in the Galaxy Tab Bible. lol. This is what I would do. It worked for me.
Password for P1000XWJJ7.rar
Gentlemen,
I've downloaded both P1000XWJJ7.rar and P1010XWKC1_OXXKC1 to fix my bricked tab, but both require a password to extract the archives. Does anyone know the password? Has anyone had the same issue? I doubt it, otherwise i think it would have been addressed. Any help is appreciated.
I'm having the same problem were you able to fix it?
jairo_pena said:
Gentlemen,
I've downloaded both P1000XWJJ7.rar and P1010XWKC1_OXXKC1 to fix my bricked tab, but both require a password to extract the archives. Does anyone know the password? Has anyone had the same issue? I doubt it, otherwise i think it would have been addressed. Any help is appreciated.
Click to expand...
Click to collapse
try sampro.pl
see if that works.
I too require the passwords to be able to extract these files if someone would be so kind.
Copied straight from SamFirmware.com. It is right at the top of the download page.
try both of these... seems it could be either one of them
## Password is samfirmware.com
# Password is samsung-firmwares.com
Click to expand...
Click to collapse
where can i get these files for the sprint version of the tab i believe the model is p100 I don't see it listed on the recommended website
oxbeast1210 said:
where can i get these files for the sprint version of the tab i believe the model is p100 I don't see it listed on the recommended website
Click to expand...
Click to collapse
do a quick search of the dev thread for EA24 and you should be able to find the original SPH-P100 files. then you can find the EB28 and EF17 updates as well to get all the way to the official GB release.
tried the suggested file still get the error that the OP got in the first screen
oxbeast1210 said:
tried the suggested file still get the error that the OP got in the first screen
Click to expand...
Click to collapse
ok, no one likes a bricked device so let's see what we can do to help you. tell us where you are with your problem. by that i mean what model do you have, what rom were you running, what did you do or try to do that bricked your phone. i'll keep an eye on this thread looking for your response and we'll go from there.
I have the sprint p100 model room was stock rooted gingerbread.
I mailed the Tab to my brother when he got it tab battery was
completely dead and after he charged it and turned it on
he had that error
---------- Post added at 01:30 AM ---------- Previous post was at 01:29 AM ----------
thank you very much for helping me!!
can anyone help?
I have the T-Mobile version of this, but here's a guide and download files to recover your stock ROM. You can follow the entire guide if you want the Overcome ROM as well:
Guide:
http://www.teamovercome.net/p1000/?page_id=17
Downloads:
http://www.teamovercome.net/p1000/?page_id=21
Good luck!
NOTE:
Sprint modem is not listed, but you can fix that later. If you can get it to work with this guide & using the last modem file, we can go from there.
gtabspring said:
​
I have tried installing EA24 stock (http://forum.xda-developers.com/showthread.php?t=1133053) but still Freeze when booting. The error message shown on the picture. I am clueless and need your help.
Click to expand...
Click to collapse
try the one on teamovercome . net I have soft bricked mine but it worked after i followed their instructions there..
Has anyone EVER confirmed that overcome work for non GSM tab, for unbricking and CwM functions?
Sent from my GT-P1000 using XDA

Tried updating to ICS through KIES. Update failed

Hello guys.
I really need some help. Im going away for 2 weeks on 4 June. And after i come back ill be ghone after 2 days again for 2 weeks and i need my phone!
My story:
I saw an update for my phone to ICS. So i plugged on my laptop and put the update on with KIES 2.1.3.
At about 64% the update didnt go ferther and it gave an error report.
The program KIES shut down, and my phone turned off.
I putted everything back on. But now my phone says this:
''Firmware upgrade encountered an issue. Please select recovery mode in KIES & try again.''
KIES doesnt see my phone anymore. And the recovery mode i found on the internet.
Volume button up, home button+ power button doesnt work.
It keeps going to this screen.
My phone was 2.3.6 standard, non rooted etc etc.
How can i fix this fast?
I tried rooting and flashing, but i just cant do anything with my phone exept this screen i explained.
Thanks in advance.
Mitchell
Can you get your phone into download mode.
Device off>vol-down+home+power ?
Belfia said:
Can you get your phone into download mode.
Device off>vol-down+home+power ?
Click to expand...
Click to collapse
I didnt knew about this mode.
Yes it worked.
Seems a little bit like hope for me?
Thanks.
damitch300 said:
I didnt knew about this mode.
Yes it worked.
Seems a little bit like hope for me?
Thanks.
Click to expand...
Click to collapse
Just download ODIN app for Windows, get right stock firmware from development thread ( Dr. Ketan's post ) and flash it with ODIN. It's as simple as clicking select file and start. Everything is described in the thread with firmware downloads.
Yes. Then there is hope. Now I recommend you to try flashing one of the stock roms from dr.ketans thread in development section.
Its not very complicated. But feel free to ask if you need more help.
I just cant explain how happy i am with this forum.
Brings so much luck into live
Thanks.
Ill see if i need more help. Hopefully not.
Is there any dutch ICS rom?
Or should i stick with a basic english?
I got exactly the same problem. Called T-Mobile's helpdesk. With everything I asked, the girl said, it's in the manual. Finally, the best she had to offer was for me to send my Note to Samsung.
So then I started looking for a solution myself and found it here.
Solved it with the said solution. Flashing with Odin is a piece of cake. Thanks for the expertise folks.
Good thing we can help. Wouldnt call myself an expert though
damulder said:
I got exactly the same problem. Called T-Mobile's helpdesk. With everything I asked, the girl said, it's in the manuel. Finally, the best she had to offer was for me to send my Note to Samsung.
So then I started looking for a solution myself and found it here.
Solved it with the said solution. Flashing with Odin is a piece of cake. Thanks for the expertise folks.
Click to expand...
Click to collapse
Well i searched for hours to. My sister had her S2 upgraded with KIES. That worked, but the ICS update itself was plain suck.
I fixed it thanks to XDA forum. Nothing found on the internet exept sending to help desk.
Same with what i got now.
But now it is fixed and im thankfull to the ones helping.
Now i am willing to try ICS without KIES.
Lol in kies you have recovery mode you missed an option
Good thing you got it fixed
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
Lol in kies you have recovery mode you missed an option
Good thing you got it fixed
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Like i said, KIES didnt see my phone. Neither did windows.
So it wasnt an option.
Glad its fixed
Sent from my GT-N7000 using Tapatalk 2
BTW, after getting my Note up and running again, I used KIES again for updating to ICS and this time I had no problem at all.
damulder said:
BTW, after getting my Note up and running again, I used KIES again for updating to ICS and this time I had no problem at all.
Click to expand...
Click to collapse
For me this didnt work. KIES had an upgrade, but seems like it still doesnt do the job right.
Ran some tests. Now i am back at the issue.
Now Odin doesnt want to continue updating like KIES always does.
I wish i didnt do the tests...
damitch300 said:
Ran some tests. Now i am back at the issue.
Now Odin doesnt want to continue updating like KIES always does.
I wish i didnt do the tests...
Click to expand...
Click to collapse
what tests are you referring to?
and i'm guessing you're on Mac? and having trouble with kies identifying your device?
ngocdao said:
what tests are you referring to?
and i'm guessing you're on Mac? and having trouble with kies identifying your device?
Click to expand...
Click to collapse
W7 Ultimate N
And trying out different KIES versions.
Well at the 2nd update 2.3.6 to 4.0.3 it ran stuck again.
And now Odin doesnt do anything to aswell. Keeps saying ''Failure'' after some time.
Now ODIN is stuck at syaing ''BOOT'' above ID:COM.
How can i fix this?
Well seems like the Dutch roms aint working.
I did an European right now wich worked.

"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try aga

"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try aga
My watch is stuck on a screen saying
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I can't get it to connect to Odin, adb, anything...
Can't get it into recovery or download mode.
If I hold the power button, it just flashes off quickly, then straight back into that screen.
Any ideas??
I understand you're in a panic because your device is having issues. But please read the forum rules and search for your issue before posting the same question in multiple threads like you just did. By you posting the same question over and over searching becomes difficult and people are less likely to help. Please try searching again. If you can't find a resolution post exactly what you did, and what files you were trying to load.
I haven't had any further progress.
When I try to flash with Odin, it gets stuck at SetupConnection..
lokidokie said:
I haven't had any further progress.
When I try to flash with Odin, it gets stuck at SetupConnection..
Click to expand...
Click to collapse
Did you find out how to go on download or recovery mode?
americo85 said:
Did you find out how to go on download or recovery mode?
Click to expand...
Click to collapse
No, but the device does "show up" in Odin. But again, doesn't get past Setup Connection when I try to flash something.
Ok... Fixed my issue.
Just had to flash the MK7 firmware. That was the ONLY one that works.
Thanks all!
lokidokie said:
Ok... Fixed my issue.
Just had to flash the MK7 firmware. That was the ONLY one that works.
Thanks all!
Click to expand...
Click to collapse
Could you please tell us how you fixed your issue?
americo85 said:
Could you please tell us how you fixed your issue?
Click to expand...
Click to collapse
If you would please read. The answer is in the post above yours!!!!!!!!!!!
You even quoted the answer!!!
americo85 said:
Could you please tell us how you fixed your issue?
Click to expand...
Click to collapse
Yeah mate,
You just have to download a stock MK7 firmware from sammobile. I don't think it matters which region, I used Australia (because that's where I am).
Then connect up the watch, right click on Odin 3.09 to "open as administrator", make sure the watch shows up in a "COM" port, load the MD5 into AP, then start.
Not sure how much more detail I can give.
Good luck guy!
lokidokie said:
Yeah mate,
You just have to download a stock MK7 firmware from sammobile. I don't think it matters which region, I used Australia (because that's where I am).
Then connect up the watch, right click on Odin 3.09 to "open as administrator", make sure the watch shows up in a "COM" port, load the MD5 into AP, then start.
Not sure how much more detail I can give.
Good luck guy!
Click to expand...
Click to collapse
That's exactly what I did but for some reason mine is not working
I got the same issue. When i do it, im still stock at "SetupConnection.."
By the way, im from Denmark, so which region do i have to choose? Cause, denmark is not on the list.
And, what were you flashing at first when you bricked your Gear ?
A friend of mine went through the same problems 2 days ago, he tried to flash directly Tizen 2.2.1.1 over Null_rom (Android), and it went bad like your Gear.
I found out he needed to first flash Tizen 2.2.0, the very first Tizen version that came out.
This version weights 200MB+ than the latest.
I guess it's all the Android -> Tizen conversion software and tools that are embedded, and if flashing a newer Tizen version directly, it fails because of this 200MB+ stuff lacking in the rom.
Is it what you did too ?
I don't know if this is documented somewhere down here, didn't searched before reply.
edit: user nunyabiziz too had sorted it out : http://forum.xda-developers.com/showpost.php?p=53872341&postcount=3
chleb said:
And, what were you flashing at first when you bricked your Gear ?
A friend of mine went through the same problems 2 days ago, he tried to flash directly Tizen 2.2.1.1 over Null_rom (Android), and it went bad like your Gear.
I found out he needed to first flash Tizen 2.2.0, the very first Tizen version that came out.
This version weights 200MB+ than the latest.
I guess it's all the Android -> Tizen conversion software and tools that are embedded, and if flashing a newer Tizen version directly, it fails because of this 200MB+ stuff lacking in the rom.
Is it what you did too ?
I don't know if this is documented somewhere down here, didn't searched before reply.
edit: user nunyabiziz too had sorted it out : http://forum.xda-developers.com/showpost.php?p=53872341&postcount=3
Click to expand...
Click to collapse
That is exactly what i did
But i've tried with Tizen 2.2.0 too. Does the same thing.
I had this prob went from android to tizen by mistake. Had to find firmware an install it again. Back running though
Sent from my Nexus 5 using Tapatalk

Categories

Resources