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

Device Essential Material *** Firmware, Source Code, Root etc.***

This thread will list and link to all core device essential stuff.
PM me if there is new stuff or something doesn't work please​
STOCK ASUS FIRMWARE
WW_epaduser_11_4_1_17_UpdateLauncher.zip: HERE
US_epaduser_11_4_1_17_UpdateLauncher.zip: HERE
WW_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
US_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
CN_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
TW_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
US_epaduser_10_26_1_7_UpdateLauncher.zip: HERE
TW_epaduser_10_26_1_7_UpdateLauncher.zip: HERE
CN_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
JP_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
US_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
WW_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
CN_epaduse_10_14_1_45_UpdateLauncher.zip: HERE
How to flash:
Step 1: Download and unzip the zipfile of your choice.
Step 2: Copy the new Zipfile and paste it in root directory of your internal SdCard, then reboot the device and the update will automatically start.
ASUS SOURCE CODE
kernel_10_14_1_42.rar: HERE
kernel_10_14_1_45.rar: HERE
kernel_10_14_1_47.rar: HERE
kernel_10_26_1_7.rar: HERE
kernel_10_26_1_18.rar: HERE
kernel_11_4_1_17.rar: HERE
UNLOCK YOUR DEVICE
0820-0954_SIGNED_UnLock_for_TF701_repart.apk: HERE
How to unlock:
- Download the Asus unlock app
- Install and run the app. This will require a valid google account (if you use one time passwords, you'll need to generate one for this purpose) and internet access.
- When booting with [vol-] + [power] pressed, the transformer will show the message "The device is unlocked"
ROOT TOOLS
Read here: http://forum.xda-developers.com/showthread.php?t=2516215
CUSTOM RECOVERY
CWM Recovery V6.0.4.8. for 4.3*: HERE
ATTENTION: you must have an unlocked bootloader
How to flash this:
- reboot device into fastboot mode:
- adb reboot bootloader
- now flash the recovery using : fastboot flash recovery recovery.img [where recovery.img is the name of the file image you downloaded]
CUSTOM ROM'S
By Sbdags based on stock with quite some enhancements: HERE
CyanogenMod 11 Preview Proxy thread: HERE
THEMES
Non available yet
BOOTANIMATIONS
Non available yet
OTHER MOD'S
None available yet
PARTITION INFORMATION**
Code:
name device mountpoint fs description
/dev/block/platform/sdhci-tegra.3/ADF /dev/block/mmcblk0p7 /ADF ext4 ?
/dev/block/platform/sdhci-tegra.3/APD /dev/block/mmcblk0p6 /APD ext4 ASUS Product Demo
/dev/block/platform/sdhci-tegra.3/APP /dev/block/mmcblk0p4 /system ext4 Android OS
/dev/block/platform/sdhci-tegra.3/CAC /dev/block/mmcblk0p5 /cache ext4 recovery logs
/dev/block/platform/sdhci-tegra.3/CRA /dev/block/mmcblk0p11 ?
/dev/block/platform/sdhci-tegra.3/DTB /dev/block/mmcblk0p2 ?
/dev/block/platform/sdhci-tegra.3/EKS /dev/block/mmcblk0p13 NVEKSP
/dev/block/platform/sdhci-tegra.3/LNX /dev/block/mmcblk0p3 Linux kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/MDA /dev/block/mmcblk0p12 ?
/dev/block/platform/sdhci-tegra.3/MSC /dev/block/mmcblk0p8 empty (misc, bootloader etc.)
/dev/block/platform/sdhci-tegra.3/PER /dev/block/mmcblk0p10 /persist ext4 config/calibration data
/dev/block/platform/sdhci-tegra.3/SOS /dev/block/mmcblk0p1 Recovery kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/UDA /dev/block/mmcblk0p14 /data ext4 Android user data
/dev/block/platform/sdhci-tegra.3/USP /dev/block/mmcblk0p9 Staging (blob)
RECOVERY.FSTAB**
Code:
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/devices/platform/sdhci-tegra.2/mmc_host/mmc1 /storage/sdcard1 vfat default voldmanaged=sdcard:auto
/devices/platform/tegra-ehci.0 /mnt/usbdrive vfat default voldmanaged=usbdrive:auto
BLOB**
Code:
name size description status
10.14.1.47: [ATTACH]2435244[/ATTACH]
blob.BCT 8,192 Bytes Boot Config Table (original) [ATTACH]2435246[/ATTACH]
blob.BC1 8,192 Bytes ? (original) [ATTACH]2435245[/ATTACH]
blob.EBT 1,396,736 Bytes Bootloader (original) [ATTACH]2435247[/ATTACH]
blob.PT 2,202 Bytes Partition Table (original) [ATTACH]2435248[/ATTACH]
10.26.1.7: [ATTACH]2435238[/ATTACH]
blob.BCT 8,192 Bytes Boot Config Table (unchanged) [ATTACH]2435241[/ATTACH]
blob.BC1 8,192 Bytes ? (changed) [ATTACH]2435240[/ATTACH]
blob.EBT 1,421,312 Bytes Bootloader (changed) [ATTACH]2435242[/ATTACH]
**= Thanks to Ipdunwell for sharing this info
HOW TO UNBRICK YOUR DEVICE
Read here: http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1
ATTENTION​
YOUR WARRANTY COULD BE VOID DUE TO ROOTING AND UNLOCKING YOUR DEVICE (depending of which country you reside)
I am NOT responsible for bricked devices, dead SD cards or dead docks.
Please do some research if you have any concerns about the files here BEFORE flashing anything!
When you have no clue what we are talking about here you better leave your hands off it!!
YOU are choosing yourself freely to use these file(s) all by yourself!!!​

Updated Recovery for 4.3 with working "external" SD card, found here
http://forum.xda-developers.com/show....php?t=2621051
Custom Rom's
Cromi-x
http://forum.xda-developers.com/show....php?t=2608129
CM11 -Preview (Unofficial)
http://forum.xda-developers.com/show....php?t=2621028

Delete

Root and firmware.
Hello all. I'm new to the site, and very sorry if this is a dumb question, but Id rather sound dumb than brick my transformer.. I'm planning to root my TF701 following lpdunwells guide. One of the prerequisites is to have 10.14.1.47 as the firmware version. My question is this.. When I unlock my bootloader and it wipes my tablet, will it reset me back to the original firmware version? Or will this matter?
My current firmware version is 10.26.1.18
Thank you very much in advance for your help, also, I will greatly appreciate any and all help and info regarding this matter.

tf701mega said:
Hello all. I'm new to the site, and very sorry if this is a dumb question, but Id rather sound dumb than brick my transformer.. I'm planning to root my TF701 following lpdunwells guide. One of the prerequisites is to have 10.14.1.47 as the firmware version. My question is this.. When I unlock my bootloader and it wipes my tablet, will it reset me back to the original firmware version? Or will this matter?
My current firmware version is 10.26.1.18
Thank you very much in advance for your help, also, I will greatly appreciate any and all help and info regarding this matter.
Click to expand...
Click to collapse
If you want to root then use my guide as it is for 10.26.1.18. Downgrading to .47 and back up again is really painful.

download problem
Hi OP,
Download links are down...
please fix theme?

henengel said:
Hi OP,
Download links are down...
please fix theme?
Click to expand...
Click to collapse
anyone know where I can get the files? links are broken

kuthedude said:
anyone know where I can get the files? links are broken
Click to expand...
Click to collapse
Which files are you looking for?
Most of the files are available from ASUS's website and the ROM and recovery links are old and newer ones are available in the Development section of this form.

Sorry for the inconvenience.
Asked in the OP to PM me if there is new stuff or if somethings doesn't work but received nothing.
Files will be back end of the day with latest firmware and kernel source.

Hi, I am getting my tablet soon, and I am assuming the tablet will be on 4.3 or earlier by the time I get it.
What firmware/kernal/boot loader is the best setup to get me onto the latest 4.3 OS. I only am wanting this because I want to avoid the 4.4.2 battery drain issues (since I am most likely going to flash an AOSP ROM after I get this tablet).
Also, how would I be able to properly update the tablet with the firmware/kernal/boot loader? Thanks for the help!
Sent from my SCH-I545 using Tapatalk 2

Hi, I tried pushing my firmware file to root, but it wouldn't work. I would use root explorer and it would just freeze and restart. anyone know why this would happen? Im trying to update to 4.3 without getting into 4.4.2. please help if you can

You have to unpack the file, inside this is another zip file. Put it then in sd root this should work as far as i know
Gesendet von meinem LG-D855 mit Tapatalk

Hi
There is a new firmware version 11.4.1.27.
Is it posible to add this version to the post?

[DEV] Kazam Thunder Q4.5 Development Thread {CWM} {SYS-IMG}

So I was at XDA DevCon and Kazam donated me one of their Thunder Q4.5 devices, I'm going to be doing my best to bring much loved XDA goodies to this device, there is no time schedule or eta's, this will go at the pace at which I can go!
I am aware that a few others won the Thunder Q4.5 during giveaways, so if you want to help in getting some development love on this device then feel free. I'm also aware that a lot of people probably don't own this device, so if it's just me documenting and bringing things to the device then so be it!
System
I've gained root and dumped /system, available here for inspecting: https://www.androidfilehost.com/?fid=23681161096071461
Recovery & Boot
CWM Recovery working on the Kazam Thunder 4.5Q
You need MTK Droid Root & Tools to install:
1) Select the "root, backup, recovery" tab
2) Select the "Install already prepared files" button and hit "Recovery and Boot"
3) For the Boot.img select the downloaded Boot.img below and for recovery select the Recovery.img below.
4) When you get the "Install patched boot to phone" window, select "Yes"
5) When you get to "Install created recovery" select "Yes".
6) When asked to reboot into recovery, that is down to you!
7) Profit!
Recovery: https://www.androidfilehost.com/?fid=95747613655040353
Patched Boot Img: https://www.androidfilehost.com/?fid=95747613655040352
Old Documentation:
This is where some tricky stuff is, I've never dealt with a device that doesn't have a dedicated /recovery other than Xperia who combine it with /boot though that is easy to deal with.
As we can see here:
Code:
Partition Information:
preloader 0x0000000000c00000 0x0000000000000000 2 /dev/misc-sd
mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1
pro_info 0x0000000000300000 0x0000000000100000 2 /dev/block/mmcblk0
nvram 0x0000000000500000 0x0000000000400000 2 /dev/block/mmcblk0
protect_f 0x0000000000a00000 0x0000000000900000 2 /dev/block/mmcblk0p2
protect_s 0x0000000000a00000 0x0000000001300000 2 /dev/block/mmcblk0p3
seccfg 0x0000000000020000 0x0000000001d00000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000001d20000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x0000000001d80000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000002380000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x0000000002980000 2 /dev/block/mmcblk0p4
misc 0x0000000000080000 0x0000000002f80000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000003000000 2 /dev/block/mmcblk0
ebr2 0x0000000000080000 0x0000000003300000 2 /dev/block/mmcblk0
expdb 0x0000000000a00000 0x0000000003380000 2 /dev/block/mmcblk0
android 0x000000002bc00000 0x0000000003d80000 2 /dev/block/mmcblk0p5
cache 0x0000000007e00000 0x000000002f980000 2 /dev/block/mmcblk0p6
usrdata 0x0000000040000000 0x0000000037780000 2 /dev/block/mmcblk0p7
fat 0x000000006fc00000 0x0000000077780000 2 /dev/block/mmcblk0p8
bmtpool 0x0000000001500000 0x00000000ff3f00a8 2 /dev/block/mmcblk0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc boot (null) 0
2 /cache ext4 /dev/block/mmcblk0p6 (null) 0
3 /data ext4 /dev/block/mmcblk0p7 (null) 0
4 /misc emmc misc (null) 0
5 /recovery emmc recovery (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk0p8 0
7 /system ext4 /dev/block/mmcblk0p5 (null) 0
8 /sdcard2 vfat /dev/block/mmcblk0p8 (null) 0
mbr, pro_info, nvram, seccfg, uboot, bootimg, recovery, misc, logo, ebr2, expdb, bmtpool
These are all in /dev/block/mmcblk0 and we want hold of bootimg and recovery as these are the important ones!
There is a hexadecimal offset of some sort by the looks of things:
Code:
recovery 0x0000000000600000 0x0000000002380000 2 /dev/block/mmcblk0
Converting these in to deciaml values give:
Code:
recovery 6291456 37224448 2 /dev/block/mmcblk0
The issue lies with the fact that this looks like over 2gig or something, a recovery image is not that big, should be <10mb.

Awesome, I wondered if anyone would be posting work for kazam.
I'm hoping to move onto mtk after L drops (specifically the upcoming kazam device).
Do you remember the name of the guy who was at the booth?

cybojenix said:
Awesome, I wondered if anyone would be posting work for kazam.
I'm hoping to move onto mtk after L drops (specifically the upcoming kazam device).
Do you remember the name of the guy who was at the booth?
Click to expand...
Click to collapse
Yeah I think he was called David, I've got his card around somewhere. He said he'd send me kernel source but haven't heard anything.
I don't think there are many people supporting it haha
I'll be doing what I can regarding mtk, kazam and L when it drops

matt4321 said:
Yeah I think he was called David, I've got his card around somewhere. He said he'd send me kernel source but haven't heard anything.
I don't think there are many people supporting it haha
I'll be doing what I can regarding mtk, kazam and L when it drops
Click to expand...
Click to collapse
@dave79
I have the source code, but I'm having serious problems in compiling it (Thunder2 5.0) - haven't set it up on git yet but below is the shared dropbox folder, looks like your email address is "pending" on the shared options (maybe check your email?).
https://www.dropbox.com/sh/aj0tjqzh9fzsf57/AABCgx-Yhc71CVjTcmRkM9P2a?dl=0
To build the kernel for Thunder2_50, you will need the dct folder I put in Tools - this took me ages to find and edit for the MT6582 chip (the original I downloaded didn't like the codegen file for konka82_wet_i277), for the ThunderQ 4.5 you should be OK though, I noticed a lot of stuff is missing in the Thunder2_50 source code...

Hi there,
This is Dave from Kazam. Let me know if there's anything else you need. I'll gladly share the source code of the Q4.5, just PM me with your email and I'll share my Dropbox link. (I'll upload it here when I get back from my vacation (oh yeah, I'm in Spain ).
Thanks all
Dave

Jonny said:
@dave79
I have the source code, but I'm having serious problems in compiling it (Thunder2 5.0) - haven't set it up on git yet but below is the shared dropbox folder, looks like your email address is "pending" on the shared options (maybe check your email?).
https://www.dropbox.com/sh/aj0tjqzh9fzsf57/AABCgx-Yhc71CVjTcmRkM9P2a?dl=0
To build the kernel for Thunder2_50, you will need the dct folder I put in Tools - this took me ages to find and edit for the MT6582 chip (the original I downloaded didn't like the codegen file for konka82_wet_i277), for the ThunderQ 4.5 you should be OK though, I noticed a lot of stuff is missing in the Thunder2_50 source code...
Click to expand...
Click to collapse
Wow the 4.2 mtk code base really sucks. I'm glad it's a lot better with 4.4, and I hear all the hals now work against aosp.
Thanks for uploading the sources here

I'm about to embark on the challenge of porting CM12/AOSP L to the thunder q4.5, I shall make a seperate forum thread for this project as of when I get a first build, any volunteers for testing my ports of CM12 would be great, pm me if interested, and then I'll give you a download to the first flashable zip i get compiled. Also, just to make you guys aware when flashing, if you decide to take any of my ports, I will be configuring it to install TWRP along with CM12, incase you don't already have TWRP installed, it shall be installed when flashing.
Also, this may take some time to create even an initial release, as to quote Dees_Troy on irc earlier "Porting CM to MediaTek devices is a *****"
Also, if I get the time, then I will continue to update a cm12 for this device as often as I can, I will eventually have a dropbox shared folder publicly accessible with all the versions made so far available to download.
@matt4321 You're not the only one working on bringing XDA loved stuff to this device
Note: if we can get a separate forum for the thunder q4.5, I will be moving this post to a new thread over there. Also, anyone interested in being alpha/beta testers, pm me and I'll add you to the shared dropbox where I will be uploading all the builds, as I get round to making them

Help! I flashed recovery and camera stopped working! Is there a way to bring it back to it's out-of-the-box state? (with original recovery and stuff) IT'S URGENT!!!!

drumandbassfreak said:
Help! I flashed recovery and camera stopped working! Is there a way to bring it back to it's out-of-the-box state? (with original recovery and stuff) IT'S URGENT!!!!
Click to expand...
Click to collapse
That's really weird, mine works fine. Try doing it again and see what happens. Well you'd need to flash back to stock. I don't actually have the stock files unfortunately, ask in the Q&A section to see if anyone has the stock recovery and kernel

Thanks, I'm gonna do it! I know thats weird, how in the world would be the recovery related to the camera??

How do I open The IMG that you uploaded. PowerISO says it is corrupted

drumandbassfreak said:
How do I open The IMG that you uploaded. PowerISO says it is corrupted
Click to expand...
Click to collapse
You need to mount it in Ubuntu or a similar distro to access it. That's how I did it.

Well I finally sent it to repair service, but I wanna know. Is there a way to backup stock boot and recovery IMG's? (in case i screw it up again)

drumandbassfreak said:
Well I finally sent it to repair service, but I wanna know. Is there a way to backup stock boot and recovery IMG's? (in case i screw it up again)
Click to expand...
Click to collapse
I have the factory images here https://drive.google.com/folderview?id=0B1SOxwG8KsFkMFdicjdEQXEzMTA# to use em, just flash with sp flash tools or mtk droid root and tools
Sent from my KAZAM Thunder Q45 using XDA Free mobile app

How do I enter flash mode?

ROM MIUI V5 for KAZAM THUNDER Q4.5
I'm glad to announce that I successfully ported Miui ROM for Kazam, download link will be available soon. Send me a email for request ROM

[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!

How do you unpack and repack boot.img?

NOTE: Unfortunately I've had to remove links from this post because I'm a new user. I'll add them back in once I have enough posts.
I've been trying to edit a file in boot.img from the CyanogenMod 12.1 (huashan) nightlies but I'm experiencing some issues finding the right tools/methods for the job.
Most scripts I've found expect an Android Magic number at the beginning of the file but this simply isn't there. It seems there is no header at all that matches the specification from bootimg.h (missing link) though I did discover the cmdline argument at the end of the file with a hex editor.
After searching and experimenting for hours I found a script here (missing link) which enabled me to extract the kernel and ramdisk images despite the missing header but now I don't know how to repack the files into a boot.img of the same structure.
I've tried the following but it results in a boot.img that is about 40% larger than the orginal (despite me only adding one line of code) and has an entirely different structure (with an Android Magic number, etc.).
Code:
mkbootimg --base 0x00200000 --pagesize 2048 --kernel boot.img-kernel.gz --ramdisk newramdisk.cpio.gz -o newboot.img
I found this resource (TWRP, missing link) which mentions that Xperia devices have special boot images (or something like that, I didn't understand all of it) - this might explain why the boot.img structure is so different - but I can't find any further documentation on this or instructions on how to deal with the format.
The Xperia devices have a recovery-in-boot arrangement. This means that the recovery is booted using the regular kernel / boot image in the device. Team Win has worked with the FreeXperia device maintainers to come up with a way to extract the ramdisk from the FOTAKernel partition and use the ramdisk from that partition instead of the recovery that is included in the boot image of your device. This means that if you install current CM nightlies and flash TWRP to the FOTAKernel partition, you will be able to use TWRP instead of the CWM or CM recovery that normally comes in a CM boot image. Other boot images including stock kernels can be repacked to include this extraction utility to allow you to use TWRP from the FOTAKernel partition. This setup allows you to choose what recovery you want to have installed and allows you to update your recovery more easily. Unfortunately this setup requires that the boot image that you have installed include the ramdisk extraction utility.
Click to expand...
Click to collapse
So now I'm at a loss at how to continue. I would much appreciate any pointers, ideas or help in general.

@infernalpostcard , hopefully this tool made by @Adrian DC will help you out.
https://github.com/AdrianDC/android_huashan_bootimg_editor

Raienryu said:
@infernalpostcard , hopefully this tool made by @Adrian DC will help you out.
https://github.com/AdrianDC/android_huashan_bootimg_editor
Click to expand...
Click to collapse
Thanks. This looks really promising. I'm trying it out now...
EDIT: It worked! This is exactly what I needed. Unfortunately what I was actually trying to achieve (apply a fix to break a boot-loop my phone gets in, due to an encrypted filesystem) didn't work so I'll have to come up with new ideas.