Where are the jars in XposedInstaller from? - Xposed General

I started digging a little inside https://github.com/rovo89/XposedInstaller source code and would like to know where they are from.
Code:
286987 48 -rw-r--r-- 1 47645 Jan 25 13:46 ./libs/libsuperuser-185868.jar
286985 32 -rw-r--r-- 1 30181 Jan 25 13:46 ./libs/StickyListHeaders-d7f6fc.jar
286986 632 -rw-r--r-- 1 644520 Jan 25 13:46 ./libs/android-support-v13.jar
287177 1160 -rw-r--r-- 1 1184741 Jan 25 13:46 ./tools/signapk.jar
286973 100 -rw-r--r-- 1 98482 Jan 25 13:46 ./assets/XposedBridge.jar
286983 4 -rw-r--r-- 1 3191 Jan 25 13:46 ./lib/AndroidHiddenAPI.jar
Are some jar official google ones and from AOSP? From other rovo89 repositories?

Related

[DEV]Sprint One Partition Layout

Got my One from HTC, dev unlocked, and am already underway Here is some useful info for devs...
Code:
[email protected]:/ $ cat /proc/emmc
dev: size erasesize name
mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p36: 00fffe00 00000200 "recovery"
mmcblk0p35: 01000000 00000200 "boot"
mmcblk0p37: 73fffc00 00000200 "system"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p38: 27fffe00 00000200 "cache"
mmcblk0p39: 680000000 00000200 "userdata"
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p33: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p29: 00040000 00000200 "skylink"
mmcblk0p30: 01900000 00000200 "carrier"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p32: 034ffa00 00000200 "reserve_2"
mmcblk0p34: 05fffc00 00000200 "reserve_3"
mmcblk0p31: 04729a00 00000200 "reserve"
Code:
[email protected]:/ $ cat /proc/partitions ls -la /dev/block/platform/dw_mmc/by-name
major minor #blocks name
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 130671 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16 mmcblk0p5
179 6 256 mmcblk0p6
179 7 15577 mmcblk0p7
179 8 256 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 256 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 2080 mmcblk0p12
179 13 5120 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 61441 mmcblk0p16
179 17 8190 mmcblk0p17
179 18 32768 mmcblk0p18
179 19 1022 mmcblk0p19
179 20 4096 mmcblk0p20
179 21 4096 mmcblk0p21
179 22 20480 mmcblk0p22
179 23 4 mmcblk0p23
179 24 256 mmcblk0p24
179 25 16 mmcblk0p25
179 26 1280 mmcblk0p26
179 27 64 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 256 mmcblk0p29
179 30 25600 mmcblk0p30
179 31 72870 mmcblk0p31
179 32 54270 mmcblk0p32
179 33 76800 mmcblk0p33
179 34 98303 mmcblk0p34
179 35 16384 mmcblk0p35
179 36 16383 mmcblk0p36
179 37 1900543 mmcblk0p37
179 38 655359 mmcblk0p38
179 39 27262976 mmcblk0p39
Code:
[email protected]:/ # fdisk -l /dev/block/mmcblk0
Warning: deleting partitions after 60
Disk /dev/block/mmcblk0: 31.2 GB, 31268536320 bytes
1 heads, 16 sectors/track, 3816960 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 17 128 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 17 49 256 51 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 49 16382 130671 5d Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 16382 3816960 30404624 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 16383 16384 16 5a Unknown
/dev/block/mmcblk0p6 16385 16417 256 73 Unknown
/dev/block/mmcblk0p7 16417 18364 15577+ 5b Unknown
/dev/block/mmcblk0p8 18364 18396 256 5c Unknown
/dev/block/mmcblk0p9 18396 18524 1024 45 Unknown
/dev/block/mmcblk0p10 18524 18556 256 47 Unknown
/dev/block/mmcblk0p11 18556 18812 2048 46 Unknown
/dev/block/mmcblk0p12 18812 19072 2080+ 4c Unknown
/dev/block/mmcblk0p13 19072 19712 5120 34 Unknown
/dev/block/mmcblk0p14 19712 19840 1024 36 Unknown
/dev/block/mmcblk0p15 19840 19968 1024 0 Empty
/dev/block/mmcblk0p16 19968 27649 61441 50 Unknown
/dev/block/mmcblk0p17 27649 28672 8190+ 74 Unknown
/dev/block/mmcblk0p18 28673 32768 32768 0 Empty
/dev/block/mmcblk0p19 32769 32896 1022+ 76 Unknown
/dev/block/mmcblk0p20 32896 33408 4096 4a Unknown
/dev/block/mmcblk0p21 33409 33920 4096 4b Unknown
/dev/block/mmcblk0p22 33921 36481 20480 19 Unknown
/dev/block/mmcblk0p23 36481 36481 4 0 Empty
/dev/block/mmcblk0p24 36481 36513 256 23 Unknown
/dev/block/mmcblk0p25 36513 36515 16 0 Empty
/dev/block/mmcblk0p26 36515 36675 1280+ 0 Empty
/dev/block/mmcblk0p27 36675 36683 64 0 Empty
/dev/block/mmcblk0p28 36684 36811 1024 0 Empty
/dev/block/mmcblk0p29 36812 36844 256 0 Empty
/dev/block/mmcblk0p30 36844 40044 25600 83 Linux
/dev/block/mmcblk0p31 40044 49152 72870+ 0 Empty
/dev/block/mmcblk0p32 49153 55936 54270+ 0 Empty
/dev/block/mmcblk0p33 55936 65536 76800+ 77 Unknown
/dev/block/mmcblk0p34 65537 77824 98303 0 Empty
/dev/block/mmcblk0p35 77825 79872 16384 48 Unknown
/dev/block/mmcblk0p36 79873 81920 16383+ 71 Unknown
/dev/block/mmcblk0p37 81921 319488 1900543 83 Linux
/dev/block/mmcblk0p38 319489 401408 655359+ 83 Linux
/dev/block/mmcblk0p39 401409 3809280 27262976 83 Linux
/dev/block/mmcblk0p40 16383 16384 16 5a Unknown
/dev/block/mmcblk0p41 16385 16417 256 73 Unknown
/dev/block/mmcblk0p42 16417 18364 15577+ 5b Unknown
/dev/block/mmcblk0p43 18364 18396 256 5c Unknown
/dev/block/mmcblk0p44 18396 18524 1024 45 Unknown
/dev/block/mmcblk0p45 18524 18556 256 47 Unknown
/dev/block/mmcblk0p46 18556 18812 2048 46 Unknown
/dev/block/mmcblk0p47 18812 19072 2080+ 4c Unknown
/dev/block/mmcblk0p48 19072 19712 5120 34 Unknown
/dev/block/mmcblk0p49 19712 19840 1024 36 Unknown
/dev/block/mmcblk0p50 19840 19968 1024 0 Empty
/dev/block/mmcblk0p51 19968 27649 61441 50 Unknown
/dev/block/mmcblk0p52 27649 28672 8190+ 74 Unknown
/dev/block/mmcblk0p53 28673 32768 32768 0 Empty
/dev/block/mmcblk0p54 32769 32896 1022+ 76 Unknown
/dev/block/mmcblk0p55 32896 33408 4096 4a Unknown
/dev/block/mmcblk0p56 33409 33920 4096 4b Unknown
/dev/block/mmcblk0p57 33921 36481 20480 19 Unknown
/dev/block/mmcblk0p58 36481 36481 4 0 Empty
/dev/block/mmcblk0p59 36481 36513 256 23 Unknown
/dev/block/mmcblk0p60 36513 36515 16 0 Empty
Enjoy
Nice I was going to wait on the S4 but I think I'm diving into this, thanks and may the force be with you. You do great work.
Where for you pick up your dev edition from?
Sent from my Evo 3D CDMA using Tapatalk 2
Paleryder said:
Nice I was going to wait on the S4 but I think I'm diving into this, thanks and may the force be with you. You do great work.
Where for you pick up your dev edition from?
Sent from my Evo 3D CDMA using Tapatalk 2
Click to expand...
Click to collapse
It was sent to me from HTC
-viperboy- said:
It was sent to me from HTC Elevate
Click to expand...
Click to collapse
In the next cycle they said they were going to accept new ppl in the that program... Have they started accepting?
Sent from my 5th Dimension eVo 3D
*Team 420 band of Misfits*
miggsr said:
In the next cycle they said they were going to accept new ppl in the that program... Have they started accepting?
Sent from my 5th Dimension eVo 3D
*Team 420 band of Misfits*
Click to expand...
Click to collapse
Nope, didn't even know they were going to.
Any chance you can dd mmcblk0p3, p4, p5 and p30 and upload them?
Also this is a partition layout that will have really good info. Need root with busybox installed.
fdisk -l /dev/block/mmcblk0
Can you post those results? Don't worry about dding those partitions, that can wait until Friday. Thank you for getting the disk tho!
Sent from my SPH-L710 using Tapatalk 2
18th.abn said:
Any chance you can dd mmcblk0p3, p4, p5 and p30 and upload them?
Click to expand...
Click to collapse
Here you go:
https://www.dropbox.com/sh/eymkva9qmtbtuh2/ETpX8Xcnmu
Also this is a partition layout that will have really good info. Need root with busybox installed.
fdisk -l /dev/block/mmcblk0
Can you post those results? Don't worry about dding those partitions, that can wait until Friday. Thank you for getting the disk tho!
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Added to OP
Thx a bunch. The extended partition table is pretty much identical to the one x. Also thx for the partitions. I got them so you can pull them down.
Sent from my SPH-L710 using Tapatalk 2
Nice, Viper got a one... So this means I'll be rocking viperrom again?
Sent from my PG86100 using xda app-developers app
Konfuzion said:
Nice, Viper got a one... So this means I'll be rocking viperrom again?
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
It's already being worked on, svn is about 30+ revisions deep. Maybe an early beta on launch day, we'll see
Sent from my HTCONE using Tapatalk 2
You mean like...you ordered the developer version and paid for it, or you sign up somewhere and they pick people to send them to.
Because...er...I would sure like to have one. I really want to try porting MIUI to it. There's already a CM10 alpha for it, which is mostly all I'd need.
If there's a site to sign up, can you point me in that direction?
digitalhigh said:
You mean like...you ordered the developer version and paid for it, or you sign up somewhere and they pick people to send them to.
Because...er...I would sure like to have one. I really want to try porting MIUI to it. There's already a CM10 alpha for it, which is mostly all I'd need.
If there's a site to sign up, can you point me in that direction?
Click to expand...
Click to collapse
It's not like everyone got a free phone, they picked a certain small amount of people and sent it to them. And it's not an open enrollment thing.
-viperboy- said:
It's not like everyone got a free phone, they picked a certain small amount of people and sent it to them. And it's not an open enrollment thing.
Click to expand...
Click to collapse
Whod bring cm10 its outdated
pbedard said:
Whod bring cm10 its outdated
Click to expand...
Click to collapse
?
Sent from my HTCONE using Tapatalk 2
pbedard said:
Whod bring cm10 its outdated
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC ONE using Tapatalk 2
You know he meant 10.1
Sent from my HTCONE using xda app-developers app
youkosnake said:
You know he meant 10.1
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
I don't even know what he said.
Sent from my HTCONE using Tapatalk 2
-viperboy- said:
I don't even know what he said.
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
Lol. I meant to quote. I was talking to him.
Translation: "Who'd bring CM10 to the HTC one? CM10.1 is out, so 10 is outdated."
Sent from my HTCONE using xda app-developers app
you can add mmcblk0p12 to the OP for hboot
thx joeykrim for the info & getting support for ruuveal
Mmcblk0p1- sbl1
Mmcblk0p2 - sbl2
Mmcblk0p9 n sbl3

