Related
Hi everyone.
I'd really like to know the steps to modify, recompile and finally build a kernel zip to flash on our O1.
For instance, I'm downloading the ThunderG Kernel from mik_os here: https://github.com/mik9/ThunderG-Kernel
But I really dont know how to procede.
The programming language seems to be C++, but...
Which compiler should I use to compile it?
The source code is 100+ Mb sized, how can I build the kernel in a simple zip to let me flash it through custom recovery?
I'm really new to all this, I've little experience in C/C++/Java programming, and I'd really like to know how to procede.
An example of initial use I'm interested in, is summing up various fixes from different kernel's and make a unique kernel to flash on my phone.
For the real example:
This: http://forum.xda-developers.com/showthread.php?t=929941
plus this: http://forum.xda-developers.com/showpost.php?p=11166426&postcount=47 (waiting for source from the author)
I'd be really glad to see a newbie (not completely ^^) step-by-step guide doing everything from Windows platform.
I already read other topics on this argument, but none of them had a real guide that could be useful to anyone.
I want to thank you in advance
I'm interested too!
To start with change ur pc os to ubuntu 10.10
ccdreadcc said:
To start with change ur pc os to ubuntu 10.10
Click to expand...
Click to collapse
Couldn't Compiling and building a source code be done from any platform?
As far as I know it should (though I'm not an expert ^^).
I'd like to know if this can be done from Windows, as I'm not planning to change os at the moment
You can always use a Live CD of Ubuntu 10.10.
badeaioan said:
You can always use a Live CD of Ubuntu 10.10.
Click to expand...
Click to collapse
That's not the problem, I already installed Ubuntu other times, but I did a complete format these days and I'm not planning to install it anymore for now.
I still believe that I dont need it to compile a C/C++ source
I'd like to know the steps so I can say it surely.
If Linux is absolutely needed, I just want to know
I thing, that it can be possible compile on other system (cygwin + compilers, library, ...) but you will must download huge dependent software/library/source code. It probably will have same size as whole system :-/
Ok you convinced me, let's say I want to do it on ubuntu, could someone make a guide for everyone?
that would be great!
Sent from my LG-P500 using XDA App
I use gcc for compiling stuff. How to turn the compiled stuff into a package (for flashing) however, is what I don't know
What I would also like to know is how to incorporate a kernel into a ROM. That would shed some light. Thanks to whoever answers this!
The ThunderG package includes a lot of things, do I have to compile the "kernel" folder only to build a kernel for flash?
I really don't know how to procede... ^^
I'm installing Ubuntu 10.10 right now trough wubi..
Sippolo said:
Couldn't Compiling and building a source code be done from any platform?
Click to expand...
Click to collapse
No, especially the kernel source code makes heavily use of filename case sensitivity.
In linux abcd.e and abcD.e are different files- in windows they are not.
Extract a linux Kernel in windows and you will see what I mean.
So even if you got the cross compilers and libs together you will not be able to compile the kernel.
Cygwin is a way- but you could also run XUbuntu with VirtualBox which easier.
The best and fastest is a native linux system.
Sippolo said:
The ThunderG package includes a lot of things, do I have to compile the "kernel" folder only to build a kernel for flash?
Click to expand...
Click to collapse
Get the android ndk, extract it and append the folder with "arm-eabi-gcc" to your system path (export PATH=$PATH:"$NDKPATH/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin").
Extract Thunderg_Kernel.tar.gz, go to the directory and run "make thunderg-perf_defconfig" that will create a .config for the kernel. Or grab your O1 config from /proc/config.gz (per adb, ftp server app, copy with file manager to sd card...) and move it to $kerneldir/.config.
Have a look at "make menuconfig" and then try "make zImage".
Maybe you must install a few dependencies with synaptic (when you are using ubuntu).
kpbotbot said:
I use gcc for compiling stuff. How to turn the compiled stuff into a package (for flashing) however, is what I don't know
What I would also like to know is how to incorporate a kernel into a ROM. That would shed some light. Thanks to whoever answers this!
Click to expand...
Click to collapse
Load mik_os' touchscreen fixed kernel and extract the zip file.
Delete the cert* and manifest* files under META-INF.
Change the zImage under Kernel maybe the kernel modules (system/lib/modules) too.
ZIP it all together again (directory structure must be the same as in mik_os' zip).
To sign read this: http://www.robmcghee.com/android/creating-an-android-update-zip-package/
or this: http://www.londatiga.net/it/how-to-sign-apk-zip-files/
hello, first of all to compile a kernel you need to config this kernel (enabling the drivers you are intersted in, kernel tweaks... and so on)
to do that (on linux) go to your kernel directory and run this command
make menuconfig
this would run the gui config for the kernel where you can configure the kernel.
anyway every board or device has it's own configureations os the kernel can handel the hw on this device you can start gussing what are the right configurations for the P500 which is not an option at all hehehe
or you can use the predefind config included in the Thunderg kernel
to use that config go to the kernel folder and run this command
make thunderg-perf_defconfig
this command will configure the kernel with the predefind configuration
after that you need to compile the kernel using a cross platform compiler, the machine you are working on is x86 but P500 mobile have an ARM cpu so you can't just compile the kernel for your machine and run it on the mobile to do that find a cross compiler on the net (i use the CodeSourcery) then compile your kernel using this command
make CROSS_COMPILE={path to the corss compiler bin}
after finishing the compile process (first time it would take a while) you will find a file called "zImage" which is the kernel for the ARM cpu under the directory arch/arm/boot inside your kernel directory
then to flash that image to your device you need to create your own ROM and sign it then flash it using the coustom recovery.
hopt that this info is useful and sorry for any wrong information
Thanks everyone
I found out that android ndk solution was much easier and straightforward.
Now I've my zImage ready in "ThunderG-Source/arch/arm/boot/" directory (not in the kernel directory as waleedq stated?).
Now I cant understand the meaning of "signing" my kernel to a custom ROM, I'm using the custom recovery from http://forum.xda-developers.com/showthread.php?t=844483
I've read the two articles above about signing an application .apk to your rom and generate an update package.
But here I dont have an apk but a zImage which I really dont know how to use ^^
Isn't there a way to directly create the kernel update zip file and flash it with custom recovery?
P.S. Surfing on the web I found this link, might be useful to someone: part1: http://lazydroid.com/2010/06/how-to-compile-kernel-part-1/ part2: http://lazydroid.com/2010/06/how-to-compile-kernel-part-2/ It just explains what you have already explained though
Sippolo said:
Thanks everyone
I found out that android ndk solution was much easier and straightforward.
Now I've my zImage ready in "ThunderG-Source/arch/arm/boot/" directory (not in the kernel directory as waleedq stated?).
Click to expand...
Click to collapse
Your "kernel" directory has the name "ThunderG-Source"
It is all ok- waleedg didn't mean the "kernel/kernel" directory
Sippolo said:
Isn't there a way to directly create the kernel update zip file and flash it with custom recovery?
Click to expand...
Click to collapse
Read my post more thoroughly (I have edited it)
Yeah I did understand what you wrote in that reply, just was wondering what is "signing" actually, but I found out when doing it
Now I've my signed kernel update to flash
I used the SignApk jar program to do it, it's fast and I've everything already done and ready for future signing (certificate and key must not be remade each time as far as I see, I just need to sign each new zip with the already present certificate/key).
Thank you everyone, now I'm finally done with this request, it's solved
Side Question to waleedq: will you publish the code of your workaround for axis inversion? I'm curious which source file handle these things, should be /drivers/input/touchscreen/mcs6000_ts.c, am I wrong?
Sippolo said:
Yeah I did understand what you wrote in that reply, just was wondering what is "signing" actually, but I found out when doing it
Now I've my signed kernel update to flash
I used the SignApk jar program to do it, it's fast and I've everything already done and ready for future signing (certificate and key must not be remade each time as far as I see, I just need to sign each new zip with the already present certificate/key).
Thank you everyone, now I'm finally done with this request, it's solved
Side Question to waleedq: will you publish the code of your workaround for axis inversion? I'm curious which source file handle these things, should be /drivers/input/touchscreen/mcs6000_ts.c, am I wrong?
Click to expand...
Click to collapse
yes i am publishing the code , today if i got some spare time
and about the mcs6000_ts.c yes this is the driver that handel our screen
here is the workaround source code
https://github.com/waleedq/ThunderG-Kernel/blob/thunderg_oc/drivers/input/touchscreen/mcs6000_ts.c
i just forked nik_os kernel and added my workaround code to it so now all the features are implemented
waleedq said:
here is the workaround source code
https://github.com/waleedq/ThunderG-Kernel/blob/thunderg_oc/drivers/input/touchscreen/mcs6000_ts.c
i just forked nik_os kernel and added my workaround code to it so now all the features are implemented
Click to expand...
Click to collapse
That's perfect, thank you
you are welcome my friend hope that someone will make it better than this stage
Hello everyone, I just recently got Kali Linux installed on my galaxy tab 10.1 (vnc, working on a dual boot) and was wondering how hard it would be to port the 32 bit version of the metasploit framework to arm. I really want to use these tools on my tab, could some show me some of the steps I would need to take to port this? Thanks!
Kobalt.Kitsune said:
Hello everyone, I just recently got Kali Linux installed on my galaxy tab 10.1 (vnc, working on a dual boot) and was wondering how hard it would be to port the 32 bit version of the metasploit framework to arm. I really want to use these tools on my tab, could some show me some of the steps I would need to take to port this? Thanks!
Click to expand...
Click to collapse
Using a complete GNU/Linux distribution (as opposed to Android/Linux), I'd say it's more or less just to compile it. No porting needed.
kuisma said:
Using a complete GNU/Linux distribution (as opposed to Android/Linux), I'd say it's more or less just to compile it. No porting needed.
Click to expand...
Click to collapse
Your right, I was able to install it through the synaptic package manager.
I had the hardest time trying to get the terminal to work though. I kept getting an error saying something about Xterm not being able to find system/bin/sh. I couldn't find the file to change the path to /bin/sh so I ended up just creating a system/bin folder, copying and renaming dash to sh, and placing it in the new directory. Now the console works, but it just shows the hash sign: #. I don't know about this distribution, but when I was using Backtrack and Ubuntu, it would say '[email protected]' or '<username>@ubuntu' something other then just the hash sign... Any thoughts on this?
Kobalt.Kitsune said:
Your right, I was able to install it through the synaptic package manager.
I had the hardest time trying to get the terminal to work though. I kept getting an error saying something about Xterm not being able to find system/bin/sh. I couldn't find the file to change the path to /bin/sh so I ended up just creating a system/bin folder, copying and renaming dash to sh, and placing it in the new directory. Now the console works, but it just shows the hash sign: #. I don't know about this distribution, but when I was using Backtrack and Ubuntu, it would say '[email protected]' or '<username>@ubuntu' something other then just the hash sign... Any thoughts on this?
Click to expand...
Click to collapse
I have no idea what "Xterm" you are trying to run, but most GNU/Linux distributions have replaced it with something different flavored, such as "gnome-terminal", leaving ol' xterm quite butchered. To me, it sounds you've tried to invoke some xterm from the Android world (using a script beginning with the line "#!/system/bin/sh"). Look for the proper terminal instead. I'll bet a virtual peanut it's "gnome-terminal".
Can someone help me with a rootfs build? It was built via the instructions in the gen8 debian wiki. I've copied the kernel from the Angstrom system but it doesn't seem to boot it correctly. The image runs okay in qemu on a debian 6 VM on my laptop. I've attached a pastebin of the startup but I'm not sure why the kernel is failing. I think it's wifi driver related but not 100%. I've loaded the wifi drivers via the wiki as well.
pastebin. com/7Xf7Rhvq
allenelson said:
Can someone help me with a rootfs build? It was built via the instructions in the gen8 debian wiki. I've copied the kernel from the Angstrom system but it doesn't seem to boot it correctly. The image runs okay in qemu on a debian 6 VM on my laptop. I've attached a pastebin of the startup but I'm not sure why the kernel is failing. I think it's wifi driver related but not 100%. I've loaded the wifi drivers via the wiki as well.
pastebin. com/7Xf7Rhvq
Click to expand...
Click to collapse
I don't think it is the wifi, I never tried ubuntu with the 2.6.29 kernel, so wouldn't what the problem is. Kernel panics are not an easy thing to debug. For ubuntu you can also use bootstrap to build your rootfs, alot easier. See http://dev.openaos.org/wiki/LubuntuGen8#a3Buildrootfstarballwithrootstock
You can also follow the complete guide and use the 2.6.37 kernel which is better for ubuntu.
divx118
divx118 said:
I don't think it is the wifi, I never tried ubuntu with the 2.6.29 kernel, so wouldn't what the problem is. Kernel panics are not an easy thing to debug. For ubuntu you can also use bootstrap to build your rootfs, alot easier. See *edited because I cant post urls*
You can also follow the complete guide and use the 2.6.37 kernel which is better for ubuntu.
divx118
Click to expand...
Click to collapse
sorry divx i kind of lied. i didn't follow the guide to a T because the netboot installer fails. it doesn't find the disk if you set the root as /dev/ram, it needs to be /dev/sda with the valid image file.. so essentially i have been debootstrapping the installs but have also used the netboot install images with no success. TBH your name looks familiar, I'm pretty certain I was reading your documentation or maybe posts on here regarding gen8's you've written. but anyway..
my goal is ubuntu-desktop on the tablet. i've been using ubuntu natty as the base because it has desktop and also the armel-installer support (but installing both ways, netboot and bootstrap). i've even failed using older versions of debian. for the latest test i built a tiny 200MB test image with minimal packages installed. they run fine in qemu but die with a kernel panic and the same limited details. :/
as a test i compared the debianlxde floating around to the images i'm making but can't find an issue or difference between them that would cause them to fail. that's why i was hoping something would stick out in that greek error message but i think it's just the developer-os going through the reboot process. just the wifi statements stuck out, i was curious why the driver would even be referenced so early in the boot process of the tablet.
allenelson said:
sorry divx i kind of lied. i didn't follow the guide to a T because the netboot installer fails. it doesn't find the disk if you set the root as /dev/ram, it needs to be /dev/sda with the valid image file.. so essentially i have been debootstrapping the installs but have also used the netboot install images with no success. TBH your name looks familiar, I'm pretty certain I was reading your documentation or maybe posts on here regarding gen8's you've written. but anyway..
my goal is ubuntu-desktop on the tablet. i've been using ubuntu natty as the base because it has desktop and also the armel-installer support (but installing both ways, netboot and bootstrap). i've even failed using older versions of debian. for the latest test i built a tiny 200MB test image with minimal packages installed. they run fine in qemu but die with a kernel panic and the same limited details. :/
as a test i compared the debianlxde floating around to the images i'm making but can't find an issue or difference between them that would cause them to fail. that's why i was hoping something would stick out in that greek error message but i think it's just the developer-os going through the reboot process. just the wifi statements stuck out, i was curious why the driver would even be referenced so early in the boot process of the tablet.
Click to expand...
Click to collapse
I indeed wrote the debian lxde guide and also the one I posted above for lubuntu. For testing if wifi is really your problem or not, just commend out the code to load it. BTW in the pastebin you posted there is nothing to see related to wifi. Did you perhaps mean the "twl4030" messages. IIRC it is has something todo with power supply for usb. To be sure I need to check the code in the kernel, but I know for sure it has nothing todo with wifi.
I still think you would be better of using the 2.6.37 kernel for ubuntu, so follow the guide I posted. Also be aware you have an hd device, this will slow down ubuntu/or any other linux distro. The rootfs is on your hd and there will be a constant need of read/write access, when using a gen8 flash version this will be faster.
Sadly my old gen8 101IT has blown batteries, so I don't use it anymore. However if you have some questions, you can also join #openaos on irc.freenode.net . My irc client is 24/7 online, there also be some other people that maybe can help. Just post your question there with details, then be patient. It can take some hours before you get an answer.
divx118
divx118 said:
I indeed wrote the debian lxde guide and also the one I posted above for lubuntu. For testing if wifi is really your problem or not, just commend out the code to load it. BTW in the pastebin you posted there is nothing to see related to wifi. Did you perhaps mean the "twl4030" messages. IIRC it is has something todo with power supply for usb. To be sure I need to check the code in the kernel, but I know for sure it has nothing todo with wifi.
I still think you would be better of using the 2.6.37 kernel for ubuntu, so follow the guide I posted. Also be aware you have an hd device, this will slow down ubuntu/or any other linux distro. The rootfs is on your hd and there will be a constant need of read/write access, when using a gen8 flash version this will be faster.
Sadly my old gen8 101IT has blown batteries, so I don't use it anymore. However if you have some questions, you can also join #openaos on irc.freenode.net . My irc client is 24/7 online, there also be some other people that maybe can help. Just post your question there with details, then be patient. It can take some hours before you get an answer.
divx118
Click to expand...
Click to collapse
appreciate the feedback sir. i'll give a different kernel a go. yes indeed, the twl4030 message was confusing me, but then again i was seeing it in the shutdown portion after the kernel panic. again thanks, i'll post again if i'm successful.
i'm still tinkering with the thing, trying to find some better ways to debug this. it seems minicom and securecrt dont print everything out. i think it loses the console connection after the image fails to load because if i pull the USB cable in minicom i do see some additional output but it's hard to tell whether or not it's actually in order.
i'm comparing these two pastebins, one from angstrom and one from a wheezy debian image i just created. i put a whitespace where the images succeed/fail. if you have a minute let me know what you think. i'll put the commands below i used to create the wheezy image and copy some angstrom files. it loops the image but isn't loading so i must be missing something fairly simple like the actual boot parameters or root to mount.
angstrom (good) - http://pastebin. com/X3qKDHtG
debian (bad) - http://pastebin. com/pGDDEHGx
root# dd if=/dev/zero of=rootfs.img bs=1M count=1024
mkfs.ext3 rootfs.img
losetup -f rootfs.img
mount /dev/loop0 /mnt/root
debootstrap --arch armel wheezy /mnt/root ftp.us.debian. org/debian
--- debootstrap complete, copy files from saved angstrom image ---
losetup -f angstrom.img
mount /dev/loop1 /mnt/ang
cp -a /mnt/ang/boot/. /mnt/root/boot
cp -a /mnt/ang/media/. /mnt/root/media
cp -a /mnt/ang/dev/. /mnt/root/dev
cp -a /mnt/ang/lib/firmware /mnt/root/lib
cp -a /mnt/ang/lib/modules /mnt/root/lib
cp /mnt/ang/etc/fstab /mnt/root/etc
umount /mnt/ang
umount /mnt/root
losetup -d /dev/loop*
--- plugin archos and enter USB from recovery ---
mount /dev/sda1 /mnt/root
cp rootfs.img /mnt/root
umount /mnt/root
--- reboot archos with serial debugging ---
can someone teach me how to use abootool
i want to extract fastboot command from Huawei mate 7
the instruction in github too little for very novice who have little knowledge in programming like me.
i already install python, download abootool.zip, python-adb.zip. place everything in one folder with my rom img. run python command like suggested in the github but
the error was adb module not found.
maybe some setting not correct.
Welcome to Treble Toolkit, a software that has various tools designed for devices with Project Treble support.
Features:
Treble GSI Flashing, TWRP Flashing, TWRP Booting, Bootloader Unlocker, Permissiver Flasher and FreeCMD (allows you to run your own commands in the Platform Tools included), dynamic theme (adapts to your computer's theme), Partition Erasing and Integrated Updating Service (Annotation 2).
Compatibility:
Treble Toolkit - Supported Operating Systems
Know if your computer is compatible with Treble Toolkit.
youraveragegamer.wixsite.com
Device Compatibility:
Treble Toolkit - Supported Devices
Know if your Android device is compatible with Treble Toolkit.
youraveragegamer.wixsite.com
Screenshots:
Treble Toolkit - Screenshots
Check out some screenshots of Treble Toolkit.
youraveragegamer.wixsite.com
Downloads:
Treble Toolkit - Downloads
Download links for all versions of Treble Toolkit.
youraveragegamer.wixsite.com
Source Code:
Treble Toolkit - Open Source
Download and learn how to build the Treble Toolkit source code.
youraveragegamer.wixsite.com
Update Server (If anyone's curious):
https://www.dropbox.com/home/TrebleToolkitOTA(release.zip and version are for launchers 5.2-5.9 and update.zip and version.txt for launchers 6.0-current)
Hello to all Treble Toolkit users.
Please rate the current 21.9.1 design from 1 to 10 and please leave feedback (if any).
I'm currently taking select user suggestions for future versions of Treble Toolkit to improve even more.
The compatibility list has moved to:
Treble Toolkit - Supported Operating Systems
Know if your computer is compatible with Treble Toolkit.
youraveragegamer.wixsite.com
And:
Treble Toolkit - Supported Devices
Know if your Android device is compatible with Treble Toolkit.
youraveragegamer.wixsite.com
@stevegsames
Very interesting and nice tool. Thx for that.
I can confirm that the flashing of a gsi works with Xperia XZ2 Dual (idk about twrp and bl unlocker; i didn't test it).
I used phhussons android 10 quack gsi for the test. The vbmeta img was the special vbmeta for GSIs.
Two questions:
1. Can you make the tool for Linux?
2. Do this tool supports fastbootd? The newer pixels need this mode to flash system imgs.
Thank you!
I will add the device as a working device and I will start working on a Linux version as I have Ubuntu dual booted in my machine.
stevegsames said:
I will add the device as a working device and I will start working on a Linux version as I have Ubuntu dual booted in my machine.
Click to expand...
Click to collapse
Thx.
What about fastbootd?
Btw if needed i can play the tester for linux and the fastbootd thing because my second pc runs on a debian 10 distro and i'm using a pixel 4 xl as daily device.
PS: Just as friendly suggestion: Your op would be better readable if you make some paragraphs
I´m currently researching that fastbootd thing
dhacke said:
Thx.
What about fastbootd?
Btw if needed i can play the tester for linux and the fastbootd thing because my second pc runs on a debian 10 distro and i'm using a pixel 4 xl as daily device.
Click to expand...
Click to collapse
I didn´t know that even existed, so it might take a few days, same for linux, as I don´t know much about coding in linux.
stevegsames said:
I didn´t know that even existed, so it might take a few days, same for linux, as I don´t know much about coding in linux.
Click to expand...
Click to collapse
No problem. Before a few month i didn't know from it, too. Seems that it is introduced since android 10. So i guess more and more devices will need this mode in the future.
Here's a link for some info. Mayby it helps you someway.
https://source.android.com/devices/bootloader/fastbootd
No problem. Take the time you need.
I researched it
dhacke said:
No problem. Before a few month i didn't know from it, too. Seems that it is introduced since android 10. So i guess more and more devices will need this mode in the future.
Here's a link for some info. Mayby it helps you someway.
https://source.android.com/devices/bootloader/fastbootd
No problem. Take the time you need.
Click to expand...
Click to collapse
Can you test the current version on the pixel? I believe the commands weren´t changed (except for recovery)
stevegsames said:
Can you test the current version on the pixel? I believe the commands weren´t changed (except for recovery)
Click to expand...
Click to collapse
Yes i can. But i will wait with the test until the february sec patch comes because then i flashing anyway.
OK
dhacke said:
Yes i can. But i will wait with the test until the february sec patch comes because then i flashing anyway.
Click to expand...
Click to collapse
Sounds Good
Linux version
dhacke said:
Yes i can. But i will wait with the test until the february sec patch comes because then i flashing anyway.
Click to expand...
Click to collapse
Linux version released
stevegsames said:
Linux version released
Click to expand...
Click to collapse
Great news. I will test it at least for my xz Dual as soon as possible (before february sec patch).
---------- Post added at 08:02 PM ---------- Previous post was at 07:35 PM ----------
Sry but i don't understand how i use it with Linux. I copied the vbmeta file and the system.img into the tool but for what do i need all chmod things?
I have already the plattform tools installed (on my desktop). So in my understanding is should be enough when i copy the folder "Place GSI Files here" into my plattform tool, then copy the "Flash-A-B.sh' and run it in the terminal there.
But the script doesn't run.
Mayby i make something wrong
Update 1:
I tested once more and copied the entire folder of the unzipped GSI Flasher into the plattform tools.
Then opened the terminal there, run chmod 755 Flash-A-B.sh and at least the terminal accept the script.
Nevertheless i get the following errors:
Code:
mv: '1.img' and '1.img' are the same file
mv: The call from stat for '*.img' isn't possible: File or directory not found
mv: '1.img' and '1.img' are the same file
mv: '1.img' and '1.img' are the same file
After that i get errors in the Flash-A-B.sh script at line 18-21 with ''./fastboot: no permission. When i execute the script with sudo it's the same picture.
Update 2:
Finally get the Flash-A-B.sh working. I copy all the necessary files in the root of my plattform tools and copy the script at this place too.
Then i edit it so that i had only the fastboot commands in there. And voila the script runs without any errors.
Idk what you think about it but mayby the Linux version should be changed so that the user needs to copy the files in the plattform tools root, edit the file name in the scripts and just run it in the terminal.
About that?
dhacke said:
Great news. I will test it at least for my xz Dual as soon as possible (before february sec patch).
---------- Post added at 08:02 PM ---------- Previous post was at 07:35 PM ----------
Sry but i don't understand how i use it with Linux. I copied the vbmeta file and the system.img into the tool but for what do i need all chmod things?
I have already the plattform tools installed (on my desktop). So in my understanding is should be enough when i copy the folder "Place GSI Files here" into my plattform tool, then copy the "Flash-A-B.sh' and run it in the terminal there.
But the script doesn't run.
Mayby i make something wrong
Update 1:
I tested once more and copied the entire folder of the unzipped GSI Flasher into the plattform tools.
Then opened the terminal there, run chmod 755 Flash-A-B.sh and at least the terminal accept the script.
Nevertheless i get the following errors:
Code:
mv: '1.img' and '1.img' are the same file
mv: The call from stat for '*.img' isn't possible: File or directory not found
mv: '1.img' and '1.img' are the same file
mv: '1.img' and '1.img' are the same file
After that i get errors in the Flash-A-B.sh script at line 18-21 with ''./fastboot: no permission. When i execute the script with sudo it's the same picture.
Update 2:
Finally get the Flash-A-B.sh working. I copy all the necessary files in the root of my plattform tools, copy the script there too.
Then i edit it so that i had only the fastboot commands in there. And voila the script runs without any errors.
Idk what you think about it but mayby the Linux version should be changed so that the user needs to copy the files in the plattform tools root, edit the file name in the script and just run it in the terminal.
Click to expand...
Click to collapse
You don´t need to do that.
1-cd to the GSI tools
run those commands.
Be careful as some of them have some stuff you need to replace with your info.
Making a toolkit for Linux is a bit of a mixed bag, as there are thousands of distros... I only tested it with Ubuntu... What´s your distro?
As for the "1.img" errors, they are normal, it just means you ran it previously without changing the system.img. No need to worry about those.
Edit: please post your full logs!
Edit 2: The chmods are because this toolkit comes with integrated adb/fastboot (just like in windows)
stevegsames said:
Making a toolkit for Linux is a bit of a mixed bag, as there are thousands of distros... I only tested it with Ubuntu... What´s your distro?
Click to expand...
Click to collapse
Yeah Linux is tricky sometimes. You get a error and first you have no idea why you get it
I picked out the needed fastboot commands for my current gsi devices out of your scripts so i have everything what need atm.
I'm on a debian 10 distro named MX Linux 19.
Can you do the following?
dhacke said:
Yeah Linux is tricky sometimes. You get a error and first you have no idea why you get it
I picked out the needed fastboot commands for my current gsi devices out of your scripts so i have everything what need atm.
I'm on a debian 10 distro named MX Linux 19.
Click to expand...
Click to collapse
Please put the system/boot/vbmeta files and run the toolkit.
After that please confirm that in the system/boot/vbmeta files are named 1.img
And when you run it please attach the full log.
stevegsames said:
Please put the system/boot/vbmeta files and run the toolkit.
After that please confirm that in the system/boot/vbmeta files are named 1.img
And when you run it please attach the full log.
Click to expand...
Click to collapse
Do i need all three files (boot, system, vbmeta) to get the tool working? I'm asking because for example for my xperia xz2 i have only a system and vbmeta.img. No boot.img.
Oh, about that
You do need to have a boot.img, because this formats your current boot partition. I found this article that might help you: https://forum.xda-developers.com/xperia-xz2/help/h8216-stock-boot-image-t3813788
Edit: I Will respond tomorrow, since I gtg to sleep bc it's late here in Portugal...
This cool tool just installed Pixel Experience for me. Fantastic, much better than doing it via TWRP tbh (since the TWRP on my Moto G7 Power frequently has a no touch screen bug. Constantly having to restart TWRP makes it take longer). Thanks for this tool.
I wonder if it could also install GSIs for the E6, which does not have TWRP yet
Yes, you can!
You just need:
-Your phone's boot.img, desired gsi and vbmeta (A/B
or
-Your phone's boot.img and desired gsi (A-Only)
- Unlocked bootloader