Hi to all, guys, I need your help in this situation: I try to install CWM on S5830i thru flashing zip from SD, after flashing my phone take reboot, after this I got black screen. I wait approx 10 minutes, and then try to enter recovery mode (power+home+vol up) - nothing, I got black screen again. I try to enter ODIN mode (power+BOTH volume keys), with sucsess, so I understood that the only way to rise up my phone is USB flashing. I download all needed drivers and ODIN v1.85 (also I try to connect them with ODIN 4.38, but he cant se phone even with manually writing COM port). So, I download stock firmware S5830iXXKK5.tar, put tis file on PDA and begin flashing. I got this:
<ID:0/003> Added!!
<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)
It was surprised me, because I read that there is no needed PID file for stock firmware. I try google PID for my phone, but with no result.
If you have any ideas how rise up this dead phone to ANY firmware, please help. Thanks a lot.
i´m not really sure about what difference between generic gt-s5830 and gt-s5830i, but did u use correct ops file? i mean the cooper.ops file.
the ops file define correct partition layout, and if u use incompatible ops that will result in a whole lot mess including bricking.
So you need Odin 1.85,drivers and here's the PDA file for Odin.
http://www.4shared.com/file/Ls2CAsHv/PDA.html
an0nym0us_ said:
i´m not really sure about what difference between generic gt-s5830 and gt-s5830i, but did u use correct ops file? i mean the cooper.ops file.
the ops file define correct partition layout, and if u use incompatible ops that will result in a whole lot mess including bricking.
Click to expand...
Click to collapse
i-series have other processor and video accelerator. http://forum.xda-developers.com/showthread.php?t=1459479
ickyyy said:
So you need Odin 1.85,drivers and here's the PDA file for Odin.
Click to expand...
Click to collapse
I try your PDA file, but have the same error, could you pls see screenshot?
varvsn said:
I try your PDA file, but have the same error, could you pls see screenshot?
Click to expand...
Click to collapse
why u use that odin? does gt-s5830i really need to use that odin?
afaik odin v3.xx or v4.xx that we regularly use doesnt have that pit tabs, intead we use ops.
moreover if u really need to use that odin, why is the pit tabs empty? its obvious by the pit error in the log that it cannot find pit file. lol
an0nym0us_ said:
why u use that odin? does gt-s5830i really need to use that odin?
afaik odin v3.xx or v4.xx that we regularly use doesnt have that pit tabs, intead we use ops.
moreover if u really need to use that odin, why is the pit tabs empty? its obvious by the pit error in the log that it cannot find pit file. lol
Click to expand...
Click to collapse
If you read again my first post:
(also I try to connect them with ODIN 4.38, but he cant see phone even with manually writing COM port)
So if you explain, why older version is working fine instead of 4.38, or take me some ideas, how I can use "right" ODIN, it will be great.
PIT = where you should place your .ops probably
varvsn said:
If you read again my first post:
(also I try to connect them with ODIN 4.38, but he cant see phone even with manually writing COM port)
So if you explain, why older version is working fine instead of 4.38, or take me some ideas, how I can use "right" ODIN, it will be great.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=23460922&postcount=9
EmoBoiix3 said:
PIT = where you should place your .ops probably
Click to expand...
Click to collapse
no pit's are not same as ops if i am not wrong.. other sammy devices do use pit..high end ones.
madman_amit said:
http://forum.xda-developers.com/showpost.php?p=23460922&postcount=9
no pit's are not same as ops if i am not wrong.. other sammy devices do use pit..high end ones.
Click to expand...
Click to collapse
.pit = All those with custom binary counter
.ops = All those with no custom counter
EmoBoiix3 said:
.pit = All those with custom binary counter
.ops = All those with no custom counter
Click to expand...
Click to collapse
cool ..
thats why sammy makes them locked down
madman_amit said:
http://forum.xda-developers.com/showpost.php?p=23460922&postcount=9
no pit's are not same as ops if i am not wrong.. other sammy devices do use pit..high end ones.
Click to expand...
Click to collapse
Great.. Is it mean, that my phone becomes useless break?
varvsn said:
Great.. Is it mean, that my phone becomes useless break?
Click to expand...
Click to collapse
someone will have to make pit file for your device thats the thing..
Can someone do this, guys?
Related
Hello everyone...
I have a Galaxy SII HD LTE (SHV-E120L).
History:
The phone worked fine for 1 day, except a minor issue with sending sms. I am a total noob, however I decided to flash the TL 1.3 firmware to solve that issue. Someting went wrong in that process so, stupid as I usualy am, I started to play with the checkboxes of Odin. Result: a hard bricked 1/2 month salary worth phone
I found a JTAG shop who manage to "repair" the phone. all works fine except I cant connect to a mobile network. I did a firmware upgrade via Kies and received an error with the baseband upgrade.
The emergency recovery also ends in an error after 97% upload.
All the different firmware I try to flash via Odin gets an error when flashing the amss.bin (Complete(Write) operation failed. (see picture).
Here's the Odin error:
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> boot.img
<ID:0/013> NAND Write Start!!
<ID:0/013> recovery.img
<ID:0/013> system.img.ext4
<ID:0/013> amss.bin
<ID:0/013>
<ID:0/013> Complete(Write) operation failed.
So the problem I have is:
- I can' connect to a mobile network.
- I can't flash other firmware
Am I right to say that I have a corrupt Modem - Radio - Baseband in the phone?
I know a little bit of Linux so I checked the filesystem with ADB Shell.
Can I delete certain files or change permissions or upload files from another phone to repair it?
What would you do in my place? I realy need someone to point me in the right direction. Thanks
---------------------------------------------------------------------------
The versions installed are:
Baseband: E120L.EL21.O843.LT
Kernel: 2.6.35.11-E120L.FB05.0938.CL939741
Build: GINGERBREEAD.FB05
---------------------------------------------------------------------------
No one can help me?
gs2 hd lte
did you try to flash other TL firmwares like the ics version or the GDphone one..? & make sure to find the right version for your phone E120L, not E120K or E120S; remembre that.
yakie47 said:
did you try to flash other TL firmwares like the ics version or the GDphone one..? & make sure to find the right version for your phone E120L, not E120K or E120S; remembre that.
Click to expand...
Click to collapse
Thanks for the reaction, yakie47...
I tried several firmwares beside TL (LGU+ HOME_E120L.FB05.0938_CL939741_REV00_user_low_ship, HOME_E120L.EL07.0011_CL718581_REV00_user_low_ship). Everytime Odin reaches amss.bin to flash, I get the - "Complete(Write) operation failed" - error.
I will now try the GDphone firmware and hope things will be better. I'll let you know later.
vdbergh, it seems that the problem for you is not firmware-related, but lies somewhere in the flashing process.
There're some point you may want to get before you flash the firmware, f.e.:
Do you use USB cable from the phone package?
Do you use USB port on motherboard rather than some external one?
Do you have any antivirus/firewall/any other security software disabled before flashing?
Additionally, you can try another USB port to connect the phone with.
rxulan said:
vdbergh, it seems that the problem for you is not firmware-related, but lies somewhere in the flashing process.
There're some point you may want to get before you flash the firmware, f.e.:
Do you use USB cable from the phone package?
Do you use USB port on motherboard rather than some external one?
Do you have any antivirus/firewall/any other security software disabled before flashing?
Additionally, you can try another USB port to connect the phone with.
Click to expand...
Click to collapse
Thank you for the sugestions Rxulan....
you are right that my problem is not firmware-related.
It is obvious now that it's related to the modem or baseband software, because I can flash everything except the amss.bin. What is amss.bin actually?
The phone is rooted, so is there anything I could check in the efs-directory or somewhere else?
Sould I send it back to Samsung for repair?
amss.bin is a part of modem software along with mdm.bin.
You can try ones from some stock firmware, just leave only those 2 files in the tar archive and flash the tar via PDA field.
You can download the latest firmware using Check Fus Downloader.
rxulan said:
amss.bin is a part of modem software along with mdm.bin.
You can try ones from some stock firmware, just leave only those 2 files in the tar archive and flash the tar via PDA field.
You can download the latest firmware using Check Fus Downloader.
Click to expand...
Click to collapse
I downloaded the latest stock firmware with Check Fus and left nlamss.bin and mdm.bin files in the tar. Flashing this with Odin gives the same error:
<ID:0/014> File analysis..
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Get PIT for mapping..
<ID:0/014> Firmware update start..
<ID:0/014> amss.bin
<ID:0/014> NAND Write Start!!
<ID:0/014>
<ID:0/014> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Help! 2 months later and still nowhere.
I can flash the boot.img, recovery.img, system.img.ext4, but not the amss.bin.
Conclusion: It's impossible to flash the modem software (amss.bin) into this phone.
Why?
What to do now?
That's weird really.
Conclusion: It's impossible to flash the modem software (amss.bin) into this phone.
Click to expand...
Click to collapse
It's definitely possible since I flashed FD03 modem onto FB05 official ROM myself.
rxulan said:
That's weird really.
It's definitely possible since I flashed FD03 modem onto FB05 official ROM myself.
Click to expand...
Click to collapse
Hi rxulan...
I've been digging a bit deeper... and have a little theory about my problem. I'm not sure but would like to have your opinion...
The modem software in my phone is corrupt.
All the firmwares I checked seem to have the same mdm.bin and amss.bin files.
Now I think that the mdm.bin file in all these firmwares are corrupt!
Why? When I try to extract the files from mdm.bin, all are ok except the amss.mbn file. Extracting that file gives me a "file is broken" error. And this happens with every firmware i tried.
Maybe you could see if you can extract the amss.mbn file from mdm.bin from your firmware?
So I think that if you're phone doesn't have a modem problem like mine, it doesn't extract the mdm.bin file from mdm.bin when flashing new firmware.
Does all this makes sence to you?
vdbergh
Well, that makes sense actually.
Try to download tar with FD03 modem software from here.
It's in russian, but it's ok, just resolve the captcha and click the green button.
EDIT: this tar can be flashed as is, no need to extract anything.
rxulan said:
vdbergh
Well, that makes sense actually.
Try to download tar with FD03 modem software from here.
It's in russian, but it's ok, just resolve the captcha and click the green button.
EDIT: this tar can be flashed as is, no need to extract anything.
Click to expand...
Click to collapse
Thanks for your help rxulan... I really appreciate this.
I downloaded the file, but flashing gives the same error as before.
When I look inside the mdm.bin file, the AMSS.MBN file is the same as in other firmware, and has the same problem of not beening able to be extracted.
(see pic)
Try for yourself and you will see that you can extract every file from amss.bin and mdm.bin except the AMSS.MBN file in mdm.bin.
That amss.bin is not needed really. It's probably just some 7zip issue with the bin package. What you need is amss.bin from the ROM directly, no need to extract anything from bin files.
So, you you did try to flash the tar given itself, without any modification, and it failed? That's really weird it can't flash amss.bin only.
No clue what can be the cause for now then. Are you sure it's not some antivirus software/etc?
Probably, it makes sense to try flashing from another computer?
rxulan said:
That amss.bin is not needed really. It's probably just some 7zip issue with the bin package. What you need is amss.bin from the ROM directly, no need to extract anything from bin files.
So, you you did try to flash the tar given itself, without any modification, and it failed? That's really weird it can't flash amss.bin only.
No clue what can be the cause for now then. Are you sure it's not some antivirus software/etc?
Probably, it makes sense to try flashing from another computer?
Click to expand...
Click to collapse
I know that I don't need to extract the .bin files, but flashing any firmware always results in error in amss.bin. I tried everything: reinstall drivers, other usb cables, other usb ports, other computer, all without result.
I am a total newbe in this but as far as I could learn, amss.bin has to do with the modem. And this is exactly the problem with my phone... I can't connect to a wireless network after JTAG hard brick recovery.
When I googled futher then I found that the AMSS.MBN file has to do with the Qualcomm baseband chip.
Now, it could be a coincidence, but I find it very strange that it's exactly this file (AMSS.MBN) that is impossible to extract. All other files in the .bin file are ok.
So I know that it's strange but I think that the amss.mbn file of all the firmwares are equal and corrupt.
The only thing I see that I can still try is to take the amss.mbn (/system/etc/firmware/amss.mbn) file from another E120L and copy it into mine.
Would you be so kind to send me this file from your phone?
No problem, here it is.
rxulan said:
No problem, here it is.
Click to expand...
Click to collapse
Thank you so much rxulan....
This file came form your phone and not from a firmware file?
It was the last thing I could come up with, but it doesn't solve my problem. I don't know anymore what to do.
Yes, this file is right from the phone.
Probably, try to update firmware with Kies? Will emergency firmware recovery work?
rxulan said:
Yes, this file is right from the phone.
Probably, try to update firmware with Kies? Will emergency firmware recovery work?
Click to expand...
Click to collapse
I tried Kies before, but that doesn't work. In firmware information I have "Your device does not support software upgrade via Kies"
Try the following. If your phone is rooted, you must have Root explorer installed.
Run Root explorer, then go to /system folder. Choose R/W permissions for the folder (see the appropriate Root explorer button in header). Long tap on build.pro file, then scroll menu down and choose to open the file in the text editor.
then change the FB05 part of ro.build.PDA value to EL22. Then tap on the phone menu button and choose save and exit. Reboot the phone and connect to Kies.
You should have firmware upgrade option available now.
rxulan said:
Try the following. If your phone is rooted, you must have Root explorer installed.
Run Root explorer, then go to /system folder. Choose R/W permissions for the folder (see the appropriate Root explorer button in header). Long tap on build.pro file, then scroll menu down and choose to open the file in the text editor.
then change the FB05 part of ro.build.PDA value to EL22. Then tap on the phone menu button and choose save and exit. Reboot the phone and connect to Kies.
You should have firmware upgrade option available now.
Click to expand...
Click to collapse
Thanks again!
I did as you explained and it worked. Kies started the upgrade but ended with an error (pic1). The emergency upgrade also ended with an error (pic2).
I have the feeling that the error is generated the moment the modem is flashed.
What could be the reason that this phone doesn't accept any updates? Could some files have the wrong permission (ro)?
A friend of mine over at a Swedish forum is having problems with his SGS3 i9300. His phone just died, completely random, and refused to boot. he can only boot to download mode, nothing else.
He tried flashing a stock nordic ROM, which failed since ODIN threw him a "there is no pit partition" message. He tried flashing various PIT files, but it all stops with "there is not PIT partition" He did not do anything to his device for this to happen, it just died on him and that's where it all started.
Shot in the dark, but has his NAND memory somehow crashed, which caused the error of not booting/not accepting PIT files?
Theshawty said:
A friend of mine over at a Swedish forum is having problems with his SGS3 i9300. His phone just died, completely random, and refused to boot. he can only boot to download mode, nothing else.
He tried flashing a stock nordic ROM, which failed since ODIN threw him a "there is no pit partition" message. He tried flashing various PIT files, but it all stops with "there is not PIT partition" He did not do anything to his device for this to happen, it just died on him and that's where it all started.
Shot in the dark, but has his NAND memory somehow crashed, which caused the error of not booting/not accepting PIT files?
Click to expand...
Click to collapse
Hi! It just happened to me today! In the morning I was using the phone - calling someone.
Then put it into my pocket, went to work, and there it was already at the boot page, and staying there when resetting.
Tried to flash with odin, and I get the same error message as your friend.
I had a stock 4.0.4 rom, never touched anything on the phone yet.....
Any idea from someone?
edit:
as i9000 has linked to newer firmware with everything in post bellow, so just use that.
http://forum.xda-developers.com/show....php?t=1825272
niches said:
Hi! It just happened to me today! In the morning I was using the phone - calling someone.
Then put it into my pocket, went to work, and there it was already at the boot page, and staying there when resetting.
Tried to flash with odin, and I get the same error message as your friend.
I had a stock 4.0.4 rom, never touched anything on the phone yet.....
Any idea from someone?
Click to expand...
Click to collapse
Return under warranty .
jje
JJEgan said:
Return under warranty .
jje
Click to expand...
Click to collapse
yeah, problem is I bought it from amazon.de so I have to send it then via Post :S
tumult said:
full firmware flash with pit, bootloader, tz, etc..
hooe the link still works, if not i can make mirror tomorrow
also check in Odias thread in original android development if pit for 16 & 32 is same, but as far as i remember it is.
ps. i have flashed this firmware (without pit, but it is safe to download , no viruses, etc).
hope it helps
Click to expand...
Click to collapse
Thanks, I'll try it when I arrive home from celebrating the 253rd birtday of Mr. Guiness
Theshawty said:
A friend of mine over at a Swedish forum is having problems with his SGS3 i9300. His phone just died, completely random, and refused to boot. he can only boot to download mode, nothing else.
He tried flashing a stock nordic ROM, which failed since ODIN threw him a "there is no pit partition" message. He tried flashing various PIT files, but it all stops with "there is not PIT partition" He did not do anything to his device for this to happen, it just died on him and that's where it all started.
Shot in the dark, but has his NAND memory somehow crashed, which caused the error of not booting/not accepting PIT files?
Click to expand...
Click to collapse
All ROMs have full set images of partitions and may be flash with pit and repartition, pit - attached...
http://forum.xda-developers.com/showthread.php?t=1825272
as i9000 said:
All ROMs have full set images of partitions and may be flash with pit and repartition, pit - attached...
http://forum.xda-developers.com/showthread.php?t=1825272
Click to expand...
Click to collapse
edit: i was wrong, all partitions are there.
when you say full partition, you mean sboot.bin and tz.img also? sorry, don't think so , but if so good to know.
that's why i posted link above, that was only full firmware I could find.. but maybe it's just me.
tumult said:
when you say full partition, you mean sboot.bin and tz.img also? sorry, don't think so , but if so good to know.
that's why i posted link above, that was only full firmware I could find.. but maybe it's just me.
Click to expand...
Click to collapse
You can watch attached screen, 9 images:
sboot.bin
param.bin
tz.img
boot.img
recovery.img
system.img
cache.img
hidden.img
modem.bin...
You upload link of ROM full service ROM for Russia...
Why swedish man csc ser, russian location?
all the more so very old...
as i9000 said:
You can watch attached screen, 9 images:
sboot.bin
param.bin
tz.img
boot.img
recovery.img
system.img
cache.img
hidden.img
modem.bin...
You upload link of ROM full service ROM for Russia...
Why swedish man csc ser, russian location?
all the more so very old...
Click to expand...
Click to collapse
and i said sorry if i missed it .. anyway, i will delete my link then as yours are uptodate.
tumult said:
and i said sorry if i missed it .. anyway, i will delete my link then as yours are uptodate.
Click to expand...
Click to collapse
should not be deleted link, and the Russian people attend the xda forum ...
tumult said:
edit:
as i9000 has linked to newer firmware with everything in post bellow, so just use that.
http://forum.xda-developers.com/show....php?t=1825272
Click to expand...
Click to collapse
this is all great, but I think that does not work, I have met with this diagnosis: "there is no pit partition"
INTERNAL MMC IS DEAD... ((((
I'm having a similar problem. Except mine is a GT-I9300. Odin gives me this error.
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006>
<ID:0/006> There is no PIT partition.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
TinyGrasshopper said:
I'm having a similar problem. Except mine is a GT-I9300. Odin gives me this error.
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006>
<ID:0/006> There is no PIT partition.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Hey all, I have exactly the same error message. Running cm10 and my phone just froze, after re-boot i'm stuck on boot screen, no recovery and can only enter download mode....HELP!!!!
Someone reported that they had success with flashing the CF-Root to gain CWM recovery back and then flashing DarkyROM from it. But I don't know if that is even true.
PjotrFias said:
Someone reported that they had success with flashing the CF-Root to gain CWM recovery back and then flashing DarkyROM from it. But I don't know if that is even true.
Click to expand...
Click to collapse
thanks for the reply, i tried it but to no avail :crying:
Where did it stop? The first part?
PjotrFias said:
Where did it stop? The first part?
Click to expand...
Click to collapse
yeah i got the no pit message, tried flashing the pit file but won't do it...
I've just received this error on my phone too, Has there been any progress on solutions to this?
Another problem is that I can get into download mode and my system status is "Custom", How will this effect a return to manufacturer?
alot of replies with this errors lately...u guys used any custom FW ?
Hi
Yesterday i rooted my Samsung Galaxy S2 i9100m VIA The zergrush exploit.
I Tried to flash CWM Via Odin and it did not work!
My phone will not access recovery and when turned on normally says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
I have tried flashing the bootloader, kernel, CSC, modem, and firmware several times but they always fail!
I tried to follow this guide here and it also did not work!
I can not think of what else to do so i have posted this thread here!
Thanks
*EDIT*
This is what originally ****ed me up: http://galaxys2root.com/galaxy-s2-r...ckworkmod-recovery-on-rooted-galaxy-s2-i9100/
if you read the comments everyone is having the same issue
*EDIT*
- What is the error you were getting in Odin=I have successfully flashed a pit file and when trying to flash my firmware it comes up with 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> factoryfs.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So it is failing at NAND Write Start!!
- Did you try to flash other recovery's? If yes, then which one= No but i am now
- Do you still have download mode= Yes
- Did you flash .pit files or re-partitoned= Yes i flashed the correct pit file and it succeeded
- What firmware were you on= I9100MKG2
- Did you reinstall the drivers= Several Times
- Tried different usb port / pc= Yes
- Did you try different cables= Yes
So I guess you've flashed a stock I9100M ROM via odin and failed too, right?
Sent from the little guy
gastonw said:
So I guess you've flashed a stock I9100M ROM via odin and failed too, right?
Sent from the little guy
Click to expand...
Click to collapse
Yes i have!
Flash custom kernel so you can get to recovery then.
And if you tried that too keep on flashing.
Hold on a sec, odin passes or fails?
Sent from the little guy
gastonw said:
Flash custom kernel so you can get to recovery then.
And if you tried that too keep on flashing.
Hold on a sec, odin passes or fails?
Sent from the little guy
Click to expand...
Click to collapse
It fails
Jenham said:
It fails
Click to expand...
Click to collapse
it fails
You gotta keep on trying. Trial & error.
Sent from the little guy
gastonw said:
So I guess you've flashed a stock I9100M ROM via odin and failed too, right?
Sent from the little guy
Click to expand...
Click to collapse
Updated
?
Got it working again?
Sent from the little guy
Jenham said:
Updated
Click to expand...
Click to collapse
Huh?
Sent from my digital submersible hovercraft.
You need to start giving more details if you want help...
- What is the error you were getting in Odin?
- Did you try to flash other recovery's? If yes, then which one?
- Do you still have download mode?
- Did you flash .pit files or re-partitoned?
- What firmware were you on?
- Did you reinstall the drivers?
- Tried different usb port / pc?
- Did you try different cables?
If you want help, I suggest you start giving us all the info that you can give us instead of saying "they always fail".
He's mute.
Sent from the little guy
Lennyz1988 said:
You need to start giving more details if you want help...
- What is the error you were getting in Odin?
- Did you try to flash other recovery's? If yes, then which one?
- Do you still have download mode?
- Did you flash .pit files or re-partitoned?
- What firmware were you on?
- Did you reinstall the drivers?
- Tried different usb port / pc?
- Did you try different cables?
If you want help, I suggest you start giving us all the info that you can give us instead of saying "they always fail".
Click to expand...
Click to collapse
Sorry about that and i have updated my thread!
Oh boy, did I just read that you used a .pit file and that the flashing failed? You do know that the flashing needs to succeed when you flash a .pit?
Did you use a .pit the first time when the flashing failed?
http://forum.xda-developers.com/attachment.php?attachmentid=1750999&stc=1&d=1361525591
Really should stay well away from .pit files man.... Reads like jtag or paperweight time.
Amen.
Sent from the little guy
gaosphappy said:
http://forum.xda-developers.com/attachment.php?attachmentid=1750999&stc=1&d=1361525591
Really should stay well away from .pit files man.... Reads like jtag or paperweight time.
Click to expand...
Click to collapse
Lol the pit succeeded
Take a long breath, and when I say long I mean LONG.
Sent from the little guy
Hi I'm in the exact same boat, My sgs2 wont reboot and wont go into recovery. Everytime I flash with odin I get failed. What can I do ? I can't even find the pit file to flash that. I'm getting really worried. Please help
sawdoctor said:
Hi I'm in the exact same boat, My sgs2 wont reboot and wont go into recovery. Everytime I flash with odin I get failed. What can I do ? I can't even find the pit file to flash that. I'm getting really worried. Please help
Click to expand...
Click to collapse
Check the phistachio thread.
Sent from the little guy
I am the owner of a Galaxy S3 i9300 and have the following problem.
The phone starts logo appears and stays GT-i9300.
I tried to write software with odin and not working. enter download mode but not recovery mode.
What happens?
ovid1u said:
I am the owner of a Galaxy S3 i9300 and have the following problem.
The phone starts logo appears and stays GT-i9300.
I tried to write software with odin and not working. enter download mode but not recovery mode.
What happens?
Click to expand...
Click to collapse
If I understand you well, you are able to get into download mode but not into recovery?
What does Odin tell you as error message?
chrismast said:
If I understand you well, you are able to get into download mode but not into recovery?
What does Odin tell you as error message?
Click to expand...
Click to collapse
Yes, only in download mode.recover mode does not work.
<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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
that the file can try flashing the corrupted by a bad download, try downloading another rom.
Looks like you are not following the instructions and are trying to repartition the phone .
jje
JJEgan said:
Looks like you are not following the instructions and are trying to repartition the phone .
jje
Click to expand...
Click to collapse
I tried other firmware with 3 files + pit
result:
http://imageshack.us/photo/my-images/842/i9300e.jpg/
Donate the dead phone to a developer .
jje
JJEgan said:
Donate the dead phone to a developer .
jje
Click to expand...
Click to collapse
to understand that it's "sudden death"?
who would want a donation like that? )
great
no, you ticked "repartition", which is against the instructions, thus killing your phone. apparently
I would take it xD
Did you try it on another computer? Other USB port? I had the same problem last year with a galaxy tab.
Sent from my GT-I9300 using xda app-developers app
JJEgan said:
Donate the dead phone to a developer .
jje
Click to expand...
Click to collapse
iWilliBlecha said:
I would take it xD
Did you try it on another computer? Other USB port? I had the same problem last year with a galaxy tab.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I tried to other computers .
he can do anything?
How Glebun allready said, uncheck "repartition".
cuthoo thou
Glebun said:
no, you ticked "repartition", which is against the instructions, thus killing your phone. apparently
Click to expand...
Click to collapse
when you add pit automatically tick "repartition". I do not think that would be the problem here.
http://forum.xda-developers.com/showthread.php?t=2091045
You have a faulty eMMC... Either send it to a samsung service center, or find one who can change the faulty eMMC
ovid1u said:
when you add pit automatically tick "repartition". I do not think that would be the problem here.
Click to expand...
Click to collapse
why did you flash a pit file anyway? if it doesn't work after a pit file flash, you killed it
Glebun said:
why did you flash a pit file anyway? if it doesn't work after a pit file flash, you killed it
Click to expand...
Click to collapse
Like i said donate the phone to a dev for future XDA development .
jje
Glebun said:
why did you flash a pit file anyway? if it doesn't work after a pit file flash, you killed it
Click to expand...
Click to collapse
I always flash using pit files, does it fail, then I will just revive it using my riff box. You can not kill it beyond repair with just a pit file, and certainly not I9300
Sendt fra min GT-I9505 med Tapatalk2
Ratata82 said:
I always flash using pit files, does it fail, then I will just revive it using my riff box. You can not kill it beyond repair with just a pit file, and certainly not I9300
Sendt fra min GT-I9505 med Tapatalk2
Click to expand...
Click to collapse
Not all can own that device and understand how it works. So for users like us flashing with re-partition ticked is pretty much killing the device. And why do even need to tick the re-partition everytime you flash? lol
Ratata82 said:
I always flash using pit files
Click to expand...
Click to collapse
why?
I tried to flash the stock Samsung firmware to the phone, because I wanted to see if I liked samsung's iteration of Jellybean. I got it to flash, (I thought), but now if I try and start it up, it boot loops. I cannot get into recovery mode, but it does get into download mode fine. Here's what it says on the ODIN screen:
ODIN MODE
Product Name: GT-I9300
Custom Binary Download: Yes (1 counts)
Current Binary: Samsung Official
System Status: Custom.
How can I get it to flash a stock ROM? I've tried ODIN, and it keeps on not working.
Nevermind. I apparently had a corrupt partition table. I had to flash the phone again using a *.pit file I downloaded from the internet, and check the boxes marked "Auto-Reboot", "Re-Partition", "F. Reset Time", "Nand Erase All", and "Phone Bootloader Update". Doing all of this, and adding the *.pit file along with the *.tar.md5 file from sammobile, I was able to get my phone back online. If anybody wants the *.pit file I used to fix the phone, I would be more than happy to upload it.
Please upload it. I know someone whose phone got this error and I suggested him everything but with no results. Are you using a 16 or 32 GB S3 ?
Sent from my GT-I9300 using XDA Premium 4 mobile app
Andr3y29 said:
Please upload it. I know someone whose phone got this error and I suggested him everything but with no results. Are you using a 16 or 32 GB S3 ?
Sent from my GT-I9300 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm on the 16GB model. I have attached the *.pit file that I used to restore my phone.
Thanks! I was talking about @windows07 .
HAVING THE SAME PROBLEM..Partition damaged.
k-semler said:
I'm on the 16GB model. I have attached the *.pit file that I used to restore my phone.
Click to expand...
Click to collapse
I am facing the problem as yours..my partition has been damaged.
I tried using the pit file you uploaded..but nothing happens after this:-
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
I have to unplug the cable after this since nothing happens..
can you please also tell me about the other files you used..like PDA, CSC, PHONE, Bootloader.....If possible please share the links of the same.
Thank you!
shasha9250 said:
I am facing the problem as yours..my partition has been damaged.
I tried using the pit file you uploaded..but nothing happens after this:-
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
I have to unplug the cable after this since nothing happens..
can you please also tell me about the other files you used..like PDA, CSC, PHONE, Bootloader.....If possible please share the links of the same.
Thank you!
Click to expand...
Click to collapse
I just used the file available from Sammobile available here: http://www.sammobile.com/firmwares/3/?download=26624
You did decompress the file, (take it out of the *.zip), before attempting to flash it, correct? Did you have all the checkboxes I said I used earlier? That will COMPLETELY wipe your phone. There will be nothing on it. It will restore the boot loader too.
If you have a removable MicroSD, I recommend removing it during the flash process, just to be safe. It's probably not necessary, but it can't hurt to take extra precautions.