Related
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
ID:COM =0:[COM4]
i know its in wrong section but q&a gets no love lol
Neither will this thread in the wrong section... Q&A gets no love because you tools never post in it, and of you do it's something so simple that five minutes of reading rectify most of those issues
Sent from my SGH-T959 using XDA App
If you use vista or windows 7 open odin by right clicking and run as administrator. Then put phone in dl mode and connect it.
Sent from my SGH-T959 using XDA App
5:38 you posted this in the QA
5:52 you posted this in the Dev forum (wrong one)
You where right the first time.
Did you:
Read the stickies (both the general and Dev sections)
http://forum.xda-developers.com/showthread.php?t=771111
http://forum.xda-developers.com/showthread.php?t=732458
Do a search here
http://forum.xda-developers.com/search.php?searchid=49162361
Do a google search
http://lmgtfy.com/?q=Odin+cant+open+com+port
Dont take it as people here are just being mean or rude to you. The general feeling is if you don't try to help yourself first (search, read, search again) then why should they?
Its best to identify what you think the problem is, then explain what you have read (done) to try and fix it.
Hope it helps
Moped_Ryder said:
5:38 you posted this in the QA
5:52 you posted this in the Dev forum (wrong one)
You where right the first time.
Did you:
Read the stickies (both the general and Dev sections)
http://forum.xda-developers.com/showthread.php?t=771111
http://forum.xda-developers.com/showthread.php?t=732458
Do a search here
http://forum.xda-developers.com/search.php?searchid=49162361
Do a google search
http://lmgtfy.com/?q=Odin+cant+open+com+port
Dont take it as people here are just being mean or rude to you. The general feeling is if you don't try to help yourself first (search, read, search again) then why should they?
Its best to identify what you think the problem is, then explain what you have read (done) to try and fix it.
Hope it helps
Click to expand...
Click to collapse
yeah im pretty tech savy... i posted this because i havnt seen any posts anywhere regarding com ports.. i self trouble shooted and figured out all i had to do was switch usb ports... also i got to a screen that was not recovery or download mode and i have never seen anyone talk about that either.. i figured out odin and flashed successfully pretty quick ...
im just as bad as most of u and hate when ppl dont research but im on this forum almost 12 hours a day and i hadnt seen anything that i had yet but i figured it out on my own and idk what the hype is because odins easy as pie!
/thread
The COM port number typically doesn't matter as the PC will assign one, IF you have the drivers installed properly and the device is in Download mode. If both factors are present, you'll see a little yellow box light up in ODIN indicating the COM port assigned. If you're still experiencing this error, then it is likely as someone else has said that you're using Windows 7 or Vista and need to run ODIN as an administrator.
Actually it did matter com 4 would not work I switched usb ports and then it said com5 and worked perfectly
Sent from my SGH-T959 using XDA App
Bricked Phone?
This is a solution I found to work on my own GS4. The Verizon Update Utility seems to be able to restore a phone without any problems. However, if you are in a Soft-brick situation all of your data will most likely be erased (which is why we are told to backup so much). I looked all over the place for the Upgrade Assistant online since you can't access it from your phone if it's bricked, so I figured I could post it here and hopefully help someone out who has a bricked phone.
Instructions:
Install the Upgrade Assistant and SAMSUNG USB Drivers
Put your phone in Download mode
Connect to your computer (allow driver detect on Windows)
Open the Upgrade Assistant
Go to Repair Assistant
Press Start
Wait: the Process should take anywhere from 30-90 minutes (because it downloads the Stock 1.6ish gb rom)
In the Zip file you will find:
The Verizon Upgrade Assistant (PC/MAC)
Samsung USB Drivers
These files come directly from the stock ROM on the GS4
Hope it helps!
EDIT: The Mac Software installs great, however the Windows software doesn't seem to be working for me. So if you can get it to work thats awesome!
Please note: this is not my software and is only the software of it's respective owner. I do not claim for it to be mine, I am only posting a link so as it can be used to help.
Keep in mind that if youre on MDK this will probably up you to ME7... and lock your Booyloader.
If on MDK and you brick your device, I would ask around for assistance to manually unbrick
Sent from my SCH-I545 using xda app-developers app
PetrichorXFi said:
Keep in mind that if youre on MDK this will probably up you to ME7... and lock your Booyloader.
If on MDK and you brick your device, I would ask around for assistance to manually unbrick
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Hi Guys
I've googled the internet soooo hard trying to find this file attached at the first post of this thread but sadly the attachment is gone
I've spent hours trying to find a download link but sadly i couldn't find any at all!!
so please please please, can someone re-upload it for me and everyone out there looking for it.
Thank you guys !
flashbolt said:
Hi Guys
I've googled the internet soooo hard trying to find this file attached at the first post of this thread but sadly the attachment is gone
I've spent hours trying to find a download link but sadly i couldn't find any at all!!
so please please please, can someone re-upload it for me and everyone out there looking for it.
Thank you guys !
Click to expand...
Click to collapse
You need to take more Google jujitsu classes lol. If you search the name of the zip on Google it's the first link that comes up
Yaaaay xD!!
joshm.1219 said:
You need to take more Google jujitsu classes lol. If you search the name of the zip on Google it's the first link that comes up
Click to expand...
Click to collapse
i already did that xD
googling again with ur keyword, please wait....
yes i see what u meant, but all the link are not available/downloadable
that's why i had to ask u, i think this is my first time to ever ask something in any forum hehe, i've never been this stuck in my life xD
but sadly I've lost all my chakara xD
anyway it seems that even if i did find it i won't be able to install it, the reason why is like below
1- i remembered i had a note 3 verizon, i attached it, copied the vzw software assistance.exe and all files related
2- tried to install it from my local harddrive copy, nothing would lunch or pop-up
3- backed it up as *iso and mounted it, still got nothing lunching or popping up when i try to open the *exe
4- connected my note 3 and lunched it from the phone and it directly pop up an agreement message with "install" button,
one must be connected to the internet when installing
so after all it turns out without a verizon device connected and used to install it, one cant use the software unless it's already installed
so i thought i'd share this info for anyone who wants
anyway thank you for your time and help =D
unbricking my note 2 sch-i605 ongoing.. xD
wish me luck =d
i'll post this just for information
so after i have soft bricked my phone to a brick that cannot be fixed through odin i managed to fix it with the verizon software repair
the error i have faced was that everytime i try to flash any rom or anything to sch-i605 verizon note 2 phone it will return an erorr messag sayong
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
so after installing Verizon software assistant and connecting my phone to it, it have completely repaired my phone :victory:
tip: u have to install "Verizon software assistant" from a working Verizon phone only, you can't install it from copied files.
Thanks for all you provide XDA Dev's !!!
The software might be too outdated, I can't get it to run. It keeps force closing on my mac. It won't even launch in windows, I found a report of a user that had removed the samsung signature on the file with launching success, but even that didn't work for me. Lol I'm just going to have to wait for the stock rom to download so I can Odin it
Same situation here - I am stuck with the phone telling me to run Verizon Software Repair Assistant. and that does not work on Windows 10. I was able to remove the digirtal signature. I have the task manager running and the app does appear to launch but gets closes right away. Stuck phone - please help....
Just an update for those who care. I had success with windows 10. I plugged in a working verizon phone to get the upgrade assistant which has the repair assistant in it. It installed without a hitch. It wouldn't recognise my phone until I manually put it in download mode. Took about 7 mins to repair with fiber internet.
Sorry folk, can't install software.
Any help?
Running Windows 7 x64, drivers installed.
Regards
Recovere said:
Bricked Phone?
Instructions:
Install the Upgrade Assistant and SAMSUNG USB Drivers
Put your phone in Download mode
Connect to your computer (allow driver detect on Windows)
Open the Upgrade Assistant
Go to Repair Assistant
Press Start
Wait: the Process should take anywhere from 30-90 minutes (because it downloads the Stock 1.6ish gb rom)
EDIT: The Mac Software installs great, however the Windows software doesn't seem to be working for me. So if you can get it to work thats awesome!
Please note: this is not my software and is only the software of it's respective owner. I do not claim for it to be mine, I am only posting a link so as it can be used to help.
Click to expand...
Click to collapse
Working file FOUND!!!
Thanks for the info and initial file OP. Unfortunately, the zip is out of date and does not install on any version of Windows I have tried.
I have tried Windows 7 64 bit and 32 bit, as well as windows XP 32 bit. The assistant did not open in any of these versions of windows.
I found a working file...
Direct download link (as of 11/3/2016) for the repair assistant from Samsung's website:
http
://support
-us.samsung.com/VerizonSoftwareUpdateWin/
I was directed to the above download link from this Verizon web page. You can find any needed instructions on using the tool there.
https
://www
.verizonwireless.com/support/knowledge-base-80201/
Here is the Verizon page for the Software Upgrade Assistant:
https
://www
.verizonwireless.com/support/knowledge-base-80200/#windows
Hi Guys,
I have the following problem:
I have an Samsung Galaxy SII and have never flashed anything on it, just did Upgrades via KIES to 4.1.2 (I think). It´s not branded by a Telekom Company or anything. Just a stock Phone from Samsung.
A few days ago I used that phone, put it into my pocket and after 2 hours when I wanted to use it again, it was stuck on the boot logo (you know the Galaxy GT9100 .... Screen)
If I have the power cable attached it just displays an empty battery and the circle is NOT "circling". Battery symbol is not getting "full"
Now I can´t get into the recovery mode BUT I can get into the download mode.
I already tried to Flash with ODIN but it always gives me an error like this:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> zImage
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Honestly I don´t care about the phone. I just want the data from my phone.
Does anyone have an idea?
Well you won't be getting any data of the phone unless you get it to boot/function normally, so first thing's first. Search for Hopper8's 'Odin troubleshooting' thread. Try the stuff in his thread until the phone successfully takes an Odin flash.
Hmm. How about you flash CWM on it and make a backup of the Stock ROM with it?
Sent from my GT-I9100 using XDA Premium 4 mobile app
seems like its bricked it self.. mYbe an emmc failure.. i got my s3 with the same problems.. tried everythng but nothing work.. send it to samsung and they tell me that motherboard replacement are the only solution.
lawong said:
seems like its bricked it self.. mYbe an emmc failure.. i got my s3 with the same problems.. tried everythng but nothing work.. send it to samsung and they tell me that motherboard replacement are the only solution.
Click to expand...
Click to collapse
Nah, I think he's just missing something while flashing via odin.
Sent from my GT-I9100 using XDA Premium 4 mobile app
but his issue are same as mine, except mine fails at odin with 'cant find any partition'
Hahaha, no partition is a screwed mobo definitely!
Sent from my GT-I9100 using XDA Premium 4 mobile app
lawong said:
but his issue are same as mine, except mine fails at odin with 'cant find any partition'
Click to expand...
Click to collapse
yeah , that s3 was a victim of exynos SDS ..
Gee there's been an awful lot of unfounded assumptions made in this thread over the past 15 minutes
lawong said:
seems like its bricked it self.. mYbe an emmc failure.. i got my s3 with the same problems.. tried everythng but nothing work.. send it to samsung and they tell me that motherboard replacement are the only solution.
Click to expand...
Click to collapse
just curious but isnt the emmc limited to 4.0.4 ?
Going through the hoppers guide now
Alright I can do whatever I want. Odin always Fails at the NAND write step.
Which means one of two things:-
1) I don't know how much of Hopper's thread you read, but I'm fairly sure he makes the point that fixing cases like these is often a matter of persevering. You keep trying stuff until it works. The first 11 flash attempts might not work, but for whatever reason the 12th works. You can keep doing that if you want, or it could be
2) The NAND really is borked. If that's truly the case, then yes, only a motherboard replacement is fixing it (either a new one by a service centre or a 2nd hand one by you/a local mobile repair shop), and you can kiss goodbye any chance of recovering data from the phone.
Now, if it was my phone, I know what I'd be doing before I gave up & declared it a case of option 2 (but YMMV, obviously).
MistahBungle said:
Which means one of two things:-
1) I don't know how much of Hopper's thread you read, but I'm fairly sure he makes the point that fixing cases like these is often a matter of persevering. You keep trying stuff until it works. The first 11 flash attempts might not work, but for whatever reason the 12th works. You can keep doing that if you want, or it could be
2) The NAND really is borked. If that's truly the case, then yes, only a motherboard replacement is fixing it (either a new one by a service centre or a 2nd hand one by you/a local mobile repair shop), and you can kiss goodbye any chance of recovering data from the phone.
Now, if it was my phone, I know what I'd be doing before I gave up & declared it a case of option 2 (but YMMV, obviously).
Click to expand...
Click to collapse
right, so is the storage fixed on the Mainboard and not a seperate module (like harddrives in Computers)?
So in case I switch the Mainboard I cannot take the old storage to the new Mainboard.
Correct.
MistahBungle said:
Correct.
Click to expand...
Click to collapse
not good
I am still trying here ...
phone can be fixed my booting to recovery mode and factory resetting the phone
OOORR
if u just want the data flash siyah kernel via odin and boot to recovery mode
go to mounts and storage
mount usb storage while phone connected to pc
Sent from my GT-I9100 using xda premium
iamtalha said:
phone can be fixed my booting to recovery mode and factory resetting the phone
OOORR
if u just want the data flash siyah kernel via odin and boot to recovery mode
go to mounts and storage
mount usb storage while phone connected to pc
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thanks for your answer but you lost me a little here.
As I wrote the recovery mode isn´t working at all. Only the download mode.
Already tried flashing the siyah kernel but still no difference in phone behaviour.
What exactly do you mean with "mount usb storage while phone connected to pc"?
When I connect the phone to the pc, Windows always tells me that there is a device that can´t be recognized (don´t know the exact error message) and that leads to no access to the phone by the Windows Explorer, Kies, ...
if the data in the phone is not much important than try this its my own fix.
http://forum.xda-developers.com/showthread.php?t=2400535
Sent from my GT-I9100 using xda premium
Hi all,
A classmate of my son has a bricked GPS 4.2 (YP-GI1CW/XEN). Another classmate tried to root it. But it got wrong.
By reading and searching guides here, i have rooted some htc phones and succesfully tried several roms, so i offered to take a look.
I did not know this player before and i dont know what happened to it. The only think my son has heard is: someone rooted it, installed a rom, made it empty again, searched for the right software (rom), but could not find it.
When we got the phone it only showed the logo of galaxy S2. There is no sd-card inside.
I spend hours of reading, finding the download mode (3-button), odin, heimdall, kies etc.
Tried everything, but can't get it done
Could anyone please help me?
Download method works
The 3-button method works and gets the player in download mode.
Info on screen: (WITHOUT usb connection!)
Odin mode
Product name: YP-GI1
Custom binary download: yes (13 counts)
Current binary: custom
downloading....
do not turn off target!!
Click to expand...
Click to collapse
I tried and maybe did stupid things
I have tried heimdall and kies. Kies does not see the player. Heimdall does, but it did not work or i could not work with it.
Installed and uninstalled Heimdall following their textfile.
I unstalled Kies also. Cleaned up my computer. Updated java. Used ccleaner. etc. Removed unused devices, with 'device remover'
Once or twice i clicked the "re-partition" in odin. With or without PIT-file. Now I read, that this could brick your phone. :silly:
I tried all tabs, now i know i should only use the PDA-tab.
I might have done more stupid things.
I found "one-click" in http://forum.xda-developers.com/showthread.php?t=1153310
It took me a while before seeing that not all things where good for this player type. When rooting htc, a wrong rom won't brick your phone, so i did not take it too seriously.
I tried 1 or 2 roms, before seeing that they where for other player versions.
I tried the GalaxyPlayer-Bootloader.zip from http://forum.xda-developers.com/showthread.php?t=1386669
Now i see it is specially for player 5.0.
Here i also used the partition file.
At last i did:
Installed samsung usb drivers again: "SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.33.0.exe"
From: http://forum.xda-developers.com/showthread.php?t=961956
When connecting the player to the computer (while already in download mode), windows start 'downloading' the samsung drivers again...
Dont know why and if this can be a problem.
Tried ADB in command, but 'adb devices' does not give a list, but odin seems to work at first.
Odin (3 v3.07) recognizes it and says:
<ID:0/010> Added!!
and: "0:[com100]"
Now in Odin I first uncheck ALL checks like: repartition, auto reboot and refresh time and the others.
I did try the "NAND ERASE" option. Erasing looks to hang, but at last Odin comes back and gives a fail on flashing.
Between every odin try, I remove the battery, unconnect usb and restart the download mode, then connect again, then start Odin again.
Now I tried 3 roms/kernels:
- CWMStockGI1 kernel.tar (http://forum.xda-developers.com/showthread.php?t=2198444)
- yp-gi1cw.factoryfs.rooted.tar (http://forum.xda-developers.com/showthread.php?t=1884071)
- yp-gi1cw.kernel.stock.tar (http://forum.xda-developers.com/showthread.php?t=1884071)
Odin responds when flashing:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> normalboot.img
<ID:0/010> NAND Write Start!!
Click to expand...
Click to collapse
Then nothing.....
On unconnecting:
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
Click to expand...
Click to collapse
I am out of options
Please help. :crying:
Stop before you actually brick it!!!
STOP EVERYTHING RIGHT NOW!!! First thing's first, this is a samsung device and not a HTC device. You screw up flashing this with the wrong device rom and you are screwed. right now, you are lucky in that the state of the device is currently in the state of what is called a softbrick or download only. you need to get stock files for this exact device, preferably able to be used with odin. then after that you can focus on rooting the device. honestly, dont touch the device right now, post a fourm under q and a asking for who has stock recovery files for a 4.2 international version, (i am guessing that you have the international version due to what your location is set as.) once you get those, then flash them with odin. then once it is working again, you can use this exploit to root it.
http://forum.xda-developers.com/showthread.php?t=1312859&highlight=rooting
good luck.
Thanks for your reply.
I was indeed aware that i should not touch the player, until i got feedback
Though I am a bit suprised that flashing a wrong rom could get me into a hard brick.
I will look for the recovery software you mentioned or ask for it.
joly said:
Thanks for your reply.
I was indeed aware that i should not touch the player, until i got feedback
Though I am a bit suprised that flashing a wrong rom could get me into a hard brick.
I will look for the recovery software you mentioned or ask for it.
Click to expand...
Click to collapse
in terms of the recovery images, your going to need to ask someone with a 4.2 to get them off of theirs and send them to you. odin and hemidall are avaiable in the galaxy player all in one forum at the top of the development page.
interms of the wrong image hard bricking a device, it is possable with samsung devices (i've done it once before and have learned to be carefull). Most samsung galaxy player roms not only contain the rom, but also a kernel. if a kernel that was not made for your device is flashed on to it. it might as well be a hard brick because with out a jtag box, you will never get it working again.
I hope you are able to obtain the files and i wish you the best of luck.
I am trying to flash the Stock ROM on my Galaxy S3 i9300. Constantly I am getting this Error.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME.tar.md 5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Note:
1)Device GT-i9300
2)I can ONLY goto the Download Mode.
3)Using Original Data Cable.
**this is "a last port to call" this is the last thing you should try**
Try flashing this via recovery: https://drive.google.com/file/d/0B4vTiHTBB629d2syOEV1MkdmTjg/view?usp=drivesdk
Then flash your stock rom via odin.
Beamed in by telepathy.
Try different USB cables and USB 2.0 ports.
potatoknight8 said:
I am trying to flash the Stock ROM on my Galaxy S3 i9300. Constantly I am getting this Error.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME.tar.md 5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Note:
1)Device GT-i9300
2)I can ONLY goto the Download Mode.
3)Using Original Data Cable.
Click to expand...
Click to collapse
Another EMMC brickbugged i9300. Unless you replace the EMMC chip on the PCB, your phone is kaput. Or get another motherboard. And don't even think about getting your stuff back. They're either done for or locked because what EMMC brick bug, as the name suggests, it's a bug of a specific batch of EMMC chips that after some number of IO operations or some other condition, it just locks, leaving only the first part of the EMMC working, < 1 megabyte in my researches. In reality, your EMMC is not done with, it could be accessed IF you have a device which can reset the EMMC controller or something like that.
Or just flash a .pit file for your device model and capacity, something like i9300 xxg.pit, replacing the xx with the capacity of the EMMC, 16, 32 or 64 gigabytes.
---------- Post added at 20:17 ---------- Previous post was at 20:16 ----------
shivadow said:
**this is "a last port to call" this is the last thing you should try**
Try flashing this via recovery: https://drive.google.com/file/d/0B4vTiHTBB629d2syOEV1MkdmTjg/view?usp=drivesdk
Then flash your stock rom via odin.
Beamed in by telepathy.
Click to expand...
Click to collapse
There is no pit and you suggest flashing a bootloader? Non, non, non, you're wrong. And the man said he can ONLY ACCESS DOWNLOAD MODE. Read before you post.
---------- Post added at 20:19 ---------- Previous post was at 20:17 ----------
audit13 said:
Try different USB cables and USB 2.0 ports.
Click to expand...
Click to collapse
Don't think so.
I have been flashing the captivate, s2, s3,s4,s5, note 1, note 2, note 3, note 4, etc. for several years and have often revived the "no pit partition" error when using incompatible it USB cables and ports.
If using the original USB cable doesn't work, try flashing with a pit file.
In my experience flashing a pit file will 9 times out of 10 doorstop the device. Flashing that bootloader "might" allow the emmc to reset, or it may doorstop the device. So, the choices are your way (90% chance of killing it) or my way (50% chance of killing it).
So logically thinking me chose not to reveal the ultimate killing method just yet. I also presumed that the ol' cable and port routine was already done seeing as he already has a response from the device.
I also presumed that after doing some research on the matter before I suggested it that, seeing as many other people have reported that it has fixed a no pit condition on "thought to be dead" devices, it would be a better option than attempting the said ultimate device killing option.
I also believe that there is a method for flashing the bootloader via download mode should a minor amount of research be done on Google.
So, it would be better if YOU did the research before commenting instead of coming out with useless, degrading, ignorant, self righteous, arsehole (full of s**t) posts like yours before taking random potshots at people who have actually spent a couple of years with the device in their hand and are still learning new things to this day. Maybe a more constructive comment like "you missed the bit where he can only get to download mode, maybe he could use the .tar version".. But no. Too much..
Beamed in by telepathy.
I am getting the exact same error in Odin while Flashing the Stock ROM.
西村大一 said:
Another EMMC brickbugged i9300. Unless you replace the EMMC chip on the PCB, your phone is kaput. Or get another motherboard. And don't even think about getting your stuff back. They're either done for or locked because what EMMC brick bug, as the name suggests, it's a bug of a specific batch of EMMC chips that after some number of IO operations or some other condition, it just locks, leaving only the first part of the EMMC working, < 1 megabyte in my researches. In reality, your EMMC is not done with, it could be accessed IF you have a device which can reset the EMMC controller or something like that.
Or just flash a .pit file for your device model and capacity, something like i9300 xxg.pit, replacing the xx with the capacity of the EMMC, 16, 32 or 64 gigabytes.
---------- Post added at 20:17 ---------- Previous post was at 20:16 ----------
There is no pit and you suggest flashing a bootloader? Non, non, non, you're wrong. And the man said he can ONLY ACCESS DOWNLOAD MODE. Read before you post.
---------- Post added at 20:19 ---------- Previous post was at 20:17 ----------
Don't think so.
Click to expand...
Click to collapse
Thanks for an Honest answer and making me lose my **** :laugh:
shivadow said:
**this is "a last port to call" this is the last thing you should try**
Try flashing this via recovery
Then flash your stock rom via odin.
Beamed in by telepathy.
Click to expand...
Click to collapse
Well Sir i don't have access to Recovery Mode.I can only goto Dowonload Mode.
audit13 said:
Try different USB cables and USB 2.0 ports.
Click to expand...
Click to collapse
Yes sir i have tried Three Samsung Original Data Cables and two different Laptops with Different Operating Systems (Win 10,Win 8.1).
:crying:
shivadow said:
In my experience flashing a pit file will 9 times out of 10 doorstop the device. Flashing that bootloader "might" allow the emmc to reset, or it may doorstop the device. So, the choices are your way (90% chance of killing it) or my way (50% chance of killing it).
So logically thinking me chose not to reveal the ultimate killing method just yet. I also presumed that the ol' cable and port routine was already done seeing as he already has a response from the device.
I also presumed that after doing some research on the matter before I suggested it that, seeing as many other people have reported that it has fixed a no pit condition on "thought to be dead" devices, it would be a better option than attempting the said ultimate device killing option.
I also believe that there is a method for flashing the bootloader via download mode should a minor amount of research be done on Google.
So, it would be better if YOU did the research before commenting instead of coming out with useless, degrading, ignorant, self righteous, arsehole (full of s**t) posts like yours before taking random potshots at people who have actually spent a couple of years with the device in their hand and are still learning new things to this day. Maybe a more constructive comment like "you missed the bit where he can only get to download mode, maybe he could use the .tar version".. But no. Too much..
Beamed in by telepathy.
Click to expand...
Click to collapse
Edit: you're suggesting flashing a bootloader and then a stock ROM, and then vo on to say that MY advice with flashing a .pit, which by the way, IS MISSING, can killi it? And where did you get those numbers? 50 per cent, 90 per cent? Don't mess with me, KILLING OPTION? Go tell that to the Samsung Service Centre in Tokyo, they will laugh at you. Spare me of this please, and don't bother to quote this post, i will not provide further assistance, happy bricking devices, no, "fixing" devices. Oh, and I solved an efs problem some time ago on my i9305, everything was ok, serial no, imei, but no network. Found a backup, extracted it and flashed it dirrctly through ADB with the dd command. Working like new since then.
I guess you have YEARS of experience in flashing devices. Ok. But i might want to get gour attention to remove the last paragraph and show what part of my post was "useless", "degrading" or "self righteous" before starting to throw accusations around. I try to help here, so please, I have had Android devices in my hand, rooted, flashed stock and custom ROMs since the days of the Galaxy Mini. I have even revived many low end Mediatek devices with "irrecoverable" errors, and have a part time job at a GSM service here. Why didn't YOU tell him what to do if you are so HIGH and MIGHTY that you can't take another opinion but your own. And every time someone came into the GSM store i worked with a Samsung device with those symptoms, it was an eMMC brickbugged device which could not be recovered. I have tried bootloaders, pit files, cables, ports, machines, laptops, you name it. None worked. I even desoldered the eMMC and tried to access it via some instructions i found online. Nada. Nothing. So please stop talking like you know everything. I don't and have never said I know anything. FIN
Guys lets not let this turn into a flame war please, ALL OPINIONS are welcome and we also welcome debate but keep it polite please. Just because someone has a different opinion to you doesn't give you the excuse to be rude.
I'm surprised no one has suggested trying kies/smartswitch emergency firmware recovery btw, If i only had download mode that would be my first port of call
Regards
Sawdoctor
sawdoctor said:
Guys lets not let this turn into a flame war please, ALL OPINIONS are welcome and we also welcome debate but keep it polite please. Just because someone has a different opinion to you doesn't give you the excuse to be rude.
I'm surprised no one has suggested trying kies/smartswitch emergency firmware recovery btw, If i only had download mode that would be my first port of call
Regards
Sawdoctor
Click to expand...
Click to collapse
Hello there Sir could you be more specific about kies/smartswitch emergency firmware recovery.
Sorry I'm a noob.
:|
Some older phones are not supported by Smartswitch so you would need to use Kies.
http://www.samsung.com/us/smart-switch/
Download and install Kies first. Once installed, there is an upgrade/recovery under the options.
If your phone is not supported by Kies, try SmartSwitch.
Good luck.
Remember, we were all newbies at one point.
西村大一 said:
Edit: you're suggesting flashing a bootloader and then a stock ROM, and then vo on to say that MY advice with flashing a .pit, which by the way, IS MISSING, can killi it? And where did you get those numbers? 50 per cent, 90 per cent? Don't mess with me, KILLING OPTION? Go tell that to the Samsung Service Centre in Tokyo, they will laugh at you. Spare me of this please, and don't bother to quote this post, i will not provide further assistance, happy bricking devices, no, "fixing" devices. Oh, and I solved an efs problem some time ago on my i9305, everything was ok, serial no, imei, but no network. Found a backup, extracted it and flashed it dirrctly through ADB with the dd command. Working like new since then.
I guess you have YEARS of experience in flashing devices. Ok. But i might want to get gour attention to remove the last paragraph and show what part of my post was "useless", "degrading" or "self righteous" before starting to throw accusations around. I try to help here, so please, I have had Android devices in my hand, rooted, flashed stock and custom ROMs since the days of the Galaxy Mini. I have even revived many low end Mediatek devices with "irrecoverable" errors, and have a part time job at a GSM service here. Why didn't YOU tell him what to do if you are so HIGH and MIGHTY that you can't take another opinion but your own. And every time someone came into the GSM store i worked with a Samsung device with those symptoms, it was an eMMC brickbugged device which could not be recovered. I have tried bootloaders, pit files, cables, ports, machines, laptops, you name it. None worked. I even desoldered the eMMC and tried to access it via some instructions i found online. Nada. Nothing. So please stop talking like you know everything. I don't and have never said I know anything. FIN
Click to expand...
Click to collapse
You missed the bit where I "didn't say" you were wrong about the brickbug but if you've tried everything why suggest a known defunct method aka pit file knowing that it won't work.
If you came here for an argument you need to give your head a wobble, you won't get one. I couldn't care less who you've worked for or been with, you know jack about my background which "could" be more than yours.
So "Mr HIGH and MIGHTY", I say that because the bully always projects their insecurities on others as you have, no one said who was better than anyone so I suggest you climb down out of that Ivory tower before someone knocks it down around you. "no more fixing bricks" blah blah.. That is a PERFECT example of how much of a whiny little tart you are. Grow up and grow a pair of balls. "High and mighty".. D**khead comment that m8. Your true colours are showing.
Your personal interaction skills leave "A LOT" to be desired.
** waits for the post that says "tried flashing a pit file and now the device is dead"**.
Beamed in by telepathy.
@shivadow @西村大一 @audit13
Use Z3x flasher, forget Odin!.It happened to me,exactly we had the same situation..Finally I just flashed stock firmware and recovered.
Is Z3x flasher free?
Thread cleaned up.
Please don't talk about cracked versions here on XDA. It is considered as Warez.
The XDA Rulesforum.xda-developers.com/announcement.php?a=81 #6 clearly states
6. Do not post or request warez.
If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit members to request, post, promote or describe ways in which warez, cracks, serial codes or other means of avoiding payment, can be obtained or used. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community.
Click to expand...
Click to collapse
Now let's get the thread back on topic.
Regards
Vatsal,
Forum Moderator.
potatoknight8 said:
Well Sir i don't have access to Recovery Mode.I can only goto Dowonload Mode.
Click to expand...
Click to collapse
same with me sir, when powered on normally it goes to a white screen. sometimes with multicolored dots. I also tried flashing with pit files only and pit files with the roms but no luck.
Is there any other way to revive this phone? Kies tries to connect but never completes connection, suggesting to reboot the device then all the same thing happens. It would really be a big help and I know that many will benefit if and when someone will have a clear solution. Cheers to the XDA community!!!