[Q] Handset frozen & won't accept re-flash - Galaxy S III Q&A, Help & Troubleshooting

Hi,
Hoping someone can help me, i've searched for a couple of days for answers and tried out suggestions and followed procedures but not getting anywhere so could do with some direct help I think.
Handset details:
Galaxy S3 not locked to any UK network nor does it have any network specific software on it.
Not had any modifications done other than normal OTA software updates and is currently running ICS.
Problem:
Woke up one morning to find the handset frozen on the black & white splashscreen after it being fine the night before and still having plenty of charge. Now won't respond to powering off, just goes blank then returns to splashscreen, only way is to remove battery. Will not respond to normal reset method (vol up + home + power) but will enter download mode (vol down + home + power) and connect to PC.
Attempted solutions:
Have downloaded Odin3 v3.07 along with various firmware .tar files and followed the procedure to reflash the handset but it fails everytime at the 'NAND write' stage.
*Kies is not running at the same time as Odin3
*All drivers are installed and working correctly
*All different USB ports have been tried
*Only have the one USB cable to use
*All settings on Odin3 are correct with regards to checkboxes, etc.
The following is what appears in the message box after each failed attempt: (the <OSM> stages all complete fine)
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialization..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> Boot.img
<ID:0/006> NAND write start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Any help would be much appreciated as I am completely at a loss as to why this has happened considering i've done nothing to the handset with regards to rooting, etc. and I don't really want to send my handset away for repair if I can help it.
Thanks in advance.

Nand fail = service centre repair .
jje

Thanks for the reply, I had a bad feeling that it would need sent away
Any ideas as to why the handset should just stop working all of a sudden? I could understand it if I had tried to install some dodgy software or otherwise mess about with it but there's been no tinkering, no liquid ingress, nothing.

Service center for u buddy.. sorry
Sent from my GT-I9300 using xda premium

Related

[Q] [Problem] Frozen memory?

Hello,
since a few days my GT-P7510 reboots suddenly and falls back into the status before last reboot. That means all settings, copied files/apps are gone and all deleted files/app are restored. It looks like my memory is somehow frozen in a specific status from a few days ago.
I didn't try to root it or something like that. It start all of a sudden.
Thats what I tried so far to solve the problem:
1.Hard Reset with normal method and factory reset with the bootloader (Power button and Volume down menu). No effect at all.
2. Try to root my tab with the manual from this forum. I'm able to flash cwm. At least odin gives no error. But when I reboot cwm isnt flashed. The normal bootloader appears again. So, I have no chance to wipe my tab on this way.
3. Flash stock rom via Odin. That's when I get a Error-Message from odin an my Tab. Error-Message: http://imageshack.us/photo/my-images/822/camerazoom2012062021092.jpg/ But I dont know what it means and havent found it out so far.
I tried several stock roms, read several forums, google etc but no one seems to have a real solution.
I found one guy here http://www.galaxytabforums.net/forum/galaxy-tab-10-1-general-discussions/4260-my-gt-useless-impossible-hard-reset-delete-create-files-etc.html and one guy here in this forum: http://forum.xda-developers.com/archive/index.php/t-1576134.html who have similar problems. But as I said nothing helped yet.
Btw, the data on my tab isnt important so I wouldnt have any problem with a solution which wipes everything. The main thing is that my tab is working properly again. Hopefully one of you experts has an idea.
Thanks in advance
This is pretty weird. Maybe your filesystem is corrupted. You may try to flash a .pit file first. But it could well be a h/w problem. If it's under warranty sent it to Samsung.
Sent from my amazing 10.1 galaxy tab
I tried it with this pit-file: android_fastboot_emmc_full_p4_16G_32G.pit
But I'm not quite sure if its the right one.
In connection with this ROM: P7510XABKMP_P7510UEKMP_HOME.tar, I got those error messages:
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> boot.img
<ID:0/009> NAND Write Start!!
<ID:0/009> bootloader.bin
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And in red on my tab:
Bct_sync_Odin: Error toNvBuBctUpdate![Err:0x140005]
DownloadPartition_Odin: Error to Bct_sync_Odin![err:0x140005]
Tegra_Nand_Write: Error to DowloadPartition_Odin![err:0x140005]
Buildnumber of my tab is HTJ85B.UEKMP P7510UEKMP. So it should be right ROM?
From what I know, you should first use the pit without the rom. Then flash the rom. You should also try a different usb port on your pc and the tab shouldn't be in a dock or a usb hub. That's one of the reasons the flash fails.

[Q] GT-I9300 stuck at Bootlogo, can't flash, what to do next?

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

[Q] Odin Fails When Converting M250S to i9100

