*dentist*, eh? that's alright, you don't have to tell us her name ...
loaded on Cm9 of May 8th this morning using Odin and still working fine after 14 hours no problem, except for the missing instructions that I had to figure out miself.
Now my question, and maybe this is stupid: what WAS the reason people got bootloops? 'cause I don't think I saw an explanation anywhere .....
tx in advance and best regards,
Jacobus
LOL because of this --> *dentist*, eh? that's alright, you don't have to tell us her name ...
Personally, I believe some people who flash on CWM with their USB cable plugged in that got the bootloop problem. I've never had any bootloop when flashing custom kernel. And I did try (once) switching between kernels, no bootloop.
And you can see how many people on CM9 thread say that they got into bootloop when flashing CM9 ROM (with their USB cable plugged on).
I flashed the newest nightly build coming from CM9 with mnics kernel also no bootloop.
The only time I got bootloop (since using ICS) is when I flash theme.
actually yes, I was serious I'm a programmer, albeit on a totally different platform and language, but I always insist on detailed instructions in my job ('foolproof'). It gets to be part of your personality.
but I get your point, none taken and grateful for your effort, for sure.
"if it's worth doin' in production, it's worth documentin'"
So how about writing up a well structured, detailed step-by-step guide about the usage of Odin in order to flash a custom kernel?
This way you could help others that run into similar problems with your experience in production and documentation :)
And finally, what you missed in the OP of this kernel would be fixed by yourself.
... tapatalked
Samsung Galaxy Nexus
ROM: CM 10.1
Kernel: franco.Kernel r366
Samsung Galaxy S
ROM: CM 10.1
Kernel: Semaphore Kernel 2.9.15s
Hugemempatch (409MB)
LOL because of this --> *dentist*, eh? that's alright, you don't have to tell us her name ...
Personally, I believe some people who flash on CWM with their USB cable plugged in that got the bootloop problem. I've never had any bootloop when flashing custom kernel. And I did try (once) switching between kernels, no bootloop.
And you can see how many people on CM9 thread say that they got into bootloop when flashing CM9 ROM (with their USB cable plugged on).
I flashed the newest nightly build coming from CM9 with mnics kernel also no bootloop.
The only time I got bootloop (since using ICS) is when I flash theme.
I never flashed with the usb cable plugged in and those bootloop issues quite often. But let's not fill this thread with bootloop stories ;) There's an extra thread only about this problem.
So how about writing up a well structured, detailed step-by-step guide about the usage of Odin in order to flash a custom kernel?
This way you could help others that run into similar problems with your experience in production and documentation :)
And finally, what you missed in the OP of this kernel would be fixed by yourself
I give up explaining this. There's a post about 2 pages back which explains why I will not do what you just suggested.
You can open a thread and do this if you want, no problem.
Quote:
Originally Posted by Fenvarien
And finally, what you missed in the OP of this kernel would be fixed by yourself
Now I'm getting really angry. I missed a detailed explanation about how Odin works and I can fix it myself this way ???
Before I have to go to work, some Initramfs info as requested (this is copied from our sources):
# CM9 currently uses an init system with two separate initramfs
# images which are packed into the kernel image at compile time.
# During every boot process the needed initramfs image (recovery
# or Android) gets extracted and the boot process continues using
# the freshly extracted initramfs.
We are not sure but we thought packing and extracting separate boot images for recovery/normal boot images at every boot could be the reason, maybe something goes wrong withing this process. So we decided to build an initramfs/init that does *not* have to unpack initramfs images at every boot. I'm not sure about it but until now I did not see new bootloop reports.
SGS1 work: Midnight-/MNICS-/MNCM7-/MNGB-kernels, personal slimmed down ROMs, small framework MODs...
SGS2 work: No time**, just using it \w XWLQ2/Speedmod...
Nexus7: Stock
The Following User Says Thank You to mialwe For This Useful Post: [ Click to Expand ]
I give up explaining this. There's a post about 2 pages back which explains why I will not do what you just suggested
Mialwe, you completely misunderstood my intention - I tried to support your position! I answered to Jacobuscuracao's posting. Please - read my text again without anger :)
Grüße aus dem wilden Süden,
Fenvarien
... tapatalked
Samsung Galaxy Nexus
ROM: CM 10.1
Kernel: franco.Kernel r366
Samsung Galaxy S
ROM: CM 10.1
Kernel: Semaphore Kernel 2.9.15s
Hugemempatch (409MB)
Flash latest nightly and boot rom.
Power off.Go to download mode,flash midnight via odin.
Everything ok.I didn't loose modules folder.
I tried flashing midnight on the latest CM9 nightly with Odin too (usually I take Heimdall).
Odin works flawlessly and I encountered no further problems with the modules folder.
... tapatalked
Samsung Galaxy Nexus
ROM: CM 10.1
Kernel: franco.Kernel r366
Samsung Galaxy S
ROM: CM 10.1
Kernel: Semaphore Kernel 2.9.15s
Hugemempatch (409MB)
Mialwe, you completely misunderstood my intention - I tried to support your position! I answered to Jacobuscuracao's posting. Please - read my text again without anger :)
So sorry Fenvarien, really, really sorry.
Yes, I completely misunderstood your post. That happens if I'm angry anyways and just dont read the text you quoted and then write too fast.
I'm really sorry and apologize for this.
Not a good day today, now I'm waiting for the next bad thing to happen, started this morning, continued at work and now I'm waiting...
SGS1 work: Midnight-/MNICS-/MNCM7-/MNGB-kernels, personal slimmed down ROMs, small framework MODs...
SGS2 work: No time**, just using it \w XWLQ2/Speedmod...
Nexus7: Stock
The Following 4 Users Say Thank You to mialwe For This Useful Post: [ Click to Expand ]
Yes, I completely misunderstood your post. That happens if I'm angry anyways and just dont read the text you quoted and then write too fast.
I'm really sorry and apologize for this.
Not a good day today, now I'm waiting for the next bad thing to happen, started this morning, continued at work and now I'm waiting...
Kudos for being such a gentleman!
(I'm having one of those days too. One of my main work tools, a really expensive bass guitar, fell over from its stand and its neck cracked. Later I spilled a cup of coffee on my keyboard. Great. So you're not alone!)
XDA Elite Recognized Developer AdamOutler is known … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?