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 ?
Related
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 had the latest 4.1.2 stock OTA installed via CWM and I wanted to unroot and go back to stock and that seemed to work fine.... I went to the old version VRALL4 and once rebooted it asked me to update OTA so I did and that was fine........ and it asked me to do it again for some reason and now I'm in a boot loop. The Galaxy note 2 logo flashes on the screen real fast and turns off over and over. I can only get into ODIN and not stock recovery. I've tried re-flashing the original odin package, and the pre-rooted odin packages and nothing is working.... what can I do? am i fux0rd? thx
edit: also USB all drivers are installed .......
Try a factory reset in the stock recovery. Then give it a whirl.
Sent from my SCH-I605 using Tapatalk 2
enkrypt3d said:
I had the latest 4.1.2 stock OTA installed via CWM and I wanted to unroot and go back to stock and that seemed to work fine.... I went to the old version VRALL4 and once rebooted it asked me to update OTA so I did and that was fine........ and it asked me to do it again for some reason and now I'm in a boot loop. The Galaxy note 2 logo flashes on the screen real fast and turns off over and over. I can only get into ODIN and not stock recovery. I've tried re-flashing the original odin package, and the pre-rooted odin packages and nothing is working.... what can I do? am i fux0rd? thx
edit: also USB all drivers are installed .......
Click to expand...
Click to collapse
Checkout this thread by Adam Outler called "DON'T ACCEPT OTA UPDATES" in the Verizon Galaxy Note II General section. I'm aware that you aren't experiencing this specific problem, but it should fix your boot loop problem. You'll need the two files that he makes available just below the picture. I've had others tell me that they used those files to successfully fix boot loops.
RomsWell said:
Try a factory reset in the stock recovery. Then give it a whirl.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I can only get into odin... not even stock recovery. the odin app doesn't even work most of the time....
If i hold vol up + power + home it just continues to boot loop flashing the note 2 logo....... downloading one more odin file to see if this can fix it..... :crying:
I knew I should have used triangle away before doing this as if I take it to the VZ store they're going to be able to tell that it'd been modified before....
The lesson you should learn from this is DO NOT ACCEPT OTAS! Not sure how you haven't understood that since it has been stated more than enough times in almost every thread.
BoostedB18C said:
The lesson you should learn from this is DO NOT ACCEPT OTAS! Not sure how you haven't understood that since it has been stated more than enough times in almost every thread.
Click to expand...
Click to collapse
First of all, I'm not a noob and I did get the system back up.... as I said above i was trying to UNROOT not ROOT my device using Odin which I have done many times. This is the first time I've ran into the boot loop issue.... so I flashed a stock unrooted odin tar.md5 and this is the issue that I had.... now when I did that, I thought I was unrooted but obviously the bootloader did not get flashed back to stock... anyways thanks for your oh so useful post in lumping me in with the n00bz... :laugh:
anyways
now im facing another issue where its still has the rooted bootloader installed but an "official" stock rom on it.....
I'm not saying you're a noob. All I'm trying to get you to understand is to read before doing. As with your unlocked bootloader issue, you probably overlooked that there are 2 ways to restore to stock. One re locks the bootloader and the other doesn't. Read more and don't skim the guide, that's all I'm saying my dude.
BoostedB18C said:
I'm not saying you're a noob. All I'm trying to get you to understand is to read before doing. As with your unlocked bootloader issue, you probably overlooked that there are 2 ways to restore to stock. One re locks the bootloader and the other doesn't. Read more and don't skim the guide, that's all I'm saying my dude.
Click to expand...
Click to collapse
thats what Ive been trying to find for ages and I've downloaded 4 or 5 different "stock" odin packages which puts me back to the original 4.1.1 I506VRALJB version....
So I'm trying to find the ODIN package that wipes everything (bootloader esp)....... thanks..... and with goo.im having so many issues its really tough finding all the files I need.
....hmmmmmmm so I updated superSU and unchecked a box that "hides" root - but if I accept another OTA i'm sure I'll be stuck with another boot loop until I really flash the unlocked bootloader with the OEM one right?
DO NOT ACCEPT OTAS! Lol. I forgot which thread had the right file. I'll look around and try to find it. Which files from which threads have you tried?
This is where I pointed the last person I helped and it worked for them
http://forum.xda-developers.com/showthread.php?p=41584579
BoostedB18C said:
DO NOT ACCEPT OTAS! Lol. I forgot which thread had the right file. I'll look around and try to find it. Which files from which threads have you tried?
Click to expand...
Click to collapse
lol yea my goal is to be on the latest and greatest OTA but of course im not going to accept an OTA until I'm 100% locked first....
http://forum.xda-developers.com/showthread.php?t=2040264
Tried this one which puts me on the original oem rom that came with the phone w/ no updates....
The only way I was able to get out of the boot loop is use the PIT file and this file root66_VZW_stock_system.tar.md5
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-verizon-galaxy-note-2-sch-i605/
Here is where I Found the "pre-rooted" file... I put that in the bootloader section of ODIN along with the PIT file and this fixed my boot loop problem.
so even tho ODIN mode says "official" and not custom - this is bc I disabled root thru superSU even though its still rooted..
http://d-h.st/Qd4
I think this is the baseline unrooted baseband......trying it out.
enkrypt3d said:
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-verizon-galaxy-note-2-sch-i605/
Here is where I Found the "pre-rooted" file... I put that in the bootloader section of ODIN along with the PIT file and this fixed my boot loop problem.
so even tho ODIN mode says "official" and not custom - this is bc I disabled root thru superSU even though its still rooted..
Click to expand...
Click to collapse
I would advise you to stay away from guides that are not on xda. Just because there is more knowledge here.
BoostedB18C said:
I would advise you to stay away from guides that are not on xda. Just because there is more knowledge here.
Click to expand...
Click to collapse
Just showing where I Got the file to recover from boot loop.... that guide isnt even for the right phone model...... read back as I added a bunch to my last post.
Trying to flash with the below file in the "phone" section so that it wipes the entire phone but it fails.... I've also removed superSU by using the option to "unroot" inside SuperSU..... whats going on? I have the PIT File in place, "phone bootloader update" checked or unchecked doesn't seem to matter..... and same for Phone EFS Clear......
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> cache.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> hidden.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> param.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> recovery.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> sboot.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
http://forum.xda-developers.com/showthread.php?t=2120726
This is the exact problem I have.....
From what I am understanding you can't write boot on Vrall4. So you would need to be on vraljb before being able to re lock the bootloader. I'm my head it makes sense but not sure how you need to go about it. I only looked at it real quick and I can't look into it right now. I'll check with you later and see what you have figured out. So post anything that you come across.
finally resolved it by erasing nand and flashing root66, then factory reset, then flashing one without the sboot.bin......
it took so many times - i dont think ive ever flashed this phone this many times before....... ugh what a pIta.... never rooting this phone again as its so freakin tempermental.
Or just don't unroot it. Problem solved??
Sent from my SCH-I605 using Tapatalk 2
enkrypt3d said:
finally resolved it by erasing nand and flashing root66, then factory reset, then flashing one without the sboot.bin......
it took so many times - i dont think ive ever flashed this phone this many times before....... ugh what a pIta.... never rooting this phone again as its so freakin tempermental.
Click to expand...
Click to collapse
please instruct me on all steps u took... where did u put the files and what u checked and what not.. i have the same exact problem except it gets stuck at Logo... i cannot go into recovery as well.
i have tried all the same files as u and all fail except root66 but it stays stuck on logo
as far as I can remember, take odin, put the pit file in the pit location in odin:
http://d-h.st/mKu
Then flash with root66...
http://androidfilehost.com/?fid=9390210501348163619
then see if u can get into stock recovery and do a factory reset and then go back into odin mode.... then tick nand erase and then use the alternate restore and put it in the phone section of the ODIN app and flash it....... of course this doesnt have the sboot but this was the only way i was able to get it back up....
if u are able to get the phone back up with root66, then stop there..... erasing the nand and not doing it right can brick it. i spent 2 days fixing mine and I must have tried flashing the phone at least 25 times... when I got root66 up and running I went into SuperSU app and went into settings and theres an option to remove or hide root. this may have helped. right now im finally on the latest OTA and it says official (not custom rom) in odin mode and in the about phone section. Hope this helps.
keep the back cover off the phone bc you'll be pulling the battery out if it gets stuck... good luck. FYI I always use the PIT file and that always seemed to have helped.
enkrypt3d said:
as far as I can remember, take odin, put the pit file in the pit location in odin:
http://d-h.st/mKu
Then flash with root66...
http://androidfilehost.com/?fid=9390210501348163619
then see if u can get into stock recovery and do a factory reset and then go back into odin mode.... then tick nand erase and then use the alternate restore and put it in the phone section of the ODIN app and flash it....... of course this doesnt have the sboot but this was the only way i was able to get it back up....
if u are able to get the phone back up with root66, then stop there..... erasing the nand and not doing it right can brick it. i spent 2 days fixing mine and I must have tried flashing the phone at least 25 times... when I got root66 up and running I went into SuperSU app and went into settings and theres an option to remove or hide root. this may have helped. right now im finally on the latest OTA and it says official (not custom rom) in odin mode and in the about phone section. Hope this helps.
keep the back cover off the phone bc you'll be pulling the battery out if it gets stuck... good luck. FYI I always use the PIT file and that always seemed to have helped.
Click to expand...
Click to collapse
ah man... i can get PASS! on root66 but it still gets stuck at logo.. anything else i flash will just fail at boot.img nand write... think im just f*ck'ed dude..
my thread is here if anything... thank you !
http://forum.xda-developers.com/showthread.php?t=2296441
Best bet is to erase nand and try flashing with the alternative rom and pit file at the same time...tomorrow I'll post the files I used as most mirrors are slow as balls..
Sent from my SCH-I605 using xda app-developers app
Dear XDA'ers,
I know their are a lot of topics on this problem, but I can't seem to find the answer.
The first thing I tried was going into recovery mode and doing a factory reset. That did not do the trick.
After that I wasn't able to get into recovery mode anymore, so I went online and searched some topics.
I downloaded a stock S2 ROM and flashed it through ODIN, but it kept failing.
From searching topics it seemed like my S2 suffered from NAND rw corruption.
And nothing fixed, so eventually I went to flash the bootloader. This was the first flash that was succesfull and it got me back to the samsung home screen. Then I tried to flash a new 3 part stock ROM, but it is not working, it keeps getting stuck at this point.
Any one that can talk me through this? Have not a lot of experience with this, so please try to keep it simple for me.
Thanks in advance
If the NAND is really stuffed, motherboard replacement. There is no other fix. Or you could search for Hopper8's 'Odin troubleshooting' thread & keep trying the stuff in the thread over & over & over.
Up to you.
MistahBungle said:
If the NAND is really stuffed, motherboard replacement. There is no other fix. Or you could search for Hopper8's 'Odin troubleshooting' thread & keep trying the stuff in the thread over & over & over.
Up to you.
Click to expand...
Click to collapse
but if that would be stuffed. I shouldn't be able to flash a bootloader should I?
You're the one who mentioned NAND corruption.
If the NAND really is corrupted, then that's the fix. And no, 'successfully' flashing a bootloader (or anything) does not necessarily mean the phone is easily fixable. 'Success' in Odin without the phone working/booting normally isn't success at all.
As per my previous post, find the thread (which really is the reference of these things here), try the stuff in it, see if you can fix it.
If not, you know what to do.
same problem bootlooping
hi guys i am currently having the same problem, i successfuly flashed the JB stock firmware but it's still keep bootlopping..my combo button doesnt work so i am using USB JIG to go into donwload mode, i can even go to recovery mode..hoping for some can link me or provide with FULL PACKAGE, meaning it has a PIT file, BOOTLOADER, CSC, PDA AND PHONE..I think this will be my last resort, so if anyone having this file im looking for plz plz plz direct mo to tha..thnaks
yes u have emmc corruption I have fixed it
but my fix was for data partition your problem is the kernel partition ill make a fix for your phone and inform u soon
Sent from my GT-I9100 using xda premium
follow my guide
http://forum.xda-developers.com/showthread.php?t=2400535
but instead of using the data fix pit as mentioned in the guide use the attached kernel fix pit file the rest of the steps are the same
Sent from my GT-I9100 using xda premium
iamtalha said:
follow my guide
http://forum.xda-developers.com/showthread.php?t=2400535
but instead of using the data fix pit as mentioned in the guide use the attached kernel fix pit file the rest of the steps are the same
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
No luck .
Stuck at NAND WRITE:
Log:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> zImage
<ID:0/006> NAND Write Start!!
Hey guys, recently got mugged for my new S5 and was given a unlocked, bootloop'd S3 i9300 international galaxy s3 (Im from Canada). My buddy told me he had dropped it from about knee high onto carpet when it started having some issues with restarting randomly. He attempted to root it to solve the problems and ended up getting it stuck in a bootloop without the possibility of entering recovery mode. However the phone does go into download mode, so I'm assuming this is a fixable semi brick?
Anyways I started doing my research and found out I should try and reflash the stock firmware using Odin. I found a firmware which I beleive to be the right one, and tried to use Odin.
I got the following message;
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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
So I have no idea what this means, as every guide I've seen has said not to touch the PIT button etcetc
I'm not sure if this is helpful, but the writing in download mode is as follows : Odin Mode * Product Name (Blank) * Custom Binary Download : No * Current Binary : Samsung Official * System Status : Custom.
That's about all of the info I have, and seeing how this is the only phone I can afford right now any help would be very much appreciated. Thanks guys.
AlexD73 said:
Hey guys, recently got mugged for my new S5 and was given a unlocked, bootloop'd S3 i9300 international galaxy s3 (Im from Canada). My buddy told me he had dropped it from about knee high onto carpet when it started having some issues with restarting randomly. He attempted to root it to solve the problems and ended up getting it stuck in a bootloop without the possibility of entering recovery mode. However the phone does go into download mode, so I'm assuming this is a fixable semi brick?
Anyways I started doing my research and found out I should try and reflash the stock firmware using Odin. I found a firmware which I beleive to be the right one, and tried to use Odin.
I got the following message;
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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
So I have no idea what this means, as every guide I've seen has said not to touch the PIT button etcetc
I'm not sure if this is helpful, but the writing in download mode is as follows : Odin Mode * Product Name (Blank) * Custom Binary Download : No * Current Binary : Samsung Official * System Status : Custom.
That's about all of the info I have, and seeing how this is the only phone I can afford right now any help would be very much appreciated. Thanks guys.
Click to expand...
Click to collapse
Have you tried more than one stock firmware. Where is the phone originally from? I'm not able to find and Canadian firmware.
Darke5tShad0w said:
Have you tried more than one stock firmware. Where is the phone originally from? I'm not able to find and Canadian firmware.
Click to expand...
Click to collapse
I was using UK stock firmwares, but I am unable to flash any firmwares at all successfully due to the error above. It wont go father then the "No Pit".
This try
http://www.ibtimes.co.uk/install-i9300xxugna5-android-4-3-stock-firmware-galaxy-s3-1434726
AlexD73 said:
I was using UK stock firmwares, but I am unable to flash any firmwares at all successfully due to the error above. It wont go father then the "No Pit".
Click to expand...
Click to collapse
Heres the link to the rescue firmware. All the info you gave me says you have pit problems.
This is an emergency firmware that will ever fix or brick the phone but the phone was given to you and you have nothing to lose.
http://forum.xda-developers.com/showpost.php?p=30087735
Darke5tShad0w said:
Heres the link to the rescue firmware. All the info you gave me says you have pit problems.
This is an emergency firmware that will ever fix or brick the phone but the phone was given to you and you have nothing to lose.
http://forum.xda-developers.com/showpost.php?p=30087735
Click to expand...
Click to collapse
The 4.3 download doesn't have the PIT file in it though, I'm guessing that's the important part? Edit *** repartition failed with the 4.1.2
AlexD73 said:
The 4.3 download doesn't have the PIT file in it though, I'm guessing that's the important part? Edit *** repartition failed with the 4.1.2
Click to expand...
Click to collapse
The pit file is in the rescue firmware file. That's the whole point of the rescue firmwares.
I'm sorry I can't help you any further. I'm not going to provide you a pit file etc as I have no knowledge with them or used them.
Sounds to me like it is bricked.
Good Luck.
The power button is stuck, try to flick it some times and it should stop the bootloop. i drop mine when i was getting it out of my pocket last week and same thing happen, the smd switch got stuck and eventually i broke it down trying to get it lose again.
Hello guys!
I am new here, nice to meet all you guys. I have a huge problem with my S3 and I hope it can be fixed without having to replace the motherboard. Last week a flashed the 24th December nightly of CM14. I did a clean flash through my recovery (TWRP) and everything was working fine until two days ago when I found my phone stuck with the CM logo. I removed the battery and tried to switch it on again after reinserting it: it only showed the "Galaxy SIII" logo and couldn't boot. Now, my phone is still in this state. I can go into download mode (and it correctly shows the model number) and I have full access to the twrp recovery. However, the recovery says "no OS installed" and shows an internal memory of 0mb. It is impossible to do a full wipe as it can't mount any partition (only the recovery partition). Using Odin, I can't flash ANY rom I tried so far... I think it's a soft break as I have full access to the recovery, with a full funcioning touch screen and vibration. Is there a way to fix it? Any help? When I'm home I will give you more details and even post some photos of the error messages I get from Odin and the recovery.
Happy new year to everyone and thanks for your help.
trufogio said:
Hello guys!
I am new here, nice to meet all you guys.
Spoiler
I have a huge problem with my S3 and I hope it can be fixed without having to replace the motherboard. Last week a flashed the 24th December nightly of CM14. I did a clean flash through my recovery (TWRP) and everything was working fine until two days ago when I found my phone stuck with the CM logo. I removed the battery and tried to switch it on again after reinserting it: it only showed the "Galaxy SIII" logo and couldn't boot. Now, my phone is still in this state. I can go into download mode (and it correctly shows the model number) and I have full access to the twrp recovery. However, the recovery says "no OS installed" and shows an internal memory of 0mb. It is impossible to do a full wipe as it can't mount any partition (only the recovery partition). Using Odin, I can't flash ANY rom I tried so far... I think it's a soft break as I have full access to the recovery, with a full funcioning touch screen and vibration. Is there a way to fix it? Any help? When I'm home I will give you more details and even post some photos of the error messages I get from Odin and the recovery.
Happy new year to everyone and thanks for your help.
Click to expand...
Click to collapse
You should try to flash a Factory formatting firmware and remapping the partitions with Pit file using Odin. If this doesn't work... There's nothing else to do
TapaStalking
Where can I find the right factory formatting firmware and pit file? I have an International version of GSIII bought in Italy (16gb). In case it doesn't work, will replacing the motherboard do the job? The thing I still don't get is how can the internal memory be damaged if I have full access to the recovery? The recovery is stored in the internal memory, isn't it?
Are you Italian? If so, take a look at this... http://www.androidiani.com/forum/showthread.php?t=344896
TapaStalking
Yes, I am! Thanks, I'll have a look at that link.
Ok, I've tried flashing a PIT file to repartition through Odin and this is what I got:
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
When I switch it on I can still go in download mode and recovery, but nothing has changed. I will try now to download a factory formatting firmware.
EMMC brick bug claims another device. Nothing can be done other than replacing the EMMC chip in a specialised repair shop. Or buy another motherboard (i know you're against it, but sh*t happens, yo).
西村大一 said:
EMMC brick bug claims another device. Nothing can be done other than replacing the EMMC chip in a specialised repair shop. Or buy another motherboard (i know you're against it, but sh*t happens, yo).
Click to expand...
Click to collapse
But if the EMMC chip is bricked, how can I still enter into recovery mode? Isn't the recovery stored in the EMMC like any other partition? Am I missing something? I mean, If I couldn't go into recovery I would agree with you, the EMMC would have broken. But as I DO enter into recovery (and can read some files) looks like another problem... If I am wrong, please explain how it works because I'm a little bit lost
I had researched before posting and hadn't found anything helpful, that's why I asked here. There is no need to be rude as this forum is here to offer help between all members of the community
trufogio said:
Ok, I've tried flashing a PIT file to repartition through Odin and this is what I got:
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
When I switch it on I can still go in download mode and recovery, but nothing has changed. I will try now to download a factory formatting firmware.
Click to expand...
Click to collapse
Why "added" come later then repatriation operation... I think you should try and try.... Maybe you can change Odin version too. Don't give up just after one try
TapaStalking
ivano949 said:
Why "added" come later then repatriation operation... I think you should try and try.... Maybe you can change Odin version too. Don't give up just after one try
TapaStalking
Click to expand...
Click to collapse
Thanks, I will try!! Anyway if it keeps failing, I found a new gs3 motherboard for just 20 euros...if it's not too difficult to replace I think I will buy it.
trufogio said:
Thanks, I will try!! Anyway if it keeps failing, I found a new gs3 motherboard for just 20 euros...if it's not too difficult to replace I think I will buy it.
Click to expand...
Click to collapse
That's difficult for nothing. Done this summer on my sweet S3, there are tons of tutorial in youtube.... The only thing is wishing new motherboard is OK and don't have a locked imei.... Think at this... Maybe is just time to have a new (and newer) phone
TapaStalking
Are you using the original Samsung USB cable and USB 2.0 ports?
audit13 said:
Are you using the original Samsung USB cable and USB 2.0 ports?
Click to expand...
Click to collapse
yes, I am! I tried several times but it fails every single time... I think I'll buy a new motherboard, 20 euros is a great price. I already have a newer phone (galaxy s6) but I need this s3 to be back to work in order to use it with my secondary sim card Anyway, If you think about installing CM14 nightlies, they are not stable at all at the moment.
trufogio said:
I had researched before posting and hadn't found anything helpful, that's why I asked here. There is no need to be rude as this forum is here to offer help between all members of the community
Click to expand...
Click to collapse
I am not intending to be rude, I even explained what EMMC Brick bug means as a way to educate you and the ones that search the forums for explanations, but since you got my post deleted because you thought i was trying to be rude, well yeah, okay. That's why I hate people.
Please keep it respectful in here, and respect each others opinions..
Here's a thorough read for you guys : XDA Rulesforum.xda-developers.com/announcement.php?a=81
Regards
Vatsal,
Forum Moderator.