Related
[DEV]TWRP RECOVERY FOR LG D315 F70
Warning : This operation involves risk. XDA community or me can not be held responsible for any problems
Hi everyone!
Well, Since this smartphone is somewhat forgotten in the Android community, I decided to work on it ! I unlocked the fastboot and ported TWRP Recovery for the LG F70 ! It works on the D315, for others I really don't know ... But since I did the porting myself it must be considered as an alpha version x ') The only problem is I had to use a theme for TWRP, because the default theme was too big for this phone :/ Well you might say, it is nice like that ! The themer is "z31s1g". Anyway. If some people want to test and give feedback, this is here
First, make sure your phone is rooted (you can do it with towelroot) and make sure you have the Android SDK installed, and the LG drivers.
Download my attachment and extract it on your computer.
Right now you have to activate fastboot, fastboot is hidden behind the download mode, so backup your download mode :
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img.
And now set zero the download mode with this command, then reboot :
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
adb reboot
Now you have replaced the download mode by fastboot. Let's start fastboot, to do so, you have to turn off your phone, hold Vol+ button and plug in the USB cable.
On the console, do this command to check if phone is connected and detected.
Code:
fastboot devices
There should be a random sequence of numbers, and "fastboot" displayed.
So now we will proceed to flash the recovery with this command :
Code:
fastboot flash recovery c:\PathToTheRecoveryImage\recovery.img
Then reboot with this command :
Code:
fastboot reboot
Done ! This is my first tutorial in english... I'm a 17 years old french user, excuse me if my english is bad x)
************************************************************************************
UPDATE HERE, BOOTLOADER UNLOCKED AND NEW RECOVERY
************************************************************************************
Thanks in advance if someone want to test it and post a feedback, I will make a little list of what's working / not working (I already tested it, I didn't see nothing right now Enjoy !
KuroHaki said:
TWRP RECOVERY FOR LG D315 F70
Warning : This operation involves risk. XDA community or me can not be held responsible for any problems
Hi everyone!
Well, Since this smartphone is somewhat forgotten in the Android community, I decided to work on it ! I unlocked the fastboot and ported TWRP Recovery for the LG F70 ! It works on the D315, for others I really don't know ... But since I did the porting myself it must be considered as an alpha version x ') The only problem is I had to use a theme for TWRP, because the default theme was too big for this phone :/ Well you might say, it is nice like that ! The themer is "z31s1g". Anyway. If some people want to test and give feedback, this is here
First, make sure your phone is rooted (you can do it with towelroot) and make sure you have the Android SDK installed, and the LG drivers.
Download my attachment and extract it on your computer.
Right now you have to activate fastboot, fastboot is hidden behind the download mode, so backup your download mode :
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img.
And now set zero the download mode with this command, then reboot :
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
adb reboot
Now you have replaced the download mode by fastboot. Let's start fastboot, to do so, you have to turn off your phone, hold Vol+ button and plug in the USB cable.
On the console, do this command to check if phone is connected and detected.
Code:
fastboot devices
There should be a random sequence of numbers, and "fastboot" displayed.
So now we will proceed to flash the recovery with this command :
Code:
fastboot flash recovery c:\PathToTheRecoveryImage\recovery.img
Then reboot with this command :
Code:
fastboot reboot
Done ! This is my first tutorial in english... I'm a 17 years old french user, excuse me if my english is bad x)
Thanks in advance if someone want to test it and post a feedback, I will make a little list of what's working / not working (I already tested it, I didn't see nothing right now Enjoy !
Click to expand...
Click to collapse
Hello, it seems that only me and you have this phone. So, I'd like to root my phone, do you think that I could use towelroot without risk?
I think I'll try your guide too... after root
Thanks in advance
Yes, you can use Towelroot, but for the recovery, remember it's only a first test, and I don't know if the bootloader is locked... but the recovery seems to work
good. towelroot works well and I have no problem since now. do you think I could install gravity box in this phone with stock rom? how can I unroot this phone? thanks in advance
It was not able to enter the Fastboot
Hi. I thank you TWRP who porting. I have not imagined and think you made using the TWRP in the F70 model. However Execution has not been in the loading screen of the download mode it is not possible that you have used the dd if = / dev / zero of = ~~ command as described in your article, but to enter the fastboot.
How can I do? I use F370s model.
I'm sorry. I use google translations...
d315
hi. also have the korean version of this phone. can i use international rom on this phone so that mine test isnt korean language?
---------- Post added at 03:47 PM ---------- Previous post was at 03:41 PM ----------
can someone confirm this
seventivi.blogspot.com/2014/10/upgradeupdate-lg-f70-d315-to-50-lollipop.html
mrteejay said:
hi. also have the korean version of this phone. can i use international rom on this phone so that mine test isnt korean language?
Click to expand...
Click to collapse
I think yes. I've Singapore's version of D315 and flashed a Hungarian D315 rom with no problem.
You can download some ROMs from 4pda F70 Flash thread.
rom
Thats freakin awesome. Can you guide me on how u accomplished flashing ur phone. So far im only rooted
mrteejay said:
Thats freakin awesome. Can you guide me on how u accomplished flashing ur phone. So far im only rooted
Click to expand...
Click to collapse
I've used this tool (this tool has a tutorial on its page). After flashing you have to root again.
Duble check to be sure that you have lg d315 model and downloaded lg d315 firmware!
This is the model of my phone. It didnt say it is d315. But i read it its the same only it is the korean version. See attached image. Should i go continue flash?and what is the consequence if i use different rom for my phone?
mrteejay said:
This is the model of my phone. It didnt say it is d315. But i read it its the same only it is the korean version. See attached image. Should i go continue flash?and what is the consequence if i use different rom for my phone?
Click to expand...
Click to collapse
There is no guarantee for a successful firmware flash.
What if flashing failed? Can i revert back?
mrteejay said:
What if flashing failed? Can i revert back?
Click to expand...
Click to collapse
If flashing failed you will have to disassemble a bootloader and to correct security checks inside.
So, It's possible but VERY hard.
Hi all ! I just worked on this phone night and day x)
I just unlocked the bootloader, and made a CWM port (I personnally prefer CWM x) ) And i'm working to make a port of Cyanogenmod 11, but i'm only 17 y-o and... Well, that's too hard for me x) I've compiled it, with bin blobs, and other stuff, all the config files, etc, but it's not working YET x) (If anyone want to help me I can share my project...) Well :
/!\ For Recovery to work, you MUST unlock the bootloader by this method, this is very simple (Thanks to Zaaap72) /!\
CWM 6.0.5.0 : CWM 6.0.5.0.img
Method to unlock bootloader (not by me) : http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
The G2 Mini (D620) Has the same architecture as the F70, I mean Qualcomm msm8226, Snapdragon400, Same amount of ram, etc, BUT, not the same screen... And I'm trying to adapt the cutom kernel, and sources of D620 CM11 for my F70 x) Again, If anyone can/want help me
(Remember that the recoveries I made are in beta-test, this is my first try, and I will update them in the future, If you find any bugs, tell me, or modify the .img by yourself with AIK and upload the image for me Thanks !)
Have a nice day guys
KuroHaki, what version of device (D315/F370), device region and firmware (v10a/b/c...) bootloader did you use to unlock? Zaaap72's unlock method is very risky and unstable solution. The best solution is on 4pda, Anyway you're done!
You can try to make a recovery image with LG-L70 recovery binary and F70 kernel. It may work, I've made like that before with MTK devices.
I have a v10b D315, and I used the 4-bytes method, on aboot and abootb, it awesomely worked I played with chance on this, and it worked x) If anyone want to test it on another firmware/model of F70... And for the Image, I don't need recovery, I need a Kernel that can boot Cyanogenmod, because the LG sources make my phone bootloop on the LG first logo... I tried with Zaaap port of Quarx sources, with no success... Kernel compilation is very hard for me, I had many errors with Drivers on Quarx source, I changed the files with errors with files from LG source, and It compiled, but not worked... I don't understand why... Well, if anyone have a solution for this kernel... x)
I am the owner LG F70 phones and watches this topic for a long time but did not move anything, whether it was by the opportunity to do any ROM for this device ?
Wow! Thanks for this Recovery!!!! Was looking a while for twrp on the F70! :good:
I did flash the recovery successfully with the method in the OP. However, when I reboot to recovery (adb reboot recovery) it failed to boot TWRP - a screen showed 'secure boot error' then there were was a dump screen with lots of drives mounted to my linux pc.
This is likely because I didn't unlock the boot loader right? However, the method provided to unlock looks a bit too risky - especially since I dont have a recovery to restore if the stuff break the system. Anyway, thanks for this!
@up
I don't think so the unlock bootloader it's dangerous. I have done files aboot and abootb so i can send you.
Russian LG bootloader guru Andrew-New from 4pda has made a patched bootloader for lg d315 from v10b aboot.bin as I've requested him.
Hi everybody!
On our 4pda.ru forum we are struggling with this phone in two ways- rootin it and unlocking in order to update manually to 2.0 and even 2.2; and other way- working android (already have beta rom which is exact copy of rom from another alcatel 6014x which runs android and similar to our Fire E 6015x).
if there are any enthusiasts about android, i can translate the guide for you and share the needed files and programs. Almost everything works except sim-card(when there is no one- phone asks to insert it, when there is one- phone says its not registered) but we are working on it
i came over a https://www.soeren-hentzschel.at/mo...ch-verteilt-firefox-os-2-0-und-firefox-hello/ that states that in Germany some people already received 2.0 update on their Fire E. Here arises my question- are here people who own updated Fire E? I mean update to 2.0.
If there are ones, would you be so kind to make a copy of your rom for our little development? I can provide you with guides and software on how to do it.
I can post guides for making this an android phone.
Hi my dear russian brother - greetings from Germany.
I do have an updated 6015x device to FFOS2.0 and I could dump the rom for U. Just gimme links to the needed info. My russian is not one of my strength, but I think I can manage it - I'm a bulgarian after all.
hej, i also have a 6015X (fire e) with firefox os 2.0 running
tell me how to make a rom which i can send to you
root
After few months of waiting my phone get the forefoxos2.0 update
01008d yes it is fine but how to root it?
cybervitexud said:
After few months of waiting my phone get the forefoxos2.0 update
01008d yes it is fine but how to root it?
Click to expand...
Click to collapse
Look, please, do you have in System settings parameters of russian language on your FFOS 2.0.
HOWTO ROOT ALCATEL OT 6015X:
1. Download CWM recovery image made for 6014x.
https:// yadi.sk/d/BIdXndcbfR2Gm
2. Download Install-SuperSU.
download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. Turn your phone to bootloader mode anyway.
4. Run modrecovery:
Code:
fastboot boot my_recovery.img
5. In CWM menu follow "install zip" -> "install zip from sideload"
6. On pc:
Code:
adb sideload UPDATE-SuperSU-v2.46.zip
7. reboot phone
I am sure lowlevel utilities from android's SuperSU are working fine on any FFOS (because FFOS based on Android now).
WBR
Alcatel's stock ROM for the Fire E has been published at sourceforge.net in the Alcatel project.
dermartinac said:
Alcatel's stock ROM for the Fire E has been published at sourceforge.net in the Alcatel project.
Click to expand...
Click to collapse
I wonder how do you use it though, can you build it on its own? The B2G by Mozilla still hasn't got an option for this device.
Svinka said:
Look, please, do you have in System settings parameters of russian language on your FFOS 2.0.
HOWTO ROOT ALCATEL OT 6015X:
1. Download CWM recovery image made for 6014x.
https:// yadi.sk/d/BIdXndcbfR2Gm
2. Download Install-SuperSU.
download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. Turn your phone to bootloader mode anyway.
4. Run modrecovery:
Code:
fastboot boot my_recovery.img
5. In CWM menu follow "install zip" -> "install zip from sideload"
6. On pc:
Code:
adb sideload UPDATE-SuperSU-v2.46.zip
7. reboot phone
I am sure lowlevel utilities from android's SuperSU are working fine on any FFOS (because FFOS based on Android now).
WBR
Click to expand...
Click to collapse
I tried your recovery image but it doesn't seem to work. There is no error but after booting the image, the device isn't visible in fastboot or adb. For that reason, I'm unable to sideload the Su zip update.
sybiam said:
I tried your recovery image but it doesn't seem to work. There is no error but after booting the image, the device isn't visible in fastboot or adb. For that reason, I'm unable to sideload the Su zip update.
Click to expand...
Click to collapse
Flashing the recovery image works though, then sideloading the SU image works from clock work mode recovery.
Ok, here's some news. I built a boot image that enables adb as root. All you need is to flash it on the boot partition and reboot the phone. I made a few changes to the boot image.
default.prop
Code:
ro.secure = 0
ro.debuggable = 1
To flash:
Code:
fastboot flash boot boot3.img
and replaced /sbin/adbd by an adbd built with "ALLOW_ADBD_ROOT". (I used the sources fetched using b2g repo).
Cool thing..wish I am able
Sent from my SM-G7102 using XDA Free mobile app
Hi. Update firefox os 3.0?
lirondeespaña said:
Hi. Update firefox os 3.0?
Click to expand...
Click to collapse
As far as i know even Firefox OS 2.2 is not officially released yet.
There are only pre Versions.
Has anybody else troubles with FFOS 2.0 on the Alcatel Fire E?
The phone sometimes hangs completely while it was sleeping. (Can´t wake up or even call the phone)
Only if i press the start button for some seconds the phone starts again.
I hope someone builds a FFOS 2.2 Rom for the Fire E --> Copy and paste :good:
How can I switch this piece of **** called smartphone to bootloader mode?
Softbricked 6015x
Hey guys,
I got stuck with creating the boot.img and figured out that the backed up one doesn't work.
Does anybody have a working boot.img for the 6015x, NOT the 6014x?
I tried also getting the venezuelian one, but those TLDs are not reachable anymore - all gone.
The custom boot images from the russian 4pda forum are also not working.
I currently have only access to ADB, the TWRP recovery mod (temporarily) and fastboot, so I need a fastboot working image.
The Mobile Upgrade Q / TCL Updater / QDST distribution updater is Windows only - and crawling the binaries for URLs is a dead-end. The tool also requires
a fully booted OS, so it's pretty much the dumbest update tool out there and not practical to use. As I don't have Windows, the imgc files for the eMMC flashing tool are also a dead-end.
I really need only the boot.img file.
I really need only the boot.img file.
Click to expand...
Click to collapse
Did you try my boot img?
sybiam said:
Did you try my boot img?
Click to expand...
Click to collapse
Yes, my device constantly reboots and fails to initialize the display (seems like an Xorg alike error to me) when trying to figure out what logcat shows.
Due to the constant reboots I can't debug it using adb, because of constantly lost connections. That's why I'm asking for an OEM boot.img file.
I started to collect the working stuff over at github.com/martensms/alcatel-6015x (cant post links -_-)
cmartensms said:
Yes, my device constantly reboots and fails to initialize the display (seems like an Xorg alike error to me) when trying to figure out what logcat shows.
Due to the constant reboots I can't debug it using adb, because of constantly lost connections. That's why I'm asking for an OEM boot.img file.
I started to collect the working stuff over at github.com/martensms/alcatel-6015x (cant post links -_-)
Click to expand...
Click to collapse
Did you try to boot with fastboot or did you flash it to the boot partition. I had no success booting with fastboot but flashing works. That said, you have to install a custom recovery image.
Also, I'm working on building FFOS from sources but as won't be home for a month, it's kind of slow.
sybiam said:
Did you try to boot with fastboot or did you flash it to the boot partition. I had no success booting with fastboot but flashing works. That said, you have to install a custom recovery image.
Also, I'm working on building FFOS from sources but as won't be home for a month, it's kind of slow.
Click to expand...
Click to collapse
Both. Didn't work. As I said, I have no functioning boot image available. All boot images, from everywhere including your one, don't work.
I don't know what's so hard to understand. NO custom boot.img works. Seriously. None. Simple as that. I tried 9 different boot.img out, I even tried extracting the eMMC boot.img which obviously failed.
Again, third time, I just need an OEM boot.img in order to get further debugging my device because I can't debug my device in 3 second disconnect intervals from ADB.
edit: I unbricked my device now and made backup images of all OEM partitions - github.com/martensms/alcatel-6015x
cmartensms said:
Both. Didn't work. As I said, I have no functioning boot image available. All boot images, from everywhere including your one, don't work.
I don't know what's so hard to understand. NO custom boot.img works. Seriously. None. Simple as that. I tried 9 different boot.img out, I even tried extracting the eMMC boot.img which obviously failed.
Again, third time, I just need an OEM boot.img in order to get further debugging my device because I can't debug my device in 3 second disconnect intervals from ADB.
edit: I unbricked my device now and made backup images of all OEM partitions - github.com/martensms/alcatel-6015x
Click to expand...
Click to collapse
That's weird, my custom boot works on my own phone. 6015x, it's a russian phone. Firmware revision: 01005, hardware revision 01, platform version: 28. Firefox OS 1.3.0.0 .
I guess, if you had a newer version of Firefox, there could be something wrong with the boot image.
I have ported EFIDroid (developed by @m11kkaa) for the Nexus 5.
@m11kkaa's original EFIDroid thread here: https://forum.xda-developers.com/android/software-hacking/efidroid-t3447466.
This is an unofficial port of beta software. I am not responsible for anything that may happen to your device. Use at your own risk.
NOTE: This has been tested with last LineageOS Build (21/03/2017) and TWRP 3.1.0-0. All other configurations are untested by me, but should work.
Working ROMs
[Here I will post the ROM's that are working for multiboot (Of course I will need people's feedback to fullfill this list)]
LineageOS 14.1 (As primary, as secondary with SELinux permissive option)
DU 11.2 (As primary, as secondary with SELinux permissive option) tested by @AndresOrue
PureNexus 7.1.1 (Should work as primary but not tested, as secondary with SELinux permissive option) tested by @AndresOrue
Lineage OS DarkRom by Dark_Eyes (As primary, not tested as secondary-should work with SELinux permissive option) tested by @willyinpr4u
AlmostVanillaAOSP Marshmallow (As primary, not tested as secondary-should work with SELinux permissive option) tested by @alessio89g
AOSP Nougat (Should work as primary but not tested, as secondary with SELinux permissive option) tested by @alessio89g
UntouchedAOSP 6.0.1 tested by @BreckZeBoulay
MiUI 8 tested by @sa4ni
Euclidean OS tested by @willyinpr4u
Xenon HD AOSP tested by @willyinpr4u
AICP 12.1 7.1.2 tested by @phpbb3
Elixr-hammerhead-V1.1-20140420 tested by @playerkirk1
Plasma-Mobile tested by me
Installation
Install the attached EFIDroid Manager apk. Since this is an unofficial port, the EFIDroid Manager app from the Play Store won't work. (This is modified to use my unofficial server)
Open the EFIDroid Manager app, open the menu (at the top left), and click "Install/Update".
Click the big orange Install button.
And voila, you're done in 3 easy steps! Reboot to see your new 2nd-stage bootloader!
Post below with your installed ROM if you have success.
To update EFIDroid, just repeat step 2, and the click the big orange Update button.
The app won't automatically check for updates, so I'll post an announcement on this thread whenever an important update is available.
Migrating from MultiROM
TWRP Backups should work fine but as /sdcard gets mocked on TWRP for secondary ROMs to prevent an "accidental" wipe there is some steps to follow
1-Create a new slot
2-Go to /data/media/0/multiboot/your_new_slot/data
3-Create folder media/0/TWRP/BACKUPS
4-Move/copy your backup to the created folder -remember the backup folder is the one that look like a hash (like "'03480ffg04395g234")
5-Boot TWRP from EFIDroid for the new slot
6-Format System
7-Flash your backup
Multibooting
You can use EFIDroid as a multiboot manager. To add a multiboot ROM, do the following:
Open the EFIDroid Manager app. Press the plus button at the bottom right side of the screen to start adding a multiboot slot.
Under "Location", there should be a couple paths. Select the one containing "/data/media/0".
You can give the slot a name/description by using the appropriate fields.
Press the checkmark at the top right side of the screen to create the multiboot slot.
Reboot. When EFIDroid comes up, select TWRP, then select the newly created slot.
Go to the "Wipe > Advanced Wipe" menu. Select "System", then swipe to wipe.
Install all the zips you want on that slot.
NOTE: To prevent accidentall data loss when booting in recovery the real /sdcard gets mocked so you are not going to find your .zips as usual under TWRP's /sdcard. To acces the "real" /sdcard go to /multiboot/data/media/0
Reboot, and when EFIDroid comes up, your new slot should automatically be selected. Press the power button to boot, and enjoy!
IMPORTANT:your main ROM should boot without changing any configuration on EFIDroid but secondary ROM's are used to fail because of selinux denials. I strongly reccomend you to enable Force SELinux to permissive under EFIDroid options (the Gear icon in the main screen placed at the top right) - Once you kwon your secondary ROM is working you can try to boot without this option disabled - If you end up in a bootloop logcat and dmesg are welcome.
Troubleshooting
If you are unable to boot the OS/recovery from EFIDroid, do the following (you do have a working boot.img (from your main OS) and recovery.img (TWRP 3.1.0-0 recommended), right?)
This assumes you have fastboot properly setup. (Ubuntu: sudo apt-get install android-tools-fastboot - Windows: just google for the binaries)
OPTION 1:
In EFIDroid, use the volume keys to navigate to "Fastboot", the press the power key to select it.
There should only be one entry in the Fastboot menu. Press the power key to select it.
Connect your phone to your computer with a USB cable. Run the following (on the computer), one line at a time:
Code:
fastboot flash boot <path/to/boot.img>
fastboot flash recovery <path/to/recovery.img>
fastboot oem exit
In EFIDroid, use the volume keys to navigate to the back button at the top of the screen. Press the power key to select.
Use the volume keys to navigate to "Reboot", then press the power key to select.
OPTION 2:
Enter LG's Fastboot Mode (Volume Down + Power Off)
Connect your phone to your computer with a USB cable. Run the following (on the computer), one line at a time:
Code:
fastboot flash boot <path/to/boot.img>
fastboot flash recovery <path/to/recovery.img>
fastboot reboot-bootloader
Use the volume keys to navigate and select "Start" or "Recovery", then press the power key to select.
You should be able to boot the installed OS/recovery now. If this doesn't work, you can always enter Fastboot Mode (Volume Down + Power Off) and then flash your recovery and boot from there.
Clarifications
When Installing EFIDroid boot and recovery partitions are flashed so you only can enter recovery through EFIDroid to prevent any confusion
To enter Recovery just select your recovery on EFIDroid and then select the ROM you want the recovery to apply the .zip you are going to flash (EFIDroid properly patches TWRP ramdisk to affect the desire slot/ROM)
How does this work?
Well I'm going to explain it a little:
Right now you have your ROM kernel (boot.img) custom or stock ( it don't mind) in your boot partition and your recovery.img (I think TWRP) in your recovery partition. UEFIDroid is a kernel but it is not a linux kernel, it's based on Little Kernel aka LK... Qualcom port LK to Snapdragon chipsets and developed their custom bootloader, then the EFIDroid developer take this and implemented UEFI over the Qualcom's LK port.
Whe you install EFIDroid this is what happens:
-EFIDroid Manager backups your boot.img and recovery.img in /data/media/0/UEFIESP folder
-EFIDroid Manager flash EFIDroid in your boot and your recovery partitions (the recovery is flashed to prevent you using your recovery without booting it from EFIDroid)
Then the next time you boot the stock bootloader aka aboot loads UEFIDroid that is flashed in your boot partition, LK kernel boots and execute UEFI. Then the UEFI looks for the original boot.img (for booting your actual ROM aka Internal) and looks for your actual recovery.img, remember both were saved into /data/media/0/UEFIESP.
And finally it looks for slots/ROMs in /data/media/0/multiboot (of course these are the slots for multibooting a lot of ROMs).
A slot for a ROM is composed by a data folder, a system.img(1GB) and a boot.img (these are the ones used/mounted to boot the ROM you select in multiboot menu) -slots are added from EFIDroid Manager app.
In the last step it shows you the Menu to select what you want to boot and it applies the propers patchs to ramdisk to use the correct data folder and system.img, then boot the correct boot.img using libboot (the usually used by android bootloaders)
Recoveries
I personally tested EFIDroid with TWRP and TWRP CAF in their 3.1.0.0 versions and they worked great.
As I stated before, your current recovery is backed up to /data/media/0/partition_recovery.img so if you somehow ended having trouble to boot your recovery, you can boot to your main OS and replace /data/media/0/partition_recovery.img with another recovery (ofc change the name of the new recovery to partition_recovery.img) - YOU NEED A ROOT BROWSER -
Custom Kernels
Well custom kernels are known to break things, so to say that a ROM is working I need you to test with the stock kernel that comes with it, then of course if you want to test custom kernels you're welcome and I will update this post with your feedback.
NOT WORKING CUSTOM KERNELS:
ElementalX 7.09 (Don't pass EFIDroid boot Splash Screen) tested by @AndresOrue with DU 11.2 (It should not matter because it's not booting the ROM at all) -may be ramdisk patching problem-
WORKING CUSTOM KERNELS:
BluSpark r122 tested by @AndresOrue
Franco.Kernel r105 tested by @alessio89g
ElementalX 8.00 tested by me
Credits
-All credit goes to @m11kkaa for doing all the hard work in developing EFIDroid.
-@abraha2d for the help with porting and giving permission to use his post for Note 4 as the base for this one!
Kernel Special Features: UEFI, MultiBoot
Version Information
Status: Beta
Current Beta Version: 0.1
EFI Specification: 2.60
Beta Release Date: 2017-03-27
Created 2017-03-28
Last Updated 2017-04-17
-Initial Release 2017-03-27
Bugs:
ElementalX 7.09 Kernel not booting (may be ramdisk compression incompatibility)
Screen blinks when using AROMA Installers in TWRP (no details) - AROMA Installer is usable but in a very annoying way :/
Flashable scripts logs are not shown in TWRP console when flashing in a secondary ROM (no details)
Thank you mate for it, i will try it as soon as i can and i let you know how it works.
Edited: app installed, works ok so far
Edit2: @lukss12 mate the new boot Menu works but the phone don't boot anymore. I don't try to install new roms only reboot the phone but it only says rebooting android 7.1.1 internal .
I solved the problem, i dirty flash my rom ( du 11.2).
My rom: DU 11.2 android 7.1.1
Anyway at night i will try again
The prospect of an alternative to multirom is exciting. The great hammerhead lives on!
AndresOrue said:
Thank you mate for it, i will try it as soon as i can and i let you know how it works.
Edited: app installed, works ok so far
Edit2: @lukss12 mate the new boot Menu works but the phone don't boot anymore. I don't try to install new roms only reboot the phone but it only says rebooting android 7.1.1 internal .
I solved the problem, i dirty flash my rom ( du 11.2).
My rom: DU 11.2 android 7.1.1
Anyway at night i will try again
Click to expand...
Click to collapse
Great you could solve ur problem, yes flashing boot.img from your actual ROM will boot the device. Remember EFIDroid is also installed in your recovery partition, you can boot TWRP from there but if you want to revert back to "stock" DU with TWRP you need to flash TWRP to recovery partition.
About your boot problem, mine takes about 7 seconds on "booting" splash before showing bootanimation...
Did you try to set Force Selinux permissive option in Efidroid?
Also for the internal ROM you can try unpatched boot... For this boot efidroid and long press the power button on the Entry for your ROM.
lukss12 said:
Great you could solve ur problem, yes flashing boot.img from your actual ROM will boot the device. Remember EFIDroid is also installed in your recovery partition, you can boot TWRP from there but if you want to revert back to "stock" DU with TWRP you need to flash TWRP to recovery partition.
About your boot problem, mine takes about 7 seconds on "booting" splash before showing bootanimation...
Did you try to set Force Selinux permissive option in Efidroid?
Also for the internal ROM you can try unpatched boot... For this boot efidroid and long press the power button on the Entry for your ROM.
Click to expand...
Click to collapse
Did you try to set Force Selinux permissive option in Efidroid?
No i will try it at night.
About your boot problem, mine takes about 7 seconds on "booting" splash before showing bootanimation...
For me 5 min and nothing.
Also i need to read a little more to avoid problems.. and also i think when flash suspersu breaks the boot but i need to confirm it
AndresOrue said:
Did you try to set Force Selinux permissive option in Efidroid?
No i will try it at night.
About your boot problem, mine takes about 7 seconds on "booting" splash before showing bootanimation...
For me 5 min and nothing.
Also i need to read a little more to avoid problems.. and also i think when flash suspersu breaks the boot but i need to confirm it
Click to expand...
Click to collapse
Yep I recommend reading the full OP once or twice before starting....well is good to see that the app and installation is working... It's weird that you can't boot internal - please if you can try the unpatched boot option-
lukss12 said:
Yep I recommend reading the full OP once or twice before starting....well is good to see that the app and installation is working... It's weird that you can't boot internal - please if you can try the unpatched boot option-
Click to expand...
Click to collapse
Questions:
What is lf laf recovery?
I flashed twrp from my pc but i still have this new boot, other way to deleted?
How can i deleted this app completely? flashing stock rom is ok or i can flash a custom rom with full wipe?
Anyway now i am doing a backup of my app So I can try it without problems
AndresOrue said:
Questions:
What is lf laf recovery?
I flashed twrp from my pc but i still have this new boot, other way to deleted?
How can i deleted this app completely? flashing stock rom is ok or i can flash a custom rom with full wipe?
Anyway now i am doing a backup of my app So I can try it without problems
Click to expand...
Click to collapse
Enter fastboot mode (volume down + power off)
fastboot flash recovery twrp.img
fastboot reboot-bootloader
Select recovery
Flash your ROM zip
Or extract boot.img from your ROM zip
Enter fastboot mode
fastboot flash boot boot.img
fastboot flash recovery twrp.img
Both of those options will revert your boot and recovery partition to "stock"
I apologize for the question, but I did not understand a bit, efidroid will be work if I have installed a custom kernel?
lukss12 said:
Enter fastboot mode (volume down + power off)
fastboot flash recovery twrp.img
fastboot reboot-bootloader
Select recovery
Flash your ROM zip
Or extract boot.img from your ROM zip
Enter fastboot mode
fastboot flash boot boot.img
fastboot flash recovery twrp.img
Both of those options will revert your boot and recovery partition to "stock"
Click to expand...
Click to collapse
A few things:
To revert to stock recovery, I had to repeat two times the process of flashing the boot.img and twrp.
Obviously you lose root at this time.
Installed EFIdroid again and now first rom boot ok , no more "booting android internal" for 5 min anymore. I dont know if it because I reflashed the boot image again or maybe was the custom kernel because now i have stock DU kernel.
Now i try to add a second rom:
1) Steps from EFIdroid to create second rom works great.
2) rebooting ok
3) I selected twrp and install DU 11.2
4) installation was ok
5) Rebooting into second rom , bootloop in bootanimation after five minutes it freeze and reboot
6)edited here ( i forgot the part of change selinux to permissive )
7) wipe and installed again the second rom and finally second rom boot ok , using DU 11.2 as second rom.
8) Supersu was intalled and works ok in second rom too.
I can confirm now that the reason that the first and second rom dont boot was elementalX kernel. With the stock DU kernel works perfect. primary and secondary rom.
I hope it helps...
Questions:
how i delete second rom completely ? only with full wipe?
---------- Post added at 09:02 PM ---------- Previous post was at 08:57 PM ----------
MINECRAFT4PDA said:
I apologize for the question, but I did not understand a bit, efidroid will be work if I have installed a custom kernel?
Click to expand...
Click to collapse
the first time that i installed EFIdroid i was using elementalx 7.09 and it installed ok but first rom dont boot anymore. The second time, after i reflashed the boot image from DU the rom boot fine
edited: I can confirm now that with elementalX the rom dont boot
MINECRAFT4PDA said:
I apologize for the question, but I did not understand a bit, efidroid will be work if I have installed a custom kernel?
Click to expand...
Click to collapse
Well I'm going to explain it a little:
Right now you have your ROM kernel (boot.img) custom or stock ( it don't mind) in your boot partition and your recovery.img (I think TWRP) in your recovery partition. UEFIDroid is a kernel but it is not a linux kernel, it's based on Little Kernel aka LK... Qualcom port LK to Snapdragon chipsets and developed their custom bootloader, the EFIDroid developer take this and implemented UEFI over the Qualcom's LK port.
Whe you install EFIDroid this is what happens:
-EFIDroid backups your boot.img and recovery.img in /data/media/0/UEFIESP folder
-EFIDroid Manager flash EFIDroid in your boot and your recovery partitions (the recovery is flashed to prevent you using your recovery without booting it from EFIDroid)
Then the next time you boot the stock bootloader aka aboot loads UEFIDroid that is flashed in your boot partition, LK kernel boot and execute UEFI. Then the UEFI looks for the original boot.img (for booting your actual ROM aka Internal) and looks for your actual recovery.img, remember both were saved into /data/media/0/UEFIESP.
And finally it looks for slots/ROMs in /data/media/0/multiboot (of course these are the slots for multibooting a lot of ROMs).
-An slot for a ROM is composed by a data folder, a system.img(1GB) and a boot.img (these are the ones used/mounted to boot the ROM you select in multiboot menu) -slots are added from EFIDroid Manager app.
In the last step it shows you the Menu to select what you want to boot. It applies the propers patchs to ramdisk to use the correct data folder and system.img and boot the correct boot.img using libaboot (the usually used by android bootloaders)
Deleted
AndresOrue said:
Installed EFIdroid again and now first rom boot ok , no more "booting android internal" for 5 min anymore. I dont know if it because I reflashed the boot image again or maybe was the custom kernel because now i have stock DU kernel.
Click to expand...
Click to collapse
Great so DU works as internal , and secondary with SELinux permissive
AndresOrue said:
I can confirm now that the reason that the first and second rom dont boot was elementalX kernel. With the stock DU kernel works perfect. primary and secondary rom.
Click to expand...
Click to collapse
Yes it is possible that a custom kernel is making problem to patch ramdisk
AndresOrue said:
Questions:
how i delete second rom completely ? only with full wipe?
Click to expand...
Click to collapse
No, you don't need full wipe. Slots/ROMs are stored ind /data/media/0/multiboot/your_rom, just delete "your_rom" folder with a root browser and goodbye ROM.
AndresOrue said:
Deleted
Click to expand...
Click to collapse
Sorry I was on the phone and it's a little slow to write and QUOTE there.
I have not tested custom kernels because I don't use them, I think is possible that the custom kernel makes ramdisk patching to fail
lukss12 said:
Sorry I was on the phone and it's a little slow to write and QUOTE there.
I have not tested custom kernels because I don't use them, I think is possible that the custom kernel makes ramdisk patching to fail
Click to expand...
Click to collapse
Sorry too mate I posted it before I read that you replied to me... yes DU11.2 works as primary and secondary rom. I will try others roms tomorrow but so far all is working great in secondary rom.
Thank you for you work!!!
AndresOrue said:
Sorry too mate I posted it before I read that you replied to me... yes DU11.2 works as primary and secondary rom. I will try others roms tomorrow but so far all is working great in secondary rom.
Thank you for you work!!!
Click to expand...
Click to collapse
There is no need to thank I'm doing this for fun
It' can be usefull if you got us some dmesg and logcat logs when the secondary ROM is bootlooping because of the SELinux permissive option not enabled. - you can get this with adb, the ROM bootloops but adb should get started at some point (of course you need to properly boot to the ROM the first time and enable adb and authorize your computer -
Thanks for the testing and wathever you have to share about using EFIDroid is usefull
lukss12 said:
There is no need to thank I'm doing this for fun
It' can be usefull if you got us some dmesg and logcat logs when the secondary ROM is bootlooping because of the SELinux permissive option not enabled. - you can get this with adb, the ROM bootloops but adb should get started at some point (of course you need to properly boot to the ROM the first time and enable adb and authorize your computer -
Thanks for the testing and wathever you have to share about using EFIDroid is usefull
Click to expand...
Click to collapse
Here is the log from second rom with selinux permissive not enable.
Also I confirm that the first rom boot ok with selinux permissive not enable ( selinux as enforcing ).
tell me if the log are correct, if not i try again.
Edited: i did some more test:
I tried as secondary pure nexus rom version : purenexus_hammerhead-7.1.1-20170216-HOMEMADE and boot ok in permissive enable
Also as secondary and permissive enable, I tried DU11.2 with the kernel blu_spark_r122_hammerhead_5472df4 and here boot ok too. It Does not hang up, with the massage " booting android 7.1.1" ( so elementalX 7.09 doesn't work so far).
Thanks for taking the time for this amazing work.
Just downloaded the .apk and installed, boot to EFIDroid, I guess, because I saw a never before seen menu with my internal ROM, TWRP, etc...
As of now it's late where I'm from, but I will download a secondary ROM later and post results.
Thanks.
willyinpr4u said:
Thanks for taking the time for this amazing work.
Just downloaded the .apk and installed, boot to EFIDroid, I guess, because I saw a never before seen menu with my internal ROM, TWRP, etc...
As of now it's late where I'm from, but I will download a secondary ROM later and post results.
Thanks.
Click to expand...
Click to collapse
Yep that "never seen before menu" is EFIDroid hehe, so your primary ROM is booting ok, please share what ROM you are using. And remember to enable Force SELinux permissive when booting a secondary ROM to prevent a SELinux denial bootloop, then you can try with the option disabled. But if the LineageOS kernel, that is the most "normal" kernel I know, couldn't do it I don't think any other could boot with SELinux enforced as secondary ROM. Anyways logcat and dmesg from a bootloop are useful and welcome.
DISCLAIMER
unlocked bootloader is required , Me or any contributor in the software or XDA or Any where in the world DOES NOT take responsibility of damages caused to your phone due to this ROM....! Proceed at your own risk your warranty is void now
Caution : back up your TA partition if not yet Unlocked boot loader ... , ITS NOT PRE ROOTED ROM , so CONSIDER Before proceeding you may loose some features ... how ever its perfectly root-able with SU v 2.82 SR1 201706 This rom is for those who just need BASIC aosp android with minimal apps and most basic apps installed Only...so enjoy ..
How to Flash Instructions
Boot your phone into fast boot mode ( Plug in the usb cable connected to your pC while holding the volume up button ) it will turn on the blue light
Flash the system image by entering the command fastboot flash system system.img Down here
Flash the boot image by entering the command fastboot flash boot boot.img Download from here
Reboot
After First boot , the IMEI and base band will not be available to some users ( known issue post AOSP flashing same happened for Noughat build as well ) , to solve this flash following Modem file via recovery mode to resolve the modem issue.
MODEM Files
Following method is working but since some users reported FC so Halting below until its fixed m working on it.
1. Copy ROM zip to your sd card
2. Go to your Recovery TWRP 3.xx is recommended ( not tested on any other )
3. Full Wipe
4. Flash the Zip
5. Reboot and enjoy.
Additional : Install Gapps
Gapps :
http://opengapps.org use MM 6.0.1 version
Whats Working
Every thing ..! Camera working fine ,
ROOTING
Download SU v 2.82 SR1 201706 and Flash Via Recovery
Whats Not working
Nothing so far i noticed
DownLoad link
Working but Due to Force Closure reports in Google play some work still needs to be done.
Download Version 1.1
CREDITS:
Sony devices AOSP sources ,
erikcas
zacharias.maladroit
SUPERUSER
[*]XDA devs.
[*]Google AOSP build guides
[/LIST]
XDA:DevDB Information
MarshMallow Stock AOSP rom , ROM for the Sony Xperia Z Ultra
Contributors
pintspin
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Unlocked BootLoader Atleast 5.1.1 base
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 1.1
Stable Release Date: 2017-06-17
Created 2017-06-22
Last Updated 2017-06-24
Reserved
Reserved
I flashed this rom. in bootscreem (Android), phone turns off...
What is model is it 6833 ? And which recovery. You are using ? Its recommended twrp 3.xx its not tested on other recov and did you performed full wipe ?
sollysally said:
I flashed this rom. in bootscreem (Android), phone turns off...
Click to expand...
Click to collapse
pintspin said:
What is model is it 6833 ? And which recovery. You are using ? Its recommended twrp 3.xx its not tested on other recov and did you performed full wipe ?
Click to expand...
Click to collapse
Is this patch included in the rom?
https://github.com/opengapps/opengapps/wiki/Notes-for-Android-6.0
https://github.com/TeamExodus/frameworks_base/commit/9c36be651e83fb039a262682839bd920b033007a
SUPERUSER said:
Is this patch included in the rom?
https://github.com/opengapps/opengapps/wiki/Notes-for-Android-6.0
https://github.com/TeamExodus/frameworks_base/commit/9c36be651e83fb039a262682839bd920b033007a
Click to expand...
Click to collapse
No its working without theses patches I have tested it . just need to reenter recovery after first boot n then flash gapps pico its working fine
pintspin said:
What is model is it 6833 ? And which recovery. You are using ? Its recommended twrp 3.xx its not tested on other recov and did you performed full wipe ?
Click to expand...
Click to collapse
yes, it is 6833 and twarp 3.0.2
and I do full wipe
SUPERUSER said:
Is this patch included in the rom?
https://github.com/opengapps/opengapps/wiki/Notes-for-Android-6.0
https://github.com/TeamExodus/frameworks_base/commit/9c36be651e83fb039a262682839bd920b033007a
Click to expand...
Click to collapse
Can u guide me how to include this PAtvh I will try to include this on week end preferred ably if u can send terminal commands to cherry. Pick .
pintspin said:
No its working without theses patches I have tested it . just need to reenter recovery after first boot n then flash gapps pico its working fine
Click to expand...
Click to collapse
I have to disagree with you on this one.
I have had it working too and figured out different orders to flash additional zips in recovery to get the phone to boot without it dying at the boot animation but there were tons of force close every time I installed something from play store.
There is some workarounds like a-gapps and beansgapps that can cope better without the patch.
But you need to implement it.
SUPERUSER said:
I have to disagree with you on this one.
I have had it working too and figured out different orders to flash additional zips in recovery to get the phone to boot without it dying at the boot animation but there were tons of force close every time I installed something from play store.
There is some workarounds like a-gapps and beansgapps that can cope better without the patch.
But you need to implement it.
Click to expand...
Click to collapse
OK I will can you send me terminal command of cherry pick of above two patches ? I will definitely include these but still don't get reason why its not working because I tested it my device n it worked with out any patch really
pintspin said:
Can u guide me how to include this PAtvh I will try to include this on week end preferred ably if u can send terminal commands to cherry. Pick .
Click to expand...
Click to collapse
Im no dev on Android devices but here is a user who simplified a way on how to "use" the patch by a bashfile. Execute and you're done.
https://github.com/jomo/fix_open_gapps_permissions
Perhaps send a pm to some active user here who posts roms?
I have limited knowledge of working with source code and It was years since I compiled software mostly on Slackware, Gentoo and bsd. Haven't had much interest for it until not long ago. Perhaps I'll learn with time..
SUPERUSER said:
Im no dev on Android devices but here is a user who simplified a way on how to "use" the patch by a bashfile. Execute and you're done.
https://github.com/jomo/fix_open_gapps_permissions
Perhaps send a pm to some active user here who posts roms?
I have limited knowledge of working with source code and It was years since I compiled software mostly on Slackware, Gentoo and bsd. Haven't had much interest for it until not long ago. Perhaps I'll learn with time..
Click to expand...
Click to collapse
thanks Superuser , unfortunately i am also a bit new to Rom development although i figured out from this link that i need to included one .SH script and which need to be executed while installing the rom , i learn how to run .SH via edify but its keep on giving me Error 6 , i am sure that its the syntax issue only
i am hopefull that some one can tell me how to do it prperly i am pasting the code here my edify code is below
( the .SH script is on the root of Sdcard
Code:
package_extract_file("a.sh", "/sdcard/a.sh");
set_perm(0, 0, 0755, "/sdcard/a.sh");
run_program("/sdcard/a.sh");
i have added above 3 lines on my edify scrpt i have omiited the lines of .system and .boot images
OPTION 2 ,
as an Alternative i will going to post the .system and .boot images here for manual flashing via fastboob method.
Uploaded the system and boot images + modem fix , needs to be loaded via fastboot ... and Enjoy ... hope it wont give FC . because its pure aosp fresh build files. NON customized
regards
pintspin said:
thanks Superuser , unfortunately i am also a bit new to Rom development although i figured out from this link that i need to included one .SH script and which need to be executed while installing the rom , i learn how to run .SH via edify but its keep on giving me Error 6 , i am sure that its the syntax issue only
i am hopefull that some one can tell me how to do it prperly i am pasting the code here my edify code is below
( the .SH script is on the root of Sdcard
Code:
package_extract_file("a.sh", "/sdcard/a.sh");
set_perm(0, 0, 0755, "/sdcard/a.sh");
run_program("/sdcard/a.sh");
i have added above 3 lines on my edify scrpt i have omiited the lines of .system and .boot images
OPTION 2 ,
as an Alternative i will going to post the .system and .boot images here for manual flashing via fastboob method.
Click to expand...
Click to collapse
shouldn't it be a six before the 755.
Code:
package_extract_file("a.sh", "/sdcard/a.sh");
set_perm(0, 0, 06755, "/sdcard/a.sh");
run_program("/sdcard/a.sh");
I'm on my phone and text is disappearing when I zoom in in Firefox but..
Are you using a proper text editor like Notepad++ ?
Is the system partition being mounted before your insert of that code?
You can perhaps try this tool
https://forum.xda-developers.com/showthread.php?t=2599759
Its a tool to review the formatting. It's very easy to miss a spot that might be causing the syntax error.
Ask in this Q&A thread https://forum.xda-developers.com/showthread.php?t=1770284&page=145
pintspin said:
Uploaded the system and boot images + modem fix , needs to be loaded via fastboot ... and Enjoy ... hope it wont give FC . because its pure aosp fresh build files. NON customized
regards
Click to expand...
Click to collapse
Hi, Newbie question. I got the system and boot images loaded and roms starts up fine, modem just doesn't work.
How do i loaded the modem fix?
C:\Users\Dennis\Desktop\Sony Xperia Z Ultra\C6833 Modem Patch>fastboot flash modem c6833-modem.zip
target didn't report max-download-size
sending 'modem' (273 KB)...
OKAY [ 0.015s]
writing 'modem'...
FAILED (remote: Command not allowed)
finished. total time: 0.029s
Btw, how can i root my phone? I tried loads of stuff, i don't bother the root access for most things like controlling the firewall, but do i need it also to install custom recovery? I've got the bootloader unlocked, but i would like to have CWM installed as well because i currently have no recovery options available.
SubZeRo666 said:
Hi, Newbie question. I got the system and boot images loaded and roms starts up fine, modem just doesn't work.
How do i loaded the modem fix?
C:\Users\Dennis\Desktop\Sony Xperia Z Ultra\C6833 Modem Patch>fastboot flash modem c6833-modem.zip
target didn't report max-download-size
sending 'modem' (273 KB)...
OKAY [ 0.015s]
writing 'modem'...
FAILED (remote: Command not allowed)
finished. total time: 0.029s
Btw, how can i root my phone? I tried loads of stuff, i don't bother the root access for most things like controlling the firewall, but do i need it also to install custom recovery? I've got the bootloader unlocked, but i would like to have CWM installed as well because i currently have no recovery options available.
Click to expand...
Click to collapse
you need to install a custom recovery and then flash the modem .zip file from recovery .
Download the recovery from this link
save it to your adb folder
you need to do the following steps
1, Fastboot Flash recovery recovery.img
2, reboot into recovery by typing the command while you stay in fastboot
fastboot boot recovery.img
3, once you will be in recovery , just press install zip button or install button
4, select the location where you saved the modem.zip
5, flash it .
6, reboot,
once reboot just wait for 3-4 minutes and your are done....!
regards
can we flash this without using the PC method , flashable Zip please? :\
OmarKhalifa said:
can we flash this without using the PC method , flash-able Zip please? :\
Click to expand...
Click to collapse
Yes Omar you can but some users reported that its giving them issues . so i am trying to fix it once its fixed
i will re upload the zip file but still if wanna give it a go ( please back up every thing of your data ) then there is a link available in the first post under you can try and adivse back if you have getting same issues or not other wise a good option is to use the fastboot mode its working fine without issues .
downloads for zip
Memória ram
Hi, I was wondering if this is just 1.4 Gb memória Ram
Hi,
I am working on a Pixel 5 phone. I have made some changes to the default kernel (redfin-rq1a.210105.003). I am able to build the kernel successfully (using build_redbull.sh which uses build.config.redbull.no-cfi )without any errors. However, I am having problems with flashing it. The default build script located at build/build.sh seems to also export the new boot.img(9.3Mb) to the out/../dist/ folder. When I try to boot this image file with "fastboot boot boot.img" my phone gets stuck on startup google logo.
I also tried to follow a second method with Android Kitchen. However, the problem with this method is I am unable to unpack the "default" boot.img with the unpacking.sh script. It throws an error:
./unpackimg.sh: line 218: 28549 Segmentation fault: 11 "$bin/$arch/unpackbootimg" -i "$img"
Error!
"
I tried the android kitchen method with PROTON kernel V1.1(in the description it says it comes with a custom flasher). The unpacking.sh script seems to work on this one. However, When I replace the "ProtonKernel-pixel5-v1.1.img-zImage"(1.7Mb) with my "Image.lz4-dtb" (9.3Mb) (generated by the build script in out/../dist/ folder) the repacking.sh does not work. It throws an "buffer" too short error.
So I am right now unable to test my kernel. I am a beginner and would really appreciate if anyone can provide me step by step direction to flash my custom kernel.
I am having similar issues trying to flash a modified kernel on the Pixel 5.
And it seems like there isn't much help available online regarding the flashing process (on Google etc.)
Any help would be appreciated.