I popped darky ROM on my wifes galaxy I9000T about 6 months ago and she has been very happy with it, but for the last month each time she reboots it goes to recovery then reboots fine. Today however it goes to recovery then tries to load then reboots then goes back to recovery. I'm happy to load a new ROM on but Cyanogen and others say to "Install the ROM from internal sdcard using ClockworkMod Recovery" I can't get to the internal sdcard as the bugger wont boot. Any suggestions would be great?
nevermind I factory reset and wiped cache and has come back to life for the moment, I think my wife installs too many apps
Related
I've tried repeatedly to install CM7.2 and keep getting stuck on a blank screen. I'll see a "CyanogenMod" then "loading..." right below that. Then it goes blank and nothing ever happens after that.
Some background info. I've had CM7 installed on this in the past without problems. Months ago I went back to a rooted stock. Then yesterday I decided to try CM9 alpha. That installed perfectly. But it was too slow, so I decided to try CM7.2.
I used the same CWM 1GB boot SD, copied "encore_CM72-MiRaGe-02012012.zip" along with the Gingerbread Gapps and CWM. Installed in the same order and wipe data/factory reset.
So I got stuck on that blank screen after the CyanogenMod loading... message. I then decided restore to stock. Installed the 1.01 stock image. It also wouldn't boot up, but I powered it on and off 8 times and it did a factory reinstall and then it booted up normally.
Once back at a factory fresh system. I powered it off and tried installing CM7.2 again. Unfortunately I'm having the same problem again. Ugh, why won't it load now.
Hang on... I might be in the process of making a newb mistake. MD5 didn't match on my SD card, probably the ROM.ZIP is corrupted. Trying again with a good copy.
That was it. It's working now. Please disregard my idiot on the Internet moment. Thank you.
You always figure it out five minutes after you finally give up and post for help/venting.
Been there.
Before I startת I tried to find this problem also search on Google and here but could not find any information about this problem.
This night I did not put the device to a charger because he had already 90% battery, so I left it disconnected,in the morning I got up I saw the phone is turn off, I tried to turn the phone light up and the ATT screen turn on,
I went and when I came back after 10 minutes I saw that the phone is still stuck on the "Galaxy S" screen.
I removed battery, changed, and it's still stuck.
I'm running version CM7.1,
The phone can get into the recovery menu.
Can anyone help me?
I do not understand in the android system and I don't have any backups of my pictuers...
Any chance to save the phone?
update: I search for a solution, and found on the CWM the option of "Mount USB storage" and I copied my pictures to my computer...
so now my new question is how can I get the phone to turn on again? only format and install new rom?
I can use CM7.2 zip file and install via the recovery menu?
you can go to cwmr and can do a data wipe which will uninstall all your apps and data but will not touch your sdcards
You won't lose your pictures on the sd card. If you are still stuck, try wiping dalvik cache from recovery
Sent from my ICS Samsung Captivate
I have a similar problem. Like eidoll32, I did not plug in my cappy and when I went to turn it on the next day, I was only able to get a boot loop at the AT&T screen. Currently, I cannot get into recovery, but only download mode.
I originally rooted the phone with the Galaxy_One_Click_Root tool, and installed CyanogenMod 7.1 for the captivate, when CM7.2 went to RC1, I flashed that from CWM, doing a full wipe. Later I wanted to try ICS, so I flashed AOKP - captivatemtd - M5 b30, doing a full wipe (twice).
That's where I was when this happened, and where I am now.
I finally upgraded my wife's Verizon Tab to the 7/25/12 CM9 nightly four days ago. In that time, she's experienced two random sleep-of-death instances, from which I succesfully recovered. Today, however, she put her Tab down after using it for a bit, went back to it later, and it was off again, and very warm. She plugged it in and tried to re-start it, but it would hang on the CM9 splash screen forever.
I tried to re-start it and got the same results.
Then I tried booting into CWM Recovery to reboot from there, but got the same results.
I tried to fix permissions in CWM, but CWM became unresponsive.
I rebooted into CWM again and tried to restore a nandroid, but it failed since /data couldn't be mounted.
I then tried to flash the 7/28 nightly, but it couldn't mount /data either.
I used Heimdall to reflash Recovery and kernel (5.0.2.7 if I remember correctly) I had used to upgrade to CM9, and then tried to flash the 7/28 CM9 again. This time, after a very quick flash sequence, and a very long time (20 minutes) on the CM9 splash screen, it finally moved on to the boot animation, and eventually booted...right into a screen that said "Encryption Unsuccesful."
Per that screen's instructions, I elected to do a factory reset and reboot. After a very long time, the Tab rebooted to the same error screen.
Bottom line is, I've since learned the "Encryption Unsuccesful" bug is an ICS one (especially with unofficial ROMs), and it does a number on your internal and external data partitions/SD card. I was lucky in that the SD card didn't get wiped, but my Tab is unrecoverable. My latest attempt is to load a rooted stock Verizon ROM/recovery/kernel using Heimdall, but after almost an hour, I've just made it to the "Verizon Wireless" boot animation. Most threads I've read on this issue end up in dead-ends, and I couldn't find a single one that pertained to the Original Galaxy Tab, much less Verizon's.
Does anyone have any ideas as to what else I can do?
Hi,
My SGS GT-I9000, running cm-11-20140504-SNAPSHOT-M6-galaxysmtd ran out of battery over night (thats already happend many times before ), but this time it can boot up only into CWM (v6.0.4.8).
I am running this ROM since the release date and i have ran out of the battery many times in this period of time, so i don't think it is a problem of new ROM, kernel, etc.
Next thing is that I cannot access sdcard0, it doesn't let me install zip or mount sdcard0.
Little details: the phone gets into CWM even if i try to charge it, without pressing any button. For that few moments before it go into CWM it doesn't show the battery status animation.
Edit: factory reset do nothing
Edit: odin didn't work
Thanks for any help.
I recently updated my gt-p1000 to cm10, by following a youtube tutorial. After Two days of use , i encountered a bootloop.
i tried factory reset and wiped dalvk cache, cache but it still ddnt work. i then put ICS, (CM9) but still ddnt work.It still keeps restarting.
then i tried to install the latest kernel, but after i did this im stuck on the cyanogenmod logo, it just keeps rotating. I then used odin and down graded to the stock rom, and im suprised that the restarting still ddnt stop. It just keeps restrating every 20-30mins or sumtimes just after u turn it on, (10sec). Pls help Me, i've dont everything told on the internet ( wiped cache, dalvk cache, factory reset, formated sys) EVERYTHING!
Hi,
It sounds a lot like a stuck power button issue to me. Especially if it behaves the same after returning to stock.
But for other opinions and ideas, I will have your thread moved to your device section.
Good luck!
ted my galaxy tab p1000 2.2 froyo with z4mod.
Then initially I installed cwm with ROM manager for galaxy tab T because there wasn't any specific model of cwm for p1000.
But but when I switched off and booted recovery, stock recovery always came......I could access cwm only through the ROM manager ("boot into recovery")....and that too if i choose any function it starts to load and when I press home twice it says "replacing stock with cwm" and that goes on forever...
So I installed cwm with Odin as I couldn't access functions like "install" in cwm without going into the loading phase.....but as the process in Odin finished, my tab started to boot and at "galaxy", the sceen got all pixalated and it went till " samsung " and the whole process looped........ Help!
I actually was trying to install lollipop 5.0.2...