Related
I've checked the other threads for solutions and I've tried many different things today but my phone still doesn't work, so I guess I should make a thread and ask you guys directly.
Ok, so my phone stopped working last night. It was running stock everything. Only upgraded to Froyo through Kies Mini a long time ago. Anyway, when I powered up the phone, it gets to the Galaxy S logo and then the screen dies. It's technically still on, since the four keys light up when I tap the screen. I took the battery out for a bit and put it back in, same thing. Logn story short, I tried to odin it back to stock JFD this morning and it didn't change anything. The screen goes to black right after the logos. Then I tried Eugene's Vibrant_Full_Froydin_AND_2E_Recovery_+SD_Fixed. It sorta worked. By that I mean, the phone loads up the OS and I got the home screen, but now it doesn't recognize the internal SD card. In fact, the notification gives me "Blank Internal SD card." In the Settings area, the phone storage read as either unavailable or 0.0 space. I tried to odin back to stock but then it gets stuck on Galaxy S logo again. I've tried this back and forth multiple times and it's still the same. Either it gets stuck on the logo or it doesn't recognize the internal sd card. I've tried it with repartition on and repartition off, but no difference.
So, are there any trick to fixing this? Thanks in advance!
Could you post the links to the files you are flashing? Honestly ODIN should have fixed it.
kawika said:
Could you post the links to the files you are flashing? Honestly ODIN should have fixed it.
Click to expand...
Click to collapse
Hi. I got the stock JVD from the Noob Guide (http://forum.xda-developers.com/showthread.php?t=849028). I followed the steps there to flash to stock through ODIN and I got the black screen/lighted buttons. Then I downloaded and flashed it with the one that came with the toolbox (http://forum.xda-developers.com/showthread.php?t=954509). same thing, black screen with lighted buttons. I also tried Eugene's ROMs (Eugene_SD+2E_JK2_Froyo - http://www.multiupload.com/12QAKU043I and the Froyo ~That does not Brick! - http://www.4shared.com/file/dJiyRz3v/EUGENE373_SamsungS_Froyo_PDA.html). Both links are from Eugene's forum page.
The only "success" I have so far is using Eugene_SD+2E_JK2_Froyo, but whenever it's loaded, I always get the "Blank internal sd card" notification and the phone storage is shown as unavailable. :\
Bump. I'm still trying to get this phone to work. :\
Give the following a try..
http://forum.xda-developers.com/showthread.php?t=1230059
Alex9090 said:
Give the following a try..
http://forum.xda-developers.com/showthread.php?t=1230059
Click to expand...
Click to collapse
Didn't quite work for me unfortunately.
1. When it's in recovery mode, I can't get adb to connect. I can only do it when it's loaded up.
2. When I tried to do print in parted, I get this error
Error: /dev/block/mmcblk0: unrecognised disk label
Click to expand...
Click to collapse
.
Do you have external card in the phone? First try taking it out and then reboot without it and see what happens. If that doesn't do anything..try the cleaning and repartitioning method posted by Br1ck'd ..
I have posted about it in several threads, including my own, so I figured I would finally put it in a central location. This is my FTDNB method for starting with a fresh, clean phone, without any ghosts of roms past popping up to cause you issues.
Download this first, and flash through Odin with your standard 512 pit file
http://eb-productions.proboards.com/...splay&thread=8
Then when it reboots to the recovery screen, pull your battery, reinsert it and boot up to dl mode, and flash the following, with your same pit file, and selecting repartition in Odin this second flash only:
http://eb-productions.proboards.com/...splay&thread=3
The first link there is Eugene's Froyo That Does Not Brick, but it doesnt work that well as a driver. As an eraser its great though! The second link is the Froyo JK2 leak, with fixed recovery and already rooted. If the first one didnt, the second flash will definitely put you back on Froyo bootloaders.
Thats my whole secret to keeping a clean phone and wiping out any ghosts. You can proceed from there in your desired direction (back to ZD or GZ preferrably) in a safe manner. Its always worked for me to clear up any oddness, and literally takes 15 minutes tops once you have the files downloaded.
Click to expand...
Click to collapse
I've tried that before. Eugene's Vibrant_Full_Froydin_AND_2E_Recovery_+SD_Fixed (Froyo JK2 leak) is the one that lets me load the system all the way through (better than running stock JVF which only gets me to the logo and then gets stuck). The internal sd card problem remains however. I get the "Blank internal sd card" notification. The phone can't function properly.
EDIT: I finally got the external sd card to work. Is there any program for me to fix my internal sd through my external sd card?
I'm having similar problems. Flashed back to stock Froyo using Heimdall (Mac only here), everything seemed fine, but when it all came back to life, I have no service and my Internal SD card is blank and cannot be reformatted.
It won't mount in the recovery tools, and so unable to format.
Any thoughts on how to restore functionality??
Bump. I'm still trying to get my phone working again. Thanks in advance!
If it just "happend" one day, then you're looking at a hardware failure. Flashing firmware can only make it worse.
xoxo1001 said:
I've checked the other threads for solutions and I've tried many different things today but my phone still doesn't work, so I guess I should make a thread and ask you guys directly.
Ok, so my phone stopped working last night. It was running stock everything. Only upgraded to Froyo through Kies Mini a long time ago. Anyway, when I powered up the phone, it gets to the Galaxy S logo and then the screen dies. It's technically still on, since the four keys light up when I tap the screen. I took the battery out for a bit and put it back in, same thing. Logn story short, I tried to odin it back to stock JFD this morning and it didn't change anything. The screen goes to black right after the logos. Then I tried Eugene's Vibrant_Full_Froydin_AND_2E_Recovery_+SD_Fixed. It sorta worked. By that I mean, the phone loads up the OS and I got the home screen, but now it doesn't recognize the internal SD card. In fact, the notification gives me "Blank Internal SD card." In the Settings area, the phone storage read as either unavailable or 0.0 space. I tried to odin back to stock but then it gets stuck on Galaxy S logo again. I've tried this back and forth multiple times and it's still the same. Either it gets stuck on the logo or it doesn't recognize the internal sd card. I've tried it with repartition on and repartition off, but no difference.
So, are there any trick to fixing this? Thanks in advance!
Click to expand...
Click to collapse
'I had a similar problem but later learned tht the SD card was actually damaged some how during flashing'
so try using a new SD card and Odin back to stock
Hey guys,
Little help needed... I soft-bricked my Vibrant... so I used Odin v1.85 to flash the stock rom (s1_odin_20100512.pit + T959UVJFD.tar)... both were flashed successfully and the phone booted up normally... annoying T-mobile jingle, Galaxy S splash screen, and then lockscreen.
BUT, i see in the notification bar "Preparing internal SD card"... then "Preparing external SD card"... and then BLACK... phone just turns off... sometimes it would just re-boot, other times just stay off. I have tried flashing these files multiple times through Odin using different USB ports and tried restarting the computer a few times as well... no luck... I tried searching but couldn't find anyone else with this same problem...
HAS anyone had this problem? I feel like I'm missing something, but I can't imagine what... maybe more experienced users could see more clearly what I'm missing here... I appreciate all your help... thanks!
Steven
I responded. You may want to let others know you were trying to ODIN the wrong phones pit/tar earlier...
have you tried eugenes froyo that does not brick yet?
Are you changing anything in ODIN? All the checkboxes should be untouched. Once you load them, all 3 on the left will be checked, including re-partition.
s15274n said:
I responded. You may want to let others know you were trying to ODIN the wrong phones pit/tar earlier...
have you tried eugenes froyo that does not brick yet?
Are you changing anything in ODIN? All the checkboxes should be untouched. Once you load them, all 3 on the left will be checked, including re-partition.
Click to expand...
Click to collapse
Yeah I tried the Samsung Galaxy S 4G at first, and that didn't fix anything (of course)... but then I over wrote all that with the stock Vibrant files... so shouldn't that restore everything to stock?
Haven't tried Eugenes froyo... I'll try to give that a shot...
And yeah, all three checkboxes were left untouched, including re-partition... and it does everything successfully... but the phone still shuts down after mounting the SD Cards...
Any luck with this?
I did basically the same thing (flashed with wrong pit+pda, used the 4G on the vibrant) and now I'm having the same problem (reproducible crash right after the SD mount), though every so often I also see random graphical corruption and it crashes before getting to the SD mount.
I've been playing with all of the standard roms with odin and heimdall in an attempt to get something working, but that's pretty much what I end up with.
I've spent a couple days searching, but there doesn't appear to be a relevant enough thread to help me here, so I've resorted to asking for help, hopefully you guys can help me figure this out.
I got my girlfriend a used Telus SGH-T959D (same thing as the T-mobile version pretty well) several months back. It was on stock 2.1 and worked fine but was very laggy compared to my rooted HTC Desire on oxygen 2.3.2. So I rooted it and installed a 2.2 rom with Voodoo sound control (but no lagfix), and she's been using it this way for months now. It was better than stock but still laggy. I can't remember what rom it was but it was based on Samsuck firmware, hence why it's still laggy I guess.
For some reason, when I originally rooted it I had trouble with CWM recovery not installing, I can't even remember now what exactly was happening, but I managed to get the rom installed without a proper custom recovery, so when I go into recovery it's just the stock Samsung recovery, with no options for nandroid backup, restore, flash zip from sd card, etc. Basically I can't do anything useful in recovery.
Anyways lately, worse and worse she has been getting the Android text message to wrong recipient bug. If you aren't aware of it, it causes messages you sent to go to a different person in your text message message list. No it is not user error.
So I decided to try and data wipe. After this there is basically no launcher when it boots up. The notification pulldown is there and working, and it shows the phone has a signal and wifi is turning on and working, capacitive buttons light up when you press them, but you can't do anything except grab the pulldown.
It won't connect to USB when booted up, phone shows a message that you must close running processes first, or something like that. But I cannot flash a rom from recovery anyways, since it only brings up a stock recovery.
I can get it into download mode, if I hold my tongue just right and try several times, but not sure what to try to flash with Odin. I already downloaded an ICS Passion rom, but then reading the tutorial saw that I must first download CM7 and install that, then upgrade the bootloaders to the GB ones, then flash the ICS rom. I would really like to at least upgrade to 2.3 and something not based on Samsung fw, but the main priority is to get it working again.
Anyways, whatever you guys can suggest to try would be greatly appreciated. Thanks.
Honestly bro, everything I'm seeing in Google makes it seem like that phone is more on par with the Galaxy S Fascinate than with our Vibrant. Although on the exterior they all look so similar... I dunno, maybe check out their forums and see if you get anymore help there?
Here's the link:http://forum.xda-developers.com/forumdisplay.php?f=718
Goodluck!
The title of this thread looks similar to my problem with my Samsung Vibrant. So I would ask it here, too.
I'm not sure if I bricked my vibrant, it's still power up, only to to first screen, which has the words Vibrant (and) Samsung and stay there forever.
I first rooted my Vibrant successfully.
Then, I've followed the instructions below:
1. Download the latest version of the ROM from the original development page.
2. Transfer the downloaded zip file to the root of the internal SD card on your phone.
3. Turn off your phone and wait for complete shutdown (wait for capacitive button lights to go off).
4. Then, boot into Clockworkmod (CWM) recovery. To do so, press and hold these 3 buttons together: Volume Up, Volume Down, & the Power button till the screen turns on, then let go of the buttons. In recovery, use Volume keys to scroll up and down and power key to select an option.
5. Perform a full Wipe (this will not wipe your SD cards)
a. Wipe data / factory reset –> then Select Yes - Wipe data/Factory reset on the next screen.
b. Select “mounts and storage“, then select “format system” -> select “Yes” on next screen to confirm. Then, select “go back” to go back to the main recovery menu.
6. Now scroll to “Install zip from sdcard” and select it.
7. Select “Choose zip from sdcard”. Scroll to the file you transferred in Step 2 and select it.
8. Now confirm installation by selecting “Yes — Install **your_rom_file_name**.zip – The ROM will start installing.
9. The phone will reboot to recovery in the middle of the installation, then continue installing the ROM.
When I got to step 7, instead of running the zip file downloaded on step 1. I run the update.zip (something like that). And I couldn't get back to the CWM recovery screen anymore. Only I can boot it to the regular recovery screen, where it let you:
reboot the system
reinstall packages
delete all user data
delete cache data.
Or boot up to the screen described at the beginning of this post.
So what should/can do to fix this problem?
I think my phone is t959 (it's t-mobile Samsung Vibrant)
Thanks for the reply. As far as I thought the only similarity between this and the at t fascinate was the name fascinate. There's is the i5000 and mine is the t959d? Should this post be moved over there? I found a thread there with someone having partly. the same issue as mine not being able to install cwm but its been there for days and likely will not be replied to.
I've spent a lot of time trying to fix messed-up installs. Seems to me that if for any reason you can't rrflash the rom, or reflashing and wiping doesn't work, just Odin-ing back to JFD and going from there is the best bet.
Well I was about to go ahead and download stock JFD and try flashing that but it appears that Mega upload has been shutdown by the FBI for fraudulent activity, and Rapid share is not working either. Maybe they're too busy because of the mega Upload shutdown or they were owned by the same people and have also been shut down. So now I'm not sure where to even find files that are safe to flash.
I just spent another hour on here and Android forums, and basically all the the threads are one or two posts, with no resolution to the OP, and none of the downloads links anywhere are working. I'm pretty patient but I'm ready to give up. Does anyone want to trade a soft bricked T959D in mint condition for any old beatup HTC that works? I've had my fill of Samsung's now.
No trade sorry but if you want to donate shoot me a pm.
Before you dump it, give me some time to look into this and I'll see if I can get you up and running with some files. Sammys are way user friendly unless you aren't doing something right, then you could always go back to stock.
Hold the phone. Haha. I'll get back to you.
You too ciditin
Thanks Woodrube, I will definitely wait patiently as long as I know I'm going to be able to sort it out eventually. I'm busy with schoolwork so even though I enjoy this kind of thing I hate spending hours upon hours on it just trying to get the phone operational again.
I've been spoiled by my htc desire, it's been almost foolproof to do anything after spending a short time reading a few FAQ's and there have been no close calls. Soon I'll probably try an ICS rom once they get a bit more stable.
I will definitely do a donate if you can help me get it going with a decent rom. I would love to have lag fix on it since my girlfriend is a bit annoyed at the lag.
Since I got my first Android phone in August 2010, I've rooted and rom'd an LG Shine Plus, LG Optimus One, HTC Desire, the T959D and Galaxy S2 T989D (sold after I got it on an early renewal). I also had to fix my sisters I9000M after a failed 2.3 update operation. So I'm no expert on this, but I've got a little bit of experience messing around with stuff. Just they all require different processes, different programs to do the job, so you have to relearn it for every new phone.
The Samsung's have been the biggest pain compared to the others, but I think it's mostly because the Canadian versions are always slightly different than the Tmobile version, but besides that Samsung always has several different versions of the same.
If I get this thing up and running again I will probably check out your GPS fix thread, cause the GPS on this phone would lock on but it was way out to lunch. Like 6 streets away from us out to lunch.
I found the way to fix my problem, hopefully it'll fix yours.
I was able to restore my stock.
Here is what you have to do.
WARNING!!! THIS WILL WIPE ANY DATA ON YOUR DEVICE, IT WILL REPLACE YOUR BASEBAND, KERNEL, RECOVERY AND OS.
DOWNLOADS:
ODIN application
512 PIT file - I can't post link so pm me
T-Mobile Vibrant JFD Image – I can't post link so pm me
USB Drivers from the Samsung Galaxy S – 32 Bit Windows Download \ 64 Bit Windows Download (again I can't post link, yet)
INSTRUCTIONS:
1. Turn off your phone (remove battery, and usb cable to pc).
2. Plug usb cable to your phone (this is just for easy to connect to the PC in the next step), do NOT connect it to your pc just yet.
3. Get your phone into DOWNLOAD mode by holding the Volume Up, Volume down, and plug your usb cable to your PC. A yellow digging Android sign should be on the screen of your phone. This may take a few tries to get it right.
3. Launch ODIN.The third box dow from the top-left box should then say a COM port (the box under the top-left box should be yellow).
4. In ODIN, load each file with its corresponding field:
___a. Click PIT and select *.pit file extracting from the 512 PIT file above.
___b. Click PDA and select the *.tar, stock JFD file.
5. Don’t check anything else, the other two boxes should be checked by default (Auto Reboot and Reset Time)
6. Hit “start.” Be patient for a couple minutes! (The bar under the top left box should show the progress, and on you phone, too)
7. You should have your Vibrant back in with stock configuration.
Good luck!
NOTE: COM3 worked fine for me. COM should not matter as long as you are using the correct drivers.
350Rocket said:
I will definitely do a donate if you can help me get it going with a decent rom. I would love to have lag fix on it since my girlfriend is a bit annoyed at the lag.
Click to expand...
Click to collapse
Ok. I wasn't soliciting for a monetary donation, I was just going off that you wanted to trade. I can't trade but if you ever want to donate your phone then just PM me.
I have to agree with kawika that everything I have read has been that your model number is for the Fascinate. Easy tip off would be; does your phone have a sim card? It is probably a CDMA phone with no sim slot. I suggest getting the files you need from the Fascinate forums as I am almost positive that the T959 files will not work on the T959d. Since you have modded a I-9000m you know that they are slightly different than the I-9000. Same thing goes with this circumstance.
Good luck and sorry that there wasn't more I could do but it is just a different phone.
@Citidin - Good to see you got yours solved. If you have questions, please ask (in the correct thread for your question a this one will probably be closed out).
It definitely has a sim card and it's HSPA, I pulled the Sim card out and put it in my HTC Desire for her to use, and put my SIM card in this crappy little LG Optimus One that's too small for me to type on. So I guarantee it has a sim card and is nothing like the Verizon phones which will not work on any of the Canadian carriers AFAIK. I think nobody understands what the phone is, and that's why almost every thread with a problem like this ends in 0 replies. I think from now on I will stay away from Samsung's abortion phones that they sell in Canada. Or at least I will research community support before getting one.
Ours is called the Fascinate, but its completely different model # than theirs, it is the T959D. Just like how the new Telus galaxy S2x is the T989D, same phone as the T mobile T989_.
For some reason there seems to be a few posts in the Fascinate section, for Telus only, I think that only started because of confusion about what the phone was, but the phone has nothing in common with the Verizon CDMA version. Actually I think if you look up, just about every phone that Telus or Bell (same network basically) gets, is a phone that T mobile got first. HTC Amaze being another one. HTC Desire Z is the same as the Tmobile G2.
Sorry I misunderstood you about donating the phone itself. My last effort will be the JFD file that Citidin sent me a link to. Hopefully that gets it going. If not I will stash it away until I have extra time to try again.
Well once I got the JFD file downloaded and put phone in download mode, turned on Odin, realized the PC recognizes the device attached and being malfunctioned, so I cannot flash with Odin.
I tried Heimdall which I downloaded yesterday, but the program won't load as it says I'm missing a DLL file.
I tried Android flasher which I downloaded who knows when, and tried to just install a recovery image with it, but it gets stuck while pushing recovery image and the program locks up.
I decided to try my girlfriends Laptop instead of mine after maybe 40 failed attempts to get Odin to communicate on mine, and to my surprise it recognized it right away. I transferred my files, with the JFD to this computer and then flashed with Odin. It took about 2 minutes and it was up and running. I checked about phone and it said 2.3.3 firmware. Really confused I looked back at odin and realized I flashed the I9000M stock 2.3.3 firmware (KG3) that I flashed on my sisters phone back around xmas. I forgot I did that on this laptop.
Anyways it is working as it should except for the home button not working (which I had already read about in a thread about using I9000M or Vibrant roms on the T959D).
While it is unfortunately stock again, the 2.3.3 should fix the original problem of sending to texts to the wrong recipient, and it also seems a lot less laggy. I think I'll just let her try it as is and hope she is happy.
If you use the JFD file from the link I sent you, it should be the stock Tmobile Vibrant.
Similar problem
Sorry dont mean to hijack your thread but I think I am having a similar problem - posted in the wrong spot before so hopefully I am ok here...
Have a Vibrant and some how got crossed up on it.
I have been able to use Odin to update the phone, however after it says its done, it does a reboot as it supposed to, shows the samsung screen then just shuts down.
After about a hundred tries, someone pointed me to Eugene's no brick. I tried that and it will fix it so it will boot and go into recovery, but I can't seem to do much once I get there. My only options are to update, wide data and wipe cache. Can't get to the point where I can load an update onto the unit.
I tried wide data and reset, then reboot. It shows the samsung vibrant logo, then the splash screen, then the big S and then screen goes black and the cap buttons stay lit.
If I try to go back and load the stock pit and jfd file, it just goes back to not booting at all and shutting down after the logo
I cant seem to get it into recovery unless I do Eugene's fix
In one of my earlier attempts, I did check to repartition as direct in one of the other threads - been chasing this a while now!
Edit: It was originally a bell phone - does this matter?
If it was a Bell phone than it should be the I9000M. It sounds like your problem is a bit different than mine was. I was able to get into recovery mode and download mode just fine. I just didn't know which files to flash with.
I intended to flash the JFD that citidin sent me, but I accidentally use the KJ3 (latest I9000M 2.3.3 firmware). The I9000 and Vibrant roms are compatible with the T959D Telus Fascinate though, only problem being no home or search button.
It sounds like the Eugene thing (whatever that is, I'm not familiar) gets you into stock recovery. Like my original issue, you cannot flash or mount the sd card, or much of anything with the stock recovery.
Do you know that the file your flashing is compatible with your phone (the I9000M I assume)? More info that would probably help, is what firmware did you have on it before, was it JFD? What update did you try on it? Bootloader version - there are gingerbread bootloaders, and froyo bootloaders I think?
Have you tried different files other than the one that doesn't seem to boot up for you? I think most of the tutorials I've looked at, said not to check repartition. When i finally got this T959D working with the I9000 rom I did not check repartition and did not select a pit file, just the PDA, phone, CSC.
Yes it is a I9000M - I was trying to load the JFD tar file along with the 512 pit file. I followed a thread in the I9000 section and loaded a JPD tar file onto it, now it shows up as a I9000B - maybe I should stop
I can now get into recovery and or download (i think the steps are differant than hold both volume buttons - mine is holding the volume one way for recovery and the other way for download, along with home and power)
Wondering if I am in this bind because it isnt really what most are calling a Vibrant - maybe under Bell it is something else.
Bootloader? didn't know I had to do anything there
I just picked up the phone used from someone - I assumed it was stock and didn't do a good check to see what was on it.
I9000m is not the Vibrate but rather the Bell version of the Captivate. There is a dev section for the I9000m in the I9000 group.
I would definately stop what you are doing and read over there.
******
Also 350 you can re-map your keys to work but I am mobile now and cant search it for you. Reason being that the. Vibrant keys are laid out differently in, ahh can't think right niece where they are, but it is fixable. Just search key remap or remapping.
Thanks very much for the help - have to wonder why they cant call them the same names regardless of where they are sold - guess thats why they get the big bucks
Hi guys,
I have a big problem over here and I hope someone can help me out.
I wanted to create an ext3 partition on my external SDcard with fdisk (from busybox) in "Terminal Emulator".
But instead of partitioning the EXTERNAL SD (mmcblk1) I deleted the partition on my INTERNAL SD (mmcblk0).:crying:
After a reboot the phone hang at the Samsung logo.
I then tried to reflash a Stock JellyBean Firmware with Odin but it allways hangs at "Nand Write Start".
On the phone the blue bar gets to 100% instantly and hangs also.
Does anyone have any suggestions on what I could do?
I thougt about repartitioning with a pit file, which seems to work if I uncheck everything exept "repartition" and use only the pit but it does not seem to do anything. Problem still persists.
I'd appreciate any help... can't go to sleep like this and have to go to work tomorow morning. :silly:
mickmattes said:
Hi guys,
I have a big problem over here and I hope someone can help me out.
I wanted to create an ext3 partition on my external SDcard with fdisk (from busybox) in "Terminal Emulator".
But instead of partitioning the EXTERNAL SD (mmcblk1) I deleted the partition on my INTERNAL SD (mmcblk0).:crying:
After a reboot the phone hang at the Samsung logo.
I then tried to reflash a Stock JellyBean Firmware with Odin but it allways hangs at "Nand Write Start".
On the phone the blue bar gets to 100% instantly and hangs also.
Does anyone have any suggestions on what I could do?
I thougt about repartitioning with a pit file, which seems to work if I uncheck everything exept "repartition" and use only the pit but it does not seem to do anything. Problem still persists.
I'd appreciate any help... can't go to sleep like this and have to go to work tomorow morning. :silly:
Click to expand...
Click to collapse
Use odin to reinstall the firmware, you will also need a pit file to repartition it, dont panic , just search the forums for odin repartition
swukjay said:
Use odin to reinstall the firmware, you will also need a pit file to repartition it, dont panic , just search the forums for odin repartition
Click to expand...
Click to collapse
For those interested in a solution:
After ~2hrs of goo...startpageing I finally found a solution.
As oposed to many opinions the pit file to use is the one with ..._20120329.pit even if you have no 64GB Galaxy S3. Mine is 32GB..
Together with a Stock-JB-Firmware (I used XXEMG4) that is made of 3 parts (PDA,PHONE,MODEM) and Odin 1.85 (don't know if that really matters) it suddenly started flashing. However, the phone hung at the Samsung bootlogo.
After another search I found out, that you have to keep the device connected to your PC until Odin gives out "PASS". There is still being data written to the GS3 even after the reboot.
Man I still can't believe I managed to get it back to work. These phones are awesome.
@ swukjay: Thanks for the info and your kind words.
Going to sleep now...still got 2,5hrs.
mickmattes said:
For those interested in a solution:
After ~2hrs of goo...startpageing I finally found a solution.
As oposed to many opinions the pit file to use is the one with ..._20120329.pit even if you have no 64GB Galaxy S3. Mine is 32GB..
Together with a Stock-JB-Firmware (I used XXEMG4) that is made of 3 parts (PDA,PHONE,MODEM) and Odin 1.85 (don't know if that really matters) it suddenly started flashing. However, the phone hung at the Samsung bootlogo.
After another search I found out, that you have to keep the device connected to your PC until Odin gives out "PASS". There is still being data written to the GS3 even after the reboot.
Man I still can't believe I managed to get it back to work. These phones are awesome.
@ swukjay: Thanks for the info and your kind words.
Going to sleep now...still got 2,5hrs.
Click to expand...
Click to collapse
Your welcome, glad you got it sorted
Long story short, stock phone just randomly blew up and I'm trying to re-install its stock Android OS. Phone has never been rooted before, it just started to reboot on its own and now I'm in a position where I can only access download mode.
I'm in Odin, with what I believe is the correct firmware for my device (SM-N950U1) and I just keep getting a "Secure Check Fail: system" when trying to flash. it via Odin. The Odin log says "FAIL! (auth) right after trying to write system.img.ext4 for a few minutes. The "Secure Check Fail: system" is the printout on the phone screen itself.
Any clues?
Bump! Anyone?
playbacktri said:
Bump! Anyone?
Click to expand...
Click to collapse
I see that you have not received an answer. That is upsetting. I am also struggling with this exact same issue on a g955u1. Have not found a solution. Did you end up solving your problem? If so, what did you have to do?
ap7x942 said:
I see that you have not received an answer. That is upsetting. I am also struggling with this exact same issue on a g955u1. Have not found a solution. Did you end up solving your problem? If so, what did you have to do?
Click to expand...
Click to collapse
Nope, I have not solved the problem. I've scoured the internet and other people asking the problem all have not had any answers either. My assumption is that the actual internal memory of the phone is corrupted and won't let me write past a certain point, or on certain sectors, or something and its not actually fixable via software. I think everyone else just stops at this point and its never resolved because there is no resolution hah.
Good luck, let me know if you ever figure it out...
playbacktri said:
Nope, I have not solved the problem. I've scoured the internet and other people asking the problem all have not had any answers either. My assumption is that the actual internal memory of the phone is corrupted and won't let me write past a certain point, or on certain sectors, or something and its not actually fixable via software. I think everyone else just stops at this point and its never resolved because there is no resolution hah.
Good luck, let me know if you ever figure it out...
Click to expand...
Click to collapse
This phone I am working on is for a customer of mine. Thankfully, they have given me an open ended time frame. I have been working on this for about a week trying to figure out whats going on.
The memory corruption thing you were talking about resonates with me, because prior to my customer bringing this in, they had attempted a couple factory resets trying to resolve the original issue which was all the system apps crashing. The phone would reboot like someone killed all the processes. Pretty much from the moment it reached the home screen, and it was not power related. The problem persisted after their factory resets within recovery mode. And then I hit the phone with Odin and ended up with a partial flash. Soft bricking the phone.
You saying that kinda reinforces what I was already thinking, that it might be a hardware issue. Im not sure.
5 minutes ago I was able to get odin to successfully flash BL, CP, and CSC. It even brought me back to the Samsung logo for a minute but hung there. That's the most success I have had with this thing. Ive flashed numerous firmwares and every single one of them fails on system.img.ext4. After it reboots, it boots directly into this altered version of download mode with an emergency recovery error.
I have flashed dozens of phones before without issue. This is the first time I have ever experienced this one. You could be right but I refuse to accept defeat in this case lol so im gonna keep trying and ill report back if I have success.
ap7x942 said:
This phone I am working on is for a customer of mine. Thankfully, they have given me an open ended time frame. I have been working on this for about a week trying to figure out whats going on.
The memory corruption thing you were talking about resonates with me, because prior to my customer bringing this in, they had attempted a couple factory resets trying to resolve the original issue which was all the system apps crashing. The phone would reboot like someone killed all the processes. Pretty much from the moment it reached the home screen, and it was not power related. The problem persisted after their factory resets within recovery mode. And then I hit the phone with Odin and ended up with a partial flash. Soft bricking the phone.
You saying that kinda reinforces what I was already thinking, that it might be a hardware issue. Im not sure.
5 minutes ago I was able to get odin to successfully flash BL, CP, and CSC. It even brought me back to the Samsung logo for a minute but hung there. That's the most success I have had with this thing. Ive flashed numerous firmwares and every single one of them fails on system.img.ext4. After it reboots, it boots directly into this altered version of download mode with an emergency recovery error.
I have flashed dozens of phones before without issue. This is the first time I have ever experienced this one. You could be right but I refuse to accept defeat in this case lol so im gonna keep trying and ill report back if I have success.
Click to expand...
Click to collapse
Man, that sounds very very familiar to mine. I don't know if you found my other threads where I was asking for help, but I woke up with a phone that wouldn't turn on. Finally found the key button combo to get it to soft reboot, then it would turn on and just crash in the middle of using it after anywhere from 30 seconds to 5 minutes. If i started to use the phone heavily it would just shut off instantly and reboot back up on its own.
After clearing the boot cache, then doing a factory reset, it finally just stopped turning on at all (just samsung boot logo loop)
So I hit it with odin, unsuccessfully for 2-3 days, and then out of nowhere it just finally took a successful flash. However, it still just bootlooped, so I did a factory reset again and it put it back to being toast.
Since then, not a single successful complete flash from odin. I too can do the BL, CSC and CP files but I can't flash the AP file as it is writing the most data and finally fails about 3-4 minutes into to writing the system image file.
Again...good luck, ha!