[q] please help - Fascinate Q&A, Help & Troubleshooting

Note: I have tried to be as detailed as possible. If anyone can help I would really appreciate it.
I flashed from CM7-Nightly Build 35 (JT Kernel v5) to CM7-Nightly Build 64.
Prior to flashing my phone functioned fully.
Since I flashed:
-I can no longer connect to my PC via USB.
-The phone will not boot past the intial splash screen. (The non animated screen that says Galaxy S and cyanogenmod)
I can use the three button method to boot into clockwork mod v4.0.1.0. I have tried flashing other nightly builds (35 and 57) but this resolves none of the issues.
I cannot connect to Odin.
Could somebody please help me?

your boot looped...You might try heimdall or adb, but I dont know the first thing about it. Your last resort is getting a "jig"(search it on google). This is a common issue that I have seen posted many times. Search thru some of the posts in this section, probably will get a better answer.

i know how to fix bootloops, but the phone wasnt recongnized via usb so i couldnt do any of the usual fixes
turns out it was my laptop, i had to fix my usbports, i connected it to another laptop and was able to connect to odin.
thanks for the reply though!

Related

[Q] odin failed, flash recovery.bin cwm

i was trying to root a phone for someone and after odin completed it said it had failed.
the phone is a telus samsung t959d running froyo.
I followed the instructions from (I would post the url for the link but i am not allowed to.)cyanogenmod's wiki, after it failed I rebooted the phone and it got stuck on the screen in the attached pic. I have tried to boot back into download mode to no avail. From the screen it's stuck on I cannot get any tool to register the device as being present, adb, heimdall, zdiag, etc... I even tried fastboot out of desperation.Before I used odin I tried to get the phone to boot into the bootloader but it only ever went to either recovery or a normal boot and I tried every button press combo I could think of and found and nada.
Even running adb reboot bootloader just made the device boot normally. I think that if I could get it to boot to fastboot usb i could then try fastboot. I am new to rooting devices and have successfully rooted my HTC EVO3D and got s-off and simlock removed for any carrier. So I do know how to follow instructions properly, why flashing the recovery.bin failed I don't know and every fix I seem to find says BOOT TO DOWNLOAD MODE. if I could do that I wouldn't be having this problem lol. Anyway can someone please help me figure this out. Thanks. ANd if you need any further info please let me know. I don't want to have to give my friend my phone due to a software issue.
And YES I did pick PDA not anything else.
machv5 said:
i was trying to root a phone for someone and after odin completed it said it had failed.
the phone is a telus samsung t959d running froyo.
I followed the instructions from (I would post the url for the link but i am not allowed to.)cyanogenmod's wiki, after it failed I rebooted the phone and it got stuck on the screen in the attached pic. I have tried to boot back into download mode to no avail. From the screen it's stuck on I cannot get any tool to register the device as being present, adb, heimdall, zdiag, etc... I even tried fastboot out of desperation.Before I used odin I tried to get the phone to boot into the bootloader but it only ever went to either recovery or a normal boot and I tried every button press combo I could think of and found and nada.
Even running adb reboot bootloader just made the device boot normally. I think that if I could get it to boot to fastboot usb i could then try fastboot. I am new to rooting devices and have successfully rooted my HTC EVO3D and got s-off and simlock removed for any carrier. So I do know how to follow instructions properly, why flashing the recovery.bin failed I don't know and every fix I seem to find says BOOT TO DOWNLOAD MODE. if I could do that I wouldn't be having this problem lol. Anyway can someone please help me figure this out. Thanks. ANd if you need any further info please let me know. I don't want to have to give my friend my phone due to a software issue.
And YES I did pick PDA not anything else.
Click to expand...
Click to collapse
I kept reading other threads and sadly I din't pully the battery first before disconnecting the usb and repartition may have been checked as I see that it does the as default for my version. Also i turned off ODIN as I was hoping a reboot of my computer might help. I will keep trying to find an answer till someone gets back to me. this post may not even show up if I can't do a second post if no one has replied first.
Everyone was a nub at one time wasn't it FUN hahahahahaha sob cry
machv5 said:
I kept reading other threads and sadly I din't pully the battery first before disconnecting the usb and repartition may have been checked as I see that it does the as default for my version. Also i turned off ODIN as I was hoping a reboot of my computer might help. I will keep trying to find an answer till someone gets back to me. this post may not even show up if I can't do a second post if no one has replied first.
Everyone was a nub at one time wasn't it FUN hahahahahaha sob cry
Click to expand...
Click to collapse
I tried a jig and that didn't work. There must be some way of getting the device to give up on completing a task i no longer can give it due to ODIN being shut off.
Why is it that the "how to root/unlocks" never have the "if x fails then do these steps etc..." Had the how to had "pull the battery before disconnecting USB and don't reset or shut off ODIN" I wouldn't be in this mess. I realize that it's user beware but a few important steps like that in case of a fail would go a long way to you guys not shaking your heads. Instead of "silly nub hahahahahaha". No offence but I get that a lot and try to remember that when I teach someone how to use a computer. I am new at phones not at everything.
Further Developments Please can someone help?
I was giving someone a new memory card and they had a Samsung SGH-I896 it has an EB575152VA battery and the one I have the T959D has an EB575152VU battery. I exchanged my battery for hers by accident somehow and when I plugged my phone in it didn't go to the phone triangle computer logo screen it booted to recovery and said it couldn't charge the battery and kept rebooting to recovery. I got my battery back and it booted back to the phone triangle computer logo again. Grrrr....
The other thing I saw while the recovery screen was an error message that said
Code:
E:/data/fota not accessible
(may not be 100% accurate I don't have the battery to check right now but can get it again if need be) anyway I now see that there may be some light at the end of the tunnel. i have the correct stock firmware for the device I tried flashing it while in recovery but the phone kept rebooting before anything got done. My question is how can I get the dang phone to stop asking for Odin and go to recovery so I can flash stock firmware and ROM back to it? As I cannot as far as I know give it what it wants because I reset Odin and nothing seems to see that the phone is connected to the computer. I am going to try the other battery on a full charge to see what that does.
I am new at all this and want to get it fixed. I cannot afford to send it off to a service center and besides that I want to do it myself as I want to become a developer and droid technician. I would gladly donate to anyone but am still trying to get Google to accept my pay-as-you-go credit card and I don't have PayPal either. Which is really frustrating when it comes to giving back. I posted a Q&A on how to without PayPal or CC but as of the last time I checked no one has gotten back to me about it.
The CyanogenMod guide is flat out WRONG. I've tried to change it, but anything I do is reverted in an instant. I also tried to use it to install the ROM only, ended up bricking my phone and it took me hours to unbrick. That's how I became acquainted with XDA.
So, to get this straight:
1. you're using the stock USB cable
2. you remove the battery
3. you hold volume down
4. you plug in the usb cable
5. after a few seconds, you release volume down
6. the screen does not display a yellow triangle with an android
Posted from my Galaxy Tab with CM10
MultipleMonomials said:
The CyanogenMod guide is flat out WRONG. I've tried to change it, but anything I do is reverted in an instant. I also tried to use it to install the ROM only, ended up bricking my phone and it took me hours to unbrick. That's how I became acquainted with XDA.
So, to get this straight:
1. you're using the stock USB cable
2. you remove the battery
3. you hold volume down
4. you plug in the usb cable
5. after a few seconds, you release volume down
6. the screen does not display a yellow triangle with an android
Posted from my Galaxy Tab with CM10
Click to expand...
Click to collapse
That is correct. If you think that my idea below is a bad one or if I downloaded the wrong firmware package please let me know and /or you have a fix that will work? ty
I have though come up with an idea that may work. I am going to charge the "wrong" battery in erm the right phone lol and then use it to trick the device into booting into recovery instead of the cellphone triangle computer (CTC, for want of a better acronym) The I896 battery ends in a V not an ? (sorry can't rem don't have it on me) from the I896 model I think it is, plugging it into USB with the power off sends it to recovery with the "battery cannot be charged " message instead of the CTC screen.
I tried it but the charge in the battery was too low and rebooted. I am hoping that with a full charge (as long as I don't power on the phone first as this will make it go to CTC logo again.
I am hoping that I can install the update.zip that I made by first unzipping the T959UVJFD_firmware.tar I downloaded then unpacked and then repacked into an update.zip as I don't think that it will read the package as a tar file and if it's not called update.zip The recovery is still stock. If I get the phone working I am not going to try unlocking and rooting it again. I will just post two separate adverts one as a carrier locked device and the other one (higher of course to cover buying the unlock from Telus) as carrier unlocked and then I will buy the unlock code if the blah blah you get the drift. sorry for rambling on.
oh and I can't rem if I said this or not, In recovery it "E:/data/fota not accessible" I don't know what that means yet I have been busy with other things and haven't looked it up yet.
Since you can get into at least some version of recovery, your bootloader is intact and you should be able to unbrick it. You ought to be able to get into download mode using a download jig. You can get one on ebay for a few bucks or you can make one yourself. There's a guide floating around here somewhere that lets you make one from a microusb cable.
Posted from my Galaxy Tab with CM10

[Q] Soft-Brick help!

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

please help

Before anyone says anything, sorry for another s2 brick post but I've searched like mad! Downloaded like mad n stayed up till 2 hours before work to sort this n nothing so far.
I rooted my s2 successfully and installed a working kernel. For some reason any ROM o tried failed at flashing, so I went back intoodin n installed a new kernel but my laptop froze n now I'm bricked. I've tried reinstalling the kernel that worked n no hope and tried maybe 10 different kernels n nothing worked. I read on a post to try installing new firmware, some work n some fail, some just go into boot loop n some come up firmware problem use kies. I've tried combinations of kernels n firmware but its not worked, sometimes the phone loads up to boot logo then just goes off.
I'm trying to download some files now but my stock ROM download keeps stopping, I've got the bootloader n kernel just the ROM is playing up.
The one click unbrick doesn't see my phone as mass storage so won't work. Kies won't connect. I can get into recovery and download
Anyone have files that will definitely work or any advice.....phone is s2 i9100 on o2 uk
1) Download the stock rom using another internet connection (I.E an internet cafe. Because flashing one is the only way you're fixing this).
2) There has been dozens of 'Odin won't work/PC & phone won't recognise each other' threads on here over the past month. In many of them, someone here has listed the troubleshooting steps you go thru when this happens. Find them. And try those steps. All of them. With multiple PC's if you need to. And keep trying them until it works.
Edit - Use a more descriptive title than 'Please help'. Many people here will automatically not even bother to read your thread by default, which may deny you the chance to fix your phone.

[Q] Galaxy S2 I-777 Booting Issue No Recovery

I have looked around at some of the boot loop thread for an answer and I haven't see one for my exact issue. Before the error I was running Shostock3 and wanted to update to the Dirty Unicorns rom. My CWM wasn't the correct version so I flashed a new kernel that was recommended to me so I could run this rom. After successfully flashing the kernel I restarted my phone, but doing so places me in a stuck boot loop.
I only have access to Download mode and when I go into it and try to get odin to detect it, it fails to recognize my phone. I made sure the S2 mobile drivers were installed. I used several different cables and usb ports, I even tried a different computer to see if it would work with no success. I wanted to ask the brilliant people here if there was anything that could be done or would this be a lost cause?
If possible I would love to save my phone but I'm not sure what to try next. If this is somehow answered in another thread please don't stone me to death. I asked a couple of users and it was recommended that I asked for further help here. Thank you for taking the time to help me.
I also noticed this is in the wrong phone area and I'm sorry about that. Can this be move dto the I-777 forums

Sprint Note 5 stuck in twrp?

Please help. I've searched the forum far and wide for a solution. I also hope I'm posting this in the right area.
I was looking to root my Sprint Galaxy Note 5 SM-N920P(6.0.1). I found what I believe to be the correct twrp for my device. After I successfully installed twrp, I booted into it (twrp), and did nothing else. After that, I tried to boot my phone into the regular system but it never gets passed the initial splash screen (that says Samsung). It just shows me that screen over and over again. I can get into Download mode and twrp but nothing else. And to make things worse, my laptop(windows 7)doesn't recognize the device anymore. I've tried different cables, made sure I have all drivers but still nothing. I get the chime on my laptop when I hook it up (that a new device has been attached). But I can't access the storage and Odin doesn't recognize it.
Please help. Any and all suggestions will greatly be appreciated.
Mod Edit links removed
Please give us new LINK

Categories

Resources