Hello ppl,
i got a big problem, i hope someone can help me.
A friend of mine, gave me his galaxy s 2 to fix it. It just showed the battery icon with a circle running into it.
I fixed it with the JIG and got into download mode.
Everything is fine until now, even the flash with Odin shows success, but the phone just wont start up.
It doesnt matter what i do, or flash, its stuck in the samsung galaxy s II screen.
Download Mode is working, but Recovery not. When i try to enter the recovery mode, the phone hangs with the same screen like above.
Is there anything i could try to fix this?
Thank you
geminga
Okay relax, as you can get into download mode, there's a chance that you can still fix it.
I think you're running the wrong kernel or modem here.
I advice you to freshly install a new rom, and then install a CF-Rooted kernel that allows you to get back into recovery.
Once you got that worked out, get into recovery and select Wipe/factory reset. It should boot now.
If this still does not solve your problem, install VillainRom 2.0 using the process described in the thread. I had the bootloop problem too, but Wiping, Flashing and Wiping again did the trick for me.
Thank you mate I will try this later. Im will report if I was successful. (i hope so)
I flashed 2.3.4 ROM with Odin and then CF-Recovery but i can still not access recovery mode. It shows the yellow triangel but still hangs with the samsung galaxy screen.
I think that phone has become a nice paperweight...
As 2.3.4 is a test release i would try older stable firmware .
Flash a stock 2,3,3 rom via Odin and see if it boots .
jje
Is there something for Samsung that completely replaces everything including ROM,recovery and such things?
From my desire I know, if a RUU can't boot your phone it is 100% bricked. So I need something like that for that sgs2, to be sure that this is no hardware failure...
I will try some flashes and report after that.
Sent from my HTC Pyramid using XDA App
what i would do is install one of these carrier branded ROMs http://forum.xda-developers.com/showthread.php?t=1113928
and see if it boots, if it does then flash the cfroot [specific to the carrier version you choose e.g. KF2] make sure thats the right one. that should give you recovery as prodygee has said. then do a full wipe, system, data, cache, dalvik and reboot.
afaik this should work. that's worked for me on numerous bootloops!
Hope this helps, Rumble
solved [Arrow Galaxy s 2 wont start]
i just followed this link... >>1.Make sure that your phone is Samsung Galaxy S2 not any other.If you try this process on any other phone then the phone will be damaged.
2.Create a backup of your all useful phone data with the help of backup apps that ensure your phone data.
3.This process will take several minutes or may be hours so make sure that your phone battery consumption is maximum.
4.Remove the SIM card and external storage SD card.
5.Download both these files.
Download Gingerbread 2.3.4 XXKGI Firmware
Odin3 v 1.83
Procedure for Update Samsung Galaxy S2 GT I9100 to Gingerbread XXKG1 2.3.4 Firmware.
1. Open the Odin.exe file you will see the window image on your screen.
2. Switch off your phone then press and hold the Volume Button with the Power Key and HOME to turn the phone into the download mode.
3. Now connect your phone via USB cable to the computer. After connectivity you will see the window screen in which you see the COM ID 5 as a yellow color.
4. Now add the following files in the corresponding options:
PIT – u1_02_20110310_emmc_EXT4.pit
PDA – CODE_I9100XXKG1_CL349526_REV02_user_low_ship.tar
Phone – MODEM_I9100XXKG1_REV_02_CL1034110.tar
CSC- GT-I9100-CSC-MULTI-OXAKG1.tar
5. Click on the "Start button". Then updation process is start and wait for some time.Please don't interrupt your device will installation.
6. When the installation is completed reboot your phone and remove cable connectivity.The previous version of this firmware is also stored in cache memory.Remove your previous firmware version by dialing*2767*3855#.Now Update and check the latest version by dialing *#1234#.
it worked perfectly for me
Wellp, I tried to install Cyanogenmod and it bricked the crap out of my phone. I followed their guide at http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide and got to the "The Samsung Vibrant now has ClockworkMod Recovery installed. Continue to the next section." step and upon my phone's startup (with the added Clockworkmod flash screen) was greeted with nothing but a black screen. All I see is the samsung "S," glowing for ten or so seconds, like the Windows logo, then it goes black. I tried One Click Unbrick (http://forum.xda-developers.com/showthread.php?t=1153310), which restarts my phone, and brings me back to the same screen. Next, I tried doing the three button (sound-up, sound-down, and power) boot into the Android System Recovery program. There, I deleted the cache data, all user data, and attempted to reinstall packages, but I got a "failed to verify whole-file signature" error, as well as a "signature verification failed" error. I also, tried to re-flash via ODIN, but the only way to get it to see the phone is to boot it to the S logo screen (and the darkness beyond). There is the no-man's-land that Odin detects. Unfortunately, Odin gets stuck at the connecting step, and goes no further (unless that takes more than a few minutes). Fun stuff.
I'm sure you get people asking for help all the time, so I am very sorry to be yet another person asking, but this is quite the frustrating brick.
I am able to boot into download mode, as well as the android recovery menu (the aforementioned area with clear cache, user data, etc.) so I have found a bit of solace in those facts.
Thank you so much for your time.
rushmix said:
Wellp, I tried to install Cyanogenmod and it bricked the crap out of my phone. I followed their guide at http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide and got to the "The Samsung Vibrant now has ClockworkMod Recovery installed. Continue to the next section." step and upon my phone's startup (with the added Clockworkmod flash screen) was greeted with nothing but a black screen. All I see is the samsung "S," glowing for ten or so seconds, like the Windows logo, then it goes black. I tried One Click Unbrick (http://forum.xda-developers.com/showthread.php?t=1153310), which restarts my phone, and brings me back to the same screen. Next, I tried doing the three button (sound-up, sound-down, and power) boot into the Android System Recovery program. There, I deleted the cache data, all user data, and attempted to reinstall packages, but I got a "failed to verify whole-file signature" error, as well as a "signature verification failed" error. I also, tried to re-flash via ODIN, but the only way to get it to see the phone is to boot it to the S logo screen (and the darkness beyond). There is the no-man's-land that Odin detects. Unfortunately, Odin gets stuck at the connecting step, and goes no further (unless that takes more than a few minutes). Fun stuff.
I'm sure you get people asking for help all the time, so I am very sorry to be yet another person asking, but this is quite the frustrating brick.
I am able to boot into download mode, as well as the android recovery menu (the aforementioned area with clear cache, user data, etc.) so I have found a bit of solace in those facts.
Thank you so much for your time.
Click to expand...
Click to collapse
which rom did u come from?
Froyo. I followed the guide to a 't' and got this black screen. I have no idea what I did wrong.
Well, I need to run off to work now, but I'd really appreciate any responses.
It seems like my phone isn't being detected by odin or windows when it is in download mode, though windows does recognize that a Samsung USB device is being connected. This is recognized in the windows tray (under the name "Samsung_Android"), and in Heimdall's Zadig driver tool ("Samsung_Android").
Hmm first tthings first, your reinstall package error seems pretty simple, yu dont have the right update.zip and recovery combination... if u wanna solve that problem, find the recovery 3e to 2e tool (google it) and run it (follow directions).. then you can run reinstall packages (might havr tto do it twice). If that doesnt cut it, find the CWM update.zip and put iit into the root of your internal sd card (the 12gb one), then run reinstall packages again. You may have to reinstall packages more than once.
Your odin problem might be caused by a lack of drivers on your comp... go on the android dev section and look for a thread talking aboout ms64 and 86 drivers samsung something...
If you can get into download mode, you can unbrick your phone so dont panic
Now odin is a very dangerous tool imo so if you really are sorry about askint, do us a favir and read the sticky oon how to odin before you use it so you dont have to come back and ask us about how to Really unbrick your phone
Also, your brick is referred to as a soft brick and the android recovery program is referred to as recovery mode.
And if you really **** up, we now have the unbrickable mod in the vibrant android dev section which will unbrick your phone no matter wat (it takes somr hardware modifying though)
Sent from a cell tower to the XDA server to you.
And if i were you, id redownload the cm7 package again to make sure that it wasnt a bad download and id read some general vibrant info before diving into cm7... if youre running stock recov and have never odined before etc, youre prob not the best candidate for flashing.. just my opinion
Sent from a cell tower to the XDA server to you.
Thank you very much for your reply. I couldn't find a related tool with the Google search string "3e to 2e recovery tool vibrant," but I did find a modified 3e tool at dkszone(*)net/bypass-e-signature-verification-fail-issue-on-samsung-vibrant-android-2.2 . However, this gets stuck at "checking for temporary root."
As for installing drivers, I have installed the Samsung galaxy 64 bit drivers several times now, but I'll give the 32 bit drivers a whirl as well.
I am unable to access the SD card, and don't have a mini SD card reader, so that compounds the problem (damn my lack of cash!).
*Edit* Upon my attempted installation of the 32 bit drivers I get the following (word for word) "Swallowtail has being used. You need to eject device and reboot your computer. Rerun (Japanese or Chinese characters) after reboot your computer." Google returns zero results when I search for this error. I tried rebooting my computer and running it again, but got the same error (even with the phone unplugged from the computer).
*Double Edit* I've been trying to use the AIO Vibrant Toolbox to restore my phone to factory defaults, but I've been having no luck, as it claims my phone is not in USB debugging mode (and obviously I can't change this, as I have no access to the Android OS).
Try this, mate and hopefully you will be up and running soon...
http://forum.xda-developers.com/showthread.php?t=1278683
When I run this the program handshakes, downloads the pit file, then restarts and "...Local and device PIT files don't match and repartition wasn't specified!
Ending session...
Rebooting device...
Device not connected.."
It reboots to the black screen of death and stays there. Perhaps I could select "Flash Bootloader," but the warning of possible permanent damage scares me.
According to the thread...
"REPARTITIONING ISSUE WITH HEIMDALL 1.3.0
Heimdall currently has an issue with repartitioning. 99% of the time you will not need to repartition. Failure to follow these directions can possibly lead to bricking:
Do not flash bootloaders if you see this message:
Code:
Local and device PIT files don't match and repartition wasn't specified!
This message means your partition tables do not match the firmware."
So I guess one of the roots of my problem is that my partition tables do not match the firmware. I have no idea what to do about that.
In this case try another computer if you can, install the right drivers and see odin recognizes your phone. I'm sure it will, for some people sometimes it takes fair few tries for no reason.
Another suggestion, take out sim card and external sd while connecting in download mode. Sometimes that helps.
---------- Post added 29th September 2011 at 12:01 AM ---------- Previous post was 28th September 2011 at 11:43 PM ----------
Here is a recent thread where someone had issue with odin connection.
http://forum.xda-developers.com/showthread.php?t=1225197#16797271
Well, I ran Heim one click on another computer and had the same boot-to-blackscreen process happen.
I was, however, successful at getting Odin to recognize the phone with AIO vibrant toolbox. Odin kept getting stuck at "set pit file" though.
Baby steps...
This is so frustrating. I feel like I'm so close.
How do I get the right PIT file on my phone if ODIN is getting stuck at that step?
Now, after installing the drivers provided with Heimdall-one-click's Zadig, ODIN doesn't recognize the phone.
One step forward, two steps back.
*Edit* Nevermind, got ODIN to recognize it again by uninstalling/reinstalling all related drivers.
Then odin to stock with tthe stock jfd files.. follow the manual, report results
Sent from a cell tower to the XDA server to you.
http://forum.xda-developers.com/showthread.php?t=734475
Use those files and the procedure for ODIN.
As for what caused your problem. You flashed a clockwork recovery for a different phone, possibly the Vibrant (non-MTD) mode? Usually installing Clockwork on the Vibrant only works from ROM Manager app when its running stock JFD. At least for me anyway. Any other ROM it ****s it somehow and I end up in a situation like yours. Not to worry though. Here's a quick install guide after you ODIN the phone to stock.
Put latest nightly of CM7 on the phone memory (not external microSD)
Install clockwork (Easiest way to do this is put the update.zip file I've attached onto the root of your phone memory, not the external microsd card, then reboot into recovery (hold both volume buttons and turn it on) and select Reinstall packages twice. It will then boot you into Clockwork).
Wipe data and cache in clockwork
Install zip from SD card--> pick the latest CM7 nightly.
DONE.
I'd like to use those files, but every single link is broken...
*Edit* Never mind. Found another source. I'll post upon success/failure.
*Edit again* Actually, it doesn't seem like the new link on mediafire has all the files required by the process (OP: http://forum.xda-developers.com/showthread.php?t=734475), and I can't post in that thread (because I'm a new user).
This is the post that uploaded the files: http://forum.xda-developers.com/showpost.php?p=17512889&postcount=615
So I haven't changed a damn thing yet, and all that happens when I try to put the phone in download mode is | Phone----Warning (!) Sign----Computer | screen comes up.
Even when I only plug it into a power outlet...
Flashing the IPhone was easier and more stable than this, years ago. I honestly expected better from Google.
*Edit*
OH MY GOD. Odin is going somewhere! Go, AIO Vibrant Toolbox, Go!
*Edit again*
And it stopped at about 90% with "<ID:0/003> dbdata.rfs
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
"
Well, I tried again and everything finished uploading, and got the green "pass!" for the first time in Odin.
Now my poor little 959v is stuck in a booting loop. The Samsung Vibrant screen comes up, disappears, comes up again, disappears, ad infinitum.
rushmix said:
Well, I tried again and everything finished uploading, and got the green "pass!" for the first time in Odin.
Now my poor little 959v is stuck in a booting loop. The Samsung Vibrant screen comes up, disappears, comes up again, disappears, ad infinitum.
Click to expand...
Click to collapse
959v is the not the vibrant, tis the galaxy s4g, if you odined vibrant files on your 4g then that's why you are in a bootloop
Dear god do I feel stupid. I googled it a while ago just to be sure, and it seemed to say that the V stood for "Vibrant." I guess that would be why I've been having this sneaking suspicion...
Well it's good news for you, mate. Head over to galaxy s 4g
forums and hopefully you will be able to get your phone back.
Hello guys, I have (I think) soft bricked my Galaxy S2.
(Details: UK Phone, Carrier was Orange but now I am running 3 on it, official phone model Galaxy I9100T (NFC support iirc) )
Right I am curious bunny hacking away at the phone from the day I bought it, reading pages after pages on different roms and kernel and everything. Finally I settled on CyanogenMod 9 and then went straight to the CM10.1 release. Today Morning I installed the 23/02/2013 CM10.1 realease and then started browsing the XDA forums on whats new. I came across the Siyah 6.0b kernel release and saw it was compatible with cm10.1, eager and foolish I downloaded the apk without doing any further reading or any instruction, overconfident from all the flashing I have been doing for the past year, flashed the kernel via CWM recovery. Now the phone is stuck in what I assume is a boot loop (again I am pretty noobish).
So What have I tried to fix the soft brick?
I tried to go "restore" an img I had taken a week ago of the system with CWM but the phone would no longer boot into recovery.
So I went ahead and got all the recovery package (I9100TDULP9_I9100THUTLP7_HUT) to reflash my phone with Odin 3.07.
This is where I hit a brick wall and now I am truly lost at what to do, my computer doesn't recognise the phone (Download Mode). I keep getting "there is a problem with this device" error and the Device manager shows an unknown device connected. So I installed the Samsung drivers from the samsung website with no luck. Still getting unknown device error. So I googled for a solution and the only solution that came up was reformat my PC since it could be a problem within the OS, so I went forward and used two other PC and still getting the error. Please Help SOS.
tl;dr: Getting Device not recognised error when I connect phone to the computer via USB cable.
Thanks in advance to all the knights to my rescue
DNoob92 said:
I came across the Siyah 6.0b kernel release and saw it was compatible with cm10.1, eager and foolish I downloaded the apk without doing any further reading or any instruction, overconfident from all the flashing I have been doing for the past year, flashed the kernel via CWM recovery. Now the phone is stuck in what I assume is a boot loop (again I am pretty noobish).
So What have I tried to fix the soft brick?
Click to expand...
Click to collapse
Just go to recovery menu (VOLUP+MENU+POWER) and wipe cache and wipe dalvik. That should fix it.
surplus mplieac
crocodilechris said:
Just go to recovery menu (VOLUP+MENU+POWER) and wipe cache and wipe dalvik. That should fix it.
Click to expand...
Click to collapse
I cannot enter Recovery Mode, the screen just goes blank
EDIT: So the only thing that works atm is
1) The battery charge animation (huge green battery in the middle of the screen) when plugged in.
2) Download/Odin mode (which 3 computer refuse to recognise when connected via a USB cable)
EDIT2: The other thing I forgot to mention was, that I have lost the original SII micro USB cable which was black and now I am using the white micro USB cable I received with my Galaxy Note 2.
You could try uninstalling all Samsung-related drivers/software (Ie: Kies), download the Android Naked Driver or the Android ADB Driver (I wish I could recall where I got it from, but it also came with the driver for the Galaxy SII... Sounds like it might be more of a driver issue than it would be a cable issue..
Borrow and S2 cable.
There are a lot of guys having issues with note's cable.
Try a laptop, and install kies on any other pc you try.
Flash siyah v5 instead of flashing v6.
You can relax, if the only thing you did is flash a kernel then there is nothing wrong with your phone.
Try different cables, try Odin 1.85 (that one always worked for me), try different pc's, reinstall drivers, make sure no kies process is running in the background.
First of all thanks for the replies
I couldn't get the drivers working still (after re-installing, installing kies). But while eating lunch I remembered reading about removing battery and pressing the Power button and it doing something I couldn't quite remember. So I thought to myself it wouldn't hurt trying. Did that and the phone Finally booted in recovery mode, I took a breather of relief and than located my previous backup img and restored the phone.
But now a new problem arose, the phone went into SIM lock as soon as it booted and now I guess I have to fix that
Well thanks guys
Quick question guys is SIM network unlock pin basically same unlocking phone form a carrier?
It's asking for a SIM pin or network code?
Get galaxysim unlock by searching xda (free here, paid at play store).
Sent from the little guy
I have a Samsung Tab 3 (SM-T210R) that started rebooting in the middle of the night. It gets to the main screen and about 10 seconds later reboots. The date is reset to December.
I've tried everything I can find. First the easy stuff such as full charge, different USB cable, different USB port.
I've also tried other things. I do have TWRP installed and tried factory reset that appears to do nothing. I've also tried CWR with factory reset and get errors such as "can't mount /cache/recovery/log" and "can't open an't mount /cache/recovery/log".
I tried to flash a stock ROM with several versions of odin and it fails. At one time it said pit not found so tried to flash that it it fails as well. The last attempt with odin v 3.07 and pit and stock ROM it just hung.
I'm now going to try an different computer.
Any thoughts on what to do next? I've spent at least 10 hours on this and go nothing but frustration.
Thank you
Edit ----
Odin on a older PC appeared to work. The flash ROM and PIT were loaded successfully according to Odin .... BUT, everything appears as it was before. All the old apps show up, the rebooting issue remains.
It would appear that no flashing takes. I also tried to flash newer version of TWRP and CWR and neither took.
mtbgca said:
I have a Samsung Tab 3 (SM-T210R) that started rebooting in the middle of the night. It gets to the main screen and about 10 seconds later reboots. The date is reset to December.
I've tried everything I can find. First the easy stuff such as full charge, different USB cable, different USB port.
I've also tried other things. I do have TWRP installed and tried factory reset that appears to do nothing. I've also tried CWR with factory reset and get errors such as "can't mount /cache/recovery/log" and "can't open an't mount /cache/recovery/log".
I tried to flash a stock ROM with several versions of odin and it fails. At one time it said pit not found so tried to flash that it it fails as well. The last attempt with odin v 3.07 and pit and stock ROM it just hung.
I'm now going to try an different computer.
Any thoughts on what to do next? I've spent at least 10 hours on this and go nothing but frustration.
Thank you
Edit ----
Odin on a older PC appeared to work. The flash ROM and PIT were loaded successfully according to Odin .... BUT, everything appears as it was before. All the old apps show up, the rebooting issue remains.
It would appear that no flashing takes. I also tried to flash newer version of TWRP and CWR and neither took.
Click to expand...
Click to collapse
If Stock ROM flashed with Odin doesn't solve the issue, then you probably have hardware issue.
Take it to a repair shop or Samsung Customer Service.
Nonta72 said:
If Stock ROM flashed with Odin doesn't solve the issue, then you probably have hardware issue.
Take it to a repair shop or Samsung Customer Service.
Click to expand...
Click to collapse
Thanks for the reply, To me it appears to be software. I can use TWRP and communicate via adb. For example, push , shell, sideload from my PC to the tablet. I can copy, move and delete files.
I'm suspecting it's a partition problem but don't know enough to confirm it or fix it.
mtbgca said:
Thanks for the reply, To me it appears to be software. I can use TWRP and communicate via adb. For example, push , shell, sideload from my PC to the tablet. I can copy, move and delete files.
I'm suspecting it's a partition problem but don't know enough to confirm it or fix it.
Click to expand...
Click to collapse
Odin normally formats all the partitions, so, it should have fixed it if it was a partition problem.