Database Develop

[Bootloader] LK for Xperia T

LK for Xperia T
LT30p Only - Unlocked Bootloader Required
WARNING 1: This modification makes changes
to the devices partition table. I (lilstevie) am not
responsible for any damage to your device or
data loss that may occur.
WARNING 2: ICS kernels currently do not boot
with this modification at this point in time. This
can only be used with JB kernels including those
from the alpha and leaked releases. At the time
of writing the TWRP 2.4.1.1 FOTA image has
everything required to boot without any changes.
Since getting the Xperia T the biggest annoyance is only having one bootable partition.
To combat this issue I have spent some time porting the Little Kernel bootloader. This
allows booting different kernels for recovery and boot as well as a full implementation
fastboot.
Features:
Separate boot and recovery partition.
Full fastboot implementation including fastboot boot (with correctly formatted boot.img)
Ability to load both Android boot image and sony elf formats.
Boot to recovery, and boot to recovery from userspace (requires patched kernel).
Known Issues:
No display until kernel has booted – This is also the case with S1Boot.
Cannot reboot into another boot mode without kernel patch.
No LEDs to indicate status.
ICS 3.0 kernels will not boot.
Usage:
After 1 second from pressing the power button LK will listen for input on the volume keys for 2-5 seconds:
Volume Up -> boot recovery.
Volume Down -> boot fastboot.
Credits:
Rebellos -- Inital work on getting eMMC and buttons working.
Dees_Troy -- extract_elf_ramdisk served as a base for elf parsing.
cdesai -- Bug fixes and hosting bootloader on his github.
Various others for support, if you think your name should be here
and that I have forgotten all about you let me know.
How to install LK:
Download LittleKernel-1.0-FINAL.zip
Copy LittleKernel-1.0-FINAL.zip to device
Boot into recovery
Install LittleKernel-1.0-FINAL.zip
How to install LK ready kernel:
Download JB_Kernel_LK.zip
Copy JB_Kernel_LK.zip to device
Boot into recovery
Install JB_Kernel_LK.zip

Versions:
Version 1.0:
Initial Release.
MD5Sums:
LittleKernel-1.0-FINAL.zip - fd550025493533db904ecb5bc299ac9b
JB_Kernel_LK.zip - cc185b728e28865fe6323f4cc96e17a0
Building a boot image for lk should be done with the
following boot image settings:
Base Address: 0x80200000
Ramdisk Address: 0x81400000
Page Size: 2048
Cmdline: “user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2 kgsl.mmutype=gpummu”
Copyleft:
LK here.
Kernel here.

reserved for future use

reserved for future use

Sweet. I saw the patch on gerrir and was wondering how it worked. Will have a try.
The only thing I'm wondering is whether there is a way to reverse the changes to the partition table.
Sent from my Xperia T using Tapatalk 2

Very interesting... Awesome work guys...
And good to see cdesai around
I am still unclear on few things though..
Ok so from what I understand you are still depending on s1boot as primary bootloader. Then once the primary bootloader passes boot sequence to main kernel (mmcblk0p4) you have little kernel which will intercept it and then function as a bootloader? Which can then accept these commands or in turn boot a secondary kernel (fotakernel) or mmcblk0p16 which will now act as boot partition for the OS?
My concern is how are you making space for that mmcblk0p16? Are you repartitioning internal sdcard?
Sent from my LT30p using xda app-developers app
tilal6991 said:
Sweet. I saw the patch on gerrir and was wondering how it worked. Will have a try.
The only thing I'm wondering is whether there is a way to reverse the to the partition table.
Sent from my Xperia T using Tapatalk 2
Click to expand...
Click to collapse
I think flashing a standard full stock firmware should restore partition table
Sent from my LT30p using xda app-developers app

There is 300mb free space at the end of the emmc, and this makes a new 30mb partition after the sdcard.
Like you said DooMLoRD, s1boot is still used, and it loads lk which in turn loads p16 as kernel, and p11(FOTA) as recovery.
There's still enough space left to add more kernels, and some sort of a boot menu to multi boot

DooMLoRD said:
Ok so from what I understand you are still depending on s1boot as primary bootloader. Then once the primary bootloader passes boot sequence to main kernel (mmcblk0p4) you have little kernel which will intercept it and then function as a bootloader? Which can then accept these commands or in turn boot a secondary kernel (fotakernel) or mmcblk0p16 which will now act as boot partition for the OS?
Click to expand...
Click to collapse
We can't actually replace S1Boot due to code signatures, and S1Boot is actually multiple bootloader stages in 1. Other devices would have pbl sbl and appsboot.mbn, Sony have combined them all into 1, LK is only a replacement for appsboot, thankfully between each stage everything that was turned on gets turned on for the purpose of appsboot (such as mmu) get turned off again before the next stage which allows us to do this without major hacks. Essentially what we are doing is adding an extra boot stage.
mmcblk0p16 which has been added to the end indeed does act as the new boot partition. I did originally plan to add another extra partition for boot, but after talking to Dees_Troy we worked out a situation where we could utilise FOTAKernel for recovery and not impact installation of TWRP from goomanager.
DooMLoRD said:
My concern is how are you making space for that mmcblk0p16? Are you repartitioning internal sdcard?
Click to expand...
Click to collapse
I do understand this concern, however I did notice that all Xperia T's that I have encountered so far (I checked with ~10 peoples devices) and they all have 300±25MB of unused, and unpartitioned space at the end of their eMMCs, I do not delete or resize any partitions. This is the script I run when installing lk if you are interested in seeing how it is done.
DooMLoRD said:
I think flashing a standard full stock firmware should restore partition table
Click to expand...
Click to collapse
Utimately this is what eased my feelings towards modifying the partition table, I understand people get a little bit funny about things that cannot be easily reverted, and in this case flashing a stock ftf or using EMMA to reflash back to stock will undo the changes to the partition table.

Please contact me if you have any of the following devices with a bootloader unlock: Xperia TX, TL (Are any of these unlocked?) and V. I would like to add support for these devices but as I do not have any of them I will need some testers.
EDIT: Xperia V is off the table for the moment as there isn't enough free space to remap the kernel partition.

Have a tx unlocked
Sent from my LT29i using xda app-developers app

travis82 said:
Have a tx unlocked
Sent from my LT29i using xda app-developers app
Click to expand...
Click to collapse
from recovery can you please run "parted /dev/block/mmcblk0 unit MB print free" and paste the output for me.

parted /dev/block/mmcblk0 unit MB print free
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 15634MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
0.02MB 0.13MB 0.11MB Free Space
1 0.13MB 2.23MB 2.10MB TA
2 2.23MB 3.80MB 1.57MB Boot
3 3.80MB 5.37MB 1.57MB Boot2
5.37MB 6.29MB 0.92MB Free Space
4 6.29MB 27.3MB 21.0MB Kernel
5 27.3MB 28.3MB 1.05MB TZ
28.3MB 29.4MB 1.05MB Free Space
6 29.4MB 32.5MB 3.15MB modemst1
32.5MB 33.6MB 1.05MB Free Space
7 33.6MB 36.7MB 3.15MB modemst2
36.7MB 37.7MB 1.05MB Free Space
8 37.7MB 40.9MB 3.15MB fsg
9 40.9MB 46.1MB 5.24MB ramdump
10 46.1MB 54.5MB 8.39MB ext4 apps_log
11 54.5MB 71.3MB 16.8MB FOTAKernel
12 71.3MB 1359MB 1288MB ext4 System
13 1359MB 1621MB 262MB ext4 Cache
14 1621MB 3769MB 2147MB ext4 Userdata
15 3769MB 15634MB 11866MB ext4 SDCard
Makes me wanna do what I did with the Note and redo the partition format and add a bit more space to the sdcard partition. So lets say we use CM rom. Couldn't we just remove the fota partition a boot partition, ram dump, apps log, etc.. and add the extra to the sd or data partition.
So the main question is I guess what partitions does the phone need to run aosp so we can use the extra space somewhere more useful?

