Related
Alright, I have some weird things going on in my galaxy tab. I think its bricked, but if it is, its definitely only soft bricked.
Figured I'd post a video showing stuff as I cant really explain it. It shows up in my windows, so i can access inside it, but i have no idea what to do, it shows up in Kies, too
I'm wanting to hopefully make it usable, and if not usable AT LEAST get rid of clockwork mod recovery so I can return it!
So how do i fix my tab?
(note i was following the samsunggalaxytabhacks unrooting guide when I did this, I cant link b/c new
7510, btw
did you flash anything prior to this happening? I ask as I used the wrong kernel one time, one that wasn't for TW and when I rebooted it did the exact same thing... Did you make a backup?
Try to d/l one of the custom roms, since kies can see it, place the zip on sdcard and follow the OP to install it.
yeah im pretty sure i used the 3g model/non touchwiz kernal and this happened! i cleared m device, thinking it would fix it i guess i lost my backup!
go to roms section on 10.1 android development, and look for the correct kernel, transfer to sdcard via kies and go to recovery and reflash kernel for the TW. Or just d/l Tasks/Phantoms rom Paris and do the same, follow the OP to a T, that should fix it.
which one would be the right one?
I would use
http://forum.xda-developers.com/showthread.php?t=1284355
reload
There is a very good walkthough on putting your 7510 back to stock (first step I would suggest). This walk through gives you all the files you need. I have tested this (files include tested pit files, rom files, etc..)
Hope this helps...
http://p7510.teamovercome.net/?page_id=18
Hey All,
I've been looking for an answer for over a day now, but can't seem to find anything about my specific problem. Here's what happened:
I had flashed to ICS 4.0.3 on my Samsung Vibrant about a month ago and everything was working great until yesterday when I woke up to find the "Encryption Unsuccessful" screen on my phone. I did a little research to find out that there is a fix to this and to NOT reset the phone. So, I took the steps to ODIN the phone back to Stock Eclair in hopes that starting from the beginning again would be easiest way to fix the problem. The ODIN process finished completely fine (PASSED), but now when it reboots, I only get to the first "Vibrant" screen, then it shows the battery and spinning circle icon. Apparently it won't fully reboot. I've tried to ODIN it back to stock several times, and I keep getting the same results. I can get it into download mode and plugged into my computer, but that's about it.
From the posts I've read, it sounds like my phone might still be okay to recover since it does power up, but I can't seem to find a solution to get it fully back up and running.
Any help/recommendations would be greatly appreciated!
Thanks in advance!
Maybe your JFD file is corruption. Check with your MD5 sum if there any error or mismatch.. Just give you an idea.BTW what Odin are u using. I recommend Odin 1.7 I stay away the older Odin or the newer Odin
You are screwed.
Sorry to tell you this but i had the exact same problem and found no solution whatsoever to fix the phone. I finally gave up and bought a Galaxy Nexus. You can try flashing Eugene's Unbrickable Froyo Rom which is flashable through odin as a .tar package along with the pit file. You might be able to fix it but i highly doubt it. I flashed Eugene's rom and got the same results as you described. By any chance did you click "Reset Phone" when the "Encryption Unsuccessful" showed up? If so well yeah your phone is pretty much paperweight as of now...until someone finds a solution. Like you i am also able to access download mode. So i guess there may be a way to fix your phone. Not saying it's impossible...hopefully someone finds a solution soon.
Here is the link to Euguene's rom: http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=8
Good luck.
OP, what ROM were you running (specifically. Not just ICS 4.0.3-what is the name of the ROM)? Also what kernel?
Since you are not the only one this happened to, I would like to know the above and see if it correlates to the others that this happened to in the Vibrant section. I'll post the same in their threads too.
Check here out for a possible solution/workaround.
Replacement Vibrant Coming
Thanks for your recommendations/help guys.
I decided to go to T-Mobile and complain and they are sending me a replacement phone. Apparently it's still under warranty, so it won't cost me anything, and if my data is lost, then so be it...at least all my contacts will still be in tact through my Google account.
Merio - I did NOT hit the Reset Button when I saw the Encryption Unsuccessful screen. Before doing anything I did a little research and I found a forum here on xda that said to not hit that button, and tried to explain a way to fix it using the Heimdall One-Click. Basically it sounded like I'd be flashing back to a Gingerbread ROM. So, instead I just went ahead and tried to flash back to stock Eclair. The results of that were obviously not good.
Woodrube - I was running the Passion 13 ROM (ICS 4.0.3). Was really enjoying it until I got the Encryption "Screen of Death"
I don't know what Kernel it was, actually, I don't really know what a Kernel is...
Thanks again guys. Hopefully I'll be up and running on my replacement phone soon!
Now I know this question, in general, has been asked a lot. I've literally searched and tried the solutions in other threads, but this phone might be beyond help. I just want to know if someone has another solution as to how to revive this phone. I honestly think my situation is different than most....I downloaded and installed Team Hacksung's ICS 4.0.3 Build 6.1 ROM and I was using it just fine for a couple of months. Everything was working the whole time. Today, I am browsing through my local news station's app and my phone freezes on me! I pulled the battery and restarted the phone. It boots up fine and gets to the startup screen with the time and the screen lock. I did notice right away that the digitizer screen was not responding to my touch because I could not slide my lock over to get into my phone. I tried a few more soft resets and still nothing. I did notice, however, that the soft keys at the bottom did respond to my touch and they blinked and provided haptic feedback, so at this point I'm thinking it shouldn't be a problem with my digitizer. So I took the battery out then put the phone into recovery and wiped data, cache and dalvik. Then I rebooted the phone once again and still no response to touch at the home/lock screen. I then proceeded to try to reflash the same ICS ROM all over again and that's where the problem started. I can get into download mode and I've already tried to load stock froyo and stock gingerbread, but nothing works. My phone will not go past the "Samsung" boot-up screen. I've already tried several other forums' threads on how to recover a bricked Fascinate, but no matter what I try to load with Odin, Heimdall or anything else, my phone won't load past the Samsung screen. I can get into Download mode and that's it. My phone will not go into recovery using the 3-finger method. When I run odin I get a success message each time. I've even tried to heimdall the files individually and even tried to reload the stock kernel. The other problem I am running into is a lot of the links on these sites are all broken so I am unable to get the files I need. Has anyone else ever had this problem?
Edit: P.S. When the phone is off and on the charger, the grey battery shows the "loading" circle (whatever you call it) in the middle of it, but never converts to showing the green bars moving up and down indicating the battery is being charged. The loading circle is also frozen and does not spin.
im dizzy after reading a few sentences lol...check out my guide in the general section.
droidstyle said:
im dizzy after reading a few sentences lol...check out my guide in the general section.
Click to expand...
Click to collapse
Are you referring to http://forum.xda-developers.com/showthread.php?t=1238070?
If so, I just did it and it won't go past "Samsung."
Did you do check repartition and use the atlas pit file? That would be key, I believe, in returning you properly to stock.
Droidstyle's guide has all the working links you'll ever need.
http://forum.xda-developers.com/showthread.php?t=1238070
jawman27 said:
Did you do check repartition and use the atlas pit file? That would be key, I believe, in returning you properly to stock.
Droidstyle's guide has all the working links you'll ever need.
http://forum.xda-developers.com/showthread.php?t=1238070
Click to expand...
Click to collapse
I did check re-partition and yes I did load the atlas pit file. Still nothing.
e
So you tried heimdall? What commands did you do? and what rom?
also which links were dead that you needed?
mvmacd said:
So you tried heimdall? What commands did you do? and what rom?
also which links were dead that you needed?
Click to expand...
Click to collapse
I used heimdall front end to load DI01 files, I didn't use any commands. Also, I was just referring to "Unbrick your samsung fascinate" threads on other websites. A lot of the links I found were outdated or broken.
yea unfortunately not many guides have working links these days...Mine is about the only one left that is kept up to date. Im very suprised a full odin session did not fix your issues. One thing left to try is to odin a older stock package like DL09
Found here:
http://forum.xda-developers.com/showthread.php?t=1526488
Just tried pushing the DL09 file in odin AND in heimdall and neither worked. I still get stuck on the "Samsung" boot and it goes no further. Can't even get into recovery....
I think I truly have a brick...
kinna long shot
but why not try a different PC and a new or different cable.
believe me a faulty cable did me in, a week back and i was sure at the time that my phone is gone, but then it wasn't as bad as the impression i am getting from your description.
all the best with this , and hoping that something solves this issue.
god bless
haoleflip said:
Now I know this question, in general, has been asked a lot. I've literally searched and tried the solutions in other threads, but this phone might be beyond help. I just want to know if someone has another solution as to how to revive this phone. I honestly think my situation is different than most....I downloaded and installed Team Hacksung's ICS 4.0.3 Build 6.1 ROM and I was using it just fine for a couple of months.....
Click to expand...
Click to collapse
I am having a similiar problem now. I was able to odin an older CWM (3.0 blue I got somewhere). From there I mounted usb and loaded ext4_formatter_all.zip. I ran this script and odin'd dh03 and finally got back to stock. That's where I am now.
Hope this helps
kduffman said:
I am having a similiar problem now. I was able to odin an older CWM (3.0 blue I got somewhere). From there I mounted usb and loaded ext4_formatter_all.zip. I ran this script and odin'd dh03 and finally got back to stock. That's where I am now.
Hope this helps
Click to expand...
Click to collapse
I have a blue recovery [3.x, voodoo], here it is if the OP wishes to try it.
[Use Heimdall and select recovery]
cwm3_voodoo-blue.bin http://www.mediafire.com/?4ls06x8gha88vtp
cwm4-bml-i500-fascinate.bin http://www.mediafire.com/?2ny1ql66yh69bn3
35c31418dbe9a9db70de954cdf7369ef cwm3_voodoo-blue.bin
05f3e376ca697fd0fb8700dea05254aa cwm4-bml-i500-fascinate.bin
I threw in an extra 4.x cwm for good measure, lol. [I saved these in a folder in case I ever needed them..I was going to delete the folder since I upgraded to THS ICS rom (build 7.1), but I decided not to delete them for some reason]
it seems OP sounds like he knows what he is talking about, but lets start simple.
Have you tried going all the way back to 100% stock?
In droidstlyes FANTASTIC guide
do section 5, perhaps try with out repartition or the atlas....that has worked for me in the past.
I know on my THS ICS 7.1 build i had a "sleep of death" (wouldnt wake up) and i was lazy and did the 3 finger salute and it would ONLY boot into CWM. a battery pop would have been fine but like i said i was lazy. i had to Odin back to stock in order to re-flash everything. [luckily i had a nandroid from a few days earlier]
Good Luck
Edit: I have never seen or heard of a fassy that CAN get into Download mode and not be recovered to 100% functional.
I'm just thinking out loud here, but here are two things to consider. Perhaps the senior members will comment.
1. Have you considered flashing a different bootloader?
2. Is it possible you have a corrupt stock and/or pit file? Have you tried re-downloading them and giving it another go?
OP, can you post the md5sums of the files, along with the filenames that you are using in Odin/Heimdall?
thanks
Well, I ended up getting a droid bionic from a friend, so I will turn this fassy into a project phone. If I can get it to work I will sell it or keep it for backup. Anyway...
I have not tried the older blue recovery yet. I will try that when I get back to my computer. It seems like I've gone beyond anything I've ever had to try with this phone. I read on one thread that if odin did not work, keep trying heimdall over and over until the phone boots up. I must have tried at least 8 times on one run. It still won't go past samsung screen. I can get into download just fine. No matter how many different cwms I try, I can't get into recovery using the three finger method. Im pretty knowledgeable when it comes to this stuff and I didn't flash the wrong rom or kernel or anything like that. I was running smoothly on an ics rom until my phone froze. I did have it overclocked with ns tools, but not at the time the phone froze. I honestly don't think its hardware related, but merely a glitch in the software or a bad kernel that does not want to come out? I have no clue....help me revive this baby lol...
Sent from my DROID BIONIC using Tapatalk
jawman27 said:
I'm just thinking out loud here, but here are two things to consider. Perhaps the senior members will comment.
1. Have you considered flashing a different bootloader?
2. Is it possible you have a corrupt stock and/or pit file? Have you tried re-downloading them and giving it another go?
Click to expand...
Click to collapse
I've tried different pit files from different threads. Even the one from droidstyle's thread. I've also tried different versions of the following stock files from different "known" and trusted sites: DI01, DL09, ED01, EB01, EH03, CM7, CM9 other ICS roms and different kernels that suit each both voodoo and non voodoo. And excuse my newbness on the terms, but what do you mean by flashing a new bootloader?
Sent from my DROID BIONIC using Tapatalk
haoleflip said:
... but what do you mean by flashing a new bootloader?
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
Bootloaders can be flashed in Odin the same way a ROM can. A bootloader is the rudimentary software that gets the other software up and running. When Glitch's kernel started requiring Gingerbread bootloaders for complete functionality, a lot of us realized that just having GB didn't mean you had GB bootloaders.
http://www.mediafire.com/?fqojvsynkff93hc
Hopefully this link will work. It's certainly worth a try. It doesn't seem like you have much to lose. I'd recommend flashing it the exact same way you do a ROM. There's a bootloader section in Odin, but most people avoid it. Good luck.
Hey I recently rooted my Samsung Galaxy S II I9100, at first everything was fine, but i had some trouble installing apps so i used es file manager to install them, it began to work for some apps. anyway, this morning I woke and turned it on and it didn't get past the bootscreen(i left it for about 45 minutes on one occasion, and I tried rebooting many times.
The first thing i did after attempting to boot my device was to flash the kernel again via odin, this did not work(tried twice).
so i did a lot of research over the past 10 hours into my problem and have tried many different things; installing a stock rom, removing battery, pretty much anything on the forums that people said have worked. nothing.
I can get into recovery mode and download mode.
I don't care about my data on my phone, it has already been wiped.
It's still covered by warranty so i can wipe the flash count(?) and send it in for warranty IF I HAVE TO. preferably not however.
although i highly doubt it, I may have been using the wrong rom, and I may have forgotten to reset my phone before one of the re-flash's
So if you havn't figured out my question by now, how do i return my phone to working condition?
Don't get mad at me for making a thread that has probably been made a hundred times, none of the solutions in the other threads fixed my problems, and I was browsing not only xda but other forums for hours, I found that reason enough to post a new thread. Apologies if this is in the wrong section, I am new here, and never found it necessary to create an account until now, when I couldn't find a solution.
Help is appreciated, this problem is really rustling my Jimmies on Christmas day.
because this is such a problem, I will REWARD anyone who presents a working solution that does not involve sending it off for warranty or buying a jig. Sorry if i missed out some information, please request for missing info in a response.
1.forget about warranty and jig....that has nothing to do with your current situation.
2.post the details about your phone and what firmware your on and what crap you were flashing.
Maybe a simple reset/wipe in stock recovery is needed.
.
theunderling said:
1.forget about warranty and jig....that has nothing to do with your current situation.
2.post the details about your phone and what firmware your on and what crap you were flashing.
Maybe a simple reset/wipe in stock recovery is needed.
Click to expand...
Click to collapse
originally i was on ics 4.0.3, and i used this tutorial galaxys2root.com/galaxy-s2-root/how-to-root-galaxy-s2-i9100-icsandroid-4-0/ (can't post url link because im a new user) and this kernel by the file name "CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5.tar". I then searched for stock roms for it and got "CF-Root-SGS2_XX_OXA_KP8-v5.2-CWM5.tar" and "CF-Root-SGS2_XX_XEO_LPQ-PROPER-v5.4-CWM5.tar"
If you want a stock rom go to Sammobile,join(so you can download).....then input smartphone>android>your phone model>your country/carrier.
Choose whatever 4.0.3 it recommends after you input the above and hit send.
Then flash that with Odin and see what happens.
Then report back here.
I am from Australia and when I searched for roms for the I9100, no Australian roms showed :s
would one from another country work, or would that be locked or...?
Theres 3 listed for starters for the plain gt-i9100.....is that your exact model....or is it p/g/m etc.
This is why I asked for your model.
gt-i9100 is my model that's all it said in my phone information in the settings (before it stuffed up), manual, on start up and in download mode.
sorry, I'm not excellent with my technical android terminology.
false alarm, it just didn't load properly before, I will start a the download (will take like 15 minutes) and report back when i flash it. gt-i9100 is definitely my model.
You just input which one of these 3 applies,hit send,then download.
Then flash it (the extracted file)in download mode with Odin.
so i put the extracted file in the 'PDA' field, put it into download mode, plug it in and start the process?
Yep.
It failed the first 2 tries, I think I have a bad usb cord, but worked the third, might of been what stuffed it up in the first place maybe (?), thank you so much for your help man
Good.Wait til boxing day til you flash siyah-s2.v.4.1.5 kernel for root.......lol.
hehe... yeah... I'm not going to try root again... lol
syntaxibles said:
It failed the first 2 tries, I think I have a bad usb cord, but worked the third, might of been what stuffed it up in the first place maybe (?), thank you so much for your help man
Click to expand...
Click to collapse
Going back to your first post,maybe you could make a donation to one of the developers on this site of your choosing.
sounds good, which developer in particular would be a good choice?
I quite like Doomlord,but its up to you
And just post back on this thread if you need help rooting etc.
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).