Database Info

Alcatel LTE One Touch Sonic

Hi to start id like to say F androidarea51.com they are little cry baby's on a power trip and banning ppl like crazy for no reason...anyways i have recenty purchased a Alcatel LTE One Touch Sonic on 4.1.2 and have been trying to find some help porting CWM to my device. I have MANAGED to pull the boot.img,system.img and recovery.img from my device. I rooted with SRS-Root which can be found here http://download.unlocksamsungonline.nl/~xtrusion/SRSRoot-Setup.exe
I have uploaded and decompled system.img,boot.img and recovery.img which can be found here http://www.mediafire.com/download/2nt0nt9tjrw449f/AlcatelIMG.rar
Once you open the extracted recovery.img you may notice that the fstab is a lil different than lower version android OS's and does not list the partitions name...I will provide a txt file within the next couple of days with the proper partition names and mmcblocks...
If anyone is willing to help me port CWM for this device please feel free to contact me via email or reply with a comment
[email protected]
Ps the system.img has been slightly modified it is rooted and is not stock...I changed some props to change the android OS version id and device id..
___________________________________________________________________________________________________
/dev/block/platform/msm_sdcc.1
lrwxrwxrwx root root 1969-12-31 20:27 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1969-12-31 20:27 abootbk -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1969-12-31 20:27 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1969-12-31 20:27 cache -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1969-12-31 20:27 fota -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1969-12-31 20:27 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1969-12-31 20:27 grow -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1969-12-31 20:27 iqap -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1969-12-31 20:27 iqbp -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1969-12-31 20:27 misc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1969-12-31 20:27 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1969-12-31 20:27 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1969-12-31 20:27 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1969-12-31 20:27 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1969-12-31 20:27 persist -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1969-12-31 20:27 recovery -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1969-12-31 20:27 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1969-12-31 20:27 rpmbk -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1969-12-31 20:27 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1969-12-31 20:27 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1969-12-31 20:27 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1969-12-31 20:27 sbl3bk -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1969-12-31 20:27 ssd -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1969-12-31 20:27 system -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1969-12-31 20:27 traceability -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1969-12-31 20:27 tunning -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1969-12-31 20:27 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1969-12-31 20:27 tzbk -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1969-12-31 20:27 userdata -> /dev/block/mmcblk0p13
-------------------------------------------------------------------------------------------------------------------------------------------
/dev/block/platform/msm_sdcc.3
lrwxrwxrwx root root 1969-12-31 20:27 p1 -> /dev/block/mmcblk1p1
___________________________________________________________________________________________________
Model: MMC 004G90 (sd/mmc)
Disk /dev/block/mmcblk0: 3959MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 67.1MB 134MB 67.1MB fat16 modem
2 134MB 134MB 131kB sbl1
3 134MB 135MB 262kB sbl2
4 135MB 135MB 524kB sbl3
5 135MB 136MB 524kB aboot
6 136MB 136MB 524kB rpm
7 201MB 212MB 10.5MB boot
8 268MB 269MB 524kB tz
9 269MB 269MB 1024B pad
10 269MB 272MB 3146kB modemst1
11 272MB 275MB 3146kB modemst2
12 336MB 1409MB 1074MB ext4 system
13 1409MB 3288MB 1879MB ext4 userdata
14 3288MB 3297MB 8389kB ext4 persist
15 3297MB 3632MB 336MB ext4 cache
16 3691MB 3692MB 1049kB misc
17 3758MB 3769MB 10.5MB recovery
18 3769MB 3772MB 3146kB fsg
19 3825MB 3825MB 8192B ssd
20 3825MB 3826MB 524kB sbl3bk
21 3826MB 3826MB 524kB abootbk
22 3826MB 3829MB 3146kB tunning
23 3829MB 3830MB 1049kB traceability
24 3830MB 3847MB 16.8MB fota
25 3847MB 3848MB 524kB rpmbk
26 3848MB 3848MB 524kB tzbk
27 3848MB 3849MB 1049kB iqbp
28 3849MB 3856MB 6291kB ext4 iqap
29 3856MB 3959MB 104MB grow
___________________________________________________________________________________________________
I managed to get adb to work with full root access with the device powered off! the downside is there is no working recovery..i wiill leave a download link if anyone would like to see it for themselves however I AM NOT RESPONSIBLE if this ruins your device..Neverthe less im 99.9% positive nothing bad wil happen to your devices otherwise i would not leave a download link to it...
https://www.mediafire.com/?fna3sj08rsdv7w7
-------------------------------------------------------------------------------------------------------------------------------------------
MAKE SURE YOUR SYSTEM IS MOUNTED RW
adb shell
su
busybox mount -o remount,rw system system
-------------------------------------------------------------------------------------------------------------------------------------------
adb push recovery.img /system/bin
adb shell
su
dd if=/system/bin/recovery.img of=/dev/block/mmcblk0p17
rm /system/bin/recovery.img
-------------------------------------------------------------------------------------------------------------------------------------------
busybox poweroff
adb devices
adb shell
su
ls
------------------------------------------------------------------------------------------------------------------------------------------------------------------

