New here and need some help - Galaxy S II Q&A, Help & Troubleshooting

Hello,
I reciently rooted my samsung galaxy s2. I tried a few roms so i could get used to the system or restoring etc. However i encountered a problem whilst having a peek at an alpha jellybean rom, where i noticed that my CWM app on the phone had vanished? I attempted the restore using the 3 button combo and found that i kept recieveing E: can't mount/ E: can't cache messages whilst on the restore screen. i could find my latest restore on my sd card however it wouldnt restore. I believe the CWM was removed from my phone which caused it to not work. I was then stuck in a bootloop. no matter what i done, boot to a stock rom via odin, try the different CF roms i and try to put CWM back on to the phone? I read a post on here from someone who had the same problem, who was told it looked as though there is a problem with the partitions. i followed a tutorial and used odin to put Latona 20110114.pit on the phone. it said i would get a blank screen once this has done and i needed to remove then place the battery back in the phone then put it into download again. This didnt happen!! I done as instructed and now my phone wont go into recovery mode, download mode or even boot loop. I fear i have completely bricked my phone so i am trying to use oneclick heimdall to sort it however my PC keeps saying i need admin rights to install it which i have.
Can someone please help me out. I am new to this so please go easy on me.
many thanks

If you have no signs of life from the phone, it's probably cactus.
You might as well try a jig (but unlikely to work; still try one tho). Only option is service centre & hope they can't tell/don't care you've been messing with it & fix it under warranty or JTAG repair by a 3rd party repairer, at your cost obviously; will be cheaper than having Samsung/an authorised repairer fix it if they refuse warranty service which they're quite within their rights to do.

edinsam said:
i followed a tutorial and used odin to put Latona 20110114.pit on the phone.
Click to expand...
Click to collapse
First result of searching suggests that's meant for the I9003. Good job.

HA
Hello,
Awe well then. never mind eh, whats done is done! Its totally bricked so i thought i would chance my luck by sending it back to O2 for repair. I was reading the only other way to get the phone running again was to take it to bits and hook it up for some stock flashing. so heres hopping they sort it!
lesson learnt!!!

Related

Phone won't start after flashing in Odin...

Hey guys
1) Restarted my phone today using CM10.1 from a very recent nightly (within the past week).
2) On restart, phone froze and got kernel panic.
3) Restarted into CWM and tried to do a restore to an earlier backup I had made.
4) Half-way through the restore, I got ANOTHER kernel panic (never had that before)...
5) Only things I could do with the phone after that was enter download mode...nothing else...couldn't enter recovery mode anymore.
6) Went into download mode and flashed this CWM-Recovery (http://forum.xda-developers.com/showthread.php?t=1118693) and followed the instructions to the letter.
7) Odin 3.07 hung on NAND Write Start
8) Tried using Odin 1.3, and it seemed to flash correctly. It says completed no errors.
Phone will now not even start and is completely unresponsive...pressing any combination of buttons will not start the phone, and the phone is not recognized in Odin anymore...did I just hard brick it? Any other ideas?
Thanks,
Elliott
Service centre. Although if you can have someone who does JTAG's have a look at it to determine whether it can be JTAG'd without you giving them any money up front (I.E you only pay them if it can be JTAG'd), try that first.
Thanks that's what I thought.
Also, try a jig if you can get one. In all likelihood won't work, but stranger things have happened & you have nothing to lose.
Yeah thanks that's what I plan on doing. Any idea what I did wrong, though? I don't want it to happen again if I get it working with a jig.
Impossible to say. Not sure why you flashed that nondescript kernel/recovery in that situation tho given it probably wouldn't have worked even if the flash had been successful (You would probably have ended up with bootloop given recovery was obviously 'broken'). I would have flashed stock with Odin (And that's certainly what I tell people in your situation on here to do because it normally works).
But flashing recovery rather than a stock rom probably didn't break your phone, put it that way, so you didn't do anything 'wrong' per se. Just remember if you get into a similar situation again, go back to stock via Odin & start again (re-root your phone/restore a backup, flash your custom rom/kernel again, etc).
If the jig works (and don't get your hopes up or anything, we're talking a 1 in 10,000 chance, and that's probably being generous), flash stock with Odin (you wont have much choice).
Well...brought it to a JTAG specialist today and he couldn't fix it either...says it's very rare and he's had 5 out of 80 S2's like this happen without being able to fix them...
Bummer. Motherboard replacement in that case. If the phone's under warranty, take it to a service centre & say as little as possible. You might blag it for a warranty fix. No warranty ? You can still have a new motherboard put in by a service centre (more expensive option usually), or you can source a 2nd hand MB from a 'donor' phone (one with a broken screen that's otherwise OK, etc) & either swap it in yourself or pay a local mobile repair shop to do it (usually cheaper option).
@ OP By following what you flashed I noticed the date, we're talking about a 2 years old thread, a lot have changed since.
Not sure that was what bricked your device but I get that panic mode.
The other thing that it comes to mind is nand corruption, which has been quite common these days with people running custom.
I'm with bungle there, the best recovery package is going back to stock and start fresh.
I, on the other hand, wouldn't accept the situation you are on, I would spend a whole week trying to get that phone to boot again, whether a second opinion on a jtag, a new jig, another battery or any other thread on here at xda.
If the device gets hot near the rear camera and it won't even charge nor get warm around that area dismiss what I just said and proceed with the mobo replacement bungle suggested.
And of course, if you did something else to your device and didn't share it please, come clean so others don't freak out by reading this.
Sent from...this is not even my S2
Hey
Nothing else was done to the device...just what I stated exactly.
I caved today and bought a BNIB S3 because I couldn't go without a phone anymore...
Thanks for the help, guys
Elliott

