[Solved] Rooting error (Odin) - AT&T Samsung Galaxy Note I717

Hello, First off i am fairly new to Odin and kernels as on my actual device is a HOX (The note is my mothers). I have been trying to flash the pda.tar from http://forum.xda-developers.com/showthread.php?t=1504218 and am just getting the following error.
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
?
NAND Write Start!!
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
I have also gotten ahold of the other pda.tar folder from galaxynoteroot.com (Or somthing like that) and it did succeed but i did not gain root. Any help is appreciated :thumbup:. This is a Telus Galaxy note (I171D) on GB.

Driver issue ???
PC antivirus issue ???
Odin copy could have an issue also ...
First ....kill the antivirus program when using Odin.
Then use a powered rear port for USB ...
And the factory cable ...
P.S.
Cable issues are common ...g

gregsarg said:
Driver issue ???
PC antivirus issue ???
Odin copy could have an issue also ...
First ....kill the antivirus program when using Odin.
Then use a powered rear port for USB ...
And the factory cable ...
P.S.
Cable issues are common ...g
Click to expand...
Click to collapse
Well I don't have anti virus in here and the drivers are installed. As for factory cable, it's a couple thousand miles away as I'm on vacation so I'm just using another line for my HOX. Also this is a mac book with windows installed (also not mine).
Sent from my HTC One XL using xda premium

Ah ...
I see 2 issues ...
The mac pc/Odin conflict ....(not always, but some odin errors exist )
Not using the factory cable ....( this is pretty much a requirement )
Dang it ....you may be hosed without that cable.
Do you have any available electronics outlets ?
If so ....a gold plated USB cable may solve the problem. But the PC environment is semi adequate ...and the cable may not help anyway .
My emergency suggestion, is to download the needed files again, and attempt a reflash.
This go around ...place the .tar files to desktop only, Odin also.
Then run Odin as administrator only.
The readout you gave shows a possible error with Odin locating the .tar from the directory , and I'm trying to side step that condition. At this point I don't know about the cable ...it's just too vague to be sure.
I'm sorry you are having trouble ...and I really am trying to solve this for you ....g

gregsarg said:
Ah ...
I see 2 issues ...
The mac pc/Odin conflict ....(not always, but some odin errors exist )
Not using the factory cable ....( this is pretty much a requirement )
Dang it ....you may be hosed without that cable.
Do you have any available electronics outlets ?
If so ....a gold plated USB cable may solve the problem. But the PC environment is semi adequate ...and the cable may not help anyway .
My emergency suggestion, is to download the needed files again, and attempt a reflash.
This go around ...place the .tar files to desktop only, Odin also.
Then run Odin as administrator only.
The readout you gave shows a possible error with Odin locating the .tar from the directory , and I'm trying to side step that condition. At this point I don't know about the cable ...it's just too vague to be sure.
I'm sorry you are having trouble ...and I really am trying to solve this for you ....g
Click to expand...
Click to collapse
Well good news My aunt has a GS3 which basicly uses the exact same cables as the Note. As for the .tar folder I will try your suggestions tommrow with my sisters mac (Currently on the the other side of the world). I might just be able to visit a Internet cafe but then administrator permissions will be a pain to get... Well thanks for helping, I will report back tommrow/tonight
Sent from my HTC One XL using xda premium

Talk to ya then....g

I don't see why the factory cable thing matters, I use other cables all the time and have never had a problem, just use a real windows machine and not a parallel and you should be fine

Its not that it has to be the factory cable, but when people are having unexplained errors you use known good cables and it eliminates things as you troubleshoot. If everything works, good. If problems, eliminate a typical problem causer, like the cable or the usb port, etc.
Not all usb cables are charging cables but you can't tell by just looking at it.

Yeah I can see that, I would just think almost any cable would work (even those $1 ebay ones work for me), the Windows parallel is the big red flag here though if you had to isolate an issue.

Alas all your tips didn't work... And now I have the gapps error so I'm now urgently looking to somehow get root or a recovery in. Also rangercaptain seems Korean Starbuck doesn't have free wifi....
Sent from my HTC One XL using xda premium