Backlight notification in MIUI and slowdown

Hello. I install MIUI version 4.1.24 based on Android 4.2.2. Why Lg backlight notification dont working and why this rom have slowdown animations ??
Log from lg notification :
Code:
Thu Jan 30 22:48:43 CET 2014 :: start :: Starting new log
Thu Jan 30 22:48:54 CET 2014 :: debug :: Screen on: false
Thu Jan 30 22:48:54 CET 2014 :: debug :: onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_SCREEN_OFF
Thu Jan 30 22:48:54 CET 2014 :: debug :: Unregister sensor MPL accel
Thu Jan 30 22:49:05 CET 2014 :: debug :: Screen on: true
Thu Jan 30 22:49:05 CET 2014 :: debug :: onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_SCREEN_ON
Thu Jan 30 22:49:05 CET 2014 :: debug :: onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_USER_INTERACTION
Thu Jan 30 22:49:05 CET 2014 :: debug :: pnn: false
Thu Jan 30 22:50:48 CET 2014 :: debug :: Screen on: false
Thu Jan 30 22:50:48 CET 2014 :: debug :: onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_SCREEN_OFF
Thu Jan 30 22:50:48 CET 2014 :: debug :: Unregister sensor MPL accel
Thu Jan 30 22:51:08 CET 2014 :: debug :: Screen on: true
Thu Jan 30 22:51:08 CET 2014 :: debug :: onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_SCREEN_ON
Thu Jan 30 22:51:21 CET 2014 :: debug :: onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_USER_INTERACTION
Thu Jan 30 22:51:21 CET 2014 :: debug :: pnn: false
Thu Jan 30 22:51:52 CET 2014 :: debug :: Screen on: false
Thu Jan 30 22:51:52 CET 2014 :: debug :: onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_SCREEN_OFF
Thu Jan 30 22:51:52 CET 2014 :: debug :: Unregister sensor MPL accel
Thu Jan 30 22:51:55 CET 2014 :: debug :: Screen on: true
Thu Jan 30 22:51:55 CET 2014 :: debug :: onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_SCREEN_ON
Thu Jan 30 22:52:26 CET 2014 :: debug :: Screen on: false
Thu Jan 30 22:52:26 CET 2014 :: debug :: onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_SCREEN_OFF
Thu Jan 30 22:52:26 CET 2014 :: debug :: Unregister sensor MPL accel
Thu Jan 30 22:52:45 CET 2014 :: debug :: Screen on: true
Thu Jan 30 22:52:45 CET 2014 :: debug :: onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_SCREEN_ON
Thu Jan 30 22:52:46 CET 2014 :: debug :: onStartCommand() com.martinborjesson.o2xtouchlednotifications.services.MainService.ACTION_USER_INTERACTION
Thu Jan 30 22:52:46 CET 2014 :: debug :: pnn: false

