Hi! first of all i dont know if this is the right forum to right this question. Dont know if it should be in the Dream forum but i have a magic, so i write it in the Magic forum.
My problem is that i for some reason can't flash Cyanogen's ROMs.
I have had Cyanogen's 4.0.3 ROM on my magic, but a couple of days ago i decided to upgrade it and try the Experimentel version 4.1.8.
I First tried to use the CM Updater, but for some reason it did not work, it would not flash the ROM.
So i downloaded the ROM manually and did as i always do: boot in recovery, wipe, apply and then reboot. Everything went fine until the reboot. After reboot the phone gets stuck at the HTC Magic screen, and nothing happens, only thing i can do is to remove the battery and the try and boot the phone again, and then it just get stuck at the HTC Magic screen again.
I have no problem flashing a MyHero 1.1.1. It works perfect.
I have also tried with a number of the other Cyanogen ROM versions, even tried 3.9.1 (cant remember the exact version number) have also tried the 4.0.3 version that did work before all this happened, but still no luck.
I have tried installing the Cyanogen Recovery image and the flash the Cyanogen ROM, but it still gets stuck at the HTC Magic screen.
I have tried reformating my sdcard and then flash, but no luck.
Can it be that i need a new SPL, Radio or something?
My current Fastboot screen looks like this:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.33.2010 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
If anyone know what i need to do to get the Cyanogen ROM on my magic, i would really like to know.
Any suggestions would be much appreciated. Hope to here from you.
Per
Cyanogen is built for 32B (You seem to have a 32A) so you need to flash a 32A-kernel on top of the cyanogen ROM.
Check this thread:
http://forum.xda-developers.com/showthread.php?t=544854
do what psyduck says, AND wipe before you do it. going from a stable to an experimental build requires a wipe or you will have a lot of issues.
Okay, thx for the answer both of you.
So i just "flash" the kernel first, like if it was an normal update? e.g. rename it update.zip, push it to sdcard, wipe, flash and then reboot. And then flash the ROM like i would normal do?
But what if I would like to flash a stable build, e.g. 4.0.4 what do i do then? i can't find a kernel for that in the link. Or can i just use 1 of the kernels in that link?
Per
Cyanogens ROM first! Otherwise the kernel will be overwritten with the one included in the cyanogen ROM.
Don't know why the old kernels were removed? Better to ask in the linked thread.
Decided to try Donut on my MT3G and had the same issue, I did a wipe after I noticed it didn't get past the first splash screen and that fixed it.
Thx for the help all of you, im now on the Cyanogen ROM, finally. its good to be back
But have 1 last question: When i deside to upgrade the current Cyanogen ROM im on now, i would also need to flash a new kernel right?
the thread listed by PsyDuck has it.
first page, look at the file called "Base Kernel v4.1.9.2"
link for it is right below.
Use amonRA's Recovery so you dont have to rename the updates.
download CM's latest 4.1.9.2 ROM and the basekernal. put both in root directory of SD.
boot into recovery, nandroid backup, wipe, Flash ROM then Flash update.
reboot. should work fine.
I did so, and everything works now. really nice, finally
32a looping after flashing CyanogenMod 4.1.99
I have a 32a and I used to run CM 4.0.4 perfectly fine.
I've been trying to flash to later CM roms but until now still not able to do so.
Every steps in http://forum.xda-developers.com/showthread.php?t=568032 were followed carefully. Here is what I do:
1. Copy the HTC ADP 1.6 DRC83 into the SD card
2. Copy CyanogenMod 4.1.99 into the SD card
3. Copy the Kernel Port file into the SD card
4. Wipe
5. Flash HTC ADP 1.6 DRC83
6. Flash CyanogenMod 4.1.99
7. Flash the Kernel Port file
8. Reboot
The phone reboots into the first screen (HTC Magic) and after a while, reboot again and still stuck at the same screen.
Eventually I have to take out the battery.
I don't partition my SD card and it has been working fine with the other roms such as RA 1.6.1H, MyHero 1.1.2 etc, so I doubt that could be the problem.
I tried to plug the USB and "adb lolcat" but my WinXP says USB device not recognized.
The strange thing is it seems everyone's 32A doesn't have this problem, except me. I've reported this problem before but wasn't able to get a solution.
Is there anyway to troubleshoot to find out what goes wrong?
Thanks in advance.
thats actually weird..try restoring nandroid backup..
i followed the same instructions with the exception of not wiping..try that see if it helps.
Thanks for replying. I didn't manage to flash successfully before that's why not able to do a nandroid backup ... unless of course if someone is willing to share the backup with me.
str4vag said:
thats actually weird..try restoring nandroid backup..
i followed the same instructions with the exception of not wiping..try that see if it helps.
Click to expand...
Click to collapse
Same Boat
I have the same problem when flashing CM 4.1.99[9] ROMS. It goes into the endless boot/reboot mode.
I used to have the problem with the HoFo ROM as well (between versions 2.0.5 - 2.0.9). HoFo started working after that. I don't know what changed.
Code:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.33.2005 (SAPP10000)
RADIO-3.22.20.17
Apr 20 2009, 15:30:43
ranger79 said:
I have a 32a and I used to run CM 4.0.4 perfectly fine.
I've been trying to flash to later CM roms but until now still not able to do so.
Every steps in http://forum.xda-developers.com/showthread.php?t=568032 were followed carefully. Here is what I do:
1. Copy the HTC ADP 1.6 DRC83 into the SD card
2. Copy CyanogenMod 4.1.99 into the SD card
3. Copy the Kernel Port file into the SD card
4. Wipe
5. Flash HTC ADP 1.6 DRC83
6. Flash CyanogenMod 4.1.99
7. Flash the Kernel Port file
8. Reboot
The phone reboots into the first screen (HTC Magic) and after a while, reboot again and still stuck at the same screen.
Eventually I have to take out the battery.
I don't partition my SD card and it has been working fine with the other roms such as RA 1.6.1H, MyHero 1.1.2 etc, so I doubt that could be the problem.
I tried to plug the USB and "adb lolcat" but my WinXP says USB device not recognized.
The strange thing is it seems everyone's 32A doesn't have this problem, except me. I've reported this problem before but wasn't able to get a solution.
Is there anyway to troubleshoot to find out what goes wrong?
Thanks in advance.
Click to expand...
Click to collapse
phone: htc dream/t-mo g1
current recovery: clockworkmod recovery v2.0.1.3
spl: haykuro (pretty sure but i don't remember)
radio: i don't remember but i know i had updated that at one point too
(if there are ways to check i will)
short version is: can i restore a nandroid backup made with amon ra v1.2.2 using clockwork v2.0.1.3?
more of the story: i had amon ra v1.2.2 and made a nandroid backup, wiped phone, and tried to load a new rom. it didn't want to go passed the g1 loading screen so i pulled the battery and restored using nandroid. went to market downloaded free version of rom manager installed clockworkmod recovery(figured maybe a newer recovery tool might be needed) and used rom manager to install the rom. still wouldn't move passed the g1 loading screen. so i load up recovery and click nandroid and restore, but it tells me none found.
are they two different types of nandroid saves that the recovery program can't use either others? or isit that clockwork looks somewhere else for the nandroid save and i could maybe move stuff around on the sd card to make it work?
this question is for after i figure out the above problem: but i had cyanogenmod v4.2.15.1 and the amon ra v1.2.2 when i made the nandroid. and i was trying to put cyanogenmod v5.0.8 and now i am using clockworkmod recovery v2.0.1.3. when i install cm5 and then reboot it sits at g1 screen, it doesn't keep rebooting. sat for a good 10mins before i figured maybe something is wrong. am i missing something? i have already upgraded my spl a while ago when i was trying out hero/2.0 roms a while back (pretty sure i put haykuro on my phone, is there a way to check?). anyone able to help me or suggest something for this?
thanks for your time
not sure if you can never tried.
Clockwork stores it files in a folder clockworkmod\backup\yyyy-mm-dd-hh.mm.ss\
When i first installed cm6 alpha it took about 15mins to reboot. Best thing to do is launch logcat while booting to see whats going on.
Hey guys
I have a t mobile G1 rooted with Danger SPL and (Just Recently Flashed) Amon Ra 1.7.0 Recovery image.
All my troubles started after I saw that Super Froyo had a new bulid of 4.4, so I wiped my system, cache, sd-card, data (But not my boot) with my old Clockwork Mod 2.5.2. Everything went fine and dandy and the new bulid ran nicely, but as I reread over the directions for Super Froyo 4.4 i found that partitioning your SD card would increase speeds on this particular build. So I flashed Amon-Ra's recovery and then I partitioned my SD card to 512MB EXT3 / LinuxSWAP 64MB... After this I encountered alot of FC's.... So i flashed back over to CM6 Stable after partitioning again and now... Im stuck in countless bootloops.
Ive only had a somewhat-firm grasp on rom's so far, but i think my G1 is not technically bricked if i can access the recovery image full menu.
I need help ASAP.
Thanks.
Its alive :d nm xd xd horray!
I'm running the newest Cyanogenmod 6.1, coming from a Fresh ROM. I've had the same Recovery image since I rooted the phone, RA-heroc-v1.2.3.
I'm trying to use the ROM Manager included with my new ROM. In order to do so, I need to have clockwork as my recovery image. I've flashed both the Clockwork recovery image 2.5.0.1, as well as an updated version of RA's (v1.6.2) using ROM Manager. In each case, the process appears to complete successfully.
However, when I boot back into recovery using Home+End, I continue to get my original RA recovery 1.2.3 menu.
is there something I'm doing wrong that's preventing me from updating my recovery image?
Any help would be greatly appreciated.
drewski3420 said:
I'm running the newest Cyanogenmod 6.1, coming from a Fresh ROM. I've had the same Recovery image since I rooted the phone, RA-heroc-v1.2.3.
I'm trying to use the ROM Manager included with my new ROM. In order to do so, I need to have clockwork as my recovery image. I've flashed both the Clockwork recovery image 2.5.0.1, as well as an updated version of RA's (v1.6.2) using ROM Manager. In each case, the process appears to complete successfully.
However, when I boot back into recovery using Home+End, I continue to get my original RA recovery 1.2.3 menu.
is there something I'm doing wrong that's preventing me from updating my recovery image?
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I had the same issue the other day. I think its a rom manager problem. If you can find the clockwork recovery img file for the hero, you can try manually flashing using terminal emulator on your phone or through adb.
Sent from my HERO200 using XDA App
HBoot compatibility aside, in the past, Clockworkmod had issues with not formatting all the directories it was supposed to format. with 3.0.0.5, do they solve the problem with this version?
I like the new version and had no issues, but when flashing other ROMs some still say not to use ClockworkMod and use Amon_ra. I have an EVO 4G ver 003. I love CyanogenMod 7 and I just want to make sure I am using the best recovery for this ROM.
Newbee -