TheNightHawk223 said:
Alas all your tips didn't work... And now I have the gapps error so I'm now urgently looking to somehow get root or a recovery in. Also rangercaptain seems Korean Starbuck doesn't have free wifi....
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Okay,
please tell us your current device state:
do you have a stock recovery ?
do you have a working rom ?
We need to know where your device is, with respect to software as of today.
And if in your location, I would revert to stock until you get to a location with proper connections, wifi, etc.
If we can get you that far...
We need to flash a stock odin .tar file if possible, to get you running again...IMHO

TheNightHawk223 said:
Alas all your tips didn't work... And now I have the gapps error so I'm now urgently looking to somehow get root or a recovery in. Also rangercaptain seems Korean Starbuck doesn't have free wifi....
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Ok you're in the ROK. Who would have guessed that? What model of phone? There is a Korean, international, and North American model.

rangercaptain said:
Ok you're in the ROK. Who would have guessed that? What model of phone? There is a Korean, international, and North American model.
Click to expand...
Click to collapse
Oh I have the American model, only here on vacation, actually live at Canada.
Sent from my HTC One XL using xda premium

gregsarg said:
Okay,
please tell us your current device state:
do you have a stock recovery ?
do you have a working rom ?
We need to know where your device is, with respect to software as of today.
And if in your location, I would revert to stock until you get to a location with proper connections, wifi, etc.
If we can get you that far...
We need to flash a stock odin .tar file if possible, to get you running again...IMHO
Click to expand...
Click to collapse
Okay, I am stock on the telus RUU, I'm almost sure that I have stock recovery but as I had tried flashing cwm I'm not sure and don't know how to get into recovery (First Sammy I played with) with this phone I cannot be sure. I am on Telus gb stock.
Sent from my HTC One XL using xda premium

If your phone is working, and you cannot get a good PC environment to use, then wait until you get home, and we can continue.
Recovery is gained by powering off the device, ( no cable attached) and pressing the volume up, and down buttons together, and then pressing the power button. Once you feel a single vibration, then release the power button while holding the volume buttons until the recovery screen appears.
If you verify your recovery is stock, then we should wait...IMHO (it will say 3e recovery if stock)
If the flash of CWM is a success, then we can proceed...g

gregsarg said:
If your phone is working, and you cannot get a good PC environment to use, then wait until you get home, and we can continue.
Recovery is gained by powering off the device, ( no cable attached) and pressing the volume up, and down buttons together, and then pressing the power button. Once you feel a single vibration, then release the power button while holding the volume buttons until the recovery screen appears.
If you verify your recovery is stock, then we should wait...IMHO (it will say 3e recovery if stock)
If the flash of CWM is a success, then we can proceed...g
Click to expand...
Click to collapse
Soo sorry for wasting your time... I realized that the recovery did flash and it was my idiacy that i did not figure out how to get into fastboot/recovery with this phone... Thank you very much for your time!

Dont sweat it...
you didnt waste my time...
I'd rather spend the time up front, to avoid the potential of creating a brick later on.
If you need more help, just ask.....g
P.S.
If you are good at this point, please place the word "SOLVED" in the title of your thread.
It will steer users to the solution faster, and helps keep the threads clean.
Thank you....g

Related

[Solved] Help reverting to stock rom?

