I cannot figure out how to install kexec boot. I have the latest crombi-kk and twrp 2.6.3-that3. I tried running the latest 2.5.6 script as root in android terminal emulator, but I keep running into problems. I can successfully install Kexec blob, however when I try to install Android kexec Kernel I keep getting the same error "You are not running this script from the correct directory. Exiting" (I a have it located on my external sd card in a folder named "TF700t-AKBI-v2.5.6"). I cannot for the life of me figure out how to get passed this. And yes I have experience with linux and I have tons of experience with android and roms and flashing things.
Related
Hi all,
Forgive the noobishness.
I rooted my device using the "One-Click" method found here: http://forum.xda-developers.com/showthread.php?t=1011196. It appears to have flashed the 1.3.0 Tiamat kernel in the process.
I am trying to follow the instructions here to flash the latest 1.4.0 Tiamat kernel: http://forum.xda-developers.com/showthread.php?t=978013
When I went to Mounts & Storage --> Mount USB Storage, I received a pop-up in Windows informing me that I had to format the drive before first use. I tried cancelling that to avoid it, but there was no way around it. I ended up formatting some 3MB drive (although I'm not sure where/what this is.)
I then proceed with the instructions "Drop kernel onto SD card". The problem is, the ZIP is larger than 3MB and won't fit onto the drive that shows up on my PC when I mount the storage as instructed.
Confused as to what I actually "formatted for first use", I actually put an SD Card in the Xoom's reader (even though I don't think it was working yet, which is part of why I want the new kernel), and repeated the 'mount' process. This didn't seem to help at all.
So - where did I go awry? Any advice on where to go from here and how to flash 1.4.0? Thanks in advance.
The easiest way to flash tiamat is to download kernal manager for the market and flash that way.
Jthom203 said:
The easiest way to flash tiamat is to download kernal manager for the market and flash that way.
Click to expand...
Click to collapse
Had no clue such a thing existed. I had to also install Busybox but it seems to have done the trick. Thanks once again for your help!
no worries
I may have spoken too soon. It seems that the method didn't work properly. Kernel Manager says I installed the kernel, but when I go to Settings --> About Tablet, it still shows version 1.3.0 Tiamat kernel.
It also seems to have broken my Wifi Radio, which now says "Error" since the reboot.
Any ideas?
run it one more time. Make sure you hit the more info button to verify the version
How do I run it again? I had verified before that it was the 1.4.0 Kernel in the Info.
When I go back, all it says is "Install" but the button is greyed out.
When I installed BusyBox through the market, I unloaded it to /system/xbin.
Would this explain why WiFi isn't working?
The wifi isn't working because something wasn't pushed right. I would try to flash to 1.3.2 then back up to 1.4.0 if that doesn't work we'll have to manually push the wifi drivers.
Edit :
If you open busybox are you running 1.18.4?
Hey again -
I did as you suggested, flashed down to 1.3.2 then back up to 1.4.0 via Kernel Manager. I should note that each time I flashed, to whichever version, I had to activate the device for the 3G radio to work.
After doing this, Wifi still isn't working. In About Tablet, Kernel Version is showing up as "2.6.36.3Tiamat_Xoom-v1.3.0-g5019ece-dirty [email protected] #3".
I am going to have to call it a night but any/all info you can post, I will read in the AM. Thanks again for answering these questions.
Ok this is what i would try next. Go here and down load the 1.3.1 kernel: http://forum.xda-developers.com/showpost.php?p=11798679&postcount=2 copy and paste these commands:
Code:
1. Reboot into the bootloader by running:
adb reboot bootloader
2. Flash the boot image to your boot partition, then boot back into Android by running:
fastboot flash boot boot.img
fastboot reboot
3. Push the bcm4329.ko, scsi_wait_scan.ko, and any other modules to your /system/lib/modules folder and reboot.
adb remount
adb push bcm4329.ko /system/lib/modules/bcm4329.ko
adb push tun.ko /system/lib/modules/tun.ko
adb push scsi_wait_scan.ko /system/lib/modules/scsi_wait_scan.ko
adb push cifs.ko /system/lib/modules/cifs.ko
adb push vold.fstab /system/etc/vold.fstab
adb reboot
NOTE: Special Instructions for 1.3.1
You have to manually make a new directory called "sdcard2" inside "sdcard" prior to flashing. Either use your file explorer of choice or...
Code:
adb shell
mkdir /data/media/sdcard2
exit
CREDIT FOR Flashing Instructions Template goes to coolbho3000
This will enable your sdcard slot. Then you can download the zip 1.4.0 and put it onto you sdcard and flash through clock work recovery
I wonder what exactly you formatted? I don't think the actual SD card will pop up in windows explorer unless you run a script that enables it for USB.
Make sure the sdcard2 folder is in the root xoom folder in windows explorer (or the sd folder in the Xoom explorer), flash down to 1.31, push the five files then flash CWM. If done correctly CWM can mount the actual sd card on its own and you can install 1.40 there.
I reverted to 1.3.1 and the Wifi radio is now fixed. Thanks!
I created the sdcard2 folder, and now have to go scrounge up a microSD.
So, where ought I place the Tiamat_Xoom-v1.4.0.zip? I'm assuming it goes on the sdcard2 folder when I mount the USB storage via CWM? Or do I need to push it to /data/media/sdcard2 via ADB?
EDIT: all figured out now. Thanks to all for your help!
Please note: the 1.4.0 kernel through Kernel Manager is bunk! At least as of last night! Flashing through CWM did the trick, but I had to flash 1.3.1 first...
volta said:
Please note: the 1.4.0 kernel through Kernel Manager is bunk! At least as of last night! Flashing through CWM did the trick, but I had to flash 1.3.1 first...
Click to expand...
Click to collapse
It might have to do with the fact that the sdcard was not yet functional on your xoom. I started flashing at 1.3.0 and flashed as BRD was releasing stable kernels. So by the time 1.4.0 was released i was all ready on 1.3.2 and Kernal manager worked great for me. But i am glad you were able to get everything working, and enjoy 1.4.0 BRD is doing some excellent work.
Hi. I just installed Cyanogenmod 10.2 on my tf300t along with cifs-manager and when trying to mount some shared folder, I get an "unknown device" error message.
I tried several solutions to this issue.
As lsmod only returns two modules, I first tried to find and copy some cifs.ko and other cifs related modules into /system/lib/modules - got a read only error and I'm not even sure if the modules I found will work with my current kernel (3.1.10-g47ec43e)
I also tried to install an android 4.3 kernel from the following thread: http://forum.xda-developers.com/showthread.php?t=2107224
Flashed it via twrp, wiped dalvik cache, no effect: still cannot mount in cifs-manager (haven't tried mounting directly from command line atm) and oddly, uname -a yields the same kernel version: 3.1.10-g47ec43e (is there anything special I must do when flashing a kernel?)
So here are my questions:
1. Why aren't the cifs modules included in Cyanogenmod as they were before? (if I recall correctly, 10.1 had no such problem).
1.1: Will they get included?
2. Where can I find the proper cifs modules for tf300t, kernel 3.1.10?
2.1: How can I bypass this "read-only" error I'm getting and copy the modules to the right place?
3. Where can I find a kernel build that would perhaps already include the cifs modules?
3.1: What are the precise steps to perform when trying to flash a kernel via TWRP, is marking the .zip file containing the kernel for installation, installing and wiping cache sufficent?
An answer to any of the above questions will be greatly appreciated!
Thanks!
This thread popped up fron a seemingly unrelated google search but I think I can give you a couple hints in case you still haven't figured it out:
1.Cyanogenmod decided to disable module support in the kernel for some reason.
1.1 probably not
2. you need to build a kernel with CONFIG_MODULES=y and CONFIG_CIFS=m, or directly CONFIG_CIFS=y so that you won' need to load a module
2.1 remount system with write support: either with "adb remount" or "mount -o rw,remount /system" from terminal
3. build it yourself or ask someone who makes his own cm build to do it for you
3.1 replace the boot.img from any kernel cwm zip you can find with 7zip; wiping caches is not necessary.
I'm trying to get an SSH server running on touchwiz adopting following instructions: https://alainwolf.ch/tech-talk/ssh-cyanogenmod/ . Touchwiz comes without ssh binaries, but I could run the ones copied from CM. The rest of instructions seem to be working as well. However, no matter how hard I try, I cannot figure out where do I inject a startup script. I tried both /data/local/userinit.d/ and /system/etc/init.d . None of locations auto-execute scripts on boot in 4.4. Anyone can help?
Most OEM kernels have startup scripts disabled, in my experience. Try using something like this app (safer) or this (could softbrick your device). You could also flash a custom kernel, as most have init.d support built in.
Hello there, I flashed the KatKernel for Android 5.0, moved the Linux folders into the /data/media/linux folder. The dual boot works great, it boots into XUbuntu, I managed to get the Wifi and the sound work allthough the sound volume is a little low. I also noticed that I have lag when playing hd videos but this isnt't the point. The problem is the Android. It boots into Android but it became unusable as I constantly get errors like Launcher3 stopped working or googleplayservices stopped working. I have CM 12 and XUbuntu. How can I get the Android to work again and still be able to boot into Ubuntu?
niemand_23 said:
... How can I get the Android to work again and still be able to boot into Ubuntu?
Click to expand...
Click to collapse
Did You tried kexecboot kernel? You need to replace android kernel inside archive. To do so You should extract blob file from CM12 firmware and then unpack them with androidroot blobtools and boottools. If You use windows minimal set in attach. First of all drop blob on blobunpack.exe to get <blob_name>.LNX file. Then drop <blob_name>.LNX on bootunpack.exe to get <blob_name>.LNX-ramdisk.cpio.gz and <blob_name>.LNX-kernel.gz. Now rename <blob_name>.LNX-ramdisk.cpio.gz to initrd.img and <blob_name>.LNX-kernel.gz to zImage and replace similar files inside archive in system/boot directory.
Graiden05 said:
Did You tried kexecboot kernel? You need to replace android kernel inside archive. To do so You should extract blob file from CM12 firmware and then unpack them with androidroot blobtools and boottools. If You use windows minimal set in attach. First of all drop blob on blobunpack.exe to get <blob_name>.LNX file. Then drop <blob_name>.LNX on bootunpack.exe to get <blob_name>.LNX-ramdisk.cpio.gz and <blob_name>.LNX-kernel.gz. Now rename <blob_name>.LNX-ramdisk.cpio.gz to initrd.img and <blob_name>.LNX-kernel.gz to zImage and replace similar files inside archive in system/boot directory.
Click to expand...
Click to collapse
Quick question: Would it be easier if I do a full wipe, install KatKiss-5.0_TF300T_017 and then install DB_katkern18_50? I am asking this becaus e I want to perform a clean installation of a new Android Rom and KatKiss doesn't seem that bad. What do you think?
niemand_23 said:
Quick question: Would it be easier if I do a full wipe, install KatKiss-5.0_TF300T_017 and then install DB_katkern18_50? I am asking this becaus e I want to perform a clean installation of a new Android Rom and KatKiss doesn't seem that bad. What do you think?
Click to expand...
Click to collapse
Possibly yes. Dualboot kernel is much closer to original boot method but it have one disadvantage - it's really hard to keep it up to date. So I don't know if curent KatKiss uses same kernel source as dualboot kernel, but it shouldn't cause any big issues.
Graiden05 said:
Possibly yes. Dualboot kernel is much closer to original boot method but it have one disadvantage - it's really hard to keep it up to date. So I don't know if curent KatKiss uses same kernel source as dualboot kernel, but it shouldn't cause any big issues.
Click to expand...
Click to collapse
I flashed the KatKiss Rom and then the KatKernel for DualBoot, the Android works now but it wont't boot into XUbuntu any more. I get the following errors:
*Setting up X socket directories...
start-stop-daemon: unable to start /usr/sbin/kerneloops (Permission denied)
*speech-dispatcher disabled: edit /etc/default/speech-dispatcher
saned disabled: edit /etc/default/saned
What seems to be the problem?
niemand_23 said:
I flashed the KatKiss Rom and then the KatKernel for DualBoot, the Android works now but it wont't boot into XUbuntu any more. I get the following errors:
*Setting up X socket directories...
start-stop-daemon: unable to start /usr/sbin/kerneloops (Permission denied)
*speech-dispatcher disabled: edit /etc/default/speech-dispatcher
saned disabled: edit /etc/default/saned
What seems to be the problem?
Click to expand...
Click to collapse
May be permissions was overwritten during ROM installation.
Graiden05 said:
May be permissions was overwritten during ROM installation.
Click to expand...
Click to collapse
So what now? How can I restore the permissions? It is very weird because back when I had CM 12 and the dual boot kernel it would boot into XUbuntu without any issue but the Android wasn' t working anymore. Now after i flashed the KatKiss Rom and then the dual boot kernel again, it won' t boot into XUbuntu anymore. Has anyone magaged to have a fully working dual boot (Android 5.0 and XUbuntu) ?
niemand_23 said:
So what now? How can I restore the permissions? It is very weird because back when I had CM 12 and the dual boot kernel it would boot into XUbuntu without any issue but the Android wasn' t working anymore. Now after i flashed the KatKiss Rom and then the dual boot kernel again, it won' t boot into XUbuntu anymore. Has anyone magaged to have a fully working dual boot (Android 5.0 and XUbuntu) ?
Click to expand...
Click to collapse
Just a dumb question... Where exactly did you find the dual boot Katkernel? I've looked pretty much everywhere and still no luck for me.
Mich3lin said:
Just a dumb question... Where exactly did you find the dual boot Katkernel? I've looked pretty much everywhere and still no luck for me.
Click to expand...
Click to collapse
This is where I got the dual boot kernel from: http://forum.xda-developers.com/showpost.php?p=57927124&postcount=556 (it's the 5.0 experimental one). I just don't understand why it won't boot into XUbuntu anymore now that I have the KatKiss Rom. Back when I got CM 12, it had no issues, the Android wouldn't work though.
It allways stops at this:
*Setting up X socket directories...
start-stop-daemon: unable to start /usr/sbin/kerneloops (Permission denied)
*speech-dispatcher disabled: edit /etc/default/speech-dispatcher
saned disabled: edit /etc/default/saned
niemand_23 said:
This is where I got the dual boot kernel from: http://forum.xda-developers.com/showpost.php?p=57927124&postcount=556 (it's the 5.0 experimental one). I just don't understand why it won't boot into XUbuntu anymore now that I have the KatKiss Rom. Back when I got CM 12, it had no issues, the Android wouldn't work though.
It allways stops at this:
*Setting up X socket directories...
start-stop-daemon: unable to start /usr/sbin/kerneloops (Permission denied)
*speech-dispatcher disabled: edit /etc/default/speech-dispatcher
saned disabled: edit /etc/default/saned
Click to expand...
Click to collapse
So, I finally had time to try this kernel and it works! Boots just fine into Katkiss ROM and Ubuntu, though I have not used my own rootfs, instead I used img file for our sibling TF700 https://goo.im/devs/rabits/tf700/rootfs.img.7z.zip/. Wifi works, though I couldn't connect...
If I'll have time I'll try to build my own rootfs and report back.
Mich3lin said:
So, I finally had time to try this kernel and it works! Boots just fine into Katkiss ROM and Ubuntu, though I have not used my own rootfs, instead I used img file for our sibling TF700 https://goo.im/devs/rabits/tf700/rootfs.img.7z.zip/. Wifi works, though I couldn't connect...
If I'll have time I'll try to build my own rootfs and report back.
Click to expand...
Click to collapse
Surprisingly , Ubuntu boots fine from the img file, but directly doesn't work. This is odd. Has anyone got a full working rootfs.img ?
@Mich3lin in order to make the wifi work open up a terminal session and type following (password for sudo is ubuntu):
sudo groupadd -r -g 3003 inet
sudo groupadd -r -g 3004 netraw
sudo groupadd -r -g 3005 netadmin
sudo adduser ubuntu inet
sudo adduser ubuntu netraw
sudo adduser ubuntu netadmin
Afterwards, log out and log in again. Now the wifi should work.
The audio works only on the headphones and the volume is kinda low. I really don't know how to make the speakers work.
The key mappings have some bugs. The volume buttons don't work properly. Instead of turning up or down the volume, it takes a screenshot.
I tried to install LibreOffice but I cannot install anything as I keep getting the error unsolved broken packages.
Hey everyone
I am working on a dual boot Ubuntu Touch, Droidian (mobian-hybris) setup without breaking either of the systems. I have figured everything out on how everything should work and modifications that need to be done to the recovery image but there is one question that i do not have an answer for but here is some information but how things work.
So right now Ubuntu Touch uses a customized version of LineageOS recovery to do OTA updates. and is when installed it replaces androids rootfs. Then we have Droidian which uses a rootfs.img file as its rootfs which is mounted at boot as a loop device. (file is placed in /data)
They use different kernels because they have different ramdisks (obviously). My plan is to write a desktop file in both OSes to create a file to let recovery know to flash the right kernel (kernels will be placed under /data aswell no space limitations). I have the recovery and desktop file code mostly ready the only remaining thing is the command to flash a kernel.img/boot.img file to the device (Redmi Note 9S)
I know that LineageOS does not have a terminal all of the flashing tasks will be done by a script which checks which kernel should be flashed.
Is there some documentation on this? Because TWRP can do the same and TWRP is just a GUI on top of the android shell with some added functionality for backups and such.
Any response is appreciated.
FakeShell said:
Hey everyone
I am working on a dual boot Ubuntu Touch, Droidian (mobian-hybris) setup without breaking either of the systems. I have figured everything out on how everything should work and modifications that need to be done to the recovery image but there is one question that i do not have an answer for but here is some information but how things work.
So right now Ubuntu Touch uses a customized version of LineageOS recovery to do OTA updates. and is when installed it replaces androids rootfs. Then we have Droidian which uses a rootfs.img file as its rootfs which is mounted at boot as a loop device. (file is placed in /data)
They use different kernels because they have different ramdisks (obviously). My plan is to write a desktop file in both OSes to create a file to let recovery know to flash the right kernel (kernels will be placed under /data aswell no space limitations). I have the recovery and desktop file code mostly ready the only remaining thing is the command to flash a kernel.img/boot.img file to the device (Redmi Note 9S)
I know that LineageOS does not have a terminal all of the flashing tasks will be done by a script which checks which kernel should be flashed.
Is there some documentation on this? Because TWRP can do the same and TWRP is just a GUI on top of the android shell with some added functionality for backups and such.
Any response is appreciated.
Click to expand...
Click to collapse
Answering my question as the answer was just too dumb but for some reason i could not figure it out.
dd can be used like a regular linux machine
dd if=/data/boot.img of=/dev/block/platform/soc/by-name/boot
Closing down
I kinda had the same issue here: https://forum.xda-developers.com/t/...wrp-openrecoveryscript.4301279/#post-85681605
I remember that I read somewhere / was told actually not to use /dev/block/platform/soc/by-name/boot (which is a symlink) but the actual device path the symlink resolves to with dd.
I'm not sure what the reasoning was though. I'd like to mention this here, maybe someone knows why.