travis82 said:
parted /dev/block/mmcblk0 unit MB print free
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 15634MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
0.02MB 0.13MB 0.11MB Free Space
1 0.13MB 2.23MB 2.10MB TA
2 2.23MB 3.80MB 1.57MB Boot
3 3.80MB 5.37MB 1.57MB Boot2
5.37MB 6.29MB 0.92MB Free Space
4 6.29MB 27.3MB 21.0MB Kernel
5 27.3MB 28.3MB 1.05MB TZ
28.3MB 29.4MB 1.05MB Free Space
6 29.4MB 32.5MB 3.15MB modemst1
32.5MB 33.6MB 1.05MB Free Space
7 33.6MB 36.7MB 3.15MB modemst2
36.7MB 37.7MB 1.05MB Free Space
8 37.7MB 40.9MB 3.15MB fsg
9 40.9MB 46.1MB 5.24MB ramdump
10 46.1MB 54.5MB 8.39MB ext4 apps_log
11 54.5MB 71.3MB 16.8MB FOTAKernel
12 71.3MB 1359MB 1288MB ext4 System
13 1359MB 1621MB 262MB ext4 Cache
14 1621MB 3769MB 2147MB ext4 Userdata
15 3769MB 15634MB 11866MB ext4 SDCard
Makes me wanna do what I did with the Note and redo the partition format and add a bit more space to the sdcard partition. So lets say we use CM rom. Couldn't we just remove the fota partition a boot partition, ram dump, apps log, etc.. and add the extra to the sd or data partition.
So the main question is I guess what partitions does the phone need to run aosp so we can use the extra space somewhere more useful?
Click to expand...
Click to collapse
Modifying the existing partition table isn't a good idea, and even if you plan on doing that, it would be safer if you don't touch anything below system.
FOTAKernel partition is currently used to store recovery (though the kernel partition has a recovery as well).
Boot[2] contains the bootloader(s), so you can't remove them - you'll end up with a brick.
ramdump isn't used on production devices from what i know, so it could be used to store something else (since TX and V do not have any free space at the end of the partition table, while T does)
So what could be done is flash lk to Kernel, kernel to FOTAKernel, and a trimmed down recovery to ramdump, which is doable without modifying the existing partition table.

AW: [Bootloader] LK for Xperia T
Thank you very much. 2 questions:
1: does your patched kernel include TWRP 2.4.1.1 or 2.4.1.0 and we have to do it through goomanager?
2: when I backup stock jb, wipe and flash cm i don't lose TWRP? because cm10 has cwm in the boot.img and with this method it won't override my current recovery?
thanks
Gesendet von meinem LT30p mit Tapatalk 2

cdesai said:
Modifying the existing partition table isn't a good idea, and even if you plan on doing that, it would be safer if you don't touch anything below system.
FOTAKernel partition is currently used to store recovery (though the kernel partition has a recovery as well).
Boot[2] contains the bootloader(s), so you can't remove them - you'll end up with a brick.
ramdump isn't used on production devices from what i know, so it could be used to store something else (since TX and V do not have any free space at the end of the partition table, while T does)
So what could be done is flash lk to Kernel, kernel to FOTAKernel, and a trimmed down recovery to ramdump, which is doable without modifying the existing partition table.
Click to expand...
Click to collapse
Sounds great. I like having separate kernel and recovery partitions. I hate that kernel and recovery is in one image.

cmajetic said:
Thank you very much. 2 questions:
1: does your patched kernel include TWRP 2.4.1.1 or 2.4.1.0 and we have to do it through goomanager?
2: when I backup stock jb, wipe and flash cm i don't lose TWRP? because cm10 has cwm in the boot.img and with this method it won't override my current recovery?
thanks
Gesendet von meinem LT30p mit Tapatalk 2
Click to expand...
Click to collapse
At present my boot.img that I supplied has TWRP 2.4.1.0 in it due to packaging in the wrong ramdisk, my kernel should have no recovery in it at all as this allows recovery to live on its own partition, TWRP 2.4.1.1 that installs on to FOTA when you run goomanager is set up for this method of booting.
As for CM, I've been working with cdesai to get this merged into cm10.1, if successful CM will no longer be built like that but rather be a rom that uses lk as the bootloader with seperate kernel and recovery

AW: [Bootloader] LK for Xperia T
lilstevie said:
At present my boot.img that I supplied has TWRP 2.4.1.0 in it due to packaging in the wrong ramdisk, my kernel should have no recovery in it at all as this allows recovery to live on its own partition, TWRP 2.4.1.1 that installs on to FOTA when you run goomanager is set up for this method of booting.
As for CM, I've been working with cdesai to get this merged into cm10.1, if successful CM will no longer be built like that but rather be a rom that uses lk as the bootloader with seperate kernel and recovery
Click to expand...
Click to collapse
okay but I have a problem. goomanager does download successful and says installation successful but when I enter recovery it is still 2.4.1.0, tried several times now...
Gesendet von meinem LT30p mit Tapatalk 2

cmajetic said:
okay but I have a problem. goomanager does download successful and says installation successful but when I enter recovery it is still 2.4.1.0, tried several times now...
Gesendet von meinem LT30p mit Tapatalk 2
Click to expand...
Click to collapse
I had this problem the other day, you need to be root for it to work, what I did was downloaded 2.4.1.1 linked here under the heading "Download - FOTAKernel Image" then flash it with lk fastboot using the command "fastboot flash recovery openrecovery-twrp-2.4.1.1-mint.img"

AW: [Bootloader] LK for Xperia T
lilstevie said:
I had this problem the other day, you need to be root for it to work, what I did was downloaded 2.4.1.1 linked here under the heading "Download - FOTAKernel Image" then flash it with lk fastboot using the command "fastboot flash recovery openrecovery-twrp-2.4.1.1-mint.img"
Click to expand...
Click to collapse
i am rooted but okay I will try it the way you mentioned, thanks
Gesendet von meinem LT30p mit Tapatalk 2

[LOST IMEI] Warning for D410HN users (Brazilian Dual-SIM with NFC variant)

