Hello
For a couple of weeks now, i've been trying to fix this phone for a friend who studies as an artist. She wanted the Galaxy Beam for presentations and bought one used as they seemingly ain't to be found in the stores any longer.
Originally, the firmware ends at 2.3.6 on this brand, but this one was rooted to be fit with 4.1.2.
The phone bugged and hung in weird ways, so i thought to follow the steps into downgrading it to stock rom for her and see if that would help.
I am no expert, but since i have successfully rooted several phones and tablets earlier with no issues (its pretty straight forward when it works, right), i felt up for the tast.
I have spent a lot of time googling the last couple weeks, and reading a lot of solutions here on these forums, but i can't seem to find this ecact problem, so here goes.
Samsung Galaxy Beam GT.I8530
Odin3 v3.07
Windows 7 and 8 fully updated (tried both)
No matter which Android version i chose, it ends up at the same spot. Stuck at logo screen after first boot.
I have tried both with and without a PIT file, same result.
This last try was with a PIT and Android 4.1.2. (i understand that PIT is not nessessary, as it should be baked within the PDA if it's a single file, but what won't you try eventually, right?)
Load Odin, admin rights
Boot phone in download mode
Insert USB
-->
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8530DXLJ1_I8530OLBLJ1_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.img.md5
<ID:0/003> NAND Write Start!!
<ID:0/003> hidden.img.md5
<ID:0/003> kernel.bin.md5
<ID:0/003> modem.bin.md5
<ID:0/003> system.img.md5
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
- here, the phone reboots and loads to logo screen *
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
- from here the phone wont nudge from the logo screen. can reboot, nothing new happens.
No other functions work, other than:
- volume down+home+power (download mode)
- power (boots to logo screen)
Thanks for reading! Hope someone feels up for the task
Edit: It might be vital information that the phone will uncharge the battery at logo screen eventually, even when connected to a computer. (5v output) But i believe this is common somehow.
Also, if i try and shut down the phone, it will reboot into a frozen "star icon".
Bump*
What makes this issue differ from others i've read on these forums, is this:
Akiiras said:
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Any theories?
As much as i hate bumping, i'm feeling kind of responsible to try and fix it. Hope someone got a clue on what might be wrong. Thanks
"I bet you 10 buck you'll get your answer here within a couple days" -a friend said, well, in norwegian though.
I guess a week later and no response means that i've at least earned 10 buck! ^^
Guess i can give it one more shot here before i send it to a repair guy.
*bump*
Akiiras said:
Guess i can give it one more shot here before i send it to a repair guy.
*bump*
Click to expand...
Click to collapse
Are you sure about the right region when choosing a firmware? Did you also try Odin 1.85? Have you tried flash a custom recovery via Odin and flash a rom manually?
LS.xD said:
Are you sure about the right region when choosing a firmware? Did you also try Odin 1.85? Have you tried flash a custom recovery via Odin and flash a rom manually?
Click to expand...
Click to collapse
Hi, and thanks for the reply!
I am pretty sure i got the right firmware region. At least, the only region that covered my location (norway) that i could find, was nordic.
I have not tried Odin v1.85 or manually. I guess i can find a guide on how to do it manually here somewhere, but i'll go for a shot with the older version of Odin right away.
Thanks!
Akiiras said:
Hi, and thanks for the reply!
I am pretty sure i got the right firmware region. At least, the only region that covered my location (norway) that i could find, was nordic.
I have not tried Odin v1.85 or manually. I guess i can find a guide on how to do it manually here somewhere, but i'll go for a shot with the older version of Odin right away.
Thanks!
Click to expand...
Click to collapse
BTW there are 4 different versions for nodric countries --> LINK
Odin3 v1.85 didn't work. Well, in the sense that it probably does a job well done and says everything went well, but the phone wont nudge past boot screen.
I'll see if i can learn how to do it manually and come back with the result.
Edit:
LS.xD said:
BTW there are 4 different versions for nodric countries --> LINK
Click to expand...
Click to collapse
Oh, thanks! I couldnt find it at sammobile myself, so i found it somewhere else. This could be it!
any developments?
I Have the Same Problem
I Have the same problem please anyone help me!!!!!
SOLUTION
Akiiras said:
Hello
For a couple of weeks now, i've been trying to fix this phone for a friend who studies as an artist. She wanted the Galaxy Beam for presentations and bought one used as they seemingly ain't to be found in the stores any longer.
Originally, the firmware ends at 2.3.6 on this brand, but this one was rooted to be fit with 4.1.2.
The phone bugged and hung in weird ways, so i thought to follow the steps into downgrading it to stock rom for her and see if that would help.
I am no expert, but since i have successfully rooted several phones and tablets earlier with no issues (its pretty straight forward when it works, right), i felt up for the tast.
I have spent a lot of time googling the last couple weeks, and reading a lot of solutions here on these forums, but i can't seem to find this ecact problem, so here goes.
Samsung Galaxy Beam GT.I8530
Odin3 v3.07
Windows 7 and 8 fully updated (tried both)
No matter which Android version i chose, it ends up at the same spot. Stuck at logo screen after first boot.
I have tried both with and without a PIT file, same result.
This last try was with a PIT and Android 4.1.2. (i understand that PIT is not nessessary, as it should be baked within the PDA if it's a single file, but what won't you try eventually, right?)
Load Odin, admin rights
Boot phone in download mode
Insert USB
-->
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8530DXLJ1_I8530OLBLJ1_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.img.md5
<ID:0/003> NAND Write Start!!
<ID:0/003> hidden.img.md5
<ID:0/003> kernel.bin.md5
<ID:0/003> modem.bin.md5
<ID:0/003> system.img.md5
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
- here, the phone reboots and loads to logo screen *
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
- from here the phone wont nudge from the logo screen. can reboot, nothing new happens.
No other functions work, other than:
- volume down+home+power (download mode)
- power (boots to logo screen)
Thanks for reading! Hope someone feels up for the task
Edit: It might be vital information that the phone will uncharge the battery at logo screen eventually, even when connected to a computer. (5v output) But i believe this is common somehow.
Also, if i try and shut down the phone, it will reboot into a frozen "star icon".
Click to expand...
Click to collapse
I have The solution For that remove your battery and charge battery by use of another working mobile or battery charger box
after charging you do the flashing using android 4.1.2
it successfully works on my mobile
the problem is battery is low so that at the time of flashing it turned off ....so fill the battery and use......
Related
Hello everyone,
I am not sure whether this is the right place for my question but my Galaxy S II stopped working and I was wondering if anyone might help me?
I tried updating the FW from 2.3 to 4.0 (I'm guessing) through Kies and after about 45 minutes of seeing both screens (PC and Phone) unchanged, I ended up removing the phone. Next, Kies suggested an "Emergency Firmware thingy" (it said it in German so I wouldn't really know how to translate it). Tried again, after 45 minutes gave up once more.
Since then, I downloaded ODIN and tried to follow instructions I found online to flash it (first I tried with Ice-Cream, then with Gingerbread).
Ever since I removed it from Kies, it would only show a phone connected to a PC with a yellow warning triangle in the middle. Whenevery I use the Volume-Menu-Power button, the warning on changing the OS appears and then, when I press "volume up", it shows the green android in the middle and tells me it's downloading and not to turn off the device, though there is no downloading progress.
When I try with ODIN, ODIN recognizes the device on both USB ports - I found md5 files for Germany but every time I start it the Message window says:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLA4_I9100VIAKI1_I9100XXKI4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
and doesn'tget any farther than "cache.img".
I am at a complete loss as to what to do or try. I have had this phone for a year now, this is the first time I tried to update with Kies - the phone had not been rooted or anything else. The phone has no simlock (I don't know if any other information is relevant).
Any ideas or has my phone thus become the infamous brick? *pleasenopleasenopleaseno*
Thanks in advance for your time and patience - in case I've overread a thread with this exact same problems, I apologize and would appreciate if someone could re-direct me. I've already spent so much time looking for solutions, my concentration may have suffered.
Best wishes,
Junivere
Before flashing with Odin, did you kill all Kies processes from Windows task manager? If not, do that and then start flash.
Edit: And since you can access download mode, its not bricked...so you can relax
Sent from my GT-N7100 using Tapatalk 2
I9100?
Flash JB.
And try an older ODIN version.
And check kies like the above poster suggested.
Other usb port/usb cable might do the work too.
Sent from the little guy
Thanks for the replies!!!
I stopped all the Kies processes over the task manager before (was that enough?) and tried from both USB ports of my laptop (006 and 007 I guess) with equal results.
I used Odin3 v1.85 - is that too old or too new? Which version should I try?
And I am sooooooooo relieved it's not a brick!!!
Thanks again!
kinda old, try 1.3 or 3.x
And flash siyah v5 just for kicks.
Sent from the little guy
I tried again and I'll try to explain step by step, ok? Maybe you notice something I did wrong?
I killed all the Kies processes in the task manager like before.
I downloaded Odin 3 v.07 and started it. I had "Auto reboot" and "F.Reset time" checked and clicked on "PDA" to add the *.md5 file with the firmware.
I started the phone in the download mode and connected it to the PC, Odin recognized it alright.
I started and the first time, with the USB port in front, it stopped at "cache.img" in the message window.
I tried a different FW file and the other USB port further back and for the first time the phone shows a tiny bit of blue in the progress underneath "Downloading..." but in Odin it is now stuck at "factoryfs.img" for the last ten minutes,
The entire message window says this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLA4_I9100VIAKI1_I9100XXKI4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
<ID:0/007> factoryfs.img
Any ideas???
Best wishes and thanks again!!!
Flash siyah V5.
Sent from the little guy
How do I do that? I tried to find an instruction in the XDA forum in the 15 minutes I have between posts but couldn't find anything.
Junivere83 said:
How do I do that? I tried to find an instruction in the XDA forum in the 15 minutes I have between posts but couldn't find anything.
Click to expand...
Click to collapse
gokhanmoral.com
Siyah v5 for SII.
Put it on PDA, press start and flash away.
Sent from the little guy
Ok, so now I am starting to get slightly terrified:
When trying to flash Siyah 5 (Siyah-s2-v5.0.1), it stops there:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> zImage
:crying:
Keep trying, you'll come around.
Another usb cable could help.
Another pc would as well.
Sent from the little guy
Ok, so the Sivyah v5 flash worked when I tried Odin3 v1.3 but I'm still battling with the actual firmware.
Thanks for your help so far, though - I'm really greatful and I'll keep trying.
My mission for today will be finding someone's cable and PC to borrow...
I'll keep you posted, though!
Wow, you are the bestest ever!!!
With a netbook (OS Windows 7) I eventually managed the flash - now I'm reconfiguring everything. I am sooooo relieved!!!!
I have one last question (sorry for being so naive!), though:
Is it still possible with a flashed phone (with the Sivya thing on it) to use Kies to try and update or do automatic updates or do I have to flash all the newer firmware?
Best wishes,
Junivere
Junivere83 said:
Wow, you are the bestest ever!!!
With a netbook (OS Windows 7) I eventually managed the flash - now I'm reconfiguring everything. I am sooooo relieved!!!!
I have one last question (sorry for being so naive!), though:
Is it still possible with a flashed phone (with the Sivya thing on it) to use Kies to try and update or do automatic updates or do I have to flash all the newer firmware?
Best wishes,
Junivere
Click to expand...
Click to collapse
Depends on what ROM you are flashing.
For instance, if you flash LS8 you'll get a 22 mb update to get you to LSD.
I would flash LSD straight up tho.
If you don't want a headache with odin no more, feel free to try Mobile Odin, it will perform all the flashing for you.
Sent from the little guy
Hello everybody!
First of all, I'm not sure about my english skills...please have mercy on me :fingers-crossed:
Here I go:
I got my S3 in August/Sept with a T-Mobile Branding. My first action was getting it rootet and flashed with an official Samsung Rom just to get rid of the branding.
Two days ago I woke up to my charging S3 only showing the "Samsung..." Bootlogo. Removed the battery, nothing changed. Tried the Volume up-HomeButton-PowerButton Combo and it only resulted in a blinking logo (the logo disappears for a few seconds). The only thing I have access to is the Download-Mode.
What I tried since then:
Flashing a new one-part-rom with Odin, this was the result:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXALE8_554452_REV00_user_low_ship.tar.md 5 is valid.
<OSM> MODEM_I9300XXLE8_REV02_REV04_CL1145430.tar.md5 is valid.
<OSM> CSC_OJV_I9300OJVALE7_CL547448_REV00_user_low_noshi p.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> sboot.bin
<ID:0/003> NAND Write Start!!*
<ID:0/003>*
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Same with a three-part-rom.
Then I tried to downgrade the bootloader with ADB. But I don't get the drivers (Universal-Naked-Drivers) running. The S3 shows up as "unknown device" at the device manager but it doesn't want to be updated with the right drivers. PdaNet also refused to install USB-Drivers.
It's like they don't recognize the S3.. Perhaps I don't have USB-Debugging enabled? I'm not sure about this, because this brick just happened from one day to another.
I installed and uninstalled the "normal Samsung USB-Driver for mobile phones" often while trying to get the other drivers running. When installed, the S3 showed up in the device manager as one of the USB-Controllers.
Installed Kies for a factory reset but it didn't recognize the S3..
This shows up in Download-Mode:
ODIN*MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: Yes (3 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
I guess it's no sudden death because it shows the product name? Also I have no idea why it has three flash counts, I just flashed it once seven month ago.
Since I never updated to Jelly Bean the S3 was running on ICS 4.0.4
Edit:
Next steps I tried:
Flashing with an older version of Odin (v.1.85) But also failed at <ID:0/003> Complete(Write) operation failed
Flashing CF-Root v.6.4 to get the recovery mode back. Failed at <ID:0/003> Complete(Write) operation failed
Flashing Resurrection Odin CheckRom EvoHD v.4. Failed at <ID:0/003> Complete(Write) operation failed
Repartition with 20120329.pit and mx.pit. Failed at <ID:0/003> Complete(Write) operation failed
I'd still appreciate any kind of help or feedback!
It sounds like partial nand failure or simple partition corruption. Search here in q&a for solutions to repartition, but if that fails then your nand is probably toast.
try flashing a pit file
not sure if it will help but..
connect it to computer..when it fails to install drivers..Turn off and Pull battery out for few secs restart..
sometimes this helps to reinstall drivers..not sure in your case of a bootloop though?
Thanks for your answers!
I tried to repartition with a PIT-File but it didn't work.
At first I tried the GT-I9300_mx_20120329.pit with this 3-part-rom:
CODE_I9300XXALE8_554452_REV00_user_low_ship.tar.md5 is valid.
MODEM_I9300XXLE8_REV02_REV04_CL1145430.tar.md5 is valid.
CSC_OJV_I9300OJVALE7_CL547448_REV00_user_low_noship.tar.md5 is valid.
But the same error appeared.. also the error appeared so fast I don't think there happened a repartition at all?
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Second try was 3-part-rom recommended with the mx.pit-File:
CODE_I9300XXALEF_611327_REV00_user_low_ship.tar.md5 is valid.
MODEM_I9300XXLEF_REV02_REV04_CL1147871.tar.md5 is valid.
CSC_OXF_I9300OXFALEA_613742_REV00_user_low_ship.tar.md5 is valid.
With the same result...
It's always the same error, again and again...
Any further ideas?
you are done
Only two answers one wrong PIT or partition damaged .
Two Nand damaged see how much will a new motherboard cost .
jje
Thanks again!
With the GT-I9300_mx_20120220.pit-File I got my S3 responding for the first time since it died. It showed the blue loading-bar, but it didn't move at all and Odin stopped at <ID:0/004> NAND Write Start!!
Tried this rescue-version http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 with mx.pit but of course it didn't work..
you are done
Click to expand...
Click to collapse
seems like you're right, unfortunately..
But if you have ANY idea what I could try, please post it.
Are you sure it's a NAND damage or could it be a bootloader problem? I found this thread: http://forum.xda-developers.com/showthread.php?t=1916796 but I don't understand what they are talking about yet.
Update:
I couldn't find a solution and send it to a Samsung repair service and it was repaired under warranty. Don't know why exactly..they didn't need to because of my flash-counter. There was a letter in the package that said the mainboard was replaced and that's all!
Anyways, thanks for the help!
Can be closed!
Possible Solution
xylakant said:
Update:
I couldn't find a solution and send it to a Samsung repair service and it was repaired under warranty. Don't know why exactly..they didn't need to because of my flash-counter. There was a letter in the package that said the mainboard was replaced and that's all!
Anyways, thanks for the help!
Can be closed!
Click to expand...
Click to collapse
I had a similar problem, my phone just froze in the middle of a phone call, had to pull out battery, and when i tried to turn it on, it wouldn't pass the second "SAMSUNG" logo, just stayed there forever, with the blue light (Official JB 4.1.2 - not rooted)... Anyway, after 3 days of trying, downloaded bunch of firmwares, but all of them gave me the infamous "Complete(Write) operation failed". This is how I MANAGED to revive my i9300 16Gb Int:
1.Open ODIN, load ONLY the pit file corresponding to your phone (In my case i9300 16Gb Int'l - GT-I9300_mx_20120220.pit), check "Repartition" and "F.Reset Time" and hit "Start".
- If this step goes OK (All threads completed. (succeed 1 / failed 0))
2. Click on the "Reset" button in Odin (or close and re-open it), in PDA select "recovery-cwm-touch-6.0.1.2-i9300.tar", make sure only "F.Reset Time" and "Auto Reboot" are checked, and flash it. If everything goes OK, you should now have CWM instead of Stock recovery.
3. Take any microSD card, any size, and put THIS file on the root of the microSD using a card reader or whatever you prefer - but be careful, copy the zip as it is - do not unzip it.
4. Insert the memory card in the phone, enter recovery*, and select "Install zip from External Storage" and choose the file you put on the root of the card (by the way, it's a 4.0.4 downgrade bootloader), it should flash in a second, the phone will restart, and that's it!
5. Download and flash 4.0.4 Stock FW using Odin (i used "I9300XXBLH1_OXEBLF1.zip"), everything should go OK, and the phone will be bootable again.
*(my phone didn't wanted to enter recovery the old fashioned way using 3-button combo, but i managed to enter recovery from charging mode, by connecting the charger on a switched off phone, and as soon it starts charging press Vol Up + Home + Power, and when the FIRST Logo (Galaxy S III GT-I9300) appears, let go of the power button, keep pressing the Vol Up + Home, and it enters recovery).
ATRAC3 said:
1.Open ODIN, load ONLY the pit file corresponding to your phone (In my case i9300 16Gb Int'l - GT-I9300_mx_20120220.pit), check "Repartition" and "F.Reset Time" and hit "Start".
- If this step goes OK (All threads completed. (succeed 1 / failed 0))
Click to expand...
Click to collapse
Odin Stuck at "Set Partition" ^^
"<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
Help ?
Did you give it the pit file? Pit is really a last resort AFTER you've ruled out sending for repair
Sent from my GT-I9300 using Tapatalk 4
I have the pit file and Checked the Box ^^
MrFraggii said:
I have the pit file and Checked the Box ^^
Click to expand...
Click to collapse
Correct PIT file ??? for your phone ??
Flashing PIT 99% kill the phone .
You require a service centre .
Warranty will depend upon their report .
jje
Have the right Pit file ^^ But odin Stuck at Set mapping
MrFraggii said:
Have the right Pit file ^^ But odin Stuck at Set mapping
Click to expand...
Click to collapse
Where can you download these 16, 32 or 64 .pit files ? I couldn't find them anywhere ...
If you start playing with PIT files you will end up with a dead phone and at best have to buy a new motherboard .
They might be found on sammobile
jje
JJEgan said:
If you start playing with PIT files you will end up with a dead phone and at best have to buy a new motherboard .
They might be found on sammobile
jje
Click to expand...
Click to collapse
Thanks for the lead, I will look for them on Sammobile.
But Please, this is the only answer I could reald along my searches "do not mess with .pit file". That does not answers the "where" and "which file" questions. I think people know playing with .pit files is touchy and they have a reason to ask for it.Stop being their mother and just answer the question accurately !
tris16 said:
Thanks for the lead, I will look for them on Sammobile.
But Please, this is the only answer I could reald along my searches "do not mess with .pit file". That does not answers the "where" and "which file" questions. I think people know playing with .pit files is touchy and they have a reason to ask for it.Stop being their mother and just answer the question accurately !
Click to expand...
Click to collapse
Your sense of entitlement is awe inspiring, if you searched and read you would find many people who flashed pit files to fix just a soft brick and then had to pay for a new motherboard.
So no, we won't help people wreck their phones.
Pit Files
tris16 said:
Where can you download these 16, 32 or 64 .pit files ? I couldn't find them anywhere ...
Click to expand...
Click to collapse
This is where i got mine.
http://forum.xda-developers.com/showthread.php?p=30547929
I rooted my phone about 1.5 years ago when I got it. I remember I installed a custom ROM (can't remember which right now for sure - possibly omega?) and kernel (siyah) .. I'm not sure if that matters? I know I had clockworkmod installed.
Phone's worked fine for ages. Today it randomly crashed playing a youtube video and got stuck in a boot loop. On a couple of occasions it came up with a welcome/start screen as if it was a brand new stock s3 but then booted again.
It kept coming up with the b&w samsung galaxy s3. That's it, it'd sometimes turn off and on, same thing again.
I can't get it to go into recovery mode. It happened once or twice very briefly, but then just rebooted again.
I got it in download mode. I tried recovering using KIES but it failed. Tried using ODIN and a stock s3 ROM and it failed. Tried using ODIN with a "nowipe" root ROM and odin hung.
Now if I try to turn it on without download mode it just says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
Can anyone give me any suggestions/help? Am I screwed, is it permanently bricked?
jeemer said:
I rooted my phone about 1.5 years ago when I got it. I remember I installed a custom ROM (can't remember which right now for sure - possibly omega?) and kernel (siyah) .. I'm not sure if that matters? I know I had clockworkmod installed.
Phone's worked fine for ages. Today it randomly crashed playing a youtube video and got stuck in a boot loop. On a couple of occasions it came up with a welcome/start screen as if it was a brand new stock s3 but then booted again.
It kept coming up with the b&w samsung galaxy s3. That's it, it'd sometimes turn off and on, same thing again.
I can't get it to go into recovery mode. It happened once or twice very briefly, but then just rebooted again.
I got it in download mode. I tried recovering using KIES but it failed. Tried using ODIN and a stock s3 ROM and it failed. Tried using ODIN with a "nowipe" root ROM and odin hung.
Now if I try to turn it on without download mode it just says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
Can anyone give me any suggestions/help? Am I screwed, is it permanently bricked?
Click to expand...
Click to collapse
have a look here, maybe same challenge you are facing (I just flew over the thread).
I tried a few other things since.
Using Odin I tried flashing a stock ROM, after ending the Kies process and using a different USB. It all said it had worked, gave me a boot screen and said android is upgrading - optimising apps. It hung doing this at 10 of 70 or something. I tried resetting and it hung at 5 of 70, and when i reset again it just wouldn't get past that.
Tried flashing with a more recent stock ROM using Odin 1.3 as above, but it hung at system.img
Tried flashing with the more recent stock ROM using the latest Odin. The blue bar counted right up to full on my screen, then the phone reset.
It was sitting with the little 3d android character with the spinning 3d mesh sphere in his stomach. A blue line started counting up but has frozen about maybe 25% of the way along. After a short while Odin said PASS! and it all seems to have completed according to Odin
The android graphic was still spinning but nothing else was happening, the blue line would not progress any further.
After a few minutes the phone screen went black, and came up with the black and white Samsung Galaxy SIII screen for a second or so. Then it just went black again.
Here is the Odin log
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELL4_I9300O2UELL1_I9300BWELK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> recovery.img
<ID:0/004> modem.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
When I turn it on now the same thing happens - the black and white Samsung Galaxy SIII screen comes on for a second or so and then the screen goes black.
If I try and put it in recovery mode the same thing happens. If I try to put it in download mode, that works.
Am I right in thinking I still have a hope to save it here since Odin still sees it? What do I try now? :/
http://forum.xda-developers.com/showthread.php?t=1840030
this is the only other suggestion I've found so far and it seems quite scary!
Flash a full stock rom using latest odin, immediately boot into recovery and factory reset.
Because you left the phone for so long on a firmware that was not SDS safe you may have nand memory damage, even if the file structure is still intact.
Sent from my GT-I9300 using Tapatalk
I tried doing a full flash again with the older stock firmware I started with. Got right through the whole process again, says it passed and it hung at the Android guy with the spinning mesh sphere.
I've never managed to get it into recovery mode since i got it in clockwork recovery mode a couple of occasions last night and it reset each time
Any suggestions as to what I could try to get it past this stage?
If it looks like I have nand memory damage would it be worth trying what's in that "scary" link i posted? :/
I tried flashing again to see if I could instantly get it into recovery and it failed for the first time
Here is the log
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXDLIH_I9300O2UDLI3_I9300BWDLI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> recovery.img
<ID:0/004> modem.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELL4_I9300O2UELL1_I9300BWELK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I'm guessing this is a nand issue then? Is my only option at that point the link above (http://forum.xda-developers.com/showthread.php?t=1840030) ?
really don't get it.. tried it again and this time the whole process passed according to odin
same again though, android guy with spinning mesh... nothing for a while
phone eventually goes black, resets, samsung galaxy s3 in black and white. goes black. if i leave it for a while that screen will come up again, then it'll go black etc.
do i bite the bullet and try that method that involves nand reset all? please advise i'm in a bit of a pickle here as i'm in the middle of interviewing for jobs so i could use my phone.. do need to try and fix this asap if i can...
You can try flashing the rescue firmware, search in general forum, but if that doesn't work then you need a new motherboard.
Sent from my GT-I9300 using Tapatalk
ok - that seems to be this one for the s3 - http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
that look right?
downloading now. fingers crossed, thanks for your help i really do appreciate it.
GS II i9100
Note: Warranty is already expired
Before I write anything further, I have been trying to get the most I can out of this thread: http://forum.xda-developers.com/showthread.php?t=1457458
Sadly, I can't seem to wrap my head around this problem, so here goes:
Yesterday I've found out, that the new CM11 came out. Of course I went off to download it, put it in my phone and started to install it through recovery (I had siyah at that time). Well, it failed, must've been corrupt or something, since I got the error status 7. Anyways, while exiting the install screen, siyah asked me, if I want to repair something, because something may have gotten corrupt (Sorry, can't remember the exact thing). Being the sloppy person I am, I clicked yes.
Five minutes later, after going back to stock firmware, because apparently during the install something did go corrupt, and the phone wouldn't boot, only play the boot sound, I've read, that I need the newest CWM for CM11 to work.
Another five minutes later I'm staring at this:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.07.9-i9100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
I've tried changing computers, kicking KIES out through the window, using different USB slots and cables, but to no avail. It just keeps throwing this error at me every time I try to install anything through Odin. The strangest part is, though, that the phone is working perfectly fine.
What could be the problem, and if it is possible, how do I fix it?
Another quick note would be my counter in the download screen of my SII. It's 12 (yeah, I know, I kept forgetting about it, but now, since I'm unable to install anything through Odin, I can't even root the phone and reset the damn thing)
Don't flash nothing to this phone. Be happy it works or get rid of it while it does still works. Seen this before and this is the first stage of mb failure. Trust me don't flash nothing to this phone and get rid of it. If not start reading about the pit file
andrewwright said:
Don't flash nothing to this phone. Be happy it works or get rid of it while it does still works. Seen this before and this is the first stage of mb failure. Trust me don't flash nothing to this phone and get rid of it. If not start reading about the pit file
Click to expand...
Click to collapse
And apparently, this is now happening:
Baseband version - XXMS2
Build - XWLSS
I think I may have messed it up a little...
Please close the thread
This thread can be closed.
Should anyone need this:
After losing patience spending hours on the phone I have decided to JTAG it... Ant it worked. The phone is running like a charm now.
Okay to give the details I have a samsung galaxy note 4 most uptodate version. Earlier today I followed this video.
I cant post links yer but its a video by a guy named wwjoshdew on youtube titled THE EASIEST WAY TO ROOT THE SAMSUNG GALAXY NOTE 4. I would put the link but I cant.
I followed it step by step and made no mistakes and everything happening with his phone was happening with mines until 4:58 in the video. My phone got stuck on that screen while his continued with no issues the only difference is he was using an older version of odin and I was using a newer one. The other difference it our model numbers are almost the same but i have the t3 version and he just has the t version.
Now my phone is stuck on the screen at 4:58 the only thing I can do is hold volume down power and home to navigate to the warning screen. if i volume down to restart phone it simply brings me back to the screen from 4:58. However when i hit volume up I get brought to the downloading screen.
It is impossible for me to go to the recovery screen by holding volume up poer and home it just will not work for whatever reason. I tried downloading the galaxy note 4 2.2 GB stock rom and putting that in odins AP section and hitting start but it fails.
The code log says
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910T3UVU1EPE3_N910T3TMB1EPE3_N910T3UVU1EPE3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on my phone ot says sw rev check fail: aboot fused 2 > binary 1
1 emc write fail aboot.
I dont need root all I want is my precious galaxy note 4 to work again please some smart well educated phone person on here please save my precious note 4 and restore balance and earnesty to my life lol.
Im serious though im devestated over this and after looking at the date of the video and the comment section i see similiar things happened to people who followed this step by step. I didnt do anything wrong so not sure why this is happening please dont tell me its bricked forever please I have no money to get it fixed and need my phone please give me a glimmer of hope somebody please.
Check the model under the battery...Does it have n910T3 or just n910T? I think, for some reason, the firmware is a little different and can cause it to fail.
Another option, if you have the serial number, is to use Samsung Smart Switch for PC in emergency mode.
es0tericcha0s said:
Check the model under the battery...Does it have n910T3 or just n910T? I think, for some reason, the firmware is a little different and can cause it to fail.
Another option, if you have the serial number, is to use Samsung Smart Switch for PC in emergency mode.
Click to expand...
Click to collapse
Thanks but I was able to save it the other day by putting it in download mode and using kies to install the old firmware. Sucks that I lost my porn collection games save data music etc but well at least it works again. I dont need root that bad will never risk again lol.]