hey
i use to be an s3 user, did all the youtube tutorials and had fun with rooting custom roms, didnt know anything too serious. went to windows phone...
well im back! (was a lurker, first time poster)
so my cousin tried his hand at ODIN and what not and now cant get boot his phone it shows the GALAXY S III i9300T screen.
i gave it a go on odin with a stock rom, didnt work.
tried a reset, didnt work.
i looked at the odin menu, looks like its still on a stock rom and doesnt look like its been rooted properly, at least thats what the counter says.
anywho this is the screens i've been getting
if anyone could offer any suggests.
i read up about the EFS, sounds really ****ed. pretty sure the kid didnt even back up before trying to root.
even if it was just without EFS hwo do i get it up to working condition??
Try the rescue firmware with pit from general forum, but it looks like the emmc chip is corrupt.
Related
I was trying to root and get a custom rom on my friends Fascinate. I rooted it fine and then found out I had to use odin to set the firmware back so I could flash clockwork cause the stock recovery wouldn't let me. I'm pretty sure I used the wrong odin or something on accident. When I boot up the phone it shows at&t world phone. It wont boot up past that screen. It won't boot up with the usb cable in either. the phone is the 1008 version. Can anyone tell me if this is a for sure brick or not and if it isnt how to fix it or if it is if theres a way to get the at&t logo off the screen so verizon doesnt ask questions.
You flashed the wrong rom.
go here and get this Its the stock rom.http://www.multiupload.com/I9HBT8MXN1
and here get this its the stock pit. http://dl.dropbox.com/u/2056318/atlas_v2.2.pit
And if you need odin get it here. http://www.mediafire.com/download.php?t093btu771q0bgi
Them i would suggest using this rom and reading up on it here, http://forum.xda-developers.com/showthread.php?t=983395
this should get you strait. If not go here as a last resort, it is a bit confusing at first. http://forum.xda-developers.com/showthread.php?t=755265 and read this it includes a download link.
you will need to unzip the stock rom to get to the files you need for this.
The instructions there look pretty spot-on. You should thank DaleV.
Additional things:
1. ALWAYS make sure what you flash is for the VERIZON FASCINATE.
2. ONLY use the PDA button in Odin. NEVER EVER EVER use the phone button.
3. Jesus Christ. Be more careful with other people's $600 devices.
Yeah i know. Thanks so much man. Saved my butt. And yeah, ive really got to do ALL the research first and not cut corners. Lesson learned ha. Thanks guys REALLY appreciate it.
Hi guys
I was using ICS LP7 3uk stock, rooted, basically i found it a bit laggy compared to gingerbread i was using and decided to revert back, but completely stock, and start again with gingerbread.
So away i went, flashed gingerbread, everything fine in odin, no problems, flashed, THIS IS WHEN ALL MY PROBLEMS STARTED,,,,,,,,,,,,,,
Upon trying to use the phone, no problem, apps work, phone calls, messages etc, no probs, but when i go on android market, i started getting connection timed out, so i tethered up to check my speeds, and my what a suprise i got,
My speedtests on 4 different testing sites came back at between 4k to 6k a second, basically i am on 3uk and used to have speeds of 7mbps average and download at around 800kbps average, my oh my, what a drop.....
So i figured i did something wrong, when i flashed the gb i flashed with the .pit file.
Ive since flashed back to 3 different versions of ics, with and without pit, and nothing has changed, no matter what i do, i cant get a download at any faster than 5k a second, even the market is now unuseable, arrrgggghhhhhh.
What did i do wrong.
I wondered if anyone else has had this problem, or maybe knows a way to try and fix this, id preferably like to go bk to GB, completely stock, even if it means flashing a boot file which i havent done yet.
PLEASE help, this is terrible and my beloved s2 is choking to death on its own vomit..............pretty please.....
Try a different modem.
Sent from my GT-I9100 using XDA
Try following this
http://www.youtube.com/watch?v=cCeVPex27n4
****** S O L V E D ******
Hey chaps just to update you, ive fixed it, 3 hours of research lead me to believe something was sadly wrong with the structure of the files on my phone after flashing the .pit file, morale of the story, LISTEN TO WHAT YA TOLD ON HERE AND STAY THE FU** AWAY FROM THE PIT FILE....
JEEZ man, ive been around long enough to know better, and frankly these people making posts telling ya to flash their firmware with the pit file shouldnt be doing this, oh well.
That was the problem, basically, flashing the pit somehow managed to erase some files from my efs folder, very odd, but the research lead me down that path, thankfully, i did listen like a good boy when i was told to backup my efs folder, so, i restored the folder, rebooted and factory wiped and now all is well, totally bizarre, so i guess it was a soft brick, boy was i panicking, my new shiny pebble blue S3 doesnt arrive till saturday, screwed if im flashing that, ill root it and leave it as is.
Anyway those that replied or took the time to contemplate my issue, many thanks, and yer, i am a **** and i dont mind you telling me so, it is my own fault for flashing that pit, and i ended up in a deep pit, so Noobs, DONT do what i did.
Hi Guys,
I have been scouring the boards and the internet on a solution to this problem.
GF had the phone and put it to charge.
Picked it up sometime later and it was off.
Turned it back on and it was stuck in a bootloop.
Phone was using Stock Firmware and was unrooted. It was running Jelly Bean 4.1.2. The EXACT firmware eludes me.
Phone is able to go into Download mode and recovery mode.
I have included a picture of what recovery mode looks like. [pic]
I tried flashing via ODIN. I tried different firmwares. All of them stopped at Boot.bin
I tried Kernel flash via PDA and it stopped at "NAND Write Start!" and just stayed there.
I tried flashing a bootloader and the progress bar appeared (only time it ever appeared) but it stopped after a little budge and did not move again. Not even after 30 mins. [pic]
Is there anything else I can do? I followed all the tips from http://forum.xda-developers.com/showthread.php?t=1449771 and I'm still here. Any insight would be appreciated. Thank you.
Hopper8's "Odin troubleshooting' thread. Find it, try the stuff in it. All of it. Not just try a few things & then post here saying 'I tried everything' when you didn't. The only thing that will happen if you do that is you'll still have a busted phone. And you need to try the stuff in that thread repeatedly. Over and over. As many times as you need to.
That's the only way you're fixing it (the alternative involves paying a Samsung service centre a considerable amount of money to fix it). There are no easy/simple fixes in these situations.
Im pretty sure I was in exactly the same situation a while back.Youll need to look back at my posts as Ive forgotten exactly how I fixed it.
It did involve GB and pit files via odin as nothing would flash by recovery.
Im on 2.3.5 as that was about the only thing that would flash properly and make the phone boot.I initially thought I had a bootloader problem as ICS/JB wouldnt load.
I spent 5 hours on that,and cant recall if it was the pit or the special 2.3.5 rom/or both that fixed it.
theunderling said:
Im pretty sure I was in exactly the same situation a while back.Youll need to look back at my posts as Ive forgotten exactly how I fixed it.
It did involve GB and pit files via odin as nothing would flash by recovery.
Im on 2.3.5 as that was about the only thing that would flash properly and make the phone boot.I initially thought I had a bootloader problem as ICS/JB wouldnt load.
I spent 5 hours on that,and cant recall if it was the pit or the special 2.3.5 rom/or both that fixed it.
Click to expand...
Click to collapse
Thanks. I'll search your posts.
I think I posted a pic with similar errors to yours,so look and compare them.Theres not much info floating around about our/your problem.Pit files are only meant to be a last resort option,and I was in that category.
I also think that most/all things I flashed with odin passed,but phone would not boot,which led me to flash 2.3.5 combined with pit file.
I can't find your posts.....
Im only commenting because Im pretty sure its nothing to do with odin,I feel my phone and maybe yours has a hardware problem.I done a search before and only saw 1 situation like mines on another website.
For me,there was something major wrong for my phone not to accept ics/jb stock firmwares.
I have posted a pic before with the errors,and commented what I done to get the phone working.
I also dont think anyone on here can help,as it was the worst thing to fix Ive ever came across,and its not been mentioned on here.
Its up to you what you want to flash,but my moneys on a frankenstein GB rom c/w pit.Only try it at your own risk,or wait until someone else has alternative advice.
theunderling said:
Im only commenting because Im pretty sure its nothing to do with odin,I feel my phone and maybe yours has a hardware problem.I done a search before and only saw 1 situation like mines on another website.
For me,there was something major wrong for my phone not to accept ics/jb stock firmwares.
I have posted a pic before with the errors,and commented what I done to get the phone working.
I also dont think anyone on here can help,as it was the worst thing to fix Ive ever came across,and its not been mentioned on here.
Its up to you what you want to flash,but my moneys on a frankenstein GB rom c/w pit.Only try it at your own risk,or wait until someone else has alternative advice.
Click to expand...
Click to collapse
So I flashed the pit file.... and nothing happened. It just stopped there at "DO NOT TURN OFF TARGET!!!" I eventually closed ODIN but the phone still behaves the same way. If the EPROM is damaged, it won't have a partition to partition right? Any other suggestions?
I tried to flash CF root. Just to try anything. If hung up after kernel flash. Not it says I have a custom binary. Count 1. I don't know if that is relevant but... it shows something.
levi_jm said:
I tried to flash CF root. Just to try anything. If hung up after kernel flash. Not it says I have a custom binary. Count 1. I don't know if that is relevant but... it shows something.
Click to expand...
Click to collapse
Youll need to ignore half of my previous advice(about odin),and follow Mistahbungles advice.......as my memory is playing tricks on me.Also,it was the other way around in my case.....ICS/JB flashed ok,it was GB that wouldnt(but doesnt matter here).
You have a damaged partition table,so that hopefully will be fixed by flashing .pit using Odin.If you cant get Odin to work,you could try a friends pc,or see if a local shop has Odin working.
Apologies to you both for my memory.........lol
theunderling said:
Youll need to ignore half of my previous advice(about odin),and follow Mistahbungles advice.......as my memory is playing tricks on me.Also,it was the other way around in my case.....ICS/JB flashed ok,it was GB that wouldnt(but doesnt matter here).
You have a damaged partition table,so that hopefully will be fixed by flashing .pit using Odin.If you cant get Odin to work,you could try a friends pc,or see if a local shop has Odin working.
Apologies to you both for my memory.........lol
Click to expand...
Click to collapse
I did try his advice and with 6 different versions of odins on two different laptops with 6 usb ports between them. I don't think ODIN is the problem. I think the problem is a corrupted NAND. It is so corrupt that it did not accept a .PIT flash. It didn't hard brick the phone. It did nothing to it. I am unsure what else to do.
Well maybe I was right all along about odin,but that doesnt help anything.
I cant remember if I could do anything via recovery,but I do remember that several things I tried just kept giving that page of errors.
Youll just need to google each error and see what it throws up.Stuff thats said ranges from removing sd card to replace recovery(but by odin which you cant do).
So to start off I've got an s3 through the dreaded ALLTEL... I know there's hardly anything for it so ya.. I flashed cwm through Odin and installed supersu and quickly found out I had to go through Knox.. I went and ran the de-samsungnizer script to remove Knox so no more Samsung firewall crap.. Got it rooted and everything's good til I realize the main reason I rooted (WiFi hotspot) doesn't even work so I go back to Google and find a WiFi hack mod .zip and flash it now I'm stuck at booting.. Come to find out that somehow I've switched my phone to d2spr.... Or at least thats what cwm says when I tried to flash a d2usc cm11 nightly.. Dumb me i know i will be harshly scolded.. I didnt make a backup!!!! Now trying to get back to stock now... Thinking.. My wife has the same phone bone stock could I just make a nandroid of hers and flash over mine or have I turned my phone into a really nice paper weight???
Flash stock rom via odin, to recover the you'll have to start again, btw your in the wrong forum this is for int'l s3.
Okay, I don't really know if i'm aloud to start a new thread for this but I'm going to see what happens.
Okay, I'm fairly new to rooting and flashing. I've flashed maybe 4 phones with custom roms and everything went fairly smoothly. I just got a Galaxy S8+ Sprint SM-G955u and was attempting the sampwnd root method on here. I thought I was following the directions to a T but apparently I wasn't because I got a fail pretty much right off the bat. Now my phone will not whatsoever. I am able to get it into download mode but that is it. No recovery mode no nothing. I have tried flashing the stock firmware but I get the same result. A fail pretty much right off the bat. I am running odin as admin, I've tried flashing the files individually as well as all together in both regular odin and comsey odin and I still just get the same failed result . Please tell me what ive done wrong and please please tell me i'm not screwed.
haven't rooted anything in a while but i used to do all my phones, do the normal 3 things when you fail, 1) re download the files 2) look around for more odins that other people are saying works and 3) try different cables, this is the dumb reason i have failed many flashes so don't overlook this. you can get into download mode so you're not screwed yet. best of luck
Thats really the best advice giving your situation. Ive had scenarios in the past where each one of those fixed my problems
Well sprint phones dont have root or custom roms as far as i see, but, maybe the other lines do. But if you really screwed up...try selecting nand erase all option and use the stock rom. Thats always been my last resort, and it always worked