So I tried odining my phone back to eb13 today, but the program keeps on hanging on the factoryfs process about 3/4ths of the way through. I already tried putting the .tar in the phone and pda section, and using other usb ports on my computer, is there any hope for me?
what eb13 tar are you using?
I would try to download it again (the eb13 extended is a great place to start, if you're going to use a rom afterwards)
be sure to uncheck the time reset checkbox and include the pit the tar needs to be odin'd with.
good luck
Try a different usb cord, samsungs stock cable isn't great. Also try pulling your sd card outa the phone while you odin, I guess some people have run into problems with odin when the sd is in.
Sent from my ACS frozen Epic
Related
Hello , i ran the EB13 exe that was on the samsung website but it froze halfway thru.
then i tried to ODIN back to DI18 but it kept freezing after about three hours it went thu then i flashed the "update.zip" to get to EB13 which worked but it was very unstable for me so i decided to use ODIN and the EB13 tar file.
well its been seven hours of redownloading the Tar files reinstalling drivers , diffrent usb ports and still nothing.
i can only get into Download mode but ODIN just freezes everytime same with the exe i've tried on both my computers nothing has worked.
i install the drivers and the computer recognizes the phone but ODIN always seems to freeze along with the exe any ideas on why?
i don't believe im "rooted" because i was able to ODIN EB13 but it never got passed the samsung boot so im not worried about taking it into a sprint store but that won't be possible until late tommorow can someone PLEASE HELP??
I will be forever grateful
iSaint said:
Hello , i ran the EB13 exe that was on the samsung website but it froze halfway thru.
then i tried to ODIN back to DI18 but it kept freezing after about three hours it went thu then i flashed the "update.zip" to get to EB13 which worked but it was very unstable for me so i decided to use ODIN and the EB13 tar file.
well its been seven hours of redownloading the Tar files reinstalling drivers , diffrent usb ports and still nothing.
i can only get into Download mode but ODIN just freezes everytime same with the exe i've tried on both my computers nothing has worked.
i install the drivers and the computer recognizes the phone but ODIN always seems to freeze along with the exe any ideas on why?
i don't believe im "rooted" because i was able to ODIN EB13 but it never got passed the samsung boot so im not worried about taking it into a sprint store but that won't be possible until late tommorow can someone PLEASE HELP??
I will be forever grateful
Click to expand...
Click to collapse
Try again, removing the battery from the device for at least 5 minutes. Press the power button, and hold it for a few seconds, with the battery out. Reboot your computer prior to continuing, insert the battery, then try the flash procedure again, in the download mode, with DI18. Worked for me. Good luck!
Thank you , but no luck yet that didn't even work 8(
getting desperate now
iSaint said:
Thank you , but no luck yet that didn't even work 8(
getting desperate now
Click to expand...
Click to collapse
Hmmm... Try an older version of Odin. Maybe the version that was around at the time of DI18. I'm all out of suggestions after this. Again, good luck!
Are you using a USB port directly on the back of the motherboard?
Have you successfully used odin in the past with this pc?
Here is my problem. It all started a few days ago. My phone's drivers on the computer got all messed up. I reinstalled it and thought nothing of it. Today I was guna flash a new rom on. I odin my phone to do a clean install. Then i rooted it to ext4. (After the fact i realized i had clicked the wrong file and loaded di18) However then my bro wanted to use my computer for his epic to odin it too. So i can't load my phone cause its in ext4. I can't fix the drivers because its in download mode and can't get into regular mode. And I can't odin it back because odin wont' recognize it because of my drivers. Its a circle of pain. Is there anything I can do?
After thinking about it will loading a di18 ext4 rom work to fix it?
Reinstall the drivers. And odin ec05 pre rooted. If ur in download mode its fine. Just delete the drivers reboot your pc re install the drivers put your phone into download mode and connect too your usb cable. Your phone doesn't have too be in "regular" mode as you callled it
There aren't any DI18 EXT4 roms. There isn't any EXT4 support for Eclair.
Redownload the Drivers then run ODIN. Install one of the pre rooted .tars.
http://www.multiupload.com/A9VPX4G2ZW here's the ec05 ext4 pre rooted tar
driver
i already redownloaded drivers it kept on not installing saying failing to install.
Ok download the link I gave u for ec05 tar. Put the tar in pda. Make sure u have the pit file selected as well.
And when u open odin. If your phone connects it'll be a yellow box saying com whatever could be com 6 or com 8. Also only have auto reboot checked nothing else
Sounds like your not using odin properly. Here Is a video showing you exactly what too do.http://www.youtube.com/watch?v=YQ2g6J1JgjU
samdsox said:
i already redownloaded drivers it kept on not installing saying failing to install.
Click to expand...
Click to collapse
Uninstall the drivers first and reboot.
fixed but new issue
I managed to. Fix it by using another computer and my dads phone to install drivers. Btw I already knew how to get in dl mode use odin root flash roms and all of that. My problem came from the fact thatb odin didn't recognize my phone in dl mode on my main computer. Now onto my new issue. Last night after I fixed the phone I had a small pinl blotch on the topleft o my phone. Now the blotch. Has spread to my whole phone along with blue and purple dots almost like its leaking. Is the lcd broken? Any ideas?
Ditch odin and learn to use heimdall
Sent from my SPH-D700 using XDA App
best way to fix this is to uninstall the usb root hubs in the device manager and reboot. that's for the driver issue...
Ive rooted and flashed roms many time and this morning I wasnt thinking and was in goo mngr and flashed 10.2. whatever cm nightly. Of course im mk4 4.3 and that of course is 4.4. anyway it worked except for the fact it would not install google play even though i did g apps and was 4.4 as well so nothing would load as far as apps. And I tried to restore in my philz touch recovery and would not restore md5 mismatch. so after long frustration I factory reset my phone because after all the time of trying to restore it had little space left and plus it stoped reading my ext sd card how convienient. So I downloaded the stock l900vpubmk4 tar file and went to donload mode and open odin set pda for that file and hit start and it will not go past saying startup connection. And now when I try to turn on recovery it says problem with the firmware go to kies recovery to solve this issue or something to that effect which I have never seen this before so there it is Big Mistake if I have to I will go buy a note 3 and be done with it ive put this phone through hell and back so im supprised its taken this long. Any suggestion would be greatly appreaciated!
Stay calm! Please verify your MD5 on the .tar file and try again!
Use an OFFICIAL CABLE! I cannot stress this enough. Use a Samsung or HTC USB cable or find someone who has one (some cheap cables have never worked for me when servicing phones through Odin). Put your phone into Download mode, connect the USB cable, wait a few seconds, now open Odin. You should see a COM port. Try it now.
Sent from my SPH-L900. Please hit the thanks button if I helped you out!
OK! SO, basically it's like this!
i have the phone SGH-T989 anf its going in downloading mode but not in recovery! ok and no OS is installed as it only stuck at SAMSUNG logo when turning on normally!
now i have alll the ODIN version but i am using ODIN v1.85V for this! and firstly when i flash that
T989UVMC6_T989TMB_T989UVMC6_HOME.tar
file it says GETTING PIT partiotion something
and then NO PIT found or something like that!!
now i used other ODIN version V3.04 V3.07 or .09
but all JUST HANGS like ODIN works but nothing righ above [ID:COM] SECTION AND NOTHING ON PHONE OR SOMETHING!!
doesn't even start the process after pressing START!
what the HELL should i do even tried PIT file in that but it says FAIL i do tick RE-PARTITION also! ) i also have
T989UVLI4_T989TMBLI4_T989UVLI4_HOME.tar
but same with this and i have this PIT file!
CELOX_USA_0824.PIT
HELLPPPP!
Never check "repartition"...you may have dug a hole with that already I'm afraid.
To flash the official firmware, Odin 3.04 or 3.07 are the ones to try. You need to be sure your phone is in download and communicating with Odin. If you don't see "added" when you plug it in, your drivers aren't right.
That other pit you mentioned is not for this device, not that I know of anyway. Flashing that will likely be the end if your phone.
And one big thing with Odin.....Kies can not be running. Go into the PC's task manager and end any kies processes. Then open Odin. Then plug your phone in.
See how that goes. Any errors, write them down and post them here.
Repartitioning may have already landed you in hot water tho...
I have a Sprint Note 4 that supposedly had a custom ROM installed on but I believe the digitizer is broken. Nothing shows up on the display. I booted into DOWNLOAD MODE using Home Power and volume down and flashedN910PVPU1ANK2_N910PSPT1ANK2_SPR then N910PVPU1ANIE_N910PSPT1ANIE_SPR via ODIN It sounds like its stuck in a boot loop after both flashes, but ODIN says PASSED when it finishes. Since I can't access the screen, how can i get this flashed back to a stock rom? Any help would be greatly appreciated.
I'm confused; why flash two stock tars? Did you let the phone boot after flashing the first stock tar?
I'd suggest a factory reset in recovery, power down, Odin the factory tar of your choice and let it auto boot. You should see the phone boot into into recovery briefly on the auto boot when flashing stock tar in Odin, then fully boot. If not seeing the brief recovery, start over and try again.
I recall a YouTube video on a digitizer issue that may have been resolved. The guy had a dead spot on the digitizer. I think it only suggests a possible fix in a follow-up video the user posted. But maybe the stock tar will fix it.
why flash two stock tars?
After flashing the the first one, it just kept rebooting. That was last night. Today I flashed the older one. I'm trying install ADB on my Windows 7 desktop to enter recovery.
So you can't do power down, volume up, home plus power to get to recovery?
The stock kernel won't allow adb access; permission denied when booted. Haven't tried adb on a boot loop; don't know if it lets you in or not.
Did you check the md5 for match prior to Odin? Maybe bad download?
Have you tried Odin without the sdcard installed. Bad user data or root directory data bad?
You could Odin the TWRP tar recovery and wipe everything but recovery and boot partition. Then Odin the stock tar after a power down.
Be careful not to select repartition during Odin. There was a PIT file posted but AFAIK, no one has shared a successful experience using the repartition with PIT file. Anyone correct me if I'm wrong and post a link to correct PIT file to use. Please.
samep said:
So you can't do power down, volume up, home plus power to get to recovery?
The stock kernel won't allow adb access; permission denied when booted. Haven't tried adb on a boot loop; don't know if it lets you in or not.
Did you check the md5 for match prior to Odin? Maybe bad download?
Have you tried Odin without the sdcard installed. Bad user data or root directory data bad?
You could Odin the TWRP tar recovery and wipe everything but recovery and boot partition. Then Odin the stock tar after a power down.
Be careful not to select repartition during Odin. There was a PIT file posted but AFAIK, no one has shared a successful experience using the repartition with PIT file. Anyone correct me if I'm wrong and post a link to correct PIT file to use. Please.
Click to expand...
Click to collapse
I tried without SD card and I didn't check repartition in ODIN. The md5 matched on both.
Did you try the suggestion of using TWRP to wipe partitions prior to stock tar? Look next to last paragraph of previous post.
Only other advice I can think of ATM is that the stock tars are so large, it takes a few moments to verify once selected. I leave my phone USB disconnected until Odin has verified the tar selected. Then I plug the USB and make sure I have the COM pop-up prior to start. If not, disconnect and reconnect the USB until COM is displayed. Not sure but I think there were some posters that didn't really flash the stock tar in Odin.
samep said:
Did you try the suggestion of using TWRP to wipe partitions prior to stock tar? Look next to last paragraph of previous post.
Only other advice I can think of ATM is that the stock tars are so large, it takes a few moments to verify once selected. I leave my phone USB disconnected until Odin has verified the tar selected. Then I plug the USB and make sure I have the COM pop-up prior to start. If not, disconnect and reconnect the USB until COM is displayed. Not sure but I think there were some posters that didn't really flash the stock tar in Odin.
Click to expand...
Click to collapse
How can I use TWRP without the screen?
thanks
Sorry but I got focused on the boot loop issue and lost focus on the screen issue.
No screen has me wondering how you know you're in download mode to flash Odin tar?
Starting over, I've never used kies but there was a similar problem in this thread I found with Google.
www.androidpit.com/forum/606685/phone-no-os-or-cwm-or-download-mode-please-help
Scroll down to post 10 for instructions.
Anyone else have experience or suggestion to share? Please jump in.
samep said:
Sorry but I got focused on the boot loop issue and lost focus on the screen issue.
No screen has me wondering how you know you're in download mode to flash Odin tar?
Starting over, I've never used kies but there was a similar problem in this thread I found with Google.
www.androidpit.com/forum/606685/phone-no-os-or-cwm-or-download-mode-please-help
Scroll down to post 10 for instructions.
Anyone else have experience or suggestion to share? Please jump in.
Click to expand...
Click to collapse
I went by feel....and the fact that Odin said COM connected. and PASSED
kevg77 said:
I went by feel....and the fact that Odin said COM connected. and PASSED
Click to expand...
Click to collapse
So you pulled the battery, pressed and held volume down, home and power buttons until it vibrated, waited to make sure it wasn't just booting, when satisfied, you pressed volume up; right?
I'd say that is a sufficient feel.
If the Odin or kies update won't take and screen is dead; with no adb access, who would know what's on the phone unless it's just not playing the right boot tone when it keeps rebooting? Problem?
I think that may be enough to take your phone back to point of sale and ask for replacement without worrying about root voiding warranty?
Did you try the Kies update?
I am familiar with the Note 3, thats how I was able to get it into Download mode by feel. I tried KIES and it said that my device is not supported. Im using the latest version of KIES. I know I'm running into an issue with the usb driver recognizing...Im on Windows 10 technical preview. thinking about trying it on an old Win7 laptop.. thanks for the advice