Boot.img from xoom and info from koush himself on his website
http://www.koushikdutta.com/2011/02/motorola-xoom-rooted.html
The devs said this would help. Has anyone tried to compile the stingray kernel or koushes modified? He said the harmony didnt go so well for him.
Related
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 ...
I hate making a thread like this, but I can't help but feel like I'm going to mess things up if I don't get some clarification. This is only my second android device, so I'm not too familiar with all the steps/processes to properly obtain root and change ROM's and kernels on this device.
I just received my xoom and I'm on 3.0.1. I'd like to run the tiamat kernel and ROM. I understand how to do most of the stuff, I'm just concerned with the proper order in terms of maintaining root when needed and making sure that flashing one thing before another wont cause issues. I'd appreciate it if someone can just list the most direct and proper steps for running the tiamat katana kernel and ROM from 3.0.1.
Thanks in advance
CC Lemon said:
I hate making a thread like this, but I can't help but feel like I'm going to mess things up if I don't get some clarification. This is only my second android device, so I'm not too familiar with all the steps/processes to properly obtain root and change ROM's and kernels on this device.
I just received my xoom and I'm on 3.0.1. I'd like to run the tiamat kernel and ROM. I understand how to do most of the stuff, I'm just concerned with the proper order in terms of maintaining root when needed and making sure that flashing one thing before another wont cause issues. I'd appreciate it if someone can just list the most direct and proper steps for running the tiamat katana kernel and ROM from 3.0.1.
Thanks in advance
Click to expand...
Click to collapse
What you want is actually easier then you think.
fastboot oem unlock
Let your device update itself to 3.1 cause you will need the bootloader.
fastboot flash recovery recovery.img
boot into recovery and flash tiamat 1.1.
That's it. Tiamat rom already has root and the kernel. You will have to download everything, its all in my link below. Biggest mistake is letting the system reboot in the os after you flash recovery as the os will erase it.
Sent from my PG86100
I was planning on using the katana rom and kernel on 3.2. Is there any reason not to go that route?
If I do go with that, would I just follow the kernel instructions and flash the 3.1 found in that thread instead of updating normally since that includes root? So:
-flash tiamat 3.1
-flash tiamat katana rom
-flash katana kernel?
The katana rom gets flashed before the kernel but in the same boot?
CC Lemon said:
I was planning on using the katana rom and kernel on 3.2. Is there any reason not to go that route?
If I do go with that, would I just follow the kernel instructions and flash the 3.1 found in that thread instead of updating normally since that includes root? So:
-flash tiamat 3.1
-flash tiamat katana rom
-flash katana kernel?
The katana rom gets flashed before the kernel but in the same boot?
Click to expand...
Click to collapse
I Would still let it update on its on, just because you need the bootloader thats not in 3.1 rom. Then instead of flashing the 3.1 rom, just flash the 3.2 rom. Then kernel of course.
Thanks for the help! It was a lot easier than I was thinking... I guess I was just paranoid about messing up with my brand new "toy". This is definitely a smoother experience than my phone, so far.
Hello,
I am very confused as to whether or not it is possible to go from my rooted US Xoom Wifi only running rooted stock 3.1 directly to the Manta Ray rom, or do I go to stock rooted 3.2 first? Whatever the case, could someone link me to the correct procedure? I cannot find something that matches my exact setup, and the Rom's thread is unclear whether I have to update first. Yes, I know, this is probably a noob question, but I am pretty new to rooting in general.
Does anyone how to do this?
merauder75 said:
Hello,
I am very confused as to whether or not it is possible to go from my rooted US Xoom Wifi only running rooted stock 3.1 directly to the Manta Ray rom, or do I go to stock rooted 3.2 first? Whatever the case, could someone link me to the correct procedure? I cannot find something that matches my exact setup, and the Rom's thread is unclear whether I have to update first. Yes, I know, this is probably a noob question, but I am pretty new to rooting in general.
Does anyone how to do this?
Click to expand...
Click to collapse
Since you're rooted your bootloader is already unlocked
Just flash CWM 3.2.0.0 RC4
Wipe from CWM
Load Tiamat.
It should be that easy.
Ok, so the manta ray package is the whole system image for 3.2? Will it work essentially like an update?
EDIT: Also, just for clarification, I use wipe data/factory reset, and then put the rom on a microSD, then flashing it by doing what, exactly?
merauder75 said:
Ok, so the manta ray package is the whole system image for 3.2? Will it work essentially like an update?
EDIT: Also, just for clarification, I use wipe data/factory reset, and then put the rom on a microSD, then flashing it by doing what, exactly?
Click to expand...
Click to collapse
If you're downloading the Team Tiamat Mantay Ray 2.0.1 ROM - Yes, it includes everything.
You will boot into CWM recovery 3.2.0.0 RC4, do you have that installed? If not, please flash it first.
Then you flash the rom from CWM itself, after booting into CWM. Have the rom zip package on the flash card.
If you need more explicit instructions, they can be pieced together from the CWM thread and the Tiamat rom thread
Alright, got CWM 3.2.0.0 RC4 installed, now, for the part that scares me..Im gonna flash the Tiamat img now.
merauder75 said:
Alright, got CWM 3.2.0.0 RC4 installed, now, for the part that scares me..Im gonna flash the Tiamat img now.
Click to expand...
Click to collapse
dont be scared
wipe first (from recovery menu option)
then load the rom .img
join #xoom on irc.freenode.net if you need help
Any way to upgrade the CWM in Valhalla black to 5.0.2.8 without using another kernel? Right now it is on 5.0.2.7 and I would like to upgrade if possible.
Thanks for any help in advance.
There aren't any BML kernels that use 5.0.2.8 at the moment. Why do you want it.
No particular reason, just wanted to be on the latest version. Thanks for the response.
Actually hampster kernel has cwm 5.0.2.8 (blue cwm) but some users are having issues with nand backups and going to mtd with that kernel.
sent from my batcave
FBis251 said:
There aren't any BML kernels that use 5.0.2.8 at the moment. Why do you want it.
Click to expand...
Click to collapse
FB, why not rebuild the kernel in vb with my new initramfs?
bhundven said:
FB, why not rebuild the kernel in vb with my new initramfs?
Click to expand...
Click to collapse
Added it to my todo list. The thing is that now I really like your CM7 build.sh and am disliking the BML kernel's build.sh. I might just go ahead and do it with anton's kernel since he has a lot of patches already, or he can do it himself.
Does this thing auto-root? I don't see any references to it in your commit history.
FBis251 said:
Added it to my todo list. The thing is that now I really like your CM7 build.sh and am disliking the BML kernel's build.sh. I might just go ahead and do it with anton's kernel since he has a lot of patches already, or he can do it himself.
Does this thing auto-root? I don't see any references to it in your commit history.
Click to expand...
Click to collapse
I looked at CWM briefly, but I don't know much about our phone boot and recovery process. I don't even understand why recovery has to be build for each device individually and cannot use a single binary and some config and script files.
This is the latest source for the touch recovery:
https://github.com/CyanogenMod/android_bootable_recovery
If we can figure how to build and use it I'll include it in the kernel.
Bryan was messing around with getting a build of it going on CM7. Once touch works, it'll be a lot simpler to include it in BML kernels.
FBis251 said:
Bryan was messing around with getting a build of it going on CM7. Once touch works, it'll be a lot simpler to include it in BML kernels.
Click to expand...
Click to collapse
Yup... again
working on it
AntonX said:
I looked at CWM briefly, but I don't know much about our phone boot and recovery process. I don't even understand why recovery has to be build for each device individually and cannot use a single binary and some config and script files.
This is the latest source for the touch recovery:
https://github.com/CyanogenMod/android_bootable_recovery
If we can figure how to build and use it I'll include it in the kernel.
Click to expand...
Click to collapse
This is because the way recovery works is based on the the BoardConfig.mk and other make variables that are specific to the board (like the size of the partitions, other device features that are enabled, etc...)
You don't want to look at the ICS branch. If you want touch recovery, you need to look at the cm-7.2.0 branch... but it has a lot of weird dependencies and as I've said in this forum already... I got a handle on it. I should have something by or on this weekend.
I finally found the kernel that works for my phone with 5.0.2.8 Blue on it. Seems to work good on my phone, but not really sure where I got it from originally. Any way this helps to make the transition easier?
You can flash AntonX's 1.1.3 Kennel and get CWM 5.0.2.8 I'm running it on Valhalla Black..the blue CWM looks really nice.
Compile a CM 10.1 kernel, baseband and kernel unknown.
I'm a beginner. Learning to using CM source compiler kernel, and ROM.
The help of many good-hearted people, such as: AndreiLux and simone201
I can use CM10.1 source to compiled kernel for n7108 now.
However, while normal boot the system. The phone has no signal.
In the settings. Baseband and kernel is unknown.
Who can help me. Or tell me how to solve this problem.
Thank you.
In the annex, I have attached the the adb log when up and running.
wctliu said:
Compile a CM 10.1 kernel, baseband and kernel unknown.
I'm a beginner. Learning to using CM source compiler kernel, and ROM.
The help of many good-hearted people, such as: AndreiLux and simone201
I can use CM10.1 source to compiled kernel for n7108 now.
However, while normal boot the system. The phone has no signal.
In the settings. Baseband and kernel is unknown.
Who can help me. Or tell me how to solve this problem.
Thank you.
In the annex, I have attached the the adb log when up and running.
Click to expand...
Click to collapse
I haven't looked at the logs but my guess is you used n7100 proprietaries instead of the ones from n7108.
Extract the files (filenames here ) from a stock n7108 firmware (you've probably overwritten them on your device already) and recompile.
Make sure you have a modem for n7108 loaded (flash stock firmware with odin to be sure).
victorator said:
I haven't looked at the logs but my guess is you used n7100 proprietaries instead of the ones from n7108.
Extract the files (filenames here ) from a stock n7108 firmware (you've probably overwritten them on your device already) and recompile.
Make sure you have a modem for n7108 loaded (flash stock firmware with odin to be sure).
Click to expand...
Click to collapse
Thank you very much for your reply.
You are a good-hearted people.
I am afraid that is not the problem.
First of all, I use a script to crawl 7108 proprietaries, from my 7108.
Second, because the comparison of 7100 and 7108 the official firmware, only one file difference.
That is, "libsec-ril.so", this file I have also replaced the 7108 version.