Database Info

Problem with flashing Cyanogen

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

No luck installing cyanogen

I have successfully installed amon-ra's rom on my rogers' 32a magic device (also using his recovery image).
I have tried countless ways to install the cyanogen rom (followed all instructions on wiki), but I can never get past the rogers boot screen.
Any ideas what could be causing this? Do I need to be using the cyanogen recovery image too? If so, when I flash that recovery image, I can not seem to get into it (home+power).
Thanks for the help...

what are the steps you are following. are you flashing the custom recovery before you flash cyanogen like it says to in the wiki?

Hey, thanks for the quick reply.
In the recovery bootup, I am
flashing : DRC83_base_defanged.zip
then flashing: update-cm-4.2.10.1-signed.zip
I have also tried the various 'wipe' options that are in the recovery menu, but nothing has made a difference. I have read that you should wait a while for it to boot, but how long is long? After about 15 mins, I give up.
I have followed the instructions on:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_MT3G/Magic_Firmware_to_CyanogenMod
The ION rom takes not time at all to successfully boot after flashing.

You flash the base, the rom, then the port file.
You did everything correctly except you didn't flash the latest 32A port. You basically flashed 32B Cyanogen which obviously won't work and will hang at a black screen.
Flash the 32A port.

Got it! Flashed the third file, and I now see the funky cyanogen logo booting up.
So...shouldn't the cyanogen wiki be updated to mention this third file that needs to be flashed?

