[Q] boot failure: AOSP Froyo kernel for Magic 32A - myTouch 3G, Magic Android Development

Hi all, I have a Magic 32A (radio 3.22) and wish to compile a working Froyo kernel for it. Compilation went fine, but it won't boot (stuck at the 1st boot screen).
Basically, here were what I did:
1. downloaded android-msm-2.6.32 from AOSP.
2. make msm_defconfig, add "CONFIG_MSM_AMSS_SUPPORT_256MB_EBI1=y" to .config, then make (to compile kernel). All went fine.
3. compiled system/wlan/ti/sta_dk_4_0_4_32/wlan.ko
4. downloaded and compile all other froyo stuffs. At last, I got all necessary images.
system.img ran fine on emulator. Based on http://wiki.cyanogenmod.com/index.php?title=How_to_build_a_kernel_port_for_CM6, I used AnyKernel to recreate boot.img.
Flashed system.img (from fastboot) and signed_update.zip (from recovery). NO, it stucked on the 1st boot screen. Went back to recovery and flashed the most current CM EBI1 kernel, boot went fine.
So, it must be the KERNEL I compiled. Did I miss anything? I had been stucked on this for weeks. Thanks in advance!

Related

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!

Working kernel based on toast's source?

Has anybody on here been able to compile/boot their own evo kernel? I have been able to
compile a kernel just fine but given the limitations of fastboot on our spl i cannot test the
image using "fastboot flash zimage zImage". I have tried packing the kernel into a boot
image then signing and flashing rom. This got me stuck at the 1st boot screen. I have also
tried to unpack and repack the stock boot image without making any edits and that fails at
the first boot screen as well. So I believe there is definately something different to the
procedure of flashing or creating boot images.
So does anybody have any advice? maybe a fix? If anyone is able to boot a custom kernel please send me a pm!
haven't had a chance to test out the kernel ... i know in flipz supersonic .6 rooted ROM a kernel is flashed in the update.zip file. not sure what kernel this is since the OTA update from .1 to .6 the boot.img didnt change, md5sum the same. i didnt compare the md5sum of the boot.img hes using to the RUU boot.img .
i know the froyo ROM on here flashes a boot.img, which i think remember reading was compiled from toast's kernel source. i'd imagine mainly with a modified init.rc ...
hope that helps a bit and gives you some motivation its possible although the two examples i've given are from toast and flipz who both appear to be ahead of the curve!
once the htc kernel source hits i plan on kernel compiling ...

deck evo4g ICS Alpha4 boot.img Boot Manager

I have used Boot Manager for quite a while now and while the Boot Manager dev explains that most ICS ROMs will not work with it, Deck's EVO 4g ICS mod did work in Boot Manager with the pre-releases, alpha1, and alpha2 . I never got to try alpha3 but alpha4 does not work with boot manager anymore. What changed that prevents a proper boot.img being built on alpha4? Is there something I can do or is it up to deck to decide if he wants to make alpha4 compatible with boot manager (as were the pre-releases and alpha1 and alpha2)?
I figured it out late last night. I reinstalled my boot image from phone ROM, restored slot1 (CM7 256) with boot image, re-installed slot 2 (alpha4) with newly built boot image and all is well. Guess I jacked it up at some point .... good thing for back-ups eh

[Q] PAC-man ROM not booting anymore

