Related
When I try to turn my phone on it shows the image of a cellphone a orange triangle with ! in it and a computer. What did I do? Please help!
No. you're not bricked. It just failed during an Odin flash.
Here's how to fix it.
http://forum.xda-developers.com/showthread.php?t=1052813
That was what I did originally to get to this point. It gets stuck at set pit file
Is there anyway to fix it with cwm?
Give it another try. This time don't use the pit file. Just the SPH-D700-EC05-8Gb-REL.tar file in the PDA section and make sure there's a check next to it. Also, under option, just have "auto reboot" checked. Leave "re-partition" and "reset time" blank.
Before you posted your last message, i tried doing it again I got further but than my screen turned red and hung for 15 minutes. I pulled the battery and now my phone wont turn on at all. I cant even get it to dl mode
Read the unbrick post in delv sec than watch the videos from qbking77 before you do anything else and you wont have any problems.
Then thank qbking77 for educating the epic community on proper install procedures
I was going off that post when all of this happened. Doesnt matter now anyway it wont even turn on now. Tomorrow I have to go to the sprint store and hope they wont be able to know I was trying to flash.
thegameksk said:
I was going off that post when all of this happened. Doesnt matter now anyway it wont even turn on now. Tomorrow I have to go to the sprint store and hope they wont be able to know I was trying to flash.
Click to expand...
Click to collapse
Try pulling out the SD card and battery, then put battery back in and boot into download mode without SD card.
Might take a few tries with removing the battery.
Ill try that. If that doesnt work do you think sprint wud be able to tell that odin didnt flash correctly/ Should I just call and say my phone was lost?
Also even if I plug it into the wall with battery in phone it doesnt show red light on that shows its charging.
thegameksk said:
Ill try that. If that doesnt work do you think sprint wud be able to tell that odin didnt flash correctly/ Should I just call and say my phone was lost?
Also even if I plug it into the wall with battery in phone it doesnt show red light on that shows its charging.
Click to expand...
Click to collapse
If it's a true brick, even sprint techs won't be able to get it to power on/boot, in which case, they won't know what's on it. If it's still under the 1 year manufacture's warranty, in most cases, it normally cost $35 for a replacement or free if you're lucky, YMMV tho.
Hope things work out for ya, I've felt your pain before my friend.
Dont give up sometimes just sitting for a couple hours with no battery helps.
I got this while trying to odin the new EF## or whatever...
I tried to reset it and it didnt work, i tried odin'ing the EC05 tar and pit and it didnt work, it stuck...
Then i got the EB13 tar and pit and odin'd and it worked
Try checking repartition in odin, could have possibly been checked during the bad odin session and doing it again should clear it up. Use the stock ef02 tar not the pre rooted one
Sent from my SPH-D700 using XDA Premium App
I was on the FK23 rom for a while, and everything was working perfectly. However, last night, I ran a white noise machine app from my phone while it was on the charger all night.
When I went to unlock the phone this morning, it wouldn't unlock, so I pulled the battery, and it started to bootloop. It would do the Galaxy SII screen, then the Sprint bootup, then it would play the Sprint boot down animation. Over and over.
So I tried flashing FL16 with ODIN, and when I do that, it gets stuck on hidden.img and doesn't do anything. Then I tried flashing EL29 with ODIN, and it gets stuck on recovery.bin and doesn't do anything. I have used multiple PCs and multiple cables. WHAT AM I DOING WRONG?! I just want my phone to work T_T
anchor_th said:
I was on the FK23 rom for a while, and everything was working perfectly. However, last night, I ran a white noise machine app from my phone while it was on the charger all night.
When I went to unlock the phone this morning, it wouldn't unlock, so I pulled the battery, and it started to bootloop. It would do the Galaxy SII screen, then the Sprint bootup, then it would play the Sprint boot down animation. Over and over.
So I tried flashing FL16 with ODIN, and when I do that, it gets stuck on hidden.img and doesn't do anything. Then I tried flashing EL29 with ODIN, and it gets stuck on recovery.bin and doesn't do anything. I have used multiple PCs and multiple cables. WHAT AM I DOING WRONG?! I just want my phone to work T_T
Click to expand...
Click to collapse
Do a factory restore and wipe then odin one click stock EL29 and start from scratch.
I can't do a factory restore. When I hold Vol up + power, it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
:edited: Didn't see your response to graydiggy
Redownload a complete one click, verify md5 and try putting the phone in download mode and attempting again. It's possible that your download was bad.
so is there nothing I can do?
By technicality, that is not a brick. You should be able to flash from that message. That was the case with the Samsung Captivate.
I downloaded EL29 and verified it again. It is doing the same thing. stuck on recovery.bin
I also tried flashing from that message just now. Same thing. ODIN gets stuck on recovery.bin
thanks for the help but I think it's ****ed. something might have messed up in the filesystem and that's why ODIN gets stuck maybe.
anchor_th said:
I downloaded EL29 and verified it again. It is doing the same thing. stuck on recovery.bin
I also tried flashing from that message just now. Same thing. ODIN gets stuck on recovery.bin
Click to expand...
Click to collapse
Ok, so I found a solution by sfhub that worked for someone from a while ago. Try using pc odin to flash each piece seperately. Modem, kernel, then rom..
Here's my ref:
See post #9 http://forum.xda-developers.com/showthread.php?t=1492771
I'll see if this works. Hopefully it does, I'm ready to toss the thing out of a window, haha
edit: noob question, how do I flash the .md5 files? I downloaded odin multi downloader but the phone doesn't show up in it.
edit 2: okay nevermind I figured it out, it seems to be flashing
edit 3: so modem flashed just fine and the phone rebooted but when I try kernel it loads the green bar all the way on odin then it freezes...
edit 4: so I think my phone's flash memory might be screwed somehow. I've been reading other threads and someone had a similar problem as me and couldn't fix it.
anchor_th said:
I'll see if this works. Hopefully it does, I'm ready to toss the thing out of a window, haha
edit: noob question, how do I flash the .md5 files? I downloaded odin multi downloader but the phone doesn't show up in it.
edit 2: okay nevermind I figured it out, it seems to be flashing
edit 3: so modem flashed just fine and the phone rebooted but when I try kernel it loads the green bar all the way on odin then it freezes...
edit 4: so I think my phone's flash memory might be screwed somehow. I've been reading other threads and someone had a similar problem as me and couldn't fix it.
Click to expand...
Click to collapse
Have you flashed all three pieces before trying to let the phone boot completely? Once you flash the first piece and it restarts, Just hold power+vol down and get back into download. Do that until you have all three segments flashed. Then try letting it boot.
I flashed the modem, it worked, then I rebooted back into download. Then I tried flashing kernel and the bar on ODIN filled up but then it froze and did nothing. I let it sit for about 10 minutes and it still did nothing. so I tried skipping that and flashing the rom and the bar on ODIN moved barely then froze. Like I said, I think my phone's flash memory got messed up somehow. :\
anchor_th said:
I flashed the modem, it worked, then I rebooted back into download. Then I tried flashing kernel and the bar on ODIN filled up but then it froze and did nothing. I let it sit for about 10 minutes and it still did nothing. so I tried skipping that and flashing the rom and the bar on ODIN moved barely then froze. Like I said, I think my phone's flash memory got messed up somehow. :\
Click to expand...
Click to collapse
Then there may be one more thread that might help if that's the case.
Kernel is only the zimage file. Hang on, let me find it.
:edit: Maybe this will help you. If not, maybe graydiggy or someone else has some ideas.
With this, you'll have to see if you can't flash a custom recovery. From the sound of it, it may not be helpful at all.
http://forum.xda-developers.com/showthread.php?t=1865102
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
Yeah, I don't think there's a way to do that since I can't access ADB...
anchor_th said:
Yeah, I don't think there's a way to do that since I can't access ADB...
Click to expand...
Click to collapse
http://mobiletechvideos.mybigcommerce.com/samsung-epic-4g-touch-jtag-brick-repair/
I'll try that as a last resort. I'm going to a Sprint store tomorrow and I'll see what they tell me. I just might use all this as an excuse to finally get a Note II.
anchor_th said:
I'll try that as a last resort. I'm going to a Sprint store tomorrow and I'll see what they tell me. I just might use all this as an excuse to finally get a Note II.
Click to expand...
Click to collapse
They will probably know you borked it by trying to flash. If they can get to a recovery to see if you have flashed anything, you are screwed.
Do you by chance have a USB Download Mode JIG?
No, I don't. My download count in download mode is at 1, too.... so they probably won't fix it... but I might get lucky. Who knows.
edit: the messed up thing is I don't really know what messed it up. it worked fine for about a month on FK23, then boom, this morning it won't unlock and bootloops when I pull battery. before I tried flashing it, it wouldn't even go into recovery. when I held vol up + power, it just went to the Samsung screen and rebooted over and over
anchor_th said:
No, I don't. My download count in download mode is at 1, too.... so they probably won't fix it... but I might get lucky. Who knows.
edit: the messed up thing is I don't really know what messed it up. it worked fine for about a month on FK23, then boom, this morning it won't unlock and bootloops when I pull battery. before I tried flashing it, it wouldn't even go into recovery. when I held vol up + power, it just went to the Samsung screen and rebooted over and over
Click to expand...
Click to collapse
I have a theory... Give it a couple hours of plug in time without turning it on or trying to flash. Just give it like 3 hours and see if you can flash from there. You may have a battery that is low and it could be resulting in your problem of not being able to flash.
the battery was also on the charger all night... but I'll plug it in. is it charging even though it is on the connect to kies screen?
anchor_th said:
the battery was also on the charger all night... but I'll plug it in. is it charging even though it is on the connect to kies screen?
Click to expand...
Click to collapse
Just keep it completely powered off and use the normal wall charger.
I have created this thread for all you SG-SIII Noobs & Senior Members!
The purpose of this thread is to limit the number of (sometimes useless) threads, that are created over a simple problem that can easily be solved by READING OR SEARCHING.
This is the Emergency thread!
*Did you run into a problem and need quick assistance?
*Do you have a question or concern about your SG-SIII device?
Don't panic just ask here and I or WE THE SG-SIII COMMUNITY will gladly help!
In case of emergency!
Okay I guess I'll be the first to post.
About an hour ago my phone shut off at 26% battery (16gb galaxy S3 running CM10.1 nightly 01/16). As I went to turn it back on it will boot into the CM splash screen spin a few times and just shut off. I attempted to charge it, and turn it back on but same thing. After that an attempt to get into CWM, which I was able to get in and it shut off while I was in it. I also tried putting the phone in download mode and about the same time frame it took for the other attempts resulted in a shut down.
Any advice? Or am I stuck doing a warranty exchange?
Rayman0625 said:
Okay I guess I'll be the first to post.
About an hour ago my phone shut off at 26% battery (16gb galaxy S3 running CM10.1 nightly 01/16). As I went to turn it back on it will boot into the CM splash screen spin a few times and just shut off. I attempted to charge it, and turn it back on but same thing. After that an attempt to get into CWM, which I was able to get in and it shut off while I was in it. I also tried putting the phone in download mode and about the same time frame it took for the other attempts resulted in a shut down.
Any advice? Or am I stuck doing a warranty exchange?
Click to expand...
Click to collapse
Sounds like its your battery not a hardware problem. Leave it overnight or a couple hours charging and if it indeed boots up its your battery.
If it doesn't then flash stock and test it if the same result then call up that Warranty. I've seen this same issue with other devices where the battery dies at 50%+ and usually replacing the battery fixes the problem. Test your battery for overheating or swollen.
Sent from my HTC One S using Tapatalk 2
...Awesome... said:
Sounds like its your battery not a hardware problem. Leave it overnight or a couple hours charging and if it indeed boots up its your battery.
If it doesn't then flash stock and test it if the same result then call up that Warranty. I've seen this same issue with other devices where the battery dies at 50%+ and usually replacing the battery fixes the problem. Test your battery for overheating or swollen.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
The battery isnt swollen, thats one of the things I checked also. I thought it might be that, the only other option I have is to try a different battery. The good thing is I work in a tmobile store so im gonna give that a shot tomorrow.
Sv: ***Emergency Thread*** Here To Help!
Can you start it without battery connected to the wall charger? If so try wipe cache. Or after reflash ROM.
Sent from my LG-P990 using xda app-developers app
lintz said:
Can you start it without battery connected to the wall charger? If so try wipe cache. Or after reflash ROM.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Phone wont boot without the battery in, and with it in I cant stay in recovery without with rebooting.
Rayman0625 said:
The battery isnt swollen, thats one of the things I checked also. I thought it might be that, the only other option I have is to try a different battery. The good thing is I work in a tmobile store so im gonna give that a shot tomorrow.
Click to expand...
Click to collapse
Even better then lol just test it out at work. I'm about 80% its your battery specially if you OV/UC.
I have the t-mobile US t999.
Last night I was having an odd issue with the networking dropping. I've had the phone for about a month, modded since day 1 with a CM10 variation of a rom (sorry, I forget the exact rom). I had no issues whatsoever up until this point. After a few restarts thinking maybe it was a fluke issue with the network, or network signal in my room, the phone forced itself into emergency call mode only. I couldn't get it to come out.
So I decided I was going to odin on a stock rom as I could get it into download mode, that went through successfully. When the phone boots, I get the android taking off (Tmobile 4g) logo. Then the white samsung logo, and it doesn't go beyond this. I know this can take long so I left it there for about an hour, nothing. The phone also displays a blue led the entire time it's hanging as well.
Also worth noting, when I attempt to boot into recovery it just vibrates over and over.
Not sure what my next steps should be. Any help would be greatly appreciated.
heartspains88 said:
I have the t-mobile US t999.
Last night I was having an odd issue with the networking dropping. I've had the phone for about a month, modded since day 1 with a CM10 variation of a rom (sorry, I forget the exact rom). I had no issues whatsoever up until this point. After a few restarts thinking maybe it was a fluke issue with the network, or network signal in my room, the phone forced itself into emergency call mode only. I couldn't get it to come out.
So I decided I was going to odin on a stock rom as I could get it into download mode, that went through successfully. When the phone boots, I get the android taking off (Tmobile 4g) logo. Then the white samsung logo, and it doesn't go beyond this. I know this can take long so I left it there for about an hour, nothing. The phone also displays a blue led the entire time it's hanging as well.
Also worth noting, when I attempt to boot into recovery it just vibrates over and over.
Not sure what my next steps should be. Any help would be greatly appreciated.
Click to expand...
Click to collapse
after you odin, you need to wipe data/ factory reset to boot. If you can't get into recovery ( Power, Home Button, and Volume Up), then try reflashing your stock image in Odin and check your MD5 sum, so you can rule out a bad download
Thanks for the reply, I'm re-downloading the stock rom now to verify it's integrity and do a new flash. I cannot get into recovery, so we will see after the new flash. Pleading ignorance on one subject, how would I go about checking the MD5 sum to verify the file has no issues?
Additionally I did try to Odin recovery and still could not boot into it, this was however before attempting to re-download and flash a stock rom again.
**Edit//Update** Re-downloaded and flashed stock rom, was able to get into recovery and wipe, booted up fine.
Wow.. great idea for a thread and THANK YOU!!
Perfect timing too cause i need a little help please.
I am not new to android but new to samsung (WOW, didnt realize it would be so different from HTC ont he rooting and flashing side of things).
Long story short. I have a tmo s3. Bought it today and wanted to root. phone was working perfectly as it shoudl on stock rom unrooted. I downloaded the tool kit v7, used that to root adn install TWRP and rebooted into the stock rom that is now rooted. Still everything working perfect.
Here is what i did next and where the issues start.
Downloaded Synergy r290, went to recovery.
Wiped Cache, Dalvik, Data, and System (made a backup first)
flashed the rom and rebooted to system
However, nothing ever happened. I see the samsung logo, then all goes black and nothing happens (left it there for 10min)
I cant seem to get back into recovery holding vol up, home and power either and have no adb access to use that. I AM able to get into download mode which i know i can fix my problem here with odin, but i am just not sure what to flash and where.
Is there an easier way??
Thanks in advance for any help!
frettfreak said:
Wow.. great idea for a thread and THANK YOU!!
Perfect timing too cause i need a little help please.
I am not new to android but new to samsung (WOW, didnt realize it would be so different from HTC ont he rooting and flashing side of things).
Long story short. I have a tmo s3. Bought it today and wanted to root. phone was working perfectly as it shoudl on stock rom unrooted. I downloaded the tool kit v7, used that to root adn install TWRP and rebooted into the stock rom that is now rooted. Still everything working perfect.
Here is what i did next and where the issues start.
Downloaded Synergy r290, went to recovery.
Wiped Cache, Dalvik, Data, and System (made a backup first)
flashed the rom and rebooted to system
However, nothing ever happened. I see the samsung logo, then all goes black and nothing happens (left it there for 10min)
I cant seem to get back into recovery holding vol up, home and power either and have no adb access to use that. I AM able to get into download mode which i know i can fix my problem here with odin, but i am just not sure what to flash and where.
Is there an easier way??
Thanks in advance for any help!
Click to expand...
Click to collapse
If you absolutely can't get into recovery to restore your backup..
Flash the UVDLJA root66 file in this thread http://forum.xda-developers.com/showthread.php?t=1949687 via odin. You will have the latest UVDLJA JB update, and will be rooted. From there, install goo manager from the play store to flash TWRP.
After that you're all set to flash whatever you want (just make sure it's for the Tmobile s3).
Sent from my SGH-T999 using Tapatalk 2
Towle said:
If you absolutely can't get into recovery to restore your backup..
Flash the UVDLJA root66 file in this thread http://forum.xda-developers.com/showthread.php?t=1949687 via odin. You will have the latest UVDLJA JB update, and will be rooted. From there, install goo manager from the play store to flash TWRP.
After that you're all set to flash whatever you want (just make sure it's for the Tmobile s3).
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Ok, easy enough, but do i put that in the PDA field in Odin or phone?
This sounds MUCh easier than what i thought i would have to do.. thanks a ton!
frettfreak said:
Ok, easy enough, but do i put that in the PDA field in Odin or phone?
This sounds MUCh easier than what i thought i would have to do.. thanks a ton!
Click to expand...
Click to collapse
Just upload the file to PDA and hit start. Make sure to let it finish completely, once the phone reboots, it's done.
Sent from my SGH-T999 using Tapatalk 2
Flashing stock with Odin can take up to ten minutes its normal like the man said above just let it do its thing
Towle said:
Just upload the file to PDA and hit start. Make sure to let it finish completely, once the phone reboots, it's done.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Worked great! Thanks!!
http://forum.xda-developers.com/showthread.php?t=2113883
Let's see if you have any solution for me?
Weird problem. When I set kernel frequencies on my phone, they at some point get locked at the maximum frequency. This has happened every time I flash a new ROM or kernel, and I'm worried that it will soon start to affect the battery. I'm using the msmdvcs governor on both kernels that I've tried (stock and faux)
ohshootrawr said:
Weird problem. When I set kernel frequencies on my phone, they at some point get locked at the maximum frequency. This has happened every time I flash a new ROM or kernel, and I'm worried that it will soon start to affect the battery. I'm using the msmdvcs governor on both kernels that I've tried (stock and faux)
Click to expand...
Click to collapse
Do u happened to have apps that control frequency like setcpu etc? They might be conflicting each other
Sent from my HTC One S using Tapatalk 2
I'm trying to help a friend fix his S3 - model sgh-i747m - and have run into much bigger problems. Here's how it started.
He came to me with his S3 and showed me that it won't successfully complete its bootup. It passes all the logos, even the sound/animated Samsung splash screen. And then it stops there, hangs indefinitely. The LED still pulsates between dark and light blue.
I did some research about the problem and found that this should have easily been fixed by reapplying a stock rom. I should mention that the phone's built in recovery methods did not succeed, I tried those first. So I downloaded Odin3_v3.07_SGSIII as well as two versions of the stock rom for his Telus device; 4.1.2 and 4.3. I had read that you must flash the 4.1.2 before trying to flash the 4.3, so to play it safe (my friend doesn't know what version it was) I started with the 4.1.2.
I have used odin before. with my brand new Galaxy Note 3 in fact, and it worked amazingly fine. This time it wasn't working so well though. I started by making sure the drivers were installed. I booted the S3 into download mode, and connected it with the original USB cable, to a motherboard USB port on the back of my computer. All this time Odin was running and waiting, and everything was going as planned. Put the rom in the PDA loading area, and clicked start. Then things went fine, until it failed to 'write', whatever that meant. The progress bar on Odin and the device was stuck at half now. I let it sit for a while and observed no change. I idly clicked on the odin window and got the sad Windows fade-to-white effect, it had froze. Nothing I could do to unfreeze it, I let windows collect its crash data and relaunched Odin. I reconnected the phone but this time, almost instantly, the 'failed firmware' message popped up.
Did a little more googling at that point and found that it still should be able to proceed normally. So I tried again, with the same process. Booted into download mode, with Odin reset and running, with the PDA file ready to start loading.. But this time, Odin stops at "Initializing" and won't go any further.
Back to google some more. I tried various tricks some people suggested, like leaving the battery out, or putting the battery back in when Odin sees the device, and reinstalling the USB drivers, rebooting the PC, trying every different port I have.. And every single time it just gets stuck at "Initializing"
At this point I'm at a loss. My friend was already ready to write the phone off, but everything I've read tells me its still recoverable. Its not a hard brick, its only soft-bricked from what I can tell. I can still go into Download mode. Just something is being stubborn or difficult now.
So after about 4 straight hours of trying to figure it out on my own, searching the forums here there and everywhere, I decided to give in and ask for help. I hope you guys can lead me in the right direction and get this thing back up and running. I'm open to any helpful tips, suggestions, links or downloads, tools, whatever it takes to make it work again.
Since you could not load a stock 4.1.2 image using desktop Odin, sounds like the phone has been updated to 4.3 ROM with a stock 4.3 bootloader; therefore, you cannot flash any stock ROM via desktop Odin that tries to downgrade the bootloader.
Try this: download and install a pre-rooted Telus 4.3 image from here: http://forum.xda-developers.com/showthread.php?t=1739426 via desktop Odin. Do not check auto reboot. Once you see the word reset in the window, pull the battery, go into stock recovery, wipe/factory reset, and boot the phone.
Good luck.
audit13 said:
Good luck.
Click to expand...
Click to collapse
Well, luck seems to be against me this time. I tried what you said, then Odin spits out a missing PIT error. I found the PIT file for this device, and tried following the steps documented for applying it. And then it spits out a Complete(Write) fail at me. I decided to try this all from a different computer in my house. So I got everything all set up, went to boot the phone into download mode... and now it won't even do that. I thought maybe the battery was too low, but when I plug it in without the battery, just a red LED shows up. Can't do anything with it now.
So at this point, do I just give up? Seems the only possibility now would be a JTAG service.
steven_archer said:
Well, luck seems to be against me this time. I tried what you said, then Odin spits out a missing PIT error. I found the PIT file for this device, and tried following the steps documented for applying it. And then it spits out a Complete(Write) fail at me. I decided to try this all from a different computer in my house. So I got everything all set up, went to boot the phone into download mode... and now it won't even do that. I thought maybe the battery was too low, but when I plug it in without the battery, just a red LED shows up. Can't do anything with it now.
So at this point, do I just give up? Seems the only possibility now would be a JTAG service.
Click to expand...
Click to collapse
Maybe the battery has been depleted. Leave it on a charger for a while and try again.
steven_archer said:
Well, luck seems to be against me this time. I tried what you said, then Odin spits out a missing PIT error. I found the PIT file for this device, and tried following the steps documented for applying it. And then it spits out a Complete(Write) fail at me. I decided to try this all from a different computer in my house. So I got everything all set up, went to boot the phone into download mode... and now it won't even do that. I thought maybe the battery was too low, but when I plug it in without the battery, just a red LED shows up. Can't do anything with it now.
So at this point, do I just give up? Seems the only possibility now would be a JTAG service.
Click to expand...
Click to collapse
Try to give it a bit to charge but it sounds like you have a hard brick now... You might be able to use a debrick SD card.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
---------- Post added at 02:52 PM ---------- Previous post was at 02:46 PM ----------
Try this If you did or think you had 4.3 bootloaders http://forum.xda-developers.com/showthread.php?t=2549068
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
---------- Post added at 03:01 PM ---------- Previous post was at 02:52 PM ----------
If you can get into download mode again you should visit www.sammobile.com (you need a username to download firmware from that site but they are a trusted source.) because you have an I747M you can probably find an appropriate Odin flash able stock tar just make sure it is for the correct carrier phone version.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I have a very strange problem with this device (g920p), Backstory: i got it with the screen broked so i replaced it. There was no problem until the sound stopped working. I pressed vol - and power button but it never came to life.
What i did / Result:
Hard Reset (wipe cache and data, cache partition). / Same status Softbricked
Installed custom recovery and wiped out caches dalvik. / Still Bricked
Download and installed stock ROMS: CPD2, CPB6 (6.0.1) / After the odin procedure, it reboots and then it updates system, later says "optimizing apps" and when finish the phone stucks at "Starting Apps" (for hours) and it never starts. If i reboot it, after the samsung logo it just shows blue light blinking but the screen stays black.
I have downgraded to almost all 5.1.1 ROMS / Same result as above.
I have installed almost all ROMS after wipes (with stock recovery and custom) / no sucess.
I have tried to recover it with Smart Swich but i cant get the s/n, barcodes only shows MEID but no serial.
I have left the battery die then i do all the previuos trys with no sucess, i can just get to "Android is Upgrading - starting apps" screen.
I have tried installing custom kernels after rom installs / NO luck.
Safemode does nothing.
Any clues to get my s6 back to life?
If it's the 32gb version, I recommend flashing the pit file found in the general section.
Sent from my SM-G920P using Tapatalk
elesbb said:
If it's the 32gb version, I recommend flashing the pit file found in the general section.
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
Yep its the 32gb varient, i cant locate the pit file.
elesbb said:
If it's the 32gb version, I recommend flashing the pit file found in the general section.
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
i found "ZEROFLTE_USA_SPR.pit" and i got the same result, shows the samsung logo then the screen goes black, it stucks at Starting apps screen.
pablitokio said:
i found "ZEROFLTE_USA_SPR.pit" and i got the same result, shows the samsung logo then the screen goes black, it stucks at Starting apps screen.
Click to expand...
Click to collapse
You need to make sure you are flashing the proper stuff. You can't just go throwing random sh*t at it.
This is the proper PIT for your device: https://www.androidfilehost.com/?fid=24499762636008230
If you were to look through the thread, specifically the general section, as I mentioned, you would have found it
Flash the PIT file by selecting "PIT" inside odin and NOTHING else. Then reboot and flash the stock tar.
elesbb said:
You need to make sure you are flashing the proper stuff. You can't just go throwing random sh*t at it.
This is the proper PIT for your device: https://www.androidfilehost.com/?fid=24499762636008230
If you were to look through the thread, specifically the general section, as I mentioned, you would have found it
Flash the PIT file by selecting "PIT" inside odin and NOTHING else. Then reboot and flash the stock tar.
Click to expand...
Click to collapse
Thanks a lot, i did look for it and found the other one. After flashing the PIT i flashed the .tar (CPB6) and the result was the same, blackscreen with blue light dimming intermitent. This time the "optimizing apps screen" didnt show up. i havent touched the device yet, im waiting for the optimization screen to show up. Im waiting 30min if it doesnt works im gonna reboot the device and do the wipes and reboot.
elesbb said:
You need to make sure you are flashing the proper stuff. You can't just go throwing random sh*t at it.
This is the proper PIT for your device: https://www.androidfilehost.com/?fid=24499762636008230
If you were to look through the thread, specifically the general section, as I mentioned, you would have found it
Flash the PIT file by selecting "PIT" inside odin and NOTHING else. Then reboot and flash the stock tar.
Click to expand...
Click to collapse
Didnt work but i realized now it has no IMEI or MEID.
pablitokio said:
Didnt work but i realized now it has no IMEI or MEID.
Click to expand...
Click to collapse
Let it die completely. Once it dies attempt to boot into download mode until it wont anymore (completely dead), charge to about 15%, reboot. Should be fixed. If not retry. What happened I think is the minute reboot with no signal/baseband/imei etc., except you flashed a rom or something to try to fix it so now it appears to bootloop but really is doing the same minute automatic reboot no signal issue. I had same happen to me when i flashed a rom trying to fix it, it "bootlooped", but being the first boot taking the standard additional time it never made it to the full boot up, until letting it die, then all was good. Nothing else is needed except complete drain of battery
droseofc said:
Let it die completely. Once it dies attempt to boot into download mode until it wont anymore (completely dead), charge to about 15%, reboot. Should be fixed. If not retry. What happened I think is the minute reboot with no signal/baseband/imei etc., except you flashed a rom or something to try to fix it so now it appears to bootloop but really is doing the same minute automatic reboot no signal issue. I had same happen to me when i flashed a rom trying to fix it, it "bootlooped", but being the first boot taking the standard additional time it never made it to the full boot up, until letting it die, then all was good. Nothing else is needed except complete drain of battery
Click to expand...
Click to collapse
Thank you im gonna try this for sure. I have worked all day long with this device. and i am not giving up until it totally die or work.
UPDATE (Battery not drained yet):
I realized about some things when i flash the stock rom, after odin finish the phone shows a screen that says "updating system" a progress bar loads but only reaches to 32% then says Erasing and reboots, then just hangs at "starting apps" screen.
Same result as previous ones. Stucked at "Starting Apps". After the flash .pit file, i flash the .tar, then when finish the devices reboots and the screen shows a progress bar that reads "Installing system update" but it only reaches to 32%.
That is odd. Did the sound ever come back? Maybe it has something to do with the hardware fix. Wherever you got the replacement from were there any reviews that may indicate others having similar issues or contacting whoever u got it from? If the sound stopped working and then you reset it and etc and now its not booting fully up maybe it does some type of hardware check and reboots if and when it fails.. idk truthfully, if it were me Id go back to looking at the screen replacement
i'll try doing all the previous steps but with the original screen. i'll update the post ASAP
My g920p got exactly the same problem. It die for 2 weeks. I try every thing i can but it can't get out of "starting apps". So i place it in my desk until today i boot it up and actually, it start. Still have no sound, but when it check for update and i press update now, the "starting apps" loop show up. Have you fixed your phone yet?
Sorry for my bad English.
It looks like you really did a number on it!
Good Luck!
Help
Does anyone have the same problem???
Samsung S6- G920P impossible to Fix
Had same problems with my G920P and nobody even replied to my cry for help....thanks guys! No really,without help i had to learn the hard way. Anyways, I flashed the Pit file then flashed a boot file, then a modem file, then last but not least the complete Home tar. Let me know if this works for you. According to my G920P it took me 48 days, and very long nights to get it back up and running. Hard bricked a Galaxy S7 in the process........next project i guess!
Samsung S6- G920P impossible to Fix
Had same problems with my G920P and nobody even replied to my cry for help....thanks guys! No really,without help i had to learn the hard way. Anyways, I flashed the Pit file then flashed a boot file, then a modem file, then last but not least the complete Home tar. Let me know if this works for you. According to my G920P it took me 48 days, and very long nights to get it back up and running. Hard bricked a Galaxy S7 in the process........next project i guess! Having trouble uploading those files to you but i will get them out tonight. By the way, theyre PI3 files. i was on PB6 but the only thing that worked was to bump up a couple versions.
Mrm35150 said:
Had same problems with my G920P and nobody even replied to my cry for help....thanks guys! No really,without help i had to learn the hard way. Anyways, I flashed the Pit file then flashed a boot file, then a modem file, then last but not least the complete Home tar. Let me know if this works for you. According to my G920P it took me 48 days, and very long nights to get it back up and running. Hard bricked a Galaxy S7 in the process........next project i guess! Having trouble uploading those files to you but i will get them out tonight. By the way, theyre PI3 files. i was on PB6 but the only thing that worked was to bump up a couple versions.
Click to expand...
Click to collapse
bro, im having the same problem, can u elaborate step by step how you did it?
RadarZgin said:
bro, im having the same problem, can u elaborate step by step how you did it?
Click to expand...
Click to collapse
I will get the files together and get them to you
Mrm35150 said:
I will get the files together and get them to you
Click to expand...
Click to collapse
thanks bro