I am using the UCKH7 one click w/root tool.
I start download mode by holding volume up and down while plugging in USB. I click the start button but the program hangs at 'factoryfs.img'
Please help. Thanks.
AT&T galaxy s2
Deenybird said:
I am using the UCKH7 one click w/root tool.
I start download mode by holding volume up and down while plugging in USB. I click the start button but the program hangs at 'factoryfs.img'
Please help. Thanks.
AT&T galaxy s2
Click to expand...
Click to collapse
I use heimdall personally. Never had any problems with it. Do you have all the sgs2 drivers installed?
Also check md5 sums to make sure your download is ok.
Sent from my SGH-I777
I'll try heimdall. Drivers should be fine as kies is installed. Rom should be good as I've tried 2 different download sources
Make sure you install the libusb drivers for heimdall before flashing. The instructions are in the heimdall readme. Good luck
Sent from my SGH-I777
Just wanted to post that my problem is solved.
Summary: My AT&T Galaxy SII showed an error on boot (software upgrade failed. connect to kies...). Kies wouldn't even recognize the device so that route was a no go. So as everyone's recommended method of last resort, I decided to flash the device back to stock via odin. I entered download mode (volume up + volume down and plug in usb) and Odin would recognize the device, I would load the stock rom in the PDA slot and hit start and it would begin normally, but it would always fail after a few seconds on 'NAND write start', or 'factoryfs.img'. So I got a 1 click download solution using odin for reverting my phone back to stock. Same thing, it would recognize the phone, but stall out and fail. I also tried flashing clockworkmod via odin but and same problem. People recommended I try heimdall. It would recognize my device, and then fail after 'kernel 100%'.
I tried both programs on 3 different computers, and must have tried 12 different USB slots amongst all of them. I'm fairly handy with this stuff and I worked for hours on it.
xtra info: I had successfully used odin on my computer to flash a kernel just a week ago so I know my stock usb cable was working etc...
Resolution: So I hung my head and drove to the ATT store. After pressing a few buttons on the device and not getting anywhere they sent me to a nearby Device Support Center. I told the girl at the counter that my phone booted to this error screen and that connecting it to Kies did nothing. She asked if it was ok that in the case that she couldn't fix it she would offer me a replacement. I said that was fine and after 10 minutes in the back room she came out with a replacement (free of charge).
Well that was the good news. For the bad news, unfortunately I still don't know how to fix the problem I had, and don't really know how to avoid it in the future. I thought phone's could only get truly bricked if you messed with PIT files and such. There didn't seem to be anything more I could do than flash with odin or heimdall as those were already last resorts. I know I had the right files, the right drivers, and working usb. No matter how crazy I got with my iphone, a full restore was only a click away by plugging in to iTunes. Somehow I messed up my phone so bad that even the device support center couldn't fix it....? Shouldn't have had to be like that.
Thank yous: Thanks to ATT for having a walk-in store and for so easily offering up a replacement. Thanks to the many people on the web who offered remedies.
tl;dr - phone broke, att replaced, still a mystery

[GUIDE][REF]Basic Trouble Shooting Steps for ODIN FAILURE