hi,
so as i can not post in the android development subforum i'll have to try it here..
I have: HOS with TWRP 2.4.4.0 (goo manager) with HBOOT 2.15 (S-ON) running PAC-man ROM 22.1 (the newest update)
also i have bubba v4 installed and everything was working really perfectly. (s2w and some kernel tuner settings)
yesterday i played a bit with UI settings, nothing that i thought would stop my device from booting..
today i woke up, the battery was empty so i plugged in, turned on and left, after a while i came back and it was still at the boot
animation (PAC is loading...).
now i have tried to reflash bubba, PAC (cache+dalvik wipe) and the boot.img via fastboot. still it is stuck on that loading screen.
now i'd really like to use this rom with the bubba kernel.
any clues how i could get it out of this boot cycle?
thanks
-t.
2.4.4.0 is kinda crap in certain things. Flashing roms is one of them. Please use 2.3.3.0 as this will work.
why do you think that twrp version is the problem?
flashing this rom with 2.4.4 has worked well, so flashing over the same ROM with it shouldn't be problem...?
when flashing or wiping everything seems to work normally.
also, i am not sure how to downgrade twrp!?
best,
-t.
edit: okay i found out, fastboot flash recovery .. should work. i'll let you know if it works afterwards *fingers crossed*
edit2: reflashing the ROM it takes much longer (maybe thats good?) i just hope it finishes at some point...
edit3: okay, so re-flashing with twrp 2.3.3.0 did'nt work either, it is still stuck at the "PAC loading..." stage
(yes, i flashed the boot.img too)
any more clues?
finally i had this phone set up just the way i wanted, it was perfect and then this. why couldn't it just keep working
makes me sad, i want to use my phone damnit
okay, so i flashed and wiped and flashed and wiped a few times, system, cache, dalvik whatever, suddenly it started working... i also flashed some different kernels (as i thought some bubba stuff might still be there)
soo IDK what it was but now it works again, thank god..
maybe its worth mentioning that i flashed an older PAC rom (v22.0.1_20130324-230044) though i am not sure if that was the problem...
Sorry, I was off for some time from this forum.
If your bootloader version is > 1.09 you'll have to flash the kernel separately due to some restrictions in the higher bootloader versions.
If e.g. you flashed boot.img only from the 'bubba.zip' you're missing some of the modules needed for working coming with that flashable zip. Just have a look inside the zip file and you'll see some different content besides the boot.img. So you need to flash the complete zip file (to get the modules) and separately again the boot.img (to get the kernel itself).
The point about 2.4.4.0 / 2.5.0.0 is, that some installer scripts for some roms don't work as they should.
:good:
Hey,
Thanks, yeah but the thing is I installed Bubba right I think. Even manually copying the modules and setting the permissions...
and it has been working. Does the system lose modules when the permissions are not exactly right? I remember leaving the exec permission on for the modules because I was lazy
Well nevermind I guess I learned something from this little action that cost me most of my precious Saturday...
Also I now tried flashing twisted 3 and bulletproof kernel neither of them worked for pac rom, maybe someone could explain to me which kernel works for which rom? I thought they are completely interchangeable as long as they are compatible to the hardware..
And how do boot images work? I thought if you flash a boot image it overrides the old one, but flashing a Rom and then only installing a boot image from some kernel doesn't end with booting the rom (that's how I tried to repair it in the first place )
Well, appreciate the help.
Best,
#t.
Sent from my One S using xda app-developers app harhar
Bulletproof is for sense
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
Aha okay, I thought sense is like any app running ontop of any kernel...alright.
Sent from my One S using xda app-developers app
tehtomi said:
Hey,
Thanks, yeah but the thing is I installed Bubba right I think. Even manually copying the modules and setting the permissions...
and it has been working. Does the system lose modules when the permissions are not exactly right? I remember leaving the exec permission on for the modules because I was lazy
Click to expand...
Click to collapse
Usually the installer script should set the right permissions already. Nah, modules shouldn't go lost this way ( system/lib/modules/*.ko).
tehtomi said:
And how do boot images work? I thought if you flash a boot image it overrides the old one, but flashing a Rom and then only installing a boot image from some kernel doesn't end with booting the rom (that's how I tried to repair it in the first place )
Click to expand...
Click to collapse
In short: boot.img = kernel
It's stored in an own partition (block) on the phone, That's why you have to use 'fastboot flash boot boot.img'. Same for radio: 'fastboot flash radio radio.img' and so on. The bootloader will load them first from this block. But search Google if you'd like to know more. lol
Usually there is a boot.img file in any rom.zip that can be extracted and flashed also it's supposed to be flashed with the rest of rom.zip in one go. Blame htc for their bootloaders which prevent you from this. That's why we talk about htc's half assed bootloader unlock.
To come to an end: There are sense based roms, AOSP and AOKP based roms. Whereas AOSP and AOKP based kernels could be interchangeable, sense based kernels are only compatible to htcs sense UI. That's why you can't mix them up with all the roms out there. Sense is deeply integrated into kernel.

Categories

Resources