Related
I had the update with OCLF installed and it worked fine until I decided "accidentally" (very very regretful now) to install Voodoo from the OCLF app. Then the phone went into a soft reset and got stuck at the Vibrant screen.
Since then I've tried to select "install packages" or "reboot system" options in the recovery mode, but it showed only a partial progress bar at the bottom, then it got stuck at the Vibrant screen.
I gave Odin a try but the app does not see any com port after use ADB reboot or recovery commands.
Btw I did NOT select USB debugging mode before installing voodoo. I did install the USB driver for the Vibrant but am not sure it even works because the Odin app did not see any com port.
Any help is appreciated! I don't want to loose data and files in the internal storage. This is kinda urgent because I need to use phone.
i900 said:
I had the update with OCLF installed and it worked fine until I decided "accidentally" (very very regretful now) to install Voodoo from the OCLF app. Then the phone went into a soft reset and got stuck at the Vibrant screen.
Since then I've tried to select "install packages" or "reboot system" options in the recovery mode, but it showed only a partial progress bar at the bottom, then it got stuck at the Vibrant screen.
I gave Odin a try but the app does not see any com port after use ADB reboot or recovery commands.
Btw I did NOT select USB debugging mode before installing voodoo. I did install the USB driver for the Vibrant but am not sure it even works because the Odin app did not see any com port.
Any help is appreciated! I don't want to loose data and files in the internal storage. This is kinda urgent because I need to use phone.
Click to expand...
Click to collapse
The same thing happened to me. I even posted it yesterday to warn people to be careful with RYANZA Voodoo and I got flamed and insulted. Basically you fried your kernel. I tried different things and what worked for me was ODIN the JI6 back. Go to Vibrant Directory Bible under Samsung Vibrant--Android Development and find that thread. Go to the ODIN section and download the JI6 package. You will need to get into 'Download" mode on your Vibrant for ODIN to work. You need to have the phone plugged into computer via USB, hold down both volume buttons and the power button at the same time. When the screen becomes black, release only the power button and download mode will pop up. Then bring up ODIN and make sure the yellow com message pops up. With ODIN it will work right away (like 2 minutes). If you see it hanging then you need to try it again. When you get your phone back up you need to disable voodoo. Good luck. Know that the Vibrant is almost impossible to kill, you will be able to bring the phone back to life.
here's the link: http://forum.xda-developers.com/showthread.php?t=771111
instructions here: http://forum.cyanogenmod.com/topic/...r-vibrant-and-return-to-stock-phone-pc-error/
I tried flashing it using odin but the phone would start, show the tmobile thingy and just turns off. Is there any way around this?
Sent from my HTC Glacier using XDA App
Thank you for your prompt reply
quest4fire said:
The same thing happened to me. I even posted it yesterday to warn people to be careful with RYANZA Voodoo and I got flamed and insulted. Basically you fried your kernel. I tried different things and what worked for me was ODIN the JI6 back. Go to Vibrant Directory Bible under Samsung Vibrant--Android Development and find that thread. Go to the ODIN section and download the JI6 package. You will need to get into 'Download" mode on your Vibrant for ODIN to work. You need to have the phone plugged into computer via USB, hold down both volume buttons and the power button at the same time. When the screen becomes black, release only the power button and download mode will pop up. Then bring up ODIN and make sure the yellow com message pops up. With ODIN it will work right away (like 2 minutes). If you see it hanging then you need to try it again. When you get your phone back up you need to disable voodoo. Good luck. Know that the Vibrant is almost impossible to kill, you will be able to bring the phone back to life.
here's the link: http://forum.xda-developers.com/showthread.php?t=771111
instructions here: http://forum.cyanogenmod.com/topic/...r-vibrant-and-return-to-stock-phone-pc-error/
Click to expand...
Click to collapse
I'll give it a try later. Is there a good link to download the USB driver? I did but am not sure it will work with Odin. I also forgot to release the pwr button only when the Vibrant screen came on. You said release it at the black screen.
Theres voodoo on the oclf app? Where do you download it? When I downloaded it from the market it wasn't there. Do I need to install a supported kernel before it shows up?
Another thing is the phone is not in USB debugging mode before. Is this needed for Odin to work?
It is in OCLF app
krackers said:
Theres voodoo on the oclf app? Where do you download it? When I downloaded it from the market it wasn't there. Do I need to install a supported kernel before it shows up?
Click to expand...
Click to collapse
I don't remember exactly how it looks but the app has like 3 tabs: 2nd is available, 3rd unavailable or vice versa, 1st is probably the voodoo one. BE CAREFUL, read the kernel instruction first! I am sure they are not compatible. It should be disabled one or the other so users wouldn't get hacked.
ok the 3 button procedure got the phone into Recovery mode like this screen with yellow text:
--------------------------------------
Android system recovery <2e>
reboot system now
reinstall packages
--Appling Multi-CSC
Installing Multi-CSC
------------------------------------
Selecting either "reboot system now" or "reinstall packages" gives this screen:
----------------------------------------
Installing from sd card completed
rebooting..
Phone reset done
-----------------------------------------
The phone now got stuck at the Vibrant screen!
How to get into the download mode?
Holding vols up down with battery in and then plug in the USB cable, the Downloading screen came up with the digging icon and a message "do not turn off target" but it just got stuck there. I typed in the adb reboot download under the folder containing the adb files but it said "error no device found". I installed both drivers, one from Samsung site and one x86 from Softpedia site. Is it time to get a new one?
Try this.
Click HERE FOR ODIN 1.30
Samsung USB Drivers MS Windows 64bit HERE 32bit drivers HERE pick the drivers that work with your pc I have windows 7 so I use 64bit.
Step 1. Download the 512 PIT file HERE this file needs to be un rared with Winrar its a free program its HERE.
Step 2. Download the T959UVJFD.tar HERE
Step 3. Get your phone in download mode try just holding the volume up and down at the same time then plug the usb in, you might have to pull the battery and then put it back in the phone then hold volume up and down at the same time then plug the usb in it should go into download mode.
Step 4. Open Odin 1.30.
Step 5. Load the 512 PIT file you extracted with winrar into Odin 1.30 PIT section of Odin
Step 6. Load the T959UVJFD.tar you downloaded into Odin 1.30 into the PDA section of Odin.
Step 7. Click the Star button in Odin.
Step 8. Let it do its thing.
Step 9. Thank me
Step 10. Hope this helped it really doesn't get much easier then what Ive given you in this list.
Will the pit file WIPE the data (photo..)?
AustinKnight45 said:
Try this.
Click HERE FOR ODIN 1.30
Samsung USB Drivers MS Windows 64bit HERE 32bit drivers HERE pick the drivers that work with your pc I have windows 7 so I use 64bit.
Step 1. Download the 512 PIT file HERE this file needs to be un rared with Winrar its a free program its HERE.
Step 2. Download the T959UVJFD.tar HERE
Step 3. Get your phone in download mode try just holding the volume up and down at the same time then plug the usb in, you might have to pull the battery and then put it back in the phone then hold volume up and down at the same time then plug the usb in it should go into download mode.
Step 4. Open Odin 1.30.
Step 5. Load the 512 PIT file you extracted with winrar into Odin 1.30 PIT section of Odin
Step 6. Load the T959UVJFD.tar you downloaded into Odin 1.30 into the PDA section of Odin.
Step 7. Click the Star button in Odin.
Step 8. Let it do its thing.
Step 9. Thank me
Step 10. Hope this helped it really doesn't get much easier then what Ive given you in this list.
Click to expand...
Click to collapse
Somewhere in the forum said that selecting the pit file will wipe all data. Is that true because I so want to keep EVERYTHING intact! Just got back from a short vacation in Waikiki
I got the PC to see the Vibrant now with Odin but I downloaded the newer tar file T959UVJI6 (2.1 updated ver) but can not see it from selecting PDA button, it can only see the old T959UVD (stock 2.1). I am at the no point of return now so within 15mins if there is no answer then I must get going.
Thanks again!
Never mind guys! my bad did not unrar the tar file..going to download it now..wish me best of luck!
ok downloading now... it is a nerve wrecking experience comparing to WM6.1 custom rom flash which was very smooth going. I still miss the original i900 Omnia. I am going to be late for the church but God please forgive me! Oh it passed the downloading and got the S logo..
it booted up but stuck at black screen with all soft keys lighted up, tried the install packages in recovery mode again..
I guess I need to download the pit file? Will this wipe out all data?
I don't have voodoo... where did you get your oclf app from? Is it not showing because I have stock JI6 kernel?
i900 said:
I guess I need to download the pit file? Will this wipe out all data?
Click to expand...
Click to collapse
Did you follow my to-do list to the T?
this might help
you need to flash this PDA file with odin EUGENE373_SamsungS_Froyo_PDA along with the PIT 512 you should still have from the unbrick instruction odin forum then after you flash those files you need to let it do its thing it will prob take you to recovery just long press the power button and when it turns off put the usb back in the phone to get it into Download mode(just get back into download mode any way you know how) and then follow those instructions you did earlier with the unbrick instructions forum just flash the Eugene373 SamsungS Froyo PDA file first then after you flash it get right back into download mode and flash stock vibrant rom through odin.
Odin in eugenes froyo that doesnt brick.Make sure you use the 513 pit file that comes with it. When its done, pull the battery and odin the jfd. Use the 512 pit file with jfd. Check the repartition box for this one. You will be back to stock and all the lag fixes will be gone. This process works to save your vibrant from ALMOST everything
^^^oops, didnt make it to your post...just tryin to help
OCLF from the market by Ryan
krackers said:
I don't have voodoo... where did you get your oclf app from? Is it not showing because I have stock JI6 kernel?
Click to expand...
Click to collapse
But use it with extreme CAUTION at your own risk. Don't brick it like mine
Again guys thanks for your time and help but just one more time, I am still a bit confused, can you list exactly what files to download in order to get the phone back alive without loosing any data and files?
Download 512 or 513 pit first? Do it together with the tar file (check both boxes in Odin)? I understand 512 pit go with JFD (stock 2.1 rom before the update). How about the latter one? It goes with JI6? Now I got only the JI6 in the phone without the pit file. Should I download 512 with JFD first then do the latter one with JI6, and all data still remain intact?
I have the galaxy s4 from sprint (sph-l720). I was having the phone flashed to page plus. something went wrong and he couldnt get it to flash. now the phone won't boot past the samsung screen but, i can get to recovery. I have been searching for days and days on how to figure this out. When i connect it to my computer odin wont recognize the phone in download mode. i have tried to re-install the drivers but they keep failing. my computer does make the sound when i connect the usb and it does attempt to install the drivers but fails. If anyone can help me i would greatly appreciate it. i know time and knowledge is money, i am not looking for a hand out. I am out of options here, please.
1dollarbi11 said:
I have the galaxy s4 from sprint (sph-l720). I was having the phone flashed to page plus. something went wrong and he couldnt get it to flash. now the phone won't boot past the samsung screen but, i can get to recovery. I have been searching for days and days on how to figure this out. When i connect it to my computer odin wont recognize the phone in download mode. i have tried to re-install the drivers but they keep failing. my computer does make the sound when i connect the usb and it does attempt to install the drivers but fails. If anyone can help me i would greatly appreciate it. i know time and knowledge is money, i am not looking for a hand out. I am out of options here, please.
Click to expand...
Click to collapse
Sounds like a couple of things.
First go buy (or use) a brand new usb cable!
A buddy of mine was banning his head trying to connect recently and found his cable was for charging only. And I've had old usb cable s cause a world of frustration.
next uninstall the Samsung drivers and then reinstall them "as administrator".
then go find the full tar of the m f9 Rom not just the firmware but the full tar. its a zip extract it. open up Odin as administrator, put it in the PDA slot. then plug your device in and flash
Sent from my SPH-L720 using XDA Premium 4 mobile app
leaderbuilder said:
Sounds like a couple of things.
First go buy (or use) a brand new usb cable!
A buddy of mine was banning his head trying to connect recently and found his cable was for charging only. And I've had old usb cable s cause a world of frustration.
next uninstall the Samsung drivers and then reinstall them "as administrator".
then go find the full tar of the m f9 Rom not just the firmware but the full tar. its a zip extract it. open up Odin as administrator, put it in the PDA slot. then plug your device in and flash
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
okay i will try the install as admin, guess i missed that and will report back thank you for responding so fast this is driving me crazy
looks like odin still wont show the magic connection
oh and before this happened odin did work fine with this USB that i have (the one that came with the S4)
1dollarbi11 said:
oh and before this happened odin did work fine with this USB that i have (the one that came with the S4)
Click to expand...
Click to collapse
You said you can access recovery..is it a custom recovery? If so flash a stock rom
If not heres a ota mf9 flashed from stock recovery http://androidromupdate.com/2013/07/09/sprint-galaxy-s4-ota-update-l720vpuamf9-stock-via-recovery/
Sent from my SPH-L720 using xda app-developers app
1dollarbi11 said:
oh and before this happened odin did work fine with this USB that i have (the one that came with the S4)
Click to expand...
Click to collapse
Ok uninstall your old sammy driver and install the latest Sammy drivers 'as administrator'.
Make sure your phone is charged to at least 60%. Even if it doesn't turn on plug it in to the wall for a while and let it charge.
Don't connect it to PC yet.
HERE is the FULL system tar. All stock, kernel, recovery, ROM Modem.
Extract the zip and extract the .tar.md5.
Run Odin 'as administrator'. Place tar.md5 into PDA slot of Odin. Odin should look like this If you check on 'repartition or anything you are going to hose your phone...
With Odin open on your PC and your phone still not connected, put it into download mode - Simultaneously Press and Hold [Power][VolDn] until confirmation screen appears
Press [VolUp] to enter Download mode.
NOW plug your phone into the PC [Windows may install additional drivers; hopefully] and see if it shows up in any COM port (doesn't matter which one). If it shows up press start and let it finish. You should then have a stock MF9 working. First boot takes about 5 full earth minutes, let it go for even a little longer if necessary. If it doesn't boot after 10 earth minutes you may have to pulll the battery and then restart it but it should start.
You can then use the CF-Autoroot method to quickly root the phone. Then download goomanager and install a custom recovery and your off to the races.
Good luck.
leaderbuilder said:
Ok uninstall your old sammy driver and install the latest Sammy drivers 'as administrator'.
Make sure your phone is charged to at least 60%. Even if it doesn't turn on plug it in to the wall for a while and let it charge.
Don't connect it to PC yet.
HERE is the FULL system tar. All stock, kernel, recovery, ROM Modem.
Extract the zip and extract the .tar.md5.
Run Odin 'as administrator'. Place tar.md5 into PDA slot of Odin. Odin should look like this If you check on 'repartition or anything you are going to hose your phone...
With Odin open on your PC and your phone still not connected, put it into download mode - Simultaneously Press and Hold [Power][VolDn] until confirmation screen appears
Press [VolUp] to enter Download mode.
NOW plug your phone into the PC [Windows may install additional drivers; hopefully] and see if it shows up in any COM port (doesn't matter which one). If it shows up press start and let it finish. You should then have a stock MF9 working. First boot takes about 5 full earth minutes, let it go for even a little longer if necessary. If it doesn't boot after 10 earth minutes you may have to pulll the battery and then restart it but it should start.
You can then use the CF-Autoroot method to quickly root the phone. Then download goomanager and install a custom recovery and your off to the races.
Good luck.
Click to expand...
Click to collapse
way cool thank you for the write up I am in the process of trying this out. thank you very much
dang still a no go as far as odin seeing the phone. i guess i dont understand why odin was working before but now after reinstalling the drivers several times still cant pick it up.... any ideas? tried different port and new cable. anyone able to check it out remotely?
1dollarbi11 said:
dang still a no go as far as odin seeing the phone. i guess i dont understand why odin was working before but now after reinstalling the drivers several times still cant pick it up.... any ideas? tried different port and new cable. anyone able to check it out remotely?
Click to expand...
Click to collapse
one more silly thing to try.
After your phone is fairly well charged take out the battery for 1/2 hour or more even. I had some issues with other sammy's and doing that worked a few times; think it lets all the capicitors fully discharge on the device.
Put it back in the phone and go straight to download mode. Then start Odin and plug your phone in.
Also did you uninstall the old drivers, reboot, then install the new drivers and then reboot again before trying to connect?
I had this problem as well once. My cure was using Revo or some other advanced uninstaller to remove Samsung Kies, then I reinstalled the Samsung drivers.
However, that is only assuming that your problem is coming from your computer. Sounds like your phone's usb drivers got messed up during the flash. This seems somewhat reasonable to me, as I assume the USB drivers are in /system and the flash would disturb files there.
One other idea: be advised that Download Mode eventually times out. So, if you turn your phone on in Download Mode and leave it there for a while THEN connect it. Odin may not register it because your phone shuts off the download stream after a certain time of inactivity.
Hope this helps.
What are you guys using to unzip this image files, I downloaded like more than 10 stock files, every time I try to unzip them, it says the file is broken. I used 7zip, WinZip. My laptop has windows 7.
You should just have a .zip file that you flash via the recovery interface.
-Mobile post
richardpunch said:
You should just have a .zip file that you flash via the recovery interface.
-Mobile post
Click to expand...
Click to collapse
No, I'm talking about stock images that are in zip or rar files, that I need to unzip to get the the other tar.md5 files to odin, cause my phone is not working anymore. I think it might be my computer, or my internet connection. I don't know, I'm lost
maurogg84 said:
No, I'm talking about stock images that are in zip or rar files, that I need to unzip to get the the other tar.md5 files to odin, cause my phone is not working anymore. I think it might be my computer, or my internet connection. I don't know, I'm lost
Click to expand...
Click to collapse
NO just unzip the zip file.
Download the zip. extract the .tar.md5 file - it's a 2.10GB file after extraction named "L720VPUAMF9_L720SPTAMF9_L720VPUAMF9_HOME.tar.md5" .
Launch Odin 'as administrator' and put that ONE .tar.md5 file in the PDA slot.
Re-read the tips here on the rest.
leaderbuilder said:
NO just unzip the zip file.
Download the zip. extract the .tar.md5 file - it's a 2.10GB file after extraction named "L720VPUAMF9_L720SPTAMF9_L720VPUAMF9_HOME.tar.md5" .
Launch Odin 'as administrator' and put that ONE .tar.md5 file in the PDA slot.
Re-read the tips here on the rest.
Click to expand...
Click to collapse
I used a friend computer, and I was able to unzip the file, I think my computer is corrupting those files some how. Thanks for the help though.
ODIN keeps failing at 'system.img.ext4' - 4.3 with KNOX bootloader
Hi guys
I've recently tried to flash a 4.3 stock rom via Odin and it failed, and I now have a bricked phone that has this warning:
PHONE-----YELLOW TRIANGLE----- COMPUTER
'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
I tried to flash the latest KNOX bootloader roms via ODIN to boot up the phone, however....
ODIN keeps hanging on the "system" flashing command and goes to a red "fail". It won't start flashing "system.img.ext4.... etc"
I've tried all versions of ODIN and all version of 4.3
I can't use any 4.2.2 roms as the phone only seems to accept 4.3 stock roms now.
Do you guys know why ODIN keeps failing at flashing 'system.img.ext4' ?
Any advice would be greatly appreciated, thanks!
how to fix odin fail
Hey guys
I found a way to fix my ODIN flashing errors (with system.img.ext4)
Install SAMSUNG USB drivers from here: http://forum.xda-developers.com/showthread.php?t=2038555
Make sure you are NOT using VMWare Fusion on Mac OS X.
Bootcamp your Mac if you have to (with 64 bit Windows 7 preferably), or borrow a friends' Windows laptop.
My biggest mistake was running VMWare Fusion on Mac OS X - the new KNOX bootloader/roms doesn't like being flashed on virtual Windows PC
Odin flash PDA should work perfectly fine now
I finally saved my phone from being a brick after 36 hours!!!!
Thanks for this - I too was attempting to do this using VM Fusion. Sorted once I flashed on a non virtual machine.
VMWare Fusion
I had the exact same issue using Odin from VMWare Fusion. Since I didn't have a PC handy, I had Parallels installed on my other mac. I was able to successfully flash the new ROM via my Parallels VM.
I Just flash the PIT file form 4.2.2 after flash 4.3 and everything is ok.
Wysłane z mojego GT-I9506 przy użyciu Tapatalka
I have the same problem but in windows
Hello community
can someone get me some instructions to solve this on a windows 8.1 notebook
S4 mini I9195 - Spanish Vodafone phone, flagged already with KNOX 0x1
4.2.2. android
Thank you in advance
orchid18 said:
I had the exact same issue using Odin from VMWare Fusion. Since I didn't have a PC handy, I had Parallels installed on my other mac. I was able to successfully flash the new ROM via my Parallels VM.!
Click to expand...
Click to collapse
Oh Geez! Wish I had found this post hours ago...
Thank so much!
orchid18 said:
Hey guys
I found a way to fix my ODIN flashing errors (with system.img.ext4)
Install SAMSUNG USB drivers from here: http://forum.xda-developers.com/showthread.php?t=2038555
Make sure you are NOT using VMWare Fusion on Mac OS X.
Bootcamp your Mac if you have to (with 64 bit Windows 7 preferably), or borrow a friends' Windows laptop.
My biggest mistake was running VMWare Fusion on Mac OS X - the new KNOX bootloader/roms doesn't like being flashed on virtual Windows PC
Odin flash PDA should work perfectly fine now
I finally saved my phone from being a brick after 36 hours!!!!
Click to expand...
Click to collapse
very nice! Thank! This worked for me. After 7 hours make trying recover my mini s4!
orchid18 said:
Hey guys
I found a way to fix my ODIN flashing errors (with system.img.ext4)
Install SAMSUNG USB drivers from here: http://forum.xda-developers.com/showthread.php?t=2038555
Make sure you are NOT using VMWare Fusion on Mac OS X.
Bootcamp your Mac if you have to (with 64 bit Windows 7 preferably), or borrow a friends' Windows laptop.
My biggest mistake was running VMWare Fusion on Mac OS X - the new KNOX bootloader/roms doesn't like being flashed on virtual Windows PC
Odin flash PDA should work perfectly fine now
I finally saved my phone from being a brick after 36 hours!!!!
Click to expand...
Click to collapse
I have the same problem with my s5 mini (dual sim) sm-g800H, Odin fails just when it starts system.img.ext4. Any help with this, i have tried it on a couple of Windows 7 pcs using different USB cables and different Odin versions, any idea how to solve this?
Kitkat
if you have installed Stock Kitkat or Custom 4.4.2 Touchwiz rom [some roms support rolling back and others don't], you won't be able to roll back to 4.3 . i had this problem when i tried to roll back to 4.3 from 4.4.2
Fix : install latest Kitkat firmware
Al_Jourgensen said:
Hello community
can someone get me some instructions to solve this on a windows 8.1 notebook
S4 mini I9195 - Spanish Vodafone phone, flagged already with KNOX 0x1
4.2.2. android
Thank you in advance
Click to expand...
Click to collapse
1.install samsung usb driver
2. find your mobile model and download single .tar image from sammobile
3. flash through odin(tick only F.reset time and auto reboot)
Odin Fail with VMWare Fusion on Mac: The below worked for me
This post is late to this thread: Wanted to share what worked for me for Verizon SCH-I545 Samsung Galaxy S4:
* Used Windows 7 on VMWare Fusion 7.0.1 on MacBook Air; Odin 3.09
* Experienced same Odin failure for "system.img.ext4" during process; this fixed it.
* Change Fusion USB Settings: Close Windows but not Fusion. Go to "Fusion Settings/USB & Bluetooth". Go to "Advanced USB options" and select "USB Compatibility" USB 1.1.
* Restart Fusion and restart Windows.
* I used TAR file "I545VRUFNC5_I545VZWFNC5_I545VRUFNC5_HOME.tar.md5" inside downloadable file "I545VRUFNC5_I545VZWFNC5_VZW" which was downloaded from URL: sammobile.com/firmwares/database/SCH-I545
* Note: I joined this website for 1 week to take advantage of faster download speeds. I tried without joining and the download timed out before the download was completed. Speed was much faster with membership.
* Prep phone for download by pressing 3-buttons "Power-Home-Volume Down". Note: Be sure to hold down the "Volume Down" portion of the button and not the complete Volume button. Press Volume Up when prompted on screen by the phone.
* Start Odin 3.0.9
* Plug in phone using USB cable that came with phone. Other cables may work - but I don't know.
* Odin will indicate that the phone was "Added"
* Be sure to select in Odin the Options "Auto Reboot" and "F. Reset Time". Select "AP" and go to file to add: "I545VRUFNC5_I545VZWFNC5_I545VRUFNC5_HOME.tar.md5"
* Adding this file takes a few seconds. Once added click "Start"
* The process seemed to take quite a bit of time, likely due to it being a USB 1.1 but it eventually took.
* Once it "Passed" in Odin the phone was on the red Verizon screen for about 3 minutes and then indicated it was updating the apps
* Once apps were updated the phone was in startup mode
* It worked fine and was back to normal.
* Close Windows, and reset Fusion USB settings back to USB 2.0.
* Note: I use USB 2.0 settings in Fusion as Windows 7 doesn't recognize USB 3.0 and Windows (in Windows Explorer) has difficulties, when USB 3.0 is selected, recognizing many connected USB devices even though Fusion indicates these devices are connected.
Hope this works. Thanks to the many folks on this thread and in this forum who assisted me in determining a solution.
you saved my life !!!!
thanks
it works with parallel desktop.
I'm still having that problem.
orchid18 said:
Hey guys
I found a way to fix my ODIN flashing errors (with system.img.ext4)
Install SAMSUNG USB drivers from here: http://forum.xda-developers.com/showthread.php?t=2038555
Make sure you are NOT using VMWare Fusion on Mac OS X.
Bootcamp your Mac if you have to (with 64 bit Windows 7 preferably), or borrow a friends' Windows laptop.
My biggest mistake was running VMWare Fusion on Mac OS X - the new KNOX bootloader/roms doesn't like being flashed on virtual Windows PC
Odin flash PDA should work perfectly fine now
I finally saved my phone from being a brick after 36 hours!!!!
Click to expand...
Click to collapse
i have downloaded drivers but this time when that fails. it just moved little bit but still fails
Swapnil Soni said:
i have downloaded drivers but this time when that fails. it just moved little bit but still fails
Click to expand...
Click to collapse
orchid18 said:
ODIN keeps failing at 'system.img.ext4' - 4.3 with KNOX bootloader
Hi guys
I've recently tried to flash a 4.3 stock rom via Odin and it failed, and I now have a bricked phone that has this warning:
PHONE-----YELLOW TRIANGLE----- COMPUTER
'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
I tried to flash the latest KNOX bootloader roms via ODIN to boot up the phone, however....
ODIN keeps hanging on the "system" flashing command and goes to a red "fail". It won't start flashing "system.img.ext4.... etc"
I've tried all versions of ODIN and all version of 4.3
I can't use any 4.2.2 roms as the phone only seems to accept 4.3 stock roms now.
Do you guys know why ODIN keeps failing at flashing 'system.img.ext4' ?
Any advice would be greatly appreciated, thanks!
Click to expand...
Click to collapse
I finally get rid of this after several hours of searching. for me im flashing the 4 files, after failed flashing, ive red from somewhere to rename the phone/cp file, by removing .md5, then extracting modem.bin to put in cp box(odin), then flash success, then reboot samsung to download mode again the flash the last csc file, finally saw the progress bar.
Worked for me too, thanks!!! Was trying to install using Odin v3.12.3 in VMware Workstation on Windows 10.
I have just bricked my newly-bought Note 3 (N900).
I wanted to flash the latest version of Note 3 via Odin 3.08 (from 4.3 to 4.4.2). I made a big mistake as I didn't enable the "USB DEBUGGING" mode before go to download mode.
I clicked start in Odin and it show FAIL!!!
After I restart the phone all I see on the screen is the message "Firmware upgrade encountered an issue Please select recovery mode in Kies & try again."
I tried to recover it through Kies, but the it shows the phone is not connected or not support. Meaning the Kies cannot communicate with the phone at all.
I also tries to flash in Odin many times, but it still fails.
Please!!! Can anyone here give me some solution.
Thanks.
boycam said:
I have just bricked my newly-bought Note 3 (N900).
I wanted to flash the latest version of Note 3 via Odin 3.08 (from 4.3 to 4.4.2). I made a big mistake as I didn't enable the "USB DEBUGGING" mode before go to download mode.
I clicked start in Odin and it show FAIL!!!
After I restart the phone all I see on the screen is the message "Firmware upgrade encountered an issue Please select recovery mode in Kies & try again."
I tried to recover it through Kies, but the it shows the phone is not connected or not support. Meaning the Kies cannot communicate with the phone at all.
I also tries to flash in Odin many times, but it still fails.
Please!!! Can anyone here give me some solution.
Thanks.
Click to expand...
Click to collapse
make sure kies is not running then try odin again
jaythenut said:
make sure kies is not running then try odin again
Click to expand...
Click to collapse
I tried many time already, but still fail. I think because the usb debugging mode was not enable at the first place.
Thank anyway.
boycam said:
I tried many time already, but still fail. I think because the usb debugging mode was not enable at the first place.
Thank anyway.
Click to expand...
Click to collapse
Usb debugging has nothing to do with it failing when you're using odin. Try a different version of odin.
A simple reflash via Odin 1.85 or 3.07/3.04 will fix it.
boycam said:
I have just bricked my newly-bought Note 3 (N900).
I wanted to flash the latest version of Note 3 via Odin 3.08 (from 4.3 to 4.4.2). I made a big mistake as I didn't enable the "USB DEBUGGING" mode before go to download mode.
I clicked start in Odin and it show FAIL!!!
After I restart the phone all I see on the screen is the message "Firmware upgrade encountered an issue Please select recovery mode in Kies & try again."
I tried to recover it through Kies, but the it shows the phone is not connected or not support. Meaning the Kies cannot communicate with the phone at all.
I also tries to flash in Odin many times, but it still fails.
Please!!! Can anyone here give me some solution.
Thanks.
Click to expand...
Click to collapse
USB Debugging has nothing to do with odin flash, make sure while flashing below steps.
1. Update boot loader is selected in odin.(Edit:for single file not required)
2. Disable antivirus.
3. make sure note 3 drivers are installed.
4. kies not running in bag round.
5.Clear Factory Data & Catch before flash.
if all of those step fail..
try to flash ur rom on other computer or laptop
Sent from my SM-N900 using XDA Premium 4 mobile app
radicalisto said:
A simple reflash via Odin 1.85 or 3.07/3.04 will fix it.
Click to expand...
Click to collapse
Thankx man itis worked:good::good:
jdomadia said:
USB Debugging has nothing to do with odin flash, make sure while flashing below steps.
1. Update boot loader is selected in odin.(Edit:for single file not required)
2. Disable antivirus.
3. make sure note 3 drivers are installed.
4. kies not running in bag round.
5.Clear Factory Data & Catch before flash.
Click to expand...
Click to collapse
tried flashin with diff odin versions, was not working, tried ver 1.85, cause it lets you select update boot loader.......and BAM,,it worked on my tmobile tab 4, now i c.an wipe the tears off the key board, thanks, didnt do # 5 tho, was rooting the tab with cf auto.
markap99 said:
tried flashin with diff odin versions, was not working, tried ver 1.85, cause it lets you select update boot loader.......and BAM,,it worked on my tmobile tab 4, now i c.an wipe the tears off the key board, thanks, didnt do # 5 tho, was rooting the tab with cf auto.
Click to expand...
Click to collapse
You've indeed saved my day... I've been searching high and low, installing various versions of Odin3, downloading tonnes of tar, tarmd5, zip, etc.!
Pardon me for my ignorance, but I never intended to root my cell phone in the first place. I was merely following what Kies suggested, "A New Firmware, Wanna Upgrade?" Oh, truly? Gee, thanks! And **** it, it screwed up my GT-N7000, saying "Firmware upgrade encountered an issue..." and my cell phone never saw the daylight again, regardless how I started it, factory-reset mode wasn't possible at all, only download mode could be started up. Tried with various methods of Odin3 on multiple ROMS, to no avail, until I read your short reply. BAM! (As you put it...)
Thanks a bunch, mate!
I have a similar issue with my sm n900. Lost my imei and baseband, i needed to flash a custom rom to get my baseband before working on the imei, after flashing via odin phone boots to samsung logo then goes blank. And recovery says E failed to mount efs . But i need to use adb on my pc. So how can i possibly enabe usb debugging in order for adb to find my device?
Flashing a stock ROM from sammobile.com via Odin does not require USB debugging. Flashing a stock ROM will flash everything, including modem, bootloader, and recovery.
My N900 Bricked
I am unable to Go to download mode not even the charging symbol too
no Luck at all phone is not starting need a Unbrick or help me how to get it sorted
galaxy Note 3 Sm N900
Tried to open the phone to short the wire but the shorting mentioned in all the imagees doesnt match the design of the phone internal
can some one tell me which points to short to start the phoen in Ext sd mode
or any help would help
hello guys bit new here, i have tried rooting my device via ODIn coz vroot dint work and couldnt understand the reason since it was in CHINESE.
for now the device is stuck at "firmware problem need to upgrade it via kies mode" thogh i have tried doing the same through kies and kies 3 but wasnt succeful.
Please help as i am in urgent need of tablet.
the model no is SM T 231
Hi,
I will have your thread moved to your device section.
Good luck!
Moved to the correct forum.
Have you tried to flash a stock ROM from Odin in Download Mode? (not kies)
orangekid said:
Moved to the correct forum.
Have you tried to flash a stock ROM from Odin in Download Mode? (not kies)
Click to expand...
Click to collapse
nope i dont where to download the STOCK and even the procedure
I would DL stock KitKat with this link:
http://www.sammobile.com/firmwares/3/?download=33706
You might have to register to DL but sammobile is the only place I can find a decent DL for it.
Once it downloads unzip the file.
Download Odin 3.09 (you can find a free download everywhere).
Make sure your device is off, then hold vol dn and them power till it says to hit the button for download mode.
Once in download mode plug into your computer and if windows 7 or 8 let the drivers install fully.
If it does not find drivers then look for them manually.
Once you've got the drivers open Odin. It should be a green light on comm 1 or something like that showing a device is plugged into it.
Make sure ONLY F Reset Time and Auto Reboot are checked and nothing else.
Hit the AP button and find the tar file or md5 file you unzipped earlier.
Once it loads up hit start and hope for the best while it flashes.
Warning; read more about this before you try it. Once KitKat flashes do not try to downgrade, but read all about it.
I linked you to firmware for device SM-T231 so that had better be your device. Triple and quadruple check to make sure the file is the right one for your device...
Hope this helps.
Sent from my 1+bacon.