So, you've been flashing stuff and now for whatever reason, your phone won't boot.
Now you're trying to save your poor phone's life with Odin but odin keeps failing.
Here are a few basic steps to go over to try and get Odin to cooperate:
First things First, if the device shows no signs of life whatsoever, you press the power button and it just sits there blank,
i am sorry to inform you, you are bricked and at a point beyond the help of odin. this will require JTAG to fix.
if you are in a bootloop or the phone freezes at some point of the boot sequence, this is what odin can fix.
if you do not have odin, get it HERE
here are the USB DRIVERS
i will not provide links to stock firmwares to use, those are ALL OVER the forum,
this is to help get those flashed not to completely hold your hand
only thing i'll add about which to use is:
DO NOT USE A PACKAGE CONTAINING BOOTLOADERS
IF ODIN FAILS DURING THE WRITING OF A BOOTLOADER THAT WILL BRICK THE DEVICE
STEPS:
Use USB ports connected to MOTHERBOARDno front panel ports, hubs etc...
Use a Known good usb data cable preferably OEM, you may want to have 1 or more spare just in case
right click odin and run as administrator
Have odin ready to go before you touch your phoneAll files in the proper place, now boot to DL mode and connect
If this is still Failing try:
Exiti Odin
Uninstall USB drivers
Reboot PC
Reinstall USB drivers
Switch usb port being used on pc
Rinse and Repeat until either it works or all ports exhausted
If after trying all motherboard ports odin is still cursing at you from Asgard, try one of those spare cables i mentioned earlier.
Sometimes PCs just don't wanna work, if you have the availability of another pc ANYWHERE (even the library or something) try these steps on that machine.
If its still failing on multiple pcs, clean out the usb port on the phone with Q-tip dipped in rubbing alcohol
then blowing it out with compressed air and let dry.
still nothing? you may have a hardware failure in the usb port on the phone.
Standard disclaimer: I AM NOT responsible for anything you've done or will do to your device.... this is merely a reference for you to use to get yourself out of a bind.
thank you, you're welcome, Good luck and happy flashing.
Nice work Studa .... had to fight the urge to quote the op so you knew what I was talking about.
Bubbajoe40356 said:
Nice work Studa .... had to fight the urge to quote the op so you knew what I was talking about.
Click to expand...
Click to collapse
I kind of like seeing everything written out several times . . . it's like deja-vu all over again.
Good job cris, lets hope this gets used!
Lol... I kinda made it for me to use.
I've typed this out a couple dozen times... now I can just link to here
studacris said:
So, you've been flashing stuff and now for whatever reason, you're phone won't boot.
Now you"re trying to save your poor phone's life with Odin but odin keeps failing.
Here are a few basic steps to go over to try and get Odin to cooperate:
First things First, if the device shows no signs of life whatsoever, you press the power button and it just sits there blank,
i am sorry to inform you, you are bricked and at a point beyond the help of odin. this will require JTAG to fix.
if you are in a bootloop or the phone freezes at some point of the boot sequence, this is what odin can fix.
if you do not have odin, get it HERE
here are the USB DRIVERS
i will not provide links to stock firmwares to use, those are ALL OVER the forum,
this is to help get those flashed not to completely hold your hand
only thing i'll add about which to use is:
DO NOT USE A PACKAGE CONTAINING BOOTLOADERS
IF ODIN FAILS DURING THE WRITING OF A BOOTLOADER THAT WILL BRICK THE DEVICE
STEPS:
Use USB ports connected to MOTHERBOARDno front panel ports, hubs etc...
Use a Known good usb data cable preferably OEM, you may want to have 1 or more spare just in case
right click odin and run as administrator
Have odin ready to go before you touch your phoneAll files in the proper place, now boot to DL mode and connect
If this is still Failing try:
Exiti Odin
Uninstall USB drivers
Reboot PC
Reinstall USB drivers
Switch usb port being used on pc
Rinse and Repeat until either it works or all ports exhausted
If after trying all motherboard ports odin is still cursing at you from Asgard, try one of those spare cables i mentioned earlier.
Sometimes PCs just don't wanna work, if you have the availability of another pc ANYWHERE (even the library or something) try these steps on that machine.
If its still failing on multiple pcs, clean out the usb port on the phone with Q-tip dipped in rubbing alcohol
then blowing it out with compressed air and let dry.
still nothing? you may have a hardware failure in the usb port on the phone.
Standard disclaimer: I AM NOT responsible for anything you've done or will do to your device.... this is merely a reference for you to use to get yourself out of a bind.
thank you, you're welcome, Good luck and happy flashing.
Click to expand...
Click to collapse
I unlike bubba will quote the op nice work friend
Sent from my SAMSUNG-SGH-I717 using xda premium
What does it mean to Odin? I kdd....great work
rquiett said:
I unlike bubba will quote the op nice work friend
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Show off
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Awesomeness bump. Great read.
Sent from The Bacon Pope's Oppo Find 5
Phone stuck
Hi, I'm hoping maybe someone can help me figure out what the problem is.
I'm trying to flash CWM Recovery on GTI9105p. I've actually done this before on the same device, but this time it doesn't work. Odin seems to work fine and shows PASS! after 32 seconds, but my phone stays on "Downloading..." with the blue bar full. If I manually reboot the device and try to go to recovery, it stays on Samsung model logo. Otherwise I can boot the phone just fine. What could be the issue?

[Q] Bricked GT-P7510 not recognized by various PC's

