I have an ATT Galaxy S3 its been two days I've been trying to update from 2 different computers. I don't know what else to do. Someone please help me
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
GrapePopRocks said:
I have an ATT Galaxy S3 its been two days I've been trying to update from 2 different computers. I don't know what else to do. Someone please help me
Click to expand...
Click to collapse
Couple of questions before anyone can answer...
1 . How are you trying to update .. through KIES or ODIN ?
2 . How are you connecting it to your computer via USB .. Front or Rear ports ?
Using Kies and side ports on laptop
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Are you using the micro usb cable that came with the phone?
A lousy cable or as mentioned above a crummy usb port could be a source of problems. Also is the laptop plugged in and the s3 fully charged?
Kies uses Odin to flash the firmware update via the USB cable to the phone, so technically you are using Odin. You wouldn't really notice Odin was being used during the flash unless you look carefully at the small dialog in the upper left corner of the s3 screen during the update.
hi, what im trying to do is use odin to install root66 jb rom but before i do that i am running aokp 4.1.2 . do i first need to wipe phone before i use odin to flash rom or is it ok to just go head and install with odin? what i mean by wipeing phone is to wipe data /factory reset wipe cash wipe dav format system and what ever else there is in cwm to do. im just not sure havent done this before so some help would great.. thanks
ralphie1267 said:
hi, what im trying to do is use odin to install root66 jb rom but before i do that i am running aokp 4.1.2 . do i first need to wipe phone before i use odin to flash rom or is it ok to just go head and install with odin? what i mean by wipeing phone is to wipe data /factory reset wipe cash wipe dav format system and what ever else there is in cwm to do. im just not sure havent done this before so some help would great.. thanks
Click to expand...
Click to collapse
You'll need to do that wipe sooner or later (otherwise the stock ROM will fail to boot); you can either do it now or wait until after you've done the flash and use the stock recovery to do the wipe. I'd consider doing the wipe first to be easier.
Actually what I'm having issues with is Kies itself. I used a separate computer so that I could download Kies new but it's also a problem. Is there an easier way?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
GrapePopRocks said:
Actually what I'm having issues with is Kies itself. I used a separate computer so that I could download Kies new but it's also a problem. Is there an easier way?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Are you using the kies version from the support page on Samsung.com for YOUR phone? If you're trying to use kies instead of a mini version for a US phone, that hasn't worked for any of the other Galaxy line phones (at least in my experience).
Sent from my SGH-I747 using xda app-developers app
I don't know if this qualifies as easier (it would for me), but if Kies isn't working for you for whatever reason, you might try just using Odin directly. You can get Odin itself over in this thread, and completely stock images over in this thread; if you want the latest AT&T build, that would be this one.
(If you're slightly more ambitious, you could also try the rooted-but-otherwise-stock images found here, as a gateway to future customisation, but that's entirely up to you...)
Yes it's Kies from the support page. I will try with Odin directly see how that goes. If not I will be back LOL
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
To put it kindly, Kies is a steaming pile of cr4p. To be honest, upgrading via Odin with the official ROM is the best way to go. I spent days trying to get my phone to connect to Kies and it was a mess. I went to the AT&T store and they told me that there wasn't anything that they can do, this is an open issue. It works for some people, not others.
Finally I downloaded Kies on my wife's Mac and it worked. So maybe try a Mac?
My sister has a Mac I will try that
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Related
Hello,
Let me start off by saying if this is the wrong place to post this please inform me of the right forum.
I just recently got a Samsung Galaxy SIII (on August 29) and everything was working really well, until today. Yes it is rooted. I plugged the phone into my computer and Kies said there was a firmware update for my phone. I began doing the upgrade and my beloved windows computer got the blue screen of death during the actual update process.
After restarting my computer, I began to do the update recovery to continue with my upgrade. Same blue screen. I spoke to a rogers tech rep and he requested I re-install my Kies software, which I did. Upon having no success from that I began to do more research, however most of them are saying to reflash the stock firmware (which I have) using ODIN. I have no success here as well. Every time i do get into download/recovery mode, ODIN recognizes my phone, but fails when i click start.
In my recovery mode the information i see is as follows:
ODIN MODE
PRODUCT NAME: SGH-1747M
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOM SECUREBOOT: ENABLE
Is there anything at all I can do to fix this? Or am I one of those most unfortunate people who just got screwed lol.
ANY assistance is VERY MUCH appreciated!
Thanks in advance
If you have clockwork recovery, try formatting the system first then flash the ROM. Just dont reboot without flashing the ROM first.
Have you tried the emergency firmware load through KIES?
Sent from my SGH-I747M using xda app-developers app
cue_32 said:
If you have clockwork recovery, try formatting the system first then flash the ROM. Just dont reboot without flashing the ROM first.
Have you tried the emergency firmware load through KIES?
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
thank you for the quick reply! sorry for my late one, just got home from a family emergency...
no I don't have CWM.. I'm very familiar with it though I didn't put it on my SIII (i was planning to do so tonight)
I've tried the emergency firmware, however it asked for a code which I don't have :S
I'm new to Samsung's version of Android, previously I owned an Xperia X10
Try running Odin on a different computer
If you're using a desktop use the usb ports on the back Odin don't like the usb hub on front, or try different computers, I have one computer that Odin will never work on but I go right to my other one and works fine, try restarting pc or uninstall Odin and download a different version, also try downloading a few different roms try these below, I've been in that position then finally after trying and trying a Rom will finally take
http://forum.xda-developers.com/showthread.php?t=1739426
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
rob1216 said:
If you're using a desktop use the usb ports on the back Odin don't like the usb hub on front, or try different computers, I have one computer that Odin will never work on but I go right to my other one and works fine, try restarting pc or uninstall Odin and download a different version, also try downloading a few different roms try these below, I've been in that position then finally after trying and trying a Rom will finally take
http://forum.xda-developers.com/showthread.php?t=1739426
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
that worked!!!!!!!!! thank you, i just changed the USB port lol.. its always something so simple you wouldn't think to do it initially!
thanks so much!
I'm having an issue with my t989 that has persisted since I stopped using Kang's ROMs and the Bullet Kernel.
After going from the Juggernaut ROM to Darkside's ICS when it came out, my phone started to not be recognized by any computer, be it OSX or Windows. I've tried everything on the PC software side, from clearing Kies and the Samsung Drivers, as well as clearing registry information and re-installing both separately, and this has not helped at all. The windows error is:
Windows has stopped this device because it has reported problems. (Code 43)
I don't use antivirus, and I don't use a firewall, suffice to say I'm a programmer and have plenty of experience in doodling with phones, and I'm stumped. I've come to the conclusion that the Bullet Kernel installed from my Juggernaut days is the cause of the issue, as I repeated the process on a friend's device and he has the exact same symptoms.
With this situation, I'm not able to access ODIN to return to complete stock, so I can't flash over the Bullet Kernel. Alongside the USB device not recognized problem, I also was not able to get into ODIN / download mode until I made my own USB Jig to get around it.
Is there any way to get back to the stock kernel without ODIN? Would Mobile Odin Pro work if Chainfire added support for our device? It's really pissing me off as I'm a software developer and can't use my own device to build to.
EDIT: As a note, when moving from Juggernaut / Bullet to Darkside, I flashed the appropriate ICS radio and kernel, but when returning to 2.3.5 stock from Samsung, somehow the Bullet kernel managed to persist.
edit: nvm you answered my question.
Im not aware of a way to unroot without Odin Can you get into recovery?
Hey, not sure if this will help, but there's links to flashable stock zips in this thread:
http://forum.xda-developers.com/showthread.php?t=1869082
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
blackangst said:
edit: nvm you answered my question.
Im not aware of a way to unroot without Odin Can you get into recovery?
Click to expand...
Click to collapse
There is still a way to get back to the Stock ROM ( 2.3.5 ) and Recovery, but the kernel flash was not included with the package:
http://galaxys2root.com/t-mobile-galaxy-s2/how-to-unroot-t-mobile-galaxy-s2-sgh-t989/
This is apparently the "Zedomax" unroot that does not need the ability to hook up to Odin, so needless to say, it's not unrooting that I need, it's getting back to the stock kernel that is the problem.
Obviously now that I'm unrooted, there really isn't a way for me to install Mobile Odin Pro even if I had it. I've been looking how to contact him to request it, because I don't want to be rude and PM him the request when I'm sure that's not the way that respected XDA members would want.
Can I ask why you think the kernel alone isn't being overwritten? That seems odd to me, since every ROM packs its own kernel, and flashing a kernel specifically only replaces the kernel. So if you flash an ICS ROM you're getting an ICS kernel, GB you get a GB kernel, etc. It wouldn't work otherwise. If you haven't done it already, you might want to try Darkside super and cache wipes.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
RTFOP said:
Can I ask why you think the kernel alone isn't being overwritten? That seems odd to me, since every ROM packs its own kernel, and flashing a kernel specifically only replaces the kernel. So if you flash an ICS ROM you're getting an ICS kernel, GB you get a GB kernel, etc. It wouldn't work otherwise. If you haven't done it already, you might want to try Darkside super and cache wipes.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Well, for one, I get a Bullet loading screen... Apparently reading through other threads, it's a known issue that Zedomax's Stock ROM method doesn't include the kernel, which basically means I may have f'ed myself permanently seeing as how I can't get ODIN access. Unfortunately, galaxys2root.com didn't tell people on their site that it didn't include the kernel, so needless to say, I'm never going to that site again and I would advise people not to follow any of their stuff either.
Although it's a small omission, their lack of providing information has just caused me to possibly lose a moddable phone.
EDIT: the threads that I've been reading through are the ones you supplied, RTFOP
So can you not get into download mode or get your computer to recognize your phone in recovery? If you're willing to tinker some you can back track and root and reinstall and overwrite that kernel and then circle back.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
RTFOP said:
So can you not get into download mode or get your computer to recognize your phone in recovery? If you're willing to tinker some you can back track and root and reinstall and overwrite that kernel and then circle back.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Well, to re-hash over what I've said already for clarification's sake:
1. I can get into download / ODIN mode
2. I still CANNOT get my phone to recognize in recovery. I know it's not my PCs, it's the phone, and I suspect the Bullet Kernel as it was not reverted back to the stock kernel when I flash Zedomax.
With that said, I don't see how it's possible for me to root and get CWM seeing as how I'm on stock Recovery (3e), and I can't ODIN. Unless there is a untethered way to root the t989, I think i'm up ****'s creek.
At what point did you lose root access though?
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
RTFOP said:
At what point did you lose root access though?
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
The whole point of flashing Zedomax's .zip is to unroot and go back to stock Samsung 2.3.5.
Just to verify, I downloaded root checker and it states I do not have root access.
So if you can get into Odin with your jig workaround, why can't you load a custom recovery and super user and then run Darkside wipes and install whatever ROM you want?
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
RTFOP said:
So if you can get into Odin with your jig workaround, why can't you load a custom recovery and super user and then run Darkside wipes and install whatever ROM you want?
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
I think there's a fundamental misunderstanding between you and I. When I say I can get into download / Odin MODE, that means I can force the phone itself into ODIN Mode, but since my computer does not recognize my t989, the ODIN application on my windows box does not recognize the phone, and the ID box does not 'turn yellow' as it should if my phone were recognized by my PC.
So even though my phone is waiting for the ODIN application on my windows to send it commands, I can't send it commands because the application won't recognize the phone.
Thus is my quandary.
Yeah, sorry, I didn't get that. Have you tried plugging it in without the sd card in? It's kind of a long shot, but errors on there might be keeping your computer from communicating with the device, since it seems to be working otherwise. Maybe the jtag repair service through mobile tech videos?
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
RTFOP said:
Yeah, sorry, I didn't get that. Have you tried plugging it in without the sd card in? It's kind of a long shot, but errors on there might be keeping your computer from communicating with the device, since it seems to be working otherwise. Maybe the jtag repair service through mobile tech videos?
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
As you suggested, I tried taking out the SD card and that didn't help.
I'm trying to do as much as possible before I try and repair it. I may consider trying for a warranty replacement and take the risk, but I'd like to try everything I can before I take that step, I don't like not being able to fix something =p.
Thanks for the help btw.
IM sorry all you are passing through , I couldn't use my phone for two week when I messed up, . Well let's try get root with this apps
http://forum.xda-developers.com/showthread.php?t=833953
If the permanent root doesn't work try the temporary
Sent from my SGH-T989 using xda app-developers app
I bought a T-Mobile Galaxy S 3 LTE with model number SGH-T999L. I used Odin V3 1.85 to flash TWRP recovery and CyanogenMod 10.0.0.
Everything went well but my camera doesn't work. On launching the camera, I get a "Can't connect to camera" error and it quits. The same behavior is observed when using other camera apps. I tried the instructions in this thread(http://forum.xda-developers.com/showthread.php?t=2239414) but it did not fix my problem. I now want to go back to my stock ROM. I successfully downloaded and flashed stock recovery using Odin. However, Odin fails when I try to flash the stock ROM obtained from the samsung website. It gives me a "write failed" error and stops. Any tips or suggestions to help me out would be appreciated. Thanks
Is it supposed to use T999 firmware?
Only odin flash T999L firmware. I dont see it released yet at samsing-updates.com though.
Maybe samfirmware.com? I can look later.
Sent from my SGH-T999 using xda premium
re: sure fix
newidforu said:
I bought a T-Mobile Galaxy S 3 LTE with model number SGH-T999L. I used Odin V3 1.85 to flash TWRP recovery and CyanogenMod 10.0.0.
Everything went well but my camera doesn't work. On launching the camera, I get a "Can't connect to camera" error and it quits. The same behavior is observed when using other camera apps. I tried the instructions in this thread(http://forum.xda-developers.com/showthread.php?t=2239414) but it did not fix my problem. I now want to go back to my stock ROM. I successfully downloaded and flashed stock recovery using Odin. However, Odin fails when I try to flash the stock ROM obtained from the samsung website. It gives me a "write failed" error and stops. Any tips or suggestions to help me out would be appreciated. Thanks
Click to expand...
Click to collapse
Why not reflash the stock ODIN flash rom and make sure it all works ok for you, that will tell you exactly what the problem is.
If the stock rom is working properly, then there is only one thing left which is the culprit and that is the CM10/AOKP/AOSP
or PORTED roms which many people seem to like flashing.
The CM10/AOKP/AOSP and ported roms are excellent if you are a developer or if you like to do a lot of experimentation with your phone.
So the thing to do now is reboot your phone to recovery mode, do a "Factory Reset", "Wipe Cache", "Wipe System" and "Wipe Dalvik".
When that's done Open Odin and put the stock rooted T999 Tmobile Jellybean 4.1.2 into Odin's PDA slot, go into download mode
and once you see Odin is connected to the phone start the flash. Have patience for the phone to boot after its done flashing.
Here is the stock rooted Odin flash T999 Tmobile Jellybean 4.1.2 rom that you can download if you like: T999_UVDMD5
Official JB Firmware - Latest JB 4.1.2 Firmware
My suggestion to you is to only flash Samsung T999 Tmobile stock based Jellybean 4.1.1 or 4.1.2 roms in the future.
But who am I to say whats best..... This is just my personal opinion...... Which usually is not worth a dime. LOL
Sorry, but untill we know more about it, I would not flash T999 firmware onto the T999L.
Its only been out a day and tgey are different model phones with different hardware.
If you decide to try anyway, please post your results
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Sorry, but untill we know more about it, I would not flash T999 firmware onto the T999L.
Its only been out a day and tgey are different model phones with different hardware.
If you decide to try anyway, please post your results
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I am a newbie. I thought the T999 was the same as the T999L. That would explain why Odin doesnt flash stock T999 onto my device. Can anyone here post a link to the stock SGH-T999L ROM?
Just did a quick check and I dont see that the firmware has been made available for download yet.
If you want stock I would flash one of the stock based custom roms via recovery for now.
Out of curiosity, what is your current baseband version?
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Just did a quick check and I dont see that the firmware has been made available for download yet.
If you want stock I would flash one of the stock based custom roms via recovery for now.
Out of curiosity, what is your current baseband version?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Baseband version is T999LUVAMB7. Still waiting for stock ROM to be released on samsung-updates or sammobile.
newidforu said:
Baseband version is T999LUVAMB7. Still waiting for stock ROM to be released on samsung-updates or sammobile.
Click to expand...
Click to collapse
I had the same issue with the same phone. Got it 2 weeks ago haha. Did you happen to make a backup first using CWM Recovery? If so, you can just restore that backup and you'll have your camera functionality back. It's pretty annoying switching back and forth from CM10.1 back to stock just to take pictures but Rom manager makes it pretty quick and effortless.
Actually now that I think of it, they prob wont release the original firmware. Seems like the first build is never available, only when an update is released do we get firmware we csn download.
I am working with another member on getting something going for the T999L, but right now we are stuck until a verified safe method of rooting is found. (Dont want to flash a recovery or cf autoroot w/o knowing it wont screw something up)
Itll happen, but we just gotta be patient.
Just reread the op and see that you say you flashed TWRP. So you were able to initially gain root without any problems?
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Actually now that I think of it, they prob wont release the original firmware. Seems like the first build is never available, only when an update is released do we get firmware we csn download.
I am working with another member on getting something going for the T999L, but right now we are stuck until a verified safe method of rooting is found. (Dont want to flash a recovery or cf autoroot w/o knowing it wont screw something up)
Itll happen, but we just gotta be patient.
Just reread the op and see that you say you flashed TWRP. So you were able to initially gain root without any problems?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I used Odin to flash Clockwork Mod recovery first. I did not like Clockwork Mod's interface and reflashed with TWRP. I had no problems to gain root with either of these methods. I also tried Cyanogenmod stable 10.0.0 and then 10.1 RC2 without any problems. As far as I can tell, all apps work except for the camera. One word of caution though. As you can see from my posts, I am new and dont know what I am doing. I might have just gotten lucky since my device is still unbricked. I had only one "scary" moment during the entire process. I used TWRP to wipe my phone clean and was stuck with no OS install file. ADB sideload did not work since it could not recognize the device at that point. Luckily, I had a micro SD card lying around and was able to put in a new OS install file using my laptop and then TWRP was able to handle it.
tsticge aye
faytx1 said:
I had the same issue with the same phone. Got it 2 weeks ago haha. Did you happen to make a backup first using CWM Recovery? If so, you can just restore that backup and you'll have your camera functionality back. It's pretty annoying switching back and forth from CM10.1 back to stock just to take pictures but Rom manager makes it pretty quick and effortless.
Click to expand...
Click to collapse
Wish I had made a backup! Could you zip up the files contained inside "/system/cameradata/" folder and post a link here? It would help me and anyone else with the same problem restore the camera's functionality. In case you want to try it out, follow the instructions in this link but using the files from your stock backup
http://forum.xda-developers.com/showthread.php?t=2239414
newidforu said:
Wish I had made a backup! Could you zip up the files contained inside "/system/cameradata/" folder and post a link here? It would help me and anyone else with the same problem restore the camera's functionality. In case you want to try it out, follow the instructions in this link but using the files from your stock backup
http://forum.xda-developers.com/showthread.php?t=2239414
Click to expand...
Click to collapse
Here is the cameradata folder from the T999L.
http://d-h.st/Ciy
Good Luck!
How did you get Cyanogenmod installed on the t999l every time i try it aborts with status 7
Mine was failing with this same error. I reverted back to stock, re rooted, then downloaded the flash directly to the phones internal storage. Worked like a champ. I think in my case, there is an issue with the SD card, its kind of old.
Sent from my SGH-T999 using xda app-developers app
Beefstew said:
Mine was failing with this same error. I reverted back to stock, re rooted, then downloaded the flash directly to the phones internal storage. Worked like a champ. I think in my case, there is an issue with the SD card, its kind of old.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
You reverted to stock on the T999L? please exspain how that was done
Re flashed stock ROM using Odin. I believe I got the file from Samsung's website, but I'm not positive of that. I do know its huge, over 1 gig. If you need help with the re flash I know there are already how to's on here about that, so I won't go into it here.
Sent from my SGH-T999 using xda app-developers app
You must be using a T999 as your sig indicates, not a T999L. Am I correct?
Sent from my SGH-T999 using xda premium
Don't I feel like a tool now. Yes Doc, plain old t999 here. Now that I read back through the whole thread here I see that I was being a bit redundant. Now I will return to my closet under the stairs.
Sent from my SGH-T999 using xda app-developers app
No worries! We all do stuff like that from time to time!
Sent from my SGH-T999 using xda premium
In serious need of your help here guys. I bricked my T-mo SGH-M919 today trying to root. Now I can't flash the stock recovery thru Odin. Tried a zillion times, uninstalled and reinstalled drivers restarted my comp, done everything I could think of still no dice.
I keep getting this Fail message in Odin saying " There is no PIT partition" tried to search for a PIT file for my specific model but couldn't find any. I even tried recovery thru kies emergency recovery and failed at the last step. Anybody can help me please.
NYCguy2020 said:
In serious need of your help here guys. I bricked my T-mo SGH-M919 today trying to root. Now I can't flash the stock recovery thru Odin. Tried a zillion times, uninstalled and reinstalled drivers restarted my comp, done everything I could think of still no dice.
I keep getting this Fail message in Odin saying " There is no PIT partition" tried to search for a PIT file for my specific model but couldn't find any. I even tried recovery thru kies emergency recovery and failed at the last step. Anybody can help me please.
Click to expand...
Click to collapse
If you can still get into Odin mode, there's still hope. Have you tried using Odin to flash a stock image instead of Kies?
NYCguy2020 said:
In serious need of your help here guys. I bricked my T-mo SGH-M919 today trying to root. Now I can't flash the stock recovery thru Odin. Tried a zillion times, uninstalled and reinstalled drivers restarted my comp, done everything I could think of still no dice.
Dont use Pit thats why Use pda
I keep getting this Fail message in Odin saying " There is no PIT partition" tried to search for a PIT file for my specific model but couldn't find any. I even tried recovery thru kies emergency recovery and failed at the last step. Anybody can help me please.
Click to expand...
Click to collapse
Don't use and dont need pit file.
Find the stock shipped tar file (aka) 4.1.2 Rom
Load in pda leave everything checkedbin odin thats checked.
Rooting isnt hard at all just got my s4 3 hrs ago rooted in 5 minutes soon as I walked in the door.
You need the Root_m919uvuamdl.zip
And then flash MDB setUIDoff .zip
Then flash superuser.
Thats it.
If u have odin Booted its 1000% NOT BRICKED
Sent from my SGH-M919 using xda app-developers app
lojak29 said:
Don't use and dont need pit file.
Find the stock shipped tar file (aka) 4.1.2 Rom
Load in pda leave everything checkedbin odin thats checked.
Rooting isnt hard at all just got my s4 3 hrs ago rooted in 5 minutes soon as I walked in the door.
You need the Root_m919uvuamdl.zip
And then flash MDB setUIDoff .zip
Then flash superuser.
Thats it.
If u have odin Booted its 1000% NOT BRICKED
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Had that and tried flashing it thru Odin several times and I keep getting the same error message. "there is no PIT partition"
Let me ask you one thing. .. is the com port in odin coming up recognize the phone ...if so you are not bricked. . The two vital things u need to see is com port turn on usually blue color and download mode..
The problem def lies somewhere else possibly bad tar file .
Try to find another source for the stock rom tar file another option is boot into recovery and flash a stock rom if you have recovery still
Sent from my SGH-M919 using xda app-developers app
Change cable, change PC, download latest Odin version, and reflash stock TMO ROM
Yes cable and USB port can affect Odin's ability to flash
Sent from my Nexus 7 using Tapatalk 4
Gunkk said:
Yes cable and USB port can affect Odin's ability to flash
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Thanks guys. Finally got it resolved. Rooted and rocking Wicked V5.1
Id at least like to know what resolved it and if anyones opinion? We told ya it wasnt bricked. ..
Bricked is No pc to usb recognition and or phone wont boot into anything ..Black screen of death
Sent from my SGH-M919 using xda app-developers app
I bet he changed USB port or cable.
extrem0 said:
I bet he changed USB port or cable.
Click to expand...
Click to collapse
Uninstalled and reinstalled drivers and Odin, rebooted my comp and used the Sammy USB cable.
Well glad you got it.... but i still find it hard to believe any usb was the issue Usb recognition is usb recognition. .if odin seen the phone usb was working. ..its literally that simple... the problem initially explained was that the pit error was coming up... that all relates usually to a file error .
But glad it worked out and u didnt loose a 600$ phone.
Sent from my SGH-M919 using xda app-developers app
When I read this post, my stomach felt like it felt the first time I almost bricked my brand new s2 when it first came out, glad you got it to work
lojak29 said:
Well glad you got it.... but i still find it hard to believe any usb was the issue Usb recognition is usb recognition. .if odin seen the phone usb was working. ..its literally that simple... the problem initially explained was that the pit error was coming up... that all relates usually to a file error .
But glad it worked out and u didnt loose a 600$ phone.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
I own three Samsung devices, and my sgs2 will not transfer files or work with adb when I use a generic best buy rocketfish usb cable. The original Samsung cable works every time.
Sent from my Xiaomi MI2S
I have seen that a lot.
I actually bought a few spare Samsung ones from eBay to make sure I would always have a good cable.
Sent from my SGH-T999 using XDA Premium 4 mobile app
Well... one case to the next is different. .. ive never had issue using a lg cord moto cord or htc on a samsung device. .
I just think that the op post if you read his initial problem and how it was stated i think it had to do with trying to odin in the pit section instead of pda.
Ive seen this issue before.
Once again glad its fixed
Sent from my SGH-M919 using xda app-developers app
Nope, it was in the PDA section. I'm familiar with Odin and used it several time in the past (on my Note 8.0) . I believe the error message was either due to corrupt download and/or the USB cable. Anyway so glad it was solved quickly and thanks again for your help.
NYCguy2020 said:
Nope, it was in the PDA section. I'm familiar with Odin and used it several time in the past (on my Note 8.0) . I believe the error message was either due to corrupt download and/or the USB cable. Anyway so glad it was solved quickly and thanks again for your help.
Click to expand...
Click to collapse
+1 for the corrupt dload.
:thumbdown:Usb not likely since Odin seen the phone ill leave it at that.
Sent from my SGH-M919 using xda app-developers app
lojak29 said:
+1 for the corrupt dload.
:thumbdown:Usb not likely since Odin seen the phone ill leave it at that.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Pit file. That solved my problems. Flash it alone, then flash a good stock rom.
Hi Everyone, I actually have a SGH-I317m (Rogers Note 2), but thought I would post here since this gets more traffic.
I have been having constant problems with Odin trying to flash files to my Note 2.
Currently using the factory Samsung USB cable, disconnecting any other USB devices connected (BT gamepad) to my computer, and being sure to run Odin as "Administrator" in Windows 7 (64bit).
I've used the recommended Odin 1.85 as well as the latest Odin 3.x, with the newest release being somewhat more reliable.
Basically I've grown too paranoid to try and flash custom roms, and even the root package to my phone in fear of a permanent soft brick. KIES failed to update my phone to stock 4.3, so I then used Odin to flash it. I recently tried to flash a root package, which failed every time, then my stock image, which failed about 14 out of 15 tries. Once the Stock ROM flashed successfully, I breathed a sigh of relief and gave up.
Is there something specific that could be causing Odin to fail so consistantly? My phone is stock 4.3,recovery, unrooted, with locked bootloader and SIM.
I've seen recommendations that a Factory Reset be performed after flashing a new ROM, which I have not done. What is the logic behind this?
I'd be willing to try, but without root (aka without Titanium BackUp) a Wipe is not ideal. That being said, if I put all these flashing issues behind me, I'd happily give it a try.
I am curious to try Mobile Odin as well, which of course requires root.
The fact that both Odin and Kies failed to flash my device is curious. I'd like some suggestions on how to proceed.
I'd be happy not flashing custom ROMs, however I do feel that root access is a requirement for my usage.
Anyone?
Sent from my SGH-I317M using xda app-developers app
what root package did you use?
The one found in http://forum.xda-developers.com/showthread.php?t=2004650this thread, which is for my device.
Sent from my SGH-I317M using xda app-developers app
search for newest samsung mobile usb driver... make sure its the latest one and download it
uninstall the good for nothing kies software... reboot your pc and install the samsung mobile usb driver.
then connect your device and let windows reinstall the driver....
then try odin again.
Thanks. I ditched Kies once it failed to flash my device, then failed to recover it.
I will try reinstalling the driver. The one I have installed likely came from the "Galaxy Note 2 Toolkit", which hasn't been updated awhile.
I will try and report back.
Sent from my SGH-I317M using xda app-developers app
Interesting. Samsung's Canadian site does not have USB drivers, and the US version doesn't include my model... I will keep digging.
Sent from my SGH-I317M using xda app-developers app
Ok, I've resolved my issues and will post here for others should they have the same. My issue was caused by usb drivers. Uninstall Kies, and any Samsung drivers you may have installed. Reboot your pc, and install the latest Samsung drivers from here, for your device.
http://m.samsung.com/us/support/owners/product/SGH-I317TSAATT
After, plug in your phone, and let Windows install what it needs. Then proceed with Odin as normal.
Thanks to everyone for their help.
Sent from my SGH-I317M using xda app-developers app