[Q] Repair shop killed my phone ?

Hello,
I have a Samsung Galaxy S2.
After reading this post http://forum.xda-developers.com/showthread.php?t=2382579 I decided to root my phone.
So I went ahead and started with this step http://forum.xda-developers.com/showthread.php?t=1118693 because I was unsure if I had a kernel with the MMC-SUPERBRICK-BUG.
After I flashed CWM-SuperSU-v0.97.zip using Odin version 1.85 and after the phone rebooted it was stuck at the "triangle screen" for a few seconds then the display went black and I couldn't do anything further.
Up to this point the phone was still accessible in download mode (volume up, power and center button). I believe this is called "download mode". Sorry but I am a complete noob with rooting phones, etc...
So I panicked and took the phone to a repair shop (big mistake). The guy ran it in download mode then tried to flash something onto the phone (I think he used all 4 fields: Bootloader, PDA, Phone and CSC.
Then, in the middle of the operation, Odin froze when writing "setting up connection". Then the phone died ! pressing the 3 famous buttons does nothing and the phone just stays dead.
I had to leave the phone there as the guy said they will try to bypass stuff and try to connect to the CPU directly (sorry again if this sounds noobish). I did update my modem firmware and my computer BIOS in the past... but I guess this one was more complicated.
At the shop, they asked me to check again in 3 days. I am lost here. I don't know what to do anymore.
Is the phone hard bricked ? Should they bear all expenses for what they did ? I would bring back my phone and try something like this http://forum.xda-developers.com/showthread.php?t=1878255 or even a stock flash but I am afraid I cannot do that as the phone isn't even powering up anymore after they tried to repair it at the shop.
Any advice is appreciated.
Nope. You borked it. You tried to flash custom firmware to the phone & obviously failed spectacularly at it. Instead of trying to flash it yourself via download mode (which you could easily have done unless the NAND was borked), you paid them to do it. Sometimes flashes go bad. Sounds like that's what happened in this case.
Reading between the lines they sound like they're going to try & JTAG it (or have someone else do it). And if that fails I presume they'll change motherboards. You could always get the phone back & take it to someone who does JTAGs if that shop doesn't themselves.
MistahBungle said:
Nope. You borked it. You tried to flash custom firmware to the phone & obviously failed spectacularly at it. Instead of trying to flash it yourself via download mode (which you could easily have done unless the NAND was borked), you paid them to do it. Sometimes flashes go bad. Sounds like that's what happened in this case.
Reading between the lines they sound like they're going to try & JTAG it (or have someone else do it). And if that fails I presume they'll change motherboards. You could always get the phone back & take it to someone who does JTAGs if that shop doesn't themselves.
Click to expand...
Click to collapse
Yes I know I failed at it
Or maybe the shop technician is the one who broke it. At least when I had the phone with me I was still able to boot in Odin mode.
Do you think I could have recovered my phone if I had kept it with me and it was booting in download mode ?
I feel so pissed that I took it to that shop. I just wish I hadn't panicked and I had tried, instead, to fix it at home by asking for more help.
Anyway I still haven't paid them anything so far.
We agreed that they will pay for the motherboard because I brought in a working phone (that would power up at least). The owner of the shop was nice enough to agree that he would only charge me fees for installing new software on the phone (even if they have to change the motherboard) because he knows the phone was booting in Odin mode when I came in to the shop and his technician flashed the wrong firmware.
I also wrote down the board serial number so I can be sure they changed it (if they say they did that). So you are telling me the phone can still be fixed ? What does JTAG mean ?
Even if it is fixed I think I will be too scared to try and root it again. Unless I can understand in advance, step by step, what I need to do and what file version(s) I need to use.
Ok, I got my phone today in good working condition.
According to the shop, they had to replace an IC (I don't know what damaged the IC, I am assuming this happened when they tried to electrically jolt the phone) then JTAG it to get it to work again. They charged me a small fee (and they did end up bearing more than 50% of the expenses) because I brought in a phone that was booting in download mode and they take responsibility for what happened after that (flashing wrong files which caused the phone to completely stop booting).
Anyway, long story short, this was my first attempt to root a mobile phone and I learned my lesson.
I am running the following:
Model Number: GT-I9100
Android Version: 4.0.3 (which I will need to upgrade to 4.1.2 of course)
Baseband Version: I9100XXLPW
I know you will say read the sticky posts or the guides but the truth is, that's exactly what I did (you can see the links to the guide I tried to follow in my original post) and I still ended up failing at rooting/installing cyanogen on my phone right after installing Clockwork Mod.
The truth is I am scared to try again and mess up the phone. So this time I would rather be safe than sorry.
What can I do, this time, to safely root it and install a mod like Cyanogen.
Detailed steps are appreciated:
- Do I need to upgrade to 4.1.2 before rooting as 4.0.3 might have the superbrick bug ?
- How to backup the phone.
- Odin version to use, ClockWork Mod version to use, Cyanogen version to use
- How to connect the phone, how to reboot in download mode and all the necessary actions to avoid bricking my phone.
No spoon feeding aloud on XDA.better to read and learn how to do this and that but before you flash anything after learning how to do that learn how to fix it if it doesn't work. :thumbup:
andrewwright said:
No spoon feeding aloud on XDA.better to read and learn how to do this and that but before you flash anything after learning how to do that learn how to fix it if it doesn't work. :thumbup:
Click to expand...
Click to collapse
Fair enough, I figured I'd get that reply from someone and it's normal to be honest.
I decided not to try anything on my phone before I re-read the guides and be sure I know what I am doing.
I will also keep the phone running on stock firmware (after upgrading to JB 4.1.2) to check the battery consumption behavior which, I hope, will be fine since someone tampered with my phone's electronic components at the shop.

[Q] possable SDS, can i fix or data recover? help!

hey guys thanks for any help. here is my problem.
i got an s3 i9300T to fix for sister in law. she apparently went in to telstra and got told that if it was her fault she would have ot pay for the repairs and she needed a phone while its away so she just payed of the contract. not sure what she exactly wants except for her data back.
upon taking a quick look it had a familiar screen. the computer triangle phone screen. im like sweet easy fix with an odin flash.
i installed a 4.0.4 version of telstra software(will look what one later) and it magically booted im like sweet. then encounter the sim lock. had to wait a day for the information so i left it over night on charge. (she wanted her contacts as well apparently but at the time i didn't know what she wanted really and i didnt just think to take out the sim.) ended up asking what she exeactly was wanting and phone was looking fine. tryed to update through kies and apparetly wasnt not able to be done on that android version. i left it another day and noticed that it was stuck on that boot logo/splash screen. i noticed i can still get in to recovery and download so i tryed to reflash same software. unsuccessful half way i tryed to use a 4.1.2 version that would not get pasts a tz** (replace starts with letters i cant remember atm) i suggested to just keep in on wanrrenty as odin hasnt counted anything yet. but they seam more for data recovery. should i try something iive tryed again or not tryed. or just try flashing recovery and trying to get the data off that way?
as i cant access stock recovery atm and its back to the computer triangle?
i know i dragged on sorry hope i explained correctly.
sorry fail to understand the post and your problem.
If its SDS you cannot recover data but you can fix with a new motherboard .
as far as i can tell i cant get the device too boot or accept new firmware, and it looks to be the sds problem but im not sure.. i think ill try and install a custom recovery and see if i cant mount it and get the data back.

[Q] My S2 won't start after trying to install and root cyangenmod.

Hey, i was going to install cyanogenmod and rooting it. downloaded all the files then the cyangenmod failed, had to restore phone and it only booted in recovery, then i dide full wipe on phone. Now phone will not start it's dead, won't start in recovery either download mode. I need HELP!:crying:
Read this link carefully and try everything it says.. http://forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Its to bring your phone to download mode and to life again.
^^^
No, it's not. Have you even been through the thread yourself ?
There is only one thing in that thread that might (and it's a very big might, like a 1 in 10,000 chance) help a phone that won't boot/no download mode or recovery, and that's the 'jumpstart' method. And I can count the number of people I've seen this work for in 2.5 yrs on one hand. Same with a jig, almost certainly won't work but try one if you can get one.
Motherboard replacement is almost always the only way to fix this, assuming a JTAG can be attempted at no cost if it doesn't work; JTAG's almost always won't work in this situation either.

[PLEASE HELP] T-Mobile Galaxy S5 Random Reboots, Freezes and Force Closes.

Hello, This is my first Post on XDA so please help me to familiarize myself with rules and procedures and I apologize if I break any in any way.
Okay, So My phone (SM-G900T) is about 5 months old. I bought it in August, Without insurance (Terrible Idea), and now it is having problems. In the amount of time I've had it, I rooted it in mid to late September and used only an app called Xmod for a game. I then started using greenify, solid explorer and eventually used Xposed installer to try a few Xposed modules. Specifically I used, the YouTube adaway, Rich Pandora notification and that's about it. I also later installed Samsung Tools to backup my IMEI and important partitions.
A few days ago my phone randomly rebooted in the middle of a YouTube video so I let it reboot, but it rebooted again, and again, and again. I pulled the battery and turned it back on but the same problem persisted. I couldn't do anything to fix it so I just decided to factory reset the device through the stock recovery. Also, I did not install any custom roms or anything either. The factory reset did nothing. Now when I was in setup, everything force closed, froze and rebooted, repeatedly. So I found the original firmware that my phone came with and flashed it to my phone through Odin because I literally had no hope of what to do anymore. The problem lessened so I didn't install all my apps and overload the device as it would reboot when the RAM would get pretty full or too many things were running simultaneously in the background or foreground. The problem got a little worse so I factory reset one more time and it lessened again but now it came back and factory Resetting isn't lessening the problem. Now it just force closes a bunch of stuff and freezes and reboots into a bootloop midway through initial setup. I am desperate at this point right now and I need help from you guys. I don't have warranty because I rooted and I made the Extremely stupid decision of not getting insurance. So please can anyone help me out? I will be eternally grateful if you can help me turn this $609 brick into a phone again.
I will try to check this thread daily, but I go to school and I may not respond immediately, so please understand.
ahmed12534 said:
Hello, This is my first Post on XDA so please help me to familiarize myself with rules and procedures and I apologize if I break any in any way.
Okay, So My phone (SM-G900T) is about 5 months old. I bought it in August, Without insurance (Terrible Idea), and now it is having problems. In the amount of time I've had it, I rooted it in mid to late September and used only an app called Xmod for a game. I then started using greenify, solid explorer and eventually used Xposed installer to try a few Xposed modules. Specifically I used, the YouTube adaway, Rich Pandora notification and that's about it. I also later installed Samsung Tools to backup my IMEI and important partitions.
A few days ago my phone randomly rebooted in the middle of a YouTube video so I let it reboot, but it rebooted again, and again, and again. I pulled the battery and turned it back on but the same problem persisted. I couldn't do anything to fix it so I just decided to factory reset the device through the stock recovery. Also, I did not install any custom roms or anything either. The factory reset did nothing. Now when I was in setup, everything force closed, froze and rebooted, repeatedly. So I found the original firmware that my phone came with and flashed it to my phone through Odin because I literally had no hope of what to do anymore. The problem lessened so I didn't install all my apps and overload the device as it would reboot when the RAM would get pretty full or too many things were running simultaneously in the background or foreground. The problem got a little worse so I factory reset one more time and it lessened again but now it came back and factory Resetting isn't lessening the problem. Now it just force closes a bunch of stuff and freezes and reboots into a bootloop midway through initial setup. I am desperate at this point right now and I need help from you guys. I don't have warranty because I rooted and I made the Extremely stupid decision of not getting insurance. So please can anyone help me out? I will be eternally grateful if you can help me turn this $609 brick into a phone again.
I will try to check this thread daily, but I go to school and I may not respond immediately, so please understand.
Click to expand...
Click to collapse
Do you have SD card installed? If you do try taking it out and leave out or replace with another SdCard. Then flash the original stock firmware as you said you did before through (odin!) Then if that dont work try kias3 and use the emergency firmware recovery tool. Before you do any of this make sure you factory reset through stock recovery if possible.
Sent from my SM-G900T?
---------- Post added at 03:17 PM ---------- Previous post was at 03:07 PM ----------
Have you tried this tool? I had the same issue with my phone and reinstalled firmware and stock recovery through this tool and it stopped. If none of these tips work id say your phone may be borked or have faulty hardware. Take a look here as welll. Hope you can get your phone back to normal. I can understand what you're going through, like i said i had same issue with mine and mine has seems to be fine as of now. http://forum.xda-developers.com/showthread.php?t=2721146 . GOOD LUCK
Sent from my SM-G900T ?
beachbum40 said:
Do you have SD card installed? If you do try taking it out and leave out or replace with another SdCard. Then flash the original stock firmware as you said you did before through (odin!) Then if that dont work try kias3 and use the emergency firmware recovery tool. Before you do any of this make sure you factory reset through stock recovery if possible.
Sent from my SM-G900T?
---------- Post added at 03:17 PM ---------- Previous post was at 03:07 PM ----------
Have you tried this tool? I had the same issue with my phone and reinstalled firmware and stock recovery through this tool and it stopped. If none of these tips work id say your phone may be borked or have faulty hardware. Take a look here as welll. Hope you can get your phone back to normal. I can understand what you're going through, like i said i had same issue with mine and mine has seems to be fine as of now. http://forum.xda-developers.com/showthread.php?t=2721146 . GOOD LUCK
Sent from my SM-G900T ?
Click to expand...
Click to collapse
Okay, so I'm resetting it back to stock firmware through Odin as we speak. And yes, I had an SD card and have already taken it out and left it out and reset but still the problem has persisted, I will definitely try the solution you just mentioned, here I go. And thank you for replying...
Edit:
Hold on, which do you want me to try first? kias3(can you please link it if possible) with emergency firmware recovery tool? OR the Unified Android Toolkit?
Also... I don't exactly know how to use the toolkit, can you verify the steps to take to use the toolkit properly if I should use this solution? I'm sorry but I'm not very advanced at Android development, just intermediately experienced I suppose...
ahmed12534 said:
Okay, so I'm resetting it back to stock firmware through Odin as we speak. And yes, I had an SD card and have already taken it out and left it out and reset but still the problem has persisted, I will definitely try the solution you just mentioned, here I go. And thank you for replying...
Edit:
Hold on, which do you want me to try first? kias3(can you please link it if possible) with emergency firmware recovery tool? OR the Unified Android Toolkit?
Also... I don't exactly know how to use the toolkit, can you verify the steps to take to use the toolkit properly if I should use this solution? I'm sorry but I'm not very advanced at Android development, just intermediately experienced I suppose...
Click to expand...
Click to collapse
Try kies first that dont work try toolkit. Just Google how to use the toolkit it's pretty self explanatory but I don't think you'll need to use the tool kit anyways. http://www.sammobile.com/kies/
HOW TO USE RECOVERY TOOL IN KIES
http://forum.xda-developers.com/showthread.php?t=2261153&page=4
beachbum40 said:
Try kies first that dont work try toolkit. Just Google how to use the toolkit it's pretty self explanatory but I don't think you'll need to use the tool kit anyways. http://www.sammobile.com/kies/
HOW TO USE RECOVERY TOOL IN KIES
http://forum.xda-developers.com/showthread.php?t=2261153&page=4
Click to expand...
Click to collapse
okay, I tried resetting it using Kies3 but the device was not recognized so I had to find a different way because the guide on how to use Kies advised using Odin if Kies didn't recognize your phone. I don't have a code either, So I tried reflashing the stock firmware through Odin and it started up, froze and went into what I presume to be a bootloop as it is stuck on the T-Mobile splash screen with the notification light pulsing continuously. Did I also mention where my phone says Knox warranty void 0x1 there is another statement that says "Counter: 4" or something like that, while I am in download mode, does this have any significance? but yeah, other that Kies and Odin, I'm not sure if the android toolkit will help, because it's basically doing that same thing as I am with Odin, just more automated... Or am I wrong?
but as far as I know, that toolkit is literally the last option I have left, I guess I'll be trying that out tomorrow, with option 10 I believe where it says "10. Download, Extract + Flash Stock Firmware via Odin" but I'm not sure what ADB mode means... I can't really boot up the device so I don't know if that applies
Also, on a side note, how much do you think this will cost if I were to send the phone to Samsung and pay for repairs out of pocket, and do you think they could even repair it at all?
You know what... Do you think if I somehow installed CM12 on the device that the problem would fix itself? Because to me it seems like it's the Samsung software itself that is causing all this trouble along with a few Google apps. Now how would I root it and flash CM12 if it won't boot up fully...
Not sure if this would brick my phone either, let me know if it would if I tried to root through Odin and try to install CM12 through CWM recovery or something
Just throwing ideas, hoping this thread doesn't die before my problem is solved
Also, does geeksquad repair Samsung phones one time for a low fee if you've voided warranty?? If so then this could possibly be my final solution.
Also Never EVER buying a Samsung device again, they just aren't what they used to be back in the day, the other OEMs have caught up and left Samsung and their revenue in the dust...
ahmed12534 said:
Also Never EVER buying a Samsung device again, they just aren't what they used to be back in the day, the other OEMs have caught up and left Samsung and their revenue in the dust...
Click to expand...
Click to collapse
I disagree with this completely. Very few other handsets can hold a candle to the S5 or the Note 4. I don't know of anybody that has the problems you are describing with their phones without a hardware issue of some type or bad app. The Samsung software runs perfectly on millions of devices without the issues you're having. Therefore it's probably a bad app you've gotten a hold of, or you have a bad phone. CM12 will only introduce more issues and probably won't solve anything.
A stripped down custom rom might be a good bet because you can then start adding your apps back to find out where the issue is, or if it still has the same issues then it almost guarantees that there is some kind of a hardware issue.

Categories

Resources