edited boot.img - myTouch 3G, Magic Android Development

I seem to be having problems with ANY edited boot.img? Is there much changed in the boot.img for official magic sense ui?
Reason im asking is i can flash cyan roms,nko2 roms etc but if i try and based on sense ui it gives me a write_raw_image:BOOT error
ok if i fastboot boot boot.img it loads to the HAMI boot screen but just loops?

bonesy said:
I seem to be having problems with ANY edited boot.img? Is there much changed in the boot.img for official magic sense ui?
Reason im asking is i can flash cyan roms,nko2 roms etc but if i try and based on sense ui it gives me a write_raw_image:BOOT error
ok if i fastboot boot boot.img it loads to the HAMI boot screen but just loops?
Click to expand...
Click to collapse
well there is a good reason to release a hero kernel there should be a difference!

its even doing it with the official sense ui for magic
well there is a good reason to release a hero kernel there should be a difference!
Click to expand...
Click to collapse
So not only hero builds

The problem is the BFS Boot.img whenever i try a rom with this it fails. If i use an old boot.img from a superlight hero rom it works fine?

what are is the logcat when it loops at the hami screen??

no booting image anymore, ive managed to boot and use magicuni official sense ui with the boot.img from superlight sapphire hero rom but wifi wont work

take the wlan.ko from /system/lib/modules/ folder in the superlight sapphire hero and place it in your magic uni build in /system/lib/modules/
wifi should work
wlan.ko goes with boot.img to make wifi work
so if you just changed the boot.img in uni build your wifi wont work becuase the wrong wlan.ko is there
if that doesnt make sense ill just repackage the whole thing and put it in update.zip format for you to flash over any rom in order to use it on your phone

Thanks zarboz Its ok i realised i need the wlan.ko when i was at work so fixed it using their computer i wouldnt mind the 107meg ram hack in the dwang donut rom though working for sense on my phone?

bonesy said:
Thanks zarboz Its ok i realised i need the wlan.ko when i was at work so fixed it using their computer i wouldnt mind the 107meg ram hack in the dwang donut rom though working for sense on my phone?
Click to expand...
Click to collapse
idk i thnk the only boot.img's floating around for 32b with the ram hack are BFS patched wich are the boot.img's your having an issue with right?

that is correct looks like ill just have to use the standard launcher instead of sense and use some widget goodness

Now using reignzone with the same boot.img as before and rosie does not keep restarting on me no matter what i do!

Related

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 ...

[Q] UOT Kitchen Bootloader not working

I cooked a theme in the kitchen, flashed it and everything takes except the bootloader animation.
Not sure what I am missing. I am using the new Serendipity rom.
TOA Duck said:
I cooked a theme in the kitchen, flashed it and everything takes except the bootloader animation.
Not sure what I am missing. I am using the new Serendipity rom.
Click to expand...
Click to collapse
Not sure if Mikey has an updated kernel with bootanimation support.
Either that or you need to rename /system/media/bootanimation.zip to /system/media/sanim.zip
I gotcha, I will push it through root explorer.
Thanks

[Q] Switch between ICS and JB mods?

Hey Guys,
I´m new to HOS custom mods and so I have a question.
Yesterday I successfully installed Trickdroid 9.1 which is JB and would like to try Vipermod which is ICS.
I would do it like this: Go to recovery, clear cache,dalvik,system and simply install the rom.
To switch back to Trickdroid, I have to flash the stock 9.0 Trickdroid rom and then restore my backup.
Is this procedure right?
Thanks alot for all your work, I really like this site!
Sounds about right... Except I dont think you need to flash trickdroid before restoring your backup.
Ive been switching between viper and Dark Jelly a few times by only restoring the backups (+fastboot flash the boot.img's)
Thanks!
I´ll give it a try this afternoon
gerryfresh said:
Thanks!
I´ll give it a try this afternoon
Click to expand...
Click to collapse
Just make sure to fastboot the boot.img from the Viper ROM (ie extract the boot.img from the Viper ROM and then fastboot flash boot boot.img)
The kernels for JB and ICS are not the same. you would need to flash the rom and fastboot the boot.img unless you are on a low hboot (ie ver 1.06, 1.09)
Viper provides a flash-script in their thread, so all you need to do (for viper) is extract it and doubleclick flash-boot-windows.bat
Hint: That also works with other boot.img's. Simply replace the boot.img with any other boot.img
Thanks for the replies! Flashing the boot.img with commandline is no problem!
Both work great, but I think I´ll stay with Trickdroid until ViperOneS 2 is released
Anyway thanks for the infos!

[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.

[Q] Stuck on green htc logo

Hello.
I currently have my pico with stock rom, with sense 3.5. and i'm tryin to flash a new rom, but every time i try to flash one from this thread ( http://forum.xda-developers.com/showthread.php?t=1754876 ) i got stuck on htc logo screen. and i cant get passed it... i've wiped everything, reflashed kernel, reflashed stock, but still cant get it to work. maybe these kernels arent for stock roms, if they're not, can you point some kernels that work on stock?
thanks in advance.
Stock rom should have stock kernel too.
Flash the gingerbread kernels.. they must work. PS: The ROM.zip already contain kernels that get installed when the zip is flashed.
Red Devil said:
Flash the gingerbread kernels.. they must work. PS: The ROM.zip already contain kernels that get installed when the zip is flashed.
Click to expand...
Click to collapse
where can i find those gingerbread kernels? so if they're inside the "rom.zip" is it possible to "extract" them to a flashable zip? only the kernel withouth the rom itself...?
Gingerbread kernels are in the Index of all kernels..
From the ROM.zip if you want to extract them then just extract the boot.img normally and also extract the modules from the zip .. in /system/lib..
In fastboot mode flash boot.img via :
Code:
fastboot flash boot boot.img
and
then via adb push the modules. I suggest you search a bit and find some answers yourself . Its easier that way cause these questions have been answered millions and millions of times. So use the search function
i've searched, and believe me when i say that i havnt found anything about this... all the kernels i go for, on the thread only talks about the kernel itself and not the roms compatible... and i've tried that method and got stuck on htc green logo... thanks for answering
these kernels work on stock rom:
1- cranium kernel
2- ateeq kernel
3- garuda's kernel
search them in the development thread I hope you'll find them.
i've tried all those kernels... one by one and never got passed the htc green logo... always get stuck there... i tried flashing trough fastboot and trough recovery... nothing works... any other suggetions?
try to flash ateeq rom then ateeq kernel..it works for me.
but i dont want to have ateeq rom, i want to stay with my stock rom, but change the kernel... only that. but thats for answering. i'm getting used to the idea that i cant be changed (the stock kernel).
thanks
Need urgent help
i had rooted my pico months back and was on different custom roms......now i want 2 get back to the stock rom which i have downloaded Odexed Stock ROM Flashable Zip (With Link2SD Support)(Revision 3)(http://forum.xda-developers.com/showpost.php?p=40385554&postcount=76) and i have flashed this rom 5 - 10 times and everytime i reboot after flashing the rom.....i am stuck on htc boot logo.....can u plssssss help

Categories

Resources