Hi,
I've been trying to upgrade my Hero from cyanogenmod 6.1 RC1 for a while now. Every new rom I try to install just hangs the phone at the initial HTC screen. I've tried wiping every partition I can possibly wipe before I install the new ROM's but no go. The only way to get my phone back is to install 6.1 RC1 again.
Not sure what to do. I've tried different memory cards too.
Any suggestions? Maybe my phone just doesn't like the new 7.X roms?
Try reflashing your recovery. You might want to check out Ra1.7. Or you could try this after you reflash your recovery
Backup all of your data to your pc. Then format your sd threw your pc and restore factory defaults. Then format it again threw your recovery with no partitions no swap just all fat/system. Then redownload the rom of your choice+gapps. Then perform a fully wipe as in data,cache davilk-cache. Then flash the rom then the gspps and see if the rom will reboot.
Locked & Loaded
yeah you should definitely use the wipe function in the recovery menu before you flash the new rom,
if that doesn't help, restore to the original and start over, maybe use different recovery, i use the the amonra, it's been working well
Thanks, I will give it another go in a day or two and let you know how it goes.
Related
can someone help me? I want to change my theme from dark hero cyano to something else. do i have to wipe my phone at the boot or no need to. Just update the new one into it?
quanzt said:
can someone help me? I want to change my theme from dark hero cyano to something else. do i have to wipe my phone at the boot or no need to. Just update the new one into it?
Click to expand...
Click to collapse
you should be able to just flash the theme, but if it acts weird or doesn't look like the theme is supposed to or boot loops, then reflash your rom, then flash the theme. you shouldn't have to wipe, but if all else fails then you will.
You shouldn't have to... I switched between a few trying to settle on one a while ago (3.5 era cyanogen) and never had to wipe.
another question. if i wanna switch the rom from one to another. what should i do? wipe and flash it? i got partition SD ext and linux swap.
it depends on what rom you are wanting to flash. if it is a hero then you will have to flash and most likely wipe your ext2/3/4 partition. if it is another ADP based rom then you might not have to to wipe, but if it doesn't work properly then you will have to wipe.
Hey... just make a backup and try it.
If you go from a non-Hero to a Hero or vice-versa then you may as well wipe just to make sure. Clean out your ext partition as well. (Make a backup of course.)
Then go ahead and try a upgrade install. If it begins to act strange (such as compass, or touchscreen, etc) then go ahead and wipe and try again. You may also want to try to fastboot flash your data.img file from your nandroid backup. That sometimes works.
In the event that you wipe, install and can't get it to boot and want to go back to your old rom, just fastboot flash your .img files. Then just restore your backups to your ext partition (if you had to delete everything) and voila! Just like it never happened (after you restore your ext backup if you had to delete everything).
Phone: CDMA Hero
ROM: Freshhh2.0d
Recovery Image: 1.5.2
Well the story begins:
Last week installed Freshh2.0d rom everything worked perfect...... until I tried to screw with the lock screen (tried to install vanilla lock screen and for some reason it messed the rom soon I assign password to lock screen!!) To even realize it was the lock screen I had to reboot and flash the rom several times (maybe like 8-10!!!) then finally it started working!!!
But after the last flash, I started having force close issues with several core apps, like touch screen, google apps etc..... so this morning decided to reflash the rom one last time and see if it fixes the issues.... but I feel like I have done more than just that..... here is what I have done....
1. Re-flashed Freshhh2.0d rom, after reboot got stuck at "htc" screen that comes up after all the animations
2. I wiped or did a factory reset and flashed again..... same result
3. Wiped again and this time I wanted to download the rom again and while downloading rom, I stumbled up on new recovery image 1.6.2
4. I applied new recovery image with wiped or factory reset phone, rebooted in recovery and flashed rom
5. Again stuck under htc screen after all animations....
6. Went back to recovery image 1.5.2 and flashed rom
7. After all this the net result is still same...... stuck in htc screen....... not booting the phone!!!!
Can somebody point me to the right direction???? I am even thinking about trying a different rom and see if that comes up!!!
Ok, first go back to the 1.6.2 recovery.
Next, wipe the following:
Factory Reset
Dalvik Cache
SD: EXT (if you were using apps2sd this will nuke your apps, so be sure you have a backup).
Then reflash Fresh 2.0d (or whatever ROM you want to use).
If you still have problems I recommend doing the RUU to return it to stock and start over.
Same with me I have been trying to flash fresh 20d. On my first reboot it always gets stuck on HTC screen. I'm comming from Fresh 2.0b2. Don't know what else to try. Though I can do Nandroid and get back to Fresh2.0b2
smw6180 said:
Ok, first go back to the 1.6.2 recovery.
Next, wipe the following:
Factory Reset
Dalvik Cache
SD: EXT (if you were using apps2sd this will nuke your apps, so be sure you have a backup).
Then reflash Fresh 2.0d (or whatever ROM you want to use).
If you still have problems I recommend doing the RUU to return it to stock and start over.
Click to expand...
Click to collapse
I do not have back up of my apps and I am using apps2sd, is there a way at least I can get a list of apps in my sd? I tried to do cd /data/app under shell and it won't let me ......
bigd1231 said:
Same with me I have been trying to flash fresh 20d. On my first reboot it always gets stuck on HTC screen. I'm comming from Fresh 2.0b2. Don't know what else to try. Though I can do Nandroid and get back to Fresh2.0b2
Click to expand...
Click to collapse
When in doubt, always wipe before going to a new rom. When NOT in doubt, wipe anyhow.
Sure you can go to a new rom sometimes without a wipe...but 80% of the time you do much better going clean.
Also, how long have you waited on the HTC screen? I've seen that take upwards of 10 minutes.
I have waited as much as an hour. Also, I did do a Factory reset many times. I just don't know what else to try.
if none of that works. just use the right ruu for your device.
bigd1231 said:
I have waited as much as an hour. Also, I did do a Factory reset many times. I just don't know what else to try.
Click to expand...
Click to collapse
Did you wipe dalvik and SD: ext as well?
You should wipe everything there's an option for.
NO I actually didn't do that I'm going to try right now and post back THANK YOU Didn't wipe SD: ext
bigd1231 said:
NO I actually didn't do that I'm going to try right now and post back THANK YOU Didn't wipe SD: ext
Click to expand...
Click to collapse
Wipe all 3 again, then reflash.
Factory
Dalvik
SD: ext
Then let us know how it goes.
Your problems are caused by apps2sd... plain and simple. Fresh 2.0d's release notes tell you that you are going to have to wipe your sd:ext (as well as data wipe). That is because there were several versions of apps2sd floating around before and they aren't all compatible.
http://geekfor.me/new-release/fresh-20d/
Secondly make sure you are using ext3 and not ext2.
http://geekfor.me/faq/apps2sd/
Yes It worked Finally. I wiped all Three and reflashed it and waited 15 mins and it worked.
yes it worked. I wiped all 3 and worked
smw6180 said:
Wipe all 3 again, then reflash.
Factory
Dalvik
SD: ext
Then let us know how it goes.
Click to expand...
Click to collapse
Great! that did the trick!!!
Flipz, there is one shortcoming with 2.0d (not sure if its something inherent to the original rom itself!) When I use my corporate email on my Hero it forces me to assign password and when I do that and lock my screen phone stops responding there after. This happens when I am using vanilla screen lock update.... I can't unlock for anything.... any idea how to fix this?
Glad to hear you're both up and running.
Hi, I have installed seeARMS ROM and followed his instuction. I have kept the JL2 modem and speedmod kernell (I was already on speedmod). I have tried 2 methods to install. The seeARMS.UGJL2.v0.4.zip with the seearms file and the CWM.
Both install went OK and I even had a congratulations screen. The problem is when the phone reboot it stays on the boot animation and get stuck there. I have tried 2 different boot animation and the same happen.
I have no problem to restore my data since I had backup but I would like to have the seearms ROM. Any idea?
Also a side question, can we get the new CK1 modem with seearms?
Richard
Have you been wiping your phone before flashing the rom? I have been having issues like you describe only when i flashed a rom w/o wiping.
(In CWM Recovery: wipe data/factory reset, wipe cache and advanced -> wipe dalvik cache)
No. I did not wipe. I am not interested in the new ROM if it mean wiping. I made a test by downloading a boot animation app. I trying 2 different boot animation and had the same result. The boot animation play with no sound but I have a vibration during boot and then nothing. Eventually it go back to the animation, vibrate and this repeat until I restore the backup.
I am wondering if tehre is something special about the Bell Canada boot animation?
Can I use the seearms without any boot animation folder?
I don't think it's a problem about the boot ani in particular.
I am not very familiar with the rom, since i have another device. In the seearms rom thread the dev mentioned two versions of the rom, one that requires wiping and one that does not.
So i guess it could be working out to flash the latter w/o wiping. But in my expirience those things rarely work out that way.
There might be incompabilities with the config data left behind by the rom installed before, or other possible issues.
Only way to be sure that those things aren't blocking anything is to wipe the phone and do a clean flash.
Personally i always do it that way. And if i like the rom, and choose to use it, it is always possible to get back all the apps and settings back with titanium backup and/or syncing them back.
But as always before wiping, if you choose to do so, please be sure to have a full nandroid backup, in case you want to go back, or something goes wrong.
I will try the wipe version
What rom were u on before seearms
Sent from my GT-I9000 using XDA Premium App
I was still on stock (froyo 2.2). Actually still on it today
You were right. The wipe version worked fine. I have now to decide to keep it or not...lol
ROM is awasome was worth well the trouble.
Glad it worked out for you - have fun with the rom
Sent from my Desire Z
Hi all,
So after I flash a new ROM (MIUI MGv2/RC8vC/MGv1) I always hang at the Galaxy S GT-I9000 screen - the first boot screen.
I am wondering what this means? is it a corrupt file, something wrong with my internal sdcard, ROM not installed properly?
Please help,
Thanks.
some times a wipe from recovery will help and goes back to normal boot
many issues may cause this problem for instance if framework.jar or android.policy.jar or... have some bugs , will happen like that
Hi,
By wipe you mean clearing the formatting system, data, cache, dalvik cache and a factory reset? I ask this because the MIUI roms are not are non-wipe and the instructions recommend you to format those places before install (which I did).
I mean wipe cache partition from recovery. just try it and ley us know if it works
Well I just tried again but it doesn't work because I can't access recovery mode. It hangs at the Galaxy S screen and doesn't move from there so I'm wondering why because if I can't fix the bad install then I can't access the recovery mode and can only flash.
if recovery dont work BUT download mode does,
start the whole process again, flash back to stock froyo with froyo bootloader.
did you come to MIUI from Gingerbread ??
Well i've done the process like 10 times, nearly every single time from froyo (JPU,JS5,Ezbase 2.0) and I also went from 2.1 to 2.2 and then to MIUI. The other times I have tried coming from CM7 as CM7 works.
well i have a similar issue but in my case i just wiped my data thru cwm on darky v8 xxjpy..
now i get boot loops,any idea what should i do??
i know this is not exactly the thread but if i get my answer it'll save me from starting a new one..
When I got bootloops i normally reflashed. If you don't have data it will probably work?
I assume you have data as your on Dark v8 when V9 is out?
i dont understand by have data??
i flashed v9.5 but went back to v 8 few months ago..
today i just wiped/factory reset my phone using cwm and it was succesful but now its bootloops and vibrations..
i never wiped my phone before and only have flashed using cwm,never used odin for flashing roms!!
OH I see, by data i meant personal data that you might want to back up...I'm not to most knowledgeable but I know how to flash roms. I reckon you should try to flash V8 it again if you can enter recovery.
Hello!
Today, i decided to install cyanogemmod on my 2x. So i downloaded ROM manager and downloaded cyanogenmod. everything went fine until i was going to boot for the first time. I got into a bootloop. so i tried taking out the battery and all that stuff but it still would't work. So i tried to recover the phone. I recovered it to a month old backup (I could not find the one i made in ROM manager before i installed cyanogenmod) The recovery went fine. But, when i rebooted it got into a loop on the lg logo! (the one without the loading bar) it would just load the lg logo, be there for like 10sec, then it would do the same. I tried recovering one more time, but it didn't work. The same thing happend. What should i do? :S Should i wipe data/factory reset?
EDIT: My phone was on android 2.3.4 before i download cyanogenmod.
BTW before i installed cyanogenmod, i forgot to clear cache and data. I was in a hurry so i did't notice the screen popping up, I automatically pressed "ok" without selecting anything.
Thanks for the help
- Kashif
Different partitions... Look for something called backtoext3 in the dev section (or somewhere else) The problem is that when you flash a custom rom like CM you convert your filesystem to EXT4, while stock is EXT3.
So basically what you have to do is:
1) Reboot into recovery
2) Wipe everything
3) Flash Backtoext3 zip
4) Restore Nandroid.
This should work. this will take you back to stock.
So i have to restart the phone, Choose wipe data/factory reset, then flash backtoext3 (how do i do it? lol) then restore nandroid (the backup i just tried to restore twice?)
kashi169 said:
So i have to restart the phone, Choose wipe data/factory reset, then flash backtoext3 (how do i do it? lol) then restore nandroid (the backup i just tried to restore twice?)
Click to expand...
Click to collapse
Yes
Flashing backtoext3 is just flashing the zip file you put on the sd card. (and then install zip from SD ) an then restore your nandroid stock backup and you're back on stock.
But you said you wanted to try CM right? In that case, wipe everything (factory reset/data + cache + dalvik) and then flash the CM7 rom and you have CM! Don't worry about backtoext3, your partitions are already on EXT4, because of your prior CM flash.
Ohh! Thanks Can you send the files for cm (2.3.4)? I've found some, but im not sure if my phone is compitable with them :S im really afraid to mess something up again
My. Signature. (CM7 temasek's KANG = the best CM7 at the moment )
I did everything and i got into a bootloop at the skating andriod screen again
OK, restored my phone back... Now it wont connect to the network and the battery has a question mark inside it. It also says the battery level is 999% heelp
Nvm, got my phone back to normal still dont understand why cm wont work...
You need cwm5 to flash cm.
I have a G2x, which is basically the same phone. But anyway, I would recommend nvflashing CWM and not getting it from ROM Manager.
CWM 5.0.2.0 will do just fine, but it is indeed old...
Anyway, are you sure you waited long enough on the CM boot screen? The first boot might take a couple of minutes. (4 or 5)