I have a Samsung Vibrant Galaxy S. I rooted it and flashed it with froyo 2.2. I followed the sticky and everything went smoothly. I backed everything up with ROM manager and Titanium Backup.
The problem is that I tried to restore to stock JI6 without sitting in front of the computer.( I know, a careless , careless mistake) Lesson learned...
Everything was working smoothly for a couple of days, but then the the software started lagging and freezing so I decided to restore the rom by using the restore feature in Rom Manager. When I selected the ROM to restore, the phone rebooted into recovery mode (not in Rom Manager recovery mode). I then selected reinstall packages and an installation process ran. When the phone was done installing the package the phone rebooted and is now stuck on the samsung vibrant boot screen.
There was no update.zip in the root directory when this is was selected.
From reading threads I dont believe that the phone is bricked since it shows the boot screen.
Is there any way to fix this without creating a jig?
Will a jig even fix this?
Please help I have read threads for hours and no solution has worked yet.
I have installed eclipse with android sdk and adt and tried to put the phone in download mode but I cannot adb to the device since the phone can not be put into developer mode.
can you get into download mode by taking out the battery plug in the usb to a computer hold the volume keys while putting the battery back in or turn the phone off then hold the volume keys while plugging in the usb to a computer sometimes that works too
egc+voodoo jl1
Also I think theres info on a jig in the team whisky website
egc+voodoo jl1
The second method worked thanks a lot.
Related
Listen i'm somewhat new so forgive me if i posted in the wrong place.
Just hear me out please.
Ok heres a little s/a. I have a samsung vibrant, last night i flashed my vibrant which was on a rooted vibrant9 rom. To bionix 1.9.1 w/ jacs oc kernal and the voodoo lagfix. Before flashing to the bionix i switched the boot logo and .wav file to one i perfered, i also did the same for the shutdown logo. Now, per the instructions for installing bionix 1.9.1 i took a nandroid backup of my phone on vibrant9 before performing the flash. After i did i flashed using clockwork. Everything went fine, the phone flashed, rebooted and was working great. However i rebooted the phone and relized that the shutdown screen wasnt working as it should because i forgot to include the shutdown.cfg thats required. What i did was took the bionix.zip off my sd card went into it and added the .cfg file i needed. I added it back to the sd card and figured i'd just reflash and all would be fine. Not so lucky however, i tried to reflash using clockwork (which took me to the regular recovery menu you would get to holding down the volume buttons and power) and it failed giving me an error which said "error on line 80". Relizing that the instruction said that if you had the voodoo lagfix you should disable it, i decided to do a factory wipe of all data (thinking that would definitly disable voodoo) after the factory wipe i attempted to flash bionix 1.9.1 again with no luck. After the last attempt i decided to just restore using the nandroid backup of vibrant9 i had taken earlier, the phone went through the restore process with waht appeared to be no problems. After it finished i rebooted from the recovery menu then bammmm. The phone is stuck in a boot loop. Its not a normal boot loop though the initial samsung logo will pop up for a sec then the phone screen will show what looks like tv static for a sec, it just keeps repeating this. To get it to stop i have to pull the battery. Ive tried booting into recovery by holding the volume buttons and the power button, but all that happens is the phone starts into the above mentioned bootloop. As a note whenever i plug the phone up via usb to my computer a grey battery screen pops up but it dosent charge it just sits there, and if i unplug the usb it goes right back into the bootloop. Also my computer will not recognize the phone so using odin seems like a lost cause. I read in a forum for this phone just a bit earlier that its nearly impossible to brick this phone. Have i done the impossible?
Well it sounds like you have hardware locked phone. Also you cannot do a nand restore w/ voodoo enable. That's your problem. There are threads on xda about recovering hardware lock phones. You need to search. If you can get into download mode, you need to flash eugene373's "Froyo that does not brick". Also, once you get phone working, isuggest you keep a disable-lagfix zip on your internal sd.
Sent from my SGH-T959 using Tapatalk
Great Success
Ok, ok after what seems like a million tries i finally got my vibrant working. After finally getting my vibrant into download mode (by removing the battery, putting the battery back into the phone, holding down both volume buttons and plugging in the phone via usb) i used odin to try and flash back to the factory rom. The flash worked except for an error i noticed when the phone was kicked into factory recovery mode to format itself. There i noticed that at the point when all user data was supposed to be wiped it would have a failure to wipe data. After the flash completed with this error i was able to get past the boot loop. At this point my phone would finish the boot sequence but after the samsung s disappeared the screen would just stay black. However, when ever i pushed any of the soft keys on the front they would light up. So what i did was followed the instructions in the above post and used odin to flash eugenes froyo rom that wont brick. Again the flash would complete but when the phone was kciked into factory recovery mode i got an error and it wouldnt complete it would just hang. So what i did next was use odin to again flash the factory rom and to my surprise it worked. So my vibrant is now restored to its full glory. I owe everything to the patrons of this community. Thanks all.
Alright, I was having problems with my CyanogenMod, and I went to restart my phone because it kept force closing all my apps (including system processes) and it got stuck on the Vibrant screen and never started up.
I went to Nandroid to restore my backup I made before CM7, and it must be corrupted, because it refused to restore, so I said to hell with it and decided to start from scratch.
Long story short, I ended up flashing the wrong ROM by accident because I got confused between the Samsung Vibrant and the Samsung Galaxy S 4G, and somehow I got my phone stuck at an AT&T World Phone logo, and it won't do anything else. I've tried entering recovery AND download mode, and neither will work. Also, when I plug my phone into the USB port, the charging indicator gets stuck at the very beginning, showing a pinwheel and a greyed out battery.
I ordered a USB jig, hoping this would help send my phone into DL mode, but I'm still open to any ideas anyone has until then. I haven't had a phone for a couple days and its killing me!
itsjuztin said:
Alright, I was having problems with my CyanogenMod, and I went to restart my phone because it kept force closing all my apps (including system processes) and it got stuck on the Vibrant screen and never started up.
I went to Nandroid to restore my backup I made before CM7, and it must be corrupted, because it refused to restore, so I said to hell with it and decided to start from scratch.
Long story short, I ended up flashing the wrong ROM by accident because I got confused between the Samsung Vibrant and the Samsung Galaxy S 4G, and somehow I got my phone stuck at an AT&T World Phone logo, and it won't do anything else. I've tried entering recovery AND download mode, and neither will work. Also, when I plug my phone into the USB port, the charging indicator gets stuck at the very beginning, showing a pinwheel and a greyed out battery.
I ordered a USB jig, hoping this would help send my phone into DL mode, but I'm still open to any ideas anyone has until then. I haven't had a phone for a couple days and its killing me!
Click to expand...
Click to collapse
Here's some tips:
1. NEVER restore non-cm7 nandroid backups on a cm7 based rom.
2. Flash stock JFD with repartitioning checked to go back to stock.
3. Reflash vibrant bootloaders. You may have some captivate bootloaders or a mismatched param.lfs that's causing the AT&T bootsplash. It could be one or the other and mismatching captivate and vibrant bootloaders or params could lead to a brick so just flash the vibrant bootloaders since it contains both bootloaders and param.lfs.
4. DL mode depends on the bootloaders you run.
Froyo bootloaders-------------
1. Volume up and down with USB inserted and with battery disconnected
2. Insert battery without letting go of buttons
Gingerbread bootloaders-------
1. hold power and volume up with the battery inserted and with the phone powered off
2. connect USB to pc when booted into DL mode.
P.S. Can you take a picture of the front and the back of the phone so I can identify the kind of phone you are using at this moment?
The name you are using for the device you have is kinda confusing me.
I installed the latest nightly build (cm_galaxys2_full-88.zip) on my phone yesterday night and restored the all the apps through Titanium Backup. Everything was working fine until this morning I tried to create a backup using CWM recovery in Rom Manager. The phone shut down and has since been stuck on the initial boot screen (one with the Samasung galaxy S2 logo). It does not boot into recovery mode using the button combinations. I can only get it into download mode but Odin does not recognize it as I thing i forgot to enable USB debugging.
I have tried removing the battery and rebooting and also tried to access it through odin a number of times. But nothing seems to work.
What am I missing here ?
This might help?
mjondj said:
I cannot boot into recovery, but I can boot into download. However, odin is no longer recognizing my GS2 when I plug it into my PC.
The bootloop began when I was attempting to flash the cyanogen7 with the google apps.
I read every post in this thread, and have seen a number of people who cant boot into recovery, but can boot to download. I haven't seen anyone else mention that their phone is no longer recognized by odin on their pc.
Please help.
edit:
Perhaps odin doesn't see my phone because I didn't have USB debugging enabled? if that's the case, what can I do?
------------------------------------------------------------------------------------------------------------------
solved:
heimdall overwrites a driver and stops odin from seeing your phone. i attempted to remove it, unsuccesfully. but loaded odin onto a different computer (that had never seen heimdall).
i booted into download, connected to 2nd pc w/ odin, and ran CF-Root-SGS2_XW_NEE_KI8-v4.3-CWM4.tar (search forum) in PDA. this made my phone bootable again.
Click to expand...
Click to collapse
also check that you dont have kies running on your pc
icecreampop3 said:
This might help?
also check that you dont have kies running on your pc
Click to expand...
Click to collapse
Thanks. Although that did not do what I expected it to (due to some license issues), but it got me into recovery mode from where I could restore a Nandroid backup. Am back on RevolutionROM for now. Looks like CyanogenMod will have to wait for me.
I experienced the very same thing for the first time today. Had checkrom revolution and ran rom manager to backup and am now unable to boot into recovery/download. Will try to hook it to odin then
Hi
I used the factory reset function on my tab a couple days ago to delete all apps and such and upon reboot it was stuck at the slowly flashing Samsung logo and would proceed no further. I left it for a good hour and a half in that state before I tried hard resetting it but no dice. I've had it do this before when I first rooted it, but unlike that time it doesn't replay the whole boot animation, just the logo part at the end of the animation. I managed to get it in clockwork mod or bootloader whatever that function is and cleared all the caches and did a reboot recovery (i believe thats what it was called) but upon reboot it did the same exact thing. So after that I gave up and went to bed, but the next day when I went back at it again it wouldn't even turn on. After messing around with the power button and volume button trying to get into recovery mode it finally turned on but went to the battery screen with no other actions. I've tried several times to get it into recovery mode but it either wont turn on or it just goes to the battery screen. I have it plugged into my pc at the moment and apparently it is in recovery mode or something because Odin recognizes it. Says [0:COM3] and the box is yellow, but the screen never turns on though when holding the power button and volume button while it's plugged into a pc, the pc recognizes something plugged into the USB slot. My pc is only recognizing it as a modem and will do nothing else with it.
I have the Starburst rom and the overclocked kernel installed and would like to either revert it to stock rom or perhaps the AOKP rom, milestone 6. Is there any way to do this if I can't boot it into a state where I can access the SD card on my pc? All the guides I've found always require I put files on the sd card to flash in clockwork recovery mod. Thanks for any assistance
Edit: Solved it myself, feel free to delete this post. Thanks!
Hi all,
I need some help please.
I tried to root my sons galaxy young S6310N using a video on you tube
However at the 4.41 point I didnt have the yes- root option.
I themn rebooted and it went back into CWM recovery. v6.0.3.2
It's been stuck in this for 2 days now, I have searched everywhere for a solution but I'm lost now. I have information overload I think.
I have tried to install drivers through Kies but it won't recognise my phone in CWM recovery or in download mode.
I have tried to install a custom rom via sd card, it seems to work but reboots into CWM again.
I fear I may have made a mess of it now by messing around with things I know nothing about. I panicked really.
The phone was running jelly bean and is only a week old.
I can get adb but not sure how to use it properly.
Could someone please help?
Thanks in advance
sorted it myself
Hi, just in case anyone was interested I managed to sort this.
I put phone into download mode (holding vol - & menu & power) then pressed up at logo screen to enter download mode.
My pc then installed drivers automatically (something I had been struggling with in CWM recovery mode)
I then installed stock rom recovery.tar.md5 file using odin and the phone rebooted as normal.
I have given up trying to root it now, I may learn properly before attempting again, or may leave it.
Search for your device first before making a thread..!!
driller66 said:
Hi, just in case anyone was interested I managed to sort this.
I put phone into download mode (holding vol - & menu & power) then pressed up at logo screen to enter download mode.
My pc then installed drivers automatically (something I had been struggling with in CWM recovery mode)
I then installed stock rom recovery.tar.md5 file using odin and the phone rebooted as normal.
I have given up trying to root it now, I may learn properly before attempting again, or may leave it.
Click to expand...
Click to collapse
Good..but always use recovery for ur phone only..or make it for ur phone..
And do any changes in stock ROM after creating a BACKUP of the same..
ROOTING is not a difficult now-a-days but overcoming from the loss of time and data after BRICKING is so painful.
If you are not friendly with the commands and codes then use a software for that or follow up the WRITTEN guide..or use FARMAROOT app.
Head to thread...Thanks Mr. Bin4ry for this awesome method:
Rooting almost every phone
Enjoy..!!