major minor #blocks name

major minor #blocks name
253 0 1048576 vnswap0
179 0 15388672 mmcblk0
179 1 15360 mmcblk0p1
179 2 58816 mmcblk0p2
179 3 512 mmcblk0p3
179 4 64 mmcblk0p4
179 5 32 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 3072 mmcblk0p9
179 10 7136 mmcblk0p10
179 11 10240 mmcblk0p11
179 12 14336 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 3072 mmcblk0p14
179 15 13312 mmcblk0p15
179 16 15360 mmcblk0p16
179 17 13312 mmcblk0p17
179 18 7159 mmcblk0p18
179 19 1 mmcblk0p19
179 20 8 mmcblk0p20
179 21 8192 mmcblk0p21
179 22 9216 mmcblk0p22
179 23 2406400 mmcblk0p23
179 24 153600 mmcblk0p24
179 25 10240 mmcblk0p25
179 26 12628975 mmcblk0p26
179 32 512 mmcblk0rpmb

Need tech names of partition. I attached a piture of myapp i am attemting. To prope

I need the boot partition, data partition and and systems partition.
I ran this in terminal. And it pokes out this.
[email protected]:/ $ cat /proc/partitions
major minor #blocks name
7 0 4190 loop0
7 1 2111 loop1
7 2 8348 loop2
7 3 2111 loop3
7 4 13545 loop4
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 1024 mmcblk0p6
179 7 16384 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 1 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 1 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 32768 mmcblk0p14
179 15 16384 mmcblk0p15
179 16 3072 mmcblk0p16
179 17 512 mmcblk0p17
179 18 512 mmcblk0p18
179 19 1 mmcblk0p19
179 20 512 mmcblk0p20
179 21 8192 mmcblk0p21
179 22 8192 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 32768 mmcblk0p24
179 25 32768 mmcblk0p25
179 26 32768 mmcblk0p26
179 27 32768 mmcblk0p27
179 28 8192 mmcblk0p28
179 29 2048 mmcblk0p29
179 30 512 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 1024 mmcblk0p32
259 1 8 mmcblk0p33
259 2 3407872 mmcblk0p34
259 3 819200 mmcblk0p35
259 4 81920 mmcblk0p36
259 5 16384 mmcblk0p37
259 6 25739264 mmcblk0p38
259 7 12271 mmcblk0p39
179 32 4096 mmcblk0rpmb
254 0 4189 dm-0
254 1 2110 dm-1
254 2 8347 dm-2
254 3 2110 dm-3
254 4 13545 dm-4
[email protected]:/ $
*
Sent from my LG-D959 using XDA Premium 4 mobile app
streetmedic said:
I need the boot partition, data partition and and systems partition.
I ran this in terminal. And it pokes out this.
Whichh one is. Wich
[email protected]:/ $ cajull t /proc/partitions
major minor #blocks name
7 0 4190 loop0
7 1 2111 loop1
7 2 8348 loop2
7 3 2111 loop3
7 4 13545 loop4
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 1024 mmcblk0p6
179 7 16384 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 1 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 1 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 32768 mmcblk0p14
179 15 16384 mmcblk0p15
179 16 3072 mmcblk0p16
179 17 512 mmcblk0p17
179 18 512 mmcblk0p18
179 19 1 mmcblk0p19
179 20 512 mmcblk0p20
179 21 8192 mmcblk0p21
179 22 8192 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 32768 mmcblk0p24
179 25 32768 mmcblk0p25
179 26 32768 mmcblk0p26
179 27 32768 mmcblk0p27
179 28 8192 mmcblk0p28
179 29 2048 mmcblk0p29
179 30 512 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 1024 mmcblk0p32
259 1 8 mmcblk0p33
259 2 3407872 mmcblk0p34
259 3 819200 mmcblk0p35
259 4 81920 mmcblk0p36
259 5 16384 mmcblk0p37
259 6 25739264 mmcblk0p38
259 7 12271 mmcblk0p39
179 32 4096 mmcblk0rpmb
254 0 4189 dm-0
254 1 2110 dm-1
254 2 8347 dm-
254 3 2110 dm-3
254 4 13545 dm-4
[email protected]:/ $
*
[email protected]:/ $ cat /proc/partitions major minor #blocks name 7 0 4190 loop0 7 1 2111 loop1 7 2 8348 loop2 7 3 2111 loop3 7 4 13545 loop4 179 0 30535680 mmcblk0 179 1 65536 mmcblk0p1 179 2 1024 mmcblk0p2 179 3 512 mmcblk0p3 179 4 512 mmcblk0p4 179 5 1024 mmcblk0p5 179 6 1024 mmcblk0p6 179 7 16384 mmcblk0p7 179 8 1024 mmcblk0p8 179 9 1 mmcblk0p9 179 10 3072 mmcblk0p10 179 11 3072 mmcblk0p11 179 12 1 mmcblk0p12 179 13 16384 mmcblk0p13 179 14 32768 mmcblk0p14 179 15 16384 mmcblk0p15 179 16 3072 mmcblk0p16 179 17 512 mmcblk0p17 179 18 512 mmcblk0p18 179 19 1 mmcblk0p19 179 20 512 mmcblk0p20 179 21 8192 mmcblk0p21 179 22 8192 mmcblk0p22 179 23 16384 mmcblk0p23 179 24 32768 mmcblk0p24 179 25 32768 mmcblk0p25 179 26 32768 mmcblk0p26 179 27 32768 mmcblk0p27 179 28 8192 mmcblk0p28 179 29 2048 mmcblk0p29 179 30 512 mmcblk0p30 179 31 1024 mmcblk0p31 259 0 1024 mmcblk0p32 259 1 8 mmcblk0p33 259 2 3407872 mmcblk0p34 259 3 819200 mmcblk0p35 259 4 81920 mmcblk0p36 259 5 16384 mmcblk0p37 259 6 25739264 mmcblk0p38 259 7 12271 mmcblk0p39 179 32 4096 mmcblk0rpmb 254 0 4189 dm-0 254 1 2110 dm-1 254 2 8347 dm-2 254 3 2110 dm-3
Sent from my LG-D959 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my LG-D959 using XDA Premium 4 mobile app
For what ?
Because i need to input the names into this application. And i need to tell it boot partitions name is mmcblk0 boot partition. System and Data and the Misc if there is one . Evxample is boot partition. Path
Is /mmncblk0_10
Sent from my LG-D959 using XDA Premium 4 mobile app
Download "partition table" from play store and under advanced it shows what you want

