Hello, today I got a Samsung Galaxy S2 from a friend. I'm not sure how to identify exactly which model, but it's american and doesn't have the oval home(?) button at the bottom.
I've done rooting and flashed roms before onto Samsung phones, and I haven't had this problem.
The phone started off completely stock, no modification whatsoever. Then I downloaded a kernel with clockworkmod on it, and it wouldn't boot again. It would get stuck in the bootloop with the little yellow caution symbol. After trying several other things I was able to flash another kernel onto it, however, something happened in ODIN and it disconnected. Ever since the only thing it does is the blue LED comes on. I cannot access download mode, or the recovery I was going for. When it's turned on it doesn't even have a bootloader.
Thank you very much for the help.
Your problem starts at 'I'm not exactly sure what model it is'. If it has no home button and does have a blue Led, it's most certainly not an i9100. I'm willing to bet you've been flashing the wrong firmwares all along.
Now that your phone disconnected during an Odin flash, it's done for. When you plug it in to the charger, does it get hot? If so, motherboard replacement.
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
Remove the battery and check the model.
Then go to the device's forum or ask the mods to move it 98% chance this is the wrong place for you.
Sent from...this is not even my S2
Related
Okay, So I am as NOOB as NOOB can be,
I got a used SGS2 (Bell/Virgin), I am on Telus so I figured, how hard can it be to unlock it instead of paying some dude to do it for me? (First mistake, and have been humbled every step of the way since!...)
Anyway I will try to keep this relatively short (it will be difficult)... ...I read a few things online and saw that I needed ODIN and a Rooting software, I originally used SuperOneClick, and to download the right insecure kernel to match my original one etc... ...problem is I obviously didn't read nearly enough when I started because I was almost done and then there was a hiccup when SuperOneClick said that I needed to enable SU in Kies. So I decided to go into Kies to try and do so but the instructions before I started Rooting said to put the phone in USB debugging mode. Apparently Kies doesn't see the phone if it is in that mode. Well by this time I can't get past the logo screen and this is where my downward spiral begins.
I then tried to unroot the phone to go back to stock but didn't really know what I was doing and then I read something about the cache needing to be wiped and then after that I read that maybe my OS was wiped. So at this point I did lots of reading (what I should have done in the first place) and most of anything useful I found was on XDA so that is why I am here. It seemed like yes, in fact my OS was wiped because of one of my not so S-M-R-T actions. So I fumbled through and found the right OS for my S2 and I had ODIN going strong and I had the OS loading, the green bar getting bigger in ODIN and the blue bar working it's way across the screen of my S2...I thought "finally!!, I rock!!"... ...then for some reason everything stopped! I had seen in a post that I had to uninstall Kies before doing anything, which I did...but I didn't see until after the fact that my anti-virus likely interfered (I didn't disable it for the process before I started).
At that point of course I was left with a phone that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
So then I was afraid to try anything else because many say to steer clear of Kies and also I had read that I may need a USB jig to be able to get it back into download mode because all I was getting was the "firmware upgrade issue" screen. I did make a USB jig with a resistance of 300K Ohms and I *can* get the phone into download mode. (Though another concern is that when I plug the USB jig in and it brings the phone into download mode, the counter is not reset and I read that that was supposed to be reset by the jig.)
So last night I got brave and decided to try and run ODIN and to have another attempt at installation of OS. Now I can get ODIN to detect the phone, but I put the I9100MUGLD3_I9100MBMCLD3_I9100MXXLD3_HOME.tar.md5 file into the PDA section of ODIN and it starts and gets to the part where it says loading firmware or something and then bootload.bin and it stayed like that for like, an hour and then I gave up, fearing that I am just going to screw it up even more.
So now I decided that I am not even close to knowing what to do next but every time I found anything to move forward it was on this site so I figured I may as well join the site since I have been here so often. Now I am hoping for some kind of miracle...so, in advance, please please please and thank you thank you thank you all for your input. (Sorry for the length of this I just wanted to get all the info I could into this)
Its quite a long story and didnt bother reading it.
If you can still access your phone via odin at downloadmode. Flash a stock firmware for your device and it should fix if it is just a soft brick.
Sent from my GT-I9100 using Tapatalk
UnwiredDroid said:
Its quite a long story and didnt bother reading it.
If you can still access your phone via odin at downloadmode. Flash a stock firmware for your device and it should fix if it is just a soft brick.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Sorry for the length of the story, I thought there may be alot of useful info mixed in with the useless info... ...when you say use stock firmware do you mean the kernel or the actual OS? I tried loading ICS onto it (which I thought was stock but I may be wrong). Is it supposed to be gingerbread or something else? Also where would I find a good file for it.
Thank you again for any input, very much appreciated!
Hey ,
I also have a Virgin Samsung S2 i9100 and the first time I tried rooting it, it got stuck on the screen with the yellow triangle and wouldnt move at all. I believe it was bricked?
anyways, I m not sure I totally understand your situation, but I solved my problem using this thread
http://forum.xda-developers.com/showthread.php?p=21493413
look it under the i9100M section. hope this helps
schtiven said:
Hey ,
I also have a Virgin Samsung S2 i9100 and the first time I tried rooting it, it got stuck on the screen with the yellow triangle and wouldnt move at all. I believe it was bricked?
anyways, I m not sure I totally understand your situation, but I solved my problem using this thread
http://forum.xda-developers.com/showthread.php?p=21493413
look it under the i9100M section. hope this helps
Click to expand...
Click to collapse
Thank you all so much for your help, I could not get it to work after several tries, I even tried three or 4 different USB cables and ports on my PC and still no. I read on another thread that one person tried another PC and it worked so I tried my friend's laptop and it worked!...my SGS2 boots up and all that now! Very very happy thank you all.
I have a SGH-I747M 4.1.1 Galaxy S3.
I used the Unified Toolkit and rooted/installed CWM, backuped and ready for a new ROM.
As I was installing this custom ROM (Pardus HD), and error popped up and it was aborted, (still in the CWM main menu)
but having only the said custom ROM zip file in the internal memory,
I figured I just shut down and download a fresh copy of the ROM.
and put it in an external SD card then power on the phone back into recovery.
Only thing is it wont power on anymore, the screen is just black, plugging in USB and computer just makes connected/disconnected noise.
(Devices say its "Qualcomm HS-USB DQLoader 9008")
Also tried taking out putting in the battery.
(I know my mistake is I never re-installed the backup) I've run out of ideas, please help.
I have a very similar problem. I had my battery checked thinking that could be the problem. My battery shows that is no good. I tried a new one and still nothing. I can't help but think if it were a missing program it would still come on at least. Lucky for me its covered under insurance. I'd still like to know what happened and if I could fix it.
I'd like to know too if I could fix it myself, other than ''the jig'' or a repair service. currenty trying to revive it still
edit: currently trying this Heimdall thing, goodluck to me...
Have you checked the battery? If I wasn't sending mine back on an insurance claim I would take it apart. I have a Motorola that has a fuse next to the battery under the back of the case. Seems dumb, I know but how could changing the rom "short" out my battery. Dumb again I always thought bricking was only being able to bring up recovery.
I think the battery is fine, as CWM was still running after the error.
That's pretty much what happened to me. Maybe we got to the same problem 2 different ways. Hope you get it figured out.
THIS IS GT-I9300 SECTION..
c'mon there was an stickie on top of this section for you..
HERE.. http://forum.xda-developers.com/forumdisplay.php?f=1705
Your problem is that you flashed a rom for gt-i9300 (International) and you have some U.S. variant of s3. That in most cases bricks the phone.
Probably time for a service center visit.
Verizon Galaxy Tab 10.1 4G LTE (sch-i905)
So I got this tablet from a friend who said it was bricked, said I could have it if I got it working. So I plug it in and it turns on no problem, strange. wiped tablet and added a couple apps. Got busy at work and the tablet drain power. That's when I got to see it bricked, but still not sure why it booted for a bit for me.
Symptoms:
Boots to Samsung Galaxy Tab 10.1 splash screen (not the animated one after), sits there for ever.
Boots to Odin update mode
When booting to recovery I get a blank, back lit screen and nothing ever.
I've tried:
-Pushing clockwork mode to fix recovery
-I've had a hell of a time finding stock firmware for some reason (it isn't on sammobile), but I did find one eventually. I pushed it to the tablet via Odin, and it was successful, but rebooted to blank black back-lit screen. Have to hard boot and hold power buttun until I see the splash screen to get that far. I followed the guide on rootzwiki reposted on icsforums - www icsforums com/forum/showthread / 13525 (sorry new member can't post links)
-Followed another guide that involved draining battery completely, no go.
I don't care what firmware I end up on, or if I can use LTE (I won't anyway)
I'm a network engineer so I'm tech savy, but not heavy on Android OS. I'm looking for anything else I can try. I saw another method involving heimdall suite, but can't find the files for my model.
Any help or guidance is greatly appreciated.
@Juicebox4242
I had this problem on my gt-p7510...
What I ended up doing was wiping my sdcard..I must have had something corrupt in my file system or a kernel issue( still not sure which )..
Since you have no recovery..I think you can use odin to repartition ( I CAN NOT STRESS ENOUGH THAT THIS IS JUST A GUESS )..I have not tried it..but i will search after this post to confirm..I also believe there is a way using ADB..again not sure..
I just wanted to post this so you would know somebody was looking and to maybe give you a couple ideas to follow up on...I'll search around and see what I find
Edit...I believe ADB will only work with usb debugging checked...But you can flash a stock rom in odin with re-partition checked..you need a .pit file....I think...
Edit...Here is a link to a stock rom thread for you're device..It seems to have helped a couple people with their soft-bricked devices..just follow directions in OP..no repartition checked. I cant even find a .pit file to do a re-partition with for you're device..
http://forum.xda-developers.com/showthread.php?t=1342995 Let me know if this works for you..
Thanks for the post!! Really appreciate it.
That firmware is the one I found in the end and tried. Odin pushes it ok, but then still doesn't boot. In fact after pushing that firmware it boots to backlit blank screen, but when hard reset boots to splash screen.
I tried a pit file I found that I thought was the right one, but it failed when I used that so it must have been wrong.
Juicebox4242 said:
Thanks for the post!! Really appreciate it.
That firmware is the one I found in the end and tried. Odin pushes it ok, but then still doesn't boot. In fact after pushing that firmware it boots to backlit blank screen, but when hard reset boots to splash screen.
I tried a pit file I found that I thought was the right one, but it failed when I used that so it must have been wrong.
Click to expand...
Click to collapse
I have the exact same problem as you, except sometimes I can't my tablet to boot. I know it is a software problem because before I was messing with recovery yesterday, everything was working just fine. All I wanted to do was restore to factory settings and instead ended up bricking the device... If you find / know the answer, please do share.
Juicebox4242 said:
Verizon Galaxy Tab 10.1 4G LTE (sch-i905)
So I got this tablet from a friend who said it was bricked, said I could have it if I got it working. So I plug it in and it turns on no problem, strange. wiped tablet and added a couple apps. Got busy at work and the tablet drain power. That's when I got to see it bricked, but still not sure why it booted for a bit for me.
Symptoms:
Boots to Samsung Galaxy Tab 10.1 splash screen (not the animated one after), sits there for ever.
Boots to Odin update mode
When booting to recovery I get a blank, back lit screen and nothing ever.
I've tried:
-Pushing clockwork mode to fix recovery
-I've had a hell of a time finding stock firmware for some reason (it isn't on sammobile), but I did find one eventually. I pushed it to the tablet via Odin, and it was successful, but rebooted to blank black back-lit screen. Have to hard boot and hold power buttun until I see the splash screen to get that far. I followed the guide on rootzwiki reposted on icsforums - www icsforums com/forum/showthread / 13525 (sorry new member can't post links)
-Followed another guide that involved draining battery completely, no go.
I don't care what firmware I end up on, or if I can use LTE (I won't anyway)
I'm a network engineer so I'm tech savy, but not heavy on Android OS. I'm looking for anything else I can try. I saw another method involving heimdall suite, but can't find the files for my model.
Any help or guidance is greatly appreciated.
Click to expand...
Click to collapse
Did you ever get this fixed? I've had the same problem for months. I just gave up and put it away. I recently fixed a Galaxy Tab 2 and now I want to see if anyone else was able to fix this i905 not booting issue.
did anyone know the solution of this question
Hi everyone,
Hopefully I have put this in the right place.
I have a N7000 sitting doing nothing.
I made it not work at all in trying to fix it.
I know alot more now but believe the device soft bricked and in trying to fix ended up using odin, a stock flash and ticked repartition.
So, the ROM install failed and the partitions got wiped.
The device does not show anything on the screen now at all. Believe it charges, as when I plug it in the device gets warm.
Anyways, is there someone near me (sydney, australia) that has a JTAG device which could be used to bring this device back from the dead?
Thanks
Hello. I have a 2012 Samsung Tab 2 that was branded for ATT and the model number is SGH 1497. It has been in a drawer for a year and I never use it but I thought I would experiment with it and try to install the Marshmellow Rom even though I am a noob at this stuff. My first problem was that I saw nothing for my version SGH 1497 but I did read on a forum that the Rom 5113 would work for that model. After going through a lot of websites I finally found one that seemed pretty easy and the root process went perfectly for me, no issues at all. I then followed instructions and downloaded the needed files and moved them onto my tablet and all was going well. I was then instructed to boot into recovery mode and that is where my troubles started. I believe it said to hold power and volume down key. Recovery mode would pop onto the screen but then vanish and it would never go into it. So I did more reading and someone had posted that I needed to download the toolkit and re-install a new recovery mode. So I did that just fine and still the same thing happened. I then tried 2-3 more of the other recovery modes and the same thing happened. At that time the tablet would still boot normally. So then I did something else and now my tablet wont turn on anymore. If I push power enough times the Samsung logo will pop onto the screen and then it goes away and that's it. It will turn on to download mode but that is it. Nothing else. Im not upset because I knew this could happen but I surely should have came here first. Is there anything I can do to get this thing back working again or is it hopeless??
Thank you for any help and advice.
Thomas
I was able to fix it by finding the exact same firmware that ATT put on this tablet and then using Odin to flash it. Works fine and is rooted.
Does anyone know of a custom rom that will work on this model sgh 1497??
Thanks.