Hello I recently got my refurbished Captivate from AT&T and it came running 2.1 Android. First thing I did with it was go and root it by downloading the update.zip to it, and that went all fine and well.
Next thing I did was get ROM Manager and installed Clockwork Recovery Mod, then went ahead and made a backup of my ROM. So from here I was getting ready to get myself ready for Cyanogen Mod 7, and grabbed the Clockwork Mod version with speedmod and installed that through the Clockwork Recovery.
After I did this the boot screen changed on my phone and would lock up at the Galaxy S SGH-1897 Samsung screen, which had replaced the 3g one by AT&T. The phone will just hang at this bootscreen for infinite amount of time, any suggestions on how to help?
I'd like to point out that I currently have no USB cable for this phone, I did not receive a micro USB with it as it is a refurbished product and do not happen to have any laying around. I do however have a micro SD card, in which Clockwork doesn't seem to support this.
I come to you asking for help to resolve said issue, I can no longer use my phone as a result. I've tried restoring my backup but the same replaced boot logo appears and refuses to actually start up the phone.
The 3 zips that I can access on the internal SD are
-the root.zip
-clockworkmod
-clockworkmod with SpeedMod
Any ideas?
First of all, you will definitely need a micro USB cable. You need to flash back to stock at the moment. Don't worry though, if it's still showing the boot screen your phone "should" be fine.
Second of all, for CM7 you need to follow the EXACT instructions to install CM7 (you can risk bricking your phone with CM7, unlike any other usual ROMs). Do you know, and understand all of the steps involved?
Sorry, but what were you doing? You need odin to install cm7 & without a cord you were never going to succeed.
As mentioned above you need a cord, and need to reread the instructions
CM7
Related
I rooted my nook yesterday using the autonooter 3.0 which i guess is not official, but anyways, I'm just not happy with it and I would like to get my Nook back to stock. However, when I try to do 8 failed boots, it won't cancel the boot when I press the power button. I mean I am jamming it down and it still goes through the boot.
Unfortunately, I also have not figured out how to get adb working. I followed the instructions on nookDevs and adb devices kept showing my SN as 11223344556677. Mind you it was showing up fine in device manager as Android composite ADB device. I figured heck with it I'll just root it. Now its not showing up at all.
So it seems like I'm hosed as far as resetting my nook. Any way out of this?
install clockwork recovery and use that to flash the stock rom.
ok well I installed ROM manager and then flashed CWR to my SD card. I then made a backup of my current rom in case I somehow decided to go back to it. But after selecting reboot system now in CWR it keeps booting into CWR. How do i get out of it?
Is the SD card flashed to CWR still in there? Is like a pc set to boot from the cd drive before hdd, no matter what, if theres a sd card in it, it will try to boot from it first..
You can remove the sd card when in CWR just remove it and then select reboot
Sent from one of those missing Droids
Yeah, I took it out. But for some reason it didnt recognize it wasnt in there. so it was pretty much boot cycling just it was going into CWR. I just flashed the stock 1.0.1 ROM so it's working now, just have to reregister the nook.
I haven't touched my Rogers G1 rom, it is as stock as they come. One day the battery died, so I plugged the phone to charge and also tried to start it up.
My problem started after that.
I will try to restart the phone and it'll get stuck on boot screen - where it says HTC or sometimes even just the Rogers screen.
Only solution is to take battery out, do hard reset.
I've searched the forums but everybody else asks regarding modded roms and not stock.
Any idea how I could resolve this issue without flashing new roms? Or is that my only way out?
Thanks.
Did you apply Rogers mandatory 911 update that was released about a year ago? You can check by booting into fastboot mode (hold the camera button while powering it on). If your radio version is 3.22.26.17 you have the update. Rogers locked down fastboot in this latest update and the only way to root it is through the ROM. If you don't have this update I can walk you though the steps to root your phone though fastboot.
Just checked and it does have the update.
Should I just go ahead and flash new roms?
I keep having the same issue as before.
With the latest update Rogers locked down fastboot so it is useless. So, I don't believe that there is any way to flash a new ROM without first booting into your existing ROM.
Sorry but I'm inexperienced with flashing roms...
If I can't flash by the fastboot method, I can still flash by rooting the phone, correct?
JiggyNS said:
Sorry but I'm inexperienced with flashing roms...
If I can't flash by the fastboot method, I can still flash by rooting the phone, correct?
Click to expand...
Click to collapse
I'm not completely sure, but usually you need to be able to get into the rom to root. Maybe there is another way.
6 hours later and i got nowhere...
I rooted phone, flashed new cyanogen rom, setup amon ra's recovery but I didn't do new radio since my current is one of the newer ones.
The booting goes nowhere as soon as the rogers logo shows at the beginning of boot up.
Would a new radio help? Could that be the issue?
edit:
The phone rebooted properly and now I have a working fone!
Wait, how did you root the phone without getting into the ROM?
beav_35 said:
Wait, how did you root the phone without getting into the ROM?
Click to expand...
Click to collapse
I used the Androot method, copied onto sd card, launched file via file manager app on phone and it rooted the phone. This is how I remember anyways - I fiddled with the phone for good part of the afternoon so my memory is all over the place with the specifics.
I used this site for rooting.
I thought you said in the op that you couldn't boot into the ROM (got stuck on boot screen). So, what was the problem in the first place? (or how did you fix the ROM?)
Sorry I guess I wasn't clear enough in op.
The only way I could get to use the phone was to do a hard reset and let the phone boot up from there, however if I ever wanted to turn the phone off or restart the phone it would get stuck on the next boot up.
I was able to flash the rom by constantly hard reseting the phone every time I needed to put files onto the memory card.
First:
I'm running 1.2.0, stock + root
Stock Kernel + OC
Ok, I know that's a lame post title, but I couldn't think of a better one. My microSD crapped out on me earlier today and I, for the life of me, can't remember how I had it set up (yes, I have copy/paste backups on my PC). Read on, I'll explain.
Before, I could keep my flashable microSD in all the Nook all the time and boot, reboot at will without being forced into CWM. Shortly after my microSD crapped out on me, my Nook got stuck in a bootloop. This happened, I assume, because in my insomnia-dazed brain, I copy/pasted my microSD backup without making it flashable and then updated CWM via Rom Manager when it told me there was an update.
Anyway, I grabbed a CWM image from here and flashed it up, got everything going again, but now my system boots directly into CWM with my microSD inserted in the Nook. What the heck do I need to flash to take it back the way it used to be? Pardon my lack of common sense. It's been a busy day and I've gotten about 8 hours of sleep over the past 3 days.
No ideas at all?
N/M, got it all worked out....ya worthless bastards.
I had recently rooted the Samsung Captivate. And was trying to install cyanogen mod onto it. I installed it and everything went through ok... until the phone went to the AT&T screen, had like a fuzzy noise like screen coming up and went black.. then there was a voice saying something about data or something. It just keeps repeating itself over and over and over and over again. My phone is able to charge though to say the least. Is there a fix for this.
teenphresh said:
I had recently rooted the Samsung Captivate. And was trying to install cyanogen mod onto it. I installed it and everything went through ok... until the phone went to the AT&T screen, had like a fuzzy noise like screen coming up and went black.. then there was a voice saying something about data or something. It just keeps repeating itself over and over and over and over again. My phone is able to charge though to say the least. Is there a fix for this.
Click to expand...
Click to collapse
I had a bootloop after flashing an AT&T bootloader. Since I had a ROM on my SD card already, I just booted to recovery and re-flashed a rom.
Try to get into recovery, if not - download mode and odin to stock.
Sounds like the phone is trying to do a voodoo lagfix conversion. I would flash a stock ROM. Then take the stuff you want to keep off the phone. Leave the folder named voodoo. Then, reformat the internal sd card. Put your stuff back on the phone. Then flash whatever you want, per the directions from the thread of whatever ROM you want.
mrhaley30705 said:
Sounds like the phone is trying to do a voodoo lagfix conversion. I would flash a stock ROM. Then take the stuff you want to keep off the phone. Leave the folder named voodoo. Then, reformat the internal sd card. Put your stuff back on the phone. Then flash whatever you want, per the directions from the thread of whatever ROM you want.
Click to expand...
Click to collapse
I agree with haley. The only time the phone speaks to you when booting up would be if it's trying to do a voodoo conversion. Which does not go well with cm7. Flash stock via odin, then root and get cwm, and flash cm7 through cwm. Nothing should go wrong then
I have had a ATT captivate for almost 2 years now. It falls in the IMEI range specified by ATT. But it wasn't really a problem until very recently.
It got much worse about 3 weeks ago when the phone kept constantly rebooting. It would load the OS, begin media scanning, once that concluded, it would immediately reboot (almost every 20 seconds). Only way to stop the reboot cycle is to take out the battery. No new apps were installed, no system changes were made when this happened.
I am able to get the phone's menu which allows me to wipe and I am able to get the phone into download mode.
I have read (4) of this article regarding sleepdeath and all corresponding articles referenced.
This is what I did...
1) Performed hard reset, cleared storage. This eliminated all third party apps, returned the phone to stock (I think), but the phone is still rebooting.
2) Attempted to install a brand new rom (CM) via CWM = Problem got much worse. Still rebooting but this time, after the ATT logo appears, the screen changes to static (noise) and reboots. Followed instructions and diles from here.
3) Since the phone became useless, I hunted around to return it to stock again and used this. The phone now boots up into the OS, but now it's back to rebooting.
I repeated steps 2 and 3 just to make sure I didn't miss a step, but same problem.
I have 2 goals:
1) Get the phone working, if at all possible!
2) If that's not possible, recover the 300 pictures that are on the device.
My challenge is that since the phone keeps rebooting every 20 seconds, by the time it connects to my PC via USB as external storage, it reboots! This ofcourse is also preventing me from loading a ROM directly on to the SD card.
So if anyone can help me to do the following:
1) Point me in the right direction to how I can keep the phone in a certain mode or setting (download mode doesn't work) where I can transfer files, recover my pics, and perhaps load a custom ROM?
2) Next steps?? Am I even on the right track? Since the stock rom keeps the phone rebooting, will a custom ROM solve the problem (have not been able to get a conclusive answer on this on the threads referring to sleep death (which this is an exaggerated version of) or is the phone a lost cause?
I know I can call ATT and try to haggle a replacement (since the phone is out of warranty), the only benefit being they don't renew my contract, and I don't have to upgrade.
Any help or guidance is much appreciated.
Wow, bummer
Well i don't know if you can mount the sd card in stock recovery (never used it) but if you can't then you could flash one of the stock one click roms with cwm recovery from this thread.... http://forum.xda-developers.com/showthread.php?t=1300843
In cwm recovery there is an option to mount sd while connected to pc so you can backup your stuff.
For the reboots, could it be your power button? Mine is acting up, and often seems to cause reboots. There are threads about fixing that. Idk just a thought.
Hope that helped a bit
Sent from phone with app
Like the previous post says, maybe try a custom recovery, go to mounts and storage, and mount USB storage. While you're at it, try flashing a compatible ROM through that recovery i.e. GB rom if its a GB kernel with CWM recovery or ICS rom if its an ICS recovery.
Did you try to do a dump of SD card data with adb?
Sent from my GT-I9000 using xda premium
The static issue is because you flashed a gingerbread kernel but you don't have gingerbread bootloaders. You can fix this by flashing an AT&T stock one click with bootloaders.
Once there, you can flash corn kernel and use recovery to mount the sd card.
Or I guess you could flash a froyo kernel.. there's a number of ways to do this.
Sent from a jelly bean