This warning also serves to other variants.
I see that many users of this variant are using other variant binaries and images trying to unlock the bootloader and install TWRP recovery.
My advise is to not do this or you can end with a brick.
Even worse, when trying to unbrick the phone, people are using other variant nand backup images, this will lead you to the infamous lost IMEI problem, and from this point if you don't have your modemst partitions backups, you are lost.
Flashing KDZ won't recover these partitions, they are unique to your phone and are not flashed in a normal KDZ flash, the only way to flash them is in TWRP or ADB.
I already supplied the proper D410HN Kitkat v10c and Lollipop v20a/b/c (they are the same) unlocked aboots and bootstacks but people insist flashing files from other variants.
My advise is, after rooting your phone, before doing anything else, the first thing you must do is to backup your modemst1 and modemst2 partitions to make sure you IMEI data is safe. You can make this backup in ADB or Android Terminal app with:
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/storage/external_SD/modemst1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/storage/external_SD/modemst2.img
This will save modemst1.img and modemst2.img in your external microSD. If you want to save in your internal SD, replace /storage/external_SD to /sdcard.
Also, make a nand backup image in case of you need to make a testpoint or direct flash in nand to attempt to unbrick the phone.
Code:
dd if=/dev/block/mmcblk0 of=/storage/external_SD/unbrick.img bs=512 count=323583
This will save an unbrick.img in your external microSD. If you want to save in your internal SD, replace /storage/external_SD to /sdcard. Do not share this file with anyone else, this image have your IMEI data.
Why make your own unbrick.img file?
If you look at the partition table, you will have this:
Code:
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) unit s
unit s
(parted) print
print
Model: MMC 8WMB3R (sd/mmc)
Disk /dev/block/mmcblk0: 15269888s
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 16384s 147455s 131072s fat16 modem
2 147456s 149503s 2048s sbl1
3 149504s 150527s 1024s rpm
4 150528s 151551s 1024s tz
5 151552s 152575s 1024s sdi
6 152576s 156671s 4096s aboot
7 156672s 157695s 1024s rpmb
8 157696s 158719s 1024s tzb
9 158720s 162815s 4096s abootb
10 162816s 166911s 4096s pad
11 166912s 173055s 6144s modemst1
12 173056s 179199s 6144s modemst2
13 179200s 211967s 32768s misc
14 212992s 278527s 65536s ext4 persist
15 278528s 323583s 45056s laf
16 327680s 372735s 45056s boot
17 372736s 417791s 45056s recovery
18 417792s 423935s 6144s fsg
19 425984s 427007s 1024s fsc
20 427008s 428031s 1024s ssd
21 442368s 443391s 1024s DDR
22 458752s 459775s 1024s encrypt
23 459776s 460799s 1024s rct
24 475136s 491519s 16384s ext4 drm
25 491520s 507903s 16384s ext4 sns
26 507904s 548863s 40960s factory
27 548864s 614399s 65536s fota
28 622592s 624639s 2048s sbl1b
29 624640s 690175s 65536s ext4 mpt
30 704512s 909311s 204800s ext4 cust
31 917504s 918527s 1024s eksst
32 933888s 5128191s 4194304s ext4 system
33 5128192s 6971391s 1843200s ext4 cache
34 6971392s 15223807s 8252416s ext4 userdata
35 15237120s 15269854s 32735s grow
(parted)
This ubrick image have your partition table and the partitions until sector 323583 (partition 15 - laf), which is enough to enter in download mode and flash KDZ with LG Flash Tool and make a complete and perfect recover. This also explains why when you flash an unbrick image from a unknown source and variant you lose your IMEI, modemst1 (11) and modemst2 (12) partitions are flashed along, overwriting your unique data.
Keep your backups in a safe place and now you can go ahead and unlock the bootloader, install TWRP, change partitions size and etc knowing that if anything goes wrong, if you manage to unbrick your phone, you won't loose your IMEI.
Good luck :good:
Files:
Unlocked bootloaders (aboot):
D410HN KitKat v10c: http://www.mediafire.com/download/lg0ewb6vnl184mq/aboot_d410hn_v10c_unlocked_.zip
D410HN Lollipop v20abc: http://www.mediafire.com/download/dzp38dk9jivw31j/aboot_d410hn_v20abc_unlocked.zip
TWRP Custom Recovery: http://forum.xda-developers.com/lg-l90/development/recovery-twrp2-7-1-0lgl90w7xxshoxx-t2826150
Bootstacks:
D410HN KitKat v10c: http://www.mediafire.com/download/qx3cv5fzdzjsod2/Bootstack_D410hn_KitKat_v10c.zip
D410HN Lollipop v20c: http://www.mediafire.com/download/wxa5m1ch80hth54/Bootstack_D410hn_Lollipop_v20c.zip
Stock Flashable ZIP (for stock partition tables only):
D410HN KitKat v10c: http://www.mediafire.com/download/8u4zsj8tnyz4r6n/Flashable_D410hn_Stock_KitKat_v10c.zip
D410HN Lollipop v20c: http://www.mediafire.com/download/oqp0ubsq2jmzjph/Flashable_D410hn_Stock_Lollipop_v20c.zip

Thanks for posting these files for D410hn and warning owners of this LG L90 variant.
Recently, I decided to switch from stock to cyanogenmod and I got to find out your files in the middle of other posts.
Now this post made things crystal clear.

Thanks !
Gacrux, i must first of all thank you for your effort on gather all that info e put it on one post, this for us newbies was a great hand. But, for those like me that already have did things wrong, and already are on a mud puddle, and not expert like you guys here on XDA learning and teaching all concernments about root, flash, custom rom, stock, our beloved android, i must ask you some more of your patience, and write some more detailed tutorial, link us to posts that can help recover lost IMEI because used that russian files and process that you quote on another post. I managed after long time research to find a process that a could insert one of my IMEI to the slot one, but slot 2 stills IMEI "0", checked with *#06#. Interesting is that here on my home, phone are getting signal on both sims, i have tested and both can do and receive calls, data flow, etc, but when i got to drive to another near city, like go to my job, i loose signal on both. So, i dont have (i didnt know that i have to) that backups modemst1 and modemst2 partitions, what can i do ? I still can remove my battery and put on a paper that 2 IMEi numbers that i need, in case to do some process. I'm using D410HN lollipop 5.0.2, base band M8626A-AAAANAZM-1.0.6063 kernel 3.4.0+ ,next info LRX22G.A1440649755 and V20c-OP1-HQ What would be the steps i need to follow to at least try to put IMEI on place, unlock, install a more light rom, that consumes least internal storage space, but all functions like cameras, nfc, bluetooth, etc are working. I'm sure 100% that you will be helping a lot of people. Thanks another time, and awatin directions !

