I downloaded cyanogen from the Rom manager and it.goes threw. The process but once.it.gets to The splash screen just stops and keep repeating itself left it like thatvfor 3 hrs before having to restore then tried again same thing any ideas why its doing that
Try a battery pull. If that doesnt work, dont use Rom Manager. Just download the zip file from the CM7 thread on here, place it on the sd card, wipe and flash.
Related
this was my first time installing a rom i downloaded bootstrap and rom manager made backup downloaded the blackout rom and installed zip from sd card and when i reboot my phone it takes like 3mins to start up and when it gets to home screen can see anything just a whole bunch of app stopped unexpectedly im i skipping a step plaza let me know.
Which ever Tom you are installing, make sure to read the instructions thoroughly. Also, when installing a ROM, its always recommended that you format system. Which ROM are you trying to install?
N.B. I have S-Off (but not full radio), an overclocking module loaded and clockwork recovery.
My phone has been working absolutely fine the last few days overclocked to 1.3. Today I downloaded megajump (a game) and played it for a bit before the screen went blank, so I did a battery pull reset. Since then I have been unable to boot fully, it makes the HTC sound and gets stuck at the HTC screen.
Occasionally when I reboot it it starts up clockwork recovery but I'm not sure what to do with this and how to initiate this recovery stage to start with.
I know the answers to this problem are in the forum somewhere but I'm struggling to find where to start. It seems an odd issue as it has been working fine (including switching on and off etc).
N.B. Shortly before this problem I updated ROM manager from the market
Thanks in advance
gloscherrybomb said:
N.B. I have S-Off (but not full radio), an overclocking module loaded and clockwork recovery.
My phone has been working absolutely fine the last few days overclocked to 1.3. Today I downloaded megajump (a game) and played it for a bit before the screen went blank, so I did a battery pull reset. Since then I have been unable to boot fully, it makes the HTC sound and gets stuck at the HTC screen.
Occasionally when I reboot it it starts up clockwork recovery but I'm not sure what to do with this and how to initiate this recovery stage to start with.
I know the answers to this problem are in the forum somewhere but I'm struggling to find where to start. It seems an odd issue as it has been working fine (including switching on and off etc).
N.B. Shortly before this problem I updated ROM manager from the market
Thanks in advance
Click to expand...
Click to collapse
Hook your phone up to the comp with it powered off, type in "adb logcat" into your computer's Terminal, and display the results.
gloscherrybomb said:
N.B. I have S-Off (but not full radio), an overclocking module loaded and clockwork recovery.
My phone has been working absolutely fine the last few days overclocked to 1.3. Today I downloaded megajump (a game) and played it for a bit before the screen went blank, so I did a battery pull reset. Since then I have been unable to boot fully, it makes the HTC sound and gets stuck at the HTC screen.
Occasionally when I reboot it it starts up clockwork recovery but I'm not sure what to do with this and how to initiate this recovery stage to start with.
I know the answers to this problem are in the forum somewhere but I'm struggling to find where to start. It seems an odd issue as it has been working fine (including switching on and off etc).
N.B. Shortly before this problem I updated ROM manager from the market
Thanks in advance
Click to expand...
Click to collapse
Ok so once it boots into Clockwork recovery you have a couple of options, first did you ever make a back up of any of your roms? If yes , scroll down to backup and restore and select it, next choose Restore, It will give you a list of any roms you have backup before, choose one and it will restore to one of those backup roms, option two if you have a complete rom zip file on your sd card you can choose install zip from SD card, choose zip from SD card, apply and your good, if you dont have a rom zip on your SDcard you can put one there by selecting mounts and storage in Clockwork recovery, Mount USB storage, and put a rom on the root of you SDcard, then go back and run my option two that I just gave you, If for some reason you cant mount the sdcard, shut the phone down, remove the sdcard, use a card reader to install a zip to the root of the sdcard and then follow option two.
Remember before you flash anything wipe data/ and cache.
Panic over, having reset it numerous times and left it for well over 30 mins, it has now managed to load up properly.
Very strange!
Mods feel free to delete this topic if you like...
Read a few other loop posts, but none were for the evo and/or helped much. I've been running CyanogenMod (newest) with little problems except for one which is why I wanted to try a few others.
Using ROM manager, I did try to d/l myn's as I have used it in the past, and after the download, reboot, the install kept showing the android package and a triangle with exclamation point. When completed, it rebooted and just kept looping through the CyanogenMod bootloader screen (so I know the myn's didn't get installed). I have 3 backups, the one from this morning and 2 older ones.
I did a reboot / recovery with this mornings backup and had the same results (note I didn't wipe, just backed up). I did let it sit a good 15 minutes of the loader, black screen, loader, etc.
I then restarted again and selected the older backup (which was using fresh rom). Got my loader, and everything did start (thankfully) and I could make a few calls. The problem(s) I have are;
I don't want fresh which is why I switched. I just tried using ROM manager to select myn's, even selected the WIPE DATA and backup with the results. The installer goes 2 quick to read, but I just see that triangle with ! as it tries to flash the new myn's rom.
Ideas / suggestions are appreciated.
I've heard that ROM manager might not clear the Dalvik cache very well. This is what I'd try:
1) Download and install AMON RA 2.2.1 that I've attached. Its labeled as PC36IMG so your phone will automatically recognize it.
2) Download a check sum program for your computer, you should verify the MD5 value to this one below. You need to make sure you didn't have any download issues and this file isn't corrupt, otherwise you've got a new set of problems.
26eadae1e206784d0bb9426f24f4303d
3) Place this file on your SD card root directory. Also put Warm2.2 ROM on the SD card as well.
4) With your phone off, hold down the volume down button and turn it on.
5) You should go into the bootloader screen. The phone will automatically scan for the PC36IMG file. Agree to install it.
6) After this is installed, remove this PC36IMG file off your SD card just to make things less confusing.
6) With the phone off, go into the bootloader screen again. This time select "Recovery" after it scans.
7) You should now be in AMON_RA 2.2.1 recovery. Navigate to Wipe. For a completely clean install, wipe data, cache, Dalvik, and SD:EXT.
8) Then navigate to the Flash from SD card, find your Warm2.2 ROM and install. When complete, reboot the phone. Things should work now.
Hope this helps.
@coiledwire - thanks for such a great detailed reply. I did exactly what you suggested and sure enough worked like a charm.
Although Fresh was ok (and working), you don't go through all the trouble to go 90% ... thanks again...
Sweet! Glad to hear things are resolved.
In the future, always wipe the cache and dalvik before flashing. That goes for kernels, mods, as well as ROMs (wipe the data also when doing these). Some even suggest wiping these 3 times just to make sure.
Top 3 sources of problems: corrupted download, didn't wipe, and incompatible mods. IMHO.
Yea, well normally I would use ROM manager (free) and didn't delete the data which this time I did from the recovery mode which was probably a good part.
So at least now it's the newest radio, ROM and everything I want (except the vanilla lock screen) which when I tried to install from SD I received a nice error talking about the app was written with some old things, so that's my next project!
Thanks again ... great info!
I thought it might help if I shared how I installed Cyanogenmod 7.1, highlighting the issues I overcame.
Rooting the phone using Odin and insecure ROM was easy.
I tried to use the RomManager app to flash ClockworkModRecovery. I rebooted into ClockworkModRecovery and then attempted to install the Cyanogenmod 7.1 zip I had downloaded and copied to the SDCard. I got errors like "Invalid whole-file signature"
I then used Odin to flash GT-I9100_ClockworkMod-Recovery_4.0.0.2.tar. There is a guide that mentions using this, although I did not actually find a guide at the time.
I rebooted into ClockworkModRecovery and then I deleted the cache and Dalvik cache, next a Factory reset. Then I attempted to install the Cyanogenmod 7.1 zip. This time, it seemed to install far too quickly. I rebooted and sure enough it failed to boot.
When I rebooted into ClockworkModRecovery I found it had been upgraded from 4.0.0.2 to 5.2.6 or something. I attempted to install the Cyanogenmod 7.1 zip again. A proper installation bar appeared. I also installed the Google apps zip.
I rebooted. Finally Cyanogenmod loaded normally.
I used Titaniumbackup to restore everything. Cyanogenmod then became unstable with crashes in Android core components.
I decided to revert to stock rom to save my contacts etc. and tried to install it using Odin. It would not boot. (I tried several times)
I reflashed Cyanogenmod again and found a way to extract my contacts from the Kies backup file to get them on to the phone. I lost some but never mind.
I had problems with the market - it would not download some of my apps (saved in my Google profile). I kept deleting the market cache over and over and gradually it allowed me to (re)install my apps.
I had problems with the phone shutting down when showing 66% power, so I recalibrated the battery which seemed to resolve it.
I've now replaced the ADW launcher with Zeam, dialler with DiallerOne, sms messager with Go SMS Pro, keyboard with Go Keyboard, browser with Dolphin Browser HD. Installed AdAway ad blocker, Droidtools, MyPhoneExplorer client. I turned off the lock screen as I just want to use the old pattern unlock one.
Finally, Cyanogenmod rules. But it has to rule since it looks like I cannot go back to stock roms with Odin any more.
Why cant u go back?
I installed cyanogen today
(a must is to back up your original data - so if you make a mistake, you can revert back to it)
i rooted with a insecure kernal, but this did not have cwm 'which lead to hours of wasted time', so i re flashed with a CF-Root kernal
(this did the trick with that verify whole life error)
(AFTER ROOT)
1. enter cwm (by holding the volume up, home key + ON key) make sure phone is off
2.wipe data/factory reset
3.wipe cache partition
install (/cyanogen/whatever) zip (internal) sd card
(that really stuffed me up, i was stuck in boot loop because i was using my external sd card) *make sure to save the file to the root of your internal sd card beforehand*
reboot
4. get depressed that your phone interface looks cheap, your camera doesnt work properly, you wonder where your external sd card files are, your favourite videos dont play etc, lol
I tried a few times reflashing stock Samsung ROM with Odin, but phone got stuck in booting.
Flashing a replacement kernel eg. Siyahkernel seems to be ok.
For_itembine said:
4. get depressed that your phone interface looks cheap, your camera doesnt work properly, you wonder where your external sd card files are, your favourite videos dont play etc, lol
Click to expand...
Click to collapse
I didn't have these issues. Camera is fine for me, sd card works alright. Don't know about videos - haven't tried. As for interface, you can change the launcher to what you like. I use Zeam as it uses minimal memory.
You didn't follow the instructions. Could have saved you some time.
Instructions: http://forum.xda-developers.com/showthread.php?t=1176411
It says to install my cwm kernel: http://forum.xda-developers.com/showthread.php?t=1118693
It also says to flash twice.
And another rule is to not use backups made on a stock rom.
samsung android is no real android. ;-)
If only I'd done the Nandroid backup of the Samsung ROM.
Never mind. I like Cyanogenmod much better than the Samsung firmware anyway.
For_itembine said:
I installed cyanogen today
(a must is to back up your original data - so if you make a mistake, you can revert back to it)
i rooted with a insecure kernal, but this did not have cwm 'which lead to hours of wasted time', so i re flashed with a CF-Root kernal
(this did the trick with that verify whole life error)
(AFTER ROOT)
1. enter cwm (by holding the volume up, home key + ON key) make sure phone is off
2.wipe data/factory reset
3.wipe cache partition
install (/cyanogen/whatever) zip (internal) sd card
(that really stuffed me up, i was stuck in boot loop because i was using my external sd card) *make sure to save the file to the root of your internal sd card beforehand*
reboot
4. get depressed that your phone interface looks cheap, your camera doesnt work properly, you wonder where your external sd card files are, your favourite videos dont play etc, lol
Click to expand...
Click to collapse
So actually where am I supposed to copy the files, in the external sd or internal sd ??
Because on all tutorials and HowTo's it just says copy to sd card
ehknaton said:
So actually where am I supposed to copy the files, in the external sd or internal sd ??
Because on all tutorials and HowTo's it just says copy to sd card
Click to expand...
Click to collapse
SD card is the SD card not the one that the phone might not have as its an extra for some .
jje
the reason why stockflashed firmware wont boot!!!!
the reason that the firmware that you flashed wont boot and goes into a bootloop is because you have to press upp button home button and power button so u can get into the stockCWM... do a factory reset and clear cashe from there and you will boot fine in stock rom just wait 2-4 minutes ! ut takes some time i know !
Hey guys.
I've had one of the latest nightly versions of CyanogenMod 10 on my phone. I tried to install the rEmIxRoM just to see how it looks and if I'd like it, but I didn't like it. So I decided to install the latest Slim Bean version out there. But when I flashed the .zip to install, the screen became dark and then the Semaphore logo came up, and nothing happened for a few minutes. I tried the 3-button combo to get back to the Clockwork Mod, but it didn't work also. Now my phone is stuck on the Semaphore logo every time I try to turn it on, with no option to do anything.
What am I supposed to do? Please guide me...
It's too easy.
just flash 3 files (Stock GB ROM) with Odin and then your phone will boot and ok.
I'm sorry but I don't really understand... I don't know much about these things.
I don't know how to work with Odin, I don't even have it on my PC, I usually just install roms via recovery. Is there a guide that can tell me exactly what to do? Because it sounds easy but I don't even know where to get these 3 files from... :angel:
By the way I can't get my phone to CWM or download mode. Both just end up showing me a weird battery graphic (it doesn't mean that the battery is empty)
Technetium37 said:
I'm sorry but I don't really understand... I don't know much about these things.
Click to expand...
Click to collapse
Assuming you are here to learn, read carefully and digest it before attempting
B]Need to know what is your phone model [/B]. Check Here to chose your forum/Guide by Version of your phone or you will have more problems by using wrong solutions due to different versions of Galaxy S
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
This alone could have solved your CWM problems, if not try a solution from My Android Solutions
To get basic idea about Odin try watching these http://forum.xda-developers.com/showthread.php?t=810130 and http://www.youtube.com/watch?v=KyAIUOYufrU and http://www.youtube.com/watch?v=33I-aNCypVM
If anything you are not sure of use the google search will give you many more to watch and learn
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu>Settings>Applications>Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
Thanks for the help.
I couldn't get into download mode or CWM at first, but after a lot of tries the phone managed to boot. I just flashed the Slim Bean zips and all is ok for now. I actually saved your post on my pc, in case I have problems in the future. :good:
Tips before Flashing:-
...
Backup your EFS Folder to PC or Ext SD card
Click to expand...
Click to collapse
I'm not stuck in the same situation (back on 2.3.6 JW8 again) but the above mentioned point is not so easy.
I tried 4.0.4 / 4.1.1 myself (SlimROMs of CM9 / CM10) and it seems to run fine but I lost my IMEI every time.
Even with root access you're not able to make a full backup (e.g. with ES File Explorer, Ghost Commander, Total Commander). The only solution I fould was to make a sector disk dump (dd) via terminal which is way to much effort for a quick flash.
Or are there some other tricks for this?
Hayabusa_XDA said:
Or are there some other tricks for this?
Click to expand...
Click to collapse
yes, read efs problems and solutions in My Android Solutions
Everything is working for me now, except for one problem: some apps can't be downloaded from the Google Play. I keep getting the "App could not be downloaded due to an error (942)". When I try to access them through the PC browser, it's saying that the app is incompatible with my I9000, even though I used it on my previous roms. The big question is why does this happen only with some apps, but with other apps there's no such problem?