How To Guide How to compile the OmniROM for the ASUS Zenfone 8

How to compile the OmniROM for the ASUS Zenfone 8
Update 14.11.2022 /bs
This HowTo is about how to compile the OmniROM 12 for the ASUS Zenfone 8 -- see How to compile the OmniROM 13 for the ASUS Zenfone 8 for how to compile the OmniROM 13 for the ASUS Zenfone 8.
Correction
There was a spelling error in the name of the command to list all available targets : the command name is breakfast
Compiling the CustomROM OmniROM from within Linux is a very simple and straight forward process -- the developer for the OmniROM did a really amazing good job setting up the build environment for the OmniROM.
But some information are missing in the instructions (at least I did not found them ...)
Therefor I document here what I did to compile the OmniROM for the ASUS Zenfone 8 on my Linux notebook:
First install the neccessary tool called "repo" to maintain the repositories for the OmniROM ; see here https://gerrit.googlesource.com/git-repo/
Next create a new directory on your PC; switch to that directory, and initialize the necessarry repositories like described in the section "Getting Started" here: https://github.com/omnirom/android :
Note [29.07.2022]:
The repositories for the branch android-12.0 are somehow outdated with the security patch level from February 2022 . To get the code with the security patch level from June 2022 use the repositories for the branch android-12.1.
Bash:
repo init -u https://github.com/omnirom/android.git -b android-12.1
# Then to sync up:
repo sync
Be aware that the repositories need about 140 GB disk space so this will take a while.
Please note that I did not install any additional tool to compile the CustomROM for android - everything neccessary was installed by synching the repositories.
When the download is finished you must add the repositories for the vendor and device tree for your phone to the manifests in the local repositories.
This should be done in the file .repo/local_manifests/local_manifest.xml . For the ASUS Zenfone 8 the file should look like this:
Code:
[[email protected] /data/develop/android/OmniROM]$ cat .repo/local_manifests/local_manifest.xml
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="DonkeyCoyote"
fetch="https://github.com/DonkeyCoyote" />
<project path="device/asus/zenfone8" name="android_device_asus_zenfone8" remote="omnirom" revision="android-12.0" />
<project path="vendor/asus" name="proprietary_vendor_asus" remote="DonkeyCoyote" revision="android-12.1" />
</manifest>
After updating the file local_manifest.xml do another
Bash:
repo sync
to sync the added repositories. This time the download will be faster because only the two additional repos will be downloaded.
Now you can start the build with these commands:
Bash:
. build/envsetup.sh
brunch omni_zenfone8-user
in the directory with the downloaded repositories (use the command "breakfast" instead of "brunch" to see other possible targets)
Note that the first time the compile process will take 4 hours or more. And keep in mind that the compile process will need additional 140 GB for the temporary output files.
If everything is fine there will be a ZIP file with your own CustomROM image in the directory ./out/target/product/zenfone8/ when the compile script is done, e.g:
Code:
[[email protected] /data/develop/android/OmniROM]$ ls -ltr out/target/product/zenfone8/omni-12-20220621-zenfone8-HOMEMADE.zip
-rw-rw-r--. 25 xtrnaw7 xtrnaw7 1253703465 Jun 25 10:03 out/target/product/zenfone8/omni-12-20220621-zenfone8-HOMEMADE.zip
[[email protected] /data/develop/android/OmniROM]$
That image can now be installed on the Zenfone 8 using the LineageOS Recovery or TWRP.
Notes
[Update 29.07.2022]
In case you want to rename the directory with the repositories for OminROM:
Be aware that the make scripts for the OmniROM will create some absolute links in the repo directories in ./out. Therefor you must recreate these links after renaming the directory.
How to create an OmniROM image with MicroG
To create an OmniROM image with MicroG these additional steps are neccesarry:
Add the repo with the prebuild MicroG apks, android_prebuilts_prebuiltapks, to your local_manifests.xml file, e.g:
Code:
[[email protected] /data/develop/android/OmniROM]$ cat .repo/local_manifests/local_manifest.xml
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="DonkeyCoyote"
fetch="https://github.com/DonkeyCoyote" />
<project path="device/asus/zenfone8" name="android_device_asus_zenfone8" remote="omnirom" revision="android-12.0" />
<project path="vendor/asus" name="proprietary_vendor_asus" remote="DonkeyCoyote" revision="android-12.1" />
<project path="vendor/microg" name="android_prebuilts_prebuiltapks" remote="omnirom" revision="android-12.0" />
</manifest>
[[email protected] /data/develop/android/OmniROM]$
Do another repo sync to download the repository for MicroG:
Code:
repo sync
and create the CustomROM using these instructions:
Code:
export ROM_BUILDTYPE=MICROG
brunch omni_zenfone8-user
This will create an OmniROM Image with MicroG already installed, e.g:
Code:
[[email protected] /data/develop/android/OmniROM]$ ls -ltr out/target/product/zenfone8/omni-12-20220621-zenfone8-MICROG.zip
-rw-rw-r--. 25 xtrnaw7 xtrnaw7 1253703465 Jun 25 10:03 out/target/product/zenfone8/omni-12-20220621-zenfone8-MICROG.zip
[[email protected] /data/develop/android/OmniROM]$
Update 29.09.2022 /bs
There seems to be a bug or feature in the scripts to compile OmniROM:
Old versions of the ZIP file with the image in the output directory will always be overwritten or replaced with the current image, e.g.:
Code:
[ OmniRomDev - [email protected] /data/develop/android/test ] $ ls -l /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220*zip
-rw-rw-r--. 20 xtrnaw7 xtrnaw7 1256445293 Sep 27 18:12 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220728-zenfone8-MICROG.zip
-rw-rw-r--. 20 xtrnaw7 xtrnaw7 1256445293 Sep 27 18:12 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220729-zenfone8-MICROG.zip
-rw-rw-r--. 20 xtrnaw7 xtrnaw7 1256445293 Sep 27 18:12 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220804-zenfone8-MICROG.zip
-rw-rw-r--. 20 xtrnaw7 xtrnaw7 1256445293 Sep 27 18:12 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220809-zenfone8-HOMEMADE.zip
-rw-rw-r--. 20 xtrnaw7 xtrnaw7 1256445293 Sep 27 18:12 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220810-zenfone8-MICROG.zip
-rw-rw-r--. 20 xtrnaw7 xtrnaw7 1256445293 Sep 27 18:12 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220820-zenfone8-MICROG.zip
-rw-rw-r--. 20 xtrnaw7 xtrnaw7 1256445293 Sep 27 18:12 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220828-zenfone8-MICROG.zip
-rw-rw-r--. 20 xtrnaw7 xtrnaw7 1256445293 Sep 27 18:12 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220904-zenfone8-MICROG.zip
-rw-rw-r--. 20 xtrnaw7 xtrnaw7 1256445293 Sep 27 18:12 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220911-zenfone8-MICROG.zip
-rw-rw-r--. 20 xtrnaw7 xtrnaw7 1256445293 Sep 27 18:12 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220918-zenfone8-MICROG.zip
-rw-rw-r--. 20 xtrnaw7 xtrnaw7 1256445293 Sep 27 18:12 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220927-zenfone8-MICROG.zip
[ OmniRomDev - [email protected] /data/develop/android/test ] $
[ OmniRomDev - [email protected] /data/develop/android/test ] $ cksum /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220*zip
592627598 1256445293 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220728-zenfone8-MICROG.zip
592627598 1256445293 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220729-zenfone8-MICROG.zip
592627598 1256445293 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220804-zenfone8-MICROG.zip
592627598 1256445293 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220809-zenfone8-HOMEMADE.zip
592627598 1256445293 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220810-zenfone8-MICROG.zip
592627598 1256445293 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220820-zenfone8-MICROG.zip
592627598 1256445293 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220828-zenfone8-MICROG.zip
592627598 1256445293 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220904-zenfone8-MICROG.zip
592627598 1256445293 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220911-zenfone8-MICROG.zip
592627598 1256445293 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220918-zenfone8-MICROG.zip
592627598 1256445293 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220927-zenfone8-MICROG.zip
[ OmniRomDev - [email protected] /data/develop/android/test ]
Update 03.11.2022 /bs
When compiling aborts with error messages like these
Code:
error: vendor/qcom/opensource/interfaces/wifi/supplicant/aidl/Android.bp:16:23: unrecognized property "versions_with_info"
error: vendor/qcom/opensource/interfaces/bluetooth_audio/aidl/Android.bp:17:23: unrecognized property "versions_with_info"
Do a forced repo sync:
Bash:
repo sync --force-sync
and start the compile process again .

Categories

Resources