Hi xda. I just installed (flashed) cyanogenmod 9 on my nexus s, after getting bored with the stock kernel so I flashed trinity ics kernel. Now when I try and flash a new kernel nothing changes, cwm recovery said it flashed successfully. The procedure I did when I installed it was:
1) install zip from SD card
2) choose zip
3) yes
4) reboot system
Is there anything I did wrong? Do i need to clean the cache and dalvik cache?
Sent from my Nexus S using xda premium
How are confirming that it did not flash?
Clockwork recovery said it was successfully installed. Also the version of the kernels are right for my rom (ics)
Sent from my Nexus S using xda premium
You missed understood me.
How are you checking/confirming that the kernels you flashed after trinity are not actually flashing/ booting/being used or how ever you want to phrase it?
cm changed their ramdisk(again). so now custom kernels without cm ramdisk wont boot cm. as always, cm likes to "break" things. complain to cm. i recommend other non cm based roms, like rasbean jelly. it doesnt have as much junk included and is a faster/smoother experience than cm. many kernel developers arent willing to cater to cm anymore because of these changes they constantly make. enough is enough.
Im with you Simms but I think this one is a case of him seeing the boot animation of Trinity and thinking it is still the kernel.
albundy2010 said:
Im with you Simms but I think this one is a case of him seeing the boot animation of Trinity and thinking it is still the kernel.
Click to expand...
Click to collapse
maybe so, bit i dont see a mention of a boot animation
---------- Post added at 03:07 PM ---------- Previous post was at 03:03 PM ----------
albundy2010 said:
Im with you Simms but I think this one is a case of him seeing the boot animation of Trinity and thinking it is still the kernel.
Click to expand...
Click to collapse
ah, ok. i reread the op very slowly.
op, did you check the kernel version in your about phone? other kernels wont get rid of the boot animation unless they offer a boot animation or include a script to delete it.
Yeah. But he is saying he doesn't see a change. Implying the phone boots up as it did prior.
He is also on cm9 , not the new cm10 that botched things up again.
That is why I am trying to get him to confirm how he is checking if the kernel changed. Almost certain its the op just seeing the boot animation and thinking that it didn't change due to that.
Op. Go to settings /about phone and look at kernel version. Flash a different kernel again. Check again.
I am confirming that it did not flash by going to settings and then about phone. In kernel it still says Trinity kernel rather that matrix kernel or air kernel (2 roms I've tried flashing).
Sent from my Nexus S using xda premium
Strange. What recovery and version of it are you using? If its a older cwm with a updated version or a different recovery altogether.
You can boot the different recovery with fastboot boot recovery name of.img and flash without loosing your current one
[/QUOTE]
albundy2010 said:
Strange. What recovery and version of it are you using? If its a older cwm with a updated version or a different recovery altogether.
You can boot the different recovery with fastboot boot recovery name of.img and flash without loosing your current one
Click to expand...
Click to collapse
I am using Clockworkmod Recovery version 6.0.1.0. Would you suggest flashing a new rom, I am considering that as a last resort. Also I am fairly new to rooting and things like that so I do not know a great deal about ramdisks etc.
I would try to flash a kernel with twrp first. I am not a fan of cwm recovery myself and don't trust it.
If that's a no go. Try a different ICS ROM if that's what you want. Or jb etc.
Still find it odd that recovery says it flashes but it doesn't. Usually as Simms was saying the phone doesn't boot with strange kernel behavior/ incompatibility. Honestly not sure what exactly what is causing it. So just use process of elimination to try and sort it out.
Maybe Simms knows of or heard of this type of behavior before and can provide some info.
I am using Clockworkmod Recovery version 6.0.1.0. Would you suggest flashing a new rom, I am considering that as a last resort. Also I am fairly new to rooting and things like that so I do not know a great deal about ramdisks etc.[/QUOTE]
albundy2010 said:
I would try to flash a kernel with twrp first. I am not a fan of cwm recovery myself and don't trust it.
If that's a no go. Try a different ICS ROM if that's what you want. Or jb etc.
Still find it odd that recovery says it flashes but it doesn't. Usually as Simms was saying the phone doesn't boot with strange kernel behavior/ incompatibility. Honestly not sure what exactly what is causing it. So just use process of elimination to try and sort it out.
Maybe Simms knows of or heard of this type of behavior before and can provide some info.
Click to expand...
Click to collapse
Ok ll try that
You can flash my cm compatible kernel.
Make a backup of your current setup in cwm recovery. Then format /boot under mounts and storage to wipe your current kernel. Then flash new kernel and reboot. Even if this gives you an issue, you have a current backup that can be restored.
Sent from my Nexus S 4G using Tapatalk 2
p1gp3n said:
Make a backup of your current setup in cwm recovery. Then format /boot under mounts and storage to wipe your current kernel. Then flash new kernel and reboot. Even if this gives you an issue, you have a current backup that can be restored.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
I gave up and flash a new rom and kernel thanks for the help.
Related
Since I was an android virgin until just before Christmas, I'm still trying to get to grips with all the cool stuff that can be done.
I've rooted the phone and unlocked the bootloader. Everything else is currently stock.
I don't want to go to Clockwork recovery, or Cyanogen/MoDaCo ROMs. Not yet. I'm still savouring the "Google Experience".
However, I have three questions (which may turn into many more ) about flashing new kernels, and I don't want to clog up any specific kernal thread with noob questions.
1) Does flashing a kernel wipe the whole phone the way unlocking the bootloader did?
2) If you're running stock ROM with new kernel, will you still pick up OTA updates as before?
3) How do you get the original kernal back if you don't like the new one (or if it just goes totally tits up)?
Thanks guys
EDIT: Yes, I realise there is a search and this may well have been asked before. But before someone points this out, I'd like to mention that if you do a search for "android kernel", you get approximately 1 bajillion hits...
Mr.Clark said:
Since I was an android virgin until just before Christmas, I'm still trying to get to grips with all the cool stuff that can be done.
I've rooted the phone and unlocked the bootloader. Everything else is currently stock.
I don't want to go to Clockwork recovery, or Cyanogen/MoDaCo ROMs. Not yet. I'm still savouring the "Google Experience".
However, I have three questions (which may turn into many more ) about flashing new kernels, and I don't want to clog up any specific kernal thread with noob questions.
1) Does flashing a kernel wipe the whole phone the way unlocking the bootloader did?
2) If you're running stock ROM with new kernel, will you still pick up OTA updates as before?
3) How do you get the original kernal back if you don't like the new one (or if it just goes totally tits up)?
Thanks guys
EDIT: Yes, I realise there is a search and this may well have been asked before. But before someone points this out, I'd like to mention that if you do a search for "android kernel", you get approximately 1 bajillion hits...
Click to expand...
Click to collapse
1) No, you should not wipe anything before flashing a kernel. You should however do a NANDroid backup.
2) You should be able to but it will wipe your kernel.
3) Restore your backup from #1
Mr.Clark said:
Since I was an android virgin until just before Christmas, I'm still trying to get to grips with all the cool stuff that can be done.
I've rooted the phone and unlocked the bootloader. Everything else is currently stock.
I don't want to go to Clockwork recovery, or Cyanogen/MoDaCo ROMs. Not yet. I'm still savouring the "Google Experience".
However, I have three questions (which may turn into many more ) about flashing new kernels, and I don't want to clog up any specific kernal thread with noob questions.
1) Does flashing a kernel wipe the whole phone the way unlocking the bootloader did?
2) If you're running stock ROM with new kernel, will you still pick up OTA updates as before?
3) How do you get the original kernal back if you don't like the new one (or if it just goes totally tits up)?
Thanks guys
EDIT: Yes, I realise there is a search and this may well have been asked before. But before someone points this out, I'd like to mention that if you do a search for "android kernel", you get approximately 1 bajillion hits...
Click to expand...
Click to collapse
flashing a kernel doesnt wipe your phone, it simply replaces whatever kernel is in your phone at the moment.
kenvan19 said:
1) No, you should not wipe anything before flashing a kernel. You should however do a NANDroid backup.
Click to expand...
Click to collapse
Right. Guess what my next question will be
kenvan19 said:
2) You should be able to but it will wipe your kernel.
3) Restore your backup from #1
Click to expand...
Click to collapse
2) Is fine, as once I've figured out how to NANDroid backup, re-flashing it should be easy enough. 3) Is fine, once I've taken the backup in the first place.
simms22 said:
flashing a kernel doesnt wipe your phone, it simply replaces whatever kernel is in your phone at the moment.
Click to expand...
Click to collapse
Excellent, thanks!
Ok. So all the NANDroid guides I've seen here start with ADB and Fastboot (which I remember doing when I rooted the phone), but then they say about flashing alternative recovery images... is that necessary? Or is that what the fastboot thing was?
I've just checked and ADB still works, so if fastboot is an alternative recovery image, am I good to take a NANDroid backup, and if so, how do I do that?
If Fastboot is not an appropriate recovery image, do I need Clockwork Recovery (is that different to the "CWM" I see mentioned around here?)?
The Nexus S guide I read said that there was a NANDroid option in the Clockwork Recovery. Now this isn't in my recovery options, obviously, but I assume with ADB, a command prompt and a few instructions, I can do it manually. Maybe.
Bear with me guys, I'll get there eventually...
Ok, scratch the NANDroid questions. NANDroid is a backup tool contained in the Clockwork Mod recovery image.
Using Fastboot, you can boot from the recovery image without flashing it (using this guide here), so I've still got whatever recovery image I got when I did Paul's rooting technique, but have booted into CWM once to do the NANDroid backup.
I may flash CWM later, that's a task for another day.
So. Now I've got the backup (and thus, booting from that image again later, the ability to restore from it), I can try flashing the kernel. Which I can do from the regular recovery image.
Mr.Clark said:
Ok, scratch the NANDroid questions. NANDroid is a backup tool contained in the Clockwork Mod recovery image.
Using Fastboot, you can boot from the recovery image without flashing it (using this guide here), so I've still got whatever recovery image I got when I did Paul's rooting technique, but have booted into CWM once to do the NANDroid backup.
I may flash CWM later, that's a task for another day.
So. Now I've got the backup (and thus, booting from that image again later, the ability to restore from it), I can try flashing the kernel. Which I can do from the regular recovery image.
Click to expand...
Click to collapse
To flash from the stock recovery you must rename files update.zip just FYI. I've said it before and I'll say it again; there are no possible negative repercussions from flashing a non-stock recovery image.
Apparently it was unsigned, so the stock recovery wouldn't do anything with it.
Back in CWM and it worked fine. I may have to flash that, it's damned useful...
So now I have a new kernel!
Thanks for all your help
Mr.Clark said:
Apparently it was unsigned, so the stock recovery wouldn't do anything with it.
Back in CWM and it worked fine. I may have to flash that, it's damned useful...
So now I have a new kernel!
Thanks for all your help
Click to expand...
Click to collapse
It is very useful indeed! Enjoy your kernel
Ah, am I right in thinking that if I flash CWM, I can't revert back to stock if I want to?
I'm hoping to do nothing permanent at this point...
Mr.Clark said:
Ah, am I right in thinking that if I flash CWM, I can't revert back to stock if I want to?
I'm hoping to do nothing permanent at this point...
Click to expand...
Click to collapse
Yes, you can flash back. Not only can you but depending on how you did flash the recovery the phone may revert it on your behalf. I know mine has several times, like any time I reboot. There's ways to stop it from doing that but I don't mind.
To get the stock recovery back if it isn't automatically restoring means flashing an NAND from the Dev section here.
I didn't want to open a new thread just to ask this so I hope it's OK to post it here.
I'm very interested in getting supercurio's voodoo sound and ext4 mod on my Nexus S but I don't need/want the overclocked frequencies and other stuff included on most of the kernels out there. You guys know any kernel that I could flash to get those and keep my stock fequencies?
Thanks
Sent from my Nexus S using XDA App
nicholasbgr said:
I didn't want to open a new thread just to ask this so I hope it's OK to post it here.
I'm very interested in getting supercurio's voodoo sound and ext4 mod on my Nexus S but I don't need/want the overclocked frequencies and other stuff included on most of the kernels out there. You guys know any kernel that I could flash to get those and keep my stock fequencies?
Thanks
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I use overclocked with voodoo and setcpu...you can keep it set to 1000 and not over the stock limit.
Bionix 1.3 is solid and no OC
Sent from my Nexus S using XDA App
nicholasbgr said:
I didn't want to open a new thread just to ask this so I hope it's OK to post it here.
I'm very interested in getting supercurio's voodoo sound and ext4 mod on my Nexus S but I don't need/want the overclocked frequencies and other stuff included on most of the kernels out there. You guys know any kernel that I could flash to get those and keep my stock fequencies?
Thanks
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
If you flash the Trinity max kernel and do not adjust the clock you will have everything your asking for. This kernel boots at stock and has Voodoo and ext4 built in.
icandy75 said:
If you flash the Trinity max kernel and do not adjust the clock you will have everything your asking for. This kernel boots at stock and has Voodoo and ext4 built in.
Click to expand...
Click to collapse
So your saying the trinity max kernel has voodoo built in?
Sent from my bionix nexus s
mrnexus said:
So your saying the trinity max kernel has voodoo built in?
Sent from my bionix nexus s
Click to expand...
Click to collapse
That is exactly what he is saying, yes =)
Thanks guys, I'm gonna take a look at your recommendations as soon as I get some spare time.
Do all the trinitys have voodoo
Sent from my bionix nexus s
mrnexus said:
Do all the trinitys have voodoo
Sent from my bionix nexus s
Click to expand...
Click to collapse
No, only the most recent ones.
kenvan19 said:
No, only the most recent ones.
Click to expand...
Click to collapse
Such as:
Sent from my bionix nexus s
Dont want to muck up the CM7 thread and no thread was started.
FB Im wondering if twrp is fully wiping when you run the wipe option. I used the kj6 heimdall one-click to get back from a bad flash. However once I finally was able to get everything set back up I had restored some apps through Titanium Backup, but only app no data. Amazon app store was one and I had to delete the backup and uninstall the app, reboot clear cache and then re-install it to get it to work. The theme chooser app was fcing on me until I did the same thing.
After I did this I applied a theme apk that borked me. I was stuck on the team acid logo. No boot loop just stuck. I then one clicked to kj6 again, then used antonx kernel one click. Made a new backup of my efs, wiped everything including boot img. Flashed the twrpcm7 zip and followed the directions to finish.
I know anything is possible but is it likely that twrp is seeing something not wiped in the bml to mtd conversion and its causing conflicts?
If your not comfortable with the possibility of bricking your phone do not follow my steps and format everything. Formatting boot has the possibility to brick your device.
Hmm, well /data isn't getting wiped in R11. Bryan submitted a patch for updater.sh that should take care of this though I haven't tested it. I haven't tested a BML->MTD (cm7-twrp) flash though, but I'll have to look into it in the next few days. I'm running a rom build right now, so I'll probably test that out tonight.
I didn't wipe anything, I just flashed the twrp boot.img. I am running Team Kick Asses MIUI Revenge (MTD). After I flashed and the phone booted, wifi would not turn on, and it said error underneath the button. Pulled a logcat but all it said was wifi failed to initialize. Is that error due to the fact I didn't wipe anything or factory reset/fix perms?
Either way, it is super sweet recovery!
Max says its a driver issue. Ill find the post and link it.
m4xm4n said:
The reason wifi didn't work is because the wifi module needed to be from the same kernel build. I'm not sure how FB built the two builds, so I don't know if he included a module from a different kernel build or not.
Try the R11B with TWRP and then install R11(not B) with inject TWRP enabled.
Sent from my SGH-T959V using XDA
Click to expand...
Click to collapse
Now that you have twrp make a cwm zip for the r11 kernel, flash it via twrp and leave the "inject twrp" option enabled. You should get working wifi and twrp
Sent from my SGH-T959V
Like I said on cm thread the wifi module is different from the one Max used on his new boot.img which is why twrp and the new boot.img doesn't work with the current miui build ...the first release of dianxin os had the new boot.img fb sent me and that was the wifi issue.
sent from my batcave
I flashed miui on with twrp doing a wipe firs and it installed miui fine, with wifi and everything seems to be fully functional. Just to be safe I wanted to test out twrp on miui, however the only way I could get to it was volume up+down+ power. But that loads it right up, and I flashed a few different modems to see which gave me the best signal, and it worked each time. Btw, nice work fb twrp is great.
Sent from my SGH-T959V using xda premium
Which modems did you flash? If the modem flash DID work you should be able to go into Settings > About Phone and check under baseband version. I'm not sure if that's the exact menu on MIUI but there should be something very similar.
I just flashed kg4 and that's what it says under baseband version, I flashed kd1 earlier and that's what it said before I just flashed kg4. Just to make sure it was working. I think it says t959vuvkg4 or something to that effect, it definately just changed though from kd1
Sent from my SGH-T959V using xda premium
Hey guys just a progress report on this. I've been messing with a twrp injection cwm zip all evening. After some discussion with bhundven, the way we're going to go about this is to NOT include twrp by default in cm7. It's been really hard to get a working copy compiled and included with cm7 and if we can't do this automatically there's no point to doing it at all.
The CWM zip will (hopefully) allow us to give you the option of using TWRP even if you're using CWM at the moment. The benefits are the following:
You won't need to mess around with kernel features that don't work (wifi was broken, ffc was broken)
You only really need to inject twrp once via CWM since twrp comes with an inject option before you flash a CM7 update.
It'll make it easier on us since we'll have less releases and thus have to provide less support.
At the moment I'm trying to have something for you guys tonight, but the chances are slim for that happening.
FB
For some reason TWRP can't Flash Zip file like Mtd modem kd1. I try to make a nandroid bk and didn't work. Also I try to save error logs on sd card didn't work.
My english is not the best, sorry
Sent from my SGH-T959V using xda premium
Please post the logs here.
What errors did you get when trying to flash the kd1 modem or make the nandroid backup? I've tried making and restoring a nandroid backup using CM7 R11 with twrp injected by the zip and it's worked fine for me.
What rom/kernel combination are you using?
Error: Unable to open zip file
I try nandroid backup again and for some reason did work but wasn't working.
Am using CM7 R11B & CWM TWRP
Everyting else is working good thanks!!!!
Sent from my SGH-T959V using xda premium
To whoever can help me -- I'm trying to use kexec to install CM10 on my SGS3, but i've been hearing that when you hard-reboot your phone, AKA battery pull/death, or using the power button, you go right back to the recovery. This isn't a problem, as long as I don't have to re-flash CM10 every time I boot, or I have no choice but to go to the stock ROM. I'd like to be able to either boot to the CM10 or go to my currently flashed version of CM10 from the recovery.
Any clarification on how kexec works on the SGS3 or any advice might help.
Thanks!
Bumping... could really use help here.
Just reboot from recovery and it will bootloop a couple times then boot up.
DonSagiv said:
Any clarification on how kexec works on the SGS3 or any advice might help.
Thanks!
Click to expand...
Click to collapse
Flash a recovery that supports kexec. You'll find this in the OP of the CM10 threads. Then make a backup, wipe data/cache, flash CM10, and flash Gapps, reboot. When your phone boots, it will appear to bootloop once or twice. Ignore it and give it a few minutes, longer after a new flash. Expect that every time. Once in a while, a cold boot may boot you into recovery. In recover, just tell it to reboot and you'll be back in CM10. That's all there is to it, for an end user. It won't force you to go back to stock, and you don't have to flash anything every boot.
You may have heard conflicting information from outdated threads. Before some smart cookies automated the kexec process, you had to do some manual flashing every reboot. This is no longer the case.
lazarus2405 said:
Flash a recovery that supports kexec. You'll find this in the OP of the CM10 threads. Then make a backup, wipe data/cache, flash CM10, and flash Gapps, reboot. When your phone boots, it will appear to bootloop once or twice. Ignore it and give it a few minutes, longer after a new flash. Expect that every time. Once in a while, a cold boot may boot you into recovery. In recover, just tell it to reboot and you'll be back in CM10. That's all there is to it, for an end user. It won't force you to go back to stock, and you don't have to flash anything every boot.
You may have heard conflicting information from outdated threads. Before some smart cookies automated the kexec process, you had to do some manual flashing every reboot. This is no longer the case.
Click to expand...
Click to collapse
In which cases would someone lose kexec and need to reinstall it?
Zalithian said:
In which cases would someone lose kexec and need to reinstall it?
Click to expand...
Click to collapse
When u flash back to stock.
droidstyle said:
When u flash back to stock.
Click to expand...
Click to collapse
Or any rom.
jaymattt said:
Or any rom.
Click to expand...
Click to collapse
not necessarily...if your flashing a custom rom/kernel like beans custom stock, cm10, paranoidandroid, aokp, or imosyeons Touchwiz leankernel, kexec is always there...kexec is built into the kernel, cwm 6.0.1 is compatible with kexec.
Question though. Could cwm touch be modified to make it kexec enabled?
Sent from my SCH-I535 using xda app-developers app
Vorfidus said:
Question though. Could cwm touch be modified to make it kexec enabled?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I used cwm touch for the very first kexec kernel release(boosted v.1 https://www.dropbox.com/sh/mv3gz6skad1nsnx/-oUr708Bc2), where you had to reflash the emmc in recovery on each reboot in order to stay on the custom kernel. Not sure if cwm touch works for the later kexec builds...
droidstyle said:
Just reboot from recovery and it will bootloop a couple times then boot up.
Click to expand...
Click to collapse
Thanks! CM10 works beautifully on here.
droidstyle said:
I used cwm touch for the very first kexec kernel release(boosted v.1 https://www.dropbox.com/sh/mv3gz6skad1nsnx/-oUr708Bc2), where you had to reflash the emmc in recovery on each reboot in order to stay on the custom kernel. Not sure if cwm touch works for the later kexec builds...
Click to expand...
Click to collapse
There is a kexec cwm touch recovery some where here on xda.sorry don't have the link. There is also a kexec twrp 2.2 recovery but it didn't work for me.
piiman said:
There is a kexec cwm touch recovery some where here on xda.sorry don't have the link.
Click to expand...
Click to collapse
yea i know, thats what I used in reference to my previous post.
droidstyle said:
yea i know, thats what I used in reference to my previous post.
Click to expand...
Click to collapse
would love the link, all i have is 6.0.1.0. if anyone needs a kexec (old) CWM, i posted it here:
techneesh.com/recovery.tar
err, looks like this post has touch kexec cwm?
http://forum.xda-developers.com/showthread.php?t=1773514
Triskite said:
would love the link, all i have is 6.0.1.0. if anyone needs a kexec (old) CWM, i posted it here:
techneesh.com/recovery.tar
err, looks like this post has touch kexec cwm?
http://forum.xda-developers.com/showthread.php?t=1773514
Click to expand...
Click to collapse
let this thread die....there is no need to use anything kexec. stick to cwm 6.0.1.0 or 6.0.1.2
I'm having a problem flashing marmite 4.4 to the newest miui build (2.9.7).
Basically in cwm recovery and flashed the kernel.
Will say "ununderstandable message 3" and "lid is licked"
Reboot the device and it will get stuck on the miui boot screen.
Tried installing both the "stock OTA" and "All other ROM" version of marmite.
Same message comes up.
Already tried performing a full wipe (actual full restore, format system, format boot), reload the ROM.
Tried wipe cache and dalvic (even though it is not needed)
Just wondering if there is something incompatible or not.
I was able to flash air kernel without issues.
I haven't tried an older version of marmite yet, but will try later.
I'm not blaming marmite, it could be miui as well, or it could be just me.
I'm certain I'm flashing correctly.
I read bedalus' marmite post and saw 2 others with this issue (not same version of kernel or ROM).
The suggestion was that they didn't use the correct kernel for ROM.
I would assume miui would not be categorized as "stock OTA", so I tried "all other ROM" version first"
Am I doing something wrong?
There is a new version 4.5 the message you get I believe is like a joke. It does show however that the installation was successful.
Never experienced boot loops flashing his kernels.
Sent from my Nexus S
Actually, I downloaded that one just now to try and same issue.
It will just stall at the miui (ROM) boot screen.
I am trying some other stuff right now as well.
Really want to use this kernel. :good:
I'll report back later.
Thanks for the help.
Good luck. His kernel offers great speed and stability!
Sent from my Nexus S
For marmite 4.5, did a full wipe again, even formatted the SD partition.
So flashed miui 2.9.7.
Booted to the ROM.
Made sure things seem normal in the ROM.
Restarted just to be sure.
Boot back to recovery.
Flashed marmite 4.5
And it is stuck on the miui loading screen again.
Only thing I haven't tried this time is to fix permissions. (didn't wipe cache or dalvic either)
I'll try it again. :laugh:
Since I formatted the SD partition, it should rule out that it was something on the SD card right?
It's time consuming to copy things back to the NS.
I'll try an older version of marmite afterwards and then an older version of miui.
It should tell me what is causing the lock up by then. I think. :silly:
.... yes I have a lot of time ....
I forgot to mention one thing.
I'm flashing the official Chinese version of miui 2.9.7.
Wonder if that's the cause.
I guess I will download the US or UK version to try as well.
Well if your phone boots with original kernel, it must be kernel related. There's no need to wipe anything before flashing a kernel. Just flash it. It could be that the Chinese rom is different from the others, but that's a guess I'm no expert on compatability.
Sent from my Nexus S
kwibis said:
Well if your phone boots with original kernel, it must be kernel related. There's no need to wipe anything before flashing a kernel. Just flash it. It could be that the Chinese rom is different from the others, but that's a guess I'm no expert on compatability.
Sent from my Nexus S
Click to expand...
Click to collapse
Took some time to test, but sort of found my answer.
It's the official Chinese miui that's causing the issue.
Well at least some component in the ROM.
I tested with the MIUI UK (miuiandroid) version 2.9.7 and it installed like a charm.
Before flashing the UK version, I tested with earlier versions of marmite (4.3 and 3.5) on the Chinese 2.9.7.
All failed at the ROM boot screen.
I should check with the miuiandroid team and see what they changed that made it different.
When I was testing I did a full wipe, installed ROM, booted ROM, boot to recovery and flashed the kernel.
I didn't even wipe cache or dalvic (which is not needed anyways).
I had to do a full wipe because the ROM just wouldn't boot back up afterwards.
I'm tempted to test with an earlier version of the official Chinese miui and see if it makes any difference.
... too much time and/or no life ... :laugh:
Lol, well it's good you found your answer So its not a waste lf time as you learn from this
Sent from my Nexus S
If you flash air kernel, and if it worked, I guess marmite's boot.img type can cause a problem.
Sent from my Nexus S using Tapatalk 2
Articudos said:
If you flash air kernel, and if it worked, I guess marmite's boot.img type can cause a problem.
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
Not sure what the boot.img type is, but I'll look it up. Thanks.
I posted on miuiandroid forums and someone replied saying that the Chinese version is odexed and not busyboxed.
UK and US version is definitely deodexed, I downloaded them and checked. I haven't found out how to check busybox.
I have a few choices.
1. I can use the UK or US version, since I was able to flash marmite on them... easy way out.
2. Find out how to deodex the ROM and, I guess, how to add busybox (?)... I get to learn more stuff.
3. Use a way faster ROM (eg. Paranoid Android - great ROM by the way!) and flash marmite on it as well... but really want to use miui again.
Thanks guys for your help though. Really appreciate the information. :good:
Glad you found a solution
For the past few days now, I've been attempting to flash $droyd$'s unofficial AOKP and thicklizard's komodo kernel, with no success. I've fastboot flashed before and/or after, wiped everything, run wipe scripts, chanted voodoo prayers, but nothing has worked. It either hangs on the boot animation, or occasionally makes it to the welcome screen before freezing and rebooting. I've been flashing ROM's on this thing for a while, and have been using unofficial cm10.1 so far as my daily driver. What the hell am I doing wrong?
Not sure but you may also still want to flash the kernel zip and then fastboot flash. There may be kernel modules that the zip needs to install for the kernel to work well on 10.1
Sent from my HTC One S using xda premium
AKToronto said:
Not sure but you may also still want to flash the kernel zip and then fastboot flash. There may be kernel modules that the zip needs to install for the kernel to work well on 10.1
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Still no dice unfortunately, I guess it's just not meant to be. CM10.1 is running great so I don't have much to complain about.
Ok I think I've pinpointed the problem-it has something to do OC kernels. I just flashed your new Canuck kernel with PACman and I'm getting the same freezing and rebooting issue. Is my phone overheating somehow?
trathiang said:
Ok I think I've pinpointed the problem-it has something to do OC kernels. I just flashed your new Canuck kernel with PACman and I'm getting the same freezing and rebooting issue. Is my phone overheating somehow?
Click to expand...
Click to collapse
Are these kernels being flashed with arioma installer... If you go to my aokp thread 2nd post you will see a tweaked 4.2 version-- it already has komodo modules installed and komodo is the boot.IMG inside the zip... Do this no skipseys---download that rom-- fastboot the boot.IMG in my zip---boot to recovery and wipe every thing INCLUDING SD CARD..x3---- now mount your phone to PC and copy and paste the ROM zip to your SD card..it will look weird cause it will be the only thing on there. ----- now install ROM then wipe only the caches after that--- hit reboot----system
And enjoy aokp with komodo kernel... Now to explain---every time you re flash that kernel you are stacking modules that is why you won't boot and also why you now need to do the spring cleaning wipe.... If you follow those steps exact no skipseys you will get it done---
Sent from my Nexus 7 using xda premium
Eureka! Did adb bugreport while it was booting to see what was going wrong, and I saw that there was something up with the voltages. Set the clock speed to minimum and then turned up the voltages in kernel tuner and VOILA, working overclock! I guess my phone, for whatever reason, disliked the undervolted voltages.