ajhuddy said:
Got it! Flashed the third file, and I now see the funky cyanogen logo booting up.
So...shouldn't the cyanogen wiki be updated to mention this third file that needs to be flashed?
Click to expand...
Click to collapse
the "third" file is a port file created by third party (bcrook/radix) and it is unsupported by cyanogen that why it isnt inlcuded on the wiki (the wiki is part of cyan's official site).

Fair enough. So it's all up and running now.
Couple questions:
I used the latest CM rom posted (update-cm-4.2.11-signed), but notice that in 'About phone', the 'Mod Version' is listed as 4.2.4 - is this expected?
Also, will I be able to use the CMUpdater utility, or must I always apply a new CM rom through recovery mode, and do the 3-step flash as before?
Thanks!

Unable to put back to stock RUU (Need Original ROM HTC Incredible S)

Hello,
I have HBOOT-2.01.0001 RADIO-3822.01.08.14_M eMMC-boot and I'm running newest Cyanogenmod RC 7.2.0 RC1. Yesterday my phone was stock RUU and I went to HTCDEV.com and unlocked it. After that I flashed the recovery to Clockworkmod v.4.0.1.4 through ADB. Put the CM RC 7.2.0 RC1 .zip on the root of the SD card along with Gapps .zip file.
Then I rebooted into Clockworkmod recovery and installed the 2 .zip files and rebooted. It would not boot and was stuck on HTC logo screen. I found out that I had to separately flash the boot.img file from within the CM RC 7.2.0 RC1 .zip and then everything worked fine.
(Oh yeah, forgot to mention that I did do a backup from within the Clockworkmod before flashing the CM rom)
Ok, so I tested Cyanogenmod for a couple of hours and found out that it was a bit faster than the new stock Ice Cream Sandwich (latest update per 20 april 2012) and it had a lot of ekstra features, but the interface and layout is really low end in my opinion. I gave it a honest try and spent some time changing settings and layouts and even downloaded a couple of ADW themes. Nothing that was even near the new ICS.
Bottom line is that I really want to get back to the original stock RUU Ice Cream Sandwich and I'm unable to
Attempt 1:
I have tried to restore the backup that I made in Clockworkmod and it seems to install just fine. But when restarting it gets stuck on HTC logo Screen. So I thought, maybe this has something to do with the boot.img that has to be flashed manually. So I took out the SD card and put it in my PC using a adapter. Found the boot.img file from the backup inside the clockworkmod/Backup folder and flashed the boot.img file and I'm still stuck on HTC logo screen. It will not boot after recovering the backup no matter what I try.
Attempt 2:
After googling a lot I found the website Shipped ROMs and found my model which I believe to be VIVO (I have a HTC Incredible S from april 2011 in Norway (Europe)).
The only logical RUU i can find is: RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20 .2808.30.085AU_3805.06.03.03_M_release_199308_sign ed.exe
Since the other 2 RUU's listed are ASIA.
I downloaded the WWE RUU and ran it. I followed the instructions to the point and got the message Error 155 after about 30 seconds right after it is finished with sending.....
Now the phone will not boot again, stuck on HTC logo screen. And so I'm running out of ideas. In other words I'm stuck here
I reflashed the same Cyanogenmod rom and at least that works again
Anybody have any suggestions in how to solve this or any info at all to direct me into the right direction? This would be much appreciated
I'm thinking maybe anybody knows where I can find a stock ROM .zip file for this phone modell that I can flash the same way i do Cyanogenmod (as described above)?
Maybe even an older version like Froyo, but then I hope it is possible to update to latest stock RUU just using the built in "search for update" function in settings.
Yours sincerely,
Mr. T. Nuis

[Q] CM10 Stable not working?

Ok. I just flashed CM10 stable on my SGS2 Skyrocket, and LOVE it, so I wanted to give it a shot on my Xoom (MZ604). I was having problems getting into CWM, due to the recovery image being overwritten (I was running stock, unrooted 4.1.2 until tonight).
I got that all sorted by flashing the stock, rooted ROM found here, and that was humming away fine. Rebooted into the bootloader, and flashed the CWM linked here. Rebooted into that version of CWM, only to find that I can't access my external SD card where I have the CM10 image stored.
Flashed back to the original CWM I had when first rooting, and flashed CM10. Flash went well, rebooted, and now I'm stuck at the CM load screen. The one with the circle going around and around.
I thought maybe something was wrong with my tablet, so I rebooted into CWM again, and reflashed the stock, rooted version, and it was fine. Flashed back over to CM10, and the same thing. Stuck at the load screen,. It has been there for at least 30 minutes.
I did wipe the cache and Dalvik before every flash of both ROMs.
Any ideas anyone? TIA
EDIT: Is it possible to put the CM10 image on internal SD card and flash it from there? I had assumed that wouldn't work because of formatting and the like, but if it's on /sdcard and not /system...
Edit 2: Just did a factory reset(can't believe I forgot this!!), and all is well now. Mods, please lock this thread. Thank you

[Q] upgarde snaufu...

was running viperXL 3.2.5 and wiped and went to cm10.1 now i used goo manager to download xhata (sorry i butchered it) now i can only boot into spash screen and bootloader. i used fastboot to reflash twrp and still only boots to the custom spash... hboot 1.09 s-off..... im kinda lost here. should have syuck with viper, why screw with perfection.

What is xhata? Is it a rom?
I'm not sure we can install roms with Goo Manager on this phone.
If you installed a rom for the quad-core Tegra One X, your phone will not boot and you're lucky you didn't get a brick. You need to do a full wipe and reflash.

first off not a noob. it was the evita rom. i still have bootloader access and can get half way into recovery( spash screen then twrp spash...) then reboot into custom splash. it was the rom... http://forum.xda-developers.com/showthread.php?t=2075783 so if anyone has any ideas please help, just dont start with the usual u screwed up flashing roms i know better. and the odd part is after reflashing the recovery via fastboot i get Twrp spash before going back to the phone main splash and boot looping.... and yes im s-off

No need to be so defensive. If we don't know exactly what you flashed, all we can do is ask. Its not meant as an insult. But its always better to ask the seemingly "obvious" questions first, get them out of the way.
If there is a "usual thing" that gets mentioned, its because the mistake of flashing ROMs for the ENDEAVORU in fact happens so often. Downloading from GooManager is not a great idea either, and often a red flag that someone installed a ROM for the wrong version of the phone.
Did the phone operate properly when you were on CM10.1?
What version of TWRP, and what fastboot command did you use to flash it?

I asked the "usual" questions because:
-You have less than 100 posts. That's often a sign of someone who is new to this.
-You used a rom name I've never heard of, and suggested you weren't sure of the name yourself. That's usually a big red flag for someone who flashed some random rom they found via Google.
-You mentioned using Goo Manager. That's a non-standard method for this phone, and an awful lot of people have bricked their phones trying to flash roms through apps that aren't well-supported. CWM Touch was notorious for this when the One X first came out.
If you don't want people to assume things, you need to state them up front.
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.

iElvis said:
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
Click to expand...
Click to collapse
Yeah, I saw that too, and why I asked the OP what version of TWRP.

i had problems with that rom on version 4.0.1 and 4.1.0 had alot of errors and trouble. i haven't tried 4.2.0 though, i have been having better luck with rom after clearing out recovery cache running "fastboot erase cache" and running only twrp 2.3.3.1.

i flashed the second to last release of twrp (latest gave mount issues), viper was running great, cm 10.1 avatar was running fine just didnt like how plain it was so i used goo manager to download hatkaXL and when the download finished i picked select and flash.. then the usual warning about flashing and it rebooted, hit spash screen where it still is hours later. i then tried manually boot into recovery, it hit the bootloader i selected recovery and it seemed to try and load. next step was back to fast boot and to reflash twrp (fastboot flash recovery recovery.img ) flashed 100% success and still wont boot into recovery just the bootloader, and i wasnt trying to get all defensive, i sent first post using the wifes phone and posted quick, had a guy hooking up my satellite at same time as phone crashed. has anyone tried the new version of cwm for the evita? maybe flashing that may get me back, i have roms and backups on the pc that i can seem to side load but never boot as well.

well after repeated flashing of recovery and (fastboot erase cache) it finally booted to recovery, now to see if my backup will load.