Hey all.... Long time lurker and reader here. I usually find all my answers through previous posts but I'm a little stuck here and cannot find the appropriate guide to help me out.
I have a GT-P7510 which has always been rooted and has had a few ROM lifes, so I'm no stranger to CWM and download mode, Odin Etc... (But I'm certainly no expert by any means)
Last week I tried a flash and ended up bricked. (Soft brick) I tried several times to flash back to stock with the current as well as last known good firmware from SamFiles, but ODIN would fail partially through the flash. I got the message "Can't open the specified file. (Line: 1876)", so I checked here: http://forum.xda-developers.com/showthread.php?t=1370433 But that didn't help me.... And now, my tab is not recognized in any of the laptops or desktops I plug it into. (WinXP, WinVista, Win7 -- Kies drivers all fresh from Samsung)
I can get into Download mode. I can get into recovery, (I have done a wipe/re-format Factory reset in recovery a few times now) but nothing seems to help. I'd be willing to learn how to probe around with ADB, but haven't tried for lack of a driver being recognized. I have a few Linux boxes here at the house and haven't tried them. I wouldn't know where to start if the device was recognized by them.
Any suggestions on how to get the device recognized? Or, maybe what I can do from CWM (Sideload?). or even if I get an ADB connection from one of my linux boxes, would I be able to re-flash the firmware?
Thanks in advance.
first thing is to check your cable, then your pc drivers, if u can get in to cwm, try a new cable and mount the usb from there, put in a new rom, and flash it.
hope this helps, dude. Good luck.
If you foobarred the tab by a failed flash using Odin as you described logic would dictate that it has absolutely nothing too do with pc drivers suddenly not being good if they worked before, same for pc and cable.
You need to reinstall using Odin as you say you can get into download, using a .pit file, ticking repartition, and a stock firmware file. If that works you can go on to play another day....
If you're not sue about stuff you're using, good version of Odin (not all versions flash the 7510 properly) for 7510 and drivers are here http://forum.xda-developers.com/showthread.php?t=1518895
I'll put a .pit file up here when I get to a computer and get yourself a STOCK rom from samfirmware to flash thro Odin and you should be good to go
Sent from my GT-P7510 using XDA Premium HD app
stinky73 said:
If you foobarred the tab by a failed flash using Odin as you described logic would dictate that it has absolutely nothing too do with pc drivers suddenly not being good if they worked before, same for pc and cable.
You need to reinstall using Odin as you say you can get into download, using a .pit file, ticking repartition, and a stock firmware file. If that works you can go on to play another day....
If you're not sue about stuff you're using, good version of Odin (not all versions flash the 7510 properly) for 7510 and drivers are here http://forum.xda-developers.com/showthread.php?t=1518895
I'll put a .pit file up here when I get to a computer and get yourself a STOCK rom from samfirmware to flash thro Odin and you should be good to go
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
That sounds great man.... THANKS! I do have the correct Odin, and I have a clean firmware from SamFiles. But I have tried looking for a pit for the 7510 and haven't had much luck. If you could post one, I'd be forever in your debt.
Here y'are
stinky73 said:
Here y'are
Click to expand...
Click to collapse
Thank you brother! I'll report back in a day or so.
Good luck!
sent from my still superb Google I/O 7510
stinky73 said:
Good luck!
Click to expand...
Click to collapse
Back to the drawing board I guess... I have a new cable on-order. However I was able to get the driver loaded by utilizing the dreaded "Plug - Unplug" routine several times until I just got lucky.
Odin can see it as COM5, and I used your pit (Again, TY!) I tried using the "P7510XABLPL_P7510UELPL" file I got from Samsung, but Odin is locked up at this point. (See screen cap)
I'll keep beating my head against this wall
:silly:
Odin 1.85 is just about the most random version of the prog when it comes to the 7510...
Try the one I have posted below (v1.3) it has never let me down (whereas 1.85 often has done to me what it is doing to you)
Worth a try
stinky73 said:
Odin 1.85 is just about the most random version of the prog when it comes to the 7510...
Try the one I have posted below (v1.3) it has never let me down (whereas 1.85 often has done to me what it is doing to you)
Worth a try
Click to expand...
Click to collapse
Yes. Sorry I forgot to mention that.
I saw your other post and did grab that 1.3 version. However, When I get the drivers loaded (When windows "sees" the tablet after plugging and unplugging numerous times) It will show up as COM3 or COM5 in any version of odin Except 1.3.
I tried various versions of Odin and when they all see the com port, 1.3 does not. Truly bizarre to me.... With 1.85 and or 1.7 I was successful in just loading the pit file, but if I try to load a PDA, it just freezes.
I installed Android SDK and started playing with ADB yesterday. I haven't had much success in addressing the Tablet. Also, I cannot get into recovery any more. It appears that the tablet is stuck in download mode, as if it's in a loop. ('the device states that it's downloading even after a reboot with no cable attached.)
My new cables will be here in a couple of days. Until then, I'm letting the battery die completely and will try again with the new cables.
P-tek said:
Yes. Sorry I forgot to mention that.
I saw your other post and did grab that 1.3 version. However, When I get the drivers loaded (When windows "sees" the tablet after plugging and unplugging numerous times) It will show up as COM3 or COM5 in any version of odin Except 1.3.
I tried various versions of Odin and when they all see the com port, 1.3 does not. Truly bizarre to me.... With 1.85 and or 1.7 I was successful in just loading the pit file, but if I try to load a PDA, it just freezes.
I installed Android SDK and started playing with ADB yesterday. I haven't had much success in addressing the Tablet. Also, I cannot get into recovery any more. It appears that the tablet is stuck in download mode, as if it's in a loop. ('the device states that it's downloading even after a reboot with no cable attached.)
My new cables will be here in a couple of days. Until then, I'm letting the battery die completely and will try again with the new cables.
Click to expand...
Click to collapse
That's an odd one for the download reboot.... As normally you should get choice of recovery or download as first step... Would tend to signal a failed download
I've often seen people say here "have you tried a different computer?" and scoffed a bit at that but maybe in your case...
However to be scientific you should only change one variable at a time so as to know where the result comes from, so start with the cable and we can see where you go from there
sent from my still superb Google I/O 7510 (xda hd)
Victorious
stinky73 said:
That's an odd one for the download reboot.... As normally you should get choice of recovery or download as first step... Would tend to signal a failed download
I've often seen people say here "have you tried a different computer?" and scoffed a bit at that but maybe in your case...
However to be scientific you should only change one variable at a time so as to know where the result comes from, so start with the cable and we can see where you go from there
sent from my still superb Google I/O 7510 (xda hd)
Click to expand...
Click to collapse
Thank you again for all your help!
My new cables arrived and appeared to be at the center of the issue. Once plugged in, the drivers properly loaded and I was successful with Odin. I used the pit you gave me for a re-partition, and the UELPL PDA from Samfiles.
It was initially stuck in a boot loop after the successful flash, but I was able to reboot to recovery, F/R, wipe and clean it up and now it's ALIVE! :victory:
Yeeee. Haaaaah!!!!
sent from my still superb Google I/O 7510 (xda hd)

