Hello all.
Today, I tried to root my TELUS Samsung Galaxy S Fascinate by using Odin and CWM3-Voodoo-blue.tar.md5. I received a "FAIL!" message, so I pressed Start again, which yielded nothing. So, I removed the USB cord from the phone and tried to boot it up. Nothing happened. I tried to use cwm-recovery-ALL.tar, but, again, I received a "FAIL!" message, and ended up with nothing.
It seems, at the moment, the phone can boot up in download mode (Vol Up + Vol Down + Power). However, the screen appears filled with randomly coloured pixels, and nothing else works on the phone. Is there a way to recover my phone from this state?
I'm going to sleep right now, so I won't be able to reply right away, but I'll check replies as soon as possible.
EDIT: Now, it seems as if the screen isn't booting up at all. However, I can still see the download screen with Vol Up+Vol Down. I don't think the phone was rooted at all, so I'm thinking of sending it back to Samsung so they can fix it. Is there a way to check if a phone is fully rooted or not?
Related
Hi All,
So, I tried to flash Cyanogen mod last night using the instructions here: http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide. I was coming from a BIONIX ROM that flashed fine.
Anyways, the phone went into a reboot loop in the recovery screen and I foolishly just held the power button until it stopped. When I turned it back on it was broken. That is, now all it does is display the white Vibrant logo in the middle of the screen with the smaller Samsung logo below it. If I hold the power button for about 8 seconds the screen goes black for about 2 seconds and then comes right back up to where it was. I can't seem to even turn the phone off any more. It just stays on that screen permanently unless I hold the power button, in which case the screen is off for 2 out of every 10 seconds. Yanking the battery of course turns it off, but putting it back in immediately returns it to the state I've described.
I've scoured these forums and tried every button press + battery state + cable state + SD card/SIM state combo suggested, but the phone won't go to download or recovery mode. I found one thread describing the exact same problem. The OP said he'd try a jig and then disappeared without any further updates. I'm going to try to get my friend to make a jig using one of these sets of instructions
http://forum.xda-developers.com/showthread.php?t=819551
http://factoidz.com/how-to-unbrick-your-samsung-vibrant-galaxy-s/
but until then my questions is: does anyone have any experience with this problem (can't even turn the phone off)? If so, do you have any recommendations? Did a Jig work?
keep trying to get to download mode, pull battery, plug usb in to computer and to the phone, while holding both volume up and volume down pop in the battery. People have tried hundreds of times with it not working and then all of a sudden *bam* download mode.
So... my friend made me a jig and it works in that I can see the shoveling droid indicating download mode. However Heimdall/Odin won't recognize my phone. Heimdall's zadig utility won't locate the phone either, even with the cable plugged in. I'm, once again, stumped.
Just an update; I've tried Odin on three different computers, two Windows 7 (64 bit) and a Mac (with Heimdall). None of them seem to recognize the phone. Device manager on the Windows 7 machine does not update when I plug the phone in (in Download mode via the jig or not) and I can't find anything about Samsung in it anywhere. However I have installed the Samsung drivers; a few different sets I've found around the forums. I've also tried a couple utilities like the Vibrant toolbox and one click unbrick. Nothing seems to have any effect. I was so hopeful when the jig worked and got me to download mode, but now it's seeming I'm actually bricked. Has anyone seen a phone that could get to download mode but still be bricked? Oh, and I checked the cable using a friend's phone; her Mac recognized her phone using the cable. Haven't tried her phone on my Window's machines though.
Once again, any help is more than appreciated.
Have you tried to see if adb is working? If it does then try adb reboot recovery? If it works there is a file I can post for you later (is in my pc) that can restore your sbl.bin and fix your download mode problems.
Thanks for your help everyone, the problem was apparently resolved by a new cable; which is strange because the old one works for data transfers... just not for flashing apaprently. :S
So, I wanted to update the Rom, so tried to go into recovery mode. Pushed the volume down button instead of up, so got into download mode. Pushed the volume down button to cancel. Then pushed the right combination, but nothing past the Galaxy S2 logo with the warning triangle happened.
Tried to reboot a couple of times, but now the phone is completely dead.
Everytime I turn it on the Galaxy S2 logo appear, and when it dissappear the phone seems to be dead. However if I look closely, the screen is not turned off, it it just black (but turned on), and every 5 seconds or so I can see it "blinking", but it blinks "black" if you could say that, you won't notice it if you don't look careful, or you are in a dark room.
If you triple click the home button you normally "invert" the colours on the screen, and this also works in this case. Instead of it flashing with an almost unnoticable black, it is now white and every 5 seconds the screen turns off very briefly, but then the screen is white again.
To get it to stop doing this I need to remove battery. If I push and hold the power button the phone just restarts with the galaxy s2 logo, and then does the same again.
When I connect the phone to a charger or to a PC (while it's powered down), the battery logo appears for a couple of seconds, and then it enters this "blinking" screen thing again.
When connected to a PC it does not appear as a drive - however it seems like windows detects it, it installs the GT-9100 drivers. Samsung Kies can't connect, it just keeps trying to connect forever, without coming with an error, but it's not connecting.
Hard reset is not working in any of the described ways, whatever I do, if its to get it into recovery mode, download mode, or just trying to turn the damn phone on, it just do the blinking thing.
Is this some sort of a boot loop from hell!!?
sounds strange, can you still get it in download mode without issues?
If you can i would advice to flash back to stock(!!)
or you could try to flash a cf-root to see if thats gets you into recovery format system, data, cache, dalvik and flash the new rom.
but im not sure if that would work, a clean install from stock would be better i believe,
as to why it went this way i have no idea!
Good luck!
If you can get in download mode, flash a stock rom with odin and that should do the trick
yes!
Well, that was odd, thought I had tried that several times, but yes now at least I can get it into download.
Now I used ODIN to flash a file (CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5.tar) that I had laying on my PC from back when I was originally rooting my phone. ODIN gave me a "Pass" reply and I got the phone into a bootloader. I quickly wiped everything I could, and at the moment I'm seeing if I can boot the phone normally.
Thanks!!
Well my rom is f***** it won't boot, but atleast I can get it into recovery mode.
Have just installed cyanogen 9 stable + gapps, it is now booting up!
Luckily I backed my phone up with Titanium backup just a couple of hours ago!!!
it's working!
Well that saved my ass. I was so close to throwing my phone out of the window and going online to order a S3...
Now I'm setting up my phone - nice, wanted to try Cyanogen 9 anyway.
Cool.. Always be patient.... Rather than thinking of purchasin a new phone when these kind of situations occur. Keep a usb jig with you
Sent from my GT-I9100G using xda premium
How the problem occurred
So a year or two ago I bought a Jiayu G4A/T/Whatever they're calling it and safely got it here. I've used the stock ROM for a bit but I wanted to get rid of the bloatware that was still on it, so I eventually ended up with a properly rooted phone with a ROM from Jiayu.es (Everything worked, have ClockworkMod as recovery, accessible via Mobileuncle Tools), which was essentially a stock Kitkat rom made to work for the phone. Now I got sick of the ROM and recently saw the new EMUI version on Huawei's P8 Lite, so I figured I'd look around for a tailored ROM running that, and ended up at "jiayu-emui-3-0-stable" from Needrom.
What I did
1. I downloaded a ROM from Needrom with identifier "jiayu-emui-3-0-stable" (I can't post external links)
2. Backed up my important files following a guide from androidcentral titled "[Guide] How to Backup and Restore Apps and Data when installing new ROMs" that I can't link,and did a full backup using CWM
3. Placed the ZIP on my internal SD card, went into recovery, wiped data/cache (not dalvik, since it wasn't described in the instructions, I think this might be a probable cause) and installed the new ROM from ZIP
4. Rebooted the phone and now it's stuck in the boot loop I mentioned.
What the problem is
Bootloops aren't that much of a problem usually, except this one is... I can't get into recovery mode. From there on it'd be cake, since I made the right preparations, but I can't get into it. While connected to my PC it keeps powering on, showing a splash screen from Jiayu.es briefly (which shouldn't be present anymore) and powering off after 10 seconds, only to come back to the splash screen.
What I've tried
I've unplugged it, removed the battery, waited to get a full power cycle and tried to hold my buttons in these combinations: [power button + volume up], [power button + volume down] - but neither work. It just keeps going with the boot loop. I can succesfully power it down, and when I plug it in from there it shows the low battery image. At the moment of seeing that I thought I could connect to it using ADB / Fastboot, but no luck there either. It keeps saying no devices found, and with fastboot it keeps on <waiting for device>.
My questions
What exactly can I do if there is no way for me to get into recovery mode? Are there any alternatives? How can I get my device to be recognized by ADB? Is that even possible? Why is this bootloop any different from others?
Update from the massive Q&A thread:
ZipAddict said:
Is it booting up on its own too after being off? This happened to wifes phone and it turned out the power button was stuck. I took a pencil and hit the power button with the eraser a few times and it worked then. Her case mustve dislogded it. I will keep my fingers crossed for u. If not send me a private message and i will look for an answer tomorrow and get back with u
Click to expand...
Click to collapse
Thank you for the reply!
Yes, it does. I took the battery out and let it lay disassembled for a night, after which I cleaned it a little and re-inserted the battery. With the case back on, nothing happened, so the power button wasn't stuck for sure. When I powered it back on with the power button (no USB attached) it showed the emblem for ~8 seconds and powered off. It then buzzes to show it's powered on again and up comes the splash screen again. Could it be that the ROM was just a rebooting falsehood? Why would it disallow me getting into recovery mode? I really hope there is something that can still force the device into recovery mode / interact with it somehow while in this state.
Oh, I also tried to see if the volume down button was broken but all the contacts seem intact, plus, they worked an hour before I started switching roms.
Hello and thank you for anyone bothering to read this.
I got a CAT S50 and was experiencing a bit of instability lately.
I've run LTE_S0201121.0_S50_0.023.00 without a hitch for a while, then it decided to crash several applications, from google play to any other app open.
That's when I decided to do a factory reset and see if it would help. Performed the rest without a hitch, but the errors kept coming back. At one point, the screen went black. I knew the phone was on because the backlit was working. I hard-reseted it (hold the power button for 30 seconds or more) and rebooted. The phone froze on the CAT splash logo screen and that's when I hard-reset it again. But when I tried to turn it on, the phone simply refused to work. No vibrate, sounds or anything. It's dead.
When I plug it on the computer's USB, the PC makes a sound as if it detected the device, but when I go to the device manager, I get this QHSUSB_BULK with the yellow exclamation mark
I want to know if it is possible to unbrick this phone and if so, if there is a tutorial or if someone can direct me to the correct procedure. I looked everywhere for the ftf file for this phone to attempt this with flashtool, but I simply can't find it.
ANY help of any form is greatly appreciated.
Sadly I had the same thing happen to me, just a black screen. It decided to delete recovery mode or I just cant get to it.
Power Off the Phone,
While pressing Press Vol Down + Cam Button insert a Powersource -- hold down Vol Down + Cam
Recoverymenu should start
Then flash the original rom via ADB Sideload or SD Card.
btw. i have flashed the LTE_S0201121.0_S50_0.023.00 but i want test older ROMs!
can anyone link or upload an older ROM ?
Guy i have the same issue, can you please help me
I got the same problem I search lots place but still nothing then normal update rom anyone can help?
I had recently installed evolution x, everything worked fine, but i stupidly hit the update button today and now im stuck on the twrp splash screen...
When it turns on i get the galaxy s9 plus splash screen then the twrp 3.5.2_9-0 splash screen.
I am not able to turn the phone off with the power button, i have to hold both volume down and power to restart it.
I have also left the phone overnight just incase it needed a bit of time but no luck, still just stuck on the twrp splash screen.
I have tried many hardware button combinations with no luck. I am unable to see the device on adb or fastboot, and i am unable to see the device when plugged in to install drivers for odin.
How do i fix this? (To be clear i dont care about the data on the phone, it is backed up but the phone is currently a paperweight in this state)
Edit [SOLVED]:
After weeks of googling i was able to find one thread for a different phone with a slightly different problem that said letting the phone run out of battery let them boot into download mode and it worked, as soon as i plugged in the phone and held the button combination i was able to get into download mode and install a later twrp version.
Hopefully other people can find this solution faster than i did
I am still looking for information on this if anyone has any.
I have also had to let the phone run out of battery and am hoping that doesnt make things worse.