Ok, I've done a load of research trying to figure out the problem with no luck so I'm, asking you htc legend gurus out there for help.
- My gf's htc legend was OTA upgraded to 2.2
- I found the downgrade RUU procedure to get back to 1.31 with gold card to root the phone. DONE (still hboot 1.01)
- Installed CM7RC4 last month, no problem
- CM7 Stable 7.0 was released, didn't notice until CM7 7.0.2 was released
- Tried to install 7.0.2 and this is where i get problems
- I downloaded the zip and used rom manager to update
- does its thing, backups etc then reboots and installs the rom
- fone reboots and stays on the htc logo white screen for a while then goes black and back to the htc logo white screen (not the android skateboarding across the screen cm7 animation), then it goes to the black screen with the phone and red exclamation mark
- so i volume up + power, and reboot system now.. same thing back to same exclamation mark
- thought it was a corrupt zip so i download again, same result
- downloaded it again and put it on the sd card
- booted to the stock recovery, fake flash cwm update.zip recovery and manually updated by selecting the zip, SAME RESULT red exclamation mark
- gave up on 7.0.2 and downloaded 7.0 and that worked!
- installed fine and when i rebooted it went to the CM7 animation! and have a fully working phone and rom
- wasted enough time and now that it works i didn't bother with 7.0.2
- now 7.0.3 was released so i downloaded that, and tried to update it
- SAME RESULT with the red exclamation mark.
I'm following the same process for 7.0.3 as I did for 7.0. What am i missing here? Is it gold card related?
I've got a htc desire myself, rooted with miui and I was around with the htc dream/g1 rooting updating cm roms - I do have some knowledge, but this one has me stumped!
Please help, its very frustrating. Thanks in advance!
If you are using Clockwork rom manager its easy...boot into recovery (either adb reboot recovery or power on holding vol down,choose recovery,when in recovery press up + power select install update.zip and then should be in clockworkmod.......
Afer that choose install zip from sdcard,clockworkmod (folder) then flick throug htill you find the CM7 you want and flash it!
Other than that you are doing a full wipe?
yup, performed those exact steps. in various combinations via adb without adb, via rom manager via fastboot all ends in the same result
i've tried no wipe, same result
i've tried partial wipe (wipe cache and dalvik), same result
i've tried full factory wipe/reset, same result
always have to nandroid restore my 7.0 install. i really dont want to go through the whole rooting process again.
FYI cos of hboot 1.01 mine is S-ON so the phone doesn't boot direct into cwm recovery.. i have to go to stock recovery then use update.zip. I don't see how that should cause a problem if cm7.0 works fine when I flash it.
Try wiping everything? Except SDCard ofc. A good wipe usually solves the problem for me.
I usually wipe data/factory reset, then format boot, system, data, and cache.
Worth a try =)
Greets,
BartAertgeerts
Downloaded 7.0.3 again on PC this time and used Rom Manager to install it... only wiping dalvik.
Worked this time! finally Legend is 7.0.3. I hate wiping everything cos of all the customisations and tweaks I need to make.
Thanks, Calvin
Related
To begin with, I am a complete noob with any and all phone mods. I'll run down what I've done and whats happening when I do it.
I used the adb method to root my tbolt. Once that was done, I installed Superuser, and Rom Manager and flashed with the latest CWR, after clearing the download manager and turning on the erase option in settings. I have done this (flash cwr) before each attempt to flash a rom.
I have tried 3 roms: Das Bamf 1.3.2 themed (tried twice), The Perfect Storm 1.2 and VirusROM RC1b3. I used identical steps to flash them:
1. Booted to CWR
2. made a nandroid backup
3. wiped data
4. wiped cache
5. wiped Davlik (sp?)
6. wiped battery
7. install zip from sd, choose zip from sd
8. after installation, reboot
When I reboot, the white boot screen with green htc logo appears, disappears, appears, disappears, and so on. I assume this is what people are referring to as a boot loop. It happened with both Roms, and luckily I am still able to get back to recovery and restore the stock rooted rom.
I've asked for help in the android forums, and a couple of people there have been trying to help, but the only real suggestion I've received is bad dl's. I haven't been able to find the md5's for the .zips to compare to what I generate, but I can't believe 3 straight dl's are corrupt.
Anyone have any suggestions as to what I'm doing wrong? Any help is greatly appreciated.
hootinani said:
To begin with, I am a complete noob with any and all phone mods. I'll run down what I've done and whats happening when I do it.
I used the adb method to root my tbolt. Once that was done, I installed Superuser, and Rom Manager and flashed with the latest CWR, after clearing the download manager and turning on the erase option in settings. I have done this (flash cwr) before each attempt to flash a rom.
I have tried 3 roms: Das Bamf 1.3.2 themed (tried twice), The Perfect Storm 1.2 and VirusROM RC1b3. I used identical steps to flash them:
1. Booted to CWR
2. made a nandroid backup
3. wiped data
4. wiped cache
5. wiped Davlik (sp?)
6. wiped battery
7. install zip from sd, choose zip from sd
8. after installation, reboot
When I reboot, the white boot screen with green htc logo appears, disappears, appears, disappears, and so on. I assume this is what people are referring to as a boot loop. It happened with both Roms, and luckily I am still able to get back to recovery and restore the stock rooted rom.
I've asked for help in the android forums, and a couple of people there have been trying to help, but the only real suggestion I've received is bad dl's. I haven't been able to find the md5's for the .zips to compare to what I generate, but I can't believe 3 straight dl's are corrupt.
Anyone have any suggestions as to what I'm doing wrong? Any help is greatly appreciated.
Click to expand...
Click to collapse
Did you try hitting install ROM from SD card in ROM manager and just flashing it through the app? Not sure that will change your result but it flashes it for you and you can choose the options to make a backup and wipe. Can't hurt to try it.
I did try it with Das Bamf, but got the same result. Thats when I read that using rom manager to install the roms could cause problems and started doing it manually.
After uninstalling/reinstalling rom manager and flashing cwr again, I got TPS 1.1 to flash, and its working great. I then tried to flash 1.2 thru cwr, both with a data wipe and without, but both times it boot looped.
I've dl'd TPS 1.2 from a different source, and I'll try to install it when I get home. But any other suggestions are very appreciated. I'm just glad I finally got something to flash.
I'm stumped. I tried new dl's of TPS 1.2 and Das Bamf 1.3.2te, and both of them failed. I even tried turning off my antivirus while dl'ing and moving the file to my sdcard, but it didn't make a difference.
Hello all,
I need some advice. I originally followed this page http://wiki.cyanogenmod.com/wiki/Sam...l_Update_Guide to flash and everything was fine for 3 or 4 days and then the fc's came. So i odin'd to stock and when getting ready to reflash i see that you need to be on 2.2 to use his guide. So another member kwkslvr (who has been very helpful and patient btw) told me his method for flashing CM7 so i attempted to straight from 2.1 with no root to the following...
(kwkslvr's method) You definitely don't need to be on Froyo. You don't need root either. What has worked best for me is to Odin to 2.1, reboot into stock recovery and flash update.zip. Since you've flashed before, update.zip will probably already be in your internal sdcard unless you removed it. You'll have to flash it twice in a row without rebooting and that will load ClockworkMod Recovery.
Once you're in CMW Recovery (probably green recovery), wipe data/factory reset then format/system. These two steps are CRUCIAL! Flash your CM7 Nightly twice. The first time you flash it, it installs blue recovery. The second time it installs CM7. After that, again without rebooting, install gapps.
From that point, wipe data/factory reset again and reboot into the OS.
So i tried that and got to where the phone restarts after the flash and it has galaxy and cyanogen below it for a few seconds and then immediately script with font like from recovery mode races down the screen for a few seconds, then back to galaxy/cyanogen in a loop. So i odin'd again and as of now am stock 2.1 with the options of kies n it to 2.2 and then follow cyan page again or trying kwkslvr's method again. I did notice he mentioned nightlies but i am attempting to flash the stable on page 1 of this thread but don't think that would make much difference. I love the way this ROM looks and performed before it went off the tracks. Any suggestions are welcomed. Thanks alot
EDIT: At the boot loop sequence i 3 buttoned to recovery and reflashed and it seems to have worked. I notice the battery gauge no longer has the # %. And the horizontal line next to it is gone too. On my market page under "not installed" i have adobe flash showcase (Reads this item is not available at top), google search which just has a open tab (Already is installed), magic 8 ball by dennis bond (Reads this not available in your country?? it was the first time i installed it) Any ideas on how to get these 3 items off the not installed section. It's mainly a minor annoyance. I have cleared cache in market with no luck. Thanks.
So I rooted with HTC method with hboot 1.5.
I have lots of roms on it to check the speed, battery life, features of them but there has been a problem with many ROMs (MIUI, ICS alpha, Mik, Infected, Warm) all will act "wonky" after couple of days of using the rom. They will show red lines, slow downs, temporary freezes, battery would drop by 1% every 30 sec.
So, the usual thing to do is restart and BAM! They rom's logo shows up and it freezes there. Do I need a new radio update or RUU or something?
Never encountered anything close and I've been tweaking phones since the Moto Q days!
New radios might help. Are you wiping EVERYTHING before flashing?
We're comin from a pure power source.
How can I flash this new radio? Just install .zip of the file from recovery, correct?
I do "factory reset" on the twrp 2.0 recovery before I install any rom
ninten5 said:
I do "factory reset" on the twrp 2.0 recovery before I install any rom
Click to expand...
Click to collapse
I'm using twrp2 and I do
Factory reset
Wipe cache
Wipe dalvic cache
Wipe system
Factory reset (again)
Flash Rom
Reboot system.
And i never have any bootloops or stuck in HTC white screen or any issues.
Sent From My Optimized R3Dimensions
Yea. Factory reset isn't enough. I encountered that issue when doin restores on me og evo. I had to wipe cache and dalvik to get it to work.
We're comin from a pure power source.
Use cwm older 4 version as recovery.
Fastboot boot recovery.img. make sure you have a copy of it in your adb folder.
Wipe everything and flash rom
OK ill try that.
What about backup and restores, my nAndroid backups don't work
ninten5 said:
So I rooted with HTC method with hboot 1.5.
I have lots of roms on it to check the speed, battery life, features of them but there has been a problem with many ROMs (MIUI, ICS alpha, Mik, Infected, Warm) all will act "wonky" after couple of days of using the rom. They will show red lines, slow downs, temporary freezes, battery would drop by 1% every 30 sec.
So, the usual thing to do is restart and BAM! They rom's logo shows up and it freezes there. Do I need a new radio update or RUU or something?
Never encountered anything close and I've been tweaking phones since the Moto Q days!
Click to expand...
Click to collapse
Either one of two things:
your phone is defective
stop using so many apps for stuff like checking on system statuses. Just install a ROM fresh and leave it for a week with just your base essential apps like email and stuff. If the problem doesnt arise you know all your crap is causing it.
A radio update isnt going to do anything for a system issue as it is just your signal and stuff that the radio firmware would affect.
Sounds like the flash went bad due to not a full wipe or boot.img.
Twrp 2.0 is known to have its own issues.
Update: So I have infected rom installed for a couple of days, installed it using the method mentioned with wiping cache, dalvik cache, system, battery stats and guess WHAT?
It happend again, I would lose touch screen and touch button control, only way to regain control was to close screen by hitting power and waiting a few seconds and pressing it again to open the screen. Got fed up after a while and decided a battery pull, froze of Infected LOGO
Is it the way I flash the rom that is causing issues? I install the zip first with cwm 2.0 then I connect to computer and type "fastboot boot boot.img" to push the boot.img for that rom.
ninten5 said:
Update: So I have infected rom installed for a couple of days, installed it using the method mentioned with wiping cache, dalvik cache, system, battery stats and guess WHAT?
It happend again, I would lose touch screen and touch button control, only way to regain control was to close screen by hitting power and waiting a few seconds and pressing it again to open the screen. Got fed up after a while and decided a battery pull, froze of Infected LOGO
Is it the way I flash the rom that is causing issues? I install the zip first with cwm 2.0 then I connect to computer and type "fastboot boot boot.img" to push the boot.img for that rom.
Click to expand...
Click to collapse
Do this man
Get cwm 4.0 version ok now flash that then leave a copy of it in your adb folder where adb is...
Now make sure debug is on
adb reboot bootloader
fastboot boot recovery.img
Then wipe everything but not your SD card
and flash rom works this way just like the S off users use. You don't have to use flash gui or pull boot img..
So I took out twrp 2.0 recovery and put clockworkmod 5.0
I don't know why but I cant boot into the recovery without connecting my phone and pushing the .img through fastboot
Well at least two things are solved, after a restart the rom doesnt freeze and I dont have to fastboot boot.img for installing a new rom.
ninten5 said:
So I took out twrp 2.0 recovery and put clockworkmod 5.0
I don't know why but I cant boot into the recovery without connecting my phone and pushing the .img through fastboot
Well at least two things are solved, after a restart the rom doesnt freeze and I dont have to fastboot boot.img for installing a new rom.
Click to expand...
Click to collapse
cwm 4 is better for this phone dude. he said 4 not 5.
Hey,
First off i hope i have put this on the right sub forum.
I've been stupid (I Think) I've olso looked around on the forum and the [READ THIS] Got a Boot Loop? Don't post a New Thread!
topic.
I'm using my SGS2 for a year now and was using the ressurexionRimix rom for a while.
I've been plaing around with my phone so i got lots of folder that were not used etc, so I wanted to get it back to factory settings, here is when all went down.
Via Settings-Backup and recovery i gave my phone a factory reset (while using the latest ressurexionremix rom, i think this is the misstake i made) When my phone went into the reboot is got stuck on the splash screen, it kept reapeeting the boot animation.
The second mistake i mad was not puting back my back-up but thought well i want it back to it's first state so i'll use ODIN to flash the stock ROM onto it. now, 4 hours later and about 10 trys with diferent versions of the stock roms i'm still stuck on the boot screen.
I've also tryd flashing a cwm so i could get in cwm recovery, this also without any luck
Does anyone have a idea what to do!?
go back to recovery - mounts andstorage and format the following :
cache, system, data, sdcards if you have it in recovery. reboot
you have a bkank screen as your phone has been wiped. reboot into download mode.
Connect odin and flash a stock rom. reboot and your phone should work provided that you have not damaged the flash chip on the motherboard.
Is this in CWM? the problem is i dont have that anymore because i've flashed it toc stok. I now get in the Android system recovery
The option i get there ar:
Reboot system now
apply update from external storage
Wype data/factory reset
Wipe cache parition
apply update from cash
test redbend fola[FS]
Will try this, thank..will let you know if it worked
Wiped data/factory reset and cache after this i ebooted my phone and i got the message installing application, now i'm in the setup menu. Looks like it is working.
Did'nt realice there was a recovery besides CWM Thank yoy so much Cosmic Blue!!! You saved my life!!
well I was flashing MIUI V5 UNIVERSAL - v. 3.7.12 for the 3vo and it got stuck in a bootloop. to try and fix it I tried to restore a backup and that rom played a little of the boot animation but then gets stuck in a bootloop. I also tried to wipe/format everything but, that didn't work. If a logcat would help i would appreciate a link on how to do that without being able to boot. I can boot to 4ext recovery. The cause could be that while flashing I selected the file to flash, I selected a file that didn't finish downloading. Thanks in advance for any help
Also if it matters my original rom was negalite blurom.
cdog1213 said:
well I was flashing MIUI V5 UNIVERSAL - v. 3.7.12 for the 3vo and it got stuck in a bootloop. to try and fix it I tried to restore a backup and that rom played a little of the boot animation but then gets stuck in a bootloop. I also tried to wipe/format everything but, that didn't work. If a logcat would help i would appreciate a link on how to do that without being able to boot. I can boot to 4ext recovery. The cause could be that while flashing I selected the file to flash, I selected a file that didn't finish downloading. Thanks in advance for any help
Also if it matters my original rom was negalite blurom.
Click to expand...
Click to collapse
I ran into your same problem today.
At the time my phone was on latest sprint firmware, ICS coolrom (latest rom and kernel) with hboot 1.58 unlocked s-off.
The steps I did preparing to install MIUI was
1) wipe data/factory reset from 4EXT
2) format all (except sdcard)
3) Install MIUI > chose mirage kernal
4) rebooted
after reboot it was stuck at the logo, at least I thought it was, let it sit for about 5 minutes.
Pulled the battery and tried steps 1-4 again.
Kept getting bootloop at that point. Boot splash -> logo -> reboot.
Next I tried flashing the latest mirage kernel from 4ext.
No luck, same issue.
Tried repeating steps 1-4 again.
No luck stuck in bootloop.
At that point I tried to run recovery from a backup I knew was working.
Wiped all data and format all -> selected recovery from 4ext.
Result: still boot loop.
At that point I tried changing bootloader to 1.58.58 jbear. and wiping/formatting all and trying recovery again from known working cool ics backup.
Result: still bootloop.
Switched back to 1.58 bootloader and tried fresh install of CoolICS rom. (I always wipe all data and format all before any rom change.)
Result: still bootloop.
At this point I was getting frustrated but I had an idea that the MIUI install when selecting mirage kernel may have messed up the partition size for the kernel since the mirage kernel states it must be flashed from the flash gui app first to resize the boot partition.
Next I downloaded pacman rom and attempted that install.
result: could not install due to wrong bootloader.
Next I downgraded bootloader to 1.50.50 jbear.
Wiped everything and retried pacman rom.
Install success, before starting the reboot from recovery, I received a message that the boot image has changed and will make a backup/format/flash the new boot image.
upon reboot I was able to successfully boot into pacman rom.
At that point I tried to wipe all again and install CoolICS rom again.
result: bootloop, but probably because of bootloader version. Did not fully test it as at this point I just wanted a working phone again and wanted to try out MIUI.
Rebooted to recovery and wiped everything again.
Installed MIUI using stock kernel option. This time on reboot I let it sit at the rom logo without touching anything. I think it restarted once on its own.
Result: Success. Phone working normally now. such a headache I am just leaving it as is for now.
Jeffjb said:
I ran into your same problem today.
At the time my phone was on latest sprint firmware, ICS coolrom (latest rom and kernel) with hboot 1.58 unlocked s-off.
The steps I did preparing to install MIUI was
1) wipe data/factory reset from 4EXT
2) format all (except sdcard)
3) Install MIUI > chose mirage kernal
4) rebooted
after reboot it was stuck at the logo, at least I thought it was, let it sit for about 5 minutes.
Pulled the battery and tried steps 1-4 again.
Kept getting bootloop at that point. Boot splash -> logo -> reboot.
Next I tried flashing the latest mirage kernel from 4ext.
No luck, same issue.
Tried repeating steps 1-4 again.
No luck stuck in bootloop.
At that point I tried to run recovery from a backup I knew was working.
Wiped all data and format all -> selected recovery from 4ext.
Result: still boot loop.
At that point I tried changing bootloader to 1.58.58 jbear. and wiping/formatting all and trying recovery again from known working cool ics backup.
Result: still bootloop.
Switched back to 1.58 bootloader and tried fresh install of CoolICS rom. (I always wipe all data and format all before any rom change.)
Result: still bootloop.
At this point I was getting frustrated but I had an idea that the MIUI install when selecting mirage kernel may have messed up the partition size for the kernel since the mirage kernel states it must be flashed from the flash gui app first to resize the boot partition.
Next I downloaded pacman rom and attempted that install.
result: could not install due to wrong bootloader.
Next I downgraded bootloader to 1.50.50 jbear.
Wiped everything and retried pacman rom.
Install success, before starting the reboot from recovery, I received a message that the boot image has changed and will make a backup/format/flash the new boot image.
upon reboot I was able to successfully boot into pacman rom.
At that point I tried to wipe all again and install CoolICS rom again.
result: bootloop, but probably because of bootloader version. Did not fully test it as at this point I just wanted a working phone again and wanted to try out MIUI.
Rebooted to recovery and wiped everything again.
Installed MIUI using stock kernel option. This time on reboot I let it sit at the rom logo without touching anything. I think it restarted once on its own.
Result: Success. Phone working normally now. such a headache I am just leaving it as is for now.
Click to expand...
Click to collapse
well I went to go try and boot P.A.C. and my phone just booted normally. So thanks for the help