[Q] There is no PIT partition, phone works fine though

First off, I found several cases of no PIT partition, but in every case the phone wasn't working, so my case is different
On my first try to root my I9300 the process hung at getting the PIT info. After a while I unplugged, took off battery and the phone booted fine after reinserting the battery. It took me a while to muster the courage to retry rooting and this time I got the "There is no PIT partition" error message. Phone still works fine.
I used Odin 3.07. Could it be the Odin version? Or certainly something interfering with the USB?
Anyway, my main question is, if it gets past the getting PIT part and starts actually flashing, can I feel at ease flashing using this computer (win 8.1), or should I use my ages old XP laptop? I mean if I think I've fixed the issue (which I think is some software interfering with the USB traffic), is it really fixed, if Odin goes past the part of getting the PIT or can it be only partially fixed and the actual flashing will/can still be fuxored?
pkauko said:
First off, I found several cases of no PIT partition, but in every case the phone wasn't working, so my case is different
On my first try to root my I9300 the process hung at getting the PIT info. After a while I unplugged, took off battery and the phone booted fine after reinserting the battery. It took me a while to muster the courage to retry rooting and this time I got the "There is no PIT partition" error message. Phone still works fine.
I used Odin 3.07. Could it be the Odin version? Or certainly something interfering with the USB?
Anyway, my main question is, if it gets past the getting PIT part and starts actually flashing, can I feel at ease flashing using this computer (win 8.1), or should I use my ages old XP laptop? I mean if I think I've fixed the issue (which I think is some software interfering with the USB traffic), is it really fixed, if Odin goes past the part of getting the PIT or can it be only partially fixed and the actual flashing will/can still be fuxored?
Click to expand...
Click to collapse
Have u tried flashing with other versions of odin?
Tried other usb ports like the ports at the motherboard which is at the back.
Have u tried another wire?
Have u tried other files to root the phone?
Sent from my GT-I9300 using xda app-developers app
Give a thank if I helped you
JellyYogurt said:
Have u tried flashing with other versions of odin?
Tried other usb ports like the ports at the motherboard which is at the back.
Have u tried another wire?
Have u tried other files to root the phone?
Sent from my GT-I9300 using xda app-developers app
Give a thank if I helped you
Click to expand...
Click to collapse
Didn't try other versions yet, any specific suggestions on which version is the most recommended to be used with I9300?
I tried all the USB ports on the front, haven't tried one on the back yet, will give that a try as soon as I have the time.
The wire I'm using is the one that came with the phone, I assumed that's the safest bet. I'll try another wire if the ports directly on the mother board don't work.
Haven't tried any other files for root, because AFAIK the process never gets so far as to even try actually flashing the phone. I'm at work now so I can't verify the root file I have, but I double, triple and quadruple checked and it should be the right one for my phone
Thanks for the pointers, will click thanks if your suggestions turn out as fixes for my problem.
EDIT: in case someone reads this and ponders why is nothing happening; the 4.3 update just came OTA for my phone and after that update I think I'm "forced" to install a custom rom. Reason being that the update had some extra bloatware that's causing certain apps to reload completely after only locking the phone and then unlocking. I didn't have this issue before the update. Now I'm reading up on roms and trying to decide which to go with... When I've made up my mind, I'll get back to this issue and hopefully get it fixed, as there's no other way to install a custom recovery, right?

