hi i dint find any other place but its about samsung omnia i900 which got dead while flashing
how should i recover???
Depends on when the i900 died on you...
Sometimes (!) it helps to charge the device - and flash again.
Make sure you have the necessary Samsung driver on your computer, your device is fully charged, USB2 slots are available. And it is better to use a laptop instead of a computer. You wouldn't like an outage while flashing...
HI
You might have probably lost your boot files. Try to find the .eb0 file for your mobile from internet, flash it with whatever software you are using.
Related
Hey guys,
When I bought my Omnia 2 with WM 6.1 on it, it worked great but when I went and installed the stupid PC studio software that came with the phone I tryed to update and now my phone has either a thing saying
"DOWNLOAD MODE!
Do not turn off.
It takes about 10 minuites."
or it will have a symbol of a phone connecting to a "!" next to a computer symbol.
I can no longer use this phone if anyone can help me it would be very much appreciated.
Thanks.
hahaha to funny bricked means it no longer turns on meaning you don't even get the download mode. its just like a useless brick. But anyways to the problem at hand, there is only one way to brick the omnia and that is if you flash the eboot which you have not done since it still works and turns on.
Unplug from USB cable and turn it of and/or take out the battery. Put the battery back in and plug it into your PC and try to update it with PC studio and see if it works it should not have an issue. Repeat the steps if it fails but this time start PC studio first and then plug in the omnia and see if that works.
If all else fails you need to get OCTANS and download the official firmware for your region or a custom firmware if you want. I'm assuming you have a I8000 which OCTANS is used to flash don't know if that is the case with other omnia 2 as well. Visit this site and look for OCTANS and all the firmware you need. Since you are flashing anyways i would recommend you flash JD3 ROMS so you have the latest. Either go official ROM or go Lite i myself am using tw2 lite ROM.
I went to that site and nothing on there says anything about "OCTANS" so could you possibly give me a link of some sort to what I need.
I've tried running PC Studio on XP and Vista with no luck on getting the computer to even see the phone anymore so I've just about given up on the whole thing.
heavywater said:
I went to that site and nothing on there says anything about "OCTANS" so could you possibly give me a link of some sort to what I need.
I've tried running PC Studio on XP and Vista with no luck on getting the computer to even see the phone anymore so I've just about given up on the whole thing.
Click to expand...
Click to collapse
Here is the Octans Downloader's latest version. Just run it (If you are using Windows Vista or 7, set compatibility mode to Windows XP SP2), select the appropriate parts in various slots, click Detect Device and then turn off and plug your phone into usb cable. It will detect the phone, then just press Start and wait for the process to complete.
In addition to these steps, you might also need to update activesync drivers and install Samsung CDMA Modem drivers if you are using Windows 7 or Vista. For more details, see this thread :
http://www.modaco.com/content/b7610-omnia-pro-b7610-modaco-com/299070/tut-flashing-rom-using-octans/
I hope you get back your phone soon!
Good luck and Cheers!
same problem - cannot flash: the phone is stuck with an image of a mobile device, a pc, and a (!) sign in between.
unable to hard reset, unabe to flash - octan does not detect the phone...
any chance to save my phone?
1. get the ROMs from modaco site.
2. Start Octans and follow the ROM update guide in modao.
3. Click detect in Octans.
4. Power off phone (remove battery and insert back in ur case).
5. connect phone to PC/laptop (do not use any usb hub).
6. u shd see the download button becomes ungrey. click it to flash.
the download button remains grey......
what OS are u using?
If it's vista or win 7 and whether it is 32bit or 64bit.
The solutions are at modaco.
i read modaco.
the device is stuck: when i turn it on, the screen shows only one image:
an image of a mobiel device, a pc, and in between a (!) sign.
cannot hard reset device, cannot do anything.
am using vista, and followed all protocol from modaco (first time was able to flash - thats how the device got bricked).
octans (or the pc) does not detect the device when i connect it to the - that is the problem...
OK I now have installed the CDMA drivers and i'm running OCTANS in XP SP2 mode what OS should I download to use with the phone and how big will it be?
Thanks so much for the help guys.
And btw is there any versions that will keep the samsung virtual keypad and things like that (not the damn cube though)?
like i menchioned get a lite ROM I use tw2 ROM's Garys are good to. I like tw2 ROM because they are totally stipped ROMS except for samsung dialer and SMS and he gives cabs of all the apps so people can restore what they use. Garys is also very nice lite ROM with the basic apps that mainly everyone uses. Its your choice really what you want you can install the JD3 stock ROM as well, but why? when these lite ROM's giuve you more RAM.
As for drivers you may need to search on the site i don't have the links because there are new updated drivers for windows 7 which should work on vista too. When using octans make sure to hit detect and then plug in the phone (phone must be off) then click start. You only need to flash the PDA unless other parts messed up during the update, you won't know till you flash.
Driver installation:
1.) Turn off Phone
2.) Plug into PC
3.) Let it install the default drivers
4.) Go into device manager
5.) Go under the phone menu
6.) Update drivers and follow the steps and when asked which location point to the driver you just downloaded.
flash i8000
PROBLEM-HEPL pls..
cannot flash: the phone is stuck with an image of a mobile device, a pc, and a (!) sign in between!
unable to hard reset, unabe to flash - octan does detect the phone, but flash phone image and error (the end)
octan write: [Setup:0] PDA Device removed.
[Setup] Windows XP
[Setup] Download Ram Size :41777920 bytes,(39 MB)
OnDeviceChange \\?\USB#VID_04E8&PID_6619#5&ed04620&0&4#{25dbce51-6c8f-4a72-8a6d-b54c2b4fc835}
[Down] CSC Image.
[Down] MoviNAND Image.
[Down] Phone Image.
[CSC:0] Download start 0x0
[CSC:0] ----------------- Information of Multi CSC Image ------------------
[CSC:0] Verision:[I8000ATOIJ8]
[CSC:0] SalesCode:[ATO]
[CSC:0] Priority:[0x1]
[PDA:0] LANG_ID:[7][0405]
[Phone:0] Download to 0x0
[Phone:0] StartOffset: 0
[Phone:0] EndOffset: 16777216
[MOVINAND:0] Download start 0x0 and all!! :-(
I have win 7 32bit..driver install from modaco..octans (setting XP service pack3), restart..but cannot flash..HELP please? Soory, my bad english...
I have a s 2 i flashed a Lightening rom XWEK7 and it worked fine all day until a hour ago when my phone froze and restarted it self and now it wont recognize being plugged in it will go into download mode on the phone but still wont come up on the computer end. And is currently not going past the screen that says " Samsung Galaxy S 2 GT - 19100 and the yellow triangle at the bottom.
Need help ASAP as is my work phone.
The main thing is you can get into download mode. Get stock firmware from here if your carrier is listed, if not get country specific firmware here and flash that in Odin.
Edit - I just re-read your post & realised your PC won't recognise your phone. Uninstall/reinstall Kies so you have the drivers in place for Odin to recognise the phone (drivers might be corrupt ?). Make sure you kill off Kies in task manager before you attempt to flash stock firmware in Odin. If you find the PC still won't recognise your phone try a different USB cable/different USB ports (I know there's only one port on my laptop Odin works on), failing that try a different PC/different version of Windoze. And if all that doesn't work, you might want to try Heimdall. Search the forum, plenty of posts on how to use it (never used it myself so I can't guide you in the use of same).
http://forum.xda-developers.com/showthread.php?t=1449771
Follow this, and the phone will live again
Hey guys just wanted to say thanks for all the help you provide on a daily basis, for all the people trying to unlock the potential in their phones. However with that being said I might have tried too hard and messed up my phones. I have a Samsung Vibrant SGH-T595 with 2.1 (update 1) updated officially by Samsung.
I rooted the phone, used clock work recovery mod and then downloaded and installed cyanogenmod 7.1 RC. However in the end I did not like so I tried to go back using my backed up copy created by clockwork mod. Doing this has now what you would call "soft bricked" my phone.
The phone is currently stuck on the Samsung boot screen when trying to power on the device. I am unable to put it into download mode via the three button setup, but I bought a USB jig and it sets it into download mode.
Everything seems great at this point but the Odin program is unable to recognize my phone. I have downloaded the official Samsung Kies, and 64 bit drivers as well for my windows 7 system but it is unable to detect my phone. I believe it maybe a defective USB issue with this phone but not sure since it can be charged through USB but I can't remember the last time I was able to connect it to the PC and transfer files via the USB cable.
My question is what else can I do other then sell it for scrap?
Try another USB cable and different ports. It will recognize it eventually.
As you have a windows 7 x64 bit version i guess Odin may need to be opened by giving Administrator permissions.
Try right clicking odin and click Run as administrator. I guess this should work.
Ran into this issue last night with my wife's Nook Color and moving some file and driver issues. Guess what? It was a bad cord. Actually used my Vibrant cord and it was instantly recognized. Yes sometimes it IS actually THAT simple.
I also suggest you go to the Dev section and download the AIO Toolbox (links are live again and don't forget the .Net files too). Uninstall the drivers you have installed and run to toolbox. It has all the correct drivers, pit/tar files and Odin. It is an invaluable tool.
Sidenote: Kies is notorious for hardbricking devices. You should stay away from it altogether.
Woodrube said:
Sidenote: Kies is notorious for hardbricking devices. You should stay away from it altogether.
Click to expand...
Click to collapse
Exactly. And that is how i tried updating my vibrant to froyo and ended up hard bricking it..
Yeah like someone in here said, download aio vibrant toolkit.. its a surefire way to know your drivers are good and right.. once youve ruled them out, try a diff usb port and cable (mentioned above as well). If nothing works, then you may begin to entertain the idea that your phone is in difficult position.
Probably not hardbricked tho, vibrants are very resilient; just keep trying.
Then ttheres jtag and unbrickable mod if youre absolutely sure lifes over
Sent from a cell tower to the XDA server to you.
Thanks guys I ended up recycling my phones cause nothing I did worked. I did try AIO toolbox got the drivers, tried different cables. My SG II is able to be recognized by odin 1.85 with no issues but not my vibrant. I believe it is an issue with the vibrant's usb port. I originally rooted it by doing the update.zip fix from its external sd card, did not use my usb cable at that time. My other vibrant is completely hard bricked since it wont power on with two different fully charged batteries. Anyway thanks again and next time I will research more before modding my phones.
Hey OP,
I did the same exact thing as you and soft bricked it in the same manner. Then when I tried to get Odin to recognize the phone it wouldn't with my Samsung cable. I thought I was out of luck but I went and bought a USB cable made my Belkin from Meijer and Odin recognized it! I looked at the Samsung cable and the Belkin cable and the black plastic inside the microUSB in the Belkin is thicker than the Samsung. I think that helps create a tighter contact between phone microUSB and the cable. I thought I was screwed like you and I fixed the issue with a new cable!! That simple
I used the Samsung Galaxy S II usb cable which looks like it has a very tight connection with the contacts like you said. Thanks anyway I will try that brand of cable, if I ever run into that issue.
Hi guys, I need some help with my Samsung Galaxy S3 GT-I9300.
A couple weeks ago my phone turned off by itself and never turned on completely again. If I turn it on, it stays on the very first boot screen forever (the white text saying Samsung Galaxy S3 GT-I9300, like this one (https://cdn-images.xda-developers.com/direct/1/1/5/2/1/9/8/I9300.bootlogo.jpg).
I've removed the SIM card and the MicroSD card with no effects whatsoever, and I've also left the device turned on for hours but it always stays on the same screen.
I cannot enter recovery mode (it just shows the boot screen mentioned above) but I can enter download mode. At download mode, I get this info:
ODIN MODE
Product name: GT-I9300
Custom binary download: No
Current binary: Samsung Official
System Status: Oficial
As you can see, I have never flashed a custom rom (or rooted or even unlocked the bootloader). This is what intrigues me the most, since everybody I've seen with the same problem had trouble during or after a flash.
My last OS version was 4.3.1 and it was received OTA months ago.
In the past few months, my device rebooted out of nowhere, even when I was not using it. Occasionally, it had the stuck power button, which caused it to reboot on a loop, but I always solved it by nudging the power button a little. I don't know if these two previous problems might have caused the problem I'm facing now, but they're not showing up anymore.
Anyway, I've tried to flash the newest official rom (NK1 - ZTO) via Odin but I always get a NAND Write error.
I've tried changing USB ports, USB cable and computers; tried Odin 3.04, 3.07 and 3.09; tried Samsung USB drivers v1.5.45 and 1.5.49 but nothing of the above made any difference.
Today things started getting worse, though. In the past, Windows would always recognize the device on at least one specific USB port; Odin would also recognize the device and then I would get the NAND Write error. Now, Windows will not recognize the device no matter the cable, USB port or driver version. I only get a unknown device error and Odin won't recognize anything connected.
I tested all my setup with a working Galaxy S3 I9300 and it got recognized every single time, no matter the USB port, the cable or the computer.
Considering that another device is getting recognized by different computers, I suppose that the problem lies in my Galaxy S3.
So, can anyone offer me any kind of advice or point me in any direction on how I can try to fix my phone? Is my phone physically dying and no software solution will unbrick it?
Your power button issue has corrupted/damaged the nand memory. Try the dead boot recovery thread in general forum but unless you have warranty you might be better off with a new phone.
I was afraid of that.
I checked the post you mentioned but it seems I'd have to buy tools and hardware more expensive than the phone itself, so I'd rather buy a new smartphone.
Thanks for the help!
Guys I have already rooted my sgs3 and used many other roms. but few months earlier i put 4.3 stock rom to my device.
even now my phone is getting detected via odin(when it is turned on) and kies. But when i put it into the download mode phone isnt getting detected by odin. what i actually need to do it install custom recovery and root this device.
but now framaroot is not working and i have tried many other apks. please help me out
SLDarKprince said:
Guys I have already rooted my sgs3 and used many other roms. but few months earlier i put 4.3 stock rom to my device.
even now my phone is getting detected via odin(when it is turned on) and kies. But when i put it into the download mode phone isnt getting detected by odin. what i actually need to do it install custom recovery and root this device.
but now framaroot is not working and i have tried many other apks. please help me out
Click to expand...
Click to collapse
Aren't you just missing some drivers? Maybe try to reinstall them: http://forum.xda-developers.com/showthread.php?t=961956
Also make sure to allow drivers to interact with your device if anything prompts while in Odin.
Android Debugging activated?
blint6 said:
Aren't you just missing some drivers? Maybe try to reinstall them: http://forum.xda-developers.com/showthread.php?t=961956
Also make sure to allow drivers to interact with your device if anything prompts while in Odin.
Click to expand...
Click to collapse
Have you tried installing Sammy's USB driver?
And I'm presuming the device IS on download mode already (I don't believe it appears on Odin while on normal mode)
1. yes i have already installed drivers and phone is detecting via KIES and ODIN when it is turned on.. it suddenly disconnect whenever i put into download mode.
2. yep usb debugging is activated...
3. Im using 4.3 stock rom.. arent there any other way to root this device without pc .. coz i checked lot of forums but none helped me..
4. my pc - windows 10. but i dont think that it will be a issue coz it's detected when it's turned on (means not using download mode).
SLDarKprince said:
1. yes i have already installed drivers and phone is detecting via KIES and ODIN when it is turned on.. it suddenly disconnect whenever i put into download mode.
2. yep usb debugging is activated...
3. Im using 4.3 stock rom.. arent there any other way to root this device without pc .. coz i checked lot of forums but none helped me..
4. my pc - windows 10. but i dont think that it will be a issue coz it's detected when it's turned on (means not using download mode).
Click to expand...
Click to collapse
Bumping Up this thread since i have really same issue, as in literally the same.
Anyone can help me/us?
xaiury said:
Bumping Up this thread since i have really same issue, as in literally the same.
Anyone can help me/us?
Click to expand...
Click to collapse
mate you have to try a different PC or a port. I have fixed my issue using another PC
Download vroot PC Latest Version VRoot 1.7.8
http://www.vrootdownload.com
Downloading mode only..
I have tried 10000000000000000000000000000 tips tricks and almost everything in this and other websites.. but there is no solution for this:
I have GT-I9300 Pathetic galaxy SIII and since I tried flashing recovery to this it goes into download mode... and its been there ever since.. i have downloaded 32 different kind of drivers claiming Samsung drivers.., buying and trying 8 different USB Cables, formatted my laptop 3 time in order to get it detected by ODIN 3.04 to 3.12... or kies or Smart switch.. working on this piece of crap since 3 weeks day and night but getting nowhere,... If any one knows a way to get it fixed... EVEN IF IT NOT DETECTED BY ODIN OR KIES.
PLZ HELP....
Gr8mobiPro said:
I have tried 10000000000000000000000000000 tips tricks and almost everything in this and other websites.. but there is no solution for this:
I have GT-I9300 Pathetic galaxy SIII and since I tried flashing recovery to this it goes into download mode... and its been there ever since.. i have downloaded 32 different kind of drivers claiming Samsung drivers.., buying and trying 8 different USB Cables, formatted my laptop 3 time in order to get it detected by ODIN 3.04 to 3.12... or kies or Smart switch.. working on this piece of crap since 3 weeks day and night but getting nowhere,... If any one knows a way to get it fixed... EVEN IF IT NOT DETECTED BY ODIN OR KIES.
PLZ HELP....
Click to expand...
Click to collapse
Relax.. I understand how frustrating it can be.
I need a detail explanation of what you did to get it into that state and what you've tried. A bullet point list will suffice. I just need to know so I can work out how buggered it is and where to go from here.
I need to know which PC operating system you're using, which variant of s3 you have including its region (this can be determined by the sticker in the battery compartment unless you already know.
There is a possibility it is your os not detecting the device because of drivers but if you've tried formatting and starting over then it shouldn't have any issues. The only other option is to manually edit the drivers ".cat" file with the s3's actual physical address before installing the drivers, but this is in extreme circumstances when the os is not "playing ball".
Also remove kies or at least stop all of its running processes when using odin.
My advice at this stage is to manually remove all drivers from the pc OS regarding the s3 and wait until we figure out where the s3 is at. I have a gdrive with some useful stuff that I know works on Windows XP flawlessly. https://drive.google.com/folderview?id=0B4vTiHTBB629ZW5vQndpbjFnblk
One question though.. When you pull the battery out and reinsert it. Does the phone automatically boot to download mode, is it stuck there permanently or does it boot loop?.
Beamed in by telepathy.
shivadow said:
Relax.. I understand how frustrating it can be.
I need a detail explanation of what you did to get it into that state and what you've tried. A bullet point list will suffice. I just need to know so I can work out how buggered it is and where to go from here.
I need to know which PC operating system you're using, which variant of s3 you have including its region (this can be determined by the sticker in the battery compartment unless you already know.
There is a possibility it is your os not detecting the device because of drivers but if you've tried formatting and starting over then it shouldn't have any issues. The only other option is to manually edit the drivers ".cat" file with the s3's actual physical address before installing the drivers, but this is in extreme circumstances when the os is not "playing ball".
Also remove kies or at least stop all of its running processes when using odin.
My advice at this stage is to manually remove all drivers from the pc OS regarding the s3 and wait until we figure out where the s3 is at. I have a gdrive with some useful stuff that I know works on Windows XP flawlessly. https://drive.google.com/folderview?id=0B4vTiHTBB629ZW5vQndpbjFnblk
One question though.. When you pull the battery out and reinsert it. Does the phone automatically boot to download mode, is it stuck there permanently or does it boot loop?.
Beamed in by telepathy.
Click to expand...
Click to collapse
1st of all I want to thank you bro for reply...
Now..
I am using Windows 10 64bit, using Samsung galaxy sIII GT-I9300 Indian single sim varient.
I rooted it using KingoRoot successfully but I found I wasn't able to get SuperSU and without that I was not able to use root fun properly so I tried to flash the same with flashFire.. it failed as it require SuperSU. So I tried installing TWRP recovery from playstore and it started flashing and after reboot, It stuck on the Downloading mode.. No matter how many buttons I tried pushing combined it stuck on downloading mode...
I tried almost all method on YouTube and websites but it still don't work. Worst thing .. I tried fixing the same by Kies as well as ODIN but .. I never detect my phone.. when i connect my phone after uninstalling and Or installing the samsung driver and Kies as well.. windows didn't recognise it.
I am about to give up n this and almost ready to smash the phone with wall hammer and throw it under my car tyres but I committed myself not to do that before 14th May.
The problem is most likely Windows 10 64bit. I'm quite sure the drivers don't agree with them.
You're going to have to find an older OS and try it. Either use a virtual machine or dual boot and load up a real OS like XP. Then we can begin the proper problem solving. I hate putting percentages on things but I'm 90% confident that windows 10 is an issue here, mainly for the fact it is 64bit and the drivers aren't made for that.
As for button combo's if they don't work while booting and it goes straight to download mode then there is a big problem and it could be bricked. You can try holding just the power button for about 15 seconds while in download mode and it "should" attempt to reboot. If not then as I said, big issue ahead.
No matter what you need to get it seen by odin so get yourself xp somehow and use the stuff on my gdrive. You need to get yourself a copy of the latest firmware for your phone, ready to flash via odin should you get it to see the phone.
Beamed in by telepathy.
Windows 10 to win7
shivadow said:
The problem is most likely Windows 10 64bit. I'm quite sure the drivers don't agree with them.
You're going to have to find an older OS and try it. Either use a virtual machine or dual boot and load up a real OS like XP. Then we can begin the proper problem solving. I hate putting percentages on things but I'm 90% confident that windows 10 is an issue here, mainly for the fact it is 64bit and the drivers aren't made for that.
As for button combo's if they don't work while booting and it goes straight to download mode then there is a big problem and it could be bricked. You can try holding just the power button for about 15 seconds while in download mode and it "should" attempt to reboot. If not then as I said, big issue ahead.
No matter what you need to get it seen by odin so get yourself xp somehow and use the stuff on my gdrive. You need to get yourself a copy of the latest firmware for your phone, ready to flash via odin should you get it to see the phone.
Beamed in by telepathy.
Click to expand...
Click to collapse
I have moved to windows 10 to win7.. and tried all over again (in the process to downgrade the same i formatted by all drive.. thanks to my idiot brother)..
i tried all the same thing again but still no luck..
now trying windows XP 32 bit in virtual machine.
i will let you know..
and i am thinking to hand it over to samsung service center.. lets see what they can do?
Gr8mobiPro said:
I have moved to windows 10 to win7.. and tried all over again (in the process to downgrade the same i formatted by all drive.. thanks to my idiot brother)..
i tried all the same thing again but still no luck..
now trying windows XP 32 bit in virtual machine.
i will let you know..
and i am thinking to hand it over to samsung service center.. lets see what they can do?
Click to expand...
Click to collapse
If you can afford to have them look at it then it's up to you but you will be billed for it as the s3 is out of warranty. They haven't made the s3 for about 3 years now.
Beamed in by telepathy.
shivadow said:
If you can afford to have them look at it then it's up to you but you will be billed for it as the s3 is out of warranty. They haven't made the s3 for about 3 years now.
Beamed in by telepathy.
Click to expand...
Click to collapse
I know.. hopefully it will be done under my expectation.. or last thing I know to donate the same to hammer and trash bin :cyclops: