Related
Hey I've searched for more help but I am stuck.........
So i got a samsung fascinate for verzion.
Ran the 'One click root' ,... I have superuser
currently on DI01 and want to get to DL09
I am now trying to install clockworkmod ....
following directions from here http://forum.xda-developers.com/showthread.php?t=788099
:::
Put phone into download mode.
-Turn off phone
-Pull battery
-Press vol down button while plugging into computer
-Should show a yellow triangle
Open odin on pc
-Odin should show a yellow bar with a com port showing that it detects your phone
Click "PDA" button and select the CWMrecovery.tar you downloaded earlier
Click start
I keep getting this error
<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)
I have rebooted my PC, tried different clockwork files [CWMrecovery.tar and CWMRecovery_DJ05_DL09.tar.md5]... searched here, read a lot of instruction, searched google and other fourms but I can not find any thing on the 'Can't open the serial(COM) port' error
i have tried with Debugging mode turned off and get the same error.
....anyone have any ideas to help?
I have flashed many roms, radios and programs to my current phone so I don't feel I am a complete noob, but this is frustrating me...I like to think I can figure most things out and this temporarily kicked my butt....and I don't like it
.
hhp_211 said:
Hey I've searched for more help but I am stuck.........
So i got a samsung fascinate for verzion.
Ran the 'One click root' ,... I have superuser
currently on DI01 and want to get to DL09
I am now trying to install clockworkmod ....
following directions from here http://forum.xda-developers.com/showthread.php?t=788099
:::
Put phone into download mode.
-Turn off phone
-Pull battery
-Press vol down button while plugging into computer
-Should show a yellow triangle
Open odin on pc
-Odin should show a yellow bar with a com port showing that it detects your phone
Click "PDA" button and select the CWMrecovery.tar you downloaded earlier
Click start
I keep getting this error
<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)
I have rebooted my PC, tried different clockwork files [CWMrecovery.tar and CWMRecovery_DJ05_DL09.tar.md5]... searched here, read a lot of instruction, searched google and other fourms but I can not find any thing on the 'Can't open the serial(COM) port' error
i have tried with Debugging mode turned off and get the same error.
....anyone have any ideas to help?
I have flashed many roms, radios and programs to my current phone so I don't feel I am a complete noob, but this is frustrating me...I like to think I can figure most things out and this temporarily kicked my butt....and I don't like it
.
Click to expand...
Click to collapse
Have you tried a different USB port? Also re-installing the drivers might work.
Hope it helps, Good luck.
Your drivers up to date?
Sent from my SCH-I500 using XDA App
Check the file you are trying to odin. I all but guarantee that you have a corrupt file on your hands.
EDIT:
To be a tad more specific:
Download the odin patch again two more times. Either make sure you can unpack the tar, check the corresponding md5sums, or simply look at the file byte sizes to see if two are identical. Odin really freaks out if you give it bad files.
That is a good thing! Far better that than flash bad data to your pda.
Swyped w/ XDA App. When in doubt, mumble.
uslacson1 said:
Have you tried a different USB port? Also re-installing the drivers might work.
Hope it helps, Good luck.
Click to expand...
Click to collapse
zachsx said:
Your drivers up to date?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Hey thanks for quick responses.
I currently have the 'Samsung_Mobile_USB_Driver_V1.3.550.0_SCH-i500_Fascinate.msi' Driver installed
I believe I had installed SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe before when I was trying to get it rooted.
I have not yet tried a different USB port... I will and get back to you...
soba49 said:
Check the file you are trying to odin. I all but guarantee that you have a corrupt file on your hands.
Swyped w/ XDA App. When in doubt, mumble.
Click to expand...
Click to collapse
I have downloaded 3 different times both files, so I don't know ????
different USB port ... same result...
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
soba49 said:
Check the file you are trying to odin. I all but guarantee that you have a corrupt file on your hands.
EDIT:
To be a tad more specific:
Download the odin patch again two more times. Either make sure you can unpack the tar, check the corresponding md5sums, or simply look at the file byte sizes to see if two are identical. Odin really freaks out if you give it bad files.
That is a good thing! Far better that than flash bad data to your pda.
Swyped w/ XDA App. When in doubt, mumble.
Click to expand...
Click to collapse
When you say odin patch I guess you mean the 'CWMrecovery.tar'
I can unpack it and I have a 'recovery.bin' and a 'zImage' inside the file.
both 5081 KB in every 'CWMrecovery.tar' that I have.
Weird. My old copy from Nov. 26 is 9.93MB (10,414,130 bytes). It contains zImage and recovery.bin, each 5,202,168 bytes. I must be wrong, then.
EDIT:
Just for sake of good practice, I did look up the md5 for that file and I did download it again, and they do match. There are a lot of ways to get MD5s, I used a program called digestIT 2004 to generate it.
http://goo.gl/HELdr
ecfeb7b1633786c1ae9dfb276bfeb231 CWMrecovery.tar
I had no problems downloading it, the hosting is good. It's highly unlikely that I was right about resolving your Odin error.
Sorry I can't be more helpful. I did this once way way back when and had no issues. I did have an issue with a modem.bin packed in a tar later on, and the errors looked a lot like what you are getting now, so I assumed it was the same problem. Thanks for humoring me, and good luck.
I'm a nub.. help..
So I've been trying to follow directions here, but I feel I'm missing something very simple... I cant even get this restore started, it keeps telling me "Invalid Image Type" when i select the CWMrecovery.tar file?? help??
it could be that Kies, or other application that uses USB connection is active.
Hi there!
I am desperate!
Can't root my new SG2!
Here is what comes in odin:
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
it freezes there and the phone stays in download mode forever.
I also used Gingerbreak 1.10 but it stays in epxloit phase forever...
The phone is baught in Greece, provider is Cosmote and Kernel is:
[email protected] #2
I cant root it!!!!
OK some more info.
It stays in Download mode forever. When I remove battery and start it it starts and boots fine (not rooted though)
Every method fails!
I even used the automated odin 185 process again failed and froze at zimage
I also downloaded the patched KF3 tar for my kernel, used odin in download mode, again frozen forever!
Nothing I can do!!!!
It doesn't seem like you read or followed any guide.
Go to the dev forum, cf-root thread and follow the instructions. Make sure you installed Kies to get the drivers and then close Kies and kill EVERY process in task manager that belongs to Kies. Now you can use Odin, according to the guide!
Sent from my GT-I9100
d3l1 said:
It doesn't seem like you read or followed any guide.
Much more fun if they totally fail to read any instructions and make it up as they go along .
jje
Click to expand...
Click to collapse
Instead of throughing accusations on people having problems try to be more helpful or dont post at all.
I was the owner of a Samsung Galaxy S and now a S G 2.
I am also the Head IT and the man responsible for a group of S.A. companies that have over 250 mobile connections.
I have rooted many devices before S G 2 (HTC mainly and a few S Galaxy S) and it's something I can do very easily thanks to the very helpful guides that exist here in this forum that even non-experienced users can very easily follow.
The S G 2 was the first phone to cause such a problem to me!
The answer to my problem has been found by me and it was no other than the USB ports I used.
For some reason they were stuck and when the process would begin at odin it would freeze at the zimage task and stay there forever. The Gingerbreak 1.10 doesnt seem to work anyway for my kernel.
After switching USB port for the third time the whole process completed successfully.
Installing a fresh Kies copy (I never use it but the usb drivers are there) was something I did even before receiving the phone from the post.
A different solution would be to use 32 bit O.S. because 64bit O.Ses have such problems in other devices as well (a week ago I tried jailbreaking an IPhone 4 and a thousand errors occured while trying to upgrade to 4.3.3. When I installed Itunes in XP everything was perfect and everything was done flawlessly)
So there u have it ppl if you get such error in rooting try switching usb port or use 32 bit operating systems.
S G 2 Rooted (d3l1 - JJEgan thanks for nothing I guess)!
With the lack of information you provided there was hardly anything to help you with. So I assumed and started explaining the basics. My fault if it offended you, it wasn't meant that way!
And it's correct to assume a software problem given the very little information in post 1 which mostly is forgetting to end the Kies processes causing Odin to hang/crash.
So maybe you should provide more information as to what can be ruled out, post 1 gives us nothing to rule out.
I admit that the information I gave could not make things clear on what my knowledge and my experience is. However if you wanted more info you could ask and I would be happy to provide. Your post was not that offending but the next one was...I found it very upseting asking for help and getting replies like that. Perhaps my lvl was unclear....but someone can always ask. Your post alone wouldnt bother me so much. I guess its the combo with the next one. Anyway no prob mate!
Sent from my GT-I9100 using XDA App
I am also the Head IT and the man responsible for a group of S.A. companies that have over 250 mobile connections
?????????????????????
So there u have it ppl if you get such error in rooting try switching usb port
Thats plastered all over the forum mate though i will agree that you need to use the search button and read a lot of disjointed posts to get a lot of information .
I apologise for putting in print my thoughts that you are an idiot .
jje
You are So pathetic... So my guess is that if from software point of view everything is perfect and u get the yellow COM signal in Odin and u have selected the correct patch for your Kernel and Odin starts fine and freezes at some point in a PC you have rooted several other phones your guess would be the usb port. Send me a CV and I will pass it to my boss so that you can take my job! Looking forward to it!
p.s. Find a girlfriend. A real one not Lara Croft. Might help u a bit and relax your mind!
Sent from my GT-I9100 using XDA App
Hey everyone, so I've been using a Cyanogenmod S2 for the past few months and everything was great.
Until recently it started to reboot by itself,
until one day when I woke up "Kernel panic upload mode" was on the screen.
I rebooted the phone,
and then was greeted with a black screen after the Samsung Galaxy S2 screen.
The buttons do light up, but nothing else could be done.
I entered download mode to flash a new firmware,
but then somehow it failed and then it says connect to computer to redownload firmware or something when I boot it on right now.
I can't get it to flash anything at all, whenever I use odin it gets stuck at setup connection,
I installed Kies but it doesn't recognize my phone as well, neither does my computer....
Need help. Desperately. :crying::crying::crying:
Can u enter cwm
Sent from my GT-I9100 using xda premium
stopro said:
Can u enter cwm
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
No I can't..
Can only enter Download mode
Then you need to flash a stock rom with Odin. You don't really have any other option.
MistahBungle said:
Then you need to flash a stock rom with Odin. You don't really have any other option.
Click to expand...
Click to collapse
<OSM> T989UVMC6_T989TMB_T989UVMC6_HOME.tar.md5 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> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
That's the problem, I can't seem to get Odin to flash no matter what, I've already tried different versions of Odin,
but they always end up with either this (failure) or stuck at setup connection..
Any ideas, please?
There's been many threads re: this issue on here over the past week listing the troubleshooting steps to go thru when Odin won't work, search for those threads (Immortalneo has listed them, go through his posts as a shortcut).
Edit - Hang on a minute, what model number do you have; what's the sticker on the phone chassis under the battery say ?
MistahBungle said:
There's been many threads re: this issue on here over the past week listing the troubleshooting steps to go thru when Odin won't work, search for those threads (Immortalneo has listed them, go through his posts as a shortcut).
Edit - Hang on a minute, what model number do you have; what's the sticker on the phone chassis under the battery say ?
Click to expand...
Click to collapse
I'm using a GT-i19100
I'm going through immortalneo's posts but so far nothing's up..
Am currently following this guide but to no avail, (no .pit file in the compressed .rar file) http://forum.xda-developers.com/showthread.php?p=40154030&highlight=+pit#post40154030
Edit: I think it's a GT-i19100G because I vaguely remember such a thing on the startup screen...
If you've got an I9100, why are you trying to flash firmware for T-989 ?? I suggest you go back to Samfirmware & get an I9100 stock rom for starters.
Ignore that guide; your phone isn't bricked. However, it may well be if you try & flash a PIT file (Although, if you've somehow flashed firmware for a different model including PIT, you may need to at some point. Just not yet). OK. This is the first & last time I'm posting this stuff for the next month:-
Stuff to try when Odin doesn't work
-----------------------------------
*Must run Odin as administrator in Windoze.
*Ensure Kies & all it's processes aren't running in Windoze task manager. Kill them if they are (choose 'kill process tree').
*Try different USB ports; you must be using a 'powered' or mainboard port.
*Try different USB cables (particularly the cable that came with the phone if you're not using it now)
*Try different versions of Odin (search on here/Google)
*Uninstall Kies, reboot, redownload & reinstall it, reboot, try the flash again.
*Check the rom/kernel you download for corruption. Programs like 7Zip, IZarc, WinRar, etc will allow you to 'test' the rom file you download. If there are any errors/any of the files fail the test, bad download. Try again/try downloading with a different internet connection if it keeps happening.
*Run Windoze Update.
*And if all this fails, try a different PC. And if it won't work first time on another PC, go thru the above steps on that PC.
Hello everyone ..
It could solve the problem? I am in a very similar, and have helped me a lot, but none of the options so far have been effective. I'm starting to resign myself to use it as a paperweight, but still have not lost hope.:crying:
Geeenie said:
I'm using a GT-i19100
I'm going through immortalneo's posts but so far nothing's up..
Am currently following this guide but to no avail, (no .pit file in the compressed .rar file) http://forum.xda-developers.com/showthread.php?p=40154030&highlight=+pit#post40154030
Edit: I think it's a GT-i19100G because I vaguely remember such a thing on the startup screen...
Click to expand...
Click to collapse
Stop Now :0 ! You are trying to install a T-Mobile T989 firmware.It's a Galaxy s2 too,but from T-Mobile.It's not the same.Search on Sammobile for an I9100 firmware,preferable Android 4.0.3 or 4.0.4.Of course it gives an error,because it's not the right firmware.
Now this thread is just fun!
Sent from the little guy
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!!!