I've been trying to convert the firmware on my M250S to I9100. I've followed the guide to the letter and all the drivers are installed as well as Kries. I also made sure Kries was inactive while Odin was up. This is how far I get before it fails.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
If anyone has any ideas I would appreciate it. I've tried everything I can think of including using different firmwares, pits, as well as versions of Odin. That's as far as I get before it fails.
How are you trying to do it? As I recall (I don't have an M250 so didn't pay crazy attention) there's two ways to convert one to an i9100. One involves Odin failing intentionally. Although, the method involving a pit file doesn't intentionally fail. If you're flashing pits and they're failing that's definitely not good... Potential brick.
Search for a guide in the s2 general section, I read one a couple weeks back which members were using with success.
You can also click the link in my signature and follow the steps there. As you're not doing a 'regular' Odin flash bear in mind some things will be a little different.
Sent from a galaxy far, far away
I actually was following this guide http://forum.xda-developers.com/showpost.php?p=30976988&postcount=1182
I swapped usb cables and it got to nand write this time before it failed. Now my phone stays in page that says upgrade with a samsungmobile.com link. I can still get into download mode.
Edit: I tried another computer and it worked flawlessly. So now I'm running on i9100. Although I'm having a few issues. It doesn't show my battery charging when the usb is plugged in. Also when I shut down my phone it doesn't completely shut down. It goes to a screen with a green battery. This actually happened before but I thought perhaps changing firmware would fix it. Before this the device would come back on automatically when I tried to shut it down and I read it could be the usb port so I cleaned the usb port with alcohol.
Slywolf15 said:
I actually was following this guide http://forum.xda-developers.com/showpost.php?p=30976988&postcount=1182
I swapped usb cables and it got to nand write this time before it failed. Now my phone stays in page that says upgrade with a samsungmobile.com link. I can still get into download mode.
Click to expand...
Click to collapse
Ah so it may not be a case of what you're trying to do, it might be a case of how the flash is set up/what hardware (pc, cable etc) you're using. In that case, use the link in my signature to troubleshoot it. Perseverance is key. Also have a look here : http://forum.xda-developers.com/showthread.php?p=45131292
It might be because of bad rom , try with another one [You can check my guide here , I provide 100% working stock rom.]
ZivC12 said:
It might be because of bad rom , try with another one [You can check my guide here , I provide 100% working stock rom.]
Click to expand...
Click to collapse
No it's working now and I flashed the firmware successfully. My main problems now are now my s2 won't charge through the usb anymore and when I shut down the phone, instead of shutting down, it brings up the green battery screen with the little white dots below it.
Slywolf15 said:
No it's working now and I flashed the firmware successfully. My main problems now are now my s2 won't charge through the usb anymore and when I shut down the phone, instead of shutting down, it brings up the green battery screen with the little white dots below it.
Click to expand...
Click to collapse
it happened to me with bad uk unbranded rom, try to flash new rom, if you cant turn on the phone switch battery

[Q] Galaxy Beam i8530, rooted, stuck at logo-screen

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......

[Q] Bricked S3 I9300 / Boot Loop / S3 Logo

Hello everyone
I apologize if you think this looks like a duplicate question but I could not find exact same features about my problem.
I've been trying to fix my phone for 2 days now so I thought I could ask for help to see if there is anything to do for my phone.
What happened just before :
I was using cyanogenmod 13 nightly and updated. It worked like a charm even fixing the camera.
I plugged it on the wall to charge and left my apartment. Sadly a storm went for 15 min before I got back to my apartment.
From this time, the phone was stuck on S3 logo.
What works right now :
I can go into download mode, the phone is recognized by computer
Info displayed are : odin mode / Product name : GT-I9300 / Custom binary download : yes (3 counts) / Current binary : custom / System status : custom
I can access recovery, I use TWRP 3.0.0-2
Touch is working well, but like other people I've got the mount error about storage, 0mb is displayed for any storage, and can't wipe or format data to fix it.
I can charge the battery as usual
What I tried to fix :
I tried using odin to flash custom rom, then stock rom 1 file from sammobile (several), even pit re-partition checking right boxes, sadly message is always :
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1101)..
<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> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried to use Heimdall too, with 3 different zadig drivers, I could download my pit several times, but could not flash : most of the times there was no response, handshake error, libusb error or protocol fail.
I tried several cables, and several usb plugs. Phone is always recognised by computer but can never transfer.
I tried to flash from micro sd card via twrp, but the 0mb displayed error prevented me from accessing the card.
I feel that my phone could still work, but I need advices on what to try next, and of people could diagnose the state of my phone, I might have forgotten some steps I completed, and really hope someone can help me try something new or tell me what's wrong with it.
Thanks in advance for your help, feel free to ask for any info I might have forgotten to write here.
Sun of rays from south of France, take care,
Emy -`ღ´-
Bump
Can somebody make a diagnosis about the state of the phone?
Do I need to change the motherboard?
Any help appreciated !
@eyrtv, you can try to repartition by flashing 4part-firmware with PIT-file.
You can flash alone system.img, sboot.bin. ect using odin? Did command make_ext4fs /dev/block/mmcblk0p9 ect. work for you ?
Dead nand imo if 16gb
Use last twrp
https://www.androidfilehost.com/?fid=24499762636003755
try to flash with this firmware sir.
rp158 said:
@eyrtv, you can try to repartition by flashing 4part-firmware with PIT-file.
Click to expand...
Click to collapse
Hey, thanks for yout suggestion
Already tried that sadly
asadnow2k said:
https://www.androidfilehost.com/?fid=24499762636003755
try to flash with this firmware sir.
Click to expand...
Click to collapse
Hey thanks for the suggestion
I downloaded this firmware, but now here is another problem, my phone stayed for 1 month + in my drawer with the battery in... My phone did not charge, for 2 minutes the screen reacted and I thought it was ok, then I tried to trun it on too soon, now does not charge at all... Im going to let it charge for hours now, and hope it will react...
If works than fine or try to get a test with new battery
Sent from my iPhone using Tapatalk

Categories

Resources