Native linux for Samsung GT-i9105 Galaxy S II Plus
After all this u will loose your external sdcard data
We need:
I. SDcard with at least 4 GB
II. Samsung GT-i9105 Galaxy S II Plus
1. Download and put to the root of your internal sdcard ubuntu-i9105_by-sssemil.tar.gz (910,96 Mb)
2. Now type in terminal emulator:
Code:
su
mke2fs /dev/block/mmcblk1p1
mount -o rw -t ext2 /dev/block/mmcblk1p1 /root
cd /root
tar -xzvf /storage/sdcard0/ubuntu-i9105_by-sssemil.tar.gz
Wait....
3. Now type:
Code:
sync
cat /root/deb_ext2_swa_k1p1.img > /dev/block/mmcblk0p6
sync
4. Done! Now to reboot to ubuntu type:
Code:
su -c reboot recovery
And to reboot to android just reboot ubuntu.
If ubuntu is not booting just remove sdcard and boot without it!
Working:
Wi-Fi
Partly sound
Touchscreen
etc.
Not working:
Camera
Ril stuff
...
suleymanovemil8 said:
Native linux for Samsung GT-i9105 Galaxy S II Plus
After all this u will loose your external sdcard data
We need:
I. SDcard with at least 4 GB
II. Samsung GT-i9105 Galaxy S II Plus
1. Download and put to the root of your internal sdcard ubuntu-i9105_by-sssemil.tar.gz (910,96 Mb)
2. Now type in terminal emulator:
Code:
su
mke2fs /dev/block/mmcblk1p1
mount -o rw -t ext2 /dev/block/mmcblk1p1 /root
cd /root
tar -xzvf /storage/sdcard0/ubuntu-i9105_by-sssemil.tar.gz
Wait....
3. Now type:
Code:
sync
cat /root/deb_ext2_swa_k1p1.img > /dev/block/mmcblk0p6
sync
4. Done! Now to reboot to ubuntu type:
Code:
su -c reboot recovery
And to reboot to android just reboot ubuntu.
If ubuntu is not booting just remove sdcard and boot without it!
Working:
Wi-Fi
Partly sound
Touchscreen
etc.
Not working:
Camera
Ril stuff
...
Click to expand...
Click to collapse
what happen to ur cm10.1 for i9105 thread? u build ur own or source from skullface's(the bugs are the same)
nickchk said:
what happen to ur cm10.1 for i9105 thread? u build ur own or source from skullface's(the bugs are the same)
Click to expand...
Click to collapse
I used skulface`s device source as base(forgot about credits)
S2 Plus 9015
suleymanovemil8 said:
I used skulface`s device source as base(forgot about credits)
Click to expand...
Click to collapse
Can work on S2 Plus 9105P too?
thanks
haky 86 said:
Can work on S2 Plus 9105P too?
thanks
Click to expand...
Click to collapse
Try that method :
1. Flash Custom Recovery(CWM/TWRT) for 9105
2. Flash this ubuntu build
3. Wipe cache,data and dalvik(optional)
4. Reboot system
what about bugs ?
Can you Post Screen Shot and Video ! and what about Bugs ?
Oh man, if some1 can confirm this with screenshots or even just a few words that it is working on GT-i9105P, I would love to try it out even if RIL doesn't work!
SethPDA said:
Oh man, if some1 can confirm this with screenshots or even just a few words that it is working on GT-i9105P, I would love to try it out even if RIL doesn't work!
Click to expand...
Click to collapse
You can see if it's working by simply flashing custom recovery for 9105 and then flash this build through it
OK
I can try it on my phone but is still new only 2 days of life and i have to say is a good phone however can i reflash stock firmware without losing warranty? thanks
:good:
haky 86 said:
I can try it on my phone but is still new only 2 days of life and i have to say is a good phone however can i reflash stock firmware without losing warranty? thanks
:good:
Click to expand...
Click to collapse
Yes :good:
You can flash stock roms via ODIN
DenisRonaldo798 said:
Yes :good:
You can flash stock roms via ODIN
Click to expand...
Click to collapse
if iam wrong is a native system not ubuntu touch?
haky 86 said:
if iam wrong is a native system not ubuntu touch?
Click to expand...
Click to collapse
I didn't try it.I'm not interesting in this rom.I'm using CM11 and everything is nice
About the warranty you should reset the countery bin(using triangle away*100%safe and working app*) and then flash the stock rom
Can some1 please upload this somewhere else? Downloading from turbobit is very very slow.
Maybe mega.co.nz please?
hi
the diffrence between original rom and costum rom ?
pretfish said:
the diffrence between original rom and costum rom ?
Click to expand...
Click to collapse
You can use google for that....but ok i'll give you some examples with galaxy s2+:
More Free RAM than the stock roms which are using TouchWiz
Faster and smoother than the stock.You can easily find the differences if you try custom rom
Higher benchmark score
They are pre-rooted
And custom roms gives you the possibility to have the latest Android version if your phone doesn't have official one which is the best reason to have custom rom
Custom roms can be customized a lot and easy+they have a lot of features which stocks doesn't have
Some of the customs are better for gaming(if you are using your phone for gaming)
Some custom roms have the possibility to control the minimum and maximum CPU frequency(overcloack) but in others you will need a custom kernel.
I think that these are the main reasons to try a custom rom or custom kernel(optional)
The choise is yours
Is that ubuntu phone?
Not sure
lukypuie said:
Is that ubuntu phone?
Click to expand...
Click to collapse
I am not sure this one is an ubuntu touch however i'll upload the file into another file hosting like google drive because i still downloading (2 hours and finish)
haky 86 said:
I am not sure this one is an ubuntu touch however i'll upload the file into another file hosting like google drive because i still downloading (2 hours and finish)
Click to expand...
Click to collapse
Mega is the best.
Anyway, sorry, I meant Ubuntu Touch instead of Ubuntu phone *
So, it's Ubuntu touch?
Not Sure
lukypuie said:
Mega is the best.
Anyway, sorry, I meant Ubuntu Touch instead of Ubuntu phone *
So, it's Ubuntu touch?
Click to expand...
Click to collapse
I don't so this rom is Ubuntu Touch btw, i try to install it on i9105P i guess is same way for i9105 too i rename the archive into u.tar.gz to be short, any one can help me, thanks.
Ok, i've searched around the web and i've found the "original" thread (in a russian forum) and there was two videos about this "rom"
And no, is Debian, not ubuntu touch
https://www.youtube.com/watch?v=FsAYdFTfuqA
https://www.youtube.com/watch?v=LJ0FmwhdnDU
Related
Froyo 2.2.2 port for Huawei U8120.
Maybe it will work on Huawei U8100/U8110 series, but for now it is focused on U8120.
So I dont know what behavior has on U8100 etc.
I must say a big thanks to Tom_G for his awesome work, especially for his froyo port on pulse.Without his work and his posts
on modaco forum, I will not be able to accomplish this.
kalt kaffe's 2.6.29 kernel.
Android 2.2.2 from aosp with some codeaurora changes.
JIT enabled.
Working:
RIL
Audio
GPS
Bluetooth
Wifi
SD card
Sensors
TSCalibration from codeaurora(still the app needs some improvements.For now use a stick or pen when you calibrate the screen)
Not working/bugs:
camera
broken layout on dialer
sdcard cannot be mounted in pc
Its still under development.This is not a finished rom and its not fully tested.
Probably it has problems that I have not yet encountered.So I would not suggest you to try it,
except if you have some experience and you want to help.
I have tried to make it as plain and simple as it gets.No google apps, no bootanimation etc.When all bugs are fixed then I will include them or I will post
my rom.But there are guys that are more expert in rom cooking than me.
Here is a zip with already compiled image files if someone wants to try it and post any bugs/fixes that have found.I have also uploaded here gapps if someone wants them(gmail,market etc)
Code: https://github.com/tas0s
Device tree: https://github.com/tas0s/android_device_huawei_u8120
Try it at your own risk.
Im not responsible for any damage that this may cause.
v.1 initial build
How to build it:
- Install git and gpg (gnupg).
- Download repo - http://source.android.com/source/git-repo.html
$ mkdir android
$ cd android
$ repo init -u https://github.com/tas0s/platform_manifest.git
$ repo sync
- Extract necessary binaries
Some compiled code from the official eclair roms is re-used in froyo. Because some of this code is not opensources I cannot included in the git repository.
The files can be extracted from any u8120 eclair rom.
Place the rom zip in the android directory an rename it to u8120_update.zip
navigate to /device/huawei/u8120:
cd device/huawei/u8120
Then execute from the android directory
$sh device/huawei/u8120/unzip_files.sh
else you can extract them from a working u8120 phone with an eclair rom (check that adb is enabled)
$device/huawei/u8120/extract_files.sh
- Building the system
Once thats done you can start compiling.
Follow the aosp instructions on setting up the build environment. - http://source.android.com/source/download.html
After the environment is setup.
$ cd android
$ source build/envsetup.sh
$ lunch
Select the device u8120.
$ make
I recommend using multiple threads for make if you have a multi core/processor system. By default make will use
1 thread (-j1), set it to use 2*NumberOfCPUsAvailable (so on my dual core -j4). Reducing the number of threads used will reduce the impact on
system performance while the build is running.
The output will be image files in {buildroot}/out/target/product/u8120/. Flash with fastboot.
$ fastboot flash boot out/target/product/u8120/boot.img
$ fastboot flash system out/target/product/u8120/system.img
$ fastboot flash userdata out/target/product/u8120/userdata.img
$ fastboot reboot
For some reason the generated boot.img fails to boot.Maybe I have something wrong about kernel base etc in the BoardConfig.mk.
For now just use the ramdisk.img and the provided kernel and pack it with dsixda's kitchen or with the huawei-u8100 tools that have been posted on the forum.
Then just use fastboot as stated above.
for the future
thnx for the gifts up to it tomorrow
A question about camera problem, only video or all features?
bitye said:
A question about camera problem, only video or all features?
Click to expand...
Click to collapse
The camera fails after a few secs.When an image appears in the preview window.
I have read that the the way that android handles camera has changed in froyo.In cyanogen they are using a libcamera2 (just libcamera with a few changes I think so it can work with the new framework).
As you can see in the BoardConfig.mk I have already include the libcamera2 statements but not the lib
When I manage to get some free time I would try the libcamera2.Maybe until the end of the week or sooner.
Ρε πατριδα αξιζει η rom ή οχι;
tas0s said:
For some reason the generated boot.img fails to boot.Maybe I have something wrong about kernel base etc in the BoardConfig.mk.
For now just use the ramdisk.img and the provided kernel and pack it with dsixda's kitchen or with the huawei-u8100 tools that have been posted on the forum.
Then just use fastboot as stated above.
Click to expand...
Click to collapse
There's a little fix using bootbuilder for U8120, see this post:
http://android.modaco.com/content/t...l-r1-bootbuilder-for-pulsemini-alpha-release/
In the 6th reply you can find the info you could need it
Good luck!
Hi can you tell me on wich kernel it runs?
the 2.6.32 or2.6.29?
and if wiifi is completly fixed no crashes sleep works mac adress?
thanks
calibration fixed at this repo?
larissamafia said:
Ρε πατριδα αξιζει η rom ή οχι;
Click to expand...
Click to collapse
Πατριωτάκι δεν είναι για καθημερινή χρήση ακόμα.Γιαυτό δεν έχω βγάλει και έτοιμη rom.
@Shiftok:
The calibration is integrated in the framework etc but it has some small issues.
As I say in the first post, it needs improvement.
@Cedric123:
Im using 2.6.29 kernel.The wifi works normally.If I remember right and MAC address.
tas0s said:
@Shiftok:
The calibration is integrated in the framework etc but it has some small issues.
As I say in the first post, it needs improvement.
@Cedric123:
Im using 2.6.29 kernel.The wifi works normally.If I remember right and MAC address.
Click to expand...
Click to collapse
ah okey
does this work?
i extract boot.img
put my own zImage in it
repack boot.img
start Phone?
i rly want my own kernel in the ROM with my overclock funtion adn all my +kalt+kaffes optimizations
cedric123 said:
ah okey
does this work?
i extract boot.img
put my own zImage in it
repack boot.img
start Phone?
i rly want my own kernel in the ROM with my overclock funtion adn all my +kalt+kaffes optimizations
Click to expand...
Click to collapse
The kernel Im using is kalt kaffe's kernel.So I think that if you just replace the kernel and the kernel modules in /system/lib/modules you will be fine.
Im uploading now a zip with the compiled images.
It has the problems I mention in the first post etc.
Just an observation.If the calibration isnt correct the screen is always on landscape mode Propably because it gets wrong screen dimensions.So if you see something like that, calibrate your screen with the TSCalibration app.
When im done with the camera, I will fix the calibration bugs.
Hi. Im testing your rom.
I cannot mount the sdcard on computer. when i press to activate usb storage it does nothing in computer.
EDIT - i cant install anything because i dont have a file explorer to see the sdcard files. can you please add one or make an .img with the stock apps
joilaroi said:
Hi. Im testing your rom.
I cannot mount the sdcard on computer. when i press to activate usb storage it does nothing in computer.
EDIT - i cant install anything because i dont have a file explorer to see the sdcard files. can you please add one or make an .img with the stock apps
Click to expand...
Click to collapse
Thank you very much for the feedback joilaroi.I have updated the first post with the sdcard bug.I tried myself and you are right.I will try to fix it.
As I know the stock android froyo hasnt any file manager/explorer.Maybe we can get it from cyanogens.
For now, you can do this.Flash the gapps update that I have in the first post,setup market etc and download a file manager from the market(ex.astro file explorer).
tas0s said:
Thank you very much for the feedback joilaroi.I have updated the first post with the sdcard bug.I tried myself and you are right.I will try to fix it.
As I know the stock android froyo hasnt any file manager/explorer.Maybe we can get it from cyanogens.
For now, you can do this.Flash the gapps update that I have in the first post,setup market etc and download a file manager from the market(ex.astro file explorer).
Click to expand...
Click to collapse
thanks. its what i am doing. if i find anything i will give feedback
EDIT - Cant install superuser and have permissions. it downloads su-2.3.1-bin-signed.zip to sdcard but its corrupted. maybe its better if its already on .img
Im getting more MFLOPS with 633Mhz in this rom than with 691Mhz with the other kernel. its now with 4.45 MFLOPS vs 4.1MFLOPS. Nice
Do you know where i can find su-2.3.1-bin-signed.zip?
Ubuntu 10.10 x64 under W7 VMWare will be enought for compile?
PC: C2D [email protected],2GHZ 8GB RAM
Laptop: Lenovo T410 i5 vPro 2,4GHz Quad Core 4GB RAM
I think yes
I can't post to the development section because i'm new here, so feel free to move this thread
I've found some really interesting things around the internet.
I got an mt6573 device half a year ago(Star A920) and ported over some ROM'S.
Now i wan't to get deeper, the problem is the sourcecode from mediatek. Alcatel has released its sources (OT918d, OT991d) which are mt6573 phones. For building the mediatek Android, we need other files, which were not included in their sources.
Now it's getting interesting:
I've found this on the internet:
www.github.com/fanjunwei/mytqe
It seem like this is the development environment for the ALPS MTK builds.
I also found this "How-To" for the environment.
http://wenku.baidu.com/view/86c3bad749649b6648d74748.html
..and the kernelsource for the alcatel 991d.
www.sourceforge.net/projects/alcatel/files/OT_991D_20120725.tar.xz/download
I'm trying to build an android from sources, maybe we are successfull together.
If I'm wrong - correct me, please.
edit: sucessfully build Android 2.3.6 from sources!!! ( ALPS.GB.FDD2.MP.V4.5 , e1101_v73_jbl1ctp_a515, Kernel Version 2.6.35.7 )
Whoa bro !
can u make a guide how to compile from sources ?
Chrizzly92 said:
I can't post to the development section because i'm new here, so feel free to move this thread
I've found some really interesting things around the internet.
I got an mt6573 device half a year ago(Star A920) and ported over some ROM'S.
Now i wan't to get deeper, the problem is the sourcecode from mediatek. Alcatel has released its sources (OT918d, OT991d) which are mt6573 phones. For building the mediatek Android, we need other files, which were not included in their sources.
Now it's getting interesting:
I've found this on the internet:
www.github.com/fanjunwei/mytqe
It seem like this is the development environment for the ALPS MTK builds.
I also found this "How-To" for the environment.
http://wenku.baidu.com/view/86c3bad749649b6648d74748.html
..and the kernelsource for the alcatel 991d.
www.sourceforge.net/projects/alcatel/files/OT_991D_20120725.tar.xz/download
I'm trying to build an android from sources, maybe we are successfull together.
If I'm wrong - correct me, please.
edit: sucessfully build Android 2.3.6 from sources!!! ( ALPS.GB.FDD2.MP.V4.5 , e1101_v73_jbl1ctp_a515, Kernel Version 2.6.35.7 )
Click to expand...
Click to collapse
it's cool!!
can you make a tutorial for comiling android from source?
look at the second link i've posted. there is an complete tutorial. (setting up a virtual machine, for example). you have to use "./makeMtk baoxue r" to build the komplete system with recovery, boot.img etc.
then u need some cust_xxx.c files from the alcatel sources, or the build fails. ( copy them manually to the folders, shown in the error logs of the builds).
I have to get deeper into it, maybe compiling a new kernel for our devices. Sure I will make an Tutorial, but at first i have to know exactly what im dooing. I hope someone else can help me, so we can get the best results out of it.
Chrizzly92 said:
I can't post to the development section because i'm new here, so feel free to move this thread
I've found some really interesting things around the internet.
I got an mt6573 device half a year ago(Star A920) and ported over some ROM'S.
Now i wan't to get deeper, the problem is the sourcecode from mediatek. Alcatel has released its sources (OT918d, OT991d) which are mt6573 phones. For building the mediatek Android, we need other files, which were not included in their sources.
Now it's getting interesting:
I've found this on the internet:
www.github.com/fanjunwei/mytqe
It seem like this is the development environment for the ALPS MTK builds.
I also found this "How-To" for the environment.
http://wenku.baidu.com/view/86c3bad749649b6648d74748.html
..and the kernelsource for the alcatel 991d.
www.sourceforge.net/projects/alcatel/files/OT_991D_20120725.tar.xz/download
I'm trying to build an android from sources, maybe we are successfull together.
If I'm wrong - correct me, please.
edit: sucessfully build Android 2.3.6 from sources!!! ( ALPS.GB.FDD2.MP.V4.5 , e1101_v73_jbl1ctp_a515, Kernel Version 2.6.35.7 )
Click to expand...
Click to collapse
Congratulations buddy, a tut by your experience shall be highly helpful
Xperia Neo V? thas NOT an mt6573 based Phone. maybe you have a chinese fake or something, then u could be right here.
Great work! what is the latest news??
Header is missing
Hi pals,
the Problem is that the repack-MT6577.pl assumes tht the needed Header information is already in the zImage, which is because normally you would pass the zImage which you extractet from a original boot.img to the script. So it will not boot until you append the Header to the zImage,
i extracted the Header with dd and build a zImage with it. Will try that out now
Edit:
the header is the first 512bytes of the original zImage
Edit2:
It boots with my custom kernel Forgot to mention my device: Alcatel OT998 (sold by Base in Germany, almost the same as OT997/OT997D)
Edit3: sorry Wrong Thread, as it is a different MTK-Platform but the info correct for you also i guess
HUELK said:
Hi pals,
the Problem is that the repack-MT6577.pl assumes tht the needed Header information is already in the zImage, which is because normally you would pass the zImage which you extractet from a original boot.img to the script. So it will not boot until you append the Header to the zImage,
i extracted the Header with dd and build a zImage with it. Will try that out now
Edit:
the header is the first 512bytes of the original zImage
Edit2:
It boots with my custom kernel Forgot to mention my device: Alcatel OT998 (sold by Base in Germany, almost the same as OT997/OT997D)
Edit3: sorry Wrong Thread, as it is a different MTK-Platform but the info correct for you also i guess
Click to expand...
Click to collapse
Again nice work!
Can you a somewhat detailed tutorial??
balamu96m said:
Again nice work!
Can you a somewhat detailed tutorial??
Click to expand...
Click to collapse
hi ,
sorry sure i can give detail, well at least i try:
1. Get the zImage from a working boot.img eg with unmkbootimg or split_bootimg.pl
2. The needed header is in the first 512bytes of the zImge extract that:
dd if=<zImgeOrig> of=header bs=512 count=1
3. Append the header to the build zImage
3.1 dd if=header of=zImageMod
2.2 dd if=zImageCustom of=zImageMod seek=512
4. Repack Boot.img with repack-MT65xx.pl as known
5. Flash through CWM:
I flash it to my device over the adb console after putting the Image on the sdcard with adb push:
dd if=/sdcard/<boot.img> of=/dev/bootimg
NOT TESTET: flashing through the cwm update-script with write_raw_image("boot.img", "/dev/bootimg");
Thats the way i got it up to boot, but i have some Problems with the permission of pvrsrvkm.ko know, i building CM10 for my Device if anyone wants to know...
i guess you can easily modify the repack-MT6577.pl to include that for fresh kernels, i will have a look at that in the next days.
Greetz HUELK
<-----THANKS Button
HUELK said:
hi ,
sorry sure i can give detail, well at least i try:
1. Get the zImage from a working boot.img eg with unmkbootimg or split_bootimg.pl
2. The needed header is in the first 512bytes of the zImge extract that:
dd if=<zImgeOrig> of=header bs=512 count=1
3. Append the header to the build zImage
3.1 dd if=header of=zImageMod
2.2 dd if=zImageCustom of=zImageMod seek=512
4. Repack Boot.img with repack-MT65xx.pl as known
5. Flash through CWM:
I flash it to my device over the adb console after putting the Image on the sdcard with adb push:
dd if=/sdcard/<boot.img> of=/dev/bootimg
NOT TESTET: flashing through the cwm update-script with write_raw_image("boot.img", "/dev/bootimg");
Thats the way i got it up to boot, but i have some Problems with the permission of pvrsrvkm.ko know, i building CM10 for my Device if anyone wants to know...
i guess you can easily modify the repack-MT6577.pl to include that for fresh kernels, i will have a look at that in the next days.
Greetz HUELK
<-----THANKS Button
Click to expand...
Click to collapse
Bad that I can't give a double thanks for your highly useful post!
Building CM 10 = awesome!
I would like to know more....cm10 with dual sim support??
Thanks again!
balamu96m said:
Bad that I can't give a double thanks for your highly useful post!
Building CM 10 = awesome!
I would like to know more....cm10 with dual sim support??
Thanks again!
Click to expand...
Click to collapse
Hi,
building cm10 with dual sim support will be complicated as there is no support for it in cm10 , my device has no dual sim but nfc instead. i now almost got it up running, the pvrdrv loads now correctly but there is some problem with some framework files and BOOTCLASSPATH variable. I think i will get it fully up today. Was awake till 6 o'clock on this .
HUELK said:
Hi,
building cm10 with dual sim support will be complicated as there is no support for it in cm10 , my device has no dual sim but nfc instead. i now almost got it up running, the pvrdrv loads now correctly but there is some problem with some framework files and BOOTCLASSPATH variable. I think i will get it fully up today. Was awake till 6 o'clock on this .
Click to expand...
Click to collapse
Great again! Hope you complete it soon!
I would somehow try to port it.....!
Hi thanks for your procedure.
I tried , i can boot but the display is very slowly. I tried with this source code https://github.com/wiko-sources/cink-king
I have a wiko cink king with mt6577.
Have you ever used repack-MT65xx.pl for mt6577?
TY
HUELK said:
hi ,
sorry sure i can give detail, well at least i try:
1. Get the zImage from a working boot.img eg with unmkbootimg or split_bootimg.pl
2. The needed header is in the first 512bytes of the zImge extract that:
dd if=<zImgeOrig> of=header bs=512 count=1
3. Append the header to the build zImage
3.1 dd if=header of=zImageMod
2.2 dd if=zImageCustom of=zImageMod seek=512
4. Repack Boot.img with repack-MT65xx.pl as known
5. Flash through CWM:
I flash it to my device over the adb console after putting the Image on the sdcard with adb push:
dd if=/sdcard/<boot.img> of=/dev/bootimg
NOT TESTET: flashing through the cwm update-script with write_raw_image("boot.img", "/dev/bootimg");
Thats the way i got it up to boot, but i have some Problems with the permission of pvrsrvkm.ko know, i building CM10 for my Device if anyone wants to know...
i guess you can easily modify the repack-MT6577.pl to include that for fresh kernels, i will have a look at that in the next days.
Greetz HUELK
<-----THANKS Button
Click to expand...
Click to collapse
@HUELK
Where you able to boot? I would like to try the process on a mtk6573
Kudos!
myphoneuser said:
@HUELK
Where you able to boot? I would like to try the process on a mtk6573
Kudos!
Click to expand...
Click to collapse
would like to help here too, already working on rom development for mt6573...
HUELK said:
3. Append the header to the build zImage
3.1 dd if=header of=zImageMod
2.2 dd if=zImageCustom of=zImageMod seek=512
Click to expand...
Click to collapse
The zImageMod and zImageCustom is confusing me. Can you differentiate between them??
Thanks.
boots now
Hi,
NEWS: got it up to boot cm10! yes display is slow for me too, but its a start
greetz huelk
---------- Post added at 11:14 PM ---------- Previous post was at 11:12 PM ----------
balamu96m said:
The zImageMod and zImageCustom is confusing me. Can you differentiate between them??
Thanks.
Click to expand...
Click to collapse
hi yes, the zImage Custum is the zImage wich resides in arch/arm/boot/zImage after you build the kernel, the zImage Mod is the Output file which will be inside the boot.img that you will flash
HUELK
---------- Post added at 11:17 PM ---------- Previous post was at 11:14 PM ----------
balamu96m said:
The zImageMod and zImageCustom is confusing me. Can you differentiate between them??
Thanks.
Click to expand...
Click to collapse
As i told you my device is a mt6577 but the changes you need should be the same, can you send me an original boot.img of your device, i will have a look.
HUELK said:
Hi,
NEWS: got it up to boot cm10! yes display is slow for me too, but its a start
greetz huelk
---------- Post added at 11:14 PM ---------- Previous post was at 11:12 PM ----------
hi yes, the zImage Custum is the zImage wich resides in arch/arm/boot/zImage after you build the kernel, the zImage Mod is the Output file which will be inside the boot.img that you will flash
HUELK
---------- Post added at 11:17 PM ---------- Previous post was at 11:14 PM ----------
As i told you my device is a mt6577 but the changes you need should be the same, can you send me an original boot.img of your device, i will have a look.
Click to expand...
Click to collapse
Thanks for clarifying my doubt!
And great to know that CM 10 booted :highfive: !
here is my boot.img : here
btw, how can the slow touch response be solved bro ??
Chrizzly92 said:
would like to help here too, already working on rom development for mt6573...
Click to expand...
Click to collapse
Hey bro,
i'm asking this, because you had cloned the full MT6573 source........Can you upload the following folders from the source's root :
Kernel
Mediatek
I need it to try my hands at the MT6573 kernel!
Thanks in advance!
MT6592 CM 12.1 PORTING GUIDE
Lots of people asked me how i ported cm 12.1 from @fire855's compiled rom for kingzone k1 Turbo
First of all huge thanks to @fire855 and other Dev who helped him for bringing cm 12.1 on mt6592
Give support to him via pressing thanks or Donate , here is it's Link : http://forum.xda-developers.com/and...od-12-kingzone-k1-turbo-t3119908#post61000671
Requirements :
1. Stock Rom KK
2. Working Good Custom Recovery
3. Good Porter and Mind
Lets Start This Short Guide :
1. Download Latest Cm 12.1 from above link
2. Extract in a new folder
3. Use this tool LInk : http://forum.xda-developers.com/android/development/tool-convert-folder-to-ext4-format-t3099237
unpack .dat file and copy extracted system folder in new folder as stated in step 2.
4. Using @michfood's tool (link : http://forum.xda-developers.com/showthread.php?t=2036528)
change Kernel and Do necessary changes acc. to your stock's ramdisk
5. Copy new boot.img that created in step 4 and replace in new folder as stated in step 2.
6. From stock kk rom ...........extract libaudio.primary.default.so (system/lib) and modem.img (system/etc/firmware) nd replace in cm 12.1 's rom ................ in the same location
7. Delete meta-inf folder of cm 12.1's rom and extract this (link : https://www.sendspace.com/file/vnf0gi)
8. Open meta-inf's updater-script in notepad++ and change mountpoint of system acc. to your's phone
9. Pack the folder as in zip format and flash via recovery
( meta-inf, install ,system, boot.img, file context these files must there in zip )
10. Voila Rom booted .............if not comment
If Rom Booted ..............Follow this steps :
1. Download this apk (link : http://forum.xda-developers.com/showthread.php?t=2524485)
2. Go to Settings>developer>enable root and install apk from step 1
3. Open app and Set as permissive ,reboot Your device
4. Voila your wifi,bluetooth etc will start working, even Dual Sim
5. If you faced basedband unknown that mean restore your imei
6. For Home Key Bug , Edit generic.kl and mtk-kpd.kl (system/user/keylayout)
7. For Storage Bug, Edit Framework-res.apk and set sdcard1 as primary and edit boot's ramdisk MT6592.rc, fstab
8. For Other Bugs, Let Me Know
Notice : Always give thanks and link of @fire855's Rom Link
Credits : everyone (who's name i added in this guide and there's tools )
@[email protected] Thanks for a great guide, I was able to succesfully port the rom and it booted as well and after setting the selinux to permission my sims also started working but mic is not working, my device is MT6582 (Intex Aqua Speed). I have a working CM11 already ported for my device which is working perfectly fine. Also the soft keys (capacitive keys are not working nor even the power button). Please advise...
contactwajeeh said:
@[email protected]. . . . but mic is not working . . . .
Click to expand...
Click to collapse
The microphone is also not working in all apps (except Telephone where it work's fine) in the original CM12.1 by fire855 for the Kingzone K1. (The Rom this Porting Guide is based on).
That could be part of the problem.
Dominic
G-GFFD said:
The microphone is also not working in all apps (except Telephone where it work's fine) in the original CM12.1 by fire855 for the Kingzone K1. (The Rom this Porting Guide is based on).
That could be part of the problem.
Dominic
Click to expand...
Click to collapse
But its not working in calls as well. BTW I am using @moonrotation build as my base. I haven't asked for permissions to port it yet. But that should be fine as far as I dont do the public release of it.
What necessary changes i must do in ramdisk?help
contactwajeeh said:
But its not working in calls as well. BTW I am using @moonrotation build as my base. I haven't asked for permissions to port it yet. But that should be fine as far as I dont do the public release of it.
Click to expand...
Click to collapse
currently mic problem is there ....wait for fixes
contactwajeeh said:
@[email protected] Thanks for a great guide, I was able to succesfully port the rom and it booted as well and after setting the selinux to permission my sims also started working but mic is not working, my device is MT6582 (Intex Aqua Speed). I have a working CM11 already ported for my device which is working perfectly fine. Also the soft keys (capacitive keys are not working nor even the power button). Please advise...
Click to expand...
Click to collapse
edit keylayout's genric.kl etc
mirrr46 said:
What necessary changes i must do in ramdisk?help
Click to expand...
Click to collapse
like some some extra lines der in urs .
Tried to port this, Device reboots right after vendor logo
I compare stock Ramdisk with CM12. There are no diff. At end both have same values. I changed Kernel and Kernel Header
I changed the updater script so it fits to my partition. It gave me strange errors:
lsetfilecon of /system/lost+found to ubject_r:system_file:s0 failed: No such file or directory
m_file:s0 failed: Operation not supported on transport endpoint
Error flashing Zip : Failed
Updating partition details...
Click to expand...
Click to collapse
Also @michfood's tool just ain't work here, i took the v4 for my x64 win8.1. The Program is unable to extract the Ramdisk path, so i was forced to use "MTK Firmware Adapter Tool"
Recovery:TWRP 2.8.1.0
SoC:MT6592
Device: Doogee DG550
Traace said:
Tried to port this, Device reboots right after vendor logo
I compare stock Ramdisk with CM12. There are no diff. At end both have same values. I changed Kernel and Kernel Header
I changed the updater script so it fits to my partition. It gave me strange errors:
Also @michfood's tool just ain't work here, i took the v4 for my x64 win8.1. The Program is unable to extract the Ramdisk path, so i was forced to use "MTK Firmware Adapter Tool"
Recovery:TWRP 2.8.1.0
SoC:MT6592
Device: Doogee DG550
Click to expand...
Click to collapse
1. don't touch kernel header....change only kernel
2. u should try other recovery like philz
3. delete lost and found folder if present
4. use my meta-inf only....just change mountpoint of system........it seems u need good recovery with lp supported or philz recovery :fingers-crossed:
Thanks for guide.
My camera does not work and gallery does not see SD card.
How to fix it?
mirrr46 said:
Thanks for guide.
My camera does not work and gallery does not see SD card.
How to fix it?
Click to expand...
Click to collapse
1. camera icon in launcher is issue (for mt6592)
2. for storage...fixes r from mt6592.rc in this file read proper sysmlink and do changes acc. to it ,decompile framework-res.apk....set sdcard1 as primary ,fstab changes also needed
Enforcing to Permissive
Does anyone know how to make selinux permissive without any app,I tried to change ro.build.selinux and set it to 0 but it didn't work...does anyone know what to edit in ramdisk to make selinux permissive.?
Traace said:
Tried to port this, Device reboots right after vendor logo
I compare stock Ramdisk with CM12. There are no diff. At end both have same values. I changed Kernel and Kernel Header
I changed the updater script so it fits to my partition. It gave me strange errors:
Also @michfood's tool just ain't work here, i took the v4 for my x64 win8.1. The Program is unable to extract the Ramdisk path, so i was forced to use "MTK Firmware Adapter Tool"
Recovery:TWRP 2.8.1.0
SoC:MT6592
Device: Doogee DG550
Click to expand...
Click to collapse
I'm still struggling to port this rom to DG550.
1. The tool you used to extract the kernel does not work in Windows 8.1 and Windows 10 (I got empty RAMDISK folder). So I switched back to Windows 7 and it worked well.
2. Compared both Ramdisk folders in Stock DG550 Kitkat and Stock Kingzone K1 Kitkat boot.img's.
There is no difference except in ueventd.rc file. I tried to mix DG550 kernel and Kingzone Z1 stock Ramdisk with DG550 Kitkat rom. It didn't boot at first. The problem was in ueventd.rc file. See line 152 (Mali Node). After replacing ueventd.rc file from DG550 ramdisk it booted and worked well (stock kitkat rom). So both the stock ramdisks are identical if ueventd.rc file is replaced.
3. But it fails when porting the boot.img for CM12.1. Theoretically CM12.1 ramdisk should work with DG550 kernel for CM12.1 rom without any changes (except ueventd.mt6592.rc). It does not pass the boot logo.
4. Also I noticed that there's some issue in sbin folder in ramdisk.
ADev_28 said:
Does anyone know how to make selinux permissive without any app,I tried to change ro.build.selinux and set it to 0 but it didn't work...does anyone know what to edit in ramdisk to make selinux permissive.?
Click to expand...
Click to collapse
/system/bin/setenforce 0
From any root terminal.
Thanks,
1. But i did port for mtk6582 (camera unfortunelty has stop)
chanaka89 said:
I'm still struggling to port this rom to DG550.
1. The tool you used to extract the kernel does not work in Windows 8.1 and Windows 10 (I got empty RAMDISK folder). So I switched back to Windows 7 and it worked well.
2. Compared both Ramdisk folders in Stock DG550 Kitkat and Stock Kingzone K1 Kitkat boot.img's.
There is no difference except in ueventd.rc file. I tried to mix DG550 kernel and Kingzone Z1 stock Ramdisk with DG550 Kitkat rom. It didn't boot at first. The problem was in ueventd.rc file. See line 152 (Mali Node). After replacing ueventd.rc file from DG550 ramdisk it booted and worked well (stock kitkat rom). So both the stock ramdisks are identical if ueventd.rc file is replaced.
3. But it fails when porting the boot.img for CM12.1. Theoretically CM12.1 ramdisk should work with DG550 kernel for CM12.1 rom without any changes (except ueventd.mt6592.rc). It does not pass the boot logo.
4. Also I noticed that there's some issue in sbin folder in ramdisk.
Click to expand...
Click to collapse
Please let us know if u can let it boot
Ramdisk sBin shoudn't be a problem, if they really cause trouble, try copy the missing files from base dg550 kk to cm12
[email protected] said:
1.
Click to expand...
Click to collapse
Thank you very much... Your guide was very appreciated... Work like a charm..
I used the device MT6592 - BLU VIVO IV of the my friend for port CM12.1
Sent from my LIFE PLAY X KK using XDA Free mobile app
lopestom said:
Thank you very much... Your guide was very appreciated... Work like a charm..
I used the device MT6592 - BLU VIVO IV of the my friend for port CM12.1
Sent from my LIFE PLAY X KK using XDA Free mobile app
Click to expand...
Click to collapse
congo
Traace said:
Please let us know if u can let it boot
Ramdisk sBin shoudn't be a problem, if they really cause trouble, try copy the missing files from base dg550 kk to cm12
Click to expand...
Click to collapse
mirrr46 said:
1. But i did port for mtk6582 (camera unfortunelty has stop)
Click to expand...
Click to collapse
seems storage bug...u need to fix storage .............check guide and comments
chanaka89 said:
I'm still struggling to port this rom to DG550.
1. The tool you used to extract the kernel does not work in Windows 8.1 and Windows 10 (I got empty RAMDISK folder). So I switched back to Windows 7 and it worked well.
2. Compared both Ramdisk folders in Stock DG550 Kitkat and Stock Kingzone K1 Kitkat boot.img's.
There is no difference except in ueventd.rc file. I tried to mix DG550 kernel and Kingzone Z1 stock Ramdisk with DG550 Kitkat rom. It didn't boot at first. The problem was in ueventd.rc file. See line 152 (Mali Node). After replacing ueventd.rc file from DG550 ramdisk it booted and worked well (stock kitkat rom). So both the stock ramdisks are identical if ueventd.rc file is replaced.
3. But it fails when porting the boot.img for CM12.1. Theoretically CM12.1 ramdisk should work with DG550 kernel for CM12.1 rom without any changes (except ueventd.mt6592.rc). It does not pass the boot logo.
4. Also I noticed that there's some issue in sbin folder in ramdisk.
Click to expand...
Click to collapse
i don't think so....again try and don't touch ramdisk
[email protected] said:
congo
seems storage bug...u need to fix storage .............check guide and comments
i don't think so....again try and don't touch ramdisk
Click to expand...
Click to collapse
How to solve storage bug??
Device booted.Not able to mount/access storage. ??
TWRP 3.1.0.0 with FIsH for our FLEX 2
Tested on h955 and it's still a BETA
Requirements
Here are the pre-requirements you have to met!
If you can't get them: Close this page and FORGET it (until the day you met those reqs)!
Here are the 2 simple requirements you have to met:
1. root by SuperSU >=v2.76 (greater or equal v2.76)
--> to test this requirement just start the installer of FIsH with --check (see next lines) which will check for all requirements and abort if its not possible
--> for many devices - if not all - this means you HAVE TO downgrade/install LL. It also means that you have to upgrade your SuperSU to this version by e.g. FlashFire if you have a lower version installed!
--> SU by phh is NOT supported => It needs a modified /boot and this would void the boot signing chain!
--> Magisk is NOT supported => It needs a modified /boot and this would void the boot signing chain!
--> I will NOT provide downgrading guides there are plenty of them so search and read.
--> I will NOT provide any guides in rooting your device
--> Before you think about downgrading to LL read about ANTI-ROLLBACK protection some devices and may have! Anti-Rollback means you CAN NOT downgrade - it would HARD-BRICK your device (wtf thinking the vendors who we are?? Is this even legal?!)! Check that before!!
2. you have to be able to disable SELinux in your booted Android
--> You do NOT need to set SELinux permanently to permissive. Just CHECK if you COULD get it MANUALLY. If you can get it OK. If not.. you obviously have not full root access but check the forums maybe there is something you can do about this.
--> I will NOT provide any guides enabling SELinux but some lines later you will see how u can execute the very simple check
--> to test this requirement just start the installer of FIsH with --check (see next lines) which will check for all requirements and abort if its not possible
Those above are hard facts so it may NEVER work with MM. Google has changed the way on how the boot chain will be verified and that means changes in /system will void it from now on.
If MM can get fully rooted somehow/somewhen on your device with SuperSU installed and you are able to disable SELinux the method will work there as well.
If you can not meet ALL of the above 2 requirements lay down and cry.
For the others: calm down and read on!
You can simply test those both requirements by downloading the FIsH package and execute the installer with the following test parameter:
./install.sh --check
This way nothing get installed but you will see if it would work on your device or not.
Limitations!
Keep in mind what I said above: FIsH does NOT unlock your bootloader!
That means with TWRP-in-FIsH you can NOT:
Install a custom ROM like CM/Lineage (this will modify boot = SOFT-BRICK)
Install a custom Kernel (this will modify boot = SOFT-BRICK)
Install a custom recovery (this will modify recovery = may SOFT-BRICK)
In short: do nothing which modifies boot or recovery partitions. Those changes will BREAK your boot signing chain.
You can of course flash everything which is modifying /system /data only (e.g. xposed, Audio mods, etc...)
You're able to backup and restore as well of course and doing any other modifications which you may can't while the Android system is running.
Download
READ THE REQUIREMENTS above before proceeding!
Then UNDERSTAND the requirements before proceeding! <-- omg this is crucial important!!!! Ensure that you really do not skip this step!
READ THE LIMITATIONS above before proceeding!
Then UNDERSTAND the limitations before proceeding! <-- omg this is crucial important!!!! Ensure that you really do not skip this step!
... and NEVER ask for ETA's!
if you can say:
Yes! I have read and totally understood the limitations AND the requirements!
then proceed. Otherwise read again until you got it.
Keep in mind that this is a HACK. It may soft-brick your device. you have been warned!
The concept is the same for all models but again no guarantees here for anything.
There is ALWAYS a risk and you should better backup what you do not want to loose before starting downloading this.
Download
Installation (Linux)
You can just install any newer version over an old one.
boot Android and connect USB cable
download the newest version to your PC and open a terminal in that directory
tar xzf TWRP-in-FIsH*.tgz
cd android_FIsH
./install.sh
check the output of that script. you should not see any errors there (hopefully)
Installation (Windows)
use FWUL or be patient.. maybe i or someone else release an installer... maybe...
First run (no PC required)
This FIsH gets installed PERMANENTLY! That means:
You can boot up TWRP the same way as described here again without re-installing.
If you re-install your STOCK image you have to re-install TWRPinFIsH as well.
reboot Android
you should now see: LED goes from blue to GREEN
NOW directly when u see this GREEN LED press VOLUME DOWN and do NOT release
wait until the device vibrates and the LED changed to RED. Then release the Volume Down button.
Wait until FIsH completed and TWRP should be shown --> This means FIsH has done it's job well!
This is a good time to do a full backup isn't it ? Manually mount the SYSTEM partition as it gets not auto mounted atm and do a full backup
reboot from here (safely ignore the msg "no OS installed" and reboot anyways) and you should see Android booting (hopefully ... if not see bottom)
Daily Usage (no PC required)
reboot Android
you should now see: LED goes from blue to GREEN
NOW directly when u see this GREEN LED press VOLUME DOWN and do NOT release
wait until the device vibrates and the LED changed to RED. Then release the Volume Down button.
Wait until FIsH completed and TWRP should be shown --> This means FIsH is doing it's job still very well
AGAIN: keep your mind up! You HAVE to ensure that whatever you do and whatever you flash -> NEVER TOUCH BOOT/RECOVERY! If you flash a ZIP ensure first that it do not modify them! Otherwise you WILL softbrick. You have been warned (several times now)
Trouble / Bootloop fix
if you encounter a bootloop (should never happen but who knows) you have 3 choices at least:
Option 1a: (TWRP-Bootloop) Within TWRP open Advanced -> File Manager -> Goto: /system/su.d and click "select" button -> Delete
Option 1b: (TWRP-Bootloop) From your PC: adb shell rm -rf /system/su.d/
Important: Catch the fish log (see next topic)
Option 2 (this works also for a bootloop without twrp): boot into download mode and use LGLaf to get a shell
then:
setenforce 0 <-- if that doesn't work you may have to do a FULL restore to stock
mount -oremount,rw /system
rm -rf /system/su.d/
reboot. You are out of the bootloop.
Important: Catch the fish log (see next topic)
Option 3: Last resort: Reflash STOCK. sorry.. there is always a risk..
Catch the FIsH logs
when in TWRP (or other ramdisk providing adb shell):
adb shell "cat /cache/fish/fish.log"
adb shell "cat /tmp/recovery.log"
OR - when in Android:
adb shell "su -c cat /cache/fish/fish.log"
adb shell "su -c cat /cache/fish/fish.log.old"
adb shell "su -c tar cvzf recoverylogs.tgz /cache/recovery"
adb pull recoverylogs.tgz
Upload the output to https://paste.omnirom.org and paste the link in the IRC channel (see next topic)
Support / IRC Channel
IRC means Internet Relay Chat and you will get best support here only.
Choose how to get in:
PC (HexChat and Pidgin are only 2 of them! This list is not complete!)
Android (Yaaic, AndChat, HoloIRC, AndroIRC are only a few of them! This list is not complete!)
Web (KiwiIRC-Web,FreenodeWebchat])
When you have to choose a channel it is: #Carbon-user
When you will be asked for a server network choose: freenode
Known issues (may never get fixed)
Due to the fact that FIsH is a BRUTAL hijack of the booting process several things may not work as expected.
This will normally not harm anything but you have to know about.
ZIP / ROM flashing:
omg really you wanna hear that again? OK: DON'T TOUCH BOOT / RECOVERY. And you be safe.
When you try to install a ROM it will modify at least BOOT. That means soft-brick!
When you try to install a custom Kernel.. omg really? It will definitively SOFT-BRICK! Maybe you should read the limitations again??
When you try to install a ZIP like xposed, supersu, Vipermod and others ensure that those are not modifying BOOT or RECOVERY partitions. For those mentioned it would be very unlikely but who knows.
FIRMWARE partition:
cannot be mounted - even not manually. You have to live with it.
Double Tap to wakeup (in TWRP):
Unfortunately this cannot work in TWRP-in-FIsH due to the nature of this hijack. You have to live with it.
Credits (without them - no FIsH!!!)
If you feel that someone / you is missing on this list lemme know!
Chainfire for SuperSU! This is the main part of FIsH.
TeamWin for TWRP
@cray_Doze, @dssmex, @Aaahh and @KeiranFTW for their hijack implementations (e.g. https://forum.xda-developers.com/showthread.php?t=2608408, first steps to a G4 hijack)
steadfasterX for the android FIsH !
Here is the h955 device tree for building TWRP with omnirom minimal sources - https://github.com/jarno83/android_device_lge_h955
Here are TWRP logs from backups and restoring if anyone interested - https://github.com/jarno83/twrp_logs
Changelog
29.04.2017 - TWRP-3.1-in-FIsH-v2.0_LGFLEX2_LL_BETA3.zip
Latest FIsH source code and fixes.
3.04.2017 - TWRP-3.1-in-FIsH-v2.0_LGFLEX2_LL_BETA2.zip
Fixed the RESTORE issue - thanks to SteadfasterX
Used latest FIsH source code.
Went to zip format, now a pit smaller.
2.04.2017 - TWRP-3.1-in-FIsH-v2.0_LGFLEX2_LL.tar.gz
The fishfood is TWRP 3.1.0.0 it uses 15c stock kernel for now. And has a problem with restoring.
What is TESTED
BACKUP and RESTORING /system and /data partitions - OK
Xposed V87 - flashes ok with twrp and works - http://dl-xda.xposed.info/framework/sdk22/arm64/
Tested Device List
H955 running 5.1.1 15c ROM
H950 running 5.1.1 PR ROM - thanks to iDefalt
Congrats
Have you seen the XDA template for FIsH?
https://forum.xda-developers.com/an...ack-to-boot-want-device-t3578373/post71567825
.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Congrats
Have you seen the XDA template for FIsH?
https://forum.xda-developers.com/an...ack-to-boot-want-device-t3578373/post71567825
.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Ok, thanks Didn't saw that
So anyone tested it yet ? TWRP booting ?
I have my phone in repair center atm cant test anything.
Yes, I have it on my h955 and twrp boots fine. I tested system backup and restore, now working. Flashed xposed also ?
Sent from my LG-H955 using XDA-Developers Legacy app
/data backuped and restored with success ?
Sent from my LG-H955 using XDA-Developers Legacy app
Ok so now what? What is the next step? On road To install custom rom or custom kernel.
dadaa1 said:
Ok so now what? What is the next step? On road To install custom rom or custom kernel.
Click to expand...
Click to collapse
SteadfasterX is developing some stuff... so maybe on day we will have a possibility to use full custom roms.
But for now we have a custom recovery
If someone is willing to cook something interesting that can work with not touching the boot or recovery partitions... then well I would call it a custom rom
In theory it should work on a H950PR? So I can at least test it
maucvs said:
In theory it should work on a H950PR? So I can at least test it
Click to expand...
Click to collapse
Hi, I think it will work. You'll need to be rooted and You can give it a try ?
Sent from my LG-H955 using XDA-Developers Legacy app
It should work..
I already tried this on h950 but there is dead android with red '!' ..
For some reason it wont boot into the fishrecovery and goes to the recovery partition..
Ill try smth when i have time.
adds08 said:
It should work..
I already tried this on h950 but there is dead android with red '!' ..
For some reason it wont boot into the fishrecovery and goes to the recovery partition..
Ill try smth when i have time.
Click to expand...
Click to collapse
Seams like the twrp I build is not liking h950
Sent from my LG-H955 using XDA-Developers Legacy app
I'll try to make h950 tree and build a test twrp.
Sent from my LG-H955 using XDA-Developers Legacy app
adds08 said:
It should work..
I already tried this on h950 but there is dead android with red '!' ..
For some reason it wont boot into the fishrecovery and goes to the recovery partition..
Ill try smth when i have time.
Click to expand...
Click to collapse
Can you test this... made a h950 test tree. The twrp boots on my h955 also.
ergo911 said:
Seams like the twrp I build is not liking h950
Click to expand...
Click to collapse
I had a similar issue for the g4 and here it was FIsH because it was too slow for some devices . I will release a new FIsH release which improves speed dramatically asap.
.
Sent from my LG-H815 using XDA Labs
Thanks ?
ergo911 said:
Thanks ?
Click to expand...
Click to collapse
Ok so please use git pull to get the latest updates!
Lemme know if you have any trouble.
.
Sent from my LG-H815 using XDA Labs
ergo911 said:
Can you test this... made a h950 test tree. The twrp boots on my h955 also.
Click to expand...
Click to collapse
Works like a charm on my H950. Thanks! The only issue is TWRP booting time, but it's should be right that, if I understand correctly.
Thank you!
HI Guys , its me again so after a long working night of disabling encryptions and verifications i finaly was able to boot a AOSP Generic System Image on my LG G7 (EUROPEAN VARIANT ONLY) and now im here to show you how to install
How to install ?
Download the GSI from PHH AOSP thread , take a/b ones with ot without gapps as you like
Download my SecuretyOff-Vendor-image and my Permissive boot.img
Reboot to fastboot and unlock your bootloader if you havent done it yet (you can find tutorials online, same method as on g6 and previous)
flash the magisk enabled securetyoff permissive kernel with the command "fastboot flash boot_a pathtoimghere"
Reboot your G7 to LG Stock os and install magisk manager and TerminalEmulator from PlayStore
Now copy the Downloaded Vendor file to your internal sdcard and rename it to vendor.img
Open TerminalEmulator (adb shell works aswell) and type su, hit enter, then type "dd if=/sdcard/vendor.img of=/dev/block/bootdevice/by-name/vendor_a" , hit enter m this will take some time pls be patient
Once youre done with flashing the new vendor reboot to fastboot again and flash the GSI with the following command "fastboot flash system_a pathtoimghere"
One last step before you can enjoy AOSP type "fastboot -w" and then "fastboot reboot"
Whats Working ?
So for me everyting works so far i just noticed 2 small bugs till now
1. the Notification LED wont stop blinking (im on that already)
2.sometimes the display turns black for about 0,5secs
3. if your headphone jack doesn't work open up a root shell and enter "setprop persist.sys.overlay.devinputjack true"
Credits
Me for testing and patching the **** out of that boot.img and vendor.img
AutoPrime for his G7 system Dump
Phhuson for his brilliant work on GSI's
Zefie for recommending me the right tool to repack kernel without bootloops (xD)
SGMarkus for providing ideas and additional Help
reserved
reserved 2
Update , Ressurection Remix Gsi and LineageOS Gsi work too , also i was able to fix the blinking led , but it doesnt work at all anymore (lights hal doesnt load will investiagte tomorrow) but RR or Los doesnt have gapps packed with them so you will need to wait for twrp to be ready (i think i will finish it in next few days)
J0SH1X said:
HI Guys , its me again so after a long working night of disabling encryptions and verifications i finaly was able to boot a AOSP Generic System Image on my LG G7 (EUROPEAN VARIANT ONLY) and now im here to show you how to install
How to install ?
Download the GSI from PHH AOSP thread , take a/b ones with ot without gapps as you like
Download my SecuretyOff-Vendor-image and my Permissive boot.img
Reboot to fastboot and unlock your bootloader if you havent done it yet (you can find tutorials online, same method as on g6 and previous)
flash the magisk enabled securetyoff permissive kernel with the command "fastboot flash boot_a pathtoimghere"
Reboot your G7 to LG Stock os and install magisk manager and TerminalEmulator from PlayStore
Now copy the Downloaded Vendor file to your internal sdcard and rename it to vendor.img
Open TerminalEmulator (adb shell works aswell) and type su, hit enter, then type "dd if=/sdcard/vendor.img of=/dev/block/bootdevice/by-name/vendor_a" , hit enter m this will take some time pls be patient
Once youre done with flashing the new vendor reboot to fastboot again and flash the GSI with the following command "fastboot flash system_a pathtoimghere"
One last step before you can enjoy AOSP type "fastboot -w" and then "fastboot reboot"
Whats Working ?
So for me everyting works so far i just noticed 2 small bugs till now
1. the Notification LED wont stop blinking (im on that already)
2.sometimes the display turns black for about 0,5secs
Credits
Me for testing and patching the **** out of that boot.img and vendor.img
AutoPrime for his G7 system Dump
Phhuson for his brilliant work on GSI's
Zefie for recommending me the right tool to repack kernel without bootloops (xD)
SGMarkus for providing ideas and additional Help
Click to expand...
Click to collapse
Amazing work friend
What about the rom with the DAC? I can change this in the settings of the sound more precise. So not like the lg rom, the preset sound profiles?
Look forward to this! Many thanks +++
what about the dac? sound does not work over jack connection.
Hi.
Does the wide camera work with this rom?
And does the radio fm work?
Where can I find the last release?
Thanks.
Sent from my LM-G710 using Tapatalk
ricxgp said:
Hi.
Does the wide camera work with this rom?
And does the radio fm work?
Where can I find the last release?
Thanks.
Sent from my LM-G710 using Tapatalk
Click to expand...
Click to collapse
wide angle works on aosp rom , fm radio idk but try , you can find the latest release in treble enabled device section of xda
Any word on AOSP 9? As far as I know it requires vndk 8.1 but the g7 launched with Android 8. Do we have to wait for Android 8.1/9 from LG for AOSP 9?
https://highonandroid.com/android-r...oject-treble-unlocked-bootloader-twrp-method/
I saw a video on youtube by max lee i do believe he said you could install this as long as you had twrp recover
I have the sprint verison so i cant try but if anyone with twrp can try and comment
LameMonster82 said:
Any word on AOSP 9? As far as I know it requires vndk 8.1 but the g7 launched with Android 8. Do we have to wait for Android 8.1/9 from LG for AOSP 9?
Click to expand...
Click to collapse
does not work will maybe never work
Guys, can anyone pls do this in adb (or if you have root with terminal app):
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms >/sdcard/kallsyms.txt
UltraM8 said:
Guys, can anyone pls do this in adb (or if you have root with terminal app):
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms >/sdcard/kallsyms.txt
Click to expand...
Click to collapse
With the stock ROM or with aosp?
LameMonster82 said:
With the stock ROM or with aosp?
Click to expand...
Click to collapse
Doesn't really matter
so the headphone jack is now fixed open up a root shell and type setprop persist.sys.overlay.devinputjack true then reboot and it will work
UltraM8 said:
Guys, can anyone pls do this in adb (or if you have root with terminal app):
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms >/sdcard/kallsyms.txt
Click to expand...
Click to collapse
Hello, sorry for being so late but i finaly got the files that youre looking for. "Kptr_restrict" is attached in the post but "kallsyms" is too big so i uploaded it to my google drive. The link is:
https://drive.google.com/file/d/1Mn9jeS7n681dbRWvZqlundCuTAvNF4FJ/view?usp=drivesdk
LameMonster82 said:
Hello, sorry for being so late but i finaly got the files that youre looking for. "Kptr_restrict" is attached in the post but "kallsyms" is too big so i uploaded it to my google drive. The link is:
https://drive.google.com/file/d/1Mn9jeS7n681dbRWvZqlundCuTAvNF4FJ/view?usp=drivesdk
Click to expand...
Click to collapse
thx man!
LameMonster82 said:
Hello, sorry for being so late but i finaly got the files that youre looking for. "Kptr_restrict" is attached in the post but "kallsyms" is too big so i uploaded it to my google drive. The link is:
https://drive.google.com/file/d/1Mn9jeS7n681dbRWvZqlundCuTAvNF4FJ/view?usp=drivesdk
Click to expand...
Click to collapse
I've checked kallsyms, how did you get it? via terminal app, or adb (or even twrp maybe if it's possible on g7)? The prob is that functions addresses are zeros, that's not good.