[Q] Help Pls: Odin Fail

Hi
I just can't seem to get Odin to flash my S2. I am new to android hacking but I'm no 'tech-tard'. I have read a lot the Odin related threads on here and on google and can't seem to get it to work. I'll explain what I'm trying to do and what I have done so far.
What I want to do is to setup my old S2 for my mum, she is Vietnamese and would be great to have Vietnamese Language support so that menus, etc..are in Vietnamese! I have tried some locale apps but they're very limited. So basically I want to flash the phone with a firmware which has Vietnamese.
My phone is a UK Vodafone S2 and it's fully updated. The info on the phone is as follows:
Model Number GT-I9100
Android Version 4.1.2
Baseband Version I9100BULS3
Kernel Version 3.1.31-1484249
[email protected]#3
SMP PREEMPT Tue Dec 3 20:24:29
KST 2013
Build Number JZ054K.I9100XWMS2
I have installed Kies, have got MTP drivers installed and have got samsung usb drivers installed (v1.5.33.0). I have Odin 1.85, 3.07 and 3.09. One thing to note is that I have never been able to connect to Kies even though all the drivers are installed and working as I can access the phone via windows explorer.
The firmware I've been trying to flash is I9100DXLSD_I9100OLBLSD_I9100DXLS8_HOME.tar.md5 This firmware also came with SS_DL.dll (i'm not sure what I'm suppose to do with this file)
I have tried using the original S2 usb cable, S4 usb cable, HTC usb cable and Nexus 7 usb cable. I have tried the front and rear USB ports on my pc (although have yet to try every single rear usb port)
I think I have done clean installs of Kies and the USB drivers, by using YourUninstaller to remove them and clean up the registry, reboot. Reinstalling Kies and USB drivers and rebooting again.
I've turned on USB debugging on the phone. The phone is in download mode. I start up Odin as admin, plug the phone in and Odin sees the phone and I get the messages 'Added!' and COMx where x is 3, 4 or 5. In Odin 3.07 or 3.09 when loading the firmware, the firmware is confirmed ok but when flash is started it stalls at 'SetupConnection'. I've left it for about 15 mins and still stuck there. In Odin 1.85 it's similar except I eventually get a FAIL after the SetupConnection step.
I'm not sure what else I can do, apart form try another computer. Any help would be much appreciated.
Thanks
Q
take a look at hopper8's odin troubleshooting thread stickied in general section
TheImpossibleEnemy said:
take a look at hopper8's odin troubleshooting thread stickied in general section
Click to expand...
Click to collapse
Yeah, I've read that and followed it and still no luck.
That thread is the 'Bible' for these situations; there really isn't much else that isn't in the thread which can be suggested in these situations.
So...Your options are:-
*Try everything (you haven't done that yet) in the thread over and over and over and over until you get a successful flash. When these are recoverable (and the majority are), they're almost always fixed with perseverance.
*Give up & take your phone to a Samsung service centre (who will take a lot of your money) or a local mobile repair shop (who will charge you a bit less money) for diagnosis/repair. Obviously you're in their hands with regard to trusting them to honestly diagnose what's wrong & charge you accordingly.
The only other thing which comes to mind in this situation is an idea KeithRoss39 has bandied about recently; flash fails in this situation are sometimes caused by a malfunctioning USB board in the phone (this has become a very common fault with this phone as the time since it's initial release has increased).
Thing is, if this is indeed the case here, it's possible that your previous attempts at flashing have already corrupted the NAND, and only a motherboard replacement is fixing this. If this hasn't already happened & the board is faulty, any further flashing attempts might give you this result. But unless you know how to diagnose electronics like this, you have no way of knowing whether this is the case or not.
So, you can proceed as above, or you can stop attempting to flash right now & replace the USB board/port yourself before you attempt any further flashes. Keith has a guide in General (not stickied, there's a link in Hopper's thread) which will enable you to get this done quickly/easily/cheaply yourself if you decide to go down this path.
delete
MistahBungle said:
That thread is the 'Bible' for these situations; there really isn't much else that isn't in the thread which can be suggested in these situations.
So...Your options are:-
*Try everything (you haven't done that yet) in the thread over and over and over and over until you get a successful flash. When these are recoverable (and the majority are), they're almost always fixed with perseverance.
*Give up & take your phone to a Samsung service centre (who will take a lot of your money) or a local mobile repair shop (who will charge you a bit less money) for diagnosis/repair. Obviously you're in their hands with regard to trusting them to honestly diagnose what's wrong & charge you accordingly.
The only other thing which comes to mind in this situation is an idea KeithRoss39 has bandied about recently; flash fails in this situation are sometimes caused by a malfunctioning USB board in the phone (this has become a very common fault with this phone as the time since it's initial release has increased).
Thing is, if this is indeed the case here, it's possible that your previous attempts at flashing have already corrupted the NAND, and only a motherboard replacement is fixing this. If this hasn't already happened & the board is faulty, any further flashing attempts might give you this result. But unless you know how to diagnose electronics like this, you have no way of knowing whether this is the case or not.
So, you can proceed as above, or you can stop attempting to flash right now & replace the USB board/port yourself before you attempt any further flashes. Keith has a guide in General (not stickied, there's a link in Hopper's thread) which will enable you to get this done quickly/easily/cheaply yourself if you decide to go down this path.
Click to expand...
Click to collapse
I don't think the USB board is faulty. It charges fine and I can access the phone via windows explorer, transferring and copying files.
You try uninstall all drivers (kies and samsung usb) ,and install again only a usb drivers (without kies).
^^^
Didn't bother to read the OP, eh ?
Download Odin v3.07 And Connect your phone to pc using download mode. ( Power + Vol. D + Home ). And in odin click pda and choose ur downloaded tar file. Just let it flash. And see. Try Splitting that .tar file to CSC, PDA, MODEM using splitfus. Check google for further help.
Hit thanks if I helped you
Sent from my GT-I9100 using XDA Premium 4 mobile app
Someone else who didn't read the OP. Fantastic.
Bullit Lee said:
Download Odin v3.07 And Connect your phone to pc using download mode. ( Power + Vol. D + Home ). And in odin click pda and choose ur downloaded tar file. Just let it flash. And see. Try Splitting that .tar file to CSC, PDA, MODEM using splitfus. Check google for further help.
Hit thanks if I helped you
Sent from my GT-I9100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'll give that a shot.
Been reading about the default recovery console. Is it possible to flash the vietnamese 4.1.2 firmware over my uk 4.1.2 firmware using ADB? From what I've ready you could transfer the firmware to a memory card and use the apply update from external storage? Is this correct or would would it have to be done via ADB sideload from the SDK?
Thanks
Can't be done with stock on the S2 to the best of my knowledge (can with some other phones).

Categories

Resources