Alcatel one touch sonic
I used kingroot to root my Alcatel one touch sonic, but now that I did, do I need the CWM or the other recovery app? Also, how can I flash my ROM? OK still can't find much on this. Did you get that cwm to work? If so could you dumb it Down lol! This is my first root

Hello There
i just brick my phone trying to get rip of a gosh virus wich installs apps on system...
and well now phone is stuck inTracfone logo
is there any way to restore my phone using ur system.img?
i set a fastboot adb and drivers
but the only thing i can do is "adb shell", where i can look into the phone directory
adb fastboot or fastboot flash system system.im is not working
if u can help me pliz that will be nice ><

How does one edit the bootsplash for metropcs lg f60 (ms395)?

How does one edit the bootsplash for metropcs lg f60 (ms395)?
I've seen other posts that say to flash a raw image to the
Code:
splash
or
Code:
splash1
partition, but I don't see one on the ms395.
output of
Code:
ls -l /dev/block/platform/*/by-name
:
Code:
DDR -> /dev/block/mmcblk0p21
aboot -> /dev/block/mmcblk0p6
abootb -> /dev/block/mmcblk0p9
boot -> /dev/block/mmcblk0p16
cache -> /dev/block/mmcblk0p32
drm -> /dev/block/mmcblk0p24
eksst -> /dev/block/mmcblk0p30
encrypt -> /dev/block/mmcblk0p22
factory -> /dev/block/mmcblk0p26
fota -> /dev/block/mmcblk0p27
fsc -> /dev/block/mmcblk0p19
fsg -> /dev/block/mmcblk0p18
grow -> /dev/block/mmcblk0p34
laf -> /dev/block/mmcblk0p15
misc -> /dev/block/mmcblk0p13
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p11
modemst2 -> /dev/block/mmcblk0p12
mpt -> /dev/block/mmcblk0p29
pad -> /dev/block/mmcblk0p10
persist -> /dev/block/mmcblk0p14
rct -> /dev/block/mmcblk0p23
recovery -> /dev/block/mmcblk0p17
rpm -> /dev/block/mmcblk0p3
rpmb -> /dev/block/mmcblk0p7
sbl1 -> /dev/block/mmcblk0p2
sbl1b -> /dev/block/mmcblk0p28
sdi -> /dev/block/mmcblk0p5
sns -> /dev/block/mmcblk0p25
ssd -> /dev/block/mmcblk0p20
system -> /dev/block/mmcblk0p31
tz -> /dev/block/mmcblk0p4
tzb -> /dev/block/mmcblk0p8
userdata -> /dev/block/mmcblk0p33
I looked at the boot ramdisk but I only found images displayed for charging the battery.
Thanks.

[URGENT] Requesting Bootloader dump image for HD 10 (2017)?

Hi, I want to (urgently) investigate the bootloader internals of recent Fire devices, so please provide me with a bootloader dump in Fire HD 10 (2017). Here's how to get it;
Get into an ADB command prompt/terminal.
Type the commands in this order;
Code:
adb shell
Code:
su
Code:
cd /dev/block/bootdevice/by-name
Code:
ls -all
Try to find the bootloader image, this is kind of hard. It's usually named as 'aboot'. If you fail to find that then please copy paste the result of the last command, I will try to guess what it is.
If you somehow notices the correct one, look at the text in front of it, in form of "/dev/block/****", and type;
Code:
dd if=/dev/block/**** of=/sdcard/Download/aboot.img
Of course replace the stars with your partition.
(aboot.img works universally I think because the dump name doesn't matter, if that doesn't work, replace aboot.img with [YOUR-ABOOT-ALTERNATIVE].img replacing with the bootloader image text you found above).
Upload the resulting .img file in a post in this thread quickly as possible!
Thank you!

I'm not very good at this, but I can try to help. Not sure which file(s) to grab.
I got the following in /dev/block/platform/soc/by-name
lrwxrwxrwx root root 2018-02-22 22:47 MISC -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2018-02-22 22:47 PMT -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2018-02-22 22:47 boot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2018-02-22 22:47 boot0hdr0 -> /dev/block/mmcblk0boot0p1
lrwxrwxrwx root root 2018-02-22 22:47 boot0hdr1 -> /dev/block/mmcblk0boot0p2
lrwxrwxrwx root root 2018-02-22 22:47 boot0img0 -> /dev/block/mmcblk0boot0p3
lrwxrwxrwx root root 2018-02-22 22:47 boot0img1 -> /dev/block/mmcblk0boot0p4
lrwxrwxrwx root root 2018-02-22 22:47 cache -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2018-02-22 22:47 dkb -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2018-02-22 22:47 kb -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2018-02-22 22:47 lk -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2018-02-22 22:47 metadata -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2018-02-22 22:47 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2018-02-22 22:47 recovery -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2018-02-22 22:47 reserved -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2018-02-22 22:47 system -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2018-02-22 22:47 tee1 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2018-02-22 22:47 tee2 -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2018-02-22 22:47 userdata -> /dev/block/mmcblk0p15

luvboox said:
I'm not very good at this, but I can try to help. Not sure which file(s) to grab.
I got the following in /dev/block/platform/soc/by-name
lrwxrwxrwx root root 2018-02-22 22:47 MISC -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2018-02-22 22:47 PMT -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2018-02-22 22:47 boot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2018-02-22 22:47 boot0hdr0 -> /dev/block/mmcblk0boot0p1
lrwxrwxrwx root root 2018-02-22 22:47 boot0hdr1 -> /dev/block/mmcblk0boot0p2
lrwxrwxrwx root root 2018-02-22 22:47 boot0img0 -> /dev/block/mmcblk0boot0p3
lrwxrwxrwx root root 2018-02-22 22:47 boot0img1 -> /dev/block/mmcblk0boot0p4
lrwxrwxrwx root root 2018-02-22 22:47 cache -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2018-02-22 22:47 dkb -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2018-02-22 22:47 kb -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2018-02-22 22:47 lk -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2018-02-22 22:47 metadata -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2018-02-22 22:47 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2018-02-22 22:47 recovery -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2018-02-22 22:47 reserved -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2018-02-22 22:47 system -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2018-02-22 22:47 tee1 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2018-02-22 22:47 tee2 -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2018-02-22 22:47 userdata -> /dev/block/mmcblk0p15
Click to expand...
Click to collapse
Uhhh, I'm not sure either. One of Amazon's obscure modifications. :crying::crying:

Supersonic27543 said:
Uhhh, I'm not sure either. One of Amazon's obscure modifications. :crying::crying:
Click to expand...
Click to collapse
Also, try "reserved" please? Thanks!

luvboox said:
I'm not very good at this, but I can try to help. Not sure which file(s) to grab.
I got the following in /dev/block/platform/soc/by-name
lrwxrwxrwx root root 2018-02-22 22:47 MISC -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2018-02-22 22:47 PMT -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2018-02-22 22:47 boot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2018-02-22 22:47 boot0hdr0 -> /dev/block/mmcblk0boot0p1
lrwxrwxrwx root root 2018-02-22 22:47 boot0hdr1 -> /dev/block/mmcblk0boot0p2
lrwxrwxrwx root root 2018-02-22 22:47 boot0img0 -> /dev/block/mmcblk0boot0p3
lrwxrwxrwx root root 2018-02-22 22:47 boot0img1 -> /dev/block/mmcblk0boot0p4
lrwxrwxrwx root root 2018-02-22 22:47 cache -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2018-02-22 22:47 dkb -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2018-02-22 22:47 kb -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2018-02-22 22:47 lk -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2018-02-22 22:47 metadata -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2018-02-22 22:47 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2018-02-22 22:47 recovery -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2018-02-22 22:47 reserved -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2018-02-22 22:47 system -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2018-02-22 22:47 tee1 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2018-02-22 22:47 tee2 -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2018-02-22 22:47 userdata -> /dev/block/mmcblk0p15
Click to expand...
Click to collapse
Also, did you try /dev/block/bootdevice/by-name ? Thank you

Supersonic27543 said:
Also, did you try /dev/block/bootdevice/by-name ? Thank you
Click to expand...
Click to collapse
No /dev/block/bootdevice/ I'm afraid, just /dev/block/platform/ and /dev/block/vold (which is an empty folder).

@Supersonic27543 and others
Have you seen this : https://forum.xda-developers.com/showpost.php?p=74987132&postcount=3

The bootloader files you're looking for are in the update .bin (it's really a .zip; look in the "images" folder). The links to the update file are in the thread cited above (in post #2).
As discussed earlier in this thread, the preloader is locked down (read/write commands missing). Absent access to Amz's signature(s) for the DA, what are you looking to do with these files?

retyre said:
The bootloader files you're looking for are in the update .bin (it's really a .zip; look in the "images" folder). The links to the update file are in the thread cited above (in post #2).
As discussed earlier in this thread, the preloader is locked down (read/write commands missing). Absent access to Amz's signature(s) for the DA, what are you looking to do with these files?
Click to expand...
Click to collapse
I'm trying to see if any backdoor has been left by Amazon by looking at unusual differences.

Trying to Port MIUI To MI A1-Discussion,Help :)

Guys as i said i will try to port MIUI to MI A1 but we have some problems that i don't know how to solve it so i need help from other people/devs./testers..
We have same Hardware like 5x only problem it's Partitions that we have some other partitions that 5X doesn't have like (system_a,system_b,boot_a,boot_b,modem_a,modem_b,and others..)
You can see the Difference Below
5X partitions
Code:
modem -> /dev/block/mmcblk0p1
fsc -> /dev/block/mmcblk0p2
ssd -> /dev/block/mmcblk0p3
sbl1 -> /dev/block/mmcblk0p4
sbl1bak -> /dev/block/mmcblk0p5
rpm -> /dev/block/mmcblk0p6
rpmbak -> /dev/block/mmcblk0p7
tz -> /dev/block/mmcblk0p8
tzbak -> /dev/block/mmcblk0p9
devcfg -> /dev/block/mmcblk0p10
devcfgbak -> /dev/block/mmcblk0p11
dsp -> /dev/block/mmcblk0p12
modemst1 -> /dev/block/mmcblk0p13
modemst2 -> /dev/block/mmcblk0p14
DDR -> /dev/block/mmcblk0p15
fsg -> /dev/block/mmcblk0p16
sec -> /dev/block/mmcblk0p17
splash -> /dev/block/mmcblk0p18
aboot -> /dev/block/mmcblk0p19
abootbak -> /dev/block/mmcblk0p20
boot -> /dev/block/mmcblk0p21
recovery -> /dev/block/mmcblk0p22
devinfo -> /dev/block/mmcblk0p23
system -> /dev/block/mmcblk0p24
cache -> /dev/block/mmcblk0p25
persist -> /dev/block/mmcblk0p26
misc -> /dev/block/mmcblk0p27
keystore -> /dev/block/mmcblk0p28
config -> /dev/block/mmcblk0p29
oem -> /dev/block/mmcblk0p30
limits -> /dev/block/mmcblk0p31
mota -> /dev/block/mmcblk0p32
dip -> /dev/block/mmcblk0p33
mdtp -> /dev/block/mmcblk0p34
syscfg -> /dev/block/mmcblk0p35
mcfg -> /dev/block/mmcblk0p36
lksecapp -> /dev/block/mmcblk0p37
lksecappbak -> /dev/block/mmcblk0p38
cmnlib -> /dev/block/mmcblk0p39
cmnlibbak -> /dev/block/mmcblk0p40
cmnlib64 -> /dev/block/mmcblk0p41
cmnlib64bak -> /dev/block/mmcblk0p42
keymaster -> /dev/block/mmcblk0p43
keymasterbak -> /dev/block/mmcblk0p44
apdp -> /dev/block/mmcblk0p45
msadp -> /dev/block/mmcblk0p46
dpo -> /dev/block/mmcblk0p47
logdump -> /dev/block/mmcblk0p48
cust -> /dev/block/mmcblk0p49
userdata -> /dev/block/mmcblk0p50
MI A1 Partitions
Code:
modem_a -> /dev/block/mmcblk0p1
modem_a -> /dev/block/mmcblk0p2
fsc -> /dev/block/mmcblk0p3
ssd -> /dev/block/mmcblk0p4
sbl1 -> /dev/block/mmcblk0p5
sbl1bak -> /dev/block/mmcblk0p6
rpm -> /dev/block/mmcblk0p7
rpmbak -> /dev/block/mmcblk0p8
tz -> /dev/block/mmcblk0p9
tzbak -> /dev/block/mmcblk0p10
devcfg -> /dev/block/mmcblk0p11
devcfgbak -> /dev/block/mmcblk0p12
dsp -> /dev/block/mmcblk0p13
modemst1 -> /dev/block/mmcblk0p14
modemst2 -> /dev/block/mmcblk0p15
DDR -> /dev/block/mmcblk0p16
fsg -> /dev/block/mmcblk0p17
sec -> /dev/block/mmcblk0p18
splash -> /dev/block/mmcblk0p19
aboot -> /dev/block/mmcblk0p20
abootbak -> /dev/block/mmcblk0p21
boot_a -> /dev/block/mmcblk0p22
boot_b -> /dev/block/mmcblk0p23
devinfo -> /dev/block/mmcblk0p24
system_a -> /dev/block/mmcblk0p25
system_b -> /dev/block/mmcblk0p26
persist -> /dev/block/mmcblk0p27
misc -> /dev/block/mmcblk0p28
keystore -> /dev/block/mmcblk0p29
config -> /dev/block/mmcblk0p30
limits -> /dev/block/mmcblk0p31
mota -> /dev/block/mmcblk0p32
dip -> /dev/block/mmcblk0p33
mdtp -> /dev/block/mmcblk0p34
syscfg -> /dev/block/mmcblk0p35
mcfg -> /dev/block/mmcblk0p36
lksecapp -> /dev/block/mmcblk0p37
lksecappbak -> /dev/block/mmcblk0p38
cmnlib -> /dev/block/mmcblk0p39
cmnlibbak -> /dev/block/mmcblk0p40
cmnlib64 -> /dev/block/mmcblk0p41
cmnlib64bak -> /dev/block/mmcblk0p42
keymaster -> /dev/block/mmcblk0p43
keymasterbak -> /dev/block/mmcblk0p44
apdp -> /dev/block/mmcblk0p45
msadp -> /dev/block/mmcblk0p46
dpo -> /dev/block/mmcblk0p47
logdump -> /dev/block/mmcblk0p48
userdata -> /dev/block/mmcblk0p49
My First Idea:
We can push parted to our device and from recovery we can remove the partitions and create every partition from 0 like 5X then we will need someone from 5x to backup their partitions and flash it to our device (first backup yours ) but there's high risk for Bricking our device but 85% after that MIUI will work
My Second Idea:
To Download MI 5X firmware and flash using MI Flash but as i see in the folder images there's file partition that shows all partitions (in that file there all partitions on list but some of the partitions are missing fsc,ssd and other so i think if we add them maybe we can boot it but i'm not sure) also i don't know does MI Flash is Repartitioning Our Device or just Overwrite the Partitions also there's gpt_backup0.bin file that backup gpt partitions so maybe we will have issues with that also we will need to modify some other files..but this is highly in danger we can brick our device totally
My Third Idea:
To someone create tool or find tool that can automatically repartition our Emmc with 5X partitions in Download Mode or Fastboot but i'm not sure about that
Also i will need some Testers
That's it
You can Join to our Telegram Group for Next Discussions and Testers:
https://t.me/joinchat/FcfGpRGIPfQi5m4STTy0mw

Umm better u can define the partitions in updaterscript itself
Sent from my Mi A1 using Tapatalk

Uhm I'm not really familiar with development per se. But can't you just install it on our partitions and symlink it accordingly? It'll probably slow everything down a bit but I prefer to not play around with partition tables other than for treble because that is the easiest way to get your phone hardbricked.

Or you can try to create repartition script just like lanchon created for galaxys 2 i9100.
https://github.com/Lanchon/REPIT
Just an idea

Comming New Alpha Test i'm uploading now i will post also i'm 75% sure that will boot just flash at twrp but first wipe everything Flash at your OWN RISK!!!!

Do you tested , do you have the phone ?
Enviado do meu Mi A1 através do Tapatalk

Alek Dev said:
Comming New Alpha Test i'm uploading now i will post also i'm 75% sure that will boot just flash at twrp but first wipe everything Flash at your OWN RISK!!!!
Click to expand...
Click to collapse
Please stop porting features to a phone you do not have! It is very likely that you simply brick other people devices!

__BJ__ said:
Please stop porting features to a phone you do not have! It is very likely that you simply brick other people devices!
Click to expand...
Click to collapse
???
Join telegram group, its serious and as I know he have Mi A1.
Wysłane z mojego Mi A1 przy użyciu Tapatalka

__BJ__ said:
Please stop porting features to a phone you do not have! It is very likely that you simply brick other people devices!
Click to expand...
Click to collapse
You don't see my work for Mi A1?? i have the device
Sent from my Mi A1 using Tapatalk

euricoalex said:
Do you tested , do you have the phone ?
Enviado do meu Mi A1 através do Tapatalk
Click to expand...
Click to collapse
If it's possible to make a great kernel without device then he doesn't have mi a1...???

I contacted Guy who already ported MiUI for our A1 but he have issues with setup wizard he will upload Tomorrow on XDA atleast it boots[emoji41]
Sent from my Mi A1 using Tapatalk

Alek Dev said:
You don't see my work for Mi A1?? i have the device
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
Ok then sorry, but It reads as your are not sure what you are doing...

__BJ__ said:
Ok then sorry, but It reads as your are not sure what you are doing...
Click to expand...
Click to collapse
He made the Extreme Kernel for Mi A1. He knows what he's doing.

I'm really excited about having So much variety on this device, like MIUI android one, Lineage, pixel experience.. it's such so good and i learn a lot, thanks to all the devs and people that make ROMs possible.

You can have partition table with usual fdisk tool, or via EDL mode in MiFlash (the associated XML will write partition table).
Just be sure you backup all partitions with EMMCDL first, and are willing to disassemble device for testpoints method if or when you brick it
I've been meaning to port MIUI too btw, but my #1 priority is Project Treble support, and I will be making it a Treble-enabled MIUI GSI instead. I'm kind of waiting for stock 8.1 to launch officially before I go full throttle with it, and/or the Mi 6x to launch (it's the only Treble-enabled MIUI device that has similar hardware to ours, as far as I know).

Which Partition is the recovery?

I've ls the symlinks, but i'm not able to say which one is the recovery partition.
Can anyone explain the list for me?
abl_a -> /dev/block/mmcblk0p33
abl_b -> /dev/block/mmcblk0p34
apdp -> /dev/block/mmcblk0p36
bluetooth_a -> /dev/block/mmcblk0p45
bluetooth_b -> /dev/block/mmcblk0p46
The bootimages to patch with Magisk:
boot_a -> /dev/block/mmcblk0p13
boot_b -> /dev/block/mmcblk0p14
cmnlib64_a -> /dev/block/mmcblk0p22
cmnlib64_b -> /dev/block/mmcblk0p24
cmnlib_a -> /dev/block/mmcblk0p21
cmnlib_b -> /dev/block/mmcblk0p23
ddr -> /dev/block/mmcblk0p43
devcfg_a -> /dev/block/mmcblk0p58
devcfg_b -> /dev/block/mmcblk0p59
devinfo -> /dev/block/mmcblk0p62
dip -> /dev/block/mmcblk0p35
dpo -> /dev/block/mmcblk0p38
dsp_a -> /dev/block/mmcblk0p31
dsp_b -> /dev/block/mmcblk0p32
dtbo_a -> /dev/block/mmcblk0p54
dtbo_b -> /dev/block/mmcblk0p55
elableinfo -> /dev/block/mmcblk0p53
frp -> /dev/block/mmcblk0p60
fsc -> /dev/block/mmcblk0p47
fsg -> /dev/block/mmcblk0p11
hyp_a -> /dev/block/mmcblk0p7
hyp_b -> /dev/block/mmcblk0p8
keymaster_a -> /dev/block/mmcblk0p19
keymaster_b -> /dev/block/mmcblk0p20
keystore -> /dev/block/mmcblk0p57
limits -> /dev/block/mmcblk0p40
logdump -> /dev/block/mmcblk0p61
logfs -> /dev/block/mmcblk0p42
mdtp_a -> /dev/block/mmcblk0p27
mdtp_b -> /dev/block/mmcblk0p28
mdtpsecapp_a -> /dev/block/mmcblk0p25
mdtpsecapp_b -> /dev/block/mmcblk0p26
misc -> /dev/block/mmcblk0p56
modem_a -> /dev/block/mmcblk0p29
modem_b -> /dev/block/mmcblk0p30
modemst1 -> /dev/block/mmcblk0p49
modemst2 -> /dev/block/mmcblk0p50
msadp -> /dev/block/mmcblk0p37
oemowninfo -> /dev/block/mmcblk0p12
persist -> /dev/block/mmcblk0p51
pmic_a -> /dev/block/mmcblk0p9
pmic_b -> /dev/block/mmcblk0p10
pwinfo -> /dev/block/mmcblk0p52
rawdump -> /dev/block/mmcblk0p65
rpm_a -> /dev/block/mmcblk0p5
rpm_b -> /dev/block/mmcblk0p6
sec -> /dev/block/mmcblk0p44
splash -> /dev/block/mmcblk0p39
ssd -> /dev/block/mmcblk0p48
sti -> /dev/block/mmcblk0p63
storsec -> /dev/block/mmcblk0p64
system_a -> /dev/block/mmcblk0p15
system_b -> /dev/block/mmcblk0p16
toolsfv -> /dev/block/mmcblk0p41
tz_a -> /dev/block/mmcblk0p3
tz_b -> /dev/block/mmcblk0p4
userdata -> /dev/block/mmcblk0p68
vbmeta_a -> /dev/block/mmcblk0p66
vbmeta_b -> /dev/block/mmcblk0p67
vendor_a -> /dev/block/mmcblk0p17
vendor_b -> /dev/block/mmcblk0p18
xbl_a -> /dev/block/mmcblk0p1
xbl_b -> /dev/block/mmcblk0p2