KERNEL IS ONLY FOR KUMQUAT. XDA DEVDB SHOWS SOLA ALSO FOR P,U AND GO ! DO NOT CROSSFLASH
Hello.
As we (me and Gava97) built succesfully SlimKat 4.4.2 (we will share it in the next hours) , i would like to share the kernel included in the out folder.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
The kernel contains Team Win Recovery Project but i am not sure that it will work.
Link
1st boot image :- http://d-h.st/uB7
Warning
We'll try to keep this project up with slimkat nightlies but if we see that it's too difficult,we will leave
Flash
Install fastboot drivers
Open flashtool
Flash icon > fastboot mode
Select kernel to flash
Choose dir where you downloaded boot.img
Connect phone in fastboot mode (hold vol up + connecting usb cable)
Choose "Open"
Wait kernel flashes
Boot in cwm (When [IF] showing sony logo,press volume down button continously)
Report us !
Credits
munjeni
New Maclaw
XDA:DevDB Information
[RECOVERY] Team Win Recovery Project [ALPHA], a Kernel for the Sony Xperia Sola
Contributors
DroidModderXtreme, Gava97
Kernel Special Features: TWRP KERNEL
Version Information
Status: Testing
Created 2014-02-19
Last Updated 2014-02-18
DroidModderXtreme said:
XDAevDB Information
[RECOVERY] Team Win Recovery Project [ALPHA], a Kernel for the Sony Xperia Sola
Click to expand...
Click to collapse
Sorry i am not trying to be a troll but this is not for xperia u?!?!?!
@ribben xda shows xsola also for xu,p and go
Tried, but can't access recovery.Stuck on boot logo ( not boot animation).
Sent from XU powered by KitKat.
PuiuMarius2000 said:
Tried, but can't access recovery.Stuck on boot logo ( not boot animation).
Sent from XU powered by KitKat.
Click to expand...
Click to collapse
Thanks for report
Sent from my GT-I9300 using xda app-developers app
DroidModderXtreme said:
Thanks for report
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
the kernel basically works, you can use the device normally. but when trying to access to recovery occurs the bug that @PuiuMarius2000 has said.
Sent from my Xperia U using Tapatalk
What can you say about 3.4 kernel?
I'm not asking for eta, I'm just curious and I want to know if there are problems or not (as I hope)
Thanks
Inviato dal mio Xperia U utilizzando Tapatalk
@alematt we will work on it when slimkat and slimbean will be ready for daily usage
Here you guys go- http://d-h.st/7Ln
This will boot directly in recovery instead of normal booting. If someone just wants to get a taste, you can flash it. Touch is buggy/not-working and this won't boot into system. I know exactly how to fix that but my internet speed is capped. So it'll take sometime for me to fix it but I'm sure of getting this work
Cheers,
AJ
Abhinav2 said:
Here you guys go- http://d-h.st/7Ln
This will boot directly in recovery instead of normal booting. If someone just wants to get a taste, you can flash it. Touch is buggy/not-working and this won't boot into system. I know exactly how to fix that but my internet speed is capped. So it'll take sometime for me to fix it but I'm sure of getting this work
Cheers,
AJ
Click to expand...
Click to collapse
works but must repeatedly pressing the touch menús to access them.
PD: and sometimes this take owned by itself and enter to menu backups jeje
Kobalto07 said:
works but must repeatedly pressing the touch menús to access them.
PD: and sometimes this take owned by itself and enter to menu backups jeje
Click to expand...
Click to collapse
Yes this problem with touch also happens in XGo, XP(don't know about xsola, never tried for it but it will be in it.) But its secondary problem. First thing should be getting this booted correctly. I've made a build which will most probably boot in recovery and normally but I need someone to PM me if they want to try since this could be dangerous. If someone wants PM me but I shouldn't be blamed if something goes wrong. Know how to fix your device.
Cheers,
AJ
Here it is(tested and working)- d-h.st/p2b
It will boot perfectly boot into system.
Will also boot in recovery when power button is pressed.
Added both vibration and led to indicate when power button has to be pressed(LED not tested)
Touch is a complete mess don't complain about it I know about that.
Completely changed the ramdisk structure to make it boot. The original ramdisk has been shrinked to lowest possible size(and recovery has been removed from it instead is triggered differently) and both the original recovery and recovery-ramdisk have been triggered separately with a init script to control the boot and all of that is then packed as the master recovery.
Cleaner way and easier to change recoveries with it. Just replace ramdisk-recovery.cpio with any of your recovery in the same format from any kernel to do so.
Somethings I would appreciate if users can do-
Give the logs in /cache/recovery/
Since touch event logging is not yet enabled yet(I'll enable it later in the source) so I think it'll be hard to fix it for now but I'll do my best.
Check if ADB works in recovery. -> OK not working. Will check it.
If you could help me solve the bugs with touch in any way it'll be nice
Thanks everyone.
Cheers,
AJ
Abhinav2 said:
Here it is(tested and working)- d-h.st/p2b
It will boot perfectly boot into system.
Will also boot in recovery when power button is pressed.
Added both vibration and led to indicate when power button has to be pressed(LED not tested)
Touch is a complete mess don't complain about it I know about that.
Completely changed the ramdisk structure to make it boot. The original ramdisk has been shrinked to lowest possible size(and recovery has been removed from it instead is triggered differently) and both the original recovery and recovery-ramdisk have been triggered separately with a init script to control the boot and all of that is then packed as the master recovery.
Cleaner way and easier to change recoveries with it. Just replace ramdisk-recovery.cpio with any of your recovery in the same format from any kernel to do so.
Somethings I would appreciate if users can do-
Give the logs in /cache/recovery/
Since touch event logging is not yet enabled yet(I'll enable it later in the source) so I think it'll be hard to fix it for now but I'll do my best.
Check if ADB works in recovery. -> OK not working. Will check it.
If you could help me solve the bugs with touch in any way it'll be nice
Thanks everyone.
Cheers,
AJ
Click to expand...
Click to collapse
can i test on slimkat?
Matoxxi said:
can i test on slimkat?
Click to expand...
Click to collapse
It should
Cheers,
AJ
Abhinav2 said:
It should
Cheers,
AJ
Click to expand...
Click to collapse
the device starts well :good: ,and goes well in recovery, but it is a problem that goes by itself to backup menu ( must repeatedly pressing the touch menús to access them too)
Kobalto07 said:
the device starts well :good: ,and goes well in recovery, but it is a problem that goes by itself to backup menu ( must repeatedly pressing the touch menús to access them too)
Click to expand...
Click to collapse
I said I'll work on it And actually it doesn't goes into backup menu but if you observe it closely it keeps on touching the center part of the screen. So it is to be fixed
Cheers,
AJ
@Abhinav2 hit me if you need any sort of help
recovery.log from xperia go
here are recovery.log taken from xperia go twrp (compiled by me). hope it could help
wan5xp said:
here are recovery.log taken from xperia go twrp (compiled by me). hope it could help
Click to expand...
Click to collapse
wan5xp said:
Does anyone have any idea which partition is fotakernel partition?
Click to expand...
Click to collapse
Thanks for log. I'm glad to see that you added touch logging event flag. I had such log from my XP. I'll try to debug it Also I think you are trying the elf extract method the one with FOTA partition. Most probably because your kernel isn't booting to recovery if I'm not wrong. I can help you with that if not already solved. I have the boorec-device and basic structure for kernel ready. Just use the kernel I shared for Xperia U with XGo. Extract the ramdisk and got recovery ramdisk from sbin of your compiled kernel. Extract my kernel and replace ramdisk-recovery.cpio with the one from your kernel(it'll be in gz format. Just extract it to cpio and rename accordingly). Next you can edit bootrec from ramdisk in sbin folder and remove the vibration triggering lines and recovery extracting since I added already in init script and both normal ramdisk and recovery ramdisk will work separately. The lines would look something like this-
Code:
# trigger vibration
echo '200' > /sys/class/timed_output/vibrator/enable
# disable button-backlight
echo '0' > /sys/devices/platform/nmk-i2c.2/i2c-2/2-0040/leds/button-backlight/brightness
# disable LEDs
echo '0' > /sys/devices/platform/nmk-i2c.2/i2c-2/2-0040/leds/red/brightness
echo '0' > /sys/devices/platform/nmk-i2c.2/i2c-2/2-0040/leds/green/brightness
echo '0' > /sys/devices/platform/nmk-i2c.2/i2c-2/2-0040/leds/blue/brightness
cat /dev/input/event2 > /dev/keycheck &
sleep 3
kill -9 $!
if [ -s /dev/keycheck -o -e /cache/recovery/boot ]
then
rm -r /cache/recovery/boot
stop ta_rmt_service
stop rmt_storage
stop tad
stop cspsa
mount -o remount,rw rootfs /
umount -l /system
umount -l /data
umount -l /cache
umount -l /storage
rm -r *.rc
rm -r /etc
rm -r /tmp
mkdir /etc
mkdir /tmp
cd / && gunzip < /sbin/recovery_ramdisk.gz | cpio -i -d
chroot / /init
fi
Optional step for slimming the kernel- Also you can remove recovery_ramdisk.gz from sbin and recovery binary. Then you must also remove everything symlinking to it directly or indirectly as it'll all become useless. If you want I can do that stuff for u
Cheers,
AJ
Do you mind to share your device tree?
Related
I read in the bootloader development thread that it'd reached a level where it could almost boot into a custom system image stored on the SD card. Some questions about that:
1. The creation of that image, is it similar to how it's done for use with the XDAndroid project? (The porting of Android to HTC WinMo devices)
2. Is there a way to avoid having to reflash the device after every attempt? It looks like the boot-scripts take control pretty early in the process so having a choice if you want to proceed would be awesome, especially since I can't figure out how to get hold of a bootlog.
Thanks
ddewbofh said:
1. The creation of that image, is it similar to how it's done for use with the XDAndroid project? (The porting of Android to HTC WinMo devices)
Click to expand...
Click to collapse
I have no clue how they do it for XDAndroid, but here's how I created mine:
dd if=/dev/zero of=rootfs.ext2 bs=1M count=512 (for 512Mb fixed size)
mkfs.ext2 rootfs.ext2 (press y to accept)
mount somewhere
copy your stuff into
umount
ddewbofh said:
2. Is there a way to avoid having to reflash the device after every attempt? It looks like the boot-scripts take control pretty early in the process so having a choice if you want to proceed would be awesome, especially since I can't figure out how to get hold of a bootlog.
Click to expand...
Click to collapse
You don't need to re/flash at all. Pressing any key during the bootup will cancel the script and get you back into old good SE's 1.6
zdzihu said:
You don't need to re/flash at all. Pressing any key during the bootup will cancel the script and get you back into old good SE's 1.6
Click to expand...
Click to collapse
I've tried hammering all the keys without any success, since it works for you maybe I'm doing it at the wrong time. Where in the boot process do you do it?
And thanks for the tip about the image, didn't want to risk messing something up since I had to reflash after every try.
ddewbofh said:
I've tried hammering all the keys without any success, since it works for you maybe I'm doing it at the wrong time. Where in the boot process do you do it?
Click to expand...
Click to collapse
Bash them for a while as soon as you see SE logo appearing
ddewbofh said:
And thanks for the tip about the image, didn't want to risk messing something up since I had to reflash after every try.
Click to expand...
Click to collapse
Make sure you either name your image rootfs.img (not .ext2) or edit the init in the ramdisk accordingly.
Cheers
Thanks, that should make things much, much easier.
zdzihu said:
I have no clue how they do it for XDAndroid, but here's how I created mine:
dd if=/dev/zero of=rootfs.ext2 bs=1M count=512 (for 512Mb fixed size)
mkfs.ext2 rootfs.ext2 (press y to accept)
mount somewhere
copy your stuff into
umount
You don't need to re/flash at all. Pressing any key during the bootup will cancel the script and get you back into old good SE's 1.6
Click to expand...
Click to collapse
is there different form flash?
I've figured out why my phone refuses to go back to normal after testing the chroot. It needs grep and the standard sh doesn't provide it nor is there a grep symlink/binary in /system/bin so I'll add those manually.
Anyways, if anyone has a script or something to do all this it would be very helpful. I'm not looking forward to going over tons of symlinks manually.
ddewbofh said:
I've figured out why my phone refuses to go back to normal after testing the chroot. It needs grep and the standard sh doesn't provide it nor is there a grep symlink/binary in /system/bin so I'll add those manually.
Anyways, if anyone has a script or something to do all this it would be very helpful. I'm not looking forward to going over tons of symlinks manually.
Click to expand...
Click to collapse
How about busybox --install -s /your_destination_dir ?
zdzihu said:
How about busybox --install -s /your_destination_dir ?
Click to expand...
Click to collapse
Awesome, thanks. My knowledge about busybox is limited at best so when I saw install listed as a busybox function I assumed it was the "normal" install command.
In the quest for finding a way to use custom kernels I'm playing around with the splboot module but I need to find a way to get hold of dmesg or kmsg from failed attempts. Is there a reliable way to get any of these logs?
I've tried adding a line in the mount_iso script which cats kmsg to a file right before executing the splboot but I'm seeing nothing that would indicate that I'm running anything but the stock kernel.
Any ideas?
This is only for use on the X10 Mini Pro.
Credits go to nobodyAtall & D4rKn3sSyS for the actual CWM files. Other credits in the README.txt file.
Both version currently use CWM v3.x r5
Windows
Requirements:
Windows PC
USB Cable
Phone driver installed
Android Version 2.1 Stock ROM (2.1.1.A.0.6) (May work on Froyo and Gingerbread ROM's but any custom ROM should have a recovery already installed)
Usage:
You need to set your phone in Debugging Mode.
Connect your phone to your computer
Open up install.bat and follow the instructions inside that.
CWM Usage:
When booting your phone and when the 'Sony Ericsson' letters appear, press and release continuously the 'back' button.
Once you are in the CWM recovery, use the volume keys to navigate upwards / downwards, the 'home' or camera button key to select, the 'back' key to go back.
Last Update:
21-03-2012 v5
Updated Superuser apk and su to version 3.0.7
Replaced SuperOneClick with alternative method
Prefixed relative paths with %~dp0 to complete full paths. This is to combat over zealous group policies. Thanks go to satanselbow
Linux
Requires your phone to be ROOTed but there is now a ROOTer for Linux that can ROOT your phone if not already done. Can be found in this forum.
Requirements:
*nix PC/Laptop
USB Cable
Android Version 2.1 Stock ROM (2.1.1.A.0.6) (May work on Froyo and Gingerbread ROM's but any custom ROM should have a recovery already installed)
Usage:
You need to set your phone in Debugging Mode
Connect your phone to your computer
Open up terminal
Go to the directory it is extracted to
Start the installer by typing "sh cwm-x10minipro.sh"
CWM Usage:
When booting your phone and when the 'Sony Ericsson' letters appear, press and release continuously the 'back' button.
Once you are in the CWM recovery, use the volume keys to navigate upwards / downwards, the 'home' or camera button key to select, the 'back' key to go back.
Last Update:
23-Sept-2011 (v4)
Fixed question about USB Debugging
Fixed permissions on ADB
Links:
Original X10 Mini CWM Thread: http://forum.xda-developers.com/showthread.php?t=1105745
Original X10 Mini Pro CWM Thread: http://forum.xda-developers.com/showthread.php?t=1106146
Changes:
The changes for the latest version are included in the relevant sections above. A more detailed list of changes across all versions is in the CHANGES.txt file that is in the archive file.
Download:
Windows: Download
Linux: Download
Please do not re-host or re-release without permission.
Don't forget if you found this helpful please push the "Thanks" button
copy failed read only file system
is this basically a batch file?
because if so i could port it to linux for you
mopgawka - Did you get the correct mtdblock number. The file would set the system dir as r/w to enable you. The mtdblock number is the number directly after the text mtdblock, in the image below it is 0.
Another question was there an error after the "Getting ROOT rights" text? This was the bit that caused me the most issues.
x10man - Yes it is just basically a batch file. If you want to port to linux then go ahead
ClockWorkMod Recovery Installer for X10 Mini Pro by rect2409.
Requirements and credits are listed in the README.txt file.
Please make sure requirements are met before continuing.
...
..
Для продолжения нажмите любую клавишу . . .
Starting ADB Server if not started.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Getting ROOT rights.
rootsh: permission denied
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Enter the mtdblock number listed "/dev/block/mtdblock? on /system"
Enter mtdblock number: 0
Mount system as R/W.
mount: Operation not permitted
Do you already have a recovery installed? (Y/N):n
Pushing recovery tar file.
failed to copy 'recovery\recovery.tar' to '/system/bin/recovery.tar': Read-only
file system
Pushing chargemon.
failed to copy 'recovery\chargemon' to '/system/bin/chargemon': Read-only file s
ystem
Setting permissions for recovery tar file.
Unable to chmod /system/bin/recovery.tar: Read-only file system
Setting permissions for chargemon.
Unable to chmod /system/bin/chargemon: Read-only file system
Stopping ADB Server.
* server not running *
..
i always rooted
Ok, Currently working on a new version which hopefully fixes your issues.
Thanks I will dl it and take a look later and post the result here
Sent from my U20i using XDA App
how did you root your phone? I also don't have a script called "rootsh". also you can check if you are rooted with "id". many ppl like me are just rooted after entering the shell
also it's better to use "su" when calling commands that have to be done by root: "su - -c 'mount xyz' "
also don't forget the "*" if you check for keyboard inputs (there are people that may miss the key they wanted to push .D)
good luck.
Finnaly! Thank you! Would love to see cwm being imported in the slades kernel, that way we never have to deal with broken files!
Snoopo said:
how did you root your phone? I also don't have a script called "rootsh". also you can check if you are rooted with "id". many ppl like me are just rooted after entering the shell
also it's better to use "su" when calling commands that have to be done by root: "su - -c 'mount xyz' "
also don't forget the "*" if you check for keyboard inputs (there are people that may miss the key they wanted to push .D)
good luck.
Click to expand...
Click to collapse
Yeah I just noticed that i left rootsh in there. Was just something I was playing with.
One thing I hate is Permission Denied error's with adb... Oh fun.
damn. i just did the port and managed to delete the files. DAMN windows temp file thingys anyway tommorow it will be done
TY man u awesome!!!!! thx u all work fine!!!!
rect2409 said:
mopgawka - Did you get the correct mtdblock number. The file would set the system dir as r/w to enable you. The mtdblock number is the number directly after the text mtdblock, in the image below it is 0.
Another question was there an error after the "Getting ROOT rights" text? This was the bit that caused me the most issues.
x10man - Yes it is just basically a batch file. If you want to port to linux then go ahead
Click to expand...
Click to collapse
In linux we used to set the mount point to a variable and then issuing the r/w command. I don't know how you can do this trick in windows.
Code:
mtd=mount | grep system | awk '{print $1}'
echo "Mounting /system rw"
mount -o remount,rw -t yaffs2 $mtd /system
The question about the mount point isnt in the newer version. It just assumes that the system mtdblock is 0.
If it causes a problem in the future I may change it back to selecting the mtdblock number but from all the times I have tried the mtdblock on the x10 mini pro has always been 0.
In windows the answer is just saved as a variable that you assign to the question.
Sent from my X10 Mini Pro using XDA App
Updated with v3.
Just added new way of gaining ROOT access and another check to make sure phone is ROOTed.
EDIT: Oops forgot I had posted last :/ Sorry
3.2.0.0-r3 is old newest is 3.2.0.0-r5
I tried to fix permissions but it's been doing that for almost an hour now... Is that normal, to take that long? Should I remove the battery?
EDIT: Forget it, after looong time waiting, it's finished
EDIT 2: It erased all my preferences! Is that supposed to happen?
I have never had to fix permissions myself so I don't know the process it uses. You could try in the CWM thread where they should be able to help you. Link is http://forum.xda-developers.com/showthread.php?t=1106146
Sorry
quangnhut123 - I don't have that version of CWM and the CWM thread only has r3. If you have r5 then could you give me the files please and will update it.
rect2409 said:
I have never had to fix permissions myself so I don't know the process it uses. You could try in the CWM thread where they should be able to help you. Link is http://forum.xda-developers.com/showthread.php?t=1106146
Sorry
quangnhut123 - I don't have that version of CWM and the CWM thread only has r3. If you have r5 then could you give me the files please and will update it.
Click to expand...
Click to collapse
r5 is the one with multiboot i believe
x10man said:
r5 is the one with multiboot i believe
Click to expand...
Click to collapse
Ahhh. Okay didn't realise that.
Have uploaded a version that includes r5 for the people that have to have the latest... Also kept v3 up as all that has changed is the CWM version.
Ok guys, starting this theard also to find other devs that also are working on porting ubuntu touch to the same device and buildup a team, anyone interested?
So my 1st try was when CM wasn't final release and got stuck at boot, i could connect with adb, but i only got displayed ubuntu and kernel version, and only a few commands worked, this is my 2nd try, so let's hope it will work better this time, also i will put my work on github.
24.NOV.2013:
-Having issues with libstagefright: http://pastebin.com/C8cuCAYA
Not much at rom porting but I'm a strictly linux only user and will help anyway I can. Send me a pm or post where your git is.
Sent from my GT-I9505 using xda app-developers
JustSueMe said:
Not much at rom porting but I'm a strictly linux only user and will help anyway I can. Send me a pm or post where your git is.
Sent from my GT-I9505 using xda app-developers
Click to expand...
Click to collapse
Nice to have people interested in this project, I will get GIT up when I will have it running 1st 13.10 since its stable.
nyl said:
Nice to have people interested in this project, I will get GIT up when I will have it running 1st 13.10 since its stable.
Click to expand...
Click to collapse
Nice I have a dev build env for ubuntu touch but unsure how to pull repo for unknown device. But if u get a build that boots I'm more than eager to work on it
Sent from my GT-I9505 using xda app-developers app
I've tried a few times to get it going for the M919 but each time I can't get past the Samsung Splash screen. I wasn't even able to connect via adb. Granted, I don't exactly know what I'm doing, but I do have a build environment set up and do have a little experience building and debugging builds. I should have time to tinker with it again in a few weeks.
ubuntu build
nyl said:
Nice to have people interested in this project, I will get GIT up when I will have it running 1st 13.10 since its stable.
Click to expand...
Click to collapse
i have a build enviroment made up and pulled repos ect.. i just need to work a few things out before im ready to test it and post on here, if you can point in right direction (if yours boots)
need to do the audio part but can boot without sound in the alpha
neeed to add in apparmor later, can be done later ubuntu should boot without it
brightness, i dont think it matters so much as booting up is priority but i dont seem to have file it wants me to change "device/[manufacturer]/[codename]/init.[codename].rc"
problem with the way fstab has to be setup
within my android source my fstab is "void.fstab" which has lines that look like :
dev_mount sdcard /storage/sdcard1 auto /devices/platform/msm_sdcc.4/mmc_host/mmc2/ /devices/platform/msm_sdcc.2/mmc_host/mmc2/
ubuntu port guide for fstab asks to find a filename like "fstab.jfltexx" and have lines that look like:
/dev/block/platform/omap/omap_hsmmc.1/by-name/EFS /efs ext4 nosuid,nodev,barrier=1
help with fstab will be much appreciated.
then ill make my build ready for testing/debugging + suppose ill upload files output files for others that are interested to use
Try this
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1,errors=panic wait
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noatime,nosuid,nodev,journal_async_commit wait,check
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,journal_async_commit,noauto_da_alloc,errors=panic wait,check,encryptable=footer,length=-16384
# recovery
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults recoveryonly
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults recoveryonly
# vold managed volumes
/devices/platform/msm_sdcc.2/mmc_host/mmc2 auto auto defaults voldmanaged=sdcard1:auto
/devices/platform/msm_hsusb_host/usb auto auto defaults voldmanaged=sda:auto
Yes I used part of that, problem now is compile errors, I have fixed a lot of them which involved discarding some features for the time being.
Boot is the main priority though
Im stuck on a compile errors for shared library, ill attempt this one after I've slept.
Hope fully this is the last error, then ill have a .zip to upload .
Thats some great news ^^
What is the rom size?
Sent from my GT-I9505 using XDA Premium 4 mobile app
coolnessQ said:
Thats some great news ^^
What is the rom size?
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Erm i haven't got a system to flash yet, possibly I could try just getting a boot.img and flashing a ubuntu filesystem but the system modified will be needed to boot fully, in theory I'd only get a shell. I did have a boot.img [seemed to have misplaced it :s , comes out at 7.3mb]
When I've got more time I will go bk to source code and try work out how to solve the errors so I can have boot.img and system.img.
If anyone else is working on this, share problems and solutions With me ti help further the progress.
JustSueMe said:
Erm i haven't got a system to flash yet, possibly I could try just getting a boot.img and flashing a ubuntu filesystem but the system modified will be needed to boot fully, in theory I'd only get a shell. I did have a boot.img [seemed to have misplaced it :s , comes out at 7.3mb]
When I've got more time I will go bk to source code and try work out how to solve the errors so I can have boot.img and system.img.
If anyone else is working on this, share problems and solutions With me ti help further the progress.
Click to expand...
Click to collapse
are you unsing tw stock sources for the kernel? with 7.3mb it almost looks like that.
I have tried porting it before and here is my advise, you really have to look at the errors that it gives you during compiling rather then skipping it, or ignoring it, this is the only way you will get it decently working. the rom itself is only around 100mb if i remember correctly. the ubuntu package is like 400mb on top, but thats all proprietary files so universal.
Im using ubuntu tool.
So sources come from cyanogen's clone with modifications (if thats correct)
Yes I have been fixing errors hence no nfc support, but atm it's a problem with libstagefright [hardware video decoder] I was advised to remove it as not needed to make 1st boot but seems to be hardcoded in there
$ grep -r -H "stagefright" *
JustSueMe said:
Im using ubuntu tool.
So sources come from cyanogen's clone with modifications (if thats correct)
Yes I have been fixing errors hence no nfc support, but atm it's a problem with libstagefright [hardware video decoder] I was advised to remove it as not needed to make 1st boot but seems to be hardcoded in there
$ grep -r -H "stagefright" *
Click to expand...
Click to collapse
Here is the reference :good:
Code:
[email protected] /media/broodplank/linuxdatanew/AOSP-KK/device/samsung $ grep -r 'stagefright' .
./qcom-common/qcom-common.mk: libstagefrighthw \
also if you need clean sources for some particular things just use my repos from AOSP 4.3 (https://github.com/aosp-s4). it only includes the needed commits for jf devices only. way less filled with potential compile breakers like the source of cm.
broodplank1337 said:
Here is the reference :good:
Code:
[email protected] /media/broodplank/linuxdatanew/AOSP-KK/device/samsung $ grep -r 'stagefright' .
./qcom-common/qcom-common.mk: libstagefrighthw \
also if you need clean sources for some particular things just use my repos from AOSP 4.3 (https://github.com/aosp-s4). it only includes the needed commits for jf devices only. way less filled with potential compile breakers like the source of cm.
Click to expand...
Click to collapse
Ah I see this seems to of cleared it up abit for me, im busy today but may get look in at code, if not then tomorrow and clean it up abit and try recompile.
If it looks like a lost cause ill jump over to your git and pull that repo.
Fingers crossed
Sent from my GT-I9505 using xda app-developers app
commit to github so we can all take a look at it
.
..
You need to copy some header files for libstagefright to compile:
cp hardware/qcom/media/mm-core/inc/QCMediaDefs.h frameworks/av/media/libstagefright/
cp hardware/qcom/media/mm-core/inc/QCMetaData.h frameworks/av/media/libstagefright/
cp hardware/qcom/media/mm-
core/inc/QOMX_AudioExtensions.h frameworks/av/media/libstagefright/
cp hardware/qcom/media/mm-core/inc/OMX_QCOMExtns.h frameworks/av/media/libstagefright/
cp hardware/qcom/media/mm-core/inc/QCMediaDefs.h frameworks/av/media/libmediaplayerservice
My cm compiled but it wont boot (after flashing .zip and ubuntu system)
hmm.. did you remove all unecessary APPS? that are only needed by android not ubuntu touch? at you it seems relating to mounting points, something in your source doesn't let the kernel mount the partitions, maybe find a different approach to mount and add it to the source tree.
http://e2fsprogs.sourceforge.net/
everyone with interest in using ubuntu
if your interested in ubuntu touch on jfltexx and want to help
your now in luck
go here http://forum.xda-developers.com/showthread.php?p=48344910#post48344910
there is the download links and a few fixes for connectivity
Here is the link to the AT&T/Tmobile rom download : http://www.androidfilehost.com/?fid=23252070760974893'
Here is the link to the how to site (now instead of the phablet download use the one above) : http://forum.xda-developers.com/showthread.php?t=2564187
Oh and you need to flash the lokidoki zip file if used for AT&T.
Had it working perfectly, it is in extreme alpha, I had the wifi working and sound only works when plugged into headphones.
This should be more than enough to get the rom started up and getting a nice UT running shortly where everything works :3
I am not responsible for whatever happens to you or your device before, during, or after this. :3
Greetings!
I'd like to present a TWRP recovery for the single-sim Xperia X. This release works on Xperia X F5121 and F5122
DISCLAIMER:
I'm not responsible for any damage done to your device. You have been warned.
REQUIREMENTS
Unlocked bootloader
Working ADB and Fastboot (You can get the latest version through Android Studio or by visiting this site)
FEATURES
MTP support
ADB Sideload
Backups and restores almost every partition
Full SELinux support
Working encryption. You can access /data within recovery
NEEDS TESTING
USB-OTG
DOWNLOADS
INSTALLATION
Unlock the bootloader
Download the file
Put the following code in CMD/Terminal:
Code:
fastboot flash recovery twrp-3.1.1-suzu-*.img
//Replace * with the version you want to flash
Unplug the cable
Press Volume Down + Power to activate the recovery. When installed properly, the device should vibrate funnily, purple LED should appear and after a couple of seconds you should see the TWRP screen.
Enjoy!
BUILD
You need to sync the OmniROM and vendor blobs from DonkeyCoyote. You can find my sources on GitHub.
android_device_sony_loire_common
https://github.com/omnirom/android_bootable_recovery/commits/android-7.1
Thanks:
@grayleshy - for initial TWRP
@AndroPlus for some of his flags
OmniROM team for sources
If you find my work useful, consider buying me a cup of coffee
[TWRP] TWRP 3.1.0 for Xperia X
Old OP below:
Team Win Recovery Project 3.1.0
REQUIREMENT:
- Unlocked bootloader
FEATURES:
- MTP support
- USB OTG storage support
- Covers most partitions for nandroid backups
- ADB root
- Full SELinux support
- Support for partition decryption
Download: Dropbox
Installation via the bootloader (Platform-tools (adb & fastboot))
Code:
fastboot flash recovery recovery.img
Running TWRP: turn the phone off, wait 5 seconds, then pinch at the same time the power key and the volume down key until the device vibrates, release the keys. Recovery starts within 5-10 seconds.
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
Special thanks kistigun for testing recovery on the device.
Changelog: twrp.me
TWRP was going on OmniRom 7.1 sources and XperiaDeveloper.
SOURCEs: Suzu; loire; Common.
Nice work! Finally no more decryption problems on the X!
Working well, thanks!
One question ; is it possible to reboot the recovery via twrp reboot menu (or use an app like flashfire /flashify)? When I've tried the phone boots normally instead.
baddesthad said:
One question ; is it possible to reboot the recovery via twrp reboot menu (or use an app like flashfire /flashify)?
Click to expand...
Click to collapse
Unfortunately the reboot Recovery does not work from the specifics of the section, but in the future maybe will be fixed. If I don't find how to fix that button will be removed.
samavar89 said:
Unfortunately the reboot Recovery does not work from the specifics of the section, but in the future maybe will be fixed.
Click to expand...
Click to collapse
Good to know, thanks for clarifying
Is there a difference to the 3.1.0 TWRP recovery from the Poison thread?
Oel said:
Is there a difference to the 3.1.0 TWRP recovery from the Poison thread?
Click to expand...
Click to collapse
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
kistigun said:
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
Click to expand...
Click to collapse
Ah...
Ok, Thanks!
kistigun said:
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
Click to expand...
Click to collapse
No,
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
someone knows a recovery that finally works?
robby.pgn said:
No, don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
Click to expand...
Click to collapse
This problem is strange, please provide a log recovery.
I flashed this on my xperia x dual on nougat 7.0
I can go to recovery but when i try to turn on the phone normally it says "The phone is corrupt and cant be trusted bluh bluh..."
it says press power button to continue but when i press it screen turns off and nothings happens
what should i do?!
Kianush said:
I flashed this on my xperia x dual on nougat 7.0
I can go to recovery but when i try to turn on the phone normally it says "The phone is corrupt and cant be trusted bluh bluh..."
it says press power button to continue but when i press it screen turns off and nothings happens
what should i do?!
Click to expand...
Click to collapse
In Your kernel there is support for DM-Verity and Sony RIC?
it's stock kernel man, I unlocked bootloader and flashed stock nougat for xperia X dual sim
I just wanna root it, if there is any other way pls help me out
-----
btw after this problem i used flashtool to flash system and kernel from stock rom to be able to use my phone again
robby.pgn said:
No,
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
someone knows a recovery that finally works?
Click to expand...
Click to collapse
Kianush said:
it's stock kernel man, I unlocked bootloader and flashed stock nougat for xperia X dual sim
I just wanna root it, if there is any other way pls help me out
-----
btw after this problem i used flashtool to flash system and kernel from stock rom to be able to use my phone again
Click to expand...
Click to collapse
use this tool/guide to make a rooted kernel(and edit DM-Verity and Sony RIC): https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
grayleshy said:
Team Win Recovery Project 3.1.0
Click to expand...
Click to collapse
I've installed and tried this TWRP in my Xperia X with MM. Very nice that it can access the data partition! I did not try to install any zip yet.
Some problems I've seen:
dmesg.log: no output
recovery.log: https://pastebin.com/EwbtuC9q
What is interesting in the output:
Code:
I:cmd: /sbin/exfat-fuse -o big_writes,max_read=131072,max_write=131072 /dev/block/mmcblk1p1 /external_sd
CANNOT LINK EXECUTABLE "sh": cannot locate symbol "__fwrite_chk" referenced by "/sbin/busybox"...
I:exfat-fuse failed to mount with result '', trying vfat
I:Unable to mount '/external_sd'
I:Actual block device: '/dev/block/mmcblk1p1', current file system: 'vfat'
Looks like something is not right with the busybox in the image. Maybe it is that what is causing the external sdcard (in my case in exfat filesystem) not being mounted?
Thanks
robby.pgn said:
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup.
Click to expand...
Click to collapse
This problem is almost resolved, just need to test, but I don't have time to compile recovery. In the test version recovery without decryption, problem solved.
juliompinheiro said:
I've installed and tried this TWRP in my Xperia X with MM. Very nice that it can access the data partition! I did not try to install any zip yet.
Some problems I've seen:
dmesg.log: no output
recovery.log: https://pastebin.com/EwbtuC9q
What is interesting in the output:
Code:
I:cmd: /sbin/exfat-fuse -o big_writes,max_read=131072,max_write=131072 /dev/block/mmcblk1p1 /external_sd
CANNOT LINK EXECUTABLE "sh": cannot locate symbol "__fwrite_chk" referenced by "/sbin/busybox"...
I:exfat-fuse failed to mount with result '', trying vfat
I:Unable to mount '/external_sd'
I:Actual block device: '/dev/block/mmcblk1p1', current file system: 'vfat'
Looks like something is not right with the busybox in the image. Maybe it is that what is causing the external sdcard (in my case in exfat filesystem) not being mounted?
Click to expand...
Click to collapse
This issue failed to reproduce, and yet there is no solution. You the problem is not in Busybox, and something else.
grayleshy said:
Running TWRP: turn the phone off, wait 5 seconds, then pinch at the same time the power key and the volume down key until the device vibrates, release the keys. Recovery starts within 5-10 seconds.
Click to expand...
Click to collapse
For whatever reason I'm not able to boot into TWRP like I should be. I've used the poison version of TWRP before so I know what to do, and yet the phone will just boot normally despite holding volume down and power when off.
I know that TWRP is installed though as I am able to boot to it if I first boot to the bootloader using a USB cable but that is very cumbersome to do though.
grayleshy said:
This issue failed to reproduce, and yet there is no solution. You the problem is not in Busybox, and something else.
Click to expand...
Click to collapse
Clearly for the image available at your dropbox there are some libraries dependency errors, not only for the 'busybox', but also for other binaries that are in /sbin.
I do not know why this issue is only happening on my device since you said you can't reproduce this error. If there is anything I can do to help solve this strange behavior, count on me. I am an advanced linux user, but not too familiar with android specifics.
On latest 333 ROM for UK so that fingerprint scanner works on my Xperia X F5121.
I also modified by kernel/boot so that TWRP doesn't brick (actually boot loop) the device like it did the first time. After using these awesome instructions flashing TWRP recovery from here didn't kill the device any longer: https://forum.xda-developers.com/crossdevice-dev/sony/root-root-stock-firmware-modern-sony-t3558904
I was able to take an early nandroid backup before a bunch of Titanium restores, etc. Now I get stuck at "Backing up data" step and it literally doesn't move to the next file. Attaching an image of where I get stuck. FYI, I do use password encryption on the backup and I did disable MD5 creation... still just stuck.
Next tests are to:
see if the stall is on the same exact file number
try no encryption
do a check disk (fsck) type of repair just in case I have corruption --- on my brand new device
Any suggestions greatly appreciated!
UPDATED:
I only back up Boot, System & Data (the default)
On second attempt it stopped at file 18869 of 22065 --- so it does jump and not consistently stop at a certain file.
I am not responsible for bricked devices,
This is a port of Ubuntu Touch for the LG V20 T-Mobile h918 variant. Not yet stable.
Before install halium-boot.img backup only your boot partition. You can restore your current system after try Ubuntu touch. Ubuntu touch will be install in data partition not in system partition.
Youtube :
Sources:
Kernel:
https://github.com/walidham/android_kernel_lge_msm8996/tree/halium-7.1
Device:
https://github.com/walidham/android_device_lge_h918/tree/halium-7.1
https://github.com/walidham/android_device_lge_msm8996-common/tree/halium-7.1
Manifest file
https://github.com/walidham/lge_manifest/tree/master
Status
Working:
Audio
Calling
SMS
4G
Wifi
GPS
Vibration
Orientation sensor
Missing:
Video recording/decoding
Bluetooth
Flash light
ADB/MTP
Libertine
camera
fingerprint
There are two methods to install Ubuntu Touch
Method 1 : unofficial installation with TWRP
1- Download zip file UT TWRP
2- push it in internal storage or sdcard
3- backup up your current boot partition (to restor it later if you want return to android rom)
4- install zip file, make sure your data partition is ext4 (option if you want fresh install you can wipe data partition)
5- rebbot
Note : password is "1111"
Method 2 : official installation/ hard for newbie
NOTE: As the LGV20 aren't community devices yet, the install process may be a little "non-noobie-friendly"
Install twrp on your device, format data partotion to ext4
Download the latest precompiled system.img and halium-boot.img from : halium-boot
Download the JBB's halium install script
Download either the regular rootfs or the Edge one
While on TWRP:
Code:
halium-install -p ut the_rootfs_you_choose.tar.gz system.img
While on TWRP:
Code:
adb shell 'mkdir /a; mount /data/rootfs.img /a; echo manual | tee /a/etc/init/rsyslog.override; umount /a; sync'
While on TWRP: install halium-boot.img (on boot partition)
Then reboot
Connect to phone with ssh
Code:
ssh [email protected]
When entering in ssh run those commands:
Code:
$ sudo -i
$ mount -o remount,rw /
$ cat /var/lib/lxc/android/rootfs/ueventd*.rc | grep ^/dev | sed -e 's/^\/dev\///' | awk '{printf "ACTION==\"add\", KERNEL==\"%s\", OWNER=\"%s\", GROUP=\"%s\", MODE=\"%s\"\n",$1,$3,$4,$2}' | sed -e 's/\r//' >/etc/udev/rules.d/70-h918.rules
$ reboot
If you want suport this project you can donate
Edited : 03-09-2022 :
Now H910 is supported,
For LG V20, i finished the port for H910, its beta version need more test and fixe bugs.
Download link : https://www.androidfilehost.com/?fid=14871746926876820212
Installatio:
1- backup your data and boot partition. System partition you can take it, we not use it.
2- Download ubuntu-touch-h910-01-01-2020.zip
3- Install the zip
4- Rebbot
excellent sir
Got Camera work, but without video record, just take photo on 12mb max
i want to try ubuntu. can you make more detail about instal ubuntu.
because in step 1 . always like this
not found.
thank you
Tried
Very little would need to be fixed to get me to use this ROM full time. GREAT WORK!!!!!!
Excited to see this rom/OS take off. Got this loaded on my phone, love the OS, but found a few issue (might be my fault).
Slow but mostly usable.
Can't use keyboard in Settings > Accounts. Configuring NextCloud, can't type anything in at all. Would have been way more usable if i could configure the accounts.
Other places didn't toggle keyboard when selecting a text field.
If anyone else is or is not having those issue, please let me know as I might have done something wrong.
Calls, messaging, tethering all work great
Is there a debug that Ubuntu Touch uses. Doesn't look like it uses JournalCTL. I would like to see the issue in the debug if possible to see if there is a way i can help.
AGAIN, GREAT WORK!!! AMAZING STUFF!!!
nickhaven said:
Very little would need to be fixed to get me to use this ROM full time. GREAT WORK!!!!!!
Excited to see this rom/OS take off. Got this loaded on my phone, love the OS, but found a few issue (might be my fault).
Slow but mostly usable.
Can't use keyboard in Settings > Accounts. Configuring NextCloud, can't type anything in at all. Would have been way more usable if i could configure the accounts.
Other places didn't toggle keyboard when selecting a text field.
If anyone else is or is not having those issue, please let me know as I might have done something wrong.
Calls, messaging, tethering all work great
Is there a debug that Ubuntu Touch uses. Doesn't look like it uses JournalCTL. I would like to see the issue in the debug if possible to see if there is a way i can help.
AGAIN, GREAT WORK!!! AMAZING STUFF!!!
Click to expand...
Click to collapse
Can you tell to me how to Input step 1 in twrp?
In my device every want to input halium-boot always not found
nickhaven said:
Very little would need to be fixed to get me to use this ROM full time. GREAT WORK!!!!!!
Excited to see this rom/OS take off. Got this loaded on my phone, love the OS, but found a few issue (might be my fault).
Slow but mostly usable.
Can't use keyboard in Settings > Accounts. Configuring NextCloud, can't type anything in at all. Would have been way more usable if i could configure the accounts.
Other places didn't toggle keyboard when selecting a text field.
If anyone else is or is not having those issue, please let me know as I might have done something wrong.
Calls, messaging, tethering all work great
Is there a debug that Ubuntu Touch uses. Doesn't look like it uses JournalCTL. I would like to see the issue in the debug if possible to see if there is a way i can help.
AGAIN, GREAT WORK!!! AMAZING STUFF!!!
Click to expand...
Click to collapse
try to fix display scalling
1- when system boot connect to the phone via ssh
ssh [email protected]
Code:
sudo -i
cd /etc/ubuntu-touch-session.d
nano h918.conf
add this lines
Code:
GRID_UNIT_PX=29
QTWEBKIT_DPR=2.5
NATIVE_ORIENTATION=portrait
FORM_FACTOR=handset
save file and reboot
For debug
Code:
cat /var/log/syslog
dmesg
sudo /system/bin/logcat
raf21 said:
Can you tell to me how to Input step 1 in twrp?
In my device every want to input halium-boot always not found
Click to expand...
Click to collapse
in twrp, select install -> clique button install image (at the bottom)
select halium-boot.img (you must copie from pc to your phone)
walidham said:
in twrp, select install -> clique button install image (at the bottom)
select halium-boot.img (you must copie from pc to your phone)
Click to expand...
Click to collapse
To input halium-install, use terminal in twrp ? Or use terminal in pc.
Sorry for my english
raf21 said:
To input halium-install, use terminal in twrp ? Or use terminal in pc.
Sorry for my english
Click to expand...
Click to collapse
Look at halium-install link
halium-install is done on a linux pc/livecd/virtual machine that has the following installed
qemu-user-static
qemu-system-arm
e2fsprogs
simg2img
sudo
binfmt-support
Looks like it asks for the phone to be connected via usb as well.
Phoenix591 said:
Look at halium-install link
halium-install is done on a linux pc/livecd/virtual machine that has the following installed
qemu-user-static
qemu-system-arm
e2fsprogs
simg2img
sudo
binfmt-support
Looks like it asks for the phone to be connected via usb as well.
Click to expand...
Click to collapse
i noob in linux
can you make step for install this .... please
iam very interest in ubuntu touch
raf21 said:
To input halium-install, use terminal in twrp ? Or use terminal in pc.
Sorry for my english
Click to expand...
Click to collapse
1- reboot to recovery
2- connect your phone to pc (system ubuntu must be)
3- copy halium-boot.img to interal storage of phone
4- run halium install script
Code:
ex : ./halium-install -p ut ubuntu-touch-hybris-xenial-edge-armhf-rootfs.tar.gz system.img
5-install halium-boot.img with twrp
walidham said:
1- reboot to recovery
2- connect your phone to pc (system ubuntu must be)
3- copy halium-boot.img to interal storage of phone
4- run halium install script
Code:
ex : ./halium-install -p ut ubuntu-touch-hybris-xenial-edge-armhf-rootfs.tar.gz system.img
5-install halium-boot.img with twrp
Click to expand...
Click to collapse
how to run script
every i take halium script in terminal ubuntu always
/home/alienware/Desktop/ubuntu touch/halium-install-master/halium-install.sh' -p
Unsupported post install release! Exiting now
maybe i will try again if anybody can tell to me complete step by step to install ubuntu touch
thank for porting to ubuntu touch to h918
raf21 said:
how to run script
every i take halium script in terminal ubuntu always
/home/alienware/Desktop/ubuntu touch/halium-install-master/halium-install.sh' -p
Unsupported post install release! Exiting now
maybe i will try again if anybody can tell to me complete step by step to install ubuntu touch
thank for porting to ubuntu touch to h918
Click to expand...
Click to collapse
make dot and slash before commande like this ./halium-install.sh
youtub : https://youtu.be/E2FtIR7SUYU
Any chance that this would come to the other LG V20's such as the L997 (sprint)?
Americancosworth said:
Any chance that this would come to the other LG V20's such as the L997 (sprint)?
Click to expand...
Click to collapse
I have just h918, but i can build UT for others variant and i need tester for it.
walidham said:
I have just h918, but i can build UT for others variant and i need tester for it.
Click to expand...
Click to collapse
Can you help me to build Ubuntu touch for us998 lg v30 sir
raf21 said:
Can you help me to build Ubuntu touch for us998 lg v30 sir
Click to expand...
Click to collapse
for help you can join us at telegram
https://t.me/ubports_porting
unofficial installation with TWRP
1- Download zip file UT TWRP
2- push it in internal storage or sdcard
3- backup up your current boot partition (to restor it later if you want return to android rom)
4- install zip file, make sure your data partition is ext4 (option if you want fresh install you can wipe data partition)
5- rebbot