I'll try to look into this IMEI issue soon and try to find out if there is a chance to rebuild both modemst partitions with both SIM cards on D410hn, but from what I could find until now, I wouldn't get hopes up... In the past, when IMEI were stored in EFS partitions, they were stored in plain text and could be hex edited, but they don't do this anymore, I downloaded modemst partitions from two L90 and compared them and found out that this data is now fully encrypted.
You loose signal probably because you are using other variant modem and modemst data.
Regarding the storage issue, I have a self made slim version of stock v20c and modified the partition tool in this topic (http://forum.xda-developers.com/lg-...ck-partition-table-tool-lg-l90really-t2946323) to fit to my needs, and more importantly, to change the units he used to respect the partitions beginnings and ends (partition by sectors I find to be more precise and safe), I removed everything that I judged useless from the stock LG rom and remade the partition table to shrink system partition to give more room for userdata.
I removed this stuff from the original ROM:
/system/usbautorun.iso
/system/app/Books
/system/app/ChromeWithBrowser
/system/app/Drive
/system/app/Gmail2
/system/app/GoogleTTS
/system/app/Hangouts
/system/app/LGPCSuiteUI
/system/app/LGSearchWidgetProvider
/system/app/LGWeather
/system/app/LGWeatherService
/system/app/LGWeatherTheme
/system/app/Maps
/system/app/Music2
/system/app/Newsstand
/system/app/PlayGames
/system/app/PlusOne
/system/app/Street
/system/app/talkback
/system/app/Videos
/system/app/YouTube
/system/apps/bootup/LGBoxnet
/system/apps/bootup/LGFlashlightWidget
/system/apps/bootup/LGSmartWorld
/system/apps/bootup/LGTaskManager
/system/priv-app/LGApplicationManager
/system/priv-app/LGBackup
/system/priv-app/LGBrowser
/system/priv-app/LGDictionary
/system/priv-app/LGDMSClient
/system/priv-app/LGEasyHome
/system/priv-app/LGEmail
/system/priv-app/LGFileManager
/system/priv-app/LGMemo
/system/priv-app/LGPCSuite
/system/priv-app/LGQTranslator
/system/priv-app/LGUpdateCenter
/system/priv-app/Velvet
/system/vendor/carrier/system/LGRemoteCall
/system/vendor/carrier/system/rspermlge
/system/vendor/overlay/com.android.browser
/system/vendor/overlay/com.lge.appbox.client
/system/vendor/overlay/com.lge.bnr
/system/vendor/overlay/com.lge.easyhome
/system/vendor/overlay/com.lge.email
/system/vendor/overlay/com.lge.filemanager
/system/vendor/overlay/com.lge.lgworld
/system/vendor/overlay/com.lge.task
/system/vendor/overlay/com.lge.updatecenter
/system/vendor/overlay/com.lge.sizechangable.weather
/system/vendor/overlay/com.lge.sizechangable.weather.theme.optimus
My post on the repartition tool thread about my personal changes: http://forum.xda-developers.com/showpost.php?p=63218497&postcount=151

So, about that modem partitions, i read somewhere, that some "box" called octopus/octoplus can repair that **** i did on my phone e by that restore that 2 IMEI to his place, i looked into some tecnicians here im my city, but anyone have that, nor knows nothing that can repair, help me, i will try a day off my job next week to search on a bigger city for a technical assistance that have this box to try it out, this is what i could found, about this problem losing imei by overrun that partition where they are writed. I must say that I have encountered too much resistence from the people that knows how to do the process, because they think i stole the phone, even seeing me gather to his front door inside my police uniform. I must thank you Gacrux another time to be willing to help me and other people, even without know me, thank you man ! About your rom, all hardware is functional ? Did you managed to reduce the size of that system data about to 4.21 GB that are untouchable, chequing from configuration=>general=>storage just below cache data, "many" where when i click i can see that "system data" in about 4.21 GB. I already did a full wipe, but i dont have a custom recovery, because i tried to install twrp from "rom installer" from JRummy and it says that no one is compatible with my phone. This is one thing that i wanted to with a custom recovery, install a custom rom that have this system data a little smaller.

My phone is fully functional, mainly because from the start I never flashed other variant files in my phone and after rooting I knew it was a wise move to backup my modemst partitions before doing anything else after root the phone.
When I decided to mod my L90 I saw that nobody had unlocked the D410hn variant or made proper bootstack for us, with a little search I realized how to unlock our kitkat and lollipop aboots with IDA disassembler and built the proper bootstack from the partitions extracted of our kdz file.
As far as I tested, from bootloader downgrade and softbricks, the modemst and own unbrick images were enough to make a perfect recover of the phone (I had to simulate some scenarios in my own phone to test if my files and my advises would actually work).
Unfortunately, for the ones that didn't know that they MUST do some obligatory backups files, the lack of these backups lead them to problems like the one you are facing.
Custom recovery can be flashed with adb, no need for app, I'll post later when I arrive home.
System partition is actually 2GB. With stock LG ROM, there are around 60MB free. The debloating I did freed around 610MB, this allowed me to reduce system partition to 1.39GB. Also, I reduced cache partition from 900MB to 64MB. The difference was given to userdata partition, allowing me to grow from the stock 3.34GB to 5.38GB.

thank you your attention ! From your knowledge im making my own, thank you for advices too, that i will follow for sure !

To flash custom recovery with adb only (needs root and unlocked bootloader, if you already have, there is no need to repeat):
1. Root.
2. Copy aboot.bin and recovery.img (rename TWRP_2.8.7.0_270615_L90.img) to the root of your external microSD card.
3. Open adb shell or android terminal, take superuser permission with su and allow it in your phone screen.
4. Flash the hacked unlocked bootloader for D410HN Lollipop with dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
5. Flash custom recovery (TWRP) with dd if=/storage/external_SD/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
To boot the custom recovery, from android you can send reboot recovery in adb or terminal (needs su). To boot recovery from the phone off, hold VOL - and PWR, when LG logo appears, release and hold PWR button. A blank screen asking to reset the phone to factory settings will appear, select YES twice and wait custom recovery to boot. Don't worry, your phone won't be reset since stock recovery was replaced with a custom one.

Well, i think i can take that line of commands with ADB, but the problem here is that files, can you please link that needed files that are "for sure" functioning in D410HN lollipop 5.0.2, because i dont want a new brick ! You can link to some post, that you are certain about, and i will go there e download, thanks again !
edit: I dont have unlocked bootloader, because, as i said i was feared that i could download wrong files and did **** again, if you can help in this one too, i will pay a beer !
edit: About root, i tried purpledrake, towelroot, and others, last one, and only that works was kingroot, fully functional, checked with root checker.

I think I found a way to recover the second SIM IMEI.
Requires Qualcomm Product Support Tools (QPST), HxD (or any other decent hex editor), LG Mobile Support Tool and an IMEI to HEX converter.
Though I didn't tested it myself in my own phone, I believe it's going to works, also in any Dual-SIM variant.
I'll first try to find a way to convert the SIM to those HEX values (they are not a straight text to HEX conversion), if OK, I'll write something about this matter and will post soon.
---
It's done, read: http://forum.xda-developers.com/lg-l90/general/imei-fix-2nd-sim-slot-t3229097

Hi there. I also have a D410hn. I was on 20b rooted and using TWRP, then the 20c upgrade came. So I've used your 20c flashable zip to go to 20c.
It worked just fine, then I've used the flashable superuser as you've suggested and it worked just fine too. The problem is that when I go to phone settings -> about this phone -> software info it displays "V20B-SCA-XXXX". I've checked build.prop and it shows 20c, so what's wrong?
If I flash your 20c bootstack it will fix it? Will I lose something like have to root or install custom recovery again?
Thanks
Sent from my LG-D410 using XDA Free mobile app

Flash v20c bootstack. Lollipop bootstack v20c is different from v20ab, as noted here: http://forum.xda-developers.com/showpost.php?p=63292272&postcount=57
The user who edits the topic didn't updated to include the newer bootstack for D410hn.
You are not going to loose anything since it won't flash boot and system partitions.

It worked, settings display 20c now. Thanks
Sent from my LG-D410 using XDA Free mobile app

Hello. I have D405n and when I try to unlock bootloader i bricked phone. Then I was searching for solution and somehow did that with success but in setting phone was D405 (without N). It was few months ago but these days I was testing custom roms and noticed that on rom 5.1.1 i dont have imei and dont have signal, but on stock lollipop I have signal but imei is zero. Any ideas how to fix this?
Would help flashing loader?

Fangio92 said:
Hello. I have D405n and when I try to unlock bootloader i bricked phone. Then I was searching for solution and somehow did that with success but in setting phone was D405 (without N). It was few months ago but these days I was testing custom roms and noticed that on rom 5.1.1 i dont have imei and dont have signal, but on stock lollipop I have signal but imei is zero. Any ideas how to fix this?
Would help flashing loader?
Click to expand...
Click to collapse
Try QPST: http://forum.xda-developers.com/showthread.php?t=2701861
This can also be a 5.1.1 issue or you are in a different bootloader. CM development for L90 is a little messy, don't know if it's using kitkat or lollipop bootloader now.

How to flash stock bootloader? I try flashing 4.4 kdz and 5.0 kdz and its the same.

Fangio92 said:
How to flash stock bootloader? I try flashing 4.4 kdz and 5.0 kdz and its the same.
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479

Done that few times and its the same... QPST not working but with EFS I manage to read data but not to write.

If I get a backup of another L90 and restore it to mine, and then change the IMEI 1 through the QPST, does it works?
ps .: my IMEI 2 is zero

LG-D410HN "deadboot"
Hello, have a LG D410hn with deadboot, someone would have Loader.img file D410hn (Brazil), as did only with the D410 and the front camera has stopped working and zeroed IMEI. If anyone can help I am grateful!

Working Bootable recovery for the KFFOWI (Ford)

As you know, root has been achieved on this device. Now, let's move on to recovery. The recovery.img is a lot like the boot.img, in the way that you can boot from it. In theory, if we make a 3e recovery.bin for this device (TWRP/CWM), and we boot from it, we will be able to install any rom. Let's let the Recovery.bin development start!
THIS DEVICE DOES NOT SUPPORT FLASHING RECOVERIES. YOU HAVE TO BOOT FROM THEM IN FASTBOOT.​
This device now has 2 custom recoveries, those 2 being TWRP (Team Win Recovery Project) and CM (CyanogenMod) Recovery. CyanogenMod recovery is much like the stock recovery, with the only difference being that CM Recovery can install files that don't have the Amazon ZIP Signature. TWRP, on the other hand, has a touchscreen display, and is much more user friendly than CM Recovery. The links to both are here:
CM Recovery
TWRP
You can do many things in a Custom Recovery, such as:
Install custom ROMs (Found here)
Install modifications to your current OS (XPosed Framework, Root, etc.)
Install GAPPS (Google Applications, including Play Store and Play Services)
Wipe your current ROM
Backup your current ROM
Restore a backup of a previous ROM
If you have any questions, ask them here.
Now, press the thank button here and thank the developers that made these recoveries and ROMs possible, and you are good to go.
Good Luck!

Im dumping the recovery partition right now as well as the boot as well and the other two extra bootloader stuff that may help us

I have attached the images we can use. I dont know if we need the system image file but if we do just let me know hopefully ill be able to upload it or someone else might cause its 1 GB it may take some time.

Awesomeslayerg said:
I have attached the images we can use. I dont know if we need the system image file but if we do just let me know hopefully ill be able to upload it or someone else might cause its 1 GB it may take some time.
Click to expand...
Click to collapse
Well, we just need someone to build a recovery for this device. Once that is bootable, we can install roms. Also, since we will most likely not be able to unlock the bootloader, Safestrap might be our best bet.

True.. it's a mediatek soc so there's gotta be a way to unlock the bootloader because most of the mediatek devices have unlocked bootloader I think. And besides it gives us an unlock code so we need to see what that deal is

Just leaving here partitions structure:
Model: MMC 8GND3R (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 2097kB 1049kB KB
2 2097kB 3146kB 1049kB DKB
3 3146kB 21.4MB 18.2MB EXPDB
4 21.4MB 22.4MB 1049kB UBOOT
5 22.4MB 39.2MB 16.8MB boot
6 39.2MB 56.0MB 16.8MB recovery
7 56.0MB 56.5MB 524kB MISC
8 56.5MB 60.2MB 3670kB LOGO
9 60.2MB 65.4MB 5243kB TEE1
10 65.4MB 70.6MB 5243kB TEE2
11 70.6MB 1329MB 1258MB ext4 system
12 1329MB 1591MB 262MB ext4 cache
13 1591MB 7818MB 6227MB ext4 userdata

Hmm it looks like the MTK Droid Root and Tools V2.5.3 works now so we can flash images via that as well as recovery AND boot. But someone should get a 2nd fire and try it out because we have no scatter file.
We could possibly install a 2nd bootloader

Awesomeslayerg said:
Hmm it looks like the MTK Droid Root and Tools V2.5.3 works now so we can flash images via that as well as recovery AND boot. But someone should get a 2nd fire and try it out because we have no scatter file.
We could possibly install a 2nd bootloader
Click to expand...
Click to collapse
I have made this one and test ro readback partitions bug gets error 2004
Partition lists
storage, boot_channel & block_size maybe not good
Model: MMC 8GND3R (sd/mmc)
storage: SDMMC ????
Sometimes tablet wont boot and have to remove battery connector
Last SP Flash TOOL, linux version have much errors and force to remove battery
http://firmware.su/51343-sp-flash-tool.html
DO NO USE TO DOWNLOAD ANYTHING
UNDER CONSTRUCTION
scatter updated, UNTESTED

Lets go recovery!

idme print as su
unlock_code:
---------- Post added at 12:09 PM ---------- Previous post was at 11:52 AM ----------
There are 2 boads type and 2 preloaders......
Mine have preloader_prod.img board_id: 0025001040000015
Code:
# check if production device
if ("0025001000000015" == read_file_str("/proc/idme/board_id") ||
"0025001000010015" == read_file_str("/proc/idme/board_id") ||
"0025001010000015" == read_file_str("/proc/idme/board_id") ||
"0025001010010015" == read_file_str("/proc/idme/board_id") ||
"0025001020000015" == read_file_str("/proc/idme/board_id"))
then
ui_print("Copying preloader.img to boot partition 0 for unsecure device...");
package_extract_file("images/preloader.img", "/dev/block/platform/mtk-msdc.0/mmcblk0boot0");
else
ui_print("Copying preloader_prod.img to boot partition 0 for secure device...");
package_extract_file("images/preloader_prod.img", "/dev/block/platform/mtk-msdc.0/mmcblk0boot0");
endif;

my /proc/idme/board_id reads 0025001040000015

Can anyone try this: http://forum.xda-developers.com/showthread.php?t=2798257?
Sent from my KFFOWI using Tapatalk

I did yesterday didn't work

Awesomeslayerg said:
I did yesterday didn't work
Click to expand...
Click to collapse
Did you try Fastboot boot recovery.img with the one it gave?
Sent from my XT912 using Tapatalk

No I'll try today

Okay i used the MTK-TWRP thing right now and used it to unpack the recovery image and it looks like we can use this to our advantage to flash unverified files by editing some of the prop settings.

Can someone try this: http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device? It might work.

How would we flash it?

Awesomeslayerg said:
How would we flash it?
Click to expand...
Click to collapse
Zips are flashable in flashfire...

Awesomeslayerg said:
How would we flash it?
Click to expand...
Click to collapse
Use the following commands to flash the recovery
Code:
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/platform/mtk-msdc.0/by-name/recovery
- I have Cyanogenmod Recovery working except a few minor niggles
- Let you know once it's fully working
- It looks like we can't boot unsigned images that are flashed to the recovery partition
- If I boot the image from fastboot rather than flashing it then it works
- CVE-2014-0973 is patched in the bootloader

[kexec] droid4-kexecboot and booting raw partitions

We can now boot distros with droid4-kexecboot without being locked to the stock initramfs or rootfs :
droid4-kexecboot images
droid4-kexecboot buildroot source
It works by using utagboot generated mmcblk1p8 utags partition to boot the stock kernel to a 4MB buildroot image that can be flashed to the unused mmcblk1p13 bpsw partition. Then it starts kexecboot to use kexec for booting to the selected distro.
Currently supported are recent mainline kernels with the pending LCD patches added. SafeStrap is not necessary but can be booted to. And v3.0.8 legacy kernels installed into SafeStrap rom slots are supported (but need to be manually updated if slot kernels are updated) .
UPDATED: Booting to the stock Android and SafeStrap is now supported out of the box with for pivot_root.
Changes are needed to v3.0.8 kernel config and initramfs to not use CONFIG_CMDLINE_FORCE=y and safestrap/active_slot file and instead just use kernel cmdline to mount the desired rootfs. Distros using the mainline kernel do not have these limitations, and can use the 608MB mmcblk1p22 preinstall, 1.3GB mmcblk1p23 webtop partitions. And the 8GB mmcblk1p25 can also be reformatted to ext4 and used as rootfs if you don't need it for Android. I have not dared to try to reformat mmcblk1p20 system partition, but that too might be usable unless the Motorola bootloader does some checks on it on boot.
There are some experimental patches for initramfs modifications for postmarketos:
https://github.com/postmarketOS/pmbootstrap/pull/1039
But we need also similar Android changes if somebody has time to work on patching and rebuilding LineageOS

Nice, this works with lineage os on slot 1 now. Im currently building postmarketos and a mainline kernel to test

The bootloader refuses to boot with mmcblk1p20 erased. But a empty ext3 partiton is apperently enough to make it happy

IM_back! said:
The bootloader refuses to boot with mmcblk1p20 erased. But a empty ext3 partiton is apperently enough to make it happy
Click to expand...
Click to collapse
Oh interesting I don't think I've seen that. Do you mean the Motorola bootloader refuses to start or kexecboot? Sounds like we should document this and how to fix it if it happens if you can write up something on it for droid4-kexecboot README file.

tmlind said:
Oh interesting I don't think I've seen that. Do you mean the Motorola bootloader refuses to start or kexecboot? Sounds like we should document this and how to fix it if it happens if you can write up something on it for droid4-kexecboot README file.
Click to expand...
Click to collapse
The Motorola booloader goes directly to fastboot if i:
Code:
dd if=/dev/zero of=/dev/block/mmcblk1p20
but
Code:
mkfs.ext3 /dev/block/mmcblk1p20
keeps the Motorola bootloader happy. im not shure if it needs to be ext3 i just whent with that because thats what the stock rom uses. It is extreamly annoying that we can not flash modified system.img's via fastboot. I will experiment a bit more with it and submit a patch to the README file.
I got The mainline kernel to boot, but without a rootfs it dosent do anything usefull of course.
that aside i can't seam to get postmarketos to work. I installed pmos rootfs to the webtop partiton and supplyed kernel command line with PMOS_NO_SAFESTRAP and correct root= but it just boots to a black screen , no uart output either
Do you have something that works that i could take a look at?

IM_back! said:
The Motorola booloader goes directly to fastboot if i:
Code:
dd if=/dev/zero of=/dev/block/mmcblk1p20
but
Code:
mkfs.ext3 /dev/block/mmcblk1p20
keeps the Motorola bootloader happy. im not shure if it needs to be ext3 i just whent with that because thats what the stock rom uses. It is extreamly annoying that we can not flash modified system.img's via fastboot. I will experiment a bit more with it and submit a patch to the README file.
Click to expand...
Click to collapse
Interesting so it seems that the cdt.bin mmcblk1p6 partition tells mbmloader to check some partitions for content and some partitions just for the fs. I wonder if also for example cdrom mmcblk1p16 partition can be modified too that way.
IM_back! said:
I got The mainline kernel to boot, but without a rootfs it dosent do anything usefull of course.
that aside i can't seam to get postmarketos to work. I installed pmos rootfs to the webtop partiton and supplyed kernel command line with PMOS_NO_SAFESTRAP and correct root= but it just boots to a black screen , no uart output either
Do you have something that works that i could take a look at?
Click to expand...
Click to collapse
As a test I only verified that NotKit's kernel mentioned in his postmarketos pull request boots with uart with kexecboot after I noticed he has a patch for gcc6 support and APKBUILD prepare -Werror search and replacement
I enabled CONFIG_EMU_UART_DEBUG=y, disabled CONFIG_CMDLINE_FORCE and configured kexecboot boot.cfg to use CMDLINE=console=ttyO2,115200 [email protected] vram=10300K omapfb.vram=0:8256K,1:4K,2:2040K ro rootwait root=/dev/mmcblk1p13 debug earlyprintk' to boot back to droid4-kexecboot.

tmlind said:
As a test I only verified that NotKit's kernel mentioned in his postmarketos pull request boots with uart with kexecboot after I noticed he has a patch for gcc6 support and APKBUILD prepare -Werror search and replacement
Click to expand...
Click to collapse
FYI, the postmarketos pull request mentioned above has been now merged. And I pushed out updated droid4-kexecboot images last night that now also support booting to the stock Android and SafeStrap.

I will be trying to get this thing to boot for my phone motorola electrify 2. Don't have much of knowledge but atleast trying is not going cost me alot .

mmcblk1p16 partition is usable as alternative ISO storage
tmlind said:
Interesting so it seems that the cdt.bin mmcblk1p6 partition tells mbmloader to check some partitions for content and some partitions just for the fs. I wonder if also for example cdrom mmcblk1p16 partition can be modified too that way.
Click to expand...
Click to collapse
Actually, after some trial and error I managed to turn the cdrom partition (mmcblk1p16) into something more useful. Now my maserati works as a portable "Linux booting device"
When plugged to a computer it behaves by default as a CD-ROM drive, and it's capable of booting a Linux ISO on the PC. Bear in mind that the partition size is slightly above 200 MB, so we have limited space. Apparently if mmcblk1p16 is formatted as ext3, ext4 or contains a filesystem other than ISO, the phone will NOT boot (I had to reinstall the whole Stock firmware a few times).
I could make a mini tutorial with detailed instructions.
So perhaps this partition could be useful for storing a customised read-only distro for the maserati, similar to a Live environment. Or at least capable of booting a minimum environment with essential files.
I'd like to test your kexec files as soon as I can, but still need to understand the whole process. About to receive a second maserati for tests
Cheers!

dinosaur99 said:
Actually, after some trial and error I managed to turn the cdrom partition (mmcblk1p16) into something more useful. Now my maserati works as a portable "Linux booting device"
Click to expand...
Click to collapse
Hey that's great! FYI, one more thing to consider is that I noticed allow-mbmloader-flashing-mbm.bin is more permissive compared to mbm.bin. They seem to parse some permissions table from cdt.bin. I guess it would not be too hard to figure out that format if somebody cares. And I now also wonder if using cdt.bin_patch instead of cdt.bin is even more permissive?
Anyways, do not mess with the mbmloader.bin or allow-mbmloader-flashing-mbm.bin partitions though that can brick the device..

tmlind said:
FYI, the postmarketos pull request mentioned above has been now merged. And I pushed out updated droid4-kexecboot images last night that now also support booting to the stock Android and SafeStrap.
Click to expand...
Click to collapse
Thank you for your excellent work!

Can't boot to safestrap
This is my first approach to boot something other than Android. Not very usable though, but I got this far.
I first installed droid4-kexecboot following instructions on README, and created the boot/boot.cfg on a fresh EXT4 sdcard by copying the sample rom-slot1 and rom-slot2 entries. After reboot, kexecboot shows a very nice graphical menu, and loads successfully all configurations. Unfortunately the slot entries don't work from kexecboot (phone restarts). However I can load Safestrap and boot stock and both ROM slots.
Then I built latest postmarketOS for Droid 4 using pmbootstrap, and selected Weston (one of the lightweight flavours). The result is three files: kernel, initramfs and a disk image containing two partitions. In order to install pmOS into rom-slot2, I wiped all slot2 partitions and installed CM11 as explained here https://wiki.postmarketos.org/wiki/Motorola_Droid_4_(motorola-maserati) . The next steps were done locally on my laptop instead of using ADB (i.e. replace file userdata.img in rom-slot2 directory with the pmOS disk image, and also replace /etc/kexec/ramdisk.img and /etc/kexec/kernel located inside system.img with the new initramfs/kernel). Then rebooted, jumped from kexecboot to Safestrap, and it launched postmarketOS.
USB networking connects right away and SSH works.
The wiki states that Framebuffer graphics works, but I get no screen output. LCD backlight is on. Xwayland and weston are running by default.
All LEDs work.
Touchscreen, vol buttons and keyboard seem to work.
Kernel is 3.0.8.
Finally I managed to boot pmOS with kexecboot. Directory "boot" on mmcblk0p1 contains following files:
Code:
atags # borrowed from safestrap
boot.cfg
devtree # borrowed from safestrap
initramfs-motorola-maserati
vmlinuz-motorola-maserati
Here's a few facts that I don't really understand
kexecboot boots pmOS on rom-slot only if safestrap is configured to boot on that slot, otherwise it boots into something else which responds to ping, but no SSH. Why is this happening if kexecboot overrides safestrap?
Excuse my ignorance, but what is in practice the need for a devtree file, and where am I supposed to obtain it?
The kernel cmdline is apparently overriden by atags file required to boot linux 3.0.8. It seems like boot configuration is hardcoded somehow. But why doesn't it boot regular android slots?
Is it actually possible to pass something like root=/dev/mmcblk0p1 or maybe even get screen working by using a recent kernel?
Sorry if I mixed up too many different topics... just trying to sort the whole thing out.
Thanks!

Is it possible to boot LineageOS with a Linux kernel of 3.20 or higher?

dinosaur99 said:
Here's a few facts that I don't really understand
kexecboot boots pmOS on rom-slot only if safestrap is configured to boot on that slot, otherwise it boots into something else which responds to ping, but no SSH. Why is this happening if kexecboot overrides safestrap?
Excuse my ignorance, but what is in practice the need for a devtree file, and where am I supposed to obtain it?
The kernel cmdline is apparently overriden by atags file required to boot linux 3.0.8. It seems like boot configuration is hardcoded somehow. But why doesn't it boot regular android slots?
Is it actually possible to pass something like root=/dev/mmcblk0p1 or maybe even get screen working by using a recent kernel?
Sorry if I mixed up too many different topics... just trying to sort the whole thing out.
Click to expand...
Click to collapse
Sorry for being slow to respond..
There is an issue with most droid4 images using the 3.0.8 kernel files and init scripts which is the scripts check the SafeStrap config from the mmc for things to mount etc.
This is no longer needed at and the scripts should be just modified to do that only if booted with safestrap. We should now just use standard Linux way meaning
parse the partitions to mount from kernel command line and so on NotKit posted some patches to sort out that as linked in the first post in this thread for the
PostmarketOK pull request. But I don't think those are applied and also the Android Images need to be updated too for LineageOS and then you can just boot
Android from whatever partition you like such as mmcblk0p1 or mmcblk1p25 in the standard Android way.
So omebody just please do standard LineageOS images that don't rely on SafeStrap!
The devtree file is only needed for old 3.0.8 kernels and is non-compatible with the current mainline kernel dtb file omap4-droid4-xt894.dtb. Motorola used custom
device tree properties and it's in big-endian format. The devtree file should be the same as what you have on the eMMC devtree partition mmcblk1p11.
Current mainline kernel still has the LCD patches pending, for v4.19-rc series I posted the pending patches I have to:
https://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git/log/?h=droid4-pending-v4.19
Those are still being worked on though because of omapdrm changing over to use generic displays.

andeaker said:
Is it possible to boot LineageOS with a Linux kernel of 3.20 or higher?
Click to expand...
Click to collapse
See the previous post about v4.19-rc5 kernel status. No idea how much work it would be to get LineageOS images working with the
mainline kernel.. Probably at least the graphics would be an issue. Using TI's Android tree with droid4 patches backported to it might
be a good starting point if somebody wants to experiment with that, TI might have SGX540 support there for other SoCs.

how would i go about getting this working n the droid bionic? im wanting to run maemo-leste, but the latest update switched from just safestrap and ddroid, to this. and apparently trying to stupidly flash this as-is didnt work out

tvall said:
how would i go about getting this working n the droid bionic? im wanting to run maemo-leste, but the latest update switched from just safestrap and ddroid, to this. and apparently trying to stupidly flash this as-is didnt work out
Click to expand...
Click to collapse
Hmm you probably need to stick with SafeStrap for bionic, I don't think bionic uses a utags partition that's needed for the kernel cmdline.

tmlind said:
So omebody just please do standard LineageOS images that don't rely on SafeStrap!
Click to expand...
Click to collapse
I finally got around finishing writing some docs for installing LineageOS to raw partitions, please test
Make back-ups as needed first though.
For instructions, see files PARTITIONS and INSTALL at:
https://github.com/tmlind/droid4-kexecboot

hope this is on-topic - is it possible to use this to boot an OS that's installed on the SD card? I don't have D4 yet, but am waiting to receive one in the next few weeks.

sicelo.m said:
hope this is on-topic - is it possible to use this to boot an OS that's installed on the SD card? I don't have D4 yet, but am waiting to receive one in the next few weeks.
Click to expand...
Click to collapse
Yeah you can boot whatever Linux distro(s) you prefer from the SD card with the current mainline kernel and few pending patches.
That's all work in progress though, certainly usable for tinkering though
I doubt that booting Android on the SD card currently works though.

[Discussion] TREBLE Support for Motorola G5s

Hello developers ( @kalyansundhar@govind1233 @lohanbarth @squid2),
I think everybody heard of project Treble. (Link, Link)
Of course Motorola isn't going to support it to our device(OTA update with repartition is very risky).
But somebody did already a unofficial port to the Xiaomi redmi note 4. This device isn't the same as the Moto G5s.
Today there is a developer doing it to the Xiaomi redmi 3s(Screenshots). This device is almost the same as the Moto G5s.
Specs of Xiaomi redmi 3s(Link)
Qualcomm MSM8937 Snapdragon 430
Adreno 505
5.0 inches
Accelerometer, gyro, proximity, compass
16 GB, 2 GB RAM
Specs of Moto G5s (Link)
Qualcomm MSM8937 Snapdragon 430
Adreno 505
5.2 inches
Fingerprint (front-mounted), accelerometer, gyro, proximity, compass
32 GB, 3 GB RAM
Do you developers think its possible for the Motorola G5s?
If this works we can make a lot of custom roms based on Treble.

Update
I think we must use OEM partition as Vendor partition.
Since a new partition was required for full treble we converted an unused cust partition into vendor which is almost 830mb in size, No we are not re-partitioning your device or anything else which may hardbrick your device
(Source)

GoldeneyeS2 said:
Update
I think we must use OEM partition as Vendor partition.
Since a new partition was required for full treble we converted an unused cust partition into vendor which is almost 830mb in size, No we are not re-partitioning your device or anything else which may hardbrick your device
(Source)
Click to expand...
Click to collapse
We could take one step at a time. First within the current setup, we should separate system and vendor libraries completely. There should not be any mix. Means /system/lib and /system/bin should have only system related. Similarly /system/vendor/lib and /system/vendor/bin should have only vendor related stuff. If we make the device work with this change, then it would be easy to make 'vendor' as separate partition. Even now we have /vendor folder in device root. This is just a symlink to /system/vendor, not a partition. In my opinion this would be a better way to go. Please correct me if I am wrong.
Thanks
KS

kalyansundhar said:
We could take one step at a time. First within the current setup, we should separate system and vendor libraries completely. There should not be any mix. Means /system/lib and /system/bin should have only system related. Similarly /system/vendor/lib and /system/vendor/bin should have only vendor related stuff. If we make the device work with this change, then it would be easy to make 'vendor' as separate partition. Even now we have /vendor folder in device root. This is just a symlink to /system/vendor, not a partition. In my opinion this would be a better way to go. Please correct me if I am wrong.
Thanks
KS
Click to expand...
Click to collapse
Its a good idea to take one step at the time.
What's wrong with this vendor tree? https://github.com/kayesk/android_ve...torola_montana
Project Treble on the Xiaomi Redmi Note 4
How did he do it? He used the “cust” partition on the device for his make-shift vendor partition. The cust partition normally holds a lot of device-specific stuff from MIUI, so it’s essentially wasted space on an AOSP build. Using the approximately 830MB unused partition, he moved the vendor HALs from system into cust without needing to repartition—which was a justification that OEMs such as Nokia and OnePlus used in their statements about why they weren’t going to bring Treble compatibility to their devices
We can use OEM partition. But what's the size of the OEM partition? And how do we make the HAL files?
We can also wait for the xiami 3s and port it to our phone.

GoldeneyeS2 said:
Its a good idea to take one step at the time.
What's wrong with this vendor tree? https://github.com/kayesk/android_ve...torola_montana
Click to expand...
Click to collapse
There is nothing wrong with the vendor tree you mentioned. You take any device tree in github, you could notice mix of libraries and binaries in /system/lib and /system/bin folder. It was ok to have it mixed till Nougat. But with Oreo and with the introduction of HIDL, things are changed. In Nougat we had only one binder. But in Oreo we have 3 binders (binder, hwbinder and vndbinder). Inter process communication is dealt differently. Even with OREO the mixed setup would work. But If we want to go Treble route, then it is better to move out remaining vendor binaries and libraries from /system partition.
We can download the factory image of one of the Pixel like BULLHEAD, MARLIN, etc. And study how the system and vendor partitions are laid out in their OREO release. Theoretically a treble supported system image should be device and make independent (a plain android system). Boot and Vendor partitions would be device specific. I mentioned boot partition here because it would be having device specific boot scripts like init.qcom..., init.mmi..., etc.
Thanks
KS

kalyansundhar said:
There is nothing wrong with the vendor tree you mentioned. You take any device tree in github, you could notice mix of libraries and binaries in /system/lib and /system/bin folder. It was ok to have it mixed till Nougat. But with Oreo and with the introduction of HIDL, things are changed. In Nougat we had only one binder. But in Oreo we have 3 binders (binder, hwbinder and vndbinder). Inter process communication is dealt differently. Even with OREO the mixed setup would work. But If we want to go Treble route, then it is better to move out remaining vendor binaries and libraries from /system partition.
We can download the factory image of one of the Pixel like BULLHEAD, MARLIN, etc. And study how the system and vendor partitions are laid out in their OREO release. Theoretically a treble supported system image should be device and make independent (a plain android system). Boot and Vendor partitions would be device specific. I mentioned boot partition here because it would be having device specific boot scripts like init.qcom..., init.mmi..., etc.
Thanks
KS
Click to expand...
Click to collapse
https://forum.xda-developers.com/xiaomi-redmi-3s/development/oreo-xperience-12-t3672111/
TEST build with vendor:
xperience-12.1.0-20180214-NIGHTLY-land.zip
-----------------------
Initial treble support
U need a custom recovery
Downlaod from here!
http://downloads.hostingsharedbox.com/ascarex/XPerience/12/land/3.2.0.1-TWRP-Land-Treble.img
Download the rom from here!.
http://downloads.hostingsharedbox.c...nd/xperience-12.1.0-20180214-NIGHTLY-land.zip
remember this is a initial work may contain some bugs if u are in older xperience build u not need to perform a clean install
Root u need this
https://drive.google.com/a/my.smccd.edu/uc?id=1oi5G-zzmPMX-WurvyiFRF1u1JjGr-Jvt&export=download
was made by abhishek987 AKA TheScarastic for the redmi note 4
https://forum.xda-developers.com/showpost.php?p=75527103&postcount=2233

Moto g5s doesn't support compass.. (model XT1797) and several model doesn't have NFC too

michael50310 said:
Moto g5s doesn't support compass.. (model XT1797) and several model doesn't have NFC too
Click to expand...
Click to collapse
That's not a big problem.

GoldeneyeS2 said:
https://forum.xda-developers.com/xiaomi-redmi-3s/development/oreo-xperience-12-t3672111/
TEST build with vendor:
xperience-12.1.0-20180214-NIGHTLY-land.zip
-----------------------
Initial treble support
U need a custom recovery
Downlaod from here!
http://downloads.hostingsharedbox.com/ascarex/XPerience/12/land/3.2.0.1-TWRP-Land-Treble.img
Download the rom from here!.
http://downloads.hostingsharedbox.c...nd/xperience-12.1.0-20180214-NIGHTLY-land.zip
remember this is a initial work may contain some bugs if u are in older xperience build u not need to perform a clean install
Root u need this
https://drive.google.com/a/my.smccd.edu/uc?id=1oi5G-zzmPMX-WurvyiFRF1u1JjGr-Jvt&export=download
was made by abhishek987 AKA TheScarastic for the redmi note 4
https://forum.xda-developers.com/showpost.php?p=75527103&postcount=2233
Click to expand...
Click to collapse
Wait i'm a little confused. Did you post this rom for our device, because it looks like it's for the Redmi 3s. I know the whole idea is beased on this device, but i'm still confused. Don't want to flash anything and brick my device. Sorry if i'm being dumb, just want to be sure

Joseph Hill said:
Wait i'm a little confused. Did you post this rom for our device, because it looks like it's for the Redmi 3s. I know the whole idea is beased on this device, but i'm still confused. Don't want to flash anything and brick my device. Sorry if i'm being dumb, just want to be sure
Click to expand...
Click to collapse
Don't use this on Motorola G5s. Its for the Redmi 3s.
If there will be a version you will find it in another thread.

@vaserbanix (https://forum.xda-developers.com/moto-g5s/development/kernel-tweaks-t3744384/page2)
also i repaked that XperienceOS for mi3s from new.dat to meta-data for better wiev without install
download the rom and study it
https://drive.google.com/open?id=1Cp...L_gtJ1zQIqIOca
!!! do not install it!!!!
@kalyansundhar
Can you use this?

Many thanks for your hard work.
Can you maybe release your software on github?
I want to used it for the Motorola G5s. Its almost the same device only I need not suc as vendor but OEM as vendor. But that can I fix if I have your code.
Yeah I have it for Moto Z play too but u need to wait until my isp fix my internet issues , so for now I can't upload the source sorry
I hope it can be fixed in 3 days
-------------------------------------------------------------------
I ask the developer to release his source code. We have to wait till his internet is fixed:laugh:

Look there is a ARM 32bits system image thats support's Treble
Download:
v12 (android-8.1.0_r15):
system.img for A/B ARM64 devices with GApps and SU
system.img for A/B ARM64 devices vanilla
system.img for A-only ARM64 devices with GApps and SU
system.img for A-only ARM64 devices vanilla
system.img for A-only ARM32 devices vanilla
Patches for custom ROMs build
Source: https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659

Dear members, any luck with porting MIUI for Moto G5s plus?
Request you to please guide and share link.